WO2005009006A2 - Premium voice services for wireless communications systems - Google Patents
Premium voice services for wireless communications systems Download PDFInfo
- Publication number
- WO2005009006A2 WO2005009006A2 PCT/US2004/023038 US2004023038W WO2005009006A2 WO 2005009006 A2 WO2005009006 A2 WO 2005009006A2 US 2004023038 W US2004023038 W US 2004023038W WO 2005009006 A2 WO2005009006 A2 WO 2005009006A2
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- message
- session
- handset
- server
- duplex
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/16—Arrangements for providing special services to substations
- H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
- H04L12/1813—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast for computer conferences, e.g. chat rooms
- H04L12/1818—Conference organisation arrangements, e.g. handling schedules, setting up parameters needed by nodes to attend a conference, booking network resources, notifying involved parties
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/16—Arrangements for providing special services to substations
- H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
- H04L12/189—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast in combination with wireless systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/16—Arrangements for providing special services to substations
- H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
- H04L12/1859—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast adapted to provide push services, e.g. data channels
-
- 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
- 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
Definitions
- NEXTEL uses such a system, based on a solution developed by MOTOROLA known as IDEN.
- IDEN MOTOROLA
- a dedicated private network is costly to install and maintain and is employed by a few public wireless carriers.
- the IDEN system is non-standard, and hence cannot be used in standard wireless communications networks, such as those based on CDMA and GSM.
- VoIP Voice over LP
- group-based voice services are provided by a dispatch gateway that interfaces to the wireless network to provide the group-based voice services therein, wherein both the dispatch gateway and mobiles that use the group-based voice services communicate with each other using call setup and in-band signaling within the wireless network.
- the present invention discloses two advanced group-based voice services, known as Push-to-Conference (P2C) and Push-to-Message (P2M) services.
- P2C Push-to-Conference
- P2M Push-to-Message
- the present invention also identifies a technique to achieve zero call-delay during call origination in Press-to-Talk services to enhance the user's experience.
- a real-time exchange interfaces to the wireless network to provide a full-duplex Push-to-Conference (P2C) session between an initiator and two or more other participants, wherein the P2C session comprises a full-duplex conference call, and both the real-time exchange and handsets participating in the P2C session communicate with each other using call setup and in-band signaling within the wireless network.
- the real-time exchange may be coupled to and work with a Push-to-Message (P2M) server to deliver multimedia messages in a non-real time manner from an originator to one or more recipients, without establishing voice paths, between the originator and recipients, wherein the P2M server, and an optional Voice Mail Server, provide a message storage facility for the multimedia messages.
- P2M Push-to-Message
- the handsets also permit zero-delay call setup. The user starts talking immediately upon initiation of call setup, wherein the user's speech is buffered by the handset. The buffered speech is then forwarded to the destination upon completion of the call setup.
- FIG. 1 is a block diagram that illustrates an exemplary embodiment of the dispatch services architecture framework according to a preferred embodiment of the present invention
- FIG. 2 illustrates a proposed architecture for the real-time exchange according to the preferred embodiment of the present invention
- FIG. 3 is a diagram that illustrates the call flow for the user initiating a P2C session according to the preferred embodiment of the present invention
- FIG. 4 is a diagram that illustrates the call flow for the user upgrading a P2T session to a P2C session according to the preferred embodiment of the present invention
- FIG. 1 is a block diagram that illustrates an exemplary embodiment of the dispatch services architecture framework according to a preferred embodiment of the present invention
- FIG. 2 illustrates a proposed architecture for the real-time exchange according to the preferred embodiment of the present invention
- FIG. 3 is a diagram that illustrates the call flow for the user initiating a P2C session according to the preferred embodiment of the present invention
- FIG. 4 is a diagram that illustrates the call flow for the user upgrading a P2T session to
- FIG. 5 is a diagram that illustrates the call flow for the user receiving an upgrade of a P2T session to a P2C session according to the preferred embodiment of the present invention
- FIG. 6 illustrates a system architecture for the P2M service according to the preferred embodiment of the present invention
- FIG. 7 is a diagram that illustrates the call flow between a P2M server and a voice mail server according to the preferred embodiment of the present invention
- FIG. 8 is a diagram that illustrates the call flow for the P2M Client sending a voice message using a Multi Media Services (MMS) protocol according to the preferred embodiment of the present invention
- FIG. 9 is a diagram that illustrates the call flow for the P2M server processing a P2M message according to the preferred embodiment of the present invention
- FIG. 10 is a diagram that illustrates the call flow for the P2M Server retrieving a P2M message according to the preferred embodiment of the present invention
- FIG. 11 is a diagram that illustrates the call flow for the P2M Client deleting a
- FIG. 12 depicts the processing at the handset to implement zero delay call setup according to the preferred embodiment of the present invention
- FIG. 13 is a diagram that illustrates the call flow for a GSM P2T call according to a preferred embodiment of the present invention
- FIG. 14 is a diagram that illustrates the call flow for a CDMA P2T call according to a preferred embodiment of the present invention.
- the present invention provides two advanced group-based voice services, known as Push-to-Conference (P2C) and Push-to-Message (P2M) services, in addition to Press-to-Talk (P2T) services. These services are provided by an architectural framework that interfaces into the wireless network in order to provide group call setup and messaging.
- P2C Push-to-Conference
- P2M Push-to-Message
- P2T Press-to-Talk
- the present invention describes the architectural framework in more detail below, and also shows the call flows for performing these advanced group-based voice services within the wireless network.
- FIG. 1 is a block diagram that illustrates an exemplary embodiment of a wireless communications network according to a preferred embodiment of the present invention.
- an RTX Real-Time Exchange
- MSC Mobile Switching Center
- PSTN Public Switched Telephone Network
- SS7 - ISUP/W ⁇ N/CAMEL Signaling System 7 - Integrated Services Digital Network User Part/Wireless Intelligent Network/Customized Applications for Mobile Enhanced Logic
- a bearer path 110 implements a TDM (Time Division Multiplexing) interface carrying PCM (Pulse Code Modulation) or TFO (Tandem Free Operation) voice frames.
- Support for TFO in this path 110 is negotiated between a BSC (Base Station Controller) 112 and the RTX 102 for each originating and terminating leg of a group call.
- BSC Base Station Controller
- the use of TFO ensures high voice quality (as voice codec conversion is avoided) between mobile-to-mobile calls.
- the MSC 104 routes the call to the RTX 102.
- the MSC 104 also requests the BSC 112 via 116 to establish a radio traffic path 118 with the mobile handset 120 via the BTS (Base Transceiver Station) 122 (as it does for a normal cellular call).
- the BSC 112 tries to negotiate TFO (if it is supported) on a TDM link with the far end (in this case, the RTX 102).
- the RTX 102 identifies the terminating group users and their MS-ISDN (Mobile Station ISDN Number) numbers. It sends a ISUP call origination request for each terminating handset 120.
- MS-ISDN Mobile Station ISDN Number
- the RTX 102 may send requests directly to the MSC 104, PSTN 106 or IP network 124 via a PDSN (Public Data Switched Network) 126, Router 128, and/or Internet/Intranet 130, depending on the routing table configuration for terminating MS-ISDN numbers.
- PDSN Public Data Switched Network
- Router 128, and/or Internet/Intranet 130 depending on the routing table configuration for terminating MS-ISDN numbers.
- the RTX 102 begins a negotiation with the far end (in this case, the terminating BSC 112) for each terminating leg to a handset 120.
- bearer paths 110 are established for originating and terminating legs for a group call, the RTX 102 switches (or duplicates) voice frames from the originating handset 120 to all terminating mobiles 120.
- the RTX 102 may use an IP network 124 or the Internet/Intranet 130 for two different purposes.
- the IP network 124 or the Internet/Intranet 130 can be used in a toll bypass mode where two RTXs 102 can exchange voice traffic bypassing the PSTN 106. However, each RTX 102 is responsible for terminating traffic to its closest MSC 104. In this case, the T-P network 124 or the Internet/Intranet 130 is used as a backbone transport of voice traffic between two RTXs 102.
- the IP network 124 or the Internet/Intranet 130 can also be used for a registration and presence application. Since the MSC 104 will not direct a registration request from a handset 120 to the RTX 102 (because it would require changes in the MSC 104), the latter does not have any information of the registered mobiles 120.
- a registration and presence application runs over an IP stack in the handset 120.
- the registration and presence application in the handset 120 registers with the RTX 102 using its IP address.
- the RTX 102 also uses this IP interface to update the presence information of other group members to a handset 120.
- SMS Short Message Service
- a Home Location Register (HLR) 132 can be accessed via the MSC 104 and an IS-41 link 134.
- the HLR 132 can be used to track the presence of members of a group within the network and updates the mobiles 120 for those members with the network availability of other members of the group. This is described in more detail later in this document.
- FIG. 2 illustrates a proposed architecture for the RTX 102 according to the preferred embodiment of the present invention.
- the architecture includes a Call Processing system 200, Presence Server 202, Real-Time Event Processing system 204, one or more Media Managers 206, and an SMPP (Short Message Peer-to-Peer) Transport 208, as well as modules for various SS7 protocols, such as MTP-1 (Message Transfer Part Level 1) 210, MTP-2 (Message Transfer Part Level 2) 212, MTP-3 (Message Transfer Part Level 3) 214, ISUP (Integrated Services Digital Network User Part) 216, SCCP (Signaling Connection Control Part) 218, and TCAP (Transactions Capabilities Application Part) 220 protocols.
- MTP-1 Message Transfer Part Level 1
- MTP-2 Message Transfer Part Level 2
- MTP-3 Message Transfer Part Level 3
- ISUP Integrated Services Digital Network User Part
- SCCP Synignaling Connection Control Part
- TCAP Transactions Capabilities Application Part
- the Real-Time Event Processing system 204 communicates directly with the Call Processing system 200, Presence Server 202, and the modules for various SS7 protocols.
- the modules for various SS7 protocols communicate with other entities via a SS7 Signaling Link 224.
- the SMPP Transport 206 communicates with a SMSC (Short Message Service Center) gateway using the SMPP protocol 226.
- SMSC Short Message Service Center
- the Media Managers 204 communicate among themselves using the H.l 10 protocol 228. The operation of these various components are described in more detail below.
- Push-to-Conference The RTX 102 interfaces to the wireless network 100 to provide support for a full-duplex Push-to-Conference (P2C) session between an initiator and two or more other participants, wherein the P2C session comprises a full-duplex conference call, and both the RTX 102 and handsets 120 participating in the P2C session communicate with each other using call setup and in-band signaling within the wireless network 100.
- the participants may comprise one or more contacts, one or more groups of contacts, or a subset of a group of contacts.
- the initiator may initiate the full-duplex P2C session by invoking "Push-to- Conference" on their handset 120.
- the initiator may upgrade an established half-duplex Push-to-Talk (P2T) session to the full-duplex P2C session by invoking "Upgrade to Conference" on their handset 120.
- P2T Push-to-Talk
- the initiator's handset 120 signals the RTX 102 via the wireless network 100, e.g., by transmitting one or more configured DTMF (Dual Tone Multi Frequency) digits to the RTX 102.
- the Media Manager systems 206 receive the DTMF digits and pass the DTMF digits to the Call Processing system 200.
- the Call Processing (CP) system 200 determines whether the initiator has subscribed to the P2C feature before initiating the full-duplex P2C session.
- CP Call Processing
- the Call Processing system 200 Upon confirmation, the Call Processing system 200 initiates a new P2C session and, when upgrading a P2T session, suspends floor management for the P2T session.
- the Call Processing system 200 interacts with the Presence Server 202 and Real-Time event Processing system 204 to cause the wireless network 100 to perform call setup with the other participants for the full-duplex P2C session, and thereafter to manage the full-duplex P2C session.
- the initiator hears the "Conference Confirmation" or "Conference Upgrade” tone, if the initiator's request is accepted by the RTX 102 to initiate the full-duplex P2C session.
- the RTX 102 can reject the request, if the initiator has not subscribed with the network operator for the P2C service, wherein the RTX 102 transmits an error tone (e.g., "bong") to the initiator's handset 120.
- an error tone e.g., "bong"
- the other participants hear a "Join Conference” tone, if the initiator's request to initiate the full-duplex P2C session is accepted by the RTX 102, or the other participants hear a "Conference Upgrade” tone, if the initiator's request to upgrade the half-duplex P2T session to the full-duplex P2C session is accepted by the RTX 102.
- the RTX 102 may respond with "Conference Confirmation” or "Conference Upgraded” tone as required.
- the Call Processing system 200 interacts with the Media Manager systems 206 to maintain the H.110 channels 227 and assign any additional H.110 channels 228 required for the P2C session, which may span across multiple Media Manager systems 206.
- the Media Manager systems 206 of the RTX 102 are used to mix audio streams from the initiator and other participants, and then deliver these mixed audio streams to the initiator and other participants, for full-duplex conference calling.
- the H.l 10 channels 228 are used for passing mixed and unmixed audio streams voice between the Media Manager systems 200 as required.
- the P2C session may be terminated in different ways. For example, the full-duplex P2C session may be terminated when the initiator disconnects the call, even if the other participants do not disconnect. On the other hand, the full-duplex P2C session may continue when the initiator disconnects the call, if at least two of the other participants do not disconnect. These alternatives are intended to be selectable by the network 100 operator and/or the user.
- the system is designed to support the following features to accommodate user and network operator preferences: •
- the initiator and other participants can choose to remain silent by selecting a "mute" option on their handset 120, which will cause the handset 120 microphone to be muted.
- the "unmute” option will allow the initiator and other participants to speak by unmuting the handset 120 microphone.
- the initiator can add or drop participants during an active P2C session.
- the initiator can downgrade to a half-duplex P2T session.
- the P2C session may be charged in different ways. For example, all charges related to the full-duplex P2C session could be charged to the initiator.
- the initiator and other participants in the full-duplex P2C session could all be charged for their own usage during the P2C session.
- These alternatives are selectable by the network 100 operator and/or the user. • If the network 100 operator subscribes to the "Calling Party Pays" regime, where all charges related to a P2T session or a P2C session are charged to the calling party (initiator), then the P2C session is terminated when the initiator disconnects the call, even if the other participants do not disconnect.
- the network 100 operator subscribes to the "Called Party Pays" regime, where the initiator and other participants in a P2C call are each charged for their own usage, the P2C session continues, even if the initiator disconnects, so long as there are at least two participants on the P2C session.
- the facilities for the full-duplex P2C session or for upgrading the established half-duplex P2T session to the full-duplex P2C session are available to users who have subscribed to this service. The user also must possess a handset 120 with suitable modifications to allow menu interactions to service the P2C feature.
- P2C Call Flows The following sections describes the call flows for some of the major operations in the P2C service.
- FIG. 3 is a diagram that illustrates the call flow for the user initiating a P2C session according to the preferred embodiment of the present invention.
- the user selects or creates a group on the handset 120.
- the RTX 102 returns one or more messages that show the current presence or availability for all group members, for all available networks. In a preferred embodiment, the current presence or availability of all group members is visually displayed on the handset 120 within a few seconds of any state change, for all available networks. (An alert tone may also be used, as specified by the user.) 3.
- the RTX returns one or more messages containing a "Conference Confirmation" tone, if the initiator's request to initiate the P2C session is accepted by the RTX 102, or an error tone, if the initiator's request to initiate the P2C session is denied by the RTX 102. 5.
- the user speaks into the handset 120 to talk, and a corresponding voice signal is transmitted to the RTX 102, for mixing with other audio and re-distribution to the other participants. 6.
- the user receives messages from the RTX 102 at the handset 120, wherein the messages include the mixed audio from the participants distributed by the RTX 102. Further call processing is described in FIG. 4.
- FIG. 4 is a diagram that illustrates the call flow for the user upgrading a P2T session to a P2C session according to the preferred embodiment of the present invention.
- the user who has already established a P2T session, presses the 'Upgrade to P2C button or menu item on the handset 120, and a corresponding message is transmitted to the RTX 102.
- the RTX returns one or more messages containing a "Conference Confirmation" tone, if the user's request to upgrade to a P2C session is accepted by the RTX 102, or an error tone, if the user's request to upgrade to a P2C session is denied by the RTX 102. 3.
- the user speaks into the handset 120 to talk, and a corresponding message is transmitted to the RTX 102, for mixing with other audio and re-distribution to the other participants. 4.
- the user receives messages from the RTX 102 at the handset 120, wherein the messages include the mixed audio from the participants distributed by the RTX 102. Further call processing is described in FIG. 5.
- FIG. 5 is a diagram that illustrates the call flow for the user receiving an upgrade of a P2T session to a P2C session according to the preferred embodiment of the present invention. 1.
- the RTX sends a message containing a
- the RTX returns one or more messages containing a "Conference Confirmation” tone, if the user's request to join the P2C session is accepted by the RTX 102, or an error tone, if the user's request to join the P2C session is denied by the RTX 102. 4. During the P2C session, the user speaks into the handset 120 to talk, and a corresponding message is transmitted to the RTX 102, for mixing with other audio and re-distribution to the other participants. 5.
- P2M Push-to-Message
- MMS Multi Media Services
- the system architecture includes one or more RTXs 102 coupled to a P2M server 600, which is (optionally) coupled to a Voice Mail Server 602, wherein the RTX 102 and the P2M server 600 work together to deliver P2M messages in a non-real time manner from an originator to one or more recipients, without establishing voice paths between the originator and recipients.
- Recipients may comprise one or more contacts, one or more groups of contacts, or a subset of a group of contacts.
- the P2M Server 600 provides a message storage facility for a user's P2M messages, and may interface to the Voice Mail Server 602 to provide a message storage facility for the multimedia messages, so that a user's message storage capacity is not limited to the capacity of their handset 120.
- the user can store P2M messages in the P2M Server 600, retrieve P2M messages from the P2M Server 600, and reply to the messages, or forward the messages to other P2M subscribers.
- the P2M service supports the sending of P2M messages to one or more contacts, one or more groups of contacts, or a subset of a group of contacts. It is also possible to integrate any existing Voice Mail Server (VMS) with the P2M service. In such situations, the VMS can notify the P2M server 600 if any new messages are waiting for a subscriber.
- MMS is used as the transport mechanism for communicating the P2M messages between the handset 120 and P2M Server 600.
- the P2M Server 600 interfaces to an SMSC (Short Message Service Center) 604, which conveys SMS messages to the MSC 104 and then to the handset 120, as well as the reverse. In some instances, it is also possible to use MMS or IP in place of SMS messaging.
- the P2M Server 600 interfaces to an MMSC (MMS Service Center) 606, which conveys MMS messages to a WAP (Wireless Application Protocol) Gateway 608 and then to the handset 120, as well as the reverse.
- MMSC MMS Service Center
- WAP Wireless Application Protocol
- the major advantages of the P2M service include the following: • Users can transmit P2M messages in a non-real-time manner without needing to establish end-to-end voice paths to the recipients. • Users can deliver P2M messages to a large number of recipients. • Users can schedule the delivery of P2M messages for a specific time. • The P2M Server 600 allows for the storage and retrieval of large P2M messages, thereby overcoming potential limitations in handset 120 message storage capacity. o The P2M service does not require any changes to the wireless network elements. o Users can request a consolidated delivery receipt for any messages sent.
- a P2M subscriber wishing to send a P2M message selects a recipient (i.e., one or more contacts, one or more groups of contacts, or a subset of a group of contacts), and records the P2M message.
- the P2M Client 610 in the handset 120 stores the recorded P2M message into a file in a predefined format.
- the P2M Client 210 forms an MMS message with the recipient's information (such as Group Id, Member Index, etc.), attaches the file to the MMS message, and sends the MMS message to the P2M Server 600.
- the P2M Server 600 receives the MMS message from the MMSC 606 over the MM7 interface.
- the P2M Server 600 performs authentication, extracts the recipient's information from the MMS message, and stores the P2M message in its temporary data 612.
- the P2M Server 600 then performs a remote query to one or more RTXs 102 to obtain the recipient's status and group member information.
- the P2M server forms a new MMS message that contains the P2M message and sends it to recipients who are on line, and also stores the message in the inbox. For recipients who are off-line, the messages would be stored in the P2M server 600 and marked as new (unread) message.
- the P2M Client 610 executed by the handset 120 registers with P2M Server
- the P2M Client 610 receives a notification from the MMSC 606 of the new MMS message, and then retrieves the new MMS message from the MMSC 606. Thereafter, the P2M Client 610 provides an alert notification to the user of the new MMS message.
- the P2M Client 610 also adds the new MMS message to the inbox of the handset 120, and also keeps track of read and unread messages. Using the new MMS message, the P2M Client 610 can request delivery of the P2M message stored by the P2M Server 600.
- the P2M Client 610 Upon receipt of the P2M message, the P2M Client 610 plays or displays any audio, video, images, data or text found in the P2M message.
- the P2M message may also be stored on the P2M Client 610 (even if temporarily).
- the P2M Client 610 provide the necessary functionality to manage the P2M messages, regardless of where they are stored. For example, the P2M Client 610 may store a user selectable number of P2M messages in the handset 120 itself, and may store another user selectable number of P2M messages in the P2M Server 600. Further, the user can choose to retrieve, delete, forward or reply to any of the P2M messages.
- the P2M Server 600 would store the P2M message as temporary data 612.
- the P2M Server 600 would store the P2M message using the message storage 614 of the Voice Mail Server 602, wherein standard FTP (File Transfer Protocol) commands would be used to store and retrieve P2M messages from the Voice Mail Server 602.
- the P2M Server 600 would store each P2M message using a Subscriber Id and Sequence Id.
- the P2M Server 600 does not define how the P2M message should be stored in the Voice Mail Server 602.
- FIG. 7 is a diagram that illustrates the call flow for the third approach.
- the P2M Server 600 sends a PUT message to the Voice Mail Server 602, wherein the message includes a Subscriber Id and Sequence Id.
- the Voice Mail Server 602 sends a response to the P2M Server 600, acknowledging the PUT message. 3.
- the P2M Server 600 transfers a file containing the P2M message to the Voice Mail Server 602, and the Voice Mail Server 602 stores the file using the Subscriber Id and Sequence Id. 4.
- the P2M Server 600 sends a GET message to the Voice Mail Server 602, wherein the message includes a Subscriber Id and Sequence Id. 5.
- the Voice Mail Server 602 sends a response to the P2M Server 600, acknowledging the GET message. 6.
- the Voice Mail Server 602 retrieves a file contaming the P2M message using the Subscriber Id and Sequence Id, and then transfers the file to the P2M Server 600. 7.
- the P2M Server 600 sends a DELETE message to the Voice Mail Server 602, wherein the message includes a Subscriber Id and Sequence Id. 8.
- the Voice Mail Server 602 deletes a file containing the P2M message using the Subscriber Id and Sequence Id, and then sends a response to the P2M Server 600, acknowledging the DELETE message.
- the Voice Mail Server 602 sends a NOTIFY message to the P2M Server 600 indicating the Subscriber Id and Calling Party Id. 10.
- the P2M Server 600 responds to the Voice Mail Server 602 with a
- P2M Call Flows The following sections describes the call flows for some of the major operations in the P2M service.
- FIG. 8 is a diagram that illustrates the call flow for the P2M Client 610 sending a message using MMS according to the preferred embodiment of the present invention.
- the user selects a recipient on the handset 120. 2. The user presses the P2M button on the handset 120. 3. The P2M Client 610 plays a Start Message tone on the handset 120. 4. The P2M Client 610 records the P2M message. 5. The user releases the P2M button on the handset 120. 6. The P2M Client 610 displays a menu on the handset 120, that indicates three options for the user: review, send or re-record. 7. The user selects either review, send or re-record from the menu on the handset 120.
- the P2M Client 610 forms an MMS message (MM1_SUBMIT.REQ) with the recipient's information as the text part and the file containing the P2M message as an attachment. The P2M Client 610 then sends the MMS message to the MMSC 606. 9. The MMSC 606 sends a response (MM1_SUBMIT.RES) message to the P2M Client 610. Further message processing is described in FIG. 9.
- FIG. 9 is a diagram that illustrates the call flow for the P2M Server 600 processing the message according to the preferred embodiment of the present invention.
- the MMSC 606 sends a delivery request (MM7_DELINER.REQ) message to the P2M Server 600.
- the P2M Server 600 sends a response (MM7_DELIVER.RES) message to the MMSC 606.
- the P2M Server 600 sends a query message to the RTX 102 to obtain subscriber, group and recipient information.
- the P2M Server 600 assigns a unique Message Id to the P2M message, for later reference. A new MMS message is formed and then sent to any recipients that are currently online.
- the new MMS message may be locally stored and sent later to recipients that are currently offline, when they are online again.
- the P2M Server 600 sends a submit request (MM7_SUBMIT.REQ) message to the MMSC 606. 5.
- the MMSC 606 sends a response (MM7_SUBMIT.RES) message to the P2M Server 600.
- the MMSC 606 sends a notify request (MMl_NOTTFY.REQ) message to the P2M Client 610.
- the P2M Client 610 uses the Subject field in the notify request message to identify the P2M message.
- the P2M Client 610 sends a response (MMl_NOTJFY.RES) message to the MMSC 606. 8.
- the MMSC 606 sends a report request (MM7_REPORT.REQ) message to the P2M Server 600. 9.
- the P2M Server 600 sends a response (MM7_REPORT.RES) message to the MMSC 606.
- the P2M Client 610 sends a retrieve request (MM1_RETRTENE.REQ) message to the MMSC 606.
- the P2M Client 610 retrieves the MMS message immediately, and preferably, in the background.
- the MMSC 606 sends a response (MM1_RETRJJEVE.RES) message to the P2M Client 610. 12.
- the P2M Client 610 Upon completion of the download of the MMS message, the P2M Client 610 sends a read reply receipt request
- MM1_READ_REPLY_RECE ⁇ PT.REQ message to the MMSC 606.
- the P2M Client 610 plays an Alert New P2M Message tone is played and/or an indication is displayed on the handset 120. The user can choose to display or play the P2M message immediately or at a later time.
- the MMSC 606 sends a read reply receipt request (MM7_READ_RECEIPT.REQ) message to the P2M Server 600.
- the P2M Server 600 sends a response (MM7_READ_RECELPT.RES) message to the MMSC 606. Further message processing is described in FIG. 10.
- FIG. 10 is a diagram that illustrates the call flow for the P2M Server 600 processing the message according to the preferred embodiment of the present invention.
- the user selects a message for retrieval on the handset 120.
- the P2M Client 610 sends an SMS message containing the details of the P2M message to be retrieved, i.e., the corresponding Message Id, to the SMSC 604.
- the SMSC 604 sends a deliver (SMMP: DELIVER SM) message with the corresponding Message Id to the P2M Server 600 via the MMSC 606.
- the P2M Server 600 retrieves the P2M message using the Message Id. 4.
- SMMP DELIVER SM
- the P2M Server 600 sends a submit request (MM7_SUBMIT.REQ) message to the MMSC 606. 5.
- the MMSC 606 sends a response (MM7_SUBMIT.RES) message to the P2M Server 600.
- the MMSC 606 sends a notify request (MMl_NOTIFY.REQ) message to the P2M Client 610 via the SMSC 604.
- the P2M Client 610 sends a response (MMl_NO ⁇ FY.RES) message to the MMSC 606 via the SMSC 604.
- the MMSC 606 sends a delivery report request (MM7_DELINERY_REPORT.REQ) message to the P2M Server 600.
- the P2M Server 600 sends a response
- the P2M Client 610 sends a retrieve request (MM1 JRETRTEVE.REQ) message to the MMSC 606 via the SMSC 604. 11.
- the MMSC 606 sends a response (MM1 J ETRIEVE.RES) message to the P2M Client 610 via the SMSC 604.
- the P2M Client 610 sends a read reply receipt request (MM1_READ_REPLY_RECELPT.REQ) message to the MMSC 606 via the SMSC 604.
- the P2M Client 610 plays an Alert tone (or displays text) and then displays or plays the P2M message on the handset 120. 14.
- the MMSC 606 sends a read receipt request (MM7_READ_RECEIPT.REQ) message to the P2M Server 600. 15.
- the P2M Server 600 sends a response (MM7_READ_RECEIPT.RES) message to the MMSC 606. Further message processing is described in FIG. 11.
- FIG. 11 is a diagram that illustrates the call flow for the P2M Client 610 deleting the P2M message according to the preferred embodiment of the present invention. 1. The user selects a P2M message for deletion on the handset 120. 2. To delete a P2M message, the P2M Client 610 sends an SMS message containing the details of the P2M message to be deleted, i.e., the corresponding
- the P2M message is also deleted locally on the handset 120 (if it exists).
- the SMSC 604 sends a deliver (SMMP: DELIVER SM) message with the corresponding Message Id to the P2M Server 600 via the MMSC 606.
- SMMP DELIVER SM
- the P2M Server 600 Upon receipt of the message, the P2M Server 600 deletes the P2M message using the Message Id.
- the P2M Server 600 sends a submit (MM7_SUBMIT SM) message as a response to the SMSC 604 via the MMSC 606. 5.
- the SMSC 604 sends a confirmation message to the P2M Client 610.
- Message Inbox Functionality The P2M Message Inbox functionality is provided to support management of messages as in email.
- the P2M Client 610 provides functionality to list out previously received P2M messages for a specified duration (configured in the P2M Server 600 for the subscriber).
- the P2M Client 610 can store a specified number of P2M messages in the handset 120 and the remaining messages would be stored in the P2M Server 600.
- the user can play, delete, forward or reply to any of the saved messages.
- the P2M Client 610 can download, via MMS, P2M messages stored in the P2M Server 600 through an SMS request to the P2M Server 600 indicating the Message LD (Identification) of the selected message.
- the size of P2M messages conveyed over MMS is limited in size to around 30 Kilobytes, which for voice messages indicates a limit of 40 seconds. Using fragmentation and reassembly, longer duration messages can be accommodated. For longer duration messages, the P2M Client 610 divides the message into multiple smaller messages to fit within the constraint of MMS. The P2M Server 600 receives and sends the fragmented MSS messages to the intended recipients. The terminating P2M Client 610 would reassemble the fragmented messages and regenerate the original long duration message.
- FIG. 12 depicts the processing at a handset 120 that interfaces to the wireless network to provide voice services between a user and one or more destinations, wherein call setup for the voice services involves zero delay.
- the user starts talking immediately upon initiation of the call setup, the user's speech is buffered by the handset 120, and the buffered speech is forwarded to the destination upon completion of the call setup.
- the steps involved are indicated below: 1.
- the user initiates a P2T/P2C session by pressing the P2T/P2C button on the handset 120 (or by performing an equivalent operation such as choosing a menu item in the handset 120). 2.
- Call setup starts. 3.
- the handset 120 generates a confirmation signal, the user starts talking immediately upon receiving the confirmation signal, and the handset 120 buffers the user's speech for a specified duration.
- the confirmation signal may comprise a "chirp,” “click,” “pop-up message,” etc.
- the handset 120 may receive an error signal if one or more of the destinations is unavailable, or if the user if the user does not control a floor for group services.
- the use of such signals is optional, not mandatory, and thus the signals can be employed according to a user preference. 4.
- Call setup completes. 5.
- the handset 120 stops buffering the user's speech and starts its playout of the buffered speech for transmission to the destination.
- the specified duration may be determined by a user preference, and generally comprises the smaller of a time period required to complete the call setup or a time period between the user pressing and releasing a button on the handset 120. 6. Finally, the user releases the P2T/P2C button on the handset 120. The above steps apply to the first push of the button only. 7. Playout of the buffered speech completes. Although the steps of FIG. 12 illustrate the situation where the specified duration is equal to the call setup time, those skilled in the art will recognize that the specified duration may be less than the call setup time, for example, when the P2T/P2C button is released by the user before call setup completes.
- the user may talk for an arbitrary amount of time, but the buffer period is limited and, as indicated above, is the smaller of call setup time or the period of the first push of the P2T/P2C button.
- the first push of the P2T/P2C button may be 4 seconds long. In that case, only 2 seconds of speech are buffered and playout of those 2 seconds of speech occurs as soon as call setup is completed.
- the first push of the P2T/P2C button is only 1.5 seconds, only 1.5 seconds of speech is buffered, and playout of those 1.5 seconds of speech occurs after call setup is completed. In any case, the playout of the buffered speech starts only after call setup is complete.
- FIG. 13 is a diagram that illustrates the call flow for a GSM P2T or P2C call according to a preferred embodiment of the present invention.
- the first or originating handset 120 (identified in the figure as handset #1) requests an assignment of a dedicated signaling channel for call origination, and starts buffering the user's speech.
- a dedicated signaling channel is assigned and intimated to the first handset 120.
- a CM Service Request is send to the MSC 104 to initiate a call setup procedure.
- the MSC 104 may delay the authentication in order to speed up the call setup. 4.
- the MSC 104 sends a CM Service Accept to the first handset 120 in order to proceed with call setup. In this case, authentication may be initiated by the MSC 104 at a later time. 5.
- the first handset 120 sends a setup message with the dialed digits.
- the dialed digits contain the access code for the group call and the group ID.
- the MSC 104 Because the origination trigger criteria is met as per the subscriber's profile for P2T/P2C service, the MSC 104 originates an Initial DP (Detection Point) Request to the RTX 102 for further service interaction.
- Initial DP Detection Point
- the RTX 102 After receiving the Initial DP Request from the MSC 104, the RTX 102 looks into its database of group information in order to obtain directory numbers of group members belonging to the group ID specified in the message. For each member of the group, the RTX 102 originates an LAM and sends it to the MSC 104 with a directory number as the called party number. The RTX 102 also sends CIC information for each terminating leg to the MSC 104. 8.
- the GSM SCF Service Control Function instructs the MSC 104 to connect to the RTX 102 by specifying a redirection number.
- the MSC 104 triggers the assignment procedure for allocating terrestrial resources between the BSC 112 and MSC 104, and radio resources for the first handset 120.
- the first handset 120 is notified about the allocated channel for this call.
- the MSC 104 begins routing the call based on the redirection number received from the GSM SCF.
- the MSC 104 terminates the call to the RTX 102 by sending an LAM.
- the RTX 102 after receiving the IAM, immediately responds to the MSC 104 with an ACM, and subsequently, an ANM with no delay between them.
- the MSC 104 sends an Alert to the first handset 120 to trigger alerting at the first handset 120.
- the RTX 102 sends an ANM to the MSC 104.
- the MSC 104 sends a connect to the first handset 120, which stops the alerting tone at the first handset 120.
- the first handset 120 stops buffering the user's speech, and begins the playout of the buffered speech, in order to transmit the speech packets to the RTX 102.
- the MSC 104 send a paging request to the BSC 112 to locate the second or terminating handset 120 (identified in the figure as handset #2).
- the BSC 112 performs a paging procedure to locate the second handset 120.
- the second handset 120 requests a dedicated signaling channel.
- a dedicated signaling channel is assigned and intimated to the second handset 120.
- the second handset 120 sends a paging response through the dedicated signaling channel.
- the BSC 112 When the BSC 112 receives the paging response from the second handset 120, it sends an MS Conn Estd (Mobile Station Connection Established) message to the MSC 104.
- MS Conn Estd Mobile Station Connection Established
- the MSC 104 sends a Setup message to the second handset 120 with information such as the called party number and group ID.
- the second handset 120 responds with a Call Confirmed message to the MSC 104.
- the MSC 104 performs an assignment procedure to allocate terrestrial and radio resources. 25. After successful allocation of all resources, the second handset 120 sends an Alerting message to the MSC 104 to indicate that it is alerting. 26. The MSC 104 sends an ACM to the RTX 102 confirming the alerting of the terminating handset 120. 27. The second handset 120 (without waiting for user response) sends a Connect message to the MSC 104 if the service does not require the user to press any key on the handset 120 to accept the call. This provides instant connectivity between the originating and terminating handsets 120. 28. The MSC 104 sends an ANM message to the RTX 102 and the RTX 102 completes the one-way voice path from the originating handset 120 to terminating handset 120.
- FIG. 14 is a diagram that illustrates the call flow for a CDMA P2T call according to a preferred embodiment of the present invention.
- the first or originating handset 120 (identified in the figure as handset #1) originates a group call, and starts buffering the user's speech. 2.
- the MSC 104 Upon receiving the origination request, the MSC 104 analyzes the dialed digits and determines that the trigger code in the called party IE meets the origination trigger criteria. On satisfying the origination trigger criteria, an ORREQ (Origination Request) message is sent to the RTX 102.
- the ORREQ contains the dialed digits. 3.
- the MSC 104 begins allocating terrestrial resources required for the call between the BSC 112 and the MSC 104, and sends CIC (Circuit Identity Code) information in an Assignment request to the BSC 112. 4.
- the BSC 112 performs a traffic channel setup for the first handset 120, which initiates the radio channel allocation procedure.
- the RTX 102 analyzes the dialed digits and identifies the group id. It responds to the MSC 104 with an ORREQ message, which contains the routing number to the RTX 102 so that the MSC 104 can terminate this group call to the RTX 102. 6.
- the RTX 102 gets the group id from the dialed digits received in the ORREQ message.
- MDN Mobile Directory Number
- LAM Initial Address Message
- the terminating legs are set-up in parallel with originating leg set-up to speed up the call set-up time. 7.
- the BSC 112 sends an Assignment Complete message to the MSC 104.
- the MSC 104 begins to route the call based on routing info (TERMLIST) received from the RTX 102 in the ORREQ message.
- the MSC 104 sends an LAM message to the RTX 102. 9.
- the RTX 102 after receiving the IAM, immediately responds to the MSC 104 with an ACM (Address Complete Message), and subsequently ANM (Answer Message) with no delay between them. 10.
- the MSC 104 plays an in-band ring back tone after receiving the ACM.
- the ANM is received by the MSC 104 and it stops the ring back tone.
- the first handset 120 stops buffering the user's speech, and begins the playout of the buffered speech, in order to transmit the speech packets to the RTX 102.
- the MSC 104 sends a paging request to the BSC 112 in order to locate the second or terminating handset 120 (identified in the figure as handset #2).
- the BSC 112 performs a paging procedure for the second handset 120.
- the BSC 112 gives a paging response to the MSC 104.
- the MSC 104 allocates a terrestrial circuit between the MSC 104 and BSC 112, and sends the information to the BSC 112 in an Assignment Request.
- the Assignment Request message also contains the calling party number with its group ID and signal IE for the alerting second handset 120.
- the BSC 112 performs a traffic channel setup procedure for the second handset 120, which initiates the radio channel allocation procedure. 18. Subsequent to completion of the traffic channel setup, the BSC 112 sends an Assignment Complete message to the MSC 104. 19.
- the BSC 112 sends an Alert With Info message to the second handset 120 to start alerting.
- This message has the calling party number, which contains the group ID.
- the second handset 120 understands from this group LO that the call is a P2T or P2C, and ignores signal IE in this message.
- the MSC 104 sends an ACM to the RTX 102 after receiving an Assignment Complete message from the BSC 112, indicating that the second handset 120 is alerting.
- the second handset 120 (without waiting for user response) sends a connect message to the BSC 112 and MSC 104 if the service does not require the user to press any key on the handset 120 to accept the call. This provides instant connectivity between the originating and terminating handsets 120.
- the MSC 104 sends an ANM message to the RTX 102 and the RTX 102 completes the one-way voice path from the originating handset 120 to the terminating handset 120.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- General Engineering & Computer Science (AREA)
- Multimedia (AREA)
- Telephonic Communication Services (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
Claims
Priority Applications (10)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/564,903 US20060189337A1 (en) | 2003-07-18 | 2004-07-16 | Premium voice services for wireless communications systems |
EP04778507A EP1649706A4 (en) | 2003-07-18 | 2004-07-16 | Premium voice services for wireless communications systems |
US11/126,587 US7738892B2 (en) | 2002-05-24 | 2005-05-11 | Architecture, client specification and application programming interface (API) for supporting advanced voice services (AVS) including push to talk on wireless handsets and networks |
PCT/US2005/016534 WO2005112494A1 (en) | 2004-05-11 | 2005-05-11 | Architecture, client specification and application programming interface (api) for supporting advanced voice services (avs) including push to talk on wireless handsets and networks |
PCT/US2005/016771 WO2005115032A1 (en) | 2004-05-14 | 2005-05-13 | Roaming gateway for support of advanced voice services while roaming in wireless communications systems |
US11/129,268 US7403775B2 (en) | 2002-05-24 | 2005-05-13 | Roaming gateway for support of advanced voice services while roaming in wireless communications systems |
US11/134,883 US7764950B2 (en) | 2002-05-24 | 2005-05-23 | Advanced voice services architecture framework |
PCT/US2005/018243 WO2005117474A1 (en) | 2004-05-24 | 2005-05-24 | Subscriber identity module (sim) enabling advanced voice services (avs) including push-to-talk, push-to-conference and push-to-message on wireless handsets and networks |
US11/136,233 US7738896B2 (en) | 2002-05-24 | 2005-05-24 | Subscriber identity module (SIM) enabling advanced voice services (AVS) including push-to-talk, push-to-conference and push-to-message on wireless handsets and networks |
US11/158,527 US7529557B2 (en) | 2002-05-24 | 2005-06-22 | Press-to-connect for wireless communications systems |
Applications Claiming Priority (7)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/US2003/016386 WO2003101007A1 (en) | 2002-05-24 | 2003-05-23 | Dispatch service architecture framework |
US48863803P | 2003-07-18 | 2003-07-18 | |
US60/488,638 | 2003-07-18 | ||
US49265003P | 2003-08-05 | 2003-08-05 | |
US60/492,650 | 2003-08-05 | ||
US57609404P | 2004-06-02 | 2004-06-02 | |
US60/576,094 | 2004-06-02 |
Related Parent Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2003/016386 Continuation-In-Part WO2003101007A1 (en) | 2002-05-24 | 2003-05-23 | Dispatch service architecture framework |
US11/129,268 Continuation-In-Part US7403775B2 (en) | 2002-05-24 | 2005-05-13 | Roaming gateway for support of advanced voice services while roaming in wireless communications systems |
US11/134,883 Continuation-In-Part US7764950B2 (en) | 2002-05-24 | 2005-05-23 | Advanced voice services architecture framework |
Related Child Applications (7)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2003/016386 Continuation-In-Part WO2003101007A1 (en) | 2002-05-24 | 2003-05-23 | Dispatch service architecture framework |
US10/515,556 Continuation-In-Part US7787896B2 (en) | 2002-05-24 | 2003-05-23 | Dispatch service architecture framework |
US11/126,587 Continuation-In-Part US7738892B2 (en) | 2002-05-24 | 2005-05-11 | Architecture, client specification and application programming interface (API) for supporting advanced voice services (AVS) including push to talk on wireless handsets and networks |
US11/129,268 Continuation-In-Part US7403775B2 (en) | 2002-05-24 | 2005-05-13 | Roaming gateway for support of advanced voice services while roaming in wireless communications systems |
US11/134,883 Continuation-In-Part US7764950B2 (en) | 2002-05-24 | 2005-05-23 | Advanced voice services architecture framework |
US11/136,233 Continuation-In-Part US7738896B2 (en) | 2002-05-24 | 2005-05-24 | Subscriber identity module (SIM) enabling advanced voice services (AVS) including push-to-talk, push-to-conference and push-to-message on wireless handsets and networks |
US11/158,527 Continuation-In-Part US7529557B2 (en) | 2002-05-24 | 2005-06-22 | Press-to-connect for wireless communications systems |
Publications (2)
Publication Number | Publication Date |
---|---|
WO2005009006A2 true WO2005009006A2 (en) | 2005-01-27 |
WO2005009006A3 WO2005009006A3 (en) | 2005-04-21 |
Family
ID=34437736
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2004/023038 WO2005009006A2 (en) | 2002-05-24 | 2004-07-16 | Premium voice services for wireless communications systems |
Country Status (1)
Country | Link |
---|---|
WO (1) | WO2005009006A2 (en) |
Cited By (38)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2007048671A1 (en) * | 2005-10-24 | 2007-05-03 | Nokia Siemens Networks Gmbh & Co. Kg | Communication network and communication method in a communication network |
WO2007126642A2 (en) | 2006-04-07 | 2007-11-08 | Cisco Technology, Inc. | System and method for dynamically upgrading/downgrading a conference session |
US7403775B2 (en) | 2002-05-24 | 2008-07-22 | Kodiak Networks, Inc. | Roaming gateway for support of advanced voice services while roaming in wireless communications systems |
WO2009053871A1 (en) * | 2007-10-25 | 2009-04-30 | Koninklijke Philips Electronics N.V. | Communications service |
US7529557B2 (en) | 2002-05-24 | 2009-05-05 | Kodiak Networks, Inc. | Press-to-connect for wireless communications systems |
US7689238B2 (en) | 2005-08-03 | 2010-03-30 | Kodiak Networks, Inc. | Architecture and implementation of closed user groups and limiting mobility in wireless networks |
US7738896B2 (en) | 2002-05-24 | 2010-06-15 | Kodiak Networks, Inc. | Subscriber identity module (SIM) enabling advanced voice services (AVS) including push-to-talk, push-to-conference and push-to-message on wireless handsets and networks |
US7738892B2 (en) | 2002-05-24 | 2010-06-15 | Kodiak Networks, Inc. | Architecture, client specification and application programming interface (API) for supporting advanced voice services (AVS) including push to talk on wireless handsets and networks |
US7764950B2 (en) | 2002-05-24 | 2010-07-27 | Kodiak Networks, Inc. | Advanced voice services architecture framework |
US7787896B2 (en) | 2002-05-24 | 2010-08-31 | Kodiak Networks, Inc. | Dispatch service architecture framework |
US7813722B2 (en) | 2005-02-18 | 2010-10-12 | Kodiak Networks, Inc. | Enhanced features in an advanced voice services (AVS) framework for wireless communications systems |
US7853279B2 (en) | 2006-04-26 | 2010-12-14 | Kodiak Networks, Inc. | Advanced features on a real-time exchange system |
US8036692B2 (en) | 2005-08-08 | 2011-10-11 | Kodiaks Networks, Inc. | Brew platform enabling advanced voice services (AVS) including push-to-talk, push-to-conference and push-to-message on wireless handsets and networks |
US8369829B2 (en) | 2010-03-03 | 2013-02-05 | Kodiak Networks, Inc. | Prepaid billing solutions for push-to-talk in a wireless communications network |
US8498660B2 (en) | 2009-03-30 | 2013-07-30 | Kodiak Networks, Inc. | Enhanced group calling features for connected portfolio services in a wireless communications network |
US8670760B2 (en) | 2008-01-24 | 2014-03-11 | Kodiak Networks, Inc. | Converged mobile-web communications solution |
US8676189B2 (en) | 2008-01-24 | 2014-03-18 | Kodiak Networks, Inc. | Converged mobile-web communications solution |
US9088876B2 (en) | 2012-02-01 | 2015-07-21 | Kodiak Networks, Inc. | WiFi interworking solutions for push-to-talk-over-cellular (PoC) |
US9775179B2 (en) | 2004-11-23 | 2017-09-26 | Kodiak Networks, Inc. | Method to achieve a fully acknowledged mode communication (FAMC) in push-to-talk over cellular (PoC) |
US9913300B2 (en) | 2011-12-14 | 2018-03-06 | Kodiak Networks, Inc. | Push-to-talk-over-cellular (PoC) |
US9961514B2 (en) | 2013-07-23 | 2018-05-01 | Kodiak Networks, Inc. | Effective presence for push-to-talk-over-cellular (PoC) networks |
US10057105B2 (en) | 2004-11-23 | 2018-08-21 | Kodiak Networks, Inc. | Architecture framework to realize push-to-X services using cloudbased storage services |
US10110342B2 (en) | 2015-10-06 | 2018-10-23 | Kodiak Networks Inc. | System and method for tuning PTT over LTE according to QoS parameters |
US10111055B2 (en) | 2004-11-23 | 2018-10-23 | Kodiak Networks, Inc. | Optimized methods for large group calling using unicast and multicast transport bearer for PoC |
US10116691B2 (en) | 2004-11-23 | 2018-10-30 | Kodiak Networks, Inc. | VoIP denial-of-service protection mechanisms from attack |
US10129307B2 (en) | 2015-10-06 | 2018-11-13 | Kodiak Networks Inc. | PTT network with radio condition aware media packet aggregation scheme |
US10178513B2 (en) | 2004-11-23 | 2019-01-08 | Kodiak Networks, Inc. | Relay-mode and direct-mode operations for push-to-talk-over-cellular (PoC) using WiFi-technologies |
US10257669B2 (en) | 2016-12-01 | 2019-04-09 | Kodiak Networks, Inc. | PTX data analytic engine notifying group list of detected risk event |
US10341823B2 (en) | 2016-12-30 | 2019-07-02 | Kodiak Networks Inc. | System and method for direct mode push to talk communication protocols |
US10362535B2 (en) | 2016-04-22 | 2019-07-23 | Kodiak Networks, Inc. | System and method for push-to-talk (PTT) key one-touch calling |
US10362074B2 (en) | 2015-02-03 | 2019-07-23 | Kodiak Networks, Inc | Session management and notification mechanisms for push-to-talk (PTT) |
US10367863B2 (en) | 2004-11-23 | 2019-07-30 | Kodiak Networks Inc. | Method for providing dynamic quality of service for push-to-talk service |
WO2019173429A1 (en) | 2018-03-06 | 2019-09-12 | Mutualink, Inc. | Implementing push-to-talk in a multimedia conferencing system |
US10555370B2 (en) | 2016-09-28 | 2020-02-04 | Kodiak Networks, Inc. | System and method for push-to-talk (PTT) in high latency networks |
US10609138B2 (en) | 2015-05-07 | 2020-03-31 | Kodiak Networks Inc. | System and method for mobile data synchronization |
US10630529B2 (en) | 2016-12-29 | 2020-04-21 | Kodiak Networks, Inc. | System and method for push-to-talk (PTT) in mobile edge computing (MEC) |
US10630742B2 (en) | 2015-10-23 | 2020-04-21 | Kodiak Networks, Inc. | System and method for content messaging |
US10750327B2 (en) | 2004-11-23 | 2020-08-18 | Kodiak Networks Inc | Method for multiplexing media streams to optimize network resource usage for push-to-talk-over-cellular service |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9137646B2 (en) | 2004-11-23 | 2015-09-15 | Kodiak Networks, Inc. | Method and framework to detect service users in an insufficient wireless radio coverage network and to improve a service delivery experience by guaranteed presence |
US8958348B2 (en) | 2008-10-20 | 2015-02-17 | Kodiak Networks, Inc. | Hybrid push-to-talk for mobile phone networks |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6404746B1 (en) * | 1999-07-13 | 2002-06-11 | Intervoice Limited Partnership | System and method for packet network media redirection |
US6982961B2 (en) * | 2001-07-19 | 2006-01-03 | Telefonaktiebolaget Lm Ericsson (Publ) | Push-to-talk and push-to-conference in a CDMA wireless communications system |
US7043266B2 (en) * | 2002-02-04 | 2006-05-09 | Sprint Spectrum L.P. | Method and system for selectively reducing call-setup latency through management of paging frequency |
US8411594B2 (en) * | 2002-09-20 | 2013-04-02 | Qualcomm Incorporated | Communication manager for providing multimedia in a group communication network |
-
2004
- 2004-07-16 WO PCT/US2004/023038 patent/WO2005009006A2/en active Application Filing
Non-Patent Citations (1)
Title |
---|
See references of EP1649706A4 * |
Cited By (42)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7787896B2 (en) | 2002-05-24 | 2010-08-31 | Kodiak Networks, Inc. | Dispatch service architecture framework |
US7764950B2 (en) | 2002-05-24 | 2010-07-27 | Kodiak Networks, Inc. | Advanced voice services architecture framework |
US7403775B2 (en) | 2002-05-24 | 2008-07-22 | Kodiak Networks, Inc. | Roaming gateway for support of advanced voice services while roaming in wireless communications systems |
US7738896B2 (en) | 2002-05-24 | 2010-06-15 | Kodiak Networks, Inc. | Subscriber identity module (SIM) enabling advanced voice services (AVS) including push-to-talk, push-to-conference and push-to-message on wireless handsets and networks |
US7529557B2 (en) | 2002-05-24 | 2009-05-05 | Kodiak Networks, Inc. | Press-to-connect for wireless communications systems |
US7738892B2 (en) | 2002-05-24 | 2010-06-15 | Kodiak Networks, Inc. | Architecture, client specification and application programming interface (API) for supporting advanced voice services (AVS) including push to talk on wireless handsets and networks |
US10111055B2 (en) | 2004-11-23 | 2018-10-23 | Kodiak Networks, Inc. | Optimized methods for large group calling using unicast and multicast transport bearer for PoC |
US10178513B2 (en) | 2004-11-23 | 2019-01-08 | Kodiak Networks, Inc. | Relay-mode and direct-mode operations for push-to-talk-over-cellular (PoC) using WiFi-technologies |
US10750327B2 (en) | 2004-11-23 | 2020-08-18 | Kodiak Networks Inc | Method for multiplexing media streams to optimize network resource usage for push-to-talk-over-cellular service |
US10057105B2 (en) | 2004-11-23 | 2018-08-21 | Kodiak Networks, Inc. | Architecture framework to realize push-to-X services using cloudbased storage services |
US10116691B2 (en) | 2004-11-23 | 2018-10-30 | Kodiak Networks, Inc. | VoIP denial-of-service protection mechanisms from attack |
US10367863B2 (en) | 2004-11-23 | 2019-07-30 | Kodiak Networks Inc. | Method for providing dynamic quality of service for push-to-talk service |
US9775179B2 (en) | 2004-11-23 | 2017-09-26 | Kodiak Networks, Inc. | Method to achieve a fully acknowledged mode communication (FAMC) in push-to-talk over cellular (PoC) |
US7813722B2 (en) | 2005-02-18 | 2010-10-12 | Kodiak Networks, Inc. | Enhanced features in an advanced voice services (AVS) framework for wireless communications systems |
US7689238B2 (en) | 2005-08-03 | 2010-03-30 | Kodiak Networks, Inc. | Architecture and implementation of closed user groups and limiting mobility in wireless networks |
US8036692B2 (en) | 2005-08-08 | 2011-10-11 | Kodiaks Networks, Inc. | Brew platform enabling advanced voice services (AVS) including push-to-talk, push-to-conference and push-to-message on wireless handsets and networks |
WO2007048671A1 (en) * | 2005-10-24 | 2007-05-03 | Nokia Siemens Networks Gmbh & Co. Kg | Communication network and communication method in a communication network |
EP2008192A4 (en) * | 2006-04-07 | 2017-03-22 | Cisco Technology, Inc. | System and method for dynamically upgrading/downgrading a conference session |
WO2007126642A2 (en) | 2006-04-07 | 2007-11-08 | Cisco Technology, Inc. | System and method for dynamically upgrading/downgrading a conference session |
US7853279B2 (en) | 2006-04-26 | 2010-12-14 | Kodiak Networks, Inc. | Advanced features on a real-time exchange system |
WO2009053871A1 (en) * | 2007-10-25 | 2009-04-30 | Koninklijke Philips Electronics N.V. | Communications service |
US8676189B2 (en) | 2008-01-24 | 2014-03-18 | Kodiak Networks, Inc. | Converged mobile-web communications solution |
US8670760B2 (en) | 2008-01-24 | 2014-03-11 | Kodiak Networks, Inc. | Converged mobile-web communications solution |
US8498660B2 (en) | 2009-03-30 | 2013-07-30 | Kodiak Networks, Inc. | Enhanced group calling features for connected portfolio services in a wireless communications network |
US8369829B2 (en) | 2010-03-03 | 2013-02-05 | Kodiak Networks, Inc. | Prepaid billing solutions for push-to-talk in a wireless communications network |
US9913300B2 (en) | 2011-12-14 | 2018-03-06 | Kodiak Networks, Inc. | Push-to-talk-over-cellular (PoC) |
US9088876B2 (en) | 2012-02-01 | 2015-07-21 | Kodiak Networks, Inc. | WiFi interworking solutions for push-to-talk-over-cellular (PoC) |
US9961514B2 (en) | 2013-07-23 | 2018-05-01 | Kodiak Networks, Inc. | Effective presence for push-to-talk-over-cellular (PoC) networks |
US10362074B2 (en) | 2015-02-03 | 2019-07-23 | Kodiak Networks, Inc | Session management and notification mechanisms for push-to-talk (PTT) |
US10609138B2 (en) | 2015-05-07 | 2020-03-31 | Kodiak Networks Inc. | System and method for mobile data synchronization |
US10110342B2 (en) | 2015-10-06 | 2018-10-23 | Kodiak Networks Inc. | System and method for tuning PTT over LTE according to QoS parameters |
US10218460B2 (en) | 2015-10-06 | 2019-02-26 | Kodiak Networks, Inc. | System and method for improved push-to-talk communication performance |
US10230777B2 (en) | 2015-10-06 | 2019-03-12 | Kodiak Networks Inc. | System and method for media encoding scheme (MES) selection |
US10129307B2 (en) | 2015-10-06 | 2018-11-13 | Kodiak Networks Inc. | PTT network with radio condition aware media packet aggregation scheme |
US10630742B2 (en) | 2015-10-23 | 2020-04-21 | Kodiak Networks, Inc. | System and method for content messaging |
US10362535B2 (en) | 2016-04-22 | 2019-07-23 | Kodiak Networks, Inc. | System and method for push-to-talk (PTT) key one-touch calling |
US10555370B2 (en) | 2016-09-28 | 2020-02-04 | Kodiak Networks, Inc. | System and method for push-to-talk (PTT) in high latency networks |
US10257669B2 (en) | 2016-12-01 | 2019-04-09 | Kodiak Networks, Inc. | PTX data analytic engine notifying group list of detected risk event |
US10630529B2 (en) | 2016-12-29 | 2020-04-21 | Kodiak Networks, Inc. | System and method for push-to-talk (PTT) in mobile edge computing (MEC) |
US10341823B2 (en) | 2016-12-30 | 2019-07-02 | Kodiak Networks Inc. | System and method for direct mode push to talk communication protocols |
WO2019173429A1 (en) | 2018-03-06 | 2019-09-12 | Mutualink, Inc. | Implementing push-to-talk in a multimedia conferencing system |
EP3763104A4 (en) * | 2018-03-06 | 2021-11-17 | Mutualink, Inc. | Implementing push-to-talk in a multimedia conferencing system |
Also Published As
Publication number | Publication date |
---|---|
WO2005009006A3 (en) | 2005-04-21 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20060189337A1 (en) | Premium voice services for wireless communications systems | |
WO2005009006A2 (en) | Premium voice services for wireless communications systems | |
US7853279B2 (en) | Advanced features on a real-time exchange system | |
US8498660B2 (en) | Enhanced group calling features for connected portfolio services in a wireless communications network | |
US7738896B2 (en) | Subscriber identity module (SIM) enabling advanced voice services (AVS) including push-to-talk, push-to-conference and push-to-message on wireless handsets and networks | |
US20090149167A1 (en) | Connected portfolio services for a wireless communications network | |
US8369829B2 (en) | Prepaid billing solutions for push-to-talk in a wireless communications network | |
US8958348B2 (en) | Hybrid push-to-talk for mobile phone networks | |
JP4384595B2 (en) | Dispatch service architecture framework | |
US7738892B2 (en) | Architecture, client specification and application programming interface (API) for supporting advanced voice services (AVS) including push to talk on wireless handsets and networks | |
US8478261B2 (en) | Predictive wakeup for push-to-talk-over-cellular (POC) call setup optimizations | |
US20080064364A1 (en) | Emergency group calling across multiple wireless networks | |
US20060030347A1 (en) | Virtual push to talk (PTT) and push to share (PTS) for wireless communications systems | |
US20110183659A1 (en) | Community group client and community auto discovery solutions in a wireless communications network | |
WO2006105287A2 (en) | Advanced voice services using an ussd interface | |
WO2005117474A1 (en) | Subscriber identity module (sim) enabling advanced voice services (avs) including push-to-talk, push-to-conference and push-to-message on wireless handsets and networks | |
CA2567041A1 (en) | Architecture, client specification and application programming interface (api) for supporting advanced voice services (avs) including push to talk on wireless handsets and networks | |
EP1769647A1 (en) | Subscriber identity module (sim) enabling advanced voice services (avs) including push-to-talk, push-to-conference and push-to-message on wireless handsets and networks |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A2 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SY TJ TM TN TR TT TZ UA UG UZ VC VN YU ZA ZM ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A2 Designated state(s): BW GH GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
WWE | Wipo information: entry into national phase |
Ref document number: 11158527 Country of ref document: US |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2006189337 Country of ref document: US Ref document number: 10564903 Country of ref document: US |
|
WWP | Wipo information: published in national office |
Ref document number: 11158527 Country of ref document: US |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2004778507 Country of ref document: EP |
|
WWP | Wipo information: published in national office |
Ref document number: 2004778507 Country of ref document: EP |
|
WWP | Wipo information: published in national office |
Ref document number: 10564903 Country of ref document: US |