IP Library Granted Patent US 12,373,546
Granted Patent B1
US 12,373,546 · App. 17/810,319 · Granted Jul 29, 2025

Automated cloud-based network function interoperability testing

Inventors: Julius Mueller (Santa Cruz, CA); Dimitrios Elissaios (Seattle, WA); Sanket Modak (Bellevue, WA); Nikolay Krasilnikov (Seattle, WA)
Assignee: Amazon Technologies, Inc.
G06F21/53G06F2221/033
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,373,546
App. No.
17/810,319
Granted
Jul 29, 2025
Kind
B1
Abstract

A testing manager at a provider network configures a multi-network-function test sandbox for a first network function developed by a first vendor. To configure the sandbox, the testing manager causes the first network function to be run at a first server and verifies network connectivity between the first network function and another network function which is not developed by the first vendor. The testing manager causes a test to be run, which includes transmission of messages from the first network function to the second network function. A result of the test is provided via a programmatic interface.

Claims (58)

1. A system, comprising:

a testing manager of a network function management service of a cloud provider network; and

a test resource fleet comprising a plurality of servers;

wherein the testing manager is configured to:

receive a testing request, via a programmatic interface, indicating at least a first network function of a radio-based application, wherein the first network function is developed by a first software vendor; and

in response to the received testing request:

establish a multi-network-function test sandbox for the first network function, wherein said establish the multi-network-function test sandbox comprises:

establish a first isolated virtual network of a virtualized computing service of the cloud provider network;

launching, at a first server of the test resource fleet, a first compute instance within the first isolated virtual network;

cause the first network function to be executed using the first compute instance; and

verify network connectivity between the first network function and a second network function, wherein the second network function is developed by a second software vendor; and

run a test which includes an exchange of messages between the first network function and the second network function; and

provide, via a programmatic interface, a result of the test.

2. The system as recited in claim 1 , wherein the testing manager is further configured to:

determine a number of servers to be included in the multi-network-function test sandbox based at least in part on a network function interconnection topology included in the testing request; and

cause the second network function to be executed at a second server of the test resource fleet in accordance with the network function interconnection topology.

3. The system as recited in claim 1 , wherein the second network function is (a) a network function of a physical or L1 layer of a radio-based technology stack and (b) executed at least in part at a hardware network function accelerator, and wherein the first network function is a network function of another layer of the radio-based technology stack.

4. The system as recited in claim 1 , wherein during the test, the second network function is run within a second isolated virtual network.

5. The system as recited in claim 1 , wherein to run the test, the testing manager is further configured to:

determine a response of the first network function to an introduced error or failure in accordance with a resilience testing specification indicated in the testing request.

6. A computer-implemented method, comprising:

performing, by a testing manager of a network function management service of a provider network:

receiving a testing request, via a programmatic interface, indicating a first network function of a radio-based application, wherein the first network function is developed by a first vendor; and

in response to the received testing request:

establishing a multi-network-function test sandbox for the first network function, wherein establishing the multi-network-function test sandbox comprises:

causing the first network function to be run at a first server assigned by the testing manager; and

verifying network connectivity between the first network function and a second network function, wherein the second network function is not developed by the first vendor; and

executing a test which includes transmission of messages from the first network function to the second network function; and

providing, via a programmatic interface, a result of the test.

7. The computer-implemented method as recited in claim 6 , wherein the testing request is submitted by the first vendor.

8. The computer-implemented method as recited in claim 6 , further comprising:

providing, via a programmatic interface prior to receiving the testing request to an entity other than the first vendor, an indication that the first network function is available for testing of radio-based application pipelines, wherein the testing request is submitted by the entity other than the first vendor.

9. The computer-implemented method as recited in claim 6 , wherein establishing the multi-network-function test sandbox comprises:

establishing a load balancer for network traffic transmitted between a pair of layers of a multi-layer network function pipeline, wherein executing the test comprises causing network traffic to be transmitted between the pair of layers, and wherein the first network function is executed in the test at a particular layer of the multi-layer network function pipeline.

10. The computer-implemented method as recited in claim 6 , wherein establishing the multi-network-function test sandbox comprises:

establishing an auto-scaling group for resources at a particular layer of a multi-layer network function pipeline, wherein the first network function is executed in the test at a particular layer of the multi-layer network function pipeline.

11. The computer-implemented method as recited in claim 6 , wherein executing the test comprises:

causing a workload level of the first network function to be varied in accordance with a performance testing specification indicated in the testing request.

12. The computer-implemented method as recited in claim 6 , wherein executing the test comprises:

determining a response of the first network function to an introduced error or failure in accordance with a resilience testing specification indicated in the testing request.

13. The computer-implemented method as recited in claim 6 , wherein executing the test comprises:

causing at least one network function executed during the test to be run at a network function accelerator of the first server.

14. The computer-implemented method as recited in claim 6 , wherein the testing request includes an interconnection topology to be used for the test, the computer-implemented method further comprising:

utilizing, in accordance with the interconnection topology, a second server to run the second network function.

15. The computer-implemented method as recited in claim 6 , wherein the first network function implements a portion of one of: (a) a distributed unit (DU) of a radio access network (RAN) node, (b) a centralized unit (CU) of a RAN node, or (c) a core network of a radio-based application.

16. A non-transitory computer-accessible storage medium storing program instructions that when executed on a processor implement a testing manager of a provider network, wherein the testing manager is configured to, responsive to receiving a testing request:

establish a multi-network-function test sandbox for a first network function, wherein the first network function is developed by a first vendor, wherein said establish of the multi-network-function test sandbox comprises:

cause the first network function to be run at a server of the provider network; and

verify network connectivity between the first network function and a second network function, wherein the second network function is not developed by the first vendor;

initiate a test which includes transmission of messages from the first network function to the second network function; and

provide, via a programmatic interface, a result of the test.

17. The non-transitory computer-accessible storage medium as recited in claim 16 , wherein the testing manager is further configured to:

cause messages produced by a workload generation tool to be received at a network function of the first and second network functions, wherein the workload generation tool is indicated in a programmatic request for the test.

18. The non-transitory computer-accessible storage medium as recited in claim 16 , wherein the first network function implements a portion of one of: (a) a distributed unit (DU) of a radio access network (RAN) node, (b) a centralized unit (CU) of a RAN node, or (c) a core network of a radio-based application.

19. The non-transitory computer-accessible storage medium as recited in claim 16 , wherein the testing manager is further configured to:

cause, during the test, a workload level of the first network function to be varied in accordance with a performance testing specification.

20. The non-transitory computer-accessible storage medium as recited in claim 16 , wherein the testing manager is further configured to:

determine a response of the first network function to an introduced error or failure in accordance with a resilience testing specification.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 16, 2024
From: MUELLER, JULIUS; ELISSAIOS, DIMITRIOS; MODAK, SANKET; KRASILNIKOV, NIKOLAY
To: AMAZON TECHNOLOGIES, INC.
Reel/Frame 067439/0415 →
References Cited (71)
US 8539079B2 · Thireault · 2013 [cited by applicant]
US 9125047B2 · Sundaresan et al. · 2015 [cited by applicant]
US 9703660B2 · Cillis et al. · 2017 [cited by applicant]
US 9838268B1 · Mattson · 2017 [cited by applicant]
US 9876851B2 · Chandramouli et al. · 2018 [cited by applicant]
US 10064242B2 · Pawar et al. · 2018 [cited by applicant]
US 10135702B2 · Lahiri · 2018 [cited by examiner]
US 10244507B2 · Tarlazzi et al. · 2019 [cited by applicant]
US 10257105B2 · Majmundar et al. · 2019 [cited by applicant]
US 10419550B2 · Nainar et al. · 2019 [cited by applicant]
US 10581717B2 · Tejaprakash et al. · 2020 [cited by applicant]
US 10594456B2 · Park · 2020 [cited by examiner]
US 10608734B2 · Barbieri et al. · 2020 [cited by applicant]
US 10705808B2 · Chiosi et al. · 2020 [cited by applicant]
US 10749721B2 · Fertonani et al. · 2020 [cited by applicant]
US 10750514B2 · Fujinami · 2020 [cited by applicant]
US 10817409B2 · Zeng et al. · 2020 [cited by applicant]
US 10880173B2 · Seenappa · 2020 [cited by examiner]
US 10944668B2 · Rajagopal · 2021 [cited by applicant]
US 10959098B2 · Cidon et al. · 2021 [cited by applicant]
US 10999783B2 · Pateromichelakis · 2021 [cited by applicant]
US 11190413B1 · Priya et al. · 2021 [cited by applicant]
US 11356500B1 · Gupta et al. · 2022 [cited by applicant]
US 11539582B1 · Gupta et al. · 2022 [cited by applicant]
US 11552842B2 · Barabell · 2023 [cited by applicant]
US 20120127151A1 · Murakami · 2012 [cited by applicant]
US 20180146375A1 · Pawar et al. · 2018 [cited by applicant]
US 20180365635A1 · Lucrecio et al. · 2018 [cited by applicant]
US 20190042326A1 · Chilikin · 2019 [cited by applicant]
US 20190158606A1 · Guim Bernat et al. · 2019 [cited by applicant]
US 20190165906A1 · Bala et al. · 2019 [cited by applicant]
US 20190190785A1 · Power · 2019 [cited by applicant]
US 20190213029A1 · Liu et al. · 2019 [cited by applicant]
US 20190289497A1 · Rajagopal · 2019 [cited by applicant]
US 20190391855A1 · Bernat et al. · 2019 [cited by applicant]
US 20190394826A1 · Wang et al. · 2019 [cited by applicant]
US 20200245229A1 · Horn et al. · 2020 [cited by applicant]
US 20210006944A1 · Raghothaman et al. · 2021 [cited by applicant]
US 20210073047A1 · Bhandaru · 2021 [cited by applicant]
US 20210144517A1 · Guim Bernat et al. · 2021 [cited by applicant]
US 20210144555A1 · Kim et al. · 2021 [cited by applicant]
US 20210243770A1 · Roessler · 2021 [cited by applicant]
US 20210271517A1 · Guim Bernat · 2021 [cited by applicant]
US 20220030117A1 · Young et al. · 2022 [cited by applicant]
US 20220046084A1 · Nair · 2022 [cited by applicant]
US 20220070734A1 · Rajagopal · 2022 [cited by applicant]
US 20220188403A1 · Montasser · 2022 [cited by examiner]
US 20220377615A1 · Radunovic · 2022 [cited by applicant]
U.S. Appl. No. 18/146,126, filed Dec. 23, 2022, Diwakar Gupta. [cited by applicant]
U.S. Appl. No. 18/067,651, filed Dec. 16, 2022, Frank Paterra. [cited by applicant]
U.S. Appl. No. 18/067,650, filed Dec. 16, 2022, Jiandong Huang. [cited by applicant]
U.S. Appl. No. 18/066,943, filed Dec. 15, 2022, Awaiz Ahmad Khan. [cited by applicant]
U.S. Appl. No. 18/067,654, filed Dec. 16, 2022, Frank Paterra. [cited by applicant]
Ashfaq Ahmed, et al., “Hybrid Automatic Repeat Request (HARQ) in Wireless Communication Systems and Standards: A Contemporary Survey”, IEEE Communications Surveys & Tutorials 23.4, 2021, pp. 2711-2752. [cited by applicant]
Unknown, “5G; NG-RAN; Architecture Description”, Technical Specification, ETSI TS 138 401, Version 16.8.0, Release 16, Jan. 2022, pp. 1-82. [cited by applicant]
U.S. Appl. No. 17/710,571, filed Mar. 31, 2022, Manjari Asawa. [cited by applicant]
U.S. Appl. No. 17/548,391, filed Dec. 10, 2021, Ammar Latif. [cited by applicant]
U.S. Appl. No. 17/364,791, filed Jun. 30, 2021, Diwakar Gupta. [cited by applicant]
U.S. Appl. No. 17/364,779, filed Jun. 30, 2021, Diwakar Gupta. [cited by applicant]
U.S. Appl. No. 17/364,788, filed Jun. 30, 2021, Diwakar Gupta. [cited by applicant]
U.S. Appl. No. 17/806,684, filed Jun. 13, 2022, Benjamin Wojtowicz. [cited by applicant]
U.S. Appl. No. 17/806,685, filed Jun. 13, 2022, Benjamin Wojtowicz. [cited by applicant]
U.S. Appl. No. 17/461,785, filed Aug. 30, 2021, Diwakar Gupta. [cited by applicant]
U.S. Appl. No. 17/809,864, filed Jun. 29, 2022, Nikolay Kirschenmann, et al. [cited by applicant]
U.S. Appl. No. 17/820,542, filed Aug. 17, 2022, Nikolay Kirschenmann, et al. [cited by applicant]
U.S. Appl. No. 17/807,343, filed Jun. 16, 2022, Upendra Bhalchandra Shevade et al. [cited by applicant]
U.S. Appl. No. 17/807,344, filed Jun. 16, 2022, Upendra Bhalchandra Shevade et al. [cited by applicant]
U.S. Appl. No. 17/807,341, filed Jun. 16, 2022, Upendra Bhalchandra Shevade et al. [cited by applicant]
U.S. Appl. No. 17/808,518, filed Jun. 23, 2022, Ozgur Dural. [cited by applicant]
U.S. Appl. No. 17/326,218, filed May 21, 2021, Ximeng Simon Yang. [cited by applicant]
U.S. Appl. No. 17/326,221, filed May 20, 2021, Ximeng Simon Yang. [cited by applicant]