|Publication number||US7899465 B1|
|Application number||US 10/148,775|
|Publication date||Mar 1, 2011|
|Filing date||Dec 7, 1999|
|Priority date||Dec 7, 1999|
|Also published as||CN1381125A, DE69930972D1, DE69930972T2, EP1238514A1, EP1238514B1, WO2001043395A1|
|Publication number||10148775, 148775, PCT/1999/9593, PCT/EP/1999/009593, PCT/EP/1999/09593, PCT/EP/99/009593, PCT/EP/99/09593, PCT/EP1999/009593, PCT/EP1999/09593, PCT/EP1999009593, PCT/EP199909593, PCT/EP99/009593, PCT/EP99/09593, PCT/EP99009593, PCT/EP9909593, US 7899465 B1, US 7899465B1, US-B1-7899465, US7899465 B1, US7899465B1|
|Inventors||Nedko Ivanov, Simo Veikkolainen|
|Original Assignee||Nokia Corporation|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (33), Non-Patent Citations (1), Referenced by (5), Classifications (43), Legal Events (3)|
|External Links: USPTO, USPTO Assignment, Espacenet|
This is a U.S. national stage of PCT application No. PCT/EP99/09593, filed on Dec. 7, 1999. Priority is claimed on that application.
The present invention relates to the usage of subscriber location information in a mobile Internet protocol (IP) telephony network. In particular, the present invention relates to a method and a system for performing routing using location information of an IP terminal in a mobile IP telephony network.
In conventional mobile circuit switched networks like GSM (Global System for Mobile communications) the location information of a mobile station is indicated to the network by a BSS (Base Station System). In a mobile IP telephony network, the mobile IP related services may be totally transparent to the underlying access network like GPRS (General Packet Radio Service) so that the access network has no means to provide any location information to the mobile IP telephony core network. Therefore, whenever there is a need for a mobile subscriber's location information in an IP telephony network, the location information (e.g. Cell ID) is not necessarily shown to the application that could have some use for it.
Therefore, it is an object of the present invention to improve application functionality in a mobile IP telephony network.
According to one aspect of the present invention, this object is achieved by a system for performing routing using location information of an IP terminal in a mobile IP telephony network. This system comprises an IP terminal as a subscriber of the mobile IP telephony network and a control unit as shown in
A call control application in the IP terminal obtains the location information of the IP terminal by communicating with a mobile terminal MT connected thereto. The call control application in the IP terminal may request the location information like a Cell ID from the mobile terminal.
The call originated from the IP terminal may be directed to a special service number which requires the location information of the IP terminal. In this case, the control unit maps the special service number or alias to a subscriber or destination address on the basis of the location information.
According to another aspect of the present invention, the above-mentioned object is achieved by a method for performing routing using location information of an IP terminal in a mobile IP telephony network.
In a first step, a call is originated from an IP terminal of the mobile IP telephony network to another subscriber. In the next step, it is checked whether location information of the IP terminal is required for this call. When location information is required, the step of adding location information to call setup data follows. Then a subscriber or destination address is determined on the basis of the call setup data and the location information. If no location information is required, no location information is added to the call setup data and the subscriber address is determined on the basis of the call setup data alone. After the destination address has been determined, the call is routed to the determined destination address.
The location information may be provided by a communication between a call control application in the IP terminal and a dedicated mobile terminal MT.
According to a further aspect of the present invention, the object is achieved by an IP terminal in a system for performing routing using location information of the IP terminal in a mobile IP telephony network. The IP terminal is adapted to originate a call to another subscriber, wherein the IP terminal checks whether location information of the IP terminal is required for the call and adds location information to call setup data when required.
Moreover, according to a still further aspect of the present invention, the object is achieved by a control unit in a system for performing routing using location information of an IP terminal in a mobile IP telephony network. The control unit receives a call originated from an IP terminal to another subscriber together with call setup data comprising location information of the IP terminal. Then, the control unit determines a subscriber or destination address on the basis of the call setup data and the location information and routes the call to the determined destination address.
With the present invention, the application functionality in a mobile IP telephony network can be improved.
According to the present invention, subscriber location information can be obtained on request or automatically from a mobile terminal associated with the subscriber like an IP terminal. The location information can be used for a location based routing to a special subscriber or number.
In the following the present invention will be described by way of preferred embodiments thereof with reference to the accompanying drawings.
In the following, a first embodiment of the present invention will be described with reference to
The application knows that it has to get the location information of the IPTE for this call. The location information is obtained from a mobile terminal MT through an interface between the mobile aware H.323 application and the MT. Hence, in a message 3, the H.323 application inquires the MT for the current Cell ID indicating the location of the IPTE. Thereupon, in a message 4, the MT returns the Cell ID.
The location information is passed to the CSCF as part of the Setup message 5. In the message 5, the subscriber IPTE sends the Setup message to the CSCF with the special alias as destinationAddress and the Cell ID in the nonStandardData field (or in a dedicated field) in the user to user information element (UUIE) of the Setup message. Now, the CSCF has the necessary information (the alias like PizzaHut.hu and the Cell ID) in order to do the alias translation to an E.164 or alias of the nearest office or subscriber to the area where the subscriber IPTE is located. In other words, in step 6 in
In a message 7, the CSCF sends the Setup message with the new E.164 number as called party number to a Media Gateway Control Function (MGCF). Thereupon, the MGCF converts the H.323 Setup message to an Initial Address Message(IAM) carried over Sigtran and, in a message 8, sends the IAM to a Transport Signaling Gateway (T-SGW), the IAM including the new E.164 number. The T-SGW converts the Sigtran IAM to an SS7 IAM and sends it to a local exchange according to message 9. In a message 10, the local exchange initiates a call setup towards a local PizzaHut office.
When the called subscriber (the local PizzaHut office) answers the call, it sends a Connect message (message 11) to the local exchange and the local exchange acknowledges with a Connect Acknowledge (message 11). In a message 12, the local exchange sends an SS7 Answer Message (ANM) corresponding to the Connect message to the T-SGW. The T-SGW converts the SS7 ANM to a Sigtran ANM and sends it to the MGCF in a message 13. Finally, in a message 14, the MGCF sends a Connect message corresponding to the Sigtran ANM to the IPTE via the CSCF. At this point, both ways communication is possible between the subscriber IPTE and the called subscriber, i.e. the local PizzaHut office.
After the conversation is over and one of the parties hangs up (in this case the local PizzaHut office), a Disconnect message 15 (
In the following, a second embodiment of the present invention will be described with reference to
In an emergency call case, the first message is an implicit request for the mobile terminal MT to provide the location information to the application. In other words, when a user of an IP terminal IPTE in a mobile IP telephony network initiates an emergency call by pressing for example an EC button on his H.323 application, the application itself first notifies the MT and requests an EC Packet Data Protocol (PDP) context establishment in a message 1, GPRS access being assumed.
In a message 2, the MT sends an activate EC PDP context request to an enhanced serving GPRS support node (E-SGSN) in order to create an access to the mobile IP telephony network. It is to be noted that the EC PDP context has to use a high priority and guaranteed bandwidth quality of service (QoS). The E-SGSN sends a create EC PDP context request to an enhanced gateway GPRS support node (E-GGSN) identified by an access point name (APN) pointing to the mobile IP telephony network in a message 3. After the E-GGSN has created the EC PDP context, in a message 4 it sends a response to the E-SGSN.
In a message 5, the E-SGSN indicates acceptance of the request from the MT for the EC PDP context activation. After the EC PDP context has been established, the MT sends the Cell ID to the H.323 application in a message 6 in order to put it in the nonStandardData field (or in a dedicated field) in the user to user information element (UUIE) of the Emergency Setup message.
Now that the IPTE has a high priority access to the mobile IP telephony network, it has to discover a CSCF which can serve its request. To be precise, due to the fact that the application may not know of any available CSCFs in the network, it has to perform a gatekeeper discovery procedure using H.323. Therefore, in a message 7, the IPTE sends a Gatekeeper Request (GRQ) message with an indication in the nonStandardData field (or in a dedicated field) that it requires the H.225.0 call signalling TA in a Gatekeeper Confirm(GCF) message.
All the CSCFs which can serve the IPTE have to reply with a GCF message including their H.225.0 call signalling TA in the nonStandardData field (or in a dedicated field) of the GCF message in a message 8. Since this is an emergency call, registration (registration request (RRQ), registration confirm (RCF)) and admission (ARQ, ACF) are not required. The IPTE also knows the H.225.0 call signalling TA from the GCF message so it can start sending a call control signaling. In a message 9, the IPTE sends an Emergency Setup message to the CSCF with the Cell ID in the nonStandardData field (or in a dedicated field) as part of the UUIE.
In step 10 in
The messages following the message 11, i.e. the messages 12 to 22, correspond to the messages 8 to 18 described in the first embodiment in connection with
According to a message 23 in
Since the IPTE had activated a high priority and guaranteed bandwidth QoS PDP context for which it does not have to pay due to the EC nature, after the call has been released, the H.323 application sends a release notification to the MT in a message 24, so that the MT can deactivate the above-mentioned PDP context. In a message 25, a normal user initiated PDP Context Deactivation procedure is performed. Finally, the MT acknowledges the EC PDP Context deactivation in a message 26.
With the present invention, the application functionality in a mobile IP telephony network can be improved.
According to the present invention, subscriber location information can be obtained on request or automatically from the mobile terminal residing in an IP terminal. The location information can be used for a location based routing to a special number or alias.
While the invention has been described with reference to a preferred embodiment, the description is illustrative of the invention and is not to be construed as limiting the invention. Various modifications and applications may occur to those skilled in the art without departing from the true spirit and scope of the invention as defined by the appended claims.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US5440541 *||Jul 29, 1993||Aug 8, 1995||Fujitsu Limited||System and method for establishing communications between subscribers based on personal number assigned to each subscriber|
|US5479482 *||Sep 26, 1994||Dec 26, 1995||At&T Corp.||Cellular terminal for providing public emergency call location information|
|US5946618 *||Apr 10, 1997||Aug 31, 1999||Qualcomm Incorporated||Method and apparatus for performing position-based call processing in a mobile telephone system using multiple location mapping schemes|
|US5963861 *||Apr 5, 1996||Oct 5, 1999||Lucent Technologies Inc.||Dealer-locator service and apparatus for mobile telecommunications system|
|US5999536 *||Nov 24, 1997||Dec 7, 1999||Anritsu Corporation||Router for high-speed packet communication between terminal apparatuses in different LANs|
|US6067529 *||Aug 12, 1998||May 23, 2000||Ericsson Inc.||System and method for sending a short message containing purchase information to a destination terminal|
|US6075783 *||Mar 6, 1997||Jun 13, 2000||Bell Atlantic Network Services, Inc.||Internet phone to PSTN cellular/PCS system|
|US6115600 *||Dec 21, 1995||Sep 5, 2000||Nokia Telecommunications Oy.||Method for improving charging criteria in a mobile telephone network|
|US6272129 *||Jan 19, 1999||Aug 7, 2001||3Com Corporation||Dynamic allocation of wireless mobile nodes over an internet protocol (IP) network|
|US6304753 *||Jul 16, 1998||Oct 16, 2001||Openwave Technologies Inc.||Integration of voice and data services provided to a mobile wireless device|
|US6311055 *||Oct 2, 1997||Oct 30, 2001||Ericsson Inc||System and method for providing restrictions on mobile-originated calls|
|US6330453 *||Feb 4, 1999||Dec 11, 2001||Matsushitas Electric Industrial Co., Ltd.||Map information providing method and system and terminal device used therein|
|US6356761 *||Aug 24, 1998||Mar 12, 2002||Telefonaktiebolaget Lm Ericsson (Publ)||Method and arrangement for finding information|
|US6374108 *||Nov 30, 1999||Apr 16, 2002||Motorola, Inc.||Assigning an IP address to a mobile station while roaming|
|US6377810 *||Jun 11, 1999||Apr 23, 2002||Motorola, Inc.||Method of operation of mobile wireless communication system with location information|
|US6466571 *||Jan 19, 1999||Oct 15, 2002||3Com Corporation||Radius-based mobile internet protocol (IP) address-to-mobile identification number mapping for wireless communication|
|US6549625 *||Jun 24, 1999||Apr 15, 2003||Nokia Corporation||Method and system for connecting a mobile terminal to a database|
|US6584098 *||Aug 14, 1998||Jun 24, 2003||British Telecommunications Public Limited Company||Telecommunications system|
|US6591306 *||Jul 21, 1999||Jul 8, 2003||Nec Corporation||IP network access for portable devices|
|US6600735 *||Mar 1, 1999||Jul 29, 2003||Hitachi, Ltd.||Internet telephone connection method, bandwidth controller and gate keeper|
|US6611516 *||Jun 21, 1999||Aug 26, 2003||Nokia Telecommunications Oyj||Short message service support over a packet-switched telephony network|
|US6650902 *||Nov 15, 1999||Nov 18, 2003||Lucent Technologies Inc.||Method and apparatus for wireless telecommunications system that provides location-based information delivery to a wireless mobile unit|
|US6677894 *||Nov 30, 1998||Jan 13, 2004||Snaptrack, Inc||Method and apparatus for providing location-based information via a computer network|
|US6693894 *||Jan 12, 1999||Feb 17, 2004||Telefonaktiebolaget Lm Ericsson (Pulb)||Communications network and method for directly routing calls to mobile subscribers using an internet protocol network|
|US6717937 *||Dec 23, 1998||Apr 6, 2004||Nortel Networks Limited||Method and apparatus for voice over internet protocol resource management|
|US6728215 *||Dec 30, 1998||Apr 27, 2004||Ericsson Inc.||System and method for placing wireless calls on an internet protocol based local area network based upon quality of service conditions|
|US6731621 *||Mar 3, 1999||May 4, 2004||Hitachi, Ltd.||Mobil communication system for providing IP packet communications and method for routing IP packets|
|US6765920 *||Oct 29, 1999||Jul 20, 2004||Mitsubishi Materials Corporation||Network address converting apparatus and storage medium|
|US6876634 *||Jul 8, 1999||Apr 5, 2005||Lg Information & Communications, Ltd.||Architecture of mobile communication systems network and method for transmitting packet data using the same|
|EP0800320A2||Mar 25, 1997||Oct 8, 1997||Lucent Technologies Inc.||Dealer-locator service and apparatus for a mobile telecommunications system|
|EP0817444A2||Jun 30, 1997||Jan 7, 1998||Sun Microsystems, Inc.||System for context-dependent name resolution|
|JPH1051859A||Title not available|
|JPH10126445A||Title not available|
|1||Office Action issued by the Chinese Patent Office on Nov. 6, 2009 for Chinese Patent Application No. 200610107458.2.|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US9178742 *||Mar 21, 2006||Nov 3, 2015||Cisco Technology, Inc.||System and method for maintaining a provisioned configuration for an endpoint in a communications network|
|US9485061 *||Jul 15, 2013||Nov 1, 2016||Samsung Electronics Co., Ltd.||Communication system with flexible repeat-response mechanism and method of operation thereof|
|US20070223446 *||Mar 21, 2006||Sep 27, 2007||Mcmenamy Kevin R||System and method for maintaining a provisioned configuration for an endpoint in a communications network|
|US20120189002 *||Apr 2, 2012||Jul 26, 2012||Todd Poremba||Protocol Converting 9-1-1 Emergency Messaging Center|
|US20140105127 *||Jul 15, 2013||Apr 17, 2014||Samsung Electronics Co., Ltd.||Communication system with flexible repeat-response mechanism and method of operation thereof|
|U.S. Classification||455/456.1, 455/428, 455/414.1, 370/395.52|
|International Classification||H04W4/02, H04W76/00, H04W4/20, H04L29/08, H04L12/56, H04W4/22, H04W8/08, H04W92/02, H04W80/04, H04W76/02, H04L29/12, H04L29/06, H04M3/00, H04W24/00|
|Cooperative Classification||H04L65/1069, H04L29/12783, H04W76/02, H04W76/007, H04L29/06027, H04W4/20, H04W80/04, H04W4/22, H04L61/35, H04W4/02, H04W92/02, H04W8/085, H04L29/12009, H04L67/16, H04L67/14, H04L67/18|
|European Classification||H04L29/08N17, H04L29/06M2S1, H04L29/12A, H04L29/12A6, H04L29/08N15, H04L29/08N13, H04W4/02, H04W4/20, H04L61/35|
|Aug 29, 2002||AS||Assignment|
Owner name: NOKIA CORPORATION, FINLAND
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:IVANOV, NEDKO;VEIKKOLAINEN, SIMO;SIGNING DATES FROM 20020715 TO 20020808;REEL/FRAME:013843/0139
|Aug 6, 2014||FPAY||Fee payment|
Year of fee payment: 4
|May 12, 2015||AS||Assignment|
Owner name: NOKIA TECHNOLOGIES OY, FINLAND
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:NOKIA CORPORATION;REEL/FRAME:035615/0763
Effective date: 20150116