Peripheral device calling method, peripheral device calling system and electronic device

Abstract

The application discloses a peripheral device calling method, a peripheral device calling system and electronic equipment, and relates to the field of financial technology. The method comprises the following steps: receiving a peripheral device calling request sent by a business system, wherein the peripheral device calling request comprises the identification of a current operator and the identification of a current peripheral device; when it is determined that the current operator has the permission to call the current peripheral device according to the pre-stored calling permission information, calling the current peripheral device according to the pre-stored peripheral device interface specification and the driving instance of the current peripheral device; obtaining the current user information collected by the current peripheral device; performing a desensitization operation on the current user information to obtain the current desensitized user information, and performing encryption on the current desensitized user information according to the pre-stored security parameters to obtain the current encrypted user information; sending the current encrypted user information to the cloud, and receiving the verification result sent by the cloud; and sending the verification result to the business system. The method improves the reusability and security of the peripheral device calling process.

Description

Technical Field

[0001] This invention relates to the field of financial technology, and in particular to a peripheral device invocation method, a peripheral device invocation system, and an electronic device. Background Technology

[0002] In the financial industry, especially in bank counter services, peripheral devices (hereinafter referred to as peripherals) are the core hardware supporting business operations. Peripherals include fingerprint scanners, printers, in-counter clearing devices, out-of-counter clearing devices, and seal control devices. Counter systems, bank-enterprise reconciliation systems, and other business systems interface with peripherals to enable the use of their functions.

[0003] In related technologies, the peripheral device integration solution commonly used in the financial industry is an architecture in which the peripheral device platform is deeply integrated with the counter system. The startup, update and device call of the peripheral device platform all depend on the corresponding functions of the counter system.

[0004] However, in the aforementioned peripheral device integration solutions, the peripheral device platform is tightly bound to the counter system, lacking independent operation and deployment capabilities. It cannot provide peripheral device access services to other business systems such as bank-enterprise reconciliation systems. The peripheral device platform has poor reusability, requiring each business system to independently develop peripheral device adaptations, resulting in significant duplication of development and increased construction and maintenance costs. Furthermore, the lack of access control for operators during peripheral device access leads to high security risks. Summary of the Invention

[0005] This invention provides a peripheral device invocation method, a peripheral device invocation system, and an electronic device to solve the technical problems of poor reusability and high security risks in peripheral device invocation methods in related technologies.

[0006] According to one aspect of the present invention, a peripheral device invocation method is provided, applied to an edge node located in a financial institution branch, the method comprising: Receive peripheral call requests sent by the business system; wherein, the peripheral call request includes the identifier of the current operator and the identifier of the current peripheral; When it is determined, based on pre-stored access permission information, that the current operator has permission to call the current peripheral device, the current peripheral device is called according to the pre-stored peripheral device interface specification and the driver instance of the current peripheral device. Obtain the current user information collected by the current peripheral device; The current user information is de-identified to obtain the de-identified user information. Then, the de-identified user information is encrypted according to the pre-stored security parameters to obtain the encrypted user information. The access permission information, the peripheral interface specifications, and the security parameters are all information that is pre-sent from the cloud to the edge node. The system sends the current encrypted user information to the cloud and receives the verification result sent by the cloud; wherein the verification result is the information obtained by the cloud after decrypting the current encrypted user information and verifying it. The verification result is sent to the business system.

[0007] According to another aspect of the present invention, a peripheral device access system is provided, the system comprising: a cloud, an edge node, and a peripheral device; The edge nodes are connected to the cloud and the peripheral devices, respectively. The edge node is used to execute the peripheral invocation method described in any of the above embodiments; The cloud is used to receive the current encrypted user information, decrypt the current encrypted user information, verify it, obtain the verification result, and send the verification result to the edge node.

[0008] According to another aspect of the present invention, a peripheral device calling device is provided, the device being disposed at an edge node, the edge node being disposed at a branch of a financial institution, the device comprising: The first receiving module is used to receive peripheral call requests sent by the business system; wherein, the peripheral call request includes the identifier of the current operator and the identifier of the current peripheral. The calling module is used to call the current peripheral device according to the pre-stored peripheral device interface specification and the driver instance of the current peripheral device when it is determined that the current operator has the right to call the current peripheral device based on the pre-stored calling permission information. The first acquisition module is used to acquire the current user information collected by the current peripheral device; The first determining module is used to perform a de-identification operation on the current user information to obtain the current de-identified user information, and encrypt the current de-identified user information according to the pre-stored security parameters to obtain the current encrypted user information; wherein, the calling permission information, the peripheral interface specification, and the security parameters are all information pre-sent to the edge node by the cloud; The first sending module is used to send the current encrypted user information to the cloud. The second receiving module is used to receive the verification result sent by the cloud; wherein, the verification result is the information obtained by the cloud after decrypting the current encrypted user information and verifying it; The second sending module is used to send the verification result to the business system.

[0009] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the peripheral invocation method described in any embodiment of the present invention.

[0010] According to another aspect of the present invention, a computer-readable storage medium is provided, the computer-readable storage medium storing a computer program configured to cause a processor to execute and implement the peripheral invocation method described in any embodiment of the present invention.

[0011] According to another aspect of the present invention, a computer program product is provided, comprising a computer program that, when executed by a processor, implements the peripheral invocation method described in any embodiment of the present invention.

[0012] The technical solution of this invention, based on a peripheral invocation system that integrates cloud, edge nodes, and peripheral devices, allows edge nodes located in financial institution branches to enable business systems to invoke current peripherals. Firstly, the business systems in this embodiment are not limited to counter systems, thus decoupling the peripheral invocation process from the counter system. Edge nodes can invoke peripherals for any business system that needs to, improving the reusability of the peripheral invocation process, avoiding redundant development, and reducing the construction and maintenance costs of business systems. Secondly, edge nodes can verify the invocation permissions of the current operator. The current peripheral is only invoked when the operator is confirmed to have the necessary permissions, preventing information security issues caused by unauthorized operators invoking peripherals and reducing security risks during the peripheral invocation process. Furthermore, encrypted user information is sent to the cloud, preventing sensitive data from being directly transmitted to the cloud, further reducing security risks. Thirdly, invocation permission information, peripheral interface specifications, and security parameters are all information pre-sent from the cloud to the edge nodes, enabling remote operation and maintenance of the edge nodes from the cloud, improving operational efficiency and reducing operational costs.

[0013] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

[0014] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0015] Figure 1 This is a schematic diagram of the structure of a peripheral device calling system provided in an embodiment of the present invention; Figure 2 This is an application diagram of a peripheral device calling system provided in an embodiment of the present invention; Figure 3 This is a flowchart of a peripheral device invocation method provided in an embodiment of the present invention; Figure 4 This is a flowchart of another peripheral device invocation method provided in an embodiment of the present invention; Figure 5 This is a flowchart of another peripheral device calling method provided in an embodiment of the present invention; Figure 6 This is a flowchart of another peripheral device invocation method provided in an embodiment of the present invention; Figure 7 This is a schematic diagram of the structure of a peripheral device calling device provided in an embodiment of the present invention; Figure 8 This is a schematic diagram of the structure of an electronic device that implements the peripheral device invocation method of this invention. Detailed Implementation

[0016] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0017] It should be noted that the terms "currently," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the term "comprising" and any variations thereof are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0018] In this embodiment of the invention, the acquisition, storage, use, and processing of data all comply with relevant national laws and regulations. The information collected in this embodiment of the invention is information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, storage, use, processing, transmission, provision, disclosure, and application of related data all comply with relevant national and regional laws, regulations, and standards, necessary confidentiality measures have been taken, and public order and good morals have not been violated. Corresponding operation entry points are provided for users to choose to authorize or refuse.

[0019] In related technologies, the architecture of deep integration between peripheral platforms and counter systems has the following problems.

[0020] 1. Poor platform reusability and prominent siloed construction issues: The peripheral platform is strongly bound to the counter system, lacks independent operation and deployment capabilities, and cannot provide peripheral calling services for other business systems such as bank-enterprise reconciliation systems. The number of counter-type business systems in various bank branches is increasing year by year, and each business system needs to independently carry out peripheral adaptation development, forming a siloed construction model, resulting in a large amount of redundant development and increasing the construction and maintenance costs of business systems.

[0021] 2. Low efficiency in operation and maintenance and configuration management: Logs are only stored locally on the computer devices running the peripheral platform, without a unified log center and monitoring and alarm system, making it difficult to troubleshoot peripheral faults and monitor their operating status; peripheral configuration adopts a local update mode on the terminal, without centralized configuration management and distribution capabilities, resulting in low configuration maintenance efficiency, a large workload for synchronizing configurations across multiple terminals, and a tendency for configuration inconsistencies to occur.

[0022] 3. Inconsistent peripheral device interface standards and lack of masking of manufacturer differences: There is no unified interface standard for peripheral devices. The calling interfaces and protocols of peripheral devices of the same type but different brands are different. Business systems need to develop interface logic separately for devices from different manufacturers. The adaptation cycle is long and the adaptation efficiency is low when adding or replacing devices.

[0023] 4. Lack of compatibility with the domestic IT innovation environment: The existing technology stack uses C language to call the vendor's dynamic link library (DLL), which is only compatible with non-domestic IT innovation terminals and cannot run on domestic IT innovation operating systems and domestic chip architectures. This does not meet the requirements of the development of the domestic IT innovation industry and cannot meet the construction needs of the full-stack domestic IT innovation in the financial industry.

[0024] 5. Outdated technology stack, high development and maintenance costs: The C language used has a high development threshold and cumbersome syntax, poor flexibility in dynamic library calls, difficulty in cross-platform development and debugging, low development efficiency for subsequent platform function iterations and expansions, and high maintenance costs.

[0025] To address the aforementioned issues, this embodiment provides a peripheral invocation system with a three-tier collaborative architecture consisting of a cloud management platform (also known as the cloud), edge nodes, and peripheral terminals (also known as peripherals), realizing a peripheral invocation method based on edge computing. Figure 1 This is a schematic diagram of the structure of a peripheral device calling system provided in an embodiment of the present invention. Figure 1 As shown, this embodiment provides a peripheral invocation system that coordinates cloud, edge nodes, and peripheral devices. The edge nodes are located in financial institution branches. For example, the financial institution in this embodiment can be a bank. Figure 1 Let's take an example with N financial institution branches. Each branch deploys at least one edge node. When there are multiple edge nodes, a master-slave configuration can be used among them. Figure 1 The example of deploying two edge nodes at each financial institution branch is used to illustrate this point.

[0026] Figure 2 This is an application diagram of a peripheral device calling system provided in an embodiment of the present invention. For example... Figure 2 As shown, the content above the gateway represents the functionality implemented by edge nodes, while the content below the gateway represents the functionality implemented by the cloud. Edge nodes can display information through HyperText Markup Language 5 (HTML5), Cascading Style Sheets 3 (CSS3), Vue, TypeScript, and NGINX static resource management. The cloud management platform can implement basic services such as Spring Boot, Gateway, Druid, JDBC, and Fastjson, as well as third-party services such as end-to-end monitoring, signature verification, and log collection. The cloud management platform can also cache data and manage logs, and implement operations and maintenance through containerization engines (such as Docker), container management platforms (such as KubeSphere), integrated R&D security and operations (such as ADevSecOps), version control systems (such as Git), and project management tools (such as Maven). The cloud management platform can also implement functions such as Optical Character Recognition (OCR), large-scale front-end services, Robotic Process Automation (RPA) services, and intelligent teller assistants.

[0027] To facilitate understanding of this solution, the development process of the peripheral device calling system will be briefly introduced below.

[0028] In this embodiment, the front end of the edge node uses Python technology stack to realize cross-platform peripheral calls, the cloud uses Java microservices to build a cloud management platform, and the edge node deploys lightweight containerized components to undertake local computing tasks. At the same time, a unified peripheral interface specification and a full-link security architecture are designed. The specific implementation steps include steps 1 to 5.

[0029] Step 1: Build a three-level collaborative architecture of "cloud-edge-device".

[0030] The cloud management platform in this embodiment is built on a distributed microservice cloud-native architecture, integrating components such as a configuration registry, log center, tracing, and message queue. It is responsible for global configuration distribution, unified device management, log aggregation and analysis, security policy management, and edge node scheduling. Security policy management is used to configure security policies such as access permissions and security parameters. Edge node scheduling controls the online / offline status of edge nodes and the number of replicas of edge nodes.

[0031] In this embodiment, the edge nodes can adopt a lightweight containerized deployment scheme. Furthermore, the edge nodes in this embodiment can be adapted to domestically developed container platforms. The edge nodes integrate driver invocation modules in a pre-defined programming language (e.g., Python), local caching modules (e.g., a lightweight version of Redis), data encryption modules, and local offline task queues, enabling peripheral device invocation, data preprocessing, local caching, and other computing tasks to be offloaded, avoiding reliance on real-time cloud connections. In this embodiment, data preprocessing refers to the edge nodes encapsulating information that needs to be uploaded to the cloud into a unified message format.

[0032] The peripheral terminals in this implementation include peripheral devices such as fingerprint scanners, printers, cabinet clearing devices, and cabinet clearing devices. They support both domestically developed and non-domestically developed terminals and communicate with local edge nodes through preset protocols, such as HyperText Transfer Protocol (HTTP), to perform specific hardware operations.

[0033] The key design features of the peripheral device invocation system in this embodiment include the following: Edge node deployment location: Deployed in the computer rooms of financial institution branches or local servers close to peripheral terminals, achieving "one branch, one edge" localized service. Cloud and edge node collaboration: Dynamic registration of edge nodes is achieved through a registration center. The cloud distributes peripheral interface specifications, invocation permission information, security parameters, etc., to the edge node cache. Edge nodes periodically synchronize their operating status and log data to the cloud. Deployment adaptation: Both the cloud management platform and edge nodes are adapted to the domestic IT innovation platform, meeting the requirements of full-stack domestic IT innovation.

[0034] Step 2: Select a cross-platform technology stack and set up a development environment.

[0035] Optionally, the technology stack of the front-end client of the edge node in this embodiment is as follows: Python is selected as the development language, and its C language type (ctypes) module is used to efficiently call DLL / Shared Object (SO) dynamic libraries, cross-platform features and rich third-party libraries to adapt to the peripheral driver calls of domestic and non-domestic innovation terminals.

[0036] Optionally, the cloud technology stack in this embodiment adopts a general development framework, is based on microservice development, and the project structure is divided into a common component module, a driver management module, a lightweight module (to realize login, parameter management, etc.), and a communication module (to realize communication between the server and edge nodes), etc., supporting containerized deployment and elastic expansion.

[0037] Optionally, the edge node technology stack in this embodiment adopts a lightweight container framework adapted from Kubernetes (K8s) and integrates Python driver calling components, AntDB-Lite local caching components, national cryptographic algorithm encryption components, and offline task queue components to ensure lightweight and high-performance operation of edge nodes.

[0038] Development environment setup: Set up development and testing environments that are compatible with both domestic and international innovation platforms, and integrate the DevOps engineering practice system, including continuous integration, security scanning, quality access control, automated testing, and continuous deployment capabilities.

[0039] Step 3: Establish a unified interface standard for peripheral devices.

[0040] For core peripherals used in bank teller operations, such as fingerprint scanners, printers, in-counter clearing devices, out-of-counter clearing devices, and seal control devices, we have compiled a list of core functions and calling logic for each type of device. This list masks the interface and protocol differences between different manufacturers, and establishes unified peripheral interface specifications and function lists. It clearly defines the interface declarations, parameter definitions, return value specifications, and timeout mechanisms for peripheral calls. The function list here includes all the functions that various peripherals can perform.

[0041] For example, the fingerprint scanner interface specification includes: defining fingerprint feature value reading (Read function), fingerprint template reading (Mould function), fingerprint template synthesis (Composite function), and detecting whether the finger is lifted. The fingerprint template synthesis refers to writing fingerprint feature values ​​into the fingerprint template. The general peripheral interface specification: for peripherals such as printers, internal and external clearing devices, it uniformly defines interface protocols for device initialization, function calls, status queries, and anomaly feedback, supporting various peripheral standards such as the Pioneering Information System Architecture / Protocol for Financial Terminal Standard Service (PISA), Linux Financial Services Extension Specification (LFS), and Windows Open System Architecture (WOSA), achieving loose coupling between applications and peripherals.

[0042] Step 4: Develop the core functional modules for “cloud-edge-device” collaboration.

[0043] The core functions of the cloud and edge nodes will be described in detail in subsequent embodiments.

[0044] Step 5: Adaptation and docking test of peripheral devices.

[0045] 5.1 Driver Adaptation: Communicate with various peripheral manufacturers to obtain domestically developed and non-domestically developed version device drivers, and encapsulate the driver dynamic library through the ctypes module to enable cross-platform driver calls.

[0046] 5.2 Standardization: In accordance with the established unified peripheral interface standard, develop interface development for devices such as fingerprint scanners, printers, cabinet internal clearing devices, and cabinet external clearing devices to shield the differences in manufacturer interfaces.

[0047] 5.3 Functional Testing: In both domestically and internationally-based terminal environments, the core functions of each peripheral device are tested to verify the stability of functions such as fingerprint reading, printing, ID card recognition, and password input.

[0048] 5.4 Performance Testing: Test the peripheral call response latency, concurrent processing capability, offline runtime, and other indicators of the edge nodes to ensure that they meet the high concurrency and low latency requirements of bank counter services.

[0049] 5.5 Compatibility Testing: Integrate the peripheral device access system with business systems such as the counter system and bank-enterprise reconciliation system to test the compatibility and stability of multiple systems sharing peripheral device services.

[0050] 5.6 Security Testing: Test data encryption transmission, access control, log security, etc., to ensure compliance with the data security classification protection requirements of the financial industry.

[0051] Step 6: Deployment and launch of the peripheral device calling system.

[0052] 6.1 Pilot Deployment: Select 1-2 pilot sites, deploy edge nodes and cloud management platforms for domestic IT innovation, adapt to core peripherals such as fingerprint scanners and printers, and verify core functions such as edge call latency, offline operation, and security encryption.

[0053] 6.2 Functional Iteration: Optimize edge node load balancing, fault self-healing, and cloud collaboration logic based on pilot feedback, and improve the adaptation of domestic IT innovation components (such as the edge framework being compatible with domestic container platforms).

[0054] 6.3 Large-scale deployment: Deploy edge nodes in batches at the branches of financial institutions, achieve unified management and control through the cloud management platform, and simultaneously complete the cloud-edge collaborative transformation of existing peripheral platforms.

[0055] 6.4. Operation and Maintenance System Setup: Establish edge node monitoring dashboards, fault alarm mechanisms, and remote operation and maintenance processes to ensure operation and maintenance efficiency after large-scale deployment.

[0056] The following details the implementation process of the peripheral calling method provided in this embodiment.

[0057] Figure 3 This is a flowchart illustrating a peripheral device invocation method provided in an embodiment of the present invention. This embodiment is applicable to scenarios in the financial industry where peripheral devices are invoked during business processing. The method can be executed by a peripheral device invocation device, which can be implemented in hardware and / or software. This peripheral device invocation device can be configured in an edge node, such as a computer device or a production server. Figure 3 As shown, the method includes the following steps 301 to 306.

[0058] Step 301: Receive peripheral call requests sent by the business system.

[0059] The peripheral device access request includes the identifier of the current operator and the identifier of the current peripheral device.

[0060] The peripheral device invocation method provided in this embodiment is based on a cloud-edge-device collaborative peripheral device invocation system. For scenarios with high real-time requirements, such as fingerprint authentication, ID card reading inside the cabinet, and password input outside the cabinet, the invocation logic is pushed down to the edge node. Compared with the way business systems communicate with the cloud, it achieves low-latency response in the peripheral device invocation process, improving business processing efficiency and user experience.

[0061] In this embodiment, the business system can be any system within a financial institution's branch that needs to call external devices, such as a counter system or a bank-enterprise reconciliation system. Compared to related technologies where the counter system and the external device calling process are strongly bound together, this embodiment decouples the external device calling process from the counter system. By setting up local edge nodes within the financial institution's branch, the business system can call the current external device without needing to access the cloud across networks.

[0062] It is understandable that in step 301, the actual process is to receive a peripheral call request sent by the computer device where the business system is located.

[0063] In this embodiment, the "current operator" refers to a staff member of a financial institution, such as a teller. The "current peripheral" refers to the peripheral that the business system needs to access at this time. For example, if the current operator needs to access a fingerprint scanner when processing a withdrawal for the current user, then the fingerprint scanner is the "current peripheral."

[0064] For example, business systems and edge nodes can exchange information via the Hypertext Transfer Protocol (HTTP).

[0065] Step 302: When it is determined that the current operator has permission to call the current peripheral device based on the pre-stored call permission information, the current peripheral device is called according to the pre-stored peripheral device interface specification and the driver instance of the current peripheral device.

[0066] To enhance the security of the peripheral device access process, step 302 verifies the access permissions of the current operator. In this embodiment, the access permission information is pre-sent from the cloud to the edge node. This access permission information indicates the peripheral device access permissions for each operator or type of operator.

[0067] In step 302, when it is determined that the current operator has permission to call the current peripheral, the current peripheral is called according to the pre-stored peripheral interface specification and the driver instance of the current peripheral. The peripheral interface specification is information pre-sent from the cloud to the edge node. In this embodiment, a unified peripheral interface specification can be pre-defined for peripherals from multiple manufacturers and of multiple types, shielding manufacturer differences, achieving loose coupling between the application and the peripheral, significantly reducing the adaptation cost of adding or replacing peripherals, and improving the reusability of the peripheral calling system.

[0068] The driver instance of the current peripheral is information pre-stored by the edge node. In this embodiment, the current peripheral is invoked according to the pre-stored peripheral interface specification and the driver instance of the current peripheral. For example, the hardware can be directly driven to invoke the current peripheral through the Python ctypes module. Optionally, the response latency of the peripheral invocation method provided in this embodiment is within 20 milliseconds (ms).

[0069] Optionally, if it is determined that the current operator does not have permission to access the current peripheral device, an insufficient permission prompt is returned to the business system.

[0070] Step 303: Obtain the current user information collected by the current peripheral device.

[0071] After the current peripheral is invoked, it begins to function. For example, if the current peripheral is a fingerprint scanner, it will begin collecting the current user's information. The peripheral then sends the collected user information back to the edge node.

[0072] In step 303, the edge node acquires the current user information collected by the current peripheral device.

[0073] Step 304: Perform a de-identification operation on the current user information to obtain the de-identified user information, and encrypt the de-identified user information according to the pre-stored security parameters to obtain the encrypted user information.

[0074] Among them, the access permission information, peripheral interface specifications, and security parameters are all information that is pre-sent from the cloud to the edge nodes.

[0075] Step 305: Send the current encrypted user information to the cloud and receive the verification result sent by the cloud.

[0076] The verification result is the information obtained by decrypting the current encrypted user information in the cloud and then verifying it.

[0077] In steps 304 and 305, cloud verification is performed to confirm the correctness of the current user information. To enhance information security, in step 304, the current user information is first anonymized to obtain the anonymized user information. Then, based on pre-stored security parameters, the anonymized user information is encrypted to obtain the encrypted user information.

[0078] Optionally, the de-identification operation in this embodiment includes at least one of the following: hash operation, partial field masking. For example, when the current user information is a fingerprint feature value, the de-identification operation can be a hash operation of the fingerprint feature value; when the current user information is identity information, the de-identification operation can be partial field masking.

[0079] Optionally, the encryption process in this embodiment can employ the SM4 block cipher algorithm (SM4). Security parameters can be SM4-related parameters. Using SM4 can meet the security compliance requirements of domestic IT innovation.

[0080] In step 304, the edge node is responsible for desensitizing and encrypting the current user information to prevent sensitive information from being directly transmitted to the cloud and improve data security.

[0081] After receiving the encrypted user information, the cloud can decrypt it and verify it. It's important to note that although the cloud obtains the anonymized user information after decryption, this anonymized information is unique and can still be used for verification. For example, if the user information is a fingerprint, the cloud compares it to a fingerprint database and the anonymized user information during verification. If a matching fingerprint exists in the database, the verification passes; otherwise, it fails. The cloud then sends the verification result to the edge nodes, which receive the result.

[0082] Step 306: Send the verification result to the business system.

[0083] After receiving the verification result, the edge node can send the verification result to the business system, thus completing a closed loop of a peripheral device call process.

[0084] In this embodiment, the cloud enables centralized management and flexible distribution of peripheral configurations, supporting unified editing, batch distribution, and synchronization between the cloud and edge nodes. Optionally, business personnel can edit configuration information through the configuration management interface of the cloud management platform. The cloud can distribute configuration information to each edge node. Edge nodes cache the configuration information and write it to their local configuration files. The configuration information in this embodiment includes access permission information, peripheral interface specifications, and security parameters.

[0085] Furthermore, the cloud in this embodiment can also support differentiated configuration distribution, allowing for the creation of personalized configuration information for different locations and different peripheral device types.

[0086] Optionally, the peripheral device invocation method provided in this embodiment further includes the following steps: receiving a configuration update notification sent from the cloud; obtaining updated configuration information from the cloud, wherein the updated configuration information includes at least one of the following: updated invocation permission information, updated peripheral interface specifications, and updated security parameters; when it is determined that the updated configuration information is compatible with the peripheral connected to the edge node, sending an update success result to the cloud; when it is determined that the updated configuration information is incompatible with the peripheral connected to the edge node, sending a configuration exception result to the cloud. In this implementation, after receiving the configuration update notification, the edge node obtains the updated configuration information from the cloud. Compared to directly receiving the updated configuration information from the cloud, this ensures that the updated configuration information is obtained when the network between the cloud and the edge node is available, avoiding transmission errors caused by network issues. Furthermore, this implementation can perform compatibility detection of the updated configuration information.

[0087] Furthermore, the peripheral device invocation method provided in this embodiment also includes the following steps: the edge node periodically synchronizes the configuration information or the execution status of the updated configuration information to the cloud to ensure that the configuration information of the cloud and the edge node is consistent.

[0088] Optionally, the edge nodes in this embodiment can adopt a primary / backup mode. If the primary edge node fails, it automatically switches to the backup edge node to execute the aforementioned peripheral device invocation method, ensuring uninterrupted service.

[0089] The peripheral device invocation method provided in this embodiment of the invention is based on a peripheral device invocation system that integrates cloud, edge nodes, and peripheral device collaboration. Edge nodes deployed in financial institution branches can enable business systems to invoke current peripheral devices. Firstly, the business systems in this embodiment are not limited to counter systems, thus decoupling the peripheral device invocation process from the counter system. Edge nodes can invoke peripheral devices for any business system that needs to do so, improving the reusability of the peripheral device invocation process, avoiding redundant development, and reducing the construction and maintenance costs of business systems. Secondly, edge nodes can verify the invocation permissions of the current operator. The current peripheral device is only invoked when it is determined that the current operator has the permission, avoiding information security issues caused by unauthorized operators invoking peripheral devices and reducing the security risks of the peripheral device invocation process. Furthermore, encrypted user information is sent to the cloud, preventing sensitive data from being directly transmitted to the cloud, further reducing security risks. Thirdly, invocation permission information, peripheral device interface specifications, and security parameters are all information pre-sent from the cloud to the edge nodes, enabling remote operation and maintenance of the edge nodes from the cloud, improving operation and maintenance efficiency, and reducing operation and maintenance costs.

[0090] Figure 4 This is a flowchart of another peripheral device invocation method provided in an embodiment of the present invention. This peripheral device invocation method... Figure 3Based on the illustrated embodiments and various optional implementations, other steps included in the method will be described in detail. For example... Figure 4 As shown, the peripheral device calling method provided in this embodiment includes the following steps 401 to 410.

[0091] Step 401: Receive peripheral call requests sent by the business system.

[0092] The peripheral device access request includes the identifier of the current operator and the identifier of the current peripheral device.

[0093] Step 402: When it is determined that the current operator has permission to call the current peripheral device based on the pre-stored call permission information, the current peripheral device is called according to the pre-stored peripheral device interface specification and the current peripheral device driver instance.

[0094] Step 403: Obtain the current user information collected by the current peripheral device.

[0095] The implementation process and technical principles of steps 401, 402, 303, and 404 are similar, and will not be repeated here.

[0096] Step 404: If the verification result is successfully obtained based on the current user information and the pre-stored user information, then send the verification result to the business system.

[0097] Step 405: If no verification result can be obtained based on the current user information and the pre-stored user information, then proceed to step 406.

[0098] This embodiment and Figure 3 The difference between the illustrated embodiment and various optional implementations is that, in this embodiment, local verification can be prioritized when verifying the current user information. Cloud verification is only performed when a verification result cannot be obtained during local verification, i.e., steps 406 to 407 below are executed.

[0099] During local verification, the verification result is determined based on the current user information and pre-stored user information. The verification result is either verification passed or verification failed.

[0100] Step 406: Perform a de-identification operation on the current user information to obtain the de-identified user information, and encrypt the de-identified user information according to the pre-stored security parameters to obtain the encrypted user information.

[0101] Among them, the access permission information, peripheral interface specifications, and security parameters are all information that is pre-sent from the cloud to the edge nodes.

[0102] Step 407: Send the current encrypted user information to the cloud and receive the verification result sent by the cloud.

[0103] The verification result is the information obtained by decrypting the current encrypted user information in the cloud and then verifying it.

[0104] Step 408: Send the verification result to the business system.

[0105] The implementation process and technical principles of steps 406, 407, 305, 408, and 306 are similar, and will not be repeated here.

[0106] Furthermore, after step 404 or step 408, the peripheral device calling method provided in this embodiment also includes the following steps.

[0107] Step 409: Record the peripheral call log of the current peripheral device and store the peripheral call log.

[0108] The peripheral call log includes at least one of the following: the current peripheral call record, the current peripheral status data, and the verification result.

[0109] Optionally, the current peripheral device call record may include a call timestamp and the identifier of the current operator. The current peripheral device status data may include whether the current peripheral device is working properly. The verification result includes verification passed or verification failed.

[0110] To facilitate subsequent backtracking, the edge nodes in this embodiment can record and store peripheral call logs after a peripheral call process is completed. Furthermore, to save storage space, the edge nodes can store peripheral call logs for a preset duration. For example, the preset duration can be 7 days, 10 days, etc.

[0111] Step 410: Identify the exception logs in the peripheral device call logs and send the exception logs to the cloud.

[0112] Among them, the anomaly log is used to determine the fault information of peripheral devices and / or edge nodes.

[0113] To reduce network traffic, edge nodes can send only exception logs from peripheral call logs to the cloud. The purpose of these exception logs is to identify fault information in peripherals and / or edge nodes.

[0114] Optionally, the exception log in this embodiment refers to a log that includes at least one of the following: peripheral call failure, verification failure, or no permission to call.

[0115] Furthermore, the peripheral device invocation method provided in this embodiment also includes the following steps: within each statistical period, determining the summary invocation data of peripheral devices connected to the edge node; and sending the summary invocation data to the cloud. The summary invocation data in this embodiment may include the number of times each type of peripheral device is invoked within a preset time period at a certain network point.

[0116] The peripheral device invocation method provided in this embodiment has two advantages. First, it prioritizes local verification to reduce peripheral device invocation latency. If local verification fails, cloud verification is then performed, improving the reliability of the verification process. Second, this embodiment records and stores peripheral device invocation logs and sends exception logs from these logs to the cloud. This reduces network traffic and enables efficient fault location in the future.

[0117] Figure 5 This is a flowchart of another peripheral device invocation method provided in this embodiment of the invention. The peripheral device invocation method provided in this embodiment... Figure 3 or Figure 4 Based on the illustrated embodiments and various optional implementations, other steps included in the method will be described in detail. For example... Figure 5 As shown, the peripheral device calling method provided in this embodiment includes the following steps 501 to 517.

[0118] Step 501: Monitor the connection status between the edge node and the cloud.

[0119] Step 502: If the connection status is determined to be network interrupted, then the current working status of the edge node is determined to be offline mode.

[0120] Step 503: If the connection status is determined to be normal, then the current working status of the edge node is determined to be online mode.

[0121] In this embodiment, the edge node can select an appropriate operating mode based on its connection status with the cloud. In step 501, the edge node can monitor its connection status with the cloud through a heartbeat detection mechanism. When the connection status indicates a network interruption, the current operating status is determined to be offline mode to ensure uninterrupted service; when the connection status indicates a normal network connection, the current operating status is determined to be online mode. That is, for scenarios where some network points have unstable or outage networks, the edge node has the capability to operate offline.

[0122] Step 504: Receive peripheral call requests sent by the business system.

[0123] The peripheral device access request includes the identifier of the current operator and the identifier of the current peripheral device.

[0124] Step 505: When it is determined that the current operator has permission to call the current peripheral device based on the pre-stored call permission information, the current peripheral device is called according to the pre-stored peripheral device interface specification and the driver instance of the current peripheral device.

[0125] Step 506: Obtain the current user information collected by the current peripheral device.

[0126] The implementation process and technical principles of steps 504, 505, 302, 506, and 303 are similar, and will not be repeated here.

[0127] It should be noted that the execution process of steps 504 to 506 is similar regardless of whether it is online or offline mode. That is, because the edge node caches core configuration information, such as call permission information, peripheral interface specifications, and security parameters, the edge node can still independently respond to local peripheral call requests when the connection between the edge node and the cloud is lost.

[0128] Step 507: If the current working status is offline mode, determine the verification result based on the current user information and the pre-stored user information, and send the verification result to the business system.

[0129] Perform local verification in offline mode: Determine the verification result based on the current user information and pre-stored user information, and send the verification result to the business system.

[0130] Step 508: Store the current peripheral device's exception log to the local offline task queue.

[0131] The current peripheral's exception log includes at least one of the following: the current peripheral's exception call record, the current peripheral's exception status data, and the exception verification result.

[0132] To ensure that exception logs generated in offline mode are not lost, edge nodes store the exception logs of current peripherals in a local offline task queue during offline mode. The purpose of the local offline task queue is to cache exception logs generated in offline mode. After the network between the edge node and the cloud is restored, the edge node can upload the exception logs in the local offline task queue to the cloud.

[0133] It should be noted that before step 508, the peripheral device calling method provided in this embodiment further includes the following steps: recording the peripheral device calling log of the current peripheral device and storing the peripheral device calling log, wherein the peripheral device calling log includes at least one of the following: the calling record of the current peripheral device, the status data of the current peripheral device and the verification result; and determining the abnormal log in the peripheral device calling log.

[0134] Step 509: If the current working status is online mode, then proceed to step 510.

[0135] It should be noted that when the current working status is online mode, it can also be done according to... Figure 4 The scheme shown in the embodiment first performs local verification: if the verification result is successfully obtained based on the current user information and the pre-stored user information, the verification result is sent to the business system; if the verification result cannot be obtained based on the current user information and the pre-stored user information, then step 510 is executed, that is, cloud verification is performed.

[0136] Step 510: Perform a de-identification operation on the current user information to obtain the de-identified user information, and encrypt the de-identified user information according to the pre-stored security parameters to obtain the encrypted user information.

[0137] Among them, the access permission information, peripheral interface specifications, and security parameters are all information that is pre-sent from the cloud to the edge nodes.

[0138] Step 511: Send the current encrypted user information to the cloud and receive the verification result sent by the cloud.

[0139] The verification result is the information obtained by decrypting the current encrypted user information in the cloud and then verifying it.

[0140] Step 512: Send the verification result to the business system.

[0141] The implementation process and technical principles of steps 510 and 304, 511 and 305, and 512 and 306 are similar, and will not be repeated here.

[0142] Step 513: Upload the current peripheral device's abnormal logs to the cloud in real time.

[0143] In online mode, after step 512, the abnormal logs of the current peripheral device can be uploaded to the cloud in real time. Optionally, before step 513, the following steps are included: recording the peripheral call logs of the current peripheral device and storing the peripheral call logs, wherein the peripheral call logs include at least one of the following: the call record of the current peripheral device, the status data of the current peripheral device, and the verification result; and identifying the abnormal logs in the peripheral call logs.

[0144] Optionally, after storing the current peripheral's exception log to the local offline task queue, the method further includes the following steps.

[0145] Step 514: If the connection status is determined to be network restored, then the current working status is determined to be online mode.

[0146] After the network is restored, the edge nodes switch back to online mode.

[0147] Step 515: Send the data in the local offline task queue to the cloud in chronological order.

[0148] After switching back to online mode, the edge nodes send the data in their local offline task queue to the cloud in chronological order. This local offline task queue contains the exception logs.

[0149] Step 516: Receive confirmation information sent from the cloud.

[0150] The confirmation information is generated by the cloud after data fusion and verification.

[0151] Optionally, the confirmation information in step 516 can be confirmation information for each piece of data sent, or confirmation information for multiple pieces of data sent. In this embodiment, the fusion verification refers to the verification of whether information loss occurred during data transmission. The confirmation information is used to indicate whether there was no information loss during transmission or whether information loss occurred during transmission.

[0152] Step 517: Once all data in the local offline task queue has been sent to the cloud and the confirmation message indicates that no data was lost during the transmission process, clear the local offline task queue.

[0153] To conserve storage space on edge nodes, all data in the local offline task queue is sent to the cloud. Once confirmation indicates that no data loss occurred during transmission, the local offline task queue is cleared. Afterward, the edge node resumes the mechanism of uploading exception logs in real time.

[0154] Furthermore, in offline mode, the edge nodes in this embodiment can also perform peripheral fault diagnosis and basic operation and maintenance, such as driver restart and configuration reset, reducing reliance on the cloud.

[0155] The peripheral device invocation method provided in this embodiment has two advantages. First, when the connection between the edge node and the cloud is interrupted, the edge node can switch to offline mode and independently respond to peripheral device invocation requests, improving the reliability of the peripheral device invocation process. Second, the edge node can store the exception logs generated in offline mode in a local offline task queue. After the network is restored, the data in the local offline task queue is sent to the cloud in chronological order to ensure that no data is lost.

[0156] Please continue to refer to Figure 1 The peripheral device access system provided in this embodiment includes a cloud, edge nodes, and peripheral devices. The edge nodes are connected to both the cloud and the peripheral devices.

[0157] The edge nodes in this system are used to execute the peripheral calling methods provided in any of the above embodiments.

[0158] The cloud in this system is used to receive the current encrypted user information, decrypt the current encrypted user information, verify it, obtain the verification result, and send the verification result to the edge node.

[0159] Optionally, both the cloud and edge nodes in this embodiment are adapted to the domestic IT innovation platform, and the communication process between the cloud and the edge nodes meets the security requirements of domestic IT innovation.

[0160] Optionally, the cloud in this embodiment can realize visual monitoring: through link tracing tools, such as SkyWalking, the central processing unit, memory usage, number of peripheral connections, call success rate and other indicators of the edge node can be monitored in real time, and cloud alarms can be triggered when the working status of the edge node is determined to be abnormal.

[0161] Optionally, in this embodiment, the edge nodes locally store detailed peripheral call logs, while the cloud stores exception logs and call summary data. The cloud can support log retrieval by edge node, peripheral type, and time range, facilitating fault location.

[0162] Optionally, the cloud in this embodiment can realize remote operation and maintenance of edge nodes: it supports remote upgrades (container image updates), configuration modifications, and troubleshooting of edge nodes without on-site operation.

[0163] Figure 6 This is a flowchart of another peripheral device invocation method provided by an embodiment of the present invention. This method describes how the cloud updates configuration information from the perspective of interaction between the cloud and edge nodes. For example... Figure 6 As shown, the peripheral device calling method includes the following steps 601 to 611.

[0164] Step 601: Receive the updated configuration information entered by the operations and maintenance personnel on the cloud management platform.

[0165] Step 602: The configuration center in the cloud records the configuration information version and filters the target edge nodes based on the updated configuration information.

[0166] Step 603: The cloud pushes configuration update notifications to the target edge nodes via message queues.

[0167] Step 604: The target edge node receives the configuration update notification.

[0168] Step 605: The target edge node obtains the updated configuration information from the cloud.

[0169] Step 606: The target edge node overwrites the existing configuration information in the local cache and writes the updated configuration information to a local file for persistent storage.

[0170] Step 607: Verify the effectiveness of the startup configuration on the target edge node.

[0171] The purpose of the configuration activation verification is to check the compatibility of the updated configuration information with the peripherals connected to the target edge node.

[0172] Step 608: If the updated configuration information is incompatible with the peripheral device, return the configuration error information to the cloud.

[0173] Step 609: Cloud-based operation and maintenance alarm is triggered.

[0174] Step 610: If the updated configuration information is compatible with the peripheral device, the updated configuration information takes effect, and the device parameters of the peripheral device connected to the target edge node are updated according to the updated configuration information.

[0175] Step 611: Send a message to the cloud indicating that the configuration update was successful.

[0176] Step 612: Update configuration status in the cloud.

[0177] For example, mark the configuration status as "effective".

[0178] The peripheral device invocation system provided in this embodiment adopts a three-level collaborative architecture design of "cloud-edge-device". It integrates edge computing technology into the domestically developed peripheral device platform, realizes local peripheral device invocation tasks through edge nodes, achieves low-latency response and offline operation capabilities for peripheral device invocation, and solves the network dependency and latency problems of centralized cloud deployment. The cloud is responsible for global management, and the edge is responsible for local execution, forming a highly efficient collaborative architecture.

[0179] This peripheral calling system adopts a full-stack cross-platform technology adapted to domestic IT innovation: the front end uses the Python technology stack, which utilizes the ctypes module's efficient calling capability for DLL / SO dynamic libraries and cross-platform characteristics to adapt to both domestic and non-domestic IT innovation terminals; the edge nodes adopt a lightweight domestic IT innovation container framework, and the cloud adopts a Java microservice architecture, with full-link adaptation to domestic chips and operating systems, meeting the requirements of domestic IT innovation industry policies.

[0180] This peripheral access system adopts a unified peripheral interface standard: it formulates a unified interface standard for peripherals from multiple manufacturers and of multiple types, shields the differences between manufacturers, achieves loose coupling between applications and peripherals, significantly reduces the adaptation cost of adding or replacing devices, and improves the reusability of the platform.

[0181] The peripheral calling system adopts an edge-side data security and offline operation mechanism: data anonymization and encryption are implemented at the edge nodes to avoid direct transmission of sensitive data to the cloud and reduce security risks; at the same time, offline operation capability is designed to cache core configurations and task queues to ensure business continuity when the network is interrupted and improve system fault tolerance.

[0182] This peripheral device access system enables centralized operation and maintenance and differentiated configuration management: it achieves unified monitoring, remote operation and maintenance, and configuration distribution of edge nodes and peripheral devices through a cloud management platform, supports differentiated configuration strategies, solves the problems of scattered logs and low configuration maintenance efficiency in traditional platforms, and reduces operation and maintenance costs.

[0183] In summary, this embodiment provides a peripheral device invocation system and method based on edge computing in a domestic IT innovation environment. It solves the problems of lack of compatibility, poor reusability, high security risks, and low operation and maintenance efficiency of existing peripheral platforms in domestic IT innovation environments. It achieves the goals of full-stack domestic IT innovation adaptation, multi-system sharing of peripheral services, data security compliance, and centralized operation and maintenance configuration. At the same time, it adopts a general and flexible technology stack to reduce development and maintenance costs, creating a technologically advanced, independently controllable, and stable "cloud-edge-device" collaborative peripheral platform to meet the peripheral device invocation needs of various business systems in financial industry branches.

[0184] The peripheral device invocation system and method provided in this embodiment have the following beneficial effects: Achieving full-stack domestic IT innovation adaptation: The peripheral device calling system in this embodiment can run stably on domestic IT innovation operating systems and domestic chip architectures, while being compatible with non-domestic IT innovation terminals, thus meeting the construction needs of full-stack domestic IT innovation in the financial industry.

[0185] Low-latency response to meet real-time business needs: Edge nodes take over peripheral device call tasks nearby, reducing response latency from 100ms in the traditional cloud mode to less than 20ms, perfectly meeting the needs of real-time scenarios such as fingerprint authentication and password input, improving business processing efficiency and user experience.

[0186] Multi-business system sharing of peripheral services reduces construction costs: This peripheral calling system has independent operation and deployment capabilities, eliminating dependence on counter systems. It can provide standardized peripheral calling services for all business systems in the branch, such as bank-enterprise reconciliation systems, avoiding the redundant development of peripheral adaptation for each business system. It is estimated that it can reduce the workload of peripheral adaptation development by more than 70%.

[0187] Data security is compliant and risks are controllable: Sensitive data is de-identified and encrypted at the edge, and only the necessary encrypted data is uploaded to the cloud, reducing the risk of leakage during cross-network transmission; the entire chain adopts national cryptographic algorithms for encryption, which meets the data security classification protection requirements of the financial industry.

[0188] Reduced network dependence and improved business continuity: Edge nodes have the ability to operate offline, can independently support basic services when the network is down, and automatically synchronize data after the network is restored to ensure continuous business operation.

[0189] Improved operation and maintenance efficiency and reduced maintenance costs: Through centralized cloud monitoring and configuration management, log retrieval and troubleshooting time is reduced from several hours to several minutes, and the workload of configuration and maintenance is reduced by more than 90%; remote operation and maintenance are supported, eliminating the need for on-site operation and significantly reducing operation and maintenance costs.

[0190] The technology stack is versatile and flexible, and iterative expansion is convenient: It adopts a general technology stack of Python + Java, which has a low development threshold, rich community support, and high flexibility in dynamic library calls.

[0191] Figure 7 This is a schematic diagram of a peripheral device access mechanism provided in an embodiment of the present invention. The device is located at an edge node. Edge nodes are located at financial institution branches. For example... Figure 7 As shown, the peripheral calling device provided in this embodiment includes the following modules: a first receiving module 71, a calling module 72, a first obtaining module 73, a first determining module 74, a first sending module 75, a second receiving module 76, and a second sending module 77.

[0192] The first receiving module 71 is used to receive peripheral call requests sent by the business system.

[0193] The peripheral device call request includes the identifier of the current operator and the identifier of the current peripheral device.

[0194] The calling module 72 is used to call the current peripheral device according to the pre-stored peripheral device interface specification and the driver instance of the current peripheral device when it is determined that the current operator has the right to call the current peripheral device based on the pre-stored calling permission information.

[0195] The first acquisition module 73 is used to acquire the current user information collected by the current peripheral device.

[0196] The first determining module 74 is used to perform a de-identification operation on the current user information to obtain the current de-identified user information, and to encrypt the current de-identified user information according to the pre-stored security parameters to obtain the current encrypted user information.

[0197] The access permission information, the peripheral interface specifications, and the security parameters are all information that is pre-sent from the cloud to the edge node.

[0198] The first sending module 75 is used to send the current encrypted user information to the cloud.

[0199] The second receiving module 76 is used to receive the verification result sent by the cloud.

[0200] The verification result is the information obtained by the cloud after decrypting the current encrypted user information and verifying it.

[0201] The second sending module 77 is used to send the verification result to the business system.

[0202] In one embodiment, the device further includes a second determining module. The second sending module 77 is further configured to send the verification result to the business system if a verification result is successfully obtained based on the current user information and pre-stored user information. The second determining module is configured to determine to execute the steps performed by the first determining module 74 if a verification result cannot be obtained based on the current user information and pre-stored user information.

[0203] In one embodiment, the device further includes a recording and storage module and a third determining module. The recording and storage module is used to record and store the peripheral call log of the current peripheral device, wherein the peripheral call log includes at least one of the following: the call record of the current peripheral device, the status data of the current peripheral device, and the verification result. The third determining module is used to determine abnormal logs in the peripheral call log. The first sending module 75 is further used to send the abnormal logs to the cloud. The abnormal logs are used to determine fault information of the peripheral device and / or edge nodes.

[0204] In one embodiment, the device further includes a monitoring module, a fourth determining module, and a fifth determining module. The monitoring module is used to monitor the connection status between the edge node and the cloud. The fourth determining module is used to determine that the current operating state of the edge node is offline if the connection status is determined to be a network interruption. The fifth determining module is used to determine that the current operating state of the edge node is online if the connection status is determined to be a normal network connection.

[0205] Optionally, the device further includes a sixth determining module, a storage module, a seventh determining module, and an uploading module. The sixth determining module is used to determine a verification result based on the current user information and pre-stored user information if the current working state is offline mode. The second sending module 77 is also used to send the verification result to the business system. The storage module is used to store the current peripheral's exception logs in a local offline task queue, wherein the current peripheral's exception logs include at least one of the following: the current peripheral's exception call record, the current peripheral's exception status data, and the exception verification result. The seventh determining module is used to determine to execute the steps performed by the first determining module 74 if the current working state is online mode. The uploading module is used to upload the current peripheral's exception logs to the cloud in real time.

[0206] In one embodiment, the device further includes an eighth determining module and a clearing module. The eighth determining module is used to determine the current working state as online mode if the connection status is determined to be network restored. The first sending module 75 is further used to sequentially send the data in the local offline task queue to the cloud in chronological order. The second receiving module 76 is further used to receive confirmation information sent by the cloud, wherein the confirmation information is information generated by the cloud after performing fusion verification on the data. The clearing module is used to clear the local offline task queue when all the data in the local offline task queue has been sent to the cloud and the confirmation information indicates that no information was lost during transmission.

[0207] In one embodiment, the device further includes a second acquisition module. The second receiving module 76 is further configured to receive a configuration update notification sent by the cloud. The second acquisition module is configured to acquire updated configuration information from the cloud, wherein the updated configuration information includes at least one of the following: updated call permission information, updated peripheral interface specifications, and updated security parameters. The first sending module 75 is further configured to send an update success result to the cloud when it is determined that the updated configuration information is compatible with the peripheral connected to the edge node. The first sending module 75 is further configured to send a configuration error result to the cloud when it is determined that the updated configuration information is incompatible with the peripheral connected to the edge node.

[0208] In one embodiment, the device further includes a ninth determining module. The ninth determining module is configured to determine the call summary data of the peripherals connected to the edge node within each statistical period. The first sending module 75 is further configured to send the call summary data to the cloud.

[0209] The peripheral device calling device provided in the embodiments of the present invention can execute the peripheral device calling method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0210] Figure 8 This is a schematic diagram of the structure of an electronic device implementing the peripheral invocation method of an embodiment of the present invention. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, production servers, blade production servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

[0211] like Figure 8 As shown, the electronic device 10 includes at least one processor 11 and a memory, such as a read-only memory 12 or a random access memory 13, communicatively connected to the at least one processor 11. The memory stores computer programs executable by the at least one processor. The processor 11 can perform various appropriate actions and processes based on the computer program stored in the read-only memory 12 or loaded from storage unit 18 into the random access memory 13. The random access memory 13 may also store various programs and data required for the operation of the electronic device 10. The processor 11, read-only memory 12, and random access memory 13 are interconnected via a bus 14. An input / output interface 15 is also connected to the bus 14.

[0212] Multiple components in electronic device 10 are connected to input / output interface 15, including: input unit 16, such as keyboard, mouse, etc.; output unit 17, such as various types of monitors, speakers, etc.; storage unit 18, such as disk, optical disk, etc.; and communication unit 19, such as network card, modem, wireless transceiver, etc. Communication unit 19 allows electronic device 10 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0213] Processor 11 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 11 include, but are not limited to, central processing units, graphics processing units, various special-purpose artificial intelligence computing chips, various processors running machine learning model algorithms, digital signal processors, and any suitable processor, controller, microcontroller, etc. Processor 11 performs the various methods and processes described above, such as peripheral invocation methods.

[0214] In some embodiments, the peripheral invocation method may be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or installed on the electronic device 10 via read-only memory 12 and / or communication unit 19. When the computer program is loaded into random access memory 13 and executed by processor 11, one or more steps of the peripheral invocation method described above may be performed. Alternatively, in other embodiments, processor 11 may be configured to execute the peripheral invocation method by any other suitable means (e.g., by means of firmware).

[0215] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays, application-specific integrated circuits (ASICs), application-specific standard products (ASICs), systems-on-a-chip (SoCs), payload programmable logic devices, computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0216] Computer programs used to implement the methods of the present invention can be written in any combination of one or more programming languages. These computer programs can be provided to the processor of a general-purpose computer, a special-purpose computer, or other device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be performed. The computer programs can be executed entirely on a machine, partially on a machine, as a standalone software package partially on a machine and partially on a remote machine, or entirely on a remote machine or production server.

[0217] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory, read-only memory, erasable programmable read-only memory (flash memory), optical fibers, portable compact disk read-only memory, optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0218] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a cathode ray tube or liquid crystal display monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0219] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data production servers), or middleware components (e.g., application production servers), or frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0220] A computing system can include clients and production servers. Clients and production servers are generally geographically separated and typically interact via a communication network. The client-production server relationship is established by computer programs running on the respective computers and having a client-production server relationship with each other. The production server can be a cloud production server, also known as a cloud computing production server or cloud host, which is a host product within the cloud computing production service system to address the shortcomings of traditional physical hosts and virtual private servers, such as high management difficulty and weak business scalability.

[0221] This invention also provides a computer program product, including a computer program that, when executed by a processor, implements the peripheral invocation method provided in any embodiment of this invention.

[0222] In the implementation of a computer program product, computer program code for performing the operations of this invention can be written in one or more programming languages ​​or a combination thereof. Programming languages ​​include object-oriented programming languages ​​as well as conventional procedural programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or production server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including local area networks (LANs) or wide area networks (WANs), or it can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0223] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.

[0224] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A method for invoking a peripheral device, characterized in that, The method, applied to edge nodes located in financial institution branches, includes: Receive peripheral call requests sent by the business system; wherein, the peripheral call request includes the identifier of the current operator and the identifier of the current peripheral; When it is determined, based on pre-stored access permission information, that the current operator has permission to call the current peripheral device, the current peripheral device is called according to the pre-stored peripheral device interface specification and the driver instance of the current peripheral device. Obtain the current user information collected by the current peripheral device; The current user information is de-identified to obtain the de-identified user information. Then, the de-identified user information is encrypted according to the pre-stored security parameters to obtain the encrypted user information. The access permission information, the peripheral interface specifications, and the security parameters are all information that is pre-sent from the cloud to the edge node. The system sends the current encrypted user information to the cloud and receives the verification result sent by the cloud; wherein the verification result is the information obtained by the cloud after decrypting the current encrypted user information and verifying it. The verification result is sent to the business system.

2. The method according to claim 1, characterized in that, Before performing a de-identification operation on the current user information to obtain the de-identified user information, and encrypting the de-identified user information according to pre-stored security parameters to obtain the encrypted user information, the method further includes: If a verification result is successfully obtained based on the current user information and the pre-stored user information, then the verification result is sent to the business system. If a verification result cannot be obtained based on the current user information and the pre-stored user information, then the step of "de-identifying the current user information to obtain the current de-identified user information, and encrypting the current de-identified user information according to the pre-stored security parameters to obtain the current encrypted user information" is determined to be executed.

3. The method according to claim 1 or 2, characterized in that, After sending the verification result to the business system, the method further includes: Record and store the peripheral call log of the current peripheral device; wherein the peripheral call log includes at least one of the following: the call record of the current peripheral device, the status data of the current peripheral device, and the verification result; Identify the abnormal logs in the peripheral device call logs and send the abnormal logs to the cloud; wherein, the abnormal logs are used to identify fault information of peripheral devices and / or edge nodes.

4. The method according to claim 1, characterized in that, Before receiving the peripheral call request sent by the business system, the method further includes: Monitor the connection status between the edge node and the cloud; If the connection status is determined to be network interrupted, then the current working status of the edge node is determined to be offline mode; If the connection status is determined to be normal, then the current working status of the edge node is determined to be online mode; After obtaining the current user information collected by the current peripheral device, the method further includes: If the current working state is offline mode, then the verification result is determined based on the current user information and the pre-stored user information, and the verification result is sent to the business system; Store the current peripheral's exception log to the local offline task queue; wherein the current peripheral's exception log includes at least one of the following: the current peripheral's exception call record, the current peripheral's exception status data, and the exception verification result; If the current working state is online mode, then the following steps are determined to be executed: "to perform a de-identification operation on the current user information to obtain the current de-identified user information, and to encrypt the current de-identified user information according to the pre-stored security parameters to obtain the current encrypted user information"; After sending the verification result to the business system, the method further includes: uploading the current peripheral device's abnormal log to the cloud in real time.

5. The method according to claim 4, characterized in that, After storing the current peripheral device's exception log to the local offline task queue, the method further includes: If the connection status is determined to be network restored, then the current working status is determined to be online mode; The data in the local offline task queue is sent to the cloud sequentially in chronological order. Receive confirmation information sent by the cloud; wherein the confirmation information is generated by the cloud after performing fusion verification on the data; When all data in the local offline task queue is sent to the cloud, and the confirmation information indicates that no information is lost during the transmission process, the local offline task queue is cleared.

6. The method according to claim 1 or 2, characterized in that, The method further includes: Receive configuration update notifications sent from the cloud; The updated configuration information is obtained from the cloud; wherein the updated configuration information includes at least one of the following: updated call permission information, updated peripheral interface specifications, and updated security parameters; When it is determined that the updated configuration information is compatible with the peripherals connected to the edge node, a success update result is sent to the cloud. When it is determined that the updated configuration information is incompatible with the peripheral devices connected to the edge node, a configuration error result is sent to the cloud.

7. The method according to claim 1 or 2, characterized in that, The method further includes: Within each statistical period, the summary call data of the peripherals connected to the edge node is determined; The aggregated call data is sent to the cloud.

8. A peripheral device calling system, characterized in that, The system includes: cloud, edge nodes, and peripherals; The edge nodes are connected to the cloud and the peripheral devices, respectively. The edge node is used to execute the peripheral invocation method as described in any one of claims 1 to 7; The cloud is used to receive the current encrypted user information, decrypt the current encrypted user information, verify it, obtain the verification result, and send the verification result to the edge node.

9. The system according to claim 8, characterized in that, Both the cloud and the edge nodes are compatible with the domestic IT innovation platform, and the communication process between the cloud and the edge nodes meets the security requirements of domestic IT innovation.

10. An electronic device, characterized in that, The electronic device includes: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the peripheral invocation method according to any one of claims 1 to 7.

Images