Data compression processing method and device, electronic equipment, storage medium and chip

Abstract

The invention discloses a data compression processing method and device, electronic equipment, a storage medium and a chip, and relates to the technical field of communication, and the method comprises the steps: firstly obtaining a plurality of pieces of first IP data in to-be-compressed IP data; determining prior information corresponding to the plurality of pieces of first IP data according to the plurality of pieces of first IP data; and performing parallel compression on the plurality of pieces of first IP data through a plurality of uplink data compression UDC engines based on the prior information. Compared with the prior art, the method has the advantages that the to-be-compressed IP data is divided into the multiple pieces of first IP data, the prior information of the first IP data is confirmed, parallel compression of the IP data is achieved, compression is conducted through the multiple UDC engines at the same time, the compression speed can be increased, the compression time can be shortened, and the UDC file compression processing efficiency of a multi-core processor is improved in a multiplied mode; and the use efficiency of the uplink bandwidth can also be improved.

Description

Technical Field

[0001] This application relates to the field of data processing technologies, and in particular, to a data compression method, apparatus, electronic device, storage medium, and chip. Background Art

[0002] When a user makes a voice call using a terminal, there may be a situation where the signal is weak, resulting in a low voice call connection rate. To improve the voice call connection rate, in the 3rd Generation Partnership Project (3GPP) protocol, it is necessary to perform data compression processing on the IP data of the Internet Protocol (IP) Multimedia Subsystem (IMS) for interconnection between networks.

[0003] Currently, in a multi-core processor, mainly one Uplink Data Compression (UDC) engine sequentially performs serial compression processing on IP data in the order of the IP data to be compressed.

[0004] However, in the case where the data volume of the IP data to be compressed is large, using this serial compression processing method will result in a slow compression speed and a long compression time, thereby reducing the compression efficiency of the multi-core processor. Summary of the Invention

[0005] In view of this, this application provides a data compression processing method, apparatus, electronic device, storage medium, and chip, mainly aiming to improve the technical problem that the current use of the serial compression processing method will result in a slow compression speed, a long compression time, and thus a reduction in the compression efficiency of the multi-core processor.

[0006] In a first aspect, this application provides a data compression processing method, including:

[0007] Obtain multiple first IP data in the IP data to be compressed;

[0008] Determine the prior information corresponding to the multiple first IP data according to the multiple first IP data;

[0009] Based on the prior information, perform parallel compression on the multiple first IP data through multiple Uplink Data Compression (UDC) engines.

[0010] In a second aspect, this application provides a data compression processing apparatus, including:

[0011] An obtaining module, configured to obtain multiple first IP data in the IP data to be compressed;

[0012] A determination module, configured to determine prior information corresponding to the plurality of first IP data according to the plurality of first IP data;

[0013] A compression module, configured to perform parallel compression on the plurality of first IP data through a plurality of uplink data compression (UDC) engines based on the prior information.

[0014] In a third aspect, the present application provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the data compression processing method described in the first aspect is implemented.

[0015] In a fourth aspect, the present application provides an electronic device, including a storage medium, a processor, and a computer program stored on the storage medium and executable on the processor. When the processor executes the computer program, the data compression processing method described in the first aspect is implemented.

[0016] In a fifth aspect, the present application provides a chip, including one or more interface circuits and one or more processors; the interface circuit is configured to receive a signal from a memory of an electronic device and send the signal to the processor, and the signal includes computer instructions stored in the memory; when the processor executes the computer instructions, the electronic device is caused to execute the data compression processing method described in the first aspect.

[0017] By means of the above technical solutions, a data compression processing method, apparatus, electronic device, storage medium, and chip provided by the present application specifically first obtain a plurality of first IP data in the IP data to be compressed; then determine prior information corresponding to the plurality of first IP data according to the plurality of first IP data; and then perform parallel compression on the plurality of first IP data through a plurality of uplink data compression (UDC) engines based on the prior information. Compared with the current existing technologies, the present application divides the IP data to be compressed into a plurality of first IP data, respectively determines the prior information of the first IP data, realizes parallel compression of a large amount of IP data, and at the same time uses a plurality of UDC engines for compression, which can improve the compression speed, reduce the compression time, multiply the efficiency of the multi-core processor in processing UDC file compression, and can also improve the utilization efficiency of the uplink bandwidth.

[0018] The above description is only an overview of the technical solutions of the present application. In order to be able to understand the technical means of the present application more clearly, it can be implemented according to the content of the specification. And in order to make the above and other purposes, features, and advantages of the present application more obvious and understandable, the specific embodiments of the present application are hereinafter specifically exemplified. Description of the Drawings

[0019] The accompanying drawings herein are incorporated into and constitute a part of this specification, showing embodiments consistent with the present application, and are used together with the specification to explain the principles of the present application.

[0020] To more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the accompanying drawings required for use in the description of the embodiments or the prior art. Obviously, for those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings.

[0021] Figure 1 It shows a schematic flowchart of a data compression processing method provided by an embodiment of the present application;

[0022] Figure 2 It shows a schematic flowchart of a data compression processing method provided by an embodiment of the present application;

[0023] Figure 3 It shows a schematic diagram of an example provided by an embodiment of the present application;

[0024] Figure 4 It shows a schematic diagram of an example provided by an embodiment of the present application;

[0025] Figure 5 It shows a schematic diagram of an example provided by an embodiment of the present application;

[0026] Figure 6 It shows a schematic diagram of an example provided by an embodiment of the present application;

[0027] Figure 7 It shows a schematic diagram of an example provided by an embodiment of the present application;

[0028] Figure 8 It shows a schematic diagram of an example provided by an embodiment of the present application;

[0029] Figure 9 It shows a schematic diagram of an example provided by an embodiment of the present application;

[0030] Figure 10 It shows a schematic diagram of an example provided by an embodiment of the present application;

[0031] Figure 11 It shows a schematic structural diagram of a data compression processing device provided by an embodiment of the present application. Detailed Embodiments

[0032] The following will describe the embodiments of the present application in more detail with reference to the accompanying drawings. It should be noted that, without conflict, the embodiments in the present application and the features in the embodiments can be combined with each other.

[0033] In order to improve the technical problem that the current use of serial compression processing method leads to slow compression speed, long compression time, and thus reduces the compression efficiency of multi-core processors. This embodiment provides a data compression processing method, as Figure 1 shown, the method includes:

[0034] Step 101, obtain multiple first IP data in the IP data to be compressed.

[0035] In some examples, the method shown in this embodiment can be executed by a terminal device, and the terminal device may include a mobile phone, a tablet computer with a voice call function, a vehicle-mounted device, a camera, and so on. The specific technologies and specific device forms adopted by the terminal device are not limited in the embodiments of the present disclosure.

[0036] Optionally, the Internet Protocol (IP) data may be uplink IP packet data. Exemplarily, in the high-speed download scenario of a Time Division Duplexing (TDD) system, the IP data may be a large number of Transmission Control Protocol (TCP) acknowledgment (ACK) packets.

[0037] In the embodiment of the present application, the first IP data is multiple IP data obtained by splitting the IP data to be compressed, and the byte lengths of the first IP data are different from each other.

[0038] Step 102, determine the prior information corresponding to the multiple first IP data according to the multiple first IP data.

[0039] It should be noted that in the process of data compression, the corresponding prior information needs to be determined for each IP before compression can be performed; correspondingly, the prior information can be the compression benchmark of the IP data.

[0040] Exemplarily, if the string included in the first IP data is 1, 2, 2, 4, 5, 5, 7, 9, the prior information corresponding to the first IP data is 1, 2. In the process of compressing the first IP data, 1, 2 are existing strings, and the information such as the distance and length corresponding to the 1, 2 strings can be used to replace the 1, 2 strings in the first IP data, and then the compression result of the first IP data is obtained as A, 2, 4, 5, 5, 7, 9, where A represents the information such as the distance and length corresponding to the 1, 2 strings.

[0041] Step 103, based on the prior information, perform parallel compression on the multiple first IP data through multiple UDC engines.

[0042] For this embodiment, the UDC engine is an engine for data compression. Correspondingly, parallel compression can be performed by multiple UDC engines simultaneously.

[0043] It should be noted that the multiple UDC engines can be at least two. The specific number of engines needs to be adjusted according to the configuration of multi-core processing and the data volume of the IP data to be compressed. The terminal can set the maximum number of engines according to actual needs and its own software and hardware capabilities. At the same time, the terminal can decide whether to start multiple UDC engines or stop a certain UDC engine according to the actual cached service data volume. The number of multiple UDC engines is not specifically limited in the embodiments of this application.

[0044] Exemplarily, if the multi-core processor used for compression processing includes four UDC engines A, B, C, and D, the number of engines used for parallel compression can be determined according to the data volume of the IP data to be compressed. For example, if the data volume is small, engines A and B or B and C can be used for compression. If the data volume is large, all four engines can be used for compression processing, and so on. By analogy, no further examples will be given here.

[0045] Compared with the current existing technologies, in this embodiment, by dividing the IP data to be compressed into multiple first IP data and respectively confirming the prior information of the first IP data, parallel compression of a large amount of IP data is realized. At the same time, multiple UDC engines are used for compression, which can improve the compression speed, reduce the compression time, multiply the efficiency of the multi-core processor in processing UDC file compression, and also improve the utilization efficiency of the uplink bandwidth.

[0046] To further illustrate the specific implementation process of the method in this embodiment, this embodiment provides the following Figure 2 specific method, where the method includes:

[0047] Step 201, obtain multiple first IP data in the IP data to be compressed.

[0048] For this embodiment, before step 201, the method in this embodiment further includes: performing pre-check processing on the received IP data; based on the processing result of the pre-check processing, determining the IP data that meets the preset compression condition in the IP data as the IP data to be compressed.

[0049] Optionally, for all received IP packet data, it is necessary to perform Packet Data Convergence Protocol Sequence Number (PDCP SN) numbering in the order of receipt. Even if some packets are not compressed, they also participate in the PDCP SN numbering in order to avoid the disorder of the IP packet order received by the server.

[0050] In the application embodiment, the pre - inspection process for the received IP data can be as follows: after numbering the received IP data, each IP packet data needs to be scanned one by one, calculate the number of characters with American Standard Code for Information Interchange (ASCII) values between 144 and 255, and obtain the processing result of the pre - inspection process through Formula 1. Formula 1 is as follows:

[0051] R = n / L (Formula 1)

[0052] In Formula 1, R represents the ratio of the number of characters with ASCII values between 144 and 255 in the IP data to the total number of characters in the IP data, which is the processing result of the pre - inspection process; n represents the number of characters with ASCII values between 144 and 255; and L represents the total number of characters in the IP data.

[0053] In some examples, the preset compression condition can be a threshold value r for the ratio of the number of characters with ASCII values between 144 and 255 in the preset IP data to the total number of characters in the IP data. The threshold value r can be adjusted according to the usage scenario, and the specific value of the threshold value r is not specifically limited in the application embodiment.

[0054] It should be noted that as Figure 3 shown, the protocol describes that the static Huffman code table uses 9 - byte (bit) codewords to encode characters between 144 and 255. If the number of characters in this range in the IP packet is large, 1 more bit is required for each encoded character. Therefore, the packet after UDC compression may instead become longer.

[0055] Correspondingly, in the pre - inspection result of the IP data, if R is greater than r, the IP data is not suitable for compression; if R is less than r, the IP data can be compressed.

[0056] For the application embodiment, in addition to the above examples, the network may also configure UDC compression in other data transmission scenarios. These packets may be relatively large in size themselves, and some packets may have low compression efficiency or even become longer after compression, such as encrypted Encapsulating Security Protocol (ESP) packets, Secure Hypertext Transfer Protocol (Https) and other encrypted IP packets. For such packets, not only the processing resources and power of the terminal are wasted, but also the wireless bandwidth resources are wasted. Through packet pre - inspection, such packets can be avoided from being compressed.

[0057] Exemplarily, as Figure 4 shown, assume that due to the limited uplink bandwidth, a large amount of IP data has accumulated on the terminal side and cannot be sent out in time. The byte length of each IP data is 1KB, as Figure 5 shown, scan each IP packet one by one, calculate the number of characters with ASCII values between 144 and 255 and record it as n. If n / L (the byte length of the IP data packet) is greater than the preset threshold r, it is considered that the packet is not suitable for compression; otherwise, it is considered that the packet can be compressed.

[0058] Step 202: Analyze the configuration information of the first first IP data for the first UDC engine corresponding to the first first IP data.

[0059] Among them, the byte length of the first first IP data is the first preset byte.

[0060] It should be noted that the method of this embodiment further includes: for multiple first IP data other than the first first IP data, determine the prior information of the next first IP data based on the previous first IP data.

[0061] Among them, the byte lengths of multiple first IP data other than the first first IP data increase sequentially based on the first preset byte.

[0062] Optionally, step 202 may specifically include: determining the second IP data including the second preset byte at the end of the previous first IP data as the prior information corresponding to the next first IP data.

[0063] Among them, the second preset byte is less than half of the first preset byte, and the byte capacity of the second preset byte is the same as the compression cache of the second UDC engine corresponding to the current first IP data.

[0064] In some examples, if the characters of the previous first IP data are 1, 2, 3, 3, 4, 5, 6, 7, 7, and if the second preset byte is 3, then the second IP data including the second preset byte at the end of the previous first IP data is the last 3-byte data, that is, 6, 7, 7, and 6, 7, 7 are used as the prior information of the next first IP data.

[0065] As another optional way, if the characters of the next first IP data are 1, 2, 2, 3, 4, 4, 6, 8, 9, and if the second preset byte is 4, then the second IP data including the second preset byte at the end of the previous first IP data is the last 4-byte data, that is, 4, 6, 8, 9, and 4, 6, 8, 9 are used as the prior information of the next first IP data, and no more examples are given here.

[0066] It should be noted that the size of the second preset byte is determined by the byte capacity of the compression buffer of the second UDC engine corresponding to the next first IP data, that is, the size of the second preset byte of the previous second IP data is the same as the byte capacity of the compression buffer of the second UDC engine corresponding to the next first IP data. Correspondingly, the UDC engine compression buffer is used to store the prior information of the first IP data.

[0067] Exemplarily, if the byte capacity of the compression buffer of the UDC engine for the (n + 1)-th first IP data is 3 bytes, then the byte length of the second IP data corresponding to the n-th first IP data is 3 bytes.

[0068] Step 203: Based on the analysis result of the configuration information, determine the prior information of the first first IP data.

[0069] In the embodiment of the present application, step 203 may specifically include: if a compression dictionary is configured in the compression buffer of the first UDC engine, determine the compression dictionary as the prior information of the first first IP data; if no compression dictionary is configured in the compression buffer of the first UDC engine, initialize the prior information of the first first IP data.

[0070] For this embodiment, the compression dictionary may be the IP data commonly used in the compression process as the prior information of the first first IP data. If no compression dictionary is configured in the Compression Buffer of the first UDC engine, the prior information of the first first IP data is initialized to zero.

[0071] Step 204: Based on the prior information, parallelly compress multiple first IP data through multiple UDC engines.

[0072] In some examples, before step 204, the method of this embodiment further includes: respectively allocate multiple first IP data with the same number as the number of UDC engines to the compression buffers to be compressed of multiple UDC engines; allocate at least one first IP data other than the multiple first IP data with the same number as the number of UDC engines to the compression buffer to be compressed of the third UDC engine in ascending order of the included byte length.

[0073] Wherein, the third UDC engine is the first UDC engine among the target number of UDC engines to complete the compression of the first IP data.

[0074] It should be noted that before step 204, the method of this embodiment further includes: distributing the prior information corresponding to the first IP data with the same number as the UDC engines to the compression caches of the target number of UDC engines respectively; sequentially distributing the prior information corresponding to at least one first IP data other than the first IP data with the same number as the UDC engines to the compression cache of the third UDC engine.

[0075] Optionally, the lookahead buffer of the UDC engine is used to store the first IP data to be compressed.

[0076] Exemplarily, based on the example in step 201, as Figure 6 shown, if the compression buffer size win_size = 4KB, for compressible packets, select consecutive cumulative K bytes (more than twice the compression buffer size) of packets and allocate them to compression engine #1, and then allocate consecutive cumulative K + i * wind_size (i > 1) byte packets to compression engine #2 for compression.

[0077] As Figure 7 shown, fill the compression buffer. If a dictionary is configured, use the dictionary to fill compression buffer #1; if there is no dictionary, clear compression buffer #1; use the content of the last several packets with the length corresponding to the compression buffer size to fill compression buffer #2.

[0078] As Figure 8 shown, the two compression engines start to compress the allocated packets respectively. As Figure 9 shown, when UDC engine (Engine) #1 has finished compressing all data, the IP packets #18 / #19 / #20#21 allocated to UDC Engine #2 have not been compressed yet. Fill the compression cache #1 with the last several packets of the last wind_size size, and allocate X + i * wind_size (i > 1) bytes of data to UDC Engine #1 according to the remaining X bytes of data to be compressed by UDC Engine #2. Repeat the above process until all IP packets are compressed.

[0079] It should be noted that when the terminal allocates data to the completed UDC Engine again, the allocated data volume needs to be i * wind_size (i > 1) more than the remaining uncompressed data volume X bytes of the working UDC Engine, so as to ensure that there is enough uncompressed prior data to fill the compression cache when the working engine finishes compression.

[0080] Exemplarily, if the first IP data is 3 bytes, the Compression Buffer capacity is 1 byte, the second IP data needs to be 4 bytes, the third IP data needs to be 5 bytes, and so on. Specific examples are not given here.

[0081] The existing 3GPP UDC compression scheme is currently mainly applied to IMS signaling compression. The IMS signaling uses the Session Initiation Protocol (SIP) encoding method, which has the characteristics of many repeated strings and low transmission frequency, and has low requirements for UDC processing performance.

[0082] When the existing Deflate algorithm performs data compression, as Figure 10 shown, it will use Compression Buffer, Lookahead Buffer, and a hash table for recording the information of repeated strings existing in the Compression Buffer. Their functions are as follows: Compression Buffer is used to store the processed source text data and works in a first-in, first-out manner; Lookahead Buffer is used to store the text data to be compressed, also using the first-in, first-out method; hash Table stores the position information of possible repeated strings in the Compression Buffer according to a certain hash algorithm.

[0083] When the traditional Deflate compression algorithm works, the compression steps are as follows: Initialize the Compression Buffer. If there is a dictionary, fill it with the dictionary; otherwise, initialize it to all zeros; Read data from the file to fill the Lookahead Buffer; Read 3 bytes of data from the Lookahead Buffer and calculate its corresponding hash value according to the hash algorithm; Search the hash table to determine whether there is a string with the same hash value; If there is a string with the same hash value, match the data in the Lookahead Buffer with the data at the corresponding position in the Compression Buffer. If the match is successful, replace the repeated string with (distance, length) information; Otherwise, output these 3 characters as single characters, push them into the Compression Buffer and update the hash table; Perform static Huffman encoding on the output single characters or (distance, length); Read the processed length of data from the data to be compressed and update it to the end of the Lookahead Buffer; Repeat the steps until all data is compressed.

[0084] The embodiments of the present application belong to the field of wireless communication data encoding and compression, and can also be applied to the compressed storage of text files, the compressed transmission of hypertext protocol data such as Https and Real-time Transport Protocol (RTP) in the communication field, so as to improve the storage efficiency and transmission efficiency of data.

[0085] Compared with the current existing technologies, in this embodiment, the IP data to be compressed is divided into multiple first IP data, the prior information of the first IP data is respectively confirmed, and then the prior information required for IP data compression is input into the compression cache of the corresponding UDC engine, so as to realize the parallel compression of a large amount of IP data. At the same time, multiple UDC engines are used for compression, which can improve the compression speed, reduce the compression time, and multiply the efficiency of the multi-core processor in processing UDC file compression. It can also improve the utilization efficiency of the uplink bandwidth; by pre-checking and processing the received IP data, the data that is not suitable for UDC compression can be identified, and the IP data with low compression efficiency or that may become longer after compression can be removed, avoiding the waste of software and hardware resources and wireless bandwidth resources.

[0086] Further, as Figure 1 and Figure 2 a specific implementation of the method shown, this embodiment provides a data compression processing device, as Figure 11 shown, the device includes: an acquisition module 31, a determination module 32, and a compression module 33.

[0087] The acquisition module 31 is configured to acquire multiple first IP data in the IP data to be compressed;

[0088] The determination module 32 is configured to determine the prior information corresponding to the multiple first IP data according to the multiple first IP data;

[0089] The compression module 33 is configured to perform parallel compression on the multiple first IP data through multiple uplink data compression UDC engines based on the prior information.

[0090] In some examples of this embodiment, the determination module 32 is specifically configured to analyze the configuration information of the first UDC engine corresponding to the first first IP data for the first first IP data, where the byte length of the first first IP data is the first preset byte; based on the analysis result of the configuration information, determine the prior information of the first first IP data.

[0091] In some examples of this embodiment, the byte lengths of multiple first IP data other than the first first IP data are incremented in sequence based on the first preset byte; correspondingly, the determining module 32 is further specifically configured to, for multiple first IP data other than the first first IP data, determine the prior information of the next first IP data according to the previous first IP data.

[0092] In some examples of this embodiment, the determining module 32 is further specifically configured to determine, as the prior information corresponding to the next first IP data, a second IP data whose end contains a second preset byte in the previous first IP data, where the second preset byte is less than half of the first preset byte, and the second preset byte is the same as the byte capacity of the second UDC engine compression cache corresponding to the current first IP data.

[0093] In some examples of this embodiment, the determining module 32 is further specifically configured to, if the first UDC engine configures a compression dictionary in the compression cache, determine the compression dictionary as the prior information of the first first IP data; if the first UDC engine does not configure a compression dictionary in the compression cache, perform an initialization process on the prior information of the first first IP data.

[0094] In some examples of this embodiment, the compression module 33 is further configured to respectively allocate multiple first IP data with the same number as the UDC engines to the compression caches to be compressed of the multiple UDC engines; allocate at least one first IP data other than the multiple first IP data with the same number as the UDC engines to the compression cache to be compressed of the third UDC engine in ascending order of the included byte lengths, where the third UDC engine is the first UDC engine among the target number of UDC engines to complete the compression of the first IP data.

[0095] In some examples of this embodiment, the compression module 33 is further configured to respectively allocate the prior information corresponding to the first IP data with the same number as the UDC engines to the compression caches of the target number of UDC engines; sequentially allocate the prior information corresponding to at least one first IP data other than the first IP data with the same number as the UDC engines to the compression cache of the third UDC engine.

[0096] In some examples of this embodiment, the obtaining module 31 is further configured to perform a pre - inspection process on the received IP data; based on the processing result of the pre - inspection process, determine the IP data that meets the preset compression condition in the IP data as the IP data to be compressed.

[0097] It should be noted that for other corresponding descriptions of each functional unit involved in a data compression processing device provided in this embodiment, reference can be made to Figure 1and Figure 2 The corresponding descriptions in it will not be elaborated here.

[0098] Based on the above as Figure 1 and Figure 2 shown in the method, correspondingly, this embodiment also provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the method shown in the above as Figure 1 and Figure 2 is implemented.

[0099] Based on such an understanding, the technical solution of this application can be embodied in the form of a software product, and the software product can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.), and includes several instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods of various implementation scenarios of this application.

[0100] Based on the above as Figure 1 and Figure 2 shown in the method, as well as Figure 11 shown in the virtual device embodiment, in order to achieve the above object, this embodiment of the application also provides an electronic device, such as intelligent terminals such as smart phones, tablet computers, drones, and intelligent robots. The device includes a storage medium and a processor; the storage medium is used to store a computer program; the processor is used to execute the computer program to implement the method shown in the above as Figure 1 and Figure 2 is implemented.

[0101] Optionally, the above-mentioned physical device may further include a user interface, a network interface, a camera, a radio frequency (RF) circuit, sensors, an audio circuit, a WI-FI module, and so on. The user interface may include a display screen (Display), an input unit such as a keyboard (Keyboard), etc., and optionally the user interface may further include a USB interface, a card reader interface, etc. The network interface may optionally include a standard wired interface, a wireless interface (such as a WI-FI interface), etc.

[0102] Those skilled in the art can understand that the above-mentioned physical device structure provided in this embodiment does not constitute a limitation to the physical device, and may include more or fewer components, or combine some components, or arrange different components.

[0103] The storage medium may further include an operating system and a network communication module. The operating system is a program for managing the hardware and software resources of the above-mentioned physical device, and supports the operation of information processing programs and other software and / or programs. The network communication module is used to implement communication between the components inside the storage medium, as well as communication with other hardware and software in the information processing physical device.

[0104] Based on the methods shown above such as Figure 1 and Figure 2 and the virtual device embodiments shown in Figure 11 This embodiment also provides a chip, including one or more interface circuits and one or more processors; the interface circuit is configured to receive signals from a memory of an electronic device and send the signals to the processor, and the signals include computer instructions stored in the memory; when the processor executes the computer instructions, the electronic device is caused to execute the methods shown above such as Figure 1 and Figure 2 shown.

[0105] Through the description of the above embodiments, those skilled in the art can clearly understand that this application can be implemented by means of software plus a necessary general hardware platform, or can be implemented by hardware. By applying the solution of this embodiment, compared with the current existing technologies, in this embodiment, the IP data to be compressed is divided into multiple first IP data, the prior information of the first IP data is respectively confirmed, and then the prior information required for IP data compression is input into the compression cache of the corresponding UDC engine, so as to realize parallel compression of a large amount of IP data. At the same time, multiple UDC engines are used for compression, which can improve the compression speed, reduce the compression time, and multiply the efficiency of the multi-core processor in processing UDC file compression, and can also improve the utilization efficiency of the uplink bandwidth; by pre-checking and processing the received IP data, the data that is not suitable for UDC compression can be identified, and the IP data with low compression efficiency or that may become longer after compression can be removed, avoiding the waste of software and hardware resources and wireless bandwidth resources.

[0106] It should be noted that in this article, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the term "comprising", "including" or any other variation thereof is intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements not only includes those elements, but also includes other elements not expressly listed, or also includes elements inherent to such process, method, article or device. Without further limitation, an element defined by the statement "including a..." does not exclude the existence of additional identical elements in the process, method, article or device including the element.

[0107] The above are only specific embodiments of the present application, enabling those skilled in the art to understand or implement the present application. Various modifications to these embodiments will be obvious to those skilled in the art, and the general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to these embodiments described herein, but rather will conform to the broadest scope consistent with the principles and novel features claimed herein.

Claims

1. A data compression processing method, characterized in that: include: Acquire a plurality of first IP data from the international interconnection protocol IP data to be compressed; Determine, based on the plurality of first IP data, prior information corresponding to the plurality of first IP data; Based on the prior information, the multiple first IP data are compressed in parallel by multiple uplink data compression UDC engines.

2. The method according to claim 1, characterized in that The determining, based on the plurality of first IP data, the prior information corresponding to the plurality of first IP data includes: For the first first IP data, performing configuration information analysis on the first UDC engine corresponding to the first first IP data, wherein the byte length of the first first IP data is the first preset byte; Based on the configuration information analysis result, the prior information of the first first IP data is determined.

3. The method according to claim 2, characterized in that The byte lengths of the plurality of first IP data except the first first IP data are increased in sequence based on the first preset byte; The determining, based on the plurality of first IP data, the prior information corresponding to the plurality of first IP data further includes: For a plurality of first IP data except the first first IP data, the prior information of the next first IP data is determined according to the previous first IP data.

4. The method according to claim 3, characterized in that The determining, for the plurality of first IP data except the first first IP data, the prior information of the next first IP data according to the previous first IP data, comprises: The second IP data containing the second preset byte at the end of the previous first IP data is determined as the prior information corresponding to the next first IP data, the second preset byte is smaller than half of the first preset byte, and the second preset byte is the same as the byte capacity of the second UDC engine compression cache corresponding to the current first IP data.

5. The method according to claim 2, characterized in that: The determining, based on the configuration information analysis result, the prior information of the first first IP data includes: If the first UDC engine is configured with a compression dictionary in the compression cache, the compression dictionary is determined as the prior information of the first first IP data.

6. The method according to claim 5, characterized in that The determining the prior information of the first first IP data based on the configuration information analysis result further includes: If the first UDC engine is not configured with a compression dictionary in the compression cache, the prior information of the first first IP data is initialized.

7. The method according to claim 1, characterized in that Before compressing the plurality of first IP data in parallel by using a plurality of uplink data compression UDC engines based on the prior information, the method further includes: Allocate a plurality of first IP data having the same number as the number of UDC engines to the to-be-compressed buffers of the plurality of UDC engines respectively; According to the byte length from short to long, at least one first IP data except multiple first IP data with the same number as the UDC engines is allocated to the cache to be compressed of the third UDC engine, and the third UDC engine is the first UDC engine among the target number of UDC engines to complete the compression of the first IP data.

8. The method according to claim 1, characterized in that Before compressing the plurality of first IP data in parallel by using a plurality of uplink data compression UDC engines based on the prior information, the method further includes: Allocate the prior information corresponding to the first IP data of the same number as the number of UDC engines to the compression caches of the target number of UDC engines respectively; The prior information corresponding to at least one first IP data except the first IP data having the same number as that of the UDC engines is sequentially allocated to the compression buffer of the third UDC engine.

9. The method according to claim 1, characterized in that: Before obtaining a plurality of first IP data in the IP data to be compressed, the method further includes: Perform pre-inspection processing on the received IP data; Based on the processing result of the pre-checking processing, the IP data in the IP data that meets the preset compression condition is determined as the IP data to be compressed.

10. A data compression processing device, characterized in that: include: An acquisition module, configured to acquire a plurality of first IP data from the IP data to be compressed; A determination module, configured to determine the prior information corresponding to the plurality of first IP data according to the plurality of first IP data; The compression module is configured to compress the multiple first IP data in parallel through multiple uplink data compression UDC engines based on the prior information.

11. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 1 to 9 is implemented.

12. An electronic device comprising a storage medium, a processor, and a computer program stored in the storage medium and executable on the processor, characterized in that: When the processor executes the computer program, the method according to any one of claims 1 to 9 is implemented.

13. A chip, characterized in that: The electronic device comprises one or more interface circuits and one or more processors; the interface circuit is used to receive a signal from a memory of the electronic device and send the signal to the processor, wherein the signal includes a computer instruction stored in the memory; when the processor executes the computer instruction, the electronic device executes the method described in any one of claims 1 to 9.

Images