Group Messaging Server Consolidated Billing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional billing systems for multi-party messaging in mobile telecommunications networks face challenges with data storage and transmission due to the duplication of messages across networks, leading to inefficiencies and potential fraudulent activities.

Innovation Solution

A data processing method and system that uses a group messaging server to store and transmit messages with a common message identifier, allowing for efficient grouping and generation of charging data, reducing data storage and transmission by billing related messages with a single interconnect fee.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If per-message billing is used for group messaging, then accurate charging for each message can be achieved, but data storage and transmission requirements increase significantly

Engineering Contradiction:
Improvecharging accuracyVSAvoiddata storage and transmission
Core Design Contradiction:
Measurement precisionVSQuantity of substance

Solution Approach 1:

The patent merges multiple individual message billing records into a single consolidated billing record for the entire group messaging session. Instead of creating separate billing entries for each message sent to each recipient, the system consolidates all messages into one billing transaction, reducing data storage and transmission requirements while maintaining accurate charging.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent segments the billing process into two distinct stages: (1) message delivery stage where messages are routed to recipients without generating billing data, and (2) consolidation stage where a single billing record is created after all message delivery is complete. This segmentation allows accurate charging while minimizing intermediate data storage and transmission.

Inventive Principle:
Principle #1Segmentation

2Measurement precision

If each message is billed separately between networks, then interconnect charges can be accurately calculated, but the complexity of billing management increases

Engineering Contradiction:
Improveinterconnect charge calculationVSAvoidbilling management complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent combines multiple interconnect charge calculations into a single consolidated calculation. Instead of separately calculating charges for each message between networks, the system aggregates all interconnect messages and calculates a single charge, significantly reducing billing management complexity while maintaining accurate interconnect charge calculation.

Inventive Principle:
Principle #5Merging (Combining)

3Reliability

If message duplication is performed for all group recipients, then complete message delivery is ensured, but data transmission volume increases

Engineering Contradiction:
Improvemessage delivery completenessVSAvoiddata transmission volume
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent performs message duplication in advance before billing data generation. Messages are duplicated and delivered to all group recipients first, and only after delivery is complete is the single consolidated billing record created. This preliminary action ensures complete message delivery while minimizing the volume of billing-related data transmission.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP3059934B1Group messaging system and method
Publication Date: 2019.08.07 VODAFONE IP LICENSING LTD
  • EP3059934B1 patent drawingFigure 1
  • EP3059934B1 patent drawingFigure 2
  • EP3059934B1 patent drawingFigure 3

AI summary

A data processing method performed in a group messaging server of a mobile telecommunications network, the method comprising the steps of receiving an incoming message at the group messaging server from a remote user terminal, the message being for distribution to a group of users; storing details of the incoming message in a messaging log, the details comprising a message identifier received with the incoming message; identifying at least one recipient from the group of users to which the incoming message should be transmitted; transmitting an outgoing message to each of the at least one recipient, wherein the outgoing message comprises at least part of the incoming message and the message identifier; storing details of each outgoing message in the message log, the details comprising the message identifier; and processing the message log to identify groups of messages, wherein the groups of messages are identified by having a common message identifier, and generating charging data based on the groups of messages.