Method, device and equipment for locally refreshing jump page among multiple systems and storage medium
By creating a target container in the cloud system and building a second page, obtaining and passing refresh information, the problem of web page reloading when pages are redirected between multiple systems is solved, ensuring the retention of user operation records and the partial refresh of pages.
Patent Information
- Application Number
- CN202411167805.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-23
- Publication Date
- 2024-12-17
AI Technical Summary
When pages are redirected between multiple systems, the existing technology causes the web pages of the cloud system to be reloaded, resulting in the user operation records being cleared and reset, and local refresh cannot be achieved without reloading.
By creating a target container and building a second page on the target system, loading the target address to start the second target system, generating refresh information, and creating a new target address based on this information, so that the second page can obtain refresh information from the new target address and pass it on Go to the first page, partial refresh is achieved without the need for the first page to be reloaded.
It effectively avoids web page reloading, ensures that the user operation records in the system are not cleared and reset, and realizes local refresh of pages between multiple systems.
Smart Images
Figure CN119149843A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of software technology, and in particular to a method, device, equipment and storage medium for partially refreshing a page jump between multiple systems. Background Art
[0002] At present, for cloud systems, when they are running, user operation traces are usually left on the interface and some user operation information is also retained in the memory. When there is a page jump between multiple systems, for example, when a function of cloud system A that stores user operation records needs to obtain some information M from a third-party system B to refresh the interface, it often jumps to system B by changing the browser address, and attaches the callback address of system A to the jump link. Then, after system B processes the relevant logic, it jumps to the callback address again, and attaches the information M required by cloud system A to the address, so that cloud system A can obtain the information M returned by system B.
[0003] Although cloud system A can obtain information M in the above manner to achieve partial refresh of the page, this method will cause the webpage of cloud system A to be reloaded, which means that all user operation records stored in cloud system A will be cleared and reset. It can be seen that when achieving partial refresh of jump pages between multiple systems, how to avoid reloading of webpages is a problem that needs to be solved urgently. Summary of the invention
[0004] The present application provides a method, device, equipment and storage medium for partially refreshing a page for jumping between multiple systems, which can solve the technical problem of web page reloading caused by partially refreshing a page for jumping between multiple systems by changing a browser address in the prior art.
[0005] In a first aspect, an embodiment of the present application provides a method for partially refreshing a page jump between multiple systems, comprising the following steps:
[0006] When there is a partial refresh requirement for the first page of the first target system, creating a target container and building a second page on the first target system;
[0007] loading a target address based on the target container to start a second target system, the target address including an address of the second target system and an address of a second page;
[0008] generating refresh information by a second target system, and creating a new target address based on the refresh information and the address of the second page;
[0009] The new target address is loaded based on the target container, so that the second page obtains refresh information from the new target address and transmits it to the first page, so that the first page performs partial refresh based on the refresh information.
[0010] In combination with the first aspect, in one implementation, the address of the second page is the same as the address of the first page.
[0011] In combination with the first aspect, in one implementation, a size of the second page is the same as a size of the first page, so that the first page is covered by the second page.
[0012] In combination with the first aspect, in one implementation, the method further includes:
[0013] Controlling the first page to monitor messages of the target container, so that the first page obtains refresh information transmitted by the second page;
[0014] After the first page obtains the refresh information, the message monitoring is removed.
[0015] In a second aspect, an embodiment of the present application provides a device for partially refreshing a page jump between multiple systems, including:
[0016] A first processing module, configured to create a target container and construct a second page on the first target system when a local refresh requirement exists on the first page of the first target system;
[0017] A second processing module, which is used to load a target address based on a target container to start a second target system, wherein the target address includes an address of the second target system and an address of a second page;
[0018] a third processing module, configured to generate refresh information through a second target system, and create a new target address based on the refresh information and the address of the second page;
[0019] The fourth processing module is used to load the new target address based on the target container, so that the second page obtains refresh information from the new target address and transmits it to the first page, so that the first page performs partial refresh based on the refresh information.
[0020] In conjunction with the second aspect, in one implementation, the address of the second page is the same as the address of the first page.
[0021] In combination with the second aspect, in one implementation, a size of the second page is the same as a size of the first page, so that the first page is covered by the second page.
[0022] In combination with the second aspect, in one implementation, the device further includes a fifth processing module, which is used to:
[0023] Controlling the first page to monitor messages of the target container, so that the first page obtains refresh information transmitted by the second page;
[0024] After the first page obtains the refresh information, the message monitoring is removed.
[0025] In the third aspect, an embodiment of the present application provides a multi-system jump page local refresh device, wherein the multi-system jump page local refresh device comprises a processor, a memory, and a multi-system jump page local refresh program stored in the memory and executable by the processor, wherein when the multi-system jump page local refresh program is executed by the processor, the steps of the multi-system jump page local refresh method as described above are implemented.
[0026] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, on which a local refresh program for jumping pages between multiple systems is stored. When the local refresh program for jumping pages between multiple systems is executed by a processor, the steps of the local refresh method for jumping pages between multiple systems as described above are implemented.
[0027] The beneficial effects brought by the technical solution provided in the embodiments of the present application include:
[0028] When there is a need for partial refresh of the first page of the first target system, a target container is created and a second page is constructed on the first target system, and a target address composed of the address of the second target system and the address of the second page is loaded based on the target container to start the second target system; refresh information is then generated through the second target system, and a new target address is created based on the refresh information and the address of the second page, so that the target container can jump to the second page on the first target system when loading the new target address, so that the second page can obtain the refresh information from the new target address and pass it to the first page; at this time, the first page can be partially refreshed based on the refresh information without reloading. It can be seen that when implementing partial refresh of jump pages between multiple systems, the present application completes the transmission of refresh information by constructing a container to avoid reloading the web page, thereby ensuring that the user operation records stored in the system will not be cleared and reset. BRIEF DESCRIPTION OF THE DRAWINGS
[0029] Figure 1 This is a flow chart of an embodiment of a method for partially refreshing a page between multiple systems of the present application;
[0030] Figure 2 A schematic diagram of a specific process of partially refreshing a page involved in an embodiment of the present application;
[0031] Figure 3 This is a schematic diagram of the hardware structure of a local refresh device for jumping pages between multiple systems involved in the embodiment of the present application. DETAILED DESCRIPTION
[0032] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.
[0033] In order to make the objectives, technical solutions and advantages of the present application clearer, the implementation methods of the present application will be further described in detail below with reference to the accompanying drawings.
[0034] In a first aspect, an embodiment of the present application provides a method for partially refreshing a page jump between multiple systems.
[0035] In one embodiment, referring to Figure 1 , Figure 1 This is a flow chart of an embodiment of the method for partially refreshing a page between multiple systems of the present application. Figure 1 As shown, the method for partially refreshing a page between multiple systems includes:
[0036] Step S10: When there is a need for partial refresh of the first page of the first target system, a target container is created and a second page is constructed on the first target system.
[0037] Exemplarily, in this embodiment, the first target system is a cloud system that retains user operation information (hereinafter referred to as system A), and the first page is a page in the first target system that retains user operation traces (hereinafter referred to as page A1); when a certain function of page A1 (such as login function, user data synchronization function, external service call function, etc.) needs to obtain refresh information N through a third-party system (i.e., the second target system, hereinafter referred to as system B) to refresh the interface, the user can trigger the creation of a target container by performing relevant operations on page A1, and at the same time, global positioning is performed in system A and a second page for transmitting refresh information N is constructed (hereinafter referred to as page A2).
[0038] It should be noted that the target container may be an Iframe (Inline Frame) container, or other containers capable of embedding other pages in a page, which is not limited here.
[0039] Furthermore, in one embodiment, the size of the second page is the same as the size of the first page, so that the first page is covered by the second page.
[0040] Exemplarily, in this embodiment, when global positioning is performed in system A, the height and width are set to construct page A2; wherein, for functions that require user operation (such as the login function), the height and width of page A2 may preferably be set to be the same as page A1, so that page A2 can cover page A1, which can not only serve as a front-end security measure to prevent users from bypassing the current operation process to access protected resources, but also ensure that users are not disturbed by other page contents during the operation, thereby focusing more on the current operation.
[0041] It should be noted that for functions that do not require user operation (such as payment services, logistics inquiries, weather information, map services and other external service call functions), it is preferred to set the height and width of page A2 to 0 so that the user is unaware of the external service call process, thereby improving the user experience.
[0042] Step S20: loading a target address based on the target container to start the second target system, wherein the target address includes an address of the second target system and an address of the second page.
[0043] Exemplarily, in this embodiment, the address of system B is created, and the address of page A2 (i.e., the bounce address A_Adress_2) is added to the address of system B to form a target address; the target container loads the target address to start system B, so that system B generates the refresh information N required for page A1. It should be noted that in this embodiment, the address A_Adress_2 of page A2 can be preferably set to be different from the address A_Adress_1 of page A1, so as to effectively prevent the page flashing problem and effectively avoid the logical conflict between page A2 and page A1.
[0044] Furthermore, in one embodiment, the address of the second page is the same as the address of the first page.
[0045] Exemplarily, in this embodiment, the address A_Adress_2 of page A2 may be preferably set to be the same as the address A_Adress_1 of page A1, so that the purpose of logical aggregation can be achieved when performing code programming, thereby facilitating code maintenance. It should be noted that when the address A_Adress_2 of page A2 is the same as the address A_Adress_1 of page A1, page screen flashing problems and logical conflicts between page A2 and page A1 may occur, so relevant measures may be taken and code programming may be used to solve the page screen flashing problem and the logical conflict between page A2 and page A1. It should be understood that how to solve the page screen flashing problem and the logical conflict between page A2 and page A1 through code programming is common knowledge in the art and will not be repeated here.
[0046] Step S30: Generate refresh information through the second target system, and create a new target address based on the refresh information and the address of the second page.
[0047] Exemplarily, in this embodiment, when system B is started, it can generate refresh information N required for page A1, and concatenate the jump back address A_Adress_2 in the target address with the refresh information N to form a new target address, so that the target container can jump to page A2 based on the new target address. It should be noted that the refresh information N refers to the information required by the function corresponding to page A1 (such as login function, user data synchronization function, external service call function, etc.), and the specific information contained therein is determined according to the function type and is not limited here.
[0048] Step S40: loading the new target address based on the target container, so that the second page obtains refresh information from the new target address and transmits it to the first page, so that the first page performs partial refresh based on the refresh information.
[0049] Exemplarily, in this embodiment, after the target container loads the new target address and jumps to page A2 corresponding to A_Adress_2, it will trigger page A2 to obtain the refresh information N carried in the new target address, and pass the refresh information N to page A1, so that page A1 can obtain the refresh information N for partial page refresh without reloading. It should be noted that if the refresh information N is an information storage address (such as the address of a data storage server), etc., then after page A2 obtains the refresh information N, it will also obtain the corresponding other refresh information P from the system or platform corresponding to the address recorded in the refresh information N, and then pass the other refresh information P to page A1, so that page A1 can obtain the refresh information P for partial page refresh without reloading.
[0050] It can be seen that when implementing partial refresh of jump pages between multiple systems, this embodiment completes the transmission of refresh information by constructing a container to avoid reloading the web page, thereby ensuring that user operation records stored in the system will not be cleared and reset.
[0051] Furthermore, in one embodiment, the method further includes:
[0052] Controlling the first page to monitor messages of the target container, so that the first page obtains refresh information transmitted by the second page;
[0053] After the first page obtains the refresh information, the message monitoring is removed.
[0054] Exemplarily, in this embodiment, if the target container is an Iframe container, when page A2 obtains the refresh information N, it can notify the parent system A of the refresh information N in the form of a message through PostMessage (this function is used to put a message into the message queue associated with the thread created by the specified window, and return without waiting for the thread to process the message); and page A1 in system A will monitor the message of the target container to obtain the refresh information N in the message, and after page A1 obtains the refresh information N, remove the message monitoring to avoid the occurrence of unknown behaviors or message leakage.
[0055] It should be noted that if the target container is not an Iframe container, when page A2 obtains the refresh information N, it can pass the refresh information N to the parent system A through the message passing method corresponding to the target container, so that page A1 in system A obtains the refresh information N.
[0056] The following combination Figure 2 Taking the Iframe container as an example in the login scenario, the principle and process of partial refresh of the page jump between multiple systems are explained.
[0057] When a user logs in to page A1 with the address A_Adress_1 in system A, the function of obtaining the refresh information of system B will be triggered. Then, an Iframe container will be created on page A1, and global positioning and height and width settings will be performed to generate page A2 with the address A_Adress_2. Message messages will be listened to through window.addEventListener (this method is used to add an event listener to a specified element or object) to determine whether there is refresh information N in the message sent by the Iframe container. If so, the refresh information N in the message will be obtained, and after the refresh information N is obtained on page A1, the Iframe container will be closed and the message listening will be removed, and then page A1 of system A will be partially refreshed through the refresh information N.
[0058] If it does not exist, create the address of the third-party system B page, and splice the jump address A_Adress_2 into the address to form the target address; the target container will load the target address to start system B, so that system B generates the refresh information N required for page A1, and splice the refresh information N into the jump address A_Adress_2 to obtain the new target address; the target container jumps to page A2 based on the jump address A_Adress_2 in the new target address, triggering page A2 to obtain the refresh information N carried in the new target address; page A2 notifies the parent layer system A of the refresh information N in the form of a message through PostMessage; and page A1 in system A obtains the refresh information N in the message through message monitoring, and after page A1 obtains the refresh information N, it stores the refresh information N, closes the Iframe container and removes the message monitoring, and then partially refreshes page A1 of system A through the refresh information N.
[0059] In summary, this embodiment loads the third-party system B through the container and sets the callback address of system A. When the container jumps to the address of system A, the message is notified to the parent system A through PostMessage. System A can obtain the refresh information of the third party and perform a partial refresh without reloading the current page, thereby ensuring that the operation information of the current page including the memory status is still retained after the jump to the third-party system B and the login is successful.
[0060] In a second aspect, an embodiment of the present application further provides a device for partially refreshing a page jump between multiple systems.
[0061] In one embodiment, the device for partially refreshing a page jump between multiple systems includes:
[0062] A first processing module, configured to create a target container and construct a second page on the first target system when a local refresh requirement exists on the first page of the first target system;
[0063] A second processing module, which is used to load a target address based on a target container to start a second target system, wherein the target address includes an address of the second target system and an address of a second page;
[0064] a third processing module, configured to generate refresh information through a second target system, and create a new target address based on the refresh information and the address of the second page;
[0065] The fourth processing module is used to load the new target address based on the target container, so that the second page obtains refresh information from the new target address and transmits it to the first page, so that the first page performs partial refresh based on the refresh information.
[0066] Furthermore, in one embodiment, the address of the second page is the same as the address of the first page.
[0067] Furthermore, in one embodiment, the size of the second page is the same as the size of the first page, so that the first page is covered by the second page.
[0068] Furthermore, in one embodiment, the apparatus further includes a fifth processing module, which is configured to:
[0069] Controlling the first page to monitor messages of the target container, so that the first page obtains refresh information transmitted by the second page;
[0070] After the first page obtains the refresh information, the message monitoring is removed.
[0071] Among them, the functional implementation of each module in the above-mentioned multi-system jump page partial refresh device corresponds to the various steps in the above-mentioned multi-system jump page partial refresh method embodiment, and its functions and implementation processes are no longer repeated here.
[0072] In a third aspect, an embodiment of the present application provides a device for partially refreshing a page jump between multiple systems. The device for partially refreshing a page jump between multiple systems may be a personal computer (PC), a laptop computer, a server, or other device with data processing capabilities.
[0073] Reference Figure 3 , Figure 3 The hardware structure diagram of the multi-system jump page partial refresh device involved in the embodiment of the present application is shown in FIG. In the embodiment of the present application, the multi-system jump page partial refresh device may include a processor, a memory, a communication interface, and a communication bus.
[0074] The communication bus may be of any type and is used to interconnect the processor, the memory, and the communication interface.
[0075] The communication interface includes an input / output (I / O) interface, a physical interface, and a logical interface, etc., which are used to interconnect the devices inside the multi-system jump page partial refresh device, and an interface used to interconnect the multi-system jump page partial refresh device with other devices (such as other computing devices or user devices). The physical interface can be an Ethernet interface, an optical fiber interface, an ATM interface, etc.; the user device can be a display, a keyboard, etc.
[0076] The memory can be various types of storage media, such as random access memory (RAM), read-only memory (ROM), non-volatile RAM (NVRAM), flash memory, optical storage, hard disk, programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), etc.
[0077] The processor may be a general-purpose processor, and the general-purpose processor may call the local refresh program of the multi-system jump page stored in the memory, and execute the local refresh method of the multi-system jump page provided in the embodiment of the present application. For example, the general-purpose processor may be a central processing unit (CPU). The method executed when the local refresh program of the multi-system jump page is called may refer to the various embodiments of the local refresh method of the multi-system jump page of the present application, which will not be repeated here.
[0078] Those skilled in the art will understand that Figure 3 The hardware structure shown in the figure does not constitute a limitation on the present application, and may include more or less components than shown in the figure, or combine certain components, or arrange the components differently.
[0079] In a fourth aspect, an embodiment of the present application also provides a computer-readable storage medium.
[0080] The readable storage medium of the present application stores a local refresh program for jumping pages between multiple systems, wherein when the local refresh program for jumping pages between multiple systems is executed by a processor, the steps of the local refresh method for jumping pages between multiple systems as described above are implemented.
[0081] Among them, the method implemented when the local refresh program of the multi-system jump page is executed can refer to the various embodiments of the local refresh method of the multi-system jump page of the present application, and will not be repeated here.
[0082] It should be noted that the serial numbers of the above-mentioned embodiments of the present application are only for description and do not represent the advantages or disadvantages of the embodiments.
[0083] The terms "including" and "having" and any variations thereof in the specification and claims of this application and the above-mentioned drawings are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally includes steps or units that are not listed, or optionally includes other steps or units inherent to these processes, methods, products or devices. The terms "first", "second" and "third" are used to distinguish different objects, etc., and do not represent a sequence, nor do they limit "first", "second" and "third" to different types.
[0084] In the description of the embodiments of the present application, "exemplary", "for example" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary", "for example" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary", "for example" or "for example" is intended to present related concepts in a specific way.
[0085] In the description of the embodiments of the present application, unless otherwise specified, “ / ” means or, for example, A / B can mean A or B; the “and / or” in the text is merely a description of the association relationship of associated objects, indicating that three relationships may exist, for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of the present application, “multiple” refers to two or more than two.
[0086] In some processes described in the embodiments of the present application, multiple operations or steps that appear in a specific order are included, but it should be understood that these operations or steps may not be executed in the order in which they appear in the embodiments of the present application or in parallel, and the sequence number of the operation is only used to distinguish the different operations, and the sequence number itself does not represent any execution order. In addition, these processes may include more or fewer operations, and these operations or steps may be executed in sequence or in parallel, and these operations or steps may be combined.
[0087] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, disk, CD) as described above, and includes a number of instructions for a terminal device to execute the methods described in each embodiment of the present application.
[0088] The above are only preferred embodiments of the present application, and are not intended to limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present application.
Claims
1. A method for partially refreshing a page jump between multiple systems, characterized in that: The following steps are involved: When there is a partial refresh requirement for the first page of the first target system, creating a target container and building a second page on the first target system; loading a target address based on the target container to start a second target system, the target address including an address of the second target system and an address of a second page; generating refresh information by a second target system, and creating a new target address based on the refresh information and the address of the second page; The new target address is loaded based on the target container, so that the second page obtains refresh information from the new target address and transmits it to the first page, so that the first page performs partial refresh based on the refresh information.
2. The method for partially refreshing a page between multiple systems as claimed in claim 1, characterized in that: The address of the second page is the same as the address of the first page.
3. The method for partially refreshing a page between multiple systems as claimed in claim 1, characterized in that: The size of the second page is the same as that of the first page, so that the first page is covered by the second page.
4. The method for partially refreshing a page between multiple systems as claimed in claim 1, characterized in that: The method further comprises: Controlling the first page to monitor messages of the target container, so that the first page obtains refresh information transmitted by the second page; After the first page obtains the refresh information, the message monitoring is removed.
5. A device for partially refreshing pages between multiple systems, characterized in that: include: A first processing module, configured to create a target container and construct a second page on the first target system when a local refresh requirement exists on the first page of the first target system; A second processing module, which is used to load a target address based on a target container to start a second target system, wherein the target address includes an address of the second target system and an address of a second page; a third processing module, configured to generate refresh information through a second target system, and create a new target address based on the refresh information and the address of the second page; The fourth processing module is used to load the new target address based on the target container, so that the second page obtains refresh information from the new target address and transmits it to the first page, so that the first page performs partial refresh based on the refresh information.
6. The device for partially refreshing a page between multiple systems as claimed in claim 5, characterized in that: The address of the second page is the same as the address of the first page.
7. The device for partially refreshing a page for jumping between multiple systems as claimed in claim 5, characterized in that: The size of the second page is the same as that of the first page, so that the first page is covered by the second page.
8. The device for partially refreshing a page between multiple systems as claimed in claim 5, characterized in that: The device also includes a fifth processing module, which is used to: Controlling the first page to monitor messages of the target container, so that the first page obtains refresh information transmitted by the second page; After the first page obtains the refresh information, the message monitoring is removed.
9. A device for partially refreshing pages between multiple systems, characterized in that: The multi-system jump page local refresh device includes a processor, a memory, and a multi-system jump page local refresh program stored in the memory and executable by the processor, wherein when the multi-system jump page local refresh program is executed by the processor, the steps of the multi-system jump page local refresh method as described in any one of claims 1 to 4 are implemented.
10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a multi-system jump page partial refresh program, wherein when the multi-system jump page partial refresh program is executed by a processor, the steps of the multi-system jump page partial refresh method according to any one of claims 1 to 4 are implemented.