Modular Control System Resource View for Thin Client State Monitoring
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Modular access control systems face challenges in managing multiple devices and configuring controllers and peripherals, leading to complexities such as misconfiguration, compatibility issues, and resource management inefficiencies, particularly in large-scale systems where hardware and logical implementations are not separated.
Innovation Solution
The system introduces a method where controllers in a distributed access control system define primary and logging resources, enabling thin clients to view state and event information without storing it, and allowing logging resources to manage historical data, thereby reducing computational load and improving configuration management by separating logical and hardware implementations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If thin clients store state and event information locally, then access to historical data is improved, but computing resources and storage capacity are wasted
Solution Approach 1:
The patent extracts the storage function from thin clients and centralizes it in logging resources. Thin clients no longer store state and event information locally, instead accessing historical data through logging resources that specialize in data retention. This separation eliminates the need for thin clients to maintain storage capacity while preserving full access to historical information.
Solution Approach 2:
Logging resources serve multiple functions: they store state information, maintain event logs, and provide historical data access to multiple thin clients simultaneously. This universal resource eliminates redundant storage across multiple clients and optimizes computing resource utilization system-wide.
2Adaptability or versatility
If controllers manage both hardware control and data storage, then system functionality is improved, but device complexity increases
Solution Approach 1:
The patent segments controller functions into distinct components: primary resources handle hardware control operations while logging resources manage data storage and historical information. This functional segmentation reduces controller complexity by separating control logic from data management responsibilities.
Solution Approach 2:
Logging resources act as intermediaries between thin clients and primary resources. They mediate data access requests, allowing thin clients to retrieve historical state and event information without direct interaction with control hardware, thereby simplifying the controller's operational complexity.
3Ease of operation
If thin clients handle both viewing and storing information, then data accessibility is improved, but configuration management becomes complex
Solution Approach 1:
The patent extracts the storage configuration from thin clients and consolidates it in logging resources. Thin clients are configured only for data viewing and access, while logging resources are configured for data retention and management. This separation simplifies configuration management by eliminating redundant storage configurations across multiple clients.
Data Source
Figure 1
Figure 2A~2B
Figure 3A
AI summary
A method may include receiving a request to define a primary resource. The primary resource may enable access to a primary handler that corresponds to a logical entity that controls a device or a port or another resource. The method may include identifying a primary domain object for the primary resource. The primary domain object maps the primary resource to the primary handler. The primary domain object represents a state of the primary resource. The method may include identifying an interface for the primary resource. The interface may be configured to receive a command through a link from a client. The method may include receiving a state request associated with the interface for the primary resource, wherein the primary domain object handler is configured to send a state message indicating the state of the primary resource in response to the request.