WO2021139240A1

WO2021139240A1 - Domain name compression method and product related thereto

Info

Publication number: WO2021139240A1
Application number: PCT/CN2020/118337
Authority: WO
Inventors: 杨绮昊
Original assignee: 平安科技（深圳）有限公司
Priority date: 2020-07-28
Filing date: 2020-09-28
Publication date: 2021-07-15
Also published as: CN111917899B; CN111917899A

Abstract

The present application relates to the field of data processing. Disclosed are a domain name compression method and a related product. The domain name compression method comprises: acquiring first data, wherein the first data is data of a domain name system (DNS) protocol resolution record; classifying the first data to obtain five types of data; locally compressing the five types of data, respectively, to obtain second data; and carrying out associated compression on the second data to obtain target data. The processing speed of a large number of domain names by a domain name server is improved, and the utilization rate of system resources is improved.

Description

A domain name compression method and related products

This application claims the priority of a Chinese patent application filed with the Chinese Patent Office on July 28, 2020, the application number is 202010742846.8, and the application name is "a domain name compression method and related products", the entire content of which is incorporated herein by reference Applying.

Technical field

This application relates to the field of computer technology, in particular to a domain name compression method and related products.

Background technique

With the continuous development and progress of science and technology, big data and intelligent management have been implanted in all walks of life, and people's lives have been greatly facilitated. The domain name compression greatly reduces the time people spend browsing the web.

At present, in the field of domain name compression, the inventor found that in the high-traffic scenario, the domain name server needs to resolve a large number of domain names. At this time, the DNS server will face greater processing pressure, and the response time of the domain name server will become longer. . Therefore, how to further reduce the processing time of the domain name server and increase the processing rate of the domain name server has become a problem to be solved.

technical problem

In high-access scenarios, the DNS server has the problem of slow processing a large number of domain names.

Technical solutions

Based on the problem that the domain name server processes a large number of domain names at a slow rate in a high-access scenario, the embodiments of the present application provide a presentation generation method, device, electronic equipment, and computer-readable storage medium.

In a first aspect, an embodiment of the present application provides a domain name compression method. The method includes: acquiring first data, where the first data is data recorded by a DNS resolution of a domain name system protocol; and classifying the first data, Obtain five types of data; respectively perform partial compression on the five types of data to obtain second data; perform associated compression on the second data to obtain target data.

In a second aspect, an embodiment of the present application provides a domain name compression device, the domain name compression device includes: an acquiring unit configured to acquire first data, where the first data is data of a DNS resolution record of the Domain Name System Protocol; and a classification unit , Used to classify the first data to obtain five types of data; a local compression unit, used to locally compress the five types of data respectively, to obtain the second data; an associated compression unit, used to obtain the second data Second, the data is associated and compressed to obtain the target data.

In a third aspect, an embodiment of the present application provides an electronic device, including a processor, a memory, a communication interface, and one or more programs, wherein the one or more programs are stored in the memory and are configured by the above The processor executes the following steps: acquiring first data, the first data being the data recorded by the DNS resolution of the domain name system protocol; classifying the first data to obtain five types of data; respectively Perform partial compression to obtain the second data; perform associated compression on the second data to obtain the target data.

In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, wherein the above-mentioned computer-readable storage medium stores a computer program for electronic data exchange, wherein the above-mentioned computer program causes the computer to perform the following steps: Data, the first data is the data recorded by the DNS resolution of the domain name system protocol; the first data is classified to obtain five types of data; the five types of data are respectively compressed locally to obtain the second data; Perform associative compression on the second data to obtain the target data.

In a fifth aspect, the embodiments of the present application provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program, and the computer program is operable to cause a computer to execute as implemented in this application. For example, part or all of the steps described in any method of the first aspect. The computer program product may be a software installation package.

Beneficial effect

The domain name server of the embodiment of the application obtains first data, which is the data recorded by the DNS resolution of the domain name system protocol; classifies the first data to obtain five types of data; respectively, the five types of data Perform partial compression to obtain second data; perform associated compression on the second data to obtain target data, which improves the rate at which the domain name server processes a large number of domain names and improves the utilization of system resources.

Description of the drawings

FIG. 1 is a schematic diagram of a domain name processing flow provided by an embodiment of the application.

FIG. 2A is a schematic flowchart of a domain name compression method provided by an embodiment of the application.

FIG. 2B is a schematic diagram of analysis records of five types of data provided by an embodiment of the application.

FIG. 3 is a schematic flowchart of a domain name compression method provided by an embodiment of the application.

Fig. 4 is a schematic structural diagram of an electronic device provided by an embodiment of the present application.

Fig. 5 is a block diagram of functional units of a domain name compression device provided by an embodiment of the present application.

Embodiments of the present invention

DNS is a domain name system. It is a distributed database on the World Wide Web as a mapping between domain names and IP addresses. It can make it easier for users to access the Internet without having to remember IP numbers that can be directly read by machines. The purpose of DNS is to resolve domain names into IP addresses. In high-traffic scenarios, it is necessary to resolve a large number of domain names. At this time, the DNS server will face processing pressure, and users can obviously feel that the server's response time becomes longer. Among the parameters for evaluating DNS service performance, the percentage of server processing time is an important evaluation index. Therefore, the domain name compression technology that can increase the percentage of server processing time is very valuable in the DNS field, which can help websites improve user experience and create high-quality website services.

Existing domain name compression methods are subject to business rules. The compression process must depend on the absolute position of the data packet where the domain name is located, and only supports real-time compression of the domain name during the request and response process. When large-scale user access occurs This compression method cannot predict the required resolution resources, cannot allow the DNS server to process a large number of domain names in a short period of time, and cannot reduce the real-time consumption of responses. It not only fails to effectively utilize system resources, but also fails to meet expectations.

The following describes the embodiments of the application in detail.

Please refer to FIG. 1. FIG. 1 is a schematic diagram of a domain name processing flow provided by an embodiment of the present application.

In order to solve the problem that the domain name server processes a large number of domain names at a slow rate in a high-access scenario, this application provides a domain name compression method, specifically as shown in FIG. 2A, the method may include but is not limited to the following steps S201-S204.

S201. The domain name server obtains the first data.

Among them, the first data is the data recorded by the DNS resolution of the domain name system protocol. Among them, the data of each DNS resolution record includes: the main domain name of the DNS resolution record, host record, record type, record value, and the time-to-live (TTL) of the domain name resolution record in the DNS server. The record types include any of the following: address (Address, A) records, AAAA records, alias records CNAME records, mail exchange (mail exchanger, MX) records, and domain name server (Name Server, NS) records.

S202. The domain name server classifies the first data to obtain five types of data.

Among them, the five types of data include: the first type of data, the second type of data, the third type of data, the fourth type of data, and the fifth type of data. Among them, the first type of data is the resolution records of the same primary domain name, the same host record, and the same record type, which are recorded as type I; the second type of data is the resolution records of the same primary domain name, the same host record, and the resolution of different record types. Records are recorded as type II; the third type of data is the resolution records of the same main domain name, different host records, and the same record type, recorded as type III; the fourth type of data is the same main domain name, different host records, and different record types The analysis records are recorded as category IV; the fifth type of data is the analysis records of different main domain names and the same host record, and is recorded as category V. As shown in FIG. 2B, FIG. 2B is a schematic diagram of analyzing and recording five types of data.

In specific implementation, the domain name server classifies the first data to obtain five types of data, including but not limited to: the domain name server records the analysis record in the first data according to the main domain name, host record, and record type in the analysis record , Divided into resolution records of the same primary domain name, same host record, and same record type; resolution records of the same primary domain name, same host record, and resolution records of different record types; resolution record of the same primary domain name, different host records, and same record type ; Resolution records of the same primary domain name, different host records, and different record types; resolution records of different primary domain names and the same host record.

S203. The domain name server performs partial compression on the five types of data respectively to obtain second data.

In specific implementation, the domain name server performs partial compression on the five types of data to obtain the second data, including but not limited to: the domain name server performs partial compression on the five types of data according to the first byte offset table to obtain the second data .

In specific implementation, before the domain name server locally compresses the five types of data to obtain the second data, the method further includes: the domain name server establishes a first byte offset table corresponding to the five types of data, and the first byte offset table is established by the domain name server. The one-byte offset table is used to locally compress the five types of data; the domain name server detects each of the five types of data to be detected and the first byte of each parsing record to be detected Whether the detected analysis record in the offset table is redundant; if so, the domain name server saves the offset size of the analysis record to be detected in each of the five types of data in the first word Section offset table; if not, the domain name server adds the aforementioned parsing record to be detected in the first byte offset table.

Where further explanation is needed, the domain name server establishes the first byte offset table corresponding to the five types of data, including but not limited to: performing the same internal analysis on each type of the five types of data. After partial compression, the domain name server determines the first position of the parsing record of each of the five types of data, where the first position is the reference position in each type of data of the five types of data; the domain name server is based on The first position sets the first offset size corresponding to each of the five types of data; the domain name server determines the first byte offset based on the first offset size and the first position Move the table.

S204: The domain name server performs associated compression on the second data to obtain target data.

In specific implementation, the domain name server associates and compresses the second data to obtain the target data, including but not limited to: the domain name server divides the second data into three types of regional data; the domain name server analyzes records in the three types of regional data Perform associative compression.

Wherein, the three types of area data include: first area data, second area data, and third area data, and the first area data, the second area data, and the third area data are different from each other.

It needs to be further explained that the domain name server associates and compresses the analysis records in the three types of area data, including but not limited to: the domain name server compares the first area data with the second area data according to the second byte offset table. The area data are respectively jointly compressed to obtain the third data; the domain name server jointly compresses the third data and the third area data according to the second byte offset table.

Among them, the second byte offset table can be determined through the following specific steps: establish the second byte offset table; determine the reference position, current position, and offset position of each analytical record of the three types of area data; The base position, current position, and offset position of a parsing record are saved in the position byte offset table.

It can be seen that the domain name server in the embodiment of the application obtains the first data, and the first data is the data recorded by the DNS resolution of the domain name system protocol; the first data is classified to obtain five types of data; Each type of data is locally compressed to obtain the second data; the second data is associated and compressed to obtain the target data, which improves the rate at which the domain name server processes a large number of domain names and improves the utilization rate of system resources.

In a possible example, the classification of the first data to obtain five types of data includes: recording the DNS resolution of the first data according to the data characteristics of the DNS resolution record in the first data Divide into five types and get five types of data.

Among them, the five types of data include: the first type of data, the second type of data, the third type of data, the fourth type of data, and the fifth type of data. Among them, the first type of data is the resolution records of the same primary domain name, the same host record, and the same record type; the second type of data is the resolution records of the same primary domain name, the same host record, and the resolution records of different record types; the third type of data is resolution records of the same primary domain name, the same host record, and different record types. The data is the resolution records of the same primary domain name, different host records, and the same record type; the fourth type of data is resolution records of the same primary domain name, different host records, and different record types; the fifth type of data is different primary domain names, the same host record Analytical records.

Among them, in the five types of data, the main domain name, host record, record type, record value, and duration of the domain name resolution record in the DNS server of the DNS resolution record. The data characteristics of the DNS resolution record include: the main domain name, host record, and record type of the DNS resolution record.

In specific implementation, the domain name server divides the DNS resolution records of the first data into five types according to the data characteristics of the DNS resolution records in the first data to obtain five types of data, including but not limited to: the domain name server according to the first data The primary domain name, host record, and record type of the DNS resolution record in the first data divide the DNS resolution record of the first data into five types to obtain five types of data.

For example, the domain name server divides the resolution records of the same primary domain name, the same host record, and the same record type in the first data into the first type data among the five types of data; the domain name server divides the same primary domain name and the same host in the first data Records and resolution records of different record types are divided into the second type of data among the five types of data; the domain name server divides the resolution records of the same primary domain name, different host records, and the same record type in the first data into five types of data The third type of data; the domain name server divides the resolution records of the same primary domain name, different host records, and different record types in the first data into the fourth type of data among the five types of data; the domain name server divides the different primary data in the first data The analysis records of the domain name and the same host record are divided into the fifth type of data among the five types of data.

It can be seen that the domain name server in this embodiment divides the DNS resolution records of the first data into five types according to the data characteristics of the DNS resolution records in the first data to obtain five types of data. The data are respectively compressed locally to obtain the second data; the second data is associated and compressed to obtain the target data, which improves the rate at which the domain name server processes a large number of domain names and improves the utilization rate of system resources.

In a possible example, the performing partial compression on the five types of data to obtain the second data includes: performing partial compression on the five types of data respectively according to the first byte offset table, Obtain the second data.

In specific implementation, the five types of data are respectively locally compressed according to the first byte offset table to obtain the second data, including but not limited to: according to each of the first byte offset tables The offset size in the analytic record performs partial compression on the five types of data respectively to obtain the second data.

It can be seen that the domain name server in this embodiment divides the DNS resolution records of the first data into five types according to the data characteristics of the DNS resolution records in the first data to obtain five types of data: The one-byte offset table performs partial compression on the five types of data respectively to obtain the second data; performs associative compression on the second data to obtain the target data, which improves the processing speed of the domain name server for a large number of domain names and improves the system resources Utilization rate.

In a possible example, before the partial compression is performed on the five types of data to obtain the second data, the method further includes: establishing a first byte offset table corresponding to the five types of data , The first byte offset table is used to locally compress the five types of data; each of the five types of data to be detected is detected with each of the analysis records to be detected and the first Whether the detected analysis records in the byte offset table are redundant; if so, the offset size of each analysis record to be detected in each of the five types of data is recorded in the first In the one-byte offset table; if not, add each of the analytical records to be detected in the first byte offset table.

Among them, it needs to be further explained that the establishment of the first byte offset table corresponding to the five types of data includes but is not limited to: triggering the first word when the attribute value of the analysis record in the five types of data changes The section offset table update operation updates the attribute value data of the first byte offset table and the resolution record, where the attribute value of the resolution record includes: the main domain name, host record, and record type of the DNS resolution record.

Among them, it should be further explained that if it is detected that each of the five types of data to be detected is different from the detected analysis record in the first byte offset table. Redundancy, after each of the analysis records to be detected is added to the first byte offset table, it further includes: offsetting the analysis records to be detected in each of the five types of data The size is recorded in the first byte offset table.

Take the analysis record of the third type of data as an example. First, establish a byte offset table for the analysis record of the third type of data; then, check whether the main domain name, host record, and record type of each analysis record are the same as those that have been checked. The resolution record is redundant; if it is redundant, the relative offset size of the main domain name and host record must be recorded in the byte offset table; if it is not redundant, the original index value must be recorded in the byte offset table.

It can be seen that the domain name server in this embodiment establishes a first byte offset table corresponding to the five types of data, and the first byte offset table is used to locally compress the five types of data; Whether each analytical record to be detected in each of the five types of data is redundant with the analytical record that has been detected in the first byte offset table; if so, the five types of data The offset size of each analysis record to be detected in each type of data in the type data is recorded in the first byte offset table; if not, it is added to the first byte offset table Each of the analysis records to be detected is convenient to increase the rate at which the domain name server processes a large number of domain names, and improves the utilization rate of system resources.

In a possible example, the establishment of the first byte offset table corresponding to the five types of data includes: performing local compression of the same type of analysis records for each type of the five types of data. Afterwards, determine the first position of the analysis record of each type of the five types of data, where the first position is the reference position in each type of data of the five types of data; set according to the first position A first offset size corresponding to each of the five types of data; the first offset size and the first position are used to determine the first byte offset table.

The first position is the reference position in each of the five types of data, that is, the first position is 0.

In a specific implementation, the domain name server establishes the first byte offset table corresponding to the five types of data, including: after the analysis records of each type of the five types of data are locally compressed within the same type, the domain name The server determines the first position of the parsing record of each of the five types of data, where the first position is the reference position in each type of data of the five types of data; the domain name server calculates five types of data according to the first position. A first offset size corresponding to each type of data of each type of data; the domain name server determines the first byte offset table based on the first offset size and the first position. As shown in Table 1, Table 1 is the first byte offset table corresponding to the analysis records of the five types of data.

Table 1.

It can be seen that, in this embodiment, the domain name server determines the first analysis record of each of the five types of data after locally compressing the analysis records of each type of the five types of data. A position, where the first position is a reference position in each type of data of the five types of data; the first offset size corresponding to each type of data of the five types of data is set according to the first position ; The first offset size and the first location, determine the first byte offset table, it is convenient to improve the domain name server processing a large number of domain names, and improve the utilization of system resources.

In a possible example, the performing associative compression on the second data to obtain the target data includes: dividing the second data into three types of regional data; performing associative compression on the analysis records in the three types of regional data .

In specific implementation, the second data is divided into three types of regional data; the analysis records in the three types of regional data are associated and compressed, including but not limited to: dividing the second data into three types of regional data according to five types of data, Perform associative compression on the analysis records in the three types of regional data.

It can be seen that in this embodiment, the domain name server divides the second data into three types of regional data; the analysis records in the three types of regional data are associated and compressed, which is convenient to increase the speed of the domain name server to process a large number of domain names. Utilization of system resources.

In a possible example, the three types of area data include: first area data, second area data, and third area data, and the first area data, the second area data, and the third area data Are different from each other; said performing associative compression on the analysis records in the three types of area data includes: jointly compressing the first area data and the second area data respectively according to a second byte offset table, Obtain third data; and jointly compress the third data and the third area data according to the second byte offset table.

In specific implementation, the second data is divided into three types of regional data; the analysis records in the three types of regional data are associated and compressed, including but not limited to: according to the primary domain name and host of the analysis records in the second data Record, complete the establishment of the dynamic data dictionary, and store the newly added analysis record information; divide the second data corresponding to the first type of data and the second data corresponding to the second type of data into one area, which is recorded as three types of area data The first area data in the data is the I field; the second data corresponding to the third type data and the second data corresponding to the fourth type data are divided into one area, which is recorded as the second area data in the three types of area data, namely Domain II; divide the second data corresponding to the fifth type of data into one area, and record it as the third area data of the three types of area data, that is, type V; by searching the analysis records in the dynamic data dictionary, respectively The Ⅱ domains respectively carry out cross-type region association compression; then the Ⅰ domain, Ⅱ domain and the third region data are associated, which is marked as Ⅲ Domain, cross-type region correlation compression is performed on the III domain.

What needs further explanation is that the cross-type zone association compression is performed on domain I and domain II respectively, including: referring to the second byte offset table, first parse the main domain name and host record of the record for domain I and domain II respectively. Perform compression offset size correction operation.

What needs to be further explained is that the cross-type zone association compression of the III domain includes: the main domain name and host record of the resolution record of the III domain, and the compression offset correction operation.

Wherein, before dividing the second data into three types of area data; before performing associative compression on the analysis records in the three types of area data, a byte offset table needs to be established for each area, and the offset of the associated compression The shift size is recorded in the shift table. The step of determining the offset size of the associated compression is as follows: the offset size of the associated compression needs to be dynamically calculated according to the current position of the analysis record, where the current position may be the position of the first domain name resolution record in each zone. As shown in Table 2, Table 2 is the second byte offset table.

Table 2.

It can be seen that the domain name server in this embodiment jointly compresses the first area data and the second area data according to the second byte offset table to obtain the third data; according to the second byte offset table The table shifting joint compresses the third data and the third area data, which is convenient to increase the rate at which the domain name server processes a large number of domain names, and improves the utilization of system resources.

The following describes the embodiments of the present application in detail through a specific example.

Consistent with the embodiment shown in FIG. 2A, please refer to FIG. 3. FIG. 3 is a schematic flowchart of a platform-based danger prevention method provided by an embodiment of the present application, and the method includes S301-S305.

S301. The domain name server obtains first data, where the first data is data recorded by the DNS resolution of the domain name system protocol.

S302. The domain name server divides the DNS resolution records of the first data into five types according to the data characteristics of the DNS resolution records in the first data to obtain five types of data.

S303. The domain name server performs partial compression on the five types of data respectively according to the first byte offset table to obtain second data.

S304. The domain name server divides the second data into three types of regional data.

S305. The domain name server associates and compresses the analysis records in the three types of area data.

It can be seen that the domain name server in the embodiment of the application obtains the first data, and the first data is the data of the DNS resolution record of the domain name system protocol; according to the data characteristics of the DNS resolution record in the first data, the first data is Five types of DNS resolution records are divided into five types to obtain five types of data; the five types of data are respectively compressed locally according to the first byte offset table to obtain the second data; according to the second data Divided into three types of regional data; performing correlation compression on the analysis records in the three types of regional data. Increasing the rate at which the domain name server processes a large number of domain names and improving the utilization of system resources

Please refer to FIG. 4, which is a schematic structural diagram of an electronic device 400 provided by an embodiment of the present application. As shown in the figure, the electronic device 400 includes an application processor 410, a memory 420, a communication interface 430, and one or more A program 421, wherein the one or more programs 421 are stored in the foregoing memory 420 and configured to be executed by the foregoing application processor 410, and the one or more programs 421 include steps for performing the following steps: Data, the first data is the data recorded by the DNS resolution of the domain name system protocol; the first data is classified to obtain five types of data; the five types of data are respectively compressed locally to obtain the second data; Perform associative compression on the second data to obtain the target data.

In a possible example, in terms of classifying the first data to obtain five types of data, the one or more programs 421 include the steps specifically for performing the following steps: According to the data characteristics of the DNS resolution record of the first data, the DNS resolution record of the first data is divided into five types, and five types of data are obtained.

In a possible example, in terms of performing partial compression on the five types of data to obtain the second data, the one or more programs 421 include specifically configured to perform the following steps: The section offset table performs partial compression on the five types of data respectively to obtain the second data.

In a possible example, before the partial compression is performed on the five types of data to obtain the second data, the one or more programs 421 further include the steps specifically configured to perform the following steps: The first byte offset table corresponding to the type data, where the first byte offset table is used to locally compress the five types of data; and detect every type of data in the five types of data. Whether the parsing records to be detected and the parsing records that have been detected in the first byte offset table are redundant; if so, each of the five types of data to be detected is The offset size of the analysis record is recorded in the first byte offset table; if not, the each analysis record to be detected is added to the first byte offset table.

In a possible example, in the aspect of establishing the first byte offset table corresponding to the five types of data, the one or more programs 421 include specifically configured to perform the following steps: After the analysis records of each type of data of each type are locally compressed within the same type, the first position of the analysis record of each type of the five types of data is determined, and the first position is the position of the five types of data. The reference position in each type of data; the first offset size corresponding to each of the five types of data is set according to the first position; the first offset size and the first position are set, Determine the first byte offset table.

In a possible example, in terms of performing associative compression on the second data to obtain target data, the one or more programs 421 include specifically configured to perform the following steps: dividing the second data into three types of regional data ; Perform associative compression on the analysis records in the three types of regional data.

In a possible example, the three types of area data include: first area data, second area data, and third area data, and the first area data, the second area data, and the third area data Are different from each other; in the aspect of associating and compressing the parsed records in the three types of area data, the one or more programs 421 include specifically configured to perform the following steps: according to the second byte offset table The first area data and the second area data are respectively jointly compressed to obtain third data; the third data and the third area data are jointly compressed according to the second byte offset table.

The foregoing mainly introduces the solution of the embodiment of the present application from the perspective of the execution process on the method side. It can be understood that, in order to implement the above-mentioned functions, an electronic device includes hardware structures and/or software modules corresponding to each function. Those skilled in the art should easily realize that in combination with the units and algorithm steps of the examples described in the embodiments provided herein, this application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software-driven hardware depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.

The embodiment of the present application may divide the electronic device into functional units according to the foregoing method examples. For example, each functional unit may be divided corresponding to each function, or two or more functions may be integrated into one processing unit. The above-mentioned integrated unit can be implemented in the form of hardware or software functional unit. It should be noted that the division of units in the embodiments of the present application is illustrative, and is only a logical function division, and there may be other division methods in actual implementation.

FIG. 5 is a block diagram of the functional unit composition of the domain name compression device 500 involved in an embodiment of the present application. The domain name compression device 500 includes: an acquisition unit 501, a classification unit 502, a local compression unit 503, and an association compression unit 504.

The obtaining unit 501 is configured to obtain first data, where the first data is data of a DNS resolution record of a domain name system protocol.

The classification unit 502 is configured to classify the first data to obtain five types of data.

The local compression unit 503 is configured to perform local compression on the five types of data respectively to obtain second data.

The associative compression unit 504 is configured to perform associative compression on the second data to obtain target data.

Wherein, the domain name compression apparatus 500 may further include a storage unit 505 for storing program codes and data of the electronic device. The acquiring unit 501 may be a transceiver, and the storage unit 505 may be a memory.

In a possible example, in terms of classifying the first data to obtain five types of data, the classification unit 502 is specifically configured to: according to the data characteristics of the DNS resolution record in the first data, The DNS resolution records of the first data are divided into five types, and five types of data are obtained.

In a possible example, in terms of performing local compression on the five types of data to obtain the second data, the local compression unit 503 is specifically configured to: compare the five types of data according to the first byte offset table. Each type of data is locally compressed to obtain the second data.

In a possible example, before the partial compression is performed on the five types of data to obtain the second data, the partial compression unit 503 is further specifically configured to: establish the first byte corresponding to the five types of data. Offset table, the first byte offset table is used to locally compress the five types of data; detect each of the five types of data to be detected and the analysis record and all Whether the detected analytical records in the first byte offset table are redundant; if so, the offset size of each analytical record to be detected in each of the five types of data is recorded in In the first byte offset table; if not, add each parsing record to be detected in the first byte offset table.

In a possible example, in the aspect of establishing the first byte offset table corresponding to the five types of data, the local compression unit 503 is specifically configured to: in the analysis of each type of the five types of data After the records are locally compressed within the same type, the first position of the analysis record of each type of the five types of data is determined, and the first position is the reference position in each type of the five types of data Set the first offset size corresponding to each of the five types of data according to the first position; determine the first byte offset by combining the first offset size and the first position Move the table.

In a possible example, in terms of performing associative compression on the second data to obtain target data, the associative compression unit 504 is specifically configured to: divide the second data into three types of regional data; Analyze records in the associated compression.

In a possible example, the three types of area data include: first area data, second area data, and third area data, and the first area data, the second area data, and the third area data Are different from each other; in terms of associating and compressing the analysis records in the three types of area data, the associating compression unit 504 is specifically configured to: compare the first area data with the first area data according to a second byte offset table The two area data are respectively jointly compressed to obtain the third data; the third data and the third area data are jointly compressed according to the second byte offset table.

An embodiment of the present application also provides a computer storage medium, wherein the computer storage medium stores a computer program for electronic data exchange, and the computer program enables a computer to execute part or all of the steps of any method as recorded in the above method embodiment , The above-mentioned computer includes electronic equipment. The computer-readable storage medium may be non-volatile or volatile.

The embodiments of the present application also provide a computer program product. The above-mentioned computer program product includes a non-transitory computer-readable storage medium storing a computer program. The above-mentioned computer program is operable to cause a computer to execute any of the methods described in the above-mentioned method embodiments. Part or all of the steps of the method. The computer program product may be a software installation package, and the above-mentioned computer includes electronic equipment.

In the above-mentioned embodiments, the description of each embodiment has its own emphasis. For parts that are not described in detail in an embodiment, reference may be made to related descriptions of other embodiments.

The units described above as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.

In addition, the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or software functional unit.

If the above integrated unit 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 memory. Based on this understanding, the technical solution of the present application essentially or the part that contributes to the existing 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 memory. A number of instructions are included to enable a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the foregoing methods of the various embodiments of the present application. The aforementioned memory includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard drives, magnetic disks, or CD-ROMs and other media that can store program codes.

Those of ordinary skill in the art can understand that all or part of the steps in the various methods of the above-mentioned embodiments can be completed by a program instructing relevant hardware. The program can be stored in a computer-readable memory, and the memory can include: a flash disk , Read-Only Memory (English: Read-Only Memory, abbreviated as: ROM), Random Access Memory (English: Random Access Memory, abbreviated as: RAM), magnetic disk or CD, etc.

The above are only specific implementations of this application, but the protection scope of this application is not limited to this. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed in this application. Should be covered within the scope of protection of this application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims

A domain name compression method, wherein the method includes:

Acquiring first data, where the first data is data recorded by a DNS resolution of a domain name system protocol;

Classify the first data to obtain five types of data;

Perform partial compression on the five types of data respectively to obtain second data;

The second data is associated and compressed to obtain the target data.
The method according to claim 1, wherein said classifying said first data to obtain five types of data comprises:

According to the data characteristics of the DNS resolution records in the first data, the DNS resolution records of the first data are divided into five types to obtain five types of data.
The method according to claim 1, wherein said performing partial compression on said five types of data to obtain second data respectively comprises:

The five types of data are respectively locally compressed according to the first byte offset table to obtain the second data.
The method according to claim 1 or 3, wherein, before the partial compression is performed on the five types of data to obtain the second data, the method further comprises:

Establishing a first byte offset table corresponding to the five types of data, where the first byte offset table is used to locally compress the five types of data;

Detecting whether each analytical record to be detected in each of the five types of data and the analytical record that has been detected in the first byte offset table are redundant;

If yes, record the offset size of each parsing record to be detected in each of the five types of data in the first byte offset table;

If not, add each of the analytical records to be detected in the first byte offset table.
The method according to claim 4, wherein said establishing a first byte offset table corresponding to said five types of data comprises:

After the analysis records of each type of the five types of data are locally compressed within the same type, the first position of the analysis record of each type of the five types of data is determined, and the first position is all Describe the reference position in each of the five types of data;

Setting a first offset size corresponding to each of the five types of data according to the first position;

Determine the first byte offset table by using the first offset size and the first position.
The method according to claim 1, wherein said performing associative compression on the second data to obtain the target data comprises:

Divide the second data into three types of regional data;

Perform associative compression on the analysis records in the three types of regional data.
The method according to claim 6, wherein the three types of area data include: first area data, second area data, and third area data, the first area data, the second area data, and the The third area data is different from each other;

The associative compression of the analysis records in the three types of regional data includes:

Performing joint compression on the first area data and the second area data respectively according to the second byte offset table to obtain third data;

The third data and the third area data are jointly compressed according to the second byte offset table.
A domain name compression device, wherein the domain name compression device includes:

An obtaining unit, configured to obtain first data, where the first data is data recorded by a DNS resolution of a domain name system protocol;

The classification unit is used to classify the first data to obtain five types of data;

The local compression unit is used to locally compress the five types of data to obtain second data;

The correlation compression unit is used to correlate and compress the second data to obtain the target data.
An electronic device, including a processor, a memory, a communication interface, and one or more programs, the one or more programs are stored in the memory, and the processor is configured to perform the following steps:

Acquiring first data, where the first data is data recorded by a DNS resolution of a domain name system protocol;

Classify the first data to obtain five types of data;

Perform partial compression on the five types of data respectively to obtain second data;

The second data is associated and compressed to obtain the target data.
The electronic device according to claim 9, wherein the processor is configured to:

According to the data characteristics of the DNS resolution records in the first data, the DNS resolution records of the first data are divided into five types to obtain five types of data.
The electronic device according to claim 9, wherein the processor is configured to:

The five types of data are respectively locally compressed according to the first byte offset table to obtain the second data.
The electronic device according to claim 9 or 11, wherein the processor is further configured to:

Establishing a first byte offset table corresponding to the five types of data, where the first byte offset table is used to locally compress the five types of data;

Detecting whether each analytical record to be detected in each of the five types of data and the analytical record that has been detected in the first byte offset table are redundant;

If yes, record the offset size of each parsing record to be detected in each of the five types of data in the first byte offset table;

If not, add each of the analytical records to be detected in the first byte offset table.
The electronic device according to claim 12, wherein the processor is configured to:

After the analysis records of each type of the five types of data are locally compressed within the same type, the first position of the analysis record of each type of the five types of data is determined, and the first position is all Describe the reference position in each of the five types of data;

Setting a first offset size corresponding to each of the five types of data according to the first position;

Determine the first byte offset table by using the first offset size and the first position.
The electronic device according to claim 9, wherein the processor is configured to:

Divide the second data into three types of regional data;

The analysis records in the three types of regional data are associated and compressed.
The electronic device according to claim 14, wherein the three types of area data include: first area data, second area data, and third area data, and the first area data, the second area data, and the The data in the third region are different from each other;

The processor is used for:

Performing joint compression on the first area data and the second area data respectively according to the second byte offset table to obtain third data;

The third data and the third area data are jointly compressed according to the second byte offset table.
A computer-readable storage medium, wherein it stores a computer program for electronic data exchange, wherein the computer program causes a computer to perform the following steps:

Acquiring first data, where the first data is data recorded by a DNS resolution of a domain name system protocol;

Classify the first data to obtain five types of data;

Perform partial compression on the five types of data respectively to obtain second data;

The second data is associated and compressed to obtain the target data.
The computer-readable storage medium according to claim 16, wherein the computer program causes the computer to further perform the following steps:

According to the data characteristics of the DNS resolution records in the first data, the DNS resolution records of the first data are divided into five types to obtain five types of data.
The computer-readable storage medium according to claim 16, wherein the computer program causes the computer to further perform the following steps:

The five types of data are respectively locally compressed according to the first byte offset table to obtain the second data.
The computer-readable storage medium according to claim 16 or 18, wherein the computer program causes the computer to further perform the following steps:

Establishing a first byte offset table corresponding to the five types of data, where the first byte offset table is used to locally compress the five types of data;

Detecting whether each analytical record to be detected in each of the five types of data and the analytical record that has been detected in the first byte offset table are redundant;

If yes, record the offset size of each parsing record to be detected in each of the five types of data in the first byte offset table;

If not, add each of the analytical records to be detected in the first byte offset table.
The computer-readable storage medium according to claim 19, wherein the computer program causes the computer to further perform the following steps:

After the analysis records of each type of the five types of data are locally compressed within the same type, the first position of the analysis record of each type of the five types of data is determined, and the first position is all Describe the reference position in each of the five types of data;

Setting a first offset size corresponding to each of the five types of data according to the first position;

Determine the first byte offset table by using the first offset size and the first position.