Source: https://patents.google.com/patent/WO2013128178A1/en
Timestamp: 2019-07-20 01:21:31
Document Index: 592067332

Matched Legal Cases: ['art 102', 'art 104', 'arty 126', 'art 102', 'art 104', 'art 502', 'art 502', 'art 502', 'art 502', 'art 502', 'art 502', 'art 502', 'art 502', 'arty 126', 'art 502', 'arts 502', 'art 102', 'art 104', 'art 102', 'art 102', 'arty 1', 'arty 2', 'arty 2', 'arty 2', 'arty 2', 'arty 1', 'art 102', 'art 104', 'art 102', 'art 104']

WO2013128178A1 - Methods and apparatus for transferring an established communication session in a telecommunications network - Google Patents
Methods and apparatus for transferring an established communication session in a telecommunications network Download PDF
WO2013128178A1
WO2013128178A1 PCT/GB2013/050476 GB2013050476W WO2013128178A1 WO 2013128178 A1 WO2013128178 A1 WO 2013128178A1 GB 2013050476 W GB2013050476 W GB 2013050476W WO 2013128178 A1 WO2013128178 A1 WO 2013128178A1
PCT/GB2013/050476
2012-02-27 Priority to US201261603870P priority Critical
2012-02-27 Priority to US61/603,870 priority
2013-09-06 Publication of WO2013128178A1 publication Critical patent/WO2013128178A1/en
Measures for transferring an established communication session in a telecommunications network, the communication session being established between one of a plurality of communication clients associated with a user and a remote device associated with a remote party. At a call control system located in the signalling path for the established communication session, a communication session transfer request is received from a device associated with the user, the communication session transfer request having been generated by and transmitted from the device. Transfer of the established communication session from the one communication client in the plurality of communication clients to another communication client in the plurality of communication clients is initiated at the call control system. The transfer is conducted on the basis of a preconfigured data set, specific to the user, identifying one or more of the plurality of communication clients associated with the user.
The present disclosure relates to transfer of communication sessions. In particular, but not exclusively, the present disclosure relates to transfer of a communication session established between one of a plurality of communication clients associated with a user and a remote device associated with a remote party in a telecommunications network. Background
Telephony users have long had to deal with a proliferation of user devices (sometimes referred to as 'user equipment' or 'endpoints') through which third parties may contact them. For example, a user might have a fixed-line (or 'wireline') telephony user device for use at home, a further fixed-line telephony user device for use in the office, and a mobile telephony user device for use whilst on the move. Each type of telephony device has associated advantages; whilst a mobile telephony device provides the user with mobility, a fixed-line telephony device typically provides more reliable and higher quality communications and no battery recharge concerns.
A circuit-switched telephony device may comprise a fixed-line Plain Old Telephone Service (POTS) telephone equipped with a circuit-switched interface and communication client for conducting communications via a Public Switched Telephone Network (PSTN). A circuit-switched telephony user device may comprise a mobile (or 'cellular') telephone equipped with a wireless circuit- switched interface and communication client for conducting communications via a cellular network such as a Global System for Mobile Communications (GSM) network or Code Division Multiple Access (CDMA) network.
More recently, packet-switched telephony devices have proliferated which may take the form of a fixed-line Internet Protocol (IP) telephone equipped with a fixed-line packet-switched interface and communication client for communicating via an IP network, such as the internet or an IP Private Branch Exchange (IP-PBX). Similarly, a user may conduct communications via a personal computer (PC) equipped with a packet-switched communication client for conducting communications over the internet via a fixed-line internet connection. A mobile packet-switched telephony device may take the form of a portable computing device, such as a laptop or tablet, equipped with a wireless packet-switched interface and communication client for communicating via an IP network, such as the internet, using a Wi-Fi™ or Bluetooth™ compliant wireless access point. A packet-switched communication client may conduct communications according to an internet telephony protocol, commonly referred to as Voice over Internet Protocol (VoIP), with associated setup and control protocols such as the Session Initiation Protocol (SIP) or H.323.
Increasingly, user devices are available that are equipped with multiple communication interfaces to facilitate communication via multiple access technologies. For example, a modern "smartphone" is typically equipped with a circuit-switched interface for communicating via a cellular network and a packet- switched interface for communicating via the internet. Commonly, a smartphone may be equipped with several packet-switched interfaces, for example, a short-range radio interface, e.g. Wi-Fi™ or Bluetooth™ compliant, and/or or via an interface for communication of packet data through a cellular network, such as 3 Generation Partnership Project (3 GPP) Long Term Evolution (LTE), LTE- Advanced (LTE-A), High Speed Packet Access (HSPA), Wideband Code Division Multiple Access (W- CDMA) or Mobile WiMax etc. In such cases, a packet-switched communication client may also be deployed for conducting communications via one or more of the available wireless packet-switched interfaces. In cases such as this where a device is equipped with more than one communication client, the various clients deployed in that device are referred to as co-located. A suitable packet-switched communication client may be deployed on a user equipment prior to sale, or could be deployed subsequently through an application distribution portal such as the Apple® App StoreSM or Android™ Market etc.
To avoid confusing calling parties with identifiers such as telephone dialling numbers for each of the various communication clients of a user, a one-telephone dialling number telephony service allows the user to publish a single telephone dialling number on which they can be contacted. Thus, when the single telephone dialling number is called, all of the user's communication clients will ring, preferably simultaneously. The user is then able to answer the call at a telephony user device of his choosing, via an access technology of his choosing.
When a user is conducting a call on telephony user device, the user may wish to transfer (or 'jump' or 'switch') the call to another device. Known call transfer systems employ a call 'push' technique where a user initiates the call transfer jump from within a call they are currently conducting on one of their devices. Some such known techniques require a user firstly to enter in a number of digits on their device for activating the call transfer, for example entering digits of a 'star code', and secondly to enter in digits for the telephone dialling number for the device the call is to be transferred to.
Such known call transfer techniques provide poor user experience as the user is required to remember the appropriate code to invoke the call transfer and also the telephone number of the target device the call is to be transferred to. Further, the call transfer process is cumbersome because a significant number of button presses are required by the user to complete the call transfer operation. Still further, input of digits by a user causes in-band transmittal of tones, for example Dual-Tone Multi- Frequency (DTMF) signalling, which may disrupt the flow of media associated with communication session.
It would therefore be desirable to provide improved call transfer services. Summary
In accordance with first embodiments, there is a method of transferring an established communication session in a telecommunications network, the communication session being established between one of a plurality of communication clients associated with a user and a remote device associated with a remote party, the method comprising, at a call control system located in the signalling path for the established communication session:
receiving, from a device associated with the user, a communication session transfer request, the communication session transfer request having been generated by and transmitted from the device; and
initiating transfer of the established communication session from the one communication client in the plurality of communication clients to another communication client in the plurality of communication clients,
the transfer being conducted on the basis of a preconfigured data set, specific to the user, identifying one or more of the plurality of communication clients associated with the user.
In accordance with second embodiments, there is apparatus for use in transferring an established communication session in a telecommunications network, the communication session being established between one of a plurality of communication clients associated with a user and a remote device associated with a remote party, the apparatus comprising a processing system adapted to, at a call control system located in the signalling path for the established communication session:
receive, from a device associated with the user, a communication session transfer request, the communication session transfer request having been generated by and transmitted from the device; and
initiate transfer of the established communication session from the one communication client in the plurality of communication clients to another communication client in the plurality of communication clients,
In accordance with third embodiments, there is computer software adapted to perform a method of transferring an established communication session in a telecommunications network, the communication session being established between one of a plurality of communication clients associated with a user and a remote device associated with a remote party, the method comprising, at a call control system located in the signalling path for the established communication session:
initiate transfer of the established communication session from the one communication client in the plurality of communication clients to an another communication client in the plurality of communication clients,
In accordance with embodiments, there is a computer program product comprising a (non-transitory) computer-readable storage medium having computer readable instructions stored thereon, the computer readable instructions being executable by a computerized device to cause the computerized device to perform a method of transferring an established communication session in a telecommunications network, the communication session being established between one of a plurality of communication clients associated with a user and a remote device associated with a remote party, the method comprising, at a call control system located in the signalling path for the established communication session:
In accordance with fourth embodiments, there is a method of transferring an established communication session in a telecommunications network, the communication session being established between one of a plurality of communication clients associated with a user and a remote device associated with a remote party, the method comprising, at a device associated with the user:
configuring a user interface on the device to display at least one communication session transfer option to the user;
receiving, via the user interface, user input indicating selection of the displayed at least one communication session transfer option by the user; and
transmitting, to a call control system located in the signalling path for the established communication session, a communication session transfer request, the transmitted communication session transfer request being operable to instruct the call control system to initiate transfer of the established communication session from the one of the communication clients in the plurality to another communication client in the plurality,
In accordance with fifth embodiments, there is apparatus for use in transferring an established communication session in a telecommunications network, the communication session being established between one of a plurality of communication clients associated with a user and a remote device associated with a remote party, the apparatus comprising a processing system adapted to, at a device associated with the user:
configure a user interface on the device to display at least one communication session transfer option to the user;
receive, via the user interface, user input indicating selection of the displayed at least one communication session transfer option by the user; and
transmit, to a call control system located in the signalling path for the established communication session, a communication session transfer request, the transmitted communication session transfer request being operable to instruct the call control system to initiate transfer of the established communication session from the one of the communication clients in the plurality to another communication client in the plurality, the transfer being conducted on the basis of a preconfigured data set, specific to the user, identifying one or more of the plurality of communication clients associated with the user.
In accordance with sixth embodiments, there is computer software adapted to perform a method for transferring an established communication session in a telecommunications network, the communication session being established between one of a plurality of communication clients associated with a user and a remote device associated with a remote party, the method comprising, at a device associated with the user:
In accordance with embodiments, there is a computer program product comprising a (non-transitory) computer-readable storage medium having computer readable instructions stored thereon, the computer readable instructions being executable by a computerized device to cause the computerized device to perform a method for transferring an established communication session in a telecommunications network, the communication session being established between one of a plurality of communication clients associated with a user and a remote device associated with a remote party, the method comprising, at a device associated with the user: configuring a user interface on the device to display at least one communication session transfer option to the user;
In accordance with seventh embodiments, there is a method of transferring an established communication session in a telecommunications network, the communication session being established between one of a plurality of communication clients associated with a user and a remote device associated with a remote party, the method comprising, at a device associated with the user:
maintaining a set of one or more communication session triggering conditions; in response to detecting that at least of the one or more communication session triggering conditions has occurred, transmitting, to a call control system located in the signalling path for the established communication session, a communication session transfer request, the transmitted communication session transfer request being operable to instruct the call control system to initiate transfer of the established communication session from the one of the communication clients in the plurality to another communication client in the plurality,
Further features and advantages will become apparent from the following description of preferred embodiments, given by way of example only, which is made with reference to the accompanying drawings. Brief Description of the Drawings
Figure 1 shows a system diagram according to embodiments.
Figure 2 shows a flow diagram according to embodiments.
Figure 3 shows a flow diagram according to embodiments.
Figure 4 shows a flow diagram according to embodiments.
Figure 5 shows a system diagram according to embodiments.
Figure 6 shows a system diagram according to embodiments.
Figure 7 shows a block diagram according to embodiments.
Figure 8 shows a flow diagram according to embodiments.
Figure 9 shows a screen-shot of a user device according to embodiments.
Figure 10 shows a block diagram of a user device according to embodiments.
Figure 11 shows a flow diagram according to embodiments.
Figure 12 shows a flow diagram according to embodiments.
Figure 13 shows a screen-shot of a user device according to embodiments.
Figure 14 shows a screen-shot of a user device according to embodiments.
Figure 15 shows a block diagram of a user device according to embodiments.
Figure 16 shows a block diagram of a user device according to embodiments.
Figure 17 shows a block diagram of a user device according to embodiments.
Figure 1 shows an exemplary telecommunications network 1 in which embodiments of the present disclosure can be implemented. Telecommunications network 1 includes a circuit-switched telecommunications network part 102, a packet- switched network part 104 and may include other network parts (not shown). According to embodiments, a client-shared telephony service is hosted and controlled by a call control system 106.
Although depicted in Figure 1 as a single network entity located in-between circuit-switched network 102 and packet-switched network 104, call control system 106 may comprise a plurality of network entities, with elements located within circuit- switched network 102 and/or packet-switched network 104 or one or more other networks (not shown). Call control system 106 comprises a database 180 for storing data associated with client-shared telephony services.
A user of the client-shared telephony service may have a number of user devices 108 through which they may conduct communication sessions via the service. The various devices 108 through which a user can conduct communications via the service are considered to be associated with that user. The user's associated devices may include, for example, desk phone 110, mobile (or 'cellular') telephone 112, tablet 114 and/or personal computer 116.
Each of the user's telephony devices is equipped with one or more interfaces and one or more communication clients for conducting communications in telecommunications network 1. Devices equipped with a circuit-switched interface and communication client are adapted to conduct communications in telecommunications network 1 via link 118 with circuit-switched network 102. The circuit-switched interface may comprise a landline PSTN interface in the case of a fixed-line device such as desk phone 110, or a cellular radio telephony interface in the case of a mobile device such as mobile telephone 112. Devices equipped with a packet-switched communications client are adapted to conduct communications in telecommunications network via link 120 with packet- switched network 104. This packet-switched interface could comprise a wired interface to the internet in the case of a fixed line device such as personal computer 1 16, or a wireless interface (e.g. Wi- Fi, Bluetooth, 3G-LTE, WiMax, etc.) to the internet in the case of a mobile device such as tablet 114. The packet-switched interface may comprise an Ethernet part.
Some devices may be equipped with multiple communications clients. For example, in addition to the aforementioned circuit- switched communication client and associated interface, mobile telephone 112 may also be equipped with one or more packet-switched communications clients and interfaces for conducting communications with packet-switched network 104 via link 120. In this case, the multiple communication clients equipped on mobile telephone 112 are referred to as co-located communication clients, i.e. multiple communication clients on a single device.
A communication session established between a communication client on one of the user's devices 108 and a communication client on a device of a remote party 126 can be routed between circuit-switched network 102 and call control system 106 via link 122. Link 122 may for example comprise a SIP trunk, or other high capacity communications link. Similarly, communication sessions can be routed between packet-switched network 104 and call control system 106 via link 124. Link 122 and/or link 124 may comprise one or more gateway or session border controller entities (not shown) which carry out conversion between the various protocols and data formats used to transfer media data and signalling data in the different networks making up telecommunications network 1. For example, a media gateway (not shown) may convert between the different protocols of media data passing between circuit-switched network 102 and packet-switched network 104, such as packetised VoIP data into Time-Division-Multiplexing (TDM) voice data and vice versa. A signalling gateway (not shown) may convert between the different protocols of signalling information passing between circuit- switched network 102 and packet- switched network 104, such as SIP, Signalling System 7 (SS7), Integrated Services Digital Network User Part (ISUP), American National Standards Institute (ANSI) - 41, Mobile Application Part (MAP) formats, etc.
In order to provide the client-shared telephony service, circuit-switched network 102 is configured to route communication sessions conducted between the user's devices 108 and a remote party device 126 via call control system 106. Call control system 106 may comprise a media gateway controller, service platform, call agent, application server or Softswitch and may also perform other functions typically associated with such entities.
In embodiments, call control system 106 is located in the signalling path for communication sessions conducted to/from a user's devices 108. In embodiments, call control system 106 is located in the media path for communication sessions conducted to/from a user's devices 108.
Operation of the client-shared telephony service in telecommunications network 1 will now be described in relation to Figure 2.
Figure 2 shows a signalling message flow diagram describing the operation of telecommunications network 1 of Figure 1 for providing a client-shared telephony service according to embodiments. At step 2a, a communication session setup request to the client-shared dialling number is transmitted by a communication client on remote party device 126. Circuit-switched network 102 has been configured to route communication session signalling data relating to the client-shared dialling number service to call control system 106, and contacts call control system with appropriate communication session signalling data accordingly in step 2b. Upon receipt of the communication session signalling data of step 2b, call control system 106 takes control of the communication session, as shown by item 202.
At step 2c, call control system 106 transmits communication session set up requests to the user's packet-switched communication clients 108a via packet- switched network 104. Upon receipt of such communication session set up requests, the user's packet-switched communication clients 108a will (unless unavailable, for example due to network problems or due to being switched off) alert the user as to the request for incoming communication as shown by item 204. Such alerting will involve activating one or more alert functions on the appropriate device, such as ring and/or vibrate functions. Similarly, at step 2d, call control system 106 transmits communication session set up requests to the user's circuit-switched clients 108b via circuit-switched network 102 in step 2e. Upon receipt of such communication session set up requests, the user's circuit-switched communication clients 108b will alert the user accordingly, as shown by item 206.
The result of steps 2a to 2e is that all of the user's communication clients (which are available) will ring, allowing the user to select at which communication client (and therefore via which associated access technology) on which device to accept the received communication session set up request and hence conduct a communication session on.
In the embodiments depicted in Figure 2, the user accepts the communication session set up request at one of their circuit-switched communication clients, at step 208, by entering appropriate user input e.g. by pressing an answer key via a user interface on the device on which the circuit- switched communication client in question is deployed. This results in the transmission of a communication session setup response message (in this case an acceptance response message) being transmitted from the circuit-switched communication client back to call control system 106 via circuit-switched network 102, as shown by steps 2f and 2g. Call control system 106 then transmits a communication session setup response (acceptance) message back to remote party device 126 via circuit-switched network entity 102, as shown by steps 2h and 2i. Having completed the end-to-end communication session set up signalling flow, a communication session is established between remote party device 126 and the circuit- switched communication client 108b at which the communication session was accepted by the user as shown by item 210.
Note that in the embodiments depicted in Figure 2, the user chose to accept the communication session setup request such that an acceptance response message was generated by the user communication client in question. If the user had chosen to reject the communication session setup request, then the user communication client in question would have generated a rejection response message, transmitted the rejection response message to call control system 106 and a communication session would not have been established with remote party device 126.
In embodiments, established communication session 210 consists of multiple communication session legs. A communication session leg is a subset of the established communication session that provides end to end communication for a part of a communication session path. For example, communication session 210 may comprise one communication session leg between remote party device 126 and call control system 106, and another communication session leg between call control system 106 and a user communication client 108. This allows call control system 106 to maintain its presence on the communication session path and provide additional features or call services if required. Each of the communication session legs between call control system 106 and the remote party device communication client may actually be subdivided into a number of further legs, but will be referred to below as a single leg for the sake of simplicity. Further, the communication session legs need not connect to the same node in call control system 106 and may be bridged by one or more further legs in order to provide the required end-to-end communications.
Figure 3 shows a signalling message flow diagram describing the operation of telecommunications network 1 of Figure 1 when a user initiates (or 'places') a call from a packet-switched client of the client-shared telephony service according to embodiments. At step 3 a, when a user enters in a telephone dialling number or other identifier for remote party device 126 or selects a corresponding entry from a contact address book or suchlike, packet-switched client 108a, located on a device associated with a user of the client-shared telephony service, generates and transmits a communication session setup request, directed to a communication client on remote party device 126, from packet-switched client 108a to call control system 106 via packet-switched network 104. Upon receipt of the communication session setup request of step 3 a, call control system 106 takes control of the communication session, as shown by item 302.
Having taken control of the communication session, call control system 106 transmits a communication session setup request to remote party device 126 via circuit-switched network 102, as shown by steps 3b and 3c. The communication setup request of step 3 c may pass through a number of further entities or network parts (not shown) between call control system 106, circuit-switched network 102 and remote party device 126 such as one or more telephone switches (or 'local exchanges', 'central offices' or 'class 5 switches').
Upon receipt of the communication session setup request of step 3c, the communication client on remote party device 126 will alert the remote party as to the incoming request for setup of a communication session; such alerting may involve activation of an alert function on remote party device such as a ringing function (as shown by item 304) and/or a vibrate function, etc. In the embodiments of Figure 3, the remote party accepts the communication session setup request at step 306 by appropriate user input on remote party device 126. This results in the transmission of a communication session setup response message (in this case an acceptance response message) being transmitted from the communication client on remote party device 126 back to circuit-switched network 102 in step 3d. Circuit-switched network 102 has been configured to route communication session signalling data relating to the client-shared dialling number to call control system 106 and contacts call control system 106 with appropriate communication session signalling data accordingly in step 3e.
Upon receipt of the communication session signalling data of step 3e, call control system 106 transmits a communication session setup response (acceptance) message back to packet-switched client 108a via packet-switched network 104, as shown by step 3f. Having completed the end-to-end communication session setup signalling flow, a communication session is established between packet-switched communication client 108a and remote party device 126, as shown by item 308.
Note that in the embodiments depicted in Figure 3, the remote party chose to accept the communication session setup request such that an acceptance response message was generated by the communication client on remote party device 126. If the remote party had chosen to reject the communication session setup request, then the communication client on the remote party device would have generated and transmitted a rejection response message and a communication session would not have been established.
Figure 4 shows a signalling message flow diagram describing the operation of telecommunications network 1 of Figure 1 for a user initiating a call from a circuit- switched client of the client-shared telephony service according to embodiments.
At step 4a, when a user enters in a telephone dialling number or other identifier for remote party device 126 or selects a corresponding entry from a contact address book or suchlike, circuit-switched client 108b, located on a device associated with a user of the client-shared telephony service, generates and transmits a communication session setup request directed to a communication client on remote party device 126, into circuit-switched network 102. Circuit-switched network 102 has been configured to route communication session signalling data relating to the client-shared dialling number service to call control system 106, and contacts call control system 106 with appropriate communication session signalling data accordingly in step 4b. Upon receipt of the communication session signalling data of step 4b, call control system 106 takes control of the communication session, as shown by item 402.
Having taken control of the communication session, call control system 106 transmits a communication session setup request to remote party device 126 via circuit-switched network 102, as shown by steps 4c and 4d. The communication setup request of step 4d may pass through a number of further entities or network parts (not shown) between call control system 106, circuit-switched network 102 and remote party device 126 such as one or more telephone switches (or 'local exchanges', 'central offices' or 'class 5 switches').
Upon receipt of the communication session setup request of step 4d, the communication client on remote party device 126 will alert the remote party as to the incoming request for setup of a communication session; such alerting may involve activation of an alert function on remote party device such as a ringing function (as shown by item 404) and/or a vibrate function, etc. In the embodiments of Figure 4, the remote party accepts the communication session setup request at step 406 by appropriate user input on remote party device 126. This results in the transmission of a communication session setup response message (in this case an acceptance response message) being transmitted from the communication client on remote party device 126 back to circuit-switched network 102 in step 4e. Circuit-switched network 102 has been configured to route communication session signalling data relating to the client-shared dialling number service to call control system 106 and contacts call control system 106 with appropriate communication session signalling data accordingly in step 4f.
Upon receipt of the communication session signalling data of step 4f, call control system 106 transmits a communication session setup response (acceptance) message back to circuit-switched client 108b via circuit-switched network 102, as shown by steps 4g and 4h. Having completed the end-to-end communication session setup signalling flow, a communication session is established between remote party device 126 and the circuit-switched communication client 108b.
Figure 5 shows telecommunications network 1 depicted in Figure 1 in more detail according to embodiments; in such embodiments, circuit switched-network part 102 comprises a mobile (or 'cellular') telephony network 102A and packet-switched network part 104 comprises IP network 104A. A client-shared telephony service is hosted and controlled by call control system 106.
According to the embodiments shown in Figure 5, a user of the client-shared telephony service has one or more devices 108 associated with their client-shared dialling number through which they may conduct communications via the service. The user's associated devices include, at least, mobile telephone 112. In embodiments, the user's associated devices also include tablet 114. Mobile telephone 112 is equipped with a cellular radio telephony interface and circuit-switched communication client for conducting communications in telecommunications network 1 via mobile telephony network 102 A. In embodiments, mobile telephone 112 is also equipped with at least one wireless packet-switched interface and packet-switched communications client for conducting communications in telecommunications network 1 via radio link 580 with IP network 104A; in such embodiments where mobile telephone comprises multiple communication clients, the communication clients are referred to as co-located communication clients.
Tablet 114 is equipped with at least one wireless packet-switched interface and packet-switched communications client for conducting communications in telecommunications network 1 via radio link 582 with IP network 104 A.
Mobile telephony network 102 A allows for provision of telephony services to a number of mobile telephones, although only the user's mobile telephone 112 and tablet 114 are depicted in Figure 5. Mobile telephony network 102A comprises home mobile network part 502a, which is generally associated with mobile telephone 112. Communication sessions initiated to a telephone dialling number associated with mobile telephone 112, e.g. a Mobile Station International Subscriber Directory Number (MSISDN), are routed to home mobile network part 502a for processing as a result of that general association. Home mobile network part 502a comprises mobile switching centre (MSC) 514 and home location register (HLR) 516. HLR 516 comprises a database which provides, upon request, MSC 114 with data relating to users generally associated with home mobile network 502a, such as the location of their mobile telephones and configuration data such as call routing triggers, billing information, etc.
Mobile telephony network 102A also comprises visited mobile network part 502b, which is transiently associated with mobile telephone 112. Visited mobile network part 502b comprises serving MSC 522, Visitor Location Register (VLR) 524 and base transceiver station (BTS) 512. BTS 512 transmits radio signals to, and receives radio signals from, the circuit-switched communications client and cellular radio telephony interface on mobile telephone 112 via a radio communication link. It is this communication relationship that provides the transient association between mobile telephone 112 and visited mobile network part 502b. Mobile telephone 112 is located in an area (commonly known as a 'cell') served by BTS 512. BTS 512 may be controlled by a basestation controller (BSC; not shown), which may also control a number of further BTSs (also not shown), which, in combination with a number of further BSCs and BTSs, may provide a number of geographically distributed cells served by MSC 522.
When mobile telephone 112 associates with serving MSC 522 (e.g. by entering a cell served by MSC 522), serving MSC 522 informs home MSC 514, which in turn updates HLR 516 with the location of mobile telephone 112. In this way, HLR 516 is kept up-to-date with the most recent location of mobile telephone 112. Additionally, configuration data relating to mobile telephone 112 is copied into VLR 524. This allows calls placed by mobile telephone 112 while being served by serving MSC 522 to be correctly handled according to the aforementioned configuration data.
Depending on the location of mobile telephone 112, home mobile network part 502a may also serve mobile telephone 112, in which case it will comprise the same network part as visited mobile network part 502b.
According to embodiments, a client-shared telephony service is provided by associating one or more communication clients (including the packet-switched communication client on mobile telephone 112) with a telephone dialling number associated with the circuit-switched communication client on mobile telephony device 112, such as its MSISDN. This can be referred to as 'twinning' the additional communication clients with the circuit-switched communication client. According to the embodiments, the client-shared dialling number is therefore the MSISDN of the circuit- switched communication client on mobile telephony device 112.
A communication session between a communication client on one of the user's devices 108 and a communication client on a device of a remote party 126 is routed between the remote party device 126 and home mobile network part 502a via one or more further network parts (not shown). In some embodiments, remote party device 126 comprises also a mobile telephone, in which case the communication session may be routed via one or more serving mobile network parts and home mobile network parts associated with the remote party device. These could be the same as mobile network parts 502a and/or 502b, or further mobile network parts (not shown). In other embodiments, remote party device 126 comprises a fixed line circuit- switched telephone, such as a POTS telephone, in which case the communication session may be routed via a PSTN and one or more gateway entities, such as a gateway MSC, to convert between the various protocols and data formats used to transfer media data and signalling data in the PSTN and mobile telephony network 102A. Home MSC 514 may fulfil the role of the gateway entity, or it may be fulfilled by another intermediate entity. In further alternative embodiments, remote party device 126 comprises an IP telephony device, such as a SIP telephone, in which case the communication session may be routed via an IP network, such as the internet, and one or more gateway entities. Again, home MSC 514 may fulfil the role of the gateway entity, or it may be fulfilled by another intermediate entity.
A communication session between a communication client on one of the user's devices 108 and a communication client on remote party device 126 can be routed between mobile telephony network 102 A and call control system 106 via, for example, a SIP trunk, or other high capacity communications link. The links between IP network 104 A, call control system 106 and mobile telephony network 102 A may comprise one or more gateway or session border controller entities (not shown) which carry out conversion between the various protocols and data formats used to transfer media data and signalling data in the different networks making up telecommunications network 1.
In order to provide a client-shared telephony service, mobile telephony network 102 A is configured to route communication session setup, signalling and or/media data relating to one of the user's devices 108 via call control system 106. This can be achieved by configuring HLR 516 with one or more triggers for communication session data relating to the client-shared dialling number, such that data originating from or directed to that dialling number results in appropriate communication session signalling data being sent to call control system 106. According to some embodiments, this could comprise a routing query to establish where the communication session data should be routed.
In other embodiments, the communication session data itself may be routed to call control system 106, which then handles the sending of communication session data to any appropriate further entities. In such embodiments, communication session data transmitted from call control system 106 to the circuit- switched communication client on mobile telephone 112 would be undesirably routed back to call control system 106 by mobile telephony network 102 A if routed by conventional methods on the basis of the MSISDN of the circuit-switched communication client. There are several methods for overcoming this behaviour, for example, the transmitted data may include additional information to indicate that the triggers stored in HLR 516 should not be utilised, causing HLR 516 to return the location of the mobile telephone 112 instead of invoking the associated trigger. Alternatively, call control system 106 may be adapted to query HLR 516 directly via a further interface (not shown) to obtain a temporary routing number (TRN) for communicating with the circuit-switched communication client on mobile telephone 112. Routing communications to the circuit-switched communication client on mobile telephone 112 via such a TRN would not invoke the triggers stored in HLR 516, as the client-shared dialling number is not used.
Call control system 106 comprises call control server 518, and user database
180. Call control server 518 is responsible for processing communication session data, including data such as user data stored in database 180. Database 180 is used to store data relating to a number of users of the client-shared telephony service, including a set of identifiers for the communication clients associated with each given user. In this manner, by querying database 180, call control server 518 is able to determine which communication clients and/or devices a communication session setup request received from a remote party should be routed to, or which user a communication session setup request received from a given communication client relates to, etc.
In some embodiments, database 180 is also used to store a user profile for each of the users, containing for example user-configurable preferences. These user- configurable preferences could comprise call routing preferences for defining complex ringing scenarios, which might define a subset of a user's communication clients which should be used to route calls to under certain conditions. For example, a user may wish to configure their user preferences such that only business calls are routed to their desk phone at the office if it is earlier than 6pm on a weekday, or that calls from family are not routed to their tablet between 9am and 5pm on weekdays.
In embodiments, communication session setup requests are transmitted to all communication client associated with a user. However, in other embodiments, communication session setup requests are directed to a specific communication client in a number of ways. According to some embodiments, a communication session setup request is routed to a communication client on the basis of a unique identifier for that communication client. According to other embodiments, a communication session setup request is transmitted to all of a user's communication clients, but with the identifiers of the targeted communication clients included as an additional parameter.
In embodiments, when a communication client receives the communication session setup request, it checks its own identifier against the included identifiers, and alerts the user to the communication session setup request if there is a matching identifier. In embodiments, when a communication client receives the communication session setup request, it checks its own identifier against the included identifiers, and auto-answers the communication session setup request if there is a matching identifier.
A communication client that receives the communication session setup request but does not identify its own identifier as being included in the identifiers included as additional parameters will not alert the user as to the presence of communication session setup request. Such communication clients may silently reject the communication session setup request.
Call control system 106 may further comprise a media gateway controller, service platform, call agent, application server or Softswitch and may perform other functions typically associated with such entities. The elements comprised by call control system 106 may be located within mobile telephony network part 102A and/or IP network part 104 A, or one or more other networks (not shown). By virtue of connecting to mobile telephony network 102 A and IP network 104 A via a wireless interface, each of the communication clients equipped on mobile telephone 112 may have intermittent connectivity to call control system 106, and therefore are only intermittently able to conduct communications. This may be due to mobility reasons, for example moving in and out of range of the various cells and access points, or due to interference from other wireless communication equipment etc. From the perspective of call control system 106, a communication client on tablet 114 can also be considered to have intermittent availability. Hence, database 180 may be further configured to store availability information for communication clients associated with a given user. According to some embodiments, this is achieved by configuring each communication client to periodically send a message (commonly referred to as a heartbeat) to call control server 518. If such a heartbeat message is not received by call control server 518, that communication client can be considered unavailable until a subsequent heartbeat message is successfully received. Alternatively, in other embodiments, call control server 518 is adapted to periodically "poll" each communication client to probe for its availability using a request response protocol.
Figure 6 shows telecommunications network 1 in more detail according to embodiments; in such embodiments, circuit switched-network part 102 comprises a fixed-line circuit-switched network 102B, such as a PSTN. Telecommunications network 1 includes PSTN part 102B, IP network 104A and may include other network parts (not shown). A client-shared telephony service is hosted and controlled by call control system 106, which comprises call control server 518 and user database 180, the functions of which are similar to those described above in relation to Figure 5.
Circuit-switched fixed-line telephony network 102B comprises telephone switch 614 and routing database 616. Routing database 616 is queried by telephone switch 614 in order to establish how to route communication session data. As well as providing basic routing information, routing database 616 can be configured with a number of triggers in relation to certain calling or called parties. In embodiments, routing database 616 is configured to route all communication session data either originating from, or directed to, communication clients on one of a user's devices 108 via call control system 106. In embodiments shown in Figure 6, the user's devices 108 comprise a desk phone 110 and tablet 114. Desk phone 110 is configured with a fixed-line circuit- switched PSTN interface and a circuit-switched communication client. Tablet 114 is equipped with a wireless packet-switched interface and a packet-switched communication client for conducting communications in telecommunications network 1 via radio link 684 with IP network 104A. The packet-switched client on tablet 114 has been configured into the multiple client shared dialling number telephony service with respect to a telephone dialling number associated with the circuit- switched client on desk phone 110. Again, this can also be described by referring to the packet switched communication client on tablet 114 as having been 'twinned' with the circuit- switched client on desk phone 110.
Figure 7 shows a user device 700 adapted to conduct communication sessions such as voice calls in telecommunication network 1 according to embodiments. User device 700 may for example comprise mobile telephone 112 depicted in Figure 1.
User device 700 comprises a processor 702 for carrying out data processing tasks of embodiments. User device 700 comprises a memory 704 for storing data, including user entries comprising identifiers for each of a user's communication clients and/or user devices. User device 700 comprises a user interface 706 for collecting user input from a user of the device, including user input associated with setting up and acceptance of communication sessions, such as telephone dialling number digits, and call transfer operations.
In embodiments, user device 700 comprises a display 724. In embodiments display 724 comprises a touch-screen display, which, in conjunction with user interface 706, forms a graphical user interface. One or more touch-sensitive screen regions (or 'buttons') are configurable by processor 702 on the graphical user interface.
In embodiments, user device 700 comprises a first communication client 710 adapted to communicate via a first part of telecommunications network 1 and a second communication client 720 adapted to communicate via a second, different part of telecommunications network 1. In such embodiments, first communication client 710 and second communication client 720 are co-located on user device 700. First communication client 710 communicates via a first part of telecommunications network 1 via a first communication interface 712. Second communication client 710 communicates via a second part of telecommunications network 1 via a second communication interface 714. User device 700 includes one or more antennae 730 connected to first communication interface 712 and/or second communication interface 714 for wireless radio communication.
In embodiments, first communication client 710 comprises a cellular communication client adapted to communicate via a cellular part of telecommunications network 1 and second communication client 720 comprises a VoIP communication client adapted to communicate via a packet-switched part of telecommunications network 1. In embodiments, first communication interface 712 comprises a cellular radio modem and second communication interface 714 comprises a non-cellular radio modem.
Embodiments described below in relation to Figure 8 enable transfer of an established communication session in telecommunications network 1. A communication session 800 is established between one of a plurality of communication clients associated with a user, in this example first communication client 710 on user device 700 which comprises a packet-switched communication client and a remote device 126 associated with a remote party, for example as described above in relation to any of Figures 2 to 4.
Call control system 106 is located in the signalling path for the established communication session and maintains a user database 180 containing user entries for a plurality of users, each user entry comprising a set of identifiers for communication clients associated with the respective user.
User interface 706 on user device 700 is configured to display at least one communication session transfer option to the user, in this case an option to transfer the communication session established between packet-switched communication client 710 and circuit-switched communication client 712 which is co-located on user device 700. The configuration to display the at least one communication session transfer option to the user may for example occur in response to circuit-switched communication client 712 on user device 700 detecting establishment of a communication session via co-located packet-switched communication client 710 on user device 700.
An exemplary screen-shot of user device 700 configured to display at least one communication session transfer option to the user is depicted in Figure 9 according to embodiments. Button 901 includes the text 'switch' indicating to the user that selecting this button will allow them to switch (or 'transfer' or 'jump') the established communication session to another communication client (in this case circuit-switched communication client 712).
A diagram of user device 700 configured to display at least one communication session transfer option to the user is depicted in Figure 10 according to embodiments. Button 960 includes the text 'slide to switch' indicating to the user that selecting this button will allow them to switch (or 'transfer' or 'jump') the established communication session to another communication client (in this case circuit-switched communication client 712). In this embodiment, the arrow form of the button which points to the right indicates to the user that they should touch the button located in position 960 and slide the button to the right to position 970 in order to initiate transfer of the communication session.
User input is received via user interface 706, as shown by step 8a, which indicates selection of the displayed at least one communication session transfer option by the user of user device 700.
User device 700 transmits, to call control system 106, a communication session transfer request, as shown by step 8b in Figure 8. The transmitted communication session transfer request of step 8b is operable to instruct call control system 106 to initiate transfer of the established communication session from packet- switched communication client 710 to circuit-switched communication client 712.
Call control system 106 receives, from user device 700, the communication session transfer request of step 8b, the communication session transfer request of step 8b having been generated by and transmitted by user device 700 in response to the user input of step 8a via user interface 706 on user device 700. In response to receipt of the communication session transfer request of step 8b, call control system 106 performs a lookup in the user database, for example user database 180. The lookup identifies at least another communication client in the plurality of communication clients associated with the user, in this case circuit-switched communication client 712 which is co-located on user device 700. Call control system initiates transfer of the established communication session from packet-switched communication client 710 in the plurality of communication clients to circuit-switched communication client 712 in the plurality of communication clients associated with the user of user device 700.
The transfer is conducted on the basis of a preconfigured data set, specific to the user, which identifies one or more of the plurality of communication clients associated with the user. In these embodiments, the preconfigured data set is retrieved from database 180 by call control system 106.
In embodiments, the initiating comprises transmitting a communication session leg setup request to circuit switched communication client 712 via circuit- switched network 102 in steps 8c and 8d and a communication session 802 is established between remote party device 126 and circuit-switched communication client 712.
In the embodiments depicted in Figure 8, communication session 800 established between remote party device 126 and packet-switched communication client 710 is torn down after establishment of communication session 802 as shown by step 8e. In alternative embodiments, communication session 800 established between remote party device 126 and packet-switched communication client 710 is torn down before establishment of communication session 802.
In embodiments, user device 700 inserts an identifier for circuit-switched communication client 712 to which the user wants to transfer the communication session into the communication session transfer request of step 8b. When call control system 106 receives the identifier for the circuit- switched communication client 712, call control system 106 can thus identify which communication client the user wishes to transfer the communication session and transmits the communication session transfer request of step 8c into circuit-switched network accordingly.
In the embodiments described above in relation to Figures 8 to 10, the user only has two communication clients, both of which are co-located on the same user device 700. The operation of transferring a communication session from one communication client 710 on user device 700 to another communication client 712 can be described either as a 'push' operation from communication client 710 to communication client 712 or a 'pull' operation from communication client 712 to communication client 710.
In embodiments, a user has a plurality of communication clients located on a plurality of associated devices. In embodiments described below in relation to Figure 11, a user has a user device 700 with communication client 710 and co-located communication client 712, and a further user device 900 with communication client 910. User device 700 may for example comprise mobile telephone 112 with co- located packet-switched and circuit-switched communication clients 710 and 712 and user device 900 may for example comprise tablet 114 with a packet-switched communication client 910.
Embodiments described below in relation to Figure 11 enable transfer of an established communication session in telecommunications network 1 where the user has a choice of more than one communication client to which to transfer an established communication session to. The various networks within which each of the devices is located have been omitted here for ease of explanation.
A communication session 1100 is established between one of a plurality of communication clients associated with a user, in this example between first communication client 710 on user device 700 and a remote device 126 associated with a remote party, for example as described above in relation to any of Figures 2 to 4.
Upon establishment of communication session 1100 between first communication client 710 on user device 700 and remote party device 126, call control system performs a lookup in database 180 for the user of user device 700 and determines that the user also has a user device 900 with communication client 910 installed on it. Call control system 106 therefore notifies user device 900 that there is a communication session 1200 currently being conducted between first communication client 710 on user device 700 and remote party device 126 in step 11a. User interface 706 on user device 700 is configured to display at least one communication session transfer option to the user, in this case an option to transfer the communication session established between first communication client 710 and either second communication client 712 which is co-located on user device 700 or third communication client 910 which is located on user device 900.
User input is received via user interface 706 of user device 700, as shown by step l ib, which indicates selection of the displayed at least one communication session transfer option by the user on user device 700.
User device 700 transmits, to call control system 106, a communication session transfer request, as shown by step 11c in Figure 11. The transmitted communication session transfer request of step 11c is operable to instruct call control system 106 to initiate transfer of the established communication session from first communication client 710 on user device 700 to second communication client 712 on user device 700 or third communication client 910 on user device 900.
Call control system 106 receives, from user device 700, the communication session transfer request of step 11c, the communication session transfer request of step 11c having been generated by and transmitted by user device 700 in response to the user input of step 1 lb via user interface 706 on user device 700. In response to receipt of the communication session transfer request of step 11c, call control system 106 performs a lookup in the user database, for example user database 180. The lookup identifies second communication client 712 and third communication client 910 as being communication clients associated with the user.
Call control system initiates transfer of the established communication session from first communication client 710 in the plurality of communication clients to second communication client 712 on user device 700 or third communication client 910 on user device 900 by transmitting one communication session leg setup request to second communication client 712 on user device 700 in step l id and another communication session leg setup request to third communication client 910 on user device 900 in step l ie.
Upon receipt of the communication session leg setup request of step l id by second communication client 712, second communication client 712 alerts the user as to the receipt of the communication session leg setup request by activating an alert function on user device 700 such as a ringing function associated with second communication client 712.
Upon receipt of the communication session leg setup request of step l ie by third communication client 910, third communication client 712 alerts the user as to the receipt of the communication session leg setup request by activating an alert function on user device 900 such as a ringing function associated with third communication client 910.
The user can now choose to accept the communication session transfer at either second communication client 712 on user device 700 or third communication client 910 on user device 900. In this case, the user chooses to accept the communication session transfer third communication client 910 on user device 900 by entering suitable user input on user device 900 as shown by step l lf. The user input may for example involve the user pressing an 'answer call' button activated on a user interface of user device 900.
Upon receipt of the user input accepting the communication session transfer at third communication client 910 on user device 900, user device 900 transmits a communication session leg setup response to call control system 106 in step 1 lg.
Upon receipt of the communication session leg setup response of step 1 lg at call control system 106, call control system 106 establishes a communication session between remote party device 126 and third communication client 910 on user device 900 as shown by item 1102.
Call control system 106 tears down the communication session established between remote party device 126 and first communication client 710 in step 1 lh.
Note that in the embodiments described above in relation to Figure 11 even if the user of user device 700 terminates (i.e. 'hangs-up') the communication session 1100 currently being conducted between first communication client 710 and remote party device 126 after entering user input in step l ib, call control system 106 still transmits the communication session leg setup requests of steps l id and l ie and transfer of the terminated communication session can still take place.
In the above embodiments, once the communication session between remote party device 126 and third communication client 910 is established, call control system 106 tears down the communication session established between remote party device 126 and first communication client 710. In alternative embodiments, the communication session established between remote party device 126 and first communication client 710 is maintained. A three-way communication session (or 'teleconference') can thus ensue between the remote party, a user of user device 700 and a user of user device 900.
The alert functions activated in response to receipt of the communication session leg setup requests of steps l id and l ie relating to transfer of a communication session between communication clients associated with a user may comprise a distinctive ring tone which sounds different from a ring tone activated in response to receipt of a communication session leg setup request associated with a standard, noncommunication session transfer related request from another remote party. Such a distinctive alert function can also be useful if a user's device is a shared household telephone, such that people in the household other than the user know not to answer a transferred communication session because the telephone rings differently from normal incoming calls to the telephone.
In embodiments, initiating transfer of the established communication session comprises transmitting an instruction to second communication client 712 and/or third communication client 910 to activate an alert function which is distinctive for a communication session transfer scenario.
In embodiments, the alert function comprises a distinctive ringing function. A user can therefore easily distinguish between communication session transfers and standard incoming calls by listening to and recognising the different sounding alert function associated with a communication session transfer.
In embodiments, the alert function comprises a distinctive display function. A user can therefore easily distinguish between communication session transfers and standard incoming calls by viewing and recognising the difference in appearance of the different display function associated with a communication session transfer. In embodiments described above, upon establishment of communication session 1100 between first communication client 710 on user device 700 and remote party device 126, call control system performs a lookup in database 180 for the user of user device 700, determines that the user also has a user device 900 with communication client 910 installed on it and notifies user device 900 that there is a communication session 1200 currently being conducted between first communication client 710 on user device 700 and remote party device 126 in step 11a. In alternative embodiments, call control system 106 does not transmit the notification of step 11a upon establishment of communication session 1100, but waits for the occurrence of a further event such as the user opening communication session transfer application software on user device 700 or the user selecting a part of the user interface of user device 700 associated with communication session transfers, etc.
In embodiments, an additional message is transmitted from call control system 106 to first communication client 710 when the communication session leg setup requests of steps l id and l ie are transmitted. The additional message transmitted to first communication client 710 comprises a further communication session leg setup request, which in this case is rejected by first communication client 710 because a communication session is already established via first communication client 710.
In the embodiments described above, in response to receipt of the communication session transfer request of step 11c, call control system 106 performs a lookup in user database 180 in order to determine one or more communication clients associated with the user to transmit communication session setup request to, in this case first communication client 710 and third communication client 910. In alternative embodiments, some of the logic associated with the communication session transfer operation is provided by a user's device, rather than by call control system 106. In such embodiments, user device 700 maintains a set of identifiers for one or more communication clients associated with the user and inserts one or more of such identifiers into the communication session transfer request of step 11c. In such embodiments, call control system 106 need not maintain user database 180 with user entries for a plurality of users containing a set of identifiers for one or more communication clients associated with each user, nor perform lookup in any such database because the communication clients associated with the user (in this case first communication client 710 and third communication client 910) are identified in the communication session transfer request of step 11c. Call control system 106 can thus transmit the communication session let setup requests of steps l id and l ie on the basis of information contained in the communication session transfer request of step 11c. In such embodiments, user device 700 may insert further logic into the communication session transfer request of step 11c in order to instruct call control system 106 on the communication session transfer. In such alternative embodiments, the transfer is conducted on the basis of a preconfigured data set, specific to the user, which identifies one or more of the plurality of communication clients associated with the user. In these embodiments, the preconfigured data set is provided to call control system 106 by user device 700.
The embodiments described above in relation to Figure 11 involve the displayed at least one transfer option comprising an option to push the communication session established on first communication client 710 on user device 700 to the second communication client 712 on user device 700 or the third communication client 910 on a different user device 900.
Embodiments described below in relation to Figure 12 involve the displayed at least one transfer option comprising an option to pull a communication session established on first communication client 710 on user device 700 to a third communication client 910 on a different user device 900.
A communication session 1200 is established between one of a plurality of communication clients associated with a user, in this example between first communication client 710 on user device 700 and a remote device 126 associated with a remote party, for example as described above in relation to any of Figures 2 to 4.
Upon establishment of communication session 1200 between first communication client 710 on user device 700 and remote party device 126, call control system performs a lookup in database 180 for the user of user device 700 and determines that the user also has a user device 900 with communication client 910 installed on it. Call control system 106 therefore notifies user device 900 that there is a communication session 1200 currently being conducted between first communication client 710 on user device 700 and remote party device 126 in step 12a.
Upon receipt of the notification of step 12a, a user interface on user device 900 is configured to display at least one communication session transfer option to the user, in this case an option to pull the communication session established between first communication client 710 on user device 700 and remote party device 126 to third communication client 910 located on user device 900.
An exemplary screen-shot of display of such a communication session transfer option to the user of user device 900 is given in Figure 13. Here the user is informed that there is an active call with a third party (in this example somebody called 'Michael Thorpe') on user device 700 (which is an ipad™ in this example) and a 'pull call here' button 1300 is displayed to the user.
A further exemplary screen-shot of display of such a communication session transfer option to the user of user device 900 is given in Figure 14. Here the user is informed that there is an active call with Michael Thorpe on user device 700 (which is a Nexus One in this example) and a 'slide to transfer call here' button 1400 is displayed to the user.
User input is received via the user interface of user device 900, as shown by step 12b, (for example pushing of button 1300 or sliding of button 1400) which indicates selection of the displayed at least one communication session transfer option by the user.
User device 900 transmits, to call control system 106, a communication session transfer request, as shown by step 12c in Figure 12. The transmitted communication session transfer request of step 12c is operable to instruct call control system 106 to initiate transfer of the established communication session from first communication client 710 on user device 700 to third communication client 910 on user device 900.
Call control system 106 receives, from user device 900, the communication session transfer request of step 12c, the communication session transfer request of step 12c having been generated and transmitted by user device 900 in response to the user input of step 12b via a user interface on user device 900. In response to receipt of the communication session transfer request of step 12c, call control system 106 performs a lookup in the user database, for example user database 180. The lookup identifies that the user of user device 900 also has a user device 700 and that a communication session is currently being conducted between first communication client 710 of user device 700 and remote party device 126.
Call control system initiates transfer of the established communication session from first communication client 710 on user device 700 to third communication client 910 on user device 900 by transmitting a communication session leg setup request to third communication client 910 on user device 900 in step 12d.
Upon receipt of the communication session leg setup request of step 12d by third communication client 910, third communication client 910 transmits a communication session leg setup response to call control system 106 in step 12e.
Upon receipt of the communication session leg setup response of step 12e at call control system 106, call control system establishes a communication session 1202 between remote party device 126 and third communication client 910 on user device 900.
Call control system 106 tears down communication session established between remote party device 126 and first communication client 710 in step 12f.
Note that in the embodiments described above in relation to Figure 12 even if the user of user device 700 terminates (i.e. 'hangs-up') the communication session 1200 currently being conducted between first communication client 710 and remote party device 126 after entering user input in step 12b, call control system 106 still transmits the communication session leg setup request of step 12d and transfer of the terminated communication session can still take place.
Note that in the embodiments of Figure 12 described above, no further user input is required on user device 900 after step 12b for the communication session to be transferred to third communication client 910. In embodiments, upon receipt of the user input of step 12b, third communication client 910 on user device 900 is configured into an auto-answer mode in relation to the initiated communication session transfer such that upon receipt of the communication session leg setup request of step 12d by third communication client 910, third communication client 910 transmits the communication session leg setup response of step 12e to call control system 106 without requiring any further user input.
Similarly to alternative embodiments described above in relation to Figure 1 1, in alternative embodiments relating to Figure 12, some of the logic associated with the communication session transfer operation is provided by a user's device, rather than by call control system 106. In such embodiments, user device 900 maintains a set of identifiers for one or more communication clients associated with the user and inserts one or more of such identifiers into the communication session transfer request of step 12c. In such embodiments, call control system 106 need not maintain user database 180 with user entries for a plurality of users containing a set of identifiers for one or more communication clients associated with each user, nor perform lookup in any such database because the relevant communication clients associated with the user (in this case first communication client 710 and third communication client 910) are identified in the communication session transfer request of step 12c. Call control system 106 can thus transmit the communication session let setup request of step 12d on the basis of information contained in the communication session transfer request of step 12c. In such embodiments, user device 700 may insert further logic into the communication session transfer request of step 12c in order to instruct call control system 106 on the communication session transfer. In such alternative embodiments, the transfer is conducted on the basis of a preconfigured data set, specific to the user, which identifies one or more of the plurality of communication clients associated with the user. In these embodiments, the preconfigured data set is provided to call control system 106 by user device 900.
In embodiments, a communication session transfer request transmitted to call control system 106 from a user device comprises an identifier for the user. Upon receipt of such a communication session transfer request, call control system 106 extracts the user identifier from the received communication session transfer request and performs a lookup in user database 180. The lookup results in call control system receiving information as to the communication clients associated with that user and is thus able to contact such communication clients accordingly.
In embodiments, the at least one displayed communication session transfer option comprises a set of one or more identifiers for communication clients in the plurality and the selection comprises selection by the user of an identifier for the another communication client in the plurality from the set. A diagram of user device 700 configured to display a plurality of communication session transfer options to the user is depicted in Figure 15 according to embodiments.
Button 961a includes the text 'switch to ccl ' indicating to the user that selecting this button will allow them to switch to communication client number 1. The arrow form of the button which points to the right, indicates to the user that they should touch the button located in position 961a and slide the button to the right to position 961b in order to initiate transfer of the communication session to communication client number 1.
Button 962a includes the text 'switch to cc2' indicating to the user that selecting this button will allow them to switch to communication client number 2. The arrow form of the button which points to the right, indicates to the user that they should touch the button located in position 962a and slide the button to the right to position 962b in order to initiate transfer of the communication session to communication client number 2.
Button 963a includes the text 'switch to cc3' indicating to the user that selecting this button will allow them to switch to communication client number 3. The arrow form of the button which points to the right, indicates to the user that they should touch the button located in position 963a and slide the button to the right to position 963b in order to initiate transfer of the communication session to communication client number 3.
It may be inconvenient for a user to have to remember which of their communication clients is communication client number 1, which of their communication clients is communication client number 2, etc. Therefore, in embodiments, one or more of the identifiers displayed for communication clients are user-configurable, for example communication client number 1 could be user- configured to display as 'my iPhone™', communication client number 2 could be user-configured to display as 'my Skype communication client number 3 could be user-configured to display as 'my tablet', etc.
In embodiments, rather than a user selecting a generic initiate communication session transfer option displayed to the user, a user selects a particular communication client from a set of a plurality of communication session transfer options displayed to the user. In such embodiments, a communication session transfer request transmitted to call control system 106 from the user device comprises an identifier for the particular communication client associated with the user which the user selected. Upon receipt of such a communication session transfer request, call control system 106 extracts the communication client identifier from the received communication session transfer request and performs a lookup in user database 180. The lookup in database 180 results in call control system 106 identifying which communication client associated with that user the user selected and is thus able to transmit a single communication session leg setup request to the particular communication client selected by the user, rather than transmitting multiple communication session leg setup requests to multiple communication clients associated with the user.
Figure 16 shows a front view of a user device 1600 comprising a touch-screen user interface 1604 according to embodiments. In these embodiments, the user of user device 1600 is currently conducting a communication session with a remote party device so an in-call screen application is running on mobile telephony device 1600. The in-call screen application is displaying an in-call screen on touch-screen user interface 1604. The in-call screen displayed on touch-screen user interface 1604 includes a number of soft-keys which are responsive to user touches to provide input to the in-call screen application running on user device 1600. The soft-keys include dial-pad digits 1, 2, ... to 0 and the * ('star') and # ('hash') symbols which are used for entering telephone dialling numbers. The soft-keys also include several other soft- keys 1616, 1618, 1620, 1622, 1624, 1626 which are operable to initiate other in-call functionality in response to user input, for example end-call, call-hold, mute, speaker- phone, and show/hide dial-pad operations.
In embodiments, one or more touch-sensitive screen regions which are operable to receive selection input from the user are configured on touch-screen user interface 1604 of user device 1600. In embodiments, the one or more touch- sensitive screen regions are configured as an overlay portion 1732 over at least a part of a screen displayed by user device 1600.
Figure 17 shows a front view of user device 1600 according to embodiments. In these embodiments, overlay portion 1732 comprises several touch-sensitive screen regions 1750, 1752 and 1754 which are operable to initiate one or more communication session transfer operations independently of the in-call screen application in response to user input via touch-sensitive screen regions 1750, 1752, 1754. This means that user input via any of touch-sensitive screen regions 1750, 1752, 1754 will not be passed to the in-call screen application displaying the in-call screen below the overlay portion, but rather will lead to transmittal of an appropriate communication session transfer request from user device 1600 to call control system 106.
In embodiments, button 1750 includes the text 'switch to ccl ' (not shown) indicating to the user that selecting this button will allow them to switch to a communication client number 1. In embodiments, button 1752 includes the text 'switch to cc2' (not shown) indicating to the user that selecting this button will allow them to switch to a communication client number 2. In embodiments, button 1754 includes the text 'switch to cc3' (not shown) indicating to the user that selecting this button will allow them to switch to a communication client number 3.
In embodiments, configuring of the user interface comprises configuring one or more touch-sensitive screen regions which are operable to receive user input in the form of a sliding action in a given direction over an overlay portion, for example overlaid over an in-call screen display, beginning at one of the touch-sensitive screen regions.
In embodiments, call control system 106 receives availability information from one or more communication clients and/or devices associated with a user and stores the received availability information in database 180.
In embodiments, call control system 106 retrieves availability information from database 180 which is indicative of which communication clients in the plurality of communication clients associated with the user are currently available for transfer of a communication session and transmits the retrieved availability information to one or more user devices associated with the user.
When availability information is received at a user device associated with the user, the user device is aware of which communication clients in the plurality are currently available for transfer of a communication session, including communication clients on other devices associated with the user. A user device can thus configure its user interface on the basis of the received availability information.
In embodiments, a user device configures its user interface to display only communication session transfer options associated with communication clients which are currently available. This helps a user to avoid attempting to transfer a communication session to a communication session which is currently unavailable.
In embodiments, a user device configures its user interface to display available communication clients in a different display mode from configuration for an unavailable communication client. For example, unavailable communication clients may still be presented as communication session transfer options, but displayed as 'greyed-out' communication session transfer options.
In embodiments, call control system 106 transmits a command to a user device associated with a user to configure itself into an auto-answer mode in relation to an initiated communication session transfer. Such embodiments allow a communication session to be transferred to a different communication client without the need for receipt of further user input from the user such as selection of an 'accept transfer' button on a user interface of the user device.
In embodiments, a command transmitted to a user device instructing the user device to configure itself into an auto-answer mode comprises an identifier for a communication client on the device which is to enter an auto-answer mode in relation to the initiated communication session transfer. Such embodiments allow a communication session to be transferred to a particular communication client without the need for receipt of further user input from the user.
In embodiments, configuring the user interface on a user device comprises displaying a set of one or more communication clients associated with the user via which communication sessions are currently being conducted. A user can therefore keep track of communication sessions, including multiple concurrent communication sessions which are being conducted via their communication clients.
Embodiments comprise receiving, during the established communication session, a communication session setup request associated with setup of a further communication session. In such embodiments, the displayed at least one communication session transfer option comprises an option to initiate transfer of the further communication session to one or more communication clients associated with the user via which communication sessions are not currently being conducted. A user can thus choose a communication client to transfer the further communication session to.
Embodiments comprise receiving, during the established communication session, a communication session setup request associated with setup of a further communication session. In such embodiments, the displayed at least one communication session transfer option comprises an option to initiate transfer of the established communication session to one or more communication clients associated with the user via which communication sessions are not currently being conducted. A user can thus choose a communication client to transfer the established communication session to.
Such embodiments could be useful for example if a user is conducting a call say on his home phone with remote party 1 and receives a further incoming call from a remote party 2 (say his mother-in-law). The user can see from the display configured on his home phone that his tablet user device is not currently being used for conducting a communication session and decides to transfer the further incoming call to his tablet user device. Another user (for example the user's wife) can then take the further incoming call from remote party 2 (her mother) on the tablet user device.
Alternatively, the user can decide to transfer the further incoming call from remote party 2 to his home phone and talk to remote party 2 himself and transfer the current call to his tablet user device where his wife or another family member can talk to remote party 1.
In embodiments, configuring the user interface on a user device comprises displaying a set of one or more communication clients associated with the user via which communication sessions are currently being conducted on a non-telephony user device such as a PC. In such embodiments, at least one communication session transfer option may be configured on the non-telephony user device. Such embodiments could for example be useful to allow a secretary to monitor calls that her boss is conducting and transfer calls between his various devices on his behalf.
Embodiments comprise transferring an established communication session in a telecommunications network, the communication session being established between one of a plurality of communication clients associated with a user and a remote device associated with a remote party. Such embodiments comprise at a device associated with the user:
maintaining a set of one or more communication session triggering conditions; in response to detecting that at least of the one or more communication session triggering conditions has occurred, transmitting, to a call control system located in the signalling path for the established communication session, a communication session transfer request, the transmitted communication session transfer request being operable to instruct the call control system to initiate transfer of the established communication session from the one of the communication clients in the plurality to at least another communication client in the plurality.
In embodiments, the one or more triggering conditions comprise the availability of a predetermined wireless access point via a communication client in said plurality of communication clients associated with the user.
In embodiments, the one or more triggering conditions are configurable by the user.
Remote party device 126 has been described above as being provided with communication services via circuit-switched network 102. Remote party device 126 can equally be provided with communication services via one or more other networks, including cellular networks, non-cellular networks, IP networks, IP Multimedia
Subsystem (IMS) networks, etc.
Any or all functions of processor 702 may be carried out by computer software and/or firmware, communication session transfer application software and/or the operating system of the user device. In embodiments described above in relation to Figure 1, telecommunications network 1 comprises a circuit-switched telecommunications network part 102 and a packet-switched network part 104. Embodiments may equally apply in a telecommunications network 1 which comprises only a circuit-switched telecommunications network part 102 or only a packet-switched network part 104. Similarly, embodiments may equally apply in a telecommunications network 1 which comprises only a cellular part, only a PSTN part, only a packet-switched part, etc.
1. A method of transferring an established communication session in a telecommunications network, the communication session being established between one of a plurality of communication clients associated with a user and a remote device associated with a remote party, the method comprising, at a call control system located in the signalling path for the established communication session:
maintaining a user database containing user entries for a plurality of users, each user entry comprising a set of identifiers for one or more communication clients associated with a respective user; and
in response to receipt of the communication session transfer request, performing a lookup in the user database, the lookup identifying the at least another communication client in the plurality of communication clients associated with the user,
wherein the transmittal of the communication session leg setup request to the at least another communication client is carried out in response to the lookup.
3. A method according to claim 1 or 2, wherein the received communication session transfer request comprises an identifier for the at least another communication client, and wherein the transmittal of the communication session leg setup request to the at least another communication client is carried out in response to receipt of the identifier for the another communication client by the call control system.
4. A method according to any preceding claim, wherein the initiating comprises transmitting a communication session leg setup request to the at least another communication client.
5. A method according to any preceding claim, wherein the initiating comprises transmitting communication session leg setup requests to at least two communication clients in the plurality of communication clients associated with the user.
6. A method according to claim 5, wherein the received communication session transfer request comprises an identifier for the user, and
wherein the transmittal of the communication session leg setup requests to the at least two communication clients in the plurality of communication clients associated with the user is carried out in response to receipt of the identifier for the user by the call control system and lookup of the identifier for the user in a user database containing user entries for a plurality of users, each user entry comprising a set of identifiers for one or more communication clients associated with the respective user.
7. A method according to preceding claim, the method comprising:
receiving a communication session setup response from the at least another communication client;
establishing a communication session between the another communication client and the remote device; and
tearing down the communication session established between the one communication client and the remote device.
8. A method according to any of claims 1 to 6, the method comprising: receiving a communication session setup response from the another communication client;
maintaining the communication session established between the one communication client and the remote device.
9. A method according to any preceding claim, the method comprising: receiving availability information from one or more communication clients and/or devices associated with the user; and
storing the received availability information in an availability database.
10. A method according to claim 9, the method comprising retrieving from the availability database availability information indicative of which communication clients in the plurality of communication clients associated with the user are currently available for transfer of a communication session; and
transmitting the retrieved availability information to the device.
11. A method according to any preceding claim, wherein the one communication client and the another communication client are co-located on the device.
12. A method according to any of claims 1 to 10, wherein the one communication client is located on the device and the another communication client is located on a further device associated with the user.
13. A method according to any of claims 1 to 10, wherein the another communication client is located on the device and the one communication client is located on a further device associated with the user.
14. A method according to any preceding claim, the method comprising transmitting a command to a device associated with the user to configure itself into an auto-answer mode in relation to the initiated communication session transfer.
15. A method according to claim 14, wherein the command comprises an identifier for a communication client on the device which is to enter an auto-answer mode in relation to the initiated communication session transfer.
16. A method according to any preceding claim, wherein a communication client comprises one or more of:
a cellular radio communication client,
a non-cellular radio communication client,
a Voice over Internet Protocol (VoIP) communication client, and
a Plain Old Telephone Service (POTS) communication client.
17. A method according to any preceding claim, wherein at least two of the communication clients in the plurality of communication clients associated with the user are co-located on the device.
18. A method according to any preceding claim, wherein at least two of the communication clients in the plurality of communication clients associated with the user are co-located on a further device associated with the user.
19. A method according to any preceding claim, wherein the initiating comprises transmitting an instruction to the at least another communication client to activate an alert function which is distinctive for a communication session transfer scenario.
20. A method according to claim 19, wherein the alert function comprises a distinctive ringing function.
21. A method according to claim 19 or 20, wherein the alert function comprises a distinctive display function.
22. Apparatus for use in transferring an established communication session in a telecommunications network, the communication session being established between one of a plurality of communication clients associated with a user and a remote device associated with a remote party, the apparatus comprising a processing system adapted to, at a call control system located in the signalling path for the established communication session:
23. Computer software adapted to perform a method of transferring an established communication session in a telecommunications network, the communication session being established between one of a plurality of communication clients associated with a user and a remote device associated with a remote party, the method comprising, at a call control system located in the signalling path for the established communication session:
initiate transfer of the established communication session from the one communication client in the plurality of communication clients to an another communication client in the plurality of communication clients, the transfer being conducted on the basis of a preconfigured data set, specific to the user, identifying one or more of the plurality of communication clients associated with the user.
24. A method of transferring an established communication session in a telecommunications network, the communication session being established between one of a plurality of communication clients associated with a user and a remote device associated with a remote party, the method comprising, at a device associated with the user:
25. A method according to claim 24, wherein at least two of the communication clients in the plurality are co-located on the device.
26. A method according to claim 24 or 25, wherein at least two of the communication clients in the plurality are co-located on a further device associated with the user.
27. A method according to any of claims 24 to 26, wherein the at least one displayed communication session transfer option comprises an identifier for the another communication client in the plurality.
28. A method according to any of claims 24 to 27, wherein the at least one displayed communication session transfer option comprises a set of one or more identifiers for communication clients in the plurality and the selection comprises selection by the user of an identifier for the another communication client in the plurality from the set.
29. A method according to any of claims 24 to 28, the method comprising at the device associated with the user:
maintaining a set of identifiers for one or more communication clients associated with the user; and
inserting into the transmitted communication session transfer request at least one identifier from the set.
30. A method according to any of claims 24 to 29, wherein the instructing of the call control system to initiate transfer of the established communication session comprises instructing the call control system to initiate setup of a communication session leg to the another communication client.
31. A method according to claim 30, wherein the transmitted communication session transfer request comprises an identifier for the another communication client, and
wherein initiating the setup is carried out in response to receipt of the identifier for the another communication client by the call control system.
32. A method according to any of claims 24 to 31, wherein the instructing of the call control system to initiate transfer of the established communication session comprises instructing the call control system to initiate setup of communication session legs to a plurality of communication clients associated with the user.
33. A method according to claim 32, wherein the transmitted communication session transfer request comprises an identifier for the user, and
wherein initiating the setup is carried in response to receipt of the identifier for the user by the call control system.
34. A method according to any of claims 24 to 33, the method comprising receiving, from the call control system, availability information indicative of which communication clients in the plurality are currently available for transfer of a communication session,
wherein the configuring is carried out on the basis of the received availability information.
35. A method according to claim 34, wherein configuration for an available communication client is carried out in a different display mode from configuration for an unavailable communication client.
36. A method according to any of claims 24 to 35, wherein the one communication client and the another communication client are co-located on the device.
37. A method according to claim 36, wherein the displayed at least one transfer option comprises an option to push the communication session established on the one communication client on the device to the another communication client on the device.
38. A method according to claim 36, wherein the displayed at least one transfer option comprises an option to pull the communication session established on the one communication client on the device from another communication client on the device.
39. A method according to any of claims 24 to 35, wherein the one communication client is located on the device and the another communication client is located on a further device associated with the user,
40 A method according to claim 39, wherein the at least one transfer option comprises an option to push the communication session established on the one communication client on the device to another communication client on the further communication device.
41. A method according to any of claims 24 to 35, wherein the another communication client is located on the device and the one communication client is located on a further device associated with the user.
42 A method according to claim 41, wherein the at least one transfer option comprises an option to pull the communication session established on the one communication client on the device to another communication client on the further communication device.
43. A method according to any of claims 24 to 42, the method comprising configuring the device into an auto-answer mode in relation to the initiated communication session transfer.
44. A method according to any of claims 24 to 43, wherein the user interface comprises a touch-screen user interface and the configuring of the user interface comprises configuring one or more touch-sensitive screen regions which are operable to receive the selection input from the user.
45. A method according to claim 44, wherein the one or more touch- sensitive screen regions are configured as an overlay portion over at least a part of a screen displayed by the device.
46. A method according to claim 45, wherein the configuring of the user interface comprises configuring one or more touch-sensitive screen regions which are operable to receive user input in the form of a sliding action in a given direction over the overlay portion beginning at one of the touch-sensitive screen regions.
47. A method according to claim 45 or 46, wherein the screen displayed by the device comprises an in-call screen.
48. A method according to any of claims 24 to 47, wherein one or more of the identifiers for the another communication client and/or the one or more identifiers in the set are user-configurable.
49. A method according to any of claims 24 to 48, wherein a communication client comprises one or more of:
50. A method according to any of claims 24 to 49, the method comprising configuring the user interface on the device to display a set of one or more communication clients associated with the user via which communication sessions are currently being conducted.
51. A method according to claim 50, the method comprising;
receiving, during the established communication session, a communication session setup request associated with setup of a further communication session,
wherein said displayed at least one communication session transfer option comprises an option to initiate transfer of said further communication session to one or more communication clients associated with the user via which communication sessions are not currently being conducted.
52. A method according to claim 50 or 51, the method comprising;
wherein said displayed at least one communication session transfer option comprises an option to initiate transfer of said established communication session to one or more communication clients associated with the user via which communication sessions are not currently being conducted.
53. Apparatus for use in transferring an established communication session in a telecommunications network, the communication session being established between one of a plurality of communication clients associated with a user and a remote device associated with a remote party, the apparatus comprising a processing system adapted to, at a device associated with the user:
transmit, to a call control system located in the signalling path for the established communication session, a communication session transfer request, the transmitted communication session transfer request being operable to instruct the call control system to initiate transfer of the established communication session from the one of the communication clients in the plurality to another communication client in the plurality,
54. Computer software adapted to perform a method for transferring an established communication session in a telecommunications network, the communication session being established between one of a plurality of communication clients associated with a user and a remote device associated with a remote party, the method comprising, at a device associated with the user: configuring a user interface on the device to display at least one communication session transfer option to the user;
55. A method of transferring an established communication session in a telecommunications network, the communication session being established between one of a plurality of communication clients associated with a user and a remote device associated with a remote party, the method comprising, at a device associated with the user:
56. A method according to claim 55, wherein the one or more triggering conditions comprises the availability of a predetermined wireless access point via a communication client in said plurality of communication clients associated with the user.
57. A method according to claim 55 or 56, wherein the one or more triggering conditions are configurable by the user.
PCT/GB2013/050476 2012-02-27 2013-02-27 Methods and apparatus for transferring an established communication session in a telecommunications network WO2013128178A1 (en)
US201261603870P true 2012-02-27 2012-02-27
US61/603,870 2012-02-27
EP13713946.5A EP2820833B1 (en) 2012-02-27 2013-02-27 Methods and apparatus for transferring an established communication session in a telecommunications network
GB1415073.4A GB2515207B (en) 2012-02-27 2013-02-27 Methods and apparatus for transferring an established communication session in a telecommunications network
EP18201172.6A EP3451643A1 (en) 2012-02-27 2013-02-27 Methods and apparatus for transferring an established communication session in a telecommunications network
US14/470,758 US9438739B2 (en) 2012-02-27 2014-08-27 Methods and apparatus for transferring an established communication session in a telecommunications network
US15/232,614 US9813561B2 (en) 2012-02-27 2016-08-09 Methods and apparatus for transferring an established communication session in a telecommunications network
US14/470,758 Continuation US9438739B2 (en) 2012-02-27 2014-08-27 Methods and apparatus for transferring an established communication session in a telecommunications network
WO2013128178A1 true WO2013128178A1 (en) 2013-09-06
ID=48045579
PCT/GB2013/050476 WO2013128178A1 (en) 2012-02-27 2013-02-27 Methods and apparatus for transferring an established communication session in a telecommunications network
US (2) US9438739B2 (en)
EP (2) EP2820833B1 (en)
GB (2) GB2515207B (en)
WO (1) WO2013128178A1 (en)
2013-02-27 EP EP13713946.5A patent/EP2820833B1/en active Active
2013-02-27 GB GB1415073.4A patent/GB2515207B/en active Active
2013-02-27 GB GBGB1905531.8A patent/GB201905531D0/en active Pending
2013-02-27 EP EP18201172.6A patent/EP3451643A1/en active Pending
2013-02-27 WO PCT/GB2013/050476 patent/WO2013128178A1/en active Application Filing
2014-08-27 US US14/470,758 patent/US9438739B2/en active Active
2016-08-09 US US15/232,614 patent/US9813561B2/en active Active
GB201905531D0 (en) 2019-06-05
GB2515207A (en) 2014-12-17
EP3451643A1 (en) 2019-03-06
GB2515207B (en) 2019-06-05
GB201415073D0 (en) 2014-10-08
US9813561B2 (en) 2017-11-07
US20160352914A1 (en) 2016-12-01
US20140369484A1 (en) 2014-12-18
EP2820833B1 (en) 2019-01-02
EP2820833A1 (en) 2015-01-07
US9438739B2 (en) 2016-09-06
EP2479969A1 (en) 2012-07-25 A network abstraction gateway and corresponding method to abstract an endpoint
US8270582B1 (en) 2012-09-18 Methods and systems for routing calls
US7986775B2 (en) 2011-07-26 Method for realizing ring back tone in communication system
Ref document number: 13713946
Ref document number: 1415073.4
Ref document number: 1415073
Free format text: PCT FILING DATE = 20130227
Ref document number: 2013713946