Distributed multi-terminal data co-processing method and device, equipment and medium

Abstract

The invention relates to the technical field of data processing, can be applied to business scenes of financial science and technology, medical health, lease and the like, and discloses a distributed multi-terminal data cooperative processing method, which comprises the following steps: receiving a structured data unit containing business logic generated by an initiating terminal, and transmitting the structured data unit to a business verification server, receiving verification result data returned by the service verification server, and performing security encapsulation processing on the verification result data to generate security encapsulation data; calling a distributed communication service interface of the distributed operating system, and detecting a connectable device set in a network domain where the initiating terminal is located; and establishing a multi-path transmission link based on the transmission capability parameters of the terminal devices in the connectable device set, and distributing the security encapsulation data to the target terminal device group through the multi-path transmission link. According to the invention, efficient distribution and synchronization of data are realized through a multipath transmission link, the dependence on a background system is reduced, the timeliness and consistency of data synchronization are improved, and the maintenance cost of the system is reduced.

Description

Technical Field

[0001] The present invention relates to the technical field of data processing, and in particular, to a distributed multi-terminal data collaborative processing method, apparatus, device, and storage medium. Background Art

[0002] In industries such as leasing, healthcare, and finance, the business processes are complex and involve a large number of approval links. The approval efficiency directly affects the operation of enterprises and the customer experience. With the in-depth development of digitization and mobility, more and more terminal devices have been introduced into the approval process, including smartphones, tablets, PCs, and industry-specific devices (such as healthcare terminals, intelligent counter terminals, etc.). However, due to the variety of terminal devices, there are great challenges in synchronizing and distributing approval messages between different terminals. Traditional solutions usually rely on the background server for scheduling and distributing approval information, but this method is greatly affected by the network environment and server load, resulting in difficulties in ensuring the timeliness, integrity, and consistency of approval messages. There may even be situations such as approval message delays, approval omissions, or duplicate approvals.

[0003] Currently, mainstream approval systems mostly adopt long connection communication mechanisms to keep the terminal devices continuously connected to the background server for real-time synchronization of approval status. Although this method can improve the synchronization ability of approval data to a certain extent, its maintenance cost is high and the development difficulty is large. Especially in the scenario of parallel approval of multiple terminals, the system requires additional architecture design to support message synchronization of multiple devices. In addition, there are differences in the communication capabilities of different types of terminal devices. For example, some smart wearable devices, mobile POS machines, or embedded medical devices are limited by hardware resources and cannot maintain stable long connection communication for a long time, thus restricting the applicability and expansion ability of the approval process in different terminal environments.

[0004] In the business scenario of multi - terminal parallel approval, the traditional background centralized management mode cannot effectively ensure the synchronization efficiency of approval messages and is easily affected by factors such as network fluctuations and server overload. For example, in the lease business scenario, the approval process involves multiple links such as equipment leasing, contract approval, credit review, and payment approval, and usually requires collaborative processing on multiple terminal devices. For example, in the large - scale equipment leasing industry, the lease approval of equipment needs to be reviewed by multiple roles such as business managers, financial personnel, and risk control departments. Each role may use different terminal devices. For example, business managers use mobile terminals for on - site approval, financial personnel approve lease payment information through the PC side, and the risk control department needs to conduct credit assessment and risk judgment in combination with the big data analysis platform. Since the approval process involves multiple business systems, the synchronization of approval information between different terminal devices is crucial. However, the traditional background centralized management mode is easily affected by factors such as network latency and server load, resulting in delays in the approval process and even possible approval omissions, thus affecting the efficiency of equipment leasing and the customer experience. In the financial field, loan approval involves multiple links and multiple terminal devices, such as the PC side of credit review specialists, the mobile approval terminals of risk control personnel, and the internal approval systems of banks. If the approval status cannot be synchronized in a timely manner, it may lead to delays in the loan review process and affect the efficiency of fund disbursement. In the field of medical and health, processes such as medical record approval and drug review involve multiple entities such as doctors, pharmacists, and insurance companies. Inconsistencies in the approval status may lead to delays in drug approval and affect the progress of patient medication or insurance claims. The dependence of existing technologies on the background server makes it difficult to meet the actual requirements for the transmission efficiency and consistency of approval information, especially in scenarios of high - concurrency approval and multi - terminal collaborative approval, where the problems are more prominent. Summary of the Invention

[0005] The main object of the present invention is to provide a distributed multi - terminal data collaborative processing method, device, equipment, and storage medium, aiming to solve the technical problems that existing technologies rely on long - term connections for approval message synchronization, resulting in serious dependence of information interaction between terminal devices on the background system, increasing the system burden, and being unable to efficiently and low - cost realize the synchronization and consistency of approval messages among multiple terminals.

[0006] To achieve the above object, the present invention provides a distributed multi - terminal data collaborative processing method, including:

[0007] Receiving a structured data unit containing business logic generated by an initiating terminal;

[0008] Transmitting the structured data unit to a business verification server;

[0009] Receiving verification result data returned by the business verification server;

[0010] Perform secure encapsulation processing on the verification result data to generate secure encapsulated data;

[0011] Invoke the distributed communication service interface of the distributed operating system, and detect the set of connectable devices within the network domain where the initiating terminal is located through the distributed communication service interface;

[0012] Establish a multi-path transmission link based on the transmission capacity parameters of the terminal devices in the set of connectable devices;

[0013] Distribute the secure encapsulated data to the target terminal device group in the set of connectable devices through the multi-path transmission link.

[0014] Furthermore, to achieve the above object, the present invention provides a distributed multi-terminal data collaborative processing device, including:

[0015] A data processing module, configured to receive a structured data unit containing business logic generated by an initiating terminal;

[0016] A data transmission module, configured to transmit the structured data unit to a service verification server;

[0017] A verification response processing module, configured to receive the verification result data returned by the service verification server;

[0018] A data security encapsulation module, configured to perform secure encapsulation processing on the verification result data to generate secure encapsulated data;

[0019] A device discovery module, configured to invoke the distributed communication service interface of the distributed operating system, and detect the set of connectable devices within the network domain where the initiating terminal is located through the distributed communication service interface;

[0020] A multi-path scheduling module, configured to establish a multi-path transmission link based on the transmission capacity parameters of the terminal devices in the set of connectable devices;

[0021] A data distribution module, configured to distribute the secure encapsulated data to the target terminal device group in the set of connectable devices through the multi-path transmission link.

[0022] Furthermore, to achieve the above object, the present invention also provides a computer device, where the computer device includes a memory, a processor, and a distributed multi-terminal data collaborative processing program stored on the memory and executable on the processor. When the distributed multi-terminal data collaborative processing program is executed by the processor, the steps of the distributed multi-terminal data collaborative processing method as described above are implemented.

[0023] Further, to achieve the above object, the present invention also provides a computer-readable storage medium, on which a distributed multi-terminal data collaborative processing program is stored. When the distributed multi-terminal data collaborative processing program is executed by a processor, the steps of the above-mentioned distributed multi-terminal data collaborative processing method are implemented.

[0024] Beneficial effects: The present invention relates to the technical field of data processing and can be applied to business scenarios such as fintech, healthcare, and leasing. It discloses a distributed multi-terminal data collaborative processing method, including: receiving a structured data unit containing business logic generated by an initiating terminal, and transmitting the structured data unit to a business verification server; receiving the verification result data returned by the business verification server, performing security encapsulation processing on the verification result data to generate secure encapsulated data; invoking the distributed communication service interface of a distributed operating system to detect a set of connectable devices within the network domain where the initiating terminal is located; establishing a multi-path transmission link based on the transmission capacity parameters of the terminal devices in the set of connectable devices, and distributing the secure encapsulated data to the target terminal device group through the multi-path transmission link. By establishing a multi-path transmission link based on the transmission capacity parameters of multi-terminal devices, the present invention realizes the efficient distribution and synchronization of approval data, reduces the dependence of the terminal on the background management system, improves the synchronization timeliness and consistency of approval data among multi-terminal devices, reduces problems such as duplicate approvals and missed approvals, and at the same time reduces the system maintenance cost, and is applicable to application scenarios of multi-terminal collaborative processing. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] The present invention will be further described below in conjunction with the drawings and embodiments. In the drawings:

[0026] Figure 1 is a schematic diagram of an application environment of the distributed multi-terminal data collaborative processing method in an embodiment of the present invention;

[0027] Figure 2 is a schematic flowchart of an embodiment of the distributed multi-terminal data collaborative processing method of the present invention;

[0028] Figure 3 is a schematic diagram of functional modules of a preferred embodiment of the distributed multi-terminal data collaborative processing device of the present invention;

[0029] Figure 4 is a schematic diagram of the structure of a computer device in an embodiment of the present invention;

[0030] Figure 5 is another schematic diagram of the structure of a computer device in an embodiment of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0031] It should be understood that the specific embodiments described herein are only used to explain the present invention and are not used to limit the present invention.

[0032] The distributed multi-terminal data collaborative processing method provided by the embodiments of the present invention can be applied in application environments such as Figure 1 . Among them, the user terminal communicates with the server through the network. The server can receive the structured data unit containing the service logic generated by the initiating terminal through the user terminal, transmit the structured data unit to the service verification server, receive the verification result data returned by the service verification server, perform security encapsulation processing on the verification result data to generate secure encapsulated data; call the distributed communication service interface of the distributed operating system to detect the set of connectable devices within the network domain where the initiating terminal is located; establish a multi-path transmission link based on the transmission capacity parameters of the terminal devices in the set of connectable devices, and distribute the secure encapsulated data to the target terminal device group through the multi-path transmission link. The present invention realizes the efficient distribution and synchronization of approval data by establishing a multi-path transmission link based on the transmission capacity parameters of multi-terminal devices, reduces the dependence of the terminal on the background management system, improves the synchronization timeliness and consistency of approval data among multi-terminal devices, reduces problems such as duplicate approvals and missed approvals, and at the same time reduces the system maintenance cost, and is applicable to application scenarios of multi-terminal collaborative processing. Among them, the user terminal can be, but is not limited to, various personal computers, laptop computers, smart phones, tablet computers, and portable wearable devices. The server can be implemented by an independent server or a server cluster composed of multiple servers. The present invention will be described in detail below through specific embodiments.

[0033] Please refer to Figure 2 , Figure 2 which is a schematic flowchart of an embodiment of the distributed multi-terminal data collaborative processing method provided by the present invention. It should be noted that although the logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than here.

[0034] As Figure 2 shown, the distributed multi-terminal data collaborative processing method proposed by the present invention includes the following steps:

[0035] S10, receiving a structured data unit containing service logic generated by an initiating terminal;

[0036] In this embodiment, the execution entity is the communication center, which is responsible for receiving, distributing, and managing data to achieve data synchronization and coordination among multiple terminals. The communication center is usually a server or edge computing node with high computing power and data processing capabilities, which can be deployed in the cloud, enterprise local server, or edge computing device. The specific choice depends on business requirements and the deployment environment. For example, in an enterprise office system, the communication center can be a private cloud server within the enterprise; in a financial approval system, the communication center may be the data middle platform of a bank; and in a healthcare management system, the communication center can be a medical data transfer server or edge computing device in a hospital.

[0037] The main function of the communication center is to receive data units generated by terminal devices and perform preprocessing, storage, routing, and distribution. Since different terminal devices may use different communication protocols and data formats, the communication center needs to have the ability to convert and standardize data formats to ensure data compatibility between different devices. At the same time, to improve the timeliness of data processing, the communication center usually has distributed computing capabilities, which can process data streams from multiple terminals in parallel and perform intelligent scheduling based on business logic. In addition, the communication center also needs to have security control capabilities, including data encryption, authentication, access rights management, etc., to ensure the security of data in a multi-terminal environment.

[0038] In addition, the communication center can be an independent network service unit or embedded in terminal devices to operate as part of a distributed architecture. The main functions of the communication center include:

[0039] Data management: Receive, store, process, and distribute business data to ensure data integrity and consistency;

[0040] Device discovery: Detect available network devices and dynamically maintain the connection relationship of terminal devices;

[0041] Path optimization: Build an efficient data transmission channel based on the transmission capacity parameters of terminal devices;

[0042] Security encapsulation: Encrypt and sign the transmitted data to ensure the security of the data transmission process;

[0043] Data synchronization: Achieve data synchronization among multiple devices to ensure data consistency and timeliness.

[0044] The deployment method of the communication center can be centralized (deployed on the server side) or distributed (embedded in terminal devices) to adapt to different business requirements and system architectures.

[0045] The communication center receives the structured data unit containing the business logic generated by the initiating terminal and is responsible for data storage, parsing, verification, and subsequent processing. As the core node for data processing, the communication center can uniformly manage the data streams of multiple terminal devices, ensure the consistency of data formats and business logics, while reducing the dependence of terminal devices on the back-end system and improving the data processing efficiency and reliability.

[0046] The initiating terminal is the data generation source, responsible for collecting, processing, and generating structured data units, which can include smartphones, tablets, computers, or other intelligent devices with computing and data processing capabilities. The initiating terminal can perform data collection and conversion according to business requirements and scenarios to make the data conform to the preset format for subsequent processing by the communication center. In multi-terminal data collaborative processing, the initiating terminal and the communication center work together, where the initiating terminal completes the parsing, formatting, and preprocessing of the original data, while the communication center is responsible for unified data management, transmission optimization, and security encapsulation.

[0047] The selection of the initiating terminal is usually closely related to the business scenario. For example, in an enterprise office system, the initiating terminal may be an employee's office computer or mobile device; in a financial approval process, the initiating terminal may be the business processing terminal of bank staff; in a medical health management system, the initiating terminal may be a doctor's workstation or intelligent medical device. In these scenarios, the initiating terminal is not only a data input end but can also perform operations such as data encryption, field filling, and version control in advance to optimize the data processing efficiency in the communication center and reduce redundant data transmission.

[0048] The structured data unit is a data entity generated by the initiating terminal, containing standardized business data, enabling the data to be accurately parsed by different systems during subsequent transmission and processing. To ensure data integrity and consistency, the structured data unit usually adopts a predefined data format, containing multiple fields, such as form data fields, business logic fields, unique identifier fields, timestamps, etc. In practical applications, the structured data unit can adopt data formats such as JSON, XML, Protobuf, etc., making the data suitable for cross-platform transmission and meeting the high-efficiency requirements of data parsing.

[0049] Business logic is an important part of structured data units. It defines the attributes of data, processing rules, and the execution methods in different business processes. During the data generation process, the initiating terminal needs to extract key information from the original business data and perform conversions according to business rules. For example, in an approval system, business logic can stipulate different levels of approval authority, the execution order of the approval process, and automatic approval rules under specific conditions. To ensure data consistency, the initiating terminal matches the original data according to the business type mapping table to make it conform to the preset business logic framework, thereby ensuring that data processing methods are unified under different business scenarios.

[0050] During the process of generating structured data units, the initiating terminal needs to preprocess the data to ensure data accuracy and security. First, the initiating terminal obtains the original data from user input or system interfaces and screens, classifies, and converts key fields according to business logic requirements. For example, in a financial service system, the initiating terminal may need to extract fields such as identity information, credit scores, and loan amounts from the information submitted by applicants and calculate credit ratings according to a preset credit assessment model. In a medical management system, the initiating terminal may need to extract patient information, diagnosis results, prescription data, etc. from medical record data and ensure that they conform to medical data format specifications.

[0051] To improve data security, the initiating terminal needs to encrypt or desensitize sensitive data while generating structured data units. For data involving privacy protection, such as ID numbers, bank card numbers, medical record information, etc., the initiating terminal can use hash algorithms, symmetric encryption, or asymmetric encryption technologies to process the data. For example, in a financial payment system, the initiating terminal can use the AES encryption algorithm to encrypt payment information to ensure that the data is not stolen or tampered with during transmission. In a medical data management system, the initiating terminal can adopt data desensitization technology to partially hide patients' sensitive information to ensure both the availability and security of the data.

[0052] To ensure data traceability and consistency, the initiating terminal attaches data version information and timestamps when generating structured data units. The data version information is used to identify the data format and processing rule versions, ensuring that different versions of data can be parsed compatibly. For example, in a dynamically changing approval rule system, the data version information can help the system identify the data generation environment and rule set to select an appropriate parsing strategy during subsequent processing. The timestamp is used to record the data generation time, ensuring that in a multi-terminal collaborative processing environment, the data can be correctly processed in chronological order to avoid data overwriting or out-of-sync problems.

[0053] By generating a structured data unit containing business logic through the initiating terminal, the dependence of the terminal device on the background system can be reduced, the front-end processing and standardization of data can be realized, and the timeliness and consistency of data can be improved. By adopting a preset business logic mapping rule, the initiating terminal can generate data units that meet the process requirements according to different business scenarios, avoiding the problem of difficult parsing caused by inconsistent data formats. Combining field-level encryption, data version control, and timestamp mechanism ensures the security and traceability of data during the transfer process, effectively reducing the risks of data leakage, tampering, and out-of-sync, providing a basic guarantee for multi-terminal data collaborative processing.

[0054] S20, transmit the structured data unit to the service verification server;

[0055] In this embodiment, the communication center transmits the generated structured data unit to the service verification server to achieve compliance verification of data and business process control. The structured data unit is a data carrier that conforms to a preset format and contains key contents such as business logic fields, approval type identifiers, data version information, and timestamps to ensure correct parsing and execution between different systems. The service verification server is used to receive, parse, and verify the transmitted data unit, and can judge whether the data meets the requirements of the business process according to the preset rules or database records inside. The transmission process can be based on different communication protocols, such as HTTP, WebSocket, MQTT, or a proprietary communication interface based on a distributed operating system, to meet the transmission requirements under different business scenarios.

[0056] During the data transmission process, the structured data unit can be transmitted in a synchronous or asynchronous manner. The synchronous transmission method is suitable for applications with high requirements for real-time performance, such as financial transaction approval or medical emergency data transmission, which can ensure that the data is verified and a response is returned within a short time. The asynchronous transmission method is suitable for scenarios with a large amount of data or where a certain time delay is allowed in the business process, such as lease contract approval or batch data review, and is transmitted through a message queue or middleware to improve the system throughput capacity. To ensure the integrity and security of the data, technical means such as data encryption, signature authentication, and redundancy check can be combined during the transmission process to prevent the data from being tampered with or lost during the transmission.

[0057] The data unit can be transmitted in a secure channel-based manner. For example, data encryption transmission can be carried out through a TLS encrypted tunnel to ensure that data is not illegally stolen in the network. Data can also be stored and certified based on blockchain technology. A data hash value is generated on the business verification server side, and the integrity and immutability of the data are ensured through smart contracts. Additionally, data compression technology can be combined to perform compression encoding on structured data units to reduce network bandwidth occupancy and improve transmission efficiency. Furthermore, in high-concurrency scenarios, load balancing technology can be adopted to distribute data requests to multiple business verification servers, improving the stability and response speed of the system.

[0058] By transmitting the structured data unit to the business verification server, standardized verification of data and business process management are achieved, ensuring the compliance and consistency of data. Multiple security mechanisms are adopted to guarantee the security of data transmission, prevent data from being illegally tampered with or intercepted in the network, and improve the reliability of data transmission. At the same time, different transmission modes and optimization means are adopted to improve the transmission efficiency of data, making the approval process more efficient and intelligent.

[0059] S30, receive the verification result data returned by the business verification server;

[0060] In this embodiment, the communication center receives the verification result data returned by the business verification server to complete the compliance confirmation of data and the advancement of the business process. The verification result data is the result returned by the business verification server after auditing the structured data unit, including the audit status, approval conclusion, business feedback information, and other relevant additional data. This data can be in a structured format, such as JSON, XML, Protocol Buffers, or in a binary encoding format to adapt to different system architectures and transmission requirements.

[0061] When the communication center receives the verification result data returned by the business verification server, it can adopt the active pull or passive reception method. The active pull method is suitable for business scenarios with high real-time requirements, such as financial risk control audits, medical approval authorizations, etc. The communication center will periodically send query requests to the business verification server to obtain the latest verification result data. The passive reception method is suitable for applications with a certain delay in the business process, such as lease approvals, contract signing confirmations, etc. The business verification server actively pushes the verification result data to the communication center after the audit is completed, improving the system response speed and reducing unnecessary network requests.

[0062] During the data reception process, in order to ensure the integrity and security of the data, technical means such as digital signatures, data encryption, and hash verification can be used to prevent the data from being tampered with or illegally intercepted. After the initiating terminal receives the data, it needs to decode, parse the data, and store and process the key information to support subsequent business operations.

[0063] The verification result data can be encrypted and transmitted based on a secure transmission protocol, such as TLS / SSL, to ensure that the data will not be stolen or tampered with during the transmission process. A message queue mechanism, such as Kafka or RabbitMQ, can be adopted to store the verification result data in the queue, allowing the communication center to pull the data when needed, improving the stability and reliability of data interaction. Blockchain technology can also be combined to store the key verification results in the blockchain network to ensure the immutability and traceability of the data, which is applicable to business scenarios with high security requirements such as finance and healthcare.

[0064] Example illustration: In the field of healthcare, the doctor's mobile device can serve as the initiating terminal, and the communication center receives the patient's medical record approval result returned by the business verification server. The verification result data includes information such as the medical record review status, whether it meets the diagnosis and treatment standards, and whether additional review processes are required, ensuring the integrity and compliance of the medical record data and supporting the connection with insurance institutions or pharmacy systems to improve the automation level of the medical process.

[0065] In the financial field, the enterprise's financial management system can serve as the initiating terminal, and the communication center receives the loan approval result returned by the business verification server. The verification result data includes information such as credit rating assessment, loan amount, interest rate calculation, and repayment plan, ensuring the smooth execution of the loan business process and at the same time supporting further analysis and decision-making by the risk control system, improving the efficiency and accuracy of loan approval.

[0066] By receiving the verification result data returned by the business verification server through the communication center, the approval feedback can be obtained in a timely manner to ensure the smooth progress of the business process. The use of encryption transmission and digital signature technology improves the security of data transmission and prevents the data from being illegally tampered with or intercepted during network transmission. It supports multiple data interaction methods, improves the flexibility of the system, adapts to different business scenarios and technical architectures, and enhances the stability of data transmission and the efficiency of business processing.

[0067] S40, perform a secure encapsulation process on the verification result data to generate secure encapsulated data;

[0068] In this embodiment, after the verification result data is received, it needs to be securely encapsulated to ensure that the data is not tampered with, forged, or leaked during transmission and storage. The core objective of secure encapsulation is to protect the integrity, authenticity, and confidentiality of the data, so that the data can remain trustworthy when transmitted between different terminal devices. Securely encapsulated data is a data unit generated after a series of security processes such as encryption, signature, and timestamp encapsulation on the basis of the original verification result data.

[0069] First, to ensure the authenticity of the data, the hardware unique identification code of the device can be extracted from the secure encryption module and bound to the verification result data to identify the source device of the data. The hardware unique identification code can be the serial number of the device, IMEI, MAC address, or other information that can be used to uniquely identify the device.

[0070] Then, the bound verification result data is encrypted using asymmetric encryption technology to generate a digital signature to ensure the integrity of the data and prevent tampering. Asymmetric encryption technology can adopt encryption algorithms such as RSA, ECC (Elliptic Curve Cryptography), etc., where the private key is used for signing and the public key is used for verification. After the data is signed, any unauthorized modification will cause the signature verification to fail, thus ensuring the integrity of the data.

[0071] Next, a secure data extension field is created and the digital signature is embedded in it to support the integrity check and source authentication of the data. The secure data extension field can contain additional authentication information, such as a public key certificate, a hash digest value, or a timestamp, to enhance the security of the data.

[0072] To further enhance the security of the data, a timestamp and a communication protocol version identifier can also be added to record the time when the data is generated and the protocol version. The timestamp can prevent replay attacks on the data, and the protocol version identifier can ensure the compatibility of the data with different system versions.

[0073] Finally, the timestamp, the communication protocol version identifier, and the secure data extension field are encapsulated together to form the final securely encapsulated data, enabling it to be securely transmitted and stored between different terminals.

[0074] A Hardware Security Module (HSM) can be used to generate and store private keys, ensuring that the keys are not leaked and enhancing data security. A hashing algorithm (such as SHA-256) can be used to hash the verification result data, and the hash value is encrypted together with the timestamp and device identification information to ensure data consistency during transmission between different devices. Blockchain forensics can also be used to store the hash value of the securely encapsulated data in the blockchain network to improve the immutability of the data, which is applicable to scenarios with high security requirements such as finance and healthcare. In addition, zero-knowledge proof technology can be combined so that the data recipient can verify the authenticity of the data without exposing the specific content of the data, thereby enhancing the privacy protection ability.

[0075] By performing secure encapsulation processing on the verification result data, it is possible to ensure that the data is not tampered with or forged during transmission and storage, improving the security and credibility of the data. Asymmetric encryption and digital signature technologies are adopted to ensure the traceability of the data source and prevent unauthorized modifications. Combining the timestamp and protocol version identifier enhances the anti-replay ability and cross-system compatibility of the data, enabling the data to remain consistent when transmitted between different devices.

[0076] S50, call the distributed communication service interface of the distributed operating system, and detect the set of connectable devices within the network domain where the initiating terminal is located through the distributed communication service interface;

[0077] In this embodiment, in order to achieve efficient data synchronization among multiple terminal devices, it is necessary to call the distributed communication service interface of the distributed operating system to detect the set of connectable devices within the network domain where the initiating terminal is located. The distributed communication service interface provides an efficient way for device discovery and data communication, enabling terminal devices to automatically sense and establish connections with other terminals, thereby realizing cross-device data sharing and synchronization.

[0078] The communication center sends a device detection request to other devices within the current network domain through the distributed communication service interface, and this request is used to obtain the set of currently available terminal devices. The division of the network domain is usually based on Wi-Fi, Bluetooth, cellular networks, or local area networks. In different network environments, the connection methods of devices are also different. For example, in a Wi-Fi environment, device discovery can be based on the Multicast Protocol, in a Bluetooth environment, discovery can be performed through Bluetooth Low Energy (BLE) scanning, and in a cellular network, device detection can rely on a distributed scheduling algorithm.

[0079] In the implementation of device discovery, different technical means can be adopted based on different distributed operating systems (such as HarmonyOS, Android, Fuchsia, etc.). For example, in HarmonyOS, the Device Discovery API can be used for device discovery and connection; in the Android system, technologies such as Wi-Fi Direct and Bluetooth Low Energy Mesh (BLE Mesh) can be utilized for device detection; in the Fuchsia system, device management can be carried out based on the distributed protocol natively supported by its kernel. Different systems adopt different device discovery methods, but their core goal is the same, that is, to improve the interconnection efficiency between terminal devices and achieve fast data synchronization.

[0080] Device detection requests usually contain filtering conditions to ensure that only devices meeting the requirements are discovered. For example, device detection requests can include the minimum protocol version requirement, signal strength threshold, device type, etc., to prevent devices with low compatibility or poor signal quality from being misidentified as connectable devices. After sending a device detection request, terminal devices within the network domain will respond to the request and return a response message containing their own device identifier, communication capability parameters, and current resource status. The initiating terminal receives and parses these response messages to obtain the basic information of connectable devices.

[0081] During the device detection process, various network technologies can be used for optimization. For example, the Multicast DNS (mDNS) protocol can be used for device discovery. This protocol can dynamically register and discover devices in the local network, improving the real-time performance of device discovery. At the same time, Beacon technology can be combined to enable devices to broadcast their own status periodically, improving the efficiency of device detection. In addition, in the case of high network load, a distributed scheduling mechanism can be adopted to reduce the number of broadcasts and improve the stability of device detection. To enhance the robustness of device discovery, different technical strategies can be selected in different network environments, such as using the broadcast method in the local area network environment and the point-to-point discovery mechanism in the wide area network environment.

[0082] If it is necessary to improve the security of data synchronization, the device detection response data can be encrypted. For example, the Transport Layer Security (TLS) protocol can be used for encrypted transmission to prevent detection data from being stolen or tampered with. In addition, blockchain technology can be combined to assign a unique identity identifier to each device, making the connection of devices more secure and trustworthy and preventing malicious devices from forging identities to participate in network communication.

[0083] In different network environments, different methods can be adopted for device detection. For example, in a local area network environment, device discovery can be based on the UDP broadcast method, while in a cellular network, remote device management can be carried out through a cloud coordination mechanism. In addition, to improve the efficiency of device discovery, machine learning algorithms can be combined to analyze historical device connection data, optimize the detection strategy, making the device discovery faster and more accurate. In some application scenarios, device detection can be combined with a user authentication mechanism to ensure that only authorized terminal devices can join the data synchronization network. For example, in an enterprise internal network, access control policies can be set to ensure that only devices that have passed identity authentication can join the data synchronization network, while in an open network environment, a dynamic key exchange mechanism can be combined to ensure the security of communication between devices.

[0084] By calling the distributed communication service interface of the distributed operating system and automatically detecting the set of connectable devices within the network domain where the initiating terminal is located, the automatic interconnection between terminal devices is achieved, avoiding the problem in traditional methods where terminal devices rely on a background server for device management, and improving the efficiency and reliability of data synchronization. At the same time, by setting screening conditions, the device discovery process can be made more accurate, reducing invalid connections and enhancing the stability of data transmission. Combining various optimization techniques, such as beacon broadcasting and dynamic scheduling, during the device discovery process makes the success rate of device discovery higher and the connection more stable.

[0085] S60, establish a multi-path transmission link based on the transmission capacity parameters of the terminal devices in the set of connectable devices;

[0086] In this embodiment, to improve the data transmission efficiency and reliability between terminal devices, it is necessary to establish a multi-path transmission link based on the transmission capacity parameters of the terminal devices in the set of connectable devices. The establishment of a multi-path transmission link can effectively utilize the transmission capabilities of different devices, achieve parallel transmission of data on multiple transmission paths, improve the overall stability of data synchronization, reduce transmission latency, and provide a fast switching mechanism when a certain path fails to ensure the continuity of data transmission.

[0087] The communication center first filters out the terminal devices that meet the main path transmission conditions based on the transmission capacity parameters of the terminal devices in the set of connectable devices. The transmission capacity parameters generally include but are not limited to the device's network bandwidth, signal strength, data throughput capacity, latency situation, network protocol compatibility, etc. The main path transmission conditions require that the transmission capacity parameters of the terminal devices reach the first screening threshold, that is, they need to meet the characteristics of high bandwidth, low latency, and high stability. The devices that meet these conditions will be added to the main path node set and jointly form the main path transmission link. The establishment of the main path transmission link can ensure that data is preferentially transmitted through high-performance devices, reducing data loss and transmission latency.

[0088] After determining the set of main path nodes, it is necessary to exclude the terminal devices that have already been added to the set of main path nodes from the set of connectable devices and screen the terminal devices that meet the secondary path transmission conditions. The secondary path transmission conditions require that the transmission capacity parameter of the terminal device reaches a second screening threshold, which is lower than the main path transmission conditions and is applicable to devices with a smaller bandwidth but still capable of stably transmitting data. The eligible devices will be added to the set of secondary path nodes and jointly form a secondary path transmission link. The role of the secondary path transmission link is to provide an alternative transmission path. When congestion or failure occurs in the main path, it can undertake part or all of the data transmission tasks to ensure the stability and continuity of data synchronization.

[0089] To achieve the orderly transmission of data between different paths, it is necessary to assign a main path transmission channel identifier to each terminal device in the set of main path nodes. This identifier is used to mark the role and data flow direction of the device in the main path transmission link. Similarly, it is necessary to assign a secondary path transmission channel identifier to each terminal device in the set of secondary path nodes to distinguish the data streams of different paths during data transmission. The transmission channel identifiers of the main path and the secondary path can be managed based on the unique identifier of the device, the transmission priority, or a dynamically generated session identifier to ensure the orderly nature of data transmission and the flexibility of path allocation.

[0090] To optimize the dynamic allocation of data between multiple paths, it is necessary to deploy a multi-path state coordination connection between the main path transmission link and the secondary path transmission link. This connection is used to monitor the status of each transmission path in real time and dynamically adjust the data allocation ratio according to the transmission performance. The multi-path state coordination connection can obtain the current available state data of the main path and the secondary path based on the method of periodically transmitting control signals or feedback data, such as network latency, data loss rate, bandwidth occupancy rate, etc. Based on this data, the data transmission ratio between the main path transmission link and the secondary path transmission link can be dynamically adjusted. For example, when the bandwidth of the main path is sufficient, data is preferentially allocated to the main path, and when congestion occurs in the main path, the load of the secondary path is increased, thereby improving the overall efficiency and reliability of data transmission.

[0091] By establishing a multi-path transmission link based on the transmission capacity parameters of the terminal devices in the set of connectable devices, multi-channel transmission of data is achieved, improving the stability and transmission efficiency of data synchronization. Through the division of the main path and the secondary path, high-performance devices can be preferentially utilized for data transmission, and when congestion or failure occurs in the main path, a quick switch to the secondary path can be made to ensure the continuity of data transmission. The introduction of the multi-path state coordination connection makes the allocation of data between different paths more intelligent, capable of dynamically adjusting according to the real-time network state, improving the overall transmission performance, and reducing data loss and transmission latency.

[0092] S70 distributes the secure encapsulated data to the target terminal device group in the set of connectable devices through the multi-path transmission link.

[0093] In this embodiment, the communication center distributes the secure encapsulated data to the target terminal device group in the set of connectable devices through the multi-path transmission link, which can achieve efficient data distribution, improve the timeliness of data synchronization, reduce transmission latency, and ensure the consistency of data on multiple terminal devices. To ensure the accuracy and stability of data transmission, it is necessary to perform refined management on the screening of the target terminal device group, the fragmentation and routing mapping of data, the allocation of paths, and the reception and recombination of data.

[0094] First, it is necessary to screen the terminal devices that meet the target transmission conditions from the set of connectable devices to generate the target terminal device group. The screening criteria include but are not limited to the transmission capacity parameters of the terminal devices, network status, task priorities, and the current load conditions of the devices. The target transmission conditions require that the transmission capacity parameters of the terminal devices reach a preset distribution threshold to ensure that they can stably receive data and interact efficiently with other terminal devices. The establishment of the target terminal device group can adopt a dynamic adjustment mechanism. For example, when the device status changes, the selection strategy of the target terminal devices can be adjusted in real time to improve the adaptability of data distribution.

[0095] To optimize the data transmission efficiency, the communication center needs to fragment the secure encapsulated data. The communication center divides the secure encapsulated data into multiple data fragments and attaches a fragment sequence identifier to each data fragment, so that the target terminal devices can recombine the data in the correct order after receiving it. The size of the data fragments can be dynamically adjusted according to the current network conditions to adapt to different transmission bandwidths and device processing capabilities, improving the stability and throughput of data transmission.

[0096] Next, it is necessary to generate a fragmentation routing mapping table based on the transmission channel identification information in the multi-path transmission link. This mapping table records the binding relationship between each data fragment and the transmission channel to ensure that the data can be transmitted along the predetermined path. The main path transmission channel is usually preferred to carry critical data, and the secondary path transmission channels are used for load balancing and data redundancy. When the load of the main path is too high or an abnormality occurs, the fragmentation routing mapping table can be adjusted to dynamically allocate more data to the secondary path to ensure the stability of data transmission.

[0097] During the data transmission phase, the communication center sends the first data shard group containing the main path transmission channel identifier through the main path transmission channel. The main path transmission channel usually has higher bandwidth and lower latency, and is suitable for data transmission with high real-time requirements. At the same time, the communication center sends the second data shard group containing the secondary path transmission channel identifier through the secondary path transmission channel. The transmission capacity of the secondary path transmission channel is relatively low, and it is mainly used to carry secondary data or provide redundant transmission when the main path fails.

[0098] After the devices in the target terminal device group receive the first data shard group and the second data shard group, they need to perform sequential recombination of the received data shards according to the shard sequence identifier to restore the complete securely encapsulated data. During the data recombination process, packet loss detection and error correction techniques can be adopted, such as based on the forward error correction (FEC) mechanism, where redundant information is appended during data transmission so that the data can still be correctly restored in the case of partial data loss. In addition, in order to ensure the integrity and consistency of the data, it is necessary to perform shard integrity and sequential continuity verification on the recombined securely encapsulated data. After the verification passes, the terminal devices in the target terminal device group write the securely encapsulated data into their respective data storage areas to ensure the consistency of the data on multiple terminal devices.

[0099] Under different network environments and service requirements, the data distribution method can be optimized. For example, in scenarios with high low-latency requirements, a bandwidth-aware path scheduling strategy can be adopted to make the data preferentially distributed through the channel with the optimal transmission capacity. In scenarios of multi-device collaboration, a collaborative data distribution mechanism can be adopted to enable the target terminal devices to share the data they have received, reduce duplicate transmissions, and improve the overall transmission efficiency. In addition, in an environment with large network fluctuations, machine learning algorithms can be combined to predict the path quality and dynamically adjust the data allocation ratio between the main path and the secondary path to improve the adaptability of data transmission.

[0100] Data distribution through the multi-path transmission link can improve the synchronization efficiency of data among multiple terminal devices, reduce data transmission latency, and reduce data loss and duplicate transmission problems among devices. The combination of the main path and the secondary path makes the data transmission have higher fault tolerance. Even if a certain path fails, the data distribution continuity can be maintained through the secondary path. Based on the sharding and routing mapping mechanism, it ensures the orderliness of data transmission, improves the data recovery efficiency at the data receiving end, and reduces the risk of data synchronization errors caused by network fluctuations.

[0101] The present invention relates to the technical field of data processing and can be applied to business scenarios such as fintech, healthcare, and leasing. It discloses a distributed multi-terminal data collaborative processing method, which includes: receiving a structured data unit containing business logic generated by an initiating terminal, transmitting the structured data unit to a business verification server, receiving the verification result data returned by the business verification server, performing security encapsulation processing on the verification result data to generate secure encapsulated data; invoking the distributed communication service interface of the distributed operating system to detect a set of connectable devices within the network domain where the initiating terminal is located; establishing a multi-path transmission link based on the transmission capacity parameters of the terminal devices in the set of connectable devices, and distributing the secure encapsulated data to the target terminal device group through the multi-path transmission link. By establishing a multi-path transmission link based on the transmission capacity parameters of multi-terminal devices, the present invention realizes the efficient distribution and synchronization of approval data, reduces the dependence of the terminal on the background management system, improves the synchronization timeliness and consistency of approval data among multi-terminal devices, reduces problems such as duplicate approvals and missed approvals, and at the same time reduces the system maintenance cost, and is applicable to application scenarios of multi-terminal collaborative processing.

[0102] In one embodiment, the above S10 includes:

[0103] S101, parsing the original business data through the initiating terminal and extracting the form field content in the original business data;

[0104] S102, through the initiating terminal, matching the form field content with the corresponding business logic policy according to a preset business type mapping table to generate a business logic binding field;

[0105] S103, inserting a business type identification field into the business logic binding field through the initiating terminal;

[0106] S104, performing field-level encryption on the sensitive data fields in the business logic binding field through the initiating terminal to generate an encrypted field data block;

[0107] S105, combining the encrypted field data block with the unencrypted fields in the business logic binding field through the initiating terminal, and adding a data version identifier and a serialization timestamp to generate the structured data unit;

[0108] S106, receiving the structured data unit sent by the initiating terminal.

[0109] In this embodiment, the initiating terminal generates a structured data unit containing business logic. Through the parsing of the original business data, field matching, data encryption, and timestamp marking, the standardization and security of the data are achieved, ensuring the consistency and traceability of the data in the distributed system. The initiating terminal can be an intelligent device that executes an approval process, such as a mobile phone, a tablet computer, a PC, or an embedded device. These devices have the ability to process business data and can interact with the distributed data synchronization system.

[0110] First, the initiating terminal needs to parse the original business data and extract the form field content from it. The original business data may come from user input, task push from the background system, or synchronization information from other terminal devices. The form field content includes, but is not limited to, data such as user identity information, approval request content, and timestamp. The parsing process can combine the business data format, such as JSON, XML, or database records, and use methods such as regular expression matching and key-value pair mapping to extract the key fields to ensure the accuracy and integrity of the data.

[0111] After completing the data parsing, the initiating terminal needs to match the form field content with the corresponding business logic strategy according to the business type mapping table to generate a business logic binding field. The business type mapping table is a predefined set of rules that contains the field mapping rules for various approval processes. For example, in the financial approval business, credit approval needs to match the customer's credit score field, while in the medical and health data review scenario, medical record approval needs to match the patient's diagnosis information field. By matching the business logic strategy, it can ensure the uniformity of data processing rules for different approval processes and avoid data parsing errors caused by business type differences.

[0112] Next, the initiating terminal inserts a business type identification field into the business logic binding field to clarify the approval type to which the data belongs. The business type identification field usually contains the approval type code and the process node number. For example, in the enterprise financial approval system, the approval type code may include "expense reimbursement", "purchase approval", etc., and the process node number is used to identify the current approval stage, such as "preliminary review", "recheck", "final approval", etc. By introducing the business type identification field, the recognition degree of the data in the distributed system can be improved, making the subsequent data processing more accurate.

[0113] To ensure data security, the initiating terminal needs to perform field-level encryption on the sensitive data fields in the business logic binding fields to generate encrypted field data blocks. Sensitive data fields include user identity information, transaction amounts, medical records, etc. Adopting field-level encryption can protect critical data while maintaining the integrity of the data structure. The encryption method can use AES (Advanced Encryption Standard), SM4 (GuoMi algorithm), or other encryption technologies suitable for distributed data synchronization. The implementation of field-level encryption can be carried out during database storage and data transmission to prevent data from being tampered with or leaked during transmission.

[0114] After the data encryption is completed, it is necessary to combine the encrypted field data blocks with the unencrypted fields in the business logic binding fields, and add a data version identifier and a serialized timestamp to generate a structured data unit. The data version identifier is used to identify the iteration of the data format to maintain compatibility during system upgrades, while the serialized timestamp records the generation time of the data to ensure the correct parsing of the data's temporal relationship in a distributed environment. When combining the data, various formats can be used for storage, such as JSON structured data, Protobuf binary format, or custom data encapsulation formats, to meet different storage and transmission requirements.

[0115] After the data unit is generated, the initiating terminal sends it to the communication center. The communication center, as a data transfer and distribution node, receives the structured data unit sent by the initiating terminal and is responsible for subsequent verification, storage, and transmission. The deployment method of the communication center can be flexibly configured according to specific business requirements and system architecture. It can be an independent server node, assuming the role of centralized data processing, or a software component in a distributed operating system environment, embedded in the terminal device to complete data processing and synchronization locally on the device, reducing dependence on external servers. In a distributed system architecture, some terminal devices can run lightweight communication center modules to enable them to have message queue management, data flow control, and device-to-device synchronization capabilities, while other terminal devices still interact with data through independent communication center nodes.

[0116] In practical applications, the deployment form of the communication center can be adjusted according to the computing power and network environment of the terminal device. For example, in a cloud computing environment, the communication center can run as a cloud server, providing high-performance data transfer and processing capabilities to support large-scale concurrent data flow. In an edge computing environment, the communication center can be deployed on edge computing nodes or intelligent gateway devices to reduce data transmission latency and improve data processing efficiency. In addition, on resource-constrained embedded devices, the communication center can run as a lightweight module to enable the terminal device to have data synchronization and local caching capabilities, realizing local data processing and collaborative computing.

[0117] With this architecture, the communication center can flexibly adapt to different business scenarios. It can either manage the global data flow as an independent server node or run in some terminal devices to achieve local data transfer, improving the reliability and scalability of the system.

[0118] In this embodiment, through the parsing, field matching, data encryption, and timestamp marking of the original business data, it is possible to improve the security and traceability of the data in a distributed environment while ensuring data consistency. Using a business type mapping table for field matching enables approval data of different business types to be processed according to unified rules, improving the standardization degree of the data. The field-level encryption mechanism ensures the security of sensitive data, effectively preventing data leakage even when the data is transmitted between multiple terminals. In addition, the introduction of data version identifiers and timestamps enables the data to maintain stable compatibility during system upgrades or device synchronization.

[0119] In one embodiment, the above S30 includes:

[0120] S301, receiving the encrypted data packet sent by the service verification server through a preset response port;

[0121] S302, decrypting the encrypted data packet with a preset session key to obtain the original verification result data generated by the service verification server;

[0122] S303, verifying the digital signature in the original verification result data to generate the original verification result data with verified passing;

[0123] S304, parsing the original verification result data with verified passing and extracting the approval status identifier and associated business identifier in the original verification result data with verified passing;

[0124] S305, performing format standardization processing on the approval status identifier and the associated business identifier to generate standardized verification result data.

[0125] In this embodiment, the communication center receives the verification result data returned by the service verification server to ensure the security and consistency of business data while ensuring the efficient operation of the approval process. In a distributed system, the service verification server is responsible for verifying the authenticity and integrity of the data, and the communication center needs to obtain the verification result from the server to determine the subsequent data processing flow. To ensure the secure transmission and anti-tampering of the data, an encryption mechanism is adopted during the data transmission, and the integrity of the data is ensured through digital signature technology.

[0126] The communication center receives the encrypted data packet sent by the service verification server through a preset response port. The response port is the network port specified by the terminal device during the interaction with the server, and this port needs to be negotiated and determined when the initiating terminal establishes communication with the server. The encrypted data packet is the service data encrypted and protected during the data transmission process to prevent man-in-the-middle attacks or malicious tampering. The encryption method can be based on the Transport Layer Security (TLS) protocol or adopt the End-to-End Encryption (E2EE) technology to ensure that the data is not stolen or tampered with during the transmission process.

[0127] After receiving the encrypted data packet, the communication center decrypts it through a preset session key to obtain the original verification result data generated by the service verification server. The session key is a symmetric key negotiated by both communication parties and is usually securely exchanged through an asymmetric encryption mechanism (such as RSA or ECC) to ensure that the key is not leaked. During the decryption process, the communication center can adopt algorithms such as AES (Advanced Encryption Standard), SM4 (National Cryptography Algorithm), etc. to convert the encrypted data into the original verification result data. After successful decryption, the terminal obtains the unmodified service data, which contains key information such as the approval result and service status.

[0128] To further ensure the authenticity of the data, the communication center needs to verify the digital signature in the original verification result data to ensure the reliability of the data source. The digital signature is an encrypted digest generated by the service verification server using the private key, which is used to ensure that the data has not been tampered with and provides source authentication. The communication center uses the public key of the server to verify the digital signature. If the verification is successful, it indicates that the data has not been tampered with during the transmission process. The digital signature algorithm can adopt methods such as RSA signature, ECDSA (Elliptic Curve Digital Signature Algorithm), etc. to ensure the integrity and non-repudiation of the data.

[0129] After the verification is passed, the communication center parses the original verification result data and extracts the approval status flag and the associated service identifier. The approval status flag is used to indicate the processing status of the current approval, such as "pending approval", "approved", "rejected", etc., while the associated service identifier is used to associate the specific business process, such as a certain order number, contract number, etc. The data parsing can be based on structured formats such as JSON, XML, etc., or a custom binary format can be used for efficient storage and parsing.

[0130] Finally, the communication center standardizes the format of the approval status identifier and the associated service identifier to ensure that the data can be consistent across different systems. Format standardization includes operations such as field format conversion, data type adjustment, and encoding rule unification. For example, converting the approval status from string format to a standard encoding format (e.g., 0 represents pending approval, 1 represents approved, etc.), or adjusting the date format to the ISO 8601 standard. After standardization processing, standardized verification result data is generated, which can be used for subsequent data storage, analysis, and distributed synchronization.

[0131] In this embodiment, by adopting the end-to-end encryption and digital signature mechanism, the security and integrity of the data during transmission are ensured. The decryption method based on the session key improves the data privacy protection ability, and at the same time, the standardization processing enhances the compatibility of the data between different systems. The parsing and conversion of the approval status and service identifier enable the data to be efficiently transmitted and stored, and can adapt to different business requirements, thus improving the accuracy of data synchronization and the automation level of the approval process.

[0132] In one embodiment, the above S40 includes:

[0133] S401, extracting the hardware unique identification code of the initiating terminal from the security encryption module, and binding the hardware unique identification code with the verification result data to generate the bound verification result data;

[0134] S402, processing the bound verification result data through the asymmetric encryption module to generate a secure encapsulated digital signature;

[0135] S403, creating a secure data extension field, embedding the secure encapsulated digital signature into the secure data extension field to generate verification result data containing the secure data extension field;

[0136] S404, obtaining the current time and generating a timestamp, encapsulating the timestamp and a preset communication protocol version identifier to generate a secure data packet header;

[0137] S405, combining the secure data packet header with the verification result data containing the secure data extension field to generate the secure encapsulated data.

[0138] In this embodiment, the communication center performs secure encapsulation on the verification result data to ensure that the data is not tampered with or forged during transmission and to ensure that the source of the data is traceable. By binding the hardware unique identification code, using asymmetric encryption for digital signature, constructing a secure data extension field, and generating a timestamp and a communication protocol identifier, the data has the integrity verification ability during transmission and the compatibility between different devices and systems is improved.

[0139] The communication center extracts the hardware unique identifier of the initiating terminal device from the secure encryption module. The secure encryption module is an important component for device authentication, data encryption, identity verification, and secure communication, ensuring the integrity, confidentiality, and immutability of the data transmission process. In a distributed data collaboration system, the main role of the secure encryption module is to provide device identity management, key generation and storage, encryption and decryption operations, and support for remote authentication to prevent illegal devices from tampering with or forging data. This module can exist in the form of an independent hardware security chip (such as Trusted Execution Environment TEE, Trusted Platform Module TPM, Secure Element SE) or a software encryption module (such as the built-in encryption API of the system, password service module), and interact securely with the communication center and the initiating terminal to ensure the unified execution of data security policies.

[0140] In the specific implementation of the secure encryption module, a hardware-based encryption mechanism is usually adopted, such as TEE (Trusted Execution Environment) or HSM (Hardware Security Module), to provide a high level of key protection capabilities. For example, TEE provides a secure operating environment independent of the operating system, can store keys, execute encryption operations, and provide a device unique identifier (Hardware Unique Identifier, HWID) to verify the legitimacy of the device. Similarly, TPM (Trusted Platform Module) provides hardware-level security functions through a dedicated chip, supports identity authentication, key management, and encryption calculations, and is suitable for enterprise-level security authentication and device identity binding.

[0141] In addition to hardware-level encryption, the secure encryption module can also be based on software encryption mechanisms, such as the encryption services provided by the operating system (Android Keystore, Apple Secure Enclave, Windows BitLocker). These modules can use system-level encryption functions to encrypt device identities and data packets, and provide security operations based on asymmetric encryption (RSA, ECC, SM2), symmetric encryption (AES, SM4), hash algorithms (SHA-256, SM3), etc., to ensure data integrity and anti-tampering. For example, in the distributed security architecture of HarmonyOS, the built-in encryption module of the system can provide functions such as device authentication, identity verification, and data encryption to ensure the security of data transmission between terminal devices.

[0142] In the distributed data collaboration scenario, when the communication center receives data sent by the initiating terminal, it needs to extract the hardware unique identification code of the initiating terminal from the security encryption module for device authentication and data binding. The hardware unique identification code can be the device's IMEI (International Mobile Equipment Identity), MAC address, CPU serial number, or the device fingerprint generated by the security encryption module. The communication center can use this identification code to authenticate the device identity, ensure the authenticity of the data source, and prevent unauthorized terminals from forging data or conducting man-in-the-middle attacks. After extracting the hardware unique identification code, the communication center can use asymmetric encryption (such as RSA, SM2) to sign the data and authenticate with the service verification server to ensure the security of the device and the reliability of data transmission.

[0143] In addition, the security encryption module can also be used to store and manage keys to support encrypted data transmission and digital signature verification. The communication center can use this module to generate a temporary session key to encrypt the service data and adopt end-to-end encryption (E2EE) technology during data transmission to ensure that the data is not leaked or tampered with during network transmission. At the same time, the security encryption module supports the Remote Attestation protocol, which can verify the security status of the device when the device accesses the system and provide a trusted computing environment to prevent malware attacks or device identity forgery.

[0144] Bind the hardware unique identification code to the verification result data to generate the bound verification result data. The hardware unique identification code refers to the unique identifier of the device, such as the unique ID provided by the device's security chip (TPM, SE), IMEI, MAC address, or the device fingerprint information generated based on the trusted computing module. By binding the device identifier and the verification result data, it can be ensured that the data is only used by specific devices, preventing the data from being tampered with or received by illegal devices.

[0145] The communication center processes the bound verification result data through the asymmetric encryption module to generate a secure encapsulated digital signature. The asymmetric encryption module includes RSA, ECC (Elliptic Curve Cryptography), SM2 (National Cryptography Asymmetric Encryption Algorithm), etc. The communication center calculates the hash value of the bound data using the private key and signs the hash value to generate a digital signature. This signature guarantees the integrity of the data and the credibility of the source, and the receiving end can use the public key for verification to ensure that the data has not been tampered with.

[0146] The communication center creates a secure data extension field and embeds the secure encapsulated digital signature into it to generate the verification result data containing the secure data extension field. The secure data extension field is used to store additional security information, such as digital signature, device fingerprint, encryption algorithm version, etc., to ensure that the data has self-describing capabilities and can be applicable to different terminal devices and business scenarios.

[0147] The communication center obtains the current time and generates a timestamp, encapsulates the timestamp and a preset communication protocol version identifier, and generates a secure data packet header. The timestamp is used to prevent replay attacks and ensure the validity of data. The communication protocol version identifier is used to indicate the security protocol adopted by the data packet, such as TLS1.3, SSL, DTLS, or specific industry standards, such as the medical data transmission protocol HL7, the ISO 20022 standard in the financial industry, etc.

[0148] The communication center combines the secure data packet header with the verification result data containing the secure data extension field to generate secure encapsulated data. The final format of the secure encapsulated data can be JSON, XML, or a binary format (such as Protobuf, CBOR) for efficient storage and transmission.

[0149] In this embodiment, by securely encapsulating the verification result data, the tamper-proof ability and credibility of the data are improved. Through the binding of the hardware unique identification code, a strong binding relationship between the data and the device is achieved, preventing illegal devices from forging data. Through asymmetric encryption to generate a digital signature, the authenticity of the data source is ensured and non-repudiation is provided. By constructing a secure data extension field, the data can carry its own security attributes, improving the compatibility of the data between different systems. Through the timestamp and protocol identifier, the validity of the data during transmission is ensured, preventing replay attacks and protocol mismatch problems, thereby improving the security and reliability of data transmission.

[0150] In one embodiment, the above S50 includes:

[0151] S501, invoking the device discovery interface of the distributed operating system to broadcast a device detection request to the network domain where the initiating terminal is located, the device detection request including a preset minimum protocol version and a preset signal strength threshold;

[0152] S502, receiving response messages returned by each terminal device in the network domain through the distributed operating system bus;

[0153] S503, parsing the response messages to extract the device identifiers, protocol versions, and signal strength parameters of each terminal device;

[0154] S504, screening out candidate terminal devices that meet the protocol compatibility condition and whose signal strength meets the signal strength condition from each terminal device in the network domain according to the preset minimum protocol version and the preset signal strength threshold, and generating a preliminary candidate terminal device set;

[0155] S505, generating a final set of connectable devices based on the resource load parameters of each terminal device in the preliminary candidate terminal device set.

[0156] In this embodiment, the communication center performs device discovery operations using the distributed communication service interface of the distributed operating system to determine the set of devices available for communication within the network domain. The distributed operating system can include HarmonyOS, Android Fuchsia, etc., which support cross-device distributed communication, enabling terminal devices to sense other devices in the same network environment and establish data transmission channels.

[0157] The communication center calls the device discovery interface of the distributed operating system to broadcast device detection requests within the network domain. The device discovery interface is used to actively send detection requests to determine the available devices in the current network. The detection request usually includes the minimum protocol version and signal strength threshold to ensure that the detected devices have basic communication capabilities and stable connection quality. The device detection request can be sent based on technologies such as UDP broadcast, mDNS (Multicast DNS), Wi-Fi Direct, BLE Mesh, etc., to adapt to different network environments. For example, in a Wi-Fi environment, the Wi-Fi detection protocol can be used; in a Bluetooth environment, BLE broadcast can be used for device discovery; in a cellular network environment, signaling broadcast of the mobile communication operator can be used for device screening.

[0158] The communication center receives the response messages returned by each terminal device through the distributed operating system bus. The bus is a mechanism for communication between devices. For example, in HarmonyOS, the Distributed Virtual Bus (D-Bus) can be used for message passing, and each device communicates through the distributed bus. The response message usually contains information such as device identifier, protocol version, and signal strength. The initiating terminal parses this information to obtain the basic information of the device.

[0159] The communication center parses the response message to extract the device identifier, protocol version, and signal strength parameters of each terminal device. The device identifier can be used to uniquely identify the device, such as the MAC address of the device, UUID (Universally Unique Identifier), or other device-specific identification codes. The protocol version indicates the communication protocol version supported by the device, such as the supported TCP / IP version, Bluetooth protocol version, Wi-Fi Direct version, etc. The signal strength parameter is used to measure the connection quality between the device and the initiating terminal, such as RSSI (Received Signal Strength Indicator) or SNR (Signal-to-Noise Ratio).

[0160] According to the preset minimum protocol version and signal strength threshold, candidate terminal devices that meet the protocol compatibility conditions and whose signal strength meets the minimum requirements are screened from each terminal device within the network domain, generating a preliminary candidate terminal device set. This step ensures that the selected devices meet the minimum communication standards and avoids unstable devices from affecting the data transmission quality. The protocol compatibility conditions may include supported encryption algorithms, data transmission rates, network topologies, etc., to ensure the smooth progress of subsequent data transmission.

[0161] Based on the resource load parameters of each terminal device in the preliminary candidate terminal device set, the communication center generates a final set of connectable devices. The resource load parameters include the CPU utilization rate of the device, memory occupancy rate, available network bandwidth, battery power, etc., to ensure that the selected devices not only meet the basic communication requirements but also have sufficient computing and storage capabilities to participate in the data synchronization process. In practical applications, a distributed scheduling algorithm can be adopted to dynamically adjust the joining or exiting of devices and optimize the efficiency of data synchronization.

[0162] In this embodiment, by using the distributed communication service interface of the distributed operating system for device discovery, the flexibility of device connection is improved, and the limitations of the traditional centralized device management mode are avoided. By setting the minimum protocol version and signal strength threshold, the stability and reliability of the connected devices are ensured, and weak signal devices or low compatibility devices are prevented from affecting the data transmission quality. By optimizing the set of connectable devices in combination with the resource load parameters, the efficiency of data synchronization between devices is improved, and resource-constrained devices are prevented from affecting the overall transmission performance. In addition, by adopting a dynamic device discovery and screening strategy, the system can adapt to different network environments, improving the adaptability and scalability of device connection.

[0163] In one embodiment, the above S60 includes:

[0164] S601, according to the transmission ability parameters of the terminal devices in the connectable device set, screen the terminal devices that meet the main path transmission conditions, and the main path transmission conditions require that the transmission ability parameters of the terminal devices reach the first screening threshold;

[0165] S602, add the terminal devices that meet the main path transmission conditions to the main path node set, and the terminal devices in the main path node set form a main path transmission link;

[0166] S603, exclude the terminal devices included in the main path node set from the connectable device set, and screen the terminal devices that meet the secondary path transmission conditions. The secondary path transmission conditions require that the transmission ability parameters of the terminal devices reach the second screening threshold and the second screening threshold is lower than the first screening threshold;

[0167] S604. Add the terminal devices that meet the secondary path transmission conditions to the secondary path node set, and the terminal devices in the secondary path node set form a secondary path transmission link;

[0168] S605. Assign a primary path transmission channel identifier to each terminal device in the primary path node set, and the primary path transmission channel identifier corresponds to the logical transmission channel of the primary path transmission link;

[0169] S606. Assign a secondary path transmission channel identifier to each terminal device in the secondary path node set, and the secondary path transmission channel identifier corresponds to the logical transmission channel of the secondary path transmission link;

[0170] S607. Deploy a multi-path state coordination connection between the primary path transmission link and the secondary path transmission link;

[0171] S608. Obtain the current available state data of the primary path transmission channel and the secondary path transmission channel through the multi-path state coordination connection;

[0172] S609. Adjust the data transmission ratio between the primary path transmission link and the secondary path transmission link according to the current available state data of the primary path transmission channel and the secondary path transmission channel.

[0173] In this embodiment, the transmission capacity parameters of the terminal device include but are not limited to bandwidth capacity, network latency, data throughput rate, connection stability, device load conditions, etc. These parameters determine whether the terminal device is suitable as a node of the data transmission path. The transmission capacity parameters can be obtained through real-time measurement or historical statistical data, such as measuring the actual network rate of the device and evaluating the data packet loss rate, etc.

[0174] When establishing a multi-path transmission link, it is first necessary to screen the terminal devices that meet the primary path transmission conditions. The primary path transmission conditions usually require that the transmission capacity parameters of the terminal device meet a higher performance threshold, that is, the first screening threshold. For example, the bandwidth must reach a certain rate, the latency must be lower than the set time limit, and the load level of the device must not exceed a specific upper limit. The devices that meet these conditions are considered suitable for undertaking the primary path transmission task, ensuring high reliability and low latency of data transmission.

[0175] The terminal devices that meet the primary path transmission conditions will be added to the primary path node set, and these devices will form the primary path transmission link. The role of the primary path transmission link is to undertake the main data transmission task, ensuring that data can be transmitted efficiently and stably between terminal devices. The primary path is usually used for low-latency and high-priority data synchronization, such as real-time voice communication, financial transaction data synchronization, etc.

[0176] After the main path device is determined, it is necessary to exclude the devices that have been incorporated into the main path from the set of connectable devices and screen the devices that meet the conditions for secondary path transmission. The requirements for secondary path transmission are lower than those for the main path, and it is applicable to devices in a complex network environment with limited bandwidth but still available as an alternative path. The screening for secondary path transmission conditions is based on a second screening threshold, which is lower than the first screening threshold, so that some devices with slightly lower performance than the main path but still usable are selected.

[0177] The terminal devices that meet the conditions for secondary path transmission are added to the secondary path node set to form a secondary path transmission link. The secondary path transmission link is usually used for redundant backup and data traffic sharing. When congestion or failure occurs in the main path, it can be switched to the secondary path for data transmission, improving the robustness of the system and the continuity of data transmission.

[0178] To manage the transmission of data in different paths, each main path node is assigned a main path transmission channel identifier, which is used to uniquely determine the data transmission channel in the main path, enabling data packets to be transmitted in the main path according to the set routing rules. Similarly, the secondary path nodes are also assigned a secondary path transmission channel identifier to ensure that data can be correctly routed to the target device in the secondary path.

[0179] A multi-path state coordination connection is deployed between the main path and the secondary path transmission link. This coordination connection is used to dynamically monitor the availability of the main path and the secondary path to ensure adaptive adjustment of data transmission. Multi-path state coordination can detect parameters such as bandwidth occupancy, transmission delay, and packet loss rate of each path in real time through a network monitoring module to ensure that the data stream can be dynamically allocated to the optimal path.

[0180] Through the multi-path state coordination connection, the system can obtain the current available state data of the main path transmission channel and the secondary path transmission channel, including network congestion conditions, device load conditions, etc. Based on this data, the system can adjust the data transmission ratio between the main path and the secondary path. For example, when the load of the main path is too high, part of the data is transferred to the secondary path for transmission to balance the data traffic and improve the stability and efficiency of data transmission.

[0181] In this embodiment, by establishing a multi-path transmission link, the reliability and fault tolerance of data transmission are improved, enabling the terminal device to dynamically adjust the data transmission path according to the current network state, avoiding data loss or transmission interruption caused by a single path failure. The dynamic scheduling mechanism of the main path and the secondary path enables data to be evenly distributed on different paths according to the network load, improving bandwidth utilization and reducing data transmission latency. In addition, through the intelligent selection and optimization of the main path and the secondary path, the system can maintain efficient data transmission in various complex network environments, especially suitable for data synchronization scenarios where multiple terminal devices cooperate.

[0182] In one embodiment, the above S70 includes:

[0183] S701, screening terminal devices that meet the target transmission conditions from the terminal devices in the set of connectable devices according to the transmission capability parameters of the terminal devices to generate a target terminal device group, where the target transmission conditions require that the transmission capability parameters of the terminal devices reach a preset distribution threshold;

[0184] S702, splitting the secure encapsulated data into multiple data shards, and attaching a shard sequence identifier to each data shard;

[0185] S703, generating a shard routing mapping table according to the identification information of the transmission channels in the multi-path transmission link, where the shard routing mapping table records the binding relationship between each data shard and the transmission channel;

[0186] S704, sending a first data shard group containing the identification of the main path transmission channel through the main path transmission channel in the multi-path transmission link;

[0187] S705, sending a second data shard group containing the identification of the secondary path transmission channel through the secondary path transmission channel in the multi-path transmission link;

[0188] S706, receiving the first data shard group and the second data shard group in the target terminal device group;

[0189] S707, sequentially reorganizing the received data shards according to the shard sequence identifier to generate the reorganized secure encapsulated data;

[0190] S708, verifying the shard integrity and sequential continuity of the reorganized secure encapsulated data;

[0191] S709, when the verification passes, writing the reorganized secure encapsulated data into the data storage area of the terminal devices in the target terminal device group.

[0192] In this embodiment, the establishment of the multi-path transmission link allows data to be transmitted in parallel between multiple devices, thereby improving the reliability and transmission efficiency of data distribution. Before data distribution, it is necessary to screen devices that meet the target transmission conditions based on the transmission capability parameters of each terminal device in the set of connectable devices to generate a target terminal device group. The target transmission conditions set a minimum distribution threshold, including but not limited to factors such as network bandwidth, signal strength, data processing ability, and response time, to ensure that data reception and storage are only performed on suitable terminal devices to ensure the stability and efficiency of data transmission.

[0193] The distribution of securely encapsulated data adopts a sharding transmission method. The securely encapsulated data is first divided into multiple data shards, and each data shard is appended with a shard sequence identifier, which is used to record the order of the shards so that the target terminal device group can correctly reconstruct the complete data when receiving the data. The sharding strategy can be based on fixed-size splitting or adopt a dynamic sharding method, such as adaptively adjusting the shard size according to the current network environment to optimize the transmission performance.

[0194] To ensure the correct transmission of data, the system needs to generate a shard routing mapping table based on the identification information of the transmission channels in the multi-path transmission link. The shard routing mapping table records the binding relationship between each data shard and the specific transmission channel, enabling the data shards to be scheduled according to the optimized transmission path. The construction of the mapping table can consider the real-time availability of the channels, path congestion conditions, and the load conditions of the devices to ensure the efficiency and reliability of data transmission.

[0195] During the actual data transmission process, the securely encapsulated data will be sent through the main path transmission channel and the secondary path transmission channel in the multi-path transmission link. The first data shard group is transmitted through the main path transmission channel, which is usually used for high-priority, low-latency real-time data transmission to ensure that the data can be quickly delivered to the target device. The second data shard group is transmitted through the secondary path transmission channel, which can be used for data redundancy, load balancing, or low-priority data transmission.

[0196] After the devices in the target terminal device group receive the first data shard group and the second data shard group, they need to sequentially reconstruct the received data shards according to the shard sequence identifier to ensure that the data is restored to the complete securely encapsulated data in the correct order. The sequential reconstruction process can be sorted based on the sequence numbers of the data shards and adopt an error detection mechanism, such as checksum verification or hash verification, to ensure data integrity.

[0197] After the data reconstruction is completed, integrity verification is required to confirm that the data shards are not lost or damaged. Integrity verification can be carried out based on methods such as data hash value comparison, digital signature verification, or error correction code mechanism to ensure that the data has not been tampered with or lost during the transmission process. In addition, it is also necessary to detect the sequential continuity of the data to avoid data disorder or loss caused by network jitter or packet loss.

[0198] When the integrity and sequential continuity verification pass, the reconstructed securely encapsulated data will be written into the data storage areas of each terminal device in the target terminal device group. Data storage can adopt local storage, distributed storage, or cloud storage, etc., to meet different application requirements. For example, in high-security scenarios, an encrypted storage method can be adopted to encrypt the data and store it in the secure storage area of the device to improve data security.

[0199] In this embodiment, data is distributed through a multi-path transmission link, enabling intelligent allocation of data according to the transmission capabilities of terminal devices, improving the stability and efficiency of data transmission. By adopting the data sharding method, data can be transmitted in parallel through multiple channels, reducing congestion problems caused by a single channel and increasing the overall throughput. Through the management of the sharding routing mapping table, the data transmission path can be dynamically adjusted according to the network state, optimizing the data flow distribution strategy. By adopting a data recombination and integrity verification mechanism, it is ensured that the data is correctly restored on the terminal device, avoiding data loss or tampering, and improving the security and reliability of the data.

[0200] In one embodiment, a distributed multi-terminal data collaborative processing device is provided, which corresponds one-to-one with the distributed multi-terminal data collaborative processing method in the above embodiment. Refer to Figure 3 , Figure 3 FIG. is a schematic diagram of the functional modules of a preferred embodiment of the distributed multi-terminal data collaborative processing device of the present invention. Data processing module 10, data transmission module 20, verification response processing module 30, data security encapsulation module 40, device discovery module 50, multi-path scheduling module 60, and data distribution module 70. The detailed description of each functional module is as follows:

[0201] The data processing module 10 is used to receive a structured data unit containing business logic generated by the initiating terminal;

[0202] The data transmission module 20 is used to transmit the structured data unit to the service verification server;

[0203] The verification response processing module 30 is used to receive the verification result data returned by the service verification server;

[0204] The data security encapsulation module 40 is used to perform security encapsulation processing on the verification result data to generate security encapsulated data;

[0205] The device discovery module 50 is used to call the distributed communication service interface of the distributed operating system and detect the set of connectable devices within the network domain where the initiating terminal is located through the distributed communication service interface;

[0206] The multi-path scheduling module 60 is used to establish a multi-path transmission link based on the transmission capability parameters of the terminal devices in the set of connectable devices;

[0207] The data distribution module 70 is used to distribute the security encapsulated data to the target terminal device group in the set of connectable devices through the multi-path transmission link.

[0208] In one embodiment, the data processing module 10 is specifically configured to:

[0209] Initiate a terminal to parse the original service data and extract the form field content in the original service data;

[0210] Based on a preset service type mapping table by the initiating terminal, match the form field content with the corresponding service logic policy to generate a service logic binding field;

[0211] Insert a service type identification field into the service logic binding field by the initiating terminal;

[0212] Execute field-level encryption on the sensitive data fields in the service logic binding field by the initiating terminal to generate an encrypted field data block;

[0213] Combine the encrypted field data block with the unencrypted fields in the service logic binding field by the initiating terminal, and add a data version identifier and a serialization timestamp to generate a structured data unit;

[0214] Receive the structured data unit sent by the initiating terminal.

[0215] In one embodiment, the verification response processing module 30 is specifically configured to:

[0216] Receive the encrypted data packet sent by the service verification server through a preset response port;

[0217] Decrypt the encrypted data packet with a preset session key to obtain the original verification result data generated by the service verification server;

[0218] Verify the digital signature in the original verification result data to generate the original verification result data with verification passed;

[0219] Parse the original verification result data with verification passed and extract the approval status identifier and the associated service identifier in the original verification result data with verification passed;

[0220] Perform format standardization processing on the approval status identifier and the associated service identifier to generate standardized verification result data.

[0221] In one embodiment, the data security encapsulation module 40 is specifically configured to:

[0222] Extract the hardware unique identifier of the initiating terminal from the security encryption module and bind the hardware unique identifier to the verification result data to generate the bound verification result data;

[0223] Process the verified result data after binding through an asymmetric encryption module to generate a secure encapsulated digital signature;

[0224] Create a secure data extension field, embed the secure encapsulated digital signature into the secure data extension field, and generate verified result data with a secure data extension field;

[0225] Obtain the current time and generate a timestamp, encapsulate the timestamp and a preset communication protocol version identifier to generate a secure data packet header;

[0226] Combine the secure data packet header with the verified result data with a secure data extension field to generate the secure encapsulated data.

[0227] In one embodiment, the device discovery module 50 is specifically configured to:

[0228] Call the device discovery interface of the distributed operating system to broadcast a device detection request to the network domain where the initiating terminal is located. The device detection request includes a preset minimum protocol version and a preset signal strength threshold;

[0229] Receive response messages returned by each terminal device in the network domain through the distributed operating system bus;

[0230] Parse the response messages to extract the device identifiers, protocol versions, and signal strength parameters of each terminal device;

[0231] According to the preset minimum protocol version and the preset signal strength threshold, screen out candidate terminal devices that meet the protocol compatibility condition and whose signal strength meets the signal strength condition from each terminal device in the network domain, and generate a preliminary candidate terminal device set;

[0232] Generate a final set of connectable devices based on the resource load parameters of each terminal device in the preliminary candidate terminal device set.

[0233] In one embodiment, the multi-path scheduling module 60 is specifically configured to:

[0234] According to the transmission capacity parameters of the terminal devices in the connectable device set, screen out the terminal devices that meet the main path transmission condition. The main path transmission condition requires that the transmission capacity parameters of the terminal devices reach a first screening threshold;

[0235] Add the terminal devices that meet the main path transmission condition to the main path node set, and the terminal devices in the main path node set form a main path transmission link;

[0236] Exclude the terminal devices included in the set of main path nodes from the set of connectable devices, and filter the terminal devices that meet the secondary path transmission conditions. The secondary path transmission conditions require that the transmission capacity parameter of the terminal device reaches a second screening threshold, and the second screening threshold is lower than the first screening threshold;

[0237] Add the terminal devices that meet the secondary path transmission conditions to the set of secondary path nodes. The terminal devices in the set of secondary path nodes form a secondary path transmission link;

[0238] Assign a main path transmission channel identifier to each terminal device in the set of main path nodes. The main path transmission channel identifier corresponds to the logical transmission channel of the main path transmission link;

[0239] Assign a secondary path transmission channel identifier to each terminal device in the set of secondary path nodes. The secondary path transmission channel identifier corresponds to the logical transmission channel of the secondary path transmission link;

[0240] Deploy a multi-path status coordination connection between the main path transmission link and the secondary path transmission link;

[0241] Obtain the current available status data of the main path transmission channel and the secondary path transmission channel through the multi-path status coordination connection;

[0242] Adjust the data transmission ratio between the main path transmission link and the secondary path transmission link according to the current available status data of the main path transmission channel and the secondary path transmission channel.

[0243] In one embodiment, the data distribution module 70 is specifically configured to:

[0244] Filter the terminal devices that meet the target transmission conditions according to the transmission capacity parameters of the terminal devices in the set of connectable devices to generate a target terminal device group. The target transmission conditions require that the transmission capacity parameter of the terminal device reaches a preset distribution threshold;

[0245] Split the secure encapsulated data into multiple data shards, and attach a shard sequence identifier to each data shard;

[0246] Generate a shard routing mapping table according to the identifier information of the transmission channels in the multi-path transmission link. The shard routing mapping table records the binding relationship between each data shard and the transmission channel;

[0247] Send a first data shard group containing the main path transmission channel identifier through the main path transmission channel in the multi-path transmission link;

[0248] Send a second data shard group containing the secondary path transmission channel identifier through the secondary path transmission channel in the multi-path transmission link;

[0249] Receive the first data shard group and the second data shard group in the target terminal device group;

[0250] Reorder the received data shards according to the shard sequence identifier to generate the reorganized secure encapsulated data;

[0251] Verify the shard integrity and sequential continuity of the reorganized secure encapsulated data;

[0252] When the verification passes, write the reorganized secure encapsulated data into the data storage area of the terminal device in the target terminal device group.

[0253] In one embodiment, a computer device is provided. The computer device can be a server, and its internal structure diagram can be as shown in Figure 4 Figure. The computer device includes a processor, a memory, a network interface, and a database connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes non-volatile and / or volatile storage media, and internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The network interface of the computer device is used to communicate with an external client through a network connection. When the computer program is executed by the processor, it realizes the functions or steps on the server side of a distributed multi-terminal data collaborative processing method.

[0254] In one embodiment, a computer device is provided. The computer device can be a client, and its internal structure diagram can be as shown in Figure 5 Figure. The computer device includes a processor, a memory, a network interface, a display screen, and an input device connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes non-volatile storage media and internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The network interface of the computer device is used to communicate with an external server through a network connection. When the computer program is executed by the processor, it realizes the functions or steps on the client side of a distributed multi-terminal data collaborative processing method

[0255] In one embodiment, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the following steps are implemented:

[0256] Receive a structured data unit containing business logic generated by an initiating terminal;

[0257] Transmit the structured data unit to the service verification server;

[0258] Receive the verification result data returned by the service verification server;

[0259] Perform security encapsulation processing on the verification result data to generate security encapsulated data;

[0260] Invoke the distributed communication service interface of the distributed operating system, and detect the set of connectable devices within the network domain where the initiating terminal is located through the distributed communication service interface;

[0261] Establish a multi-path transmission link based on the transmission capacity parameters of the terminal devices in the set of connectable devices;

[0262] Distribute the security encapsulated data to the target terminal device group in the set of connectable devices through the multi-path transmission link.

[0263] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the following steps are implemented:

[0264] Receive a structured data unit containing business logic generated by an initiating terminal;

[0265] Transmit the structured data unit to the service verification server;

[0266] Receive the verification result data returned by the service verification server;

[0267] Perform security encapsulation processing on the verification result data to generate security encapsulated data;

[0268] Invoke the distributed communication service interface of the distributed operating system, and detect the set of connectable devices within the network domain where the initiating terminal is located through the distributed communication service interface;

[0269] Establish a multi-path transmission link based on the transmission capacity parameters of the terminal devices in the set of connectable devices;

[0270] Distribute the security encapsulated data to the target terminal device group in the set of connectable devices through the multi-path transmission link.

[0271] It should be noted that for the functions or steps that the above computer-readable storage medium or computer device can achieve, reference can be made to the relevant descriptions on the server side and the user side in the foregoing method embodiments. To avoid repetition, they will not be described one by one here.

[0272] Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be completed by instructing relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above methods. Among them, any reference to a memory, storage, database, or other medium used in the embodiments provided in this application can include non-volatile and / or volatile memories. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), Rambus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and Rambus dynamic RAM (RDRAM), etc.

[0273] Those skilled in the art can clearly understand that for the convenience and simplicity of description, only the above division of each functional unit and module is used as an example. In actual applications, the above functions can be allocated to different functional units and modules according to needs, that is, the internal structure of the device is divided into different functional units or modules to complete all or part of the functions described above.

[0274] It should be noted that if there are software tools or components of other companies in the embodiments of this application, they are only used for example introduction and do not represent actual use. The above embodiments are only used to illustrate the technical solutions of the present invention, not to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that they can still modify the technical solutions recorded in the foregoing embodiments, or perform equivalent replacements on some of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present invention, and should all be included in the protection scope of the present invention.

Claims

1. A distributed multi-terminal data collaborative processing method, characterized in that: The following steps are involved: Receiving a structured data unit containing business logic generated by an initiating terminal; transmitting the structured data unit to a business verification server; Receiving the verification result data returned by the business verification server; Performing security encapsulation processing on the verification result data to generate secure encapsulation data; Calling a distributed communication service interface of a distributed operating system, and detecting a set of connectable devices in the network domain where the initiating terminal is located through the distributed communication service interface; Establishing a multipath transmission link based on the transmission capability parameters of the terminal devices in the connectable device set; The secure encapsulated data is distributed to a target terminal device group in the connectable device set via the multipath transmission link.

2. The distributed multi-terminal data collaborative processing method according to claim 1, characterized in that: Receive a structured data unit containing business logic generated by the initiating terminal, including: Parsing the original business data through the initiating terminal, and extracting the form field content in the original business data; By means of the initiating terminal, the form field content is matched with the corresponding business logic policy according to a preset business type mapping table to generate a business logic binding field; Inserting a service type identification field into the service logic binding field by the initiating terminal; Performing field-level encryption on the sensitive data field in the business logic binding field by the initiating terminal to generate an encrypted field data block; The encrypted field data block is combined with the unencrypted field in the business logic binding field by the initiating terminal, and a data version identifier and a serialization timestamp are added to generate a structured data unit; The structured data unit sent by an initiating terminal is received.

3. The distributed multi-terminal data collaborative processing method according to claim 1, characterized in that: Receiving the verification result data returned by the business verification server, including: Receiving the encrypted data packet sent by the business verification server through a preset response port; Decrypting the encrypted data packet using a preset session key to obtain the original verification result data generated by the service verification server; Verifying the digital signature in the original verification result data to generate original verification result data that passes the verification; Parsing the original verification result data that has passed the verification, and extracting the approval status identifier and the associated business identifier from the original verification result data that has passed the verification; The approval status identifier and the associated business identifier are format-standardized to generate standardized verification result data.

4. The distributed multi-terminal data collaborative processing method according to claim 1, characterized in that: The verification result data is securely packaged to generate secure packaged data, including: Extracting the hardware unique identification code of the initiating terminal from the security encryption module, and binding the hardware unique identification code with the verification result data to generate bound verification result data; The bound verification result data is processed by an asymmetric encryption module to generate a secure encapsulation digital signature; Creating a security data extension field, embedding the security encapsulation digital signature into the security data extension field, and generating verification result data containing the security data extension field; Obtaining the current time and generating a timestamp, encapsulating the timestamp and a preset communication protocol version identifier, and generating a secure data packet header; The security data packet header is combined with the verification result data containing the security data extension field to generate the security encapsulation data.

5. The distributed multi-terminal data collaborative processing method according to claim 1, characterized in that: Calling a distributed communication service interface of a distributed operating system, and detecting a set of connectable devices in a network domain where the initiating terminal is located through the distributed communication service interface, including: Calling a device discovery interface of a distributed operating system to broadcast a device detection request to the network domain where the initiating terminal is located, wherein the device detection request includes a preset minimum protocol version and a preset signal strength threshold; Receive response messages returned by each terminal device in the network domain through the distributed operating system bus; Parsing the response message to extract the device identifier, protocol version and signal strength parameter of each terminal device; According to the preset minimum protocol version and the preset signal strength threshold, candidate terminal devices that meet the protocol compatibility condition and whose signal strength meets the signal strength condition are screened out from the terminal devices in the network domain, and a preliminary candidate terminal device set is generated; Based on the resource load parameters of each terminal device in the preliminary candidate terminal device set, a final connectable device set is generated.

6. The distributed multi-terminal data collaborative processing method according to claim 1, characterized in that: Establishing a multipath transmission link based on the transmission capability parameters of the terminal devices in the connectable device set includes: According to the transmission capability parameters of the terminal devices in the connectable device set, screening the terminal devices that meet the main path transmission condition, wherein the main path transmission condition requires that the transmission capability parameters of the terminal devices reach a first screening threshold; Adding terminal devices that meet the main path transmission condition to the main path node set, the terminal devices in the main path node set constitute a main path transmission link; Excluding the terminal devices included in the main path node set from the connectable device set, and screening the terminal devices that meet the auxiliary path transmission condition, wherein the auxiliary path transmission condition requires that the transmission capability parameter of the terminal device reaches a second screening threshold and the second screening threshold is lower than the first screening threshold; Adding terminal devices that meet the auxiliary path transmission condition to the auxiliary path node set, the terminal devices in the auxiliary path node set constitute an auxiliary path transmission link; Allocating a main path transmission channel identifier to each terminal device in the main path node set, wherein the main path transmission channel identifier corresponds to a logical transmission channel of the main path transmission link; Allocating an auxiliary path transmission channel identifier to each terminal device in the auxiliary path node set, wherein the auxiliary path transmission channel identifier corresponds to a logical transmission channel of an auxiliary path transmission link; Deploy a multipath state coordination connection between the primary path transmission link and the secondary path transmission link; Acquire currently available status data of the main path transmission channel and the auxiliary path transmission channel through the multi-path status coordination connection; According to the currently available status data of the main path transmission channel and the auxiliary path transmission channel, the data transmission ratio between the main path transmission link and the auxiliary path transmission link is adjusted.

7. The distributed multi-terminal data collaborative processing method according to claim 1, characterized in that: Distributing the secure encapsulated data to a target terminal device group in the connectable device set through the multipath transmission link includes: According to the transmission capability parameters of the terminal devices in the connectable device set, terminal devices that meet the target transmission condition are screened to generate a target terminal device group, wherein the target transmission condition requires that the transmission capability parameters of the terminal devices reach a preset distribution threshold; Splitting the securely encapsulated data into a plurality of data fragments, and attaching a fragment sequence identifier to each data fragment; Generate a slice routing mapping table according to the identification information of the transmission channel in the multi-path transmission link, wherein the slice routing mapping table records the binding relationship between each data slice and the transmission channel; Sending a first data slice group including a main path transmission channel identifier through a main path transmission channel in the multi-path transmission link; Sending a second data slice group including an auxiliary path transmission channel identifier through an auxiliary path transmission channel in the multipath transmission link; Receiving the first data slice group and the second data slice group in the target terminal device group; Sequentially reorganize the received data fragments according to the fragment sequence identifiers to generate reorganized secure encapsulated data; Verifying the integrity and sequential continuity of the fragments of the reorganized secure encapsulated data; When the verification is passed, the reorganized secure encapsulated data is written into the data storage area of ​​the terminal device in the target terminal device group.

8. A distributed multi-terminal data collaborative processing device, characterized in that: The distributed multi-terminal data collaborative processing device comprises: A data processing module, used for receiving a structured data unit containing business logic generated by an initiating terminal; A data transmission module, used for transmitting the structured data unit to a business verification server; A verification response processing module, used to receive the verification result data returned by the business verification server; A data security encapsulation module, used to perform security encapsulation processing on the verification result data to generate secure encapsulation data; A device discovery module, used to call a distributed communication service interface of a distributed operating system, and detect a set of connectable devices in the network domain where the initiating terminal is located through the distributed communication service interface; A multipath scheduling module, used to establish a multipath transmission link based on the transmission capability parameters of the terminal devices in the connectable device set; A data distribution module is used to distribute the securely encapsulated data to a target terminal device group in the connectable device set via the multi-path transmission link.

9. A computer device, characterized in that: The computer device includes a memory, a processor, and a distributed multi-terminal data collaborative processing program stored in the memory and executable on the processor. When the distributed multi-terminal data collaborative processing program is executed by the processor, the steps of the distributed multi-terminal data collaborative processing method according to any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium, characterized in that: The storage medium stores a distributed multi-terminal data collaborative processing program, which, when executed by a processor, implements the steps of the distributed multi-terminal data collaborative processing method according to any one of claims 1 to 7.

Images