Session-Type User Identifiers for Wireless Billing Precision
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current 3G wireless communication networks lack the ability to differentiate between types of communication sessions in billing, as Usage Data Records (UDRs) do not provide session type information, leading to inadequate charging mechanisms for varying network resource demands.
Innovation Solution
Implementing a method to select and use different user identifiers based on the type of communication session, allowing UDRs to include session type information, enabling a billing system to apply specific billing formulas for each session type.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If a single user identifier is used for all communication sessions, then the system is simple to operate, but billing precision deteriorates because session type information cannot be differentiated
Solution Approach 1:
The patent segments the single user identifier into multiple session-type-specific identifiers (e.g., NAI-PTT for push-to-talk sessions, NAI-Web for web browsing sessions). This segmentation allows the billing system to differentiate between session types and apply appropriate charging formulas, thereby improving billing precision without requiring users to manually manage complex identifier selections.
Solution Approach 2:
The patent introduces an intermediary mechanism (the session identifier mapping system) that automatically selects and substitutes the appropriate user identifier based on the communication session type. This intermediary handles the complexity of multiple identifiers behind the scenes, maintaining ease of operation for users while enabling precise billing through session-type-specific identifiers.
2Measurement precision
If Usage Data Records include session type information, then billing precision improves, but the complexity of the UDR format increases
Solution Approach 1:
The patent extracts session type information from the user identifier itself rather than adding it as a separate field in the UDR. By embedding session type indicators within the user identifier (e.g., different NAI formats for different session types), the solution improves billing precision while avoiding increases in UDR format complexity.
Solution Approach 2:
The patent makes the user identifier multi-functional by designing it to simultaneously serve as both a user identification mechanism and a session type indicator. This universality allows the existing UDR structure to convey session type information without requiring additional fields or increasing format complexity.
3Measurement precision
If different billing formulas are applied to different session types, then charging accuracy improves, but the system complexity increases
Solution Approach 1:
The patent performs preliminary action by pre-configuring the mapping between session types and user identifiers before billing processing occurs. The session identifier mapping system is established in advance, allowing the billing system to automatically determine the appropriate charging formula based on the user identifier without requiring complex real-time analysis, thereby improving charging accuracy while managing system complexity.
Solution Approach 2:
The patent implements a feedback mechanism where the user identifier provides information back to the billing system about the session type, enabling automatic selection of the appropriate billing formula. This feedback loop allows the system to adapt charging based on session type without requiring manual intervention or complex decision-making logic.
Data Source
AI summary
A user uses a wireless communication device to engage in a communication session over a packet-switched network. The communication session is one of a plurality of different session types, e.g., a push-to-talk (PTT) session or a Web browsing session. The user is identified in the communication session by a user identifier that is dependent on the session type. The user identifier used in a particular communication session is included in a usage record generated for that communications session. A billing system determines the session type from the user identifier in the usage record. Based on this session type, the billing system selects a billing formula to calculate a charge to the user for the communication session.