A data transmission method and system based on distributed data center

Abstract

The present application discloses a data transmission method and system based on a distributed data middle station, which is used to solve the technical problem that the existing data middle station architecture solution is costly for small and medium-sized enterprises. Among them, each edge service node determines the current state of its corresponding virtual host or lightweight application container, and uses the edge service node corresponding to the virtual host or lightweight application container in the online state as the online edge service node; the online edge service node determines the address of its corresponding virtual host or lightweight application container, and sends the address to the client; the online edge service node receives the request data packet sent by the client, and stores the request data packet in the disk of the virtual host or lightweight application container corresponding to the online edge service node; the online edge service node forwards several request data packets stored in the disk of its corresponding virtual host or lightweight application container to the data middle station according to the preset time interval.

Description

Technical Field

[0001] The present application relates to the field of big data technology, and in particular to a data transmission method and system based on a distributed data middle station. Background Art

[0002] In recent years, various industries have gradually deepened their understanding of big data systems, and big data applications have become increasingly mature. The demand for building big data systems has also gradually shifted from large enterprises and Internet giants to small and medium-sized enterprises. The big data products provided by cloud computing suppliers include data collection, data storage, data cleaning, data analysis, data display and data application from top to bottom, and each link has its corresponding product. The products are interconnected and data is interoperable, which can be used out of the box and respond promptly and efficiently. Big data product solutions and technical support services bring many conveniences to small and medium-sized enterprises, especially the rapid construction of data centers in the start-up period.

[0003] However, the big data products provided by cloud vendors also have some disadvantages, such as high capital cost, inability to be highly customized, and deep coupling of technology selection with cloud platforms. For a small or medium-sized data middle platform system, enterprises need to continuously invest in service rental fees, which is costly. Therefore, most small and medium-sized enterprises choose to build their own data middle platforms to meet their own computing and storage resource needs, but the cost of existing data middle platform architecture solutions on the market is still relatively high. For small and medium-sized enterprises, using high-performance data services still requires a lot of capital and operating costs. Summary of the invention

[0004] The embodiments of the present application provide a data transmission method and system based on a distributed data middle platform, so as to solve the technical problem that the existing data middle platform architecture solution is relatively costly for small and medium-sized enterprises.

[0005] On the one hand, an embodiment of the present application provides a data transmission method based on a distributed data middle platform, including: each edge service node determines the current status of its corresponding virtual host or lightweight application container, and uses the edge service node corresponding to the virtual host or lightweight application container in an online state as an online edge service node; wherein the current state includes an online state and an offline state; the online edge service node determines the address of its corresponding virtual host or lightweight application container, and sends the address to the client so that the client can send data to the online edge service node; the online edge service node receives the request data packet sent by the client, and stores the request data packet in the disk of the virtual host or lightweight application container corresponding to the online edge service node; the online edge service node forwards several request data packets stored in the disk of its corresponding virtual host or lightweight application container to the data middle platform at preset time intervals.

[0006] In one implementation of the present application, after the online edge service node determines the address of its corresponding virtual host or lightweight application container and sends the address to the client, the method also includes: the client receives an address list consisting of the addresses of multiple online edge service nodes, and traverses and accesses the interfaces corresponding to each online edge service node through the address list to determine the link status of the interface; the client determines the load capacity and response time of the corresponding online edge service node according to the link status of the interface; the client determines the target edge service node for uploading the request data packet from the online edge service nodes according to the load capacity and response time.

[0007] In one implementation of the present application, a target edge service node for uploading a request data packet is determined from online edge service nodes based on load capacity and response time, specifically including: a client determines a first priority value and a second priority value corresponding to each online edge service node, respectively; wherein the first priority value corresponds to the load capacity of the online edge service node, and the second priority value corresponds to the response time of the online edge service node; the client determines a weight corresponding to the load capacity and a weight corresponding to the response time, respectively, and performs a weighted summation of the load capacity and the response time based on the weight, the first priority value, and the second priority value; the client sorts the results of the weighted summation to obtain a corresponding result sequence, and determines, based on the result sequence, a target edge service node for uploading the request data packet from the online edge service nodes.

[0008] In one implementation of the present application, the client determines the first priority value and the second priority value corresponding to each online edge service node respectively, specifically including: the client arranges each online edge service node in the order of its load capacity to obtain a corresponding load capacity sequence; and according to the order of each online edge service node in the load capacity sequence, determines in sequence the first priority value corresponding to each online edge service node; the client arranges the online edge service nodes in the order of their response time to obtain a corresponding response time sequence; and according to the order of each online edge service node in the response time sequence, determines in sequence the second priority value corresponding to each online edge service node.

[0009] In one implementation of the present application, after determining the target edge service node for uploading the request data packet, the method also includes: the client determines a target edge service node sequence composed of the target edge service nodes; the client adopts a weighted polling strategy to upload the request data packet to the corresponding target edge service nodes in sequence; when the request data packet is successfully uploaded to the target edge service node, the client uploads the request data packet again to the next target edge service node of the target edge service node based on the target edge service node sequence.

[0010] In one implementation of the present application, the method also includes: when the client fails to successfully upload a request data packet to the target edge service node, the client retries uploading the request data packet to the next target edge service node of the current target edge service node in the order of arrangement of each target edge service node in the target edge service node sequence until the request data packet is successfully uploaded to any target edge service node.

[0011] In one implementation of the present application, the method also includes: the data middle station reports the export IP address of the data middle station to the edge service node through the IP address reporting program deployed in the data middle station; the edge service node reports the address of the virtual host or lightweight application container corresponding to the edge service node, as well as the IP address of the data middle station to other edge service nodes and the data middle station respectively through the IP address reporting program deployed in the edge service node.

[0012] In one implementation of the present application, the method also includes: when the export IP address of the data middle station is changed, the data middle station reports the export IP address of the data middle station to the edge service node through the IP address reporting program deployed in the data middle station; when the edge service node cannot access the data middle station, the edge service node inquires the adjacent edge service node or data middle station about the export IP address of the data middle station.

[0013] In one implementation of the present application, virtual hosts or lightweight application containers are deployed in a clustered manner to structure edge services.

[0014] On the other hand, an embodiment of the present application also provides a data transmission system based on a distributed data middle platform, the system including: an edge service node and a client; each edge service node is used to determine the current status of its corresponding virtual host or lightweight application container, and use the edge service node corresponding to the virtual host or lightweight application container in an online state as an online edge service node; wherein the current state includes an online state and an offline state; the online edge service node is used to determine the address of its corresponding virtual host or lightweight application container, and send the address to the client so that the client can send data to the online edge service node; the online edge service node is used to receive a request data packet sent by the client, and store the request data packet in the disk of the virtual host or lightweight application container corresponding to the online edge service node; the online edge service node is used to forward several request data packets stored in the disk of its corresponding virtual host or lightweight application container to the data middle platform at preset time intervals.

[0015] The data transmission method and system based on the distributed data middle station provided by the embodiment of the present application have at least the following beneficial effects: the edge service of the cloud resource architecture such as virtual host or lightweight application container can significantly reduce the system architecture cost on the basis of satisfying the data computing and storage functions, and is suitable for small and medium-sized enterprises that are more sensitive to costs. In addition, each edge service node adopts the storage and forwarding mode, which greatly reduces the dependence on hardware resources, realizes the architecture of high-performance edge services on low-performance hardware, and makes full use of network resources. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0017] Figure 1 A flowchart of a data transmission method based on a distributed data middle station provided in an embodiment of the present application;

[0018] Figure 2 A functional schematic diagram of a client provided in an embodiment of the present application;

[0019] Figure 3 A functional schematic diagram of an edge service node provided in an embodiment of the present application;

[0020] Figure 4 A functional schematic diagram of a data center provided in an embodiment of the present application;

[0021] Figure 5 An overall architecture diagram of a data transmission system based on a distributed data middle station provided in an embodiment of the present application. DETAILED DESCRIPTION

[0022] In order to make the purpose, technical solution and advantages of the present application clearer, the technical solution of the present application will be clearly and completely described below in combination with the specific embodiments of the present application and the corresponding drawings. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present application.

[0023] The technical solution proposed in the embodiments of the present application is described in detail below with reference to the accompanying drawings.

[0024] Figure 1 A flow chart of a data transmission method based on a distributed data middle station provided in an embodiment of the present application. Figure 1As shown, the data transmission method based on the distributed data middle station provided in the embodiment of the present application can mainly include the following steps:

[0025] S101. Each edge service node determines the current state of its corresponding virtual host or lightweight application container, and uses the edge service node corresponding to the virtual host or lightweight application container in an online state as an online edge service node.

[0026] The current status includes online status and offline status.

[0027] In an embodiment of the present application, multiple virtual hosts or lightweight application containers are used to construct edge services in a clustered deployment manner, and form corresponding multiple edge service nodes. Each edge service node needs to determine that the current state of its corresponding virtual host or lightweight application container is online or offline, wherein the edge service node corresponding to the online virtual host or lightweight application container serves as an online edge service node for subsequent data transmission. Virtual hosts and lightweight application containers generally include a small scripting engine (PHP, Python) with a small amount of file or data storage capacity and low price, and using it to set up edge services can greatly reduce costs. The clustered deployment method makes up for the defect of insufficient system performance during access peaks, and can effectively cope with high concurrent access.

[0028] S102: The online edge service node determines the address of the corresponding virtual host or lightweight application container, and sends the address to the client, so that the client sends a request data packet to the online edge service node.

[0029] In an embodiment of the present application, the online edge service node determines the address (IP address or domain name) of its corresponding virtual host or lightweight application container, and sends the address to the client, so that the client can send a request data packet and determine the online edge service node for uploading the request data packet.

[0030] In one embodiment, the client receives an address list consisting of the addresses of multiple online edge service nodes, and traverses the interfaces of the online edge service nodes in the access list through the address list to determine the corresponding link status. Afterwards, the load capacity and response time of the corresponding online edge service node are determined respectively according to the link status of each interface. Each edge service node has an interface for exposing its own load status and health status. The client accesses the interface corresponding to each edge service node in turn, so as to obtain the load capacity corresponding to the node. At the same time, the client will also ping each edge service node in turn to determine the response time corresponding to each node. Based on the load capacity and response time, the client will select some edge service nodes with stronger load capacity and shorter response time from each online edge service node as the target edge service node for uploading the request data packet.

[0031] Specifically, the client determines the first priority value and the second priority value corresponding to each online edge service node respectively. Among them, the first priority value is used to represent the load capacity of the edge service node, and the second priority value is used to represent the request response time of the edge service node. That is, the online edge service nodes are arranged in the order of their load capacity to obtain a corresponding load capacity sequence; and according to the order of the online edge service nodes in the load capacity sequence, the first priority value corresponding to each online edge service node is determined in turn. In addition, the client arranges the online edge service nodes in the order of their response time to obtain a corresponding response time sequence; and according to the order of the online edge service nodes in the response time sequence, the second priority value corresponding to each online edge service node is determined in turn.

[0032] Further, the weight corresponding to the load capacity and the weight corresponding to the response time are determined respectively, and the load capacity and the response time are weightedly summed according to the weight, the first priority value and the second priority value to obtain a corresponding weighted summation result.

[0033] Furthermore, the client sorts the weighted sum of the load capacity and response time corresponding to each edge service node to obtain a corresponding result sequence. The result sequence can be arranged in descending order or ascending order. Then, from each online edge service node, some nodes with strong load capacity and short response time are selected as target edge nodes according to the order of the result sequence.

[0034] For example, there are five edge service nodes, namely node 1, node 2, node 3, node 4 and node 5, and they are all online. The client traverses and accesses the interfaces corresponding to the above edge service nodes. The load capacity of each edge service node is arranged in descending order as node 3, node 4, node 2, node 5, and node 1, and the corresponding first priority values ​​are set to 5, 4, 3, 2, and 1; the response time is arranged in descending order as node 5, node 4, node 1, node 2, and node 3, and the corresponding second priority values ​​are also set to 5, 4, 3, 2, and 1. Assuming that the weight corresponding to the load capacity is 0.6 and the weight corresponding to the response time is 0.4, the weighted sum corresponding to each edge service node is obtained by weighted summation as 1.8, 2.6, 3.4, 4, and 3.2, among which node 4 has a relatively strong load capacity and a low response time. Arrange the above summation results in descending order to obtain the result sequence node 4, node 3, node 5, node 2, and node 1. The client can select the target edge service node from the result sequence in order.

[0035] In one embodiment, the client determines a target edge service sequence consisting of target edge service nodes, and then uses a weighted round-robin load strategy to load a request data packet to the target edge service node. When uploading data, the client will upload the same request data packet to the virtual hosts or lightweight application containers corresponding to the two target edge service nodes at the same time. That is to say, if the request data packet is successfully uploaded to a target edge service node, the client will upload the request data packet again to the next target edge service node of the current target edge service node in the order of the target edge service node sequence. If the request data packet sent by the client fails to upload, it will continue to try to upload the request data packet to the next target edge service node of the current target edge service node in the order of the target edge service nodes in the target edge service node sequence until the request data packet is successfully uploaded to any target edge service node.

[0036] Distributing client requests to multiple online edge service nodes in the cluster increases the system throughput, avoids device overload, and achieves load balancing. At the same time, the client selects nodes with relatively low load and relatively short response time from each edge service node to upload the request data packet, achieving the selection of the optimal link without additional cost. The data double upload and retry mechanism further ensures the stability and security of the data.

[0037] S103: The online edge service node receives the request data packet sent by the client, and stores the request data packet in a disk of a virtual host or a lightweight application container corresponding to the online edge service node.

[0038] In an embodiment of the present application, each online edge service node will not forward the request data packet immediately after receiving it, but will temporarily store the request data packet in the disk of the corresponding virtual host or lightweight application container. It should be noted that the online edge service node mentioned here represents the target edge service node in the online edge service node. In this way, the CPU and memory resources of the virtual host or lightweight application container are only used for protocol processing, which reduces the use requirements of CPU and memory resources and makes full use of network resources.

[0039] S104. The online edge service node forwards several request data packets stored in the disk of its corresponding virtual host or lightweight application container to the data center at a preset time interval.

[0040] In the embodiment of the present application, after the request data packet is successfully uploaded, the online edge service node will forward the request data packet temporarily stored in the disk to the data center at a preset time interval to achieve timed batch forwarding of data. Therefore, the online edge service node will not perform other operations on the request data packet sent by the client except for storage and forwarding. Using the "store and forward" architecture mode to implement edge services can greatly reduce the dependence on hardware resources and improve the throughput of the system.

[0041] In one embodiment, both the data center and the edge service node are deployed with an IP address reporting program with the same identity. If the online edge service node is to successfully forward the request data packet to the data center, each online edge service node needs to know the address of the data center.

[0042] Specifically, the data center reports the export IP address of the data center to the edge service node through the IP address reporting program deployed in the data center. At the same time, the edge service node will also report the address of the virtual host or lightweight application container corresponding to the edge service node and the IP address of the data center to other edge service nodes and the data center through the IP address reporting program deployed therein. Through this distributed peer-to-peer network service discovery mechanism, each edge service node and the data center can automatically understand each other, thereby achieving normal data transmission.

[0043] In one embodiment, the IP address will change with the expiration of the lease or the restart of the router, and the data middle station needs to rely on the export IP address for external services. If the export IP changes, the edge service node will not be able to find the data middle station, and the system will be unavailable. When the export IP address of the data middle station is changed, in order to enable the edge service node to discover the new export IP address in time, the IP address reporting program of the data middle station will report the export IP address of the data middle station to the edge service node, and then through inquiries between each node, the new export IP address can be propagated to all edge service nodes. Correspondingly, if the edge service node cannot access the data middle station, it can ask the neighboring edge service node or data middle station for the export IP address of the data middle station. The service discovery of intranet services on the public network is realized through the identity-peer service discovery mechanism, and the data middle station service address can be updated in time and automatically without the need for additional hardware resources. There is no need for manual configuration when adding or offline nodes.

[0044] Figure 2 A functional schematic diagram of a client provided in an embodiment of the present application. Figure 2As shown in the figure, when the client uploads a request data packet, it selects some nodes with lower load and shorter response time from multiple online edge service nodes as the target edge service nodes, and uploads the request data packet to the above target edge service nodes through weighted polling, thus achieving client load balancing and optimal line selection for data upload. At the same time, data dual upload and retry further improve the security and stability of data.

[0045] Figure 3 A functional diagram of an edge service node provided in an embodiment of the present application. Figure 3 As shown in the figure, the functions implemented by the edge service node are mainly service discovery, data collection, and storage and forwarding. The edge service node collects request data packets from the client, and conducts service discovery with the data center through the IP address reporting program of the corresponding virtual host or lightweight application container, thereby forwarding the request data packets stored on the disk to the data center.

[0046] Figure 4 This is a functional diagram of a data center provided in an embodiment of the present application. Figure 4 As shown, the functions of the data center are service discovery and data reception, that is, the data center establishes a connection with the edge service node through a distributed identity peer service discovery mechanism to receive the corresponding request data packet.

[0047] The above is an embodiment of the method proposed in this application. Based on the same inventive concept, the embodiment of this application also provides a data transmission system based on a distributed data middle station, and its overall architecture is as follows Figure 5 shown.

[0048] like Figure 5 As shown, a data transmission system based on a distributed data middle station provided by an embodiment of the present application includes a client, an edge service node and a data middle station. Based on multiple virtual hosts, the corresponding edge service nodes are respectively constructed, and an edge service cluster is formed by clustered deployment. After the client issues an application request, the edge service node receives the corresponding request data packet and stores it on the disk, and then forwards it to the data middle station in batches at regular intervals. The data flows from the client to the edge service node and is finally transmitted to the data middle station. The edge service node and the data middle station use a distributed peer-to-peer service discovery mode for service discovery, that is, the edge service node can report its IP address or domain name to the adjacent node or the data middle station. Among them, the domain name is set for the situation where the IP address is reused in the clustered deployment. Similarly, the data middle station can also report its IP address to each edge service node. After the edge service node and the data middle station know each other's addresses, the data can be forwarded from the edge service node to the data middle station.

[0049] In one embodiment of the present application, each edge service node is used to determine the current state of its corresponding virtual host or lightweight application container, and use the edge service node corresponding to the virtual host or lightweight application container in an online state as an online edge service node; wherein the current state includes an online state and an offline state; the online edge service node is used to determine the address of its corresponding virtual host or lightweight application container, and send the address to the client so that the client can send data to the online edge service node; the online edge service node is used to receive a request data packet sent by the client, and store the request data packet in the disk of the virtual host or lightweight application container corresponding to the online edge service node; the online edge service node is used to forward several request data packets stored in the disk of its corresponding virtual host or lightweight application container to the data center at preset time intervals.

[0050] In one embodiment of the present application, the client is used to receive an address list consisting of addresses of multiple online edge service nodes, and to traverse and access the interfaces corresponding to each online edge service node through the address list to determine the link status of the interface; the client is used to determine the load capacity and response time of the corresponding online edge service node according to the link status of the interface; the client is used to determine the target edge service node for uploading a request data packet from the online edge service nodes according to the load capacity and response time.

[0051] In one embodiment of the present application, the client is used to respectively determine a first priority value and a second priority value corresponding to each online edge service node; wherein the first priority value corresponds to the load capacity of the online edge service node, and the second priority value corresponds to the response time of the online edge service node; the client is used to respectively determine a weight corresponding to the load capacity and a weight corresponding to the response time, and perform a weighted sum of the load capacity and the response time according to the weight, the first priority value and the second priority value; the client is used to sort the results of the weighted summation to obtain a corresponding result sequence, and according to the result sequence, determine a target edge service node for uploading a request data packet from the online edge service nodes.

[0052] In one embodiment of the present application, the client is used to arrange each online edge service node in the order of its load capacity to obtain a corresponding load capacity sequence; and according to the order of each online edge service node in the load capacity sequence, determine the first priority value corresponding to each online edge service node in sequence; the client is used to arrange the online edge service nodes in the order of their response time to obtain a corresponding response time sequence; and according to the order of each online edge service node in the response time sequence, determine the second priority value corresponding to each online edge service node in sequence.

[0053] In one embodiment of the present application, the client is used to determine a target edge service node sequence consisting of various target edge service nodes; the client is used to adopt a weighted polling strategy to upload request data packets to the corresponding target edge service nodes in sequence; the client is used to upload the request data packet again to the next target edge service node of the target edge service node based on the target edge service node sequence when the request data packet is successfully uploaded to the target edge service node.

[0054] In one embodiment of the present application, when a request data packet is not successfully uploaded to a target edge service node, the client is used to retry uploading the request data packet to the next target edge service node of the current target edge service node in the order of arrangement of each target edge service node in the target edge service node sequence until the request data packet is successfully uploaded to any target edge service node.

[0055] In one embodiment of the present application, the data middle station is used to report the export IP address of the data middle station to the edge service node through the IP address reporting program deployed in the data middle station; the edge service node is used to report the address of the virtual host or lightweight application container corresponding to the edge service node, as well as the IP address of the data middle station to other edge service nodes and the data middle station respectively through the IP address reporting program deployed in the edge service node.

[0056] In one embodiment of the present application, the data middle station is used to report the export IP address of the data middle station to the edge service node through the IP address reporting program deployed in the data middle station when the export IP address of the data middle station is changed; the edge service node is used to inquire the export IP address of the data middle station from the adjacent edge service node or data middle station when the edge service node cannot access the data middle station.

[0057] In one embodiment of the present application, a virtual host or a lightweight application container is used to structure edge services in a clustered deployment manner.

[0058] Each embodiment in this application is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0059] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0060] The above is only an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. A data transmission method based on a distributed data center, characterized in that: The method comprises: Each edge service node determines the current state of its corresponding virtual host or lightweight application container, and uses the edge service node corresponding to the virtual host or lightweight application container in an online state as an online edge service node; wherein the current state includes an online state and an offline state; The online edge service node determines the address of the corresponding virtual host or lightweight application container, and sends the address to the client, so that the client can send data to the online edge service node; The online edge service node receives the request data packet sent by the client, and stores the request data packet in a disk of a virtual host or a lightweight application container corresponding to the online edge service node; The online edge service node forwards several request data packets stored in the disk of its corresponding virtual host or lightweight application container to the data center at a preset time interval; After the online edge service node determines the address of the corresponding virtual host or lightweight application container and sends the address to the client, the method further includes: The client receives an address list consisting of addresses of a plurality of the online edge service nodes, and traverses and accesses interfaces corresponding to each of the online edge service nodes through the address list to determine a link status of the interface; The client determines the load capacity and response time of the corresponding online edge service node according to the link status of the interface; The client determines, from the online edge service nodes, a target edge service node for uploading the request data packet according to the load capacity and the response time.

2. According to claim 1, a data transmission method based on a distributed data middle station is characterized in that: Determining, from the online edge service nodes, a target edge service node for uploading the request data packet according to the load capacity and the response time, specifically includes: The client determines a first priority value and a second priority value corresponding to each online edge service node respectively; wherein the first priority value corresponds to the load capacity of the online edge service node, and the second priority value corresponds to the response time of the online edge service node; The client determines a weight corresponding to the load capacity and a weight corresponding to the response time respectively, and performs a weighted summation of the load capacity and the response time according to the weight, the first priority value and the second priority value; The client sorts the weighted sum results to obtain a corresponding result sequence, and determines a target edge service node for uploading the request data packet from the online edge service nodes according to the result sequence.

3. According to claim 2, a data transmission method based on a distributed data middle station is characterized in that: The client determines the first priority value and the second priority value corresponding to each online edge service node respectively, specifically including: The client arranges the online edge service nodes in order of their load capacity to obtain a corresponding load capacity sequence; and determines the first priority value corresponding to each online edge service node in sequence according to the order of the online edge service nodes in the load capacity sequence; The client arranges the online edge service nodes in the order of their response time to obtain a corresponding response time sequence; and determines the second priority value corresponding to each online edge service node in turn according to the order of each online edge service node in the response time sequence.

4. According to claim 1, a data transmission method based on a distributed data middle station is characterized in that: After determining the target edge service node for uploading the request data packet, the method further includes: The client determines a target edge service node sequence consisting of the target edge service nodes; The client adopts a weighted polling strategy to upload the request data packets to the corresponding target edge service nodes in sequence; When the request data packet is successfully uploaded to the target edge service node, the client uploads the request data packet again to the next target edge service node of the target edge service node based on the target edge service node sequence.

5. According to claim 4, a data transmission method based on a distributed data middle station is characterized in that: The method further comprises: When the request data packet is not successfully uploaded to the target edge service node, the client retries to upload the request data packet to the next target edge service node of the current target edge service node in the order of arrangement of the target edge service nodes in the target edge service node sequence until the request data packet is successfully uploaded to any target edge service node.

6. According to claim 1, a data transmission method based on a distributed data middle station is characterized in that: The method further comprises: The data middle station reports the egress IP address of the data middle station to the edge service node through the IP address reporting program deployed in the data middle station; The edge service node reports the address of the virtual host or lightweight application container corresponding to the edge service node and the IP address of the data center to other edge service nodes and the data center through the IP address reporting program deployed in the edge service node.

7. A data transmission method based on a distributed data middle station according to claim 6, characterized in that: The method further comprises: When the egress IP address of the data center is changed, the data center reports the egress IP address of the data center to the edge service node through the IP address reporting program deployed in the data center; When the edge service node cannot access the data middle station, the edge service node inquires the egress IP address of the data middle station from the adjacent edge service node or the data middle station.

8. A data transmission method based on a distributed data middle station according to claim 1, characterized in that: The virtual host or lightweight application container is deployed in a clustered manner to structure the edge service.

9. A data transmission system based on a distributed data middle station, characterized in that: The system comprises: an edge service node and a client; Each edge service node is used to determine the current state of its corresponding virtual host or lightweight application container, and use the edge service node corresponding to the virtual host or lightweight application container in an online state as an online edge service node; wherein the current state includes an online state and an offline state; The online edge service node is used to determine the address of the corresponding virtual host or lightweight application container, and send the address to the client, so that the client can send data to the online edge service node; The online edge service node is used to receive the request data packet sent by the client, and store the request data packet in a disk of a virtual host or a lightweight application container corresponding to the online edge service node; The online edge service node is used to forward several request data packets stored in the disk of its corresponding virtual host or lightweight application container to the data center according to a preset time interval; The client receives an address list consisting of addresses of a plurality of the online edge service nodes, and traverses and accesses interfaces corresponding to each of the online edge service nodes through the address list to determine a link status of the interface; The client determines the load capacity and response time of the corresponding online edge service node according to the link status of the interface; The client determines, from the online edge service nodes, a target edge service node for uploading the request data packet according to the load capacity and the response time.

Images