Verizon Patent and Licensing Inc.

David Taft

Maqbool Chauhan

Jerry Steben

Parry Cornell Booker

Sudhakar Reddy Patil

Nicklous D Morris

Imtiyaz Shaikh

Lap Tse

Kalyani Bogineni

Vinod Kumar Choyi

Hossein M Ahmadi

Mark T Watts

Minbao Li

Luay Jalil

Ye Huang

Donna L Polehn

Violeta Cakulev

Suzann Hua

Maria G Lam

Raymond So

Anthony Clay Reynolds

Lily H Zhu

Kristen Sydney Young

Vishwanath Ramamurthi

Thomas W Haynes

Yuexin Dong

Kirk Campbell

Corey J Christopherson

Jude M Munn

Raquel Morera Sempere

Vijayakrishna P Guduru

Abhitabh Kushwaha

Sankaran Ramanathan

John P Demko

Ambreen Habib

Gregory Pultorak

Anthony Mathias George

Massimiliano Troiani

Tony Ferreira

Eric T Handley

Muralidhar Devarakonda

Michael L Hoarle

Eugene A Oliva

Neeharika S Peter

Andrew Lee Ray

Julian Jimenez

Shane Ronan

James D Shannon

Scott Kurzweg

Theresa Marie Rivera

Anthony Sirignano

Edward G Leyton

Chad Allenbrand

Systems and methods described herein provide a slice management and prioritization service on a per user equipment (UE) device level. A network device in a core network may receive a notification that a UE device has exhausted a quota of available simultaneous data radio bearers (DRBs) and, afterwards, receive an indication that an application on the UE device has requested a new protocol data unit (PDU) session on a requested network slice that is not currently active for the UE device. The network device may identify relative priorities for the requested network slice and active network slices for the UE device; determine, based on the relative priorities, if the new PDU session can preempt a DRB for an active PDU session; and delete the active PDU session when it is determined the new PDU session can preempt a DRB for an active PDU session.

Systems and methods for management of maximum simultaneous slices

A device may receive, from a user equipment (UE), a request for an application, and may receive, from the UE, parameters of the application and key performance indicator (KPI) targets for the application. The device may receive, based on the request, KPIs from a core network, a mobile edge computing (MEC) device, and an application server, and may compare the KPIs and the KPI targets for the application. The device may determine, based on comparing the KPIs and the KPI targets, whether to utilize the MEC device or the application server for providing the application to the UE. The device may selectively identify a first user plane function (UPF) associated with the MEC device based on determining to utilize the MEC device, or may identify a second UPF associated with the application server based on determining to utilize the application server.

Systems and methods for providing application and subscription aware user plane function selection, steering, and anchoring

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

A computer device may include a memory storing instructions and processor configured to execute the instructions to host a network function container that implements a microservice for a network function in a wireless communications network, wherein the network function container is deployed by a container orchestration platform; host a service proxy container associated with the network function container, wherein the service proxy container is deployed by the container orchestration platform; and configure the hosted service proxy container to apply a wireless network policy to the microservice for the network function. The processor may be further configured to intercept messages associated with the microservice for the network function using the configured service proxy container; and apply the wireless network policy to the intercepted messages using the configured service proxy container.

Wireless network policy manager for a service mesh

Embodiments described herein allow reduced latency and computational costs by identifying a slice associated with a packet and determining an action to be performed with respect to the packet without having to perform deep packet inspection on the packet. An aspect of the present disclosure is a method comprising receiving a packet including a slice identifier corresponding to a slice of a network, the slice identifier having a plurality of bits; determining a bit value for each bit in a subset of the plurality of bits; and performing an action with respect to the packet based on the bit value of at least one bit in the subset.

Systems and methods for packet management

A method, a network device, and a non-transitory computer-readable storage medium are described in relation to an EASDF secure service. The EASDF secure service may include a network-side service that may validate access and authorization to use a domain name system (DNS) resolver device, such as an edge application server discovery function. The network-side service may validate access and authorization of an end device based on tokens. The EASDF secure service may include an end device-side service that includes a token with a DNS query to the DNS resolver device. The end device-side service may further provide authorization regarding access and use of applications, networks, and application devices that host applications and/or assets by the end device at the end device. The end device-side service may determine access and/or authorization based on tokens and a validation procedure performed at the end device.

Method and system for EASDF secure service

A method may include identifying network slices associated with transmitting data in a network and determining, by a routing device, that a failure associated with a path used to transmit data has occurred. The method may also include determining, by the routing device, whether the failure is associated with one of the plurality of network slices. The method may further include prioritizing, by the routing device, a route selection process in response to determining that the failure is associated with one of the plurality of network slices.

Slice-based recovery and convergence

A method, a device, and a non-transitory computer-readable storage medium are described in which an predictive discontinuous reception (DRX) bypass service is provided. The bypass service may provide flow control signaling that enables an uplink grant to be transmitted to an end device regardless of the DRX mode. The bypass service may provide for an immediate grant for uplink data and may improve latency. The bypass service may also provide flow control signaling for downlink data that may cause the end device to wake up from a DRX mode and receive downlink data. The bypass service also provides predictive scheduling that allows an external network, such as a multi-access edge computing network to establish a DRX-free downlink connection before completion of data processing. The flow control signaling may include a quality of service flow identifier value that correlates to the bypass service.

Method and system for predictive discontinuous reception bypass

One or more computing devices, systems, and/or methods for managing security associated with applications are provided. In an example, a central security gateway may determine first security policy information associated with a first application. The central security gateway may establish a first encrypted connection with a first device of the first application. The central security gateway may manage, based upon the first security policy information and using the first encrypted connection, security associated with the first application. The central security gateway may determine second security policy information associated with a second application. The central security gateway may establish a second encrypted connection with a second device of the second application. The central security gateway may manage, based upon the second security policy information and using the second encrypted connection, security associated with the second application.

Systems and methods for application security utilizing centralized security management

Systems and methods described herein provide for User Equipment (UE)-initiated authentication and authorization updates to Network Slice-Specific Authentication and Authorization (NSSAA). A network device in a core network receives a message from a user device outside of the core network, wherein the message includes a request to initiate a NSSAA procedure. The network device initiates the NSSAA procedure in response to the request. The systems and methods also provide for UE-initiated authorization revocation of NSSAA.

Systems and methods for UE-initiated NSSAA procedures

A device may receive explicit congestion notification data associated with user devices connected to a network of network devices, and may receive network data identifying network metrics associated with the network devices. The device may generate an active queue management mapping table based on utilizing a model to process the explicit congestion notification data and the network data. The device may determine, based on the active queue management mapping table and the network data, a routing table that includes routing data identifying traffic paths with active queue management enabled network devices and without non-active queue management enabled network devices of the network devices. The device may provide the routing table to the network devices.

Systems and methods for determining routing data based on explicit congestion notifications and active queue management enabled network devices

A source network device may receive a multicast data stream to be provided to a plurality of network devices of a network, and may generate, for the multicast data stream, a segment routing header that identifies the plurality of network devices to be provided the multicast data stream. The source network device may cause the multicast data stream to be serially provided to the plurality of network devices identified in the segment routing header without requiring the plurality of network devices to store and reconstruct the segment routing header and without requiring the plurality of network devices to maintain state.

Systems and methods for providing a multicast data stream without storing or reconstructing a header or maintaining state

A device may include a processor configured to establish a data traffic flow for a user equipment (UE) device and determine per flow descriptor attributes associated with the data traffic flow, wherein the per flow descriptor attributes identify at least a source, a destination, and a protocol associated with the data traffic flow. The processor may be further configured to determine at least one additional per flow descriptor attribute for the data traffic flow and send the per flow descriptor attributes and the at least one additional per flow descriptor attribute to a network exposure device of a core network, wherein the network exposure device is configured to communicate with servers outside the core network.

Systems and methods for exposing custom per flow descriptor attributes

A network device may receive Network Slice Selection Assistance Information (NSSAI) and network information from network components and from a set of Integrated Access and Backhaul (IAB) nodes; generate descriptions of, or updates to the descriptions of, routing paths based on the NSSAI and the network information; and send the descriptions or the updates to the IAB nodes. The routing paths may include one or more backhaul links between the IAB nodes, and the descriptions and the updates associate each of the routing paths with one or more Single-NSSAIs (S-NSSAIs).

System and method for controlling and managing integrated access and backhaul

Growing community of inventors

Keller, TX, United States of America

David Taft