Disclosed are methods and electronic devices for use in a mobile communication network, and more particularly methods and electronic devices for coordinating a single telephone number among multiple mobile communication devices of an activation pool of mobile communication devices.
Mobile communication devices, such as cellular telephones, have become an important part of everyday life. Many subscribers own more than one mobile communication device. For example, different devices may have different device capabilities; a particular device may have still or video camera capability, or multimedia playback capability. As another example, a subscriber may own multiple mobile communication devices in order to have available a range of applications and accessories to coordinate with the user's appearance and life style.
An executive may wish, during the day, to coordinate her cellular telephone, PDA, or other mobile device with her business needs. For her daily use, she may own a “business phone,” with many business applications and a business-like, professional look. While entertaining or otherwise out for the evening, she may prefer to carry a small cellular phone better coordinated to her evening attire, having a dressier or more fashionable look, that is an “evening phone” which can easily fit into a small evening bag. On the weekend, or when out with friends, she may want to carry along a mobile communication device with a sportier look, that is a “fun phone,” that may include, for example an MP3 player and a video camera.
At present, an owner of two or more code division multiple access (CDMA) phones cannot easily switch between phones making one active and another inactive. For a user of a CDMA phone, the existing CDMA phone identity procedures are typically locked to a particular piece of hardware of a particular phone. To switch between phones, the solution of a removable user identity module (R-UIM), that is a small chip that can be manually removed from a phone and placed in another telephone, can be difficult for users to manually manipulate. Thus, a more convenient solution to the problem of switching between phones is desirable.
It would be beneficial to have methods and devices by which an owner of multiple CDMA mobile communication devices can easily transfer an operational identity between two such devices, making one active and another inactive, but maintain the same telephone number or other operational identity. A set of commonly owned CDMA devices, described below as an activation pool, is configured to easily transfer an operational identity between the devices so that one CDMA phone may be actively associated with the operational identity at a given time. The operational identity may be, for example, a user account number, a telephone number, or other identifier that can identify the active CDMA device in the CDMA communication network. The operational identity allows telephone calls or other communications to be sent to one device of the set of commonly owned devices via, for example a service provider.
To activate an operational identity of a particular device of an activation pool, a CDMA device may transmit a signal to a server of the service provider to make active the CDMA device and to operate the CDMA device under the operational identity. The active CDMA device may be registered as active with the service provider, and the previously active CDMA device may be registered as inactive. In this manner the operational identity can be coordinated among the set of CDMA devices of the activation pool. Thus, a user may switch between commonly owned CDMA devices using the phone of her choice in the activation pool without the need to physically transfer an R-UIM or other device component between mobile communication devices.
The instant disclosure is provided to explain in an enabling fashion the best modes of making and using various embodiments in accordance with the present invention. The disclosure is further offered to enhance an understanding and appreciation for the invention principles and advantages thereof, rather than to limit in any manner the invention. While the preferred embodiments of the invention are illustrated and described here, it is clear that the invention is not so limited. Numerous modifications, changes, variations, substitutions, and equivalents will occur to those skilled in the art having the benefit of this disclosure without departing from the spirit and scope of the present invention as defined by the following claims. It is understood that the use of relational terms, if any, such as first and second, up and down, and the like are used solely to distinguish one from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions.
At least some inventive functionality and inventive principles may be implemented with or in software programs or instructions and integrated circuits (ICs) such as application specific ICs. In the interest of brevity and minimization of any risk of obscuring the principles and concepts according to the present invention, discussion of such software and ICs, if any, is limited to the essentials with respect to the principles and concepts within the preferred embodiments.
Each mobile communication device within the activation pool 104 is configured to communicate in accordance with its operational identity. That is, if a mobile communication device in the activation pool 104 is active, its operational identity is active. If the mobile communication device in the activation pool is inactive, its operational identity is inactive. An operational identity may be, for example, a telephone number or other identifier that can identify the active mobile communication device 108 in the communication network 102. Telephone calls or other communications 112 may be sent via the network 102 to the one active device 108 of the set of commonly owned devices via, for example a service provider. The network 102 may communicate 112 with a mobile communication device 108 with an active operational identity 110. Other devices within the activation pool 104, in this example mobile communication device 114 and mobile communication device 116, may be configured with the same operational identity, which in this example is inactive 118 and 120, respectively. In this way a user can choose to use a mobile communication device of their preference within the activation pool 104.
The mobile communication device 108 of the activation pool 104 acquires an operational identity 110 via a server 106 that is configured to enable the operational identity. As just discussed, an operational identity may be, for example, a telephone number or other identifier that can identify an active mobile communication device 108 in the communication network 102. The operational identity may be associated in the server 106, or in a database of the server 106, with other data associated with the mobile communication device, for example, a billing account number or user account number. In an embodiment, the user account number may in addition serve as the operational identity.
At power up of the mobile communication device 108, in order to communicate 112 with another remote mobile communication device (not shown) having a different operational identity, the server 106 can activate the operational identity 110 of the mobile communication device 108. At the same time, other mobile communication devices 114, 116 of the activation pool 104 of mobile communication devices are registered by the server as inactive, and may have an inactive operational identity, for example, 118 and 120, respectively, or none at all.
The communication network 102 may be a code division multiple access (CDMA) communication network, or another Third Generation Partnership Project 2 (3GPP2) compliant communication network. Similarly, the mobile communication devices may be CDMA devices or other 3GPP2 compliant mobile communication devices. It is understood that other 3GPP2 compliant methods and devices are within the scope of this discussion.
A set of commonly owned mobile communication devices is described as an activation pool 104, in that one phone or mobile communication device 108, for example, may be actively associated with an operational identity 110, for example, at a given time. As mentioned above, the operational identity 110 may be, for example, a user account number, a telephone number, or other identifier that can identify the active mobile communication device 108 in the communication network 102 so that telephone calls or other communications 112 may be sent via the network 102 to the one active device 108 of the set of commonly owned devices via, for example a service provider.
As discussed above, the mobile communication devices of the activation pool 104, and the server 106 of the communication network 102, are configured so that a mobile communication device may be registered upon power up as active with the communication network 102, and the previously active mobile communication device may be registered as inactive. In this manner the operational identity can be coordinated among the set of mobile communication devices for example 108, 114, and 116 of the activation pool 104 so that a user may switch between mobile communication devices of the activation pool 104 in order to use the phone of her choice without the need to physically transfer an R-UIM or other device component between mobile communication devices. Thus, by the methods and devices described below an owner or user of multiple mobile communication devices of an activation pool can easily transfer an operational identity between two such devices, making one active and another inactive, but maintaining the same telephone number or other operational identity.
The mobile communication devices 108, 114, and 116, as discussed above, belong to an activation pool 104 and may be commonly owned. Each such device has an identifying number, for example an electronic serial number (ESN) or mobile equipment identifier (MEID), by which it may be identified to the server 106 of the communication network 102. By comparing the identifying number with a database, for example database 122, the server 106 can determine whether a mobile communication device has a transferable identity.
A mobile communication device has a transferable identity when the mobile communication device belongs to an activation pool 104 of mobile communication devices such as 108, 114, and 116, any one of which able to acquire an operational identity associated with the activation pool 104 in a manner that leaves the other members of the activation pool 104 without an active operational identity. That is, the operational identity may be transferred to the one mobile communication device. As just described, a database 122 accessible to the server may include identifying numbers of mobile communication devices along with operational identities associated with the mobile communication devices. When two or more mobile communication devices are associated in the database 122 with the same operational identity, those devices belong to the same activation pool 104. Thus, the server 106 may be able to determine whether a mobile communication device has a transferable identity. Further details of the server are described in connection with
The modules 230 may in addition include an identity module 247 configured to determine that the mobile communication device has a switchable identity, and also include a registering module 256 configured to register the mobile communication device as an active mobile communication device to the exclusion of others of a plurality of mobile communication devices of an activation pool of mobile communication devices. The modules 230 further include a transferring module 261 configured to transfer the operational identity to the mobile communication device, and a deactivation module 262 configured to register as inactive mobile communication devices, the other mobile communication devices of the activation pool. The modules 230 may also include a messaging module 267 configured to send for each of the other mobile communication devices of the activation pool, an SMS message, or any other type of message, to the other mobile communication device indicating that the other mobile communication device is inactive.
The modules can carry out certain processes of the methods as described herein. The modules can be implemented in software, such as in the form of one or more sets of prestored instructions, and/or hardware, which can facilitate the operation of the mobile station or electronic device as discussed below. The modules may be installed at the factory or can be installed after distribution by, for example, a downloading operation. The operations in accordance with the modules will be discussed in more detail below.
The mobile communication device 308 may be implemented as a cellular telephone (also called a mobile phone). The mobile communication device 308, for example, may include a cellular antenna 332 that may be coupled to the transceiver 326. The mobile communication device 308 also includes a user interface 334 coupled to the controller 324, and modules 330.
The mobile communication device 308 represents a wide variety of devices that have been developed for use within various networks. Such handheld communication devices include, for example, cellular telephones, messaging devices, personal digital assistants (PDAs), notebook or laptop computers incorporating communication modems, mobile data terminals, application specific gaming devices, video gaming devices incorporating wireless modems, and the like. Any of these portable devices may be referred to as a mobile station or user equipment. Herein, wireless communication technologies may include, for example, voice communication, the capability of transferring digital data, SMS messaging, Internet access, multi-media content access and/or voice over internet protocol (VoIP).
The user interface 334 may include a display 335 and a keypad 336. A speaker 337 and microphone 338 may be a user interface for a speech recognition application and for other voice applications. It is understood that any type of user interface is within the scope of this discussion. The user interface 334 is configured to receive activation choice input to operate the mobile communication device 308 under the operational identity to the exclusion of other mobile communication devices of the plurality of mobile communication devices of the activation pool 104 (see
The user interface 334 may also include a fingerprint sensor, camera, or other sensors that may be used to confirm the identity of a user. For example, the display 335 may include a touch sensitive portion that may be configured to effect a fingerprint scan. In another embodiment the mobile communication device 308 may include a separate fingerprint sensor. In yet another embodiment, the mobile communication device 308 may include a camera 339. While attempting to activate the device 308 a user may be required to enter a password, passcode, scan a fingerprint, and/or use facial recognition to validate his or her identity as an authorized user of the account. Thus, the user interface may be configured to receive identification and authentication input including at least one of a fingerprint scan, a facial image, a passcode, and a password. It is understood that identifying and authenticating the user may be carried out in any manner as known in the art.
The modules 330 may be configured with instructions to carry out steps of the described method. The modules 330 include a powering module 340, a registration module 342, a confirmation module 352, and an activation module 361. Steps of methods may involve modules and modules may be inferred by the methods discussed herein. The modules can be implemented in software, such as in the form of one or more sets of prestored instructions, and/or hardware, which can facilitate the operation of the mobile station or electronic device as discussed below. The modules may be installed at the factory or can be installed after distribution by, for example, a downloading operation. The operations in accordance with the modules will be discussed in more detail below.
The powering module 340 is configured to power up the mobile communication device. The power up may take place, for example, in response to a press of a key of the user interface 334 keypad 336. The power up may instead be in response to activation of the mobile communication device via for example an on-off switch of the device, or the result of a timer expiring in the controller 324. Upon power up the device may execute self-test functions as well as loading of data and of instructions for execution by the controller 324.
The registration module 342 is configured to generate a signal to the server 206 (see
The confirmation module 352 is configured to send an activation choice signal in response to a message from a server of the communication network 102 (see
The activation module 361 is configured to receive the operational identity for example 310 from the server 106 (see
As described previously, a user may power up 440 an initially inactive mobile communication device of the activation pool 104 (see
Upon power up, the mobile communication device may initiate a power up registration procedure 442. The power up registration procedure may occur according to a powering module 340 (see
The registration message 444 typically includes a mobile communication device identifier, such as for example, an electronic serial number (ESN) or a mobile equipment identifier (MEID). An electronic serial number (ESN) is a unique identification number placed within the mobile communication device by the manufacturer. The ESN may be embedded or inscribed on a microchip in the device. The MEID is a unique number that identifies a physical piece of CDMA mobile station equipment throughout the world, and has been introduced to replace use of ESNs.
The registration message 444 may include other data related to authorization of the device to operate in the communication network 102 (see
When the registration message 444 is received by the server 406, it is processed by a Home Location Register (HLR) accessed by the server. The HLR is a central database that includes details of each subscriber of the communication network 102 (see
The server may generate a message to the mobile communication device 408 in accordance with the generating module 245 (see
Other components of the server may provide, for example, SMS messaging functionality. Upon processing the registration message 444, the server may acknowledge the registration message and transmit 448 to the mobile communication device 408 an SMS message. Depending on the capability and/or configuration of the mobile communication device, the SMS message may include instructions to the mobile communication device according to different options.
The mobile communication device 408 is capable of receiving an SMS message 448. In a first option, the SMS message may include text to be displayed 450 to the user of the mobile communication device 408, via, for example, the display 335 (see
The mobile communication device 408 may be capable in addition of initiating a packet data call. For example, the mobile communication device may connect to the communication network 102 (see
Authentication of the mobile communication device 408 may proceed 460 whether according to the first, call-back 452 option, or whether according to the second, IP-based 456 option, or in response to the user continuing to make a phone call. The server 406 provides authentication 460 to the mobile communication device and deactivates 462 the other hitherto active communication device of the activation pool 104 (see
The deactivation 462 of the other mobile communication device need not entail remotely powering down the other communication device 414. However, upon deactivation, the other communication device is no longer registered for operation within the communication network 102 (see
The mobile communication device 408, upon receiving an active operational identity may continue with additional processing 468 preparatory to acquiring full access to the communication network 102 (see
In
The server 106 (see
In yet another embodiment, the server may detect 545 an initiation of a communication by the mobile communication device 108 (see
The server 106 (see
The server may determine 547 that the mobile communication device is one that has a switchable identity in accordance with identity module 247 (see
The server registers 556 the mobile communication device 108 (see
The operation of the mobile communication device 108 (see
The server 206 (see
The server 206 (see
In a step 567 the server sends a message to each of the other mobile communication devices of the activation pool 104 (see
The server 206 (see
The described methods and devices provide that an owner of multiple mobile communication devices of an activation pool can easily transfer an operational identity between two mobile communication devices of the activation pool, making one active and another inactive, but maintain the same telephone number or other operational identity. The operational identity may be, for example, a user account number, a telephone number, or other identifier that can identify the active mobile communication device in the communication network so that telephone calls or other communications may be sent to and/or received by one device of the set of devices of the activation pool. As described, a mobile communication device may transmit a signal to a server of the communication network to make active the mobile communication device and to operate the device under the operational identity. At the same time, the server may register as inactive the previously active mobile device of the activation pool. In this manner the operational identity can be coordinated among the set of mobile communication devices of the activation pool. Thus, a user may switch between mobile communication devices that belong to an activation pool using the device of her choice without the need to physically transfer an R-UIM or other device component between mobile communication devices.
This disclosure is intended to explain how to fashion and use various embodiments in accordance with the technology rather than to limit the true, intended, and fair scope and spirit thereof. The foregoing description is not intended to be exhaustive or to be limited to the precise forms disclosed. Modifications or variations are possible in light of the above teachings. The embodiment(s) was chosen and described to provide the best illustration of the principle of the described technology and its practical application, and to enable one of ordinary skill in the art to utilize the technology in various embodiments and with various modifications as are suited to the particular use contemplated. All such modifications and variations are within the scope of the invention as determined by the appended claims, as may be amended during the pendency of this application for patent, and all equivalents thereof, when interpreted in accordance with the breadth to which they are fairly, legally and equitably entitled.