(19)
(11)EP 3 164 981 B1

(12)EUROPEAN PATENT SPECIFICATION

(45)Mention of the grant of the patent:
19.02.2020 Bulletin 2020/08

(21)Application number: 15731379.2

(22)Date of filing:  29.06.2015
(51)International Patent Classification (IPC): 
H04L 29/08(2006.01)
H04L 12/24(2006.01)
(86)International application number:
PCT/EP2015/064731
(87)International publication number:
WO 2016/001162 (07.01.2016 Gazette  2016/01)

(54)

IMPROVED REMOTE ASSISTANCE FOR A MOBILE COMMUNICATIONS TERMINAL

VERBESSERTE FERNASSISTENZ FÜR EIN MOBILE KOMMUNIKATIONSENDGERÄT

TÉLÉASSISTANCE AMÉLIORÉE POUR UN TERMINAL MOBILE DE COMMUNICATION


(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: 04.07.2014 EP 14290197
01.09.2014 EP 14290260

(43)Date of publication of application:
10.05.2017 Bulletin 2017/19

(73)Proprietor: Doro AB
211 20 Malmö (SE)

(72)Inventors:
  • CRIOU, Acher
    FR-92200 Neuilly-sur-Seine (FR)
  • FREUND, Emmanuel
    FR-75014 Paris (FR)
  • CHEVALLIER, Arthur
    FR-75018 Paris (FR)
  • BROGGI, Pierre
    FR-75005 Paris (FR)

(74)Representative: Ström & Gulliksson AB 
P O Box 4188
203 13 Malmö
203 13 Malmö (SE)


(56)References cited: : 
EP-A1- 2 680 532
US-A1- 2005 044 232
US-A1- 2011 029 241
US-A1- 2014 129 612
EP-A2- 2 722 755
US-A1- 2010 211 594
US-A1- 2013 263 287
  
      
    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] This application relates to methods, mobile communications terminals, a system and a computer-readable storage medium for improved remote assistance for a mobile communications terminal, and in particular to methods, a mobile communication terminal, a system and a computer-readable storage medium for improved remote assistance for a mobile communications terminal belonging to a technically inapt user.

    BACKGROUND



    [0002] Contemporary mobile communications terminals are becoming more and more advanced and offer an almost endless array of possibilities to a user. It is, as such, difficult for a technically inapt user, such as an elderly person with little or no experience of mobile communications terminals, to handle their terminals and/or to operate them to their fullest.

    [0003] Many systems exist where a technically skilled user may offer remote assistance based on assuming control of the terminal of the technically inapt user. However, such solutions suffer from the drawbacks that it may be difficult for the technically inapt user to properly describe the problem experienced to the technically skilled user, thereby necessitating time consuming problem finding for the technically skilled user, and that the technically inapt user may not understand what the technically skilled user is doing and thus does not learn how to use his terminal. There is also a risk of malicious use threatening the personal integrity and security of the technically inapt user and his terminal, as full control of the terminal is surrendered to the technically skilled user.

    [0004] Another problem when offering remote assistance is that the technically inapt user may not understand the instructions given to him by a technically skilled user, or the technically inapt user's terminal may be configured wrongly in such a way that it is impossible for the technically skilled user to convey his instructions properly.

    [0005] The U.S. patent application published as US2014129612A1 discloses methods, systems, and apparatus for providing assistance to a user of a mobile application are described. A request for assistance from the user is detected and a request is issued to a remote device for establishment of a remote assistance session. Information describing a state of the mobile device is periodically transmitted to the remote device and one or more commands may be received from the remote device. The commands may be executed on the mobile device.

    [0006] The U.S. patent application published as US2011029241A1 discloses a personal navigation system, including: at least one inertial sensor module associated with a user, the inertial sensor module comprising at least one sensor to generate location data associated with the user; a communication device to receive and/or transmit at least a portion of the location data; and an onsite computer to communicate with the communication device and receive at least a portion of the location data; wherein at least one of the inertial sensor module and the onsite computer is configured to determine at least one activity of the user based at least in part upon the location data; wherein the onsite computer is programmed to configure a display including a representation of the user based at least in part upon the location data; wherein at least one of the determination and the configuration is performed substantially in real-time.

    [0007] There is thus a need for an improved manner of providing remote assistance.

    SUMMARY



    [0008] It is an object of the teachings of this application to overcome the problems listed above by providing a mobile communications terminal according to claim 1.

    [0009] This allows for a remote user to alleviate problems that may give rise to an overall status indication affecting also functions that are not currently activated without having to activate such functions and/or to take active control of the second mobile communications terminal. An erroneously setting may thus be corrected with a single input from the remote terminal.

    [0010] The teachings herein thus provide for a remote user to ascertain an erroneously set setting, and to alleviate this error without taking any control of the mobile communications terminal or take part of any content stored thereon thereby preserving the personal integrity of the user of the mobile communications terminal.

    [0011] This saves both time as well as communication resources, both relating to processor power and to communication interface resources (power and bandwidth).

    [0012] It is an object of the teachings of this application to overcome the problems listed above by providing a system according to claim 11.

    [0013] It is an object of the teachings of this application to overcome the problems listed above by providing a method for use in a mobile communications terminal according to claim 12.

    [0014] It is an object of the teachings of this application to overcome the problems listed above by providing a method for use in a system according to claim 13.

    [0015] It is also an object of the teachings of this application to overcome the problems listed above by providing a computer-readable storage medium encoded with instructions that, when executed on a processor, perform any of the methods according to the above.

    [0016] This allows for a technically skilled user to offer and also provide remote assistance to a technically inapt user without taking control of the user interface of the technically inapt user's terminal. The technically skilled user is thus able to execute certain control commands that enables the terminal of the technically inapt user to function properly and avoid critical events, such as low battery warnings, from occurring. By enabling the technically skilled user to control various aspects, such as volume control, the technically skilled user may take actions to ensure that the technically inapt user is able to receive and understand his instructions. For example, the technically skilled user may remotely increase the speaker volume on the technically inapt user's terminal to ensure that the technically inapt user can hear any instructions spoken by the technically skilled user.

    [0017] The inventors of the present invention have realized, after inventive and insightful reasoning, that by compiling a compiled overall status for a technically inapt user's terminal based on runtime data and presenting this to a technically skilled user, without at first giving too many details on the runtime data, and by offering the technically skilled user options for changing the operation of the technically inapt user's terminal remotely, the technically skilled user may control certain aspects of the technically inapt user's terminal without affecting the integrity or security of the technically inapt user's terminal.

    [0018] As the control might be limited to a few controls, the risk of a malicious use is greatly reduced and the personal integrity of the technically inapt user is also safeguarded.

    [0019] The technically skilled user is thus provided with a compiled indicator of the internal status of the second terminal, and based on this, the technically skilled user may provide technical support that effects the operation of the technically inapt user's terminal by for example remotely executing commands on the technically inapt user's terminal.

    [0020] Other features and advantages of the disclosed embodiments will appear from the following detailed disclosure, from the attached dependent claims as well as from the drawings.

    [0021] Generally, all terms used in the claims are to be interpreted according to their ordinary meaning in the technical field, unless explicitly defined otherwise herein. All references to "a/an/the [element, device, component, means, step, etc]" are to be interpreted openly as referring to at least one instance of the element, device, component, means, step, etc., unless explicitly stated otherwise. The steps of any method disclosed herein do not have to be performed in the exact order disclosed, unless explicitly stated.

    BRIEF DESCRIPTION OF DRAWINGS



    [0022] The teachings herein will be described in further detail under reference to the accompanying drawings in which:

    Figure 1 shows a schematic view of a mobile communications terminal according to one embodiment of the teachings of this application;

    Figure 2 shows a schematic view of the general structure of a mobile communications terminal according to one embodiment of the teachings of this application;

    Figure 3 show a schematic view of a telecommunications network according to one embodiment of the teachings of this application;

    Figure 4 shows a schematic view of a computer-readable medium according to one embodiment of the teachings herein;

    Figure 5 shows a schematic overview of a communications system according to an embodiment herein;

    Figure 6 shows an example embodiment of a communication system arranged for remote assistance according to one embodiment of the teachings herein;

    Figure 7 shows a flowchart for a general method according to one embodiment of the teachings herein; and

    Figure 8 shows a flowchart for a general method according to one embodiment of the teachings herein.


    DETAILED DESCRIPTION



    [0023] The disclosed embodiments will now be described more fully hereinafter with reference to the accompanying drawings, in which certain embodiments of the invention are shown. This invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided by way of example so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. Like numbers refer to like elements throughout.

    [0024] Figure 1 shows a schematic overview of a mobile communications terminal 100 adapted according to the teachings herein. In the embodiment shown the mobile communications terminal is a mobile phone 100. In other embodiments the mobile communications terminal 100 is computer tablet, a laptop computer, a personal digital assistant, a media player, a location finding device or any hand-held device capable of communicating with other devices. The mobile phone 100 comprises a housing 110 in which a display 120 is arranged. In one embodiment the display 120 is a touch display. In other embodiments the display 120 is a non-touch display. Furthermore, the mobile phone 100 comprises two keys 130a, 130b. In this embodiment there are two keys 130, but any number of keys, including none, is possible and depends on the design of the mobile phone 100. In one embodiment the mobile phone 100 is configured to display and operate a virtual key 135 on the touch display 120. It should be noted that the number of virtual keys 135 are dependent on the design of the mobile phone 100 and an application that is executed on the mobile phone 100. In one embodiment the communications terminal 100 comprises an ITU-T keypad or a QWERTY (or equivalent) keypad in addition to or as an alternative to a touch-sensitive display. In one embodiment where the keypad is an alternative to a touch-sensitive display, the display 120 is a non-touch-sensitive display.

    [0025] The mobile phone may be navigated through touch input (if the display 120 is a touch display) or input using physical keys 130 or a combination of the two. In the description below there will be made no difference between use of physical keys to scroll between labels such as soft key labels or other manners of presenting options, and the use of virtual keys.

    [0026] Figure 2 shows a schematic view of the general structure of a mobile communications terminal 100 according to figure 1. The mobile communications terminal 100 comprises a controller 210 which is responsible for the overall operation of the mobile communications terminal 100 and is preferably implemented by any commercially available CPU ("Central Processing Unit"), DSP ("Digital Signal Processor") or any other electronic programmable logic device. The controller 210 is implemented using instructions that enable hardware functionality, for example, by using computer program instructions executable in a general-purpose or special-purpose processor that may be stored on a computer readable storage medium (disk, memory etc) 240 to be executed by such a processor. The controller 210 is configured to read instructions from the memory 240 and execute these instructions to control the operation of the mobile communications terminal 100. The memory 240 may be implemented using any commonly known technology for computer-readable memories such as ROM, RAM, SRAM, DRAM, CMOS, FLASH, DDR, EEPROM memory, flash memory, hard drive, optical storage or any combination thereof. The memory 240 is used for various purposes by the controller 210, one of them being for storing application data and various software modules in the mobile terminal. The software modules include a real-time operating system, an application handler as well as various applications. The applications are sets of instructions that when executed by the controller 210 control the operation of the mobile communications terminal 100.

    [0027] The mobile communications terminal 100 further comprises drivers for a user interface 220, which in the mobile communications terminal 100 of figure 1 is comprised of the display 120, the keys 130, 135, a microphone and a loudspeaker. The user interface (UI) drivers 220 also includes one or more hardware controllers, which together with the UI drivers cooperate with the display 120, keypad 130, as well as various other I/O devices such as microphone, loudspeaker, vibrator, ringtone generator, LED indicator, etc. As is commonly known, the user may operate the mobile terminal through the man-machine interface thus formed.

    [0028] The mobile communications terminal 100 further comprises a radio frequency interface 230, which is adapted to allow the mobile communications terminal to communicate with other communication terminals in a radio frequency band through the use of different radio frequency technologies. Examples of such technologies are W-CDMA, GSM, UTRAN, LTE and NMT to name a few. The controller 210 is configured to operably execute the applications 250, such as the voice call and message handling applications, through the RF interface 230 and software stored in the memory 240, which software includes various modules, protocol stacks, drivers, etc. to provide communication services (such as transport, network and connectivity) for the RF interface 230, and optionally a Bluetooth interface and/or an IrDA interface for local connectivity. The RF interface 230 comprises an internal or external antenna as well as appropriate radio circuitry for establishing and maintaining a wireless link to a base station. As is well known to a person skilled in the art, the radio circuitry comprises a series of analogue and digital electronic components, together forming a radio receiver and transmitter. These components include, i.e., band pass filters, amplifiers, mixers, local oscillators, low pass filters, AD/DA converters, etc.

    [0029] Figure 3 shows a schematic view of the general structure of a telecommunications system 300 according to the teachings herein. In the telecommunication system of figure 3, various telecommunications services such as cellular voice calls, www/wap browsing, cellular video calls, data calls, facsimile transmissions, music transmissions, still image transmissions, video transmissions, electronic message transmissions and electronic commerce may be performed between a mobile terminal 100, 300, 350 according to the disclosed embodiments and other communications terminals, such as another mobile terminal 355 or a stationary telephone 380. The mobile terminals 350, 355 are connected to a mobile telecommunications network 310 through Radio Frequency links via base stations 340.

    [0030] The telecommunications system 300 comprises at least one server 330. A server 330 has a data storage and a controller that is implemented by any commercially available CPU ("Central Processing Unit"), DSP ("Digital Signal Processor") or any other electronic programmable logic device. In one embodiment such a server is a Mobility Management Entity (MME). In one embodiment such a server is a Gateway (GW). The servers 330 are configured to communicate with a mobile telecommunications core network (CN) 310 and/or an external resource 320 such as the internet or a Public Switched Telephone Network (PSTN). A PSTN 320 is configured to communicate with and establish communication between stationary or portable telephones 380. In one embodiment the external resource comprises or is configured to communicate with an external service provider 390. In one embodiment the servers 330 are configured to communicate with other communications terminals using a packet switched technology or protocol. In such an embodiment the servers 330 may make up an Evolved Packet Core (EPC) layer.

    [0031] The servers 330 are configured to communicate with nodes, also referred to as base stations 340. In one embodiment the base station 340 is an evolved Node Base (eNB). A base station 340 is further configured to communicate with a server 330. In one embodiment the communication between a server 330 and a base station 340 is effected through a standard or protocol 370. In one embodiment the protocol is S1. A base station 340 is configured to communicate with another base station 340. In one embodiment the communication between a base station 340 and another base station 340 is effected through a standard or protocol 360. In one embodiment the protocol 360 is X2. A base station 340 is further configured to handle or service a cell 380. In one embodiment the at least one base stations 340 make up a Long Term Evolution (LTE) layer. In one embodiment the at least one base stations 340 make up an LTE Advanced layer.

    [0032] In one embodiment the base station 340 is configured to communicate with a mobile communications terminal 330 (100) through a wireless radio frequency protocol.

    [0033] In one embodiment the telecommunications system 300 is an Evolved Packet System (EPS) network. In one embodiment the telecommunications system is a system based on the 3GPP (3rd Generation Partnership Project) standard. In one embodiment the telecommunications system is a system based on the UMTS (Universal Mobile Telecommunications System) standard. In one embodiment the telecommunications system is a system based on a telecommunications standard such as GSM, D-AMPS, CDMA1000, FOMA or TD-SCDMA.

    [0034] As would be apparent to a skilled reader, a computer-enabled communications network, such as the Internet or a telecommunications network, provides many possibilities and variations of how to connect two terminals, and the embodiments disclosed herein are for purely exemplary purposes and should not be construed to be limiting.

    [0035] References to 'computer-readable storage medium', 'computer program product', 'tangibly embodied computer program' etc. or a 'controller', 'computer', 'processor' etc. should be understood to encompass not only computers having different architectures such as single /multi- processor architectures and sequential (Von Neumann)/parallel architectures but also specialized circuits such as field-programmable gate arrays (FPGA), application specific circuits (ASIC), signal processing devices and other devices. References to computer program, instructions, code etc. should be understood to encompass software for a programmable processor or firmware such as, for example, the programmable content of a hardware device whether instructions for a processor, or configuration settings for a fixed-function device, gate array or programmable logic device etc.

    [0036] Figure 4 shows a schematic view of a computer-readable storage medium, such as a computer-readable storage medium, as described in the above. The computer-readable medium 40 is in this embodiment a data disc 40, being an example of a tangible computer-readable medium. In one embodiment the data disc 40 is a magnetic data storage disc. The data disc 40 is configured to carry instructions 41 that when loaded into a controller, such as a processor, execute a method or procedure according to the embodiments disclosed above. The data disc 40 is arranged to be connected to or within and read by a reading device 42, for loading the instructions into the controller. One such example of a reading device 42 in combination with one (or several) data disc(s) 40 is a hard drive. It should be noted that the computer-readable medium can also be other mediums such as compact discs, digital video discs, flash memories or other memory technologies commonly used.

    [0037] The instructions 41 may also be downloaded to a computer data reading device 44, such as a mobile communications terminal 44 or other device capable of reading computer coded data on a computer-readable medium, by comprising the instructions 41 in a computer-readable signal 43 which is transmitted via a wireless (or wired) interface (for example via the Internet) to the computer data reading device 44 for loading the instructions 41 into a controller. In such an embodiment the computer-readable signal 43 is one type of a (non-tangible) computer-readable medium 40.

    [0038] The instructions may be stored in a memory (not shown explicitly in figure 4, but referenced 240 in figure 2) of the mobile communications terminal 44.

    [0039] References to computer program, instructions, code etc. should be understood to encompass software for a programmable processor or firmware such as, for example, the programmable content of a hardware device whether instructions for a processor, or configuration settings for a fixed-function device, gate array or programmable logic device etc.

    [0040] Figure 5 shows a schematic overview of a communications system 500 according to an embodiment herein. The communication system comprises a first terminal 100A, such as the mobile communications terminal 100 of figures 1 or 2, which is arranged to communicate with a second terminal 100B, such as the mobile communications terminal 100 of figures 1 or 2, for example through the internet or a telecommunications network as per figure 3. The communication system 500 may further comprise at least one server 550 for providing for example information to the first terminal 100A about the second terminal 100B.

    [0041] The first terminal 100A is arranged with a remote assistance application which enables a technically skilled user to assist a technically inapt user of the second terminal 100B.

    [0042] The second terminal 100B is therefore arranged with a runtime data retrieving application which retrieves runtime data on the operation of the second terminal 100B and sends the status data to the first terminal 100A.

    [0043] The runtime data may be retrieved upon a request from the first terminal or regularly or upon an event by the second terminal 100B.

    [0044] The runtime data correlating to an internal characteristic or internal status of an application or the device, which characteristic or status may not currently be visibly presented. The runtime data is not related to a simple screen dump or other means of purveying what is currently displayed on the second mobile communication terminal's display.

    [0045] The runtime data may relate to battery level, memory usage, application usage, number of user interface actuations, such as key presses - both virtual and physical, for use of an application, number of missed calls (indicating a too low ringtone volume), number of unread messages (indicating a too low incoming message signal), number of error messages received relating email (indicating a wrongly set up email account or contact), to name a few aspects.

    [0046] The first terminal 100A is configured to display three segments on the display 120 for providing the technically skilled user with information on the second terminal 100B and also controls for offering assistance to the technically inapt user of the second terminal 100B.

    [0047] It should be noted that even though the description herein is directed at displaying three segments, it should be clear that any number of segments may be displayed and the information and controls displayed in the various segments may be grouped or combined in different manners while still being included in the general teachings of this application.

    [0048] In the example embodiment of figure 5, the first terminal 100A is arranged to display a status segment 122 where a compiled status and possibly the identity or name of the technically inapt user is displayed. Some control options may also be displayed, as will be discussed below, in the status segment 122. Controls are displayed in a control segment 124. The controls may be displayed as virtual keys and/or fields and offer a technically skilled user to issue controls that are to be effectuated by the second terminal 100B. A data sharing segment 126 is also displayed which enables a technically skilled user to share data with the technically inapt user. Such data may be, but is not limited to, exchanging data files, contacts or tutorials, either directly or indirectly by sharing an identifier, such as a link or an address, for download of the data. By allowing a technically skilled user to share data with the technically inapt user, the technically skilled user is enabled to execute certain tasks on behalf of the technically inapt user without taking control of the technically inapt user's second terminal 100B by simply sharing the result of such tasks. For example, instead of allowing the technically skilled user to create a contact on the technically inapt user's second terminal 100B, the technically skilled user can create the contact on his first terminal 100A and share the created contact with the technically inapt user.

    [0049] The server 550 may be contacted by the technically skilled user's first terminal 100A to request further data regarding the second terminal 100B. The server 550 may also be used for (intermediate) storage of data files to be shared. The server 550 may also be contacted by terminal 100A and/or 100B to request runtime data regarding network usage or other network data.

    [0050] The server 550 may also be configured and used for (temporary) storage of runtime data collected by the second terminal 100B and to be delivered or sent to the first terminal 100A. This is useful when there is currently no active data communication channel between the first terminal 100A and the second terminal 100B, wherein the server 550 then acts as a buffer. In one embodiment, the server 550 may also be configured to compile the compiled overall status partially or fully and/or rank the various aspects of the runtime data before sending the runtime associated data to the first terminal 100A. The compiled overall status is thus automatically determined and relates to runtime data concerning possibly several aspects, currently activated or not and/or currently visible or not

    [0051] Figure 6 shows an example embodiment of a communication system 500 arranged for remote assistance according to herein. The first terminal 100A receives a runtime data message from the second terminal 100B. As is indicated by the dashed arrow, the runtime data message may be compiled and sent by the second terminal 100B upon receiving a request for a status update from the first terminal 100A.

    [0052] Such a request may be issued manually by the technically skilled user activating a request runtime data option in the remote assistance application, which option is illustrated as a virtual key in figure 6.

    [0053] As the first terminal 100A receives the runtime data, it analyzes the data and compiles a compiled overall status for the second terminal 100B. The compiled overall status is based on usage factors such as memory consumption, battery level (and also battery consumption), missed calls, frequency of use for specific application(s), error messages received for application/action.

    [0054] The compiled ocverall status is thus not a status for a single application, function or resource of the terminal, but a collation of statuses for different applications, functions or resources, which are compiled to indicate a compiled overall status of a terminal. By combining various runtime into one aspect, further aspects of the usage may be determined, such as indicating that a user is in need of assistance - given remotely by a second user.

    [0055] Such a compilation also carries the benefit that the status of the device is determined automatically and the internal status of the terminal is thus provided to a user without the user - or the other user - having to ascertain the runtime data and make any conclusions based on the runtime data - a process which may require substantive information gathering through many different applications and interfaces before a reasonably safe conclusion can be made.

    [0056] The status of a single application or resource may be provided through the runtime time and the run time data thus may include statuses for individual applications (such as error messages to give one example) and/or resources (such as memory usage to give one example).

    [0057] Examples of resources are memory usage, processor usage, battery usage, sound levels (which may also be given as a status for an application), Radio Frequency communication interface usage (is the WiFi or Bluetooth (for example) often switched off) to name a few.

    [0058] The compiled status may be based on an individual assessment of each aspect for the runtime data.

    [0059] The compiled status may be based on a weighted sum of rankings of such runtime data or the compiled status may be based on an individual ranking of each aspect for the runtime data.

    [0060] In one embodiment where the first terminal 100A is configured to determine the compiled overall status based on a weighted sum of rankings or on an individual ranking, the first terminal 100A is configured to rank each aspect of the runtime data. An aspect may be related to a specific use or component, such as battery level for example. A ranking of the battery level may be linear or divided into steps. One example of a stepwise ranking for the battery level is shown below.
    Battery levelRanking
    100% - 80 % 10
    80 % -50 % 9
    50 % - 40 % 8
    40 % - 30 % 7
    30% - 25 % 6
    25 % - 20 % 5
    20 % - 16 % 4
    16 % - 12 % 3
    12 % - 8 % 2
    8 % - 5 % 1
    <5% 0


    [0061] A ranking of 10 indicates a proper usage and a lower ranking indicates that something is not operating at optimum conditions. High rankings will therefore lead to a high compiled overall status which will indicate a proper usage, whereas a low ranking will indicate that the technically inapt user is not fully aware of a function and that assistance may be needed.

    [0062] Another aspect related to battery level is how quickly the battery level drops. A fast decline in battery level may indicate an improper usage. It may also indicate that the technically inapt user may not be aware that he can take actions to reduce the rate of battery power consumption. An example of an action to be taken to reduce the battery power consumption is to reduce the brightness level of the display 120.

    [0063] The first terminal 100A is thus configured to rank the various aspects of the runtime data and compile a compiled overall status and present this compiled overall status through the user interface of the first terminal 100A.

    [0064] It should be noted that presenting in the context of this application should be understood to include displaying both still images and moving images, playing sound or audio files, displaying text, playing speech derived from text using various text-to-speech technologies, and also to indirectly present data by providing an identifier, such as a link or address for download of the data to be presented.

    [0065] The compiled overall status may thus be presented in the status segment 122 of the display as a key word or text (e.g. good, acceptable, bad), an image (e.g. happy smiley, sad smiley), a color (e.g. green, yellow, red), a link to the server 550 for retrieving the status (if the compiled overall status has been compiled by the server 550), and also in other manners.

    [0066] In one embodiment, the compiled overall status is compiled as being the average of all or most of the rankings. In another embodiment, the compiled overall status is compiled as being the lowest ranking.

    [0067] The compiled overall status enables the technically skilled user to get a quick overview of the status for the technically inapt user without having to browse through all details available on the technically inapt user's usage of the second terminal 100B.

    [0068] Should the technically skilled user want to see more details about the status of the technically inapt user, an option for displaying further details may be presented and selected by the technically skilled user.

    [0069] To enable the technically skilled user to provide remote assistance to the technically inapt user, the first terminal is configured to display or otherwise present one or more control options. These may be displayed in the setup or control segment 124 as virtual keys or by other means known to a skilled person.

    [0070] In one embodiment, the control options displayed correspond to respective control functions to be executed by the second terminal 100B. By only displaying control options that correspond to control functions of the second terminal a technically skilled user will be prevented from taking over control of the technically inapt user's second terminal completely, thereby safeguarding the personal integrity of the technically inapt user and also reducing the risk of any malicious use. This while still enabling the technically skilled user to provide assistance through the selected control functions. The control functions possibly being to turn on/off an RF interface (WiFi, Bluetooth®, to name some examples), to raise/lower a sound level, and/or to increase/decrease illumination of the screen to name a few examples.

    [0071] The skilled user of the first terminal is thus allowed or enabled to issue control commands for affecting also functions that are not currently visible on the second mobile communications terminal for alleviating a problematic situation as indicated by the compiled overall status, without taking control of the user interface of the second mobile communications terminal.

    [0072] A control command may therefore be sent from the first terminal 100A to the second terminal 100B by actuating or selecting a control option at the first terminal 100A, whereby the second terminal, upon receiving the control command, executes the control command by executing the corresponding control function.

    [0073] Using these control options the technically skilled user can take an action to improve the operation of the technically inapt user's second terminal 100B without having to be close to the second terminal 100B.

    [0074] In one embodiment the first terminal 100A may be configured to indicate an action to be taken, possibly by highlighting the corresponding control (or data to be shared). In the example of figure 6 it is indicated that a tutorial should be shared. The first terminal 100A may be configured to determine the action to be taken by finding a correlation between a ranking, possibly one having a low ranking, and an action. The correlation may be stored in the first terminal or may be retrieved from the server 550. For example, a high number of missed calls would be correlated to increasing the ring tone volume and a high consumption of battery power would be correlated to reducing the brightness and also to share a tutorial on battery management (more on sharing tutorials in the below). A high number of error messages for an application or a feature may be correlated to a tutorial for the application or feature. A tutorial may also be correlated to other aspects of the runtime data. For example, a high number of missed calls may be correlated to a tutorial on ringtones and vibrations. A high memory usage may be correlated to a tutorial on memory management.

    [0075] Some examples of actions to be taken to improve a compiled overall status based on the receive runtime status are discussed below.

    [0076] If the runtime data indicates or includes a high memory usage, the technically skilled user may opt to perform some remote memory management. One control that could be enabled for the technically skilled user would be to initiate archiving or uploading of rarely accessed data files.

    [0077] If the runtime data indicates a high number of error messages for an application or feature, the technically skilled user may opt to share a tutorial on the application or feature. The tutorial may be found through a correlation (stored or retrieved from the server 550) between the application or feature and the tutorial.

    [0078] A tutorial may be shared by sending the actual tutorial or by sending an identifier, such as a link or address to the tutorial that causes the second terminal 100B to download or retrieve the tutorial. Using a standard library for tutorials provided by the server 550, the technically inapt user can trust that the tutorial is true and that the teachings of the tutorial will improve the technically inapt user's handling of the second terminal.

    [0079] As in the above, it should be noted that presenting in the context of this application should be understood to include displaying both still images and moving images, playing sound or audio files, displaying text, playing speech derived from text using various text-to-speech technologies, and also to indirectly present data by providing an identifier, such as a link or address for download of the data to be presented.

    [0080] The tutorial may thus be presented as a text, one or a series of images, moving or still, an audio file, a video file, a link to the server 550 for retrieving the tutorial, and also in other manners. As has been discussed in the above, the technically skilled user may opt to decrease the illumination/brightness of the display of the second terminal 100B if the runtime data indicates a high battery consumption.

    [0081] As has been discussed in the above, the technically skilled user may opt to increase the ringtone volume of the second terminal 100B if the runtime data indicates a high number of missed calls or unread messages.

    [0082] The technically skilled user is also enabled to offer remote assistance by the first terminal 100A being configured to present at least one option for sharing data files with the second terminal 100B. The technically skilled user may then offer remote assistance by sending files that are of interest to the technically inapt user, to generate and share data files that the technically inapt user is not able to generate (such as contacts) and/or to share tutorials that the technically inapt user would benefit from taking part of.

    [0083] The options to share data may be presented as virtual keys, possibly associated with a field for searching or browsing for the file to be shared. As would be apparent to a skilled person, other options are also possible to associate with a sharing option.

    [0084] Data may be shared as image, video, music or other media files, contact files, tutorial files (possibly being text, image, audio and/or video files) or indirectly through an identifier, such as a link or address, to downloadable data to be downloaded by the second terminal 100B.

    [0085] As has been mentioned in the above, the options may be presented and selected as virtual keys 135, labels for physical keys and/or selectable items which can be scrolled through using the physical keys 130, or a combination of such options for presentation and selection.

    [0086] In one embodiment, the first terminal is configured to receive runtime data from the second terminal, analyze the runtime data, possibly by ranking aspects of the runtime data and determine a tutorial related to at least one aspect and indicate this as a proposed tutorial to be shared. This may, in such an embodiment, be made without compiling a compiled overall status and/or without presenting other control options. A technically skilled user may thus provide assistance in selecting, possibly among many tutorials, a tutorial to be shared with the technically inapt user.

    [0087] In one embodiment the server 550 may be configured to receive runtime data from the second terminal, analyze the runtime data, possibly by ranking aspects of the runtime data, determine a tutorial related to at least one aspect, and share the tutorial with the second terminal 100B.

    [0088] Figure 7 shows a flowchart for a general method according to one embodiment of the teachings herein.

    [0089] The first terminal 100A receives 710 runtime data from the second terminal 100B, possibly as a response to a request for runtime data. In one embodiment, the first terminal 100A may be configured to (regularly) request runtime data from the second terminal 100B. In one embodiment, the second terminal 100B may be configured to (regularly) send runtime data to the first terminal 100A without being prompted to do so by the first terminal 100A.

    [0090] The first terminal 100A analyzes 720 the runtime data, possibly by ranking 722 different aspects of the runtime data and compiling a compiled overall status 724 which is presented 726, possibly on the display 120 of the first terminal 100A. Another manner of presenting the status is through a text to speech interface.

    [0091] The first terminal then receives a control command 730 and/or a command to share data 740. If a control command is received, the first terminal 100A transmits 735 the control command to the second terminal 100B causing the second terminal 100B to execute the control command. If a command to share data is received, the file (or other data) to be shared is selected and transmitted 745 to the second terminal 100B.

    [0092] The operation of the second terminal 100B is shown in figure 8, being a flowchart for a general method according to one embodiment of the teachings herein.

    [0093] The second terminal 100B generates or collects 810 the runtime data and transmits 820 the runtime data to the first terminal 100A. The runtime data may be collected continuously or upon a request received from the first terminal. Likewise, the runtime data may be transmitted regularly or upon a request by the first terminal 100A.

    [0094] By not sending the runtime data only when an event, such as a low battery warning, occurs, the technically skilled user is able to monitor the technically inapt user's usage of the second terminal 100B more closely and possibly being able to prevent any event from arising.

    [0095] The second terminal 100B then receives a control command 830 and/or a data file (or other data) to be shared, 840.

    [0096] If a control command is received, 830, the second terminal 100B executes the control command, 835.

    [0097] If a file (or other data) to be shared is received, 840, the second terminal 100B presents 845 the file (or other data) to be shared in a manner consistent with the type of file (or other data) to be shared. Possibly a prompt is presented first asking the technically inapt user if he is willing to accept the shared file and whether the shared file should be presented or stored for later presentation.

    [0098] To setup a communication system 500 as in figure 5, the second terminal 100B is configured to receive a connection request 800 from the first terminal 100A. Alternatively or additionally, the first terminal 100A is configured to receive 700 a connection request from the second terminal 100B.

    [0099] The connection request only needs to be transmitted once, as is indicated by the dashed line, and the connection does not need to be repeated every time runtime data is to be transmitted.

    [0100] Upon accepting the request, the first terminal 100A is enabled to receive runtime data from the second terminal 100B and the second terminal 100B is enabled to receive shared files or other shared data and/or control commands from the first terminal 100A. The use of a connection request which has to be generated and sent by one of the terminals 100A, 100B and accepted by the other terminal 100B, 100A, will provide mutual security for the users of the terminals 100A, 100B and safeguard personal integrity.

    [0101] The runtime data, control commands and/or the shared data files may be transmitted through a known protocol such as the Internet Protocol (IP), a text based protocol using short message service (SMS) messages or multimedia messages (MMS) messages, or a proprietary protocol.

    [0102] The teachings herein have mainly been described above with reference to a few embodiments. However, as is readily appreciated by a person skilled in the art, other embodiments than the ones disclosed above are equally possible within the scope of the invention, as defined by the appended patent claims.


    Claims

    1. A mobile communications terminal (100A) comprising a user interface (120, 135, 130) and a controller (210), wherein the controller (210) is configured to:

    receive runtime data from a second mobile communications terminal (100B), wherein the runtime data corresponds to a plurality of statuses of at least one application and/or at least one resource, the runtime data not being screen dumps;

    automatically compile a compiled overall status for the second mobile communications terminal (100B) based on the runtime data, the compiled overall status thereby relating to runtime data concerning several aspects whereby the plurality of runtime data are combined into one compiled overall status;

    present the compiled overall status through the user interface (120, 130, 135);

    receive user input through the user interface (120, 130, 135), the user input indicating a control command and/or data to be shared; and

    if the user input indicates a control command, send the control command to the second mobile communications terminal (100B), thereby causing the second mobile communications terminal (100B) to execute the control command, wherein the control command relates to a control function of the second mobile communications terminal thereby preventing full control of the second mobile communications terminal (100B) by only allowing control of a set of control functions, and

    if the user input indicates data to be shared, send the data to be shared to the second mobile communications terminal (100B), thereby causing the second mobile communications terminal (100B) to present the data to be shared.


     
    2. The mobile communications terminal (100A) of claim 1, wherein the controller (210) is further configured to present control command options corresponding to a control function to be executed by the second mobile communications terminal (100B), wherein the user input indicating a control command is an actuation of a control command option, and wherein the second mobile communications terminal (100B) is caused to execute the control command by executing the corresponding control function.
     
    3. The mobile communications terminal (100A) of claim 1 or 2, wherein the controller (210) is further configured to compile the overall status based on the runtime data by ranking at least one aspect of the runtime data and compiling the overall status based on the ranking of the at least one aspect of the runtime data.
     
    4. The mobile communications terminal (100A) according to any of claims 1 to 3, wherein the controller is further configured to compile the compiled overall status based on an average of the at least one aspect of the runtime data.
     
    5. The mobile communications terminal (100A) according to any of claims 1 to 4, wherein the controller is further configured to compile the compiled overall status based on a lowest ranked of the at least one aspect of the runtime data.
     
    6. The mobile communications terminal (100A) according to any of claims 1 to 5, wherein the controller is further configured to determine a proposed action to be taken and by finding a correlation between an aspect having a low ranking and an action, and indicating the proposed action to be taken through the user interface (120, 130, 135).
     
    7. The mobile communications terminal (100A) according to claim 6, wherein the proposed action to be taken is to send a tutorial to the second mobile communications terminal (100B), wherein the tutorial is correlated to an aspect of the runtime data.
     
    8. The mobile communications terminal (100A) according to claim 7, wherein the tutorial to be sent to the second terminal is sent as an identifier to a downloadable tutorial to be downloaded by the second mobile communications terminal (100B).
     
    9. The mobile communications terminal (100) according to any of claims 1 to 8, wherein the controller (210) is further configured to receive a connection request from the second mobile communications terminal (100B) and upon accepting the request, enable the mobile communications terminal (100A) to receive runtime data from the second mobile communications terminal (100B).
     
    10. The mobile communications terminal (100) according to any of claims 1 to 9, wherein the runtime data relate to memory consumption, battery level, battery consumption, missed calls, frequency of use for specific application(s), error messages received for application/action, memory usage, application usage, number of user interface actuations, such as key presses - both virtual and physical, for use of an application, number of unread messages, number of error messages received relating email.
     
    11. A system comprising a first mobile communications terminal (100A) and a second mobile communications terminal (100B),
    wherein the second mobile communications terminal (100B) is configured to:

    collect runtime data wherein the runtime data corresponds to a plurality of statuses of at least one application and/or at least one resource, the runtime data not being screen dumps; and

    transmit the runtime data to the first mobile communications terminal (100A),

    wherein the first mobile communications terminal (100A) is configured to:

    receive the runtime data from the second mobile communications terminal (100B);

    automatically compile a compiled overall status for the second mobile communications terminal (100B) based on the runtime data, the compiled overall status thereby relating to runtime data concerning several aspects whereby the plurality of runtime data are combined into one compiled overall status;

    present the compiled overall status through the user interface (120, 130, 135);

    receive user input through the user interface (120, 130, 135), the user input indicating a control command and/or data to be shared; and

    if the user input indicates a control command, send the control command to the second mobile communications terminal (100B), thereby causing the second mobile communications terminal (100B) to execute the control command, wherein the control command relates to a control function of the second mobile communications terminal thereby preventing full control of the second mobile communications terminal (100B) by only allowing control of a set of control functions, and

    if the user input indicates data to be shared, send the data to be shared to the second mobile communications terminal (100B), thereby causing the second mobile communications terminal (100B) to present the data to be shared,

    and wherein the second mobile communications terminal (100B) is further configured to:

    receive the control command and/or the data to be shared from the first mobile communications terminal (100A); and

    if a control command is received, execute the control command, and

    if data to be shared is received, present the data to be shared.


     
    12. A method for use in a mobile communications terminal (100A) comprising a user interface (120, 135, 130), wherein the method comprises:

    receiving runtime data from a second mobile communications terminal (100B), wherein the runtime data corresponds to a plurality of statuses of at least one application and/or at least one resource, the runtime data not being screen dumps;

    automatically compiling a compiled overall status for the second mobile communications terminal (100B) based on the runtime data, the compiled overall status thereby relating to runtime data concerning several aspects whereby the plurality of runtime data are combined into one compiled overall status;

    presenting the compiled overall status through the user interface (120, 130, 135);

    receiving user input through the user interface (120, 130, 135), the user input indicating a control command and/or data to be shared; and

    if the user input indicates a control command, sending the control command to the second mobile communications terminal (100B), thereby causing the second mobile communications terminal (100B) to execute the control command, wherein the control command relates to a control function of the second mobile communications terminal thereby preventing full control of the second mobile communications terminal (100B) by only allowing control of a set of control functions, and

    if the user input indicates data to be shared, sending the data to be shared to the second mobile communications terminal (100B), thereby causing the second mobile communications terminal (100B) to present the data to be shared.


     
    13. A method for use in a system comprising a first mobile communications terminal (100A) and a second mobile communications terminal (100B), wherein the method comprises:

    the second mobile communications terminal (100B) collecting runtime data, wherein the runtime data corresponds to a plurality of statuses of at least one application and/or at least one resource, the runtime data not being screen dumps; and

    transmitting the runtime data to the first mobile communications terminal (100A), wherein the method further comprises:

    the first mobile communications terminal (100A) receiving the runtime data from the second mobile communications terminal (100B);

    automatically compiling a compiled overall status for the second mobile communications terminal (100B) based on the runtime data, the compiled overall status thereby relating to runtime data concerning several aspects whereby the plurality of runtime data are combined into one compiled overall status;

    presenting the compiled overall status through the user interface (120, 130, 135);

    receiving user input through the user interface (120, 130, 135), the user input indicating a control command and/or data to be shared; and

    if the user input indicates a control command, sending the control command to the second mobile communications terminal (100B), thereby causing the second mobile communications terminal (100B) to execute the control command, wherein the control command relates to a control function of the second mobile communications terminal thereby preventing full control of the second mobile communications terminal (100B) by only allowing control of a set of control functions, and

    if the user input indicates data to be shared, sending the data to be shared to the second mobile communications terminal (100B), thereby causing the second mobile communications terminal (100B) to present the data to be shared,

    and wherein the method further comprises:

    the second mobile communications terminal (100B) receiving the control command and/or the data to be shared from the first mobile communications terminal (100A); and

    if a control command is received, executing the control command, and

    if data to be shared is received, presenting the data to be shared.


     
    14. A computer-readable storage medium (40) encoded with instructions (41) that, when executed on a processor, perform the method according to claim 11, 12 or 13.
     


    Ansprüche

    1. Mobiles Kommunikationsendgerät (100A), umfassend eine Benutzeroberfläche (120, 135, 130) und eine Steuerung (210), wobei die Steuerung (210) zu Folgendem ausgelegt ist:

    Empfangen von Laufzeitdaten von einem zweiten mobilen Kommunikationsendgerät (100B), wobei die Laufzeitdaten einer Vielzahl von Statusangaben von mindestens einer Anwendung und/oder mindestens einer Ressource entsprechen, wobei die Laufzeitdaten keine Bildschirmkopien sind;

    automatisches Zusammenstellen eines zusammengestellten Gesamtstatus des zweiten mobilen Kommunikationsendgeräts (100B) auf der Grundlage der Laufzeitdaten, wobei der zusammengestellte Gesamtstatus dadurch Laufzeitdaten in Bezug auf mehrere Aspekte betrifft, wodurch die Vielzahl von Laufzeitdaten zu einem zusammengestellten Gesamtstatus vereinigt wird;

    Präsentieren des zusammengestellten Gesamtstatus über die Benutzeroberfläche (120, 130, 135);

    Empfangen einer Benutzereingabe über die Benutzeroberfläche (120, 130, 135), wobei die Benutzereingabe einen Steuerbefehl und/oder zu teilende Daten angibt; und

    wenn die Benutzereingabe einen Steuerbefehl angibt, Senden des Steuerbefehls an das zweite mobile Kommunikationsendgerät (100B), wodurch das Ausführen des Steuerbefehls durch das zweite mobile Kommunikationsendgerät (100B) bewirkt wird, wobei der Steuerbefehl eine Steuerfunktion des zweiten mobilen Kommunikationsendgeräts betrifft, und dadurch Verhindern einer vollständigen Kontrolle des zweiten mobilen Kommunikationsendgeräts (100B) durch das Zulassen nur eines Satzes von Steuerfunktionen, und

    wenn die Benutzereingabe zu teilende Daten angibt, Senden der zu teilenden Daten an das zweite mobile Kommunikationsendgerät (100B), wodurch das Präsentieren der zu teilenden Daten durch das zweite mobile Kommunikationsendgerät (100B) bewirkt wird.


     
    2. Mobiles Kommunikationsendgerät (100A) nach Anspruch 1, wobei die Steuerung (210) weiterhin zum Präsentieren von Steuerbefehlsoptionen ausgelegt ist, die einer von dem zweiten mobilen Kommunikationsendgerät (100B) auszuführenden Steuerfunktion entsprechen, wobei die einen Steuerbefehl angebende Benutzereingabe eine Aktivierung einer Steuerbefehlsoption ist und wobei bewirkt wird, dass das zweite mobile Kommunikationsendgerät (100B) den Steuerbefehl durch Ausführen der entsprechenden Steuerfunktion ausführt.
     
    3. Mobiles Kommunikationsendgerät (100A) nach Anspruch 1 oder 2, wobei die Steuerung (210) weiterhin zum Zusammenstellen des Gesamtstatus auf der Grundlage der Laufzeitdaten durch Anordnen mindestens eines Aspekts der Laufzeitdaten in einer Rangfolge und Zusammenstellen des Gesamtstatus auf der Grundlage der Rangfolge des mindestens einen Aspekts der Laufzeitdaten ausgelegt ist.
     
    4. Mobiles Kommunikationsendgerät (100A) nach einem der Ansprüche 1 bis 3, wobei die Steuerung weiterhin zum Zusammenstellen des zusammengestellten Gesamtstatus auf der Grundlage eines Durchschnittswerts des mindestens einen Aspekts der Laufzeitdaten ausgelegt ist.
     
    5. Mobiles Kommunikationsendgerät (100A) nach einem der Ansprüche 1 bis 4, wobei die Steuerung weiterhin zum Zusammenstellen des zusammengestellten Gesamtstatus auf der Grundlage eines am niedrigsten eingestuften Aspekts des mindestens einen Aspekts der Laufzeitdaten ausgelegt ist.
     
    6. Mobiles Kommunikationsendgerät (100A) nach einem der Ansprüche 1 bis 5, wobei die Steuerung weiterhin zum Bestimmen einer vorgeschlagenen zu ergreifenden Maßnahme durch Finden einer Korrelation zwischen einem Aspekt mit einer niedrigen Rangstufe und einer Maßnahme, sowie Angeben der vorgeschlagenen zu ergreifenden Maßnahme über die Benutzeroberfläche (120, 130, 135) ausgelegt ist.
     
    7. Mobiles Kommunikationsendgerät (100A) nach Anspruch 6, wobei die vorgeschlagene zu ergreifende Maßnahme das Senden eines Tutorials an das zweite mobile Kommunikationsendgerät (100B) ist, wobei das Tutorial mit einem Aspekt der Laufzeitdaten in Verbindung steht.
     
    8. Mobiles Kommunikationsendgerät (100A) nach Anspruch 7, wobei das an das zweite Endgerät zu sendende Tutorial als eine Identifizierung eines herunterladbaren Tutorials gesendet wird, das von dem zweiten mobilen Kommunikationsendgerät (100B) heruntergeladen werden soll.
     
    9. Mobiles Kommunikationsendgerät (100) nach einem der Ansprüche 1 bis 8, wobei die Steuerung (210) weiterhin zum Empfangen einer Verbindungsanforderung von dem zweiten mobilen Kommunikationsendgerät (100B) und nach Annehmen der Anforderung dem Kommunikationsendgerät (100A) zu ermöglichen, Laufzeitdaten von dem zweiten mobilen Kommunikationsendgerät (100B) zu empfangen.
     
    10. Mobiles Kommunikationsendgerät (100) nach einem der Ansprüche 1 bis 9, wobei die Laufzeitdaten Speicherverbrauch, Akkustand, Stromverbrauch, verpasste Anrufe, Häufigkeit der Verwendung bestimmter Anwendungen, betreffend Anwendungen/Maßnahmen erhaltene Fehlermeldungen, Speichernutzung, Anwendungsnutzung, Anzahl von Benutzeroberflächenbetätigungen, wie Tastenbetätigungen - sowohl virtuell als auch physisch - zur Verwendung einer Anwendung, Anzahl ungelesener Nachrichten, Anzahl von E-Mails betreffenden Fehlermeldungen betreffen.
     
    11. System, umfassend ein erstes mobiles Kommunikationsendgerät (100A) und ein zweites mobiles Kommunikationsendgerät (100B),
    wobei das zweite mobile Kommunikationsendgerät (100B) zu Folgendem konfiguriert ist:

    Erfassen von Laufzeitdaten, wobei die Laufzeitdaten einer Vielzahl von Statusangaben von mindestens einer Anwendung und/oder mindestens einer Ressource entsprechen, wobei die Laufzeitdaten keine Bildschirmkopien sind;

    Übertragen der Laufzeitdaten an das erste mobile Kommunikationsendgerät (100A),

    wobei das erste mobile Kommunikationsendgerät (100A) zu Folgendem konfiguriert ist:

    Empfangen der Laufzeitdaten von dem zweiten mobilen Kommunikationsendgerät (100B);

    automatisches Zusammenstellen eines zusammengestellten Gesamtstatus des zweiten mobilen Kommunikationsendgeräts (100B) auf der Grundlage der Laufzeitdaten, wobei der zusammengestellte Gesamtstatus dadurch Laufzeitdaten in Bezug auf mehrere Aspekte betrifft, wodurch die Vielzahl von Laufzeitdaten zu einem zusammengestellten Gesamtstatus vereinigt wird;

    Präsentieren des zusammengestellten Gesamtstatus über die Benutzeroberfläche (120, 130, 135);

    Empfangen einer Benutzereingabe über die Benutzeroberfläche (120, 130, 135), wobei die Benutzereingabe einen Steuerbefehl und/oder zu teilende Daten angibt; und

    wenn die Benutzereingabe einen Steuerbefehl angibt, Senden des Steuerbefehls an das zweite mobile Kommunikationsendgerät (100B), wodurch das Ausführen des Steuerbefehls durch das zweite mobile Kommunikationsendgerät (100B) bewirkt wird, wobei der Steuerbefehl eine Steuerfunktion des zweiten mobilen Kommunikationsendgeräts betrifft, und dadurch Verhindern einer vollständigen Kontrolle des zweiten mobilen Kommunikationsendgeräts (100B) durch das Zulassen nur eines Satzes von Steuerfunktionen, und

    wenn die Benutzereingabe zu teilende Daten angibt, Senden der zu teilenden Daten an das zweite mobile Kommunikationsendgerät (100B), wodurch das Präsentieren der zu teilenden Daten durch das zweite mobile Kommunikationsendgerät (100B) bewirkt wird,

    und wobei das zweite mobile Kommunikationsendgerät (100B) weiterhin zu Folgendem konfiguriert ist:

    Empfangen des Steuerbefehls und/oder der zu teilenden Daten von dem ersten mobilen Kommunikationsendgerät (100A); und

    Ausführen des Steuerbefehls, wenn ein Steuerbefehl empfangen wurde, und

    Präsentieren der zu teilenden Daten, wenn zu teilende Daten empfangen wurden.


     
    12. Verfahren zur Verwendung in einem mobilen Kommunikationsendgerät (100A), umfassend eine Benutzeroberfläche (120, 135, 130), wobei das Verfahren umfasst:

    Empfangen von Laufzeitdaten von einem zweiten mobilen Kommunikationsendgerät (100B), wobei die Laufzeitdaten einer Vielzahl von Statusangaben von mindestens einer Anwendung und/oder mindestens einer Ressource entsprechen, wobei die Laufzeitdaten keine Bildschirmkopien sind;

    automatisches Zusammenstellen eines zusammengestellten Gesamtstatus des zweiten mobilen Kommunikationsendgeräts (100B) auf der Grundlage der Laufzeitdaten, wobei der zusammengestellte Gesamtstatus dadurch Laufzeitdaten in Bezug auf mehrere Aspekte betrifft, wodurch die Vielzahl von Laufzeitdaten zu einem zusammengestellten Gesamtstatus vereinigt wird;

    Präsentieren des zusammengestellten Gesamtstatus über die Benutzeroberfläche (120, 130, 135);

    Empfangen einer Benutzereingabe über die Benutzeroberfläche (120, 130, 135), wobei die Benutzereingabe einen Steuerbefehl und/oder zu teilende Daten angibt; und

    wenn die Benutzereingabe einen Steuerbefehl angibt, Senden des Steuerbefehls an das zweite mobile Kommunikationsendgerät (100B), wodurch das Ausführen des Steuerbefehls durch das zweite mobile Kommunikationsendgerät (100B) bewirkt wird, wobei der Steuerbefehl eine Steuerfunktion des zweiten mobilen Kommunikationsendgeräts betrifft, und dadurch Verhindern einer vollständigen Kontrolle des zweiten mobilen Kommunikationsendgeräts (100B) durch das Zulassen nur eines Satzes von Steuerfunktionen, und

    wenn die Benutzereingabe zu teilende Daten angibt, Senden der zu teilenden Daten an das zweite mobile Kommunikationsendgerät (100B), wodurch das Präsentieren der zu teilenden Daten durch das zweite mobile Kommunikationsendgerät (100B) bewirkt wird.


     
    13. Verfahren zur Verwendung in einem System, umfassend ein erstes mobiles Kommunikationsendgerät (100A) und ein zweites mobiles Kommunikationsendgerät (100B), wobei das Verfahren umfasst:

    Erfassen von Laufzeitdaten von einem zweiten mobilen Kommunikationsendgerät (100B), wobei die Laufzeitdaten einer Vielzahl von Statusangaben von mindestens einer Anwendung und/oder mindestens einer Ressource entsprechen, wobei die Laufzeitdaten keine Bildschirmkopien sind;

    Übertragen der Laufzeitdaten an das erste mobile Kommunikationsendgerät (100A), wobei das Verfahren weiterhin umfasst:

    Empfangen der Laufzeitdaten von dem zweiten mobilen Kommunikationsendgerät (100B) am ersten mobilen Kommunikationsendgerät (100A);

    automatisches Zusammenstellen eines zusammengestellten Gesamtstatus des zweiten mobilen Kommunikationsendgeräts (100B) auf der Grundlage der Laufzeitdaten, wobei der zusammengestellte Gesamtstatus dadurch Laufzeitdaten in Bezug auf mehrere Aspekte betrifft, wodurch die Vielzahl von Laufzeitdaten zu einem zusammengestellten Gesamtstatus vereinigt wird;

    Präsentieren des zusammengestellten Gesamtstatus über die Benutzeroberfläche (120, 130, 135);

    Empfangen einer Benutzereingabe über die Benutzeroberfläche (120, 130, 135), wobei die Benutzereingabe einen Steuerbefehl und/oder zu teilende Daten angibt; und

    wenn die Benutzereingabe einen Steuerbefehl angibt, Senden des Steuerbefehls an das zweite mobile Kommunikationsendgerät (100B), wodurch das Ausführen des Steuerbefehls durch das zweite mobile Kommunikationsendgerät (100B) bewirkt wird, wobei der Steuerbefehl eine Steuerfunktion des zweiten mobilen Kommunikationsendgeräts betrifft, und dadurch Verhindern einer vollständigen Kontrolle des zweiten mobilen Kommunikationsendgeräts (100B) durch das Zulassen nur eines Satzes von Steuerfunktionen, und

    wenn die Benutzereingabe zu teilende Daten angibt, Senden der zu teilenden Daten an das zweite mobile Kommunikationsendgerät (100B), wodurch das Präsentieren der zu teilenden Daten durch das zweite mobile Kommunikationsendgerät (100B) bewirkt wird, und wobei das Verfahren weiterhin umfasst:

    Empfangen des Steuerbefehls und/oder der zu teilenden Daten von dem ersten mobilen Kommunikationsendgerät (100A) am zweiten mobilen Kommunikationsendgerät (100B); und

    Ausführen des Steuerbefehls, wenn ein Steuerbefehl empfangen wurde, und

    Präsentieren der zu teilenden Daten, wenn zu teilende Daten empfangen wurden.


     
    14. Computerlesbares Speichermedium (40), das mit Anweisungen (41) codiert ist, die beim Ausführen auf einem Prozessor das Verfahren nach Anspruch 11, 12 oder 13 durchführen.
     


    Revendications

    1. Terminal de communication mobile (100A) comprenant une interface utilisateur (120, 135, 130) et un contrôleur (210), dans lequel le contrôleur (210) est configuré de manière à :

    recevoir des données d'exécution en provenance d'un second terminal de communication mobile (100B), dans lequel les données d'exécution correspondent à une pluralité d'états d'au moins une application et/ou d'au moins une ressource, les données d'exécution n'étant pas des copies d'écran ;

    compiler automatiquement un état global compilé pour le second terminal de communication mobile (100B) sur la base des données d'exécution, l'état global compilé se rapportant par conséquent à des données d'exécution concernant plusieurs aspects, moyennant quoi les données de la pluralité de données d'exécution sont combinées en un état global compilé ;

    présenter l'état global compilé par l'intermédiaire de l'interface utilisateur (120, 130, 135) ;

    recevoir une entrée d'utilisateur par l'intermédiaire de l'interface utilisateur (120, 130, 135), l'entrée d'utilisateur indiquant une instruction de commande et/ou des données devant être partagées ; et

    si l'entrée d'utilisateur indique une instruction de commande, envoyer l'instruction de commande au second terminal de communication mobile (100B), ce qui permet d'amener par conséquent le second terminal de communication mobile (100B) à exécuter l'instruction de commande, dans lequel l'instruction de commande se rapporte à une fonction de commande du second terminal de communication mobile empêchant par conséquent la commande totale du second terminal de communication mobile (100B) en permettant uniquement la commande d'un ensemble de fonctions de commande ; et

    si l'entrée d'utilisateur indique des données devant être partagées, envoyer les données devant être partagées au second terminal de communication mobile (100B), ce qui permet par conséquent d'amener le second terminal de communication mobile (100B) à présenter les données devant être partagées.


     
    2. Terminal de communication mobile (100A) selon la revendication 1, dans lequel le contrôleur (210) est en outre configuré de manière à présenter des options d'instruction de commande correspondant à une fonction de commande devant être exécutée par le second terminal de communication mobile (100B), dans lequel l'entrée d'utilisateur indiquant une instruction de commande correspond à une activation d'une option d'instruction de commande, et dans lequel le second terminal de communication mobile (100B) est amené à exécuter l'instruction de commande en exécutant la fonction de commande correspondante.
     
    3. Terminal de communication mobile (100A) selon la revendication 1 ou 2, dans lequel le contrôleur (210) est en outre configuré de manière à compiler l'état global sur la base des données d'exécution, en classant au moins un aspect des données d'exécution et en compilant l'état global sur la base du classement dudit au moins un aspect des données d'exécution.
     
    4. Terminal de communication mobile (100A) selon l'une quelconque des revendications 1 à 3, dans lequel le contrôleur est en outre configuré de manière à compiler l'état global compilé sur la base d'une moyenne dudit au moins un aspect des données d'exécution.
     
    5. Terminal de communication mobile (100A) selon l'une quelconque des revendications 1 à 4, dans lequel le contrôleur est en outre configuré de manière à compiler l'état global compilé sur la base d'un aspect classé le plus bas parmi ledit au moins un aspect des données d'exécution.
     
    6. Terminal de communication mobile (100A) selon l'une quelconque des revendications 1 à 5, dans lequel le contrôleur est en outre configuré de manière à déterminer une action proposée à entreprendre, et à trouver une corrélation entre un aspect, présentant un classement faible, et une action, et à indiquer l'action proposée à entreprendre, par l'intermédiaire de l'interface utilisateur (120, 130, 135).
     
    7. Terminal de communication mobile (100A) selon la revendication 6, dans lequel l'action proposée à entreprendre consiste à envoyer un tutoriel au second terminal de communication mobile (100B), dans lequel le tutoriel est corrélé à un aspect des données d'exécution.
     
    8. Terminal de communication mobile (100A) selon la revendication 7, dans lequel le tutoriel à envoyer au second terminal de communication mobile est envoyé sous la forme d'un identificateur à un tutoriel téléchargeable devant être téléchargé par le second terminal de communication mobile (100B).
     
    9. Terminal de communication mobile (100) selon l'une quelconque des revendications 1 à 8, dans lequel le contrôleur (210) est en outre configuré de manière à recevoir une demande de connexion en provenance du second terminal de communication mobile (100B) et, après acceptation de la demande, à permettre au terminal de communication mobile (100A) de recevoir des données d'exécution en provenance du second terminal de communication mobile (100B).
     
    10. Terminal de communication mobile (100) selon l'une quelconque des revendications 1 à 9, dans lequel les données d'exécution se rapportent à une consommation de mémoire, à un niveau de batterie, à une consommation de batterie, à des appels manqués, à une fréquence d'utilisation pour une ou des applications spécifiques, à des messages d'erreur reçus pour une application/action, à une utilisation de mémoire, à une utilisation d'application, à un nombre d'activations d'interface utilisateur, par exemple des pressions de touches, tant virtuelle que physique, pour l'utilisation d'une application, à un nombre de messages non lus, et à un nombre de messages d'erreur reçus concernant un courriel.
     
    11. Système comprenant un premier terminal de communication mobile (100A) et un second terminal de communication mobile (100B),
    dans lequel le second terminal de communication mobile (100B) est configuré de manière à :

    collecter des données d'exécution, dans lesquelles les données d'exécution correspondent à une pluralité d'états d'au moins une application et/ou d'au moins une ressource, les données d'exécution n'étant pas des copies d'écran ; et

    transmettre les données d'exécution au premier terminal de communication mobile (100A) ;

    dans lequel le premier terminal de communication mobile (100A) est configuré de manière à :

    recevoir les données d'exécution en provenance du second terminal de communication mobile (100B) ;

    compiler automatiquement un état global compilé pour le second terminal de communication mobile (100B) sur la base des données d'exécution, l'état global compilé se rapportant par conséquent à des données d'exécution concernant plusieurs aspects, moyennant quoi les données de la pluralité de données d'exécution sont combinées en un état global compilé ;

    présenter l'état global compilé par l'intermédiaire de l'interface utilisateur (120, 130, 135) ;

    recevoir une entrée d'utilisateur par l'intermédiaire de l'interface utilisateur (120, 130, 135), l'entrée d'utilisateur indiquant une instruction de commande et/ou des données devant être partagées ; et

    si l'entrée d'utilisateur indique une instruction de commande, envoyer l'instruction de commande au second terminal de communication mobile (100B), ce qui permet d'amener par conséquent le second terminal de communication mobile (100B) à exécuter l'instruction de commande, dans lequel l'instruction de commande se rapporte à une fonction de commande du second terminal de communication mobile empêchant par conséquent la commande totale du second terminal de communication mobile (100B) en permettant uniquement la commande d'un ensemble de fonctions de commande ; et

    si l'entrée d'utilisateur indique des données devant être partagées, envoyer les données devant être partagées au second terminal de communication mobile (100B), ce qui permet par conséquent d'amener le second terminal de communication mobile (100B) à présenter les données devant être partagées ; et

    dans lequel le second terminal de communication mobile (100B) est en outre configuré de manière à :

    recevoir l'instruction de commande et/ou les données devant être partagées en provenance du premier terminal de communication mobile (100A) ; et

    si une instruction de commande est reçue, exécuter l'instruction de commande ; et

    si des données devant être partagées sont reçues, présenter les données devant être partagées.


     
    12. Procédé destiné à être utilisé dans un terminal de communication mobile (100A) comprenant une interface utilisateur (120, 135, 130), dans lequel le procédé comprend les étapes ci-dessous consistant à :

    recevoir des données d'exécution en provenance d'un second terminal de communication mobile (100B), dans lequel les données d'exécution correspondant à une pluralité d'états d'au moins une application et/ou d'au moins une ressource, les données d'exécution n'étant pas des copies d'écran ;

    compiler automatiquement un état global compilé pour le second terminal de communication mobile (100B) sur la base des données d'exécution, l'état global compilé se rapportant par conséquent à des données d'exécution concernant plusieurs aspects, moyennant quoi les données de la pluralité des données d'exécution sont combinées en un état global compilé ;

    présenter l'état global compilé par l'intermédiaire de l'interface utilisateur (120, 130, 135) ;

    recevoir une entrée d'utilisateur par l'intermédiaire de l'interface utilisateur (120, 130, 135), l'entrée d'utilisateur indiquant une instruction de commande et/ou des données devant être partagées ; et

    si l'entrée d'utilisateur indique une instruction de commande, envoyer l'instruction de commande au second terminal de communication mobile (100B), ce qui permet d'amener par conséquent le second terminal de communication mobile (100B) à exécuter l'instruction de commande, dans lequel l'instruction de commande se rapporte à une fonction de commande du second terminal de communication mobile empêchant par conséquent la commande totale du second terminal de communication mobile (100B) en permettant uniquement la commande d'un ensemble de fonctions de commande ; et

    si l'entrée d'utilisateur indique des données devant être partagées, envoyer les données devant être partagées au second terminal de communication mobile (100B), ce qui permet par conséquent d'amener le second terminal de communication mobile (100B) à présenter les données devant être partagées.


     
    13. Procédé destiné à être utilisé dans un système comprenant un premier terminal de communication mobile (100A) et un second terminal de communication mobile (100B), dans lequel le procédé comprend les étapes ci-dessous dans lesquelles ou consistant à :

    le second terminal de communication mobile (100B) collecte des données d'exécution, dans lequel les données d'exécution correspondent à une pluralité d'états d'au moins une application et/ou d'au moins une ressource, les données d'exécution n'étant pas des copies d'écran ; et

    transmettre les données d'exécution au premier terminal de communication mobile (100A), dans lequel le procédé comprend en outre les étapes ci-dessous dans lesquelles ou consistant à :

    le premier terminal de communication mobile (100A) reçoit les données d'exécution en provenance du second terminal de communication mobile (100B) ;

    compiler automatiquement un état global compilé pour le second terminal de communication mobile (100B), sur la base des données d'exécution, l'état global compilé se rapportant par conséquent à des données d'exécution concernant plusieurs aspects, moyennant quoi les données de la pluralité de données d'exécution sont combinées en un état global compilé ;

    présenter l'état global compilé par l'intermédiaire de l'interface utilisateur (120, 130, 135) ;

    recevoir une entrée d'utilisateur par l'intermédiaire de l'interface utilisateur (120, 130, 135), l'entrée d'utilisateur indiquant une instruction de commande et/ou des données devant être partagées ; et

    si l'entrée d'utilisateur indique une instruction de commande, envoyer l'instruction de commande au second terminal de communication mobile (100B), ce qui permet d'amener par conséquent le second terminal de communication mobile (100B) à exécuter l'instruction de commande, dans lequel l'instruction de commande se rapporte à une fonction de commande du second terminal de communication mobile empêchant par conséquent la commande totale du second terminal de communication mobile (100B) en permettant uniquement la commande d'un ensemble de fonctions de commande ; et

    si l'entrée d'utilisateur indique des données devant être partagées, envoyer les données devant être partagées au second terminal de communication mobile (100B), ce qui permet par conséquent d'amener le second terminal de communication mobile (100B) à présenter les données devant être partagées ; et dans lequel le procédé comprend en outre les étapes ci-dessous dans lesquelles ou consistant à :

    le second terminal de communication mobile (100B) reçoit l'instruction de commande et/ou les données devant être partagées en provenance du premier terminal de communication mobile (100A) ; et

    si une instruction de commande est reçue, exécuter l'instruction de commande ; et

    si des données devant être partagées sont reçues, présenter les données devant être partagées.


     
    14. Support de stockage lisible par ordinateur (40) codé avec des instructions (41) qui, lorsqu'elles sont exécutées sur un processeur, mettent en Ĺ“uvre le procédé selon la revendication 11, 12 ou 13.
     




    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