WO2011073712A1

WO2011073712A1 - Method and apparatus for having multiple identities on a mobile device

Info

Publication number: WO2011073712A1
Application number: PCT/IB2009/007826
Authority: WO
Inventors: Kai Allan Inha
Original assignee: Nokia Corporation
Priority date: 2009-12-18
Filing date: 2009-12-18
Publication date: 2011-06-23

Abstract

In accordance with an example embodiment of the present invention, an apparatus comprising: at least one memory including user data for a plurality of users, an interface configured to receive a user's personal key, and at least one processor configured to provide user data associated with a user when the user's personal key is connected through said interface.

Description

METHOD AND APPARATUS FOR HAVING MULTIPLE

IDENTITIES ON A MOBILE DEVICE

TECHNICAL FIELD

[0001] The present application relates generally to having multiple identities on a mobile device. BACKGROUND

[0002] The use of mobile devices is increasing rapidly and mobile devices are becoming a part of people's life.

SUMMARY

[0003] Various aspects of examples of the invention are set out in the claims.

[0004] According to a first aspect of the present invention, an apparatus comprising:at least one memory including user data for a plurality of users, an interface configured to receive a user's personal key, and at least one processor configured to provide user data associated with a user when the user's personal key is connected through said interface.

[0005] According to a second aspect of the present invention, a method comprising: storing user data for a plurality of users on a mobile device, and when a user's personal key is connected to the mobile device, providing the user data associated with the user to the user.

[0006] According to a third aspect of the present invention, a computer program product comprising a computer-readable medium bearing computer program code embodied therein for use with a computer, the computer program code comprising: code for storing user data for a plurality of users on a mobile device, and code for pairing and unpairing a unique identifier associating with the entire storage space and functionalities, or for limiting storage space and functionalities or user data areas.

[0007] According to a fourth aspect of the present invention, a personal key comprising: means to connect to a mobile device, and a unique identifier that can be read and used by the mobile device to activate user data associated with a user among a plurality of user data stored on the mobile device.

BRIEF DESCRIPTION OF THE DRAWINGS

[0008] For a more complete understanding of example embodiments of the present invention, reference is now made to the following descriptions taken in connection with the accompanying drawings in which: [0009] FIGURE 1 is a block diagram depicting an electronic device operating in accordance with an example embodiment of the invention;

[0010] FIGURE 2 is a block diagram depicting a personal key operating in accordance with an example embodiment of the invention;

[0011] FIGURE 3 is a flow diagram illustrating an example method for providing a user's data with a personal key in accordance with an example embodiment of the invention;

[0012] FIGURE 4 is a flow diagram illustrating an example method for locking a user's data in accordance with an example embodiment of the invention;

[0013] FIGURE 5 is a block diagram depicting an electronic device and personal keys operating in accordance with an example embodiment of the invention; and

[0014] FIGURE 6 is a picture illustrating an example use case operating in accordance with an example embodiment of the invention.

DETAILED DESCRIPTON OF THE DRAWINGS

[0015] An example embodiment of the present invention and its potential advantages are understood by referring to FIGURES 1 through 6 of the drawings. Multiple users in a family could share one mobile device. In addition, mobile device can be rented or given to third party to make a call. Furhtermore, the same user can have multuiple profiles in the same mobile device.

[0016] FIGURE 1 is a block diagram depicting an electronic device 100 operating in accordance with an example embodiment of the invention. In an example embodiment, the electronic device 100 comprises a processor 110 or other processing component. In an example embodiment, the electronic device 100 may comprise multiple processors, such as processor 110. In an example embodiment, the electronic device 100 also comprises a user interface 130. The user interface 130 comprises one or more input or output components, such as a universal serial bus (USB) connector, an audio/video jack, and/or the like.

[0017] In an embodiment, an electronic device 100 may comprise memory 120. For example, the electronic device may comprise volatile memory, such as random access memory (RAM). Volatile memory may comprise a cache area for the temporary storage of data. Further, the electronic device 100 may also comprise non-volatile memory, which may be embedded and/or may be removable. The non- volatile memory may also comprise an electrically erasable programmable read only memory, flash memory, and/or the like. In an alternative embodiment, the processor 110 may comprise memory. For example, the processor 110 may comprise volatile memory, non-volatile memory, and/or the like.

[0018] In an embodiment, the electronic device 100 may use at least one memory to store one or more users' data. In an example embodiment, the user's data may comprise personal settings, user profiles, e-mails, short message service (SMS), music, pictures, videos, global positioning system (GPS) location data and history, address book, call histories, and/or the like. The user's data may further comprise commonly shared documentation and/or commonly shared access rights or functionalities with other users.

[0019] The electronic device 100 may also use at least one memory to store one or more instructions related to a security algorithm. The security algorithm is used to determine identification information, capable of uniquely identifying each user. For example, the processor 110, using the stored instructions, may determine an identity, e.g., user identity or user information, for access to the electronic device 100.

[0020] In an embodiment, the processor 110 of the electronic device 100 may comprise circuitry for implementing audio feature, logic features, and/or the like. For example, the processor 110 may comprise a digital signal processor device, a microprocessor device, a digital to analog converter, other support circuits, and/or the like. In an embodiment, control and signal processing features of the processor 110 may be allocated between devices, such as the devices describe above, according to their respective capabilities. Further, the processor 110 may also comprise an internal voice coder and/or an internal data modem. Further still, the processor 110 may comprise features to operate one or more software programs. For example, the processor 110 may be capable of operating a software program for connectivity, such as a conventional Internet browser. Further, the connectivity program may allow the electronic device 100 to transmit and receive Internet content, such as location-based content, other web page content, and/or the like. In an embodiment, the electronic device 100 may use a wireless application protocol (WAP), hypertext transfer protocol (HTTP), file transfer protocol (FTP) and/or the like to transmit and/or receive the Internet content.

[0021] In an embodiment, the electronic device 100 may be capable of operating in accordance with any of a number of a first generation communication protocol, a second generation communication protocol, a third generation communication protocol, a fourth generation communication protocol, and/or the like. For example, the electronic device 100 may be capable of operating in accordance with second generation (2G) communication protocols IS- 136, time division multiple access (TDMA), global system for mobile communication (GSM), IS- 95 code division multiple access (CDMA), and/or the like. Further, the electronic device 100 may be capable of operating in accordance with third-generation (3G) communication protocols, such as Universal Mobile Telecommunications System (UMTS), CDMA2000, wideband CDMA (WCDMA), time division-synchronous CDMA (TD-SCDMA), and/or the like. Further still, the electronic device 100 may also be capable of operating in accordance with 3.9 generation (3.9G) wireless communication protocols, such as Evolved Universal Terrestrial Radio Access Network (E-UTRAN) or the like, or wireless communication projects, such as long term evolution (LTE) or the like. Still further, the electronic device 100 may be capable of operating in accordance with fourth generation (4G) communication protocols.

[0022] In an alternative embodiment, the electronic device 100 may be capable of operating in accordance with a non-cellular communication mechanism. For example, the electronic device 100 may be capable of communication in a wireless local area network

(WLA ), other communication networks, and/or the like. Further, the electronic device 100 may communicate in accordance with techniques, such as radio frequency (RF), infrared (IrDA), any of a number of WLAN techniques. For example, the electronic device 100 may communicate using one or more of the following WLAN techniques: IEEE 802.11, e.g., 802.1 la, 802.1 lb, 802. l lg, 802.11η, and/or the like. Further, the electronic device 100 may also communicate, via a world interoperability, to use a microwave access (WiMAX) technique, such as IEEE 802.16, and/or a wireless personal area network (WPAN) technique, such as IEEE 802.15, BlueTooth (BT), ultra wideband (UWB), and/or the like.

[0023] It should be understood that the communications protocols described above may employ the use of signals. In an example embodiment, the signals comprises signaling information in accordance with the air interface standard of the applicable cellular system, user speech, received data, user generated data, and/or the like. In an embodiment, the electronic device 100 may be capable of operating with one or more air interface standards, communication protocols, modulation types, access types, and/or the like. It should be further understood that the electronic device 100 is merely illustrative of one type of electronic device that would benefit from embodiments of the invention and, therefore, should not be taken to limit the scope of embodiments of the invention.

[0024] While embodiments of the electronic device 100 are illustrated and will be hereinafter described for purposes of example, other types of electronic devices, such as a portable digital assistant (PDA), a pager, a mobile television, a gaming device, a camera, a video recorder, an audio player, a video player, a radio, a mobile telephone, a traditional computer, a portable computer device, a global positioning system (GPS) device, a GPS navigation device, a GPS system, a mobile computer, a browsing device, an electronic book reader, a combination thereof, and/or the like, may be used. While several embodiments of the invention may be performed or used by the electronic device 100, embodiments may also be employed by a server, a service, a combination thereof, and/or the like.

[0025] FIGURE 2 is a block diagram depicting a personal key 200 operating in accordance with an example embodiment of the invention.

[0026] In an example embodiment, the personal key 200 comprises an identifier chip 210. The identifier chip 210 may store one or more instructions related to a security algorithm, such as the security algorithm in memory 120 of FIGURE 1, to assist the electronic device 100 of FIGURE 1 to determine an identity, e.g., user identity or user information. In an example embodiment, the identifier chip 210 is an enhanced accessory control interface (ECI) chip. In an example embodiment, the identifier chip has a secret challenge-response mechanism. The challenge-response mechanism is described in further detail with respect to FIGURE 3. In another example embodiment, the identifier chip has a unique identifier. The unique identifier may be preset by manufacture or by user. For example, fixed, factory preset identifier number or other series of symbols, can be implemented in order to ensure secure identification of a known key.

[0027] In an example embodiment, the personal key 200 comprises a plug 220. The plug 220 is used to connect the personal key physically to an electronic device, such as electronic device 100 of FIGURE 1. In an example embodiment, the plug may be an audio/video (A V) plug. In an alternative embodiment, the personal key 200 may not comprise a plug 220. The personal key 200 may be connected physically to an electronic device through other interfaces, such as a keypad, a camera, a USB connector, and/or the like.

[0028] The personal key 200 is merely illustrative of one type of personal key that operates in accordance with embodiments of the invention and, therefore, should not be taken to limit the scope of embodiments of the invention. Any key mechanism may be used. For example, in an example embodiment, the personal key 200 may comprise USB device or a headset or other accessory that is equipped with an identifier chip, such as an ECI chip or other chip with similar functionalities. The USB device or a headset or other accessory with an identifier chip may be paired with an electronic device.

[0029] An example embodiment to pair a key with an electronic device is when a user gets a new phone, regardless of whether a personal key is in the inbox or not, a user could plug a key in for the first time and define rights for that key. A user could pair a key associated with the entire storage space and functionalities. A user could limit the storage space and functionalities or user data areas.

[0030] It may be possible to substitute or overrule a personal key by some other, less user friendly methods, such as a PIN code insertion in case of lost key or restoring to initial settings or reset to factory settings. However, this substituting or overruling key or method does not become publicly known. For example, a phone could have a factory restore PIN code in an inbox only, and it is unique to every phone. Without this precaution stolen phones could be unlocked, cleaned and sold onwards.

[0031] FIGURE 3 is a flow diagram illustrating an example method for providing a user's data with a personal key in accordance with an example embodiment of the invention. Example method 300 may be performed by an electronic device, such as electronic device 100 of FIGURE 1. [0032] At 310, an electronic device detects connection of a personal key to an interface of the electronic device. In an example embodiment, a personal key is an A/V plug with ECI chip or other chip with similar functionalities.. In an example embodiment, the A/V plug is inserted to the headset connector of the electronic device. In another example embodiment, a personal key is a USB type of device. The USB type of device is inserted to the USB connector of an electronic device. In yet another example embodiment, a personal key is a PIN code which may be entered in case of lost key, restored to initial settings or reset to factory settings. The PIN code may be inputted to the electronic device, for example, through keypad, touch screen, and/or the like.

[0033] At 320, the electronic device checks whether the personal key matches a user's identity or user information. There may be one or more users' data stored in the electronic device. The electronic device may use a security algorithm stored in at least one memory of the electronic device to determine the user identity or user information associated with the personal key.

[0034] In an example embodiment, an ECI chip is given a number by the electronic device. The ECI chip uses the number in its security algorithm to respond with another number. The responded number is given to the security algorithm in the electronic device. Since the same security algorithm is running on the electronic device, the security algorithm knows the key is valid when the responded number is correct. The security algorithm may further check whether the key matches with any of the users' identity or information.

[0035] In another example embodiment, the one or more users each have a personal PIN code stored in at least one memory of the electronic device. The security algorithm in the electronic device verifies whether the entered PIN code matches one of the users' stored PIN code.

[0036] In yet another example embodiment, the same user may have more than one personal key. For example, the user may use one key for work use, for example for access to work related information and use another key for home use, for example for access to personal non- work related information.

[0037] If at 330 it is determined that a match of a user identity or information is found, then at 340 the electronic device provides the user's data to the user. For example, the user may access the user's personal settings, user profiles, e-mails, SMS, music, pictures, videos, GPS location data and history, address book, call histories, and/or the like. The user may also have access to commonly shared documentation or functionalities with other users. The example method 300 ends.

[0038] If at 330 it is determined that no match of a user identity or information is found, then the example method 300 ends. In an alternative embodiment, if there is no match of user identity or information, then the method returns to block 310 or block 320. [0039] The example method 300 for providing a user's data with a personal key disclosed herein is merely an example and, therefore, should not be taken to limit the scope of embodiments of the invention.

[0040] FIGURE 4 is a flow diagram illustrating an example method for locking a user's data in accordance with an example embodiment of the invention. Example method 400 may be performed by an electronic device, such as electronic device 100 of FIGURE 1.

[0041 ] At 410, an electronic device detects disconnection of a personal key of a user from the electronic device.

[0042] At 420, a processor of the electronic device activates a timer when the device detects disconnection of a personal key from the device. The timer may have a predefined period of time. In an example embodiment, the timer is settable in the device's settings. For example, an "auto lock period" may be used to set the predefined period of time. The user's data remains active during the predefined period of time. This allows the user to use the electronic device's connectivity features without the key inserted. The predefined period of time may comprise a value of zero, therefore a user's data may be locked when a key is disconnected from an electronic device.

[0043] In an example embodiment, a personal key is an A V plug with ECI chip or other chip with similar functionalities. When the A/V plug is disconnected from a headset connector of an electronic device, the user's data remains active during the predefined pe od of time. This allows the user to reserve the headset connector for other use, such as insertion of a wired headset. In an example embodiment, a personal key is a USB type of device. When the USB type of device is disconnected from a USB connector of an electronic device, the user's data remains active during the predefined period of time. This allows the user to reserve the USB connector for other use, such as insertion of a USB device. In an example embodiment, a USB device or a headset with an identifier chip could also be used as a personal key. In this example embodiment, the USB device or a headset integrates the identifier chip or functionalities in the identifier chip. The timer may be set with a value of zero in this example embodiment, therefore a user's data may be locked when a key is disconnected from an electronic device.

[0044] If at 430 it is determined that the timer expired, then at 440 the electronic device locks the user's data. The example method 400 ends.

[0045] If at 430 it is determined that the timer is not expired, then at 450 the electronic device keeps the user's data active. The process returns to block 430.

[0046] The example method 400 for locking user's data disclosed herein is merely illustrative of one type of method that the embodiments of the invention would benefit from and, therefore, should not be taken to limit the scope of embodiments of the invention. For example, an electronic device may lock a user's data when the electronic device detects connection of a personal key to the device. In another example, an electronic device may lock a user's data when the user closes the lid of a phone, locks the keyboard, selects "close account" from the menu, turns the phone to "off state" or when the phone battery runs out of power.

[0047] FIGURE 5 is a block diagram depicting an electronic device 510 and personal keys operating in accordance with an example embodiment of the invention. The electronic device 510 may be similar to electronic device 100 of FIGURE 1. The electronic device 510 comprises at least one memory 520 to store data of one or more users. In the example of FIGURE 5, user l's data is stored at 530 and user 2's data is stored at 540.

[0048] The personal keys 560, 570 and 580 may be similar to personal key 200 of FIGURE 2. In an example embodiment, when personal key 1 560 is connected to electronic device 510, user 1 's data stored in 530 and/or user rights are provided in the electronic device 510. In another example embodiment, when personal key 2 570 is connected to electronic device 510, user 2's data stored in 540 and/or user rights are provided in the electronic device 510. In yet another example embodiment, some keys can be programmed to have rights over some other keys for allowed functionalities and access rights. In this example embodiment, personal key 3 580 is programmed to have rights over key 1 560 and key 2 570. When personal key 3 580 is connected to electronic device 510, both user l's and user 2's data in 530 and 540 and/or user rights may be accessed in the electronic device 510.

[0049] FIGURE 6 is a picture illustrating an example use case operating in accordance with an example embodiment of the invention. The example use case 600 comprises an electronic device 610, such as electronic device 100 of FIGURE 1. The example use case 600 may further comprise a wrist strap 620, with for example a 2.5 mm or 3.5 mm A/V plug 630, such as the plug 220 of FIGURE 2, and ECI chip 640, such as the identifier chip 210 of FIGURE 2.

[0050] Without in any way limiting the scope, interpretation, or application of the claims appearing below, a technical effect of one or more of the example embodiments disclosed herein may be enabling multiple users to use the same electronic device. Another technical effect of one or more of the example embodiments disclosed herein may be enabling safe rental or lease of an electronic device to a user without leaking out other users' data or identity. Another technical effect of one or more of the example embodiments disclosed herein may be using a personal key to access a user's data on the electronic device.

[0051] Embodiments of the present invention may be implemented in software, hardware, application logic or a combination of software, hardware and application logic. The software, application logic and/or hardware may reside on an electronic device or a personal key. If desired, part of the software, application logic and/or hardware may reside on an electronic device and part of the software, application logic and/or hardware may reside on a personal key. In an example embodiment, the application logic, software or an instruction set is maintained on any one of various conventional computer-readable media. In the context of this document, a "computer-readable medium" may be any media or means that can contain, store, communicate, propagate or transport the instructions for use by or in connection with an instruction execution system, apparatus, or device. A computer-readable medium may comprise a computer-readable storage medium that may be any media or means that can contain or store the instructions for use by or in connection with an instruction execution system, apparatus, or device.

[0052] If desired, the different functions discussed herein may be performed in a different order and/or concurrently with each other. Furthermore, if desired, one or more of the above-described functions may be optional or may be combined.

[0053] Although various aspects of the invention are set out in the independent claims, other aspects of the invention comprise other combinations of features from the described embodiments and/or the dependent claims with the features of the independent claims, and not solely the combinations explicitly set out in the claims.

[0054] It is also noted herein that while the above describes example embodiments of the invention, these descriptions should not be viewed in a limiting sense. Rather, there are several variations and modifications which may be made without departing from the scope of the present invention as defined in the appended claims.

Claims

WHAT IS CLAIMED IS

1. An apparatus, comprising:

at least one memory including user data for a plurality of users;

an interface configured to receive a user's personal key; and

at least one processor configured to provide user data associated with a user when the user's personal key is connected through said interface.

2. The apparatus of Claim 1 , wherein the user data is at least one of the following: personal setting, user profile, e-mail, short message service, music, pictures, videos, Global Positioning System (GPS) location data and history, address book, and call history.

3. The apparatus of Claim 1, wherein the user data is commonly shared documentation or user rights with other users.

4. The apparatus of Claim 1, wherein the at least one processor is further configured to activate a timer to lock the user data associated with the user when the user's personal key is disconnected from said interface.

5. The apparatus of Claim 1, wherein the at least one processor is further configured to lock the user data associated with the user when at least one of the following event occurs: the user closes a lid of said aparatus, locks a keyboard, selects "close account" from a menu, the personal key is disconnected, a new personal key is connected, said apparatus runs out of power or said apparatus is turned to off-state.

6. The apparatus of Claim 1, wherein the user's personal key is a physical key.

7. The apparatus of Claim 1, wherein the user's personal key is physically connected to the interface of said apparatus.

8. A method, comprising:

storing user data for a plurality of users on a mobile device; and

when a user's personal key is connected to the mobile device, providing the user data associated with the user to the user.

9. The method of Claim 8, wherein the user data is at least one of the following: personal setting, user profile, e-mails, short message service, music, pictures, videos, Global Positioning System (GPS) location data and history, address book, and call history.

10. The method of Claim 8, wherein the user data is commonly shared documentation or user rights with other users.

11. The method of Claim 8, further comprising activating a timer to lock the user data associated with the user when the user's personal key is disconnected from the mobile device.

12. The method of Claim 8, further comprising locking the user data associated with the user when at least one of the following event occurs: the user closes a lid of the mobile device, locks a keyboard, selects "close account" from a menu, the personal key is disconnected, a new personal key is connected, the mobile device runs out of power or the mobile device is turned to "off-state".

13. A computer program product comprising a computer-readable medium bearing computer program code embodied therein for use with a computer, the computer program code comprising:

code for storing user data for a plurality of users on a mobile device; and

code for pairing and unpairing a unique identifier associating with the entire storage space and functionalities, or for limiting storage space and functionalities or user data areas.

14. A computer program product of Claim 13, wherein the user data is at least one of the following: personal setting, user profile, e-mails, short message service, music, pictures, videos, Global Positioning System (GPS) location data and history, address book, and call history.

15. A computer program product of Claim 13, wherein the user data is commonly shared documentation or user rights with other users.

16. A computer program product of Claim 13, further comprising code for activating a timer to lock the mobile device when a personal key is disconnected from the mobile device.

17. A computer program product of Claim 13, further comprising code for locking the user data associated with the user when at least one of the following event occurs: the user closes a lid of the mobile device, locks a keyboard, selects "close account" from a menu, the personal key is disconnected, a new personal key is connected, the mobile device runs out of power or the mobile device is turned to "off-state".

18. A personal key, comprising:

means to connect to a mobile device; and

a unique identifier that can be read and used by the mobile device to activate user data associated with a user among a plurality of user data stored on the mobile device.

19. The personal key of Claim 18, wherein the personal key is at least one of an A/V (Audio/Video) plug with an identifier chip, a headset equipped with an identifier chip, and other accessory equipped with an identifier chip.

20. The personal key of Claim 19, wherein the identifier chip is an enhanced accessory control interface chip.

21. The personal key of Claim 18, wherein the unique identifier is at least one of the following: a USB device, a PIN code in case of lost key, and factory default key.