WO2001022766A1 - System and method for call routing in an integrated telecommunications network having a packet-switched network portion and a circuit-switched network portion - Google Patents

System and method for call routing in an integrated telecommunications network having a packet-switched network portion and a circuit-switched network portion Download PDF

Info

Publication number
WO2001022766A1
WO2001022766A1 PCT/SE2000/001656 SE0001656W WO0122766A1 WO 2001022766 A1 WO2001022766 A1 WO 2001022766A1 SE 0001656 W SE0001656 W SE 0001656W WO 0122766 A1 WO0122766 A1 WO 0122766A1
Authority
WO
WIPO (PCT)
Prior art keywords
msc
serving
call
trunk
destination
Prior art date
Application number
PCT/SE2000/001656
Other languages
French (fr)
Inventor
Zeng-Jun Xiang
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
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
Priority to AU75650/00A priority Critical patent/AU7565000A/en
Application filed by Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Priority to EP00964825A priority patent/EP1214858A1/en
Priority to CA002385478A priority patent/CA2385478A1/en
Publication of WO2001022766A1 publication Critical patent/WO2001022766A1/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/02Processing 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/08Mobility data transfer
    • H04W8/10Mobility data transfer between location register and external networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/45Network directories; Name-to-address mapping
    • H04L61/4588Network directories; Name-to-address mapping containing mobile subscriber information, e.g. home subscriber server [HSS]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W92/00Interfaces specially adapted for wireless communication networks
    • H04W92/02Inter-networking arrangements

Definitions

  • the present invention relates to integrated telecommunication systems and, more particularly, to a system and method for routing long-distance calls in an integrated telecommunications network having a packet-switched network portion (for example, a network using Internet Protocol (IP)) that is coupled to circuit-switched network portions such as a wireless telephony network portion, a Public Switched Telephone Network (PSTN), or both.
  • IP Internet Protocol
  • PSTN Public Switched Telephone Network
  • PSN packet-switched network
  • CSN circuit-switched network
  • VoIP Voice-over-IP
  • H.323 High-power Bluetooth
  • ITU International Telecommunications Union
  • devices such as personal computers can inter-operate seamlessly in a vast inter-network, sharing a mixture of audio, video, and data across all forms of packet- based network portions.
  • the H.323 standard defines four major types of components for forming an inter-operable network: terminals, gateways, gatekeepers and Multipoint Control Units (MCUs).
  • terminals, gateways and MCUs of an H.323-based network are referred to as "endpoints.”
  • Gateways are typically provided between networks (or network portions) that operate based on different standards or protocols. For example, one or more gateways may be provided between a packet-switched network portion and a circuit-switched network portion.
  • Terminals are employed by end-users for accessing the network or portions thereof, for example, for placing or receiving a call, or for accessing multimedia content at a remote site.
  • the gatekeeper is typically defined as the entity on the network that provides address translation and controls access to the network for other H.323 components.
  • a gatekeeper is provided with the address translation capability for a specified portion of the network called a "zone.”
  • a zone comprises all terminals, gateways, and MCUs (that is, all endpoints) managed by a single gatekeeper.
  • a plurality of gatekeepers may be provided for managing the entire network, each gatekeeper being responsible for a particular zone.
  • gatekeepers may also provide other services to the terminals, gateways, and MCUs such as bandwidth management and gateway location.
  • GMSC gateway MSC
  • HLR Home Location Register
  • the VMSC for a Temporary Location Directory Number (TLDN) for routing the call to the mobile subscriber.
  • TLDN Temporary Location Directory Number
  • the TLDN is then passed to the GMSC for routing the call using circuit-switched trunks.
  • the GMSC-VMSC call leg can be a long distance call between two neighboring regions such as LATAs, two LATAs geographically separated from each other, or across a continent.
  • routing such long distance call segments over CSN portions defeats the rationale behind the use of VoEP network portions in integrated telecommunications networks having CSN portions.
  • the present invention is directed to an integrated telecommunications network having a packet-switched network portion (e.g., a Voice-over-Internet Protocol (VoEP) network portion) and one or more circuit- switched network (CSN) portions such as a PSTN or a radio telephony network.
  • VoIP Voice-over-Internet Protocol
  • CSN circuit- switched network
  • a Mobile Switching Center (MSC) serving one or more mobile subscribers is provided with an Internet Protocol (EP)-Interworking Unit interface towards the Vo P network portion.
  • MSC Mobile Switching Center
  • EP Internet Protocol
  • the radio telephony network also includes a Location Server (LS) containing mapping information between routing numbers (e.g., Temporary Location Directory Numbers or TLDNs), called party numbers (B-numbers) and EP addresses of entities to which a call can be routed over an EP trunk from the MSC.
  • LS Location Server
  • routing numbers e.g., Temporary Location Directory Numbers or TLDNs
  • B-numbers called party numbers
  • EP addresses e.g., Temporary Location Directory Numbers or TLDNs
  • a querying mechanism is provided in the MSC for interrogating the LS based upon a routing number, a called party number, or both, provided to the MSC.
  • the MSC obtains an EP address from the LS which is used for effectuating the EP trunk.
  • a plurality of Bearer Independent Call Control (BICC) messages and a plurality of Integrated Services Digital Network (ISDN) User Part (ISUP) messages are transmitted among the various nodes of the integrated telecommunications network, e.g., one or more MSCs with the EP interfaces, a Local Exchange ofthe PSTN, etc. for establishing the EP trunk.
  • a circuit-switched path such as, e.g, a Synchronous Transfer Mode (STM) trunk, is used for completing the call routing path.
  • STM Synchronous Transfer Mode
  • the present invention is directed to several embodiments of an EP -based long distance call routing method.
  • the call routing method relates to routing a call originated by a PSTN phone to an MS disposed in the integrated telecommunications network comprising the infrastructure as set forth above.
  • the call routing method relates to routing a call from an MS to a PSTN phone served by a Local Exchange.
  • the call routing method ofthe present invention is directed to routing a call originated by an MS to another MS that is located in its home area.
  • the call routing method relates to routing an MS-originated call to an MS that is located outside its home area.
  • FIG. 1A depicts a functional block diagram of an integrated telecommunications network provided in accordance with the teachings ofthe present invention
  • FIGS. IB and 1C depict two scenarios, respectively, of a routing scheme for MS-to-MS calls wherein the called MS is located in a home system of an integrated telecommunications network;
  • FIGS. 2A and 2B depict a flow chart of a call routing method for MS-to-MS calls wherein the called MS is located in a home system;
  • FIGS. 3A and 3B depict two scenarios, respectively, of a routing scheme for MS-to-MS calls wherein the called MS is roaming in a visited system of an integrated telecommunications network;
  • FIGS. 4A - 4D depict a flow chart of a call routing method for MS-to-MS calls wherein the called MS is roaming;
  • FIGS. 5 A and 5B depict two scenarios, respectively, of a routing scheme for PSTN-to-MS calls in an integrated telecommunications network
  • FIGS. 6A - 6C depict a flow chart of a call routing method for PSTN-to-MS calls in an integrated telecommunications network
  • FIGS. 7A and 7B depict two scenarios, respectively, of a routing scheme for MS-to-PSTN calls in an integrated telecommunications network
  • FIGS. 8A - 8C depict a flow chart of a call routing method for MS-to-PSTN calls in an integrated telecommunications network.
  • FIG. 1 A depicted therein is a functional block diagram of an integrated telecommunications network 10 provided in accordance with the teachings ofthe present invention. It should be appreciated that the integrated telecommunications network 10 is provided herein in order to exemplify the network-level infrastructure used in the various call routing scenarios described in greater detail hereinbelow.
  • the integrated telecommunications network 10 comprises a PSN portion 14 such as, for example, an H.323-based Voice-over-EP (VoEP) portion, that is coupled to a plurality CSN portions including, for example, one or more wireless telephony network portions (e.g., WL-CSN portions 12A and 12B) and a PSTN portion 50.
  • a PSN portion 14 such as, for example, an H.323-based Voice-over-EP (VoEP) portion, that is coupled to a plurality CSN portions including, for example, one or more wireless telephony network portions (e.g., WL-CSN portions 12A and 12B) and a PSTN portion 50.
  • VoIP Voice-over-EP
  • the wireless CSN portions ofthe integrated telecommunications network 10 may be realized in any known radio telephony technology, for example, a Time Division Multiple Access (TDMA), et cetera.
  • TDMA Time Division Multiple Access
  • et cetera any known radio telephony technology
  • WL-CSN portion 12A is shown in greater detail.
  • a Home Location Register (HLR) 16 is provided for maintaining a subscriber profile or record associated with a mobile subscriber / mobile station (MS) 28.
  • a Radio Base Station (RBS) 26 is included as part of the cellular infrastructure that comprises the WL-CSN portion 12A, in order to provide radio access services to the MS 28.
  • VLR Visitor Location Register
  • MSC Mobile Switching Center
  • an IP-Interworking Unit is provided as a hardware/firmware platform for interfacing and interworking between the switching node (i.e., the MSC/VLR combination in this exemplary embodiment) of the WL-CSN portion 12A and the PSN portion 14.
  • the EP-IWU 30A is provided as an EP interface to the MSC 24, and includes appropriate media gateway (MGW) functionality for carrying voice traffic (i.e., payload) over the EP -based PSN portion 14.
  • a Location Server (LS) 18 is provided as an entity within the WL-
  • CSN portion 12A that operates as a query-able database containing, preferably, mappings between CSN-based routable numbers (e.g., a called party's number (i.e., the B-number) or a Temporary Location Directory Number or TLDN) and an IP- network address of a signaling endpoint (e.g., an MSC having the EP-IWU interface)).
  • the switching node e.g., the MSC/VLR combination 24/22 or the MSC 24 separately
  • the switching node includes a hardware/software/firmware-based LS-query function 25 that facilitates interrogation by the MSC of the LS 18.
  • the LS is preferably configured in such a way that it returns a unique EP -network address of a "destination MSC" which, in some instances, may be an MSC that serves a called MS.
  • the MSC associated with the called MS does not have an IP interface (i.e., not IP-addressable)
  • the LS is configured so as to return the EP address of an MSC that is located closest thereto.
  • the destination MSC is the terminating EP signaling point connected to a Local Exchange (LE) disposed in the PSTN 50.
  • LE Local Exchange
  • FIG. IB depicted therein is an integrated telecommunications network 100 for effectuating a routing scheme for an MS-to-MS call in accordance with the teachings of the present invention.
  • Region3 102C is not involved in the call routing scenario contemplated herein and accordingly, will not be described in this section.
  • a call-originating party, MSI 108A is located in region 1 102 A, and is served byMSCl/VLRl 104A.
  • AnRBSl 106A provides radio access services to MSI 108A.
  • a call- terminating party, MS2 108B is located in region2 (home area for MS2 in this exemplary scenario), and is served by MSC2/VLR2 104B. Also, an RBS2 106B is included for providing radio access to MS2 108B.
  • MSC1 and MSC2 are provided with a suitable EP-IWU as described above. Also, a Location Server (LS 112) is provided within the network 100. Because
  • MSCl/VLRl and MSC2/VLR2 are located in two different geographic areas, the MS1-MS2 call is a long distance call.
  • MSC2 is treated as both the home gateway MSC and serving MSC of MS2.
  • a signaling path 114 is provided between MSC1 and LS 112.
  • another signaling path 116 is provided between MSC1 and MSC2.
  • An EP trunk path 118 is established therebetween for routing the voice payload associated with the call.
  • FIG. 1C depicts the network 100 in a form that is essentially identical to the network arrangement described above, except that the called party, that is MS2 108B, is served by an MSC (MSC3/VLR3 104) that has no direct EP-EWU interface.
  • MSC2 operates as the destination MSC, the MSC with IP interface that is closest to the serving MSC (i.e., MSC3).
  • MSC3 MSC3/VLR3 104
  • MSC3 MSC3/VLR3 104
  • MSC2 operates as the destination MSC, the MSC with IP interface that is closest to the serving MSC (i.e., MSC3).
  • an additional signaling path 124 and a circuit-switched trunk such as a Synchronous Transfer Mode (STM) trunk 122 (e.g., Tl or El) are established between the destination MSC and the serving MSC.
  • STM trunk 122 is
  • FIGS. 2 A and 2B depict a flow chart that describes a call routing method for the two exemplary network arrangements set forth above. It should be appreciated that the various messages depicted in FIGS. IB and 1C are used in setting forth the steps of the flow chart. Accordingly, FIGS. IB and 1C may again be refened to in connection with the flow chart shown in FIGS. 2 A and 2B. After MSCl receives a call initiation from MSI including MS2's B-number
  • MSCl performs a number analysis on the B-number (step 204) to determine if the call to MS2 is a long distance call (decision block 206). If it is not a long distance call, the call maybe completed using conventional local call termination procedures (step 208). If MSCl determines that the call involves a different region (i.e., a long distance call), it interrogates the Location Server by sending a Service Location Protocol (SLP) message (SERVICEREQ), together with the B-number ofthe called party (step 210) to query the EP address ofthe destination MSC (MSC is IP-capable and its EP address is provided in the LS's database), which can also be the serving MSC (as illustrated in FIG. IB).
  • SLP Service Location Protocol
  • SERP Service Location Protocol
  • the destination MSC is used as a transit MSC (as illustrated in FIG. 1C) in the case where serving MSC (MSC3 in this case) is not IP- capable.
  • the Location Server in response, returns the EP address of MSC2, which is provided as the IP-capable MSC, via a servicereq message to MSCl (steps 214 and 224).
  • MSCl the serving MSC for the called MS is IP-capable or not.
  • MSC2 is the EP -capable serving MSC for MS2
  • MSCl sends a Bearer Independent Call Control (BICC) message called Initial Address Message (IAM)+ to MSC2, including the B-number and the EP address of MSCl (step 216).
  • BICC Bearer Independent Call Control
  • the IAM+ message is essentially a modified N-ISDN User Part (N-ISUP) Z4 message, provided to effectuate the signaling as set forth herein.
  • N-ISUP N-ISDN User Part
  • ACM+ Address Complete Message
  • MSC2 MSC2
  • ANMJ+ BICC message called Answer Message
  • MSC2 MSC2
  • SDP Session Description Protocol
  • MSC2 is only the IP-capable destination MSC because the serving MSC (MSC3) is not IP-capable
  • an IAM+ message is also initially sent from MSCl to MSC2, after receiving the result from the LS (step 226).
  • an ISUP IAM message is forwarded by MS C2 to MSC3 (step 228).
  • MSC3 then sends an ACM message to MSC2 as an acknowledgment ofthe IAM message (step 230).
  • MSC2 initiates a BICC ACM+ message to MSCl (step 232).
  • the ISUP ⁇ N message is then sent by MSC3 to MSC2 (step 234), which is forwarded by MSC2 to MSC 1 by sending the BICC ANM+ message (step 236).
  • the STM trunk 122 is thereby established between MSC2 and MSC3.
  • the EP trunk 1 18 is subsequently established between MSC 1 and MSC2 via RTP and SDP to convey the voice payload as shown in the consolidated step 238.
  • FIGS. 3 A and 3B depict the relevant network arrangements for effectuating
  • MS 108B is no longer located in its home area, that is, region2 102B. Rather, it is now located in region3, being served by MSC4 VLR4 104D.
  • RBS4 106D is included in the infrastructure ofthe region for providing radio access services to MS2.
  • MSC2 is still provided as the home gateway MSC of MS2.
  • FIG. 3A depicts the scenario where the serving MSC (MSC4) does not have an EP interface and, accordingly, has to connect to a destination MSC (MSC3 in this exemplary embodiment; MSC3 is the IP- capable MSC that is geographically closest to MSC4) via an Enter-Exchange Carrier (IXC) 51 OB that is disposed between region2 and region3. Consequently, the network arrangement in FIG.
  • IXC Enter-Exchange Carrier
  • FIGS. 4A - 4D depict a flow chart for the call routing scenarios described above. Once again, FIGS. 3A and 3B may be referred to for locating appropriate signaling messages referenced in the flow chart. Further, it should be appreciated that most ofthe steps effectuated in this flow chart are similar to the steps described in the flow chart of FIGS. 2A and 2B. Accordingly, a concise description ofthe call routing method for each ofthe scenarios is set forth below without explicitly referring to the reference numerals ofthe flow chart shown in FIGS. 4A - 4D.
  • the call routing steps are as follows. After MSC 1 receives a call initiation from MS 1 including MS2's B-number, MSC 1 performs B-number analysis to determine if the call is a long distance call. If so, MSC 1 interrogates LS by sending the SLP SER VICEREQ message including the B-number to query the EP address ofthe destination MSC. Since MSC2 is provided to be the home gateway MSC of MS2, the SLP servicereq message (transmitted back to MSC 1 by LS) includes the EP address ofthe home gateway MSC, i.e., MSC2. A BICC IAM+ message is then sent by MSCl to MSC2, including the B- number and MSCl's EP address.
  • MSC2/VLR2 Upon receiving the IAM+ message, MSC2/VLR2 checks its record and determines that MS2 is not in its home system, i.e., MS2 has roamed out. An ANSI- 41 LOCREQ is transmitted by MSC2 to HLR to query the location ofthe serving MSC that currently serves MS2. Upon receiving the LOCREQ message, HLR verifies the active services and queries the serving MSC4/VLR4 in region3 by transmitting an ANSI-41 ROUTREQ message. The pre-routing call setup is done by MSC4bymeans of paging MS2. The serving MSC4/VLR4 replies with an ANSI-41 routreq message containing the routing number (TLDN). Thereafter, HLR sends the answer message locreq including the TLDN to MSC2.
  • TLDN routing number
  • An SLP SERVICEREQ message including the TLDN of MSC4 is then sent by MSC2 to LS to query the EP address of MSC4.
  • the returned servicereq message from LS contains the EP address of MSC4.
  • a BICC IAM+ message is sent by MSC2 to MSC4.
  • a BICC ACM+ message is sent to MSC2 by MSC4 to acknowledge the IAM+ message.
  • a BICC A CM+ message is then forwarded by MSC2 to MSCl as an acknowledgment.
  • a BICC ANM+ message is sent to MSC2 by MSC4, which is subsequently forwarded to MSC 1 by MSC2.
  • the direct EP trunk between MSC 1 and MSC4 is then established via RTP and SDP to convey the voice payload associated with the call.
  • the call routing process is essentially similar to the above up to the SLP SERVICEREQ message sent by MSC2 to LS to query the IP address of MSC4. Since in this exemplary embodiment none of the MSCs in region3 are provided with a direct EP connection, a destination MSC (i.e., MSC3) is found in region2. Thereafter, an STM trunk is established via the IXC between MSC3 and MSC4, in addition to the EP trunk between MSCl and MSC3, for the purpose of call routing. It should, however, be understood that in other variations ofthe present invention, a destination MSC may be provided within region3, thereby obviating the need for the IXC.
  • FIGS. 5 A and 5B depict network arrangements for effectuating two exemplary embodiments of a PSTN-to-MS call routing scheme in accordance with the teachings ofthe present invention.
  • FIGS. 5 A and 5B depict network arrangements for effectuating two exemplary embodiments of a PSTN-to-MS call routing scheme in accordance with the teachings ofthe present invention.
  • a PSTN phone 504 served by a Local Exchange (LEI) 508 is provided as the call-originating entity in regionl 102A.
  • MSI 108 A is provided as the call-terminating party and, in this exemplary embodiment, is roaming out of its home system (MSC2/VLR2 104B) provided in region 2.
  • MSC3/VLR3 104C is provided as the serving system for MS 1 in the visited region, region3 102C.
  • An IXC 51 OA is provided between regionl and region2 for establishing an STM trunk (first circuit-switched trunk path involving trunk segments 564 and 568) between LEI and MSC2.
  • the serving MSC (MSC3) is provided with an EP interface (i.e., EP-EWU interface).
  • the serving MSC (MSC4) is not IP-capable and, therefore, a separate destination MSC (MSC3) is provided in FIG. 5B. Accordingly, another STM trunk (second circuit-switched trunk path 582) is established between MSC3 and MSC4 for the scenario illustrated in FIG. 5B.
  • the destination MSC IP-capable MSC that is closest to the serving MSC
  • region3 where the serving MSC is also located
  • the destination MSC may be outside the region ofthe serving MSC, thereby necessitating the use of another IXC.
  • FIGS. 6A - 6C depict a flow chart for a call routing scheme for the network arrangements set forth above.
  • the steps provided in the flow chart are believed to be self-explanatory and, in large part, similar to the steps of the call routing methods already set forth hereinabove. Accordingly, a concise description ofthe flow chart is provided below.
  • an exemplary embodiment of the PSTN-to-MS call routing scheme is as follows. After LE 1 receives a call initiation from the PSTN phone including MS 1 's B-number, LEI performs a number analysis and routes the call to MSl's home gateway MSC
  • MSC2 via IXC by sending an IAM message.
  • an ANSI-41 LOCREQ message is sent by MSC2 to HLR to query the location ofthe serving MSC.
  • HLR verifies the active services and queries the serving MSC3/VLR3 with an ANSI-41 ROUTREQ message.
  • the pre-routing call setup is done by MSC3 by means of paging MSI .
  • the serving MSC3 replies with an ANSI-41 routreq message which includes the routing number (i.e., TLDN).
  • HLR Upon receiving the routreq message, HLR sends the locreq message including the TLDN to MSC2.
  • MSC2 sends an SLP SERVICEREQ message containing the TLDN ofthe serving MSC3 to LS in order to query the EP address of MSC3.
  • a servicereq message is sent back to MSC2 from LS with MSC3's EP address.
  • a BICC IAM+ message is then sent by MSC2 to MSC3.
  • a BICC ACM+ message is returned byMSC3 to MSC2 in order to acknowledge the IAM+ message.
  • MSC2 Upon receiving the ACM+ message, MSC2 sends an ISUP A CM message to LE 1 via IXC to acknowledge the ELWmessage sent by LE 1. Afterwards, a BICC ANM+ message is sent to MSC2 by MSC3. MSC2 then sends an ISUP A CM message to LE 1 via IXC to acknowledge the ELWmessage sent by LE 1. Afterwards, a BICC ANM+ message is sent to MSC2 by MSC3. MSC2 then sends an ISUP A CM message to LE 1 via IXC to acknowledge the ELWmessage sent by LE 1. Afterwards, a BICC ANM+ message is sent to MSC2 by MSC3. MSC2 then sends an ISUP A CM message to LE 1 via IXC to acknowledge the ELWmessage sent by LE 1. Afterwards, a BICC ANM+ message is sent to MSC2 by MSC3. MSC2 then sends an ISUP A CM message to LE 1 via IXC to acknowledge the
  • the call routing process is essentially similar up to the servicereq message from LS which now includes the EP address ofthe destination MSC (i.e., MSC3).
  • MSC3 the destination MSC
  • additional ISUP and BICC messaging is done in order to effectuate an STM trunk between MSC3 and MSC4.
  • the call leg between MSC2 and MSC3 is still routed over an EP trunk via RTP and SDP.
  • FIGS. 7A and 7B depict two network arrangements for effectuating MS-to- PSTN call routing.
  • an EP-capable MSC (MSC3) 104C within region3 is used as a destination MSC to route the call via the EP network to the called PSTN phone 586 (served by LE3 584).
  • MSC3 EP-capable MSC
  • FIG. 7B since there are no EP-capable MSCs in region3, MSC2 in region 2 (which is the closest EP-capable MSC to LE3) is used as a destination MSC to route the call via the EP network to the called PSTN phone 586.
  • FIGS. 8A - 8C depict a flow chart for an exemplary embodiment ofthe MS-to- PSTN call routing scheme for the network arrangements set forth above. Again, only a concise account thereof is set forth below.
  • MSC 1 After MSCl receives a call initiation from MSI together with the PSTN phone's B-number, MSC 1 performs a number analysis to determine if the call is a long distance call. If so, MSC 1 interrogates LS by sending an SLP SER VICEREQ message including the B-number to query the EP address ofthe destination MSC if the call is EP-routable. Since the B-number is a PSTN number and LE has no direct EP connection, a servicereq message including the EP address of MSC 3 (closest MSC with EP capability in region3 with respect to LE3) is sent back to MSCl from LS. A BICC IAM+ message is then sent by MSC 1 to MSC3, including the B-number and the EP address of MSC 1.
  • MSC3/VLR3 Upon receiving the IAM+ message, MSC3/VLR3 sends an LAM message to LE3. An ACM message is sent back by LE3 to MSC3 as an acknowledgment to the J4 message. After receiving the A CM message, MSC3 sends a BICC ACM+ message to acknowledge the IAM+ message. An ISUP viN message is sent thereafter by LE3 to MSC3. Once MSC3 receives the ANM message, it sends a BICC ANM+ message to MSCl . Subsequently, an EP trunk is established between MSC 1 and MSC3 via RTP and SDP, and a circuit- switched STM trunk (first circuit- switched trunk) is established between MSC3 and LE3 for carrying the voice payload.
  • STM trunk first circuit- switched trunk
  • the SLP servicereq message from LS contains the EP address of MSC2, which is the geographically closest MSC to LE3.
  • a BICC IAM+ message is then sent by MSCl to MSC2 together with the PSTN phone's B-number and the EP address of MSCl .
  • second circuit-switched trunk is established between MSC2 and LE3 via the IXC, in addition to the EP trunk between MSCl and MSC2, for the purpose of call routing.
  • the present solution advantageously provides an EP -based call routing scheme for use with an integrated telecommunications network having a PSN portion that is coupled to one or more CSN portions (wireless, wireline, or both). It should be apparent that the present invention efficiently utilizes the EP "backbone" for routing long distance calls by providing a cellular infrastructure entity (i.e., a Location Server) that includes a query-able database containing mapping data between routable numbers and EP addresses of entities provided with an EWU interface. It should further be appreciated that the EP call routing provided herein does not involve the H.323 protocol. Also, because the Location Server is provided to be a cellular component that can interface with EP-capable MSCs, current cellular infrastructures may be leveraged to a greater extent in integrated telecommunications networks as the components can be retrofitted with appropriate EP interfaces etc.
  • a cellular infrastructure entity i.e., a Location Server
  • the Location Server is provided to be a cellular component that can interface with EP-capable MSCs, current cellular

Abstract

A system and method for IP-based call routing in an integrated telecommunications network having a packet-switched network portion (e.g., a Voice-over-Internet Protocol (VoIP) network portion (14) and one or more circuit-switched network (CSN) portions (12) such as a PSTN (50) or a radio telephony network. A mobile Switching Center (MSC (24)) serving one or more mobile subscribers (28) is provided with an Internet Protocol (IP)-Interworking Unit interface (30) towards the VoIP network portion. The radio telephony network also includes a Location Server (LS(18)) containing mapping information between routing numbers (e.g., Temporary Location Directory Numbers or TLDNs), called party numbers (B-numbers) and IP addresses of entities to which a call can be routed over an IP trunk from the MSC. A querying mechanism is provided in the MSC for interrogating the LS based upon a routing number, a called party number, or both, provided to the MSC. The MSC obtains an IP address from the LS which is used for effectuating the IP trunk. A plurality of Bearer Independent Call Control (BICC) messages and a plurality of Integrated Services Digital Network (ISDN) User Part (ISUP) messages are transmitted among the various nodes of the integrated telecommunications network, e.g., one or more MSCs with the IP interface, a Local Exchange of the PSTN, etc. for establishing the IP trunk. Where an IP trunk is not available, a circuit-switched path (e.g., a Synchronous Transfer Mode (STM) trunk), is utilized in the call path. The IP trunk is implemented using Real-time Transfer Protocol (RTP) and Session Description Protocol (SDP) to convey the voice payload associated with the call.

Description

SYSTEM AND METHOD FOR CALL ROUTING IN AN INTEGRATED TELECOMMUNICATIONS NETWORK HAVING A PACKET- SWITCHED NETWORK PORTION AND A CIRCUIT-SWITCHED
NETWORK PORTION
BACKGROUND OF THE INVENTION
Technical Field ofthe Invention
The present invention relates to integrated telecommunication systems and, more particularly, to a system and method for routing long-distance calls in an integrated telecommunications network having a packet-switched network portion (for example, a network using Internet Protocol (IP)) that is coupled to circuit-switched network portions such as a wireless telephony network portion, a Public Switched Telephone Network (PSTN), or both. Description of Related Art Coupled with the phenomenal growth in popularity ofthe Internet, there has been a tremendous interest in using packet-switched network (PSN) infrastructures (e.g., those based on IP addressing) as a replacement for the existing circuit-switched network (CSN) infrastructures used in today' s telephony. From the network operators ' perspective, the inherent traffic aggregation in packet-switched infrastructures allows for a reduction in the cost of transmission and the infrastructure cost per end-user.
Ultimately, such cost reductions enable the network operators to pass on the concomitant cost savings to the end-users. One ofthe well-known advantages ofthe IP-based networks with respect to voice transmission is that considerable savings in long distance charges may be realized for calls that are to be routed over multiple geographic regions such as, for example, Local Access and Transport Areas (LATAs).
Some of the market drivers that impel the existing Voice-over-IP (VoLP) technology are: improvements in the quality of EP telephony; the Internet phenomenon; emergence of standards; cost-effective price-points for advanced services via media- rich call management, et cetera. One ofthe emerging standards in this area is the well- known H.323 protocol, developed by the International Telecommunications Union (ITU) for multimedia communications over packet-based networks. Using the H.323 standard, devices such as personal computers can inter-operate seamlessly in a vast inter-network, sharing a mixture of audio, video, and data across all forms of packet- based network portions. The H.323 standard defines four major types of components for forming an inter-operable network: terminals, gateways, gatekeepers and Multipoint Control Units (MCUs). In general, terminals, gateways and MCUs of an H.323-based network are referred to as "endpoints." Gateways are typically provided between networks (or network portions) that operate based on different standards or protocols. For example, one or more gateways may be provided between a packet-switched network portion and a circuit-switched network portion. Terminals are employed by end-users for accessing the network or portions thereof, for example, for placing or receiving a call, or for accessing multimedia content at a remote site.
The gatekeeper is typically defined as the entity on the network that provides address translation and controls access to the network for other H.323 components.
Usually, a gatekeeper is provided with the address translation capability for a specified portion of the network called a "zone." Typically, a zone comprises all terminals, gateways, and MCUs (that is, all endpoints) managed by a single gatekeeper. Accordingly, a plurality of gatekeepers (sometimes referred to as a "gatekeeper cloud") may be provided for managing the entire network, each gatekeeper being responsible for a particular zone. In addition to address translation, gatekeepers may also provide other services to the terminals, gateways, and MCUs such as bandwidth management and gateway location.
Those of ordinary skill in the art should appreciate that although the current VoIP networks offer rudimentary location services, they are not adequate for the mobility management required of a wireless network. In part, this deficiency is due to the condition that the gatekeeper which provides for call routing services and the registration of other H.323 entities within the VoIP network is typically unaware of conventional telecommunications terminals. While this condition is not a problem for fixed wireline telephones in terms of providing savings in long distance charges (one of the most important economic motivations behind EP -based call routing), calls involving mobile stations (MSs) may still require establishing long distance circuit- switched trunks from one Mobile Switching Center (MSC) to another for routing. For example, when a call to a mobile subscriber is received in a gateway MSC (GMSC), it queries a Home Location Register (HLR) ofthe mobile subscriber for the location ofthe serving MSC. The HLR, in turn, queries the serving MSC (or, visited MSC or
VMSC) for a Temporary Location Directory Number (TLDN) for routing the call to the mobile subscriber. The TLDN is then passed to the GMSC for routing the call using circuit-switched trunks. Since the mobile station is no longer present in its home area, the GMSC-VMSC call leg can be a long distance call between two neighboring regions such as LATAs, two LATAs geographically separated from each other, or across a continent. Clearly, routing such long distance call segments over CSN portions defeats the rationale behind the use of VoEP network portions in integrated telecommunications networks having CSN portions.
It should also be understood that there are situations in some integrated telecommunications networks where long distance call segments are used even when the mobile subscriber is not roaming. For example, when the MSC that services the call originating mobile station (MS) and the MSC serving the home area of the terminating MS (that is, home gateway MSC) are situated in two different regions (e.g., LATAs), and the terminating MS is located in its home area, the call path still involves a CSN-based inter-MSC long distance trunk. Again, the economic advantages of a VoEP network are not achieved in such situations. Similarly, calls between a mobile station and a wireline phone served by a Local Exchange (LE) ofthe PSTN are also typically routed over CSN-based long distance trunks if different geographic regions are involved. Providing for EP -based call routing in such situations also gives rise to savings in long distance charges.
Based on the foregoing, it can be readily appreciated that there is an acute need for a solution that provides EP -based call routing so that the benefits of integrating VoEP network portions with CSN portions in an integrated telecommunications network are realized. The present invention provides such a solution.
SUMMARY OF THE INVENTION In one aspect, the present invention is directed to an integrated telecommunications network having a packet-switched network portion (e.g., a Voice-over-Internet Protocol (VoEP) network portion) and one or more circuit- switched network (CSN) portions such as a PSTN or a radio telephony network. A Mobile Switching Center (MSC) serving one or more mobile subscribers is provided with an Internet Protocol (EP)-Interworking Unit interface towards the Vo P network portion. The radio telephony network also includes a Location Server (LS) containing mapping information between routing numbers (e.g., Temporary Location Directory Numbers or TLDNs), called party numbers (B-numbers) and EP addresses of entities to which a call can be routed over an EP trunk from the MSC. A querying mechanism is provided in the MSC for interrogating the LS based upon a routing number, a called party number, or both, provided to the MSC. The MSC obtains an EP address from the LS which is used for effectuating the EP trunk. A plurality of Bearer Independent Call Control (BICC) messages and a plurality of Integrated Services Digital Network (ISDN) User Part (ISUP) messages are transmitted among the various nodes of the integrated telecommunications network, e.g., one or more MSCs with the EP interfaces, a Local Exchange ofthe PSTN, etc. for establishing the EP trunk. Where an EP trunk segment is not available or possible, a circuit-switched path such as, e.g, a Synchronous Transfer Mode (STM) trunk, is used for completing the call routing path. In another aspect, the present invention is directed to several embodiments of an EP -based long distance call routing method. In one embodiment, the call routing method relates to routing a call originated by a PSTN phone to an MS disposed in the integrated telecommunications network comprising the infrastructure as set forth above. In another embodiment, the call routing method relates to routing a call from an MS to a PSTN phone served by a Local Exchange. In yet another embodiment, the call routing method ofthe present invention is directed to routing a call originated by an MS to another MS that is located in its home area. In a still further embodiment, the call routing method relates to routing an MS-originated call to an MS that is located outside its home area.
BRIEF DESCRIPTION OF THE DRAWINGS A more complete understanding of the present invention may be had by reference to the following Detailed Description when taken in conjunction with the accompanying drawings wherein:
FIG. 1A depicts a functional block diagram of an integrated telecommunications network provided in accordance with the teachings ofthe present invention;
FIGS. IB and 1C depict two scenarios, respectively, of a routing scheme for MS-to-MS calls wherein the called MS is located in a home system of an integrated telecommunications network; FIGS. 2A and 2B depict a flow chart of a call routing method for MS-to-MS calls wherein the called MS is located in a home system;
FIGS. 3A and 3B depict two scenarios, respectively, of a routing scheme for MS-to-MS calls wherein the called MS is roaming in a visited system of an integrated telecommunications network; FIGS . 4A - 4D depict a flow chart of a call routing method for MS-to-MS calls wherein the called MS is roaming;
FIGS. 5 A and 5B depict two scenarios, respectively, of a routing scheme for PSTN-to-MS calls in an integrated telecommunications network;
FIGS. 6A - 6C depict a flow chart of a call routing method for PSTN-to-MS calls in an integrated telecommunications network;
FIGS. 7A and 7B depict two scenarios, respectively, of a routing scheme for MS-to-PSTN calls in an integrated telecommunications network; and
FIGS. 8A - 8C depict a flow chart of a call routing method for MS-to-PSTN calls in an integrated telecommunications network.
DETAILED DESCRIPTION OF EMBODIMENTS
En the drawings, like or similar elements are designated with identical reference numerals throughout the several views, and the various elements depicted are not necessarily drawn to scale. Referring now to FIG. 1 A, depicted therein is a functional block diagram of an integrated telecommunications network 10 provided in accordance with the teachings ofthe present invention. It should be appreciated that the integrated telecommunications network 10 is provided herein in order to exemplify the network-level infrastructure used in the various call routing scenarios described in greater detail hereinbelow.
The integrated telecommunications network 10 comprises a PSN portion 14 such as, for example, an H.323-based Voice-over-EP (VoEP) portion, that is coupled to a plurality CSN portions including, for example, one or more wireless telephony network portions (e.g., WL-CSN portions 12A and 12B) and a PSTN portion 50.
It should be readily apparent that the wireless CSN portions ofthe integrated telecommunications network 10 may be realized in any known radio telephony technology, for example, a Time Division Multiple Access (TDMA), et cetera. The
WL-CSN portion 12A is shown in greater detail. A Home Location Register (HLR) 16 is provided for maintaining a subscriber profile or record associated with a mobile subscriber / mobile station (MS) 28. A Radio Base Station (RBS) 26 is included as part of the cellular infrastructure that comprises the WL-CSN portion 12A, in order to provide radio access services to the MS 28. A serving system 20, comprising a
Visitor Location Register (VLR) 22 and a Mobile Switching Center (MSC) 24, is also included as a switching node therewith.
In accordance with the teachings ofthe present invention, an IP-Interworking Unit (EWU) is provided as a hardware/firmware platform for interfacing and interworking between the switching node (i.e., the MSC/VLR combination in this exemplary embodiment) of the WL-CSN portion 12A and the PSN portion 14. Preferably, the EP-IWU 30A is provided as an EP interface to the MSC 24, and includes appropriate media gateway (MGW) functionality for carrying voice traffic (i.e., payload) over the EP -based PSN portion 14. In addition, a Location Server (LS) 18 is provided as an entity within the WL-
CSN portion 12A that operates as a query-able database containing, preferably, mappings between CSN-based routable numbers (e.g., a called party's number (i.e., the B-number) or a Temporary Location Directory Number or TLDN) and an IP- network address of a signaling endpoint (e.g., an MSC having the EP-IWU interface)). Preferably, the switching node (e.g., the MSC/VLR combination 24/22 or the MSC 24 separately) includes a hardware/software/firmware-based LS-query function 25 that facilitates interrogation by the MSC of the LS 18. Further, the LS is preferably configured in such a way that it returns a unique EP -network address of a "destination MSC" which, in some instances, may be an MSC that serves a called MS. On the other hand, if the MSC associated with the called MS does not have an IP interface (i.e., not IP-addressable), the LS is configured so as to return the EP address of an MSC that is located closest thereto. With respect to PSTN calls, the destination MSC is the terminating EP signaling point connected to a Local Exchange (LE) disposed in the PSTN 50.
Based on the foregoing, it should be readily appreciated that the provision of a database as set forth above in conjunction with a query function provided in an IP- capable MSC facilitates efficient call routing over an P network without having to utilize the H.323 protocol, etc.
Set forth below in greater detail are a plurality of exemplary call routing scenarios for routing calls in an integrated telecommunications network such as the network described hereinabove. More specifically, the following scenarios are provided:
(A) MS-to-MS call routing where the called MS is in its home system;
(B) MS-to-MS call routing where the called MS is roaming;
(C) PSTN-to-MS call routing; and (D) MS-to-PSTN call routing.
Furthermore, each ofthe scenarios is provided in two exemplary embodiments, depending on certain conditions as will be described hereinbelow.
In the ensuing portions of the Detailed Description, various arrangements of an integrated telecommunications network are presented that are appropriate for the different call routing schemes, in addition to the necessary message flows wherein signaling message paths are shown in broken lines and payload-bearing paths are depicted using solid lines.
(A) MS-TO-MS CALL ROUTING WHERE THE CALLED MS is IN ITS HOME SYSTEM First, the network arrangements for two exemplary embodiments are described. The MS-to-MS call routing method is then explained in greater detail.
Referring now to FIG. IB, depicted therein is an integrated telecommunications network 100 for effectuating a routing scheme for an MS-to-MS call in accordance with the teachings of the present invention. Three geographic regions, region 1 102 A, region2 102B and region3 102C, form a coverage area of the network 100. Region3 102C is not involved in the call routing scenario contemplated herein and accordingly, will not be described in this section.
A call-originating party, MSI 108A, is located in region 1 102 A, and is served byMSCl/VLRl 104A. AnRBSl 106A provides radio access services to MSI 108A.
A call- terminating party, MS2 108B, is located in region2 (home area for MS2 in this exemplary scenario), and is served by MSC2/VLR2 104B. Also, an RBS2 106B is included for providing radio access to MS2 108B.
MSC1 and MSC2 are provided with a suitable EP-IWU as described above. Also, a Location Server (LS 112) is provided within the network 100. Because
MSCl/VLRl and MSC2/VLR2 are located in two different geographic areas, the MS1-MS2 call is a long distance call. For illustrative purposes, MSC2 is treated as both the home gateway MSC and serving MSC of MS2. A signaling path 114 is provided between MSC1 and LS 112. Also, another signaling path 116 is provided between MSC1 and MSC2. An EP trunk path 118 is established therebetween for routing the voice payload associated with the call.
FIG. 1C depicts the network 100 in a form that is essentially identical to the network arrangement described above, except that the called party, that is MS2 108B, is served by an MSC (MSC3/VLR3 104) that has no direct EP-EWU interface. MSC2 operates as the destination MSC, the MSC with IP interface that is closest to the serving MSC (i.e., MSC3). Accordingly, an additional signaling path 124 and a circuit-switched trunk such as a Synchronous Transfer Mode (STM) trunk 122 (e.g., Tl or El) are established between the destination MSC and the serving MSC. The STM trunk 122 is used in conjunction with the EP path 118 for transporting the voice payload.
FIGS. 2 A and 2B depict a flow chart that describes a call routing method for the two exemplary network arrangements set forth above. It should be appreciated that the various messages depicted in FIGS. IB and 1C are used in setting forth the steps of the flow chart. Accordingly, FIGS. IB and 1C may again be refened to in connection with the flow chart shown in FIGS. 2 A and 2B. After MSCl receives a call initiation from MSI including MS2's B-number
(step 202), MSCl performs a number analysis on the B-number (step 204) to determine if the call to MS2 is a long distance call (decision block 206). If it is not a long distance call, the call maybe completed using conventional local call termination procedures (step 208). If MSCl determines that the call involves a different region (i.e., a long distance call), it interrogates the Location Server by sending a Service Location Protocol (SLP) message (SERVICEREQ), together with the B-number ofthe called party (step 210) to query the EP address ofthe destination MSC (MSC is IP-capable and its EP address is provided in the LS's database), which can also be the serving MSC (as illustrated in FIG. IB). The destination MSC is used as a transit MSC (as illustrated in FIG. 1C) in the case where serving MSC (MSC3 in this case) is not IP- capable. The Location Server, in response, returns the EP address of MSC2, which is provided as the IP-capable MSC, via a servicereq message to MSCl (steps 214 and 224). Depending on whether the serving MSC for the called MS is IP-capable or not, two scenarios emerge.
Where MSC2 is the EP -capable serving MSC for MS2, MSCl sends a Bearer Independent Call Control (BICC) message called Initial Address Message (IAM)+ to MSC2, including the B-number and the EP address of MSCl (step 216). The IAM+ message is essentially a modified N-ISDN User Part (N-ISUP) Z4 message, provided to effectuate the signaling as set forth herein. Upon receiving the IAM+ message, a
BICC message called Address Complete Message (ACM)+ is sent back to MSCl to by MSC2 (step 218). Thereafter, a BICC message called Answer Message (ANMJ+ is sent by MSC2 to MSCl (step 220). Subsequently, the EP trunk 118 is established between MSCl and MSC2 via Real-time Transfer Protocol (RTP) and Session Description Protocol (SDP) to convey the voice payload (step 222) associated with the call. These actions are shown in a consolidated step 222. Where MSC2 is only the IP-capable destination MSC because the serving MSC (MSC3) is not IP-capable, an IAM+ message is also initially sent from MSCl to MSC2, after receiving the result from the LS (step 226). Subsequently, an ISUP IAM message is forwarded by MS C2 to MSC3 (step 228). MSC3 then sends an ACM message to MSC2 as an acknowledgment ofthe IAM message (step 230). Thereafter, upon receiving the ACM message, MSC2 initiates a BICC ACM+ message to MSCl (step 232). The ISUP ΛN message is then sent by MSC3 to MSC2 (step 234), which is forwarded by MSC2 to MSC 1 by sending the BICC ANM+ message (step 236). The STM trunk 122 is thereby established between MSC2 and MSC3. The EP trunk 1 18 is subsequently established between MSC 1 and MSC2 via RTP and SDP to convey the voice payload as shown in the consolidated step 238.
(B) MS-TO-MS CALL ROUTING WHERE THE CALLED MS is ROAMING
FIGS. 3 A and 3B depict the relevant network arrangements for effectuating
MS-to-MS call routing where the called MS is roaming. It is clear that the network arrangements shown herein are similar to those described above. Accordingly, only the salient features of FIGS. 3A and 3B are set forth herein.
The called MS 108B is no longer located in its home area, that is, region2 102B. Rather, it is now located in region3, being served by MSC4 VLR4 104D. An
RBS4 106D is included in the infrastructure ofthe region for providing radio access services to MS2. MSC2 is still provided as the home gateway MSC of MS2. Whereas in FIG. 3 A, each ofthe call-originating MSC (MSCl), home gateway MSC (MSC2), and the serving MSC (MSC4) have EP interfaces, FIG. 3B depicts the scenario where the serving MSC (MSC4) does not have an EP interface and, accordingly, has to connect to a destination MSC (MSC3 in this exemplary embodiment; MSC3 is the IP- capable MSC that is geographically closest to MSC4) via an Enter-Exchange Carrier (IXC) 51 OB that is disposed between region2 and region3. Consequently, the network arrangement in FIG. 3B depicts STM trunks (path 170 and path 172) for the LXC connection. FIG. 3 A, on the other hand, illustrates a direct EP connection 162 between the originating MSC and serving MSC for call routing. FIGS. 4A - 4D depict a flow chart for the call routing scenarios described above. Once again, FIGS. 3A and 3B may be referred to for locating appropriate signaling messages referenced in the flow chart. Further, it should be appreciated that most ofthe steps effectuated in this flow chart are similar to the steps described in the flow chart of FIGS. 2A and 2B. Accordingly, a concise description ofthe call routing method for each ofthe scenarios is set forth below without explicitly referring to the reference numerals ofthe flow chart shown in FIGS. 4A - 4D.
Where the serving MSC (MSC4) is provided with the EP interface, the call routing steps are as follows. After MSC 1 receives a call initiation from MS 1 including MS2's B-number, MSC 1 performs B-number analysis to determine if the call is a long distance call. If so, MSC 1 interrogates LS by sending the SLP SER VICEREQ message including the B-number to query the EP address ofthe destination MSC. Since MSC2 is provided to be the home gateway MSC of MS2, the SLP servicereq message (transmitted back to MSC 1 by LS) includes the EP address ofthe home gateway MSC, i.e., MSC2. A BICC IAM+ message is then sent by MSCl to MSC2, including the B- number and MSCl's EP address.
Upon receiving the IAM+ message, MSC2/VLR2 checks its record and determines that MS2 is not in its home system, i.e., MS2 has roamed out. An ANSI- 41 LOCREQ is transmitted by MSC2 to HLR to query the location ofthe serving MSC that currently serves MS2. Upon receiving the LOCREQ message, HLR verifies the active services and queries the serving MSC4/VLR4 in region3 by transmitting an ANSI-41 ROUTREQ message. The pre-routing call setup is done by MSC4bymeans of paging MS2. The serving MSC4/VLR4 replies with an ANSI-41 routreq message containing the routing number (TLDN). Thereafter, HLR sends the answer message locreq including the TLDN to MSC2.
An SLP SERVICEREQ message including the TLDN of MSC4 is then sent by MSC2 to LS to query the EP address of MSC4. The returned servicereq message from LS contains the EP address of MSC4. Thereafter, a BICC IAM+ message is sent by MSC2 to MSC4. After receiving the IAM+ message, a BICC ACM+ message is sent to MSC2 by MSC4 to acknowledge the IAM+ message. A BICC A CM+ message is then forwarded by MSC2 to MSCl as an acknowledgment. Afterwards, a BICC ANM+ message is sent to MSC2 by MSC4, which is subsequently forwarded to MSC 1 by MSC2. The direct EP trunk between MSC 1 and MSC4 is then established via RTP and SDP to convey the voice payload associated with the call.
Regarding the case where the serving MSC does not have an P address, the call routing process is essentially similar to the above up to the SLP SERVICEREQ message sent by MSC2 to LS to query the IP address of MSC4. Since in this exemplary embodiment none of the MSCs in region3 are provided with a direct EP connection, a destination MSC (i.e., MSC3) is found in region2. Thereafter, an STM trunk is established via the IXC between MSC3 and MSC4, in addition to the EP trunk between MSCl and MSC3, for the purpose of call routing. It should, however, be understood that in other variations ofthe present invention, a destination MSC may be provided within region3, thereby obviating the need for the IXC.
(C) PSTN-TO-MS CALL ROUTING
FIGS. 5 A and 5B depict network arrangements for effectuating two exemplary embodiments of a PSTN-to-MS call routing scheme in accordance with the teachings ofthe present invention. Once again, only the essentials are set forth herein because the components ofthe network arrangements are similar to the components described above.
A PSTN phone 504 served by a Local Exchange (LEI) 508 is provided as the call-originating entity in regionl 102A. MSI 108 A is provided as the call-terminating party and, in this exemplary embodiment, is roaming out of its home system (MSC2/VLR2 104B) provided in region 2. MSC3/VLR3 104C is provided as the serving system for MS 1 in the visited region, region3 102C. An IXC 51 OA is provided between regionl and region2 for establishing an STM trunk (first circuit-switched trunk path involving trunk segments 564 and 568) between LEI and MSC2.
In the scenario exemplified in FIG. 5 A, the serving MSC (MSC3) is provided with an EP interface (i.e., EP-EWU interface). However, in the scenario illustrated in FIG. 5B, the serving MSC (MSC4) is not IP-capable and, therefore, a separate destination MSC (MSC3) is provided in FIG. 5B. Accordingly, another STM trunk (second circuit-switched trunk path 582) is established between MSC3 and MSC4 for the scenario illustrated in FIG. 5B. While the destination MSC (IP-capable MSC that is closest to the serving MSC) is provided within region3 (where the serving MSC is also located), one of ordinary skill should understand that in some other exemplary embodiments ofthe present invention, the destination MSC may be outside the region ofthe serving MSC, thereby necessitating the use of another IXC.
FIGS. 6A - 6C depict a flow chart for a call routing scheme for the network arrangements set forth above. The steps provided in the flow chart are believed to be self-explanatory and, in large part, similar to the steps of the call routing methods already set forth hereinabove. Accordingly, a concise description ofthe flow chart is provided below.
With respect to the case where the serving MSC is provided to be IP-capable, an exemplary embodiment of the PSTN-to-MS call routing scheme is as follows. After LE 1 receives a call initiation from the PSTN phone including MS 1 's B-number, LEI performs a number analysis and routes the call to MSl's home gateway MSC
(MSC2) via IXC by sending an IAM message. After receiving the call, an ANSI-41 LOCREQ message is sent by MSC2 to HLR to query the location ofthe serving MSC. Upon receiving the LOCREQ message, HLR verifies the active services and queries the serving MSC3/VLR3 with an ANSI-41 ROUTREQ message. The pre-routing call setup is done by MSC3 by means of paging MSI .
The serving MSC3 replies with an ANSI-41 routreq message which includes the routing number (i.e., TLDN). Upon receiving the routreq message, HLR sends the locreq message including the TLDN to MSC2. Thereafter, MSC2 sends an SLP SERVICEREQ message containing the TLDN ofthe serving MSC3 to LS in order to query the EP address of MSC3. A servicereq message is sent back to MSC2 from LS with MSC3's EP address. A BICC IAM+ message is then sent by MSC2 to MSC3. In response, a BICC ACM+ message is returned byMSC3 to MSC2 in order to acknowledge the IAM+ message. Upon receiving the ACM+ message, MSC2 sends an ISUP A CM message to LE 1 via IXC to acknowledge the ELWmessage sent by LE 1. Afterwards, a BICC ANM+ message is sent to MSC2 by MSC3. MSC2 then sends an
ISUP ANM message to LEI via IXC. Thereafter, an STM trunk between LEI and MSC2 is established, in addition to an IP trunk between MSC2 and MSC3 via RTP and SDP.
With respect to the scenario where the serving MSC does not have an EP interface, the call routing process is essentially similar up to the servicereq message from LS which now includes the EP address ofthe destination MSC (i.e., MSC3). As can be seen in FIG. 5B, additional ISUP and BICC messaging is done in order to effectuate an STM trunk between MSC3 and MSC4. The call leg between MSC2 and MSC3 is still routed over an EP trunk via RTP and SDP.
(D) MS-TO-PSTN CALL ROUTING
FIGS. 7A and 7B depict two network arrangements for effectuating MS-to- PSTN call routing. In FIG. 7A, an EP-capable MSC (MSC3) 104C within region3 is used as a destination MSC to route the call via the EP network to the called PSTN phone 586 (served by LE3 584). In FIG. 7B, since there are no EP-capable MSCs in region3, MSC2 in region 2 (which is the closest EP-capable MSC to LE3) is used as a destination MSC to route the call via the EP network to the called PSTN phone 586. FIGS. 8A - 8C depict a flow chart for an exemplary embodiment ofthe MS-to- PSTN call routing scheme for the network arrangements set forth above. Again, only a concise account thereof is set forth below.
After MSCl receives a call initiation from MSI together with the PSTN phone's B-number, MSC 1 performs a number analysis to determine if the call is a long distance call. If so, MSC 1 interrogates LS by sending an SLP SER VICEREQ message including the B-number to query the EP address ofthe destination MSC if the call is EP-routable. Since the B-number is a PSTN number and LE has no direct EP connection, a servicereq message including the EP address of MSC 3 (closest MSC with EP capability in region3 with respect to LE3) is sent back to MSCl from LS. A BICC IAM+ message is then sent by MSC 1 to MSC3, including the B-number and the EP address of MSC 1. Upon receiving the IAM+ message, MSC3/VLR3 sends an LAM message to LE3. An ACM message is sent back by LE3 to MSC3 as an acknowledgment to the J4 message. After receiving the A CM message, MSC3 sends a BICC ACM+ message to acknowledge the IAM+ message. An ISUP viN message is sent thereafter by LE3 to MSC3. Once MSC3 receives the ANM message, it sends a BICC ANM+ message to MSCl . Subsequently, an EP trunk is established between MSC 1 and MSC3 via RTP and SDP, and a circuit- switched STM trunk (first circuit- switched trunk) is established between MSC3 and LE3 for carrying the voice payload.
Where there are no EP-capable MSCs in region3 (as illustrated in FIG.7B), the SLP servicereq message from LS contains the EP address of MSC2, which is the geographically closest MSC to LE3. A BICC IAM+ message is then sent by MSCl to MSC2 together with the PSTN phone's B-number and the EP address of MSCl . After additional ISUP and BICC messaging as shown in FIG. 7B, an STP trunk
(second circuit-switched trunk) is established between MSC2 and LE3 via the IXC, in addition to the EP trunk between MSCl and MSC2, for the purpose of call routing.
Based upon the foregoing, it should be appreciated by those of ordinary skill in the art that the present solution advantageously provides an EP -based call routing scheme for use with an integrated telecommunications network having a PSN portion that is coupled to one or more CSN portions (wireless, wireline, or both). It should be apparent that the present invention efficiently utilizes the EP "backbone" for routing long distance calls by providing a cellular infrastructure entity (i.e., a Location Server) that includes a query-able database containing mapping data between routable numbers and EP addresses of entities provided with an EWU interface. It should further be appreciated that the EP call routing provided herein does not involve the H.323 protocol. Also, because the Location Server is provided to be a cellular component that can interface with EP-capable MSCs, current cellular infrastructures may be leveraged to a greater extent in integrated telecommunications networks as the components can be retrofitted with appropriate EP interfaces etc.
Further, it is believed that the operation and construction of the present invention will be apparent from the foregoing Detailed Description. While the method and system shown and described have been characterized as being preferred, it should be readily understood that various changes and modifications could be made therein without departing from the scope ofthe present invention as set forth in the following claims.

Claims

WHAT IS CLAIMED IS:
1. A call routing method for routing a call originated by a PSTN phone to a mobile station (MS) disposed in an integrated telecommunications network having a packet-switched network (PSN) portion and a wireless circuit-switched network
(CSN) portion including a Location Server (LS) containing mapping information between routing number information and Internet Protocol (EP) address information, the method comprising the steps of: receiving, in a Local Exchange (LE) disposed in a PSTN portion, a call initiation message from the PSTN phone, the call initiation message including the
MS 's number; performing a number analysis on the MS's number by the LE; routing the call by the LE to a home gateway Mobile Switching Center (MSC) ofthe MS via an Inter-Exchange Carrier (IXC); determining, in the home gateway MSC, if the MS is located in a visited area, wherein the home gateway MSC includes an Internet Protocol (EP) interface towards the PSN portion and a querying means to query the LS; if so, querying, by the home gateway MSC, a Home Location Register (HLR), for location information of a serving MSC that currently serves the MS in the visited area; responsive to the querying step by the home gateway MSC, interrogating the serving MSC by the HLR for a routing number with respect to the call originated by the PSTN phone; responsive to the interrogating step by the HLR, returning the routing number by the serving MSC to the HLR; forwarding the routing number to the home gateway MSC by the HLR; thereafter, querying, by the home gateway MSC, the LS for a routable Internet Protocol (EP) address; determining, in the LS, if an EP address ofthe serving MSC exists based on the routing number; if so, returning the EP address ofthe serving MSC to the home gateway MSC by the LS; based on the EP address of the serving MSC received from the LS, establishing an EP trunk between the home gateway MSC and the serving MSC; routing the call originated by the PSTN phone to the serving MSC using a first circuit-switched path between the LE and the home gateway MSC via the
IXC, in conjunction with the EP trunk between the home gateway MSC and the serving MSC, the EP trunk forming at least a segment ofthe PSN portion; if the determining step in the LS determines that the serving MSC does not have an EP address based on the routing number, ascertaining an EP address of a destination MSC which includes an EP interface towards the PSN portion and is located closest to the serving MSC; thereafter, forwarding the EP address of the destination MSC to the home gateway MSC; based on the EP address ofthe destination MSC received from the LS, establishing an EP trunk between the home gateway MSC and the destination MSC; and routing the call originated by the PSTN phone to the serving MSC using the first circuit-switched path between the LE and the home gateway MSC via the EXC, in conjunction with the P trunk between the home gateway MSC and the destination MSC, the EP trunk forming at least a segment ofthe PSN portion, and a second circuit-switched path between the destination MSC and the serving MSC.
2. The call routing method as set forth in claim 1, wherein the step of querying the HLR by the home gateway MSC is effectuated by sending an ANSI-41 LOCREQ message from home gateway MSC to the HLR.
3. The call routing method as set forth in claim 2, wherein the step of interrogating the serving MSC by the HLR is effectuated by sending an ANSI-41 ROUTREQ message from the HLR to the serving MSC.
The call routing method as set forth in claim 3, further comprising the step of paging the MS by the serving MSC for a pre-routing call setup.
5. The call routing method as set forth in claim 3, wherein the step of querying the LS by the home gateway MSC is effectuated by sending a Service Location Protocol (SLP) SERVICEREQ message from the home gateway MSC to the
LS.
6. The call routing method as set forth in claim 3, wherein the step of establishing an EP trunk between the home gateway MSC and the destination MSC and the step of establishing EP trunk between the home gateway MSC and the serving MSC are effectuated by sending a plurality of Bearer Independent Call Control (BICC) messages and a plurality of Integrated Services Digital Network (ISDN) User Part (ISUP) messages among at least a subset ofthe following nodes: the LE, the IXC, the home gateway MSC, the serving MSC and the destination MSC.
7. The call routing method as set forth in claim 6, wherein the
EP trunk between the home gateway MSC and the destination MSC and the EP trunk between the home gateway MSC and the serving MSC are implemented using Realtime Transfer Protocol (RTP) and Session Description Protocol (SDP) to convey a voice payload associated with the call.
8. The call routing method as set forth in claim 6, wherein the each ofthe first and second circuit-switched paths comprises a Synchronous Transfer Mode (STM) trunk.
9. A call routing method for routing a call originated by a mobile station (MS) to a PSTN phone disposed in an integrated telecommunications network having a packet-switched network (PSN) portion and a wireless circuit-switched network (CSN) portion including a Location Server (LS) containing mapping information between called party numbers and Internet Protocol (EP) addresses, the method comprising the steps of: receiving, in a Mobile Switching Center (MSC) serving the MS, a call initiation message from the MS, the call initiation message including the PSTN phone' s number, wherein the MSC includes an Internet Protocol (EP) interface towards the PSN portion and a querying means to query the LS; performing a number analysis on the PSTN phone's number by the
MSC to determine if the call is a long distance call; if so, interrogating the LS by the MSC to obtain an EP address of a destination MSC which includes an EP interface towards the PSN portion and is located closest to a Location Exchange (LE) that serves the PSTN phone; responsive to the interrogating step, receiving the EP address of the destination MSC by the MSC serving the MS; based on the EP address ofthe destination MSC received from the LS, establishing an EP trunk between the MS's MSC and the destination MSC; if the destination MSC and the LE are located in a single coverage area, routing the call originated by the MS to the LE using the EP trunk between the MS ' s
MSC and the destination MSC, in conjunction with a first circuit-switched path between the LE and the destination MSC; and otherwise, routing the call using the EP trunk between the MS's MSC and the destination MSC, in conjunction with a second circuit-switched path between the LE and the destination MSC via an Inter-Exchange Carrier (EXC).
10. The call routing method as set forth in claim 9, wherein the step of interrogating the LS by the MSC serving the MS is effectuated by sending a Service Location Protocol (SLP) SERVICEREQ message from the MSC to the LS.
11. The call routing method as set forth in claim 10, wherein the step of establishing an EP trunk between the MSC and the destination MSC is effectuated by sending a plurality of Bearer Independent Call Control (BICC) messages and a plurality of Integrated Services Digital Network (ISDN) User Part (ISUP) messages among at least a subset ofthe following nodes: the LE, the IXC, the MSC serving the
MS, and the destination MSC.
12. The call routing method as set forth in claim 11, wherein the
EP trunk between the MSC serving the MS and the destination MSC is implemented using Real-time Transfer Protocol (RTP) and Session Description Protocol (SDP) to convey a voice payload associated with the call.
13. The call routing method as set forth in claim 12, wherein the each ofthe first and second circuit-switched paths comprises a Synchronous Transfer Mode (STM) trunk.
14. A call routing method for routing a call originated by a first mobile station (MS) and terminating at a second MS located in its home area, each ofthe MSs disposed in an integrated telecommunications network which includes a packet- switched network (PSN) and a circuit-switched network (CSN) portion including a Location Server (LS) containing mapping information between called party numbers and Internet Protocol (EP) addresses, the method comprising the steps of: receiving, in a Mobile Switching Center (MSC) serving the first MS, a call initiation message from the first MS, the call initiation message including the second MS's number, wherein the first MS's MSC includes an Internet Protocol (EP) interface towards the PSN portion and a querying means to query the LS; performing a number analysis on the second MS's number by the MSC serving the first MS to determine if the call is a long distance call; if so, interrogating the LS by the first MS's MSC to obtain an EP address of a serving MSC that serves the second MS in its home area, the intenogating step including sending the second MS's number from the first MS's MSC to the LS;
determining, in the LS, if the EP address of the serving MSC exists based on the second MS's number; if so, returning the P address of the serving MSC to the first MS's MSC by the LS; based on the EP address of the serving MSC received from the LS, establishing an EP trunk between the first MS's MSC and the serving MSC; routing the call originated by the first MS to the serving MSC using the EP trunk between the first MS's MSC and the serving MSC, the EP trunk forming at least a segment ofthe PSN portion; if the determining step in the LS determines that the serving MSC does not have an EP address based on the second MS's number, ascertaining an EP address of a destination MSC which includes an EP interface towards the PSN portion and is located closest to the serving MSC; thereafter, forwarding the EP address of the destination MSC to the MSC serving the first MS; based on the EP address ofthe destination MSC received from the LS, establishing an EP trunk between the first MS's MSC and the destination MSC; and routing the call originated by the first MS to the serving MSC using the EP trunk between the first MS's MSC and the destination MSC, the EP trunk forming at least a segment of the PSN portion, and a circuit-switched path between the destination MSC and the serving MSC.
15. The call routing method as set forth in claim 14, wherein the step of interrogating the LS by the MSC serving the first MS is effectuated by sending a Service Location Protocol (SLP) SERVICEREQ message from the first MS's MSC to the LS which includes the second MS's number.
16. The call routing method as set forth in claim 15, wherein the step of establishing an EP trunk between the MSC serving the first MS and the destination MSC and the step of establishing an EP trunk between the first MS's MSC and the serving MSC are effectuated by sending a plurality of Bearer Independent Call Control
(BICC) messages and a plurality of Integrated Services Digital Network (ISDN) User Part (ISUP) messages among at least a subset ofthe following nodes: the MSC serving the first MSC, the serving MSC serving the second MS, and the destination MSC.
17. The call routing method as set forth in claim 16, wherein the
EP trunk between the first MS's MSC and the destination MSC and the EP trunk between the first MS's MSC and the second MS's serving MSC are implemented using Real-time Transfer Protocol (RTP) and Session Description Protocol (SDP) to convey a voice payload associated with the call.
18. The call routing method as set forth in claim 16, wherein the circuit- switched path between the destination MSC and the serving MSC comprises a Synchronous Transfer Mode (STM) trunk.
19. A call routing method for routing a call originated by a first mobile station (MS) and terminating at a second MS located outside its home area, each ofthe
MSs disposed in an integrated telecommunications network which includes a packet- switched network (PSN) and a circuit-switched network (CSN) portion including a Location Server (LS) containing mapping information between routing numbers, called party numbers and Internet Protocol (EP) addresses, the method comprising the steps of: receiving, in a Mobile Switching Center (MSC) serving the first MS, a call initiation message from the first MS, the call initiation message including the second MS's number, wherein the first MS's MSC includes an Internet Protocol (EP) interface towards the PSN portion and a querying means to query the LS; performing a number analysis on the second MS ' s number by the MS C serving the first MS to determine if the call is a long distance call; if so, interrogating the LS by the first MS's MSC to obtain an EP address of a home gateway MSC that serves the second MS in its home area, the interrogating step including sending the second MS's number from the first MS's MSC to the LS; determining, in the LS, the EP address ofthe home gateway MSC based on the second MS's number; returning, by the LS, the EP address ofthe home gateway MSC to the MSC serving the first MS; thereafter, sending the second MS's number and the EP address ofthe first MS's MSC from the first MS's MSC to the home gateway MSC; responsive to the second MS's number received from the first MS's MSC, determining by the home gateway MSC that the second MS is located in a visited area; querying, by the home gateway MSC, a Home Location Register (HLR) ofthe second MS to obtain the second MS's location; responsive to the querying step by the home gateway MSC, interrogating by the HLR a serving MSC that serves the second MS in the visited area; responsive to the interrogating step by the HLR, returning a routing number by the serving MSC to the HLR; forwarding the routing number to the home gateway MSC by the HLR; thereafter, interrogating the LS by the home gateway MSC to obtain an EP address of the serving MSC that serves the second MS in the visited area, the interrogating step including sending the routing number received from the HLR; determining, in the LS, if the EP address of the serving MSC exists based on the routing number; if so, returning the EP address ofthe serving MSC to the home gateway MSC by the LS; forwarding the EP address ofthe serving MSC from the home gateway MSC to the MSC serving the first MS; based on the EP address of the serving MSC received from the home gateway MSC, establishing an EP trunk between the MSC serving the first MS and the serving MSC which serves the second MS in the visited area; routing the call originated by the first MS to the serving MSC using the EP trunk between the first MS's MSC and the serving MSC, the EP trunk forming at least a segment ofthe PSN portion; if the determining step in the LS determines that the serving MSC does not have an EP address based on the routing number, ascertaining an IP address of a destination MSC which includes an EP interface towards the PSN portion and is located closest to the serving MSC; thereafter, returning the EP address ofthe destination MSC to the home gateway MSC by the LS; forwarding the EP address of the destination MSC from the home gateway MSC to the MSC serving the first MS; based on the EP address ofthe destination MSC received from the home gateway MSC, establishing an EP trunk between the MSC serving the first MS and the destination MSC; and routing the call originated by the first MS to the serving MSC using the EP trunk between the first MS's MSC and the destination MSC, the EP trunk forming at least a segment of the PSN portion, and a circuit-switched path between the destination MSC and the serving MSC.
20. The call routing method as set forth in claim 19, wherein the step of interrogating the LS by the first MS's MSC is effectuated by sending a Service Location Protocol (SLP) SERVICEREQ message from the first MS's MSC to the LS which includes the second MS's number.
21. The call routing method as set forth in claim 20, wherein the step of interrogating the LS by the home gateway MSC is effectuated by sending a Service Location Protocol (SLP) SERVICEREQ message from the home gateway MSC to the LS which includes the routing number ofthe serving MSC received from the HLR.
22. The call routing method as set forth in claim 21, wherein the step of establishing an EP trunk between the first MS's MSC and the destination MSC and the step of establishing an EP trunk between the first MS's MSC and the serving MSC are effectuated by sending a plurality of Bearer Independent Call Control (BICC) messages and a plurality of Integrated Services Digital Network (ISDN) User Part
(ISUP) messages among at least a subset ofthe following nodes: the first MS's MSC, the home gateway MSC for the second MS, the serving MSC that serves the second MS in the visited area, and the destination MSC.
23. The call routing method as set forth in claim 22, wherein the
EP trunk between the first MS's MSC and the destination MSC and the EP trunk between the first MS's MSC and the serving MSC are implemented using Real-time Transfer Protocol (RTP) and Session Description Protocol (SDP) to convey a voice payload associated with the call.
24. The call routing method as set forth in claim 22, wherein the the circuit-switched path between the destination MSC and the serving MSC comprises a Synchronous Transfer Mode (STM) trunk.
25. The call routing method as set forth in claim 24, wherein the the Synchronous Transfer Mode (STM) trunk involves an Inter-Exchange Carrier disposed between the serving and destination MSCs.
26. An integrated telecommunications network with a wireless circuit- switched network (CSN) portion and a Voice-over-Internet Protocol (VoEP) network portion, comprising: a Mobile Switching Center (MSC) serving one or more mobile subscribers, the MSC having an Internet Protocol (EP)-Interworking Unit interface towards the VoEP network portion; a Location Server (LS) containing mapping information between routing numbers, called party numbers and EP addresses of entities to which a call can be routed over an EP trunk from the MSC; and querying means in the MSC for interrogating the LS based upon at least one of a routing number and a called party number provided to the MSC, in order to obtain an EP address from the LS for effectuating the EP trunk from the MSC based on the EP address such that a call involving a mobile subscriber that is served by the MSC is routed at least in part over the EP trunk.
27. The integrated telecommunications network as set forth in claim 26, wherein the querying means operates by sending a Service Location Protocol (SLP) SERVICEREQ message from the MSC to the LS.
28. The integrated telecommunications network as set forth in claim 26, wherein the EP trunk is implemented using Real-time Transfer Protocol (RTP) and Session Description Protocol (SDP) to convey a voice payload associated with the call.
29. The integrated telecommunications network as set forth in claim 26, further includes a PSTN wherein the call is originated by a PSTN phone served by a Local Exchange disposed in the PSTN.
30. The integrated telecommunications network as set forth in claim 26, further includes a PSTN wherein the call is terminated to a PSTN phone served by a
Local Exchange disposed in the PSTN.
PCT/SE2000/001656 1999-09-21 2000-08-29 System and method for call routing in an integrated telecommunications network having a packet-switched network portion and a circuit-switched network portion WO2001022766A1 (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
AU75650/00A AU7565000A (en) 1999-09-21 2000-08-28 System and method for call routing in an integrated telecommunications network having a packet-switched network portion and a circuit-switched network portion
EP00964825A EP1214858A1 (en) 1999-09-21 2000-08-29 System and method for call routing in an integrated telecommunications network having a packet-switched network portion and a circuit-switched network portion
CA002385478A CA2385478A1 (en) 1999-09-21 2000-08-29 System and method for call routing in an integrated telecommunications network having a packet-switched network portion and a circuit-switched network portion

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US39991899A 1999-09-21 1999-09-21
US09/399,918 1999-09-21

Publications (1)

Publication Number Publication Date
WO2001022766A1 true WO2001022766A1 (en) 2001-03-29

Family

ID=23581484

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2000/001656 WO2001022766A1 (en) 1999-09-21 2000-08-29 System and method for call routing in an integrated telecommunications network having a packet-switched network portion and a circuit-switched network portion

Country Status (5)

Country Link
EP (1) EP1214858A1 (en)
AR (1) AR025642A1 (en)
AU (1) AU7565000A (en)
CA (1) CA2385478A1 (en)
WO (1) WO2001022766A1 (en)

Cited By (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2003036412A2 (en) * 2001-10-24 2003-05-01 Serebrennikov Oleg Aleksandrov Method and system for getting on-line status, authentication, verification, authorization, communication and transaction services for web-enabled hardware and software, based on uniform telephone address related applications
WO2006049421A1 (en) * 2004-11-02 2006-05-11 Samsung Electronics Co., Ltd. Network interworking system and method for providing seamless voice service and short message service between wireless communication networks, and packet switch apparatus therefor
WO2006052083A1 (en) * 2004-11-09 2006-05-18 Samsung Electronics Co., Ltd. Network interworking system and method for providing seamless voice service and short message service between wireless communication networks
WO2006067269A1 (en) * 2004-12-23 2006-06-29 Nokia Corporation Method for the routing of communications to a voice over internet protocol terminal in a mobile communication system
WO2007087898A1 (en) * 2006-02-01 2007-08-09 Telefonaktiebolaget Lm Ericsson (Publ) Routing media streams from packet switched network to circuit switched network
US7289463B2 (en) 2002-04-30 2007-10-30 Alcatel Lucent Hierarchical wireless network and an associated method for delivering IP packets to mobile stations
US7339928B2 (en) 2001-08-29 2008-03-04 Alcatel Lucent Micro-mobility network routing system and method
CN100452917C (en) * 2004-06-08 2009-01-14 华为技术有限公司 Mobile Terminal login system and method thereof
WO2009067880A1 (en) * 2007-11-12 2009-06-04 Huawei Technologies Co., Ltd. Method, system for the mobility management of a terminal and apparatus thereof
US7966423B2 (en) 2003-01-20 2011-06-21 Mitel Networks Corporation Internet appliance proxy protocol to support location-based services
US8086238B1 (en) 2011-06-15 2011-12-27 Metropcs Wireless, Inc. HLR-dual circuit switched and packet switched registration support
CN103546936A (en) * 2013-10-14 2014-01-29 南京邮电大学 Method for searching specific user group and specific service number based on WiMAX (worldwide interoperability for microwave access) local routing technology

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5781547A (en) * 1996-02-29 1998-07-14 Motorola, Inc. Router and method for use in a communication system
JPH10303990A (en) * 1997-04-16 1998-11-13 Lucent Technol Inc Method for establishing audio connection and distributed database
WO1999005590A2 (en) * 1997-07-25 1999-02-04 Starvox, Inc. Apparatus and method for integrated voice gateway
WO1999033250A1 (en) * 1997-12-23 1999-07-01 Telefonaktiebolaget Lm Ericsson (Publ) Internet protocol telephony for a mobile station on a packet data channel

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5781547A (en) * 1996-02-29 1998-07-14 Motorola, Inc. Router and method for use in a communication system
JPH10303990A (en) * 1997-04-16 1998-11-13 Lucent Technol Inc Method for establishing audio connection and distributed database
WO1999005590A2 (en) * 1997-07-25 1999-02-04 Starvox, Inc. Apparatus and method for integrated voice gateway
WO1999033250A1 (en) * 1997-12-23 1999-07-01 Telefonaktiebolaget Lm Ericsson (Publ) Internet protocol telephony for a mobile station on a packet data channel

Cited By (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7339928B2 (en) 2001-08-29 2008-03-04 Alcatel Lucent Micro-mobility network routing system and method
WO2003036412A3 (en) * 2001-10-24 2003-07-17 Oleg Aleksandrov Serebrennikov Method and system for getting on-line status, authentication, verification, authorization, communication and transaction services for web-enabled hardware and software, based on uniform telephone address related applications
WO2003036412A2 (en) * 2001-10-24 2003-05-01 Serebrennikov Oleg Aleksandrov Method and system for getting on-line status, authentication, verification, authorization, communication and transaction services for web-enabled hardware and software, based on uniform telephone address related applications
US7289463B2 (en) 2002-04-30 2007-10-30 Alcatel Lucent Hierarchical wireless network and an associated method for delivering IP packets to mobile stations
US7966423B2 (en) 2003-01-20 2011-06-21 Mitel Networks Corporation Internet appliance proxy protocol to support location-based services
CN100452917C (en) * 2004-06-08 2009-01-14 华为技术有限公司 Mobile Terminal login system and method thereof
WO2006049421A1 (en) * 2004-11-02 2006-05-11 Samsung Electronics Co., Ltd. Network interworking system and method for providing seamless voice service and short message service between wireless communication networks, and packet switch apparatus therefor
WO2006052083A1 (en) * 2004-11-09 2006-05-18 Samsung Electronics Co., Ltd. Network interworking system and method for providing seamless voice service and short message service between wireless communication networks
WO2006067269A1 (en) * 2004-12-23 2006-06-29 Nokia Corporation Method for the routing of communications to a voice over internet protocol terminal in a mobile communication system
US7400881B2 (en) 2004-12-23 2008-07-15 Nokia Corporation Method for the routing of communications to a voice over internet protocol terminal in a mobile communication system
CN101069390B (en) * 2004-12-23 2010-12-22 诺基亚公司 Method for the routing of communications to a voice over internet protocol terminal in a mobile communication system
WO2007087898A1 (en) * 2006-02-01 2007-08-09 Telefonaktiebolaget Lm Ericsson (Publ) Routing media streams from packet switched network to circuit switched network
WO2009067880A1 (en) * 2007-11-12 2009-06-04 Huawei Technologies Co., Ltd. Method, system for the mobility management of a terminal and apparatus thereof
US8086238B1 (en) 2011-06-15 2011-12-27 Metropcs Wireless, Inc. HLR-dual circuit switched and packet switched registration support
CN103546936A (en) * 2013-10-14 2014-01-29 南京邮电大学 Method for searching specific user group and specific service number based on WiMAX (worldwide interoperability for microwave access) local routing technology
CN103546936B (en) * 2013-10-14 2017-02-22 南京邮电大学 Method for searching specific user group and specific service number based on WiMAX (worldwide interoperability for microwave access) local routing technology

Also Published As

Publication number Publication date
CA2385478A1 (en) 2001-03-29
AU7565000A (en) 2001-04-24
AR025642A1 (en) 2002-12-04
EP1214858A1 (en) 2002-06-19

Similar Documents

Publication Publication Date Title
US6795444B1 (en) System and method for providing wireless telephony over a packet-switched network
CA2375995C (en) Mobility within a packet-switched telephony network
US6611516B1 (en) Short message service support over a packet-switched telephony network
JP4076775B2 (en) Multiple protocol home location register
JP4606686B2 (en) Multiple protocol home location register
US7450565B2 (en) Conversational bearer negotiation
US6490451B1 (en) System and method for providing packet-switched telephony
US7400881B2 (en) Method for the routing of communications to a voice over internet protocol terminal in a mobile communication system
US20060079236A1 (en) Pseudo number portability in fixed-mobile convergence with one number
WO2000079825A1 (en) Gateway, system and method for supporting roaming
US6751204B1 (en) Call routing method for 3G.IP networks
EP1849286B1 (en) Method and apparatuses for routing or redirecting video traffic in communications system
KR20040106237A (en) Server component redirection of new media path portion between packet-switched and circuit-switched portions of mobile switching center
CA2371555C (en) Virtual numbering plan for inter-operability between heterogeneous networks
WO2001031842A2 (en) System and method for improved resource management in an integrated telecommunications network having a packet-switched network portion and a circuit-switched network portion
US8644833B1 (en) Method and system using a mobility server for handoff of a multi-mode mobile station
WO2001076276A2 (en) Telecommunications network integrating cellular, packet-switched, and voice-over-ip infrastructures
EP1214858A1 (en) System and method for call routing in an integrated telecommunications network having a packet-switched network portion and a circuit-switched network portion
JP2003505939A (en) Communications system
AU2011300A (en) System and method for mobile terminal registration in an integrated wireless packet-switched network
Liao Mobile internet telephony: Mobile extensions to H. 323
CA2315496A1 (en) Architecture to support service features for wireless calls in a wireless telecommunication system
Yang et al. Wireless VoIP: opportunities and challenges
WO2000079815A1 (en) Mobility in packet-switched telephony networks
Pang et al. GSM‐IP: A VoIP service for mobile networks

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CR CU CZ DE DK DM DZ 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 MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG 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 MZ 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
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
WWE Wipo information: entry into national phase

Ref document number: 2000964825

Country of ref document: EP

Ref document number: 2385478

Country of ref document: CA

WWP Wipo information: published in national office

Ref document number: 2000964825

Country of ref document: EP

WWW Wipo information: withdrawn in national office

Ref document number: 2000964825

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: JP