Envelope Reporting in 3GPP CP-UP Architecture
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing solutions fail to efficiently support envelope reporting in radio communication networks with separated control plane (CP) and user plane (UP) functions, leading to unnecessary complexity and non-3GPP agnostic UP functions.
Innovation Solution
Implement a mechanism where the CP function sets a time quota mechanism (TQM) and reporting triggers in a usage reporting rule (URR), instructing the UP function to generate usage reports upon envelope closure, thereby managing the complexity of time-based measurement and envelope reporting within the CP function.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If envelope reporting is implemented in a radio communication network with separated CP and UP functions, then reporting efficiency and accuracy are improved, but device complexity increases due to the need for coordination between CP and UP functions
Solution Approach 1:
The patent divides the envelope reporting function into two separate parts: the CP function handles control plane operations including setting TQM and receiving usage reports, while the UP function handles user plane operations including monitoring traffic and generating envelope closure reports. This segmentation allows each function to operate independently with well-defined interfaces, improving reporting efficiency without creating unnecessary complexity in either component.
Solution Approach 2:
The patent extracts the time-based measurement and envelope reporting logic from the UP function and places it in the CP function. The CP function sets the TQM parameters and determines envelope closure timing based on received usage reports, while the UP function simply monitors traffic and reports envelope closures. This extraction improves overall system efficiency by centralizing control logic while keeping the UP function simple and 3GPP agnostic.
2Measurement precision
If the UP function implements time-based measurement and envelope reporting, then measurement precision is improved, but the UP function loses 3GPP agnostic property and gains unnecessary complexity
Solution Approach 1:
The patent extracts the TQM configuration and envelope reporting logic from the UP function and relocates it to the CP function. The UP function receives simple instructions to monitor traffic and report envelope closures, while the CP function handles the complex tasks of setting TQM parameters, determining envelope closure timing, and generating usage reports. This maintains measurement precision while keeping the UP function simple and vendor-neutral.
Solution Approach 2:
The patent introduces the CP function as an intermediary between the traffic monitoring process and the reporting process. The CP function receives usage reports from the UP function, determines envelope closure timing based on TQM parameters, and generates the final usage reports for charging. This intermediary role allows the UP function to remain simple and 3GPP agnostic while still achieving precise time-based measurement through coordinated operation.
Data Source
AI summary
A method performed in a CP node. The method comprises setting a TQM in a URR to which its corresponding SDFs are applicable for envelope reporting, setting at least one reporting trigger in the URR, to instruct the UP function to generate a usage report upon closure of an envelope, setting a measurement method in the URR, to instruct the UP function to collect usage of volume, time and/or event, sending the set URR to the UP function, receiving one or more usage reports from the UP function, in response to the sent URR, wherein the received usage report(s) comprises at least a usage report trigger set to envelope closure, determining a starting time and/or an ending time for each envelope, based on the received usage report(s), and storing each envelope, with the determined starting time and/or ending time, for online or offline charging.


