MTC-IWF Charging Data Record Generation for Control Plane
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current systems lack detailed methods for generating and transferring Charging Data Records (CDRs) for Small Data Transmission (SDT) and Machine-Type-Communication (MTC) device triggers over the control plane, with existing literature focusing on user plane charging and not providing sufficient details for control plane charging.
Innovation Solution
A Machine Type Communication-Inter Working Function (MTC-IWF) is introduced, comprising a relay unit to receive and deliver device trigger information, a generation unit to create CDRs with MTC-IWF addresses, and a transfer unit to send these CDRs to a Charging Data Function (CDF) for charging, along with a communication system that counts messages and generates CDRs for successful deliveries.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If charging for SDT and MTC device trigger over control plane is implemented, then charging capability is improved, but system complexity increases due to lack of existing detailed methods
Solution Approach 1:
The MTC-IWF is designed to perform multiple functions: it acts as a relay for device triggers, generates CDRs for charging, and interfaces with both the SCS and CDF. This multi-functional design allows the same network element to handle both control plane signaling and charging operations, avoiding the need for separate dedicated charging infrastructure and thus reducing overall system complexity while improving charging capability
Solution Approach 2:
The MTC-IWF serves as an intermediary between the SCS (Service Capability Server) and the CDF (Charging Data Function). It receives device trigger information from the SCS, generates the appropriate CDRs, and transfers them to the CDF. This intermediary role simplifies the architecture by centralizing the charging data generation function in one element rather than requiring direct integration between multiple charging and signaling components
2Measurement precision
If CDR generation and transfer details are specified, then charging precision is improved, but implementation difficulty increases
Solution Approach 1:
The patent specifies in advance the exact format and content requirements for CDRs generated by the MTC-IWF, including which fields must be populated (e.g., MTC-IWF address, device trigger information). By defining these requirements beforehand, network implementers can build systems that automatically generate compliant CDRs without requiring complex real-time decision logic, thus improving charging precision while reducing implementation difficulty
Solution Approach 2:
The patent defines specific parameters and fields that must be included in CDRs for control plane charging, such as the MTC-IWF address field and device trigger information fields. By standardizing these parameters, the patent enables precise charging measurements while providing clear implementation guidelines that reduce the complexity of building compliant charging systems
Data Source
Figure 1
Figure 2
Figure 3
AI summary
In order for charging SDT and MTC device trigger over control plane, there is provided a network node (40) that relays messages over a control plane (T5 and Tsp) between an MTC device (10) and an SCS (50). The network node (40) counts the number of messages successfully relayed, and generates a CDR in accordance with the counted number. The messages are SDT messages delivered from the MTC device (10) to the SCS (50), SDT messages delivered from the SCS (50) to the MTC device (10), or MTC device trigger messages delivered from the SCS (50) to the MTC device (10). The network node (40) transfers the CDR to an OCF (31) or a CDF (32).