Page processing method, apparatus, device, storage medium, and product

Abstract

The present disclosure provides a page processing method, device, equipment, storage medium and product, and relates to the technical field of computers. The method comprises the following steps: in response to a page access request of a parent application front end to a child application page, obtaining resource address information of the child application page from a child application back end and returning the resource address information to the parent application front end; creating an inline frame element in a parent application page by the parent application front end, and sending a page loading request comprising the resource address information to a child application front end; in response to the page loading request, determining target page configuration information according to first preset page configuration information and second preset page configuration information of the parent application page by the child application front end, and rendering the child application page according to the target page configuration information, so that the child application page is displayed in the inline frame element. By adopting the above technical solution, the display of the application page carried by the inline frame in the parent application page can be more coordinated, and the page display effect can be improved.

Description

Technical Field

[0001] This disclosure relates to the field of computer technology, and in particular to page processing methods, apparatus, devices, storage media, and products. Background Technology

[0002] With the rapid development of computer and internet technologies, front-end pages are carrying increasingly rich and diverse functions.

[0003] In some scenarios, different functional systems may need to add the same new functionality. For example, adding a public welfare function to an e-commerce system, a food delivery system, and a travel system. Before adding the new function, different functional systems are often developed and maintained independently, possibly using different technology stacks. For example, an e-commerce system might be developed using React, while a food delivery system might be developed using Vue. This difference increases the complexity of uniformly deploying the new function. Traditional solutions require extensive customization for each functional system, which is time-consuming, labor-intensive, and has high integration costs. In addition, the front-end page styles of different functional systems may differ. If the page style of the new function is designed uniformly across different functional systems, it will lead to differences in the page display of the new function compared to the original functions, affecting the page display effect and resulting in a poor user experience. Summary of the Invention

[0004] This disclosure provides page processing methods, apparatus, devices, storage media, and products, which can optimize existing page processing solutions.

[0005] In a first aspect, embodiments of this disclosure provide a page processing method, including:

[0006] The parent application backend responds to the parent application frontend's page access request for the child application page, obtains the resource address information of the child application page from the child application backend, and returns the resource address information to the parent application frontend. The resource address information includes the first preset page configuration information of the child application page.

[0007] The parent application frontend creates an inline frame element in the parent application page to carry the child application page, and sends a page loading request for the child application page to the child application frontend based on the resource address information, wherein the page loading request includes the resource address information;

[0008] The sub-application frontend responds to the page loading request, determines the target page configuration information based on the first preset page configuration information and the second preset page configuration information of the parent application page in the page loading request, and renders the sub-application page according to the target page configuration information so that the sub-application page is displayed in the inline frame element.

[0009] Secondly, embodiments of this disclosure also provide a page processing apparatus, including:

[0010] The resource address information processing module is used to respond to the page access request for the child application page from the parent application backend, obtain the resource address information of the child application page from the child application backend, and return the resource address information to the parent application frontend. The resource address information includes the first preset page configuration information of the child application page.

[0011] The page loading request module is used to create an inline frame element in the parent application page to carry the child application page through the parent application front-end, and send a page loading request for the child application page to the child application front-end based on the resource address information, wherein the page loading request includes the resource address information;

[0012] The page rendering module is used to respond to the page loading request through the sub-application front-end, determine the target page configuration information based on the first preset page configuration information and the second preset page configuration information of the parent application page in the page loading request, and render the sub-application page according to the target page configuration information so that the sub-application page is displayed in the inline frame element.

[0013] Thirdly, embodiments of this disclosure also provide an electronic device, the electronic device comprising:

[0014] One or more processors;

[0015] Storage device for storing one or more programs.

[0016] When the one or more programs are executed by the one or more processors, the one or more processors implement the page processing method provided in the embodiments of this disclosure.

[0017] Fourthly, embodiments of this disclosure also provide a storage medium containing computer-executable instructions, which, when executed by a computer processor, are used to perform the page processing method provided in embodiments of this disclosure.

[0018] Fifthly, embodiments of this disclosure also provide a computer program product, including a computer program that, when executed by a processor, implements the page processing method provided in embodiments of this disclosure.

[0019] The page processing scheme provided in this disclosure involves the parent application backend responding to a page access request for a child application page from the parent application frontend. The backend obtains the resource address information of the child application page from the child application backend and returns this information to the parent application frontend. The resource address information includes first preset page configuration information for the child application page. The parent application frontend creates an inline frame element within the parent application page to host the child application page and sends a page loading request for the child application page, including the resource address information, to the child application frontend based on the resource address information. The child application frontend responds to the page loading request, determines the target page configuration information based on the first preset page configuration information and the second preset page configuration information of the parent application page, and renders the child application page according to the target page configuration information, so that the child application page is displayed within the inline frame element. By adopting the above technical solution, the display of the application page hosted by the inline frame element within the parent application page can be more coordinated, improving the page display effect. Attached Figure Description

[0020] The above and other features, advantages, and aspects of the embodiments of this disclosure will become more apparent from the accompanying drawings and the following detailed description. Throughout the drawings, the same or similar reference numerals denote the same or similar elements. It should be understood that the drawings are schematic, and the originals and elements are not necessarily drawn to scale.

[0021] Figure 1 This is a schematic flowchart of a page processing method provided in an embodiment of the present disclosure;

[0022] Figure 2 This is a schematic flowchart illustrating another page processing method provided in an embodiment of the present disclosure;

[0023] Figure 3 This is a schematic diagram of an interface interaction in related technologies;

[0024] Figure 4 This is a schematic diagram of an interface interaction provided in an embodiment of the present disclosure;

[0025] Figure 5 A schematic flowchart illustrating yet another page processing method provided in an embodiment of this disclosure;

[0026] Figure 6 This is a schematic diagram of a communication process provided in an embodiment of the present disclosure;

[0027] Figure 7 This is a schematic diagram of the structure of a page processing apparatus provided in an embodiment of the present disclosure;

[0028] Figure 8 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this disclosure. Detailed Implementation

[0029] Embodiments of this disclosure will now be described in more detail with reference to the accompanying drawings. While some embodiments of this disclosure are shown in the drawings, it should be understood that this disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this disclosure. It should be understood that the accompanying drawings and embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure.

[0030] It should be understood that the steps described in the method embodiments of this disclosure may be performed in different orders and / or in parallel. Furthermore, the method embodiments may include additional steps and / or omit the steps shown. The scope of this disclosure is not limited in this respect.

[0031] The term "comprising" and its variations as used herein are open-ended inclusions, meaning "including but not limited to". The term "based on" means "at least partially based on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Definitions of other terms will be given in the description below.

[0032] It should be noted that the concepts of "first" and "second" mentioned in this disclosure are used only to distinguish different devices, modules or units, and are not used to limit the order of functions performed by these devices, modules or units or their interdependencies.

[0033] It should be noted that the terms "a" and "a plurality of" used in this disclosure are illustrative rather than restrictive, and those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as "one or more".

[0034] The names of messages or information exchanged between multiple devices in the embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of such messages or information.

[0035] Figure 1 This is a flowchart illustrating a page processing method provided in an embodiment of the present disclosure. This embodiment is applicable to page processing scenarios where there is functional nesting. The method can be executed by a page processing device, which can be implemented in software and / or hardware. Optionally, it can be implemented by an electronic device, such as a mobile terminal like a mobile phone, smartwatch, tablet computer, or personal digital assistant, or a device like a personal computer (PC) or server.

[0036] like Figure 1 As shown, the method includes:

[0037] Step 101: Respond to the page access request for the child application page by the parent application backend, obtain the resource address information of the child application page from the child application backend, and return the resource address information to the parent application frontend. The resource address information includes the first preset page configuration information of the child application page.

[0038] In this embodiment, the parent application can be an application within an existing functional system, such as an e-commerce system, a food delivery system, or a travel system. The child application can be an application corresponding to a new function (such as a public welfare function) newly added to an existing functional system. This child application can be added to multiple different functional systems, thus becoming a child application of multiple different parent applications. The page in this embodiment can be an application page or a webpage corresponding to a preset client, etc., without specific limitations. The preset client is a client running on an electronic device; it can be a preset application or a webpage client. The child application page is a child page embedded within the parent application page. In this embodiment, the child application page is embedded within the parent application page based on inline frame technology. Specifically, the inline frame can be an iframe (Inline Frame), which is a Hyper Text Markup Language (HTML) element used to embed another HTML page within the current page. It creates an inline floating frame that can contain data from different sources, adapting to various parent application front-end technology stacks, ensuring compatibility with the parent application front-end, and significantly shortening the deployment time of child applications used to implement new functions.

[0039] For example, a user interacts with the relevant functions of a parent application through the parent application frontend. This can be achieved by inputting an access operation for the parent application page through the parent application frontend. Upon receiving this access operation, the parent application frontend sends an access request for the parent application page and a page access request for the child page to the parent application backend. In response to the access request for the parent application page, the parent application backend performs the rendering operation for the parent application page and sends a request to the child application backend to obtain the resource address information of the child application page. The backend then receives the resource address information of the child application page returned by the child application backend and returns this resource address information to the parent application frontend. Specifically, the resource address information can be a Uniform Resource Locator (URL). In this embodiment, the resource address information may include information for locating and accessing resources in the child application page, as well as preset page configuration information for the child application page (denoted as the first preset page configuration information). The first preset page configuration information may be page configuration information set during the development of the child application. The page configuration information in this embodiment may include theme configuration information, page configuration parameters such as font, font size, character spacing, color (e.g., font color, border color, background color, and link color), cursor, and component style, etc. The first preset page configuration information may include the parameter values ​​of any one or more of the above page configuration parameters.

[0040] Step 102: Create an inline frame element in the parent application page through the parent application front-end to carry the child application page, and send a page loading request for the child application page to the child application front-end based on the resource address information, wherein the page loading request includes the resource address information.

[0041] Optionally, a Software Development Kit (SDK) can be integrated into the parent application frontend. The SDK allows the creation of inline frame elements within the parent application page to host child application pages. Management of these inline frame elements can also be handled by the SDK. For example, new inline frame elements can be created within child application pages hosted by existing inline frame elements to host even lower-level child application pages. This enables iterative updates of new features without requiring additional modifications to the parent application frontend, reducing update costs. Furthermore, the SDK facilitates data interaction with child application frontends, as well as sending and receiving events. By integrating a unified SDK into different parent application frontends and providing standardized interfaces, the difficulty of integrating new features into different existing systems can be significantly reduced, enabling rapid integration and improving the timeliness of new feature applications.

[0042] For example, after receiving the resource address information of the child application page, the parent application frontend creates an inline frame element in the parent application page through the SDK, and can continue to send a page loading request for the child application page to the child application frontend based on the received resource address information through the SDK. The page loading request includes the resource address information so that the child application frontend can obtain the first preset page configuration information by parsing the resource address information.

[0043] Step 103: The sub-application front-end responds to the page loading request, determines the target page configuration information based on the first preset page configuration information and the second preset page configuration information of the parent application page in the page loading request, and renders the sub-application page according to the target page configuration information so that the sub-application page is displayed in the inline frame element.

[0044] For example, after receiving a page loading request from the parent application frontend, the sub-application frontend obtains resource address information from the page loading request and parses the resource address information to obtain first preset page configuration information. Based on the obtained first preset page configuration information and the parent application page's preset page configuration information (denoted as second preset page configuration information), it jointly determines the target page configuration information of the sub-application page to be rendered and renders the sub-application page according to the target page configuration information, so that the sub-application page can be displayed in the inline frame element of the parent application page. The second preset page configuration information may include the parameter values ​​of any one or more of the above page configuration parameters. The second preset page configuration can be obtained by the sub-application frontend from the sub-application backend. The sub-application backend can pre-store the second preset page configuration information corresponding to each parent application page in multiple different functional systems. For example, the second preset page configuration information can be stored by a configuration storage service in the sub-application backend, and it can also store component resource information of the parent application page, such as image links and jump addresses for banner components. Before rendering the subpage, the sub-application frontend dynamically obtains the second preset page configuration information of the current parent application page, and then dynamically determines the target page configuration information. This ensures that the rendered sub-application page is more in line with the page style of the parent application page, and guarantees that the sub-application page carried by the inline frame is displayed more harmoniously in the parent application page, thus improving the page display effect.

[0045] Optionally, during the process of determining the target page configuration information based on the first preset page configuration information and the second preset page configuration information, the parameter values ​​of the page configuration parameters in the first preset page configuration information and the second preset page configuration information can be merged. If the first preset page configuration information and the second preset page configuration information both contain a parameter value of a certain page configuration parameter, and the parameter values ​​are different, the parameter value of that page configuration parameter in the target page configuration information can be determined according to a preset method, such as taking the middle value of the two parameter values, or taking the parameter value in the first preset page configuration information, or taking the second preset page configuration information, etc.

[0046] The page processing method provided in this embodiment responds to a page access request for a child application page from the parent application backend. It obtains the resource address information of the child application page from the child application backend and returns the resource address information to the parent application frontend. The resource address information includes first preset page configuration information for the child application page. The parent application frontend creates an inline frame element in the parent application page to host the child application page and sends a page loading request for the child application page, including the resource address information, to the child application frontend based on the resource address information. The child application frontend responds to the page loading request, determines the target page configuration information based on the first preset page configuration information and the second preset page configuration information of the parent application page, and renders the child application page according to the target page configuration information, so that the child application page is displayed in the inline frame element. By adopting the above technical solution, and embedding inline frame elements in the parent application page to carry the child application page, it can adapt to various parent application front-end technology stacks, ensuring compatibility with the parent application front-end. The child application front-end comprehensively determines the target page configuration information for rendering the child application page based on the preset page configuration information of the child application page and the preset page configuration information of the parent application page. This ensures that the child application page carried by the inline frame is displayed more harmoniously in the parent application page, improving the page display effect and enhancing the user experience.

[0047] In some embodiments, the first preset page configuration information includes parameter values ​​of a first page configuration parameter, and the second preset page configuration information includes parameter values ​​of a second page configuration parameter; wherein, determining the target page configuration information based on the first preset page configuration information in the page loading request and the second preset page configuration information of the parent application page includes: determining that the parameter value of the first target page configuration parameter is a parameter value in the preset page configuration information to which it belongs, wherein the first target page configuration parameter is a page configuration parameter in the symmetric difference set of the first page configuration parameter and the second page configuration parameter, and the preset page configuration information includes the first preset page configuration information and the second preset page configuration information; determining that the parameter value of the second target page configuration parameter is a parameter value of the second preset page configuration information, wherein the second target page configuration parameter is a page configuration parameter in the intersection set of the first page configuration parameter and the second page configuration parameter; and determining the target page configuration information based on the parameter values ​​of the first target page configuration parameter and the second target page configuration parameter. Therefore, when there is a conflict between the page configuration of the parent application and the page configuration of the child application, the page configuration of the parent application shall prevail in determining the corresponding parameter values, so as to ensure that the rendered child application page can better match the page style of the parent application page and ensure the consistency of visual effects.

[0048] For example, suppose the first page configuration parameters include parameters a, b, c, and d, and the second page configuration parameters include parameters a, d, e, and f. The symmetric difference set includes parameters c, b, e, and f, and the intersection set includes parameters a and d. In the target page configuration information, the parameter values ​​of parameters c and b are the parameter values ​​in the first preset page configuration information, the parameter values ​​of parameters e and f are the parameter values ​​in the second preset page configuration information, and the parameter values ​​of parameters a and d are the parameter values ​​in the second preset page configuration information.

[0049] Figure 2 This is a flowchart illustrating another page processing method provided in this embodiment. This embodiment optimizes the various optional solutions described above, adding steps related to cross-domain communication between the parent application page and the child application page. Specifically, the method includes the following steps:

[0050] Step 201: Respond to the page access request for the child application page through the parent application backend, obtain the resource address information of the child application page from the child application backend, and return the resource address information to the parent application frontend. The resource address information includes the first preset page configuration information of the child application page.

[0051] Step 202: Create an inline frame element in the parent application page through the parent application frontend to carry the child application page, and send a page loading request for the child application page to the child application frontend based on the resource address information, wherein the page loading request includes the resource address information.

[0052] Step 203: The sub-application frontend responds to the page loading request, determines the target page configuration information based on the first preset page configuration information and the second preset page configuration information of the parent application page in the page loading request, and renders the sub-application page according to the target page configuration information so that the sub-application page is displayed in an inline frame element.

[0053] Step 204: The sub-application frontend responds to the preset interactive operation for the sub-application page and sends the target event corresponding to the preset interactive operation to the parent application frontend.

[0054] For example, after the child application page is rendered, a cross-system communication channel can be established between the parent application frontend and the child application frontend. For instance, the parent application frontend can send an initialization message to the child application frontend through cross-origin communication (postMessage). After receiving the response message returned by the child application frontend, the establishment of the communication channel is confirmed, and then secure cross-domain communication can be carried out based on the communication channel.

[0055] Optionally, an event detector can be registered in the parent application's frontend using a preset event registration function via the SDK. This function could be, for example, `on(eventNname, callback)`, where `eventNname` represents the event name and `callback` represents the callback function in the parent application's frontend, which can be passed through to the SDK. Similarly, an event detector can be removed from the parent application's frontend using a preset event removal function via the SDK. This function could be, for example, `off(eventNname, callback)`. After registering the event detector, when the child application's frontend detects a preset interactive operation on the child application's page, it can trigger the corresponding target event using a preset event trigger function and send relevant data about the target event to the parent application's frontend. This trigger function could be, for example, `emit(eventNname, data)`, which can specifically trigger the callback function corresponding to the target event in the parent application's frontend. The structure of the sent `postMessage`-based message can include the event type, data, and timestamp. Among these features, security checks can be performed when sending messages, such as verifying the source of received messages to ensure that the messages come from the expected source, encrypting messages using shared keys or asymmetric encryption algorithms, adding message signatures to ensure that messages are not modified during transmission, and preventing replay through message sequence numbers or timestamps.

[0056] The specific type of the target event in this embodiment is not limited, but may include, for example, a modal display event.

[0057] Step 205: Respond to the target event through the parent application's front end and execute the page processing operation corresponding to the target event in the parent application's page.

[0058] For example, after the callback function corresponding to the target event in the parent application frontend is triggered, the parent application frontend can execute the page processing operation corresponding to the target event in the parent application page, instead of the child application frontend executing the page processing operation corresponding to the target event. This makes the operation result of the page processing operation more consistent with the parent application page, further ensuring the page display effect.

[0059] Optionally, if the target event is a modal display event, this step may include: responding to the modal display event through the parent application frontend, creating a modal container corresponding to the modal display event in the parent application page, and adding a layer with a preset transparency (greater than 0 and less than 1) below the modal container, wherein the preset transparency is greater than 0 and less than 1, and the size of the layer is the same as the size of the parent application page; rendering the modal content corresponding to the modal display event through the child application frontend, so that the modal content is displayed in the modal container. Thus, by creating a modal container through the parent application frontend, the displayed modal is visually consistent with the modal displayed when no child application page is embedded, providing users with a unified operating experience and improving user experience.

[0060] Figure 3 This is a schematic diagram of an interface interaction in related technologies, such as... Figure 3 As shown, a child application page 302 is embedded in the parent application page 301. When the user clicks the "View Details" button in the child application page 302, the child application front-end handles the event and pops up a modal 303 in the child application page 302. The modal 303 is displayed in the center of the child application page 302. A semi-transparent layer is added under the modal 303. The size of the semi-transparent layer is the same as the size of the child application page 302. Visually, the boundary between the child application page 302 and the parent application page 301 is obvious, the sense of separation is strong, and the operation experience is poor.

[0061] Figure 4 This is a schematic diagram of an interface interaction provided in an embodiment of the present disclosure, such as... Figure 4As shown, a child application page 402 is embedded in the parent application page 401. When the user clicks the "View Details" button in the child application page 402, a modal display event is sent to the parent application frontend. The parent application frontend creates a modal container 403 corresponding to the modal display event in the parent application page, and adds a semi-transparent layer under the modal container 403. The size of this layer is the same as that of the parent application page 401. The content displayed in the modal container 403 is rendered by the child application frontend. The parent application frontend does not need to care about the specific content of the modal. Visually, there is no obvious boundary between the child application page 402 and the parent application page 401, which ensures the consistency of the user operation experience and effectively guarantees the user experience.

[0062] Furthermore, since the modal container can determine the display style of the modal, the parent application can customize it according to its own needs, making the display style of the modal more consistent with the display style of the parent application page, thus further improving the user experience.

[0063] The page processing method provided in this disclosure, by embedding inline frame elements in the parent application page to carry the child application page, can adapt to various parent application front-end technology stacks, ensuring compatibility with the parent application front-end. The child application front-end comprehensively determines the target page configuration information for rendering the child application page based on the preset page configuration information of the child application page and the preset page configuration information of the parent application page. After the child application page is rendered, the child application front-end responds to the preset interactive operation for the child application page and sends the target event corresponding to the preset interactive operation to the parent application front-end. The parent application front-end responds to the target event and executes the page processing operation corresponding to the target event in the parent application page, instead of the child application front-end executing the page processing operation corresponding to the target event. This makes the operation result of the page processing operation more consistent with the parent application page, further ensuring the page display effect and user experience.

[0064] In some embodiments, the resource address information further includes token information; wherein, the process of obtaining the resource address information of the sub-application page from the sub-application backend and returning the resource address information to the parent application frontend in response to a page access request for the sub-application page from the parent application backend includes: authenticating the page access request in response to a page access request for the sub-application page from the parent application frontend, and obtaining the resource address information of the sub-application page from the sub-application backend after successful authentication, and returning the resource address information to the parent application frontend; wherein, the process of determining the target page configuration information based on the first preset page configuration information and the second preset page configuration information of the parent application page in response to a page loading request from the sub-application frontend includes: initiating verification of the token information in the page loading request to the sub-application backend in response to the page loading request from the sub-application frontend, and determining the target page configuration information based on the first preset page configuration information and the second preset page configuration information of the parent application page after successful verification.

[0065] In this embodiment of the disclosure, a sub-application page can be embedded in the parent application pages of different parent applications, and the user access permissions of different parent applications are managed independently. Therefore, the parent application backend performs access authentication for the page access request of the sub-application page, without the need for the sub-application backend to perform access authentication, thereby reducing the development cost on the sub-application side and improving the timeliness of embedding the sub-application into the parent application.

[0066] The token information can be a token. The token information is generated by the sub-application backend, and the specific generation method is not limited. For example, the sub-application backend can generate initial address information containing a timestamp and a random string, use a private key to generate token information based on the initial address information, and then append the token information as a parameter to the initial address information to obtain the resource address information of the sub-application page.

[0067] Figure 5 This is a flowchart illustrating another page processing method provided in this embodiment. This embodiment optimizes the various optional solutions in the above embodiments and adds relevant steps for a token information refresh mechanism. Figure 6 This is a schematic diagram of a communication process provided in an embodiment of the present disclosure. Optionally, the sub-application backend may include a sub-application middleware and basic services.

[0068] Specifically, the method includes the following steps:

[0069] Step 501: The parent application backend responds to the parent application frontend's page access request for the child application page, performs access authentication on the page access request, and after successful authentication, obtains the resource address information of the child application page from the child application backend and returns the resource address information to the parent application frontend.

[0070] like Figure 6 As shown, when a parent application user accesses a parent application page in the parent application frontend, the parent application frontend requests access to a child application page from the parent application backend. The parent application backend authenticates the current parent application user's access permissions and, upon successful authentication, sends a request to the child application backend's underlying service to retrieve the resource address information of the child application page, such as a URL including a token. After generating a URL including the token, the underlying service returns the URL to the parent application backend, which then returns the URL to the parent application frontend.

[0071] Step 502: Create an inline frame element in the parent application page through the parent application frontend to carry the child application page, and send a page loading request for the child application page to the child application frontend based on the resource address information, wherein the page loading request includes the resource address information.

[0072] like Figure 6 As shown, after receiving the URL, the parent application frontend initializes the SDK, creates an iframe element through the SDK, and requests the child application middleware to load the child application page, including the URL in the page load request.

[0073] Optionally, configuration parameters, such as the embedding position of the inline frame element in the parent application page, can be received via the SDK (this may be unknown in the DOM). The SDK creates an iframe element in the parent application page, generates a unique iframe ID, and inserts the created iframe element into the aforementioned embedding position.

[0074] Step 503: The sub-application frontend responds to the page loading request and initiates verification of the token information in the page loading request to the sub-application backend. After successful verification, the target page configuration information is determined based on the first preset page configuration information in the page loading request and the second preset page configuration information of the parent application page. The sub-application page is then rendered based on the target page configuration information so that the sub-application page is displayed in an inline frame element.

[0075] like Figure 6As shown, the sub-application frontend sends a token verification request to the sub-application middleware. The sub-application middleware calls the underlying service via Remote Procedure Call (RPC) to parse the token. The underlying service can use the private key used when generating the token to parse it and returns the parsing result to the sub-application middleware. The sub-application middleware then returns the verification result to the sub-application frontend. Upon receiving the verification result, if the sub-application frontend determines the token is valid, it determines the target page configuration information and renders the page content data of the sub-application page, displaying the sub-application page within the iframe element of the parent application page. If the token is invalid, it sends an invalid token event to the parent application frontend, causing the parent application frontend to handle the token invalidation and display an error message to prompt the user.

[0076] Step 504: The sub-application frontend responds to the preset interactive operation for the sub-application page and sends the target event corresponding to the preset interactive operation to the parent application frontend. The target event includes the modal display event.

[0077] like Figure 6 As shown, the child application frontend and the parent application frontend communicate using postMessage. Assuming the preset interaction operation is to open a pop-up window, the child application frontend sends an open pop-up window event to the parent application frontend.

[0078] Step 505: Respond to the modal display event in the parent application front end, create a modal container corresponding to the modal display event in the parent application page, and add a layer with preset transparency below the modal container.

[0079] like Figure 6 As shown, after the parent application frontend receives the pop-up event, it uses a custom Modal component to create a modal container.

[0080] Step 506: Render the modal content corresponding to the event through the sub-application front-end so that the modal content is displayed in the modal container.

[0081] like Figure 6 As shown, after the parent application user completes the operation, the parent application frontend can send a completion event to the child application frontend.

[0082] Step 507: In response to the preset scheduled task being triggered, the parent application frontend sends a token update request to the parent application backend.

[0083] For example, the preset timer for the scheduled task can be set according to actual needs, such as once every 10 minutes, to perform timed polling for token updates. This allows the parent application frontend to periodically check the token's validity period and request a new token through a secure channel when it is about to expire. Figure 6 As shown, after the preset scheduled task is triggered, the parent application frontend sends a request to the parent application backend to obtain a new token.

[0084] Step 508: Respond to the token update request through the parent application backend, obtain the new token information from the child application backend, and return the new token information to the parent application frontend.

[0085] like Figure 6 As shown, after receiving a request to obtain a new token, the parent application retrieves the new token from the child application's backend and returns the new token to the parent application's frontend.

[0086] Step 509: The parent application frontend interacts with the child application frontend based on the new token information.

[0087] like Figure 6 As shown, the parent application frontend updates the token to the child application frontend to prevent the token from becoming invalid. The child application frontend can then verify the new token again. If the verification passes, data interaction can continue; if the verification fails, an invalid token event can be sent.

[0088] The page processing method provided in this disclosure authenticates the page access requests of the child application page through the parent application backend, without requiring the child application backend to perform access authentication, thereby reducing the development cost on the child application side and improving the timeliness of embedding the child application into the parent application. Furthermore, by dynamically generating resource address information, token information authentication, timed updating of token information, and encrypted communication, it comprehensively ensures the security of cross-system data interaction between the parent application frontend and the child application frontend.

[0089] Figure 7 This is a schematic diagram of the structure of a page processing apparatus provided in an embodiment of the present disclosure, as shown below. Figure 7 As shown, the device includes:

[0090] The resource address information processing module 701 is used to respond to a page access request for a child application page from the parent application backend, obtain the resource address information of the child application page from the child application backend, and return the resource address information to the parent application frontend. The resource address information includes the first preset page configuration information of the child application page.

[0091] The page loading request module 702 is used to create an inline frame element in the parent application page to carry the child application page through the parent application front-end, and send a page loading request for the child application page to the child application front-end based on the resource address information, wherein the page loading request includes the resource address information;

[0092] The page rendering module 703 is used to respond to the page loading request through the sub-application front-end, determine the target page configuration information according to the first preset page configuration information and the second preset page configuration information of the parent application page in the page loading request, and render the sub-application page according to the target page configuration information so that the sub-application page is displayed in the inline frame element.

[0093] The page processing apparatus provided in this disclosure carries a child application page by embedding inline frame elements in the parent application page. This adapts to various parent application front-end technology stacks, ensuring compatibility with the parent application front-end. The child application front-end comprehensively determines the target page configuration information for rendering the child application page based on the preset page configuration information of the child application page and the preset page configuration information of the parent application page. This ensures that the child application page carried by the inline frame is displayed more harmoniously in the parent application page, improving the page display effect and enhancing the user experience.

[0094] Optionally, the first preset page configuration information includes parameter values ​​of a first page configuration parameter, and the second preset page configuration information includes parameter values ​​of a second page configuration parameter; wherein, determining the target page configuration information based on the first preset page configuration information in the page loading request and the second preset page configuration information of the parent application page includes: determining that the parameter value of the first target page configuration parameter is a parameter value in the preset page configuration information to which it belongs, wherein the first target page configuration parameter is a page configuration parameter in the symmetric difference set of the first page configuration parameter and the second page configuration parameter, and the preset page configuration information includes the first preset page configuration information and the second preset page configuration information; determining that the parameter value of the second target page configuration parameter is a parameter value of the second preset page configuration information, wherein the second target page configuration parameter is a page configuration parameter in the intersection set of the first page configuration parameter and the second page configuration parameter; and determining the target page configuration information based on the parameter values ​​of the first target page configuration parameter and the second target page configuration parameter.

[0095] Optionally, the device may also include:

[0096] The target event sending module is used to send a target event corresponding to the preset interactive operation to the parent application frontend after the sub-application frontend renders the sub-application page according to the target page configuration information.

[0097] The target event response module is used to respond to the target event through the parent application front end and perform the page processing operation corresponding to the target event in the parent application page.

[0098] Optionally, the target event includes a modal display event;

[0099] The target event response module includes:

[0100] A modal container creation unit is used to create a modal container corresponding to the modal display event in the parent application page in response to the modal display event from the parent application front end.

[0101] A layer adding unit is used to add a layer with a preset transparency to the lower layer of the modal container, wherein the preset transparency is greater than 0 and less than 1, and the size of the layer is the same as the size of the parent application page;

[0102] The content rendering unit is used to render the modal content corresponding to the modal display event through the sub-application front end, so that the modal content is displayed in the modal container.

[0103] Optionally, the resource address information may also include token information;

[0104] The process of responding to a page access request for a child application page by the parent application backend, obtaining the resource address information of the child application page from the child application backend, and returning the resource address information to the parent application frontend includes: authenticating the page access request by the parent application backend in response to the page access request for the child application page from the parent application frontend, and after successful authentication, obtaining the resource address information of the child application page from the child application backend and returning the resource address information to the parent application frontend;

[0105] Specifically, the process of determining target page configuration information by responding to the page loading request through the sub-application frontend and based on the first preset page configuration information in the page loading request and the second preset page configuration information of the parent application page includes: initiating verification of the token information in the page loading request to the sub-application backend through the sub-application frontend in response to the page loading request, and determining the target page configuration information based on the first preset page configuration information in the page loading request and the second preset page configuration information of the parent application page after successful verification.

[0106] Optionally, the device may also include:

[0107] The update request module is used to send a token update request to the parent application backend in response to the triggering of a preset timed task by the parent application frontend.

[0108] The token update module is used to respond to the token update request through the parent application backend, obtain new token information from the child application backend, and return the new token information to the parent application frontend;

[0109] The data interaction module is used to interact with the child application frontend through the parent application frontend based on the new token information.

[0110] The page processing apparatus provided in this disclosure can execute the page processing method provided in any embodiment of this disclosure, and has the corresponding functional modules and beneficial effects of executing the method.

[0111] It is worth noting that the various units and modules included in the above-mentioned device are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be realized; in addition, the specific names of each functional unit are only for easy differentiation and are not used to limit the protection scope of the embodiments of this disclosure.

[0112] Figure 8 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this disclosure. Reference is made below. Figure 8 It illustrates an electronic device suitable for implementing embodiments of the present disclosure (e.g., Figure 8 The diagram below shows the structure of the terminal device or server 800. The terminal device in this embodiment may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), and vehicle terminals (e.g., vehicle navigation terminals), as well as fixed terminals such as digital TVs and desktop computers. Figure 8 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments disclosed herein.

[0113] like Figure 8 As shown, the electronic device 800 may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 801, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 802 or a program loaded from a storage device 808 into a random access memory (RAM) 803. The RAM 803 also stores various programs and data required for the operation of the electronic device 800. The processing device 801, ROM 802, and RAM 803 are interconnected via a bus 804. An edit / output (I / O) interface 805 is also connected to the bus 804.

[0114] Typically, the following devices can be connected to I / O interface 805: input devices 806 including, for example, touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, gyroscopes, etc.; output devices 807 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 808 including, for example, magnetic tapes, hard disks, etc.; and communication devices 809. Communication device 809 allows electronic device 800 to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 8 An electronic device 800 with various devices is shown; however, it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed alternatively.

[0115] In particular, according to embodiments of this disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this disclosure include a computer program product comprising a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device 809, or installed from a storage device 808, or installed from a ROM 802. When the computer program is executed by a processing device 801, it performs the functions defined in the methods of embodiments of this disclosure.

[0116] The names of messages or information exchanged between multiple devices in the embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of such messages or information.

[0117] The electronic device provided in this embodiment and the page processing method provided in the above embodiments belong to the same inventive concept. Technical details not described in detail in this embodiment can be found in the above embodiments, and this embodiment has the same beneficial effects as the above embodiments.

[0118] This disclosure provides a computer storage medium storing a computer program that, when executed by a processor, implements the page processing method provided in the above embodiments.

[0119] This disclosure provides a computer program product, including a computer program that, when executed by a processor, implements the page processing method provided in the above embodiments.

[0120] It should be noted that the computer-readable medium described in this disclosure can be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this disclosure, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in connection with an instruction execution system, apparatus, or device. In this disclosure, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium can be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wires, optical fibers, RF (radio frequency), etc., or any suitable combination thereof.

[0121] In some implementations, clients and servers can communicate using any currently known or future-developed network protocol such as HTTP (Hypertext Transfer Protocol) and can interconnect with digital data communication (e.g., communication networks) of any form or medium. Examples of communication networks include local area networks (“LANs”), wide area networks (“WANs”), the Internet (e.g., the Internet of Things), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future-developed networks.

[0122] The aforementioned computer-readable medium may be included in the aforementioned electronic device; or it may exist independently and not assembled into the electronic device.

[0123] The aforementioned computer-readable medium carries one or more programs. When the electronic device executes the one or more programs, the electronic device causes the following: In response to a page access request for a child application page from a parent application frontend, the electronic device obtains resource address information of the child application page from the child application backend and returns the resource address information to the parent application frontend, wherein the resource address information includes first preset page configuration information of the child application page; The electronic device creates an inline frame element in the parent application page to host the child application page, and sends a page loading request for the child application page to the child application frontend based on the resource address information, wherein the page loading request includes the resource address information; In response to the page loading request, the electronic device determines target page configuration information based on the first preset page configuration information and the second preset page configuration information of the parent application page in the page loading request, and renders the child application page according to the target page configuration information, so that the child application page is displayed in the inline frame element.

[0124] Computer program code for performing the operations of this disclosure can be written in one or more programming languages ​​or a combination thereof, including but not limited to object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0125] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0126] The units described in the embodiments of this disclosure can be implemented in software or hardware. The names of modules do not necessarily limit the module itself; for example, the resource address information processing module can also be described as "a module that, in response to a page access request from the parent application frontend for a child application page, obtains the resource address information of the child application page from the child application backend and returns the resource address information to the parent application frontend."

[0127] The functions described above in this document can be performed, at least in part, by one or more hardware logic components. For example, exemplary types of hardware logic components that can be used, without limitation, include: Field Programmable Gate Arrays (FPGAs), Application-Specific Integrated Circuits (ASICs), Application Standard Products (ASSPs), System-on-Chip (SoCs), Complex Programmable Logic Devices (CPLDs), and so on.

[0128] In the context of this disclosure, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0129] According to one or more embodiments of this disclosure, a page processing method is provided, comprising:

[0130] The parent application backend responds to the parent application frontend's page access request for the child application page, obtains the resource address information of the child application page from the child application backend, and returns the resource address information to the parent application frontend. The resource address information includes the first preset page configuration information of the child application page.

[0131] The parent application frontend creates an inline frame element in the parent application page to carry the child application page, and sends a page loading request for the child application page to the child application frontend based on the resource address information, wherein the page loading request includes the resource address information;

[0132] The sub-application frontend responds to the page loading request, determines the target page configuration information based on the first preset page configuration information and the second preset page configuration information of the parent application page in the page loading request, and renders the sub-application page according to the target page configuration information so that the sub-application page is displayed in the inline frame element.

[0133] According to one or more embodiments of this disclosure, the first preset page configuration information includes parameter values ​​of a first page configuration parameter, and the second preset page configuration information includes parameter values ​​of a second page configuration parameter.

[0134] The step of determining the target page configuration information based on the first preset page configuration information in the page loading request and the second preset page configuration information of the parent application page includes:

[0135] The parameter value of the first target page configuration parameter is determined to be the parameter value in the preset page configuration information, wherein the first target page configuration parameter is the page configuration parameter in the symmetrical difference set of the first page configuration parameter and the second page configuration parameter, and the preset page configuration information includes the first preset page configuration information and the second preset page configuration information;

[0136] The parameter value of the second target page configuration parameter is determined to be the parameter value of the second preset page configuration information, wherein the second target page configuration parameter is the page configuration parameter in the intersection of the first page configuration parameter and the second page configuration parameter;

[0137] The target page configuration information is determined based on the parameter values ​​of the first target page configuration parameters and the second target page configuration parameters.

[0138] According to one or more embodiments of this disclosure, after rendering the sub-application page through the sub-application frontend based on the target page configuration information, the method further includes:

[0139] The sub-application front-end responds to a preset interactive operation on the sub-application page and sends a target event corresponding to the preset interactive operation to the parent application front-end.

[0140] The parent application frontend responds to the target event, and the page processing operation corresponding to the target event is executed in the parent application page.

[0141] According to one or more embodiments of this disclosure, the target event includes a modal display event;

[0142] Specifically, the parent application frontend responds to the target event, and performs the corresponding page processing operation on the parent application page, including:

[0143] In response to the modal display event, the parent application frontend creates a modal container corresponding to the modal display event in the parent application page, and adds a layer with a preset transparency below the modal container, wherein the preset transparency is greater than 0 and less than 1, and the size of the layer is the same as the size of the parent application page.

[0144] The modal content corresponding to the modal display event is rendered by the sub-application front-end so that the modal content is displayed in the modal container.

[0145] According to one or more embodiments of this disclosure, the resource address information further includes token information;

[0146] Specifically, the process of responding to a page access request for a child application page by the parent application backend, obtaining the resource address information of the child application page from the child application backend, and returning the resource address information to the parent application frontend includes:

[0147] The parent application backend responds to the parent application frontend's page access request for the child application page, performs access authentication on the page access request, and after successful authentication, obtains the resource address information of the child application page from the child application backend and returns the resource address information to the parent application frontend.

[0148] Specifically, the sub-application frontend responds to the page loading request and determines the target page configuration information based on the first preset page configuration information and the second preset page configuration information of the parent application page in the page loading request, including:

[0149] The sub-application frontend responds to the page loading request by initiating verification of the token information in the page loading request to the sub-application backend. After successful verification, the target page configuration information is determined based on the first preset page configuration information in the page loading request and the second preset page configuration information of the parent application page.

[0150] According to one or more embodiments of this disclosure, it further includes:

[0151] The parent application frontend responds to the triggering of a preset timed task by sending a token update request to the parent application backend;

[0152] The parent application backend responds to the token update request, obtains new token information from the child application backend, and returns the new token information to the parent application frontend.

[0153] The parent application frontend interacts with the child application frontend based on the new token information.

[0154] The above description is merely a preferred embodiment of this disclosure and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of this disclosure is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the above-described concept. For example, technical solutions formed by substituting the above features with (but not limited to) technical features disclosed in this disclosure that have similar functions.

[0155] Furthermore, while the operations are described in a specific order, this should not be construed as requiring these operations to be performed in the specific order shown or in a sequential order. In certain environments, multitasking and parallel processing may be advantageous. Similarly, while several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of this disclosure. Certain features described in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

[0156] Although this page configuration has been described using language specific to structural features and / or methodological logic, it should be understood that the page configuration defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are merely illustrative examples of implementing the claims.

Claims

1. A page processing method, characterized in that, include: The parent application backend responds to the parent application frontend's page access request for the child application page, obtains the resource address information of the child application page from the child application backend, and returns the resource address information to the parent application frontend. The resource address information includes the first preset page configuration information of the child application page. The parent application frontend creates an inline frame element in the parent application page to carry the child application page, and sends a page loading request for the child application page to the child application frontend based on the resource address information, wherein the page loading request includes the resource address information; The sub-application frontend responds to the page loading request, determines the target page configuration information based on the first preset page configuration information and the second preset page configuration information of the parent application page in the page loading request, and renders the sub-application page according to the target page configuration information so that the sub-application page is displayed in the inline frame element.

2. The method according to claim 1, characterized in that, The first preset page configuration information includes the parameter values ​​of the first page configuration parameters, and the second preset page configuration information includes the parameter values ​​of the second page configuration parameters; The step of determining the target page configuration information based on the first preset page configuration information in the page loading request and the second preset page configuration information of the parent application page includes: The parameter value of the first target page configuration parameter is determined to be the parameter value in the preset page configuration information, wherein the first target page configuration parameter is the page configuration parameter in the symmetrical difference set of the first page configuration parameter and the second page configuration parameter, and the preset page configuration information includes the first preset page configuration information and the second preset page configuration information; The parameter value of the second target page configuration parameter is determined to be the parameter value of the second preset page configuration information, wherein the second target page configuration parameter is the page configuration parameter in the intersection of the first page configuration parameter and the second page configuration parameter; The target page configuration information is determined based on the parameter values ​​of the first target page configuration parameters and the second target page configuration parameters.

3. The method according to claim 1, characterized in that, After rendering the sub-application page through the sub-application frontend according to the target page configuration information, the process further includes: The sub-application front-end responds to a preset interactive operation on the sub-application page and sends a target event corresponding to the preset interactive operation to the parent application front-end. The parent application frontend responds to the target event, and the page processing operation corresponding to the target event is executed in the parent application page.

4. The method according to claim 3, characterized in that, The target events include modal display events; Specifically, the parent application frontend responds to the target event, and performs the corresponding page processing operation on the parent application page, including: In response to the modal display event, the parent application frontend creates a modal container corresponding to the modal display event in the parent application page, and adds a layer with a preset transparency below the modal container, wherein the preset transparency is greater than 0 and less than 1, and the size of the layer is the same as the size of the parent application page. The modal content corresponding to the modal display event is rendered by the sub-application front-end so that the modal content is displayed in the modal container.

5. The method according to claim 1, characterized in that, The resource address information also includes token information; Specifically, the process of responding to a page access request for a child application page by the parent application backend, obtaining the resource address information of the child application page from the child application backend, and returning the resource address information to the parent application frontend includes: The parent application backend responds to the parent application frontend's page access request for the child application page, performs access authentication on the page access request, and after successful authentication, obtains the resource address information of the child application page from the child application backend and returns the resource address information to the parent application frontend. Specifically, the sub-application frontend responds to the page loading request and determines the target page configuration information based on the first preset page configuration information and the second preset page configuration information of the parent application page in the page loading request, including: The sub-application frontend responds to the page loading request by initiating verification of the token information in the page loading request to the sub-application backend. After successful verification, the target page configuration information is determined based on the first preset page configuration information in the page loading request and the second preset page configuration information of the parent application page.

6. The method according to claim 5, characterized in that, Also includes: The parent application frontend responds to the triggering of a preset timed task by sending a token update request to the parent application backend; The parent application backend responds to the token update request, obtains new token information from the child application backend, and returns the new token information to the parent application frontend. The parent application frontend interacts with the child application frontend based on the new token information.

7. A page processing apparatus, characterized in that, include: The resource address information processing module is used to respond to the page access request for the child application page from the parent application backend, obtain the resource address information of the child application page from the child application backend, and return the resource address information to the parent application frontend. The resource address information includes the first preset page configuration information of the child application page. The page loading request module is used to create an inline frame element in the parent application page to carry the child application page through the parent application front-end, and send a page loading request for the child application page to the child application front-end based on the resource address information, wherein the page loading request includes the resource address information; The page rendering module is used to respond to the page loading request through the sub-application front-end, determine the target page configuration information based on the first preset page configuration information and the second preset page configuration information of the parent application page in the page loading request, and render the sub-application page according to the target page configuration information so that the sub-application page is displayed in the inline frame element.

8. An electronic device, characterized in that, The electronic device includes: One or more processors; Storage device for storing one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors implement the page processing method as described in any one of claims 1-6.

9. A storage medium containing computer-executable instructions, characterized in that, The computer-executable instructions, when executed by a computer processor, are used to perform the page processing method as described in any one of claims 1-6.

10. A computer program product, characterized in that, It includes a computer program that, when executed by a processor, implements the page processing method as described in any one of claims 1-6.

Images