Firmware real-time editing generation method and device, electronic equipment and storage medium
By mapping the firmware data structure to memory space, real-time editing of firmware is achieved, and the problems of low development efficiency and high maintenance costs in the existing technology are solved, meeting the needs of different users.
Patent Information
- Application Number
- CN202411004979.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-25
- Publication Date
- 2024-11-15
AI Technical Summary
When the firmware function requirements change, software engineers need to have a deep understanding of the hardware principles and modify codes, resulting in low development efficiency and high maintenance costs, making it difficult to meet the needs of different users.
By mapping the firmware data structure to memory space, real-time editing is performed based on user operations, new firmware is generated, and real-time editing and modification of the firmware is realized.
It improves firmware development efficiency, can meet the needs of different users, and reduces maintenance costs and development complexity.
Smart Images

Figure CN118963727A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of firmware writing, and in particular to a firmware real-time editing and generating method, device, electronic equipment and storage medium. Background Art
[0002] Firmware is software stored inside a hardware device. It connects the hardware to the operating system and enables the device to run in a predetermined manner. With the advancement of technology, early firmware was mostly stored in ROM, while modern devices widely use rewritable storage media such as EPROM, EEPROM and Flash Memory. Today's storage media provide convenience for software engineers to change firmware functions and re-burn.
[0003] During the work process, after the firmware is released to different users, different users have different needs. Writing high-quality firmware requires in-depth understanding of the working principle of the hardware, the lower-level software architecture, and the communication protocol, which puts high demands on users to modify the firmware. When user needs change, software engineers need to modify the code, recompile, and release new firmware to users, which causes great inconvenience to developers and users.
[0004] Therefore, there is an urgent need for a firmware real-time editing and generating method, device, electronic device and storage medium to solve the above technical problems. Summary of the invention
[0005] The embodiments of the present invention provide a method, device, electronic device and storage medium for real-time editing and generating firmware, which can edit the firmware in real time to meet the needs of different users.
[0006] In a first aspect, an embodiment of the present invention provides a firmware real-time editing and generating method, comprising:
[0007] Receive user operations based on the presentation layer and send the received user operations to the data processing layer; the user operations include firmware content display, firmware editing, firmware generation and configuration of firmware data structure;
[0008] sending the received firmware data structure to the configuration file parsing layer based on the data processing layer;
[0009] Parsing the firmware data structure based on the configuration file parsing layer to obtain instantiated data information, and sending the instantiated data information to the data processing layer;
[0010] The data processing layer maps the instantiated data information to a memory space, and edits the firmware based on the user operation to generate a new firmware.
[0011] In a second aspect, an embodiment of the present invention further provides a firmware real-time editing and generating device, comprising:
[0012] A receiving unit, configured to receive user operations based on the presentation layer and send the received user operations to the data processing layer; the user operations include firmware content display, firmware editing, firmware generation, and configuration of firmware data structure;
[0013] A sending unit, configured to send the received firmware data structure to the configuration file parsing layer based on the data processing layer;
[0014] A parsing unit, configured to parse the firmware data structure based on the configuration file parsing layer to obtain instantiated data information, and send the instantiated data information to the data processing layer;
[0015] An editing unit is used for the data processing layer to map the instantiated data information to a memory space, and to edit the firmware based on the user operation to generate a new firmware.
[0016] In a third aspect, an embodiment of the present invention further provides an electronic device, including a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the method described in any embodiment of this specification is implemented.
[0017] In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium having a computer program stored thereon, which, when executed in a computer, enables the computer to execute the method described in any embodiment of this specification.
[0018] In a fifth aspect, an embodiment of the present invention further provides a computer program product, including a computer program, which implements the steps of the above-mentioned firmware real-time editing and generating method when executed by a processor.
[0019] The embodiment of the present invention provides a method for real-time editing and generating firmware. By parsing the firmware data structure, instantiated data information can be obtained. By mapping the instantiated data information to the memory space, the firmware can be edited in the memory based on the user operation, thereby generating a new firmware. It can be seen that the present application can edit and modify the firmware in real time, with high development efficiency, and can meet the needs of different users. BRIEF DESCRIPTION OF THE DRAWINGS
[0020] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.
[0021] Figure 1 It is a flow chart of a firmware real-time editing and generating method provided by an embodiment of the present invention;
[0022] Figure 2 is a hardware architecture diagram of an electronic device provided by an embodiment of the present invention;
[0023] Figure 3 It is a structural diagram of a firmware real-time editing and generating device provided by an embodiment of the present invention;
[0024] Figure 4 It is a schematic diagram of the arrangement of function points A and B in the memory in a configuration file provided by an embodiment of the present invention;
[0025] Figure 5 It is a schematic diagram of the arrangement of A and B function points in the memory in a configuration file provided by another embodiment of the present invention. DETAILED DESCRIPTION
[0026] In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, rather than all the embodiments. Based on the embodiments in the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention.
[0027] As mentioned above, after the firmware is released to different users, different users have different needs. In order to meet the needs of different users, the following two methods are currently used to modify the firmware:
[0028] One is to change the program of the lower computer to recompile and generate the firmware, and then release the firmware to the user. However, this method is a waste of manpower and material resources, with low efficiency and a long process, and is the least efficient method. The second is to modify the generated firmware by writing a hard-coded upper computer program. However, when the data structure of the firmware changes, the upper computer program needs to be linked. Although this method can meet the needs for a period of time, when one of the factors such as the subsequent lower computer architecture, data structure, or data modification method changes, the upper computer needs to generate more versions to meet the needs. This method leads to high maintenance costs, high maintenance difficulty, and easy to make mistakes.
[0029] In response to the above problems, the inventor proposes that the firmware data structure can be mapped to the memory space, and the firmware can be edited in the memory to improve the efficiency of firmware development and meet the needs of different users.
[0030] Please refer to Figure 1 The embodiment of the present invention provides a firmware real-time editing and generating method, comprising:
[0031] Step 100, receiving user operations based on the presentation layer, and sending the received user operations to the data processing layer; the user operations include firmware content display, firmware editing, firmware generation and configuration of firmware data structure;
[0032] Step 102, sending the received firmware data structure to the configuration file parsing layer based on the data processing layer;
[0033] Step 104, parsing the firmware data structure based on the configuration file parsing layer to obtain instantiated data information, and sending the instantiated data information to the data processing layer;
[0034] Step 106: The data processing layer maps the instantiated data information to the memory space, and edits the firmware based on the user operation to generate a new firmware.
[0035] In this embodiment, by parsing the firmware data structure, instantiated data information can be obtained. By mapping the instantiated data information to the memory space, the firmware can be edited in the memory based on the user operation, thereby generating a new firmware. It can be seen that the present application can edit and modify the firmware in real time, with high development efficiency, and can meet the needs of different users.
[0036] Described below Figure 1 How the various steps are performed.
[0037] First, for step 100, user operations are received based on the presentation layer, and the received user operations are sent to the data processing layer; the user operations include firmware content display, firmware editing, firmware generation, and configuration of firmware data structure.
[0038] The following are the descriptions of the above four user operations:
[0039] (I) Display operations for firmware content:
[0040] The firmware content display includes instructions on data format, display method, whether to display, and function modification methods. Among them:
[0041] 1) The data format supports variables and arrays of u8, u16, and u32 types, and variables of u8, u16, and u32 bit segment types.
[0042] 2) Data presentation method:
[0043] When the data length is less than or equal to 8 bits, the data content is partially read and displayed;
[0044] When the data length is an integer multiple of 8 bits, the data content is read and displayed as complete bytes;
[0045] When the data length is not an integer multiple of 8 bits and is greater than 8 bits, the data content is read and displayed in full + in part.
[0046] 3) Whether the firmware content is displayed and the notes for display:
[0047] If the firmware function supports modification, a prompt will be displayed to show how to modify the function in the firmware and how to fill in the hexadecimal functional data in the firmware.
[0048] (II) Firmware editing operations:
[0049] The firmware editing modes include: bit modification, single byte modification, multi-byte overall modification, big-endian data format selection, little-endian data format selection and overall function coverage. Users can select the appropriate firmware editing method according to the data length and characteristics of the functions in the firmware.
[0050] Each editing method is described in detail below.
[0051] 1) Bit modification and single byte modification require the user to manually enter the value;
[0052] 2) Multiple bytes can be modified by manually modifying a single byte to complete the modification of multiple bytes or by importing bin file data to modify multiple bytes;
[0053] 3) Select the data input format to be big endian or little endian;
[0054] 4) Overall functional coverage: The configuration file will mark which functions can be modified. The functional data of the entire software can be entered into the module. The module will automatically intercept and cover the functional data that can be modified to achieve the purpose of modifying all functions.
[0055] (III) Firmware generation operation:
[0056] When the presentation layer receives the firmware generation operation, it sends the operation to the data processing layer. At this time, the data processing layer will allocate space of the firmware size in the memory to store the firmware data, and change the memory data in real time according to the instantiated data information sent by the configuration file parsing layer. After the user changes are completed, the CRC32 method / algorithm with specific processing is used for calculation, and the memory data can be output into a bin file for functional testing.
[0057] (IV) Operations for configuring firmware data structures:
[0058] When performing firmware data structure configuration operations, the overall data structure alignment principle must be followed. The overall data structure alignment principle includes the user-defined alignment principle and the sizeof alignment principle of the C language standard. Among them, the user-defined alignment principle includes:
[0059] A. When defining a structure, there can only be one level of nesting;
[0060] B. Bit segments cannot be stored across bytes. For example, the bit segment of type int uses the values 9 15 16. Among them, 9 and 15 are in a four-byte int, and 16 is a separate four-byte.
[0061] C. Bit segments cannot be stored across types;
[0062] D. When the basic data type of the data changes, the memory location pointer moves backward, and the unused space is discarded and byte aligned;
[0063] E. The first address of the structure variable can be divided by the size of its widest basic type member;
[0064] F. The offset of each member of the structure relative to the first address of the structure is an integer multiple of the member size;
[0065] H. The total size of the structure is an integer multiple of the size of the widest basic type member of the structure;
[0066] I. The memory data between structures is arranged sequentially and does not need to be aligned again.
[0067] In this step, changing different configuration files can change the data arrangement or position of the firmware function points in the memory in real time. Here, the standard C language alignment principle is not repeated.
[0068] Regarding step 102 and step 104:
[0069] After receiving the firmware data structure information sent by the data processing layer, the configuration file parsing layer will instantiate and parse the relevant configuration file information. The instantiated information is judged to see whether it completely matches the size of the space opened in the memory, mainly to see whether the size of the space opened in the memory is sufficient for the instantiated information. The instantiated information is imported into the overall data structure alignment principle algorithm for parsing and processing, and the number of bytes used by each structure is obtained. Then, the arrangement of each functional point in the firmware in the memory is obtained, and the data is passed to the data processing module in the form of multiple single bytes for use.
[0070] In some implementations, the firmware data structure is parsed based on the configuration file parsing layer to obtain instantiated data information, including:
[0071] S1, read the configuration file;
[0072] S2, judging whether the displayed function point data in the memory space opened by the data processing layer completely matches the function point data to be displayed in the configuration file; if so, executing S3; if not, prompting the data not displayed, and performing data parsing according to the information in the configuration file, and executing S3;
[0073] S3, parses the firmware data structure based on the overall data structure alignment principle to obtain the number of bytes used by each structure and the location information of each function point in the configuration file in the memory space.
[0074] Finally, for step 106, the data processing layer maps the instantiated data information to the memory space, and edits the firmware based on the user operation to generate a new firmware, including:
[0075] Open up a firmware-sized memory space in the memory;
[0076] Map the number of bytes used by each structure and the location information of each function point in the configuration file in the memory space to the memory space;
[0077] Edit memory data based on the mapping relationship between user operations and memory space, and output the edited data to the buffer;
[0078] The data in the buffer is processed based on the CRC64 algorithm to obtain a new firmware.
[0079] In this step, the data processing layer first obtains the data structure of the firmware according to the configuration file parsing layer, passes the data structure to the data processing layer in bytes, and maps the data structure information to the memory opened by the data processing layer to form a correspondence. After receiving the user operation sent by the presentation layer, the data processing layer will modify the firmware data in the memory. After the modification is completed, the modified data will be provided to the presentation layer for display and generation, etc., to complete the corresponding operation.
[0080] When the data processing layer is editing data, it changes the memory data according to the data, length and location in the memory of the function point fed back by the configuration file parsing layer. Although the presentation layer supports multiple means (bit modification, single byte, multiple byte modification, etc.) to edit data information, the data received by the data processing layer enters the module in bytes to modify the memory data, and does not process information in other formats.
[0081] When the data processing layer generates firmware, it copies the data in the memory to the buffer, processes the data in the buffer using a specific CRC64 method, and outputs the processed data in the form of a bin for the user to use.
[0082] like Figure 4 and Figure 5 The following is an example of selecting different configuration files in the firmware function memory:
[0083] Select the configuration file A.xml. The data in the memory where functions A and B are located is arranged as follows Figure 4 shown.
[0084] Change the A.xml configuration file to the B.xml configuration file. The data in the memory where functions A and B are located is arranged as follows Figure 5 shown.
[0085] As can be seen from the figure, the arrangement of the firmware's functional points in memory can be easily changed by changing the configuration file, thereby changing the memory data to regenerate the firmware.
[0086] like Figure 2 , Figure 3 As shown, an embodiment of the present invention provides a firmware real-time editing and generating device. The device embodiment can be implemented by software, or by hardware or a combination of software and hardware. From the hardware level, Figure 2 As shown, it is a hardware architecture diagram of an electronic device where a firmware real-time editing and generating device provided by an embodiment of the present invention is located, except Figure 2 In addition to the processor, memory, network interface, and non-volatile memory shown, the electronic device in the embodiment may also include other hardware, such as a forwarding chip responsible for processing messages, etc. Taking software implementation as an example, Figure 3 As shown, as a device in a logical sense, the CPU of the electronic device in which it is located reads the corresponding computer program in the non-volatile memory into the internal memory and runs it. This embodiment provides a firmware real-time editing and generating device, including:
[0087] The receiving unit 300 is used to receive user operations based on the presentation layer and send the received user operations to the data processing layer; the user operations include firmware content display, firmware editing, firmware generation and configuration of firmware data structure;
[0088] The sending unit 302 is used to send the received firmware data structure to the configuration file parsing layer based on the data processing layer;
[0089] The parsing unit 304 is used to parse the firmware data structure based on the configuration file parsing layer to obtain instantiated data information, and send the instantiated data information to the data processing layer;
[0090] The editing unit 306 is used for the data processing layer to map the instantiated data information to the memory space, and edit the firmware based on the user operation to generate a new firmware.
[0091] In some implementations, the firmware content display includes instructions on data format, display method, whether to display, and function modification method.
[0092] In some implementations, the editing methods of the firmware editing include: bit modification, single byte modification, overall modification of multiple bytes, big-endian data format selection, little-endian data format selection, and overall function coverage.
[0093] In some implementations, when executing the configuration firmware data structure, the overall data structure alignment principle must be followed, and the overall data structure alignment principle includes the user-defined alignment principle and the sizeof alignment principle of the C language standard; wherein the user-defined alignment principle includes:
[0094] A. When defining a structure, there can only be one level of nesting;
[0095] B. Bit segments cannot be stored across bytes;
[0096] C. Bit segments cannot be stored across types;
[0097] D. When the basic data type of the data changes, the memory location pointer moves backward, and the unused space is discarded and byte aligned;
[0098] E. The first address of the structure variable can be divided by the size of its widest basic type member;
[0099] F. The offset of each member of the structure relative to the first address of the structure is an integer multiple of the member size;
[0100] H. The total size of the structure is an integer multiple of the size of the widest basic type member of the structure;
[0101] I. The memory data between structures is arranged sequentially and does not need to be aligned again.
[0102] In some implementations, the parsing unit 304 is configured to perform the following operations:
[0103] S1, read the configuration file;
[0104] S2, judging whether the displayed function point data in the memory space opened by the data processing layer completely matches the function point data to be displayed in the configuration file; if so, executing S3; if not, prompting the data not displayed, and performing data parsing according to the information in the configuration file, and executing S3;
[0105] S3, parses the firmware data structure based on the overall data structure alignment principle to obtain the number of bytes used by each structure and the location information of each function point in the configuration file in the memory space.
[0106] In some implementations, the editing unit 306 is configured to perform the following operations:
[0107] Open up a firmware-sized memory space in the memory;
[0108] Map the number of bytes used by each structure and the location information of each function point in the configuration file in the memory space to the memory space;
[0109] Edit memory data based on the mapping relationship between user operations and memory space, and output the edited data to the buffer;
[0110] The data in the buffer is processed based on the CRC64 algorithm to obtain a new firmware.
[0111] It is to be understood that the structure illustrated in the embodiment of the present invention does not constitute a specific limitation on a real-time firmware editing and generating device. In other embodiments of the present invention, a real-time firmware editing and generating device may include more or fewer components than shown in the figure, or combine some components, or split some components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.
[0112] The information interaction, execution process and other contents between the modules in the above-mentioned device are based on the same concept as the embodiment of the method of the present invention. For specific contents, please refer to the description in the embodiment of the method of the present invention, and no further description is given here.
[0113] An embodiment of the present invention further provides an electronic device, including a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, a firmware real-time editing and generating method in any embodiment of the present invention is implemented.
[0114] An embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the processor executes a firmware real-time editing and generating method in any embodiment of the present invention.
[0115] An embodiment of the present application also provides a computer program product, which includes a computer program. A processor of a computer device reads the computer program from a computer-readable storage medium, and the processor executes the computer program, so that the computer device executes any of the firmware real-time editing and generation methods in the above embodiments.
[0116] Specifically, a system or device equipped with a storage medium can be provided, on which software program code that implements the functions of any of the above-mentioned embodiments is stored, and a computer (or CPU or MPU) of the system or device can be enabled to read and execute the program code stored in the storage medium.
[0117] In this case, the program code itself read from the storage medium can realize the function of any one of the above-mentioned embodiments, and thus the program code and the storage medium storing the program code constitute a part of the present invention.
[0118] The storage medium embodiments for providing the program code include a floppy disk, a hard disk, a magneto-optical disk, an optical disk (such as CD-ROM, CD-R, CD-RW, DVD-ROM, DVD-RAM, DVD-RW, DVD+RW), a magnetic tape, a non-volatile memory card, and a ROM. Alternatively, the program code can be downloaded from a server computer by a communication network.
[0119] In addition, it should be clear that the functions of any of the above embodiments can be implemented not only by executing the program code read by the computer, but also by enabling an operating system operating on the computer to complete part or all of the actual operations based on instructions from the program code.
[0120] In addition, it can be understood that the program code read from the storage medium is written to a memory provided in an expansion board inserted into the computer or to a memory provided in an expansion module connected to the computer, and then based on the instructions of the program code, a CPU installed on the expansion board or expansion module is enabled to perform part or all of the actual operations, thereby realizing the functions of any of the above-mentioned embodiments.
[0121] 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 such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the statement "comprise a ..." do not exclude the presence of other identical factors in the process, method, article or device including the elements.
[0122] A person of ordinary skill in the art can understand that all or part of the steps of implementing the above method embodiments can be completed by hardware related to program instructions, and the aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it executes the steps of the above method embodiments; and the aforementioned storage medium includes: ROM, RAM, magnetic disk or optical disk, etc., various media that can store program codes.
[0123] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present invention.
Claims
1. A method for real-time editing and generating firmware, characterized in that: include: Receive user operations based on the presentation layer, and send the received user operations to the data processing layer; The user operations include firmware content display, firmware editing, firmware generation and configuration of firmware data structure; sending the received firmware data structure to the configuration file parsing layer based on the data processing layer; Parsing the firmware data structure based on the configuration file parsing layer to obtain instantiated data information, and sending the instantiated data information to the data processing layer; The data processing layer maps the instantiated data information to a memory space, and edits the firmware based on the user operation to generate a new firmware.
2. The method according to claim 1, characterized in that: The firmware content display includes instructions on data format, display method, whether to display, and function modification method.
3. The method according to claim 1, characterized in that The firmware editing modes include: bit modification, single byte modification, overall modification of multiple bytes, big-endian data format selection, little-endian data format selection and overall function coverage.
4. The method according to claim 1, characterized in that: When executing the configuration firmware data structure, the overall data structure alignment principle must be followed, and the overall data structure alignment principle includes the user-defined alignment principle and the sizeof alignment principle of the C language standard; wherein the user-defined alignment principle includes: A. When defining a structure, there can only be one level of nesting; B. Bit segments cannot be stored across bytes; C. Bit segments cannot be stored across types; D. When the basic data type of the data changes, the memory location pointer moves backward, and the unused space is discarded and byte aligned; E. The first address of the structure variable can be divided by the size of its widest basic type member; F. The offset of each member of the structure relative to the first address of the structure is an integer multiple of the member size; H. The total size of the structure is an integer multiple of the size of the widest basic type member of the structure; I. The memory data between structures is arranged sequentially and does not need to be aligned again.
5. The method according to claim 4, characterized in that The step of parsing the firmware data structure based on the configuration file parsing layer to obtain instantiated data information includes: S1, read the configuration file; S2, judging whether the displayed function point data in the memory space opened by the data processing layer completely matches the function point data to be displayed in the configuration file; if so, executing S3; if not, prompting the data not displayed, and performing data parsing based on the information in the configuration file, and executing S3; S3, parsing the firmware data structure based on the overall data structure alignment principle to obtain the number of bytes used by each structure and the location information of each function point in the configuration file in the memory space.
6. The method according to claim 5, characterized in that The data processing layer maps the instantiated data information to the memory space, and edits the firmware based on the user operation to generate a new firmware, including: Open up a firmware-sized memory space in the memory; Mapping the number of bytes used by each structure and the location information of each function point in the configuration file in the memory space to the memory space; Editing memory data based on the mapping relationship between the user operation and the memory space, and outputting the edited data to a buffer; The data in the buffer is processed based on the CRC64 algorithm to obtain a new firmware.
7. A firmware real-time editing and generating device, characterized in that: include: A receiving unit, used for receiving user operations based on the presentation layer, and sending the received user operations to the data processing layer; The user operations include firmware content display, firmware editing, firmware generation and configuration of firmware data structure; A sending unit, configured to send the received firmware data structure to the configuration file parsing layer based on the data processing layer; A parsing unit, configured to parse the firmware data structure based on the configuration file parsing layer to obtain instantiated data information, and send the instantiated data information to the data processing layer; An editing unit is used for the data processing layer to map the instantiated data information to a memory space, and to edit the firmware based on the user operation to generate a new firmware.
8. An electronic device comprising a memory and a processor, wherein a computer program is stored in the memory, wherein: When the processor executes the computer program, the method according to any one of claims 1 to 6 is implemented.
9. A storage medium having a computer program stored thereon, characterized in that: When the computer program is executed in a computer, the computer is caused to execute the method according to any one of claims 1 to 6.
10. A computer program product, characterized in that The method comprises a computer program, wherein when the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.
