WO2015043476A1

WO2015043476A1 - Devices and methods for webpage display

Info

Publication number: WO2015043476A1
Application number: PCT/CN2014/087365
Authority: WO
Inventors: Hui Tang
Original assignee: Tencent Technology (Shenzhen) Company Limited
Priority date: 2013-09-26
Filing date: 2014-09-25
Publication date: 2015-04-02
Also published as: CN104142966A

Abstract

A client device may comprise a local storage medium comprises a set of instructions for webpage display, and a processor, in communication with the local storage medium. When the processor executes the set of instructions, the processor conducts functions to send to a server a first display request for displaying a target webpage, receive webpage data of the target webpage from the server, and store the webpage data in the local storage medium. When receiving a second display request for displaying the target webpage, the processor may further determine whether the local storage medium stores the webpage data; and then read the webpage data from the local storage medium and displaying the corresponding target webpage when the local storage medium stores the webpage data.

Description

DEVICES AND METHODS FOR WEBPAGE DISPLAY

Priority Statement

This application claims the priority benefit of Chinese Patent Application No. 2013104463991 filed on September 26, 2013, the disclosure of which is incorporated herein in its entirety by reference.

Field

The present disclosure relates to the field of internet technology. Specifically, the present disclosure relates to devices and methods for webpage display.

Background

With the development in the communication technology, communication client devices exhibit increasingly powerful functions. Users can take advantage of communication client devices to share information, browse webpages, talk with other users, and so on. Besides, the use frequency of client devices is also increasing gradually. Wherein, when a communication client device is displaying a webpage, the user may need to open a same webpage repeatedly due to user’s misoperation or other causes. For example, when a user is using a communication client device to browse webpage A and the communication client device receives a message, the user may quit the displayed webpage A in order to view the message. After viewing, the user may need to browse the webpage A again. For another example, after displaying webpage A with a communication client device, a user may want to browse the content in webpage A again. Then the user needs to use the communication client device again to display the webpage A. In existing communication techniques, a request should be sent to the server in which the webpage locates every time the webpage is to be displayed. Namely, repeatedly displaying a same webpage means repeatedly sending request to the server to repeatedly receive the webpage returned by the server. So, it is slow and takes much flow to display a same webpage repeatedly with the existing technique.

Summary

Example embodiments of the present disclosure provide methods and client devices for displaying webpage. The client device may store webpage date of a target webpage in a local storage medium and retrieve the webpage data offline when the target webpage is repeatedly displayed.

According to an aspect of the present disclosure, a client device may comprise a local storage medium comprising a set of instructions for webpage display, and a processor, in communication with the local storage medium. When the processor executes the set of instructions, the processor conducts functions to: send to a server a first display request for displaying a target webpage； receive webpage data of the target webpage from the server； store the webpage data in the local storage medium； when receiving a second display request for displaying the target webpage, determine whether the local storage medium stores the webpage data； and read the webpage data from the local storage medium and displaying the corresponding target webpage when the local storage medium stores the webpage data.

According to another aspect of the present disclosure, a processor-implemented method for webpage display may comprise: providing a client device to a user, the client device comprising a local storage medium； sending, by the client device, to a server a first display request for displaying a target webpage； receiving, by the client device, webpage data of the target webpage from the server； storing, by the client device, the webpage data in the local storage medium； when the client device receives a second display request for displaying the target webpage, determining, by the client device, whether the local storage medium stores the webpage data； and reading, by the client device, the webpage data from the local storage medium and displaying the corresponding target webpage when the local storage medium stores the webpage data.

According to yet another aspect of the present disclosure, a non-transitory processor-readable storage medium may comprise a set of instructions for webpage display, wherein the set of instructions, when executed by a processor, directs the processor to perform functions of: sending to a server a first display request for displaying a target webpage； receiving webpage data of the target webpage from the server； storing the webpage data in the storage medium； when the processor receives a second display request for displaying the target webpage, determining whether the storage medium stores the webpage data； and reading the webpage data from the storage medium and displaying the corresponding target webpage when the storage medium stores the webpage data.

Description of drawings

Drawings used in the description of the example embodiments and prior art are briefly introduced to make further illustration on the technical scheme of the example embodiments of this present disclosure and prior art. It is apparent that the described drawings are only for the specific the example embodiments of this present disclosure. Person of skill in the art may get other accompanying drawings according to these drawings without any creative labor.

Fig. 1 shows a flow diagram of a method for webpage display according to example embodiments of this present disclosure.

Fig. 2 shows a flow diagram of another method for webpage display according to the example embodiments of this present disclosure.

Fig. 3 and Fig. 4 show the methods for webpage display being implemented in WebView according to the example embodiments of the present disclosure.

Fig. 5 shows a structural diagram of a client device for webpage display according to the example embodiments of the present disclosure；

Fig. 6 shows a structural diagram of another client device for webpage display according to the example embodiments of the present disclosure； and

Fig. 7 illustrates a structural diagram of a client device according to the example embodiments of the present disclosure.

Detailed description

Subject matter will now be described more fully hereinafter with reference to the accompanying drawings, which form a part hereof, and which show, by way of illustration, specific example embodiments. Subject matter may, however, be embodied in a variety of different forms and, therefore, covered or claimed subject matter is intended to be construed as not being limited to any example embodiments set forth herein； example embodiments are provided merely to be illustrative. Likewise, a reasonably broad scope for claimed or covered subject matter is intended. Among other things, for example, subject matter may be embodied as methods, devices, components, or systems. The following detailed description is, therefore, not intended to be limiting on the scope of what is claimed.

Throughout the specification and claims, terms may have nuanced meanings suggested or implied in context beyond an explicitly stated meaning. Likewise, the phrase “in one embodiment” as used herein does not necessarily refer to the same embodiment and the phrase “in another embodiment” as used herein does not necessarily refer to a different embodiment. It is intended, for example, that claimed subject matter includes combinations of example embodiments in whole or in part.

In general, terminology may be understood at least in part from usage in context. For example, terms, such as “and”,“or”, or “and/or,” as used herein may include a variety of meanings that may depend at least in part upon the context in which such terms are used. Typically, “or” if used to associate a list, such as A, B or C, is intended to mean A, B, and C, here used in the inclusive sense, as well as A, B or C, here used in the exclusive sense. In addition, the term “one or more” as used herein, depending at least in part upon context, may be used to describe any feature, structure, or characteristic in a singular sense or may be used to describe combinations of features, structures or characteristics in a plural sense. Similarly, terms, such as “a,” “an,” or “the,” again, may be understood to convey a singular usage or to convey a plural usage, depending at least in part upon context. In addition, the term “based on” may be understood as not necessarily intended to convey an exclusive set of factors and may, instead, allow for existence of additional factors not necessarily expressly described, again, depending at least in part on context.

In the example embodiments of the present disclosure, the client device may be a device implementing WeChat, a social communication platform application for instant communication between its users, or other device implementing other type of instant communication client device, displaying news, and/or games and so on.

Besides, the example embodiments of the present disclosure do not limit the scope of a target webpage mentioned herein. The target webpage may be any webpage in field of internet, such as picture webpage, text webpage, video webpage, audio and video webpage, and so on. The webpage data of target webpage may be the required webpage for displaying the target webpage. For example, if the target webpage is a picture webpage, the database of the target webpage may contain picture data, text data and webpage button data, as well as other webpage data.

Fig. 7 illustrates a structural diagram of a client device according to the example embodiments of the present disclosure. The client device may be implemented as systems and/or to operate methods disclosed in the present disclosure.

The client device may include an RF (Radio Frequency) circuit 1110, one or more than one memory unit (s) 1120 of computer-readable memory media, an input unit 1130, a display unit 1140, a sensor 1150, an audio circuit 1160, a WiFi (wireless fidelity) module 1170, at least one processor 1180, and a power supply 1190. Those of ordinary skill in the art may understand that the structure of the client device shown in Fig. 7 does not constitute restrictions on the client device. Compared with what may be shown in the figure, more or fewer components may be included, or certain components may be combined, or components may be arranged differently.

The RF circuit 1110 may be configured to receive and transmit signals during the course of receiving and transmitting information and/or phone conversation. Specifically, after the RF circuit 1110 receives downlink information from a base station, it may hand off the downlink information to the processor 1180 for processing. Additionally, the RF circuit 1110 may transmit uplink data to the base station. Generally, the RF circuit 1110 may include, but may be not limited to, an antenna, at least one amplifier, a tuner, one or multiple oscillators, a subscriber identification module (SIM) card, a transceiver, a coupler, an LNA (Low Noise Amplifier), and a duplexer. The RF circuit 1110 may also communicate with a network and/or other devices via wireless communication. The wireless communication may use any communication standards or protocols available or one of ordinary skill in the art may perceive at the time of the present disclosure. For example, the wireless communication may include, but not limited to, GSM (Global System of Mobile communication), GPRS (General Packet Radio Service), CDMA (Code Division Multiple Access), WCDMA (Wideband Code Division Multiple Access), LTE (Long Term Evolution), email, and SMS (Short Messaging Service).

The memory unit 1120 may be configured to store software programs and/or modules. The software programs and/or modules may be sets of instructions to be executed by the processor 1180. The processor 1180 may execute various functional applications and data processing by running the software programs and modules stored in the memory unit 1120. The memory unit 1120 may include a program memory area and a data memory area, wherein the program memory area may store the operating system and at least one functionally required application program (such as the audio playback function and image playback function)； the data memory area may store data (such as audio data and phone book) created according to the use of the client device. Moreover, the memory unit 1120 may include high-speed random-access memory and may further include non-volatile memory, such as at least one disk memory device, flash device, or other volatile solid-state memory devices. Accordingly, the memory unit 1120 may further include a memory controller to provide the processor 1180 and the input unit 1130 with access to the memory unit 1120.

The input unit 1130 may be configured to receive information, such as numbers or characters, and create input of signals from keyboards, touch screens, mice, joysticks, optical or track balls, which are related to user configuration and function control. Specifically, the input unit 1130 may include a touch-sensitive surface 1131 and other input devices 1132. The touch-sensitive surface 1131, also called a touch screen or a touch pad, may collect touch operations by a user on or close to it (e.g., touch operations on the touch-sensitive surface 1131 or close to the touch-sensitive surface 1131 by the user using a finger, a stylus, and/or any other appropriate object or attachment) and drive corresponding connecting devices according to preset programs. The touch-sensitive surface 1131 may include two portions, a touch detection device and a touch controller. The touch detection device may be configured to detect the touch location by the user and detect the signal brought by the touch operation, and then transmit the signal to the touch controller. The touch controller may be configured to receive the touch information from the touch detection device, convert the touch information into touch point coordinates information of the place where the touch screen may be contacted, and then send the touch point coordinates information to the processor 1180. The touch controller may also receive commands sent by the processor 1180 for execution. Moreover, the touch-sensitive surface 1131 may be realized by adopting multiple types of touch-sensitive surfaces, such as resistive, capacitive, infrared, and/or surface acoustic sound wave surfaces. Besides the touch-sensitive surface 1131, the input unit 1130 may further include other input devices 1132, such as the input devices 1132 may also include, but not limited to, one or multiple types of physical keyboards, functional keys (for example, volume control buttons and switch buttons), trackballs, mice, and/or joysticks.

The display unit 1140 may be configured to display information input by the user, provided to the user, and various graphical user interfaces on the client device. These graphical user interfaces may be composed of graphics, texts, icons, videos, and/or combinations thereof. The display unit 1140 may include a display panel 1141. The display panel 1141 may be in a form of an LCD (Liquid Crystal Display), an OLED (Organic Light-Emitting Diode), or any other form available at the time of the present disclosure or one of ordinary skill in the art would have perceived at the time of the present disclosure. Furthermore, the touch-sensitive surface 1131 may cover the display panel 1141. After the touch-sensitive surface 1131 detects touch operations on it or nearby, it may transmit signals of the touch operations to the processor 1180 to determine the type of the touch event. Afterwards, according to the type of the touch event, the processor 1180 may provide corresponding visual output on the display panel 1141. In Fig. 7, the touch-sensitive surface 1131 and the display panel 1141 realize the input and output functions as two independent components. Alternatively, the touch-sensitive surface 1131 and the display panel 1141 may be integrated to realize the input and output functions.

The client device may further include at least one type of sensor 1150, for example, an optical sensor, a motion sensor, and other sensors. An optical sensor may include an environmental optical sensor and a proximity sensor, wherein the environmental optical sensor may adjust the brightness of the display panel 1141 according to the brightness of the environment, and the proximity sensor may turn off the display panel 1141 and/or back light when the client device may be moved close an ear of the user. As a type of motion sensor, a gravity acceleration sensor may detect the magnitude of acceleration in various directions (normally three axes) and may detect the magnitude of gravity and direction when it may be stationary. The gravity acceleration sensor may be used in applications of recognizing the attitude of the client device (e.g., switching screen orientation, related games, and magnetometer calibration) and functions related to vibration recognition (e.g., pedometers and tapping)； the client device may also be configured with a gyroscope, barometer, hygrometer, thermometer, infrared sensor, and other sensors.

An audio circuit 1160, a speaker 1161, and a microphone 1162 may provide audio interfaces between the user and the client device. The audio circuit 1160 may transmit the electric signals, which are converted from the received audio data, to the speaker 1161, and the speaker 1161 may convert them into the output of sound signals； on the other hand, the microphone 1162 may convert the collected sound signals into electric signals, which may be converted into audio data after they are received by the audio circuit 1160； after the audio data may be output to the processor 1180 for processing, it may be transmitted via the RF circuit 1110 to, for example, another terminal； or the audio data may be output to the memory unit 1120 for further processing. The audio circuit 1160 may further include an earplug jack to provide communication between earplugs and the client device.

WiFi may be a short-distance wireless transmission technology. Via the WiFi module 1170, the client device may help users receive and send emails, browse web pages, and visit streaming media. The WiFi module 1170 may provide the user with wireless broadband Internet access.

The processor 1180 may be the control center of the client device. The processor 1180 may connect to various parts of the entire client device utilizing various interfaces and circuits. The processor 1180 may conduct overall monitoring of the client device by running or executing the software programs and/or modules stored in the memory unit 1120, calling the data stored in the memory unit 1120, and executing various functions and processing data of the client device. The processor 1180 may include one or multiple processing core (s). The processor 1180 may integrate an application processor and a modem processor, wherein the application processor may process the operating system, user interface, and application programs, and the modem processor may process wireless communication.

The client device may further include a power supply 1190 (for example a battery), which supplies power to various components. The power supply may be logically connected to the processor 1180 via a power management system so that charging, discharging, power consumption management, and other functions may be realized via the power management system. The power supply 1190 may further include one or more than one DC or AC power supply, a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator, and other random components.

Further, the client device 1100 may also include a camera, Bluetooth module, etc., which are not shown in Fig. 7.

Fig. 1 Fig. 1 shows a flow diagram of a method for webpage display according to example embodiments of this present disclosure. The method may be implemented in an application of a social communication platform (e.g., WeChat) operated by a client device such as 1100. The method may comprise the steps as below.

S101, a client device sends to a server a first display request for displaying a target webpage.

The server may be one providing the target webpage. After the server receives the first display request, it sends webpage data of the target webpage to the client device.

S102, the client device receives webpage data of the target webpage from the server, displays the target webpage according to the webpage data and caches the webpage data into a local cache.

When the received target webpage meets some conditions, the webpage data will be stored in local cache. For example, in case that the number of times that the target webpage is displayed on the client device exceeds a predetermined number, or the received target webpage is pre-recognized webpage, such as a reliable webpage or a webpage with good comment, the webpage data will be stored in the local cache； or when the client device receives a certain instruction to save the target webpage data, the webpage data will be stored into local cache. Wherein, the local cache may be a cache, static random access memory (SRAM), dynamic random access memory (DRAM), solid state disk (SSD), or other memory device.

S103, when receiving a second display request for displaying the target webpage, the client device determines whether or not the local cache stores the webpage data according to the second browsing request； if it does, the client device reads the webpage data contained in the local cache and displays the target webpage according to the webpage data.

The step S103 may be executed after quitting the target webpage displayed in the step S102, or during display of the target webpage displayed in the step S102. Namely, when the step S103 is being executed, the client device has quitted display of the target webpage above； or when the step S103 is being executed, the client device is displaying the target webpage above.

In case that the client device receives the second display request, it determines whether there is corresponding webpage data stored in the local cache or not. If there is, the webpage data in local cache will be read in order to display the target webpage.

The second display request may be a second display request sent by other client devices, or one generated by the client device automatically, or one input by user, or the like.

Through steps above, when the client device displays the webpage again, there is no need to send request to server or to receive the webpage data sent by the server. Therefore, the display speed of target webpage is improved and the amount of data flow is reduced. Besides, there is no need to interact with server when the target webpage is displayed again, so that the target webpage can be displayed even if the instant communication client device is off-line.

The method above may be used in any device supporting client device. Namely all the devices, such as tablet, mobile phone, e-reader, remoter, in-vehicle device, internet television, wearable device, as well as other intellectual devices with network function, can be used to realize the method above.

With the technical scheme above, the webpage database is cached into the local cache when the webpage is displayed for the first time and when the webpage needs to be displayed again, it can be read directly from the cache in order to display the webpage again. The client device in the example embodiments of the present disclosure is used to display webpage repeatedly and this improves the efficiency of display and reduces flow loss.

Fig. 2 shows a flow diagram of another method for webpage display according to the example embodiments of this present disclosure. The method may be implemented in an application of a social communication platform (e.g., WeChat) operated by a client device such as 1100. The method may comprise the steps as below.

S201, a client device sends to a server a first display request for displaying a target webpage.

The first display request may be a uniform resource locator (URL) of the target webpage. For example, the client device may transmit the URL for finding the target webpage to the server.

S202, the client device receives webpage data of the target webpage from the server, displays the target webpage accordingly and caches the webpage data into a local cache.

The step of caching the webpage data into the local cache may be to cache the identification (for example, URL) of the target webpage and webpage data (e.g., content of the target webpage) of the target webpage together. Thus, when the client device needs to determine whether it visited the target webpage before, the client device may search stored webpage identifications in the local cache to find one that matches with the identification of the target webpage. When such identification is found, the corresponding webpage data will be found directly according to identification of the target webpage.

The caching the webpage data into local cache may be to cache the webpage data automatically. Namely, the webpage data is directly cached during display of the target webpage. Besides, it may be under some conditions to cache the webpage data, for example, when receiving a caching request of user for caching the webpage data； or when the target webpage is a certain type of webpage. The details are described below.

The step S202 may further comprise the following steps: the client device receives webpage data of the target webpage sent by the server and displaying the target webpage according to the webpage data； the client device receives a caching request for caching the webpage data； and the client device responds the caching request and caches the webpage data into local cache.

Wherein, the caching request may be input by a user of the client device or generated by client device automatically. For example, during display of the target webpage above, the client device may display a cache button for caching the webpage data of the current webpage. If the user needs and/or wishes to cache the webpage data, all he/she has to do is to click the button directly. Thereby, the client device can receive the caching request and store the webpage data into local cache.

The step S202 may also comprise the following steps: the client device receives webpage data of the target webpage sent by the server and displays the target webpage according to the webpage data； and the client device determines whether the target webpage is a preset webpage； if it is, the client device caches the webpage data into the local cache.

Wherein, the preset webpage may be at least one of the following: a webpage that has been repeatedly displayed for a number of times more than a predetermined number； a webpage with better credit than a preset credit, a webpage connected to a communication account of the user in the social communication platform corresponding to the client device, and so on.

Wherein, the information of the credit above may be transmitted to the client device together with the target webpage data when the target webpage data is returned by the server. The webpage that is connected to the communication account may be a webpage which includes the user’s communication account in its webpage content.

Through the steps above, it is possible to cache only the webpage data of certain webpage, which is browsed repeatedly by user.

S203, the client device receives a second display request for displaying the target webpage.

When executing the step S203, the target webpage displayed in step S202 may be closed or still be displayed. Namely, several target web pages can be displayed at a mean time.

The step may be to receive the second display request input by user or sent by other communication account.

Step S203 may comprise: the client device receives a second display request (for example, a URL of the target webpage), sent by a communication account (“a friend communication account”) in a friend list of the user’s communication account (“the first communication account”), for displaying a target webpage, in which the first communication account is corresponding to the client device. Namely, the social communication platform may comprise the user communication account of the user and the friend communication account of a friend of the user； the user communication account is associated with the friend communication account through a friend list in the user communication account； the second display request is sent from the friend communication account through the social communication platform. For example, if the friend communication account sends the URL above to the first communication account, the client device will display the target webpage corresponding to the URL； or, the client device receives the URL, user clicks the URL, and then client device receives the clicked instruction of user and displays the target webpage corresponding to the URL.

The step S203 may also comprise: the client device receives the second display request (for example, URL of target webpage) for displaying the target webpage. For example, a user inputs URL directly on the interface of client device.

S204, the client device determines whether the local cache stores the webpage data or not according to the second display request； if it does, executes the step S205, if not, executes the step S206.

In this step, the client device may read the identification of the target webpage contained in the second display request, and search the webpage data in the local cache according to the identification, for example, to search the webpage data containing the identification of the target webpage. When the webpage data above is found, the client device may determine that the local cache contains the webpage data. If the client device cannot find a stored webpage data containing the identification, it may determine that the local cache does not contain the webpage data.

S205, the client device reads the webpage data contained in local cache and displays the target webpage according to the webpage data.

When it determines that the local cache stores the webpage data, the client device will read the webpage data contained in local cache and display the target webpage according to the webpage data.

S206, the client device sends the second display request to the server.

In case that the local cache does not contain the webpage data, the step S206 will be executed. Wherein, the second display request may be the same as the first display request.

S207, the client device receives webpage data of the target webpage sent by the server and displays the target webpage according to the webpage data.

When executing step S207, the client device may also store the webpage data in the local cache.

After step S202, the method may comprise: deleting the webpage data in the local cache when the length of time the webpage data is stored in the local cache exceeds a preset time threshold. Wherein, the preset time threshold may be set by the user or automatically set in the client device, for example, 10 minutes, 30 minutes, 1 hour and so on. This step may be combined together by a condition that during this period of time the terminal device does not retrieve the webpage data more than a predetermined number of times.

Through the step above, the webpage data stored in the local cache will only be stored in the local cache for a certain period of time. The webpage data will be deleted, when the caching time exceeds the preset time threshold. For example, when executing step S204, if the time for caching the webpage data into local cache exceeds the preset time threshold, the step S204 will determine that the local cache does not contain the webpage data, and then the step S206 will be executed.

The disclosure below takes WebView browsing as an example to illustrate the steps above in details. Wherein, the WebView may be controls installed in the client device used to process URL request, load webpage, render and interact with webpage. Besides, the WebView may be installed in the terminal of client device. In case the client device needs to use the WebView, the client device will call the WebView from the terminal.

The step of the client device receiving webpage data of the target webpage sent by the server, displaying the target webpage according to the webpage data and caching the webpage data into local cache may comprise: the client device receives webpage data of the target webpage sent by the server, calls the WebView to display the target webpage according to the webpage data and caches the webpage data into local cache through the WebView. When the WebView gets the webpage data above, it may display (for example, render or display) the target webpage.

The step of determining whether the local cache stores the webpage data or not according to the second display request may comprise: the client device calling the WebView to determine whether the local cache stores the webpage data or not according to the second display request. When the WebView gets the second display request, it determines whether the local cache stores the webpage data or not according to the second display request.

The step of the client device reading the webpage data contained in local cache and displaying the target webpage according to the webpage data may comprise: the client device calling the WebView to read the webpage data contained in local cache and displays the target webpage according to the webpage data.

The above example uses WebView to make illustration rather than to limit example embodiments of the present disclosure. For example, client device may realize the steps above using other parts for webpage processing.

In technical scheme above, various available implementation methods have been introduced on basis of example embodiments above. Besides, in case that the client device in the example embodiments of the present disclosure is used to display webpage repeatedly, all the methods can improve the efficiency of display and reduce flow loss.

S301, a client device displays a target webpage, namely user accesses a target webpage, as shown in detail in Fig. 4-1.

S302, a WebView installed in the client device stores data of the target webpage locally.

S303, the client device receives from a user a request to re-access the target webpage, namely the user needs to access the target webpage again, as shown in detail in Fig. 4-2.

S304, the WebView determines whether or not webpage data of the target webpage has been stored locally.

S305, when the target webpage has been stored locally, the WebView directly calls the webpage data of the target webpage stored locally to display the target webpage, as shown in detail in Fig. 4-3.

S306, When the target webpage has not been stored locally, the WebView sends a display request to a server for displaying the target webpage.

S307, the client device receives the webpage data of the target webpage from the server and the WebView calls the webpage data of the target webpage to display the target webpage.

Fig. 5 shows a structural diagram of a client device for webpage display according to the example embodiments of the present disclosure. The client device may have a hardware structure as the client device 1100 and may functionally comprises a first requesting unit 51, a first display unit 52, a first determining unit 53 and a second display unit 53.

The first request unit 51 is configured to send to a server a first display request for displaying a target webpage.

The server above may be a server providing the target webpage. After the server receives the first display request, it will send webpage data of the target webpage to the client device.

The first display unit 52 is configured to receive webpage data of the target webpage sent by the server, display the target webpage according to the webpage data and cache the webpage data into a local cache.

The first display unit 52 may be configured to store the webpage data into the local cache when a target webpage in display is received and the target webpage meets some predetermined conditions. For example, in case that the number of times that the target webpage is displayed on the client device exceeds a predetermined number, or the received target webpage is a reliable webpage or a webpage with good review, the webpage data will be stored in the local cache； or when a predetermined instruction is received to store the target webpage, the webpage data will be cached into the local cache. Wherein, the local cache may be a cache, static random access memory (SRAM), dynamic random access memory (DRAM), solid state disk (SSD), or other memory device.

When the client device receives a second display request for displaying the target webpage, the first determining unit 53 is configured to determine according to the second display request whether the local cache stores the webpage data or not. The first determining unit 53 may execute the step after quitting the target webpage displayed by the first display unit 52, or during display of the target webpage displayed by the first display unit 52. Namely, when the first determining unit 53 is executing the step, the client device has quitted display of the target webpage above, or when the first determining unit 53 is executing the step, the client device is displaying the target webpage above.

The second display unit 54 is configured to read the webpage data contained in local cache and display the target webpage according to the webpage data, in case that the first determining unit determines that the local cache does have cached the webpage data.

In case that the client device receives the second display request, the first determining unit 53 can determine whether the requested webpage data is stored in the local cache or not. If there is, the second display unit 54 will read the webpage data in the local cache in order to display the target webpage.

With the units above, when the client device displays the target webpage again, there is no need to send request to the server or to receive the webpage data from the server. Therefore, the display speed of target webpage is improved and flow loss is reduced. Besides, there is no need to interact with server when the target webpage is displayed again, so that the target webpage can be displayed even if the instant communication client device is off-line.

The client device above may be used in any device supporting client device. Namely all the devices, such as tablet, mobile phone, e-reader, remoter, in-vehicle device, internet television, wearable device, as well as other intellectual devices with network function, can be configured to realize the method above.

With technical scheme above, webpage database of a webpage is cached into the local cache when the webpage is displayed for the first time, and when the webpage needs to be displayed again, it can be read directly from the cache, in order to display the webpage again. In case that the client device in the example embodiments of the present disclosure is used to display webpage repeatedly, it can improve the efficiency of display and reduce flow loss.

Fig. 6 shows a structural diagram of another client device for webpage display according to the example embodiments of the present disclosure. The client device may have a hardware structure as the client device 1100 and may functionally comprises a first requesting unit 61, a first display unit 62, a first determining unit 63, a second display unit 64, a second requesting unit 65 and a third display unit 66.

The first request unit 61 is configured to send to a server a first display request for displaying a target webpage. For example, the first request unit 61 may be configured to send a URL for finding the target webpage from the server.

The first display unit 62 is configured to receive the webpage data of the target webpage sent by the server, display the target webpage according to the webpage data and cache the webpage data into a local cache. Wherein the step of the first display unit 62 caching the webpage data into the local cache may be to cache the identification (for example, URL) and webpage data of the target webpage together. Consequently, when determining if a webpage has been stored in the local cache, the client device may be able to find the webpage data directly from the cache according to identification of the target webpage.

The step of the first display unit 62 caching the webpage data into the local cache may be to cache the webpage data automatically. Namely, the webpage data is cached directly during display of the target webpage. The client device may also cache the webpage data under some predetermined conditions. For example, the client device may cache the webpage data when receiving a caching request of user for caching the webpage data； or to cache the webpage data when the target webpage is a certain predetermined type of webpage. The details are described as below.

The first display unit 62 may include:

A first display sub-unit (not depicted in the drawings), configured to receive webpage data of the target webpage sent by the server and display the target webpage according to the webpage data；

A first receiving unit (not depicted in the drawings), configured to receive the caching request for caching the webpage data； and

A first caching unit (not depicted in the drawings), configured to respond the caching request and cache the webpage data into the local cache.

The caching request may be manually input by the user or generated by client device automatically. For example, during display of the target webpage above (for example, displaying the target webpage above), the client device may display a cache button on its screen or its keyboard and/or body for caching webpage data of the current webpage. If the user needs to cache the webpage data, all he/she has to do is to click the button directly. Thereby, the client device can receive the caching request and store the webpage data into local cache.

The first display unit 62 may further include:

A second display sub-unit (not depicted in the drawings), configured to receive webpage data of the target webpage sent by the server and display the target webpage according to the webpage data；

A second determining unit (not depicted in the drawings), configured to determine whether the target webpage is a preset webpage； and

A second caching unit (not depicted in the drawings), configured to cache the webpage data into the local cache in case that the second determining unit determines that the local cache have cached the webpage data.

Wherein, the preset webpage may be at least one of the followings: a webpage being displayed more than a predetermined number of times, a webpage with better credit than a preset credit, a webpage connected to the communication account corresponding to the communication client device, and so on.

Wherein, the information of the above credit may be transmitted to client device together when the webpage data is returned by the server. The content in webpage connected to communication account may contain the webpage of the communication account.

Through the steps above, it is possible to cache only webpage data of certain webpage, which is browsed repeatedly by the user.

The first determining unit 63 is configured to determine according to the second display request whether the local cache stores the webpage data or not, when receiving a second display request for displaying the target webpage.

When the first determining unit 63 is executing the step, the target webpage displayed by the first display unit 62 may be quitted or in display. Namely, several target web pages can be displayed at a mean time.

The first determining unit 63 may read identification of the target webpage contained in the second display request and search the webpage data in local cache according to the identification, for example, search for webpage data containing the identification of the target webpage. When the webpage data above is found, it can be determined whether the local cache contains the webpage data or not.

The second display unit 64 is configured to read the webpage data contained in local cache and display the target webpage according to the webpage data, in case that the first determining unit 63 determines that the local cache stores the webpage data.

When the first determining unit 63 determines that the local cache stores the webpage data, the second display unit 64 will read the webpage data contained in local cache and display the target webpage according to the webpage data.

The second requesting unit 65 is configured to send the second display request to server when the first determining unit 63 determines no data of the target webpage is stored in local cache.

In case that the local cache does not contain the webpage data, the second requesting unit 65 will send the second display request to server. Wherein, the second display request may be the same as the first display request.

The third display unit 66 is configured to receive webpage data of the target webpage sent by the server and display the target webpage according to the webpage data.

Of course, the webpage data may be stored in the local cache by the third display unit 66.

The client device may further include: a deleting unit (not depicted in the drawings), configured to delete the webpage data in the local cache, in case that the caching time, taken to cache the webpage data into the local cache, exceeds preset time threshold. Wherein, the preset time threshold may be set by user or automatically set in client device； for example, 10 minutes, 30 minutes, 1 hour and so on.

Through the step above, only the webpage date can only be cached in the local cache for a certain amount of time. The webpage data will be deleted, in case that the caching time exceeds a certain time.

The client device may further include the followings:

A second receiving unit (not depicted in the drawings), configured to receive a second display request (for example, URL of target webpage), sent by the communication account in friend list of a first communication account, for displaying a target webpage； in which, the first communication account is corresponding to the client device. For example, if a communication account in the friend list sends the URL above to the first communication account, the client device will display the target webpage corresponding to the URL； or, the client device receives the URL, user clicks the URL, and then client device receives the clicked instruction of user and displays the target webpage corresponding to the URL.

A third receiving unit (not depicted in accompanying drawings), configured to receive the second display request (for example, URL of target webpage) for displaying the target webpage. For example, a user inputs URL directly on the interface of client device.

The below example takes WebView as an example to illustrate the steps above in detail. Wherein, the WebView may be the controls installed in the client device configured to process URL request, load webpage, render and interact with webpage. Besides, the WebView may be installed in the terminal of client device. In case that the client device needs to use the WebView, it will call the WebView from the terminal.

The first display unit 62 may be configured to receive webpage data of the target webpage sent by the server, invoke WebView to display the target webpage according to the webpage data and cache the webpage data into local cache through the WebView.

When the WebView gets the webpage data above, it may displays (for example, render or display) the target webpage.

The first determining unit 63 may be configured to invoke the WebView to determine whether the local cache stores the webpage data or not according to the second display request.

When the WebView receives the second display request, it may determine whether the local cache stores the webpage data or not according to the second display request.

The second display unit 64 may be configured to invoke the WebView to read the webpage data contained in local cache and display the target webpage according to the webpage data.

The WebView above intends to make illustration, rather than to limit example embodiments of the present disclosure. For example, client device may realize the steps above using other parts for webpage processing.

In technical scheme above, various available implementation methods have been introduced on basis of example embodiments above. Besides, in case that the client device in the example embodiments of the present disclosure is configured to display webpage repeatedly, all the methods can improve the efficiency of display and reduce flow loss.

A person of ordinary skill in the art will understand that the whole or part of the method in the example embodiments above may be realized through relevant hardware under instruction of computer program, in which the program may be stored in a computer-readable memory medium. When the program is executed, flow processes in example embodiments of the method above may be contained. The memory medium above may be diskette, optical disk, Read-Only Memory (ROM) or Random Access Memory (RAM), or the like.

All disclosures above are the preferred the example embodiments of the present disclosure, which are not intending to limit the range of the present disclosure. Therefore, any equivalent change according to the claims of the present disclosure is still in the scope of the present disclosure.

Claims

Aclient device, comprising:

a local storage medium including a set of instructions to display webpages under a social communication platform, and

a processor, in communication with the local storage medium, wherein when the processor executes the set of instructions to:

send to a server a first display request for displaying a target webpage；

receive webpage data of the target webpage from the server；

store the webpage data in the local storage medium, and

when receiving a second display request for displaying the target webpage, determine whether the local storage medium stores the webpage data； and

read the webpage data from the local storage medium and display the corresponding target webpage when the local storage medium stores the webpage data.
The client device according to claim 1, wherein to store the webpage data in the local storage medium, the processor further conducts the functions to store a target identification associated with the target webpage as an identification of the target webpage in the local storage medium,

wherein the second display request comprises the target identification of the target webpage； and

wherein to determine whether the local storage medium stores the webpage data, the processor further conducts the functions to determine whether the received target identification matches with the stored target identification.
The client device according to claim 1, wherein to receive the webpage data from the server, the processor further conducts the functions to:

display the target webpage according to the webpage data；

receive a caching request for storing the webpage data； and

store the webpage data in the local storage medium according to the caching request.
The client device according to claim 1, wherein after receiving the webpage data from the server, the processor further conducts the functions to:

display the target webpage according to the webpage data；

determine whether the target webpage meets a predetermined condition； and

store the webpage data in the local storage medium automatically when the target webpage meets a predetermined condition.
The client device according to claim 4, wherein the predetermined condition is at least one of

when the target webpage has been displayed by the client device for more than a predetermined number of times；

the target webpage has a credit value more than a predetermined credit； and

the target webpage is associated with a communication account of the user in a social communication platform corresponding to the client device.
The client device according to anyone of claims 1, wherein the processor further conducts the functions to:

delete the webpage data from the local storage medium when the webpage data has been stored in the local storage medium longer than a predetermined period of time.
The client device according to claim 1, wherein the processor conducts the functions under a social communication platform；

the social communication platform comprises a user communication account of the user and a friend communication account of a friend of the user；

the user communication account is associated with the friend communication account through a friend list in the user communication account； and

the second display request is sent from the friend communication account through the social communication platform.
A processor-implemented method for webpage display, comprising:

providing a client device to a user, the client device comprising a local storage medium；

sending, by the client device, to a server a first display request for displaying a target webpage；

receiving, by the client device, webpage data of the target webpage from the server；

storing, by the client device, the webpage data in the local storage medium；

when the client device receives a second display request for displaying the target webpage, determining, by the client device, whether the local storage medium stores the webpage data； and

reading, by the client device, the webpage data from the local storage medium and displaying the corresponding target webpage when the local storage medium stores the webpage data.
The method according to claim 1, wherein the storing of the webpage data in the local storage medium comprises storing a target identification associated with the target webpage as an identification of the target webpage in the local storage medium；

the second display request comprises the target identification of the target webpage； and

the determining of whether the local storage medium stores the webpage data comprises determining whether the received target identification matches with the stored target identification.
The method according to claim 1, wherein the receiving of the webpage data from the server further comprising:

displaying the target webpage according to the webpage data；

receiving a caching request for storing the webpage data； and

storing the webpage data in the local storage medium according to the caching request.
The method according to claim 1, wherein the receiving of the webpage data from the server further comprising:

displaying the target webpage according to the webpage data；

determining whether the target webpage meets a predetermined condition； and

storing the webpage data in the local storage medium automatically when the target webpage meets the predetermined condition.
The method according to claim 11, wherein the predetermined condition is at least one of

when the target webpage has been displayed by the client device for more than a predetermined number of times；

the target webpage has a credit value more than a predetermined credit； and

the target webpage is associated with a communication account of the user in a social communication platform corresponding to the client device.
The method according to anyone of claims 1, further comprising:

deleting, by the client device, the webpage data from the local storage medium when the webpage data has been stored in the local storage medium longer than a predetermined period of time.
The method according to claim 8, wherein the method is operated by the client device under a social communication platform；

the social communication platform comprises a user communication account of the user and a friend communication account of a friend of the user；

the user communication account is associated with the friend communication account through a friend list in the user communication account； and

the second display request is sent from the friend communication account through the social communication platform.
Anon-transitory processor-readable storage medium, comprising a set of instructions to display webpages under a social communication platform, wherein the set of instructions, when executed by a processor, directs the processor to perform functions of:

sending to a server a first display request for displaying a target webpage；

receiving webpage data of the target webpage from the server；

storing the webpage data in the storage medium；

when the processor receives a second display request for displaying the target webpage, determining whether the storage medium stores the webpage data； and

reading the webpage data from the storage medium and displaying the corresponding target webpage when the storage medium stores the webpage data.
The storage medium according to claim 15, wherein the receiving of the webpage data from the server further comprising:

displaying the target webpage according to the webpage data；

receiving a caching request for storing the webpage data； and

storing the webpage data in the storage medium according to the caching request.
The storage medium according to claim 15, wherein the receiving of the webpage data from the server further comprising:

displaying the target webpage according to the webpage data；

determining whether the target webpage meets a predetermined condition； and

storing the webpage data in the storage medium automatically when the target webpage meets the predetermined condition.
The storage medium according to claim 17, wherein the predetermined condition is at least one of

when the target webpage has been displayed by the processor for more than a predetermined number of times；

the target webpage has a credit value more than a predetermined credit； and

the target webpage is associated with a communication account of the user in a social communication platform corresponding to the client device.
The storage medium according to anyone of claims 15, further comprising:

deleting the webpage data from the storage medium when the webpage data has been stored in the storage medium longer than a predetermined period of time.
The storage medium according to claim 15, wherein the method is operated by the client device under a social communication platform；

the social communication platform comprises a user communication account of the user and a friend communication account of a friend of the user；

the user communication account is associated with the friend communication account through a friend list in the user communication account； and

the second display request is sent from the friend communication account through the social communication platform.