[go: up one dir, main page]
More Web Proxy on the site http://driver.im/

EP1135901A2 - Systeme et procede de mise en oeuvre de commutation mobile et de services de lignes collectives dans un reseau a commutation par paquets - Google Patents

Systeme et procede de mise en oeuvre de commutation mobile et de services de lignes collectives dans un reseau a commutation par paquets

Info

Publication number
EP1135901A2
EP1135901A2 EP99963738A EP99963738A EP1135901A2 EP 1135901 A2 EP1135901 A2 EP 1135901A2 EP 99963738 A EP99963738 A EP 99963738A EP 99963738 A EP99963738 A EP 99963738A EP 1135901 A2 EP1135901 A2 EP 1135901A2
Authority
EP
European Patent Office
Prior art keywords
gateway
mcu
terminal
network
mobile subscriber
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
Application number
EP99963738A
Other languages
German (de)
English (en)
Inventor
Hung Tran
Laura Hernandez
Jean-François Bertrand
Bartosz Balazinski
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget LM Ericsson AB filed Critical Telefonaktiebolaget LM Ericsson AB
Publication of EP1135901A2 publication Critical patent/EP1135901A2/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2854—Wide area networks, e.g. public data 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
    • 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/09—Mapping addresses
    • H04L61/10—Mapping addresses of different types
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M7/00—Arrangements for interconnection between switching centres
    • H04M7/006—Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP), including next generation networks with a packet-switched transport layer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M7/00—Arrangements for interconnection between switching centres
    • H04M7/12—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal
    • H04M7/1205—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal where the types of switching equipement comprises PSTN/ISDN equipment and switching equipment of networks other than PSTN/ISDN, e.g. Internet Protocol networks
    • H04M7/1285—Details of finding and selecting a gateway for a particular call
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/06—De-registration or detaching
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2207/00—Type of exchange or network, i.e. telephonic medium, in which the telephonic communication takes place
    • H04M2207/18—Type of exchange or network, i.e. telephonic medium, in which the telephonic communication takes place wireless networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals

Definitions

  • the present invention relates to telecommunication systems and, more particularly, to a system and method for providing mobile switching and multi-party services over a packet-switched network such as, for example, a network using the Internet Protocol (IP).
  • IP Internet Protocol
  • Noice-over-IP networks implement communications infrastructures that are typically based on multiple protocols which include, for example, the well-known H.323 protocol.
  • POCS Plain Old Cellular System
  • GSM Global System for Mobile communications
  • GSM Global System for Mobile communications
  • POCS systems are based on switched physical trunk connections. These mechanisms are not compatible with the packet switching/routing mechanisms such as, e.g., Domain Name System (DNS), Dynamic Host Configuration Protocol (DHCP), etc. required for managing device/host addressing and configuration. Incompatibilities also exist between POCS protocols and communications protocols of the existing VoIP applications.
  • the POCS systems cannot support aPlain Old Telephone System (POTS) or Integrated Services Digital Network (ISDN) client in the Internet context.
  • POTS Packet Old Telephone System
  • ISDN Integrated Services Digital Network
  • the Internet "client” is typically required to handle Internet- based protocols such as, e.g., Real-time Transfer Protocol (RTP), Resource Reservation Protocol (RSNP), etc. which are not in the definition or domain of the POCS systems.
  • RTP Real-time Transfer Protocol
  • RSNP Resource Reservation Protocol
  • the IP entity that facilitates multi-party services such as, e.g., a three-party conference
  • a current protocol e.g., the H.323 standard
  • the current procedures for setting up a three-party conference using the H.323 protocol do not support call enquiry, call waiting, or three-party conferencing as defined by the mobile communications standard ANSI-53 or certain proprietary flash messaging schemes.
  • ANSI-53 or certain proprietary flash messaging schemes it would be of significant benefit to provide a system and method for supporting the ANSI-53 or proprietary flash messaging within the context of an integrated VoIP system.
  • the present invention is directed to an integrated wireless packet- switched network for providing telecommunications services to a mobile subscriber.
  • the network comprises an IP -based network portion for transporting communication traffic relating to the mobile subscriber.
  • a radio network controller is provided for controlling radio access for the mobile subscriber.
  • a gateway is disposed between the packet-switched network (IP-based) portion and the radio network controller. Further, the gateway includes means for switching the communication traffic relating to the mobile subscriber.
  • the interface between the gateway and radio network controller includes a first protocol translator for converting Transaction Capability Application Part (TCAP) messaging into IP messaging and a second protocol translator for converting Integrated Services Digital Network (ISDN) User Part (ISUP) messaging into Primary Rate Interface (PRI) messaging.
  • TCAP Transaction Capability Application Part
  • ISUP Integrated Services Digital Network
  • PRI Primary Rate Interface
  • either or both of the translators may be integrated within the IP gateway.
  • the present invention is directed to a method of registering a mobile terminal in an integrated wireless packet-switched network which includes a cellular network portion and a packet-switched network portion.
  • the cellular network portion comprises a serving radio network controller (RNC) for providing radio access services for the mobile terminal.
  • the packet-switched network portion includes a gatekeeper and a gateway, wherein the gateway comprises an IP stack for switching cellular traffic related to the mobile terminal.
  • the method begins by determining, in the serving RNC, that the mobile terminal is located in a service area associated with the serving RNC. Responsive to the determining step, an Invoke message is sent from the serving RNC to the gateway, wherein a Registration Update signal is encapsulated in the Invoke message.
  • a Registration Request message is then sent from the gateway to the gatekeeper, the Registration Request message including a terminalAlias parameter. Responsive thereto, a Registration Confirm message is sent from the gatekeeper to the gateway if the mobile terminal is successfully registered at the gatekeeper. Otherwise, a Registration Reject message is sent from the gatekeeper to the gateway. Thereafter, responsive to receiving either the Registration Confirm message or the Registration Reject message, a registration status of the mobile terminal is reported via a Return Result message sent by the gateway to the RNC.
  • the present invention is related to a method of de-registering a mobile terminal in an integrated wireless packet-switched network system which includes a cellular network portion and a packet-switched network portion.
  • the cellular and packet-switched network portions include components as set forth above.
  • the method begins by first determining, in the serving RNC, that the mobile terminal located in a service area associated with the serving RNC has powered down. Responsive to the determining step, an Invoke message is sent from the serving RNC to the gateway, wherein a Registration Update signal is encapsulated in the Invoke message. Upon receiving the Invoke message, an Unregistration Request message is sent from the gateway to the gatekeeper, the Unregistration Request message including an endpointAlias parameter.
  • an Unregistration Confirm message is sent from the gatekeeper to the gateway if the mobile terminal is successfully unregistered at the gatekeeper. Otherwise, an Unregistration Reject message is sent from the gatekeeper to the gateway. Subsequently, responsive to receiving one of the Unregistration Confirm and Unregistration Reject messages, a registration status of the mobile terminal is reported via a Return Result message sent from the gateway to the RNC.
  • the present invention is directed to an integrated wireless packet-switched network having a wireless portion and an Internet Protocol (IP) portion.
  • IP Internet Protocol
  • the IP portion preferably includes a gateway for interfacing with the wireless portion.
  • the network system comprises a radio network controller for providing radio access services to a mobile subscriber.
  • the gateway includes means for switching communication traffic relating to the mobile subscriber.
  • the network system further includes one or more protocol translators disposed between the gateway and the radio network controller.
  • the present invention provides an integrated Voice over
  • VoIP IP
  • the VoIP network preferably comprises a radio network controller that provides radio access services to one or more mobile subscribers.
  • a gateway is operably coupled to the radio network controller for combining a packet-switched portion and a circuit-switched cellular portion of the integrated VoIP network.
  • a Multipoint Control Unit (MCU) for setting up multi-party services is connected to the packet-switched portion.
  • a flash proxy agent is disposed between the MCU and the gateway for mapping ANSI-53 or proprietary flash messages relating to the multi-party services into messages compatible with the MCU.
  • the flash proxy agent may be integrated within suitable
  • H.323 components such as, e.g., the MCU or the gateway.
  • FIG. 1 depicts a functional block diagram of a wireless IP (WLIP) network in accordance with the teachings of the present invention
  • FIG .2 depicts a functional block diagram of a portion of the exemplary WLIP network with additional components for providing IP -based switching;
  • FIG. 3 depicts a functional block diagram of an addressing scheme for use in the WLIP network
  • FIGS. 4 A and 4B depict, respectively, control message pathways for registration and de-registration of a mobile station in the WLIP network
  • FIG. 5 depicts a control message pathway for placing a call from a mobile station in the WLIP network
  • FIG. 6 depicts a control message pathway for placing a call to a mobile station in the WLIP network
  • FIG. 7 depicts a control message pathway for an exemplary embodiment of a call waiting scenario in the WLIP network
  • FIG. 8 depicts a control message pathway for an exemplary embodiment of a call enquiry scenario in the WLIP network
  • FIG. 9 depicts a control message pathway for supporting an exemplary embodiment of a multi-party conference in the WLIP network
  • FIG. 10 depicts a functional block diagram of another view of the WLIP network portion for supporting multi-party services using a Multipoint Control Unit (MCU);
  • FIG. 11 depicts a functional block diagram of the WLIP network portion with the MCU for supporting multi-party services using a flash agent provided in accordance with the teachings of the present invention;
  • MCU Multipoint Control Unit
  • FIGS. 12-14 depict control message pathways for additional embodiments of a multi-party conference using the flash agent; and FIGS. 15 and 16 depict control message pathways for additional exemplary embodiments of call waiting scenarios in the WLIP network portion having the flash agent.
  • FIG. 1 depicts a functional block diagram of a WLIP network system 100 for providing H.323-based mobile switching in accordance with the teachings of the present invention.
  • a legacy PSTN/PLMN network portion 102 is connected to a Home Location Register (HLR) 160 via a Signaling System No. 7 (SS7) path 257.
  • An H.323-based VoIP portion 206 comprises an IP network 207 disposed among a plurality of H.323-compliant components such as, for example, a gatekeeper 200, one or more terminals (e.g., terminal 203), one or more PCS (e.g., PC 202), a Multipoint Conference Unit (MCU) 204, et cetera.
  • MCU Multipoint Conference Unit
  • a conventional Mobile Switching Center (MSC) of the POCS network is modified in accordance with the teachings of the present invention to provide only radio services. Accordingly, the switching functionality of the MSC is removed therefrom such that it becomes a Radio Network Controller (RNC), for example, RNC 130 shown in FIG. 1.
  • RNC Radio Network Controller
  • An IP or RNC gateway 250 is provided preferably as an interface between the IP network 207 and the RNC 130.
  • the IP/RNC gateway 250 is an H.323-compliant gateway that is suitably modified to support the communication between the H.323 network and the RNC 130.
  • An SS7/ANSI-41 path 210 is used between the RNC 130 and the IP gateway 250 during call setup.
  • An ISDN User Part (ISUP) signaling path 208 is also provided between the RNC 130 and the IP gateway 250 in order to establish trunk connections for voice transferring during the call.
  • ISUP ISDN User Part
  • the gatekeeper (GK) 200 operates as a mobility server for keeping track of various call clients and servers.
  • the gatekeeper 200 maintains registration and status information with respect to mobile stations (for example, MS 103) and
  • the gatekeeper 200 is provided as an H.323 entity on the IP network 207 (which may comprise a Local Area Network) that provides address translation and controls access to the network for the other H.323 components.
  • the H.323 terminals (e.g., terminal 203) are preferably provided as IP clients that may transfer voice, video, and multimedia data.
  • the MCU 204 is preferably provided for establishing conference calls and multi-party services.
  • a Multipoint Controller may also be provided as part of the
  • VoIP portion 206 VoIP portion 206.
  • a "plain" PSTN gateway 249 may be provided between the VoIP network portion 206 and the legacy PSTN/PLMN network portion
  • the legacy PSTN/PLMN network portion 102 with a connection 253.
  • the legacy PSTN/PLMN network portion 102 with a connection 253.
  • the GK 200 may decide to route a call to the external network
  • the PSTN/PLMN portion 102 via either the IP/RNC GW 250 or the PSTN GW 249, using their respective paths alternatively (i.e., path 255 or path 253 , respectively).
  • the GK may also perform a load balancing or bandwidth control function with respect to such routing to the external network portion.
  • FIG. 2 illustrates a functional diagram of a relevant portion 202 of the exemplary WLIP network system 100 shown in FIG. 1, with additional details provided for the gateway-RNC interface pathway.
  • a first protocol translator (Tl) 304 is preferably provided as an SS7 stack on the path 210 for converting Transaction Capability Application Part (TC AP) messaging into suitable IP messaging.
  • a second protocol translator (T2) 306 is provided on the path 208 for performing the translation between ISUP messaging and Primary Rate Interface (PRI) messaging.
  • TC AP Transaction Capability Application Part
  • T2 Primary Rate Interface
  • cellular entities such as, for example, a Visitor Location Register (VLR), one or more base stations, an Authentication Center (AC), Service Control Points (SCPs), et cetera, may be included within the WLIP network system 100.
  • VLR Visitor Location Register
  • AC Authentication Center
  • SCPs Service Control Points
  • FIG. 3 shown therein is a functional block diagram of an exemplary addressing scheme for use in the WLIP network 100.
  • the address translation between the Location Area (LA) and the RNC is performed only when the IP gateway 250 supports more than one RNC.
  • An RNC e.g., RNC 130, may control one or more base stations (BSs).
  • BS 140A and BS140B are shown in this FIG.
  • LA Translation between Mobile Identification Number (MIN) and LA is preferably performed only when the LA information is to be maintained within an access network instead of the gatekeeper 200.
  • the LA information may be transmitted to the gatekeeper 200 as a terminalAlias parameter in a Registration Request (RRQ) message and may be returned as a destinationlnfo or srclnfo parameter in an Admission Confirm (ACF) message.
  • RRQ Registration Request
  • ACF Admission Confirm
  • the LA information may also be sent as nonStandardData in the RR and ACF messages.
  • a mobile station (MS) may be paged globally.
  • a control message pathway is illustrated therein for registering an MS (e.g., MS 103) disposed in the WLIP network 100.
  • the serving RNC 130 After determining that the MS 103 is located within its serving area, the serving RNC 130 sends an ANSI-41 private message, e.g., H323 Invoke message 602 to the RNC gateway 250.
  • the MSS-MRS RegUpdate signal is encapsulated within the H323 Invoke message 602.
  • the RNC gateway 250 Upon receiving the Invoke message 602, the RNC gateway 250 sends a RAS RRQ message 604 to the gatekeeper 200.
  • the gatekeeper 200 If the MS has previously registered with a gateway within the domain of the JO- gatekeeper 200, the gatekeeper 200 simply returns a RASACF message. Otherwise, it stores the MIN as an alias of the gateway and returns a RAS Registration Confirm (RCF) message 606. If the MS has failed the registration process, a RJS Registration Reject (RRJ) return message (also labeled as message 606) may be sent. Upon receiving either the RJS RCF or RRJ message 606, the JP RNC gateway 250 constructs an ANSI-41 private message, H323 Return Result (RR) response message 616, by wrapping the MSS-MRS RegUpdateR signal and returns it to the RNC 130.
  • RJS Registration Reject also labeled as message 606
  • FIG.4B depicts a control message pathway for de-registering an MS (e.g., MS 103) in the WLIP network 100 provided in accordance with the teachings of the present invention.
  • the RNC 130 sends an ANSI-41 H323 Invoke message 610 (with encapsulated MSS-MRS RegUpdate signal) to the IP/RNC gateway 250 to inform the H.323 IP network 206 that the MS 103 has powered down.
  • the gateway 250 Upon receiving the H323 Invoke message 610, the gateway 250 sends a RJS Unregistration Request (URQ) message 612 to the gatekeeper 200 to remove the MS from its registry.
  • URQ RJS Unregistration Request
  • An endpointAlias parameter is provided within the RJS URQ message 612.
  • the gatekeeper 200 After determining that the registration of the MS can be revoked, the gatekeeper 200 updates its registry appropriately and sends aRJS Unregistration Confirm ( UCF) message 614 to the IP/RNC gateway 250. If the registration of the MS cannot be revoked for some reason, the gatekeeper 200 transmits &RAS Unregistration Reject (URJ) message (also denoted as message 614) to the gateway. Thereafter, responsive to the UCF or URJ message 614, the IP/RNC gateway 250 sends an ANSI-41 H323 RR response message 616 to the RNC 130, including the encapsulated RegUpdateR signal therein.
  • UCF &RAS Unregistration Reject
  • FIG. 5 depicted therein is a control message pathway for placing a call from an MS to a terminal (e.g., terminal 203 shown in FIG. 1 or FIG.2) disposed in the WLIP network 100.
  • An ANSI-41 H323 Invoke message 702 (with an encapsulated SeizeTCIl signal) is sent from the RNC 130 to the IP/RNC gateway 250.
  • a RAS Admission Request (ARQ) message 704 which includes the calling and called parties' numbers (A# and B#, respectively) is sent from the IP/RNC gateway 250 to the gatekeeper 200.
  • a RASACF message 706 is then returned from the gatekeeper 200.
  • the IP/RNC gateway 250 After receiving the A CF message 706, the IP/RNC gateway 250 determines if the call can be handled. If not, an ANSI-41 H323 RR message 708 including suitable parametric information, e.g., CallCong parameter, is returned to the RNC 130. Otherwise, the IP/RNC gateway 250 returns an ANSI-41 H323 Invoke message 710 with a ConnectMS2 parameter to the RNC 130. In response thereto, an ANSI-41 H323
  • RR message 712 including a MSConnected parameter is returned to the gateway 250. Subsequently, a trunk connection 714 is established between the gateway 250 and RNC 130 using the B# and a suffix received in the MSConnected parameter.
  • a Q.931 SetUp message 716 with appropriate parametric information is sent from the IP/RNC gateway 250 to the terminal 203.
  • a Q.931 Call Proceeding message 718 is returned from the terminal 203 to the gateway 250.
  • the terminal 203 also engages in RJS messaging with the gatekeeper 200 as shown by the RASARQ and ACF messages 720 and 722, respectively.
  • the terminal 203 sends a Q.931 Alerting message 724 to the IP/RNC gateway 250.
  • a Q.931 Connect message 728 is sent by the terminal 203 to the gateway 250. Thereafter, an H.245 phase 730 is established between the RNC 130 and the terminal 203.
  • a voice gateway (GW)
  • the voice GW 152 is provided as a media gateway, preferably for interfacing between the VoIP network portion and the PSTN (not shown).
  • the voice GW 152 first engages in RJS messaging with the gatekeeper 200 as exemplified by ARQ and ACF messages 802 and 804, respectively. Thereafter, a Q.931 SetUp message 806 with appropriate parametric information is sent from the voice GW to the IP/RNC gateway 250. Responsive thereto, the IP/RNC gateway 250 sends a Call Proceeding message 808 to the voice GW 152.
  • the IP/RNC gateway 250 then engages in its own RJS messaging with the gatekeeper 200 as depicted by ARQ and A CF messages 810 and 812, respectively. Subsequently, the IP/RNC gateway 250 sends an ANSI-41 H323 Invoke message 814 to the RNC 130 with a FindMSposl signal encapsulated therein. After successfully finding the MS' location, the RNC 130 responds by returning an ANSI-41 H323 RR message 816 with the encapsulated MSposfoundl signal. Thereafter, a trunk connection 822 is established between the RNC 130 and the IP/RNC gateway 250, pursuant to the H323 Invoke and RR messages 818 and 820, respectively. These messages include, respectively, ConnectMS2 and MSConnected parameters.
  • FIGS .7 through 9 depict control message pathways for multi-party transactions involving proprietary flash messages which are converted or mapped to appropriate
  • H.323 messages by a flash proxy agent that is described in greater detail hereinbelow.
  • a two-party call (designated as the A-B call) 1004 is first established preferably in a manner set forth above.
  • a third party caller (C) attempts to reach the B party, a number of Q.931 and RJS messages (messages 1006 - 1020) similar to those described hereinabove are propagated among the PBX 1002, voice GW 152, IP/RNC gateway 250 and, the gatekeeper 200.
  • a C ⁇ llW ⁇ iting tone 1022 is issued from the IP/RNC gateway 250 to the RNC 130 serving the MS.
  • Q.931 Alerting message 1024 is sent from the gateway 250 to the PBX 1002, a fl ⁇ shwinfo message 1026 is sent by the RNC 130 to the IP/RNC gateway 250. Responsive thereto, a hold message 1028 is issued by the JP/RNC gateway 250 to the voice GW 152 for holding the A-B call. A hold ⁇ ck message is returned from the voice GW 152 thereafter. Subsequently, a Q.931 Connect message 1032 is sent by the
  • FIG. 8 depicts a control message pathway for an exemplary call enquiry scenario in the WLIP network 100 of the present invention. It should be readily appreciated that the establishment of a two-party call 1102 and subsequent control messages 1104 - 1128 are similar to those described in greater detail in the foregoing sections. Accordingly, it is believed that the exemplary call enquiry method is readily apparent from FIG. 8 and the description above taken in conjunction herewith.
  • a 3-party state 1202 is established with decentralized control, for example, in a multicast manner, of the parties involved.
  • Aflashwinfo message 1204 is sent from the RNC 130 to the IP/RNC gateway 250 after a two-party call (e.g., A-B call) has been put on hold.
  • the IP/RNC gateway 250 sends a retrieve message 1206 to the voice GW 152 in order to effectuate the retrieval of the held A-B call.
  • a retrieve ack response message 1208 is returned from the voice GW 152 to the IP/RNC gateway 250.
  • the present invention advantageously provides an integrated wireless IP network solution for realizing end- user switching services on a packet-based network. Furthermore, the present invention provides an inexpensive way to integrate IP -based switching with cellular networks because of the ease of the provision of an IP switching stack in a gateway and removing the costly MSC components from the network. Accordingly, it should be further appreciated that by using the present invention, operators can quickly and cost- effectively provide IP-based cellular telephony solutions within compact LAN architectures.
  • FIG. 10 depicts a functional block diagram of another view of the WLIP network portion 1202 for supporting multi-party conferences using an MCU 1302.
  • H.323-based network a brief description of the H.323 entities is provided hereinbelow.
  • the H.323 standard defines four major types of components for forming an inter-operable network: terminals, gateways, gatekeepers and multipoint control units (MCUs).
  • Gateways are typically provided between networks (or network portions) that operate based on different standards or protocols.
  • 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.” Accordingly, a plurality of gatekeepers may be provided for carrying out address translation that is necessary for the entire network, each gatekeeper being responsible for a particular zone. In addition, gatekeepers may also provide other services to the terminals, gateways, and MCUs such as bandwidth management and gateway location.
  • the H.323 standard defines multiple types of addresses associated with each endpoint such as, for example, a transport address (which, for example, corresponds to the IP address and the port address of a terminal operated by the end-user) and an alias address.
  • An endpoint may have one or more aliases associated with it.
  • Exemplary aliases may include the well-known EJ64 telephone numbers, H.323 IDs (such as names, email-like addresses, etc.), and so on.
  • the address translation service of the gatekeeper provides an alternative method of addressing an endpoint wherein a user-friendly alias (e.g., the EJ64 telephone number) associated therewith may be translated into its appropriate transport address used by the protocol.
  • the exemplary VoIP core network 206 comprises one or more gatekeepers (e.g., gatekeepers 200A and 200B), one or more terminals (e.g., VCONl terminal 1304 and VCON2 terminal 1306), et cetera, in addition to the MCU 1302.
  • the gateway 250 is preferably provided for interfacing with a radio network controller (e.g., RNC 130) as described hereinabove.
  • RNC 130 radio network controller
  • One or more base stations for example, BS 1204, and associated MSs (e.g., MSI
  • 103 A and MS2 103B are preferably disposed in the cellular network portion of the WLIP network 100 as described hereinabove.
  • the MCU 1302 is provided within the H.323-based VoIP core 206 as an endpoint for providing the capability for three or more terminals and gateways to participate in a multipoint conference. While the MCU 1302 is capable of supporting a conference involving the H.323 entities, it is well-known that the current procedures used in setting up an H.323 conference do not support multi-party services such as call enquiry, call waiting, or 3-party conferences, as defined by the mobile communications standard ANSI-53.
  • FIG. 11 depicts a functional block diagram of yet another view of the WLIP network portion 1203 for supporting multi-party services using a flash agent 203 provided in accordance with the teachings of the present invention. Only relevant portions of the overall network architecture are depicted in this FIGURE.
  • the flash agent 203 is preferably provided as a proxy device disposed between the gateway 250 and the MCU 1302. Accordingly, the flash agent 203 maps an ANSI-53 flash, or such other proprietary flash messages as maybe appropriate (e.g., the flash messages shown in FIGS. 7 through 9) to a suitable H.323 procedure for creating a conference or effectuating a multi-party service.
  • FIGS. 12-14 depict control message pathways for additional exemplary embodiments of a three-party conference service in accordance with the teachings of the present invention.
  • FIGS. 15 and 16 depict control message pathways for two additional exemplary call waiting scenarios, respectively.
  • the flash agent 203 is advantageously utilized between the gateway 250 and MCU 1302 for mapping ANSI-53 messages.
  • an H.323 terminal e.g., VCONl 1304
  • Jhe VCONl terminal 1304 creates a two-party conference with an MS by sending a Create message 1402 to the MCU 1302.
  • the Create message 1402 preferably includes a conference password (e.g., 8711), a separator (which may be provided as a sequence of special characters, e.g., **), and the MS' telephone number (e.g., 888-555-0001).
  • the MCU 1302 sends an Invite message 1404 which contains the password and telephone number information received from the VCONl terminal 1304 to the gateway 250.
  • a Call 1406 is then placed by the gateway 250 to the MS using this information which is routed via the RNC 130.
  • VCON2 terminal 1306, is sent from the RNC 130 to the gateway 250, responsive to the data entered at the MS pursuant to a second conference password.
  • the first conference password i.e., 8711
  • the LAN connection is put on hold (i.e., the RTP speech handler and a call handler associated with the initial two-party conference are disassociated).
  • a Create message 1412 is generated by the gateway 250 which includes the second conference password (e.g., 8712), a separator (which may again be provided as a sequence of special characters, e.g., **), and the telephone number for the VCON2 terminal 1306. This message 1412 is sent from the gateway 250 to the MCU 1302.
  • the MCU 1302 Responsive to the Create message 1412, the MCU 1302 sends an Invite message 1414 to the VCON2 terminal 1306, including the password and telephone number information, for connecting the terminal with the MS. Thereafter, the MS toggles between the original MS-VCON1 connection and the MS- VCON2 connection until a three-party state is achieved.
  • the toggling between the connections is preferably effectuated by sending Flash messages with embedded codes (e.g., messages 1418, 1422, and 1426) and propagating Release messages (e.g., messages 1416 and 1418) between the gateway 250 and the VCON terminals.
  • a Release message 1436 is propagated between the gateway 250 and the MCU 1302.
  • FIG. 13 depicts the control message pathway for the situation where the MS is the creator of the original two-party conference with a VCON terminal.
  • the control messages 1502 - 1536 are substantially similar to those described above in reference to FIG. 12 and accordingly, only the salient features with respect to this exemplary call scenario are described herein.
  • the MS creates and invites the VCONl terminal 1304 to the first conference connection via dialing a conference password (e.g., 8711), a separator, and the terminal's telephone number (e.g., 777-555-0001) (control messages 1502, 1506, and 1508).
  • a conference password e.g., 8711
  • separator e.g., 777-555-0001
  • the MS creates and invites the VCON2 terminal 1306 to the second conference connection via dialing another conference password (e.g., 8712), a separator, and the second terminal's telephone number (e.g., 777-555-0002) (control messages 1512-1514).
  • another conference password e.g., 8712
  • separator e.g., a separator
  • the second terminal's telephone number e.g., 777-555-0002
  • FIG. 14 depicts the conference scenario where two MSs, e.g., MSI 103 A and MS2 103B, are involved in the call connections. Again, only the salient features of this callflow are set forth.
  • MS 1 103 A is provided to be the creator of the original two- party call.
  • MS2 103B is the creator of the enquiry two-party conference connection.
  • MSI creates and invites MS2 to the first conference via dialing in the data as exemplified above.
  • the control messages 1604-1608 illustrate this callflow portion.
  • MS2 creates and invites a terminal (e.g., the VCON2 terminal 1306) to the second conference by dialing in the requisite data as shown by messages 1614-1616.
  • a Release message 1638 is propagated between the gateway 250 and MCU 1302.
  • FIG. 15 depicts a control message pathway for an exemplary embodiment of a call waiting scenario in the WLIP network portion 1203 provided in accordance with the teachings of the present invention.
  • MSI 103 A receives a call from the VCONl terminal 1304 while engaged in a two-party conference with MS2 103B, as shown by control messages 1702-1708.
  • the call from the VCONl terminal 1304 is preferably effectuated in the same manner as described hereinabove.
  • an H.323 Admission Request (ARQ) message is sent from the gateway 250 to the gatekeeper (not shown in this
  • the gateway 250 Upon receiving anAdmission Confirm (ACF) response message therefrom, the gateway 250 stores the ID of the call handler associated with the two-party conference and issues a Call Waiting tone 1716 to the RNC 130. Depending upon the dial input at the MSI, three exemplary events may then take place. For example, by inputting a "0" (message 1718), a Release 1720 of the Call Waiting leg is effectuated between the gateway 250 and the VCONl terminal 1304. By inputting a "1" (message 1722), the original two-party connection is terminated (Release message 1726) and the MSI 142A may then answer the waiting call (Connect messagel728).
  • ACF Application Confirm
  • FIG. 16 depicts yet another exemplary embodiment of a call waiting scenario in the WLIP network portion 1203 wherein MS 1 103 A receives a call from MS2 103B while in a two-party conference with a terminal, e.g., the VCONl terminal 1304.
  • the establishment of the original two-party conference is exemplified by messages 1802- 1806.
  • MS2 103B places a call
  • the RNC 130 sends a Call From message 1808 to the gateway 250.
  • a Call Waiting tone 1812 is issued from the gateway 250 to MSI.
  • an ARQ- ACF messaging session is established between the gateway 250 and the gatekeeper (not shown in this FIG.) so that the gateway 250 stores the ID of the call handler associated with the original two-party conference. Subsequently, similar to the call waiting events described above, multiple call events may be effectuated in this exemplary embodiment by inputting appropriate information at MSI 103 A.
  • the flash agent 203 provided in accordance with the teachings herein advantageously converts legacy ANSI-53 messaging used for establishing multi-party services into appropriate H.323 messaging usable in a host of VoIP implementations. It should further be appreciated that the flash agent functionality, which may be suitably integrated within a gateway or other H.323 components of the network, may also be provided in conjunction with the RNC 130 disposed in the WLIP network portion 202 that includes suitable protocol translators as disclosed herein with respect to FIG. 2.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Telephonic Communication Services (AREA)

Abstract

La présente invention concerne un système et un procédé de mise en oeuvre d'un système de réseau intégré à commutation par paquets sans fil (100, 1202), comprenant un dispositif de commutation basé sur le protocole Internet (IP) (207) dans une passerelle (250) associée. Une partie du réseau cellulaire (102) du système de réseau intégré comprend un contrôleur de réseau radio (130) qui fournit des services d'accès radio aux stations mobiles (103). Une partie du réseau de commutation par paquet (206) transporte le trafic de télécommunication cellulaire. Une interface située entre la passerelle et le contrôleur de réseau radio comprend un premier traducteur de protocole (304) destiné à transformer la messagerie du sous-système de gestion des transactions (SSGT) en messagerie IP, et un deuxième traducteur de protocole (306) destiné à transformer la messagerie du sous-système utilisateur (SSUT) du réseau numérique à intégration de services (ISDN) en messagerie d' 'interface d'accès à débit primaire' (Primary Rate Interface (PRI)). Dans certains modes de réalisation exemples, l'un et/ou les deux traducteurs peuvent être intégrés dans la passerelle IP. Dans un autre mode de réalisation, un agent mandataire clignotant (203) est placé entre la passerelle et une unité de contrôle multipoint (1302) pour faciliter les téléconférences impliquant ANSI-53 ou une messagerie de clignotant propriétaire.
EP99963738A 1998-12-03 1999-11-23 Systeme et procede de mise en oeuvre de commutation mobile et de services de lignes collectives dans un reseau a commutation par paquets Withdrawn EP1135901A2 (fr)

Applications Claiming Priority (5)

Application Number Priority Date Filing Date Title
US11081198P 1998-12-03 1998-12-03
US110811P 1998-12-03
US42651399A 1999-10-26 1999-10-26
US426513 1999-10-26
PCT/SE1999/002163 WO2000033518A2 (fr) 1998-12-03 1999-11-23 Systeme et procede de mise en oeuvre de commutation mobile et de services de lignes collectives dans un reseau a commutation par paquets

Publications (1)

Publication Number Publication Date
EP1135901A2 true EP1135901A2 (fr) 2001-09-26

Family

ID=26808406

Family Applications (1)

Application Number Title Priority Date Filing Date
EP99963738A Withdrawn EP1135901A2 (fr) 1998-12-03 1999-11-23 Systeme et procede de mise en oeuvre de commutation mobile et de services de lignes collectives dans un reseau a commutation par paquets

Country Status (6)

Country Link
EP (1) EP1135901A2 (fr)
CN (1) CN1134944C (fr)
AR (1) AR024844A1 (fr)
AU (1) AU2011100A (fr)
CA (1) CA2353582A1 (fr)
WO (1) WO2000033518A2 (fr)

Families Citing this family (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2352929A (en) * 1999-05-24 2001-02-07 Nec Corp Packet handling in a mobile network
US6400950B1 (en) 1999-07-28 2002-06-04 Ericsson Inc. System and method for de-registration of multiple H.323 end points from a H.323 gatekeeper
AU1318001A (en) * 1999-10-26 2001-05-08 Telefonaktiebolaget Lm Ericsson (Publ) System and method for improved resource management in an integrated telecommunications network having packet-switched network portion and a circuit-switched network portion
WO2001076276A2 (fr) * 2000-04-05 2001-10-11 Telefonaktiebolaget Lm Ericsson (Publ) Reseau de telecommunications integrant des infrastructures cellulaires, de commutation de paquets et de voix sur ip
AU2000265074A1 (en) * 2000-07-31 2002-02-13 Ericsson Inc. System and method for de-registration of multiple h.323 end points from a h.323 gatekeeper
ES2624480T3 (es) * 2001-01-18 2017-07-14 Ntt Docomo, Inc. Sistemas de comunicación de paquetes
KR100369803B1 (ko) * 2001-03-10 2003-02-05 삼성전자 주식회사 무선통신 네트워크의 패킷 음성 호 서비스 방법 및네트워크 구조
CA2468921C (fr) * 2001-12-07 2011-06-14 Telefonaktiebolaget Lm Ericsson (Publ) Systeme et procede d'acces a des services et a un reseau de teleconference dans un reseau de telecommunications
ITTO20020088A1 (it) * 2002-01-31 2003-07-31 Telecom Italia Lab Spa ,,procedimento per realizzare l'interazione fra terminali di reti di telecomunicazioni e relativo sistema,,.
US7333483B2 (en) 2002-04-02 2008-02-19 Huawei Technologies Co., Ltd. Integrated mobile gateway device used in wireless communication network
CN1190978C (zh) * 2002-04-03 2005-02-23 华为技术有限公司 无线通信网络综合移动关口设备
CN100372388C (zh) * 2003-07-16 2008-02-27 Ut斯达康(中国)有限公司 一种基于ip交换的分布式的无线网络控制器
US8554945B1 (en) 2003-08-29 2013-10-08 Sprint Communications Company L.P. Cellular extension of wireless local area networks
RU2376716C2 (ru) * 2004-07-30 2009-12-20 Телефонактиеболагет Лм Эрикссон (Пабл) Способ и устройство для обеспечения средства корреляции в гибридных телекоммуникационных сетях
CN1758635B (zh) * 2004-10-07 2010-04-28 华为技术有限公司 一种基于ip接入的业务去注册方法
EP1838059A4 (fr) * 2004-12-21 2010-05-12 Zte Corp Systeme de commutation pour reseau de communication fixe et mobile et son procede d'implementation
CN100388705C (zh) * 2005-09-06 2008-05-14 华为技术有限公司 给用户提供多种子速率接入的设备和方法
US20090201835A1 (en) * 2008-02-07 2009-08-13 Motorola Inc Method for supporting a multi-party call in combinational session
CN105120204B (zh) * 2015-08-06 2018-08-28 苏州科达科技股份有限公司 兼容多协议的会议中分享双流音频的方法、装置及系统

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2307828A (en) * 1995-12-01 1997-06-04 Northern Telecom Ltd Providing Packet Data to a Mobile Communications System
WO1998040988A1 (fr) * 1997-03-13 1998-09-17 Telefonaktiebolaget Lm Ericsson (Publ) Acces a un reseau informatique avec connexion uniquement au niveau du transfert de donnees

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5475689A (en) * 1990-12-06 1995-12-12 Hughes Aircraft Company Cellular telephone with datagram and dispatch operation
FI104869B (fi) * 1995-05-24 2000-04-14 Ericsson Telefon Ab L M Menetelmä verkkojen välisen puheyhteyden muodostamiseksi ja älyverkkopalvelu

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2307828A (en) * 1995-12-01 1997-06-04 Northern Telecom Ltd Providing Packet Data to a Mobile Communications System
WO1998040988A1 (fr) * 1997-03-13 1998-09-17 Telefonaktiebolaget Lm Ericsson (Publ) Acces a un reseau informatique avec connexion uniquement au niveau du transfert de donnees

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ETSI: "Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); Service description; Stage 2 (GSM 03.60 version 6.1.0 DRAFT)", GSM03.60 V6.1.0 DRAFT 1998-05, May 1998 (1998-05-01), XP014018522 *
ETSI: "Digital cellular telecommunications system (Phase 2+); Mobile Application Part (MAP) specification (GSM 09.02)", DRAFT PRETS 300 599, MARCH 1997, SIXTH EDITION, pages 78 - 85 *

Also Published As

Publication number Publication date
CN1134944C (zh) 2004-01-14
CA2353582A1 (fr) 2000-06-08
WO2000033518A3 (fr) 2000-08-17
WO2000033518A2 (fr) 2000-06-08
AU2011100A (en) 2000-06-19
CN1335008A (zh) 2002-02-06
AR024844A1 (es) 2002-10-30

Similar Documents

Publication Publication Date Title
US10587573B2 (en) Exchange and use of globally unique device identifiers for circuit-switched and packet switched integration
US6795444B1 (en) System and method for providing wireless telephony over a packet-switched network
US6888803B1 (en) System, method, and computer program product for connectivity of wireless base station to PSTN via an IP data network
AU774880B2 (en) Method of and system for providing intelligent network control services in IP telephony
EP1611720B1 (fr) Procede, systeme et dispositif a passerelle permettant l'interfonctionnement entre des reseaux fondes sur le protocole internet et des reseaux a commutation de circuits
US8213418B2 (en) Providing packet-based multimedia services via a circuit breaker
US7110393B1 (en) System and method for providing user mobility handling in a network telephony system
EP1894372B1 (fr) Acheminement d'appels inter-domaines
EP1483888B1 (fr) Appareil et procede pour couplage ordinateur telephone dans des reseaux teleponiques a commutation par paquets
EP1135901A2 (fr) Systeme et procede de mise en oeuvre de commutation mobile et de services de lignes collectives dans un reseau a commutation par paquets
US20070070976A1 (en) Mobile and packet-based call control
US20090034471A1 (en) Method and system for handoff between wireless networks
US20060092925A1 (en) Roaming between circuit-switched and all-IP networks
AU2004222782B2 (en) Network, private branch exchange, wireless LAN terminal, multiprotocol communication terminal control method therefor
US9161190B2 (en) Methods, systems, and computer readable media for unifying fixed and mobile devices via third party call control
EP1914973B1 (fr) Système et procédé pour fournir des services combinés à des appelants anonymes
CA2353626A1 (fr) Systeme et procede d'enregistrement de terminal mobile dans un reseau integre a commutation par paquets sans fil
KR100401262B1 (ko) 이동전화망에서의 화상전화 서비스 제공 장치 및 그 방법
Liao et al. VoIP mobility in IP/cellular network internetworking
Hribar et al. Usage of BICC and SIP protocol in IP core network

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: 20010601

AK Designated contracting states

Kind code of ref document: A2

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: BALAZINSKI, BARTOSZ

Inventor name: BERTRAND, JEAN-FRANCOIS

Inventor name: HERNANDEZ, LAURA

Inventor name: TRAN, HUNG

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)

17Q First examination report despatched

Effective date: 20070927

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20080208