177
edits
Changes
→Pre-Requisites for server implementation
|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.
|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
|Memory Requirements
|Cloud services demand a large amount of memory, which is why the minimum recommended memory size is 8GB.
|Cloud services demand a large amount of memory, which is why the minimum recommended memory size is 8GB.
|-
|-
|Hard disk
|Hard disk
|For a medium-sized server, 300GB RAID1 disks can be recommended.
|For a medium-sized (up to a 1000 devices) server, 300GB RAID1 disks can be recommended.
|-
|-
|Database
|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.
|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.
|-
|-
|Security
|Security
|Teltonika devices support TLS Encryption which can be implemented on the server side.
|Teltonika devices support TLS Encryption which can be implemented.
[[How to generate TLS certificates (Windows)?]]
|-
|-
|Programming Skills
|Programming Skills
|Knowledge about programming language is an asset, where Python, C#, JAVA can be used for Backend.
|Knowledge about programming language is a must. Teltonika Telematics is a hardware production company, we do not provide software programming services and cannot help with writing code for the server. Only consult on the logic and algorithms of device features and possible issues in data interpretation from the server side.
|-
|-
|Hardware Knowledge
|Hardware Knowledge
|It can be found on our Teltonika WIKI: https://wiki.teltonika-gps.com/view/Main_Page
|It can be found on our Teltonika WIKI: https://wiki.teltonika-gps.com/view/Main_Page
To understand the devices, their use cases and how they send data.
|-
|Protocol Implementation
|Teltonika Telematics device protocols need to be implemented for the server to understand and parse the received data correctly.
[[Teltonika Data Sending Protocols]]
|-
|-
|Socket Programming
|Socket Programming
|Sockets and the socket API are used to send messages across a network. For Teltonika devices to make connection to your server, the server needs to have an application socket programmed to accept these connection request.
|Sockets and the socket API are used to send messages across a network. For Teltonika devices to make connection to your server, the server needs to have an application socket programmed to accept these connection request.
'''Note:'''
Each socket should be dedicated to one device, this will allow the server to differentiate the devices when more than 1 device is sending data at the same time.
|-
|-
|Network Considerations
|Network Considerations
|-
|-
|IP Address Requirements
|IP Address Requirements
|Static IP or a dedicated port and domain is required because device configuration would always need to be changed if IP and Port would change, which is not convenient.
|Static IP or a dedicated port and domain is required otherwise device configuration would need to be updated constantly with a new IP or a new Port.
|-
|-
|}
|}