RPS Work Process

Refer to the figure, it shows the process RPS works process.

1.

When phone power on, it will try to get the following file from the factory config sever path.
1). Factory000x.bin
2). Cfg000x.xml
3). $mac.cfg
4). Cfg$mac
5). Cfg$mac.xml
The factory config server path is: https://rps.htek.com/index.php/fn/g

All the file get info will be send to RPS server:
Get: https://rps.htek.com/index.php/fn/g /factory000x.bin
Get: https://rps.htek.com/index.php/fn/g /cfg000x.bin
Get: https://rps.htek.com/index.php/fn/g /$mac.cfg
Get: https://rps.htek.com/index.php/fn/g /cfg$mac
Get: https://rps.htek.com/index.php/fn/g /cfg$mac.xml

2.

The RPS server will check the request, if the phone require for cfg$mac and cfg$mac.xml, it will redirect the URL to the one you have set on the server.
In the example, when phone try to visit the url:
https://rps.htek.com/fn/g /cfg001fc11a9664
or https://rps.htek.com/fn/g /cfg001fc11a9664.xml ,
the server will redirect it, response code 302 and the url which has been set before. The example mac have been set point to http://192.168.0.54/cfg


Phone get the response: "====302=====http://192.168.0.54/cfg/cfg001fc11a9664"
And "====302=====http://192.168.0.54/cfg/cfg001fc11a9664.xml"


Then phone will try to get the configuration file through the URL.

3.

After getting the configuration file, phone will reboot with this file.

After rebooting, phone has loaded the configuration file on your server.