How rotanova/isc works
Project Type and Purpose
• The project is the “智慧安防管理平台” (Smart Security Management Platform) built on top of the asmoboot framework. It is intended as a full-stack, low-code management platform focused on security and surveillance. The platform supports device integration (such as cameras using GB28181/RTSP), incorporates AI algorithms for tasks like face recognition and behavior analysis, and even includes IoT device management.
• Its typical use cases include managing video streams for surveillance, configuring AI capabilities (both prepackaged and customizable), and providing complete permission, configuration, and device management setups for smart security applications.
Analysis of the File Structure
• The top-level project layout shows just a few items: a .gitmodules file, README.md, asmoboot, and asmoboot-web.
• The “asmoboot” directory likely contains the “backend” or core service components based on a Java framework (as indicated by the Java badge in the README).
• The “asmoboot-web” directory appears to hold the frontend part of the platform (and hints via the npm/vue badge that it uses Vue.js).
• The .gitmodules file indicates that there are external submodules (potentially shared libraries or components) that get integrated).
Key Components
a. Core Backend (asmoboot):
• This module underpins the business logic, low-code platform services, and REST API endpoints.
• It handles critical functionalities such as permissions management, device configuration, AI integration logic, and security/authentication services.
b. Frontend (asmoboot-web):
• The web client (likely built with Vue) which interacts with the core backend.
• It presents the user interface for management panels (dashboard, device configuration, AI management, etc.).
c. External/Supporting Services (as indicated in the README and deployment instructions):
• AI Server: Provides AI algorithm services (e.g., face detection, behavior analysis) and should be represented as a separate module that the backend communicates with.
• Image/File Server (MINIO): Acts as the image hosting/media storage service.
• System Monitoring/Authentication Service: Runs on a specified port (9877) for authentication and monitoring.
• SIP/国标 Service: Handles streaming, SIP device connectivity, and possibly PTZ control (the README specifies ports and configuration for this).
Relationships and Component Interactions
• The Frontend (asmoboot-web) sends requests (e.g., via REST API calls) to the Backend (asmoboot) for data and command execution.
• The Backend interacts and integrates with external services:
▸ API calls or service requests to the AI Server.
▸ Image/media upload/download with MINIO.
▸ SIP/streaming services for video feed integration.
Architectural Patterns and Design Principles
• The system uses a modular and decoupled architecture. The separation between asmoboot (backend) and asmoboot-web (frontend) represents the typical full-stack approach.
• Integration of external microservices (AI, image server, system monitoring) via RESTful APIs.
• That the design supports plug-in based AI capabilities—allowing new AI algorithms or customized modules to be added.