US20120214459A1 - Method for routing incoming communications in a communications network - Google Patents
Method for routing incoming communications in a communications network Download PDFInfo
- Publication number
- US20120214459A1 US20120214459A1 US13/461,330 US201213461330A US2012214459A1 US 20120214459 A1 US20120214459 A1 US 20120214459A1 US 201213461330 A US201213461330 A US 201213461330A US 2012214459 A1 US2012214459 A1 US 2012214459A1
- Authority
- US
- United States
- Prior art keywords
- communications
- communications device
- sim
- message
- incoming communication
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/15—Setup of multiple wireless link connections
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/60—Context-dependent security
- H04W12/69—Identity-dependent
- H04W12/72—Subscriber identity
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/16—Communication-related supplementary services, e.g. call-transfer or call-hold
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
- H04W8/04—Registration at HLR or HSS [Home Subscriber Server]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/26—Network addressing or numbering for mobility support
Definitions
- the present invention relates generally to telecommunication network implementations; and in particular to a method and system for routing incoming communications in a communications network.
- the method and system allowing for one mobile phone number (MSISDN) to be associated with a plurality of wireless devices (Multi-SIM) described herein provides the requisite art for a wireless subscriber to present/utilize one phone number (Mobile Station Integrated Services Digital Network (MSISDN) Number) across a plurality of wireless devices (and their inherent, requisite SIMs (Subscriber Identity Modules)).
- MSISDN Mobile Station Integrated Services Digital Network
- SIMs Subscriber Identity Modules
- the invention of present seeking the protection of Letters Patent enables multiple independent SIMs (e.g. with individual IMSIs (International Mobile Station Identifiers)) to utilize the same phone number (MSISDN) for the purpose of providing telephony services via a macroscopic (GSM) carrier.
- GSM macroscopic
- MSISDN common phone number
- the mobile subscriber in question may choose which wireless device (and its associated SIM) s/he wishes to receive telecommunications upon in the preferred embodiment.
- various non-limiting manifestations of the invention may optionally direct Voice, SMS (Short Message Services), MMS (Multi-Media Message Services), MWI (Message Waiting Indicator) services towards different wireless devices and their associated SIMs.
- Optional manifestations of the invention limits the number of simultaneous telecommunications activity which emanate from the plurality of devices associated with the Multi-SIM service.
- Further optional manifestations of the invention permits the automated redirection of telecommunications services (e.g. call delivery and location retrieval) based on a pre-configured settings or the detection of activity from the plurality of wireless device or active polling to determine the status of the plurality of wireless devices.
- FIG. 1 illustrates a typical, non-limiting embodiment of the system level architecture employed in the disclosure of present
- FIG. 1A details a non-limiting call-flow of the subscriber registration sequence for mobile originated voice telecommunications of the method and system allowing for one mobile phone number (MSISDN) to be associated with a plurality of wireless devices.
- MSISDN mobile phone number
- FIG. 1B represents a non-limiting call-flow detailing the means through which mobile terminating SMS or MMS traffic is managed by the method and system allowing for one mobile phone number (MSISDN) to be associated with a plurality of wireless devices.
- MSISDN mobile phone number
- FIG. 1C represents a non-limiting call-flow detailing the means through which the location of a mobile station may be retrieved.
- FIG. 1D represents a non-limiting call-flow detailing the means through which an indication of the unsuccessful nature of a SMS delivery attempt will be relayed to a SMS-C.
- FIG. 1D also represents a non-limiting call-flow detailing the means through which the unavailability of a given mobile station may be provided to a given SMSC for subsequent SMS delivery attempts.
- FIG. 1E represents a non-limiting call-flow detailing the means through which an indication of availability (for the purpose of receiving Short Messages) may be relayed to a SMS-C.
- FIG. 1F represents a non-limiting call-flow detailing the means through which unstructured supplementary service (USSD) message handling is accommodated.
- USSD unstructured supplementary service
- FIG. 1G represents a non-limiting call-flow detailing the means through which supplementary service message handling is accommodated.
- FIG. 1H represents a non-limiting call-flow detailing the means through which call delivery to a wireless device is accommodated.
- the essential logic 70 B for the method and system allowing for one mobile phone number (MSISDN) to be associated with a plurality of wireless devices (‘Multi-SIM’) 70 provides the core Mobile Application Part (MAP) intercept function 70 A establishing devices against the Multi-SIM Mobile Station Integrated Services Digital Network (MSISDN) in the network such that outgoing traffic is seen to originate from the Multi-SIM MSISDN.
- the Multi-SIM computer program product 70 also intercepts incoming traffic to the Multi-SIM MSISDN and directs it to the nominated primary device ( 1 A, 1 B, 1 C as applicable) for that traffic type. Practitioners and other honorable members skilled in the art will recognize that the primary device need not be bound to one (1) of three (3) selections and may exceed such limitations to the state of the art.
- MAP messages which will ordinarily be encountered by the Multi-SIM method and system include the messages, including the various parametric attributes, as prescribed in the GSM TS 09.02, ETSI TS 100 974, and 3GPP TS 29.002 Mobile Application Part (MAP) specifications as amended from time to time.
- Wireless subscribers who obtain the high-level service delineated herein from their respective telecommunications carriers and/or network operators will have a defined number of devices ( 1 A, 1 B, 1 C and so forth); each device is provisioned in the HLR (Home Location Register) 50 and in the Multi-SIM database 70 C.
- An individual MSISDN is associated with each device ( 1 A, 1 B, 1 C) in the HLR 50 but is not used outside of the HLR 50 and Multi-SIM inventions 70 .
- FIGS. 1A , 1 B, 1 C, 1 D, 1 E, 1 F, 1 G, and 1 H have been included as variants of FIG. 1 to ease and facilitate the instruction of the art, and should be interpreted as aiding and helping to achieve such ends.
- the labels of FIG. 1 are therefore incorporated by reference.
- the mobile and/or wireless device ( 1 A, 1 B, 1 C) (among others and as applicable), is activated (‘turned on’).
- a given wireless device After a given wireless device completes any programmed self-check procedure, it will initiate the registration sequence via the applicable air-interface as well as the serving MSCNLR 30 A per steps 100 A.
- the serving MSCNLR 30 A as per the usual operational processes of a GSM network, normally forwards the MAP Update Location message to the HLR 50 associated with the IMSI‘x’ of the mobile device's SIM.
- the MAP Update Location message will instead be forwarded to the Multi-SIM invention 70 at step IOOB.
- the Multi-SIM invention 70 will appear as a defacto HLR for IMSI‘x’ from the perspective of the serving MSCNLR 30 A.
- the Multi-SIM invention 70 After receiving the MAP Update Location message, the Multi-SIM invention 70 will store the addressing information of the MSC/VLR 30 A associated with IMSI‘x’. The Multi-SIM invention will also retrieve the address of the HLR 50 associated with IMSI‘x’ and forward the MAP Update Location message to the appropriate HLR 50 via the SS7 network at step 100 C. An optional manifestation of the Multi-SIM invention 70 will initiate a MAP version negotiation sequence (not shown) as described in GSM 09.02 (and similar specifications) if the MAP version number of the received message at step IOOB is greater than that currently supported by the HLR 50 associated with IMSI‘x’.
- the HLR 50 utilizes received VLR and MSC addressing information in the MAP layer of the Update Location message to invoke service screening criteria as defined by GSM specifications. For example, a VLR or MSC address associated with a given service provider's ‘home’ network may be accorded different service attributes relative to the VLR and MSC associated with a ‘foreign’ network. To that end, an optional manifestation of the invention will map the VLR and MSC addressing information received in the MAP layer of the Update Location message to a predefined subset of alternative VLR and MSC addresses in order to invoke an appropriate set of service attributes for the subscribers associated with the Multi-SIM service. Those skilled in the art will recognize that for the aforementioned optional manifestation of the invention that the HLR 50 will have to be configured (typically via translation tables) to apply a specific set of service attributes given the predefined subset of alternative VLR and MSC addresses.
- the HLR 50 will retrieve the subscriber's profile using IMSI‘x’ as the index key using established processes commonly implemented by HLR vendors.
- the subscriber's profile will include, among other subscribed service attributes, the MSISDN‘x’ associated with IMSI‘x’.
- the HLR 50 will in turn initiate a MAP Insert Subscriber Data sequence, containing the subscribed attributes associated with the subscriber's profile and MSISDN‘x’, which will be forwarded to the Multi-SIM invention 70 via the SS7 network at step IIOA.
- the HLR 50 will direct the MAP Insert Subscriber Data sequence to the Multi-SIM invention 70 via the SS7 network by virtue of the received MTP and SCCP addressing information received at step IOOC.
- the MAP Insert Subscriber Data message is received from the HLR 50 by the art of the Multi-SIM invention 70 (specifically 70 A) at IIOA.
- the Primary MSISDN is retrieved (not shown) from an internal database/table 70 C (via 70 B).
- An optional manifestation of the invention will store the status of the wireless device associated with IMSI‘x’ in the application memory or internal database 70 C for the purpose of applying optional routing procedures for outgoing and incoming as noted in a subsequent portion of this disclosure.
- Yet another optional manifestation of the invention will store selected attributes associated with Intelligent Network (IN) services in application memory or internal database 70 C.
- IMSI‘x’ Intelligent Network
- the Multi-SIM invention 70 will generate an MAP Insert Subscriber Data message where the MSISDN‘x’ received from the HLR 50 will be replaced by the Public MSISDN retrieved from the Multi-SIM internal database 70 C.
- the Multi-SIM invention 70 will forward the MAP Insert Subscriber Data message to the serving MSCNLR 30 A via the SS7 network at step IIOB.
- a characteristic of the invention is that the MAP Insert Subscriber Data received by a MSCNLR 30 A always contains the Public MSISDN regardless of which IMSI‘x’ (and corresponding SIM and wireless device) was activated.
- the serving MSCNLR 30 A processes the information received via the MAP Insert Subscriber Data message received at step IIOB
- the serving MSCNLR 30 A generates and forwards a MAP Insert Subscriber Data acknowledgement message to the Multi-SIM invention 70 at step 120 A.
- the Multi-SIM invention 70 will forward a MAP Insert Subscriber Data acknowledgement message to the HLR 50 modifying the MTP, SCCP, TCAP, and MAP layers of the message relative to that received at step 120 A as required.
- the Primary MSISDN will be replaced by MSISDN‘x’.
- the HLR 50 will receive the MAP Insert Subscriber Data message and generate an MAP Update Location acknowledgement message using established processes commonly implemented by HLR vendors.
- the HLR 50 will forward the MAP Update Location acknowledgement message to the Multi-SIM invention at step 130 A.
- the serving MSCNLR 30 A will receive the MAP Update Location acknowledgement message and initiate an appropriate confirmation message to the wireless device I‘x’ at step 130 B.
- the serving MSCNLR will complete the registration sequence with the mobile station.
- a mobile originated call may then be established at step 140 A.
- the MSCNLR 30 A will initiate a call to the intended destination address via the Public Switched Telephone Network (PSTN) using the procedures prescribed using the ISDN User Part (ISUP) protocol at step 140 B.
- PSTN Public Switched Telephone Network
- ISUP ISDN User Part
- a characteristic of the disclosed invention is that the Calling Party Number information associated with the call establishment procedure will be set to the primary MSISDN forwarded to the serving MSCNLR 30 A by the Multi-SIM invention 70 at step IIOB.
- GPRS General Packet Radio Service
- a characteristic of the disclosed invention is that the Primary MSISDN identifier will be associated with a given IMSI‘x’ for the PDP (Packet Data Protocol) Context Activation establishment procedure.
- PDP Packet Data Protocol
- an optional manifestation of the Multi-SIM invention 70 may selectively screen outgoing call attempts by utilizing procedures associated with IN services.
- an IN message e.g. CAMEL INITIAL_DP
- the Multi-SIM invention 70 may invoke screening criteria based on the destination and source address information contained in the IN message.
- the Multi-SIM invention 70 may also invoke incremental screening criteria based on the state of a given mobile device (associated with IMSI‘x’) as stored in the Multi-SIM invention database 70 C (not shown).
- the Multi-SIM invention 70 may use screening criteria to limit the number of simultaneous calls or to redirect calls to an alternative destination address.
- the Multi-SIM invention 70 will instruct the serving MSCNLR 30 A via an appropriate IN message (e.g. CAMEL CONTINUE or CAMEL CONNECT or CAMEL CANCEL) as to the appropriate course of action based on the screening criteria.
- an appropriate IN message e.g. CAMEL CONTINUE or CAMEL CONNECT or CAMEL CANCEL
- the optional manifestation of the Multi-SIM invention 70 will provide functionality commonly associated with a Service Control Point (SCP).
- SCP Service Control Point
- Those skilled in the art will also recognize that there are a variety of IN protocols which are defined by various specifications which serve the similar purposes without diluting the intent and scope of the present invention including those associated with CAMEL and CS-1 (Capability Set 1) as well as derivations thereof.
- Another optional manifestation of the Multi-SIM invention 70 may act as an intermediation gateway between the serving MSCNLR 30 A and
- SMS-C 40 the respective Short Message (SM) stored in SMS-C 40 remains to be delivered.
- SMS-C will generate and forward a MAP SEND-ROUTING-INFO-FOR-SM (SRI for SM) message which will be directed to the Multi-SIM invention.
- SRI for SM MAP SEND-ROUTING-INFO-FOR-SM
- MAP SRI for SM message there are a variety of mechanisms by which the MAP SRI for SM message can be forwarded to the Multi-SIM invention 70 using the inherent capabilities of the SS7 network and the associated translation capabilities of the SMS-C 40 .
- the Multi-SIM invention 70 will appear as a defacto HLR for a given Primary MSISDN from the perspective of the SMS-C 40 .
- the Multi-SIM invention 70 will retrieve the subscriber's service profile using the Primary MSISDN as the index key from an internal database/table 70 C (not shown).
- the service profile will contain, among other attributes, information pertaining to the specific routing preferences for Short Message as well as Multi-Media Messages and Voice-Mail alerts as the case may be.
- the Multi-SIM invention will generate and forward a MAP SRI for SM response message to the SMS-C 40 at step 210 .
- the MAP SRI for SM response message will contain information so that the SMS-C will consider the Multi-SIM invention as the serving MSC for the purpose of Short Message delivery.
- the Network Node Number parameter will contain an identifier which will uniquely identify the Multi-SIM invention as the serving MSC for the purpose of Short Message delivery.
- the MAP SRI for SM response message at step 210 will contain other parameters so that the SMS-C will be able to continue processing the delivery of the Short Message.
- the MAP SRI for SM message will contain an IMSI value which can be selected from the set of IMSI‘x’ associated with the Primary MSISDN or set to a configurable range of values.
- the Multi-SIM invention 70 will appear as a defacto VLR from the perspective of the SMS-C 40 .
- the SMS-C will attempt delivery of the message by generating and forwarding a MAP MT-FORWARD-SHORT-MESSAGE (MT FSM) message to the Multi-SIM invention 70 .
- the Multi-SIM invention will determine the appropriate mobile device (as identified by the IMSI‘x’ associated with a given SIM and mobile device respectively) to receive the Short Message based on a number of factors including the source address contained in the MT FSM message as well as the nature of the message (e.g. short message or alert).
- the Multi-SIM invention 70 may use a variety of techniques in order to determine the appropriate mobile device based on either programmatic methods (for example, the last device that registered may be used to forward all short messages) or based on pre-established criteria as provided by the subscriber (for example, the subscriber may send Short Messages and alert messages to different devices based on the relative capabilities supported on each device).
- the programmatic methods may in turn be affected by the state of each device (e.g. whether a given mobile device is engaged in a call or registered).
- Those skilled in the art will recognize that a variety of techniques may be used in order to determine the destination mobile device without diluting the intent and scope of the present invention.
- a characteristic of the disclosed invention is that telecommunication services can be selectively terminated to the plurality of mobile devices based on a number of programmatic techniques as well as pre-configured routing criteria.
- the Multi-SIM invention will generate and forward a MT FSM to the serving MSC/VLR 30 A associated with the IMSI‘x’ of the selected mobile station, modifying the MTP, SCCP, TCAP, and MAP layers of the message relative to that received at step 230 as required.
- the Multi-SIM invention 70 will appear as a defacto SMS-C from the perspective of the serving MSC/VLR 30 A.
- the short message will be delivered to the mobile station 1 A, 1 B, 1 C (among others and as applicable) associated with IMSI‘x’.
- a MAP MT FSM response message containing an indication of the successful or unsuccessful nature of the delivery attempt will be initiated by the serving MSC/VLR 30 A and forwarded to the Multi-SIM invention 70 .
- the Multi-SIM invention 70 will generate and forward a MT FSM response to the appropriate SMS-C 40 , modifying the MTP, SCCP, TCAP, and MAP layers of the message relative to that received at step 250 as required.
- a Location Client 80 will initiate a location retrieval request via an Application Programming Interface (API) at 300 A which will include a number of parameters including but not limited to the Primary MSISDN and a transaction identifier.
- API Application Programming Interface
- the Location Client may provide a pseudonym which can be correlated to the Primary MSISDN.
- the purpose of the transaction identifier being to uniquely correlate a given request with other messages which may be received asynchronously including, but not limited to, a confirmation response.
- object oriented application programming interfaces e.g. Common Object Request Broker Architecture (CORBA) or Extensible Markup Language (XML) may be used.
- the Gateway Mobile Location Centre (GMLC) 81 will receive the location retrieval request.
- the GMLC 81 will initiate a MAP ANY-TIME-INTERROGATION (ATI) sequence to the Multi-SIM invention 70 .
- ATI MAP ANY-TIME-INTERROGATION
- the Multi-SIM invention 70 will appear as a defacto HLR for IMSI‘x’ from the perspective of the GMLC 81 .
- the functionality of the GMLC is generally defined by a variety of specifications including GSM 03.71 and 3GPP 23.071 as amended from time to time and that modifications to the capabilities of the GMLC as prescribed by the noted specifications does not dilute the intent and scope of the present invention.
- a characteristic of the disclosed invention is that the location of a given mobile terminal can be retrieved without sending messages to the HLR 50 .
- the Multi-SIM invention 70 effectively emulates certain capabilities associated with the HLR for the purpose of retrieving the location associated with a mobile station.
- the Multi-SIM invention 70 will retrieve the subscriber's service profile using the Primary MSISDN as the index key from an internal database/table 70 C (not shown).
- the service profile will contain, among other attributes, information pertaining to the specific preferences for location retrieval, the last known location of the device based on previous location retrieval attempts, as well as the current list of active or registered devices (as identified via the IMSI‘x’ identifier associated with a given SIM and mobile device respectively).
- the Multi-SIM invention 70 will determine the appropriate mobile device (as identified by the IMSI‘x’ associated with a given SIM and mobile device) for the purpose of a location query based on a number of factors including the source address contained in the MAP ATI message.
- the Multi-SIM invention 70 may use a variety of techniques in order to determine the appropriate mobile device for the location query based on either programmatic methods (for example, the last device that registered) or based on pre-established criteria as provided by the subscriber (for example, the subscriber may rank order a number of devices to be located in preferential order).
- the programmatic methods may in turn be affected by the state of each device (e.g. whether a given mobile device is engaged in a call or registered).
- Those skilled in the art will recognize that a variety of techniques may be used in order to determine the mobile device for a location query without diluting the intent and scope of the present invention.
- the Multi-SIM invention 70 will initiate a MAP PROVIDE-SUBSCRIBER-Info (PSI) message towards the appropriate serving MSC/VLR 30 A based on the selected mobile station (which is associated with a given IMSI(x)) modifying the MTP, SCCP, TCAP, and MAP layers of the message relative to that received at step 300 B as required.
- PSI MAP PROVIDE-SUBSCRIBER-Info
- the serving MSC/VLR 30 A will retrieve the location of the mobile station.
- the mechanisms of retrieving the location of the mobile station are generally prescribed by a variety of specifications including GSM 03.71 and 3GPP 23.071 as amended from time to time.
- a MAP PSI response message will be initiated by the serving MSC/VLR 30 A which will contain the location of the mobile terminal.
- the MAP PSI response message will be forwarded to the Multi-SIM invention 70 .
- the Multi-SIM invention 70 will generate and forward a MAP ATI response to the GMLC 81 , modifying the MTP, SCCP, TCAP, and MAP layers of the message relative to that received at step 310 A as required.
- An optional manifestation of the Multi-SIM invention 70 will store the location of mobile station (associated with IMSI‘x’) in the internal database/table 70 C (not shown).
- the GMLC 81 will provide the location information to the Location Client 80 via the API.
- an optional manifestation of the Multi-SIM invention 70 may abbreviate the location retrieval attempt by providing location information associated with previous location attempts. This will effectively result in steps 300 C and 310 A being bypassed.
- the retrieval and provision of stored location information is governed by programmatic control and there are a number of procedures and conditions (for example, time based methods) which may be applied to abbreviate the location retrieval process.
- a SMS delivery report associated with a SMS delivery attempt is to be forwarded to the appropriate SMS-C.
- a MAP MT-FORWARD-SHORT-MESSAGE (MT FSM) response message containing an indication of the unsuccessful nature of the delivery attempt will be initiated by the serving MSC/VLR 30 A and forwarded to the Multi-SIM invention 70 .
- the Multi-SIM invention 70 will appear as a defacto SMS-C from the perspective of the serving MSC/VLR 30 A based on the intermediation of registration and SMS delivery sequences previously described.
- the Multi-SIM invention 70 will generate and forward a MT FSM response to the appropriate SMS-C 40 , modifying the MTP, SCCP, TCAP, and MAP layers of the message relative to that received at step 400 A as required.
- the SMS-C 40 A will initiate a MAP REPORT-SM-DELIVERY-STATUS which will contain a number of parameters including the Primary MSISDN and Service Center address and which will be forwarded to the Multi-SIM invention 70 .
- the Multi-SIM invention 70 will appear as a defacto HLR for a given Primary MSISDN from the perspective of the SMS-C 40 A.
- the Multi-SIM invention 70 will emulate the capabilities associated with a HLR 50 for the purpose of setting and maintaining the Message Waiting Data file for the Primary MSISDN.
- the Message Waiting Data file can be implemented via a variety of mechanisms without diluting the intent and scope of the present invention.
- the Message Waiting Data file can be stored as a multi-element data element in the Multi-SIM database 70 C (as indexed by the Primary MSISDN).
- the intent of the Message Waiting Data file in the HLR is to record the address of SMS-Cs for subsequent notification once a given mobile station is deemed active (registers).
- the Multi-SIM invention 70 will initiate a MAP REPORT-SM-DELIVERY-STATUS response message to the SMS-C 40 A indicating that the SMS-Cs address has been stored.
- the SMS-C 40 A may provide an indication of the unsuccessful delivery attempt to the Message Center 41 A.
- a Message Center 41 B may attempt to deliver a Short Message to the a given subscriber as identified by the Primary MSISDN.
- the SMS-C 40 B will generate and forward a SRI for SM message which will be directed to the Multi-SIM invention 70 .
- Those skilled in the art shall recognize that there are a variety of mechanisms by which the MAP SRI for SM message can be forwarded to the Multi-SIM invention 70 using the inherent capabilities of the SS7 network and the associated translation capabilities of the SMS-C 40 .
- the Multi-SIM invention 70 will retrieve the subscriber's service profile and the Message Waiting Data file using the Primary MSISDN as the index key from an internal database/table 70 C (not shown).
- the service profile will contain, among other attributes, information pertaining to the specific routing preferences for Short Message as well as Multi-Media Messages and Voice-Mail alerts as the case may be.
- the Multi SIM platform 70 will generate and forward a MAP SRI for SM response message to the SMS-C 40 B at step 440 which will indicate that the subscriber is absent (typically by sending the User Error parameter to ‘Absent Subscriber_SM’).
- the SMS-C 40 B will initiate a MAP REPORT-SM-DELIVERY-STATUS which will contain a number of parameters including the Primary MSISDN and Service Center address and which will be forwarded to the Multi SIM platform 70 .
- the Multi-SIM invention 70 will initiate a MAP REPORT-SM-DELIVERY-STATUS response message to the SMS-C 40 B indicating that the SMS-Cs address has been stored.
- FIG. 1E which illustrates the intercept of the MAP READY FOR SM operation generally used by the MSC/VLR 30 A if a subscriber, whose message waiting flag is active in the VLR, has re-established radio contact with the network or has memory available.
- the MSC/VLR 30 A generates MAP READY FOR SM message which is forwarded to the Multi-SIM invention 70 .
- the Multi-SIM invention 70 will appear as a defacto HLR for a given IMSI‘x’ from the perspective of the MSC/VLR 30 A.
- the MAP READY FOR SM message will contain several parameters indicating if the mobile subscriber is present or if the mobile station has memory.
- the Multi-SIM invention will generate and forward a MAP READY FOR SM response message to the MSC/VLR 30 A indicating that the message at step 500 has been received and processed successfully.
- the Multi-SIM invention 70 will retrieve the subscriber's service profile using the IMSI‘x’ as the index key from an internal database/table 70 C (not shown).
- the service profile will contain, among other attributes, information pertaining to the specific routing preferences for Short Message as well as Multi-Media Messages and Voice-Mail alerts as the case may be.
- the service profile will contain the Primary MSISDN associated with IMSI‘x’ which will in turn be used to index the Message Waiting Data elements. Based on the information retrieved, the Multi-SIM invention will determine which SMS-C should be contacted.
- the Multi-SIM invention may use a variety of techniques in order to determine the appropriate SMS-C based on the information contained in the internal database/table 70 C (not shown).
- the Multi-SIM invention may determine that a SMS-C may not be contacted based on the routing preferences prescribed by the subscriber.
- the Multi-SIM invention may determine that several SMS-Cs (not shown) should be contacted.
- the Multi-SIM invention will generate and forward a MAP ALERT-SERVICE-CENTRE (Alert SC) to the selected SMS-C 40 A (or SMS-Cs (not shown)) indicating that a given subscriber (as identified by the Primary MSISDN) is ready to receive Short Messages.
- the SMS-C may alert Message Centers to the effect that a given subscriber may receive Short Messages.
- the SMS-C 40 A will generate and forward a MAP Alert SC response message to the Multi-SIM invention 70 indicating that the MAP Alert SC message was received and processed successfully.
- the SMS-C 40 may initiate the short message delivery mechanisms as described earlier in the text associated with FIG. 1B .
- USSD MAP messages are typically routed to and from the USSD Application via the serving MSC/VLR and HLR using the methods, operations, and protocols specified in GSM 03.90 and GSM 09.02 as amended from time to time.
- An optional manifestation of the invention provides an USSD-based subscriber interface to change default routing preferences of Multi-SIM subscribers.
- the Multi-SIM invention will also permit subscribers and network operators to make configuration changes via a (web-based) provisioning interface.
- a subscriber may invoke an Unstructured Supplementary Service Data (USSD) service by keying in a USSD short code (e.g. *XX#).
- USSD short code e.g. *XX#
- PUSSR USSD Message
- the Multi-SIM invention 70 may recognize that the USSD short code (as provided via the USSD String parameter) matches a prescribed code associated with the invocation of a feature of the Multi-SIM service.
- Example services include modifying the routing behavior of the Multi-SIM service for received voice or messaging traffic or obtaining information pertaining to the current settings of the Multi-SIM invention for the subscriber.
- the Multi-SIM invention initiates a MAP USSD response message.
- the MAP USSD response message may contain text which indicates that the requested feature was invoked successfully or requested information pertaining to the status of the Multi-SIM service.
- the MSC/VLR will relay the information to the mobile station per the processes described in GSM 03.90 and GSM 09.02.
- a USSD message which is not associated with a Multi-SIM service or feature is propagated to the USSD Based Application 90 via the Multi-SIM invention 70 and HLR 50 .
- the Multi-SIM invention modifies the SCCP, TCAP, and MAP layers of the message relative to that received at step 620 A as required.
- the Multi-SIM invention 70 will appear as a defacto HLR for IMSI‘x’ (or the Primary MSISDN) from the perspective of the MSC/VLR 30 —and that the Multi-SIM invention will appear as a defacto MSC/VLR for IMSI‘x’ (or MSISDN‘x’) from the perspective of the HLR 50 .
- steps 630 , 640 A, 640 B an USSD response message initiated from the USSD Based Application 90 and is propagated to the serving MSC/VLR 30 A via the HLR 50 and Multi-SIM invention 70 .
- the Multi-SIM invention modifies the SCCP, TCAP, and MAP layers of the message relative to that received at step 640 A as required.
- the MSC/VLR will relay the information to the mobile station per the processes described in GSM 03.90 and GSM 09.02.
- Supplementary services are typically modified (in order to activate, deactivate, register, erase, or check the status of supplementary services as the case may be) via MAP messages between the MSC and the VLR and between the VLR and the HLR using the methods, operations, and protocols specified in GSM 09.02 as amended from time to time.
- a subscriber may invoke a command via the Man Machine Interface (MMI) of his/her mobile terminal in order to modify a supplementary service. This will invoke a Supplementary Service MAP message (e.g.
- MMI Man Machine Interface
- the Multi-SIM invention 70 will retrieve the subscriber's service profile from an internal database/table 70 C (not shown).
- the service profile will contain, among other attributes, the complete range of terminal information associated with the subscriber—including the entire suite of IMSI‘x’ and MSISDN‘x’ information associated with the subscriber.
- the Multi-SIM invention will propagate the appropriate Supplementary Service MAP message to the HLR(s) 50 associated with a given IMSI‘x’ for each device 1 A, 1 B, 1 C as applicable (in particular, each IMSI‘x’ may be associated with a different HLR). Practitioners skilled in the art will recognize that the number of devices need not be bound to one (1) of three (3) selections and may exceed such limitations to the state of the art.
- the HLR(s) will generate and initiate appropriate Supplementary Service MAP response messages which will be forwarded to the Multi-SIM invention 70 .
- the appropriate Supplementary Service MAP response message will be generated and forwarded to the Serving MSC/VLR 30 A.
- a Supplementary Service MAP response message indicating an unsuccessful attempt will be provided to the serving MSC/VLR 30 A.
- An optional manifestation of the invention may roll-back the settings associated with a given supplementary service by invoking the complementary Supplementary Service command (e.g. a DEACTIVATE_SS message to counter a prior ACTIVATE_SS message) (not shown).
- the optional manifestation of the invention will retrieve the status of a given Supplementary Service setting via the MAP INTERROGATE_SS message (not shown) prior to invoking the subscriber command at steps 710 , 730 , 750 .
- a call will be received by the Gateway MSC 30 C from the PSTN 95 .
- the Gateway MSC 30 C will generate and forward a MAP SEND_ROUTING_INFORMATION (SRI) message to the Multi-SIM invention 70 .
- the Multi-SIM invention 70 will retrieve the subscriber's service profile using the Primary MSISDN as the index key from an internal database/table 70 C (not shown).
- the service profile will contain, among other attributes, information pertaining to the specific preferences for call delivery, the last known location of the device based on previous location retrieval attempts, as well as the current list of active or registered devices (as identified via the IMSI‘x’ identifier associated with a given SIM and mobile device respectively).
- the Multi-SIM invention 70 may use a variety of techniques in order to determine the appropriate mobile device (as identified by the IMSI‘x’ associated with a given SIM and mobile device) for call delivery based on either programmatic methods (for example, the last device that registered) or based on pre-established criteria as provided by the subscriber (for example, the subscriber may rank order a number of devices for call delivery in preferential order).
- the programmatic methods may in turn be affected by the state of each device (e.g. whether a given mobile device is engaged in a call or registered).
- an optional manifestation of the Multi-SIM invention will confirm the status of the selected mobile station by initiating a MAP PROVIDE-SUBSCRIBER-Info (PSI) message to the serving MSC/VLR 30 A.
- PSI MAP PROVIDE-SUBSCRIBER-Info
- the serving MSC/VLR 30 A will provide a MAP PSI response message containing the status of the mobile station.
- the Multi-SIM invention may select an alternative mobile station and confirm the status of the alternative mobile station (not shown) (in effect, steps 800 C and 810 will be repeated). This process will continue until a suitable mobile station (as identified by IMSI‘x’) is determined to be available for the purpose of receiving a call.
- the Multi-SIM invention will generate a MAP SRI message and forward it to the HLR.
- the HLR 50 will generate a MAP PROVIDE_ROAMING_NUMBER (PRM) message and forward it to the Multi-SIM invention 70 .
- the Multi-SIM invention 70 will forward the MAP PRM message to the serving MSC/VLR 30 A modifying the MTP, SCCP, TCAP, and MAP layers of the message relative to that received at step 830 as required.
- the serving MSC/VLR 30 A will generate and forward a MAP PRM response message containing the roaming number to the Multi-SIM invention 70 .
- the Multi-SIM invention 70 will forward the MAP PRM response message to the serving HLR 50 modifying the MTP, SCCP, TCAP, and MAP layers of the message relative to that received at step 850 as required.
- the HLR will generate and forward a MAP SRI response message to the Multi-SIM invention 70 containing the roaming number.
- the Multi-SIM invention 70 will forward the MAP SRI response to the Gateway MSC 30 C modifying the MTP, SCCP, TCAP, and MAP layers of the message relative to that received at step 870 A as required.
- the Gateway MSC 30 C will establish a call to the serving MSC/VLR 30 A via the PSTN using the routing number received at step 870 B.
- a characteristic of the disclosed invention is that the incoming calls can be selectively prioritized based on a number of attributes including the state of each mobile device (as identified by IMSI‘x’) and the prescribed routing preferences of the subscriber.
- the Multi-SIM invention 70 will appear as a defacto HLR for a Primary MSISDN or IMSI‘x’ from the perspective of the Gateway MSC 30 C and the serving MSC/VLR 30 A respectively.
- the Multi-SIM invention 70 will appear as a defacto Gateway MSC and serving MSC/VLR for a MSISDN‘x’ and IMSI‘x’ from the perspective of the HLR 50 .
- an optional manifestation of the Multi-SIM invention 70 may act as an intermediation gateway between the serving Gateway MSC 30 C and a given Service Control Point (not shown) for the purpose of ensuring the seamless support of IN services supported by the Service Control Point (not shown).
Abstract
A method and system for routing incoming communications in a communications network are provided. The network comprises a plurality of network elements. An addressable number is associated with a plurality of communications devices each identified by a unique identifier. A communication addressed to a communications device is received at a network element, the communication comprising the addressable number. A subscriber service profile associated with the addressable number is retrieved at a discrete network element, where an appropriate communications device for delivery of the incoming communication based on pre-established criteria in the subscriber service profile is determined. An identifier of the appropriate communications device is forwarded from the discrete network element to the network element. The communication is transmitted to the appropriate communications device. The subscriber service profile comprises preferences for delivery of communications, and a list of communications devices that are at least one of active and registered.
Description
- The present application is a continuation of U.S. patent application Ser. No. 12/700,331, filed Feb. 4, 2010; which is a continuation of U.S. patent application Ser. No. 10/438,097, filed May 15, 2003, now U.S. Pat. No. 7,680,491, all of which are incorporated by reference herein.
- The present invention relates generally to telecommunication network implementations; and in particular to a method and system for routing incoming communications in a communications network.
- As a whole, the teachings of the prior demonstrate that it has largely been pre-occupied with other priorities within this niche. For instance, much art is devoted to varied apparatus for allowing one wireless phone to share two (or more) telephone numbers (or SIMs) or conversely for allowing one SIM card to be shared between two masters (as between a cellular radiotelephone and multi-mode satellite radiotelephone as detailed for instance in U.S. Pat. No. 6,141,564 to Bruner, et al. entitled method of sharing a SIM card between two masters).
- And similarly, other art has likewise been devoted to switching between multiple SIM cards within a wireless phone as to maximize time-of-day discounts (consider for instance European Patent Application 1098543 by Fragola, F.), or as to lower roaming costs (consider U.S. patent application Ser. No. 20020154632 by Wang, Yung-Feng et al.) and so forth.
- Other inventions, as UK Patent No. 2375261 to Hiltunen, M. entitled transfer of SIM data between mobile computing devices, are devoted to ‘acquiring’ the identification information contained within the SIM card of one mobile phone and transferring it to another, thereby creating a manner of ‘virtual’ SIM, thereby obviating for physically transferring SIM cards between wireless devices and the corresponding lag and down-time associated with such.
- Still further art as U.S. Pat. No. 6,466,804 to Pecen, et al. entitled method and apparatus for remote multiple access to subscriber identity module, details a method and apparatus for remote multiple access to services of a subscriber identity module (SIM) card by multiple subscriber devices in a GSM system. The crux of the subject matter delineated thereof deals with the scenario whereby multiple wireless devices use a single SIM. Whereas the invention of present seeking the protection of Letters Patent effectively enables multiple independent SIMs (e.g. with individual IMSIs) to appear as a single SIM for the purpose of providing telephony services via a macroscopic (GSM) carrier.
- Indeed, we submit that there remains nothing in the prior art which intimates or anticipates the particular network based solution presented herein.
-
REFERENCES CITED U.S. Patent Application 20020154632 October 2002 Wang, et al. 370/389 U.S. Pat. No. 6,466,804 October 2002 Pecen, et al. 455/558 U.S. Pat. No. 6,141,564 October 2000 Bruner, et al. 455/558 Foreign Patent Document(s) 2375261 November 2002 GB 1098543 May 2001 EP -
- GSM 03.40, Digital cellular telecommunications system (Phase 2+); Technical realization of the Short Message Service (SMS)
- GSM 09.02, Mobile Application Part (MAP) specification
- GSM 03.90, Digital cellular telecommunications system (Phase 2+); Unstructured Supplementary Service Data (USSD)-Stage 2
- The method and system allowing for one mobile phone number (MSISDN) to be associated with a plurality of wireless devices (Multi-SIM) described herein provides the requisite art for a wireless subscriber to present/utilize one phone number (Mobile Station Integrated Services Digital Network (MSISDN) Number) across a plurality of wireless devices (and their inherent, requisite SIMs (Subscriber Identity Modules)). Effectively, the invention of present seeking the protection of Letters Patent enables multiple independent SIMs (e.g. with individual IMSIs (International Mobile Station Identifiers)) to utilize the same phone number (MSISDN) for the purpose of providing telephony services via a macroscopic (GSM) carrier. The collective effect of the invention with respect to the telecommunication services which can be offered via a plurality of wireless devices will be characterized as the ‘Multi-SIM’ service.
- The art has been articulated such that, even across a multiplicity of wireless devices, when originating a telecommunication, a common phone number (MSISDN) is always displayed.
- The mobile subscriber in question may choose which wireless device (and its associated SIM) s/he wishes to receive telecommunications upon in the preferred embodiment. In particular, various non-limiting manifestations of the invention may optionally direct Voice, SMS (Short Message Services), MMS (Multi-Media Message Services), MWI (Message Waiting Indicator) services towards different wireless devices and their associated SIMs. Optional manifestations of the invention limits the number of simultaneous telecommunications activity which emanate from the plurality of devices associated with the Multi-SIM service. Further optional manifestations of the invention permits the automated redirection of telecommunications services (e.g. call delivery and location retrieval) based on a pre-configured settings or the detection of activity from the plurality of wireless device or active polling to determine the status of the plurality of wireless devices.
-
FIG. 1 illustrates a typical, non-limiting embodiment of the system level architecture employed in the disclosure of present; -
FIG. 1A details a non-limiting call-flow of the subscriber registration sequence for mobile originated voice telecommunications of the method and system allowing for one mobile phone number (MSISDN) to be associated with a plurality of wireless devices. -
FIG. 1B represents a non-limiting call-flow detailing the means through which mobile terminating SMS or MMS traffic is managed by the method and system allowing for one mobile phone number (MSISDN) to be associated with a plurality of wireless devices. -
FIG. 1C represents a non-limiting call-flow detailing the means through which the location of a mobile station may be retrieved. -
FIG. 1D represents a non-limiting call-flow detailing the means through which an indication of the unsuccessful nature of a SMS delivery attempt will be relayed to a SMS-C.FIG. 1D also represents a non-limiting call-flow detailing the means through which the unavailability of a given mobile station may be provided to a given SMSC for subsequent SMS delivery attempts. -
FIG. 1E represents a non-limiting call-flow detailing the means through which an indication of availability (for the purpose of receiving Short Messages) may be relayed to a SMS-C. -
FIG. 1F represents a non-limiting call-flow detailing the means through which unstructured supplementary service (USSD) message handling is accommodated. -
FIG. 1G represents a non-limiting call-flow detailing the means through which supplementary service message handling is accommodated. -
FIG. 1H represents a non-limiting call-flow detailing the means through which call delivery to a wireless device is accommodated. - In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular embodiments, elements, interfaces, hardware configurations, data structures, software flows, techniques, etc. in order to provide a thorough understanding of the present invention. However, it will be apparent to one skilled in the art that the present invention may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well known methods, devices, and elements are omitted so as not to obscure the description of the present invention with unnecessary detail.
- With reference to
FIG. 1 , the essential logic 70B for the method and system allowing for one mobile phone number (MSISDN) to be associated with a plurality of wireless devices (‘Multi-SIM’) 70, provides the core Mobile Application Part (MAP)intercept function 70 A establishing devices against the Multi-SIM Mobile Station Integrated Services Digital Network (MSISDN) in the network such that outgoing traffic is seen to originate from the Multi-SIM MSISDN. The Multi-SIMcomputer program product 70 also intercepts incoming traffic to the Multi-SIM MSISDN and directs it to the nominated primary device (1A, 1B, 1C as applicable) for that traffic type. Practitioners and other honorable members skilled in the art will recognize that the primary device need not be bound to one (1) of three (3) selections and may exceed such limitations to the state of the art. - A non-limiting, illustrative list of such MAP messages which will ordinarily be encountered by the Multi-SIM method and system include the messages, including the various parametric attributes, as prescribed in the GSM TS 09.02, ETSI TS 100 974, and 3GPP TS 29.002 Mobile Application Part (MAP) specifications as amended from time to time.
- Wireless subscribers who obtain the high-level service delineated herein from their respective telecommunications carriers and/or network operators will have a defined number of devices (1A, 1B, 1C and so forth); each device is provisioned in the HLR (Home Location Register) 50 and in the Multi-SIM database 70C. An individual MSISDN is associated with each device (1A, 1B, 1C) in the
HLR 50 but is not used outside of theHLR 50 andMulti-SIM inventions 70. -
FIGS. 1A , 1B, 1C, 1D, 1E, 1F, 1G, and 1H have been included as variants ofFIG. 1 to ease and facilitate the instruction of the art, and should be interpreted as aiding and helping to achieve such ends. The labels ofFIG. 1 are therefore incorporated by reference. - With reference now to
FIG. 1A , the mobile and/or wireless device (1A, 1B, 1C) (among others and as applicable), is activated (‘turned on’). After a given wireless device completes any programmed self-check procedure, it will initiate the registration sequence via the applicable air-interface as well as the servingMSCNLR 30A persteps 100A. The servingMSCNLR 30A, as per the usual operational processes of a GSM network, normally forwards the MAP Update Location message to theHLR 50 associated with the IMSI‘x’ of the mobile device's SIM. For the purpose of the disclosed invention, the MAP Update Location message will instead be forwarded to theMulti-SIM invention 70 at step IOOB. Those skilled in the art shall recognize that there are a variety of mechanisms by which the MAP Update Location message can be forwarded to theMulti-SIM invention 70 using the inherent capabilities of the SS7 (Signaling System 7) network and the associated translation capabilities of the serving MSC/VLR 30A. Those skilled in the art will recognize that theMulti-SIM invention 70 will appear as a defacto HLR for IMSI‘x’ from the perspective of the servingMSCNLR 30A. - After receiving the MAP Update Location message, the
Multi-SIM invention 70 will store the addressing information of the MSC/VLR 30A associated with IMSI‘x’. The Multi-SIM invention will also retrieve the address of theHLR 50 associated with IMSI‘x’ and forward the MAP Update Location message to theappropriate HLR 50 via the SS7 network atstep 100C. An optional manifestation of theMulti-SIM invention 70 will initiate a MAP version negotiation sequence (not shown) as described in GSM 09.02 (and similar specifications) if the MAP version number of the received message at step IOOB is greater than that currently supported by theHLR 50 associated with IMSI‘x’. Those skilled in the art will recognize that there are a number of well understood message sequences associated with the MAP version negotiation procedure and that the intent of such a such a procedure is to ensure that subsequent messages received from network elements such as the serving MSC/VLR 30A are set to a MAP version level no higher than the MAP version level supported by theHLR 50 associated with IMSI‘x’. The MTP (Message Transfer Part) and SCCP (Signaling Connection Control Part) of the MAP Update Location message forwarded to theHLR 50 at step IOOC will be modified by theMulti-SIM invention 70 so that the Multi-SIM invention will appear as a VLR from the perspective of theHLR 50. Those skilled in the art will recognize that theHLR 50 utilizes received VLR and MSC addressing information in the MAP layer of the Update Location message to invoke service screening criteria as defined by GSM specifications. For example, a VLR or MSC address associated with a given service provider's ‘home’ network may be accorded different service attributes relative to the VLR and MSC associated with a ‘foreign’ network. To that end, an optional manifestation of the invention will map the VLR and MSC addressing information received in the MAP layer of the Update Location message to a predefined subset of alternative VLR and MSC addresses in order to invoke an appropriate set of service attributes for the subscribers associated with the Multi-SIM service. Those skilled in the art will recognize that for the aforementioned optional manifestation of the invention that theHLR 50 will have to be configured (typically via translation tables) to apply a specific set of service attributes given the predefined subset of alternative VLR and MSC addresses. - Still in reference to
FIG. 1A , theHLR 50 will retrieve the subscriber's profile using IMSI‘x’ as the index key using established processes commonly implemented by HLR vendors. The subscriber's profile will include, among other subscribed service attributes, the MSISDN‘x’ associated with IMSI‘x’. TheHLR 50 will in turn initiate a MAP Insert Subscriber Data sequence, containing the subscribed attributes associated with the subscriber's profile and MSISDN‘x’, which will be forwarded to theMulti-SIM invention 70 via the SS7 network at step IIOA. Those skilled in the art shall recognize that theHLR 50 will direct the MAP Insert Subscriber Data sequence to theMulti-SIM invention 70 via the SS7 network by virtue of the received MTP and SCCP addressing information received at step IOOC. - Still in reference to
FIG. 1A , the MAP Insert Subscriber Data message is received from theHLR 50 by the art of the Multi-SIM invention 70 (specifically 70A) at IIOA. Using said IMSI‘x’ as an index key, the Primary MSISDN is retrieved (not shown) from an internal database/table 70C (via 70B). An optional manifestation of the invention will store the status of the wireless device associated with IMSI‘x’ in the application memory or internal database 70C for the purpose of applying optional routing procedures for outgoing and incoming as noted in a subsequent portion of this disclosure. Yet another optional manifestation of the invention will store selected attributes associated with Intelligent Network (IN) services in application memory or internal database 70C. Those skilled in the art will recognize that there are a variety of IN services which are defined by various specifications which serve the similar purposes without diluting the intent and scope of the present invention including those associated with CAMEL (Customized Applications for Mobile Network Enhanced Logic) and CS-1 (Capability Set 1) as well as derivations thereof. - Still in reference to
FIG. 1A , theMulti-SIM invention 70 will generate an MAP Insert Subscriber Data message where the MSISDN‘x’ received from theHLR 50 will be replaced by the Public MSISDN retrieved from the Multi-SIM internal database 70C. TheMulti-SIM invention 70 will forward the MAP Insert Subscriber Data message to the servingMSCNLR 30A via the SS7 network at step IIOB. Those skilled in the art will recognize that a characteristic of the invention is that the MAP Insert Subscriber Data received by aMSCNLR 30A always contains the Public MSISDN regardless of which IMSI‘x’ (and corresponding SIM and wireless device) was activated. - Still in reference to
FIG. 1A , after the servingMSCNLR 30A processes the information received via the MAP Insert Subscriber Data message received at step IIOB, the servingMSCNLR 30A generates and forwards a MAP Insert Subscriber Data acknowledgement message to theMulti-SIM invention 70 atstep 120A. At step 120B, theMulti-SIM invention 70 will forward a MAP Insert Subscriber Data acknowledgement message to theHLR 50 modifying the MTP, SCCP, TCAP, and MAP layers of the message relative to that received atstep 120A as required. For example, the Primary MSISDN will be replaced by MSISDN‘x’. TheHLR 50 will receive the MAP Insert Subscriber Data message and generate an MAP Update Location acknowledgement message using established processes commonly implemented by HLR vendors. TheHLR 50 will forward the MAP Update Location acknowledgement message to the Multi-SIM invention atstep 130A. The servingMSCNLR 30A will receive the MAP Update Location acknowledgement message and initiate an appropriate confirmation message to the wireless device I‘x’ atstep 130B. Atstep 130C, the serving MSCNLR will complete the registration sequence with the mobile station. - Still in reference to
FIG. 1A , a mobile originated call may then be established atstep 140A. TheMSCNLR 30A will initiate a call to the intended destination address via the Public Switched Telephone Network (PSTN) using the procedures prescribed using the ISDN User Part (ISUP) protocol at step 140B. A characteristic of the disclosed invention is that the Calling Party Number information associated with the call establishment procedure will be set to the primary MSISDN forwarded to the servingMSCNLR 30A by theMulti-SIM invention 70 at step IIOB. - Still in reference to
FIG. 1A , those skilled in the art will recognize that a similar sequence will be invoked for GPRS (General Packet Radio Service) registration scenarios. In particular, a characteristic of the disclosed invention is that the Primary MSISDN identifier will be associated with a given IMSI‘x’ for the PDP (Packet Data Protocol) Context Activation establishment procedure. - Still in reference to
FIG. 1A , an optional manifestation of theMulti-SIM invention 70 may selectively screen outgoing call attempts by utilizing procedures associated with IN services. In particular, an IN message (e.g. CAMEL INITIAL_DP) originated from the servingMSCNLR 30A will indicate a call attempt being made by amobile station 1A, 1B, 1C. TheMulti-SIM invention 70 may invoke screening criteria based on the destination and source address information contained in the IN message. TheMulti-SIM invention 70 may also invoke incremental screening criteria based on the state of a given mobile device (associated with IMSI‘x’) as stored in the Multi-SIM invention database 70C (not shown). For example, theMulti-SIM invention 70 may use screening criteria to limit the number of simultaneous calls or to redirect calls to an alternative destination address. TheMulti-SIM invention 70 will instruct the servingMSCNLR 30A via an appropriate IN message (e.g. CAMEL CONTINUE or CAMEL CONNECT or CAMEL CANCEL) as to the appropriate course of action based on the screening criteria. Those skilled in the art will recognize that the optional manifestation of theMulti-SIM invention 70 will provide functionality commonly associated with a Service Control Point (SCP). Those skilled in the art will also recognize that there are a variety of IN protocols which are defined by various specifications which serve the similar purposes without diluting the intent and scope of the present invention including those associated with CAMEL and CS-1 (Capability Set 1) as well as derivations thereof. Another optional manifestation of theMulti-SIM invention 70 may act as an intermediation gateway between the servingMSCNLR 30A and a given Service Control Point (not shown) for the purpose of ensuring the seamless support of IN services supported by the Service Control Point (not shown). - Now with reference to
FIG. 1B , where the respective Short Message (SM) stored in SMS-C 40 remains to be delivered. Those skilled in the art will recognize that the Short Message may also consist of a Multi-Media or voice-mail alerting message. The SMS-C will generate and forward a MAP SEND-ROUTING-INFO-FOR-SM (SRI for SM) message which will be directed to the Multi-SIM invention. Those skilled in the art shall recognize that there are a variety of mechanisms by which the MAP SRI for SM message can be forwarded to theMulti-SIM invention 70 using the inherent capabilities of the SS7 network and the associated translation capabilities of the SMS-C 40. Those skilled in the art will recognize that theMulti-SIM invention 70 will appear as a defacto HLR for a given Primary MSISDN from the perspective of the SMS-C 40. - Still in reference to
FIG. 1B , theMulti-SIM invention 70 will retrieve the subscriber's service profile using the Primary MSISDN as the index key from an internal database/table 70C (not shown). The service profile will contain, among other attributes, information pertaining to the specific routing preferences for Short Message as well as Multi-Media Messages and Voice-Mail alerts as the case may be. The Multi-SIM invention will generate and forward a MAP SRI for SM response message to the SMS-C 40 atstep 210. The MAP SRI for SM response message will contain information so that the SMS-C will consider the Multi-SIM invention as the serving MSC for the purpose of Short Message delivery. For example, the Network Node Number parameter will contain an identifier which will uniquely identify the Multi-SIM invention as the serving MSC for the purpose of Short Message delivery. Those skilled in the art will recognize that the MAP SRI for SM response message atstep 210 will contain other parameters so that the SMS-C will be able to continue processing the delivery of the Short Message. For example, the MAP SRI for SM message will contain an IMSI value which can be selected from the set of IMSI‘x’ associated with the Primary MSISDN or set to a configurable range of values. Those skilled in the art will recognize that theMulti-SIM invention 70 will appear as a defacto VLR from the perspective of the SMS-C 40. - Still in reference to
FIG. 1B , atstep 220, the SMS-C will attempt delivery of the message by generating and forwarding a MAP MT-FORWARD-SHORT-MESSAGE (MT FSM) message to theMulti-SIM invention 70. Atstep 230, the Multi-SIM invention will determine the appropriate mobile device (as identified by the IMSI‘x’ associated with a given SIM and mobile device respectively) to receive the Short Message based on a number of factors including the source address contained in the MT FSM message as well as the nature of the message (e.g. short message or alert). Note that theMulti-SIM invention 70 may use a variety of techniques in order to determine the appropriate mobile device based on either programmatic methods (for example, the last device that registered may be used to forward all short messages) or based on pre-established criteria as provided by the subscriber (for example, the subscriber may send Short Messages and alert messages to different devices based on the relative capabilities supported on each device). The programmatic methods may in turn be affected by the state of each device (e.g. whether a given mobile device is engaged in a call or registered). Those skilled in the art will recognize that a variety of techniques may be used in order to determine the destination mobile device without diluting the intent and scope of the present invention. A characteristic of the disclosed invention is that telecommunication services can be selectively terminated to the plurality of mobile devices based on a number of programmatic techniques as well as pre-configured routing criteria. - Still in reference to
FIG. 1B , atstep 230, the Multi-SIM invention will generate and forward a MT FSM to the serving MSC/VLR 30A associated with the IMSI‘x’ of the selected mobile station, modifying the MTP, SCCP, TCAP, and MAP layers of the message relative to that received atstep 230 as required. Those skilled in the art will recognize that theMulti-SIM invention 70 will appear as a defacto SMS-C from the perspective of the serving MSC/VLR 30A. Atstep 240, the short message will be delivered to themobile station 1A, 1B, 1C (among others and as applicable) associated with IMSI‘x’. Atstep 250, a MAP MT FSM response message containing an indication of the successful or unsuccessful nature of the delivery attempt will be initiated by the serving MSC/VLR 30A and forwarded to theMulti-SIM invention 70. Atstep 260, theMulti-SIM invention 70 will generate and forward a MT FSM response to the appropriate SMS-C 40, modifying the MTP, SCCP, TCAP, and MAP layers of the message relative to that received atstep 250 as required. - Now with reference to
FIG. 1C , aLocation Client 80 will initiate a location retrieval request via an Application Programming Interface (API) at 300A which will include a number of parameters including but not limited to the Primary MSISDN and a transaction identifier. In lieu of a Primary MSISDN, the Location Client may provide a pseudonym which can be correlated to the Primary MSISDN. The purpose of the transaction identifier being to uniquely correlate a given request with other messages which may be received asynchronously including, but not limited to, a confirmation response. Practitioners skilled in the art shall recognize that a variety of object oriented application programming interfaces (e.g. Common Object Request Broker Architecture (CORBA) or Extensible Markup Language (XML)) may be used. - Still in reference to
FIG. 1C , atstep 300B, the Gateway Mobile Location Centre (GMLC) 81 will receive the location retrieval request. TheGMLC 81 will initiate a MAP ANY-TIME-INTERROGATION (ATI) sequence to theMulti-SIM invention 70. Those skilled in the art shall recognize that there are a variety of mechanisms by which the MAP ATI message can be forwarded to theMulti-SIM invention 70 using the inherent capabilities of the SS7 network and the associated translation capabilities of theGMLC 81. Those skilled in the art will recognize that theMulti-SIM invention 70 will appear as a defacto HLR for IMSI‘x’ from the perspective of theGMLC 81. Those skilled in the art will recognize that the functionality of the GMLC is generally defined by a variety of specifications including GSM 03.71 and 3GPP 23.071 as amended from time to time and that modifications to the capabilities of the GMLC as prescribed by the noted specifications does not dilute the intent and scope of the present invention. A characteristic of the disclosed invention is that the location of a given mobile terminal can be retrieved without sending messages to theHLR 50. Those skilled in the art will recognize that theMulti-SIM invention 70 effectively emulates certain capabilities associated with the HLR for the purpose of retrieving the location associated with a mobile station. - Still in reference to
FIG. 1C , at step 300C, theMulti-SIM invention 70 will retrieve the subscriber's service profile using the Primary MSISDN as the index key from an internal database/table 70C (not shown). The service profile will contain, among other attributes, information pertaining to the specific preferences for location retrieval, the last known location of the device based on previous location retrieval attempts, as well as the current list of active or registered devices (as identified via the IMSI‘x’ identifier associated with a given SIM and mobile device respectively). TheMulti-SIM invention 70 will determine the appropriate mobile device (as identified by the IMSI‘x’ associated with a given SIM and mobile device) for the purpose of a location query based on a number of factors including the source address contained in the MAP ATI message. TheMulti-SIM invention 70 may use a variety of techniques in order to determine the appropriate mobile device for the location query based on either programmatic methods (for example, the last device that registered) or based on pre-established criteria as provided by the subscriber (for example, the subscriber may rank order a number of devices to be located in preferential order). The programmatic methods may in turn be affected by the state of each device (e.g. whether a given mobile device is engaged in a call or registered). Those skilled in the art will recognize that a variety of techniques may be used in order to determine the mobile device for a location query without diluting the intent and scope of the present invention. TheMulti-SIM invention 70 will initiate a MAP PROVIDE-SUBSCRIBER-Info (PSI) message towards the appropriate serving MSC/VLR 30A based on the selected mobile station (which is associated with a given IMSI(x)) modifying the MTP, SCCP, TCAP, and MAP layers of the message relative to that received atstep 300B as required. Upon receipt of the MAP PSI message, the serving MSC/VLR 30A will retrieve the location of the mobile station. The mechanisms of retrieving the location of the mobile station are generally prescribed by a variety of specifications including GSM 03.71 and 3GPP 23.071 as amended from time to time. - Still in reference to
FIG. 1C , atstep 310A a MAP PSI response message will be initiated by the serving MSC/VLR 30A which will contain the location of the mobile terminal. The MAP PSI response message will be forwarded to theMulti-SIM invention 70. Atstep 310B, theMulti-SIM invention 70 will generate and forward a MAP ATI response to theGMLC 81, modifying the MTP, SCCP, TCAP, and MAP layers of the message relative to that received atstep 310A as required. An optional manifestation of theMulti-SIM invention 70 will store the location of mobile station (associated with IMSI‘x’) in the internal database/table 70C (not shown). Atstep 310C, theGMLC 81 will provide the location information to theLocation Client 80 via the API. Those skilled in the art will recognize that an optional manifestation of theMulti-SIM invention 70 may abbreviate the location retrieval attempt by providing location information associated with previous location attempts. This will effectively result insteps 300C and 310A being bypassed. The retrieval and provision of stored location information is governed by programmatic control and there are a number of procedures and conditions (for example, time based methods) which may be applied to abbreviate the location retrieval process. - Now with reference to
FIG. 1D , where a SMS delivery report associated with a SMS delivery attempt is to be forwarded to the appropriate SMS-C. Atstep 400A, a MAP MT-FORWARD-SHORT-MESSAGE (MT FSM) response message containing an indication of the unsuccessful nature of the delivery attempt will be initiated by the serving MSC/VLR 30A and forwarded to theMulti-SIM invention 70. Those skilled in the art will recognize that theMulti-SIM invention 70 will appear as a defacto SMS-C from the perspective of the serving MSC/VLR 30A based on the intermediation of registration and SMS delivery sequences previously described. Atstep 400B, theMulti-SIM invention 70 will generate and forward a MT FSM response to the appropriate SMS-C 40, modifying the MTP, SCCP, TCAP, and MAP layers of the message relative to that received atstep 400A as required. - Still in reference to
FIG. 1D , atstep 410, the SMS-C 40A will initiate a MAP REPORT-SM-DELIVERY-STATUS which will contain a number of parameters including the Primary MSISDN and Service Center address and which will be forwarded to theMulti-SIM invention 70. Those skilled in the art will recognize that theMulti-SIM invention 70 will appear as a defacto HLR for a given Primary MSISDN from the perspective of the SMS-C 40A. To that end, theMulti-SIM invention 70 will emulate the capabilities associated with aHLR 50 for the purpose of setting and maintaining the Message Waiting Data file for the Primary MSISDN. The Message Waiting Data file can be implemented via a variety of mechanisms without diluting the intent and scope of the present invention. For example, the Message Waiting Data file can be stored as a multi-element data element in the Multi-SIM database 70C (as indexed by the Primary MSISDN). Those skilled in the art will recognize that the intent of the Message Waiting Data file in the HLR, among other functions, is to record the address of SMS-Cs for subsequent notification once a given mobile station is deemed active (registers). Atstep 420A, theMulti-SIM invention 70 will initiate a MAP REPORT-SM-DELIVERY-STATUS response message to the SMS-C 40A indicating that the SMS-Cs address has been stored. At step 420B, the SMS-C 40A may provide an indication of the unsuccessful delivery attempt to theMessage Center 41A. - Still in reference to
FIG. 1D , atstep 430A, a Message Center 41B may attempt to deliver a Short Message to the a given subscriber as identified by the Primary MSISDN. Atstep 430B, the SMS-C 40B will generate and forward a SRI for SM message which will be directed to theMulti-SIM invention 70. Those skilled in the art shall recognize that there are a variety of mechanisms by which the MAP SRI for SM message can be forwarded to theMulti-SIM invention 70 using the inherent capabilities of the SS7 network and the associated translation capabilities of the SMS-C 40. TheMulti-SIM invention 70 will retrieve the subscriber's service profile and the Message Waiting Data file using the Primary MSISDN as the index key from an internal database/table 70C (not shown). The service profile will contain, among other attributes, information pertaining to the specific routing preferences for Short Message as well as Multi-Media Messages and Voice-Mail alerts as the case may be. As the Message Waiting File will indicate that the mobile station is not active/registered, theMulti SIM platform 70 will generate and forward a MAP SRI for SM response message to the SMS-C 40B atstep 440 which will indicate that the subscriber is absent (typically by sending the User Error parameter to ‘Absent Subscriber_SM’). - Still in reference to
FIG. 1D , atstep 450, the SMS-C 40B will initiate a MAP REPORT-SM-DELIVERY-STATUS which will contain a number of parameters including the Primary MSISDN and Service Center address and which will be forwarded to theMulti SIM platform 70. Atstep 460, theMulti-SIM invention 70 will initiate a MAP REPORT-SM-DELIVERY-STATUS response message to the SMS-C 40B indicating that the SMS-Cs address has been stored. - Now with reference to
FIG. 1E , which illustrates the intercept of the MAP READY FOR SM operation generally used by the MSC/VLR 30A if a subscriber, whose message waiting flag is active in the VLR, has re-established radio contact with the network or has memory available. Atstep 500, the MSC/VLR 30A generates MAP READY FOR SM message which is forwarded to theMulti-SIM invention 70. Those skilled in the art will recognize that theMulti-SIM invention 70 will appear as a defacto HLR for a given IMSI‘x’ from the perspective of the MSC/VLR 30A. The MAP READY FOR SM message will contain several parameters indicating if the mobile subscriber is present or if the mobile station has memory. Atstep 510, the Multi-SIM invention will generate and forward a MAP READY FOR SM response message to the MSC/VLR 30A indicating that the message atstep 500 has been received and processed successfully. - Still in reference to
FIG. 1E , theMulti-SIM invention 70 will retrieve the subscriber's service profile using the IMSI‘x’ as the index key from an internal database/table 70C (not shown). The service profile will contain, among other attributes, information pertaining to the specific routing preferences for Short Message as well as Multi-Media Messages and Voice-Mail alerts as the case may be. The service profile will contain the Primary MSISDN associated with IMSI‘x’ which will in turn be used to index the Message Waiting Data elements. Based on the information retrieved, the Multi-SIM invention will determine which SMS-C should be contacted. Those skilled in the art will recognize that the Multi-SIM invention may use a variety of techniques in order to determine the appropriate SMS-C based on the information contained in the internal database/table 70C (not shown). In particular, the Multi-SIM invention may determine that a SMS-C may not be contacted based on the routing preferences prescribed by the subscriber. Alternatively, the Multi-SIM invention may determine that several SMS-Cs (not shown) should be contacted. Atstep 520A, the Multi-SIM invention will generate and forward a MAP ALERT-SERVICE-CENTRE (Alert SC) to the selected SMS-C 40A (or SMS-Cs (not shown)) indicating that a given subscriber (as identified by the Primary MSISDN) is ready to receive Short Messages. At step 520B, the SMS-C may alert Message Centers to the effect that a given subscriber may receive Short Messages. - Still in reference to
FIG. 1E , atstep 530B, the SMS-C 40A will generate and forward a MAP Alert SC response message to theMulti-SIM invention 70 indicating that the MAP Alert SC message was received and processed successfully. At this point in time, the SMS-C 40 may initiate the short message delivery mechanisms as described earlier in the text associated withFIG. 1B . - Still in reference to
FIG. 1E , those skilled in the art will recognize that other mechanisms including the registration process described inFIG. 1A may invoke the MAP Alert SC sequence described atstep 520A. - Now with reference to
FIG. 1F , USSD MAP messages are typically routed to and from the USSD Application via the serving MSC/VLR and HLR using the methods, operations, and protocols specified in GSM 03.90 and GSM 09.02 as amended from time to time. An optional manifestation of the invention provides an USSD-based subscriber interface to change default routing preferences of Multi-SIM subscribers. The Multi-SIM invention will also permit subscribers and network operators to make configuration changes via a (web-based) provisioning interface. - Still with reference to
FIG. 1F , atstep 600, a subscriber may invoke an Unstructured Supplementary Service Data (USSD) service by keying in a USSD short code (e.g. *XX#). This will invoke a USSD Message (e.g. MAP PROCESS_UNSTRUCTURED_SS_REQUEST (PUSSR)) which will be forwarded to theMulti-SIM invention 70 using the inherent capabilities of the SS7 network and the associated translation capabilities of the serving MSC/VLR 30A. Atstep 610, theMulti-SIM invention 70 may recognize that the USSD short code (as provided via the USSD String parameter) matches a prescribed code associated with the invocation of a feature of the Multi-SIM service. Example services include modifying the routing behavior of the Multi-SIM service for received voice or messaging traffic or obtaining information pertaining to the current settings of the Multi-SIM invention for the subscriber. Atstep 610, the Multi-SIM invention initiates a MAP USSD response message. The MAP USSD response message may contain text which indicates that the requested feature was invoked successfully or requested information pertaining to the status of the Multi-SIM service. Atstep 610, the MSC/VLR will relay the information to the mobile station per the processes described in GSM 03.90 and GSM 09.02. - Still with reference to
FIG. 1F , atsteps USSD Based Application 90 via theMulti-SIM invention 70 andHLR 50. At step 620B, the Multi-SIM invention modifies the SCCP, TCAP, and MAP layers of the message relative to that received atstep 620A as required. Those skilled in the art will recognize that theMulti-SIM invention 70 will appear as a defacto HLR for IMSI‘x’ (or the Primary MSISDN) from the perspective of the MSC/VLR 30—and that the Multi-SIM invention will appear as a defacto MSC/VLR for IMSI‘x’ (or MSISDN‘x’) from the perspective of theHLR 50. Atsteps USSD Based Application 90 and is propagated to the serving MSC/VLR 30A via theHLR 50 andMulti-SIM invention 70. At step 640B, the Multi-SIM invention modifies the SCCP, TCAP, and MAP layers of the message relative to that received atstep 640A as required. At step 640B, the MSC/VLR will relay the information to the mobile station per the processes described in GSM 03.90 and GSM 09.02. - Now with reference to
FIG. 1G , Supplementary services (e.g. call forwarding services) are typically modified (in order to activate, deactivate, register, erase, or check the status of supplementary services as the case may be) via MAP messages between the MSC and the VLR and between the VLR and the HLR using the methods, operations, and protocols specified in GSM 09.02 as amended from time to time. Atstep 700, a subscriber may invoke a command via the Man Machine Interface (MMI) of his/her mobile terminal in order to modify a supplementary service. This will invoke a Supplementary Service MAP message (e.g. MAP ACTIVATE_SS) which will be forwarded to theMulti-SIM invention 70 using the inherent capabilities of the SS7 network and the associated translation capabilities of the serving MSC/VLR 30A. TheMulti-SIM invention 70 will retrieve the subscriber's service profile from an internal database/table 70C (not shown). The service profile will contain, among other attributes, the complete range of terminal information associated with the subscriber—including the entire suite of IMSI‘x’ and MSISDN‘x’ information associated with the subscriber. Atsteps device 1A, 1B, 1C as applicable (in particular, each IMSI‘x’ may be associated with a different HLR). Practitioners skilled in the art will recognize that the number of devices need not be bound to one (1) of three (3) selections and may exceed such limitations to the state of the art. Atsteps Multi-SIM invention 70. Atstep 770, once theMulti-SIM invention 70 has received confirmation that the required supplementary service command has been carried out successfully, the appropriate Supplementary Service MAP response message will be generated and forwarded to the Serving MSC/VLR 30A. Atstep 770, if one of the responses from the HLR indicates an unsuccessful attempt, a Supplementary Service MAP response message indicating an unsuccessful attempt will be provided to the serving MSC/VLR 30A. An optional manifestation of the invention may roll-back the settings associated with a given supplementary service by invoking the complementary Supplementary Service command (e.g. a DEACTIVATE_SS message to counter a prior ACTIVATE_SS message) (not shown). The optional manifestation of the invention will retrieve the status of a given Supplementary Service setting via the MAP INTERROGATE_SS message (not shown) prior to invoking the subscriber command atsteps - Now with reference to
FIG. 1H , atstep 800A, a call will be received by the Gateway MSC 30C from thePSTN 95. Atstep 800B, the Gateway MSC 30C will generate and forward a MAP SEND_ROUTING_INFORMATION (SRI) message to theMulti-SIM invention 70. TheMulti-SIM invention 70 will retrieve the subscriber's service profile using the Primary MSISDN as the index key from an internal database/table 70C (not shown). The service profile will contain, among other attributes, information pertaining to the specific preferences for call delivery, the last known location of the device based on previous location retrieval attempts, as well as the current list of active or registered devices (as identified via the IMSI‘x’ identifier associated with a given SIM and mobile device respectively). TheMulti-SIM invention 70 may use a variety of techniques in order to determine the appropriate mobile device (as identified by the IMSI‘x’ associated with a given SIM and mobile device) for call delivery based on either programmatic methods (for example, the last device that registered) or based on pre-established criteria as provided by the subscriber (for example, the subscriber may rank order a number of devices for call delivery in preferential order). The programmatic methods may in turn be affected by the state of each device (e.g. whether a given mobile device is engaged in a call or registered). At step 800C, an optional manifestation of the Multi-SIM invention will confirm the status of the selected mobile station by initiating a MAP PROVIDE-SUBSCRIBER-Info (PSI) message to the serving MSC/VLR 30A. Atstep 810, the serving MSC/VLR 30A will provide a MAP PSI response message containing the status of the mobile station. Depending on the nature of the status information received, the Multi-SIM invention may select an alternative mobile station and confirm the status of the alternative mobile station (not shown) (in effect, steps 800C and 810 will be repeated). This process will continue until a suitable mobile station (as identified by IMSI‘x’) is determined to be available for the purpose of receiving a call. Atstep 820, once a suitable mobile station is selected, the Multi-SIM invention will generate a MAP SRI message and forward it to the HLR. Atstep 830, theHLR 50 will generate a MAP PROVIDE_ROAMING_NUMBER (PRM) message and forward it to theMulti-SIM invention 70. Atstep 840, theMulti-SIM invention 70 will forward the MAP PRM message to the serving MSC/VLR 30A modifying the MTP, SCCP, TCAP, and MAP layers of the message relative to that received atstep 830 as required. Atstep 850, the serving MSC/VLR 30A will generate and forward a MAP PRM response message containing the roaming number to theMulti-SIM invention 70. Atstep 860, theMulti-SIM invention 70 will forward the MAP PRM response message to the servingHLR 50 modifying the MTP, SCCP, TCAP, and MAP layers of the message relative to that received atstep 850 as required. Atstep 870A, the HLR will generate and forward a MAP SRI response message to theMulti-SIM invention 70 containing the roaming number. At step 870B, theMulti-SIM invention 70 will forward the MAP SRI response to the Gateway MSC 30C modifying the MTP, SCCP, TCAP, and MAP layers of the message relative to that received atstep 870A as required. - Still in reference to
FIG. 1H , the Gateway MSC 30C will establish a call to the serving MSC/VLR 30A via the PSTN using the routing number received at step 870B. A characteristic of the disclosed invention is that the incoming calls can be selectively prioritized based on a number of attributes including the state of each mobile device (as identified by IMSI‘x’) and the prescribed routing preferences of the subscriber. Those skilled in the art will recognize that theMulti-SIM invention 70 will appear as a defacto HLR for a Primary MSISDN or IMSI‘x’ from the perspective of the Gateway MSC 30C and the serving MSC/VLR 30A respectively. Those skilled in the art will recognize that theMulti-SIM invention 70 will appear as a defacto Gateway MSC and serving MSC/VLR for a MSISDN‘x’ and IMSI‘x’ from the perspective of theHLR 50. - Still in reference to
FIG. 1H , an optional manifestation of theMulti-SIM invention 70 may act as an intermediation gateway between the serving Gateway MSC 30C and a given Service Control Point (not shown) for the purpose of ensuring the seamless support of IN services supported by the Service Control Point (not shown).
Claims (6)
1. A method for routing incoming communications in a communications network comprising a plurality of network elements in which an addressable number is associated with a plurality of communications devices each having a unique identifier associated therewith, the method comprising:
receiving, at a first one of said network elements, an incoming communication addressed to a communications device of said plurality of communications devices, said incoming communication comprising said addressable number;
retrieving, at a discrete network element, a subscriber service profile associated with said addressable number;
determining, at said discrete network element, from said plurality of communications devices associated with said addressable number an appropriate communications device for delivery of said incoming communication based on pre-established criteria in said subscriber service profile, wherein said determining said appropriate communications device for delivery of said incoming communication comprises:
selecting a first communications device from among said plurality of communications devices according to said pre-established criteria;
determining if said first communications device is available or unavailable to receive said incoming communication;
if said first communications device is available to receive said incoming communication, designating said first communications device as said appropriate communications device; and
if said first communications device is unavailable to receive said incoming communication, then:
selecting an alternative communications device from among the plurality of communications devices according to said pre-established criteria; and
determining if said alternative communications device is available or unavailable to receive said incoming communication and if said alternative communications device is available to receive said incoming communication, designating said selected alternative communications device as said appropriate communications device;
if said alternative communications device is unavailable, repeating selecting of communication devices and determining availability thereof until said appropriate communications device has been designated or until all communications devices of said plurality of communications devices have been determined to be unavailable; and
if all said communications devices of said plurality of communications devices have been determined to be unavailable, then designating an address for delivery of said incoming communication, wherein said address is specified in said subscriber service profile;
forwarding an identifier of said appropriate communications device from said discrete network element to said first one of said network elements; and
transmitting said incoming communication to said appropriate communications device,
wherein said subscriber service profile comprises preferences for delivery of incoming communications, and a list of communications devices, of said plurality of communications devices, that are at least one of active and registered.
2. The method as claimed in claim 1 , wherein said pre-established criteria comprises a preferential order of communications devices for delivery of incoming communications.
3. The method as claimed in claim 1 , wherein said subscriber service profile further comprises a last location of each communications device, of said plurality of communication devices, based on previous location retrieval attempts.
4. The method as claimed in claim 1 , wherein said determining if said first communications device is available or unavailable to receive said incoming communication comprises determining if said first communications device is registered or unregistered by:
sending an interrogation to said first communications device;
determining, based on the presence or absence of an appropriate reply to said interrogation, that said first communications device is respectively registered or unregistered.
5. The method as claimed in claim 1 , wherein said incoming communication is received from at least one of a telephony service, a text message service, and a data service, and said appropriate communications device is selected based on a type of service that said incoming communication is received from.
6. The method as claimed in claim 1 , wherein said communications network is enabled to route different types of communications, and said pre-established criteria comprises routing preferences based on a type of said incoming communication.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/461,330 US20120214459A1 (en) | 2003-05-15 | 2012-05-01 | Method for routing incoming communications in a communications network |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/438,097 US7680491B2 (en) | 2003-05-15 | 2003-05-15 | Method and system allowing for one mobile phone number (MSISDN) to be associated with a plurality of wireless devices (‘Multi-SIM’) |
US12/700,331 US20100136982A1 (en) | 2003-05-15 | 2010-02-04 | Method and system for routing incoming communications in a communications network |
US13/461,330 US20120214459A1 (en) | 2003-05-15 | 2012-05-01 | Method for routing incoming communications in a communications network |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/700,331 Continuation US20100136982A1 (en) | 2003-05-15 | 2010-02-04 | Method and system for routing incoming communications in a communications network |
Publications (1)
Publication Number | Publication Date |
---|---|
US20120214459A1 true US20120214459A1 (en) | 2012-08-23 |
Family
ID=33417501
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/438,097 Active 2025-10-05 US7680491B2 (en) | 2003-05-15 | 2003-05-15 | Method and system allowing for one mobile phone number (MSISDN) to be associated with a plurality of wireless devices (‘Multi-SIM’) |
US12/700,331 Abandoned US20100136982A1 (en) | 2003-05-15 | 2010-02-04 | Method and system for routing incoming communications in a communications network |
US13/461,330 Abandoned US20120214459A1 (en) | 2003-05-15 | 2012-05-01 | Method for routing incoming communications in a communications network |
Family Applications Before (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/438,097 Active 2025-10-05 US7680491B2 (en) | 2003-05-15 | 2003-05-15 | Method and system allowing for one mobile phone number (MSISDN) to be associated with a plurality of wireless devices (‘Multi-SIM’) |
US12/700,331 Abandoned US20100136982A1 (en) | 2003-05-15 | 2010-02-04 | Method and system for routing incoming communications in a communications network |
Country Status (2)
Country | Link |
---|---|
US (3) | US7680491B2 (en) |
EP (2) | EP1631106A3 (en) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20100088374A1 (en) * | 2007-02-16 | 2010-04-08 | Astroem Bo | Supplementary Services in Communication Networks |
US20110167118A1 (en) * | 2010-01-06 | 2011-07-07 | Yigang Cai | Message waiting notification to external message centers |
TWI548260B (en) * | 2013-06-14 | 2016-09-01 | 國立臺灣大學 | A system and method of trigger service |
Families Citing this family (113)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
AU2001285023A1 (en) | 2000-08-17 | 2002-02-25 | Mobileum, Inc. | Method and system for wireless voice channel/data channel integration |
US7590417B2 (en) | 2003-08-05 | 2009-09-15 | Roamware Inc. | Method, system and computer program product for countering anti-traffic redirection |
US7929953B2 (en) | 2003-08-05 | 2011-04-19 | Roamware, Inc. | Controlling traffic of an inbound roaming mobile station between a first VPMN, a second VPMN and a HPMN |
US7684793B2 (en) | 2003-08-05 | 2010-03-23 | Roamware, Inc. | Anti-traffic redirection system |
DE10246124A1 (en) * | 2002-10-01 | 2004-04-15 | T-Mobile Deutschland Gmbh | SIM card for operation with a terminal of a mobile communication network |
US7577431B2 (en) | 2003-02-18 | 2009-08-18 | Roamware, Inc. | Providing multiple MSISDN numbers in a mobile device with a single IMSI |
US8175622B2 (en) * | 2003-02-14 | 2012-05-08 | Roamware, Inc. | Method and system for keeping all phone numbers active while roaming with diverse operator subscriber identity modules |
WO2004075579A2 (en) | 2003-02-14 | 2004-09-02 | Roamware, Inc. | Signaling and packet relay method and system including general packet radio service (“gprs”) |
US8478277B2 (en) * | 2003-02-18 | 2013-07-02 | Roamware Inc. | Network-based system for rerouting phone calls from phone networks to VoIP clients for roamers and subscribers who do not answer |
US8331907B2 (en) | 2003-02-18 | 2012-12-11 | Roamware, Inc. | Integrating GSM and WiFi service in mobile communication devices |
US20040185888A1 (en) * | 2003-03-18 | 2004-09-23 | Nokia Corporation | Solving mobile station identity in a multi-SIM situation |
US7680491B2 (en) * | 2003-05-15 | 2010-03-16 | Redknee Inc. | Method and system allowing for one mobile phone number (MSISDN) to be associated with a plurality of wireless devices (‘Multi-SIM’) |
US8121594B2 (en) | 2004-02-18 | 2012-02-21 | Roamware, Inc. | Method and system for providing roaming services to inbound roamers using visited network Gateway Location Register |
US7873358B2 (en) * | 2003-08-05 | 2011-01-18 | John Yue Jun Jiang | Method and system for providing inbound traffic redirection solution |
US8583109B2 (en) | 2005-05-09 | 2013-11-12 | Roamware, Inc. | Method and system for exchanging NRTRDE files between a visited network and a home network in real time |
US8238905B2 (en) * | 2003-08-05 | 2012-08-07 | Roamware, Inc. | Predictive intelligence |
US7616954B2 (en) * | 2003-08-05 | 2009-11-10 | Roamware, Inc. | Method and system for providing GSMA IR. 73 SoR compliant cellular traffic redirection |
SG145763A1 (en) * | 2003-08-13 | 2008-09-29 | Roamware Inc | Signaling gateway with multiple imsi with multiple msisdn (mimm) service in a single sim for multiple roaming partners |
DE10347617A1 (en) * | 2003-10-09 | 2005-05-19 | T-Mobile Deutschland Gmbh | Control of call delivery and call diversion of telecommunications connections, especially in multi-device configurations |
EP1983776B1 (en) | 2004-03-10 | 2010-12-29 | Roamware, Inc. | Inbound Roamer Multimedia Messaging Systems |
US9237430B2 (en) | 2004-10-12 | 2016-01-12 | Mobileum, Inc. | Flash caller ID for roaming |
US7583646B2 (en) * | 2004-10-14 | 2009-09-01 | Alcatel-Lucent Usa Inc. | Method and apparatus for facilitating interaction between a home subscriber server (HSS) and a home location register (HLR) in a legacy network |
WO2006066510A1 (en) * | 2004-12-22 | 2006-06-29 | Huawei Technologies Co., Ltd. | A method and system for realizing one phone multi-number |
US7912504B2 (en) * | 2004-12-30 | 2011-03-22 | Telepo Ab | Alternative routing |
JP4964148B2 (en) * | 2004-12-30 | 2012-06-27 | テレポ アクチボラゲット | Method and server in a cellular telecommunications network provided for different routing |
ES2339699T3 (en) | 2005-03-02 | 2010-05-24 | Roamware, Inc. | CALL CONTROL SYSTEM FOR SUBSCRIBER ENTERING ITINERANCE. |
ES2359736T3 (en) | 2005-03-02 | 2011-05-26 | Roamware, Inc. | DYNAMIC GENERATION OF CSI FOR OUTGOING ITINERANT SUBSCRIBERS. |
US20080272187A1 (en) * | 2005-03-03 | 2008-11-06 | Masao Fujimoto | Electronic Money System, Information Storage Medium, and Mobile Terminal Device |
US7899468B2 (en) | 2005-09-30 | 2011-03-01 | Telecommunication Systems, Inc. | Location sensitive messaging |
US8731585B2 (en) | 2006-02-10 | 2014-05-20 | Telecommunications Systems, Inc. | Intelligent reverse geocoding |
US20070078596A1 (en) | 2005-09-30 | 2007-04-05 | John Grace | Landmark enhanced directions |
KR101276002B1 (en) * | 2005-12-01 | 2013-06-19 | 텔레폰악티에볼라겟엘엠에릭슨(펍) | Call handling for ims registered user |
WO2007089821A2 (en) * | 2006-01-31 | 2007-08-09 | Roamware, Inc. | Caller line identification in mobile number portability |
GB2435156A (en) * | 2006-02-10 | 2007-08-15 | Intellprop Ltd | Communication system for accessing more than one device at a single address |
US8027436B1 (en) * | 2006-04-19 | 2011-09-27 | At&T Mobility Ii Llc | User initiated voice mail reset system |
US8874145B2 (en) * | 2006-08-02 | 2014-10-28 | Telecommunication Systems, Inc. | Personal location code broker |
US7957751B2 (en) * | 2006-08-02 | 2011-06-07 | Telecommunication Systems, Inc. | Personal location code |
US8620380B2 (en) * | 2006-08-29 | 2013-12-31 | Intel Corporation | Subscriber identity module having a plurality of subscriber identities |
US8190174B2 (en) * | 2006-12-22 | 2012-05-29 | Verizon Patent And Licensing Inc. | Method, system, and computer program product for providing location based services |
US8712474B2 (en) * | 2007-04-20 | 2014-04-29 | Telefonaktiebolaget L M Ericsson (Publ) | Secure soft SIM credential transfer |
EP1993310B1 (en) * | 2007-05-16 | 2016-08-10 | Vodafone Libertel B.V. | Handling of reachability of multiple mobile communication units sharing the same user identification code |
US10469556B2 (en) * | 2007-05-31 | 2019-11-05 | Ooma, Inc. | System and method for providing audio cues in operation of a VoIP service |
US9225626B2 (en) * | 2007-06-20 | 2015-12-29 | Ooma, Inc. | System and method for providing virtual multiple lines in a communications system |
US8326353B1 (en) * | 2007-06-27 | 2012-12-04 | ENORCOM Corporation | Customizable mobile device |
US8311513B1 (en) | 2007-06-27 | 2012-11-13 | ENORCOM Corporation | Automated mobile system |
JP4637146B2 (en) * | 2007-07-20 | 2011-02-23 | 株式会社エヌ・ティ・ティ・ドコモ | Communications system |
KR100908353B1 (en) | 2007-08-01 | 2009-07-20 | 에스케이 텔레콤주식회사 | Method and apparatus for processing a call using a universal subscriber identity card in a mobile communication system |
WO2009029296A1 (en) * | 2007-08-31 | 2009-03-05 | At & T Mobility Ii Llc | Enhanced messaging with language translation feature |
EP2037707B1 (en) * | 2007-09-13 | 2010-04-14 | Deutsche Telekom AG | Method for monitoring and identifying radio coverage gaps of a public land mobile network |
US20090168755A1 (en) * | 2008-01-02 | 2009-07-02 | Dennis Peng | Enforcement of privacy in a VoIP system |
US8515021B2 (en) * | 2008-02-25 | 2013-08-20 | Ooma, Inc. | System and method for providing personalized reverse 911 service |
US8266307B2 (en) * | 2008-05-12 | 2012-09-11 | Nokia Corporation | Method, system, and apparatus for access of network services using subscriber identities |
WO2010002382A1 (en) * | 2008-06-30 | 2010-01-07 | At&T Mobility Ii Llc | Call handling treatment for voicemail systems |
DE102008048513A1 (en) * | 2008-09-23 | 2010-03-25 | Giesecke & Devrient Gmbh | Data communication in a telemetry system |
US20100121744A1 (en) * | 2008-11-07 | 2010-05-13 | At&T Intellectual Property I, L.P. | Usage data monitoring and communication between multiple devices |
KR20100098797A (en) * | 2009-03-02 | 2010-09-10 | 삼성전자주식회사 | Apparatus and method for operating dual mode of portable terminal |
US9369938B2 (en) * | 2009-03-31 | 2016-06-14 | Microsoft Technology Licensing, Llc | Subscriber identity module (SIM) for mobile stations |
US9736675B2 (en) * | 2009-05-12 | 2017-08-15 | Avaya Inc. | Virtual machine implementation of multiple use context executing on a communication device |
KR101854132B1 (en) * | 2009-09-21 | 2018-05-03 | 삼성전자주식회사 | Apparatus and method for selecting sim in portable terminal |
KR101683883B1 (en) * | 2009-12-31 | 2016-12-08 | 삼성전자주식회사 | Method and system for supporting security in mobile telecommunication system |
US9372885B2 (en) | 2010-06-11 | 2016-06-21 | Doat Media Ltd. | System and methods thereof for dynamically updating the contents of a folder on a device |
GB2494598A (en) | 2010-06-11 | 2013-03-13 | Doat Media Ltd | A system and methods thereof for enhancing a user's search experience |
US9529918B2 (en) | 2010-06-11 | 2016-12-27 | Doat Media Ltd. | System and methods thereof for downloading applications via a communication network |
US9141702B2 (en) | 2010-06-11 | 2015-09-22 | Doat Media Ltd. | Method for dynamically displaying a personalized home screen on a device |
US9552422B2 (en) | 2010-06-11 | 2017-01-24 | Doat Media Ltd. | System and method for detecting a search intent |
US10713312B2 (en) | 2010-06-11 | 2020-07-14 | Doat Media Ltd. | System and method for context-launching of applications |
US9665647B2 (en) | 2010-06-11 | 2017-05-30 | Doat Media Ltd. | System and method for indexing mobile applications |
US9639611B2 (en) * | 2010-06-11 | 2017-05-02 | Doat Media Ltd. | System and method for providing suitable web addresses to a user device |
US9069443B2 (en) | 2010-06-11 | 2015-06-30 | Doat Media Ltd. | Method for dynamically displaying a personalized home screen on a user device |
CN101977412B (en) * | 2010-07-23 | 2013-01-09 | 展讯通信(上海)有限公司 | Application processor, modem and communication method therebetween |
US8862161B2 (en) * | 2010-10-12 | 2014-10-14 | Qualcomm Incorporated | Method and apparatus for efficient idle operation in a dual-SIM CDMA 1X mobile station |
US8863256B1 (en) | 2011-01-14 | 2014-10-14 | Cisco Technology, Inc. | System and method for enabling secure transactions using flexible identity management in a vehicular environment |
CN102083200A (en) * | 2011-01-28 | 2011-06-01 | 中兴通讯股份有限公司 | Method and system for registering multi-mode, multi-standby and multi-card terminal |
US9858342B2 (en) | 2011-03-28 | 2018-01-02 | Doat Media Ltd. | Method and system for searching for applications respective of a connectivity mode of a user device |
US9763080B2 (en) | 2011-12-23 | 2017-09-12 | Nokia Technologies Oy | Method and apparatus for selectively activating multiple subscriber identity modules |
ES2661115T3 (en) * | 2012-03-06 | 2018-03-27 | Telefónica Germany GmbH & Co. OHG | Establishing calls to an active SIM card identifier in a mobile communications network |
US9258744B2 (en) | 2012-08-29 | 2016-02-09 | At&T Mobility Ii, Llc | Sharing of network resources within a managed network |
CN103905660B (en) * | 2012-12-24 | 2017-05-31 | 中兴通讯股份有限公司 | Two phones just one number associated call method, device and application server |
US9386148B2 (en) | 2013-09-23 | 2016-07-05 | Ooma, Inc. | Identifying and filtering incoming telephone calls to enhance privacy |
US9560198B2 (en) | 2013-09-23 | 2017-01-31 | Ooma, Inc. | Identifying and filtering incoming telephone calls to enhance privacy |
US9445385B2 (en) * | 2014-02-25 | 2016-09-13 | Qualcomm Incorporated | System and methods for improving network registration for all SIMs of a multi-SIM device using a dynamically-determined registration order |
US10769931B2 (en) | 2014-05-20 | 2020-09-08 | Ooma, Inc. | Network jamming detection and remediation |
US10553098B2 (en) | 2014-05-20 | 2020-02-04 | Ooma, Inc. | Appliance device integration with alarm systems |
US9633547B2 (en) | 2014-05-20 | 2017-04-25 | Ooma, Inc. | Security monitoring and control |
KR102150349B1 (en) | 2014-05-29 | 2020-09-01 | 삼성전자주식회사 | Method and apparatus for transmitting and receiving voice call in communication system |
US11330100B2 (en) | 2014-07-09 | 2022-05-10 | Ooma, Inc. | Server based intelligent personal assistant services |
TWI548298B (en) * | 2014-08-13 | 2016-09-01 | 合發昌業有限公司 | System, method, server, and application for communication |
US10255429B2 (en) | 2014-10-03 | 2019-04-09 | Wells Fargo Bank, N.A. | Setting an authorization level at enrollment |
US9723462B2 (en) | 2014-11-07 | 2017-08-01 | At&T Intellectual Property I, L.P. | Cloud-based device twinning |
FR3028705B1 (en) * | 2014-11-14 | 2018-03-02 | Oberthur Technologies | EUICC CARD STORING SHORT NUMBERS PER SUBSCRIBER PROFILE TO NOTIFY SUBSCRIPTION MANAGEMENT SERVER |
US9615250B2 (en) * | 2014-12-16 | 2017-04-04 | Microsoft Technology Licensing, Llc | Subscriber identification module pooling |
US10743181B1 (en) | 2014-12-23 | 2020-08-11 | Wells Fargo Bank, N.A. | System for binding multiple sim cards to an electronic device |
US9520911B2 (en) | 2014-12-23 | 2016-12-13 | Wellsfargo Bank, N.A. | System for binding multiple SIM cards to an electronic device |
US10771396B2 (en) | 2015-05-08 | 2020-09-08 | Ooma, Inc. | Communications network failure detection and remediation |
US9521069B2 (en) | 2015-05-08 | 2016-12-13 | Ooma, Inc. | Managing alternative networks for high quality of service communications |
US11171875B2 (en) | 2015-05-08 | 2021-11-09 | Ooma, Inc. | Systems and methods of communications network failure detection and remediation utilizing link probes |
CN115866578A (en) | 2015-05-08 | 2023-03-28 | 深圳市斯凯荣科技有限公司 | Virtual subscriber identity module for mobile communication device |
US10009286B2 (en) | 2015-05-08 | 2018-06-26 | Ooma, Inc. | Communications hub |
US10911368B2 (en) | 2015-05-08 | 2021-02-02 | Ooma, Inc. | Gateway address spoofing for alternate network utilization |
US10567949B2 (en) * | 2015-07-16 | 2020-02-18 | T-Mobile Usa, Inc. | MMS termination on different networks |
US10116796B2 (en) | 2015-10-09 | 2018-10-30 | Ooma, Inc. | Real-time communications-based internet advertising |
CN106255074B (en) * | 2016-07-27 | 2019-12-03 | Oppo广东移动通信有限公司 | A kind of group's method for building up and device |
CN108377575B (en) * | 2016-11-08 | 2020-07-24 | 展讯通信(上海)有限公司 | Multi-card mobile terminal and service processing method thereof |
CN108377479B (en) | 2016-11-08 | 2021-03-23 | 展讯通信(上海)有限公司 | Multi-card mobile terminal and service processing method and device thereof |
CN108377225B (en) | 2016-11-14 | 2021-04-02 | 展讯通信(上海)有限公司 | Multi-channel terminal service processing method and device |
KR102293683B1 (en) | 2017-02-13 | 2021-08-26 | 삼성전자 주식회사 | Apparatus and Methods for Access Control on eSIM |
US11425140B1 (en) * | 2017-05-30 | 2022-08-23 | Amazon Technologies, Inc. | Secure and efficient cross-service sharing of subscriber data |
FI128024B (en) | 2018-03-15 | 2019-08-15 | Telia Co Ab | Connection establishment |
CN108616869B (en) * | 2018-03-22 | 2020-06-09 | 深圳市优克联新技术有限公司 | Multi-card multi-standby system, method, device, communication device and computer readable storage medium |
US11812515B2 (en) | 2018-05-01 | 2023-11-07 | Intermetro Communications, Inc. | Multiple active network wireless device using a shadow number |
MX2020011466A (en) | 2018-05-01 | 2021-03-31 | Intermetro Communications Inc | Multiple active network wireless device. |
WO2020231758A1 (en) * | 2019-05-10 | 2020-11-19 | Intermetro Communications, Inc. | Multiple active network wireless device using a shadow number |
CN111918275B (en) * | 2020-09-03 | 2023-04-11 | 中国联合网络通信集团有限公司 | Method and device for transmitting data |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7680491B2 (en) * | 2003-05-15 | 2010-03-16 | Redknee Inc. | Method and system allowing for one mobile phone number (MSISDN) to be associated with a plurality of wireless devices (‘Multi-SIM’) |
Family Cites Families (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US3319789A (en) | 1964-04-09 | 1967-05-16 | United States Steel Corp | Method of filtering liquid from solid particles |
SE470041B (en) * | 1992-10-01 | 1993-10-25 | Nordictel Ab | Digital mobile telephone system in which each subscription is assigned a subscriber number and multiple subscriber cards (SIM) |
JPH08140136A (en) * | 1994-11-07 | 1996-05-31 | Oki Electric Ind Co Ltd | Communication system |
US5943620A (en) * | 1996-12-09 | 1999-08-24 | Ericsson Inc. | Method for associating one directory number with two mobile stations within a mobile telecommunications network |
US6393275B1 (en) * | 1996-12-27 | 2002-05-21 | At&T Corp. | Cellular extension service using single line and multiple cellular telephone sets |
US6181934B1 (en) * | 1998-11-13 | 2001-01-30 | Ericsson Inc. | System and method for providing efficient signaling for a positioning request and an indication of when a mobile station becomes available for location services |
DE69837765T2 (en) * | 1998-12-22 | 2008-01-17 | Naxos Data LLC, Las Vegas | Method for routing an incoming call, telecommunication terminal and device for selecting a terminal suitable for the type of call |
DE50008167D1 (en) * | 1999-01-22 | 2004-11-18 | Siemens Ag | Mobile network and method for controlling the accessibility of terminals of a mobile network |
DE69906592T2 (en) * | 1999-05-05 | 2004-01-29 | Nokia Corp | METHOD FOR DETERMINING A MOBILE STATION |
US6141564A (en) | 1999-09-30 | 2000-10-31 | Motorola, Inc. | Method of sharing a SIM card between two masters |
EP1098543A1 (en) | 1999-11-03 | 2001-05-09 | Guala Dispensing S.P.A. | Multi-card cellular telphone apparatus |
US6937713B1 (en) * | 1999-12-30 | 2005-08-30 | At&T Corp. | IP call forward profile |
US6466804B1 (en) | 2000-08-25 | 2002-10-15 | Motorola, Inc. | Method and apparatus for remote multiple access to subscriber identity module |
US6912389B2 (en) * | 2001-01-12 | 2005-06-28 | Lucent Technologies Inc. | Interworking and interoperability of GPRS systems with systems of other technology families |
TW508933B (en) | 2001-04-23 | 2002-11-01 | Inventec Appliances Corp | Method for automatically switching SIM card of mobile phone and device therefor |
GB2375261B (en) | 2001-04-30 | 2004-10-13 | Nokia Corp | Radiotelephone system |
US20030125072A1 (en) * | 2002-01-02 | 2003-07-03 | Dent Paul W. | Method of providing multiple mobile telephones with the same telephone number |
US7127051B2 (en) * | 2002-09-17 | 2006-10-24 | Bellsouth Intellectual Property Corporation | System and method for providing advanced telephony services using a virtual telephone number |
US7369839B2 (en) * | 2003-03-14 | 2008-05-06 | Nokia Siemens Networks Oy | Method and apparatus for determining individual or common mobile subscriber number in mobile network for handling multiple subscribers having the same calling line identity |
US20040185888A1 (en) * | 2003-03-18 | 2004-09-23 | Nokia Corporation | Solving mobile station identity in a multi-SIM situation |
-
2003
- 2003-05-15 US US10/438,097 patent/US7680491B2/en active Active
-
2004
- 2004-05-14 EP EP04076444A patent/EP1631106A3/en not_active Withdrawn
- 2004-05-14 EP EP12175426A patent/EP2509349A1/en not_active Withdrawn
-
2010
- 2010-02-04 US US12/700,331 patent/US20100136982A1/en not_active Abandoned
-
2012
- 2012-05-01 US US13/461,330 patent/US20120214459A1/en not_active Abandoned
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7680491B2 (en) * | 2003-05-15 | 2010-03-16 | Redknee Inc. | Method and system allowing for one mobile phone number (MSISDN) to be associated with a plurality of wireless devices (‘Multi-SIM’) |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20100088374A1 (en) * | 2007-02-16 | 2010-04-08 | Astroem Bo | Supplementary Services in Communication Networks |
US8489682B2 (en) * | 2007-02-16 | 2013-07-16 | Telefonaktiebolaget L M Ericsson (Publ) | Supplementary services in communication networks |
US20110167118A1 (en) * | 2010-01-06 | 2011-07-07 | Yigang Cai | Message waiting notification to external message centers |
US8549083B2 (en) * | 2010-01-06 | 2013-10-01 | Alcatel Lucent | Message waiting notification to external message centers |
TWI548260B (en) * | 2013-06-14 | 2016-09-01 | 國立臺灣大學 | A system and method of trigger service |
Also Published As
Publication number | Publication date |
---|---|
US7680491B2 (en) | 2010-03-16 |
US20040229601A1 (en) | 2004-11-18 |
EP1631106A2 (en) | 2006-03-01 |
EP2509349A1 (en) | 2012-10-10 |
US20100136982A1 (en) | 2010-06-03 |
EP1631106A3 (en) | 2010-03-24 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7680491B2 (en) | Method and system allowing for one mobile phone number (MSISDN) to be associated with a plurality of wireless devices (‘Multi-SIM’) | |
US8175622B2 (en) | Method and system for keeping all phone numbers active while roaming with diverse operator subscriber identity modules | |
US8478277B2 (en) | Network-based system for rerouting phone calls from phone networks to VoIP clients for roamers and subscribers who do not answer | |
US6810257B1 (en) | Method and apparatus for providing partitioned telecommunication services | |
CN101341764B (en) | Service of intelligent network | |
AU755380B2 (en) | Short message service notification forwarded between multiple short message service centers | |
US6622016B1 (en) | System for controlled provisioning of telecommunications services | |
US20080207181A1 (en) | Method and system for applying value added services on messages sent to a subscriber without affecting the subscriber's mobile communication | |
US6826397B1 (en) | System and method to notify subscribers of call terminating treatment | |
EP2061284B1 (en) | Method and System providing a short message (SMS) forwarding unconditional service | |
US20090111489A1 (en) | Telecommunications services apparatus and methods | |
US8909266B2 (en) | Methods, systems, and computer readable media for short message service (SMS) forwarding | |
US6473422B2 (en) | Communications network and method for screening incoming circuit switched calls | |
US20120320899A1 (en) | Routing Call To UMA-Capable Terminals Using A Geographic Number | |
EP2547131A1 (en) | Routing call to UMA-capable terminals using a geographic number | |
EP1985130B1 (en) | Keeping all phone numbers active | |
WO2001050804A1 (en) | Redirection at terminating call setup for dual-mode mobile stations operating through radio access networks having non-integrated air interface standards | |
US7174177B1 (en) | System and method for providing indication of maximum teleservice payload size in a wireless communication network | |
GB2435156A (en) | Communication system for accessing more than one device at a single address | |
WO2005004511A1 (en) | Additional number provision in cellular telecommunications network | |
EP1681894A2 (en) | Telecommunications services apparatus and method | |
WO2000045611A2 (en) | Handling of a digital wireless office system user profile | |
EP1494493B1 (en) | Method and devices for handling subscriber information of a subscriber of a mobile radio network | |
MXPA00002996A (en) | System and method for providing restrictions on mobile-originated calls | |
CN101835291A (en) | The intelligent network service |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: REDKNEE INC., CANADA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ZABAWSKYJ, BOHDAN KONSTANTYN;TAIT, STEVEN ROBERT;RAHIM, RUBENS;AND OTHERS;SIGNING DATES FROM 20050422 TO 20050423;REEL/FRAME:028456/0540 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |