Verizon Patent and Licensing Inc.

Cellco Partnership

Raymond So

Sudhakar Reddy Patil

Parry Cornell Booker

Jerry Steben

Lalit R Kotecha

Ye Huang

Violeta Cakulev

Suzann Hua

Lixia Yan

James Mathison

Maria G Lam

Ho Yin Cheuk

David Taft

Lee K Tjio

William Howard Stone, Jr

Lap Tse

Priscilla Lau

Deepak Kakadia

Yee Sin Chan

Mingxing Li

Matthew W Nelson

Thomas H Tan

Emerando M Delos Reyes

Manish Mohan Sharma

Maqbool Chauhan

Amir Saghir

Oleg Berzin

Said Hanbaly

Shanthala Kuravangi-Thammaiah

Thaddeus Jude Dudziak

Helen Osias Eglip

Satish S Vasamsetti

William W Wong

Jayshree A Bharatia

Peter B Sensenbrenner

Richard Janocko

Systems and methods described herein enable premium session retainability for differentiation of services with respect to network function failures. A first network function of a core network obtains a session retention indicator during establishment of a protocol data unit (PDU) session. The first network function calculates a compute footprint for the first network function to support the PDU session and any other premium sessions currently serviced by the first network function. An orchestration device receives the compute footprint and provisions a second network function based on the compute footprint. The first network function and the second network function perform data replication of state information for the PDU session to allow premium sessions to continue with no or minimal interruption in the event of a failover scenario.

Systems and methods for premium session retainability in core networks

A primary application cloud instance may receive historical usage of an application, may allocate, based on the historical usage, a quantity of cloud resources for enabling the application to be accessed, and may enable the application to be accessed. The primary application cloud instance may provide, to a backup application cloud instance that allocates a minimum quantity of cloud resources for providing a skeletal version of the application, heartbeat and session state information associated with the primary application cloud instance, and the quantity of cloud resources for enabling the application to be accessed. The primary application cloud instance may provide, to the backup application cloud instance, an indication of a failure of the primary application cloud instance, via the heartbeat and session state information, to cause the backup application cloud instance to allocate the quantity of cloud resources and to enable access to the application.

Systems and methods for optimizing resources for applications deployed in primary and backup geographically dispersed cloud environments

A network device may maintain a list of existing slice identifiers, associated with slices of a core network, that are in use in active UE sessions, and may receive a slice identifier associated with a slice of the core network and provided in a request to establish a session between a UE and the slice of the core network. The network device may determine whether the slice identifier matches an existing slice identifier included in the list, and may create a new network address, with an address of the network device and the slice identifier, based on the slice identifier failing to match an existing slice identifier included in the list. The network device may utilize the new network address to establish the session between the UE and the slice of the core network.

Systems and methods for network slice traffic identification using dynamic network addressing

Systems and methods described herein employ a service profile for user equipment (UE). The UE service profile may be defined per network slice, such that a subscriber can have different registration area profiles, paging profiles, or performance profiles in different slices. According to one implementation, a network device receives a registration request requesting access to a network slice and obtains a UE service profile for the network slice. The service profile may indicate a paging profile and a registration profile associated with the UE device for the network slice.

Systems and methods for selecting a paging profile and registration area in a mobile network

Disclosure are techniques for allocating aggregation devices in a lawful intercept system. In an embodiment, a method includes maintaining a list of point of interception aggregation (PAG) functions in a network function repository function (NRF) of a cellular network upon instantiation of the PAG functions; receiving a lawful intercept (LI) request; querying the NRF to determine a respective PAG function; and associating a point of interception (POI) function with the respective PAG function.

Network discovery in a lawful intercept system

A method is provided for enforcing quality of service parameters. A gateway receives a request for data usage from a mobile device. The gateway sends, to a controller, inquiry for allowed bit rate. Upon receiving a first bit rate value, the gateway sends, to a charging system, request for quota. In response to receiving the quota, the gateway provides data to the mobile device based on the first bit rate value. The gateway provides data to the mobile device until the quota is exhausted. Once a data usage threshold is reached, the gateway receives, from the controller, a second bit rate value. In response to receiving the second bit rate value, the gateway provides data to the mobile device based on the second bit rate value, until an activation-time is reached. When the activation-time is reached, the gateway resets the allowed bit rate to the first bit rate value.

Enforcing parameters for quality of data link service at a future time

A method is provided for enforcing quality of service parameters. A gateway receives a request for data usage from a mobile device. The gateway sends, to a controller, inquiry for allowed bit rate. Upon receiving a first bit rate value, the gateway sends, to a charging system, request for quota. In response to receiving the quota, the gateway provides data to the mobile device based on the first bit rate value. The gateway provides data to the mobile device until the quota is exhausted. Once a data usage threshold is reached, the gateway receives, from the controller, a second bit rate value. In response to receiving the second bit rate value, the gateway provides data to the mobile device based on the second bit rate value, until an activation-time is reached. When the activation-time is reached, the gateway resets the allowed bit rate from the second bit rate value to the first bit rate value.

A base station may establish a radio resource control (RRC) connection with a first user device. The base station may determine a bearer attribute of a bearer associated with the RRC connection and the first user device. The base station may determine that the bearer attribute satisfies a set of conditions, and may analyze multiple bearer attributes associated with multiple established RRC connections. The base station may select a terminable RRC connection, of the multiple established RRC connections, based on analyzing the multiple bearer attributes. The terminable RRC connection may be associated with a second user device that is different from the first user device, and the terminable RRC connection may be different from the RRC connection. The device may terminate the terminable RRC connection based on selecting the terminable RRC connection.

Managing radio resource control (RRC) connections based on radio bearer attributes

A device may receive information associated with a network resource request. The network resource request may be a request, by a user device, for access to a network resource associated with a network. The device may determine a subscriber class associated with the user device based on receiving the information associated with the network resource request. The device may determine a service type associated with the network resource request based on receiving the information associated with the network resource request. The device may determine an allocation and retention priority (ARP) level based on the determined subscriber class and the determined service type. The device may assign the ARP level to the network resource.

Tier-based admission control for user equipment

A device may receive a request for a transmission of traffic from an application, the application being associated with an application identifier. The device may determine an application category of the application using the application identifier associated with the application. The device may identify a set of rules associated with the application category, where the set of rules includes at least one of one or more rules associated with foreground traffic, or one or more rules associated with background traffic. The device may selectively block or permit the transmission of traffic, from the application, based on the set of rules.

Selectively blocking traffic based on a set of rules associated with an application category

A server device may store inter-layer quality of service ('QoS') information, indicating a set of link layer QoS levels that are associated with a particular device, a set of network layer QoS levels that are associated with the set of link layer QoS levels, and a set of MPLS QoS levels that are associated with the set of link layer QoS levels. A network device may establish a set of bearers, that correspond to the set of link layer QoS levels, with a particular device; output information regarding the set of network layer QoS levels that are associated with the set of link layer QoS levels, to allow the particular device to select a bearer, of the set of bearers, via which to output traffic to the network device; receive, from the particular device, traffic via the bearer; and determine a particular MPLS QoS level associated with the received traffic.

Inter-layer quality of service preservation

A method may include receiving information identifying a radio frequency (RF) usage policy that is associated with a user equipment (UE). The UE may communicate with a network using RF signals, and the RF access signaling usage policy may identify an RF access signaling usage threshold. The RF access signaling usage threshold may identify a quantity of bearers and an action to perform based on the UE requesting the quantity of bearers. The method may include causing a gateway device to monitor RF access signaling usage of the UE. The method may include receiving an RF access signaling usage update. The method may include determining that the RF access signaling usage satisfies the RF access signaling usage threshold based on the RF access signaling usage update. The method may include causing an action to be performed based on the RF access signaling usage policy.

Enforcing radio frequency usage billing and control policies

A network device receives utilization information, for an infrastructure network, that provides data for individual segments of the infrastructure network. Based on the data for the individual segments, the network device generates a costing matrix that includes prices for each segment of the individual segments. The network device identifies particular segments of the infrastructure network associated with an end-to-end path for a subscriber and generates pricing of different service levels for the end-to-end path. The pricing is based on the costing matrix and a particular time period. The network device provides, to the subscriber, a user interface that includes service plan options with the pricing of different service levels for the end-to-end path and receives, via the user interface, a selection of one of the service plan options. The network device sends instructions to provision the infrastructure network to support the selected service plan option.

Growing community of inventors

San Ramon, CA, United States of America

Raymond So