EP2355479A1 - Call transfer using a direct short-range information exchange between the transferor and the transfer target - Google Patents
Call transfer using a direct short-range information exchange between the transferor and the transfer target Download PDFInfo
- Publication number
- EP2355479A1 EP2355479A1 EP10166494A EP10166494A EP2355479A1 EP 2355479 A1 EP2355479 A1 EP 2355479A1 EP 10166494 A EP10166494 A EP 10166494A EP 10166494 A EP10166494 A EP 10166494A EP 2355479 A1 EP2355479 A1 EP 2355479A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- telephony device
- wireless
- wireless handheld
- devices
- target local
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Withdrawn
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/58—Arrangements for transferring received calls from one subscriber to another; Arrangements affording interim conversations between either the calling or the called party and a third party
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/02—Services making use of location information
- H04W4/029—Location-based management or tracking services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
- H04M1/725—Cordless telephones
- H04M1/72502—Cordless telephones with one base station connected to a single line
- H04M1/72505—Radio link set-up procedures
- H04M1/72513—On hold, intercom or transfer communication modes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2203/00—Aspects of automatic or semi-automatic exchanges
- H04M2203/10—Aspects of automatic or semi-automatic exchanges related to the purpose or context of the telephonic communication
- H04M2203/1091—Fixed mobile conversion
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2207/00—Type of exchange or network, i.e. telephonic medium, in which the telephonic communication takes place
- H04M2207/18—Type of exchange or network, i.e. telephonic medium, in which the telephonic communication takes place wireless networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2207/00—Type of exchange or network, i.e. telephonic medium, in which the telephonic communication takes place
- H04M2207/20—Type of exchange or network, i.e. telephonic medium, in which the telephonic communication takes place hybrid systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2250/00—Details of telephonic subscriber devices
- H04M2250/02—Details of telephonic subscriber devices including a Bluetooth interface
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2250/00—Details of telephonic subscriber devices
- H04M2250/06—Details of telephonic subscriber devices including a wireless LAN interface
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/42229—Personal communication services, i.e. services related to one subscriber independent of his terminal and/or location
- H04M3/42263—Personal communication services, i.e. services related to one subscriber independent of his terminal and/or location where the same subscriber uses different terminals, i.e. nomadism
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/42314—Systems providing special services or facilities to subscribers in private branch exchanges
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/02—Services making use of location information
Definitions
- the present application relates to wireless handheld telephony devices and, more particularly, to systems and methods for transferring an end of an ongoing communication session from a first telephony device to a second telephony device.
- a telephony device such as a wireless telephone
- a second telephony device such as a desk telephone
- the ability to make such transfers can, for example, improve the security of the call session (e.g., the security of the communications from eavesdroppers), the comfort of the user, the economics of the telephone call (such, for example, where a wireless telephone subscription disfavors extended wireless use) and other factors.
- Some systems and devices for transferring calls from wireless to other telephony devices do exist. However, they tend to be less flexible, secure, dependable, and user friendly than they might be. There is need for improvement.
- the disclosure provides a method of transferring to a second telephony device an end of a communications session previously established between a wireless handheld telephony device and at least one third telephony device, where the wireless handheld telephony device comprises at least one wireless signal receiver, at least one wireless signal transmitter, at least one data processor, and media readable by the at least one data processor comprising coded program instructions.
- Such methods can, for example, comprise: while maintaining the previously-established communications session between the wireless handheld telephony device and the at least one third telephony device, receiving direct from one or more target local telephony devices one or more wireless signals representing data useful for establishing communications between the one or more target local telephony devices and a call server managing the end of the previously-established communications session associated with the wireless handheld telephony device; using the wireless signals received direct from the one or more target local telephony devices, instructing the call server to establish a communications session between a selected one of the at least one target local telephony devices and the at least one third telephony device; and upon establishment of a communications session between the selected local telephony device and the at least one third telephony device, terminating the previously-established communications session between the wireless handheld telephony device and the at least one third telephony device.
- the disclosure herein provides a wireless handheld telephony device comprising at least one wireless signal receiver, at least one wireless signal transmitter, at least one data processor, and media readable by the at least one data processor comprising coded program instructions adapted for enabling the wireless handheld telephony device to cause transfer to a second telephony device of an end of a communications session previously established between the wireless handheld telephony device and at least one third telephony device.
- the wireless handheld telephony device can, for example, do so using the method described above.
- Figure 1 shows a schematic diagram of an example system for managing telephone and other communications in accordance with the disclosure herein;
- Figures 2-5 show schematic diagrams of example embodiments of details of a system such as that shown in Figure 1 ;
- Figure 6 shows a schematic diagram of an example system for managing telephone and other communications in accordance with the disclosure herein;
- Figure 7 provides schematic diagrams of wireless handheld telephony devices suitable for use in implementing the systems, devices, and methods disclosed herein;
- Figure 8 shows a schematic flow diagram of an example of a method of transferring an ongoing communication in accordance with the disclosure herein;
- Figure 9 is a signaling diagram generally showing an example of a transfer of a communications session in accordance with the disclosure herein.
- FIGS. 10A - 10C are schematic diagrams of examples of systems for managing telephone and other communications in accordance with the disclosure herein.
- Embodiments of the present application are not limited to any particular operating system, mobile device architecture, server architecture, or computer programming language.
- the present application relates to the control and management of communications.
- calls in the description of example embodiments below, it will be appreciated that the described systems and methods are applicable to session-based communications in general and not limited to voice calls, and that references to "calls" are intended to refer to session-based communications sessions of any type, including voice, data or text communications, unless clearly indicated otherwise by context. It will also be appreciated that the systems and methods may not be limited to sessions and may be applicable to messaging-based communications in some embodiments.
- System 10 includes an enterprise or business communications system 20, which may include a local area network (LAN).
- LAN local area network
- the enterprise or business system 20 may be referred to as an enterprise network 20.
- enterprise network 20 may include more than one network and may be located in multiple geographic areas in some em bodim ents.
- Enterprise network 20 may be connected, for example through a firewall 22, to a wide area network (WAN) 30, such as the Internet.
- Enterprise network 20 may also be connected to a public switched telephone network (PSTN) 40 via direct inward dialing (DID) trunks or primary rate interface (PRI) trunks.
- PSTN public switched telephone network
- DID direct inward dialing
- PRI primary rate interface
- Enterprise network 20 may also communicate with a public land mobile network (PLMN) 50, which may also be referred to as a wireless wide area network (WWAN) or, in some cases, a cellular network. Connection with the PLMN 50 may be made via a relay 26, as known in the art.
- PLMN public land mobile network
- WWAN wireless wide area network
- relay 26 as known in the art.
- Enterprise network 20 may also provide one or more wireless local area networks (WLANs) 32a featuring wireless access points.
- WLANs 32 may exist outside enterprise network 20.
- WLAN 32b may be connected to WAN 30.
- System 10 may include and/or interact with a number of enterprise-associated mobile devices 11 (only one shown).
- Mobile device(s) 11 may include devices equipped for cellular communication through the PLMN 50, mobile devices equipped for Wi-Fi communications over one of the WLANs 32, and/or dual-mode devices capable of both cellular and WLAN communications.
- WLANs 32 may be configured in accordance with one of the IEEE 802.11specifications.
- the mobile devices 11 include one or more radio transceivers and associated processing hardware and software to enable wireless communications with the PLMN 50 and/or one of the WLANs 32.
- the PLMN 50 and mobile devices 11 may be configured to operate in compliance with any one or more of a number of wireless protocols, including GSM, GPRS, CDMA, EDGE, UMTS, EvDO, HSPA, 3GPP, or a variety of others. It will be appreciated that the mobile device 11 may roam within the PLMN 50 and across PLMNs, in for example any of a variety of known manners, as the user moves.
- the dual-mode mobile devices 11 and/or enterprise network 20 are configured to facilitate roaming between the PLMN 50 and a WLAN 32, and are thus capable of seamlessly transferring sessions (such as voice calls) from a connection with the cellular interface of the dual-mode device 11 to the WLAN 32 interface of the dual-mode device 11, and vice versa.
- Enterprise network 20 typically includes a number of networked servers, computers, and other devices.
- enterprise network 20 may connect one or more desktop or laptop computers 15 (one shown). The connection may be wired or wireless in some embodiments.
- Enterprise network 20 may also connect to one or more digital telephone sets 17 (one shown).
- Enterprise network 20 may include one or more mail servers, such as mail server 24, for coordinating the transmission, storage, and receipt of electronic messages for client devices operating within enterprise network 20.
- Typical mail servers include the Microsoft Exchange ServerTM and the I BM Lotus DominoTM server.
- Each user within the enterprise typically has at least one user account within enterprise network 20.
- message address information such as an e-mail address.
- Messages addressed to a user message address are stored on enterprise network 20 in the mail server 24.
- the messages may be retrieved by the user using a messaging application, such as an e-mail client application.
- the messaging application may be operating on a user's computer 15 connected to enterprise network 20 within the enterprise.
- the user may be permitted to access stored messages using a remote computer, for example at another location via the WAN 30 using a VPN connection.
- the user may also compose and send messages addressed to others, within or outside enterprise network 20.
- the messaging application causes the mail server 24 to send a composed message to the addressee, often via the WAN 30.
- the relay 26 serves to route messages received over the PLMN 50 from the mobile device 11 to the corresponding enterprise network 20.
- the relay 26 also pushes messages from enterprise network 20 to the mobile device 11via the PLMN 50.
- enterprise network 20 also includes an enterprise server 12.
- the enterprise server 12 can function to redirect, copy, or relay incoming e-mail messages addressed to a user's e-mail address within enterprise network 20 to the user's mobile device 11and to relay incoming e-mail messages composed and sent via the mobile device 11 out to the intended recipients within the WAN 30 and/or elsewhere.
- enterprise server 12 and relay 26 together can facilitate "push" e-mail service for the mobile device 11 enabling the user to send and receive e-mail messages using the mobile device 11 as though the user were connected to an e-mail client within enterprise network 20 using the user's enterprise-related e-mail address, for example on computer 15.
- enterprise network 20 can include one or more Private Branch exchanges (although in various embodiments the PBX(s) may be standard PBX(s) or IP-PBX(s), for simplicity the description below uses the term PBX to refer to both) 16 having a connection with the PSTN 40 for routing incoming and outgoing voice calls to and from digital and/or analog telephones or other telephony devices for the enterprise.
- PBX 16 is connected to the PSTN 40 via DID trunks or PRI trunks, for example.
- PBX 16 may use ISDN signaling protocols for setting up and tearing down circuit-switched connections through the PSTN 40 and related signaling and communications.
- PBX 16 may be connected to one or more conventional analog telephones 19.
- PBX 16 may also be connected to enterprise network 20 and, through it, to telephone terminal devices, such as digital telephone sets 17, softphones operating on computers 15, etc.
- each individual may have an associated extension number, sometimes referred to as a PNP (private numbering plan), or direct dial phone number.
- Calls outgoing from PBX 16 to the PSTN 40 or incoming from the PSTN 40 to PBX 16 are typically circuit-switched calls.
- voice calls are often packet-switched calls, for example Voice-over-IP (VoIP) calls.
- VoIP Voice-over-IP
- Enterprise network 20 may include a Service Management Platform (SMP) 18 for performing aspects of messaging or session control, such as call control and advanced call processing features. SMP 18 may, in some cases, also perform some media handling. Collectively SMP 18 and PBX 16 may be referred to as the enterprise communications platform, generally designated 14. It will be appreciated that the enterprise communications platform 14 and, in particular, SMP 18, is implemented on one or more servers having suitable communications interfaces for connecting to and communicating with PBX 16 and/or DID/PRI trunks. Although SMP 18 may be implemented on a stand-alone server, it will be appreciated that it may be implemented into an existing control agent/server as a logical software component. As will be described below, SMP 18 may be implemented as a multi-layer platform.
- SMP Service Management Platform
- enterprise communications platform 14 can implement switching to connect session legs and may provide conversion between, for example, a circuit-switched call and a VolPcall, or connect legs of other media sessions. Such calls/sessions may be set up and modified on behalf of devices 1 1 , 19 and any desired telephony devices, within or outside enterprise network 20, including for example devices 19, 107 connected to PSTN 40.
- the enterprise communications platform 14 provides a number of additional functions including automated attendant, interactive voice response, call forwarding, voice mail, etc. It may also implement certain usage restrictions on enterprise users, such as blocking international calls or 1-900 calls.
- Session Initiation Protocol may be used to set up, manage, and terminate media sessions for voice calls.
- Other protocols may also be employed by the enterprise communications platform 14, for example, Web Services, Computer Telephony Integration (CTI) protocol, Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), and various custom Application Programming Interfaces (APIs), as will be described in greater detail below.
- CTI Computer Telephony Integration
- SIMPLE Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions
- APIs Application Programming Interfaces
- enterprise communications platform 14 may extend the features of enterprise telephony to mobile device(s) 11.
- enterprise communications platform 14 may allow mobile device(s) 11 to perform functions akin to those normally available on a standard office telephone, such as the digital telephone set 17 or analog telephone set 15.
- Example features may include direct extension dialing, enterprise voice mail, conferencing, call transfer, call park, etc.
- enterprise communications platform 14 can further provide functions such as transfer of corresponding ends of existing communications sessions from one or more mobile devices 11to wired telephony devices 19 associated with platform 14.
- FIGS. 2 to 4 show example embodiments of enterprise communications system 14.
- calls or call-centric features
- the architectures and systems depicted and described are applicable to session-based (e.g., voice) communications in general and, in some instances, to text, image, or other messaging-based communications.
- FIG. 2 illustrates an embodiment intended for use in a circuit-switched TDM context.
- PBX 16 is coupled to SMP 18 via PRI connection 60 or other suitable digital trunk.
- PRl connection 60 may include a first PRI connection, a second PRI connection, and a channel service unit (CSU), wherein the CSU is a mechanism for connecting computing devices to digital mediums in a manner that allows for the retiming and regeneration of incoming signals. It will be appreciated that there may be additional or alternative connections between PBX 16 and SMP 18.
- CSU channel service unit
- SMP 18 assumes control over both call processing and the media itself.
- This architecture may be referred to as "First Party Call Control”.
- Many of the media handling functions normally implemented by PBX 16 are handled by SMP 18 in this architecture.
- Incoming calls addressed to any extension or direct dial number within the enterprise, for example, are always first routed to SMP 18. Thereafter, a call leg is established from SMP 18 to the called party within the enterprise, and the two legs are bridged.
- SMP 18 includes a digital trunk interface 62 and a digital signal processing (DSP) conferencing bridge 64.
- DSPconferencing bridge 64 performs the bridging of calls for implementation of various call features, such as conferencing, call transfer, etc.
- Digital trunk interface 62 may be implemented as a plurality of telephonic cards, e.g. Intel Dialogic cards, interconnected by a bus and operating under the control of a processor. Digital trunk interface 62 may also be partly implemented using a processor module such as, for example, a Host Media Processing (HMP) processor.
- HMP Host Media Processing
- SMP 18 may include various scripts 66 for managing call processing.
- Scripts 66 are implemented as software modules, routines, functions, etc., stored in non-volatile memory and executed by the processor of SMP 18.
- Scripts 66 may implement call flow logic, business logic, user preferences, call service processes, and various feature applications.
- FIG. 3 shows another embodiment in which PBX 16 performs the functions of terminating and/or bridging media streams, but call control functions are largely handled by SMP 18.
- SMP 18 may be referred to as a call control server 18.
- This architecture may be referred to as "Third-Party Call Control”.
- Call control server 18 is coupled to PBX 16, for example through the LAN, enabling packet-based communications and, more specifically, IP-based communications.
- communications between PBX 16 and call control server 18 are carried out in accordance with SIP.
- call control server 18 uses SIP-based communications to manage the set up, tear down, and control of media handled by PBX 16.
- the call control server 18 may employ a communications protocol conforming to the ECMA-269 or ECMA-323 standards for Computer Supported Telecommunications Applications (CSTA).
- CSTA Computer Supported Telecommunications Applications
- FIG 4 shows yet another embodiment of enterprise communications system 14. This embodiment reflects the adaptation of an existing set of call processing scripts to an architecture that relies on third-party call control, with separate call control and media handling.
- SMP 18 includes a call processing server 74.
- the call processing server 74 includes the scripts or other programming constructs for performing call handling functions.
- SMP 18 also includes a SIP server 72 and a media server 76.
- the separate SIP server 72 and media server 76 logically separate the call control from media handling.
- SIP server 72 interacts with the call processing server 74 using a computer-implemented communications handling protocol, such as one of the ECMA-269 or ECMA-323 standards. These standards prescribe XML based messaging for implementing Computer Supported Telecommunications Applications (CSTA).
- CSTA Computer Supported Telecommunications Applications
- SIP server 72 interacts with the media server 76 using SIP-based media handling commands.
- SIP server 72 and media server 76 may communicate using Media Server Markup Language (MSML) as defined in IETF document Saleem A., "Media Server Markup Language", Internet Draft, draft-saleem-msml-07, August 7, 2008.
- the media server 76 may be configured to perform Host Media Processing (HMP).
- HMP Host Media Processing
- SMP 18 is a multi-layer platform that includes a protocol layer 34, a services layer 36 and an application layer 38.
- Protocol layer 34 includes a plurality of interface protocols configured for enabling operation of corresponding applications in the application layer 38.
- the services layer 36 includes a plurality of services that can be leveraged by the interface protocols to create richer applications.
- the application layer 38 includes a plurality of applications that are exposed out to the communication devices and that leverage corresponding ones of the services and interface protocols for enabling the applications.
- protocol layer 34 preferably includes protocols which allow media to be controlled separate from data.
- protocol layer 34 can include, among other things, a Session Initiation Protocol or SIP 80, a Web Services protocol 82, an Application Program m ing Interface or API 84, a Computer Telephony Integration protocol or CTI 86, and a Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions or SIMPLE protocol 88.
- interface protocols 80-88 are plug-ins that can interface directly with corresponding servers in enterprise network 20, which will be further described below.
- SIP 80 will be utilized, although it is appreciated that system 10 can operate using the above disclosed or any other suitable protocols.
- SIP is the IETF (Internet Engineering Task Force) standard for multimedia session management, and more specifically is an application-layer control protocol for establishing, maintaining, modifying and terminating multimedia sessions between two or more endpoints.
- SIP protocol 80 includes two interfaces for signaling: SIP-Trunk (hereinafter referred to as "SIP-T”) and SIP-Line (hereinafter referred to as "SIP-L").
- SIP-T interface is utilized when the endpoint is a non-specific entity or not registered (i.e., when communicating between two network entities).
- SIP-L interface is utilized when the endpoint is registered (i.e., when dialing to a specific extension). The specific operation of system 10 utilizing SI P 80 will be described in further detail below.
- SMP 18 also includes a plurality of enablers, among other things, a VolP enabler 90, a Fixed Mobile Convergence or FMC enabler 92, a conference services/call and/or session transfer enabler 94, a presence enabler 96, and an Instant Messaging or I M enabler 98.
- Each of the enablers 90-98 can be used by corresponding services in the services layer 36 that combine one or more of the enablers.
- Each of the applications in the application layer 38 can then be combined with one or more of the services to perform the desired application.
- a phone call service may use the VoIP or PBX enabler
- an emergency response application may use the phone call service, an Instant Messenger service, a video call service, and email service and/or a conference service.
- Application layer 38 may include a conference services application 63 that, together with the conference services enabler 94, enables multiple communication devices (including desk telephones and personal computers) to participate in a conference call through use of a centralized conference server 55.
- Conference server 55 is provided in enterprise network 20 and is in communication with the conference services enabler 94 preferably through SIP protocol 80, although it is recognized that additional protocols that control media separate from data may be appropriate, such as the Web Services protocol 82 or the CTI protocol 86.
- Conference call server 55 is configured for directing media and data streams to and from one or more communication devices (i.e., mobile devices 11, telephones 17, and computers 15).
- FIG. 6 shows, in block diagram form, an example system for transferring an end of a com m unication session from a wireless handheld telephony device 111 to a second telephony device 101 in accordance with the disclosure herein.
- the system comprises one or more wireless handheld telephony device(s) 111, any one or more of which may be engaged in established or ongoing communications with at least one third telephony device 121 through PSTN or other communication cloud or network 115, such as PSTN 40 or PLMN 50 of Figure 1 .
- the system may be a hosted environment, such as a corporate or enterprise environment, or it may be a switching environment.
- Communication cloud 115 may be adapted for carrying voice communications according, for example, to any of the several IP or non-IP protocols described above, or any other suitable protocols or methods.
- communication cloud 115 may comprise or otherwise interact with a PSTN 40 and/or PLMN 50.
- Communication cloud 115 may also be capable of carrying image, text, or other data.
- communication cloud 115 may comprise a WAN 30, such as the Internet.
- Wireless handheld telephony device(s) 111 may be any type of wireless handheld device with telephony capabilities including, but not limited to, cellular telephones, BlackBerryTMdevices, PDAs and other devices described herein. Such wireless handheld telephony devices 111 can facilitate voice telephonic and/or other communications through, for example, wireless call server(s) 105.
- Call server(s) 105 can comprise any systems, processors, and/or other components suitable for use in implementing the systems and functions described herein.
- call server(s) 105 can include any or all suitable components of enterprise network 20, including for example any or all of the components communications platform 14 and/or enterprise server 12.
- communications between wireless handheld telephony devices 111 and at least one third telephony device 121 may be routed through a PBX 16 as, for example, described above in relation to Figure 1 .
- PBX(s) 16 may comprise the service management platform 18 or enterprise communications system 14 described in relation to Figures 1 - 5 ; for simplicity, they are referred to herein simply as PBX(s) 16.
- the at least one third telephony device 121 can include any type of telephony devices suitable for accomplishing the purposes described herein, including, but not limited to, landline or wired telephones, such as VOIP protocol or other digital telephone sets 17, analog telephone sets 15, and/or wireless telephony devices 11 accessible through, for example, wireless call servers 125.
- One or more of such third telephony devices 121 may also be enterprise telephones accessible through, for example, a PBX 116.
- PBX 116 may or may not be the same as PBX 16.
- Wireless call server 125 may or may not be the same as wireless call server 105.
- a user of a wireless handheld telephony device 111 may, in various circumstances, wish to transfer the user's end of a previously-established communication session from the user's wireless handheld telephony device 111 to a second telephony device such as one of target local telephony devices 101.
- a second telephony device such as one of target local telephony devices 101.
- This may be desirable when, for example, the battery on wireless handheld telephony device 111 is low or the user does not wish to drain the battery further, when second telephony device 101 is considered more secure, when wireless audio quality or wireless signal is poor or when the user of wireless handheld telephony device 111 wishes to use some of the functionality available on second telephony device 101.
- Target local telephony devices 101 may be enterprise telephony devices configured to communicate through an intermediary 130 comprising, for example, PBX 16.
- target local telephony device 101 may be a public telephony device and may be configured to communicate through an intermediary 130 which may, for example, comprise a switching environment.
- Target local telephony devices 101 may be wired devices, or they may be connected to intermediary 130 wirelessly such as, for example, through a Wi-Fi connection.
- target local telephony devices 101 may be configured to allow voice communications to be made over the Internet, such as a device equipped with SkypeTM software.
- intermediary 130 may comprise PBX 16. In other embodiments, intermediary 130 may comprise a switching environment. In some embodiments, intermediary 130 may form part of communication cloud 115.
- Each of the one or more target local telephony devices 101 include functionality which will allow wireless handheld telephony device 111 to receive one or more wireless signals directly from the one or more target local telephony devices 101. Such signals can represent data useful for establishing communications between the one or more target local telephony devices 101 and wireless call server 105 which administers or is otherwise associated with wireless handheld telephony device 111.
- such wireless signals may be pushed from the one or more target local telephony devices 101 to any wireless handheld telephony device 111 within communications range of target local telephony device 101.
- each target local telephony device 101 may include hardware, such as a radio or other wireless transmitter, capable of broadcasting such wireless signals.
- target local telephony devices 101 may include BlueToothTM capabilities.
- wireless handheld telephony device(s) 111 may be adapted to receive, interpret, and further process wireless signals broadcast by the one or more target local telephony devices 101 in accordance with this disclosure.
- the wireless signals are transmitted by target local telephony device 101 only when the telephony device 101 is in an idle state (e.g. not in use for an active call session).
- each target local telephony device 101 may include a radio-frequency identification (RFI D) transponder configured to respond to an inquiry signal received wirelessly from a suitably-configured RFID transmitter associated with a wireless handheld telephony device 111 within range of target local telephony device 101.
- RFID D radio-frequency identification
- Wireless signals provided by a particular target local telephony device 101 may be received by all wireless handheld telephony devices 111 within range of the local device, or they may be directed only to a particular user or group of users.
- a user's desk phone may be configured to only send wireless signals to that user's wireless handheld telephony device 111 or to wireless handheld telephony device 111 of users within the same working group.
- a target local telephony device 101 may be configured not to transmit wireless signals to any wireless handheld telephony device 111.
- Figure 7 provides schematic diagrams of wireless handheld telephony devices 11, 111 suitable for use in implementing the systems, devices and methods disclosed herein.
- Figure 7a provides a schematic front view of a wireless handheld telephony device 11, 111
- Figure 7b provides a functional block diagram of components suitable for use in configuring wireless handheld telephony device 11, 111 for the purposes disclosed herein.
- wireless handheld telephony device 11, 111 comprises input means 902 and output means 904.
- Input means 902 can include devices such as keyboard(s) 922, function button(s)/switch(es) 924, microphone(s) 940, and pointing device(s) 926 such as a trackball, thumbwheel, etc. for providing single- or multi-stroke input for building and/or issuing command signals for use by processor(s) 900 as described herein.
- Input means 902 can be configured to provide various forms of input command signals to processor 900 of the handheld device, for local processing and or for output by the processor to one or more of memory(s) 912, output device(s) 904, and/or transmitter 906 for transmission to external devices such as wireless control server 105.
- Output means 904 can include devices such as display(s) 928 and speaker(s) 930 for providing visual and audio outputs, respectively.
- input and output means or devices 902, 904 can be of any types and include any such means or devices suitable for use in accomplishing the purposes described herein. A wide variety of suitable means and devices are now known, and doubtless others will hereafter be developed.
- Output means 904 can be configured to process output signals provided by processor(s) 900 in response to internal processing as described herein, and/or as received from external sources such as wireless control server 105 via antenna 910 and receiver 908.
- wireless handheld telephony device 11, 111 comprises one or more processors 900, input means 902, output means 904, wireless transmitter 906, wireless receiver 908, antenna(s) 910, and memory(s) 912.
- processors 900, wireless transmitters 906, receivers 908, and antennas 910 can be provided for use in implementing digital and/or analog voice, data, and/or command signal and communications processes.
- separate sets of antennas 910, receivers 908, transmitters 906, processors 900, and associated memories 912 can be provided for each of voice and data communications systems, and/or one or more of such components may be used for multiple types of communications using multiple protocols.
- processors, transmitters, receivers, antennas, and memories can be of any types and include means or devices suitable for use in accomplishing the purposes described herein. Awide variety of suitable means and devices are now known, and doubtless others will hereafter be developed.
- Figure 8 shows a flow diagram representing an example of a method 700 for transferring an end of a communications session from a wireless handheld telephony device 111 to a second telephony device, the second telephony device being, for example one of target local telephony devices 101.
- Method 700 is suitable for use, for example, in conjunction with systems 10, 100 of Figures 1 and/or 6 and wireless handheld telephony devices 11, 111 of Figure 7 in implementing the disclosure herein.
- a method 700 can be considered to begin at block 702, where a communication session, such as a voice communication session, has been established between a wireless handheld telephony device 111 and at least one third telephony device 121 through PSTN 40, PLMN 50, or other communications cloud 115.
- Wireless handheld telephony device 111's end of the call session can be controlled by a wireless server 105.
- wireless handheld telephony device 111 receives pulled or pushed wireless signals from one or more target local telephony devices 101.
- Such wireless signals can represent, at least in part, data useful for establishing communications between one or more target local telephony devices 101 and its controlling wireless call server 105.
- Such wireless signals may for example comprise identifying information for each target local telephony device 101, or set of devices 101, such as, for example, extension numbers, telephone name(s) or other identifier(s), or office, cubicle, or other physical location.
- the wireless signals may also include directional information, such as global or relative coordinates, ranges, or compass directions. In some embodiments, the directional information may be useful in providing a directional display displayed on wireless handheld telephony device 111.
- Such signals may also include data useable by a wireless call server 105 controlling wireless handheld telephony device 111's end of the communication session in identifying an intermediary 130 that controls the corresponding target local telephony device(s) 101 , and suitable for use by call server 105 in requesting authentication of one or more selected target local telephony devices 101.
- a list of one or more target local telephony devices 101 can be displayed by or otherwise provided to the user of wireless handheld telephony device 111 through the use of any suitable output display screen 928 of wireless handheld telephony device 111, or other means.
- Such list may include any information suitable for use in identifying to the user the name, location, or distance to target local telephony device(s) 101, including for example some or all of the identifying information which may be included in the wireless signals, or any useful information based thereon.
- such list may include the extension number, telephone name, or office, cubical, or other physical location information for some or all of target local telephony devices 101.
- the list may also include range and/or directional information such as that described above.
- Directional information may be used to the provide the user with, for example, directions to a target local telephony device 101, the distance to one or more of target local telephony devices 101 and/or a map displaying the location of one or more of target local telephony devices 101.
- signals representing data useful for identifying available target local telephony devices 101 can be transmitted to an antenna 910, processed by receiver 908 of wireless handheld telephony device 111, and provided to a processor 900 as shown in Figure 7 .
- Processor 900 can interpret the received and processed signals to provide suitably-configured output signals to a display 928 controlled by the processor 900 in such form that a human user of the device 111 can interpret them as described herein.
- a list of target local telephony devices 101 displayed on wireless handheld telephony device 111 may be sorted in a particular order such as, for example, according to a range or distance from wireless handheld telephony device 111 (e.g. from nearest to farthest). In some embodiments, the list may be sorted according to one or more preferences established by some criteria set, for example, by the user of wireless handheld telephony device 111 or by an administrator. For example, one or more target local telephony devices 101 can be preferred due to type of device and/or functionality offered, public/semi-public/private location or status, security (e.g. the level of encryption), or cost. In some instances, another wireless handheld telephony device may be preferred for battery or other quality reasons.
- the list may include only a predetermined number of telephony devices.
- the list may include only the five (or other convenient number) target local telephony devices 101 which are nearest to wireless handheld telephony device 111.
- Data useful in presenting the list on the display 928 can be temporarily or persistently stored in one or more memories 912 of wireless handheld telephony device 111, for later access and processing by processor 900 in response to input requests received from a user of the device.
- the list of target local telephony devices 101 provided at 706 may include all local telephony devices within effective communications range of wireless handheld telephony device 111. That is, they may include all devices within range of effective communications with respect to the sharing of identifying information at 704, or effective communications of other desired type or purpose.
- the list of target local telephony devices 101 may include only those telephony devices which meet some predetermined criteria.
- the list of target local telephony devices 101 may include only those telephony devices which are within a certain desired or required proximity of wireless handheld telephony device 111, such as within x number of meters (e.g. five meters) of wireless handheld telephony device 111 or on the same floor of a building as wireless handheld telephony device 111.
- certain telephony devices may be excluded from lists of target local telephony devices 101 even though they may match criteria for inclusion (e.g. they may be within five meters of wireless handheld telephony device 111). For example, telephony devices which are currently in use may be excluded from the list of target local telephony devices 101. Other telephony devices may, for example, be excluded from the list by the owner/user of the telephony device or by an administrator based on security, cost, etc.. For example, an employee who may be vacating his desk, office, or cubicle temporarily may be able to indicate that they would prefer not to have any wireless conversations transferred to their office telephone. Similarly, an administrator could decide that only those telephones which are normally unused, such as those located in boardrooms or vacant offices, can be included in the list of target local telephony devices 101.
- the user of wireless handheld telephony device 111 can select second telephony device 101 to which the user's end of the communications session will be transferred, for example, working from a list of target local telephony devices 101 provided at 706.
- Such selection may, for example, be made using any suitable input device 902 such as, for example, a keyboard, touch screen, mouse, trackball or the like, using any suitable input functionality, including, for example, special key commands, interaction with an interactive displayed list, etc. to provide suitably-configured input command signals to the responsible processor(s) 900 of the handheld device.
- the identity of selected target local telephony device 101 and any other useful information derived from the wireless signals at 704 (or otherwise) can be sent to wireless call server 105 which will coordinate the transfer with intermediary 130. This process will be discussed in greater detail in relation to Figure 8 .
- second telephony device 101 may be automatically selected by wireless handheld telephony device 111 based on one or more pre-established rules established by the user of the device 111 and/or any administrator(s) thereof. For example, wireless handheld telephony device 111 may always select the nearest target local telephony device 101, or the nearest such device meeting one or more predetermined criteria.
- a human-interpretable signal may be emitted by second telephony device 101 once the end of the communications session previously assigned to wireless handheld telephony device 111 has been successfully transferred or when the transfer is ready to be completed.
- a signal may, for example, include a visual signal, such as illumination of a light located on the target device, and/or an audio signal, such as a ring tone, buzz, pre-selected melody, or other signal, which may for example have been previously selected or designated by the user of wireless handheld telephony device 111 or by an administrator of wireless handheld telephony device 111 and/or target local telephony device 101.
- An audio signal produced by the target device may be the same audio signal (e.g.
- the signal may indicate to the user that they may now continue their conversation on second telephony device 101.
- the signal may also help the user locate the device they had selected.
- the user of wireless handheld telephony device 111 may unhook or otherwise pick up the target device by, for example, lifting the receiver or pushing a button on the target device to activate a speaker function.
- the user may at that time, if not already otherwise accomplished, cause transfer of the user's end of the communication session to target local telephony device 101 to be completed by, for example, activating an input command from wireless handheld telephony device 111.
- wireless handheld telephony device 111 may, upon establishment of a communications session between selected target local telephony device 101 and the at least one third telephony device 121, display a confirmation message on an output display screen 928 of wireless handheld telephony device 111, and require confirmatory input from the user in order to complete transfer of the user's end of the communication session. It may be required or desirable that the at least one third telephony device 121 be placed on 'hold' or otherwise in a state of suspended communications pending the transfer.
- the user may continue the ongoing conversation (or other communication) with at least one third telephony device 121 using second telephony device 101.
- the portion of the communication session extending to wireless handheld telephony device 111 may be automatically terminated by, for example, intermediary 130.
- the user may 'hang up' or otherwise manually terminate any continuing call session processes in progress at wireless handheld telephony device 111 .
- Transfer of the user's end of the communication session may also include transfer of one or more telephony functions relating to the communication session.
- Telephony functions that may be transferred in this manner may include telephony functions applicable to an on-going communication session such as, for example, call forwarding, call holding, call transfer, call muting, call logs, caller ID, etc.
- User preferences relevant to an ongoing call including, for example preprogrammed soft button settings or volume level, may also be transferred.
- Service profiles associated with one or more users may be stored in the wireless call server 105 and may be associated with the wireless handheld telephony device 111. Transfer of telephony functions from the wireless handheld telephony device 111 to the second telephony device 101 may also transfer the profile association to the second telephony device 101 , such that settings stored in the service profile are applied to the second telephony device 101.
- one or more telephony functions that may be transferred to the second telephony device 101 may be limited or unable to be transferred, due to limitations in the second telephony device 101.
- Figure 9 shows an example of command signal interchange operations of a system 10, 100 in transferring a wireless end of a communication session between a wireless handheld telephony device 111 and at least one third telephony device 121 to a second telephony device 101.
- voice data streams or connections are depicted using dashed lines and signals comprising command signal data are depicted using solid lines.
- acommunication session has previously been established between wireless handheld telephony device 111 and at least one third telephony device 121.
- the end of the communications session assigned to wireless handheld telephony device 111 is managed by a wireless call server 105.
- the communications session may be established and managed as, for example, disclosed herein, using SIP or other suitable protocols.
- wireless handheld telephony device 111 for example upon coming within wireless communication range of one or more target local telephony devices 101, receives directly from each of such one or more target local telephony devices 101 signals representing data useful for establishing communications between the one or more target local telephony devices 101 and wireless call server 1 05. (That is, the signals are sent direct from target local telephony device(s) 101 to wireless handheld telephony device 111, without necessity for the signals to be routed through, for example, PBX 16.) As explained herein, the wireless signals may comprise identifying information and/or directional information for each target local telephony device 101.
- Such information may be formatted in accordance with, or compatible with any suitable protocol, such as those described herein, or may be formatted according to individual system preferences.
- Such signals may, for example, be received by one or more antenna(s) 910 of wireless handheld telephony device 111 and processed by receiver 908 for further processing by one or more processor(s) 900 of the device.
- data provided by one or more target local telephony devices 101 useful by wireless handheld telephony devices 111 and/or their controlling call servers 105 for identifying such devices 101 can be provided on a push basis by target local telephony device(s) 101 , or they can be pulled by a wireless handheld telephony device 111, either continuously, periodically, or in response to a query signal transmitted by wireless handheld telephony device 111 at the command of its user.
- a user of a wireless handheld telephony device 111 walking into an office area containing one or more target local telephony devices 101 and desiring to transfer his/her end of an ongoing telephone call can activate a key-based command to cause the wireless device to push out a polling signal using, for example, an RFI D-capable transmitter 906.
- the polling signal might be received and answered by one or more target local telephony devices 101 using suitably-configured RFID transponders.
- wireless handheld telephony device 111 In response to receipt and suitable display by wireless handheld telephony device 111 of signals from one or more target local telephony devices 101, the user of wireless handheld telephony device 111 can be provided an interactive opportunity to request transfer of the user's end of the ongoing call session to a selected one of target local telephony devices 101. For example, as described herein, when a user of wireless handheld telephony device 111 determines that he/she would like to transfer the ongoing communications session to a selected one of target local telephony devices 101 , the user can enter input data indicating that the user would like to transfer the call to selected target local telephony device 101 , using any one or more of input devices 902.
- a list of one or more eligible target local telephony devices 101 can be displayed on an output screen of the user's wireless handheld telephony device 111 ; and a desired target phone may be selected by the user using interactive input means.
- a processor 900 of wireless handheld telephony device 111 can cause a signal or signals representing a request to transfer the user's end of the call to such target local telephony device 101 to be sent to the responsible wireless call server 105.
- the responsible wireless call server 105 can be provided by wireless handheld telephony device 111 with signals representing a request for authentication of at least selected target local telephony device 101.
- authentication of multiple target local telephony devices 101 can be requested prior to selection by a user of wireless handheld telephony device 111.
- wireless call server 105 responsible for controlling wireless handheld telephony device 111's end of the communications session can, using data provided by the wireless device (which might include data provided originally by the selected target local telephony devices 101), forward the request for authentication of the selected target local telephony devices 101 to a PBX or other intermediary 130 controlling or otherwise responsible for administering the selected target local telephony devices 101.
- data can, for example, be formatted in accordance with, or compatible with, any suitable protocols, as described herein.
- uch server 16 can in various embodiments be incorporated in target local telephony devices 101 as a software and/or hardware component thereof.
- intermediary 130 responsible for controlling selected target local telephony device(s) 101 can, before, after, or while authorizing and/or authenticating the availability and suitability of selected target local telephony device(s) 101 , send to the querying wireless call server 105 signals representing a request for authentication of wireless handheld telephony device 111 from which the request originated. This may be done, for example, in order to confirm that wireless handheld telephony device 111 is a valid end user (e.g. that the device is not using a false identity or "spoofing").
- authentication of device(s) 111,101 , by their responsible servers 105, 16, 103 can be required for a wide variety of purposes, including security, accounting/billing, or control of signal traffic for bandwidth, capacity, or other reasons.
- the responsible wireless server 105 can provide to the requesting intermediary 130 signals useful in establishing the authentication requested at 810.
- intermediary 130 can provide to the requesting wireless call server 105 signals useful by the wireless server 105 in establishing the authentication requested at 808.
- the requesting server 105, 130 and/or device 101, 111 can be notified and a new selection, or other appropriate action, may be requested.
- wireless call server 105 can provide to the requesting wireless handheld telephony device 111 signals representing a request for confirmation that a user of the device 111 wishes to transfer the end of the call session assigned to wireless handheld telephony device 111 to a selected target local telephony device 101.
- wireless call server 105 can provide to wireless handheld telephony device 111 signals adapted to cause a processor 900 of the device 111 to display on an output display screen 928 of the device a request, which may be interactive, for the user of the device 111 to confirm his/her desire to complete the transfer.
- the user can input command signals adapted to confirm or deny that the user wishes to complete transfer of the user's end of the call session to selected target local telephony device 101.
- further processing can be undertaken by wireless call server 105 and other system components to transfer the call session, as herein described.
- processing can be halted and the pre-existing call session between wireless handheld telephony device 111 and third telephony device 121 can be continued.
- a user of wireless handheld telephony device 111 can enter suitably-adapted keystrokes to cause processor 900 of wireless handheld telephony device 111 to provide to wireless call server 105 signals adapted for causing server 105 to complete transfer of the call session.
- third telephony device 121 can be placed in such a hold state at any necessary or convenient point in the transfer process. As will be understood by those skilled in the relevant arts, such a necessary or convenient point may depend upon the protocol(s) and system architecture(s) used in creating and controlling the relevant call sessions.
- wireless call server 105 can send to third telephony device 121 (or its corresponding server) a signal requesting that third telephony device 121's end of the call session be placed in a hold state.
- wireless call server 105 having received a request for transfer of wireless handheld telephony device 111's end of the call session to selected target local telephony device 101 and optionally a confirmation of that request, can forward to intermediary 130 controlling selected target local telephony device 101 a request for target local telephony device 101 to join the call session previously established between wireless handheld telephony device 111 and third telephony device 121, or otherwise accept transfer of wireless handheld telephony device 111's end of that call session.
- a selected or selectable (i.e., target) local telephony device 101 be provided with means such as an audio and/or visual signal for identifying to a user of wireless handheld telephony device 111 the selected or selectable local telephony device 101, and optionally for indicating to such user that the selected or selectable (i.e., target) local telephony device 101 is ready to assume wireless handheld telephony device 111's end of the communications session.
- intermediary 130 can send to selected target local telephony device 101 a signal adapted to cause selected target local telephony device 101 to provide for the user of wireless handheld telephony device 111 a ringtone or other audio and/or visual signal, so that the user will pick up the receiver of selected target local telephony device 101, activate a speakerphone control, or otherwise activate the local telephony device in order to complete the transfer of wireless handheld telephony device 111's end of the communication session.
- the user of wireless handheld telephony device 111 can pick up the receiver of selected target local telephony device 101 , activate a speakerphone control, or otherwise initiate pick-up of wireless handheld telephony device 111's end of the communications session, and cause target local telephony device 101 to provide to intermediary 130 a signal indicating that selected target local telephony device 101 is ready to accept transfer of the communications session.
- intermediary 130 can provide to wireless call server 105 signals confirming that selected target local telephony device 101 has initiated the call pick-up process and that wireless server 105 may terminate wireless handheld telephony device 111's end of the call session.
- wireless server 105 upon receipt of confirmation that selected target local telephony device 101 and/or intermediary 130 have initiated the process of picking up wireless handheld telephony device 111's end of the call session, can terminate wireless handheld telephony device 111's end of the call session. Suitable confirmation may be provided by the wireless server 105 to the wireless device.
- intermediary 130 upon confirmation or instruction that selected local device is ready to pick up wireless handheld telephony device 111's end of the call session, can provide to third telephony device 121 and/or a call server controlling third telephony device 121 signals configured for use by third telephony device 121 and/or its server in causing outgoing communications from third telephony device 121 to be routed to selected target local telephony device 101, and incoming communications from target local telephony device 101 to be routed to third telephony device 121.
- selected target local telephony device 101 can communicate with third telephony device 121, so that at 838 the transferred call session can continue, between selected local device 101 and third telephony device 121.
- Further signals useful for processing communications between target local telephony device 101 and third telephony device 121 can be provided and processed according to any desired telephony protocol.
- FIGS 10A, 10B and 10C show, in block diagram form, three example systems 900A, 900B and 900C for transferring communication from a wireless handheld telephony device 111 to a second telephony device 101.
- data connections are represented by solid lines where as voice connections are represented by dashed lines.
- Systems 900A, 900B and 900C of Figures 10A, 10B and 10C may represent specific examples of system 100 of Figure 6 .
- intermediary 130 comprises enterprise server 12, 902, corporate mobile voice server (MVS) 904, and PBX 16, 906.
- Wireless handheld telephony device 111 may be engaged in an ongoing conversation with at least one third telephony device 121 through PBX 906.
- second telephony device 101 may be another corporate telephony device which is configured to communicate through PBX 906.
- Wireless handheld telephony device 111 may receive wireless signals from second telephony device 101 as described above. Wireless handheld telephony device 111 may send identifying information received through the wireless signals to the enterprise serve 902 and corporate MVS 904. Using this information, corporate MVS 904 may instruct PBX 906 to transfer the communication session from wireless handheld telephony device 111 to second telephony device 101 such that the communication session continues between second telephony device 101 and at least one third telephony device 121 through PBX 906.
- intermediary 130 comprises internet server 908, consumer MVS 910 and switching environment 912.
- Wireless handheld telephony device 111 may be engaged in an ongoing conversation with at least one third telephony device 121 through switching environment 912.
- second telephony device 101 may be a public telephony device which is capable of communicating through switching environment 912.
- Wireless handheld telephony device 111 may receive wireless signals from second telephony device 101 as described above. Wireless handheld telephony device 111 may send identifying information received through the wireless signals through a data connection to internet server 908 which is connected to consumer MVS 910. Switching environment 912 may then be directed to transfer the ongoing communication from wireless handheld telephony device 111 to second telephony device 101 such that the communication session continues between second telephony device 101 and at least one third telephony device 121 through switching environment 912.
- the communication session may be transferred via switching environment 912 over the internet using IP addressing.
- the communication session may be transferred via switching environment 912 over, for example a PSTN such as PSTN 40 of Figure 1 .
- intermediary 130 comprises a service provider switching environment 914.
- Wireless handheld telephony device 111 may be engaged in an ongoing conversation with at least one third telephony device 121 through service provider switching environment 914.
- second telephony device 101 may be a public telephony device which is capable of communicating through service provider switching environment 914.
- Wireless handheld telephony device 111 may receive wireless signals from a second telephony device 101 as described above. Once the identity of second telephony device 101 to which communication will be transferred has been established, wireless handheld telephony device 111 may provide this information to the service provider switching environment 914. This may be done using, for example, in-band or sideband DTMF, data signaling via a carrier APN or simple SMS back to the SPSE or using any other available protocol. Service provider switching environment 914 may transfer the ongoing communication from wireless handheld telephony device 111 to second telephony device 101 such that the communication session continues between second telephony device 101 and at least one third telephony device 121 through service provider switching environment 914.
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Telephonic Communication Services (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
- The present application relates to wireless handheld telephony devices and, more particularly, to systems and methods for transferring an end of an ongoing communication session from a first telephony device to a second telephony device.
- There is a need for improved devices and methods for allowing a user of a telephony device, such as a wireless telephone, to transfer the user's end of a telephone call session from the telephony device on which the call session was established to a second telephony device, such as a desk telephone. The ability to make such transfers can, for example, improve the security of the call session (e.g., the security of the communications from eavesdroppers), the comfort of the user, the economics of the telephone call (such, for example, where a wireless telephone subscription disfavors extended wireless use) and other factors.
- Some systems and devices for transferring calls from wireless to other telephony devices do exist. However, they tend to be less flexible, secure, dependable, and user friendly than they might be. There is need for improvement.
- For example, in some aspects, the disclosure provides a method of transferring to a second telephony device an end of a communications session previously established between a wireless handheld telephony device and at least one third telephony device, where the wireless handheld telephony device comprises at least one wireless signal receiver, at least one wireless signal transmitter, at least one data processor, and media readable by the at least one data processor comprising coded program instructions. Such methods can, for example, comprise: while maintaining the previously-established communications session between the wireless handheld telephony device and the at least one third telephony device, receiving direct from one or more target local telephony devices one or more wireless signals representing data useful for establishing communications between the one or more target local telephony devices and a call server managing the end of the previously-established communications session associated with the wireless handheld telephony device; using the wireless signals received direct from the one or more target local telephony devices, instructing the call server to establish a communications session between a selected one of the at least one target local telephony devices and the at least one third telephony device; and upon establishment of a communications session between the selected local telephony device and the at least one third telephony device, terminating the previously-established communications session between the wireless handheld telephony device and the at least one third telephony device.
- In some other aspects, the disclosure herein provides a wireless handheld telephony device comprising at least one wireless signal receiver, at least one wireless signal transmitter, at least one data processor, and media readable by the at least one data processor comprising coded program instructions adapted for enabling the wireless handheld telephony device to cause transfer to a second telephony device of an end of a communications session previously established between the wireless handheld telephony device and at least one third telephony device. The wireless handheld telephony device can, for example, do so using the method described above.
- Other aspects of the disclosure will be apparent to those of ordinary skill in the art from a review of the following detailed description in conjunction with the drawings.
- Reference will now be made, by way of example, to the accompanying drawings which show example embodiments of subject matter disclosed herein, and in which:
-
Figure 1 shows a schematic diagram of an example system for managing telephone and other communications in accordance with the disclosure herein; -
Figures 2-5 show schematic diagrams of example embodiments of details of a system such as that shown inFigure 1 ; -
Figure 6 shows a schematic diagram of an example system for managing telephone and other communications in accordance with the disclosure herein; -
Figure 7 provides schematic diagrams of wireless handheld telephony devices suitable for use in implementing the systems, devices, and methods disclosed herein; -
Figure 8 shows a schematic flow diagram of an example of a method of transferring an ongoing communication in accordance with the disclosure herein; -
Figure 9 is a signaling diagram generally showing an example of a transfer of a communications session in accordance with the disclosure herein; and -
Figures 10A - 10C are schematic diagrams of examples of systems for managing telephone and other communications in accordance with the disclosure herein. - Similar reference numerals may have been used in different figures to denote similar components.
- Embodiments of the present application are not limited to any particular operating system, mobile device architecture, server architecture, or computer programming language.
- The present application relates to the control and management of communications. Although reference may be made to "calls" in the description of example embodiments below, it will be appreciated that the described systems and methods are applicable to session-based communications in general and not limited to voice calls, and that references to "calls" are intended to refer to session-based communications sessions of any type, including voice, data or text communications, unless clearly indicated otherwise by context. It will also be appreciated that the systems and methods may not be limited to sessions and may be applicable to messaging-based communications in some embodiments.
- Reference is now made to
Figure 1 , which shows, in block diagram form, an example of a system, generally designated 10, for the control and management of communications, suitable for use in implementing the systems and methods disclosed herein.System 10 includes an enterprise orbusiness communications system 20, which may include a local area network (LAN). In the description below, the enterprise orbusiness system 20 may be referred to as anenterprise network 20. It will be appreciated thatenterprise network 20 may include more than one network and may be located in multiple geographic areas in some em bodim ents. -
Enterprise network 20 may be connected, for example through afirewall 22, to a wide area network (WAN) 30, such as the Internet.Enterprise network 20 may also be connected to a public switched telephone network (PSTN) 40 via direct inward dialing (DID) trunks or primary rate interface (PRI) trunks. -
Enterprise network 20 may also communicate with a public land mobile network (PLMN) 50, which may also be referred to as a wireless wide area network (WWAN) or, in some cases, a cellular network. Connection with the PLMN 50 may be made via arelay 26, as known in the art. -
Enterprise network 20 may also provide one or more wireless local area networks (WLANs) 32a featuring wireless access points.Other WLANs 32 may exist outsideenterprise network 20. For example, WLAN 32b may be connected toWAN 30. -
System 10 may include and/or interact with a number of enterprise-associated mobile devices 11 (only one shown). Mobile device(s) 11 may include devices equipped for cellular communication through the PLMN 50, mobile devices equipped for Wi-Fi communications over one of theWLANs 32, and/or dual-mode devices capable of both cellular and WLAN communications.WLANs 32 may be configured in accordance with one of the IEEE 802.11specifications. - It will be understood that the
mobile devices 11 include one or more radio transceivers and associated processing hardware and software to enable wireless communications with thePLMN 50 and/or one of theWLANs 32. In various embodiments, the PLMN 50 andmobile devices 11 may be configured to operate in compliance with any one or more of a number of wireless protocols, including GSM, GPRS, CDMA, EDGE, UMTS, EvDO, HSPA, 3GPP, or a variety of others. It will be appreciated that themobile device 11 may roam within thePLMN 50 and across PLMNs, in for example any of a variety of known manners, as the user moves. In some instances, the dual-modemobile devices 11 and/orenterprise network 20 are configured to facilitate roaming between thePLMN 50 and aWLAN 32, and are thus capable of seamlessly transferring sessions (such as voice calls) from a connection with the cellular interface of the dual-mode device 11 to theWLAN 32 interface of the dual-mode device 11, and vice versa. -
Enterprise network 20 typically includes a number of networked servers, computers, and other devices. For example,enterprise network 20 may connect one or more desktop or laptop computers 15 (one shown). The connection may be wired or wireless in some embodiments.Enterprise network 20 may also connect to one or more digital telephone sets 17 (one shown). -
Enterprise network 20 may include one or more mail servers, such asmail server 24, for coordinating the transmission, storage, and receipt of electronic messages for client devices operating withinenterprise network 20. Typical mail servers include the Microsoft Exchange Server™ and the I BM Lotus Domino™ server. Each user within the enterprise typically has at least one user account withinenterprise network 20. Associated with each user account is message address information, such as an e-mail address. Messages addressed to a user message address are stored onenterprise network 20 in themail server 24. The messages may be retrieved by the user using a messaging application, such as an e-mail client application. The messaging application may be operating on a user's computer 15 connected toenterprise network 20 within the enterprise. In some embodiments, the user may be permitted to access stored messages using a remote computer, for example at another location via the WAN 30 using a VPN connection. Using the messaging application, the user may also compose and send messages addressed to others, within oroutside enterprise network 20. The messaging application causes themail server 24 to send a composed message to the addressee, often via theWAN 30. - The
relay 26 serves to route messages received over thePLMN 50 from themobile device 11 to thecorresponding enterprise network 20. Therelay 26 also pushes messages fromenterprise network 20 to the mobile device 11via the PLMN 50. - In the embodiment shown,
enterprise network 20 also includes anenterprise server 12. Together with therelay 26, theenterprise server 12 can function to redirect, copy, or relay incoming e-mail messages addressed to a user's e-mail address withinenterprise network 20 to the user's mobile device 11and to relay incoming e-mail messages composed and sent via themobile device 11 out to the intended recipients within theWAN 30 and/or elsewhere. Among other functions,enterprise server 12 andrelay 26 together can facilitate "push" e-mail service for themobile device 11 enabling the user to send and receive e-mail messages using themobile device 11 as though the user were connected to an e-mail client withinenterprise network 20 using the user's enterprise-related e-mail address, for example on computer 15. - As is typical in many enterprises,
enterprise network 20 can include one or more Private Branch exchanges (although in various embodiments the PBX(s) may be standard PBX(s) or IP-PBX(s), for simplicity the description below uses the term PBX to refer to both) 16 having a connection with thePSTN 40 for routing incoming and outgoing voice calls to and from digital and/or analog telephones or other telephony devices for the enterprise.PBX 16 is connected to thePSTN 40 via DID trunks or PRI trunks, for example.PBX 16 may use ISDN signaling protocols for setting up and tearing down circuit-switched connections through thePSTN 40 and related signaling and communications. In some embodiments,PBX 16 may be connected to one or more conventional analog telephones 19.PBX 16 may also be connected toenterprise network 20 and, through it, to telephone terminal devices, such as digital telephone sets 17, softphones operating on computers 15, etc. Within the enterprise, each individual may have an associated extension number, sometimes referred to as a PNP (private numbering plan), or direct dial phone number. Calls outgoing fromPBX 16 to thePSTN 40 or incoming from thePSTN 40 to PBX 16 are typically circuit-switched calls. Within the enterprise, e.g. betweenPBX 16 and terminal devices, voice calls are often packet-switched calls, for example Voice-over-IP (VoIP) calls. -
Enterprise network 20 may include a Service Management Platform (SMP) 18 for performing aspects of messaging or session control, such as call control and advanced call processing features.SMP 18 may, in some cases, also perform some media handling. CollectivelySMP 18 andPBX 16 may be referred to as the enterprise communications platform, generally designated 14. It will be appreciated that theenterprise communications platform 14 and, in particular,SMP 18, is implemented on one or more servers having suitable communications interfaces for connecting to and communicating withPBX 16 and/or DID/PRI trunks. AlthoughSMP 18 may be implemented on a stand-alone server, it will be appreciated that it may be implemented into an existing control agent/server as a logical software component. As will be described below,SMP 18 may be implemented as a multi-layer platform. - For devices such as
telephony devices 11, 19 controlled by or otherwise associated with it,enterprise communications platform 14 can implement switching to connect session legs and may provide conversion between, for example, a circuit-switched call and a VolPcall, or connect legs of other media sessions. Such calls/sessions may be set up and modified on behalf of devices 1 1 , 19 and any desired telephony devices, within oroutside enterprise network 20, including for example devices 19, 107 connected toPSTN 40. In some embodiments, in the context of voice calls theenterprise communications platform 14 provides a number of additional functions including automated attendant, interactive voice response, call forwarding, voice mail, etc. It may also implement certain usage restrictions on enterprise users, such as blocking international calls or 1-900 calls. In many embodiments, Session Initiation Protocol (SIP) may be used to set up, manage, and terminate media sessions for voice calls. Other protocols may also be employed by theenterprise communications platform 14, for example, Web Services, Computer Telephony Integration (CTI) protocol, Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), and various custom Application Programming Interfaces (APIs), as will be described in greater detail below. - One of the capabilities of
enterprise communications platform 14 is to extend the features of enterprise telephony to mobile device(s) 11. For example,enterprise communications platform 14 may allow mobile device(s) 11 to perform functions akin to those normally available on a standard office telephone, such as the digital telephone set 17 or analog telephone set 15. Example features may include direct extension dialing, enterprise voice mail, conferencing, call transfer, call park, etc. As further described elsewhere herein,enterprise communications platform 14 can further provide functions such as transfer of corresponding ends of existing communications sessions from one or more mobile devices 11to wired telephony devices 19 associated withplatform 14. - Reference is now made to
Figures 2 to 4 , which show example embodiments ofenterprise communications system 14. Again, although references are made below to "calls" or call-centric features it will be appreciated that the architectures and systems depicted and described are applicable to session-based (e.g., voice) communications in general and, in some instances, to text, image, or other messaging-based communications. -
Figure 2 illustrates an embodiment intended for use in a circuit-switched TDM context.PBX 16 is coupled toSMP 18 viaPRI connection 60 or other suitable digital trunk. In some embodiments,PRl connection 60 may include a first PRI connection, a second PRI connection, and a channel service unit (CSU), wherein the CSU is a mechanism for connecting computing devices to digital mediums in a manner that allows for the retiming and regeneration of incoming signals. It will be appreciated that there may be additional or alternative connections betweenPBX 16 andSMP 18. - In this embodiment,
SMP 18 assumes control over both call processing and the media itself. This architecture may be referred to as "First Party Call Control". Many of the media handling functions normally implemented byPBX 16 are handled bySMP 18 in this architecture. Incoming calls addressed to any extension or direct dial number within the enterprise, for example, are always first routed toSMP 18. Thereafter, a call leg is established fromSMP 18 to the called party within the enterprise, and the two legs are bridged. Accordingly,SMP 18 includes a digital trunk interface 62 and a digital signal processing (DSP) conferencing bridge 64. DSPconferencing bridge 64 performs the bridging of calls for implementation of various call features, such as conferencing, call transfer, etc. Digital trunk interface 62 may be implemented as a plurality of telephonic cards, e.g. Intel Dialogic cards, interconnected by a bus and operating under the control of a processor. Digital trunk interface 62 may also be partly implemented using a processor module such as, for example, a Host Media Processing (HMP) processor. -
SMP 18 may includevarious scripts 66 for managing call processing.Scripts 66 are implemented as software modules, routines, functions, etc., stored in non-volatile memory and executed by the processor ofSMP 18.Scripts 66 may implement call flow logic, business logic, user preferences, call service processes, and various feature applications. -
Figure 3 shows another embodiment in whichPBX 16 performs the functions of terminating and/or bridging media streams, but call control functions are largely handled bySMP 18. In this embodiment,SMP 18 may be referred to as acall control server 18. This architecture may be referred to as "Third-Party Call Control". - Call
control server 18 is coupled toPBX 16, for example through the LAN, enabling packet-based communications and, more specifically, IP-based communications. In one embodiment, communications betweenPBX 16 andcall control server 18 are carried out in accordance with SIP. In other words, callcontrol server 18 uses SIP-based communications to manage the set up, tear down, and control of media handled byPBX 16. In one example embodiment, thecall control server 18 may employ a communications protocol conforming to the ECMA-269 or ECMA-323 standards for Computer Supported Telecommunications Applications (CSTA). -
Figure 4 shows yet another embodiment ofenterprise communications system 14. This embodiment reflects the adaptation of an existing set of call processing scripts to an architecture that relies on third-party call control, with separate call control and media handling.SMP 18 includes a call processing server 74. The call processing server 74 includes the scripts or other programming constructs for performing call handling functions.SMP 18 also includes a SIP server 72 and amedia server 76. The separate SIP server 72 andmedia server 76 logically separate the call control from media handling. SIP server 72 interacts with the call processing server 74 using a computer-implemented communications handling protocol, such as one of the ECMA-269 or ECMA-323 standards. These standards prescribe XML based messaging for implementing Computer Supported Telecommunications Applications (CSTA). - SIP server 72 interacts with the
media server 76 using SIP-based media handling commands. For example, SIP server 72 andmedia server 76 may communicate using Media Server Markup Language (MSML) as defined in IETF document Saleem A., "Media Server Markup Language", Internet Draft, draft-saleem-msml-07, August 7, 2008. Themedia server 76 may be configured to perform Host Media Processing (HMP). - Other architectures or configurations for
enterprise communications system 14 will be appreciated by those ordinarily skilled in the art. - Reference is now made to
Figure 5 , which shows an embodiment ofenterprise communications system 14 with a Third Party Call Control architecture. In this embodiment,SMP 18 is a multi-layer platform that includes aprotocol layer 34, aservices layer 36 and anapplication layer 38.Protocol layer 34 includes a plurality of interface protocols configured for enabling operation of corresponding applications in theapplication layer 38. Theservices layer 36 includes a plurality of services that can be leveraged by the interface protocols to create richer applications. Finally, theapplication layer 38 includes a plurality of applications that are exposed out to the communication devices and that leverage corresponding ones of the services and interface protocols for enabling the applications. - Specifically,
protocol layer 34 preferably includes protocols which allow media to be controlled separate from data. For example,protocol layer 34 can include, among other things, a Session Initiation Protocol orSIP 80, aWeb Services protocol 82, an Application Program m ing Interface orAPI 84, a Computer Telephony Integration protocol orCTI 86, and a Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions orSIMPLE protocol 88. It is contemplated that the interface protocols 80-88 are plug-ins that can interface directly with corresponding servers inenterprise network 20, which will be further described below. - For the purposes of this disclosure,
SIP 80 will be utilized, although it is appreciated thatsystem 10 can operate using the above disclosed or any other suitable protocols. As known by those skilled in the relevant arts, SIP is the IETF (Internet Engineering Task Force) standard for multimedia session management, and more specifically is an application-layer control protocol for establishing, maintaining, modifying and terminating multimedia sessions between two or more endpoints. As further known by those skilled in the relevant arts,SIP protocol 80 includes two interfaces for signaling: SIP-Trunk (hereinafter referred to as "SIP-T") and SIP-Line (hereinafter referred to as "SIP-L"). Specifically, SIP-T interface is utilized when the endpoint is a non-specific entity or not registered (i.e., when communicating between two network entities). In contrast, SIP-L interface is utilized when the endpoint is registered (i.e., when dialing to a specific extension). The specific operation ofsystem 10 utilizingSI P 80 will be described in further detail below. -
SMP 18 also includes a plurality of enablers, among other things, a VolP enabler 90, a Fixed Mobile Convergence or FMC enabler 92, a conference services/call and/or session transfer enabler 94, apresence enabler 96, and an Instant Messaging orI M enabler 98. Each of the enablers 90-98 can be used by corresponding services in theservices layer 36 that combine one or more of the enablers. Each of the applications in theapplication layer 38 can then be combined with one or more of the services to perform the desired application. For example, a phone call service may use the VoIP or PBX enabler, and an emergency response application may use the phone call service, an Instant Messenger service, a video call service, and email service and/or a conference service. -
Application layer 38 may include aconference services application 63 that, together with the conference services enabler 94, enables multiple communication devices (including desk telephones and personal computers) to participate in a conference call through use of a centralized conference server 55. As seen inFigure 5 , Conference server 55 is provided inenterprise network 20 and is in communication with the conference services enabler 94 preferably throughSIP protocol 80, although it is recognized that additional protocols that control media separate from data may be appropriate, such as theWeb Services protocol 82 or theCTI protocol 86. Conference call server 55 is configured for directing media and data streams to and from one or more communication devices (i.e.,mobile devices 11,telephones 17, and computers 15). - Reference is now made to
Figure 6 , which shows, in block diagram form, an example system for transferring an end of a com m unication session from a wireless handheld telephony device 111 to asecond telephony device 101 in accordance with the disclosure herein. The system comprises one or more wireless handheld telephony device(s) 111, any one or more of which may be engaged in established or ongoing communications with at least onethird telephony device 121 through PSTN or other communication cloud ornetwork 115, such asPSTN 40 orPLMN 50 ofFigure 1 . In some embodiments, the system may be a hosted environment, such as a corporate or enterprise environment, or it may be a switching environment. -
Communication cloud 115 may be adapted for carrying voice communications according, for example, to any of the several IP or non-IP protocols described above, or any other suitable protocols or methods. For example, in some embodiments,communication cloud 115 may comprise or otherwise interact with aPSTN 40 and/orPLMN 50.Communication cloud 115 may also be capable of carrying image, text, or other data. For example,communication cloud 115 may comprise aWAN 30, such as the Internet. - Wireless handheld telephony device(s) 111 may be any type of wireless handheld device with telephony capabilities including, but not limited to, cellular telephones, BlackBerry™devices, PDAs and other devices described herein. Such wireless handheld telephony devices 111can facilitate voice telephonic and/or other communications through, for example, wireless call server(s) 105. Call server(s) 105 can comprise any systems, processors, and/or other components suitable for use in implementing the systems and functions described herein. For example, call server(s) 105 can include any or all suitable components of
enterprise network 20, including for example any or all of thecomponents communications platform 14 and/orenterprise server 12. In some embodiments, communications between wireless handheld telephony devices 111 and at least onethird telephony device 121 may be routed through aPBX 16 as, for example, described above in relation toFigure 1 . - It will be understood by those skilled in the relevant arts that PBX(s) 16 may comprise the
service management platform 18 orenterprise communications system 14 described in relation toFigures 1 - 5 ; for simplicity, they are referred to herein simply as PBX(s) 16. - The at least one
third telephony device 121 can include any type of telephony devices suitable for accomplishing the purposes described herein, including, but not limited to, landline or wired telephones, such as VOIP protocol or other digital telephone sets 17, analog telephone sets 15, and/orwireless telephony devices 11 accessible through, for example,wireless call servers 125. One or more of suchthird telephony devices 121 may also be enterprise telephones accessible through, for example, a PBX 116. PBX 116 may or may not be the same asPBX 16.Wireless call server 125 may or may not be the same aswireless call server 105. - As explained herein, a user of a wireless handheld telephony device 111 may, in various circumstances, wish to transfer the user's end of a previously-established communication session from the user's wireless handheld telephony device 111 to a second telephony device such as one of target
local telephony devices 101. This may be desirable when, for example, the battery on wireless handheld telephony device 111 is low or the user does not wish to drain the battery further, whensecond telephony device 101 is considered more secure, when wireless audio quality or wireless signal is poor or when the user of wireless handheld telephony device 111 wishes to use some of the functionality available onsecond telephony device 101. - Target
local telephony devices 101 may be enterprise telephony devices configured to communicate through an intermediary 130 comprising, for example,PBX 16. In other embodiments, targetlocal telephony device 101 may be a public telephony device and may be configured to communicate through an intermediary 130 which may, for example, comprise a switching environment. Targetlocal telephony devices 101 may be wired devices, or they may be connected to intermediary 130 wirelessly such as, for example, through a Wi-Fi connection. In some embodiments, targetlocal telephony devices 101 may be configured to allow voice communications to be made over the Internet, such as a device equipped with Skype™ software. - As mentioned above, in some embodiments, intermediary 130 may comprise
PBX 16. In other embodiments, intermediary 130 may comprise a switching environment. In some embodiments, intermediary 130 may form part ofcommunication cloud 115. - Each of the one or more target
local telephony devices 101 include functionality which will allow wireless handheld telephony device 111 to receive one or more wireless signals directly from the one or more targetlocal telephony devices 101. Such signals can represent data useful for establishing communications between the one or more targetlocal telephony devices 101 andwireless call server 105 which administers or is otherwise associated with wireless handheld telephony device 111. - In some embodiments, such wireless signals may be pushed from the one or more target
local telephony devices 101 to any wireless handheld telephony device 111 within communications range of targetlocal telephony device 101. For example, each targetlocal telephony device 101 may include hardware, such as a radio or other wireless transmitter, capable of broadcasting such wireless signals. For example, targetlocal telephony devices 101 may include BlueTooth™ capabilities. In such embodiments wireless handheld telephony device(s) 111 may be adapted to receive, interpret, and further process wireless signals broadcast by the one or more targetlocal telephony devices 101 in accordance with this disclosure. In some embodiments, the wireless signals are transmitted by targetlocal telephony device 101 only when thetelephony device 101 is in an idle state (e.g. not in use for an active call session). - In other embodiments, such wireless signals may be pulled from target
local telephony devices 101 by wireless handheld telephony device 111. For example, each targetlocal telephony device 101 may include a radio-frequency identification (RFI D) transponder configured to respond to an inquiry signal received wirelessly from a suitably-configured RFID transmitter associated with a wireless handheld telephony device 111 within range of targetlocal telephony device 101. - Wireless signals provided by a particular target
local telephony device 101 may be received by all wireless handheld telephony devices 111 within range of the local device, or they may be directed only to a particular user or group of users. For example, a user's desk phone may be configured to only send wireless signals to that user's wireless handheld telephony device 111 or to wireless handheld telephony device 111 of users within the same working group. Similarly, in some embodiments, a targetlocal telephony device 101 may be configured not to transmit wireless signals to any wireless handheld telephony device 111. -
Figure 7 provides schematic diagrams of wirelesshandheld telephony devices 11, 111 suitable for use in implementing the systems, devices and methods disclosed herein.Figure 7a provides a schematic front view of a wirelesshandheld telephony device 11, 111,whileFigure 7b provides a functional block diagram of components suitable for use in configuring wirelesshandheld telephony device 11, 111 for the purposes disclosed herein. - In the example shown in
Figure 7a , wirelesshandheld telephony device 11, 111 comprises input means 902 and output means 904. Input means 902 can include devices such as keyboard(s) 922, function button(s)/switch(es) 924, microphone(s) 940, and pointing device(s) 926 such as a trackball, thumbwheel, etc. for providing single- or multi-stroke input for building and/or issuing command signals for use by processor(s) 900 as described herein. Input means 902 can be configured to provide various forms of input command signals toprocessor 900 of the handheld device, for local processing and or for output by the processor to one or more of memory(s) 912, output device(s) 904, and/ortransmitter 906 for transmission to external devices such aswireless control server 105. - Output means 904 can include devices such as display(s) 928 and speaker(s) 930 for providing visual and audio outputs, respectively. As will be readily understood by those skilled in the relevant arts, input and output means or
devices wireless control server 105 viaantenna 910 andreceiver 908. - In the example shown in
Figure 7b , wirelesshandheld telephony device 11, 111 comprises one ormore processors 900, input means 902, output means 904,wireless transmitter 906,wireless receiver 908, antenna(s) 910, and memory(s) 912. One ormore processors 900,wireless transmitters 906,receivers 908, andantennas 910 can be provided for use in implementing digital and/or analog voice, data, and/or command signal and communications processes. For example, separate sets ofantennas 910,receivers 908,transmitters 906,processors 900, and associatedmemories 912 can be provided for each of voice and data communications systems, and/or one or more of such components may be used for multiple types of communications using multiple protocols. As will be readily understood by those skilled in the relevant arts, and as described further herein, such processors, transmitters, receivers, antennas, and memories can be of any types and include means or devices suitable for use in accomplishing the purposes described herein. Awide variety of suitable means and devices are now known, and doubtless others will hereafter be developed. - Reference will now be made to
Figure 8 , which shows a flow diagram representing an example of a method 700 for transferring an end of a communications session from a wireless handheld telephony device 111 to a second telephony device, the second telephony device being, for example one of targetlocal telephony devices 101. Method 700 is suitable for use, for example, in conjunction withsystems 10, 100 ofFigures 1 and/or 6 and wirelesshandheld telephony devices 11, 111 ofFigure 7 in implementing the disclosure herein. - A method 700 can be considered to begin at
block 702, where a communication session, such as a voice communication session, has been established between a wireless handheld telephony device 111 and at least onethird telephony device 121 throughPSTN 40,PLMN 50, orother communications cloud 115. Wireless handheld telephony device 111's end of the call session can be controlled by awireless server 105. - At 704, wireless handheld telephony device 111 receives pulled or pushed wireless signals from one or more target local telephony devices 101.Such signals can represent, at least in part, data useful for establishing communications between one or more target
local telephony devices 101 and its controllingwireless call server 105. Such wireless signals may for example comprise identifying information for each targetlocal telephony device 101, or set ofdevices 101, such as, for example, extension numbers, telephone name(s) or other identifier(s), or office, cubicle, or other physical location. The wireless signals may also include directional information, such as global or relative coordinates, ranges, or compass directions. In some embodiments, the directional information may be useful in providing a directional display displayed on wireless handheld telephony device 111. Such signals may also include data useable by awireless call server 105 controlling wireless handheld telephony device 111's end of the communication session in identifying an intermediary 130 that controls the corresponding target local telephony device(s) 101 , and suitable for use bycall server 105 in requesting authentication of one or more selected targetlocal telephony devices 101. - At 706, a list of one or more target
local telephony devices 101 can be displayed by or otherwise provided to the user of wireless handheld telephony device 111 through the use of any suitableoutput display screen 928 of wireless handheld telephony device 111, or other means. Such list may include any information suitable for use in identifying to the user the name, location, or distance to target local telephony device(s) 101, including for example some or all of the identifying information which may be included in the wireless signals, or any useful information based thereon. For example, such list may include the extension number, telephone name, or office, cubical, or other physical location information for some or all of targetlocal telephony devices 101. In some embodiments, the list may also include range and/or directional information such as that described above. Directional information may be used to the provide the user with, for example, directions to a targetlocal telephony device 101, the distance to one or more of targetlocal telephony devices 101 and/or a map displaying the location of one or more of targetlocal telephony devices 101. - For example, signals representing data useful for identifying available target
local telephony devices 101 can be transmitted to anantenna 910, processed byreceiver 908 of wireless handheld telephony device 111, and provided to aprocessor 900 as shown inFigure 7 .Processor 900 can interpret the received and processed signals to provide suitably-configured output signals to adisplay 928 controlled by theprocessor 900 in such form that a human user of the device 111 can interpret them as described herein. - A list of target
local telephony devices 101 displayed on wireless handheld telephony device 111 may be sorted in a particular order such as, for example, according to a range or distance from wireless handheld telephony device 111 (e.g. from nearest to farthest). In some embodiments, the list may be sorted according to one or more preferences established by some criteria set, for example, by the user of wireless handheld telephony device 111 or by an administrator. For example, one or more targetlocal telephony devices 101 can be preferred due to type of device and/or functionality offered, public/semi-public/private location or status, security (e.g. the level of encryption), or cost. In some instances, another wireless handheld telephony device may be preferred for battery or other quality reasons. In some embodiments, the list may include only a predetermined number of telephony devices. For example, the list may include only the five (or other convenient number) targetlocal telephony devices 101 which are nearest to wireless handheld telephony device 111. Data useful in presenting the list on thedisplay 928 can be temporarily or persistently stored in one ormore memories 912 of wireless handheld telephony device 111, for later access and processing byprocessor 900 in response to input requests received from a user of the device. - In some embodiments, the list of target
local telephony devices 101 provided at 706 may include all local telephony devices within effective communications range of wireless handheld telephony device 111. That is, they may include all devices within range of effective communications with respect to the sharing of identifying information at 704, or effective communications of other desired type or purpose. In other embodiments, the list of targetlocal telephony devices 101 may include only those telephony devices which meet some predetermined criteria. For example, the list of targetlocal telephony devices 101 may include only those telephony devices which are within a certain desired or required proximity of wireless handheld telephony device 111, such as within x number of meters (e.g. five meters) of wireless handheld telephony device 111 or on the same floor of a building as wireless handheld telephony device 111. - In some embodiments, certain telephony devices may be excluded from lists of target
local telephony devices 101 even though they may match criteria for inclusion (e.g. they may be within five meters of wireless handheld telephony device 111). For example, telephony devices which are currently in use may be excluded from the list of targetlocal telephony devices 101. Other telephony devices may, for example, be excluded from the list by the owner/user of the telephony device or by an administrator based on security, cost, etc.. For example, an employee who may be vacating his desk, office, or cubicle temporarily may be able to indicate that they would prefer not to have any wireless conversations transferred to their office telephone. Similarly, an administrator could decide that only those telephones which are normally unused, such as those located in boardrooms or vacant offices, can be included in the list of targetlocal telephony devices 101. - At 708, the user of wireless handheld telephony device 111 can select
second telephony device 101 to which the user's end of the communications session will be transferred, for example, working from a list of targetlocal telephony devices 101 provided at 706. Such selection may, for example, be made using anysuitable input device 902 such as, for example, a keyboard, touch screen, mouse, trackball or the like, using any suitable input functionality, including, for example, special key commands, interaction with an interactive displayed list, etc. to provide suitably-configured input command signals to the responsible processor(s) 900 of the handheld device. The identity of selected targetlocal telephony device 101 and any other useful information derived from the wireless signals at 704 (or otherwise) can be sent towireless call server 105 which will coordinate the transfer with intermediary 130. This process will be discussed in greater detail in relation toFigure 8 . - In some embodiments,
second telephony device 101 may be automatically selected by wireless handheld telephony device 111 based on one or more pre-established rules established by the user of the device 111 and/or any administrator(s) thereof. For example, wireless handheld telephony device 111 may always select the nearest targetlocal telephony device 101, or the nearest such device meeting one or more predetermined criteria. - At 710, a human-interpretable signal may be emitted by
second telephony device 101 once the end of the communications session previously assigned to wireless handheld telephony device 111 has been successfully transferred or when the transfer is ready to be completed. Such a signal may, for example, include a visual signal, such as illumination of a light located on the target device, and/or an audio signal, such as a ring tone, buzz, pre-selected melody, or other signal, which may for example have been previously selected or designated by the user of wireless handheld telephony device 111 or by an administrator of wireless handheld telephony device 111 and/or targetlocal telephony device 101. An audio signal produced by the target device may be the same audio signal (e.g. ring tone) used in other circumstances (such as when wireless handheld telephony device 111 or targetlocal telephony device 101 rings) or it may be unique to this process. The signal may indicate to the user that they may now continue their conversation onsecond telephony device 101. The signal may also help the user locate the device they had selected. - At 712, the user of wireless handheld telephony device 111may unhook or otherwise pick up the target device by, for example, lifting the receiver or pushing a button on the target device to activate a speaker function. The user may at that time, if not already otherwise accomplished, cause transfer of the user's end of the communication session to target
local telephony device 101 to be completed by, for example, activating an input command from wireless handheld telephony device 111. For example, wireless handheld telephony device 111 may, upon establishment of a communications session between selected targetlocal telephony device 101 and the at least onethird telephony device 121, display a confirmation message on anoutput display screen 928 of wireless handheld telephony device 111, and require confirmatory input from the user in order to complete transfer of the user's end of the communication session. It may be required or desirable that the at least onethird telephony device 121 be placed on 'hold' or otherwise in a state of suspended communications pending the transfer. - Upon completion of the transfer, the user may continue the ongoing conversation (or other communication) with at least one
third telephony device 121 using second telephony device 101.The portion of the communication session extending to wireless handheld telephony device 111 may be automatically terminated by, for example, intermediary 130. In other embodiments the user may 'hang up' or otherwise manually terminate any continuing call session processes in progress at wireless handheld telephony device 111 . - Transfer of the user's end of the communication session may also include transfer of one or more telephony functions relating to the communication session.
- Telephony functions that may be transferred in this manner may include telephony functions applicable to an on-going communication session such as, for example, call forwarding, call holding, call transfer, call muting, call logs, caller ID, etc. User preferences relevant to an ongoing call, including, for example preprogrammed soft button settings or volume level, may also be transferred. Service profiles associated with one or more users may be stored in the
wireless call server 105 and may be associated with the wireless handheld telephony device 111. Transfer of telephony functions from the wireless handheld telephony device 111 to thesecond telephony device 101 may also transfer the profile association to thesecond telephony device 101 , such that settings stored in the service profile are applied to thesecond telephony device 101. In some examples, one or more telephony functions that may be transferred to thesecond telephony device 101 may be limited or unable to be transferred, due to limitations in thesecond telephony device 101. - Although various telephony functions have been described as being transferred to form the wireless handheld telephony device 111 to the
second telephony device 101 , it should be understood that such transferal may also be a duplication of one or more telephony functions, such that such functions may be available both on the wireless handheld telephony device 111 and on thesecond telephony device 101 , rather than a strict transferal of functions. - While the steps of method 700 are shown as occurring in a particular order, it will be appreciated by those skilled in the relevant arts that many of the process steps, and portions thereof, are interchangeable and may occur in different orders that that shown without materially affecting the end results of the method 700. It will further be appreciated by such persons that not all of such steps are required in order to accomplish the purposes disclosed herein, and that further steps may be optionally implemented.
- Reference is now made to
Figure 9 , which shows an example of command signal interchange operations of asystem 10, 100 in transferring a wireless end of a communication session between a wireless handheld telephony device 111 and at least onethird telephony device 121 to asecond telephony device 101. InFigure 9 voice data streams or connections are depicted using dashed lines and signals comprising command signal data are depicted using solid lines. - At 802 acommunication session has previously been established between wireless handheld telephony device 111 and at least one
third telephony device 121. In in the example shown, the end of the communications session assigned to wireless handheld telephony device 111 is managed by awireless call server 105. The communications session may be established and managed as, for example, disclosed herein, using SIP or other suitable protocols. - At 804 wireless handheld telephony device 111, for example upon coming within wireless communication range of one or more target
local telephony devices 101, receives directly from each of such one or more targetlocal telephony devices 101 signals representing data useful for establishing communications between the one or more targetlocal telephony devices 101 and wireless call server 1 05. (That is, the signals are sent direct from target local telephony device(s) 101 to wireless handheld telephony device 111, without necessity for the signals to be routed through, for example,PBX 16.) As explained herein, the wireless signals may comprise identifying information and/or directional information for each targetlocal telephony device 101. Such information may be formatted in accordance with, or compatible with any suitable protocol, such as those described herein, or may be formatted according to individual system preferences. Such signals may, for example, be received by one or more antenna(s) 910 of wireless handheld telephony device 111 and processed byreceiver 908 for further processing by one or more processor(s) 900 of the device. - As explained herein, data provided by one or more target
local telephony devices 101 useful by wireless handheld telephony devices 111 and/or theircontrolling call servers 105 for identifyingsuch devices 101 can be provided on a push basis by target local telephony device(s) 101 , or they can be pulled by a wireless handheld telephony device 111, either continuously, periodically, or in response to a query signal transmitted by wireless handheld telephony device 111 at the command of its user. For example, a user of a wireless handheld telephony device 111 walking into an office area containing one or more targetlocal telephony devices 101 and desiring to transfer his/her end of an ongoing telephone call can activate a key-based command to cause the wireless device to push out a polling signal using, for example, an RFI D-capable transmitter 906. The polling signal might be received and answered by one or more targetlocal telephony devices 101 using suitably-configured RFID transponders. - In response to receipt and suitable display by wireless handheld telephony device 111 of signals from one or more target
local telephony devices 101, the user of wireless handheld telephony device 111 can be provided an interactive opportunity to request transfer of the user's end of the ongoing call session to a selected one of targetlocal telephony devices 101. For example, as described herein, when a user of wireless handheld telephony device 111 determines that he/she would like to transfer the ongoing communications session to a selected one of targetlocal telephony devices 101 , the user can enter input data indicating that the user would like to transfer the call to selected targetlocal telephony device 101 , using any one or more ofinput devices 902. For example, as described herein in connection with block/step 708 ofFigure 7 , a list of one or more eligible targetlocal telephony devices 101 can be displayed on an output screen of the user's wireless handheld telephony device 111 ; and a desired target phone may be selected by the user using interactive input means. - Upon input by the user of key-based or other command(s) indicating the user's selection of the desired target
local telephony device 101 , at 806 aprocessor 900 of wireless handheld telephony device 111 can cause a signal or signals representing a request to transfer the user's end of the call to such targetlocal telephony device 101 to be sent to the responsiblewireless call server 105. For example, at 806 the responsiblewireless call server 105 can be provided by wireless handheld telephony device 111 with signals representing a request for authentication of at least selected targetlocal telephony device 101. Optionally, authentication of multiple targetlocal telephony devices 101 can be requested prior to selection by a user of wireless handheld telephony device 111. - At 808
wireless call server 105 responsible for controlling wireless handheld telephony device 111's end of the communications session can, using data provided by the wireless device (which might include data provided originally by the selected target local telephony devices 101), forward the request for authentication of the selected targetlocal telephony devices 101 to a PBX or other intermediary 130 controlling or otherwise responsible for administering the selected targetlocal telephony devices 101. Such data can, for example, be formatted in accordance with, or compatible with, any suitable protocols, as described herein. (Such server 16 can in various embodiments be incorporated in targetlocal telephony devices 101 as a software and/or hardware component thereof.) - At 810 intermediary 130 responsible for controlling selected target local telephony device(s) 101 can, before, after, or while authorizing and/or authenticating the availability and suitability of selected target local telephony device(s) 101 , send to the querying
wireless call server 105 signals representing a request for authentication of wireless handheld telephony device 111 from which the request originated. This may be done, for example, in order to confirm that wireless handheld telephony device 111 is a valid end user (e.g. that the device is not using a false identity or "spoofing"). - As will be appreciated by those skilled in the relevant arts, authentication of device(s) 111,101 , by their
responsible servers - At 812 the
responsible wireless server 105 can provide to the requesting intermediary 130 signals useful in establishing the authentication requested at 810. - At 814, in response to signals provided at 812, or independently, intermediary 130 can provide to the requesting
wireless call server 105 signals useful by thewireless server 105 in establishing the authentication requested at 808. - If either authentication fails, the requesting
server device 101, 111 can be notified and a new selection, or other appropriate action, may be requested. - At 816
wireless call server 105 can provide to the requesting wireless handheld telephony device 111 signals representing a request for confirmation that a user of the device 111 wishes to transfer the end of the call session assigned to wireless handheld telephony device 111 to a selected targetlocal telephony device 101. For example,wireless call server 105 can provide to wireless handheld telephony device 111 signals adapted to cause aprocessor 900 of the device 111 to display on anoutput display screen 928 of the device a request, which may be interactive, for the user of the device 111 to confirm his/her desire to complete the transfer. - In embodiments in which the request for confirmation presented to the user of wireless handheld telephony device 111 at 816 is implemented, at 820 the user can input command signals adapted to confirm or deny that the user wishes to complete transfer of the user's end of the call session to selected target
local telephony device 101. In the event the user's intent to transfer the call is confirmed, further processing can be undertaken bywireless call server 105 and other system components to transfer the call session, as herein described. I the event the user declines to confirm a desire to complete transfer of the call, processing can be halted and the pre-existing call session between wireless handheld telephony device 111 andthird telephony device 121 can be continued. - For example, at 820 a user of wireless handheld telephony device 111 can enter suitably-adapted keystrokes to cause
processor 900 of wireless handheld telephony device 111 to provide towireless call server 105 signals adapted for causingserver 105 to complete transfer of the call session. - In many embodiments, as will be readily appreciated by those skilled in the relevant arts, it will be desirable in transferring wireless handheld telephony device 111's end of a call to a selected local telephony device to place
third telephony device 121 in a 'hold' state, so thatthird telephony device 121's end of the existing call session (812) will not be dropped.Third telephony device 121 can be placed in such a hold state at any necessary or convenient point in the transfer process. As will be understood by those skilled in the relevant arts, such a necessary or convenient point may depend upon the protocol(s) and system architecture(s) used in creating and controlling the relevant call sessions. Thus, ifthird telephony device 121 has not already been placed in a hold state, at 822wireless call server 105 can send to third telephony device 121 (or its corresponding server) a signal requesting thatthird telephony device 121's end of the call session be placed in a hold state. - At 824
wireless call server 105, having received a request for transfer of wireless handheld telephony device 111's end of the call session to selected targetlocal telephony device 101 and optionally a confirmation of that request, can forward to intermediary 130 controlling selected target local telephony device 101 a request for targetlocal telephony device 101 to join the call session previously established between wireless handheld telephony device 111 andthird telephony device 121, or otherwise accept transfer of wireless handheld telephony device 111's end of that call session. - As noted herein, it is desirable in some embodiments that a selected or selectable (i.e., target)
local telephony device 101 be provided with means such as an audio and/or visual signal for identifying to a user of wireless handheld telephony device 111 the selected or selectablelocal telephony device 101, and optionally for indicating to such user that the selected or selectable (i.e., target)local telephony device 101 is ready to assume wireless handheld telephony device 111's end of the communications session. For example, at 826, in response to the signal provided bylocal call server 105 at 824, intermediary 130 can send to selected target local telephony device 101 a signal adapted to cause selected targetlocal telephony device 101 to provide for the user of wireless handheld telephony device 111 a ringtone or other audio and/or visual signal, so that the user will pick up the receiver of selected targetlocal telephony device 101, activate a speakerphone control, or otherwise activate the local telephony device in order to complete the transfer of wireless handheld telephony device 111's end of the communication session. - At 828, and optionally in response to the sending of the ringtone or other signal command by intermediary 130 at 826, the user of wireless handheld telephony device 111 (or other user) can pick up the receiver of selected target
local telephony device 101 , activate a speakerphone control, or otherwise initiate pick-up of wireless handheld telephony device 111's end of the communications session, and cause targetlocal telephony device 101 to provide to intermediary 130 a signal indicating that selected targetlocal telephony device 101 is ready to accept transfer of the communications session. - As shown at 830, upon activation of target
local telephony device 101 at 828, upon confirmation at 820 of the user's desire to transfer the call, or at other suitable point, intermediary 130 can provide towireless call server 105 signals confirming that selected targetlocal telephony device 101 has initiated the call pick-up process and thatwireless server 105 may terminate wireless handheld telephony device 111's end of the call session. - As shown at 834,
wireless server 105, upon receipt of confirmation that selected targetlocal telephony device 101 and/or intermediary 130 have initiated the process of picking up wireless handheld telephony device 111's end of the call session, can terminate wireless handheld telephony device 111's end of the call session. Suitable confirmation may be provided by thewireless server 105 to the wireless device. - As shown at 832, intermediary 130, upon confirmation or instruction that selected local device is ready to pick up wireless handheld telephony device 111's end of the call session, can provide to
third telephony device 121 and/or a call server controllingthird telephony device 121 signals configured for use bythird telephony device 121 and/or its server in causing outgoing communications fromthird telephony device 121 to be routed to selected targetlocal telephony device 101, and incoming communications from targetlocal telephony device 101 to be routed tothird telephony device 121. - As shown at 836, and necessary or desirable signals useful for causing selected target
local telephony device 101 to communicate withthird telephony device 121 can be sent to selected targetlocal telephony device 101, so that at 838 the transferred call session can continue, between selectedlocal device 101 andthird telephony device 121. - Further signals useful for processing communications between target
local telephony device 101 andthird telephony device 121 can be provided and processed according to any desired telephony protocol. - Reference will now be made to
Figures 10A, 10B and10C , which show, in block diagram form, threeexample systems 900A, 900B and 900C for transferring communication from a wireless handheld telephony device 111 to asecond telephony device 101. In each of these diagrams, data connections are represented by solid lines where as voice connections are represented by dashed lines.Systems 900A, 900B and 900C ofFigures 10A, 10B and10C , respectively, may represent specific examples of system 100 ofFigure 6 . - Referring first to
Figure 10A , an example system for transferring a communication is shown involving a corporate or enterprise environment. In this example, intermediary 130 comprisesenterprise server PBX third telephony device 121 throughPBX 906. In this embodiment,second telephony device 101 may be another corporate telephony device which is configured to communicate throughPBX 906. - Wireless handheld telephony device 111 may receive wireless signals from
second telephony device 101 as described above. Wireless handheld telephony device 111 may send identifying information received through the wireless signals to the enterprise serve 902 andcorporate MVS 904. Using this information,corporate MVS 904 may instructPBX 906 to transfer the communication session from wireless handheld telephony device 111 tosecond telephony device 101 such that the communication session continues betweensecond telephony device 101 and at least onethird telephony device 121 throughPBX 906. - Referring next to
Figure 10B , an example system for transferring a communication is shown involving a consumer environment. In this embodiment, intermediary 130 comprisesinternet server 908,consumer MVS 910 and switchingenvironment 912. Wireless handheld telephony device 111 may be engaged in an ongoing conversation with at least onethird telephony device 121 through switchingenvironment 912. In this embodiment,second telephony device 101 may be a public telephony device which is capable of communicating through switchingenvironment 912. - Wireless handheld telephony device 111 may receive wireless signals from
second telephony device 101 as described above. Wireless handheld telephony device 111 may send identifying information received through the wireless signals through a data connection tointernet server 908 which is connected toconsumer MVS 910.Switching environment 912 may then be directed to transfer the ongoing communication from wireless handheld telephony device 111 tosecond telephony device 101 such that the communication session continues betweensecond telephony device 101 and at least onethird telephony device 121 through switchingenvironment 912. In some embodiments, wheresecond telephony device 101 is configured for voice communications over the internet (such as a Skype-enabled device), the communication session may be transferred via switchingenvironment 912 over the internet using IP addressing. In other embodiments, the communication session may be transferred via switchingenvironment 912 over, for example a PSTN such asPSTN 40 ofFigure 1 . - Finally, referring to
Figure 10C , an example system for transferring a communication is shown involving a consumer environment where a data connection is not available. In this embodiment, intermediary 130 comprises a service provider switching environment 914. Wireless handheld telephony device 111 may be engaged in an ongoing conversation with at least onethird telephony device 121 through service provider switching environment 914. In this embodiment,second telephony device 101 may be a public telephony device which is capable of communicating through service provider switching environment 914. - Wireless handheld telephony device 111 may receive wireless signals from a
second telephony device 101 as described above. Once the identity ofsecond telephony device 101 to which communication will be transferred has been established, wireless handheld telephony device 111 may provide this information to the service provider switching environment 914. This may be done using, for example, in-band or sideband DTMF, data signaling via a carrier APN or simple SMS back to the SPSE or using any other available protocol. Service provider switching environment 914 may transfer the ongoing communication from wireless handheld telephony device 111 tosecond telephony device 101 such that the communication session continues betweensecond telephony device 101 and at least onethird telephony device 121 through service provider switching environment 914. - While the this disclosure and its examples have been described and illustrated in connection with specific, presently-preferred embodiments, many variations and modifications may be made without departing from the spirit and scope of the disclosure. The disclosure is therefore not to be limited to the exact components or details of methodology or construction set forth above. Except to the extent necessary or inherent in the processes themselves, no particular order to steps or stages of methods or processes described in this disclosure, including the Figures, is intended or implied. In many cases the order of process steps may be varied without changing the purpose, effect, or import of the methods described. The scope of the claims is to be defined solely by the appended claims, giving due consideration to the doctrine of equivalents and related doctrines.
Claims (13)
- A method of transferring to a second telephony device (17,101) an end of a communications session previously established between a wireless handheld telephony device (11,111) and at least one third telephony device (121), the wireless handheld telephony device (11, 1 1 1 ) comprising at least one wireless signal receiver (908), at least one wireless signal transmitter (906), at least one data processor (900), and media readable by the at least one data processor (900) comprising coded program instructions, the method comprising:while maintaining the previously-established communications session between the wireless handheld telephony device (11,111) and the at least one third telephony device (121), receiving direct from one or m ore target local telephony devices (17,101) one or more wireless signals representing data useful for establishing communications between the one or more target local telephony devices (17, 101) and a call server (105) managing the end of the previously-established communications session associated with the wireless handheld telephony device (11,111);using the wireless signals received direct from the one or more target local telephony devices (17,101), instructing the call server (105) to establish a communications session between a selected one of the at least one target local telephony devices (17,101) and the at least one third telephony device (121); andupon establishment of a communications session between the selected local telephony device (17,101) and the at least one third telephony device (121), terminating the previously-established communications session between the wireless handheld telephony device (11,111) and the at least one third telephony device (121).
- The method of claim 1,wherein the wireless signals representing data useful for establishing communications between the one or more target local telephony devices (17,101)and a call server (105) include signals representing one or more of an extension number, a name, an office location and a relative physical location for each of the one or more target local telephony devices (17, 101).
- The method of claim 1 or claim 2, further comprising providing to the wireless handheld telephony device (11,111) signals for causing the wireless handheld telephony device (11,111) to display a list identifying the one or more target local telephony devices (17, 101).
- The method of claim 3, wherein the list comprises all local telephony devices (17, 101) within a predetermined range of the wireless handheld telephony device (11,111).
- The method of claim 3, wherein the list comprises local telephony devices (17,101) within range of the wireless handheld telephony device (11,111) which are in an idle state.
- The method of claim 3, wherein the list comprises a predetermined number of local telephony devices (17, 101) within range of the wireless handheld telephony device (11, 111).
- The method of claim 6, wherein the predetermined number of local telephony devices (17,101) are listed according to: distance from the wireless handheld telephony device (11, 111); one or more previously determined criteria established by an administrator of the wireless handheld telephony device (11,111);and one or more previously determined criteria established by a user associated with the wireless handheld telephony device (11,111).
- The method of any one of claims 1 to 7, further comprising providing to the wireless handheld telephony device (11,111) signals representing information useful in physically locating the one or more target local telephony devices (17,101).
- The method of claim 8, wherein the information useful in physically locating the one or more target local telephony devices (17, 101) comprises at least one of a map and textual information useful for locating the one or more target local telephony devices (17, 101).
- A wireless handheld telephony device (11, 111) comprising at least one wireless signal receiver (908), at least one wireless signal transmitter (906), at least one data processor (900), and media readable by the at least one data processor (900) comprising coded program instructions adapted for enabling the wireless handheld telephony device (11,111) to cause transfer to a second telephony device (17,101) of an end of a communications session previously established between the wireless handheld telephony device (11,111) and at least one third telephony device (121) according to the method of any one of claims 1 to 9
- The wireless handheld telephony device of claim 10, wherein the wireless signals are pulled from the one or more target local telephony devices (17,101) by the wireless handheld telephony device (11, 111).
- The wireless handheld telephony device of claim 11, wherein the one or more target local telephony devices (17,101) comprise an RFI D transponder and the wireless handheld telephony device (11,111) comprises an RFID transmitter (906) adapted to pull the wireless signals from the transponder of the one or more target local telephony devices (17,101).
- The wireless handheld telephony device of any one of claims 10 to 12, further comprising at least one display (928) for displaying a list identifying the one or more target local telephony devices (17, 101).
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US29701410P | 2010-01-21 | 2010-01-21 |
Publications (1)
Publication Number | Publication Date |
---|---|
EP2355479A1 true EP2355479A1 (en) | 2011-08-10 |
Family
ID=42732002
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP10166494A Withdrawn EP2355479A1 (en) | 2010-01-21 | 2010-06-18 | Call transfer using a direct short-range information exchange between the transferor and the transfer target |
Country Status (3)
Country | Link |
---|---|
US (1) | US8798605B2 (en) |
EP (1) | EP2355479A1 (en) |
CA (1) | CA2725507A1 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP3588925A1 (en) * | 2018-06-29 | 2020-01-01 | Nagravision S.A. | Method for switching a communication link and system and device for implementing this method |
Families Citing this family (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP5826254B2 (en) * | 2010-05-11 | 2015-12-02 | オランジュ | Call transfer from a first fixed communication terminal located in the local network to a second fixed communication terminal in the same local network |
US9367224B2 (en) * | 2011-04-29 | 2016-06-14 | Avaya Inc. | Method and apparatus for allowing drag-and-drop operations across the shared borders of adjacent touch screen-equipped devices |
US9078078B1 (en) | 2011-09-15 | 2015-07-07 | Google Inc. | Call forwarding methods and systems |
US8639230B2 (en) * | 2011-11-04 | 2014-01-28 | Google Inc. | Transferring an active call to another device |
US8515407B1 (en) | 2012-03-21 | 2013-08-20 | Google Inc. | Redirecting incoming phone calls |
US9240941B2 (en) * | 2012-05-09 | 2016-01-19 | Twilio, Inc. | System and method for managing media in a distributed communication network |
EP2770713B1 (en) * | 2013-02-25 | 2017-11-15 | Alcatel Lucent | Enterprise phone that can provide professional services during a communication set up on a private cellular phone |
US20140269439A1 (en) * | 2013-03-15 | 2014-09-18 | Vonage Network, Llc | Systems and methods for handling incoming communications directed to a telephony device |
EP2802134B1 (en) * | 2013-05-08 | 2019-12-11 | Swisscom AG | Call-forward initiated by hand movement |
US9294455B2 (en) | 2013-06-04 | 2016-03-22 | Google Inc. | Maintaining video conference session continuity during transfer of session to alternative device |
WO2014201669A1 (en) * | 2013-06-20 | 2014-12-24 | Nokia Corporation | Method and apparatus for causation of performance of an activity on a companion apparatus |
US10313514B1 (en) * | 2018-02-21 | 2019-06-04 | Plantronics, Inc. | Device registry for mediating communication sessions |
US10958706B2 (en) | 2018-11-02 | 2021-03-23 | Infinite Convergence Solutions, Inc. | Devices and method for voice over internet protocol call continuity |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2001043459A2 (en) * | 1999-12-08 | 2001-06-14 | Koninklijke Philips Electronics N.V. | Method for in-progress telephone call transfer between a wireless telephone and a wired telephone using a short-range communication control link |
US20030073431A1 (en) * | 2001-10-16 | 2003-04-17 | Jheroen Dorenbosch | Transferring communications over a network |
US7171221B1 (en) * | 1999-12-20 | 2007-01-30 | Cingular Wirelesss Ii, Llc | System and method for automatically transferring a call from a first telephone to a designated telephone in close proximity |
WO2007050126A1 (en) * | 2005-10-26 | 2007-05-03 | Sony Ericsson Mobile Communications Ab | Method and apparatus for multimedia session transfer |
US20070274292A1 (en) * | 2006-05-24 | 2007-11-29 | Sbc Knowledge Ventures, L.P. | Method and apparatus for migrating between terminals |
GB2452020A (en) * | 2007-07-20 | 2009-02-25 | Nec Technologies | Communication establishment methodand related communication devices |
Family Cites Families (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7072457B2 (en) * | 2001-12-17 | 2006-07-04 | International Business Machines Corporation | Transferring a call to a backup according to call context |
US7092385B2 (en) * | 2002-03-12 | 2006-08-15 | Mci, Llc | Policy control and billing support for call transfer in a session initiation protocol (SIP) network |
US20060072591A1 (en) | 2004-09-24 | 2006-04-06 | Gary Rogalski | Initiation of call forwarding for wireless telephone |
US7424288B2 (en) * | 2004-11-22 | 2008-09-09 | Searete Llc | Call transfer to proximate devices |
US20060246882A1 (en) * | 2005-04-29 | 2006-11-02 | Siemens Communications, Inc. | Intelligent call forwarding via RFID technology |
NO322831B1 (en) * | 2005-07-15 | 2006-12-11 | Tandberg Telecom As | Procedure for immediate conference call scheduling. |
US20090296913A1 (en) * | 2008-05-28 | 2009-12-03 | Eric Thomas | System and method for location based call processing |
US8848895B2 (en) | 2008-05-30 | 2014-09-30 | Verizon Patent And Licensing Inc. | Method and system for a call transfer |
US20110177801A1 (en) * | 2010-01-21 | 2011-07-21 | Research In Motion Limited | System and Method for Transferring Telephony Functions Associated With A Wireless Handheld Telephony Device |
-
2010
- 2010-06-18 EP EP10166494A patent/EP2355479A1/en not_active Withdrawn
- 2010-06-18 US US12/818,642 patent/US8798605B2/en not_active Expired - Fee Related
- 2010-12-15 CA CA2725507A patent/CA2725507A1/en not_active Abandoned
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2001043459A2 (en) * | 1999-12-08 | 2001-06-14 | Koninklijke Philips Electronics N.V. | Method for in-progress telephone call transfer between a wireless telephone and a wired telephone using a short-range communication control link |
US7171221B1 (en) * | 1999-12-20 | 2007-01-30 | Cingular Wirelesss Ii, Llc | System and method for automatically transferring a call from a first telephone to a designated telephone in close proximity |
US20030073431A1 (en) * | 2001-10-16 | 2003-04-17 | Jheroen Dorenbosch | Transferring communications over a network |
WO2007050126A1 (en) * | 2005-10-26 | 2007-05-03 | Sony Ericsson Mobile Communications Ab | Method and apparatus for multimedia session transfer |
US20070274292A1 (en) * | 2006-05-24 | 2007-11-29 | Sbc Knowledge Ventures, L.P. | Method and apparatus for migrating between terminals |
GB2452020A (en) * | 2007-07-20 | 2009-02-25 | Nec Technologies | Communication establishment methodand related communication devices |
Non-Patent Citations (1)
Title |
---|
SALEEM A., MEDIA SERVER MARKUP LANGUAGE, 7 August 2008 (2008-08-07) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP3588925A1 (en) * | 2018-06-29 | 2020-01-01 | Nagravision S.A. | Method for switching a communication link and system and device for implementing this method |
Also Published As
Publication number | Publication date |
---|---|
US20110177818A1 (en) | 2011-07-21 |
US8798605B2 (en) | 2014-08-05 |
CA2725507A1 (en) | 2011-07-21 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8798605B2 (en) | System and method for transferring an ongoing communication from a wireless handheld telephony device | |
CA2725514C (en) | System and method for transferring an ongoing communication from a wireless handheld telephony device | |
US9225839B2 (en) | System and method for reconnecting a device to a group call | |
CA2701553C (en) | Method and system for pulling a call | |
US20130129065A1 (en) | Call access management | |
US8676179B2 (en) | System and method for providing identifying information to a mobile device | |
US8428647B2 (en) | Verifying and identifying incoming PBX calls on mobile devices | |
US20110183653A1 (en) | Error correction for dtmf corruption on uplink | |
CA2722550C (en) | Verifying and identifying incoming pbx calls on mobile devices | |
CA2694508C (en) | System and method for reconnecting a device to a group call | |
CA2718213C (en) | System, method and device for maintaining a communication session suspended for servicing of power supply | |
CA2725916C (en) | Error correction for dtmf corruption on uplink | |
CA2694891C (en) | System and method for providing identifying information to a mobile device | |
CA2692078C (en) | System and method for establishing a secure communication link | |
EP2418834A1 (en) | Call Management | |
EP2378756A1 (en) | Call access management |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
17P | Request for examination filed |
Effective date: 20100618 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO SE SI SK SM TR |
|
AX | Request for extension of the european patent |
Extension state: BA ME RS |
|
RAP1 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: BLACKBERRY LIMITED |
|
RAP1 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: BLACKBERRY LIMITED |
|
17Q | First examination report despatched |
Effective date: 20140530 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN |
|
18D | Application deemed to be withdrawn |
Effective date: 20170103 |