8
edits
Changes
no edit summary
|-
|-
|To develop the platform, below are the requirements:
|To develop the platform, below are the requirements:
#Hardware Requirements: A high CPU count promotes better cloud tiering throughout because although object storage can be slow in I/O operations per thread, object storage can support many threads. Any standard x86 64-bit servers can be ideally used.
#Memory/RAM Requirements: Cloud tiering services demand a large amount of memory, which is why the minimum recommended memory size is 8GB.
#Harddisk Requirements: For a medium-sized server, 300GB RAID1 disks can be recommended.
#Network Protocols: TCP/IP and UDP are the basic protocols supported by our devices. MQTT is also supported.
#Knowledge about programming language is an asset, where Python, C#, JAVA can be used for Backend.
#Database: A database is required to store the records/messages incoming from multiple devices. Further, this data must be assigned to its appropriate device ( recognized by IMEI ). MySQL can be used for the database.
#Skillsket for Socket Programming is an asset to develop a server.
#Security: Teltonika device support TLS Encryption which can be implemented on the server side.
#Hardware Knowledge: It can be found on our Teltonika WIKI: https://wiki.teltonika-gps.com/view/Main_Page
|}
|}
For example, IMEI 356307042441013 would be sent as 000F333536333037303432343431303133. First two bytes denote IMEI length. In this case 0x000F means, that IMEI is 15 bytes long.
For example, IMEI 356307042441013 would be sent as 000F333536333037303432343431303133. First two bytes denote IMEI length. In this case 0x000F means, that IMEI is 15 bytes long.
After receiving IMEI, server should determine if it would accept data from this module. If yes, server will reply to module 01, if not - 00. Note that confirmation should be sent as binary packet. I.e. 1 byte 0x01 or 0x00. Then module starts to send first AVL data packet. After server receives packet and parses it, server must report to module number of data received as integer (four bytes). If sent data number and reported by server doesn’t match module resends sent data.
After receiving IMEI, server should determine if it would accept data from this module. If yes, server will reply to module 01, if not - 00. Note that confirmation should be sent as binary packet. I.e. 1 byte 0x01 or 0x00. Then module starts to send first AVL data packet. After server receives packet and parses it, server must report to module number of data received as integer (four bytes). If sent data number and reported by server doesn't match module resends sent data.
|}
|}