Patent Grant
8175622
The present invention generally relates to mobile communication. More specifically, the invention relates to mobile communication corresponding to Multiple Mobile Station International Subscriber Directory Numbers (MSISDNs) associated with Multiple International Mobile Subscriber Identity (IMSIs) for a subscriber.
Mobile communication services are becoming increasingly popular. Hence, there is increasing competition between different mobile operators for building their roaming revenues. Mobile subscribers who frequently roam between two or more countries/networks contribute a majority of this roaming revenue. These mobile subscribers roam between their Home Public Mobile Network (HPMN) and one or more Visited Public Mobile Networks (VPMNs). The HPMN and the VPMNs can be in the same country or may be present in different countries. A local MSISDN of each of the VPMNs (i.e. VPMN MSISDNs) allows the roaming subscribers to call local subscribers of the VPMNs at cheaper local rates instead of expensive roaming rates. In addition, other local subscribers of the VPMN can also call these roaming subscribers of the HPMN at the local rates.
Usually, a roaming subscriber of the HPMN buys a new Subscriber Identity Module (SIM) of each VPMN he wants to visit. Hence, in such a case, the roaming subscriber needs to swap his HPMN SIM with the VPMN SIM, and therefore may not be able to receive call-related and non-call related services on his HPMN MSISDN. In addition, when the roaming subscriber returns to the HPMN, he cannot use call-related and non call-related services on his VPMN MSISDN. Therefore, it is desirable to facilitate mobile communication corresponding to both the HPMN MSISDN and VPMN MSISDNs.
In one technique (such as that taught by the present inventor in PCT Application Number WO US04/004975 entitled, “Providing Multiple MSISDN Numbers in a Mobile Device with a Single IMSI”) to provide such a service to the roaming subscriber, the HPMN reserves a special range of HPMN IMSIs to provide the service. To subscribe for the service, the roaming subscriber needs to buy a special HPMN SIM card with an HPMN IMSI belonging to the special HPMN IMSI range. The HPMN assigns one or more VPMN MSISDNs to the subscriber upon subscription request and associates those VPMN MSISDNs with the HPMN MSISDN. The VPMN MSISDNs belong to a special range of VPMN MSISDNs reserved by each of the VPMNs. The roaming subscriber, when registered in the VPMNs, enjoys a local rate benefit on the VPMN MSISDNs and in addition, is able to receive call-related and non call-related services on the HPMN MSISDN. However, the roaming subscriber is able to use the services corresponding to his HPMN profile only, even when he is in the VPMN.
According to another technique (such as that taught by the present inventor in PCT Application Number WO WO US04/026410, entitled, “Signaling Gateway with Multiple IMSI with Multiple MSISDN (MIMM) Service in a Single SIM for Multiple Roaming Partners”) to provide the service, the roaming subscriber carries a special SIM card that contains an HPMN IMSI and multiple VPMN IMSIs, with corresponding HPMN MSISDN and VPMN MSISDNs, respectively. When the roaming subscriber registers in one of the VPMNs, a SIM Tool-Kit (STK) application residing in the SIM card automatically detects the current location of the roaming subscriber and selects a corresponding IMSI and MSISDN. The roaming subscriber then enjoys the local rate benefit in the VPMN.
However, in one or more of the aforementioned techniques, the HPMN must reserve the special range of HPMN IMSIs and the VPMNs must reserve the special range of the VPMN MSISDNs. In addition, the VPMNs need to configure corresponding network elements of the VPMNs to route signaling messages, such as Signaling Connection and Control Part (SCCP) messages, to a Signaling Gateway (SG) hosted either in the HPMN or in the VPMNs. In addition, the roaming subscriber is unable to use services corresponding to his local VPMN profile. Furthermore, the VPMNs have to perform special billing procedures for these special range of IMSIs.
According to another technique to provide the service that contains a distributed network of nodes for handling the service, the roaming subscriber carries a special SIM card that contains an HPMN IMSI and a SIM Tool-Kit (STK) application. When the roaming subscriber registers with a VPMN with the HPMN IMSI in a first registration attempt, the STK application informs a VPMN node about the roaming subscriber's location and an HPMN node. The VPMN node will then send a VPMN IMSI and a corresponding VPMN MSISDN to the roaming subscriber's SIM card. The STK will cause the handset to initiate a second registration attempt with the VPMN IMSI this time. Thereafter, the VPMN node provides information to the HPMN node about the roaming subscriber, i.e. the roaming subscriber's location, the VPMN IMSI, and the VPMN MSISDN. The roaming subscriber then enjoys the local rate benefit in the VPMN. The VPMN node and HPMN node also coordinate to handle call and SMS services, on either a HPMN number or a VPMN number. However, in this approach two registration attempts are required before the roaming subscriber is treated a local subscriber. Furthermore, a distributed network of nodes consisting of HPMN node and a node in each VPMN the subscriber visits, is also required.
In accordance with the foregoing, there is a need in the art for a cost-effective solution for facilitating mobile communication corresponding to the HPMN MSISDN and multiple VPMN MSISDNs of the roaming subscriber.
The present invention is directed to provide a method for proving mobile communication corresponding to Multiple MSISDNs associated with Multiple IMSIs of a subscriber. The method includes associating at a Signaling Gateway (SG), a first IMSI corresponding to a first network with one or more other IMSIs upon receipt of one or more association messages. The first and other IMSIs is associated with a subscriber using at least one SIM. Further, each IMSI has a corresponding MSISDN. The method further includes facilitating mobile communication corresponding to any associated IMSI and the corresponding associated MSISDN, irrespective of the IMSI being activated in the SIM.
An aspect of the invention presents a system for providing the “MIMM” (Multiple IMSI Multiple MSISDN) service. The system includes a Signaling Gateway (SG) coupled to the first network. The SG receives one or more association messages for associating a first IMSI corresponding to a first network with one or more other IMSIs. The first and other IMSIs are associated with a subscriber using at least one SIM. Further, each IMSI has a corresponding MSISDN. The SG further facilitates mobile communication corresponding to any associated IMSI and the corresponding associated MSISDN, irrespective of the IMSI being activated in the SIM.
Another aspect of the present invention provides a computer program product including a computer usable program code for providing MIMM service by, associating at a Signaling Gateway (SG), a first IMSI corresponding to a first network with one or more other IMSIs upon receipt of one or more association messages, and facilitating mobile communication corresponding to any associated IMSI and the corresponding associated MSISDN, irrespective of the IMSI being activated in the SIM.
In the drawings, the same or similar reference numbers identify similar elements or acts.
In the following description, for purposes of explanation, specific numbers, materials and configurations are set forth in order to provide a thorough understanding of the invention. It will be apparent, however, to one having ordinary skill in the art, that the invention may be practiced without these specific details. In some instances, well-known features may be omitted or simplified, so as not to obscure the present invention. Furthermore, reference in the specification to “one embodiment” or “an embodiment” means that a particular feature, structure or characteristic, described in connection with the embodiment, is included in at least one embodiment of the invention. The appearance of the phrase “in an embodiment”, in various places in the specification, does not necessarily refer to the same embodiment.
The present invention provides a system, method and a computer program product for facilitating Multiple IMSI Multiple MSISDN (MIMM) service. The system facilitates MIMM service for a subscriber who is associated with an HPMN, with a corresponding first IMSI and first MSISDN, but may be roaming in a VPMN with a VPMN SIM and its corresponding second IMSI and second MSISDN. The HPMN IMSI and HPMN MSISDN are hereinafter referred to as IMSI-H and MSISDN-H respectively. Likewise, the VPMN IMSI and VPMN MSISDN are hereinafter referred to as IMSI-V and MSISDN-V. Further, the system may be interchangeable referred to as MIMM system. The system enables registration of the subscriber in the VPMN with a VPMN IMSI and VPMN MSISDN while keeping the MSISDN-H active, thus applying local rates for the subscriber in the VPMN. The former embodiment of multiple VPMN SIMs requires the subscriber to swap the HPMN SIM with the VPMN SIM whenever he wishes to use the MIMM services in corresponding VPMN network. Usually, in such a case, the operator implementing the MIMM service will form partnership with one or more VPMNs, and may refer them as FPMNs. Hereinafter, VPMNs may be interchangeably referred to as FPMNs. Further, the operator may procure prepaid or postpaid SIMs from these VPMN operators offer the same to its subscribers, who subscriber to the MIMM service. However, in latter embodiment of single HPMN SIM with multiple VPMN IMSIs, the subscriber either manually chooses the VPMN IMSI corresponding to the VPMN country or the STK application automatically selects the correct VPMN IMSI-V. The system provides a seamless implementation to allow a plurality of services, but not limited to, call related and non-call related (i.e. VAS) for all its subscribers.
In one embodiment, the present invention can also support postpaid VPMN IMSI/MSISDN in the VPMN profiles; however in this case, it will require a special billing process and special IMSI/MSISDN range, unless the postpaid users are also subscribers of VPMN operators. Such a scenario is best handled as described in U.S. patent application Ser. No. 10/918,645, entitled “Signaling Gateway with Multiple IMSI with Multiple/Single MSISDN (MIMM/MSIM) Service in a Single SIM for Multiple Roaming Partners”, filed on Aug. 13, 2004, one of the parent applications of the present application. The procedure described in this parent application does not require a VPMN profile or a VPMN authentication procedure. Nevertheless, if the postpaid subscribers have separate accounts with the VPMN operators, i.e., each postpaid sucscriber is separately responsible for the VPMN operators' bill, there may be no need for the special billing process, in accordance with one embodiment of the present invention.
In the case of prepaid VPMN local number, there are no special billing changes (other than the prepaid reseller or distributor relationship). In the case of postpaid, special billing will be required since the customers belong to a HPMN, unless the subscriber also has a direct billing relationship with the VPMN operator. The billing can be done via a MVNO operator, for example.
One embodiment of the present invention provides an alternative to the solution described in U.S. patent application Ser. No. 10/778,861, entitled “Signaling and Packet Relay Including General Packet Radio Services (“GPRS”, filed Feb. 13, 2004, on supporting a sponsored operator's subscriber to roam in a VPMN operator that only has a roaming relationship with a sponsor operator not with the sponsored operator. In this case, the sponsored operator's subscriber can simply take a sponsor operator SIM (with or without using a dual IMSI SIM) to the VPMN operator. It is particularly attractive for the case of just using a sponsor operator SIM since dual IMSI SIMs can be a lengthy logistic process. The sponsored operator's subscriber can just obtain a prepaid or postpaid sponsor operator SIM and roam in the VPMN operator without losing calls and SMS on his sponsored operator phone number.
MIMM System
HPMN 102 allocates an HPMN SIM to a first IMSI and a corresponding first MSISDN when subscriber 106 registers with HPMN 102. However, subscriber 106 may visit one or more VPMN networks. There are two ways to offer the MIMM service in such a case. In the first case, subscriber 106 may receive multiple VPMN SIMs (for each VPMN network/country he plans to visit) from HPMN 102. The HPMN operator may form a partnership with one or more VPMN operators and procure multiple VPMN SIMs (postpaid or prepaid) from its subscriber. Alternatively, the subscriber may not have to pre-buy and pre-register a partner VPMN SIM before embarking on a trip. The subscriber may buy the VPMN SIM once he visits that VPMN network/country. In one embodiment of the invention, the partnership may be with different VPMN operators in same country. In another embodiment of the invention, the partnership may be with different VPMN operators in different countries.
In the case where a subscriber is able to purchase a SIM from the participating VPMN on his arrival in the visited country, the VPMN, or SIM reseller, may promote the service by sending the subscriber a “Welcome SMS” message or other notification as is known in the art, upon the subscriber's arrival in the visited country, or the VPMN's territory.
Such a Welcome SMS message or other notification could contain a hyperlink or callback number which the subscriber could activate to receive more information about obtaining a VPMN SIM enabling a MIMM service. Alternatively, the message itself could contain information directing the subscriber to where he might purchase a MIMM enabling SIM. In another alternative, based on detecting the subscriber handset location, the message or notification can direct the subscriber to the nearest store selling the VPMN SIM enabling the MIMM service. Alternatively, a user could activate the message to elect receiving such a SIM, and based on the handset location, a delivery person could deliver the SIM to the subscriber (e.g. at the customs or baggage claim exit, at the rental car counter, or at the subscriber's hotel.)
Referring to a scenario in which the MIMM service is offered by more than one VPMN within the same territory, the subscriber may also use an HPMN SIM with multiple VPMN IMSIs in the same SIM, to avoid changing the SIM each time he changes the VPMN network. In both cases, the VPMN operator can provide local handset configuration information, such as but not limited to, GPRS, MMS and WAP. The VPMN operator also provides IMSI, Ki and SMSC information in multiple IMSI in a single SIM implementation to the HPMN operator. The multiple IMSI SIM has a special STK application that modifies the IMSI and Ki entry. The SIM is also equipped with different authentication algorithms for A3 and A8. Usually, operators follow GSM recommended algorithms for A3 and A8, however, some exceptions such as Vodafone™ require modified algorithms. In such cases, these special SIMs may be manufactured by SIM vendors such as Bluefish and Axalto/Gemplus. Moreover, different client applications such as, but not limited to, BREW, Symbian, Java™, Microsoft®, and Linux™ may be used instead of STK. While similar or more advanced implementations are also possible within the scope of this invention, STK is used only as an exemplary implementation.
A special file called IMSI-Subscription is present in the SIM. This file contains records in the following possible formats, in accordance with various embodiments of the present invention.
a) MCC IMSI Ki Algorithm-Index SMSC-Address
The first entry may be the home country record post-fixed by H.
b) MCC-H IMSI-H Ki-H Algorithm-Index-H SMSC-H
In another embodiment of the invention, MCC may be a wildcard such as “*”. This is usually applicable with the HPMN IMSI as the last entry in the file.
c) * HPMN-IMSI Ki-HPMN Algorithm-Index-HPMN HPMN-SMSC
Usually, MCC is supported by a MCC-matching IMSI. For example, a China MCC 460 can be supported by a 46001-X IMSI.
d) 460 46001-X Ki Algorithm-Index 46001-SMSC
However, MCC also can be supported by an IMSI that does not have the identical MCC. For example, Netherlands MCC (204) may be supported by a Belgium IMSI with MCC 206.
e) 204 20610-X Ki Algorithm-Index 20610-SMSC
Similarly, there could also be multiple entries for the same MCC with different IMSIs. For example, two different China IMSIs (China Mobile and China Unicom, respectively) may support China.
f) 460 46000-X Ki-X Algorithm-Index-X 46000-SMSC
g) 460 46001-Y Ki-Y Algorithm-Index-Y 46001-SMSC
In yet another example, two different Belgium IMSIs (e.g. MobileStar and Proximus) might support Netherlands.
i) 204 20610-X Ki-X Algorithm-Index-X 20610-SMSC
j) 204 20601-Y Ki-Y Algorithm-Index-Y 20601-SMSC
In addition, in some particular cases, there could be another IMSI support as well for the same country. For example, a Netherlands IMSI (e.g. ONL 20420-X) may best support Netherlands. However, if the IMSI 20420 ONL does not have coverage at any spot in Netherlands, an alternative Belgium IMSI may be used (e.g. Mobilestar IMSI 20610-Y). However, the same country order is based on preference settings.
k) 204 20420-X Ki-X Algorithm-Index-X 20420-SMSC
l) 204 20610-Y Ki-Y Algorithm-Index-Y 20420-SMSC
The switching of IMSIs is transparent to the subscriber, although there may be a manual selection mechanism via a menu for the subscriber to select a VPMN IMSI. When the subscriber registers in a network with any current IMSI in the SIM, the STK application is able to know the network and the country in which the subscriber is registered. Further, when the subscriber is unable to register with a network corresponding to the current IMSI in the SIM, the STK application is aware of the present country of the subscriber by referring to the forbidden list in the SIM. Thereafter, the STK application chooses the optimum IMSI from the subscriber's IMSI-Subscription file for that country. In case no matching entry for IMSI is found, the default is set to HPMN IMSI.
Otherwise, the STK application loads the located IMSI, and its corresponding Ki into the corresponding SIM location, and sets the current security algorithms to those as indexed by the Algorithm-Index of the located IMSI. The STK application then forces a re-registration process. This process repeats itself until either the subscriber is registered with a network in the current country, or it fails to register with a network with all the IMSIs that are suitable for that country. If at any given time, the subscriber is registered with an IMSI for a country that has a preferred IMSI, the STK application periodically performs the replacement to check for the more preferred IMSI, in decreasing order of preference.
When subscriber 106 buys these partner VPMN SIMs, or uses the original HPMN SIM with VPMN IMSIs, the HPMN operator performs the registration process required for each VPMN operator via various methods such as, but not limited to, a customer care shop, a retail shop, and a kiosk (e.g., at an airport). In addition, the registration process may include a requirement of the subscriber's identification details, at the VPMN operator, which may be sent by the HPMN operator via an IP network, such as email. SG 108 residing in HPMN 102 performs this registration process. SG 108 authenticates each VPMN SIM and its corresponding IMSI in the local network to which it is associated. Furthermore, SG 108 maintains a local profile of subscriber 106 corresponding to the IMSI activated in his SIM. In other words, the local service at VPMN 104, such as SMS, call, supplementary services, and data, will be conforming to his local VPMN profile rather than HPMN 102's profile. It will be apparent to a person skilled in the art, that HPMN 102 operator may be an MVNO operator hosting SG 108. The process of association of HPMN IMSI-H and MSISDN-H, with one or more VPMN IMSI-V and MSISDN-V, is described in conjunction with
Upon receiving the SMS as the association message at SG 108, it acquires IMSI-H of subscriber 106 by issuing a MAP SRI-SM query or Send IMSI query on MSISDN-H to HLR-H 112. Thereafter, at step 218, SG 108 issues a location update such as, a MAP LUP, on the IMSI-H of subscriber 106 to HLR-H 112, with the assigned HPMN GT as VMSC-V 128 and VLR-V 130. In one embodiment of the invention, the subscriber's profile corresponding to IMSI-H does not necessarily have to be granted for roaming. In another embodiment of the invention, SG 108 uses special fictitious foreign GT to fake as VLR-V 130 and VMSC-V 128, when roaming is a pre-requisite for subscriber 106's profile at HLR-H 112. However, in such a case, STP-H 110 is configured to route these fictitious foreign GT-destined SCCP messages towards SG 108. Thereafter, at step 220, HLR-H 112 issues an ISD message to SG 108. SG 108, at step 222, acknowledges the ISD message. Finally, at step 224, HLR-H 112 acknowledges LUP message to activate and associate the IMSI-V and MSISDN-V of subscriber 106 to IMSI-H and MSISDN-H. Hence, SG 108 facilitates mobile communication corresponding to associated MSISDNs and IMSIs, irrespective of IMSI active in the SIM.
As described above, subscriber 106 is able to have both IMSI-H and IMSI-V active, in order to make and receive calls and other VAS on the corresponding MSISDNs. However, the subscriber is not able to have multiple VPMN MSISDNs active along with HPMN MSISDN. It will be apparent to a person skilled in the art that in order to provide such facility to the subscriber, the association process described in conjunction with
In one embodiment of the invention, SG 108 maintains a database of the association between IMSI-H, MSISDN-H and IMSI-V and MSISDN-V. Hence, subscriber 106 gets the benefit of local rate calling even when he is in VPMN 104, as his VPMN SIM and IMSI are associated with HPMN SIM and IMSI. Subscriber 106 is able to make and receive calls and messages in VPMN 104 as a local VPMN subscriber. As an exemplary case, Mobile Originated (MO) SMS from subscriber 106 with VPMN SIM in VPMN network is treated as a local subscriber. Hence, SMSC-V 132 is used and caller identification while sending the SMS is MSISDN-V instead of MSISDN-H. Similarly, a Mobile Terminated (MT) SMS or call on MSISDN-V, is treated as a local SMS and call in VPMN 104, respectively.
Alternatively, subscriber 106 may wish to use services corresponding to his HPMN profile. The services may include, but may not be limited to, information service, call back service, and profile information change. In such a case, he may use HPMN SIM in VPMN 104, if roaming is supported in his HPMN profile to send a short code message to HPMN SME service.
Usually, when the subscriber sends the SMS to HPMN SME address, the short code for the HPMN SME address is present in the first line of the SMS. For example, +123 is a short code address. When SG 108 receives the forwarded SMS, SG 108 checks in its database for association between IMSI-V and IMSI-H and their corresponding MSISDNs. In accordance with one embodiment of the present invention, at step 316, SG 108 removes this first line and relays the forwarded SMS to SMSC-H 116 by changing the IMSI-V and MSISDN-V, with IMSI-H and MSISDN-H, respectively. In addition, SG 108 also replaces the address of VMSC-V as the address of SG 108. This enables acknowledgment and delivery receipt to SG 108 itself, at step 318. At step 320, SG 108 forwards the received SMS acknowledgement to SMSC-V 132. Thereafter, at step 322, SMSC-V 132 sends a delivery report to subscriber 106's handset. In accordance with another embodiment of the present invention, SG 108 removes the first line of the SMS and delivers the SMS itself, by performing the functions of an SMSC. Hence, in this case, SG 108 itself does the acknowledgment and delivery receipt of the SMS. By doing so, subscriber 106 can send SMS using any of MSISDN-H or MSISDN-V depending on the profile settings.
The HPMN operator can choose to have SMS always going through HPMN 102, instead of SMSC-V 132, as described in
In accordance with one embodiment of the invention, subscriber 106 at VPMN 104 is able to make calls with a caller ID (MSISDN) of his choice.
In addition, subscriber is also able to use VAS, such as GPRS and MMS, using his HPMN or VPMN SIM. MO-GPRS service such as, but may not be limited to, WAP, email and MMS, initiated by the subscriber 106 using a VPMN SIM, are treated as a local subscriber in VPMN 104. In this case, VPMN SGSN and VPMN GGSN will be used. In addition, in all the GPRS signaling exchange, MSISDN-V is displayed. However, if any GPRS service ties with HPMN 102 for security reason or VPMN establishment, then subscriber 106 can use HPMN SIM if roaming is allowed on his HPMN profile. If VPMN 104 is a partner network of HPMN 102, then HPMN 102 assigns a special HPMN APN name to subscriber 106's handset if HPMN's original APN name conflicts with the VPMN APN name.
Generally, SGSN-V 601 first establishes a PDP context with SG 108, which then applies DNS resolution on HPMN APN depending on the profile selection to find the corresponding GGSN-H 605. Thereafter, at step 608, GGSN-H 605 acknowledges the message to SG 108. Thereafter, at step 610, SG 108 relays this acknowledgment to SGSN-V 601, which in turn, relays it to subscriber 106's handset, at step 612. At step 614, subscriber 106 sends a GTP PDU back to SGSN-V 601. SGSN-V 601 relays the GTP PDU to SG 108, at step 616. Finally, at step 618, SG 108 relays the GTP PDU to GGSN-H 605.
The subscriber can also use GPRS service when his VPMN profile is activated. The call flow for such a case would be similar as explained earlier in
As explained earlier, a Mobile Terminated (MT) SMS or call on MSISDN-V, is treated as a local SMS and call in VPMN 104, respectively.
Thereafter, at step 810, HLR-H 112 returns the PRN ACK with R# to GMSC-H 114. Thereafter, at step 812, GMSC-H 114 continues the call on this R# using IAM(A, R#) to a special switch. In various embodiments of the invention, the special switch can be GMSC-H 114 itself or a VoIP platform having a special routing configuration for R#. The VoIP platform is coupled to HPMN 102. Thereafter, the special switch processes the R# to deduce the final destination number in the following two ways: firstly, the special switch removes the prefix to get MSISDN-V and secondly, the special switch passes the call control for R# to SG 108. Furthermore, at step 814, SG 108 requests GMSC-H 114 (i.e. the special switch) to route the call to MSISDN-V, using IAM(A, OCN=MSISDN-H, MSISDN-V). The signaling in this case can be one of, but may not be limited to, ISUP loopback, IN (INAP), non-standard IN, CAP, WIN and SIP. The insertion of OCN=MSISDN-H in IAM message is optional. Finally at step 816, the GMSC-H 114 routes the call to GMSC-V 124 at MSISDN-V.
As mentioned in various embodiments of the invention that local profile is maintained for each network IMSI, i.e. IMSI-H or IMSI-V, or likewise, these IMSIs also have corresponding voicemail forwarding number. In one embodiment of the invention, if only HPMN provides voicemail forwarding, then late forwarded calls on any MSISDN (MSISDN-1), irrespective of the subscriber's current location (MSISDN-V), are forwarded to HPMN Voicemail. MSISDN-1 may correspond to a new VPMN-1 other than VPMN 104. Hence, the called MSISDN-1 and the currently registered network VPMN 104 are not corresponding to the same VPMN. For example, if the subscriber is registered at VPMN-1, and he is not answering a call on his MSISDN-H, the call is routed through the SG to the HPMN voicemail. As another example, if the subscriber is registered at VPMN 1, and he is not answering a call to his VPMN 2 MSISDN, the call is again routed through the SG to the HPMN voicemail. However, if the subscriber is registered at VPMN 1 and he is not answering to a call on his VPMN 1 MSISDN, the call is dropped. Further, it will be apparent to a person skilled in the art, that if the subscriber is at HPMN and he is not answering a call on his HPMN MSISDN, then the call is forwarded to his HPMN voicemail. However, in case only VPMN provides a voicemail forwarding, then late call forwarding on the VPMN MSISDN goes to that voicemail. The call is dropped only when the subscriber is registered at VPMN-1, and does not answer the call on MSISDN-1 corresponding to VPMN-1.
A local SMSC, corresponding to the subscriber's location, notifies whenever a voicemail is left for the subscriber. In another instance, the voicemail for the subscriber may be left at a network that is different from his current registered location. The voicemail notification (MT-SMS) message goes through the SG where the SG checks the message whether the sender is from a voicemail system. If it is, then the SG precedes the voicemail notification with an SMS of its own, which informs the subscriber for the network from which the next voice mail notification comes. Hence, the subscriber is able choose the correct IMSI and profile to check his voicemail.
In an embodiment of the invention, the subscriber dials in to the voicemail system to check his voicemail. In the case of multiple VPMN SIMs approach, since the voicemail number is stored in the SIM, the subscriber can press “1” on the keypad to check the voicemail. In case of multiple IMSI in single SIM approach, in the case of multi-IMSI STK-based SIM approach, the STK application can swap in the corresponding voicemail number on a selected IMSI in the SIM, and the subscriber can still press “1” on the keypad to check the corresponding voice mail.
In an embodiment of the invention, the MT-SMS may not be delivered to subscriber 106's handset because the handset may be switched off, or could be out of coverage area, or the inbox of the handset could be full.
When VMSC-V 128 makes radio contact with subscriber 106's handset when the handset is switched on, or comes in coverage area, or subscriber 106 deletes one or more messages from his inbox, the VMSC-V 128, at step 1102, sends the READY FOR SM message to HLR-V 126 of VPMN 104. At step 1104, HLR-V 128 sends the acknowledgement to VMSC-V 128. Since SG 108 is registered for notification on MSISDN-V, at step 1106, HLR-V 126 sends AlertSC to SG 108. Thereafter, at step 1108, SG 108 sends an AlertSC ACK to HLR-V 128 of MSISDN-V. Thereafter, at step 1110, SG 108 issues a ReadyForSM to HLR-H 112 for IMSI-H. Thereafter, at step 1112, SG 108 receives an acknowledgment for the ReadyForSMS message from HLR-H 112. Hence, at step 1114, HLR-H 112 sends AlertSC to originating SMSC 1001. Finally, at step 1116, originating SMSC 1001 sends back the acknowledgment to AlertSC to start the original SMS re-delivery.
It will be apparent to a person skilled in the art that a call flow similar to MT SMS is applicable for MT-USSD or other supplementary services.
Similar to MT calls and SMS, subscriber is also able to receive GPRS services on his HPMN MSISDN. It will be apparent to a person skilled in the art that MT GPRS services on VPMN MSISDN does not involve SG 108. As explained earlier in conjunction with
It will be apparent to a person skilled in the art that similar to MT GPRS service, the subscriber is also able to receive a MT MMS as his associated MSISDNs. When a MMS is sent to the subscriber's MSISDN-V, it will reach the subscriber's VPMN MMSC. Thereafter, the VPMN MMSC will send out a MMS alert to the MSISDN-V. The MMS is essentially delivered as an SMS (or WAP push over SMS bearer channel) to the subscriber's handset registered with VPMN 104 with a VPMN SIM. However, if the subscriber's handset is configured to have the VPMN-APN, MMSC address and WAP Gateway, he is able to use GPRS network of VPMN 104 and VPMN WAP Gateway to pull the MMS message from the VPMN MMSC. Furthermore, the subscriber can benefit from the local rates of VPMN. However, if the subscriber's handset is configured to have the HPMN APN, MMSC address and WAP Gateway, then the MMS alert acknowledgment fails. Subsequently, the subscriber is prompted to select the VPMN configuration to retrieve the MMS message.
Alternately, when a MMS is sent to the subscriber's MSISDN-H, the MMS message reaches the HPMN MMSC. Thereafter, HPMN MMSC sends out a MMS alert to the MSISDN-H. The MMS is delivered as an SMS (or WAP push over SMS bearer channel) to the subscriber's handset. However, if the subscriber's handset is configured to have the HPMN APN, MMSC address and WAP Gateway, then the subscriber's handset will be able to use the VPMN GPRS Roaming and HPMN WAP Gateway to pull the MMS message from the HPMN MMSC. However, if the subscriber's handset is configured to have the VPMN APN, MMSC address and WAP Gateway, then the MMS alert acknowledgment fails. Subsequently, the subscriber is prompted to select the HPMN configuration to retrieve the MMS message.
In an alternate embodiment, SG 108 uses MM3 or MM7 interface to set MMS forwarding from MSISDN-H to MSISDN-V. Hence, MMS sent to the MMSC corresponding to MSISDN-H is forwarded to the MMSC corresponding to MSISDN-V via MM4 interface, like MMS inter-working. However, there may be an instance when an MMS is sent to a non-registered (associated) MSISDN of the subscriber.
Similar to forwarding the MMS at an un-registered VPMN MSISDN-V1 to a registered VPMN MSISDN-V, MT calls can also be forwarded to the subscriber's current location.
Subsequently, the MT call to MSISDN-V1 is finally routed over the special MSRN R# and reaches GMSC-H 114, at step 1612, as an IAM (A,R#) message. At step 1614, GMSC-H 114 passes the call control using a message such as, but not limited to, IDP (A, R#), to SG 108 via ISUP loopback or an IN trigger. Thereafter, at step 1616, SG 108 swaps in the MSISDN-V with R#, and modifies the caller ID by a suffix or prefix via ISUP loopback or IN Connect such as CON(CC-1+A, MSISDN-V). In an embodiment of the invention, the suffix or prefix is the country code CC-1 corresponding to MSISDN-V1 obtained from the mapping. Finally, at step 1618, GMSC-H 114 initiates the call setup using IAM(CC-1+A, MSISDN-V) to GMSC-V 124. In another embodiment of the invention, caller ID of A is left unchanged, but the called number is sent as out-of-band message such as, but may not be limited to, an SMS, a GPRS push message and instant messaging. However, in such a case, the call is temporarily suspended until the out-of-band SMS is delivered, or timed out, or an error is received.
Other supplementary services like ODB and call barring are also managed, based on local profiles. For example, the subscriber can define, via SS MMI or customer care, to set call barring, call forwarding, or any other SS. This is done like a local subscriber when the subscriber is registered at the VPMN network with the VPMN IMSI, or roaming with the VPMN IMSI/SIM at any other network (VPMN or HPMN). Hence, SS values of different IMSI profiles are independent of each other. For example, if the subscriber sets incoming call barring at the HPMN HLR, when registered at a VPMN with his VPMN IMSI, the incoming call to his VPMN MSISDN may not be barred. Similar is the case for roaming services. As another example, if the subscriber bars his incoming or outgoing calls while roaming at the HPMN HLR, when registered at the VPMN with his VPMN IMSI/SIM, the MO and MT calls to his VPMN MSISDN may not be barred.
Since the local operator providing the service defines ODB, it is tied to an IMSI profile at a network, and is independent of the ODB situation of another IMSI profile at another network. For example, in order to bar an incoming call at a particular MSISDN (HPMN or VPMN), when the subscriber is registered at any other network, with the VPMN IMSI, the subscriber can use the SS call barring of incoming call with the HPMN IMSI registered at the VPMN as a roamer. Alternatively, the subscriber can do the same while he is registers the HPMN with the HPMN IMSI, before he registers with the VPMN network. Any change in the profile subscription of HPMN, by different VPMN networks, requires coordination between the HPMN and the other networks. In one embodiment of the invention, the SG may have OMAP interfaces with each VPMN network to perform the coordination.
As regards the billing for the calls and other VAS of the subscriber, if the HPMN SIM is used, normal roaming billing process applies. However, if a prepaid VPMN SIM is used, the VPMN bills the subscriber via its local prepaid system. The subscriber then pays for the prepaid SIM or recharges the credit in SIM at HPMN or VPMN. Moreover, if a postpaid VPMN SIM is used, the VPMN sends the bill to the HPMN operator, who then bills the subscriber.
It will be apparent to a person skilled in the art, that the MIMM services can also be applied to CDMA/ANSI-41D, and other technologies such as, but may not be limited to, VoIP, WiFi, 2G, 3G, and inter-standard roaming. For example, a CDMA roaming subscriber traveling with a VPMN CDMA handset. Another example is a CDMA roaming subscriber travelling with a VPMN GSM SIM and a GSM handset. Yet another example is a GSM roaming subscriber traveling with a VPMN CDMA RUIM and a CDMA handset. To support these variations, the SG 108 will have a SS7 and network interface corresponding to the VPMN network as well as a SS7 and network interface corresponding to the HPMN network. It would be obvious to a person skilled in the art, that these two interfaces in different directions may not have to be the same technologies. In addition, there could be multiple types of interfaces in both directions.
An exemplary list of the mapping between GSM MAP and ANSI41D is described in the table below as a reference.
In
The STP of the CDMA operator redirects the SMS to the Roaming Gateway. The Roaming Gateway then registers its own location as the subscriber's location to the CDMA HLR.
The present invention can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment containing both hardware and software elements. In accordance with an embodiment of the present invention, software, including but not limited to, firmware, resident software, and microcode, implements the invention.
Furthermore, the invention can take the form of a computer program product, accessible from a computer-usable or computer-readable medium providing program code for use by, or in connection with, a computer or any instruction execution system. For the purposes of this description, a computer-usable or computer readable medium can be any apparatus that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.
The medium can be an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system (or apparatus or device) or a propagation medium. Examples of a computer-readable medium include a semiconductor or solid state memory, magnetic tape, a removable computer diskette, a random access memory (RAM), a read-only memory (ROM), a rigid magnetic disk and an optical disk. Current examples of optical disks include compact disk-read only memory (CDROM), compact disk-read/write (CD-R/W) and Digital Versatile Disk (DVD).
An operator uses the MIMM system to serve subscribers, associated with its network, even when they are not in the coverage of home network and are in VPMN networks. The MIMM system facilitates such subscriber to use local rate dialing benefits even when they are in VPMN networks. The MIMM system provides multiple MSISDNs in either a single SIM or multiple VPMN SIMs. The subscriber may use his existing HPMN SIM and can avail the benefit of local rates when he is in VPMN, by using his VPMN MSISDN. Alternatively, the subscriber may use multiple VPMN SIMs, each having its corresponding MSISDN, so as to enable local rate dialing. In addition, the subscriber can use services corresponding to the local profile in the SIM/IMSI. The MIMM system facilitates subscribers to use call related and value added services at any of the associated MSISDNs. The subscriber can receive calls at his HPMN MSISDN, as well as at his VPMN MSISDN, irrespective of his current location. Furthermore, the subscriber can indicate his desired MSISDN in CLI, when initiating any call or a VAS from the HPMN or VPMN. The MIMM system caters to both post-paid and pre-paid subscribers. Moreover, the MIMM system also facilitates the subscriber to make or receive any call or VAS message at any of his associated MSISDNs, by forwarding the call or VAS message from the number at which it is received, to his desired associated MSISDN.
The components of MIMM system described above include any combination of computing components and devices operating together. The components of the MIMM system can also be components or subsystems within a larger computer system or network. The MIMM system components can also be coupled with any number of other components (not shown), such as other buses, controllers, memory devices, and data input/output devices, in any number of combinations. In addition, any number or combination of other processor-based components may be carrying out the functions of the MIMM system.
It should be noted that the various components disclosed herein may be described using computer aided design tools and/or expressed (or represented), as data and/or instructions embodied in various computer-readable media, in terms of their behavioral, register transfer, logic component, transistor, layout geometries, and/or other characteristics. Computer-readable media in which such formatted data and/or instructions may be embodied include, but are not limited to, non-volatile storage media in various forms (e.g., optical, magnetic or semiconductor storage media) and carrier waves that may be used to transfer such formatted data and/or instructions through wireless, optical, or wired signaling media or any combination thereof.
Unless the context clearly requires otherwise, throughout the description and the claims, the words “comprise,” “comprising,” and the like are to be construed in an inclusive sense as opposed to an exclusive or exhaustive sense; that is to say, in a sense of “including, but may not be limited to.” Words using the singular or plural number also include the plural or singular number respectively. Additionally, the words “herein,”“hereunder,” “above,” “below,” and words of similar import refer to this application as a whole and not to any particular portions of this application. When the word “or” is used in reference to a list of two or more items, it covers all of the following interpretations: any of the items in the list, all of the items in the list and any combination of the items in the list.
The above description of illustrated embodiments of the MIMM system is not intended to be exhaustive or to limit the MIMM system to the precise form disclosed. While specific embodiments of, and examples for, the MIMM system are described herein for illustrative purposes, various equivalent modifications are possible within the scope of the MIMM system, as those skilled in the art will recognize. The teachings of the MIMM system provided herein can be applied to other processing systems and methods. They may not be limited to the systems and methods described above.
The elements and acts of the various embodiments described above can be combined to provide further embodiments. These and other changes can be made in light of the above detailed description.
Other Variations
In describing certain embodiments of the MIMM system under the present invention, this specification follows the path of a telecommunications call, from a calling party to a called party. For the avoidance of doubt, that call can be for a normal voice call, in which the subscriber telecommunications equipment is also capable of visual, audiovisual or motion-picture display. Alternatively, those devices or calls can be for text, video, pictures or other communicated data.
In the foregoing specification, specific embodiments of the present invention have been described. However, one of ordinary skill in the art will appreciate that various modifications and changes can be made without departing from the scope of the present invention as set forth in the claims below. Accordingly, the specification and figures are to be regarded in an illustrative rather than a restrictive sense, and all such modifications are intended to be included within the scope of present invention. The benefits, advantages, solutions to problems, and any element(s) that may cause any benefit, advantage, or solution to occur or become more pronounced are not to be construed as a critical, required, or essential features or elements of any or all the claims.
Appendix
Technical References (each of which is incorporated by reference in its entirety)
This application is a continuation-in-part of U.S. patent application Ser. No. 11/699,505, entitled “Method and System for Keeping All Phone Numbers Active While Roaming with Diverse Operator Subscriber Identity Modules,” filed on Jan. 30, 2007, claiming priority from Jan. 30, 2006. This application is also a continuation-in-part of U.S. patent application Ser. No. 10/782,681, entitled “Providing Multiple MSISDN in a Single SIM for multiple roaming partners”, filed on Feb. 18, 2004, claiming priority from Feb. 18, 2003, and U.S. patent application Ser. No. 10/918,645, entitled “Signaling Gateway with Multiple IMSI with Multiple/Single MSISDN (MIMM/MSIM) Service in a Single SIM for Multiple Roaming Partners”, filed on Aug. 13, 2004, claiming priority from Aug. 13, 2003. This application is also related to U.S. patent application Ser. No. 10/778,861, entitled “Signaling and Packet Relay Including General Packet Radio Services (“GPRS”),” filed Feb. 13, 2004. The aforementioned patent applications are incorporated herein by this reference in their entireties.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5353328 | Jokimies | Oct 1994 | A |
| 5586166 | Turban | Dec 1996 | A |
| 5742910 | Gallant et al. | Apr 1998 | A |
| 5764730 | Rabe et al. | Jun 1998 | A |
| 5818824 | Lu et al. | Oct 1998 | A |
| 5854982 | Chambers et al. | Dec 1998 | A |
| 5901359 | Malmstrom | May 1999 | A |
| 5903832 | Seppanen et al. | May 1999 | A |
| 5924035 | Joensuu | Jul 1999 | A |
| 5930701 | Skog | Jul 1999 | A |
| 5940490 | Foster et al. | Aug 1999 | A |
| 5943620 | Boltz et al. | Aug 1999 | A |
| 5953653 | Josenhans et al. | Sep 1999 | A |
| 5987318 | Alperovich et al. | Nov 1999 | A |
| 5987323 | Huotori | Nov 1999 | A |
| 5987325 | Tayloe | Nov 1999 | A |
| 6014561 | Molne | Jan 2000 | A |
| 6052604 | Bishop et al. | Apr 2000 | A |
| 6058309 | Huang et al. | May 2000 | A |
| 6075855 | Christiansen et al. | Jun 2000 | A |
| 6085084 | Christmas | Jul 2000 | A |
| 6138005 | Park | Oct 2000 | A |
| 6138009 | Birgerson | Oct 2000 | A |
| 6148197 | Bridges et al. | Nov 2000 | A |
| 6163701 | Saleh et al. | Dec 2000 | A |
| 6185295 | Frederiksen et al. | Feb 2001 | B1 |
| 6185436 | Vu | Feb 2001 | B1 |
| 6192255 | Lewis et al. | Feb 2001 | B1 |
| 6195532 | Bamburak et al. | Feb 2001 | B1 |
| 6208864 | Agrawal et al. | Mar 2001 | B1 |
| 6212372 | Julin | Apr 2001 | B1 |
| 6356755 | Valentine et al. | Mar 2002 | B1 |
| 6356756 | Koster | Mar 2002 | B1 |
| 6456845 | Drum et al. | Sep 2002 | B1 |
| 6456859 | Desblancs et al. | Sep 2002 | B1 |
| 6463298 | Sorenson et al. | Oct 2002 | B1 |
| 6466786 | Wallenius | Oct 2002 | B1 |
| 6505050 | Brudos et al. | Jan 2003 | B1 |
| 6515974 | Inoue et al. | Feb 2003 | B1 |
| 6574481 | Rathnasabapathy et al. | Jun 2003 | B1 |
| 6603761 | Wang et al. | Aug 2003 | B1 |
| 6603968 | Anvekar et al. | Aug 2003 | B2 |
| 6611516 | Pirkola et al. | Aug 2003 | B1 |
| 6628934 | Rosenberg et al. | Sep 2003 | B2 |
| 6636502 | Lager et al. | Oct 2003 | B1 |
| 6671523 | Niepel et al. | Dec 2003 | B1 |
| 6684073 | Joss et al. | Jan 2004 | B1 |
| 6693586 | Walters et al. | Feb 2004 | B1 |
| 6738622 | Stadelmann et al. | May 2004 | B1 |
| 6738636 | Lielbridis | May 2004 | B2 |
| 6764003 | Martshitsch et al. | Jul 2004 | B1 |
| 6782264 | Anderson | Aug 2004 | B2 |
| 6795444 | Vo et al. | Sep 2004 | B1 |
| 6856818 | Ford | Feb 2005 | B1 |
| 6876860 | Berg et al. | Apr 2005 | B1 |
| 6920487 | Sofer et al. | Jul 2005 | B2 |
| 6925299 | Sofer et al. | Aug 2005 | B1 |
| 6961559 | Chow et al. | Nov 2005 | B1 |
| 6963543 | Diep et al. | Nov 2005 | B2 |
| 6968383 | Heutschi et al. | Nov 2005 | B1 |
| 6975852 | Sofer et al. | Dec 2005 | B1 |
| 6978156 | Papadopoulos et al. | Dec 2005 | B1 |
| 7020479 | Martschitsch | Mar 2006 | B2 |
| 7031704 | Di Claudio et al. | Apr 2006 | B2 |
| 7139570 | Elkarat et al. | Nov 2006 | B2 |
| 7184764 | Raviv et al. | Feb 2007 | B2 |
| 7231431 | Sofer et al. | Jun 2007 | B2 |
| 7372860 | Haumont | May 2008 | B1 |
| 20020009199 | Ala-Laurila et al. | Jan 2002 | A1 |
| 20020012351 | Sofer et al. | Jan 2002 | A1 |
| 20020037708 | McCann et al. | Mar 2002 | A1 |
| 20020061745 | Ahn et al. | May 2002 | A1 |
| 20020087631 | Sharma | Jul 2002 | A1 |
| 20020101858 | Stuart et al. | Aug 2002 | A1 |
| 20020101859 | Maclean | Aug 2002 | A1 |
| 20020160763 | Mittal et al. | Oct 2002 | A1 |
| 20020187780 | Souissi | Dec 2002 | A1 |
| 20020191575 | Kalavade et al. | Dec 2002 | A1 |
| 20020196775 | Tuohino et al. | Dec 2002 | A1 |
| 20020197991 | Anvekar et al. | Dec 2002 | A1 |
| 20030017843 | Noblins | Jan 2003 | A1 |
| 20030050047 | Ala-Luukko | Mar 2003 | A1 |
| 20030051041 | Kalavade et al. | Mar 2003 | A1 |
| 20030064723 | Thakker | Apr 2003 | A1 |
| 20030069922 | Arunachalam | Apr 2003 | A1 |
| 20030129991 | Allison et al. | Jul 2003 | A1 |
| 20030133421 | Sundar et al. | Jul 2003 | A1 |
| 20030139180 | McIntosh et al. | Jul 2003 | A1 |
| 20030157938 | Haase et al. | Aug 2003 | A1 |
| 20030165135 | Itzkovitz et al. | Sep 2003 | A1 |
| 20030208560 | Inoue | Nov 2003 | A1 |
| 20030224795 | Wilhoite et al. | Dec 2003 | A1 |
| 20030229791 | De Jong | Dec 2003 | A1 |
| 20040019539 | Raman et al. | Jan 2004 | A1 |
| 20040053610 | Kim | Mar 2004 | A1 |
| 20040082346 | Skytt et al. | Apr 2004 | A1 |
| 20040087305 | Jiang | May 2004 | A1 |
| 20040120552 | Borngraber et al. | Jun 2004 | A1 |
| 20040131023 | Auterinen | Jul 2004 | A1 |
| 20040132449 | Kowarch | Jul 2004 | A1 |
| 20040148400 | Mostafa | Jul 2004 | A1 |
| 20040196858 | Tsai et al. | Oct 2004 | A1 |
| 20040224680 | Jiang | Nov 2004 | A1 |
| 20040229601 | Zabawskyj et al. | Nov 2004 | A1 |
| 20040236836 | Appleman | Nov 2004 | A1 |
| 20050021834 | Coulombe | Jan 2005 | A1 |
| 20050047378 | Wuschke et al. | Mar 2005 | A1 |
| 20050064883 | Heck et al. | Mar 2005 | A1 |
| 20050070278 | Jiang | Mar 2005 | A1 |
| 20050130654 | Di Claudio et al. | Jun 2005 | A1 |
| 20050186939 | Barnea et al. | Aug 2005 | A1 |
| 20050186960 | Jiang | Aug 2005 | A1 |
| 20050186979 | McCann et al. | Aug 2005 | A1 |
| 20050192007 | Kumar et al. | Sep 2005 | A1 |
| 20050192035 | Jiang | Sep 2005 | A1 |
| 20050215250 | Chava et al. | Sep 2005 | A1 |
| 20050232282 | Silver et al. | Oct 2005 | A1 |
| 20050250493 | Elkarat et al. | Nov 2005 | A1 |
| 20060003775 | Bull et al. | Jan 2006 | A1 |
| 20060009204 | Ophir | Jan 2006 | A1 |
| 20060025129 | Wolfman et al. | Feb 2006 | A1 |
| 20060052113 | Ophir et al. | Mar 2006 | A1 |
| 20060068778 | Della-Torre | Mar 2006 | A1 |
| 20060068786 | Florence | Mar 2006 | A1 |
| 20060079225 | Wolfman et al. | Apr 2006 | A1 |
| 20060079236 | Del Pino et al. | Apr 2006 | A1 |
| 20060148459 | Wolfman et al. | Jul 2006 | A1 |
| 20060205404 | Gonen et al. | Sep 2006 | A1 |
| 20060211420 | Ophir et al. | Sep 2006 | A1 |
| 20070021118 | Ophir et al. | Jan 2007 | A1 |
| 20070049269 | Ophir et al. | Mar 2007 | A1 |
| 20070054665 | Elkarat et al. | Mar 2007 | A1 |
| 20070072587 | Della-Torre et al. | Mar 2007 | A1 |
| 20070178885 | Lev et al. | Aug 2007 | A1 |
| 20070232300 | Wolfman | Oct 2007 | A1 |
| 20070259663 | Weintraub et al. | Nov 2007 | A1 |
| 20080020760 | Elkarat et al. | Jan 2008 | A1 |
| 20090122759 | Kumar et al. | May 2009 | A1 |
| Number | Date | Country |
|---|---|---|
| 199940379 | Jan 2000 | AU |
| 2281041 | Feb 2001 | CA |
| 0899 974 | Mar 1999 | EP |
| 2322998 | Sep 1998 | GB |
| 2379135 | Feb 2003 | GB |
| WO 9826621 | Jun 1998 | WO |
| WO 9826626 | Jun 1998 | WO |
| WO 0001179 | Jan 2000 | WO |
| WO 0018156 | Mar 2000 | WO |
| WO 0051375 | Aug 2000 | WO |
| WO 0079761 | Dec 2000 | WO |
| WO 0079825 | Dec 2000 | WO |
| WO 0122750 | Mar 2001 | WO |
| WO 0165884 | Sep 2001 | WO |
| WO 0241641 | May 2002 | WO |
| WO 02019667 | Jul 2002 | WO |
| 03019969 | Mar 2003 | WO |
| WO 03019960 | Mar 2003 | WO |
| WO 03043367 | May 2003 | WO |
| WO 03065660 | Aug 2003 | WO |
| WO2004075598 | Sep 2004 | WO |
| WO 2004081802 | Sep 2004 | WO |
| WO2005101857 | Oct 2005 | WO |
| WO2008012815 | Jan 2008 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 20070213050 A1 | Sep 2007 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60762893 | Jan 2006 | US | |
| 60447998 | Feb 2003 | US | |
| 60495202 | Aug 2003 | US | |
| 60447533 | Feb 2003 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 11699505 | Jan 2007 | US |
| Child | 11700964 | US | |
| Parent | 10782681 | Feb 2004 | US |
| Child | 11699505 | US | |
| Parent | 10918645 | Aug 2004 | US |
| Child | 10782681 | US | |
| Parent | 10778861 | Feb 2004 | US |
| Child | 10918645 | US |
