CN111414563B - Webpage interaction method, device, computer equipment and storage medium - Google Patents

Webpage interaction method, device, computer equipment and storage medium Download PDF

Info

Publication number
CN111414563B
CN111414563B CN202010209161.7A CN202010209161A CN111414563B CN 111414563 B CN111414563 B CN 111414563B CN 202010209161 A CN202010209161 A CN 202010209161A CN 111414563 B CN111414563 B CN 111414563B
Authority
CN
China
Prior art keywords
embedded
webpage
embedded webpage
request
interaction
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202010209161.7A
Other languages
Chinese (zh)
Other versions
CN111414563A (en
Inventor
刘俊杰
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Guangzhou Cubesili Information Technology Co Ltd
Original Assignee
Guangzhou Cubesili Information Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Guangzhou Cubesili Information Technology Co Ltd filed Critical Guangzhou Cubesili Information Technology Co Ltd
Priority to CN202010209161.7A priority Critical patent/CN111414563B/en
Publication of CN111414563A publication Critical patent/CN111414563A/en
Application granted granted Critical
Publication of CN111414563B publication Critical patent/CN111414563B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90Details of database functions independent of the retrieved data types
    • G06F16/95Retrieval from the web
    • G06F16/957Browsing optimisation, e.g. caching or content distillation
    • G06F16/9574Browsing optimisation, e.g. caching or content distillation of access to content, e.g. by caching
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90Details of database functions independent of the retrieved data types
    • G06F16/95Retrieval from the web
    • G06F16/958Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking

Abstract

The disclosure provides a webpage interaction method, a webpage interaction device, computer equipment and a storage medium, and belongs to the technical field of computers. The method comprises the following steps: the interactive management process of the application program receives an interactive request sent by the first embedded webpage, wherein the interactive request comprises an identifier of the second embedded webpage and an identifier of the request content, if the interactive management process determines that the second embedded webpage is an interactable webpage according to the identifier of the second embedded webpage, the interactive management process sends an acquisition request of the request content to the second embedded webpage, receives the request content sent by the second embedded webpage, and sends the request content sent by the second embedded webpage to the first embedded webpage. Through the method and the device, the web page display blocking can be reduced.

Description

Webpage interaction method, device, computer equipment and storage medium
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a method, an apparatus, a computer device, and a storage medium for web page interaction.
Background
In an application, two web pages in the application typically interact, and the web pages that interact may be referred to as embedded web pages.
In the related art, the interaction process of the embedded web page is as follows: the embedded webpage A sends an interaction request to a server (a background server of an application program to which the embedded webpage A belongs), wherein the interaction request comprises requested content and an address of the embedded webpage B. After receiving the interactive request, the server may obtain the requested content and the address of the embedded web page B therein. And then the server sends a content acquisition request to the embedded webpage B according to the address of the embedded webpage B. The embedded webpage B sends the content requested by the embedded webpage A to the server. And the server sends the content requested by the embedded webpage A to the embedded webpage A. Thus, the embedded web page a will obtain the content to be requested from the embedded web page B.
Because the interaction of the embedded web page needs to be participated by a server, network bandwidth needs to be occupied in communication, and thus, in the application program with high interaction, web page display of the application program is blocked due to network fluctuation.
Disclosure of Invention
The embodiment of the disclosure provides a webpage interaction method, a webpage interaction device, computer equipment and a storage medium, which can solve the problem of webpage display blocking. The technical scheme is as follows:
in a first aspect, a method for web page interaction is provided, the method comprising:
An interaction management process of an application program receives an interaction request sent by a first embedded webpage, wherein the interaction request comprises an identifier of a second embedded webpage and an identifier of a request content;
if the interaction management process determines that the second embedded webpage is an interactable webpage according to the identification of the second embedded webpage, sending an acquisition request for requesting content to the second embedded webpage;
and the interaction management process receives the request content sent by the second embedded webpage and sends the request content sent by the second embedded webpage to the first embedded webpage.
In one possible implementation, the method further includes:
and if the identifier of the second embedded webpage exists in the interactive webpage list, determining the second embedded webpage as the interactive webpage.
In one possible implementation, the method further includes:
the interaction management process receives an interaction registration request sent by the second embedded webpage when the second embedded webpage is started;
the interaction management process adds the identification of the second embedded web page to the list of interactable web pages.
In one possible implementation, the method further includes:
The interactive management process receives a modification message sent by the second embedded webpage, wherein the modification message comprises modification content;
and the interaction management process sends the modified content to a third embedded webpage, wherein the third embedded webpage is an embedded webpage for acquiring the modified content.
In one possible implementation, the embedded web page is a hypertext markup language HTML5 type embedded web page.
In a second aspect, a method for web page interaction is provided, the method comprising:
the second embedded webpage receives an acquisition request of request content sent by an interaction management process in an application program;
the second embedded webpage determines request content indicated by the acquisition request;
and the second embedded webpage sends the request content indicated by the acquisition request to the interaction management process.
In one possible implementation, the method further includes:
and the second embedded webpage sends a registration request to the interaction management process when being started, wherein the registration request comprises the identification of the second embedded webpage.
In one possible implementation, the method further includes:
the second embedded webpage receives a modification instruction of target content and obtains modification content corresponding to the target content;
And the second embedded webpage sends the modified content to the interaction management process.
In a third aspect, there is provided an apparatus for web page interaction, the apparatus comprising:
the receiving module is used for receiving an interaction request sent by the first embedded webpage, wherein the interaction request comprises an identifier of the second embedded webpage and an identifier of the request content;
the sending module is used for determining that the second embedded webpage is an interactable webpage according to the identification of the second embedded webpage, and sending an acquisition request for requesting content to the second embedded webpage;
the receiving module is further configured to receive the request content sent by the second embedded web page;
the sending module is further configured to send the request content sent by the second embedded web page to the first embedded web page.
In one possible implementation, the apparatus further includes: a determining module for:
and if the identifier of the second embedded webpage exists in the interactive webpage list, determining the second embedded webpage as the interactive webpage.
In one possible implementation manner, the receiving module is further configured to: receiving an interactive registration request sent by the second embedded webpage when the second embedded webpage is started;
The determining module is further configured to: and adding the identification of the second embedded webpage to the interactive webpage list.
In one possible implementation manner, the receiving module is further configured to: receiving a modification message sent by the second embedded webpage, wherein the modification message comprises modification content;
the sending module is further configured to: and sending the modified content to a third embedded webpage, wherein the third embedded webpage is an embedded webpage for acquiring the modified content.
In one possible implementation, the embedded web page is a hypertext markup language HTML5 type embedded web page.
In a fourth aspect, there is provided an apparatus for web page interaction, the apparatus comprising:
the receiving module is used for receiving an acquisition request of request content sent by an interaction management process in an application program;
a determining module, configured to determine a request content indicated by the acquisition request;
and the sending module is used for sending the request content indicated by the acquisition request to the interaction management process.
In a possible implementation manner, the sending module is further configured to send a registration request to an interaction management process at startup, where the registration request includes an identifier of the second embedded web page.
In a possible implementation manner, the receiving module is further configured to receive a modification instruction of the target content, and obtain modified content corresponding to the target content;
and the sending module is also used for sending the modified content to the interaction management process.
In a fifth aspect, there is provided a computer device comprising a processor and a memory having stored therein at least one computer instruction that is loaded and executed by the processor to perform the operations performed by the method of web page interaction as described in the first aspect or to perform the operations performed by the method of web page interaction as described in the second aspect.
In a sixth aspect, there is provided a computer readable storage medium having stored therein at least one computer instruction loaded and executed by a processor to implement the operations performed by the method of web page interaction as described in the first aspect or to implement the operations performed by the method of web page interaction as described in the second aspect.
The technical scheme provided by the embodiment of the disclosure has the beneficial effects that:
in the embodiment of the disclosure, when the embedded web pages in the application program are interacted, interaction can be performed through the interaction management process in the application program without passing through a background server of the application program and without occupying network bandwidth, so that the blocking of web page display can be reduced.
Drawings
FIG. 1 is a schematic view of a scenario of web page interactions provided by an embodiment of the present disclosure;
FIG. 2 is a flow chart of a method of web page interaction provided by an embodiment of the present disclosure;
FIG. 3 is a flow chart of a method of web page interaction provided by an embodiment of the present disclosure;
FIG. 4 is a schematic structural diagram of a device for web page interaction provided by an embodiment of the present disclosure;
FIG. 5 is a schematic structural diagram of a device for web page interaction provided by an embodiment of the present disclosure;
FIG. 6 is a schematic structural diagram of a device for web page interaction provided by an embodiment of the present disclosure;
fig. 7 is a schematic structural diagram of a terminal provided in an embodiment of the present disclosure.
Detailed Description
For the purposes of clarity, technical solutions and advantages of the present disclosure, the following further details the embodiments of the present disclosure with reference to the accompanying drawings.
Currently, in applications with more interactions, interactions between embedded web pages are common. And as Flash technology in applications changes to HTML (Hyper Text Markup Language ) 5 (which may be abbreviated as H5) technology, there are more and more interactive embedded web pages in applications. But they require a medium because of the cross-domain limitations of the embedded web pages, which do not allow direct establishment of communication links between the embedded web pages. In the related art, a background server (simply referred to as a server) of an application program is generally used for interaction, but an embedded web page with more interaction frequently communicates with the server, which occupies more network bandwidth and possibly causes the web page display of the application program to be blocked, so that a method for reducing the page display blocking is needed.
Embodiments of the present disclosure provide a method for web page interaction, where the execution subject of the method may be an interaction management process of an application program (also referred to as a client). The application is installed on a terminal that includes a processor, a memory, and a transceiver. The processor may be used to perform processing of the web page interaction process, the transceiver may be used to receive and transmit data during the web page interaction process, the memory may be used for data required for the web page interaction process, generated data, and the like.
As shown in fig. 1, in the embodiment of the present disclosure, an application program includes a first embedded web page, a second embedded web page, and an interaction management process. The first embedded webpage is any embedded webpage in the application program, and the second embedded webpage is any embedded webpage except the second embedded webpage in the application program. The interaction management process is used for managing interaction processing between the first embedded webpage and the second embedded webpage.
As shown in fig. 2, in an embodiment of the present disclosure, a flow of a method for web page interaction is provided:
in step 201, an interaction management process of an application program receives an interaction request sent by a first embedded webpage, where the interaction request includes an identifier of a second embedded webpage and an identifier of a requested content.
The identifier of the second embedded web page may be an address of the second embedded web page.
In this embodiment, when the first embedded web page is displayed, a part of content is requested from the second embedded web page, and an interaction request may be generated. And adding the identification of the second embedded webpage and the identification of the request content in the interactive request, wherein the request content is the content which the first embedded webpage needs to request from the second embedded webpage.
The first embedded web page may then send an interaction request to an interaction management process. And the interaction management process receives an interaction request sent by the first embedded webpage, analyzes the interaction request, and obtains the identification of the second embedded webpage and the identification of the request content.
Step 202, if the interaction management process determines that the second embedded webpage is an interactable webpage according to the identifier of the second embedded webpage, sending an acquisition request for requesting content to the second embedded webpage.
Wherein, the interactable webpage refers to an embedded webpage which can interact with other embedded webpages.
In this embodiment, the interaction management process may use the identifier of the second embedded web page to determine whether the second embedded web page is an interactable web page. If the interaction management process determines that the second embedded webpage is an interactable webpage, an acquisition request of the request content can be generated, wherein the acquisition request comprises an identification of the request content. The interactive management process may then send an acquisition request to the second embedded web page requesting content using the address of the second embedded web page.
After the second embedded webpage receives the acquisition request, the acquisition request can be analyzed to obtain the identification of the request content. And then the second embedded webpage uses the identification of the request content to determine the request content corresponding to the identification of the request content. The second embedded web page then sends the requested content to the interaction management process.
In step 203, the interaction management process receives the request content sent by the second embedded web page, and sends the request content sent by the second embedded web page to the first embedded web page.
In this embodiment, the interaction management process receives the request content sent by the second embedded web page, and may send the request content to the first embedded web page. And the first embedded webpage receives the request content, and displays the content corresponding to the request content in the first embedded webpage according to the request content. Thus, the first embedded web page receives the content to be requested from the second embedded web page.
For example, in the embodiment of fig. 2, the first embedded web page is an a web page, the second embedded web page is a B web page, the B web page is a web page triggered by buttons in the a web page, there are currently 6 buttons in the a web page, and the B web page is currently triggered by the 4 th button. When the 3 rd button is deleted by the A webpage and the B webpage is triggered again, the B webpage requests the A webpage which button the B webpage belongs to trigger through the interaction management process, and the 3 rd button is deleted by the A webpage at the moment, so that the current 3 rd button is acquired by the B webpage, and the B webpage is triggered through the 3 rd button.
Thus, the interaction medium of the embedded web page in the application program is the interaction management process in the application program, and a background server of the application program is not needed, so that the blocking of the web page can be reduced.
In one possible implementation, in step 202, the interaction management process may determine that the second embedded web page is an interactable page using:
and if the identifier of the second embedded webpage exists in the interactable webpage list, determining the second embedded webpage as the interactable webpage.
In this embodiment, an interactive web page list is stored in the interaction management process, where the interactive web page list includes an identifier of an embedded web page that can be interacted with.
The interaction management process may look at the list of interactable web pages if there is an identification of a second embedded web page. If the identifier of the second embedded webpage exists in the interactable webpage list, the interaction management process can determine that the second embedded webpage is the interactable webpage. If the identification of the second embedded webpage does not exist in the interactable webpage list, the interaction management process can determine that the second embedded webpage is a non-interactable webpage.
In addition, when the interaction management process determines that the second embedded webpage is a non-interactable webpage, an acquisition failure message of the request content can be sent to the first embedded webpage. The first embedded webpage receives the acquisition failure message, and can send an acquisition request of the request content to a background server of an application program to which the first embedded webpage belongs, and acquire the request content from the second embedded webpage through the server.
In one possible implementation, in the embodiment of the present disclosure, the interactive embedded web page is to register in the interaction management process to represent itself as an interactive web page, and is processed as follows:
the interaction management process receives an interaction registration request sent by a second embedded webpage when the second embedded webpage is started; the interaction management process adds the identification of the second embedded web page to the list of interactable web pages.
In this embodiment, after the second embedded web page is started, an interactive registration request may be generated, or a stored interactive registration request may be obtained. The interactive registration request includes an identification of the second embedded web page. The second embedded web page then sends the interactive registration request to the interactive management process.
After the interactive management process receives the interactive registration request, the interactive registration request can be analyzed, and the identification of the second embedded webpage is obtained. The interaction management process then adds the identification of the second embedded web page to the list of interactable web pages.
In addition, the interactive management process may delete the interactable list each time the application to which the interactive management process belongs is closed.
In a possible implementation manner, in an embodiment of the present disclosure, after the second embedded web page modifies its own content, a processing procedure of modifying other embedded web pages including the content is also provided:
The interaction management process receives a modification message sent by the second embedded webpage, wherein the modification message comprises modification content; and the interaction management process sends the modified content to a third embedded webpage, wherein the third embedded webpage is an embedded webpage for acquiring the modified content.
In the embodiment of the disclosure, the user may modify the content of the second embedded web page during the application program, so that the second embedded web page includes the modified content. For example, the second embedded web page is a web page that includes a nickname of the user, and the user modifies the nickname in the second embedded web page, then the modified content is the modified nickname.
The second embedded web page may generate a modification message including modification content therein. The second embedded web page then sends the modification message to the interaction management process. And the interaction management process receives the modification message, analyzes the message and acquires the modification content. The interaction management process may send the modified content to all of the embedded web pages (which may be referred to as third embedded web pages) that include the modified content. Thus, all the embedded web pages for acquiring the modified content acquire the modified content.
It should be noted that, at present, some third embedded web pages may not be displayed, so the interaction management process only notifies that the modified content is available, and does not pay attention to the processing results of the embedded web pages.
In a possible implementation manner, in an embodiment of the present disclosure, after the second embedded web page modifies its own content (the modified content may be referred to as modified content), the process of broadcasting the modified content by the interaction management process is further provided:
and the interaction management process receives the modification message sent by the second embedded webpage, analyzes the message and acquires the modification content. The interaction management process may send the modified content to all embedded web pages in the application to which it belongs. Thus, the modified content is obtained from the embedded web page for which the modified content is desired to be obtained.
It should be noted that, at present, some embedded web pages for acquiring the modified content may not be displayed, so the interaction management process only notifies that the modified content is available, and does not pay attention to the processing results of the embedded web pages. In addition, it is possible that not all the embedded web pages need to acquire the modified content, so the interactive management process only notifies that the modified content exists and does not pay attention to the processing results of the embedded web pages.
In one possible implementation, the embedded web pages mentioned in the embodiments of the present disclosure are all H5 type embedded web pages.
It should be noted that, in the embodiment of the present disclosure, each time the embedded web page is opened for the first time, the initialization content needs to be obtained from the background server of the application program. When opened again later, interactions between embedded web pages may be performed by way of embodiments of the present disclosure.
In addition, in the embodiment of the present disclosure, in order to better understand the embodiment of the present disclosure, a signaling diagram as shown in fig. 3 is also provided:
step 301, a first embedded web page sends an interaction request to an interaction management process;
step 302, the interaction management process receives an interaction request;
step 303, the interaction management process determines that the second embedded webpage is an interactable webpage according to the identifier of the second embedded webpage, and sends an acquisition request for requesting content to the second embedded webpage;
step 304, the second embedded web page receives an acquisition request for the requested content;
step 305, the second embedded web page sends the request content to the interaction management process;
step 306, the interactive management process receives the request content sent by the second embedded webpage, and sends the request content sent by the second embedded webpage to the first embedded webpage;
in step 307, the first embedded web page receives the request content sent by the interactive management process.
In the embodiment of the disclosure, an interaction management process of an application program receives an interaction request sent by a first embedded webpage, wherein the interaction request comprises an identifier of a second embedded webpage and an identifier of a request content, and if the interaction management process determines that the second embedded webpage is an interactable webpage according to the identifier of the second embedded webpage, the interaction management process sends an acquisition request of the request content to the second embedded webpage. And the interaction management process receives the request content sent by the second embedded webpage and sends the request content sent by the second embedded webpage to the first embedded webpage. Therefore, when the embedded web pages in the application program are interacted, interaction can be performed through the interaction management process in the application program, a background server of the application program is not needed, network bandwidth is not needed to be occupied, and therefore blocking of web page display can be reduced.
Based on the same technical concept, the embodiment of the disclosure further provides a device for web page interaction, as shown in fig. 4, where the device includes:
a receiving module 410, configured to receive an interaction request sent by a first embedded web page, where the interaction request includes an identifier of a second embedded web page and an identifier of a requested content;
the sending module 420 is configured to send an acquisition request for requesting content to the second embedded web page if the second embedded web page is determined to be an interactable web page according to the identifier of the second embedded web page;
the receiving module 410 is further configured to receive the request content sent by the second embedded web page;
the sending module 420 is further configured to send the request content sent by the second embedded web page to the first embedded web page.
In one possible implementation, as shown in fig. 5, the apparatus further includes: a determining module 430, configured to:
and if the identifier of the second embedded webpage exists in the interactive webpage list, determining the second embedded webpage as the interactive webpage.
In one possible implementation, the receiving module 410 is further configured to: receiving an interactive registration request sent by the second embedded webpage when the second embedded webpage is started;
The determining module 430 is further configured to: and adding the identification of the second embedded webpage to the interactive webpage list.
In one possible implementation, the receiving module 410 is further configured to: receiving a modification message sent by the second embedded webpage, wherein the modification message comprises modification content;
the sending module 420 is further configured to: and sending the modified content to a third embedded webpage, wherein the third embedded webpage is an embedded webpage for acquiring the modified content.
In one possible implementation, the embedded web page is an H5 type embedded web page.
Based on the same technical concept, the embodiment of the disclosure further provides a device for web page interaction, as shown in fig. 6, where the device includes:
a receiving module 610, configured to receive an acquisition request of a request content sent by an interaction management process in an application program;
a determining module 620, configured to determine a request content indicated by the acquisition request;
and a sending module 630, configured to send, to the interaction management process, the request content indicated by the acquisition request.
In a possible implementation manner, the sending module 630 is further configured to send a registration request to an interaction management process at startup, where the registration request includes an identifier of the second embedded web page.
In a possible implementation manner, the receiving module 610 is further configured to receive a modification instruction of the target content, and obtain modified content corresponding to the target content;
the sending module 630 is further configured to send the modified content to the interaction management process.
In the embodiment of the disclosure, when the embedded web pages in the application program are interacted, interaction can be performed through the interaction management process in the application program without passing through a background server of the application program and without occupying network bandwidth, so that the blocking of web page display can be reduced.
It should be noted that: in the device for web page interaction provided in the above embodiment, only the division of the above functional modules is used for illustration, and in practical application, the above functional allocation may be performed by different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules, so as to complete all or part of the functions described above. In addition, the embodiments of the method for interaction between the device for interaction between the web page and the web page provided in the foregoing embodiments belong to the same concept, and specific implementation processes of the method embodiments are detailed in the method embodiments, which are not repeated herein.
Fig. 7 shows a block diagram of a terminal 700 provided in an exemplary embodiment of the present disclosure. The terminal 700 may be: a smart phone, a tablet computer, an MP3 player (Moving Picture Experts Group Audio Layer III, motion picture expert compression standard audio plane 3), an MP4 (Moving Picture Experts Group Audio Layer IV, motion picture expert compression standard audio plane 4) player, a notebook computer, or a desktop computer. Terminal 700 may also be referred to by other names of user devices, portable terminals, laptop terminals, desktop terminals, etc.
In general, the terminal 700 includes: a processor 701 and a memory 702.
Processor 701 may include one or more processing cores, such as a 4-core processor, an 8-core processor, and the like. The processor 701 may be implemented in at least one hardware form of DSP (Digital Signal Processing ), FPGA (Field-Programmable Gate Array, field programmable gate array), PLA (Programmable Logic Array ). The processor 701 may also include a main processor, which is a processor for processing data in an awake state, also referred to as a CPU (Central Processing Unit ); a coprocessor is a low-power processor for processing data in a standby state. In some embodiments, the processor 701 may integrate a GPU (Graphics Processing Unit, image processor) for rendering and drawing of content required to be displayed by the display screen. In some embodiments, the processor 701 may also include an AI (Artificial Intelligence ) processor for processing computing operations related to machine learning.
Memory 702 may include one or more computer-readable storage media, which may be non-transitory. The memory 702 may also include high-speed random access memory, as well as non-volatile memory, such as one or more magnetic disk storage devices, flash memory storage devices. In some embodiments, a non-transitory computer readable storage medium in memory 702 is used to store at least one instruction for execution by processor 701 to implement the methods of web page interaction provided by the method embodiments of the present disclosure.
In some embodiments, the terminal 700 may further optionally include: a peripheral interface 703 and at least one peripheral. The processor 701, the memory 702, and the peripheral interface 703 may be connected by a bus or signal lines. The individual peripheral devices may be connected to the peripheral device interface 703 via buses, signal lines or a circuit board. Specifically, the peripheral device includes: at least one of radio frequency circuitry 704, touch display 705, camera 706, audio circuitry 707, positioning component 708, and power supply 709.
A peripheral interface 703 may be used to connect I/O (Input/Output) related at least one peripheral device to the processor 701 and memory 702. In some embodiments, the processor 701, memory 702, and peripheral interface 703 are integrated on the same chip or circuit board; in some other embodiments, either or both of the processor 701, the memory 702, and the peripheral interface 703 may be implemented on separate chips or circuit boards, which is not limited in this embodiment.
The Radio Frequency circuit 704 is configured to receive and transmit RF (Radio Frequency) signals, also referred to as electromagnetic signals. The radio frequency circuitry 704 communicates with a communication network and other communication devices via electromagnetic signals. The radio frequency circuit 704 converts an electrical signal into an electromagnetic signal for transmission, or converts a received electromagnetic signal into an electrical signal. Optionally, the radio frequency circuit 704 includes: antenna systems, RF transceivers, one or more amplifiers, tuners, oscillators, digital signal processors, codec chipsets, subscriber identity module cards, and so forth. The radio frequency circuitry 704 may communicate with other terminals via at least one wireless communication protocol. The wireless communication protocol includes, but is not limited to: metropolitan area networks, various generations of mobile communication networks (2G, 3G, 4G, and 5G), wireless local area networks, and/or WiFi (Wireless Fidelity ) networks. In some embodiments, the radio frequency circuitry 704 may also include NFC (Near Field Communication ) related circuitry, which is not limited by the present disclosure.
The display screen 705 is used to display a UI (User Interface). The UI may include graphics, text, icons, video, and any combination thereof. When the display 705 is a touch display, the display 705 also has the ability to collect touch signals at or above the surface of the display 705. The touch signal may be input to the processor 701 as a control signal for processing. At this time, the display 705 may also be used to provide virtual buttons and/or virtual keyboards, also referred to as soft buttons and/or soft keyboards. In some embodiments, the display 705 may be one, providing a front panel of the terminal 700; in other embodiments, the display 705 may be at least two, respectively disposed on different surfaces of the terminal 700 or in a folded design; in still other embodiments, the display 705 may be a flexible display disposed on a curved surface or a folded surface of the terminal 700. Even more, the display 705 may be arranged in a non-rectangular irregular pattern, i.e. a shaped screen. The display 705 may be made of LCD (Liquid Crystal Display ), OLED (Organic Light-Emitting Diode) or other materials.
The camera assembly 706 is used to capture images or video. Optionally, the camera assembly 706 includes a front camera and a rear camera. Typically, the front camera is disposed on the front panel of the terminal and the rear camera is disposed on the rear surface of the terminal. In some embodiments, the at least two rear cameras are any one of a main camera, a depth camera, a wide-angle camera and a tele camera, so as to realize that the main camera and the depth camera are fused to realize a background blurring function, and the main camera and the wide-angle camera are fused to realize a panoramic shooting and Virtual Reality (VR) shooting function or other fusion shooting functions. In some embodiments, camera assembly 706 may also include a flash. The flash lamp can be a single-color temperature flash lamp or a double-color temperature flash lamp. The dual-color temperature flash lamp refers to a combination of a warm light flash lamp and a cold light flash lamp, and can be used for light compensation under different color temperatures.
The audio circuit 707 may include a microphone and a speaker. The microphone is used for collecting sound waves of users and environments, converting the sound waves into electric signals, and inputting the electric signals to the processor 701 for processing, or inputting the electric signals to the radio frequency circuit 704 for voice communication. For the purpose of stereo acquisition or noise reduction, a plurality of microphones may be respectively disposed at different portions of the terminal 700. The microphone may also be an array microphone or an omni-directional pickup microphone. The speaker is used to convert electrical signals from the processor 701 or the radio frequency circuit 704 into sound waves. The speaker may be a conventional thin film speaker or a piezoelectric ceramic speaker. When the speaker is a piezoelectric ceramic speaker, not only the electric signal can be converted into a sound wave audible to humans, but also the electric signal can be converted into a sound wave inaudible to humans for ranging and other purposes. In some embodiments, the audio circuit 707 may also include a headphone jack.
The location component 708 is operative to locate the current geographic location of the terminal 700 for navigation or LBS (Location Based Service, location-based services). The positioning component 708 may be a positioning component based on the United states GPS (Global Positioning System ), the Beidou system of China, the Granati system of Russia, or the Galileo system of the European Union.
A power supply 709 is used to power the various components in the terminal 700. The power supply 709 may be an alternating current, a direct current, a disposable battery, or a rechargeable battery. When the power supply 709 includes a rechargeable battery, the rechargeable battery may support wired or wireless charging. The rechargeable battery may also be used to support fast charge technology.
In some embodiments, the terminal 700 further includes one or more sensors 710. The one or more sensors 710 include, but are not limited to: acceleration sensor 711, gyroscope sensor 712, pressure sensor 713, fingerprint sensor 714, optical sensor 715, and proximity sensor 716.
The acceleration sensor 711 can detect the magnitudes of accelerations on three coordinate axes of the coordinate system established with the terminal 700. For example, the acceleration sensor 711 may be used to detect the components of the gravitational acceleration in three coordinate axes. The processor 701 may control the touch display screen 705 to display a user interface in a landscape view or a portrait view according to the gravitational acceleration signal acquired by the acceleration sensor 711. The acceleration sensor 711 may also be used for the acquisition of motion data of a game or a user.
The gyro sensor 712 may detect a body direction and a rotation angle of the terminal 700, and the gyro sensor 712 may collect a 3D motion of the user to the terminal 700 in cooperation with the acceleration sensor 711. The processor 701 may implement the following functions based on the data collected by the gyro sensor 712: motion sensing (e.g., changing UI according to a tilting operation by a user), image stabilization at shooting, game control, and inertial navigation.
The pressure sensor 713 may be disposed at a side frame of the terminal 700 and/or at a lower layer of the touch display screen 705. When the pressure sensor 713 is disposed at a side frame of the terminal 700, a grip signal of the user to the terminal 700 may be detected, and the processor 701 performs left-right hand recognition or quick operation according to the grip signal collected by the pressure sensor 713. When the pressure sensor 713 is disposed at the lower layer of the touch display screen 705, the processor 701 controls the operability control on the UI interface according to the pressure operation of the user on the touch display screen 705. The operability controls include at least one of a button control, a scroll bar control, an icon control, and a menu control.
The fingerprint sensor 714 is used to collect a fingerprint of the user, and the processor 701 identifies the identity of the user according to the fingerprint collected by the fingerprint sensor 714, or the fingerprint sensor 714 identifies the identity of the user according to the collected fingerprint. Upon recognizing that the user's identity is a trusted identity, the processor 701 authorizes the user to perform relevant sensitive operations including unlocking the screen, viewing encrypted information, downloading software, paying for and changing settings, etc. The fingerprint sensor 714 may be provided on the front, back or side of the terminal 700. When a physical key or vendor Logo is provided on the terminal 700, the fingerprint sensor 714 may be integrated with the physical key or vendor Logo.
The optical sensor 715 is used to collect the ambient light intensity. In one embodiment, the processor 701 may control the display brightness of the touch display 705 based on the ambient light intensity collected by the optical sensor 715. Specifically, when the intensity of the ambient light is high, the display brightness of the touch display screen 705 is turned up; when the ambient light intensity is low, the display brightness of the touch display screen 705 is turned down. In another embodiment, the processor 701 may also dynamically adjust the shooting parameters of the camera assembly 706 based on the ambient light intensity collected by the optical sensor 715.
A proximity sensor 716, also referred to as a distance sensor, is typically provided on the front panel of the terminal 700. The proximity sensor 716 is used to collect the distance between the user and the front of the terminal 700. In one embodiment, when the proximity sensor 716 detects that the distance between the user and the front face of the terminal 700 gradually decreases, the processor 701 controls the touch display 705 to switch from the bright screen state to the off screen state; when the proximity sensor 716 detects that the distance between the user and the front surface of the terminal 700 gradually increases, the processor 701 controls the touch display screen 705 to switch from the off-screen state to the on-screen state.
Those skilled in the art will appreciate that the structure shown in fig. 7 is not limiting of the terminal 700 and may include more or fewer components than shown, or may combine certain components, or may employ a different arrangement of components.
In an exemplary embodiment, a computer readable storage medium, such as a memory comprising instructions executable by a processor in a terminal to perform the method of web page interaction of the above embodiments is also provided. The computer readable storage medium may be non-transitory. For example, the computer readable storage medium may be a ROM (Read-Only Memory), a RAM (Random Access Memory ), a CD-ROM (Compact Disc Read-Only Memory), a magnetic tape, a floppy disk, an optical data storage device, and the like.
It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program for instructing relevant hardware, where the program may be stored in a computer readable storage medium, and the storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.
The foregoing description of the preferred embodiments of the present disclosure is provided for the purpose of illustration only, and is not intended to limit the disclosure to the particular embodiments disclosed, but on the contrary, the intention is to cover all modifications, equivalents, alternatives, and alternatives falling within the spirit and principles of the disclosure.

Claims (12)

1. A method of web page interaction, the method comprising:
an interaction management process of an application program receives an interaction request sent by a first embedded webpage, wherein the interaction request comprises an identifier of a second embedded webpage and an identifier of a request content, the interaction request is generated by the first embedded webpage when the first embedded webpage needs to request the content from the second embedded webpage for display, and the request content is the content requested by the first embedded webpage from the second embedded webpage;
if the interaction management process determines that the second embedded webpage is an interactable webpage according to the identification of the second embedded webpage, sending an acquisition request for requesting content to the second embedded webpage, wherein the interactable webpage refers to an embedded webpage capable of interacting with other embedded webpages;
the interaction management process receives the request content sent by the second embedded webpage, sends the request content sent by the second embedded webpage to the first embedded webpage, and the first embedded webpage is used for receiving the request content and displaying the content corresponding to the request content in the first embedded webpage according to the request content;
The first embedded webpage is any embedded webpage in the application program, the second embedded webpage is any embedded webpage except the first embedded webpage in the application program, and the interaction management process is used for managing interaction processing between the first embedded webpage and the second embedded webpage.
2. The method according to claim 1, wherein the method further comprises:
and if the identifier of the second embedded webpage exists in the interactive webpage list, determining the second embedded webpage as the interactive webpage.
3. The method according to claim 2, wherein the method further comprises:
the interaction management process receives an interaction registration request sent by the second embedded webpage when the second embedded webpage is started;
the interaction management process adds the identification of the second embedded web page to the list of interactable web pages.
4. A method according to any one of claims 1 to 3, further comprising:
the interactive management process receives a modification message sent by the second embedded webpage, wherein the modification message comprises modification content;
and the interaction management process sends the modified content to a third embedded webpage, wherein the third embedded webpage is an embedded webpage for acquiring the modified content.
5. A method according to any one of claims 1 to 3, wherein the embedded web page is a hypertext markup language HTML5 type embedded web page.
6. A method of web page interaction, the method comprising:
the method comprises the steps that a second embedded webpage receives an acquisition request of request content sent by an interaction management process in an application program, wherein the acquisition request is generated by the first embedded webpage when the first embedded webpage needs to request the content from the second embedded webpage for display, the interaction management process receives an interaction request sent by a first embedded webpage, the second embedded webpage is determined to be an interactable webpage according to the identification of the second embedded webpage in the interaction request, and the interactable webpage refers to the embedded webpage which can interact with other embedded webpages;
the second embedded webpage determines request content indicated by the acquisition request;
The second embedded webpage sends request content indicated by the acquisition request to the interaction management process, the interaction management process is used for sending the request content to the first embedded webpage, and the first embedded webpage is used for receiving the request content and displaying content corresponding to the request content in the first embedded webpage according to the request content;
the first embedded webpage is any embedded webpage in the application program, the second embedded webpage is any embedded webpage except the first embedded webpage in the application program, and the interaction management process is used for managing interaction processing between the first embedded webpage and the second embedded webpage.
7. The method of claim 6, wherein the method further comprises:
and the second embedded webpage sends a registration request to the interaction management process when being started, wherein the registration request comprises the identification of the second embedded webpage.
8. The method according to claim 6 or 7, characterized in that the method further comprises:
the second embedded webpage receives a modification instruction of target content and obtains modification content corresponding to the target content;
And the second embedded webpage sends the modified content to the interaction management process.
9. An apparatus for web page interaction, the apparatus comprising:
the system comprises a receiving module, a processing module and a processing module, wherein the receiving module is used for receiving an interaction request sent by a first embedded webpage, wherein the interaction request comprises an identifier of a second embedded webpage and an identifier of request content, the interaction request is generated by the first embedded webpage when the first embedded webpage needs to request content from the second embedded webpage for display, and the request content is the content requested by the first embedded webpage from the second embedded webpage;
the sending module is used for sending an acquisition request of request content to the second embedded webpage if the second embedded webpage is determined to be the interactable webpage according to the identification of the second embedded webpage, wherein the interactable webpage refers to the embedded webpage which can interact with other embedded webpages;
the receiving module is further configured to receive the request content sent by the second embedded web page;
the sending module is further configured to send the request content sent by the second embedded web page to the first embedded web page, where the first embedded web page is configured to receive the request content, and display, according to the request content, content corresponding to the request content in the first embedded web page;
The first embedded webpage is any embedded webpage in the application program, the second embedded webpage is any embedded webpage except the first embedded webpage in the application program, and the device is used for managing interaction processing between the first embedded webpage and the second embedded webpage.
10. An apparatus for web page interaction, the apparatus comprising:
the system comprises a receiving module, a receiving module and a display module, wherein the receiving module is used for receiving an acquisition request of request content sent by an interaction management process in an application program, the acquisition request is an interaction request sent by a first embedded webpage by the interaction management process, the second embedded webpage is determined to be an interactable webpage according to an identification of the second embedded webpage in the interaction request, the interaction request is generated by the first embedded webpage when the first embedded webpage needs to request content from the second embedded webpage for display, the interaction request also comprises an identification of request content, the request content is the content requested by the first embedded webpage from the second embedded webpage, and the interactable webpage refers to the embedded webpage which can interact with other embedded webpages;
A determining module, configured to determine a request content indicated by the acquisition request;
the sending module is used for sending the request content indicated by the acquisition request to the interaction management process, the interaction management process is used for sending the request content to the first embedded webpage, and the first embedded webpage is used for receiving the request content and displaying the content corresponding to the request content in the first embedded webpage according to the request content;
the first embedded webpage is any embedded webpage in the application program, the second embedded webpage is any embedded webpage except the first embedded webpage in the application program, and the interaction management process is used for managing interaction processing between the first embedded webpage and the second embedded webpage.
11. A computer device comprising a processor and a memory having stored therein at least one computer instruction that is loaded and executed by the processor to perform the operations performed by the method of web page interaction of any of claims 1 to 5 or the operations performed by the method of web page interaction of any of claims 6 to 8.
12. A computer-readable storage medium having stored therein at least one computer instruction loaded and executed by a processor to perform the operations performed by the method of web page interaction of any of claims 1 to 5 or the operations performed by the method of web page interaction of any of claims 6 to 8.
CN202010209161.7A 2020-03-23 2020-03-23 Webpage interaction method, device, computer equipment and storage medium Active CN111414563B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010209161.7A CN111414563B (en) 2020-03-23 2020-03-23 Webpage interaction method, device, computer equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010209161.7A CN111414563B (en) 2020-03-23 2020-03-23 Webpage interaction method, device, computer equipment and storage medium

Publications (2)

Publication Number Publication Date
CN111414563A CN111414563A (en) 2020-07-14
CN111414563B true CN111414563B (en) 2024-03-01

Family

ID=71493198

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010209161.7A Active CN111414563B (en) 2020-03-23 2020-03-23 Webpage interaction method, device, computer equipment and storage medium

Country Status (1)

Country Link
CN (1) CN111414563B (en)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108416021A (en) * 2018-03-06 2018-08-17 腾讯科技(深圳)有限公司 A kind of browsing device net page content processing method, device, electronic equipment and readable medium
CN110032702A (en) * 2019-04-08 2019-07-19 腾讯科技(深圳)有限公司 Webpage display process, device, equipment and storage medium
CN110110263A (en) * 2019-05-13 2019-08-09 北京三快在线科技有限公司 Webpage display process, device, terminal and storage medium
CN110276034A (en) * 2019-06-28 2019-09-24 广州酷狗计算机科技有限公司 Content item methods of exhibiting, device, computer equipment and storage medium
CN110442400A (en) * 2019-08-15 2019-11-12 网易(杭州)网络有限公司 Browser control method and device

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10565402B2 (en) * 2014-10-14 2020-02-18 Dropbox, Inc. System and method for serving online synchronized content from a sandbox domain via a temporary address
US9948709B2 (en) * 2015-01-30 2018-04-17 Akamai Technologies, Inc. Using resource timing data for server push in multiple web page transactions
US20180225715A1 (en) * 2017-02-08 2018-08-09 Arkadium, Inc. Automatic generation of interactive web page content

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108416021A (en) * 2018-03-06 2018-08-17 腾讯科技(深圳)有限公司 A kind of browsing device net page content processing method, device, electronic equipment and readable medium
CN110032702A (en) * 2019-04-08 2019-07-19 腾讯科技(深圳)有限公司 Webpage display process, device, equipment and storage medium
CN110110263A (en) * 2019-05-13 2019-08-09 北京三快在线科技有限公司 Webpage display process, device, terminal and storage medium
CN110276034A (en) * 2019-06-28 2019-09-24 广州酷狗计算机科技有限公司 Content item methods of exhibiting, device, computer equipment and storage medium
CN110442400A (en) * 2019-08-15 2019-11-12 网易(杭州)网络有限公司 Browser control method and device

Also Published As

Publication number Publication date
CN111414563A (en) 2020-07-14

Similar Documents

Publication Publication Date Title
CN110674022B (en) Behavior data acquisition method and device and storage medium
CN110368689B (en) Game interface display method, system, electronic equipment and storage medium
CN110278464B (en) Method and device for displaying list
CN113204298B (en) Method and device for displaying release progress, electronic equipment and storage medium
CN110740340B (en) Video live broadcast method and device and storage medium
CN111177013B (en) Log data acquisition method, device, computer equipment and storage medium
CN110851823B (en) Data access method, device, terminal and storage medium
CN111159604A (en) Picture resource loading method and device
CN111510482B (en) Method and device for determining failed network request and computer storage medium
CN109783176B (en) Page switching method and device
CN111625315A (en) Page display method and device, electronic equipment and storage medium
CN109614563B (en) Method, device and equipment for displaying webpage and storage medium
CN111008083B (en) Page communication method and device, electronic equipment and storage medium
CN111275607A (en) Interface display method and device, computer equipment and storage medium
CN114143280B (en) Session display method and device, electronic equipment and storage medium
CN113377647B (en) Page processing method, device, server, terminal and readable storage medium
CN113051015B (en) Page rendering method and device, electronic equipment and storage medium
CN110971692B (en) Method and device for opening service and computer storage medium
CN113836426A (en) Information pushing method and device and electronic equipment
CN111158780B (en) Method, device, electronic equipment and medium for storing application data
CN112988254B (en) Method, device and equipment for managing hardware equipment
CN111414563B (en) Webpage interaction method, device, computer equipment and storage medium
CN109189525B (en) Method, device and equipment for loading sub-page and computer readable storage medium
CN111241451A (en) Webpage processing method and device, computer equipment and storage medium
CN111010732A (en) Network registration method, device, electronic equipment and medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
TA01 Transfer of patent application right

Effective date of registration: 20210111

Address after: 511442 3108, 79 Wanbo 2nd Road, Nancun Town, Panyu District, Guangzhou City, Guangdong Province

Applicant after: GUANGZHOU CUBESILI INFORMATION TECHNOLOGY Co.,Ltd.

Address before: 511446 24 / F, building B-1, Wanda Plaza, Panyu District, Guangzhou City, Guangdong Province

Applicant before: GUANGZHOU HUADUO NETWORK TECHNOLOGY Co.,Ltd.

TA01 Transfer of patent application right
EE01 Entry into force of recordation of patent licensing contract

Application publication date: 20200714

Assignee: GUANGZHOU HUADUO NETWORK TECHNOLOGY Co.,Ltd.

Assignor: GUANGZHOU CUBESILI INFORMATION TECHNOLOGY Co.,Ltd.

Contract record no.: X2021440000054

Denomination of invention: Method, device, computer device and storage medium for web page interaction

License type: Common License

Record date: 20210208

EE01 Entry into force of recordation of patent licensing contract
GR01 Patent grant
GR01 Patent grant