A page data cross-domain interaction method, device and equipment and readable medium

Abstract

The application provides a page data cross-domain interaction method, device and equipment and readable medium, and the scheme comprises the following steps: receiving an incoming parameter of a first page, wherein the incoming parameter at least comprises to-be-sent data and a destination sending address; analyzing the incoming parameter, and forwarding the to-be-sent data in the incoming parameter to the destination sending address. The technical scheme of the embodiment can realize cross-domain data exchange between pages without the participation of a server, because the server does not need to be bridged, thereby reducing the development cost and meeting the cross-domain flow of data between multiple pages.

Description

TECHNICAL FIELD

[0001] The present application relates to the computer technical field, and particularly relates to a page data cross-domain interaction method and device, equipment and readable medium. BACKGROUND

[0002] At present, for the consideration of security level and the like, the information cannot be directly called between the web pages using the programming architecture of the JavaScript language, and sometimes the information interaction between the pages is needed in the web project development process. In order to achieve this purpose, some existing technologies adopt the web proxy mode, and some adopt the mode of participating in the server, taking the server as a transfer station for the data interaction between the pages. However, the web proxy mode increases the access pressure of the service, and in the case of large concurrency, a bottleneck is formed. The mode of participating in the server has a high development cost.

[0003] Therefore, it is necessary to provide a convenient method for realizing the cross-domain interaction between the pages in the project. SUMMARY

[0004] The embodiments of the present specification provide a page data cross-domain interaction method, device, equipment and readable medium, so as to provide a convenient method for realizing the cross-domain interaction between the pages in the project.

[0005] To solve the above technical problems, the embodiments of the present specification are implemented as follows:

[0006] The embodiments of the present specification provide a page data cross-domain interaction method, which comprises:

[0007] Receiving the incoming parameters of the first page, wherein the incoming parameters at least include the to-be-sent data and the destination sending address;

[0008] Analyzing the incoming parameters and forwarding the to-be-sent data in the incoming parameters to the destination sending address.

[0009] The embodiments of the present specification provide a page data cross-domain interaction method and device, which comprises:

[0010] The incoming parameter receiving module is used for receiving the incoming parameters of the first page, wherein the incoming parameters at least include the to-be-sent data and the destination sending address;

[0011] The incoming parameter sending module is used for analyzing the incoming parameters and forwarding the to-be-sent data in the incoming parameters to the destination sending address.

[0012] The embodiments of the present specification provide a page data cross-domain interaction device, which comprises:

[0013] At least one processor; and

[0014] a memory in communication with the at least one processor; wherein

[0015] the processor stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to:

[0016] receive incoming parameters of a first page, the incoming parameters at least including to-be-sent data and a destination sending address;

[0017] parse the incoming parameters, and forward the to-be-sent data in the incoming parameters to the destination sending address.

[0018] The computer readable medium provided by the embodiment of the present specification has computer readable instructions stored thereon, and the computer readable instructions can be executed by a processor to implement a page data cross-domain interaction method.

[0019] At least one embodiment provided in the present specification can achieve the following beneficial effects:

[0020] The technical solution of the embodiment does not need the participation of a server to realize cross-domain data exchange between pages, because without the participation of the server, the server bridging process is not needed, thereby reducing the development cost while meeting the cross-domain flow demand of data between multiple pages. At the same time, in the technical solution of the present application, the cross-domain flow of data between pages is realized based on a project platform, and the pages no longer directly interact with data, which can avoid repeated flow of data between different pages in certain technical scenarios. BRIEF DESCRIPTION OF DRAWINGS

[0021] In order to more clearly illustrate the technical solutions in the embodiments of the present specification or the prior art, the drawings needed to be used in the embodiment or prior art description will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments described in the present application, and those skilled in the art can also obtain other drawings according to these drawings without creative labor.

[0022] Figure 1 The application scenario diagram of the page data cross-domain interaction method in the embodiment of the present specification;

[0023] Figure 2 The method flowchart of the page data cross-domain interaction method in the embodiment of the present specification;

[0024] Figure 3 The structural diagram of the page data cross-domain interaction device corresponding to Figure 2 provided by the embodiment of the present specification;

[0025] Figure 4is a schematic diagram of a page data cross-domain interaction device provided by an embodiment of the present specification. DETAILED DESCRIPTION

[0026] In order to make the purpose, technical solutions and advantages of one or more embodiments of the present specification clearer, the technical solutions of one or more embodiments of the present specification will be described clearly and completely below in combination with specific embodiments of the present specification and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of the present specification, not all the embodiments. Based on the embodiments in the present specification, all other embodiments obtained by a person of ordinary skill in the art without making creative labor fall within the scope of protection of one or more embodiments of the present specification.

[0027] It should be understood that although the terms first, second, third, etc. may be used in the present application to describe various information, these information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other.

[0028] At present, for the consideration of security level and other aspects, the web pages using the programming architecture of JavaScript language cannot directly call information from each other, and sometimes information interaction between pages is needed in the development process of web project. The prior art generally adopts the way of web proxy and the way of user local dump to solve the problem of cross-domain access. However, the way of web proxy increases the access pressure of service, and in the case of large concurrency, it will form a bottleneck; the way of user local dump has the problem of browser compatibility.

[0029] Therefore, it is necessary to provide a convenient method for realizing cross-domain interaction between pages in a project.

[0030] In order to solve the defects in the prior art, the present scheme gives the following embodiments.

[0031] Figure 1 is a schematic diagram of the overall application scenario of a page data cross-domain interaction method in an embodiment of the present specification. As shown in Figure 1 The first page is a sub-page embedded in a project platform (the project platform can be understood as also a page), based on the actual demand under a certain scenario, the first page needs to send a message to the second page. In the technical solution of the present embodiment, the project platform acts as a data transfer station, and the pages which need to interact with each other in the project platform are pre-registered, such as the page marked as A needs to interact with the pages marked as B and C, or the page marked as B needs to send a message to the pages marked as D and E. Thus, according to the pre-registration information, the cross-domain flow of messages between pages can be realized based on the project platform.

[0032] The technical solutions provided by the embodiments of the present specification are described in detail below with reference to the accompanying drawings.

[0033] Figure 2 A flowchart of a page data cross-domain interaction method provided by the embodiments of the present specification is shown. From the perspective of a program, the execution subject of the flowchart can be a program loaded on an application terminal.

[0034] As shown in Figure 2 , the flowchart can include the following steps:

[0035] Step S202: receiving incoming parameters of a first page, the incoming parameters including at least to-be-sent data and a destination sending address.

[0036] The execution subject of this step is a project platform, which can also be understood as a page. The first page can refer to a sub-page embedded in the project platform. For example, when developing a website, another sub-page can be embedded in a page based on an iframe tag.

[0037] The incoming parameters can refer to the parameters that the first page, i.e., the page embedded in the project platform, wants to send to another page or multiple pages. For example, the first page is page A, and this page A needs to send a message to page B. When the first page sends a message to other pages based on the project platform, the message sent to the project platform needs to inform the project platform of the destination sending address of the to-be-sent data, i.e., the final receiving address of the to-be-sent data, in addition to the to-be-sent data itself.

[0038] Step S204: parsing the incoming parameters and forwarding the to-be-sent data in the incoming parameters to the destination sending address.

[0039] After receiving the incoming parameters including the to-be-sent data and the destination sending address sent by the first page, the project platform parses the incoming parameters, and finally forwards the to-be-sent data to the destination sending address according to the parsed to-be-sent data and the destination sending address. In this process, the project platform acts as a data transfer station and forwards the data, thereby realizing the flow of data between cross pages.

[0040] The technical solutions of the embodiments do not need the participation of a server to realize cross-domain data exchange between pages. Because the participation of the server is not required, the server does not need to perform bridging processing, thereby reducing development costs while meeting the cross-domain flow of data between multiple pages. At the same time, in the technical solutions of the present application, the cross-domain flow of data between pages is realized based on the project platform, and the pages no longer directly interact with each other. In some technical scenarios, this can avoid repeated flow of data between different pages.

[0041] It should be understood that in the method described in one or more embodiments of the present specification, the order of some steps can be adjusted according to actual needs, or some steps can be omitted.

[0042] Based on Figure 2 The embodiments of the present specification also provide some specific implementations of the method, which are described below.

[0043] In an optional embodiment, before receiving the incoming parameter of the first page, the first page obtains a parent window instance of the first page.

[0044] In an optional embodiment, the first page sends the incoming parameter to the project platform based on the postMessage method of the HTML5 standard.

[0045] In the embodiment, the iframe tag and the postMessage function based on the HTML5 specification are used to realize the sending of the first page to the project platform. More specifically, since the postMessage function is a window-level method, the first page is a sub-page embedded in the project platform, and the first page must first obtain the instance of the parent window of the first page before sending messages to other pages.

[0046] In an optional embodiment, before receiving the incoming parameter of the first page, the method further comprises receiving a registration message of a second page requesting to receive the incoming parameter of the first page.

[0047] In the embodiment, the first page is a sub-page embedded in the project platform, and can send messages to multiple pages based on the project platform. After receiving the to-be-sent data, the project platform needs to know the final sending address of the to-be-sent data, that is, the page receiving the to-be-sent data needs to register the behavior of receiving the to-be-sent data, so that the project platform can accurately forward the to-be-sent data based on the registration information in the subsequent stage.

[0048] In an optional embodiment, the incoming parameter further comprises a first message digest obtained by digitally signing the combined content of the to-be-sent data and the destination sending address based on a first key.

[0049] In an optional embodiment, the analyzing the incoming parameter specifically comprises: verifying the first message digest based on the public key corresponding to the first key to verify the authenticity of the sending address of the incoming parameter; performing operation on the combined content of the incoming parameter and the sending address based on a hash method to obtain a second message digest; and comparing the first message digest and the second message digest to verify the authenticity of the incoming parameter.

[0050] Through such a setting, on the one hand, the authenticity of the source of the incoming parameter is ensured, and on the other hand, whether the transmission parameter is maliciously changed in the transmission process can be verified to ensure the authenticity of the data.

[0051] In an optional embodiment, after the relevant page receives the incoming data, subsequent corresponding activities can be carried out based on the incoming data.

[0052] Based on the same idea, the present specification also provides a device corresponding to the above method. Figure 3 The present specification provides a page data cross-domain interaction device corresponding to Figure 2 The structure diagram of the page data cross-domain interaction device is shown in the figure. Figure 3 The device can include:

[0053] The incoming parameter receiving module 302 is configured to receive the incoming parameter of the first page, wherein the incoming parameter at least includes to-be-sent data and a destination sending address.

[0054] The incoming parameter sending module 304 is configured to parse the incoming parameter and forward the to-be-sent data in the incoming parameter to the destination sending address.

[0055] It can be understood that the above-mentioned modules refer to computer programs or program segments, which are used to execute one or more specific functions. In addition, the division of the above-mentioned modules does not mean that the actual program code must also be separated.

[0056] Based on the same idea, the present specification also provides a device corresponding to the above method.

[0057] Figure 4 The present specification provides a page data cross-domain interaction device corresponding to Figure 2 The structure diagram of the page data cross-domain interaction device is shown in the figure. Figure 4 The device 400 can include:

[0058] At least one processor 410; and

[0059] The memory 430 in communication connection with the at least one processor; wherein

[0060] The memory 430 stores instructions 420 executable by the at least one processor 410, and the instructions are executed by the at least one processor 410.

[0061] The instructions can enable the at least one processor 410 to:

[0062] Receive the incoming parameter of the first page, wherein the incoming parameter at least includes to-be-sent data and a destination sending address;

[0063] parsing the incoming parameter, and forwarding the to-be-sent data in the incoming parameter to the destination sending address.

[0064] Based on the same idea, the embodiments of the present specification also provide a computer readable medium corresponding to the above method. The computer readable medium stores computer readable instructions, and the computer readable instructions can be executed by a processor to implement the following method:

[0065] receiving an incoming parameter of a first page, the incoming parameter at least including to-be-sent data and a destination sending address;

[0066] parsing the incoming parameter, and forwarding the to-be-sent data in the incoming parameter to the destination sending address.

[0067] The above describes specific embodiments of the present specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in an order different than the order in the embodiments and still achieve the desired result. In addition, the processes depicted in the figures do not necessarily require the particular order shown or sequential order to achieve the desired results. In certain implementations, multitasking and parallel processing can be advantageous or possible.

[0068] Each of the embodiments in the present specification is described in a progressive manner, and the same or similar parts between each embodiment can be referred to each other.

[0069] The device, equipment and method provided by the embodiments of the present specification are corresponding, therefore, the device and equipment also have similar beneficial technical effects as the corresponding method, since the beneficial technical effects of the method have been described in detail above, therefore, the beneficial technical effects of the corresponding device and equipment will not be described here.

[0070] In the 1990s, it was relatively easy to distinguish whether an improvement in a technology was a hardware improvement (e.g., an improvement in the circuit structure of a diode, transistor, switch, etc.) or a software improvement (an improvement in a method flow). However, as technology has evolved, many improvements in method flows today can be considered as direct improvements in hardware circuit structures. Designers almost always obtain the corresponding hardware circuit structures by programming the improved method flows into hardware circuits. Therefore, it cannot be said that an improvement in a method flow cannot be implemented using hardware entity modules. For example, a programmable logic device (PLD) (e.g., a field programmable gate array (FPGA)) is an integrated circuit whose logic function is determined by user programming of the device. A designer programs a digital system "integrated" on a PLD by himself, without having to ask a chip manufacturer to design and manufacture a special integrated circuit chip. Moreover, instead of manually manufacturing integrated circuit chips, this programming is now mostly implemented using "logic compiler" software, which is similar to the software compiler used when developing programs, and the original code before compilation must also be written in a specific programming language, which is called a hardware description language (HDL), and there are many types of HDLs, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc., and the most commonly used are VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also be aware that it is easy to obtain a hardware circuit that implements a logical method flow by simply logically programming the method flow in the above-mentioned hardware description languages and programming it into an integrated circuit.

[0071] The controller can be implemented in any suitable way, for example, the controller can take the form of a microprocessor or processor and a computer readable medium storing computer readable program code, such as software or firmware, executable by the (micro)processor, logic gates, switches, an application specific integrated circuit (ASIC), a programmable logic controller and an embedded microcontroller, examples of which include but are not limited to the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20 and Silicone Labs C8051F320, the memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also know that, in addition to being implemented in pure computer readable program code, the controller can also be implemented to perform the same functions in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers and embedded microcontrollers, etc. by logically programming the method steps. Therefore, such a controller can be considered as a hardware component, and the means included therein for implementing various functions can also be considered as structures within the hardware component. Alternatively, the means for implementing various functions can even be considered as both a software module implementing a method and a structure within a hardware component.

[0072] The systems, apparatuses, modules or units illustrated by the above embodiments can be specifically implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer can be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0073] For the sake of description, the above apparatuses are described in functional division and are described respectively. Of course, the functions of the units can be implemented in the same or multiple software and / or hardware in the implementation of the present application.

[0074] Those skilled in the art will understand that the embodiments of the present application can be provided as a method, a system or a computer program product. Therefore, the present application can take the form of a complete hardware embodiment, a complete software embodiment or an embodiment combining software and hardware aspects. Moreover, the present application can take the form of a computer program product implemented on one or more computer usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer usable program code.

[0075] The computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks. Figure 1 one or more flowcharts and / or blocks in the flowcharts and / or combination thereof. Figure 1 one or more flowcharts and / or blocks in the flowcharts and / or combination thereof.

[0076] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instructions which implement the function specified in the flowchart block or blocks. Figure 1 one or more flowcharts and / or blocks in the flowcharts and / or combination thereof. Figure 1 one or more flowcharts and / or blocks in the flowcharts and / or combination thereof.

[0077] These computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks. Figure 1 one or more flowcharts and / or blocks in the flowcharts and / or combination thereof. Figure 1 one or more flowcharts and / or blocks in the flowcharts and / or combination thereof.

[0078] In one typical configuration, the computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory.

[0079] The memory can include non-persistent memory and / or volatile memory, such as random access memory (RAM) and / or cache memory, non-volatile memory, such as read-only memory (ROM), EPROM, and / or flash memory. The memory is an example of computer-readable media.

[0080] Computer-readable media includes permanent and non-permanent, movable and non-movable media that can be implemented by any method or technology to store information. The information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassette, magnetic tape disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information accessible to a computing device. According to the definition herein, computer-readable media does not include transitory media such as modulated data signals and carriers.

[0081] It should also be noted that the terms "comprising", "containing", or any other variant thereof are intended to cover non-exclusive inclusion, such that a process, method, article or apparatus that comprises a list of elements does not only include those elements, but also other elements not explicitly listed or inherent to such process, method, article or apparatus. Without more limitations, the element defined by the statement "comprising a" does not exclude the presence of additional identical elements in the process, method, article or apparatus that includes the element.

[0082] Those skilled in the art will appreciate that embodiments of the present application can be provided as a method, system or computer program product. Accordingly, the present application can take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application can take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROMs, optical storage devices, etc.) containing computer usable program code.

[0083] The present application can be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform particular tasks or implement particular abstract data types. The present application can also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communication network. In a distributed computing environment, program modules can be located in both local and remote computer storage media including memory storage devices.

[0084] The above merely provides an example of the present application, and is not intended to limit the present application. Any modification, equivalent replacement, improvement, etc. within the spirit and principle of the present application should be included in the scope of claims of the present application.

Claims

1. A method for cross-domain interaction of page data, applied to a project platform, and based on the project platform, a first page sends a message to a second page, the method comprising: receiving a registration message of the second page requesting to receive an incoming parameter of the first page; receiving the incoming parameter of the first page, the incoming parameter comprising at least to-be-sent data and a destination sending address; the destination sending address is an address of the second page; the first page is a sub-page embedded in the project platform; the second page is another sub-page in the project platform, and the second page is multiple; the incoming parameter further comprises a first message digest obtained by digitally signing a combination of the to-be-sent data and the destination sending address based on a first key; verifying the first message digest based on a public key corresponding to the first key to verify authenticity of the destination sending address of the incoming parameter; operating the combination of the to-be-sent data and the destination sending address based on a hash method to obtain a second message digest; comparing the first message digest and the second message digest to verify authenticity of the incoming parameter based on whether the first message digest and the second message digest are consistent; forwarding the to-be-sent data in the incoming parameter to the destination sending address.

2. The method of claim 1, wherein, Before receiving the incoming parameter of the first page, the first page acquires a parent window instance of the first page.

3. The method of claim 2, wherein, The first page sends the incoming parameter to the project platform based on a postMessage method of an HTML5 standard. 4.An apparatus for cross-domain interaction of page data, applied to a project platform, and based on the project platform, a first page sends a message to a second page, comprising: an incoming parameter receiving module configured to receive a registration message of the second page requesting to receive an incoming parameter of the first page; receive the incoming parameter of the first page, the incoming parameter comprising at least to-be-sent data and a destination sending address; the destination sending address is an address of the second page; the first page is a sub-page embedded in the project platform; the second page is another sub-page in the project platform, and the second page is multiple; the incoming parameter further comprises a first message digest obtained by digitally signing a combination of the to-be-sent data and the destination sending address based on a first key; an incoming parameter sending module configured to verify the first message digest based on a public key corresponding to the first key to verify authenticity of the destination sending address of the incoming parameter; operate the combination of the to-be-sent data and the destination sending address based on a hash method to obtain a second message digest; compare the first message digest and the second message digest to verify authenticity of the incoming parameter based on whether the first message digest and the second message digest are consistent; and forward the to-be-sent data in the incoming parameter to the destination sending address.

5. A page data cross-domain interaction device, applied to a project platform, and configured to enable a first page to send a message to a second page based on the project platform, comprising: at least one processor; and a memory in communication connection with the at least one processor; wherein the processor stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to: receive a registration message of the second page requesting to receive incoming parameters of the first page; receive incoming parameters of the first page, the incoming parameters comprising at least to-be-sent data and a destination sending address; the destination sending address is an address of the second page; the first page is a sub-page embedded in the project platform; the second page is another sub-page in the project platform, and the second page is multiple; the incoming parameters further comprise a first message digest obtained by digitally signing a combination of the to-be-sent data and the destination sending address based on a first key; verify the authenticity of the destination sending address of the incoming parameters based on a public key corresponding to the first key to verify the first message digest; obtain a second message digest by performing an operation on the combination of the to-be-sent data and the destination sending address based on a hash method; compare the first message digest and the second message digest, and verify the authenticity of the incoming parameters based on whether the content of the first message digest and the second message digest is consistent; forward the to-be-sent data in the incoming parameters to the destination sending address.

6. A computer readable medium having computer readable instructions stored thereon, the computer readable instructions being executable by a processor to implement the page data cross-domain interaction method of any one of claims 1-3.

Images