Abstract: A wireless communication system may include an SGW operably coupled to a PGW to setup a session responsive to a request from a terminal to establish the session between the terminal and the PGW. The system further includes an MME configured to authenticate the terminal and provide bearer management in response to the request. The MME is configured to provide bearer information to the SGW. The system also includes base stations operably coupled to the SGW via a data plane connection and operably coupled to the MME via a control plane connection. The base stations are configured to handover connection to the terminal between the base stations in response to movement of the terminal between coverage areas of the base stations.

Abstract: A packet communications network is adapted for efficiently handling of multi-priority traffic (such as multi-media traffic) by defining an access algorithm that not only ensures the requested loss probabilities for both priorities of traffic, but also optimizes the bandwidth required to carry both priority classes. A buffer having a properly sized occupancy threshold admits high priority traffic if there is room in the buffer, but admits lower priority traffic only if the buffer occupancy is below the occupancy threshold. The resulting consolidated multi-priority traffic can then be characterized by an effective bandwidth which increases the packet network capacity substantially. The multi-priority access mechanisms require little or no changes in the prior art access mechanisms and utilize pre-existing leaky bucket, route selection and link metric mechanisms of the prior art.

Abstract: Each network node in a communications network maintains its own copy of the network topology database defining network resources. Each resource record contains a "timer" field which is initially set to a maximum value but which may be decremented on a daily basis. If the timer field is decremented to zero without being reset, the node unilaterally removes the resource record from its copy of the database. The timer field will normally reach zero only for obsolete resource records since each network node responsible for a resource broadcasts a timer-resetting message for the resource (1) each time the resource status changes, (2) when the node first joins or rejoins the network, and (3) on a periodic (weekly) basis regardless of whether conditions (1) or (2) have occurred.