WO2010017692A1

WO2010017692A1 - Terminal, system and method for supporting mobile internet application

Info

Publication number: WO2010017692A1
Application number: PCT/CN2009/000922
Authority: WO
Inventors: 朱春梅; 张鑫; 侯睿; 程宝平; 侯清富; 于川
Original assignee: 中国移动通信集团公司
Priority date: 2008-08-12
Filing date: 2009-08-12
Publication date: 2010-02-18
Also published as: CN101651633B; CN101651633A

Abstract

A terminal, system and method for supporting mobile Internet application are disclosed. The terminal comprises: an application operating engine which manages comprehensively the mobile Internet application and an internal server which provides service and/or expanding ability support for the application operating engine; the application operating engine and the internal server operate respectively in two independent threads and communicate with each other. The system includes the terminal and external service server. The method includes the following steps: sending the invocation of the service or expanding ability to the internal server through the application operating engine when using the service or expanding ability in mobile Internet application; the internal server invokes the service or expanding ability and returns to the mobile Internet application. The proposed terminal, system and method, which support mobile Internet application to enable extension across platform, support the provisions of local mobile communication ability, the third party service and network side ability to the mobile Internet application.

Description

Terminal, system and method for supporting mobile internet application

The present invention relates to the field of mobile internet applications, and in particular, to a terminal, system and method for supporting a mobile internet application. Background technique

The closest prior art to the present invention is WRT (WebRunTime) technology, which implements a variety of mobile widgets. Widgets are WEB pages and are usually designed for a specific purpose; mobile Widgets are Widgets that run on mobile devices. Through the development of WRT-based technology, mobile terminals can support the mobile Internet application runtime environment, support the parsing of extended tags, and manage the operation of mobile Widget applications. WRT technology extends the JavaScript core within the mobile terminal (JavaScript is a standard Internet technology, also a description language), enabling the mobile terminal to support the analysis of mobile extension tags, while implementing Widget management. The function. WRT technology implements JavaScript extensions by mapping extension object calls between the JavaScript core and the native program.

At present, although WRT technology implements support for mobile Internet applications, when the extension is implemented, the call of the extended object is directly mapped between the JavaScript core and the native capability, and the extension mode is single, and the third-party service cannot be extended to the mobile Internet application. It also does not support extending network-side capabilities to mobile Internet applications. Summary of the invention

An object of the embodiments of the present invention is to provide a terminal, system and method for supporting a mobile internet application in order to extend more services and capabilities to a mobile internet application, aiming at a single defect of a method for supporting an Internet application in the prior art. .

Embodiments of the present invention provide a terminal supporting a mobile internet application, including a mobile internet connection An application running engine that is fully managed by the web application; an internal server that provides service and/or extended capability support for the application running engine; the application running engine and the internal server respectively run in two separate threads and communicate.

The embodiment of the present invention provides a system for supporting a mobile Internet application, including the terminal in the foregoing technical solution, and a network side service server external to the terminal, where the network side service server pushes the network side capability to the internal server of the terminal.

The embodiment of the present invention further provides a method for supporting a mobile internet application. When a service or an extension capability is used in a mobile internet application, a call to a service and/or an extension capability is sent to an internal server by an application execution engine; Service and/or extension capabilities and return to mobile internet applications.

Embodiments of the present invention provide a cross-platform terminal, system, and method for supporting mobile Internet application implementation extension, which breaks a single extension manner in the prior art (that is, an extension object is called when the extension object is in the JavaScript core and the local machine. Instead of mapping directly between capabilities, it provides a more flexible way to scale. The solution for supporting the mobile internet application provided by the embodiment of the present invention can not only realize the extension of the local mobile communication capability, but also realize the extension of the local capability by operating the internal server that can be run in a separate thread. One way; and can support the expansion of third-party services to mobile Internet applications, and support the extension of network-side capabilities to mobile Internet applications. DRAWINGS

1 is a system architecture diagram of a terminal supporting a mobile internet application in Embodiment 1 of the present invention; FIG. 2 is a schematic diagram of an interface between related modules in a terminal supporting a mobile internet application according to Embodiment 1 of the present invention;

FIG. 3 is a schematic flowchart of a method for expanding a communication capability according to an embodiment of the present invention; FIG. 4 is a flowchart of a method for extending a communication capability by using a telephone function in FIG. 3; FIG. FIG. 6 is a flowchart of a method for supporting a mobile Internet application to implement a second native capability extension according to Embodiment 2 of the present invention (taking a telephone function as an example); 7 is a flowchart of a method for supporting a third-party service capability extension of a mobile internet application according to Embodiment 3 of the present invention (taking a search service as an example);

FIG. 8 is a flowchart of a method for supporting a mobile internet application to implement network side capability expansion according to Embodiment 4 of the present invention. detailed description

The specific embodiments of the present invention are described in detail below with reference to the accompanying drawings.

1 is a system architecture diagram of a terminal supporting a mobile internet application according to Embodiment 1 of the present invention. As shown in FIG. 1, the mobile terminal 1 supporting the extension of the mobile internet application mainly includes an application running engine 2 and an internal server 3. Application Run Engine 2 is the management container for mobile Internet applications and is responsible for the overall management of mobile Internet applications, including registration, loading, running, and more. The internal server 3 is a container for third-party services, native services, and network-side capability integration deployment, providing support for application runtime engines and service extensions. Application Runtime Engine 2 runs on internal server 3 in two separate threads, communicating in a standard communication protocol such as the HTTP protocol.

The application running engine 2 mainly includes an application management module 4, a capability analysis module 5, a traditional capability module 6, a native capability module 7, and a capability agent module 8. The application management module 4 is responsible for managing the mobile internet application, including application resource allocation, security control, and communication between applications. At the same time, this module is responsible for parsing language level calls in the mobile internet application into an object subtree. The capability parsing module 5 maintains a complete object tree (DOM Tree) supported by a system, and distributes the access mapping of the mobile Internet application to the underlying capabilities to different capability modules (for example, the traditional capability module and the native capability module). The traditional capability module 6 is a support for the traditional Internet capability. The native capability module 7 is a support for the extension of the local mobile communication capability, and the capability proxy module 8 is responsible for cooperating with the internal server to expand the service and network side capabilities in the internal server. Give mobile internet applications.

The interface between the above modules is shown in Figure 2. Where IF1 is a script supported by the system; IF2 is a property or method of the DOM object; IF3 is a property or method of the native object class; IF4 is a call to the specific capabilities of the native system; IF5 is a method or property of the capability proxy class; IF6 Is a standard communication protocol message, such as an HTTP message, packaged according to internal transport rules. The internal server 3 provides extended support for the application running engine 2 in a service manner, including a service container 9 and a network side capability module 12, which in turn may include a third party service module 10 and a local service module 11, and then a third party service , native packaging services and network side capabilities are available for mobile internet applications. Internal server 3 deploys and manages services in plug-in mode. The system defines a common service plug-in management interface, and third-party services and native services are encapsulated according to standard plug-in interfaces. Service container 9 uses the established plug-in interface management service to achieve flexible and rapid deployment of services.

The application runtime engine 2 and the internal server 3 shield the difference between the underlying platforms and provide a unified application programming interface for the upper mobile Internet applications on different platforms. The system has two extension methods through the capability analysis module 5, the capability proxy module 8, and the internal server 3. The first method is to bind the upper layer call directly to the local extension capability. The specific interaction process is shown in Figure 3. . Extending with the first method requires the ability to be extended to be packaged in the «Several Capabilities Module. In Figure 4, the flow of the first extension method is illustrated by a telephone function, in which the telephone function is encapsulated in the native capability module. The specific process is as follows: The mobile Internet Widget application uses a phone function to initiate a phone call in a JavaScript program; the application management module parses the Widget application into an object subtree, and passes the call to the phone DOM object to the capability resolution module; the capability resolution module will The DOM Call object maps to the native class in the native capability module, and the native capability module invokes the underlying operating system to initiate a phone call.

In addition to the above method, the second extension method is used in the embodiment of the present invention, and the extended capability is deployed in an internal server in a service manner, and then provided to the capability proxy module in a message manner, and then provided to the upper layer. application. When the second method is used for capacity expansion, the interaction process between modules is shown in Figure 5. The specific process is as follows: The mobile Internet application uses the extension capability; the application management module parses it into a call to extend the DOM object; the capability resolution module maps the DOM object capability through the service extension to the capability proxy module; the capability proxy module will extend the capability The call is encapsulated as an asynchronous HTTP message sent to the internal server; the internal server parses the call message and evokes the response to the service, returning the result.

The following is a detailed description of specific embodiments: FIG. 6 shows Embodiment 2 of the present invention, wherein a method for supporting a mobile Internet application to implement native capability extension is illustrated by using a telephone function as an example:

Step S102: The mobile internet Widget application initiates a telephone call by using a telephone function in a JavaScript program;

Step S104: The application management module parses the Widget application into an object subtree, and transmits a call to the phone DOM object (DOM Call) to the capability parsing module;

Step S106: The capability parsing module maps the DOM Call object to a proxy class in the capability proxy module.

Step S108: The capability proxy module encapsulates the call to the proxy class into an HTTP message and sends it to the internal server.

Step S110: The internal server parses the HTTP message to obtain the parameter information invoked by the local telephone, and transmits the parameter information to the encapsulated local telephone service;

Step S112: the local telephone service evokes the result of the telephone service operation to the internal server; Step S114: The internal server encapsulates the operation result to the capability agent module;

Step S116: The capability proxy module sends the operation result to the capability parsing module.

Step S118: The capability parsing module sends the call object operation result to the application management module. Step S120: The application management module returns the result of creating the call to the mobile internet application.

The method described in the above embodiment 2 realizes the extension of the native capability by a method different from the prior art (packaging the capability in the native capability module) by adding several service modules in the internal server.

For extensions to third-party services, the system deploys third-party services in an internal server in standard plug-in mode. FIG. 7 shows Embodiment 3 of the present invention, wherein a search service is taken as an example to describe a method for supporting a mobile Internet application to implement third-party service capability extension:

Step S202: The mobile internet Widget application calls a "local query" function in the JavaScript program;

Step S204: The application management module parses the Widget application into an object subtree, and passes the call of the query function DOM object to the capability parsing module; Step S206: The capability parsing module maps the DOM query object to a proxy class in the capability proxy module.

Step S208: The capability proxy module encapsulates the call to the proxy class into an HTTP message and sends it to the internal server.

Step S210: The internal server receives the message invoked by the local query and distributes it to a third-party service plug-in that implements the local query function.

Step S212: The third-party service plug-in processes the result and returns the result to the internal server. Step S214: The internal server encapsulates the query result and sends the result to the capability agent module.

Step S216: The capability proxy module sends the query result to the capability parsing module.

Step S218: The capability parsing module sends the query result of the extended object to the application management module. Step S220: The application management module returns the query result to the mobile internet application.

The method described in Embodiment 3 above implements the extension of the third-party service capability by adding a third-party service module in the internal server.

For the extension of the network side capability, the service server is required to push the network side capability to the internal server of the mobile terminal, and the internal server in turn responds to the request of the application running engine for the network capability. The specific interaction process is shown in Embodiment 4 of Figure 8. The method of "acquiring free bandwidth" is used as an example to support the mobile Internet application to implement network side service capability extension:

Step S302: The mobile internet Widget application calls the "get idle bandwidth" function in the JavaScript program;

Step S304: The application management module parses the Widget application into an object subtree, and passes the call for acquiring the idle bandwidth function DOM object to the capability parsing module;

Step S306: The capability parsing module maps the DOM query idle bandwidth to the proxy class in the capability proxy module.

Step S308: The capability proxy module encapsulates the call of the proxy class into an HTTP message and sends the call to the internal server.

Step S310: The internal server sends a request to the external service server after receiving the message called for the idle bandwidth. Step S312: The external service server pushes the network side capability to the internal server of the mobile terminal;

Step S314: The internal server encapsulates the idle broadband information and sends it to the capability proxy module. Step S316: The capability proxy module returns the idle bandwidth information to the capability parsing module. Step S318: The capability parsing module sends the idle bandwidth result information of the extended object to the Application management module;

Step S320: The application management module returns the idle bandwidth size to the mobile internet application.

The method described in the foregoing embodiment 4 implements the extension of the network side capability by using the network side capability module in the internal server and the interaction between the network side capability module and the external service server. A single extension mode provides a more flexible extension mechanism. It not only expands the native mobile communication capabilities for mobile Internet applications, but also easily extends third-party service capabilities and network-side service capabilities.

The above disclosure is only a few specific embodiments of the present invention, but the present invention is not limited thereto, and any changes that can be conceived by those skilled in the art should fall within the protection scope of the present invention.

Claims

Rights request

A terminal for supporting a mobile internet application, comprising:

An application running engine that comprehensively manages mobile Internet applications;

An internal server that provides service and/or extension capability support for the application execution engine; the application execution engine and the internal server respectively run in two separate threads and communicate.

2. The terminal according to claim 1, further comprising:

A capability proxy module, configured to cooperate with the internal server to extend services and/or capabilities in the internal server to a mobile internet application.

The terminal according to claim 2, wherein the capability agent module is located inside the application execution engine, and the mobile internet application extends the service and/or capability in the internal server through the capability agent module.

The terminal according to claim 2, wherein the capability proxy module is located between the application execution engine and the internal server.

The terminal according to any one of claims 1 to 4, wherein the internal server comprises:

Service container, used to support extensions to native and/or third-party services; and / or,

The network side capability module is configured to interact with a network side service server outside the terminal to support network side capability extension.

The terminal according to claim 5, wherein the application running engine specifically includes:

An application management module for managing mobile internet applications and parsing language level calls in mobile internet applications;

The capability parsing module is configured to maintain the parsing result of the application management module, and distribute the access mapping of the mobile internet application to the underlying capability to different capability modules.

The terminal according to claim 6, wherein the capability proxy modules are respectively associated with The capability resolution module is connected to an internal server.

The terminal according to claim 7, wherein a method or an attribute interface of the capability proxy class is adopted between the capability proxy module and the capability analysis module.

9. The terminal according to claim 5, wherein the application running engine communicates with the internal server by using a standard communication protocol message packaged according to an internal transmission rule.

10. The terminal of claim 9, wherein the standard communication protocol is an HTTP protocol.

The terminal according to claim 6, wherein the application running engine further comprises a native capability module for providing support for the extension of the local mobile communication capability.

12. A system for supporting a mobile internet application, comprising the terminal of any one of claims 1 to 11.

The system according to claim 12, further comprising a network side service server external to the terminal, wherein the network side service server pushes the network side capability to an internal server of the terminal.

14. A method for supporting a mobile internet application, the method comprising:

When a service and/or extension capability is used in a mobile internet application, a call to the service and/or extension capability is sent to the internal server by the application runtime engine;

The internal server invokes the service and/or extension capabilities and returns to the mobile internet application.

The method according to claim 14, wherein the internal server invokes the service and/or extension capability, and returns to the mobile internet application specifically:

Deploy the extended capabilities as a service in an internal server;

And provided to the capability agent module by means of a message;

It is then provided to mobile internet applications.

The method according to claim 14 or 15, further comprising: when the native extension capability is used in the mobile internet application, mapping the local extension capability call to the local machine by the application execution engine Capability module The native capability module provides native extension capabilities of its own internal package to the application runtime engine for use in mobile Internet applications.

The method according to claim 14 or 15, wherein the invoking the service and/or the extension capability by the internal server specifically comprises:

Calling native services; and / or

Third party services; and / or

Network side expansion capability.

The method according to claim 17, wherein the local service is a phone function service; the third party service is a search query service; and the network side extension capability is an idle bandwidth.