Abstract:
An example method is provided in one example embodiment and may include receiving an indication of a radio access technology (RAT) change for a user equipment (UE); determining availability of a preferred RAT type for a policy related rule associated with the UE, wherein the policy related rule includes, at least in part, the preferred RAT type for one or more service data flows for the UE; and configuring the one or more service data flows for the UE based, at least in part, on a change in availability of the preferred RAT type following the RAT change. In at least one case, the method can include routing downlink packets to the UE using the one or more service data flows for the preferred RAT type if the preferred RAT type is available.
Abstract:
An example method is provided in one example embodiment and may include receiving an indication of a radio access technology (RAT) change for a user equipment (UE); determining availability of a preferred RAT type for a policy related rule associated with the UE, wherein the policy related rule includes, at least in part, the preferred RAT type for one or more service data flows for the UE; and configuring the one or more service data flows for the UE based, at least in part, on a change in availability of the preferred RAT type following the RAT change. In at least one case, the method can include routing downlink packets to the UE using the one or more service data flows for the preferred RAT type if the preferred RAT type is available.
Abstract:
An example method is provided in one example embodiment and may include receiving an indication of a radio access technology (RAT) change for a user equipment (UE); determining availability of a preferred RAT type for a policy related rule associated with the UE, wherein the policy related rule includes, at least in part, the preferred RAT type for one or more service data flows for the UE; and configuring the one or more service data flows for the UE based, at least in part, on a change in availability of the preferred RAT type following the RAT change. In at least one case, the method can include routing downlink packets to the UE using the one or more service data flows for the preferred RAT type if the preferred RAT type is available.
Abstract:
An example method is provided in one example embodiment and may include receiving a session request for a user equipment (UE) at a node, wherein the session request includes a timestamp for the UE and a retry count; determining if the session request is a stray session request; and maintaining session information for an existing session for the UE at the node if the session request is a stray session request. The method can include identifying the received session request as a stray request if the timestamp received in the request is less than a timestamp stored for an existing session for the UE. The method can also include identifying the received request as a stray request if the timestamp received is equal to the timestamp stored for the existing session and if the retry count received is less than or equal to a retry count stored for the session.
Abstract:
An example method is provided in one example embodiment and may include receiving a session request for a user equipment (UE) at a node, wherein the session request includes a timestamp for the UE and a retry count; determining if the session request is a stray session request; and maintaining session information for an existing session for the UE at the node if the session request is a stray session request. The method can include identifying the received session request as a stray request if the timestamp received in the request is less than a timestamp stored for an existing session for the UE. The method can also include identifying the received request as a stray request if the timestamp received is equal to the timestamp stored for the existing session and if the retry count received is less than or equal to a retry count stored for the session.
Abstract:
An example method is provided in one example embodiment and may include receiving an indication of a radio access technology (RAT) change for a user equipment (UE); determining availability of a preferred RAT type for a policy related rule associated with the UE, wherein the policy related rule includes, at least in part, the preferred RAT type for one or more service data flows for the UE; and configuring the one or more service data flows for the UE based, at least in part, on a change in availability of the preferred RAT type following the RAT change. In at least one case, the method can include routing downlink packets to the UE using the one or more service data flows for the preferred RAT type if the preferred RAT type is available.
Abstract:
An example method is provided in one example embodiment and may include receiving a session request for a user equipment (UE) at a node, wherein the session request includes a timestamp for the UE and a retry count; determining if the session request is a stray session request; and maintaining session information for an existing session for the UE at the node if the session request is a stray session request. The method can include identifying the received session request as a stray request if the timestamp received in the request is less than a timestamp stored for an existing session for the UE. The method can also include identifying the received request as a stray request if the timestamp received is equal to the timestamp stored for the existing session and if the retry count received is less than or equal to a retry count stored for the session.
Abstract:
The present disclosure is directed at systems, methods and media for providing bearer call-back services for bearers that have been rejected or pre-empted by a network apparatus in a core network. In some embodiments, if a network apparatus enters a state in which it becomes necessary to reject or pre-empt a bearer associated with a user equipment (UE) (e.g., due to load conditions in a radio access network, the core network, or an application server), the network apparatus can send to the UE a call-back message when the network apparatus exits the state that precipitated the bearer rejection or pre-emption. By sending a call-back message, the network apparatus can save the UE from multiple unsuccessful attempts to establish a bearer, or from waiting an unnecessarily long time before establishing a bearer.