JP5355787B2 - Method and apparatus for switching virtual SIM service contract based on user profile - Google Patents

Abstract

A system and method store provisioning data supporting a plurality of service providers in a VSIM internal memory unit of a mobile device. A user may specify a user profile to automatically enable provisioning data supporting one of the plurality of service providers stored in the VSIM internal memory unit to conduct a wireless communication when certain criteria values are satisfied. The automatic enabling of provisioning data may be determined based upon mobile device location, communication usage request and/or time and date.

Description

  The present invention relates generally to cellular telephone technology, and more particularly to a system and method for selecting and validating cellular telephone provisioning information based on user-specified preferences.

  Currently, mobile devices include, for example, Global System for Mobile Communication (GSM), Code Division Multiple Access (CDMA), and / or Universal Mobile Telecommunications System (UMTS) technology, depending on the selected service provider. Take advantage of the various technologies and formats you get. To store the necessary provisioning data that enables mobile devices to communicate with a wireless communication network, GSM and UMTS mobile devices utilize a subscriber identity module (SIM), commonly known as a SIM card . A SIM card is a removable smart card that contains a large amount of personal data such as mobile device provisioning data and phone books, stored SMS messages, downloaded data, and personalization settings. Since the SIM card is removable, a plurality of SIM cards with alternative provisioning information can be exchangeably inserted into the mobile device. In this way, GSM mobile devices and UMTS mobile devices can be used internationally simply by inserting a SIM card with the appropriate local provisioning information. By carrying a plurality of SIM cards each containing provisioning information for different service providers, the user can switch between service providers simply by physically switching the SIM cards. Furthermore, the exchangeable aspect of the SIM card allows the user to purchase a limited time prepaid SIM card. The limited time prepaid SIM card gives the user access to the communication network as long as the prepaid SIM card account is valid. This option allows the user to essentially maintain service contracts with a wide variety of service providers as opposed to traditional methods of maintaining service contracts with a single service provider. This allows the user to access a number of communication networks.

  The limited time prepaid SIM card option is particularly useful, for example, for international travelers who want access to a local wireless communication network during a trip but do not require further access to the local wireless communication network after returning home. However, since the user's personal SIM card is exchanged for a prepaid SIM card during the trip, the user cannot access the personal data stored in his / her personal SIM card. This can be frustrating to the user because personal data such as contact data stored in the phone book on the personal SIM is no longer accessible while the prepaid SIM card is in use. Furthermore, if the user travels outside the area where the prepaid SIM card provides wireless communication network access, the user must purchase a different prepaid SIM card with appropriate provisioning data for the new area. As a result, the user may have to carry several different prepaid SIM cards and know which prepaid SIM card contains the appropriate provisioning data for each region.

  Similar devices for other mobile network systems, such as Removable User Identity Module (RUIM), Universal Subscriber Identity Module (USIM), or Universal Integrated Circuit Card (UICC) (referred to herein as a “smart card”) Have been developed, but these devices have the same problem that prepaid locally provisioned smart cards are preferred and personal data is lost when RUIM, USIM or UICC is removed .

  Some CDMA mobile devices store provisioning information on removable cards that can be transferred from mobile device to mobile device, but many CDMA phones do not provide this functionality. Thus, many CDMA device users are not given the option to use their personal mobile devices when traveling abroad. In general, these users must rent mobile devices or purchase disposable devices that are provisioned for local use or that can accept SIM cards.

  Yet other non-international travel users may discover the ability to quickly access the wireless communication networks of attractive service providers. A typical mobile device user subscribes to a single service provider for a relatively long term wireless communication service. A user may select a service provider based on a number of considerations including, but not limited to, cost, network coverage, and available services. Service providers are good in some aspects, but may not be sufficient in other aspects. The user may need to make a trade-off when selecting a single service provider. By using a SIM card, the user is not restricted to a single service provider. The user may select the service provider to use based on which service provider provides the best service for the user's specific needs. The user can then simply replace the current SIM card with a desired service provider's SIM card on a usage basis. For example, suppose service provider A provides excellent network coverage for voice communications on the east coast, but not on the west coast, and provides a slow data service. While on the east coast and making a voice call, the user may choose to insert Service Provider A's SIM card. However, if the user wants to travel the West Coast or make a data call, the user may choose to replace Service Provider A's SIM card with another Service Provider's SIM card. In this way, the user can optimize wireless communication services, but must grasp and carry multiple physical SIM cards.

U.S. Patent Application No. 11 / 963,918

  Accordingly, systems and methods that allow users to more easily change provisioning data according to location, usage, and / or time are desired.

  In various embodiments, systems and methods are provided for modifying provisioning data contained within a memory of a mobile device. Provisioning data is stored in a virtual SIM (VSIM) card that may be included as part of the internal memory of the mobile device. Provisioning data for multiple service providers can be stored in VSIM and selectively enabled and disabled according to user-defined profiles according to various criteria category values such as time, location, and / or usage requirements. obtain.

  The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and, together with the above general description and the following detailed description, explain the features of the invention. To help.

It is a system diagram showing an implementation system that provides a virtual SIM (VSIM) service contract. 1 is a system block diagram of a mobile device suitable for use in one embodiment. FIG. FIG. 5 is a process flow diagram illustrating method steps of an implementation method for obtaining a VSIM service contract. 2 is an exemplary preferred roaming list (PRL) system and acquisition table. 1 is a system diagram of a cellular communication network that implements a VSIM service contract to connect calls. FIG. FIG. 5 is a process flow diagram illustrating steps of an implementation method for a mobile device to complete a communication call using a VSIM service contract. FIG. 4 is a hardware / software architecture diagram of a mobile device and VSIM showing the flow of data in provisioning data requests and responses. FIG. 6 is a system diagram illustrating an alternative implementation communication system in which a mobile device may obtain a VSIM service contract. FIG. 6 is a process flow diagram illustrating steps of an alternative implementation method for obtaining a VSIM service contract. FIG. 2 is a system diagram illustrating an alternative implementation communication system in which a mobile device can obtain VSIM service contracts as well as personal data stored in a remote VSIM server / database. FIG. 4 is a process flow diagram showing steps of an alternative implementation method for obtaining a VSIM service contract and personal data stored in a remote VSIM server / database. FIG. 4 is a menu tree diagram illustrating an exemplary cascade of menus presented to a user when creating or editing a user profile. FIG. 4 is an exemplary user profile data table used in one embodiment for selecting and switching VSIM service contracts according to user-specified preferences. FIG. FIG. 6 is an exemplary criteria category value table used in one embodiment for selecting and switching VSIM service contracts according to user-specified preferences. FIG. FIG. 4 is an exemplary priority list index data table used in one embodiment for selecting and switching VSIM service contracts according to user-specified preferences. FIG. FIG. 6 is a process flow diagram illustrating steps of an embodiment for creating or editing a user profile. FIG. 6 is a process flow diagram illustrating the steps of one embodiment for automatically selecting a VSIM service contract to complete a call according to user-specified preferences. FIG. 6 is an exemplary user profile data table for use in an alternative embodiment for selecting and switching VSIM service contracts according to user-specified preferences. FIG. 6 is a process flow diagram illustrating steps of an alternative embodiment for creating or editing a user profile. FIG. 5 is a process flow diagram illustrating steps of an alternative embodiment for automatically selecting a VSIM service contract to complete a call according to user-specified preferences.

  Various embodiments will be described in detail with reference to the accompanying drawings. Wherever possible, the same reference numbers will be used throughout the drawings to refer to the same or like parts. References made to particular examples and implementations are for illustrative purposes, and are not intended to limit the scope of the invention or the claims.

  As used herein, the term mobile device refers to cellular phones, personal digital assistants (PDAs), palmtop computers, laptop computers, wireless email receivers (e.g., BlackBerry® and Treo® devices). ), A multimedia internet-enabled cellular phone (eg, iPhone®), and any one or all of similar personal electronic devices including a programmable processor and memory. In a preferred embodiment, the mobile device is a cellular handset that can communicate via a cellular telephone network (eg, a cell phone).

  As used herein, the term “server” refers to any of a variety of commercially available computer systems configured to operate in a client-server architecture. In particular, the term “server” generally includes a processor, a memory (eg, hard disk memory), and a network interface circuit configured to connect the server processor to a network, such as the Internet or a cellular telephone network. In particular, it refers to a server accessible to the Internet.

  Recently, some users of mobile devices have begun to subscribe to multiple service providers for services so that different service providers can be used for different purposes. These users store provisioning data for different service contracts on the SIM card and simply replace the SIM card containing the desired provisioning data. In addition, alternative service provider contracts have become available to mobile device users. Allows users to access a service provider's communications network for a limited period of time, rather than requiring the user to commit to a long-term service contract that maintains a monthly account with a single service provider Short term prepaid service contracts from various service providers are available to users. In general, a user using a short term prepaid service contract (PPSC) can access a communication network for a limited number of minutes, a limited number of bytes of data to be transferred, or a combination thereof. A short term prepaid service contract expires when a user accesses the communication network for a limited number of minutes, transfers a limited number of bytes of data, or both. For simplicity, this specification will describe the PPSC as only fractional. However, the embodiments described herein provide a PPSC period (e.g., a certain number of minutes, days, weeks or months), bytes of data transferred, or hours and minutes and bytes of data transferred. Those skilled in the art will appreciate that a combination of these can function in a similar manner. Traditionally, short term prepaid service contracts are established by purchase of a subscriber identity module (SIM) card. A replaceable SIM card containing the necessary provisioning data to allow access to the service provider's communication network can be purchased and inserted into the user's mobile device. Once activated, a service provider that supports short-term prepaid service contracts can monitor usage and deny access to the communications network when the service contract expires.

  The SIM card stores the necessary provisioning data, such as the service subscriber key used to identify the mobile device to the wireless communication network to allow the mobile device to access a specific communication network Removable memory chips or smart cards used in GSM and UMTS mobile devices. A user can use a different mobile device by simply removing the SIM card from one mobile device and inserting it into another mobile device. A typical low cost SIM card has as little as 2-3 KB of memory sufficient to hold provisioning data and possibly a personal phone book. The data stored on the SIM card is used directly by telephone. SIM cards with additional applications are available in many storage sizes, the largest being able to store up to 1 gigabyte of information. Smaller size SIM cards that can store up to 32KB or 16KB are most prevalent in the area of underdeveloped GSM networks.

  The use of SIM cards is essential in GSM cellular telephone networks. SIM cards store network-specific information used to authenticate and identify subscribers on the network, the most important of which are ICCID, IMSI, authentication key (Ki), and local area Identification information (LAI). The SIM also stores other carrier specific data such as SMSC (Short Message Service Center) number, Service Provider Name (SPN), Service Dialing Number (SDN), and Value Added Service (VAS) applications. The equivalent of a SIM card in a UMTS cellular telephone network is called a universal integrated circuit card (UICC). A CDMA phone may include a similar removable user identification module (RUIM).

  SIM cards have become an ideal platform for distributing PPSCs due to their portability, but their use is not without their drawbacks. For example, each short-term prepaid service contract SIM card (prepaid SIM) is provisioned with a pre-provisioned phone number. Each time a particular prepaid SIM is inserted into the mobile device, the mobile device's phone number may change. Thus, each time a user exchanges a prepaid SIM, a caller who is not aware of the prepaid SIM exchange cannot contact the user's mobile device. Furthermore, since the prepaid SIM is replaced with the user's personal SIM card, the user's personal data stored in the personal SIM card is not available to the user while the prepaid SIM is being used. Each prepaid SIM is also generally serviced by a single service provider. If the user wants to use another service provider's communication network, the user must remove the prepaid SIM card and replace it with another card. Thus, if a user travels outside the area where a particular SIM card is provisioned, the user must exchange the SIM card for another card. This is the case for international travel.

  Similarly, if a user wishes to access another service provider's communication network to take advantage of some of the great features, the user must also replace the SIM card with another card. For example, one service provider may provide better voice communication and other service providers may provide better data communication. This constant replacement of the physical SIM card can be cumbersome. The user must not only physically change the SIM card, but also carry a wide variety of SIM cards.

  Various embodiments address these issues by creating a virtual SIM (VSIM) card function that enables a portion of the mobile device's internal memory to store provisioning information for various service providers. ease. VSIM can be implemented on all mobile devices including GSM, UMTS and CDMA types. A user may purchase a VSIM service contract (such as PPSC) from any service provider and download the corresponding provisioning data for that service provider. Provisioning information can be loaded into the VSIM of the mobile device. In addition, the user can store provisioning information for multiple service contracts on the VSIM. The user may then switch service providers simply by setting a user profile to control switching service contracts in response to various reference category values specified by the user. When a user travels from one area to another (ie, international travel), the user can quickly access and implement appropriate provisioning information for the area where the user is currently located. Furthermore, the user can maintain a constant telephone number despite changes in the provisioning information implemented. In this way, the caller can continue to contact the user's mobile device regardless of which service contract is currently active on the VSIM.

  FIG. 1 illustrates an overall system of one embodiment in which each service provider providing a VSIM service contract operates its own VSIM service contract provisioning (SCP) server 102-105. The user connects to the service provider's VSIM SCP servers 102-105 via the communications network 100 and downloads the appropriate provisioning data to support the desired service contract, thereby enabling the VSIM PPSC or VSIM monthly service contract (MSC). You can purchase (collect VSIM service contract) and get it. The communication network 100 can be, for example, either a cellular telephone network or the Internet. For simplicity, various embodiments will be described as the mobile device 101 is connected to the VSIM SCP server via a cellular telephone network. However, those skilled in the art will appreciate that the user can also connect to the VSIM SCP server via the Internet and then transfer the SCP provisioning data to the mobile device VSIM. Although four separate VSIM SCP servers 102-105 are shown in FIG. 1, the number of VSIM SCP servers will depend on the number of service providers offering VSIM service contracts. VSIM SCP servers 102-105 contain internal memory storage units such as mass storage disk drives or store provisioning data and account status for each individual VSIM service contract (PPSC or MSC) running on the system It can be connected to a corresponding VSIM SCP database 106-109 that can. Each of the VSIM SCP servers 102-105 and the VSIM SCP databases 106-109 may be operated by different service providers. Furthermore, each VSIM SCP server 102-105 and / or VSIM database 106-109 may provide various service contracts to the user. For example, each VSIM SCP server 102-105 and / or VSIM database 106-109 may provide a user with either a VSIM PPSC or a VSIM MSC. Further, various VSIM service contracts may provide voice-only services, data-only services, or combinations thereof.

  Various embodiments include various mobile devices such as, for example, cellular phones, personal information terminals with cellular phones (PDAs), mobile email receivers, mobile web access devices, and other processor equipped devices that may be developed in the future. It can be implemented in any of the devices. Further, the embodiments described above can be implemented in any of a variety of computing devices, including but not limited to desktop and laptop computers.

  FIG. 2 illustrates exemplary components of a mobile device 101 that can support various embodiments. A typical mobile device 101 includes a processor 191 coupled to an internal memory 192 and a user interface display 11. The internal memory 192 includes a VSIM memory unit 193 that is used to store provisioning information for a plurality of VSIM PPSC accounts. VSIM memory unit 193 may be a partition within mobile device internal memory 192 or may be a separate internal memory unit (ie, a separate memory chip). Furthermore, the VSIM memory unit 193 may store personal data downloaded from the VSIM server 130 for use with applications running on the mobile device processor 191.

  Mobile device 101 may include an antenna 194 for transmitting and receiving electromagnetic radiation connected to a wireless data link and / or connected to a cellular telephone transceiver 195 coupled to processor 191. In some implementations, the transceiver 195 used for cellular telephony and the portions of the processor 191 and memory 192 are referred to as an air interface because the combination provides a data interface over a wireless data link. In addition, the mobile device 101 includes a speaker 18 for generating audible sound and a microphone 19 for sensing sound, such as receiving a user's voice. Both microphone 19 and speaker 18 may be connected to processor 191 via vocoder 199, which converts the analog electrical signal received from microphone 19 into a digital code and converts the digital code received from processor 191 to analog electrical The speaker 18 can convert the analog electrical signal into a sound wave. In some implementations, the vocoder 199 may be included as part of the circuitry and programming of the processor 191.

  The processor 191 can be any programmable microprocessor, microcomputer or one or more multiprocessor chips that can be configured by software instructions (applications) to perform various functions, including the functions of the various embodiments described below. It can be. Depending on the mobile device, a plurality of processors 191 may be provided, such as one processor dedicated to wireless communication functions and one processor dedicated to executing other applications. In general, software applications may be accessed and stored in internal memory 191 before being loaded into processor 192. In some mobile devices, processor 191 may include internal memory sufficient to store application software instructions. As used herein, the term memory refers to all memory accessible by processor 191 including internal memory 192, VSIM memory unit 193, and memory within processor 191 itself. Internal memory 192 and VSIM memory unit 193 can be volatile memory, or non-volatile memory such as flash memory, or a mixture of both. In one preferred embodiment, the VSIM memory unit 193 is a non-volatile memory for holding service contract provisioning data when the mobile device is turned off. Mobile devices typically also include a keypad 13 and menu selection buttons or rocker switches 12 for receiving user input.

  FIG. 3 shows a process flow of exemplary method steps that may be performed to obtain VSIM service contract provisioning data. In operation, the mobile device 101 is stored in a VSIM memory unit 193 that allows the mobile device 101 to connect with a wireless data network for a limited purpose of communicating with any of the VSIM SCP servers 102-105. It can be programmed with sufficient general provisioning data. General provisioning data does not allow mobile device 101 to establish normal communications, but mobile device 101 connects with VSIM SCP servers 102-105 to purchase selected service contract provisioning data Make it possible. Each VSIM SCP server 102-105 may be operated by a different service provider, but some service providers offer different types of service contracts, deal with different areas, or provide duplicate functionality Several VSIM SCP servers can be run to do this. Mobile device 101 stores in its internal memory 192 or VSIM memory unit 193 a list of server network addresses (e.g., IP addresses or URLs) for servers of various carriers in different areas offering VSIM service contracts. obtain. These server network addresses and corresponding service providers may be described, for example, by region, country, or continent.

  Referring to FIG. 3, if the menu is organized by region (for service carriers), a list of possible regions is displayed to the user on the mobile device display 11 (step 201). This menu is not limited to various events including but not limited to initial power up, when a previously purchased VSIM PPSC expires, or when the mobile device 101 has its current provisioning data at its current location. It can be presented whenever it is determined that it will not work. The user may select a region where the user wishes to purchase a VSIM service contract by using any of various user interface keys 12, 13 and switches incorporated within the mobile device 101. The region selection is received by the mobile device processor 191 (step 202), and the mobile device processor 191 prompts the user with a list of possible VSIM service contract service providers for the selected region (step 203). Using again any of the various user interface keys 12, 13 and switches incorporated within the mobile device 101, the user selects a VSIM service contract service provider from the displayed list. The user selection of the service contract service provider is received by the processor 191 of the mobile device 101 (step 204). Based on the received VSIM service contract service provider selection, the mobile device processor 191 accesses the corresponding server network address, initiates a communication link, and logs in (step 205).

  Upon logging into the appropriate VSIM SCP server (102-105), the mobile device receives a list of VSIM service contract options, presents them on the display, and prompts the user to select (step 206). These VSIM service contract options may include, for example, PPSC, MSC, and various combinations of voice plans and data plans, as well as various time periods or usage restrictions. In response, the user selects a service contract option from the displayed list. The processor 191 of the mobile device 101 receives the user's selection of service contract options (step 207), sends the user's selection to the selected VSIM SCP server (102-105), and the selected VSIM SCP server (102 to 105). Based on the received selection, the service contract provisioning data is downloaded to the mobile device VSIM memory unit 193 via the established data connection by the VSIM SCP server (102-105) (step 209). Finally, the VSIM service contract is activated and activated on the mobile device 101 (step 210). The selected VSIM service contract can be loaded by loading the corresponding provisioning data into the VSIM provisioning data buffer 314 (see FIG. 7) or by directing the mobile device processor 191 to the memory location that stores the corresponding provisioning data via the pointer list. Can be validated by doing

  As part of the enabling and activating step, a code identifying mobile device 101 is sent to the selected VSIM SCP server (102-105), along with other VSIM service contract account data, the VSIM SCP server (102- 105) mass storage devices or corresponding VSIM SCP databases 106-109. The stored mobile device identification code and service contract account data allow VSIM SCP service providers to monitor individual VSIM service contract accounts and enable communication as long as the VSIM service contract is valid. become. As an alternative step (not shown), any of several well-known electronic payment methods and electronic commerce methods to handle the exchange of funds prior to downloading provisioning data to VSIM memory unit 193 Can be implemented.

  In order to establish and route wireless communication calls, conventional mobile devices and service networks are assigned special codes. These codes, described below, identify individual mobile devices 101 to various communication networks and identify accessed networks to mobile devices. Without the proper code, a communication link cannot be established. Therefore, in order to give the VSIM service contract to the mobile device 101, the network identification code is downloaded into the VSIM service contract provisioning data, the mobile device identification code corresponds to the mass storage device VSIM SCP server (102-105) or the corresponding Uploaded to VSIM service contract account data stored in VSIM SCP database (106-109). Whenever the VSIM SCP server (102-105) that is processing the VSIM service contract account for mobile device 101 attempts to allow mobile device 101 to access the communications network using the mobile device's identification code, Monitor the use of the mobile device 101 to check the mobile device 101 and determine whether the VSIM service contract account is valid. For example, if the VSIM service contract is PPSC, the VSIM SCP server (102-105) may determine whether the VSIM PPSC has expired. If the VSIM PPSC expires, the VSIM SCP server (102-105) may provide the user with an opportunity to “recharge” the VSIM PPSC account by purchasing additional prepaid services (e.g., purchasing additional fractions). Or if the user refuses to purchase additional service hours, after expiration, the mobile device 101 may not be given access to the communication network.

The identification code includes:
(a) an electronic serial number (ESN), which is a unique 32-bit number programmed when the mobile device is manufactured;
(b) a mobile identification number (MIN), which is a 10-digit number derived from a unique phone number assigned to the mobile device;
(c) a system identification code (SID), which is a unique five-digit number assigned to each wireless service provider by the FCC;
(d) CDMA type mobile, which is a priority listing of approved SIDs that service providers give to mobile devices to determine which network SIDs are allowed for the mobile devices to use for services. Preferred roaming list (PRL) for devices / Public Land Mobile Network (PLMN) for GSM type mobile devices,
(e) An authentication key (A key), which is a shared secret key that can be generated after initial authentication.

  While ESN is generally considered a permanent part of mobile device 101, MIN, SID and PRL / PLMN are programmed into VSIM 193 when a VSIM service contract is purchased and activated. In some embodiments, the ESN can be programmed into VSIM 193 as well. In such an embodiment, the ESN programmed on the VSIM may be examined as opposed to the ESN of the mobile device 101. Each time the mobile device 101 accesses the communication network, either ESN or MIN is examined by the VSIM SCP server to ensure that the VSIM service contract is still valid. If the VSIM service contract is valid, the VSIM SCP server will connect the communication request, start decrementing the remaining time if the VSIM service contract is a PPSC account, or use time if the VSIM service contract is an MSC Is incremented. In this way, the service provider can ensure that the mobile device 101 is only allowed to access a communication network that matches the terms of the VSIM service contract.

  As part of the downloaded provisioning data, CDMA type mobile devices are programmed using PRL. GSM type mobile devices are provisioned using PLMN, which acts in the same way as PRL. For simplicity, this embodiment will be described using CDMA terminology. However, similar implementation systems and methods may be implemented in GSM type mobile devices in a similar manner.

  A user of mobile device 101 may purchase a VSIM service contract from a particular service provider, but the service provider may use other services provider's communications network to allow other customers You may have a contract with a service provider. This allows service providers to provide their customers with a wider coverage zone without having to install their own equipment throughout the coverage zone. In some situations this may be referred to as “roaming”. Thus, when a user purchases a VSIM service contract through a particular service provider, the user may be given access to and use of other service provider's communication networks. The PRL is a priority list of alternative communication networks that a user can access if the primary communication network is not available.

  In a given area, multiple wireless communication networks and cellular communication networks may be operated by multiple service providers. In addition, other dedicated and / or non-commercial communication networks may operate in certain areas. To determine which communication network the mobile device 101 can utilize in a given area, the mobile device 101 determines which channel or analog frequency is scanned and with what priority to establish a communication link In order to access the downloaded PRL for the selected service contract stored in VSIM 193.

  The PRL is maintained so that the mobile device can easily determine which communication networks cover a common geographic area. Reference to a common geographic area means a common radio coverage area. Moreover, communication networks serving in a common geographic area are prioritized, i.e., ranked from most desirable to least desirable. The mobile device is programmed to attempt to obtain a service that begins with the most desirable communication network available in the current geographical area of the mobile device. Since communication networks generally provide services only within a limited geographic area, it is useless to attempt to obtain services on a communication network outside the current geographical area of the mobile device.

  On many communication networks, it is recommended to update the PRL regularly if the user frequently operates the mobile device outside the home system, especially in multiple different areas. This allows the mobile device to select the best roaming carrier, especially the “roaming partner” where the home system has a cost-saving roaming agreement, rather than using an unaffiliated carrier. It becomes possible. The PRL file can also be used to identify the home system with the roaming partner, so the PRL becomes the actual list that determines the user's total coverage for both home and roaming coverage.

  Associated with each communication network in the PRL is a system ID (SID) and corresponding acquisition parameters (bandwidth, channel, etc.) for each communication network. The PRL is created, loaded and updated by the VSIM service contract service provider. When a user purchases and activates a VSIM service contract, the provisioning data downloaded to VSIM 193 on mobile device 101 replaces the previous PRL so that the new communication network SID and acquisition parameters are recognized by mobile device 101 .

  The PRL is maintained by the service provider and is usually not accessible to the user. Many service providers offer the ability for users to download the latest PRL to their devices by dialing an over-the-air (OTA) feature code such as * 228. Alternatively, the latest PRL can be downloaded to the mobile device via a hardwired connection. Similarly, the PRL can be updated to the VSIM 193 of the mobile device 101 by a network VSIM push of a user initiated download call, such as by * 228.

  The PRL contains two tables (along with some header and overhead information). The two tables are a system table and an acquisition table. The system table is a priority list of communication networks (home system and roaming network) that the mobile device is allowed to access. Each communication network entry in the system table belongs to a geographical area known as GEO. Each entry also defines an acquisition table index that identifies the frequency associated with that particular communications network and the type of instructions that should be displayed to the user when the user is receiving service from that network. Give with a roaming indicator. The acquisition table is an indexed list of frequencies that the mobile device can search for a particular network. The acquisition table optimizes network acquisition time by identifying a limited number of frequencies to be searched by the mobile device, rather than requiring the mobile device to search the entire frequency spectrum.

  FIG. 4 shows an exemplary system table and acquisition table for a PRL for a particular geographic region. The acquisition table 152 includes a record describing communication channels or frequencies in a priority communication order from top to bottom. For the acquisition table shown, for example, the mobile device will first contact the PCS CDMA block B channel, then contact the block A channel, and then contact channels 283, 699, 384, and 777. If the mobile device cannot contact these CDMA channels, the mobile unit will attempt to contact the network using the cellular analog system A frequency.

  The PRL system table 151 includes a record having several fields. The “SID” field contains the system identification number of the preferred communication network. “Selective Preference” identifies the relative priority of each network with respect to connection designability. As shown, for example, it is more desirable for a mobile device to connect with a VSIM service contract home system SID that is more effective than other networks. The “roaming indicator” field indicates the roaming indication display status on the mobile device as either “off” or “on” depending on which network the mobile device is connected to. In general, if the mobile device is connected to a home system with a valid VSIM service contract, the roaming indicator is turned off. The “acquisition index” field indicates the acquisition table record number associated with the SID. Thus, the “Acquisition Index” field entry indicates the channel or frequency associated with a particular SID. As shown, for example, the SID (acquisition index 0) of the home system is associated with the PCS CDMA block B channel (acquisition table record 0). Similarly, the SID (acquisition index 3) of the roaming partner 3 is associated with the cellular analog system frequency (acquisition table record 3).

  Therefore, when the mobile device 101 downloads the VSIM service contract provisioning data to the VSIM memory unit 193 (step 209), the mobile device 101 downloads the PRL corresponding to the VSIM service contract. By downloading the PRL from the VSIM SCP server (102-105) and / or the VSIM SCP database (106-109) to the VSIM memory unit 193 of the mobile device 101, the mobile device 101 can communicate with a communication network that supports the VSIM service contract. Given all necessary parameters to establish a communication link.

  FIG. 5 shows an exemplary system diagram of a mobile device 101 that uses a VSIM service contract to establish a call. When mobile device 101 selects a VSIM service contract account to establish a call, mobile device 101 places provisioning data for the selected VSIM service contract in VSIM memory unit 193 and selects the selected VSIM service. The contract PRL may be copied to the active call application memory. VSIM memory unit 193 may include provisioning data for multiple VSIM service contracts. The selected VSIM service contract may be any of the various types of VSIM service contracts provided on the VSIM SCP server (102-105) and / or the VSIM SCP database (106-109). This step essentially swaps the selected VSIM service contract PRL with the PRL previously in memory. Using the selected VSIM service contract PRL, the mobile device acquires the communication network via the base station 120 and uses the described frequency to make a request to complete a voice or data call. Base station 120 may be part of a communication network described in a downloaded PRL that acts as a portal to cellular telephone network 122. The base station 120 may be in communication with a server 121 that receives a communication request from the mobile device 101 via the base station 120. The communication request may include VSIM service contract account information indicating a service provider supporting the selected VSIM service contract account and the ESN / MIN of the mobile device 101 making the communication request. Based on the VSIM service contract account information, the communication request is routed via the cellular telephone network 122 to a VSIM SCP server (shown as 102 in FIG. 5) that supports the VSIM service contract account. The VSIM SCP server may reference data stored in either the VSIM SCP server's mass storage or the corresponding VSIM SCP database (106) to verify the VSIM service contract account and the requesting mobile device 101. If the VSIM service contract account is still valid (for example, if the PPSC account has enough access time left or the MSC is still active), the VSIM SCP server (102) checks the VSIM service contract account and Allow the mobile device 101 to connect to the intended recipient. The scheduled recipient may be another mobile device 125, a server 126 hosting data, a computing device 127, and / or a landline phone 129. The call can then be routed via the cellular telephone network 122 to the intended recipient. If the wireless device (eg, mobile device 125 or computing device 127) is the intended recipient, the call may be routed through the second base station 128. Alternatively, the intended call can be routed by the conventional telephone network 122 to the intended recipient via a landline connection.

  FIG. 6 shows a process flow of steps that may be performed to connect a call using a VSIM service contract. A user of the mobile device 101 may have several different VSIM service contract accounts stored in the mobile device VSIM memory unit 193. The user must first select the VSIM service contract account he wishes to implement to connect the call (step 220). By selecting the desired VSIM service contract account, the processor 191 retrieves the corresponding provisioning data from the VSIM memory 193 and loads it into the active memory buffer 314 for use by the mobile device 101. Using the PRL data associated with the selected VSIM service contract account, the mobile device 101 establishes a communication link with an available communication network and makes a call request (step 221). Based on the VSIM service contract account data included in the call request, the VSIM SCP server (shown as 102 in FIG. 5) is contacted to verify the VSIM service contract account (step 222). In order to confirm the VSIM service contract account, related data identifying the VSIM service contract account and the mobile device 101 (ESN / MIN) is transmitted to the VSIM SCP server 102. After the identification information is received by the VSIM SCP server 102, the identification data is used to access VSIM service contract account data stored in either the VSIM SCP server 102 mass storage device or the corresponding VSIM SCP database 106. To do. The VSIM SCP server 102 examines the VSIM service contract account data to ensure that the VSIM service contract account is still valid (decision 225).

  If the VSIM service contract account is not a valid account (i.e., decision 225 = No), the VSIM SCP server may optionally indicate that the VSIM service contract account is invalid and an option to purchase a valid VSIM service contract account Is returned to the mobile device 101 (decision 227). If the user responds affirmatively (i.e., decision 227 = yes), the mobile device and the VSIM SCP server will allow the mobile device 101 user to purchase a valid VSIM service contract account as shown in FIG. Steps 201 to 210 shown in FIG. 5 are implemented (Step 228). The call is then connected using the newly activated VSIM service contract (step 231). Alternatively, if an optional step is not provided that gives the user the ability to purchase a valid VSIM service contract account, the call is simply terminated (step 232). Similarly, if the user refuses to purchase a valid VSIM service contract account (ie, decision 227 = No), the call is terminated (step 232).

  However, if the VSIM service contract account is valid (i.e., decision 225 = yes), the VSIM SCP server 102 determines whether there is enough room on the VSIM service contract account to support the call request. Judgment is made (decision 226). If the VSIM service contract is an MSC, this determination may involve determining whether there is enough “in plan” or whether the excess applies. If the VSIM service contract is a PPSC, this determination may involve determining whether enough remains on the PPSC. A predetermined fractional threshold may be used to determine if “sufficient” minutes are available on the VSIM service contract account. If there is enough remaining on the VSIM service contract account (ie, decision 226 = yes), the call is connected using the VSIM PPSC account data (step 231). The VSIM SCP server 102 continues to monitor the call after the call is connected to determine how many minutes should be counted against the VSIM service contract account after the call is completed. Alternatively, the VSIM SCP server 102 can remove minutes from the VSIM PPSC account as the call progresses so that, as a result of the call, the caller can be notified if the remaining minutes are below the threshold during the call. Can be decremented.

  If there is not enough remaining on the VSIM service contract account (i.e. decision 226 = No), such as when all prepaid minutes have been used, or all `` in-plan '' minutes have been used, The VSIM SCP server sends a message to the mobile device 101 indicating that the VSIM service contract account has expired or nearly expired and giving the user of the mobile device 101 an option to recharge the VSIM service contract account (decision 229) . If the user chooses to recharge the VSIM service contract account (i.e., decision 229 = yes), the remaining time on the VSIM service contract account is set or reset to the number of additional minutes purchased (step 230). ), Connect the call as requested (step 231). However, if the user refuses to recharge the VSIM service contract account, the call request ends (step 232). In embodiments where the VSIM service contract account is an open-ended account (ie, no restrictions on outgoing calls), steps 226, 229, and 230 may be omitted.

  In one embodiment, the VSIM SCP server may decrement time from the VSIM service contract while the call is in progress. If the remaining time on the VSIM service contract account then falls below a threshold, the VSIM SCP will place the call on hold and provide the caller with an opportunity to recharge the account, etc. An alarm is issued (step 229). If the user chooses to purchase additional time, the account balance is reset accordingly (step 230) and the call continues (not shown, but similar to step 231). However, if the user chooses not to purchase additional time (ie, decision 229 = No), the call is terminated as soon as the remaining balance reaches 0 (step 232).

FIG. 7 shows a mobile device hardware / software architecture 300 along with a VSIM hardware / software architecture 310. When the mobile device 101 is functioning, the various applications 306 run on or request services from various hardware elements of the mobile device. For example, these hardware elements include a processor and internal memory, an input element such as a keyboard or microphone, an output element such as a display or speaker (none shown), a cellular transceiver, a Global Positioning System (GPS) receiver And communication units such as WiFi wireless transceivers and Bluetooth local wireless transceivers. Some applications 306 may access a mobile device's cellular transceiver to initiate a telephone or data call. In order to initiate a telephone or data call, application 306 needs to access provisioning data stored in VSIM memory unit 193. Application 306 requests this provisioning data through hardware / software architecture 300 and 310. As shown in FIG. 7, the application 306 can communicate with the device operating system 304 via the API layer 305. The API layer 305 includes code for supporting an application 306 request to create a processor service from code provided by the operating system 304. The operating system 304 performs basic tasks such as controlling and allocating memory, prioritizing system requests, controlling input / output devices, and enabling file system networking and management. The operating system 304 communicates with various device resources via the physical layer 303. One or more driver layers 302 may be provided to control various device elements, such as a connected modem or transceiver. Driver layer 302 includes specific types of computer software developed to allow interaction with specific hardware elements. In general, this is to communicate with a particular hardware element through a particular computer bus or communication subsystem to which the hardware element is connected, to give commands to the hardware element, and / or to receive data from the hardware element And an essential interface to the operating system 304 via the physical layer 303 on the other end. The hardware interface 301 includes a physical connection with a hardware device, such as a socket or outlet to which a hardware element connects.

  In various embodiments, when an application 306 running on the mobile device 101 requests provisioning data stored in the VSIM memory 315, the data request reaches the hardware interface layer 301 and the VSIM Propagates through device hardware / software architecture 300 until it enters VSIM hardware / software architecture 310 via hardware interface 311. This data access request may be by direct memory access and / or general purpose input / output (GPIO). The VSIM hardware interface layer 311 can include connector pins that can be physical connections that plug the VSIM 193 into the mobile device 101, or the bus connection to which the VSIM 193 is connected when the VSIM is integrated into the internal memory 192 of the mobile device 101. It can be. After being received at the VSIM hardware layer 311, the request for provisioning data corresponding to the currently active VSIM service contract in the VSIM memory 314 generated in the application 306 propagates up the hardware / software architecture 310. . The driver 302 accesses the VSIM data via the hardware interface 311 and gives information to the application. Alternatively, the data request is communicated from the hardware interface 311 to the driver layer 312. As described above, the driver layer 312 includes a particular type of computer software that has been developed to allow interaction between the VSIM memory unit 193 in the physical layer 313 and the hardware interface 311. The data request then accesses the data in a valid VSIM provisioning data buffer 314, which is a memory block used to hold provisioning data for the service provider currently selected for use. As a result, the currently selected VSIM service contract provisioning data 314 is accessed and the requested information is passed to the requesting application 306 in the reverse manner. VSIM provisioning data buffer 314 may be an embedded file system or a secure file system implementation. The embedded file system abstracts the operating system (OS) to access VSIM data as a logical file. A secure file system provides an additional level of protection against spoofing of VSIM data by software or hardware encryption.

  As described above, the VSIM memory unit 193 may include multiple VSIM service contract account provisioning data sets 315 for different VSIM service contract accounts purchased by a user. When the user selects a particular one of the stored VSIM service contract accounts for use, such as a VSIM service contract that provides voice call services, the mobile device processor 191 accesses as described above. Access the selected VSIM provisioning data 315 via layers 311-313 and copy the provisioning data to a valid VSIM provisioning data buffer 314. Thereafter, the access request received from the application is provided with provisioning data from a valid VSIM provisioning data buffer 314.

  Alternatively, provisioning data corresponding to each of the plurality of VSIM service contract accounts may be stored separately at a location within the VSIM memory unit 193. The mobile device processor 191 may maintain a valid VSIM pointer in the buffer that points to the currently valid VSIM service contract provisioning data (by holding the memory address of the corresponding data). When a different VSIM service contract is selected to complete a voice or data call, the valid VSIM pointer stored in the pointer buffer indicates the mobile device processor 191 VSIM memory for the currently selected VSIM service contract provisioning data. Changed to direct to memory location in unit 193.

  The hardware / software architectures 300 and 310 shown in FIG. 7 are merely meant to represent one example configuration of data and software for implementing various embodiments. Other software / hardware architectures with equal effectiveness may be used, as one skilled in the art of cellular handheld device design and programming will appreciate.

  An alternative embodiment for providing a VSIM service contract account is shown in FIG. In this alternative embodiment, a single VSIM SCP server 110 serves as a central server for multiple VSIM SCP databases 106-109. For example, mobile device 101 may connect to a single central VSIM SCP server 110 via communication network 100. A single central VSIM SCP server 110 allows multiple VSIM SCP databases to allow mobile device 101 to connect with a single VSIM SCP server 110 and obtain VSIM service contract accounts from various service providers. (106-109). As in the previous embodiment, the VSIM SCP databases 106-109 each contain the necessary provisioning data for each VSIM service contract provided by each of the respective service providers. Although the user may maintain various VSIM PPSC and MSC accounts, by providing a central VSIM SCP server 110, this embodiment can be used to allow the user to be assigned a single phone number. Note that a single central VSIM SCP server 110 can be a regional server, and mobile device 101 can connect to multiple central VSIM SCP servers depending on which specific region mobile device 101 is currently located in. I want to be. For example, if mobile device 101 is currently located in Europe, mobile device 101 may connect to VSIM SCP server 110 serving Europe. Similarly, the central VSIM SCP server 110 may be located in other geographic regions (eg, Asia, West Asia, East Asia, Africa, South America, etc.). The regional VSIM SCP server 110 may serve different sized geographic regions depending on the number of mobile devices 101 operating in the region. As more and more mobile devices operate within a region, the size of the region served by a single VSIM SCP server 110 may decrease, and vice versa.

  FIG. 9 illustrates alternative method steps that may be implemented to obtain a VSIM service contract account. In this embodiment, a single central VSIM SCP server is connected to multiple VSIM databases. Each of the plurality of VSIM databases is operated by a separate service provider to give the user the ability to purchase any of the various VSIM service contracts provided by the service provider. In this embodiment, the user connects to a central VSIM SCP server to purchase a VSIM service contract provided by the selected service provider, which is the independent VSIM database of the selected service provider. Connect to. When the mobile device 101 is operating in an implementation system, such as the implementation system shown in FIG. 8, where a single VSIM SCP server 110 connects to multiple VSIM SCP databases 106-109 operated by independent service providers The internal memory 192 of the additional mobile device 101 need not store multiple server network addresses as in other embodiments. Rather, each time a user of mobile device 101 wishes to purchase a new VSIM service contract, it can simply connect to a single VSIM SCP server 110, so only one server VSIM SCP network address is stored in memory. Is remembered. For example, if the user is planning to travel internationally, prior to the trip, the user can log on to the VSIM SCP server 110 to purchase a PPSC for each country they are traveling to. If the VSIM SCP server 110 is hosted by the user's traditional service provider, additional VSIM service contracts may simply be charged to the user's long-term account.

  In the embodiment shown in FIG. 9, a communication link is established between the mobile device 101 and the VSIM SCP server 110 (step 240). After the mobile device 101 logs into the VSIM SCP server 110, the mobile device 101 downloads and displays a list of areas for the user to purchase a VSIM service contract account through the VSIM SCP server 110 (step 241). These regions can be described, for example, by region, country, or continent. The user may select the area that the user desires by using any of various user interface keys 12, 13 and switches incorporated within the mobile device 101. The user selection is transmitted to the VSIM SCP server 110 (step 242). Based on the user selection, the VSIM SCP server 110 downloads a list of possible VSIM service contract providers for the selected region to the mobile device 101 for display to the user (step 243). Using again any of the various user interface keys 12, 13 and switches incorporated within the mobile device 101, the user selects a VSIM service contract provider from the displayed list. The user's selection of the VSIM service contract provider is transmitted to the VSIM SCP server 110 (step 244).

  Based on the received selection, the VSIM SCP server 110 initiates a communication link with the VSIM SCP database (106-109) corresponding to the selected VSIM service contract provider (step 245). After logging into the appropriate VSIM SCP database (106-109), a list of VSIM service contract options is downloaded and sent to the mobile device 101 for display to the user (step 246). These VSIM service subscription options may give different combinations of voice plans, data plans, voice and data plans, and different access periods. Using any of the various user interface keys 12, 13 and switches incorporated within the mobile device 101, the user selects a VSIM service contract option from the displayed list. Alternatively, a VSIM service contract may be automatically selected by the mobile device processor 191 using a user specified profile to determine when to select which VSIM service contract. Via the VSIM SCP server 110, the VSIM service contract selection is transmitted to the selected VSIM SCP database (106 to 109), which is received by the VSIM SCP database (106 to 109) (step 247).

  Based on the sent selection, it downloads VSIM service contract provisioning data from the VSIM SCP database (106-109) to the VSIM SCP server 110, which sends the information to the mobile device 101, and the mobile device 101 Then, information is stored in the VSIM memory unit 193 (step 248). Finally, the VSIM service contract is activated and activated on the mobile device 101 (step 249). As part of the activation and activation step, a code identifying the mobile device 101 to be stored in the selected VSIM SCP database 106-109 along with other VSIM service contract account data is passed through the VSIM SCP server 110. Can be sent to the selected VSIM SCP database. Storing the identification code and account data allows the VSIM service contract provider to monitor individual VSIM service contract accounts and enable communications as long as the VSIM service contract is valid. As an alternative step (not shown), any of several well-known electronic payment and electronic commerce methods may be used to handle the exchange of funds prior to downloading provisioning data to mobile device 101. Can be implemented.

  In other embodiments, some service providers operate their own independent VSIM SCP servers 102-105 (see FIG. 1) and VSIM databases 106-109, while other service providers operate a central VSIM SCP server One may choose to run independent VSIM databases 106-109 connected to 110. In such embodiments, the system may include an independent VSIM SCP server and a central VSIM SCP server. In such embodiments, depending on which VSIM SCP server (independent or central) hosts the selected service provider's VSIM service contract, the process flow shown in both FIG. 3 and FIG. 8 may be implemented. .

  An alternative embodiment for providing both a VSIM service contract account as well as user personal VSIM data is shown in FIG. If the user does not have the user's personal mobile device 101 at hand, the user may rent or rent the mobile device 101a. In other examples, a user may purchase a disposable mobile phone. In either case, when the user does not have his own mobile device 101, the user may need access to personal data stored on the user's own mobile device 101 as well as the VSIM service contract account. In other examples, the user may have his own mobile device 101, but may have lost personal data from the internal memory 192 of the mobile device 101. This alternative implementation system and method allows a user to access a VSIM service contract account and download personal data that has been backed up to a remote VSIM storage unit 130/132. A more complete description of the remote VSIM storage unit 130/132 is described in US patent application Ser. No. 11 / 963,918 entitled “Virtual SIM card for Mobile Handsets,” the entire contents of which are incorporated herein by reference. . For simplicity, FIG. 10 and the description herein describe a mobile device 101a that has been rented, rented, or purchased. However, the user may also implement the implementation method and system using the user's personal mobile device 101.

  FIG. 10 illustrates one embodiment of a mobile handset 101a that is rented or purchased communicates with a VSIM server 130 over a cellular telephone network to send and receive both VSIM service contract provisioning data and backed up personal data. Shows the overall architecture. Mobile device 101a may be programmed with general provisioning data stored in internal memory unit 192 that allows mobile device 101a to communicate with VSIM server 130 over cellular telephone network 100a. VSIM server 130 may be coupled to authentication server 131, such as by wired, fiber optic or wireless network connection. VSIM server 130 may include an internal memory storage unit, such as a mass storage disk drive, or connected to a VSIM database 132 capable of storing personal data information for individual mobile handsets operating on the system. obtain. Similarly, the authentication server 131 includes an internal memory storage unit, such as a mass storage disk drive, or connected to an authentication database 133 that can store authentication credentials for individual VSIM accounts running on the system. it can. In one embodiment, the VSIM server 130 may also act as the authentication server 131 by incorporating authentication functionality into the VSIM server software and providing sufficient memory storage units.

  Since sensitive personal data, mobile device provisioning information, and authentication and verification information can be transmitted between the mobile handset 101a and the VSIM server 130, the VSIM server 130 and the mobile device processor 191 are not allowed to view Software can be configured to encrypt such information using known data encryption and key methods to protect the data from Information stored in the VSIM 193 is backed up and maintained on the external VSIM server 130.

  The VSIM service provided by the VSIM server 130 may be provided to mobile device users as a standard feature of the service or as a premium subscription fee service. This architecture allows provisioning and personal information to be uploaded to the VSIM memory unit 193 at any time, providing flexibility for new mobile device provisioning and programming. This architecture also provides the user with an external backup of personal data that retains the user's personal data, even if the entire mobile device 101 is lost. By logging on to the VSIM server 130 via the cellular telephone network, the user can back up his personal data to the VSIM server 130 and / or the VSIM database 132. Then, even if the entire mobile device 101 is lost or destroyed, the user's personal data is retained and is ready to be reloaded on the replacement mobile device.

  In order to restore retained user personal data, or to move those personal data to a rented or rented mobile device provisioned using a VSIM service contract, the user may use a cellular telephone network. To authenticate itself by sending an authentication certificate for comparison with an authentication certificate previously stored in the authentication database 133. Authenticated users can restore their personal data, and optionally provisioning information, to a rented or mobile device for replacement by downloading the information directly to the VSIM memory unit 193. Unauthenticated users are denied access to the VSIM database 132. In addition, the VSIM server 130 is connected to at least one VSIM SCP database (106, 107) to allow the user to purchase a VSIM service contract, thereby allowing the central VSIM described above with respect to FIG. Can act as a central VSIM SCP server similar to SCP server 110.

  FIG. 11 shows an overview of the process for purchasing a VSIM service contract and retrieving personal data stored in the VSIM server 130 and / or the VSIM database 132 to the mobile device 101a. In response to powering on the mobile device 101a or other interval preset by the user or service provider, the mobile device 101a establishes a wireless communication link to the VSIM server 130 via the cellular telephone network (step 250). . When the communication link is established, login to the VSIM server 130 is achieved (step 251). As part of the login process, the user is prompted to enter the user's account information via the mobile device 101a keyboard (step 252). The account name may be automatically received by the VSIM server 130, such as when the telephone number associated with the mobile device 101a is used as the user account name. It also prompts the user to enter authentication credentials (step 253). Any of several authentication credentials forms may be employed including password verification, biometric recognition, and combinations thereof. Once entered into the mobile device 101a, the authentication credentials are preferably encrypted by the mobile device 101a processor and sent to the VSIM server 130 via the cellular telephone network (step 254), which authenticates the data. The data is transmitted to the server 131 (step 255).

  The VSIM server 130 and / or the authentication server 131 decrypts the received user account and authentication certificate data (step 256). The processor of the VSIM server 130 or authentication server 131 accesses the stored authentication credentials associated with the user account (step 257). To authenticate the user and verify that the authorized user is attempting to log in, the decrypted received authentication credential is compared to the authentication credential previously stored in the authentication database 133 (decision 258). ). If the authentication credentials match (ie, decision 258 = yes), the user is authenticated and access to the user account file stored in the VSIM database 130 is permitted (step 259).

  If access is granted, the user uploads / backups personal data from the mobile device 101a VSIM to the VSIM database 132 via the VSIM server 130 or restores personal data to the mobile device 101a memory (step 260). During the backup procedure, personal data is transmitted from the VSIM memory unit 193 of the mobile device 101a to the VSIM database 132 via the VSIM server 130. During the restore operation, personal data is transmitted from the VSIM database 132 to the mobile device 101a and stored in its VSIM memory unit 193. The user may also perform other actions, such as changing personal data stored in the VSIM database 132. The data change procedure can be similar to the backup procedure. As long as access is granted to the user, personal data can flow from the VSIM memory unit 193 of the mobile device 101a to the VSIM database 132 via the VSIM server 130, and vice versa.

  When the user completes the desired personal data backup, restoration, and modification procedures (step 260), the mobile device 101a may obtain and use a VSIM service contract account to complete voice and data calls. The mobile device 101a implements the process flow shown in FIG. 9 to allow the mobile device 101 user to select and purchase a valid VSIM service contract account via the central VSIM server 130 (step 261). ). When the VSIM service contract provisioning data is downloaded, the mobile device 101a logs off from the VSIM server 130 (step 262).

  If the authentication credentials do not match when presented, the authentication server 131 denies access to the VSIM database 132 via the VSIM server 130. As shown in FIG. 11, a flag is set or a count is established to record the number of unsuccessful authentication attempts (step 263). If the number of unsuccessful authentication attempts exceeds a preset number (ie, decision 264 = yes), the VSIM server 130 logs off the user (step 262). Otherwise, if the number of unsuccessful authentication attempts is less than the preset number (ie, decision 264 = No), the user is prompted to attempt authentication again (step 253). In an alternative embodiment, the method may simply allow an unlimited number of authentication attempts, in which case there is no need to perform counter start step 263 or too many attempts are made as in decision 264. There is no need to decide whether or not.

  As explained above, as mobile device 101 moves within the coverage zone or moves from one geographic area to another to ensure quality of service (QOS), service providers PRLs can often be updated. Since different communication networks operate in different geographical areas, as the mobile device moves to different geographical areas, it was selected to ensure that the list of possible communication networks it can connect to is accurate It is important to renew the VSIM service contract PRL. Depending on the current location of the mobile device 101, the updated VSIM service contract PRL can re-prioritize the list of networks supported by the available VSIM service contract, or include other networks in the list Or the list can be modified to exclude it from the list.

  Each VSIM service contract service provider tries to maintain a high QOS for its customers, but in some cases, VSIM service contract service providers simply give their customers an appropriate in the geographical area to give a high QOS May not give access to secure communication networks. Thus, simply updating the PRL may not be sufficient to give the customer a high QOS (or service). For example, a service provider may operate in North America, but the service provider does not give its customers access to a communications network in Europe. In order to obtain a high QOS, the user may have to switch service providers completely. By maintaining multiple VSIM service contract accounts on the VSIM memory unit 193 of the mobile device, the user can copy the provisioning data of the selected new VSIM service contract account to a valid VSIM provisioning data buffer 314, etc. You can quickly activate a new VSIM service contract account. This swap-out of VSIM service contract account data activates a new VSIM service contract account PRL to allow the mobile device 101 to access a locally available communication network.

  The location may not be the only operational parameter value that suggests a change in the VSIM service contract account. It may be beneficial to change the VSIM service contract account when the mobile device is attempting various types of communication usage requests. For example, a particular VSIM service contract provider's communication network may be particularly suitable for handling high speed data calls. However, access to a particular VSIM service contract provider's communications network can be costly. Thus, utilizing a particular VSIM service contract provider's communication network for simple voice or data calls where high speed functionality is not required is not cost effective. In one implementation, when the mobile device 101 attempts to make a high-speed communication data call, such as for mobile TV or downloading a large multimedia data file, the mobile device 101 is supported by a VSIM that is supported by a particular service provider communication network. A service contract account may be activated. If the mobile device 101 is attempting to make a medium speed data call, such as for web browsing, a different VSIM service contract account may be enabled. In other cases where the mobile device 101 is attempting to make a low speed data call for MMS or the like, yet another VSIM service contract account may be enabled. Different VSIM service contract accounts may be selected to support different communication usage requests. Alternatively, different VSIM service contract accounts may be selected to support different provisioned services. For example, different VSIM service contract accounts may be used to support GSM only, GSM and GPRS, UMTS only, GSM, GPRS, UMTS, 1x only, 1x and EvDO. In order to support additional provisioned services, additional VSIM service contract accounts may be stored in the VSIM memory unit 193 of the mobile device 101. By storing various VSIM service contract account provisioning data in the VSIM memory unit 193, such switching between alternative VSIM service contract accounts can be quickly accomplished without having to communicate with the VSIM SCP server.

  In addition to location, communication usage request, or service request, a VSIM service contract account may be selected based on operating parameter values for time of day, day of week, and even annual time. Some service provider communication networks may receive increased call volume during certain times of the day, days of the week, and even during certain times of the year. Increased call volume can cause a reduction in QOS.

  Switching between VSIM service contracts stored in the VSIM memory unit 193 is more convenient than physically switching the SIM card on the mobile device, but always manually selecting which VSIM service contract should be valid What needs to be done can be cumbersome for some users. Various embodiments allow the mobile device 101 to automatically select a VSIM service contract based on a user profile.

  In various embodiments, the mobile device may be configured with software and user-specified profiles to automatically switch between VSIM service contracts when various user-specified criteria category values are met. If the criteria specified in the activated user profile are not met, the mobile device will not switch VSIM service contracts. Each user profile may specify which particular VSIM service contract is to be valid based on various user specified criteria category values. Alternatively, each user profile may specify a priority list of multiple VSIM service contracts to be enabled based on various user specified criteria category values. The priority list of multiple VSIM service contracts may be a hierarchy of possible VSIM service contracts to be enabled. A user may wish to enable a particular VSIM service contract for a given set of conditions, but in some situations, communication over a network that supports that particular VSIM service contract may not be possible . For example, a network that supports a particular VSIM service contract can be temporarily overloaded by call volume, or atmospheric or other interference can interfere with sufficient communication links with the network, or the network can be damaged. Is given. Instead of the user having to activate an entirely new user profile to select a different VSIM service contract, the user may specify multiple VSIM service contracts that are listed in the preference list. The priority order is an order in which the user designates the mobile device 101 to validate each described VSIM service contract. If the highest priority VSIM service contract in the list is not available, mobile device 101 will be able to connect mobile device 101 to a network that supports one of the listed VSIM service contracts, or The next highest priority VSIM service contract may be activated until the priority list is empty and there are no more networks available.

  By implementing user profiles, VSIM service contracts can be automatically selected and validated under a number of criteria category values based on user preferences. Various embodiments allow the user to customize both the reference category value and the priority list of possible VSIM service contracts to be enabled. In some cases, users have a specific purpose or reason to use a specific VSIM service contract to support communications calls based on intuition or other purposes that are not at all related to QOS or cost efficiency. Can do. For example, an enterprise may grant a VSIM service contract to its employees to make business voice calls and data calls. Provisioning information supporting this “enterprise” VSIM contract may be stored in the VSIM memory unit 193. A user may wish to make a personal call on the same mobile device 101, but does not want the cost of such a personal call to be recorded or charged for an enterprise VSIM service contract. Thus, the user may decide to purchase a separate VSIM service contract for personal use. Provisioning information that supports this “individual” VSIM service contract may also be stored in the VSIM memory unit 193. In one embodiment, the mobile device 101 then automatically selects and activates an “enterprise” VSIM service contract during business hours and automatically returns to an “individual” VSIM service contract during off hours. The employee can create a user profile. A network that supports a user's “personal” VSIM service contract may provide the user with a more cost-effective or better QOS solution for making voice or data calls, but under the user profile, during business hours An “enterprise” VSIM service contract is automatically selected and activated. In this user profile, the reference category is time, and the reference category value is “business hours” such as 8:00 am to 5:00 pm.

  In an alternative embodiment, the user may customize the user profile based on various criteria category values, not just time. Some of the most common criteria category values may allow the user to specify which VSIM service contracts should be activated based on location, time, and / or application. For example, a user may specify a user profile so that when a mobile device detects that the mobile device is at a specific location, a specific VSIM service contract is selected and activated. As another example, a user may specify a user profile so that a particular VSIM service contract is selected and activated when the mobile device is attempting to make a call related to a particular application. . For example, if a user attempts to send an email, the mobile device may recognize the email application and thus select and activate a particular VSIM service contract based on that application. Alternative embodiments may allow a user to create a user profile that specifies a particular VSIM service contract to be activated based on any combination of criteria values. For example, a user profile specifies a particular VSIM service contract that should be activated when the mobile device is at a specified location, for a specified period of time, and / or when a specified application is implemented. obtain.

  In another embodiment, the user may simply specify a priority list of VSIM service contracts without specifying a reference category value. In this embodiment, the user may simply prefer to select and activate one VSIM service contract over all other VSIM service contracts for all situations. However, by specifying a priority list, the user can define which VSIM service contracts should be valid if the network that supports the most preferred VSIM service contracts is not available. By ranking each VSIM service contract in the priority list, the mobile device is given an order of VSIM service contracts that the user wishes to utilize in an attempt to make a call to the mobile device.

  In still other embodiments, other additional criteria category values may be specified by the user. For example, the user may specify a particular VSIM service contract to be activated based on which telephone number, email address, or web address was entered. In this way, the user can ensure that calls to specific clients or contacts are charged for the appropriate VSIM service contract. For simplicity, the above describes an embodiment that includes time, location, and application criteria categories. However, the various embodiments should not be limited to these particular reference categories. It should also be noted that various embodiments do not require the use of all of these reference categories. The user can specify a profile without being based on a reference category, or can specify a profile based on one of the reference categories, or a combination of some or all of the reference categories. For example, a user may specify a particular VSIM service contract to use regardless of location, time, application, or other criteria. In this case, no criteria will be specified in the user profile.

  FIG. 12 is an exemplary menu tree 350 illustrating a possible cascade of menu options available to a user when the user attempts to create a new user profile or edit an existing user profile. The menu tree shown in FIG. 12 is not comprehensive. This is only an example and represents only a limited number of possible options available to the user when editing or creating a user profile.

As shown in FIG. 12, the user may be presented with an action selection (menu 351) in which the VSIM service contract stored in the VSIM memory unit 193 is switched. For example, the various VSIM service contracts stored in the VSIM memory unit 193 may automatically switch based on some general criteria such as cost efficiency or QOS or based on a selected user profile. By selecting a user profile option, the user may then be presented with a user profile selection option (menu 352). In the user profile selection menu 352, the user may be requested to select any one of a plurality of existing user profiles stored in memory or to create a new user profile. As shown in FIG. 12, a plurality of existing user profiles are stored in the memory in advance. Illustrative examples of user profiles include profiles named “Standard”, “Home”, “Office”, and “Travel”. After an existing profile (eg, “Office”) has been selected for editing (or a new profile name has been created), the user selects the criteria category to define the user profile The VSIM profile first reference category menu 353 is presented. As shown in the exemplary menu tree 350, possible criteria categories include “time”, “location”, and “application”. In addition, the user also selects the “Priority” option (menu 354) that allows the user to specify a priority list of possible VSIM service accounts to be enabled without specifying a baseline value. obtain. If no reference category value is specified, the mobile device may attempt to validate the VSIM service contract based solely on the priority list. Priority that allows the user to specify the order of VSIM service contracts that the mobile device should attempt to activate if the user selects the Priority option in the VSIM profile first criteria category menu 353 A list menu 354 is presented. In addition, if the "Priority" option is selected, other criteria category values other than the priority list itself are VSIMs to be enabled.
Not used to select a service contract.

  If the user selects the “Time” option in the VSIM profile first reference category menu 353, the user may be presented with a time reference option menu 355 that allows the user to specify various time reference values. For example, the user may specify a morning time zone (12:00 am to 9:00 am) as the time reference value. Alternatively, the user may specify any time range as the time reference value. Once the time reference value is entered, the user can be presented with the option to add other reference category values to the selected user profile or the order of VSIM service contracts that the mobile device should attempt to validate (i.e. Option to specify a priority list).

  If the user chooses to add other criteria category values to the selected user profile, the user may be presented with a VSIM profile second criteria category menu 358. Similar to the VSIM profile first criteria category menu 353, the VSIM profile second criteria category menu 358 presents the user with additional criteria categories that the user can specify to define the selected user profile. The VSIM profile second reference category menu 358 is described in more detail below.

  If the user chooses to specify a priority list order (as opposed to a single VSIM service contract), when the mobile device detects that the time reference has been met (until the network connection is made) ) The mobile device attempts to validate the various VSIM service contracts in the order listed in the priority list. For example, if the mobile device detects that the current time is within the range of 9:00 am to 5:00 pm (i.e., business hours), until the network connection is made and the call is completed, The mobile device attempts to connect to the network using the VSIM service contracts listed in “Priority List 2” in the order specified by the user.

  Under the VSIM profile first criteria menu 353, if the user selects the "Location" option (as opposed to the "Time" option), the user can specify various location criteria values A location criteria option menu 356 may be presented. Similar to the time base option menu 355, the user may specify various location values. For example, the user may specify “Area 1”, “Area 2”, and / or “Area 3”. Once the location criteria are entered, the user may be presented with an option to add additional criteria to the selected user profile or specify the order of VSIM service contracts that the mobile device should attempt to activate. You can be presented with options to specify. If the user chooses to add other criteria category values to the user profile, the user may be presented with a VSIM profile second criteria menu 358.

  In the example shown in FIG. 12, a “priority list” is designated for the “area” of each location. Thus, if the mobile detects that the current location is within one of the specified areas (i.e., area 1, area 2 or area 3), a network connection is made and the call is completed Until then, the mobile device attempts to connect to the network using the VSIM service contracts listed in the corresponding “priority list” in the order specified by the user.

  Under the VSIM profile first criteria menu 353, if the user selects the "Application" option (as opposed to the "Time" or "Location" option), the user specifies various application criteria values An application criteria option menu 357 may be presented that allows Similar to both the time criteria option menu 355 and the location criteria option menu 356, the user can specify various application values. For example, the user may specify “Internet” or “electronic mail”. Once the application criteria are entered, the user may be presented with the option to add additional criteria to the selected user profile or specify the order of VSIM service contracts that the mobile device should attempt to validate. You can be presented with options to specify. If the user chooses to add additional criteria values to the user profile, the user may be presented with a VSIM profile second criteria menu 358.

  As shown in FIG. 12, a “priority list” is designated for each application. Thus, if the mobile device detects that the current application is about to make a voice call or data call, the mobile device will make a corresponding “priority list” until a network connection is made and the call is completed. Attempt to connect to the network using the VSIM service contracts listed in the order specified by the user.

  If the user chooses to add other criteria category values to the user profile, the user may be presented with a VSIM profile second criteria menu 358. The VSIM profile second criteria category menu 358 presents the user with possible additional criteria categories for defining the selected user profile. As shown in the exemplary menu tree 350, the VSIM profile second criteria category menu 358 was accessed from the time criteria options menu 355 so that only “Location” and “Application” are displayed as other criteria categories possible. The Similar to the description above, if the user selects the “Location” option, the user may be presented with a location criteria option menu 359 that allows the user to specify various location criteria values. Alternatively, if the user selects the “Application” option, the user may be presented with an application criteria option menu 360 that allows the user to specify various application criteria values. Each of these respective criteria category option menus was selected not only to allow the user to specify criteria values, but also to specify the order of VSIM service contracts that the mobile device should attempt to activate The user is also presented with the option to add other criteria category values to the user profile or option.

  If the user chooses to specify the priority list order, when the mobile device detects that the time criteria and location or application criteria are met (until a network connection is made), the mobile device Attempts to activate the various VSIM service contracts in the order listed in the priority list. For example, if the mobile device detects that the current time is in the range of 12:00 am to 9:00 am (ie, the morning time zone) and the mobile device is in Region 2, then the network connection Until the call is completed, the mobile device attempts to connect to the network using the VSIM service contracts listed in “Priority List 8” in the order specified by the user.

  If the user chooses to add other criteria category values to the user profile, the user may be presented with a VSIM profile third criteria menu 361. The VSIM profile third criteria menu 361 presents the user with additional possible criteria for defining the selected or generated user profile. Since the VSIM profile third criteria category menu 361 was accessed from the time criteria option menu 355 and the location criteria option menu 359, as shown in the exemplary menu tree 350, “Application” is the only remaining possible criteria. Displayed as a category. Similar to the description above, when the user selects the “Application” option, the user may be presented with an application criteria option menu 362 that allows the user to specify various application criteria values. In addition to specifying application criteria, the user is presented with an option to specify the order of VSIM service contracts that the mobile device should attempt to validate.

  FIG. 13a shows a user profile data table 401 containing pointers to reference category values defining each user profile. Further, if the user profile criteria category value is satisfied, the user profile data table 401 includes a priority list index that indicates which priority list should be implemented. FIG. 13a shows only an exemplary user profile data table 401 and does not limit the present invention. When the user creates a new user profile, the new user profile name is entered in the “name” data field of the user profile data table 401. Multiple user profiles may be stored in the memory of the mobile device 101 as shown in FIG. 13a. For example, as shown in FIG. 13a, the user profiles included in the mobile device are “priority”, “home”, “work”, “travel”, “travel 2”, “email”, “Internet” It may include profiles named “Travel 3”, “Travel 4”, “Email 2”, “Mobile TV”, “Internet 2” and “Mobile TV 2”.

  Each user profile may be defined by any number of criteria categories. In the exemplary embodiment shown in FIG. 13a, an exemplary user profile may be defined by up to three criteria categories: time, location, and application. For example, an “Internet 2” user profile is defined by three criteria, as indicated by pointers stored in each of three criteria columns (data fields). Thus, when the “Internet 2” user profile is activated, the VSIM service contract is switched according to the priority list index 12 if all three criteria category values are met. Alternatively, other user profiles such as “home” may be defined only by “time” criteria. Thus, when the “Home” user profile is activated, only the “Time” criteria category value must be met before the VSIM service subscription switching operation can begin. In other cases, in both situations, a default VSIM service contract may be maintained to support communication. Yet another user profile may be defined by the absence of a reference value. For example, the absence of a reference value pointer is indicated for a “priority” user profile. Thus, when the “Priority” user profile is activated, VSIM service contracts are selected and activated according to the associated priority list, regardless of the baseline category value.

  When the user creates a new user profile, the profile name is stored in the “name” data field of the user profile data table 401 and a new user profile data record is generated in the user profile table. When the user chooses to edit an existing user profile, the desired user profile is selected and a user profile data record is retrieved. In any case, if the user chooses to define a selected user profile with a particular reference category value, the user may first be presented with an option for the reference category that defines the selected user profile. . Once a reference category is selected, the user may be presented with an option to define a selected reference category with previously stored reference values or enter an entirely new reference value. If the user chooses to define a selected user profile with a previously stored value for a particular reference category, the pointer for the previously stored value is appropriate for the selected user profile. It is input to the user profile data table 401 under the reference category. Referring to FIG. 13a, in the “home” user profile, the pointer C1 is stored in the “time” data field. Thus, the “home” user profile is defined by the time reference value stored under the C1 data field of the reference value table 402 shown in FIG. 13b. Similarly, in the “work” user profile, the pointer C 1 is stored in the “location” data field of the user profile data table 401. Thus, the “work” user profile is defined by the location reference value stored under the C1 data field of the reference value table 402.

  However, if the user chooses to enter an entirely new reference value, the new reference value is entered into a new data field in the reference value data table 402, and the pointer for the new reference value is for the selected user profile. Entered into the appropriate reference category.

  Further, in each user profile described in the user profile data table 401, the priority list index is indicated in the “priority index” data field. When the user specifies a particular order of VSIM service contracts that the mobile device 101 should attempt to validate, that order is stored in the priority index table 403, described in more detail with respect to FIG. 13c. An index corresponding to the designated ordered list is stored in the user profile data table 401. As with the baseline category value, the user may be presented with an option to specify a previously stored priority list for the currently selected user profile. If the user chooses to reuse the existing priority list, the priority list index corresponding to the ordered list is stored in the user profile data table 401 corresponding to the selected user profile.

FIG. 13b shows a reference value data table 402 that stores unique user-defined reference values for each of the reference categories that define the various user profiles. The reference category is described in the first data field belonging to the heading “reference”. As shown in FIG. 13b, possible criteria categories used in the exemplary criteria value data table include “time”, “location”, and “application”. Each of these reference categories occupies its own data record. Note that although the exemplary reference value table 402 shown in FIG. 13b shows only three reference categories, an unlimited number of reference categories may be specified to define various user profiles. Each new reference category simply occupies a new data record in the reference value data table 402. The reference value data table 402 may also store reference values designated for each reference category. For example, data field C1 of exemplary reference value data table 402 stores “8:00 am to 5:00 pm” in the “time” reference category and “North America” in the “location” reference category. In the “application” standard category, “voice” is stored. Each of these reference values may have no commonality with other reference values in the C1 data field, except that each was the first stored reference value for its respective reference category. is there. As explained above, when a user defines a selected user profile by adding various reference category values, the user can select a reference value for each reference category previously stored in the reference value table 402. Can be presented. If the user selects a pre-stored reference value, a pointer to that reference value (eg, C1, C2, C3, etc.) is placed in the corresponding data record for the selected user profile name in the user profile data table 401. Can be remembered. However, if the user chooses to specify a new reference category value, a new data field may be added to the reference value data table 402 to accommodate the new reference category value. If the user only wants to add a new reference value for one or some of the reference categories, the remaining reference categories in the new data field will be updated by the user with new reference values for the other reference categories. It can be left blank, such as when it is desired to add. In this way, the reference value data table 402 can grow continuously. As each new reference value is added to the reference value data table 402, a pointer to the corresponding data field is added to the appropriate reference category for the selected user profile in the user profile data table 401.

  FIG. 13c shows an exemplary priority index data table 403 that indexes various user-specified ordered lists of VSIM service contracts. For each priority list index, the various VSIM service contracts are arranged in the order in which the user wishes the mobile device to attempt to validate those VSIM service contracts under certain criteria conditions. As shown in FIG. 13c, not all VSIM service contracts stored in VSIM memory unit 193 may be included in a particular priority list. For example, referring to FIG. 13c, the priority list index 1 indicates that VSIM service account # 1 is listed first in the priority list. VSIM service account # 2 is listed second in the priority list. VSIM service account # 4 is listed third in the priority list. VSIM service accounts # 3 and 5-8 are not included in the priority list. Therefore, when the priority list index 1 is called, the mobile device 101 first tries to activate the VSIM service account # 1. If the connection to the communication network supporting VSIM service account # 1 is satisfactory, the call can be made or received using VSIM service account # 1. However, if the connection to the communication network that supports VSIM service account # 1 is unavailable for any reason, mobile device 101 attempts to validate VSIM service account # 2. This process may continue until a connection to a communication network that supports at least one of the VSIM service accounts in the priority list is satisfactory or the priority list is exhausted. Note that the example data tables shown in FIGS. 13a-13c and FIG. 16 only illustrate possible data structures that may be implemented to enable various embodiments. Those skilled in the art will appreciate that other data structures with equal effects can be implemented.

  FIG. 14 is a process flow diagram illustrating the steps performed in one embodiment when a user creates or edits a user profile. This embodiment may be implemented as part of the main loop routine 501 of the processor 191 of the mobile device 101. Main loop routine 501 may be used to control various applications and functions of mobile device 101. At any time during the execution of the main loop 501, the mobile device processor 191 receives a request from the user to create a new user profile or to edit an existing user profile (step 502). When a request to create or edit a user profile is received, the mobile device processor 191 displays a menu that queries whether the user wants to create a new user profile or edit an existing user profile. Present to the user (decision 503). If the user chooses to create a new user profile (ie, decision 503 = No), the mobile device processor 191 requests the user to enter a new user profile name (step 504). The input new user profile name is received and stored in the user profile data table 401 (see FIG. 13a) as a new data record (step 506). If the user chooses to edit an existing user profile (ie, decision 503 = yes), the user profile record is retrieved from the user profile data table 401 (step 505). If the user profile name is stored in the user profile data table 401 or the user profile record is retrieved, whether the mobile device processor 191 wants the user to add a reference category value to define the user profile A menu for querying is presented to the user (decision 507). If the user responds positively to the query (ie, decision 507 = yes), the user is requested to select a reference category (step 508).

  Once the reference category is selected, the user is then presented with an option to enter a new reference category value or to utilize a reference category value pre-stored in memory (decision 509). If the user chooses to enter a new reference category value (i.e., decision 509 = yes), the new reference category value is received from the user and entered into the reference value data table 402 (or the selected reference category as a new data field). If there is an empty cell for, store it in the empty cell (step 510). When the new reference category value is stored in the reference value data table 402, a pointer to the location of the reference category value stored in the reference value data table 402 is stored in the corresponding reference category data field of the user profile data table 401. (Step 512). A reference category value pointer that indicates the location of the reference category value stored in the reference value data table 402 if the user chooses to use an existing reference category value pre-stored in memory (ie, decision 509 = No) Is taken out (step 511). When the reference category value pointer is retrieved, the pointer to the location of the reference category value stored in the reference value table 402 is stored in the corresponding reference category data field of the user profile data table 401 (step 512).

  Once the reference value pointer is stored in the user profile data table 401, the user is presented with the option to add more reference categories to further define the selected user profile (decision 513). If the user chooses to add more criteria categories to further define the selected user profile (i.e., decision 513 = yes), step until no more criteria categories are added by the user 508 to 512 are repeated. If no more reference categories should be added (ie, decision 513 = No), the user is requested to specify the order of VSIM service contracts that the mobile device should attempt to validate (step 514).

Further, in decision 507, if the user chooses not to add or edit any user profile criteria category (i.e., decision 507 = No), the order of VSIM service contracts that the mobile device should attempt to activate is determined. The user is requested to specify (step 514). The user is presented with an option to implement a pre-stored priority list as a sequence of VSIM service contracts that the mobile device should attempt to validate (decision 515). If the user chooses to specify a new priority list (i.e., decision 515 = Yes), the mobile device receives the order of the VSIM service contracts that the user wishes to attempt to validate and receives the new priority list Stored as a rank list (step 517). This priority list is stored in the priority list index data table 403, and an index corresponding to the new priority list is allocated and stored in the priority list index data table 403. If the user chooses to implement a pre-specified priority list (ie, decision 515 = No), the index corresponding to the desired priority list is retrieved from the priority list index data table 403 (step 516). When a priority list index is retrieved (step 516) or a new index corresponding to a new priority list is assigned (step 517), the index corresponding to the priority list is replaced with data corresponding to the selected user profile. The record is stored in the user profile data table 401 (step 518). Once the priority list index is stored in the user profile data table 401, the user is presented with an option to activate the selected user profile (decision 519). If the user chooses to activate the selected user profile (ie, decision 519 = yes), set the selected user profile to active (step 520). This is accomplished by setting a flag in the user profile data table 401 (not shown) or by placing the active user profile name or data pointer to the activated user profile in a memory register. Can be done. When the user profile is activated, the mobile device processor returns to the main loop 501. However, if the user chooses not to activate the selected user profile (ie, decision 519 = No), the mobile device processor 191 simply returns to the main loop 501 without activating the user profile. .

FIG. 15 shows an implementation process flow for selection of a VSIM service contract from a plurality of VSIM service contracts stored in the VSIM memory unit 193 based on the activated user profile and various reference values. A mobile device processor 191 may execute a main loop 501 that controls and monitors some application activities and activities. During execution of the main loop 501, the processor 191 may periodically determine whether it is necessary to switch VSIM service contracts according to the user profile. In one implementation, the processor 191 determines whether the call is currently active (decision 550). If the call is currently active (ie, decision 550 = Yes), processor 191 returns to main loop 501. By returning to the main loop, the implementation method ensures that no active calls are dropped while the VSIM service contract is switched. If there is no currently active call (ie, decision 550 = No), the processor 191 may continue to determine whether the VSIM service contract should be switched according to the user profile. The processor 191 must first determine which user profile is currently active (step 552). This can be accomplished by ascertaining which user profile in the user profile data table 401 has a flag set, or by retrieving the user profile name or pointer from the data register. Once the active user profile name is determined, the user profile data table 401 is examined to determine whether the activated user profile has at least one reference category value that defines the user profile (decision 554). ). If the activated user profile has at least one reference category value that defines the user profile (i.e., decision 554 = yes), the processor 191 refers to the user profile data table 401 to activate the activated user A reference category defining the profile is determined (step 556). To determine the reference category that defines the activated user profile, the processor 191 determines whether a pointer is stored in each of the reference category data fields of the user profile data table 401. If the pointer is stored in a particular reference category column, that reference category is used to determine the appropriate priority list to implement. Once processor 191 determines the reference categories used in the activated user profile (step 556), processor 191 determines the current reference values for each of those reference categories (step 558). These current reference values can be temporarily stored in a memory buffer.

  Based on the reference value pointer stored in the user profile data table 401, the processor 191 stores the reference value data table 402 for comparison with the determined current value for each reference category stored in the memory buffer. Take the reference value. If all of the current reference values meet the relevant reference values stored in the reference value data table 402 (i.e., decision 560 = Yes), the processor 191 can perform a user profile data table 401 for the activated user profile. Is used to retrieve a priority list from the priority list index table 403 (step 562). If any of the current reference values cannot satisfy any of the related reference values stored in the reference value data table 402 (ie, decision 560 = No), the processor 191 returns to the main loop 501.

  Further, after determining the active user profile and the reference category that can define the active user profile in step 552, if it is determined that the reference category pointer is not stored in the active user profile (i.e., decision 554 = No), The processor 191 also uses the priority list index stored in the user profile data table 401 for the activated user profile for which the reference category pointer is not stored in the data record, and uses the priority list index table 403. The priority list is extracted from (step 562).

  Using the priority list index stored in the user profile data table 401, when the priority list of the VSIM service contract is retrieved from the priority list index data table 403, the processor 191 of the mobile device 101 has the highest priority. It is determined whether a communication network that supports the VSIM service contract is available to the mobile device 101 (step 564 and decision 566). If a communication network that supports the highest priority VSIM service contract is not available to the mobile device 101 (i.e., decision 566 = No), the processor 191 of the mobile device 101 determines whether there is any available communication network. Is determined (decision 574). Mobile device 101 may be in a geographical area where pilot signals may not be received from any communication network, such as when mobile device 101 is underground. If the mobile device 101 has not received a pilot signal from any communication network (i.e., decision 574 = No), the user is notified of the situation (step 576) and the processor 191 of the mobile device 101 returns to the main loop ( Step 501). If the processor 191 of the mobile device 101 determines that another communication network is available (i.e., decision 574 = yes), the VSIM service contract supported by the unavailable communication network is excluded from consideration (step 578). ), The availability of the next highest priority VSIM service contract is again checked (step 564). In this way, in step 564, the VSIM service contract that is unavailable (or the VSIM service for which the support communication network is not available) is determined until the highest priority VSIM service contract for which the support communication network is available is determined. Contract) is excluded from consideration.

  If a communication network that supports the highest priority VSIM service contract is available to mobile device 101 (i.e., decision 566 = Yes), mobile device processor 191 determines that the highest priority available VSIM service contract is VSIM memory. Determine if it is currently active on unit 193 (decision 568). If the currently active VSIM service contract account is the same as the highest priority available VSIM service contract (i.e., decision 568 = yes), then the active VSIM service is in accordance with steps 221-232 described above with respect to FIG. A communication call is established using the contract account (step 572).

  If the highest priority available VSIM service contract account is not currently active (i.e., decision 568 = No), the mobile device processor 191 accesses the mobile device VSIM memory unit 193 and is stored in the VSIM memory unit 193. The highest priority available VSIM service contract account is selected and activated by copying the highest priority available VSIM service contract account provisioning data to a valid VSIM provisioning data buffer 314 (step 570). Once the highest priority available VSIM service contract account provisioning data has been validated in the VSIM provisioning data buffer 314, the mobile device 101 establishes a call according to steps 221-232 described above with respect to FIG. 6 (step 572). ). Alternatively, the mobile device processor 191 selects and activates the highest priority VSIM service contract by retrieving the highest priority VSIM service contract account provisioning data from the location in the VSIM memory unit 193 via a pointer. (Step 570). When the call is connected or terminated according to the process flow described above with respect to FIG. 6, the mobile device processor 191 returns to the main loop (step 501).

  In alternative embodiments, mobile device 101 may support a finite number of user profiles depending on the number of possible reference categories and reference category value options made available to the user. As the number of reference categories increases and the granularity of the reference category value option increases, a larger finite number of user profiles can be presented to the user for selection. For example, time value options may be given in months, weeks, days, groups of hours, individual hours, minutes, etc. Location value options may be given in continents, countries, regions, cell towers, etc. Each of the user profiles can be defined by the same reference category, but is distinguished by a different reference value for each reference category. Prior to user designation, each of the finite user profiles implements a default VSIM service contract or priority list when its criteria are met. Thus, prior to user customization, for all possible situations, the mobile device 101 activates the default VSIM service contract or priority list. When the user desires to customize the user profile, the user is prompted to select a reference value option for each reference category. Then, optionally, the user can name a particular combination of criteria category values. The user can then customize a particular VSIM service contract or priority list associated with a particular combination of criteria values. In this way, VSIM service contracts can be switched according to a user-customized priority list when a particular combination of reference category values is met.

FIG. 16 shows an exemplary user profile data table 405 for use in an alternative embodiment. As shown in FIG. 16, in an exemplary alternative embodiment, a finite user profile is defined by three criteria categories: time, location, and application. Those skilled in the art will appreciate that a user profile can be defined by more than three criteria categories. The use of the three criteria categories, time, location, and application is for illustration only. These reference categories are shown as data field headings in the user profile data table 405. There can be a limited number of reference value options for each reference category. For example, the user may be presented with three reference value options for the time category. These three time value options are: morning (12:00 am-8:00 am), business (8:00 am-5:00 pm), and evening (5:00 pm-12 am) Hour 00 minutes). Similarly, the user may be presented with three reference value options for the location category. These three location value options may include North America, Europe, and Asia. Similarly, the user can be presented with three reference value options for the application category. These three application value options may include voice, text, and internet. Given these reference value options, the user can generate 27 possible combinations to define 27 possible user profiles. FIG. 16 shows 27 possible user profile combinations. Thus, 27 possible combinations are presented to the user that allow the user to specify the priority list order of VSIM service contracts that the mobile device will attempt to enable to support communications. Those skilled in the art will appreciate that fewer or more reference categories and reference values may be implemented. Although the 27 possible combinations may seem limited on the surface, many users will appreciate that only a few possible combinations of reference category values require customization. For most possible combinations, the user will find that the default priority list is sufficient. Thus, the user may only choose to customize a limited number of possible combinations.

  In the example shown in FIG. 16, some of the possible criteria category value combinations indicate that the default priority list is associated with a particular combination. Other combinations have a priority list index associated with those particular combinations of criteria category values indicating that the user has customized the combination. Furthermore, certain combinations of reference category values have user-customized names associated with those combinations. For example, the user has customized the combination of time = business, location = North America, and application = voice with the index “1” and associated with the priority list renamed to “work voice”. There is. The alternative user profile data table 405 can be utilized by the mobile device processor 191 with a priority list index data table 403 similar to that shown in FIG. 13c to determine when a VSIM service contract should be automatically replaced. .

  FIG. 17 is a process flow diagram illustrating the steps of customizing a combination of user profiles according to the alternative embodiment described above with respect to FIG. As with the embodiments described above, alternative embodiments may be implemented as part of the main loop routine 501 of the mobile device processor 191. Main loop routine 501 may be used to control various applications and functions of mobile device 101. At any time during the execution of the main loop 501, the mobile device processor 191 receives a request from the user to create a new user profile or to edit an existing user profile (step 502). When a request to create or edit a user profile is received, the mobile device processor 191 displays a menu that queries whether the user wants to create a new user profile or edit an existing user profile. Present to the user (decision 503). If the user chooses to create a new user profile (i.e., decision 503 = No), the mobile device processor 191 determines one possible time reference value option (step 580), location reference value option (step 582), And presents the user with a menu requesting the user to select an application baseline option (step 584). Those skilled in the art will appreciate that the order of these steps is arbitrary. Further, additional steps can be inserted or deleted if the user profile is defined by fewer or more criteria categories. Once all the reference category value options are selected, the mobile device processor 191 identifies which of the reference value combinations has been selected (step 586). The user may also optionally be presented with a request to name a specified reference value combination. The input name is stored in the user profile data table 405 (step 588).

  Alternatively, if the user chooses to edit an existing user profile combination, the user may be presented with a menu that selects a particular reference value combination by name. In other cases, the user may simply select the desired reference value option that constitutes the named combination through steps 580-586. Once a new / edited reference value combination is selected and identified, the mobile device processor 191 attempts to enable the mobile device to support the call when a particular reference value combination is met. A menu is presented to the user requesting the user to enter the order of VSIM service contracts desired by the user (step 514). The alternative embodiment then implements steps 515-518 as described above to enter the user specified priority list into the priority list index data table 403 and the priority list index into the user profile data table 405. And memorize. Once the priority list and priority list index are properly stored in the appropriate data table, the mobile device processor 191 can return to the main loop 501.

FIG. 18 is a process flow of steps implemented by an alternative implementation method for switching VSIM service contracts according to a customized user profile. Similar to the process flow diagram shown in FIG. 15 and described above, the alternative embodiment begins by executing a main loop 501 that controls and monitors the activities and activities of several applications. During execution of the main loop 501, the processor 191 may periodically determine whether it is necessary to switch VSIM service contracts according to the user profile. The processor 191 determines whether the call is currently active (decision 550). If the call is currently active (ie, decision 550 = Yes), processor 191 returns to main loop 501. By returning to the main loop, the implementation method ensures that no active calls are dropped while the VSIM service contract is switched. If no call is currently active (ie, decision 550 = No), the processor 191 determines the current value of each of the reference categories (step 558). Once the current reference category value is determined, the user profile associated with the user profile satisfied by the current reference category value is identified in the user profile data table 405 (step 592). Once a user profile is identified, the priority list index associated with that user profile may be retrieved from the user profile data table 405. In an example where the user has not specified a user profile priority list, a default priority list is implemented. In the example where the user specifies the priority list of the user profile, the priority list index allows the mobile device processor 191 to retrieve the user-specified priority list from the priority list index data table 403 (step 564). ). Once the appropriate priority list is retrieved, the mobile device processor implements steps 566-578 as described above with respect to the process flow diagram shown in FIG. 15 and is appropriate to support communication over the wireless network. A simple VSIM service contract. In this way, one of the plurality of VSIM service contracts stored in the VSIM memory unit 193 may be selected to support communication according to user preferences. When the situation changes (e.g., the mobile device moves to a new location, the time changes, and / or the user wants to start a new application), the user supports communication calls according to the user's preferences To specify which VSIM service contracts are implemented.

  The above embodiments have been described as being executed by a mobile device processor. The above embodiments may alternatively be executed by a remote server processor, in which case the user profile data table, the reference category data table, and the priority list index data table are stored in the remote server memory. Those skilled in the art will appreciate. The current reference category values are determined by the mobile device 101 and for comparison against various values in the remotely stored user profile data table, reference category data table, and priority list index data table, Can be sent to a remote server. Once a determination is made regarding which priority list to implement, such a determination may be sent to the mobile device 101 for implementation.

  The above method descriptions and process flow diagrams are provided by way of illustration only and do not require or imply that the steps of the various embodiments must be performed in the order presented. . As those skilled in the art will appreciate, the order of the steps in the above embodiments may be performed in any order.

  The hardware used to implement the above embodiments, as will be appreciated by those skilled in the art, is a microprocessor unit, microcomputer unit, programmable floating point gate array (FPGA), and application specific integrated circuit (ASIC). Processing elements and memory elements configured to execute a set of instructions for performing method steps corresponding to the method described above. Alternatively, some steps or methods may be performed by circuitry that is specific to a given function.

  Those skilled in the art will appreciate that the various exemplary logic blocks, modules, circuits, and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or a combination of both. Will be understood. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Those skilled in the art may implement the described functionality in a variety of ways for each particular application, but such implementation decisions should not be construed as departing from the scope of the present invention.

  The method or algorithm steps described with respect to the embodiments disclosed herein may be implemented directly in hardware, implemented in software modules executed by a processor, or a combination of the two. The software modules can reside in processor readable storage media and / or processor readable memory, both of which are RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD- It can be either a ROM or any other tangible form of data storage medium known in the art. Moreover, the processor readable memory may include two or more memory chips, memory within the processor chip, separate memory chips, and combinations of various types of memory such as flash memory and RAM memory. References to the memory of a mobile handset herein are meant to encompass any one or all memory modules in the mobile handset, not limited to a particular configuration, type or packaging. An exemplary storage medium is coupled to the processor such that the processor in either the mobile handset or the theme server can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium can reside in an ASIC.

  The above description of various embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. obtain. Accordingly, the present invention is not limited to the embodiments shown herein, but instead, the claims have the broadest scope consistent with the principles and novel features disclosed herein. Should be given.

11 User interface display
12 User interface keys
12 Rocker switch
13 Keypad
13 User interface keys
18 Speaker
19 Microphone
100 communication network
100a cellular telephone network
101 mobile devices
101 personal mobile devices
101a mobile handset
101a mobile devices
102 VSIM service contract provisioning (SCP) server
102 VSIM SCP server
103 VSIM service contract provisioning (SCP) server
103 VSIM SCP server
104 VSIM service contract provisioning (SCP) server
104 VSIM SCP server
105 VSIM Service Contract Provisioning (SCP) server
105 VSIM SCP server
106 VSIM SCP Database
107 VSIM SCP Database
108 VSIM SCP Database
109 VSIM SCP Database
110 VSIM SCP server
110 Central VSIM SCP server
120 base station
121 servers
122 cellular telephone network
125 mobile devices
126 Server hosting data
127 Computing devices
128 Second base station
129 landline
130 VSIM server
130 Remote VSIM storage unit
131 Authentication server
132 VSIM database
132 Remote VSIM storage unit
133 Authentication Database
151 System table
152 Collection table
191 processor
191 Mobile Device Processor
192 Internal memory
192 Internal memory unit
193 VSIM
193 VSIM memory
193 VSIM memory unit
194 Antenna
195 transceiver
199 Vocoder
300 Mobile Device Hardware / Software Architecture
301 hardware interface
301 Hardware interface layer
302 drivers
302 Driver layer
303 Physical layer
304 operating system
305 API layer
306 Application
310 VSIM hardware / software architecture
311 VSIM hardware interface layer
311 Access layer
312 Access layer
312 Driver layer
313 Access layer
313 Physical layer
314 VSIM service contract provisioning data
314 VSIM provisioning data buffer
314 VSIM memory
314 Active memory buffer
315 VSIM Service Contract Account Provisioning Data Set
315 VSIM provisioning data
315 VSIM memory
350 Menu tree
350 Example Menu Tree
351 Menu
352 Menu
352 User profile selection menu
353 VSIM Profile 1st Standard Category Menu
353 VSIM profile first reference menu
354 Priority list menu
355 Time Reference Option Menu
356 Location criteria option menu
357 Application criteria option menu
358 VSIM Profile Second Standard Category Menu
358 VSIM profile second reference menu
359 Location criteria option menu
360 application criteria option menu
361 VSIM Profile Third Reference Menu
362 Application Criteria Option Menu
401 User profile data table
402 Reference data table
402 Base value table
403 priority index data table
403 Priority list index data table
403 Priority list index table
403 priority index table
405 User profile data table

Claims (23)

A method for supporting wireless communication calls on a mobile device having a VSIM internal memory unit storing provisioning data for multiple service contracts, comprising:
Storing a plurality of user profiles and a plurality of priority lists of service contracts, each of the plurality of user profiles being used in supporting the wireless communication call. Specifying a criterion for selecting one of the priority lists, storing;
Collecting a plurality of reference category values from the mobile device;
Comparing the plurality of collected criteria category values to the criteria specified in a selected one of the plurality of user profiles;
Retrieving one of the plurality of priority lists of service contracts associated with the selected one of the plurality of user profiles for which stored criteria are satisfied by the collected criteria category value;
Retrieving provisioning data corresponding to a highest priority service contract among a plurality of service contracts described in the retrieved one of the plurality of priority lists of service contracts;
Attempting to establish a communication link to a communication network using the retrieved provisioning data.   The method of claim 1, wherein the collected plurality of reference category values includes time, mobile device location, and application.   The application according to claim 2, wherein the application corresponds to the type of wireless communication call being initiated and includes one application type selected from the group consisting of voice call, SMS text, email, internet browsing, and mobile TV. The method described. Determining whether a communication network supporting the highest priority service contract is available to the mobile device;
Excluding the communication network from consideration if the communication network supporting the highest priority service contract is unavailable to the mobile device;
2. The method of claim 1, further comprising retrieving provisioning data from the VSIM internal memory unit corresponding to a next highest priority service contract that appears in the order of the plurality of service contracts. Determining whether a wireless communication call on the mobile device is currently active;
Establishing a communication link to a communication network using the retrieved provisioning data corresponding to the highest priority service contract only if a wireless communication call on the mobile device is not currently active. The method of claim 1. Means for storing provisioning data for multiple service contracts;
Means for storing a plurality of user profiles and a plurality of priority lists of service contracts, wherein each of the plurality of user profiles is a plurality of priority of service contracts for use in supporting a wireless call; Means for storing, specifying criteria for selecting one of the lists;
Means for collecting multiple reference category values;
Means for comparing the plurality of collected criteria category values with the criteria specified in a selected one of the plurality of user profiles;
Means for retrieving one of the plurality of priority lists of service contracts associated with the selected one of the plurality of user profiles whose stored criteria are satisfied by the collected criteria category value When,
Means for retrieving provisioning data corresponding to a highest priority service contract among a plurality of service contracts described in the retrieved one of the plurality of priority lists of service contracts;
Means for attempting to establish a communication link to a communication network using the retrieved provisioning data.   The mobile device of claim 6, wherein the collected plurality of reference category values includes time, mobile device location, and application.   8. The mobile device of claim 7, wherein the application corresponds to a type of initiated wireless communication call selected from the group consisting of voice call, SMS text, email, internet browsing, and mobile TV. Means for determining whether a communication network supporting the highest priority service contract is available to the mobile device;
Means for excluding the communication network from consideration if the communication network supporting the highest priority service contract is unavailable to the mobile device;
7. The mobile device of claim 6, further comprising means for retrieving provisioning data corresponding to a next highest priority service contract that appears in the order of the plurality of service contracts from the VSIM internal memory unit. Means for determining whether a wireless communication call on the mobile device is currently active;
7. The mobile device of claim 6, further comprising means for establishing a communication link to a communication network using the retrieved provisioning data only if a wireless communication call on the mobile device is not currently active. . A memory storing a plurality of user profiles, each of the plurality of user profiles specifying a criterion for selecting one of a plurality of priority lists of service contracts stored in the memory ; A service contract of each of the plurality of priority lists ,
A processor coupled to the memory;
A communication interface circuit coupled to the processor, the communication interface circuit configured to connect the processor to a communication network;
The processor is
Receiving a plurality of collected reference category values from a mobile device;
Comparing the plurality of collected criteria category values to criteria specified in a selected one of the plurality of user profiles;
Retrieving the priority list of service contracts associated with a met criteria specified in the selected one of the plurality of user profiles;
Transmitting the retrieved priority list index to the mobile device via the communication interface circuit, the server comprising software instructions for performing steps including:   12. The server of claim 11, wherein the received collected plurality of reference category values includes time, mobile device location, and application.   13. The server of claim 12, wherein the application corresponds to a wireless communication call type selected from the group consisting of voice call, SMS text, email, internet browsing, and mobile TV. A processor;
An internal memory unit coupled to the processor, the internal memory unit comprising:
Including VSIM provisioning data buffer,
Provisioning data for multiple service contracts in a VSIM memory unit;
Multiple user profiles,
Remembers multiple priority lists of service contracts and
Each of the plurality of user profiles specifies a criterion for selecting one of the plurality of priority lists of the service contract for use in supporting a wireless call;
The processor is
Collecting a plurality of current baseline category values;
Comparing the plurality of collected criteria category values to criteria specified in a selected one of the plurality of user profiles;
Retrieving one of the plurality of priority lists of service contracts associated with a selected one of the plurality of user profiles in which a specified criterion is met by the collected current criterion category value When,
Retrieving provisioning data from the VSIM memory unit corresponding to a highest priority service contract among a plurality of service contracts appearing in the retrieved priority list of service contracts;
Attempting to establish a communication link to a communication network using the retrieved provisioning data. The mobile device comprising software instructions for performing steps comprising:   15. The mobile device of claim 14, wherein the collected plurality of reference category values includes time, mobile device location, and application.   16. The mobile device of claim 15, wherein the application corresponds to a wireless communication call type selected from the group consisting of voice call, SMS text, email, internet browsing, and mobile TV. The processor further comprises:
Determining whether a communication network supporting the highest priority service contract is available to the mobile device;
Excluding the communication network from consideration if the communication network supporting the highest priority service contract is unavailable to the mobile device;
15.Provided with software instructions that perform the steps further comprising: retrieving provisioning data from the VSIM internal memory unit corresponding to a next highest priority service contract that appears in the order of the plurality of service contracts. The mobile device described in. The processor further comprises:
Determining whether a wireless communication call on the mobile device is currently active;
And comprising software instructions for performing the steps further comprising establishing a communication link to a communication network using the retrieved provisioning data only if a wireless communication call on the mobile device is not currently active. 15. A mobile device according to claim 14. Collecting a plurality of reference category values from a mobile device;
Comparing the plurality of collected criteria category values to criteria specified in a user profile;
Retrieving a priority list of service contracts identified in the user profile if the collected category criteria value meets the criteria specified in the user profile;
Retrieving provisioning data from the VSIM internal memory unit corresponding to the highest priority service contract among a plurality of service contracts appearing in the priority list of service contracts;
A storage medium storing processor-executable software instructions configured to cause a processor to execute steps including attempting to establish a communication link to a communication network using the retrieved provisioning data.   20. The storage medium of claim 19, wherein the collected plurality of criteria category values includes time, mobile device location, and application.   21. The storage medium of claim 20, wherein the application corresponds to a type of wireless communication call selected from the group consisting of voice call, SMS text, email, internet browsing, and mobile TV. Determining whether a communication network supporting the highest priority service contract is available to the mobile device;
Excluding the communication network from consideration if the communication network supporting the highest priority service contract is unavailable to the mobile device;
Processor-executable configured to cause the processor to perform further steps including retrieving provisioning data from the VSIM internal memory unit corresponding to a next highest priority service contract appearing in the order of the plurality of service contracts 20. A storage medium according to claim 19, comprising software instructions. Determining whether a wireless communication call on the mobile device is currently active;
Only when a wireless communication call on the mobile device is not currently active, the processor is configured to perform further steps including using the retrieved provisioning data to establish a communication link to a communication network. The storage medium of claim 19, comprising processor executable software instructions.