China Mobile intends to build a terminal management and service system, through the collection of information such as the activation, configuration and use of terminal products, combined with the terminal company's supply chain management of the product, to achieve the control of the full life cycle of the product. It is required that starting from March 2017, all customized and non-customized Android terminals entering China Mobile's product library must support terminal management functions. (Required required)
Terminal self-registration
When starting up for the first time, the IMEI of the terminal and other basic information needed by the system must be sent to the system server in the form of data. The server is responsible for parsing this HTTP message and establishing a list of correspondences between the terminal IMEI and ICCID on the server side. The corresponding relationship between the card on the terminal side changes, and the terminal must perform self-registration again.
▪ Terminal heartbeat collection
The client regularly collects terminal service configuration information and reports it to the server. The service configuration information includes but is not limited to APN configuration and VoLTE switch status collection. The service configuration capability can be expanded subsequently.
▪ The terminal service configuration
management platform server judges whether it is necessary to make configuration changes to the terminal based on the heartbeat information uploaded by the terminal. The server sends configuration instructions to the corresponding terminal service configuration processing flow. The terminal user operation flow should follow the commands issued by the server. Now only supports Volte configuration
▪ Application software management
The terminal management and service system client reads terminal application software data and reports to the server every 7 days. Application data content: terminal IMEI, terminal third-party APP list, app open time, app open times, app consumption flow.
Access process
A. Fill in the email
Fill in the "Multi-modal terminal appkey application template" form, please refer to the prompt content in the form for the filling method
Note:
1. Due to the large number of application mails, there may be omissions. If no reply mail is received within 2 working days, please send the original application mail again
2. Please resend the email when there is a new product access. If you have multiple accounts, you can log in and use it, which will not affect the storage.
3. If the product cannot be found in the "China Mobile Intelligent Hardware Products and Quality White Paper", it can be included in the "XX New", NB-IoT products (modules and complete terminals) in each category. Fill in the NB-IoT product for the level classification, and fill in the module or terminal according to the actual product for the second classification.
B. Log in to the adaptation management platform
1. Adaptation platform address: https://shipei.fxltsbl.com
2. The account password is the account password provided in the application email (password provided by the DM platform)
3. After logging in to the adaptation platform, you can download relevant documents and code files on the platform
C, integrated adaptation
The integration is divided into a debug version and a commercial version. In the integration test phase, please use the debug version (the report address is the adapted platform coap://shipei.fxltsbl.com:5683). The report of the debug version can be queried by the account password on the adapted platform Report the situation. After the integration is completed, please click "Test Cases_Multi-modal Terminal Test Cases (For Manufacturers)"
Test cases for testing.
Note: Use cases with priority "optional" can be selected and tested according to the actual situation of the product. If the test conditions are not met or items cannot be tested, please mark "N/A" directly and explain in the remarks.
Android platform:
Please provide the file directly to the R&D personnel, and the R&D will select the JDK version corresponding to the SDK for integration according to the actual situation of the product, and add the android terminal technical support QQ number: 2430416846 for technical consultation
Linux platform:
Please provide the files directly to the R&D personnel, who will carry out integration related work according to the content in the "readme", and add the Linux terminal technical support QQ number: 2361994271 for technical consultation
Other platforms:
Self-developed according to the "Multi-modal Terminal Reporting Interface Specification", and the relevant reports can be satisfied. At the same time, add the platform technical support QQ number: 2427714190 for technical consultation
D, test and release
After completing all tests of the manufacturer's self-test use cases, it is necessary to replace the commercial version (the report address is the commercial platform coap://m.fxltsbl.com:5683 ) and submit it for testing . After the quality department reports that the test passes, the product will be released in the commercial version .
What is the FAQ for the basic process of accessing DM?
1) Fill in the "multi-modal terminal appkey application template" and send it to the designated email address to obtain the ①adapted platform account password ②each manufacturer's unique APPKEY (also written as APPID)
2) Log in to the adaptation platform and download all integrated DM related materials in the document management
3) According to the material integration "debug version" DM, log in to the adaptation platform and report the verification data according to the test case
4) After passing the test, replace the "commercial version" and send it to test
How to deal with the device without IMEI ?
Answer: Devices without IMEI need to apply for CMEI at the terminal company. The CMEI will only be allocated when it is put into the library, so you can generate a fake CMEI for testing according to the IMEI rules during the debugging phase.
How to apply for CMEI?
The CMEI submitted for commercial platform testing must be real. The application for the top 8 tui of CMEI is in the marketing system. This field will be automatically generated when the product is reported.
Does the SDK have logs?
Answer: Android platform SDK, in the debug version, will generate log files in the root directory, the file path is MTLog
How to judge the successful integration?
Answer: The Android platform SDK will print the logs related to the success of the report, the self-registration function prints "onRegistrationSuccess", and the heartbeat prints "onUpdateSuccess". After seeing these words, you can go to the adaptation platform to verify the reported results. After confirming the success, please carry out self-test according to "Test Cases". In the use cases, "Required" is a required test item, and "Optional" use cases are marked. Please perform reasonable selection tests with the actual functions of the equipment. Functions that are not supported by the capabilities Can N/A
What is the interval between heartbeats?
Answer: The adapted platform version is 3 minutes, and the official commercial version is 24 hours.
How to transfer parameters to the device imsi without sim or unable to insert sim card?
Answer: Just pass null.
Why is there only a successful self-registration and no heartbeat success?
Answer: The heartbeat function needs to be started after the self-registration report is successful, and the report is triggered when the heartbeat cycle time arrives. If in
If there is a restart, process is killed, etc., the heartbeat timer will also be terminated and you need to re-register.
What should I do if the test fails?
First, confirm the failure cause by yourself, whether the test failure is caused by the incorrect reporting address. After confirming that it is correct, you can contact the technical support QQ (or QQ group) communicated in the debugging stage to try to solve the problem, and at the same time contact the platform "service window" to coordinate the next round of testing related matters.
What should I do if the application for APPKEY email is not received?
Due to the large number of applicants, individual emails may have been missed, and no reply will be received within 1 working day. Please send it directly based on the original email. The relevant person in charge will give priority to processing after seeing the email.
Demo and document download link:
Call in code:
MTSdk.init(ContextUtil.getInstance(), MobileUtil.getDeviceID(mContext), null, MobileUtil.getIMSI(mContext), "Key");
Add the following registration information to mainfest:
<service
android:name="cn.richinfo.mt.service.MTService"
android:exported="false" >
</service>
<receiver android:name="cn.richinfo.mt.receiver.MTBroadCastReceiver" >
<intent-filter>
<action android:name="cn.richinfo.mutm.action.HEARTBEAT" />
<action android:name="android.richinfo.net.conn.CONNECTIVITY_CHANGE" />
</intent-filter>
</receiver>
As shown below, add SDK and so library to the project
After making these preparations, monitor the status of the network and start calling after connecting to the network. The final effect is as follows:
