MBMS Data Volume Reporting for Accurate Charging
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In Multimedia Broadcast/Multicast Service (MBMS) systems, there is no effective way to verify the delivery of data from the Broadcast-Multicast Service Centre (BM-SC) to user equipment (UE) before the Radio Access Bearer (RAB) is released, leading to potential overcharging and service delivery issues due to undetected errors like buffer overflow at the RNC or base stations.
Innovation Solution
Implementing a method to send a data volume query from a support node to the radio access network with parameters associated with the multimedia broadcast multicast service group, allowing for data volume reports to be received, which include the amount of successfully and unsuccessfully transmitted data, enabling the detection of undelivered data and facilitating accurate charging.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data volume reporting is not implemented for MBMS service groups, then the system operation remains simple and follows standard procedures, but undelivered data cannot be detected leading to potential overcharging and service delivery issues
Solution Approach 1:
The patent implements a feedback mechanism where the support node queries the radio access network for data volume reports regarding MBMS service groups. The RNC responds with reports indicating successfully and unsuccessfully transmitted data, enabling the support node to verify delivery and detect errors. This feedback loop resolves the contradiction by providing reliable service delivery verification while maintaining manageable system complexity through standardized reporting procedures.
Solution Approach 2:
The patent introduces an intermediary reporting system where the RNC acts as a mediator between the MBMS transmission process and the support node. The RNC collects data volume information and provides structured reports to the support node, which then uses this information for verification and charging decisions. This intermediary approach enables reliable delivery verification without requiring complex direct monitoring between all system components.
2Measurement precision
If data volume reports are implemented to detect undelivered data, then accurate charging records can be generated, but additional signaling overhead and processing requirements are introduced
Solution Approach 1:
The patent implements preliminary action by having the RNC maintain data volume information ready for reporting before queries are made. The support node sends queries at appropriate intervals rather than continuously, and the RNC prepares reports in advance when data becomes available. This approach enables precise measurement of data delivery while minimizing signaling overhead by avoiding continuous monitoring and reducing processing delays.
3Reliability
If continuous monitoring of MBMS data transmission is performed, then all delivery errors can be detected, but system resources are consumed and performance is impacted
Solution Approach 1:
The patent implements periodic action through scheduled data volume queries sent from the support node to the RNC at predetermined intervals during MBMS service delivery. This periodic monitoring enables reliable error detection by checking transmission status at regular intervals while consuming minimal system resources compared to continuous monitoring. The approach balances reliability and performance by using just enough monitoring to detect errors without overwhelming the network.
Data Source
AI summary
Multicast/broadcast messaging service (MBMS) arrangement, in which a broadcast/multicast service center delivers multimedia messages to a plurality of users via a gateway GPRS support node (GGSN) and via a serving GPRS support node (SGSN) and a radio access network (RAN), in association with a given temporary mobile group identity (TMGI) and using a single radio access bearer (RAB). Responsive to a given event, the SGSN sends to the RAN a data volume report query identifying said RAB by the TMGI or another unique parameter. The RAN responds with a data volume report that indicates the amount of unsent MBMS data. If so agreed, the SGSN will pass said amount to a charging gateway for compensation in charging for the MBMS service.