CN104808971A - Network application program manager, method, device and mobile terminal - Google Patents

Abstract

The invention discloses a network application program manager, method, device and mobile terminal. The network application program manager includes: a user interaction interface unit for interacting with users; a network interface unit for obtaining network application programs; a network application program parser for running network application programs; a network application program adapter , for registering the web application with the mobile terminal, instructing the mobile terminal to run the corresponding local application or web application in response to the request of the web application, or instructing the web application resolver to run the corresponding web application.

Description

Network application program manager, method, device and mobile terminal

technical field

The present invention relates to the field of mobile terminals, and more specifically, to a network application manager capable of effectively managing network applications in a mobile terminal, a network application management method, a network application management device, and a network application management device including the network application Program manager for mobile terminals.

Background technique

In recent years, the number of web applications (Web App) has increased day by day. With the support of HTML5 and mobile operating systems iOS, Android, and Windows Phone, Web App will soon become an important application direction.

Web App is an application software that uses a web browser to operate on the Internet or an intranet. It is an application program written in a web language (such as HTML, JavaScript, Java, etc.) and needs to be run through a browser.

One of the reasons for the popularity of Web App is that it can run directly on various computer platforms without prior installation or regular upgrades. Common web application programs include many applications such as Webmail, online stores, online auctions, wikis, online forums, blogs, and online games.

Web App has many advantages: 1) It is easy to achieve cross-platform, and mobile application developers no longer need to consider complex underlying adaptation and cross-platform development language issues; because Web App runs in a web browser window, most cases 2) Web App does not require any complicated "unfolding" process, all the user needs is a suitable browser; 3) Web App usually consumes a lot of time Less user hard disk space, or no consumption at all; 4) Web App does not need to be updated, because all new features are executed on the server, and thus automatically communicated to the user; 5) Web App and server-side network products are easy Combination, such as email function and search function. In addition, the development cost of Web App is low, adaptable to a variety of mobile terminal devices, easy to replace and update, no installation and other features are also very attractive.

However, Web App has its own fatal shortcomings: 1) Web App is an isolated application. To obtain terminal services, it must rely on local client for adaptation; 2) Web App needs network support to use; Web App relies on The application files on the remote server side of the Internet, so when there is a problem with the connection, the Web App will not work normally; 3) The Web App is relatively scattered and has no good unified management, so it cannot be organically combined with local applications and systems.

The user experience effect of Web App is unsatisfactory, not as good as that of local application (Native App). The Web App runs slowly, and the local function of calling the terminal is weak. In contrast, Native App can provide users with a better experience, save network traffic, and provide rich and powerful local function calls, which are efficient and fast.

Aiming at the advantages and disadvantages of both Web App and Native App, the idea of Web App+Native App emerged, and a type of application called Hybrid App (hybrid application) was created. It looks like a Native App, but it has only one user interface. , which accesses the Web App. HybridApp makes Web App free from browser dependence, and can use some local system services to a certain extent. At present, many companies are working on the research of Web App and the combination of Web App+Native App. For example, the Baidu client, the user installs and downloads the software on the mobile phone, and uses some Web Apps through the Baidu client. The Baidu client plays the role of a browser, and at the same time encapsulates some system service interfaces to provide some local functions for the Web App. UC browser and Firefox browser also adopt a similar idea.

However, the application method of Web App+Native App still focuses on the Web App to obtain the local system services of the terminal, such as calling the SMS interface, instead of treating the Web App and Native App as equivalent Apps, and lacks Web App and Native App. App interaction design and solutions.

Contents of the invention

Therefore, an object of the present invention is to provide a web application manager installed in a mobile terminal, a web application management method, and the mobile terminal including the web application manager, wherein the web application manager can View web applications and local applications in a peer-to-peer manner, and realize interactive access between web applications and local applications.

According to one aspect of the present invention, a network application program manager is provided, including: a user interaction interface unit, used to interact with users; a network interface unit, used to obtain network application programs; a network application program parser, used to run A network application; a network application adapter, used to register the network application with the mobile terminal, respond to the request of the network application, instruct the mobile terminal to run the corresponding local application or network application, or respond to the request of the local application, Instructs the web application resolver to run the corresponding web application.

Preferably, the web application parser runs a specific web application in a background mode.

Preferably, in response to a user's selection of a specific web application run by the web application parser through the user interaction interface unit, the specific web application is cached in the memory of the mobile terminal.

Preferably, the network application adapter registers with the mobile terminal the network application selected by the user through the user interaction interface unit, or registers with the mobile terminal the default network application of the mobile terminal, or registers with the mobile terminal the network application that has been run through the network application parser A network application program, or a network application program registered with the mobile terminal and cached in the memory of the mobile terminal.

Preferably, the web application adapter registers the web application with the operating system of the mobile terminal.

Preferably, the network application adapter registers the ID and configuration information of the network application with the operating system of the mobile terminal, and the configuration information includes the types of data processed by the network application and the types of services provided.

Preferably, the network application adapter registers the ID and configuration information of the network application with the operating system of the mobile terminal, and the configuration information includes the information of the local application targeted by the network application and the service type provided by the network application.

Preferably, the network application adapter instructs the operating system of the mobile terminal to search for the corresponding local application or network application in response to the request of the network application, wherein, when the operating system searches for the corresponding local application, the operating system executes the search to the local application, and returns the running result of the searched local application to the requesting network application through the network application adapter, wherein, when the operating system searches for the corresponding network application according to the configuration information of the registered network application application, the operating system passes the web application's request to the web application adapter, so that the web application adapter instructs the web application resolver to run the corresponding web application, and the web application resolver sends the corresponding web application's run Results are returned to the requesting web application.

Preferably, the network application adapter instructs the network application resolver to run the corresponding network application in response to the request of the local application run by the operating system of the mobile terminal, wherein the network application resolver communicates with the mobile terminal through the network application adapter The operating system returns the running result of the corresponding web application to the requesting local application.

Preferably, the network application adapter instructs the network interface unit to search for the corresponding network application in response to the request of the local application run by the operating system of the mobile terminal, wherein the network application parser runs the searched corresponding network application, And return the running result of the corresponding network application program to the requesting local application program through the network application program adapter and the operating system of the mobile terminal.

Preferably, wherein, the operating system of the mobile terminal determines the network application that matches the request of the local application run by the operating system according to the configuration information of the registered network application, and transmits information about the matched network application to the network application The adapter, the web application adapter instructs the web application resolver to run the matching web application based on the information about the matching web application, wherein the web application resolver uses the web application adapter and the operating system of the mobile terminal to match the The results of the web application run are returned to the requesting local application.

Preferably, when a specific web application program running in the background mode by the web application parser receives an update message through the network interface unit, the web application parser parses the update message, and the web application adapter controls the mobile terminal to display notify.

According to another aspect of the present invention, there is provided a network application management method, including the following steps: (a) registering the network application with the mobile terminal; (b) when running the network application, responding to the running network application request, run the corresponding local application or web application; (c) when running the local application, run the corresponding web application in response to the request of the running local application.

Preferably, the registered network application program is a network application program selected by the user, a default network application program of the mobile terminal, a network application program that has been run through the operating system of the mobile terminal, or a network application program that has been cached in the memory of the mobile terminal .

Preferably, in step (a), the web application is registered with the operating system of the mobile terminal.

Preferably, in step (a), the ID and configuration information of the network application are registered with the operating system of the mobile terminal, and the configuration information includes the types of data processed by the network application and the types of services provided.

Preferably, in step (a), the ID of the network application and configuration information are registered with the operating system of the mobile terminal, and the configuration information includes the information of the local application targeted by the network application and the service type provided by the network application.

Preferably, in step (b), in response to the request of the web application, search for a corresponding local application or web application, wherein, when the corresponding local application is found, run the searched local application, and Return the running result of the searched local application program to the requesting web application program, wherein, when the corresponding web application program is searched according to the configuration information of the registered web application program, the request of the web application program is transmitted, and in response to the transmission The request runs the corresponding web application, and returns the running result of the corresponding web application to the requesting web application.

Preferably, in step (c), in response to the request of the running local application, run the corresponding network application, wherein the running result of the corresponding network application is returned to the requesting local application.

Preferably, in step (c): searching for the corresponding network application program, and running the corresponding searched network application program, wherein the running result of the corresponding network application program is returned to the requesting local application program.

Preferably, in step (c), a web application that matches the request of the running native application is determined according to the configuration information of the registered web application, and information about the matched web application is transmitted, based on information about the matched web application The information of the program runs the matching web application, wherein the running result of the matching web application is returned to the requesting local application.

According to another aspect of the present invention, a network application program management device is provided, including: a first module, registering the network application program with the mobile terminal; a second module, when running the network application program, responding to the running network application program The request is to automatically run the corresponding local application program or network application program; the third module is to automatically run the corresponding network application program in response to the request of the running local application program when running the local application program.

Preferably, the second module searches for the corresponding local application or network application in response to the request of the network application, wherein, when the corresponding local application is found, the searched local application is run, and the searched The running result of the local application program is returned to the requesting web application program, wherein, when the corresponding web application program is searched according to the configuration information of the registered web application program, the request of the web application program is transmitted, and the corresponding web application program is executed in response to the transmitted request. web application, and returns the execution result of the corresponding web application to the requesting web application.

Preferably, the third module executes the corresponding network application in response to the request of the running local application, wherein the running result of the corresponding network application is returned to the requesting local application.

Preferably, the third module searches for corresponding network applications, and executes the corresponding searched network applications, wherein the running result of the corresponding network applications is returned to the requesting local application.

Preferably, the third module determines a web application that matches the request of the running local application according to the configuration information of the registered web application, transmits information about the matched web application, and runs based on the information about the matched web application A matching web application, wherein the execution result of the matching web application is returned to the requesting native application.

According to another aspect of the present invention, there is provided a mobile terminal including the web application manager as described above.

According to another aspect of the present invention, there is provided a mobile terminal including the above-mentioned apparatus for managing network application programs.

According to the present invention, the Web App and the Native App can be regarded as equivalent Apps, and the seamless connection between the Web App and the Native App can be realized, thereby improving the running speed of the Web App and the Native App.

Description of drawings

These and/or other aspects and advantages of the present invention will become clearer and easier to understand through the following description of the embodiments in conjunction with the accompanying drawings, in which:

FIG. 1 is a block diagram illustrating a mobile terminal according to an exemplary embodiment of the present invention;

Fig. 2 is a block diagram showing the structure of a Web App manager according to an exemplary embodiment of the present invention;

Fig. 3 is a flowchart illustrating a Web App management method according to an exemplary embodiment of the present invention;

Fig. 4 shows another exemplary framework of Web App manager;

Figure 5 shows another exemplary architecture of the Web App manager

FIG. 6 shows a diagram of the architecture of the Web App manager installed in a mobile terminal using the Android operating system according to an exemplary embodiment of the present invention;

Fig. 7 is a flowchart illustrating a Web App management method according to an exemplary embodiment of the present invention;

FIG. 8 shows a block diagram of a Web App management device according to an exemplary embodiment of the present invention.

Detailed ways

The present invention is described more fully hereinafter with reference to the accompanying drawings, in which exemplary embodiments of the invention are shown. However, this invention may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art.

It should be understood that although the terms first, second, third, etc. may be used herein to describe various elements, components, regions, layers and/or sections, these elements, components, regions, layers and/or sections do not should be limited by these terms. These terms are only used to distinguish one element, component, region, layer or section from another element, component, region, layer or section. Thus, a first element, component, region, layer or section discussed below could be termed a second element, component, region, layer or section without departing from the teachings of the present invention. As used herein, the term "and/or" includes any and all combinations of one or more of the associated listed items.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, singular forms are intended to include plural forms unless the context clearly dictates otherwise. It should also be understood that when the terms "comprises" and/or "comprises" are used in this specification, it means that the features, integers, steps, operations, elements and/or components exist, but does not exclude the existence or addition of one or more Various other features, integers, steps, operations, elements, components and/or groups thereof.

Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. It will also be understood that, unless expressly defined herein, terms (such as those defined in commonly used dictionaries) should be construed to have a meaning consistent with their meaning in the context of the relevant art, and not in an ideal or overly formal manner to explain them.

Here, a mobile terminal means a computing device that can perform a voice call function while moving, including a portable phone, a smart phone, and the like.

Hereinafter, the present invention will be explained in detail with reference to the accompanying drawings.

FIG. 1 is a block diagram illustrating a mobile terminal according to an exemplary embodiment of the present invention.

1, the mobile terminal 100 includes a central processing unit (CPU) 110, an input unit 120, a camera unit 130, a broadcast receiving unit 140, a memory 150, a wireless communication unit 160, a speaker 171, a microphone 172, a display unit 180, and a web application program (Web App) Manager 190.

The CPU 110 can control the overall operation of the mobile terminal, and can include a decoder (not shown) for decoding audio streams and video streams. The CPU 110 can process and control communications (for example, voice communications and data communications), decode and output audio streams and video streams. In addition, the CPU 110 can control the display unit 180 to display various user interfaces, for example, an input interface including a virtual keyboard. According to an exemplary embodiment of the present invention, the CPU 110 may execute an Operating System (OS) installed to the mobile terminal. The operating system is capable of managing various applications that have been installed to the terminal. For example, for the Android operating system, the Android operating system may have an activity manager (Activity Manager) and a package manager (Package Manager). The activity manager and the package manager are the core modules of the framework (Framework) layer of the Android operating system, and they can manage various applications that have been installed on the terminal. The activity manager and the package manager can be easily implemented by those skilled in the art based on the prior art, and will not be described in detail here. At least some of the functionality of the campaign manager and package manager will be described below in conjunction with the web application manager.

In case the display unit 180 is implemented as a touch screen, the input unit 120 may have only a few keys. For example, a power button used for turning on and off a mobile terminal.

The camera unit 130 may include a lens, an imaging sensor such as a Charge Coupled Device (CCD) or a Complementary Metal Oxide Semiconductor (CMOS) sensor, an analog-to-digital (A/D) converter, and the like. The camera unit 130 may acquire an image signal by capturing an image of a subject, may convert the acquired image signal into a digital signal, and may transmit the digital signal to the CPU 110. The CPU 110 may perform image processing such as noise removal and color processing on the digital signal provided by the camera unit 130. The CPU 110 may display an image of a subject captured by the camera unit 130 on the display unit 180.

The broadcast receiving unit 140 may receive a broadcast program through a broadcast channel such as a terrestrial broadcast channel, a satellite broadcast channel, or a two-way channel such as the Internet. In the case that the broadcast receiving unit 140 receives a broadcast program through a broadcast channel, the broadcast receiving unit 140 may include: a tuner (not shown) for outputting a transport stream through tuning, and for demodulating an input broadcast signal; A user (not shown) demultiplexes the transport stream output by the tuner into a video stream and an audio stream.

The memory 150 may store programs for controlling overall operations of the mobile terminal 100 . For example, the memory 150 can store the operating system of the mobile terminal, various configuration programs used by the CPU 110, local application programs, and the like. In addition, the memory 150 temporarily stores data generated during operation as well as other data. For example, memory 150 may store video files, audio files, text, and the like. Memory 150 may also store cached web applications.

The wireless communication unit 160 may perform wireless communication with other mobile terminals or various servers. For example, after the mobile terminal 100 performs user identity authentication by using the user identification information stored in the memory 150, the mobile communication terminal 100 will access the wireless network, so that the wireless communication unit 160 can communicate with other mobile terminals via the mobile communication network. Wireless communication. The wireless communication unit 160 can be configured to support various communication protocols, such as Bluetooth, Zigbee, WLAN, Wi-Fi, home RF, UWB, wireless 1394, or combinations thereof.

The speaker 171 reproduces audio data transmitted and received during a call, audio data included in a received message, reproduced audio data according to an audio file stored in the storage unit 150, and the like. The microphone 172 may receive audio signals from the outside of the mobile communication terminal 100, and may transmit the received audio signals to the CPU 110.

The display unit 180 may display various user interfaces. In the case that the display unit 180 is implemented as a touch screen, the touch screen can sense a user's touch through a touch sensor disposed thereunder, and send a touch signal generated due to the user's touch to the CPU 110, so that the CPU 110 executes a corresponding operate. For example, the touch screen can display a virtual keyboard, and the virtual keyboard can include virtual number keys and virtual function keys as objects. When a user taps a specific object, the touch screen sends a corresponding touch signal to the CPU 110 .

The web application program (Web App) manager 190 can be an independent hardware component, or a software component running in the mobile terminal. Web App manager 190 includes a user interaction interface unit for interacting with users, a network interface unit for obtaining Web App, a Web App parser for running Web App, and a Web App adapter, wherein the Web App adapter can Register the Web App with the mobile terminal, instruct the mobile terminal to run the corresponding local application (Native App) or other Web App in response to the request of the Web App, or instruct the Web App parser to run the corresponding Web App in response to the request of the Native App . In this way, through the Web App adapter, the Web App and the Native App can be regarded as peer-to-peer applications, thereby realizing the interaction between the Web App and the Native App.

The Web App manager and the Web App management method are specifically described below with reference to FIGS. 2 and 3 .

FIG. 2 is a block diagram illustrating a structure of a Web App manager according to an exemplary embodiment of the present invention.

Referring to FIG. 2, the Web App manager includes a user interaction interface unit 201, a network interface unit 202, a Web App parser 203, and a Web App adapter 204.

According to an exemplary embodiment of the present invention, the Web App manager serves as a management container of the Web App, provides a hosting space for the Web App, and can perform unified management on the Web App. For example, when a user needs to use a certain Web App, the Web App manager can access the Web App through the network interface unit 202, run the Web App through the Web App parser 203, and provide the user with the information of the Web App through the user interaction interface unit 201. operation result. That is, Web App can run on Web App Manager. Generally speaking, because the Web App uses a front-end programming language (usually JavaScript scripting language) to write codes, this programming language cannot be directly run on the user terminal and requires local support, so the Web App manager is provided with a Web App parser 203. Here, the Web App parser 203 running the Web App refers to parsing the programming language of the Web App into a local executable language through the JS engine in the WebKit browser kernel. Through the above logic, the Web App can run normally on the Web App manager. The Web App manager is equivalent to a browser, so that the Web App can be loaded and run, display results, and interact with users. Figure 3 shows an exemplary architecture of a Web App manager. As shown in Figure 3, the Web App manager manages multiple Web Apps, and the Web App parser 203 parses the programming language of the Web App into a local executable language through the JS engine in the WebKit browser kernel, thereby running each Web App.

Taking the Android platform as an example, the Android system provides a WebView control, which can provide powerful web page display functions, including support for JavaScript. The WebView control can run the JS language through the underlying packaged WebCore. In this case, the Web App manager can provide each Web App with a WebView control, so that each Web App can run independently, display and interact with users. In other words, the Web App parser 203 can provide a WebView control for the Web App selected by the user and the Web App running by default on the mobile terminal. Figure 4 shows another exemplary architecture of a Web App manager. As shown in Figure 4, the Web App manager manages multiple Web Apps. The WebApp parser 203 interacts with the JS engine in the WebKit browser kernel by providing the WebView control, and parses the programming language of the Web App into a local executable language, thereby running each WebApp.

In the mobile terminal of the prior art, when other applications need to continue processing after the local application 1 (Native App1) processes certain data, Native App1 will throw an Intent (intent) to notify the operating system, and the operating system will The content (including data type, data content, data response action, etc.) selects other Native Apps that can continue to process the Intent to provide follow-up services. The processing of Intents interacting between Native Apps is performed through the above-mentioned activity manager and package manager. For example, if the local application 2 (Native App2) meets the requirements of NativeApp1, then Native App2 will be invoked by the operating system to provide services. After Native App2 completes the service, it can choose to return the data result to Native App1 so that Native App1 can continue processing.

According to an exemplary embodiment of the present invention, the Web App can be registered with the operating system of the mobile terminal (for example, the package manager under the Android operating system) through the Web App adapter 204. In this way, when Native App1 needs to request a certain service, the operating system can check whether there is a Web App that meets the requirements of Native App1 according to the registration information of the Web App adapter 204. If it is found that WebApp1 meets the requirements, the operating system will prompt the user whether to choose to run the WebApp1 that meets the requirements. If the user chooses to run Web App1, the operating system communicates the user's selection to Web App adapter 204, so that Web App adapter 204 can instruct Web App resolver 203 to run Web App1 hosted in the Web App manager. More specifically, the Web App adapter 204 obtains the Intent thrown by the Native App1, parses the Intent, and instructs the Web App parser 203 to transmit the parsed data content to Web App1, thereby running Web App1.

After Web App1 finishes processing the data, Web App1 will return the processing result to Web App adapter 204, and Web App adapter 204 will return the data information to Native App1, so as to realize the seamless interaction between local applications and network applications.

Each component of the Web App manager is described in detail below.

As mentioned above, the user interaction interface unit 201 can be used to interact with the user. Specifically, the user interaction interface unit 201 can display a user interface through the display unit 180, so that the user can perform various operations through the displayed user interface. For example, the user can view all the Web Apps managed and maintained by the WebApp manager through the displayed user interface, select the Web App that is expected to run, select the Web App that is expected to be registered, and display the running Web App and its running results after being selected by the user.

The network interface unit 202 is used to obtain network application programs. For example, the network interface unit 202 can obtain a Web App from the network by means of the wireless communication unit 160. Figure 5 shows another exemplary architecture of a Web App manager. As shown in Figure 5, the Web App manager manages multiple Web Apps. The network interface unit 202 can obtain the Web App from the network through a Web App search engine or a Web App server.

Web App parser 203 is used to run Web App. Specifically, the Web App parser 203 parses the programming language of the Web App, so that the Web App can run on the mobile terminal device. On the other hand, the Web App parser 203 can also provide a unified interface, so that the Web App can obtain some local services of the system through the Web App parser 203. For example, the Web App parser 203 provides a text message sending function, and the WebAppManager.sendTextMessage interface can be defined in advance, so that when the WebApp uses this interface, the Web App parser 203 converts the interface into a system text message interface. For example, in the Android system, the Web App parser 203 calls the SmsManager.sendTextMessage interface of the system to convert the Web App request into a system function.

The Web App adapter 204 can register the Web App with the operating system of the mobile terminal, can respond to the request of the Web App, instruct the mobile terminal to run the corresponding Native App or Web App, and can also instruct the Web App parser 203 in response to the request of the Native App Run the corresponding Web App. For example, the Web App parser 203 can register the Web App selected by the user through the user interaction interface unit 201 with the operating system of the mobile terminal, or register the default Web App of the mobile terminal with the operating system of the mobile terminal, or register with the operating system of the mobile terminal. The Web App that has been run through the Web App parser 203, or the Web App that has been cached is registered with the operating system of the mobile terminal. For example, Web App adapter 204 can interact with a package manager and/or an application manager. The Web App manager pre-defines (according to user selection or default definition) data service support types (can be defined by MIME types). If a Web App provides a certain service (for example, a Web App provides image processing functions), the Web App needs Described in its configuration file (declaring that this Web App supports MIME data of IMAGE type), the Web App adapter 203 can read the configuration information of the Web App, and register the Web App with the operating system of the mobile terminal. When a Native App requests a certain service (for example, requesting image processing), the operating system will find a matching Web App, and send a request to the WebApp adapter 204 to start and run the Web App through the Web App parser 203. Conversely, when the Web App requires the Native App to continue processing data, the Web App adapter 204 can search for a suitable Native App through the operating system and start the Native App through the operating system for processing.

For a common type of Web App, the Web App adapter 204 can register the ID and configuration information of the Web App with the operating system of the mobile terminal, and the configuration information includes the type of data processed by the Web App, the type of service provided, and the like. General-purpose Web App refers to a Web App that is not developed specifically for a Native App. The interaction process between general type Web App and Native App will be described in detail later.

On the other hand, according to the exemplary embodiment of the present invention, it is possible to design a Web App with a specific function for a specific application, that is, a specific type of Web App. For a specific type of Web App, the Web App adapter 203 registers the ID and configuration information of the Web App with the operating system of the mobile terminal, and the configuration information includes the information of the Native App targeted by the Web App (such as package name, class name, version number) And the type of service provided by the Web App. In fact, specific types of Web App application scenarios are very extensive. For example, if a manufacturer develops a Native App, but then needs to upgrade or update the Native App, the manufacturer can use a specific type of Web App to provide extended services for the Native App, or another manufacturer can develop other extensions and supplements for the manufacturer's software products A specific type of Web App for functionality. In this way, the cost of development and maintenance can be reduced, and the efficiency can be improved. Specifically, a certain manufacturer A has developed a reading software Native App1, which can read txt text files. The user downloads and installs the Native App1, but finds that Native App1 does not support reading pdf files. Manufacturer A or other manufacturers can target Native App1. Develop Web App2. When a user uses Native App1 to open a pdf file, Native App1 does not support the file type, but Web App2 can be found to provide services.

According to an exemplary embodiment of the present invention, the Web App manager provides unified management and caching functions of Web Apps. Generally speaking, Web App needs to be connected to the Internet to be used normally. In view of the hardware and software resources of the mobile network and mobile terminals, the cache demand of Web App is increasing at present. The cached Web App loads and runs faster and can run offline. At present, many caching solutions have been proposed and put into practice, and Web App caching technology has also been added to HTML5. Therefore, we will not discuss more about Web App caching here, but only expand the existing technology. In order to allow the user to use the Web App as if using the Native App, the Web App manager will prompt the user through the user interaction interface unit 201 whether to choose to cache the Web App each time a cacheable Web App is successfully loaded. If the user chooses to cache the Web App, the Web App manager will assign an ID to the Web App (which can be defined as WAID, that is, Web App ID). The Web App adapter 204 can bind and record the configuration information of the Web App with the WAID, and register with the operating system of the mobile terminal at the same time. Thereafter, when the NativeApp requests the service, the Web App adapter 204 can find the corresponding Web App and invoke the Web App.

In addition, the Web App once used by the user may be cached in the memory 150, or may be cached in a memory (not shown) set in the Web App manager, and registered to the operating system of the mobile terminal. For Web Apps that have not been used by users, the Web App Manager can provide a keyword search function. For example, the user can use the user interface provided by the user interface unit 201 to search, and search for related Web Apps through the Web App search engine (not shown) set in the Web App.

In addition, the Web App manager can perform background management on the cached Web App. An important function of the Web App is to communicate with the server in the background to update data, and users can see the latest real-time information and information through the Web App. According to an exemplary embodiment of the present invention, the network interface unit 202 provides a Push message management function. The type of Web App is registered as PUSH_MSG through the configuration file (WA profile) in advance, and the Web App parser 203 will run and manage the cached Web App of type PUSH_MSG in the background mode. The PUSH_MSG type Web App can connect to the server in real time through Ajax and other methods to obtain the latest news and information. After obtaining the information update, the Web App can call the interface WebAppManager.notifyPushMessage defined in advance by the Web App manager. At this point, the Web App parser 203 can parse WebAppManager.notifyPushMessage into a local executable code interface, and then call the notification module of the system platform through the Web App adapter 204 to notify the user. For example, in the Android system, the Web App adapter 204 can choose to call the notification interface of the NotificationManager to send the update message of the Web App to the broadcast bar of the system, and the user can choose to click the prompt in the notification bar to enter the Web App interface to view detailed information .

The following describes the interaction between Web App and Native App in detail.

When the Native App needs to request the Web App to provide services during operation, the operating system of the mobile terminal can search for a suitable Web App from the registered Web App, that is, search whether there is a Web App in the registered Web App that matches the Intent of the Native App. App. When the operating system searches for a suitable Web App (that is, a matching Web App), the operating system transmits the request of the Native App to the Web App adapter 204. The Web App adapter 204 instructs the Web App resolver 203 to run the corresponding Web App in response to the request sent by the operating system. For example, the operating system determines the WebApp that matches the request of the Native App running on the operating system according to the configuration information of the registered Web App, and transmits information about the matched Web App to the Web App adapter 204, and the Web App adapter 204 is based on the matching Web App. App information, instructs the Web App resolver 203 to run the matching Web App. Afterwards, after the Web App is processed, the Web App parser 203 can return the running result of the Web App to the requesting Native App through the network application adapter and the operating system. However, if the operating system fails to search for a suitable WebApp among the registered Web Apps, the operating system may transmit the Intent of the Native App to the Web App adapter 204 . At this point, the Web App adapter 204 can instruct the network interface unit 202 to search for a suitable Web App on the network. When a suitable Web App is found on the network, the Web App adapter 204 can instruct the user interaction interface unit 201 to prompt the user whether to choose to use the found Web App, or automatically instruct the Web App parser 203 to run the found Web App.

On the other hand, when the Web App needs to request the Native App to provide services during operation, the WebApp adapter 204 responds to the Web App's request and instructs the operating system to search for the corresponding Native App. In this case, the Web App can call the predefined interface of the Web App manager, and encapsulate the request of the Web App as an Intent through the WebApp adapter 204 and throw it to the operating system. Afterwards, when the operating system searches for a corresponding Native App, the operating system runs the found Native App for processing, and returns the running result of the Native App to the requesting Web App through the Web App program adapter 204. Optionally, if the Web App needs to request other Web Apps to provide services during operation, the Web App adapter 204 responds to the request of the Web App and instructs the operating system to search for other Web Apps according to the configuration information of the registered Web App. When the operating system searches for the corresponding Web App, the operating system transmits the request of the Web App to the Web App adapter 204, so that the Web App adapter 204 instructs the Web App parser 203 to run the corresponding web application. Thereafter, the Web App parser 203 can return the running result of the corresponding Web App to the requesting Web App.

In the following, three examples of interaction between Web App and Native App are described.

First, for a common type of Web App, when the user selects a file of an unknown type in the file manager to open, the file manager encapsulates the file URI and type information into an Intent and throws it to the operating system to find a matching application. When the operating system does not find a matching Native App based on the file type, the operating system continues to search for the cached Web App. If the operating system finds a cached Web App, it requests the Web App adapter 204 to run the Web App. At this point, the Web App adapter 204 can run the Web App through the Web App resolver 203 to open the file. If the operating system does not find the cached Web App, the operating system continues to search for other registered Web Apps, and transmits information about the found Web Apps to the Web App adapter 204. Then the Web App parser 203 runs the Web App. Optionally, when the operating system does not find a suitable Web App among the registered Web Apps, the operating system may transmit the Intent to the Web App adapter 204. In this case, the Web App adapter 204 can search for a suitable Web App on the network through the network interface unit 202. When a suitable Web App is found on the network, the user may be prompted through the user interaction interface unit 201 whether to choose to use the found Web App. When the user chooses to use the found Web App, the Web App parser 203 can run the found Web App. For example, if the user wants to open an audio file in rm format, but there is no local player that supports this format. At this time, find a Web App that supports the file format through the Web App manager, and the user can choose to use the Web App to open the rm file.

The following describes the situation for specific types of Web Apps. For example, a user starts a manufacturer's NativeApp camera (Camera) to take a photo and wants to immediately beautify or add annotations to the photo, but the camera app only has the function of taking pictures and previewing, and does not provide image processing functions, and the manufacturer or other manufacturers target the photo. Software Design develops specific types of Web Apps. In this case, the locally cached Web App can be retrieved through the operating system or the Web App can be found on the network through the Web App Manager. After finding the matching Web App, the user can choose to open and run the Web App. For example, Meitu Xiuxiu, Long Time No See, etc. can customize image processing functions for the preset Camera application of Samsung mobile phones, and bind the Web App with Samsung's Camera application. For another example, when the user uses the calendar preset in the mobile terminal, the calendar has only ordinary functions. If users want to query information about holidays, national holidays, game schedules, and today in history, the calendar application cannot meet these needs, and Web App can provide specific association binding for such needs. In this way, when the user views a certain day in the local calendar application, the corresponding Web App can be run through the Web App Manager to provide more information.

For the PUSH_MESSAGE type Web App, this Web App includes weather forecast, traffic information, road condition information, SNS information, news, etc. The Web App manager can manage the cached PUSH_MESSAGE type Web App to run in the background. This type of Web App can notify the system of the mobile terminal (such as calling the notification manager of the system) through the Web App adapter 204 to display the update information after synchronizing the server update message in the background.

FIG. 6 shows a diagram illustrating an architecture of a Web App manager installed in a mobile terminal using an Android operating system according to an exemplary embodiment of the present invention.

Referring to FIG. 6, the Web App adapter 204 registers the ID and configuration information of the Web App with the package manager of the mobile terminal, and the configuration information may include the types of data processed by the Web App and the types of services provided. On the other hand, the configuration information may include the information of the Native App targeted by the Web App (such as package name, class name, version number) and the service type provided by the Web App.

The Web App adapter 204 can respond to the request of the Web App and instruct the package manager to search for the corresponding Native App or Web App. When the package manager searches for the corresponding Native App, the activity manager of the mobile terminal runs the Native App found by the package manager, and returns the running result of the searched Native App to the requesting Web App through the Web App adapter 204 . When the package manager searches for the corresponding Web App according to the configuration information of the registered Web App, the package manager transmits the request of the Web App to the Web App adapter 204, so that the Web App adapter 204 can instruct the Web App parser 203 to run the corresponding Web App, and the Web App parser 203 returns the running result of the corresponding Web App to the requesting Web App.

Optionally, the Web App adapter 204 may instruct the Web App parser 203 to run the corresponding Web App in response to the request of the Native App run by the activity manager transmitted by the package manager. The WebApp parser 203 can return the running result of the corresponding Web App to the requesting Native App through the Web App adapter 204, the package manager and the activity manager. On the other hand, the Web App adapter 204 may instruct the network interface unit to search for a corresponding Web App in response to the request of the Native App run by the Activity Manager transmitted by the Package Manager. The Web App parser 203 runs the searched corresponding Web App, and returns the running result of the corresponding Web App to the requesting Native App through the Web App adapter 204, the package manager and the activity manager.

Optionally, the package manager determines the matching Web App according to the configuration information of the registered Web App with the request of the Native App run by the activity manager, and transmits information about the matched Web App to the Web App adapter 204, and the Web App adapter 204 Based on the information about the matching Web App, the Web App resolver 203 is instructed to run the matching Web App. The Web App parser 203 can return the running result of the matching Web App to the requesting Native App through the Web App adapter 204, the package manager and the activity manager.

FIG. 7 is a flowchart illustrating a Web App management method according to an exemplary embodiment of the present invention.

Referring to FIG. 7, in step S301, the Web App is registered with the operating system of the mobile terminal. For example, for the Android operating system, the Web App can be registered with the package manager of the mobile terminal. For general-purpose Web Apps, the ID and configuration information of the Web App can be registered with the operating system, and the configuration information includes the types of data processed by the Web App and the types of services provided. On the other hand, for a specific type of Web App, the ID and configuration information of the Web App can be registered with the operating system. The configuration information includes the information of the Native App targeted by the Web App (such as package name, class name, version number) and the Web The type of service provided by the app. Here, the registered Web App can be the Web App selected by the user through the user interaction interface unit 201, the default Web App of the mobile terminal, the Web App that has been run through the Web App parser 203, or the Web App that has been cached in the memory of the mobile terminal. App.

Next, in step S302, when running the Web App program, in response to the request of the running Web App, the mobile terminal can automatically run the corresponding Native App or Web App. Specifically, a corresponding Native App or Web App may be searched in response to a request of a running Web App. When the corresponding Native App is found, run the found Native App, and return the running result of the found Native App to the requesting Web App. On the other hand, when the corresponding Web App is searched according to the configuration information of the registered Web App, the request of the Web App is transmitted, the corresponding Web App is run in response to the transmitted request, and the operation result of the corresponding Web App is returned to the sending Requested Web App.

In addition, in step S303, when running the Native App, the corresponding Web App may be automatically run in response to the request of the running Native App. Specifically, in response to the request of the running Native App, the corresponding web application can be run, and the running result of the corresponding Web App can be returned to the requesting Native App. For example, the Web App that matches the request of the running Native App can be determined according to the configuration information of the registered Web App, and information about the matching Web App can be transmitted, so that the matching Web App can be run based on the information about the matching Web App. However, when the corresponding Web App is not found in the registered Web App, the request of the Native App can be transmitted, and the corresponding Web App can be searched based on the transmitted request, and the searched corresponding Web App can be executed.

FIG. 8 shows a block diagram of a Web App management device according to an exemplary embodiment of the present invention.

Referring to FIG. 8, the Web App management device may include a first module 801, a second module 802, and a third module 803. The first module 801 can register the Web App with the mobile terminal. When running the Web App, the second module 802 can automatically run the corresponding Native App or Web App in response to the request of the running Web App. When running the Native App, the third module 803 can automatically run the corresponding Web App in response to the request of the running Native App.

The second module responds to 802 and can search for the corresponding Native App or WebApp in response to the request of the Web App. When the corresponding Native App is found, run the found Native App, and return the running result of the found Native App to the requesting Web App. When the corresponding Web App is found according to the configuration information of the registered Web App, the request of the Web App is transmitted, the corresponding Web App is run in response to the transmitted request, and the operation result of the corresponding Web App is returned to the requesting Web App.

The third module 803 can run the corresponding Web App in response to the request of the running Native App, and then return the running result of the corresponding Web App to the requesting Native App. In addition, the third module can search for the corresponding Web App, run the corresponding Web App found, and then return the running result of the corresponding Web App to the Native App that sent the request.

In addition, the third module 803 can determine the Web App that matches the request of the running Native App according to the configuration information of the registered Web App, transmit the information about the matching Web App, and run the matching Web App based on the information about the matching Web App , and then return the running result of the matching Web App to the requesting Native App.

The Web App manager and the management method according to the exemplary embodiments of the present invention enable the seamless connection between the Web App and the Native App, so that users feel that the Web App and the Native App are the same. In addition, the Web App manager and management method according to the exemplary embodiments of the present invention can realize interaction with Native Apps for different types of Web Apps, so that users can truly realize instant search and use of Web Apps. On the other hand, the Web App manager and the management method according to the exemplary embodiments of the present invention enable the Web App to interact with the Native App through the Web App manager, improving the security of the interaction between the Web App and the Native App.

The above-mentioned Web App manager and management method according to the exemplary embodiments of the present invention may be implemented in hardware or firmware, or implemented as software or computer code or a combination thereof. In addition, the software or computer code may also be stored on a non-transitory recording medium (read only memory (ROM), random access memory (RAM), compact disk (CD)-ROM, magnetic tape, floppy disk, optical data storage device, and carrier wave (such as data transmission over the Internet)) or computer code downloaded over a network, where the computer code is originally stored on a remote recording medium, a computer-readable recording medium, or a non-transitory machine-readable medium and will be Such software, computer codes, software modules, software objects, instructions, applications, applications, apps, etc., or in programmable or dedicated hardware such as ASICs or FPGAs. As understood in the art: a computer, processor, microprocessor controller, or programmable hardware includes volatile and/or non-volatile memory and memory components (e.g., RAM, ROM, flash memory, etc.), wherein all The memory and memory elements described above may store or receive software or computer code which, when accessed and executed by a computer, processor or hardware, will implement the processing methods described herein. Furthermore, it will be appreciated that when a general purpose computer accesses code for implementing the processes illustrated herein, execution of the code transforms the general purpose computer into a special purpose computer for performing the processes illustrated herein. In addition, the program may be electronically transmitted through any medium such as a communication signal sent through a wired/wireless connection and its equivalent. The program and the computer-readable recording medium can also be distributed in network coupled computer systems so that the computer-readable codes are stored and executed in a distributed fashion.

While certain embodiments have been shown and described, it will be understood by those skilled in the art that modifications may be made to these embodiments without departing from the principles and spirit of the invention, the scope of which is defined by the claims and their equivalents limited.

Claims (28)

1. a web application manager, comprising:

User interactions interface unit, for carrying out alternately with user;

Network interface unit, for obtaining web application;

Web application resolver, for operational network application program;

Web application adapter, for to mobile terminal registered network application program, in response to the request of web application, indicating mobile terminal runs corresponding local application or web application, or in response to the request of local application, indication network application program resolver runs corresponding web application.

2. web application manager according to claim 1, wherein, web application resolver runs particular network application program with the backstage method of operation.

3. web application manager according to claim 1, wherein, pass through user interactions interface unit to the selection of the particular network application program that web application resolver runs in response to user, described particular network application program cache is in the storer of mobile terminal.

4. the web application manager according to claim 1 or 3, wherein, the web application that web application adapter is selected to mobile terminal registered user by user interactions interface unit, or to the web application of mobile terminal registration mobile terminal acquiescence, or to mobile terminal registration by the web application that web application resolver runs, or register the web application be cached in the storer of mobile terminal to mobile terminal.

5. web application manager according to claim 1, wherein, web application adapter is to the operating system registered network application program of mobile terminal.

6. web application manager according to claim 5, wherein, web application adapter to the ID of the operating system registered network application program of mobile terminal and configuration information, the data type that described configuration information comprises web application process, the COS provided.

7. web application manager according to claim 5, wherein, web application adapter to the ID of the operating system registered network application program of mobile terminal and configuration information, described configuration information comprise web application for the information of local application and the COS that provides of web application.

8. the web application manager according to claim 6 or 7, wherein, web application adapter is in response to the request of web application, and the operating system of indicating mobile terminal searches for corresponding local application or web application,

Wherein, when operating system searches corresponding local application, the local application that operating system searches, and the web application by web application adapter, the operation result of the local application searched being turned back to the request of sending

Wherein, when operating system searches corresponding web application according to the configuration information of the web application of registration, the request of web application is sent to web application adapter by operating system, thus web application adapter indication network application program resolver runs corresponding web application, and the operation result of corresponding web application is turned back to the web application of the request of sending by network application resolver.

9. the web application manager according to claim 6 or 7, wherein, web application adapter is in response to the request of the local application of the operating system of mobile terminal, and indication network application program resolver runs corresponding web application

Wherein, the operation result of corresponding web application is turned back to the local application of the request of sending by web application resolver by the operating system of web application adapter and mobile terminal.

10. the web application manager according to claim 6 or 7, wherein, web application adapter in response to the request of the local application of the operating system of mobile terminal, the corresponding web application of instruct network interface unit searches,

Wherein, the corresponding web application that web application resolver run search arrives, and the local application by the operating system of web application adapter and mobile terminal, the operation result of corresponding web application being turned back to the request of sending.

11. according to claim web application manager according to claim 7, wherein, the operating system of mobile terminal is determined and the web application that the request of the local application of operating system is mated according to the configuration information of the web application of registration, the information of the web application about coupling is sent to web application adapter, web application adapter is based on the information of the web application about coupling, the web application of indication network application program resolver Operating match

Wherein, the operation result of the web application of coupling is turned back to the local application of the request of sending by web application resolver by the operating system of web application adapter and mobile terminal.

12. web application managers according to claim 1, wherein, when receiving updating message with the particular network application program that the backstage method of operation is run by network interface unit by web application resolver, web application resolver is resolved updating message, and web application adapter controls mobile terminal display notice.

13. 1 kinds of web application management methods, comprise the following steps:

A () is to mobile terminal registered network application program;

B (), when operational network application program, in response to the request of the web application run, runs corresponding local application or web application;

C (), when running local application, in response to the request of the local application run, runs corresponding web application.

14. web application management methods according to claim 13, wherein, the web application of registration be user select web application, mobile terminal acquiescence web application, by the web application of the operating system of mobile terminal or the web application that has been cached in the storer of mobile terminal.

15. web application management methods according to claim 13, wherein, in step (a)., to the operating system registered network application program of mobile terminal.

16. web application management methods according to claim 15, wherein, in step (a)., to ID and the configuration information of the operating system registered network application program of mobile terminal, the data type that described configuration information comprises web application process, the COS provided.

17. web application management methods according to claim 15, wherein, in step (a)., to ID and the configuration information of the operating system registered network application program of mobile terminal, described configuration information comprise web application for the information of local application and the COS that provides of web application.

18. web application management methods according to claim 16 or 17, wherein, in step (b), in response to the request of web application, search for corresponding local application or web application,

Wherein, when searching corresponding local application, the local application that run search arrives, and the web application operation result of the local application searched being turned back to the request of sending,

Wherein, when the configuration information of the web application according to registration searches corresponding web application, transmit the request of web application, run corresponding web application in response to the request transmitted, and the operation result of corresponding web application is turned back to the web application of the request of sending.

19. web application management methods according to claim 16 or 17, wherein, in step (c), in response to the request of the local application run, run corresponding web application,

Wherein, the operation result of corresponding web application is turned back to the local application of the request of sending.

20. web application management methods according to claim 16 or 17, wherein, in step (c): search for corresponding web application, and the corresponding web application that run search arrives,

Wherein, the operation result of corresponding web application is turned back to the local application of the request of sending.

21. web application management methods according to claim 17, wherein, in step (c), determine and the web application that the request of the local application run is mated according to the configuration information of the web application of registration, transmit the information of the web application about coupling, based on the web application of the information Operating match of the web application about coupling

Wherein, the operation result of the web application of coupling is turned back to the local application of the request of sending.

22. 1 kinds of web application management devices, comprising:

First module, to mobile terminal registered network application program;

Second module, when operational network application program, in response to the request of the web application run, automatically runs corresponding local application or web application;

3rd module, when running local application, in response to the request of the local application run, automatically runs corresponding web application.

23. web application management devices according to claim 22, wherein, the second module responds, in the request of web application, searches for corresponding local application or web application,

Wherein, when searching corresponding local application, the local application that run search arrives, and the web application operation result of the local application searched being turned back to the request of sending,

Wherein, when the configuration information of the web application according to registration searches corresponding web application, transmit the request of web application, run corresponding web application in response to the request transmitted, and the operation result of corresponding web application is turned back to the web application of the request of sending.

24. web application management devices according to claim 22, wherein, the 3rd module responds, in the request of the local application run, runs corresponding web application,

Wherein, the operation result of corresponding web application is turned back to the local application of the request of sending.

25. web application management devices according to claim 22, wherein, the corresponding web application of the 3rd block search, and the corresponding web application that run search arrives,

Wherein, the operation result of corresponding web application is turned back to the local application of the request of sending.

26. web application management devices according to claim 22, wherein, 3rd module is determined and the web application that the request of the local application run is mated according to the configuration information of the web application of registration, transmit the information of the web application about coupling, based on the web application of the information Operating match of the web application about coupling

Wherein, the operation result of the web application of coupling is turned back to the local application of the request of sending.

27. 1 kinds of mobile terminals comprising the web application manager as described in any one claim in claim 1 to claim 12.

28. 1 kinds of mobile terminals comprising the web application management devices as described in any one claim in claim 22 to claim 26.