# US 2026/0101278 A1 · System and method for dynamic network function management

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2026/0101278 A1
- Document ID: US20260101278A1
- Status: Published application
- Kind: A1
- Application number: 19/404,469
- Filed: 2025-12-01
- Published: 2026-04-09
- Earliest claimed: 2023-10-04
- Assignees: Verizon Patent and Licensing Inc.
- Applicants: Verizon Patent and Licensing Inc.
- Inventors: Emerando M. Delos Reyes; Satish S. Vasamsetti; Tony Ferreira; Michael Kondratiuk
- Web page: https://patentgrep.com/patent/US20260101278A1

## CPC

- H04W 48/18: Selecting a network or a communication service
- H04W 24/02: Arrangements for optimising operational condition
- H04W 60/04: using triggered events
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

Systems and methods enable dynamic network function management, including obtaining user input data identifying network slice provisioning parameters for a creation of a network slice in a network; sending a request for a network repository function (NRF) instance for the network slice, to an orchestrator; receiving, from the NRF instance, a verification message of the creation of the network slice; sending, to the orchestrator, a request for a creation of multiple network function (NF) instances according to the network slice provisioning parameters; receiving, from the orchestrator, a verification message of the creation of the NF instances for the network slice; receiving, from the NRF, a confirmation message of a registration of the NF instances for the network slice; sending slice-specific subscriber provisioning data to a user data instance provisioned for the network slice; and generating a network slice creation confirmation message identifying the network slice.

## Claims

### Claim 1

A method comprising:
obtaining input data identifying network slice deletion parameters including slice identifiers;
sending a network slice deletion request to a network function management unit in a network;
sending slice-specific tear-down information to user data components associated with the network slice;
querying a network repository function (NRF) to identify network function (NF) instances serving the network slice;
notifying the identified NF instances to delete slice-specific configurations and entitlements;
sending, to an orchestrator, a request to decommission the NF instances associated with the network slice;
receiving confirmation messages verifying deletion of the NF instances; and
generating and sending a network slice deletion confirmation message indicating the network slice has been deleted.

### Claim 2 (depends on 1)

The method of claim 1, wherein the network slice deletion parameters include at least one of a network slice selection assistance information (S-NSSAI), user equipment route selection policies (URSPs), access point name (APN), or a list of serving network functions.

### Claim 3 (depends on 1)

The method of claim 1, further comprising, prior to sending the deletion request, validating the slice identifiers in the input data against provisioning records.

### Claim 4 (depends on 1)

The method of claim 1, wherein notifying the identified NF instances comprises sending slice entitlement deletion instructions to one or more of a network slice selection function (NSSF), policy control function (PCF), access and mobility management function (AMF), session management function (SMF), or user plane function (UPF).

### Claim 5 (depends on 1)

The method of claim 1, wherein sending a request to decommission the NF instances comprises invoking an automated container orchestration platform configured to manage lifecycle operations of the NF instances.

### Claim 6 (depends on 5)

The method of claim 5, wherein the container orchestration platform is selected from Kubernetes, Amazon Web Services, Nomad, IronWorker, Docker Swarm, Amazon Elastic Container Service, Helios, Apache Mesos, Red Hat OpenShift Container Platform, Cloudify, or a combination thereof.

### Claim 7 (depends on 1)

The method of claim 1, further comprising returning the freed NF resources to a resource pool accessible for subsequent network slice provisioning.

### Claim 8

A non-transitory computer-readable medium storing instructions that, when executed by one or more processors of one or more network devices, cause the one or more network devices to:
obtain input data identifying network slice deletion parameters including slice identifiers;
send a network slice deletion request to a network function management unit in a network;
send slice-specific tear-down information to user data components associated with the network slice;
query a network repository function (NRF) to identify network function (NF) instances serving the network slice;
notify the identified NF instances to delete slice-specific configurations and entitlements;
send, to an orchestrator, a request to decommission the NF instances associated with the network slice;
receive confirmation messages verifying deletion of the NF instances; and
generate and send a network slice deletion confirmation message indicating the network slice has been deleted.

### Claim 9 (depends on 8)

The non-transitory computer-readable medium of claim 8, wherein the network slice deletion parameters include at least one of network slice selection assistance information (S-NSSAI), user equipment route selection policies (URSPs), access point name (APN), or a list of serving network functions.

### Claim 10 (depends on 8)

The non-transitory computer-readable medium of claim 8, wherein the instructions further cause the one or more network devices to validate the slice identifiers in the input data against provisioning records prior to sending the deletion request.

### Claim 11 (depends on 8)

The non-transitory computer-readable medium of claim 8, wherein notifying the identified NF instances comprises sending slice entitlement deletion instructions to one or more of a network slice selection function (NSSF), policy control function (PCF), access and mobility management function (AMF), session management function (SMF), or user plane function (UPF).

### Claim 12 (depends on 8)

The non-transitory computer-readable medium of claim 8, wherein sending a request to decommission the NF instances comprises invoking an automated container orchestration platform configured to manage lifecycle operations of the NF instances.

### Claim 13 (depends on 12)

The non-transitory computer-readable medium of claim 12, wherein the container orchestration platform is selected from Kubernetes, Amazon Web Services, Nomad, IronWorker, Docker Swarm, Amazon Elastic Container Service, Helios, Apache Mesos, Red Hat OpenShift Container Platform, Cloudify, or a combination thereof.

### Claim 14 (depends on 8)

The non-transitory computer-readable medium of claim 8, wherein the instructions further cause the one or more network devices to return the freed NF resources to a resource pool accessible for subsequent network slice provisioning.

### Claim 15

One or more network devices comprising:
one or more processors configured to: obtain data identifying network slice deletion parameters including slice identifiers; send a network slice deletion request to a network function management unit in a network; send slice-specific tear-down information to user data components associated with the network slice; query a network repository function (NRF) to identify network function (NF) instances serving the network slice; notify the identified NF instances to delete slice-specific configurations and entitlements; send, to an orchestrator, a request to decommission the NF instances associated with the network slice; receive confirmation messages verifying deletion of the NF instances; and generate and send a network slice deletion confirmation message indicating the network slice has been deleted.

### Claim 16 (depends on 15)

The network device of claim 15, wherein the processors are further configured to validate slice identifiers in input data prior to sending a deletion request.

### Claim 17 (depends on 15)

The network device of claim 15, wherein the processors are further configured to notify NF instances selected from a network slice selection function (NSSF), a policy control function (PCF), an access and mobility management function (AMF), a session management function (SMF) or a user plane function (UPF).

### Claim 18 (depends on 15)

The network device of claim 15, wherein the orchestrator comprises one or more container orchestration platforms selected from Kubernetes, Amazon Web Services, Nomad, IronWorker, Docker Swarm, Amazon Elastic Container Service, Helios, Apache Mesos, Red Hat OpenShift Container Platform, Cloudify, or combinations thereof.

### Claim 19 (depends on 15)

The network device of claim 15, wherein the processors are further configured to return deleted NF resources to a resource pool for reuse.

### Claim 20 (depends on 15)

The network device of claim 15, wherein the input data identifying network slice deletion parameters comprise at least one of a Single Network Slice Selection Assistance Information (S-NSSAI), a User Equipment UE Route Selection Policies (URSPs), an Access Point Name (APN) or a list of serving network functions.
