WO2008050174A1

WO2008050174A1 - Externally triggered re-activation for user identity modules

Info

Publication number: WO2008050174A1
Application number: PCT/IB2006/003027
Authority: WO
Inventors: Uwe Schwarz; Andrew Daymond
Original assignee: Nokia Corporation; Nokia, Inc.
Priority date: 2006-10-27
Filing date: 2006-10-27
Publication date: 2008-05-02

Abstract

An apparatus for providing external data for use state determination includes a processing element and a communication element. The processing element may be configured to access information related to a subscription of a user to a first service at an account management element associated with the first service. The communication element may be configured to receive external data related to a second service and communicate the received external data to the processing element. The processing element may be further configured to determine a use state of a user identity module configured for use in association with both the first and second services based on the accessed information and the received external data.

Description

Externally triggered re-activation for user identity modules

TECHNOLOGICAL FIELD

Embodiments of the present invention relate generally to use stated determination procedures for user identity modules and, more particularly, relate to a method, apparatus, and computer program product for providing externally triggered expiry and/or re-activation for user identity modules.

BACKGROUND

The modern communications era has brought about a tremendous expansion of wireline and wireless networks. Computer networks, television networks, and telephony networks are experiencing an unprecedented technological expansion, fueled by consumer demand. Wireless and mobile networking technologies have addressed related consumer demands, while providing more flexibility and immediacy of information transfer.

Current and future networking technologies continue to facilitate ease of information transfer and convenience to users. One area in which there is a demand to increase ease of information transfer relates to the delivery of services to a user of a mobile terminal. The services may be in the form of a particular media or communication application desired by the user, such as a music player, a game player, an electronic book, short messages, email, etc. The services may also be in the form of interactive applications in which the user may communicate with a network device in order to perform a task or achieve a goal. The services may be provided from a network server or other network device, or even from the mobile terminal such as, for example, a mobile telephone, a mobile television, a mobile gaming system, etc.

One particular service which has recently been developed involves the concept of micro-banking. Micro-banking has developed in an effort to provide banking services to remote areas. In this regard, micro-banking solutions are directed toward providing opportunities for the utilization of banking services without a requirement for a local physical presence of a bank.

Another common service which has developed based on consumer demand involves the provision of prepaid services. For example, a prepaid subscriber identity module (SIM) may be utilized in connection with wireless communication services. A prepaid SIM card typically has some form of associated status or use state determining process which impacts the useful life of the SIM card. For example, when a prepaid SIM card is initially acquired and charged, the SIM card may provide all associated services for a predetermined period of time (i.e., a full use state), which may be followed by a limited use state where only some services (e.g., emergency calls or receiving calls) may be enabled until the contract period for the SIM card expires, at which time the Mobile Station Integrated Services Digital Network (MSISDN) number associated with the SIM card is cleared from a network database thereby rendering the SIM card useless. At any time before the contract period for the SIM card expires, it may be possible for the user to recharge (i.e., extend the contract period) by undertaking specific actions to that end.

Dependent upon the current use state and prepaid balance information, the user may or may not be enabled to perform certain functions. For example, the user could use all of the prepaid minutes purchased, thereby reducing the prepaid balance to zero and therefore be unable to place a call even though the SIM is within the full use state with respect to the contract period. Even though additional prepaid balance may be added or otherwise available when a service such as calling is desired, if the use state has not been updated, for example, by recharging (e.g., entering into a new contract), the user may be unable to place a call if the SIM card has progressed to the limited use state or has expired. The procedure above, regarding clearing the MSISDN of SIM cards that have not been recharged (i.e., no contract renewal has been effected) within a predetermined time period, has been maintained since there is limited MSISDN address space so that MSISDN numbers can be reused.

Although users may currently be able to re-activate an expired prepaid SIM card by calling a network operator customer care center or by going to a prepaid retailer location, each of these mechanisms requires a manual re-activation of an account through some form of user interface which calls a re-activation application programming interface (API) in the network operator's prepaid system. However, the existing mechanisms described above are disadvantageous since they may become expensive for the network operator if they are utilized frequently.

Accordingly, it may be desirable to provide a mechanism by which expiry/re-activation decisions (i.e., use state determination) regarding SIM cards or other user identity modules may be made without encountering the disadvantages described above.

BRIEF SUMMARY

A method, apparatus and computer program product are therefore provided for providing externally triggered expiry and/or re-activation for a user identity module (UIM) (e.g., a SIM). According to exemplary embodiments of the present invention, external information related to a particular service which is not associated with a communication network may be utilized in determining expiry and/or re-activation issues for UIMs. In one exemplary embodiment, a banking system may provide information related to banking services associated with the UIM. Accordingly, expiry and/or re-activation decisions may be made based on external data in addition to conventionally considered factors. In one exemplary embodiment, an identification number associated with the UIM (e.g., an MSISDN) may be associated with an identifier of an external service (e.g., a bank account) so that activity information associated with the external service may be utilized in connection with use state determination decisions associated with the UIM.

In one exemplary embodiment, a method of providing UIM use state determination based on external data is provided. The method includes accessing information related to a subscription of a user to a first service at an account management element associated with the first service, receiving external data related to a second service, and determining a use state of a user identity module configured for use in association with both the first and second services based on the received information and the received external data.

In another exemplary embodiment, a computer program product for providing UIM use state determination based on external data is provided. The computer program product includes at least one computer-readable storage medium having computer-readable program code portions stored therein. The computer-readable program code portions include first, second and third executable portions. The first executable portion is for accessing information related to a subscription of a user to a first service at an account management element associated with the first service. The second executable portion is for receiving external data related to a second service. The third executable portion is for determining a use state of a user identity module configured for use in association with both the first and second services based on the received information and the received external data.

In another exemplary embodiment, an apparatus for providing UIM use state determination based on external data is provided. The apparatus includes a processing element and a communication element. The processing element may be configured to access information related to a subscription of a user to a first service at an account management element associated with the first service. The communication element may be configured to receive external data related to a second service and communicate the received external data to the processing element. The processing element may be further configured to determine a use state of a user identity module configured for use in association with both the first and second services based on the accessed information and the received external data.

In another exemplary embodiment, a system for providing UIM use state determination based on external data is provided. The system includes a user identity module, an external service element and an account management element. The user identity module may be configured for use in association with a first service and a second service. The external service element may be associated with the second service. The account management element may be in communication with both the user identity module and the external service element. The account management element may be associated with the first service. The account management element may include a processing element configured to access information related to a subscription of a user of the first service. The account management element may also include a communication element configured to receive external data related to the second service from the external service element and communicate the received external data to the processing element. The processing element may be further configured to determine a use state of the user identity module based on the accessed information and the received external data.

In another exemplary embodiment, an apparatus for providing UIM use state determination based on external data is provided. The apparatus includes means for accessing information related to a subscription of a user to a first service at an account management element associated with the first service, means for receiving external data related to a second service and means for determining a use state of a user identity module configured for use in association with both the first and second services based on the received information and the received external data.

Embodiments of the invention may provide a method, apparatus and computer program product for employment in micro-banking and other applications. As a result, for example, mobile terminals and other electronic devices may benefit from an ability to maintain use of a particular UIM despite periods of inactivity with respect to one service associated with the UIM (e.g., a wireless communication service) by virtue of activity with respect to another service associated with the UIM (i.e., a service other than the wireless communication service).

Accordingly, micro-banking may be utilized in connection with prepaid services such as a prepaid UIM in an effort to provide banking services to remote areas. Thus, it may be possible to utilize banking services in connection with a UIM to provide cellphone banking services. Due to the comprehensive nature of cellular communication coverage, persons in many areas which are not near banks, but which have cellular communication coverage, may be enabled to perform certain banking functions.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING(S)

Having thus described embodiments of the invention in general terms, reference will now be made to the accompanying drawings, which are not necessarily drawn to scale, and wherein:

FIG. 1 is a schematic block diagram of a mobile terminal according to an exemplary embodiment of the present invention;

FIG. 2 is a schematic block diagram of a wireless communications system according to an exemplary embodiment of the present invention;

FIG. 3 illustrates a block diagram of a system for providing use state determination using external data according to an exemplary embodiment of the present invention;

FIG. 4 illustrates a block diagram of elements of an account management element according to an exemplary embodiment of the present invention;

FIG. 5 illustrate the execution of a use state determination process according to an exemplary embodiment of the present invention; FIG. 6 is a control flow diagram illustrating a set up of a UIM in accordance with exemplary embodiments of the present invention;

FIG. 7 illustrates an exemplary control flow diagram for operation of the system in response to the UIM performing use state updating according to an exemplary embodiment of the present invention;

FIG. 8 illustrates an exemplary control flow diagram for operation of the system for re-activation of the UIM in response to user request according to an exemplary embodiment of the present invention; and

FIG. 9 is a block diagram according to an exemplary method for providing external data for use state determination according to an exemplary embodiment of the present invention.

DETAILED DESCRIPTION

Embodiments of the present invention will now be described more fully hereinafter with reference to the accompanying drawings, in which some, but not all embodiments of the invention are shown. Indeed, the invention may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. Like reference numerals refer to like elements throughout.

FIG. 1 illustrates a block diagram of a mobile terminal 10 that would benefit from embodiments of the present invention. It should be understood, however, that a mobile telephone as illustrated and hereinafter described is merely illustrative of one type of mobile terminal that would benefit from embodiments of the present invention and, therefore, should not be taken to limit the scope of embodiments of the present invention. While several embodiments of the mobile terminal 10 are illustrated and will be hereinafter described for purposes of example, other types of mobile terminals, such as portable digital assistants (PDAs), pagers, mobile televisions, gaming devices, laptop computers, cameras, video recorders, audio/video players, GPS devices and other types of voice and text communications systems, or any combination of the aforementioned devices can readily employ embodiments of the present invention. Furthermore, devices that are not mobile may also readily employ embodiments of the present invention. The system and method of embodiments of the present invention will be primarily described below in conjunction with mobile communications applications. However, it should be understood that the system and method of embodiments of the present invention can be utilized in conjunction with a variety of other applications, both in the mobile communications industries and outside of the mobile communications industries.

The mobile terminal 10 includes an antenna 12 (or multiple antennae) in operable communication with a transmitter 14 and a receiver 16. The mobile terminal 10 further includes a controller 20 or other processing element that provides signals to and receives signals from the transmitter 14 and receiver 16, respectively. The signals include signaling information in accordance with the air interface standard of the applicable cellular system, and also user speech and/or user generated data. In this regard, the mobile terminal 10 is capable of operating with one or more air interface standards, communication protocols, modulation types, and access types. By way of illustration, the mobile terminal 10 is capable of operating in accordance with any of a number of first, second and/or third- generation communication protocols or the like. For example, the mobile terminal 10 may be capable of operating in accordance with second-generation (2G) wireless communication protocols IS-136 (TDMA), GSM, and IS-95 (CDMA), or with third-generation (3G) wireless communication protocols, such as UMTS, CDMA2000, and TD-SCDMA.

It is understood that the controller 20 includes circuitry required for implementing audio and logic functions of the mobile terminal 10. For example, the controller 20 may be comprised of a digital signal processor device, a microprocessor device, and various analog to digital converters, digital to analog converters, and other support circuits. Control and signal processing functions of the mobile terminal 10 are allocated between these devices according to their respective capabilities. The controller 20 thus may also include the functionality to convolutionally encode and interleave message and data prior to modulation and transmission. The controller 20 can additionally include an internal voice coder, and may include an internal data modem. Further, the controller 20 may include functionality to operate one or more software programs, which may be stored in memory. For example, the controller 20 may be capable of operating a connectivity program, such as a conventional Web browser. The connectivity program may then allow the mobile terminal 10 to transmit and receive Web content, such as location-based content, according to a Wireless Application Protocol (WAP), for example.

The mobile terminal 10 also comprises a user interface including an output device such as a conventional earphone or speaker 24, a ringer 22, a microphone 26, a display 28, and a user input interface, all of which are coupled to the controller 20. The user input interface, which allows the mobile terminal 10 to receive data, may include any of a number of devices allowing the mobile terminal 10 to receive data, such as a keypad 30, a touch display (not shown) or other input device. In embodiments including the keypad 30, the keypad 30 may include the conventional numeric (0-9) and related keys (#, *), and other keys used for operating the mobile terminal 10. Alternatively, the keypad 30 may include a conventional QWERTY keypad arrangement. The keypad 30 may also include various soft keys with associated functions. In addition, or alternatively, the mobile terminal 10 may include an interface device such as a joystick or other user input interface. The mobile terminal 10 further includes a battery 34, such as a vibrating battery pack, for powering various circuits that are required to operate the mobile terminal 10, as well as optionally providing mechanical vibration as a detectable output.

The mobile terminal 10 may further include a user identity module (UIM) 38. The UIM 38 is typically a memory device having a processor built in. The UIM 38 may include, for example, a subscriber identity module (SIM), a universal integrated circuit card (UICC), a universal subscriber identity module (USIM), a removable user identity module (R-UIM), etc. In addition, the UIM 38 may has fixed installation. The UIM 38 typically stores information elements related to a mobile subscriber. In addition to the UIM 38, the mobile terminal 10 may be equipped with memory. For example, the mobile terminal 10 may include volatile memory 40, such as volatile Random Access Memory (RAM) including a cache area for the temporary storage of data. The mobile terminal 10 may also include other non- volatile memory 42, which can be embedded and/or may be removable. The non-volatile memory 42 can additionally or alternatively comprise an EEPROM, flash memory or the like, such as that available from the SanDisk Corporation of Sunnyvale, California, or Lexar Media Inc. of Fremont, California. The memories 38, 40 and 42 can store any of a number of pieces of information, and data, used by the mobile terminal 10 to implement the functions of the mobile terminal 10. For example, the memories can include an identifier, such as an international mobile equipment identification (IMEI) code, capable of uniquely identifying the mobile terminal 10.

Referring now to FIG. 2, an illustration of one type of system that would benefit from embodiments of the present invention is provided. The system includes a plurality of network devices. As shown, one or more mobile terminals 10 may each include an antenna 12 for transmitting signals to and for receiving signals from a base site or base station (BS) 44. The base station 44 may be a part of one or more cellular or mobile networks each of which includes elements required to operate the network, such as a mobile switching center (MSC) 46. As well known to those skilled in the art, the mobile network may also be referred to as a Base Station/MSC/Interworking function (BMI). In operation, the MSC 46 is capable of routing calls to and from the mobile terminal 10 when the mobile terminal 10 is making and receiving calls. The MSC 46 can also provide a connection to landline trunks when the mobile terminal 10 is involved in a call. In addition, the MSC 46 can be capable of controlling the forwarding of messages to and from the mobile terminal 10, and can also control the forwarding of messages for the mobile terminal 10 to and from a messaging center. It should be noted that although the MSC 46 is shown in the system of FIG. 2, the MSC 46 is merely an exemplary network device and embodiments of the present invention are not limited to use in a network employing an MSC.

The MSC 46 can be coupled to a data network, such as a local area network (LAN), a metropolitan area network (MAN), and/or a wide area network (WAN). The MSC 46 can be directly coupled to the data network. In one typical embodiment, however, the MSC 46 is coupled to a GTW 48, and the GTW 48 is coupled to a WAN, such as the Internet 50. In turn, devices such as processing elements (e.g., personal computers, server computers or the like) can be coupled to the mobile terminal 10 via the Internet 50. For example, as explained below, the processing elements can include one or more processing elements associated with a computing system 52 (two shown in FIG. 2), origin server 54 (one shown in FIG. 2) or the like, as described below.

The BS 44 can also be coupled to a signaling GPRS (General Packet Radio Service) support node (SGSN) 56. As known to those skilled in the art, the SGSN 56 is typically capable of performing functions similar to the MSC 46 for packet switched services. The SGSN 56, like the MSC 46, can be coupled to a data network, such as the Internet 50. The SGSN 56 can be directly coupled to the data network. In a more typical embodiment, however, the SGSN 56 is coupled to a packet-switched core network, such as a GPRS core network 58. The packet- switched core network is then coupled to another GTW 48, such as a GTW GPRS support node (GGSN) 60, and the GGSN 60 is coupled to the Internet 50. In addition to the GGSN 60, the packet-switched core network can also be coupled to a GTW 48. Also, the GGSN 60 can be coupled to a messaging center. In this regard, the GGSN 60 and the SGSN 56, like the MSC 46, may be capable of controlling the forwarding of messages, such as MMS messages. The GGSN 60 and SGSN 56 may also be capable of controlling the forwarding of messages for the mobile terminal 10 to and from the messaging center.

In addition, by coupling the SGSN 56 to the GPRS core network 58 and the GGSN 60, devices such as a computing system 52 and/or origin server 54 may be coupled to the mobile terminal 10 via the Internet 50, SGSN 56 and GGSN 60. In this regard, devices such as the computing system 52 and/or origin server 54 may communicate with the mobile terminal 10 across the SGSN 56, GPRS core network 58 and the GGSN 60. By directly or indirectly connecting mobile terminals 10 and the other devices (e.g., computing system 52, origin server 54, etc.) to the Internet 50, the mobile terminals 10 may communicate with the other devices and with one another, such as according to the Hypertext Transfer Protocol (HTTP), to thereby carry out various functions of the mobile terminals 10.

Although not every element of every possible mobile network is shown and described herein, it should be appreciated that the mobile terminal 10 may be coupled to one or more of any of a number of different networks through the BS 44. In this regard, the network(s) can be capable of supporting communication in accordance with any one or more of a number of first-generation (IG), second- generation (2G), 2.5G and/or third-generation (3G) mobile communication protocols or the like. For example, one or more of the network(s) can be capable of supporting communication in accordance with 2G wireless communication protocols IS-136 (TDMA), GSM, and IS-95 (CDMA). Also, for example, one or more of the network(s) can be capable of supporting communication in accordance with 2.5G wireless communication protocols GPRS, Enhanced Data GSM Environment (EDGE), or the like. Further, for example, one or more of the network(s) can be capable of supporting communication in accordance with 3 G wireless communication protocols such as Universal Mobile Telephone System (UMTS) network employing Wideband Code Division Multiple Access (WCDMA) radio access technology. Some narrow-band AMPS (NAMPS), as well as TACS, network(s) may also benefit from embodiments of the present invention, as should dual or higher mode mobile stations (e.g., digital/analog or TDMA/CDMA/analog phones).

The mobile terminal 10 can further be coupled to one or more wireless access points (APs) 62. The APs 62 may comprise access points configured to communicate with the mobile terminal 10 in accordance with techniques such as, for example, radio frequency (RF), Bluetooth (BT), infrared (IrDA) or any of a number of different wireless networking techniques, including wireless LAN (WLAN) techniques such as IEEE 802.11 (e.g., 802.1 Ia, 802.1 Ib₅ 802.1 Ig, 802.1 In, etc.), WiMAX techniques such as IEEE 802.16, Wibree techniques, and/or ultra wideband (UWB) techniques such as IEEE 802.15 or the like. The APs 62 may be coupled to the Internet 50. Like with the MSC 46, the APs 62 can be directly coupled to the Internet 50. In one embodiment, however, the APs 62 are indirectly coupled to the Internet 50 via a GTW 48. Furthermore, in one embodiment, the BS 44 may be considered as another AP 62. As will be appreciated, by directly or indirectly connecting the mobile terminals 10 and the computing system 52, the origin server 54, and/or any of a number of other devices, to the Internet 50, the mobile terminals 10 can communicate with one another, the computing system, etc., to thereby carry out various functions of the mobile terminals 10, such as to transmit data, content or the like to, and/or receive content, data or the like from, the computing system 52. As used herein, the terms "data," "content," "information" and similar terms may be used interchangeably to refer to data capable of being transmitted, received and/or stored in accordance with embodiments of the present invention. Thus, use of any such terms should not be taken to limit the spirit and scope of embodiments of the present invention.

Although not shown in FIG. 2, in addition to or in lieu of coupling the mobile terminal 10 to computing systems 52 across the Internet 50, the mobile terminal 10 and computing system 52 may be coupled to one another and communicate in accordance with, for example, RF, BT, IrDA or any of a number of different wireline or wireless communication techniques, including LAN, WLAN, WiMAX and/or UWB techniques. One or more of the computing systems 52 can additionally, or alternatively, include a removable memory capable of storing content, which can thereafter be transferred to the mobile terminal 10. Further, the mobile terminal 10 can be coupled to one or more electronic devices, such as printers, digital projectors and/or other multimedia capturing, producing and/or storing devices (e.g., other terminals). Like with the computing systems 52, the mobile terminal 10 may be configured to communicate with the portable electronic devices in accordance with techniques such as, for example, RF, BT, IrDA or any of a number of different wireline or wireless communication techniques, including USB, LAN, WLAN, WiMAX and/or UWB techniques.

In an exemplary embodiment, data may be communicated over the system of FIG. 2 between different mobile terminals, any of which may be similar to the mobile terminal 10 of FIG. 1, or between a mobile terminal and other devices in communication with the system of FIG. 2. An exemplary embodiment of the invention will now be described with reference to FIG. 3, in which certain elements of a system for providing UIM state determination based on external data are displayed. The system of FIG. 3 may be employed, for example, in connection with a UIM used in the mobile terminal 10 of FIG. 1. However, it should be noted that the system of FIG. 3, may also be employed in connection with a variety of other devices, both mobile and fixed, and therefore, embodiments of the present invention should not be limited to application on devices such as the mobile terminal 10 of FIG. 1. It should also be noted, that while FIG. 3 illustrates one example of a configuration of a system for providing UIM state determination based on external data, numerous other configurations may also be used to implement embodiments of the present invention. Furthermore, although FIG. 3 will be described in the context of banking, such as a micro-banking, to illustrate an exemplary embodiment, other embodiments of the present invention need not necessarily be practiced in the context of micro-banking, but instead apply more generally to any incorporation of external data from a source that is not otherwise associated with services other than wireless communication network services. Examples of sources of such external data include a weather service, a news service, a music/video subscription service, e-book subscription service, a mobile TV service, a Visual Radio service, and virtually any other service in which activity related to the service, although unrelated to wireless communication services, may be used in making use state determinations for a UIM.

Referring now to FIG. 3, a system for providing UIM use state determination based on external data is provided. The system includes an account management element 70 in communication with a UIM 72 and an external service element 74. The UIM 74 may be embodied as any of the exemplary UIMs described above or any other known module of similar function (i.e., UICC, SIM, USIM, R-UIM, etc.). Communication between the UIM 72 and the account management element 70 may be performed pursuant to installation of the UIM 72 within a mobile terminal or other communication device. However, it should be understood that such communication need not be continuous. Further, however, it should be understood that such installation of the UIM 72 need not be continuous. For example, the UIM 72 could be associated with a particular user who does not possess a mobile terminal, but instead has periodic access to the mobile terminal in order to utilize, for example, wireless communication services and/or other services such as banking services. Similarly, communication between the account management element 70 and the external service element 74 may also be intermittent. Communication between the account management element 70 and the external service element 74 and/or the UIM 72 may be performed either via wired or wireless connections such as, for example, via the system of FIG. 2.

It should also be noted that communication between the UIM 72 and the account management element 70 may be indirect. In this regard, it should be understood that the UIM 72 (or a device associated with the UIM 72) may be in communication with another device or application in a manner such that the account management element 70 may control the communication between the UIM 72 (or the device associated with the UIM 72) and the other device or application even though the communication may not actually pass through the account management element 70. For example, a gateway device, through which communication between the UIM 72 (or the device associated with the UIM 72) and the other device or application passes, may communicate with the account management element 70 in order to determine whether to enable such communication based on a use state of the UIM 72 as determined at the account management element 70. Accordingly, the account management element 70 may allow or deny communications with the other device or application based on use state information or other subscription or account related information associated with the UIM 72.

The account management element 70 and the external service element 74 may each be any device or means embodied in either hardware, software, or a combination of hardware and software capable of performing the respective functions associated with each of the corresponding elements as described in greater detail below. In an exemplary embodiment the account management element 70 may be, for example, a server, an executable application or other device capable of storing and managing account information and making expiry and/or re-activation decisions (i.e., use state determination decisions) in connection with the UIM 72 that may impact the usability of the UIM 72. For example, the account management element 70 may be a server of a prepaid system. The external service element 74 may be a server, an executable application or other device capable of storing and managing account information or other data which may be associated with users of a service associated with the external service element 74. For example, in the case of micro-banking, the external service element 74 may be a banking application server configured to store account information associated with bank customers. In this regard, the account information may include an identifier of the account (e.g., an account number), information identifying the account owner and associated information related to activity and account status (e.g., balance, available credit, withdrawal and deposit amounts and corresponding dates, etc.).

In an exemplary embodiment, the account management element 70 may be a network server or a prepaid system server which manages use state determinations with respect to the UIM 72. As such, assume for the purposes of example, that the UIM 72 is initially activated or charged by the entry of a user into an agreement or contract for services. In an exemplary embodiment, the agreement for services may include an agreement with respect to a banking service and a wireless communication service. For example, the UIM 72 may be acquired for use with the banking service, but may also be utilized for wireless communication services such as sending short message service (SMS) messages, multimedia messaging service (MMS) messages, placing wireless phone calls, wireless email services, etc. Alternatively, the UIM 72 may be acquired in connection with a prepaid wireless communication service agreement, but may also be utilized in connection with the banking service. It should be noted, however, that although the present example is described in the context of banking services, other services are also possible for use in connection with exemplary embodiments of the present invention.

According to an exemplary embodiment, following the initial charging or activation of the UIM 72, an initial use state may be entered in accordance with the agreement. In this regard, the initial use state may be an unlimited service access state (e.g., a full use state) in which all services associated with the UIM 72 are accessible based on a prepaid balance associated with the provision of the services. In other words, for example, if there is a positive prepaid balance for wireless communication services and the UIM 72 is in a full use state, the UIM 72 may be enabled to access all wireless communication services until such time as the use state is downgraded or the prepaid balance is depleted below a level sufficient to cover the cost of the desired service. The account management element 70 may issue, update or otherwise manage account information related to the wireless service prepaid balance for the UIM 72 and the current use state of the UIM 72.

In an exemplary embodiment, a user associated with the UIM 72 may install the UIM 72 into a mobile terminal or other communication device in order to attempt to utilize a wireless communication network service via a wireless communication network associated with the account management element 70. In response to the attempt made by the user, the account management element 70 may check the use state and the prepaid balance associated with the UIM 72 before enabling the user to utilize the wireless communication network service. If the use state of the UIM 72 is such that access to the wireless communication network service may be granted, but the prepaid balance is insufficient, the account management element 70 may not enable the user to utilize the wireless communication network service. In an exemplary embodiment, the user may be informed of the deficiency and may subsequently be enabled to restore a sufficient prepaid balance by communication with the external service element 74 via the account management element 70. For example, the user may request a transfer of additional funds from a user owned account managed by the external service element 74 to be added to the user's prepaid balance. The account management element 70 may include, for example, a database associating UIM 72 identification information (e.g., MSISDN) to user bank account information, such that the account management element 70 may forward the request to transfer additional funds to the external service element 74 in connection with an account corresponding to the user of the UIM 72. In response to authentication of the request, the external service element 74 may transfer the additional funds thereby providing a sufficient prepaid balance to enable the user to utilize the wireless communication network service.

FIG. 4 illustrates elements of the account management element 70 according to an exemplary embodiment. The account management element 70 may include a processing element 90, a memory device 92 and a communication element 94. The processing elements as described herein may be embodied in many ways. For example, the processing element 90 may be embodied as a processor, a coprocessor, a controller or various other processing means or devices including integrated circuits such as, for example, an ASIC (application specific integrated circuit).

The memory device 92 may be configured to store information, data, applications, instructions or the like for enabling the processing element 90 to carry out various functions in accordance with exemplary embodiments of the present invention. For example, the memory device 92 could be configured to store applications for execution by the processing element 90. Additionally or alternatively, for example, the memory device 92 could be configured to store data such as account information under the control of the processing element 90. In an exemplary embodiment, the memory device 92 may be configured to store an identification number or other identifier associated with the UIM 72 (e.g., an MSISDN) in association with an identifier of an external service (e.g., a bank account number) so that activity information associated with the external service may be utilized in connection with use state determination decisions associated with the UIM 72 that are made by the account management element 70. In an exemplary embodiment, for privacy reasons, the memory device 92 may actually store a proxy identifier for the external service instead of an actual identifier. Accordingly, for example, the bank account number and other information may be kept confidential with respect as between services. As such, in communication between the account management element 70 and the external service element 74, the account management element 70 may utilize the proxy identifier, which the external service element 74 may then be able to associate with the actual bank account of the corresponding user. Additionally, the external service may associate the actual bank account of a user with a proxy identifier associated with a wireless customer so that wireless account data associated with the customer may be kept private.

The communication element 94 may be embodied as any device or means embodied in either hardware, software, or a combination of hardware and software that is configured to communicate data from/to the account management element 70. Accordingly, as shown in FIG. 4, the communication element 94 may be configured to communicate, either directly or indirectly, with the external service element 74 and/or the UIM 72 under the control of the processing element 90. The communication element 94 may be configured to provide a communication interface between the account management element 70 and other devices via either wired or wireless communication in accordance with any protocol known in the art. Additionally, the account management element 70 and the external service element 74 may be a same entity.

In an exemplary embodiment, as shown in FIG. 5, the processing element 90 may be configured to execute a use state determination process, such as an expiry or re-activation determination process, utilizing information received from internal and external sources. In this regard, as shown in FIG. 5, the processing element 90 may execute a use state determination application 100 by reading account data 102 related to a first service (e.g., a wireless communication service) from the memory device 92 that may be associated with a particular user and external data related to a second service. The use state determination application 100 may be executed in response to time based events (e.g., ending of a contract period), or in response to other events such as placing a call, performing a recharge, sending an SMS, etc. or in certain system based time intervals. The external data may include external data associated with the particular user 104 and external data that is not associated with the particular user 106. The external data that is associated with the particular user 104 could include, for example, banking information or any service subscription information. The external data that is not associated with the particular user 106 could include, for example, weather information, news information or other service information unrelated to the first service and the particular user. In either case, the external data may be either detailed information or merely an indicator such as a string that the account management element 70 may understand to be associated with activity or sufficient activity in connection with the external or second service. The account data 102 may include a use state variable 108, which the processing element 90 may be configured to change based on the state determination performed by the use state determination application 100. The use state variable 108 may define a current use state of the UIM 72. In an exemplary embodiment, the use state variable 108 may include states such as a pre-active state (e.g., before the UIM 72 has been activated), an active state (e.g., a full use state where full access to services is available), a credit expired state (e.g., a recharge is required and thus only limited access to services is available), and a subscription expired state (e.g., the MSISDN of the UIM 72 is cleared and no services are available). The use state determination may be made based on both the account data 102 (i.e., internal source information associated with the first service) and the external data (i.e., external source information associated with the second service). The account data may include, for example, time based information related to expiry date and other dates associated with use state changes. In an exemplary embodiment, the external data may be received by the processing element 90 via the communication element 94.

The external data that is associated with the particular user 104 may include activity information related to the second service. In other words, the external data that is associated with the particular user 104 may include activity information regarding frequency of use of the second service, account information for any account that may be associated with the user in connection with the second service (e.g., balance and/or credit available). Accordingly, activity and account information related to the second service may be utilized in determination of whether to alter the use state of the UIM 72.

In one exemplary embodiment, a use case is envisioned in which a customer may establish a bank account with a bank (i.e., the second service may be a banking service), upon establishment of the bank account, the bank may provide the customer with a UIM 72 which may be utilized at various kiosks, terminals, or in connection with a mobile terminal, to access banking services such as money transfers or cash withdrawals. The UIM 72 may also be associated with a prepaid wireless communication service (i.e., the first service may be a wireless communication service) enabling the customer to utilize wireless communications on a prepaid basis by initializing a wireless service account (i.e., assigning and activating a MSISDN for the UIM 72) for the customer automatically with an initial use state as determined in accordance with a predetermined arrangement between the bank and the wireless communications service operator. However, unlike a typical UIM for which the use state will eventually change, and potentially expire, based only on internal source information (i.e., information associated with activation and re-activation of the wireless service account), the UIM 72 according to embodiments of the present invention may include an associated use state determined based also upon external source information. Thus, a user may utilize the UIM 72 for accessing banking services, e.g. via a kiosk or booth that is offering access to the banking services, without utilizing the wireless communication services for a period of time. However, despite the lack of use of the wireless communication services, the UIM 72 may retain the capability for use in connection with the wireless communication services for so long as the banking services are being utilized. In other words, the MSISDN associated with the UIM 72 will not be deleted due to failure to use the UIM 72 in connection with the wireless communication services as long as another service associated with the external data is still being utilized. Accordingly, in an exemplary embodiment, an individual could utilize banking services to build reward points which may be redeemed for free airtime minutes or even a free phone from the wireless communication service network.

In the present use case, for example, rules associated with use state determination may be defined in relation to factors associated with the banking service (or another service or even a plurality of services). The factors associated with the banking service could include information regarding bank account status (e.g., whether the account is open, active, in use, etc.) or more detailed information related to the bank account such as the account balance or available credit.

Although the use case described above involved a situation in which a bank originally supplied the customer with the UIM 72, in other use case scenarios a wireless communication service could originally supply the UIM 72. Alternatively, if other services are provided in connection with the UIM 72, any provider of the other services may originally supply the customer with the UIM 72.

In an exemplary embodiment, a prepaid service such as a prepaid wireless communication service may request the external data from an external source in response to the occurrence of an event that would otherwise cause a use state change. For example, if a thirty day activation period associated with the UIM 72 has expired and the account management element 70 would otherwise change the use state of the UIM 72 to a subscription expired state in which the MSISDN associated with the UIM 72 is removed from association with the UIM 72 in a network database, the account management element 70 may be triggered to request external data from the banking service. If the banking service indicates that the customer has an active account, the account management element 70 may maintain the UIM 72 alive by indicating a use state that does not trigger expiration of the UIM 72. In one example, the account management element 70 may assign a credit expired state in which the UIM 72 may still be utilized for receiving calls and/or for emergency calls. Accordingly, by virtue of activity in connection with the banking service, an ability to utilize the wireless communication service in the future is preserved by maintaining the UIM 72 in a use state other than the subscription expired use state. Thus, at a later date, the customer may transfer funds to build the prepaid balance for use in connection with the wireless communication service.

In an exemplary embodiment, the account management element 70 may be further configured to utilize, for example, a recharge API and/or a re-activation API of a prepaid system providing wireless communication services automatically based on the external data. In this regard, if a use state change occurs to shift the use state of the UIM 72 to a subscription expired state, the processing element 90 of the account management element 70 may request external data from the external service element 74. In response to an indication of an active status with respect to the external or second service, the processing element 90 may call the re-activation API in order to change the use state to a credit expired use state in which the MSISDN of the UIM 72 is not cleared. Furthermore, in response to a use state change to the credit expired use state, the processing element 90 may request external data from the external service element 74. In response to an indication of an sufficient account balance with respect to, for example, a bank account associated with the external or second service, the processing element 90 may call the recharge API in order to change the use state from the credit expired use state to an active or full use state by automatically requesting and cooperating with the external service element 74 to effect a balance transfer to increase the prepaid balance associated with the UIM 72, which may be considered an automatic recharge. In various exemplary embodiments, the automatic recharge could be initiated at either the UIM 72, the account management element 70 or the external service element 74.

As stated above, external data that is not associated with the particular user 106 may also be utilized in connection with use state determinations. Thus, for example, if the account management element 70 would otherwise change the use state of the UIM 72 to a subscription expired state, the account management element 70 may request external data from a weather or news service. If the weather or news service indicates, for example, a hurricane warning or some other emergency event, the account management element 70 may assign a full use state to the UIM 72 for the duration of the emergency event to enable calls to be made for safety reasons.

FIG. 6 is a control flow diagram illustrating communication between the account management element 70, the UIM 72 and the external service element 72 in accordance with exemplary embodiments of the present invention. In this regard, FIG. 6 illustrates a control flow diagram relating to set up of a UIM in accordance with an exemplary embodiment of the present invention in which the external service is a banking service. Referring now to FIG. 6, in one exemplary embodiment, the UIM 72 may be issued to the user at a bank upon opening an account at operation 80. Information associated with the account (i.e., account information) may be stored, for example, in the external service element 74 of FIG. 3. The account information may include data such as a bank account identifier (e.g., bank account number), a personal identifier, a password, deposit/withdrawal data, bank account balance, a wireless communication network operator reactivation number, etc. The external service element 74 may then communicate with the account management element 70 of the wireless communication network in order to activate the UIM 72 and to provide the account management element 70 with the account information at operation 82. At operation 84, the account management element 70 may store information associated with the UIM 72 and the account information. The account management element 70 may then communicate the account information and activate the UIM 72 at operation 86. As an alternative to operations 84 and 86, the external service element 74 may directly communicate with the UIM 72 in order to activate the UIM 72 and transfer the account information to the UIM 72 at operation 88. At operation 89, the UIM 72 may store the account information including the re-activation phone number which may be a phone number which, when reached, may be utilized to recharge an account (i.e., alter the use state) or transfer funds to increase a prepaid balance.

FIG. 7 illustrates an exemplary control flow diagram for operation of the system when the processing element 90 executes the use state determination application 100. As shown in FIG. 7, if the account management element 70 makes a determination to execute the use state determination application 100 at operation 110, the account management element 70 may request bank account status information from the external service element 74 at operation 112. The external service element 74 may then check the bank account status at operation 114 and communicate the bank account status information to the account management element 70 at operation 116. In response to receipt of the bank account status information, the account management element 70 may determine a different use state for the UIM 72 than would have otherwise been determined using only the information available in the local account data 102. In other words, the account management element 70 may keep the UIM 72 alive (e.g., in a state other than the subscription expired state) if the bank account status information indicates that the bank account is still active, or the account management element 70 may clear the UIM 72 (i.e., delete the MSISDN) if the bank account status information indicates that the bank account is not active at operation 118. At operation 120, the account management element 70 and the external service element 74 may periodically communicate at either regular intervals or in response to other particular events. For example, the external service element 74 may automatically communicate closure of the account or inactivity for greater than a threshold amount of time.

FIG. 8 illustrates an exemplary control flow diagram for operation of the system for re-activation of the UIM 72 on user request. Such a situation might occur, for example, when the UIM 72 is in a limited use state that allows only the execution of the external banking services but not the normal wireless communication services and the user wishes to change the UIM 72 state by initiating a transfer of funds from the bank account to the prepaid account associated with the UIM 72 in the account management element 70. At operation 130, the user of the UIM 72 may initiate a re-activation procedure. In this regard, the user may utilize the re-activation number stored in the UIM 72 to initiate a call to request a fund transfer to increase the prepaid balance of the user. The request may be made directly to the external service element 74 or may be relayed to the external service element 74 by the account management element 70. Upon receiving the request, the external service element 74 may check a bank account balance associated with the user and deduct funds for transfer to the network service in accordance with the request at operation 132. The external service element 74 may then transfer money to the network service associated with the account management element 70 and an indication of the transfer to the account management element 70 at operation 134. The account management element 70 may then set the new prepaid balance based on the indication at operation 136 and send a confirmation of re-activation indication to the UIM 72 at operation 138.

FIGS. 6-8 above and FIG. 9 below are each representative of a flowchart of a system, method and program product according to exemplary embodiments of the invention. It will be understood that each block or step of the flowcharts, and combinations of blocks in the flowcharts, can be implemented by various means, such as hardware, firmware, and/or software including one or more computer program instructions. For example, one or more of the procedures described above may be embodied by computer program instructions. In this regard, the computer program instructions which embody the procedures described above may be stored by a memory device of an account management element and executed by a built-in processor in the account management element. As will be appreciated, any such computer program instructions may be loaded onto a computer or other programmable apparatus (i.e., hardware) to produce a machine, such that the instructions which execute on the computer or other programmable apparatus create means for implementing the functions specified in the flowcharts block(s) or step(s). These computer program instructions may also be stored in a computer- readable memory that can direct a computer or other programmable apparatus to function in a particular manner, such that the instructions stored in the computer- readable memory produce an article of manufacture including instruction means which implement the function specified in the flowcharts block(s) or step(s). The computer program instructions may also be loaded onto a computer or other programmable apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer- implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowcharts block(s) or step(s).

Accordingly, blocks or steps of the flowcharts support combinations of means for performing the specified functions, combinations of steps for performing the specified functions and program instruction means for performing the specified functions. It will also be understood that one or more blocks or steps of the flowcharts, and combinations of blocks or steps in the flowcharts, can be implemented by special purpose hardware-based computer systems which perform the specified functions or steps, or combinations of special purpose hardware and computer instructions.

In this regard, one embodiment of a method of providing external data for use state determination includes accessing information related to a subscription of a user of a first service at an account management element associated with the first service at operation 200. In an exemplary embodiment, the first service may be a wireless network communication service. At operation 210, external data may be received that is related to a second service. In an exemplary embodiment, the second service may be a banking service. Operation 210 may include receiving external data that is associated with the user or receiving external data that is not associated with the user. In an exemplary embodiment, operation 210 may include receiving status information related to an account associated with the second service. A use state of a user identity module configured for use in association with both the first and second services may then be determined based on the received information and the received external data at operation 220. The use state of the user identity module may be maintained active or alive in response to a determination that the account associated with the second service is active. In an exemplary embodiment, an optional operation 230 may include associating a first identifier of a first account of the user associated with the first service with a corresponding second identifier of a second account of the user associated with the second service. It should be noted that operation 230 may be performed at any point during performance of the method described above in connection with FIG. 9. In an exemplary embodiment, operation 230 may be performed once upon initialization of the UIM. In alternative exemplary embodiments, the external data may be requested, for example, based on a prepaid balance for use of the first service being reduced to zero, based on an occurrence of an event associated with initiation of a use state determination, or in response to an occurrence of an event associated with initiation of a use state determination.

The above described functions may be carried out in many ways. For example, any suitable means for carrying out each of the functions described above may be employed to carry out embodiments of the invention. In one embodiment, all or a portion of the elements of the invention generally operate under control of a computer program product. The computer program product for performing the methods of embodiments of the invention includes a computer-readable storage medium, such as the non-volatile storage medium, and computer-readable program code portions, such as a series of computer instructions, embodied in the computer- readable storage medium. Additionally, it should be noted that although the preceding descriptions refer to modules, it will be understood that such term is used for convenience and thus the modules above need not be modularized, but can be integrated and code can be intermixed in any way desired.

Many modifications and other embodiments of the inventions set forth herein will come to mind to one skilled in the art to which these inventions pertain having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the embodiments of the invention are not to be limited to the specific embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.

Claims

WHAT IS CLAIMED IS:

1. A method comprising: accessing information related to a subscription of a user of a first service at an account management element associated with the first service; receiving external data related to a second service; and determining a use state of a user identity module configured for use in association with both the first and second services based on the received information and the received external data.

2. A method according to Claim 1, wherein receiving the external data comprises receiving external data that is associated with the user.

3. A method according to Claim 1 , wherein receiving the external data comprises receiving external data that is not associated with the user.

4. A method according to Claim 1 , wherein receiving information related to the subscription of the user to the first service comprises receiving subscription information related a wireless network communication service.

5. A method according to Claim 4, wherein receiving external data related to the second service comprises receiving external data related to a banking service.

6. A method according to Claim 1 , wherein receiving external data related to the second service comprises receiving status information related to an account associated with the second service.

7. A method according to Claim 6, further comprising maintaining the use state of the user identity module active in response to a determination that the account associated with the second service is active.

8. A method according to Claim 1 , further comprising requesting the external data based on a prepaid balance for use of the first service being reduced to zero.

9. A method according to Claim 1 , further comprising requesting the external data based on an occurrence of an event associated with initiation of a use state determination.

10. A method according to Claim 9, wherein requesting the external data comprises requesting the external data in response to an occurrence of an event associated with initiation of a use state determination.

11. A method according to Claim 1 , further comprising associating a first identifier of a first account of the user associated with the first service with a corresponding second identifier of a second account of the user associated with the second service.

12. A computer program product comprising at least one computer- readable storage medium having computer-readable program code portions stored therein, the computer-readable program code portions comprising: a first executable portion for accessing information related to a subscription of a user of a first service at an account management element associated with the first service; a second executable portion for receiving external data related to a second service; and a third executable portion for determining a use state of a user identity module configured for use in association with both the first and second services based on the received information and the received external data.

13. A computer program product according to claim 12, wherein the second executable portion includes instructions for receiving external data that is associated with the user.

14. A computer program product according to Claim 12, wherein the second executable portion includes instructions for receiving external data that is not associated with the user.

15. A computer program product according to Claim 12, wherein the first executable portion includes instructions for receiving subscription information related a wireless network communication service.

16. A computer program product according to Claim 15, wherein the second executable portion includes instructions for receiving external data related to a banking service.

17. A computer program product according to Claim 12, wherein the second executable portion includes instructions for receiving status information related to an account associated with the second service.

18. A computer program product according to Claim 17, further comprising a fourth executable portion for maintaining the use state of the user identity module active in response to a determination that the account associated with the second service is active.

19. A computer program product according to Claim 12, further comprising a fourth executable portion for requesting the external data based on a prepaid balance for use of the first service being reduced to zero.

20. A computer program product according to Claim 12, further comprising a fourth executable portion for requesting the external data based on an occurrence of an event associated with initiation of a use state determination.

21. A computer program product according to Claim 20, wherein the second executable portion includes instructions for requesting the external data in response to an occurrence of an event associated with initiation of a use state determination.

22. A computer program product according to Claim 12, further comprising a fourth executable portion for associating a first identifier of a first account of the user associated with the first service with a corresponding second identifier of a second account of the user associated with the second service.

23. An apparatus comprising: a processing element configured to access information related to a subscription of a user of a first service at an account management element associated with the first service; and a communication element configured to receive external data related to a second service and communicate the received external data to the processing element, wherein the processing element is further configured to determine a use state of a user identity module configured for use in association with both the first and second services based on the accessed information and the received external data.

24. An apparatus according to Claim 23, wherein the communication element is further configured to receive external data that is associated with the user.

25. An apparatus according to Claim 23, wherein the communication element is further configured to receive external data that is not associated with the user.

26. An apparatus according to Claim 23, wherein the communication element is further configured to receive subscription information related a wireless network communication service.

27. An apparatus according to Claim 26, wherein the communication element is further configured to receive external data related to a banking service.

28. An apparatus according to Claim 23, wherein the communication element is further configured to receive status information related to an account associated with the second service.

29. An apparatus according to Claim 28, wherein the processing element is further configured to maintain the use state of the user identity module active in response to a determination that the account associated with the second service is active.

30. An apparatus according to Claim 23, wherein the processing element is further configured to request the external data based on a prepaid balance for use of the first service being reduced to zero.

31. An apparatus according to Claim 23, wherein the processing element is further configured to request the external data based on an occurrence of an event associated with initiation of a use state determination.

32. An apparatus according to Claim 31 , wherein the processing element is further configured to request the external data in response to an occurrence of an event associated with initiation of a use state determination.

33. An apparatus according to Claim 23, wherein the processing element is further configured to associate a first identifier of a first account of the user associated with the first service with a corresponding second identifier of a second account of the user associated with the second service.

34. A system comprising: a user identity module configured for use in association with a first service and a second service; an external service element associated with the second service; and an account management element in communication with both the user identity module and the external service element, wherein the account management element is associated with the first service and comprises: a processing element configured to access information related to a subscription of a user of the first service; and a communication element configured to receive external data related to the second service from the external service element and communicate the received external data to the processing element, and wherein the processing element is further configured to determine a use state of the user identity module based on the accessed information and the received external data.

35. A system according to Claim 34, wherein the communication element is further configured to receive subscription information related a wireless network communication service and external data related to a banking service.

36. A system according to Claim 34, wherein the processing element is further configured to associate a first identifier of a first account of the user associated with the first service with a corresponding second identifier of a second account of the user associated with the second service.

37. An apparatus comprising: means for accessing information related to a subscription of a user of a first service at an account management element associated with the first service; means for receiving external data related to a second service; and means for determining a use state of a user identity module configured for use in association with both the first and second services based on the received information and the received external data.

38. An apparatus according to claim 37, further comprising means for associating a first identifier of a first account of the user associated with the first service with a corresponding second identifier of a second account of the user associated with the second service.