WO2018161791A1

WO2018161791A1 - Method and device for compressing executable file

Info

Publication number: WO2018161791A1
Application number: PCT/CN2018/076624
Authority: WO
Inventors: 刘兆祥
Original assignee: 深圳创维－Rgb电子有限公司
Priority date: 2017-03-10
Filing date: 2018-02-13
Publication date: 2018-09-13
Also published as: CN106909398B; CN106909398A

Abstract

A method and device for compressing an executable file. The method comprises: analyzing a functional attribute and a storage format attribute of each data portion in a plurality of data portions of the executable file (S110); identifying, according to the functional attribute, a compressible data portion in the plurality of data portions to serve as target data (S120); obtaining, according to a storage format attribute of the target data, a compression strategy of the target data (S130); and compressing, according to the compression strategy, the target data, updating a storage format attribute of the target data, and obtaining a compressed executable file (S140). The technical solution is adopted to reduce a storage space occupied by an executable file.

Description

Executable file compression method and device

Technical field

The present disclosure relates to the field of embedded technologies, and in particular, to a method and an apparatus for compressing an executable file.

Background technique

An executable file refers to a file that can be loaded and executed by the operating system. Under the Windows operating system, the executable program is, for example, an .exe file, a .sys file, .com, and the like. Different types of executables require different compression algorithms. The executable itself takes up a certain amount of storage space. Additional compression of the compression and/or decompression algorithms is required during the compression/decompression of the executable. When compressing/decompressing multiple executable files, the storage space is large, and the system may not provide enough storage space, so the compression efficiency is lowered, and the cost of the memory chip is increased.

Summary of the invention

To solve the above related technical problem, the present disclosure provides a method and a device for compressing an executable file, so as to improve the compression ratio of the executable file, save storage space occupied by the executable file, and save hardware costs.

In a first aspect, an embodiment of the present disclosure provides a method for compressing an executable file, the method comprising: analyzing a function attribute and a storage format attribute of each of a plurality of data portions of the executable file; The function attribute, the compressible data part is identified as the target data from the plurality of data parts; and the compression strategy of the target data is obtained according to the storage format attribute of the target data; according to the compression policy, The target data is compressed, and the storage format attribute of the target data is updated to obtain a compressed executable file.

In a second aspect, an embodiment of the present disclosure provides an apparatus for executing an executable file, where the apparatus includes: an attribute analysis module, an attribute analysis module, a compression policy determination module, and a compression module.

The attribute analysis module is configured to analyze functional attributes and storage format attributes of each of the plurality of data portions of the executable file.

The attribute analysis module is configured to identify the compressible data portion from the plurality of data portions as the target data according to the function attribute.

The compression policy determination module is configured to obtain a compression strategy of the target data according to a storage format attribute of the target data.

The compression module is configured to compress the target data according to the compression policy, and update a storage format attribute of the target data to obtain a compressed executable file.

In a third aspect, an embodiment of the present disclosure provides an electronic device. The electronic device includes: one or more processors; and a memory coupled to the one or more processors. The memory stores one or more programs, the one or more programs being configured to cause the one or more processors to perform the compression method of the executable file described above.

In a fourth aspect, an embodiment of the present disclosure provides a non-transitory computer readable storage medium, wherein the storage medium stores computer instructions configured to cause a computer to execute the compression method of the executable file described above.

The method and device for compressing an executable file according to an embodiment of the present invention first analyzes a function attribute and a storage format attribute of each data part of an executable file, and can identify a compressible data part as a target according to a functional attribute of each data part. Data; according to the storage format attribute of the target data, a compression strategy of the target data is obtained; according to the compression strategy, the compressible target data is compressed, and the storage format attribute of the target data is updated to obtain a compressed executable file. By adopting the above technical solution, the compressed executable file occupies less storage space.

DRAWINGS

The drawings used in the description of the embodiments of the present invention will be briefly described below. The drawings in the following description are only some embodiments of the present invention, and those skilled in the art will not make any creative work. Further drawings may also be obtained in accordance with the teachings of the embodiments of the present invention and the drawings.

FIG. 1 is a flowchart of a method for compressing an executable file according to an embodiment of the present invention.

Figure 2A shows an executable binary file data generated after a FLASH operation.

Figure 2B shows yet another executable binary file data generated after a FLASH operation.

FIG. 3A is a diagram showing a data storage structure distribution of a pre-optimized TV FLASH memory according to an embodiment of the present invention.

FIG. 3B is a schematic diagram of a data storage structure distribution of an optimized TV FLASH memory according to an embodiment of the present invention.

FIG. 4 is a flowchart of a method for compressing an executable file according to an embodiment of the present invention.

FIG. 5 is a schematic diagram of comparison of storage space occupied by an executable file before and after compression according to an embodiment of the present invention.

FIG. 6 is a structural block diagram of an apparatus for compressing an executable file according to an embodiment of the present invention.

detailed description

The technical solutions of the embodiments of the present invention will be further described in detail below with reference to the accompanying drawings. It is obvious that the described embodiments are only a part of the embodiments of the present invention, but not all embodiments. All other embodiments obtained by a person skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

FIG. 1 is a flowchart of a method for compressing an executable file according to an embodiment of the present invention. The method of the present embodiment can be performed by, for example, a television and/or a television set-top box, etc., which can be implemented by software and/or hardware deployed in a television and/or television set-top box, which software and/or hardware can generally be integrated In an embedded system. As shown in FIG. 1, the method may include steps S110 to S140.

At S110: analyzing functional attributes and storage format attributes of respective data portions of the executable file.

The executable file refers to a file that is loaded and executed by the operating system, and the executable file mentioned in this embodiment is, for example, an executable binary file. The above executable binary file may be a binary file that has been compressed, or a binary file that has not been compressed. The person skilled in the art can determine whether the binary file has been compressed according to the compression identifier carried in the executable binary file.

Exemplarily, the storage format attribute of each data part of the executable file may be obtained from an identifier corresponding to the storage format corresponding to the data part in the corresponding storage path of each data part, and generally includes the following three cases.

1. No compression identifier is added to the corresponding storage path;

For an executable file that does not have any compression identifier added to the corresponding storage path in each data portion, the compiler only needs to complete the normal compilation processing when compiling the file, without any compression and decompression processing.

2. A compression flag with a lower compression ratio is added to the corresponding storage path;

The preset storage format attribute in the embodiment of the present invention refers to a first preset storage format (such as an identifier "-g") or a second preset storage format (such as an identifier "-7") in the storage path. The feature attribute that the saved executable has. The compression ratios corresponding to the two storage formats are different, the compression ratio corresponding to the first preset storage format is lower, and the compression ratio corresponding to the second preset storage format is higher. Specifically, when the tag of the first preset storage format is “-g”. If a "-g" identifier is detected in the corresponding storage path of a portion of the data of the executable binary file, the compiler indicates that the data portion of the executable binary file is compiled during the data portion of the executable binary file. The compression process is performed in a small compression ratio to save storage space occupied by the binary file, thereby saving material cost of hardware (such as a memory chip) storing the binary file.

3. A compression flag with a higher compression ratio is added to the corresponding storage path.

When the identifier of the second preset storage format is "-7". If the "-7" identifier is detected in the corresponding storage path of a certain data portion of the executable binary file, the compiler indicates that the data portion is larger in the process of compiling the data portion of the binary file. The compression ratio is compressed. Compared with the first preset storage format with the identifier “-g”, the above compression method can further save the storage space occupied by the executable binary file, thereby saving the storage of the binary. The material cost of the hardware of the file.

It should be noted that the storage format of each data portion of the executable binary file is not limited to the three forms listed above.

At S120: a compressible data portion is identified from the plurality of data portions as the target data according to the function attribute.

In an embodiment, before each part of the executable binary file is compressed, it is necessary to determine whether each data portion in the executable binary file can be compressed according to the basic characteristic of the functional attributes of each data portion. Illustratively, the functional attributes of the various data portions in the executable binary file may include, but are not limited to, such as storage attributes, compression or decompression attributes, and the like. In a specific operation, data of an executable binary file having a decompressed attribute or a tag attribute may not be compressed against its data attribute; and for data in a binary file having a storage attribute, It can be compressed to save storage space.

Exemplarily, the following takes the actual structure of the system as an example. The system preferably has a NOS (No Operating System) system:

FIG. 2A is an executable binary file generated after a flash memory (Flash Memory, generally referred to as FLASH) operation. As shown in FIG. 2A, by performing a write FLASH operation on the structure, in the actual generated file, 0x21000 is the actually written data. Since the address corresponds to the tag code portion, the generated file data cannot be compressed and must be stored in the actual occupied byte size.

Illustrative, for the following executable binary:

Specifically, FIG. 2B is another executable binary file generated after the FLASH operation is written. As shown in FIG. 2B, it can be understood by those skilled in the art that in the binary file, the data corresponding to the address 0002100h is consistent with the written data (54454C09 and 58336900), indicating that the part of the data in the binary file is OK. Being compressed.

By analyzing the functional attributes of each data part of the executable binary file, the target data that can be compressed in the binary file can be quickly identified, thereby quickly locking the compressible, ie, the object to be processed, and narrowing the processing range.

At S130: obtaining a compression strategy of the target data according to the storage format attribute of the target data.

Illustratively, different storage format attributes correspond to different compression strategies. In some embodiments, the target data corresponds to a storage attribute in the storage path that is not added with any compression identifier, indicating that the target data is not compressed at all. According to this, the next compression strategy of the target data can be obtained, that is, the partial data can be compressed according to a certain compression manner, thereby reducing the storage space of the target data.

In some embodiments, the target data is stored in the corresponding path in the form of a first preset storage format (eg, the identifier is "-g"), indicating that the target data is currently compressed in a compressed manner with a lower compression ratio. According to this, the next compression strategy of the target data can be obtained, and the part of the target data can be compressed in a certain compression manner higher than the current compression ratio.

In some embodiments, the target data is stored in the corresponding path according to the second preset storage format (eg, the identifier is “-7”), indicating that the target data is currently compressed by a compression method with a higher compression ratio. of. According to this, it is possible to obtain the next compression strategy of the target data, that is, it is possible to further reduce the compression ratio of the target data by replacing the compression method.

At S140: compressing the target data according to the compression policy, and updating the storage format attribute of the target data to obtain a compressed executable file.

For the compressible target data, according to the compression strategy determined in the above steps, the compression processing may be performed, and the storage format attribute in the storage path corresponding to the target data may be updated, so that the storage format attribute of the compressed target data is The current compression strategy corresponds. Thereby, the decompression strategy corresponding to the current compression strategy is selected when the target data is executed. Therefore, by identifying the storage format attribute of the target data, it can be determined whether the target data is compressed or in what manner.

Further, after the compressed executable file is saved in the FLASH, the remaining storage space of the FLASH can be saved by making full use of the remaining space, so that the utilization of the FLASH memory space is maximized. The optimization method is as follows.

FIG. 3A is a diagram showing a data storage structure distribution of a pre-optimized TV FLASH memory according to an embodiment of the present invention. As shown in FIG. 3A, in the storage space of 0-57 BANK (storage unit), the executable file of the software is mainly stored, so the size of the executable file is at most 58×64K=3712K. If the size of the executable is larger than this space, there is a risk of overwriting the data area. For data other than the executable file, the storage space is allocated according to the size of the actual structure and the actual number of channels. After all the data is stored, only 2K of free space remains, that is, the storage space is insufficient. Therefore, in order to optimize the storage space to achieve the streamlined requirements, one more BANK is saved in the seven BANKs in FIG. 3A to store data. The optimization process is as follows.

After analysis, in the 63rd BANK, the actual data is only 304 BYTE, but the storage space of FLASH is divided into BANK units, so the data of 304 BYTE in the 63rd BANK occupies the entire 63rd. BANK, caused a waste of FLASH storage space resources. FIG. 3B is a diagram showing a data storage structure distribution of an optimized TV FLASH memory according to Embodiment 1 of the present invention. As shown in FIG. 3B, by upgrading the HDCP, data of the High-bandwidth Digital Content Protection (HDCP) portion can be directly written into a predetermined memory (for example, the 58th BANK). In this way, you can save a BANK to store other program code. In addition, the data storage mode can be modified to not save, the entire table will be initialized when the system is initialized, and then when the different timings are switched, the data can be directly loaded from the table, which saves a BANK. come out. Therefore, by adopting the above method of optimizing memory allocation, the technical effect of further saving storage space can be achieved.

Optionally, for the method for saving storage space, those skilled in the art can understand that for a picture that is not needed in subsequent program execution, it can be deleted in the program data or compiled in the picture. The compression ratio of the image is modified to reduce the size of the executable file that generates the image, thereby further saving the storage space required by the program.

Optionally, the mode of masking the code that is not required to be executed in the program may be modified to directly delete the mode in which the part is shielded from being executed, thereby achieving the technical effect of further saving the storage space of the executable file. Because the technical means of masking the code is just not executing this part of the code, but in the original executable binary file, this part of the blocked executable code is still physically present in the original executable binary file, so this Part of the blocked code still occupies a certain amount of physical storage space. If the code is removed directly from the code that is being deliberately not executed, the code is physically removed, and the code is removed to further save the executable binary compared to the technical means of masking not being executed. The storage space for the file.

The embodiment provides a method for compressing an executable file. After analyzing functional attributes and storage format attributes of each data portion of the executable file, according to functional attributes such as storage, compression, or decompression of each data portion of the executable file, The target data that can be compressed in each data portion of the executable file is identified. According to the storage format attribute of the target data, a compression strategy of the target data can be obtained. The compression strategy may include compression without compression, compression according to a new compression method with a larger original compression ratio, and compression according to a new compression method with a smaller original compression ratio. According to the compression strategy, the target data is compressed, and the storage format attribute of the target data is updated to obtain a compressed executable file. By adopting the above technical solution, the compressed executable file can occupy less storage space, and the technical effect of saving the storage hardware material cost required for the executable file can be achieved, thereby indirectly improving the market competitiveness of the corresponding product.

FIG. 4 is a flowchart of a method for compressing an executable file according to an embodiment of the present invention. The present embodiment further optimizes the step S130 "the compression strategy of obtaining the target data according to the storage format attribute of the target data" on the basis of the embodiment shown in FIG. 1. Referring to FIG. 4, a method for compressing an executable file according to an embodiment of the present invention includes steps S210 to S270.

At S210: analyzing the functional attributes and storage format attributes of each data portion of the executable file.

At S220: a compressible data portion is identified from the plurality of data portions as the target data according to the function attribute.

At S230, it is determined whether the current storage format matches the preset storage format. If the current storage format matches the preset storage format, step S240 is performed; if it is determined that the current storage format does not match the preset storage format, step S260 is performed. .

Exemplarily, since the compressible target data identified through step S220 may be data that has been subjected to compression processing, it may also be data that has not undergone any compression. Therefore, by comparing the current storage format of the target data with the preset storage format, if the current storage format of the target data does not match the preset storage format, it is possible to indicate that the target data is data that has not been compressed. If the current storage format matches any of the preset storage formats, the current target data is data that has undergone compression processing according to a compression ratio corresponding to the preset storage format. Therefore, the step 230 can be used as a basis for determining a compression strategy of the current target data. After the compression policy is determined, the current target data can be further compressed by selecting an appropriate compression mode, thereby saving the storage space occupied by the target data.

In S240, it is determined whether the current storage format matches the first preset storage format corresponding to the first compression policy, and if the current storage format matches the first preset storage format corresponding to the first compression policy, step S250 is performed; If the current storage format does not match the first preset storage format corresponding to the first compression policy, step S260 is performed.

For example, if the current storage format of the target data matches the preset storage format, if the current storage format is further determined to be the first preset storage format corresponding to the first compression policy (eg, the identifier is “-g” Matching, it can be said that the target data has been compressed according to the first compression strategy. At this time, the compression strategy of the target data may be changed according to actual needs, and the original first preset storage format of the target data (such as the identifier “-g”) may be modified accordingly to improve the compression ratio of the target data. To achieve the technical effect of saving executable file storage space and saving storage material cost.

Exemplarily, whether the current storage format matches the second preset storage format corresponding to the second compression policy (eg, the identifier is “-7”), and if the current storage format corresponds to the second compression policy. If the second preset storage format matches, it can be stated that the target data has been compressed according to the second compression strategy. At this time, the compression strategy of the target data may also be changed according to actual needs, and the original second preset storage format (such as the identifier "-7") of the target data may be modified accordingly.

In S250, the target data is compressed according to the second compression policy corresponding to the second preset storage format, where the compression ratio corresponding to the second compression policy is greater than the compression ratio corresponding to the first compression policy, and step S270 is continued.

Exemplarily, if the first preset pre-storage format (such as the identifier is “-g”) in the target data is modified to the second preset storage format (if the identifier is “-7”), the target data may be upgraded. The compression ratio saves storage space. Specifically, FIG. 5 is a schematic diagram of comparison of storage space occupied by an executable file before and after compression according to Embodiment 2 of the present invention. As shown in FIG. 5, an uncompressed file (vdplayer. Bin) takes up the size of the file itself in the storage space to save storage space (1270KB); for the compressed file (vdplayer.bin), it takes up a small amount of storage space (380KB).

Exemplarily, in some specific cases, for some target data, according to actual needs, if compression is not required or not suitable, the second preset storage format (such as the identifier is "-" 7") is modified to the first preset storage format (such as the identifier "-g") to save the storage space occupied by the target data itself.

At S260: determining a compression strategy of the target data according to the preset storage format, and proceeding to step S270.

Exemplarily, if the current storage format of the target data does not match the preset storage format, it may indicate that the target data is not compressed. At this time, the preset storage format (for example, the first preset storage format or the second preset storage format) may be added to the path corresponding to the target data, and when the target data is compressed, the editor may The target data is compressed according to the compression mode corresponding to different storage formats, and target data of different compression ratios are obtained, thereby saving the storage space of the target data in the executable file and reducing the hardware cost required for storing the executable file.

At S270: compressing the target data according to the compression strategy, and updating the storage format attribute of the target data to obtain a compressed executable file.

In the second embodiment, on the basis of the foregoing embodiment, the current storage format of the target data is matched with the preset storage format, and different compression policies are adopted according to the matching result, and correspondingly added according to the selected compression policy. Or change the original storage format attribute of the current target data to the new storage format attribute, so that the compression mode of the target data can be added or changed according to actual needs, thereby improving the compression ratio of the target data of the executable file and saving the target data. Taking up storage space, indirectly achieves the technical effect of saving storage material costs.

The following is an embodiment of a compression device for an executable file provided by an embodiment of the present invention. The compression device of the executable file and the compression method for providing the executable file according to the foregoing embodiments belong to the same inventive concept.

FIG. 6 is a structural block diagram of an apparatus for compressing an executable file according to an embodiment of the present invention. The apparatus may be implemented by software and/or hardware deployed in, for example, a television and/or a television set top box, where the apparatus may generally be integrated into an embedded system of hardware entities such as televisions and/or television set top boxes.

As shown in FIG. 6, the apparatus includes: an attribute analysis module 310, a target data identification module 320, a compression policy determination module 330, and a compression module 340.

The attribute analysis module 310 is configured to analyze function attributes and storage format attributes of each part of the executable file data;

The target data identification module 320 is configured to identify, according to the function attribute, the compressible target data in each part of the data;

The compression policy determination module 330 is configured to obtain a compression strategy of the target data according to a storage format attribute of the target data.

The compression module 340 is configured to compress the target data according to the compression policy, and update a storage format attribute of the target data to obtain a compressed executable file.

The embodiment provides a compression device for an executable file, which first analyzes the function attributes and storage format attributes of each part of the executable file, and can identify the function according to the storage, compression or decompression of the data of each part of the executable file. The target data that can be compressed in the data of each part of the executable file. According to the storage format attribute of the target data, a compression strategy of the target data can be obtained. The compression strategy may include compression without compression, compression according to a new compression method with a larger original compression ratio, and compression according to a new compression method with a smaller original compression ratio. According to the compression strategy, the target data is compressed, and the storage format attribute of the target data is updated to obtain a compressed executable file. By adopting the above technical solution, the compressed executable file can occupy less storage space and achieve the technical effect of saving the storage hardware material cost required for the executable file, thereby indirectly improving the market competitiveness of the corresponding product.

Based on the foregoing embodiment, the compression policy determination module 330 may include: a compression policy determination unit.

The compression policy determining unit is configured to determine a compression policy of the target data according to the current storage format if the current storage format of the target data matches the preset storage format.

Based on the foregoing embodiment, the compression policy determining unit is configured to:

If the current storage format matches the first preset storage format corresponding to the first compression policy, the compression strategy of the target data is:

The target data is compressed according to a second compression policy corresponding to the second preset storage format, where the compression ratio corresponding to the second compression policy is greater than the compression ratio corresponding to the first compression policy.

Based on the foregoing embodiment, the compression policy determining module 330 may further be specifically configured to:

If the current storage format of the target data does not match the preset storage format, determining a compression policy of the target data according to the preset storage format.

On the basis of the foregoing embodiment, the first preset storage format is “-g”, and the second preset storage format is “-7”.

The present disclosure also provides an electronic device. The electronic device can include one or more processors and a memory coupled to the one or more processors. (memory). The memory is for storing instructions executable by the one or more processors, the instructions being executed by the one or more processors to cause the one or more processors to execute the executable file described above Compression method.

The electronic device can also include a communications interface (Communications Interface) and a bus. Among them, the processor, the communication interface, and the memory can complete communication with each other through the bus. The communication interface can be used for information transmission. The processor can invoke logic instructions in the memory to perform the deployment method of the cloud platform of the above embodiment.

In addition, the logic instructions in the above-described memory may be implemented in the form of a software functional unit and sold or used as a stand-alone product, and may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present disclosure may be embodied in the form of a software product stored in a storage medium, including a plurality of instructions for causing a computer device (which may be a personal computer, a server, or a network) The device or the like) performs all or part of the steps of the method described in various embodiments of the present disclosure. The foregoing storage medium may be a non-transitory storage medium, including: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk. A medium that can store program code, or a transitory storage medium.

Embodiments of the present disclosure provide a non-transitory computer readable storage medium, wherein the storage medium stores computer instructions configured to cause a computer to execute the compression method of the executable file described above.

The compression device of the executable file provided by the embodiment of the present invention can execute the compression method of the executable file provided by any embodiment of the present invention, and has the corresponding functional modules and corresponding beneficial effects of the execution method. For details of the technical details that are not described in detail in the above embodiments, reference may be made to the compression method of the executable file provided by any embodiment of the present invention.

Note that the above are only the preferred embodiments of the present invention and the technical principles applied thereto. Those skilled in the art will appreciate that the present invention is not limited to the specific embodiments described herein, and that various modifications, changes and substitutions may be made without departing from the scope of the invention. Therefore, the present invention has been described in detail by the above embodiments, but the present invention is not limited to the above embodiments, and other equivalent embodiments may be included without departing from the inventive concept. The scope is determined by the scope of the appended claims.

Claims

A method of compressing an executable file, comprising:

Analyzing a functional attribute and a storage format attribute of each of the plurality of data portions of the executable file;

Determining, according to the functional attribute, a compressible data portion from the plurality of data portions as the target data;

Obtaining a compression strategy of the target data according to a storage format attribute of the target data;

And compressing the target data according to the compression policy, and updating a storage format attribute of the target data to obtain a compressed executable file.
The method according to claim 1, wherein the step of obtaining a compression strategy of the target data according to a storage format attribute of the target data comprises:

And if the current storage format of the target data matches the preset storage format, determining a compression policy of the target data according to the current storage format.
The method of claim 2, wherein the step of determining a compression policy of the target data according to the current storage format comprises:

If the current storage format matches the first preset storage format corresponding to the first compression policy, the compression strategy of the target data is:

The target data is compressed according to a second compression policy corresponding to the second preset storage format, where the compression ratio corresponding to the second compression policy is greater than the compression ratio corresponding to the first compression policy.
The method according to claim 1, wherein the step of obtaining a compression strategy of the target data according to the storage format attribute of the target data further comprises:

If the current storage format of the target data does not match the preset storage format, determining a compression policy of the target data according to the preset storage format.
The method according to claim 3, wherein the first preset storage format is -g and the second preset storage format is -7.
The method of claim 1 wherein the functional attributes comprise storage attributes, compression attributes, and decompression attributes.
An executable file compression device comprising:

An attribute analysis module configured to analyze functional attributes and storage format attributes of each of the plurality of data portions of the executable file;

a target data identification module configured to identify a compressible data portion from the plurality of data portions as the target data according to the function attribute;

a compression policy determining module, configured to obtain a compression strategy of the target data according to a storage format attribute of the target data;

And a compression module, configured to compress the target data according to the compression policy, and update a storage format attribute of the target data to obtain a compressed executable file.
The apparatus of claim 7, wherein the compression policy determination module comprises:

And a compression policy determining unit, configured to determine a compression policy of the target data according to the current storage format, if a current storage format of the target data matches a preset storage format.
The apparatus of claim 8, wherein the compression policy determination unit is further configured to:

If the current storage format matches the first preset storage format corresponding to the first compression policy, the compression strategy of the target data is:

The target data is compressed according to a second compression policy corresponding to the second preset storage format, where the compression ratio corresponding to the second compression policy is greater than the compression ratio corresponding to the first compression policy.
The apparatus of claim 7, wherein the compression policy determination module is further configured to:

If the current storage format of the target data does not match the preset storage format, determining a compression policy of the target data according to the preset storage format.
The apparatus according to claim 9, wherein the first preset storage format is -g and the second preset storage format is -7.
The apparatus of claim 7, wherein the functional attributes comprise a storage attribute, a compression attribute, and a decompression attribute.
An electronic device comprising:

One or more processors; and

a memory coupled to the one or more processors;

Wherein the memory stores one or more programs, the one or more programs being configured to cause the one or more processors to execute the compression method of the executable file of claim 1.
The electronic device of claim 13 is a set top box.
A non-transitory computer readable storage medium, wherein the storage medium stores computer instructions configured to cause a computer to execute the method of compressing the executable file of claim 1.