Page processing method
By determining the page generation request and generating target pages on the terminal, the problem of low front-end page development efficiency in the prior art is solved, and the effect of quickly generating target pages and improving development efficiency is achieved.
Patent Information
- Application Number
- CN202510287014.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-03-11
- Publication Date
- 2025-06-20
AI Technical Summary
The development efficiency of existing front-end pages is inefficient and cannot quickly meet changes in user needs.
Provide a page processing method, by determining a page generation request, determining an initial page based on page attribute information, and generating a target page based on target module and target data.
It realizes the rapid generation of target pages on the terminal, improves page development efficiency, and meets user needs.
Smart Images

Figure CN120179245A_ABST
Abstract
Description
Technical Field
[0001] The embodiments of this specification relate to the technical field of front - end development, and particularly to a page processing method. One or more embodiments of this specification also relate to a computing device and a computer - readable storage medium. Background Art
[0002] With the continuous development of computer technology, in many computer service scenarios, it is necessary to use front - end pages to provide computer services for users to meet their needs; However, with the continuous increase and change of user needs, it is necessary to quickly develop front - end pages that meet user needs; currently, the development of front - end pages is achieved manually, resulting in low development efficiency of front - end pages and being unable to meet user needs. Therefore, how to improve the page development efficiency has become an urgent technical problem to be solved. Summary of the Invention
[0003] In view of this, the embodiments of this specification provide a page processing method. One or more embodiments of this specification also relate to a page processing device, a computing device, a computer - readable storage medium, and a computer program product to solve the technical defects existing in the prior art.
[0004] According to the first aspect of the embodiments of this specification, a page processing method is provided, which is applied to a terminal and includes: Determine a page generation request, where the page generation request carries page attribute information; According to the page attribute information, determine an initial page including a target module, where the initial page is a page for human - machine interaction constructed using the target module; According to the data acquisition interface of the target module, determine the target data corresponding to the target module from a data processing unit, and generate a target page based on the initial page, the target module, and the target data.
[0005] According to the second aspect of the embodiments of this specification, a page processing device is provided, which is applied to a terminal and includes: A request determination module, configured to determine a page generation request, where the page generation request carries page attribute information; An initial page determination module, configured to determine an initial page including a target module according to the page attribute information, where the initial page is a page for human - machine interaction constructed using the target module; A target page generation module, configured to determine target data corresponding to the target module from a data processing unit according to a data acquisition interface of the target module, and generate a target page based on the initial page, the target module, and the target data.
[0006] According to a third aspect of the embodiments of the present specification, a computing device is provided, including: A memory and a processor; The memory is used to store computer programs / instructions, and the processor is used to execute the computer programs / instructions. When the computer programs / instructions are executed by the processor, the steps of the above-mentioned page processing method are implemented.
[0007] According to a fourth aspect of the embodiments of the present specification, a computer-readable storage medium is provided, which stores computer programs / instructions. When the computer programs / instructions are executed by a processor, the steps of the above-mentioned page processing method are implemented.
[0008] According to a fifth aspect of the embodiments of the present specification, a computer program product is provided, including computer programs / instructions. When the computer programs / instructions are executed by a processor, the steps of the above-mentioned page processing method are implemented.
[0009] One or more embodiments of the present specification provide a page generation method applied to a terminal. The method responds to a page generation request, determines an initial page including a target module according to page attribute information carried in the page generation request, where the initial page is a page for human-computer interaction constructed using the target module; then determines target data corresponding to the target module from a data processing unit according to a data acquisition interface of the target module, and generates a target page based on the initial page, the target module, and the target data; thereby realizing the rapid generation of a target page on the terminal, improving the page development efficiency, and meeting the user requirements. Description of the Drawings
[0010] Figure 1 Is a schematic diagram of other solutions provided by an embodiment of the present specification; Figure 2 Is an application schematic diagram of a page processing method provided by an embodiment of the present specification; Figure 3 Is a flowchart of a page processing method provided by an embodiment of the present specification; Figure 4 Is a schematic diagram of a page and a module in a page processing method provided by an embodiment of the present specification; Figure 5 Is a schematic diagram of a functional module in a page processing method provided by an embodiment of the present specification; Figure 6It is a schematic diagram of a modular driving device in a page processing method provided by an embodiment of this specification; Figure 7 It is a flowchart of the processing procedure of a page processing method provided by an embodiment of this specification; Figure 8 It is a structural block diagram of a computing device provided by an embodiment of this specification. Detailed implementation manners
[0011] In the following description, numerous specific details are set forth in order to provide a thorough understanding of this specification. However, this specification can be implemented in many other ways different from those described herein, and those skilled in the art can make similar generalizations without departing from the connotation of this specification. Therefore, this specification is not limited by the specific implementations disclosed below.
[0012] The terms used in one or more embodiments of this specification are for the purpose of describing specific embodiments only and are not intended to limit one or more embodiments of this specification. The singular forms "a", "the", and "said" used in one or more embodiments of this specification and the appended claims are also intended to include the plural forms unless the context clearly dictates otherwise. It should also be understood that the term "and / or" used in one or more embodiments of this specification refers to and encompasses any and all possible combinations of one or more of the associated listed items.
[0013] It should be understood that although the terms first, second, etc. may be used in one or more embodiments of this specification to describe various information, such information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of one or more embodiments of this specification, the first can also be referred to as the second, and similarly, the second can also be referred to as the first. Depending on the context, the word "if" as used herein can be interpreted as "when" or "while" or "in response to determining".
[0014] In addition, it should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in one or more embodiments of this specification are all information and data that have been authorized by the user or fully authorized by all parties, and the collection, use, and processing of the relevant data need to comply with the relevant laws, regulations, and standards of the relevant countries and regions, and corresponding operation entrances are provided for the user to select to authorize or refuse.
[0015] First, the noun terms involved in one or more embodiments of this specification are explained.
[0016] Page: In this method, it refers to a container composed of multiple modules and has the ability to be extended. A page is a prototype and template before instantiation, with the characteristics of flexible configuration and convenient extension.
[0017] Product line: In this method, it is the information used to divide pages according to specific service areas or processes; different product lines can correspond to different page sets. It should be noted that the pages of the same product have functional differences under different product lines, mainly manifested as the same modules having different fields.
[0018] Page instance: In this method, it refers to the page after instantiation, which can be used for release and online access, and is a front-end view with complete functions that can be accessed through the url after being released online.
[0019] Module: In this method, it refers to the smallest unit that combines front-end view components and back-end service processing functions and can be referenced and arranged by pages. A module consists of multiple fields, module components, and configuration information.
[0020] Module instance: In this method, it refers to the module after page instantiation, and each module instance is associated with a unique page instance; Field: It refers to a data input or display position in the user interface. A field is used to receive data input by the user or display data obtained from the back-end. For example, in a form structure, fields are presented in various forms such as labels, input boxes, dropdown menus, checkboxes, etc.
[0021] Field component: In this method, it refers to the front-end elements that can be associated with fields, such as dropdown boxes and text input boxes.
[0022] Module component: In this method, it refers to the front-end elements that can be associated with modules, such as lists and forms, which are used to determine the interaction type of the module.
[0023] Application: In this method, it refers to the back-end part of the program that provides specific functions and execution logic.
[0024] With the continuous development of computer technology, in many computer service scenarios, it is necessary to use front-end pages to provide computer services for users to solve user needs; however, with the continuous increase and change of user needs, it is necessary to quickly develop front-end pages that meet user needs; and the current development of front-end pages is achieved manually, resulting in low development efficiency of front-end pages and unable to meet user needs.
[0025] In view of the above problems, this specification provides two other solutions. The first other solution is a low-code application development system, which provides graphical development components. Users can complete the construction of applications by dragging and configuring without writing code or only writing a small amount of code. The first other solution is a development tool for digital administrators, which has functions such as visual forms, automated processes, intelligent reports, and rich API interfaces. Through the building block construction method of dragging and dropping, it realizes mobile online management and services.
[0026] However, the above two solutions have relatively large defects; for example, Figure 1 is a schematic diagram of another solution provided by an embodiment of this specification; Figure 1 The page showing another solution; Based on Figure 1 It can be seen that the low-code system provides graphical development components. Users can complete the construction of applications by dragging and configuring the components without writing code or only writing a small amount of code. Based on Figure 1 It can be known that the above two other solutions emphasize what you see is what you get during the page configuration process and the page can be published and used after development. Therefore, a strong association method between the page and the components is adopted, directly developing components in the page, or adding the concept of a container in the middle and arranging components in the container. However, the container itself does not have the ability to be instantiated. Therefore, when a container cannot be reused in the pages of different product lines, the components cannot be differentially displayed. The main disadvantages summarized for the existing solutions are mainly reflected in the following two aspects: 1. If it is necessary to reuse the components configured on the current page in the pages of other product lines, if the fields used in different product lines are different, it is necessary to modify the component configuration and modify the bound node data. If the same fields need to be modified in the pages of different product lines, it is necessary to reconfigure the field components of each page.
[0027] 2. The components only support front-end components, mainly featuring form-driven, which has nothing to do with the product. Therefore, the configured components do not have product universality and cannot precipitate product capabilities.
[0028] Based on this, in this specification, a page processing method is provided. This specification also relates to a page processing device, a computing device, and a computer-readable storage medium, which will be described in detail one by one in the following embodiments.
[0029] See Figure 2 , Figure 2 shows an application schematic diagram of a page processing method provided by an embodiment of this specification. Based on Figure 2It can be seen that this method can install a modular drive device (such as a terminal) on the user application of the client. The current front-end view requests the modular drive device with the page instance encoding and product line information of the view as request parameters (such as page attribute information). The device obtains the page instance data and module instance data in the module data persistence according to the request parameters (such as the initial page containing the target module). The device calls the corresponding interface according to the interface configured by the module instance, and returns the executed data result (such as the target data) to the device. The modular drive device combines the configuration information of the page instance and the module instance, merges the response contents of each interface, performs differential display on the response contents according to the product line, and responds the differential result (such as the target page) to the front-end view according to the agreed module protocol. The front-end view renders the final presentation result.
[0030] See Figure 3 , Figure 3 FIG. shows a flowchart of a page processing method according to an embodiment of the present specification, which specifically includes the following steps.
[0031] Step 302: Determine a page generation request, where the page generation request carries page attribute information.
[0032] Among them, the page generation request can be understood as a request for the terminal to generate a target page. The page attribute information is information representing page attributes. For example, the page attribute information is page identification information and service information (such as product line information). Among them, the page identification information can be understood as information uniquely identifying an initial page. For example, the page identification information can be a page instance encoding, a page instance name, etc. The service information can be understood as information about the service corresponding to the initial page. Through the service information, the initial page corresponding to a specific service can be obtained. For example, service identification, product line information (such as product line identification), etc.
[0033] The terminal can be understood as a hardware device or software program for processing pages. When the terminal is a hardware device, the terminal can be a client device (such as a smart phone, a tablet computer, a laptop computer, a handheld computer, a personal computer, a smart home device, a vehicle-mounted device, etc.), a smart device, a computing device, etc.; when the terminal is a software program, the terminal can be a client program, an application program, a plugin of an application program, etc.; in one or more embodiments provided in the present specification, the terminal can be a modular drive device, and the modular drive device can be a software program, and the modular drive device can be installed in an application program.
[0034] In one or more embodiments provided in the present specification, before determining the initial page containing the target module according to the page attribute information, the following is further included: Determine at least one initial module for constructing the initial page, and determine the page configuration information corresponding to the initial page, where the page configuration information is used to adjust the at least one initial module; Use the page configuration information to adjust the initial module identification information, initial module visualization data, initial application configuration information, and initial permission information in the at least one initial module to obtain at least one target module including target module identification information, target module visualization data, target application configuration information, and target permission information; Use the at least one target module to construct the initial page.
[0035] Among them, the initial module can be understood as a functional module for constructing the initial page; the target module can be understood as a functional module adjusted using the page configuration information; The initial module identification information, initial module visualization data, initial application configuration information, and initial permission information can be understood as the module identification information, module visualization data, application configuration information, and permission information configured for the initial module; the target module identification information, target module visualization data, target application configuration information, and target permission information can be understood as the module identification information, module visualization data, application configuration information, and permission information adjusted using the page configuration information.
[0036] Among them, the module identification information can be understood as information that uniquely identifies a functional module. For example, the module identification information can be understood as the module name and module code.
[0037] The module visualization data can be understood as the data that can be visually displayed in the functional module. The module visualization data includes human-computer interaction components, visual display components, visual information, and / or component configuration information; the human-computer interaction components can be module components, field components, etc. in the functional module; the visual display components can be understood as components that can display visual information to users. For example, the visual display components can be components such as labels, backgrounds, and text boxes. The visual information can be information that can be displayed to users, such as the module title, etc. The component configuration information can be understood as the information configured for the human-computer interaction components and visual display components. For example, the component configuration information can be module extension configuration, field-level cascade control information, etc.
[0038] The application configuration information can be understood as the information configured for the associated application; the associated application can be understood as a backend program that provides specific functions and execution logics; the application configuration information includes associated application information (used to route requests initiated by module instances to specific applications) and interfaces (used to call specific execution logics or backend programs).
[0039] The permission information can be understood as the permissions configured for the function modules.
[0040] Specifically, before constructing the initial page, multiple initial modules need to be constructed. Among them, the initial module contains information such as initial module identification information, initial module visualization data, initial application configuration information, and initial permission information.
[0041] In the case where it is necessary to construct the initial page using the initial modules, at least one initial module for constructing the initial page needs to be determined from the multiple initial modules; then, page configuration information for adjusting at least one initial module used for constructing the initial page is received.
[0042] The page configuration information contains configuration information for adjusting the initial module identification information, initial module visualization data, initial application configuration information, and initial permission information. For example, module identification information, module visualization information, application configuration information, and / or claim information designed according to the actual product line, etc.
[0043] Then, using the configuration information contained in the page service information, the initial module identification information, initial module visualization data, initial application configuration information, and initial permission information in the initial module are updated or replaced, so as to obtain target module identification information, target module visualization data, target application configuration information, and target permission information; furthermore, at least one target module containing the target module identification information, target module visualization data, target application configuration information, and target permission information is obtained. Finally, at least one target module can be used to construct an initial page that meets the requirements of the actual product line.
[0044] Taking the application of the page processing method provided in this specification in the technical development scenario as an example, the page processing method is described as follows: 1. Create a function module. Before arranging the page, a corresponding function module (i.e., the initial module) needs to be created for the page; this function module can be understood as a basic module or module template; subsequently, according to different product lines, this function module can be adjusted to obtain a function module (i.e., the target module) that meets the requirements of the product line.
[0045] 2. Create a page. After creating the function module, a page can be created based on this function module. The specific implementation method is as follows: First, according to different product line information (i.e., service information), select the function module m (i.e., the initial module) that needs to be added to the page p, and reference the module m in the page p. The page p is
[0046] 3. Adjust the module.
[0047] Specifically, on page p corresponding to the product line information, contents such as page permission points of the configuration module, the industry line to which the configuration module belongs, interface input parameters of the configuration module, and display fields of the configuration module (i.e., target module identification information, target module visualization data, target application configuration information, target permission information) are configured to obtain a configured page (i.e., the initial page).
[0048] As can be seen from the above embodiments, the method for improving the component reuse rate and the rapid configuration and online ability under different product lines is realized in an end-to-end modular-driven manner; by means of module configuration field components and page reference modules, the module and the execution logic are associated to achieve the purpose of module reusability. In addition, the component reuse rate and the method of configuring component service capabilities can also be realized by classifying components into module components and field components and binding the module components to execution interfaces.
[0049] In one or more embodiments provided in the specification, the constructing the initial page by using the target module includes: Determine the module position information for the target module, and use the module position information to adjust the position of the target module to obtain a page to be instantiated; Instantiate the page to be instantiated and the target module in the page to be instantiated to obtain the initial page, where the initial page is an instantiated page instance, and the initial page contains an instantiated target module instance.
[0050] Following the above example, after the page is configured, the page can be instantiated to obtain an instantiated page; specifically, on page p corresponding to the service information, the position of each module is configured to obtain a page to be instantiated (i.e., the page to be instantiated), and then, the configured function module is instantiated to obtain a module instance (i.e., the target module instance) and obtain a page instance (i.e., the instantiated page instance) based on the module instance . Among them, function f indicates that through the page, permission points, and product line, module m in the page can be mapped to obtain a specific module instance M; where it satisfies .
[0051] It should be noted that after the page is instantiated, the page needs to be stored. Specifically, it means to persistently store the instantiated page; specifically, the method of the present invention can persistently store the instantiated page through a database to save the page instance generated by the page; at the same time, the function module referenced by the current page instance generates a corresponding module instance, and the module instance is persistently stored.
[0052] Based on the above embodiments, it can be seen that the present method can be instantiated and displayed according to the product line differences through page instantiation and module instantiation.
[0053] In one or more embodiments provided in this specification, the determining the page generation request includes: Receiving a page generation request sent by an interaction device of the terminal, where the page generation request is sent by the interaction device when the user performs a page acquisition operation.
[0054] Continuing with the above example, when the front-end view (i.e., the interaction device) renders a page using the modular driving method, first, it is necessary to obtain the page instance code, the current product line b, and the current user information a; based on the page instance code, the current product line b, and the current user information a, a fetch request (i.e., the page generation request) is generated and sent to the modular driving device.
[0055] Step 304: Determine an initial page containing the target module according to the page attribute information, where the initial page is a page for human-computer interaction constructed using the target module.
[0056] Specifically, the present method can determine an initial page containing the target module from the page storage unit according to the page attribute information; the page storage unit can be understood as a unit for storing the initial page. For example, the page storage unit can be a database, a local disk, or a cloud database, etc.
[0057] In one or more embodiments provided in this specification, after determining the initial page containing the target module according to the page attribute information, the following is further included: Rendering the initial page to the page display unit corresponding to the terminal; Among them, the page display unit can be understood as a unit for displaying the initial page or the target page. The page display unit can be a page display device such as a display screen or a projector, or the page display unit can be a page display program such as a web page or an application program interface.
[0058] Continuing with the above example, after the modular driving device requests and obtains the persistent page instance data from the database, it can return the page instance data to the front-end view; and the front-end view (i.e., the page display unit) performs preliminary rendering according to the module instance, so as to display the initial page to the user; thus meeting the user's need to obtain the page.
[0059] In one or more embodiments provided in this specification, the page generation request carries the page attribute information, service information, and permission information; The determining the initial page containing the target module according to the page attribute information includes: Perform information verification on the page attribute information and the service information to obtain an information verification result; When the information verification result indicates that the information verification is passed, obtain the initial page containing the target module from the page storage unit according to the page attribute information and the service information; Continuing with the previous example, first, for the modular drive device, when the exposed interface receives a request, it first performs parameter verification on the request parameters (i.e., page attribute information, service information) in the request; second, for the modular drive device, after the parameter verification is passed, it obtains the corresponding module instance data and page instance from the database. By verifying the information verification result, errors in the information carried in the page generation request are avoided, and thus the problem of reduced page processing efficiency caused by incorrect information is avoided.
[0060] Step 306: Determine the target data corresponding to the target module from the data processing unit according to the data acquisition interface of the target module, and generate a target page based on the initial page, the target module, and the target data.
[0061] Among them, the target page can be understood as a page containing the target module and the target data, and this target page can be rendered to the page display unit for display.
[0062] The data acquisition interface can be understood as an interface for calling the data processing unit, and this data processing unit can be a unit capable of performing data processing to obtain target data; this data processing unit can be understood as an application program, a server, etc.
[0063] In one or more embodiments provided in this specification, the determining the target data corresponding to the target module from the data processing unit according to the data acquisition interface of the target module, and generating a target page based on the initial page, the target module, and the target data includes: In response to a data acquisition request for the target module in the initial page, determine the data acquisition interface of the target module, and according to the data acquisition interface, determine the target data corresponding to the target module from the data processing unit corresponding to the target module; Generate a target page based on the initial page, the target module, and the target data, and render the target page to the page display unit of the terminal.
[0064] Among them, this initial page is the initial page rendered to the page display unit.
[0065] Continuing with the above example, after the modular drive device returns the page instance data to the front-end view for preliminary rendering and presents the initial page to the user, it can also call an interface according to the request to process the data result. Specifically: The front-end view sends an interface request to the modular drive device.
[0066] After the preliminary rendering is completed, the front-end page obtains the configured field components, which have front-end component styles such as dropdown boxes and lists; in this case, if it is still necessary to further obtain the data result corresponding to the field component, the modular drive device is used to call an interface to process the data result.
[0067] The specific method of "calling an interface to process the data result" is as follows: The modular drive device transfers the request parameters to the corresponding module component processing unit; each module component processing unit calls the logic execution method through each interface and returns the execution result data (i.e., the target data) to the modular drive device.
[0068] The modular drive device generates a target page from the returned execution result data and module configuration information and sends it to the front-end view for page echo, so as to display the complete data using the front-end view.
[0069] In one or more embodiments provided in this specification, generating a target page based on the initial page, the target module, and the target data includes: Determine the data display format corresponding to the target module, and based on the data display format, perform data screening on the target data to obtain screened data; Configure the screened data in the target module of the initial page to obtain the target page.
[0070] Among them, the data display format can be understood as the format of the data to be displayed, such as the data size, data font, etc.
[0071] Continuing with the above example, the modular drive device performs differential display on the returned data result according to the product line to obtain a differentially adjusted data result (i.e., screened data); For example, the data result obtained by using the interface is a table containing 100 rows of data; when the product line only needs the first 20 rows of data (i.e., the data display format), the "product line differential display unit" can be used to adjust the data result to obtain the data result required by the product line (i.e., the first 20 pieces of data).
[0072] Use the "execution result merging unit" to merge each data result to obtain merged data; Using the "response data conversion unit", the merged data is converted into the protocol for the field component echo data of the front-end view.
[0073] In one or more embodiments provided in this specification, the data processing unit is a data processing application; The determining of the target data corresponding to the target module from the data processing unit according to the data acquisition interface includes: Determining a data identifier for the target data, and sending the data identifier to the data processing application corresponding to the target module through the data acquisition interface; Receiving the target data corresponding to the data identifier returned by the data processing application.
[0074] Among them, the data processing application can be understood as a back-end program that provides specific functions and execution logics. The data identifier is information used to uniquely identify the target data. For example, data name, data number, etc. In the case where the target data is a data table, the data identifier can be the data table name or the data table number.
[0075] Continuing with the above example, the modular drive device can utilize each module component processing unit to call the logic execution program through each interface (i.e., the data acquisition interface), obtain the data result, and return the data result to the modular drive device, thereby obtaining the data result processed by the back-end program.
[0076] In one or more embodiments provided in this specification, the page generation request carries the page attribute information, service information, and user permission information.
[0077] The determining of the target data corresponding to the target module from the data processing unit according to the data acquisition interface of the target module, and generating a target page based on the initial page, the target module, and the target data includes: Performing information verification on the page attribute information and the service information to obtain an information verification result; Performing right item verification on the right item information in the case where the information verification result is that the information verification passes; In the case where the permission verification passes, determining the target data corresponding to the target module from the data processing unit according to the data acquisition interface of the target module, and generating the target page based on the initial page, the target module, and the target data.
[0078] Continuing with the above example, after the initial rendering is completed, the front-end page obtains the configured field components, which have front-end component styles such as drop-down boxes and lists. In this case, if further data results corresponding to the field components are still required, a modular driving device is used to call an interface to process the data results. The specific method of "calling an interface to process the data results" is as follows: 1. The modular driving device performs forward processing.
[0079] First, when the exposed interface of the modular driving device receives a request, it first verifies the request parameters in the request (i.e., page attribute information and service information). Second, after the verification passes, the modular driving device obtains the corresponding module instance data. Finally, the modular driving device performs permission verification on the request through the permission information configured in the module instance and the user information in the request parameters (i.e., user permission information). If the permission verification passes, it is determined that the forward processing is successful, and subsequent processing is executed.
[0080] 2. The modular driving device executes the processing logic.
[0081] Specifically, after the forward processing is completed, the modular driving device transfers the request parameters to the corresponding module component processing unit. Each module component processing unit calls the logic execution method through each interface and returns the execution result (i.e., the data result) to the modular driving device.
[0082] One or more embodiments of this specification provide a page generation method applied to a terminal. The method responds to a page generation request and determines an initial page including a target module according to the page attribute information carried in the page generation request. The initial page is a page for human-computer interaction constructed using the target module. Then, the target data corresponding to the target module is determined from the data processing unit according to the data acquisition interface of the target module, and a target page is generated based on the initial page, the target module, and the target data. Thus, the target page can be quickly generated on the terminal, improving the page development efficiency and meeting the user requirements.
[0083] The following combines the attached Figure 7 , taking the application of the page processing method provided in this specification in a technology development scenario as an example, to further illustrate the page processing method. Among them, Figure 7 shows the processing process flowchart of a page processing method provided by an embodiment of this specification.
[0084] First of all, it should be noted that low-code development is aimed at achieving efficient and rapid construction and release of application programs, while reducing the complexity and cost of development. Low-code development aims to reduce the workload of traditional coding through visual interfaces and predefined components, enabling enterprises to respond more quickly to market changes and product requirements.
[0085] In response to the above requirements, this specification provides an end-to-end modular-driven method for technology development, which provides a modular configuration method; Based on Figure 7 it can be known that this modular configuration method includes module configuration and persistence capabilities, page request module configuration information processing capabilities, and module execution capabilities. Among them, Figure 7 the link represented by the dashed arrow in the middle is the module configuration and persistence capabilities; Figure 7 the link represented by the solid arrow in the middle is the page request module configuration information processing and module execution capabilities of end-to-end modularization.
[0086] For the module configuration and persistence capabilities, reference can be made to Figure 7 steps 702 to 704 in Step 702: Orchestrate the page based on the module.
[0087] This step means: Orchestrate the page by configuring the modules with the required functions in the page.
[0088] Among them, the relationships among the page, module, page instance, and module instance are as shown in Figure 4 The relationship between the page and the module is many-to-many, that is to say, each page can be associated with multiple modules, each module can be referenced by multiple pages, the page can generate instance pages of different product lines according to the product line, and at the same time each page instance generates multiple module instances. Based on this, in the case of generating multiple different page instances according to the product line, one page instance can correspond to multiple module instances.
[0089] Specifically, the specific execution method of this step is as follows: 1. Create a functional module Before orchestrating the page, it is necessary to create a corresponding functional module for the page; this functional module can be understood as a basic module or module template; subsequently, it can be adjusted according to different product lines to obtain a functional module that meets the requirements of the product line.
[0090] The configuration of this functional module is as shown in Figure 5 The content shown; the functional module in the modular drive device to which it belongs has the function of including: module title, module name, module code, module components, interfaces, associated applications, domains, permission points, n field components, field-level cascade control, module extension configuration.
[0091] Among them, the module title: used to display the title of the module instance on the page; Module name and module code: used to uniquely identify a module during the persistent and modular drive device operation; Interface: used for the modular drive device to call the specific execution logic (i.e., application); Module components: determine the functions and styles of the module instance on the page, as well as the specific module component processing units called by the application during product processing; Associated application: used to route the requests initiated by the module instance to the specific application; Module extension configuration: used for the extension item configuration of the module's display style on the page instance; Permission point: used to control the user permissions of the module on the page instance; Field component: used for the front-end elements associated with the field, such as dropdown boxes and text input boxes; Field cascading control: used to control the cascading relationship between multiple fields, such as the display value of one field being controlled by the specific value of another field.
[0092] It should be noted that assuming the field component is k, the functional module m created contains n field components, which can be expressed as .
[0093] 2. Create a page.
[0094] After creating the functional module, a page can be created based on this functional module. The specific implementation method is as follows: First, according to different product line information (i.e., product line), select the functional module m that needs to be added to the page p, and reference the module m in the page p. This page p is
[0095] Second, adjust the module.
[0096] Specifically, in the page p corresponding to this product line information, configure the position of each module, configure the page permission points of the module, configure the industry line to which the module belongs, configure the interface input parameters of the module, configure the display fields of the module, etc., to obtain the configured page.
[0097] 3. Instantiate the page to obtain the instantiated page.
[0098] First, for the created page p, set the permission point a of the module m, set the product line b of the module, and set the displayable fields of the module to obtain the module instance .
[0099] Among them, the function f indicates that through the page, permission points, and product lines, the module m in the page can be mapped to obtain a specific module instance M; where it satisfies , and obtain a page instance .
[0100] Step 704: Store the page.
[0101] This step refers to the persistent storage of the instantiated page; specifically, the instantiated page is persistently stored through the database, thereby saving the page instance generated by the page; at the same time, the function modules referenced by the current page instance generate corresponding module instances, and the module instances are persistently stored (i.e., module data persistence).
[0102] Regarding the page request module configuration information processing ability and module execution ability, it can be to obtain the page instance configuration (i.e., configuration information, data result) using the front-end view. Specifically, it means that the browser (i.e., the front-end view) passes through Figure 7 the process of the solid line in to obtain the page instance information. Specifically, it can include the following steps 706 to step 716: Step 706: Obtain the page instance code and product line information; In this method, when the front-end view renders the page using the modular driving method, first, it is necessary to obtain the page instance code, the current product line b, and the current user information a; In addition, before "obtaining the page instance code and product line information", it is necessary to install an end-to-end modular driving device at each application. One application program of the terminal corresponds to one modular driving device; And, it is necessary to implement the interface of the modular driving device for accessing the application and expose the interface.
[0103] Based on Figure 6 it can be known that the modular driving device has the functions of including: a parameter verification unit, a permission verification unit, an instance acquisition unit, n module component processing units, an execution result merging unit, a product line differentiation display unit, and a corresponding data conversion unit.
[0104] As Figure 6 shown, among them, the parameter verification unit: is used to verify the page request parameters after obtaining the page request parameters in the forward processing link; The instance acquisition unit: is used to obtain the page instance and module instance according to the parameters after the parameter verification unit verifies the parameters passed.
[0105] The permission verification unit: is used to verify the permission verification information. Specifically, the modular driving device can obtain the permission verification information according to the module instance and call the permission verification unit to verify the permission verification information.
[0106] Module component processing unit: used to call the interfaces of corresponding module components and obtain the data results returned by the interfaces. Specifically, after the forward processing of the modular drive device is passed, logical processing is executed. The execution method of this logical processing is: obtain the module components of the module instance, and through the module component processing unit corresponding to this modular drive device, call the interfaces of the corresponding module components to obtain the data results.
[0107] Product line differential display unit: used to perform differential display on the returned data results according to the product line and obtain the differentially adjusted data results; Execution result merging unit, used to merge each data result to obtain merged data; Response data conversion unit, used to convert the merged data into the protocol of the field component echo data of the front-end view.
[0108] Specifically, after the forward processing and logical processing of the modular drive device are completed, response processing is performed on the data returned by each interface. The method of this response processing is: call the product line differential display unit to filter the fields differentially displayed according to the product line, call the execution result merging unit to merge the processed fields, and call the response data conversion unit to make the response data conform to the content of the module protocol for front-end view display.
[0109] Step 708: Send a request to the modular drive device.
[0110] First, generate a fetch request based on the page instance code, the current product line b, and the current user information a.
[0111] Second, send this fetch request to the modular drive device to request the modular drive device to perform a page fetch operation.
[0112] Step 710: The modular drive device obtains the instantiated page and instantiated module from the module data persistence.
[0113] First, the modular drive device requests and obtains the persisted page instance data from the database; Second, the modular drive device returns the page instance data to the front-end view; and the front-end view performs preliminary rendering according to the module instance, thereby displaying the initial page to the user.
[0114] Step 712: Call the interface to process the data results.
[0115] Specifically, the front-end view sends an interface request to the modular drive device.
[0116] After the initial rendering is completed, the front-end page obtains the configured field components, which have the styles of front-end components such as drop-down boxes and lists; in this case, if it is still necessary to further obtain the data results corresponding to the field components, a modular driving device is used to call the interface for data result processing. Among them, each module M corresponds to an application c; for the page instance P, the data results to be obtained can be defined as a set C , for the elements in the C set, interface requests associated with M are sent respectively through the interface.
[0117] The specific method of "calling the interface for data result processing" is as follows: 1. The modular driving device performs forward processing.
[0118] First, when the exposed interface of the modular driving device receives a request, it first validates the request parameters; Second, after the validation passes, the modular driving device obtains the corresponding module instance data; Finally, the modular driving device performs permission verification on the request through the permission information configured in the module instance and the user information in the request parameters.
[0119] 2. The modular driving device executes the processing logic.
[0120] Specifically, after the forward processing is completed, the modular driving device transfers the request parameters to the corresponding module component processing unit; Each module component processing unit calls the logic execution method through each interface and returns the data result to the modular driving device.
[0121] Step 714: Obtain the data result returned by the execution logic.
[0122] Specifically, after the forward processing and the execution of the processing logic are completed, the modular driving device executes the response processing; the execution method of this "response processing" is as follows: 1. The modular driving device performs differential display on the returned data results according to the product line to obtain the differentially adjusted data results (i.e., the data results); For example, the data result obtained by using the interface is a table containing 100 rows of data; when the product line only needs the first 20 rows of data, the "product line differential display unit" can be used to adjust the data result to obtain the data result required by this product line (i.e., the first 20 pieces of data).
[0123] 2. Use the "execution result merging unit" to merge each data result to obtain the merged data; 3. Use the "response data conversion unit" to convert the merged data into the protocol of the field component echo data of the front-end view.
[0124] Step 716: Return configuration information and data results for page display.
[0125] After the modular drive device completes the processing, the data results and configuration information can be sent to the front-end view for page echo, so that the complete data can be displayed using the front-end view.
[0126] The front-end view, after receiving the data responded by the modular driver of each application, responds with the data result content and displays the complete data.
[0127] Based on the above embodiments, it can be known that the page processing method provided in this specification provides an end-to-end modular driving method and device for technology development in order to solve the customized development needs of different customers in the same product line scenario, avoid repeated development, and improve product delivery efficiency. This method aims to achieve personalized customization and efficient development while realizing the decoupling of core product development through a modular design concept, and significantly enhances the ability of product iteration and adaptation to product scenarios. The method and device fully support modular drive, and each module has specific product capabilities and can be freely combined into product pages, thereby significantly improving the development efficiency of the front-end and server, and has strong expansion and customization capabilities. In a page, each module can be flexibly arranged to achieve one-time development and multiple reuse, precipitate the product capabilities of the product, and achieve several times the development efficiency and cost reduction.
[0128] Considering that the existing solutions adopt a strong association between pages and components, components are developed directly in the page, or the concept of container is added in the middle and components are arranged in the container, but the container itself does not have the ability to instantiate, so it is impossible to reuse the differentiated display of real-time components of a container in the pages of different product lines. In this regard, this method introduces the concept of module between pages and components through a modular drive method, and instantiates the pages and modules respectively. When different product lines or fields are selected for existing modules, module instances and page instances are generated. Each instance is the result of one reuse, thereby removing the strong association between pages and components.
[0129] At the same time, the components of the existing solutions only support front-end components, which are mainly form-driven and have nothing to do with the product. Therefore, the configured components do not have product universality. In response to this shortcoming, this method associates specific applications in the module and implements the execution logic (i.e., application) capability of the module driver through the module-associated execution interface, thereby ensuring that each module is driven by the corresponding execution logic and there is no coupling between interfaces between different modules.
[0130] To solve the problems of poor component configuration reuse ability, inability to support differential application of components according to product lines, inability of component interfaces to adapt to product line differences, and inability to adapt to rapid upgrades of product line changes in the scenario of multiple product lines, this specification also provides an end-to-end modular driving method. This method integrates the configuration, persistence ability, page request module configuration information processing ability, and module execution ability of the modules, thereby realizing fine-grained module configuration of the front-end page. By performing persistence processing on the configuration information, the modular driving device can organically combine the module configuration ability with the back-end application service to realize the driving and circulation of the overall function. This method effectively solves the problem of page reuse of modules in different product lines, supports the mixed orchestration of different application modules, and improves the flexibility and scalability of the system. Ensure that each product line can independently and quickly adjust and upgrade functions to meet the personalized needs of different industries and enterprises.
[0131] In summary, this specification provides an end-to-end modular driving method and device for technology development. Compared with existing low-code systems, the achieved technical effects are as follows: 1. Through the method of module configuration, a module is introduced between the page and the component to manage fields, and the ability of module instantiation is provided to realize the reuse of components.
[0132] 2. The module is bound to the application, and the functions of the complete front-end and back-end applications can be used by introducing this module in other pages, providing the ability to quickly go online with page configuration.
[0133] 3. Modular driving: By means of component modularization, product capabilities are continuously precipitated, and it becomes faster and faster to build a product solution. 4. Product line differentiation: Through the methods of page instantiation and module instantiation, instantiation display can be performed according to product line differences. 5. Precise permission control: The permission granularity can be controlled to the modules, buttons, and data rows of the page, and it can be achieved through simple configuration. 6. Complete decoupling between multiple applications and interfaces: Each module can be associated with different applications, can be associated with various interfaces, and can be flexibly orchestrated on the page. 7. Digital product capabilities: Through the online registration management of modules, all capabilities of the product are digitally depicted, facilitating visual management and transplantation of product modules and avoiding duplicate development.
[0134] Corresponding to the above method embodiments, this specification also provides page processing device embodiments. The page processing device is applied to a terminal, and the device includes: A request determination module configured to determine a page generation request, where the page generation request carries page attribute information; An initial page determination module, configured to determine an initial page containing a target module according to the page attribute information, where the initial page is a page for human-computer interaction constructed by using the target module; A target page generation module, configured to determine target data corresponding to the target module from a data processing unit according to a data acquisition interface of the target module, and generate a target page based on the initial page, the target module, and the target data.
[0135] Optionally, the page processing device further includes a page construction module, configured to: Determine at least one initial module for constructing the initial page, and determine page configuration information corresponding to the initial page, where the page configuration information is used to adjust the at least one initial module; Use the page configuration information to adjust initial module identification information, initial module visualization data, initial application configuration information, and initial permission information in the at least one initial module to obtain at least one target module including target module identification information, target module visualization data, target application configuration information, and target permission information; Construct the initial page by using the at least one target module.
[0136] Optionally, the page construction module is configured to: Determine module position information for the target module, and use the module position information to adjust the position of the target module to obtain a page to be instantiated; Instantiate the page to be instantiated and the target module in the page to be instantiated to obtain the initial page, where the initial page is an instantiated page instance, and the initial page includes an instantiated target module instance.
[0137] Optionally, the page processing device further includes a page rendering module, configured to: Render the initial page to a page display unit corresponding to the terminal; The determining target data corresponding to the target module from a data processing unit according to a data acquisition interface of the target module, and generating a target page based on the initial page, the target module, and the target data includes: In response to a data acquisition request for the target module in the initial page, determine the data acquisition interface of the target module, and according to the data acquisition interface, determine the target data corresponding to the target module from a data processing unit corresponding to the target module; Generate a target page based on the initial page, the target module, and the target data, and render the target page to the page display unit of the terminal.
[0138] Optionally, the page rendering module is configured to: Determine the data display format corresponding to the target module, and based on the data display format, perform data screening on the target data to obtain screened data; Configure the screened data in the target module of the initial page to obtain the target page.
[0139] Optionally, the data processing unit is a data processing application; The target page generation module is configured to: Determine the data identifier for the target data, and send the data identifier to the data processing application corresponding to the target module through the data acquisition interface; Receive the target data corresponding to the data identifier returned by the data processing application.
[0140] Optionally, the initial page determination module is configured to; Perform information verification on the page attribute information and the service information to obtain an information verification result; In the case where the information verification result is that the information verification is passed, obtain the initial page including the target module from the page storage unit according to the page attribute information and the service information.
[0141] Optionally, the request determination module is configured to: Receive a page generation request sent by the interaction device of the terminal, where the page generation request is sent by the interaction device when the user performs a page acquisition operation; The page rendering module is further configured to: Render the target page to the page display unit corresponding to the terminal.
[0142] One or more embodiments of this specification provide a page generation device applied to a terminal. The device responds to a page generation request, determines an initial page including a target module according to the page attribute information carried in the page generation request, where the initial page is a page for human-computer interaction constructed using the target module; then determines the target data corresponding to the target module from a data processing unit according to the data acquisition interface of the target module, and generates a target page based on the initial page, the target module, and the target data; thereby achieving the rapid generation of a target page on the terminal, improving the page development efficiency, and meeting the user requirements.
[0143] The above is a schematic solution of a page processing device according to this embodiment. It should be noted that the technical solution of this page processing device and the technical solution of the above page processing method belong to the same concept. For the details not described in the technical solution of the page processing device, reference can be made to the description of the technical solution of the above page processing method.
[0144] Figure 8 FIG. shows a block diagram of a computing device 800 according to an embodiment of the present specification. The components of the computing device 800 include, but are not limited to, a memory 810 and a processor 820. The processor 820 is connected to the memory 810 via a bus 830, and a database 850 is used to store data.
[0145] The computing device 800 further includes an access device 840, which enables the computing device 800 to communicate via one or more networks 860. Examples of these networks include the Public Switched Telephone Network (PSTN), Local Area Network (LAN), Wide Area Network (WAN), Personal Area Network (PAN), or a combination of communication networks such as the Internet. The access device 840 may include one or more of any type of wired or wireless network interface (e.g., a network interface card (NIC)), such as an IEEE 802.11 Wireless Local Area Network (WLAN) wireless interface, a Worldwide Interoperability for Microwave Access (Wi-MAX) interface, an Ethernet interface, a Universal Serial Bus (USB) interface, a cellular network interface, a Bluetooth interface, or a Near Field Communication (NFC) interface.
[0146] In an embodiment of the present specification, the above components of the computing device 800 and Figure 8 other components not shown in the figure may also be connected to each other, for example, via a bus. It should be understood that Figure 8 the block diagram of the computing device shown is only for illustrative purposes and is not a limitation on the scope of the present specification. Those skilled in the art may add or replace other components as needed.
[0147] The computing device 800 can be any type of stationary or mobile computing device, including mobile computers or mobile computing devices (e.g., tablet computers, personal digital assistants, laptop computers, notebook computers, netbooks, etc.), mobile phones (e.g., smartphones), wearable computing devices (e.g., smartwatches, smart glasses, etc.) or other types of mobile devices, or stationary computing devices such as desktop computers or personal computers (PCs). The computing device 800 can also be a mobile or stationary server.
[0148] Wherein, the processor 820 is configured to execute the following computer-executable instructions, and when the computer-executable instructions are executed by the processor, the steps of the above-mentioned page processing method are implemented.
[0149] Each embodiment in this specification is described in a progressive manner. For the same or similar parts among the embodiments, reference can be made to each other. The key point of each embodiment is to illustrate the differences from other embodiments. In particular, for the computing device embodiment, since it is basically similar to the page processing method embodiment, the description is relatively simple, and for the relevant parts, reference can be made to the partial description of the page processing method embodiment.
[0150] An embodiment of this specification also provides a computer-readable storage medium, which stores computer programs / instructions, and when the computer programs / instructions are executed by a processor, the steps of the above-mentioned page processing method are implemented.
[0151] Each embodiment in this specification is described in a progressive manner. For the same or similar parts among the embodiments, reference can be made to each other. The key point of each embodiment is to illustrate the differences from other embodiments. In particular, for the computer-readable storage medium embodiment, since it is basically similar to the page processing method embodiment, the description is relatively simple, and for the relevant parts, reference can be made to the partial description of the page processing method embodiment.
[0152] An embodiment of this specification also provides a computer program product, including computer programs / instructions, and when the computer programs / instructions are executed by a processor, the steps of the above-mentioned page processing method are implemented.
[0153] The above is a schematic solution of a computer program product of this embodiment. It should be noted that the technical solution of this computer program product and the technical solution of the above-mentioned page processing method belong to the same concept. For the details not described in detail in the technical solution of the computer program product, reference can be made to the description of the technical solution of the above-mentioned page processing method.
[0154] The above describes specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the acts or steps recited in the claims may be performed in a different order than in the embodiments and still achieve the desired result. Additionally, the processes depicted in the figures do not necessarily require the particular order or sequential order shown to achieve the desired result. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.
[0155] The computer instructions include computer program code, which may be in source code form, object code form, executable file, or some intermediate form, etc. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, USB flash drive, removable hard disk, magnetic disk, optical disc, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signal, telecommunication signal, and software distribution medium, etc. It should be noted that the content included in the computer-readable medium can be appropriately increased or decreased according to the requirements of patent practice. For example, in some regions, according to patent practice, the computer-readable medium does not include electrical carrier signals and telecommunication signals.
[0156] It should be noted that for the foregoing method embodiments, for the sake of simplicity of description, they are all expressed as a series of action combinations. However, those skilled in the art should know that the embodiments of this specification are not limited by the described order of actions, because according to the embodiments of this specification, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily essential to the embodiments of this specification.
[0157] In the above embodiments, the descriptions of the various embodiments each have their own emphases. For the parts not detailed in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.
[0158] The preferred embodiments of this specification disclosed above are only used to help explain this specification. The alternative embodiments do not detail all the details and do not limit the invention to the specific embodiments described. Obviously, many modifications and variations can be made according to the content of the embodiments of this specification. This specification selects and specifically describes these embodiments to better explain the principles and practical applications of the embodiments of this specification, so that those skilled in the art can well understand and utilize this specification. This specification is only limited by the claims and their full scope and equivalents.
Claims
1. A page processing method, applied to a terminal, comprising: Determine a page generation request, wherein the page generation request carries page attribute information; Determining an initial page including a target module according to the page attribute information, wherein the initial page is a page constructed using the target module and used for human-computer interaction; According to the data acquisition interface of the target module, the target data corresponding to the target module is determined from the data processing unit, and the target page is generated based on the initial page, the target module and the target data.
2. The page processing method according to claim 1, before determining the initial page including the target module according to the page attribute information, further comprising: Determining at least one initial module for constructing the initial page, and determining page configuration information corresponding to the initial page, wherein the page configuration information is used to adjust the at least one initial module; Using the page configuration information, adjusting the initial module identification information, the initial module visualization data, the initial application configuration information, and the initial permission information in the at least one initial module, and obtaining at least one target module including the target module identification information, the target module visualization data, the target application configuration information, and the target permission information; The initial page is constructed using the at least one target module.
3. The page processing method according to claim 2, wherein the step of constructing the initial page using the target module comprises: Determine module position information for the target module, and adjust the position of the target module using the module position information to obtain a page to be instantiated; The page to be instantiated and the target module to be instantiated are instantiated to obtain the initial page, wherein the initial page is an instantiated page instance, and the initial page contains the instantiated target module instance.
4. The page processing method according to any one of claims 1 to 3, after determining the initial page including the target module according to the page attribute information, further comprising: Rendering the initial page to a page display unit corresponding to the terminal; The step of determining target data corresponding to the target module from a data processing unit according to a data acquisition interface of the target module, and generating a target page based on the initial page, the target module and the target data, includes: In response to a data acquisition request for the target module in the initial page, determining a data acquisition interface of the target module, and determining target data corresponding to the target module from a data processing unit corresponding to the target module according to the data acquisition interface; Based on the initial page, the target module and the target data, a target page is generated, and the target page is rendered to the page display unit of the terminal.
5. The page processing method according to claim 4, wherein generating a target page based on the initial page, the target module and the target data comprises: Determine a data display format corresponding to the target module, and based on the data display format, perform data screening on the target data to obtain screened data; The screening data is configured in the target module of the initial page to obtain the target page.
6. The page processing method according to claim 4, wherein the data processing unit is a data processing application program; The step of determining target data corresponding to the target module from a data processing unit corresponding to the target module according to the data acquisition interface includes: Determine a data identifier for the target data, and send the data identifier to a data processing application corresponding to the target module through the data acquisition interface; The target data corresponding to the data identifier is received and returned by the data processing application.
7. The page processing method according to any one of claims 1 to 3, wherein the page generation request carries page attribute information and service information; The step of determining an initial page including a target module according to the page attribute information includes: Performing information verification on the page attribute information and the service information to obtain an information verification result; When the information verification result is that the information verification is passed, the initial page including the target module is obtained from a page storage unit according to the page attribute information and the service information.
8. The page processing method according to any one of claims 1 to 3, wherein the step of determining a page generation request comprises: Receiving a page generation request sent by an interactive device of the terminal, wherein the page generation request is sent by the interactive device when a user performs a page acquisition operation; After generating the target page based on the initial page, the target module and the target data, the method further includes: Render the target page to a page display unit corresponding to the terminal.
9. A computing device comprising: Memory and processor; The memory is used to store computer programs / instructions, and the processor is used to execute the computer programs / instructions. When the computer program / instructions are executed by the processor, the steps of the method according to any one of claims 1 to 8 are implemented.
10. A computer-readable storage medium storing a computer program / instruction, wherein the computer program / instruction, when executed by a processor, implements the steps of the method according to any one of claims 1 to 8.