Abstract: A method includes a first computing entity receiving a request for first data from an affiliated source device by a user device. When a re-encryption key of the user device is not based on a key pair of the first computing entity the method further includes decrypting the first encrypted data using a private key of the first computing entity and encrypting the recovered first data with a public key of a second computing entity to produce second encrypted data. The method further includes encrypting the second encrypted data with the re-encryption key of the user device to produce double encrypted data. The method further includes sending the double encrypted data to the user device, where the user device is capable of decrypting the double encrypted data to recover the first data using a private key of the user device based on a key pair of the second computing entity.

Abstract: A method includes a first computing entity editing an entry in a first copy of a common responsibility list of a proprietary network, where the entry includes information regarding the first computing entity's service responsibility for a first user computing device. The method further includes the first computing entity sending at least the edited entry to other computing entities. The method further includes the first computing entity receiving at least a second edited entry from a second computing entity. The method further includes the first computing entity updating the first copy of the common responsibility list with the at least the second edited entry.

Abstract: A method includes receiving, via a core network in accordance with a regional data routing plan, an affiliation request from a data source device based on a first level regional affiliation of the data source device and a first computing entity. The method further includes determining whether a second level regional affiliation is substantially equal to the first level regional affiliation. When the second level regional affiliation is not substantially equal to the first level regional affiliation, the method further includes identifying a second computing entity based on the second level regional affiliation and sending a notification message to the second computing entity regarding the data source device being affiliated with the second computing entity. The method further includes broadcasting a gateway message to the core network to change the regional data routing plan such that data from the data source device is routed to the second computing entity.

Abstract: A method includes a source computing device receiving an actual transmission time of a previous data message sent from the source computing device to a target computing device. When the actual transmission time is within a timing tolerance of a desired transmission time, the method further includes setting a transmission change indicator for a next data message to no-change. When the actual transmission time is greater than the timing tolerance plus the desired transmission time, the method further includes and setting the transmission change indicator to increase transmission speed. When the actual transmission time is less than the desired transmission time minus the timing tolerance, the method further includes setting the transmission change indicator to decrease transmission speed.

Abstract: A method includes receiving, via a core network in accordance with a regional data routing plan, an affiliation request from a data source device based on a first level regional affiliation of the data source device and a first computing entity. The method further includes determining whether a second level regional affiliation is substantially equal to the first level regional affiliation. When the second level regional affiliation is not substantially equal to the first level regional affiliation, the method further includes identifying a second computing entity based on the second level regional affiliation and sending a notification message to the second computing entity regarding the data source device being affiliated with the second computing entity. The method further includes broadcasting a gateway message to the core network to change the regional data routing plan such that data from the data source device is routed to the second computing entity.

Abstract: A method includes a first computing entity editing an entry in a first copy of a common responsibility list of a proprietary network, where the entry includes information regarding the first computing entity's service responsibility for a first user computing device. The method further includes the first computing entity sending at least the edited entry to other computing entities. The method further includes the first computing entity receiving at least a second edited entry from a second computing entity. The method further includes the first computing entity updating the first copy of the common responsibility list with the at least the second edited entry.

Abstract: A method includes a source computing device receiving an actual transmission time of a previous data message sent from the source computing device to a target computing device. When the actual transmission time is within a timing tolerance of a desired transmission time, the method further includes setting a transmission change indicator for a next data message to no-change. When the actual transmission time is greater than the timing tolerance plus the desired transmission time, the method further includes and setting the transmission change indicator to increase transmission speed. When the actual transmission time is less than the desired transmission time minus the timing tolerance, the method further includes setting the transmission change indicator to decrease transmission speed.

Abstract: A method includes a first computing entity receiving a request for first data from an affiliated source device by a user device. When a re-encryption key of the user device is not based on a key pair of the first computing entity the method further includes decrypting the first encrypted data using a private key of the first computing entity and encrypting the recovered first data with a public key of a second computing entity to produce second encrypted data. The method further includes encrypting the second encrypted data with the re-encryption key of the user device to produce double encrypted data. The method further includes sending the double encrypted data to the user device, where the user device is capable of decrypting the double encrypted data to recover the first data using a private key of the user device based on a key pair of the second computing entity.

Abstract: A packet non-replicating comparator device for use in a digital simulcast radio communication system generates a single seed copy of a timestamped information data packet (per channel) for transmission to either a multicast capable packet-switched network or to a packet duplicator coupled to a unicast capable packet-switched network. The multicast capability of packet-switched networks is utilized to simplify the hardware and software complexity at the comparator site, by assigning the responsibility for performing simulcast (timestamped) packet replication and distribution (to the appropriate transmitters) to the coupled packet-switched network. As a result, the elimination of the comparator performed function of sourcing multiple (replicated) packets of a seed copy frees up valuable link bandwidth and improves processing capability and makes possible the generation of multiple non-replicated packets corresponding to associated ones of multiple channels by a single comparator device.

Abstract: In a digital multi-channel simulcast system, a redundant centralized timestamping device acts as a simulcast controller for multiple channels simultaneously. All packets within a regional multi-channel system which require simulcast transmission are sent to a central timestamping device which determines the appropriate launch timestamp for each packet and attaches it thereto. The timestamping device is able to support concurrent timestamping sessions for each channel of a multiple channel system and can be dynamically assigned (trunked) to service any given radio channel on a packet by packet, call by call, or less frequent basis.

Abstract: A packet voting server and associated method for performing voting services on multiple radio channels simultaneously and including capability to be dynamically assigned (trunked) to service any given radio channel, for example, on a packet by packet, call by call, or less frequent basis.