# US 2023/0056744 A1 · Roadside edge node central management > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2023/0056744 A1 - Document ID: US20230056744A1 - Status: Published application - Kind: A1 - Application number: 17/889,484 - Filed: 2022-08-17 - Published: 2023-02-23 - Earliest claimed: 2021-08-17 - Assignees: The Regents of the University of Michigan - Applicants: The Regents of the University of Michigan - Inventors: Tyler S. WORMAN - Web page: https://patentgrep.com/patent/US20230056744A1 ## CPC - H04L 67/53: using third party service providers - H04L 67/12: specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks - H04L 67/34: {involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416)} - H04W 4/38: for collecting sensor information - H04W 4/44: for communication between vehicles and infrastructures, e.g. vehicle-to-cloud [V2C] or vehicle-to-home [V2H] - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## Abstract A system and method for managing third-party software packages at a roadside edge node. The method includes: receiving a third-party software package at an edge node management controller that is located at a roadside edge node, wherein the edge node management controller is used to execute a software manager application; using the software manager application, installing the third-party software package at the roadside edge node; executing the third-party software package at the roadside edge node; and providing sensor information to the third-party software package indicating information concerning one or more sensors that are present at the roadside edge node. ## Claims ### Claim 1 A method for managing third-party software packages at a roadside edge node, comprising the steps of: receiving a third-party software package at an edge node management controller that is located at a roadside edge node, wherein the edge node management controller is used to execute a software manager application; using the software manager application, installing the third-party software package at the roadside edge node; executing the third-party software package at the roadside edge node; and providing sensor information to the third-party software package indicating information concerning one or more sensors that are present at the roadside edge node. ### Claim 2 (depends on 1) The method of claim 1, wherein the third-party software package is installed on the edge node management controller and executed on the edge node management controller. ### Claim 3 (depends on 1) The method of claim 1, wherein an application programming interface (API) is used by the third-party software package to communicate with the software manager application. ### Claim 4 (depends on 3) The method of claim 3, wherein the sensor information is provided to the third-party software package in response to a request from the third-party software package, and wherein the request and response are configured according to the API. ### Claim 5 (depends on 3) The method of claim 3, wherein the software manager application is configured to receive sensor data requests from the third-party software package, and wherein the sensor data requests are formed according to the API. ### Claim 6 (depends on 5) The method of claim 5, wherein the software manager application is configured to receive sensor data requests from one or more other third-party software packages in addition to the third-party software package, and wherein each of the sensor data requests from the one or more other third-party software packages is formed according to the API. ### Claim 7 (depends on 1) The method of claim 1, wherein the third-party software package is received from a third-party remote computer that is located remotely from the roadside edge node. ### Claim 8 (depends on 7) The method of claim 7, wherein the third-party software package is containerized according to specifications set forth by an application programming interface (API). ### Claim 9 (depends on 8) The method of claim 8, wherein the software manager application is configured in a manner that enables any third-party sensor package that is containerized according to the API to be installed at the roadside edge node. ### Claim 10 (depends on 1) The method of claim 1, wherein the executing step further comprises the third-party software package controlling the one or more sensors. ### Claim 11 A roadside central management system, comprising: a controller having a processor and a non-transitory, computer-readable memory storing computer instructions constituting a software manager application; and a network communications interface that includes hardware enabling data communications and that is communicatively coupled to the controller; wherein the computer instructions, when executed by the processor, cause the roadside central management system to: receive a third-party software package at an edge node management controller that is located at a roadside edge node, wherein the edge node management controller is used to execute the software manager application; using the software manager application, install the third-party software package at the roadside edge node; execute the third-party software package at the roadside edge node; and provide sensor information to the third-party software package indicating information concerning one or more sensors that are present at the roadside edge node. ### Claim 12 (depends on 11) The roadside central management system of claim 11, wherein the roadside central management system is installed at the roadside edge node. ### Claim 13 (depends on 12) The roadside central management system of claim 12, wherein the one or more sensors are connected to the controller, and wherein the controller is configured to implement an application programming interface (API) that is used by the third-party software package to communicate with the software manager application. ### Claim 14 (depends on 13) The roadside central management system of claim 13, wherein the sensor information is provided to the third-party software package in response to a request from the third-party software package, and wherein the request and response are configured according to the API. ### Claim 15 (depends on 13) The roadside central management system of claim 13, wherein the software manager application is configured to receive sensor data requests from the third-party software package, wherein the sensor data requests are formed according to the API. ### Claim 16 (depends on 15) The roadside central management system of claim 15, wherein the software manager application is configured to receive sensor data requests from one or more other third-party software packages in addition to the third-party software package, wherein each of the sensor data requests of the one or more other third-party software packages is formed according to the API.