EP2050289B1 - Mécanisme d'identification des appels pour téléphones multiprotocoles - Google Patents

Mécanisme d'identification des appels pour téléphones multiprotocoles Download PDF

Info

Publication number
EP2050289B1
EP2050289B1 EP06848439.3A EP06848439A EP2050289B1 EP 2050289 B1 EP2050289 B1 EP 2050289B1 EP 06848439 A EP06848439 A EP 06848439A EP 2050289 B1 EP2050289 B1 EP 2050289B1
Authority
EP
European Patent Office
Prior art keywords
call
phone number
cellular
network
phone
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.)
Active
Application number
EP06848439.3A
Other languages
German (de)
English (en)
Other versions
EP2050289A4 (fr
EP2050289A1 (fr
Inventor
Paul Volkaerts
Paul Andrew Gelsthorpe
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.)
Cisco Technology Inc
Original Assignee
Cisco Technology Inc
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 Cisco Technology Inc filed Critical Cisco Technology Inc
Publication of EP2050289A1 publication Critical patent/EP2050289A1/fr
Publication of EP2050289A4 publication Critical patent/EP2050289A4/fr
Application granted granted Critical
Publication of EP2050289B1 publication Critical patent/EP2050289B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • 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/1225—Details of core network interconnection arrangements
    • H04M7/1235—Details of core network interconnection arrangements where one of the core networks is a wireless network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/54—Store-and-forward switching systems 
    • H04L12/56—Packet switching systems
    • H04L12/5691—Access to open networks; Ingress point selection, e.g. ISP selection
    • H04L12/5692—Selection among different networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/42025—Calling or Called party identification service
    • H04M3/42034—Calling party identification service
    • H04M3/42059—Making use of the calling party identifier
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/42195—Arrangements for calling back a calling subscriber
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M7/00—Arrangements for interconnection between switching centres
    • H04M7/0024—Services and arrangements where telephone services are combined with data services
    • H04M7/0057—Services where the data services network provides a telephone service in addition or as an alternative, e.g. for backup purposes, to the telephone service provided by the telephone services network
    • 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/128—Details of addressing, directories or routing tables
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/20—Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel

Definitions

  • This invention relates generally to cellular telephones and more particularly to cellular capable multi-protocol telephones.
  • GSM Global System for Mobile Communication
  • CDMA Code-Division Multiple Access
  • IP Internet Protocol
  • VoIP Voice over Internet Protocol
  • multi-protocol telephones have been developed that select which network is used to send or receive a phone call depending on network accessibility.
  • These multi-protocol telephones are generally provisioned with two different telephone numbers to facilitate use with a cellular network and an IP network.
  • IP network When an IP network is accessible, a call is made over the IP network from the VoIP phone number; otherwise the cellular network carries the call made from the cellular phone number.
  • FIG. 1 shows an example operation of a prior art multi-protocol phone 30.
  • the phone 30 has a cell phone number 96 and a VoIP phone number 97.
  • the call 98A travels over the cellular network 60.
  • the VoIP portion of the phone 30 is used to call endpoint B, the call 99 travels over the IP network 61.
  • Call-handling functions for the multi-protocol telephone 30 are facilitated by call-handling device 15 located at a VoIP service provider for phone 30.
  • the call-handling device 15 In order for the call-handling device 15 to provide these call-handling functions for an active incoming call, the incoming call to the multi-protocol phone 30 must be first received at the call-handling device 15. In other words, call-handling functions cannot be applied to incoming telephone calls directed to the cell phone number 96 for the multi-protocol telephone 30.
  • the call-handling device 15 provides Single Number Reach (SNR) functionality that is only available to incoming calls routed through the call-handling device 15.
  • SNR Single Number Reach
  • the cellular network 60 detects the telephone number 96 for the cellular portion of the multi-protocol telephone 30 and provides that originating telephone number 96 to the endpoint B via a Calling Line Identification (CLI) field.
  • CLI Calling Line Identification
  • a person at the called endpoint may then use the cellular telephone number 96 provided by the CLI field to make a return call 98B.
  • the return call 98B bypasses the call-handling device 15 and the multi-protocol phone 30 is denied call-handling features and SNR functionality for the duration of the returned call 98B.
  • One proposed partial solution requires all outbound mobile calls from the multi-protocol phone to automatically connect with the call-handling device at the VoIP service provider before being delivered to an endpoint.
  • a call-handling device phone number for the multiprotocol phone is included in a CLI field for the call.
  • the called party can then use the call- handling device phone number located in the CLI field to return the call to the call-handling device for the multi-protocol phone.
  • Solutions involving connecting all outbound calls to the call -handling device are expensive to deploy and generally require new hardware in the cell phone and/or the call handling device. For these and other reasons, such solutions generally have not been accepted by the industry.
  • Presentation CLI it is known that one can use Presentation CLI to allow an enterprise having several employees, each with their own direct telephone number, to make outbound calls that present a toll free "1-800" billing number for the enterprise in a CLI field of the outbound call.
  • a cellular network assigns the billing number to the CLI field of any calls from any of the employees' cellular telephones. This functionality allows the enterprise to mask the employees' telephone numbers so that returned calls are directed to a call center for the billing number.
  • the use of Presentation CLI has generally been limited to the above-described example.
  • multi-protocol telephones having cellular capability currently do not fully support SNR and do not fully integrate with call-handling functionality.
  • the disclosure that follows solves these and other problems.
  • US-A1-2004/0266415 describes a method and apparatus for providing selectable caller identification from a communication device coupled to a first and second communication infrastructure.
  • FIG. 2 is a diagram showing a system that leverages a Presentation Calling Line Identification (CLI) table so that all calls from a multi-protocol phone are identified by a call-handling device phone number.
  • CLI Presentation Calling Line Identification
  • IP call 79 originating from a Voice over IP (VoIP) portion of multi-protocol phone 30 is routed through call-handling device 15.
  • IP call 79 identifies the phone number 95 for call-handling device 15 to endpoint B so that return calls are sent back to call-handling device 15.
  • cellular call 78A when cellular call 78A is sent from the cellular portion of multi-protocol phone 30, the phone number 95 for call-handling device 15 is also identified to endpoint B.
  • Cellular network 60 receives the cellular call 78A and a call identification mechanism 21 includes call-handling device phone number 95 in a Calling Line Identification (CLI) field for the call 78A.
  • CLI Calling Line Identification
  • endpoint B When endpoint B returns the call 78A, the return call 78B is directed to the phone number 95 identified in call 78A. Therefore, return calls for both the IP and the cellular call are directed to call-handling device 15 so that call-handling functions and Single Number Reach (SNR) functions may be provided for all return calls.
  • SNR Single Number Reach
  • FIG. 3 is a detailed diagram showing the call identification mechanism 21 having a processor 50, a memory 49 and a Presentation CLI table 22.
  • the mechanism 21 leverages the Presentation CLI table 22 to associate cellular phone numbers with IP device phone numbers for IP devices such as call-handling device 15. Accordingly, calls made by a cellular phone identify an IP device phone number in a CLI field 25 rather than a cell phone number.
  • the memory 49 includes instructions that, when executed by the processor 50, perform the functions described in the flowcharts of FIG. 4 .
  • the Presentation CLI table 22 associates the cellular phone number 96 with the phone number 95 for the IP device 15.
  • the IP device 15 is a call-handling device 15 located at a VoIP service provider for multi-protocol phone 30.
  • the IP device 15 may be a call manager or any device having a local SNR application.
  • phone number 95 may be the same as phone number 97 for the VoIP portion of multi-protocol phone 30 while in other embodiments phone number 95 and phone number 97 are different.
  • the device 15 may operate according to protocols for other networks besides IP networks such as Integrated Services Digital Networks (ISDNs) or any other public or private networks used to carry phone calls.
  • ISDNs Integrated Services Digital Networks
  • the IP device 15 may receive incoming calls and then communicate with a local SNR application such as Cisco Mobility Manager or Mobile Connect to determine which of telephone numbers 96 or 97 should receive the call. For example, during the working hours of day the SNR application may direct all calls to the VoIP telephone number 97. At all other times of day, the SNR application may direct all calls to the cell phone number 96.
  • a local SNR application such as Cisco Mobility Manager or Mobile Connect to determine which of telephone numbers 96 or 97 should receive the call.
  • the SNR application may direct all calls to the VoIP telephone number 97.
  • the SNR application may direct all calls to the cell phone number 96.
  • the call-handling device 15 may move an active call from the cellular network 60 to a public or private IP network mid-call based on WiFi accessibility with an IP network to reduce call costs and add call features for the call.
  • Other call-handling functions may be provided by the IP device 15.
  • multi-protocol phone 30 includes VoIP capability and WiFi capability in addition to cellular capability.
  • the multi-protocol phone 30 may also include Signaling System 7 (SS7) capability, ISDN capability, Publicly Switched Telephone Network (PSTN) capability, etc. in addition to cellular capability.
  • SS7 Signaling System 7
  • PSTN Publicly Switched Telephone Network
  • mechanism 21 When call 24 is received by the cellular network 60, mechanism 21 identifies an origination source for the call 24 as cell phone number 96 associated with person D. Next, mechanism 21 accesses Presentation CLI table 22 to determine a call-handling device telephone number 95 to be included in the CLI field 25 for call 24. According to the Presentation CLI table 22, the mechanism 21 includes the call-handling device phone number 95 in the CLI field 25 of call 24. In other embodiments, the mechanism 21 identifies the call-handling device 15 as the calling party by using any other method such as Automatic Number Identification (ANI).
  • ANI Automatic Number Identification
  • the table 22 may include other entries such as an entry for person E having a different multi-protocol phone.
  • the Presentation CLI table 22 may be a database or a profile.
  • endpoint B When endpoint B receives the call 24, the CLI field 25 may be accessed to determine a calling party. Endpoint B determines that the calling party may be reached at telephone number 95. Thus, when a user at endpoint B returns the call 24, the return call 26A is received at the call-handling device 15 having the phone number 95.
  • the call-handling device 15 communicates with a local SNR application to determine whether the return call 26A should be directed to cell phone number 96 or VoIP phone number 97.
  • the SNR application indicates that return calls should be received at cell phone number 96
  • the return call 26B is transmitted over the cellular network 60 to multi-protocol phone 30.
  • return call 26C is transmitted over the IP network to multi-protocol phone 30.
  • the return call 26B is finally received at multi-protocol phone 30.
  • the call path for the return call 26A/26B extends through call-handling device 15; therefore, the return call 26A/26B may later be switched between cellular and IP networks mid-call by call-handling device 15. For example, when person D arrives in range of a WiFi network wirelessly coupled to the call-handling device 15, the return call 26A/26B may be partly or completely moved from the cellular network 60 to an IP network. Similarly, the call path for return call 26A/26C also extends through call-handling device 15 and therefore can be moved between cellular and IP networks mid-call.
  • FIG. 4 is a flowchart showing how the call identification mechanism 21 in FIG. 3 provides a call-handling device phone number for calls originating from a cellular phone number.
  • the mechanism 21 in block 401 associates a cell phone number for a multi-protocol phone with an IP device phone number in a Presentation CLI table.
  • a call is placed from a multi-protocol phone having a cellular portion and a VoIP portion.
  • the call is sent from the VoIP portion of the phone in block 403A.
  • the VoIP call is then routed through an IP device and thus the VoIP call identifies a phone number for the IP device.
  • the call is placed from the cellular portion of the multi-protocol phone in block 403B.
  • a cellular network receives the cellular call and determines an originating phone number for the call.
  • the mechanism 21 compares the originating phone number to the Presentation CLI table to determine the associated IP device phone number in block 405.
  • the mechanism 21 includes the associated IP device phone number in a CLI field for the cellular call.
  • the system described above can use dedicated processor systems, micro controllers, programmable logic devices, or microprocessors that perform some or all of the operations. Some of the operations described above may be implemented in software and other operations may be implemented in hardware.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • General Engineering & Computer Science (AREA)
  • Telephonic Communication Services (AREA)
  • Mobile Radio Communication Systems (AREA)

Claims (15)

  1. Procédé, comprenant :
    l'établissement d'un appel depuis une partie de protocole Internet, IP, (97) d'un téléphone mobile (30) quand un réseau IP (61) est accessible en mode sans fil par le téléphone mobile (30), ledit appel passant par un dispositif IP (15) distinct du téléphone mobile et sur le réseau IP (61) ;
    l'identification d'un numéro de téléphone (95) du dispositif IP (15) en tant que partie appelante de l'appel quand l'appel est établi sur le réseau IP (61) ;
    l'établissement de l'appel (24) depuis une partie cellulaire (96) du téléphone mobile (30) quand le réseau IP (61) n'est pas accessible en mode sans fil par le téléphone mobile, ledit appel court-circuitant le dispositif IP (15) et étant établi sur un réseau cellulaire (60) ; et
    l'identification du numéro de téléphone de dispositif IP (95) en tant que partie appelante de l'appel en incluant le numéro de téléphone de dispositif IP (95) dans un champ d'identifiant de ligne appelante, CLI, (25) de l'appel (24) quand l'appel court-circuite le dispositif IP (15) et est établi sur le réseau cellulaire (60).
  2. Procédé selon la revendication 1 dans lequel le numéro de téléphone de dispositif IP (95) est identifié en tant que partie appelante en réponse à une détermination qu'un numéro de téléphone cellulaire de départ (96) de la partie cellulaire du téléphone mobile est associé au numéro de téléphone de dispositif IP dans une table d'identification de lignes appelantes (CLI) de présentation (22).
  3. Procédé selon la revendication 2 comprenant en outre :
    la réception d'un appel de retour au numéro de téléphone de dispositif IP (95) ; et
    l'envoi de l'appel de retour sur le réseau cellulaire (60) au numéro de téléphone cellulaire (96) quand le téléphone mobile n'est pas accessible en mode sans fil sur le réseau IP (61).
  4. Procédé selon la revendication 3 comprenant en outre le passage de l'appel de retour du réseau cellulaire (60) au réseau IP (61) quand le téléphone mobile (30) devient accessible en mode sans fil sur le réseau IP.
  5. Procédé selon la revendication 4 comprenant en outre :
    la composition de l'appel de retour en utilisant le numéro de téléphone de dispositif IP (95) qui est identifié en tant que partie appelante ; et
    la connexion de l'appel de retour au numéro de téléphone cellulaire (96).
  6. Procédé selon la revendication 5 dans lequel la table CLI de présentation (22) comporte des entrées associant des numéros de téléphone d'une pluralité de téléphones à protocole unique différents à un même numéro de téléphone de facturation.
  7. Procédé, comprenant :
    l'analyse d'un appel qui arrive dans un réseau cellulaire (60) pour déterminer qu'un numéro de téléphone cellulaire (96) correspond à une source de départ de l'appel, la source de départ comprenant un téléphone cellulaire (30) ;
    la comparaison (405) dudit numéro de téléphone cellulaire à une table (22) pour déterminer un numéro de téléphone de dispositif de protocole Internet, IP, (95) de l'appel, dans lequel le dispositif IP (15) est distinct du téléphone cellulaire (30) ; et
    la fourniture (406) du numéro de téléphone de dispositif IP en tant que partie appelante en incluant le numéro de téléphone de dispositif IP (95) dans un champ d'identifiant de ligne appelante, CLI, (25) de l'appel (24) pour cacher le numéro de téléphone cellulaire à un point d'accès.
  8. Procédé selon la revendication 7 comportant en outre le renvoi d'un appel de retour du numéro de téléphone de dispositif IP au numéro de téléphone cellulaire sur le réseau cellulaire (60).
  9. Procédé selon la revendication 8 comportant en outre le transfert de l'appel de retour du réseau cellulaire (60) à un réseau IP (61) quand l'appel de retour est en cours.
  10. Procédé selon la revendication 7 dans lequel la table est une table d'identification de lignes appelantes (CLI) de présentation (22) qui comporte des entrées associant des numéros de téléphone d'une pluralité de numéros de téléphone différents de téléphones à protocole unique à un même numéro de téléphone sans frais.
  11. Procédé selon la revendication 7 dans lequel le numéro de téléphone cellulaire correspond à un téléphone multiprotocoles (30) qui effectue des appels conformément à la fois au protocole IP et au système GSM (système mondial de communications mobiles) ou au système CDMA (accès multiple par répartition en code).
  12. Système, comprenant :
    un moyen d'analyse d'un appel arrivant dans un réseau cellulaire (60) pour déterminer qu'un numéro de téléphone cellulaire (96) correspond à une source de départ de l'appel, la source de départ comprenant un téléphone cellulaire (30) ;
    un moyen de comparaison dudit numéro de téléphone cellulaire (96) à une table (22) pour déterminer un numéro de téléphone de dispositif IP associé (95) de l'appel, dans lequel le dispositif IP (15) est distinct du téléphone cellulaire (30) ; et
    un moyen de fourniture du numéro de téléphone de dispositif IP (95) en tant que partie appelante en incluant le numéro de téléphone de dispositif IP (95) dans un champ d'identifiant de ligne appelante, CLI, (25) de l'appel (24) pour cacher le numéro de téléphone cellulaire à un point d'accès.
  13. Système comprenant :
    un moyen d'établissement d'un appel depuis une unité IP (97) d'un téléphone mobile (30) quand un réseau IP (61) est accessible en mode sans fil par le téléphone mobile (30), ledit appel passant par un dispositif IP (15) distinct du téléphone mobile et sur le réseau IP (61) ;
    un moyen d'identification d'un numéro de téléphone (95) du dispositif IP (15) en tant que partie appelante de l'appel quand l'appel est établi sur le réseau IP (61) ;
    un moyen d'établissement dudit appel (24) depuis une unité cellulaire (96) du téléphone mobile (30) quand le réseau IP (61) n'est pas accessible en mode sans fil par le téléphone mobile, ledit appel court-circuitant le dispositif IP (15) et étant établi sur un réseau cellulaire (60) ; et
    un moyen d'identification du numéro de téléphone de dispositif IP (95) en tant que partie appelante de l'appel en incluant le numéro de téléphone de dispositif IP (95) dans un champ d'identifiant de ligne appelante, CLI, (25) de l'appel (24) quand l'appel court-circuite le dispositif IP (15) et est établi sur le réseau cellulaire (60).
  14. Système selon la revendication 12 ou 13 agencé pour exécuter un procédé selon l'une quelconque des revendications 1 à 11.
  15. Programme informatique, produit de programme informatique ou support lisible par ordinateur comprenant des instructions qui, à leur exécution par un ordinateur, amènent l'ordinateur à mettre en oeuvre les étapes du procédé selon l'une quelconque des revendications 1 à 11.
EP06848439.3A 2006-07-13 2006-12-06 Mécanisme d'identification des appels pour téléphones multiprotocoles Active EP2050289B1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US11/457,434 US8054828B2 (en) 2006-07-13 2006-07-13 Call identification mechanism for multi-protocol telephones
PCT/US2006/061673 WO2008008093A1 (fr) 2006-07-13 2006-12-06 Mécanisme d'identification des appels pour téléphones multiprotocoles

Publications (3)

Publication Number Publication Date
EP2050289A1 EP2050289A1 (fr) 2009-04-22
EP2050289A4 EP2050289A4 (fr) 2012-03-07
EP2050289B1 true EP2050289B1 (fr) 2018-09-26

Family

ID=38923530

Family Applications (1)

Application Number Title Priority Date Filing Date
EP06848439.3A Active EP2050289B1 (fr) 2006-07-13 2006-12-06 Mécanisme d'identification des appels pour téléphones multiprotocoles

Country Status (3)

Country Link
US (1) US8054828B2 (fr)
EP (1) EP2050289B1 (fr)
WO (1) WO2008008093A1 (fr)

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9985817B2 (en) * 2006-11-14 2018-05-29 Tp Lab, Inc. System and method for a universal phone number service
US20100115567A1 (en) * 2008-10-30 2010-05-06 Shekhar Gupta System and method for pausing programming of a television for a telephone call
US20100115568A1 (en) * 2008-10-30 2010-05-06 Shekhar Gupta System and method for altering the display of television content in response to user preferences
US9008039B2 (en) 2010-12-17 2015-04-14 Verizon Patent And Licensing Inc. Mobile phone/docking station call continuity
US9736665B2 (en) * 2010-12-17 2017-08-15 Verizon Patent And Licensing Inc. Original calling identification with mobile phone in docked mode
EP2613508B1 (fr) * 2012-01-06 2015-09-23 BlackBerry Limited Système de communication fournissant des fonctions d'identification de l'appelant basé sur une communication de champ proche et procédés apparentés
US9413867B2 (en) 2012-01-06 2016-08-09 Blackberry Limited Communications system providing caller identification features based upon near field communication and related methods
JP6021836B2 (ja) 2014-02-25 2016-11-09 Ｌｉｎｅ株式会社 通信サーバ

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CA2254393C (fr) 1997-12-16 2002-02-26 David R. Glass Methode et appareil pouvant fournir le pseudonyme d'identification du numero demandeur dans un systeme de communications
US20020118800A1 (en) * 1998-08-27 2002-08-29 Maria Martinez Telecommunication systems and methods therefor
US6711146B2 (en) 1999-02-22 2004-03-23 Genesys Telecommunications Laboratories, Inc. Telecommunication system for automatically locating by network connection and selectively delivering calls to mobile client devices
US6895002B2 (en) * 2001-02-21 2005-05-17 Intel Corporation Method and system to provide a single telephone number for geographically dispersed telephony service subscribers
US7640009B2 (en) * 2003-06-30 2009-12-29 Motorola, Inc. Method and apparatus to provide a selectable caller identification
US20060077957A1 (en) * 2004-10-08 2006-04-13 Umamaheswar Reddy Call handoff between subscriber's multiple devices associated with multiple networks
WO2006077587A2 (fr) * 2005-01-21 2006-07-27 Convergin Israel Ltd. Convergence de services dans plusieurs domaines de communication
US8345624B2 (en) * 2006-01-05 2013-01-01 At&T Intellectual Property I, Lp Methods and apparatus to provide extended voice over internet protocol (VoIP) services

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None *

Also Published As

Publication number Publication date
US8054828B2 (en) 2011-11-08
US20090028130A1 (en) 2009-01-29
WO2008008093A1 (fr) 2008-01-17
EP2050289A4 (fr) 2012-03-07
EP2050289A1 (fr) 2009-04-22

Similar Documents

Publication Publication Date Title
EP2050289B1 (fr) Mécanisme d'identification des appels pour téléphones multiprotocoles
US9232067B2 (en) Systems and methods to direct a mobile communication device to a preferred teleconference bridge
US8059805B2 (en) Enhanced services provided using communication redirection and processing
US7742578B1 (en) Location determination capabilities for emergency call services
US9497228B2 (en) Class 4 long distance softswitch network with integrated class 5 application services
KR20090098969A (ko) 네트워크들 간의 호출에 식별 데이터를 링크시키기 위한 방법 및 장치
US9497606B1 (en) Native dialer fall-back
CN101945187B (zh) 将固话分机与移动终端进行绑定的方法和系统
US8582748B2 (en) Method and system for communication forwarding
WO2008154537A3 (fr) Approvisionnement d'un exploitant de réseau mobile virtuel (mvno) et routage de messagerie vocale par un facilitateur de réseau virtuel mobile (mvne)
EP3745694B1 (fr) Procédé et système de télécommunication permettant d'établir un appel par l'intermédiaire d'au moins un réseau de télécommunications à l'aide de plusieurs numéros d'appel
US7983407B2 (en) Calling party number override for emergency services
CN101027917A (zh) 智能网方式中个性化回铃音呼叫保护的方法及装置
US6834105B2 (en) Method for operating a private telecommunications network
US20070189492A1 (en) Peering network for parameter-based routing of special number calls
CA2619321C (fr) Autocommutateur prive qui fournit des communications de depart pour un terminal a distance en presence d'une application d'une tierce partie
CN101150784B (zh) 处理由专用小交换机向移动无线电网交换的连接的方法
FI119139B (fi) Menetelmä matkapuhelinvaihteessa
FI117034B (fi) Menetelmä jonotuspalvelun toteuttamiseksi
US20070121876A1 (en) System for managing the transfer of a call waiting party into an existing subscriber call connection to replace a terminal device on the existing call connection
US20070121877A1 (en) System for managing the addition of a call waiting party to an existing subscriber call connection
FI118915B (fi) Järjestelmä
SE524946C2 (sv) Ett för telekommunikation anpassat system

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

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR

AX Request for extension of the european patent

Extension state: AL BA HR MK RS

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 84/00 20090101AFI20090330BHEP

A4 Supplementary search report drawn up and despatched

Effective date: 20120207

RIC1 Information provided on ipc code assigned before grant

Ipc: H04M 7/00 20060101ALI20120201BHEP

Ipc: H04M 3/42 20060101AFI20120201BHEP

Ipc: H04M 7/12 20060101ALI20120201BHEP

DAX Request for extension of the european patent (deleted)
17Q First examination report despatched

Effective date: 20171019

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602006056457

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04W0084000000

Ipc: H04M0003420000

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

RIC1 Information provided on ipc code assigned before grant

Ipc: H04M 3/42 20060101AFI20180322BHEP

Ipc: H04L 12/54 20060101ALI20180322BHEP

Ipc: H04M 7/00 20060101ALI20180322BHEP

Ipc: H04M 7/12 20060101ALI20180322BHEP

Ipc: H04W 4/20 20090101ALN20180322BHEP

INTG Intention to grant announced

Effective date: 20180419

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

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

Owner name: CISCO TECHNOLOGY, INC.

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1047413

Country of ref document: AT

Kind code of ref document: T

Effective date: 20181015

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602006056457

Country of ref document: DE

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20180926

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180926

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181227

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180926

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181226

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180926

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180926

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1047413

Country of ref document: AT

Kind code of ref document: T

Effective date: 20180926

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180926

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180926

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180926

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190126

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180926

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180926

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180926

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180926

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180926

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180926

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190126

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602006056457

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180926

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

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

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20181206

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180926

26N No opposition filed

Effective date: 20190627

REG Reference to a national code

Ref country code: IE

Ref legal event code: MM4A

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20181231

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180926

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20181206

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20181231

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20181231

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20181231

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180926

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180926

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20061206

P01 Opt-out of the competence of the unified patent court (upc) registered

Effective date: 20230525

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20231222

Year of fee payment: 18

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20231226

Year of fee payment: 18

Ref country code: DE

Payment date: 20231212

Year of fee payment: 18