Network Slice Selection for Flexible Application Billing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current mobile network architectures, particularly in 5G networks, face challenges in differentiating and billing for various service flows due to limited flexibility and scalability, especially in vehicular networks, where existing taxation methods are expensive, ineffective for encrypted traffic, and lack customer involvement in changing taxation conditions.
Innovation Solution
A method implemented in a network access device that determines the appropriate network slice for application data based on quality of service, security, and terminal criteria, allowing selection of network slices with specific pricing conditions, enabling the access device to initialize taxation and manage flow allocation between service providers and customers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If network slicing is deployed to provide flexible service differentiation, then service flexibility and scalability are improved, but flow metering and charging complexity increases
Solution Approach 1:
The patent segments the charging function by network slice, with each slice having its own charging parameters and billing rules. The network slice selection function selects appropriate slices based on service requirements, and the charging system applies corresponding billing policies, enabling flexible service differentiation without requiring complex unified charging analysis of all traffic
Solution Approach 2:
The patent introduces a network slice selection function as an intermediary between the access device and the charging system. This function translates service requirements into appropriate network slice selections, which then carry embedded charging information, simplifying the charging process by pre-configuring billing parameters with the slice selection rather than requiring post-hoc traffic analysis
2Measurement precision
If deep packet inspection is used to identify traffic for charging, then charging accuracy is improved, but processing time and cost increase
Solution Approach 1:
The patent applies preliminary action by pre-associating charging parameters with network slices before traffic flows are established. The network slice selection function selects appropriate slices and attaches charging information in advance, so that when traffic is routed through the selected slice, charging can be performed without requiring real-time deep packet inspection of individual data packets
Solution Approach 2:
The patent replaces the mechanical deep packet inspection approach with a higher-layer abstraction using network slice identifiers and associated charging parameters. Instead of inspecting individual packets to identify traffic patterns, the system uses the pre-selected network slice's metadata to determine charging applicability, significantly reducing processing overhead while maintaining charging accuracy
3Extent of automation
If existing charging solutions are implemented, then charging capability is provided, but customer involvement in charging conditions is lost
Solution Approach 1:
The patent implements feedback mechanisms where the access device communicates charging conditions associated with selected network slices to the terminal. The terminal can then provide feedback on acceptable charging conditions, allowing customers to accept or reject proposed charging terms before traffic is routed, thereby maintaining customer involvement in the charging process while preserving automated slice-based charging capability
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Method for fee-charging data of an application routed on a section of a communication network A method for fee-charging data of an application transmitted on a section of a communication network (100), implemented in a device (10) for accessing the network (100) and comprising a step of detecting an activation of the application, a step of transmitting an identification message comprising information relating to the identification of the application intended for an entity (51) for managing sections of the network, a step of receiving, from the entity (51) for managing sections of the network, a notification message comprising at least one identifier of a section of the network and of fee-charging parameters associated with the at least one identifier and, depending on the received message, a step of initialising the fee-charging of the data of the application.