WO2015180601A1 - WebApp启动运行、生成镜像文件的方法和装置 - Google Patents
WebApp启动运行、生成镜像文件的方法和装置 Download PDFInfo
- Publication number
- WO2015180601A1 WO2015180601A1 PCT/CN2015/079689 CN2015079689W WO2015180601A1 WO 2015180601 A1 WO2015180601 A1 WO 2015180601A1 CN 2015079689 W CN2015079689 W CN 2015079689W WO 2015180601 A1 WO2015180601 A1 WO 2015180601A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- webapp
- image file
- local
- request information
- network
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Ceased
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
Definitions
- the present application relates to the field of communications technologies, and in particular, to a method and apparatus for starting a WebApp and generating an image file.
- Internet WebApp web application
- mobile terminals such as mobile phones
- Baidu and WeChat Internet WebApp access terminals on mobile terminals
- Users can directly open the WebApp on the application platform provided by the Internet WebApp access server (such as clicking the icon in Baidu's light application to launch the third-party WebApp, clicking the menu of the public account of WeChat to launch the public account WebApp, etc.), using the Internet service.
- the method for starting the WebApp is as follows: receiving the WebApp startup instruction, connecting with the WebApp service provider providing the WebApp service through the Internet, obtaining the WebApp page information corresponding to the WebApp from the WebApp service provider, and generating and displaying the WebApp page according to the WebApp page information. .
- the existing WebApp startup method relies entirely on the Internet. When the network is not connected (no network) or the network speed is slow (weak network), the WebApp cannot be started or started very slowly.
- the technical problem to be solved by the present application is to provide a method and device for starting and running a WebApp and generating an image file, and generating and displaying a WebApp page according to a local WebApp image file, so that the WebApp does not depend on the Internet when it starts running, and has no network or weak. In the case of the network, it is still possible to start and run the WebApp stably and quickly, and access the Internet service.
- the present application discloses a method for starting a WebApp, the method comprising:
- determining the current state of the Internet including:
- the method further includes:
- WebApp request information includes:
- WebApp network address or, WebApp network address and Post request parameters.
- acquiring a local WebApp image file corresponding to the WebApp request information including:
- the local WebApp image file includes a meta-meta image file and a cached cache image file.
- meta image file is used to store WebApp request information
- cache image file is used to store WebApp page information corresponding to the WebApp request information.
- the WebApp launching operation includes: accessing a WebApp network address, and opening a WebApp page that needs to be accessed in a networkless or weak network state.
- the WebApp request information also points to a corresponding WebApp service provider. After judging the current Internet status, it also includes:
- the WebApp service provider corresponding to the WebApp request information is connected through the Internet;
- the present application also discloses a method for generating an image file, the method comprising:
- the Web application service provider uses the virtual network computer client VNC Client to access the remote mobile device in the WebApp access server through the virtual network computer server VNC Server port provided by the WebApp access server in the WebApp access server.
- the VNC server on the terminal performs a WebApp startup operation in a network web running environment built in the remote mobile terminal;
- the remote mobile terminal When the remote mobile terminal performs the WebApp startup operation on the WebApp service provider, the submitted WebApp request information and the acquired WebApp page information corresponding to the WebApp request information are recorded in the local WebApp image file.
- the WebApp launching operation includes: accessing a WebApp network address, and opening a WebApp page that needs to be accessed in a networkless or weak network state.
- the method further includes:
- the WebApp access server pushes the local WebApp image file to a preset mobile terminal.
- the file name of the local WebApp image file is a data-digest algorithm md5 value calculated according to the WebApp request information.
- the local WebApp image file includes a meta-meta image file and a cached cache image file.
- the meta image file is used to store WebApp request information
- the cache The image file is used to store the WebApp page information corresponding to the WebApp request information.
- the present application also discloses an apparatus for starting a WebApp, the apparatus comprising:
- a receiving module configured to receive a webpage application WebApp startup instruction, where the WebApp startup instruction carries WebApp request information, and the WebApp request information points to a corresponding local WebApp image file;
- a judging module for judging a current Internet status
- An obtaining module configured to acquire a local WebApp image file corresponding to the WebApp request information when the judgment result of the determining module is that the Internet status is a networkless or weak network; wherein the local WebApp image file is configured by the WebApp
- the access server generates and pushes the local device according to the WebApp startup operation of the WebApp service provider;
- the first processing module is configured to generate and display a WebApp page according to the local WebApp image file.
- the determining module includes:
- Query unit for querying a local network
- the first determining unit is configured to determine that the current Internet status is no network if the query unit does not query the network.
- the determining module further includes:
- a determining unit configured to determine, if the query unit queries the network, whether the WebApp page information corresponding to the WebApp request information is returned within a preset time interval
- a second determining unit configured to determine that the current Internet status is a weak network if the determination result of the determining unit is not.
- WebApp request information includes:
- WebApp network address or, WebApp network address and Post request parameters.
- the obtaining module includes:
- a calculation unit configured to calculate an information-digest algorithm md5 value of the WebApp request information
- a searching unit configured to find a local WebApp image file corresponding to the md5 value of the file name Pieces.
- the local WebApp image file includes a meta-meta image file and a cached cache image file.
- meta image file is used to store WebApp request information
- cache image file is used to store WebApp page information corresponding to the WebApp request information.
- the WebApp launching operation includes: accessing a WebApp network address, and opening a WebApp page that needs to be accessed in a networkless or weak network state.
- the WebApp request information is further directed to the corresponding WebApp service provider, and the device further includes:
- connection module configured to: when the judgment result of the determining module is that the Internet status is a normal network, connect to the WebApp service providing end corresponding to the WebApp request information through the Internet;
- a second processing module configured to acquire WebApp page information corresponding to the WebApp request information from the WebApp service provider, generate and display a WebApp page according to the WebApp page information obtained from the WebApp service provider, and according to the The WebApp page information obtained by the WebApp service provider updates the local WebApp image file.
- the present application also discloses a system for generating an image file, where the system includes: a WebApp service provider and a WebApp access server;
- VApp Client is set in the WebApp service provider
- the WebApp access server includes: a WebApp access server and a remote mobile terminal; and the remote mobile terminal is provided with a VNC Server;
- the WebApp service provider is configured to access the VNC Server on the remote mobile terminal through the VNC Server provided by the WebApp access server, and perform the Web operating environment built in the remote mobile terminal. WebApp starts the running operation;
- the remote mobile terminal is configured to map a VNC Server port on the remote mobile terminal to the WebApp access server by using a port mapping method; and submit the WebApp service providing end to perform a WebApp startup operation WebApp request information, obtained WebApp page information corresponding to the WebApp request information is recorded in the local WebApp image In the file.
- the WebApp launching operation includes: accessing a WebApp network address, and opening a WebApp page that needs to be accessed in a networkless or weak network state.
- the WebApp access server is configured to push the local WebApp image file to a preset mobile terminal.
- the file name of the local WebApp image file is a data-digest algorithm md5 value calculated according to the WebApp request information.
- the local WebApp image file includes a meta-meta image file and a cached cache image file.
- meta image file is used to store WebApp request information
- cache image file is used to store WebApp page information corresponding to the WebApp request information.
- the local WebApp image file corresponding to the WebApp request information is obtained, and the WebApp page is generated and displayed according to the local WebApp image file, so that the WebApp does not depend on the Internet when running, and there is no network or weak.
- the network it is still possible to start and run the WebApp stably and quickly, and access the Internet service.
- the accuracy of the obtained local WebApp image file corresponding to the WebApp request information can be improved.
- the local WebApp image file is updated according to the WebApp page information obtained from the WebApp service provider to ensure the real-time performance of the local WebApp image file used in the next time when there is no network or weak network.
- FIG. 1 is a flowchart of a method for starting a first WebApp in the embodiment of the present application
- FIG. 2 is a flowchart of a method for starting a second WebApp in the embodiment of the present application
- FIG. 3 is a flowchart of a method for generating an image file according to an embodiment of the present application
- FIG. 4 is a flowchart of a method for starting a third WebApp startup operation according to an embodiment of the present application
- FIG. 5 is a flowchart of a fourth WebApp startup operation method according to an embodiment of the present application.
- FIG. 6 is a schematic structural diagram of an apparatus for starting a first WebApp in the embodiment of the present application.
- FIG. 7 is a schematic structural diagram of a device for starting a second WebApp in the embodiment of the present application.
- FIG. 8 is a schematic structural diagram of an apparatus for generating an image file according to an embodiment of the present application.
- a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
- processors CPUs
- input/output interfaces network interfaces
- memory volatile and non-volatile memory
- the memory may include non-persistent memory, random access memory (RAM), and/or non-volatile memory in a computer readable medium, such as read only memory (ROM) or flash memory.
- RAM random access memory
- ROM read only memory
- Memory is an example of a computer readable medium.
- Computer readable media includes both permanent and non-persistent, removable and non-removable media.
- Information storage can be implemented by any method or technology.
- the information can be computer readable instructions, data structures, modules of programs, or other data.
- Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read only memory. (ROM), electrically erasable programmable read only memory (EEPROM), flash memory or other memory technology, compact disk read only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, Magnetic tape cartridges, magnetic tape storage or other magnetic storage devices or any other non-transportable media can be used to store information that can be accessed by a computing device.
- computer readable media does not include non-transitory computer readable media, such as modulated data signals and carrier waves.
- a flowchart of a method for starting a WebApp startup operation includes:
- S101 Receive a WebApp startup instruction, where the WebApp startup instruction carries the WebApp request information, and the WebApp request information points to the corresponding local WebApp image file.
- various WebApps may be displayed in the form of icons and the like in the mobile terminal interface providing the WebApp.
- the WebApp may be directly clicked on the corresponding icon or the like.
- the WebApp request information includes:
- WebApp network address or, WebApp network address and Post request parameters.
- the WebApp startup command may be sent in the Get mode or the Post mode.
- the WebApp request information includes the WebApp network address when sent by the Get mode.
- the WebApp request information includes the WebApp network address and the Post request parameter.
- the local WebApp image file is generated and pushed to the local device by the WebApp access server according to the WebApp startup operation of the WebApp service provider.
- the file name of the local WebApp image file is the md (information-digest algorithm) 5 value calculated based on the WebApp request information.
- the information calculated by the WebApp request information - the digest algorithm md5 value is used as the file name of the local WebApp image file, which can ensure the uniqueness of the file name, avoid duplication of the file name, and improve the obtained local WebApp image file corresponding to the WebApp request information. The accuracy.
- the local WebApp image file includes a meta (primary) image file and a cache (cache) image file.
- the meta image file is used to store the WebApp request information
- the cache image file is used to store the WebApp page information corresponding to the WebApp request information.
- obtaining a local WebApp image file corresponding to the WebApp request information including:
- S104 Generate and display a WebApp page according to the local WebApp image file.
- the WebApp page is generated and displayed according to the WebApp page information corresponding to the WebApp request information stored in the cache image file.
- the WebApp page can be generated and displayed according to the local WebApp image file, so that the WebApp can also be used when there is no network or weak network.
- determining the current Internet status may include:
- S102a Query the local network, if no network is queried, execute S102b; otherwise, execute S102c.
- S102b Determine that the current Internet status is no network, and then execute S103.
- S102c Determine whether there is a WebApp page information return corresponding to the WebApp request information within a preset time interval. If not, execute S102d; otherwise, execute S102e.
- the preset time interval may be set according to actual application conditions, such as setting to 0.1 seconds, 1 second, and the like.
- S102d Determine that the current Internet status is a weak network, and then execute S103.
- S102e Determine that the current Internet status is a normal network, and connect to the WebApp service provider corresponding to the WebApp request information through the Internet.
- S102f Obtain WebApp page information corresponding to the WebApp request information from the WebApp service provider, generate and display the WebApp page according to the WebApp page information obtained from the WebApp service provider, and use the WebApp page information obtained from the WebApp service provider to the local WebApp.
- the image file is updated.
- the WebApp request information stored in the meta image file is requested in the web running environment, and the actual WebApp page is requested from the WebApp service provider.
- the above process is the automatic behavior of the background in the web running environment, and will not affect the positive of the upper layer WebApp. Always running.
- the local WebApp image file is updated according to the WebApp page information obtained from the WebApp service provider, including:
- the WebApp page information obtained from the WebApp service provider is different from the WebApp page information in the cache image file
- the WebApp page information in the local WebApp image file is replaced with the WebApp page information obtained from the WebApp service provider. Page information.
- the WebApp page information in the update is updated. Or, compare the WebApp page information obtained from the WebApp service provider with the WebApp page information in the cache image file in the local WebApp image file, and the WebApp page information obtained from the WebApp service provider, and the cache image file.
- the WebApp page information is different (that is, the current WebApp page information changes)
- the WebApp page information obtained from the WebApp service provider is replaced with the WebApp page information in the cache image file in the local WebApp image file to be updated.
- the information-digest algorithm md5 value calculated according to the WebApp request information can be found, and the local WebApp image file is found according to the md5 value.
- the method for starting the running of the WebApp in this embodiment when the Internet status is no network or weak network, acquiring a local WebApp image file corresponding to the WebApp request information, generating and displaying the WebApp page according to the local WebApp image file, so that the WebApp starts.
- the runtime no longer relies on the Internet.
- Information calculated from WebApp request information - summary The md5 value of the algorithm is used to find the local WebApp image file, which can improve the accuracy of the obtained local WebApp image file corresponding to the WebApp request information.
- the local WebApp image file is updated according to the WebApp page information obtained from the WebApp service provider to ensure the real-time performance of the local WebApp image file used in the next time when there is no network or weak network.
- the embodiment provides a method for generating an image file, including:
- the Web application service provider uses the virtual network computer client VNC Client (Virtual Network Computer Client) to access the virtual network computer server VNC Server provided by the WebApp access server in the server.
- the (virtual network computer server) port accesses the VNC Server on the remote mobile terminal in the WebApp access server, and performs the WebApp startup operation in the network web running environment built in the remote mobile terminal.
- the WebApp launch operation includes: accessing the WebApp network address, and opening a WebApp page that needs to be accessed in a networkless or weak network state.
- the method further comprises:
- the WebApp access server pushes the local WebApp image file to the preset mobile terminal.
- the preset mobile terminal is a mobile terminal using the WebApp of the embodiment.
- the file name of the local WebApp image file is the information-digest algorithm md5 value calculated according to the WebApp request information.
- the local WebApp image file includes a meta-meta image file and a cached cache image file.
- the meta image file is used to store the WebApp request information
- the cache image file is used to store the WebApp page information corresponding to the WebApp request information.
- the WebApp service provider only needs to be remotely
- the WebApp access server can automatically generate data mirror files from the network request, without the need to generate the WebApp service provider, which can save the time and cost of the WebApp service provider.
- the WebApp access server pushes the local WebApp image file to the preset mobile terminal.
- the Internet status of the preset mobile terminal is no network or weak network
- the local WebApp image file corresponding to the WebApp request information is obtained, according to the local WebApp.
- Mirror files generate and display WebApp pages, so that WebApp does not rely on the Internet when it starts running. In the absence of network or weak network, it can still start and run WebApp stably and quickly, and access Internet services.
- the information calculated by the WebApp request information - the digest algorithm md5 value is used as the file name of the local WebApp image file, which can ensure the uniqueness of the file name, avoid duplication of the file name, and improve the obtained local WebApp image file corresponding to the WebApp request information.
- the accuracy is used as the file name of the local WebApp image file, which can ensure the uniqueness of the file name, avoid duplication of the file name, and improve the obtained local WebApp image file corresponding to the WebApp request information. The accuracy.
- the embodiment provides a method for starting a WebApp, and the method includes:
- the WebApp service provider Before the WebApp service provider publishes the WebApp, it needs to publish the relevant information of the WebApp to the WebApp access server.
- the related information of the WebApp includes the WebApp name, the WebApp icon, the WebApp network address, and the WebApp image file.
- the method for generating an image file is as follows:
- the WebApp service provider utilizes the VNC Client to access the VNC Server port provided by the WebApp access server in the WebApp, accesses the VNC Server on the remote mobile terminal in the WebApp access server, and the Web Web built in the remote mobile terminal. Start the WebApp startup operation in the running environment.
- the remote mobile terminal performs the WebApp startup operation on the WebApp service provider
- the submitted WebApp request information and the acquired WebApp page information corresponding to the WebApp request information are recorded in the local WebApp image file.
- the WebApp access server pushes the local WebApp image file to the preset mobile terminal.
- the WebApp service provider only needs to access the remote mobile terminal on the browser, access the upcoming WebApp through the WebApp network address on the remote mobile terminal, and browse the WebApp page that needs to be made into an image file, and then automatically record the website.
- Required WebApp Mirror Like a file.
- the file name of the local WebApp image file is the information-digest algorithm md5 value calculated according to the WebApp request information.
- the local WebApp image file includes a meta-meta image file and a cached cache image file.
- the WebApp request information is http://lifecard.aliapp.com/lifecard/src/tpl/serviceaddpage.tpl
- the obtained meta image file and cache image file are as follows: 1.
- the meta image file is: 0bfe8652d4843033d657801cbb90dc7c.meta, meta
- the contents of the image file are:
- the cache image file is: 0bfe8652d4843033d657801cbb90dc7c.cache, the contents of the cache image file are:
- S302 The WebApp access server pushes the WebApp to the mobile terminal.
- the WebApp access server When there is a new WebApp access, the WebApp access server will send a new WebApp notification to the mobile terminal through the Push channel between it and the mobile terminal, when the mobile terminal is in a network environment (such as a wifi environment, or a 3G wireless network).
- a network environment such as a wifi environment, or a 3G wireless network.
- the WebApp and WebApp image files published by the WebApp access server are downloaded to the mobile terminal. After that, the user can access the newly released WebApp in the application platform of the WebApp access server of the mobile terminal.
- S303 The mobile terminal implements the WebApp service through the local image file when there is no network or a weak network.
- the local image is accessed when the current Internet status is no network or weak network by the method of FIG. 2 .
- the specific process of accessing the local image is as described in steps S103 and S104.
- Calculate the information of the WebApp request information - the digest algorithm md5 value, and the md5 value can be used to find the meta image file and the cache image file generated in step S301.
- the contents of the cache image file are the result of the return to the upper layer network call.
- the development of the upper-level WebApp can be made without Need to care about the network situation, still use the standard HTML network protocol to make network resource calls, through the automatic detection and matching of the Web running environment, to achieve the purpose of successfully loading network resources under no network or weak network, thus achieving the effect of offline access. .
- S304 The mobile terminal implements the WebApp service through the WebApp service provider during the normal network.
- the mobile terminal connects to the WebApp service provider through the Internet.
- the WebApp request information recorded in the meta image file is requested in the web running environment, and the current WebApp page information is requested from the WebApp service provider. It is the automatic behavior of the background in the web runtime environment, and will not affect the normal operation of the upper layer WebApp.
- S305 The mobile terminal updates the local image file.
- step S304 the mobile terminal obtains the corresponding cache image file according to the md5 value, and obtains the cache image file according to the WebApp page information obtained from the WebApp service provider, after obtaining the WebApp page information from the WebApp service provider.
- the mobile terminal obtains the corresponding cache image file according to the md5 value, and obtains the cache image file according to the WebApp page information obtained from the WebApp service provider, after obtaining the WebApp page information from the WebApp service provider.
- the specific update method refer to the description of step S102f, and details are not described herein again.
- FIG. 6 it is a device for starting a WebApp operation according to an embodiment of the present application, and the device includes:
- the receiving module 401 is configured to receive a webpage application WebApp startup instruction, where the WebApp startup instruction carries the WebApp request information, and the WebApp request information points to the corresponding local WebApp image file;
- the determining module 402 is configured to determine a current Internet status
- the obtaining module 403 is configured to obtain a local WebApp image file corresponding to the WebApp request information when the judgment result of the determining module 402 is that the Internet status is no network or weak network; wherein the local WebApp image file is accessed by the WebApp according to the WebApp.
- the WebApp startup operation of the service provider is generated and pushed to the local;
- the first processing module 404 is configured to generate and display a WebApp page according to the local WebApp image file.
- the determining module 402 includes:
- Query unit for querying a local network
- the first determining unit is configured to determine that the current Internet status is no network if the query unit does not query the network.
- the determining module 402 further includes:
- a determining unit configured to determine, if the query unit queries the network, whether the WebApp page information corresponding to the WebApp request information is returned within a preset time interval
- the second determining unit is configured to determine that the current Internet state is a weak network if the determination result of the determining unit is not.
- WebApp request information includes:
- WebApp network address or, WebApp network address and Post request parameters.
- the obtaining module 403 includes:
- a calculation unit configured to calculate information of the WebApp request information-summary algorithm md5 value
- a search unit for finding a local WebApp image file whose file name corresponds to the md5 value is a search unit for finding a local WebApp image file whose file name corresponds to the md5 value.
- the local WebApp image file includes a meta-meta image file and a cached cache image file.
- meta image file is used to store the WebApp request information
- cache image file is used to store the WebApp page information corresponding to the WebApp request information.
- the WebApp launch operation includes: accessing the WebApp network address, and opening a WebApp page that needs to be accessed in a networkless or weak network state.
- the WebApp request information also points to the corresponding WebApp service provider, and the device further includes:
- the connection module 405 is configured to, when the judgment result of the determination module 402 is that the Internet status is a normal network, connect to the WebApp service provider corresponding to the WebApp request information through the Internet;
- the second processing module 406 is configured to obtain WebApp page information corresponding to the WebApp request information from the WebApp service provider, generate and display the WebApp page according to the WebApp page information obtained from the WebApp service provider, and obtain the WebApp page according to the obtained from the WebApp service provider.
- the WebApp page information updates the local WebApp image file.
- the device that is started and run by the WebApp in this embodiment acquires a local WebApp image file corresponding to the WebApp request information when the Internet status is no network or weak network, and generates and displays the WebApp page according to the local WebApp image file, so that the WebApp starts.
- the runtime no longer relies on the Internet.
- the WebApp request information the md5 value of the digest algorithm, and searching for the local WebApp image file
- the local WebApp image file is updated according to the WebApp page information obtained from the WebApp service provider to ensure the real-time performance of the local WebApp image file used in the next time when there is no network or weak network.
- the application also discloses a system for generating an image file, the system comprising: a WebApp service provider 50 and a WebApp access server 60;
- the VApp Client is set in the WebApp service provider 50;
- the WebApp access server 60 includes: a WebApp access server 601 and a remote mobile terminal 602; the remote mobile terminal 602 is provided with a VNC Server;
- the WebApp service providing terminal 50 is configured to access the VNC Server on the remote mobile terminal 602 through the VNC Server port provided by the WebApp access server, and perform the WebApp startup operation in the Web running environment built in the remote mobile terminal 602.
- the remote mobile terminal 602 is configured to map the VNC server port on the remote mobile terminal 602 to the WebApp access server by using the method of port mapping, and submit the WebApp request information when the WebApp service providing terminal 50 performs the WebApp startup operation.
- the obtained WebApp page information corresponding to the WebApp request information is recorded in the local WebApp image file.
- the WebApp launch operation includes: accessing the WebApp network address, and opening a WebApp page that needs to be accessed in a networkless or weak network state.
- the WebApp access server 601 is configured to push the local WebApp image file to the preset mobile terminal.
- the file name of the local WebApp image file is the information-digest algorithm md5 value calculated according to the WebApp request information.
- the local WebApp image file includes a meta-meta image file and a cached cache image file.
- meta image file is used to store the WebApp request information
- cache image file is used to store the WebApp page information corresponding to the WebApp request information.
- the WebApp service provider only needs to remotely perform the WebApp startup operation, and the WebApp access server can automatically generate the data request image file by the network request, without the WebApp service provider generating, Save time and cost of the WebApp service provider.
- the WebApp access server pushes the local WebApp image file to the preset mobile terminal.
- the Internet status of the preset mobile terminal is no network or weak network
- the local WebApp image file corresponding to the WebApp request information is obtained, according to the local WebApp.
- Mirror files generate and display WebApp pages, so that WebApp does not rely on the Internet when it starts running. In the absence of network or weak network, it can still start and run WebApp stably and quickly, and access Internet services.
- the information calculated by the WebApp request information - the digest algorithm md5 value is used as the file name of the local WebApp image file, which can ensure the uniqueness of the file name, avoid duplication of the file name, and improve the obtained local WebApp image file corresponding to the WebApp request information.
- the accuracy is used as the file name of the local WebApp image file, which can ensure the uniqueness of the file name, avoid duplication of the file name, and improve the obtained local WebApp image file corresponding to the WebApp request information. The accuracy.
- the device and system correspond to the foregoing method flow description, and the deficiencies refer to the description of the above method flow, and will not be further described.
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Transfer Between Computers (AREA)
Abstract
本申请公开了一种WebApp启动运行、生成镜像文件的方法和装置,属于通信技术领域。所述方法包括:接收网页应用WebApp启动指令;其中,所述WebApp启动指令中携带WebApp请求信息;判断当前的互联网状态;当所述互联网状态为无网络或弱网络时,获取与所述WebApp请求信息对应的本地WebApp镜像文件;根据所述本地WebApp镜像文件,生成并展示WebApp页面。所述装置包括:接收模块、判断模块、获取模块和第一处理模块。本发明WebApp启动运行时不再依赖互联网,在无网络或弱网络的情况下,依然可以稳定、快速地启动运行WebApp,访问互联网服务。
Description
本申请涉及通信技术领域,具体涉及一种WebApp启动运行、生成镜像文件的方法和装置。
随着通信技术的发展,手机等移动终端上的互联网WebApp(网页应用)接入服务端也越来越多,比如百度、微信等。用户可以直接打开互联网WebApp接入服务端提供的应用平台上的WebApp(比如点击百度的轻应用中的图标启动第三方WebApp、点击微信的公众帐号的菜单启动公众帐号的WebApp等),使用互联网服务,无需安装相关的应用程序。
目前,WebApp启动运行的方法如下:接收WebApp启动指令,通过互联网与提供WebApp服务的WebApp服务提供端进行连接,从WebApp服务提供端获取WebApp对应的WebApp页面信息,根据WebApp页面信息生成并展示WebApp页面。
然而,现有WebApp启动运行的方法完全依赖于互联网,当网络未连接(无网络)或网速很慢(弱网络)的情况下,WebApp无法启动运行或启动运行非常慢。
发明内容
本申请所要解决的技术问题在于提供一种WebApp启动运行、生成镜像文件的方法和装置,根据本地WebApp镜像文件,生成并展示WebApp页面,使得WebApp启动运行时不再依赖互联网,在无网络或弱网络的情况下,依然可以稳定、快速地启动运行WebApp,访问互联网服务。
为了解决上述问题,本申请公开了一种WebApp启动运行的方法,所述方法包括:
接收网页应用WebApp启动指令;其中,所述WebApp启动指令中携带WebApp请求信息,所述WebApp请求信息指向对应的本地WebApp镜像文
件;
判断当前的互联网状态;
当所述互联网状态为无网络或弱网络时,获取与所述WebApp请求信息对应的本地WebApp镜像文件;其中,所述本地WebApp镜像文件由WebApp接入服务端根据WebApp服务提供端的WebApp启动运行操作生成并推送到本地;
根据所述本地WebApp镜像文件,生成并展示WebApp页面。
进一步地,判断当前的互联网状态,包括:
查询本地的网络;
如果没有查询到网络,则确定当前的互联网状态为无网络。
进一步地,查询本地的网络之后,还包括:
如果查询到网络,则判断在预设的时间间隔内是否有与所述WebApp请求信息对应的WebApp页面信息返回;
如果没有,则确定当前的互联网状态为弱网络。
进一步地,所述WebApp请求信息包括:
WebApp网络地址,或,WebApp网络地址和Post请求参数。
进一步地,获取与所述WebApp请求信息对应的本地WebApp镜像文件,包括:
计算所述WebApp请求信息的信息-摘要算法md5值;
查找文件名称与所述md5值对应的本地WebApp镜像文件。
进一步地,所述本地WebApp镜像文件包括元meta镜像文件和缓存cache镜像文件。
进一步地,所述meta镜像文件用于存放WebApp请求信息,所述cache镜像文件用于存放与所述WebApp请求信息对应的WebApp页面信息。
进一步地,所述WebApp启动运行操作包括:访问WebApp网络地址,打开需要在无网络或弱网络状态下访问的WebApp页面。
进一步地,所述WebApp请求信息还指向对应的WebApp服务提供端,
判断当前的互联网状态之后,还包括:
当所述互联网状态为正常网络时,通过互联网与所述WebApp请求信息对应的WebApp服务提供端进行连接;
从所述WebApp服务提供端获取与所述WebApp请求信息对应的WebApp页面信息;
根据从所述WebApp服务提供端获取的WebApp页面信息生成并展示WebApp页面,并根据从所述WebApp服务提供端获取的WebApp页面信息对所述本地WebApp镜像文件进行更新。
为了解决上述问题,本申请还公开了一种生成镜像文件的方法,所述方法包括:
网页应用WebApp服务提供端利用虚拟网络计算机客户端VNC Client,通过WebApp接入服务端中的WebApp接入服务器提供的虚拟网络计算机服务端VNC Server端口,访问所述WebApp接入服务端中的远程移动终端上的VNC Server,在所述远程移动终端内置的网络Web运行环境中进行WebApp启动运行操作;
所述远程移动终端将所述WebApp服务提供端进行WebApp启动运行操作时,提交的WebApp请求信息、获取的与WebApp请求信息对应的WebApp页面信息记录在本地WebApp镜像文件中。
进一步地,所述WebApp启动运行操作包括:访问WebApp网络地址,打开需要在无网络或弱网络状态下访问的WebApp页面。
进一步地,所述方法还包括:
所述WebApp接入服务器将所述本地WebApp镜像文件推送到预设的移动终端中。
进一步地,所述本地WebApp镜像文件的文件名称为根据所述WebApp请求信息计算得到的信息-摘要算法md5值。
进一步地,所述本地WebApp镜像文件包括元meta镜像文件和缓存cache镜像文件。
进一步地,所述meta镜像文件用于存放WebApp请求信息,所述cache
镜像文件用于存放与WebApp请求信息对应的WebApp页面信息。
为了解决上述问题,本申请还公开了一种WebApp启动运行的装置,所述装置包括:
接收模块,用于接收网页应用WebApp启动指令;其中,所述WebApp启动指令中携带WebApp请求信息,所述WebApp请求信息指向对应的本地WebApp镜像文件;
判断模块,用于判断当前的互联网状态;
获取模块,用于当所述判断模块的判断结果是所述互联网状态为无网络或弱网络时,获取与所述WebApp请求信息对应的本地WebApp镜像文件;其中,所述本地WebApp镜像文件由WebApp接入服务端根据WebApp服务提供端的WebApp启动运行操作生成并推送到本地;
第一处理模块,用于根据所述本地WebApp镜像文件,生成并展示WebApp页面。
进一步地,所述判断模块包括:
查询单元,用于查询本地的网络;
第一确定单元,用于如果所述查询单元没有查询到网络,则确定当前的互联网状态为无网络。
进一步地,所述判断模块还包括:
判断单元,用于如果所述查询单元查询到网络,则判断在预设的时间间隔内是否有与所述WebApp请求信息对应的WebApp页面信息返回;
第二确定单元,用于如果所述判断单元的判断结果是没有,则确定当前的互联网状态为弱网络。
进一步地,所述WebApp请求信息包括:
WebApp网络地址,或,WebApp网络地址和Post请求参数。
进一步地,所述获取模块包括:
计算单元,用于计算所述WebApp请求信息的信息-摘要算法md5值;
查找单元,用于查找文件名称与所述md5值对应的本地WebApp镜像文
件。
进一步地,所述本地WebApp镜像文件包括元meta镜像文件和缓存cache镜像文件。
进一步地,所述meta镜像文件用于存放WebApp请求信息,所述cache镜像文件用于存放与所述WebApp请求信息对应的WebApp页面信息。
进一步地,所述WebApp启动运行操作包括:访问WebApp网络地址,打开需要在无网络或弱网络状态下访问的WebApp页面。
进一步地,所述WebApp请求信息还指向对应的WebApp服务提供端,所述装置还包括:
连接模块,用于当所述判断模块的判断结果是所述互联网状态为正常网络时,通过互联网与所述WebApp请求信息对应的WebApp服务提供端进行连接;
第二处理模块,用于从所述WebApp服务提供端获取与所述WebApp请求信息对应的WebApp页面信息,根据从所述WebApp服务提供端获取的WebApp页面信息生成并展示WebApp页面,并根据从所述WebApp服务提供端获取的WebApp页面信息对所述本地WebApp镜像文件进行更新。
为了解决上述问题,本申请还公开了一种生成镜像文件的系统,所述系统包括:WebApp服务提供端和WebApp接入服务端;
其中,所述WebApp服务提供端中设置有VNC Client;
其中,所述WebApp接入服务端包括:WebApp接入服务器和远程移动终端;所述远程移动终端中设置有VNC Server;
所述WebApp服务提供端,用于利用所述VNC Client,通过WebApp接入服务器提供的VNC Server端口,访问所述远程移动终端上的VNC Server,在所述远程移动终端内置的Web运行环境中进行WebApp启动运行操作;
所述远程移动终端,用于通过端口映射的方法,将所述远程移动终端上的VNC Server端口映射到所述WebApp接入服务器上;将所述WebApp服务提供端进行WebApp启动运行操作时,提交的WebApp请求信息、获取的与所述WebApp请求信息对应的WebApp页面信息记录在本地WebApp镜像
文件中。
进一步地,所述WebApp启动运行操作包括:访问WebApp网络地址,打开需要在无网络或弱网络状态下访问的WebApp页面。
进一步地,所述WebApp接入服务器,用于将所述本地WebApp镜像文件推送到预设的移动终端中。
进一步地,所述本地WebApp镜像文件的文件名称为根据WebApp请求信息计算得到的信息-摘要算法md5值。
进一步地,所述本地WebApp镜像文件包括元meta镜像文件和缓存cache镜像文件。
进一步地,所述meta镜像文件用于存放WebApp请求信息,所述cache镜像文件用于存放与WebApp请求信息对应的WebApp页面信息。
与现有技术相比,本申请可以获得包括以下技术效果:
当互联网状态为无网络或弱网络时,获取与WebApp请求信息对应的本地WebApp镜像文件,根据本地WebApp镜像文件,生成并展示WebApp页面,使得WebApp启动运行时不再依赖互联网,在无网络或弱网络的情况下,依然可以稳定、快速地启动运行WebApp,访问互联网服务。根据WebApp请求信息计算得到的信息-摘要算法md5值,查找本地WebApp镜像文件,可以提高获取到的与WebApp请求信息对应的本地WebApp镜像文件的准确性。根据从WebApp服务提供端获取的WebApp页面信息对本地WebApp镜像文件进行更新,保证下次在无网络或弱网络时,使用的本地WebApp镜像文件的实时性。
当然,实施本申请的任一产品必不一定需要同时达到以上所述的所有技术效果。
此处所说明的附图用来提供对本申请的进一步理解,构成本申请的一部分,本申请的示意性实施例及其说明用于解释本申请,并不构成对本申请的不当限定。在附图中:
图1是本申请实施例的第一种WebApp启动运行的方法流程图;
图2是本申请实施例的第二种WebApp启动运行的方法流程图;
图3是本申请实施例的一种生成镜像文件的方法流程图;
图4是本申请实施例的第三种WebApp启动运行的方法流程图;
图5是本申请实施例的第四种WebApp启动运行的方法流程图;
图6是本申请实施例的第一种WebApp启动运行的装置结构示意图;
图7是本申请实施例的第二种WebApp启动运行的装置结构示意图;
图8是本申请实施例的一种生成镜像文件的装置结构示意图。
以下将配合附图及实施例来详细说明本申请的实施方式,藉此对本申请如何应用技术手段来解决技术问题并达成技术功效的实现过程能充分理解并据以实施。
在一个典型的配置中,计算设备包括一个或多个处理器(CPU)、输入/输出接口、网络接口和内存。
内存可能包括计算机可读介质中的非永久性存储器,随机存取存储器(RAM)和/或非易失性内存等形式,如只读存储器(ROM)或闪存(flash RAM)。内存是计算机可读介质的示例。
计算机可读介质包括永久性和非永久性、可移动和非可移动媒体可以由任何方法或技术来实现信息存储。信息可以是计算机可读指令、数据结构、程序的模块或其他数据。计算机的存储介质的例子包括,但不限于相变内存(PRAM)、静态随机存取存储器(SRAM)、动态随机存取存储器(DRAM)、其他类型的随机存取存储器(RAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、快闪记忆体或其他内存技术、只读光盘只读存储器(CD-ROM)、数字多功能光盘(DVD)或其他光学存储、磁盒式磁带,磁带磁磁盘存储或其他磁性存储设备或任何其他非传输介质,可用于存储可以被计算设备访问的信息。按照本文中的界定,计算机可读介质不包括非暂存电脑可读媒体(transitory media),如调制的数据信号和载波。
实施例描述
下面以一实施例对本申请方法的实现作进一步说明。如图1所示,为本申请实施例的一种WebApp启动运行的方法流程图,该方法包括:
S101:接收WebApp启动指令;其中,WebApp启动指令中携带WebApp请求信息,WebApp请求信息指向对应的本地WebApp镜像文件。
具体地,可以将各种WebApp以图标等形式展示在提供WebApp的移动终端界面中,当用户需要使用时,可以直接点击相应的图标等,使用WebApp。
其中,WebApp请求信息包括:
WebApp网络地址,或,WebApp网络地址和Post请求参数。
具体地,WebApp启动指令可以通过Get方式或Post方式发送,当通过Get方式发送时WebApp请求信息中包括WebApp网络地址,当通过Post方式发送时WebApp请求信息中包括WebApp网络地址和Post请求参数。
S102:判断当前的互联网状态。
S103:当互联网状态为无网络或弱网络时,获取与WebApp请求信息对应的本地WebApp镜像文件。
其中,本地WebApp镜像文件由WebApp接入服务端根据WebApp服务提供端的WebApp启动运行操作生成并推送到本地。本地WebApp镜像文件的文件名称为根据WebApp请求信息计算得到的md(信息-摘要算法)5值。将根据WebApp请求信息计算得到的信息-摘要算法md5值作为本地WebApp镜像文件的文件名称,可以保证文件名称的唯一性,避免文件名称重复,提高获取到的与WebApp请求信息对应的本地WebApp镜像文件的准确性。
其中,本地WebApp镜像文件包括meta(元)镜像文件和cache(缓存)镜像文件。
其中,meta镜像文件用于存放WebApp请求信息,cache镜像文件用于存放与WebApp请求信息对应的WebApp页面信息。
具体地,获取与WebApp请求信息对应的本地WebApp镜像文件,包括:
计算WebApp请求信息的信息-摘要算法md5值;
查找文件名称与md5值对应的本地WebApp镜像文件。
S104:根据本地WebApp镜像文件,生成并展示WebApp页面。
具体地,根据cache镜像文件中存放的与WebApp请求信息对应的WebApp页面信息,生成并展示WebApp页面。
当互联网状态为无网络或弱网络时,可以根据本地WebApp镜像文件,生成并展示WebApp页面,使得在无网络或弱网络时还可以使用WebApp。
其中,参见图2,判断当前的互联网状态,可以包括:
S102a:查询本地的网络,如果没有查询到网络,则执行S102b;否则,执行S102c。
S102b:确定当前的互联网状态为无网络,然后执行S103。
S102c:判断在预设的时间间隔内是否有与WebApp请求信息对应的WebApp页面信息返回,如果没有,则执行S102d;否则,执行S102e。
其中,预设的时间间隔内可以根据实际应用状况进行设置,如设置为0.1秒、1秒等。
S102d:确定当前的互联网状态为弱网络,然后执行S103。
S102e:确定当前的互联网状态为正常网络,通过互联网与WebApp请求信息对应的WebApp服务提供端进行连接。
S102f:从WebApp服务提供端获取与WebApp请求信息对应的WebApp页面信息,根据从WebApp服务提供端获取的WebApp页面信息生成并展示WebApp页面,并根据从WebApp服务提供端获取的WebApp页面信息对本地WebApp镜像文件进行更新。
具体地,当通过互联网与WebApp请求信息对应的WebApp服务提供端进行连接,网络连通时,会在Web运行环境中通过meta镜像文件里存放的WebApp请求信息,向WebApp服务提供端请求实际的WebApp页面信息,上述过程是Web运行环境中后台的自动行为,不会影响上层WebApp的正
常运行。
具体地,根据从WebApp服务提供端获取的WebApp页面信息对本地WebApp镜像文件进行更新,包括:
用从WebApp服务提供端获取的WebApp页面信息,替换本地WebApp镜像文件中的cache镜像文件中的WebApp页面信息。
或,将从WebApp服务提供端获取的WebApp页面信息,与本地WebApp镜像文件中的cache镜像文件中的WebApp页面信息进行比较;
当从WebApp服务提供端获取的WebApp页面信息,与cache镜像文件中的WebApp页面信息存在不同,则用从WebApp服务提供端获取的WebApp页面信息,替换本地WebApp镜像文件中的cache镜像文件中的WebApp页面信息。
无论当前的WebApp页面信息是否发生改变,可以直接用从WebApp服务提供端获取的WebApp页面信息,替换本地WebApp镜像文件中的cache镜像文件中的WebApp页面信息,对本地WebApp镜像文件中的cache镜像文件中的WebApp页面信息进行更新。或,将从WebApp服务提供端获取的WebApp页面信息,与本地WebApp镜像文件中的cache镜像文件中的WebApp页面信息进行比较,当从WebApp服务提供端获取的WebApp页面信息,与cache镜像文件中的WebApp页面信息存在不同(即当前的WebApp页面信息发生改变)时,才用从WebApp服务提供端获取的WebApp页面信息,替换本地WebApp镜像文件中的cache镜像文件中的WebApp页面信息,进行更新。
并且,在对本地WebApp镜像文件进行更新时,可以根据WebApp请求信息计算得到的信息-摘要算法md5值,根据md5值查找到本地WebApp镜像文件。
本实施例所述的WebApp启动运行的方法,当互联网状态为无网络或弱网络时,获取与WebApp请求信息对应的本地WebApp镜像文件,根据本地WebApp镜像文件,生成并展示WebApp页面,使得WebApp启动运行时不再依赖互联网,在无网络或弱网络的情况下,依然可以稳定、快速地启动运行WebApp,访问互联网服务。根据WebApp请求信息计算得到的信息-摘要
算法md5值,查找本地WebApp镜像文件,可以提高获取到的与WebApp请求信息对应的本地WebApp镜像文件的准确性。根据从WebApp服务提供端获取的WebApp页面信息对本地WebApp镜像文件进行更新,保证下次在无网络或弱网络时,使用的本地WebApp镜像文件的实时性。
参见图3,本实施例提供了一种生成镜像文件的方法,包括:
S201:网页应用WebApp服务提供端利用虚拟网络计算机客户端VNC Client(Virtual Network Computer Client,虚拟网络计算机客户端),通过WebApp接入服务端中的WebApp接入服务器提供的虚拟网络计算机服务端VNC Server(虚拟网络计算机服务端)端口,访问WebApp接入服务端中的远程移动终端上的VNC Server,在远程移动终端内置的网络Web运行环境中进行WebApp启动运行操作。
S202:远程移动终端将WebApp服务提供端进行WebApp启动运行操作时,提交的WebApp请求信息、获取的与WebApp请求信息对应的WebApp页面信息记录在本地WebApp镜像文件中。
其中,WebApp启动运行操作包括:访问WebApp网络地址,打开需要在无网络或弱网络状态下访问的WebApp页面。
其中,该方法还包括:
WebApp接入服务器将本地WebApp镜像文件推送到预设的移动终端中。
其中,预设的移动终端是使用本实施例的WebApp的移动终端。
其中,本地WebApp镜像文件的文件名称为根据WebApp请求信息计算得到的信息-摘要算法md5值。
其中,本地WebApp镜像文件包括元meta镜像文件和缓存cache镜像文件。
其中,meta镜像文件用于存放WebApp请求信息,cache镜像文件用于存放与WebApp请求信息对应的WebApp页面信息。
本实施例所述的生成镜像文件的方法,WebApp服务提供端只需要远程
进行WebApp启动运行操作,WebApp接入服务端即可自动将网络请求得到数据生成镜像文件,无需WebApp服务提供端生成,可以节约WebApp服务提供端的时间和成本。WebApp接入服务器将本地WebApp镜像文件推送到预设的移动终端中,当预设的移动终端的互联网状态为无网络或弱网络时,获取与WebApp请求信息对应的本地WebApp镜像文件,根据本地WebApp镜像文件,生成并展示WebApp页面,使得WebApp启动运行时不再依赖互联网,在无网络或弱网络的情况下,依然可以稳定、快速地启动运行WebApp,访问互联网服务。将根据WebApp请求信息计算得到的信息-摘要算法md5值作为本地WebApp镜像文件的文件名称,可以保证文件名称的唯一性,避免文件名称重复,提高获取到的与WebApp请求信息对应的本地WebApp镜像文件的准确性。
为了便于理解,下面以具体应用为例进行进一步说明,参见图4和图5,本实施例提供了一种WebApp启动运行的方法,该方法包括:
S301:WebApp服务提供端发布WebApp。
WebApp服务提供端发布WebApp之前,需要把WebApp的相关信息发布至WebApp接入服务端,WebApp的相关信息包括WebApp名称、WebApp图标和WebApp网络地址、WebApp镜像文件等。
本实施例中,生成镜像文件的方法如下:
WebApp服务提供端利用VNC Client,通过WebApp接入服务端中的WebApp接入服务器提供的VNC Server端口,访问WebApp接入服务端中的远程移动终端上的VNC Server,在远程移动终端内置的网络Web运行环境中进行WebApp启动运行操作。远程移动终端将WebApp服务提供端进行WebApp启动运行操作时,提交的WebApp请求信息、获取的与WebApp请求信息对应的WebApp页面信息记录在本地WebApp镜像文件中。WebApp接入服务器将本地WebApp镜像文件推送到预设的移动终端中。
本实施例WebApp服务提供端只需要在浏览器上访问远程移动终端,在远程移动终端上通过WebApp网络地址访问即将发布的WebApp,把需要做成镜像文件的WebApp页面浏览一遍,即可自动录制出所需要的WebApp镜
像文件。
其中,本地WebApp镜像文件的文件名称为根据WebApp请求信息计算得到的信息-摘要算法md5值。本地WebApp镜像文件包括元meta镜像文件和缓存cache镜像文件。例如:当WebApp请求信息为http://lifecard.aliapp.com/lifecard/src/tpl/serviceaddpage.tpl,得到的meta镜像文件和cache镜像文件如下:1、meta镜像文件为:0bfe8652d4843033d657801cbb90dc7c.meta,meta镜像文件的内容为:
2、cache镜像文件为:0bfe8652d4843033d657801cbb90dc7c.cache,cache镜像文件的内容为:
通过以上生成镜像文件的方法,在Web运行环境中将浏览的所有WebApp页面都生成为以上描述的镜像文件。
S302:WebApp接入服务端推送WebApp至移动终端。
当有新的WebApp接入时,WebApp接入服务端会通过其与移动终端之间的Push通道将新WebApp通知发送到移动终端,当移动终端处于有网络环境(如wifi环境,或3G无线网络环境等)下时,会将WebApp接入服务端发布的WebApp和WebApp镜像文件下载到移动终端中。之后,用户在移动终端的WebApp接入服务端的应用平台中就能访问到新发布的WebApp。
S303:无网络或弱网络时移动终端通过本地镜像文件实现WebApp服务。
当用户在移动终端的WebApp接入服务端的应用平台中启动WebApp时,通过图2的方法,确定当前的互联网状态为无网络或弱网络时,访问本地镜像。其中,访问本地镜像的具体过程如步骤S103、S104所述。计算WebApp请求信息的信息-摘要算法md5值,通过md5值就能查找到步骤S301中生成的meta镜像文件和cache镜像文件。cache镜像文件的内容就是返回给上层网络调用的结果。通过这样的策略,可以使得上层WebApp的开发无
需关心网络情况,仍然通过标准的HTML网络协议进行网络资源调用,通过Web运行环境的自动检测和匹配,达到无网络或弱网络下仍然可以成功载入网络资源的目的,从而实现离线访问的效果。
S304:正常网络时移动终端通过WebApp服务提供端实现WebApp服务。
正常网络时,移动终端通过互联网与WebApp服务提供端进行连接,当连通后,在Web运行环境中通过meta镜像文件里记录的WebApp请求信息,从WebApp服务提供端请求当前的WebApp页面信息,这个过程是Web运行环境时后台的自动行为,不会影响上层WebApp的正常运行。
S305:移动终端更新本地镜像文件。
在步骤S304中移动终端在Web运行环境中,从WebApp服务提供端获取到WebApp页面信息后,根据md5值查找到对应的cache镜像文件,并根据从WebApp服务提供端获取的WebApp页面信息更新cache镜像文件,以备下次无网络或弱网络时使用。具体更新方法参见步骤S102f的说明,此处不再赘述。
如图6所示,是本申请实施例的一种WebApp启动运行的装置,该装置包括:
接收模块401,用于接收网页应用WebApp启动指令;其中,WebApp启动指令中携带WebApp请求信息,WebApp请求信息指向对应的本地WebApp镜像文件;
判断模块402,用于判断当前的互联网状态;
获取模块403,用于当判断模块402的判断结果是互联网状态为无网络或弱网络时,获取与WebApp请求信息对应的本地WebApp镜像文件;其中,本地WebApp镜像文件由WebApp接入服务端根据WebApp服务提供端的WebApp启动运行操作生成并推送到本地;
第一处理模块404,用于根据本地WebApp镜像文件,生成并展示WebApp页面。
进一步地,判断模块402包括:
查询单元,用于查询本地的网络;
第一确定单元,用于如果查询单元没有查询到网络,则确定当前的互联网状态为无网络。
进一步地,判断模块402还包括:
判断单元,用于如果查询单元查询到网络,则判断在预设的时间间隔内是否有与WebApp请求信息对应的WebApp页面信息返回;
第二确定单元,用于如果判断单元的判断结果是没有,则确定当前的互联网状态为弱网络。
进一步地,WebApp请求信息包括:
WebApp网络地址,或,WebApp网络地址和Post请求参数。
进一步地,获取模块403包括:
计算单元,用于计算WebApp请求信息的信息-摘要算法md5值;
查找单元,用于查找文件名称与md5值对应的本地WebApp镜像文件。
进一步地,本地WebApp镜像文件包括元meta镜像文件和缓存cache镜像文件。
进一步地,meta镜像文件用于存放WebApp请求信息,cache镜像文件用于存放与WebApp请求信息对应的WebApp页面信息。
进一步地,WebApp启动运行操作包括:访问WebApp网络地址,打开需要在无网络或弱网络状态下访问的WebApp页面。
进一步地,参见图7,WebApp请求信息还指向对应的WebApp服务提供端,该装置还包括:
连接模块405,用于当判断模块402的判断结果是互联网状态为正常网络时,通过互联网与WebApp请求信息对应的WebApp服务提供端进行连接;
第二处理模块406,用于从WebApp服务提供端获取与WebApp请求信息对应的WebApp页面信息,根据从WebApp服务提供端获取的WebApp页面信息生成并展示WebApp页面,并根据从WebApp服务提供端获取的WebApp页面信息对本地WebApp镜像文件进行更新。
本实施例所述的WebApp启动运行的装置,当互联网状态为无网络或弱网络时,获取与WebApp请求信息对应的本地WebApp镜像文件,根据本地WebApp镜像文件,生成并展示WebApp页面,使得WebApp启动运行时不再依赖互联网,在无网络或弱网络的情况下,依然可以稳定、快速地启动运行WebApp,访问互联网服务。根据WebApp请求信息计算得到的信息-摘要算法md5值,查找本地WebApp镜像文件,可以提高获取到的与WebApp请求信息对应的本地WebApp镜像文件的准确性。根据从WebApp服务提供端获取的WebApp页面信息对本地WebApp镜像文件进行更新,保证下次在无网络或弱网络时,使用的本地WebApp镜像文件的实时性。
参见图8,本申请还公开了一种生成镜像文件的系统,该系统包括:WebApp服务提供端50和WebApp接入服务端60;
其中,WebApp服务提供端50中设置有VNC Client;
其中,WebApp接入服务端60包括:WebApp接入服务器601和远程移动终端602;远程移动终端602中设置有VNC Server;
WebApp服务提供端50,用于利用VNC Client,通过WebApp接入服务器提供的VNC Server端口,访问远程移动终端602上的VNC Server,在远程移动终端602内置的Web运行环境中进行WebApp启动运行操作;
远程移动终端602,用于通过端口映射的方法,将远程移动终端602上的VNC Server端口映射到WebApp接入服务器上;将WebApp服务提供端50进行WebApp启动运行操作时,提交的WebApp请求信息、获取的与WebApp请求信息对应的WebApp页面信息记录在本地WebApp镜像文件中。
进一步地,WebApp启动运行操作包括:访问WebApp网络地址,打开需要在无网络或弱网络状态下访问的WebApp页面。
进一步地,WebApp接入服务器601,用于将本地WebApp镜像文件推送到预设的移动终端中。
进一步地,本地WebApp镜像文件的文件名称为根据WebApp请求信息计算得到的信息-摘要算法md5值。
进一步地,本地WebApp镜像文件包括元meta镜像文件和缓存cache镜像文件。
进一步地,meta镜像文件用于存放WebApp请求信息,cache镜像文件用于存放与WebApp请求信息对应的WebApp页面信息。
本实施例所述的生成镜像文件的系统,WebApp服务提供端只需要远程进行WebApp启动运行操作,WebApp接入服务端即可自动将网络请求得到数据生成镜像文件,无需WebApp服务提供端生成,可以节约WebApp服务提供端的时间和成本。WebApp接入服务器将本地WebApp镜像文件推送到预设的移动终端中,当预设的移动终端的互联网状态为无网络或弱网络时,获取与WebApp请求信息对应的本地WebApp镜像文件,根据本地WebApp镜像文件,生成并展示WebApp页面,使得WebApp启动运行时不再依赖互联网,在无网络或弱网络的情况下,依然可以稳定、快速地启动运行WebApp,访问互联网服务。将根据WebApp请求信息计算得到的信息-摘要算法md5值作为本地WebApp镜像文件的文件名称,可以保证文件名称的唯一性,避免文件名称重复,提高获取到的与WebApp请求信息对应的本地WebApp镜像文件的准确性。
所述装置、系统与前述的方法流程描述对应,不足之处参考上述方法流程的叙述,不再一一赘述。
上述说明示出并描述了本申请的若干优选实施例,但如前所述,应当理解本申请并非局限于本文所披露的形式,不应看作是对其他实施例的排除,而可用于各种其他组合、修改和环境,并能够在本文所述发明构想范围内,通过上述教导或相关领域的技术或知识进行改动。而本领域人员所进行的改动和变化不脱离本申请的精神和范围,则都应在本申请所附权利要求的保护范围内。
Claims (30)
- 一种WebApp启动运行的方法,其特征在于,所述方法包括:接收网页应用WebApp启动指令;其中,所述WebApp启动指令中携带WebApp请求信息,所述WebApp请求信息指向对应的本地WebApp镜像文件;判断当前的互联网状态,当所述互联网状态为无网络或弱网络时,获取与所述WebApp请求信息对应的本地WebApp镜像文件;其中,所述本地WebApp镜像文件由WebApp接入服务端根据WebApp服务提供端的WebApp启动运行操作生成并推送到本地;根据所述本地WebApp镜像文件,生成并展示WebApp页面。
- 如权利要求1所述的方法,其特征在于,判断当前的互联网状态,包括:查询本地的网络;如果没有查询到网络,则确定当前的互联网状态为无网络。
- 如权利要求2所述的方法,其特征在于,查询本地的网络之后,还包括:如果查询到网络,则判断在预设的时间间隔内是否有与所述WebApp请求信息对应的WebApp页面信息返回;如果没有,则确定当前的互联网状态为弱网络。
- 如权利要求1所述的方法,其特征在于,所述WebApp请求信息包括:WebApp网络地址,或,WebApp网络地址和Post请求参数。
- 如权利要求1-4任一权利要求所述的方法,其特征在于,获取与所述WebApp请求信息对应的本地WebApp镜像文件,包括:计算所述WebApp请求信息的信息-摘要算法md5值;查找文件名称与所述md5值对应的本地WebApp镜像文件。
- 如权利要求5所述的方法,其特征在于,所述本地WebApp镜像文件包括元meta镜像文件和缓存cache镜像文件。
- 如权利要求6所述的方法,其特征在于,所述meta镜像文件用于存放WebApp请求信息,所述cache镜像文件用于存放与所述WebApp请求信 息对应的WebApp页面信息。
- 如权利要求1-4任一权利要求所述的方法,其特征在于,所述WebApp启动运行操作包括:访问WebApp网络地址,打开需要在无网络或弱网络状态下访问的WebApp页面。
- 如权利要求1-4任一权利要求所述的方法,其特征在于,所述WebApp请求信息还指向对应的WebApp服务提供端,判断当前的互联网状态之后,还包括:当所述互联网状态为正常网络时,通过互联网与所述WebApp请求信息对应的WebApp服务提供端进行连接;从所述WebApp服务提供端获取与所述WebApp请求信息对应的WebApp页面信息;根据从所述WebApp服务提供端获取的WebApp页面信息生成并展示WebApp页面,并根据从所述WebApp服务提供端获取的WebApp页面信息对所述本地WebApp镜像文件进行更新。
- 一种生成镜像文件的方法,其特征在于,所述方法包括:网页应用WebApp服务提供端利用虚拟网络计算机客户端VNC Client,通过WebApp接入服务端中的WebApp接入服务器提供的虚拟网络计算机服务端VNC Server端口,访问所述WebApp接入服务端中的远程移动终端上的VNC Server,在所述远程移动终端内置的网络Web运行环境中进行WebApp启动运行操作;所述远程移动终端将所述WebApp服务提供端进行WebApp启动运行操作时,提交的WebApp请求信息、获取的与所述WebApp请求信息对应的WebApp页面信息记录在本地WebApp镜像文件中。
- 如权利要求10所述的方法,其特征在于,所述WebApp启动运行操作包括:访问WebApp网络地址,打开需要在无网络或弱网络状态下访问的WebApp页面。
- 如权利要求10所述的方法,其特征在于,所述方法还包括:所述WebApp接入服务器将所述本地WebApp镜像文件推送到预设的移动终端中。
- 如权利要求10-12任一权利要求所述的方法,其特征在于,所述本 地WebApp镜像文件的文件名称为根据所述WebApp请求信息计算得到的信息-摘要算法md5值。
- 如权利要求10-12任一权利要求所述的方法,其特征在于,所述本地WebApp镜像文件包括元meta镜像文件和缓存cache镜像文件。
- 如权利要求14所述的方法,其特征在于,所述meta镜像文件用于存放WebApp请求信息,所述cache镜像文件用于存放与所述WebApp请求信息对应的WebApp页面信息。
- 一种WebApp启动运行的装置,其特征在于,所述装置包括:接收模块,用于接收网页应用WebApp启动指令;其中,所述WebApp启动指令中携带WebApp请求信息,所述WebApp请求信息指向对应的本地WebApp镜像文件;判断模块,用于判断当前的互联网状态;获取模块,用于当所述判断模块的判断结果是所述互联网状态为无网络或弱网络时,获取与所述WebApp请求信息对应的本地WebApp镜像文件;其中,所述本地WebApp镜像文件由WebApp接入服务端根据WebApp服务提供端的WebApp启动运行操作生成并推送到本地;第一处理模块,用于根据所述本地WebApp镜像文件,生成并展示WebApp页面。
- 如权利要求16所述的装置,其特征在于,所述判断模块包括:查询单元,用于查询本地的网络;第一确定单元,用于如果所述查询单元没有查询到网络,则确定当前的互联网状态为无网络。
- 如权利要求17所述的装置,其特征在于,所述判断模块还包括:判断单元,用于如果所述查询单元查询到网络,则判断在预设的时间间隔内是否有与所述WebApp请求信息对应的WebApp页面信息返回;第二确定单元,用于如果所述判断单元的判断结果是没有,则确定当前的互联网状态为弱网络。
- 如权利要求16所述的装置,其特征在于,所述WebApp请求信息包括:WebApp网络地址,或,WebApp网络地址和Post请求参数。
- 如权利要求16-19任一权利要求所述的装置,其特征在于,所述获取模块包括:计算单元,用于计算所述WebApp请求信息的信息-摘要算法md5值;查找单元,用于查找文件名称与所述md5值对应的本地WebApp镜像文件。
- 如权利要求20所述的装置,其特征在于,所述本地WebApp镜像文件包括元meta镜像文件和缓存cache镜像文件。
- 如权利要求21所述的装置,其特征在于,所述meta镜像文件用于存放WebApp请求信息,所述cache镜像文件用于存放与所述WebApp请求信息对应的WebApp页面信息。
- 如权利要求16-19任一权利要求所述的装置,其特征在于,所述WebApp启动运行操作包括:访问WebApp网络地址,打开需要在无网络或弱网络状态下访问的WebApp页面。
- 如权利要求16-19任一权利要求所述的装置,其特征在于,所述WebApp请求信息还指向对应的WebApp服务提供端,所述装置还包括:连接模块,用于当所述判断模块的判断结果是所述互联网状态为正常网络时,通过互联网与所述WebApp请求信息对应的WebApp服务提供端进行连接;第二处理模块,用于从所述WebApp服务提供端获取与所述WebApp请求信息对应的WebApp页面信息,根据从所述WebApp服务提供端获取的WebApp页面信息生成并展示WebApp页面,并根据从所述WebApp服务提供端获取的WebApp页面信息对所述本地WebApp镜像文件进行更新。
- 一种生成镜像文件的系统,其特征在于,所述系统包括:WebApp服务提供端和WebApp接入服务端;其中,所述WebApp服务提供端中设置有VNC Client;其中,所述WebApp接入服务端包括:WebApp接入服务器和远程移动终端;所述远程移动终端中设置有VNC Server;所述WebApp服务提供端,用于利用所述VNC Client,通过WebApp接入服务器提供的VNC Server端口,访问所述远程移动终端上的VNC Server,在所述远程移动终端内置的Web运行环境中进行WebApp启动运行操作;所述远程移动终端,用于通过端口映射的方法,将所述远程移动终端上的VNC Server端口映射到所述WebApp接入服务器上;将所述WebApp服务提供端进行WebApp启动运行操作时,提交的WebApp请求信息、获取的与所述WebApp请求信息对应的WebApp页面信息记录在本地WebApp镜像文件中。
- 如权利要求25所述的系统,其特征在于,所述WebApp启动运行操作包括:访问WebApp网络地址,打开需要在无网络或弱网络状态下访问的WebApp页面。
- 如权利要求25所述的系统,其特征在于,所述WebApp接入服务器,用于将所述本地WebApp镜像文件推送到预设的移动终端中。
- 如权利要求25-27任一权利要求所述的系统,其特征在于,所述本地WebApp镜像文件的文件名称为根据所述WebApp请求信息计算得到的信息-摘要算法md5值。
- 如权利要求25-27任一权利要求所述的系统,其特征在于,所述本地WebApp镜像文件包括元meta镜像文件和缓存cache镜像文件。
- 如权利要求29所述的系统,其特征在于,所述meta镜像文件用于存放WebApp请求信息,所述cache镜像文件用于存放与所述WebApp请求信息对应的WebApp页面信息。
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410239473.7 | 2014-05-30 | ||
| CN201410239473.7A CN105446750B (zh) | 2014-05-30 | 2014-05-30 | WebApp启动运行、生成镜像文件的方法和装置 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2015180601A1 true WO2015180601A1 (zh) | 2015-12-03 |
Family
ID=54698088
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2015/079689 Ceased WO2015180601A1 (zh) | 2014-05-30 | 2015-05-25 | WebApp启动运行、生成镜像文件的方法和装置 |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN105446750B (zh) |
| WO (1) | WO2015180601A1 (zh) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108809922A (zh) * | 2017-07-31 | 2018-11-13 | 北京视联动力国际信息技术有限公司 | 一种音频故障处理方法、会议调度端和视联网终端 |
| CN109120615A (zh) * | 2018-08-14 | 2019-01-01 | 上海陆家嘴国际金融资产交易市场股份有限公司 | 信息查看的方法、装置、计算机设备和存储介质 |
| CN111338949A (zh) * | 2020-02-25 | 2020-06-26 | 深圳忆联信息系统有限公司 | 通过无线启动批量进入winpe的方法、装置、计算机设备及存储介质 |
| CN113656184A (zh) * | 2021-08-31 | 2021-11-16 | 北京沃东天骏信息技术有限公司 | 数据处理方法及装置 |
| CN114706622A (zh) * | 2022-03-10 | 2022-07-05 | 北京百度网讯科技有限公司 | 启动模型服务的方法、装置、设备、介质及产品 |
Families Citing this family (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106649595B (zh) * | 2016-11-22 | 2020-10-27 | 腾讯科技(深圳)有限公司 | 一种基于对象池的网页启动加速方法、装置及终端 |
| CN106897095B (zh) * | 2017-02-24 | 2020-10-13 | 网易(杭州)网络有限公司 | 应用程序热修复的方法、装置、可读存储介质和计算设备 |
| WO2019184053A1 (zh) * | 2018-03-28 | 2019-10-03 | 华为技术有限公司 | 一种浏览应用页面的方法及终端 |
| CN108228282B (zh) * | 2018-04-04 | 2021-08-27 | 北京三快在线科技有限公司 | 用于网站页面加载的方法及装置 |
| CN108959455B (zh) * | 2018-06-15 | 2020-12-04 | 未鲲(上海)科技服务有限公司 | 单页Web应用实现方法、装置、计算机设备和存储介质 |
| CN108845816B (zh) * | 2018-06-22 | 2021-09-10 | 平安科技(深圳)有限公司 | 应用程序更新方法、系统、计算机设备及存储介质 |
| CN109376323B (zh) * | 2018-09-11 | 2023-06-16 | 平安科技(深圳)有限公司 | 应用运行方法、装置、计算机装置及存储介质 |
| CN109213560B (zh) * | 2018-09-12 | 2020-11-27 | 南京尚网网络科技有限公司 | 一种资讯页面展示的方法及设备 |
| CN111597021B (zh) * | 2020-05-07 | 2023-07-18 | 东软集团股份有限公司 | 一种实现应用程序运行的方法、装置、系统及相关设备 |
| CN111782989B (zh) * | 2020-07-03 | 2022-11-18 | Oppo广东移动通信有限公司 | 快应用的关联方法及相关装置 |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101459571A (zh) * | 2008-12-16 | 2009-06-17 | 北京大学 | 一种网站镜像的方法、系统及装置 |
| CN103186594A (zh) * | 2011-12-29 | 2013-07-03 | 盛乐信息技术(上海)有限公司 | WebAPP动态脱机存储系统及方法 |
| US20130238808A1 (en) * | 2012-03-06 | 2013-09-12 | Mobile Helix, Inc | Mobile link system, method & apparatus |
| CN103473082A (zh) * | 2012-06-08 | 2013-12-25 | 腾讯科技(深圳)有限公司 | 一种启动WebApp的方法及装置 |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102523207A (zh) * | 2011-12-06 | 2012-06-27 | 北京航空航天大学 | 基于虚拟网络计算机的远程资源访问方法及代理设备 |
| CN102833350A (zh) * | 2012-09-11 | 2012-12-19 | 优视科技有限公司 | WebApp更新的处理方法和处理装置 |
| CN103051684B (zh) * | 2012-12-07 | 2017-03-15 | 百度在线网络技术(北京)有限公司 | 将网站转化为Web App进行展示的方法、系统和装置 |
-
2014
- 2014-05-30 CN CN201410239473.7A patent/CN105446750B/zh active Active
-
2015
- 2015-05-25 WO PCT/CN2015/079689 patent/WO2015180601A1/zh not_active Ceased
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101459571A (zh) * | 2008-12-16 | 2009-06-17 | 北京大学 | 一种网站镜像的方法、系统及装置 |
| CN103186594A (zh) * | 2011-12-29 | 2013-07-03 | 盛乐信息技术(上海)有限公司 | WebAPP动态脱机存储系统及方法 |
| US20130238808A1 (en) * | 2012-03-06 | 2013-09-12 | Mobile Helix, Inc | Mobile link system, method & apparatus |
| CN103473082A (zh) * | 2012-06-08 | 2013-12-25 | 腾讯科技(深圳)有限公司 | 一种启动WebApp的方法及装置 |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108809922A (zh) * | 2017-07-31 | 2018-11-13 | 北京视联动力国际信息技术有限公司 | 一种音频故障处理方法、会议调度端和视联网终端 |
| CN108809922B (zh) * | 2017-07-31 | 2019-07-05 | 视联动力信息技术股份有限公司 | 一种音频故障处理方法、会议调度端和视联网终端 |
| CN109120615A (zh) * | 2018-08-14 | 2019-01-01 | 上海陆家嘴国际金融资产交易市场股份有限公司 | 信息查看的方法、装置、计算机设备和存储介质 |
| CN111338949A (zh) * | 2020-02-25 | 2020-06-26 | 深圳忆联信息系统有限公司 | 通过无线启动批量进入winpe的方法、装置、计算机设备及存储介质 |
| CN113656184A (zh) * | 2021-08-31 | 2021-11-16 | 北京沃东天骏信息技术有限公司 | 数据处理方法及装置 |
| CN114706622A (zh) * | 2022-03-10 | 2022-07-05 | 北京百度网讯科技有限公司 | 启动模型服务的方法、装置、设备、介质及产品 |
| CN114706622B (zh) * | 2022-03-10 | 2023-08-18 | 北京百度网讯科技有限公司 | 启动模型服务的方法、装置、设备、介质及产品 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105446750A (zh) | 2016-03-30 |
| HK1221295A1 (zh) | 2017-05-26 |
| CN105446750B (zh) | 2019-12-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2015180601A1 (zh) | WebApp启动运行、生成镜像文件的方法和装置 | |
| US11509708B2 (en) | Application sharing method and apparatus | |
| US10412176B2 (en) | Website access method, apparatus, and website system | |
| RU2608668C2 (ru) | Система и способ управления и организации кэша веб-браузера для обеспечения автономного просмотра | |
| US20150304440A1 (en) | Systems and Methods for Pushing Applications | |
| US10097659B1 (en) | High performance geographically distributed data storage, retrieval and update | |
| CN106708899A (zh) | 自动埋点方法和装置 | |
| CN104335524B (zh) | 用于客户端侧页面处理的公共web可访问数据存储 | |
| CN107003877A (zh) | 应用的上下文深层链接 | |
| US20140337408A1 (en) | Systems, methods and media for minimizing data downloads | |
| CN108846100A (zh) | 快速搜索寄宿应用的方法及设备 | |
| US10678881B2 (en) | Usage-based predictive prefetching and caching of component-based web pages for performance optimization | |
| CN104158885B (zh) | 一种基于位置信息流式加载应用的方法和系统 | |
| CN110968331B (zh) | 应用程序运行的方法和装置 | |
| US11263297B2 (en) | Dynamic insertion of variablized secrets in a pipeline integration system | |
| US20180063234A1 (en) | Assigning client virtual machines based on location | |
| CN111783010B (zh) | 网页空白页面监测方法、装置、终端及存储介质 | |
| CN113326418A (zh) | 用于确定网页信息源及网页质量的方法和装置 | |
| CN108256014A (zh) | 页面展示方法及装置 | |
| TWI677223B (zh) | 頁面顯示的方法及裝置 | |
| CN108140037A (zh) | 在后台预先实例化本原应用 | |
| JP2020502702A (ja) | オンライントランザクションの成功率の向上 | |
| CN106649588B (zh) | 一种获取已安装应用程序列表的方法、装置及系统 | |
| US9658935B1 (en) | Processing file modifications in a networked storage system | |
| WO2015058614A1 (zh) | 一种书签存储方法及装置、确定待浏览书签的方法及装置 |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 15799320 Country of ref document: EP Kind code of ref document: A1 |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 15799320 Country of ref document: EP Kind code of ref document: A1 |

