https server client validation and retrieving specific data from server pre entered against each client

The whole project is related to telecom so untill unless u r telecom expert like LTE, 4G, 3gpp , u will not understand... But in between one functionality may be related to you, so i [login to view URL] that only.. there is device called Femto which is nothing but a LTE transmitter , whe. It turn on it will try to establish [login to view URL] and send request message to staging server(your part) and staging server has to respond in certain format the reaponse message after validating the femto.. you have to prepare staging server with let's say in mysql data base in which you have to enter few hundred or more femtos serial no , mac id and other info related to that femto( these info will be given to u by me in a csv file) when request message come from femto the staging server must validate and send response message in fixed format... I will give u the format of request and response message.... All this communication between client([login to view URL]) and server( [login to view URL] server ) must be on https, the incoming request n response shud be https incoming client connection message format { "rmno:femto": { "version": "0.1", "device": { "serial_number": "ABCD123", "hardware": "Sercomm XYZ", "software_version": "12.1.1" } } } response message we want in following format { "rmno:femto": { "version": "0.1", "segw-info": { "segw-fqdns": [ "[login to view URL]", "[login to view URL]" ], "ike-proposals": "aes128-sha256-modp2048", "esp-proposals": "aes128-sha1", "key-exchange": "ike2", "rekey": true, "reauth": true, "ike-lifetime": "24h", "lifetime": "6h" }, "ems-info": { "ems-fqdns": [ "[login to view URL]", "[login to view URL]" ], "ems-port": "8080" }, "ca-info": [ { "ca-fqdn": "[login to view URL]", "ca-path": "root/ca", "ca-port": "8080", "ca-subject": "rmno-femto-CA", "ca-protocol": "https" }, { "ca-fqdn": "[login to view URL]", "ca-path": "root/ca", "ca-port": "8080", "ca-subject": "rmno-femto-CA", "ca-protocol": "https" } ], "ntp-info": { "ntp-servers": [ "240b:c01A:9117::1211:0:1", "240b:c01A:9117::1111:0:1" ] } } }