CN114510308A

CN114510308A - Method, device, equipment and medium for storing application page by mobile terminal

Info

Publication number: CN114510308A
Application number: CN202210107729.3A
Authority: CN
Inventors: 田聪; 汤玉民
Original assignee: Beijing Baidu Netcom Science and Technology Co Ltd
Current assignee: Beijing Baidu Netcom Science and Technology Co Ltd
Priority date: 2022-01-28
Filing date: 2022-01-28
Publication date: 2022-05-17
Anticipated expiration: 2042-01-28
Also published as: CN114510308B

Abstract

The disclosure provides a method, a device, electronic equipment, a storage medium and a program product for storing an application page in a mobile terminal, and relates to the computer technology, in particular to the field of mobile terminal application. The implementation scheme is as follows: receiving a request for storing a target page displayed in an application program; responding to the request, determining a control type of a control for displaying the page content in the target page, wherein the control type indicates whether the control is a native control of an operating system of the mobile terminal; executing an obtaining operation corresponding to the control type to obtain page information of a target page, wherein the page information describes the spatial layout of the control and the page content displayed by the control; acquiring a reconstructed version of the target page based on the page information of the target page; and storing the reconstructed version as the target page.

Description

Method, device, equipment and medium for storing application page by mobile terminal

Technical Field

The present disclosure relates to the field of computer technologies, and in particular, to the field of mobile terminal applications, and in particular, to a method and an apparatus for storing an application page in a mobile terminal, an electronic device, a storage medium, and a program product.

Background

In recent years, with the rapid development of computer technology, the functions of applications on mobile terminals have become more abundant, and users sometimes need to store all the contents of application pages, such as characters, pictures, and hyperlinks corresponding to the characters and pictures, when the applications are used by the mobile terminals. However, in the current scheme, the application page is stored based on the webpage side, and the scheme for storing the application page of the mobile terminal aiming at the application of the mobile terminal is not available, so that the page information in the application program cannot be stored in the mobile terminal, and the user experience is poor.

The approaches described in this section are not necessarily approaches that have been previously conceived or pursued. Unless otherwise indicated, it should not be assumed that any of the approaches described in this section qualify as prior art merely by virtue of their inclusion in this section. Similarly, unless otherwise indicated, the problems mentioned in this section should not be considered as having been acknowledged in any prior art.

Disclosure of Invention

The present disclosure provides a method, apparatus, electronic device, computer-readable storage medium, and computer program product for content interaction with a non-native rendering engine.

According to an aspect of the present disclosure, there is provided a method for content interaction with a non-native rendering engine, the method comprising: receiving a request for storing a target page displayed in an application program; responding to the request, determining a control type of a control for displaying the page content in the target page, wherein the control type indicates whether the control is a native control of an operating system of the mobile terminal; executing an obtaining operation corresponding to the control type to obtain page information of a target page, wherein the page information describes the spatial layout of the control and the page content displayed by the control; acquiring a reconstructed version of the target page based on the page information of the target page; and storing the reconstructed version as the target page.

According to another aspect of the present disclosure, there is provided an apparatus for storing an application page in a mobile terminal, the apparatus including: a first unit configured to receive a request for storing a target page displayed in an application; the second unit is configured to respond to the request, determine a control type of a control for displaying the page content in the target page, wherein the control type indicates whether the control is a native control of an operating system of the mobile terminal; the third unit is configured to execute an obtaining operation corresponding to the control type so as to obtain page information of the target page, wherein the page information describes the spatial layout of the control and the page content displayed by the control; a fourth unit configured to obtain a reconstructed version of the target page based on the page information of the target page; and a fifth unit configured to store the reconstructed version as a target page.

According to another aspect of the present disclosure, there is provided an electronic device including: the mobile terminal comprises a memory, a processor and a computer program stored on the memory, wherein the processor is configured to execute the computer program to realize the method for storing the application page in the mobile terminal.

According to another aspect of the present disclosure, there is provided a non-transitory computer readable storage medium storing computer instructions for causing a computer to perform the above-mentioned one method of storing an application page at a mobile terminal.

According to another aspect of the present disclosure, a computer program product is provided, comprising a computer program, wherein the computer program, when executed by a processor, implements the above-mentioned method of storing application pages at a mobile terminal.

According to one or more embodiments of the disclosure, application page information is structurally stored in the mobile terminal, so that the method and the device of the embodiments of the disclosure are applicable to various operating systems and various applications of the mobile terminal, and the application page can be stored in different applications, thereby improving user experience.

It should be understood that the statements in this section do not necessarily identify key or critical features of the embodiments of the present disclosure, nor do they limit the scope of the present disclosure. Other features of the present disclosure will become apparent from the following description.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate exemplary embodiments of the embodiments and, together with the description, serve to explain the exemplary implementations of the embodiments. The illustrated embodiments are for purposes of illustration only and do not limit the scope of the claims. Throughout the drawings, identical reference numbers designate similar, but not necessarily identical, elements.

FIG. 1 illustrates a schematic diagram of an exemplary system in which various methods described herein may be implemented, according to an embodiment of the present disclosure;

FIG. 2 illustrates a flow chart of a method of storing application pages at a mobile terminal according to an embodiment of the disclosure;

FIG. 3 illustrates a flow diagram of a method of performing a get operation corresponding to a control type in the method of FIG. 2 in accordance with an embodiment of the present disclosure;

FIG. 4 shows a schematic diagram of a process for performing an acquire operation with native controls, in accordance with an embodiment of the present disclosure;

FIG. 5 is a block diagram illustrating an apparatus for storing an application page in a mobile terminal according to an embodiment of the present disclosure;

FIG. 6 illustrates a block diagram of an exemplary electronic device that can be used to implement embodiments of the present disclosure.

Detailed Description

Exemplary embodiments of the present disclosure are described below with reference to the accompanying drawings, in which various details of the embodiments of the disclosure are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope of the present disclosure. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.

In the present disclosure, unless otherwise specified, the use of the terms "first", "second", etc. to describe various elements is not intended to limit the positional relationship, the timing relationship, or the importance relationship of the elements, and such terms are used only to distinguish one element from another. In some examples, a first element and a second element may refer to the same instance of the element, and in some cases, based on the context, they may also refer to different instances.

The terminology used in the description of the various examples in this disclosure is for the purpose of describing particular examples only and is not intended to be limiting. Unless the context clearly indicates otherwise, if the number of elements is not specifically limited, the elements may be one or more. Furthermore, the term "and/or" as used in this disclosure is intended to encompass any and all possible combinations of the listed items.

When the user uses the electronic equipment, the user can generate a page for storing the current display of the electronic equipment, and the page can be a page at a webpage end or an application program page in the mobile terminal. In the prior art, no implementation scheme for saving page information in the application of the mobile terminal equipment is provided for the mobile terminal. Therefore, the use of the user is limited, and the user experience is poor.

In order to solve the above problem, the inventor proposes a method for storing an application page in a mobile terminal, which can structurally store application page information of the mobile terminal. By this means the above problems can be alleviated, reduced or even eliminated.

Embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings.

Fig. 1 illustrates a schematic diagram of an exemplary system 100 in which various methods and apparatus described herein may be implemented in accordance with embodiments of the present disclosure. Referring to fig. 1, the system 100 includes one or

more client devices

101, 102, 103, 104, 105, and 106, a server 120, and one or more communication networks 110 coupling the one or more client devices to the server 120.

Client devices

101, 102, 103, 104, 105, and 106 may be configured to execute one or more applications.

In embodiments of the present disclosure, the server 120 may run one or more services or software applications that enable performing a method of analyzing page information of a target page input by a user and generating a rebuilt version of the target page based on the page information of the target page.

In some embodiments, the server 120 may also provide other services or software applications that may include non-virtual environments and virtual environments. In certain embodiments, these services may be provided as web-based services or cloud services, for example, provided to users of

client devices

101, 102, 103, 104, 105, and/or 106 under a software as a service (SaaS) model.

In the configuration shown in fig. 1, server 120 may include one or more components that implement the functions performed by server 120. These components may include software components, hardware components, or a combination thereof, which may be executed by one or more processors. A user operating a

client device

101, 102, 103, 104, 105, and/or 106 may, in turn, utilize one or more client applications to interact with the server 120 to take advantage of the services provided by these components. It should be understood that a variety of different system configurations are possible, which may differ from system 100. Accordingly, fig. 1 is one example of a system for implementing the various methods described herein and is not intended to be limiting.

The user may use the

client device

101, 102, 103, 104, 105, and/or 106 to receive the page information of the target page input by the user and forward to the server 120, and after the page information of the target page input by the user is processed by the server 120, receive the audio information transmitted by the server and the information defining how to render the avatar, and render based on these information, outputting the avatar and the motion to the user. The client device may provide an interface that enables a user of the client device to interact with the client device. The client device may also output information to the user via the interface. Although fig. 1 depicts only six client devices, those skilled in the art will appreciate that any number of client devices may be supported by the present disclosure.

Client devices

101, 102, 103, 104, 105, and/or 106 may include various types of computer devices, such as portable handheld devices, general purpose computers (such as personal computers and laptops), workstation computers, wearable devices, smart screen devices, self-service terminal devices, service robots, gaming systems, thin clients, various messaging devices, sensors or other sensing devices, and so forth. These computer devices may run various types and versions of software applications and operating systems, such as MICROSOFT Windows, APPLE iOS, UNIX-like operating systems, Linux, or Linux-like operating systems (e.g., GOOGLE Chrome OS); or include various Mobile operating systems such as MICROSOFT Windows Mobile OS, iOS, Windows Phone, Android. Portable handheld devices may include cellular telephones, smart phones, tablets, Personal Digital Assistants (PDAs), and the like. Wearable devices may include head-mounted displays (such as smart glasses) and other devices. The gaming system may include a variety of handheld gaming devices, internet-enabled gaming devices, and the like. The client device is capable of executing a variety of different applications, such as various Internet-related applications, communication applications (e.g., email applications), Short Message Service (SMS) applications, and may use a variety of communication protocols.

Network 110 may be any type of network known to those skilled in the art that may support data communications using any of a variety of available protocols, including but not limited to TCP/IP, SNA, IPX, etc. By way of example only, one or more networks 110 may be a Local Area Network (LAN), an ethernet-based network, a token ring, a Wide Area Network (WAN), the internet, a virtual network, a Virtual Private Network (VPN), an intranet, an extranet, a Public Switched Telephone Network (PSTN), an infrared network, a wireless network (e.g., bluetooth, WIFI), and/or any combination of these and/or other networks.

The server 120 may include one or more general purpose computers, special purpose server computers (e.g., PC (personal computer) servers, UNIX servers, mid-end servers), blade servers, mainframe computers, server clusters, or any other suitable arrangement and/or combination. The server 120 may include one or more virtual machines running a virtual operating system, or other computing architecture involving virtualization (e.g., one or more flexible pools of logical storage that may be virtualized to maintain virtual storage for the server). In various embodiments, the server 120 may run one or more services or software applications that provide the functionality described below.

The computing units in server 120 may run one or more operating systems including any of the operating systems described above, as well as any commercially available server operating systems. The server 120 may also run any of a variety of additional server applications and/or middle tier applications, including HTTP servers, FTP servers, CGI servers, JAVA servers, database servers, and the like.

In some implementations, the server 120 may include one or more applications to analyze and consolidate data feeds and/or event updates received from users of the

client devices

101, 102, 103, 104, 105, and 106. Server 120 may also include one or more applications to display data feeds and/or real-time events via one or more display devices of

client devices

101, 102, 103, 104, 105, and 106.

In some embodiments, the server 120 may be a server of a distributed system, or a server incorporating a blockchain. The server 120 may also be a cloud server, or a smart cloud computing server or a smart cloud host with artificial intelligence technology. The cloud Server is a host product in a cloud computing service system, and is used for solving the defects of high management difficulty and weak service expansibility in the conventional physical host and Virtual Private Server (VPS) service.

The system 100 may also include one or more databases 130. In some embodiments, these databases may be used to store data and other information. For example, one or more of the databases 130 may be used to store information such as audio files and video files. The data store 130 may reside in various locations. For example, the data store used by the server 120 may be local to the server 120, or may be remote from the server 120 and may communicate with the server 120 via a network-based or dedicated connection. The data store 130 may be of different types. In certain embodiments, the data store used by the server 120 may be a database, such as a relational database. One or more of these databases may store, update, and retrieve data to and from the database in response to the command.

In some embodiments, one or more of the databases 130 may also be used by applications to store application data. The databases used by the application may be different types of databases, such as key-value stores, object stores, or regular stores supported by a file system.

The system 100 of fig. 1 may be configured and operated in various ways to enable application of the various methods and apparatus described in accordance with the present disclosure.

According to an aspect of the present disclosure, a method of storing an application page at a mobile terminal is provided. FIG. 2 shows a flow diagram of a method 200 of storing application pages at a mobile terminal according to an embodiment of the disclosure. The method 200 may be applied to any of the

client devices

101, 102, 103, 104, 105, and 106 in fig. 1. As shown in fig. 2, the method 200 may include the steps of:

in step 201, a request to store a target page exposed within an application is received.

In one example, when using the mobile terminal device, the user may issue a request to the mobile terminal device to save the target page by means of, for example, a gesture, voice, key pressing, or touch. It will be appreciated that the target page is not only the page of the application that the user is browsing, but may also be a page within the application that the user specifies.

In step 202, in response to the request, a control type of a control for showing the page content in the target page is determined, wherein the control type indicates whether the control is a native control of an operating system of the mobile terminal.

At present, an application program of a mobile terminal displays page information through a control. The application program on the mobile terminal device mainly uses two controls, namely a Webview control and a native control of an operating system of the mobile terminal. Therefore, when the application program is implemented by different controls, the page information of the application program needs to be acquired through different schemes.

In one example, after receiving the storage request, the mobile terminal device can determine the control type for displaying the page content in the target page by capturing a data packet of the application program and analyzing the data packet.

Alternatively or additionally, in another example, the mobile terminal device may also determine a control type for exposing page content in the target page by analyzing code of the application page layout boundary interface.

In step 203, an obtaining operation corresponding to the control type is executed to obtain page information of the target page, where the page information describes the spatial layout of the control and the page content displayed by the control.

In some examples, the page information includes, but is not limited to, size information of the controls, mutual positional relationship information between the controls, and information whether the controls are visible, and text information and picture information presented by the controls.

The execution of the obtaining operation corresponding to the control type in step 203 will be described in detail later with reference to fig. 3 and 4.

In step 204, a reconstructed version of the target page is obtained based on the page information of the target page.

According to some embodiments, the mobile terminal sends page information of the target page to the server.

In some examples, after obtaining information such as size information of the controls, mutual position relationship information between the controls, and whether the controls are visible, and page information of a target page such as text information and picture information displayed by the controls, the mobile terminal sends all data to the server through a data packet.

According to some embodiments, a rebuilt version is received from a server, wherein the rebuilt version is generated by the server de-redundantly separating page information of a target page and rebuilding the page based on the de-redundantly separated page information.

In some examples, the server first removes the redundant page information after receiving the data packet containing the page information sent by the mobile terminal. In some examples, the repeated page information may be page information of a target page, such as size information of the controls, mutual position relationship information between the controls, and whether the controls are visible, and text information and picture information presented by the controls, which are repeatedly acquired by the mobile terminal when the page information is acquired. And finally, reconstructing the page based on the page information with the redundancy removed to obtain a reconstructed version of the target page.

In step 205, the reconstructed version is stored as the target page.

And after obtaining the reconstructed version of the target page, the server sends the reconstructed version to the mobile terminal equipment. And the mobile terminal equipment stores the rebuilt version after receiving the rebuilt version.

By the method, the pages of the application program are saved in the mobile terminal, and pictures and characters in the saved pages can be copied.

Fig. 3 illustrates a flow diagram of a get operation method 203 corresponding to a control type in execution in the method 200 of fig. 2, in accordance with an embodiment of the present disclosure. The method 203 may include the following steps.

In step 301, in response to that the control type indication control is a native control of an operating system of the mobile terminal, page information of an initial page corresponding to the target page is obtained, where the initial page is a page displayed in the application program when the request is received.

Referring to fig. 4, fig. 4 shows a schematic diagram of a process 400 for performing an acquire operation with native controls, according to an embodiment of the present disclosure. In FIG. 4, 402-409 are all different child controls. 401 is a slide control and 403-405 is a child control of 401. Page 410 and page 411 show two pages of an application of the mobile terminal, respectively.

In one example, page 410 is the page at the time the mobile terminal receives a storage request for a presentation page within an application. After the mobile terminal determines that the control for exposing the page of the application is a native control, the mobile terminal may obtain all of the page information in the page 410.

In step 302, at least one of the native controls for controlling the sliding operation is determined.

With continued reference to the previous example, after obtaining the page information, the mobile terminal may also determine whether a slider control exists on the page 410. In fig. 4, the mobile terminal also determines a slider control 401.

In step 303, for each slide control, page information of a plurality of additional pages obtained after the slide operation of the slide control is performed on the basis of the initial page is obtained.

Continuing with the previous example, in FIG. 4, page 411 is slid with respect to slider control 401 in page 410. In page 411, it can be seen that child control 403 is now hidden because of sliding, but a new child control 409 is loaded. At this point page 411 may be considered an additional page to the initial page. After the page 410 is changed to the page 411, the mobile terminal also acquires page information of the page 411.

In practice, some texts and pictures of the application program in the mobile terminal device are accompanied by hyperlinks for jumping to corresponding pages, so that the page information also includes hyperlink information presented by the native widget.

According to some embodiments, the page information of the target page includes hyperlink information exposed by the native widget, and performing the obtaining operation corresponding to the widget type further includes: and traversing and clicking each child control of any one of the native controls to obtain hyperlink information displayed by any one of the native controls.

In the example of FIG. 4, all of the

controls

401 and 409 in the page 401 are native controls. In order to obtain the hyperlink of the page information, the mobile terminal may perform traversal clicking on all the child controls 402 and 408 displayed in the page 410 in a JS injection manner. And finally, obtaining the hyperlink information of the page information through the feedback result.

At present, pages of a plurality of mobile terminal application programs also show page contents through a Webview control, so that the Webview control is widely used in the application programs of the mobile terminals.

According to some embodiments, in step 203, performing the obtaining operation corresponding to the control type may include: and responding to the control type indication control as a Webview control different from the native control of the operating system of the mobile terminal, and acquiring page information of the target page.

Since Webview is used for displaying pages by loading html files, the mobile terminal can directly acquire all contents including an initial page and all additional pages when acquiring page information.

According to some embodiments, the page information of the target page includes hyperlink information exposed by the Webview control, and performing the obtaining operation corresponding to the control type further includes: and traversing and clicking each sub-control in any one Webview control to obtain hyperlink information displayed by any one Webview.

In one example, all of the

controls

401 and 409 in the page 401 are Webview controls. Referring to fig. 4, in order to obtain the hyperlink of the page information, the mobile terminal further performs traversal clicking on all the

child widgets

402 and 408 shown in the page 410 by means of JS injection. And finally, obtaining the hyperlink information of the page information through the feedback result.

According to another aspect of the present disclosure, there is also provided an apparatus for storing an application page in a mobile terminal. Fig. 5 is a block diagram illustrating an apparatus 500 for storing an application page in a mobile terminal according to an embodiment of the present disclosure. As shown in fig. 5, the apparatus 500 includes: a first unit configured to receive a request for storing a target page displayed in an application; the second unit is configured to respond to the request, determine a control type of a control for displaying the page content in the target page, wherein the control type indicates whether the control is a native control of an operating system of the mobile terminal; the third unit is configured to execute an obtaining operation corresponding to the control type so as to obtain page information of the target page, wherein the page information describes the spatial layout of the control and the page content displayed by the control; a fourth unit configured to obtain a reconstructed version of the target page based on the page information of the target page; and a fifth unit configured to store the reconstructed version as a target page.

According to some embodiments, the third unit may comprise: the first subunit is configured to, in response to the control type indication control being a native control of an operating system of the mobile terminal, obtain page information of an initial page corresponding to the target page, where the initial page is a page displayed in the application program when the request is received. The second subunit is configured to determine at least one sliding control used for controlling the sliding operation in the native controls; and the third subunit is configured to acquire, for each slide control, page information of a plurality of additional pages obtained after the slide operation of the slide control is performed on the basis of the initial page.

According to some embodiments, the third unit may comprise: and the fourth subunit is configured to click each sub-widget of any one of the native widgets in a traversal manner to obtain hyperlink information displayed by any one of the native widgets.

According to some embodiments, the third unit may comprise: and the fifth subunit is configured to, in response to the control type indication control being a Webview control different from a native control of an operating system of the mobile terminal, acquire page information of the target page.

According to some embodiments, the third unit may comprise: and the sixth subunit is configured to click each sub-control in any one of the Webview controls in a traversing manner to obtain hyperlink information displayed by any one of the Webview controls.

According to some embodiments, the fourth unit may include: the seventh subunit is configured to send the page information of the target page to the server; and an eighth subunit configured to receive a rebuild version from the server, wherein the rebuild version is generated by the server de-redundantly processing the page information of the target page and rebuilding the page based on the de-redundantly processed page information.

According to an embodiment of the present disclosure, there is also provided an electronic device, a readable storage medium, and a computer program product.

Referring to fig. 6, a block diagram of a structure of an electronic device 600, which may be a server or a client of the present disclosure, which is an example of a hardware device that may be applied to aspects of the present disclosure, will now be described. Electronic device is intended to represent various forms of digital electronic computer devices, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be examples only, and are not meant to limit implementations of the disclosure described and/or claimed herein.

As shown in fig. 6, the apparatus 600 includes a computing unit 601, which can perform various appropriate actions and processes according to a computer program stored in a Read Only Memory (ROM)602 or a computer program loaded from a storage unit 608 into a Random Access Memory (RAM) 603. In the RAM 603, various programs and data required for the operation of the device 600 can also be stored. The calculation unit 601, the ROM 602, and the RAM 603 are connected to each other via a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.

A number of components in the device 600 are connected to the I/O interface 605, including: an input unit 606, an output unit 607, a storage unit 608, and a communication unit 609. The input unit 606 may be any type of device capable of inputting information to the device 600, and the input unit 606 may receive input numeric or character information and generate key signal inputs related to user settings and/or function controls of the electronic device, and may include, but is not limited to, a mouse, a keyboard, a touch screen, a track pad, a track ball, a joystick, a microphone, and/or a remote control. Output unit 607 may be any type of device capable of presenting information and may include, but is not limited to, a display, speakers, a video/audio output terminal, a vibrator, and/or a printer. The storage unit 608 may include, but is not limited to, a magnetic disk, an optical disk. The communication unit 609 allows the device 600 to exchange information/data with other devices via a computer network, such as the internet, and/or various telecommunications networks, and may include, but is not limited to, a modem, a network card, an infrared communication device, a wireless communication transceiver, and/or a chipset, such as a bluetooth (TM) device, an 802.11 device, a WiFi device, a WiMax device, a cellular communication device, and/or the like.

The computing unit 601 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of the computing unit 601 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various dedicated Artificial Intelligence (AI) computing chips, various computing units running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, and so forth. The computing unit 601 performs the various methods and processes described above, such as the method 200. For example, in some embodiments, the method 200 may be implemented as a computer software program tangibly embodied in a machine-readable medium, such as the storage unit 608. In some embodiments, part or all of the computer program may be loaded and/or installed onto the device 600 via the ROM 602 and/or the communication unit 609. When the computer program is loaded into RAM 603 and executed by the computing unit 601, one or more steps of the method 200 described above may be performed. Alternatively, in other embodiments, the computing unit 601 may be configured to perform the method 200 in any other suitable manner (e.g., by means of firmware).

Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuitry, Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), system on a chip (SOCs), Complex Programmable Logic Devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.

Program code for implementing the methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowchart and/or block diagram to be performed. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package partly on the machine and partly on a remote machine or entirely on the remote machine or server.

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

To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic, speech, or tactile input.

The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), Wide Area Networks (WANs), and the Internet.

The computer system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server may be a cloud server, a server of a distributed system, or a server with a combined blockchain.

It should be understood that various forms of the flows shown above may be used, with steps reordered, added, or deleted. For example, the steps described in the present disclosure may be performed in parallel, sequentially or in different orders, and are not limited herein as long as the desired results of the technical solutions disclosed in the present disclosure can be achieved.

Although embodiments or examples of the present disclosure have been described with reference to the accompanying drawings, it is to be understood that the above-described methods, systems and apparatus are merely exemplary embodiments or examples and that the scope of the present invention is not limited by these embodiments or examples, but only by the claims as issued and their equivalents. Various elements in the embodiments or examples may be omitted or may be replaced with equivalents thereof. Further, the steps may be performed in an order different from that described in the present disclosure. Further, various elements in the embodiments or examples may be combined in various ways. It is important that as technology evolves, many of the elements described herein may be replaced with equivalent elements that appear after the present disclosure.

Claims

1. A method of storing an application page at a mobile terminal, comprising:

receiving a request for storing a target page displayed in an application program;

determining a control type of a control for displaying page content in the target page in response to the request, wherein the control type indicates whether the control is a native control of an operating system of the mobile terminal;

executing an obtaining operation corresponding to the control type to obtain page information of the target page, wherein the page information describes the spatial layout of the control and page content displayed by the control;

acquiring a reconstructed version of the target page based on the page information of the target page; and

storing the reconstructed version as the target page.

2. The method of claim 1, wherein performing the fetch operation corresponding to the control type comprises:

responding to the control type to indicate that the control is a native control of an operating system of the mobile terminal, and acquiring page information of an initial page corresponding to the target page, wherein the initial page is a page displayed in the application program when the request is received;

determining at least one of the native controls for controlling a sliding operation; and

and acquiring page information of a plurality of additional pages obtained after the sliding operation of the sliding control on the basis of the initial page for each sliding control.

3. The method of claim 2, wherein the page information of the target page includes hyperlink information exposed by the native widget, and performing the fetch operation corresponding to the widget type further comprises:

and traversing and clicking each sub-control of any native control to obtain the hyperlink information displayed by any native control.

4. The method of claim 1, wherein performing the fetch operation corresponding to the control type comprises:

and responding to the control type to indicate that the control is a Webview control different from a native control of an operating system of the mobile terminal, and acquiring page information of the target page.

5. The method of claim 4, wherein the page information of the target page includes hyperlink information exposed by the Webview widget, and performing the fetch operation corresponding to the widget type further comprises:

and traversing and clicking each sub-control in any one Webview control to obtain the hyperlink information displayed by any one Webview.

6. The method of any of claims 1-5, wherein obtaining the reconstructed version of the target page based on the page information of the target page comprises:

sending the page information of the target page to a server; and

receiving the rebuilt version from the server, wherein the rebuilt version is generated by the server de-redundantly separating page information of the target page and rebuilding the page based on the de-redundantly separated page information.

7. An apparatus for storing an application page at a mobile terminal, comprising:

a first unit configured to receive a request for storing a target page displayed within an application;

a second unit, configured to determine, in response to the request, a control type of a control for showing page content in the target page, where the control type indicates whether the control is a native control of an operating system of the mobile terminal;

a third unit, configured to execute an obtaining operation corresponding to the control type to obtain page information of the target page, where the page information describes a spatial layout of the control and page content displayed by the control;

a fourth unit, configured to obtain a reconstructed version of the target page based on the page information of the target page; and

a fifth unit configured to store the reconstructed version as the target page.

8. The apparatus of claim 7, wherein the third means comprises:

the first subunit is configured to, in response to the control type indicating that the control is a native control of an operating system of the mobile terminal, obtain page information of an initial page corresponding to the target page, where the initial page is a page displayed in the application program when the request is received;

a second subunit configured to determine at least one of the native controls for controlling a sliding operation; and

and the third subunit is configured to acquire, for each slide control, page information of a plurality of additional pages obtained after the slide operation of the slide control is performed on the basis of the initial page.

9. The apparatus of claim 8, wherein the page information of the target page comprises hyperlink information exposed by the native control, and the third means further comprises:

and the fourth subunit is configured to click each sub-widget of any one of the native widgets in a traversal manner to obtain the hyperlink information displayed by any one of the native widgets.

10. The apparatus of claim 7, wherein the third means comprises:

and the fifth subunit is configured to, in response to the control type indicating that the control is a Webview control different from a native control of an operating system of the mobile terminal, acquire page information of the target page.

11. The apparatus of claim 10, wherein the page information of the target page comprises hyperlink information exposed by the Webview control, and the third means comprises:

and the sixth subunit is configured to click each sub-control in any one of the Webview controls in a traversing manner to obtain the hyperlink information displayed by any one of the Webview controls.

12. The apparatus of any one of claims 7-11, wherein the fourth unit comprises:

a seventh subunit, configured to send page information of the target page to a server; and

an eighth subunit configured to receive the rebuilt version from the server, wherein the rebuilt version is generated by the server de-redundantly separating page information of the target page and rebuilding a page based on the de-redundantly separated page information.

13. An electronic device, comprising:

a memory, a processor, and a computer program stored on the memory,

wherein the processor is configured to execute the computer program to implement the method of any one of claims 1-6.

14. A non-transitory computer readable storage medium having computer instructions stored thereon, wherein the computer instructions, when executed by a computer, cause the computer to perform the method of any of claims 1-6.

15. A computer program product comprising a computer program, wherein the computer program, when executed by a computer, causes the computer to perform the method of any one of claims 1-6.