Multi-terminal cooperative processing method and system

By establishing a temporary collaboration group in the hospital terminal equipment to share and process event data, data redundancy and resource waste caused by independent reporting by multiple terminals is solved, efficient and secure collaborative processing of medical data is achieved, and system performance and data quality are improved.

CN120416835AActive Publication Date: 2025-08-01WUHAN SHENGBOHUI INFORMATION TECH CO LTD

Patent Information

Application Number
CN202510751035.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2025-06-06
Publication Date
2025-08-01
Estimated Expiration
2045-06-06

AI Technical Summary

Technical Problem

In hospital scenarios, when multiple terminal devices detect the same potential event at the same time, independently reporting data causes excessive consumption of computing resources on the remote management platform, resulting in data redundancy and conflict, increasing the communication and processing burden.

Method used

By establishing a temporary collaboration group, terminal devices share event-related data, encrypted communication and consensus algorithms are used to determine consensus event descriptions, and the leading terminal reports to the remote management platform, combining dynamic terminal selection and load balancing mechanisms to reduce redundant data flow.

Benefits of technology

It significantly reduces the network bandwidth occupation and processing burden of the remote management platform, improves the reliability of data quality and event judgment, ensures the security of medical data, the adaptability and scalability of the system, and improves the quality and efficiency of medical services.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN120416835A_ABST
    Figure CN120416835A_ABST
Patent Text Reader

Abstract

The invention discloses a multi-terminal cooperative processing method and system, and relates to the field of terminal communication, and the method comprises the steps: responding to a trigger signal of an event, determining event information, and initiating a cooperative processing request to at least one second terminal in a communication range; determining a target terminal responding to the cooperative processing request in the second terminal, and constructing a temporary cooperative group including the target terminal; acquiring shared event associated data in the temporary collaborative group, and determining a consensus event description based on the event associated data and / or the event information; a dominant reporting terminal is determined in the temporary cooperation group, and the dominant reporting terminal is used for packaging the consensus event description into a data packet and sending the data packet to a remote management platform; and receiving a response confirmation message returned by the remote management platform, and broadcasting the unique event ID and the processing state in the response confirmation message to all terminals in the temporary collaborative group. The computing resource consumption of the remote management platform can be effectively reduced.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Embodiments of the present application relate to the field of terminal communication, and in particular, to a multi-terminal collaborative processing method and system. Background Art

[0002] In a hospital scenario, a large number of terminals are deployed, such as wearable physiological parameter monitoring devices, bedside monitors, intelligent infusion pumps, mobile nursing terminals, and various environmental sensors. These terminals can collect patients' physiological data, behavior information, and environmental parameters in real time, providing data support for early warning, diagnosis, treatment, and rehabilitation management of diseases.

[0003] In a traditional hospital terminal system, when an event occurs, such as an abnormal fluctuation in a patient's vital signs or the initial signs of a public health emergency in a specific area, each relevant terminal usually independently reports the raw data or pre-processed data it senses to a remote management platform or a central server. The remote management platform is responsible for aggregating, analyzing, storing, and providing decision support for the received data.

[0004] However, in many cases, especially when multiple terminals simultaneously sense data that may point to the same potential event. For example, in a ward, multiple sensors worn by a patient (such as heart rate, blood oxygen, and body temperature sensors) and a bedside monitor may simultaneously detect an abnormality in the patient's vital signs. If these devices all independently report their respective raw data or simply processed data to the remote management platform concurrently, it will result in a large amount of redundant and potentially conflicting data being reported to the remote management platform by multiple terminals for the same event. The remote management platform needs to process a large amount of duplicate data, severely consuming computing resources, and thus increasing the communication and processing burden on the remote management platform. Summary of the Invention

[0005] Embodiments of the present application provide a multi-terminal collaborative processing method and system, which are used to effectively reduce redundant reporting, reduce the consumption of computing resources of the remote management platform, and thus reduce the communication and processing burden on the remote management platform.

[0006] To achieve the above object, the embodiments of the present application adopt the following technical solutions: In a first aspect, a multi-terminal collaborative processing method is provided, which is applied to a first terminal. The first terminal is connected to a central control device, and a remote management platform is deployed on the central control device. The method includes: In response to a trigger signal of an event, determine the event information of the event, and initiate a collaborative processing request to at least one second terminal within the communication range. The event information includes an event summary with an initial timestamp. The collaborative processing request carries the event summary. Each second terminal is connected to the central control device and is used to determine whether to respond to the collaborative processing request; Determine the target terminal that responds to the collaborative processing request in the second terminal, and construct a temporary collaborative group including the target terminal; Obtain the shared event correlation data within the temporary collaborative group, and determine the consensus event description based on the event correlation data and / or event information; Determine a leading reporting terminal in the temporary collaborative group, where the leading reporting terminal is used to encapsulate the consensus event description into a data packet and send the data packet to the remote management platform; Receive the response confirmation message returned by the remote management platform, and broadcast the unique event ID and processing status in the response confirmation message to all terminals within the temporary collaborative group, so that all terminals can synchronously update the processing progress of the event.

[0007] In a possible implementation manner of the first aspect, obtaining the shared event correlation data within the temporary collaborative group includes: Establish an encrypted communication channel within the temporary collaborative group, where the target terminal and the first terminal are used to send the collected event correlation data to the temporary collaborative group through the encrypted communication channel; Obtain the shared event correlation data within the temporary collaborative group.

[0008] In another possible implementation manner of the first aspect, establishing an encrypted communication channel within the temporary collaborative group includes: Generate a temporary session key for the temporary collaborative group, and distribute the temporary session key to all terminals within the temporary collaborative group. Among them, each terminal within the temporary collaborative group is used to encrypt the collected event correlation data through the temporary session key, and decrypt the event correlation data shared by other terminals through the temporary session key.

[0009] In another possible implementation manner of the first aspect, distributing the temporary session key to all terminals within the temporary collaborative group includes: Obtain the device identifiers and public keys of all terminals within the temporary collaborative group; For any terminal within the temporary collaborative group, encrypt the temporary session key with the public key of the terminal to obtain the encrypted session key for the terminal; Send the encrypted session key and the digital signature of the first terminal to other terminals together; After sending the encrypted session key and the digital signature of the first terminal to other terminals together, it further includes: Receive the confirmation messages returned by other terminals, where the confirmation messages include the verification values of the temporary session keys obtained after other terminals decrypt them with their private keys; When the verification values of all terminals are consistent, it is determined that the temporary session key is securely shared among all terminals.

[0010] In another possible implementation of the first aspect, the event correlation data includes continuous numerical parameters and discrete state parameters, and the event information further includes event type and severity level. Based on the event correlation data and / or the event information, a consensus event description is determined, including: In the case where the event correlation data is continuous numerical parameters, obtain the continuous numerical parameters collected by all terminals in the temporary collaboration group, and calculate the weighted average of all continuous numerical parameters, and use the weighted average as the consensus value; Use the consensus value as the consensus event description; In the case where the event correlation data is discrete state parameters, obtain the discrete state parameters collected by all terminals in the temporary collaboration group, and use the majority voting method to use the discrete state parameter with the highest number of votes as the consensus event description; When there are state values with the same number of votes, use the state value of the terminal with the highest priority as the consensus event description.

[0011] In another possible implementation of the first aspect, determining a dominant reporting terminal in the temporary collaboration group includes: According to the preset terminal priority rules, calculate the comprehensive score of each terminal in the temporary collaboration group; Use the terminal with the highest comprehensive score as the dominant reporting terminal.

[0012] In another possible implementation of the first aspect, the dominant reporting terminal encapsulates the consensus event description into a data packet and sends the data packet to the central control device, including: The dominant reporting terminal serializes the consensus event description into a standard data format, and adds the group identifier of the temporary collaboration group and the list of participating terminals to the standard data format to obtain the serialized data; Use the public key of the remote management platform to encrypt the serialized data to obtain an encrypted data payload; Calculate the digital digest of the encrypted data payload, and use the private key of the dominant reporting terminal to sign the digital digest to obtain a digital signature; Construct a data packet including the encrypted data payload and the digital signature, and send the data packet to the central control device.

[0013] In a second aspect, the present application provides a multi-terminal collaborative processing method, which is applied to a central control device. The central control device is deployed with a remote management platform. The method includes: In response to receiving the data packet sent by the dominant reporting terminal, decrypt the data packet to obtain the consensus event description; According to the consensus event description, obtain the event information of the event; Import the event information into a preset event processing queue, and send a response confirmation message to the leading reporting terminal. The response confirmation message includes a unique event ID and the processing status of the consensus event description.

[0014] In a possible implementation manner of the second aspect, after sending the response confirmation message to the leading reporting terminal, it further includes: Trigger the corresponding diagnostic engine based on the consensus event description and output the diagnostic result.

[0015] In a third aspect, the present application provides a multi-terminal collaborative processing system, including: A first terminal; At least one second terminal; A central control device, which is deployed with a remote management platform and is connected to both the first terminal and at least one second terminal.

[0016] Through the above technical solutions, the key problems of duplicate reporting, data redundancy, and resource waste of multiple devices in the traditional hospital terminal system are effectively solved. By establishing an intelligent terminal collaboration mechanism, when a medical event occurs, relevant terminals can automatically organize to form a temporary collaboration group, and through secure data sharing and consensus algorithms, the scattered monitoring data is fused into a unified and accurate event description, significantly improving the data quality and the reliability of event judgment. The unified reporting mechanism integrates multiple concurrent data streams that may originally occur into a single high-quality data packet, greatly reducing the network bandwidth occupancy and the processing burden of the remote management platform, and significantly improving the overall performance of the system. The application of encryption communication and digital signature technologies ensures the security and integrity of medical data during transmission, meeting the strict requirements of the medical industry for data security. The dynamic terminal selection and load balancing mechanism enables the system to flexibly adjust the collaboration strategy according to the actual situation, improving the adaptability and scalability of the system. The real-time status synchronization and feedback mechanism form a complete event processing closed-loop, enabling medical staff to timely understand the patient's condition and the system's response, providing reliable technical support for clinical decision-making, and ultimately improving the quality and efficiency of medical services.

[0017] Other features and advantages of the embodiments of the present application will be described in detail in the subsequent specific implementation part. Description of the Drawings

[0018] Figure 1 It is a schematic flowchart of a multi-terminal collaborative processing method provided by an embodiment of the present application; Figure 2 It is a signaling flow diagram of a multi-terminal collaborative processing method provided by an embodiment of the present application; Figure 3 It is a schematic structural diagram of a multi-terminal collaborative processing system provided by an embodiment of the present application. Detailed implementation manners

[0019] To make the objectives, technical solutions, and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. It should be understood that the specific implementation manners described herein are only for explaining and illustrating the embodiments of the present application, and are not used to limit the embodiments of the present application. All other embodiments obtained by those of ordinary skill in the art based on the embodiments in the present application without creative efforts belong to the scope of protection of the present application.

[0020] It should be noted that if there are directional indications (such as up, down, left, right, front, back,...) involved in the embodiments of the present application, the directional indications are only used to explain the relative positional relationship and movement conditions between components in a specific posture (as shown in the drawings). If the specific posture changes, the directional indications will also change accordingly.

[0021] In addition, if there are descriptions involving "first", "second", etc. in the embodiments of the present application, the descriptions of "first", "second", etc. are only for descriptive purposes, and cannot be understood as indicating or implying their relative importance or implicitly indicating the quantity of the indicated technical features. Thus, the features defined with "first" and "second" may explicitly or implicitly include at least one such feature. In addition, the technical solutions between various embodiments can be combined with each other, but it must be based on the fact that those of ordinary skill in the art can implement them. When the combination of technical solutions is contradictory or cannot be implemented, it should be considered that such a combination of technical solutions does not exist and is not within the scope of protection required by the present application.

[0022] Figure 1 A flowchart of a multi-terminal collaborative processing method according to an embodiment of the present application is schematically shown. As Figure 1 shown, an embodiment of the present application provides a multi-terminal collaborative processing method, which is applied to a first terminal. The first terminal is connected to a central control device, and a remote management platform is deployed on the central control device. The method may include the following steps.

[0023] S110. In response to a trigger signal of an event, determine the event information of the event, and initiate a collaborative processing request to at least one second terminal within the communication range. The event information includes an event summary with an initial timestamp. The collaborative processing request carries the event summary. Each second terminal is connected to the central control device and is used to determine whether to respond to the collaborative processing request; S120. Determine a target terminal that responds to the collaborative processing request in the second terminal, and construct a temporary collaborative group including the target terminal; S130. Obtain the shared event correlation data within the temporary collaboration group, and determine a consensus event description based on the event correlation data and / or event information; S140. Determine a leading reporting terminal in the temporary collaboration group. The leading reporting terminal is used to encapsulate the consensus event description into a data packet and send the data packet to the remote management platform; S150. Receive the response confirmation message returned by the remote management platform, and broadcast the unique event ID and processing status in the response confirmation message to all terminals within the temporary collaboration group, so that all terminals can synchronously update the processing progress of the event.

[0024] Refer to Figure 2 , in a hospital environment, the first terminal acts as a medical monitoring device, continuously monitoring the patient's physiological parameters or environmental status. When an abnormal situation is detected, such as the patient's heart rate exceeding the preset threshold or the blood oxygen saturation being lower than the safe range, the event detection algorithm built into the first terminal will immediately trigger an event signal. The event detection mechanism combines multi-level threshold judgment and trend analysis. First, the sliding window algorithm is used to smooth the continuously collected data, and then it is compared with the preset normal range. When the data deviates from the normal range by more than a set multiple of the standard deviation, a primary alarm is triggered; when multiple consecutive sampling points exceed the threshold or show a dangerous trend, an event signal is triggered. [[ID=ll]]

[0025] If the event is triggered, the first terminal will immediately generate an event summary containing the initial timestamp to ensure the time synchronization accuracy in a distributed environment. The event summary contains key information such as the event type identifier, severity level assessment, trigger parameter value, and the device identifier of the first terminal. The first terminal broadcasts a collaborative processing request to all second terminals within its communication range through the wireless communication module. The determination of the communication range is based on signal strength and network topology, usually covering relevant monitoring devices in the same ward or adjacent areas. The collaborative processing request adopts a lightweight message format to carry the core information of the event summary, so as to reduce the network transmission overhead. Each second terminal that receives the request will judge whether it needs to respond to the collaborative processing request according to its own device type, current working status, and relevance to the event. This mechanism of actively initiating collaboration effectively avoids the problem of false alarms by a single device and lays a foundation for subsequent data fusion and consensus reaching.

[0026] After the collaborative processing request is sent out, the second terminals within the communication range will decide whether to participate in the collaborative processing according to the preset response strategy. The response strategy is based on evaluations of multiple dimensions, including the correlation between the device and the event, the current workload of the device, the battery power status, and the network connection quality. The correlation evaluation is calculated through device type matching and spatial location correlation. For example, when a heart rate monitoring event occurs, physiological parameter monitoring devices such as blood oxygen monitors and sphygmomanometers have a high correlation, while the correlation of environmental sensors is relatively low. Each second terminal will use a weighted scoring algorithm to calculate its own response priority score. When the score of the second terminal exceeds the preset threshold, it will send a response confirmation message to the first terminal, indicating its willingness to participate in the collaborative processing.

[0027] After the first terminal collects all the response confirmation messages, it will screen out the most suitable target terminals from the responding second terminals. Once the target terminals are determined, the first terminal will send a group construction confirmation message to all the selected target terminals to officially establish a temporary collaborative group. Each terminal within the group will be assigned a temporary in-group identifier for subsequent in-group communication and data synchronization. This dynamic formation mechanism ensures that the scale of the collaborative group is appropriate, which can obtain sufficient data support and will not increase the communication complexity due to too many devices.

[0028] After the temporary collaborative group is established, a secure and reliable data sharing mechanism needs to be established within the group. First, as the initiator of the group, the first terminal will generate a temporary session key according to the key generation standard of the AES-256 encryption algorithm to ensure the security of data transmission. The key distribution process uses asymmetric encryption. The first terminal obtains the public key information of all terminals within the group, and then encrypts the temporary session key using the public key of each terminal to generate a personalized encrypted key package for each terminal. The encrypted key package, together with the digital signature of the first terminal, is sent to the corresponding terminal. The receiving terminal decrypts it with its own private key to obtain the temporary session key, and ensures the authenticity and integrity of the key by verifying the digital signature. After establishing the encrypted communication channel, each terminal within the group starts to collect data related to the event. The event-related data includes continuous numerical parameters (such as physiological indicators like heart rate, blood pressure, body temperature, etc.) and discrete state parameters (such as device operating status, patient activity status, etc.). Each terminal encrypts the collected data with the temporary session key and shares it through the in-group communication channel.

[0029] Data sharing adopts the publish - subscribe model. Each terminal is both a data publisher and a subscriber of other terminals' data. After obtaining all shared data, the group needs to determine a unified event description through a consensus algorithm. For continuous numerical parameters, a weighted average algorithm is used to calculate the consensus value, and the weights are determined based on the device's accuracy level and reliability assessment. For discrete state parameters, a majority voting mechanism is adopted. When there is a tie in the votes, the judgment result of the terminal with the highest priority is preferentially selected.

[0030] After forming a consensus event description, the temporary cooperation group needs to determine a leading reporting terminal to be responsible for communicating with the remote management platform. The selection of the leading terminal is based on a comprehensive scoring mechanism, and the scoring criteria include multiple dimensions such as the device's computing power, network connection stability, battery power level, historical reporting success rate, and the device's authority level. The terminal with the highest score is selected as the leading reporting terminal, assuming the responsibilities of data encapsulation and reporting.

[0031] The leading reporting terminal first performs standardized serialization processing on the consensus event description, organizes the data structure in JSON format, including the complete description information of the event, the list of terminals participating in the cooperation, the group identifier, and the integrity verification code of the data, etc. To ensure the security of data transmission, the leading terminal uses the public key of the remote management platform to encrypt the serialized data, generating an encrypted data payload. At the same time, calculate the SHA - 256 hash digest of the encrypted data and use its own private key to digitally sign the digest to ensure data immutability and source authentication. The final data packet contains information such as the encrypted payload, digital signature, timestamp, and transmission protocol header. The data packet is sent to the central control device through the secure network channel within the hospital. The transmission process uses the reliable TCP protocol and sets up a retransmission mechanism and timeout handling to ensure that the data can accurately reach the remote management platform. This unified reporting mechanism effectively avoids the problem of multiple terminals simultaneously sending duplicate data to the platform, significantly reducing network bandwidth occupancy and platform processing burden.

[0032] After the remote management platform receives the data packet sent by the leading reporting terminal, it will perform a series of verification and processing operations. First, it verifies the validity of the digital signature to confirm the credibility of the data source and the integrity of the data content. Then, it decrypts the data payload using the private key of the platform to obtain the complete consensus event description information. The platform assigns a globally unique event identifier (UUID) to each received event and determines the processing priority according to the type and severity of the event, and adds the event information to the corresponding processing queue. The processing status includes multiple levels such as "Received", "Processing", "Analyzed", "Needs Manual Intervention", etc., reflecting the processing progress of the event within the platform. The platform generates a response confirmation message, which contains information such as the assigned unique event ID, the current processing status, the estimated processing time, and possible preliminary suggestions. The response message is returned to the leading reporting terminal through a secure channel. After receiving the response, the leading terminal immediately broadcasts the key information to all member terminals within the temporary collaboration group. The broadcast process uses multicast to ensure that all participating terminals can synchronously obtain the update of the event processing progress.

[0033] After each terminal receives the update information, it will update the corresponding records in the event status table maintained locally, including information such as the event ID, processing status, and update time. This status synchronization mechanism enables all terminals within the group to understand the processing situation of the event in real time, providing support for subsequent possible collaborative operations or status queries. At the same time, the terminal will also adjust its monitoring strategy according to the change of the processing status. For example, after the event is properly processed, the monitoring frequency can be appropriately reduced to save power resources. The entire feedback mechanism forms a complete closed loop from the occurrence to the completion of the event, ensuring the reliability and response efficiency of the medical monitoring system.

[0034] This embodiment effectively solves the key problems of multi-device duplicate reporting, data redundancy, and resource waste in traditional hospital terminal systems. By establishing an intelligent terminal collaboration mechanism, when a medical event occurs, relevant terminals can automatically organize to form a temporary collaboration group. Through secure data sharing and consensus algorithms, scattered monitoring data is fused into a unified and accurate event description, significantly improving data quality and the reliability of event judgment. The unified reporting mechanism integrates multiple concurrent data streams that might otherwise occur into a single high-quality data packet, greatly reducing network bandwidth occupancy and the processing burden on the remote management platform, and significantly enhancing the overall performance of the system. The application of encryption communication and digital signature technologies ensures the security and integrity of medical data during transmission, meeting the strict requirements of the medical industry for data security. The dynamic terminal selection and load balancing mechanism enables the system to flexibly adjust collaboration strategies according to actual situations, improving the adaptability and scalability of the system. The real-time status synchronization and feedback mechanism form a complete closed-loop for event processing, enabling medical staff to timely understand the patient's condition and the system's response, providing reliable technical support for clinical decision-making, and ultimately enhancing the quality and efficiency of medical services.

[0035] In one implementation manner of this embodiment, obtaining shared event-related data within the temporary collaboration group includes the following steps: S210. Establish an encrypted communication channel within the temporary collaboration group. The target terminal and the first terminal are used to send the collected event-related data to the temporary collaboration group through the encrypted communication channel; S220. Obtain shared event-related data within the temporary collaboration group.

[0036] After the temporary collaboration group is established, to ensure the security and privacy protection of medical data during transmission, a secure and reliable encrypted communication channel needs to be established within the group. The establishment of the encrypted communication channel adopts a hybrid encryption system, combining the advantages of symmetric encryption and asymmetric encryption, which not only ensures the security of data transmission but also guarantees communication efficiency.

[0037] First, as the initiator and coordinator of the collaboration group, the first terminal is responsible for generating a temporary session key. The session key is generated using the AES-256 standard, with a key length of 256 bits. A high-entropy random seed is generated through a hardware random number generator to ensure the unpredictability and uniqueness of the key. The key generation process also combines information such as the current timestamp, device identifier, and event identifier as additional entropy sources to further enhance the randomness of the key. The generated temporary session key has a time limit, usually set to twice the duration of the event processing cycle, which not only ensures the continuity of data transmission but also avoids the security risks brought by long-term use of the same key.

[0038] The key distribution process adopts the public key infrastructure system. The first terminal first obtains the digital certificates and public key information of all target terminals in the temporary collaboration group from the hospital's device certificate management center. For each target terminal in the group, the first terminal uses the RSA public key of that terminal to encrypt the temporary session key, generating a personalized encrypted key package for that terminal. The OAEP padding mode is used in the encryption process to enhance the encryption strength and prevent chosen-ciphertext attacks. The encrypted key package, together with the digital signature of the first terminal, is sent to the corresponding target terminal through a secure channel.

[0039] After receiving the encrypted key package, the target terminal first verifies the validity of the digital signature of the first terminal to confirm the credibility of the message source, and then uses its own private key to decrypt and obtain the temporary session key. To ensure the success and consistency of key distribution, each target terminal calculates the hash check value of the key after obtaining the key and returns the check value to the first terminal for verification. Only when the check values of all terminals are consistent is it confirmed that the encrypted communication channel is successfully established. The established encrypted communication channel supports end-to-end encryption, and all event-related data transmitted within the channel is encrypted using AES-256. Even if the data is intercepted during transmission, it cannot be interpreted by unauthorized parties, effectively protecting patient privacy and the security of medical data.

[0040] After the secure encrypted communication channel is established, each terminal in the temporary collaboration group starts to share event-related data through this channel. The process of obtaining event-related data adopts a distributed data collection and synchronization mechanism to ensure that all terminals in the group can obtain a complete and consistent data set. Each target terminal collects various types of data related to the current event according to its own device type and monitoring capabilities. For physiological parameter monitoring devices, such as electrocardiogram monitors, detailed electrocardiogram data such as the patient's heart rate, heart rhythm, and ST-segment changes will be collected; oximeters will provide parameters such as blood oxygen saturation, pulse rate, and perfusion index; blood pressure monitoring devices will record hemodynamic indicators such as systolic blood pressure, diastolic blood pressure, and mean arterial pressure. For environmental monitoring devices, environmental parameters such as temperature, humidity, air quality, and noise level in the ward will be collected. All collected data will be marked with accurate timestamps and time synchronization will be carried out using the Network Time Protocol (NTP) to ensure the consistency of data collected by different devices in the time dimension.

[0041] After the data collection is completed, each terminal will preprocess the data, including operations such as outlier detection, noise filtering, and data format standardization. The preprocessed data is encrypted using the temporary session key with AES-256 and a message authentication code (MAC) is added to ensure the integrity and authenticity of the data. The encrypted data is sent to the shared data pool of the temporary collaborative group through the established secure communication channel. The data transmission uses a reliable transmission protocol, sets up an acknowledgment mechanism and a retransmission strategy to ensure that the data can reach the target accurately and without error. The first terminal, as the data aggregation node, is responsible for receiving, decrypting, and organizing the event correlation data from each target terminal. The received encrypted data is first verified by MAC to confirm that the data has not been tampered with during transmission, and then decrypted using the temporary session key to restore the original event correlation data. The decrypted data is sorted and aligned according to the timestamp to form a time-series data set.

[0042] To handle possible data conflicts or inconsistencies, a data fusion algorithm is used to process the same type of data from different terminals. For numerical data, more reliable data values are obtained through weighted average or median filtering; for status data, the majority voting or expert system method is used to determine the final status judgment. The entire data acquisition process realizes distributed, secure, and efficient data sharing, providing a complete and reliable data foundation for the subsequent generation of consensus event descriptions. At the same time, the privacy and security of medical data are ensured through encryption protection.

[0043] This implementation method significantly improves the security, reliability, and data quality of the multi-terminal collaborative processing system through the establishment of an encrypted communication channel and a data sharing mechanism. The establishment of the encrypted communication channel combines the high efficiency of AES-256 symmetric encryption and the security of RSA asymmetric encryption, ensuring both the absolute security of medical data transmission and that the communication efficiency is not affected. The dynamic generation and secure distribution mechanism of the temporary session key effectively prevent key leakage and replay attacks, meeting the strict requirements of the medical industry for data security. The distributed data collection and synchronization mechanism enables all terminals within the temporary collaborative group to obtain complete and consistent event correlation data, avoiding the problem of incomplete information caused by data islands in traditional systems. The application of data preprocessing and fusion algorithms improves the data quality, and through outlier detection and noise filtering, ensures the accuracy of subsequent analysis. The time synchronization mechanism ensures the consistency of data from different devices in the time dimension, providing a basis for accurate event reconstruction and analysis. The entire data sharing process realizes end-to-end security protection, with corresponding security measures at each link from data collection to data aggregation, constructing a complete data security protection system, providing a solid technical guarantee for the reliable operation of the medical monitoring system.

[0044] In one implementation of this embodiment, an encrypted communication channel is established within the temporary collaboration group, including the following steps: S310. Generate a temporary session key for the temporary collaboration group and distribute the temporary session key to all terminals within the temporary collaboration group. Each terminal within the temporary collaboration group is used to encrypt the collected event-related data through the temporary session key and decrypt the event-related data shared by other terminals through the temporary session key.

[0045] The generation of the temporary session key is the core link for establishing a secure encrypted communication channel, and its security directly determines the confidentiality level of data transmission within the entire collaboration group. The key generation process uses a cryptographically secure pseudo-random number generator and combines multiple entropy sources to ensure the unpredictability and uniqueness of the generated key. First, the first terminal will collect multiple entropy source information, including the current high-precision timestamp, the hardware serial number of the device, the unique identifier of the current event, the random data segment in the device memory, and the MAC address of the network interface, etc. These information are mixed through the SHA-256 hash function to generate a 256-bit seed value.

[0046] The seed value is then input into a key derivation function based on the AES algorithm, and the PBKDF2 standard is used for key expansion. The number of iterations is set to more than 10,000 times to ensure that even if the seed value is partially leaked, it is difficult for attackers to obtain the final session key through brute force cracking. The generated temporary session key is 256 bits in length, meeting the requirements of the AES-256 encryption standard, and has sufficient key space to resist current and foreseeable future cryptographic attacks. To enhance the timeliness and security of the key, the session key is also set with a validity period in combination with the life cycle of the event, usually set to 1.5 times the expected event processing time, which not only ensures the effectiveness of the key during the collaborative processing process but also avoids the security risks brought by using the same key for a long time. After the key generation is completed, the first terminal will calculate the checksum of the key and generate a 32-bit check code using the CRC32 algorithm for subsequent verification of the correctness of key distribution. The entire key generation process is completed in a trusted execution environment to ensure that the key will not be obtained by malware or attackers during the generation process. The generated key will be temporarily stored in the secure storage area of the device and protected by hardware-level encryption. Only authorized encryption and decryption modules can access it.

[0047] The key distribution process adopts a secure distribution mechanism based on public key cryptography to ensure that the temporary session key can be securely transmitted to all target terminals within the temporary collaboration group. First, the first terminal needs to obtain the public key certificate information of all target terminals within the group. These certificates are usually stored in the hospital's public key infrastructure system and contain information such as the RSA public key of each device, the certificate validity period, the device identifier, and the digital signature. The first terminal uses the device identifier of the target terminal as the query condition through a secure certificate query interface to obtain the corresponding digital certificate. After obtaining the certificate, the first terminal will verify the validity of the certificate, including checking whether the certificate is within the validity period, whether the certificate chain is complete, and whether the certificate has been revoked. After successful verification, the RSA public key of the target terminal is extracted from the certificate.

[0048] For each target terminal within the temporary collaboration group, the first terminal will encrypt the temporary session key using the terminal's RSA public key. The encryption process uses the OAEP (Optimal Asymmetric Encryption Padding) padding mode, which can effectively prevent chosen ciphertext attacks and other cryptographic attacks.

[0049] In addition to the session key itself, the encrypted package also contains metadata such as the key validity period information, generation timestamp, and checksum. To ensure the integrity and authenticity of the message, the first terminal will also digitally sign the encrypted key package using its own private key to generate a digital signature value. The final key distribution message contains the encrypted session key, digital signature, the certificate information of the first terminal, and the message timestamp. These messages are sent to the corresponding target terminals through the secure network channel within the hospital, and the TLS encryption protocol is used for additional transport layer protection during the transmission process.

[0050] After receiving the key distribution message, the target terminal will verify the timestamp of the message to ensure that the message is sent within a reasonable time window to prevent replay attacks. Then it verifies the validity of the digital certificate of the first terminal, including certificate chain verification, validity period check, and revocation status query. After successful certificate verification, the target terminal uses the public key of the first terminal to verify the digital signature to ensure that the message indeed comes from the first terminal and has not been tampered with. After successful signature verification, the target terminal uses its own RSA private key to decrypt the encrypted session key.

[0051] After decryption, the target terminal will verify the checksum of the session key to ensure that the key has not been corrupted during transmission. After successful verification, the target terminal stores the temporary session key in a local secure storage area and sets the corresponding validity period. To confirm the successful key distribution, the target terminal generates an acknowledgement message containing information such as the hash value of the key, the reception timestamp, and the device identifier, signs it with its own private key, and sends it back to the first terminal. After receiving the acknowledgement messages from all target terminals, the first terminal verifies the signature and the key hash value of each acknowledgement message. Only when all terminals have successfully received and verified the session key is the encrypted communication channel considered to be successfully established.

[0052] After the encrypted communication channel is established, each terminal within the temporary collaboration group can use the temporary session key to encrypt and decrypt event-related data. The data encryption process uses the CBC (Cipher Block Chaining) mode of the AES-256 algorithm, which can effectively hide the pattern characteristics of the plaintext and improve the encryption strength. For each encryption operation, the terminal generates a random initialization vector (IV) with a length of 128 bits, which matches the block size of the AES algorithm.

[0053] The encrypted data includes parts such as the ciphertext, IV, and message authentication code (MAC). When a terminal needs to decrypt data shared by other terminals, it first verifies the correctness of the MAC to ensure that the data has not been tampered with during transmission, and then uses the same temporary session key and the extracted IV for decryption operations.

[0054] Through this symmetric encryption mechanism, all terminals within the temporary collaboration group can securely share event-related data, ensuring both the confidentiality of the data and the efficiency of communication. The establishment of the encrypted communication channel provides comprehensive protection for sensitive medical data during network transmission, effectively preventing data leakage and privacy violations, and meeting the strict requirements of the medical industry for data security.

[0055] This embodiment constructs a highly secure, efficient and reliable encryption communication system, providing a solid security foundation for multi-terminal collaborative processing. The key generation process uses multiple entropy sources and a cryptographically secure random number generator to ensure the high randomness and unpredictability of the generated keys, effectively resisting various cryptographic attacks. The secure distribution mechanism based on public key cryptography realizes the secure transfer of keys, ensuring that keys cannot be stolen or tampered with even in an insecure network environment. The application of OAEP padding mode and digital signature technology further enhances the security and reliability of key distribution. The use of the symmetric encryption algorithm AES-256 ensures high security while also guaranteeing the efficiency of data encryption and decryption, meeting the real-time requirements of the medical monitoring system. The combination of CBC encryption mode and message authentication code not only protects the confidentiality of data but also ensures the integrity and authenticity of data. The time-limited design of the temporary session key effectively reduces the security risks brought by long-term use of the same key and improves the security level of the entire system. The entire encryption communication mechanism realizes end-to-end data protection, with corresponding security guarantees throughout the process from data generation to data consumption, constructing a complete data security protection system and providing reliable technical support for the secure sharing and collaborative processing of medical data.

[0056] In one implementation manner of this embodiment, the temporary session key is distributed to all terminals within the temporary collaboration group, including the following steps: S410. Obtain the device identifiers and public keys of all terminals within the temporary collaboration group; S420. For any terminal within the temporary collaboration group, encrypt the temporary session key using the public key of this terminal to obtain an encrypted session key for this terminal; S430. Send the encrypted session key and the digital signature of the first terminal to other terminals together; S440. After sending the encrypted session key and the digital signature of the first terminal to other terminals together, it further includes: S450. Receive the confirmation messages returned by other terminals, where the confirmation messages include the verification values of the temporary session key obtained after other terminals decrypt it using their private keys; S460. When the verification values of all terminals are consistent, determine that the temporary session key is securely shared among all terminals.

[0057] After the establishment of the temporary collaboration group, the first terminal needs to obtain the device identifiers and public key information of all target terminals within the group, which is a prerequisite for secure key distribution. The process of obtaining device identifiers is based on the hospital's internal device management system. Each medical terminal is registered in the device registration center during deployment to obtain a globally unique device identifier. The device identifier contains information such as hospital code, department code, device type code, and device serial number.

[0058] The first terminal obtains the complete device identifier of each target terminal by querying the member list of the temporary collaboration group. The process of obtaining the public key depends on the public key infrastructure system deployed by the hospital, which maintains the digital certificates and public key information of all medical devices. The first terminal sends a certificate query request to the Certificate Authority (CA) of the PKI system. The request contains the device identifier of the target terminal and the query timestamp. After receiving the query request, the CA system verifies the query permission of the first terminal to ensure that only authorized devices can obtain the certificate information of other devices. After successful verification, the CA system returns the digital certificate of the target terminal, which contains the device's RSA public key, certificate validity period, device attribute information, and the digital signature of the CA, etc. After receiving the certificate, the first terminal performs a series of verification operations, including verifying whether the digital signature of the certificate is correct, checking whether the certificate is within the validity period, querying the certificate revocation list to confirm that the certificate has not been revoked, etc. For each valid certificate, the first terminal extracts the RSA public key information. The public key contains two parameters, the modulus n and the public key exponent e. To improve the efficiency of subsequent encryption operations, the first terminal converts the extracted public key into an internal format suitable for encryption operations and establishes a mapping relationship table between the device identifier and the public key.

[0059] After obtaining the public key information of all terminals within the temporary collaboration group, the first terminal needs to generate an encrypted session key for each target terminal. The encryption process uses the RSA public key encryption algorithm and combines the optimal asymmetric encryption padding mode to ensure the security and anti-attack ability of encryption. For any target terminal within the temporary collaboration group, the first terminal first prepares the data packet to be encrypted. The data packet not only contains a 256-bit temporary session key but also contains metadata information of the key, such as key generation timestamp, validity period, key version number, and a 32-bit CRC checksum, etc.

[0060] The total length of the data packet is usually 320 bits and needs to be appropriately padded to meet the block size requirements of RSA encryption. The OAEP padding process first generates a random seed value with a length of 160 bits (20 bytes), and then uses the mask generation function (MGF1) to generate a mask based on the SHA-1 hash algorithm.

[0061] The length of the filled message matches the RSA key length, usually 2048 bits or 4096 bits. The RSA encryption process uses the fast modular exponentiation algorithm. After encryption, the first terminal formats the generated ciphertext and converts the binary ciphertext into a transmissible text format using Base64 encoding. The encryption session key for each target terminal is unique. Even if the temporary session keys are the same, due to the use of random seeds in OAEP padding, the encryption results for different terminals are completely different. This feature effectively prevents ciphertext analysis attacks. The encryption process also records detailed operation logs, including information such as encryption time, target terminal identifier, public key fingerprint used, and hash value of the encryption result, for subsequent auditing and troubleshooting. The entire encryption process is executed in a hardware security module to ensure that the temporary session key is not leaked or tampered with during the encryption process.

[0062] After generating personalized encryption session keys for each target terminal, the first terminal needs to securely send these encryption keys along with digital signatures to the corresponding terminals. The generation of digital signatures can ensure message integrity and authenticity. The first terminal first constructs a message digest to be signed, which contains key information such as the encryption session key, target terminal identifier, message timestamp, message sequence number, and first terminal identifier. The message digest is generated using the SHA-256 hash algorithm, producing a 256-bit hash value that can uniquely identify the content of the original message.

[0063] The digital signature process signs the message digest using the RSA private key of the first terminal. The signature formula of the signature algorithm is: , where S is the digital signature, H is the message hash value, d is the private key exponent of the first terminal, and n is the RSA modulus. To enhance the security of the signature, a random salt value is also added during the signature process to prevent signature forgery attacks.

[0064] After generating the digital signature, the first terminal constructs a complete key distribution message packet. This message packet is organized in JSON format and contains the following fields: target terminal identifier, encryption session key, digital signature, first terminal certificate, message timestamp, message type, and protocol version, etc. The message packet also adds a message integrity checksum, generated using the CRC32 algorithm, to detect data errors during transmission.

[0065] The sending process uses the hospital's internal secure communication network, usually a WiFi network or a wired Ethernet based on the 802.11 standard. To ensure the reliability of the transmission, the TCP protocol is adopted in the sending process. For each target terminal, the first terminal will establish an independent TCP connection and immediately send the corresponding key distribution message after the connection is established. The sending process also records detailed transmission logs, including information such as the sending time, target address, message size, network status, and transmission result. To prevent network attacks and eavesdropping, the transport layer also uses the TLS 1.3 protocol for additional encryption protection to ensure the security of the key distribution message during network transmission. The entire sending process realizes point-to-point secure communication. Each target terminal can only receive the session key encrypted specifically for it and cannot decrypt the key information of other terminals.

[0066] After receiving the key distribution message, the target terminal performs verification and decryption operations, and then returns a confirmation message to the first terminal to confirm the successful reception and correctness of the key. The target terminal first performs an integrity check on the received message packet to verify whether the CRC32 checksum is correct, ensuring that no errors occurred during the message transmission. Then it verifies the timestamp of the message to ensure that the message was sent within a reasonable time window and prevent replay attacks.

[0067] Next, it verifies the validity of the digital certificate of the first terminal, including steps such as certificate chain verification, validity period check, and certificate revocation status query. After the certificate verification passes, the target terminal extracts the public key of the first terminal and uses this public key to verify the correctness of the digital signature. The signature verification formula is: , where H' is the verified hash value, which is compared with the recalculated message hash value. If they are the same, it indicates that the signature is valid.

[0068] After the signature verification passes, the target terminal decrypts the encrypted session key using its own RSA private key. The decryption process first performs the RSA decryption operation, and then performs the OAEP de-padding operation to extract the original temporary session key and metadata information. After the decryption is completed, the target terminal will verify the CRC checksum of the key to ensure the correctness of the decryption result.

[0069] After verification, the target terminal calculates the verification value of the temporary session key. It performs a hash operation on the key using the SHA-256 hash algorithm to generate a 256-bit verification value. The calculation of the verification value also includes information such as the device identifier of the target terminal and the current timestamp, ensuring the uniqueness and non-forgeability of the verification value. The target terminal constructs a confirmation message containing information such as the device identifier, verification value, decryption status, and reception timestamp, and digitally signs the confirmation message using its own private key. The confirmation message uses a lightweight format to reduce network transmission overhead. When sending the confirmation message, the target terminal sets an appropriate priority to ensure that the confirmation message can reach the first terminal in a timely manner. The entire confirmation process implements two-way authentication for key distribution, not only verifying the identity and message integrity of the first terminal, but also proving to the first terminal the successful reception and correct decryption of the key.

[0070] After the first terminal receives the confirmation messages returned by all target terminals, it needs to perform a verification value consistency check to ensure the secure sharing of the temporary session key among all terminals. The verification value consistency check is the final confirmation step for the successful key distribution, ensuring that all terminals participating in the collaboration obtain the same temporary session key.

[0071] The first terminal first verifies each received confirmation message, including verifying the digital signature of the sending terminal, checking the reasonableness of the message timestamp, and confirming the correctness of the device identifier, etc. The signature verification process uses the public key of the corresponding terminal to ensure that the confirmation message indeed comes from the expected target terminal and has not been tampered with. After verification, the first terminal extracts the verification value from each confirmation message and performs a consistency comparison. Since all terminals use the same temporary session key and the same hash algorithm, in theory, all verification values should be exactly the same. The first terminal will calculate its own verification value as a benchmark and then compare the verification values of each target terminal one by one. The comparison process uses byte-level exact matching. If a situation where the verification values are inconsistent is found, the first terminal will analyze the reasons for the inconsistency, which may include network transmission errors, decryption failures, time synchronization problems, etc. For terminals with inconsistent verification values, the first terminal will regenerate and send the encrypted session key, retrying up to three times. If it is still inconsistent after retrying, the terminal will be removed from the temporary collaboration group and the corresponding error log will be recorded.

[0072] When the verification values of all terminals are consistent, the first terminal will generate a confirmation record of successful key distribution, including information such as the list of participating terminals, the key distribution time, the verification value, and the distribution status. This record will be encrypted and stored in the security log of the first terminal for subsequent auditing and troubleshooting. At the same time, the first terminal will send a notification message of key distribution completion to all target terminals, officially announcing the successful establishment of the encrypted communication channel. The notification message contains information such as the channel identifier, the validity period, and the list of participating terminals. After all terminals receive the notification, they will activate the encrypted communication function and start encrypting data transmission using the temporary session key. The entire verification process ensures the key consistency in a distributed environment, guaranteeing the security and reliability of data transmission during subsequent collaborative processing.

[0073] This embodiment constructs a highly secure key management scheme, providing a solid cryptographic foundation for multi-terminal collaborative processing. The device identification and public key acquisition mechanism ensure the authenticity of each terminal's identity and the credibility of the public key participating in the collaboration, effectively preventing identity forgery and man-in-the-middle attacks. The application of the digital signature mechanism ensures the integrity and non-repudiation of the key distribution message, and any tampering with the message can be detected in a timely manner. The confirmation mechanism of two-way authentication not only verifies the success of key distribution but also ensures the consistency of keys obtained by all terminals through verification value comparison, effectively preventing communication failures caused by key synchronization errors. The verification value consistency check mechanism provides the key correctness guarantee in a distributed environment, ensuring the reliability of subsequent encrypted communication. The retry and error handling mechanism enhances the fault tolerance of the system and can handle abnormal situations such as network instability and device failures. The entire key distribution process realizes end-to-end security protection, with corresponding security measures in each link from key generation to distribution verification, constructing a complete key management security system, providing a reliable technical guarantee for the secure transmission and collaborative processing of medical data.

[0074] In one implementation of this embodiment, the event correlation data includes continuous numerical parameters and discrete state parameters, and the event information also includes the event type and severity level. Based on the event correlation data and / or event information, a consensus event description is determined, including the following steps: S510. When the event correlation data is continuous numerical parameters, obtain the continuous numerical parameters collected by all terminals in the temporary collaboration group, and calculate the weighted average of all continuous numerical parameters, taking the weighted average as the consensus value; S520. Take the consensus value as the consensus event description; S530. When the event correlation data is discrete state parameters, obtain the discrete state parameters collected by all terminals in the temporary collaboration group, and use the majority voting method to take the discrete state parameter with the highest number of votes as the consensus event description; S540. When there are status values with the same number of votes, the status value of the terminal with the highest priority is used as the consensus event description.

[0075] In this embodiment, when the event-associated data contains both continuous numerical parameters and discrete status parameters, they are processed separately and then merged to form a complete consensus event description.

[0076] When processing continuous numerical parameters within the temporary collaboration group, it is first necessary to collect relevant numerical measurement data from all terminals participating in the collaboration. Continuous numerical parameters usually include the physiological indicators of patients, such as parameters that can be represented by specific numerical values, such as heart rate, blood pressure, body temperature, blood oxygen saturation, etc. In a hospital scenario, when a patient has an abnormal condition, multiple monitoring devices may simultaneously detect changes in relevant numerical values. For example, the bedside monitor detects a heart rate of 85 beats per minute, the wearable heart rate monitoring device detects a heart rate of 88 beats per minute, and the mobile nursing terminal obtains a heart rate of 86 beats per minute through manual measurement. To handle the numerical differences from different terminals, the method of weighted average is used to determine the final consensus value. The allocation of weights is preset. By this weighted average method, it is possible to effectively reduce the impact of the measurement errors of individual terminals on the final result, improve the accuracy and reliability of the data, and provide more accurate data support for subsequent medical decisions.

[0077] The weighted average calculated in step S510 is directly used as the consensus event description of the continuous parameter. The consensus value not only includes the numerical value itself but also needs to be appended with relevant metadata information, such as the measurement unit, confidence level, the number of terminals participating in the calculation, etc. In a specific implementation, the consensus event description is formatted into a standard data structure. The calculation of the confidence level is based on the weight distribution of the participating terminals and the degree of dispersion of the numerical values. When the measured values of each terminal are relatively close and the numerical values of high-weight terminals are dominant, the confidence level is relatively high. At the same time, the timestamp of the data is also recorded to ensure the time accuracy of the consensus event description. This structured description method not only facilitates the subsequent processing of the remote management platform but also can provide clear and accurate parameter information for medical staff. By simplifying the complex multi-source data fusion process into a single consensus value, the complexity of data processing is greatly reduced, while maintaining the integrity and traceability of the data, providing a reliable data basis for clinical decisions.

[0078] For the processing of discrete state parameters, the majority voting method is adopted to determine the final consensus event description. Discrete state parameters usually represent information with clear classifications such as device status, patient status, or environmental status, such as status values like "normal", or behavioral states like "in bed" and "out of bed". Within the ad-hoc collaboration group, each terminal will give corresponding status evaluations based on its own sensor data and algorithm judgments. For example, in the scenario of monitoring a patient's fall risk, the bedside sensor may judge it as "high risk", the wearable device judges it as "medium risk", and the environmental sensor judges it as "high risk". The implementation process of the majority voting method first counts the occurrence frequencies of each status value, and then selects the status value with the highest number of votes as the final consensus result. In the above example, "high risk" received 2 votes and "medium risk" received 1 vote, so "high risk" was selected as the consensus event description. Therefore, this solution can effectively handle the situation where multiple terminals have different judgments on the same event, improve the accuracy of judgment through collective wisdom, reduce the impact of misjudgments of individual terminals on the overall decision-making, and ensure that the final status description can reflect the consistent judgments of most terminals.

[0079] When there is a tie in the majority voting method, that is, two or more status values receive the same highest number of votes, the terminal priority mechanism needs to be used to break the tie. The determination of terminal priority is based on a comprehensive evaluation of multiple dimensions, including factors such as device type, accuracy level, deployment location, and historical reliability. In a hospital environment, different types of terminals have different levels of professionalism and reliability. For example, professional medical monitoring devices usually have a higher priority than general sensors, devices in the ICU have a higher priority than those in ordinary wards, and devices that have passed medical certification have a higher priority than ordinary Internet of Things devices. The calculation of the priority score uses a comprehensive scoring model: , where is the priority score of the i-th terminal, is the device type score, is the accuracy level score, is the location importance score, is the historical reliability score, to are the corresponding weight coefficients. When there is a tie, the status value provided by the terminal with the highest priority score will be automatically selected as the final consensus event description.

[0080] When the event-related data contains both continuous numerical parameters and discrete state parameters, the corresponding processing methods need to be applied separately, and then the results are combined to form a complete consensus event description.

[0081] This implementation method uses a weighted average method for continuous numerical parameters, fully considering the reliability and accuracy differences of different terminals, significantly improving the accuracy and stability of numerical data, and reducing the impact of single-point measurement errors on overall judgment. For discrete state parameters, a majority voting method combined with a priority mechanism is used to ensure that reasonable decisions can be made based on the professionalism of the equipment in the event of a tie. The classified processing and unified integration of mixed parameters realizes the effective fusion of different types of data and provides a complete technical solution for multi-dimensional event description in complex medical scenarios. It not only greatly reduces data redundancy and conflicts, but also reduces the processing burden of the remote management platform.

[0082] In one implementation of this embodiment, determining a leading reporting terminal in a temporary collaborative group includes the following steps: S610. Calculate the comprehensive score of each terminal in the temporary collaboration group according to the preset terminal priority rule; S620: The terminal with the highest comprehensive score is used as the leading reporting terminal.

[0083] Pre-set terminal prioritization rules cover multiple evaluation dimensions, including device performance, network connection quality, power status, historical reliability, and device type. Device performance evaluation primarily considers hardware metrics such as the terminal's processing power, memory capacity, and storage space, generating a performance benchmark score through standardized testing. Network connection quality evaluation includes network parameters such as signal strength, latency, packet loss rate, and bandwidth, which directly impact the reliability and real-time nature of data transmission. Power status evaluation considers factors such as battery charge level, charging status, and expected battery life to ensure the lead reporting terminal maintains stable operation throughout the incident handling process. Historical reliability evaluation is based on the terminal's past operational records, including historical performance metrics such as failure rate, data accuracy, and response time. Device type evaluation assigns different base scores based on the terminal's specialized features and functional characteristics; for example, specialized medical devices receive higher base scores than general-purpose sensors. The overall score is calculated using a weighted summation method, with weighting coefficients based on the actual needs of the hospital environment and empirical data. This multi-dimensional comprehensive evaluation objectively and accurately quantifies the overall capabilities and suitability of each terminal, providing a scientific basis for subsequent selection of the optimal lead reporting terminal.

[0084] The comprehensive scores of all terminals are sorted and compared, and the terminal with the highest score is identified as the candidate leading reporting terminal.

[0085] Through quantitative evaluation and weight assignment, this embodiment avoids the deviation of subjective judgment, and improves the objectivity and accuracy of the selection result. The selection strategy based on the highest score is simple and efficient, which can quickly determine the optimal leading reporting terminal, reducing the decision-making time and computational overhead. It effectively optimizes the efficiency and reliability of data transmission, and also reduces the energy consumption and resource consumption of the entire system by reducing redundant communication and repeated processing.

[0086] In one implementation of this embodiment, the leading reporting terminal encapsulates the consensus event description into a data packet and sends the data packet to the central control device, including the following steps: S710. The leading reporting terminal serializes the consensus event description into a standard data format, and adds the group identifier of the temporary cooperation group and the list of participating terminals to the standard data format to obtain the serialized data; S720. Encrypt the serialized data using the public key of the remote management platform to obtain the encrypted data payload; S730. Calculate the digital digest of the encrypted data payload, and sign the digital digest using the private key of the leading reporting terminal to obtain the digital signature; S740. Construct a data packet including the encrypted data payload and the digital signature, and send the data packet to the central control device.

[0087] The leading reporting terminal first converts the consensus event description into a standardized data format, which can ensure the correct transmission and parsing of data between different systems. The serialization uses the JSON format as the standard data format. On the basis of the standard data format, it is also necessary to add the metadata information of the temporary cooperation group, including the group identifier and the list of participating terminals. The group identifier is a unique identifier used to distinguish different cooperation groups, usually generated in the UUID format or a combination based on a timestamp and a random number. The list of participating terminals details all the terminal information participating in this collaborative processing, including the terminal ID, terminal type, data contribution degree, etc. This structured serialization method not only ensures the integrity and traceability of the data, but also provides rich context information for the subsequent processing of the remote management platform, facilitating data verification, auditing, and analysis.

[0088] Encrypt the serialized data using the public key of the remote management platform to ensure that only the remote management platform with the corresponding private key can decrypt and read the data content. In a specific implementation, the leading reporting terminal first needs to obtain the public key of the remote management platform, which is usually pre-configured into each terminal through a secure key distribution mechanism during the system initialization phase, or dynamically obtained through the PKI (Public Key Infrastructure) system.

[0089] Due to the low processing efficiency of asymmetric encryption algorithms (such as RSA) for large amounts of data, a hybrid encryption scheme is usually adopted in practical applications. The specific process is as follows: First, a random symmetric encryption key (such as an AES-256 key) is generated. This symmetric key is used to encrypt the serialized data, and then the public key of the remote management platform is used to encrypt the symmetric key. Assuming the serialized data is D, the randomly generated symmetric key is K, and the public key of the remote management platform is PK, the encryption process is as follows: Obtain the encrypted data , Obtain the encrypted key . The final encrypted data payload consists of two parts: . This hybrid encryption scheme not only ensures the security of the data but also improves the encryption efficiency. Necessary metadata such as encryption algorithm identification, key length, encryption timestamp, etc. are added during the encryption process to facilitate the correct decryption by the receiving party. Through this strong encryption mechanism, it is ensured that sensitive medical data will not be intercepted and interpreted by unauthorized third parties during transmission, meeting the strict requirements for medical data security and privacy protection.

[0090] Calculating the digital digest of the encrypted data payload and performing a digital signature can ensure data integrity and authentication. The digital digest is calculated using a secure hash algorithm such as SHA-256 or SHA-3, which converts the encrypted data payload of any length into a hash value of a fixed length.

[0091] After obtaining the digital digest, the private key of the leading reporting terminal is used to sign the digest to generate a digital signature. The digital signature is calculated using an asymmetric encryption algorithm such as RSA or ECDSA, and the signature process is as follows: , where is the private key of the leading reporting terminal. The digital signature can not only verify the integrity of the data but also confirm the source identity of the data, preventing the data from being tampered with or forged. In a hospital environment, each terminal has a unique digital certificate and key pair, and these key pairs are generated and distributed in a secure manner during device deployment. The digital signature generation process also includes timestamp information to prevent replay attacks. The complete signature structure includes metadata such as the signature value, signature algorithm identification, terminal certificate information, timestamp, etc. Through this digital signature mechanism, the remote management platform can verify whether the source of the data is a legitimate terminal device, ensuring the authenticity and credibility of the data, and providing a reliable data basis for subsequent medical decisions.

[0092] Finally, a data packet including an encrypted data payload and a digital signature is generated and sent to the central control device. The construction of the data packet requires organizing and encapsulating the encrypted data payload and the digital signature generated in the previous steps according to a predefined protocol format. The standard data packet structure adopts a hierarchical design, including three main parts: a header, a payload, and a checksum. The header contains meta-information of the data packet, such as version number, data packet type, length, source terminal ID, destination address, timestamp, etc. The payload part contains the encrypted data payload and the digital signature. The checksum part contains the checksum of the entire data packet, which is used to detect errors during transmission. The complete data packet is encoded in binary format to improve transmission efficiency and reduce bandwidth occupancy. The data packet is sent using a reliable transport protocol, such as TCP or a reliable transport protocol based on UDP, to ensure that the data can accurately reach the central control device. A retransmission mechanism is also implemented during the sending process. When a transmission failure or timeout is detected, the data will be automatically retransmitted, with a maximum of 3 retransmissions. After the sending is completed, the leading reporting terminal will wait for the confirmation response from the central control device, confirming that the data packet has been successfully received and processed. If the confirmation response is not received within the preset time, an exception handling process will be triggered, including measures such as resending, switching the network path, or sending to a backup central control device. Through this reliable data packet construction and sending mechanism, it is ensured that critical medical event data can be transmitted to the remote management platform in a timely and accurate manner, providing reliable data support for the rapid response and decision-making of medical staff.

[0093] In this embodiment, the digital signature mechanism effectively prevents data tampering and forgery, ensuring the integrity of the data and the credibility of the source, providing a reliable data basis for medical decision-making.

[0094] The embodiment of the present application also provides a multi-terminal collaborative processing method, which is applied to a central control device. The central control device is deployed with a remote management platform. The method includes: S810. In response to receiving the data packet sent by the leading reporting terminal, decrypt the data packet to obtain a consensus event description; S820. According to the consensus event description, obtain the event information of the event; S830. Import the event information into a preset event processing queue, and send a response confirmation message to the leading reporting terminal, where the response confirmation message includes a unique event ID and the processing status of the consensus event description.

[0095] After the central control device receives the data packet sent by the leading reporting terminal, it first needs to perform integrity verification and decryption on the data packet to obtain the original consensus event description. The data packet decryption process uses the reverse operation corresponding to the encryption process. First, it parses the structure of the data packet to extract key components such as the packet header information, encrypted data payload, and digital signature. Before decryption, it is necessary to verify the integrity and the legitimacy of the source of the data packet. The integrity verification is performed by calculating the checksum of the received data packet and comparing it with the checksum recorded in the packet header. If the two are inconsistent, it means that the data packet has been damaged or tampered with during transmission, and a retransmission needs to be requested. The source verification is performed through the digital signature, and the public key of the leading reporting terminal is used to verify the digital signature. If the verification passes, it means that the data indeed comes from a legitimate terminal device and has not been tampered with.

[0096] After the verification is completed, the decryption process begins. Since a hybrid encryption scheme is adopted, the decryption process is divided into two steps: First, use the private key of the central control device to decrypt the symmetric key; then use the decrypted symmetric key to decrypt the actual data. The data D obtained after decryption is the original serialized consensus event description. The decryption process also includes data format verification to ensure that the decrypted data conforms to the expected JSON format and data structure. If the decryption fails or the data format is incorrect, an exception handling process will be triggered, recording the error log and sending a decryption failure response message to the leading reporting terminal. Through this strict verification and decryption mechanism, it is ensured that only legitimate and complete data can be successfully decrypted and processed subsequently, effectively preventing malicious attacks and data pollution, and guaranteeing the security and reliability of medical data processing.

[0097] According to the consensus event description obtained by decryption, the central control device needs to extract and parse the event information contained therein to prepare for subsequent event processing. The consensus event description usually contains rich structured information, including data in multiple dimensions such as event type, parameter values, status information, timestamp, confidence level, and participating terminal information. The event information extraction process first parses the JSON-format consensus event description and extracts the values of each field according to a predefined data pattern. For example, extract the event type field from the consensus event description.

[0098] The extraction of parameter information includes numerical parameters and status parameters. Numerical parameters such as heart rate value, blood pressure value, body temperature value, etc., and status parameters such as patient consciousness state, device operation state, etc. The extraction of time information includes multiple timestamps such as the event occurrence time, data collection time, and processing time. The extracted event information will also be associated with historical data for analysis to identify whether it is a repeated event or a continuation of a related event.

[0099] Importing the extracted event information into a preset event processing queue can achieve orderly event processing and optimized resource allocation. The event processing queue adopts the data structure of a priority queue, and determines the processing priority according to factors such as the urgency of the event, the severity level, and the patient risk level. When the event information is imported into the queue, a unique event ID will be assigned, which is generated in the UUID format or based on a combination of a timestamp and a serial number to ensure global uniqueness. At the same time, metadata such as the creation time of the event, the expected processing time, and the allocated processing resources are recorded. The queue management module will dynamically adjust the processing order of the events according to the priority and resource availability to ensure that high-priority events can be processed in a timely manner. When the event is imported into the queue, the central control device will immediately send a response confirmation message to the leading reporting terminal to confirm that the data packet has been successfully received and processed. The response confirmation message contains information such as the unique event ID, the processing status, and the expected processing time. Through this orderly queue management and timely confirmation feedback mechanism, the efficiency and traceability of event processing are ensured, providing a strong guarantee for the quality and efficiency of medical services.

[0100] In this embodiment, the data packet verification and decryption mechanism ensures that only legal and complete data can enter the processing flow, effectively preventing security threats and data pollution, and guaranteeing the security and reliability of medical data processing. Comprehensive event information extraction and standardized processing ensure that data from different sources and in different formats can be uniformly processed and analyzed, improving the consistency and availability of the data. The intelligent priority queue management mechanism dynamically sorts according to the urgency and importance of the event, ensuring that critical medical events can be responded to and processed in a timely manner, maximizing the utilization efficiency of medical resources. The allocation and management of the unique event ID provide a basis for the full life cycle tracking of the event, facilitating event tracing, auditing, and statistical analysis. The timely response confirmation mechanism enables the terminal device to understand the data transmission and processing status in real time, improving the transparency and reliability of the system. The automation and standardization of the entire processing flow greatly reduce the need for manual intervention, improving the processing efficiency and accuracy. In a hospital environment, this technical solution can effectively integrate the collaborative data of multiple terminals.

[0101] In one implementation manner of this embodiment, after sending the response confirmation message to the leading reporting terminal, it further includes: S910. Trigger the corresponding diagnostic engine based on the consensus event description and output the diagnostic result.

[0102] Automatically select diagnostic algorithms and models by analyzing event characteristics. The triggering mechanism of the diagnostic engine first deeply analyzes the consensus event description and extracts key diagnostic features, including multi-dimensional information such as event type, parameter values, abnormal patterns, time characteristics, etc. According to these features, determine which diagnostic engine or engines should be activated through a preset rule engine or machine learning classifier. In a hospital environment, multiple specialized diagnostic engines are usually deployed, such as a cardiovascular disease diagnostic engine, a respiratory disease diagnostic engine, a neurological disease diagnostic engine, a fall risk assessment engine, etc., and each engine is optimized for a specific medical field.

[0103] The selection of the diagnostic engine adopts a multi-layer decision tree structure. First, it makes a rough classification according to the event type. For example, an event of the "cardiac_abnormality" type will trigger the cardiovascular diagnostic engine. On the basis of the rough classification, it further makes a fine classification according to specific parameter characteristics. For example, an abnormal heart rate may trigger an arrhythmia diagnosis sub-engine, and an abnormal blood pressure may trigger a hypertension diagnosis sub-engine. The activation process of the diagnostic engine includes steps such as model loading, parameter initialization, and data preprocessing. Model loading selects the corresponding diagnostic model from a pre-trained machine learning model library, and these models are usually trained based on a large amount of clinical data, including different types of algorithms such as deep neural networks, support vector machines, and random forests. Parameter initialization sets the initial parameters of the model according to the basic information (age, gender, medical history, etc.) of the current patient. Data preprocessing converts the raw data in the consensus event description into the standardized input format required by the diagnostic model, including operations such as numerical normalization, feature encoding, and missing value processing. The diagnostic engine also combines the patient's historical medical records for comprehensive analysis, identifies the disease development trend through time series analysis, and discovers potential complication risks through association rule mining. The entire triggering process adopts an asynchronous processing mechanism to avoid blocking the main event processing flow and ensure the real-time performance and response ability of the system.

[0104] After the diagnostic engine is successfully triggered, it starts to execute the pre-deployed diagnostic inference model and finally outputs a structured diagnostic result. The output diagnostic result contains information in multiple dimensions: main diagnosis, possible differential diagnoses, diagnostic confidence, recommended further examinations, recommended treatment plans, risk assessment, etc.

[0105] This embodiment effectively realizes a complete closed-loop from data collection to intelligent diagnosis by implementing an intelligent diagnostic engine triggering and diagnostic result output mechanism based on a consensus event description, significantly improving the intelligent level and diagnostic quality of medical services.

[0106] Refer to Figure 3 , this application embodiment also provides a multi-terminal collaborative processing system, including: The first terminal; At least one second terminal; A central control device, which is deployed with a remote management platform and is connected to the first terminal and at least one second terminal.

[0107] In this embodiment, the first terminal, the second terminal, and the central control device can be devices with a processor such as a tablet computer, a desktop computer, a laptop computer, a handheld computer, a wearable device, a notebook computer, an ultra-mobile personal computer (UMPC), a netbook, etc. Of course, the first terminal, the second terminal, and the central control device can also be servers. The specific forms of the first terminal, the second terminal, and the central control device are not particularly limited in the embodiments of the present application.

[0108] Those skilled in the art should understand that the embodiments of the present application can be provided as a method, a system, or a computer program product. Therefore, the present application can take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present application can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0109] The present application is described with reference to the flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each flow and / or block in the flowchart and / or block diagram, as well as the combination of flows and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing devices to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing devices generate a device for realizing the function specified in Figure 1 one process or multiple processes and / or blocks Figure 1 one block or multiple blocks.

[0110] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory generate a manufactured article including an instruction device, and the instruction device realizes the function specified in Figure 1 one process or multiple processes and / or blocks Figure 1 one block or multiple blocks.

[0111] These computer program instructions can also be loaded onto a computer or other programmable data processing device, so that a series of operation steps are executed on the computer or other programmable device to generate a computer-implemented process, and thus the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one process Figure 1 one process or multiple processes and / or blocks Figure 1 steps of the functions specified in one block or multiple blocks.

[0112] In a typical configuration, a computing device includes one or more processors (CPUs), an input / output interface, a network interface, and memory.

[0113] The memory may include non-permanent memory in the form of computer-readable media, random access memory (RAM) and / or non-volatile memory such as read-only memory (ROM) or flash memory (flash RAM). The memory is an example of computer-readable media.

[0114] Computer-readable media includes permanent and non-permanent, removable and non-removable media that can store information by any method or technology. The information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassette tapes, magnetic disk storage or other magnetic storage devices, or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transitory media such as modulated data signals and carrier waves.

[0115] It should also be noted that the term "comprising", "including" or any other variant thereof is intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements not only includes those elements, but also includes other elements not expressly listed, or also includes elements inherent to such process, method, commodity or device. Without further limitation, an element defined by the statement "including one..." does not exclude the existence of additional identical elements in the process, method, commodity or device including the element.

[0116] The above are only embodiments of the present application and are not intended to limit the present application. For those skilled in the art, various changes and modifications can be made to the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included within the scope of the claims of the present application.

Claims

1. A multi-terminal collaborative processing method, characterized in that, Applied to a first terminal, the first terminal is connected to a central control device, and a remote management platform is deployed on the central control device. The method includes: In response to a trigger signal of an event, determine the event information of the event, and initiate a collaborative processing request to at least one second terminal within the communication range. Among them, the event information includes an event summary with an initial timestamp, the collaborative processing request carries the event summary, and each second terminal is connected to the central control device and is used to determine whether to respond to the collaborative processing request; Determine a target terminal that responds to the collaborative processing request in the second terminal, and construct a temporary collaborative group including the target terminal; Obtain shared event-related data within the temporary collaborative group, and determine a consensus event description based on the event-related data and / or event information; Determine a leading reporting terminal in the temporary collaborative group. The leading reporting terminal is used to encapsulate the consensus event description into a data packet and send the data packet to the remote management platform; Receive a response confirmation message returned by the remote management platform, and broadcast the unique event ID and processing status in the response confirmation message to all terminals within the temporary collaborative group, so that all terminals can synchronously update the processing progress of the event.

2. The method according to claim 1, characterized in that Obtain shared event-related data within the temporary collaborative group, including: Establish an encrypted communication channel within the temporary collaborative group. The target terminal and the first terminal are used to send the collected event-related data to the temporary collaborative group through the encrypted communication channel; Obtain shared event-related data within the temporary collaborative group.

3. The method according to claim 2, characterized in that Establish an encrypted communication channel within the temporary collaborative group, including: Generate a temporary session key for the temporary collaborative group, and distribute the temporary session key to all terminals within the temporary collaborative group. Among them, each terminal within the temporary collaborative group is used to encrypt the collected event-related data through the temporary session key, and decrypt the event-related data shared by other terminals through the temporary session key.

4. The method according to claim 3, characterized in that, Distribute the temporary session key to all terminals within the temporary collaborative group, including: Obtain the device identifiers and public keys of all terminals within the temporary collaborative group; For any terminal within the temporary collaborative group, encrypt the temporary session key using the public key of the terminal to obtain an encrypted session key for the terminal; Send the encrypted session key and the digital signature of the first terminal to other terminals together; After sending the encrypted session key and the digital signature of the first terminal to other terminals, it further includes: Receive a confirmation message returned by other terminals. The confirmation message includes a verification value of the temporary session key obtained by other terminals after decrypting it with their private keys; When the verification values of all terminals are consistent, it is determined that the temporary session key is securely shared among all terminals.

5. The method according to claim 1, wherein The event-related data includes continuous numerical parameters and discrete status parameters, and the event information further includes an event type and a severity level. Determining a consensus event description based on the event-related data and / or event information includes: When the event-related data is continuous numerical parameters, obtain the continuous numerical parameters collected by all terminals within the temporary collaborative group, and calculate the weighted average of all continuous numerical parameters, and use the weighted average as the consensus value; Use the consensus value as the consensus event description; In the case where the event correlation data is discrete state parameters, obtain the discrete state parameters collected by all terminals within the temporary collaborative group, and use the majority voting method to take the discrete state parameter with the highest number of votes as the consensus event description; When there are state values with the same number of votes, take the state value of the terminal with the highest priority as the consensus event description.

6. The method according to claim 1, wherein Determine a leading reporting terminal in the temporary collaborative group, including: According to the preset terminal priority rules, calculate the comprehensive score of each terminal within the temporary collaborative group; Take the terminal with the highest comprehensive score as the leading reporting terminal.

7. The method according to claim 1, characterized in that The leading reporting terminal encapsulates the consensus event description into a data packet and sends the data packet to the central control device, including: The leading reporting terminal serializes the consensus event description into a standard data format, and adds the group identifier of the temporary collaborative group and the list of participating terminals to the standard data format to obtain the serialized data; Use the public key of the remote management platform to encrypt the serialized data to obtain the encrypted data payload; Calculate the digital digest of the encrypted data payload, and use the private key of the leading reporting terminal to sign the digital digest to obtain the digital signature; Construct a data packet including the encrypted data payload and the digital signature, and send the data packet to the central control device.

8. A multi-terminal collaborative processing method, characterized in that: Applied to the central control device, the central control device is deployed with a remote management platform, and the method includes: In response to receiving the data packet sent by the leading reporting terminal, decrypt the data packet to obtain the consensus event description; According to the consensus event description, obtain the event information of the event; Import the event information into the preset event processing queue, and send a response confirmation message to the leading reporting terminal, where the response confirmation message includes a unique event ID and the processing status of the consensus event description.

9. The method according to claim 8, characterized in that After sending the response confirmation message to the leading reporting terminal, it further includes: Based on the consensus event description, trigger the corresponding diagnostic engine and output the diagnostic result.

10. A multi-terminal collaborative processing system, characterized in that: Including: The first terminal is used to execute the multi-terminal collaborative processing method according to any one of claims 1 to 7; At least one second terminal; The central control device is deployed with a remote management platform and is connected to the first terminal and at least one second terminal, and is used to execute the multi-terminal collaborative processing method according to any one of claims 8 to 9.

Citation Information

Patent Citations

  • Intelligent home authentication method based on eUICC

    CN110995710A

  • Event sending implementation system and method for Wi-Fi equipment

    CN111885598A

  • Unmanned aerial vehicle cluster node authentication method and device, storage medium and processor

    CN113225736A

  • Multi-party signature collection scheme based on Hyperledger-fabric

    CN114091113A

  • Equipment operation management method and device, equipment and storage medium

    CN114896751A

Cited By

  • Power station material management method based on linkage of Internet of Things system and ERP system

    CN121151430A

  • Dynamic workflow collaboration method and related equipment

    CN121193754A

  • Emergency state communication method and system of law enforcement recorder

    CN121218236A

  • An emergency communication method and system for law enforcement recorders

    CN121218236B