Capability Broker for Network Architecture Simplification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The complexity of existing network architectures for communications operators hinders the efficient sharing of capabilities with third-party service providers, particularly in supporting direct-to-consumer content services and context-aware services, due to numerous interfaces and lack of control mechanisms, as well as the diversity of terminal and network types.
Innovation Solution
A capability broker is introduced between traffic proxies and enabler servers, providing a unified capability interface for traffic proxies and a service interface for service providers, allowing for simplified communication and access to network capabilities, while also managing terminal and network context information to optimize content message distribution.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a traditional network architecture with multiple direct interfaces between traffic proxies and enabler servers is used, then direct access to capabilities is achieved, but the system complexity and maintenance difficulty increase significantly
Solution Approach 1:
The patent introduces a capability broker as an intermediary component between traffic proxies and enabler servers. The capability broker provides a unified capability interface that abstracts the complexity of multiple enabler server interfaces, allowing traffic proxies to access network capabilities through a single standardized interface while the broker handles the complexity of interfacing with multiple enabler servers internally.
Solution Approach 2:
The capability broker serves multiple functions: it acts as a unified interface for traffic proxies, manages access to multiple different enabler servers, provides capability abstraction, and handles service provider interactions. This multi-functional component reduces the overall system complexity by consolidating what would otherwise require numerous direct interface implementations.
2Adaptability or versatility
If multiple direct interfaces are provided between traffic proxies and enabler servers, then direct capability access is enabled, but the maintainability of the network deteriorates
Solution Approach 1:
The capability broker serves as a mediator that isolates traffic proxies from changes in enabler server interfaces. When enabler servers are replaced or updated, only the capability broker needs to be adapted, not the traffic proxies. This significantly improves maintainability by localizing the impact of interface changes to a single component.
3Adaptability or versatility
If the network opens capabilities to service providers, then new services can be created, but the control over capability usage is lost
Solution Approach 1:
The capability broker acts as a controlled intermediary between service providers and network capabilities. It provides service providers with access to enabler server capabilities through a standardized interface while maintaining the operator's control over capability usage, access rights, and billing. The broker can enforce policies, monitor usage, and manage service provider interactions without service providers needing direct access to network infrastructure.
Data Source
Figure 1A~1B
Figure 2
Figure 3A~3B
AI summary
Disclosed are a capability broker, a related messaging system and methods. The capability broker is placed in new network architecture between traffic proxies and enabler servers. The capability broker is equipped with a capability interface adapted to receive a capability request pertaining to a request of at least one capability. The capability broker is adapted to use one or more messages to obtain the requested at least one capability from one or more enabler servers responsive to receiving said capability request, and to provide a response to said capability request on the basis of the obtained capability.