Service Orchestration Across Multiple Domains
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Communication network operators face challenges in quickly and reliably integrating new services into their native service domain, as existing methods are time-consuming and costly, and over-the-top services are not integrated with billing and assurance, limiting their control and influence.
Innovation Solution
A method of orchestrating services across different service domains by a processing unit, which involves receiving a service definition object, adding subscriber-specific data, and sending a service creation request to a sponsor service provider to subscribe to selected services, allowing for easy enhancement of existing services and integration of new features.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If network operators design and implement new services themselves, then service quality and control are improved, but time consumption and cost increase
Solution Approach 1:
The patent introduces a service orchestration system that acts as an intermediary between service providers and network operators. This system enables operators to subscribe to and integrate third-party services through standardized interfaces, maintaining service quality control while significantly reducing implementation time and cost compared to designing services in-house
Solution Approach 2:
The service orchestration system provides universal service integration capabilities that work across multiple service domains and providers. It implements a standardized service subscription mechanism that can handle diverse service types (voice, data, messaging, etc.) through a common interface, eliminating the need for operators to develop separate integration solutions for each service
2Adaptability or versatility
If network operators integrate all service infrastructure themselves, then service control and influence are improved, but device complexity and cost increase
Solution Approach 1:
The patent extracts specific service functionality from the operator's core infrastructure and delegates it to specialized service providers. The service orchestration system maintains control by managing service subscriptions and configurations, while the actual service delivery is handled by external providers, reducing infrastructure complexity while preserving adaptability
Solution Approach 2:
The service infrastructure is segmented into distinct functional components: service subscription management, service configuration, and service delivery. This segmentation allows operators to control the management layer while outsourcing the delivery layer to specialized providers, reducing overall system complexity while maintaining service control
3Adaptability or versatility
If OTT services are used, then service variety is improved, but integration with billing and assurance deteriorates
Solution Approach 1:
The service orchestration system acts as an intermediary that bridges OTT services with operator billing and assurance systems. It implements standardized interfaces that enable seamless integration, allowing diverse OTT services to be subscribed to and managed through the operator's existing infrastructure without requiring complex custom integration for each service
Data Source
Figure 1
Figure 2
Figure 3
AI summary
The present invention concerns a method of orchestrating services across at least two different service domains in a communication network. The method comprises: (a) setting up a service orchestration rule set between a home operator, managing a first service domain and a sponsor service provider, managing a second service domain for obtaining a data structure for a service definition object, the home operator being identified by a home operator identifier; (b) receiving a list of available services from the sponsor service provider, each service on the list being identified by a service identifier; (c) receiving (91) a subscriber selection of at least one service from the list, the subscriber being identified by a subscription identifier; (d) adding (95) a first set of data to the service definition object, the first set of data comprising at least subscriber specific data; (e) sending (96) a service creation request to the sponsor service provider for subscribing to the selected service, the request comprising the home operator identifier, the subscription identifier, the service identifier of the selected service, the service definition object and a service instance identifier; and (f) receiving (99) a response from the sponsor service provider, the response comprising the service definition object complemented with a second set of data to allow the selected service to be executed.