Interface Document For The Integration of Electronic Personal Safety Device (EPSD) with Electronic Personal Safety System (EPSS)

Transcription

1 Interface Document For The Integration of Electronic Personal Safety Device (EPSD) with Electronic Personal Safety System (EPSS) Ver 1.0 DXX BC By Broadcast & Communication Group Centre for Development of Advance Computing (C-DAC) Thiruvananthapuram 1 P a g e

2 Interface Document For The Integration of Electronic Personal Safety Device (EPSD) with Electronic Personal Safety System (EPSS) COPYRIGHT All rights reserved. This document or any part thereof may not, without the prior written consent of Centre for Development of Advance Computing (CDAC), be copied, reprinted or reproduced in any material form including, but without prejudice to the foregoing and not by way of exception photocopying, transcribing or storing in any medium or translating into any language, in any form or by any means, including but not limited to, electronics, mechanical, xerographic, optical, magnetic, digital or other methodology. DISCLAIMER These specifications are being provided to you strictly for informational purposes solely for the purpose of developing devices or applications that interact with Electronic Personal Safety System (EPSS). These specifications are proprietary to CDAC and constitute the intellectual property of CDAC. All title and intellectual property rights in and to the specifications is owned exclusively by CDAC; other than as expressly set forth herein, no license or other rights in or to the specifications and intellectual property rights related thereto are granted to you. CDAC reserves the right to withdraw, modify, or replace the specifications at any time, without notice. No agreement is provided by CDAC regarding the level, scope, or timing of CDAC's implementation of the functions or features discussed in these specifications. THESE SPECIFICATIONS ARE PROVIDED TO YOU "AS IS", "WITH ALL FAULTS" AND CDAC DISCLAIMS ANY AND ALL WARRANTIES, EXPRESS, IMPLIED, STATUTORY OR OTHERWISE TO THE SPECIFICATIONS. CDAC WILL NOT BE LIABLE FOR ANY INCOMPLETENESS OR INACCURACIES. CDAC WILL NOT BE LIABLE FOR ANY INDIRECT, SPECIAL, INCIDENTAL, PUNITIVE, OR CONSEQUENTIAL DAMAGES HOWEVER CAUSED, WHETHER IN CONTRACT, TORT OR UNDER ANY OTHER THEORY OF LIABILITY, RELATING TO THE SPECIFICATIONS OR THEIR USE, EVEN IF IT HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. It is further agreed by you that, by using these specifications, you agree not to copy, reproduce, or permit access to the information contained in the specifications except to those with a need-to-know for the purposes stated above. 2 P a g e

3 Revision History Issue No Rev. No Release Date Reason for Re-issue Total Doc. Pages Initial Release 27 3 P a g e

4 PREFACE Centre for Development of Advanced Computing (C-DAC) is the premier R&D organization of the Department of Electronics and Information Technology (DeitY), Ministry of Communications & Information Technology (MCIT) for carrying out R&D in IT, Electronics and associated areas. C-DAC has emerged as a premier third party R&D organization in IT&E (Information Technologies and Electronics) in the country working on strengthening national technological capabilities in the context of global developments in the field and responding to change in the market need in selected foundation areas. In that process, C-DAC represents a unique facet working in close junction with DeitY to realize nation s policy and pragmatic interventions and initiatives in Information Technology. One of our mission is to evolve technology solutions - architectures, systems and standards for nationally important problems. Electronic personal safety system is a complete eco-system for assisting women, children & elderly people in distress and can be used by any one. Electronic Personal Safety System (epss) is an integrated solution for personal security where instant police assistance is provided to a person in extreme distress or feeling high threat to safety. The system basically focuses on helping women, children and elderly people when they need immediate help. An electronic personal security device (epsd) that comes in different form factors can be used by them. The holder can just press the SoS button in the device to signal the Police Control Room for help on critical situations. On receipt of SoS message, the details of the person in distress along with location on city map will be displayed at the Police control room. The control room will now be able to track the victim and pass all the information to the nearest Police control room (PCR) vehicle for immediate action. Location of the victim on GIS map and shortest route to reach victim, will also be displayed at the Mobile Data Terminal (MDT) of the selected PCR vehicles. This system is developed and deployed using FOSS. These technical specifications describes a standard format for Emergency Message that need to be send to the Electronic Personal Safety System developed by Centre for Development of Advanced Computing (C-DAC). The emergency message contains the location information of a person in distress who requires emergency support. This document describes the communication protocol and operation sequence between the EPSD and EPSS. This enables the device manufacturers develop EPSDs of different form factors that can be integrated with the EPSS. 4 P a g e

5 Contents 1 Introduction Overview Abbreviation Definitions EPSS Control Centre: Automated Dial 100 System (AD100 System): Emergency Message: Electronic Personal Safety Device or EPSD: EPSS Network: EPSS registration portal: EPSS Registered User: Authorized Number: Scope Stakeholders Constraints Need References Operation Sequence EPSD Initialization Introduction Precondition Operation Emergency message flow Introduction P a g e

6 2.2.2 Precondition Operation Control Centre Initiated Tracking Introduction Precondition Operation EPSD Test Flow Introduction Precondition Operation DEVICE DE-INITIALIZATION Introduction Precondition Operation Message Details Type 1: Messages from EPSD to EPSS Authenticate Message Emergency Message Stop Message Cancel Message Test Message Type 2: Messages to EPSD Start Message Authenticate Success Authenticate Failure P a g e

7 3.2.4 Stop Message Initiate Tracking Test Acknowledgement Annexure Device Specifications Device Type codes P a g e

8 1 Introduction 1.1 Overview Electronic Personal Safety System (EPSS) is a personal Safety system designed and developed by Centre for Development of Advance Computing (C-DAC) aimed to provide the citizens an ability to instantaneously receive emergency Police help. The system can be integrated with the Automated Dial 100 system of the city so that a person in distress receives immediate Police help. A person need to possess an Electronic Personal Safety Device (EPSD) which can be a smart phone loaded with EPSS mobile application or an electronic device that has the capability to send an emergency message in a specific format (explained in this document) as a GSM SMS or a data packet to the EPSS control centre 1.2 Abbreviation EPSS EPSD DCRMS MDT GSM GPS SMS GPRS PDU CTI CDMA PSTN Electronic Personal Safety System Electronic Personal Safety Device Distress Call Response Management System Mobile Data Terminal Global System for Mobile Communications Global Positioning System Short Message Service General Packet Radio Service Protocol Description Unit Computer Telephony Integration Code Division Multiple Access Public Switch Telephone Network 1.3 Definitions EPSS Control Centre: This refers to the central site where the EPSS backend server infrastructure is installed, deployed and monitored. This can be centralized or distributed depending on the architecture Automated Dial 100 System (AD100 System): This is an automated system to handle Public Distress by using PSTN, GSM/CDMA/Wireless Media, CTI based Solution which handles these distress calls efficiently from Police control room, using multiple vehicle mount terminals and GPS based Automatic Vehicle Tracking 8 P a g e

9 System for navigation and guidance. The AD100 system is also known as Distress Call Response Management System (DCRMS) Emergency Message: The term Emergency message in this document represents a message framed as per the specific format defined in this document with the geographical information of the person in distress, sent to the EPSS Control Centre as a GSM SMS or a data packet Electronic Personal Safety Device or EPSD: This is a GPS enabled electronic device capable of sending Emergency message to the EPSS Control Centre, with an easily accessible panic/sos button to trigger the emergency message. The button can be either a physical button or a soft button EPSS Network: The EPSS network comprises of the network containing the EPSDs, service provider s network, EPSS backend servers deployed in the Control Centre and Mobile Data terminals mounted on rescue vehicles EPSS registration portal: The website which is used for registering a user to EPSS. EPSD users need to register in this portal to avail the service EPSS Registered User: A person who has successfully registered in the registration portal Authorized Number: The authorized number is the EPSS Control Centre phone number which is the only number from which the EPSD should accept commands after it is initialized. This number is received during the EPSD initialization process mentioned in Section Scope This document describes the communication protocol and operation sequence between the EPSD and EPSS. This enables the device manufacturers develop EPSDs of different form factors that can be integrated with the EPSS 1.5 Stakeholders Stakeholders comprises of all groups that have an interest in integrating with EPSS because those groups are more likely to be affected by changes or amendments made in this document. The stakeholders can be categorized as follows: 9 P a g e

10 Device manufacturers who can manufacture EPSDs in different form factors which are capable of sending the Emergency messages in the specific format to EPSS Control centre. Mobile application developers who can develop mobile apps in various mobile operating systems which can be used to send out Emergency messages in the specific format to EPSS Control centre 1.6 Constraints 1.7 Need SMS (Short Message Service) as specified by the ETSI (standards GSM and ) can contain up to 160 characters. There are two ways to receive and send SMS messages: a Protocol Description Unit (PDU) and Text mode. The EPSS supports SMS sending and reception in text mode only. The PDU format is not supported at this point of time. So the EPSD should be capable of sending and receiving SMS in text mode. The network aspects related to service provider and delay in delivery of SMS are outside the scope of this specification (i.e. the network connectivity, latency & SMS delay and other service provided related factors will not be discussed). To implement EPSS effectively it is important for the public to possess cost effective EPSDs of their choice and convenience. So it is important that various device manufacturers to come up with EPSDs in various form factors acceptable to the users. This document guides the device manufacturers and mobile app developers to develop devices or applications 1.8 References GSM SMS SMPP 3.4 Protocol: GPS Standards NMEA : Please refer the document DXX BC epsd Technical Specification for Device Specifications 10 P a g e

11 2 Operation Sequence This chapter provides the operation sequence of the EPSS network. Before going to the message details, understanding the operation sequence is important so that the necessity of each message and its importance in the system is known before designing the EPSD. Each EPSD in the EPSS network has to be compliant in performing the following operation sequence. Some operation sequences are mandatory and some are optional. The mandatory sequences need to be implemented in all EPSDs and optional features can be implemented at the device manufacturer s discretion. The details of various types of messages associated with the flow and the related parameters are explained in detail below. The various operation sequences supported in the EPSS is listed in the table below. Sl No Sequence Name Support in EPSD 1. EPSD Initialization Mandatory 2. Emergency Message Flow Mandatory 3. Control Centre Initiated Tracking Flow Optional 4. EPSD Test Flow Optional 5. EPSD De-Initialization Mandatory Table 1- Operation Sequence Associated Messages START AUTH AUTH_ACK AUTH_FAIL EMR_MSG STOP_MSG CANCEL_MSG INIT_TRK STOP_MSG TEST_MSG TEST_ACK UNAUTH UNAUTH_ACK 2.1 EPSD Initialization Introduction The EPSD initialization flow is used for initializing new EPSDs that are being introduced to the EPSS network Precondition Before performing this step the device user has to ensure that he/she is an EPSS registered user. After successful registration in the EPSS registration portal, the user will receive an SMS with the EPSS control centre number of his region. The user needs to have this SMS before starting this step. Also the EPSD should be powered on after installing the SIM card. 11 P a g e

12 2.1.3 Operation The user triggers the initialization process by sending the START message in a specific format to the EPSD. (The details of parameters associated with the message are explained in the Section 3.2.1). Figure 1 - EPSD Initialization When the EPSD receive the START message it should send the AUTH message to the EPSS control room number and on successful authentication it will receive an AUTH_ACK SMS which contains the configuration parameters like Server IP, port, message sending interval 12 P a g e

13 and EPSS control centre number. The device should have the capability to decode this SMS and save the configuration parameters to device storage so that it can be used for sending Emergency message when needed. Also the EPSS Control centre number received in AUTH_ACK message should be stored as the only authorized number to issue commands to the EPSD. The EPSD should accept SMS commands (like STOP, INITIATE TRACKING etc. explained later in this document) only from the authorized number. If the user registration was unsuccessful or he/she hasn t registered in the EPSS registration portal then authentication will fail. When such users send AUTH message AUTH_FAIL will be received. After sending AUTH message the EPSD should wait for 30 minutes for the response. If the response message (AUTH_ACK or AUTH_FAIL) is not received it should retry sending the AUTH message for 3 more times. If the operation doesn t succeed after 3 retries then the EPSD should send back a SMS to user mobile indicating that the initialization failed. If the AUTH_ACK or AUTH_FAIL is received then also the EPSD should indicate the status to the user by sending SMS to user mobile indicating whether the initialization succeeded or failed. The message flow is as shown in Figure 1. NOTE: The device manufacturers may provide LED indications in the device for various conditions and provide the details which denote whether the AUTH_ACK or AUTH_FAIL was received so that end user can know the device status. 2.2 Emergency message flow Introduction The Emergency Message flow is triggered when the user trigger the emergency message Precondition The EPSD user should have successfully performed the EPSD initialization Operation When the user trigger the emergency message on EPSD using the SOS/panic button, the device should send an emergency message in format mentioned in Section 3 Message Details to the EPSS control centre. The device should send the emergency message either as data packets or as GSM SMS based on network availability. When the emergency message is received at the EPSS control centre an acknowledgement message indicating that the emergency message is received at the EPSS control centre is send to the EPSD user s registered mobile number (provided in the EPSS registration portal). The EPSD should keep sending Emergency messages in the configured interval (received in the AUTH_ACK message) until a Stop or Cancel message is issued. Stop message can be issued by the EPSD user or the EPSS Control centre in the following scenarios: a) After the victim receive necessary help from the control centre, the EPSS Control Centre issue a Stop Message (STOP_MSG) to the EPSD. When the EPSD receive a STOP_MSG it should check whether the sender number is the authorized number 13 P a g e

14 and then stop sending the Emergency Messages after sending a STOP_ACK to the EPSS Control centre. b) After pressing the panic button, if the user feels he/she is safe and wants to signal the EPSS Control Centre that he/she is safe, the device should have a provision to send Stop message (STOP_MSG). The Stop message is sent from EPSD to EPSS Control Centre indicating that the user is safe. c) When the panic button in EPSD was pressed by mistake and the user wants to indicate the false alarm to the EPSS control centre, the device should have a provision to send Cancel message (CANCEL_MSG). When a Cancel message is received the control centre understands that the user pressed the panic button by mistake. However in both these cases (b) and (c) the EPSS Control Centre will ensure that the user is safe by doing proper verification steps. 14 P a g e

15 2.3 Control Centre Initiated Tracking Introduction The Control centre initiated tracking flow enables the EPSS control centre to track a user in distress if found necessary Precondition The EPSD user should have successfully performed the EPSD initialization Operation The EPSS Control Centre has an option to track the EPSD user if found necessary. This can be accomplished by sending an INIT_TRK message to initiate the tracking process. On receiving the INIT_TRK message from authorized number, the EPSD should start sending the Emergency message at the set interval to EPSS Control Centre. 15 P a g e

16 Once the tracking requirement is over, the EPSS Control Centre prompts the EPSD to stop sending emergency messages by sending a STOP_MSG. When the EPSD receive a STOP_MSG from the authorized number and then stop sending the Emergency Messages after sending a STOP_ACK to the EPSS Control centre. When the INIT_TRK message lands on an EPSD which is already sending Emergency message then the INIT_TRK message can be ignored and device should continue sending the Emergency message. If the user presses the panic button on an EPSD which is already being tracked by the EPSS Control Centre, the EPSD should continue to send EMR_MSG until STOP_MSG is being received 2.4 EPSD Test Flow Introduction The EPSD test flow enables the EPSS registered user to check whether his/her EPSD & EPSS is working properly Precondition The EPSD user should have successfully performed the EPSD initialization. 16 P a g e

17 2.4.3 Operation The EPSD user can test whether the EPSD is functional using the Test mode. The EPSD should have a provision (can be a physical button) which can be used to trigger the test mode. On pressing the Test button the device should send a Test message (TST_MSG format mentioned in Section 3.1.5) to the EPSS Control centre and the EPSS will respond with an acknowledgement message (TST_ACK format mentioned in Section 3.2.5) which contains the status of the EPSD. Also the EPSS sends a SMS to the EPSD user s mobile number provided in EPSS Registration portal indicating the device status. 2.5 DEVICE DE-INITIALIZATION Introduction The De-initialization flow enables the EPSS registered user to de-initialize the EPSD before disposing it. An EPSD user may need to de-initialize his device from the EPSS network due to various reasons like user may want to change the EPSD, relocating to another city, transfer of EPSD to another user etc. In such cases the user will require the de-initialization flow Precondition The EPSD user should have successfully performed the EPSD initialization Operation The de-initialize function can be implemented by providing some de-initialize option in the EPSD. When this button is pressed the EPSD should delete the device initialization data stored in its memory and should switch to factory mode. The device initialization data is received during the EPSD Initialization flow. 17 P a g e

18 3 Message Details In EPSS, the communication protocol consists of two way message communication that happens between the EPSD and EPSS. The communication from EPSD and EPSS can happen as GSM SMS or data packets whereas the communication from EPSS to EPSD is always as GSM SMS. This chapter explains the format of all messages that exist in the EPSS System. The messages are classified as Type 1 & Type 2. The field separator is comma, for all messages. 3.1 Type 1: Messages from EPSD to EPSS Sl. Key Message Name No. word Channel ACK Sender Receiver 1. Authenticate Message AUTH GSM Yes EPSD EPSS 2. Emergency Message EMR GSM/GPRS No EPSD EPSS 3. Stop Message/Stop ACK SEM GSM/GPRS No EPSD EPSS 4. Cancel Message CEM GSM/GPRS No EPSD EPSS 5. Test Message TST GSM/GPRS Yes EPSD EPSS Table 1: Type 1 Messages of EPSS All Type 1 messages have a common SMS format but the Message Codes and optional parameters will be different for various message types. The SMS structure for Type 1 message is as shown below. The optional and mandatory parameters will vary for different types of messages. HEADER MESSAGE CODE DEVICE TYPE UNIQUE ID LATITUDE DIRECTION LONGITUDE DIRECTION ALTITUDE SPEED DATE TIME MCC MNC LAC CELL ID CRC Description of parameters Parameter Description Data type HEADER The unique identifier for all EPSS messages Character(3 bytes) Indicate the type of message. The value indicate MESSAGE the type of message or command that is been CODE issued. Character(3 bytes) DEVICE TYPE Indicates the type of device to/ from which the message is sent/received. This field can be used for identifying the additional features supported by the EPSD. The device codes currently Character(3 bytes) supported are explained in Annexure 5.1 Device Types. USER ID The user ID of the EPSD which is the EPSD mobile number. Character(10 bytes) LATITUDE Latitude of the device s current location in degree decimal format Floating point value LAT Direction of latitude i.e. North or South Character (1 byte) 18 P a g e

19 DIRECTION LONGITUDE LONG DIRECTION Longitude of the device s current location in degree decimal format Direction of longitude i.e. East or West Floating point value Character (1 byte) ALTITUDE The altitude of the current location obtained from location data SPEED The speed with which the device is being moved The date and time of the location obtained from DATE TIME the location data. This value is in the format YYYYMMDDhhmmss MCC Mobile Country code 100 to 999 MNC Mobile Network Code 0 to LAC Location Area Code 1 to CELL ID CRC Authenticate Message The unique ID of the cell phone tower to which the phone/device is connected to The 32 bit checksum of all the characters from the header up to the CRC field Character (14 byte) 1 to bytes Authenticate message is used in the device initialization flow for authenticating a device. This message is send from the EPSD to the EPSS and this message has an acknowledgement. This message is send in response to the START message and it should be send as a GSM SMS. The messages parameters are as shown below. Parameter Description Length (Char) Value Range HEADER The unique emergency message identifier 3 EPS MESSAGE CODE Indicate the type of message. The value indicate the type of message or command that is 4 AUTH been issued. DEVICE TYPE Indicates the type of device to/ from which the message is sent/ received 3 USER ID Not Applicable 0 Not Applicable LATITUDE Not Applicable 0 Not Applicable LAT DIRECTION Not Applicable 0 Not Applicable LONGITUDE Not Applicable 0 Not Applicable LONG DIRECTION Not Applicable 0 Not Applicable ALTITUDE Not Applicable 0 Not Applicable SPEED Not Applicable 0 Not Applicable DATE TIME Not Applicable 0 Not Applicable CRC The 32 bit checksum of all the characters from the header up to the CRC field 8 Refer Appendix 5.1 Device Type Codes for details 19 P a g e

20 A sample message is shown below: EPS,AUTH,APK,,,,,,,,83306cb Emergency Message Emergency message is used in the emergency message flow for sending the geographic location of a person in distress to the EPSS control centre. This message is send from the EPSD to the EPSS and this message is acknowledged with an SMS message to the user mobile. The device will continue to send the Emergency message at the configured interval unless the user presses the STOP button or the EPSD receive a STOP command from EPSS control centre. The messages parameters are as shown below. Parameter HEADER MESSAGE CODE DEVICE TYPE USER ID LATITUDE LAT DIRECTION LONGITUDE LONG DIRECTION ALTITUDE SPEED DATE TIME CRC Description The unique emergency message identifier Indicate the type of message. The value indicate the type of message or command that is been issued. Indicates the type of device to/ from which the message is sent/ received The user ID of the EPSD which is the EPSD mobile number. Latitude of the device s current location in degree decimal. (The length may vary based on the accuracy & precision) Direction of latitude i.e. North or South Longitude of the device s current location in degree decimal (The length may vary based on the accuracy & precision) Length (Char) Direction of longitude i.e. East or West 1 The altitude of the device s current location The speed with which the device is being moved The date and time of the location obtained from the location data (in Indian Standard time) The 32 bit checksum of all the characters from the header up to the CRC field 3 EPS 3 EMR 3 10 Value Range Refer Appendix 5.1 Device Type Codes for details 10 Digit mobile number <=16 Current Latitude 1 N for North S for South <=16 Current Longitude 5 5 E for East W for West Altitude in meters (above sea level) Speed of movement obtained from GPS packet (in kmph) 14 YYYYMMDDhhmmss 8 20 P a g e

21 A sample message is shown below: EPS,EMR,APK, , ,N, ,E,52,9.88, ,165ac Stop Message The STOP message is send from EPSD to the EPSS control centre indicating that the EPSD user wants to stop the emergency message as the person is safe. This can be triggered by using the STOP message option from the EPSD when the necessary help is received. The EPSS control centre may verify the authenticity of the message by call-back option. The message code for Stop message is SEM Stop Emergency message. The same message structure is used as an ACK message in case the Stop command is being issued from the EPSS Control Centre. When the EPSD receives a Stop control message from the EPSS control centre it should acknowledge the same by sending the Stop message in this format. Parameter HEADER MESSAGE CODE DEVICE TYPE Description The unique emergency message identifier Indicate the type of message. The value indicate the type of message or command that is been issued. Indicates the type of device to/ from which the message is sent/ received Length (Char) 3 EPS 3 SEM 3 Value Range Refer Appendix 5.1 Device Type Codes for details 10 Digit mobile number USER ID The user ID of the EPSD which is the EPSD mobile number. 10 LATITUDE Not Applicable 0 Not Applicable LAT Not Applicable Not Applicable 0 DIRECTION LONGITUDE Not Applicable 0 Not Applicable LONG Not Applicable Not Applicable 0 DIRECTION ALTITUDE Not Applicable 0 Not Applicable SPEED Not Applicable 0 Not Applicable The current date and time at which DATE TIME message is send (in Indian Standard 14 YYYYMMDDhhmmss time) CRC The 32 bit checksum of all the characters from the header up to the CRC field A sample message is shown below: EPS,SEM,APK, ,,,,,,, ,165ac P a g e

22 3.1.4 Cancel Message The CANCEL message is send from EPSD to the EPSS control centre indicating that the EPSD user wants to cancel the emergency message as the person has pressed the panic button by mistake. This message is intended to cancel any false emergency messages that may have been triggered by accidental press of the panic button. The message code for Cancel message is CEM Cancel Emergency message. Parameter HEADER MESSAGE CODE DEVICE TYPE Description The unique emergency message identifier Indicate the type of message. The value indicate the type of message or command that is been issued. Indicates the type of device to/ from which the message is sent/ received Length (Char) 3 EPS 3 CEM 3 Value Range Refer Appendix 5.1 Device Type Codes for details 10 Digit mobile number USER ID The user ID of the EPSD which is the EPSD mobile number. 10 LATITUDE Not Applicable 0 Not Applicable LAT Not Applicable Not Applicable 0 DIRECTION LONGITUDE Not Applicable 0 Not Applicable LONG Not Applicable Not Applicable 0 DIRECTION ALTITUDE Not Applicable 0 Not Applicable SPEED Not Applicable 0 Not Applicable DATE TIME The date and time at which message is send(in Indian Standard time) 14 YYYYMMDDhhmmss The 32 bit checksum of all the CRC characters from the header up to the 4 CRC field A sample message is shown below: EPS,CEM,APK, ,,,,,,, ,165ac Test Message The Test message is send from EPSD to the EPSS control centre to test whether the EPSD and EPSS are functional. The message can be used to test the device. On triggering this option the device should send an emergency message with the keyword TST to the EPSS control centre. The EPSS control centre will acknowledge this message by sending a confirmation SMS to the EPSD and also user s mobile phone. Parameter Description Length Value Range The unique emergency message HEADER 3 EPS identifier 22 P a g e

23 MESSAGE CODE DEVICE TYPE USER ID LATITUDE LAT DIRECTION LONGITUDE LONG DIRECTION ALTITUDE SPEED DATE TIME CRC Indicate the type of message. The value indicate the type of message or command that is been issued. Indicates the type of device to/ from which the message is sent/ received The user ID of the EPSD which is the EPSD mobile number. Latitude of the device s current location in degree decimal. (The length may vary based on the accuracy & precision) Direction of latitude i.e. North or South Longitude of the device s current location in degree decimal (The length may vary based on the accuracy & precision) Direction of longitude i.e. East or West 1 The altitude of the device s current location The speed with which the device is being moved The date and time of the location obtained from the location data (in Indian Standard time) The 32 bit checksum of all the characters from the header up to the CRC field 3 TST 3 10 Refer Appendix 5.1 Device Type Codes for details 10 Digit mobile number <=16 Current Latitude 1 N for North S for South <=16 Current Longitude E for East W for West Altitude in meters Speed obtained from GPS packet 14 YYYYMMDDhhmmss 8 A sample message is shown below: EPS,TST,APK, , ,N, ,E,52,9.88, ,165ac Type 2: Messages to EPSD Sl. No. Message Name Code Channel Type Sender Receiver 1. Start message START GSM Control User EPSD 2. Authenticate Success AUTH GSM Control EPSS EPSD 3. Authenticate Failure FAIL GSM Control EPSS EPSD 4. Stop Message SEM GSM Control EPSS EPSD 5. Initiate Tracking UTK GSM Control EPSS EPSD 6. Test Acknowledgement TST_ACK GSM Control EPSS EPSD Start Message Start message is used in the device initialization flow for initializing the EPSD with the EPSS Control centre number. This is the initial message that initiates the EPSD registration flow. 23 P a g e

24 This message is send from the User to the EPSD. When the EPSD receive this message it initiates the communication with the EPSS by sending the Authenticate message. When a user successfully registers in the EPSS registration portal, he receives a SMS stating that registration is successful and this SMS contains the EPSS control centre number of his locality. The user should send the Start message to the EPSD to initiate the EPSD registration process. On receiving this message the EPSD initiate the EPSD Initialization flow. Parameter Description Length Value Range HEADER The unique emergency message identifier 2 ED Indicate the type of message. The value MESSAGE indicate the type of message or 3 START CODE command that is been issued. CONTROL CENTRE CODE The EPSS Control centre number received by user in the confirmation SMS after registration to EPSS Web portal A sample message is shown below: ED,START, Authenticate Success 10 3 to 10 digit short code The authenticate success message is send from the EPSS to EPSD after successfully validating the EPSS User. This message is send in response to the AUTH message. This message contains the configuration parameters like EPSS Control centre number, Static IP and Port for data communication, EPSD own number, and emergency message interval. On receiving this message the EPSD should store these parameters in the device memory so that it can use when required. Parameter Description Length Value Range HEADER The unique emergency message identifier 2 ED Indicate the type of message. The value MESSAGE indicate the type of message or 4 AUTH CODE command that is been issued. USER NUMBER CONTROL CENTRE CODE GPRS IP The users EPSS mobile number 10 The EPSS Control centre number received by user in the confirmation SMS after registration to EPSS Web portal The EPSS Control Centre static IP Address for GPRS communication digit EPSD number 3 to 10 digit short code 15 IP Address GPRS PORT GPRS port Number 4 Port Number DELAY Time interval to send Emergency message updates 3 Delay in seconds A sample message is shown below: ED,AUTH, ,1090, ,5060, P a g e

25 3.2.3 Authenticate Failure The authenticate failure message is send from the EPSS to EPSD if validating the EPSS User is not successful. This message is send in response to the AUTH message. This message is an indication to the EPSD user that device authentication has failed. Parameter Description Length Value Range The unique emergency message HEADER 2 ED identifier Indicate the type of message. The MESSAGE value indicate the type of message or 4 FAIL CODE command that is been issued. ERROR CODE NOTE: The error code indicating the reason for authentication failure : Invalid EPSD User 0002 : Server busy If ERROR CODE is 0001 the EPSD can send the SMS response to User mobile directly without retry. If ERROR CODE is 0002 the EPSD need to retry till the maximum retry limit is reached. A sample message is shown below: ED,FAIL, Stop Message The Stop message is send from the EPSS to EPSD and on receiving a Stop message the EPSD should stop sending the emergency message. This message is send when the Control centre want to stop tracking the user. This can be send in the Control centre initiated tracking flow as well as the emergency message flow. In both the cases on receiving this message the EPSD should send a STOP_ACK (Explained in Section Stop Message) message back and then stop sending emergency messages. Parameter Description Length Value Range The unique emergency message HEADER 2 ED identifier Indicate the type of message. The MESSAGE value indicate the type of message or 3 SEM CODE command that is been issued. A sample message is shown below: ED,SEM Initiate Tracking The initiate tracking message is send from the EPSS to EPSD to initiate the emergency message on the EPSD device. This can be used to find the location of an EPSD user in distress 25 P a g e

26 situations where the distress information is received from some other sources. (This can be used to find the location when a person kidnapped or missing) Parameter Description Length Value Range The unique emergency message HEADER 2 ED identifier Indicate the type of message. The MESSAGE value indicate the type of message or 3 UTK CODE command that is been issued. A sample message is shown below: ED,UTK Test Acknowledgement The test response is an SMS message indicating the device is functional and can communicate with the EPSS control centre. This can be triggered by using the Test button provided in the EPSD. When the user press this option a test message in above specified format is send to the EPSS control centre and the User receives a SMS on his mobile phone indicating the test response. Parameter Description Length Value Range The unique emergency message HEADER 2 ED identifier Indicate the type of message. The MESSAGE value indicate the type of message or 7 TST_ACK CODE command that is been issued. STATUS Indicate the device status 3 OK or NOK A sample message is shown below: ED, TST_ACK,OK 26 P a g e

27 4 Annexure 4.1 Device Specifications Please refer the document DXX BC epsd Technical Specification for Device Specifications. 4.2 Device Type codes Device type code is used to identify the type of EPSD from which the Emergency message is received. This is important because some EPSDs may support special features/functions which can be helpful to provide emergency help to victim. The device manufacturers can get in touch with CDAC to get a unique device code for their EPSD if the device has some special features/functions. Trackers comply with this document can use the codes below. Currently assigned device codes: Sl. No. Device Type Code 1. Windows App W01 2. General Tracker G01 3. Android App A01 4. IOS App I01 27 P a g e