Spectrum Sharing Controller Fallback for Communication Failure
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current spectrum sharing communication systems lack a reliable means to ensure service continuity in case of communication failures between the repository and controller, leading to potential service degradation due to the need to deactivate cells when the communication status is unknown.
Innovation Solution
Implementing a method that determines communication failures between the repository and controller, allowing for temporary or permanent continued use of spectrum resources, including maintaining cell activity, power reduction, or deactivation, with defined actions based on a safe mode fallback plan to prevent service disruption.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the system deactivates cells upon communication failure between repository and controller, then compliance with regulatory and incumbent restrictions is ensured, but service continuity deteriorates
Solution Approach 1:
The system performs preliminary actions by establishing a safe mode fallback plan before communication failure occurs. The controller stores fallback configuration parameters and maintains a database of incumbent restrictions locally, enabling it to continue operating in a compliant manner even when disconnected from the repository. This preliminary preparation resolves the contradiction by allowing service continuity while maintaining compliance through pre-stored regulatory rules.
Solution Approach 2:
The controller is designed to be self-sufficient by locally storing incumbent restriction data and fallback configurations. When communication with the repository fails, the controller autonomously enforces restrictions using its local database without requiring real-time repository communication. This self-service capability resolves the technical contradiction by maintaining both service continuity and regulatory compliance independently of continuous repository connection.
2Duration of action of stationary object
If the system maintains cell activity during communication failure, then service continuity is improved, but risk of non-compliance with incumbent restrictions increases
Solution Approach 1:
The safe mode fallback plan acts as an intermediary mechanism between the controller and incumbent restrictions during communication failure. The fallback plan contains pre-approved configuration parameters and restriction rules that mediate between the need for service continuity and compliance requirements. This intermediary resolves the contradiction by enabling cell activity while ensuring restrictions are enforced through the fallback plan's predefined rules.
Solution Approach 2:
The system provides beforehand cushioning by maintaining a local database of incumbent restrictions and fallback configurations that cushion against potential non-compliance during communication failure. This preparatory cushioning allows the controller to operate safely without real-time repository connection, resolving the contradiction by protecting both service continuity and compliance through pre-stored protective measures.
3Reliability
If persistent connection techniques are implemented between repository and controller, then communication reliability is improved, but system complexity and cost increase
Solution Approach 1:
The invention extracts the critical compliance-enforcement functionality from the continuous communication channel and embeds it locally in the controller. By taking out the incumbent restriction database and fallback configuration storage from the repository-controller communication interface, the system achieves communication reliability for essential functions without requiring complex persistent connections. This extraction resolves the contradiction by separating compliance enforcement from continuous communication requirements.
Solution Approach 2:
The system uses simple, lightweight fallback configuration parameters and local databases instead of complex persistent communication infrastructure. The fallback plan is a compact, self-contained configuration set that provides sufficient compliance assurance without requiring expensive or complex continuous communication systems. This approach resolves the contradiction by achieving communication reliability for critical functions through simple, disposable-like fallback mechanisms rather than complex persistent connections.
Data Source
AI summary
An approach for enhancing service continuity in the case of a communication failure between a repository and a controller of a spectrum sharing communication system as described. The repository is operable to at least one of store and generate restrictions governing use of a set of spectrum resources, and the controller is operable to receive the restriction from the repository and to enforce the restrictions A method implementation performed, for example, by the controller may comprise determining occurrence of a communication failure between the repository and the controller and, in response to the communication failure, taking one or more actions that result in an at least temporary continued use of spectrum resources under control of the controller.