(19)
(11)EP 2 876 913 B1

(12)EUROPEAN PATENT SPECIFICATION

(45)Mention of the grant of the patent:
22.07.2020 Bulletin 2020/30

(21)Application number: 14814661.6

(22)Date of filing:  06.08.2014
(51)International Patent Classification (IPC): 
H04W 8/08(2009.01)
H04W 4/00(2018.01)
(86)International application number:
PCT/CN2014/083791
(87)International publication number:
WO 2015/021875 (19.02.2015 Gazette  2015/07)

(54)

APPLICATION HOSTING METHOD AND SYSTEM, MOBILE TERMINAL AND SERVER

ANWENDUNGS-HOSTINGVERFAHREN UND -SYSTEM, MOBILES ENDGERÄT UND SERVER

PROCÉDÉ ET SYSTÈME D'HÉBERGEMENT D'APPLICATION, TERMINAL MOBILE ET SERVEUR


(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: 14.08.2013 CN 201310354128

(43)Date of publication of application:
27.05.2015 Bulletin 2015/22

(73)Proprietor: Huawei Technologies Co., Ltd.
Longgang District Shenzhen, Guangdong 518129 (CN)

(72)Inventors:
  • YANG, Fen
    Shenzhen Guangdong 518129 (CN)
  • XUE, Fanfan
    Shenzhen Guangdong 518129 (CN)

(74)Representative: Thun, Clemens 
Mitscherlich PartmbB Patent- und Rechtsanwälte Sonnenstraße 33
80331 München
80331 München (DE)


(56)References cited: : 
EP-A1- 2 523 109
CN-A- 102 752 327
CN-A- 103 428 671
WO-A1-2012/155937
CN-A- 102 752 327
US-A1- 2011 065 384
  
      
    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

    TECHNICAL FIELD



    [0001] The present invention relates to the communications field, and in particular, to an application takeover method and system, a mobile terminal, and a server.

    BACKGROUND



    [0002] Generally, various applications are installed on a user terminal, and applications installed on different terminals of a same user or on different terminals of different users are not completely the same. It is assumed that a user A needs to follow and operate an application A installed on a terminal A, but when the user A cannot continue to follow or operate the application A due to reasons such as a low battery of the terminal A, the user A may upload data of the application A to an application server, download, on a terminal B of a user B or the user A, the application A, log in to the application A on the terminal B by using a user name and a password of the application A, and acquire latest data of the application A from the application server, so as to continue to follow and operate the application A on the terminal B.

    [0003] Using the foregoing method needs to download and install a corresponding application on the terminal B. If the user A needs to follow multiple applications in this case, the multiple applications need to be installed on the terminal B, and subsequently accounts of all applications are used to log in to the multiple applications one by one. In this way, operations performed by a user are excessively complex, and time and traffic are consumed by downloading and installing multiple applications. In addition, these applications installed on the terminal B are very likely to be junk applications for the terminal B, which have a low utilization rate and occupy memory space.

    [0004] For example, US 2011/0065384 A1 refers to an approach for switching devices using near field communication by transferring services. A first device executes an online service. The first device initiates communication to a second device over a near field communication link during the execution of the online service to coordinate the transfer of information relating to the online service. The first device initiates the transfer of information relating to the online service to the second device for execution of the online service by the second device based on the communication.

    [0005] Further, CN 102752327 A refers to a method, system and device for performing interaction between terminals and a cloud server. As interaction progress information of an application interacting with a first terminal is recorded by the cloud server, after a handover request is acquired by the cloud server, the interaction can be continued according to the acquired identification information of a second terminal and the interaction progress information, thereby, the continuity of the application can be ensured, and moreover, the progress does not need to be sent to the first terminal again, and the application can be finished through the second terminal, thereby, resources of the terminals are saved, and moreover, the load of the cloud server is also relieved.

    SUMMARY



    [0006] In view of this, the present invention provides an application takeover method and system, a mobile terminal, and a server, so as to resolve problems that in a takeover process, an entrusted terminal needs to download a corresponding application, and time and traffic are consumed and memory space is occupied in an operation process; and also resolve a problem that a user needs to use, on the entrusted terminal, an account to log in to an application to be taken over, and an operation is excessively complex.

    [0007] In a first aspect an application takeover method performed by a system comprising a takeover server, a first terminal and a second terminal is provided, the method comprising:
    • sending, by the first terminal, an application takeover request to the second terminal;
    • receiving, by the first terminal, a takeover accept response from the second terminal;
    • after the reception of the takeover accept response by the first terminal, receiving, by the takeover server, an application takeover instruction sent by the first terminal, wherein the application takeover instruction comprises information about an application, stored on the first terminal, to be taken over, and an identifier of the second terminal, wherein the application takeover instruction is used to make the application of the first terminal be taken over by the second terminal, wherein the second terminal does not store the application;
    • establishing, by the takeover server, a takeover correspondence between the first terminal and the second terminal according to the application takeover instruction;
    • acquiring, by the takeover server, according to the information that is about the application, dynamic information of the application and operating information corresponding to the dynamic information;
    • sending, by the takeover server, based on the identifier of the second terminal the dynamic information of the application and the corresponding operating information to the second terminal.


    [0008] In a first implementation form of the first aspect, after the sending, by the takeover server, of the dynamic information of the application and the operating information reception to the second terminal, the method further comprises:

    receiving, by the second terminal, the dynamic information of the application and the operating information corresponding to the dynamic information;

    determining, by the second terminal, an operating instruction according to the dynamic information and the operating information; and

    sending, by the second terminal, the operating instruction comprising the identifier of the second terminal to the takeover server.



    [0009] In a second implementation form of the first aspect, after the sending, by the second terminal, the operating instruction comprising the identifier of the second terminal to the takeover server, further comprising:

    receiving, by the takeover server, the operating instruction comprising the identifier of the second terminal; and

    performing, by the takeover server, authentication on the second terminal according to the identifier of the second terminal and the takeover correspondence, and if the authentication succeeds, executing the operating instruction; and

    if the authentication fails, skipping, by the takeover server, the execution of the operating instruction.



    [0010] In a third implementation form of the first aspect, after the receiving, by the takeover server, the application takeover instruction sent by the first terminal, further comprising:
    receiving, by the takeover server, an application takeover cancel instruction sent by the first terminal.

    [0011] In a second aspect a system comprising a takeover server, a first terminal and a second terminal is provided, wherein the system is configured to perform any of the above methods.

    [0012] According to the technical solutions of the embodiments of the present invention, a first terminal makes an application A be taken over by a second terminal; after receiving a takeover instruction and during takeover, a server of the application A sends dynamic information of the application A of a user of the first terminal and corresponding operating information to the second terminal, and executes a corresponding operation according to an operating instruction of the second terminal, so that when the first terminal is unavailable, the second terminal may receive the dynamic information of the application A of the user of the first terminal, and send the corresponding operating instruction to the server of the application A.

    [0013] According to the application takeover method and system, the mobile terminal, and the server provided by the embodiments of the present invention, a takeover correspondence between terminals is established on a server side; therefore, a user may conveniently receive, on another terminal, dynamic information of an application that is taken over and corresponding operating information. Even if another terminal takes over multiple applications, any of the applications that are taken over does not need to be installed on the another terminal, and only dynamic information and operating information that are sent by a server needs to be received, which greatly rcduccs consumed time and traffic. Therefore, problems that, in the prior art, in a takeover process, a terminal needs to download an application to be taken over, and time and traffic are consumed and memory space is occupied in an operation process are resolved; and a problem that, in a process of implementing takeover, a user needs to use accounts of multiple applications to log in one by one on the entrusted terminal, and an operation is excessively complex is also resolved.

    BRIEF DESCRIPTION OF DRAWINGS



    [0014] The accompanying drawings included in the specification and constituting a part of the specification and the specification illustrate exemplary embodiments, features, and aspects of the present invention, and are used for explaining principles of the present invention.

    FIG. 1 is a flowchart of an application takeover method according to an embodiment of the present invention;

    FIG. 2 is a flowchart of an application takeover method according to another embodiment of the present invention;

    FIG. 3 is a flowchart of an application takeover requesting method according to an embodiment of the present invention;

    FIG. 4 is a flowchart of an application takeover method according to still another embodiment of the present invention;

    FIG. 5a is a schematic diagram of selecting an application to be taken over;

    FIG. 5b is a schematic diagram of a second terminal list;

    FIG. 5c is a schematic diagram of a takeover application request;

    FIG. 5d is a schematic diagram of a takeover accept response;

    FIG. 5e is a schematic diagram of sending an application takeover instruction;

    FIG. 5f is a schematic diagram of sending operating information;

    FIG. 6 is a flowchart of an application takeover method according to yet another embodiment of the present invention;

    FIG. 7 is a schematic structural diagram of a server according to an embodiment of the present invention;

    FIG. 8 is a schematic structural diagram of a server according to another embodiment of the present invention;

    FIG. 9 is a schematic structural diagram of a mobile terminal according to an embodiment of the present invention;

    FIG. 10 is a schematic structural diagram of a mobile terminal according to another embodiment of the present invention;

    FIG. 11 is a schematic structural diagram of an application takeover system according to an embodiment of the present invention; and

    FIG. 12 is a structural block diagram of a network device according to another embodiment of the present invention.


    DESCRIPTION OF EMBODIMENTS



    [0015] Various exemplary embodiments, features, and aspects of the present invention are described in detail in the following with reference to the accompanying drawings. In the accompanying drawings, identical reference numerals denote elements that have an identical or similar function. Although various aspects of the embodiments are shown in the accompanying drawings, unless otherwise specified, the accompanying drawings are not necessarily drawn to scale.

    [0016] The special term "exemplary" herein refers to "can be used as an example, an embodiment, or an illustration". Any embodiment described as "exemplary" herein is not necessarily to be interpreted as optimal or better than other embodiments.

    [0017] In addition, to better describe the present invention, many details are given in the following specific implementation manners. A person skilled in the art shall understand that the present invention may still be implemented even without such details. In other instances, well-known methods, means, elements, and circuits are not described in detail, so as to highlight the subject of the present invention.

    Embodiment 1



    [0018] As shown in FIG. 1, FIG. 1 is a flowchart of an application takeover method according to an embodiment of the present invention. The method mainly includes the following steps:
    S110: A server receives an application takeover instruction sent by a first terminal.

    [0019] The application takeover instruction includes an identifier of a second terminal and information about an application, of the first terminal, to be taken over. The information about the application may include an identifier of the application, and information about a user account of the application, such as a user name and a password.

    [0020] S120: The server establishes a takeover correspondence between the first terminal and a second terminal according to the received application takeover instruction, and stores the takeover correspondence.

    Embodiment 2



    [0021] As shown in FIG. 2, FIG. 2 is a flowchart of an application takeover method according to another embodiment of the present invention. The method mainly includes the following steps:
    S210: A server receives an application takeover instruction sent by a first terminal.

    [0022] The application takeover instruction includes an identifier of a second terminal where an application is to be taken over and information about the application, of the first terminal, to be taken over.

    [0023] S220: The server establishes a takeover correspondence between the first terminal and a second terminal according to the application takeover instruction.

    [0024] In this step, the server establishes and stores the takeover correspondence between an entrusting party being the first terminal and an entrusted party being the second terminal.

    [0025] S230: The server detects dynamic information of the application and operating information corresponding to the dynamic information.

    [0026] Specifically, the server detects, according to an identifier of the application and information about a user account that are in the application takeover instruction, the dynamic information of the application corresponding to the user account and the operating information corresponding to the dynamic information.

    [0027] S240: The server sends the dynamic information of the application and the corresponding operating information to the second terminal.

    [0028] The dynamic information and the operating information may be information such as a notification or a piece of news that does not need a reply from the second terminal. In this case, the second terminal does not need to respond. The dynamic information and the operating information may also be information such as adding a friend or whether to perform upgrading, which needs the second terminal to reply. In this case, this embodiment may further include the following steps:
    S250: The server receives an operating instruction sent by the second terminal.

    [0029] The operating instruction is generated by the second terminal based on the dynamic information and the operating information, where the operating instruction may include the identifier of the second terminal.

    [0030] S260: The server performs authentication on the second terminal.

    [0031] Specifically, the server performs legality and validity authentication on the second terminal according to the established takeover correspondence and the identifier of the second terminal. If the authentication succeeds, S270 is executed; if the authentication fails, S280 is executed.

    [0032] S270: The server executes the operating instruction.

    [0033] S280: The server does not execute the operating instruction.

    [0034] Further, the method provided by this embodiment may further include:
    S290: The server receives an application takeover cancel instruction sent by the first terminal.

    [0035] When a user determines that the second terminal does not need to be used to manage the application any longer, the application takeover cancel instruction may be sent to the server, and the server does not send the dynamic information and the operating information that are of the application to the second terminal any longer, so that occupation of memory of the second terminal is stopped in a timely manner.

    [0036] In a possible implementation manner, in a case in which the first terminal cannot be used because the user forgets to carry the first terminal, power of the first terminal is used up, or the like, the user may access, by using a PC, a Web client that manages the first terminal, to perform application takeover according to the present invention.

    [0037] In conclusion, according to the technical solutions provided by this embodiment of the present invention, a server establishes a takeover correspondence between a first terminal and a second terminal according to an application takeover instruction sent by the first terminal; and when detecting dynamic information and operating information that are of an application, sends the dynamic information and the operating information to the second terminal. Therefore, a user may conveniently manage, on at least one second terminal, the application. Even if the second terminal takes over multiple applications, any of the applications that are taken over does not need to be installed on the second terminal, so that time and traffic consumed by changing a terminal to operate an application are greatly reduced, and an operation is convenient and easy.

    Embodiment 3



    [0038] As shown in FIG. 3, FIG. 3 is a flowchart of an application takeover requesting method according to an embodiment of the present invention. The method mainly includes the following steps:
    S310: A first terminal sends an application takeover request to a second terminal.

    [0039] The application takeover request includes an identifier of the first terminal and an identifier of an application, of the first terminal, to be taken over, where the identifier of the first terminal may be information that can uniquely recognize an identity of the first terminal, such as a mobile number and an Imei number of the first terminal; the identifier of the application may be a name of the application, or the like.

    [0040] S320: The first terminal receives a takeover response returned by the second terminal.

    [0041] The takeover response may indicate that the takeover is accepted, refused or ignored. If the second terminal returns a takeover accept response, S330 is executed; if the second terminal returns a takeover refuse response or a takeover ignore response, the process ends.

    [0042] S330: The first terminal sends an application takeover instruction to a server, where the application takeover instruction includes an identifier of the second terminal and information about the application.

    [0043] The server establishes a takeover correspondence between the first terminal and the second terminal after receiving the application takeover instruction, so as to enable the second terminal to manage the application. If the server detects, during the takeover, dynamic information of the application and corresponding operating information, the server sends the detected information to the second terminal. Therefore, the method may further include the following steps:

    S340: The second terminal receives dynamic information of the application and operating information corresponding to the dynamic information that are sent by the server.

    S350: The second terminal determines an operating instruction according to the received dynamic information and operating information.

    S360: The second terminal sends the operating instruction including the identifier of the second terminal to the server.



    [0044] Preferably, before the first terminal sends the application takeover request to the second terminal, the method further includes the following steps:
    S300: The first terminal determines the application to be taken over and the second terminal.

    [0045] Specifically, the first terminal may determine, by using a technology such as Bluetooth, infrared, Push, Near Field Communication (NFC), shaking, or mobile phone touching, a list of terminals where the application is to be taken over, obtain an identifier of each terminal in the list, and then select at least one terminal from the list to serve as the second terminal to take over the application.

    Embodiment 4



    [0046] As shown in FIG. 4, FIG. 4 is a flowchart of an application takeover method according to still another embodiment of the present invention. The method mainly includes the following steps:
    S411: A first terminal selects an application that needs to be taken over and a second terminal.

    [0047] Specifically, multiple application programs may be installed on the first terminal. However, a user may not need to follow or operate all the applications while the user is not using the first terminal. Therefore, the first terminal first needs to select one or more applications that need to be taken over. With reference to FIG. 5a, in this embodiment, description is provided by using an example in which one application, such as Happy Farm, is taken over, which may be implemented by adding "Happy Farm" to a "takeover center".

    [0048] The first terminal may determine a terminal list by using a technology such as Bluetooth, infrared, Push, NFC, shaking, or mobile phone touching, acquire an identifier of each terminal in the list, and select at least one second terminal from the list to take over the application. With reference to FIG. 5b, the terminal list is displayed on the first terminal, and the first terminal selects the second terminal by selecting an "add" operation.

    [0049] S412: The first terminal sends an application takeover request to the second terminal.

    [0050] In this step, the application takeover request needs to include at least: an identifier of the first terminal and an identifier of the application to be taken over. The identifier of the first terminal may be information that can uniquely recognize an identity of the first terminal, such as a mobile number, an Imei number, an alias, or a label of the first terminal; the identifier of the application may be a name of the application, or the like. With reference to FIG. 5c, the application takeover request that is sent by the first terminal to the second terminal includes the identifier "first terminal" of the first terminal, and the identifier "Happy Farm" of the application.

    [0051] S413: The first terminal receives a takeover response returned by the second terminal.

    [0052] If the second terminal agrees to perform takeover, step S414 is executed; if the second terminal returns a takeover refuse response or a takeover ignore response, the process ends.

    [0053] Specifically, after receiving the takeover request, the second terminal makes a response according to a choice of a user of the second terminal, where the response may be that the takeover is accepted, refused, or ignored, and sends the corresponding takeover response to the first terminal. The first terminal receives the takeover response. With reference to FIG. 5d, the second terminal returns a takeover accept response, where the response may further include information "You may send 'tuoguan' to the SMS platform '1065×××' to start takeover", which prompts the first terminal to perform a next operation for the takeover.

    [0054] S414: The first terminal sends an application takeover instruction to a server.

    [0055] The application takeover instruction includes at least an identifier of the second terminal and information about the application, of the first terminal, to be taken over. The first terminal sends the instruction to a Happy Farm server to instruct the Happy Farm server to make Happy Farm of a user of the first terminal be taken over by the second terminal; and during the takeover, dynamic information of Happy Farm and corresponding operating information may be sent to the second terminal. The application takeover instruction may further include identifier of the application, and information about a user account, such as a user name and a login password. With reference to FIG. 5e, the first terminal sends the application takeover instruction to the Happy Farm server according to a prompt in the takeover response.

    [0056] S415: The server establishes a takeover correspondence between the first terminal and the second terminal according to the application takeover instruction.

    [0057] S416: The server detects dynamic information of the application and extracts operating information corresponding to the dynamic information.

    [0058] S417: The server sends the dynamic information of the application and the operating information to the second terminal.

    [0059] In this step, during the takeover, that is, before the first terminal sends a takeover cancel instruction to the server, if the server detects the dynamic information of the application and the corresponding operating information, the server sends the detected information to the second terminal. With reference to FIG. 5f, the second terminal receives the dynamic information "Vegetables in the garden of 'nono' are all ripe, come and pick them" of Happy Farm and the corresponding operating information "Return 009 to perform one-key picking" that are sent by the Happy Farm server.

    [0060] S418: The second terminal sends a selected operating instruction to the server.

    [0061] The second terminal sends, according to a choice of the user, a specific operating instruction to the Happy Farm server. Further, the operating instruction may also carry the identifier of the second terminal, where the identifier is used for authentication. For example, the second terminal may send "009" to the Happy Farm server.

    [0062] In some cases, when the dynamic information sent by the server to the second terminal is information such as a notification or a piece of news, the second terminal does not need to reply with the operating instruction.

    [0063] S419: The server performs authentication on the second terminal.

    [0064] The Happy Farm server receives the operating instruction of the second terminal, and performs legality and validity authentication on the second terminal according to the identifier of the second terminal and the stored takeover correspondence. If the authentication succeeds, step S420 is executed; if the authentication fails, step S421 is executed.

    [0065] S420: The server performs a corresponding operation according to the operating instruction.

    [0066] For example, the Happy Farm server performs one-key picking on the ripe vegetables of Happy Farm whose user name is nono.

    [0067] S421: Skip executing the operating instruction. This step is not illustrated in the figure.

    [0068] S422: The first terminal sends a takeover cancel instruction to the server.

    [0069] When the user determines that the second terminal does not need to be used to operate Happy Farm any longer, an application takeover cancel instruction may be sent to the Happy Farm server, and the Happy Farm server may delete the takeover correspondence, and does not send the dynamic information and the operating information that are of the application to the second terminal any longer, so that occupation of memory of the second terminal is stopped in a timely manner. Specifically, the user may cancel takeover of the application by removing the application from the "takeover center".

    [0070] It should be noted that, for descriptions of a form of communication between the first terminal, the second terminal, and the server in FIG. 5a to FIG. 5f, an SMS message is used as an example. For example, the first terminal may send the application takeover request to the second terminal by using an SMS message, and the second terminal may also send the takeover response to the first terminal by using an SMS message. The SMS message may include different operation code that can be returned, so that a receiving end can make a choice.

    [0071] To implement communication between the first terminal and the second terminal by using an SMS message method, a mobile number of the second terminal needs to be learned. Specifically:
    The first terminal may determine the mobile number of the second terminal by using a Push technology, where the mobile number of the second terminal can be acquired when a connection is established between the first terminal and a Push server.

    [0072] For the first terminal, the mobile number of the second terminal may further be manually input or loaded from an address book.

    [0073] If the second terminal is determined in a Bluetooth or infrared manner, the user of the first terminal needs to manually input, or load from the address book, the mobile number of the second terminal user after determining the application to be taken over and the second terminal, so that the first terminal sends the application takeover request to the second terminal by using an SMS message.

    [0074] In addition, in a process in which the first terminal sends the application takeover request to the second terminal by using an SMS message, the second terminal also acquires a mobile number of the first terminal, so that the second terminal may return a takeover response by using the mobile number.

    [0075] The technical solutions provided by this embodiment of the present invention resolve problems that in a process in which a second terminal takes over an application, the second terminal needs to download the application to be taken over, and time and traffic are consumed and memory space is occupied in an operation process; and also resolve a problem that in a process in which the second terminal takes over an application, a user needs to use accounts and passwords to log in to corresponding applications on the second terminal one by one, and an operation is excessively complex.

    Embodiment 5



    [0076] As shown in FIG. 6, FIG. 6 is a flowchart of an application takeover method according to yet another embodiment of the present invention. This embodiment is described by using an example in which an application is taken over based on a Push technology. The method mainly includes the following steps:
    S511: A first terminal sends a terminal list search request to a Push server.

    [0077] Request parameters of the second terminal list search request may include: an identifier of an application user, an identifier of an application, a takeover request command word, and an identifier of an entrusted terminal, such as a mobile number, an Imei number, an alias, a label, or another device identifier.

    [0078] S512: The Push server extracts a terminal list.

    [0079] Specifically, the Push server performs authentication on legality of the identifier of the application user, the identifier of the application, the takeover request command, and the like. If the authentication succeeds, the Push server finds, according to the identifier of the entrusted terminal, the terminal list of terminals that may be entrusted, where a Push agent (Push agent) is installed on the terminals of the found terminal list.

    [0080] S513: The Push server sends the found terminal list to the first terminal.

    [0081] Specifically, the Push server sends the terminal list found in step S512 to the first terminal, where the terminal list includes 0 to multiple eligible terminals, and identifiers of all the terminals.

    [0082] S514: The first terminal sends an application takeover request to a second terminal by using the Push server.

    [0083] The first terminal selects the second terminal that is used for takeover the application from the terminal list, and sends an identifier of the selected second terminal to the Push server. The first terminal may select one or more second terminals. The Push server performs authentication on the application takeover request, and after the authentication succeeds, sends the application takeover request to the second terminal. The application takeover request includes the identifier of the application and an identifier of the first terminal.

    [0084] S515: The second terminal returns a takeover response to the first terminal by using the Push server.

    [0085] The second terminal performs authentication on the takeover request. After the authentication succeeds, the second terminal returns the takeover response to the first terminal by using the Push server. This embodiment is described by using an example in which a takeover accept response is returned. In a case in which the second terminal accepts the takeover, step S517 is executed.

    [0086] S516: The first terminal sends an application takeover instruction to an application server.

    [0087] The application takeover instruction includes at least an identifier of the second terminal and information about the application, of the first terminal, to be taken over. The information about the application may include the identifier of the application, and information about a user account such as a login password of a user.

    [0088] S517: The application server establishes a takeover correspondence between the first terminal and the second terminal according to the application takeover instruction.

    [0089] S518: The application server detects dynamic information of the application and extracts operating information corresponding to the dynamic information.

    [0090] The application server may perform authentication on the application takeover instruction. After the authentication succeeds, the dynamic information of the application is detected and the operating information corresponding to the dynamic information is extracted.

    [0091] S519: The application server sends the dynamic information and the operating information that are of the application to the second terminal by using the Push server.

    [0092] The Push server may perform authentication on the operating information, and after the authentication succeeds, send the dynamic information and the operating information that are of the application to the second terminal.

    [0093] Further, in step S519, the application server may further send the identifier of the second terminal and an address of the application server to the Push server at the same time, and then the identifier of the second terminal and an address of the application server are sent to the second terminal by using the Push server.

    [0094] S520: The second terminal sends a selected operating instruction to the application server by using the Push server.

    [0095] Further, the identifier of the second terminal may be sent to the application server at the same time for authentication.

    [0096] S521: The application server performs authentication on the second terminal according to the identifier of the second terminal and the takeover correspondence, and if the authentication succeeds, executes a corresponding operation according to the operating instruction.

    [0097] S522: The first terminal sends an application takeover cancel instruction to the application server.

    [0098] When the user determines that the second terminal does not need to be used to operate the application any longer, the application takeover cancel instruction may be sent to the application server, and the application server does not send the dynamic information and the operating information that are of the application to the second terminal any longer, so that occupation of memory of the second terminal is stopped in a timely manner.

    [0099] In addition, in order to ensure security of the second terminal, a sending process from step S519 to step S520 may be performed by using the HTTPS. In addition, the application server may allocate one authorization identifier to the second terminal, where the authorization identifier is used as an authentication identifier of the second terminal and used for authentication in a subsequent process. Therefore, information such as an identifier number of the second terminal does not need to be transmitted, thereby ensuring the security of the second terminal.

    [0100] It should be noted that, a method for acquiring the identifier of the second terminal is not limited to the Push technology described in the foregoing embodiment, and may include manners such as Bluetooth, infrared, near field communication, shaking, and mobile phone touching, or a mobile number of the second terminal is directly acquired.

    [0101] The identifier of the second terminal acquired by using the foregoing methods may uniquely recognize the second terminal, and the identifier number may be used for a subsequent takeover request and takeover response, and a processing process of the application.

    Embodiment 6



    [0102] As shown in FIG. 7, FIG. 7 is a schematic structural diagram of a server according to an embodiment of the present invention. The server 10 includes: a first receiving module 101 and a correspondence establishing module 102.

    [0103] The first receiving module 101 is configured to receive an application takeover instruction sent by a first terminal, where the application takeover instruction includes at least an identifier of a second terminal and information about an application, of the first terminal, to be taken over, the application takeover instruction is used to make the application of the first terminal be taken over by the second terminal, and the application takeover instruction is generated by the first terminal based on sending an application takeover request to the second terminal and receiving a takeover accept response returned by the second terminal. The information about the application may include an identifier of the application, and information about a user account of the application, such as a user name and a password.

    [0104] The correspondence establishing module 102 is connected to the first receiving module 101, and configured to establish a takeover correspondence between the first terminal and the second terminal according to the application takeover instruction.

    [0105] As shown in FIG. 8, in an exemplary implementation manner, the server 10 further includes: an acquiring module 103, a first sending module 104, an authenticating module 105, and an executing module 106.

    [0106] The acquiring module 103 is connected to the first receiving module 101, and configured to acquire, according to the information that is about the application and in the application takeover instruction, dynamic information of the application and operating information corresponding to the dynamic information. Specifically, after the correspondence establishing module 102 of the server 10 establishes the takeover correspondence between the first terminal and the second terminal, the acquiring module 103, according to the identifier of the application carried in the application takeover instruction, detects the dynamic information of the application and extracts the corresponding operating information.

    [0107] The first sending module 104 is connected to the first receiving module 101 and the acquiring module 103, and configured to send the dynamic information of the application and the operating information corresponding to the dynamic information to the second terminal according to the identifier of the second terminal, so as to enable the second terminal to manage the application.

    [0108] Further, the first receiving module 101 is further configured to receive an operating instruction sent by the second terminal and including the identifier of the second terminal; the authenticating module 105 is connected to the first receiving module 101, and configured to perform legality and validity authentication on the second terminal according to the identifier of the second terminal and the established and stored takeover correspondence. The executing module 106 is connected to the authenticating module 105, and configured to, when the authentication succeeds, execute the operating instruction from the second terminal.

    [0109] In addition, when the first terminal does not need to make the application be taken over by the second terminal, the first receiving module 101 is further configured to receive an application takeover cancel instruction sent by the first terminal.

    [0110] In conclusion, according to the technical solutions in this embodiment of the present invention, a user may conveniently receive, on a second terminal, dynamic information of an application to be taken over and corresponding operating information. In addition, even if the second terminal receives takeover requests of multiple applications, any of the applications to be taken over does not need to be installed on the second terminal, any of the applications to be taken over does not need to be installed on other terminal either, and only dynamic information and operating information that are sent by a server need to be received, which greatly reduces consumed time and traffic. Therefore, problems that, in the prior art, in a takeover process, a second terminal needs to download multiple application programs to be taken over, and time and traffic are consumed and memory space is occupied in an operation process are resolved; and a problem that, in a process in which a second terminal performs takeover, a user needs to use accounts of multiple application programs to log in one by one on the entrusted terminal, and an operation is excessively complex is also resolved.

    Embodiment 7



    [0111] As shown in FIG. 9, FIG. 9 is a schematic structural diagram of a mobile terminal according to an embodiment of the present invention. A mobile terminal 20 is the first terminal in the foregoing embodiments, and includes a second sending module 201 and a second receiving module 202.

    [0112] The second sending module 201 is configured to send an application takeover request to a second terminal, where the application takeover request includes an identifier of the mobile terminal 20 and an identifier of an application, of the mobile terminal 20, to be taken over; and further configured to send an application takeover instruction to a server when the second receiving module 202 receives a takeover accept response returned by the second terminal, where the application takeover instruction is used to instruct the server to make the application be taken over by the second terminal, and the identifier of the mobile terminal may be information that can uniquely recognize an identity of the mobile terminal, such as a mobile number and an Imei number of the mobile terminal; the identifier of the application may be a name of the application, or the like. The application takeover instruction includes an identifier of the second terminal and information about the application.

    [0113] The second receiving module 202 is configured to receive a takeover response returned by the second terminal. Specifically, after receiving the application takeover request, the second terminal makes, according to a choice of a user, a takeover response of accepting, refusing or ignoring, and sends the takeover response to the first terminal, and then the takeover response is received by the second receiving module 202.

    [0114] As shown in FIG. 10, in an exemplary implementation manner, the mobile terminal 20 further includes: an operating instruction determining module 203, which is connected to the second receiving module 202, and configured to determine the application to be taken over and the second terminal. The second sending module 201 is further connected to the operating instruction determining module 203, and is further configured to send an operating instruction including the identifier of the second terminal to the server.

    [0115] Further, the mobile terminal 20 may further include an application determining module 204, which is connected to the second sending module 201, and configured to determine the application to be taken over and the second terminal. The application determining module 204 determines a terminal list specifically by using Bluetooth, infrared, Push, NFC, a shaking technology or a mobile phone touching technology, and selects at least one terminal from the list to serve as the second terminal.

    [0116] Preferably, the second sending module 201 is further configured to send an application takeover cancel instruction to the server. An application program may be canceled by using a method of dragging the application program out of a "takeover center".

    [0117] Manners in which the second sending module 201 and the second receiving module 202 communicate with another mobile terminal include Push, SMS message, Email, and the like; and manners in which the second sending module 201 and the second receiving module 202 communicate with the server include a Push technology, SMS message, Email, and the like.

    [0118] It is assumed that a user has multiple terminals with multiple applications installed on, and when the user goes out the user still needs to follow multiple applications, according to the method and apparatus provided by the present invention, the user does not need to carry the multiple terminals, but only needs to select one terminal to serve as an entrusted party and to make the applications that need to be followed be taken over by the entrusted terminal, which greatly improves portability of a user operation.

    [0119] In a case in which a user goes out and a terminal does not have enough power and cannot be charged, an application on the terminal may be taken over by a terminal of a companion, and dynamic information and operating information that are of the application are received by using the terminal of the companion.

    [0120] In a case in which the user forgets to carry the terminal or the terminal does not have enough power and cannot be charged, the user may log in to a Web client that manages the terminal to perform application takeover.

    Embodiment 8



    [0121] As shown in FIG. 11, FIG. 11 is a schematic structural diagram of an application program takeover system according to an embodiment of the present invention. A takeover system 300 includes the server 10 in Embodiment 6 and the mobile terminal 20 in Embodiment 7, and further includes the second terminal 30 in the foregoing embodiments.

    Embodiment 9



    [0122] FIG. 12 is a structural block diagram of a network device according to another embodiment of the present invention. A network device 1100 may be a host server, a personal computer PC, a carriable portable computer, or a terminal that has a computing capability. A specific implementation of a computing node is not limited in this embodiment of the present invention.

    [0123] The network device 1100 includes a processor (processor) 1110, a communications interface (Communications Interface) 1120, a memory (memory array) 1130, and a bus 1140. The processor 1110, the communications interface 1120, and the memory 1130 communicate with each other through the bus 1140.

    [0124] The communications interface 1120 is configured to communicate with a network element, where the network element includes a virtual machine management center, a shared memory, and the like.

    [0125] The processor 1110 is configured to execute a program. The processor 1110 may be a central processing unit CPU, or an Application-specific Integrated Circuit (ASIC), or be configured to be one or more integrated circuits that implement this embodiment of the present invention.

    [0126] The memory 1130 is configured to store a file. The memory 1130 may include a high speed RAM memory, and may also include a non-volatile memory (non-volatile memory), for example, at least one magnetic disk memory. The memory 1130 may also be a memory array. The memory 1130 may also be divided into blocks, and the blocks may be combined to form a virtual volume according to a specific rule.

    [0127] In a possible implementation manner, the foregoing program may be program code including a computer operating instruction. The program may be specifically used for:

    receiving, by a server, an application takeover instruction sent by a first terminal, where the application takeover instruction includes an identifier of a second terminal and information about an application, of the first terminal, to be taken over, the application takeover instruction is used to make the application of the first terminal be taken over by the second terminal, and the application takeover instruction is generated by the first terminal based on sending an application takeover request to the second terminal and receiving a takeover accept response returned by the second terminal; and

    establishing, by the server, a takeover correspondence between the first terminal and the second terminal according to the application takeover instruction.



    [0128] In a possible implementation manner, after the establishing, by the server, a takeover correspondence between the first terminal and the second terminal according to the application takeover instruction, the following is further included:

    acquiring, by the server according to the information that is about the application and in the application takeover instruction, dynamic information of the application and operating information corresponding to the dynamic information; and

    sending, by the server, the dynamic information of the application and the operating information corresponding to the dynamic information to the second terminal according to the identifier of the second terminal, so as to enable the second terminal to manage the application.



    [0129] In a possible implementation manner, the enabling the second terminal to manage the application specifically includes:

    receiving, by the second terminal, the dynamic information of the application and the operating information corresponding to the dynamic information;

    determining, by the second terminal, an operating instruction according to the dynamic information and the operating information; and

    sending, by the second terminal, the operating instruction including the identifier of the second terminal to the server.



    [0130] In a possible implementation manner, after the sending, by the second terminal, the operating instruction including the identifier of the second terminal to the server, the following is further included:

    receiving, by the server, the operating instruction including the identifier of the second terminal; and

    performing, by the server, authentication on the second terminal according to the identifier of the second terminal and the application takeover correspondence, and if the authentication succeeds, executing the operating instruction; and

    if the authentication fails, skipping executing the operating instruction.



    [0131] In a possible implementation manner, after the receiving, by a server, an application takeover instruction sent by a first terminal, the following is further included:
    receiving, by the server, an application takeover cancel instruction sent by the first terminal.

    [0132] According to the technical solutions in this embodiment of the present invention, a user may conveniently receive, on a second terminal, dynamic information of an application to be taken over and corresponding operating information. In addition, even if the second terminal receives takeover requests of multiple applications, any of the applications to be taken over does not need to be installed on the second terminal, any of the applications to be taken over does not need to be installed on other terminal either, and only dynamic information and operating information that are sent by a server need to be received, which greatly reduces consumed time and traffic. Therefore, problems that, in the prior art, in a takeover process, a second terminal needs to download multiple application programs to be taken over, and time and traffic are consumed and memory space is occupied in an operation process are resolved; and a problem that, in a process in which a second terminal performs takeover, a user needs to use accounts of multiple application programs to log in one by one on the entrusted terminal, and an operation is excessively complex is also resolved.

    [0133] With descriptions of the foregoing embodiments, a person skilled in the art may clearly understand that the present invention may be implemented by hardware, firmware or a combination thereof. When the present invention is implemented by software, the foregoing functions may be stored in a computer-readable medium or transmitted as one or more instructions or code in the computer-readable medium. The computer-readable medium includes a computer storage medium and a communications medium, where the communications medium includes any medium that enables a computer program to be transmitted from one place to another. The storage medium may be any available medium accessible to a computer. The following provides an example but does not impose a limitation: The computer-readable medium may include a RAM, a ROM, an EEPROM, a CD-ROM, or another optical disc storage or disk storage medium, or another magnetic storage device, or any other medium that can carry or store expected program code in a form of an instruction or a data structure and can be accessed by a computer. In addition, any connection may be properly defined as a computer-readable medium. For example, if software is transmitted from a website, a server or another remote source by using a coaxial cable, an optical fiber cable, a twisted pair, a digital subscriber line (DSL) or wireless technologies such as infrared ray, radio and microwave, the coaxial cable, optical fiber cable, twisted pair, DSL or wireless technologies such as infrared ray, radio and microwave are included in fixation of a medium to which they belong. For example, a disk (Disk) and disc (disc) used by the present invention includes a compact disc CD, a laser disc, an optical disc, a digital versatile disc (DVD), a floppy disk and a Blue-ray disc, where the disk generally copies data by a magnetic means, and the disc copies data optically by a laser means. The foregoing combination should also be included in the protection scope of the computer-readable medium.

    [0134] The foregoing descriptions are merely specific implementation manners of the present invention, but are not intended to limit the protection scope of the present invention. Any variation or replacement readily figured out by a person skilled in the art within the technical scope disclosed in the present invention shall fall within the protection scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.


    Claims

    1. An application takeover method performed by a system comprising a takeover server, a first terminal and a second terminal, the method comprising:

    • sending, by the first terminal, an application takeover request to the second terminal;

    • receiving, by the first terminal, a takeover accept response from the second terminal;

    • after the reception of the takeover accept response by the first terminal, receiving, by the takeover server, an application takeover instruction sent by the first terminal, wherein the application takeover instruction comprises information about an application, stored on the first terminal, to be taken over, and an identifier of the second terminal, wherein the application takeover instruction is used to make the application of the first terminal be taken over by the second terminal, wherein the second terminal does not store the application (S210);

    • establishing, by the takeover server, a takeover correspondence between the first terminal and the second terminal according to the application takeover instruction (S220);

    • acquiring, by the takeover server, according to the information that is about the application, dynamic information of the application and operating information corresponding to the dynamic information;

    • sending, by the takeover server, based on the identifier of the second terminal the dynamic information of the application and the corresponding operating information to the second terminal (S240).


     
    2. The application takeover method according to claim 1, wherein after the sending, by the takeover server, of the dynamic information of the application and the operating information reception to the second terminal, the method further comprises:

    receiving, by the second terminal, the dynamic information of the application and the operating information corresponding to the dynamic information;

    determining, by the second terminal, an operating instruction according to the dynamic information and the operating information; and

    sending, by the second terminal, the operating instruction comprising the identifier of the second terminal to the takeover server.


     
    3. The application takeover method according to claim 2, after the sending, by the second terminal, the operating instruction comprising the identifier of the second terminal to the takeover server, further comprising:

    receiving, by the takeover server, the operating instruction comprising the identifier of the second terminal; and

    performing, by the takeover server, authentication on the second terminal according to the identifier of the second terminal and the takeover correspondence, and if the authentication succeeds, executing the operating instruction; and

    if the authentication fails, skipping, by the takeover server, the execution of the operating instruction.


     
    4. The application takeover method according to any of claims 1 - 3, wherein after the receiving, by the takeover server, the application takeover instruction sent by the first terminal, further comprising:
    receiving, by the takeover server, an application takeover cancel instruction sent by the first terminal.
     
    5. A system comprising a takeover server, a first terminal and a second terminal, wherein the system is configured to perform any of the methods according to claims 1 - 4.
     


    Ansprüche

    1. Anwendungs-Übernahmeverfahren, das durch ein System ausgeführt wird, das einen Übernahme-Server, ein erstes Endgerät und ein zweites Endgerät umfasst, wobei das Verfahren Folgendes umfasst:

    • Senden einer Anwendungs-Übernahmeanforderung durch das erste Endgerät zu dem zweiten Endgerät;

    • Empfangen einer Übernahme-Annahmeantwort durch das erste Endgerät von dem zweiten Endgerät;

    • Empfangen einer durch das erste Endgerät gesendeten Anwendungs-Übernahmeanweisung durch den Übernahme-Server nach dem Empfang der Übernahme-Annahmeantwort durch das erste Endgerät, wobei die Anwendungs-Übernahmeanweisung Informationen über eine auf dem ersten Endgerät gespeicherte zu übernehmende Anwendung und eine Kennung des zweiten Endgeräts umfasst, wobei mit der Anwendungs-Übernahmeanweisung bewirkt wird, dass die Anwendung des ersten Endgeräts durch das zweite Endgerät übernommen wird, wobei das zweite Endgerät die Anwendung nicht speichert (S210);

    • Herstellen einer Übernahmekorrespondenz zwischen dem ersten Endgerät und dem zweiten Endgerät durch den Übernahme-Server gemäß der Anwendungs-Übernahmeanweisung (S220);

    • Beschaffen von dynamischen Informationen der Anwendung und von den dynamischen Informationen entsprechenden Betriebsinformationen durch den Übernahme-Server gemäß den Informationen, die über die Anwendung sind;

    • Senden der dynamischen Informationen der Anwendung und der entsprechenden Betriebsinformationen zu dem zweiten Endgerät durch den Übernahme-Server auf der Basis der Kennung des zweiten Endgeräts (S240).


     
    2. Anwendungs-Übernahmeverfahren nach Anspruch 1, wobei das Verfahren nach dem Senden der dynamischen Informationen der Anwendung und der entsprechenden Betriebsinformationen zu dem zweiten Endgerät durch den Übernahme-Server ferner Folgendes umfasst:

    Empfangen der dynamischen Informationen der Anwendung und der den dynamischen Informationen entsprechenden Betriebsinformationen durch das zweite Endgerät;

    Bestimmen einer Betriebsanweisung durch das zweite Endgerät gemäß den dynamischen Informationen und den Betriebsinformationen; und

    Senden der Betriebsanweisung, die die Kennung des zweiten Endgeräts umfasst, durch das zweite Endgerät zu dem Übernahme-Server.


     
    3. Anwendungs-Übernahmeverfahren nach Anspruch 2, das nach dem Senden der Betriebsanweisung, die die Kennung des zweiten Endgeräts umfasst, durch das zweite Endgerät zu dem Übernahme-Server ferner Folgendes umfasst:

    Empfangen der die Kennung des zweiten Endgeräts umfassenden Betriebsanweisung durch den Übernahme-Server; und

    Durchführen von Authentifizierung an dem zweiten Endgerät durch den Übernahme-Server gemäß der Kennung des zweiten Endgeräts und der ÜbernahmeKorrespondenz, und wenn die Authentifizierung erfolgreich ist, Ausführen der Betriebsanweisung; und

    wenn die Authentifizierung fehlschlägt, Überspringen der Ausführung der Betriebsanweisung durch den Übernahme-Server.


     
    4. Anwendungs-Übernahmeverfahren nach einem der Ansprüche 1-3, das nach dem Empfangen der durch das erste Endgerät gesendeten Anwendungs-Übernahmeanweisung durch den Übernahme-Server ferner Folgendes umfasst:
    Empfangen einer durch das erste Endgerät gesendeten Anwendungsübernahme-Abbruchanweisung durch den Übernahme-Server.
     
    5. System, das einen Übernahme-Server, ein erstes Endgerät und ein zweites Endgerät umfasst, wobei das System dafür ausgelegt ist, beliebige der Verfahren nach Anspruch 1 - 4 auszuführen.
     


    Revendications

    1. Procédé de prise en charge d'application réalisé par un système comprenant un serveur de prise en charge, un premier terminal et un deuxième terminal, le procédé comprenant :

    • l'envoi, par le premier terminal, d'une requête de prise en charge d'application au deuxième terminal ;

    • la réception, par le premier terminal, d'une réponse d'acceptation de prise en charge provenant du deuxième terminal ;

    • après la réception de la réponse d'acceptation de prise en charge par le premier terminal, la réception, par le serveur de prise en charge, d'une instruction de prise en charge d'application envoyée par le premier terminal, l'instruction de prise en charge d'application comprenant des informations sur une application, stockée sur le premier terminal, devant être prise en charge, et un identifiant du deuxième terminal, l'instruction de prise en charge d'application étant utilisée pour faire prendre en charge l'application du premier terminal par le deuxième terminal, le deuxième terminal ne stockant pas l'application (S210) ;

    • l'établissement, par le serveur de prise en charge, d'une correspondance de prise en charge entre le premier terminal et le deuxième terminal en fonction de l'instruction de prise en charge d'application (S220) ;

    • l'acquisition, par le serveur de prise en charge, en fonction des informations qui concernent l'application, d'informations dynamiques de l'application et d'informations de fonctionnement correspondant aux informations dynamiques ;

    • l'envoi, par le serveur de prise en charge, sur la base de l'identifiant du deuxième terminal, des informations dynamiques de l'application et des informations de fonctionnement correspondantes au deuxième terminal (S240).


     
    2. Procédé de prise en charge d'application selon la revendication 1, le procédé comprenant en outre, après l'envoi, par le serveur de prise en charge, des informations dynamiques de l'application et des informations de fonctionnement au deuxième terminal :

    la réception, par le deuxième terminal, des informations dynamiques de l'application et des informations de fonctionnement correspondant aux informations dynamiques ;

    la détermination, par le deuxième terminal, d'une instruction de fonctionnement en fonction des informations dynamiques et des informations de fonctionnement ; et

    l'envoi, par le deuxième terminal, de l'instruction de fonctionnement comprenant l'identifiant du deuxième terminal au serveur de prise en charge.


     
    3. Procédé de prise en charge d'application selon la revendication 2, comprenant en outre, après l'envoi, par le deuxième terminal, de l'instruction de fonctionnement comprenant l'identifiant du deuxième terminal au serveur de prise en charge :

    la réception, par le serveur de prise en charge, de l'instruction de fonctionnement comprenant l'identifiant du deuxième terminal ; et

    la réalisation, par le serveur de prise en charge, d'une authentification du deuxième terminal en fonction de l'identifiant du deuxième terminal et de la correspondance de prise en charge, et si l'authentification réussit, l'exécution de l'instruction de fonctionnement ; et

    si l'authentification échoue, l'omission, par le serveur de prise en charge, de l'exécution de l'instruction de fonctionnement.


     
    4. Procédé de prise en charge d'application selon l'une quelconque des revendications 1 à 3, comprenant en outre, après la réception, par le serveur de prise en charge, de l'instruction de prise en charge d'application envoyée par le premier terminal :
    la réception, par le serveur de prise en charge, d'une instruction d'annulation de prise en charge d'application envoyée par le premier terminal.
     
    5. Système comprenant un serveur de prise en charge, un premier terminal et un deuxième terminal, le système étant configuré pour réaliser l'un quelconque des procédés selon les revendications 1 à 4.
     




    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