WO2000079815A1 - Mobilite dans des reseaux de telephonie commutes par paquets - Google Patents

Mobilite dans des reseaux de telephonie commutes par paquets Download PDF

Info

Publication number
WO2000079815A1
WO2000079815A1 PCT/US2000/014021 US0014021W WO0079815A1 WO 2000079815 A1 WO2000079815 A1 WO 2000079815A1 US 0014021 W US0014021 W US 0014021W WO 0079815 A1 WO0079815 A1 WO 0079815A1
Authority
WO
WIPO (PCT)
Prior art keywords
subscriber terminal
network
subscriber
home
location register
Prior art date
Application number
PCT/US2000/014021
Other languages
English (en)
Inventor
Stefano M. Faccin
Khiem Van Le
Original Assignee
Nokia Networks Oy
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 Nokia Networks Oy filed Critical Nokia Networks Oy
Priority to AU50368/00A priority Critical patent/AU5036800A/en
Publication of WO2000079815A1 publication Critical patent/WO2000079815A1/fr

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/06—Registration at serving network Location Register, VLR or user mobility server
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/26—Network addressing or numbering for mobility support
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/04—Network layer protocols, e.g. mobile IP [Internet Protocol]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/08—Upper layer protocols
    • H04W80/10—Upper layer protocols adapted for application session management, e.g. SIP [Session Initiation Protocol]
    • 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/16—Gateway arrangements
    • 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

  • This application generally relates to packet-switched telephony networks, such as IP telephony networks, and more particularly to a technique to allow roaming or mobility between such packet-switched telephony networks.
  • IP telephony networks Voice or telephony services can now be provided over a packet-switched network, such as the Internet.
  • IP telephony networks are commonly referred to as IP telephony networks because the Internet Protocol (IP) is the primary protocol used over the Internet.
  • IP telephony standard for example, is the International Telecommunications Union (ITU) H.323 standard.
  • Fig. 1 illustrates an example of an IP telephony network, also known as a Voice over IP (VoIP) Network.
  • the VoIP network includes a gatekeeper function, one or more gateways and a packet-switched network (e.g., a portion of the Internet).
  • the gatekeeper function is optional and provides call authorization for both accepting and placing calls in its zone or area of control.
  • a gatekeeper can also allocate bandwidth, can maintain call detail records, and can perform other network management functions.
  • a packet-switched- telephony gateway bridges a circuit switched network such as the Public Switched Telephone Network (PSTN) and a packet-switched network such as an IP network or the Internet.
  • PSTN Public Switched Telephone Network
  • IP network such as an IP network or the Internet.
  • the IP telephony gateway bridges the PSTN and IP networks to allow phone-to-phone and phone-to-personal computer (PC) multimedia communications (voice, video and/or data).
  • the IP telephony gateway provides the appropriate translation between transmission formats (for example, H.225.0 of an H.323 endpoint to/from H.221 of an H.320 endpoint) and between communication procedures (for example, H.245 of an H.323 endpoint to/from H.242 of an H.320 endpoint).
  • the IP telephony gateway also performs call setup and clearing on both the network side and the switched circuit network side. Translation between video, audio, and data formats may also be performed in the gateway.
  • the purpose of the IP-telephony gateway is to complete the call in both directions between the network endpoint and the switched circuit network endpoint in a transparent fashion.
  • IP telephony gateway is the H.323 gateway (implementing the ITU H.323 standard).
  • H.323 gateways allow interoperation of H.323 systems with other audio/video conferencing systems on Integrated Services Digital Networks (ISDN), plain old telephone systems (POTS), Asynchronous Transfer Mode (ATM), and other transports.
  • ISDN Integrated Services Digital Networks
  • POTS plain old telephone systems
  • ATM Asynchronous Transfer Mode
  • An IP telephony gateway operates as an endpoint on the IP-telephony network that provides real-time, two-way communication between IP telephony terminals on the
  • FIG. 1 is a diagram illustrating an example IP telephony network. Referring to
  • GW IP telephony gateway
  • Originating IP telephony GW IP telephony gateway
  • the gateway contacts the gatekeeper it is registered with asking to set up a call towards the dialed number received from the incoming call set up request (Access Request, ARQ, 2).
  • the gatekeeper translates the dialed number (or directory number) into the IP address of the Destination IP-telephony gateway, i.e. the gateway that has to be reached in order to reach the final destination of the call, and provides this IP address to the originating IP telephony gateway (Access Confirmation, ACF, 3).
  • the Originating IP-telephony GW sets up an IP-telephony call over the packet-switched network or IP network towards the Destination IP-Telephony GW providing its IP address and the dialed number (Call setup, 3).
  • the Destination IP-telephony GW contacts the gatekeeper it is registered with (it may be the same as the Originating IP-telephony GW or a different gatekeeper) asking to accept a call incoming from the Originating IP-telephony GW (ARQ, 4) and directed towards the dialed number.
  • the Destination IP-telephony GW If the gatekeeper grants the incoming call to the Destination IP-telephony GW (ACF, 5), the Destination IP-telephony GW establishes the PSTN call (call, 7), and then the call is established between the two IP-telephony GWs over the IP network (call establishment, 6). The destination IP-telephony gateway translates the IP packets into the appropriate format for transmission over the PSTN.
  • IP telephony standards and products are currently defined only for fixed networks. Mobility has not been considered in IP telephony in the sense that IP telephony subscribers are not allowed to roam between IP telephony networks.
  • a subscriber in one area of the country is registered with a local gatekeeper. If the subscriber moves or travels to another part of the country, the subscriber will not be able to connect to the gatekeeper in the new part of the country because the new gatekeeper has no information describing the subscriber.
  • GSM Global System for Mobile
  • VLR visiting location register
  • HLR home location register
  • the VLR contains relevant data of all mobile stations currently located in a serving Mobile Services Switching Center (MSC).
  • MSC Mobile Services Switching Center
  • the HLR is a database in charge of the management of the mobile subscribers.
  • the data stored in the HLR includes service subscription information and location information (the identity of the currently serving VLR to enable routing of mobile-terminated calls).
  • MSISDN Mobile subscriber ISDN number
  • GMSC gateway function of the MSC
  • the GMSC based on its internal tables, correlates the MSISDN number to the specific HLR, which has to be queried to obtain subscriber information.
  • the HLR replies by providing a roaming number for routing a call to the subscriber.
  • the GMSC then re-routes the call to that particular number.
  • HLRs and VLRs in cellular systems permits roaming only for cellular calls provided over the PSTN. IP-telephony networks do not allow subscribers to roam.
  • a technique is provided to allow roaming or mobility between packet-switched telephony networks or subnetworks (such as between IP telephony networks).
  • one or more packet-switched telephony networks or VoIP networks having mobility or roaming capabilities is provided, each such network being referred to as a Mobile VoIP (MVolP) network.
  • MVolP Mobile VoIP
  • a technique is described herein which supports roaming between MVolP networks and for the routing of calls to mobile users or subscribers roaming from a MVolP network to another MVolP network, or roaming between subnetworks within a MVolP network, with each subnetwork including one or more areas.
  • a VoIP Location Register is connected to each subnetwork, and includes a database for storing subscriber profiles.
  • Each subscriber terminal of a MVolP network is statically associated with (homed by) one VolPLR at subscription time, referred to as the subscriber's Home VolPLR.
  • Each VolPLR is associated with a unique VolPLR Identification (VoIPLR ID).
  • Each VolPLR corresponds to a specific sub-network of the MVolP network, according to one embodiment of the invention.
  • the subscriber terminal When a subscriber terminal roams to a new subnetwork or to a new MVolP network, the subscriber terminal registers with the local VolPLR serving the new subnetwork (the "serving VolPLR") to provide the serving VolPLR the subscriber's current IP address (the IP address where the subscriber can be reached) and status.
  • the serving VolPLR the local VolPLR serving the new subnetwork
  • the serving VolPLR After the subscriber terminal registers its current (temporary) IP address and status to the serving VolPLR, the serving VolPLR then contacts and provides the subscriber's updated location (including the subscriber's temporary IP address) and status (e.g., connected or not) information to the subscriber's Home VolPLR. In this manner, the subscriber's Home VolPLR always will contain the subscriber terminal's current location and status information, regardless of the subscriber's location.
  • a PSTN call is placed to a Mobile IP Telephony Gateway (MITGW) in the called subscriber's MVolP network.
  • MITGW Mobile IP Telephony Gateway
  • the MITGW contacts the subscriber's Home VolPLR to obtain the called subscriber's current status and location.
  • the MITGW sets up an IP telephony call over a packet-switched network (such as the Internet) towards the IP address corresponding to the dialed DN.
  • a call originating from within the MVolP network can be delivered to a called subscriber.
  • a calling subscriber registers with a control entity (such as a gatekeeper).
  • the calling subscriber then contacts the gatekeeper and requests an IP telephony call to called subscriber identified by a DN (or other alias).
  • the gatekeeper contacts the called subscriber's home VolPLR, obtains the subscriber terminals current status and location, and sets up an IP telephony call between the calling subscriber and the called subscriber over a packet-switched network (e.g., the Internet).
  • a packet-switched network e.g., the Internet
  • the present invention allows subscribers to roam within different subnetworks of a MVolP network or between different MVolP networks.
  • Fig. 1 is a diagram illustrating an example of an IP telephony network.
  • Fig. 2 is a block diagram illustrating an example of Mobile Voice over IP (MVolP) Networks according to an embodiment of the present invention.
  • MVolP Mobile Voice over IP
  • Fig.3 is a flow chart illustrating a registration procedure according to an embodiment of the present invention.
  • Fig. 4 is a flow chart illustrating call delivery to a subscriber from a PSTN according to an embodiment of the present invention.
  • Fig. 5 is a diagram illustrating call delivery to a subscriber from a PSTN according to an embodiment of the present invention.
  • Fig. 6 is a flow chart illustrating call delivery within the MVolP network where the calling party is registered with a control entity according to an embodiment of the present invention.
  • a technique is disclosed to allow roaming between VoIP networks.
  • a VoIP network having mobility or roaming capabilities is referred to herein as a Mobile VoIP (MVolP) network.
  • MVolP Mobile VoIP
  • a technique is described herein which supports roaming between MVolP networks and for the routing of calls to mobile users or subscribers roaming from a MVolP network to another MVolP network, or roaming between subnetworks within a MVolP Network
  • each user belonging to MVolP network is identified by an alias.
  • the alias can take many forms, so long as it identifies the user.
  • the alias can be a Directory Number - DN (e.g., E.164 format) that can be dialed to set-up a call towards the user.
  • the user can also be identified or associated with a Logical
  • each user of a MVolP network is a subscriber of the MVolP network.
  • users will be referred to hereinafter as subscribers.
  • Each subscriber is associated with a globally unique identifier - a SubscriberlD.
  • the subscriber is associated with a profile, which may include information describing the subscriber including the subscriber's SubscriberlD, the subscriber's directory number (DN) and, optionally, the Logical Name associated to the subscriber.
  • DN subscriber's directory number
  • the SubscriberlD is used by the subscriber to identify itself and by the VolPLR to retrieve the corresponding subscriber profile. Because the subscriber belongs to a MVolP network, the subscriber is also associated with an IP address. For example, the subscriber's
  • IP address is seen as the transport address at which the subscriber can be reached on the packet-switched network (e.g., the subscriber's IP network address).
  • the subscriber's IP address can be allocated both statically (i.e., the address is assigned by the MVolP network at subscription time and, as such, stored in the subscriber profile) and/or dynamically (i.e., assigned when the subscriber connects to the MVolP network and, optionally, changed at every time the subscriber reconnects; the address is stored in the subscriber profile every time the user reconnects).
  • the subscriber terminal can have a different (and temporary) IP address each time it connects to a new MVolP network or subnetwork.
  • the new current IP address can be generated or obtained using IP address configuration protocols, such as Dynamic Host Configuration Protocol (DHCP), or other techniques.
  • DHCP Dynamic Host Configuration Protocol
  • a VoIP Location Register (VolPLR)
  • MITGW Mobile IP Telephony GW
  • the subscriber's Home MVolP network refers to the MVolP network with which the user has the subscription
  • the Serving MVolP network refers to the MVolP network where the subscriber is currently located.
  • Fig.2 is a block diagram illustrating an example of Mobile Voice over IP (MVolP) Networks according to an embodiment of the present invention.
  • MVolP network 1 202 includes one or more subnetworks, including, subnetwork 1 (subnet 1) 210 and subnetwork 2 (subnet 2) 230. Although two subnetworks are shown, any number can be provided within a MVolP network.
  • Subnetwork 1 210 includes subnetwork area A 212 and subnetwork area B 214.
  • subnetwork 2230 is divided into area A 232 and area B 234.
  • a subscriber terminal Y 222 is connected to subnetwork 1 210 and a subscriber terminal Z 244 is connected to subnetwork
  • gatekeeper 1 (GK1) 216 is connected to area A 212 and gatekeeper 2 (GK2) 218 is connected to area B 214 of subnetwork 1 210. Also, Gatekeeper 1 (GK1) 216 is connected to area A 212 and gatekeeper 2 (GK2) 218 is connected to area B 214 of subnetwork 1 210. Also, Gatekeeper 1 (GK1) 216 is connected to area A 212 and gatekeeper 2 (GK2) 218 is connected to area B 214 of subnetwork 1 210. Also, Gatekeeper
  • GK3 236 is connected to area A 232 and gatekeeper 4 (GK4) and gatekeeper 5 (GK5) are connected to area B 234 of subnetwork 2 230.
  • Each subnetwork corresponds to a portion of a packet-switched network (e.g., a portion of the Internet, or a Local Area Network, a portion of a Wide Area Network, etc.).
  • a VoIP Location Register (VolPLR) is connected to each subnetwork.
  • VolPLR 1 220 is connected to subnetwork 1 210 and VolPLR 2 242 is connected to subnetwork 2 230.
  • VolPLR is a database that stores a record or profile on subscribers and allows the subscribers to roam between MVolP networks and subnetworks.
  • the subnetworks are connected to the PSTN 250 via one or more Mobile IP telephony gateways (MITGWs).
  • MITGW 1 260 is connected between PSTN 250 and subnetwork 1 210.
  • MITGW 2262 and MITGW 3 264 is connected between the PSTN 250 and subnetwork 2 230.
  • a terminal X 252 is connected to PSTN 250 and may or may not be a MVolP network subscriber.
  • the other terminals 222 and 244 are presumed, for this example, to be MVolP network subscribers.
  • each area may correspond to a gatekeeper zone described in H.323. As such, there may be one gatekeeper for controlling each zone or area. Alternatively, there may be many gatekeepers associated with each area (e.g., each area includes many zones), or there may be one gatekeeper for many areas. According to an embodiment of the present invention, there may be many MVolP networks connected to one another. The present invention allows subscriber terminals to roam between MVolP networks and between subnetworks (within one MVolP network). For example, as shown in Fig. 2, MVolP network 2 270 is connected to MVolP network 1 202.
  • MVolP network 2 270 includes a subnetwork 3 272 (only one of the subnets is shown), a gatekeeper 6 (GK6), MITGW 4 278, a VolPLR 3 276 and a subscriber terminal W 280 connected to subnetwork 3 272.
  • MITGW4278 is connected to the PSTN 250.
  • the particular network configuration shown in Fig. 2 is provided only as an example embodiment that is used to explain the concepts of the present invention. The present invention is not limited to the configuration illustrated in Fig. 2.
  • Each subscriber of a MVolP network is statically associated with (homed by) one
  • Each VolPLR is associated with a unique VolPLR Identification (VoIPLR ID).
  • VoIPLR ID corresponds to a specific sub-network of the MVolP network. (Alternatively, each VolPLR could correspond to a specific MVolP network).
  • each MVolP sub-network can be divided into different areas.
  • the MVolP network identifies the particular MVolP network, subnetwork or subnetwork area to which the subscriber terminal is connecting.
  • each subscriber terminal receives the identity of the sub-network area (SNA_ID) to which the terminal is connecting.
  • SNA_ID sub-network area
  • each subnetwork includes several subnetwork areas (SNAs)
  • the SNA IDs corresponding to a sub-network are each associated with the VoIPLR ID of the VolPLR in that sub-network. As noted above, there is one VolPLR for each subnetwork.
  • the VoIPLR ID identifies the Home VolPLR of a subscriber.
  • the Home VoIPLR ID can be derived from a subscriber's SubscriberlD. In this way, from the SubscriberlD it is possible to identify the VolPLR that is home to the subscriber (the subscriber's Home VolPLR).
  • the VoIPLR ID of the Home VolPLR can be derived (or obtained) from the SubscriberlD in several different ways. For example, a look-up table can be used to identify a Home VoIPLR_ID corresponding to each SubscriberlD (because there is only one Home VolPLR per subscriber).
  • the VoIPLR ID itself can be embedded or provided within the SubscriberlD (e.g., provided as a portion of the SubscriberlD), such as a suffix or prefix in the SubscriberlD.
  • the VolPLR is a database that contains the location information needed to locate the subscriber and deliver the services.
  • the location information is an address (e.g., network address or IP address of the subscriber) towards which calls have to be forwarded to reach the subscriber terminal.
  • Each VolPLR can contains two types of records or profiles: * Complete subscriber profile, if the NoIPLR is the Home VolPLR for the subscriber.
  • the VolPLR contains the complete service profile for the subscriber, including the subscriber's name, SubscriberlD, aliases (e.g., D ⁇ and Logical Name), subscriber service and the subscriber's current status (e.g., connected or not connected) and location (i.e., IP address at which the subscriber can be reached and an identification of the MVolP network, subnetwork or area where the subscriber is located).
  • the subscriber's name e.g., SubscriberlD
  • aliases e.g., D ⁇ and Logical Name
  • subscriber service e.g., connected or not connected
  • location i.e., IP address at which the subscriber can be reached and an identification of the MVolP network, subnetwork or area where the subscriber is located.
  • Roaming subscriber profile for subscribers currently connected to the subnetwork corresponding to the VolPLR.
  • a Roaming subscriber profile is stored in the current VolPLR (corresponding to the subnetwork where the subscriber is currently connected or located) if the current VolPLR is different from the subscriber's Home VolPLR. In other words, the subscriber is roaming if he/she is located in a subnetwork outside the subnetwork corresponding to his Home VolPLR.
  • the Roaming subscriber profile could be all or a subset of the Complete subscriber profile which may downloaded into the serving
  • the location information contained in the current VolPLR record is an IP address where a mobile terminated IP telephony call can be routed in the MVolP network to reach the subscriber terminal. If the subscriber is not connected, the location information can be either void or could be a default IP address (e.g. answering machine).
  • MITGW Mobile IP-Telephony Gateway
  • the Mobile IP Telephony GW is an IP Telephony GW augmented with mobility support, as described herein.
  • the MITGW translates the received directory number (DN) of a call to the VoIPLR ID of the Home VolPLR of the called subscriber.
  • the MITGW can then communicate with the Home VolPLR to obtain the current location and status of the called subscriber (the subscriber corresponding to the DN).
  • the MITGW then establishes the IP telephony call over the packet-switched network (e.g., Internet) between the MITGW and the current IP address of the called subscriber to complete the call.
  • the data packets of the IP-telephony call can be provided between directly between the MITGW and the IP address of the called subscriber, while the signaling can be routed through the gatekeeper.
  • a registration procedure described below is used to constantly maintain updated status and location information of the subscriber terminal at the subscriber's Home VolPLR
  • the subscriber's current location stored in the Home VolPLR includes the IP address at which the subscriber can be reached and an identification of the MVolP network, subnetwork or subnetwork area where the subscriber is located (e.g., the network or subnetwork or subnetwork area to which the subscriber terminal is connected).
  • An example of such a network identification is the SNA ID which can be stored in the Home VolPLR to identify the current subnetwork area, a subnetwork ID to identify the current subnetwork and/or a MVoIP ID to identify the current MVolP network where the subscriber is located.
  • the subscriber status can include, for example, whether the subscriber terminal is connected or not connected to the network.
  • a subscriber can also select other status options, such as blocking all incoming calls, while allowing the subscriber to place outgoing IP telephony calls. If a call is received that is intended for a subscriber that is either not connected to the network or has blocked all incoming calls, the receiving MITGW (after obtaining the called subscriber's status and location from the called subscriber's Home VolPLR), can either decline to place the requested call (e.g., return a busy or unavailable indication to the caller because the called party is not connected or incoming calls are blocked) or route the call to a predetermined IP address associated with the subscriber, such as the subscriber's answering machine or voice mail system.
  • Each MITGW is able to derive or determine the VoIPLR ID of the subscriber's Home VolPLR based on a received directory number (DN) or other alias. For example, the VoIPLR ID can be identified based on the DN using a look-up table. Because the Home VolPLR contains the current location and status of the called subscriber, the MITGW can obtain the current location (including the IP address where the subscriber can be located) of the called subscriber based on the Home VoIPLR ID. According to an embodiment of the present invention, the VoIPLR_ID may actually be or include the IP address of the Home VolPLR. In this way, the MITGW is able to forward or establish the call over the IP network between the MITGW and the called subscriber regardless of the subscriber's current location. Registration
  • a registration procedure is performed in order to update the subscriber status and location information.
  • Fig. 3 is a flow chart illustrating a registration procedure according to an embodiment of the present invention.
  • the subscriber obtains an identification of the subscriber's location within the MVolP network (i.e., the SNA ID identifying the subnetwork area where the subscriber terminal is located).
  • a different SNA_ID may be broadcast in each subnetwork area.
  • the subscriber terminal may or may not register depending on whether it detects it has moved to a new subnetwork area (by detecting a new SNA ID).
  • the subscriber terminal can compare its current SNA_ID to the previous SNA ID to determine if the subscriber terminal is located in a new subnetwork area.
  • the subscriber terminal may simply provide its new status to the gatekeeper in the area (e.g., indicating that the subscriber terminal is now available to receive calls). If already registered in the area, the subscriber terminal can de-register with the Serving VolPLR just before the subscriber terminal disconnects from the network (so that the subscriber's Home VolPLR will receive this updated status information). The remainder of the description of Fig. 3 assumes that the subscriber terminal will perform registration.
  • the subscriber terminal connects to the MVolP network and provides its SubscriberlD.
  • the subscriber terminal may connect to the MVolP network by connecting to a gatekeeper located in the subnetwork where the subscriber terminal is located, and provides its SubscriberlD to the gatekeeper.
  • the SubscriberlD of the registering subscriber terminal is forwarded by the gatekeeper to the serving VolPLR in the subnetwork.
  • the serving VolPLR is the VolPLR which corresponds to or serves the local subnetwork to which the subscriber has connected (i.e., where the subscriber terminal is located).
  • Each subnetwork includes one or more subnetwork areas. There is one VolPLR which serves each subnetwork.
  • the subscriber terminal obtains or generates a new (current) IP address based on the SNA_ID, and then provides its IP address, SubscriberlD, its current status (e.g., connected or not, able to receive incoming calls or not) and old SNA ID to the serving
  • this information can be provided to the serving VolPLR through a gatekeeper.
  • the subscriber may alternatively provide this information directly to the serving
  • the subscriber may generate or obtain an IP address in a variety of different ways.
  • the subscriber's new address may be obtained using Dynamic Host Configuration
  • DHCP Home IP Protocol
  • a temporary IP address corresponding to the visited area is used by the subscriber until the subscriber roams to a different area, where a new temporary IP address corresponding to the new visited area will be used by the subscriber terminal.
  • a Home IP address may be used each time the subscriber is connected to its Home
  • MVoIPLR and a temporary IP address can be generated and used for each new area, subnetwork or network the subscriber visits outside his Home.
  • Other techniques can be used to generate or obtain new or updated IP addresses as the subscriber roams between or even within MVolP networks.
  • the serving VolPLR examines the SubscriberlD provided by the subscriber terminal and identifies or derives the VoIPLR_ID (identifying the subscriber terminal's Home VolPLR) which corresponds to the received SubscriberlD. As noted above, there is one VolPLR ID (identifying the Home VolPLR) corresponding to each
  • the Serving VolPLR for example, can use a look-up table to identify the
  • Home VoIPLR ID or the VoIPLR ID may be provided directly within the SubscriberlD itself.
  • the serving VolPLR compares the VoIPLR ID (identifying the subscriber's Home VolPLR) to its own VoIPLR ID. Two cases are possible. If the serving VolPLR is the subscriber's Home VolPLR, the registration procedure performs blocks 330 and 335.
  • the Home VolPLR updates the subscriber's current location (e.g., IP address where calls directed to the subscriber can be routed and the serving SNA ID) and status (e.g., connected or not connected) in the subscriber's Complete profile stored at the subscriber's Home VolPLR.
  • the subscriber's Home IP address can be used in this case.
  • the IP address where calls directed to the subscriber can be routed can be either the actual IP address of the subscriber terminal or an IP address of a serving gatekeeper.
  • the Home VolPLR contacts the old VolPLR in order to cancel the stored profile at the old VolPLR.
  • the identity (including address) of the old VolPLR can be either derived from the previously stored SNA_ID of the sub-network area where the terminal was previously connected or from the SNA ID provided from the subscriber terminal.
  • the Home VolPLR then contacts the old VolPLR and cancels this outdated Roaming subscriber profile stored there (because the subscriber is no longer located or connected there).
  • blocks 340 and 345 are performed.
  • the serving VolPLR contacts the Home VolPLR (based on the VoIPLR ID) and provides the subscriber terminal's current location (e.g., IP address where calls directed to the subscriber can be routed and the serving SNA ID) and status (e.g., connected or not connected) to the Home VolPLR.
  • the Home VolPLR will also cancel the old Roaming profile located at the VolPLR to which the subscriber was previously connected (only if this old VolPLR is not the Home VolPLR).
  • the serving VolPLR stores a Roaming profile for the subscriber received from the subscriber's Home VolPLR, including the subscriber's SubscriberlD, the subscriber's updated location and status .
  • the stored IP address is a temporary IP address that corresponds, for example, to the new area or subnetwork where the subscriber is located or connected.
  • This registration procedure can be performed when the subscriber roams and connects to a new MVolP, a new subnetwork, or to a new subnetwork area, etc.
  • updated location information including an updated IP address corresponding to the geographic location, area, subnetwork where the subscriber is located
  • status information for the subscriber are always maintained in one central known location (the subscriber's Home VolPLR).
  • entities e.g., gateways and gatekeepers
  • Fig. 4 is a flow chart illustrating call delivery to a subscriber from a PSTN according to an embodiment of the present invention.
  • Fig. 5 is a diagram illustrating call delivery to a subscriber from a PSTN according to an embodiment of the present invention.
  • a PSTN call is directed towards one of the Mobile IP Telephony gateways (MITGWs) of the home MVolP network of the called subscriber, block 410. This is illustrated as step 1 in Fig. 5.
  • the MITGW identifies the VoIPLR D (which identifies the Home
  • the MITGW can identify the VoIPLR ID corresponding to the DN using a look-up table or other technique.
  • the MITGW contacts the subscriber's Home VolPLR (corresponding to the dialed DN) and provides the DN to the Home VolPLR in order to have the dialed number (DN) translated into an IP address to set-up an IP telephony call towards the location of the subscriber. This is illustrated as step 2 in Fig. 5.
  • the Home VolPLR retrieves the current location and status stored of the called subscriber (e.g., from the subscriber's complete profile in the Home VolPLR) and provides the MITGW with the destination IP address towards which the call should be forwarded to reach the called subscriber. This corresponds to step 3 in Fig. 5.
  • the MITGW sets up an IP telephony call from itself towards the destination IP address received from the VolPLR (indicating the subscriber's current location), and indicating that the call is directed towards the DN (i.e., DN is used as an alias), block 430. This is illustrated as step 4 in Fig. 5.
  • X 252 (e.g., which is not a MVolP network subscriber) dials the DN corresponding to subscriber terminal Y 222.
  • VolPLR 1 220 is the Home
  • the PSTN call is routed to MITGW 1 260, for example.
  • MITGW 1 contacts VolPLR 1 220 to obtain the current IP address of terminal Y 222.
  • MITGW 1 260 sets up an IP telephony between itself and the IP address of terminal Y 222 or gatekeeper 208 (i.e., data packets can be routed through gatekeeper 208 or directly to terminal Y).
  • the IP telephony call may be established using the IP address of MITGW 1 260 as the source address) and the IP address of terminal Y 222 or the IP address of gatekeeper 208 as a destination address).
  • Fig. 6 is a flow chart illustrating call delivery within the MVolP network where the calling party is registered with a control entity.
  • the calling subscriber registers with a control entity (e.g., gatekeeper).
  • the calling subscriber contacts the control entity and requests an IP telephony call to a called subscriber corresponding to a DN.
  • the DN is provided to the control entity.
  • control entity identifies the VoIPLRJD corresponding to the DN (identifying the Home VolPLR of the called subscriber) .
  • control entity contacts the called subscriber's Home VolPLR.
  • control entity obtains the destination IP address of the called subscriber
  • the control entity sets up an IP telephony call over the IP network from the calling subscriber terminal to the destination IP address of the called subscriber. If the called subscriber's Home VolPLR cannot be reached (either because the called party is not a MVolP network subscriber or due to technical/roaming agreement problems), the call is routed as a call towards the PSTN (e.g., routed to the nearest MITGW for routing to the PSTN) using the dialed DN as destination. On the called side, this received call is managed as an incoming call from PSTN., described in Fig. 4.
  • the call is routed as a call towards PSTN using the dialed DN as destination.
  • this case is managed as an incoming call from PSTN, described in Fig. 4.

Abstract

L'invention concerne un système permettant à des utilisateurs d'être itinérants entre différents réseaux de téléphonie PI, ou entre des sous-réseaux à l'intérieur d'un réseau de téléphonie PI. Un terminal d'abonné se connecte à un sous-réseau local différent de son sous-réseau de rattachement. Le terminal d'abonné s'enregistre auprès d'un enregistreur de position de desserte correspondant au sous-réseau local. L'enregistreur de position de desserte mémorise des informations de localisation actualisées, telles qu'une adresse réseau en vigueur à laquelle le terminal de l'abonné peut être atteint lorsqu'il est relié au sous-réseau local. L'enregistreur de localisation nominal du terminal de l'abonné correspondant au sous-réseau de rattachement de l'abonné reçoit et mémorise l'adresse réseau actualisée pour le terminal de l'abonné. Une demande d'appel à l'abonné est reçue. L'adresse réseau en vigueur du terminal de l'abonné est obtenue de l'enregistreur de localisation nominal de l'abonné et l'appel de téléphonie PI est établi vers l'adresse réseau en vigueur du terminal de l'abonné.
PCT/US2000/014021 1999-06-21 2000-05-22 Mobilite dans des reseaux de telephonie commutes par paquets WO2000079815A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU50368/00A AU5036800A (en) 1999-06-21 2000-05-22 Mobility in packet-switched telephony networks

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US33733699A 1999-06-21 1999-06-21
US09/337,336 1999-06-21

Publications (1)

Publication Number Publication Date
WO2000079815A1 true WO2000079815A1 (fr) 2000-12-28

Family

ID=23320134

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2000/014021 WO2000079815A1 (fr) 1999-06-21 2000-05-22 Mobilite dans des reseaux de telephonie commutes par paquets

Country Status (2)

Country Link
AU (1) AU5036800A (fr)
WO (1) WO2000079815A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1130857A2 (fr) * 2000-03-01 2001-09-05 Mitsubishi Denki Kabushiki Kaisha Système de transmission par paquets dans communications mobiles
CN100444688C (zh) * 2005-08-08 2008-12-17 中兴通讯股份有限公司 移动性限制下的自助式漫游区域登记方法

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1998039934A2 (fr) * 1997-03-04 1998-09-11 Northern Telecom Limited Procedes pour reacheminer des appels dans un reseau de communications a base de paquets

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1998039934A2 (fr) * 1997-03-04 1998-09-11 Northern Telecom Limited Procedes pour reacheminer des appels dans un reseau de communications a base de paquets

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
LIAO W: "MOBILE INTERNET TELEPHONY: MOBILE EXTENSIONS TO H.323", PROCEEDINGS IEEE INFOCOM. THE CONFERENCE ON COMPUTER COMMUNICATIONS,US,NEW YORK, NY: IEEE, 21 March 1999 (1999-03-21), pages 12 - 19, XP000868780, ISBN: 0-7803-5418-4 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1130857A2 (fr) * 2000-03-01 2001-09-05 Mitsubishi Denki Kabushiki Kaisha Système de transmission par paquets dans communications mobiles
EP1130857A3 (fr) * 2000-03-01 2003-07-02 Mitsubishi Denki Kabushiki Kaisha Système de transmission par paquets dans communications mobiles
CN100444688C (zh) * 2005-08-08 2008-12-17 中兴通讯股份有限公司 移动性限制下的自助式漫游区域登记方法

Also Published As

Publication number Publication date
AU5036800A (en) 2001-01-09

Similar Documents

Publication Publication Date Title
US6611516B1 (en) Short message service support over a packet-switched telephony network
CA2375995C (fr) Mobilite a l'interieur d'un reseau telephonique commute par paquets
WO2000079825A1 (fr) Passerelle, systeme et procede servant a creer un support d'itinerance
US7633896B2 (en) Apparatus and method for enabling optimized gateway selection for inter-working between circuit-switched and internet telephony
US6519242B1 (en) Apparatus and method of PSTN based network roaming and SCP based subscriber management for internet telephony systems
US6654607B1 (en) Method and apparatus for enabling and monitoring mobile communication across platforms
US7317703B2 (en) H.323 user, service and service provider, mobility framework for the multimedia intelligent networking
EP1301056B1 (fr) Système pour fournir des services d'abonnés dans un réseau de télécommunication
US20020196775A1 (en) Routing a call between different types of networks
WO2000079814A1 (fr) Mobilite entre des reseaux de telephonie ip et des reseaux cellulaires
CA2229995A1 (fr) Architecture d'un systeme de communications mobile et procede d'acheminement
US7822416B2 (en) Methods and systems for allowing global roaming between devices supported by different protocols
CN1171479C (zh) 用于异构型网络之间的互操作性的虚拟编号方案
US20060193461A1 (en) Method and system for dynamically terminating wireless and wireline calls between carriers
JP4418136B2 (ja) 通信システム
US7403516B2 (en) Enabling packet switched calls to a wireless telephone user
US7062265B1 (en) Architecture to support service features for wireless calls in a wireless telecommunication system
EP1214858A1 (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
US20030119495A1 (en) Method and arrangement for controlling calls in a hybrid cellular telecommunication system
WO2000079815A1 (fr) Mobilite dans des reseaux de telephonie commutes par paquets
EP1089520A2 (fr) Structure H.323 de mobilité d' utilisateurs, de services et de fournisseurs de services pour le réseau multimédia intelligent
WO2001010086A1 (fr) Transmission de donnees dans un systeme de communications
WO2001039535A1 (fr) Procede et dispositif permettant de transmettre des informations entre des sous-systemes dans des systemes de telecommunication cellulaires hybrides
EP1279269A1 (fr) Procede et systeme d'etablissement de communication entre une premiere et une seconde entite de communication

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 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 NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG US UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW 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)
REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP