System and method for providing a trunked radio and gateway

• US 8,126,494 B2
• Filed: 12/19/2008
• Issued: 02/28/2012
• Est. Priority Date: 12/19/2008
• Status: Active Grant

• Current Assignee: STA Group, LLC
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Shaffer, Shmuel, Bicknell, David S.
• Primary Examiner(s): Mai, Lam T
• Application Number:
  US12/340,451
• Publication Number:
  US 20100159975A1
• Time in Patent Office: 1,166 Days
• Field of Search: 455/520, 455/461, 455/419, 455/445, 455/518, 455/521, 455/522, 455/426.1, 455/426.2, 455/456.1, 455/456.2, 370/312, 370/328, 370/348, 370/390, 709/223, 379/135, 379/201.01, 379/93.19, 379/93.14, 348/14.01
• US Class Current: 455/520
• CPC Class Codes: H04W 4/10 Push-to-Talk [PTT] or Push-On-Call services
• CPC Class Codes: H04W 76/32 Release of transport tunnels
• CPC Class Codes: H04W 76/45 for Push-to-Talk [PTT] or Push-to-Talk over cellular [PoC] services
• CPC Class Codes: H04W 84/08 Trunked mobile radio systems

Abstract

A method is provided in one example and includes receiving a first channel release notification from a communication network at a trunked radio network gateway connecting one or more trunked radio networks to the communication network. The method also includes determining whether the first channel release notification was generated in response to an initial seizure or a release of a channel in a trunked radio network of the gateway. The method further includes suppressing transmission of a further channel release notification based on data included in the first channel release notification that indicates an origin of the channel seizure or the release causing the first channel release notification to be generated. In more specific embodiments, the data includes parameter values indicating an originating source for the seizure or the release and a responding source generating the channel release notification.

Claims

1. A method, comprising:

receiving a first channel release notification from a gateway;

determining whether the first channel release notification was generated in response to an initial seizure or a release of a channel in a network of the gateway; and

suppressing transmission of a second channel release notification based on data included in the first channel release notification that indicates an origin of the initial seizure or the release causing the first channel release notification to be generated.

2. The method of claim 1, wherein the data includes parameter values indicating an originating source for the initial seizure or the release and a responding source generating the first channel release notification.

3. The method of claim 1, wherein the data further includes a parameter value indicating whether an originating source performed the initial seizure or the release.

4. The method of claim 1, wherein the data includes any one or more of a synchronization source (SSRC) identifier, a contributing source (CSRC) identifier, or a canonical name (CNAME) associated with an element of the network of the gateway.

5. The method of claim 1, wherein the data is read from real-time protocol (RTP) control protocol (RTCP) packets associated with RTP data packets transporting the first channel release notification.

6. The method of claim 1, wherein determining whether the first channel release notification was generated in response to a channel seizure or release in the network of the gateway is based on a history of notification messages involving the gateway.

7. The method of claim 1, further comprising:

storing a table of end-user devices that are part of a virtual talk group (VTG) managed by the gateway.

8. The method of claim 1, wherein the data is embedded in the first channel release notification using stenographic information or bit robbing.

9. An apparatus, comprising:

a gateway configured to;

receive a channel release notification, wherein a determination is made whether the channel release notification was generated in response to an initial seizure or a release of a channel in a network, and wherein a further channel release notification is suppressed based on data included in the channel release notification.

10. The apparatus of claim 9, wherein the data includes parameter values indicating an originating source for the initial seizure or the release.

11. The apparatus of claim 9, wherein the data further includes a parameter value indicating whether an originating source performed the initial or release.

12. The apparatus of claim 9, wherein the data includes any one or more of a synchronization source (SSRC) identifier, a contributing source (CSRC) identifier, or a canonical name (CNAME) associated with an element of the network of the gateway.

13. The apparatus of claim 9, wherein the data is read from real-time protocol (RTP) control protocol (RTCP) packets associated with RTP data packets transporting the channel release notification.

14. The apparatus of claim 9, wherein the gateway stores a table of end-user devices that are part of a virtual talk group (VTG) managed by the gateway.

15. A system, comprising:

means for receiving a first channel release notification;

means for determining whether the first channel release notification was generated in response to an initial seizure or a release of a channel in a network of a gateway; and

means for suppressing transmission of a second channel release notification based on data included in the first channel release notification that indicates an origin of the initial seizure or the release causing the first channel release notification to be generated.

16. The system of claim 15, wherein the data includes parameter values indicating an originating source for the initial seizure or the release and a responding source generating the first channel release notification.

17. The system of claim 15, wherein the data further includes a parameter value indicating whether an originating source performed the initial seizure or release.

18. The system of claim 15, wherein determining whether the first channel release notification was generated in response to a channel seizure or release is based on a history of notification messages involving the gateway.

19. The system of claim 15, further comprising:

means for storing a table of end-user devices that are part of a virtual talk group (VTG) managed by the gateway.

20. Logic encoded in non-transitory media for execution and when executed by a processor operable to:

receive a first channel release notification;

determine whether the first channel release notification was generated in response to an initial seizure or a release of a channel in a network of a gateway; and

suppress transmission of a second channel release notification based on data included in the first channel release notification that indicates an origin of the initial seizure or the release causing the first channel release notification to be generated.

21. The logic of claim 20, wherein the data includes parameter values indicating an originating source for the initial seizure or the release.

22. The logic of claim 20, wherein the data further includes a parameter value indicating whether an originating source performed the initial or release.

23. The logic of claim 20, wherein the data includes any one or more of a synchronization source (SSRC) identifier, a contributing source (CSRC) identifier, or a canonical name (CNAME).

24. The logic of claim 20, wherein determining whether the first channel release notification was generated in response to a channel seizure or release in the network of the gateway is based on a history of notification messages involving the gateway.

25. The logic of claim 20, wherein the logic is further operable to:

store a table of end-user devices that are part of a virtual talk group (VTG) managed by the gateway, and wherein the data is embedded in the first channel release notification using stenographic information or bit robbing.