A method, apparatus, device, and medium for extending the application of a data synchronization interface.

Abstract

This invention provides a method, apparatus, device, and readable medium for extending data synchronization interfaces. The method includes: dividing interfaces according to business types and providing a unique interface for each type of business; defining input and output parameter formats for the interfaces based on business types, and determining basic fields according to the master and sub-tables set in the ERP product; performing basic validation on the basic fields in response to the determination of the basic fields; setting extension entry points at the beginning and end of the basic validation and creating an extension method configuration table, and reading information from the extension method configuration table at the extension entry points to load the configured extensions. By using the solution of this invention, interfaces can meet the needs of different heterogeneous systems, fully validate data accuracy, improve data integration quality, reduce repetitive workload in interface development, improve interface development efficiency, and effectively avoid interface management chaos caused by developing multiple interfaces for the same business.

Description

Technical Field

[0001] This invention relates to the field of computers, and more specifically to a method, apparatus, device, and readable medium for extending the application of a data synchronization interface. Background Technology

[0002] When deploying a new ERP system, various enterprises typically need to integrate data with their existing systems. However, the original interfaces of the new ERP system often cannot meet the data integration requirements, necessitating extensive custom interface development, which is a significant workload. Furthermore, different enterprises often use different extensions for the same business form to meet their specific business needs.

[0003] Existing interface development models are all based on customized development for the heterogeneous systems being interfaced with. This results in the need to redevelop new interfaces for different heterogeneous systems, leading to poor interface reusability and high interface development and maintenance costs. Summary of the Invention

[0004] In view of this, the purpose of this invention is to provide a method, apparatus, device and readable medium for extending the application of a data synchronization interface. By using the technical solution of this invention, the interface can meet the needs of different heterogeneous systems, fully verify the accuracy of data, improve the quality of data integration, reduce the amount of repetitive work in the interface development process, improve the efficiency of interface development, and effectively avoid interface management chaos caused by developing multiple interfaces for the same business.

[0005] To achieve the above objectives, one aspect of the present invention provides a method for extending a data synchronization interface application, comprising the following steps:

[0006] The interfaces are divided according to business type, and a unique interface is provided for each type of business.

[0007] Define the input and output parameter formats for the interface based on the business type, and determine the basic fields based on the master and sub-tables set in the ERP product;

[0008] In response to the determination of the basic fields, perform basic validation on the basic fields;

[0009] Set extension pointcuts at the beginning and end of the basic verification and create an extension method configuration table. Then, read the information from the extension method configuration table at the extension pointcut to load the configured extensions.

[0010] According to an embodiment of the present invention, defining the input parameter format for the interface based on the business type includes:

[0011] Define the input parameter format of the interface for each type of business as a JSON string consisting of the basic fields and extended fields of each type of business.

[0012] According to an embodiment of the present invention, the parameter format defined for the interface based on the business type includes:

[0013] The output parameter format of the interface for each type of business is uniformly defined as a JSON string containing response code, error information, and detailed information.

[0014] According to an embodiment of the present invention, the basic fields determined based on the master and sub-tables set in the ERP product include:

[0015] Determine the required fields based on the field attributes in the master and sub-tables set in the ERP product;

[0016] The required fields are transformed based on the relationships between them and their business attributes;

[0017] The attributes of the required fields are retrieved based on the relationships between them.

[0018] According to an embodiment of the present invention, the transformation of required fields based on the association between required fields and business attributes includes:

[0019] In response to the first field being a required field and a system-specific attribute field, retrieve the second field that is related to the first field and has common business attributes;

[0020] Set the second field as a required field, and retrieve the first field by associating with the second field.

[0021] According to one embodiment of the present invention, in response to the determination of the basic fields, performing basic validation on the basic fields includes:

[0022] In response to the determination of the underlying fields, perform non-empty validation on all underlying fields;

[0023] Numerical and compliance checks are performed on all basic fields based on the logical relationships between them.

[0024] According to one embodiment of the present invention, the interfaces are divided according to business types, and a unique interface is provided for each type of business, including:

[0025] The interfaces are divided according to business type, and a unique RESTful API interface is provided for each type of business.

[0026] Another aspect of the present invention provides an apparatus for extending a data synchronization interface application, the apparatus comprising:

[0027] The partitioning module is configured to partition interfaces according to business types and provide a unique interface for each type of business.

[0028] Define the module, which is configured to define the input and output parameter formats for the interface based on the business type, and determine the basic fields based on the master and sub-tables set in the ERP product;

[0029] The validation module is configured to perform basic validation on the basic fields in response to the determination of the basic fields.

[0030] The extension module is configured to set extension point at the beginning and end of the basic verification and create an extension method configuration table, and read the information in the extension method configuration table at the extension point to load the configured extension.

[0031] According to one embodiment of the present invention, the definition module is further configured as follows:

[0032] The input parameters of the interface for each type of business are defined as a JSON string consisting of the basic fields and extended fields of each type of business;

[0033] The output parameters of the interface for each type of business are uniformly defined as JSON strings containing response codes, error messages, and detailed information.

[0034] According to one embodiment of the present invention, the definition module is further configured as follows:

[0035] Determine the required fields based on the field attributes in the master and sub-tables set in the ERP product;

[0036] The required fields are transformed based on the relationships between them and their business attributes;

[0037] The attributes of the required fields are retrieved based on the relationships between them.

[0038] According to one embodiment of the present invention, the verification module is further configured as follows:

[0039] In response to the determination of the underlying fields, perform non-empty validation on all underlying fields;

[0040] Numerical and compliance checks are performed on all basic fields based on the logical relationships between them.

[0041] Another aspect of the embodiments of the present invention also provides a computer device, the computer device comprising:

[0042] At least one processor; and

[0043] The memory stores computer instructions that can be executed by a processor, which, when executed by the processor, implement the steps of any of the methods described above.

[0044] In another aspect, embodiments of the present invention also provide a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of any of the above methods.

[0045] The present invention has the following beneficial technical effects: The method for extending the application of the data synchronization interface provided in the embodiments of the present invention divides the interface according to the business type and provides a unique interface for each type of business; defines the input parameter format and output parameter format for the interface according to the business type, and determines the basic fields according to the master and sub-tables set by the ERP product; in response to the determination of the basic fields, performs basic validation on the basic fields; sets extension entry points at the beginning and end of the basic validation and creates an extension method configuration table, and reads the information in the extension method configuration table at the extension entry point to load the configured extension technical solution. This enables the interface to meet the needs of different heterogeneous systems, fully validates the accuracy of data, improves the quality of data integration, reduces the repetitive workload in the interface development process, improves the efficiency of interface development, and effectively avoids the interface management chaos caused by the development of multiple interfaces for the same business. Attached Figure Description

[0046] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other embodiments can be obtained based on these drawings without creative effort.

[0047] Figure 1 A schematic flowchart illustrating a method for extending a data synchronization interface application according to an embodiment of the present invention;

[0048] Figure 2 A schematic diagram of an apparatus for extending a data synchronization interface according to an embodiment of the present invention;

[0049] Figure 3 This is a schematic diagram of a computer device according to an embodiment of the present invention;

[0050] Figure 4 This is a schematic diagram of a computer-readable storage medium according to an embodiment of the present invention. Detailed Implementation

[0051] To make the objectives, technical solutions, and advantages of the present invention clearer, the embodiments of the present invention will be further described in detail below with reference to specific examples and the accompanying drawings.

[0052] Based on the above objectives, a first aspect of the embodiments of the present invention provides an embodiment of a method for extending the application of a data synchronization interface. Figure 1 The diagram shown is a schematic flowchart of the method.

[0053] like Figure 1 As shown, the method may include the following steps:

[0054] S1 categorizes interfaces according to business type and provides a unique interface for each business type. A unique RESTful API interface is provided for each business type.

[0055] S2 defines the input and output parameter formats for interfaces based on business types, and determines the basic fields according to the master and sub-tables set in the ERP product. Input parameter format definition: The input parameters for each type of business interface are defined as JSON strings consisting of the basic and extended fields for that type of business. Output parameter format definition: Output parameters are uniformly set to JSON strings containing response codes, error messages, and detailed information.

[0056] S3 responds to the determination of basic fields and performs basic validation on the basic fields. Field parameters are the smallest unit of data integration. By extracting common required fields, the interface body is minimized. The extraction steps are as follows: (1) Preliminarily determine the required fields according to the field attributes in the master and sub-tables set by the ERP product. (2) Convert the required fields according to the relationship between fields and business attributes. For example, field A is a required field in the system, but it is a system-specific attribute field. Field B has a relationship with field A and its business attributes are common. Therefore, field B can be set as a required field. In business processing, field A can be obtained by associating with field B. (3) According to the relationship between the required fields, the attributes of the fields can be mutually extracted to reduce the number of required fields, so as to minimize the basic input parameters of the interface and improve the flexibility of interface expansion. After the basic fields are determined, basic validation is performed on the basic fields, that is, non-empty validation is performed on all basic fields, and numerical validation and compliance validation are performed according to the logical relationship between fields.

[0057] S4 sets extension pointcuts at the beginning and end of the basic verification and creates an extension method configuration table. The extension pointcuts then read information from this table to load the configured extensions. The extension pointcuts set extension pointcuts at the beginning and end of the basic verification and create an extension method configuration table to hold the configuration information for the extension methods. See Table 1 for details. The extension pointcuts read information from the configuration table to load the configured extensions at different times. Extension methods must use RPC communication services, and the method input and output parameters must conform to the extension specifications given by the underlying entity.

[0058] Table 1. Explanation of Extended Configuration Table

[0059]

[0060] By using the technical solution of this invention, the interface can meet the needs of different heterogeneous systems, fully verify the accuracy of data, improve the quality of data integration, reduce the amount of repetitive work in the interface development process, improve the efficiency of interface development, and effectively avoid interface management chaos caused by developing multiple interfaces for the same business.

[0061] In a preferred embodiment of the present invention, defining the input parameter format for the interface according to the business type includes:

[0062] Define the input parameter format of the interface for each type of business as a JSON string consisting of the basic fields and extended fields of each type of business.

[0063] In a preferred embodiment of the present invention, defining the parameter format for the interface according to the business type includes:

[0064] The output parameter format of the interface for each type of business is uniformly defined as a JSON string containing response code, error information, and detailed information.

[0065] In a preferred embodiment of the present invention, determining the basic fields based on the master and sub-tables set in the ERP product includes:

[0066] Determine the required fields based on the field attributes in the master and sub-tables set in the ERP product;

[0067] The required fields are transformed based on the relationships between them and their business attributes;

[0068] The attributes of the required fields are retrieved based on the relationships between them.

[0069] In a preferred embodiment of the present invention, the transformation of required fields based on the association between required fields and business attributes includes:

[0070] In response to the first field being a required field and a system-specific attribute field, retrieve the second field that is related to the first field and has common business attributes;

[0071] Set the second field as a required field, and retrieve the first field through the association between the second field and the first field. For example, field A is a required field in the system, but it is a system-specific attribute field. Field B is related to field A and its business attributes are common. In this case, field B can be set as a required field. In business processing, field A can be retrieved through field B. Based on the association between the required fields, the attributes of the fields can be retrieved from each other, thereby reducing the number of required fields, minimizing the basic input parameters of the interface, and improving the flexibility of interface expansion.

[0072] In a preferred embodiment of the present invention, in response to the determination of the basic fields, performing basic verification on the basic fields includes:

[0073] In response to the determination of the underlying fields, perform non-empty validation on all underlying fields;

[0074] Numerical and compliance checks are performed on all basic fields based on the logical relationships between them.

[0075] In a preferred embodiment of the present invention, the interfaces are divided according to business type, and a unique interface is provided for each type of business, including:

[0076] The interfaces are divided according to business type, and a unique RESTful API interface is provided for each type of business.

[0077] By using the technical solution of this invention, the interface can meet the needs of different heterogeneous systems, fully verify the accuracy of data, improve the quality of data integration, reduce the amount of repetitive work in the interface development process, improve the efficiency of interface development, and effectively avoid interface management chaos caused by developing multiple interfaces for the same business.

[0078] It should be noted that those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. The storage medium can be a magnetic disk, optical disk, read-only memory (ROM), or random access memory (RAM), etc. The embodiments of the computer program described above can achieve the same or similar effects as any of the corresponding foregoing method embodiments.

[0079] Furthermore, the method disclosed in the embodiments of the present invention can also be implemented as a computer program executed by a CPU, which may be stored in a computer-readable storage medium. When the computer program is executed by the CPU, it performs the functions defined in the method disclosed in the embodiments of the present invention.

[0080] Based on the above objectives, a second aspect of the embodiments of the present invention provides an apparatus for extending the application of a data synchronization interface, such as... Figure 2 As shown, the device 200 includes:

[0081] The partitioning module is configured to partition interfaces according to business types and provide a unique interface for each type of business.

[0082] Define the module, which is configured to define the input and output parameter formats for the interface based on the business type, and determine the basic fields based on the master and sub-tables set in the ERP product;

[0083] The validation module is configured to perform basic validation on the basic fields in response to the determination of the basic fields.

[0084] The extension module is configured to set extension point at the beginning and end of the basic verification and create an extension method configuration table, and read the information in the extension method configuration table at the extension point to load the configured extension.

[0085] In view of the above objectives, a third aspect of the present invention provides a computer device. Figure 3 The diagram shown is a schematic representation of an embodiment of the computer device provided by the present invention. Figure 3 As shown, embodiments of the present invention include the following apparatus: at least one processor 21; and a memory 22 storing computer instructions 23 executable on the processor, which, when executed by the processor, implement the following method:

[0086] The interfaces are divided according to business type, and a unique interface is provided for each type of business.

[0087] Define the input and output parameter formats for the interface based on the business type, and determine the basic fields based on the master and sub-tables set in the ERP product;

[0088] In response to the determination of the basic fields, perform basic validation on the basic fields;

[0089] Set extension pointcuts at the beginning and end of the basic verification and create an extension method configuration table. Then, read the information from the extension method configuration table at the extension pointcut to load the configured extensions.

[0090] In a preferred embodiment of the present invention, defining the input parameter format for the interface according to the business type includes:

[0091] Define the input parameter format of the interface for each type of business as a JSON string consisting of the basic fields and extended fields of each type of business.

[0092] In a preferred embodiment of the present invention, defining the parameter format for the interface according to the business type includes:

[0093] The output parameter format of the interface for each type of business is uniformly defined as a JSON string containing response code, error information, and detailed information.

[0094] In a preferred embodiment of the present invention, determining the basic fields based on the master and sub-tables set in the ERP product includes:

[0095] Determine the required fields based on the field attributes in the master and sub-tables set in the ERP product;

[0096] The required fields are transformed based on the relationships between them and their business attributes;

[0097] The attributes of the required fields are retrieved based on the relationships between them.

[0098] In a preferred embodiment of the present invention, the transformation of required fields based on the association between required fields and business attributes includes:

[0099] In response to the first field being a required field and a system-specific attribute field, retrieve the second field that is related to the first field and has common business attributes;

[0100] Set the second field as a required field, and retrieve the first field by associating with the second field.

[0101] In a preferred embodiment of the present invention, in response to the determination of the basic fields, performing basic verification on the basic fields includes:

[0102] In response to the determination of the underlying fields, perform non-empty validation on all underlying fields;

[0103] Numerical and compliance checks are performed on all basic fields based on the logical relationships between them.

[0104] In a preferred embodiment of the present invention, the interfaces are divided according to business type, and a unique interface is provided for each type of business, including:

[0105] The interfaces are divided according to business type, and a unique RESTful API interface is provided for each type of business.

[0106] In view of the above objectives, a fourth aspect of the present invention provides a computer-readable storage medium. Figure 4 The diagram shown is a schematic representation of an embodiment of the computer-readable storage medium provided by the present invention. Figure 4 As shown, computer-readable storage medium 31 stores a computer program 32 that, when executed by a processor, performs the following methods:

[0107] The interfaces are divided according to business type, and a unique interface is provided for each type of business.

[0108] Define the input and output parameter formats for the interface based on the business type, and determine the basic fields based on the master and sub-tables set in the ERP product;

[0109] In response to the determination of the basic fields, perform basic validation on the basic fields;

[0110] Set extension pointcuts at the beginning and end of the basic verification and create an extension method configuration table. Then, read the information from the extension method configuration table at the extension pointcut to load the configured extensions.

[0111] In a preferred embodiment of the present invention, defining the input parameter format for the interface according to the business type includes:

[0112] Define the input parameter format of the interface for each type of business as a JSON string consisting of the basic fields and extended fields of each type of business.

[0113] In a preferred embodiment of the present invention, defining the parameter format for the interface according to the business type includes:

[0114] The output parameter format of the interface for each type of business is uniformly defined as a JSON string containing response code, error information, and detailed information.

[0115] In a preferred embodiment of the present invention, determining the basic fields based on the master and sub-tables set in the ERP product includes:

[0116] Determine the required fields based on the field attributes in the master and sub-tables set in the ERP product;

[0117] The required fields are transformed based on the relationships between them and their business attributes;

[0118] The attributes of the required fields are retrieved based on the relationships between them.

[0119] In a preferred embodiment of the present invention, the transformation of required fields based on the association between required fields and business attributes includes:

[0120] In response to the first field being a required field and a system-specific attribute field, retrieve the second field that is related to the first field and has common business attributes;

[0121] Set the second field as a required field, and retrieve the first field by associating with the second field.

[0122] In a preferred embodiment of the present invention, in response to the determination of the basic fields, performing basic verification on the basic fields includes:

[0123] In response to the determination of the underlying fields, perform non-empty validation on all underlying fields;

[0124] Numerical and compliance checks are performed on all basic fields based on the logical relationships between them.

[0125] In a preferred embodiment of the present invention, the interfaces are divided according to business type, and a unique interface is provided for each type of business, including:

[0126] The interfaces are divided according to business type, and a unique RESTful API interface is provided for each type of business.

[0127] Furthermore, the method disclosed in the embodiments of the present invention can also be implemented as a computer program executed by a processor, which may be stored in a computer-readable storage medium. When the computer program is executed by the processor, it performs the functions defined in the method disclosed in the embodiments of the present invention.

[0128] Furthermore, the above-described method steps and system units can also be implemented using a controller and a computer-readable storage medium for storing a computer program that enables the controller to perform the functions of the above-described steps or units.

[0129] Those skilled in the art will also understand that the various exemplary logic blocks, modules, circuits, and algorithm steps described in conjunction with the disclosure herein can be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability between hardware and software, the functionality of various illustrative components, blocks, modules, circuits, and steps has been generally described. Whether this functionality is implemented as software or as hardware depends on the specific application and the design constraints imposed on the system as a whole. Those skilled in the art can implement the functionality in various ways for each specific application, but such implementation decisions should not be construed as departing from the scope of the embodiments disclosed herein.

[0130] In one or more exemplary designs, functionality may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, functionality may be stored as one or more instructions or code on or transmitted via a computer-readable medium. Computer-readable media include computer storage media and communication media, including any medium that facilitates the transfer of a computer program from one location to another. Storage media may be any available medium accessible to a general-purpose or special-purpose computer. By way of example, and not limitation, computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disc storage devices, disk storage devices or other magnetic storage devices, or any other medium that may be used to carry or store the required program code in the form of instructions or data structures and is accessible to a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection may be appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the aforementioned coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are all included in the definition of media. As used herein, disks and optical discs include compact discs (CDs), laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs, where disks typically reproduce data magnetically, while optical discs reproduce data optically using lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0131] The above are exemplary embodiments disclosed in this invention. However, it should be noted that various changes and modifications can be made without departing from the scope of the embodiments of this invention as defined by the claims. The functions, steps, and / or actions of the methods according to the disclosed embodiments described herein do not need to be performed in any particular order. Furthermore, although the elements disclosed in the embodiments of this invention may be described or claimed individually, they may be understood as multiple unless explicitly limited to a singular number.

[0132] It should be understood that, as used herein, the singular form “a” is intended to include the plural form as well, unless the context clearly supports an exception. It should also be understood that, as used herein, “and / or” refers to any and all possible combinations of one or more of the associated listed items.

[0133] The embodiment numbers disclosed in the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0134] Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware or by a program instructing related hardware. The program can be stored in a computer-readable storage medium, such as a read-only memory, a disk, or an optical disk.

[0135] Those skilled in the art should understand that the discussion of any of the above embodiments is merely exemplary and is not intended to imply that the scope of the invention (including the claims) is limited to these examples. Within the framework of the invention, technical features of the above embodiments or different embodiments can be combined, and many other variations of different aspects of the invention exist, which are not provided in the details for the sake of brevity. Therefore, any omissions, modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the invention should be included within the protection scope of the invention.

Claims

1. A method for extending a data synchronization interface application, characterized in that, Includes the following steps: The interfaces are divided according to business type, and a unique interface is provided for each type of business. Define the input and output parameter formats for the interface based on the business type, and determine the basic fields based on the master and sub-tables set in the ERP product; In response to the determination of the basic fields, perform basic validation on the basic fields; Set extension pointcuts at the beginning and end of the basic verification and create an extension method configuration table. Then, read the information in the extension method configuration table at the extension pointcut to load the configured extensions. The input parameter format for the interface is defined according to the business type, including: Define the input parameter format of the interface for each type of business as a JSON string consisting of the basic fields and extended fields of each type of business; The parameter format for the interface is defined according to the business type, including: The output parameter format of the interface for each type of business is uniformly defined as a JSON string containing response code, error information, and detailed information.

2. The method according to claim 1, characterized in that, The basic fields determined based on the master and sub-tables configured in the ERP product include: Determine the required fields based on the field attributes in the master and sub-tables set in the ERP product; The required fields are transformed based on the relationships between them and their business attributes; The attributes of the required fields are retrieved based on the relationships between them.

3. The method according to claim 2, characterized in that, The transformation of required fields based on the relationships between them and their business attributes includes: In response to the first field being a required field and a system-specific attribute field, retrieve the second field that is related to the first field and has common business attributes; Set the second field as a required field, and retrieve the first field by associating with the second field.

4. The method according to claim 1, characterized in that, In response to the determination of the underlying fields, basic validation of the underlying fields includes: In response to the determination of the underlying fields, perform non-empty validation on all underlying fields; Numerical and compliance checks are performed on all basic fields based on the logical relationships between them.

5. The method according to claim 1, characterized in that, The interfaces are divided according to business type, and a unique interface is provided for each type of business, including: The interfaces are divided according to business type, and a unique RESTful API interface is provided for each type of business.

6. A device for extending the application of a data synchronization interface, characterized in that, The device includes: A partitioning module is configured to partition interfaces according to business types and provide a unique interface for each type of business. The definition module is configured to define the input and output parameter formats for interfaces based on business types, and to determine the basic fields based on the master and sub-tables set by the ERP product. Defining the input parameter format for interfaces based on business types includes defining the input parameter format of each type of business interface as a JSON string consisting of the basic fields and extended fields of each type of business. Defining the output parameter format for interfaces based on business types includes defining the output parameter format of each type of business interface as a JSON string containing response codes, error messages, and detailed information. A verification module, configured to perform basic verification on the basic fields in response to the determination of the basic fields; An extension module is configured to set extension entry points at the beginning and end of the basic verification and create an extension method configuration table, and read information from the extension method configuration table at the extension entry point to load the configured extension.

7. A computer device, characterized in that, include: At least one processor; as well as A memory storing computer instructions executable on the processor, which, when executed by the processor, implement the steps of the method according to any one of claims 1-5.

8. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1-5.

Images