Packet Counting in CUPS Control and User Plane Separation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current usage reporting systems in Control/User Plane Separation (CUPS) primarily measure network resources in terms of octets, time, and events, lacking the ability to count packets, which is essential for accurate traffic modeling and charging in mobile networks, particularly for Cellular Internet of Things (CIoT) services.
Innovation Solution
A protocol mechanism is introduced to enable the Control Plane (CP) entity to instruct the User Plane (UP) entity to perform packet counting, allowing measurements in terms of the number of packets transmitted, received, or total packets for PDU sessions or service data flows, and to report these counts to the appropriate recipient.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If usage reporting measures network resources in terms of octets, time, and events only, then the measurement system is simple and compatible with existing protocols, but it lacks the ability to count packets which is essential for accurate traffic modeling and charging
Solution Approach 1:
The patent extends the existing measurement framework by introducing a new measurement parameter (packet count) alongside the existing parameters (octets, time, events). This is achieved by modifying the Usage Reporting Rule (URR) structure to include a measurement method indicator that can specify packet counting, thereby enhancing measurement precision without fundamentally changing the overall system architecture
Solution Approach 2:
The measurement system is designed to support multiple measurement methods (octets, time, events, and packets) within a single unified framework. The UP function can perform different types of measurements based on the measurement method indicated in the URR, making the system multi-functional and adaptable to different charging and traffic modeling requirements
2Loss of information
If the Control Plane entity instructs the User Plane entity to perform packet counting, then accurate packet-based measurements are achieved for traffic modeling and charging, but the protocol complexity increases due to additional measurement instructions and reporting mechanisms
Solution Approach 1:
The patent introduces an intermediary mechanism where the Control Plane entity provisions Usage Reporting Rules (URRs) to the User Plane entity, which then autonomously performs the actual packet counting and generates usage reports. This intermediary URR structure acts as a mediator that carries measurement instructions from the CP to the UP and delivers measured information back, reducing direct protocol complexity while maintaining information accuracy
Solution Approach 2:
The system implements a feedback mechanism where the UP function measures packet counts according to CP-provisioned URRs and sends usage reports back to the CP function. This closed-loop feedback ensures accurate traffic information is captured and reported, enabling precise traffic modeling and charging decisions based on actual measured data
3Reliability
If packet counting is implemented for PFCP sessions, then charging and policy control functions gain accurate packet-based traffic data, but the existing usage reporting framework must be extended requiring modifications to Usage Reporting Rules and measurement methods
Solution Approach 1:
The patent makes the measurement framework dynamic by introducing a measurement method indicator in the URR that can be configured to specify different measurement types (octets, time, events, or packets). This dynamic configuration allows the system to adapt to different charging requirements without requiring separate static frameworks for each measurement type, balancing reliability needs with implementation complexity
Data Source
AI summary
Systems and methods to measure the number of packets in Control/User Plane Separation, CUPS, are provided. In some embodiments, a method performed by a Control Plane, CP, entity includes: determining that packet counting should be performed by a User Plane, UP, entity; providing measurement instructions to the UP entity for counting packets and identifying a recipient of a packet count if the CP entity is not the recipient; and, if the CP entity is the recipient of the packet count, receiving, from the UP entity, a packet count. In this way, a CP function is able to instruct a UP function to perform a measurement in terms of packets, e.g., a measurement of the number of packets transmitted.