Cloud product page generation method, device, computer equipment and storage medium

Abstract

The present application relates to a cloud product page generation method, device, computer equipment and storage medium. The method includes: receiving a cloud product page display instruction, the cloud product page display instruction includes an initial access route; obtaining the configuration information of the function page to be converted in the cloud product page entry configuration file; performing information standardization conversion based on the function page configuration information to be converted to obtain the function page standard information, the function page standard information includes the function page standard route and function page generation call information; performing route conversion on the initial access route to obtain the initial function page standard route; searching for the initial function page generation call information corresponding to the initial function page standard route based on the function page standard information; generating a page based on the initial function page generation call information to obtain the cloud product initial function page. The method can improve the generation efficiency of the cloud product page, and the cloud product page can be a cloud server product page.

Description

Technical Field

[0001] The present application relates to the field of Internet technology, and in particular to a method, device, computer equipment and storage medium for generating a cloud product page. Background Art

[0002] With the development of Internet technology, cloud technology has emerged. Cloud technology refers to a hosting technology that unifies hardware, software, network and other resources in a wide area network or local area network to achieve data calculation, storage, processing and sharing. Usually, users manage cloud technology products through cloud product pages. When developing cloud product pages with multiple functions, it is usually necessary to obtain the page corresponding to each function through distributed development and then jump to display through front-end routing. For example, traditional iframe is used as the carrier container of the page, and then each function page is distributedly developed. Then jump to display through front-end routing. However, the method of using iframe as the carrier container of the page for distributed development of the front-end page and then jumping to display through the front-end routing will load all resources associated with all function pages when the cloud product page is initially entered, resulting in a slower speed of generating the initial cloud product page. Summary of the invention

[0003] Based on this, it is necessary to provide a cloud product page generation method, device, computer equipment and storage medium that can improve the efficiency of cloud product page generation in response to the above technical problems.

[0004] A method for generating a cloud product page, the method comprising:

[0005] receiving a cloud product page display instruction, wherein the cloud product page display instruction includes an initial access route;

[0006] Obtain a cloud product page entry configuration file according to the cloud product page display instruction, wherein the cloud product page entry configuration file includes configuration information of the function page to be converted;

[0007] Performing information standardization conversion based on the function page configuration information to be converted to obtain function page standard information, wherein the function page standard information includes a function page standard route and corresponding function page generation call information;

[0008] Convert the initial access route to obtain the standard route of the initial function page;

[0009] Based on the function page standard information, the initial function page corresponding to the standard route of the initial function page is searched to generate call information;

[0010] The function page is generated based on the initial function page generation call information to obtain the initial function page of the cloud product.

[0011] A cloud product page generating device, the device comprising:

[0012] An instruction receiving module, used to receive a cloud product page display instruction, wherein the cloud product page display instruction includes an initial access route;

[0013] A configuration file acquisition module is used to acquire a cloud product page entry configuration file according to a cloud product page display instruction, wherein the cloud product page entry configuration file includes configuration information of a function page to be converted;

[0014] A standard conversion module, used for performing information standardization conversion based on the function page configuration information to be converted, and obtaining the function page standard information, wherein the function page standard information includes the function page standard route and the corresponding function page generation call information;

[0015] The route conversion module is used to convert the initial access route to obtain the standard route of the initial function page;

[0016] A call information search module, used to search for an initial function page corresponding to a standard route of an initial function page based on the function page standard information to generate call information;

[0017] The function page generation module is used to generate the function page based on the initial function page generation call information to obtain the initial function page of the cloud product.

[0018] A computer device comprises a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the following steps are implemented:

[0019] receiving a cloud product page display instruction, wherein the cloud product page display instruction includes an initial access route;

[0020] Obtain a cloud product page entry configuration file according to the cloud product page display instruction, wherein the cloud product page entry configuration file includes configuration information of the function page to be converted;

[0021] Performing information standardization conversion based on the function page configuration information to be converted to obtain function page standard information, wherein the function page standard information includes a function page standard route and corresponding function page generation call information;

[0022] Convert the initial access route to obtain the standard route of the initial function page;

[0023] Based on the function page standard information, the initial function page corresponding to the standard route of the initial function page is searched to generate call information;

[0024] The function page is generated based on the initial function page generation call information to obtain the initial function page of the cloud product.

[0025] A computer-readable storage medium stores a computer program, which, when executed by a processor, implements the following steps:

[0026] receiving a cloud product page display instruction, wherein the cloud product page display instruction includes an initial access route;

[0027] Obtain a cloud product page entry configuration file according to the cloud product page display instruction, wherein the cloud product page entry configuration file includes configuration information of the function page to be converted;

[0028] Performing information standardization conversion based on the function page configuration information to be converted to obtain function page standard information, wherein the function page standard information includes a function page standard route and corresponding function page generation call information;

[0029] Convert the initial access route to obtain the standard route of the initial function page;

[0030] Based on the function page standard information, the initial function page corresponding to the standard route of the initial function page is searched to generate call information;

[0031] The function page is generated based on the initial function page generation call information to obtain the initial function page of the cloud product.

[0032] The above-mentioned cloud product page generation method, device, computer equipment and storage medium obtain a cloud product page entry configuration file according to the cloud product page display instruction when receiving a cloud product page display instruction, the cloud product page entry configuration file includes the function page configuration information to be converted, and then the function page configuration information to be converted is converted to obtain the function page standard information, the function page standard information includes the function page standard route and the corresponding function page generation call information, and then the initial access route is converted to obtain the initial function page standard route, and then the initial function page generation call information corresponding to the initial function page standard route is searched from the function page standard information, and finally the initial function page generation call information is used to generate the function page to obtain the cloud product initial function page, so that when the initial function page is generated, it is only necessary to convert the function page configuration information to be converted to obtain the function page standard information, so that there is no need to load all resources associated with all function pages, which reduces the time of loading the initial function page and improves the generation efficiency of the cloud product page. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] Figure 1 An application environment diagram of a cloud product page generation method in one embodiment;

[0034] Figure 2 A schematic diagram of a process of generating a cloud product page in one embodiment;

[0035] Figure 3 A schematic diagram of a process for determining configuration information of a function page to be converted in one embodiment;

[0036] Figure 4 A schematic diagram of a process of generating a cloud product page in another embodiment;

[0037] Figure 5 This is a schematic diagram of an initial function page in a specific embodiment;

[0038] Figure 6 A schematic diagram of an initial function page in another specific embodiment;

[0039] Figure 7 A schematic diagram of a process for generating a function page menu list in one embodiment;

[0040] Figure 8 A schematic diagram of a flow chart of generating a function page menu list in a specific embodiment;

[0041] Fig. 9 A schematic diagram of a configuration page in a specific embodiment;

[0042] Fig.10 A schematic diagram of a cloud product information configuration page in a specific embodiment;

[0043] Fig.11 A schematic diagram of generating a function page menu list in a specific embodiment;

[0044] Fig.12 A schematic diagram of a process of obtaining a first function page in an embodiment;

[0045] Fig.13 A schematic diagram of a process of obtaining a second function page in one embodiment;

[0046] Fig.14 A schematic diagram of a process of obtaining a third function page in one embodiment;

[0047] Fig.15 A schematic diagram of a process for obtaining standard information of a function page in one embodiment;

[0048] Fig.16 A schematic diagram of a process for obtaining an initial function page of a cloud product in one embodiment;

[0049] Fig.17 A schematic diagram of a process of obtaining an initial function page of a cloud product in a specific embodiment;

[0050] Fig.18 It is a flowchart of a method for generating a cloud product page in a specific embodiment;

[0051] Fig.19 It is a schematic diagram of the architecture of a method for generating a cloud product page in a specific embodiment;

[0052] Fig. 20 A schematic diagram of a cloud product target page in a specific embodiment;

[0053] Fig.21 It is a structural block diagram of a cloud product page generating device in one embodiment;

[0054] Fig. 22 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0055] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0056] The cloud product page generation method provided in this application can be applied to Figure 1In the application environment shown. Among them, the terminal 102 communicates with the server 104 through the network. The terminal 102 receives the cloud product page display instruction, and the cloud product page display instruction includes the initial access route; the terminal 102 obtains the cloud product page entry configuration file from the server 104 according to the cloud product page display instruction, and the cloud product page entry configuration file includes the function page configuration information to be converted; the terminal 102 performs information standardization conversion based on the function page configuration information to be converted to obtain the function page standard information, and the function page standard information includes the function page standard route and the corresponding function page generation call information; the terminal 102 performs route conversion on the initial access route to obtain the initial function page standard route; the terminal 102 searches for the initial function page generation call information corresponding to the initial function page standard route based on the function page standard information; the terminal 102 generates the function page based on the initial function page generation call information to obtain the cloud product initial function page. Among them, the terminal 102 can be, but is not limited to, various personal computers, laptops, smart phones, tablet computers, and portable wearable devices. The server can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers. It can also be a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms. The terminal can be a smart phone, tablet computer, laptop computer, desktop computer, smart speaker, smart watch, etc., but is not limited to this. The terminal and the server can be directly or indirectly connected via wired or wireless communication, and this application does not limit this.

[0057] In one embodiment, Figure 2 As shown, a cloud product page generation method is provided, and the method is applied to Figure 1 The terminal in is used as an example to illustrate, including the following steps:

[0058] Step 202: Receive a cloud product page display instruction, where the cloud product page display instruction includes an initial access route.

[0059] Among them, the cloud product page refers to the page for managing cloud products. The cloud product refers to a cloud service that can be productized, usually including IAAS (Infrastructure as a Service), PAAS (Platform as a Service) and SAAS (Software-as-a-Service). Specific cloud services can be, for example, cloud servers, private networks, load balancing and databases, etc. After productization, they can be provided to users on the cloud platform. The cloud product page display refers to the page that needs to display the cloud product. The cloud product can include multiple cloud service functions, and each cloud service function has a corresponding function page. The initial access route refers to the page route corresponding to the function page entered when the cloud product page is first visited. The front-end page route refers to the route that jumps at the terminal, and there is no need to request the server when jumping to the page.

[0060] Specifically, the user can access the cloud product page by inputting the page location address through the browser. The page access address may be the initial access route, and the page access address may also carry the initial access route. The terminal receives the cloud product page display instruction through the browser, and the cloud product page display instruction includes the initial access route. Among them, the browser refers to an application used to retrieve, display and transmit Web information resources, such as: Baidu Browser, QQ Browser, Firefox Browser, Google Chrome, IE (Internet Explorer) Browser and Sogou Browser, etc. The terminal can also receive the cloud product page display instruction through the cloud platform application, and the cloud product page display instruction includes the initial access route.

[0061] Step 204: Obtain a cloud product page entry configuration file according to the cloud product page display instruction, wherein the cloud product page entry configuration file includes configuration information of the function page to be converted.

[0062] Among them, the function page refers to the page corresponding to each cloud service function in the cloud product. Different cloud service functions have different pages. Function page configuration information refers to the pre-configured configuration information required to generate each function page, such as routing, image resource address, CSS (Cascading Style Sheets) file address, JS (javascript) file address and page component address, etc. The function page configuration information to be converted refers to the function page configuration information that needs to be converted into the function page standard information. The cloud product page entry configuration file is the configuration file obtained when the cloud product page is visited for the first time. The configuration file does not need to be obtained when the cloud product page is visited subsequently.

[0063] Specifically, the terminal downloads a cloud product page entry configuration file from the server according to the cloud product page display instruction, and the cloud product page entry configuration file includes the configuration information of the function page to be converted. In one embodiment, the cloud product page entry configuration file can also be saved in advance to the terminal memory, and the cloud product page entry configuration file is obtained from the memory according to the cloud product page display instruction, and the cloud product page entry configuration file is loaded.

[0064] Step 206 , performing information standardization conversion based on the function page configuration information to be converted, and obtaining function page standard information, wherein the function page standard information includes function page standard routing and corresponding function page generation call information.

[0065] Among them, the configuration information of the function page to be converted includes the native route to be converted and the dependent resources of the function page to be converted. The native route refers to the route obtained by the routing mode different from the standard routing mode used during the development of the function page. The dependent resources of the function page to be converted refer to the resource address on which the function page to be converted depends, which can be a picture resource address, CSS (Cascading Style Sheets) file address, JS (javascript) file address and page component address, etc. Information standardization conversion refers to converting the function page configuration information of each function page to be converted into configuration information in a unified form. The function page standard information refers to the function page configuration information in a unified form, which can be recognized when the page is rendered. The standard route of the function page refers to the unified form of the front-end page route. The function page generation call information refers to the information of calling the dependent resources of the function page.

[0066] Specifically, the terminal performs information standardization conversion on each function page configuration information to be converted, obtains function page standard information corresponding to all function page configuration information to be converted, and saves all function page standard information corresponding to the function page configuration information to be converted into the terminal memory for subsequent use. The function page standard information includes function page standard routing and corresponding function page generation call information.

[0067] Step 208: perform route conversion on the initial access route to obtain the initial function page standard route.

[0068] Specifically, the standard route of the initial function page refers to a unified form of route corresponding to the initial function page.

[0069] When the initial access route needs to be converted to obtain the corresponding initial function page generation call information, the terminal converts the initial access route into a standard route in a unified form according to the preset mapping rule to obtain the initial function page standard route. The preset mapping rule refers to a pre-set rule for converting the front-end page route into a unified route. The initial access route can also be converted into the initial function page standard route using a pre-defined conversion function.

[0070] Step 210 , searching for the initial function page corresponding to the initial function page standard route based on the function page standard information to generate call information.

[0071] The initial function page generation calling information refers to the function page generation calling information corresponding to the initial function page.

[0072] Specifically, the terminal uses the initial function page standard route to match a consistent function page standard route from various function page standard information, and when a consistent function page standard route is found, the function page generation call information corresponding to the consistent function page standard route is used as the initial function page generation call information.

[0073] Step 212: Generate a function page based on the initial function page generation call information to obtain the initial function page of the cloud product.

[0074] Specifically, the terminal generates call information from the server through the initial function page, and then renders the page to generate and display the initial function page of the cloud product.

[0075] The above-mentioned cloud product page generation method, when receiving a cloud product page display instruction, obtains a cloud product page entry configuration file according to the cloud product page display instruction, the cloud product page entry configuration file includes the function page configuration information to be converted, and then performs information standardization conversion on the function page configuration information to be converted to obtain the function page standard information, the function page standard information includes the function page standard route and the corresponding function page generation call information, and then performs route conversion on the initial access route to obtain the initial function page standard route, and then searches for the initial function page generation call information corresponding to the initial function page standard route from the function page standard information, and finally uses the initial function page generation call information to generate the function page to obtain the cloud product initial function page, so that when the initial function page is generated, it is only necessary to perform information standardization conversion on the function page configuration information to be converted to obtain the function page standard information, so that there is no need to load all resources associated with all function pages, which reduces the time of loading the initial function page and improves the generation efficiency of the cloud product page.

[0076] In one embodiment, Figure 3The method further includes: before step S202, that is, before receiving the cloud product page display instruction, wherein the cloud product page display instruction includes the initial access route,

[0077] Step 302: Acquire configuration information of each function page, wherein the configuration information of each function page includes access mode information of each function page.

[0078] Among them, each function page configuration information refers to the function page configuration information corresponding to all function pages of the cloud product. Function page access method information refers to the way the function page accesses the cloud product, which can be JS access, Iframe (html inline frame element, which can be embedded in an external page) access, etc. Among them, access refers to the method used to obtain data from the server. Different function page configuration information can have different function page access method information, or they can have the same function page access method information.

[0079] Specifically, the terminal obtains configuration information of each function page in advance, and the configuration information of each function page includes access mode information of each function page.

[0080] Step 304 : determining the function page configuration information to be converted from each function page configuration information based on each function page access mode information.

[0081] Step 306: Write the function page configuration information to be converted into the cloud product page entry configuration file.

[0082] Specifically, the terminal determines the function page configuration information to be converted from each function page configuration information according to the access method information of each function page. Among them, the function page access method information that needs to convert the corresponding function page configuration information is pre-set. In one embodiment, the function page configuration information to be converted can be determined from each function page configuration information according to the front-end framework used when developing the function page. For example, the function page configuration information using a common framework is the function page configuration information to be converted. The common framework can be a vue framework (a progressive framework for building user interfaces), a React (a JAVASCRIPT library for building user interfaces) framework, and the like. Then, the terminal writes the function page configuration information to be converted into the cloud product page entry configuration file for storage.

[0083] In one embodiment, when the developer completes the development of each function page, the developer will provide the function page configuration information to the development management terminal, and the management personnel will obtain the function page configuration information to configure the cloud product page entry configuration file.

[0084] In the above embodiment, the terminal can determine the function page configuration information to be converted from each function page configuration information based on the access mode information of each function page, thereby obtaining the cloud product page entry configuration file, which is convenient and fast.

[0085] In one embodiment, the cloud product page entry configuration file also includes a function page menu list;

[0086] like Figure 4 As shown, after step S210, that is, after generating a function page based on the initial function page generation call information to obtain the initial function page of the cloud product, it also includes:

[0087] Step 402 , load the function page menu list to obtain the function page menu list; each function page in the function page menu list is developed through different development modes.

[0088] The function page menu list refers to the menu list of each function page corresponding to the cloud product. The function page menu list is pre-configured in the cloud product page entry configuration file. The function page menu list can be a list of function names corresponding to the function page. The development mode refers to the front-end framework used when developing the function page. Each function page is independent, and the various function pages are developed in a distributed manner. Different groups can use different front-end development frameworks to develop function pages, and can use both new and old technology stacks to develop function pages in the cloud product, so that function pages developed with old technologies do not need to be reconstructed.

[0089] Specifically, the terminal loads the function page menu list configured in the cloud product page entry configuration file to obtain the function page menu list.

[0090] In one embodiment, each function page of the cloud product includes function pages of other cloud products. For example, each function page of the cloud server includes function pages of cloud storage and private network, so that users can complete network and storage related operations on a cloud product page, which improves the flexibility of using cloud product pages. For example, CBS (cloud hard disk), which is a cloud-based storage, can also be managed together with cloud server products, that is, some function pages of the cloud hard disk are integrated into the CVM (cloud server) function, so as to achieve management convenience. Each function front-end page of the cloud product is developed by different developers using different technology stacks for sub-modules, and then functional combinations are obtained.

[0091] Step 404: Get the cloud product target page based on the function page menu list and the cloud product initial function page.

[0092] Specifically, the cloud product target page refers to a page including a function page menu list and a cloud product initial function page. The function page menu list may be located on the left side of the cloud product target page, and the cloud product initial function page may be located on the right side of the cloud product target page. In a specific embodiment, Figure 5 As shown, the initial function page of the cloud product is the function 1 page. At this time, the function page menu list is on the left and the function 1 page is on the right. The function page menu list can be located on the upper side of the cloud product target page, and the cloud product initial function page is located on the lower side of the cloud product target page. In a specific embodiment, Figure 6 As shown, the initial function page of the cloud product is the function 1 page. At this time, the function page menu list is on the upper side and the function 1 page is on the lower side. The function page menu list can be located at the lower side of the cloud product target page, and the cloud product initial function page is located at the upper side of the cloud product target page. The function page menu list can be located on the right side of the cloud product target page, and the cloud product initial function page is located on the left side of the cloud product target page. There is no limitation on the position of the function page menu list and the position of the cloud product initial function page in the cloud product target page, as long as the position of the function page menu list does not overlap with the position of the cloud product initial function page. Users can enter the corresponding function page by clicking on a function page in the function page menu list.

[0093] In the above embodiment, by loading the function page menu list, and then obtaining the cloud product target page based on the function page menu list and the cloud product initial function page, it is convenient for users to use and improves efficiency.

[0094] In one embodiment, Figure 7 As shown, before step S202, that is, before receiving the cloud product page display instruction, the cloud product page display instruction includes the initial access route, and further includes:

[0095] Step 702: Acquire configuration information of each function page, wherein the function page configuration information includes a function page access route.

[0096] The function page access route refers to the front-end page route used when accessing the function page. The form of the function page access route may be consistent with the form of the standard route, or may be inconsistent with the form of the standard route.

[0097] Specifically, the terminal obtains configuration information of each function page, and the function page configuration information includes a function page access route.

[0098] Step 704: Combine the access routes of the various function pages to obtain a cloud product combination route.

[0099] Combining refers to splicing the access routes of various function pages. The cloud product combined route refers to the route information obtained by splicing the access routes of various function pages of the cloud product.

[0100] Specifically, the terminal sequentially splices the access routes of each function page, and the spliced ​​route information is the cloud product combination route. The cloud product combination route can be directly spliced ​​to obtain the access routes of each function page, or the access routes of each function page can be sequentially spliced ​​after being separated by a preset spacing character, and so on.

[0101] Step 706, obtain the basic function page menu list and the cloud product identifier, generate the function page menu list according to the cloud product identifier, the cloud product combination route and the basic function page menu list, and write the function page menu list into the cloud product page entry configuration file.

[0102] The basic function page menu list refers to a pre-set function page menu list template. The function page menu list template includes the function name corresponding to each function page. The cloud product identifier is used to identify the cloud product and can be the name of the cloud product.

[0103] Specifically, the terminal obtains the basic function page menu list and the cloud product identifier, associates each function page access route in the cloud product combination route with the function name in the basic function page menu list, thereby generating a function page menu list, and then writes the function page menu list into the cloud product page entry configuration file.

[0104] In a specific embodiment, Figure 8 The following is a logical diagram of generating a menu list of function pages. Specifically, users can Fig. 9The configuration information shown configures the configuration information of each function page, such as routing key, product name, access method, routing information, etc. Among them, the vmm front-end page module is developed using Tencent Cloud's tea1 framework, such as host management, image management and other front-end page modules. The vmmoss front-end page module is developed using Tencent Cloud's old bee.js framework. The prm front-end page module is developed using traditional php, jquery and other technology stacks, and uses iframe for combined access, such as the operation and maintenance management front-end page module. The hosttype front-end page is reconstructed and developed using the new tea2 framework, such as the log link front-end page. That is, a cloud product is obtained by combining multiple function pages developed separately. Then, after the configuration is completed, the terminal associates each function page with the corresponding resources. For example, the function page accessed by iframe can be associated with an accessible page address, and the function page accessed by js can be associated with an independent js or a large js resource that is packaged with js, css resources, and image resources. The function page accessed by hash routing can be associated with a series of on-demand loading of js, css and other resource information. In fact, there can be more framework access methods. Generate configuration information and generate configuration information for each function page. At the same time, the access routes of each function page are combined to obtain the cloud product combination route. Then, we get Fig.10 The cloud product information configuration page shown in the figure shows the cloud product combination route. The cloud product version ID, i.e., uuid, can also be displayed. Users can edit the name of the cloud product, such as Cloud Virtual Machine (CVM). Then, the basic function page menu list can be referenced to generate a function page menu list associated with each access route. Each function page in the function page menu list can have a corresponding menu list. Figure 8 The menu list corresponding to the function page of accessing route 1, and the menu list corresponding to the function page of accessing route 2, etc. The schematic diagram of the function page menu list of the generated cloud server product is as follows Fig.11 As shown. The function page menu list can be edited and modified. Finally, the function page menu list is written into the cloud product page entry configuration file. This allows the technology stack used in the development of the same cloud product to be gradually iterated, with new and old technology stacks coexisting and multiple technology stacks coexisting, so that all reconstructions do not need to be done at once, which improves the reconstruction efficiency of large cloud products.

[0105] In one embodiment, Fig.12 As shown, after step 404, that is, after obtaining the cloud product target page based on the function page menu list and the cloud product initial function page, the following steps are also included:

[0106] Step 1202: Receive a first function page display instruction triggered by a function page menu list, where the first function page display instruction carries a first function page route.

[0107] Among them, the first function page refers to the function page corresponding to the first cloud service function in the function page menu list. The first function page route refers to the route corresponding to the first function page. The first function page route is not a unified form of routing and requires routing conversion. That is, the first function page corresponding to the first function page route is established using a front-end general framework. The front-end general framework can be a vue framework, a vue-router framework, a react framework, a react-router framework, and so on. The first function page can be, for example, a page developed based on the browser-hash routing mode of the browser. Or a page developed based on the browser-history routing mode of the browser.

[0108] Specifically, when the user clicks on the first cloud service function name in the function page menu list, the terminal obtains the associated first function page route according to the cloud service function name, and then triggers the first function page display instruction.

[0109] Step 1204: Convert the first function page route into the first function page standard route according to a preset mapping rule.

[0110] The preset mapping rule refers to a preset rule for converting a function page route into a function page standard route. In a specific embodiment, the preset mapping rule may be converted according to the string after the last " / " in modules / function page route / function page route. For example, if the first function page route is / controller / action, the converted first function page standard route is "module / controller / action / action".

[0111] Specifically, the terminal converts the first function page route into the first function page standard route according to the preset mapping rule. The terminal may also call a preset conversion function to perform the conversion.

[0112] Step 1206 , searching for the first function page corresponding to the first function page standard route based on the function page standard information to generate call information.

[0113] The first function page generation calling information refers to information that needs to be called when generating the first function page.

[0114] Specifically, the terminal searches for a function page standard route that is consistent with the first function page standard route in each function page standard information, and when a consistent function page standard route is found, the function page generation call information corresponding to the function page standard route is used as the first function page generation call information.

[0115] Step 1208: Generate the first function page based on the first function page generation calling information to obtain the first function page.

[0116] Specifically, the terminal uses the first function page to generate call information to call the dependent front-end resources, dynamically creates the page component mounting point div of the first function page, and then searches for the corresponding mapping match according to the first function page route in the call information generated by the first function page to obtain the first function page routing framework. The first function page routing framework calls its own rendering function to render the page component into the page component mounting point div, thereby displaying the first function page.

[0117] In the above embodiment, when it is necessary to view other function pages, the first function page display instruction is triggered, and then the first function page route is converted into the first function page standard route according to the preset mapping rule, and the first function page corresponding to the first function page standard route is searched based on the function page standard information to generate the call information, and the first function page is generated based on the first function page generation call information to obtain the first function page, which can realize the display of the first function page and is convenient to use.

[0118] In one embodiment, Fig.13 As shown, after step 404, that is, after obtaining the cloud product target page based on the function page menu list and the cloud product initial function page, the following further includes:

[0119] Step 1302: Receive a second function page display instruction triggered by the function page menu list, where the second function page display instruction carries a second function page route, and the second function page route is a second function page standard route.

[0120] The second function page refers to the function page corresponding to the second cloud service function in the function page menu list. The second function page route refers to the route corresponding to the second function page. The second function page route is the standard route of the second function page. That is, the second function page is developed using a front-end framework that defines routes according to standard routing specifications.

[0121] Specifically, when the user clicks on the second cloud service function name in the function page menu list, the terminal obtains the associated second function page route according to the second cloud service function name, and then triggers the first function page display instruction.

[0122] Step 1304, obtaining the second function page generation calling information corresponding to the second function page standard route; the second function page standard route and the second function page generation calling information are written into the page implementation code.

[0123] Among them, writing the page implementation code means that when developing the second function page, the standard route of the second function page is written according to the standard routing specification and the second function page generates call information to obtain the front-end implementation code corresponding to the second function page, and then the front-end implementation code is packaged for use.

[0124] Specifically, the terminal obtains the second function page generation call information corresponding to the second function page standard route from the server, that is, downloads the front-end implementation code of the second function page from the server through the second function page standard route. The front-end implementation code includes the second function page generation call information.

[0125] Step 1306: Generate the second function page based on the second function page generation calling information to obtain the second function page.

[0126] Specifically, the terminal uses the second function page to generate call information to call the dependent front-end resources, dynamically creates the page component mounting point div of the second function page, and calls the front-end component to render the front-end component into the page component mounting point div, thereby displaying the second function page.

[0127] In one embodiment, the initial access route may also be the initial access standard route, that is, the function page for entering the cloud product for the first time is developed using a front-end framework that defines the route according to the standard route specification. Then, the initial function page generation call information corresponding to the initial function page standard route is obtained; the initial function page standard route and the initial function page generation call information are written into the page implementation code, and the initial function page is generated based on the initial function page generation call information to obtain the initial function page.

[0128] In the above embodiment, the standard route of the second function page and the second function page generation call information are written into the page implementation code, which is convenient for users to use. At the same time, developers can perform distributed development when developing pages. Different function pages are developed using different front-end frameworks, which also improves the page development efficiency of developers.

[0129] In one embodiment, Fig.14 As shown, after step 404, after obtaining the cloud product target page based on the function page menu list and the cloud product initial function page, it also includes:

[0130] Step 1402: Receive a third function page display instruction triggered by the function page menu list, where the third function page display instruction carries a third function page route.

[0131] Among them, the third function page refers to the function page corresponding to the third cloud service function in the function page menu list. The third function page route refers to the route corresponding to the third function page. The third function page is a function page developed using a front-end framework with custom routing rules. The front-end framework with custom routing rules can be the tea1 framework (Tencent Cloud front-end framework), or it can be the tea2 framework (Tencent Cloud front-end framework), etc. The tea framework (two versions, tea1 and tea2) is a front-end technology framework developed by Tencent Cloud, which usually encapsulates some common basic components and development specifications.

[0132] Step 1404, based on the third function page route, the associated page generation resource information is obtained, wherein the page generation resource information includes third function page standard information; the third function page standard information is obtained by converting the third function page configuration information into standard information during compilation of the page generation resource information.

[0133] The page generation resource information refers to the resource information required to generate the third function page, for example, it is associated with an independent js file or a large js file that is packaged with js, css, and image resources. The page generation resource information includes the third function page standard information obtained by converting the third function page configuration information into information standardization during compilation. The third function page standard information refers to the function page standard information corresponding to the third function page.

[0134] Specifically, the terminal downloads the associated page generation resource information from the server according to the third function page route, and obtains the third function page standard information from the page generation resource information.

[0135] Step 1406, determining the third function page generation calling information from the third function page standard information; generating the third function page based on the third function page generation calling information to obtain the third function page.

[0136] Specifically, the terminal determines the third function page generation call information from the third function page standard information, the terminal uses the third function page generation call information to call the dependent front-end resources, dynamically creates the page component mounting point div of the third function page, and then searches for the corresponding mapping match according to the third function page routing in the third function page generation call information to obtain the third function page routing framework. The third function page routing framework calls its own rendering function to render the page component into the page component mounting point div, thereby displaying the third function page.

[0137] In one embodiment, the initial function page standard information is obtained by converting the initial function page configuration information into information standardization when the initial function page generates resource information. That is, the function page for entering the cloud product for the first time is a page developed using a front-end framework with custom routing rules, and then the custom routing rules are converted into the initial function page standard information when compiling. Then, according to the initial access route, the associated initial function page generation resource information is downloaded from the server to obtain the initial function page standard information in the initial function page generation resource information, and then the initial function page generation call information in the initial function page standard information is obtained; the initial function page is generated based on the initial function page generation call information to obtain the initial function page.

[0138] In the above embodiment, the terminal realizes the display of the third function page, which is convenient for users to use, and at the same time enables developers to perform distributed development when developing pages. Different function pages are developed using different front-end frameworks, which also improves the page development efficiency of developers.

[0139] In one embodiment, the configuration information of the function page to be converted includes an access route, a dependent resource identifier, and a mount point identifier of the function page to be converted;

[0140] like Fig.15 As shown, step 210, based on the function page configuration information to be converted, information standardization conversion is performed to obtain function page standard information, including:

[0141] Step 1502: Convert the access route of the function page to be converted into a standard route of the function page according to a preset mapping rule.

[0142] Among them, the preset mapping rule refers to the pre-set rule for converting the function page access route into the function page standard route. The converted function page access route refers to the access route of the function page that needs to be converted. The dependent resource identifier is used to identify the resource for generating the function page, which can be a picture address, js file address, css file address, etc. The mount point identifier is used to identify the mount point div in the page (div is the positioning technology in the cascading style sheet, the full name is DIVision). The terminal converts the access route of the function page to be converted in the configuration information of the function page to be converted into the standard route of the function page according to the preset mapping rule.

[0143] Step 1504: Generate corresponding call information based on the access route of the function page to be converted, the dependent resource identifier and the mount point identifier.

[0144] The call information refers to the information generated by using the function page to be converted to access the route call dependent resources and mounting points, which can be implemented using a callback function.

[0145] Specifically, the terminal generates corresponding call information according to the access route of the function page to be converted, the dependent resource identifier and the mount point identifier according to the pre-set function page standard information generation specification.

[0146] Step 1506, obtaining the function page standard information according to the function page standard routing and calling information.

[0147] Specifically, the terminal associates and saves the function page standard route and the calling information to obtain the function page standard information.

[0148] In a specific embodiment, the generated function page standard information refers to a generated unified routing mode based on the definition of the sea.js module. The unified routing mode is defined as follows:

[0149] Function page standard information ('Function page standard route',

[0150] callback function (dependency resource, export, component) {

[0151] Implementation of specific callback function

[0152] })

[0153] Among them, the sea.js module is a JavaScript module loading framework that complies with the CMD specification and can implement JavaScript modular development and loading mechanism.

[0154] For example:

[0155] define('module / controller / action / action',

[0156] function(require,exports,module){

[0157] })

[0158] Among them, define refers to the generated function page standard information, module / controller / action / action refers to the function page standard route corresponding to the access route / controller / action. function(require,exports,module) refers to the callback function, require refers to the dependent resource parameters, exports export parameters, and module refers to the component parameters. The terminal dynamically creates each function page standard information corresponding to each function page configuration information to be converted, saves each function page standard information in memory, and when accessed through the function page menu list, loads the function page standard information for page generation.

[0159] In the above embodiment, the access route of the function page to be converted is converted into the standard route of the function page, and then the corresponding call information is generated based on the access route of the function page to be converted, the dependent resource identifier and the mount point identifier, so as to obtain the standard information of the function page. When the function page is initially accessed, it is not necessary to load the resource information of all function pages when loading. Only the standard information of the function page needs to be generated and saved. Then, when the function page is accessed, the standard information of the function page is loaded to generate the page, thereby improving the efficiency of page display.

[0160] In one embodiment, Fig.16 As shown, step 212, i.e., generating a function page based on the initial function page generation call information to obtain the cloud product initial function page, includes:

[0161] Step 1602: Load the function page dependent resources according to the dependent resource identifier in the initial function page generation call information, and create the initial function page mount point according to the mount point identifier in the initial function page generation call information.

[0162] Step 1604, calling the initial function page component according to the initial function page access route in the initial function page generation call information, and rendering the function page component to the initial function page mounting point to obtain the cloud product initial function page.

[0163] The initial function page component refers to the web page component used to generate the initial function page. The web page component includes various commonly used interface components, such as tables, trees, linked drop-down boxes, etc., which can easily construct a refreshing Web application interface with RIA (Rich Internet Application) characteristics. The initial function page mount point refers to the mount point div on the initial function page.

[0164] Specifically, the terminal loads the dependent resources of the function page according to the dependent resource identifier in the call information generated by the initial function page, and dynamically creates the initial function page mount point according to the mount point identifier in the call information generated by the initial function page, and then the initial function page access routing framework corresponding to the initial function page access routing performs rendering work, that is, calling the initial function page component through the initial function page access routing, and rendering the initial function page component to the initial function page mount point, so as to realize the display of the initial function page of the cloud product. Among them, it is also possible to render by calling the rendering function of the corresponding framework, and mount the converted DOM (document object model) information on the div node of the content container, so as to display the initial function page of the cloud product.

[0165] In the above embodiment, the initial function page is generated by generating call information to realize the generation of the initial function page of the cloud product, thereby ensuring the accuracy of the page generation.

[0166] In a specific embodiment, Fig.17 As shown in the figure, a schematic diagram of the process of generating an initial function page of a cloud product is provided, specifically:

[0167] When the initial access route is used to access the initial function page of the cloud product, the entry configuration file is downloaded from the server, and the resource information and route mapping configuration information in the entry configuration file are configured. The relevant sea.js module is dynamically created according to the access route configuration information of the function page to be converted in the route mapping configuration information, that is, the standard information of each function page is obtained and saved. Then the standard information of the function page corresponding to the initial function page of the cloud product is obtained, that is, the corresponding sea.js module is found and executed according to the initial access route. When the sea.js module is executed, the dependent resources are first loaded and the mounting point div of the page component is dynamically created. Then the corresponding mapping match is found from the route mapping configuration information, that is, the page implementation framework corresponding to the initial access route is used to execute the page rendering process, that is, the rendering function is called to render the page component to the created page component mounting point div, thereby realizing the generation of the initial function page.

[0168] In a specific embodiment, Fig.18 As shown, the cloud product page generation method includes the following steps:

[0169] 1802, receiving a cloud product page display instruction, the cloud product page display instruction including an initial access route. Obtaining a cloud product page entry configuration file according to the cloud product page display instruction, the cloud product page entry configuration file including configuration information of the function page to be converted and a function page menu list, the function page to be converted configuration information including an access route of the function page to be converted, a dependent resource identifier, and a mount point identifier.

[0170] 1804, load the function page menu list to obtain the function page menu list. Each function page in the function page menu list is developed through different development modes.

[0171] 1806. Convert the access route of the function page to be converted into the standard route of the function page according to the preset mapping rules, generate corresponding call information based on the access route of the function page to be converted, the dependent resource identifier and the mount point identifier, and obtain the standard information of the function page according to the standard route of the function page and the call information.

[0172] 1808, perform route conversion on the initial access route to obtain the initial function page standard route, and search the function page standard information for the initial function page corresponding to the initial function page standard route to generate call information.

[0173] 1810 , load the function page dependent resources according to the dependent resource identifier in the initial function page generation call information, and create the initial function page mount point according to the mount point identifier in the initial function page generation call information.

[0174] 1812, calling the initial function page component according to the initial function page access route in the initial function page generation call information, and rendering the initial function page component to the initial function page mounting point to obtain the cloud product initial function page.

[0175] 1814. Obtain a cloud product target page based on the function page menu list and the cloud product initial function page.

[0176] Then, users can also generate function pages by triggering other cloud service functions in the function page menu list. Specifically:

[0177] The terminal can receive a first function page display instruction triggered by a function page menu list, the first function page display instruction carrying a first function page route; convert the first function page route into a first function page standard route according to a preset mapping rule; search for the first function page generation call information corresponding to the first function page standard route based on the function page standard information; generate the first function page based on the first function page generation call information to obtain the first function page.

[0178] The terminal can also receive a second function page display instruction triggered by a function page menu list, the second function page display instruction carries a second function page route, and the second function page route is a second function page standard route; obtain the second function page generation call information corresponding to the second function page standard route; the second function page standard route and the second function page generation call information are written into the page implementation code; the second function page is generated based on the second function page generation call information to obtain the second function page.

[0179] The terminal can also receive a third function page display instruction triggered by a function page menu list, the third function page display instruction carries a third function page route, and obtains associated page generation resource information based on the third function page route, the page generation resource information includes third function page standard information; the third function page standard information is obtained by converting the third function page configuration information into information standardization during compilation of the page generation resource information; determining the third function page generation call information from the third function page standard information; generating the third function page based on the third function page generation call information to obtain the third function page.

[0180] The present application also provides an application scenario, which applies the above-mentioned cloud product page generation method. Specifically, the application of the cloud product page generation method in the application scenario is as follows:

[0181] The cloud product page generation method is applied to the Tencent cloud platform, such as Fig.19 The following is a schematic diagram of the architecture of the cloud product page generation method. Specifically:

[0182] The architecture of the cloud product page generation method includes three parts, namely, the page rendering part, the routing bridging part and the native business module routing part.

[0183] Among them, the routing part of the native business module refers to the front-end page module developed using various front-end technologies. For example, the front-end page module implemented by general front-end frameworks such as vue, vue-router, react, and react-router. For example, the front-end page module developed using the Tencent Cloud framework can be developed based on the tea1 framework or tea2 framework, and the routing mode is basically a custom routing mode. For example, the front-end page module developed using other niche front-end routing frameworks in the industry can directly define the routing according to the specifications of the unified routing mode.

[0184] The routing bridge part refers to the routing conversion of the front-end page modules developed using multiple routing modes, and converts them into a unified routing mode defined based on the sea.js module that can be recognized by the page rendering part. Among them, runtime dynamic conversion refers to the conversion on the front end when entering the cloud product page for the first time. Compile-time conversion refers to the conversion of the routing mode through a custom front-end compilation plug-in when the front-end page resources are packaged and compiled. Direct conversion refers to defining the routing directly according to the specifications of the unified routing mode when developing the front-end page.

[0185] The page rendering part is mainly to render the page associated with the route to generate the page. Its basic logic is that when the user enters the initial access route through the browser to access the cloud product page, the entry configuration file is downloaded from the server, and the resource information configuration, route mapping configuration information and function page menu list in the entry configuration file are configured. The function page menu list is loaded to obtain the function page menu list, and the relevant sea.js module is dynamically created according to the function page access route configuration information to be converted in the route mapping configuration information, that is, the standard information of each function page is obtained and saved. Then the function page standard information corresponding to the initial function page of the cloud product is obtained, that is, the corresponding sea.js module is found and executed according to the initial access route. When the sea.js module is executed, it first loads the dependent resources and dynamically creates the mount point div of the page component. Then the corresponding mapping match is found from the route mapping configuration information, that is, the page corresponding to the initial access route is used to implement the framework to execute the page rendering process, that is, the rendering function is called to render the page component into the created page component mount point div, thereby realizing the generation of the initial function page. Then the function page menu list and the initial function page are displayed, that is, the cloud product target page is displayed. For example, the cloud product target page displayed is as follows Fig. 20 As shown, this page is the management page of the cloud server product, wherein the cloud server product list includes cloud server specification definition products, cloud host (tenant resources) products, cloud host (platform resources) products, image management products, operation and maintenance management products, virtualization platform status products, link log product pages and model configuration products. The initial function page is the cloud server specification definition product page. Among them, some products can include different functional product pages. For example, image management products and operation and maintenance management products. In one embodiment, the list can also include some functional products of CBS (cloud storage) and VPC (private network).

[0186] Then, when the terminal receives the user's click on the cloud host (tenant resource) product in the function page menu list of the cloud server product, the terminal obtains the front-end page route of the associated cloud host (tenant resource) product, triggers the page display instruction corresponding to the cloud host (tenant resource) product, and converts the route of the cloud host (tenant resource) product front-end page into the standard route of the cloud host (tenant resource) product front-end page according to the preset mapping rule, searches for the cloud host (tenant resource) product front-end page standard route based on the function page standard information, generates the cloud host (tenant resource) product front-end page call information, generates the cloud host (tenant resource) product front-end page based on the cloud host (tenant resource) product front-end page call information, and obtains the cloud host (tenant resource) product front-end page.

[0187] Then, when the terminal receives the user's click on the virtualization platform status product in the function page menu list of the cloud server product, the terminal obtains the front-end page route of the associated virtualization platform status product, triggers the page display instruction corresponding to the virtualization platform status product, and the front-end page route of the virtualization platform status product is the standard route. The front-end page generation call information of the corresponding virtualization platform status product is obtained from the server according to the front-end page route of the virtualization platform status product, and the front-end page of the virtualization platform status product is generated based on the front-end page generation call information of the virtualization platform status product to obtain the front-end page of the virtualization platform status product.

[0188] Then, the terminal receives a signal that the user clicks on a model configuration product in the function page menu list of the cloud server product, and the terminal obtains the front-end page route of the associated model configuration product, triggers a page display instruction corresponding to the model configuration product, and obtains the associated page generation resource information based on the front-end page route of the model configuration product, wherein the page generation resource information includes the front-end page standard information of the model configuration product; the front-end page standard information of the model configuration product is obtained by performing information standardization conversion on the front-end page configuration information of the model configuration product during compilation of the page generation resource information, and the generation call information of the front-end page of the model configuration product is determined from the front-end page standard information of the model configuration product, and the front-end page of the model configuration product is generated based on the front-end page generation call information of the model configuration product to obtain the front-end page of the model configuration product.

[0189] Then, the terminal receives the user's click on the operation and maintenance management product in the menu list of the function page of the cloud server product. The operation and maintenance management product page is combined and accessed using an iframe framework, so the terminal obtains the front-end page address of the associated operation and maintenance management product and generates an embedded operation and maintenance management product page.

[0190] It should be understood that although Figure 1-4 , Figure 7 , Figure 12-16 and Fig.18 The steps in the flowchart are shown in sequence as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified in this document, there is no strict order restriction for the execution of these steps, and these steps can be executed in other orders. Moreover, Figure 1-4 , Figure 7 , Figure 12-16 and Fig.18At least part of the steps may include multiple steps or multiple stages. These steps or stages are not necessarily performed at the same time, but can be performed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed in turn or alternately with other steps or at least part of the steps or stages in other steps.

[0191] In one embodiment, Fig.21 As shown, a cloud product page generation device 2100 is provided. The device can adopt a software module or a hardware module, or a combination of the two to become a part of a computer device. The device specifically includes: an instruction receiving module 2102, a configuration file acquisition module 2104, a standard conversion module 2106, a routing conversion module 2108, a call information search module 2110 and a function page generation module 2112, wherein:

[0192] The instruction receiving module 2102 is used to receive a cloud product page display instruction, where the cloud product page display instruction includes an initial access route;

[0193] The configuration file acquisition module 2104 is used to acquire a cloud product page entry configuration file according to the cloud product page display instruction, wherein the cloud product page entry configuration file includes configuration information of the function page to be converted;

[0194] The standard conversion module 2106 is used to perform information standardization conversion based on the function page configuration information to be converted, and obtain the function page standard information, wherein the function page standard information includes the function page standard route and the corresponding function page generation call information;

[0195] The route conversion module 2108 is used to convert the initial access route to obtain the initial function page standard route;

[0196] The calling information searching module 2110 is used to search the initial function page corresponding to the standard route of the initial function page based on the function page standard information to generate the calling information;

[0197] The function page generation module 2112 is used to generate a function page based on the initial function page generation call information to obtain the initial function page of the cloud product.

[0198] In one embodiment, the device further comprises:

[0199] The module for determining information to be converted is used to obtain configuration information of each function page, wherein each function page configuration information includes access method information of each function page; determine the function page configuration information to be converted from each function page configuration information based on the access method information of each function page; and write the function page configuration information to be converted into the cloud product page entry configuration file.

[0200] In one embodiment, the cloud product page entry configuration file also includes a function page menu list; the device also includes:

[0201] List loading module, used to load the function page menu list to obtain the function page menu list; each function page in the function page menu list is developed through different development modes;

[0202] The target page obtaining module is used to obtain the cloud product target page based on the function page menu list and the cloud product initial function page.

[0203] In one embodiment, the device further comprises:

[0204] The list generation module is used to obtain the configuration information of each function page, which includes the function page access route; combine the various function page access routes to obtain the cloud product combination route; obtain the basic function page menu list and the cloud product identifier, generate the function page menu list according to the cloud product identifier, the cloud product combination route and the basic function page menu list, and write the function page menu list into the cloud product page entry configuration file.

[0205] In one embodiment, the device further comprises:

[0206] A first instruction receiving module, used to receive a first function page display instruction triggered by the function page menu list, the first function page display instruction carrying a first function page route;

[0207] A first route conversion module, used to convert the first function page route into a first function page standard route according to a preset mapping rule;

[0208] A first information search module, used for searching for a first function page corresponding to a first function page standard route based on the function page standard information to generate call information;

[0209] The first page generation module is used to generate the first function page based on the first function page generation calling information to obtain the first function page.

[0210] In one embodiment, the device further comprises:

[0211] A second instruction receiving module, used to receive a second function page display instruction triggered by the function page menu list, the second function page display instruction carries a second function page route, and the second function page route is a second function page standard route;

[0212] The second information search module is used to obtain the second function page generation call information corresponding to the second function page standard route; the second function page standard route and the second function page generation call information are written into the page implementation code;

[0213] The second page generation module generates the second function page based on the second function page generation calling information to obtain the second function page.

[0214] In one embodiment, the device further comprises:

[0215] A third instruction receiving module, used to receive a third function page display instruction triggered by the function page menu list, the third function page display instruction carrying a third function page route;

[0216] A resource information acquisition module, used for acquiring the associated page generation resource information based on the third function page route, wherein the page generation resource information includes the third function page standard information; the third function page standard information is obtained by converting the third function page configuration information into information standardization when the page generation resource information is compiled;

[0217] The third page generation module is used to determine the third function page generation calling information from the third function page standard information; generate the third function page based on the third function page generation calling information to obtain the third function page.

[0218] In one embodiment, the configuration information of the function page to be converted includes an access route, a dependent resource identifier, and a mount point identifier of the function page to be converted;

[0219] The standard conversion module 2106 is also used to convert the access route of the function page to be converted into the standard route of the function page according to the preset mapping rules; generate corresponding call information based on the access route of the function page to be converted, the dependent resource identifier and the mount point identifier; and obtain the standard information of the function page according to the standard route of the function page and the call information.

[0220] In one embodiment, the function page generation module 2112 is further used to load the function page dependent resources according to the dependent resource identifier in the initial function page generation call information, and to create the initial function page mount point according to the mount point identifier in the initial function page generation call information;

[0221] The initial function page component is called according to the initial function page access route in the initial function page generation call information, and the initial function page component is rendered to the initial function page mounting point to obtain the cloud product initial function page.

[0222] For the specific definition of the cloud product page generation device, please refer to the definition of the cloud product page generation method above, which will not be repeated here. Each module in the above-mentioned cloud product page generation device can be implemented in whole or in part by software, hardware and a combination thereof. The above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.

[0223] In one embodiment, a computer device is provided. The computer device may be a terminal, and its internal structure diagram may be as follows: Fig. 22 As shown. The computer device includes a processor, a memory, a communication interface, a display screen and an input device connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner can be achieved through WIFI, an operator network, NFC (near field communication) or other technologies. When the computer program is executed by the processor, a cloud product page generation method is implemented. The display screen of the computer device can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer covered on the display screen, or a button, trackball or touchpad set on the computer device housing, or an external keyboard, touchpad or mouse.

[0224] Those skilled in the art will understand that Fig. 22 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0225] In one embodiment, a computer device is further provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the steps in the above method embodiments when executing the computer program.

[0226] In one embodiment, a computer-readable storage medium is provided, storing a computer program, which implements the steps in the above method embodiments when executed by a processor.

[0227] In one embodiment, a computer program product or computer program is provided, the computer program product or computer program includes computer instructions, the computer instructions are stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device performs the steps in the above-mentioned method embodiments.

[0228] Those of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory or optical memory, etc. Volatile memory can include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM).

[0229] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0230] The above-mentioned embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the invention patent. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the patent of the present application shall be subject to the attached claims.

Claims

1. A method for generating a cloud product page, characterized in that: The method comprises: Receiving a cloud product page display instruction, wherein the cloud product page display instruction includes an initial access route; Obtaining a cloud product page entry configuration file according to the cloud product page display instruction, wherein the cloud product page entry configuration file includes configuration information of the function page to be converted, wherein the configuration information of the function page to be converted includes the native route to be converted and the dependent resources of the function page to be converted, wherein the dependent resources of the function page to be converted refer to resource addresses on which the function page to be converted is dependent; Performing information standardization conversion based on the function page configuration information to be converted to obtain function page standard information, wherein the function page standard information includes a function page standard route and corresponding function page generation call information; Perform route conversion on the initial access route to obtain a standard route for the initial function page; Searching for the initial function page corresponding to the initial function page standard route based on the function page standard information to generate call information; A function page is generated based on the initial function page generation call information to obtain an initial function page of the cloud product.

2. The method according to claim 1, characterized in that In the step of receiving the cloud product page display instruction, before the cloud product page display instruction includes the initial access route, the step further includes: Acquire configuration information of each function page, wherein the configuration information of each function page includes access mode information of each function page; Determining the function page configuration information to be converted from the function page configuration information based on the access mode information of each function page; The function page configuration information to be converted is written into the cloud product page entry configuration file.

3. The method according to claim 1, characterized in that: The cloud product page entry configuration file also includes a function page menu list; After generating a function page based on the initial function page generation call information to obtain the cloud product initial function page, the method further includes: Loading the function page menu list to obtain the function page menu list; each function page in the function page menu list is developed through different development modes; A cloud product target page is obtained based on the function page menu list and the cloud product initial function page.

4. The method according to claim 3, characterized in that In the step of receiving the cloud product page display instruction, before the cloud product page display instruction includes the initial access route, the step further includes: Obtaining configuration information of each function page, wherein the configuration information of each function page includes a function page access route; Combine the access routes of each functional page to obtain the cloud product combination route; Obtain a basic function page menu list and a cloud product identifier, generate the function page menu list according to the cloud product identifier, the cloud product combination route and the basic function page menu list, and write the function page menu list into the cloud product page entry configuration file.

5. The method according to claim 3, characterized in that: After obtaining the cloud product target page based on the function page menu list and the cloud product initial function page, the method further includes: receiving a first function page display instruction triggered by the function page menu list, wherein the first function page display instruction carries a first function page route; Converting the first function page route into a first function page standard route according to a preset mapping rule; Searching for a first function page corresponding to the first function page standard route based on the function page standard information to generate call information; A first function page is generated based on the first function page generation calling information to obtain a first function page.

6. The method according to claim 3, characterized in that After obtaining the cloud product target page based on the function page menu list and the cloud product initial function page, the method further includes: receiving a second function page display instruction triggered by the function page menu list, wherein the second function page display instruction carries a second function page route, and the second function page route is a second function page standard route; Obtaining the second function page generation call information corresponding to the second function page standard route; the second function page standard route and the second function page generation call information are written into the page implementation code; The second function page is generated based on the second function page generation calling information to obtain the second function page.

7. The method according to claim 3, characterized in that After obtaining the cloud product target page based on the function page menu list and the cloud product initial function page, the method further includes: receiving a third function page display instruction triggered by the function page menu list, wherein the third function page display instruction carries a third function page route; Acquire the associated page generation resource information based on the third function page route, wherein the page generation resource information includes the third function page standard information; the third function page standard information is obtained by performing information standardization conversion on the third function page configuration information when the page generation resource information is compiled; Determine the third function page generation calling information from the third function page standard information; The third function page is generated based on the third function page generation calling information to obtain the third function page.

8. The method according to claim 1, characterized in that The configuration information of the function page to be converted includes an access route, a dependent resource identifier and a mount point identifier of the function page to be converted; The performing information standardization conversion based on the function page configuration information to be converted to obtain function page standard information includes: Convert the access route of the function page to be converted into a standard route of the function page according to a preset mapping rule; Generate corresponding call information based on the access route of the function page to be converted, the dependent resource identifier and the mount point identifier; The function page standard information is obtained according to the function page standard route and the calling information.

9. The method according to claim 1, characterized in that: The generating of the function page based on the initial function page generation call information to obtain the cloud product initial function page includes: Loading dependent resources of the function page according to the dependent resource identifier in the initial function page generation call information, and creating an initial function page mount point according to the mount point identifier in the initial function page generation call information; The initial function page component is called according to the initial function page access route in the initial function page generation call information, and the initial function page component is rendered to the initial function page mounting point to obtain the cloud product initial function page.

10. A cloud product page generation device, characterized in that: The device comprises: An instruction receiving module, used to receive a cloud product page display instruction, wherein the cloud product page display instruction includes an initial access route; a configuration file acquisition module, configured to acquire a cloud product page entry configuration file according to the cloud product page display instruction, wherein the cloud product page entry configuration file includes configuration information of the function page to be converted, wherein the configuration information of the function page to be converted includes a native route to be converted and dependent resources of the function page to be converted, wherein the dependent resources of the function page to be converted refer to resource addresses on which generation of the function page to be converted depends; A standard conversion module, used for performing information standardization conversion based on the function page configuration information to be converted, and obtaining function page standard information, wherein the function page standard information includes a function page standard route and corresponding function page generation call information; A route conversion module, used to perform route conversion on the initial access route to obtain a standard route for the initial function page; A calling information search module, used for searching the initial function page corresponding to the initial function page standard route based on the function page standard information to generate calling information; The function page generation module is used to generate a function page based on the initial function page generation call information to obtain an initial function page of the cloud product.

11. The device according to claim 10, characterized in that The device further comprises: The module for determining information to be converted is used to obtain configuration information of each function page, wherein the configuration information of each function page includes access method information of each function page; determine the function page configuration information to be converted from the configuration information of each function page based on the access method information of each function page; and write the function page configuration information to be converted into the cloud product page entry configuration file.

12. The device according to claim 10, characterized in that The cloud product page entry configuration file also includes a function page menu list; the device also includes: A list loading module is used to load the function page menu list to obtain the function page menu list; each function page in the function page menu list is developed through different development modes; The target page obtaining module is used to obtain the cloud product target page based on the function page menu list and the cloud product initial function page.

13. The device according to claim 12, characterized in that The device further comprises: A list generation module is used to obtain configuration information of each function page, wherein the function page configuration information includes a function page access route; combine the various function page access routes to obtain a cloud product combination route; obtain a basic function page menu list and a cloud product identifier, generate the function page menu list according to the cloud product identifier, the cloud product combination route and the basic function page menu list, and write the function page menu list into the cloud product page entry configuration file.

14. The device according to claim 12, characterized in that The device further comprises: A first instruction receiving module, configured to receive a first function page display instruction triggered by the function page menu list, wherein the first function page display instruction carries a first function page route; A first route conversion module, used for converting the first function page route into a first function page standard route according to a preset mapping rule; A first information search module, configured to search for a first function page corresponding to the first function page standard route based on the function page standard information and generate call information; The first page generation module is used to generate a first function page based on the first function page generation calling information to obtain a first function page.

15. The device according to claim 12, characterized in that The device further comprises: A second instruction receiving module, configured to receive a second function page display instruction triggered by the function page menu list, wherein the second function page display instruction carries a second function page route, and the second function page route is a second function page standard route; A second information search module is used to obtain the second function page generation call information corresponding to the second function page standard route; the second function page standard route and the second function page generation call information are written into the page implementation code; The second page generation module generates a second function page based on the second function page generation calling information to obtain a second function page.

16. The device according to claim 12, characterized in that The device further comprises: A third instruction receiving module, used to receive a third function page display instruction triggered by the function page menu list, wherein the third function page display instruction carries a third function page route; A resource information acquisition module, used for acquiring the associated page generation resource information based on the third function page route, wherein the page generation resource information includes the third function page standard information; the third function page standard information is obtained by performing information standardization conversion on the third function page configuration information when the page generation resource information is compiled; The third page generation module is used to determine the third function page generation calling information from the third function page standard information; generate the third function page based on the third function page generation calling information to obtain the third function page.

17. The device according to claim 10, characterized in that The configuration information of the function page to be converted includes an access route, a dependent resource identifier and a mount point identifier of the function page to be converted; The standard conversion module is also used to convert the to-be-converted function page access route into a function page standard route according to a preset mapping rule; Generate corresponding call information based on the access route of the function page to be converted, the dependent resource identifier and the mount point identifier; The function page standard information is obtained according to the function page standard route and the calling information.

18. The device according to claim 10, characterized in that The function page generation module is also used to load function page dependent resources according to the dependent resource identifier in the initial function page generation call information, and create an initial function page mount point according to the mount point identifier in the initial function page generation call information; call the initial function page component according to the initial function page access route in the initial function page generation call information, and render the initial function page component to the initial function page mount point to obtain the cloud product initial function page.

19. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 9 are implemented.

20. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 9 are implemented.

21. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 9 are implemented.

Images