How qaqo0o/smart5g-nonrtric-plt-ranpm works
Main Components
• Data Ingestion & Collection: Components such as “datafilecollector” (with FTP/SFTP and HTTP clients) are responsible for gathering files. They interact with configuration (e.g., certificates, truststores) and contain controllers/endpoints (e.g., StatusController) to monitor health.
• Data Transformation & Processing: The “pm‑file‑converter” module takes care of data conversion (e.g., XML to JSON) and includes components for Kafka integration and miniocollector functionality.
• Data Production & Distribution: The “pmproducer” module, with its repository, OAuth2, and Kafka topic listener implementations, handles the publishing of PM data to messaging systems.
• Logging & Metrics: “influxlogger” is designed to interface with time series databases like InfluxDB. It manages metric ingestion via Kafka, and configuration files indicate a REST client (AsyncRestClient) for sending PM logs.
• Additional Modules and Simulators: Modules such as “es‑rapp”, “https‑server”, “o1‑sim”, and “pm‑rapp” serve additional roles (for predictive analytics, secure communications, or simulation of network functions).
• Deployment & Orchestration: The “docker‑proj” directory and the “install/helm” folder (with multiple Helm charts) define the containerized deployments and the Kubernetes resource definitions. They outline services such as Kafka clusters (Strimzi), minio instances, InfluxDB setups, and other microservices.
Interactions and Data Flow
• Flow from external or network sources (for instance, FTP/SFTP sources or HTTPS endpoints) feeding into the Datafile Collector.
• Passage of processed or raw files from the Datafile Collector to the PM Producer, possibly via an internal API or directly to messaging (Kafka) channels.
• Components for authentication & security (e.g., OAuth2 elements in both the Datafile Collector and PM Producer) that secure the data flow.
• Integration with external infrastructure services like Kafka, InfluxDB, and potentially a storage service (Minio) for file/object storage.
Architectural Patterns and Technologies
• Modular Microservices: Each main functionality (collection, transformation, production, logging) is divided into separate services.
• Containerization & Orchestration: Use Docker and Helm to deploy these services on Kubernetes, as shown by the extensive Helm charts and Dockerfiles.
• Asynchronous Messaging: The use of Kafka-related listeners and producers in several services indicates event-driven communication.
• Security & Configuration Management: The existence of separate configuration directories (with certificates, truststores, and keystores) and OAuth2-related classes shows security is built into each service.
• RESTful Interfaces: The presence of Swagger configuration classes and REST client implementations in several modules implies internal APIs built on REST principles.