CN101964742B - Method, system and device for using network open ability - Google Patents

Abstract

The embodiment of the invention discloses a method, a system and a device for using network open ability. The method comprises the following steps of: packaging and developing the open ability of an open ability provider to generate a Widget file which comprises a specific identifier, and downloading the generated Widget file by a Widget client; then receiving a call request for the open ability of the open ability provider which is sent by the Widget client, wherein the call request is generated by the Widget client which analyzes the construction of the Widget file; and the call request carries the specific identifier; acquiring corresponding data information or services from the open ability provider according to the call request which carries the specific identifier; and performing adaptor conversion on the received data information or services, and returning the converted data information or services to the Widget client. In the embodiment of the invention, Widget users can use a plurality of open abilities without knowing the service logic of the open ability provider.

Description

Method, system and device for using network open capability

technical field

The present invention relates to the field of network technologies, and more specifically, to a method, system and device for using network open capabilities.

Background technique

Widget is a small application program, mainly used as the front end of Web 2.0 service or Internet content, which can be called widget or widget. Because it can display and update local or remote data, Web designers and developers can use Widgets to create the most popular Internet experiences that users can access with a single click from the S60's desktop or application menu. Usually, during the use of the Widget, the client device downloads and installs the Widget file that has been packaged before it can be used.

Since Widget is a kind of Web program, the technologies involved in Widget are basically related technologies in the Web field, such as: HTML (Hypertext Markup Language, Hypertext Markup Language), CSS (Cascading Style Sheets, Cascading Style Sheets), JavaScript, XML (Extensible Markup Language, Extensible Markup Language), etc. Among them, HTML is used for page layout, CSS is used to control the page style, JavaScript is used to provide dynamic behavior for web pages, etc. Therefore, when developing a Widget, it is usually necessary to create the following files: HTML file, CSS file, JavaScript file, XML configuration file, image resource file, etc. After all the above files are created, they are packaged into a compressed file, such as ZIP format, and then change the compressed file into a specific file type recognized by the Widget, such as *.wgt, *.widget format files, and finally publish it for users to download and use.

In the existing Widget architecture, the Widget client generally runs the Widget engine and is responsible for parsing and executing Widget application files, and the Widget server acts on behalf of the client to obtain data information or services from the resources of the open capability provider. The open capability provider here includes the open capability of the Internet, such as Google, Yahoo! Provide map, search and other service capabilities; open capabilities of telecommunication networks, such as SMS, calling, location and other services provided by China Mobile and Vodafone; open capabilities of home networks, such as monitoring and monitoring provided by cameras and smoke detectors in the home and other capabilities; the open capabilities of industry networks, such as the billing and settlement capabilities of the banking system and the e-learning capabilities of the education system; and the platform integration capabilities of existing open capability providers, such as Mashup platforms and telecom value-added service platforms.

With the increasing openness of the Internet and telecommunication networks, the number and types of OpenAPI (OpenApplication Interface, open application programming interface) are also increasing, which requires the Widget system to provide a wide variety of open capabilities for a large number The open business on the other side has a strong ability to combine, which is convenient to solve the dynamic switching of data sources and ensure the availability of services. The existing Widget system encapsulates the provider of the open capability, such as the Mashup system, which encapsulates the open capability of the network to a certain extent. However, during the process of implementing the present invention, the inventor found that the existing technology has at least the following disadvantages: for Widget users In most cases, it is still necessary to understand the business logic of the open capability provider in order to better use the various services provided by the open capability provider, which limits the use of various open capabilities to a certain extent. Use effectively.

Contents of the invention

In view of this, the embodiments of the present invention provide a method, system and device for using network open capabilities, so that Widget users can use many open capabilities without knowing the business logic of the open capability provider.

The embodiment of the present invention is realized like this:

An embodiment of the present invention provides a method for using a network open capability, including:

Receive the invocation request for the open capability of the open capability provider sent by the Widget client, and the invocation request encapsulates the downloaded open capability of the open capability provider by the Widget client and develops and generates a Widget including a specific identifier The file is generated by parsing and constructing, and the calling request carries the specific identifier;

Obtain corresponding data information or services from the open capability provider according to the call request carrying the specific identifier;

Adapting and transforming the received data information or service and returning it to the Widget client.

Perform protocol conversion and/or data conversion on the received data information or service.

An embodiment of the present invention provides a system for using network open capabilities, including: a Widget server, a Widget client, and an open capability provider, wherein,

The Widget server is used to encapsulate the open capabilities of the open capability provider and develop and generate a Widget file including a specific identification for the Widget client to download; it specifically includes:

A receiving unit, configured to receive an invocation request for the open capability of the open capability provider sent by the Widget client, the invocation request is generated by the Widget client by analyzing and constructing the Widget file, and in the invocation request carry said specific identification;

An obtaining unit, configured to obtain corresponding data information or services from the open capability provider according to the call request carrying the specific identifier;

an adaptation conversion unit, configured to perform adaptation conversion on the data information or service;

a sending unit, configured to send the data information or service after adaptation and conversion to the Widget client;

The Widget client is configured to download the Widget file including the specific identifier, parse and construct the Widget file to generate an invocation request for the open capability of the open capability provider, and the invocation request carries the specific identifier.

The embodiment of the present invention also provides a Widget server. The Widget server encapsulates and develops the open capability of the open capability provider to generate a Widget file including a specific identifier for the Widget client to download, including:

A receiving unit, configured to receive an invocation request for the open capability of the open capability provider sent by the Widget client, the invocation request is generated by the Widget client by analyzing and constructing the Widget file, and in the invocation request carry said specific identification;

An obtaining unit, configured to obtain corresponding data information or services from the open capability provider according to the call request carrying the specific identifier;

an adaptation conversion unit, configured to perform adaptation conversion on the data information or service;

A sending unit, configured to send the data information or service after adaptation and conversion to the Widget client.

In the embodiment of the present invention, the Widget server encapsulates and develops the open capability of the open capability provider to generate a Widget file including a specific identifier. When the Widget client downloads the file and uses it, the Widget client only needs to parse the Widget file, and By sending the invocation request including the specific identifier to the Widget server, the Widget server can request corresponding data or services from the open capability provider for the Widget client according to the invocation request with the specific identifier. The technical solution provided by the embodiment of the present invention encapsulates the open capabilities of the open capability provider, so that Widget users can use many open capabilities without knowing the business logic of the open capability provider.

Description of drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following will briefly introduce the accompanying drawings that need to be used in the description of the embodiments. Obviously, the accompanying drawings in the following description are only of the present invention. For some embodiments, those of ordinary skill in the art can also obtain other drawings based on these drawings without paying creative efforts.

FIG. 1 is a flowchart of a method for using a network openness capability according to an embodiment of the present invention;

FIG. 2 is a flow chart of another method for using a network openness capability involved in an embodiment of the present invention;

FIG. 3 is a schematic structural diagram of a system for using a network open capability according to an embodiment of the present invention;

FIG. 4 is a schematic structural diagram of a Widget server involved in an embodiment of the present invention;

FIG. 5 is a schematic structural diagram of a Widget client involved in an embodiment of the present invention.

Detailed ways

The following will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only some, not all, embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the protection scope of the present invention.

An embodiment of the present invention provides a method for using a network open capability. The method includes: after encapsulating the open capability provider's open capability and developing and generating a Widget file including a specific identifier, and after the Widget client downloads it, specifically use The method is shown in Figure 1, including:

S101: Receive the invocation request for the open capability of the open capability provider sent by the Widget client, the invocation request is packaged by the Widget client for the open capability of the open capability provider downloaded and developed to include a specific identifier The Widget file is parsed and constructed, and the call request carries the specific identifier;

S102: Parsing the call request to obtain call parameters including the specific identifier;

S103: Obtain corresponding data information or services from the corresponding open capability provider according to the invocation parameters; in this embodiment, this step can be understood as: sending data information or service requests to the corresponding open capability provider according to the invocation parameters Message: receiving the data information or service sent by the corresponding open capability provider.

S104: Perform adaptation transformation on the received data information or service and return to the Widget client.

In the method for using the network open capability provided by the embodiment of the present invention, the Widget server encapsulates and develops the open capability of the open capability provider to generate a Widget file including a specific identifier. When the Widget client downloads the file and uses it, the Widget The client only needs to parse the Widget file, and send a call request including the specific identifier to the Widget server, so that the Widget server can request corresponding data or services from the open capability provider for the Widget client according to the call request. The technical solution provided by the embodiment of the present invention encapsulates the open capabilities of the open capability provider, so that Widget users can use many open capabilities without knowing the business logic of the open capability provider.

The embodiment of the present invention provides another method for using the network open capability. Before using the open capability, the Widget server first encapsulates the open capability of the open capability provider, and develops and generates the encapsulated open capability provider, including A Widget file with a specific logo is used for publishing to the Widget client.

It should be noted that before the Widget server encapsulates the open capabilities of the open capability provider, it first needs to obtain the open capability information, which can be obtained in two ways: first, the Widget server actively captures In the second way, the open capability provider actively registers on the Widget server. In the subsequent operation process, the same packaging development method can be used for the open capabilities obtained in the two ways.

For example, the following methods can be used to package and develop the open capabilities of the open capability provider:

Encapsulation of the URL/access code method, which is mainly used in open capability providers such as Mashup and telecom value-added services. For example: during a draft competition, the service provider has developed a short message value-added service on the existing mobile value-added service platform, which is used by TV viewers to send mobile phone text messages to support their favorite contestants. And if the service provider opens up this business capability at this time, allowing Widget developers to carry out secondary development on this basis, so that the value-added service can provide a unique access code to the outside world, and provide the access code to the Widget client, so that when running this service, the telecom value-added service platform can identify the corresponding service logic through the access code. After the above package development process, the Widget file describing the voting business includes the following code:

Encapsulation in the form of tags, which is mainly applied to the open capability provider that the Widget server actively captures on the network or actively registers to the Widget server. This method is used to package and develop the services of the open capability provider. Usually, after packaging, the Widget server provides some extended HTML tags to the developer, and the developer can develop HTML pages based on these HTML tags.

The JavaScript object method, the application scope of this method is basically the same as that of the label method, and it is also applied to the open capability provider that the Widget server actively captures the open capability on the network or actively registers to the Widget server. This method is used to encapsulate and develop the services of the open capability provider. Usually, after the encapsulation, the Widget server provides some extended JavaScript objects to the developer, and the developer can develop based on these JavaScript objects.

It should be noted that, the method for using network open capabilities provided by the embodiments of the present invention may not consider whether these open capability providers are in the same network when encapsulating the open capabilities of open capability providers. For example: the interfaces, logic and data formats involved in the message service capabilities provided by different operators under the telecommunication network may be different, but when encapsulating the open capabilities of these open capability providers, as long as different open capability providers Different specific identifications are provided, while unified simplified encapsulation and unified adaptation management are performed externally. An example of the above situation is as follows: Assuming that the open capabilities of telecom operator 1, telecom operator 2, Internet service provider, and data TV under the home network are uniformly encapsulated, then during the encapsulation process, it is necessary to provide The party sets a specific logo, and here, it is encapsulated in the form of a JavaScript object, which can be expressed as: Message(Tosomebody, content). The business logic after encapsulation can be expressed as follows:

if(Tosomebody.mobilePhone1=online)

Message business logic of telecom operator 1

elseif(Tosomebody.mobilePhone2=online)

Message business logic of telecom operator 2

elseif(Tosomebody.IM=online)

Internet service provider's message business logic

elseif(Tosomebody.TV=online)

Message business logic of digital TV under home network

After the above packaging and development, the relevant files are packaged into a compressed file, and then the compressed file is changed to a specific file type that Widget can recognize, such as *.wgt, *.widget format files, and finally released with For users to download and use.

After encapsulating the open capability of the open capability provider and generating a Widget file including a specific identifier, perform the steps shown in Figure 2:

Step 201: the Widget client downloads the packaged and developed Widget file to the local to perform Widget-related business.

In step 201, the client downloads the packaged and developed Widget file from the network, runs the file, and enters step 202.

Step 202: The Widget client parses and constructs the downloaded Widget file to generate an invocation request for the open capability of the open capability provider.

In step 202, according to the above-mentioned three packaging development methods, the Widget client will also encounter different situations when parsing the Widget file:

If the URL/access code method is used in the packaging development stage, when the Widget file is parsed by the Widget client, the client will encounter the URL/access code involved in the packaging development process during the parsing process. At this time, the Widget client needs to add the URL/access code to the invocation request for the open capability of the open capability provider to be constructed, so as to indicate which open capability the user needs to invoke. At the same time, the constructed call request for the open capability also includes relevant parameters such as identification information of the Widget service, which are used to indicate what kind of data or service the user needs to obtain from the open capability provider. For further details, refer to Table 1 for specific parameters included in the invocation request of the open capability.

Table 1

In addition, it should be noted that, usually, the open capability invocation request is an invocation request of the unified capability encapsulation interface, and the request is generally based on HTTP.

Step 203: the Widget client sends an invocation request for the open capability to the Widget server.

Step 204: The Widget server parses the invocation request of the open capability and obtains invocation parameters therein.

In step 204, after receiving the open capability invocation request sent by the Widget client, the Widget server parses the request to obtain relevant parameters included in the request, such as various parameters shown in Table 1.

Step 205: The Widget server sends a data or service request message to the corresponding open capability provider according to the obtained calling parameters.

In step 205, after acquiring the call parameters, the Widget server may determine which open capability the Widget client needs to call according to the parameter content contained in the call parameters, and select an appropriate open capability provider for the Widget client. This can be further specified as follows:

Since there may be many open capability providers registered on the Widget server, the Widget server can know which open capability the Widget client needs to call according to the content included in the call parameter, so that the Widget server can choose from many open capability providers An open capability provider that meets the requirements for open capability invocation.

Preferably, the Widget server can also monitor the open capability providers registered on it in real time, so as to obtain the running status of each open capability provider, and select a suitable open capability provider. As in the previous example, if in telecom operator 1, telecom operator 2, Internet service provider and home network, if the monitoring results show that telecom operator 1 is in good condition, then select telecom operator 1 for data or service Obtain.

Afterwards, the Widget server determines what kind of data or service the Widget client wants to obtain according to the Widget service identification information included in the call parameter, and the Widget server needs to send a specific request message including the message to the selected open capability provider .

Step 206: The open capability provider provides corresponding data or services to the Widget server according to the request message sent by the Widget server.

Step 207: The Widget server receives the data or service provided by the open capability provider, and adapts and transforms the data.

In step 207, since the communication protocols and data frame formats adopted by the Widget client and the open capability provider may be different, the data or services obtained from the open capability provider may not be directly used by the Widget , and the Widget server needs to convert these data or services accordingly so that they can be normally received and displayed by the Widget client.

In addition, if the Widget client also specifies the expected return result format in the call parameter, the Widget server also needs to convert the received data or service according to the format specified in advance.

Step 208: the Widget server sends the data or service to be adapted and transformed to the Widget terminal.

Since the data sent by the Widget server to the Widget terminal has been adapted and transformed, and has met the standards of the Widget client, the Widget client can directly use and display the result after receiving the data or service.

In the method for using the network open capability provided by the embodiment of the present invention, the Widget server encapsulates and develops the open capability of the open capability provider to generate a Widget file including a specific identifier. When the Widget client downloads the file and uses it, the Widget The client only needs to parse out the specific identifier contained therein, and send a calling request including the specific identifier to the Widget server, so that the Widget server can request corresponding data or services from the open capability provider for the Widget client according to the calling request. The technical solution provided by the embodiment of the present invention encapsulates the open capabilities of the open capability provider, so that Widget users can use many open capabilities without knowing the business logic of the open capability provider.

Correspondingly, the embodiment of the present invention also provides a network open capability utilization system, the system structure is shown in Figure 3, including: Widget server 301, Widget client 302 and open capability provider 303, wherein,

The Widget server 301 is configured to package the open capabilities of the open capability provider 303 and develop and generate a Widget file including a specific identifier.

The Widget client 302 is configured to download the Widget file including a specific identifier from the Widget server 301; analyze and construct the Widget file to generate a call request for the open capability of the open capability provider 303, and the call request carries the the specific identifier, and send the calling request to the Widget server 301.

In this embodiment, the Widget server 301 is further configured to receive an invocation request sent by the Widget client 302 to the open capability provider 303 to open the capability.

In this embodiment, the Widget server 301 is further configured to parse the invocation request to obtain invocation parameters including the specific identifier, and obtain corresponding data information or services from the corresponding open capability provider 303 according to the invocation parameters;

In this embodiment, the Widget server 301 is further configured to adapt and transform the received data information or service and return it to the Widget client 302 .

In the system for using the network open capability provided by the embodiment of the present invention, the Widget server encapsulates and develops the open capability of the open capability provider to generate a Widget file including a specific identifier. When the Widget client downloads the file and uses it, the Widget The client only needs to parse the Widget file, and send a call request including the specific identifier to the Widget server, so that the Widget server can request corresponding data or services from the open capability provider for the Widget client according to the call request. The technical solution provided by the embodiment of the present invention encapsulates the open capabilities of the open capability provider, so that Widget users can use many open capabilities without knowing the business logic of the open capability provider.

Furthermore, the embodiment of the present invention also provides a Widget server, the specific structure of which is shown in Figure 4, mainly including:

An encapsulation development unit 401, configured to encapsulate the open capabilities of the open capability provider and develop and generate a Widget file including a specific identifier;

The receiving unit 402 is configured to receive an invocation request for the open capability of the open capability provider sent by the Widget client, the invocation request is generated by the Widget client by parsing and constructing the Widget file, and the invocation request carries said specific identification;

An obtaining unit 403, configured to obtain corresponding data information or services from the open capability provider according to the call request carrying the specific identifier;

an adaptation conversion unit 404, configured to perform adaptation conversion on the data information or service received by the acquisition unit 403;

The sending unit 405 is configured to send the data information or service after adaptation and conversion to the Widget client.

Wherein, the obtaining unit 403 is further configured to parse the call request to obtain the call parameter including the specific identifier, and obtain corresponding data information or services from the open capability provider according to the call parameter including the specific identifier, Also can further comprise structure as shown in Figure 5:

A parsing subunit 501, configured to parse the call request to obtain call parameters including the specific identifier;

A sending subunit 502, configured to send data information or a service request message to a corresponding open capability provider according to the invocation parameter including the specific identifier;

The receiving subunit 503 is configured to receive data information or services sent by the corresponding open capability provider.

In the Widget server provided by the embodiment of the present invention, the Widget server encapsulates the open capability of the open capability provider and develops and generates a Widget file including a specific identifier. When the Widget client downloads the file and uses it, the Widget server By receiving the invocation request sent by the Widget client and including the specific identifier, and requesting corresponding data information or services from the open capability provider for the Widget client according to the invocation request. The technical solution provided by the embodiment of the present invention encapsulates the open capabilities of the open capability provider, so that Widget users can use many open capabilities without knowing the business logic of the open capability provider.

Those of ordinary skill in the art can understand that all or part of the steps for realizing the above-mentioned method embodiments can be completed by hardware related to program instructions, and the aforementioned program can be stored in a computer-readable storage medium. When the program is executed, the Including the steps of the foregoing method embodiments; and the aforementioned storage medium includes: ROM (Read-Only Memory, read-only storage memory), RAM (Random Access Memory, random storage memory), magnetic disk or optical disc, etc. various programs that can be stored The medium of the code.

The above description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the invention. Therefore, the present invention will not be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims (12)

1. A method for using a network open capability, comprising: Receive the invocation request for the open capability of the open capability provider sent by the Widget client, and the invocation request encapsulates the downloaded open capability of the open capability provider by the Widget client and develops and generates a Widget including a specific identifier The file is generated by parsing and constructing, and the calling request carries the specific identifier; Obtain corresponding data information or services from the open capability provider according to the call request carrying the specific identifier; Adapting and transforming the received data information or service and returning it to the Widget client. 2. The method according to claim 1, wherein said encapsulating the open capability of the open capability provider comprises: encapsulating the same network capability for the open capability of the open capability provider in the same network; The open capabilities of the open capability provider in the heterogeneous network perform cross-network capability encapsulation. 3. The method according to claim 1, wherein said packaging and developing the open capability of the open capability provider generates a Widget file including a specific identifier, including: Encapsulate and develop the open capability of the open capability provider to generate a Widget file including a specific uniform resource locator or a specific access code; or, Encapsulate and develop the open capabilities of the open capability provider to generate a Widget file including specific extended HTML tags; or, Encapsulate and develop the open capabilities of the open capability provider to generate a Widget file including a specific JavaScript object. 4. The method according to claim 1, wherein the receiving the call request sent by the Widget client to the open capability of the open capability provider comprises: receiving a call request sent by the Widget client for the unified capability encapsulation interface of the open capability of the open capability provider. 5. The method according to claim 1, wherein the step of obtaining corresponding data information or services from the open capability provider according to the call request carrying the specific identifier comprises; Analyzing the call request to obtain call parameters including the specific identifier; Obtain corresponding data information or services from the open capability provider according to the invocation parameter including the specific identifier. 6. The method according to claim 5, wherein the obtaining corresponding data information or services from the open capability provider according to the invocation parameters including the specific identification includes: Sending data information or a service request message to the open capability provider according to the call parameter including the specific identifier; Receive data information or services sent by the corresponding open capability provider. 7. The method according to claim 5, wherein the sending a data or service request message to the open capability provider according to the call parameter comprises: Select the open capability provider according to the specific identifier included in the call parameter, and send a data or service request message to the selected open capability provider. 8. The method according to claim 1, wherein said performing adaptation conversion on the received data information or service comprises: Perform protocol conversion and/or data conversion on the received data information or service. 9. A system for using network open capabilities, comprising: a Widget server, a Widget client, and an open capability provider, wherein, The Widget server is used to encapsulate the open capabilities of the open capability provider and develop and generate a Widget file including a specific identification for the Widget client to download; it specifically includes: A receiving unit, configured to receive an invocation request for the open capability of the open capability provider sent by the Widget client, the invocation request is generated by the Widget client by analyzing and constructing the Widget file, and in the invocation request carry said specific identification; An obtaining unit, configured to obtain corresponding data information or services from the open capability provider according to the call request carrying the specific identifier; an adaptation conversion unit, configured to perform adaptation conversion on the data information or service; a sending unit, configured to send the data information or service after adaptation and conversion to the Widget client; The Widget client is configured to download the Widget file including the specific identifier, parse and construct the Widget file to generate an invocation request for the open capability of the open capability provider, and the invocation request carries the specific identifier. 10. The system for using the network openness capability according to claim 9, wherein the Widget server is further configured to parse the call request to obtain a call parameter including the specific identifier, and according to the call parameter including the specific identifier The calling parameter obtains the corresponding data information or service from the open capability provider. 11. A Widget server, characterized in that, the Widget server encapsulates and develops the open capability of the open capability provider to generate a Widget file including a specific identification, for the Widget client to download, including: A receiving unit, configured to receive an invocation request for the open capability of the open capability provider sent by the Widget client, the invocation request is generated by the Widget client by analyzing and constructing the Widget file, and in the invocation request carry said specific identification; An obtaining unit, configured to obtain corresponding data information or services from the open capability provider according to the call request carrying the specific identifier; an adaptation conversion unit, configured to perform adaptation conversion on the data information or service; A sending unit, configured to send the data information or service after adaptation and conversion to the Widget client. 12. The Widget server according to claim 11, wherein the acquiring unit comprises: A parsing subunit, configured to parse the call request to obtain call parameters including the specific identifier; A sending subunit, configured to send data information or a service request message to a corresponding open capability provider according to the invocation parameter including the specific identifier; The receiving subunit is configured to receive data information or services sent by the corresponding open capability provider.

Images