Factory Activation Server for Mobile Device Testing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In the factory setting, mobile devices cannot be activated for testing due to unreliable connections with the activation server, and using a test SIM card or debug OS is not feasible for all devices, requiring an additional restore station that reduces production rates.
Innovation Solution
A method for securely factory activating mobile devices involves transmitting activation information to a factory activation server, generating and cryptographically signing a factory activation record, and verifying it using a factory public key to allow temporary activation for testing, with the option to dynamically set the activation and reboot times.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a test SIM card is used to activate the device for testing, then the device can be tested at OQC stage, but this solution is not feasible for devices that do not use a SIM card
Solution Approach 1:
The patent introduces a factory activation server as an intermediary between the device and the activation process. This server provides a specialized activation mechanism that works for all device types (with or without SIM cards) by generating factory activation records that bypass the need for traditional SIM card-based activation, thus resolving the compatibility issue while maintaining testing feasibility
Solution Approach 2:
The activation process is segmented into different modes: customer activation (requiring SIM card) and factory activation (using factory activation records). This segmentation allows devices to be activated appropriately based on their context, enabling universal testing capability across different device types
2Adaptability or versatility
If a debug OS is used to activate the device in debug mode, then the device can be tested at OQC stage, but an additional restore station is required to replace the debug OS with the customer OS, reducing production rates
Solution Approach 1:
The patent applies preliminary action by loading the customer OS directly onto devices destined for OQC stage during the shipping settings station, rather than using a debug OS. The device is then activated in factory mode using cryptographic verification, eliminating the need for a separate restore station and maintaining continuous production flow
Solution Approach 2:
The activation mode parameter is changed from customer activation (requiring SIM card and host connection) to factory activation (using factory activation records with cryptographic verification). This parameter change allows the device to be activated directly at the OQC station without requiring OS reinstallation, thus maintaining production rates
3Reliability
If the device is activated using the customer activation process, then the device can be properly tested, but the connection between the activation server and the factory is not sufficiently reliable to support the production rates needed at the factory
Solution Approach 1:
The factory activation record is generated and cryptographically signed in advance by the factory activation server before the device reaches the OQC station. This preliminary action eliminates the need for real-time connection during activation, allowing fast, reliable activation that supports high production rates
Solution Approach 2:
The factory activation server acts as an intermediary that provides pre-signed activation records, decoupling the activation process from the need for continuous reliable connection. The cryptographic signature serves as a trusted mediator that validates the activation without requiring ongoing communication infrastructure
4Adaptability or versatility
If the device is activated in the factory environment, then the device can be tested at OQC stage, but it is not desirable to allow the factory environment to have access to the activation server for security purposes
Solution Approach 1:
The factory activation server and cryptographic key system serve as a secure intermediary layer. The server signs activation records using private keys that never leave the secure environment, while the signed records can be verified by devices in the factory. This intermediary mechanism enables testing capability while maintaining security boundaries
Solution Approach 2:
Instead of giving direct access to the activation server, the system creates cryptographic copies (signed activation records) that contain all necessary activation information. These records can be distributed safely to the factory environment without exposing the original server or private keys, enabling testing while preserving security
Data Source
AI summary
To securely factory activate a mobile device according to authorized records, factory activation server generates and sends a signed factory activation record including a signed factory activation ticket. Signed factory activation record and ticket are cryptographically signed using factory private key stored in factory activation server. Factory private key is different from customer private key stored in the activation server that provides activation tickets for customer activation. If factory activation record is valid, application processor (AP) included in the device performs factory activation of the device which includes AP activating to allow for factory testing and rebooting at a predetermined reboot time. Wireless communication processor (BB) included in the device verifies the factory activation ticket and if valid, BB performs factory activation including: BB registering to a cellular telephone communications network for factory testing, and unregistering from the network after a predetermined unregistering time. Other embodiments are also described.