|Publication number||US7107017 B2|
|Application number||US 10/431,626|
|Publication date||Sep 12, 2006|
|Filing date||May 7, 2003|
|Priority date||May 7, 2003|
|Also published as||EP1620957A2, US20040224710, WO2004100419A2, WO2004100419A3|
|Publication number||10431626, 431626, US 7107017 B2, US 7107017B2, US-B2-7107017, US7107017 B2, US7107017B2|
|Inventors||Petri Koskelainen, Mikko Vainikainen|
|Original Assignee||Nokia Corporation|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (6), Non-Patent Citations (2), Referenced by (53), Classifications (24), Legal Events (4)|
|External Links: USPTO, USPTO Assignment, Espacenet|
This invention relates in general to communications, and more particularly to a system, apparatus, and method for providing auxiliary services in Push to Talk communication environments.
Advances in communication infrastructures and protocols have turned standard computing devices into valuable communication tools. Computers communicate with each other, and with other electronic devices, over networks ranging from Local Area Networks (LANs) to wide reaching Global Area Networks (GANs) such as the Internet. Other electronic devices have experienced similar transformations, such as mobile phones, Personal Digital Assistants (PDAs), and the like. Today, these wireless devices are being used for a variety of different types of communication. For example, current and anticipated mobile phone technologies have transformed these wireless devices into powerful communication tools capable of communicating voice, data, images, video, and other multimedia content. Mobile phones, at one time solely a mobile voice communication tool, now often include network communication capabilities such as e-mail, Internet access, etc. With the integration of wireless and landline network infrastructures, a multitude of new services are arising, and various information types can be conveniently communicated between wireless and/or landline terminals.
One such new service is the “Push to Talk” (PTT) service, also commonly referred to as the “Push to Talk over Cellular” (PoC). The PTT service provides a direct one-to-one and one-to-many voice communication service in mobile networks. It is considered to have an “always on” connection, where half-duplex communication can be initiated to both individuals and talk groups simply with the push of a button on the PTT client device. To the user, operation is similar to the traditional “walkie talkie,” but clearly more powerful in the ability to designate and select individual recipients and group recipients of the communication. And, by using cellular access and radio resources, PTT communications has a virtually global reach.
Call connection with PTT service is almost instantaneous. One-way communications are initiated by a user, while the designated recipient(s) listens at the other end. PTT calls are generally connected without the recipient(s) answering, and they are typically received through the built-in loudspeaker on the receiving device. PTT service uses cellular access and radio resources more efficiently than circuit-switched cellular services, as network resources are reserved only one-way for the duration of the talk “spurts” instead of two-way for an entire call session.
Notwithstanding all of the benefits of a PTT system, there are limitations. For example, its real-time, half-duplex speech communication inherently has limitations, such as the inability to carry out simultaneous two-way communication. Due largely to such inherent limitations, PTT systems are generally not expected to provide other services beyond its intended half-duplex voice communication.
However, PTT is a platform that may support other functions beyond just the spontaneous voice communication that it is intended for. For example, a PTT system may be a suitable platform for games or other such services. Unfortunately, current PTT platforms do not provide a way to support such services, as games or other services may require various supporting features that are not currently available in PTT systems.
Accordingly, there is a need in the communications industry for a manner of utilizing PTT systems for services beyond their traditional real-time speech communication, and to provide a manner of supporting such services by providing the various features required to make these services practical in PTT systems.
To overcome limitations in the prior art described above, and to overcome other limitations that will become apparent upon reading and understanding the present specification, the present invention discloses a system, apparatus and method for introducing services in Push to Talk (PTT) network environments.
In accordance with one embodiment of the invention, a method is provided for introducing services into a Push to Talk (PTT) environment. The method includes generating and transmitting a request for services via a requesting PTT client. The request is received at a PTT server, which forwards the request to a PTT application server recognized by the PTT server as another PTT client. The requested service is performed at the PTT application server, and a result is generated in response thereto. The result is transmitted from the PTT application server to the requesting PTT client by way of the PTT server.
In accordance with another embodiment of the invention, a method is provided for providing services in a Push to Talk (PTT) system where PTT clients can communicate with one another by way of a PTT server. The method includes receiving, at the PTT server, an over-the-air service request from a requesting PTT client. In this embodiment, the service request includes at least one service command to identify a corresponding service feature. The service request is forwarded to a PTT application server that communicates with the PTT server in the same manner that it would communicate with a PTT client. The service command is executed at the PTT application server to perform the corresponding service feature requested by the requesting PTT client.
In accordance with another embodiment of the invention, a server is provided for providing services to push to talk (PTT) clients via an intermediary PTT server. The server includes a processing system, and a database to store information targeted by service requests issued by the PTT clients. A PTT client module, operable via the processing system, communicates with the PTT server in a client-server relationship. At least one service module operable via the processing system is provided to process the service requests identifying the service module as a targeted service.
In accordance with yet another embodiment of the invention, a system is provided for providing services over a network via a Push to Talk over Cellular (PoC) platform. The system includes at least one push to talk (PTT) client device having PTT capabilities. The PTT client device is configured to generate and transmit at least one service request over-the-air (OTA). A PTT server is coupled OTA to the PTT client device to receive and redirect the service request to an addressed PTT client on the network. A PTT application server serving as the addressed PTT client is coupled to the network to receive the redirected service request, where the PTT application server includes a processing system to process the service request.
These and various other advantages and features of novelty which characterize the invention are pointed out with particularity in the claims annexed hereto and form a part hereof. However, for a better understanding of the invention, its advantages, and the objects obtained by its use, reference should be made to the drawings which form a further part hereof, and to accompanying descriptive matter, in which there are illustrated and described specific examples of a system, apparatus, and method in accordance with the invention.
The invention is described in connection with the embodiments illustrated in the following diagrams.
In the following description of the exemplary embodiment, reference is made to the accompanying drawings which form a part hereof, and in which is shown by way of illustration various embodiments in which the invention may be practiced. It is to be understood that other embodiments may be utilized, as structural and operational changes may be made without departing from the scope of the present invention.
Generally, the present invention provides a manner of introducing application-supporting services in Push to Talk (PTT) network environments. As used herein, a Push to Talk (PTT) system generally refers to any non-full-duplex (e.g., half duplex) voice communication available over an otherwise two-way radio/cellular network. PTT can serve as a very good platform for many applications, such as games. Such applications, however, may require support features/services, such as voicemail, text message retrieval, statistical information retrieval, etc. The present invention provides a manner of making such services available to the PTT users via the network. In one embodiment, service requests are initiated by PTT clients to the PTT application server by way of the PTT server that manages the PTT communications. The PTT server, substantially treating the PTT application server as a PTT client, forwards the service request to the PTT application server. A command(s) embedded in (or otherwise provided with) the service request is processed by the PTT application server to perform the service requested by the PTT client. The result is provided back to the PTT server, again where the PTT application server appears to the PTT server as a PTT client, and the result is ultimately returned to the PTT client via the PTT server.
The support services may also initially collect information that is later supplied to a requesting PTT client. For example, where the support service provided is voicemail, the PTT application server can store a voicemail from a first PTT client for subsequent retrieval by another PTT client. Application data may also be accumulated and processed to provide, for example, statistical information. An example would be the “high scores” in a game application, where the PTT application maintains the highest score for a particular game. Other support services may be real-time services, such as retrieving the current time, calculating values (e.g., calculating the average score of certain participants of a game), etc. The ability to provide such support features facilitates the practical implementation of applications on the PTT platform.
The block diagram of
The PTT system 100 may serve as a great platform for new applications/services, such as games, which may require many new features not currently available in PTT systems. In accordance with the present invention, a PTT application server 116 is introduced into the network. The PTT application server 116 essentially operates as an “advanced” PTT client. In other words, the PTT application server 116 acts like a normal client vis-à-vis the PTT server 110. In this manner, service requests issued by the PTT clients 102, 104, 106, 112 can be handled by the PTT server 110 just as if the service request had been voice packets sent in connection with standard PTT talk spurts. By implementing a PTT application server 116 as an advanced PTT client, the PTT server 110 itself does not require modification upon introduction of services such as voicemail into the PTT system 100. PTT clients do not need to be updated either, since the application logic is at the application level, so new downloadable applications (e.g., Java applications) can use new features quickly using the current PTT infrastructure. On the other hand, the PTT application server 116 can be easily upgraded and new features can be added.
In one embodiment, the PTT application server 116 is implemented external to the PTT server 110—just as a typical PTT client would be. In another embodiment, the PTT application server 116 is a distinct network entity from the PTT server 110, yet is co-located with the PTT server 110 as illustrated by block 118. More particularly, the PTT application server 116 may be physically located integral or proximate to the PTT server 110. However, because the PTT server 110 and PTT application server 116 are configured in a client-server relationship such that the PTT application server 116 acts like a normal client towards the PTT server 110, the PTT application server 116 may be physically located at any point in the network. In yet another embodiment, the PTT application server 116 may be located at the PTT server 110 as shown by block 118, where a direct interface couples the PTT server 110 and PTT application server 116.
Upon receiving the service request, the PTT server 206 delivers the service request to the PTT application server 202 as illustrated by delivery path B. The particular application at the PTT application server 202 executes the command provided via the service request. For example, where the command is get-game-status, the PTT application server 202 can retrieve stored information relating to the game from a database 208 or other memory/storage. Upon retrieving the requested information, the PTT application server 202, acting as a client with respect to the PTT server 206, returns a message with the result to the PTT server 206 as shown by return path C. Upon receiving the message, the PTT server 206 forwards the message back to the mobile PTT client 200 as shown by return path D1. In some cases, the return message may be directed to multiple or all of the PTT clients associated with the PTT group, as depicted by the additional return path(s) DN to the PTT client 210.
It should be noted that the PTT application server 202 can provide any one or more of a number of different types of services. As another example, consider a voicemail service, and assume that PTT client 200 is involved in a long-lasting game requiring such voicemail capability. The PTT application server 202 can provide such a service to the participants of the game. A voicemail initiated by PTT client 200 can be stored via the PTT application server 202, and retrieved by any of the other users in the talk group (e.g., PTT clients 210, etc.). To retrieve a voicemail, PTT client 210 can use various message protocols to deliver the command to the PTT server 206. For example, the command may be delivered via a Hypertext Transfer Protocol (HTTP), Simple Object Access Protocol (SOAP) message. In such an example, the PTT client 210 serves as the SOAP originator, the PTT application server 202 serves as the SOAP ultimate destination, and the PTT server 206 serves as a SOAP intermediary. As is known in the art, SOAP provides a message framework which defines the message structure and processing mechanism, a set of encoding rules to represent service-specific data types, and a convention to enable remote procedure calls or the exchange of messages. SOAP defines a uniform manner of passing XML-encoded data, as well as defines a manner to perform Remote Procedure Calls (RPCs) using HTTP as the underlying communication protocol. Thus, in the illustrated example, XML-encoded data (including the PTT service command) may be passed from the PTT client 210 to the PTT server 206, and ultimately to the PTT application server 202 via a SOAP message using HTTP as the underlying communication protocol.
Another representative message protocol that may be used by a PTT client 210 to access a PTT application server 202 service is SIP. SIP is a signaling protocol that can be used for creating, modifying, and terminating “sessions” with one or more participants. It can be used in applications such as Internet conferencing, telephony, presence, events notification, instant messaging, and the like. SIP enables network endpoints or “user agents” to discover one another and to agree on a session characterization. In order to locate other users, SIP utilizes an infrastructure of network proxy servers to which users can send registrations, invitations to sessions, and other requests via their terminals. SIP supports various aspects of establishing and terminating sessions, such as user availability, session setup such as ringing, session management, and some limited terminal capabilities. In one embodiment, the PTT client 210 service requests may be transferred via such SIP sessions (or analogous messaging sessions).
SIP also enables messaging outside of sessions using, for example, SIP extensions for Instant Messaging (IM), where the message is sent using a SIP signaling protocol. For example, one SIP method is referred to as a “MESSAGE,” which traditionally provides for the transport of an instant message body. A SIP MESSAGE can be sent, which includes the payload of the message, and the sender receives a confirmation as to whether the message was delivered or not. In such a case, there is no explicit association between messages, and each message stands on its own. This is contrasted with session-based messaging, where there is an explicit conversation with a beginning and an end. One embodiment of the invention involves PTT clients issuing service requests by way of such non-session-based messaging.
PTT clients may also utilize other session protocols to the PTT application server 202, such as RTP, Transmission Control Protocol (TCP), and User Datagram Protocol (UDP) sessions. It is noted that the aforementioned messaging examples are provided as representative examples, and the invention is not limited thereto. Other messaging protocols may analogously be used.
The PTT embodiment described herein is applicable in any number of network systems. For purposes of illustration and not of limitation,
Referring to the example of
The Serving GPRS Support Node (SGSN) 318 serves GPRS mobile by sending or receiving packets via a Base Station Subsystem (BSS), and more particularly via the BSC 314 in the context of GSM systems. The SGSN 318 is responsible for the delivery of data packets to and from the mobile devices 302 within its service area, and performs packet routing and transfer, mobility management, logical link management, authentication, charging functions, etc. In the exemplary GPRS embodiment shown in
Other BSCs 322 and corresponding BTSs 324 are integrated into the network 316 by way of other SGSNs 326. Mobile devices 328 communicate with the BTSs 324 in this service area. Mobile devices 302, 328 can thus communicate with one another via the GSM/GPRS network 316, 320. While GSM forms the underlying technology, the SGSNs 318, 326 described above are network elements introduced through GPRS technology. Another network element introduced in the GPRS context is the Gateway GPRS Support Node (GGSN) 330, which acts as a gateway between the GPRS network 320 and a packet switched data network, such as IP Multimedia Core 332 (IP multimedia subsystems (IMS) network in the illustrated embodiment). This gateway 330 allows mobile subscribers to access the data network 332 or specified private IP networks. The connection between the GGSN 330 and the data network 332 is generally enabled through a standard protocol, such as the Internet Protocol (IP).
The PTT server 334 and PTT application server 336 of the illustrated embodiment are provided at the IP multimedia core 332. Thus, mobile devices 302, 328 can communicate with each other over the network using standard half-duplex talk spurts. A mobile device, such as mobile device 302, may opt to invoke a service available via the PTT application server 336, which is then effected as described in connection with
For purposes of illustration, the message flow of
The PTT application server 410 thus executes the “get-game-status” command to obtain a game status result. This result is provided by the PTT application server 410 to the PTT server 408 as shown on path 418. In the illustrated embodiment, the format of the result is analogous to the format of the service request. More particularly, the result shown at block 420 includes a MESSAGE method 420A that includes the URI “firstname.lastname@example.org,” which identifies the UE 404. The content type 420B is again “application/striker-format.” The resulting data 420C, “High-score=57; Leader=Bob size 77” provides the game status requested by the UE 404. This message/result is then provided by the PTT server 408 to the UE 404 as shown on path 422.
The PTT application server 410 can provide any number of different services. For purposes of example and not of limitation, such services may include voicemail, text message retrieval, chat history retrieval, game status retrieval, automatic voice conversion, and the like. Before a PTT client can access voicemail from a voicemail service provided by the PTT application server 410, other clients will provide a voice message to the PTT application server 410. This can be done in various ways. For example, the PTT application server 410 may be integrated with a standard voicemail system using, for example, standard two-way cellular or PSTN service. The PTT application server 410 would obtain the voicemail from a standard cell network voicemail system, and the PTT application server may either send a SIP MESSAGE, SIP NOTIFY, or other analogous message indicating that voicemail has arrived for a particular PTT client. Alternatively, the PTT application server 410 may simply initiate a one-to-one speech session and play the voicemail. Another example involves the user 404 initiating a one-to-one speech session to the URI hosted at the PTT application server 410. For example, “user sip:email@example.com” may be present in every PTT session, and anybody can initiate the one-to-one speech session to that address. The initiation may be accomplished using signaling (e.g., RTP, SIP, or the like, depending on the PTT version) where the user includes the intended recipient of the voicemail message to the signaling (e.g., via a header).
Statistical services such as chat history retrieval, game status retrieval, and the like involves collection of such statistics by the PTT application server 410. For example, in a game situation, the PTT application server 410 appears as a member of the gaming group, and stores relevant game statistics for subsequent retrieval by the gaming members. Still other services, such as a voice conversion service, may be provided to add enjoyment to the game. Such a service may, for example, use a text-to-speech (or speech-to-speech) converter using a celebrity voice, animated voice, etc. The resulting voice can then be sent to the intended recipients in real-time talk spurts, or alternatively stored as voicemail if the PTT application server also supports voicemail. Any number of different services is conceivable.
There are also various manners in which the PTT server 408 can be informed that a particular PTT client service request is to be forwarded to the PTT application server 410. For example, user-specific names may be used, such as “robot” to identify the PTT application server 410. The SIP MESSAGE URI 414A illustrates such an example. Alternatively, URI parameters may be selected so the PTT server 408 knows that the particular request is to be forwarded to the PTT application server 410. For example, the SIP URI may include, for example, an entry such as “user=poc-admin” to represent the PTT application server 410 as a “user” identified as a PTT over Cellular (Poc) administrator. Any other operable manner may also be used. Furthermore, rather than using SIP messaging, HTTP SOAP or other messaging protocols may analogously be used.
As shown in
In accordance with the present invention, other selectable options may be presented to the user on any mobile device screen available to the user. In the illustrated embodiment, the “Services” option is presented with the selectable recipient list 502, 504. The selectable option may be presented in any fashion, such as together with the recipient list as shown by the “Services” entry 506A, by way of a selectable “Services” icon 506B, or the like. For example, the user can highlight the “Services” entry 506A and choose the “Select” icon 508, or can make a direct selection in the case of a “Services” button 506B. Upon selecting “Services,” the PTT client presents a PTT Services screen 510. Any number of available services can be presented to the user by way of such a screen. In the illustrated embodiment, the selectable services include voicemail 512, chat group history 514, game status 516, voice converter 518, and/or other services 520. For example, if the user highlights the game status 516 and chooses the “Select” button 522, the PTT client will generate a service request destined for the appropriate PTT application server to retrieve the desired game status.
In this manner, PTT clients can not only perform their traditional half-duplex communication with other PTT clients, they can also request the performance of services via the PTT platform.
In some cases, the service may simply execute the command and perform related internal operations. For example, a service request may request that information be stored at the PTT application server. In such a case, the service request causes the PTT application server to store the desired information, and no information is returned. Examples of such service requests include storing a voicemail, game data, etc. A service request may also request that information be returned to the PTT client, such as retrieving a voicemail, game status, etc. In such case, the PTT application server generates the appropriate message with the requested data, and forwards the message to the PTT server which in turn forwards the message to the requesting PTT client, as shown at block 606.
If the service command is one that does not require the return of information to the requesting PTT client as determined at decision block 710, the service transaction is complete upon execution of the command by the PTT application server. Otherwise, the PTT application server creates 712 a service result message identifying the URI of the PTT client, and includes the result in the message. The message is transmitted 714 from the PTT application server to the PTT server, which in turn forwards 716 the result message to the mobile device/PTT client identified by the URI.
As previously indicated, the PTT application server coupled to the PTT application server via a network. In other embodiments, the PTT application server may be co-located with the PTT server, yet the PTT application server still appears as a PTT client to the PTT server. At the PTT application server, hardware, firmware, software or a combination thereof may be used to perform the various application service functions and operations described herein. An example of a representative computing implementation of a PTT application server capable of carrying out operations in accordance with the invention is illustrated in
The example computing arrangement 800 suitable for performing the service functions of the PTT application server 801 includes a central processor 802, which may be coupled to memory 804 and storage 806. The processor 802 carries out a variety of standard computing functions as is known in the art, as dictated by software and/or firmware instructions. The storage 806 may represent firmware, hard-drive storage, etc. The storage 806 may also represent other types of storage media to store programs, such as programmable ROM (PROM), erasable PROM (EPROM), etc. The processor 802 may communicate with other internal and external components through input/output (I/O) circuitry 808. The PTT application server 801 may therefore be coupled to a display 810, which may be any type of known display or presentation screen such as LCD displays, plasma display, cathode ray tubes (CRT), etc. A user input interface 812 is provided, including one or more user interface mechanisms such as a mouse, keyboard, microphone, touch pad, touch screen, voice-recognition system, etc. Any other I/O devices 814 may be coupled to the PTT application server as well.
The PTT application server 801 may also include one or more media drive devices 816, including hard and floppy disk drives, CD-ROM drives, DVD drives, and other hardware capable of reading and/or storing information. In one embodiment, software for carrying out the PTT application service operations in accordance with the present invention may be stored and distributed on CD-ROM, diskette or other form of media capable of portably storing information, as represented by media devices 818. These storage media may be inserted into, and read by, the media drive devices 816. Such software may also be transmitted to the PTT application server 801 via data signals, such as being downloaded electronically via a network, such as the Internet 820. The PTT application server 801 may be coupled to other computing devices, such as the landline and/or mobile terminals, via a network. The server may be, for example, coupled to a Local Area Network (LAN) 822 and/or may be part of a larger network configuration as in a global area network (GAN) such as the Internet 820, which allows ultimate connection to the various landline and/or mobile client devices.
In accordance with one embodiment of the invention, the storage 806, memory 804, and/or media devices 818 store the various programs and data used in connection with the present invention. In the illustrated embodiment of
The computing arrangement 800 of
The service-requesting devices in one embodiment of the invention are PTT-enabled mobile devices, such as mobile phones, PDAs, and other mobile communicators. A representative example of such a PTT-enabled mobile device which is capable of engaging in PTT service-related functions over mobile networks in accordance with the present invention is illustrated in
The processing unit 902 controls the basic functions of the mobile device 900 as dictated by programs available in the program storage/memory 904. The storage/memory 904 may include an operating system and various program and data modules associated with the present invention. In one embodiment of the invention, the programs are is stored in non-volatile electrically-erasable, programmable read-only memory (EEPROM), flash ROM, etc., so that the programs are not lost upon power down of the mobile device. The storage 904 may also include one or more of other types of read-only memory (ROM) and programmable and/or erasable ROM, random access memory (RAM), subscriber interface module (SIM), wireless interface module (WIM), smart card, or other fixed or removable memory device. The relevant software for carrying out mobile device operations in accordance with the present invention may also be transmitted to the mobile device 900 via data signals, such as being downloaded electronically via one or more networks, such as the Internet and an intermediate wireless network(s).
For performing other standard mobile device functions, the processor 902 is also coupled to user-interface 906 associated with the mobile device 900. The user-interface (UI) 906 may include, for example, a display 908 such as a liquid crystal display, a keypad 910, speaker 912, and microphone 914. These and other UI components are coupled to the processor 902 as is known in the art. The keypad 910 may include alpha-numeric keys for performing a variety of functions, including dialing numbers for conventional cellular communication. The keypad 910 may also include a button(s) designated for PTT activity, i.e., the “talk” button. The speaker 912 represents at least a loudspeaker used for PTT activity, and also the speaker that may be used in connection with standard cellular communications. The display 908 may display, among other things, the text, graphics, icons, etc., that may be used by the user in entering/selecting PTT individual and group recipients, as well as entering/selecting the desired services in accordance with the present invention. Other UI mechanisms may be employed, such as voice commands, switches, touch pad/screen, graphical user interface using a pointing device, trackball, joystick, or any other user interface mechanism.
The wireless device 900 also includes conventional circuitry for performing wireless transmissions over the mobile network. The DSP 916 may be employed to perform a variety of functions, including analog-to-digital (A/D) conversion, digital-to-analog (D/A) conversion, speech coding/decoding, encryption/decryption, error detection and correction, bit stream translation, filtering, etc. The transceiver 918, generally coupled to an antenna 920, transmits the outgoing radio signals 922 and receives the incoming radio signals 924 associated with the mobile device 900.
In the illustrated embodiment, the storage/memory 904 stores the various PTT client programs and data used in connection with the present invention. For example, the storage 904 includes the PTT client module 930 to perform PTT communications with the PTT server. A service module 932, part of the PTT client module 932 in the illustrated embodiment, may be used to create and transmit messages to provide service requests to the PTT application server by way of the PTT server. Alternatively, the application modules 934 through 936 may themselves include the appropriate instructions for such message generation.
The application modules 934 through 936 represent software modules to engage in activities such as games. For example, application module 934 may represent software for participating in a particular game with other PTT clients. The application may be such that supporting information such as high scores, player chat, voicemail, and/or other information is desirable in connection with such a game. In these cases, the application modules 934, 936 and/or the service module 932 can be used to request such services via the PTT client module 930.
Using the description provided herein, the invention may be implemented as a machine, process, or article of manufacture by using standard programming and/or engineering techniques to produce programming software, firmware, hardware or any combination thereof. Any resulting program(s), having computer-readable program code, may be embodied on one or more computer-usable media, such as disks, optical disks, removable memory devices, semiconductor memories such as RAM, ROM, PROMS, etc. Articles of manufacture encompassing code to carry out functions associated with the present invention are intended to encompass a computer program that exists permanently or temporarily on any computer-usable medium or in any transmitting medium which transmits such a program. Transmitting mediums include, but are not limited to, transmissions via wireless/radio wave communication networks, the Internet, intranets, telephone/modem-based network communication, hard-wired/cabled communication network, satellite communication, and other stationary or mobile network systems/communication links. From the description provided herein, those skilled in the art will be readily able to combine software created as described with appropriate general purpose or special purpose computer hardware to create a system and method in accordance with the present invention.
The foregoing description of the exemplary embodiment of the invention has been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. For example, a mobile device/PTT client may also serve as the PTT application server if properly equipped with the service applications. It is intended that the scope of the invention be limited not with this detailed description, but rather defined by the claims appended hereto.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US6426956||Apr 3, 2000||Jul 30, 2002||Eshagh Isaac Eteminan||Voice-browsing system and method therefor|
|US20030149774 *||Feb 7, 2002||Aug 7, 2003||Mcconnell Von K.||Method and system for facilitating services in a communication network through data-publication by a signaling server|
|US20040009761 *||Apr 10, 2002||Jan 15, 2004||Jesse Money||Method and system for real-time tiered rating of communication services|
|US20040047303 *||Sep 10, 2002||Mar 11, 2004||Fernandez Christopher Lawrence||Apparatus, system and method for managing call requests in a communication network providing a plurality of communication services|
|US20040196826 *||Apr 2, 2003||Oct 7, 2004||Cellco Partnership As Verizon Wireless||Implementation methodology for client initiated parameter negotiation for PTT/VoIP type services|
|US20040249949 *||Mar 27, 2003||Dec 9, 2004||Christophe Gourraud||Voice and multimedia distribution using Push-To-Talk (PTT) subscribers' group|
|1||"Push to Talk over Cellular (PcC)", http://www.nokia.com/nokia/0.5184.5764.00.html.|
|2||Nokia Press Releases, "Ericsson, Nokia and Siemens join forces to promote unified solution for push to talk over GPRS and EDGE networks", Feb. 17, 2003.|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US7499720 *||Nov 16, 2006||Mar 3, 2009||Sonim Technologies, Inc.||System and method for initiating push-to-talk sessions between outside services and user equipment|
|US7512410 *||Aug 2, 2005||Mar 31, 2009||Nec Corporation||Assignment of token to PTT communications|
|US7529540 *||Nov 29, 2005||May 5, 2009||International Business Machines Corporation||Method and system for invoking push-to-service offerings|
|US7624188 *||May 3, 2004||Nov 24, 2009||Nokia Corporation||Apparatus and method to provide conference data sharing between user agent conference participants|
|US7761547 *||Dec 27, 2005||Jul 20, 2010||Hitachi, Ltd.||Network system performing application control based on context information|
|US7817995 *||Apr 1, 2005||Oct 19, 2010||Nextel Communications Company L.P.||Systems and methods for scheduling the recording of audio and/or visual content|
|US7885675 *||Dec 18, 2007||Feb 8, 2011||Huawei Technologies Co., Ltd.||Method and apparatus for providing voice mailbox function in PoC service|
|US7978684 *||Sep 14, 2004||Jul 12, 2011||Nokia Corporation||Session set-up for time-critical services|
|US7996228 *||Dec 22, 2005||Aug 9, 2011||Microsoft Corporation||Voice initiated network operations|
|US8000732 *||Oct 24, 2006||Aug 16, 2011||Telefonaktiebolaget Lm Ericsson (Publ)||Methods and apparatus for push to talk type service|
|US8019383||Jan 17, 2007||Sep 13, 2011||Nokia Corporation||Techniques to increase coverage of push-to-talk wireless networks|
|US8150334 *||Oct 11, 2006||Apr 3, 2012||Telefonaktiebolaget Lm Ericsson (Publ)||Methods and apparatus for push to talk type service|
|US8180386 *||Jun 29, 2009||May 15, 2012||Sprint Communications Company L.P.||Promoting push-to-talk communication|
|US8184558 *||May 31, 2007||May 22, 2012||Telecom Italia S.P.A.||Method, gateway and system for providing a push-to-x service to a user of a data terminal|
|US8204041 *||May 19, 2004||Jun 19, 2012||T-Mobile Deutschland Gmbh||Method and system for implementing a push-to-talk service in a mobile radio communication network of the GSM-type|
|US8385848 *||Feb 27, 2012||Feb 26, 2013||Telefonaktiebolaget Lm Ericsson (Publ)||Apparatus and method providing push to talk over cellular (PoC) dynamic service options|
|US8385962||Oct 5, 2009||Feb 26, 2013||Sprint Communications Company L.P.||Push-to-talk voice messages|
|US8406798||Dec 22, 2009||Mar 26, 2013||Motorola Solutions, Inc.||Method and apparatus for bridging calls between two disparate push-to-talk systems|
|US8442497 *||Aug 3, 2006||May 14, 2013||Stephan Blicker||Method for linking internet-based forums and web logs to a push to talk platform|
|US8665760 *||Jan 22, 2008||Mar 4, 2014||Savox Communications Oy Ab (Ltd)||Method and arrangement for connecting an ad-hoc communication network to a permanent communication network|
|US8775535||Jan 18, 2012||Jul 8, 2014||Voxilate, Inc.||System and method for the transmission and management of short voice messages|
|US8798777||Mar 8, 2011||Aug 5, 2014||Packetvideo Corporation||System and method for using a list of audio media to create a list of audiovisual media|
|US9044679 *||Mar 8, 2013||Jun 2, 2015||Cane Wireless Inc.||Wireless communication system for portable gaming device|
|US9295029||Jul 27, 2015||Mar 22, 2016||Nuance Communications, Inc.||System and method for detecting mutually supported capabilities between mobile devices|
|US20050215273 *||Feb 16, 2005||Sep 29, 2005||Nec Corporation||Push-to-talk over cellular system|
|US20050262249 *||May 3, 2004||Nov 24, 2005||Nokia Corporation||Apparatus and method to provide conference data sharing|
|US20050265350 *||May 28, 2004||Dec 1, 2005||Murali Narasimha||Concurrent packet data session set-up for push-to-talk over cellular|
|US20060040688 *||Aug 2, 2005||Feb 23, 2006||Nec Corporation||Assignment of token to PTT communications|
|US20060045071 *||Sep 14, 2004||Mar 2, 2006||Nokia Corporation||Session set-up for time-critical services|
|US20060047511 *||Sep 1, 2004||Mar 2, 2006||Electronic Data Systems Corporation||System, method, and computer program product for content delivery in a push-to-talk communication system|
|US20060055771 *||Aug 24, 2004||Mar 16, 2006||Kies Jonathan K||System and method for optimizing audio and video data transmission in a wireless system|
|US20060253886 *||Apr 1, 2005||Nov 9, 2006||Nextel Communications, Inc.||Systems and methods for scheduling the recording of audio and/or visual content|
|US20060270429 *||May 25, 2005||Nov 30, 2006||Palo Alto Research Center Incorporated||Three turn interactive voice messaging method|
|US20060277296 *||Dec 27, 2005||Dec 7, 2006||Hitachi, Ltd.||Network system performing application control based on context information|
|US20070008960 *||May 19, 2004||Jan 11, 2007||Matthias Britsch||Method and system for implementing a push-to-talk service in a mobile radio communication network of the gsm-type|
|US20070123222 *||Nov 29, 2005||May 31, 2007||International Business Machines Corporation||Method and system for invoking push-to-service offerings|
|US20070142073 *||Nov 16, 2006||Jun 21, 2007||Sonim Technology, Inc.||System and method for initiating push-to-talk sessions between outside services and user equipment|
|US20070150286 *||Dec 22, 2005||Jun 28, 2007||Microsoft Corporation||Voice Initiated Network Operations|
|US20070217347 *||Jan 24, 2005||Sep 20, 2007||Manfred Leitgeb||Method and Devices for Providing a Push-to-Talk-Connection Between at Least Two User Terminals in a Communications Network|
|US20080171567 *||Jan 17, 2007||Jul 17, 2008||Nokia Corporation||Techniques to increase coverage of push-to-talk wireless networks|
|US20080299950 *||Dec 18, 2007||Dec 4, 2008||Huawei Technologies Co., Ltd.||Method and apparatus for providing voice mailbox function in poc service|
|US20080299952 *||Aug 3, 2006||Dec 4, 2008||Stephan Blicker||Method for Linking Internet-Based Forums and Web Logs to a Push to Talk Platform|
|US20080320083 *||Oct 24, 2006||Dec 25, 2008||Henrik Albertsson||Methods and Apparatus for Push to Talk Type Service|
|US20090047915 *||Oct 11, 2006||Feb 19, 2009||Henrik Albertsson||Methods and apparatus for push to talk type service|
|US20090052380 *||Aug 13, 2008||Feb 26, 2009||Joel Espelien||Mobile media router and method for using same|
|US20090097458 *||Oct 20, 2005||Apr 16, 2009||China Mobile Communications Corporation||Method and System for Agent Redirecting the Terminal Request|
|US20100100723 *||Dec 28, 2009||Apr 22, 2010||Tencent Technology (Shenzhen) Company Ltd.||Service application platform and method for accessing service application platform|
|US20100226286 *||May 31, 2007||Sep 9, 2010||Mauro Rossotto||Method, gatew and system for providing a push-to-x service to a user of a data terminal|
|US20110085475 *||Jan 22, 2008||Apr 14, 2011||Savox Communications Oy Ab (Ltd)||Method and arrangement for connecting an ad-hoc communication network to a permanent communication network|
|US20110151917 *||Dec 22, 2009||Jun 23, 2011||Motorola, Inc.||Method and apparatus for bridging calls between two disparate push-to-talk systems|
|US20120157087 *||Feb 27, 2012||Jun 21, 2012||Henrik Albertsson||APPARATUS AND METHOD PROVIDING PUSH TO TALK OVER CELLULAR (PoC) DYNAMIC SERVICE OPTIONS|
|US20140073433 *||Mar 8, 2013||Mar 13, 2014||Ingrid J. Phang||Wireless communication system for portable gaming device|
|WO2008040109A1 *||Oct 4, 2006||Apr 10, 2008||Prolity Corporation||Voice and data communication devices, methodologies and systems|
|U.S. Classification||455/90.2, 370/357|
|International Classification||H04L29/06, H04L29/08, H04B1/38, H04L12/56, H04W4/10, H04W84/08|
|Cooperative Classification||H04L65/1016, H04L65/4061, H04M2215/2093, H04M15/00, H04W76/005, H04W4/24, H04W4/10, H04L69/329, H04L67/02|
|European Classification||H04W76/00B2, H04L29/08N1, H04W4/10, H04L29/08A7, H04L29/06M4P, H04W4/24, H04M15/00|
|Jul 18, 2003||AS||Assignment|
Owner name: NOKIA CORPORATION, FINLAND
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:KOSKELAINEN, PETRI;VAINIKAINEN, MIKKO;REEL/FRAME:014280/0659
Effective date: 20030606
|Feb 25, 2010||FPAY||Fee payment|
Year of fee payment: 4
|Feb 12, 2014||FPAY||Fee payment|
Year of fee payment: 8
|Apr 26, 2015||AS||Assignment|
Owner name: NOKIA TECHNOLOGIES OY, FINLAND
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:NOKIA CORPORATION;REEL/FRAME:035495/0928
Effective date: 20150116