Server Authentication Mediator for Device Registration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current network systems face challenges in effectively storing account data and device identification data in association with each other, leading to inefficiencies in device registration and service provisioning.
Innovation Solution
A communication system architecture that includes a terminal, a communication device, and a server, where each component transmits and stores registration requests and authentication data in a manner that associates account data with authentication data and device identification data, enabling secure and efficient registration and service provisioning.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If the server stores account data and device identification data separately without direct association, then the storage structure is simpler, but the efficiency of device registration and service provisioning deteriorates
Solution Approach 1:
The patent introduces authentication data as an intermediary element that connects account data and device identification data. The server stores authentication data that references both the account and the device, enabling efficient association without directly linking the two data types. This mediator approach allows the system to maintain separate storage structures while achieving efficient device registration and service provisioning through the connecting authentication data.
2Reliability
If the server implements a straightforward registration process, then the process is easier to implement, but security and reliability of data association deteriorates
Solution Approach 1:
The patent implements preliminary action by generating and storing authentication data before the actual device registration is completed. The server creates the authentication data that contains references to both account data and device identification data in advance, ensuring that the association is established with high reliability before the registration process finishes. This preliminary establishment of the association mechanism ensures data integrity while managing process complexity.
Solution Approach 2:
The system uses feedback mechanisms where the terminal receives authentication data from the server and uses it to complete the registration process. The terminal sends back confirmation or additional information, and the server updates the associations accordingly. This feedback loop ensures that the data associations are accurately established and verified, improving reliability while structuring the process in manageable steps.
3Loss of time
If the server processes all registration data centrally, then data consistency is maintained, but processing time and system load increase
Solution Approach 1:
The patent segments the registration process into multiple independent steps: account creation, device registration, and association establishment. Each step processes only the necessary data for that specific purpose, reducing the processing time for each individual operation. The authentication data acts as a segmented connector that maintains overall data consistency without requiring all data to be processed simultaneously in the center, thus balancing processing speed with data integrity.
Data Source
AI summary
A processor of a server is configured to receiving a first registration request from a terminal, storing first account and first authentication data in a memory of the server in association with each other, transmitting the first authentication data to terminal, receiving a third registration request from a communication device, storing device identification data and second authentication data in the memory in association with each other, transmitting the second authentication data to the communication device, receiving a fourth registration request including the first authentication data and the second authentication data, and storing the first account data associated with the first authentication data included in the fourth registration request and the device identification data associated with the second authentication data included in the fourth registration request in the memory in association with each other.


