Postal Security Device Shared Across Multiple Servers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current postage dispensing systems face issues with server failures, where a postal security device (PSD) cannot be easily transferred between servers without data loss or corruption, and is limited to handling single transactions, requiring multiple PSDs for simultaneous user support.
Innovation Solution
Implementing a system with a SCSI bus interface or Ethernet connection to allow multiple servers to access and share a PSD, enabling seamless failover to a backup server without manual intervention and maintaining data integrity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If multiple PSDs are coupled to servers to handle simultaneous transactions, then transaction handling capacity is improved, but system complexity and failure risk increase
Solution Approach 1:
Multiple servers share a single PSD through a shared memory bus architecture, consolidating what would traditionally require multiple physical PSD units into one shared resource. This merging approach maintains the ability to handle simultaneous transactions while reducing overall system complexity and hardware requirements.
Solution Approach 2:
The PSD is designed with universal access capabilities through the shared memory bus, allowing any connected server to initiate transactions with the PSD. This multi-functionality enables a single PSD to serve multiple servers simultaneously, improving resource utilization efficiency.
2Ease of operation
If PSD is coupled directly to a specific server, then transaction processing is simplified, but failover capability is lost
Solution Approach 1:
The system transitions from a static server-PSD coupling to a dynamic shared access model where servers can connect to the PSD through the shared memory bus. This dynamic architecture allows servers to be added or removed without affecting PSD functionality, and enables automatic failover when a server fails.
Solution Approach 2:
The shared memory bus acts as an intermediary between servers and the PSD, enabling indirect access. Instead of direct coupling, servers communicate with the PSD through the shared memory bus, which facilitates both simplified transaction processing and reliable failover capabilities.
3Loss of information
If PSD must be physically detached and reattached for server failover, then data integrity is maintained, but service disruption occurs
Solution Approach 1:
The shared memory bus architecture is configured in advance to support multiple servers simultaneously. When a server fails, the system already has the capability to redirect transactions to remaining servers without requiring physical intervention or data transfer, eliminating service disruption while maintaining data integrity.
Solution Approach 2:
The system replaces the mechanical process of physically detaching and reattaching PSD hardware with a software-based failover mechanism through the shared memory bus. This substitution eliminates the need for manual intervention and physical reconfiguration, enabling seamless failover that maintains both data integrity and continuous service.
4Productivity
If customer account information is stored on PSD, then transaction processing is efficient, but data transfer risk increases during server migration
Solution Approach 1:
The shared memory bus serves as an intermediary storage layer between servers and the PSD. Customer account information is accessed through this shared memory interface, allowing efficient transaction processing while providing a stable data environment that prevents data loss during server migration or failover events.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Systems and methods that allow a PSD (12) to be physically shared by multiple servers (20a, 20b, 20c) such that if a server fails, another server can be utilized as a backup server for the PSD without any manual intervention or moving of the PSD and without risking loss of data from the PSD. A PSD is interfaced by an interface device (16) to a system level bus (18) that allows for multiple initiators. An initiator is any server that can access and issue commands over the system level bus to access the PSD. When one of the servers fails, the functionality of the server can be rolled to a backup server which will be able to access the PSD over the bus.