Connecting CAN networks to cloud services

The integration of CAN-based networks into TCP/IP and telematics environments has a long history. Already mid of the 90ties, CANopen networks were remotely controlled by means of TCP/IP routers and gateways. The CiA 309 specification series supports such kind of TCP/IP connectivity. Besides an ASCII-based protocol, this series also specifies a ModbusTCP protocol and a gateway to ProfinetIO. Additionally, this series supports CiA 309-5 which specifies a mapping of CANopen communication services to RESTful, HTTP, and WebSocket protocols.

CiA has also specified a generic CANopen gateway to wireless networks. The CiA 457 profile specifies the CANopen port.

CiA does not specify in detail the wireless port of telematic gateways. However, CiA supports the specification of CAN ports. A typical example is the Telematic Gateway Unit (TGU) of DIN 4630 for commercial vehicle body builders. It collects data from the body application units and forwards them to cloud service providers. A similar approach for commercial vehicles is the fleet management system (FMS) specified by ACEA (European Automobile Manufacturers' Association). It forwards J1939-based parameter groups (PG) via telematic gateways to cloud service providers. Normally, such telematic gateways are implemented in self-propelled vehicles.