Interrelated Service UI Orchestration for Unified Network Data
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing telecommunication service provider networks face challenges in efficiently integrating and presenting data across multiple systems and user interfaces, lacking intuitive and cohesive navigation and data interaction capabilities.
Innovation Solution
An intelligent user interface system that includes a service orchestration layer to electronically coordinate multiple software services, allowing data presentation and interaction across user interfaces to be synchronized and user permissions managed, using SmartTiles to provide a unified view of network data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple independent software services with separate user interfaces are used to manage different network functions, then service functionality and versatility are improved, but system complexity and difficulty of data integration increase
Solution Approach 1:
The system is divided into independent microservices that can be developed, deployed, and scaled separately. Each service handles a specific network function (e.g., billing, authentication, network management) while maintaining its own user interface. This segmentation allows high versatility while managing complexity through modular architecture.
Solution Approach 2:
An event bus serves as an intermediary layer that enables communication and data sharing between independent services. Events published to the event bus allow services to react to changes in other services without direct coupling, reducing system complexity while maintaining functionality.
2Ease of operation
If data is presented across multiple separate user interfaces, then service-specific data presentation is improved, but user navigation efficiency and data coherence deteriorate
Solution Approach 1:
The event bus provides universal communication capabilities across all services. A single event publication can trigger updates in multiple services simultaneously, allowing users to access related data across different service interfaces without manual navigation, thus reducing navigation time while maintaining service-specific presentation.
Solution Approach 2:
Services publish events when data changes, and other services subscribe to these events to automatically update their presentations. This feedback mechanism ensures that related data across multiple user interfaces remains coherent and synchronized, reducing the time users spend checking multiple interfaces for updated information.
3Stability of the object's composition
If services are tightly integrated to share data seamlessly, then data coherence is improved, but system flexibility and ease of maintenance worsen
Solution Approach 1:
The event bus acts as an intermediary that maintains data coherence through standardized event contracts rather than tight integration. Services publish events with defined schemas, and subscribers process these events independently. This approach ensures data coherence while maintaining loose coupling, making the system easier to maintain and modify.
Solution Approach 2:
The system uses configurable event subscription filters and data transformation rules that can be modified without changing the core service logic. This allows data coherence to be maintained through parameter adjustments rather than structural changes, improving ease of maintenance while preserving data consistency.
Data Source
AI summary
Example embodiments are directed towards an intelligent user interface for interrelated services. The data-rich ecosystem of a telecommunication service provider's wireless network is leveraged in creative and intuitive ways to bring data points to users' fingertips how they need it and when they need it. A single pane of glass is made up of selectable and controllable user interface elements that paint a larger picture together of the telecommunication service provider's network and individual components thereof. For example, the system may electronically provide a plurality of software services, each having a respective user interface (UI), and electronically orchestrate, at a service orchestration layer, the plurality of software services such that when any one service of the plurality of services is used, usage of the one service automatically affects what data is presented or how the data is presented in one or more respective user interfaces of other services of the plurality of services.