IP Library › Granted Patent US 12,511,154
Granted Patent B2
US 12,511,154 · App. 17/730,499 · Granted Dec 30, 2025

Application-centric design for 5G and edge computing applications

Inventors: Kunal Rao (Monroe, NJ); Murugan Sankaradas (Dayton, NJ); Srimat Chakradhar (Manalapan, NJ)
Assignee: NEC Corporation
G06F9/485
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,511,154
App. No.
17/730,499
Granted
Dec 30, 2025
Kind
B2
Abstract

A method for specifying and executing an application including multiple microservices on 5G slices within a multi-tiered 5G infrastructure is presented. The method includes managing compute requirements and network requirements of the application simultaneously by determining end-to-end application characteristics by employing an application slice specification including an application ID component, an application name component, an application metadata component, a function dependencies component, a function instances component, and an instance connections component, specifying a function slice specification including a function network slice specification and a function compute slice specification, and employing a runtime component including a resource manager, an application slice controller, and an application slice monitor, wherein the resource manager maintains a database and manages starting, stopping, updating, and deleting application instances.

Claims (34)

1 . A method for specifying and executing an application including multiple microservices on 5G slices within a multi-tiered 5G infrastructure, the method comprising:

managing compute requirements and network requirements of the application simultaneously by:

determining end-to-end application characteristics by employing an application slice specification including an application ID component, an application name component, an application metadata component, a function dependencies component, a function instances component, and an instance connections component;

specifying a function slice specification including a function network slice specification and a function compute slice specification that includes a tier parameter that maps a function across multiple tiers; and

employing a runtime component including a resource manager, an application slice controller, and an application slice monitor, wherein the resource manager maintains a database and manages starting, stopping, updating, and deleting application instances, the resource manager initially performing static resource management that allocates resources in each tier specified by the tier parameter to a corresponding function according to requirements specified in the function slice specification in an order of cheapest tier first followed by more expensive tier and then performing dynamic resource management across tiers in coordination with the application slice controller and the application slice monitor.

2 . The method of claim 1 , wherein the application slice specification includes a latency parameter, a bandwidth parameter, a deviceCount parameter, and a reliability parameter.

3 . The method of claim 1 , wherein the function network slice specification includes a latency parameter, a throughputGBR parameter, a throughputMBR parameter, and packetErrorRate parameter.

4 . The method of claim 1 , wherein the function compute slice specification further includes a minCPUCores parameter, a maxCPUCores parameter, a minMemory parameter, and a maxMemory parameter.

5 . The method of claim 1 , wherein the application slice controller manages compute slicing and network slicing for functions by employing a network slice interface layer providing guarantees and admission control before network slice generation.

6 . The method of claim 5 , wherein the application slice monitor monitors and collects metrics for the compute slicing and the network slicing generated by the application slice controller, the metrics made available to the resource manager periodically, at specific configurable intervals.

7 . The method of claim 1 , wherein dynamic resource management includes allocating resources in each tier specified by the tier parameter to the corresponding function in an order of cheapest tier first followed by more expensive tier to accommodate changing resource needs.

8 . A non-transitory computer-readable storage medium comprising a computer-readable program for specifying and executing an application including multiple microservices on 5G slices within a multi-tiered 5G infrastructure, wherein the computer-readable program when executed on a computer causes the computer to perform the steps of:

managing compute requirements and network requirements of the application simultaneously by:

determining end-to-end application characteristics by employing an application slice specification including an application ID component, an application name component, an application metadata component, a function dependencies component, a function instances component, and an instance connections component;

specifying a function slice specification including a function network slice specification and a function compute slice specification that includes a tier parameter that maps a function across multiple tiers; and

employing a runtime component including a resource manager, an application slice controller, and an application slice monitor, wherein the resource manager maintains a database and manages starting, stopping, updating, and deleting application instances, the resource manager initially performing static resource management that allocates resources in each tier specified by the tier parameter to a corresponding function according to requirements specified in the function slice specification in an order of cheapest tier first followed by more expensive tier and then performing dynamic resource management across tiers in coordination with the application slice controller and the application slice monitor.

9 . The non-transitory computer-readable storage medium of claim 8 , wherein the application slice specification includes a latency parameter, a bandwidth parameter, a deviceCount parameter, and a reliability parameter.

10 . The non-transitory computer-readable storage medium of claim 8 , wherein the function network slice specification includes a latency parameter, a throughputGBR parameter, a throughputMBR parameter, and packetErrorRate parameter.

11 . The non-transitory computer-readable storage medium of claim 8 , wherein the function compute slice specification further includes a minCPUCores parameter, a maxCPUCores parameter, a minMemory parameter, and a maxMemory parameter.

12 . The non-transitory computer-readable storage medium of claim 8 , wherein the application slice controller manages compute slicing and network slicing for functions by employing a network slice interface layer providing guarantees and admission control before network slice generation.

13 . The non-transitory computer-readable storage medium of claim 12 , wherein the application slice monitor monitors and collects metrics for the compute slicing and the network slicing generated by the application slice controller, the metrics made available to the resource manager periodically, at specific configurable intervals.

14 . A system for specifying and executing an application including multiple microservices on 5G slices within a multi-tiered 5G infrastructure, the system comprising:

a memory; and

one or more processors in communication with the memory configured to:

manage compute requirements and network requirements of the application simultaneously by:

determining end-to-end application characteristics by employing an application slice specification including an application ID component, an application name component, an application metadata component, a function dependencies component, a function instances component, and an instance connections component;

specifying a function slice specification including a function network slice specification and a function compute slice specification that includes a tier parameter that maps a function across multiple tiers; and

employing a runtime component including a resource manager, an application slice controller, and an application slice monitor, wherein the resource manager maintains a database and manages starting, stopping, updating, and deleting application instances, the resource manager initially performing static resource management that allocates resources in each tier specified by the tier parameter to a corresponding function according to requirements specified in the function slice specification in an order of cheapest tier first followed by more expensive tier and then performing dynamic resource management across tiers in coordination with the application slice controller and the application slice monitor.

15 . The system of claim 14 , wherein the application slice specification includes a latency parameter, a bandwidth parameter, a deviceCount parameter, and a reliability parameter.

16 . The system of claim 14 , wherein the function network slice specification includes a latency parameter, a throughputGBR parameter, a throughputMBR parameter, and packetErrorRate parameter.

17 . The system of claim 14 , wherein the function compute slice specification further includes a minCPUCores parameter, a maxCPUCores parameter, a minMemory parameter, and a maxMemory parameter.

18 . The system of claim 14 ,

wherein the application slice controller manages compute slicing and network slicing for functions by employing a network slice interface layer providing guarantees and admission control before network slice generation; and

wherein the application slice monitor monitors and collects metrics for the compute slicing and the network slicing generated by the application slice controller, the metrics made available to the resource manager periodically, at specific configurable intervals.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 18, 2025
From: NEC LABORATORIES AMERICA, INC.
To: NEC CORPORATION
Reel/Frame 072938/0913 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 27, 2022
From: RAO, KUNAL; SANKARADAS, MURUGAN; CHAKRADHAR, SRIMAT
To: NEC LABORATORIES AMERICA, INC.
Reel/Frame 059751/0510 →
Continuity (3)
Provisional Application 63188639 · May 14, 2021
Provisional Application 63309030 · Feb 11, 2022
Related Publication 20220374259A1 · Nov 24, 2022
References Cited (15)
US 6370560B1 · Robertazzi · 2002 [cited by examiner]
US 20080228893A1 · MacDonald · 2008 [cited by examiner]
US 20170126506A1 · Padala · 2017 [cited by examiner]
US 20170228950A1 · Richmond · 2017 [cited by examiner]
US 20170374032A1 · Woolward · 2017 [cited by examiner]
US 20190294350A1 · Hahn · 2019 [cited by examiner]
US 20200028896A1 · Veldanda · 2020 [cited by examiner]
US 20200052991A1 · Kodaypak · 2020 [cited by examiner]
US 20200119736A1 · Weber · 2020 [cited by examiner]
US 20210204198A1 · Xin · 2021 [cited by examiner]
US 20210297876A1 · Bellamkonda · 2021 [cited by examiner]
US 20220124547A1 · Young · 2022 [cited by examiner]
US 20220138081A1 · Varma · 2022 [cited by examiner]
US 20220217610A1 · Zheng · 2022 [cited by examiner]
US 20220300296A1 · Sharma · 2022 [cited by examiner]