MPTP | Copyrights and limitation of liability 1 Mobile Phone Telematics Protocol for TWIG GSM/GPS products Version 3.25 Licensed to:Twig Com Ltd., SALO, FI Copyright Twig Com Ltd. All rights reserved Version 3.25 Rev. September 6 2012 ’ CONFIDENTIAL. Copyright Twig Com Ltd. 2007-2012. All rights reserved. | Version 3.25 | Rev. September 6 2012 Licensed to: Twig Com Ltd.
MPTP | Copyrights and limitation of liability 2 LIMITED LICENSE AGREEMENT Licensee: Licensee contact person: The licensor, Twig Com Ltd., Meriniitynkatu 11, FIN-24100 Salo, Finland, Tel +358 40 510 5058, hereby grants the licensee a limited license to use this TWIG MPTP Document solely for the Purpose of integrating TWIG devices by Twig Com Ltd. to third party software. Any other use is expressly prohibited.
MPTP | Table of contents 3 TABLE OF CONTENTS 1. INTRODUCTION............................................................................................................................................................... 5 2. OVERVIEW OF THE SYSTEM......................................................................................................................................... 6 2.1. Actors...............................................................................................................
MPTP | Table of contents 4 4.3.2. Acknowledgement to condition check permission request........................................................59 4.4. Emergency cycle commands......................................................................................................................60 4.4.1. Emergency report with text (!EMG)............................................................................................61 4.4.2. Emergency confirmation (?EMG)...........................................
MPTP | MPTP commands 1. 5 INTRODUCTION MPTP (Mobile Phone Telematics Protocol) is a protocol developed by Twig Com Ltd. . It is a key for building professional and consumer telematics solutions in GSM networks. MPTP provides sophisticated telematics commands for service integrators and providers to build and provide various applications utilising location information. MPTP enables, for example, the sending of location, tracking and route messages between service centers and Twig Com Ltd.
MPTP | MPTP commands 2. 6 OVERVIEW OF THE SYSTEM MPTP messaging takes place in the GSM network using specially formatted SMS messages. This chapter describes the roles of the actors in such MPTP messaging exchange and gives an overview of some typical scenarios involving telematics messaging. A more detailed and technical description of the format, structure and use of MPTP commands is given in subsequent chapters. 2.1. Actors MPTP messaging always takes place between two parties.
MPTP | MPTP commands 7 2.1.3. Authorisation and access rights It is desirable to limit the parties from which MPTP messages used for controlling and monitoring a Mobile Telematics Terminal are allowed, not only to protect the user’s privacy and to ensure security of stored data, but also to limit the number of messages sent. Track and Esc! use a somewhat different system for controlling MPTP messaging.
MPTP | MPTP commands • 8 All requests from unauthorized target entries require the user to accept their processing by confirming a notification. Any responses are sent to the number from which the request came. Twig Discovery Pro In the Twig Discovery Pro line of products, the Twig Configurator PC-application can be used for marking the partners as authorized or unauthorized. • All requests from authorized partners are automatically processed.
MPTP | MPTP commands 9 The MPTP commands, which can be used for realisation of these scenarios, are described in section 4.1. 2.2.2. Tracking The term tracking means a function, which enables monitoring a target’s position and possible movement. The tracked Mobile Telematics Terminal will automatically send a series of MPTP messages of its position to the Control Centre as defined by the tracking process. Typical tracking scenarios are as follows: 1.
MPTP | MPTP commands 10 2.2.3. Emergency cycle The term emergency cycle refers to an automated sequence of actions taken when the end user has pressed the emergency key. External triggers such as a verticality sensor can also start the cycle. The action sequence consists of making emergency calls and sending emergency messages containing position information.
MPTP | MPTP commands 3. 11 A Control Centre wants to activate the telematics services of the Mobile Telematics Terminal. Examples: (1) The customer of the emergency services has paid for the service and wants to start using the service. The emergency centre operator activates the telematics services of the customer’s terminal after the customer has paid for the service. After that the emergency cycle feature and rest of the telematics services of the terminal can be used.
MPTP | MPTP commands 3. 12 MESSAGE CONSTRUCTION AND INTERPRETATION As mentioned earlier, MPTP messages are sent between parties as specially formatted SMS messages. The standard 7-bit GSM character set is used (cf. GSM 7-bit default alphabet table.pdf). Most MPTP messages are sent in a semi-readable ASCII format and can thus be received and read using any SMS enabled mobile phone.
MPTP | MPTP commands 13 Telematics Terminal. If for some reason messages which have exclamation and/or question mark as first character do not work in some network, there is a possibility to change the header characters. It is recommended though that the header characters are changed only if the default ones do not work. Note also that if the header characters are changed it should be done to all the terminals which are connected to the same system.
MPTP | MPTP commands 14 gpa, position is aquired from GPS, but the timestamp is updated, since no movement is detected with motion sensor after last actual position fix. Note the motion sensor parameters, that define the needed movement. gpb position is aquired from GPS, but the timestamp is NOT updated, since movement is detected with motion sensor but not calculated by gps. Note the motion sensor parameters, that define the needed movement. net for GSM network.
MPTP | MPTP commands 15 The precision of the position given in the Position field. The unit for the precision is always meters. The range of the field is 0…255 meters . Values more than 254 are always indicated with 255 in the field. The precision is estimation calculated from multiple variables. Note that this field is present only if the Position format is 2 (WGS-84 with precision) (cf. above) In this example, the position precision has been 37 meters. 08.07.
MPTP | MPTP commands 16 If data needed for a data field is unavailable, the field is commonly filled with hyphen characters (-, Unicode 0x2D). This is the case for the Position, Time stamp, Speed and Heading fields.
MPTP | MPTP commands 17 The exact meaning of each field, along with the typical actions taken on reception of the message, is given for each command in this document. 3.3. Reassembling a received MPTP command An instrument receiving an MPTP command in several parts needs to store the parts in a buffer until all of them have been received. As soon as the full set (01/NN, 02/NN, … , NN/NN) is present, the command can be reassembled and processed.
MPTP | MPTP commands 3.7. 18 Table of MPTP commands For the table of MPTP commands and products that support them cf. Table of MPTP commands.pdf. For the table of persistent setting configuring Setting IDs and products that support them cf. Table of CNF setting IDs.pdf.
MPTP | MPTP commands 4. 19 MPTP COMMANDS This chapter lists each MPTP command, categorized according to their usage. For each command, the following information is given: • Roles and purpose: First, the roles of the sender and the recipient of the command are given. CC → MTT indicates that the role of the sender is Control Centre while that of the recipient is Mobile Telematics Terminal, and vice versa. A brief textual description of the purpose of the command follows the role information.
MPTP | MPTP commands Supported Benefon/TWIG instruments and SW versions: Twig Discovery SW CD1D.02.002.00069, CD2D.02.011.00000 Twig Hunter SW CD1H.02.002.00000 Hunter 1.0.3 Twig Discovery Pro SW CD1P.02.019.00000 Twig Discovery Pro (Tracer) SW CD1R.02.054.0000 Twig Discovery Pro (Navigation) SW CD1Q.02.054.0000 Twig Discovery Pro (Tracer, Navigation) SW CD1S.02.054.0000 Twig Locator SW 2.06 Twig Protector SW CG1P.01.001.
MPTP | MPTP commands 21 acquired from the GPS before sending a report. Old software versions will generally always send the last known position. Command format 4 Action Command* Length: 4…6 characters 1 1 ?LOC _ 0 *) cf. section 3.1 for description of this field. The Action field is described below. It may be omitted altogether.
MPTP | MPTP commands 22 4.1.2. Position report (!LOC) MTT → CC The position report command is sent by a Mobile Telematics Terminal as a sole response to a position request command from a Control Centre. It is also used by Benefon Esc! instead of the manual position report command Supported Benefon/TWIG instruments and SW versions: Twig Discovery SW CD1D.02.002.00069, CD2D.02.011.00000 Twig Hunter SW CD1H.02.002.00000 Hunter 1.0.3 Twig Discovery Pro SW CD1P.02.019.
MPTP | MPTP commands 23 Command format 4 1 5 1 4 1 4 1 3 1 1 1 24 1 19 1 7 1 Data Heading* Speed* Time stamp* Position* Position format* Position source* Battery level* Mode* Command* Part number* Length: 87...151 characters 6 1 0…60 !LOC _ 01/01 _ norm _ 075% _ gps _ 1 _ N60.26.54,3_ _ 11.07.2003_ _ 005km/h _063deg _ E022.17.37,1 09:57:46 × *) cf. section 3.1 for description of these fields. The Data field is optional and can be omitted.
MPTP | MPTP commands 24 *) cf. section 3.1 for description of these fields. The Data field includes beacon data if position format is 3. Some TWIG instruments use it also to hold textual information about the cause of failure when unable to acquire a position fix. Beacon data in above example. Different fields within Beacon data is separated with “.” (full stop):. Different Beacons are separated with”_” (underscore). Underscore (“_”) must NOT be used in Beacon name. ROOM1.5.-101.35.
MPTP | MPTP commands • 25 Stop trigger: The tracking process is stopped when this condition is met. Typical stop triggers include a specific number of reports having been sent, a specific duration of running having been reached, or reversing the trigger condition which started the process (e.g. re-entering an area earlier exited). The Control Centre can remotely set up a tracking process by sending a tracking request MPTP command.
MPTP | MPTP commands 4.2.1.1. 26 Simple tracking request: interval, minutes (?TRC) CC → MTT The simple tracking request command is sent by a Control Centre to make the receiving Mobile Telematics Terminal create and activate a tracking process with the following properties: • Start trigger: None. The tracking process is started as soon as it is created. • Interval The process will send tracking reports at the specified interval until the stop trigger condition is met.
MPTP | MPTP commands • 27 Track One, Track Pro, Trackbox, TrackKeeper, Seraph, Twig Locator: Depending on the authorization of the Control Centre which sent the request, a new tracking process may be created or the request may be disregarded altogether. Cf. section 2.1.3 for more information. • Esc!: Depending on the authorization of the Control Centre which sent the request, a new tracking process may be created automatically or user confirmation may be required. Cf. section 2.1.
MPTP | MPTP commands 28 Supported Benefon/TWIG instruments and SW versions: Twig Hunter SW CD1H.02.002.00000 Hunter 1.0.3 Twig Discovery Pro SW CD1P.02.047.00000 Twig Discovery Pro (Tracer) SW CD1R.02.054.0000 Twig Discovery Pro (Navigation) SW CD1Q.02.054.0000 Twig Discovery Pro (Tracer, Navigation) SW CD1S.02.054.0000 Twig Locator SW 2.06 Send • • • Receive • • • • • • Twig Protector SW CG1P.01.001.
MPTP | MPTP commands 29 have been sent. For information on how the receiving instrument interprets these parameters, cf. section . 4.2.1.3. Simple tracking request: stopping interval tracking (?STO) CC → MTT The simple tracking stopping command is sent by a Control Centre to make the receiving Mobile Telematics Terminal stop a tracking process created with either of the simple tracking request commands described above, ?TRC and ?TRS.
MPTP | MPTP commands 30 Cf. section 4.2.1 for information on determining the recipient of the reports sent by a tracking process. Command format Command* Length: 4 characters 4 ?STO *) cf. section 3.1 for description of this field. 4.2.1.4. Complex tracking request (?TRG) CC → MTT Using the complex tracking request, tracking processes with a multitude of different kinds of start and stop trigger conditions can be created: 0.
MPTP | MPTP commands 31 4. NOT AVAILABLE 5. NOT AVAILABLE 6. NOT AVAILABLE 7. Endless tracking: The tracking process sends reports at regular intervals indefinitely. It will only stop when requested. This type of tracking is described in detail in section 4.2.1.4.5. 8. NOT AVAILABLE 9. NOT AVAILABLE … Command* Trigger type Each supported start/stop trigger combination is defined by a trigger type to which the numbering above refers.
MPTP | MPTP commands 1. 32 • Interval: Interval for sending reports while outside the area, in minutes. • Stop trigger: Arrival at area; i.e. reversing the start trigger condition. Report while inside the area: The tracking process sends reports while the Mobile Telematics Terminal is inside the area. The tracking process parameters are in this case as follows: 2. • Start trigger: Arrival at area. • Interval: Interval for sending reports while inside the area, in minutes.
MPTP | MPTP commands 33 Reception Depending on the authorization of the Control Centre which sent the request, a new tracking process may be created or the request may be disregarded altogether. Cf. section 2.1.3 for more information. Command format (Data) Interval (Allowed value) Method (Limit) Radius Service state Trigger type Command* 4 (Trigger special data) Area centre Length: 39…46 characters 1 1 1 1 1 1…4 1 1 1 24 1 ?TRG _ 0 _ 1 _ 1000 _ 0 _ N68.28.43,9_ _ E027.27.
MPTP | MPTP commands 34 relation to the tracked area. Thus, this parameter is also relevant for Methods 2, 3 and 4. 4.2.1.4.2. Trigger type 1: stopping at report limit CC → MTT A type 1 tracking process sends reports at regular intervals until a specified number of reports have been sent. Such a process can be created and activated by a Control Centre, by sending a complex tracking request command with trigger type 1. The tracking process has the following properties: • Start trigger: None.
MPTP | MPTP commands 35 Command format (Trigger special data) (Allowed value) Unused (Limit) Interval Service state Trigger type Command* 4 Number of reports Length: 14…22 characters 1 1 1 1 1 1…5 1 1 1 1…5 ?TRG _ 1 _ 1 _ 30 _ 0 _ 20 *) cf. section 3.1 for description of this field. The special fields of the command are as follows: Field Description Range Trigger type Trigger type of complex tracking request message, as defined in section 4.2.1.4.
MPTP | MPTP commands • 36 Stop trigger: Time limit. The tracking process is stopped when it has been running for a specified time. The time limit is given in full minutes. Supported Benefon/TWIG instruments and SW versions: Send Receive Twig Discovery Pro SW CD1P.02.047.00000 Twig Discovery Pro (Tracer) SW CD1R.02.054.0000 Twig Discovery Pro (Navigation) SW CD1Q.02.054.0000 Twig Discovery Pro (Tracer, Navigation) SW CD1S.02.054.0000 • • • • Twig Protector SW CG1P.01.001.
MPTP | MPTP commands 37 Time limit 4.2.1.4.4. Stop trigger condition: the tracking process is stopped after it has been running for the time set in this field. 1…65534 (min) Trigger type 3: stopping at date and time CC → MTT A type 3 tracking process sends reports at regular intervals until a specified date and time is reached. Such a process can be created and activated by a Control Centre, by sending a complex tracking request command with trigger type 3.
MPTP | MPTP commands 38 Command format (Trigger special data) (Allowed value) Unused (Limit) Interval Service state Trigger type Command* 4 Stopping date and time Length: 25…29 characters 1 1 1 1 1 1…5 1 1 1 12 ?TRG _ 3 _ 1 _ 30 _ 0 _ 051220002015 *) cf. section 3.1 for description of this field. The special fields of the command are as follows: Field Description Range Trigger type Trigger type of complex tracking request message, as defined in section 4.2.1.4.
MPTP | MPTP commands • 39 Start trigger: None. The tracking process is started as soon as it is created. • Interval The process will send tracking reports at the specified interval, given in full minutes. • Stop trigger: None. The tracking process is never automatically stopped. To deactivate the process, use the command described in section 4.2.1.4.7. Supported Benefon/TWIG instruments and SW versions: Send Receive Twig Discovery Pro SW CD1P.02.019.00000 Twig Discovery Pro (Tracer) SW CD1R.02.
MPTP | MPTP commands 40 Interval Time between sending of tracking reports, in minutes. 4.2.1.4.6. 1…65534 (min) Trigger type 9: anchor tracking CC → MTT An anchor tracking process is used for monitoring a Mobile Telematics Terminal’s departure from an area. The process can be created and activated by a Control Centre, by sending a complex tracking request command with trigger type 9. The tracked area is circular. It is defined by a centre point and a radius.
MPTP | MPTP commands 41 The special fields of the command are as follows: Field Description Range Trigger type Trigger type of complex tracking request message, as defined in section 4.2.1.4. In this case, the trigger type number is 9. 0…9 Service state Activity of tracking process. 0…2 0: 1: Radius 4.2.1.4.7. De activate Activate Radius of tracked area.
MPTP | MPTP commands 42 Command format Trigger type Command* 4 Service state Length: 8…9 characters 1 1…2 1 ?TRG _ 0 _ 1 0 *) cf. section 3.1 for description of this field. The special fields of the command are as follows: Field Description Range Trigger type Trigger type of tracking process to be deactivated, as defined in section 4.2.1.4. 0…9, 99 To deactivate all tracking processes at once, trigger type 99 can be used. Service state 4.2.1.5. Activity of tracking process.
MPTP | MPTP commands 4. 43 Speed tracking: For future extension. 5. Report at date and time: For future extension. 6. Polygonal area tracking: For future extension. 7. Endless tracking: The tracking process sends reports at regular intervals indefinitely. It will only stop when requested. This type of tracking is described in detail in section 4.2.1.5.1. 8. Not in use. 9. Anchor tracking: For future extension.
MPTP | MPTP commands 44 The tracking process has the following properties: • Start trigger: None. The tracking process is started as soon as it is created. • Interval The process will send tracking reports at the specified interval, given in seconds. • Stop trigger: None. The tracking process is never automatically stopped. To deactivate the process, use the command described in section 4.2.1.5.2. Supported Benefon/TWIG instruments and SW versions: Send Receive Twig Protector SW CG1P.01.001.
MPTP | MPTP commands 45 be used; otherwise the process will not be activated. Interval Time between sending of tracking reports, in seconds. 4.2.1.5.2. 1…65534 (sec) Deactivating real time complex tracking CC → MTT The real time complex tracking deactivation command is sent by a Control Centre to make the receiving Mobile Telematics Terminal deactivate a tracking process created with the real time complex tracking request command described above, ?TRR.
MPTP | MPTP commands 46 *) cf. section 3.1 for description of this field. The special fields of the command are as follows: Field Description Range Trigger type Trigger type of tracking process to be deactivated, as defined in section 4.2.1.5. 0…9, 99 To deactivate all tracking processes at once, trigger type 99 can be used. Service state Activity of tracking process. Value 0 should be used; otherwise the process will not be deactivated. 0…1 4.2.2.
MPTP | MPTP commands 47 • Twig Protector SW CG1P.01.001.0000 Sending • Track One, Track Pro, Trackbox, TrackKeeper, Seraph, Twig Locator: This command can be sent by a tracking process remotely set up by a Control Centre. Cf. section 4.2.1.1 for more information. • Esc!: This command can be sent by a tracking process remotely set up by a Control Centre. The process can also be set up locally; this done by selecting the Send tracking function from the Friend Find or Commander application.
MPTP | MPTP commands 48 The special fields of the command are as follows: Field Description Range Trigger type Trigger type of the tracking process. As the simple tracking process is essentially identical to a complex tracking process with trigger type 1, the value 1 is used here. 0…9 Service state Activity of tracking process. Value 1 should be used, as the tracking process is active. 0…1 Message number The message number of the report and the total number of messages to be expected.
MPTP | MPTP commands 49 Command format 1 3 1 1 1 Time stamp* 1 1 !TRS _ 01/01 _ 1 _ 1 _ norm _ 075% _ gps _ 1 _ N68.28.43,9 _ 20.10.2003 _ E027.27.02,4 14:37:09 142km/h 4 Position* 1 1 1 Position format* 1 7 4 Position source* Battery level* Mode* Service state 1 24 1 19 1 Message number 5 Heading* 1 Speed* 4 Trigger type Command* Part number* Length: 90...104 characters 6 1 3…9 _ 114deg _ 3/10 *) cf. section 3.1 for description of these fields.
MPTP | MPTP commands 50 Reception • Twig Hunter: Upon receiving a tracking report command, Twig Hunter will notify the user and update the position it has stored for the terminal which sent the report. Command format Trigger types 0 and 9 1 1 1 !TRG _ 01/01 _ 0 _ 1 _ norm _ 075% _ gps _ 1 _ N68.28.43,9 _ 20.10.2003 _ E027.27.
Heading* Message number MPTP | MPTP commands Speed* 7 1 081km/h 6 1 3…9 _ 114deg _ 3/10 Trigger type 4 1 !TRG _ 01/01 _ 4 _ 1 _ norm _ 075% _ gps _ 1 _ N68.28.43,9 _ 20.10.2003 _ E027.27.02,4 14:37:09 081km/h 6 1 _ 114deg _ 4 1 3 1 1 1 Time stamp* 1 1 1 Position* 1 24 1 19 Message number 1 7 4 Position format* Position source* Battery level* Mode* Service state 1 Current speed 5 Heading* 1 Speed* 4 Trigger type Command* Part number* Length: 92...
MPTP | MPTP commands 52 Message number The message number of the report and the total number of messages to be expected. The first number is the message’s order number and the number after the slash character is the total number of messages to be expected. 0000….9999 / 0000….9999 If the message order number or total number of messages becomes more than 9999, 0000 is used in the field. If the total number of messages cannot be calculated 0000 is used in the field.
MPTP | MPTP commands 53 Trigger type 7 1 3 1 1 1 Time stamp* 1 1 !TRR _ 01/01 _ 1 _ 1 _ norm _ 075% _ gps _ 1 _ N68.28.43,9 _ 20.10.2003 _ E027.27.02,4 14:37:09 081km/h 4 Position* 1 1 1 Position format* 1 7 4 Position source* Battery level* Mode* Service state 1 24 1 19 Message number 5 Heading* 1 Speed* 4 Trigger type Command* Part number* Length: 90...
MPTP | MPTP commands 4.3. 54 Condition check commands Condition check is a function which enables monitoring a target’s condition without having to specifically request it by sending MPTP commands or making phone calls all the time. This is done by setting up a condition check process on a terminal to take care of presenting queries which the user of the monitored terminal must confirm. The terminal will report to a Control Centre based on the user’s response to a query, or lack thereof.
MPTP | MPTP commands 55 Sending This command can be sent by a condition check process. Cf. section 4.3 for more information. Command format 1 !CIN _ 01/01 _ 0 30 1 _ emer _ 075% _ gps _ 1 _ N68.28.43,9 _ 28.10.2003 _ E027.27.
MPTP | MPTP commands 56 Passcode Passcode entered into the query by the user. 0…4 chars The code is not verified locally. Any verification needs to be done based on this field by the Control Centre. This field is omitted if the query which caused sending the report did not require a code, or if the user failed to enter one. Currently not used. Defaults to 0 4.3.2.
Heading* Speed* 7 1 081km/h 6 Passcode 57 Queries missed MPTP | MPTP commands 1 1…5 1 0…4 _ 114deg _ 1 _ 8725 *) cf. section 3.1 for description of these fields. The special fields of the command are as follows: Field Description Range Trigger type Trigger type of the condition check process which sent the report. Currently only 0. 0…3 Interval Query interval of the process which sent the report, in full minutes. 1…65536 (min) Service state Activity of tracking process.
MPTP | MPTP commands 58 Command format 4 Trigger type Request command Approval Command* Length: 12 characters 1 1 1 3 1 1 ?ACK _ 1 _ CND _ 1 *) cf. section 3.1 for description of this field.
MPTP | MPTP commands 59 Starting the emergency cycle The emergency cycle is started when the user of a Mobile Telematics Terminal presses the emergency key of the instrument. It may also be initiated by other events such as an alarm from an external verticality sensor.. There may be a cancellation period at the start of the emergency cycle. During it, the user may cancel the cycle before any reports have been sent or calls made.
MPTP | MPTP commands 60 4.4.1. Emergency report with text (!EMG) MTT → CC This emergency report command may be sent by a Mobile Telematics Terminal during the emergency cycle. It may contain some predefined text in addition to position information. Supported Benefon/TWIG instruments and SW versions: Send Receive • • • • • • • • • Twig Discovery SW CD1D.02.002.00069, CD2D.02.011.00000 Twig Hunter SW CD1H.02.002.00000 Hunter 1.0.3 Twig Discovery Pro SW CD1P.02.019.
MPTP | MPTP commands 61 The special fields of the command are as follows: Field Description Range Mode Cf. section 3.1 for description of this field. ‘emer’ or ‘test’ Since this is an emergency report, this field usually contains the string ‘emer’. Twig SOS application in Twig Discovery Pro also has test mode and if that is used them this field contains string ‘test’. Text Predefined text to be sent with the emergency report.
MPTP | MPTP commands 62 Command format Command* Length: 4 characters 4 ?EMG *) cf. section 3.1 for description of this field. 4.5. Status and information commands Status and information commands can be used for sending different kinds of status information to a Control Centre. Typically, such messages are used for reporting the status of a task the Mobile Telematics Terminal’s user is performing. Requesting and sending information about the terminal itself is also common.
MPTP | MPTP commands 63 Supported Benefon instruments and SW versions: Send Receive • TWIG Locator SW CL1L.06.008.0000 Sending • TWIG Locator: A report can be sent automatically when an event for which such functionality has been programmed occurs. In case of an I/O event, the report is sent to the first Alert number configured as described in the user manual. Command format Note that there are different command formats for different products, applications and uses.
MPTP | MPTP commands 64 text report. chars Some status codes can have a fixed, predefined string associated with them. For Trackbox, a status text can be defined for codes 001…014. For other instruments, it can be defined for codes 001…009. Some products like Seraph have some status codes, which have build in texts. See below for those. Additional text The user may be allowed to type in additional text to be sent with the report. Such text is stored here.
MPTP | MPTP commands 65 4.5.3. Device information report (!INF) MTT → CC The device information report command can be sent by a Mobile Telematics Terminal to inform a Control Centre about the status of the instrument. It is always sent automatically when a condition programmed for it is met. Supported Benefon/TWIG instruments and SW versions: Send Twig Discovery Pro SW CD1P.02.047.00000 Twig Discovery Pro (Tracer) SW CD1R.02.054.0000 Twig Discovery Pro (Navigation) SW CD1Q.02.054.
MPTP | MPTP commands 66 *) cf. section 3.1 for description of these fields.
MPTP | MPTP commands 67 In Twig family this field contains ‘-‘ because the data is not available. Failure code Internal code indicating reason for battery failure. ‘0’ indicates OK status. 0…99 This field is present on with first six status codes. With rest of the status codes the field is totally omitted from the message. In Twig family this field contains ‘-‘ because the data is not available. Time of sending Date and time at which the report was sent. Universal Coordinated Time (UTC) is used.
Radius Method Interval MPTP | MPTP commands 1…4 1 1 1 1…5 1000 _ 0 _ 15 The special fields of the command are as follows: Field Description Range Indication type Defines the type of the indication. 0: Tracking state change caused by digital input pin 0 Note that the rest of the fields depend on the value on this field. At the moment only one indication type is supported. Time of sending Date and time at which the indication was sent. Universal Coordinated Time (UTC) is used.
MPTP | MPTP commands 69 Method Method of anchor tracking, as described above: 0: 1: 2: 3: 4: Interval 0…4 report while outside the area report while inside the area report arrival report departure report arrival and departure Time between sending of tracking reports, in minutes. 1…65534 (mins) Note that the last five fields are present only when the current activity of the tracking is active. 4.5.5.
MPTP | MPTP commands 70 Field Description Range Type Type of the automatic status reporting process. 0 Currently there is only one type of process and 0 should be used in this field always. Service state Activity of process. Value 1 should be used when activating the process; otherwise the process will not be activated. 0…1 See chapter 4.5.6 for deactivating the automatic status reporting process. Interval Time between sending of automatic status reports reports (cf. 4.5.7), in minutes.
MPTP | MPTP commands 71 Command format 4 Service state Type Command* Length: 8 characters 1 1 1 1 ?ASR _ 0 _ 0 *) cf. section 3.1 for description of this field. The special fields of the command are as follows: Field Description Range Type Type of reporting process to be deactivated, as defined in section 4.5.5. 0 Currently only one type is available Service state Activity of the process. Value 0 should be used for deactivation; otherwise the process will not be deactivated. 0…1 4.
MPTP | MPTP commands 72 Command format Type 0 4 1 5 1 1 1 1…2 1 !ASR _ 01/01 _ 0 _ 0 4 Accessory data Sent messages Battery level* Status Type Command* Part number* Length: 21...42 characters 1 _ 075% _ 1…5 20 1 1…15 _ 123456789 *) cf. section 3.1 for description of these fields. The special fields of the command are as follows: Field Description Range Type Type of the reporting process, which sent the report. Cf. section 4.5.5.
MPTP | MPTP commands Supported Benefon/TWIG instruments and SW versions: TWIG Protector SW CG1P.01.001.0000 73 Send Receive • Reception Upon receiving a SW version and IMEI request command a terminal should respond by sending a SW version and IMEI report command. Depending on the authorization of the Control Centre which requested the report, the response message may be sent automatically or the request may be disregarded altogether. Command format Command* Length: 4 characters 4 ?SIR *) cf.
1 5 1 16 1 GSM module software version IMEI GPS software version Part number* Command* 4 74 Software version MPTP | MPTP commands 16 !SIR _ 01/01 _ CG1P.01.00 _XXXXXX 1.0000 1 16 _ 352021009123456 1 20 _ MC55 Revision 04.00 *) cf. section 3.1 for description of these fields. The special fields of the command are as follows: Field Description Range Software version Software version of device. string GPS software version Software version of GPS module.
MPTP | MPTP commands 75 The appearance of the message is normally accompanied by playing the message reception tone and using lights and vibration as set in the receiving terminal; however, these default settings can be overridden by the Forced tone, Forced volume, Forced vibration and Forced lights parameters in the message. Moreover, the tone and other effects taking place at the time of reception can be repeated later to make sure that the user of the receiving terminal notices the message.
MPTP | MPTP commands Forced vibration Forced lights 76 Use of vibration upon arrival of the message: - Use default setting for vibration. 0 Do not use vibration. 1 Use vibration. Use of lights upon arrival of the message: - Use default setting for lights. 0 Do not use lights. 1 Use lights. -, 0…1 -, 0…1 Reminder interval Interval at which the message reception effects will be replayed until the user acknowledges the message.
MPTP | MPTP commands 77 4 1 5 … Setting ID Command* Part number* Please note, that some configurations require the unit to be restarted to get effect. In some devices the restart can be done with a specific MPTP command. c.f. Reset terminal request 4.9 1 4 1 … ?CNF _ 01/01 _ 0060 _ … *) cf. section 3.1 for description of these fields. Variations of the command are described in subsequent sections.
MPTP | MPTP commands 78 … 1 1 1 … 5 _ +3581234567845 _ 0 _ +3581234567878 _ 1 … Calling Call recipient Reporting Em. report recipient Slot number 2nd emergency centre record 0…41 1 1 1 0…41 1 Track One, One NT, One NT US 1 5 1 4 1 0…41 Reporting Em.
MPTP | MPTP commands 79 Em. report recipient Emergency report phone number for the Nth record. valid phone numbers Reporting Defines whether an emergency report should be sent to the Em. report recipient during the emergency cycle: 0…1 0: 1: no yes As up to five emergency centers can be defined, the length of one MPTP message may not be enough to hold the whole persistent setting configuration. Normal rules for concatenating persistent setting configuring commands – described in section 4.
MPTP | MPTP commands 80 be overwritten. Authorized number N Authorized phone number N. valid phone numbers As up to 20 authorized numbers can be defined; the length of one MPTP message may not be enough to hold the whole persistent setting configuration. Normal rules for concatenating persistent setting configuring commands – described in section 4.6 – allow a command to be broken down over several messages in this case.
MPTP | MPTP commands 81 4.6.4. Setting 0300: GPRS Telematics settings This command is used to set the User ID, Service number settings and GPRS use and Sending settings for GPRS telematics function. Supported Benefon/TWIG instruments and SW versions: Send Receive • • • Twig Discovery Pro SW CD??.02.000.00000 Twig Locator SW CL??.02.00.000 Twig Protector SW CG1P.01.001.
MPTP | MPTP commands User ID 82 Defines the ID number of the device. Number must be same as used in the backend. Typically own phonenumber String of 0…40 digits If the number is not set, the backend server cannot identify the transmissions Service number Defines the Service Number that is used incase the GPRS connection fails and SMS is defined as backup. Only Twig Discovery. If the number is not defined SMs backup on the messaging will not be used.
MPTP | MPTP commands 83 Supported Benefon/TWIG instruments and SW versions: Send Receive • • • Twig Discovery Pro SW CD??.02.000.00000 Twig Locator SW CL??.02.00.000 Twig Protector SW CG1P.01.001.0000 4 1 5 1 4 1 ?CNF _ 01/01 _ 0301 _ 0…32 1 0…32 1 0…32 internet _ username _ password 1 DNS2 DNS1 Password User name APN Setting ID Command* Part number* Command format 0…16 1 0…16 _ 123.456.456.444 _ dom@in.com *) cf. section 3.1 for description of this field.
MPTP | MPTP commands 84 not allowed to be chaged in the device by default and only factory preprogrammed values are used. This applies specifically to Twig Discovery Pro range. Supported Benefon/TWIG instruments and SW versions: Send Receive • • • Twig Discovery Pro SW CD??.02.000.00000 Twig Locator SW CL??.02.00.000 Twig Protector SW CG1P.01.001.0000 4 1 5 1 4 GPRS port number GPRS IP adderss Setting ID Command* Part number* Command format 1 ?CNF _ 01/01 _ 0302 _ 15 1 0…4 123.456.
MPTP | MPTP commands 85 4 1 5 1 4 1 ?CNF _ 01/01 _ 0303 _ 0…4 1 0…12 1 _ 081030123000 Accelerometer Duration Accelerometer sensivity Pwr OFF Delay, mins Pwr ON Interval, mins Start up time, yymmddhhmmss PWR On/Off mode Setting ID Command* Part number* Command format 1 0…5 1 0…5 1 0…3 1 0…3 _ 60 _ 5 _ 3 The special fields of the command are as follows: Field Description Range Setting ID Numeric identifier of the setting being configured. In this case, the ID is 0303.
MPTP | MPTP commands 86 4.6.8. Settings 2001–2009 -General Settings Defines the General instrument related settings. Settings can be sent in same message with limitation of 5 settings or total length of message 160 characters depending which is met first. Note that only Setting ID’s from 2000 can be combined into set of 5. (CNF2008 requires FW CG1P.01.020.0000 or later, CNF2009 requires CT1P.01.005.
MPTP | MPTP commands 2006 2007 87 MPTP header translation Defines if MPTP command headers are changed from ? to Q and ! to E. Needed in some countries due to SMSC functions. automatic answer Defines if call from any number is automatically answered. Discards whitelist call check. Default 0 0=disabled 1=enabled ( translate) 0=disabled 1=enabled 2=block all incoming calls 2008 Power off disabled 2009 Power saving mode Defines if the power key can be used to turn off the device.
MPTP | MPTP commands 4.6.10. 88 Settings 2101–2105 –Information messaging Defines the Automatic status messaging use. The INF-reply is defined in 2.2.4. Settings can be sent in same message with limitation of 5 settings or total length of message 160 chacaters depending which is met first. Supported TWIG instruments and SW versions: Send Receive • Twig Protector SW CG1P.01.001.0000 Check Command format from 4.6.
MPTP | MPTP commands 89 Check Command format from 4.6.8 The special fields of the command are as follows: Setting ID Field Description 2201 SOS Key activation mode Defines how the TWIG SOS button is activated. If set to 0, button is not active 2202 Activation method timeout Defines how long the SOS button needs to be pressed or within what tiem it needs to be pressed twice. default 5 2203 GPS ON time Defines GPS on time after TWIG SOS is activated.
MPTP | MPTP commands 90 Check Command format from 4.6.8 The special fields of the command are as follows: Setting ID Field Description 2211 Displays Defines how the display is reacting on the TWIG SOS button. If displays are disabled also backlight is disabled. Default 1. 2212 Vibrator Defines if vibrator is used to indicate “keep pressing” or “press twice”. Vibrator will activate in same sequence ans the wedges on the screen even if the displays are off.
MPTP | MPTP commands 91 Check Command format from 4.6.8 The special fields of the command are as follows: Setting ID Field Description 2301 Event type Defines the type of event number 1 2302 Number Defines the recipient 1 number 2303 Name Defines the recipient 1 name 2304 Event retries Defines how may retries are done to this individual event. Default= 1 2305 Event group Defines the group the event is linked.
MPTP | MPTP commands 92 2331 Event type Defines the type of event number 4 2332 Number Defines the recipient 4 number 2333 Name Defines the recipient 4 name 2334 Event retries Defines how may retries are done to this individual event. Default= 1 2335 Event group Defines the group the event is linked.
MPTP | MPTP commands 93 1=SMS 2=call 0-24 numbers 2371 Event type Defines the type of event number 8 2372 Number Defines the recipient 8 number 2373 Name Defines the recipient 8 name 2374 Event retries Defines how may retries are done to this individual event. Default= 1 2375 Event group Defines the group the event is linked.
MPTP | MPTP commands 94 Check Command format from 4.6.8 The special fields of the command are as follows: Setting ID Field Description 2400 MPTP SOS Text Defines the text, that is added to the data field on EMG message when TWIG SOS is sent from SOS key. Default= SOS BUTTON 2401 MPTP MD Text Defines the text, that is added to the data field on EMG message when TWIG SOS is sent from Man Down Alert.
MPTP | MPTP commands 4.6.15. 95 Settings 2430–2431 –TWIG SOS Post emergency cycle Defines the General TWIG SOS post emergency cycle settings . Settings can be sent in same message with limitation of 5 settings or total length of message 160 chacaters depending which is met first. Supported Benefon/TWIG instruments and SW versions: Send Receive • Twig Protector SW CG1P.01.001.0000 Check Command format from 4.6.
MPTP | MPTP commands 96 Check Command format from 4.6.8 The special fields of the command are as follows: Setting ID Field Description 2440 Alerts when Defines the orientation/environment when the alarm is detected 2441 Sensor usage Define the operating mode of the sensor. Default 0.
MPTP | MPTP commands 97 Check Command format from 4.6.8 The special fields of the command are as follows: Setting ID Field Description 2500 GPRS usage Defines if GPRS is used or not. Default 1 2501 USER ID Defines the ID used in GPRS communications 2502 Service Number Defines the Service number for MPTP messages used in GPRS backup 2503 IP address Defines the Gateway IP address. Default TWIG Server.
MPTP | MPTP commands 98 Check Command format from 4.6.8 The special fields of the command are as follows: Setting ID Field Description 2550 ASSIST CALL 1 Defines the call number 2551 ASSIST SMS 1 Defines the SMS number 2552 ASSIST CALL 2 Defines the call number 2553 ASSIST SMS 2 Defines the SMS number 2554 ASSIST CALL 3 Defines the call number 2555 ASSIST SMS 3 Defines the SMS number 2556 ASSIST CALL 4 Defines the call number 2557 ASSIST SMS 4 Defines the SMS number 4.6.19.
MPTP | MPTP commands Check Command format from 4.6.
MPTP | MPTP commands 100 Setting ID Field Description 2601 White list number 1 Defines the CALL/SMS number 2602 WLN 1 LOQ Defines the WLN 1 SMS location request permission Default=1 2603 WLN 1 TRG Defines the WLN 1 SMS tracking request permission Default=1 2604 WLN 1 CALL Defines the WLN 1 Call permissions Default=1 2611 White list number 2 Defines the CALL/SMS number 2612 WLN 2 LOQ Defines the WLN 2 SMS location request permission Default=1 2613 WLN 2 TRG Defines the WLN 2 SMS trac
MPTP | MPTP commands 101 2643 WLN 5 TRG Defines the WLN 5 SMS tracking request permission Default=1 2644 WLN 5 CALL Defines the WLN 5 Call permissions Default=1 2651 White list number 6 Defines the CALL/SMS number 2652 WLN 6 LOQ Defines the WLN 6 SMS location request permission Default=1 2653 WLN 6 TRG Defines the WLN 6 SMS tracking request permission Default=1 2654 WLN 6 CALL Defines the WLN 6 Call permissions Default=1 2661 White list number 7 Defines the CALL/SMS number 2662 WLN 7
MPTP | MPTP commands 102 2691 White list number 10 Defines the CALL/SMS number 2692 WLN 10 LOQ Defines the WLN 10 SMS location request permission Default=1 2693 WLN 10 TRG Defines the WLN 10 SMS tracking request permission Default=1 2694 WLN 10 CALL Defines the WLN 10 Call permissions Default=1 2701 White list number 11 Defines the CALL/SMS number 2702 WLN 11 LOQ Defines the WLN 11 SMS location request permission Default=1 2703 WLN 11 TRG Defines the WLN 11 SMS tracking request permiss
MPTP | MPTP commands 103 2733 WLN 14 TRG Defines the WLN 14 SMS tracking request permission Default=1 2734 WLN 14 CALL Defines the WLN 14 Call permissions Default=1 2741 White list number 15 Defines the CALL/SMS number 2742 WLN 15 LOQ Defines the WLN 15 SMS location request permission Default=1 2743 WLN 15 TRG Defines the WLN 15 SMS tracking request permission Default=1 2744 WLN 15 CALL Defines the WLN 15 Call permissions Default=1 2751 White list number 16 Defines the CALL/SMS number
MPTP | MPTP commands 104 Check Command format from 4.6.8 The special fields of the command are as follows: Setting ID Field Description Range 2800 Amber Alert mode Defines the mode of function. Only 0-2 are currently in use. 0=OFF, 1=Interactive, 2=local, 3=remote, 4=automatic Default 0 4.7. 2801 Amber Alert Type Defines the activation mode whether SMS or voice call. Default 1 2802 Amber Alert / Condition Check ACK Defines in REMOTE mode if Acknowledge is needed.
MPTP | MPTP commands 105 Depending on the authorization of the Control Centre which requested the action, the action may be performed automatically or the request may be disregarded altogether. Cf. section 2.1.3 for more information. 4 1 5 … Setting ID Setting ID Setting ID Command* Part number* Command format 1 4 1 4 1 4 ?PSR _ 01/01 _ 0060 _ 0051 _ 0068 … … *) cf. section 3.1 for description of these fields.
MPTP | MPTP commands 106 For the format of most of the persistent setting reports cf. 4.6. Command is of course replaced with !PSR. Reset terminal request (?RST) CC → MTT This command can be used to reset the terminal remotely. Resetting terminal means that it is switched off and on again after awhile. The command can also be used to reset the device to factory defaults Supported Benefon/TWIG instruments and SW versions: Send Receive • Twig Protector SW CG1P.01.001.
MPTP | MPTP commands 107