On-Demand Network Slicing Across Multiple Billing Platforms
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing billing systems for telecommunications networks are not agnostic and cannot support real-time or near-real-time changes to customer profiles for enterprise-level customers, hindering the provision of on-demand network slicing services without disrupting other operations.
Innovation Solution
A billing system agnostic method and system that allows for real-time changes to customer profiles, enabling on-demand network slice connections by using a Network as a Service (NaaS) runtime engine or network service platform to authorize and bill enterprise-level customers through multiple billing systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If existing billing systems are used for telecommunications networks, then billing operations can be performed, but real-time or near-real-time changes to customer profiles cannot be supported, hindering on-demand network slicing services
Solution Approach 1:
The system segments the billing architecture by introducing a separate profile management component that operates independently from the core billing system. The NaaS runtime engine handles profile changes and network slice provisioning separately, allowing real-time updates without disrupting the traditional billing operations. This segmentation enables the billing system to maintain its stability while adding real-time capabilities through the profile data repository and event subscription mechanisms.
Solution Approach 2:
The patent introduces a profile data repository and event subscription system as intermediaries between the billing system and network slice provisioning. When a profile change event occurs, the system subscribes to relevant events, retrieves updated profile data, and triggers appropriate network slice actions. This intermediary layer enables real-time profile changes without requiring modifications to the core billing system architecture.
2Reliability
If on-demand network slicing services are implemented, then seamless network communication can be provided, but existing billing systems cannot support real-time profile changes without disrupting other operations
Solution Approach 1:
The system performs preliminary actions by pre-configuring profile data in the profile data repository and establishing event subscriptions before network slice provisioning is needed. When a network slice request occurs, the system has already prepared the profile data and event handling mechanisms, enabling immediate provisioning without disruption to existing operations. This preliminary setup ensures both reliability and rapid service delivery.
Solution Approach 2:
The patent implements dynamic profile management where customer profiles can be updated in real-time based on event subscriptions. The system dynamically retrieves updated profile data when events occur and adjusts network slice provisioning accordingly. This dynamic approach allows the system to maintain reliable network communication while adapting to changing service requirements without disrupting other billing operations.
3Adaptability or versatility
If multiple billing systems are used for different enterprise-level customers, then customer-specific billing can be performed, but a billing system agnostic solution is needed for on-demand services
Solution Approach 1:
The patent creates a universal profile management framework that works across multiple billing systems. The profile data repository stores customer profiles in a standardized format that can be accessed by different billing systems. The event subscription mechanism and network slice provisioning logic are designed to be billing-system-agnostic, allowing the same framework to support multiple enterprise-level customers with different billing systems while maintaining ease of operation through centralized profile management.
Data Source
AI summary
A computer-implemented method for providing network slice connections in a telecommunications network includes receiving a request from a developer application to connect a user device associated with an enterprise level customer to a network slice. The request includes a client identifier and a device identifier. The method includes determining whether the user device is authorized to connect to the network slice based on the client identifier and the device identifier. The method includes identifying a particular billing system that is associated with the enterprise level customer. The method includes provisioning a service code to a customer profile of the enterprise level customer in the particular billing system. The method includes causing the developer application to connect the user device to the network slice. The method includes causing the developer application to bill utilization of the service feature to the enterprise level customer in the particular billing system.