WO2000027160A1 - Methods and systems to obtain a tldn for a home system in response to a call received for a wireless unit roaming in a visited system - Google Patents

Methods and systems to obtain a tldn for a home system in response to a call received for a wireless unit roaming in a visited system Download PDF

Info

Publication number
WO2000027160A1
WO2000027160A1 PCT/US1999/026193 US9926193W WO0027160A1 WO 2000027160 A1 WO2000027160 A1 WO 2000027160A1 US 9926193 W US9926193 W US 9926193W WO 0027160 A1 WO0027160 A1 WO 0027160A1
Authority
WO
WIPO (PCT)
Prior art keywords
msc
tldn
international gateway
wireless unit
request
Prior art date
Application number
PCT/US1999/026193
Other languages
French (fr)
Other versions
WO2000027160A9 (en
Inventor
Robert Andrew Adamany
Richard L. Charbono, Jr.
Edward Lawrence Didion
Ann M. Catanese
Original Assignee
Bellsouth Intellectual Property Corporation
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Bellsouth Intellectual Property Corporation filed Critical Bellsouth Intellectual Property Corporation
Priority to AU30985/00A priority Critical patent/AU3098500A/en
Publication of WO2000027160A1 publication Critical patent/WO2000027160A1/en
Publication of WO2000027160A9 publication Critical patent/WO2000027160A9/en

Links

Classifications

    • 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/08—Mobility data transfer
    • H04W8/12—Mobility data transfer between location registers or mobility servers
    • H—ELECTRICITY
    • H01—ELECTRIC ELEMENTS
    • H01L—SEMICONDUCTOR DEVICES NOT COVERED BY CLASS H10
    • H01L23/00—Details of semiconductor or other solid state devices
    • H01L23/28—Encapsulations, e.g. encapsulating layers, coatings, e.g. for protection
    • H01L23/31—Encapsulations, e.g. encapsulating layers, coatings, e.g. for protection characterised by the arrangement or shape
    • H01L23/3107—Encapsulations, e.g. encapsulating layers, coatings, e.g. for protection characterised by the arrangement or shape the device being completely enclosed
    • H—ELECTRICITY
    • H01—ELECTRIC ELEMENTS
    • H01L—SEMICONDUCTOR DEVICES NOT COVERED BY CLASS H10
    • H01L23/00—Details of semiconductor or other solid state devices
    • H01L23/34—Arrangements for cooling, heating, ventilating or temperature compensation ; Temperature sensing arrangements
    • H01L23/42—Fillings or auxiliary members in containers or encapsulations selected or arranged to facilitate heating or cooling
    • H01L23/433—Auxiliary members in containers characterised by their shape, e.g. pistons
    • H01L23/4334—Auxiliary members in encapsulations
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/12—Detection or prevention of fraud
    • H04W12/126—Anti-theft arrangements, e.g. protection against subscriber identity module [SIM] cloning
    • H—ELECTRICITY
    • H01—ELECTRIC ELEMENTS
    • H01L—SEMICONDUCTOR DEVICES NOT COVERED BY CLASS H10
    • H01L2224/00—Indexing scheme for arrangements for connecting or disconnecting semiconductor or solid-state bodies and methods related thereto as covered by H01L24/00
    • H01L2224/01—Means for bonding being attached to, or being formed on, the surface to be connected, e.g. chip-to-package, die-attach, "first-level" interconnects; Manufacturing methods related thereto
    • H01L2224/02—Bonding areas; Manufacturing methods related thereto
    • H01L2224/04—Structure, shape, material or disposition of the bonding areas prior to the connecting process
    • H01L2224/05—Structure, shape, material or disposition of the bonding areas prior to the connecting process of an individual bonding area
    • H01L2224/0554—External layer
    • H01L2224/0555—Shape
    • H01L2224/05552—Shape in top view
    • H01L2224/05553—Shape in top view being rectangular
    • H—ELECTRICITY
    • H01—ELECTRIC ELEMENTS
    • H01L—SEMICONDUCTOR DEVICES NOT COVERED BY CLASS H10
    • H01L2224/00—Indexing scheme for arrangements for connecting or disconnecting semiconductor or solid-state bodies and methods related thereto as covered by H01L24/00
    • H01L2224/01—Means for bonding being attached to, or being formed on, the surface to be connected, e.g. chip-to-package, die-attach, "first-level" interconnects; Manufacturing methods related thereto
    • H01L2224/42—Wire connectors; Manufacturing methods related thereto
    • H01L2224/44—Structure, shape, material or disposition of the wire connectors prior to the connecting process
    • H01L2224/45—Structure, shape, material or disposition of the wire connectors prior to the connecting process of an individual wire connector
    • H01L2224/45001—Core members of the connector
    • H01L2224/4501—Shape
    • H01L2224/45012—Cross-sectional shape
    • H01L2224/45015—Cross-sectional shape being circular
    • H—ELECTRICITY
    • H01—ELECTRIC ELEMENTS
    • H01L—SEMICONDUCTOR DEVICES NOT COVERED BY CLASS H10
    • H01L2224/00—Indexing scheme for arrangements for connecting or disconnecting semiconductor or solid-state bodies and methods related thereto as covered by H01L24/00
    • H01L2224/01—Means for bonding being attached to, or being formed on, the surface to be connected, e.g. chip-to-package, die-attach, "first-level" interconnects; Manufacturing methods related thereto
    • H01L2224/42—Wire connectors; Manufacturing methods related thereto
    • H01L2224/44—Structure, shape, material or disposition of the wire connectors prior to the connecting process
    • H01L2224/45—Structure, shape, material or disposition of the wire connectors prior to the connecting process of an individual wire connector
    • H01L2224/45001—Core members of the connector
    • H01L2224/45099—Material
    • H01L2224/451—Material with a principal constituent of the material being a metal or a metalloid, e.g. boron (B), silicon (Si), germanium (Ge), arsenic (As), antimony (Sb), tellurium (Te) and polonium (Po), and alloys thereof
    • H01L2224/45138—Material with a principal constituent of the material being a metal or a metalloid, e.g. boron (B), silicon (Si), germanium (Ge), arsenic (As), antimony (Sb), tellurium (Te) and polonium (Po), and alloys thereof the principal constituent melting at a temperature of greater than or equal to 950°C and less than 1550°C
    • H01L2224/45144—Gold (Au) as principal constituent
    • H—ELECTRICITY
    • H01—ELECTRIC ELEMENTS
    • H01L—SEMICONDUCTOR DEVICES NOT COVERED BY CLASS H10
    • H01L2224/00—Indexing scheme for arrangements for connecting or disconnecting semiconductor or solid-state bodies and methods related thereto as covered by H01L24/00
    • H01L2224/01—Means for bonding being attached to, or being formed on, the surface to be connected, e.g. chip-to-package, die-attach, "first-level" interconnects; Manufacturing methods related thereto
    • H01L2224/42—Wire connectors; Manufacturing methods related thereto
    • H01L2224/47—Structure, shape, material or disposition of the wire connectors after the connecting process
    • H01L2224/48—Structure, shape, material or disposition of the wire connectors after the connecting process of an individual wire connector
    • H01L2224/4805—Shape
    • H01L2224/4809—Loop shape
    • H01L2224/48091—Arched
    • H—ELECTRICITY
    • H01—ELECTRIC ELEMENTS
    • H01L—SEMICONDUCTOR DEVICES NOT COVERED BY CLASS H10
    • H01L2224/00—Indexing scheme for arrangements for connecting or disconnecting semiconductor or solid-state bodies and methods related thereto as covered by H01L24/00
    • H01L2224/01—Means for bonding being attached to, or being formed on, the surface to be connected, e.g. chip-to-package, die-attach, "first-level" interconnects; Manufacturing methods related thereto
    • H01L2224/42—Wire connectors; Manufacturing methods related thereto
    • H01L2224/47—Structure, shape, material or disposition of the wire connectors after the connecting process
    • H01L2224/48—Structure, shape, material or disposition of the wire connectors after the connecting process of an individual wire connector
    • H01L2224/481—Disposition
    • H01L2224/48151—Connecting between a semiconductor or solid-state body and an item not being a semiconductor or solid-state body, e.g. chip-to-substrate, chip-to-passive
    • H01L2224/48221—Connecting between a semiconductor or solid-state body and an item not being a semiconductor or solid-state body, e.g. chip-to-substrate, chip-to-passive the body and the item being stacked
    • H01L2224/48245—Connecting between a semiconductor or solid-state body and an item not being a semiconductor or solid-state body, e.g. chip-to-substrate, chip-to-passive the body and the item being stacked the item being metallic
    • H01L2224/48247—Connecting between a semiconductor or solid-state body and an item not being a semiconductor or solid-state body, e.g. chip-to-substrate, chip-to-passive the body and the item being stacked the item being metallic connecting the wire to a bond pad of the item
    • H—ELECTRICITY
    • H01—ELECTRIC ELEMENTS
    • H01L—SEMICONDUCTOR DEVICES NOT COVERED BY CLASS H10
    • H01L24/00—Arrangements for connecting or disconnecting semiconductor or solid-state bodies; Methods or apparatus related thereto
    • H01L24/01—Means for bonding being attached to, or being formed on, the surface to be connected, e.g. chip-to-package, die-attach, "first-level" interconnects; Manufacturing methods related thereto
    • H01L24/42—Wire connectors; Manufacturing methods related thereto
    • H01L24/47—Structure, shape, material or disposition of the wire connectors after the connecting process
    • H01L24/48—Structure, shape, material or disposition of the wire connectors after the connecting process of an individual wire connector
    • H—ELECTRICITY
    • H01—ELECTRIC ELEMENTS
    • H01L—SEMICONDUCTOR DEVICES NOT COVERED BY CLASS H10
    • H01L2924/00—Indexing scheme for arrangements or methods for connecting or disconnecting semiconductor or solid-state bodies as covered by H01L24/00
    • H01L2924/01—Chemical elements
    • H01L2924/01079—Gold [Au]
    • H—ELECTRICITY
    • H01—ELECTRIC ELEMENTS
    • H01L—SEMICONDUCTOR DEVICES NOT COVERED BY CLASS H10
    • H01L2924/00—Indexing scheme for arrangements or methods for connecting or disconnecting semiconductor or solid-state bodies as covered by H01L24/00
    • H01L2924/10—Details of semiconductor or other solid state devices to be connected
    • H01L2924/102—Material of the semiconductor or solid state bodies
    • H01L2924/1025—Semiconducting materials
    • H01L2924/10251—Elemental semiconductors, i.e. Group IV
    • H01L2924/10253—Silicon [Si]
    • H—ELECTRICITY
    • H01—ELECTRIC ELEMENTS
    • H01L—SEMICONDUCTOR DEVICES NOT COVERED BY CLASS H10
    • H01L2924/00—Indexing scheme for arrangements or methods for connecting or disconnecting semiconductor or solid-state bodies as covered by H01L24/00
    • H01L2924/10—Details of semiconductor or other solid state devices to be connected
    • H01L2924/11—Device type
    • H01L2924/14—Integrated circuits
    • H—ELECTRICITY
    • H01—ELECTRIC ELEMENTS
    • H01L—SEMICONDUCTOR DEVICES NOT COVERED BY CLASS H10
    • H01L2924/00—Indexing scheme for arrangements or methods for connecting or disconnecting semiconductor or solid-state bodies as covered by H01L24/00
    • H01L2924/15—Details of package parts other than the semiconductor or other solid state devices to be connected
    • H01L2924/181—Encapsulation
    • H—ELECTRICITY
    • H01—ELECTRIC ELEMENTS
    • H01L—SEMICONDUCTOR DEVICES NOT COVERED BY CLASS H10
    • H01L2924/00—Indexing scheme for arrangements or methods for connecting or disconnecting semiconductor or solid-state bodies as covered by H01L24/00
    • H01L2924/19—Details of hybrid assemblies other than the semiconductor or other solid state devices to be connected
    • H01L2924/1901—Structure
    • H01L2924/1904—Component type
    • H01L2924/19041—Component type being a capacitor
    • H—ELECTRICITY
    • H01—ELECTRIC ELEMENTS
    • H01L—SEMICONDUCTOR DEVICES NOT COVERED BY CLASS H10
    • H01L2924/00—Indexing scheme for arrangements or methods for connecting or disconnecting semiconductor or solid-state bodies as covered by H01L24/00
    • H01L2924/30—Technical effects
    • H01L2924/301—Electrical effects
    • H01L2924/30107—Inductance
    • H—ELECTRICITY
    • H01—ELECTRIC ELEMENTS
    • H01L—SEMICONDUCTOR DEVICES NOT COVERED BY CLASS H10
    • H01L2924/00—Indexing scheme for arrangements or methods for connecting or disconnecting semiconductor or solid-state bodies as covered by H01L24/00
    • H01L2924/30—Technical effects
    • H01L2924/301—Electrical effects
    • H01L2924/3011—Impedance
    • 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/06—Registration at serving network Location Register, VLR or user mobility server
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • This invention relates to telecommunications, and in particular, to methods and systems for obtaining a temporary location directory number (TLDN) for a home system in response to a call received for a wireless unit that is roaming in a visited system.
  • TLDN temporary location directory number
  • wireless communications are communications that are transmitted through the use of radio frequency (RF) technology.
  • Wireless communications include communications that are transmitted through the use of wireless units such as cellular telephones, mobile telephones, car phones, personal communication service (PCS) units, pagers, and the like.
  • a wireless unit is particularly useful to a person on the move. For example, a person may use his or her wireless unit while driving a car.
  • the wireless communications service to the person's wireless unit is provided typically by a service provider that may also be referred to herein as a carrier.
  • a service provider that may also be referred to herein as a carrier.
  • a person who obtains wireless communications service from a service provider is generally referred to herein as a subscriber, a customer, or a user.
  • a subscriber may make or receive communications with his or her wireless unit.
  • communication is used herein to refer to any call, message, announcement or other exchange of data or information, whether analog or digital, that may be received on a wireless unit or transmitted from a wireless unit, and/or may be received or transmitted from a wireless unit that is operating as part of any other device such as a computer.
  • a base station in or serving a predetermined geographic area wherein the subscriber is located receives the communication.
  • the geographic area that is served with wireless communications service by the carrier is referred to herein as the service area of the service provider.
  • the service provider typically operates a wireless communications network or system to provide wireless communications service to the geographic area.
  • the wireless communications network includes the referenced base station, and other elements such as mobile switching centers (MSCs).
  • the wireless communications network also includes elements that interface with the public switched telephone network (PSTN), and other networks and systems so as to provide for communications between and among parties using wireless units and/or using wireline units and/or other communication devices.
  • PSTN public switched telephone network
  • the base station Upon receipt of a communication from a wireless unit of a user, the base station transmits the communication to a mobile switching center (MSC) (sometimes referred to as a mobile-service switching center or mobile telecommunications switching office (MTSO)).
  • MSC mobile switching center
  • MTSO mobile telecommunications switching office
  • the MSC further routes the communication as appropriate. This routing may take the communication to and through the PSTN, to and through the same wireless communications system, to and through another wireless communications system, to and through other communications systems, or combinations thereof.
  • a subscriber may receive a communication on his or her wireless unit from a caller.
  • the caller typically directs his or her communication to the number associated with the subscriber's wireless unit, which is referred to herein as the mobile number (MN) of the wireless unit.
  • MN mobile number
  • the mobile number may be the mobile identification number (MIN) of the wireless unit.
  • the communication is routed through the PSTN, through other networks, and/or wireless communications systems until the communication reaches the MSC serving the subscriber's wireless unit.
  • This MSC may be referred to as the serving MSC or the serving switch.
  • the serving MSC then further routes the communication to the wireless unit.
  • a wireless unit is particularly useful when a subscriber is on the move such as when the subscriber is driving a car or otherwise travelling.
  • the subscriber's mobility may take the subscriber out of the service area served by the service provider from whom the subscriber subscribes.
  • the subscriber's mobility may take the subscriber out of his or her home service area served by his or her home service provider or home carrier.
  • the subscriber may move so as to be located in another service area that is served by a different service provider with whom the subscriber has no business relationship.
  • the subscriber is said to be "roaming" out of his or her home service area and may be referred to as a "roamer", "roaming subscriber” in a visited service area that is served by a visited system.
  • service providers have agreed to follow certain procedures in the processing of communications with respect to each other's subscribers.
  • a roaming subscriber is validated and may be authenticated by the visited system, which also may be referred to as the visited service provider. Both of these processes (validation and authentication) are used to prevent fraudulent use of wireless units and for other reasons. General descriptions of these processes and other information about wireless communications systems may be found in the book entitled Cellular and PCS - The Big Picture by Lawrence Harte, Steve Prokup and Richard Levine (McGraw-Hill 1997).
  • Roamer validation and/or authentication generally is the mechanism for providing information to the subscriber's home system as to the subscriber's location in a visited system. It is important to a home system to have information as to a subscriber's location because the home system is the initial recipient of calls that are directed to the mobile number of a subscriber's wireless unit. The home system then attempts to route a call received for its subscriber to the subscriber's roaming location. In particular, when a home system receives a call for its subscriber, the MSC in that home system (MSC-H) checks its HLR to determine if the wireless unit is operating in another system.
  • MSC-H home system
  • the home MSC (MSC-H) then sends a request to the visited MSC (MSC-V) for a temporary location directory number (TLDN)(also referred to as a temporary line directory number).
  • TLDN temporary location directory number
  • the TLDN is used with respect to the received call so that the call may be directed to the MSC-V for further routing to the wireless unit of the subscriber.
  • the TLDN generally is cross-referenced with the MIN of the visiting wireless unit in the VLR of the serving MSC in the visited system.
  • the home system Upon receipt of the TLDN from the MSC-V, the home system then routes the call that had been dialed to the subscriber's mobile number based on the TLDN.
  • the use of the TLDN routes the call to the appropriate MSC in a visited system.
  • the visited system receives the call and finds the TLDN number is listed in its VLR.
  • the visited system pages the wireless unit using the MIN which is stored in the VLR. When the subscribe
  • the above described process of using a TLDN is carried out generally with respect to communications that occur within the United States.
  • the processes generally work well within the United States.
  • wireless communications between the United States and foreign countries or wireless communications between foreign countries have been problematic. Problems arise because the processes described above may not be carried out because of the differences in the wireless systems in the respective countries.
  • a wireless system and its related wireline system in a particular country may not be networked with the wireless system and its related wireline system in a foreign country.
  • a wireless system and its related wireline system may be organized completely differently from the way a wireless system and its related wireline system is organized in another country.
  • An example of this difference in organization is the assignment of numbers for use in making calls and associated with respective communication units within a country.
  • an area code is included as part of a directory number associated with a wireline unit such that an area code corresponds to a general geographic area or area served by a particular service provider. Area codes are not generally duplicated within the United States.
  • a communication may be routed through the United States on the basis of the area code, and then the remaining numbers of the directory number.
  • a difficulty in processing communications arises between countries or between different communication systems having different numbering systems for assignment of directory or mobile numbers to communication devices.
  • One way which has been used to smooth over the differences in communication processing has been the use of prefix dialing numbers, which precede a directory number or mobile number for long distance calls.
  • a long distance call may be dialed by first dialing an access code of "1".
  • a long distance call may be dialed by first dialing an access code of "Oi l”, and then by dialing a country code (such as "44" for England) corresponding to the country including the destination of the call.
  • the access code of "Oi l” is sometimes referred to as the international access code because it is used in the United States with respect to calls whose destinations are generally outside the United States.
  • a communication from the United States to England may be dialed by first dialing the prefix dialing numbers of "Oi l 44" and then the directory number assigned to the called party pursuant to the numbering scheme used by the appropriate system in England.
  • the TLDN that is provided from a wireless system in a foreign country where a roamer is located may be insufficient or invalid to accomplish routing of a communication from the roamer's home system to the visited system in the foreign country.
  • the TLDN may be insufficient because the provided TLDN generally is based on the numbering scheme in use in the country or geographic area wherein the MSC-V is located.
  • the TLDN may be insufficient to route a call between foreign countries because the TLDN may not include information such as prefix dialing numbers, etc.
  • the use of the TLDN provided by the visited system may not result in the routing of the communication to the foreign country. In fact, the use of the TLDN may misroute the communication to some other foreign country.
  • MSC-V Signaling System 7
  • STP service transfer point
  • the MSC-H receives the message, checks out the message with respect to the roamer in a validation process, and stores information as necessary with respect to the location of the roamer in the visited system.
  • the information that is stored with respect to the location of the roamer is the point code (also referred to as an originating point code (OPC)) that arrives in the message and that indicates the message originated with a particular MSC-V.
  • An MSC like other network elements, is assigned a unique point code so that a determination may be made as to the originating network element of a message. If the roamer is valid, then the MSC-H sends a response message (typically a registration notification (regnot) response message) to the MSC-V.
  • the MSC-V receives the response, and if appropriate, registers the roamer in the visited system, and the registration process ends. Assuming connectivity between the wireless communications systems of country
  • a and country B assume the registered roamer is called by a caller in the United States.
  • the caller dials the mobile number of the wireless unit of the roamer.
  • the call is received at the MSC-H (home MSC) of the roamer.
  • the MSC-H has information that the roamer is located in an area served by MSC-V.
  • the MSC-H requests the MSC-V for a TLDN so that the call from the caller may be appropriately routed.
  • the MSC-V provides a TLDN based on the numbering system assigned by the wireless system in country B.
  • the MSC-H tries to use the TLDN to route the call.
  • the call cannot be put through because the TLDN is insufficient or invalid.
  • the numbers or other information that are the components of the TLDN may be incorrect, or may not have enough components or digits, or otherwise may not be recognized by the home system.
  • the TLDN may include components or digits that result in the routing of the call to a country or place other than country B.
  • the TLDN does not provide a mechanism or other information for routing the call from the caller to the roamer in country B. For example, assume the caller to be in the United States and the roamer to be in Chile. The MSC-V in Chile does not provide the MSC-H in the United States with information in the TLDN that the roamer is located in Chile.
  • the TLDN is provided as if the MSC-H were also located in Chile.
  • a Chilean MSC-V may include a component of "730" in the TLDN in the place (from the perspective of the wireless communications systems in the United States) of the country code.
  • "569" is the country code for Chile in the system followed in the United States. Therefore, the call cannot be put through, or at least cannot be routed to Chile.
  • the call may be routed from the MSC-H in the United States to whatever country includes a country code of "730" in its TLDN.
  • a roamer in country B generally is unable to receive calls in country B because, inter alia, of the insufficiencies and invalidities in the provision of TLDN information from the wireless communications systems in country B to the home system of the roamer.
  • Chile and the United States are used as examples in explaining the insufficiencies of the TLDN provision.
  • TLDN provision problems exist in calls between other countries, and in some cases, between systems in the same country.
  • the present inventions include methods, systems, and apparatus that allow a home wireless system to obtain a temporary location directory number (TLDN) so that the home wireless system may appropriately route a call received for a wireless unit roaming in a visited wireless system.
  • TLDN temporary location directory number
  • the present inventions correct or otherwise solve the problems associated with the insufficiency or invalidity in the provision of TLDNs that are exchanged between wireless communications systems which are located respectively in countries or systems having disparate numbering systems or other disparate processes related to the exchange of TLDNs.
  • the MSC-H in response to a call directed to a mobile number of a wireless unit served by a home service provider, and particularly by a MSC-H, the MSC-H routes a request for a TLDN to an international gateway.
  • the international gateway creates a new request or alters the request and then routes the new or altered request to the appropriate MSC-V serving the wireless unit in the visited system.
  • the international gateway had retained information on the location of the wireless unit roaming in a visited system when the wireless unit registered in the visited system.
  • the MSC-V provides the TLDN in a message to the international gateway.
  • the international gateway may add additional information to the TLDN.
  • the international gateway may add prefix dialing numbers as appropriate to the TLDN.
  • the prefix dialing numbers may include an international or other access code and a country code.
  • the TLDN is corrected so that the MSC-H may properly route the call to the wireless unit roaming in the visited system.
  • the new (or altered) message provides appropriate information so as to accomplish ultimately the routing of the call from the country of the MSC-H to the MSC-V where the roamer is roaming.
  • FIG. 1 is a block diagram illustrating use of an exemplary international gateway in an exemplary environment.
  • Fig. 2 is a flow diagram illustrating an exemplary method of the present invention.
  • Fig. 3 is a block diagram illustrating an exemplary international gateway.
  • Fig. 4 is a diagram of logical software entities in an exemplary international gateway.
  • the present inventions include methods, systems, and apparatus that allow a home wireless system to obtain a temporary location directory number (TLDN) so that the home wireless system may appropriately route a call received for a wireless unit roaming in a visited wireless system.
  • TLDN temporary location directory number
  • the present inventions correct or otherwise solve the problems associated with the insufficiency or invalidity in the provision of TLDNs that are exchanged between wireless communications systems which are located respectively in countries or systems having disparate numbering systems or other disparate processes related to the exchange of TLDNs.
  • the exemplary embodiments of the present invention contemplate uses with wireless units such as cell phones and personal communication service (PCS) phones that operate under the standards of Advanced Mobile Phone Service (AMPS), Call Division Multiple Access (CDMA), or Time Division Multiple Access (TDMA). Nonetheless, the principles of the present invention may be applied to other communication devices operating under other standards with the appropriate reconfiguration.
  • AMPS Advanced Mobile Phone Service
  • CDMA Call Division Multiple Access
  • TDMA Time Division Multiple Access
  • Exemplary embodiments of the present invention include an international gateway for use with respect to the referenced wireless communications.
  • the international gateway may be used in wireless communications so as to provide a method, system and/or apparatus to correct or otherwise solve the problems associated with the insufficiency or invalidity in the provision of TLDNs that are exchanged between wireless communications systems which are located respectively in countries or systems having disparate numbering systems or other disparate processes related to the exchange of TLDNs.
  • Exemplary embodiments of the present invention describe the international gateway as a stand-alone unit such as may be embodied by or in a service control point (SCP). But the reader is cautioned the international gateway should not be so limited in embodiment.
  • the international gateway may be incorporated in or as part of another device such as an intelligent peripheral (IP) in a wireless communications system, or in other devices or systems.
  • IP intelligent peripheral
  • the international gateway also may be referred to herein as a personal identification (PIN) validation or authentication platform.
  • the international gateway may be considered a series of functions that may be carried out in a single device or that may be carried out through the use of several devices.
  • the international gateway functions in accordance with Signaling System 7 (SS7) protocols as well as EIA/TIA IS-41 protocols, and thus, may be accessed through the connectivity between and among network elements of wireless communications systems and/or wireline communications systems. Further, the international gateway may be connected to customer service elements of the service provider of the international gateway, and even may be accessed (or partially) accessed by customers of the service provider of the international gateway through the Internet or other communications networks. Generally, customers of the service provider of the international gateway include carriers who provide wireless service to subscribers and who desire to facilitate the provision of wireless service to such subscribers when they are roaming, and particularly roaming in foreign countries or systems.
  • SS7 Signaling System 7
  • EIA/TIA IS-41 EIA/TIA IS-41
  • FIG. 1 An Exemplary International Gateway in an Exemplary Environment
  • Fig. 1 is a block diagram illustrating use of an exemplary international gateway 10 in an exemplary environment including a home system 12 and a visited system 14.
  • the home system 12 generally is a wireless communications system provided by a service provider with whom a subscriber has a relationship such that a wireless unit used by the subscriber typically is registered in a home location register (HLR) 16 of a mobile switching center (MSC-H) 18 when the wireless unit is located in the geographic area served by the MSC-H 18.
  • HLR home location register
  • MSC-H mobile switching center
  • a communication from a caller and directed to the mobile number of the wireless unit is routed to the MSC-H 18 for further routing to the called wireless unit.
  • Fig. 1 also illustrates a visited system 14 including a wireless unit 20 that is roaming or visiting in the visited system 14.
  • the wireless unit 20 When the wireless unit 20 is turned on, typically it provides registration information to a base station 22 serving the cell of the visiting system wherein the wireless unit 20 is roaming.
  • the registration information typically includes the mobile identification number (MIN) for the wireless unit 20.
  • the base station 22 generally provides the registration information to a mobile switching center (MSC-V) 24.
  • MSC-V mobile switching center
  • exemplary embodiments of the present invention allow a roamer, who is based in country (or system) A, who has registered in a visited system, and who has satisfied other processes (such as any necessary authentication or verification processes) to receive calls while roaming in a country (or system) B.
  • An exemplary method with respect to the receipt of a call by a registered roamer in country B is illustrated in Fig. 3. Assume the registered roamer is called by a caller. As illustrated in Fig. 3, after start 98, in block 100 the caller dials the mobile number (MN) of the wireless unit of the roamer. In block 102, the call is received at the MSC-H (home MSC) of the roamer.
  • MN mobile number
  • the MSC-H has stored information with respect to the registration of the roamer in a visited system and includes information as to the location of the roamer. But unlike the situation where a roamer is roaming in another service area in the United States, the information relating to the location of the roamer is not information about the MSC-V that serves the wireless unit of the roamer. Rather, the present inventions provide that the information refers to the international gateway.
  • the MSC-H in response to receipt of a call for the roamer, the MSC-H sends a request for a TLDN to the international gateway by using the point code of the international gateway 10 as a destination point code in the request.
  • the subsystem number (SSN) of the international gateway 10 also may be included in the request.
  • the international gateway 10 typically is not located in either the home system 12 or the visited system 14.
  • the international gateway 10 is functionally connected to the home system 12 and the visited system 14 so as to receive and transmit requests messages, and in particular SS7 messages, between the home system 12 and the visited system 14.
  • the international gateway 10 may be functionally connected to the systems 12, 14 such that messages, requests, and responses may be routed from a network element such as a signal transfer point (STP) (preferably over A links) to the international gateway 10.
  • STP signal transfer point
  • the international gateway receives the request for a TLDN.
  • the request typically includes information about the wireless unit roaming in the visited system, and particular, includes the ESN and MEN of the wireless unit 20.
  • the international gateway 10 generally analyzes the information in the request to the extent that the gateway determines that the request is to be further routed to the MSC-V where the wireless unit is roaming.
  • the international gateway 10 may log or store the request or pertinent information from the request so that the international gateway 10 may appropriately respond to the request at a later time.
  • the international gateway 10 may consult a table 32 for information with respect to the wireless unit 20 and with respect to the further routing of the request. In consulting the table 32, the international gateway 10 may find an entry 34 for the MIN of the wireless unit 20. This entry 34 may include information as to the MSC-V serving the roaming wireless unit. The entry 34 may provide the international gateway 10 with an association between the MIN for the wireless unit 20 and a point code for the MSC-V in the visited system. Based on this association between the MIN for the wireless unit 20 and the point code for MSC- V, the international gateway 10 creates a new request. The new request includes the point code for MSC-V as a destination point code so as to route the new request to the MSC-V.
  • the information for use of the point code for the MSC-V may be obtained in other manners, such as from other tables, from the information in a registration notification message, or otherwise so that the new request is routed to the MSC-V serving the roamer.
  • the new request may not be "new", but rather request may be translated or altered by the international gateway 10 so the destination point code in the request is changed from the point code of the international gateway 10 to the point code of the MSC-V.
  • the new request or "altered" request may be changed from the request received from the MSC-H in that the originating point code in the message may be changed, from the point code for the MSC-H to the point code for the international gateway 10.
  • the international gateway 10 After creation of the new request (or the alteration of the request as described), the international gateway 10 routes the message to the MSC-V serving the wireless unit 20.
  • the international gateway sends the new request to the MSC-V in country B because the international gateway had retained information from the registration process of the roamer as to the location of the roamer in the service area served by the MSC-V in country B.
  • the MSC-V receives the new request, analyzes the new request, and provides a TLDN based on the numbering system assigned by the wireless system in country B in a message to the international gateway.
  • the MSC- V may provide the TLDN to the international gateway in a TLDN response or message by using the point code of the MSC-V for the originating point code and by using the point code of the international gateway 10 for the destination point code.
  • the international gateway analyzes and creates a new message, but including the TLDN provided by the MSC-V in the new message.
  • the new message may include additional information to the TLDN so as to accomplish ultimately the routing of a communication from the home system in the country of the roamer to the visited system in country B where the roamer is roaming.
  • the international gateway includes additional information to the TLDN such as a prefix dialing number.
  • the prefix dialing number may contain an access code and/or a country code as appropriate to the location of the MSC-V to which the call is to be routed from the home system. For example, assume the roamer is roaming in a country foreign to the United States.
  • the new message includes a prefix dialing number including an international access code (because the call is to be routed to a foreign country) and a country code for the country to which the call is to be routed.
  • a prefix dialing number including an international access code (because the call is to be routed to a foreign country) and a country code for the country to which the call is to be routed.
  • the additional information is added to the message so that when the call is routed to the roamer, the access code provides notice of an international call and the country code provides notice of a call to Chile.
  • the prefix dialing number may include any combination of the numbers 0-9, and may be up to fifteen digits in length.
  • the additional information to the TLDN is added in the new message by the international gateway through consultation of a table, database, or other information source that includes appropriate correlations of information between a visited switch (MSC-V) and the home switch (MSC-H).
  • the prefix dialing number may be Table Driven for each MSC identification per carrier or service provider.
  • code modifications are unnecessary for each individual switch, carrier, or service provider requirements.
  • the prefix dialing numbers may be entered as each MSC identification is entered or implemented through the Table Driven process or otherwise.
  • the prefix dialing numbers may be included as respective fields for the MSCs in a home- visited relationship table that may be maintained by the international gateway.
  • the home- visited relationship table may include entries for all MSCs that may be served through the international gateway.
  • the international gateway may have to do more than prefix the prefix dialing numbers to the TLDN received from the MSC-V.
  • the international gateway may have to remove a configurable number of digits from the left side of the TLDN prior to adding the prefix dialing number.
  • the removal of a configurable number of digits from the left side of the TLDN may be required to accommodate those MSCs which use an undialable NPA/or other unknown digits in the TLDN.
  • Ecuador uses the IRM for TLDNs and 198 is not a valid NPA. Therefore, the first three digits must be deleted from the TLDN and the prefix dialing number has to include the access code, the country code, and the NPA-NXX.
  • the information on the removal of digits may be obtained from the same table or source as the prefix dialing number or from some other source.
  • the issue of whether or not digits need to be removed from the TLDN may be addressed by the inclusion of another field in the home- visited relationship table such as a "number of digits to delete from TLDN" field.
  • Logic may be added to the international gateway to read this field, and to act on the information in the field.
  • An exemplary home-visited relationship table is provided below:
  • the values in this table may override the values in the subscriber profile or any other data.
  • the international gateway may store the TLDN or pertinent information from the TLDN message from the MSC-V so that the international gateway may appropriately follow-up with respect to the TLDN message.
  • the new message includes the point code of the international gateway 10 as the originating point code and the point code (and possibly the system serial number (SSN)) of the MSC-H as the destination point code.
  • the new message may not be "new", but rather the message may be translated or altered so the destination point code in the message is changed from the point code of the international gateway 10 to the point code of the MSC-H.
  • the new message or the "altered" message may be changed from the message received from the MSC-V in that the originating point code in the message may be changed from the point code for the MSC-V to the point code for the international gateway 10.
  • the international gateway sends the new message (or the altered response) with any additional information and the TLDN to the MSC-H.
  • the international gateway 10 may use the information that the international gateway 10 may have stored in connection with the request from the MSC-H so as to appropriately respond to that request.
  • the MSC-H receives the new message (or the altered message) including the TLDN and any additional information.
  • the MSC-H does not view this new or altered message as "new” or “altered”, but rather, as a message received in response to its original request for TLDN.
  • the MSC-H uses the TLDN and any additional information to route the call to the MSC-V.
  • the new (or altered) message provides appropriate information so as to accomplish ultimately the routing of the call from the country of the MSC-H to the country B of the MSC-V where the roamer is roaming.
  • the method ends in step 114.
  • Fig. 3 illustrates elements of an exemplary international gateway 10 such as may be used in the exchange of messages and responses between a visited system and a home system.
  • the international gateway 10 generally includes an interface 73 and a translator 74.
  • the interface 73 functions as a connection to the communications systems (and elements thereof) which the international gateway serves.
  • An exemplary international gateway 10 has an interface 73 that includes SS7 links 75 that receive the messages and responses, and that pass the messages and responses to an SS7 stack 76.
  • the SS7 stack 76 discriminates and passes the messages and responses to an IS-41 message handler such as provided by the IntelliSS7-IS41 MAP 77, which is a mapping software.
  • the SS7 stack 76 passes the data of the IS-41 messages and responses to a parsing library where the message is decoded according to IS-41 standards.
  • the message type, components, and parameters are located in the received messages and responses and stored, (or a pointer stored) in structures which can be then accessed directly.
  • the data then is passed to the translator 74 carrying out the appropriate operations.
  • An exemplary international gateway 10 has a translator 74 that includes a state machine based application 78, which controls or manages each session.
  • the translator 74 may include a database access part 79 and a database 80 that may contain the table 32 that is used in determining the routing for a registration message received with respect to a particular wireless unit. More information about the database 80 and the information that may be stored in the database 80 or other memory structure is provided below under the heading "Information With Respect to the International Gateway".
  • the translator 74 may include a messaging and process infrastructure 41. This infrastructure 41 provides services such as message buffering, message passing, timers, task management, etc.
  • the international gateway 10 also typically includes at least a connection to an administrative console 82.
  • Information regarding a customer and/or a user may be provisioned in the international gateway 10 through the administrative console 82.
  • a service manager may use the administrative console 82 to monitor transactions or view transactions in the transaction log by transaction number or by MLN/ESN. Other statistical information relating to the operation of the international gateway 10 may be obtained or viewed through the administrative console 82.
  • the international gateway 10 may include an application interface to a network manager that may be accessed and/or operated through the administrative console 82 or through other elements.
  • the network manager may be an Openview Network Manager available from Hewlett Packard.
  • the application interface may be based on a simple network management protocol (SNMP) to generate traps and alarms to the network manager. Traps may include unknown message or response received and/or PIN modification retries failure.
  • SNMP simple network management protocol
  • the international gateway 10 functions in accordance with Signaling System 7 (SS7) protocols as well as EIA/TIA IS-41 protocols, and thus, may be accessed through the connectivity between and among network elements of wireless communications systems and/or wireline communications systems.
  • the international gateway 10 supports the American National Standards Institute (ANSI), International Telecommunications Union (ITU) and ITU International variants of the SS7 protocol up to the transaction capabilities application part (TCAP) layer.
  • ANSI American National Standards Institute
  • ITU International Telecommunications Union
  • TCAP transaction capabilities application part
  • the components of the international gateway 10 communicate among themselves and other data networks via TCP/IP connections.
  • the connectivity preferably supports Tl/El and V.35 at speeds of up to 64 Kbps. It is further preferred that the international gateway 10 generally does not use the Global Title Translation (GTT) in addressing entities or elements in the systems.
  • GTT Global Title Translation
  • the international gateway 10 is set up and continually updated with current information as to users, customers, MSC information, etc. so as to facilitate the exchange of messages and responses between a visited system and a home system of a wireless unit.
  • the international gateway 10 operates pursuant to IS-41 specifications. For example, the international gateway 10 starts a timer to time the interval between routing a new message and receiving a response to the new message. If appropriate, the international gateway 10 handles a timeout on the response.
  • the international gateway 10 responds with error messages in the appropriate situations. For example, the international gateway 10 responds with a Return Error with an error code of OperationNotSupported if the international gateway 10 receives a message for call delivery to a wireless unit that has not registered, that is outside its authorization period, etc. Error codes may include SystemFailure, ParameterError, UnrecognizedParameterValue; MLN/HLRMismatch, UnrecognizedESN, Operation Sequence Problem, and/or ResourceShortage.
  • the international gateway 10 may include the table 32 and/or database 80 as well as other memory or storage facilities with respect to the information that is necessary or available with respect to operation of the international gateway 10.
  • User or Subscriber Information The table 32 or database 80 may include entries or records related to users. Each entry or record may include the following information or a field (which may be empty until filled) for the following information with respect to the user or the wireless unit of the user: a mobile identification number (MIN); an electronic serial number (ESN); a user or subscriber name; a personal identification number (PIN); a date-time of last PIN change; a number of retries for PIN change in current interval; an MSC-H; a current MSC-V; a previous MSC-V; a date-time of last successful PIN validation; a number of retries for PIN validation in current interval; a date-time of last Registration Notification; OCOS information returned by the MSC-H; TCOS information returned by the MSC-H; a temporary local dialing number (TLDN
  • the international gateway 10 may store system information with respect to the international gateway 10 in the database 80 or in another storage structure.
  • the following system configuration information may be stored: a system type code; a point code; a subsystem number (SSN); and/or a carrier identification code.
  • the system configuration information may include information relating to the use of PLNs such as the maximum number of retries and the retry interval.
  • the international gateway may store a point code and a SSN for each of the mobile switching centers (MSCs) or other switches which may serve as either origination or destination points with respect to messages and responses that may be sent to and from the international gateway 10.
  • MSCs mobile switching centers
  • the international gateway 10 generally carries out transaction and tracing functions with respect to the messages and responses that may be sent to and from the international gateway 10.
  • a message and its corresponding response generally is referred to as a transaction, and the message and its corresponding response typically includes a transaction number or other identification of the transaction.
  • the international gateway 10 logs the transaction number into a transaction log (not illustrated), which also may be referred to as log files or into the database 80.
  • the log of the transaction includes a timestamp for the transaction.
  • the international gateway 10 may include a tracing mechanism (not illustrated in Fig. 3) and may include four levels of trace messages with each level providing a different amount of detailed information.
  • the international gateway 10 may include audit trails for all changes made to the database, such as changing a PIN, etc. These audit trails may be recorded and stored.
  • the international gateway 10 may store information such as attributes with respect to mobile switching centers (MSCs) which are involved in transactions related to a wireless unit. These attributes may include: an MSC identification; a location; a point code; a subsystem number (SSN); an
  • HLR identification (null if co-located with the MSC); an HLR point code; an HLR SSN; a
  • VLR identification (null if co-located with the MSC); a VLR point code; a VLR subsystem number (SSN); an authentication center (AC) identification; an AC point code; and/or an AC SSN.
  • This information may be stored in the database 80 or in some other memory structure.
  • An exemplary embodiment of the international gateway 80 stores this information in a functional entity messaging relationship table (FEMR table).
  • FEMR table functional entity messaging relationship table
  • the international gateway 10 may include a table or other structure that sets forth a relationship including operating or override values between mobile switching centers (MSCs) in a home-visited relationship. This table may be used by the international gateway 10 to override values that are present in the user or subscriber entry or record when appropriate.
  • the visited MSC may be located in a high fraud area.
  • an authorization period with respect to the registration or provision of communications service to a wireless unit may be instituted through the provision of instructions from the MSC-H or the international gateway to the MSC-V or otherwise.
  • this table may include the following attributes, information or fields: MSC-H identification; MSC-V identification; authorization period; and/or authorization value.
  • the international gateway 10 may have to determine the MSC-H of a particular wireless unit based on the information that is provided to the international gateway 10 by the MSC-V.
  • the international gateway 10 uses the MIN of the wireless unit to find the MSC-H (and its point code) by using an MSC-NPA information table.
  • the MIN may be compared to the entries of NPA-NXX-x blocks that are stored in the table to determine the NPA-NXX-x block corresponding to the MIN, and then to determine the MSC-H (and its point code) serving the NPA-NXX-x block corresponding to the MIN.
  • an entry in the MSC-NPA information table may include the following fields, attributes or information: MSC-H identification; and NPA- NXX-x block (being served by the MSC-H of the entry).
  • Fig. 4 Logical Software Entities of an Exemplary International Gateway
  • Fig. 4 presents a diagram of logical software entities or modules of such a gateway.
  • the modules are presented in the diagram from a logical standpoint. They do not represent separate processes that run the international gateway 10, but rather, each module presents a functionality that may be used in the gateway.
  • the modules include INIT 86 which is an initialization function that brings up and monitors the application processes on the international gateway 10.
  • DB 88 is a database interface in the form of a functional application program interface (API) for interaction with a user.
  • API application program interface
  • DB 88 also includes the database server part that is provided by the vendor of the database.
  • TM 90 is a transaction manager which registers with the SS7 processes to gain access to the SS7 stack. The transaction manager 90 receives and sends IS-41 messages and responses through the SS7 processes. The transaction manager 90 links with the DB 88 in order to use the database server.
  • Log 92 is a library that provides a functional API to record every IS-41 message and response that is sent and received. This API is used to record all of the IS-41 messages and responses that pass through the international gateway 10.
  • Trace 94 is a library that provides debugging aids for integration and testing.
  • SNMP Agent 96 is a process that forwards simple network management protocol (SNMP) traps to the network manager such as the Openview Network Manager from Hewlett Packard. This SNMP Agent 96 also provides a message queue for the other application software entities to send event/alarm information, which is converted to a trap and forwarded as appropriate.
  • Bulk Update 98 is a script that updates the database with large numbers of records or entries, generally with respect to users.
  • Vision Feed 100 is a process that provides a continuous feed of all IS-41 messages and responses being sent and received by the international gateway 10 to a separate entity for further processing (billing, debugging, network problems, etc.).
  • IS-41 API & Vendor's SS7 102 stack is an IS-41 API built on top of the SS7 stack. The SS7 stack functionality is handled within separate processes, i.e., they are not libraries. The IS-41 API is incorporated in these separate processes.
  • DIR 104 is a platform configuration task called the Director. It provides a command line interface for configuring the SS7 stack and all network parameters associated with setting up the international gateway 10 as a functional network entity. The DIR 104 also can be used to control the SS7 stack processes.
  • the present inventions include methods, systems, and apparatus that allow a home wireless system to obtain a temporary location directory number (TLDN) so that the home wireless system may appropriately route a call received for a wireless unit roaming in a visited wireless system.
  • TLDN temporary location directory number
  • the present inventions correct or otherwise solve the problems associated with the insufficiency or invalidity in the provision of TLDNs that are exchanged between wireless communications systems which are located respectively in countries or systems having disparate numbering systems or other disparate processes related to the exchange of TLDNs.

Abstract

Methods, systems, and apparatus that allow a home wireless system to obtain a temporary location directory number (TLDN) so that the home wireless system may appropriately route a call received for a wireless unit roaming in a visited wireless system. In response to a call directed to a mobile number of a wireless unit served by a home service provider, and particularly by a MSC-H, the MSC-H routes a request for a TLDN to an international gateway. The international gateway creates a new request or alters the request and then routes the new or altered request to the appropriate MSC-V serving the wireless unit in the visited system. In response to the new or altered request, the MSC-V provides the TLDN in a message to the international gateway. The international gateway may add additional information to the TLDN such as adding prefix dialing numbers as appropriate to the TLDN. The prefix dialing numbers may include an international or other access code and a country code. With the addition of these prefix dialing numbers, the TLDN is corrected so that the MSC-H may properly route the call to the wireless unit roaming in the visited system. Advantageously, the new (or altered) message provides appropriate information so as to accomplish ultimately the routing of the call from the MSC-H to the MSC-V where the roamer is roaming.

Description

METHODS AND SYSTEMS TO OBTAIN A TLDN FOR A HOME SYSTEM
IN RESPONSE TO A CALL RECEIVED FOR A WIRELESS UNIT
ROAMING IN A VISITED SYSTEM
RELATED APPLICATION
The present application claims priority to and the benefit of the prior filed copending and commonly owned provisional application entitled "SCP/International Gateway - An SS7 Network Element That Performs SS7 Message Routing, Call Delivery and PIN Fraud Protection for Cellular Users Roaming Internationally", filed in the United States Patent and Trademark Office on November 5, 1998, assigned Application No. 60/107,224, and incorporated herein by reference.
TECHNICAL FIELD
This invention relates to telecommunications, and in particular, to methods and systems for obtaining a temporary location directory number (TLDN) for a home system in response to a call received for a wireless unit that is roaming in a visited system.
BACKGROUND OF THE INVENTION
A distinguishing feature of humans as a species is our ability to communicate with each other. Our methods of communication have become ever more sophisticated and have led to the development of wireless communications. Generally, wireless communications are communications that are transmitted through the use of radio frequency (RF) technology. Wireless communications include communications that are transmitted through the use of wireless units such as cellular telephones, mobile telephones, car phones, personal communication service (PCS) units, pagers, and the like.
A wireless unit is particularly useful to a person on the move. For example, a person may use his or her wireless unit while driving a car. The wireless communications service to the person's wireless unit is provided typically by a service provider that may also be referred to herein as a carrier. Typically, a person who obtains wireless communications service from a service provider is generally referred to herein as a subscriber, a customer, or a user. A subscriber may make or receive communications with his or her wireless unit. The term "communication" is used herein to refer to any call, message, announcement or other exchange of data or information, whether analog or digital, that may be received on a wireless unit or transmitted from a wireless unit, and/or may be received or transmitted from a wireless unit that is operating as part of any other device such as a computer.
When a user initiates a communication on his or her wireless unit, a base station in or serving a predetermined geographic area wherein the subscriber is located receives the communication. The geographic area that is served with wireless communications service by the carrier is referred to herein as the service area of the service provider. The service provider typically operates a wireless communications network or system to provide wireless communications service to the geographic area. The wireless communications network includes the referenced base station, and other elements such as mobile switching centers (MSCs). The wireless communications network also includes elements that interface with the public switched telephone network (PSTN), and other networks and systems so as to provide for communications between and among parties using wireless units and/or using wireline units and/or other communication devices.
Upon receipt of a communication from a wireless unit of a user, the base station transmits the communication to a mobile switching center (MSC) (sometimes referred to as a mobile-service switching center or mobile telecommunications switching office (MTSO)). In response to the receipt of the communication, the MSC further routes the communication as appropriate. This routing may take the communication to and through the PSTN, to and through the same wireless communications system, to and through another wireless communications system, to and through other communications systems, or combinations thereof.
In addition to making a call, a subscriber may receive a communication on his or her wireless unit from a caller. The caller typically directs his or her communication to the number associated with the subscriber's wireless unit, which is referred to herein as the mobile number (MN) of the wireless unit. The mobile number may be the mobile identification number (MIN) of the wireless unit. The communication is routed through the PSTN, through other networks, and/or wireless communications systems until the communication reaches the MSC serving the subscriber's wireless unit. This MSC may be referred to as the serving MSC or the serving switch. The serving MSC then further routes the communication to the wireless unit. As noted, a wireless unit is particularly useful when a subscriber is on the move such as when the subscriber is driving a car or otherwise travelling. The subscriber's mobility may take the subscriber out of the service area served by the service provider from whom the subscriber subscribes. In other words, the subscriber's mobility may take the subscriber out of his or her home service area served by his or her home service provider or home carrier. The subscriber may move so as to be located in another service area that is served by a different service provider with whom the subscriber has no business relationship. The subscriber is said to be "roaming" out of his or her home service area and may be referred to as a "roamer", "roaming subscriber" in a visited service area that is served by a visited system. To provide a roaming subscriber with communications service, service providers have agreed to follow certain procedures in the processing of communications with respect to each other's subscribers. Generally, a roaming subscriber is validated and may be authenticated by the visited system, which also may be referred to as the visited service provider. Both of these processes (validation and authentication) are used to prevent fraudulent use of wireless units and for other reasons. General descriptions of these processes and other information about wireless communications systems may be found in the book entitled Cellular and PCS - The Big Picture by Lawrence Harte, Steve Prokup and Richard Levine (McGraw-Hill 1997).
Roamer validation and/or authentication generally is the mechanism for providing information to the subscriber's home system as to the subscriber's location in a visited system. It is important to a home system to have information as to a subscriber's location because the home system is the initial recipient of calls that are directed to the mobile number of a subscriber's wireless unit. The home system then attempts to route a call received for its subscriber to the subscriber's roaming location. In particular, when a home system receives a call for its subscriber, the MSC in that home system (MSC-H) checks its HLR to determine if the wireless unit is operating in another system. If so, the home MSC (MSC-H) then sends a request to the visited MSC (MSC-V) for a temporary location directory number (TLDN)(also referred to as a temporary line directory number). The TLDN is used with respect to the received call so that the call may be directed to the MSC-V for further routing to the wireless unit of the subscriber. The TLDN generally is cross-referenced with the MIN of the visiting wireless unit in the VLR of the serving MSC in the visited system. Upon receipt of the TLDN from the MSC-V, the home system then routes the call that had been dialed to the subscriber's mobile number based on the TLDN. The use of the TLDN routes the call to the appropriate MSC in a visited system. The visited system receives the call and finds the TLDN number is listed in its VLR. The visited system pages the wireless unit using the MIN which is stored in the VLR. When the subscriber answers, the call is connected.
The above described process of using a TLDN is carried out generally with respect to communications that occur within the United States. The processes generally work well within the United States. However, wireless communications between the United States and foreign countries or wireless communications between foreign countries have been problematic. Problems arise because the processes described above may not be carried out because of the differences in the wireless systems in the respective countries. A wireless system and its related wireline system in a particular country may not be networked with the wireless system and its related wireline system in a foreign country.
In addition, a wireless system and its related wireline system may be organized completely differently from the way a wireless system and its related wireline system is organized in another country. An example of this difference in organization is the assignment of numbers for use in making calls and associated with respective communication units within a country. For example, in the United States, an area code is included as part of a directory number associated with a wireline unit such that an area code corresponds to a general geographic area or area served by a particular service provider. Area codes are not generally duplicated within the United States. A communication may be routed through the United States on the basis of the area code, and then the remaining numbers of the directory number.
A difficulty in processing communications arises between countries or between different communication systems having different numbering systems for assignment of directory or mobile numbers to communication devices. One way which has been used to smooth over the differences in communication processing has been the use of prefix dialing numbers, which precede a directory number or mobile number for long distance calls. Between locations in the United States, a long distance call may be dialed by first dialing an access code of "1". Between a location in the United States and a location in another country, a long distance call may be dialed by first dialing an access code of "Oi l", and then by dialing a country code (such as "44" for England) corresponding to the country including the destination of the call. The access code of "Oi l" is sometimes referred to as the international access code because it is used in the United States with respect to calls whose destinations are generally outside the United States. In other words, a communication from the United States to England may be dialed by first dialing the prefix dialing numbers of "Oi l 44" and then the directory number assigned to the called party pursuant to the numbering scheme used by the appropriate system in England.
In wireless communications, the duplication of numbers that serve as area codes in mobile numbers and other issues related to the numbering schemes within and among countries cause problems. In particular, as is explained in greater detail below, the TLDN that is provided from a wireless system in a foreign country where a roamer is located may be insufficient or invalid to accomplish routing of a communication from the roamer's home system to the visited system in the foreign country. The TLDN may be insufficient because the provided TLDN generally is based on the numbering scheme in use in the country or geographic area wherein the MSC-V is located. Thus, the TLDN may be insufficient to route a call between foreign countries because the TLDN may not include information such as prefix dialing numbers, etc. to inform the home system that the roamer is roaming in a service area located in a foreign country. Thus, the use of the TLDN provided by the visited system may not result in the routing of the communication to the foreign country. In fact, the use of the TLDN may misroute the communication to some other foreign country.
Further details regarding the problems with the provision of TLDNs from a wireless system in a first country to a wireless system in a second country are provided in the paragraphs immediately set forth below. The reader is cautioned that the problems associated with the provision of insufficient TLDNs are described in the context of communications between respective countries. But such problems may also arise between wireless systems or other systems wherein the assignment of numbering schemes or other such issues cause such conflicts. Assume a subscriber travels from country A to country B and desires to use his or her wireless unit for communications between the two countries. The roamer' s desire cannot be satisfied if there is no connectivity, networking, or interface between the wireless communications systems of country A and country B.
There may be some connectivity between and among some countries so as to allow a roamer in country B to make and receive communications to and from country A. Generally, such connectivity takes the form of systems that follow the Signaling System 7 (SS7) protocols. In that case, the roamer powers on his or her mobile unit in country B and that power-on generally begins the registration of the mobile unit with a serving MSC (MSC-V) in country B. The MSC-V recognizes the mobile unit to be a roamer, and sends a message (typically a Registration Notification (REGNOT) message) to a routing element such as a service transfer point (STP) or the like in the visited system. Based on information in the message, the routing element routes the message to the appropriate MSC-H in the home system.
The MSC-H receives the message, checks out the message with respect to the roamer in a validation process, and stores information as necessary with respect to the location of the roamer in the visited system. The information that is stored with respect to the location of the roamer is the point code (also referred to as an originating point code (OPC)) that arrives in the message and that indicates the message originated with a particular MSC-V. An MSC, like other network elements, is assigned a unique point code so that a determination may be made as to the originating network element of a message. If the roamer is valid, then the MSC-H sends a response message (typically a registration notification (regnot) response message) to the MSC-V. The MSC-V receives the response, and if appropriate, registers the roamer in the visited system, and the registration process ends. Assuming connectivity between the wireless communications systems of country
A and country B, assume the registered roamer is called by a caller in the United States. The caller dials the mobile number of the wireless unit of the roamer. The call is received at the MSC-H (home MSC) of the roamer. As a result of the registration of the roamer with the MSC-V in country B, the MSC-H has information that the roamer is located in an area served by MSC-V. The MSC-H requests the MSC-V for a TLDN so that the call from the caller may be appropriately routed. The MSC-V provides a TLDN based on the numbering system assigned by the wireless system in country B. The MSC-H tries to use the TLDN to route the call.
Generally, the call cannot be put through because the TLDN is insufficient or invalid. The numbers or other information that are the components of the TLDN may be incorrect, or may not have enough components or digits, or otherwise may not be recognized by the home system. Alternatively, the TLDN may include components or digits that result in the routing of the call to a country or place other than country B. Thus, the TLDN does not provide a mechanism or other information for routing the call from the caller to the roamer in country B. For example, assume the caller to be in the United States and the roamer to be in Chile. The MSC-V in Chile does not provide the MSC-H in the United States with information in the TLDN that the roamer is located in Chile. Rather, the TLDN is provided as if the MSC-H were also located in Chile. For example, a Chilean MSC-V may include a component of "730" in the TLDN in the place (from the perspective of the wireless communications systems in the United States) of the country code. But "569" is the country code for Chile in the system followed in the United States. Therefore, the call cannot be put through, or at least cannot be routed to Chile. The call may be routed from the MSC-H in the United States to whatever country includes a country code of "730" in its TLDN. In sum, a roamer in country B generally is unable to receive calls in country B because, inter alia, of the insufficiencies and invalidities in the provision of TLDN information from the wireless communications systems in country B to the home system of the roamer. Chile and the United States are used as examples in explaining the insufficiencies of the TLDN provision. But TLDN provision problems exist in calls between other countries, and in some cases, between systems in the same country.
Accordingly, there is a need to provide a method, system and/or apparatus to allow for the receipt of communications by a roamer roaming in the service area of a foreign country or system. There is a particular need for a method, system and/or apparatus that corrects or otherwise solves the problems associated with the insufficiency or invalidity in the provision of TLDNs that are exchanged between wireless communications systems which are located respectively in countries or systems having disparate numbering systems or other disparate processes related to the exchange of TLDNs.
SUMMARY
The present inventions include methods, systems, and apparatus that allow a home wireless system to obtain a temporary location directory number (TLDN) so that the home wireless system may appropriately route a call received for a wireless unit roaming in a visited wireless system. Advantageously, the present inventions correct or otherwise solve the problems associated with the insufficiency or invalidity in the provision of TLDNs that are exchanged between wireless communications systems which are located respectively in countries or systems having disparate numbering systems or other disparate processes related to the exchange of TLDNs.
Generally stated, in response to a call directed to a mobile number of a wireless unit served by a home service provider, and particularly by a MSC-H, the MSC-H routes a request for a TLDN to an international gateway. The international gateway creates a new request or alters the request and then routes the new or altered request to the appropriate MSC-V serving the wireless unit in the visited system. The international gateway had retained information on the location of the wireless unit roaming in a visited system when the wireless unit registered in the visited system. In response to the new or altered request, the MSC-V provides the TLDN in a message to the international gateway.
Rather than providing the TLDN directly to the MSC-H for routing of the call to the roaming wireless unit in the visited system, the international gateway may add additional information to the TLDN. In particular, the international gateway may add prefix dialing numbers as appropriate to the TLDN. The prefix dialing numbers may include an international or other access code and a country code. With the addition of these prefix dialing numbers, the TLDN is corrected so that the MSC-H may properly route the call to the wireless unit roaming in the visited system. Advantageously, the new (or altered) message provides appropriate information so as to accomplish ultimately the routing of the call from the country of the MSC-H to the MSC-V where the roamer is roaming.
BRIEF DESCRIPTION OF THE DRAWINGS Fig. 1 is a block diagram illustrating use of an exemplary international gateway in an exemplary environment.
Fig. 2 is a flow diagram illustrating an exemplary method of the present invention.
Fig. 3 is a block diagram illustrating an exemplary international gateway.
Fig. 4 is a diagram of logical software entities in an exemplary international gateway.
DETAILED DESCRIPTION
The present inventions include methods, systems, and apparatus that allow a home wireless system to obtain a temporary location directory number (TLDN) so that the home wireless system may appropriately route a call received for a wireless unit roaming in a visited wireless system. Advantageously, the present inventions correct or otherwise solve the problems associated with the insufficiency or invalidity in the provision of TLDNs that are exchanged between wireless communications systems which are located respectively in countries or systems having disparate numbering systems or other disparate processes related to the exchange of TLDNs. Generally, the exemplary embodiments of the present invention contemplate uses with wireless units such as cell phones and personal communication service (PCS) phones that operate under the standards of Advanced Mobile Phone Service (AMPS), Call Division Multiple Access (CDMA), or Time Division Multiple Access (TDMA). Nonetheless, the principles of the present invention may be applied to other communication devices operating under other standards with the appropriate reconfiguration.
Exemplary embodiments of the present invention include an international gateway for use with respect to the referenced wireless communications. Advantageously, the international gateway may be used in wireless communications so as to provide a method, system and/or apparatus to correct or otherwise solve the problems associated with the insufficiency or invalidity in the provision of TLDNs that are exchanged between wireless communications systems which are located respectively in countries or systems having disparate numbering systems or other disparate processes related to the exchange of TLDNs.
Exemplary embodiments of the present invention describe the international gateway as a stand-alone unit such as may be embodied by or in a service control point (SCP). But the reader is cautioned the international gateway should not be so limited in embodiment. As well as a stand-alone unit, the international gateway may be incorporated in or as part of another device such as an intelligent peripheral (IP) in a wireless communications system, or in other devices or systems. As a result of the functions the international gateway carries out with respect to fraud prevention, the international gateway also may be referred to herein as a personal identification (PIN) validation or authentication platform. Moreover, the international gateway may be considered a series of functions that may be carried out in a single device or that may be carried out through the use of several devices. In the exemplary embodiments described below, generally the international gateway functions in accordance with Signaling System 7 (SS7) protocols as well as EIA/TIA IS-41 protocols, and thus, may be accessed through the connectivity between and among network elements of wireless communications systems and/or wireline communications systems. Further, the international gateway may be connected to customer service elements of the service provider of the international gateway, and even may be accessed (or partially) accessed by customers of the service provider of the international gateway through the Internet or other communications networks. Generally, customers of the service provider of the international gateway include carriers who provide wireless service to subscribers and who desire to facilitate the provision of wireless service to such subscribers when they are roaming, and particularly roaming in foreign countries or systems.
Fig. 1 - An Exemplary International Gateway in an Exemplary Environment Fig. 1 is a block diagram illustrating use of an exemplary international gateway 10 in an exemplary environment including a home system 12 and a visited system 14. The home system 12 generally is a wireless communications system provided by a service provider with whom a subscriber has a relationship such that a wireless unit used by the subscriber typically is registered in a home location register (HLR) 16 of a mobile switching center (MSC-H) 18 when the wireless unit is located in the geographic area served by the MSC-H 18. A communication from a caller and directed to the mobile number of the wireless unit is routed to the MSC-H 18 for further routing to the called wireless unit.
Fig. 1 also illustrates a visited system 14 including a wireless unit 20 that is roaming or visiting in the visited system 14. When the wireless unit 20 is turned on, typically it provides registration information to a base station 22 serving the cell of the visiting system wherein the wireless unit 20 is roaming. The registration information typically includes the mobile identification number (MIN) for the wireless unit 20. The base station 22 generally provides the registration information to a mobile switching center (MSC-V) 24. The actions of the exemplary embodiments in response to the receipt by the MSC-V 24 of the registration information of the wireless unit 20 are further explained in the copending and commonly assigned patent application entitled "Method & Systems for Providing Information to a Home System Regarding a Wireless Unit Roaming in a Visited System", filed on July 23, 1999, in the United States Patent and Trademark Office, and assigned Serial No. 09/359,515, which is incorporated herein by reference.
Fig. 2 - An Exemplary Embodiment Advantageously, exemplary embodiments of the present invention allow a roamer, who is based in country (or system) A, who has registered in a visited system, and who has satisfied other processes (such as any necessary authentication or verification processes) to receive calls while roaming in a country (or system) B. An exemplary method with respect to the receipt of a call by a registered roamer in country B is illustrated in Fig. 3. Assume the registered roamer is called by a caller. As illustrated in Fig. 3, after start 98, in block 100 the caller dials the mobile number (MN) of the wireless unit of the roamer. In block 102, the call is received at the MSC-H (home MSC) of the roamer. As a result of the registration of the roamer, the MSC-H has stored information with respect to the registration of the roamer in a visited system and includes information as to the location of the roamer. But unlike the situation where a roamer is roaming in another service area in the United States, the information relating to the location of the roamer is not information about the MSC-V that serves the wireless unit of the roamer. Rather, the present inventions provide that the information refers to the international gateway. Thus, in response to receipt of a call for the roamer, the MSC-H sends a request for a TLDN to the international gateway by using the point code of the international gateway 10 as a destination point code in the request. The subsystem number (SSN) of the international gateway 10 also may be included in the request.
The international gateway 10 typically is not located in either the home system 12 or the visited system 14. The international gateway 10 is functionally connected to the home system 12 and the visited system 14 so as to receive and transmit requests messages, and in particular SS7 messages, between the home system 12 and the visited system 14. In particular, the international gateway 10 may be functionally connected to the systems 12, 14 such that messages, requests, and responses may be routed from a network element such as a signal transfer point (STP) (preferably over A links) to the international gateway 10. Additional information relating to an exemplary international gateway is provided below in a discussion of Fig. 3.
In block 104, the international gateway receives the request for a TLDN. The request typically includes information about the wireless unit roaming in the visited system, and particular, includes the ESN and MEN of the wireless unit 20. The international gateway 10 generally analyzes the information in the request to the extent that the gateway determines that the request is to be further routed to the MSC-V where the wireless unit is roaming. In addition, the international gateway 10 may log or store the request or pertinent information from the request so that the international gateway 10 may appropriately respond to the request at a later time.
With respect to the analysis of the information in the request, the international gateway 10 may consult a table 32 for information with respect to the wireless unit 20 and with respect to the further routing of the request. In consulting the table 32, the international gateway 10 may find an entry 34 for the MIN of the wireless unit 20. This entry 34 may include information as to the MSC-V serving the roaming wireless unit. The entry 34 may provide the international gateway 10 with an association between the MIN for the wireless unit 20 and a point code for the MSC-V in the visited system. Based on this association between the MIN for the wireless unit 20 and the point code for MSC- V, the international gateway 10 creates a new request. The new request includes the point code for MSC-V as a destination point code so as to route the new request to the MSC-V. As an alternative to the use of the table 32, the information for use of the point code for the MSC-V may be obtained in other manners, such as from other tables, from the information in a registration notification message, or otherwise so that the new request is routed to the MSC-V serving the roamer. Alternatively, the new request may not be "new", but rather request may be translated or altered by the international gateway 10 so the destination point code in the request is changed from the point code of the international gateway 10 to the point code of the MSC-V. In addition, the new request or "altered" request may be changed from the request received from the MSC-H in that the originating point code in the message may be changed, from the point code for the MSC-H to the point code for the international gateway 10. After creation of the new request (or the alteration of the request as described), the international gateway 10 routes the message to the MSC-V serving the wireless unit 20. The international gateway sends the new request to the MSC-V in country B because the international gateway had retained information from the registration process of the roamer as to the location of the roamer in the service area served by the MSC-V in country B.
Referring still to Fig. 2, in block 106, the MSC-V receives the new request, analyzes the new request, and provides a TLDN based on the numbering system assigned by the wireless system in country B in a message to the international gateway. The MSC- V may provide the TLDN to the international gateway in a TLDN response or message by using the point code of the MSC-V for the originating point code and by using the point code of the international gateway 10 for the destination point code.
In block 108, in response to receipt of the TLDN in the message, the international gateway analyzes and creates a new message, but including the TLDN provided by the MSC-V in the new message. The new message may include additional information to the TLDN so as to accomplish ultimately the routing of a communication from the home system in the country of the roamer to the visited system in country B where the roamer is roaming. In an exemplary embodiment, the international gateway includes additional information to the TLDN such as a prefix dialing number. The prefix dialing number may contain an access code and/or a country code as appropriate to the location of the MSC-V to which the call is to be routed from the home system. For example, assume the roamer is roaming in a country foreign to the United States. Then, the new message includes a prefix dialing number including an international access code (because the call is to be routed to a foreign country) and a country code for the country to which the call is to be routed. With respect to the example of a call from the United States to Chile, the additional information is added to the message so that when the call is routed to the roamer, the access code provides notice of an international call and the country code provides notice of a call to Chile. Preferably, the prefix dialing number may include any combination of the numbers 0-9, and may be up to fifteen digits in length. Preferably, the additional information to the TLDN is added in the new message by the international gateway through consultation of a table, database, or other information source that includes appropriate correlations of information between a visited switch (MSC-V) and the home switch (MSC-H). For example, the prefix dialing number may be Table Driven for each MSC identification per carrier or service provider. Advantageously, with a Table Driven process, code modifications are unnecessary for each individual switch, carrier, or service provider requirements. Generally, the prefix dialing numbers may be entered as each MSC identification is entered or implemented through the Table Driven process or otherwise. In addition, the prefix dialing numbers may be included as respective fields for the MSCs in a home- visited relationship table that may be maintained by the international gateway. The home- visited relationship table may include entries for all MSCs that may be served through the international gateway.
In some cases, the international gateway may have to do more than prefix the prefix dialing numbers to the TLDN received from the MSC-V. The international gateway may have to remove a configurable number of digits from the left side of the TLDN prior to adding the prefix dialing number. The removal of a configurable number of digits from the left side of the TLDN may be required to accommodate those MSCs which use an undialable NPA/or other unknown digits in the TLDN. For example, Ecuador uses the IRM for TLDNs and 198 is not a valid NPA. Therefore, the first three digits must be deleted from the TLDN and the prefix dialing number has to include the access code, the country code, and the NPA-NXX. The information on the removal of digits may be obtained from the same table or source as the prefix dialing number or from some other source. For example, the issue of whether or not digits need to be removed from the TLDN may be addressed by the inclusion of another field in the home- visited relationship table such as a "number of digits to delete from TLDN" field. Logic may be added to the international gateway to read this field, and to act on the information in the field. An exemplary home-visited relationship table is provided below:
Figure imgf000018_0001
The values in this table may override the values in the subscriber profile or any other data. The international gateway may store the TLDN or pertinent information from the TLDN message from the MSC-V so that the international gateway may appropriately follow-up with respect to the TLDN message. In addition, the new message includes the point code of the international gateway 10 as the originating point code and the point code (and possibly the system serial number (SSN)) of the MSC-H as the destination point code.
Alternatively, the new message may not be "new", but rather the message may be translated or altered so the destination point code in the message is changed from the point code of the international gateway 10 to the point code of the MSC-H. In addition, the new message or the "altered" message may be changed from the message received from the MSC-V in that the originating point code in the message may be changed from the point code for the MSC-V to the point code for the international gateway 10.
In block 110, the international gateway sends the new message (or the altered response) with any additional information and the TLDN to the MSC-H. The international gateway 10 may use the information that the international gateway 10 may have stored in connection with the request from the MSC-H so as to appropriately respond to that request.
In block 112, the MSC-H receives the new message (or the altered message) including the TLDN and any additional information. The MSC-H does not view this new or altered message as "new" or "altered", but rather, as a message received in response to its original request for TLDN. The MSC-H uses the TLDN and any additional information to route the call to the MSC-V. Advantageously, the new (or altered) message provides appropriate information so as to accomplish ultimately the routing of the call from the country of the MSC-H to the country B of the MSC-V where the roamer is roaming. The method ends in step 114.
Fig. 3 - An Exemplary International Gateway
Fig. 3 illustrates elements of an exemplary international gateway 10 such as may be used in the exchange of messages and responses between a visited system and a home system. The international gateway 10 generally includes an interface 73 and a translator 74. The interface 73 functions as a connection to the communications systems (and elements thereof) which the international gateway serves. An exemplary international gateway 10 has an interface 73 that includes SS7 links 75 that receive the messages and responses, and that pass the messages and responses to an SS7 stack 76. The SS7 stack 76 discriminates and passes the messages and responses to an IS-41 message handler such as provided by the IntelliSS7-IS41 MAP 77, which is a mapping software. In particular, the SS7 stack 76 passes the data of the IS-41 messages and responses to a parsing library where the message is decoded according to IS-41 standards. In the parsing library, the message type, components, and parameters are located in the received messages and responses and stored, (or a pointer stored) in structures which can be then accessed directly. Once the messages and responses are parsed, the data then is passed to the translator 74 carrying out the appropriate operations.
An exemplary international gateway 10 has a translator 74 that includes a state machine based application 78, which controls or manages each session. In addition, the translator 74 may include a database access part 79 and a database 80 that may contain the table 32 that is used in determining the routing for a registration message received with respect to a particular wireless unit. More information about the database 80 and the information that may be stored in the database 80 or other memory structure is provided below under the heading "Information With Respect to the International Gateway". Still referring to Fig. 3, the translator 74 may include a messaging and process infrastructure 41. This infrastructure 41 provides services such as message buffering, message passing, timers, task management, etc.
The international gateway 10 also typically includes at least a connection to an administrative console 82. Information regarding a customer and/or a user may be provisioned in the international gateway 10 through the administrative console 82. A service manager may use the administrative console 82 to monitor transactions or view transactions in the transaction log by transaction number or by MLN/ESN. Other statistical information relating to the operation of the international gateway 10 may be obtained or viewed through the administrative console 82. Further, the international gateway 10 may include an application interface to a network manager that may be accessed and/or operated through the administrative console 82 or through other elements. For example, the network manager may be an Openview Network Manager available from Hewlett Packard. The application interface may be based on a simple network management protocol (SNMP) to generate traps and alarms to the network manager. Traps may include unknown message or response received and/or PIN modification retries failure.
Generally, the international gateway 10 functions in accordance with Signaling System 7 (SS7) protocols as well as EIA/TIA IS-41 protocols, and thus, may be accessed through the connectivity between and among network elements of wireless communications systems and/or wireline communications systems. Preferably, the international gateway 10 supports the American National Standards Institute (ANSI), International Telecommunications Union (ITU) and ITU International variants of the SS7 protocol up to the transaction capabilities application part (TCAP) layer. In particular, the components of the international gateway 10 communicate among themselves and other data networks via TCP/IP connections. The connectivity preferably supports Tl/El and V.35 at speeds of up to 64 Kbps. It is further preferred that the international gateway 10 generally does not use the Global Title Translation (GTT) in addressing entities or elements in the systems.
Information With Respect to the International Gateway
The international gateway 10 is set up and continually updated with current information as to users, customers, MSC information, etc. so as to facilitate the exchange of messages and responses between a visited system and a home system of a wireless unit. Generally, the international gateway 10 operates pursuant to IS-41 specifications. For example, the international gateway 10 starts a timer to time the interval between routing a new message and receiving a response to the new message. If appropriate, the international gateway 10 handles a timeout on the response. The international gateway 10 responds with error messages in the appropriate situations. For example, the international gateway 10 responds with a Return Error with an error code of OperationNotSupported if the international gateway 10 receives a message for call delivery to a wireless unit that has not registered, that is outside its authorization period, etc. Error codes may include SystemFailure, ParameterError, UnrecognizedParameterValue; MLN/HLRMismatch, UnrecognizedESN, Operation Sequence Problem, and/or ResourceShortage.
The international gateway 10 may include the table 32 and/or database 80 as well as other memory or storage facilities with respect to the information that is necessary or available with respect to operation of the international gateway 10. User or Subscriber Information The table 32 or database 80 may include entries or records related to users. Each entry or record may include the following information or a field (which may be empty until filled) for the following information with respect to the user or the wireless unit of the user: a mobile identification number (MIN); an electronic serial number (ESN); a user or subscriber name; a personal identification number (PIN); a date-time of last PIN change; a number of retries for PIN change in current interval; an MSC-H; a current MSC-V; a previous MSC-V; a date-time of last successful PIN validation; a number of retries for PIN validation in current interval; a date-time of last Registration Notification; OCOS information returned by the MSC-H; TCOS information returned by the MSC-H; a temporary local dialing number (TLDN); user or subscriber status; calling features mask; carrier digits; billing identification; destination digits; and/or a date-time of first unsuccessful validation attempts in current interval. The user or subscriber information may be provisioned in the international gateway 10 through the administrative console 82 or in batch mode through bulk updates transferred from customers.
System Information The international gateway 10 may store system information with respect to the international gateway 10 in the database 80 or in another storage structure. For example, the following system configuration information may be stored: a system type code; a point code; a subsystem number (SSN); and/or a carrier identification code. Also, the system configuration information may include information relating to the use of PLNs such as the maximum number of retries and the retry interval. Further, the international gateway may store a point code and a SSN for each of the mobile switching centers (MSCs) or other switches which may serve as either origination or destination points with respect to messages and responses that may be sent to and from the international gateway 10.
Transaction, Tracing and Audit Information The international gateway 10 generally carries out transaction and tracing functions with respect to the messages and responses that may be sent to and from the international gateway 10. A message and its corresponding response generally is referred to as a transaction, and the message and its corresponding response typically includes a transaction number or other identification of the transaction. The international gateway 10 logs the transaction number into a transaction log (not illustrated), which also may be referred to as log files or into the database 80. Preferably, the log of the transaction includes a timestamp for the transaction. The international gateway 10 may include a tracing mechanism (not illustrated in Fig. 3) and may include four levels of trace messages with each level providing a different amount of detailed information. Also, the international gateway 10 may include audit trails for all changes made to the database, such as changing a PIN, etc. These audit trails may be recorded and stored.
MSC Information
To facilitate the exchange of messages and responses, the international gateway 10 may store information such as attributes with respect to mobile switching centers (MSCs) which are involved in transactions related to a wireless unit. These attributes may include: an MSC identification; a location; a point code; a subsystem number (SSN); an
HLR identification (null if co-located with the MSC); an HLR point code; an HLR SSN; a
VLR identification (null if co-located with the MSC); a VLR point code; a VLR subsystem number (SSN); an authentication center (AC) identification; an AC point code; and/or an AC SSN. This information may be stored in the database 80 or in some other memory structure. An exemplary embodiment of the international gateway 80 stores this information in a functional entity messaging relationship table (FEMR table). Home-Visited Relationship The international gateway 10 may include a table or other structure that sets forth a relationship including operating or override values between mobile switching centers (MSCs) in a home-visited relationship. This table may be used by the international gateway 10 to override values that are present in the user or subscriber entry or record when appropriate. For example, the visited MSC may be located in a high fraud area. In that case, an authorization period with respect to the registration or provision of communications service to a wireless unit may be instituted through the provision of instructions from the MSC-H or the international gateway to the MSC-V or otherwise. Thus, this table may include the following attributes, information or fields: MSC-H identification; MSC-V identification; authorization period; and/or authorization value.
MSC-NPA Information
The international gateway 10 may have to determine the MSC-H of a particular wireless unit based on the information that is provided to the international gateway 10 by the MSC-V. Typically, the international gateway 10 uses the MIN of the wireless unit to find the MSC-H (and its point code) by using an MSC-NPA information table. Particularly, the MIN may be compared to the entries of NPA-NXX-x blocks that are stored in the table to determine the NPA-NXX-x block corresponding to the MIN, and then to determine the MSC-H (and its point code) serving the NPA-NXX-x block corresponding to the MIN. Thus, an entry in the MSC-NPA information table may include the following fields, attributes or information: MSC-H identification; and NPA- NXX-x block (being served by the MSC-H of the entry).
Fig. 4 - Logical Software Entities of an Exemplary International Gateway
To facilitate the understanding of the operation of an exemplary international gateway 10, Fig. 4 presents a diagram of logical software entities or modules of such a gateway. The modules are presented in the diagram from a logical standpoint. They do not represent separate processes that run the international gateway 10, but rather, each module presents a functionality that may be used in the gateway.
The modules include INIT 86 which is an initialization function that brings up and monitors the application processes on the international gateway 10. DB 88 is a database interface in the form of a functional application program interface (API) for interaction with a user. DB 88 also includes the database server part that is provided by the vendor of the database. TM 90 is a transaction manager which registers with the SS7 processes to gain access to the SS7 stack. The transaction manager 90 receives and sends IS-41 messages and responses through the SS7 processes. The transaction manager 90 links with the DB 88 in order to use the database server.
Log 92 is a library that provides a functional API to record every IS-41 message and response that is sent and received. This API is used to record all of the IS-41 messages and responses that pass through the international gateway 10. Trace 94 is a library that provides debugging aids for integration and testing. SNMP Agent 96 is a process that forwards simple network management protocol (SNMP) traps to the network manager such as the Openview Network Manager from Hewlett Packard. This SNMP Agent 96 also provides a message queue for the other application software entities to send event/alarm information, which is converted to a trap and forwarded as appropriate. Bulk Update 98 is a script that updates the database with large numbers of records or entries, generally with respect to users. Vision Feed 100 is a process that provides a continuous feed of all IS-41 messages and responses being sent and received by the international gateway 10 to a separate entity for further processing (billing, debugging, network problems, etc.). IS-41 API & Vendor's SS7 102 stack is an IS-41 API built on top of the SS7 stack. The SS7 stack functionality is handled within separate processes, i.e., they are not libraries. The IS-41 API is incorporated in these separate processes. DIR 104 is a platform configuration task called the Director. It provides a command line interface for configuring the SS7 stack and all network parameters associated with setting up the international gateway 10 as a functional network entity. The DIR 104 also can be used to control the SS7 stack processes.
Conclusion
The present inventions include methods, systems, and apparatus that allow a home wireless system to obtain a temporary location directory number (TLDN) so that the home wireless system may appropriately route a call received for a wireless unit roaming in a visited wireless system. Advantageously, the present inventions correct or otherwise solve the problems associated with the insufficiency or invalidity in the provision of TLDNs that are exchanged between wireless communications systems which are located respectively in countries or systems having disparate numbering systems or other disparate processes related to the exchange of TLDNs.
From the foregoing description of the exemplary embodiments and the several alternatives, other alternative constructions of the present invention may suggest themselves to those skilled in the art. Therefore, the scope of the present invention is to be limited only to the claims below and the equivalents thereof.

Claims

ClaimsWe claim:
1. A method to allow a home mobile switching center (MSC-H) to obtain a temporary location directory number (TLDN) for a wireless unit roaming in a visited system so as to properly route a call for the wireless unit to a visited mobile switching center (MSC-V) serving the wireless unit in the visited system, comprising:
A. in response to receiving the call for the wireless unit, causing the MSC-H to route a request for the TLDN to an international gateway; B. in response to receiving the request for the TLDN, causing the international gateway to create a new request based on the request for the TLDN, and to route the new request to the MSC-V;
C. in response to receiving the new request, causing the MSC-V to provide the
TLDN in a message to the international gateway; and D. in response to receiving the TLDN in the message, causing the international gateway to create a new message based on the message, to include the TLDN in the new message, and to route the new message to the MSC-H.
2. The method of Claim 1, wherein action D comprises causing the international gateway to include an access code and/or a country code to the new message based on the location of the MSC-V.
3. An international gateway for use in obtaining a temporary location directory number (TLDN) for a home mobile switching center (MSC-H) with respect to a wireless unit roaming in a visited system so as to have a call for the wireless unit properly routed from the MSC-H to a visited mobile switching center (MSC-V) serving the wireless unit in the visited system, comprising:
A. an interface operative to receive a request for the TLDN with respect to the call for the wireless unit from the MSC-H;
B. a translator functionally connected to the interface and operative to cause the request for the TLDN to be routed to the MSC-V; C. the interface also operative to receive from the MSC-V a message including the TLDN with respect to the call for the wireless unit; and
D. the translator also operative to cause the message including the TLDN to be routed to the MSC-H.
4. The international gateway of Claim 2, wherein the translator is further operative to include an access code and/or a country code based on the location of the MSC-V in the message including the TLDN to be routed to the MSC-H.
PCT/US1999/026193 1998-11-05 1999-11-05 Methods and systems to obtain a tldn for a home system in response to a call received for a wireless unit roaming in a visited system WO2000027160A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU30985/00A AU3098500A (en) 1998-11-05 1999-11-05 Methods and systems to obtain a tldn for a home system in response to a call received for a wireless unit roaming in visited system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US10722498P 1998-11-05 1998-11-05
US60/107,224 1998-11-05

Publications (2)

Publication Number Publication Date
WO2000027160A1 true WO2000027160A1 (en) 2000-05-11
WO2000027160A9 WO2000027160A9 (en) 2000-11-02

Family

ID=22315520

Family Applications (2)

Application Number Title Priority Date Filing Date
PCT/US1999/026193 WO2000027160A1 (en) 1998-11-05 1999-11-05 Methods and systems to obtain a tldn for a home system in response to a call received for a wireless unit roaming in a visited system
PCT/US1999/026077 WO2000027159A1 (en) 1998-11-05 1999-11-05 Methods and systems to substantially prevent fraudulent use of a wireless unit roaming in a visited system

Family Applications After (1)

Application Number Title Priority Date Filing Date
PCT/US1999/026077 WO2000027159A1 (en) 1998-11-05 1999-11-05 Methods and systems to substantially prevent fraudulent use of a wireless unit roaming in a visited system

Country Status (3)

Country Link
US (3) US6211462B1 (en)
AU (2) AU1607300A (en)
WO (2) WO2000027160A1 (en)

Families Citing this family (135)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3977014B2 (en) * 1997-11-28 2007-09-19 新潟精密株式会社 Semiconductor device and manufacturing method thereof
US8330270B1 (en) * 1998-06-10 2012-12-11 Utac Hong Kong Limited Integrated circuit package having a plurality of spaced apart pad portions
US6143981A (en) 1998-06-24 2000-11-07 Amkor Technology, Inc. Plastic integrated circuit package and method and leadframe for making the package
US6615041B2 (en) * 1998-11-05 2003-09-02 Bellsouth Intellectual Property Corporation Methods and systems for providing information to a home system regarding a wireless unit roaming in a visited system
JP3839178B2 (en) * 1999-01-29 2006-11-01 株式会社ルネサステクノロジ Semiconductor device
KR100291040B1 (en) * 1999-03-15 2001-05-15 윤종용 method for controlling illegal users in PCS
DE19929028A1 (en) * 1999-06-25 2000-12-28 Bosch Gmbh Robert Completing pressure sensor by injection-molding around sensor assembly, is assisted by clamping lead frame mounting section in injection mold during injection of casing
FI19991847A (en) * 1999-08-31 2001-02-28 Nokia Networks Oy Utilization of subscriber data in a telecommunications system
KR100526844B1 (en) * 1999-10-15 2005-11-08 앰코 테크놀로지 코리아 주식회사 semiconductor package and its manufacturing method
KR20010056618A (en) * 1999-12-16 2001-07-04 프랑크 제이. 마르쿠치 Semiconductor package
KR20010037247A (en) * 1999-10-15 2001-05-07 마이클 디. 오브라이언 Semiconductor package
US6847103B1 (en) * 1999-11-09 2005-01-25 Amkor Technology, Inc. Semiconductor package with exposed die pad and body-locking leadframe
KR100421774B1 (en) * 1999-12-16 2004-03-10 앰코 테크놀로지 코리아 주식회사 semiconductor package and its manufacturing method
KR20010058583A (en) * 1999-12-30 2001-07-06 마이클 디. 오브라이언 Lead End Grid Array Semiconductor package
US6559525B2 (en) * 2000-01-13 2003-05-06 Siliconware Precision Industries Co., Ltd. Semiconductor package having heat sink at the outer surface
JP2002016181A (en) * 2000-04-25 2002-01-18 Torex Semiconductor Ltd Semiconductor device, manufacturing method thereof, and electrodeposition frame
US7042068B2 (en) 2000-04-27 2006-05-09 Amkor Technology, Inc. Leadframe and semiconductor package made using the leadframe
US6372551B1 (en) * 2000-05-12 2002-04-16 Siliconware Precison Industries Co., Ltd. Method of manufacturing an image-sensor integrated circuit package without resin flash on lead frame and with increased wire bondability
US6696749B1 (en) * 2000-09-25 2004-02-24 Siliconware Precision Industries Co., Ltd. Package structure having tapering support bars and leads
JP3399453B2 (en) * 2000-10-26 2003-04-21 松下電器産業株式会社 Semiconductor device and manufacturing method thereof
ES2251347T3 (en) * 2000-11-24 2006-05-01 Telefonaktiebolaget Lm Ericsson (Publ) FRAUD DETECTION METHOD FOR MOBILE TELECOMMUNICATIONS NETWORKS.
US7184764B2 (en) * 2001-02-08 2007-02-27 Starhome Gmbh Method and apparatus for supporting cellular data communication to roaming mobile telephony devices
US6545345B1 (en) 2001-03-20 2003-04-08 Amkor Technology, Inc. Mounting for a package containing a chip
KR100369393B1 (en) * 2001-03-27 2003-02-05 앰코 테크놀로지 코리아 주식회사 Lead frame and semiconductor package using it and its manufacturing method
KR100393448B1 (en) * 2001-03-27 2003-08-02 앰코 테크놀로지 코리아 주식회사 Semiconductor package and method for manufacturing the same
US6597059B1 (en) 2001-04-04 2003-07-22 Amkor Technology, Inc. Thermally enhanced chip scale lead on chip semiconductor package
DE10117889A1 (en) * 2001-04-10 2002-10-24 Osram Opto Semiconductors Gmbh Leadframe used for a light emitting diode component comprises a chip assembly region, a wire connecting region, external electrical connecting strips, and a support part coupled with a thermal connecting part
US20040121760A1 (en) * 2001-04-25 2004-06-24 Illkka Westman Authentication in a communication system
US6437429B1 (en) * 2001-05-11 2002-08-20 Walsin Advanced Electronics Ltd Semiconductor package with metal pads
US7057273B2 (en) 2001-05-15 2006-06-06 Gem Services, Inc. Surface mount package
US6531782B1 (en) * 2001-06-19 2003-03-11 Cypress Semiconductor Corp. Method of placing die to minimize die-to-die routing complexity on a substrate
US20070108609A1 (en) * 2001-07-19 2007-05-17 Samsung Electronics Co., Ltd. Bumped chip carrier package using lead frame and method for manufacturing the same
KR100445072B1 (en) * 2001-07-19 2004-08-21 삼성전자주식회사 Bumped chip carrier package using lead frame and method for manufacturing the same
US6674157B2 (en) 2001-11-02 2004-01-06 Fairchild Semiconductor Corporation Semiconductor package comprising vertical power transistor
SE521103C2 (en) * 2001-12-28 2003-09-30 Ericsson Telefon Ab L M A method and system to facilitate the delivery of services to users in a communication system
US6879811B1 (en) * 2001-12-31 2005-04-12 Bellsouth Intellectual Property Corp. System and method for providing cellular telephone service during cluster testing
US6566749B1 (en) 2002-01-15 2003-05-20 Fairchild Semiconductor Corporation Semiconductor die package with improved thermal and electrical performance
US20030137976A1 (en) * 2002-01-22 2003-07-24 Yanong Zhu Method and apparatus for IP based metered service on demands network
TW533566B (en) * 2002-01-31 2003-05-21 Siliconware Precision Industries Co Ltd Short-prevented lead frame and method for fabricating semiconductor package with the same
US6621140B1 (en) * 2002-02-25 2003-09-16 Rf Micro Devices, Inc. Leadframe inductors
US6608366B1 (en) 2002-04-15 2003-08-19 Harry J. Fogelson Lead frame with plated end leads
KR100843737B1 (en) * 2002-05-10 2008-07-04 페어차일드코리아반도체 주식회사 Semiconductor package having improved reliability of solder joint
US6821817B1 (en) 2002-09-03 2004-11-23 Asat Ltd. Premolded cavity IC package
US7732914B1 (en) 2002-09-03 2010-06-08 Mclellan Neil Cavity-type integrated circuit package
US7723210B2 (en) 2002-11-08 2010-05-25 Amkor Technology, Inc. Direct-write wafer level chip scale package
US6905914B1 (en) 2002-11-08 2005-06-14 Amkor Technology, Inc. Wafer level package and fabrication method
US6798047B1 (en) 2002-12-26 2004-09-28 Amkor Technology, Inc. Pre-molded leadframe
US6806580B2 (en) * 2002-12-26 2004-10-19 Fairchild Semiconductor Corporation Multichip module including substrate with an array of interconnect structures
US6750545B1 (en) 2003-02-28 2004-06-15 Amkor Technology, Inc. Semiconductor package capable of die stacking
US6794740B1 (en) 2003-03-13 2004-09-21 Amkor Technology, Inc. Leadframe package for semiconductor devices
US8108916B2 (en) * 2003-05-21 2012-01-31 Wayport, Inc. User fraud detection and prevention of access to a distributed network communication system
CN100490140C (en) * 2003-07-15 2009-05-20 飞思卡尔半导体公司 Double gauge lead frame
US20050101313A1 (en) * 2003-08-11 2005-05-12 Stanco Bart D. Method and apparatus for communicating phone with radio services and the like
JP3789443B2 (en) * 2003-09-01 2006-06-21 Ｎｅｃエレクトロニクス株式会社 Resin-sealed semiconductor device
US6867072B1 (en) 2004-01-07 2005-03-15 Freescale Semiconductor, Inc. Flipchip QFN package and method therefor
US7362730B2 (en) 2004-02-19 2008-04-22 Research In Motion Limited Apparatus, and associated method, for facilitating routing of data in a radio communication system having a mobile node capable of roaming movement
US20050242425A1 (en) * 2004-04-30 2005-11-03 Leal George R Semiconductor device with a protected active die region and method therefor
US7759775B2 (en) * 2004-07-20 2010-07-20 Alpha And Omega Semiconductor Incorporated High current semiconductor power device SOIC package
US7208818B2 (en) * 2004-07-20 2007-04-24 Alpha And Omega Semiconductor Ltd. Power semiconductor package
KR101120718B1 (en) * 2004-08-20 2012-03-23 프리스케일 세미컨덕터, 인크. Dual gauge leadframe
CN1755929B (en) * 2004-09-28 2010-08-18 飞思卡尔半导体（中国）有限公司 Method for forming semiconductor package and its structure
US8272032B2 (en) * 2004-11-10 2012-09-18 Mlb Advanced Media, L.P. Multiple user login detection and response system
US20060214271A1 (en) * 2005-03-23 2006-09-28 Jeremy Loraine Device and applications for passive RF components in leadframes
US7615851B2 (en) * 2005-04-23 2009-11-10 Stats Chippac Ltd. Integrated circuit package system
US7507603B1 (en) 2005-12-02 2009-03-24 Amkor Technology, Inc. Etch singulated semiconductor package
US7572681B1 (en) 2005-12-08 2009-08-11 Amkor Technology, Inc. Embedded electronic component package
JP5103731B2 (en) * 2005-12-12 2012-12-19 三菱電機株式会社 Mold package
US7902660B1 (en) 2006-05-24 2011-03-08 Amkor Technology, Inc. Substrate for semiconductor device and manufacturing method thereof
US7968998B1 (en) 2006-06-21 2011-06-28 Amkor Technology, Inc. Side leaded, bottom exposed pad and bottom exposed lead fusion quad flat semiconductor package
US7683461B2 (en) * 2006-07-21 2010-03-23 Stats Chippac Ltd. Integrated circuit leadless package system
US20080073757A1 (en) * 2006-09-25 2008-03-27 Steven Alfred Kummerl Semiconductor dies and methods and apparatus to mold lock a semiconductor die
US7687893B2 (en) 2006-12-27 2010-03-30 Amkor Technology, Inc. Semiconductor package having leadframe with exposed anchor pads
US7829990B1 (en) 2007-01-18 2010-11-09 Amkor Technology, Inc. Stackable semiconductor package including laminate interposer
US7982297B1 (en) 2007-03-06 2011-07-19 Amkor Technology, Inc. Stackable semiconductor package having partially exposed semiconductor die and method of fabricating the same
US7977774B2 (en) 2007-07-10 2011-07-12 Amkor Technology, Inc. Fusion quad flat semiconductor package
US7687899B1 (en) 2007-08-07 2010-03-30 Amkor Technology, Inc. Dual laminate package structure with embedded elements
US7595226B2 (en) * 2007-08-29 2009-09-29 Freescale Semiconductor, Inc. Method of packaging an integrated circuit die
US7777351B1 (en) 2007-10-01 2010-08-17 Amkor Technology, Inc. Thin stacked interposer package
US8089159B1 (en) 2007-10-03 2012-01-03 Amkor Technology, Inc. Semiconductor package with increased I/O density and method of making the same
US7847386B1 (en) 2007-11-05 2010-12-07 Amkor Technology, Inc. Reduced size stacked semiconductor package and method of making the same
US7956453B1 (en) 2008-01-16 2011-06-07 Amkor Technology, Inc. Semiconductor package with patterning layer and method of making same
US7723852B1 (en) 2008-01-21 2010-05-25 Amkor Technology, Inc. Stacked semiconductor package and method of making same
US8208919B2 (en) 2008-02-06 2012-06-26 Cellco Partnership Route optimization using network enforced, mobile implemented policy
US20090249456A1 (en) 2008-03-25 2009-10-01 Level 3 Communications Llc System and method for authorizing and validating user agents based on user agent location
US8067821B1 (en) 2008-04-10 2011-11-29 Amkor Technology, Inc. Flat semiconductor package with half package molding
US7768135B1 (en) 2008-04-17 2010-08-03 Amkor Technology, Inc. Semiconductor package with fast power-up cycle and method of making same
US7808084B1 (en) 2008-05-06 2010-10-05 Amkor Technology, Inc. Semiconductor package with half-etched locking features
US8125064B1 (en) 2008-07-28 2012-02-28 Amkor Technology, Inc. Increased I/O semiconductor package and method of making same
US8184453B1 (en) 2008-07-31 2012-05-22 Amkor Technology, Inc. Increased capacity semiconductor package
US7847392B1 (en) 2008-09-30 2010-12-07 Amkor Technology, Inc. Semiconductor device including leadframe with increased I/O
US7989933B1 (en) 2008-10-06 2011-08-02 Amkor Technology, Inc. Increased I/O leadframe and semiconductor device including same
US8008758B1 (en) 2008-10-27 2011-08-30 Amkor Technology, Inc. Semiconductor device with increased I/O leadframe
US8089145B1 (en) 2008-11-17 2012-01-03 Amkor Technology, Inc. Semiconductor device including increased capacity leadframe
US8072050B1 (en) 2008-11-18 2011-12-06 Amkor Technology, Inc. Semiconductor device with increased I/O leadframe including passive device
US7875963B1 (en) 2008-11-21 2011-01-25 Amkor Technology, Inc. Semiconductor device including leadframe having power bars and increased I/O
US7982298B1 (en) 2008-12-03 2011-07-19 Amkor Technology, Inc. Package in package semiconductor device
US8487420B1 (en) 2008-12-08 2013-07-16 Amkor Technology, Inc. Package in package semiconductor device with film over wire
US8680656B1 (en) 2009-01-05 2014-03-25 Amkor Technology, Inc. Leadframe structure for concentrated photovoltaic receiver package
US20170117214A1 (en) 2009-01-05 2017-04-27 Amkor Technology, Inc. Semiconductor device with through-mold via
US8058715B1 (en) 2009-01-09 2011-11-15 Amkor Technology, Inc. Package in package device for RF transceiver module
US8026589B1 (en) 2009-02-23 2011-09-27 Amkor Technology, Inc. Reduced profile stackable semiconductor package
US7960818B1 (en) 2009-03-04 2011-06-14 Amkor Technology, Inc. Conformal shield on punch QFN semiconductor package
US8575742B1 (en) 2009-04-06 2013-11-05 Amkor Technology, Inc. Semiconductor device with increased I/O leadframe including power bars
US8796561B1 (en) 2009-10-05 2014-08-05 Amkor Technology, Inc. Fan out build up substrate stackable package and method
US8937381B1 (en) 2009-12-03 2015-01-20 Amkor Technology, Inc. Thin stackable package and method
US9691734B1 (en) 2009-12-07 2017-06-27 Amkor Technology, Inc. Method of forming a plurality of electronic component packages
US9049292B2 (en) * 2010-02-25 2015-06-02 Cisco Technology, Inc. Authentication to facilitate communication with roaming devices
US8324511B1 (en) 2010-04-06 2012-12-04 Amkor Technology, Inc. Through via nub reveal method and structure
US20110278054A1 (en) * 2010-05-14 2011-11-17 I-Tseng Lee Circuit board with notched conductor pads
US8294276B1 (en) 2010-05-27 2012-10-23 Amkor Technology, Inc. Semiconductor device and fabricating method thereof
CN102339763B (en) 2010-07-21 2016-01-27 飞思卡尔半导体公司 The method of assembling integrated circuit (IC)-components
US8440554B1 (en) 2010-08-02 2013-05-14 Amkor Technology, Inc. Through via connected backside embedded circuit features structure and method
US8487445B1 (en) 2010-10-05 2013-07-16 Amkor Technology, Inc. Semiconductor device having through electrodes protruding from dielectric layer
US8387121B1 (en) 2010-11-19 2013-02-26 Amdocs Software Systems Limited System, method, and computer program for authenticating a customer using a network provided by another service provider
US8791501B1 (en) 2010-12-03 2014-07-29 Amkor Technology, Inc. Integrated passive device structure and method
US8674485B1 (en) 2010-12-08 2014-03-18 Amkor Technology, Inc. Semiconductor device including leadframe with downsets
JP5796956B2 (en) * 2010-12-24 2015-10-21 セミコンダクター・コンポーネンツ・インダストリーズ・リミテッド・ライアビリティ・カンパニー Circuit device and manufacturing method thereof
US8390130B1 (en) 2011-01-06 2013-03-05 Amkor Technology, Inc. Through via recessed reveal structure and method
US8648450B1 (en) 2011-01-27 2014-02-11 Amkor Technology, Inc. Semiconductor device including leadframe with a combination of leads and lands
TWI557183B (en) 2015-12-16 2016-11-11 財團法人工業技術研究院 Siloxane resin composition, and photoelectric device employing the same
US8466539B2 (en) 2011-02-23 2013-06-18 Freescale Semiconductor Inc. MRAM device and method of assembling same
US8552548B1 (en) 2011-11-29 2013-10-08 Amkor Technology, Inc. Conductive pad on protruding through electrode semiconductor device
US9704725B1 (en) 2012-03-06 2017-07-11 Amkor Technology, Inc. Semiconductor device with leadframe configured to facilitate reduced burr formation
US9048298B1 (en) 2012-03-29 2015-06-02 Amkor Technology, Inc. Backside warpage control structure and fabrication method
US9129943B1 (en) 2012-03-29 2015-09-08 Amkor Technology, Inc. Embedded component package and fabrication method
JP6092645B2 (en) * 2013-02-07 2017-03-08 エスアイアイ・セミコンダクタ株式会社 Semiconductor device
KR101486790B1 (en) 2013-05-02 2015-01-28 앰코 테크놀로지 코리아 주식회사 Micro Lead Frame for semiconductor package
KR101563911B1 (en) 2013-10-24 2015-10-28 앰코 테크놀로지 코리아 주식회사 Semiconductor package
US9401682B2 (en) 2014-04-17 2016-07-26 Freescale Semiconductor, Inc. Structure for a radio frequency power amplifier module within a radio frequency power amplifier package
US9673122B2 (en) 2014-05-02 2017-06-06 Amkor Technology, Inc. Micro lead frame structure having reinforcing portions and method
DE102014111995B4 (en) * 2014-08-21 2022-10-13 Infineon Technologies Ag METHODS OF GRASPING, MOVING AND ELECTRICAL TESTING OF A SEMICONDUCTOR MODULE
US9418920B2 (en) * 2015-01-05 2016-08-16 Stmicroelectronics Pte Ltd Integrated circuit (IC) package with thick die pad functioning as a heat sink
US10115697B2 (en) 2015-12-22 2018-10-30 Nxp Usa, Inc. Coupling element, integrated circuit device and method of fabrication therefor
KR102298516B1 (en) * 2020-02-28 2021-09-27 주식회사 웨이브피아 Lead frame of hermetic RF chip package for incorporating the function of impedance matching
US11768229B2 (en) * 2021-08-23 2023-09-26 Allegro Microsystems, Llc Packaged current sensor integrated circuit

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1997017816A1 (en) * 1995-11-06 1997-05-15 Nokia Telecommunications Oy Service-dependent routing of a mobile-terminating call in a mobile communication system
WO1997036447A1 (en) * 1996-03-28 1997-10-02 Markport Limited A roaming interworking gateway for mobile telecommunications systems
WO1997038544A1 (en) * 1996-04-08 1997-10-16 Northern Telecom Limited Inter-network roaming arrangement
WO1997047151A2 (en) * 1996-06-07 1997-12-11 Telefonaktiebolaget Lm Ericsson (Publ) Cellular telephone network routing method and apparatus for internationally roaming mobile stations

Family Cites Families (29)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4901340A (en) 1988-09-19 1990-02-13 Gte Mobilnet Incorporated System for the extended provision of cellular mobile radiotelephone service
US5390245A (en) 1990-03-09 1995-02-14 Telefonaktiebolaget L M Ericsson Method of carrying out an authentication check between a base station and a mobile station in a mobile radio system
US5142654A (en) 1990-08-09 1992-08-25 Appex Corporation Cellular telephone system and method for dynamically switching between call routing options
JPH04280664A (en) * 1990-10-18 1992-10-06 Texas Instr Inc <Ti> Lead fram for semiconductor device
WO1993011646A1 (en) * 1991-12-03 1993-06-10 Electronic Data Systems Corporation Apparatus for detecting and preventing subscriber number tumbling in a cellular mobile telephone system
US5353331A (en) 1992-03-05 1994-10-04 Bell Atlantic Network Services, Inc. Personal communications service using wireline/wireless integration
KR100306988B1 (en) * 1992-10-26 2001-12-15 윌리엄 비. 켐플러 Device Package
SE516146C2 (en) 1994-04-05 2001-11-26 Ericsson Telefon Ab L M Method and device for roaming between different types of mobile networks
US5497412A (en) 1994-04-07 1996-03-05 Gte Telecommunication Services Incorporated Enhanced call delivery system for roaming cellular subscribers
DE4427072C1 (en) 1994-08-01 1996-02-22 Deutsche Telekom Mobil Call forwarding appts. for relaying call from first communication network to second remote group telephone system (GSM)
US5594234A (en) * 1994-11-14 1997-01-14 Texas Instruments Incorporated Downset exposed die mount pad leadframe and package
WO1996020574A1 (en) 1994-12-23 1996-07-04 Nokia Telecommunications Oy A method of routing an international call to a foreign mobile subscriber
US5699408A (en) 1995-08-07 1997-12-16 Motorola, Inc. International mobile station identification method and signaling system for cellular radiotelephones and systems
US5724658A (en) 1995-08-21 1998-03-03 Mci Communications Corporation Call routing to wireless roamers in mobile telecommunication systems
AU1459297A (en) * 1996-01-18 1997-08-11 Telefonaktiebolaget Lm Ericsson (Publ) Method and system for reducing fraud in a cellular telecommunications system
US6411807B1 (en) * 1996-02-05 2002-06-25 At&T Wireless Service, Inc. Roaming authorization system
US5978670A (en) * 1996-05-06 1999-11-02 Telefonaktiebolaget Lm Ericsson (Publ) System and method of automatic call barring in a radio telecommunications network
US5867788A (en) 1996-06-03 1999-02-02 Ericsson Inc. Coverting a routing address within a telecommunications network
WO1997049232A1 (en) * 1996-06-18 1997-12-24 Mitsubishi Denki Kabushiki Kaisha Portable telephone system
JPH1023509A (en) * 1996-07-03 1998-01-23 Toshiba Corp Mobile communication system, and its radio controller and terminal device
WO1998002011A1 (en) 1996-07-10 1998-01-15 American Pcs Communications, Llc A gateway unit
US6039624A (en) 1996-07-29 2000-03-21 At&T Wireless Services Inc. Method for allocating a mobile station TMSI
DE19635581C1 (en) 1996-09-02 1997-10-23 Siemens Ag Cellular mobile communications network subscriber location method
US5884158A (en) * 1996-10-15 1999-03-16 Pitney Bowes Inc. Cellular telephone authentication system using a digital certificate
US5970404A (en) * 1996-10-25 1999-10-19 Telefonaktiebolaget Lm Ericsson System and method of detecting and preventing fraudulent telephone calls in a radio telecommunications network
US6058301A (en) * 1996-11-27 2000-05-02 Airtouch Communications, Inc. Cellular fraud prevention using selective roaming
US6026298A (en) 1997-01-11 2000-02-15 Compaq Computer Corporation Method and apparatus for providing switch capability mediation in a mobile telephone system
US5943619A (en) 1997-04-29 1999-08-24 Ericsson Inc. Shared interworking of subscriber features within mobile telecommunications networks
US5915220A (en) 1997-05-05 1999-06-22 Northern Telecom Limited System and method for maintaining profile information in a telecommunications network

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1997017816A1 (en) * 1995-11-06 1997-05-15 Nokia Telecommunications Oy Service-dependent routing of a mobile-terminating call in a mobile communication system
WO1997036447A1 (en) * 1996-03-28 1997-10-02 Markport Limited A roaming interworking gateway for mobile telecommunications systems
WO1997038544A1 (en) * 1996-04-08 1997-10-16 Northern Telecom Limited Inter-network roaming arrangement
WO1997047151A2 (en) * 1996-06-07 1997-12-11 Telefonaktiebolaget Lm Ericsson (Publ) Cellular telephone network routing method and apparatus for internationally roaming mobile stations

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
YU J L: "OVERVIEW OF EIA/TIA IS-41", IEEE INTERNATIONAL SYMPOSIUM ON PERSONAL, INDOOR AND MOBILE RADIO COMMUNICATIONS, 19 October 1992 (1992-10-19), pages 220 - 224, XP000444612 *

Also Published As

Publication number Publication date
USRE41075E1 (en) 2010-01-12
WO2000027159A1 (en) 2000-05-11
AU3098500A (en) 2000-05-22
US6211462B1 (en) 2001-04-03
US6735429B1 (en) 2004-05-11
WO2000027159A9 (en) 2000-11-02
AU1607300A (en) 2000-05-22
WO2000027160A9 (en) 2000-11-02

Similar Documents

Publication Publication Date Title
WO2000027160A1 (en) Methods and systems to obtain a tldn for a home system in response to a call received for a wireless unit roaming in a visited system
US7289785B2 (en) Method and systems for providing information to a home system regarding a wireless unit roaming in a visited system
US7577431B2 (en) Providing multiple MSISDN numbers in a mobile device with a single IMSI
US5497412A (en) Enhanced call delivery system for roaming cellular subscribers
JP3544978B2 (en) Call handling for unregistered mobile subscribers in mobile telephone systems
CA2239649C (en) Method and apparatus for providing partitioned telecommunication services
US6735441B1 (en) Methods and systems for providing mobile telecommunications network services in a routing node
US7996006B2 (en) Wireless mobile call location and delivery for non-geographic numbers using a wireline SSP+SCP/wireless HLR interface
JP2001086546A (en) Signal transmitting method for electric communication network and converting device
CA2313036C (en) Wireless mobile call location and delivery for non-geographic numbers using a wireline ssp+scp/wireless hlr interface
US6026298A (en) Method and apparatus for providing switch capability mediation in a mobile telephone system
US6633755B1 (en) Method and nodes for routing a call in a mobile telecommunication network
US6085083A (en) Method and apparatus for providing fraud protection mediation in a mobile telephone system
US20120320899A1 (en) Routing Call To UMA-Capable Terminals Using A Geographic Number
US6226511B1 (en) Method and apparatus for configuration of authentication center operations in a mobile telephone system
EP1555844B1 (en) Method, apparatus and network arrangement for establishing calls in a communication network
WO1998031163A2 (en) Method and apparatus for implementing alias mobile id numbers in a mobile telephone system
WO1998031162A2 (en) Method and apparatus for limiting authentication directive initiation in a mobile telephone system

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AL AM AT AU AZ BA BB BG BR BY CA CH CN CR CU CZ DE DK DM EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG US UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
AK Designated states

Kind code of ref document: C2

Designated state(s): AE AL AM AT AU AZ BA BB BG BR BY CA CH CN CR CU CZ DE DK DM EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG US UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: C2

Designated state(s): GH GM KE LS MW SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

COP Corrected version of pamphlet

Free format text: PAGES 1/4-4/4, DRAWINGS, REPLACED BY NEW PAGES 1/4-4/4; DUE TO LATE TRANSMITTAL BY THE RECEIVING OFFICE

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase