JP2013500690A - Notify mobile device users of call attempts in disabled virtual SIM contracts - Google Patents

Abstract

  A system and method for notifying a user about a call made to a mobile device via a currently deactivated VSIM contract and identifying the currently activated VSIM contract on the mobile device and Sending a notification to the mobile device via the VSIM contract and notifying the user about the received call attempt. In one embodiment, the user can switch between activated VSIM contracts to receive incoming calls. Establish communication between the caller and the mobile device because the user can be notified to the caller's service provider network when switching the activated VSIM contract to the one corresponding to the dialed number be able to.

Description

  This application is a U.S. patent application Ser. No. 11 / 963,918 filed Dec. 24, 2007, “” Virtual SIM card for Mobile Handsets ”, which is incorporated herein by reference, U.S. Patent Application No. 12 / 020,028 `` Biometric Smart Card for Mobile Devices '' filed on January 25, 2008, U.S. Patent Application No. 12 / filed on June 8, 2009 480,319 `` Virtual SIM card for Mobile Devices '', U.S. Patent Application No. 12 / 480,406, filed June 8, 2009, `` Method and Apparatus for Switching Virtual SIM Service Contracts Based Upon a User Profile (Method and Apparatus for Switching Virtual SIM Service Contract Based on User Profile), '' U.S. Patent Application No. 12 / 480,453, filed June 8, 2009, `` Method and Apparatus for Updating the Rules Governing the Switching of a Virtual SIM Service C ontract (method and apparatus for updating rules governing switching of virtual SIM service contracts) '' and U.S. Patent Application No. 12 / 480,490, filed June 8, 2009, `` Method and Apparatus for Switching Virtual SIM Service Contracts when '' Roaming (method and device for switching virtual SIM service contracts when roaming) ".

  The present invention relates generally to mobile phone technology, and more specifically to notify a user that a call is being attempted to the user's mobile device through a currently disabled service provider agreement. The present invention relates to a system and method.

  Currently, portable handsets, for example, depending on the carrier selected, such as GSM (Global System for Mobile Communications), CDMA (Code Division Multiple Access), and / or UMTS (Universal Mobile Telecommunication System) technology, etc. Utilizes various technologies and formats. The network provisioning data required to access cellular networks using GSM® and UMTS technology is stored in a subscriber identity module (SIM), commonly known as a SIM card, Is plugged into a mobile device. Similar devices have been developed in other mobile communication network systems, such as a removable user identification information module (RUIM), a universal subscriber identification module (USIM), or a universal integrated circuit card (UICC). These smart card devices are often collectively referred to as smart cards or SIM cards.

  The SIM card is a removable memory module that contains the user's mobile phone supply information or contract information and personal data such as a phone book, stored SMS messages, downloaded data. By storing such information on a SIM card, mobile device users maintain the same service provider contract and preserve personal data information by simply removing the SIM card from the old device and plugging it into the new device , Mobile devices can be replaced.

  Discloses communications to monitor calls attempted to mobile devices through currently disabled VSIM contracts (that is, service provider contracts that are not currently loaded into the mobile device's active VSIM memory buffer) Systems, communication system components, and methods. In various embodiments, provisioning data that supports multiple VSIM contracts may be included in the mobile device's internal storage. Supply data for each of the plurality of service providers can be selectively acquired by the mobile device and loaded for use. Once supply data for a VSIM contract is acquired and loaded into the mobile device's active VSIM memory buffer for use, the VSIM contract is activated on the mobile device. For mobile devices that can only support one VSIM contract at a time, other service provider contracts whose supply data is stored in internal storage will be invalidated (including previously activated VSIM contracts) ). Conventionally, a call made to a deactivated contract cannot arrive at the mobile device, and the user of the mobile device is unaware of the failed call attempt. This shortcoming is overcome by the user registering a disabled VSIM contract in a supervised mode maintained by a remote server. The user can designate the VSIM contract to the monitor mode state by transmitting a status report of each of the plurality of VSIM contracts to the remote server. This status report now shows which of multiple VSIM contracts are active (i.e. loaded into active VSIM memory buffer), which of multiple VSIM contracts are invalid, and multiple disabled VSIMs Information about which of the contracts should be in the monitoring mode can be included.

  According to one embodiment, the caller has a unique identifier (e.g., assigned to a particular service provider contract) associated with at least one of a plurality of VSIM contracts whose supply data is stored in the internal storage of the called mobile device. Phone number) can be used to attempt a call to the mobile device. If the unique identifier used by the caller is associated with a currently invalidated VSIM contract, the remote server in the communications network will access the VSIM account and get status reports from each of the multiple VSIM contracts can do. Using the captured status report, the remote server will now have a unique identifier associated with the currently activated VSIM contract, along with which of the multiple VSIM contracts are activated on the called mobile device Can be determined. The remote server can generate and transmit a notification to the called mobile device using a unique identifier associated with the currently activated VSIM contract. The notification includes the unique identifier of the calling communication device, the unique identifier of the currently disabled VSIM contract from which the call attempt was made, the time at which the call attempt was made, and the type of call attempt being made (i.e. Enough information to inform the mobile device user of the call attempt, such as voice call, SMS, EMS, MMS, paging, etc.).

  In other embodiments, the notification may be presented to the user in the form of a prompt asking whether the user wants to activate the VSIM contract for which the call attempt was made. If the user chooses to switch the currently active VSIM contract, the incoming call can be connected to the user's mobile device and completed once the VSIM contract change has taken effect.

  The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the present invention and, together with the above general description and the following detailed description, It serves to explain the characteristics.

1 is a communication system diagram illustrating an implementation system that allows a mobile device to communicate with multiple virtual SIM (VSIM) service provider contracts. FIG. FIG. 5 is a process flow diagram of an implementation method for providing a notification to a user's mobile device that a call attempt has been made to a currently disabled VSIM service provider contract. FIG. 6 is a process flow diagram of another implementation method for providing a notification to a user's mobile device that a call attempt has been made to a currently disabled VSIM service provider contract. FIG. 5 is a process flow diagram of an implementation method for switching a currently enabled VSIM service provider contract and communicating the status of the VSIM service provider contract to a remote VSIM server. FIG. 5 is a process flow diagram of an implementation method for processing a call attempt to a user's mobile device by a calling gateway server. FIG. 4 is a process flow diagram of an implementation method for processing a call attempt to a user's mobile device by a VSIM server. How to provide notification to a user's mobile device that a call attempt has been received for a currently disabled VSIM service provider contract and allow the user to switch over the currently enabled VSIM service provider contract It is a process flow chart. How to provide notification to a user's mobile device that a call attempt has been received for a currently disabled VSIM service provider contract and allow the user to switch over the currently enabled VSIM service provider contract It is a process flow chart. Of an implementation method for handling call attempts to the user's mobile device by the calling gateway server when the user chooses to switch the currently activated VSIM service provider contract to complete the call attempt. It is a process flowchart. In a process flow diagram of an implementation method for processing a call attempt to a user's mobile device by a VSIM server when the user chooses to switch the currently activated VSIM service provider contract to complete the call attempt is there. FIG. 6 is a block diagram of components of a mobile device suitable for use with various embodiments. FIG. 3 is a block diagram of exemplary server components suitable for use in various embodiments.

  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 to specific 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 terms mobile device and communication device refer to mobile phones, personal digital assistants (PDAs), palmtop computers, laptop computers, wireless email receivers (e.g., Blackberry® and Devices such as Treo®), multimedia internet enabled mobile phones, and any one or all of similar personal electronic devices including programmable processors and memory. The communication device can further include static devices such as landline telephones and desktop computers. In a preferred embodiment, the mobile device and the communication device are each a cellular handset that can communicate over a mobile phone network (eg, a mobile 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” refers to a network server, particularly a server accessible over the Internet and / or an intranet, typically a server processor, such as a processor, memory (eg, hard disk memory), and the Internet or cellular network. Including a network interface circuit configured to connect to the network.

  As used herein, the term “VSIM subscription” or “VSIM subscriptions” refers to mobile services or contracts, or any provisioning information that can be maintained by a VSIM server and / or VSIM server database. Points to an account from a VSIM service provider. Multiple or multiple VSIM contracts can refer to multiple VSIM contracts from one or more VSIM service providers whose supply information can be maintained by a VSIM server and / or a VSIM server database.

  In order to support communication over a wireless cellular network, a mobile device needs to own service provider supply data. With the provisioned data, the mobile device can recognize and be recognized by the service provider's communication network device (eg, base station, server, etc.). Once recognized, the mobile device is allowed to make and receive calls (ie, voice, data, SMS, EMS, MMS, etc.) through the service provider's communication network. Note that when attempting a call, the caller and receiver may be supported by different service provider networks or the same service provider network. The reference to the service provider network may be either the same service provider network, the calling service provider network, or the receiving service provider network.

  In some locations, multiple service providers may operate a communication network to support communication. Each service provider can present different advantages and disadvantages associated with their services. For example, one service provider can provide higher data transfer rates than all other service providers at a higher cost, while other service providers have better coverage across geographic regions. And as a result, the range over which calls can be made and received may increase. Such a wide effective range can also be associated with higher costs. In order to benefit from the advantages of different cellular networks, some users may choose to maintain contracts with multiple service providers. By doing so, users can choose to use one VSIM contract compared to others and support mobile device communications that are suitable for their communication needs at a particular time. In addition, the user can choose to maintain multiple contracts with the same service provider. For example, for accurate settlement purposes, a user may choose to maintain a contract with a specific service provider for business calls and maintain another contract with the same service provider for personal calls. it can. When the user makes either call (ie, business or personal), the user can choose to activate the appropriate contract. Each of the contracts can be processed independently, as if each of the contracts are supported by different service providers.

  Traditionally, a user can maintain multiple VSIM contracts by obtaining and using interchangeable SIM cards, each containing supply data that supports communication over a particular service provider's communication network. By physically removing one SIM card from the user's mobile device and inserting another SIM card, the user can deactivate one VSIM contract and activate another VSIM contract. For example, when the user is outside the network of a particular service provider, the user can plug in a SIM card that contains provisioning data that supports communication in a communication network operating at the new location. Movement is not the only motivation for switching SIM cards. For example, a user desires to use a certain service provider's communication network for data calls because a higher data transfer rate is provided, but a voice call is provided because a voice service is provided at a lower price. May wish to use a communication network of a different service provider. Users want to use one VSIM contract for business calls and another VSIM contract for personal calls in order to maintain accurate settlement even when services and prices are the same There is.

  There are many drawbacks to the traditional method of switching physical SIM cards to change service contracts. Among them, users must physically carry multiple SIM cards and replace them to switch communication networks. This may be a tedious process. In addition, if a SIM card is lost or stolen, another user inserts the SIM card into the mobile device and begins making fraudulent calls using the VSIM contract associated with the lost / stolen SIM card be able to.

  To provide greater flexibility and efficiency to mobile device users, users can maintain multiple VSIM contracts, keep all supply data in memory, and activate virtual SIM (VSIM) cards Virtual SIM cards that can implement each VSIM contract have been proposed. As previously done, instead of switching physical SIM cards, the mobile device loads the selected service provider network supply data into the transceiver's working memory (i.e. the active memory buffer) There is no need to always grasp and carry a physical SIM card. Not only is it convenient, but there is no physical SIM card that can be used to make fraudulent calls, which can make a VSIM contract more secure. For a method, system, and apparatus for implementing a VSIM card, see US patent application Ser. No. 11 / 963,918 filed on Dec. 24, 2007, “” Virtual SIM card for Mobile, incorporated herein by reference. `` Handsets (Virtual SIM cards for portable handsets) '', U.S. Patent Application No. 12 / 020,028, `` Biometric Smart Card for Mobile Devices, '' filed January 25, 2008, June 2009 U.S. Patent Application No. 12 / 480,319 filed on May 8, `` Virtual SIM card for Mobile Devices '', U.S. Patent Application No. 12 / 480,406 filed June 8, 2009, `` Method and Apparatus for Switching Virtual SIM Service Contracts Based Upon a User Profile, U.S. Patent Application No. 12 / 480,453, filed June 8, 2009, "Method and Appa ratus for Updating the Rules Governing the Switching of a Virtual SIM Service Contract, and U.S. patent application filed June 8, 2009. 12 / 480,490, “Method and Apparatus for Switching Virtual SIM Service Contracts when Roaming”, collectively referred to as previous VSIM patent applications.

  Typically, each VSIM contract has an associated unique identifier, such as a phone number. The user can notify others of the unique identifier so that the caller can contact the user's mobile device through a VSIM contract. A mobile device user with multiple VSIM contracts can have multiple different unique identifiers (eg, phone numbers) even if multiple VSIM contracts are supported by the same service provider. Thus, when the user's mobile device has activated a different VSIM contract, others can attempt to call the user by dialing one unique identifier.

  In both conventional SIM card service provider contracts and VSIM contracts, only one service provider contract can be activated on the mobile device at a time. Thus, when one VSIM contract is activated, all other VSIM contracts are invalidated. As a result, calls made to a disabled VSIM contract (ie, dialed to a unique identifier associated with the disabled contract) cannot connect to the mobile device. The user is not notified of the call attempt because the call attempt is performed on the deactivated contract. This situation is therefore different from the call waiting signal that can be received when a call is made to a contract that is activated while the user is connected to a different call. As a result, if a call attempt is made to the user's mobile device via the currently disabled VSIM contract, the user may miss an important call or message. Some traditional mobile devices can provide the ability to support more than one SIM card (e.g. two SIM slots), so users can call on a single device through two or more active contracts And can receive calls. A mobile device with VSIM functionality can be intended to allow a user to activate more than one VSIM contract at a time. In such a situation, the mobile device can be said to have multiple contract slots. Each contract slot can simultaneously activate a different service provider contract (traditional SIM or VSIM) on the mobile device. However, users may maintain more VSIM contracts that the mobile device can activate at the same time. For simplicity, embodiments are described herein as operating on a mobile device that can support a single service provider contract at a time. Those skilled in the art will appreciate that the embodiments disclosed herein can be implemented by mobile devices that maintain more service provider contracts that can be activated simultaneously. Call attempt notification to one of the currently disabled VSIM contracts can be made to the user via any or all of the currently enabled VSIM contracts.

  These drawbacks are the monitoring of call attempts made on currently invalidated VSIM contracts and messages sent to mobile devices via the currently activated VSIM contracts, in which users attempt such attempts. Addressed by various embodiments that utilize the VSIM contract function to notify For simplicity, various embodiments can be described in terms of mobile devices that can activate a single VSIM subscription at a time. It will be appreciated by those skilled in the art that the embodiments disclosed herein can be implemented on a device that can enable more than one VSIM contract at a time to monitor calls received with a currently disabled VSIM contract. Will be self-explanatory. In one embodiment, the mobile device communicates with a remote VSIM server and the VSIM server not only determines which VSIM subscription is activated on the mobile device, but which of those activated subscriptions are currently activated. You can also be notified. A VSIM contract can be considered activated when a user purchases the contract and downloads the supply data that supports the contract into memory. A VSIM contract can be considered activated when a user loads supply data that supports the contract into an active memory buffer. As disclosed in the VSIM patent application, the VSIM server can maintain a VSIM account for each mobile device that provides services. Alternatively, the VSIM server can maintain a database of all activated VSIM contracts associated with the mobile device on which the VSIM contract is activated. In various embodiments, a VSIM account can include a data record that includes information about which VSIM subscriptions are activated on the mobile device, and personal user data. Various embodiments further store and update information regarding the status of the VSIM subscription currently enabled on the mobile device. This status information includes an indicator of currently activated VSIM contracts, an indicator of currently deactivated VSIM contracts, and an indicator of currently deactivated VSIM contracts that are to be put into monitoring mode be able to. Since the information about the currently activated VSIM contract is sufficient to indicate the deactivated contract, it is optional to include an indicator of the currently deactivated VSIM contract in the status information . Using this feature, mobile device users can notify the VSIM server of disabled VSIM contracts that they wish to monitor for incoming calls. This status information identifying currently active VSIM contracts and monitored contracts can be periodically transmitted to the VSIM server by the mobile device in the form of a status report. The VSIM server can receive such status reports and use them to update VSIM contract status information for the reporting mobile device.

  When a caller attempts a call to a user's mobile device, the call attempt may not be connected for various reasons (ie, no communication link is established). One reason is that the VSIM contract associated with the unique identifier used to attempt the call is currently invalidated on the user's mobile device. To determine whether this is the case, a data call communication can be sent to the VSIM server from the calling telephone network or from the intended recipient's service provider network. This data call communication may include information regarding the call attempt including a unique identifier (eg, a telephone number) that has been dialed. The VSIM server can receive and retrieve the data call and use the unique identifier to find and obtain a VSIM account that includes the unique identifier. The acquired VSIM account includes a VSIM contract associated with the unique identifier, information about the VSIM contract currently active on the mobile device that also contracts the VSIM contract associated with the unique identifier, and a unique identifier associated with the currently active VSIM contract. Information about can be included. The acquired VSIM account may also include VSIM contract status information and information regarding all other VSIM contracts associated with the mobile device. Using the information contained in the acquired VSIM account, the VSIM server can identify the VSIM contract currently activated on the mobile device. In addition, the VSIM server may determine whether the user associated with the acquired VSIM account has chosen to be notified when a call attempt is made on a VSIM service contract where the incoming call attempt is made. Yes (that is, whether the called VSIM contract is in supervised mode). When a VSIM contract with incoming call attempts is in supervised mode, the VSIM server uses the unique identifier associated with the VSIM contract currently active on the mobile device to generate a notification and send it to the user can do. Such notification notifies the user about the call attempt, such as the VSIM contract where the call was attempted or attempted, other information such as the unique identifier of the calling communication device, and the time the call attempt was made. It can contain enough information. Such notifications that can be communicated using a variety of different message formats (i.e., SMS, EMS, MMS, push messages, etc.) allow users to return a call immediately or to call the associated number in the future You can switch to a dialed VSIM subscription so that users can receive calls.

  In one embodiment, notifications can be transmitted immediately while the call attempt is put into a busy waiting loop, where the user accepts the call from the currently activated VSIM contract. As an option, you can be given the option to switch to a VSIM subscription with incoming call attempts. In this embodiment, the user is notified of the call attempt and is switched to the appropriate VSIM contract so that the call can be completed and there is no need to return the call. The "busy wait loop" state can be used while the network is trying to find / page the mobile number. A “busy wait loop” condition may indicate to the caller that the network is attempting to complete the call.

  FIG. 1 is a communication system diagram illustrating an implementation system 1000 that allows a user's mobile device to validate multiple virtual SIM (VSIM) contracts. In FIG. 1, a variety of different communication devices 1010, 1011, 1012, 1013 can contact a user's mobile device 1050. As shown, the initiating communication device communicates with a communication network 1070, for example, through a wired connection to a wireless communication device 1010, gateway (not shown) that communicates via a base station 1025, or a wireless connection. A server 1013 may be included that uses a wired connection to a laptop computer 1011, a landline communication device 1012, or a gateway (not shown) to a communication network 1070 that communicates with the base station 1025. The communication network 1070 can include a number of communication devices including, but not limited to, servers that can be used to receive and route calls to and from communication devices operating on the network. For simplicity, the descriptions of the various embodiments herein refer to the wireless communication device 1010 as the calling communication device. Those skilled in the art will appreciate that any of a number of communication devices can be used to initiate a call attempt.

  When the user activates the selected VSIM contract on the mobile device 1050, the mobile device 1050 registers with the communication network and device (eg, 1071 and 1045) of the selected service provider. In this example, the user has a VSIM contract with each of the three communication networks 1070, 1071, and 1072 shown, and depending on which VSIM contract is currently active, the associated base station 1025, 1045, and Any one of 1065 can be used for communication. For example, mobile device 1050 is shown as currently registered with communication network 1071 and base station 1045. Also shown are possible connections to communication networks 1070 and 1072 (and corresponding base stations 1025 and 1065). When a call is made to the user's mobile device 1050, the caller enters a unique identifier associated with the VSIM contract previously activated by the mobile device 1050. If the entered unique identifier is associated with a VSIM contract that is currently activated on mobile device 1050, then the calling service provider network 1070 is the currently activated service provider communication network 1071 and the user's mobile The call can be routed to the base station 1045 with which the device 1050 is currently communicating.

  However, if the unique identifier entered is related to a VSIM contract that is currently disabled on mobile device 1050 (i.e. not a currently enabled VSIM contract), then mobile device 1050 is related to a unique identifier. The calling service provider network 1070 cannot route the call because it is not registered with the service provider's communication network (eg, 1070 or 1072). Similarly, if the user maintains multiple VSIM contracts with the same service provider, the mobile device 1050 uses the supply information identified by the unique identifier that the caller is using for call attempts, Calling service provider network 1070 cannot route the call because it is not registered with the provider's communication network. In various embodiments, if the call attempt is not connected, the calling service provider network 1070 can transmit the data communication call to the VSIM server 1030. This data communication call indicates that the call attempt is being made to a unique identifier (for example, the telephone number assigned to the mobile device in a particular VSIM contract) entered from the caller's communication device 1010. Can be notified. The VSIM server 1030 uses the received unique identifier to access the VSIM database 1035 to obtain a VSIM account associated with or containing the dialed number. Using information obtained from the VSIM database 1035, the VSIM server 1030 can generate and transmit notifications to the user's mobile device 1050 via the communication network 1071 and the base station 1045 to which the mobile device is currently registered. Can do.

  The VSIM server 1030 can also communicate with a communication network (eg, 1072) associated with the invalidated VSIM contract. Thus, when a user switches between VSIM subscriptions, the communication network associated with the newly activated VSIM subscription (eg, 1070 or 1072) can initiate communication with the mobile device 1050.

  FIG. 2 is a process flow diagram of an implementation method for providing a notification to a user's mobile device that a call attempt has been made to a currently invalidated VSIM contract. When the caller initiates a call (e.g., voice, data, SMS, MMS, etc.) to the user's mobile device 1050, the caller is uniquely associated with the VSIM contract (referred to as the desired VSIM contract) at the caller's communication device 1010. Is entered (step 101). The call request is received by the calling service provider network 1070 (step 201). Upon receipt, the calling service provider network 1070 can attempt to route the call to the user's mobile device 1050 via the service provider network associated with the entered unique identifier (step 202).

  When a caller attempts a call request to the user's mobile device 1050 using a unique identifier associated with the VSIM contract currently enabled on the user's mobile device 1050, the call request is sent to the caller's communication network 1070. Received by. The routers and servers in the calling communication network 1070 utilize the entered unique identifier to communicate with the entered unique identifier and support communication for the currently activated VSIM contract ( For example, look up 1071). For simplicity, the entered unique identifier and the communication network associated with the currently activated VSIM contract can be referred to as the user's communication network. Although FIG. 1 depicts the user's communication network (eg, 1071) as a different communication network than the calling communication network 1070, it should be noted that these may be the same network. Once the user's communication network (ie, communication network 1071) is identified, the calling network 1070 establishes a communication session with the user's communication network and the location of the mobile device 1050 or at least the mobile device 1050 is registered. A base station (eg, 1045) is determined. Once this location is determined, a communication link between the calling communication device 1010 and the user's mobile device 1050 can be established.

  When the mobile device 1050 validates a particular VSIM contract, the mobile device 1050 registers itself with a device that supports the communication network (ie, the user's communication network 1071) and the communication network (eg, base station 1045). By doing so, the user's communication network 1071 becomes aware of the presence of the mobile device 1050. As a result, when the caller enters a unique identifier associated with the user's communication network (ie, communication network 1071), the caller's communication network 1070 uses the information about the call request to the mobile device 1050 to communicate with the user. Can contact the network. The user's communication network finds the mobile device 1050 (i.e., obtains the base station 1045 to which the mobile device 1050 is registered via the home location register database), and establishes a connection between the calling communication device 1010 and the mobile device 1050. Establish a communication link between them. Once this link is established, calls between devices can be initiated.

  However, when the user invalidates a particular VSIM contract, the supply data that allows the mobile device 1050 to communicate and register with the user's communication network is deleted from the active VSIM memory buffer of the mobile device 1050. For example, assume that a user invalidates a VSIM contract that supports communication on the communication network 1072 and activates a VSIM contract that supports communication on the communication network 1071. In this case, the communication network 1071 becomes the user's main communication network. Without the supply data that supports communication over the communication network 1072, the mobile device 1050 cannot register itself with devices associated with the communication network 1072. As a result, calls made using a unique identifier associated with a user's contract that supports calls on the communication network 1072 are not connected to the mobile device 1050. Similar results occur when the user's mobile device 1050 is powered off, away from the user's communications network (i.e., 1072) area, or in the case of a traditional mobile device, a physical SIM / This is when the RUIM card is removed from the mobile device.

  Thus, when a caller attempts a call request to a user's mobile device 1050 using a unique identifier associated with a VSIM contract that is currently disabled on the user's mobile device 1050, the call request is It is received again by the communication network 1070. The routers and servers in the calling communication network 1070 utilize the entered unique identifier to support communication to the currently invalidated VSIM contract associated with the entered unique identifier. Look up. For simplicity, the entered unique identifier and the communication network 1072 associated with the currently invalidated VSIM contract can be referred to as the user's second communication network. Note that although FIG. 1 depicts the user's second communication network (eg, 1072) as a different communication network than the calling communication network 1070, these may be the same network. Once the user's second communication network (i.e., communication network 1072) is identified, the calling network 1070 establishes a communication session with the user's second communication network and the location of the mobile device 1050 or at least the mobile device A base station (for example, 1065) that can register 1050 is determined. The mobile device 1050 is not found by the user's second communication network 1072 because the mobile device 1050 currently invalidates the VSIM contract associated with the user's second communication network 1072. As a result, a communication link between the calling communication device 1010 and the user's mobile device 1050 is not established.

  As described above with respect to FIGS. 1 and 2, if the entered unique identifier relates to a VSIM contract currently enabled on mobile device 1050 (e.g., communication network 1071), the call is routed through the calling communication network 1070. Routed to the communication network 1071 and the mobile device 1050 (step 402). Upon reception, the servers operating in the communication networks 1070 and 1071 establish a communication link between the calling communication device 1010 and the user's mobile device 1050 (step 405). Once the communication link is established, a call can be made (step 550).

  After attempting to connect the call (step 202), the communication network 1070 that supports the calling service provider contract can wait for a period of time to determine whether the call is properly connected (decision 205). ). If the call is properly connected (ie, decision 205 = yes), the call is simply allowed to continue (ie, step 550).

  However, if the unique identifier entered is associated with a currently invalidated VSIM contract, the call is not connected. Thus, if the calling service provider network 1070 determines that the call was not connected (i.e., decision 205 = No), the calling service provider network 1070 prepares a data communication call message and sends it to the VSIM server 1030. The transmitted unique identifier (ie, the desired MIN) can be indicated (step 210). The data communication call may further indicate a unique identifier of the calling communication device 1010. The VSIM server 1030 may find and obtain a VSIM account that includes the unique identifier using the unique identifier included in the data call communication as a lookup value (step 310). From the result of this database lookup, the VSIM server 1030 can determine whether the unique identifier is associated with the VSIM contract (decision 315). For example, if a database lookup does not return a VSIM account, this may indicate that the unique identifier is not associated with a VSIM contract, such as when the unique identifier is associated with a traditional service provider contract. is there. Thus, once the VSIM server 1030 determines that the entered unique identifier is not associated with a VSIM contract (i.e., determination 315 = No), such a result can be transmitted to the calling communications network 1070, and The calling communication network 1070 can end the call attempt (step 215).

  However, if the VSIM server 1030 determines that the entered unique identifier is associated with a VSIM contract (i.e., decision 315 = Yes), the VSIM server 1030 will place the VSIM contract associated with the unique identifier into monitor mode. Can be determined (decision 320).

  The acquired VSIM account includes the mobile device associated with the VSIM contract, which of the multiple VSIM contracts are activated on the mobile device, which of the multiple user's VSIM contracts are disabled, and multiple disabled Information about which of the VSIM contracts that are enabled are in monitoring mode.

  If the user chooses to activate one VSIM contract, the user can optionally put the deactivated VSIM contract into a monitored mode. By putting a disabled VSIM contract into monitor mode, the user generates a notification when a call attempt is made to the VSIM server via a monitored (disabled) VSIM contract, Instruct that it should be transmitted to the user via the currently activated VSIM contract.

  The user sends a message (e.g. an updated status report) to the VSIM server to put the disabled VSIM contract into the monitored mode state or is deactivated from the monitored mode state at any time. You can get rid of VSIM contracts. For example, if the user does not want to be disturbed, the user can choose to remove all disabled VSIM subscriptions from the monitor mode state. As a result, the user will not receive a notification if a call is attempted to a disabled VSIM contract. Alternatively, if the user expects a call through a particular VSIM contract, the user can put that particular VSIM contract into monitor mode. As a result, the user can be notified when a call is attempted through a specific VSIM contract, even if the specific VSIM contract is currently disabled. In one embodiment, unless otherwise indicated by the user, each time a VSIM contract is invalidated, the contract can be automatically put into a monitoring mode. In this way, a notification can be generated and sent each time a call attempt is received for a disabled VSIM contract.

  The VSIM server 1030 obtains a VSIM account containing the desired VSIM contract and accesses the status of the various VSIM contracts included in the VSIM account to access the desired identifier associated with the received data call communication unique identifier. It can be determined whether the VSIM contract has been put into monitor mode by the user (decision 320). If the desired VSIM contract is not in monitor mode (i.e., decision 320 = No), the VSIM server 1030 may send an indication to the calling communications network 1070 that the desired VSIM contract is not available. Yes (step 220). Upon receiving this instruction, the calling communication network 1070 can end the call attempt (step 215).

  If the incoming call is for a unique identifier corresponding to a VSIM contract that is determined to be in monitor mode (i.e., decision 320 = yes), the VSIM server 1030 determines from the obtained VSIM account information that the user's mobile device A VSIM contract currently activated at 1050 can be determined (step 325). The VSIM server 1030 can then generate a notification message and transmit the notification message over the currently enabled service provider communication network 1071 (step 330). The currently enabled service provider communication network 1071 can relay the notification message to the user's mobile device 1050 (step 430). The notification message can be received by the user's mobile device 1050 (step 530). The notification message includes the dialed number or the desired VSIM contract for which the call attempt was made, the unique identifier of the calling communication device 1010, and, if necessary, the call attempt if there is a delay in the transmission of the notification message. Information such as time of day or type of call attempted (ie voice call, SMS / EMS / MMS, paging, etc.). The notification message can be generated and transmitted by various protocols. For example, the notification may be generated as an SMS message, a multimedia message service (MMS) message, an electronic message service (EMS) message, an email, or other similar message service. Upon receipt, the user can contact the caller using information contained in the notification using, for example, a currently activated VSIM contract. If the user deactivates all VSIM contracts without activating the VSIM contract, the VSIM server 1030 cannot determine the currently activated VSIM contract on the user's mobile device 1050 from the retrieved VSIM account information There may be cases (step 325). In such a case, the VSIM server 1030 can send an indication to the calling communication network 1070 that the desired VSIM contract is not available. Upon receiving this instruction, the calling communication network 1070 can end the call attempt (step 215).

  If necessary, when the VSIM server 1030 generates and transmits a notification message, a notification or other message can also be transmitted to the calling communication device 1010. This can be accomplished to provide an indication to the caller that a notification has been sent to the user. This message can be transmitted to the caller service provider network 1070 (step 330) and relayed back to the caller communication device 1010 (step 230). This message can be received by the caller communication device 1010 (step 130). Upon receipt, the caller can choose to terminate the call attempt.

  FIG. 3 is a process flow diagram of another implementation method for providing a notification to a user's mobile device that a call attempt has been made to a currently invalidated VSIM contract. Another implementation process flow shown in FIG. 3 is similar to the process flow shown in FIG. However, in another embodiment, when a caller attempts to contact a user via a disabled VSIM contract, to notify the user of a call attempt via the currently disabled VSIM contract The user's communication network 1071, which supports the disabled VSIM contract, can initiate a data communication call to the VSIM server 1030. In some cases, the calling communication network 1070 may not be able to recognize or contact the VSIM server 1030 because it is not aware of the VSIM subscription service. Since the user's various communication networks can obtain the supply information through the VSIM server 1030, the user's communication network can recognize and contact the VSIM server 1030.

  As described above with respect to FIG. 2, the caller initiates a call attempt to the user using the unique identifier associated with the currently invalidated VSIM contract (step 101). The call request is received by the calling network 1070 (step 201) and connected to a communication network 1071 that supports the VSIM contract associated with the unique identifier (steps 202, 402, and 405). In another embodiment shown in FIG. 3, unlike the calling communication network 1070, the user's second communication network 1071 that supports the VSIM contract associated with the unique identifier determines whether the call can be connected. (Decision 450). Similar to decision 205 described above with respect to FIG. 2, if the call is properly connected (ie, decision 450 = yes), the call is simply allowed to continue (ie, step 550).

  However, if the unique identifier entered is associated with a currently invalidated VSIM contract, the call is not connected. Thus, if the user's second service provider network 1071 determines that the call was not connected (i.e., decision 450 = No), the user's service provider network 1071 receives the unique identifier entered (i.e., the desired MIN ) Can be prepared and transmitted to the VSIM server 1030 indicating (step 455).

  Unlike the process flow diagram shown in FIG. 2, in another embodiment where the user's second communications network initiates a data communications call, determining whether the unique identifier is associated with the VSIM contract shown in FIG. That is, decision 315) can be omitted. For example, since each of the user's communication networks necessarily provides a VSIM contract, any of the user's communication networks can verify that the entered unique identifier is associated with the VSIM contract. Each of the user's communication networks can support both traditional contracts as well as VSIM contracts. A unique identifier is associated with a VSIM contract to distinguish between calls made to legacy contracts (that is, those supported by SIM cards and not in monitor mode) and calls made to VSIM contracts. The user's communication network can assign a unique identifier (MIN) within a particular area. In this way, the user's communication network can quickly determine whether the call is made to a VSIM contract. Thus, upon receiving a data communication call from any of the user's communication networks, the VSIM server 1030 obtains the appropriate VSIM account associated with the unique identifier (step 310) and the same method as described above with respect to FIG. Thus, it can continue to determine whether the desired VSIM contract is in monitor mode (decision 320).

  In one embodiment, the user can activate the VSIM contract associated with the entered unique identifier after the initial call attempt is made (step 202). Due to the delay problem, the VSIM contract associated with the entered unique identifier can be validated and a status report indicating this update can be reported to the VSIM server 1030 while data call communication is being attempted. In such cases, the VSIM server 1030 determines from the obtained VSIM account information that the VSIM contract currently activated on the user's mobile device 1050 now matches the desired VSIM contract. Can do. When obtaining VSIM account information, if the VSIM server 1030 determines that the currently active VSIM contract matches the desired VSIM contract, the VSIM server 1030 communicates with the caller to try the call again. The network 1070 can be directed (step 202). For simplicity, various embodiments use a caller's communication network that initiates contact with a VSIM server when a call to a user's communication device is attempted via a disabled VSIM contract. Can be described. Those skilled in the art will appreciate that communication with the VSIM server 1030 can be initiated by either the caller's communication network or the user's communication network.

  In embodiments where each VSIM contract is automatically put into monitor mode when the VSIM contract is deactivated (i.e. the user cannot exit or deactivate monitor mode), whether the VSIM contract is in monitor mode The step of determining (ie, step 320) can be omitted. In another such embodiment, once a VSIM account is acquired, the currently activated VSIM contract can be identified and a notification can be automatically sent by the VSIM server (steps 325 and 330).

  FIG. 4 is a process flow diagram of an implementation method for switching the currently activated VSIM contract and communicating the status of the VSIM contract to the remote VSIM server. If the user chooses to activate a different VSIM contract on the mobile device 1050, the mobile device 1050 processor will prompt the user to switch the currently activated VSIM contract, for example in the form of selecting a menu option. It can be received (step 501). The request to switch VSIM contracts can be initiated by the user. Requests can also be generated by the mobile device itself, such as in the case of intelligent applications that automatically switch VSIM contracts to enable the most cost-effective contracts that provide the highest quality service in place. The request can also be generated by a VSIM server. In response, the mobile device 1050 processor can process an instruction to delete the currently enabled VSIM subscription provisioning data from the active VSIM memory buffer and invalidate the VSIM (step 502). Deleting the supply data from the active VSIM memory buffer removes the SIM card from the mobile device because the wireless transceiver cannot transmit a mobile device identifier that allows it to connect to the disabled service provider's network Similar to that. Thus, in the example shown in FIG. 1, when the user chooses to delete the supply data associated with the communication network 1071 (i.e. the currently activated VSIM contract) from the VSIM memory buffer, the mobile device 1050 I make a call from 1071 and I can't receive it.

  Prior to deletion, the processor of the mobile device 1050 further transmits a notification to the currently enabled VSIM contract communication network 1071 as necessary, and the mobile device 1050 disables the link to the network 1071. Can be notified to the network (step 503). This notification can be received as needed by the communication network 1071 that can perform an action to smoothly terminate the communication link between the mobile device 1050 and the communication network 1071 (step 403). For example, when a mobile device is notified to invalidate a VSIM contract that supports communication on the communication network 1071, the home location registry responsible for maintaining which base station the mobile device 1050 is registered with (see figure (Not shown) can positively indicate a disabled state. Therefore, when the call source communication network 1070 establishes a communication session with the communication network 1071, it is possible to immediately receive notification about the user's contract status.

  As described in more detail below, the user may be provided with a choice to put the disabled VSIM subscription into monitor mode. By placing a deactivated contract in monitor mode, a notification can be provided to the user that a call attempt is being made to the deactivated VSIM contract. To trigger the process of sending a notification to the user, the calling communication network 1070 (or the user's communication network 1071) may first determine that a connection to the user's mobile device 1050 is not possible. it can. When a user deactivates a particular VSIM contract, the mobile device 1050 will continue to activate the user's communication network (i.e., 1071) until the contract is then re-activated, the mobile device is turned on, and is within the territory of the communication network 1071. ) Is not registered. As a result, calls to the mobile device 1050 via a disabled VSIM contract are not connected. This is similar to the situation where the mobile device 1050 is turned off or goes out of range of the user's communication network. Voice calls to mobile devices that are turned off or outside the user's communications network are typically routed to a voicemail server. When the user's communication network queries the home location registry and finds that the mobile device is not currently registered with the base station, the user's communication network typically forwards the call request to a voice mail server. Various embodiments may attempt to determine whether a different VSIM contract is enabled on the user's mobile device 1050 and prior to attempting to transfer the call to a voicemail server, Notifications can be sent. If it is determined that the VSIM contract is not in monitor mode (ie, FIGS. 2 and 3, decision 320 = No), the voice call can be forwarded to the voicemail server. Alternatively, in other embodiments, such as those shown below with respect to FIGS. 7a, 7b, 8, and 9, the voice call is voicemail if the recipient does not choose to switch the enabled VSIM Can be transferred to the server. In other embodiments, if the user disables the VSIM contract and chooses to put the VSIM contract into monitor mode, the voicemail function associated with the VSIM contract can be disabled.

  The mobile device 1050 processor may also obtain supply data for the VSIM contract selected to be enabled from memory and store the supply data in an active VSIM memory buffer (step 504). As described in previous VSIM patent applications, supply data for each of the activated VSIM contracts is stored in the local internal storage of the mobile device 1050 and in the VSIM server 1030 or the associated VSIM server database 1035. Can be stored in the user's VSIM account. When a particular VSIM contract is activated, supply data for the selected VSIM contract can be obtained and stored in an active VSIM memory buffer. This active VSIM memory buffer is accessed by the wireless transceiver to obtain the mobile device identifier, network frequency, and other information necessary to establish a wireless communication link with the selected service provider's network. . Thus, loading supply data into an active VSIM memory buffer is similar to inserting a SIM card into a mobile device.

  Once the newly activated VSIM contract supply data has been acquired and loaded into the active VSIM memory buffer, the mobile device 1050 establishes a wireless communication link with the newly activated VSIM contract communication network (e.g. 1072). Can be tried (steps 505 and 605). Once a communication link is established with the newly activated VSIM service provider network 1072, the mobile device 1050 processor may generate an indication to the user that the selected VSIM subscription is activated on the mobile device 1050. (Step 510). The processor of the mobile device 1050 may further present a display prompting the user to indicate whether the previously activated VSIM contract that has been deactivated should be put into monitor mode (decision 515). As already mentioned, in another embodiment, the VSIM contract can be automatically put into monitor mode whenever the VSIM contract is disabled. In such an embodiment, steps 515-517 can be omitted. If the user chooses to put the disabled VSIM contract into monitor mode (i.e., decision 515 = Yes), the mobile device 1050 processor will include the disabled VSIM contract in the message generated in step 510. An indication can be added indicating that the monitor mode should be entered (step 516). If the user chooses not to put the deactivated (previously activated) VSIM contract into monitor mode (i.e., decision 515 = No), the mobile device 1050 processor was generated in step 510 An indication can be added to the message indicating that the invalidated (previously activated) VSIM contract should not enter monitor mode (step 517). The messages generated in steps 510, 516, and 517 indicate part or all status of the VSIM contract, including instructions for currently enabled contracts and indicators of all disabled contracts that should be in monitoring mode It may be in the form of a status report indicating If the user chooses to put additional invalidated VSIM contracts into monitor mode, or chooses to remove additional invalidated VSIM contracts from monitor mode, additional Those skilled in the art will appreciate that messages can be generated or added.

  The mobile device 1050 can transmit a message indicating the current VSIM contract status to the VSIM server 1030 via the newly enabled (previously disabled) VSIM contract communication network 1072 (step 535). The message can be relayed to the VSIM server 1030 by the service provider communication network (step 635), and the VSIM server 1030 can receive the message (step 335). The VSIM server 1030 can store the latest VSIM contract status and update the user's VSIM account stored in the local memory of the VSIM server or in the VSIM database 1035 (step 340).

  The process flow diagram shown in Figure 4 is for illustrative purposes, sending any number of different messages to the VSIM server in various orders in order to keep the VSIM server informed of the VSIM contract status of the mobile device. Can do. For example, in another embodiment, after receiving a user request to switch an activated VSIM contract, the processor of the mobile device 1050 activates which VSIM contract and which VSIM contract A status report can be generated that indicates what should be included in the. This status report may be transmitted to the VSIM server 1030 via the communication network 1071 before being removed from the active VSIM memory buffer of the supply data supporting communication via the network 1071.

  FIG. 5 is a process flow diagram of an implementation method for processing a call attempt to a user's mobile device 1050 by a caller's communication network 1070. The steps are described herein as being performed by the calling communication network. However, it should be noted that the process flow shown in FIG. 5 can also be executed by the receiving communication network when a call attempt from the calling communication network is received. In many cases, the calling communication network may be the receiving communication network. In the various embodiments described herein, the various process flows are described as being performed by the calling communication network or the receiving communication network. It will be apparent to those skilled in the art that each of these implementations can be performed on either communication network.

  When the caller initiates a call attempt to the user's mobile device 1050, the caller's service provider communication network 1070 establishes an end-to-end communication link between the caller's communication device 1010 and the user's mobile device 1050. Try that. To initiate a call, the caller enters a unique identifier (MIN, phone number, etc.) associated with at least one of the user's VSIM contracts and initiates the call (eg, by pressing the “Send” key) To do. The communication device 1010 on the transmission side transmits the call request and the input unique identifier to the service provider communication network 1070 that is the call source. The call attempt request is received by the calling service provider communication network 1070 (step 201), and based on the information (e.g., a unique identifier) included in the call request, the calling service provider communication network 1070 inputs An attempt is made to establish an end-to-end communication link with the user's mobile device 1050 via the communication network associated with the unique identifier identified (step 202). Referring to FIG. 2, if the user's mobile device 1050 has activated a VSIM contract associated with the entered unique identifier, a communication link can be established and a call can be initiated (steps 203 and 550). After a predetermined time, the calling service provider network 1070 can determine whether the call is connected (decision 205). If the call is connected (ie, decision 205 = yes), the call continues (step 550).

  However, after a predetermined time, if the calling service provider network 1070 determines that the call is not connected (i.e., decision 205 = No), the calling service provider communication network 1070 receives the unique input A data communication call message to the VSIM server 1030 indicating the identifier (ie, the desired MIN) can be prepared (step 211). The data communication call may further indicate a unique identifier of the calling communication device 1010. This data communication call can be transmitted to the VSIM server 1030 (step 212). Once the data communication call is transmitted, the calling communication network 1070 can wait for a response from the VSIM server 1030. As described above with respect to FIG. 2, the VSIM server 1030 can obtain the user's VSIM account from the VSIM database 1035 using the information contained in the data communication call (see steps 310-330). While the VSIM server 1030 performs various steps in response to the received data communication call, the calling communication network 1070 can wait for a response from the VSIM server 1030 (step 213).

  While waiting for a response, the calling communication network 1070 can periodically determine whether a predetermined response time from the VSIM server 1030 has expired (decision 214). Because the VSIM server 1030 may be down or unable to respond immediately (for example, due to a caller load capacity problem), the caller's communication network 1070 will be disabled by limiting the time to wait for a response. Guarantee that you will not wait on time. Various situations may prevent the VSIM server from immediately providing a response to the calling communication network 1070. For example, the communication link between the communication network 1070 and the VSIM server 1030 may be terminated unexpectedly. In any case, if no response is received from the VSIM server 1030 within a predetermined time (ie, decision 214 = yes), the calling communication network 1070 can end the call attempt (step 215). However, if the predetermined time period has not expired (ie, decision 214 = No), the calling communication network 1070 can continue to wait for a response from the VSIM server 1030 (step 213).

  If the calling communications network 1070 receives an indication from the VSIM server 1030 that the VSIM contract associated with the entered unique identifier is not a VSIM type contract (i.e., decision 220 = no), the calling communications network 1070 terminates the call attempt (step 215), and can optionally indicate to the caller that the call attempt failed (step 216).

  If the calling communications network 1070 receives an indication that the unique identifier entered is associated with a VSIM type contract (i.e., decision 220 = yes), then the calling service provider network 1070 It is necessary to wait for a response as to whether a communication link with the mobile device 1050 is possible. Further, the calling service provider network 1070 can await a response as to whether the VSIM contract associated with the unique identifier is in monitor mode.

  If it is determined by the VSIM server 1030 that the desired VSIM contract is not in monitor mode (see step 320 in FIG. 2) (i.e., decision 218 = No), the calling communications network 1070 receives an indication of the status. The call attempt is terminated in the response (step 215). The caller's communication network 1070 generates a message, if necessary, and transmits it to the caller, indicating that the desired VSIM contract is not in monitor mode. If the called VSIM contract is determined by the VSIM server to be in monitor mode (see step 320 in Figure 2) (i.e., decision 218 = yes), the caller's communication network 1070 will call hold from the VSIM server 1030. An indication that the notification has been sent to the user's mobile device 1050 can be received and the information relayed to the calling communication device (step 230) (see also FIG. 2). In any embodiment where a sent notification indication is not generated and sent (see Figure 2, optional steps 230, 130), the predetermined time waiting for a response from the VSIM server may time out, The calling communication network 1070 can end the call attempt (decision 214 and step 215). As described above, the caller's communication network 1070 can transmit a message to the caller's communication device, if necessary, to indicate that the call attempt has failed (step 216).

  FIG. 6 is a process flow diagram of an implementation method in a VSIM server for processing a call attempt to a user's mobile device. If the caller's communication network determines that the call is not connected (i.e., decision 205 = No in FIGS. 2 and 5), the caller's communication network 1070 will request the unique identifier and caller's communication. A data communication call to the VSIM server 1030 is prepared and transmitted using information such as the unique identifier of the device 1010. The VSIM server 1030 receives the data call communication (step 310). Using the entered unique identifier included in the received data call communication as a lookup value, the VSIM server 1030 can retrieve the user's VSIM account from the server's local memory or the associated VSIM server database 1035 (Step 315). Accessing the information in the obtained VSIM account, the VSIM server 1030 may determine whether the desired VSIM contract is in monitor mode (decision 320). If the desired VSIM contract is not in monitor mode (i.e., decision 320 = no), the VSIM server 1030 generates and transmits a message to the calling communications network 1070 to indicate that it is in such a state. The call attempt can be terminated (step 311).

  One advantage of implementing a VSIM contract is the ability to upload the supply information associated with the VSIM contract to the VSIM server 1030 and then download the supply information to any communication device that supports the VSIM contract. For example, a user can borrow a communication device during a foreign trip and download it to the communication device that borrowed some or all of the VSIM contract. Some of the VSIM contracts are downloaded to the borrowed communication device, while other VSIM contracts may be downloaded to the user's personal communication device. Thus, in some cases it may also be necessary to determine the ID of the communication device from which the VSIM contract is downloaded. For example, a record of the electronic serial number (ESN) or international mobile unit identification code (IMEI) of the communication device can be recorded in the VSIM account each time VSIM contract information is downloaded to the communication device. This information may be included in the VSIM account stored by the VSIM server 1030. Thus, if it is determined that the desired VSIM contract is in monitor mode (i.e., decision 320 = yes), the VSIM server 1030 may first determine the ID of the VSIM contract communication device associated with the desired MIN. Yes (step 321). The VSIM server 1030 can then determine a unique identifier associated with the currently activated VSIM contract for the identified communication device (step 326). Alternatively, in embodiments where all of the user's VSIM contracts are downloaded to a single communication device, the step of identifying the mobile device can be omitted. In both embodiments, using a unique identifier associated with the currently activated VSIM contract, the VSIM server 1030 generates a notification and transmits it to the user's mobile device 1050 to invalidate the VSIM. The receipt of a call attempt to the contract can be indicated (step 330).

  In this manner, the various communication network elements are coordinated and utilized to provide the user's mobile device 1050 with a notification indicating receipt of a call attempt to the desired VSIM contract. Upon receiving the notification, the user can initiate a call to the caller using the information contained in the notification via the currently activated VSIM contract. Alternatively, the user can choose to switch VSIM contracts as described above with respect to FIG. 4, so that a VSIM contract for which a call attempt has been made is activated when the caller calls back.

  In another embodiment, when receiving an incoming call notification (see FIGS. 2 and 7a, step 530), the mobile device 1050 is entered and presented with a display that gives the user the option to switch VSIM subscriptions. The VSIM contract associated with the unique identifier (ie called number) can be immediately activated. If the user chooses to switch the VSIM contract, the incoming call attempt can be completed as soon as the VSIM contract switch takes effect. Figures 7a and 7b are process flow diagrams of an implementation method for providing notification to a user's mobile device that a call attempt has been received for a disabled VSIM contract and providing the user with an option to the VSIM contract. is there. The process flow of FIGS. 7a and 7b can be executed in addition to the process flow shown in FIG. As described above with respect to FIG. 2, a notification regarding an incoming call attempt may be sent to the mobile device 1050 (see FIGS. 7A and 2, steps 330, 430, and 530). In response, the mobile device 1050 can present the user with a prompt asking if the user wants to switch the VSIM contract to activate the VSIM contract for the incoming call. If the user responds to the prompt by indicating that the VSIM contract should not be switched (i.e., decision 518 = No), the mobile device 1050 responds to the VSIM server 1030 indicating the user's decision, if necessary. Can be generated (step 550). The generated message is transmitted and relayed through the communication network 1071 associated with the currently activated VSIM contract (step 450) and can be received by the VSIM server 1030 (step 350). Upon receipt, the VSIM server 1030 generates and transmits instructions to the caller and uses the user's communication device that uses a unique identifier associated with the currently disabled VSIM contract in the caller's communication network. Otherwise, the caller's communication network can notify that it is not necessary to continue to establish a communication link with the user's communication device 1050 (step 330a). Similar to the optional steps described above with respect to FIG. 2, this indication may be relayed via the caller's service provider communication network 1070 and received by the caller's communication device 1010 (steps 230 and 130).

  However, in response to a notification and question prompt, if the mobile device 1050 user chooses to switch VSIM subscriptions (i.e., decision 518 = yes), the mobile device 1050 processor will be associated with the unique identifier entered. The supply data of the VSIM contract to be acquired can be acquired and loaded into the active VSIM memory buffer (step 504) (FIG. 7b) (see also FIG. 4, steps 501 to 535). As described in detail above with respect to FIG. 4, the mobile device 1050 processor is optionally subscribed to the service provider network 1071 associated with the disabled (previously enabled) VSIM contract. Can be notified (step 403). Loading new supply data into the active VSIM memory buffer, the mobile device 1050 processor establishes a communication link with the communication network 1072 associated with the newly activated VSIM contract and sends a call to log into the network (Steps 505 and 605) (see also FIG. 4, steps 505 and 605). Once the communication link is established, a status report showing the switching of the currently active VSIM contract can be generated and transmitted to the VSIM server 1030 (see also steps 535, 635 and 335, FIG. 4). Upon receipt of the status report (step 335), the VSIM server 1030 generates and transmits a message to the calling service provider network 1070 and uses the entered unique identifier to the user's mobile device 1050. The caller's communication network 1070 can be notified that the call can be replaced (step 350). The calling service provider network 1070 can receive this message from the VSIM server 1030 (step 250) and attempt again to establish an end-to-end communication link with the user's mobile device 1050 (step 202). With the mobile device logged into the desired service provider network, the call request establishes an end-to-end communication link between the caller and the user's mobile device in a conventional manner (steps 602 and 605). Once the communication link is established, a call can be made (step 550).

  FIG. 8 is a process flow diagram of an implementation that can be implemented in a calling service provider communication network 1070 to handle a call to a user's mobile device 1050 when the user switches a VSIM subscription to receive the call. is there. The process flow of FIG. 8 is similar to the process flow described above with respect to FIG. However, if the caller's communication network 1070 receives an indication that the desired VSIM contract is in monitor mode (i.e., decision 218 = yes), the caller's communication network 1070 determines whether the user has switched the VSIM contract. For further instructions from the VSIM server 1030 (decision 235). If the caller's communication network 1070 receives an indication that the user has chosen not to switch the currently active VSIM contract (i.e., decision 235 = No), the caller's communication network 1070 will not issue a call attempt. The call is terminated (step 215) and can indicate to the caller that the call attempt failed, if necessary (step 216). Also, the caller communication network 1070 can wait for an instruction that a call hold notification has been sent to the user's mobile device, and relay the information to the caller communication device, similar to step 230 in FIG. If the caller's communication network 1070 receives an indication that the user has switched VSIM contracts (i.e., decision 235 = Yes), the communication network 1070 will try again to establish a communication link with the user's mobile device 1050. (Step 202) (see also FIG. 7b, step 202).

  FIG. 9 is a process flow diagram of an implementation that can be implemented in the VSIM server 1030 to process a call to the user's mobile device 1050 when the user chooses to switch VSIM subscription to receive the call. . The process flow of FIG. 9 is similar to the process flow described above with respect to FIG. However, after transmitting a notification message to the user's mobile device 1050 via the currently activated VSIM contract (step 330), the VSIM server 1030 indicates whether the user has switched the activated VSIM contract. The user can wait for a response from the mobile device 1050 (step 335). The VSIM server 1030 should not wait indefinitely for a response from the user's mobile device 1050, so when the VSIM server 1030 waits for a response, it periodically checks whether a predetermined time for the response has expired. Can be determined (decision 340). For various reasons, the user's mobile device 1050 may be prevented from immediately providing a response to the VSIM server 1030. For example, the communication link between the user's mobile device 1050 and the VSIM server 1030 may be terminated unexpectedly. Alternatively, the user may simply not respond to a request to switch VSIM contracts. If the predetermined time has not expired (ie, decision 340 = No), the VSIM server 1030 may continue to wait for a response from the user's mobile device 1050 (step 335). If a response is not received from the user's mobile device 1050 within a predetermined time (i.e., decision 340 = Yes), the VSIM server 1030 sends the call attempt sent to the user's mobile device 1050 to the calling communication device 1010. Notification instructions can be transmitted (step 330a). Alternatively, since the notification has already been sent to the user's mobile device 1050, the VSIM server 1030 can simply end the process flow.

  The VSIM server 1030 may receive a response from the user's mobile device 1050 indicating that the user has switched an activated VSIM contract or that the user has refused to make such a switch. it can. In one embodiment, other responses can also be transmitted, such as instructions when the user plans to switch VSIM subscriptions, which can be sent back to the caller so that the caller is available to the user You can call back when it becomes. If the response received from the mobile device 1050 indicates that the user has chosen not to switch the VSIM subscription (i.e., decision 345 = No), the VSIM server 1030 sends the user's mobile to the calling service provider network server 1030. A message that the device is not available can be transmitted (step 330a). If the response received from the mobile device 1050 indicates that the user has switched an activated VSIM contract (i.e., decision 345 = yes), then the VSIM server 1030 will now call the calling communication device 1010. A message can be transmitted to the caller's communication network 1070 notifying that a communication link between the user and the user's mobile device 1050 can be established (step 350).

  In order to allow the user to switch the currently activated VSIM contract, the caller is notified while the call attempt is performed and the caller performs the steps necessary to switch the activated VSIM contract. You may have to withstand a slight delay. However, by implementing the process flows in Figures 7a, 7b, 8, and 9, the caller can still contact the user even if the user is logged into a different service provider network at the time of the call it can.

  FIG. 10 illustrates exemplary components of a mobile device 1050 that are suitable for use in various embodiments. A typical mobile device 1050 includes a processor 1055 coupled to an internal memory 1057 and a user interface display 1051. The internal memory 1057 includes a VSIM storage device 1058 that is used to store the supply information for the activated VSIM contract. The VSIM storage device 1058 may be a partition in the mobile device's internal memory 1057 or may be a separate internal storage device (ie, a separate memory chip). In addition, the VSIM storage device 1058 can store personal data downloaded from the VSIM server 1030 for use in applications running on the mobile device processor 1055.

  Mobile device 1050 can include a mobile phone transceiver 1056 coupled to a wireless data link and coupled to an antenna 1094 and / or a processor 1055 for transmitting and receiving electromagnetic waves. In some implementations, the transceiver 1056 used for mobile phone communication and the portion of the processor 1055 and memory 1057 are referred to as a wireless interface. This is because the combination provides a data interface via a wireless data link. In addition, the mobile device 1050 typically includes a speaker 1059b that produces audible sound and a microphone 1059a for detecting sound, such as receiving a user's language. Both the microphone 1059a and the speaker 1059b can be connected to the processor 1055 via a vocoder 1054 that converts the analog electrical signal received from the microphone 1059a into a digital code, and the speaker 1059b transmits the digital code received from the processor 1055 to the sound wave. To an analog electrical signal that can be converted to In some implementations, the vocoder 1054 may be included as part of the circuitry and programming of the processor 1055.

  The processor 1055 may be any programmable microprocessor, microcomputer or multiple processor chips, or a chip that can be configured by software instructions (applications) to perform various functions, such as the functions of the various embodiments described below. . Some mobile devices may provide multiple processors 1055, such as one processor dedicated to wireless communication functions and one processor dedicated to running other applications. Typically, software applications can be stored in internal memory 1057 before being accessed and loaded into processor 1055. In some mobile devices, the processor 1055 may include sufficient internal memory to store application software instructions. For purposes of this description, the term memory generally refers to all memory accessible by the processor 1055, including internal memory 1057, VSIM storage 1058, and memory within the processor 1055 itself. Internal memory 1057 and VSIM storage device 1058 may be volatile or non-volatile memory such as flash memory, or a mixture of both. In a preferred embodiment, the VSIM storage device 1058 is a non-volatile memory for storing service contract provisioning data when the mobile device is turned off. Mobile devices also typically include a keypad 1053, menu selection button, or rocker switch 1052 to accept user input.

  A number of the above embodiments include a VSIM server 1030 and a number of servers embedded in each of the communication networks 1070, 1071, 1072 that assist in routing calls between the communication device 1010 and the mobile device 1050. Describes a simple server. FIG. 11 shows exemplary components of server 1080 suitable for use as any of the above identified servers. Such a remote server 1080 typically includes a large capacity non-volatile memory such as a processor 1081 and a disk drive 1083 coupled to volatile memory 1082. Server 1080 may also include a floppy disk drive and / or a compact disk (CD) drive 1084 coupled to processor 1081. Server 1080 also establishes a data connection, such as an Ethernet®, USB or FireWire® connector socket, or other network connection circuit 1085 for coupling the processor 1081 to a network 1086 such as the Internet. Or include a number of connector ports coupled to the processor 1081 for receiving external storage.

  The foregoing method descriptions and process flow diagrams are provided as illustrative examples only and are not intended to require or imply that the steps of the various embodiments are performed in the order presented. As will be apparent to those skilled in the art, the order of the steps in the foregoing embodiments can be performed in any order. Furthermore, terms such as “after”, “at that time”, “next” are not intended to limit the order of the steps. These terms are only used to explain the method to the reader. In addition, for example, the use of the articles “one (a)”, “one (an)”, “the (the)” to indicate a claim element in singular form means that the element is only singular. It should not be construed as limiting.

  The various illustrative logic blocks, modules, circuits, and algorithm steps described with respect to the embodiments disclosed herein can be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described generically 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 can implement the described functions in a variety of ways for each particular application, but such implementation decisions should not be construed as departing from the scope of the invention.

  The hardware used to implement the various illustrative logic, logic blocks, modules, and circuits described with respect to the aspects disclosed herein includes general purpose processors, digital signal processors (DSPs), and application specific integrated circuits. (ASIC), Field Programmable Gate Array (FPGA) or other programmable logic device, individual gate or transistor logic, individual hardware components, or any of them designed to perform the functions described herein Can be implemented or implemented using a combination of A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices such as, for example, DSPs and microprocessors, multiple microprocessors, one or more microprocessors associated with a DSP core, or other such configuration combinations Can do. Alternatively, some steps or methods may be performed by circuitry that is specific to a given function.

  In one or more exemplary aspects, the functions described can be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. The steps of the methods or algorithms disclosed herein can be implemented in executed, processor-executable software modules that can reside on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer readable media may be RAM, ROM, EEPROM, CD-ROM, or other optical disk storage device, magnetic disk storage device or other magnetic storage device, or as desired Other program codes can be used for transmission or storage in the form of instructions or data structures, including other media accessible by a computer. Also, any connection is correctly called a computer readable medium. For example, software is transmitted from a website, server, or other remote source using coaxial technology, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, wireless, and microwave. Wireless technology such as coaxial cable, fiber optic cable, twisted pair, DSL, or infrared, radio, and microwave are included in the definition of media. The discs and discs used in this specification are compact discs (CD), laser discs (registered trademark), optical discs, digital versatile discs (DVD), floppy (registered trademark) discs, and Blu-ray discs. In general, a disk reproduces data magnetically, and a disc optically reproduces data using a laser. Combinations of the above are also included within the scope of computer-readable media. Further, the operations of the method or algorithm may be present in one or any combination of code and / or instructions, or as a set, on machine-readable media and / or computer-readable media and may be incorporated into a computer program product. .

  The previous description of the disclosed 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. Also, the general principles defined herein can be applied to other embodiments without departing from the scope of the present invention. Accordingly, the present invention is not intended to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the appended claims and with the principles and novel features disclosed herein. Should be acknowledged.

1035 VSIM database
1050 users mobile devices
1052 Rocker switch
1053 keypad
1054 vocoder
1055 processor
1057 Internal memory
1058 VSIM storage device
1059a microphone
1059b speaker
1070 communication network
1080 server
1081 processor
1082 Volatile memory
1083 disk drive
1085 Network connection circuit
1086 network
1094 antenna

Claims (86)

Receiving data regarding an attempted call from a service provider network to a mobile device, the received data including a unique identifier associated with a currently invalidated VSIM contract;
Obtaining a VSIM account associated with the mobile device from a database using the unique identifier;
Determining a status of a VSIM contract activated on the mobile device from the acquired VSIM account;
Identifying a currently activated VSIM contract from the acquired VSIM account;
Identifying a unique identifier associated with the currently activated VSIM contract;
Transmitting a notification to the mobile device using the unique identifier associated with the currently activated VSIM contract, wherein the notification is the mobile card in the currently deactivated VSIM contract. A method of notifying a user of a call attempt to a mobile device via the currently disabled service provider contract comprising the step of indicating receipt of the call attempt to the device. Determining whether the currently disabled VSIM contract is in monitor mode;
The identification of the unique identifier associated with the currently enabled VSIM contract and transmission of the notification is performed when it is determined that the currently disabled VSIM contract is in monitor mode. The method according to 1. Receiving an indication from the mobile device that the activated VSIM contract has been switched;
The method of claim 1, further comprising: notifying the service provider network that the mobile device is available. Receiving an indication from the mobile device indicating that the activated VSIM contract cannot be switched;
The method of claim 1, further comprising: notifying the service provider network that the mobile device is unavailable. Receiving from the mobile device a status report of a VSIM contract activated on the mobile device, the status report identifying a disabled VSIM contract that should be in a monitoring mode;
The method of claim 3, further comprising: updating the acquired VSIM account based on the received status report. Receiving a call request including a unique identifier associated with at least one of a plurality of VSIM contracts;
Attempting to establish a communication link with the called mobile device using the unique identifier;
Determining whether the communication link has been established correctly;
Transmitting the data including the unique identifier to a remote server if the communication link is not properly established, and attempting to call the mobile device having the plurality of VSIM contracts.   The method of claim 6, wherein the call request is received from a caller's communication network.   7. The method of claim 6, wherein the call request is received from a caller communication device. Receiving a response from the remote server indicating whether the at least one of the plurality of VSIM contracts associated with the unique identifier is in a monitor mode;
7. The method of claim 6, further comprising: relaying an indication to the calling communication device that a call attempt notification has been sent to the mobile device. Receiving a response from the remote server indicating that the mobile device is available;
7. The method of claim 6, further comprising re-attempting to establish a communication link with the mobile device using the unique identifier. Activating one of several VSIM contracts;
Determining the currently disabled VSIM contract to be put into monitor mode;
Configured to activate one of the plurality of VSIM contracts, including: a currently activated VSIM contract and a status report of the disabled VSIM contract that should be in monitoring mode to a remote server To receive notifications on selected mobile devices.   The method of claim 11, wherein determining a currently disabled contract to enter the monitor mode comprises receiving a user's selection for a currently disabled VSIM contract to enter the monitor mode. . Receiving the notification indicating that a call attempt to the mobile device has been received via a disabled VSIM contract;
12. The method of claim 11, further comprising: processing information included in the notification.   14. The method of claim 13, further comprising displaying the processed information contained in the notification to a user. Determining whether the activated VSIM contract should be changed to one corresponding to the call attempt;
Activating the VSIM contract for one corresponding to the call attempt;
14. The method of claim 13, further comprising: notifying the remote server that the VSIM contract corresponding to the call attempt has been activated.   The decision on whether to change the activated VSIM contract to one corresponding to the call attempt is made by the user input to change the activated VSIM contract to one corresponding to the call attempt. 16. The method of claim 15, comprising receiving from. Further comprising the step of transmitting a request to a communication network supporting the currently activated VSIM contract to invalidate the currently activated VSIM contract;
16. The method of claim 15, wherein the request includes a request to disable a voice mail function associated with the currently enabled VSIM contract.   Prior to activating the VSIM contract corresponding to the call attempt, a request is transmitted to the communication network supporting the currently activated VSIM contract to invalidate the currently activated VSIM contract. The method of claim 17, wherein the step of performing is performed. Receiving a call request including a unique identifier associated with at least one of a plurality of VSIM contracts;
Attempting to establish a communication link with the called mobile device using the unique identifier;
Determining whether the communication link has been established correctly;
Transmitting the data including the unique identifier to a remote server if the communication link is not properly established; receiving the transmitted data from a service provider network at the remote server;
Obtaining a VSIM account associated with the mobile device from a database using the unique identifier;
Determining a status of a VSIM contract activated on the mobile device from the acquired VSIM account;
Identifying a currently activated VSIM contract from the acquired VSIM account;
Identifying a unique identifier associated with the currently activated VSIM contract;
Transmitting a notification to the mobile device using the unique identifier associated with the currently activated VSIM contract, the notification associated with the currently deactivated VSIM contract. A method of making a call to a mobile device configured to validate one of the plurality of VSIM contracts, including: using a unique identifier to indicate receipt of a call attempt to the mobile device.   20. The method of claim 19, wherein the call request is received from a caller's communication network.   20. The method of claim 19, wherein the call request is received from a caller communication device. Determining whether the currently disabled VSIM contract is in monitor mode;
The identification of the unique identifier associated with the currently enabled VSIM contract and transmission of the notification is performed when it is determined that the currently disabled VSIM contract is in monitor mode. 19. The method according to 19. Receiving an indication from the mobile device that the activated VSIM contract has been switched;
20. The method of claim 19, further comprising: notifying the service provider network that the mobile device is available. 20. The method of claim 19, further comprising: receiving an indication from the mobile device indicating that the activated VSIM contract cannot be switched; and notifying the service provider network that the mobile device is not available. the method of. Receiving from the mobile device a status report of a VSIM contract activated on the mobile device, the status report identifying a disabled VSIM contract that should be in a monitoring mode;
The method of claim 21, further comprising: updating the obtained VSIM account based on the received status report. Means for receiving data regarding an attempted call from a service provider network to a mobile device, the received data including a unique identifier associated with a currently invalidated VSIM contract;
Means for obtaining a VSIM account associated with the mobile device from a database using the unique identifier;
Means for determining a status of a VSIM contract activated on the mobile device from the acquired VSIM account;
Means for identifying a currently activated VSIM contract from the acquired VSIM account;
Means for identifying a unique identifier associated with the currently activated VSIM contract;
Means for transmitting a notification to the mobile device using the unique identifier associated with the currently activated VSIM contract, wherein the notification is in the currently invalidated VSIM contract. Means for indicating receipt of a call attempt to said mobile device. Means for determining whether the currently disabled VSIM contract is in monitor mode;
Means for identifying the unique identifier associated with the currently activated VSIM contract and transmitting the notification when it is determined that the currently deactivated VSIM contract is in monitor mode 27. The remote server of claim 26, wherein the means identifies the unique identifier associated with the currently activated VSIM contract and transmits the notification. Means for receiving an indication from the mobile device that the activated VSIM contract has been switched;
27. The remote server of claim 26, further comprising: means for notifying the service provider network that the mobile device is available. Further comprising: means for receiving an indication from the mobile device that the activated VSIM contract cannot be switched; and means for notifying the service provider network that the mobile device is unavailable. Item 26. The remote server according to item 26. Means for receiving a status report of a VSIM contract activated on the mobile device from the mobile device, wherein the status report is for identifying a disabled VSIM contract that should be in a monitoring mode. Means,
29. The remote server of claim 28, further comprising: means for updating the obtained VSIM account based on the received status report. Means for receiving a call request including a unique identifier associated with at least one of a plurality of VSIM contracts;
Means for attempting to establish a communication link with the called mobile device using the unique identifier;
Means for determining whether the communication link has been successfully established;
Means for transmitting data including said unique identifier to a remote server if said communication link is not properly established.   32. The communication network of claim 31, wherein the means for receiving the call request receives the call request from a caller communication network.   32. The communication network according to claim 31, wherein the means for receiving the call request receives the call request from a caller communication device. Means for receiving a response from the remote server indicating whether the at least one of the plurality of VSIM contracts associated with the unique identifier is in monitor mode;
32. The communication network according to claim 31, further comprising: means for relaying an indication indicating that a call attempt notification has been transmitted to the mobile device to a caller communication device. Means for receiving a response from the remote server indicating that the mobile device is available;
32. The communication network of claim 31, further comprising: means for retrying to establish a communication link with the mobile device using the unique identifier. A means to activate one of multiple VSIM contracts;
Means for determining currently disabled VSIM contracts to be put into monitor mode;
To activate one of the plurality of VSIM contracts, including a currently activated VSIM contract and a means for transmitting a status report of the disabled VSIM contract to be in monitoring mode to a remote server Mobile device configured to.   The means for determining a currently disabled contract to be put into the monitor mode further comprises means for receiving a user's selection for a currently disabled VSIM contract to be put into the monitor mode. Item 37. The mobile device according to Item 36. Means for receiving a notification indicating that a call attempt to the mobile device has been received via a disabled VSIM contract;
37. The mobile device of claim 36, further comprising: means for processing information included in the notification.   40. The mobile device of claim 36, further comprising displaying processed information included in the notification to a user. Means for determining whether to change said activated VSIM contract to one corresponding to a call attempt;
Means for validating the VSIM contract for one corresponding to the call attempt;
37. The mobile device of claim 36, further comprising: means for notifying the remote server that the VSIM contract corresponding to the call attempt has been activated.   The means for determining whether to change the activated VSIM contract to one corresponding to the call attempt is to change the activated VSIM contract to one corresponding to the call attempt. 40. The mobile device of claim 38, further comprising means for receiving input from the user. Means for transmitting a request to a communication network supporting a currently activated VSIM contract to invalidate the currently activated VSIM contract, wherein the request is 40. The mobile device of claim 38, including a request to disable voicemail functionality associated with a VSIM contract.   In order to invalidate the currently activated VSIM contract, the means for transmitting a request to a communication network that supports the currently activated VSIM contract includes the VSIM contract corresponding to the call attempt. 41. The mobile device according to claim 40, wherein the request is transmitted before enabling. Means for receiving a call request from a communication device to a mobile device configured to validate one of the plurality of VSIM contracts, including a unique identifier associated with at least one of the plurality of VSIM contracts When,
Means for attempting to establish a communication link with the called mobile device using the unique identifier;
Means for determining whether the communication link has been successfully established;
Means for transmitting data including the unique identifier to a remote server and means for receiving at the remote server the transmitted data from a service provider network if the communication link is not properly established; ,
Means for obtaining a VSIM account associated with the mobile device from a database using the unique identifier;
Means for determining a status of a VSIM contract activated on the mobile device from the acquired VSIM account;
Means for identifying a currently activated VSIM contract from the acquired VSIM account;
Means for identifying a unique identifier associated with the currently activated VSIM contract;
Means for transmitting a notification to the mobile device using the unique identifier associated with the currently activated VSIM contract, wherein the notification is associated with a currently deactivated VSIM contract. Means for indicating receipt of a call attempt to the mobile device using the unique identifier.   45. The communication system of claim 44, wherein the means for receiving the call request receives the call request from a caller communication network.   45. The communication system according to claim 44, wherein the means for receiving the call request receives the call request from a caller communication device. Means for determining whether the currently disabled VSIM contract is in monitor mode;
Means for identifying the unique identifier associated with the currently activated VSIM contract and transmitting the notification when it is determined that the currently deactivated VSIM contract is in monitor mode 45. The communication system according to claim 44, wherein the means identifies the unique identifier associated with the currently activated VSIM contract and transmits the notification. Means for receiving an indication from the mobile device that the activated VSIM contract has been switched;
Means for notifying the communication device that the mobile device is available;
45. The communication system according to claim 44, further comprising: Means for receiving an indication from the mobile device indicating that the activated VSIM contract cannot be switched; means for notifying the communication device that the mobile device is unavailable;
45. The communication system according to claim 44, further comprising: Means for receiving a status report of a VSIM contract activated on the mobile device from the mobile device, wherein the status report identifies a disabled VSIM contract that should be in a monitoring mode; ,
49. The communication system of claim 48, further comprising: means for updating the acquired VSIM account based on the received status report. A remote server storage device;
A remote server central processing unit coupled to the remote server storage device, the remote server processor comprising:
Receiving data regarding an attempted call from a service provider network to a mobile device, the received data including a unique identifier associated with a currently invalidated VSIM contract;
Obtaining a VSIM account associated with the mobile device from a database using the unique identifier;
Determining a status of a VSIM contract activated on the mobile device from the acquired VSIM account;
Identifying a currently activated VSIM contract from the acquired VSIM account;
Identifying a unique identifier associated with the currently activated VSIM contract;
Transmitting a notification to the mobile device using the unique identifier associated with the currently activated VSIM contract, wherein the notification is the mobile card in the currently deactivated VSIM contract. A remote server configured with software instructions to perform steps including: indicating the receipt of a call attempt to the device. The remote server central processing unit is:
Configured with software instructions to perform the steps further comprising: determining whether the currently invalidated VSIM contract is in monitor mode;
The identification of the unique identifier associated with the currently enabled VSIM contract and transmission of the notification is performed when it is determined that the currently disabled VSIM contract is in monitor mode. The remote server according to 51. The remote server central processing unit is:
Receiving an indication from the mobile device that the activated VSIM contract has been switched;
52. The remote server of claim 51, configured using software instructions to perform the steps further comprising: notifying the service provider network that the mobile device is available. The remote server central processing unit is:
Receiving further instructions from the mobile device indicating that the activated VSIM contract cannot be switched, and notifying the service provider network that the mobile device is not available. 52. The remote server of claim 51, wherein the remote server is configured using software instructions. The remote server central processing unit is:
Receiving from the mobile device a status report of a VSIM contract activated on the mobile device, the status report identifying a disabled VSIM contract that should be in a monitoring mode;
54. The remote server of claim 53, configured using software instructions to perform the steps further comprising: updating the obtained VSIM account based on the received status report. Further comprising: a call routing server storage device; and a call routing server central processing unit coupled to the call routing server storage device, the call routing server processor comprising:
Receiving a call request including a unique identifier associated with at least one of a plurality of VSIM contracts;
Attempting to establish a communication link with the called mobile device using the unique identifier;
Determining whether the communication link has been established correctly;
Transmitting the data including the unique identifier to a remote server if the communication link has not been properly established. A communication network configured using software instructions to perform the steps. The call routing server central processing unit is:
57. The communication network of claim 56, configured using software instructions to further perform steps including receiving the call request from a caller communication network. The call routing server central processing unit is:
57. The communication network of claim 56, configured using software instructions to further perform steps including receiving the call request from a caller communication device. The call routing server central processing unit is:
Receiving a response from the remote server indicating whether the at least one of the plurality of VSIM contracts associated with the unique identifier is in a monitor mode;
57. The communication network of claim 56, configured using software instructions to further perform a step comprising: relaying an indication to the communication device that a call attempt notification has been sent to the mobile device. The call routing server central processing unit is:
Receiving a response from the remote server indicating that the mobile device is available;
57. The communication network of claim 56, configured using software instructions to further perform the steps comprising: re-establishing a communication link with the mobile device using the unique identifier. . A mobile device processor;
A mobile device internal storage device coupled to the processor of the mobile device, the mobile device internal storage device including a VSIM supply data buffer and storing supply data for a plurality of VSIM contracts in the VSIM storage device; Including mobile devices,
The processor of the mobile device is
Activating one of the plurality of VSIM contracts;
Determining the currently disabled VSIM contract to be put into monitor mode;
A mobile configured with software instructions to perform steps including the step of transmitting a currently active VSIM contract and a status report of the disabled VSIM contract to be put into monitor mode to a remote server machine.   The processor of the mobile device is configured with software instructions to perform steps further comprising receiving a user's selection for a currently disabled VSIM contract to be put into the monitor mode, 62. The mobile device of claim 61, wherein the step of determining a currently invalidated contract to enter is based on the received user selection. The processor of the mobile device is
Receiving a notification indicating that a call attempt to the mobile device has been received via a disabled VSIM contract;
62. The mobile device of claim 61, configured using software instructions to perform the steps further comprising: processing information included in the notification. The processor of the mobile device is
64. The mobile device of claim 63, configured using software instructions to perform the steps further comprising: displaying to the user the processed information included in the notification. The processor of the mobile device is
Determining whether to change the activated VSIM contract to one corresponding to the call attempt;
Activating the VSIM contract for one corresponding to the call attempt;
64. The mobile device of claim 63, further configured using software instructions to perform steps further comprising: notifying the remote server that the VSIM contract corresponding to the call attempt has been activated. . The processor of the mobile device is
Receiving input from a user to change the activated VSIM contract to one corresponding to the call attempt, and determining whether to change the activated VSIM contract is the receiving from the user 64. The mobile device of claim 63, configured using software instructions to perform the steps further comprising: The processor of the mobile device is
Transmitting a request to a communication network supporting a currently activated VSIM contract to invalidate the currently activated VSIM contract, wherein the request is the currently activated VSIM contract; 64. The mobile device of claim 63, wherein the mobile device is configured with software instructions to perform a step further comprising: including a request to disable voicemail functionality associated with a VSIM contract. The processor of the mobile device is
Prior to activating the VSIM contract corresponding to the call attempt, a request is transmitted to the communication network supporting the currently activated VSIM contract to invalidate the currently activated VSIM contract. 68. The mobile device of claim 67, configured using software instructions to perform the steps further comprising: Receiving data regarding an attempted call from a service provider network to a mobile device, the received data including a unique identifier associated with a currently invalidated VSIM contract;
Obtaining a VSIM account associated with the mobile device from a database using the unique identifier;
Determining a status of a VSIM contract activated on the mobile device from the acquired VSIM account;
Identifying a currently activated VSIM contract from the acquired VSIM account;
Identifying a unique identifier associated with the currently activated VSIM contract;
Transmitting a notification to the mobile device using the unique identifier associated with the currently activated VSIM contract, wherein the notification is the mobile card in the currently deactivated VSIM contract. A tangible storage medium having stored thereon software instructions executable on a processor configured to cause the processor to execute steps including receiving a call attempt to the device. The tangible storage medium is
Having software instructions executable on a processor configured to perform the steps further comprising: determining whether the currently invalidated VSIM contract is in monitor mode;
The identification of the unique identifier associated with the currently enabled VSIM contract and transmission of the notification is performed when it is determined that the currently disabled VSIM contract is in monitor mode. The tangible storage medium according to 69. The tangible storage medium is
Receiving an indication from the mobile device that the activated VSIM contract has been switched;
70. The tangible storage medium of claim 69, having software instructions executable on a processor configured to cause the processor to further comprise the step of notifying the service provider network that the mobile device is available. The tangible storage medium is
Receiving from the mobile device an indication that the activated VSIM contract cannot be switched, and notifying the service provider network that the mobile device is not available to the processor. 70. The tangible storage medium of claim 69 having software instructions executable on a processor configured to cause the processor to execute. The tangible storage medium is
Receiving from the mobile device a status report of a VSIM contract activated on the mobile device, the status report identifying a disabled VSIM contract that should be in a monitoring mode;
72. The tangible of claim 71, comprising software instructions executable on a processor configured to cause the processor to execute a step further comprising: updating the obtained VSIM account based on the received status report. Storage media. Receiving a call request including a unique identifier associated with at least one of a plurality of VSIM contracts;
Attempting to establish a communication link with the called mobile device using the unique identifier;
Determining whether the communication link has been established correctly;
Software instructions executable on a processor configured to cause the processor to perform steps comprising: transmitting data including the unique identifier to a remote server if the communication link is not properly established; Stored tangible storage medium. The tangible storage medium is
75. The tangible storage medium of claim 74 having software instructions executable on a processor configured to cause the processor to execute steps further comprising: receiving the call request from a caller's communication network. The tangible storage medium is
75. A tangible storage medium as defined in claim 74, having software instructions executable on the processor configured to cause the processor to execute steps further comprising: receiving the call request from a caller communication device. The tangible storage medium is
Receiving a response from the remote server indicating whether the at least one of the plurality of VSIM contracts associated with the unique identifier is in a monitor mode;
75. Software instructions executable on a processor configured to cause the processor to execute a step further comprising: relaying an indication to the communication device that a call attempt notification has been sent to the mobile device. The tangible storage medium described in 1. The tangible storage medium is
Receiving a response from the remote server indicating that the mobile device is available;
And having software instructions executable on a processor configured to cause the processor to perform further steps including re-attempting to establish a communication link with the mobile device using the unique identifier. 74. A tangible storage medium according to 74. Activating one of several VSIM contracts;
Determining the currently disabled VSIM contract to be in monitor mode;
Can be executed on a processor that is configured to cause the processor to perform steps including the step of transmitting a status report of the currently activated VSIM contract and the disabled VSIM contract that should be in monitor mode to the remote server Tangible storage medium that stores various software instructions. The tangible storage medium is
Receiving a user's selection for a currently disabled VSIM contract to be put into the monitor mode, wherein determining a currently disabled contract to be put into the monitor mode comprises: 80. A tangible storage medium as defined in claim 79, having software instructions executable on a processor configured to cause the processor to execute a step further comprising: The tangible storage medium is
Receiving a notification indicating that a call attempt to a mobile device has been received via a disabled VSIM contract;
81. The tangible storage medium of claim 80, having software instructions executable on a processor configured to cause the processor to execute a step further comprising: processing information contained in the notification. The tangible storage medium is
84. The tangible storage of claim 81 having software instructions executable on a processor configured to cause the processor to execute a step further comprising: displaying to the user the processed information included in the notification. Medium. The tangible storage medium is
Determining whether to change the activated VSIM contract to one corresponding to the call attempt;
Activating the VSIM contract for one corresponding to the call attempt;
82. Software instructions executable on a processor configured to cause the processor to execute a step further comprising: notifying the remote server that the VSIM contract corresponding to the call attempt has been activated. The tangible storage medium described in 1. The tangible storage medium is
Receiving input from the user to change the activated VSIM contract to one corresponding to the call attempt, whether to change the activated VSIM contract from the user. 84. A tangible storage medium as defined in claim 83, having software instructions executable on a processor configured to cause a processor to execute a step further comprising: step based on the received input. The tangible storage medium is
Transmitting a request to a communication network supporting the currently activated VSIM contract to invalidate the currently activated VSIM contract, wherein the request is the currently activated VSIM contract; 84. The tangible storage medium of claim 83, having software instructions executable on a processor configured to cause the processor to execute a step further comprising the step of disabling a voice mail function associated with the VSIM contract. The tangible storage medium is
Prior to activating the VSIM contract corresponding to the call attempt, a request is transmitted to the communication network supporting the currently activated VSIM contract to deactivate the currently activated VSIM contract. 86. A tangible storage medium as claimed in claim 85, having software instructions executable on a processor configured to cause the processor to execute the steps further comprising: