Data outgoing method, device and equipment and computer readable storage medium

By configuring multiple sending methods and constructing data acquisition tasks, the problem of existing technologies being unable to support multiple data outgoing methods has been solved, achieving flexible data sending adaptation and meeting the needs of different servers.

CN119011390APending Publication Date: 2024-11-22HANGZHOU DBAPPSECURITY CO LTD
View PDF 0 Cites 2 Cited by

Patent Information

Application Number
CN202411328340.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-09-23
Publication Date
2024-11-22

AI Technical Summary

Technical Problem

Existing technologies cannot support multiple methods of data outgoing and cannot meet the data sending needs of different servers.

Method used

A data transmission method is provided, which constructs a data acquisition task by configuring multiple transmission methods according to the receiving requirements of different servers, acquires and encapsulates the data, and then transmits it to the target server according to the matching transmission method.

Benefits of technology

It enables flexible configuration during the data collection and transmission phases, supports multiple combinations of transmission methods, covers most business scenario requirements, and users do not need to worry about the data collection and transmission process.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119011390A_ABST
    Figure CN119011390A_ABST
Patent Text Reader

Abstract

The invention relates to the technical field of data transmission, and discloses a data outgoing method, device and equipment and a computer readable storage medium, and sending configuration of multiple sending modes is carried out according to receiving requirements of different servers. And constructing a data acquisition task according to data types and data sending modes required to be acquired by different servers. And starting a data acquisition task to obtain various types of data. Packaging the target data according to a set data format, and transmitting the packaged target data to a target server according to a data sending mode matched with the target data; wherein the target data is any type of data in various types of data. The data collection stage and the data sending stage are uncoupled through configuration, flexible configuration can be achieved in the data collection stage and the data sending stage, combined configuration sending supporting multiple modes is achieved, and collection of any data and data sending of any system can be completed.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of data transmission, and in particular to a data outbound method, device, equipment and computer-readable storage medium. Background Art

[0002] With the development of information technology, business systems are becoming more and more complex, and systems often need to exchange information frequently. The current system development model is often multi-system cooperation, and there is an increasing demand for data exchange and even data hosting between different systems.

[0003] For example, the Advanced Threat Detection and Analysis System (AXDR) product sends its own alarm data to other similar products, or to other different types of products, such as Advanced Persistent Threat (APT) products, Big Data Intelligent Security Platform (AILPHA) products, etc. Conversely, data from other systems can also be sent to this system in the same way. In theory, as long as the target system has a demand for the data of this system, the data can be sent in different ways. However, the traditional data outbound method often sends data out according to a selected single data transmission method, which cannot meet the demand for sending data in different ways.

[0004] It can be seen that how to support data outbound transmission in multiple transmission modes is a problem that needs to be solved by those skilled in the art. Summary of the invention

[0005] The purpose of the embodiments of the present invention is to provide a data outbound transmission method, apparatus, device and computer-readable storage medium, which can support data outbound transmission in multiple transmission modes.

[0006] In order to solve the above technical problems, an embodiment of the present invention provides a data outbound method, which is applicable to a sending end, and the method includes:

[0007] According to the receiving requirements of different servers, multiple sending modes can be configured;

[0008] Construct data collection tasks according to the data types and data sending methods required by different servers;

[0009] Initiate the data collection task to obtain various types of data;

[0010] The target data is encapsulated according to a set data format, and the encapsulated target data is transmitted to a target server according to a data transmission method matched with the target data; wherein the target data is any one of various types of data.

[0011] On the one hand, according to the receiving requirements of different servers, multiple sending modes are configured, including:

[0012] If the server's receiving requirement is API receiving, configure the server name, server address and authentication token;

[0013] If the server needs to receive syslog, configure the server name, server IP, port, and transmission protocol;

[0014] If the server's receiving requirement is Kafka receiving, configure the server name, server list, topic, compression method, encryption method, and authentication information that matches the encryption method.

[0015] On the one hand, according to the data types and data sending methods required by different servers, the data collection tasks include:

[0016] Different data collection pages are configured according to the data types that different servers need to obtain, and the corresponding relationship between each server and the data type and the data sending method is recorded; wherein the data collection page is used to collect data that matches the data type.

[0017] On the one hand, the data collection task is started to obtain various types of data including:

[0018] According to the data collection page matched by the target server, obtain the target data corresponding to the target server;

[0019] Correspondingly, transmitting the encapsulated target data to the target server according to the data sending mode matched by the target data includes:

[0020] Querying the correspondence between each server and the data type and the data sending mode to determine the target data sending mode that matches the target server;

[0021] The encapsulated target data is transmitted to the target server according to the target data sending method.

[0022] On the one hand, according to the data types and data sending methods required by different servers, the data collection tasks include:

[0023] Build a configuration file for collecting system data and record the correspondence between each server and the data type and the data sending method.

[0024] On the one hand, the data collection task is started to obtain various types of data including:

[0025] Obtaining system data using the configuration file;

[0026] Accordingly, encapsulating the target data according to a set data format, and transmitting the encapsulated target data to the target server according to a data transmission method matched by the target data includes:

[0027] Querying the correspondence between each server and the data type and the data sending mode to determine the target data type and the target data sending mode matched by the target server;

[0028] Target data matching the target data type is screened out from the system data, the target data is packaged according to a set data format, and the packaged target data is transmitted to the target server according to the target data transmission method.

[0029] On the one hand, building a configuration file for collecting system data includes:

[0030] According to the JSON format, build a configuration file that supports MySQL query statements, interface calls, and reflection.

[0031] The embodiment of the present invention further provides a data outbound device, which is applicable to a transmitting end, and the device includes a sending configuration unit, a building unit, an acquiring unit and a transmission unit;

[0032] The sending configuration unit is used to perform sending configuration of multiple sending modes according to the receiving requirements of different servers;

[0033] The construction unit is used to construct data collection tasks according to the data types and data sending methods required by different servers;

[0034] The acquisition unit is used to start the data acquisition task to acquire various types of data;

[0035] The transmission unit is used to encapsulate the target data according to a set data format, and transmit the encapsulated target data to a target server according to a data sending method matching the target data; wherein the target data is any one of various types of data.

[0036] On the one hand, the sending configuration unit includes a first configuration subunit, a second configuration subunit and a third configuration subunit;

[0037] The first configuration subunit is used to configure the server name, server address and authentication token when the receiving requirement of the server is API receiving;

[0038] The second configuration subunit is used to configure the server name, server IP, port and transmission protocol when the receiving requirement of the server is syslog receiving;

[0039] The third configuration subunit is used to configure the server name, server list, topic, compression method, encryption method and authentication information matching the encryption method when the server's receiving requirement is Kafka reception.

[0040] On the one hand, the construction unit is used to configure different data collection pages according to the data types that different servers need to obtain, and record the correspondence between each server and the data type and the data sending method; wherein the data collection page is used to collect data that matches the data type.

[0041] On the one hand, the acquisition unit is used to acquire target data corresponding to the target server according to the data collection page matched by the target server;

[0042] Correspondingly, the transmission unit is used to query the correspondence between each server and the data type and the data sending method to determine the target data sending method matching the target server; and transmit the encapsulated target data to the target server according to the target data sending method.

[0043] On the one hand, the construction unit is used to construct a configuration file for collecting system data and record the corresponding relationship between each server and the data type and the data sending method.

[0044] On the one hand, the acquisition unit is used to acquire system data using the configuration file;

[0045] Correspondingly, the transmission unit is used to query the correspondence between each server and the data type and the data sending method to determine the target data type and the target data sending method that match the target server; filter out the target data that matches the target data type from the system data, encapsulate the target data according to the set data format, and transmit the encapsulated target data to the target server according to the target data sending method.

[0046] On the one hand, the construction unit is used to construct a configuration file that supports MySQL query statements, interface calls, and reflection in JSON format.

[0047] The embodiment of the present invention further provides a data outbound device, including:

[0048] Memory for storing computer programs;

[0049] A processor is used to execute the computer program to implement the steps of the above-mentioned data outbound method.

[0050] An embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the above-mentioned data externalization method are implemented.

[0051] It can be seen from the above technical scheme that according to the receiving requirements of different servers, multiple sending modes are configured. According to the data types and data sending modes required by different servers, data collection tasks are constructed. Data collection tasks are started to obtain various types of data. The target data is encapsulated according to the set data format, and the encapsulated target data is transmitted to the target server according to the data sending mode matched by the target data; wherein the target data is any type of data among various types of data. In this technical scheme, the data collection and data sending stages are decoupled by configuration, and any data that needs to be sent in the sending end system can be flexibly collected by constructing data collection tasks in the data collection stage. By pre-configuring the sending of multiple sending modes, the sending mode that matches the server can be flexibly selected in the data sending stage to realize data outbound delivery. In this technical scheme, it can be flexible and configurable in both the data collection and sending stages, and support for multiple modes of combined configuration sending can be realized, which can cover most business scenario requirements. And the user does not need to care about the data collection process and the sending process, and only needs to configure correctly to complete any data collection and data sending of any system. BRIEF DESCRIPTION OF THE DRAWINGS

[0052] In order to more clearly illustrate the embodiments of the present invention, the following briefly introduces the drawings required for use in the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0053] FIG1 is a flow chart of a data outbound method provided by an embodiment of the present invention;

[0054] FIG2 is a schematic diagram of a sending configuration corresponding to an API provided in an embodiment of the present invention;

[0055] 3 is a schematic diagram of a syslog corresponding sending configuration provided by an embodiment of the present invention;

[0056] FIG4 is a schematic diagram of a non-encrypted sending configuration based on Kafka provided by an embodiment of the present invention;

[0057] FIG5 is a schematic diagram of a sending configuration corresponding to SSL encryption based on Kafka provided in an embodiment of the present invention;

[0058] 6 is a schematic diagram of a sending configuration corresponding to a SASL authentication and SSL encryption based on Kafka provided in an embodiment of the present invention;

[0059] 7 is a schematic diagram of a sending configuration corresponding to a kafka-based Kerberos authentication and SSL encryption provided in an embodiment of the present invention;

[0060] FIG8 is a schematic structural diagram of a data outbound transmission device provided by an embodiment of the present invention;

[0061] FIG. 9 is a schematic diagram of the structure of a data outbound transmission device provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0062] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0063] The terms "including" and "having" in the specification of the present invention and the above-mentioned drawings, as well as any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device including a series of steps or units is not limited to the listed steps or units, but may include steps or units that are not listed.

[0064] In order to enable those skilled in the art to better understand the solution of the present invention, the present invention is further described in detail below in conjunction with the accompanying drawings and specific implementation methods.

[0065] Next, a data outbound method provided by an embodiment of the present invention is described in detail. FIG1 is a flow chart of a data outbound method provided by an embodiment of the present invention, which is applicable to a sending end, and the method comprises:

[0066] S101: Perform sending configuration of multiple sending modes according to the receiving requirements of different servers.

[0067] In actual applications, the configurations of the sender and receiver must be consistent to send data correctly. The sender can be a terminal, and the receiver can be a server. The server's receiving requirements are used to characterize the way the server receives data.

[0068] In the embodiment of the present invention, based on the current mainstream data transmission channels, a data transmission method supporting API (http, https), syslog (using UDP, TCP protocols), and kafka (supporting multiple encryptions) is designed.

[0069] There are differences in the sending configurations corresponding to different sending methods. When the server's receiving requirement is API reception, the server name, server address and authentication token can be configured. Figure 2 is a schematic diagram of a sending configuration corresponding to an API provided in an embodiment of the present invention. The basic configuration includes a server name, a server address and an authentication token. The user name can be set by the user. The API supports token authentication using http or https authentication methods.

[0070] When the server's receiving requirement is syslog receiving, the server name, server IP, port and transmission protocol can be configured. Figure 3 is a schematic diagram of a syslog sending configuration provided by an embodiment of the present invention. The basic configuration includes the server name, server IP, port and transmission protocol; wherein the transmission protocol can be UDP or TCP.

[0071] If the server's receiving requirement is Kafka receiving, you can configure the server name, server list, topic, compression method, encryption method, and authentication information that matches the encryption method.

[0072] In actual applications, regular transmission can use API or syslog, and large data volume transmission can use Kafka.

[0073] The configurations of the sender and receiver must be consistent to send data correctly. Table 1 below is a list of basic configurations of the sender and receiver under different sending modes.

[0074] Table 1

[0075]

[0076] Among them, Kafka sending can be configured whether to start the SSL channel and whether to encrypt. Encryption supports multiple methods and is adapted to almost all encryption methods to meet the encryption requirements of different servers.

[0077] Table 2 below shows six encryption methods combined by a Kafka encryption configuration provided by an embodiment of the present invention:

[0078] Table 2

[0079]

[0080] Fig. 4 is a schematic diagram of a non-encrypted sending configuration based on Kafka provided by an embodiment of the present invention, wherein the basic configuration includes server name, encryption mode, server list, topic and compression mode. The encryption mode can be selected as "None".

[0081] Fig. 5 is a schematic diagram of a sending configuration corresponding to SSL encryption based on kafka provided by an embodiment of the present invention, wherein the basic configuration includes server name, encryption mode, server list, subject, certificate status, and compression mode. Among them, the encryption mode can select "SSL".

[0082] Fig. 6 is a schematic diagram of a sending configuration corresponding to a Kafka-based SASL authentication and SSL encryption provided by an embodiment of the present invention, wherein the basic configuration includes server name, encryption mode, server list, subject, authentication user name, password, certificate status, and compression mode. Among them, the encryption mode can select "SASL authentication + SSL".

[0083] Figure 7 is a schematic diagram of a sending configuration corresponding to a Kerberos authentication and SSL encryption based on Kafka provided by an embodiment of the present invention. The basic configuration includes server name, encryption mode, server list, topic, kdc host name, service name, principal, keyTab file, certificate status, and compression mode. Among them, the encryption mode can select "Kerberos authentication + SSL".

[0084] S102: Constructing a data collection task according to the data types and data sending methods required by different servers.

[0085] There are two ways to set up data collection tasks. One is based on page configuration to collect set types of data. The other is based on configuration files to collect all system data, which is a more flexible way of data collection.

[0086] Taking page configuration as an example, different data collection pages can be configured according to the data types that different servers need to obtain, and the correspondence between each server and the data type and the data sending method can be recorded; among them, the data collection page is used to collect data that matches the data type.

[0087] Taking the configuration file as an example, a configuration file for collecting system data can be constructed, and the correspondence between each server and the data type and the data sending method can be recorded.

[0088] In actual applications, you can build a configuration file that supports MySQL query statements, interface calls, and reflection in JSON format.

[0089] MySQL query statement: You can query the MySQL database data of the sending system, which means that you can execute a MySQL query statement as the sent data.

[0090] Interface (API) call: You can call the interface of the sending system, which means that you can collect data by executing an HTTP request.

[0091] Reflection: It means that the methods in the program can be executed to collect data.

[0092] S103: Start a data collection task to obtain various types of data.

[0093] In the embodiment of the present invention, the data type that each server needs to collect and the corresponding data sending method can be regarded as a data collection task. Therefore, when constructing the data collection task, the corresponding relationship between each server and the data type and the data sending method will be recorded.

[0094] By starting the data collection task, the required data can be obtained, and then the data can be transmitted to the corresponding server according to the required data transmission method according to the corresponding relationship.

[0095] S104: Encapsulate the target data according to a set data format, and transmit the encapsulated target data to a target server according to a data transmission method matching the target data.

[0096] In the embodiment of the present invention, the data format is uniformly List <Map<String,Object> >.

[0097] Different servers need to obtain different types of data, but the methods for obtaining all types of data are similar. We will take any type of data, namely, target data, as an example to introduce. For the sake of distinction, the server corresponding to the target data can be called the target server.

[0098] Taking page configuration as an example, the target data corresponding to the target server can be obtained according to the data collection page matched by the target server. The correspondence between each server and the data type and the data sending method is queried to determine the target data sending method matched by the target server; the encapsulated target data is transmitted to the target server according to the target data sending method.

[0099] Taking the configuration file as an example, the system data can be obtained by using the configuration file. The corresponding relationship between each server and the data type and the data sending method is queried to determine the target data type and the target data sending method that match the target server; the target data that matches the target data type is filtered out from the system data, the target data is packaged according to the set data format, and the packaged target data is transmitted to the target server according to the target data sending method.

[0100] In the embodiment of the present invention, a retry mechanism can be set. When data transmission fails, the data collection task can be restarted. When the number of retries reaches the set number limit and the data cannot be successfully transmitted, the data transmission operation is terminated.

[0101] It can be seen from the above technical scheme that according to the receiving requirements of different servers, multiple sending modes are configured. According to the data types and data sending modes required by different servers, data collection tasks are constructed. Data collection tasks are started to obtain various types of data. The target data is encapsulated according to the set data format, and the encapsulated target data is transmitted to the target server according to the data sending mode matched by the target data; wherein the target data is any type of data among various types of data. In this technical scheme, the data collection and data sending stages are decoupled by configuration, and any data that needs to be sent in the sending end system can be flexibly collected by constructing data collection tasks in the data collection stage. By pre-configuring the sending of multiple sending modes, the sending mode that matches the server can be flexibly selected in the data sending stage to realize data outbound delivery. In this technical scheme, it can be flexible and configurable in both the data collection and sending stages, and support for multiple modes of combined configuration sending can be realized, which can cover most business scenario requirements. And the user does not need to care about the data collection process and the sending process, and only needs to configure correctly to complete any data collection and data sending of any system.

[0102] FIG8 is a schematic diagram of the structure of a data outbound transmission device provided by an embodiment of the present invention, which is applicable to a transmitting end, and the device includes a transmission configuration unit 81, a construction unit 82, an acquisition unit 83 and a transmission unit 84;

[0103] The sending configuration unit 81 is used to perform sending configuration of multiple sending modes according to the receiving requirements of different servers;

[0104] A construction unit 82, used to construct a data collection task according to the data types and data sending methods required by different servers;

[0105] The acquisition unit 83 is used to start the data acquisition task to acquire various types of data;

[0106] The transmission unit 84 is used to encapsulate the target data according to a set data format, and transmit the encapsulated target data to the target server according to a data transmission method matching the target data; wherein the target data is any type of data.

[0107] In some embodiments, the sending configuration unit includes a first configuration subunit, a second configuration subunit, and a third configuration subunit;

[0108] A first configuration subunit is used to configure a server name, a server address and an authentication token when the receiving requirement of the server is API receiving;

[0109] The second configuration subunit is used to configure the server name, server IP, port and transmission protocol when the receiving requirement of the server is syslog receiving;

[0110] The third configuration subunit is used to configure the server name, server list, topic, compression method, encryption method and authentication information matching the encryption method when the server's receiving requirement is Kafka reception.

[0111] In some embodiments, the construction unit is used to configure different data collection pages according to the data types that different servers need to obtain, and record the correspondence between each server and the data type and the data sending method; wherein the data collection page is used to collect data that matches the data type.

[0112] In some embodiments, the acquisition unit is used to acquire target data corresponding to the target server according to the data collection page matched by the target server;

[0113] Correspondingly, the transmission unit is used to query the correspondence between each server and the data type and the data sending mode to determine the target data sending mode that matches the target server; and transmit the encapsulated target data to the target server according to the target data sending mode.

[0114] In some embodiments, the construction unit is used to construct a configuration file for collecting system data, and record the corresponding relationship between each server and the data type and the data sending method.

[0115] In some embodiments, the acquisition unit is used to acquire system data using a configuration file;

[0116] Correspondingly, the transmission unit is used to query the correspondence between each server and the data type and the data sending method to determine the target data type and the target data sending method that match the target server; filter out the target data that matches the target data type from the system data, encapsulate the target data according to the set data format, and transmit the encapsulated target data to the target server according to the target data sending method.

[0117] In some embodiments, the construction unit is used to construct a configuration file that supports MySQL query statements, interface calls, and reflection in JSON format.

[0118] For the description of the features in the embodiment corresponding to FIG8 , reference can be made to the relevant description of the embodiment corresponding to FIG1 , and they will not be described one by one here.

[0119] It can be seen from the above technical scheme that according to the receiving requirements of different servers, multiple sending modes are configured. According to the data types and data sending modes required by different servers, data collection tasks are constructed. Data collection tasks are started to obtain various types of data. The target data is encapsulated according to the set data format, and the encapsulated target data is transmitted to the target server according to the data sending mode matched by the target data; wherein the target data is any type of data among various types of data. In this technical scheme, the data collection and data sending stages are decoupled by configuration, and any data that needs to be sent in the sending end system can be flexibly collected by constructing data collection tasks in the data collection stage. By pre-configuring the sending of multiple sending modes, the sending mode that matches the server can be flexibly selected in the data sending stage to realize data outbound delivery. In this technical scheme, it can be flexible and configurable in both the data collection and sending stages, and support for multiple modes of combined configuration sending can be realized, which can cover most business scenario requirements. And the user does not need to care about the data collection process and the sending process, and only needs to configure correctly to complete any data collection and data sending of any system.

[0120] FIG9 is a structural diagram of a data outbound device provided by an embodiment of the present invention. As shown in FIG9 , the data outbound device includes: a memory 90 for storing computer programs;

[0121] The processor 91 is used to implement the steps of the data outbound method in the above embodiment when executing a computer program.

[0122] The data outbound device provided in this embodiment may include but is not limited to a smart phone, a tablet computer, a laptop computer, or a desktop computer.

[0123] Among them, the processor 91 may include one or more processing cores, such as a 4-core processor, an 8-core processor, etc. The processor 91 can be implemented in at least one hardware form of digital signal processing (DSP), field-programmable gate array (FPGA), and programmable logic array (PLA). The processor 91 may also include a main processor and a coprocessor. The main processor is a processor for processing data in the awake state, also known as a central processing unit (CPU); the coprocessor is a low-power processor for processing data in the standby state. In some embodiments, the processor 91 may be integrated with a graphics processing unit (GPU), and the GPU is responsible for rendering and drawing the content to be displayed on the display screen. In some embodiments, the processor 91 may also include an artificial intelligence (AI) processor, which is used to process computing operations related to machine learning.

[0124] The memory 90 may include one or more computer-readable storage media, which may be non-transitory. The memory 90 may also include a high-speed random access memory, and a non-volatile memory, such as one or more disk storage devices, flash memory storage devices. In this embodiment, the memory 90 is at least used to store the following computer program 901, wherein, after the computer program is loaded and executed by the processor 91, it can implement the relevant steps of the data outbound method disclosed in any of the aforementioned embodiments. In addition, the resources stored in the memory 90 may also include an operating system 902 and data 903, etc., and the storage method may be temporary storage or permanent storage. Among them, the operating system 902 may include Windows, Unix, Linux, etc. Data 903 may include, but is not limited to, sending configurations of multiple sending methods, etc.

[0125] In some embodiments, the data external transmission device may also include a display screen 92 , an input / output interface 93 , a communication interface 94 , a power supply 95 , and a communication bus 96 .

[0126] Those skilled in the art will appreciate that the structure shown in FIG. 9 does not constitute a limitation on the data outbound transmission device, and may include more or fewer components than those shown in the figure.

[0127] It is understandable that if the data outbound method in the above embodiment is implemented in the form of 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 the present invention, or the part that contributes to the current technology, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium to execute all or part of the steps of the methods of each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), electrically erasable programmable ROM, register, hard disk, removable disk, CD-ROM, magnetic disk or optical disk, etc. Various media that can store program codes.

[0128] Based on this, an embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the above-mentioned data externalization method are implemented.

[0129] The above is a detailed introduction to a data outbound method, device, equipment and computer-readable storage medium provided by an embodiment of the present invention. The various embodiments in the specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same and similar parts between the various embodiments can be referred to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts can be referred to the method part description.

[0130] Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in the above description according to function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present invention.

[0131] The above is a detailed introduction to a data outbound method, device, equipment and computer-readable storage medium provided by the present invention. Specific examples are used herein to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only used to help understand the method of the present invention and its core idea. It should be pointed out that for ordinary technicians in this technical field, without departing from the principles of the present invention, several improvements and modifications can be made to the present invention, and these improvements and modifications also fall within the scope of protection of the present invention.

Claims

1. A data outbound method, characterized in that: Applicable to the sending end, the method includes: According to the receiving requirements of different servers, multiple sending modes can be configured; Construct data collection tasks according to the data types and data sending methods required by different servers; Initiate the data collection task to obtain various types of data; The target data is encapsulated according to a set data format, and the encapsulated target data is transmitted to a target server according to a data transmission method matched with the target data; wherein the target data is any one of various types of data.

2. The data outbound method according to claim 1, characterized in that: According to the receiving requirements of different servers, multiple sending modes are configured, including: If the server's receiving requirement is API receiving, configure the server name, server address and authentication token; If the server needs to receive syslog, configure the server name, server IP, port, and transmission protocol; If the server's receiving requirement is Kafka receiving, configure the server name, server list, topic, compression method, encryption method, and authentication information that matches the encryption method.

3. The data outbound method according to claim 1, characterized in that: According to the data types and data sending methods required by different servers, the data collection tasks include: Different data collection pages are configured according to the data types that different servers need to obtain, and the corresponding relationship between each server and the data type and the data sending method is recorded; wherein the data collection page is used to collect data that matches the data type.

4. The data outbound method according to claim 3, characterized in that: Start the data collection task to obtain various types of data including: According to the data collection page matched by the target server, obtain the target data corresponding to the target server; Correspondingly, transmitting the encapsulated target data to the target server according to the data sending mode matched by the target data includes: Querying the correspondence between each server and the data type and the data sending mode to determine the target data sending mode that matches the target server; The encapsulated target data is transmitted to the target server according to the target data sending method.

5. The data outbound method according to claim 1, characterized in that: According to the data types and data sending methods required by different servers, the data collection tasks include: Build a configuration file for collecting system data and record the correspondence between each server and the data type and the data sending method.

6. The data outbound method according to claim 5, characterized in that: Start the data collection task to obtain various types of data including: Obtaining system data using the configuration file; Accordingly, encapsulating the target data according to a set data format, and transmitting the encapsulated target data to the target server according to a data transmission method matched by the target data includes: Querying the correspondence between each server and the data type and the data sending mode to determine the target data type and the target data sending mode matched by the target server; Target data matching the target data type is screened out from the system data, the target data is packaged according to a set data format, and the packaged target data is transmitted to the target server according to the target data transmission method.

7. The data outbound method according to claim 5, characterized in that: The configuration file for collecting system data includes: According to the JSON format, build a configuration file that supports MySQL query statements, interface calls, and reflection.

8. A data outbound device, characterized in that: Applicable to a sending end, the device comprises a sending configuration unit, a building unit, an acquisition unit and a transmission unit; The sending configuration unit is used to perform sending configuration of multiple sending modes according to the receiving requirements of different servers; The construction unit is used to construct data collection tasks according to the data types and data sending methods required by different servers; The acquisition unit is used to start the data acquisition task to acquire various types of data; The transmission unit is used to encapsulate the target data according to a set data format, and transmit the encapsulated target data to a target server according to a data sending method matching the target data; wherein the target data is any one of various types of data.

9. A data outbound device, characterized in that: include: Memory for storing computer programs; A processor, configured to execute the computer program to implement the steps of the data outbound method as claimed in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the data outbound method according to any one of claims 1 to 7 are implemented.

Citation Information

Cited By

  • Data exit security management and control system and method for centralized monitoring system of transformer substation

    CN120185189A

  • Data outlet security control system and method of substation centralized monitoring system

    CN120185189B