Central Office Point of Delivery Stateless Execution Architecture
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The complexity of conventional central office point of delivery architectures in broadband access networks, which are stateful and lead to intricate implementations, hindering efficient execution of network attachment and configuration tasks.
Innovation Solution
A method utilizing an execution state database and stateless execution service functionalities, connected via a message bus, with distinct execution stages (access, processing, and device stages) to process network attachment and configuration tasks, allowing for a simplified and adaptable architecture.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a conventional stateful central access controller architecture is used, then network attachment tasks can be executed, but the system complexity increases and adaptability decreases
Solution Approach 1:
The patent segments the monolithic stateful central access controller into separate stateless execution service functionalities and a dedicated execution state database. This segmentation allows each component to have a specific, simplified responsibility while the system collectively maintains full functionality, thereby reducing individual component complexity while preserving overall adaptability.
Solution Approach 2:
The patent extracts the state management functionality from the execution service functionalities and places it in a separate execution state database. This extraction enables the execution services to be stateless and more adaptable, while the database handles state persistence, resolving the contradiction between adaptability and complexity.
2Device complexity
If stateless execution service functionalities are used, then complexity is reduced and adaptability is enhanced, but state management becomes more challenging
Solution Approach 1:
The patent introduces an intermediary mechanism (message bus with message identifiers) that connects stateless execution service functionalities with the execution state database. This intermediary enables reliable state management by allowing services to reference and manipulate state through structured messages without maintaining state internally, thus reducing complexity while ensuring reliability.
3Adaptability or versatility
If a monolithic controller architecture is used, then implementation is straightforward, but adding or removing components becomes difficult
Solution Approach 1:
The patent segments the controller architecture into independent, modular execution service functionalities that can be individually added, removed, or modified. Each service is self-contained and communicates through standardized messages, making the system easier to implement and more flexible compared to a monolithic architecture.
Solution Approach 2:
The patent creates a universal message bus infrastructure that can handle various types of network attachment tasks and configuration tasks through a common interface. This universal framework allows different execution services to be implemented using the same base infrastructure, enhancing flexibility while maintaining ease of implementation through standardized patterns.
Data Source
AI summary
A central office point of delivery within a broadband access network of a telecommunications network includes: access network facing nodes; and a control function and/or a switching fabric and/or service edge nodes. Execution of network attachment tasks and/or further functional or configuration tasks within the central office point of delivery involves using an execution state database as well as stateless execution service functionalities being assigned to different execution stages realized within the central office point of delivery, and a message bus connecting the different execution stages, wherein the execution stages comprise at least an access stage, a processing stage, and a device stage, wherein the execution service functionalities—in order to process or execute the network attachment tasks and/or further functional or configuration tasks—generate a plurality of messages on the message bus and consume a plurality of messages from the message bus.


