EP1214858A1 - Systeme et procede d'acheminement d'appels dans un reseau de telecommunications integre ayant une partie de reseau a commutation par paquets et un partie de reseau a commutation de circuit - Google Patents
Systeme et procede d'acheminement d'appels dans un reseau de telecommunications integre ayant une partie de reseau a commutation par paquets et un partie de reseau a commutation de circuitInfo
- Publication number
- EP1214858A1 EP1214858A1 EP00964825A EP00964825A EP1214858A1 EP 1214858 A1 EP1214858 A1 EP 1214858A1 EP 00964825 A EP00964825 A EP 00964825A EP 00964825 A EP00964825 A EP 00964825A EP 1214858 A1 EP1214858 A1 EP 1214858A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- msc
- serving
- call
- trunk
- destination
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Withdrawn
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
- H04W8/08—Mobility data transfer
- H04W8/10—Mobility data transfer between location register and external networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
- H04L61/4588—Network directories; Name-to-address mapping containing mobile subscriber information, e.g. home subscriber server [HSS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W92/00—Interfaces specially adapted for wireless communication networks
- H04W92/02—Inter-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
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Databases & Information Systems (AREA)
- Mobile Radio Communication Systems (AREA)
- Telephonic Communication Services (AREA)
Abstract
L'invention concerne un système et un procédé d'acheminement d'appels par Internet dans un réseau de télécommunications ayant une partie de réseau à commutation par paquets (p. ex. une partie de réseau voix sur IP (VoIP) (14)) et une ou plusieurs parties de réseau par commutation de circuit (CSN) (12), telles que RTPC (50) ou un réseau de radiotéléphonie. Un centre de commutation mobile (CCM (24)) desservant un ou plusieurs abonnés mobiles (28) comprend une interface d'unité d'interfonctionnement IP (30) à la partie de réseau VoIP. Le réseau de radiotéléphonie comporte également un serveur de localisation (LS (18)) contenant des informations de mappage entre des numéros d'acheminement (p. ex. des numéros d'appels de localisation temporaire ou TLDN), des numéros de partie appelée (numéros B) et des adresses IP d'entités auxquelles un appel peut être acheminé sur une ligne IP d'un CCM. Un mécanisme d'interrogation est compris dans le MMC pour interroger le LS sur la base d'un numéro d'acheminement, un numéro de partie appelée ou les deux fournis au MMC. Ce dernier obtient une adresse IP du LS qui est utilisée pour établir la ligne IP. Plusieurs messages de contrôle d'appels indépendant du support (BICC) et plusieurs messages du sous-système utilisateur du réseau numérique à intégration de services (ISDN) sont transmis parmi les différents noeuds du réseau de télécommunications intégré, p. ex. un ou plusieurs CCM ayant l'interface IP, un central du RTPC, entre autres, afin d'établir la ligne IP. Lorsqu'une ligne IP n'est pas disponible, une voie à commutation de circuit (p. ex. une ligne à mode de transfert synchrone (STM)), est utilisée dans la voie d'appel. La ligne IP est implantée au moyen du protocole de transfert en temps réel (RTP) et du protocole de description de session (SDP) afin de transmettre la charge utile vocale associée à l'appel.
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US39991899A | 1999-09-21 | 1999-09-21 | |
US399918 | 1999-09-21 | ||
PCT/SE2000/001656 WO2001022766A1 (fr) | 1999-09-21 | 2000-08-29 | Systeme et procede d'acheminement d'appels dans un reseau de telecommunications integre ayant une partie de reseau a commutation par paquets et un partie de reseau a commutation de circuit |
Publications (1)
Publication Number | Publication Date |
---|---|
EP1214858A1 true EP1214858A1 (fr) | 2002-06-19 |
Family
ID=23581484
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP00964825A Withdrawn EP1214858A1 (fr) | 1999-09-21 | 2000-08-29 | Systeme et procede d'acheminement d'appels dans un reseau de telecommunications integre ayant une partie de reseau a commutation par paquets et un partie de reseau a commutation de circuit |
Country Status (5)
Country | Link |
---|---|
EP (1) | EP1214858A1 (fr) |
AR (1) | AR025642A1 (fr) |
AU (1) | AU7565000A (fr) |
CA (1) | CA2385478A1 (fr) |
WO (1) | WO2001022766A1 (fr) |
Families Citing this family (12)
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 |
US20030078987A1 (en) * | 2001-10-24 | 2003-04-24 | Oleg Serebrennikov | Navigating network communications resources based on telephone-number metadata |
US7289463B2 (en) | 2002-04-30 | 2007-10-30 | Alcatel Lucent | Hierarchical wireless network and an associated method for delivering IP packets to mobile stations |
GB2397402A (en) | 2003-01-20 | 2004-07-21 | Mitel Networks Corp | Internet proxy that supports location-based services |
CN100452917C (zh) * | 2004-06-08 | 2009-01-14 | 华为技术有限公司 | 移动终端上网系统及其方法 |
WO2006049421A1 (fr) * | 2004-11-02 | 2006-05-11 | Samsung Electronics Co., Ltd. | Systeme d'interfonctionnement de reseaux et procede pour fournir un service vocal integre et un service de messages courts entre des reseaux de communication sans fil, et appareil de commutation par paquets associe |
US20060114885A1 (en) * | 2004-11-09 | 2006-06-01 | Samsung Electronics Co., Ltd. | Network interworking system and method for providing seamless voice service and short message service between wireless communication networks |
FI20041659A0 (fi) | 2004-12-23 | 2004-12-23 | Nokia Corp | Menetelmä liikkeen reitittämiseksi VoIP-päätteeseen matkaviestinjärjestelmässä |
WO2007087898A1 (fr) * | 2006-02-01 | 2007-08-09 | Telefonaktiebolaget Lm Ericsson (Publ) | Routage de flux média, d'un réseau à commutation de paquets à un réseau à commutation de circuits |
CN101437219B (zh) * | 2007-11-12 | 2011-04-20 | 华为技术有限公司 | 一种终端的移动性管理方法及设备 |
US8086238B1 (en) | 2011-06-15 | 2011-12-27 | Metropcs Wireless, Inc. | HLR-dual circuit switched and packet switched registration support |
CN103546936B (zh) * | 2013-10-14 | 2017-02-22 | 南京邮电大学 | 基于WiMAX本地路由技术查找特定用户群和特定服务号的方法 |
Family Cites Families (4)
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 |
US6198738B1 (en) * | 1997-04-16 | 2001-03-06 | Lucent Technologies Inc. | Communications between the public switched telephone network and packetized data networks |
EP1021757A1 (fr) * | 1997-07-25 | 2000-07-26 | Starvox, Inc. | Appareil et procede pour passerelle vocale integree |
US6222829B1 (en) * | 1997-12-23 | 2001-04-24 | Telefonaktieblaget L M Ericsson | Internet protocol telephony for a mobile station on a packet data channel |
-
2000
- 2000-08-28 AU AU75650/00A patent/AU7565000A/en not_active Abandoned
- 2000-08-29 EP EP00964825A patent/EP1214858A1/fr not_active Withdrawn
- 2000-08-29 CA CA002385478A patent/CA2385478A1/fr not_active Abandoned
- 2000-08-29 WO PCT/SE2000/001656 patent/WO2001022766A1/fr not_active Application Discontinuation
- 2000-09-12 AR ARP000104786A patent/AR025642A1/es unknown
Non-Patent Citations (1)
Title |
---|
See references of WO0122766A1 * |
Also Published As
Publication number | Publication date |
---|---|
WO2001022766A1 (fr) | 2001-03-29 |
AR025642A1 (es) | 2002-12-04 |
CA2385478A1 (fr) | 2001-03-29 |
AU7565000A (en) | 2001-04-24 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6795444B1 (en) | System and method for providing wireless telephony over a packet-switched network | |
CA2375995C (fr) | Mobilite a l'interieur d'un reseau telephonique commute par paquets | |
US6611516B1 (en) | Short message service support over a packet-switched telephony network | |
JP4076775B2 (ja) | 多重プロトコルホームロケーションレジスタ | |
JP4606686B2 (ja) | 多重プロトコルホームロケーションレジスタ | |
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 (fr) | Passerelle, systeme et procede servant a creer un support d'itinerance | |
US6751204B1 (en) | Call routing method for 3G.IP networks | |
EP1849286B1 (fr) | Procede et appareils d'acheminement ou de reacheminement de trafic video dans un systeme de communication | |
KR20040106237A (ko) | 미디어 경로 재지정 장치 및 방법 | |
KR100496818B1 (ko) | 통신 시스템 | |
WO2001076276A2 (fr) | Reseau de telecommunications integrant des infrastructures cellulaires, de commutation de paquets et de voix sur ip | |
WO2001031842A2 (fr) | Systeme et procede destines a une meilleure gestion des ressources dans un reseau de telecommunications integre possedant une partie a commutation par paquets et une partie a commutation par circuit | |
CA2371555C (fr) | Plan de numerotage virtuel pour une capacite de fonctionnement entre des reseaux heterogenes | |
WO2001022766A1 (fr) | Systeme et procede d'acheminement d'appels dans un reseau de telecommunications integre ayant une partie de reseau a commutation par paquets et un partie de reseau a commutation de circuit | |
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 (fr) | Architecture pour la prise en charge de fonctions de service pour des appels sans fil dans un systeme de telecommunications sans fil | |
US8644833B1 (en) | Method and system using a mobility server for handoff of a multi-mode mobile station | |
Yang et al. | Wireless VoIP: opportunities and challenges | |
WO2000079815A1 (fr) | Mobilite dans des reseaux de telephonie commutes par paquets | |
Pang et al. | GSM‐IP: A VoIP service for mobile networks |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
17P | Request for examination filed |
Effective date: 20020318 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE |
|
AX | Request for extension of the european patent |
Free format text: AL;LT;LV;MK;RO;SI |
|
RIN1 | Information on inventor provided before grant (corrected) |
Inventor name: XIANG, ZENG-JUN |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE APPLICATION HAS BEEN WITHDRAWN |
|
18W | Application withdrawn |
Effective date: 20030407 |
|
RIN1 | Information on inventor provided before grant (corrected) |
Inventor name: XIANG, ZENG-JUN |