Verizon Patent and Licensing Inc.

Verizon Patent Licensing Inc.

Parry Cornell Booker

Ye Huang

Suzann Hua

Miguel Angel Carames

Sudhakar Reddy Patil

Jerry Steben

Maqbool Chauhan

David Taft

Chien-Yuan Huang

Emerando M Delos Reyes

Feng Li

Haim Shalom Ner

Helen Osias Eglip

Jude M Munn

Yousef Abdelmalek

Raymond So

Satish S Vasamsetti

Lap Tse

Anthony Mathias George

Lily H Zhu

Jignesh Shantilal Panchal

Kalyani Bogineni

Vinod Kumar Choyi

Samirkumar Patel

Hossein M Ahmadi

Raghuram Parvataneni

Minbao Li

Gunjan Thakkar

Nicklous D Morris

Taral Patel

Ning Chen

Urvika Vummadisetty

David E Fitzgerald

Peter B Sensenbrenner

Hilda E Sierra

Massimiliano Troiani

Lalit R Kotecha

Deepak Kakadia

Ratul Kumar Guha

Maria G Lam

Matthew W Nelson

Anil Krishna Guntupalli

Kirk Campbell

Bjorn Olof Erland Kalderen

John Patrick Hickey, Iii

Imtiaz Shaikh

Alexander Fadeev

Art Zaifman

John P Demko

Khurram Abbas

Eric T Handley

Jignesh S Panchai

Carl Recchia

Chad Allenbrand

Edward G Leyton

Anthony Sirignano

Amanda C Lam

Carl M Knopf

Krzysztof Pawlikowski

Jayashree Srinivasan Kilkovalavedu

A network device, implementing a network function, receives a network slice request from a user equipment device (UE) that includes a requested network slice set in a network. The network device determines a first set of allowed network slices for the UE based on at least one of first network slices supported by a Radio Access Network (RAN), second network slices supported by the network function, third network slices to which the UE subscribes, or fourth network slices configured by a Network Slice Selection Function (NSSF) in the network. The network device obtains historical behavior data associated with the UE, and determines a second set of allowed network slices for the UE based on the first set and the historical behavior data associated with the UE. The network device returns the second set of allowed network slices to the UE.

Allowed network slice determination based on UE historical behavior

Systems and methods described herein provide an application function and interface for a Network Data Analytics Function (NWDAF) to receive, from User Equipment (UE) devices, user data for edge applications. An NWDAF receives an analytics request for user analytics for an edge application and sends, to an Edge Analytics Engine (EAE) associated with an edge location, a data request based on the analytics request. The EAE receives user data from an Edge Enabler Client (EEC) on the UE device that is connected to the edge location. The EAE forwards the user data to the network device. The NWDAF receives the user data responsive to the analytics request and generates an analytics report based on the user data.

System and methods for exposing user-driven analytics for edge applications

In the various embodiments, systems and methods are disclosed for determining the location of User Equipment (UE) in a network and for authorizing access to content based on said location. An aspect of the present disclosure is a method including receiving, by a Content Authorization Function (CAF), a request to provide a UE type of a UE and a physical location associated with the UE, the request including a UE Internet Protocol (IP) address associated with the UE; querying, by the CAF, a Network Function (NF), to provide the UE type and associated physical location, the query including the UE IP address; receiving, by the CAF from the NF, the UE type and associated physical location; and transmitting the UE type and associated physical location.

System and method for determining device location and providing access authorization

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

A device may receive user device application performance logs, radio access network (RAN) performance logs, and multi-access edge computing (MEC) compute logs, and may train a machine learning model with the user device application performance logs, the RAN performance logs, and the MEC compute logs. The device may identify application capacity requirements and MEC compute requirements associated with images of RAN coverage areas of RANs, and may generate labeled and normalized images of RAN coverage areas. The device may receive real time MEC compute data, RAN performance data, and user device application data, and may identify one of the labeled and normalized images of the RAN coverage areas that matches a RAN coverage area of a particular RAN. The device may predict an application capacity and MEC compute requirements for the particular RAN, and may perform one or more actions based on the application capacity and the MEC compute requirements.

Systems and methods for determining, monitoring, and predicting application capacity in multiple radio access networks

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

A system described herein may receive a request to establish a communication session between a core network and a User Equipment ('UE'), determine that the requested communication session is associated with one or more admission control options and receive, from the UE, a selection of a particular admission control option of the one or more admission control options. The system may identify one or more actions associated with the particular admission control option. The one or more actions include rejecting the request to establish the communication session, or accepting the request to establish the communication session. The system may perform the one or more identified actions associated with the particular admission control option. The system may include an interface between an Access and Mobility Management Function (“AMF”) of the core network and a Network Slice Access Control Function (“NSACF”) of the core network.

Systems and methods for application function-initiated admission control for a core network

Disclosed are systems and methods for utilizing designed market access (DMA) zones in conjunction with mobile networks so as to enable secure, appropriate read/write access to streaming content. The disclosed systems and methods enable a mapping of an Internet Protocol (IP) address to a particular geolocation node of a mobile network, whereby a DMA for such node can be identified/determined. Accordingly, the DMA can be leveraged for monitoring a customer user's location respective to streaming service/media access requests.

Systems and methods for streaming content control and privacy management

Techniques for packet flow description (PDF) management are disclosed. In one embodiment, a method is disclosed comprising receiving, by a network exposure function (NEF), a packet flow description (PFD) management request via an application function (AF), the PFD management request, the PFD management request comprising application identification information identifying an application, using, by the NEF, the application identification information to identify a set of unified data repositories (UDRs) affected by the PFD management request, and instructing, by the NEF, at least one UDR of the set of UDRs to make a PFD change to the identified application's application data in accordance with the PFD management request.

Packet flow description (PFD) management method and apparatus

A method, a device, and a non-transitory storage medium are described in which an inter-operator mobility service is provided. The service may provide provisioning decisions and configurations that may include core devices that are shared between users of a first entity and users of a second entity, or are dedicated to the users of the second entity to support a network slice and/or access to an application service for end devices associated with the second entity. The service may manage access and use of radio frequencies associated with the first and second entities based on subscription information and location of the end devices associated with first and second entities. The service may further include enabling inter-network handovers associated with end devices associated with end devices associated with the second entity.

Method and system for inter-operator mobility service

A network device may receive historical data identifying historical error data and error data categorizations associated with a first core network and may store the historical data in a data structure. The network device may receive a request associated with a user equipment and may receive error data from the first core network based on the request. The network device may receive network health data identifying load levels and health of the first core network and a second core network. The network device may determine possible cause data identifying causes associated with the error data based on the historical data, the error data, and the network health data. The network device may generate a cause code for the user equipment based on the possible cause data and may provide the cause code to the user equipment.

Systems and methods for providing network failure and cause code handling in 5G networks

A method, a device, and a non-transitory storage medium are described in which a network slice usage service is provided. The network slice usage service may allow a network device to obtain a network slice usage value of a network slice. The network device may calculate a network slice load value based on the network slice usage value. The network device may also provide the network slice load value to other network devices of a core network.

Method and system for network slice usage service

A network device receives, from a congestion controller, traffic policy information associated with a data stream between a sender and a receiver, where the traffic policy information includes a maximum round trip delay time (RTT) and a maximum throughput rate (Rate). The network device obtains a receiver advertised window size (RWND) for the receiver for the data stream. The network device modifies the RWND based on the RTT and the Rate to produce a modified receiver window size (RWND′) and sends the RWND′ to the sender for use in controlling congestion on the data stream between the sender and the receiver.

Systems and methods for congestion control on mobile edge networks

Growing community of inventors

Arlington, TX, United States of America

Parry Cornell Booker