5G Traffic Counting via Slice DNN and Access Network Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The complexity of 5G scenarios poses a challenge in designing effective traffic counting methods that can adapt to the diverse requirements of enhanced mobile broadband (eMBB), ultra-reliable and low latency communications (URLLC), and massive machine-type communications (mMTC) services, including managing traffic across slices, data network names (DNNs), and access networks (ANs, while ensuring accurate billing and network quality optimization.
Innovation Solution
A traffic/rate counting method that categorizes and aggregates traffic based on session information, including slice type, DNN, and access network, allowing for detailed tracking and display of traffic usage across different network layers, enabling users to manage and optimize network resource allocation and costs by selecting suitable network interfaces and applications based on quality indicators.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If traffic counting is implemented across multiple dimensions (slice, DNN, AN) in 5G networks, then measurement precision and network quality optimization improve, but device complexity and operational difficulty increase
Solution Approach 1:
The patent segments traffic counting into multiple independent dimensions (slice, DNN, AN) that can be configured and managed separately. Each dimension represents a distinct segmentation criterion for categorizing network traffic, allowing the system to handle complex 5G traffic patterns through modular, dimension-based classification rather than monolithic management.
Solution Approach 2:
The patent introduces multiple counting dimensions (slice, DNN, AN) as additional axes for traffic classification. This dimensional approach transforms traditional single-dimension traffic counting into multi-dimensional analysis, enabling precise traffic measurement across different network slices, data networks, and access networks simultaneously.
2Adaptability or versatility
If multi-dimensional traffic counting is implemented, then adaptability to diverse 5G scenarios improves, but ease of operation deteriorates
Solution Approach 1:
The patent creates a universal traffic counting framework that functions across all 5G service scenarios (eMBB, URLLC, mMTC) through a common multi-dimensional counting mechanism. The same counting architecture adapts to different service types and network configurations without requiring scenario-specific implementations, providing multi-functionality across diverse use cases.
Solution Approach 2:
The patent implements dynamic configuration capabilities where counting dimensions, rules, and parameters can be adjusted based on specific 5G scenario requirements. The system allows runtime modification of traffic counting behavior to adapt to changing network conditions, service demands, and operational priorities, making the framework flexible rather than rigid.
3Reliability
If detailed traffic tracking across slices, DNNs, and access networks is implemented, then network quality optimization improves, but loss of time in configuration and management increases
Solution Approach 1:
The patent enables preliminary configuration of traffic counting parameters, dimensions, and rules before actual traffic measurement begins. By pre-configuring counting frameworks, dimension selections, and threshold values, the system reduces runtime configuration needs and accelerates deployment, allowing network operators to establish robust traffic tracking without time-consuming setup during operation.
Data Source
AI summary
A network traffic/rate counting method includes: obtaining first session information of a first session of a terminal device, where the first session information includes: a slice of the first session, a slice type of a slice of the first session, a data network name DNN of the first session, or an access network AN used by the first session; and counting traffic of the first session into first slice traffic corresponding to the slice to which the first session belongs, or into first type slice traffic corresponding to the slice type of the slice to which the first session belongs, or into first DNN traffic corresponding to the DNN to which the first session belongs, or into first AN traffic corresponding to the AN.