CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application is a PCT application claiming priority from United States provisional applications Ser. No. 61/371,149, filed on 5 August 2010, entitled "Perso Package" and United States provisional applications Ser. No. 61/371,152, filed on 5 August 2010, entitled "SEVI WALLET," the teachings of which are incorporated by reference herein as if reproduced in full below.

BACKGROUND OF THE INVENTION

[0002] The present invention relates generally to telecom and more particularly to the ability to provide a multi-subscription application managed by a security component such as a UICC (Universal Integrated Circuit Card) directly.

[0003] The problem addressed by the present invention is how to securely switch between different profiles and network access technology from a mobile device, with no limit to the number of profiles being supported.

[0004] A scenario in which it is useful to have multiple subscriptions is when one is travelling between geographic areas served by different operators. This is usually referred to as roaming. When roaming into a visited network, a user pays roaming charges which generally are much more expensive than those charged by either the home network or the visited network operators. To get around that problem, users who frequently engage in such travel may try the solution of carrying multiple mobile devices, e.g., "my Canadian cell phone," "my French cell phone" or "my Swedish cell phone," with each cell phone being used with an operator in the corresponding country. Of course, this jostling of several units is very burdensome on the user.

[0005] Another solution is to switch out the UICC. However, there are at least two problems with that particular solution. First, the user would have to remember to carry along multiple UICCs and to know which to use in each location. Second, there is a growing trend towards embedded UICCs. In a mobile device with an embedded UICC it is not possible, at least not at the user level, to readily access the UICC and replace it.

[0006] One existing alternative solution to the problem described above is known as the multi-EVISI application, in which an application inside the UICC can switch between different credentials, based on some external trigger. This alternative solution has two limitations:

- The number of different credentials to be supported is limited by the memory of the UICC.

- It is difficult to switch between entire profiles, mainly because of limitation of memory in the UICC. Therefore the multi-IMSI application only switches the credentials (keys and codes) and some selected data (e.g. the roaming files). The rest of the profile must be shared. [0007] In multi-IMSI applications, only some parameter values of a profile are switched with other values, e.g., EVISI and telephone number. However, there is not a switch of an entire profile.

[0008] One limitation, thus, of the multi-IMSI solution is that, because entire profiles are not switched, the two operators must have the same profile format in order to allow for a switch of profiles when switching from one operator to another.. That is often not the case, and therefore the solution is often not a complete and dependable solution allowing for switching of profiles, for example while roaming.

[0009] There is a need for an improved method to provide the ability to provide multi-IMSI applications managed directly by a UICC or similar device.

BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 is a block diagram illustrating the use of a mobile telephony device in a home location and while roaming in a visited mobile network.

[0011 ] Figure 2 is a block diagram illustrating a high-level view of one example of a mobile device of Figure 1 including a UICC embedded in the mobile device.

[0012] Figure 3 is a block diagram illustrating one example of a high-level architectural organization of the hardware components of the mobile device and of the UICC of Figure 2.

[0013] Figure 4 is a block diagram illustrating programs and data stored in the nonvolatile memory of a UICC of Figures 2 and 3 including the storage of a subscriber profile.

[0014] Figure 5 is a block diagram illustrating one example of a subscriber profile wallet for storing multiple subscriber profiles which may be activated to become the currently active subscriber profile.

[0015] Figure 6 is a schematic diagram illustrating several example storage locations for the subscriber profile wallet of Figure 5.

[0016] Figure 7 is a block diagram illustrating programs and data stored in the nonvolatile memory of a UICC of Figure 4 including the storage of a subscriber profile wallet.

[0017] Figure 8 is a timing sequence diagram illustrating one possible scenario for storage of subscriber profiles in the subscriber profile wallet of Figures 5, 6, and 7. [0018] Figure 9 is a timing sequence diagram illustrating activation of a subscriber profile stored in the subscriber profile wallet of Figures 5, 6, and 7.

[0019] Figure 10 is a flow-chart illustrating the use of location to trigger activation of a subscriber profile from the subscriber profile wallet.

DETAILED DESCRIPTION OF THE INVENTION

[0020] In the following detailed description, reference is made to the accompanying drawings that show, by way of illustration, specific embodiments in which the invention may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the invention. It is to be understood that the various embodiments of the invention, although different, are not necessarily mutually exclusive. For example, a particular feature, structure, or characteristic described herein in connection with one embodiment may be implemented within other embodiments without departing from the spirit and scope of the invention. In addition, it is to be understood that the location or arrangement of individual elements within each disclosed embodiment may be modified without departing from the spirit and scope of the invention. The following detailed description is, therefore, not to be taken in a limiting sense, and the scope of the present invention is defined only by the appended claims, appropriately interpreted, along with the full range of equivalents to which the claims are entitled. In the drawings, like numerals refer to the same or similar functionality throughout the several views.

[0021 ] The technology presented herein provides a powerful, inexpensive, scalable, flexible, and universal solution for allowing a user of a mobile device to switch between different subscriber profiles. One scenario in which that is useful is roaming. Another is to allow an operator to activate an administrator or testing profile on a mobile device to allow the operator to use such a profile instead of the subscriber's own profile when doing administrative tasks or testing a mobile device. [0022] Figure 1 is a block diagram illustrating the use of a mobile telephony device in a home location and while roaming in a visited mobile network. In the upper portion of Figure 1 a user 101 is using a mobile device 103 connected to a "Home" mobile phone network A 105a. The home network may be connected to other networks via, for example, the publicly switched telephone network PSTN 107. One such network may be a mobile phone network of another operator B 105b. While connected to the home network 105a the subscriber pays for air-time and other services per a contract directly with the home network operator A.

[0023] In the lower portion of Figure 1, the user 101 ' operating the same mobile device 103' is connected to a "Visited" mobile phone network B 105b. That often happens when a user moves into a geographic area not served by the "Home" operator. In order to place or receive telephone calls (or other data communication) the subscriber pays for air-time and other services according to a roaming contract with the Visited network operator B. Usually such charges are much more expensive than what either operator charges its own customers.

[0024] Therefore, it would be useful to the user 101 if he or she could enter into a subscriber relationship with multiple operators and have a mechanism to activate the appropriate subscribe profile for whatever location the user happens to find him- or herself.

[0025] Turning now to some fundamental aspects of mobile communications technology relevant to the present technology: Figure 2 is a block diagram illustrating a high-level view of one example of the mobile device 103 of Figure 1 including a UICC 201 embedded in the mobile device 103. While a reader will recognize that the depicted mobile device 103 is a mobile telephone, also often referred to as a cell phone, the present technology is applicable to any mobile communications device, including but not limited to computers, data modems, cameras, point-of-sale devices, vehicles with onboard communication, or location devices embedded or carried by animals, equipment and human beings.

[0026] Both the UICC 201 and the mobile device 103 are computers. Typically they are connected to one another in a master-slave relationship in which the mobile device 103 is the master and the UICC 201 is the slave. The UICC 201 provides certain functions, such as storing subscriber profiles and performing security-critical operations. UICCs are typically tamper-resistant and are therefore very secure devices for storing sensitive information, such as subscriber profile and account information, and to provide secure functions, such as cryptographic operations.

[0027] Figure 3 is a block diagram illustrating one example of a high-level architectural organization of the hardware components of the mobile device 103 and of the UICC 201 of Figure 2. Typically the UICC 201 is connected to the mobile device 103 using the connectors 301 on the UICC 201 and connectors in a card slot (not shown) on the mobile device 103. The mobile device 103 may have a communications interface 303 for facilitating the communication between the two devices. In the present example, on the UICC 201 end, communication is managed directly by a CPU (Central Processing Unit) 305.

[0028] The card CPU 305 is further connected to a RAM (Random Access Memory) 307 and a NVM (Non- Volatile Memory) 309. Typically the NVM 309 is used to store information on the UICC 201 that is to persist through power-cycling the UICC 201, e.g., subscriber profiles and application programs of the UICC 201.

[0029] The mobile device 103 also contains a CPU 311 , a RAM 313 , and an NVM 315. The mobile device NVM 313 may be used to store application programs of the mobile device 103.

[0030] Figure 4 is a block diagram illustrating programs and data stored in the nonvolatile memory 309 of the UICC 201 of Figures 2 and 3 including the storage of a subscriber profile. As noted, the NVM 309 (herein, "NVM' without a modifier should be taken to refer to the UICC NVM 309 unless the context indicates otherwise) is used to store persistent data and programs. This includes a cryptography module 401 for performing cryptographic operations, e.g., encrypting a data item, decrypting an encrypted data item, and cryptographically signing a data item. These cryptographic operations may include public key cryptography or secret key cryptography. In either case, the UICC 201 would have stored thereon, e.g., in the NVM 309, a key (Card Key) 403 that is only known by the UICC 201. (Whereas it is common in computing literature to use anthropomorphic terminology such as "known" by a device, when such usage is employed herein it must be appreciated that this is a figurative use of the term and should be taken to mean that a corresponding operation is performed by the device. E.g., in this instance "known only" means that the data item in question is stored only on that device and not on other devices or cannot be retrieved by other devices) Thus, the card key 403 may be used by the UICC 201 to encrypt data items in such a manner that only the UICC 201 may decrypt them or the card key 403 may be used by the UICC 201 to cryptographically sign a data item so that the UICC 201 (or other devices) may confirm that the UICC 201 in fact is the signer of the signed data item.

[0031 ] The NVM 309 also contains one or more subscriber profiles 405 including one active subscriber profile 405a (illustrated here with a double-line border). In most cases, the NVM 309 would only include one subscriber profile 405, namely, the active subscriber profile 405a. A subscriber profile 405 may include an IMSI, a telephone number, an authentication key for authenticating a subscriber with a particular network, applications associated with the subscriber and a particular network, and any other information that is specific to a subscriber and one particular network with which the subscriber profile is associated.

[0032] The card NVM 309 may also contain a special program 407 used to switch subscriber profiles as described herein below.

[0033] The card NVM 309 may also contain a virtual machine 409 or other operating system software for controlling the operations of the UICC 201 and other data and programs 411.

[0034] In one embodiment of the technology presented herein, multiple subscriber profiles 405 may be associated with a particular user. A user or administrator may select a particular profile from this set of subscriber profiles 405 associated with a user. Figure 5 is a block diagram illustrating one example of a storage mechanism for such multiple subscriber profiles, namely, a subscriber profile wallet 501 for storing multiple subscriber profiles 405 associated with a user which may be activated to become the currently active subscriber profile on a user's mobile device 103. In the example of Figure 5, a particular subscriber has n profiles A - N stored in a subscriber profile wallet 501. [0035] Figure 6 is a schematic diagram illustrating several example storage locations for the subscriber profile wallet of Figure 5. The subscriber profile wallets 501 may be stored, for example, on a host computer 601. One example in which a host computer 601 is a useful storage location is the iPhone from Apple Inc., Cupertino, California, USA. The iPhone is a mobile device which is typically synchronized (synced) with a computer using the iTunes program on a Mac or PC computer. Via iTunes the contents on the iPhone is synchronized with the host computer 601. Thus, the host computer 601 may contain a synchronization program 603 for synchronizing contents with the mobile device 103. A plug-in or extension (not shown) to that synchronization program may activate new subscriber profiles from the subscriber profile wallet 501 A.

[0036] In another alternative, the subscriber profile wallet B 501 B is stored in the Cloud 605. An activation web application 607, for example, invoked via a web browser on the mobile device 103, may be used to activate a subscriber profile from subscriber profile wallet B 501B in the Cloud 605.

[0037] In yet another alternative, the subscriber profile wallet C 501 C is stored in the NVM 309 of the UICC Card 201 which is illustrated in Figure 7. Alternatively, for a multi-UICC mobile device, the subscriber profile wallet may be stored on one of the UICCs in the multi-UICC mobile device and the active subscriber profile may be retrieved therefrom.

[0038] Figure 8 is a timing sequence diagram illustrating one possible scenario for storage of subscriber profiles in the subscriber profile wallet of Figures 5, 6, and 7. In the example of Figure 8, an issuer A 800 creates one or more subscriber profiles 501, step 801. The profiles are transmitted to the UICC 201, step 803. The UICC 201 encrypts or cryptographically signs the profile using the card key 403, step 805, for example, using the cryptography module 401. The UICC 201 transmits the encrypted or signed subscriber profile to the subscriber profile wallet 501, step 809. The encrypted or signed subscriber profile is stored in the subscriber profile wallet 501 , step 811.

[0039] The above process may be repeated to create additional encrypted or signed subscriber profiles by the issuer, step 813.

[0040] The above steps are advantageously performed during card personalization. Additional profiles may further be created and downloaded to the UICC "over-the-air."

[0041] At some future time, for example, a second operator B 815 may create a subscriber profile for the user, step 817. This subscriber profile associates the user with the operator B 815. The subscriber profile is transmitted to the UICC 201, step 819. The UICC 201 encrypts the subscriber profile created by the operator B 815, step 821 , and transmits the encrypted or signed subscriber profile to the subscriber profile wallet 501, step 823. The encrypted or signed subscriber profile is stored in the subscriber profile wallet 501, step 825.

[0042] Figure 9 is a timing sequence diagram illustrating activation of a subscriber profile stored in the subscriber profile wallet of Figures 5, 6, and 7. A mobile device, a host computer device or a web application (collectively) 901 is operated to activate an inactive subscriber profile stored in the subscriber profile wallet 501, step 903. A program executing on the mobile device 103 may act as a profile activator application. This program can either retrieve a subscriber profile from a subscriber profile wallet stored on the mobile device, or from some other location, e.g., the UICC if it stores a subscriber profile wallet or the cloud via a web app. [0043] The program - wherever it is executing - sends a retrieve-active-profile message to the subscriber profile wallet 501, step 905. The subscriber profile wallet transmits the activated subscriber profile to the UICC 201 , step 907. At this point the subscriber profile is encrypted or cryptographically signed. Only a subscriber profile that has been encrypted or cryptographically signed by the UICC 201 that originally encrypted or digitally signed the subscriber profile is accepted by that same UICC 201. In other words, the digital signature or encryption maps a subscriber profile to a particular UICC 201 and that UICC 201 only accepts those subscriber profiles that only it has signed or encrypted.

[0044] The subscriber profile wallet 501 transmits the subscriber profile that is being activated to the UICC 201, step 907. While this is depicted here as a direct transmission from the subscriber profile wallet 501 to the UICC 201, the transmission may be via one or more intermediaries, e.g., the mobile device 103 to which the UICC 201 is connected or via a host computer 601.

[0045] The UICC 201 decrypts the subscriber profile or verifies that it was signed by the UICC 201, step 909. If the signature or decryption indicates that the subscriber profile was signed or encrypted by the UICC 201 , step 911 , the UICC 201 stores the received subscriber profile as the active subscriber profile, step 913. Conversely, if the profile is not verified to have been encrypted or signed by the UICC 201, a message may be transmitted back that the activation of the subscriber profile has been rejected, step 915.

[0046] In an alternative embodiment, a subscriber profile associated with a particular UICC 201 and a particular operator is given a version number. The UICC 201 keeps a database of subscriber profiles that it has signed or encrypted. Thus, in this embodiment, in conjunction with encrypting or signing a profile, steps 805 and 821, the UICC 201 records the version number of the subscriber profile for the operator with which it is associated. In conjunction with the verification of decryption or digital signature, step 909, the UICC 201 confirms that the subscriber profile is the most recent subscriber profile the UICC 201 has processed for that operator. The UICC 201 only activates the most recent subscriber profile for that operator, thus preventing the activation of old subscriber profiles that have either been superseded or modified.

[0047] In an alternative embodiment, activation of a new profile is automatically performed based on the location of the mobile device 103. Figure 10 is a flow-chart illustrating on scenario for automatic profile change based on location. The mobile device continuously monitors whether in a Home location or in a Roam location, step 151. If the mobile device determines that it has entered into a roaming situation with respect to the currently active subscriber profile 501, step 153, the best profile to use in the new network is selected, step 155, and that profile is activated (as illustrated and discussed in conjunction with Figure 9), step 157. Of course, if there is no change in network, step 153, nothing is done with respect to subscriber profile. Alternatively, the subscriber profiles in a subscriber profile wallet may be associated with geographical locations, e.g., countries or continents, and a mobile device would operate to trigger a change in subscriber profile based on which geographic location it finds itself. This could, for example, be performed on each start-up of the mobile device and on each hand-off to new cells while travelling through a network. [0048] From the foregoing it will be apparent that a technology is presented herein that provides for an economical, flexible, powerful, scalable, and secure mechanism for creating, managing, and activating subscriber profiles such that mobile devices, including mobile devices with embedded UICCs, may be used with multiple operators using subscriptions with each of such multiple operators. The technology may further be utilized to allow an operator to activate an administrative profile on a mobile device, for example, to allow for administration or testing of the mobile device.

[0049] In an alternative embodiment, the security functions, e.g., cryptography and storing of cryptographic keys, may be performed in a secure zone of the mobile device 103 without relying on a separate UICC 201 to host that functionality. The technology described herein for providing a user secure access to multiple subscriber profiles which each may be linked to a separate operator may be implemented in such a secure zone of the mobile device 103 or in any other way in which the security functions, such as cryptography and secure management of cryptographic keys, may be implemented. Herein, for ease of explanation, the security function is described as hosted on a UICC 201. However, that is to be taken as illustrative only.

[0050] Although specific embodiments of the invention have been described and illustrated, the invention is not to be limited to the specific forms or arrangements of parts so described and illustrated. The invention is limited only by the claims.

[0051] We Claim: