IP Library Granted Patent US 12,192,274
Granted Patent B1
US 12,192,274 · App. 17/695,405 · Granted Jan 7, 2025

Multi-access edge computing for neutral host cellular networks for supply chain management

Inventors: John Cowan (Raleigh, NC); Robert Paul Bullock (St Helier, JE); James A. Thomason (Las Vegas, NV)
Assignee: EDJX, INC.
H04L67/1021G06F16/245G06F16/80H04L67/01H04L67/02H04L67/101
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,192,274
App. No.
17/695,405
Granted
Jan 7, 2025
Kind
B1
Abstract

Systems for providing multi-access edge computing (MEC) and content delivery. At least one cloud platform and at least one server node are provided. Hypertext Transfer Protocol (HTTP) requests are operable to be send between the at least one cloud platform and at least one edge device. The at least one server node is registered in a cloud platform global registry using an HTTP POST request to a global service address, and the cloud platform global registry is associated with the at least one cloud platform. The at least one server node is operable to create at least one cellular network and provide cellular network services to the at least one edge device. The present invention is also operable to collect and analyze data from an IoT sensor network and take actions based on sensor data using the same node infrastructure and edge computing platform.

Claims (57)

1. A system for providing multi-access edge computing and content delivery, comprising:

at least one cloud platform in network communication with at least one edge device; and

at least one server node;

wherein the at least one cloud platform includes a cloud platform domain name system (DNS) service, an edge DNS service, at least one cloud platform application programming interface (API), at least one cloud platform router, a cloud platform database, a node database, and a cloud platform storage component;

wherein the at least one cloud platform is in network communication with the at least one server node;

wherein the at least one cloud platform is operable to fetch node data from the at least one server node;

wherein the at least one cloud platform is operable to receive a hypertext transfer protocol (HTTP) request from the at least one edge device;

wherein the at least one cloud platform is operable to query the node database for a nearest node;

wherein the at least one cloud platform is operable to execute the HTTP request using the nearest node;

wherein the at least one server node is registered in a cloud platform global registry using an HTTP POST request to a global service address and wherein the cloud platform global registry is associated with the at least one cloud platform;

wherein the at least one server node is operable to create at least one cellular network;

wherein the at least one server node is operable to deliver cellular network services to the at least one edge device through the at least one cellular network;

wherein the at least one server node is operable to connect to an internet of things (IoT) sensor network;

wherein the at least one server node is operable to process sensor data from the IoT sensor network, thereby creating event data and/or condition data; and

wherein the at least one server node is operable to take an action in response to the event data and/or the condition data.

2. The system of claim 1 , wherein the at least one server node includes a node identifier (ID), an internet protocol (IP) address, a set of global positioning system (GPS) coordinates, a central processing unit (CPU) ID, a version number, an uptime value, a node heartbeat value, an edge executor, a plurality of v8 isolates, and/or time zone data.

3. The system of claim 1 , wherein the at least one cloud platform is operable to fetch node data from the at least one server node using an object-oriented function, and wherein the object-oriented function is a serverless function.

4. The system of claim 1 , wherein the at least one server node is operable to store the event data and/or the condition data in a content-addressable peer-to-peer storage network.

5. The system of claim 1 , wherein the at least one server node is operable to perform at least one evolved packet core (EPC) function.

6. The system of claim 1 , wherein the at least one cellular network includes at least one virtual cellular network, at least one private network, at least one public network, and/or at least one neutral host cellular network.

7. The system of claim 1 , wherein the IoT sensor network includes a temperature sensor, a humidity sensor, a pressure sensor, a motion sensor, a proximity sensor, an optical sensor, an accelerometer, a gyroscope, an ultraviolet (UV) sensor, an infrared (IR) sensor, a gas sensor, a moisture sensor, a chemical detection sensor, a light sensor, a level sensor, a current sensor, a voltage sensor, a magnetic sensor, a capacitance sensor, an air quality sensor, a particulate sensor, a location sensor, a scanner, a beacon, a smart threshold, a smart lock, a scale, an audio sensor, a camera, and/or a video camera.

8. The system of claim 1 , wherein the at least one server node is operable to process the sensor data in real time or near real time.

9. The system of claim 1 , wherein the at least one server node is operable to process the sensor data using machine learning.

10. The system of claim 1 , wherein the at least one server node is operable to partition the processing of the sensor data.

11. The system of claim 1 , wherein the action includes the at least one server node filtering the sensor data, the event data, and/or the condition data.

12. The system of claim 1 , wherein the action includes content delivery using the at least one cellular network.

13. A system for providing multi-access edge computing and content delivery, comprising:

at least one cloud platform in network communication with at least one edge device; and

at least one server node;

wherein the at least one cloud platform includes a cloud platform domain name system (DNS) service, an edge DNS service, at least one cloud platform application programming interface (API), at least one cloud platform router, a cloud platform database, a node database, and a cloud platform storage component;

wherein the at least one cloud platform is in network communication with the at least one server node;

wherein the at least one cloud platform is operable to fetch node data from the at least one server node;

wherein the at least one cloud platform is operable to receive a hypertext transfer protocol (HTTP) request from the at least one edge device;

wherein the at least one cloud platform is operable to query the node database for a nearest node;

wherein the at least one cloud platform is operable to execute the HTTP request using the nearest node;

wherein the at least one server node is operable to create at least one cellular network;

wherein the at least one server node is operable to deliver cellular network services to the at least one edge device through the at least one cellular network;

wherein the at least one cellular network includes a neutral host cellular network;

wherein the at least one server node is operable to connect to an internet of things (IoT) sensor network;

wherein the at least one server node is operable to process sensor data from the IoT sensor network, thereby creating event data and/or condition data;

wherein the at least one server node is operable to take an action in response to the event data and/or the condition data; and

wherein the at least one server node is registered in a cloud platform global registry using an HTTP POST request to a global service address and wherein the cloud platform global registry is associated with the at least one cloud platform.

14. The system of claim 13 , wherein the at least one server node is operable to process the sensor data in real time or near real time.

15. A method for providing multi-access edge computing and content delivery, comprising:

at least one cloud platform in network communication with at least one edge device and at least one server node resolving a hypertext transfer protocol (HTTP) request;

wherein the at least one cloud platform includes a cloud platform domain name system (DNS) service, an edge DNS service, at least one cloud platform application programming interface (API), at least one cloud platform router, a cloud platform database, a node database, and a cloud platform storage component;

wherein the at least one server node is registered in a cloud platform global registry using an HTTP POST request to a global service address and wherein the cloud platform global registry is associated with the at least one cloud platform;

wherein the at least one cloud platform resolving the HTTP request comprises:

the at least one cloud platform receiving an HTTP request from the at least one edge device;

the at least one cloud platform querying the node database for a nearest node; and

the at least one cloud platform executing the HTTP request on the nearest node;

the at least one server node creating at least one cellular network;

the at least one server node delivering cellular network services to the at least one edge device through the at least one cellular network;

the at least one sensor node connecting to an internet of things (IoT) sensor network;

the at least one sensor node processing sensor data from the IoT sensor network, thereby creating event data and/or condition data; and

the at least one server node taking an action in response to the event data and/or the condition data.

16. The method of claim 15 , further comprising the at least one server node communicating the event data and/or the condition data to the at least one cloud platform.

Assignments (4)
SECURITY INTEREST Recorded Jun 19, 2023
From: EDJX, INC.
To: TARHEEL PROPERTIES, LLC; INTERSOUTH PARTNERS VII, LP
Reel/Frame 063986/0629 →
RELEASE OF SECURITY INTEREST Recorded Jul 13, 2022
From: R. STEVEN VETTER REVOCABLE TRUST
To: EDJX, INC.
Reel/Frame 060498/0249 →
SECURITY INTEREST Recorded Jun 8, 2022
From: EDJX, INC.
To: R. STEVEN VETTER REVOCABLE TRUST
Reel/Frame 060140/0842 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 15, 2022
From: COWAN, JOHN; BULLOCK, ROBERT PAUL; THOMASON, JAMES A.
To: EDJX, INC.
Reel/Frame 059271/0976 →
Continuity (7)
Continuation In Part 17307676 · May 4, 2021
Continuation In Part 17307698 · May 4, 2021
Continuation In Part 17226716 · Apr 9, 2021
Continuation In Part 17226716 · Apr 9, 2021
Continuation 16831069 · Mar 26, 2020
Provisional Application 63090265 · Oct 11, 2020
Provisional Application 62838733 · Apr 25, 2019
References Cited (78)
US 6661799B1 · Molitor · 2003 [cited by examiner]
US 6829654B1 · Jungck · 2004 [cited by examiner]
US 7032031B2 · Jungck · 2006 [cited by examiner]
US 8392912B2 · Davis · 2013 [cited by examiner]
US 8539079B2 · Thireault · 2013 [cited by examiner]
US 8694610B2 · Jungck · 2014 [cited by examiner]
US 9104326B2 · Frank et al. · 2015 [cited by applicant]
US 9391856B2 · Kazerani · 2016 [cited by examiner]
US 9444858B1 · Boyle · 2016 [cited by examiner]
US 9713000B2 · Oertle · 2017 [cited by examiner]
US 9787560B2 · Maddux · 2017 [cited by examiner]
US 9880756B2 · Mutalik et al. · 2018 [cited by applicant]
US 9904603B2 · Mutalik et al. · 2018 [cited by applicant]
US 10122547B2 · Mahindra et al. · 2018 [cited by applicant]
US 10334446B2 · Ashrafi · 2019 [cited by applicant]
US 10341868B2 · Ross et al. · 2019 [cited by applicant]
US 10445698B2 · Hunn · 2019 [cited by applicant]
US 10559202B2 · Yang et al. · 2020 [cited by applicant]
US 10567291B2 · Sabella et al. · 2020 [cited by applicant]
US 10575244B1 · Gustafson · 2020 [cited by examiner]
US 10778794B2 · Wei et al. · 2020 [cited by applicant]
US 10915862B2 · Long et al. · 2021 [cited by applicant]
US 10938916B2 · Enat · 2021 [cited by examiner]
US 20010047241A1 · Khavakh · 2001 [cited by examiner]
US 20030065763A1 · Swildens · 2003 [cited by examiner]
US 20040064693A1 · Pabla · 2004 [cited by examiner]
US 20050210149A1 · Kimball · 2005 [cited by applicant]
US 20050273593A1 · Seminaro · 2005 [cited by examiner]
US 20080060054A1 · Srivastava · 2008 [cited by applicant]
US 20100223364A1 · Wei · 2010 [cited by examiner]
US 20100287019A1 · Guo · 2010 [cited by examiner]
US 20120076134A1 · Brownrigg · 2012 [cited by examiner]
US 20120221652A1 · Sainio · 2012 [cited by examiner]
US 20130103785A1 · Lyon · 2013 [cited by examiner]
US 20130111024A1 · Setia · 2013 [cited by examiner]
US 20130297669A1 · Wang · 2013 [cited by examiner]
US 20130332559A1 · Ivars et al. · 2013 [cited by applicant]
US 20140136952A1 · Zhu et al. · 2014 [cited by applicant]
US 20140164563A1 · Leekley et al. · 2014 [cited by applicant]
US 20150074296A1 · Eidelman · 2015 [cited by examiner]
US 20170366591A1 · Thomas · 2017 [cited by examiner]
US 20180041578A1 · Lee et al. · 2018 [cited by applicant]
US 20180052839A1 · Sharma · 2018 [cited by examiner]
US 20180130098A1 · Swanson · 2018 [cited by examiner]
US 20180132015A1 · Borrelli et al. · 2018 [cited by applicant]
US 20180241814A1 · Kristiansson · 2018 [cited by examiner]
US 20180288091A1 · Doron · 2018 [cited by examiner]
US 20180302440A1 · Hu · 2018 [cited by examiner]
US 20180331832A1 · Pulsifer · 2018 [cited by applicant]
US 20180357604A1 · Li et al. · 2018 [cited by applicant]
US 20180365635A1 · Lucrecio et al. · 2018 [cited by applicant]
US 20190007521A1 · Lipstone · 2019 [cited by examiner]
US 20190036764A1 · Canessa et al. · 2019 [cited by applicant]
US 20190188581A1 · Chabin · 2019 [cited by examiner]
US 20190236793A1 · Chan · 2019 [cited by applicant]
US 20190272496A1 · Moeller · 2019 [cited by applicant]
US 20190327180A1 · Todd et al. · 2019 [cited by applicant]
US 20190386995A1 · Chafe et al. · 2019 [cited by applicant]
US 20200008007A1 · Belghoul · 2020 [cited by examiner]
US 20200019626A1 · Todd et al. · 2020 [cited by applicant]
US 20200107403A1 · Frydman et al. · 2020 [cited by applicant]
US 20200125604A1 · Canessa et al. · 2020 [cited by applicant]
US 20200151655A1 · Khoche · 2020 [cited by applicant]
US 20200153786A1 · Ward et al. · 2020 [cited by applicant]
US 20200159511A1 · Frydman et al. · 2020 [cited by applicant]
US 20200177606A1 · Valluri et al. · 2020 [cited by applicant]
US 20200259836A1 · Kumar · 2020 [cited by examiner]
US 20200296155A1 · McGrath · 2020 [cited by examiner]
US 20210012282A1 · Smith et al. · 2021 [cited by applicant]
US 20210027452A1 · Mok et al. · 2021 [cited by applicant]
US 20210044675A1 · Frydman · 2021 [cited by examiner]
US 20210233045A1 · Singh · 2021 [cited by examiner]
US 20210400485A1 · Ergen · 2021 [cited by examiner]
US 20220201056A1 · Zajac · 2022 [cited by examiner]
US 20220224759A1 · Khosrowpour · 2022 [cited by examiner]
CN 111226429A · 2020 [cited by applicant]
KR 101823293B1 · 2018 [cited by examiner]
KR 101925268B1 · 2019 [cited by examiner]
Cited By (3)
US 12,452,208 US 12,567,032 US 12,712,941