Data transmission method, system and equipment based on monitoring client and storage medium

Abstract

The embodiment of the invention provides a data transmission method, system and device based on a monitoring client and a storage medium. The method is applied to a service node, and the service node is a back-end node connected with a distributed gateway. The method comprises the following steps: receiving monitoring data uploaded by a monitoring terminal corresponding to a service node, and receiving other data transmitted by a first other node based on a first subscription channel; wherein the first subscription channel represents a data subscription channel between the service node and a first other node, the first other node represents other service nodes subscribed by the service node, and other data represents monitoring data which is received by the first other node and uploaded by a monitoring terminal corresponding to the first other node; sending the monitoring data and other data to the monitoring client based on the second subscription channel; wherein the second subscription channel represents a data subscription channel between the service node and the monitoring client, and the number of the monitoring client is at least one.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a data transmission method, system, device and storage medium based on a monitoring client. Background Technology

[0002] As the scale of data management increases across various fields, users need to manage and view data across devices. For example, in intensive care settings, data sharing across multiple devices is a key element in achieving efficient clinical collaboration.

[0003] However, current monitoring systems have limitations in cross-device data sharing, making it difficult to share data efficiently between different devices. This results in inconsistencies in data between different devices, low data transmission efficiency, and negatively impacts the user's viewing experience. Summary of the Invention

[0004] This application provides a data transmission method, system, device, and storage medium based on a monitoring client to achieve data sharing among multiple devices.

[0005] In a first aspect, embodiments of this application provide a data transmission method based on a monitoring client. This method is applied to a service node, which is a backend node connected to a distributed gateway. The method includes:

[0006] The system receives monitoring data uploaded by the monitoring terminal corresponding to the service node, and receives other data transmitted by the first other node based on the first subscription channel; wherein, the first subscription channel represents the data subscription channel between the service node and the first other node, the first other node represents other service nodes subscribed to by the service node, and the other data represents the monitoring data uploaded by the monitoring terminal corresponding to the first other node received by the first other node.

[0007] Based on the second subscription channel, the monitoring data and the other data are sent to the monitoring client; wherein, the second subscription channel represents the data subscription channel between the service node and the monitoring client, and the monitoring client includes at least one.

[0008] Secondly, embodiments of this application provide a data transmission device based on a monitoring client. This device is applied to a service node, which is a backend node connected to a distributed gateway. The device includes:

[0009] The data receiving unit is used to receive monitoring data uploaded by the monitoring terminal corresponding to the service node, and to receive other data transmitted by the first other node based on the first subscription channel; wherein, the first subscription channel represents the data subscription channel between the service node and the first other node, the first other node represents other service nodes subscribed to by the service node, and the other data represents the monitoring data uploaded by the monitoring terminal corresponding to the first other node received by the first other node.

[0010] A data sending unit is used to send the monitoring data and the other data to the monitoring client based on a second subscription channel; wherein the second subscription channel represents a data subscription channel between the service node and the monitoring client, and the monitoring client includes at least one.

[0011] Thirdly, embodiments of this application provide a data transmission system based on a monitoring client, the system including multiple service nodes, among which at least a first service node and a second service node are included;

[0012] The first service node is used to receive monitoring data uploaded by the monitoring terminal corresponding to the first service node and other data transmitted by the second service node through the first subscription channel; and to transmit the received monitoring data and other data to the corresponding monitoring client through the second subscription channel; wherein, the other data represents the monitoring data uploaded by the monitoring terminal corresponding to the second service node received by the second service node;

[0013] The second service node is used to transmit the other data received to the first service node through the first subscription channel.

[0014] Fourthly, embodiments of this application provide an electronic device, including: a memory and a processor;

[0015] The memory stores computer-executed instructions;

[0016] The processor executes computer execution instructions stored in the memory, causing the processor to perform the implementation method described in the first aspect above.

[0017] Fifthly, embodiments of this application provide a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the embodiments described in the first aspect above.

[0018] Sixthly, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the implementation methods described in the first aspect above.

[0019] This application provides a data transmission method, system, device, and storage medium based on a monitoring client. The service node, acting as a backend node of a distributed gateway, receives raw monitoring data uploaded by its corresponding monitoring terminal and simultaneously obtains monitoring data from other subscribed service nodes through a first subscription channel, thus achieving comprehensive data acquisition. The acquired data is then sent to the monitoring client via a second subscription channel. The service node acts as a data aggregation point, using a subscription mechanism to obtain data from other service nodes and then pushing the integrated data stream to the monitoring client through an independent downlink channel. This allows the monitoring client to obtain a global perspective without directly connecting to multiple data sources. By constructing data subscription channels between service nodes and between service nodes and clients, cross-terminal and cross-node data sharing is achieved, breaking the traditional one-to-one binding model, improving the flexibility and scalability of data transmission, and enhancing the user's data viewing experience. Attached Figure Description

[0020] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0021] Figure 1 A flowchart illustrating a data transmission method based on a monitoring client, provided as an embodiment of this application;

[0022] Figure 2 An implementation architecture diagram of data sharing among multiple monitoring clients provided in this application embodiment;

[0023] Figure 3 A flowchart illustrating a data transmission method based on a monitoring client, provided as an embodiment of this application;

[0024] Figure 4 A schematic diagram of a data transmission device based on a monitoring client provided in an embodiment of this application;

[0025] Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application.

[0026] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0027] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application.

[0028] First, let me explain the terms used in this application:

[0029] Monitoring terminal: This can refer to bedside equipment, such as infusion pumps, nutrition pumps, and monitors;

[0030] Monitoring clients can include various product forms such as central stations, workstations, and viewing stations;

[0031] Central Station (CS)

[0032] Workstation: Work Station, abbreviated as WS;

[0033] View Station (VS)

[0034] Service node: refers to the node connected to the backend of the distributed gateway. In this embodiment, it can be called the main service node. The distributed gateway can provide unified gateway services, and upper-layer applications can send instructions to the service node through the unified gateway services.

[0035] In intensive care settings, multi-terminal monitoring data sharing is a key element in achieving efficient clinical collaboration. Current mainstream monitoring systems generally employ a "one-to-one" binding architecture, where patient monitoring data and alarm information are only displayed on the central station directly paired with the patient; other unbound central stations or management terminals cannot access them. Even within the same hospital, desktop terminals in different wards or departments cannot view the real-time waveforms and alarm status of a target bed across terminals.

[0036] Currently, some systems attempt to copy data streams for consumption by other terminals through simple data forwarding middleware, but they lack a unified data model and synchronization mechanism. The views of each terminal are inconsistent, alarm status cannot be linked, and delays or packet loss are prone to occur when the network fluctuates, affecting the data transmission efficiency between different devices and resulting in a poor user experience when viewing data.

[0037] This application provides a data transmission method, system, device, and storage medium based on a monitoring client, which is applied in the field of communication technology to realize data sharing among multiple terminals.

[0038] It should be noted that the data in this embodiment is not specific to any particular user and does not reflect the personal information of any particular user. It should also be noted that the data in this embodiment comes from a publicly available dataset.

[0039] The collection, storage, use, processing, transmission, provision, and disclosure of user personal information involved in the technical solution of this application all comply with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0040] To enable readers to have a deeper understanding of the implementation principles of this application, the embodiments are further detailed.

[0041] Figure 1 This is a flowchart illustrating a data transmission method based on a monitoring client according to an embodiment of the present disclosure. The method can be executed by a data transmission device based on a monitoring client. The method is applied to a service node, which is a backend node connected to a distributed gateway. Figure 1 As shown, the method includes the following steps:

[0042] S101. Receive monitoring data uploaded by the monitoring terminal corresponding to the service node, and receive other data transmitted by the first other node based on the first subscription channel; wherein, the first subscription channel represents the data subscription channel between the service node and the first other node, the first other node represents other service nodes subscribed to by the service node, and the other data represents the monitoring data uploaded by the monitoring terminal corresponding to the first other node received by the first other node.

[0043] For example, a service node refers to a logical processing unit deployed on the backend of a distributed gateway that has the ability to receive, aggregate, and distribute data. Its physical form can be an independent server, a containerized microservice instance, or a virtual machine instance, used to carry out local aggregation and cross-node collaboration of monitoring data.

[0044] Monitoring terminals can include devices such as bedside monitors for monitoring patient conditions, as well as devices such as infusion pumps, analgesic pumps, anesthesia machines, nutrition pumps, and ventilators for treatment. Monitoring data can include the patient's physiological parameters and / or treatment parameters; that is, the monitoring terminal can upload the patient's physiological and / or treatment parameters it acquires as monitoring data to its assigned service node via wired or wireless means. For example, the monitoring terminal can collect the patient's dynamic physiological information in real time or at regular intervals and upload the collected information as monitoring data to the service node in real time or at regular intervals. One service node can correspond to multiple monitoring terminals; the monitoring terminals corresponding to different service nodes can be the same or different.

[0045] The first subscription channel is a one-way or two-way data communication link established based on a lightweight messaging protocol. Logically, it represents the subscription relationship between a service node and the monitoring data managed by other nodes. This channel supports both event-driven incremental push and on-demand retrieval modes, does not rely on traditional message middleware, and features low resource consumption and high throughput. An efficient data channel is established between different service nodes through a lightweight subscription engine.

[0046] The first other node refers to other service nodes within the same distributed gateway architecture as the current service node. Other data refers to the monitoring data collected by the first other node from the monitoring terminal it connects to. In other words, each service node can obtain monitoring data received from its own monitoring terminal, as well as monitoring data received from other service nodes. The data subscription channel between different service nodes is the first subscription channel.

[0047] S102. Based on the second subscription channel, the monitoring data and other data are sent to the monitoring client; wherein, the second subscription channel represents the data subscription channel between the service node and the monitoring client, and the monitoring client includes at least one.

[0048] For example, the second subscription channel is a data subscription channel between the service node and the monitoring client. Logically, it represents the service node's ability to continuously push data to the monitoring client, supporting concurrent subscription by multiple clients, reconnection after disconnection, data backtracking, and QoS (Quality of Service) graded transmission. This channel is isolated from the first subscription channel at the protocol stack, connection management, and data routing levels, ensuring decoupling between uplink aggregation and downlink distribution.

[0049] Monitoring clients can include a central station, workstations, and viewing stations. Each monitoring client can establish a second subscription channel with the service node through a standard API (Application Programming Interface) or a proprietary SDK (Software Development Kit), obtaining globally authorized bed data without directly connecting to multiple service nodes. Different monitoring clients can subscribe to the same or different service nodes.

[0050] The data obtained by the monitoring client from the service node may include monitoring data obtained by the service node from the corresponding monitoring terminal, or other data subscribed to by the service node from other nodes. In other words, the service node can push the latest monitoring data from its local cache, along with other data, to all monitoring clients with established subscription connections through a second subscription channel.

[0051] Service nodes can also respond to on-demand subscription requests initiated by monitoring clients. Based on the bed ID, data type, and time range specified by the monitoring client, they retrieve matching data from the local data cache pool, encapsulate it into a structured format, and distribute it. The local data cache pool includes monitoring data and other data.

[0052] This embodiment uses a service node as the data aggregation center of the distributed gateway backend. On the one hand, it actively accesses monitoring data managed by other service nodes through the first subscription channel, forming cross-node data fusion capabilities. On the other hand, it relies on the second subscription channel to uniformly organize and schedule local monitoring data with monitoring data from other nodes, and pushes it to multiple monitoring clients. This enables real-time synchronization and sharing of data from each monitoring terminal in each monitoring client. Each monitoring client does not need to directly connect to multiple sources to obtain data on demand, improving sharing efficiency and avoiding redundant transmission.

[0053] In this embodiment, the method further includes: transmitting the received monitoring data to a second other node based on a third subscription channel; wherein the third subscription channel represents a data subscription channel between the service node and the second other node, and the second other node represents other service nodes that have subscribed to the service node.

[0054] Specifically, a service node can subscribe to data from a first set of other nodes, and the data subscription channel between the service node and the first set of other nodes is called the first subscription channel. The service node's data can also be subscribed to by a second set of other nodes, and the data channel between the service node and the second set of other nodes is called the third data channel. The second set of other nodes refers to any service node other than the service node itself; the first set of other nodes and the second set of other nodes can be the same or different.

[0055] The third subscription channel is a message communication channel established between the service node and other nodes for one-way or two-way data push. The first, second, and third subscription channels are all high-efficiency data channels established through a lightweight subscription engine.

[0056] In this embodiment, the third subscription channel is used to carry out the distribution of the monitoring data received by the service node to the authorized second other nodes. That is, after the service node obtains the monitoring data from the corresponding monitoring terminal, it can synchronize the monitoring data to the second other nodes, so that the second other nodes can synchronize the monitoring data to the monitoring client corresponding to the second other nodes.

[0057] The advantage of this setup is that it enables service nodes to output data to other nodes via a third subscription channel, allowing service nodes to act not only as data consumers of the first subscription channel but also as data producers of the third subscription channel. This allows multiple service nodes to build a decentralized mesh data exchange structure, avoiding reliance on a single node for data aggregation and distribution. Without increasing the burden on bedside equipment, it supports wide-area collaboration of monitoring data across wards and hospitals, improving the flexibility of data transmission.

[0058] In this embodiment, the method further includes: in response to a data subscription request from any second other node, sending an authorized whitelist corresponding to the service node to the second other node; wherein the authorized whitelist includes multiple terminal identifiers, each terminal identifier representing a monitoring terminal that the second other node is allowed to subscribe to from the service node; the authorized whitelist is used to instruct the second other node to determine the required terminal identifier from the authorized whitelist in order to obtain the monitoring data corresponding to the required terminal identifier from the service node.

[0059] Specifically, an authorization whitelist refers to a set of authorized monitoring terminal identifiers, or a set of bed identifiers, pre-configured and maintained by a service node. That is, it represents the beds authorized by the service node, allowing other service nodes to subscribe to or access the data of those authorized beds. A bed can be configured with multiple monitoring terminals, meaning one bed identifier can correspond to multiple monitoring terminal identifiers. The monitoring terminals corresponding to the bed identifiers in the authorization whitelist are the authorized monitoring terminals. Each service node can have its own authorization whitelist, indicating that other service nodes can subscribe to the data of the monitoring terminals authorized by that service node. For example, service node A can receive monitoring data from monitoring terminals K, M, and N, but the authorization whitelist only contains M and N. Therefore, service node B can only choose to subscribe to the monitoring data of M and / or N from service node A. In other words, in a distributed gateway architecture, the authorization whitelist serves as the core carrier of access control policies, limiting which monitoring terminal data can be subscribed to by external service nodes. The authorized whitelist can be generated and dynamically updated by the service node in the local policy module. For example, it can be refreshed periodically or event-driven based on clinical management rules, department permission configuration, or user role policies.

[0060] A terminal identifier is an identification information that uniquely represents a monitoring terminal, and a bed identifier is an identification information that uniquely represents a bed. In this embodiment, the terminal identifier can be the smallest authorized unit in the authorized whitelist; its existence indicates that all monitoring data uploaded by the corresponding monitoring terminal is within the subscription range.

[0061] The service node listens for subscription request messages from other nodes, parses the node identity credentials carried within, reads a pre-defined authorization whitelist from its local policy database, encapsulates it into a JSON response body, and returns it to the other nodes. The other nodes then determine which monitoring terminals they wish to subscribe to based on the authorization whitelist, and subsequently subscribe to the monitoring data collected by those terminals from the service node.

[0062] The advantage of this setup is that by setting up an authorization whitelist, all subsequent data subscription activities are based on the terminal identifiers authorized within the whitelist, thereby constraining subscription permissions, preventing data leakage, and improving the security of data transmission.

[0063] Figure 2 This is a diagram illustrating the architecture for data sharing among multiple monitoring clients. Figure 2 The main service unit in the system is the service node, while the central station, workstation, and viewing station are all monitoring clients. Main service unit B subscribes to data from main service unit A, and monitoring clients subscribe to the data of their respective main service units. Each main service unit needs to register its service with the service registry and send heartbeat information in real-time or periodically to indicate that it is working normally. The unified gateway service also needs to register its service with the service registry and send heartbeat information. The unified gateway service can send instructions to the main service units through service routing; for example, it can send instructions issued by users in upper-layer applications. Each main service unit integrates at least the following functions: monitoring core service, data review core service, and data storage service. The monitoring core service receives monitoring data collected by the monitoring terminal and other data from other service nodes; the data review core service manages and transmits historically received data; and the data storage service stores the data.

[0064] In this embodiment, the method further includes: treating the received monitoring data as historical data and storing the historical data in association with the receiving time.

[0065] Specifically, monitoring data can be physiological parameter waveforms, numerical measurement results, and alarm event information uploaded in real time by service nodes from their corresponding monitoring terminals. Service nodes can receive monitoring data in real time, and each piece of monitoring data has its own reception time, representing the time when the service node received the monitoring data. After receiving the monitoring data, the service node can treat the monitoring data as historical data and associate the historical data with the corresponding reception time for storage. For example, the monitoring core service can transmit historical data and reception time to the data review core service. The data review core service can then transmit the historical data and reception time to other service nodes or monitoring clients that have subscribed to the data, and can also associate and store historical data and reception time based on data storage services.

[0066] The advantage of this setup is that by strongly binding each received monitoring data with the precise time of receipt and performing persistent storage, a historical data pool with temporal continuity and traceability is built. This allows for the independent support of advanced clinical functions such as data review, trend analysis, and alarm attribution without relying on external information systems, thus meeting the actual needs of users.

[0067] In this embodiment, the method further includes: responding to a data review instruction, obtaining a set of historical data within a preset time period based on the reception time corresponding to each historical data; and sending the set of historical data within the preset time period to the monitoring client.

[0068] Specifically, the monitoring client can not only subscribe to the monitoring data obtained by the service node in real time, but also subscribe to the monitoring data obtained by the service node in historical time. That is, it can obtain historical data from the service node.

[0069] Data review commands can be initiated by the monitoring client to request access to historical monitoring data within a specified time range. The command can include a start and end time point to define the time range of the data to be retrieved. This command can be sent to the service node via a second subscription channel, representing a reuse of an existing data subscription channel without adding new communication links. Historical data refers to predefined, structured data records that associate received monitoring data with their reception time; each historical data record includes the monitoring data content and its corresponding timestamp. The preset time period is explicitly specified in the data review command, depending on the clinical usage scenario. Data review commands can also be issued by the unified gateway service, instructing the service node to send data within the preset time period to the monitoring client.

[0070] Upon receiving a data review instruction, the system parses a preset time period from the instruction and retrieves monitoring data and other data received within that historical time period as historical data, thus obtaining a set of historical data for the preset time period. This set of historical data for the preset time period is then sent to the monitoring client via a second subscription channel.

[0071] The advantage of this setup is that it enables accurate extraction and reliable delivery of historical data within a preset time period, which is beneficial for supporting clinical business scenarios that rely on historical data, such as disease progression analysis, teaching rounds, and quality control reviews, and improves the user's data query experience.

[0072] This application provides a data transmission method based on a monitoring client. A service node, acting as a backend node of a distributed gateway, receives raw monitoring data uploaded by its corresponding monitoring terminal and simultaneously acquires monitoring data from other subscribed service nodes through a first subscription channel, thus achieving comprehensive data acquisition. The acquired data is then sent to the monitoring client via a second subscription channel. The service node acts as a data aggregation point, using a subscription mechanism to acquire data from other service nodes and then pushing the integrated data stream to the monitoring client through an independent downlink channel. This allows the monitoring client to obtain a global perspective without directly connecting to multiple data sources. By constructing data subscription channels between service nodes and between service nodes and clients, cross-terminal and cross-node data sharing is achieved, breaking the traditional one-to-one binding model, improving the flexibility and scalability of data transmission, and enhancing the user's data viewing experience.

[0073] Figure 3 A flowchart illustrating a data transmission method based on a monitoring client, as provided in this application embodiment, is shown below. Figure 3 As shown, this embodiment, based on the above embodiments, provides a detailed description of a data transmission method based on a monitoring client. The method includes:

[0074] S301. Receive monitoring data uploaded by the monitoring terminal corresponding to the service node, and receive other data transmitted by the first other node based on the first subscription channel; wherein, the first subscription channel represents the data subscription channel between the service node and the first other node, the first other node represents other service nodes subscribed to by the service node, and the other data represents the monitoring data uploaded by the monitoring terminal corresponding to the first other node received by the first other node.

[0075] S302. Determine the data to be transmitted based on monitoring data and other data.

[0076] For example, the data to be transmitted refers to the data that the monitoring client can subscribe to from the service node. For instance, the data to be transmitted can be all the data received by the service node, or it can be a portion of the data received by the service node. The data received by the service node includes the monitoring data of its own corresponding monitoring terminal and other data corresponding to other nodes. In this embodiment, the monitoring data received locally by the service node and other data forwarded by other nodes can be filtered, combined, or trimmed according to business logic to form the final output data set, i.e., the data to be transmitted, thereby achieving selective encapsulation and targeted output of multi-source monitoring information.

[0077] For example, fields such as timestamps, monitoring terminal device identifiers, data types, and alarm status can be extracted from monitoring data and other data. Based on preset business rules, it can be determined whether each data item belongs to the bed range and event type of the current monitoring client, and the successfully matched data items can be merged to form the data to be transmitted. Another example is that a lightweight preference model can be built based on the historical access behavior of the monitoring client to identify the data categories and update frequencies frequently requested by the monitoring client. Relevant data fragments can be cached in the service node's memory, and the data to be transmitted can be assembled from the cache before each push, thereby reducing real-time computing overhead and improving response efficiency.

[0078] In this embodiment, determining the data to be transmitted based on monitoring data and other data includes: determining the bandwidth information of the second subscription channel; wherein the bandwidth information characterizes the stability of the second subscription channel; and determining the data to be transmitted based on the bandwidth information according to the monitoring data and other data.

[0079] Specifically, bandwidth information refers to operational parameters reflecting the stable data transmission capacity of the second subscription channel per unit time, including but not limited to channel throughput fluctuations, continuous packet loss rate, round-trip latency jitter, and retransmission success rate. Bandwidth information does not necessarily refer to a specific fixed value or protocol layer indicator, but rather is a comprehensive representation of the overall communication reliability of the channel. Bandwidth information is typically used to measure the real-time service capability and disturbance rejection capability of network links or message channels, and is a key environmental variable affecting data distribution strategies. The bandwidth information of the second subscription channel can be determined in real time or periodically, or when the service node needs to send data to the monitoring client.

[0080] For example, before sending data to be transmitted, the bandwidth information can be continuously collected and updated through periodic probe messages, heartbeat feedback response time statistics, or link quality events reported by the underlying driver of the subscription channel, to ensure the timeliness and representativeness of the bandwidth information.

[0081] Monitoring data refers to the raw monitoring data received by the service node from its directly associated monitoring terminal, including but not limited to real-time physiological parameters and status information such as electrocardiogram waveforms, blood pressure trends, blood oxygen saturation, respiratory rate, and alarm events. Other data refers to the same type of monitoring data received by the service node from the first other node via the first subscription channel, corresponding to the monitoring terminals under the jurisdiction of the first other node. Both can maintain consistency in data structure, semantic tags, and timestamp format. Data to be transmitted is the final data set output by the service node to the monitoring client; its composition dynamically changes with the bandwidth information of the second subscription channel and does not have a fixed structure.

[0082] In this embodiment, bandwidth information is used as a control variable in the process of determining the data to be transmitted. Monitoring data and other data are used as candidate data sources. Based on the channel stability level represented by the bandwidth information, the candidate data are selectively combined or prioritized to generate an output dataset adapted to the current channel capabilities. For example, by performing periodic bandwidth probing on the second subscription channel, the quantification level of the current bandwidth information is obtained. If the level is higher than a preset level threshold, the monitoring data and other data are all included in the data to be transmitted and pushed completely according to the original sampling rate and resolution.

[0083] The beneficial effect of this setup is that by introducing the bandwidth information of the second subscription channel as a dynamic decision factor, the originally static data forwarding process is transformed into a closed-loop scheduling mechanism constrained by the network environment. Based on this, monitoring data and other data are no longer forwarded indiscriminately in full, but rather treated as a configurable data resource pool, orchestrated on demand according to the actual carrying capacity of the channel. This allows service nodes to maintain the monitoring client's continuous perception of critical vital signs and alarm information even when facing network fluctuations, bandwidth limitations, or sudden congestion, effectively improving data service quality and system robustness in cross-morphological monitoring scenarios.

[0084] In this embodiment, based on monitoring data and other data, and based on bandwidth information, the data to be transmitted is determined, including: if the bandwidth information meets a first preset condition, then both the monitoring data and other data are determined as data to be transmitted.

[0085] Specifically, a first preset condition is set in advance, which can be used to determine whether the bandwidth information is in a high-quality state. For example, the first preset condition can be that the bandwidth information is continuously higher than a first bandwidth threshold and the fluctuation range is lower than a preset jitter tolerance. Its function is to eliminate instantaneous bandwidth peak interference and ensure that the channel has sustainable guarantee capability when full transmission starts.

[0086] If the bandwidth information meets the first preset condition, it indicates that the channel status between the service node and the monitoring client is good, and the monitoring data and other data received by the service node can be identified as data to be transmitted. That is, the monitoring data and other data are sent to the monitoring client together through the second subscription channel.

[0087] The beneficial effect of this setup is that by using the first preset condition for bandwidth information as the trigger condition for full data distribution, and by leveraging the service node's autonomous perception and real-time response capability to the quality of the second subscription channel, the monitoring client can simultaneously receive all monitoring data from local and cross-node sources when channel resources are sufficient. This avoids the loss of key information due to data pruning and significantly improves the reliability and completeness of collaborative decision-making in critical care scenarios.

[0088] In this embodiment, determining the data to be transmitted based on bandwidth information includes: if the bandwidth information meets a second preset condition, obtaining a first identifier from the monitoring data; wherein the first identifier represents the importance of the monitoring data; and determining the data to be transmitted from the monitoring data according to the first identifier.

[0089] Specifically, if the bandwidth information does not meet the first preset condition, a portion of the monitoring data and other data needs to be used as the data to be transmitted. At this point, it can be determined whether the bandwidth information meets the second or third preset condition. The quality of bandwidth information meeting the third preset condition is lower than that meeting the first preset condition, and the quality of bandwidth information meeting the second preset condition is lower than that meeting the third preset condition. For example, the bandwidth threshold required by the bandwidth information under the first preset condition is higher than the bandwidth threshold required by the bandwidth information under the third preset condition, and the bandwidth threshold required by the bandwidth information under the third preset condition is higher than the bandwidth threshold required by the bandwidth information under the second preset condition.

[0090] If the bandwidth information does not meet the first preset condition, it can be determined whether the bandwidth information meets the third preset condition. If it does, the second identifier can be obtained from other data. The second identifier represents the importance of other data and is transmitted to the service node along with other data. That is, the service node can directly obtain the second identifier of other data.

[0091] Based on the second identifier, the data to be transmitted is determined from other data. For example, other data whose second identifier is a preset identifier can be determined as the data to be transmitted. Furthermore, when the bandwidth information meets the third preset condition, the monitoring data can be determined as the data to be transmitted. In other words, the data to be transmitted at this time includes all the monitoring data and some of the other data.

[0092] When it is determined that the bandwidth information does not meet the third preset condition, it can be determined whether the bandwidth information meets the second preset condition. If it does, then for the monitoring data obtained by the service node from the monitoring terminal, a first identifier for each monitoring data is determined. The first identifier represents the importance of the monitoring data, that is, its priority. When the monitoring terminal collects monitoring data, it can generate a first identifier corresponding to each monitoring data. For example, the first identifier of the monitoring data collected by the monitoring terminal can be determined according to the device type of the monitoring terminal, or it can be determined according to the numerical range of the monitoring data.

[0093] Based on the first identifier, more important data is identified from the monitoring data and designated as the data to be transmitted. For example, monitoring data with the first identifier "001" can be identified as the data to be transmitted, while other monitoring data is not considered as the data to be transmitted. It is worth noting that when the bandwidth information meets the second preset condition, the data to be transmitted is only identified from the monitoring data collected by the monitoring terminal corresponding to the service node, and not from other data. That is, at this time, the monitoring client cannot obtain other data from the first other node to the service node.

[0094] If the bandwidth information does not meet the second preset condition, the monitoring client will be unable to obtain data from the service node and can issue an alarm message to prompt the user to check.

[0095] The advantage of this setup is that by monitoring bandwidth information, important data can be prioritized for transmission, thereby supporting the synchronous visualization and coordinated response of key information by multi-form monitoring terminals under the constraint of limited network resources.

[0096] In this embodiment, the method further includes: identifying data other than the data to be transmitted from the monitoring data and other data as low-level data; compressing the low-level data; and sending the compressed low-level data to the monitoring client through a second subscription channel based on a preset delay time.

[0097] Specifically, low-level data refers to monitoring data and other data that are of lower importance. If both monitoring data and other data are data to be transmitted, then there is no low-level data. In other words, low-level data is monitoring data and other data that were not prioritized for transmission.

[0098] To ensure data integrity, low-level data can be transmitted. Since low-level data is of lower importance, it can be compressed. For example, data redundancy can be reduced to decrease transmission volume, decreasing the number of bytes while maintaining data recoverability or service availability. This reduces the bandwidth consumption of low-level data in the network link and avoids resource contention with the data to be transmitted. In this embodiment, the compression method is not specifically limited. For example, a compact serialization structure can be generated by dictionary encoding of recurring timestamps, device identifiers, and channel type fields in the low-level data.

[0099] A pre-set delay time is configured, representing the time offset by which low-level data transmission is allowed to be delayed. After the low-level data is compressed, it is sent to the monitoring client via the second subscription channel after the preset delay time.

[0100] The beneficial effects of this setup are that data not selected for transmission is explicitly defined as low-level data, its size is reduced through compression, and it is retransmitted via the same second subscription channel when the preset delay time allows for opportunistic retransmission. Compression improves the information carrying efficiency per unit bandwidth, and the delay time enables spatiotemporal peak scheduling of network resources. This avoids delays or packet loss of critical data due to bandwidth contention, and also prevents the permanent loss of secondary data. This allows the monitoring client to meet both real-time response and historical backtracking needs under different network conditions, thereby improving the overall service quality and clinical applicability of the cross-mode monitoring system.

[0101] S303. Based on the second subscription channel, the data to be transmitted is sent to the monitoring client.

[0102] For example, the second subscription channel represents a data subscription channel between the service node and the monitoring client, used to establish a stable and scalable data flow path between the service node and the monitoring client. The monitoring client can receive the data to be transmitted from the service node through the second subscription channel.

[0103] This embodiment achieves targeted distribution of multi-source monitoring data by introducing an intermediate data decision-making step involving the data to be transmitted. This not only avoids the redundant transmission and resource waste caused by indiscriminate forwarding, but also provides an operable data object foundation for dynamic control strategies based on bandwidth information. Thus, while ensuring the real-time nature of critical clinical information, it improves the overall data distribution efficiency and network adaptability of the system.

[0104] This application provides a data transmission method based on a monitoring client. A service node, acting as a backend node of a distributed gateway, receives raw monitoring data uploaded by its corresponding monitoring terminal and simultaneously acquires monitoring data from other subscribed service nodes through a first subscription channel, thus achieving comprehensive data acquisition. The acquired data is then sent to the monitoring client via a second subscription channel. The service node acts as a data aggregation point, using a subscription mechanism to acquire data from other service nodes and then pushing the integrated data stream to the monitoring client through an independent downlink channel. This allows the monitoring client to obtain a global perspective without directly connecting to multiple data sources. By constructing data subscription channels between service nodes and between service nodes and clients, cross-terminal and cross-node data sharing is achieved, breaking the traditional one-to-one binding model, improving the flexibility and scalability of data transmission, and enhancing the user's data viewing experience.

[0105] Figure 4 This is a schematic diagram of a data transmission device based on a monitoring client, provided as an embodiment of this application. Figure 4 As shown, the data transmission device 40 based on a monitoring client provided in this embodiment includes:

[0106] The data receiving unit 401 is used to receive monitoring data uploaded by the monitoring terminal corresponding to the service node, and to receive other data transmitted by the first other node based on the first subscription channel; wherein, the first subscription channel represents the data subscription channel between the service node and the first other node, the first other node represents the other service nodes subscribed to by the service node, and the other data represents the monitoring data uploaded by the monitoring terminal corresponding to the first other node received by the first other node.

[0107] The data sending unit 402 is used to send monitoring data and other data to the monitoring client based on the second subscription channel; wherein, the second subscription channel represents the data subscription channel between the service node and the monitoring client, and the monitoring client includes at least one.

[0108] In one possible implementation, the data sending unit 402 includes:

[0109] The data determination module is used to determine the data to be transmitted based on monitoring data and other data.

[0110] The data transmission module is used to send the data to be transmitted to the monitoring client based on the second subscription channel.

[0111] In one possible implementation, the data determination module is specifically used for:

[0112] Determine the bandwidth information of the second subscription channel; whereby the bandwidth information characterizes the stability of the second subscription channel.

[0113] Based on monitoring data and other data, and using bandwidth information, the data to be transmitted is determined.

[0114] In one possible implementation, the data determination module is specifically used for:

[0115] If the bandwidth information meets the first preset condition, then the monitoring data and other data will both be identified as data to be transmitted.

[0116] In one possible implementation, the data determination module is specifically used for:

[0117] If the bandwidth information meets the second preset condition, then the first identifier is obtained from the monitoring data; wherein, the first identifier represents the importance of the monitoring data;

[0118] Based on the first identifier, the data to be transmitted is determined from the monitoring data.

[0119] One possible implementation also includes:

[0120] The low-level determination unit is used to determine the data other than the data to be transmitted from the monitoring data and other data as low-level data;

[0121] The compression processing unit is used to compress low-level data and send the compressed low-level data to the monitoring client through the second subscription channel based on a preset delay time.

[0122] One possible implementation also includes:

[0123] The data transmission unit is used to transmit the received monitoring data to the second other node based on the third subscription channel; wherein the third subscription channel represents the data subscription channel between the service node and the second other node, and the second other node represents other service nodes that have subscribed to the service node.

[0124] One possible implementation also includes:

[0125] The list sending unit is used to send the authorized whitelist corresponding to the service node to the second other node in response to any data subscription request from the second other node; wherein, the authorized whitelist includes multiple terminal identifiers, and the terminal identifiers represent the monitoring terminals that the second other node is allowed to subscribe to from the service node; the authorized whitelist is used to instruct the second other node to determine the required terminal identifier from the authorized whitelist in order to obtain the monitoring data corresponding to the required terminal identifier from the service node.

[0126] One possible implementation also includes:

[0127] The data storage unit is used to store the received monitoring data as historical data and associate the historical data with the receiving time.

[0128] One possible implementation also includes:

[0129] The data review unit is used to respond to the data review command and obtain the set of historical data within a preset time period according to the receiving time corresponding to each historical data.

[0130] The historical data sending unit is used to send a set of historical data within a preset time period to the monitoring client.

[0131] This embodiment provides a data transmission device based on a monitoring client, which can execute the method provided in the above method embodiment. Its implementation principle and technical effect are similar, and will not be described in detail here.

[0132] This application also provides a data transmission system based on a monitoring client, the system including multiple service nodes, of which at least a first service node and a second service node are included;

[0133] The first service node is used to receive monitoring data uploaded by the monitoring terminal corresponding to the first service node and other data transmitted by the second service node through the first subscription channel; and to transmit the received monitoring data and other data to the corresponding monitoring client through the second subscription channel; wherein, the other data represents the monitoring data uploaded by the monitoring terminal corresponding to the second service node received by the second service node.

[0134] The second service node is used to transmit other received data to the first service node through the first subscription channel.

[0135] The first service node can be any service node in the method embodiments of this application, and the second service node is the first other node of that arbitrary service node.

[0136] Figure 5 This is a schematic diagram of the structure of an electronic device provided in this application. Figure 5 As shown, the electronic device 50 provided in this embodiment includes at least one processor 501 and a memory 502. Optionally, the device 50 further includes a communication component 503. The processor 501, memory 502, and communication component 503 are connected via a bus 504.

[0137] In a specific implementation, at least one processor 501 executes computer execution instructions stored in memory 502, causing at least one processor 501 to perform the above-described method.

[0138] The specific implementation process of processor 501 can be found in the above method embodiments, and its implementation principle and technical effect are similar. It will not be repeated here.

[0139] In the above embodiments, it should be understood that the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules within the processor.

[0140] The memory may include random access memory (RAM) and may also include non-volatile memory (NVM), such as at least one disk storage device.

[0141] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.

[0142] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described method.

[0143] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the above-described method.

[0144] The aforementioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The readable storage medium can be any available medium accessible to a general-purpose or special-purpose computer.

[0145] An exemplary readable storage medium is coupled to a processor, enabling the processor to read information from and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can reside in an Application Specific Integrated Circuit (ASIC). Alternatively, the processor and the readable storage medium can exist as discrete components in the device.

[0146] The division of units is merely a logical functional division; in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices, or units, and may be electrical, mechanical, or other forms.

[0147] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0148] In addition, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0149] If a function is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0150] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

[0151] Finally, it should be noted that other embodiments of the invention will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This invention is intended to cover any variations, uses, or adaptations of the invention that follow the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein, and is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of the invention is limited only by the appended claims.

Claims

1. A data transmission method based on a monitoring client, characterized in that, The method is applied to a service node, which is a backend node connected to the distributed gateway; the method includes: The system receives monitoring data uploaded by the monitoring terminal corresponding to the service node, and receives other data transmitted by the first other node based on the first subscription channel; wherein, the first subscription channel represents the data subscription channel between the service node and the first other node, the first other node represents other service nodes subscribed to by the service node, and the other data represents the monitoring data uploaded by the monitoring terminal corresponding to the first other node received by the first other node. Based on the second subscription channel, the monitoring data and the other data are sent to the monitoring client; wherein, the second subscription channel represents the data subscription channel between the service node and the monitoring client, and the monitoring client includes at least one.

2. The method according to claim 1, characterized in that, Based on the second subscription channel, the monitoring data and the other data are sent to the monitoring client, including: Based on the monitoring data and the other data, determine the data to be transmitted; The data to be transmitted is sent to the monitoring client via the second subscription channel.

3. The method according to claim 2, characterized in that, Based on the monitoring data and the other data, the data to be transmitted is determined, including: Determine the bandwidth information of the second subscription channel; wherein the bandwidth information characterizes the stability of the second subscription channel; Based on the monitoring data and the other data, and using the bandwidth information, the data to be transmitted is determined.

4. The method according to claim 3, characterized in that, Based on the monitoring data and the other data, and using the bandwidth information, the data to be transmitted is determined, including: If the bandwidth information meets the first preset condition, then the monitoring data and the other data are both determined as the data to be transmitted.

5. The method according to claim 3, characterized in that, Based on the bandwidth information, the data to be transmitted is determined, including: If the bandwidth information meets the second preset condition, then a first identifier is obtained from the monitoring data; wherein, the first identifier represents the importance of the monitoring data; The data to be transmitted is determined from the monitoring data based on the first identifier.

6. The method according to claim 5, characterized in that, Also includes: The data other than the data to be transmitted among the monitoring data and the other data are identified as low-level data; The low-level data is compressed, and based on a preset delay time, the compressed low-level data is sent to the monitoring client through the second subscription channel.

7. The method according to claim 1, characterized in that, Also includes: Based on the third subscription channel, the received monitoring data is transmitted to the second other node; wherein, the third subscription channel represents the data subscription channel between the service node and the second other node, and the second other node represents other service nodes that have subscribed to the service node.

8. The method according to claim 1, characterized in that, Also includes: In response to a data subscription request from any second other node, the authorized whitelist corresponding to the service node is sent to the second other node; wherein, the authorized whitelist includes multiple terminal identifiers, and the terminal identifiers represent the monitoring terminals that the second other node is allowed to subscribe to from the service node; The authorized whitelist is used to instruct other nodes to determine the required terminal identifier from the authorized whitelist in order to obtain the monitoring data corresponding to the required terminal identifier from the service node.

9. The method according to any one of claims 1-8, characterized in that, Also includes: The received monitoring data is treated as historical data, and the historical data is stored in association with the receiving time.

10. The method according to claim 9, characterized in that, Also includes: In response to the data review command, the system retrieves a set of historical data within a preset time period based on the receiving time corresponding to each historical data point. The historical data set within the preset time period is sent to the monitoring client.

11. A data transmission system based on a monitoring client, characterized in that, The system includes a plurality of service nodes as described in any one of claims 1-10, wherein the plurality of service nodes includes at least a first service node and a second service node; The first service node is used to receive monitoring data uploaded by the monitoring terminal corresponding to the first service node and other data transmitted by the second service node through the first subscription channel; And, for transmitting the received monitoring data and other data to the corresponding monitoring client through the second subscription channel; wherein, the other data represents the monitoring data uploaded by the monitoring terminal corresponding to the second service node and received by the second service node; The second service node is used to transmit the other data received to the first service node through the first subscription channel.

12. An electronic device, characterized in that, include: Memory, processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory, causing the processor to perform the method as described in any one of claims 1-10.

13. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1-10.

14. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the method described in any one of claims 1-10.

Images