Verizon Patent and Licensing Inc.

Verizea Patent and Licensing Inc.

Hans Raj Nahata

Kalyani Bogineni

Ravi Potluri

Ratul Kumar Guha

Kristen Sydney Young

Jignesh Shantilal Panchal

Abhishek Kumar

Muthukumar Retnasamy

Madhan Muralimanohar

Violeta Cakulev

Prasad Deviprasad

Sudhakar Reddy Patil

Matthew W Nelson

Fernando Oliveira

Anand J Shah

Jin Yang

Barry F Hoffner

Marc Chiaverini

Jerry Steben

Yueping Zhang

Shanthala Kuravangi-Thammaiah

Myron Eugene Bagwell

Raquel Morera Sempere

Jason T Wright

Paul Kerl

Michael Antony Raj

Joshua H Wainer

Abdul Subhan

Sandeep Sarma

Jolly Lal

Bharath Thiruveedula

Mohan Palat

Rishi Tandon

Sanjay Mishra

Harinder S Lakhian

Systems and methods described herein provide a Specialized-Operator enabled with admission control functionalities and Custom Resource Definition (CRD) plugins responsible for improving the reliability of the CNF Lifecycle Management operations for deploying containerized workloads on any heterogeneous cloud platform or in multi-cluster environments. According to one implementation, a computing device includes a sensor Network Function Virtualization (NFV)-extension and an actuator NFV-extension. The sensor NFV-extension obtains, from a Container Infrastructure Service Manager (CISM), an event signal that indicates a deficiency with a customer Containerized Network Function (CNF) deployment; detects a current state for the CNF deployment; determines an intent for the CNF deployment; identifies, based on the intent, a desired state for the CNF deployment; and selects, from a group of available actuator NFV-extensions, the actuator NFV-extension corresponding to the desired state. The actuator NFV-extension may be configured to initiate remediation of the CNF deployment to the desired state.

Containerized network function deployment during runtime resource creation

A system comprises one or more devices. The devices are configured to: receive a context associated with a flow of packets between a User Equipment device (UE) and a network slice in a wireless network; obtain one or more policy rules; apply the policy rules to the context and a model of a transport device to generate or update a map that assigns one or more contexts to queues within the transport device; and send the map to the transport device. The transport device is configured to: adjust parameters of the queues based on the map; shape traffic from each of the queues; schedule packets from the queues; and forward the scheduled packets.

Systems and methods for supporting network slice services using transport devices

One or more computing devices, systems, and/or methods for upgrading sites of a communication network are provided. Operational information of network functions within a communication network are tracked within a data repository. An upgrade ruleset is defined for identifying sites within a communication network to upgrade. The operational information, the upgrade ruleset, and model rules generated by a model for a set of candidate sites are processed to generate a positive list of sites to upgrade and a negative list of sites to not upgrade. The negative list of sites and criteria used to determine that the negative list of sites are not being upgraded are provided such as to a user. An upgrade process is performed to upgrade the sites within the positive list of sites.

Methods and systems for upgrading sites of a communication network

Systems and methods described herein enable distribution of a Charging Function group identifier ('CHF-Group-ID') and other CHF selection data to CHF consumers during Protocol Data Unit (PDU) session establishment in a 5G network. A Unified Data Repository (UDR) is provisioned with CHF-Group-ID details for each subscriber of the network. In one aspect, during PDU session establishment, CHF consumers obtain CHF-Group-ID information as part of a subscriber profile that is provided to all CHF consumers. No additional step or hop is needed for the CHF consumers to obtain the CHF-Group-ID. Thus, regionally segmented CHFs can be implemented without replication of data between CHFs in different regional segments and without additional signaling between network functions.

Systems and methods for regional segmentation and selection of charging function

A network function virtualization (NFV) orchestration service includes a centralized orchestration device and a multi-cluster container management (MCCM) platform. The centralized orchestration device stores a catalog of virtual network function descriptors (VNFDs) in an input language; generates, based on the catalog of VNFDs, intents for containerized network function (CNF) services; and stores the generated intents as blocks in a central intent database, wherein the blocks include an input data model for the CNF services. The MCCM platform includes one or more processors to receive and store a copy of the intent database; read design time policies from the copy of the intent database; and convert the input data model into a vendor-specific output data model in an output language.

Systems and methods for orchestration of network functions

A method, a network device, and a non-transitory computer-readable storage medium are described in relation to a hybrid network slicing service. The hybrid network slicing service may enable the initial configuration of a network slice according to network slice requests that may include customized and user-specified network performance criteria. The hybrid network slicing service may enable network slice requests to specify selection of network resources and use/availability based on entity-based criteria including end device and/or application specific associations. The hybrid network slicing service may optimize network slice configurations and generate network slice templates.

Method and system for hybrid network slicing

A device may receive application information of an application to be deployed in a cloud computing environment. The application information may include requirement information including information defining a compute requirement of the application, a storage requirement of the application, and a network connectivity requirement of the application, and first capability information identifying requested capabilities of the first set of devices. The device may receive second capability information identifying actual capabilities of the second set of devices. The device may compare the first capability information and the second capability information to determine a measure of similarity between the first capability information and the second capability information. The device may generate deployment information for deploying the application on a device, of the second set of devices, based on the measure of similarity.

Systems and methods for cloud topology management during deployment of virtual applications

Network devices may be configured to execute computer-executable instructions to instantiate a deployable unit based on the instructions. The instructions may include a virtual network function (VNF) template that includes: a virtualized deployment unit (VDU) template that describes the deployable unit that includes containers; and a connection point template bound to the VDU template. The deployable unit may provide services of a network function in an access network or a core network. The deployable unit may include an interface defined by the connection point template.

Systems and methods for modeling container-based network functions

A device can determine, based on a first packet flow associated with a first user device and application identifiers associated with applications accessible by the first user device, that a first packet associated with the first packet flow is destined for a low-latency application having a specified latency range. The device can identify a first low-latency bearer that satisfies the specified latency range associated with the low-latency application. The device can map the first packet flow to the first low-latency bearer.

Unified radio access network (RAN)/multi-access edge computing (MEC) platform

A device associated with a network may receive a service profile for a network slice of the network, where the service profile includes one or more service characterizations of the network slice. The device may determine, based on thresholding rules and for each service characterization, whether the service characterization requires selection from a plurality of building blocks, to obtain a group of service characterizations requiring selection. The device may select, based on selection rules and for each service characterization of the group of service characterizations requiring selection, a building block from the plurality of building blocks, to obtain selected building blocks, where the selection rules map attributes of service characterizations to building blocks. The device may stack, based on stacking rules, the selected building blocks, to obtain a slice infrastructure for the network slice. The device may deploy the slice infrastructure for the network slice in the network.

Systems and methods for designing a slice infrastructure

A computer device may include a memory configured to store instructions and a processor configured to execute the instructions to receive a request from a user equipment (UE) device to resolve a Domain Name System (DNS) query for a Uniform Resource Locator (URL) and determine that the URL corresponds to a malicious URL. The processor may be further configured to select to not resolve the DNS query in response to determining that the URL corresponds to a malicious URL and send an indication to the UE device that the URL corresponds to a malicious URL.

Security monitoring for wireless communication devices

A network device executes an account management function that pre-authorizes network service unit consumption by multiple subscribers that are members of a same, shared network service account. The account management function receives, from multiple charging systems distributed within the network, network unit consumption charges associated with each of the multiple subscribers, where the network device is centrally located within a network relative to multiple locations associated with the plurality of charging systems. The account management function updates a consumption counter for the same, shared network service account based on the network unit consumption charges associated with the multiple subscribers received from the multiple charging systems distributed within the network.

Centralized mobile network account management function for shared mobile network consumption tracking of converged charging systems

A method, a device, and a non-transitory storage medium are described in which a resource counter tracking service is provided. The service may include the collection of resource information by a charging function from a virtualized device. The resource information may include information pertaining to hardware usage, quality of service, and transport resources associated with the virtualized device, a cluster, or a data center of relevance. The charging function may generate event information based on the resource information, and make available the event information to third party devices.

Method and system for resource counter tracking

A system may receive a first definition for a virtualized instance of a network function. The first definition may include a first set of declarations in a first format that is different than respective formats supported by different virtualized environments. The system may select a first virtualized environment to run the virtualized instance based on requirements specified within the first definition, and may generate a second definition with a second set of declarations that map the first set of declarations from the first format to a second format supported by the first virtualized environment. The system may deploy the virtualized instance to the first virtualized environment using the second set of declarations from the second definition. Deploying the virtualized instance may include configuring its operation based on some of the second set of declarations matching a configuration format supported by the first virtualized environment.

Growing community of inventors

New Providence, NJ, United States of America

Hans Raj Nahata