(19)
(11)EP 2 717 542 B1

(12)EUROPEAN PATENT SPECIFICATION

(45)Mention of the grant of the patent:
26.06.2019 Bulletin 2019/26

(21)Application number: 12792185.6

(22)Date of filing:  05.03.2012
(51)International Patent Classification (IPC): 
H04L 29/08(2006.01)
G06F 8/61(2018.01)
G06F 9/445(2018.01)
(86)International application number:
PCT/CN2012/071918
(87)International publication number:
WO 2012/163123 (06.12.2012 Gazette  2012/49)

(54)

APPLICATION MANAGEMENT METHOD AND APPLICATION PLATFORM

ANWENDUNGSMANAGEMENTVERFAHREN UND ANWENDUNGSPLATTFORM

PROCÉDÉ DE GESTION D'APPLICATIONS ET PLATE-FORME D'APPLICATIONS


(84)Designated Contracting States:
AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

(30)Priority: 27.05.2011 CN 201110140138

(43)Date of publication of application:
09.04.2014 Bulletin 2014/15

(73)Proprietor: Tencent Technology (Shenzhen) Company Limited
Shenzhen, Guangdong 518044 (CN)

(72)Inventor:
  • CHANG, Qing
    Shenzhen Guangdong 518044 (CN)

(74)Representative: Gunzelmann, Rainer 
Wuesthoff & Wuesthoff Patentanwälte PartG mbB Schweigerstraße 2
81541 München
81541 München (DE)


(56)References cited: : 
CN-A- 101 336 423
CN-A- 101 895 872
US-A1- 2008 215 758
US-A1- 2011 046 956
CN-A- 101 853 296
US-A1- 2002 032 763
US-A1- 2010 287 552
  
      
    Note: Within nine months from the publication of the mention of the grant of the European patent, any person may give notice to the European Patent Office of opposition to the European patent granted. Notice of opposition shall be filed in a written reasoned statement. It shall not be deemed to have been filed until the opposition fee has been paid. (Art. 99(1) European Patent Convention).


    Description

    Field of the Invention



    [0001] The present invention relates to application providing technologies, and more particularly, to a method for managing an application and an application platform.

    Background of the Invention



    [0002] Currently, there are lots of application platforms running on a Windows desktop. A user may search for and select a desired application (which may be referred to as APP) by means of an application market provided by an application platform installed on a client, and the desired application is installed on the platform.

    [0003] In practice, when the user shifts a login site, e.g., the user logs in client A previously and installs some applications, and then the user logs in client B, then the user needs to re-search the application market for the desired application, and installs the desired application on client B. In this case, the user could not automatically obtain, in some way, a list of applications installed on client A, so that it is very troublesome to the user.

    [0004] A document (US 2010/287552 A1) relates to a method for providing integrated application management, and more particularly, to a method which can provide a convenient usage environment by integratedly managing various types of contents and application programs.

    [0005] Document US 2008/215758 A1 relates to a method, devices, and a computer program for synchronizing one or more software programs from a first device (D100) to a second device (D200).

    Summary of the Invention



    [0006] Examples of the present invention provide a method for managing an application, so that a list of applications previously installed can be easily and quickly obtained after a user shifts a login site.

    [0007] Examples of the present invention provide an application platform, so that a list of applications previously installed can be easily and quickly obtained after a user shifts a login site.

    [0008] Technical solutions provided by the examples of the present invention are implemented as follows.

    [0009] A method for managing an application includes:

    installing, by an application platform on a first client currently logged in by a user, a first application upon receiving a request for installing the first application, and sending a summary of the first application to a server; wherein an application list is maintained for each user in the server, and the application list is to store summaries of all of applications installed by each user; and

    uninstalling, by the application platform, a second application upon receiving a request for uninstalling the second application, and notifying the server to delete a summary of the second application from an application list corresponding to the user sending the request for uninstalling the second application;

    obtaining, from the server by the application platform on a second client logged in by the user after the user shifts a login site, the application list corresponding to the user, and installing a third application according to a summary of the third application stored in the application list;

    wherein the first application, the second application and the third application are a same application or different applications;

    wherein the application platform supports at least three kinds of applications comprising an application developed based on an Extensible Markup Language (XML) and a Script, an application developed based on a binary Dynamic Link Library (Dll), and an application developed based on a web page;

    the application platform supports the application developed based on the binary Dll through providing a capability for displaying a graphical interface, a capability for storing user data in the local, a network communication capability, and a security authentication capability;

    the application platform supports the application developed based on the XML and the Script through providing the capability for displaying the graphical interface, the capability for storing the user data in the local, the network communication capability, the security authentication capability, a capability for analyzing the XML, and a capability for interpreting and executing the Script; and

    the application platform supports the application developed based on the web page through providing a capability for providing an interface window, wherein a browser control is embedded in the window, and a capability for loading a designated web page into the embedded browser when the application developed based on the web page is started;

    wherein the capability for storing the user data in the local comprises storing the user data into a local database in the form of a two-dimensional table or an independent file.



    [0010] An application platform according to claim 6 is provided.

    [0011] Preferred embodiments are defined in the dependent claims.

    [0012] As can be seen from the above that when the examples provided by the present invention are employed, a list of applications previously installed is maintained for each user in the server, and the list can be easily and quickly obtained from the server after the user shifts a login site, so that troubles like re-searching can be avoided, and the application can be directly installed in accordance with the summary including the address of the installation package. Moreover, to support applications developed by different technologies, the application platform in the first and second device needs to support a plurality of capabilities, so that applications could be successfully installed.

    Brief Description of Drawings



    [0013] 

    FIG. 1 is a flowchart illustrating a method for installing an application in accordance with an example of the present invention.

    FIG. 2 is a flowchart illustrating a method for uninstalling an application in accordance with an example of the present invention.

    FIG. 3 is a schematic diagram illustrating a message channel and a recommendation channel in accordance with an example of the present invention.

    FIG. 4 is a schematic diagram illustrating a message format in accordance with an example of the present invention.

    FIG. 5 is a schematic diagram illustrating a structure of an application platform in accordance with an example of the present invention.


    Detailed Description of the Invention



    [0014] For the problem existing in conventional systems, examples of the present invention provide an improved method for managing an application, including: installing, by an application platform, an application upon receiving a request for installing the application, and sending a summary of the application to a server, wherein a list of installed applications is maintained for each user in the server, wherein the list of the installed applications includes summaries of all of the installed applications; uninstalling, by the application platform, an application upon receiving a request for uninstalling the application, and notifying the server to delete a summary of the application from a corresponding list of installed applications. Therefore, when a user shifts a login site, an application platform on a client logged in by the user can easily and quickly obtain a list of applications previously installed from the server. In this case, the application to be installed and the application to be uninstalled may be the same application or may be different applications.

    [0015] Hereinafter, the technical solution of the present invention is described in further detail with reference to the accompanying drawings and examples to make the technical solution clearer.

    [0016] FIG. 1 is a flowchart illustrating a method for installing an application in accordance with an example of the present invention. As shown in FIG. 1, the method includes operations as follows.

    [0017] In block 11, after receiving a request for installing an application, an application platform sends to a server account information and an identifier (ID) of the application, and the server checks an installation license.

    [0018] In practice, the application platform may provide an application market for a user to select a desired application of the user, and the user clicks on the application for installing.

    [0019] The account information may include information like a user ID and related permissions.

    [0020] In block 12, if the installation is permitted, the server issues an address of an installation package to the application platform.

    [0021] If there are no restrictions like level limitation or purchase opening, the installation is permitted. Accordingly, the server issues the address of the installation package to the application platform, and may issue check information also.

    [0022] In block 13, the application platform downloads the installation package according to the received address of the installation package.

    [0023] If the application platform receives the check information simultaneously, then in this block, the application platform checks the integrity and legitimacy of the download installation package in accordance with the received check information after downloading the installation package according to the received address of the installation package. Block 14 is performed when the check is passed.

    [0024] In block 14, the application platform installs the downloaded installation package.

    [0025] The installation process mainly includes operations as follows.
    1. 1) resources and a running file is copied into a designated directory; and
    2. 2) new application information is registered in an encrypted application registry file, wherein the new application information includes start-up information and running parameters.


    [0026] In block 15, the application platform sends to the server a summary of the application installed after the installation is successful. A list of installed applications is maintained for each user in the server, wherein the list is used to store summaries of the installed applications.

    [0027] The summary may include the application ID and the address of the installation package, etc. Subsequently, if the user wants to install an application that is in the list of installed applications after the user shifts a login site, the application is directly installed in accordance with the summary including the address of the installation package.

    [0028] FIG. 2 is a flowchart illustrating a method for uninstalling an application in accordance with an example of the present invention. As shown in FIG.2, the method may include operations as follows.

    [0029] In block 21, an application platform uninstalls an application upon receiving a request for uninstalling the application.

    [0030] The uninstallation process mainly includes operations as follows.
    1. 1) information about the application is deleted from an encrypted application registry file; and
    2. 2) running resources and temporary files of the application in the local are cleaned up.


    [0031] In block 22, the application platform notifies a server to delete a summary of the application from a corresponding list of installed applications.

    [0032] In practice, a user may view updated information, i.e., upgrade information, of an installed application through the application market. An upgrade process is a recombination process, in which the installation process and the uninstallation process are integrated. That is, an original application is uninstalled according to the method shown in FIG. 2 firstly, and then an upgraded application is installed according to the method shown in FIG. 1.

    [0033] In addition, the application platform may display the list of the installed applications with a friendly interaction interface, wherein the list of the installed applications is obtained by the application platform from the server. In order to provide a better service to the user and to meet demands of the user as much as possible, the application platform provided by the example of the present invention supports applications with various types, and provides a friendly application programming interface (API), so that each application may use functions provided by the application platform itself. Specifically, the application platform may support at least three kinds of applications including an application developed based on an Extensible Markup Language (XML) and a Script, an application developed based on a Dynamic Link Library (Dll), and an application developed based on a web page. For ease of description, hereinafter these three kinds of applications are referred to as XscApp, DllApp, and WebApp.

    [0034] Hereinafter, the above three kinds of applications are described, respectively.

    1) DllApp



    [0035] This kind of application is developed using a high performance language like C++, and a function of the application is ultimately registered to the application platform in the form of the Dll.

    [0036] Advantages of this kind of application are that there is a good logic encapsulation within the internal of the Dll; it has a strong capability as being developed using the high performance language like C++, e.g., the construction of a user interface does not depend on a browser, but uses a window system of a normal Windows desktop application, etc.

    [0037] Scene: it is suitable to open to a team trusted by a company to develop related advanced applications.

    [0038] To support running of this kind of application, the application platform provides a series of basic service capabilities including:
    1. A, a capability for displaying a graphical interface, i.e., to provide an interface engine;
    2. B, a local storage capability for user data, i.e., the user data is stored in a local database in the form of a two-dimensional table or an independent file;
    3. C, a network communication capability, i.e., to provide, for this kind of application, supports of communication protocols such as the Transmission Control Protocol (TCP), the User Datagram Protocol (UDP), and the Hypertext Transfer Protocol (HTTP), etc., so that this kind of application may have the network communication capability; and
    4. D, a security authentication capability, i.e., to provide capabilities like login and authentication.


    [0039] In practice, the above capabilities are usually developed using the C++ language. The DllApp may directly call the above capabilities because the DllApp is developed based on the C++ language also.

    2) XscApp



    [0040] This kind of application includes three kinds of documents, i.e., XML, Script, and Pic. Among them, the XML is used to describe an interface presentation of the application, including a size of a window, a size, a position, and a style of a button, and transparency of an icon, etc. The Script is used to describe an interaction logic of the application, e.g., a message prompt box is popped up when a user clicks on a button, etc. The Pic refers to all of icons and material files used by the application.

    [0041] Advantages of this kind of application are that difficulties and costs for developing this kind of application are lower; the XML may be quickly defined through an interface editor in the aspect of constructing an interface; logic description becomes easy and understandable for the simplicity of the Script; more importantly, a binary part/code is not included, so that it is very simple to review; capabilities of the Script may be strictly limited, so that it does not pose any security threat to the application platform itself.

    [0042] Scene: it is suitable to open to a third-party company for developing, and there is a great advantage in both the development and the review.

    [0043] Supports required by this kind of application are the same as those required by the DllApp, i.e., the application platform provides basic service capabilities like the above A, B, C, and D to support running of the XscApp. Since the XscApp is implemented by the XML and the Script, and cannot directly employ a development capability of the C++ language, an additional "middle layer" is required to provide support, i.e., the application platform also provides a capability for analyzing the XML and a capability for interpreting and executing the Script.

    [0044] In this case, the capability for analyzing the XML means that an interface engine supporting XML deserialization is required to construct interface primary colors, so that each node of the XML can be strictly translated into one or more than one interface control trees and a desired interface effect can be achieved.

    [0045] The capability for interpreting and executing the Script means to provide a script engine which is used to interpret and execute a logic script in the XscApp and mainly implements two functions including controlling a user interface constructed by the interface engine, such as displaying and hiding of a window, switching of a button, etc.; and implementing the local storage of the user data, the network communication, and the security authentication, etc., using basic services provided by a underlying layer. As the script engine can only perform logic processing, and does not have capabilities like the above storage, communication, and security authentication, these basic services are associated with the script engine in a manner of a service registration.

    3) WebApp



    [0046] Configuration information like an icon, a text description and a Uniform Resource Locator (URL) may be registered when this kind of application is registered. When a user clicks on an icon of an application, the application platform pops up an interface window in which a browser control is embedded, and loads a web page to which the URL points.

    [0047] An advantage of this kind of application is that existing web applications developed based on the web may be reused.

    [0048] Scene: it is suitable to host an existing and simple web application such as a recharging website or a navigation station.

    [0049] To support running of this kind of application, the application platform provides capabilities including a capability for providing an interface window, wherein a browser control is embedded in the window, and a size, a title, and an icon of the window may be configured according to the configuration information; and a capability for loading a designated web page, i.e., the web page to which the URL points, into the embedded browser when the application is started.

    [0050] So far, descriptions about the three kinds of applications provided by examples of the present invention are completed. Although there is a great difference in the installation package formats and the running ways of the above three kinds of applications, installation processes and uninstallation processes of these three kinds of applications are basically the same, as shown in FIG. 1 and FIG. 2.

    [0051] Further, an example of the present invention provides concepts of a message channel and a recommendation channel to accelerate the popularization of the application.

    [0052] Among them, the message channel allows the user to see the latest dynamical information about an application without starting the application. A typical scenario is "application dynamics", i.e., the user may see, in an application dynamic panel after the user logs in, the latest dynamical information about several applications, such as "three files in the file transfer station are expired", "buddy *** leaves a message in your blog", etc. Based on this, a recommendation channel for a buddy to recommend an application may be further proposed, i.e., when using an application, the user may recommend the application to a buddy if the user likes the application, and an application recommendation message is generated based on this, wherein the message may carry a comment of the user on the application; the application recommendation message is broadcasted, through the recommendation channel, into a Social Networking Services (SNS) relationship network of the user for spreading out.

    [0053] The popularization of the application is no longer limited to a traditional way due to the proposing of the message channel and the recommendation channel, and becomes more flexible and intelligent.

    [0054] FIG. 3 is a schematic diagram illustrating the message channel and the recommendation channel in accordance with an example of the present invention. As shown in FIG. 3, it relates to three parts including a message generating side, a message storage server, and a client.

    [0055] Among them, the message generating side includes a third-party server (3rd server) and an official server. The 3rd server is used to provide background supports for a designated application, and generate an application dynamic message associated with the application (an application dynamic message is generated once the application is updated). The official server is used to transmit an application recommendation message generated by a buddy.

    [0056] The message storage server is used to maintain a message stack for each user. A target user of a message is analyzed when the message is received, and the message is pushed into a message stack corresponding to the target user.

    [0057] Each message is uniquely determined by a 64-bit timestamp at which the message is generated. FIG. 4 is a schematic diagram illustrating a format of the message in accordance with an example of the present invention. As shown in FIG. 4, the format includes a message ID, a way for displaying the message, a target user, an application ID and message contents. Among them, the message ID is the 64-bit timestamp at which the message is generated. The way for displaying the message is used to illustrate in which manner the message is displayed, for example, a manner for popping up a tip may be employed, it may be determined according to information like the message contents which manner may be employed. The target user is used to illustrate to which user the message is sent. The application ID is used to illustrate with which application the message is associated. The message contents are described using an XML format. The message contents may be encrypted and compressed when there is a need.

    [0058] The client is a receiver and a displayer of the message. When a user logs in, the application platform may obtain, from the message storage server, messages that have been already sent to the user and are not displayed, and display the messages. For example, it may detect, according to the timestamp, which messages are generated between the last logout of the user and the login of the user this time, these messages are the messages that are not displayed. During an online period of the user, if a new generated message is received, the message storage server may actively issue the message to the application platform, and the application platform displays the message. Reversely, when the user uses an application and recommends the application to a buddy, the application platform generates an application recommendation message and sends to a buddy selected by the user through the message storage server.

    [0059] For the message storage server, the number of messages stored in each message stack is usually limited, so that messages which have been already displayed to the user may be deleted from the message stack. Alternatively, messages that are pushed at the earliest time are deleted using the first in-first out (FIFO) principle once the message stack is full, wherein the number of the messages deleted is the same as the number of messages newly pushed, examples of the present invention do not limit the specific implementations.

    [0060] Based on the above descriptions, FIG. 5 is a schematic diagram illustrating a structure of an application platform in accordance with an example of the present invention. As shown in FIG. 5, the application platform includes:

    an application center module 51, to install or uninstall an application according to a request received; and

    a list managing module 52, to send a summary of the installed application to a server for saving, and to notify the server to delete a summary of the uninstalled application from a corresponding list of installed applications; wherein a list of installed applications is maintained for each user in the server, and is used to store summaries of the installed applications.



    [0061] The application platform shown in FIG. 5 may further include:

    an application market module 53, to provide an application market for a user to select a desired application; and/or,

    an application displaying module 54, to display the list of the installed applications with a friendly interaction interface, wherein the list of the installed applications is obtained by the application platform from the server.



    [0062] It should be noted that the function of the application market may be provided by the application market module 53, and is to provide resource packages and description information of each application. The application market may be implemented in the form of an application, which is the only one application having an operation permission for managing an interface in the whole application platform. By this way, the application platform does not need to provide an independent entrance for the application market in the interface, so that the interface is very refreshing. At the same time, since the nature of the application market is an application, the user may adjust a position of the application market as operating an ordinary application, so as to facilitate the management of the user.

    [0063] The application center module 51 may include:

    a first application sub-module 511, to provide installation and uninstallation capabilities and a running environment of an application developed based on the XML and the Script;

    a second application sub-module 512, to provide installation and uninstallation capabilities and a running environment of an application developed based on a binary Dll; and

    a third application sub-module 513, to provide installation and uninstallation capabilities and a running environment of an application developed based on a web page.



    [0064] In this case, the first application sub-module 511 may further include an interface displaying unit, a storage unit, a network unit, an authenticating unit, an analyzing unit, and an interpreting unit (these units are not shown in the figure to simplify the drawings). The second application sub-module 512 may further include an interface displaying unit, a storage unit, a network unit and an authenticating unit (these units are not shown in the figure to simplify the drawings). The third application sub-module 513 may further include a loading unit (this unit is not shown in the figure to simplify the drawings).

    [0065] The interface displaying unit is used to display a graphical interface of the application.

    [0066] The storage unit is used to store user data in the local, i.e., to store the user data into a local database in the form of a two-dimensional table or an independent file.

    [0067] The network unit is used to provide supports of various communication protocols for the application, so that the application has a network communication capability.

    [0068] The authenticating unit is used to provide a security authentication capability for the application.

    [0069] The analyzing unit is used to analyze the XML.

    [0070] The interpreting unit is used to interpret and execute the Script

    [0071] The loading unit is used to provide an interface window, wherein a browser control is embedded in the window, and to load a designated web page into the embedded browser when the application is started.

    [0072] In addition, the application platform shown in FIG. 5 may further include:
    a message processing module 55, to obtain, from the server, messages that are sent to the user and are not displayed, display the messages; receive and display, during an online period of the user, messages issued by the server to the user and newly generated during the online period of the user.

    [0073] The message includes an application dynamic message and/or an application recommendation message, wherein the application recommendation message is a message generated according to a recommendation act from a buddy of the user on the application.

    [0074] The message processing module 55 may be further used to generate an application recommendation message when the user uses an application and recommends the application to a buddy, and to send the application recommendation message to the buddy selected by the user through the server.

    [0075] The above-mentioned message may include a message ID, a way for displaying the message, a target user, an application ID, and message contents.

    [0076] A workflow of the application platform shown in FIG. 5 may refer to descriptions in the above method examples, which are not repeated herein.

    [0077] The above are several examples of the present invention, and are not used for limiting the protection scope of the present invention, which is defined by the claims.


    Claims

    1. A method for managing an application, comprising:

    installing, by an application platform on a first client currently logged in by a user, a first application upon receiving a request for installing the first application, and sending a summary of the first application to a server; wherein an application list is maintained for each user in the server, and the application list is to store summaries of all of applications installed by each user (15); and

    uninstalling, by the application platform, a second application upon receiving a request for uninstalling the second application (21), and notifying the server to delete a summary of the second application from an application list corresponding to the user sending the request for uninstalling the second application (22);

    obtaining, from the server by the application platform on a second client logged in by the user after the user shifts a login site, the application list corresponding to the user, and installing a third application according to a summary of the third application stored in the application list;

    wherein the first application, the second application and the third application are a same application or different applications,

    characterized in that

    the application platform supports at least three kinds of applications comprising an application developed based on an Extensible Markup Language, XML, and a Script, an application developed based on a binary Dynamic Link Library, Dll, and an application developed based on a web page;

    the application platform supports the application developed based on the binary Dll through providing a capability for displaying a graphical interface, a capability for storing user data in the local, a network communication capability, and a security authentication capability;

    the application platform supports the application developed based on the XML and the Script through providing the capability for displaying the graphical interface, the capability for storing the user data in the local, the network communication capability, the security authentication capability, a capability for analyzing the XML, and a capability for interpreting and executing the Script; and

    the application platform supports the application developed based on the web page through providing a capability for providing an interface window, wherein a browser control is embedded in the window, and a capability for loading a designated web page into the embedded browser when the application developed based on the web page is started;

    wherein the capability for storing the user data in the local comprises storing the user data into a local database in the form of a two-dimensional table or an independent file.


     
    2. The method of claim 1, further comprising:
    providing, by the application platform, an application market to the user of the first client to select a desired application.
     
    3. The method of claim 1, further comprising:
    obtaining, by the application platform from the server, an application list, and displaying the application list with an interaction interface.
     
    4. The method of any of claims 1 to 3, further comprising:

    obtaining, by the application platform, a first application dynamic message from the server when the user logs in, and displaying the first application dynamic message; wherein the first application dynamic message is a message which has been already sent to the user by the server and is not displayed; and

    receiving, by the application platform during an online period of the user, a second application dynamic message from the server, and displaying the second application dynamic message; wherein the second application dynamic message is a message which is newly generated and issued by the server to the user during the online period of the user.


     
    5. The method of claim 4, wherein the first application dynamic message or the second application dynamic message comprises a message identifier, ID, a way for displaying the message, a target user, an application ID and message contents.
     
    6. An application platform, comprising:

    an application center module (51), to install, when the application platform is executed on a first client currently logged in by a user, a first application upon receiving a request for installing the first application, or to uninstall a second application upon receiving a request for uninstalling the second application, or install, when the application platform is executed on a second client logged in by the user after the user shifts a login site, a third application according to a summary of the third application stored in an application list, wherein the application list is maintained for each user in a server, and the application list is to store summaries of all of applications installed by each user;

    a list managing module (52), to send a summary of the first application to the server for storing corresponding to the user sending the request for installing the first application, or to notify the server to delete a summary of the second application from the application list corresponding to the user sending the request for uninstalling the second application, or obtain from the server the application list corresponding to the user;

    wherein the first application, the second application and the third application are a same application or different applications; wherein

    the application center module comprises:

    a first application sub-module (511), to provide installation and uninstallation capabilities and a running environment of an application developed based on an Extensible Markup Language, XML, and a Script;

    a second application sub-module (512), to provide installation and uninstallation capabilities and a running environment of an application developed based on a binary Dynamic Link Library, Dll;and

    a third application sub-module (513), to provide installation and uninstallation capabilities and a running environment of an application developed based on a web page,

    characterized in that

    the first application sub-module (511) comprises a first interface displaying unit, a first storage unit, a first network unit, a first authenticating unit, an analyzing unit, and an interpreting unit;

    the second application sub-module (512) comprises a second interface displaying unit, a second storage unit, a second network unit, and a second authenticating unit; and

    the third application sub-module (513) comprises a loading unit;

    the first interface displaying unit is to display a graphical interface of the application developed based on the XML and the Script;

    the second interface displaying unit is to display a graphical interface of the application developed based on the Dll the first storage unit is to store user data into a local database in the form of a two-dimensional table or an independent file;

    the second storage unit is to store the user data into the local database in the form of the two-dimensional table or the independent file;

    the first network unit is to provide supports of various communication protocols for the application developed based on the XML and the Script, so that said application has a network communication capability;

    the second network unit is to provide the supports of the various communication protocols for the application developed based on the Dll, so that said application has the network communication capability;

    the first authenticating unit is to provide a security authentication capability for the application developed based on the XML and the Script;

    the second authenticating unit is to provide the security authentication capability for the application developed based on the Dll;

    the analyzing unit is to analyze the XML;

    the interpreting unit is to interpret and execute the Script; and

    the loading unit is to provide an interface window, wherein a browser control is embedded in the window, and to load a designated web page into the embedded browser when the application developed based on the web page is started.


     
    7. The application platform of claim 6, further comprising:
    an application market module (53), to provide an application market to a user of a client where the application market module locates to select a desired application.
     
    8. The application platform of claim 6, further comprising:
    an application displaying module (54), to display an application list obtained by the application platform from the server with an interaction interface.
     
    9. The application platform of any of claims 6 to 8, further comprising:

    a message processing module (55), to obtain a first application dynamic message from the server when the user logs in, and to display the first application dynamic message; wherein the first application dynamic message is a message which has been already sent to the user by the server and is not displayed; and

    to receive, during an online period of the user, a second application dynamic message from the server, and to display the second application dynamic message; wherein the second application dynamic message is a message which is newly generated and issued by the server to the user during the online period of the user.


     
    10. The application platform of claim 9, wherein the first application dynamic message or the second application dynamic message comprises a message identifier, ID, a way for displaying the message, a target user, an application ID and message contents.
     


    Ansprüche

    1. Verfahren zur Verwaltung einer Anwendung, umfassend:

    Installieren einer ersten Anwendung durch eine Anwendungsplattform auf einem ersten Clienten, der aktuell durch einen Benutzer angemeldet ist, nach Empfangen einer Anforderung zum Installieren der ersten Anwendung und Senden einer Zusammenfassung der ersten Anwendung an einen Server; wobei eine Anwendungsliste für jeden Benutzer in dem Server gepflegt wird und die Anwendungsliste Zusammenfassungen aller Anwendungen speichern soll, die von jedem Benutzer installiert werden (15); und

    Deinstallieren einer zweiten Anwendung durch die Anwendungsplattform nach Empfangen einer Anforderung zum Deinstallieren der zweiten Anwendung (21) und Benachrichtigen des Servers, eine Zusammenfassung der zweiten Anwendung aus einer Anwendungsliste zu löschen, entsprechend dem Benutzer, der die Anforderung zum Deinstallieren der zweiten Anwendung gesendet hat (22);

    Beziehen der Anwendungsliste entsprechend dem Benutzer von dem Server durch die Anwendungsplattform auf einem zweiten Clienten, der durch den Benutzer angemeldet ist, nachdem der Benutzer eine Anmeldungsseite geändert hat, und Installieren einer dritten Anwendung entsprechend einer Zusammenfassung der dritten Anwendung, die in der Anwendungsliste gespeichert ist;

    wobei die erste Anwendung, die zweite Anwendung und die dritte Anwendung dieselbe Anwendung oder unterschiedliche Anwendungen sind,

    dadurch gekennzeichnet, dass

    die Anwendungsplattform mindestens drei Arten von Anwendungen unterstützt, umfassend eine Anwendung, die auf der Basis einer Extensible Markup Language, XML, und eines Skripts entwickelt wurde, eine Anwendung, die auf der Basis einer binären Dynamic Link Library, Dll, entwickelt wurde, und eine Anwendung, die auf der Basis einer Webseite entwickelt wurde;

    die Anwendungsplattform die Anwendung, die auf der Basis der binären Dll entwickelt wurde, durch Bereitstellen einer Fähigkeit zum Anzeigen einer grafischen Schnittstelle, einer Fähigkeit zum Speichern von Benutzerdaten im Lokalen, einer Netzwerkkommunikationsfähigkeit und einer Sicherheitsauthentifizierungsfähigkeit unterstützt;

    die Anwendungsplattform die Anwendung, die auf der Basis der XML und des Skripts entwickelt wurde, durch Bereitstellen einer Fähigkeit zum Anzeigen der grafischen Schnittstelle, der Fähigkeit zum Speichern der Benutzerdaten im Lokalen, der Netzwerkkommunikationsfähigkeit, der Sicherheitsauthentifizierungsfähigkeit, einer Fähigkeit zum Analysieren der XML und einer Fähigkeit zum Interpretieren und Ausführen des Skripts unterstützt und

    die Anwendungsplattform die Anwendung, die auf der Basis der Webseite entwickelt wurde, durch Bereitstellen einer Fähigkeit zum Bereitstellen eines Schnittstellenfensters, wobei eine Browser-Steuerung in dem Fenster eingebettet ist, und einer Fähigkeit zum Laden einer bezeichneten Webseite in den eingebetteten Browser, wenn die Anwendung, die auf der Basis der Webseite entwickelt wurde, gestartet wird, unterstützt;

    wobei die Fähigkeit zum Speichern der Benutzerdaten im Lokalen ein Speichern der Benutzerdaten in einer lokalen Datenbank in der Form einer zweidimensionalen Tabelle oder einer unabhängigen Datei umfasst.


     
    2. Verfahren nach Anspruch 1, weiterhin umfassend:
    Bereitstellen eines Anwendungsmarkts für den Benutzer des ersten Clienten durch die Anwendungsplattform, um eine gewünschte Anwendung auszuwählen.
     
    3. Verfahren nach Anspruch 1, weiterhin umfassend:
    Beziehen einer Anwendungsliste durch die Anwendungsplattform von dem Server und Anzeigen der Anwendungsliste mit einer Interaktionsschnittstelle.
     
    4. Verfahren nach einem der Ansprüche 1 bis 3, weiterhin umfassend:

    Beziehen einer ersten anwendungsdynamischen Nachricht von dem Server durch die Anwendungsplattform, wenn der Benutzer sich anmeldet, und Anzeigen der ersten anwendungsdynamischen Nachricht; wobei die erste anwendungsdynamische Nachricht eine Nachricht ist, die bereits durch den Server an den Benutzer gesendet wurde und nicht angezeigt wird; und

    Empfangen einer zweiten anwendungsdynamischen Nachricht von dem Server durch die Anwendungsplattform während einer Online-Periode des Benutzers und Anzeigen der zweiten anwendungsdynamischen Nachricht; wobei die zweite anwendungsdynamische Nachricht eine Nachricht ist, die neu erstellt und durch den Server an den Benutzer während der Online-Periode des Benutzers ausgegeben wird.


     
    5. Verfahren nach Anspruch 4, wobei die erste anwendungsdynamische Nachricht oder die zweite anwendungsdynamische Nachricht eine Nachrichtenkennung, ID, eine Weise zum Anzeigen der Nachricht, einen Sollbenutzer, eine Anwendungs-ID und einen Nachrichteninhalt umfasst.
     
    6. Anwendungsplattform, umfassend:

    ein Anwendungszentrumsmodul (51), um eine erste Anwendung nach Empfangen einer Anforderung zum Installieren der ersten Anwendung zu installieren, wenn die Anwendungsplattform auf einem ersten Clienten ausgeführt wird, der aktuell durch einen Benutzer angemeldet ist, oder eine zweite Anwendung nach Empfangen einer Anforderung zum Deinstallieren der zweiten Anwendung zu deinstallieren oder eine dritte Anwendung entsprechend einer Zusammenfassung der dritten Anwendung, die in einer Anwendungsliste gespeichert ist, zu installieren, wenn die Anwendungsplattform auf einem zweiten Clienten ausgeführt wird, der durch den Benutzer angemeldet ist, nachdem der Benutzer eine Anmeldungsseite geändert hat, wobei die Anwendungsliste für jeden Benutzer in einem Server gepflegt wird und die Anwendungsliste Zusammenfassungen aller Anwendungen speichern soll, die von jedem Benutzer installiert werden;

    ein Listenverwaltungsmodul (52), um eine Zusammenfassung der ersten Anwendung an den Server zum Speichern, entsprechend dem Benutzer, der die Anforderung zum Installieren der ersten Anwendung gesendet hat, zu senden, oder den Server zu benachrichtigen, eine Zusammenfassung der zweiten Anwendung aus der Anwendungsliste zu löschen, entsprechend dem Benutzer, der die Anforderung zum Deinstallieren der zweiten Anwendung gesendet hat, oder die Anwendungsliste entsprechend dem Benutzer zu beziehen;

    wobei die erste Anwendung, die zweite Anwendung und die dritte Anwendung dieselbe Anwendung oder unterschiedliche Anwendungen sind; wobei

    das Anwendungszentrumsmodul umfasst:

    ein erstes Anwendungssubmodul (511), um eine Installation und eine Deinstallation von Fähigkeiten und eine Laufumgebung einer Anwendung, die auf der Basis einer Extensible Markup Language, XML, und eines Skripts entwickelt wurde, bereitzustellen;

    ein zweites Anwendungssubmodul (512), um eine Installation und eine Deinstallation von Fähigkeiten und eine Laufumgebung einer Anwendung, die auf der Basis einer binären Dynamic Link Library, Dll, entwickelt wurde, bereitzustellen; und

    ein drittes Anwendungssubmodul (513), um eine Installation und eine Deinstallation von Fähigkeiten und eine Laufumgebung einer Anwendung, die auf der Basis einer Webseite entwickelt wurde, bereitzustellen,

    dadurch gekennzeichnet, dass

    das erste Anwendungssubmodul (511) eine erste Schnittstellenanzeigeeinheit, eine erste Speichereinheit, eine erste Netzwerkeinheit, eine erste Authentifizierungseinheit, eine Analyseeinheit und eine Interpretationseinheit umfasst;

    das zweite Anwendungssubmodul (512) eine zweite Schnittstellenanzeigeeinheit, eine zweite Speichereinheit, eine zweite Netzwerkeinheit und eine zweite Authentifizierungseinheit umfasst;

    das dritte Anwendungssubmodul (513) eine Ladeeinheit umfasst;

    die erste Schnittstellenanzeigeeinheit eine grafische Schnittstelle der Anwendung, die auf der Basis der XML und des Skripts entwickelt wurde, anzeigen soll;

    die zweite Schnittstellenanzeigeeinheit eine grafische Schnittstelle der Anwendung, die auf der Basis der Dll entwickelt wurde, anzeigen soll;

    die erste Speichereinheit Benutzerdaten in einer lokalen Datenbank in der Form einer zweidimensionalen Tabelle oder einer unabhängigen Datei speichern soll;

    die zweite Speichereinheit die Benutzerdaten in der lokalen Datenbank in der Form der zweidimensionalen Tabelle oder der unabhängigen Datei speichern soll;

    die erste Netzwerkeinheit Unterstützungen von verschiedenen Kommunikationsprotokollen für die Anwendung, die auf der Basis der XML und des Skripts entwickelt wurde, bereitstellen soll, so dass die Anwendung eine Netzwerkkommunikationsfähigkeit aufweist;

    die zweite Netzwerkeinheit die Unterstützungen der verschiedenen Kommunikationsprotokolle für die Anwendung, die auf der Basis der Dll entwickelt wurde, bereitstellen soll, so dass die Anwendung die Netzwerkkommunikationsfähigkeit aufweist;

    die erste Authentifizierungseinheit eine Sicherheitsauthentifizierungsfähigkeit für die Anwendung, die auf der Basis der XML und des Skripts entwickelt wurde, bereitstellen soll;

    die zweite Authentifizierungseinheit die Sicherheitsauthentifizierungsfähigkeit für die Anwendung, die auf der Basis der Dll entwickelt wurde, bereitstellen soll;

    die Analyseeinheit die XML analysieren soll;

    die Interpretationseinheit das Skript interpretieren und ausführen soll und

    die Ladeeinheit ein Schnittstellenfenster bereitstellen soll, wobei eine Browser-Steuerung in dem Fenster eingebettet ist, und eine bezeichnete Webseite in den eingebetteten Browser laden soll, wenn die Anwendung, die auf der Basis der Webseite entwickelt wurde, gestartet wird.


     
    7. Anwendungsplattform nach Anspruch 6, weiterhin umfassend:
    ein Anwendungsmarktmodul (53), um einen Anwendungsmarkt für einen Benutzer eines Clienten bereitzustellen, wobei das Anwendungsmarktmodul sich lokalisiert, um eine gewünschte Anwendung auszuwählen.
     
    8. Anwendungsplattform nach Anspruch 6, weiterhin umfassend:
    ein Anwendungsanzeigemodul (54), um eine Anwendungsliste, die durch die Anwendungsplattform von dem Server bezogen wurde, mit einer Interaktionsschnittstelle anzuzeigen.
     
    9. Anwendungsplattform nach einem der Ansprüche 6 bis 8, weiterhin umfassend:

    ein Nachrichtenverarbeitungsmodul (55), um eine erste anwendungsdynamische Nachricht von dem Server zu beziehen, wenn der Benutzer sich anmeldet, und die erste anwendungsdynamische Nachricht anzuzeigen; wobei die erste anwendungsdynamische Nachricht eine Nachricht ist, die bereits durch den Server an den Benutzer gesendet wurde und nicht angezeigt wird; und

    während einer Online-Periode des Benutzers eine zweite anwendungsdynamische Nachricht von dem Server zu empfangen und die zweite anwendungsdynamische Nachricht anzuzeigen; wobei die zweite anwendungsdynamische Nachricht eine Nachricht ist, die neu erstellt und durch den Server an den Benutzer während der Online-Periode des Benutzers ausgegeben wird.


     
    10. Anwendungsplattform nach Anspruch 9, wobei die erste anwendungsdynamische Nachricht oder die zweite anwendungsdynamische Nachricht eine Nachrichtenkennung, ID, eine Weise zum Anzeigen der Nachricht, einen Sollbenutzer, eine Anwendungs-ID und einen Nachrichteninhalt umfasst.
     


    Revendications

    1. Procédé pour gérer une application, comprenant :

    installer, par une plateforme d'applications sur un premier client auquel est actuellement connecté un utilisateur, une première application lors de la réception d'une requête d'installation de la première application, et envoyer un résumé de la première application à un serveur ; une liste d'applications étant conservée pour chaque utilisateur dans le serveur, et la liste d'applications étant conçue pour stocker des résumés de l'ensemble des applications installées par chaque utilisateur (15) ; et

    désinstaller, par la plateforme d'applications, une deuxième application lors de la réception d'une requête de désinstallation de la deuxième application (21), et notifier au serveur de supprimer un résumé de la deuxième application à partir d'une liste d'applications correspondant à l'utilisateur envoyant la requête de désinstallation de la deuxième application (22) ;

    obtenir, à partir du serveur par la plateforme d'applications sur un second client auquel est connecté l'utilisateur après que l'utilisateur change de site de connexion, la liste d'applications correspondant à l'utilisateur, et installer une troisième application selon un résumé de la troisième application stocké dans la liste d'applications ;

    la première application, la deuxième application et la troisième application étant une même application ou des applications différentes,

    caractérisé par le fait que

    la plateforme d'applications prend en charge au moins trois types d'applications comprenant une application développée sur la base d'un langage de balisage extensible, XML, et d'un script, une application développée sur la base d'une bibliothèque de liens dynamiques, Dll, binaire et une application développée sur la base d'une page Web ;

    la plateforme d'applications prend en charge l'application développée sur la base de la Dll binaire par l'intermédiaire de la fourniture d'une capacité pour afficher une interface graphique, d'une capacité pour stocker des données d'utilisateur en local, d'une capacité de communication réseau, et d'une capacité d'authentification de sécurité ;

    la plateforme d'applications prend en charge l'application développée sur la base du langage XML et du script par l'intermédiaire de la fourniture de la capacité pour afficher l'interface graphique, de la capacité pour stocker les données d'utilisateur en local, de la capacité de communication réseau, de la capacité d'authentification de sécurité, d'une capacité pour analyser le XML, et d'une capacité pour interpréter et exécuter le script ; et

    la plateforme d'applications prend en charge l'application développée sur la base de la page Web par l'intermédiaire de la fourniture d'une capacité pour fournir une fenêtre d'interface, une commande de navigateur étant intégrée dans la fenêtre, et d'une capacité pour charger une page Web désignée dans le navigateur intégré lorsque l'application développée sur la base de la page Web est démarrée ;

    la capacité pour stocker les données d'utilisateur en local comprenant le stockage des données d'utilisateur dans une base de données locale sous la forme d'une table bidimensionnelle ou d'un fichier indépendant.


     
    2. Procédé selon la revendication 1, comprenant en outre :
    fournir, par la plateforme d'applications, un marché d'applications à l'utilisateur du premier client pour sélectionner une application souhaitée.
     
    3. Procédé selon la revendication 1, comprenant en outre :
    obtenir, par la plateforme d'applications à partir du serveur, une liste d'applications, et afficher la liste d'applications avec une interface d'interaction.
     
    4. Procédé selon l'une quelconque des revendications 1 à 3, comprenant en outre :

    obtenir, par la plateforme d'applications, un premier message dynamique d'application à partir du serveur lorsque l'utilisateur se connecte, et afficher le premier message dynamique d'application ; le premier message dynamique d'application étant un message qui a déjà été envoyé à l'utilisateur par le serveur et n'est pas affiché ; et

    recevoir, par la plateforme d'applications pendant une période en ligne de l'utilisateur, un second message dynamique d'application à partir du serveur, et afficher le second message dynamique d'application ; le second message dynamique d'application étant un message qui est nouvellement généré et délivré par le serveur à l'utilisateur pendant la période en ligne de l'utilisateur.


     
    5. Procédé selon la revendication 4, dans lequel le premier message dynamique d'application ou le second message dynamique d'application comprend un identificateur, ID, de message, une manière d'afficher le message, un utilisateur cible, un ID d'application et des contenus de message.
     
    6. Plateforme d'applications, comprenant :

    un module de centre d'applications (51), pour installer, lorsque la plateforme d'applications est exécutée sur un premier client auquel est actuellement connecté un utilisateur, une première application lors de la réception d'une requête d'installation de la première application, ou pour désinstaller une deuxième application lors de la réception d'une requête de désinstallation de la deuxième application, ou installer, lorsque la plateforme d'applications est exécutée sur un second client auquel est connecté l'utilisateur après que l'utilisateur change de site de connexion, une troisième application selon un résumé de la troisième application stocké dans une liste d'applications, la liste d'applications étant conservée pour chaque utilisateur dans un serveur, et la liste d'applications étant conçue pour stocker des résumés de l'ensemble des applications installées par chaque utilisateur ;

    un module de gestion de liste (52), pour envoyer un résumé de la première application au serveur en vue d'un stockage correspondant à l'utilisateur envoyant la requête d'installation de la première application, ou pour notifier au serveur de supprimer un résumé de la deuxième application à partir de la liste d'applications correspondant à l'utilisateur envoyant la requête de désinstallation de la deuxième application, ou obtenir, à partir du serveur, la liste d'applications correspondant à l'utilisateur ;

    la première application, la deuxième application et la troisième application étant une même application ou des applications différentes ;

    le module de centre d'applications comprenant :

    un premier sous-module d'application (511), pour fournir des capacités d'installation et de désinstallation et un environnement d'exécution d'une application développée sur la base d'un langage de balisage extensible, XML, et d'un script ;

    un deuxième sous-module d'application (512), pour fournir des capacités d'installation et de désinstallation et un environnement d'exécution d'une application développée sur la base d'une bibliothèque de liens dynamiques, Dll, binaire ; et

    un troisième sous-module d'application (513), pour fournir des capacités d'installation et de désinstallation et un environnement d'exécution d'une application développée sur la base d'une page Web,

    caractérisée par le fait que

    le premier sous-module d'application (511) comprend une première unité d'affichage d'interface, une première unité de stockage, une première unité de réseau, une première unité d'authentification, une unité d'analyse et une unité d'interprétation ;

    le deuxième sous-module d'application (512) comprend une seconde unité d'affichage d'interface, une seconde unité de stockage, une seconde unité de réseau et une seconde unité d'authentification ; et

    le troisième sous-module d'application (513) comprend une unité de chargement ;

    la première unité d'affichage d'interface est conçue pour afficher une interface graphique de l'application développée sur la base du XML et du script ;

    la seconde unité d'affichage d'interface est conçue pour afficher une interface graphique de l'application développée sur la base de la Dll ;

    la première unité de stockage est conçue pour stocker des données d'utilisateur dans une base de données locale sous la forme d'une table bidimensionnelle ou d'un fichier indépendant ;

    la seconde unité de stockage est conçue pour stocker les données d'utilisateur dans la base de données locale sous la forme de la table bidimensionnelle ou du fichier indépendant ;

    la première unité de réseau est conçue pour fournir des prises en charge de divers protocoles de communication pour l'application développée sur la base du XML et du script, de telle sorte que ladite application a une capacité de communication réseau ;

    la seconde unité de réseau est conçue pour fournir les prises en charge des divers protocoles de communication pour l'application développée sur la base de la Dll, de telle sorte que ladite application a la capacité de communication réseau ;

    la première unité d'authentification est conçue pour fournir une capacité d'authentification de sécurité pour l'application développée sur la base du XML et du script ;

    la seconde unité d'authentification est conçue pour fournir la capacité d'authentification de sécurité pour l'application développée sur la base de la Dll ;

    l'unité d'analyse est conçue pour analyser le XML ;

    l'unité d'interprétation est conçue pour interpréter et exécuter le script ; et

    l'unité de chargement est conçue pour fournir une fenêtre d'interface, une commande de navigateur étant intégrée dans la fenêtre, et pour charger une page Web désignée dans le navigateur intégré lorsque l'application développée sur la base de la page Web est démarrée.


     
    7. Plateforme d'applications selon la revendication 6, comprenant en outre :
    un module de marché d'applications (53), pour fournir un marché d'applications à un utilisateur d'un client où se situe le module de marché d'applications pour sélectionner une application souhaitée.
     
    8. Plateforme d'applications selon la revendication 6, comprenant en outre :
    un module d'affichage d'applications (54), pour afficher une liste d'applications obtenue par la plateforme d'applications à partir du serveur avec une interface d'interaction.
     
    9. Plateforme d'applications selon l'une quelconque des revendications 6 à 8, comprenant en outre :

    un module de traitement de messages (55), pour obtenir un premier message dynamique d'application à partir du serveur lorsque l'utilisateur se connecte, et afficher le premier message dynamique d'application ; le premier message dynamique d'application étant un message qui a déjà été envoyé à l'utilisateur par le serveur et n'est pas affiché ; et

    pour recevoir, pendant une période en ligne de l'utilisateur, un second message dynamique d'application à partir du serveur, et pour afficher le second message dynamique d'application ; le second message dynamique d'application étant un message qui est nouvellement généré et délivré par le serveur à l'utilisateur pendant la période en ligne de l'utilisateur.


     
    10. Plateforme d'applications selon la revendication 9, dans laquelle le premier message dynamique d'application ou le second message dynamique d'application comprend un identificateur, ID, de message, une manière d'afficher le message, un utilisateur cible, un ID d'application et des contenus de message.
     




    Drawing














    Cited references

    REFERENCES CITED IN THE DESCRIPTION



    This list of references cited by the applicant is for the reader's convenience only. It does not form part of the European patent document. Even though great care has been taken in compiling the references, errors or omissions cannot be excluded and the EPO disclaims all liability in this regard.

    Patent documents cited in the description