gNB Notification Publish Space for Failure Detection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current communication networks face challenges in optimizing gNB failure detection and fast activation of fallback mechanisms, leading to prolonged service disruptions due to individual and inefficient failure detection processes among gNB logical entities.
Innovation Solution
A method involving the creation of a notification publish space and associated node lists across access network nodes, allowing for collaborative failure detection and rapid notification of failures, enabling faster fallback mechanism activation through shared identifiers and interfaces.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If individual failure detection processes are used among gNB logical entities, then each entity can independently detect failures, but service disruption time is prolonged due to inefficient detection
Solution Approach 1:
The patent merges individual failure detection processes into a centralized notification mechanism. A notification publish space is created where failure notifications are published and subscribed to by multiple gNB logical entities simultaneously. This combining approach allows all entities to detect failures at the same time rather than individually, reducing service disruption time while maintaining reliable failure detection across the network.
2Speed
If a centralized notification mechanism is implemented, then failure detection speed is improved, but system complexity increases due to notification publish space management
Solution Approach 1:
The notification publish space is designed as a universal mechanism that serves multiple gNB logical entities simultaneously. The same publish-subscribe infrastructure handles failure notifications for different entities without requiring separate mechanisms for each. This multi-functional approach reduces overall system complexity compared to implementing individual detection processes for each entity, while maintaining fast failure detection speed.
3Reliability
If fallback mechanisms are activated quickly, then service continuity is improved, but resource overhead increases due to standby entities
Solution Approach 1:
The patent implements preliminary action by pre-configuring standby gNB-CU-CP entities and establishing notification subscriptions before failures occur. When a failure is detected, the predefined fallback mechanism can be activated immediately without delay for configuration or setup. This advance preparation ensures service continuity while optimizing resource usage by only activating standby entities when actually needed.
Data Source
AI summary
A method includes transmitting an indication to create a notification publish space to a data storage function, the notification publish space including an identifier of a central entity of an access network node being monitored for failure; receiving an acknowledgement of the indication to create the notification publish space from the data storage function; and transmitting the identifier of the central entity and associated publish space information to at least one logical entity of the access network node or of another access network node being monitored for failure; wherein the identifier of the central entity is configured to be used with the at least one logical entity to subscribe to the notification publish space to receive information concerning a failure of the at least one logical entity of the access network node or of the another access network node.