T-mobile Usa, Inc.

T-moblle Usa, Inc.

Kirti Krishnan

Paul Bongaarts

Andrew Gapin

Mallika Deshpande

Grant Morgan Castle

Egil Gronstad

Salvador Mendoza

Otto Fonseca Escudero

Christopher Harvey Joul

Hichem Zait

A telecommunication network associated with a wireless telecommunication provider can be configured to use a backup PCRF when a primary PCRF is detected as exhibiting a failure condition. Instead of the backup PCRF synchronizing with the primary PCRF as in a redundancy mode, the backup PCRF receives a copy of messages sent to the primary PCRF and maintains session information independently from the primary PCRF. In some configurations, a node within the call flow, such as a Diameter Routing Agent (DRA) transmits a copy of the message sent to the primary PCRF to the backup PCRF. In this way, the backup PCRF will not receive data from the primary PCRF that may be corrupted. When a routing agent detects a failure condition of the primary PCRF, the routing agent seamlessly transitions to use of the backup PCRF.

Failover to a backup policy and charging rules function (PCRF) node

A telecommunication system can include routing devices, a bearer-management device, and a policy-management device. The bearer-management device can receive a request from a terminal to create a specialized bearer (SB) for a non-audio, non-video media type. The bearer-management device can determine that the request is associated with an authorized user, and then send a setup message comprising a Quality of Service (QoS) indicator to the policy-management device. The policy-management device can create the SB permitting data exchange between the terminal and a routing device. The SB can have QoS characteristics associated with the QoS indicator. In some examples, the terminal can receive a network address, determine an associated network port, and send a SIP INVITE message indicating the non-audio, non-video media type. The terminal can then exchange data on the network port with a peer network terminal.

Latency-sensitive network-traffic quality of service

A telecommunication system can include routing devices, a Quality of Service (QoS) controller, a policy-management device, and a flow-management device. The QoS controller or flow-management device can receive a request from a terminal to create a specialized flow (SF), e.g., for a non-audio, non-video media type. If the request is associated with an authorized user, a setup message can be sent comprising a QoS indicator. The system can create the SF permitting data exchange between the terminal and a routing device. The SF can have QoS characteristics associated with the QoS indicator. In some examples, the terminal can receive network-address information, determine an associated network resource, and send a flow-request message indicating a non-audio, non-video media type. The terminal can then exchange data on the network port with a peer network terminal.

QoS for latency-sensitive network-traffic flows

Growing community of inventors

Sammamish, WA, United States of America

Kirti Krishnan