A multi-terminal cooperative processing method and system

Abstract

The application discloses a multi-terminal cooperative processing method and system, and relates to the field of terminal communication. The method comprises the following steps: in response to a trigger signal of an event, determining event information, and initiating a cooperative processing request to at least one second terminal within a communication range; determining a target terminal responding to the cooperative processing request in the second terminal, and constructing a temporary cooperative group comprising the target terminal; obtaining shared event-related data in the temporary cooperative group, and determining a consensus event description based on the event-related data and / or the event information; determining a leading reporting terminal in the temporary cooperative group, the leading reporting terminal being used for encapsulating the consensus event description into a data packet, and sending the data packet to a remote management platform; receiving a response confirmation message returned by the remote management platform, and broadcasting a unique event ID and a processing state in the response confirmation message to all terminals in the temporary cooperative group. The application can effectively reduce the consumption of computing resources of the remote management platform.

Description

TECHNICAL FIELD

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

[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 real-time physiological data, behavior information, and environmental parameters of patients, 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 abnormal fluctuations in a patient's vital signs or preliminary signs of a sudden public health event in a specific area, each relevant terminal usually independently reports its perceived raw data or preliminary processed data to a remote management platform or central server. The remote management platform is responsible for aggregating, analyzing, storing, and decision support for the received data.

[0004] However, in many cases, especially when multiple terminals simultaneously perceive data that may point to the same potential event, for example, in a patient's room, multiple sensors worn by the patient (such as heart rate, blood oxygen, and body temperature sensors) and bedside monitors may simultaneously detect abnormal vital signs of the patient. If these devices independently report their respective raw data or simply processed data to the remote management platform concurrently, it will result in a large number of redundant and possibly conflicting data being reported by multiple terminals to the remote management platform for the same event, and the remote management platform needs to process a large amount of repetitive data, which severely consumes computing resources and further increases the communication and processing burden of the remote management platform. SUMMARY

[0005] Embodiments of the present application provide a multi-terminal cooperative processing method and system to effectively reduce redundant reporting and reduce the computing resource consumption of the remote management platform, thereby reducing the communication and processing burden of the remote management platform.

[0006] To achieve the above-mentioned purpose, the embodiments of the present application adopt the following technical solutions:

[0007] In a first aspect, a multi-terminal cooperative processing method is provided, applied to a first terminal, the first terminal being connected with a central control device, the central control device being deployed with a remote management platform, and the method comprising:

[0008] In response to the trigger signal of the event, event information of the event is determined, and a collaborative processing request is initiated to at least one second terminal within a communication range, wherein the event information includes an event summary of an initial timestamp, the collaborative processing request carries the event summary, each second terminal is connected with the central control device and is configured to determine whether to respond to the collaborative processing request;

[0009] A target terminal responding to the collaborative processing request is determined in the second terminal, and a temporary collaborative group including the target terminal is constructed;

[0010] Event association data shared in the temporary collaborative group is obtained, and a consensus event description is determined based on the event association data and / or the event information;

[0011] A leading reporting terminal is determined in the temporary collaborative group, and the leading reporting terminal is configured to encapsulate the consensus event description into a data packet and send the data packet to a remote management platform;

[0012] A response confirmation message returned by the remote management platform is received, and a unique event ID and a processing status in the response confirmation message are broadcasted to all terminals in the temporary collaborative group, so that all terminals synchronously update a processing progress of the event.

[0013] In a possible implementation manner of the first aspect, the event association data shared in the temporary collaborative group is obtained, including:

[0014] An encrypted communication channel is established in the temporary collaborative group, and the target terminal and the first terminal are configured to send the collected event association data to the temporary collaborative group through the encrypted communication channel;

[0015] The event association data shared in the temporary collaborative group is obtained.

[0016] In another possible implementation manner of the first aspect, the encrypted communication channel is established in the temporary collaborative group, including:

[0017] A temporary session key of the temporary collaborative group is generated, and the temporary session key is distributed to all terminals in the temporary collaborative group, wherein each terminal in the temporary collaborative group is configured to encrypt the collected event association data through the temporary session key, and decrypt the event association data shared by other terminals through the temporary session key.

[0018] In another possible implementation manner of the first aspect, the temporary session key is distributed to all terminals in the temporary collaborative group, including:

[0019] Device identifiers and public keys of all terminals in the temporary collaborative group are obtained;

[0020] encrypting the temporary session key by using the public key of the terminal to obtain an encrypted session key for the terminal;

[0021] sending the encrypted session key and the digital signature of the first terminal to the other terminals;

[0022] after sending the encrypted session key and the digital signature of the first terminal to the other terminals, further comprising:

[0023] receiving a confirmation message returned by the other terminals, wherein the confirmation message comprises a check value of the temporary session key obtained by decrypting the temporary session key by using the private key of the other terminals;

[0024] in a case where the check values of all the terminals are consistent, determining that the temporary session key is securely shared among all the terminals.

[0025] In a possible implementation of the first aspect, the event-related data comprises continuous numerical parameters and discrete state parameters, and the event information further comprises an event type and a severity level, and the consensus event description is determined based on the event-related data and / or the event information, and the determining comprises:

[0026] in a case where the event-related data is continuous numerical parameters, obtaining the continuous numerical parameters collected by all the terminals in the temporary cooperative group, and calculating a weighted average value of all the continuous numerical parameters, and taking the weighted average value as the consensus value;

[0027] taking the consensus value as the consensus event description;

[0028] in a case where the event-related data is discrete state parameters, obtaining the discrete state parameters collected by all the terminals in the temporary cooperative group, and taking the discrete state parameter with the highest number of votes as the consensus event description by using a majority voting method;

[0029] in a case where there are state values with the same number of votes, taking the state value of the terminal with the highest priority as the consensus event description.

[0030] In a possible implementation of the first aspect, a dominant reporting terminal is determined in the temporary cooperative group, and the determining comprises:

[0031] calculating a comprehensive score of each terminal in the temporary cooperative group according to a preset terminal priority rule;

[0032] taking the terminal with the highest comprehensive score as the dominant reporting terminal.

[0033] In a 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, and the encapsulating and sending comprise:

[0034] The leading reporting terminal serializes the consensus event description into a standard data format, and adds a group identifier of the temporary coordination group and a list of participating terminals in the standard data format, to obtain serialized data;

[0035] The serialized data is encrypted using a public key of the remote management platform, to obtain encrypted data payload;

[0036] A digital digest of the encrypted data payload is calculated, and the digital digest is signed using a private key of the leading reporting terminal, to obtain a digital signature;

[0037] A data packet including the encrypted data payload and the digital signature is constructed, and the data packet is sent to the central control device.

[0038] In a second aspect, the application provides a multi-terminal cooperative processing method, applied to a central control device, wherein the central control device is deployed with a remote management platform, and the method comprises:

[0039] In response to receiving the data packet sent by the leading reporting terminal, the data packet is decrypted to obtain a consensus event description;

[0040] According to the consensus event description, event information of the event is obtained;

[0041] The event information is imported into a preset event processing queue, and a response confirmation message is sent to the leading reporting terminal, wherein the response confirmation message includes a unique event ID and a processing status of the consensus event description.

[0042] In a possible implementation manner of the second aspect, after the response confirmation message is sent to the leading reporting terminal, the method further comprises:

[0043] Based on the consensus event description, a corresponding diagnostic engine is triggered, and a diagnostic result is output.

[0044] In a third aspect, the application provides a multi-terminal cooperative processing system, comprising:

[0045] A first terminal;

[0046] At least one second terminal;

[0047] A central control device, which is deployed with a remote management platform, and is connected with the first terminal and the at least one second terminal.

[0048] Through the technical solution, the key problems of multiple device repeated reporting, data redundancy and resource waste in the traditional hospital terminal system are effectively solved. Through the establishment of an intelligent terminal coordination mechanism, when a medical event occurs, related terminals can automatically organize to form a temporary coordination group, and through safe data sharing and consensus algorithm, the dispersed monitoring data is fused into unified and accurate event description, which significantly improves the data quality and reliability of event judgment. The unified reporting mechanism integrates multiple concurrent data streams that may be generated into a single high-quality data packet, significantly reducing network bandwidth occupation and the processing burden of the remote management platform, and the overall performance of the system is significantly improved. The application of encryption communication and digital signature technology 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 coordination strategy according to the actual situation, improving the adaptability and scalability of the system. The real-time state synchronization and feedback mechanism forms a complete event processing closed loop, enabling medical staff to timely understand patient conditions and system response, providing reliable technical support for clinical decision-making, and ultimately improving the quality and efficiency of medical services.

[0049] Other features and advantages of the embodiments of the present application will be described in detail in the subsequent specific embodiments section. BRIEF DESCRIPTION OF DRAWINGS

[0050] Figure 1 A flowchart of a multi-terminal cooperative processing method provided by an embodiment of the present application;

[0051] Figure 2 A signaling flow diagram of a multi-terminal cooperative processing method provided by an embodiment of the present application;

[0052] Figure 3 A structural diagram of a multi-terminal cooperative processing system provided by an embodiment of the present application. DETAILED DESCRIPTION

[0053] In order to make the purpose, technical scheme and advantages of the embodiments of the present application clearer, the technical scheme in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. It should be understood that the specific embodiments described herein are only used to illustrate and explain the embodiments of the present application, and are not used to limit the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative labor are within the scope of protection of the present application.

[0054] It should be noted that if the application embodiments involve directionality indication (such as up, down, left, right, front, back, …), the directionality indication is only used to explain the relative position relationship, motion condition, etc. between components in a certain posture (as shown in the drawings), and if the certain posture changes, the directionality indication also changes accordingly.

[0055] In addition, if the application embodiments involve "first", "second" and the like, the "first", "second" and the like are only for description purposes, and cannot be understood as indicating or implying the relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features limited by "first", "second" can be explicitly or implicitly included at least one of the features. In addition, the technical solutions of each embodiment can be combined with each other, but it must be based on the realization of ordinary skilled in the art, when the combination of technical solutions appears contradictory or unachievable, it should be considered that the combination of technical solutions does not exist, nor within the scope of protection claimed in the present application.

[0056] Figure 1 The flowchart of a multi-terminal cooperative processing method according to an embodiment of the application is schematically shown. As shown in Figure 1 The application embodiment provides a multi-terminal cooperative processing method, which is applied to a first terminal, the first terminal is connected with a central control device, the central control device is deployed with a remote management platform, and the method can include the following steps.

[0057] S110, in response to the trigger signal of the event, determining the event information of the event, and initiating a cooperative processing request to at least one second terminal within the communication range, wherein the event information includes an initial timestamp event summary, the cooperative processing request carries the event summary, each second terminal is connected with the central control device, and is used to determine whether to respond to the cooperative processing request;

[0058] S120, determining a target terminal in the second terminal that responds to the cooperative processing request, and constructing a temporary cooperative group including the target terminal;

[0059] S130, obtaining shared event association data in the temporary cooperative group, and determining a consensus event description based on the event association data and / or the event information;

[0060] S140, determining a leading reporting terminal in the temporary cooperative 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;

[0061] S150, receiving the response confirmation message returned by the remote management platform, and broadcasting the unique event ID and the processing status in the response confirmation message to all terminals in the temporary cooperative group, so as to synchronize the processing progress of all terminals.

[0062] Referring to Figure 2 In a hospital environment, the first terminal serves as a medical monitoring device, continuously monitoring physiological parameters of a patient or environmental conditions. When an abnormal situation is detected, such as a patient's heart rate exceeding a preset threshold or blood oxygen saturation being below a safe range, an event detection algorithm built into the first terminal immediately triggers an event signal. The event detection mechanism uses a combination of multi-layer threshold judgment and trend analysis. First, a sliding window algorithm is used to smooth the continuously collected data, and then the data is compared with a preset normal range. When the data deviates from the normal range by more than a set number of standard deviations, a preliminary alarm is triggered; when multiple consecutive sampling points exceed the threshold or show a dangerous trend, an event signal is triggered.

[0063] If an event is triggered, the first terminal will immediately generate an event summary containing an initial timestamp to ensure accurate time synchronization in a distributed environment. The event summary contains key information such as event type identification, severity level assessment, trigger parameter value, and first terminal device identification. The first terminal broadcasts a cooperative processing request to all second terminals within its communication range through a 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 cooperative processing request uses a lightweight message format to carry the core information of the event summary, reducing network transmission overhead. Each second terminal that receives the request will determine whether to respond to the cooperative processing request based on its device type, current working state, and relevance to the event. This mechanism of actively initiating cooperation effectively avoids false positives by a single device and lays the foundation for subsequent data fusion and consensus.

[0064] After the cooperative processing request is sent out, the second terminals within the communication range will decide whether to participate in cooperative processing according to the preset response strategy. The response strategy is based on multi-dimensional evaluation, including the relevance of the device to the event, the current workload of the device, the battery power state, and the network connection quality. Relevance assessment 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 blood pressure meters have a higher relevance, while environmental sensors have a relatively lower relevance. Each second terminal will use a weighted scoring algorithm to calculate its response priority score. When the second terminal's score exceeds a preset threshold, it will send a response confirmation message to the first terminal, indicating its willingness to participate in cooperative processing.

[0065] After collecting all the response confirmation messages, the first terminal filters out the most suitable target terminals from the responding second terminals. Once the target terminals are determined, the first terminal sends a group construction confirmation message to all the selected target terminals to officially establish the temporary collaborative group. Each terminal in the group obtains a temporary group identifier for subsequent group communication and data synchronization. This dynamic group construction mechanism ensures that the size of the collaborative group is moderate, providing sufficient data support without increasing communication complexity due to excessive devices.

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

[0067] Data sharing uses a publish-subscribe mode, where each terminal is both a data publisher and a data subscriber for other terminals. 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 weight is determined based on the device's accuracy level and reliability evaluation. For discrete state parameters, a majority voting mechanism is used, and when there is an equal number of votes, the judgment result of the terminal with the highest priority is preferred.

[0068] After forming a consensus event description, the temporary collaborative group needs to determine a dominant reporting terminal to be responsible for communication with the remote management platform. The selection of the dominant terminal is based on a comprehensive scoring mechanism, including device computing power, network connection stability, battery level, historical reporting success rate, and device authority level, among other dimensions. The terminal with the highest score is selected as the dominant reporting terminal, which is responsible for data packaging and reporting.

[0069] The leading reporting terminal first standardizes and serializes the consensus event description, organizes the data structure in JSON format, and includes the complete description information of the event, the list of terminals participating in collaboration, the group identifier, and the data integrity verification code, etc. To ensure the security of data transmission, the leading terminal encrypts the serialized data using the public key of the remote management platform to generate encrypted data payload. At the same time, the SHA-256 hash digest of the encrypted data is calculated, and the private key of the terminal is used to digitally sign the digest to ensure the data's non-tamperability and source authentication. The final data packet includes encrypted payload, digital signature, timestamp, and transmission protocol header information. The data packet is sent to the central control device through the hospital's secure network channel, and the transmission process uses reliable TCP protocol, with retransmission mechanism and timeout processing to ensure that the data can accurately reach the remote management platform. This unified reporting mechanism effectively avoids the problem of multiple terminals sending duplicate data to the platform at the same time, significantly reducing network bandwidth occupation and platform processing burden.

[0070] After receiving the data packet sent by the leading reporting terminal, the remote management platform performs a series of verification and processing operations. First, verify the validity of the digital signature to confirm the credibility of the data source and the integrity of the data content. Then use the platform's private key to decrypt the data payload 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 based on the event type and severity, adding the event information to the corresponding processing queue. The processing status includes "received", "processing", "analyzed", "manual intervention" and other levels, reflecting the progress of the event in the platform. The platform generates a response confirmation message containing the unique event ID, current processing status, estimated processing time, and possible preliminary suggestions. The response message is returned to the leading reporting terminal through a secure channel, and the leading terminal receives the response and immediately broadcasts the key information to all member terminals in the temporary collaboration group. The broadcast process uses multicast to ensure that all participating terminals can synchronize the event processing progress updates.

[0071] After receiving the update information, each terminal updates the corresponding record in the locally maintained event status table, including event ID, processing status, update time, etc. This state synchronization mechanism enables all terminals in the group to keep abreast of the event processing, providing support for subsequent collaborative operations or status inquiries. At the same time, the terminal adjusts its monitoring strategy according to the change of processing status, for example, after the event is properly handled, the monitoring frequency can be appropriately reduced to save power resources. The entire feedback mechanism forms a complete closed loop from event occurrence to completion, ensuring the reliability and response efficiency of the medical monitoring system.

[0072] The embodiment effectively solves the key problems of multiple device repeated reporting, data redundancy and resource waste in traditional hospital terminal system. Through the establishment of an intelligent terminal coordination mechanism, when a medical event occurs, the relevant terminals can automatically organize to form a temporary coordination group, and through safe data sharing and consensus algorithm, the dispersed monitoring data is fused into a unified and accurate event description, which significantly improves the data quality and the reliability of event judgment. The unified reporting mechanism integrates multiple concurrent data streams into a single high-quality data packet, significantly reducing the network bandwidth occupation and the processing burden of the remote management platform, and the overall performance of the system is significantly improved. The application of encryption communication and digital signature technology 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 coordination strategy according to the actual situation, improving the adaptability and scalability of the system. The real-time state synchronization and feedback mechanism forms a complete event processing closed loop, enabling medical staff to timely understand the patient's condition and system response, providing reliable technical support for clinical decision-making, and ultimately improving the quality and efficiency of medical services.

[0073] In one embodiment of the present embodiment, the shared event-related data obtained in the temporary coordination group includes the following steps:

[0074] S210, an encrypted communication channel is established in the temporary coordination group, and the target terminal and the first terminal are used to send the collected event-related data to the temporary coordination group through the encrypted communication channel;

[0075] S220, obtaining shared event-related data in the temporary coordination group.

[0076] After the establishment of the temporary coordination group, in order to ensure the security and privacy protection of medical data during transmission, a secure and reliable encrypted communication channel needs to be established in 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 ensures the communication efficiency.

[0077] Firstly, the first terminal as the initiator and coordinator of the coordination group is responsible for generating a temporary session key. The session key is generated by AES-256 standard, with a key length of 256 bits, and a high-entropy random seed is generated by a hardware random number generator to ensure the unpredictability and uniqueness of the key. The key generation process also combines 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 length of the event processing period, which not only ensures the continuity of data transmission, but also avoids the security risks brought by long-term use of the same key.

[0078] The key distribution process adopts a public key infrastructure system. The first terminal first obtains the digital certificates and public key information of all target terminals in the temporary collaborative group from the hospital's device certificate management center. For each target terminal in the group, the first terminal encrypts the temporary session key using the RSA public key of the terminal to generate an individual encrypted key package for the terminal. The encryption process uses the OAEP padding mode to enhance encryption strength and prevent chosen ciphertext attacks. The encrypted key package is sent to the corresponding target terminal through a secure channel along with the digital signature of the first terminal.

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

[0080] After the secure encrypted communication channel is established, each terminal in the temporary collaborative group begins to share event-related data through the channel. The event-related data acquisition process adopts a distributed data collection and synchronization mechanism to ensure that all terminals in the group can obtain complete and consistent data sets. 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 heart rate, heart rhythm, and ST segment changes are collected; blood oxygen monitors provide oxygen saturation, pulse rate, and blood perfusion index parameters; blood pressure monitoring devices record systolic pressure, diastolic pressure, and mean arterial pressure hemodynamic indicators. For environmental monitoring devices, environmental parameters such as temperature, humidity, air quality, and noise level in the ward are collected. All collected data is labeled with precise timestamps and synchronized using the Network Time Protocol (NTP) to ensure consistency in the time dimension of data collected by different devices.

[0081] After data collection, each terminal will preprocess the data, including outlier detection, noise filtering, and data format standardization. The preprocessed data is encrypted using a temporary session key and a message authentication code (MAC) to ensure data integrity and authenticity. 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, with an acknowledgement mechanism and retransmission strategy to ensure accurate data delivery. The first terminal acts as a data aggregation node, responsible for receiving, decrypting, and organizing event-related data from various target terminals. The received encrypted data is first verified by MAC to confirm that it has not been tampered with during transmission, then decrypted using the temporary session key to restore the original event-related data. The decrypted data is sorted and aligned by timestamp to form a time series data set.

[0082] To handle potential data conflicts or inconsistencies, a data fusion algorithm is used to process similar data from different terminals. For numerical data, a weighted average or median filter is used to obtain more reliable data values; for state-type data, a majority vote or expert system is used to determine the final state judgment. The entire data acquisition process achieves distributed, secure, and efficient data sharing, providing a complete and reliable data foundation for subsequent consensus event description generation, while ensuring the privacy and security of medical data through encryption protection.

[0083] This embodiment 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 an encrypted communication channel combines the efficiency of AES-256 symmetric encryption and the security of RSA asymmetric encryption, ensuring the absolute security of medical data transmission while ensuring communication efficiency. The dynamic generation and secure distribution mechanism of the temporary session key effectively prevents key leakage and replay attacks, meeting the strict requirements of the medical industry for data security. The distributed data collection and synchronization mechanism ensures that all terminals in the temporary collaborative group have complete and consistent event-related data, avoiding the incomplete information problem caused by data silos in traditional systems. The application of data preprocessing and fusion algorithms improves data quality, ensuring the accuracy of subsequent analysis through outlier detection and noise filtering. The time synchronization mechanism ensures the consistency of data from different devices in the time dimension, providing a foundation for accurate event reconstruction and analysis. The entire data sharing process achieves end-to-end security protection, with corresponding security measures at every link from data collection to data aggregation, building a complete data security protection system and providing a solid technical guarantee for the reliable operation of the medical monitoring system.

[0084] In one of the embodiments of the present embodiment, an encrypted communication channel is established in the temporary collaborative group, including the following steps:

[0085] S310, generating a temporary session key of the temporary collaborative group, and distributing the temporary session key to all terminals in the temporary collaborative group, wherein each terminal in the temporary collaborative group is configured to encrypt the collected event-related data by the temporary session key, and decrypt the event-related data shared by other terminals by the temporary session key.

[0086] The generation of the temporary session key is the core link of establishing a secure encrypted communication channel, and its security directly determines the confidentiality of data transmission in the entire collaborative group. The key generation process adopts a cryptographically secure pseudo-random number generator combined with 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 is mixed and processed by SHA-256 hash function to generate a 256-bit seed value.

[0087] The seed value is then input into the key derivation function based on the AES algorithm, and the PBKDF2 standard is used for key expansion, with an iteration number of more than 10000 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 long, meeting the requirements of the AES-256 encryption standard, and has enough key space to resist current and foreseeable future cryptographic attacks. In order to enhance the timeliness and security of the key, the session key will also be combined with the event lifecycle to set the validity period, which is usually set to 1.5 times the expected event processing time, which ensures the effectiveness of the key during collaborative processing, and avoids the security risks brought by long-term use of the same key. After the key generation is completed, the first terminal will calculate the checksum of the key, and generate a 32-bit checksum using the CRC32 algorithm, which is used for subsequent verification of the correctness of the key distribution. The entire key generation process is completed in a trusted execution environment to ensure that the key cannot be obtained by malicious software or attackers during the generation process. The generated key is temporarily stored in the secure storage area of the device, which is protected by hardware-level encryption, and only authorized encryption and decryption modules can access it.

[0088] The key distribution process adopts a secure distribution mechanism based on public key cryptography to ensure that the temporary session key can be securely delivered 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 in the group. These certificates are usually stored in the hospital's public key infrastructure system, containing the RSA public key of each device, the certificate validity period, the device identifier, and the digital signature, etc. The first terminal obtains the corresponding digital certificate by using the device identifier of the target terminal as the query condition through a secure certificate query interface. After obtaining the certificate, the first terminal verifies the validity of the certificate, including checking whether the certificate is within the valid period, whether the certificate chain is complete, and whether the certificate is revoked, etc. After verification, the RSA public key of the target terminal is extracted from the certificate.

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

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

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

[0092] After decryption, the target terminal verifies the checksum of the session key to ensure that the key has not been corrupted during transmission. After verification, the target terminal stores the temporary session key in a local secure storage area and sets the corresponding validity period. To confirm the success of key distribution, the target terminal generates an acknowledgment message containing the key's hash value, reception timestamp, and device identification, and signs it with its own private key before sending it back to the first terminal. After receiving all target terminal acknowledgment messages, the first terminal verifies the signature and key hash value of each acknowledgment message. Only when all terminals have successfully received and verified the session key is the encrypted communication channel considered successfully established.

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

[0094] Encrypted data includes ciphertext, IV, and message authentication code (MAC), among other parts. 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 extracted IV for decryption.

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

[0096] The embodiment constructs a highly secure, efficient and reliable encrypted 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, ensuring the high randomness and unpredictability of the generated key, effectively resisting various cryptographic attacks. The secure distribution mechanism based on public key cryptography enables secure transmission of the key, ensuring that the key 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 symmetric encryption algorithm AES-256 ensures high security while also ensuring 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, improving the security level of the entire system. The entire encrypted communication mechanism realizes end-to-end data protection, with corresponding security guarantees throughout the entire process from data generation to data consumption, building a complete data security protection system and providing reliable technical support for secure sharing and collaborative processing of medical data.

[0097] In one embodiment of the present embodiment, the temporary session key is distributed to all terminals in the temporary collaborative group, including the following steps:

[0098] S410, obtaining the device identifier and public key of all terminals in the temporary collaborative group;

[0099] S420, for any one terminal in the temporary collaborative group, encrypting the temporary session key using the public key of the terminal to obtain an encrypted session key for the terminal;

[0100] S430, sending the encrypted session key and the digital signature of the first terminal to the other terminals;

[0101] S440, after sending the encrypted session key and the digital signature of the first terminal to the other terminals, further comprising:

[0102] S450, receiving the confirmation message returned by the other terminals, wherein the confirmation message includes the verification value of the temporary session key obtained by the other terminals using their private keys;

[0103] S460, in the case where the verification values of all terminals are consistent, determining that the temporary session key is securely shared among all terminals.

[0104] After the temporary collaboration group is established, the first terminal needs to obtain the device identifier and public key information of all target terminals in the group, which is a prerequisite for secure key distribution. The process of obtaining the device identifier is based on the device management system within the hospital. Each medical terminal will be registered in the device registration center when deployed 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.

[0105] The first terminal obtains the complete device identifier of each target terminal by querying the member list of the temporary collaboration group. The public key acquisition process relies on the public key infrastructure system deployed by the hospital, which maintains the digital certificate 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, which contains the device identifier of the target terminal and the query timestamp. After receiving the query request, the CA system verifies the query authority of the first terminal to ensure that only authorized devices can obtain the certificate information of other devices. After verification, the CA system returns the digital certificate of the target terminal, which contains the RSA public key of the device, the certificate validity period, the device attribute information, and the digital signature of the CA. After receiving the certificate, the first terminal performs a series of verification operations, including verifying the correctness of the digital signature, checking whether the certificate is within the valid period, and querying the certificate revocation list to confirm that the certificate has not been revoked. For each valid certificate, the first terminal extracts the RSA public key information, which includes 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 to an internal format suitable for encryption operations and establishes a mapping table between the device identifier and the public key.

[0106] After obtaining the public key information of all terminals in 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 combined with the optimal asymmetric encryption padding mode to ensure the security and attack resistance of encryption. For any target terminal in the temporary collaboration group, the first terminal first prepares a data packet to be encrypted, which contains not only a 256-bit temporary session key but also metadata information such as key generation timestamp, validity period, key version number, and 32-bit CRC check code.

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

[0108] The length of the filled message matches the RSA key length, usually 2048 bits or 4096 bits. The RSA encryption process uses the fast exponentiation algorithm. After encryption is complete, the first terminal will format the generated ciphertext, using Base64 encoding to convert binary ciphertext into a transmissible text format. Each target terminal's encryption session key is unique, even if the temporary session key is the same, since a random seed is used in the OAEP padding, the encryption results of different terminals are completely different, which effectively prevents ciphertext analysis attacks. The encryption process also records detailed operation logs, including encryption time, target terminal identification, public key fingerprint used, and encryption result hash value, etc. information for subsequent audit and troubleshooting. The entire encryption process is executed in the hardware security module, ensuring that the temporary session key will not be leaked or tampered with during the encryption process.

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

[0110] The digital signature process uses the first terminal's RSA private key to sign the message digest, and 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. In order to enhance the security of the signature, the signature process will also add a random salt value to prevent signature forgery attacks.

[0111] After generating the digital signature, the first terminal constructs the complete key distribution message package, which uses the JSON format to organize and contains the following fields: target terminal identification, encryption session key, digital signature, first terminal certificate, message timestamp, message type, and protocol version, etc. The message package also adds a message integrity check code, which is generated using the CRC32 algorithm, to detect data errors during transmission.

[0112] The sending process uses the hospital's internal secure communication network, usually based on WiFi networks or wired Ethernet networks based on the 802.11 standard. To ensure the reliability of transmission, the sending process uses the TCP protocol. For each target terminal, the first terminal will establish an independent TCP connection and send the corresponding key distribution message immediately after the connection is established. The sending process also records detailed transmission logs, including sending time, target address, message size, network status, and transmission results, etc. To prevent network attacks and eavesdropping, the transmission 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, and each target terminal can only receive the session key encrypted specifically for it and cannot decrypt the key information of other terminals.

[0113] After the target terminal receives the key distribution message, it performs verification and decryption operations, and then returns an acknowledgement message to the first terminal to confirm the successful reception and correctness of the key. The target terminal first performs integrity check on the received message packet to verify whether the CRC32 check code is correct, ensuring that the message has not been error during transmission. Then verify the timestamp of the message to ensure that the message is sent within a reasonable time window, preventing replay attacks.

[0114] Next, verify the validity of the first terminal's digital certificate, including certificate chain verification, validity period check, certificate revocation status query, etc. After the certificate verification is passed, the target terminal extracts the public key of the first terminal and uses it 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 consistent, it means that the signature is valid.

[0115] After the signature verification is passed, the target terminal uses its own RSA private key to decrypt the encrypted session key. The decryption process first performs RSA decryption operation, and then performs OAEP de-padding operation to extract the original temporary session key and metadata information. After decryption, the target terminal will verify the CRC check code of the key to ensure the correctness of the decryption result.

[0116] After the verification, the target terminal calculates the check value of the temporary session key, hashes the key using the SHA-256 hashing algorithm to generate a 256-bit check value. The calculation of the check value also includes the device identifier and the current timestamp of the target terminal, ensuring the uniqueness and unforgeability of the check value. The target terminal constructs a confirmation message containing device identifier, check value, decryption status, receive timestamp, etc., 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 reaches the first terminal in a timely manner. The entire confirmation process realizes two-way authentication of 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.

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

[0118] 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, 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 intended target terminal and has not been tampered with. After verification, the first terminal extracts the check value from each confirmation message and performs consistency comparison. Since all terminals use the same temporary session key and the same hashing algorithm, theoretically all check values should be completely consistent. The first terminal calculates its own check value as a reference, and then compares each target terminal's check value one by one. The comparison process uses byte-level precise matching. If inconsistencies in check values are 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 check values, the first terminal will re-generate and send the encrypted session key, with a maximum of three retries. 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.

[0119] When the verification values ​​of all terminals are consistent, the first terminal generates a confirmation record of successful key distribution, including information such as the list of participating terminals, key distribution time, verification value, and distribution status. This record is encrypted and stored in the first terminal's security log for subsequent auditing and troubleshooting. Simultaneously, the first terminal sends a notification message to all target terminals indicating that key distribution is complete, officially declaring the successful establishment of the encrypted communication channel. The notification message includes information such as the channel identifier, validity period, and list of participating terminals. Upon receiving the notification, all terminals activate the encrypted communication function and begin using the temporary session key for encrypted data transmission. The entire verification process ensures key consistency in a distributed environment, guaranteeing the security and reliability of data transmission during subsequent collaborative processing.

[0120] This implementation constructs a highly secure key management scheme, providing a solid cryptographic foundation for multi-terminal collaborative processing. Device identification and public key acquisition mechanisms ensure the authenticity of the identity of each participating terminal and the trustworthiness of its public key, effectively preventing identity forgery and man-in-the-middle attacks. The application of a digital signature mechanism ensures the integrity and non-repudiation of key distribution messages, allowing for timely detection of any message tampering. A two-way authentication confirmation mechanism not only verifies the success of key distribution but also ensures the consistency of keys obtained by all terminals through checksum comparison, effectively preventing communication failures caused by key synchronization errors. The checksum consistency check mechanism provides a guarantee of key correctness in a distributed environment, ensuring the reliability of subsequent encrypted communication. Retry and error handling mechanisms enhance the system's fault tolerance, enabling it to cope with abnormal situations such as network instability and device failure. The entire key distribution process achieves end-to-end security protection, with corresponding security measures at each stage from key generation to distribution verification, constructing a complete key management security system and providing reliable technical support for the secure transmission and collaborative processing of medical data.

[0121] In one embodiment of this invention, the event association data includes continuous numerical parameters and discrete state parameters, and the event information also includes event type and severity level. Based on the event association data and / or event information, a consensus event description is determined, including the following steps:

[0122] S510. When the event-related data is a continuous numerical parameter, obtain the continuous numerical parameters collected by all terminals in the temporary collaborative group, calculate the weighted average of all continuous numerical parameters, and use the weighted average as the consensus value.

[0123] S520. Use consensus values ​​as descriptions of consensus events;

[0124] S530, in the case of discrete state parameters, collecting all discrete state parameters collected by terminals in the temporary collaborative group, and using majority voting method, the discrete state parameter with the highest number of votes is taken as the consensus event description;

[0125] S540, when there are state values with the same number of votes, the state value of the terminal with the highest priority is taken as the consensus event description.

[0126] In this embodiment, when the event-related data contains both continuous numerical parameters and discrete state parameters, they are processed separately and then combined to form a complete consensus event description.

[0127] When processing continuous numerical parameters in the temporary collaborative group, first, relevant numerical measurement data needs to be collected from all participating terminals. Continuous numerical parameters usually include physiological indicators of patients, such as heart rate, blood pressure, body temperature, and blood oxygen saturation, which can be represented by specific numerical values. In a hospital scenario, when a patient has an abnormal situation, multiple monitoring devices may simultaneously detect changes in related numerical values. For example, a bedside monitor detects a heart rate of 85 beats per minute, a wearable heart rate monitoring device detects a heart rate of 88 beats per minute, and a mobile nursing terminal obtains a heart rate of 86 beats per minute through manual measurement. In order to handle these numerical differences from different terminals, a weighted average method is used to determine the final consensus value. The weight distribution is preset. Through this weighted average method, the influence of measurement errors of a single terminal on the final result can be effectively reduced, and the accuracy and reliability of the data can be improved, providing more accurate data support for subsequent medical decision-making.

[0128] The weighted average value calculated in step S510 is directly taken as the consensus event description of the continuous parameter. The consensus value not only contains the numerical value itself, but also needs to be attached with relevant metadata information, such as measurement unit, confidence, and the number of terminals participating in the calculation. In specific implementation, the consensus event description will be formatted into a standard data structure. The calculation of confidence is based on the weight distribution of participating terminals and the dispersion degree of numerical values. When the measurement values of each terminal are close and the numerical value of the high-weight terminal dominates, the confidence is high. At the same time, the timestamp of the data is recorded to ensure the accuracy of the consensus event description in time. This structured description method not only facilitates the subsequent processing of the remote management platform, but also provides 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 the integrity and traceability of data are maintained, providing a reliable data foundation for clinical decision-making.

[0129] For the processing of discrete state parameters, majority voting method is adopted to determine the final consensus event description. Discrete state parameters usually represent device state, patient state or environmental state, etc. with clear classification information, such as state values like "normal", or behavior states like "in bed", "out of bed", etc. Within the temporary coordination group, each terminal will give a corresponding state assessment based on its own sensor data and algorithm. For example, in the scenario of monitoring patient fall risk, the bedside sensor may judge as "high risk", the wearable device judges as "medium risk", and the environmental sensor judges as "high risk". The implementation process of majority voting method first counts the frequency of each state value, and then selects the state value with the highest number of votes as the final consensus result. In the above example, "high risk" gets 2 votes, "medium risk" gets 1 vote, so "high risk" is selected as the consensus event description, so this scheme can effectively handle the case where multiple terminals make different judgments on the same event, improve the accuracy of judgment through collective wisdom, reduce the impact of single terminal misjudgment on the overall decision, and ensure that the final state description can reflect the consistent judgment of most terminals.

[0130] When the majority voting method has a tie, i.e. two or more state values get the same highest number of votes, the tie needs to be broken by a terminal priority mechanism. The determination of terminal priority is based on comprehensive evaluation of multiple dimensions, including device type, precision level, deployment location, historical reliability, etc. In a hospital environment, different types of terminals have different specialties and reliabilities. For example, professional medical monitoring devices usually have higher priority than general sensors, devices in the ICU have higher priority than devices in the general ward, and medical certified devices have higher priority than general Internet of Things devices. The calculation of priority score adopts a comprehensive scoring model: wherein is the priority score of the i-th terminal, is the device type score, is the precision level score, is the location importance score, is the historical reliability score, to are the corresponding weight coefficients. When there is a tie, the state value provided by the terminal with the highest priority score is automatically selected as the final consensus event description.

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

[0132] The embodiment adopts a weighted average method for continuous numerical parameters, fully considers the reliability and accuracy difference of different terminals, significantly improves the accuracy and stability of numerical data, and reduces the influence of single-point measurement error on overall judgment. For discrete state parameters, a majority voting method combined with a priority mechanism is adopted to ensure that reasonable decisions can be made based on device professionalism in the case of a tie. The classification and unified integration of mixed parameters realize the effective fusion of different types of data, and provide a complete technical solution for multi-dimensional event description in complex medical scenarios. Not only does it greatly reduce data redundancy and conflicts, but it also reduces the processing burden of the remote management platform.

[0133] In one of the embodiments of the present embodiment, a dominant reporting terminal is determined in the temporary cooperative group, including the following steps:

[0134] S610, according to the preset terminal priority rule, calculate the comprehensive score of each terminal in the temporary cooperative group;

[0135] S620, the terminal with the highest comprehensive score is taken as the dominant reporting terminal.

[0136] The preset terminal priority rule covers device performance, network connection quality, power state, historical reliability, device type and other evaluation dimensions. Device performance evaluation mainly considers the processing power, memory capacity, storage space and other hardware indicators of the terminal, and obtains performance benchmark scores through standardized testing. Network connection quality evaluation includes signal strength, network delay, packet loss rate, bandwidth and other network parameters, which directly affect the reliability and real-time performance of data transmission. Power state evaluation considers battery power, charging status, estimated battery life and other factors to ensure that the dominant reporting terminal can operate stably throughout the event processing process. Historical reliability evaluation is based on the terminal's past performance records, including failure rate, data accuracy, response time and other historical performance indicators. Device type evaluation gives different base scores based on the professionalism and functional characteristics of the terminal, such as professional medical devices having higher base scores than general sensors. The calculation of the comprehensive score adopts the weighted summation method, and the weight coefficient is set based on the actual needs of the hospital environment and experience data. Through this multi-dimensional comprehensive evaluation method, the overall ability and applicability of each terminal can be objectively and accurately quantified, providing a scientific basis for selecting the optimal dominant reporting terminal.

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

[0138] The embodiment avoids the deviation of subjective judgment through quantitative evaluation and weight distribution, 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 dominant reporting terminal, reduce the decision time and calculation overhead. The efficiency and reliability of data transmission are effectively optimized, and the energy consumption and resource consumption of the entire system are reduced by reducing redundant communication and repeated processing.

[0139] In one of the embodiments of the present embodiment, 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 following steps:

[0140] S710, the dominant reporting terminal serializes the consensus event description into a standard data format, and adds the group identifier of the temporary cooperative group and the terminal list in the standard data format, to obtain serialized data;

[0141] S720, encrypt the serialized data using the public key of the remote management platform to obtain encrypted data payload;

[0142] S730, calculate the digital digest of the encrypted data payload, and sign the digital digest using the private key of the dominant reporting terminal to obtain the digital signature;

[0143] S740, construct a data packet including the encrypted data payload and the digital signature, and send the data packet to the central control device.

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

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

[0146] Due to the low processing efficiency of asymmetric encryption algorithms (such as RSA) for large data volumes, hybrid encryption schemes are commonly used in practical applications. The specific process is as follows: first, a random symmetric encryption key (such as an AES-256 key) is generated, and this symmetric key is used to encrypt the serialized data, and then the symmetric key is encrypted using the public key of the remote management platform. Assuming that the serialized data is D, the randomly generated symmetric key is K, and the public key of the remote management platform is PK, then the encryption process is: Get encrypted data , Get encrypted key The final encrypted data payload contains two parts: This hybrid encryption scheme not only guarantees 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 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 of medical data security and privacy protection.

[0147] Computing the digital digest of the encrypted data payload and performing digital signature can ensure data integrity and identity authentication. The calculation of the digital digest uses secure hash algorithms such as SHA-256 or SHA-3 to convert the encrypted data payload of any length into a fixed-length hash value.

[0148] After obtaining the digital digest, the digest is signed using the private key of the leading reporting terminal to generate a digital signature. The calculation of the digital signature uses asymmetric encryption algorithms such as RSA or ECDSA, and the signature process is: where is the private key of the leading reporting terminal. The digital signature not only verifies the integrity of the data, but also confirms the identity of the data source, preventing data tampering or forgery. In a hospital environment, each terminal has a unique digital certificate and key pair, which is generated and distributed in a secure manner during device deployment. The generation process of the digital signature also includes timestamp information to prevent replay attacks. The complete signature structure includes signature value, signature algorithm identification, terminal certificate information, timestamp, etc. Through this digital signature mechanism, the remote management platform can verify whether the data source is a legitimate terminal device, ensuring the authenticity and credibility of the data, providing a reliable data foundation for subsequent medical decision-making.

[0149] Finally, the data packet including the encrypted data payload and the digital signature is constructed and sent to the central control device. The construction of the data packet requires the encrypted data payload and the digital signature generated in the previous steps to be organized and encapsulated according to the predefined protocol format. The standard data packet structure adopts a hierarchical design, including a packet header, a payload, and a check. The packet header includes meta-information of the data packet, such as version number, data packet type, length, source terminal ID, target address, timestamp, etc. The payload part includes the encrypted data payload and the digital signature. The check part includes the checksum of the entire data packet, which is used to detect errors in the transmission process. 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 transmission protocol, such as TCP or a reliable transmission protocol based on UDP, to ensure that the data can accurately reach the central control device. During the sending process, a retransmission mechanism is also implemented. When transmission failure or timeout is detected, automatic retransmission will be performed, up to a maximum of 3 times. After sending is completed, the leading reporting terminal will wait for the confirmation response of the central control device, confirming that the data packet has been successfully received and processed. If no confirmation response is received within the preset time, an abnormal processing procedure will be triggered, including re-sending, switching network path, or sending to the standby central control device, etc. Through this reliable data packet construction and sending mechanism, it ensures that the key 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.

[0150] 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, and providing a reliable data foundation for medical decision-making.

[0151] The application also provides a multi-terminal cooperative processing method, which is applied to a central control device and deployed with a remote management platform. The method comprises:

[0152] S810, in response to receiving the data packet sent by the leading reporting terminal, decrypting the data packet to obtain the consensus event description;

[0153] S820, according to the consensus event description, obtaining the event information of the event;

[0154] S830, importing the event information into a preset event processing queue, and sending a response confirmation message to the leading reporting terminal, wherein the response confirmation message includes a unique event ID and a processing status of the consensus event description.

[0155] After receiving the data packet sent by the leading reporting terminal, the central control device first needs to verify the integrity of the data packet and decrypt it to obtain the original consensus event description. The decryption process uses the reverse operation corresponding to the encryption process. First, the structure of the data packet is parsed to extract the header information, encrypted data payload, and digital signature, etc. Before decryption, the integrity of the data packet and the legality of the source need to be verified. The integrity verification is performed by calculating the checksum of the received data packet and comparing it with the checksum recorded in the header. If the two checksums are inconsistent, it means that the data packet has been damaged or tampered with during transmission, and retransmission is required. The source verification is performed by digital signature, which uses the public key of the leading reporting terminal to verify the digital signature. If the verification is passed, it means that the data indeed comes from a legal terminal device and has not been tampered with.

[0156] After the verification is completed, the decryption process begins. Since a hybrid encryption scheme is used, the decryption process is divided into two steps: first, the symmetric key is decrypted using the private key of the central control device; then the actual data is decrypted using the decrypted symmetric key. 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 decryption fails or the data format is incorrect, an exception handling process will be triggered, error logs will be recorded, and a decryption failure response message will be sent to the leading reporting terminal. Through this strict verification and decryption mechanism, only legal and complete data can be successfully decrypted and subsequently processed, effectively preventing malicious attacks and data pollution, and ensuring the security and reliability of medical data processing.

[0157] According to the decrypted consensus event description, 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 event type, parameter value, state information, timestamp, confidence, and participant terminal information, etc. The extraction process of event information first parses the JSON format consensus event description and extracts the values of each field according to the predefined data pattern. For example, the event type field is extracted from the consensus event description.

[0158] The extraction of parameter information includes numerical parameters such as heart rate, blood pressure, body temperature, etc., and state parameters such as patient consciousness state, device running state, etc. The extraction of time information includes event occurrence time, data collection time, processing time, etc. The extracted event information is also associated with historical data to identify whether it is a repeated event or a continuation of a related event.

[0159] Importing the extracted event information into a preset event processing queue can achieve ordered processing of events and optimized allocation of resources. The event processing queue adopts the data structure of a priority queue, and the processing priority is determined according to factors such as the urgency of the event, the severity level, the patient risk level, etc. The event information will be assigned a unique event ID when imported into the queue, generated in the form of UUID or based on a combination of timestamp and 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 dynamically adjusts the processing order of events according to priority and resource availability, ensuring that high-priority events can be processed in a timely manner. At the same time of importing events into the queue, the central control device will immediately send a response confirmation message to the master terminal, confirming that the data packet has been successfully received and processed. The response confirmation message contains information such as the unique event ID, processing status, and expected processing time. Through this ordered 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.

[0160] In this embodiment, the data packet verification and decryption mechanism ensures that only legitimate and complete data can enter the processing flow, effectively preventing security threats and data pollution, and ensuring the security and reliability of medical data processing. Comprehensive extraction and standardized processing of event information ensure that data of different sources and formats can be uniformly processed and analyzed, improving data consistency and availability. The intelligent priority queue management mechanism dynamically sorts events according to their urgency and importance, 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 unique event IDs provide a basis for tracking the entire life cycle of events, facilitating event traceability, auditing, and statistical analysis. The timely response confirmation mechanism allows terminal devices 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 reduces the need for manual intervention, improving processing efficiency and accuracy. In a hospital environment, this technical solution can effectively integrate the collaborative data of multiple terminals.

[0161] In one embodiment of the present embodiment, after sending the response confirmation message to the master terminal, it further includes:

[0162] S910, based on the consensus event description, triggering the corresponding diagnostic engine and outputting the diagnostic result.

[0163] The diagnostic algorithm and model are automatically selected by analyzing the event features. The triggering mechanism of the diagnostic engine first deeply analyzes the consensus event description, extracts key diagnostic features, including event type, parameter value, abnormal pattern, time feature, and other multidimensional information. According to these features, through the pre-set rule engine or machine learning classifier, it is determined which diagnostic engine should be activated. In the hospital environment, multiple specialized diagnostic engines are usually deployed, such as cardiovascular disease diagnostic engine, respiratory system disease diagnostic engine, nervous system disease diagnostic engine, fall risk assessment engine, etc., each of which is optimized for a specific medical field.

[0164] The selection of the diagnostic engine adopts a multi-layer decision tree structure. First, coarse classification is performed according to the event type, for example, events of the type "cardiac_abnormality" will trigger the cardiovascular diagnostic engine. On the basis of coarse classification, further fine classification is performed according to specific parameter features, for example, heart rate abnormalities may trigger the arrhythmia diagnostic sub-engine, and blood pressure abnormalities may trigger the hypertension diagnostic sub-engine. The activation process of the diagnostic engine includes model loading, parameter initialization, data preprocessing, etc. Model loading selects the corresponding diagnostic model from the pre-trained machine learning model library. These models are usually trained based on a large amount of clinical data, including deep neural networks, support vector machines, random forests, and other types of algorithms. Parameter initialization sets the initial parameters of the model according to the basic information of the current patient (age, gender, medical history, etc.). Data preprocessing converts the original data in the consensus event description into the standardized input format required by the diagnostic model, including value normalization, feature encoding, missing value processing, etc. The diagnostic engine also conducts comprehensive analysis combined with the patient's historical medical records, identifies disease development trends 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, ensuring the real-time performance and response capability of the system.

[0165] After the diagnostic engine is successfully triggered, it starts to execute the pre-deployed diagnostic reasoning model and finally outputs structured diagnostic results. The output diagnostic results contain multiple dimensions of information: main diagnosis, possible differential diagnosis, diagnostic confidence, suggested further examination, recommended treatment plan, risk assessment, etc.

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

[0167] Referring to Figure 3 The embodiments of the present application also provide a multi-terminal cooperative processing system, comprising:

[0168] a first terminal;

[0169] at least one second terminal;

[0170] a central control device, which is deployed with a remote management platform and is connected with the first terminal and the at least one second terminal.

[0171] In the embodiment, the first terminal, the second terminal and the central control device can be 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, or the like device with a processor. Of course, the first terminal, the second terminal and the central control device can also be a server. The embodiment of the present application does not specially limit the specific form of the first terminal, the second terminal and the central control device.

[0172] 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 adopt a completely hardware embodiment, a completely software embodiment or an embodiment combining software and hardware aspects. Moreover, the present application can adopt a 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 codes.

[0173] The present application is described with reference to the flowcharts and / or block diagrams of the method, device (system), computer program product according to the embodiments of the present application. It should be understood that each flow and / or block in the flowcharts and / or block diagrams and the combination of the flows and / or blocks in the flowcharts and / or block diagrams can be implemented by computer program instructions. These computer program instructions can be provided to a general-purpose computer, a special-purpose computer, an embedded processor or other programmable data processing devices to produce a machine, so that the instructions executed by the computer or other programmable data processing devices produce a device implemented in the flowcharts and / or block diagrams. Figure 1 one or more flows and / or blocks Figure 1 an apparatus that carries out the functions specified in one or more flows and / or blocks.

[0174] These computer program instructions can also be stored in a computer readable memory that can direct the computer or other programmable data processing devices to work in a specific manner, so that the instructions stored in the computer readable memory produce a manufactured product including instruction apparatus, which implements the flowcharts and / or block diagrams. Figure 1 one or more flows and / or blocks Figure 1 an apparatus that carries out the functions specified in one or more flows and / or blocks.

[0175] These computer program instructions can also be loaded into a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks. Figure 1 Figure 1

[0176] In one typical configuration, the computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory.

[0177] The memory can include non-persistent memory and / or volatile memory, such as random access memory (RAM) about which the processor can execute instructions. The memory can also include non-volatile memory, such as read only memory (ROM), electrically programmable read only memory (EPROM), electrically erasable programmable read only memory (EEPROM), flash memory, or other memory technologies, about which the processor can execute instructions. The memory is an example of computer readable media.

[0178] Computer readable media includes permanent and non-permanent, removable and non-removable media implemented in any method or technology for storage of information such as 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 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 cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information accessible to computing devices. According to the definition herein, computer readable media does not include transitory media, such as modulated data signals and carrier waves.

[0179] It should also be noted that the terms "comprising," "including," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements recited, but can also include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without limitation, an element preceded by "comprises a" does not, without more constraints, foreclose the existence of additional identical elements in the process, method, article, or apparatus that comprises the element.

[0180] ​​The above merely provides an example of the present application, and is not intended to limit the present application. For those skilled in the art, the present application can have various modifications and changes. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principle of the present application shall fall into the scope of claims of the present application.

Claims

1. A method of multi-terminal cooperative processing, characterized by, The method is applied to a first terminal connected with a central control device, and a remote management platform is deployed in the central control device. In response to a trigger signal of an event, event information of the event is determined, and a collaborative processing request is initiated to at least one second terminal within a communication range, wherein the event information includes an initial timestamp event summary, the collaborative processing request carries the event summary, and each second terminal is connected with the central control device and used to determine whether to respond to the collaborative processing request. A target terminal responding to the collaborative processing request is determined in the second terminal, and a temporary collaborative group including the target terminal is constructed. Shared event-related data is obtained in the temporary collaborative group, wherein the event-related data includes continuous numerical parameters and discrete state parameters. In the case that the event-related data is continuous numerical parameters, the continuous numerical parameters collected by all terminals in the temporary collaborative group are obtained, and a weighted average value of all continuous numerical parameters is calculated as a consensus value. The consensus value is taken as a consensus event description. In the case that the event-related data is discrete state parameters, the discrete state parameters collected by all terminals in the temporary collaborative group are obtained, and a majority voting method is used 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, the state value of the terminal with the highest priority is taken as the consensus event description. A dominant reporting terminal is determined in the temporary collaborative group, and the dominant reporting terminal is used to encapsulate the consensus event description into a data packet and send the data packet to the remote management platform. A response confirmation message returned by the remote management platform is received, and a unique event ID and a processing state in the response confirmation message are broadcast to all terminals in the temporary collaborative group, so that all terminals synchronously update the processing progress of the event.

2. The method of claim 1, wherein, Shared event-related data is obtained in the temporary collaborative group, including: An encrypted communication channel is established in the temporary collaborative group, and 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. Shared event-related data is obtained in the temporary collaborative group.

3. The method of claim 2, wherein, An encrypted communication channel is established in the temporary collaborative group, including: A temporary session key of the temporary collaborative group is generated, and the temporary session key is distributed to all terminals in the temporary collaborative group, wherein each terminal in 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 of claim 3, wherein, The temporary session key is distributed to all terminals in the temporary collaborative group, including: The device identifier and the public key of all terminals in the temporary collaborative group are obtained. For any one terminal in the temporary collaborative group, the public key of the terminal is used to encrypt the temporary session key to obtain an encrypted session key for the terminal. The encrypted session key and the digital signature of the first terminal are sent to other terminals together. After the encrypted session key and the digital signature of the first terminal are sent to other terminals together, the method further includes: receiving an acknowledgement message returned by the other terminal, wherein the acknowledgement message comprises a check value of the temporary session key obtained by the other terminal after decrypting with its private key; in the case that the check values of all terminals are consistent, determining that the temporary session key is securely shared among all terminals.

5. The method of claim 1, wherein, The event information further comprises an event type and a severity level.

6. The method of claim 1, wherein, determining a leading reporting terminal in the temporary cooperative group, comprising: calculating a comprehensive score of each terminal in the temporary cooperative group according to a preset terminal priority rule; taking the terminal with the highest comprehensive score as the leading reporting terminal.

7. The method of claim 1, wherein, The leading reporting terminal encapsulates the consensus event description into a data packet and sends the data packet to the central control device, comprising: The leading reporting terminal serializes the consensus event description into a standard data format, adds a group identifier of the temporary cooperative group and a list of participating terminals in the standard data format, and obtains serialized data; encrypting the serialized data using a public key of the remote management platform to obtain encrypted data payload; calculating a digital digest of the encrypted data payload and signing the digital digest using a private key of the leading reporting terminal to obtain a digital signature; constructing a data packet comprising the encrypted data payload and the digital signature, and sending the data packet to the central control device.

8. A method of multi-terminal cooperative processing, characterized by, The application is applied to the central control device, and the central control device is deployed with a remote management platform, and the method comprises: decrypting the data packet to obtain the consensus event description in response to receiving the data packet sent by the leading reporting terminal; parsing the consensus event description to obtain a parsing result; extracting values of fields of the parsing result according to a predefined data mode to obtain event information of the event; importing the event information into a preset event processing queue and sending a response acknowledgement message to the leading reporting terminal, wherein the response acknowledgement message comprises a unique event ID and a processing status of the consensus event description.

9. The method of claim 8, wherein, After sending the response acknowledgement message to the leading reporting terminal, further comprising: triggering a corresponding diagnostic engine based on the consensus event description and outputting a diagnostic result.

10. A multi-terminal cooperative processing system, characterized by comprising: comprising: a first terminal for executing the multi-terminal cooperative processing method according to any one of claims 1 to 7; at least one second terminal; a central control device deployed with a remote management platform and connected with the first terminal and the at least one second terminal, for executing the multi-terminal cooperative processing method according to any one of claims 8 to 9.

Images