M2M Device Profile Management via AAA Server
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current M2M communication systems lack the ability to dynamically add and manage profiles of M2M devices in communication carrier subscriber databases, requiring manual updates each time a new service agreement is made with an M2M service provider.
Innovation Solution
A method and apparatus for dynamically determining and transmitting the profile of an M2M device, including identifier information, service type, and service provider details to an AAA server, allowing for dynamic profile management and service provisioning based on device characteristics.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual updates are performed in the AAA server subscriber database each time a new M2M service agreement is made, then the profile information can be kept updated, but the administrative burden and time consumption increase significantly
Solution Approach 1:
The M2M device performs self-registration by automatically transmitting its profile information to the AAA server without requiring manual administrator intervention. The device includes identifiers, service type information, and other characteristics that enable automatic database updates, eliminating the need for manual profile management while maintaining accuracy
Solution Approach 2:
The M2M device prepares and includes its profile information in advance within its configuration or memory before attempting to access the network. This preliminary preparation allows the AAA server to automatically register and store the profile data during the initial connection attempt, preventing the need for subsequent manual updates
2Adaptability or versatility
If the AAA server stores profiles for all M2M devices, then complete service provisioning is enabled, but the device complexity and storage requirements increase
Solution Approach 1:
The profile information is segmented into essential identification elements (device identifier, service type, provider ID) that are stored in the AAA server database, while more detailed device-specific configurations remain local to each M2M device. This segmentation reduces the burden on the central database while maintaining complete service provisioning capability
Solution Approach 2:
The AAA server database is designed to handle multiple types of M2M device profiles using a universal storage structure that accommodates different service types and device characteristics through standardized fields. This universal approach simplifies the database architecture compared to maintaining separate specialized databases for each device type
Data Source
AI summary
An apparatus and a method support Machine to Machine (M2M) communication in a communication system. A method for providing an M2M service includes determining at least one of identifier (ID) information of an M2M device, ID information of an M2M Service Provider (MSP), and service type information of the M2M device to provide the M2M service. The method also includes determining a profile of the M2M device using the at least one information determined. The method further includes transmitting the profile of the M2M device to an Authentication, Authorization and Accounting (AAA) server.