This description relates to signaling for push to talk.
A Push-To-Talk (PTT) feature on mobile phones allows a mobile phone to be used as a digital two-way radio. By pressing and holding a PTT button, a user can talk while one or more other uses can listen. PTT connects mobile phone users with each other within seconds and bypasses the call setup time delay required for normal phone dialing. PTT provides a half-duplex communication mode controlled by a button used to switch between voice transmission mode and voice reception mode.
PTT may be implemented to operate over a realization of a EV-DO Rev A standard (also written as 1xEV-DO Rev A or 1x Evolution-Data Optimized Revision A) or another similarly capable standard. EV-DO Rev A is a part of a family of standards by 3GPP2.
The 1xEV-DO protocol is an EVolution of the 1xRTT standard for high-speed data-only (DO) services and has been standardized by the Telecommunication Industry Association (TIA) as TIA/ELA/IS-856, “CDMA2000 High Rate Packet Data Air Interface Specification”, 3GPP2 C.S0024-0, Version 4.0, Oct. 25, 2002, which is incorporated herein by reference. Revision A to this specification has been published as TIA/EIA/IS-856, “CDMA2000 High Rate Packet Data Air Interface Specification”, 3GPP2 C.S0024-A, Version 2.0, June 2005, which is also incorporated herein by reference.
Some implementations of PTT use an EV-DO Rev A messaging method called DataOverSignaling (DoS) to reduce the latency of push to beep, the time from when the caller pushes the PTT button to when the caller is granted the floor, (i.e., can begin speaking, also called “push to beep” latency). Data Over Signaling in EV-DO Rev-A is a mechanism to transmit “data packets” (i.e., packets whose contents are destined for higher-layer protocols) over a “control channel”. The control channel is an always-on link that is traditionally used to carry EV-DO signaling messages. When a user wishes to make a PTT call, the network sends a series of setup-messages between a handset (also referred to as an Access Terminal or AT) and various EV-DO network structures. These structures include Radio Access Networks (Access Network or AN), which are a portion of a mobile phone network that relates to the transmission between an AT and a network Base Station (BS), and Radio Network Controllers (RNC), which work with the BS to act as a link between the wireless devices (e.g. AT) and the Internet. DoS messages are passed between these devices to establish a link between the caller and the receivers.
When a user presses the PTT button on the AT to establish a connection, a message is sent from the AT to a PTT server located on a modem card of a BS. The PTT server then sends the message to an RNC to locate the target ATs. The message carries information designating the target AT. It then becomes the job of the RNC to locate the target ATs and properly establish the necessary link for a PTT connection.
The AN locates the AT by sending a small EV-DO specific signaling message, called the “page” message, over the always-on signaling control channel. The always-on signaling control channel connects the AN to sectors distributed over a geographic area where the AT is presumably located. The page message for a specific AT is sent at one or more specific times. These specific times are pre-agreed between each individual AT and the access network. At these pre-assigned times, the AT switches on its receive function and listens for messages addressed to itself. If the AT receives the page message, the AT then establishes an EV-DO connection with the RAN, over which it can receive user traffic.
Establishing such connections takes time. A long connection time detrimentally affects end-to-end “Push To Beep” time and negatively affects the user-experience.
In establishing the PTT link, some DoS messages are Session Initiation Protocol (SIP) invitations or acknowledgements (SIP INVITES/OK) for Mobile-Originated PTT (MO PTT) calls and Mobile-Terminated PTT (MT PTT) calls. In order to send the PTT message to the AT faster than would be possible with the traditional mechanism described earlier, the RAN has to send the PTT initiation message as a DOS message over the control channel, along with the page message. An AT that needs to send a PTT initiation message can also send it before a connection has been set up, by sending the message as a DOS message over a low rate access channel that exists in the network prior to traffic channel creation to speed up PTT call initiation. Call set-up messages (e.g. SIP INVITE) can be sent over the access channel, allowing for fast initiation of PTT calls. Without this mechanism, each PTT call would have to begin with the establishment of a traffic channel, and this would lead to long set-up times.
While a delay of several seconds in connecting to a server may not be noticeable to some applications, the delay may be noticeable for real-time applications such as voice and PTT. When not active, typical cellular handsets may reduce power usage by entering a sleep mode that may last as long as five seconds between awake states. This increases the latency for call set-up for PTT calls. EV-DO Rev A reduces the latency with the introduction of an Enhanced Idle State Protocol (EISP) that allows shorter sleep periods to speed up call establishment. Enhanced Idle State Protocol supports faster, variable paging.
In using DoS messaging for PTT, a typical vendor could bundle a forward link DoS message (encapsulating a SIP invite) along with a Page message. The forward link DoS message links a fixed location such as a radio node (RN) to a mobile user. A Page message is a message transmitting the ID of another device in order to establish connection with that device. Because the Page message is carried as a part of a synchronous sleep state (synSS) capsule sent on the control channel, the DoS message will also be transported in synSS. If the recipient AT is located in a sector, a network topology subdivision, the recipient AT will receive the DoS message along with the Page message. Typically, using the DoS message, a Page message is flooded to all sectors on a subnet.
For a typical IP_based push-to-talk system, even the smallest message would be 50-60 bytes in length. Commonly used SIP-based push-to-talk systems have messages that are hundreds of bytes long. Special SIP compression techniques are used to limit the initial “invite” messages to a size of less than 120 bytes. For a system that has 300 sectors in a subnet, and a modest PTT load, the control channel capacity (which is defined to be 6 DoS messages/sector/CC cycle at 76.8 Kbps) will constrain the maximum average number of PTT subscribers supported per sector, the average push to beep latency, and a limited maximum average simultaneous PTT calls per sector.
In general, in some aspects of the invention, in response to an attempt by an access terminal on a sector of a wireless network to access a service of the wireless network, a data over signaling message that identifies a recipient access terminal is transmitted from a radio network controller to the sector. The data over signaling message can be buffered until a determined time has lapsed. A unicast access terminal identifier of the data over signaling message can be used to sort the data over signaling message with respect to other data over signaling messages based on. The data over signaling message can be transmitted in an asynchronous capsule. The data over signaling message can be buffered until the access terminal attempts to access a service of the wireless network. The buffering can be performed in a base station and/or in the radio network controller. The data over signaling message can be transmitted to the recipient access terminal. The service of the wireless network can comprise a push to talk service. The data over signaling message can be used to establish a push to talk communication. The attempt by the access terminal can be in response to a second message. The second message can comprise a paging message. The data over signaling method can comprise a DoS message of EV-DO Rev. A protocol.
The method can further comprise transmitting a page message from a radio network controller to the sector. The data over signaling message can be transmitted in a synchronous capsule. The synchronous capsule can be transmitted outside of a sleep state. The synchronous capsule can be transmitted in a determined paging cycle. The page message can be transmitted in a synchronous sleep state capsule. The data over signaling message can be used to establish a push to talk communication.
In some aspects of the invention, managing a data over signaling message transport facility for a push to talk service is based on at least one of a measure of a forward link slot utilization or a measure of pending data over signaling messages. The measure of forward link slot utilization can be compared to a first configurable threshold value, the pending data over signaling messages metric is compared to a second configurable threshold value, and the first and the second configurable threshold values have different effects on the push to talk service The pending data over signaling messages metric can comprise the number of pending data over signaling messages. The comparison can be carried out on at least one of a radio network controller, or a base station. The managing can be carried out on at least one of a radio network controller, or a base station. The managing can comprise activating the message transport facility. The managing can comprise enabling the message transport facility.
In some aspects of the invention, a signaling link protocol priority is assigned to a message to enable quality of service support. The service can comprise a push to talk service. The priority can be based on a user quality of service level. The message can comprise at least one of a data over signaling acknowledgement message, or a data over signaling message. The quality of service can comprise an inter user quality of service. Different user categories can be associated with different messages. Different messages can be assigned different priorities.
In some aspects of the invention, an apparatus is disclosed comprising a means for providing, in response to an attempt by an access terminal on a sector of a wireless network to access a service of the wireless network, a transmission, from a radio network controller to the sector, of a data over signaling message that identifies a recipient access terminal. The data over signaling message can be transmitted in an asynchronous capsule. The data over signaling message can be buffered until the access terminal attempts to access a service of the wireless network.
In some aspects of the invention, a data over signaling message identifies a recipient access terminal and is transmitted from a radio network controller to a sector in response to an attempt by an access terminal on the sector of a wireless network to access a service of the wireless network. The data over signaling message can be transmitted in an asynchronous capsule. The data over signaling message can be buffered until the access terminal attempts to access a service of the wireless network.
In some aspects of the invention, an apparatus is disclosed comprising a means for providing, in response to an attempt by an access terminal on a sector of a wireless network to access a service of the wireless network, a transmission, from a radio network controller to the sector, of a page message and of a data over signaling message, the data over signaling message identifying a recipient access terminal. At least one of the page message or the data over signaling message can be transmitted in an asynchronous capsule. At least one of the page message or the data over signaling message can be buffered until the access terminal attempts to access a service of the wireless network.
In some aspects of the invention, a page message and a data over signaling message is disclosed comprising the data over signaling message identifying a recipient access terminal, and the data over signaling message transmitted from a radio network controller to a sector in response to an attempt by an access terminal on the sector of a wireless network to access a service of the wireless network. At least one of the page message or the data over signaling message can be transmitted in an asynchronous capsule. At least one of the page message or the data over signaling message can be buffered until the access terminal attempts to access a service of the wireless network.
In some aspects of the invention, a machine-readable medium is disclosed comprising including machine-executable instructions to cause the machine to dynamically optimize data over signaling message transport using at least one of a forward link slot utilization metric, or a pending data over signaling messages metric. The measure of forward link slot utilization can be compared to a first configurable threshold value, the pending data over signaling messages metric can be compared to a second configurable threshold value, and the first and the second configurable threshold values can have different effects on the push to talk service The optimizing can comprise activating the message transport facility. The optimizing can comprise enabling the message transport facility.
In some aspects of the invention, a machine-readable medium is disclosed comprising including machine-executable instructions to cause the machine to assign a signaling link protocol priority to a message to enable quality of service support. The message can comprise at least one of a data over signaling acknowledgement message, or a data over signaling message. The quality of service can comprise an inter user quality of service. The different messages can be assigned different priorities.
In some aspects of the invention, in response to an attempt by a recipient access terminal on a sector of a wireless network to access a service of the wireless network, a data over signaling message that identifies the recipient access terminal receives from at least one of a radio network controller or a base station. The data over signaling message can be transmitted in an asynchronous capsule. The page message can receive from at least one of a radio network controller or a base station. The page message and the data over signaling message may or may not be received back-to-back.
Among the advantages of the techniques described here are one or more of the following.
Because the DoS message is not bundled with the Page message, control channel capacity wastage is reduced by a factor of 1/NumberOfSectorsInSubnet, and the average delay for DoS messages for ATs in a given sector is reduced. Thus, more PTT subscribers are supported per sector.
Push to beep latency is reduced, because typically only one or two DoS messages will be transmitted per sector per control channel cycle.
Forward link sector capacity (and hence number of simultaneous PTT calls per sector) is increased, because the number of forward slots required per control channel cycle @76.8 Kbps for transmitting DoS is reduced to typically 8 from 56, i.e., almost by a factor of 1/MaxDoSMessagesPerSectorPerCCCycle
Battery life is extended for all ATs in a Rev-A sector, because of the smaller sleep state capsules.
Inter-user QoS support results in better average delays for high priority user.
Table 1 summarizes the sector throughput and average delay gain for the proposed method as compared to a Page message bundling approach.
Other features and advantages will be apparent from the description and the claims.
Referring to
Upon receiving the DoS message 14 from the PTT server 22, the RNC 28, which defines and serves a subnet 30, sends a Page+DoS message 32 (
The DoS message 14, 40, 44 is identifiable by a Unicast Access Terminal Identifier 13, 39, 43 (UATI). The UATI is a 128-bit address identifier for a High Rate Packet Data (HRPD) device. A 32-bit short version is available for transmission. When the RNC 28 forwards the DoS message 40 to the buffers 42 of the various BS's 26, the DoS message 44 is compiled with any other unexpired DoS messages 50. The compilation is sorted based on the UATI of each message. During the period the DoS message 44, 50 exists in the buffer 42, the message 44, 50 waits for an access attempt from a recipient ATs 24.
However, not all ATs contacting the BS 26 will receive the DoS message 14, 40, 44. When a recipient AT 24 attempts access but before the BS 26 sends an AcAck 54 to the AT 24, the BS 26 checks for any pending DoS 44, 50 message in the sector's 34 DoS buffer 42. The AcAck message 54 is a message sent from the BS 26 to the AT 24 confirming the location registration. If a pending DoS message 44, 50 designated for that AT 24 is found, the DoS message 44, 50 is bundled with the AcAck 54 and is transmitted in an asynchronous capsule 56 (async capsule). By capsule, we mean a data structure that may enclose one or more records such as a message. The async capsule 56 is locally constructed on the base station 26 to transmit the DoS message 44, 50. Upon receiving the AcAck 54, the receiving AT 24 sends to the BS 26 (and subsequently the RNC 28) a DoSAck 58 message acknowledging the receipt of the DoS message 44, 50 thereby establishing the connection. A non-recipient AT 60 contacting the BS 26 would not receive the DoS message 44, 50 because the DoS message 44, 50 is not designated for that non-recipient AT 60.
Referring to
In the optimized DoS message transport 72, The RNC 28 sends a Page+DoS( ) message 32 to the CCHMO 78. The Page+DoS( ) message 32 is a back-to-back transmission of a Page message 38 followed by a DoS message 40. The CCHMO 78 separates the Page+DoS( ) message 32 into the Page( ) message 38 and the DoS( ) message 40. The CCHMO 78 retains the DoS( ) message 40 and forwards the Page( ) message 38 to the recipient AT 24. The Page( ) message 38 contains an AT identifier so that the AT 24 knows that it is being paged. The DoS( ) message 44 is placed in the buffer 42 and a timer 46 is started. The timer 46 enables a timeout based flushing. A control channel cycle counter (not shown) is initialized to an initial value (such as 0 or 1) and is incremented every control channel cycle (not shown). Upon reaching a configurable (hard-coded) threshold (not shown), the DoS messages 44 is cleared from the buffer 42.
To reduce the total bandwidth required to establish the PTT Link 70, the CCHMO 78 buffers the DoS message 44 and sends the Page( ) message 38 to the recipient AT 24. Upon receiving the Page( ) message 38, the recipient AT 24 responds to the Page( ) message 38, and thereby identifying itself, by sending an AccessCapsule( ) message 48 to the ACHMO 74. The AccessCapsule( ) message 48 contains two messages, a ConnectionRequest message and a RouteUpdate message. The RouteUpdate message contains information about the strength of base station signals as detected by the AT 24. The base station with the strongest signal is most likely to provide service to the AT 24. This response is the recipient AT's 24 response to acknowledging the Page( ) message 38. Upon receiving the AccessCapsule( ) message 48, the ACHMO 74 sends an Access Acknowledge message 82 (sendAcAck( ) message) to the COMCH 76. The COMCH 76 forwards the received sendAcAck( ) message 82 to CCHMO 78.
Receiving the sendAcAck( ) message 82 from the COMCH 76 signals to the CCHMO 78 that the Page( ) message 38 was acknowledged by the intended recipient AT 24 and that an AccessCapsule( ) message 48 was sent from the recipient AT 24. This allows the CCHMO 78 to initiate the process of sending the DoS( ) message 40 to the recipient AT 24.
First, the CCHMO 78 removes the timer 46 to avoid timeout based flushing since the intended recipient AT 24 has been located successfully. Next, the CCHMO 78 sends an Inter-DoS Communication Method message 84 (DoSITC) to the OCM 80. The DoSITC( ) message 84 is a local message containing the DoS( ) message 40. The OCM 80 responds to the DoSITC( ) message 84 by parsing the DoS( ) message 40 from the DoSITC( ) message 84 and sending the DoS( ) message 40 to the CCHMO 78. The CCHMO sends the DoS( ) message 40 from the OCM 80 to the recipient AT 24. Upon receiving the DoS( ) message 40, the recipient AT completes the PTT link 70 by sending the DoSAck( ) 58 to the ACHMO 74 and the ACHMO 74 forwards the DoSAck( ) 58 to the RNC 28. The DoSAck( ) message 58 is optional and is requested by the sender.
A configurable parameter per sector, such as a DoS optimization switch, enables this improved transport. By changing the parameters of respective sectors, various levels of efficiencies are achieved. For example, changing the timer 46 affects the maximum allowed time before the network considers the recipient AT 24 undetected. Changing the timer 46 also affects the number of pages sent prior to timeout. With a longer timeout, less bandwidth is available for other pages and fewer average simultaneous PTT calls per sector are supported.
Referring to
As in the improved transport, the Page+DoS( ) message 32 is send from the RNC 28 to the CCHMO 78 and the CCHMO 78 parses the Page+DoS( ) message 32 into the Page( ) message 38 and the DoS( ) message 40. However, instead of buffering the DoS( ) message 40, the Page( ) message 38 is sent in a synchronous sleep state capsule 112 (synSS capsule) and the DoS( ) message 40 is sent in a synchronous capsule 114 (syn capsule) in an appropriate paging cycle 116. Unlike the synSS capsule 112, the syn capsule 114 occurs outside the sleep state. Both the Page( ) message 38 and the Dos( ) message 40 originate from the CCHMO 78 and is directed to the recipient AT 24. When the recipient AT 24 receives both messages, the AT 24 sends an AccessCapsule+DosAck( ) 120 message to the ACHMO 74. The ACHMO 74 then forwards the AccessCapsule+DosAck( ) 120 message to the RNC 28, thereby establishing the PTT Link 70.
This approach reduces total wait time prior to timing out. However, the total bandwidth usage is higher because the DoS( ) message 40 is sent to all AT's 24, 60 thereby increasing the total bandwidth usage and reducing the average simultaneous PTT calls per sector.
Referring to
The timer 46 enables a timeout based flushing. A control channel cycle counter (not shown) is initialized to an initial value (such as 0 or 1) and is incremented every control channel cycle (not shown). Upon reaching a configurable (hard-coded) threshold (not shown), the DoS messages 44 is cleared from the buffer 42 in the RNC.
This approach has the advantages of conserving RNC 28 to BS 26 bandwidth and of retaining DoS messaging control at the RNC level. However, the timer's 46 timing parameters will require adjustment because the recipient AT access attempts are detected at a higher level in the hierarchy. More processing resources is required of the RNC 28 in this approach because the RNC 28 is now handling the processing and buffering/caching, both of which was previously handled by the BS 26.
In some embodiments, the optimized DoS message transport 72 is dynamically enabled. The pending DoS messages 44, 50 in the buffer 42 are compared to a configurable threshold. The forward link slot utilization is compared to a second configurable threshold. If the number of pending DoS messages 44, 50 in the buffer is less than the configurable threshold, or if the forward link slot utilization is below the second configurable threshold, the optimization is automatically enabled. Depending on the implementation, the RNC 28 and/or the BS 26 can carry out the comparisons and optimization.
In some embodiments, an Inter user Quality of Service (QoS) support is added by assigning different Signaling Link Protocol (SLP) priorities (e.g. 20, 30, 40, 50) to DoSAck 58 and DoS messages 44 for different users (e.g. Gold, Silver and Bronze users). The Signaling Link Protocol (SLP) is used for reliable transfer of a signaling message, which is prioritized to support QoS. The DoSAck messages 58 are transported in a non-optimized scheme. In constructing the async capsule 34, priority is given to users with better QoS.
Other embodiments are within the scope of the following claims.
Number | Name | Date | Kind |
---|---|---|---|
6711144 | Kim et al. | Mar 2004 | B1 |
6731618 | Chung et al. | May 2004 | B1 |
6741862 | Chung et al. | May 2004 | B2 |
6781999 | Eyuboglu et al. | Aug 2004 | B2 |
7170871 | Eyuboglu et al. | Jan 2007 | B2 |
7200391 | Chung et al. | Apr 2007 | B2 |
7242958 | Chung et al. | Jul 2007 | B2 |
7277446 | Abi-Nassif et al. | Oct 2007 | B1 |
7299278 | Ch'ng | Nov 2007 | B2 |
20020196749 | Eyuboglu et al. | Dec 2002 | A1 |
20030043772 | Mathis et al. | Mar 2003 | A1 |
20030100311 | Chung et al. | May 2003 | A1 |
20040117498 | Hashimoto et al. | Jun 2004 | A1 |
20050078653 | Agashe et al. | Apr 2005 | A1 |
20050213555 | Eyuboglu et al. | Sep 2005 | A1 |
20050243749 | Mehrabanzad et al. | Nov 2005 | A1 |
20050245279 | Mehrabanzad et al. | Nov 2005 | A1 |
20050265277 | Thadasina et al. | Dec 2005 | A1 |
20050288041 | Gill et al. | Dec 2005 | A1 |
20050288049 | Gill et al. | Dec 2005 | A1 |
20060040693 | Yoon et al. | Feb 2006 | A1 |
20060046762 | Yoon et al. | Mar 2006 | A1 |
20060067422 | Chung | Mar 2006 | A1 |
20060067451 | Pollman et al. | Mar 2006 | A1 |
20060126509 | Abi-Nassif | Jun 2006 | A1 |
20060159045 | Ananthaiyer et al. | Jul 2006 | A1 |
20060240782 | Pollman et al. | Oct 2006 | A1 |
20060268871 | Van Zijst | Nov 2006 | A1 |
20060276207 | Harris et al. | Dec 2006 | A1 |
20060291420 | Ng | Dec 2006 | A1 |
20060294241 | Cherian et al. | Dec 2006 | A1 |
20070026884 | Rao | Feb 2007 | A1 |
20070058628 | Rao et al. | Mar 2007 | A1 |
20070077948 | Sharma et al. | Apr 2007 | A1 |
20070097916 | Eyuboglu et al. | May 2007 | A1 |
20070115896 | To et al. | May 2007 | A1 |
20070140172 | Garg et al. | Jun 2007 | A1 |
20070140184 | Garg et al. | Jun 2007 | A1 |
20070140185 | Garg et al. | Jun 2007 | A1 |
20070140218 | Nair et al. | Jun 2007 | A1 |
20070155329 | Mehrabanzad et al. | Jul 2007 | A1 |
20070190963 | Ananthanarayanan et al. | Aug 2007 | A1 |
20070220573 | Chiussi et al. | Sep 2007 | A1 |
20070230419 | Raman et al. | Oct 2007 | A1 |
20070238442 | Mate et al. | Oct 2007 | A1 |
20070238476 | Raman et al. | Oct 2007 | A1 |
20070242648 | Garg et al. | Oct 2007 | A1 |
20070248042 | Harikumar et al. | Oct 2007 | A1 |
20080003988 | Richardson | Jan 2008 | A1 |
20080013488 | Garg et al. | Jan 2008 | A1 |
20080062925 | Mate et al. | Mar 2008 | A1 |
20080065752 | Ch'ng et al. | Mar 2008 | A1 |
20080069020 | Richardson | Mar 2008 | A1 |
20080069028 | Richardson | Mar 2008 | A1 |
20080076398 | Mate et al. | Mar 2008 | A1 |
20080117842 | Rao | May 2008 | A1 |
20080119172 | Rao et al. | May 2008 | A1 |
20080120417 | Harikumar et al. | May 2008 | A1 |
20080139203 | Ng et al. | Jun 2008 | A1 |
20080146232 | Knisely | Jun 2008 | A1 |
20080151843 | Valmikam et al. | Jun 2008 | A1 |
20080159236 | Ch'ng et al. | Jul 2008 | A1 |
20080162924 | Chinitz et al. | Jul 2008 | A1 |
20080162926 | Xiong et al. | Jul 2008 | A1 |
20080253550 | Ch'ng et al. | Oct 2008 | A1 |
20080254792 | Ch'ng | Oct 2008 | A1 |
20090034440 | Samar et al. | Feb 2009 | A1 |
20090082020 | Ch'ng et al. | Mar 2009 | A1 |
20090088155 | Kim | Apr 2009 | A1 |
Number | Date | Country |
---|---|---|
2452688 | Mar 2009 | GB |
Number | Date | Country | |
---|---|---|---|
20070238442 A1 | Oct 2007 | US |