583
edits
DeepStream Reference Designs/Project Architecture/High Level Design: Difference between revisions
DeepStream Reference Designs/Project Architecture/High Level Design (view source)
Revision as of 18:01, 10 May 2022
, 10 May 2022→AI Manager
| Line 18: | Line 18: | ||
This module is in charge of receiving the information data coming from Camera Capture and executes the AI operations necessary to obtain useful information from the transmitted data. Within its responsibilities, the AI manager interacts with entities called engines, which abstract specific implementations on how to perform AI video analysis to infer business rules, depending on the current context of the application. Each engine provides methods to manage the flow of processed information, through basic operations such as create, start, stop and delete. | This module is in charge of receiving the information data coming from Camera Capture and executes the AI operations necessary to obtain useful information from the transmitted data. Within its responsibilities, the AI manager interacts with entities called engines, which abstract specific implementations on how to perform AI video analysis to infer business rules, depending on the current context of the application. Each engine provides methods to manage the flow of processed information, through basic operations such as create, start, stop and delete. | ||
The implementation of the engines is based on the [https://developer.nvidia.com/deepstream-sdk DeepStream SDK], which provides a set of tools to perform AI operations during streaming analysis. | The implementation of the engines is based on the [https://developer.nvidia.com/deepstream-sdk DeepStream SDK], which provides a set of tools to perform AI operations during streaming analysis. This DeepStream implementation is part of the project's framework, so the module is reusable and independent of any custom applications that need to use its services. | ||
Although the AI manager contemplates AI operations, he is not responsible for executing actions depending on the information analyzed. The output of this module will be sent to the Action dispatcher component. Even so, the AI Manager does monitor the necessary flow since the engines process the streamings through a component called Inference Listener, and they know how to parse said information to transmit it correctly to the modules that need it, through a component called Inference Parser. Both the Inference Listener and the Inference Parser provide a well-defined interface, so that they abstract their implementations, without depending on any specific technology or protocol to handle such information. | |||
=== Action Dispatcher === | === Action Dispatcher === | ||