Method for receiving inputs from user of electronic device
Claim Score by NHIP
Abstract
A method of receiving inputs by an electronic device comprising a user interface component is disclosed. The user interface component is set in an inactive operating mode, such as a keypad locking mode or a screen saver mode, for substantially non-active usage of the user interface component. An input is received in the inactive mode. The input received in the inactive operating mode may be stored and presented on a user interface component.

Term
Term ended
Expired 20 September 2025, 1 year ago.
- Priority
- Filed
- Granted
- Expired
- Today
64 claims: 7 independent, 57 dependent
- 1An electronic device comprising a user interface component and a processing unit configured to set the user interface component in an inactive operating mode to be applied during non-active or limited usage of the user interface component, wherein the electronic device is configured to detect a user input on a touch screen during the inactive mode, the device is configured to store the user input during the inactive operating mode, the device is configured to activate an application for processing the stored user input after exiting the inactive operating mode, the device is configured to submit the user input for the application, and the device is configured to prompt the user for a further action after exiting the inactive operating mode.
- 10Broadest claimClaim Score 75, broad(NHIP)A method for receiving inputs by an electronic device comprising a user interface component, the method comprising:setting the user interface component in an inactive operating mode for non-active or limited usage of the user interface component, detecting a user input on a touch screen in the inactive mode, storing the user input during the inactive operating mode, activating an application for processing the stored user input after exiting the inactive operating mode, submitting the user input for the application, and prompting the user for a further action after exiting the inactive operating mode.
- 15A computer program product embodied on a computer readable medium downloadable into a memory of a data processing device comprising a user interface component and means for setting the user interface component in an inactive operating mode and executable in a processor of the data processing device, the computer program product comprising:a program code part for controlling the data processing device to store a user input during the inactive operating mode, a program code part for controlling the data processing device to activate an application for processing the stored user input after exiting the inactive operating mode, a program code part for controlling the data processing device to submit the user input for the application, and a program code part for controlling the data processing device to prompt the user for a further action after exiting the inactive operating mode.
- 18An apparatus, comprising:a processor;and a memory unit communicatively connected to the processor and including: computer code for controlling a data processing device to store a user input during an inactive operating mode, computer code for controlling the data processing device to activate an application for processing the stored user input after exiting the inactive operating mode, computer code for controlling the data processing device to submit the user input for the application, and computer code for controlling the data processing device to prompt the user for a further action after exiting the inactive operating mode.
- 23An apparatus, comprising:at least one processor;and at least one memory including computer program code that when executed by the at least one processor causes the apparatus at least to: change a user interface on a display of the apparatus from an active operating mode that is configured for active use of the user interface to an inactive operating mode where the inactive operating mode is configured for non-active usage or limited usage of one or more user interface components;during the inactive operating mode, enable detection of a user input for an application for processing the user input and wherein the detection can be done for any one of multiple applications;in the inactive operating mode and without entering the active operating mode and based on the user input, select the application for processing the user input and automatically activate the application and wherein the selection and activation can be done for any one of multiple applications;in the inactive operating mode and without entering the active operating mode and based on the user input, submit data representing the user input to the selected application;and wherein the user input, in the inactive operating mode and without entering the active operating mode, comprises voice recognition.
- 37A method, comprising:changing a user interface on a display of an apparatus from an active operating mode that is configured for active use of the user interface to an inactive operating mode where the inactive operating mode is configured for non-active usage or limited usage of one or more user interface components;during the inactive operating mode, enabling detection of a user input for an application for processing the user input and wherein the detection can be done for any one of multiple applications;in the inactive operating mode and without entering the active operating mode and based on the user input, selecting the application for processing the user input and automatically activating the application and wherein the selecting and activating can be done for any one of multiple applications;in the inactive operating mode and without entering the active operating mode and based on the user input, submitting data representing the user input to the selected application;and wherein the user input, in the inactive operating mode and without entering the active operating mode, comprises voice recognition.
- 51A non-transitory computer readable medium comprising program instructions configured for causing an apparatus to perform at least:change a user interface on a display of an apparatus from an active operating mode that is configured for active use of the user interface to an inactive operating mode where the inactive operating mode is configured for non-active usage or limited usage of one or more user interface components;during the inactive operating mode, enable detection of a user input for an application for processing the user input and wherein the detection can be done for any one of multiple applications;in the inactive operating mode and without entering the active operating mode and based on the user input, select the application for processing the user input and automatically activate the application and wherein the selecting and activating can be done for any one of multiple applications;in the inactive operating mode and without entering the active operating mode and based on the user input, submit data representing the user input to the selected application;and wherein the user input, in the inactive operating mode and without entering the active operating mode, comprises voice recognition.
Independent claims7
48 paragraphs in 6 sections, as filed
id="REI-00001" date="20220503"
CROSS REFERENCE TO RELATED APPLICATION
id="REI-00001"
0001More than one reissue application has been filed for U.S. Pat. No. 7,562,241, and this patent application is a continuation reissue of U.S. patent application Ser. No. 16/157,231, filed Oct. 11, 2018, which is a continuation reissue of Ser. No. 15/343,790, filed Nov. 4, 2016, now U.S. Pat. No. RE47,136, which is a continuation reissue of U.S. patent application Ser. No. 14/059,897, filed Oct. 22, 2013, now U.S. Pat. No. RE46,848, which is a continuation reissue of U.S. patent application Ser. No. 13/183,323, filed Jul. 14, 2011, now U.S. Pat. No. RE44,838, which is a reissue of U.S. patent application Ser. No. 11/231,119, filed Sep. 20, 2005, now U.S. Pat. No. 7,562,241, which claims foreign priority to PCT/FI2004/000563, filed Sep. 24, 2004, the disclosures of all of the foregoing being incorporated by reference herein in their entireties.
FIELD OF THE INVENTION
0002The invention relates to a solution for receiving inputs from a user of an electronic device, and more particularly to receiving inputs when a user interface component of an electronic device is in an inactive mode, for instance a screen saver functionality is active or a keypad lock is on.
BACKGROUND OF THE INVENTION
0003Various screen saver applications are well known for use in conventional computers. These screen savers are typically activated after a predetermined idle period and serve to save power and to avoid burn-in when CRT screens are used.
0004Portable electronic devices, such as mobile phones and PDA (Personal Digital Assistant) devices, have also been provided with screen saver applications, which enables battery power to be saved. For instance, current time is shown in the screen saver mode. U.S. patent application publication US 2003/0169306 discloses a more sophisticated screen saver in which handles for different applications may be displayed in the screen saver mode. If the user selects the handle, the respective application is executed in the screen saver mode, the application creating images shown on the screen. For instance, in the screen saver mode the user may select a handle to a weather application, whereby weather information is shown on the screen.
0005A keypad lock is another exemplary user interface mode for inactive use, typically enabling unwanted keypad inputs in portable devices to be avoided. The keypad lock may be activated automatically or by the user, and may be applied simultaneously with the screen saver facility.
0006The user may face sudden situations in which a need arises to make notes. However, it is not always so easy to make notes quickly. Typically, when a user wishes to make notes, he/she needs to exit the screen saver mode and/or keypad lock by a keystroke, go to menu, select the appropriate application (e.g. a notepad), and activate the application. Only after the application has been activated, can the user make the notes. Especially when the user is moving, this procedure is not very user-friendly or quick.
BRIEF DESCRIPTION OF THE INVENTION
0007An object of the invention is thus to provide a method and an apparatus implementing the method so as to enable the above-mentioned problems to be avoided or at least alleviated. The object of the invention is achieved by a method, a portable electronic device, a computer program and a computer program product which are characterized by what has been disclosed in the independent claims. Some embodiments of the invention are disclosed in the dependent claims.
0008According to an aspect of the invention, an electronic device comprising a user interface component and means for setting the user interface component in an inactive operating mode to be applied during non-active or limited usage of the user interface component is configured to store an input in an inactive operating mode, such as a keypad locking mode or a screen saver mode. The device is further configured to perform an action for the stored input.
0009The term “inactive operating mode” generally refers to any mode intended for non-active or limited usage of one or more user interface components, for instance screen saver mode or keypad lock mode. An advantage of the arrangement of the invention is that notes may be made quickly and easily although the user interface component of the device is in an inactive mode. There is no need to exit the inactive mode by a keystroke, go to menu, select the appropriate application (e.g. a notepad), and activate the appropriate application before being able to make notes, but notes may be made quickly during the inactive mode. This improves the usability of portable electronic devices. Besides storing, further actions, during the inactive mode or after exiting the inactive mode, may be performed on the input. For instance, the input may be forwarded to another device or application. According to an embodiment of the invention, the device is configured to present the input received during the inactive operating mode in a user interface component.
0010According to another embodiment of the invention, an application is activated to which data representing an input received in the inactive mode is then fed. This embodiment enables automatic processing of the input by the application, and it is possible to arrange different types of information to be inputted in the inactive mode. Alternatively, only an application specific input may be arranged in the inactive mode.
0011According to an embodiment of the invention, an input area is arranged on the screen when the user interface component is set to inactive operating mode. Inputs from the user to the input area are then received and stored. This embodiment enables one portion of the screen to be used for inputs, and other parts of the screen may be used for a screen saver facility, for instance.
0012According to another embodiment of the invention, a device is configured to receive an input, trigger the arrangement of the input reception means, or detect an input as an appropriate input in the inactive operating mode if a predetermined activation input has been received from the user when the device is in the inactive operating mode. This embodiment enables unwanted inputs to be avoided or at least reduced, for instance when the device is in the user's pocket.
BRIEF DESCRIPTION OF THE DRAWINGS
0013The invention is now described in closer detail in connection with some embodiments and with reference to the accompanying drawings, in which
0014<figref idref="DRAWINGS">FIG. 1</figref> is a block diagram illustrating some parts of a portable electronic device according to an embodiment;
0015<figref idref="DRAWINGS">FIG. 2</figref> shows a screen view according to an embodiment;
0016<figref idref="DRAWINGS">FIG. 3</figref> is a flow diagram showing a method according to an embodiment, and
0017<figref idref="DRAWINGS">FIG. 4</figref> is a flow diagram showing a method according to another embodiment.
DETAILED DESCRIPTION OF THE INVENTION
0018As illustrated in <figref idref="DRAWINGS">FIG. 1</figref>, an electronic device ED comprises a memory MEM, a user interface, means I/O for arranging data transfer, and a processing unit PU comprising one or more processors. The user interface of the ED comprises at least a screen SC and in this embodiment also a keypad KP. Various applications APP may be implemented in the electronic device ED by executing, in the PU, a computer program code stored in the memory MEM.
0019In one embodiment, data may be transmitted to/from the electronic device ED, for instance wirelessly. Conventional transceivers and functionality for communicating with a network and/or other mobile terminals may be included in the electronic device ED. For instance, the electronic device ED may support GSM (Global System for Mobile Communications), GPRS (General Packet Radio Service), 3GPP (3<sup>rd </sup>Generation Partnership Project), WLAN (Wireless Local Area Network) and/or Bluetooth standards. The electronic device ED may be a data processing device, such as a laptop, a desktop computer, a PDA device, a mobile station, a media device such as the Nokia 7700, or a removable/portable module for some of the above-mentioned devices.
0020A screen saver functionality may be arranged in the electronic device ED by a screen saver program code executed in the processing unit PU, such screen saver facility being represented in <figref idref="DRAWINGS">FIG. 1</figref> by reference SCS. When the screen saver SCS is activated, the screen SC is set to an inactive operating mode in which a screen saver icon is displayed, for instance. The device ED of <figref idref="DRAWINGS">FIG. 1</figref> also comprises a keypad (KP) lock facility represented by reference KPL. The activation of the keypad lock KPL causes the keypad to be set into such an inactive operating mode in which only a very limited number of inputs (for instance for initiating an emergency call and for unlocking the keypad) is accepted in order to avoid unwanted keypad inputs during non-active use of the device. It is to be noted that the keypad lock, depending of the device type, may lock a physical keypad or a keypad arranged in a touch screen of an electronic device.
0021Computer program codes executed in the central processing unit PU may correspondingly enable the electronic device ED also to implement the inventive means relating to receiving inputs from the user while a user interface component is in an inactive mode, for instance when the screen saver SCS is active and/or while the keypad lock is on. Some embodiments of such means are illustrated in connection with <figref idref="DRAWINGS">FIGS. 2, 3 and 4</figref>. The computer program may be stored in a memory, e.g. on a hard disk of a PC or on a CD-ROM disc wherefrom it may be downloaded into the memory MEM of the electronic device ED executing the program. The computer program may also be downloaded via a network by using e.g. a TCP/IP protocol stack. The computer program may be a specific application for providing the inventive means and/or part of a software package comprising software also for other purposes. For instance, the software enabling user inputs during a screen saver mode as illustrated in <figref idref="DRAWINGS">FIG. 3</figref> may be part of screen saver software downloadable to the electronic device ED. In another example, the inputs during the inactive mode are processed by a specific application which stores the inputs and/or forwards them to other applications. It is also feasible to use hardware solutions or a combination of hardware and software solutions to implement the inventive means.
0022In one embodiment, the screen SC of the device ED is a touch screen. The present method can be applied in connection with substantially all touch screen types, but the touch screen type used per se is irrelevant to the implementation of the invention. The implementation of a touch screen may be based on one of the following techniques, for instance: electrical methods, a technology based on infrared light, a technology based on sound waves or pressure recognition. Some touch screen types require a stylus with integrated electronics, such as a resonance circuit. The operation of such a screen requires a stylus to be used, and the screen cannot be used by pointing with a finger, for instance. This kind of screen type also allows a virtual stylus to be used.
0023<figref idref="DRAWINGS">FIG. 2</figref> illustrates a screen view of an electronic device ED according to an embodiment in which a user input area <b>200</b> is arranged in the screen SC when at least one user interface component of the device ED is set to an inactive operating mode. In the example of <figref idref="DRAWINGS">FIG. 2</figref>, the input area <b>200</b> is limited by the dashed line, and an input made to the area <b>200</b> is detected even though the screen saver SCS and/or the keypad lock KPL, for instance, are/is active. Touch inputs to the input area <b>200</b> may be detected by touch sensitive elements in the screen SC, converted to an appropriate electronic format and displayed on the screen SC. The input area <b>200</b> for inputs in the inactive operating mode may be arranged such that only those input detection elements that reside in the area <b>200</b> are active and/or inputs from these elements are only accepted as valid input. If the screen saver SCS is activated, the screen saver SCS in this example only displays a block <b>201</b> showing time, the block <b>201</b> being arranged to change its place on the screen SC. In one embodiment, the movement of a screen saver object, such as the block <b>201</b>, is arranged such that the object does not appear in the input area <b>200</b>. However, it is to be noted that the input area <b>200</b> may cover the whole screen area. In such a case, any screen saver objects could move around the input area. It is also possible that multiple input areas <b>200</b> are arranged.
0024In the example of <figref idref="DRAWINGS">FIG. 2</figref>, the user has made notes to the input area <b>200</b> by a stylus. Based on the detected touching points of the stylus to the input area <b>200</b>, the input area <b>200</b> has been refreshed to show the movements of the stylus. The user can thus make notes very quickly directly to the screen SC. The notes made by the user may be stored and further processed, as will be illustrated by embodiments below.
0025In an alternative embodiment, a cursor is arranged on the screen (SC). The device ED is then configured to determine the inputs in the input area <b>200</b> on the basis of the detected movements of the cursor. The cursor may be controlled by a conventional keypad KP or a specific control means, such as a track ball, for instance.
0026According to yet another embodiment, the inputs during the inactive mode are received by a conventional keypad (KP). The input area <b>200</b> may also be used and used as default for keypad inputs, or the input area <b>200</b> could be selected by a specific keystroke or cursor positioning, for instance. Thus, the invention may also be applied in devices having no touchscreen.
0027According to some embodiments, a predetermined activation input may be required from the user in order to enter an input (to the input area <b>200</b> or another input means arranged during the inactive mode) to trigger establishment of the input area <b>200</b> in the data processing device ED, and/or to detect an input as an appropriate input when in the inactive mode. This embodiment may be applied with some or all of the above-illustrated input methods. The input could be a simultaneous key press when making notes to the input area, for instance. Thus, inputs can be made if the specific key is pushed at the same time. In an alternative embodiment, a specific key combination has to be pushed before inputs can be made in the screen saver mode. In another embodiment, a stylus storage/fastening means on the data processing device ED are equipped with a sensor detecting removal of the stylus. A sensor may be connected to the present functionality such that the removal of the stylus is detected as an activation input. For instance, the input area <b>200</b> is automatically established after the stylus is removed from the storage position. In another embodiment, the required activation input could be a push of a track ball (moving the cursor) in a particular position or a push of an additional key. These embodiments enable unnecessary inputs caused by unwanted keys strokes or by other kinds of input methods to be avoided or reduced. The application of a predetermined activation input is especially useful in combination with a keypad input since easily occurring unwanted keypad inputs may then be avoided or at least reduced.
0028<figref idref="DRAWINGS">FIG. 3</figref> illustrates a method according to an embodiment. The method is implemented by the data processing device ED, in one embodiment the steps of <figref idref="DRAWINGS">FIG. 3</figref> are controlled by the screen saver SCS functionality. In step <b>301</b>, the screen saver (SCS) is activated based on a screen saver initiation trigger, which could be a predetermined idle period after the last input from the user. An input area (<b>200</b>) is arranged on the screen (SC) in step <b>302</b>. The data processing device ED is in steps <b>303</b>, <b>304</b> configured to receive any inputs from the user. The process may actively continuously check whether any input is received (<b>303</b>, <b>304</b>) or passively act (enter step <b>305</b>) when an input is received from input detection means, such as touch screen means.
0029When an input is received, it is determined <b>305</b> whether the input is for deactivating the screen saver (SCS). If so, the screen saver is deactivated <b>306</b> and the current screen saver mode specific process may end. In one embodiment, a specific key or key combination is predetermined as the trigger for deactivating the screen saver. Thus, the device is configured to check in step <b>305</b> whether the input from the user matches the trigger. If the input matches the trigger, the device is configured to deactivate the screen saver and to remove the input area (<b>200</b>).
0030If the input is not for deactivating the screen saver, the device is configured to store the data representing the input and/or to display <b>307</b> the input. It is to be noted that instead of or in addition to the step of displaying the input, other actions may be performed for the input, as will be illustrated below. After step <b>307</b>, the process may return to step <b>303</b> to detect new inputs.
0031<figref idref="DRAWINGS">FIG. 4</figref> is a flow diagram showing a method according to another embodiment. The method of <figref idref="DRAWINGS">FIG. 4</figref> may be applied when a keypad lock (KPL) is activated <b>401</b>, based on an input from the user or automatically. Similarly to that shown in <figref idref="DRAWINGS">FIG. 3</figref>, an input area is arranged <b>402</b> and inputs monitored <b>403</b>. If an input is for removing the keypad lock, the keypad lock is removed <b>405</b>. Otherwise the input may be stored and/or displayed in step <b>407</b> to the user.
0032As already mentioned, a predetermined activation input may also be required in the embodiment for a keypad lock (KPL). In one embodiment, a specific key needs to be pushed during input in order to enter an input, to trigger establishment of the input area <b>200</b> in the data processing device ED, and/or to detect an input as an appropriate input. In another embodiment, a specific activation area on the screen SC needs to be selected (for instance a small icon needs to be contacted by the stylus) in order to establish the input area <b>200</b>. Further, the time for supplying the inputs after the activation of the input area <b>200</b> may be limited.
0033It is to be noted that the methods in <figref idref="DRAWINGS">FIGS. 3 and 4</figref> may also be utilized simultaneously. For instance, when either the keypad lock or the screen saver mode is set, an input area is arranged, and no other input area is needed if the other is also activated later. The methods in <figref idref="DRAWINGS">FIGS. 3 and 4</figref> are only some examples of arranging the inventive functionality. For instance, in an alternative method, only the inputs to the input area (<b>200</b>) are monitored and the detection of the screen saver deactivation and/or keypad lock removal input is a separate process to be executed by the screen saver (SCS). Thus, the input detection in the input area may be carried out by some entity other than the screen saver SCS.
0034As already mentioned, instead of the input area (<b>200</b>), the inputs during the inactive mode may be arranged by some other input method. For instance, voice recognition or a touch screen/keypad input without any input area <b>200</b> could be used.
0035In another embodiment, the input area (<b>200</b>) is removed, either automatically or on the basis of a user input. This may be carried out after step <b>307</b>/<b>407</b> or when a predetermined time period has elapsed after the activation of the input area <b>200</b>, for instance. Further, this feature may be provided such that the inactive operating mode may still be continued. In an embodiment, a selectable icon or another type of input means is arranged in the data processing device ED for removing the input area (<b>200</b>) and returning to the basic screen saver mode without any input possibility. This further enables unwanted inputs to the input area to be avoided after the appropriate input has been created and/or stored. Further, as noted above, the input area <b>200</b> may be arranged on the basis of a predetermined key combination or another specific input from the user for triggering the establishment of the input area <b>200</b>. Thus, after an appropriate input from the user, step <b>302</b> may be entered again. In a further alternative embodiment, also the screen saver is deactivated and/or the keypad lock is removed after step <b>307</b>/<b>407</b>.
0036In the following, some embodiments will be illustrated, the features of which may be implemented instead of or in addition to step <b>307</b> in <figref idref="DRAWINGS">FIG. 3</figref>.
0037According to an embodiment, the data processing device ED is configured to prompt the user for one or more further actions regarding the input. This feature may be carried out immediately after detecting the input or after the inactive operating mode is exited (after step <b>306</b>/<b>406</b>), for instance. In the first case, the inactive operating mode may be continued after an input has been received from the user and the one or more further actions have been carried out. For instance, the user may be requested to confirm the storage of the input and to select a storage position and a file name for the input. For this, a file folder view may be displayed for the user. In accordance with a received user input, the input is then stored (or not stored if the user input indicates this). It is to be noted that the input may be stored temporarily in step <b>307</b> or <b>407</b>, and when the screen saver is deactivated <b>306</b> or the keypad lock is removed <b>406</b>, the user may be prompted for the final storage of the input.
0038In an embodiment, the user is prompted to select an application and/or a file format for the input. The application and/or file type/format is then selected for the input in accordance with an input from the user. For instance, the user may determine that the input is a calendar entry, a note or an alarm. The input may then be stored in accordance with the selected format. It is possible thus to define the format of the input without necessarily activating the application already immediately after the deactivation of the screen saver mode or during the screen saver mode (for instance in step <b>307</b>).
0039According to an embodiment, the data processing device ED is configured to activate an application (APP) for which the inputs in the inactive mode are submitted. The application to be activated may be selected on the basis of a user input as illustrated above, or in an automatic manner based on one or more properties of the input. This application may then process the data representing the input as appropriate, for instance display it (possibly in an application specific view), store it, and/or further process it in an application specific way. In one embodiment, the application is activated after the screen saver mode is deactivated <b>306</b> and/or after a keypad lock is removed <b>406</b>, whereby the usage of the data processing device ED resources can be minimized when the data processing device ED is not actively used. The input may then be displayed when the active usage mode begins and the user may then return to his/her notes and further process them, for instance. It is possible to prompt the user for confirmation before activating the application for the input.
0040In a further embodiment, the device ED is configured to determine the type of the input received during the inactive mode. On the basis of the detected type or format of the input, the device ED is configured to select an appropriate application (APP) for processing the input. The device may be configured to activate the selected application and/or submit the data representing the input to the selected application. This embodiment enables multiple applications (APP) to which the input may be targeted, and the appropriate application may be automatically activated without any user input for selecting the application. According to another embodiment, the storage format may be defined (for instance in step <b>307</b>/<b>407</b>) on the basis of the determination of the type or format of the input.
0041According to one embodiment, the input area <b>200</b> is an application-specific view. The input area may be arranged for entering data for at least one of the following applications: a word processing application, a phonebook or another contact management application, a notepad application, a calendar application, a messaging application, a drawing application, or a spreadsheet application. The respective application may be actively executed when in a screen saver mode, activated upon an input to the input area, or inputs may be buffered and submitted to the application when it is later activated, for instance when the screen saver is deactivated. The device ED may be configured to receive inputs for at least one of the above-mentioned applications by some alternative input method not involving the input area <b>200</b>.
0042According to another embodiment, the device ED comprises a text recognition application and is configured to submit the input to the text recognition application for determining the text data representing the input. This embodiment thus enables free-form entries in the inactive mode to be converted to complete text for a text-processing application. Further, the recognized text could then be displayed in the application view and stored as a text document, even automatically. In another embodiment, instructions from the user for controlling one or more of the functions of the data processing device may be carried out based on the detected text format. For instance, if an input representing command “STORE” is detected, the device activates storage of the input in the input area associated with the detected store command.
0043According to yet another embodiment, the input is submitted to at least one external device such as a network element. The input may thus be transmitted using a transmitter of the electronic device ED. For instance, the input may be submitted by a short range data transmission technique to local device(s). Alternatively, an appropriate message may be formed for the input for transmission to a mobile network such as one in accordance with the 3GPP system. For instance, the input may be included in a short message sent to a short message center.
0044In a further embodiment the input is submitted to a network element performing some further action for the input. The input may then be stored in the network and/or used for some service by the network.
0045In one embodiment the data processing device comprises a client for mobile instant messaging and presence service (IMPS). The input may be submitted to the client which then arranges the transmission of the input by a IMPS specific message to a IMPS server. In some alternative solutions the input area <b>200</b> is for entering inputs to the IMPS, or an IMPS application is activated in the ED on the basis of predetermined activation input. The IMPS server may store the input in the data processing device's information and possibly submit this information to other IMPS clients (authorized to receive IMPS information of the data processing device ED) as presence information or as an instant message. More information on one feasible IMPS solution is available at the OMA (Open Mobile Alliance) WWW site (www.openmobilealliance.org). It is to be noted that the ED may be arranged to support only a presence or an instant messaging application instead of both of them. This embodiment enables the user of the data processing device ED to easily specify personal presence information for an interest group even when the device ED is in an inactive mode. For instance, when the keypad lock is active, the user could still quickly input words “In meeting” and activate transmission of this message to the IMPS system, which then automatically distributes this information to his friends. In another example the user could easily change his or her status in the IMPS system by selecting another status via the user interface of the ED although the screen saver SCS would be activated in the ED.
0046It should be appreciated that the above-illustrated embodiment may be combined in various ways. It is obvious to one skilled in the art that as technology advances, the basic idea of the invention may be implemented in many different ways. The invention and its embodiments are thus not restricted to the above examples but may vary within the scope of the claims. Different features may thus be omitted, modified or replaced by equivalents.
Contents6
5 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| EP1263199A2 | Cites | European Patent Office (EPO) | Applicant |
| EP1396813A1 | Cites | European Patent Office (EPO) | Applicant |
| US2002023237A1 | Cites | United States of America | Applicant |
| JP2002082734A | Cites | Japan | Applicant |
| US2002083357A1 | Cites | United States of America | Search report |
| US2002130868A1 | Cites | United States of America | Search report |
| US2002196294A1 | Cites | United States of America | Applicant |
| US2002198909A1 | Cites | United States of America | Search report |
| US2003054862A1 | Cites | United States of America | Applicant |
| US2003169306A1 | Cites | United States of America | Applicant |
| US2004015732A1 | Cites | United States of America | Applicant |
| US2004049533A1 | Cites | United States of America | Search report |
| WO2004077782A1 | Cites | World Intellectual Property Organization (WIPO) | Applicant |
| US2004093582A1 | Cites | United States of America | Applicant |
| US2004100457A1 | Cites | United States of America | Applicant |
| US2005221791A1 | Cites | United States of America | Search report |
| US2005239518A1 | Cites | United States of America | Search report |
| US2006046694A1 | Cites | United States of America | Applicant |
| US2006073813A1 | Cites | United States of America | Applicant |
| US2010123724A1 | Cites | United States of America | Applicant |
| US2011047368A1 | Cites | United States of America | Applicant |
| US2011137548A1 | Cites | United States of America | Applicant |
| US2012226912A1 | Cites | United States of America | Applicant |
| US2012284789A1 | Cites | United States of America | Applicant |
| US2012311499A1 | Cites | United States of America | Applicant |
| US5546538A | Cites | United States of America | Search report |
| US5706457A | Cites | United States of America | Search report |
| US5790875A | Cites | United States of America | Applicant |
| US5852436A | Cites | United States of America | Applicant |
| US6073187A | Cites | United States of America | Applicant |
| US6105142A | Cites | United States of America | Applicant |
| US6256008B1 | Cites | United States of America | Applicant |
| US6457134B1 | Cites | United States of America | Applicant |
| US6523124B1 | Cites | United States of America | Applicant |
| US6525716B1 | Cites | United States of America | Search report |
| US6633318B1 | Cites | United States of America | Applicant |
| US6683605B1 | Cites | United States of America | Applicant |
| US6782484B2 | Cites | United States of America | Applicant |
| US6892081B1 | Cites | United States of America | Applicant |
| US6903743B2 | Cites | United States of America | Applicant |
| US6938174B2 | Cites | United States of America | Search report |
| US6943667B1 | Cites | United States of America | Applicant |
| US6973664B2 | Cites | United States of America | Applicant |
| US7004394B2 | Cites | United States of America | Search report |
| US7240228B2 | Cites | United States of America | Search report |
| US7248146B1 | Cites | United States of America | Applicant |
| US7301910B2 | Cites | United States of America | Search report |
| US7373537B2 | Cites | United States of America | Applicant |
| US7421602B2 | Cites | United States of America | Applicant |
| US7484106B2 | Cites | United States of America | Applicant |
| US7925298B2 | Cites | United States of America | Applicant |
| JPH10106919A | Cites | Japan | Applicant |
| USRE44838E | Cites | United States of America | Applicant |
| US20020023237A1 | Cites | United States of America | Applicant |
| US20020083357A1 | Cites | United States of America | Search report |
| US20020130868A1 | Cites | United States of America | Search report |
| US20020196294A1 | Cites | United States of America | Applicant |
| US20020198909A1 | Cites | United States of America | Search report |
| US20030054862A1 | Cites | United States of America | Applicant |
| US20030169306A1 | Cites | United States of America | Applicant |
| US20040015732A1 | Cites | United States of America | Applicant |
| US20040049533A1 | Cites | United States of America | Search report |
| US20040093582A1 | Cites | United States of America | Applicant |
| US20040100457A1 | Cites | United States of America | Applicant |
| US20050221791A1 | Cites | United States of America | Search report |
| US20050239518A1 | Cites | United States of America | Search report |
| US20060046694A1 | Cites | United States of America | Applicant |
| US20060073813A1 | Cites | United States of America | Applicant |
| US20100123724A1 | Cites | United States of America | Applicant |
| US20110047368A1 | Cites | United States of America | Applicant |
| US20110137548A1 | Cites | United States of America | Applicant |
| US20120226912A1 | Cites | United States of America | Applicant |
| US20120284789A1 | Cites | United States of America | Applicant |
| US20120311499A1 | Cites | United States of America | Applicant |
| EP1263199A2 | Cites | European Patent Office (EPO) | Applicant |
| EP1396813A1 | Cites | European Patent Office (EPO) | Applicant |
| JPH10106919A | Cites | Japan | Applicant |
| WO2004077782A1 | Cites | World Intellectual Property Organization (WIPO) | Applicant |
| IBM Technical Disclosure Bulletin; Jan. 1989; vol. 31, No. 8; pp. 28-29. | Non-patent | – | Applicant |
| Carroll, A. et al.; “An Analysis of Power Consumption in a Smartphone”; Jun. 25, 2010; 2010 USENIX Annual Technical Conference; pp. 1-14. | Non-patent | – | Applicant |
| Lawrence S. Brakmo,, Deborah A. Wallach, Marc A. Viredaz, “uSleep: A Technique for Reducing Energy Consumption in Handheld Devices” Mobile and Media Systems Laboratory, HP Laboratories Palo Alto, HPL-2004-11, Jan. 22, 2004. | Non-patent | – | Applicant |
| IBM Technical Disclosure Bulletin; Jan. 1989; vol. 31, No. 8; pp. 28-29. | Non-patent | – | Applicant |
| Carroll, A. et al.; “An Analysis of Power Consumption in a Smartphone”; Jun. 25, 2010; 2010 USENIX Annual Technical Conference; pp. 1-14. | Non-patent | – | Applicant |
| Lawrence S. Brakmo,, Deborah A. Wallach, Marc A. Viredaz, “uSleep: A Technique for Reducing Energy Consumption in Handheld Devices” Mobile and Media Systems Laboratory, HP Laboratories Palo Alto, HPL-2004-11, Jan. 22, 2004. | Non-patent | – | Applicant |
12 members in 4 offices
Priority claims7
| Document | Office | Kind | Date |
|---|---|---|---|
| PCTFI2004000563 | World Intellectual Property Organization (WIPO) | – | |
| 2004000563 | Finland | W | |
| 23111905 | United States of America | A | |
| 201113183323 | United States of America | A | |
| 201314059897 | United States of America | A | |
| 201615343790 | United States of America | A | |
| 201816157231 | United States of America | A |
Members12
| Document | Office | Kind | |
|---|---|---|---|
| WO2006032721A1 | World Intellectual Property Organization (WIPO) | A1 | |
| US2006117197A1 | United States of America | A1 | |
| BRPI0419168A | Brazil | A | |
| JP2008515039A | Japan | A | |
| US7562241B2 | United States of America | B2 | |
| JP4773448B2 | Japan | B2 | |
| USRE44838E | United States of America | E | |
| BRPI0419168B1 | Brazil | B1 | |
| USRE46848E | United States of America | E | |
| USRE47136E | United States of America | E | |
| USRE49041E | United States of America | E | |
| USRE49058EThis record | United States of America | E |
60 transactions on the USPTO file
Allowed after 1 non-final rejection, 1 final rejection and 1 RCE.
- Non-final rejections
- 1
- Final rejections
- 1
- RCEs
- 1
- Appeals
- 0
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Email NotificationEML_NTR | EML_NTR | |
| Application ready for PDX access by participating foreign officesCCRDY | CCRDY | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Dispatch to FDCD1935 | D1935 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Email NotificationEML_NTR | EML_NTR | |
| Mailing Corrected Notice of AllowabilityMCNOA | MCNOA | |
| Email NotificationEML_NTR | EML_NTR | |
| Reasons for AllowanceEX.R | EX.R | |
| Corrected Notice of AllowabilityCNOA | CNOA | |
| Filing Receipt - CorrectedFLRCPT.C | FLRCPT.C | |
| Pubs Case Remand to TCPUBTC | PUBTC | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Reasons for AllowanceEX.R | EX.R | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Email NotificationEML_NTR | EML_NTR | |
| Mail Advisory Action (PTOL - 303)MCTAV | MCTAV | |
| Advisory Action (PTOL-303)CTAV | CTAV | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Final ActionA.NE | A.NE | |
| Substitute Specification FiledC604 | C604 | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Substitute Specification FiledC604 | C604 | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Notice of Reissue Published in Official GazetteNRE. | NRE. | |
| Paralegal Reissue Review CompletePRIR | PRIR | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Email NotificationEML_NTR | EML_NTR | |
| Application Is Now CompleteCOMP | COMP | |
| Filing ReceiptFLRCPT.O | FLRCPT.O | |
| Application Dispatched from OIPEOIPE | OIPE | |
| FITF set to NO - revise initial settingFTFI | FTFI | |
| Preliminary AmendmentA.PE | A.PE | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| PTO/SB/69-Authorize EPO Access to Search ResultsSREXR141 | SREXR141 | |
| Applicants have given acceptable permission for participating foreignAPPERMS | APPERMS | |
| Cleared by OIPE CSRL194 | L194 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Entity Status Set To Undiscounted (Initial Default Setting or Status Change)BIG. | BIG. | |
| Initial Exam Team nnIEXX | IEXX |
1 legal event, as the office reported them to INPADOC
Events
| Event | Code | |
|---|---|---|
| Fee payment procedureENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP | FEPP |
Numbers
- Publication
- RE049058
- Application
- 16998218
Titles
- English
- Method for receiving inputs from user of electronic device
Classification
- CPC, 4
- G06F3/0488
- G06F1/3215
- H04M1/67
- H04M2250/22
- IPC, 7
- G06F1 32
- G06F3 0488
- G06F1 3215
- H04M1 67
- G06F3 048
- G06F3 0489
- G06F3 04895