US20130115996A1 - Systems and methods for facilitating push-to-talk (ptt) communications using sip-based messaging - Google Patents
Systems and methods for facilitating push-to-talk (ptt) communications using sip-based messaging Download PDFInfo
- Publication number
- US20130115996A1 US20130115996A1 US13/725,031 US201213725031A US2013115996A1 US 20130115996 A1 US20130115996 A1 US 20130115996A1 US 201213725031 A US201213725031 A US 201213725031A US 2013115996 A1 US2013115996 A1 US 2013115996A1
- Authority
- US
- United States
- Prior art keywords
- media
- server
- client device
- ptt
- server device
- 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.)
- Abandoned
Links
- 238000004891 communication Methods 0.000 title claims abstract description 62
- 238000000034 method Methods 0.000 title claims abstract description 52
- 230000000977 initiatory effect Effects 0.000 claims description 21
- TYRFQQZIVRBJAK-UHFFFAOYSA-N 4-bromobenzene-1,2,3-triol Chemical compound OC1=CC=C(Br)C(O)=C1O TYRFQQZIVRBJAK-UHFFFAOYSA-N 0.000 description 17
- 230000004044 response Effects 0.000 description 12
- 238000012545 processing Methods 0.000 description 11
- 230000006870 function Effects 0.000 description 9
- 238000010586 diagram Methods 0.000 description 6
- 230000001413 cellular effect Effects 0.000 description 5
- 238000013515 script Methods 0.000 description 5
- 230000011664 signaling Effects 0.000 description 3
- 230000006978 adaptation Effects 0.000 description 2
- 230000001419 dependent effect Effects 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 230000010354 integration Effects 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 235000006508 Nelumbo nucifera Nutrition 0.000 description 1
- 240000002853 Nelumbo nucifera Species 0.000 description 1
- 235000006510 Nelumbo pentapetala Nutrition 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000000903 blocking effect Effects 0.000 description 1
- 230000010267 cellular communication Effects 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 230000008929 regeneration Effects 0.000 description 1
- 238000011069 regeneration method Methods 0.000 description 1
- 238000012552 review Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
- H04W4/10—Push-to-Talk [PTT] or Push-On-Call services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/40—Support for services or applications
- H04L65/4061—Push-to services, e.g. push-to-talk or push-to-video
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M7/00—Arrangements for interconnection between switching centres
- H04M7/12—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal
- H04M7/1205—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal where the types of switching equipement comprises PSTN/ISDN equipment and switching equipment of networks other than PSTN/ISDN, e.g. Internet Protocol networks
- H04M7/121—Details of network access arrangements or protocols
-
- 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
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/4228—Systems providing special services or facilities to subscribers in networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/12—Setup of transport tunnels
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/40—Connection management for selective distribution or broadcast
- H04W76/45—Connection management for selective distribution or broadcast for Push-to-Talk [PTT] or Push-to-Talk over cellular [PoC] services
Definitions
- the present application relates to push-to-talk systems and methods, and in particular to implementing push-to-talk using Session Initiation Protocol (SIP).
- SIP Session Initiation Protocol
- Push-to-talk generally refers to real-time direct one-to-one and one-to-group voice communication service, which may occur in the cellular, Public Switch Telephone Networks (PSTN) and Internet networks. PTT calls can be directed to both individuals and talk groups. In a PTT call, the call connection is initiated by an originator device while the receiver typically does not have to “answer” the call.
- PSTN Public Switch Telephone Networks
- PTT calls are one-way communications (half-duplex), which means that while one person speaks the others listen. In a PTT conversation, users typically no longer need to make several calls to coordinate with a group.
- PTT service users are typically engaged in some other activity than a telephone call, and they listen to the group traffic during their activity.
- a user is usually contacted by receiving a PTT call from a member of the PTT group and can respond to the PTT group with a push of a key.
- Session Initiation Protocol is a protocol which is based on a request-response model. SIP leaves open the particular implementation of the desired functionality, and for example does not provide for specific implementation of PTT. As the interpretation remains open, some implementations of PTT using SIP may lead to inefficiencies.
- media parameters are negotiated and communicated only once the PTT call is initiated by a user. This wastes resources and time between when the user actually initiates the PTT call and when the system connects the user to the receiving units. Call lags may occur each time a user initiates a PTT call. Further, such inefficiencies become magnified when the PTT group involves a large number of parties.
- FIG. 1 shows, in block diagram form, an example system for managing enterprise-related mobile calls, including an enterprise communications platform, to which example embodiments may be applied;
- FIG. 2 shows, in block diagram form, further details of an embodiment of the enterprise communications platform
- FIG. 3 shows another embodiment of the enterprise communications platform
- FIG. 4 shows yet another embodiment of the enterprise communications platform
- FIG. 5 shows further details of the enterprise communications platform of FIG. 3 ;
- FIG. 6 shows, in block diagram form, an example push-to-talk system and associated push-to-talk procedure implemented by the system of FIG. 1 ;
- FIG. 7 shows, in block diagram form, an example push-to-talk subscription procedure between a client device and a server device implemented prior to the push-to-talk procedure in the push-to-talk system of FIG. 6 ;
- FIG. 8 shows an example message to be used between devices within the push-to-talk procedures of FIGS. 6 to 7 ;
- FIG. 9 shows an example message from the client device to the server device in the subscription procedure of FIG. 8 ;
- FIG. 10 shows an example message from the sever device to the client device in the subscription procedure of FIG. 8 ;
- FIG. 11 shows an example message from an originator client device initiating a push-to-talk session within the push-to-talk procedure of FIG. 7 ;
- FIG. 12 shows an example message from a server device to receiving client devices within the push-to-talk procedure of FIG. 7 .
- a method of facilitating push-to-talk (PTT) communications between a server device and a client device using SIP-based messaging the server device being in communication with a media server.
- the method includes: receiving in the server device from the client device a SUBSCRIBE message for subscription to a push-to-talk group, the SUBSCRIBE message including media information of the client device, storing in the server device the media information of the client device, and initiating, based on receipt in the server device of a second SUBSCRIBE message for initiating a push-to-talk session, a media session between the media server and the client device using the stored media information.
- PTT push-to-talk
- a method of facilitating push-to-talk (PTT) communications between a server device and a client device using SIP-based messaging the server device being in communication with a media server.
- the method includes: receiving in the server device from the client device a SUBSCRIBE message for subscription to a push-to-talk group, sending from the server device to the client device a NOTIFY message, the NOTIFY message including media information of the media server for storage by the client device, and initiating, based on receipt in the server device of a second SUBSCRIBE message for initiating a push-to-talk session, a media session between the media server and the client device using the stored media information.
- PTT push-to-talk
- a server device for facilitating push-to-talk (PTT) communications using SIP-based messaging.
- the server device includes a memory, a controller for accessing the memory, a communications module in communications with the controller for communicating with a media server and a client device.
- the controller is configured to: receive from the client device a SUBSCRIBE message for subscription to a push-to-talk group, the SUBSCRIBE message including media information of the client device, store in memory the media information of the client device, send to the client device a NOTIFY message, the NOTIFY message including media information of the media server for storage by the client device, and initiate, based on receipt of a second SUBSCRIBE message for initiating a push-to-talk session, a media session between the media server and the client device using the stored media information.
- a system for facilitating push-to-talk (PTT) communications using SIP-based messaging includes a media server, a server device in communication with the media server, and at least one PTT receiving client devices, each for sending to the server device a SUBSCRIBE message for subscription to a push-to-talk group, the SUBSCRIBE message including media information of each of the PTT receiving client devices.
- the system further includes a PTT originator client device for sending to the server device a SUBSCRIBE message for subscription to a push-to-talk group.
- the server device is configured to: store the media information of the PTT-receiving client devices, and send to the PTT originator client device a NOTIFY message, the NOTIFY message including media information of the media server.
- the PTT originator client device is configured to store the media information of the media server.
- the server device is further configured to, upon receipt in the server device from the PTT originator client device of a second SUBSCRIBE message for initiating a push-to-talk session, initiate a media session between the media server and the client devices using the stored media information.
- the present application relates to the control and management of push-to-talk (PTT) communications.
- PTT push-to-talk
- calls and “talk” 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.
- Reference to calls may for example include voice calls as well as media sessions which may for example include video and/or audio.
- FIG. 1 shows, in block diagram form, an example system, generally designated 10 , for the control and management of communications.
- the system 10 includes an enterprise or business system 20 , which in many embodiments includes a local area network (LAN).
- LAN local area network
- the enterprise or business system 20 may be referred to as an enterprise network 20 .
- the enterprise network 20 may include more than one network and may be located in multiple geographic areas in some embodiments.
- the enterprise network 20 may be connected, often through a firewall 22 , to a wide area network (WAN) 30 , such as the Internet.
- WAN wide area network
- the 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.
- DID direct inward dialing
- PRI primary rate interface
- the 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.
- PLMN public land mobile network
- WWAN wireless wide area network
- the connection with the PLMN 50 may be made via a relay 26 , as known in the art.
- the enterprise network 20 may also provide a wireless local area network (WLAN) 32 a featuring wireless access points.
- WLANs 32 may exist outside the enterprise network 20 .
- WLAN 32 b may be connected to WAN 30 .
- the system 10 may include a number of enterprise-associated mobile devices 11 (only one shown).
- the mobile devices 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 , or dual-mode devices capable of both cellular and WLAN communications.
- WLANs 32 may be configured in accordance with one of the IEEE 802.11 specifications.
- 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 known manner, as the user moves.
- the dual-mode mobile devices 11 and/or the 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.
- the enterprise network 20 typically includes a number of networked servers, computers, and other devices.
- the 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.
- the enterprise network 20 may also connect to one or more digital telephone sets 17 (one shown).
- the 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 the enterprise network 20 .
- Typical mail servers include the Microsoft Exchange ServerTM and the IBM Lotus DominoTM server.
- Each user within the enterprise typically has at least one user account within the enterprise network 20 .
- message address information such as an e-mail address.
- Messages addressed to a user message address are stored on the 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 the 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 the 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 the enterprise network 20 to the mobile device 11 via the PLMN 50 .
- the enterprise network 20 also includes an enterprise server 12 .
- the enterprise server 12 functions to redirect or relay incoming e-mail messages addressed to a user's e-mail address within the enterprise network 20 to the user's mobile device 11 and to relay incoming e-mail messages composed and sent via the mobile device 11 out to the intended recipients within the WAN 30 or elsewhere.
- the enterprise server 12 and relay 26 together 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 the enterprise network 20 using the user's enterprise-related e-mail address, for example on computer 15 .
- the enterprise network 20 includes a Private Branch eXchange (although in various embodiments the PBX may be a standard PBX or an IP-PBX, 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 for the enterprise.
- the PBX 16 is connected to the PSTN 40 via DID trunks or PRI trunks, for example.
- the 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.
- the PBX 16 may be connected to one or more conventional analog telephones 19 .
- the PBX 16 is also connected to the 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 the PBX 16 to the PSTN 40 or incoming from the PSTN 40 to the 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
- the enterprise network 20 may further include a Service Management Platform (SMP) 18 for performing some aspects of messaging or session control, like call control and advanced call processing features.
- SMP 18 may, in some cases, also perform some media handling.
- Collectively the SMP 18 and PBX 16 may be referred to as the enterprise communications platform, generally designated 14 .
- the enterprise communications platform 14 and, in particular, the SMP 18 is implemented on one or more servers having suitable communications interfaces for connecting to and communicating with the PBX 16 and/or DID/PRI trunks.
- the 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, the SMP 18 may be implemented as a multi-layer platform.
- the enterprise communications platform 14 implements the switching to connect session legs and may provide the conversion between, for example, a circuit-switched call and a VoIP call, or to connect legs of other media sessions.
- 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 SIP may be used to set-up, manage, and terminate media sessions for voice calls.
- CTI Computer Telephony Integration
- SIMPLE Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions
- APIs Application Programming Interfaces
- One of the functions of the enterprise communications platform 14 is to extend the features of enterprise telephony to the mobile devices 11 .
- the enterprise communications platform 14 may allow the mobile device 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.
- FIG. 2 illustrates an embodiment intended for use in a circuit-switched TDM context.
- the PBX 16 is coupled to the SMP 18 via PRI connection 60 or other suitable digital trunk.
- the PRI 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.
- CSU channel service unit
- the 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 the PBX 16 are handled by the 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 the SMP 18 . Thereafter, a call leg is established from the SMP 18 to the called party within the enterprise, and the two legs are bridged.
- the SMP 18 includes a digital trunk interface 62 and a digital signal processing (DSP) conferencing bridge 64 .
- the DSP conferencing bridge 64 performs the bridging of calls for implementation of various call features, such as conferencing, call transfer, etc.
- the 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.
- the 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
- the SMP 18 may include various scripts 66 for managing call processing.
- the scripts 66 are implemented as software modules, routines, functions, etc., stored in non-volatile memory and executed by the processor of the SMP 18 .
- the 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 the PBX 16 performs the functions of terminating and/or bridging media streams, but call control functions are largely handled by the SMP 18 .
- the SMP 18 may be referred to as a call control server 18 .
- This architecture may be referred to as “Third-Party Call Control”.
- the call control server 18 is coupled to the PBX 16 , for example through the LAN, enabling packet-based communications and, more specifically, IP-based communications. In one embodiment, communications between the PBX 16 and the call control server 18 are carried out in accordance with SIP. In other words, the call control server 18 uses SIP-based communications to manage the set up, tear down, and control of media handled by the PBX 16 . In one example embodiment, 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 the 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.
- the 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.
- the 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.
- the 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
- the SIP server 72 interacts with the media server 76 using SIP-based media handling commands.
- the 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, Aug. 7, 2008.
- the media server 76 may be configured to perform Host Media Processing (HMP).
- HMP Host Media Processing
- the SMP 18 is a multi-layer platform that includes a protocol layer 34 , a services layer 36 and an application layer 38 .
- the 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.
- the protocol layer 34 preferably includes protocols which allow media to be controlled separate from data.
- the protocol layer 34 can include, among other things, a Session Initiation Protocol or SIP 80 , a Web Services protocol 82 , an Application Programming 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 .
- the interface protocols 80 - 88 are plug-ins that can interface directly with corresponding servers in the enterprise network 20 , which will be further described below.
- SIP 80 will be utilized, although it is appreciated that the system 10 can operate using the above disclosed or additional 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.
- the 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”).
- the SIP-T interface is utilized when the endpoint is a non-specific entity or not registered (i.e., when communicating between two network entities).
- the SIP-L interface is utilized when the endpoint is registered (i.e., when dialing to a specific extension).
- SIP is defined in J. Rosenberg et al., “RFC 3261—Session Initiation Protocol” (June 2002), the contents of which are herein incorporated by reference. Other procotols, extensions, and standards related to SIP may be implemented and referenced, as appropriate.
- Session Description Protocol SDP
- SDP Session Description Protocol
- the SMP 18 also includes a plurality of enablers, among other things, a VoIP enabler 90 , a Fixed Mobile Convergence or FMC enabler 92 , a conference services enabler 94 , a presence enabler 96 and an Instant Messaging or IM enabler 98 .
- Each of the enablers 90 - 98 are 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 is then 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.
- the 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 .
- the conference server 55 is provided in the enterprise network 20 and is in communication with the conference services enabler 94 preferably through the 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 .
- the 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 PTT system, generally designated 110 , for implementing a push-to-talk (PTT) procedure 140 in accordance with example embodiments.
- the PTT system 110 includes a PTT server device 112 in communication with a number of PTT client devices 114 , illustrated as one PTT originator 116 and a plurality of PTT receivers 118 , 120 , 122 .
- the client devices 114 may collectively form a PTT group.
- the PTT receivers 118 , 120 , 122 may also sometimes be referred to as terminating devices.
- the server device 112 includes a controller and a memory for storage of, among other items, the media information of client devices 114 which subscribe to a push-to-talk group.
- the server device 112 includes a communications module or submodule for communicating with other devices.
- the server device 112 may for example be part of the call control server or SMP 18 ( FIGS. 1-5 ).
- the server device 112 may further be part of the enterprise or business system 20 ( FIG. 1 ).
- the server device 112 may include or be coupled to the media server 76 ( FIG. 4 ), wherein the server device 112 controls the media handling of the media server 76 .
- client devices 114 are illustrated as handheld mobile communication devices (such as a smart phone, cellular phone, soft phone, dual-mode phone, etc.), the client devices may be any device configured with the functionality described herein, and may for example include computer devices, relays, proxies, gateways and any appropriate User Agents (as defined in SIP).
- client devices may be any device configured with the functionality described herein, and may for example include computer devices, relays, proxies, gateways and any appropriate User Agents (as defined in SIP).
- FIG. 7 shows a subscription procedure between the server device 112 and a client device 114 .
- the PTT system 110 provides a subscription-based communications wherein certain information, including media information, may be communicated between the client devices 114 and the server device 112 prior to initiation of the actual PTT session (also referred to as PTT call).
- Some communications within the PTT system 110 implement the SUBSCRIBE and NOTIFY requests, which are defined in A. B. Roach, “RFC 3265-Session Initiation Protocol (SIP)-Specific Event Notification” (June 2002), the contents of which are herein incorporated by reference.
- a PTT session is implemented by using INVITE to set a pre-established (or early) session mode.
- INVITE the basic request/response functionality provided by INVITE. It is recognized herein that the SIP SUBSCRIBE method and related commands may provide further and additional functionality and flexibility in implementation, as can be appreciated in view of the description below.
- the client device 114 sends a SUBSCRIBE request to the server device 112 , including information regarding the push-to-talk group number of the device and the port number of the particular mobile device 114 that is used to receive subsequent message, as well as for receiving a future PTT session.
- the server device 112 provides a 200-OK message (accepting the subscription request).
- the server device 112 may also reject the subscription request (and/or the subscription request may fail), for example using the 4xx or 5xx family of responses.
- the server device 112 sends a NOTIFY request to the client device 114 , with media information including a port number of the media server 176 ( FIG. 4 ) for future PTT sessions originating from the particular client device 114 .
- the client device 114 accepts the NOTIFY message by using 200-OK response.
- the server device 112 is therefore informed of the port information of each subscribing client device 114 , while each client device is informed of the port information of the media server 176 .
- the PTT procedure 140 is used to establish a PTT call or session from the PTT originator 116 to the PTT receivers 118 , 120 , 122 .
- the PTT procedure 140 typically occurs after the subscription procedure 130 ( FIG. 7 ), with the media parameters already communicated.
- the PTT originator 116 sends another SUBSCRIBE request (indicated as “RE-SUSCRIBE” for convenience) to the server device 112 .
- the server device 112 sends NOTIFY requests to the PTT receivers 118 , 120 , 122 .
- the NOTIFY request includes an indication of a new “active” state.
- the PTT receivers 118 , 120 , 122 respond with a 200-OK message if a PTT call is acceptable to be received.
- a busy message such as 486-Busy may be sent as a response if the particular PTT receiver 118 , 120 , 122 is busy or not accepting the PTT call.
- Each PTT receiver 118 , 120 , 122 which indicated 200-OK further opens its allocated port for receiving media from the media server 76 ( FIG. 4 ), for example Real-Time Transport Protocol (RTP) media, as could be implemented by those skilled in the art.
- RTP Real-Time Transport Protocol
- the server device 112 sends a 200-OK for the re-subscription message if at least one of the PTT-receivers 118 , 120 , 122 is not busy.
- the media server 76 may thereafter open its media port for receiving or listening to media from the PTT originator 116 .
- the PTT originator 116 thereafter starts a media session (e.g. an RTP media session, as could be implemented by those skilled in the art) to the port of the media server 76 , with media information previously received in the NOTIFY step 136 ( FIG. 7 ).
- FIG. 8 shows a general or generic example message template 160 for the SUBSCRIBE and NOTIFY requests.
- the message template includes a request 162 , request headers 164 and associated body, and a SDP body (if present) 166 .
- the request 162 may be either a SUBSCRIBE request 168 or a NOTIFY request 170 , depending on the particular application and implementation.
- the request headers 164 include headers relating to the PTT session information (the SUBSCRIBE or NOTIFY body is not shown here as it is context dependent). The configuration of the particular headers is dependent on the type of message being sent.
- the request headers 164 include Max-Forwards, To, From, Call-ID, CSeq, Contact, Event, Accept, Push-To-Talk-Group, Expires, Content-Type, and Content-Length.
- Event: header 172
- RFC 3265 permits the creation and use of “Event packages” which includes the creation of templates, event package responsibilities, parameters, and associated syntax and semantics for the headers 164 .
- a “push-to-talk” event package is provided, and indicated as “Event: push-to-talk” 172 (as shown).
- the SDP body 166 includes parameters relating to session description 176 , time description 178 , and media description 180 . These parameters are described in SIP. As can be appreciated, the SDP body 166 would not be present in some of the requests, such as in the RE-SUSCRIBE 142 and NOTIFY 144 messages ( FIG. 6 ). Further, the media description 180 would not be present in some of the requests, for example when media information is already provisioned in advance of a PTT session.
- the SDP body 166 as shown may include parameters indicated by an asterisk (*) which are considered optional as defined by SIP (not to be confused with parameters which are optional in the present PTT system 110 ).
- FIG. 9 shows an example message 207 for implementing the SUBSCRIBE step 132 ( FIG. 7 ) in detail.
- the message 207 indicates in the header “Event: push-to-talk” 203 .
- the message 207 also contains the “Push-To-Talk-Group” header 204 that indicates a specific PTT group-identifier (ID) which the client device 114 is subscribing to.
- the message 207 also includes in the body of the “Push-To-Talk-Group” header 204 a current “state” 206 of the client device.
- the state 206 may be “idle” while available to receive a PTT call, or “active” while wishes to initiate a PTT call.
- the state 206 is set to “idle”, as shown.
- the SUBSCRIBE message 100 also includes an “Expires:” header 208 , which includes in the body the requested expiry information of the particular subscription to the PTT group.
- the expiry information is stored by the server device 112 and generally indicates when the subscription to the PTT group is expired, and may be refreshed by subsequent SUBSCRIBE messages.
- the message 207 further includes a SDP body 210 , which contains media information 212 including port information of the client device 114 .
- the media information 212 is “SDP m-header port number 50000”, which is the port number that will be used by the client device 114 for receiving the incoming media when a PTT call is received by the client device 114 .
- port information may include Internet Protocol (IP) port, codec, etc.
- the media information 212 is sent from the server device 112 to the media server 76 for storage by the media server 76 to implement a future media session with the client device 114 .
- the media information 212 is stored by the server device 112 and passed on to the media server 76 when the media session starts.
- the server device 114 can authenticate this request if needed and either accept or reject the subscription. If the subscription is accepted the server device 112 will send 200-OK response 134 ( FIG. 7 ) to indicate the successful status of the subscription.
- the client device 114 can re-subscribe by sending another SUBSCRIBE message to the server device 112 if it wishes update the subscription, for example to modify or update SDP capabilities, expiry, state or ID of the Push-To-Talk-Group.
- FIG. 10 shows an example message 220 for implementing the NOTIFY step 136 ( FIG. 7 ) in detail.
- the NOTIFY message 220 includes the same Call-ID, an incremented CSeq (727 versus 726 as in the SUBSCRIBE message 207 ), and the same From and To headers.
- the NOTIFY message 220 includes some of the same headers 226 as the SUBSCRIBE message 207 ( FIG. 9 ).
- the NOTIFY message 220 also includes the same event package, including the header “Event package: push-to-talk” 228 and the header for “Push-To-Talk-Group” 230 as in the original SUBSCRIBE message 207 .
- the server device 112 provides to the client device 114 media information 222 of the media server 76 .
- the SDP body 224 includes the media information 222 , including port information of the media server 76 to the client device 114 .
- the client device 114 may store the media information 222 and use the media information 222 to implement a future PTT session when the client device 114 acts as a PTT-Originator 116 ( FIG. 6 ).
- the specific server device 112 and media server 76 negotiations would be understood by those skilled in the art.
- the server 112 may reduce the expiration value, and client device 114 must adhere to this new expiration value.
- the server 112 may reply with a SIP-Expires in the header of a 200 OK in response to the SUBSCRIBE command 132 .
- the server device 112 upon receiving of the SUBSCRIBE request (including the expiration value) from client device 114 will start a timer for the present subscription. Once the timer has expired the server device 112 will notify the client device 112 about the terminated/terminating state of the subscription by means of another NOTIFY request.
- the client device 112 accepts the provisioning NOTIFY message 220 request by responding with 200-OK 138 ( FIG. 7 ).
- the server device 112 can periodically send updated NOTIFY messages to the client device(s) 114 , which may for example include updated SDP information.
- the client device 114 may be configured to check for the SDP body in the NOTIFY messages.
- FIG. 11 shows an example SUBSCRIBE message 240 for implementing the RE-SUBSCRIBE step 142 ( FIG. 6 ) in detail, for initiating the PTT call or session to the PTT group.
- the SUBSCRIBE message 240 does not include an SDP body, as the SDP information (including media information) was previously provided in the previous SUBSCRIBE message 207 ( FIG. 9 ).
- the “state” 244 is set to “active”. This indicates that the particular client device 114 is initiating a PTT session to the PTT receivers 118 , 120 , 122 in the PTT group and is acting as the PTT originator 116 ( FIG. 6 ).
- using the SUBSCRIBE message 240 to initiate the PTT session would include additional information (such as the event package) when compared to a conventional INVITE message.
- the PTT-originator 116 can start the media session (such as an RTP-session) to the media information 222 , including the media port, that was previously provided in the NOTIFY message 220 ( FIG. 10 ).
- the server device 112 checks whether the current state of the PTT group is “idle” and that there is no “active” PTT session. The server device 112 also verifies whether the PTT originator 116 has permission to initiate the PTT session (the floor control functionality of the server device 112 would be understood by those skilled in the art), for example if the “expiry” for the particular subscription has expired. If the request by the PTT originator 116 is acceptable, the server device 112 will mark the PTT group as “active” and follow to the next NOTIFY step 144 . Otherwise the request will be rejected by the server device 112 sending to the PTT originator 116 one of the SIP-reject codes (e.g. 486 Busy Here).
- the PTT originator 116 one of the SIP-reject codes (e.g. 486 Busy Here).
- FIG. 12 shows an example NOTIFY message 260 for implementing the NOTIFY step 144 ( FIG. 6 ).
- the server device 112 will send the NOTIFY message 260 to all PTT receivers 118 , 120 , 122 of the PTT group ( FIG. 6 ).
- the NOTIFY message 260 indicates the “state” 262 is set to “active”.
- the NOTIFY message 260 is typically sent to those PTT receivers 118 , 120 , 122 which had previously subscribed to the PTT group (using the subscription procedure 130 , FIG. 7 ) and whose particular subscriptions have not expired, as determined by the server device 112 .
- the PTT-Receiver 118 , 120 , 122 shall be configured to not receive any RTP session and reject the NOTIFY message 260 request, for example by responding with 486 Busy Here (or 480 Temporary Unavailable) SIP-responses. Otherwise, the PTT-Receiver 118 , 120 , 122 will open the port (e.g., “listen”) which it has allocated for the media session in step 132 ( FIG. 7 ) for receiving the RTP-media. The PTT-Receiver 118 , 120 , 122 thereafter starts playing (e.g. outputting to a speaker, not shown) the RTP-media received on the port.
- the server device 112 will send 200 OK (or 202 Accepted) 148 response to the SUBSCRIBE message 240 request ( FIG. 11 )
- another client device 114 (such as one of the PTT receivers 118 , 120 , 122 ) would not be able to start another PTT session while the current state of the group is “active”.
- the PTT originator 116 sends a new RE-SUBSCRIBE request (using a SUBSCRIBE message similar to SUBSCRIBE message 240 , FIG. 11 ), in this case with the “state” indicated as “idle”.
- the server device 112 will terminate the sessions with the PTT receivers 118 , 120 , 122 by sending terminating NOTIFY requests (similar to the NOTIFY message 260 , FIG. 12 ) with the “state” indicated as “idle” to all PTT receivers 118 , 120 , 122 .
- the PTT session is considered as terminated and the server device 112 must reset states of the all group members to “idle” regardless of responses received for the terminating NOTIFY requests to the PTT receivers 118 , 120 , 122 .
- the client device 112 in order for a client device 112 to unsubscribe from the push-to-talk service (or a specific PTT group), the client device 112 must follow an un-subscription procedure, for example as described in RFC 3265, as would be understood by those skilled in the art.
- the client devices may be designated as dedicated PTT originators or dedicated PTT receivers.
- certain media information including media port information would not be included, as such information would not be used by the dedicated PTT originators or dedicated PTT receiver, thereby reducing the size of the required message content.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Multimedia (AREA)
- Telephonic Communication Services (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
- The present application is a continuation of U.S. patent application Ser. No. 12/392,177 filed Feb. 25, 2009, the contents of which are hereby incorporated by reference.
- The present application relates to push-to-talk systems and methods, and in particular to implementing push-to-talk using Session Initiation Protocol (SIP).
- Push-to-talk (PTT) generally refers to real-time direct one-to-one and one-to-group voice communication service, which may occur in the cellular, Public Switch Telephone Networks (PSTN) and Internet networks. PTT calls can be directed to both individuals and talk groups. In a PTT call, the call connection is initiated by an originator device while the receiver typically does not have to “answer” the call.
- PTT calls are one-way communications (half-duplex), which means that while one person speaks the others listen. In a PTT conversation, users typically no longer need to make several calls to coordinate with a group.
- PTT service users are typically engaged in some other activity than a telephone call, and they listen to the group traffic during their activity. A user is usually contacted by receiving a PTT call from a member of the PTT group and can respond to the PTT group with a push of a key.
- Session Initiation Protocol (SIP) is a protocol which is based on a request-response model. SIP leaves open the particular implementation of the desired functionality, and for example does not provide for specific implementation of PTT. As the interpretation remains open, some implementations of PTT using SIP may lead to inefficiencies.
- For example, in some conventional systems implementing PTT using SIP, media parameters are negotiated and communicated only once the PTT call is initiated by a user. This wastes resources and time between when the user actually initiates the PTT call and when the system connects the user to the receiving units. Call lags may occur each time a user initiates a PTT call. Further, such inefficiencies become magnified when the PTT group involves a large number of parties.
- Other difficulties with existing conventional systems will be apparent to those skilled in the art in view of the detailed description below.
- Reference will now be made, by way of example, to the accompanying drawings which show example embodiments, and in which:
-
FIG. 1 shows, in block diagram form, an example system for managing enterprise-related mobile calls, including an enterprise communications platform, to which example embodiments may be applied; -
FIG. 2 shows, in block diagram form, further details of an embodiment of the enterprise communications platform; -
FIG. 3 shows another embodiment of the enterprise communications platform; -
FIG. 4 shows yet another embodiment of the enterprise communications platform; -
FIG. 5 shows further details of the enterprise communications platform ofFIG. 3 ; -
FIG. 6 shows, in block diagram form, an example push-to-talk system and associated push-to-talk procedure implemented by the system ofFIG. 1 ; -
FIG. 7 shows, in block diagram form, an example push-to-talk subscription procedure between a client device and a server device implemented prior to the push-to-talk procedure in the push-to-talk system ofFIG. 6 ; -
FIG. 8 shows an example message to be used between devices within the push-to-talk procedures ofFIGS. 6 to 7 ; -
FIG. 9 shows an example message from the client device to the server device in the subscription procedure ofFIG. 8 ; -
FIG. 10 shows an example message from the sever device to the client device in the subscription procedure ofFIG. 8 ; -
FIG. 11 shows an example message from an originator client device initiating a push-to-talk session within the push-to-talk procedure ofFIG. 7 ; and -
FIG. 12 shows an example message from a server device to receiving client devices within the push-to-talk procedure ofFIG. 7 . - Similar reference numerals may have been used in different figures to denote similar components.
- In one aspect, there is provided a method of facilitating push-to-talk (PTT) communications between a server device and a client device using SIP-based messaging, the server device being in communication with a media server. The method includes: receiving in the server device from the client device a SUBSCRIBE message for subscription to a push-to-talk group, the SUBSCRIBE message including media information of the client device, storing in the server device the media information of the client device, and initiating, based on receipt in the server device of a second SUBSCRIBE message for initiating a push-to-talk session, a media session between the media server and the client device using the stored media information.
- In another aspect, there is provided a method of facilitating push-to-talk (PTT) communications between a server device and a client device using SIP-based messaging, the server device being in communication with a media server. The method includes: receiving in the server device from the client device a SUBSCRIBE message for subscription to a push-to-talk group, sending from the server device to the client device a NOTIFY message, the NOTIFY message including media information of the media server for storage by the client device, and initiating, based on receipt in the server device of a second SUBSCRIBE message for initiating a push-to-talk session, a media session between the media server and the client device using the stored media information.
- In yet another aspect, there is provided a server device for facilitating push-to-talk (PTT) communications using SIP-based messaging. The server device includes a memory, a controller for accessing the memory, a communications module in communications with the controller for communicating with a media server and a client device. The controller is configured to: receive from the client device a SUBSCRIBE message for subscription to a push-to-talk group, the SUBSCRIBE message including media information of the client device, store in memory the media information of the client device, send to the client device a NOTIFY message, the NOTIFY message including media information of the media server for storage by the client device, and initiate, based on receipt of a second SUBSCRIBE message for initiating a push-to-talk session, a media session between the media server and the client device using the stored media information.
- In yet another aspect, there is provided a system for facilitating push-to-talk (PTT) communications using SIP-based messaging. The system includes a media server, a server device in communication with the media server, and at least one PTT receiving client devices, each for sending to the server device a SUBSCRIBE message for subscription to a push-to-talk group, the SUBSCRIBE message including media information of each of the PTT receiving client devices. The system further includes a PTT originator client device for sending to the server device a SUBSCRIBE message for subscription to a push-to-talk group. The server device is configured to: store the media information of the PTT-receiving client devices, and send to the PTT originator client device a NOTIFY message, the NOTIFY message including media information of the media server. The PTT originator client device is configured to store the media information of the media server. The server device is further configured to, upon receipt in the server device from the PTT originator client device of a second SUBSCRIBE message for initiating a push-to-talk session, initiate a media session between the media server and the client devices using the stored media information.
- Other aspects will be apparent to those of ordinary skill in the art from a review of the following detailed description in conjunction with the drawings.
- The present application relates to the control and management of push-to-talk (PTT) communications. Although reference may be made to “calls” and “talk” 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. Reference to calls may for example include voice calls as well as media sessions which may for example include video and/or audio.
- Reference is now made to
FIG. 1 , which shows, in block diagram form, an example system, generally designated 10, for the control and management of communications. Thesystem 10 includes an enterprise orbusiness system 20, which in many embodiments includes 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 that theenterprise network 20 may include more than one network and may be located in multiple geographic areas in some embodiments. - The
enterprise network 20 may be connected, often through afirewall 22, to a wide area network (WAN) 30, such as the Internet. Theenterprise 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. - The
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. The connection with the PLMN 50 may be made via arelay 26, as known in the art. - The
enterprise network 20 may also provide a wireless local area network (WLAN) 32 a featuring wireless access points.Other WLANs 32 may exist outside theenterprise network 20. For example,WLAN 32 b may be connected toWAN 30. - The
system 10 may include a number of enterprise-associated mobile devices 11 (only one shown). Themobile devices 11 may include devices equipped for cellular communication through thePLMN 50, mobile devices equipped for Wi-Fi communications over one of theWLANs 32, or dual-mode devices capable of both cellular and WLAN communications.WLANs 32 may be configured in accordance with one of the IEEE 802.11 specifications. - 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, thePLMN 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 known manner, as the user moves. In some instances, the dual-modemobile devices 11 and/or theenterprise 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. - The
enterprise network 20 typically includes a number of networked servers, computers, and other devices. For example, theenterprise network 20 may connect one or more desktop or laptop computers 15 (one shown). The connection may be wired or wireless in some embodiments. Theenterprise network 20 may also connect to one or more digital telephone sets 17 (one shown). - The
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 within theenterprise network 20. Typical mail servers include the Microsoft Exchange Server™ and the IBM Lotus Domino™ server. Each user within the enterprise typically has at least one user account within theenterprise 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 on theenterprise 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'scomputer 15 connected to theenterprise 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 theWAN 30 using a VPN connection. Using the messaging application, the user may also compose and send messages addressed to others, within or outside theenterprise 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 from theenterprise network 20 to themobile device 11 via thePLMN 50. - The
enterprise network 20 also includes anenterprise server 12. Together with therelay 26, theenterprise server 12 functions to redirect or relay incoming e-mail messages addressed to a user's e-mail address within theenterprise network 20 to the user'smobile device 11 and to relay incoming e-mail messages composed and sent via themobile device 11 out to the intended recipients within theWAN 30 or elsewhere. Theenterprise server 12 andrelay 26 together 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 within theenterprise network 20 using the user's enterprise-related e-mail address, for example oncomputer 15. - As is typical in many enterprises, the
enterprise network 20 includes a Private Branch eXchange (although in various embodiments the PBX may be a standard PBX or an IP-PBX, 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 for the enterprise. ThePBX 16 is connected to thePSTN 40 via DID trunks or PRI trunks, for example. ThePBX 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, thePBX 16 may be connected to one or moreconventional analog telephones 19. ThePBX 16 is also connected to theenterprise network 20 and, through it, to telephone terminal devices, such as digital telephone sets 17, softphones operating oncomputers 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 from thePBX 16 to thePSTN 40 or incoming from thePSTN 40 to thePBX 16 are typically circuit-switched calls. Within the enterprise, e.g. between thePBX 16 and terminal devices, voice calls are often packet-switched calls, for example Voice-over-IP (VoIP) calls. - The
enterprise network 20 may further include a Service Management Platform (SMP) 18 for performing some aspects of messaging or session control, like call control and advanced call processing features. TheSMP 18 may, in some cases, also perform some media handling. Collectively theSMP 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, theSMP 18, is implemented on one or more servers having suitable communications interfaces for connecting to and communicating with thePBX 16 and/or DID/PRI trunks. Although theSMP 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, theSMP 18 may be implemented as a multi-layer platform. - The
enterprise communications platform 14 implements the switching to connect session legs and may provide the conversion between, for example, a circuit-switched call and a VoIP call, or to connect legs of other media sessions. 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 functions of the
enterprise communications platform 14 is to extend the features of enterprise telephony to themobile devices 11. For example, theenterprise communications platform 14 may allow themobile device 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. - Reference is now made to
FIGS. 2 to 4 , which show example embodiments of theenterprise communications system 14.FIG. 2 illustrates an embodiment intended for use in a circuit-switched TDM context. ThePBX 16 is coupled to theSMP 18 viaPRI connection 60 or other suitable digital trunk. In some embodiments, thePRI 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 thePBX 16 and theSMP 18. - In this embodiment, the
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 thePBX 16 are handled by theSMP 18 in this architecture. Incoming calls addressed to any extension or direct dial number within the enterprise, for example, are always first routed to theSMP 18. Thereafter, a call leg is established from theSMP 18 to the called party within the enterprise, and the two legs are bridged. Accordingly, theSMP 18 includes adigital trunk interface 62 and a digital signal processing (DSP)conferencing bridge 64. TheDSP conferencing bridge 64 performs the bridging of calls for implementation of various call features, such as conferencing, call transfer, etc. Thedigital 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. Thedigital trunk interface 62 may also be partly implemented using a processor module such as, for example, a Host Media Processing (HMP) processor. - The
SMP 18 may includevarious scripts 66 for managing call processing. Thescripts 66 are implemented as software modules, routines, functions, etc., stored in non-volatile memory and executed by the processor of theSMP 18. Thescripts 66 may implement call flow logic, business logic, user preferences, call service processes, and various feature applications. -
FIG. 3 shows another embodiment in which thePBX 16 performs the functions of terminating and/or bridging media streams, but call control functions are largely handled by theSMP 18. In this embodiment, theSMP 18 may be referred to as acall control server 18. This architecture may be referred to as “Third-Party Call Control”. - The
call control server 18 is coupled to thePBX 16, for example through the LAN, enabling packet-based communications and, more specifically, IP-based communications. In one embodiment, communications between thePBX 16 and thecall control server 18 are carried out in accordance with SIP. In other words, thecall control server 18 uses SIP-based communications to manage the set up, tear down, and control of media handled by thePBX 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). -
FIG. 4 shows yet another embodiment of theenterprise 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. TheSMP 18 includes acall processing server 74. Thecall processing server 74 includes the scripts or other programming constructs for performing call handling functions. TheSMP 18 also includes aSIP server 72 and amedia server 76. Theseparate SIP server 72 andmedia server 76 logically separate the call control from media handling. TheSIP server 72 interacts with thecall 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). - The
SIP server 72 interacts with themedia server 76 using SIP-based media handling commands. For example, theSIP 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, Aug. 7, 2008. Themedia server 76 may be configured to perform Host Media Processing (HMP). - Other architectures or configurations for the
enterprise communications system 14 will be appreciated by those ordinarily skilled in the art. - Reference is now made to
FIG. 5 , which shows another embodiment of theenterprise communications system 14 with a Third Party Call Control architecture. In this embodiment, theSMP 18 is a multi-layer platform that includes aprotocol layer 34, aservices layer 36 and an application layer 38. Theprotocol layer 34 includes a plurality of interface protocols configured for enabling operation of corresponding applications in the application layer 38. Theservices layer 36 includes a plurality of services that can be leveraged by the interface protocols to create richer applications. Finally, 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. - Specifically, the
protocol layer 34 preferably includes protocols which allow media to be controlled separate from data. For example, theprotocol layer 34 can include, among other things, a Session Initiation Protocol orSIP 80, aWeb Services protocol 82, an Application Programming Interface orAPI 84, a Computer Telephony Integration protocol or CTI 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 in theenterprise network 20, which will be further described below. - For the purposes of this disclosure,
SIP 80 will be utilized, although it is appreciated that thesystem 10 can operate using the above disclosed or additional protocols. As known by those of ordinary skill in the art, 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 of ordinary skill in the art, theSIP 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, the 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, the SIP-L interface is utilized when the endpoint is registered (i.e., when dialing to a specific extension). SIP is defined in J. Rosenberg et al., “RFC 3261—Session Initiation Protocol” (June 2002), the contents of which are herein incorporated by reference. Other procotols, extensions, and standards related to SIP may be implemented and referenced, as appropriate. For example, Session Description Protocol (SDP), as described herein, is defined in RFC 3264, and is herein incorporated by reference. - The specific operation of the
system 10 utilizingSIP 80 will be described in further detail below. - The
SMP 18 also includes a plurality of enablers, among other things, aVoIP enabler 90, a Fixed Mobile Convergence orFMC enabler 92, aconference services enabler 94, apresence enabler 96 and an Instant Messaging orIM enabler 98. Each of the enablers 90-98 are used by corresponding services in theservices layer 36 that combine one or more of the enablers. Each of the applications in the application layer 38 is then 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. - The application layer 38 may include a
conference services application 63 that, together with theconference services enabler 94, enables multiple communication devices (including desk telephones and personal computers) to participate in a conference call through use of acentralized conference server 55. As seen inFIG. 5 , theconference server 55 is provided in theenterprise network 20 and is in communication with theconference services enabler 94 preferably through theSIP 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 the CTI protocol 86. As will be described in further detail below, theconference 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
FIG. 6 , which shows, in block diagram form, an example PTT system, generally designated 110, for implementing a push-to-talk (PTT)procedure 140 in accordance with example embodiments. As shown, thePTT system 110 includes aPTT server device 112 in communication with a number ofPTT client devices 114, illustrated as one PTT originator 116 and a plurality of PTT receivers 118, 120, 122. Theclient devices 114 may collectively form a PTT group. The PTT receivers 118, 120, 122 may also sometimes be referred to as terminating devices. - The
server device 112 includes a controller and a memory for storage of, among other items, the media information ofclient devices 114 which subscribe to a push-to-talk group. Theserver device 112 includes a communications module or submodule for communicating with other devices. Theserver device 112 may for example be part of the call control server or SMP 18 (FIGS. 1-5 ). Theserver device 112 may further be part of the enterprise or business system 20 (FIG. 1 ). Theserver device 112 may include or be coupled to the media server 76 (FIG. 4 ), wherein theserver device 112 controls the media handling of themedia server 76. - Although the
client devices 114 are illustrated as handheld mobile communication devices (such as a smart phone, cellular phone, soft phone, dual-mode phone, etc.), the client devices may be any device configured with the functionality described herein, and may for example include computer devices, relays, proxies, gateways and any appropriate User Agents (as defined in SIP). - Reference is now to
FIG. 7 , which shows a subscription procedure between theserver device 112 and aclient device 114. Generally, thePTT system 110 provides a subscription-based communications wherein certain information, including media information, may be communicated between theclient devices 114 and theserver device 112 prior to initiation of the actual PTT session (also referred to as PTT call). Some communications within thePTT system 110 implement the SUBSCRIBE and NOTIFY requests, which are defined in A. B. Roach, “RFC 3265-Session Initiation Protocol (SIP)-Specific Event Notification” (June 2002), the contents of which are herein incorporated by reference. - In some conventional systems, a PTT session is implemented by using INVITE to set a pre-established (or early) session mode. However, such conventional systems using INVITE are limited to the basic request/response functionality provided by INVITE. It is recognized herein that the SIP SUBSCRIBE method and related commands may provide further and additional functionality and flexibility in implementation, as can be appreciated in view of the description below.
- Referring still to
FIG. 7 , a summary of thesubscription procedure 130 will now be described, which occurs prior to the PTT call. Atstep 132, theclient device 114 sends a SUBSCRIBE request to theserver device 112, including information regarding the push-to-talk group number of the device and the port number of the particularmobile device 114 that is used to receive subsequent message, as well as for receiving a future PTT session. Atstep 134, theserver device 112 provides a 200-OK message (accepting the subscription request). Theserver device 112 may also reject the subscription request (and/or the subscription request may fail), for example using the 4xx or 5xx family of responses. Atstep 136, theserver device 112 sends a NOTIFY request to theclient device 114, with media information including a port number of the media server 176 (FIG. 4 ) for future PTT sessions originating from theparticular client device 114. Atstep 138, theclient device 114 accepts the NOTIFY message by using 200-OK response. Generally, allclient devices 114 which are to form part of the PTT group would implement thesubscription procedure 130. Theserver device 112 is therefore informed of the port information of each subscribingclient device 114, while each client device is informed of the port information of themedia server 176. - Referring now to
FIG. 6 , a summary of thePTT procedure 140 will now be described. Generally, thePTT procedure 140 is used to establish a PTT call or session from the PTT originator 116 to the PTT receivers 118, 120, 122. ThePTT procedure 140 typically occurs after the subscription procedure 130 (FIG. 7 ), with the media parameters already communicated. Atstep 142, the PTT originator 116 sends another SUBSCRIBE request (indicated as “RE-SUSCRIBE” for convenience) to theserver device 112. Atstep 144, theserver device 112 sends NOTIFY requests to the PTT receivers 118, 120, 122. As will be described in detail below, the NOTIFY request includes an indication of a new “active” state. Atstep 146, the PTT receivers 118, 120, 122 respond with a 200-OK message if a PTT call is acceptable to be received. A busy message such as 486-Busy may be sent as a response if the particular PTT receiver 118, 120, 122 is busy or not accepting the PTT call. Each PTT receiver 118, 120, 122 which indicated 200-OK further opens its allocated port for receiving media from the media server 76 (FIG. 4 ), for example Real-Time Transport Protocol (RTP) media, as could be implemented by those skilled in the art. Atstep 148, theserver device 112 sends a 200-OK for the re-subscription message if at least one of the PTT-receivers 118, 120, 122 is not busy. Themedia server 76 may thereafter open its media port for receiving or listening to media from the PTT originator 116. The PTT originator 116 thereafter starts a media session (e.g. an RTP media session, as could be implemented by those skilled in the art) to the port of themedia server 76, with media information previously received in the NOTIFY step 136 (FIG. 7 ). - Detailed example implementations of the
subscription procedure 130 andPTT procedure 140 will now be described, with reference toFIG. 8 , which shows a general or genericexample message template 160 for the SUBSCRIBE and NOTIFY requests. As shown, the message template includes arequest 162,request headers 164 and associated body, and a SDP body (if present) 166. As shown, therequest 162 may be either aSUBSCRIBE request 168 or a NOTIFYrequest 170, depending on the particular application and implementation. - The
request headers 164 include headers relating to the PTT session information (the SUBSCRIBE or NOTIFY body is not shown here as it is context dependent). The configuration of the particular headers is dependent on the type of message being sent. Therequest headers 164 include Max-Forwards, To, From, Call-ID, CSeq, Contact, Event, Accept, Push-To-Talk-Group, Expires, Content-Type, and Content-Length. Regarding the “Event:”header 172, RFC 3265 permits the creation and use of “Event packages” which includes the creation of templates, event package responsibilities, parameters, and associated syntax and semantics for theheaders 164. Thus, in this particular example a “push-to-talk” event package is provided, and indicated as “Event: push-to-talk” 172 (as shown). Theheaders 164 may further contain a “Push-To-Talk-Group:” 174 and associated “state=”, which are created in the particular Event package. Note that the INVITE does not typically contain or provide for such Event packages. - The
SDP body 166 includes parameters relating tosession description 176,time description 178, andmedia description 180. These parameters are described in SIP. As can be appreciated, theSDP body 166 would not be present in some of the requests, such as in theRE-SUSCRIBE 142 and NOTIFY 144 messages (FIG. 6 ). Further, themedia description 180 would not be present in some of the requests, for example when media information is already provisioned in advance of a PTT session. TheSDP body 166 as shown may include parameters indicated by an asterisk (*) which are considered optional as defined by SIP (not to be confused with parameters which are optional in the present PTT system 110). - The subscription procedure 130 (
FIG. 7 ) and PTT procedure 140 (FIG. 6 ) will now be described in greater detail. Reference is now made toFIG. 9 , which shows anexample message 207 for implementing the SUBSCRIBE step 132 (FIG. 7 ) in detail. As shown, themessage 207 indicates in the header “Event: push-to-talk” 203. Themessage 207 also contains the “Push-To-Talk-Group”header 204 that indicates a specific PTT group-identifier (ID) which theclient device 114 is subscribing to. Themessage 207 also includes in the body of the “Push-To-Talk-Group” header 204 a current “state” 206 of the client device. For example, thestate 206 may be “idle” while available to receive a PTT call, or “active” while wishes to initiate a PTT call. In thepresent message 207 for subscribing to a PTT group, thestate 206 is set to “idle”, as shown. The SUBSCRIBE message 100 also includes an “Expires:”header 208, which includes in the body the requested expiry information of the particular subscription to the PTT group. The expiry information is stored by theserver device 112 and generally indicates when the subscription to the PTT group is expired, and may be refreshed by subsequent SUBSCRIBE messages. - The
message 207 further includes aSDP body 210, which containsmedia information 212 including port information of theclient device 114. In the example shown, themedia information 212 is “SDP m-header port number 50000”, which is the port number that will be used by theclient device 114 for receiving the incoming media when a PTT call is received by theclient device 114. For example, port information may include Internet Protocol (IP) port, codec, etc. In some example embodiments, themedia information 212 is sent from theserver device 112 to themedia server 76 for storage by themedia server 76 to implement a future media session with theclient device 114. In other example embodiments, themedia information 212 is stored by theserver device 112 and passed on to themedia server 76 when the media session starts. - The
server device 114 can authenticate this request if needed and either accept or reject the subscription. If the subscription is accepted theserver device 112 will send 200-OK response 134 (FIG. 7 ) to indicate the successful status of the subscription. - The
client device 114 can re-subscribe by sending another SUBSCRIBE message to theserver device 112 if it wishes update the subscription, for example to modify or update SDP capabilities, expiry, state or ID of the Push-To-Talk-Group. - Reference is now made to
FIG. 10 , which shows anexample message 220 for implementing the NOTIFY step 136 (FIG. 7 ) in detail. As shown, the NOTIFYmessage 220 includes the same Call-ID, an incremented CSeq (727 versus 726 as in the SUBSCRIBE message 207), and the same From and To headers. Thus, the NOTIFYmessage 220 includes some of thesame headers 226 as the SUBSCRIBE message 207 (FIG. 9 ). As shown, the NOTIFYmessage 220 also includes the same event package, including the header “Event package: push-to-talk” 228 and the header for “Push-To-Talk-Group” 230 as in theoriginal SUBSCRIBE message 207. Once theserver device 114 has accepted the subscription of theclient device 114 to the particular PTT group, theserver device 112 provides to theclient device 114media information 222 of themedia server 76. As shown, theSDP body 224 includes themedia information 222, including port information of themedia server 76 to theclient device 114. Theclient device 114 may store themedia information 222 and use themedia information 222 to implement a future PTT session when theclient device 114 acts as a PTT-Originator 116 (FIG. 6 ). Thespecific server device 112 andmedia server 76 negotiations would be understood by those skilled in the art. - Referring still to
FIG. 10 , with regards to the Expires header 232 (shown as “Expires: 2900”), theserver 112 may reduce the expiration value, andclient device 114 must adhere to this new expiration value. In other example embodiments, theserver 112 may reply with a SIP-Expires in the header of a 200 OK in response to theSUBSCRIBE command 132. - In some example embodiments, the
server device 112 upon receiving of the SUBSCRIBE request (including the expiration value) fromclient device 114 will start a timer for the present subscription. Once the timer has expired theserver device 112 will notify theclient device 112 about the terminated/terminating state of the subscription by means of another NOTIFY request. - The
client device 112 accepts the provisioning NOTIFYmessage 220 request by responding with 200-OK 138 (FIG. 7 ). - In some embodiments, the
server device 112 can periodically send updated NOTIFY messages to the client device(s) 114, which may for example include updated SDP information. Thus, theclient device 114 may be configured to check for the SDP body in the NOTIFY messages. - Reference is now made to
FIG. 11 , which shows anexample SUBSCRIBE message 240 for implementing the RE-SUBSCRIBE step 142 (FIG. 6 ) in detail, for initiating the PTT call or session to the PTT group. As shown, theSUBSCRIBE message 240 does not include an SDP body, as the SDP information (including media information) was previously provided in the previous SUBSCRIBE message 207 (FIG. 9 ). As shown, in the “Push-To-Talk Group”header 242, the “state” 244 is set to “active”. This indicates that theparticular client device 114 is initiating a PTT session to the PTT receivers 118, 120, 122 in the PTT group and is acting as the PTT originator 116 (FIG. 6 ). As can be appreciated, using theSUBSCRIBE message 240 to initiate the PTT session would include additional information (such as the event package) when compared to a conventional INVITE message. - After the
SUBSCRIBE message 240 has been sent to theserver device 112, the PTT-originator 116 can start the media session (such as an RTP-session) to themedia information 222, including the media port, that was previously provided in the NOTIFY message 220 (FIG. 10 ). - The
server device 112 checks whether the current state of the PTT group is “idle” and that there is no “active” PTT session. Theserver device 112 also verifies whether the PTT originator 116 has permission to initiate the PTT session (the floor control functionality of theserver device 112 would be understood by those skilled in the art), for example if the “expiry” for the particular subscription has expired. If the request by the PTT originator 116 is acceptable, theserver device 112 will mark the PTT group as “active” and follow to the next NOTIFYstep 144. Otherwise the request will be rejected by theserver device 112 sending to the PTT originator 116 one of the SIP-reject codes (e.g. 486 Busy Here). - Reference is now made to
FIG. 12 , which shows an example NOTIFYmessage 260 for implementing the NOTIFY step 144 (FIG. 6 ). Theserver device 112 will send the NOTIFYmessage 260 to all PTT receivers 118, 120, 122 of the PTT group (FIG. 6 ). The NOTIFYmessage 260, as shown, indicates the “state” 262 is set to “active”. The NOTIFYmessage 260 is typically sent to those PTT receivers 118, 120, 122 which had previously subscribed to the PTT group (using thesubscription procedure 130,FIG. 7 ) and whose particular subscriptions have not expired, as determined by theserver device 112. - If a PTT-Receiver 118, 120, 122 is not willing to accept the PTT call, the PTT-Receiver shall be configured to not receive any RTP session and reject the NOTIFY
message 260 request, for example by responding with 486 Busy Here (or 480 Temporary Unavailable) SIP-responses. Otherwise, the PTT-Receiver 118, 120, 122 will open the port (e.g., “listen”) which it has allocated for the media session in step 132 (FIG. 7 ) for receiving the RTP-media. The PTT-Receiver 118, 120, 122 thereafter starts playing (e.g. outputting to a speaker, not shown) the RTP-media received on the port. - Once any one of the PTT receivers 118, 120, 122 sends a 200 OK response to the NOTIFY
message 260 request, theserver device 112 will send 200 OK (or 202 Accepted) 148 response to theSUBSCRIBE message 240 request (FIG. 11 ) - It can be appreciated that another client device 114 (such as one of the PTT receivers 118, 120, 122) would not be able to start another PTT session while the current state of the group is “active”.
- Referring to
FIG. 6 , in order to terminate a PTT session, the PTT originator 116 sends a new RE-SUBSCRIBE request (using a SUBSCRIBE message similar to SUBSCRIBEmessage 240,FIG. 11 ), in this case with the “state” indicated as “idle”. Theserver device 112 will terminate the sessions with the PTT receivers 118, 120, 122 by sending terminating NOTIFY requests (similar to the NOTIFYmessage 260,FIG. 12 ) with the “state” indicated as “idle” to all PTT receivers 118, 120, 122. Once the request to terminate the session by the PTT originator 116 is received, the PTT session is considered as terminated and theserver device 112 must reset states of the all group members to “idle” regardless of responses received for the terminating NOTIFY requests to the PTT receivers 118, 120, 122. - Referring to
FIG. 6 , in order for aclient device 112 to unsubscribe from the push-to-talk service (or a specific PTT group), theclient device 112 must follow an un-subscription procedure, for example as described in RFC 3265, as would be understood by those skilled in the art. - In some example embodiments, the client devices may be designated as dedicated PTT originators or dedicated PTT receivers. Thus, in some of the provisioning message requests, certain media information including media port information would not be included, as such information would not be used by the dedicated PTT originators or dedicated PTT receiver, thereby reducing the size of the required message content.
- Certain adaptations and modifications of the described embodiments can be made. Therefore, the above discussed embodiments are considered to be illustrative and not restrictive.
Claims (19)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/725,031 US20130115996A1 (en) | 2009-02-25 | 2012-12-21 | Systems and methods for facilitating push-to-talk (ptt) communications using sip-based messaging |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/392,177 US8374643B2 (en) | 2009-02-25 | 2009-02-25 | Systems and methods for facilitating push-to-talk (PTT) communications using SIP-based messaging |
US13/725,031 US20130115996A1 (en) | 2009-02-25 | 2012-12-21 | Systems and methods for facilitating push-to-talk (ptt) communications using sip-based messaging |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/392,177 Continuation US8374643B2 (en) | 2009-02-25 | 2009-02-25 | Systems and methods for facilitating push-to-talk (PTT) communications using SIP-based messaging |
Publications (1)
Publication Number | Publication Date |
---|---|
US20130115996A1 true US20130115996A1 (en) | 2013-05-09 |
Family
ID=42631435
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/392,177 Expired - Fee Related US8374643B2 (en) | 2009-02-25 | 2009-02-25 | Systems and methods for facilitating push-to-talk (PTT) communications using SIP-based messaging |
US13/725,031 Abandoned US20130115996A1 (en) | 2009-02-25 | 2012-12-21 | Systems and methods for facilitating push-to-talk (ptt) communications using sip-based messaging |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/392,177 Expired - Fee Related US8374643B2 (en) | 2009-02-25 | 2009-02-25 | Systems and methods for facilitating push-to-talk (PTT) communications using SIP-based messaging |
Country Status (1)
Country | Link |
---|---|
US (2) | US8374643B2 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20130022018A1 (en) * | 2010-04-05 | 2013-01-24 | Lg Electronics Inc. | Method and apparatus for transmitting a broadcasting service in a system that supports machine to machine communications |
Families Citing this family (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8374643B2 (en) * | 2009-02-25 | 2013-02-12 | Research In Motion Limited | Systems and methods for facilitating push-to-talk (PTT) communications using SIP-based messaging |
US8290525B2 (en) | 2010-01-15 | 2012-10-16 | Comcast Cable Communications, Llc | Text alternative to established voice call session |
US20110188411A1 (en) * | 2010-02-02 | 2011-08-04 | Stefano Faccin | System and method for packetized emergency messages |
US20110188416A1 (en) * | 2010-02-02 | 2011-08-04 | Stefano Faccin | System and method for packetized emergency messages |
US20110189971A1 (en) * | 2010-02-02 | 2011-08-04 | Stefano Faccin | System and method for packetized emergency messages |
MY168733A (en) | 2010-11-02 | 2018-11-29 | Ericsson Telefon Ab L M | Methods and devices for media description delivery |
US9602557B2 (en) | 2012-10-15 | 2017-03-21 | Wowza Media Systems, LLC | Systems and methods of communication using a message header that includes header flags |
US9769221B2 (en) * | 2014-01-17 | 2017-09-19 | Mediatek Inc. | Method to support service continuity for multiple sessions |
WO2016004600A1 (en) * | 2014-07-10 | 2016-01-14 | Motorola Solutions, Inc. | Methods and systems for simultaneous talking in a talkgroup using a dynamic channel chain |
CN106899590A (en) * | 2017-02-24 | 2017-06-27 | 上海微喂网络科技有限公司 | The intelligence for leading to function is exhaled to wait for public network intercommunication method with simulation intercommunication one |
US11882164B1 (en) * | 2020-08-13 | 2024-01-23 | Cisco Technology, Inc. | Minimizing work disruption when integrating IP communication systems with push-to-talk systems |
CN112751748B (en) * | 2020-12-28 | 2023-04-18 | 百果园技术(新加坡)有限公司 | Session message management method, device, server and readable storage medium |
Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6477150B1 (en) * | 2000-03-03 | 2002-11-05 | Qualcomm, Inc. | System and method for providing group communication services in an existing communication system |
US20040224710A1 (en) * | 2003-05-07 | 2004-11-11 | Petri Koskelainen | System and method for providing support services in push to talk communication platforms |
US20060223563A1 (en) * | 2005-04-01 | 2006-10-05 | Samsung Electronics Co., Ltd. | Method and system for transmitting information of respondent participating in push-to-talk over cellular network session |
US20060270430A1 (en) * | 2005-05-27 | 2006-11-30 | Microsoft Corporation | Push-to-talk event notification |
US7280502B2 (en) * | 2004-04-13 | 2007-10-09 | Research In Motion Limited | Method for a session initiation protocol push-to-talk terminal to indicate answer operating mode to an internet protocol push-to-talk network server |
US20080274762A1 (en) * | 2005-07-15 | 2008-11-06 | Huawei Technologies Co., Ltd. | Method and apparatus for obtaining group information by an invited user during a session |
US7756541B2 (en) * | 2005-11-04 | 2010-07-13 | Industrial Technology Research Institute | PoC system and method for distributing media data in PoC |
US8374643B2 (en) * | 2009-02-25 | 2013-02-12 | Research In Motion Limited | Systems and methods for facilitating push-to-talk (PTT) communications using SIP-based messaging |
US9210202B2 (en) * | 2007-06-20 | 2015-12-08 | Qualcomm Incorporated | System and method for sharing media in a group communication among wireless communication devices |
Family Cites Families (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7668149B2 (en) | 2004-02-27 | 2010-02-23 | Research In Motion Limited | Methods and apparatus for facilitating concurrent push-to-talk over cellular (PoC) group communication sessions |
DE102004010925B9 (en) | 2004-03-05 | 2006-06-22 | Infineon Technologies Ag | Method and communication arrangement for establishing a push-to-talk communication connection and push-to-talk client unit |
WO2005107095A1 (en) | 2004-04-21 | 2005-11-10 | Alcatel Wireless, Inc. | Providing push-to-talk communications in a telecommunications network |
US20060178138A1 (en) | 2005-02-09 | 2006-08-10 | Dan Ostroff | Access gateway, softswitch and telephone for push-to-talk telephony |
KR20060093976A (en) | 2005-02-23 | 2006-08-28 | 삼성전자주식회사 | Method and system for giving speech in push-to-talk over cellular network |
US20060235981A1 (en) | 2005-04-19 | 2006-10-19 | Nokia Corporation | Providing a second service to a group of users using a first service |
US20070004438A1 (en) | 2005-07-01 | 2007-01-04 | Alec Brusilovsky | Method and apparatus enabling PTT (push-to-talk) communications between legacy PSTN, cellular and wireless 3G terminals |
US9225757B2 (en) | 2006-03-06 | 2015-12-29 | Intel Mobile Communications GmbH | Tree-based broadcasting service over push-to-talk mobile IP network |
CA2672291A1 (en) | 2006-12-14 | 2008-06-19 | Telefonaktiebolaget L M Ericsson (Publ) | A method and arrangement for handling a subscription for client data |
-
2009
- 2009-02-25 US US12/392,177 patent/US8374643B2/en not_active Expired - Fee Related
-
2012
- 2012-12-21 US US13/725,031 patent/US20130115996A1/en not_active Abandoned
Patent Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6477150B1 (en) * | 2000-03-03 | 2002-11-05 | Qualcomm, Inc. | System and method for providing group communication services in an existing communication system |
US20040224710A1 (en) * | 2003-05-07 | 2004-11-11 | Petri Koskelainen | System and method for providing support services in push to talk communication platforms |
US7280502B2 (en) * | 2004-04-13 | 2007-10-09 | Research In Motion Limited | Method for a session initiation protocol push-to-talk terminal to indicate answer operating mode to an internet protocol push-to-talk network server |
US20060223563A1 (en) * | 2005-04-01 | 2006-10-05 | Samsung Electronics Co., Ltd. | Method and system for transmitting information of respondent participating in push-to-talk over cellular network session |
US20060270430A1 (en) * | 2005-05-27 | 2006-11-30 | Microsoft Corporation | Push-to-talk event notification |
US20080274762A1 (en) * | 2005-07-15 | 2008-11-06 | Huawei Technologies Co., Ltd. | Method and apparatus for obtaining group information by an invited user during a session |
US7756541B2 (en) * | 2005-11-04 | 2010-07-13 | Industrial Technology Research Institute | PoC system and method for distributing media data in PoC |
US9210202B2 (en) * | 2007-06-20 | 2015-12-08 | Qualcomm Incorporated | System and method for sharing media in a group communication among wireless communication devices |
US8374643B2 (en) * | 2009-02-25 | 2013-02-12 | Research In Motion Limited | Systems and methods for facilitating push-to-talk (PTT) communications using SIP-based messaging |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20130022018A1 (en) * | 2010-04-05 | 2013-01-24 | Lg Electronics Inc. | Method and apparatus for transmitting a broadcasting service in a system that supports machine to machine communications |
US8942149B2 (en) * | 2010-04-05 | 2015-01-27 | Lg Electronics Inc. | Method and apparatus for transmitting a broadcasting service in a system that supports machine to machine communications |
Also Published As
Publication number | Publication date |
---|---|
US20100216500A1 (en) | 2010-08-26 |
US8374643B2 (en) | 2013-02-12 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8374643B2 (en) | Systems and methods for facilitating push-to-talk (PTT) communications using SIP-based messaging | |
US9055127B2 (en) | Method for designating of hosting control for a conference call | |
US8594639B2 (en) | Method and system to automatically park a voice call for data transfer | |
US8626849B2 (en) | Apparatus and method for resolving a race condition between two session initiation protocol (SIP) end points | |
US8559960B2 (en) | PBX mobility system with multiple call legs | |
US20130129065A1 (en) | Call access management | |
US8976950B2 (en) | Expedited media interconnection in third party call control | |
US8570899B2 (en) | Provisioning for enterprise services | |
CA2694447C (en) | Pbx mobility system with multiple call legs | |
EP2224663B1 (en) | Systems and methods for facilitating push-to-talk (PTT) communications using sip-based messaging | |
EP2339812B1 (en) | Method for designating of hosting control for a conference call | |
US20120039454A1 (en) | Call management | |
EP2387219A1 (en) | Registering the private branch exchange being used by an enterprise-associated mobile device | |
EP2348698B1 (en) | Expedited media interconnection in third party call control | |
CA2693693C (en) | Method and system to automatically park a voice call for data transfer | |
EP2418834A1 (en) | Call Management |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: RESEARCH IN MOTION LIMITED, CANADA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:SHATSKY, ALEXANDER;REEL/FRAME:029521/0293 Effective date: 20090223 |
|
AS | Assignment |
Owner name: BLACKBERRY LIMITED, ONTARIO Free format text: CHANGE OF NAME;ASSIGNOR:RESEARCH IN MOTION LIMITED;REEL/FRAME:037893/0239 Effective date: 20130709 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |
|
AS | Assignment |
Owner name: MALIKIE INNOVATIONS LIMITED, IRELAND Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BLACKBERRY LIMITED;REEL/FRAME:064104/0103 Effective date: 20230511 |