M2M Gateway Service Layer Charging System
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current service layer charging mechanisms lack flexibility in differentiating application-level information and service context, leading to inefficient charging models that fail to adapt to varying service flows and content types, and lack real-time decision-making capabilities for online charging.
Innovation Solution
The implementation of a flexible service layer charging system that utilizes a flow-based model, enabling different charging methods, rates, and measurements based on application and service context, with the ability to configure rating information and perform real-time online charging through advanced message queuing protocols and resource-oriented architecture.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional service layer charging mechanisms are used, then billing records are generated, but the charging model lacks flexibility in differentiating application-level information and service context
Solution Approach 1:
The charging system is segmented into multiple independent components: service layer charging function, transport network charging function, rating function, and offline charging function. Each component handles specific charging tasks independently, enabling flexible differentiation of application-level information while maintaining manageable system complexity through modular architecture.
Solution Approach 2:
The patent introduces a service layer dimension above the traditional transport network charging layer. This new dimension enables charging based on application-level information and service context, providing flexibility without overwhelming complexity by operating at a higher abstraction level rather than redesigning the entire charging system.
2Productivity
If flow-based charging model is implemented, then real-time online charging is enabled, but system complexity increases
Solution Approach 1:
A service layer charging function acts as an intermediary between the flow-based charging model and the existing billing system. This intermediary handles real-time online charging decisions and translates them into formats compatible with traditional billing infrastructure, enabling real-time capability while managing complexity through intermediate processing.
Solution Approach 2:
Rating information and charging rules are pre-configured and stored in the service layer charging function before actual charging events occur. This preliminary preparation enables rapid real-time charging decisions without complex calculations during service delivery, improving productivity while keeping the real-time system relatively simple.
3Reliability
If multiple CDRs are generated for events involving several network nodes, then complete billing records are created, but redundant records increase
Solution Approach 1:
The service layer charging function consolidates charging data from multiple transport network CDRs into a unified service layer CDR. This merging process maintains complete billing information while eliminating redundancy by aggregating records at the service layer, where a single CDR can represent the complete service transaction across multiple network nodes.
Data Source
AI summary
The present application is at least directed to an M2M gateway apparatus. The apparatus includes a non-transitory memory having instructions stored thereon for service layer online charging of a service layer event. The apparatus also includes a processor operably coupled to the non-transitory memory configured to execute a set of instructions. One of the instructions includes sending, to a service layer charging function of an M2M server, a service layer rating request message for the service layer online charging of the service layer event detected by the M2M gateway. The service layer event is triggered by an application registered to the M2M gateway and that performs a read or write operation on a resource of the M2M gateway. Another one of the instructions includes receiving, from the service layer charging function of the M2M server, a rating response including the calculated amount of service units required for the M2M gateway to process the service layer event. The resource is a uniquely addressable element having a Universal Resource Identifier (URI) and is a representation that can be manipulated via RESTful Create, Retrieve, Update, and Delete requests.