A method and system for localizing a document and a storage medium

Abstract

The application discloses a localization method and system of a bill and a storage medium, and is used for the technical field of bill processing. The method comprises the following steps: obtaining a preset bill and a localized bill template, wherein the localized bill template comprises a preset bill area and a localized metadata area; configuring localized bill metadata in the localized metadata area according to a preset local registration rule, and filling bill metadata in the preset bill except the localized bill metadata into the preset bill area according to a preset adaptation rule, so as to generate a localized bill; wherein the localized bill metadata comprises metadata of the possibility of changes of the preset bill after localization. When another preset bill needs to be localized, the localized bill metadata configured in the localized metadata area can be directly used, and the other preset bill does not need to be repeatedly developed and adapted; and the localized bill metadata can be reused between different bills.

Description

Technical Field

[0001] This application relates to the field of document processing technology, and in particular to a document localization method, localization system, and storage medium. Background Technology

[0002] Currently, different countries or regions have different localization product requirements, and documents from different countries or regions may have differences such as field layout or field validation rules.

[0003] Due to the differences in document content during document localization, existing methods use separate code to adapt the same document to different countries or regions. The new approach involves developing localization for each document, registering a plugin for each document, and hard-coding the business logic into the plugin.

[0004] However, the existing code-based adaptation process requires rewriting code on each document, resulting in high development costs. Furthermore, the business logic configured between different documents differs, making it difficult to reuse the business logic in other documents, thus leading to poor reusability. Summary of the Invention

[0005] This application provides a document localization method, localization system, and storage medium, which eliminates the need for repeated development and adaptation of localized document metadata, and allows for the reuse of localized document metadata between different documents.

[0006] The first aspect of this application provides a method for localizing documents, including:

[0007] Obtain preset documents and localized document templates, wherein the localized document templates include: a preset document area and a localized metadata area;

[0008] Configure localized document metadata in the localized metadata area according to preset local registration rules, and fill the document metadata other than the localized document metadata in the preset document into the preset document area according to preset adaptation rules to generate a localized document; wherein, the localized document metadata includes metadata that may change after the preset document is localized.

[0009] A second aspect of this application provides a document localization system, comprising:

[0010] The acquisition unit is used to acquire preset documents and localized document templates. The localized document templates include: a preset document area and a localized metadata area.

[0011] The generation unit is configured to configure localized document metadata in the localized metadata area according to preset local registration rules, and fill the document metadata other than the localized metadata in the preset document into the preset document area according to preset adaptation rules to generate a localized document; wherein, the localized document metadata includes metadata that may change after the preset document is localized.

[0012] A third aspect of this application provides an electronic device, including:

[0013] Central processing unit, memory, and input / output interfaces;

[0014] The memory is either a short-term storage memory or a persistent storage memory;

[0015] The central processing unit is configured to communicate with the memory and execute instructions in the memory to perform the method described in the first aspect of the embodiments of this application or any specific implementation thereof.

[0016] A fourth aspect of this application provides a computer-readable storage medium including instructions that, when executed on a computer, cause the computer to perform the method described in the first aspect of this application or any specific implementation thereof.

[0017] The fifth aspect of this application provides a computer program product comprising instructions or a computer program, which, when run on a computer, causes the computer to perform the method described in the first aspect of this application or any specific implementation thereof.

[0018] As can be seen from the above technical solutions, the embodiments of this application have the following advantages:

[0019] The method in this application includes: obtaining a preset document and a localized document template. The localized document template includes a preset document area and a localized metadata area. Localized document metadata is configured in the localized metadata area according to preset local registration rules, and the document metadata (excluding the localized document metadata) from the preset document is filled into the preset document area according to preset adaptation rules to generate a localized document. The localized document metadata includes metadata that may change after localization. During the localization process of the preset document, the localized document metadata and the document metadata are configured in different document template areas. When another preset document needs to be localized, the localized document metadata configured in the localized metadata area can be used directly, eliminating the need for repeated development and adaptation of the localized document metadata for the other preset document. Furthermore, the localized document metadata can be reused between different documents. Attached Figure Description

[0020] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments recorded in this application. For those skilled in the art, other drawings can be obtained based on these drawings.

[0021] Figure 1 This is a flowchart illustrating the localization process of a document as disclosed in an embodiment of this application.

[0022] Figure 2 This is a localization flowchart for another document disclosed in an embodiment of this application;

[0023] Figure 3 This is a localization diagram of a standard document disclosed in an embodiment of this application;

[0024] Figure 4 This is a schematic diagram of a document localization device disclosed in an embodiment of this application;

[0025] Figure 5 This is a schematic diagram of a localization device for another document disclosed in an embodiment of this application. Detailed Implementation

[0026] To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings. The described embodiments should not be regarded as limitations on this application. All other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0027] The terms “first,” “second,” “third,” “fourth,” etc. (if present) in the specification, claims, and drawings of this application are used to distinguish similar objects and are not necessarily used to describe a particular order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “having,” and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0028] In the following description, expressions such as "one specific implementation" or "one specific example" are used, which describe a subset of all possible embodiments. However, it is understood that "one specific implementation" or "one specific example" can be the same subset or a different subset of all possible embodiments, and can be combined with each other without conflict. In the following description, the term "plural" means at least two. The statement that a certain value reaches a threshold (if it exists) as used in this application may, in some specific examples, include cases where the former is greater than the latter.

[0029] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of this application only and is not intended to limit this application.

[0030] Existing code-based adaptation methods require rewriting code for each document, resulting in high development costs and discrepancies in business logic configuration between different documents. Therefore, this application provides a document localization method that eliminates the need for repetitive development and adaptation of localized document metadata, and allows for the reuse of localized document metadata across different documents. Figure 1 As shown.

[0031] The method described in this application will be further explained in detail below.

[0032] Please see Figure 1 The first aspect of this application provides a specific embodiment of a document localization method, including steps 101 to 103, which includes:

[0033] 101. Obtain preset documents and localized document templates.

[0034] In this embodiment, a preset document and a localized document template can be obtained. It is understood that the localized document template is a document template adapted to the local software, while the preset document is generally a standard document from a different country or region relative to the local software. The localized document template can be used to convert the preset document into a localized document. Specifically, the localized document template includes a preset document area and a localized metadata area; wherein the preset document area and the localized metadata area are configured with different document content, and the preset document area and the localized metadata area are stored in different locations within the localized document template. Metadata is data that describes data; it is descriptive information about data and information resources.

[0035] 102. Configure localized document metadata in the localized metadata area of ​​the localized document template according to the preset localized registration rules.

[0036] After obtaining the localized document template, you can configure localized document metadata in the localized document metadata area of ​​the template according to preset local registration rules. This localized document metadata includes metadata that may change after localization. It is understood that the preset document may have different metadata after localization, such as differences in field layout or field visibility. The localized document metadata includes the metadata that differs after localization.

[0037] Specifically, configuring localized document metadata in the localized metadata area of ​​the localized document template according to preset local registration rules includes: during the process of loading a preset document into a localized document, the localization framework layer can first configure localized document metadata in the localized metadata area of ​​the localized document template based on the previous localized document or its own stored documents; when the document is displayed on the page, the localized document metadata in the localized document template is then modified. It can be understood that when modifying localized document metadata during configuration, the content within the localized document metadata is generally modified. For example, if the localized document metadata is a document type, the modification will change document type A to document type B.

[0038] 103. Fill the preset document metadata (excluding localized document metadata) into the preset document area of ​​the localized document template.

[0039] After obtaining the localized document template, the document metadata (excluding the localized document metadata) from the preset document can be filled into the preset document area of ​​the localized document template. Specifically, the document metadata (excluding the localized document metadata) from the preset document can be adapted to the preset document area of ​​the localized document template, that is, the document metadata is filled into the corresponding field positions in the preset document area according to the business function logic. It can be understood that this localized document metadata is generally additional content compared to the preset document, as well as content that has changed to adapt to the preset document or due to localization needs. In other words, the document metadata (excluding the localized document metadata) from the preset document is generally content that has not changed during the adaptation of the preset document or during the localization of the preset document. The unchanged content from the preset document is then filled into the preset document area of ​​the localized document template.

[0040] It is understandable that the order of execution of steps 102 and 103 is not limited; only after steps 102 and 103 are executed can the preset document be localized and a localized document be generated.

[0041] As can be seen, the method of this application includes: obtaining a preset document and a localized document template, wherein the localized document template includes a preset document area and a localized metadata area; configuring localized document metadata in the localized metadata area according to preset local registration rules, and filling the document metadata (excluding localized document metadata) in the preset document into the preset document area according to preset adaptation rules to generate a localized document; wherein, the localized document metadata includes metadata that may change after the preset document is localized. During the localization process of the preset document, the localized document metadata and the document metadata are configured in different document template areas respectively. When another preset document needs to be localized, the localized document metadata configured in the localized metadata area can be used directly, and there is no need to repeatedly develop adaptation for the localized document metadata of the other preset document; and the localized document metadata can be reused between different documents.

[0042] In this embodiment, after configuring the localized document metadata in the localized document template, the localized document metadata in the localized document template can be reused. That is, when using the localized document template to localize multiple preset documents (such as documents from multiple different countries), the localized document metadata in the localized document template does not need to be changed. Only the unchanged content in the preset documents needs to be filled into the preset document area of ​​the localized document template, ensuring that the localized document is automatically compatible when the preset documents are modified. The localized document metadata configured in the localized document template can also be dynamically modified as needed when the page is running. It can be seen that the method of this embodiment can be understood as a general method for dynamically modifying metadata based on localization configuration. After configuring the localization function in the document, the general function does not require additional code processing. The general localization capability between different documents can be reused and can be taken effect through configuration. The localization function is abstracted, and the required runtime metadata information is dynamically changed when the page is opened based on the localization information configured in the document.

[0043] Please refer to the following: Figures 2 to 3 Based on the examples above, some specific possible implementation examples will be provided below. In practical applications, the implementation details of these examples can be combined as needed according to the corresponding functional principles and application logic:

[0044] 201. Obtain preset documents and localized document templates obtained based on preset document templates.

[0045] In this embodiment of the application, a preset document and a localized document template obtained based on the preset document template can be obtained; wherein, obtaining the preset document is similar to step 201 above, and will not be described in detail here.

[0046] After obtaining the preset document, you can configure whether the preset document is localized to obtain the corresponding configuration result. For example... Figure 3 As shown, after opening a preset document, it can be localized in the localization framework control layer. This localization can be started by configuring the document to enable localization. The localization configuration controls the document loading, that is, it controls whether to load a standard document or a localized document. If the configuration result is to enable localization, the localized document template is obtained and the localized document is loaded, and the preset document automatically adapts to the preset document area in the localized document template. If the configuration result is to disable localization, the preset document is loaded, that is, the preset document is not processed and is loaded directly.

[0047] Understandably, existing localized documents lack independence, with localization functionality coupled to the original document functionality. Customers who don't require localization for the same document may find it difficult to use independently. In this application, however, the localized document functionality is independent of the original document functionality. Enabling localization is based on configuration needs, and customers who don't require it are unaffected. By configuring whether localization is enabled for preset documents, the functionality of preset documents and localization is ensured to be independently isolated. Loading a preset document does not include localization functionality. Specifically, if a preset document has already generated a localized document, only a portion of customers may need localization capabilities. Configuration controls allow these customers to use the localized document, while the majority of customers who don't need localization capabilities can still use the preset document. Loading a preset document and loading a localized document are independent processes.

[0048] The localized document template obtained from the preset document template can be specifically as follows: The preset document template, which includes a preset document area, is retrieved; preset fields are expanded outside the preset document area using a split table method, and these preset fields are used as the localized metadata area to generate the localized document template. In other words, the localized document template can be expanded from the preset document template corresponding to the preset document. The expanded fields are stored using a split table method, meaning the localized document metadata is stored differentially. The localized document metadata and the unchanged document metadata in the preset document are stored in different areas.

[0049] 202. Modify the localized document metadata based on the location information of the preset document and the pre-configured location information.

[0050] This application embodiment can modify the localized document metadata corresponding to the pre-configured location information based on the location information of the preset document. It is understood that when loading a localized document, the localized document metadata in the localized metadata area is generally pre-configured. The localized document metadata in the localized metadata area includes the document's location information. When loading a localized document using a localized document template, the location information is pre-configured in the localized metadata area, and the corresponding localized document metadata is configured according to the pre-configured location information. For example, based on the pre-configured country information, document types and document plugins are configured. The localized document metadata corresponding to different location information can be defined by the user. This location information can include the document's country information or region information; specific details are not limited here, and hidden fields can be used to store country or region context information. When a preset document with localization enabled is running, it needs to know the location information of the preset document to be opened (whether it's a UK document or a US document) in order to achieve localized loading. Dynamic switching is required when the location information changes.

[0051] Specifically, a preset localization plugin can be used to listen to the location information of a preset document, that is, to listen to the data binding event. If the location information of the preset document is inconsistent with the location information pre-configured in the localization metadata area, the localization metadata corresponding to the pre-configured location information will be modified based on the location information of the preset document.

[0052] It is understandable that the order of execution of steps 202 and 203 is not limited, and step 202 is optional.

[0053] 203. Modify the pre-configured localized document metadata according to localized business needs.

[0054] Specifically, it can retrieve and display pre-configured localized document metadata from the localized metadata area; that is, it can open a localized document pre-loaded using a localized document template on the front end, and run the document plugin command on the back end to obtain the pre-configured localized document metadata from the localized metadata area. Users can modify the pre-configured localized document metadata according to localized business needs, that is, dynamically change runtime metadata in the localization framework control layer, generate runtime entity metadata and page metadata in the dynamic domain model, and return the changed runtime metadata to the back end, and then send it back to the front end for display.

[0055] Specifically, pre-configured localized document metadata can include: document type, localization plugin, or field alternative values, without further limitations here. That is, during the process of loading localized documents using a localized document template on a preset document, localization plugins can be registered by default, and global control plugins can be registered to implement the basic capabilities of localized documents; document types (hidden) or field alternative values ​​can be pre-configured, etc.

[0056] After loading localized documents, localized configuration information can be read, i.e., pre-configured localized document metadata. This localized configuration information can include: document code, country code, plugins, and document type, etc. Each configuration information has multiple detailed contents, such as configuration information ID, field code, field alternative values, and field query identifiers. By modifying the document type, localized plugins, or field alternative values ​​according to localized business needs, localized document metadata can be dynamically modified when the document is displayed on the page. This includes dynamically binding document types to control layout and field visibility / requirement; dynamically registering plugins for custom content such as controlling field validation rules; and dynamically adding field alternative values ​​that are automatically filled based on localized content.

[0057] 204. The preset document loading plugin performs compatibility processing on the document metadata of the preset documents.

[0058] In this embodiment, the document metadata of the preset document is processed for compatibility according to the preset document loading plugin. Specifically, the document metadata is processed to conform to the preset document area according to the preset document loading plugin. Based on the processing result, the content of the document metadata is filled into the corresponding fields in the preset document area. That is, the content of the preset document area in the localized document template is inherited from the preset document, and the content of the preset document that has not changed after localization is filled into the corresponding position in the preset document area using the corresponding logical function.

[0059] It is understandable that the order in which steps 203 and 204 are executed is not limited; the final localized document is obtained only after both steps 203 and 204 have been executed.

[0060] As can be seen, in this embodiment, based on the differences between the localized document content and the preset document content after localization, the unchanged content in the preset document is separated from the localized document metadata. The localized document carries the localized document metadata as a general localization function. Configuration rules are designed to load the document, and the localized document metadata is modified to meet different localization business needs. Localization function-related fields and plugins are configured for documents requiring different localization functions. This embodiment has several advantages: real-time performance—changes to the configuration of general localization functions take effect immediately without redeployment; flexibility—controlling the visibility, mandatory fields, layout, etc., of different countries or regions based on the monitored document location information, providing more flexible control; reusability—high degree of shared localized document metadata, eliminating the need for repeated development; independence—the content that changes after localization in the preset document is relatively isolated from the localized document metadata; compatibility—modification of content that changes after localization in the preset document is compatible with localization rules, automatically adapting to the localized content.

[0061] Please see Figure 4 A second aspect of this application provides a specific example of a document localization system, the system comprising:

[0062] The acquisition unit 401 is used to acquire a preset document and a localized document template, wherein the localized document template includes: a preset document area and a localized metadata area;

[0063] The generation unit 402 is used to configure localized document metadata in the localized metadata area according to preset local registration rules, and to fill the document metadata other than the localized document metadata in the preset document into the preset document area according to preset adaptation rules to generate a localized document; wherein, the localized document metadata includes metadata that may change after the preset document is localized.

[0064] Optionally, the acquisition unit 401 is specifically used to acquire a preset document template, wherein the preset document template includes the preset document area;

[0065] The preset document template is expanded with preset fields outside the preset document area by splitting the table, and the preset fields are used as the localized metadata area to generate the localized document template.

[0066] Optionally, the localized document metadata may further include: the location information of the preset document;

[0067] The generation unit 402 is specifically used to use a preset localization plugin to listen to the location information of the preset document;

[0068] If the location information of the preset document is inconsistent with the location information pre-configured in the localized metadata area, then the localized document metadata corresponding to the pre-configured location information is modified based on the location information of the preset document.

[0069] Optionally, the generation unit 402 is specifically used to obtain the pre-configured localized document metadata in the localized metadata area and display the pre-configured localized document metadata;

[0070] Modify the pre-configured localized document metadata according to localized business needs.

[0071] Optionally, the pre-configured localized document metadata includes: document type, localization plugin, or field candidate value; the generation unit 402 is specifically used to modify the document type, the localization plugin, or the field candidate value according to localized business requirements.

[0072] Optionally, the generation unit 402 is further configured to perform compatibility processing on the document metadata according to the preset document loading plugin to conform to the preset document area;

[0073] Based on the processing result, the content of the document metadata is filled into the corresponding field in the preset document area.

[0074] Optionally, the acquisition unit 401 is further configured to configure whether the preset document is localized and obtain the configuration result;

[0075] If the configuration result is to enable localization, then obtain the localized document template;

[0076] If the configuration result is that localization is not enabled, then the preset document is loaded.

[0077] Please see Figure 5 The electronic device 500 of this application embodiment may include one or more central processing units (CPUs) 501 and memory 502, wherein the memory 502 stores one or more applications or data.

[0078] The memory 502 can be volatile or persistent storage. The program stored in the memory 502 can include one or more modules, each module including a series of instruction operations on the electronic device. Furthermore, the central processing unit 501 can be configured to communicate with the memory 502 and execute the series of instruction operations stored in the memory 502 on the electronic device 500.

[0079] Electronic device 500 may also include one or more power supplies 505, one or more wired or wireless network interfaces 504, one or more input / output interfaces 503, and / or one or more operating systems, such as Windows Server™, MacOSX™, Unix™, Linux™, FreeBSD™, etc.

[0080] The central processing unit 501 can perform the operations performed by the first aspect or any specific method embodiment of the first aspect, which will not be described in detail here.

[0081] This application provides a computer-readable storage medium including instructions that, when executed on a computer, cause the computer to perform the method as described in the first aspect or any specific implementation thereof.

[0082] This application provides a computer program product containing instructions or computer programs, which, when run on a computer, causes the computer to perform the method described in the first aspect or any specific implementation thereof.

[0083] It is understood that, in the various embodiments of this application, the sequence number of each step does not imply the order of execution. The execution order of each step should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0084] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working process of the system and device described above can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0085] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system or apparatus, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0086] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0087] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0088] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product (computer program product) is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, a business server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

Claims

1. A method for localizing documents, characterized in that, include: Obtain a preset document and a localized document template. The localized document template includes a preset document area and a localized metadata area. Obtaining the localized document template includes: obtaining the preset document template, which includes the preset document area; expanding the preset document template outside the preset document area with preset fields using a split table method, and using the preset fields as the localized metadata area to generate the localized document template. Configure localized document metadata in the localized metadata area according to preset local registration rules, and fill the document metadata other than the localized document metadata in the preset document into the preset document area according to preset adaptation rules to generate a localized document; wherein, the localized document metadata includes metadata that may change after the preset document is localized.

2. The localization method according to claim 1, characterized in that, The localized document metadata also includes: the location information of the preset document; The step of configuring local document metadata in the localized metadata area according to preset local registration rules includes: Use a preset localization plugin to monitor the location information of the preset document; If the location information of the preset document is inconsistent with the location information pre-configured in the localized metadata area, then the localized document metadata corresponding to the pre-configured location information is modified based on the location information of the preset document.

3. The localization method according to claim 1, characterized in that, The step of configuring local document metadata in the localized metadata area according to preset local registration rules includes: Retrieve the pre-configured localized document metadata from the localized metadata area and display the pre-configured localized document metadata; Modify the pre-configured localized document metadata according to localized business needs.

4. The localization method according to claim 3, characterized in that, The pre-configured localized document metadata includes: document type, localization plugin, or field alternative values; The modification of the pre-configured localized document metadata according to localized business needs includes: Modify the document type, the localization plugin, or the field alternative values ​​according to localized business requirements.

5. The localization method according to claim 1, characterized in that, The step of filling the document metadata (excluding the localized document metadata) in the preset document into the preset document area according to preset adaptation rules includes: The document metadata is processed to conform to the preset document region according to the preset document loading plugin; Based on the processing result, the content of the document metadata is filled into the corresponding field in the preset document area.

6. The localization method according to claim 1, characterized in that, Also includes: Configure whether the preset document is localized to obtain the configuration result; If the configuration result is to enable localization, then obtain the localized document template; If the configuration result is that localization is not enabled, then the preset document is loaded.

7. A document localization system, characterized in that, include: An acquisition unit is used to acquire a preset document and a localized document template. The localized document template includes a preset document area and a localized metadata area. Acquiring the localized document template includes: acquiring the preset document template, which includes the preset document area; expanding the preset document template outside the preset document area with preset fields using a split table method, and using the preset fields as the localized metadata area to generate the localized document template. The generation unit is configured to configure localized document metadata in the localized metadata area according to preset local registration rules, and fill the document metadata other than the localized document metadata in the preset document into the preset document area according to preset adaptation rules to generate a localized document; wherein, the localized document metadata includes metadata that may change after the preset document is localized.

8. An electronic device, characterized in that, include: Central processing unit, memory, and input / output interfaces; The memory is either a short-term storage memory or a persistent storage memory; The central processing unit is configured to communicate with the memory and execute instructions in the memory to perform the method according to any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, Includes instructions that, when executed on a computer, cause the computer to perform the method as described in any one of claims 1 to 6.

10. A computer program product having a computer program stored thereon, characterized in that, When the computer program is executed by a computer device, it is used to perform the method according to any one of claims 1 to 6.

Images