Data Center Operations

Connexis supports vehicle manufacturers and Tier‑1 suppliers with systems integration and data center operations for R&D and commercial operations. Our worldwide network of facilities provides low latency and high availability.
  • Automatic Crash Notification (ACN) and emergency call
  • Remote vehicle control such as remote door unlock and HVAC adjustment
  • Remote diagnostics and maintenance scheduling
  • Remote vehicle software updating
  • Customer relationship management and billing systems
  • Vehicle probe data management for engineering research and safety applications
Connexis has data centers in the U.S., China, and Japan:
  • Grand Forks, North Dakota, U.S.A.
  • Chengdu, China
  • Yokohama, Japan
Each Connexis data center is built for fault tolerance, with redundant equipment such as multiple uninterrupted power supplies, dual power backups, and air conditioning; dual networks; and high-availability devices, such as multiple firewalls, routers, and switches. We also duplicate key equipment such as disk arrays and error-correcting memory modules. 
The inter-site network infrastructure relies on multiple ISPs to provide a redundant managed mesh network between Connexis, content providers, partners, and customers. 
The backbone of Connexis’s technology for implementing TSP services is NGTP, which Connexis developed with BMW. This back-end platform is open source and extensible to add future services and protocols. It can handle data using any over-the-air protocol and supports connections via embedded devices, tethered mobile phones, and web-enabled devices. 
The NGTP architecture is composed of subsystems that connect flexibly to content sources, call centers, and service providers through a set of specified interfaces. For instance, for map data, the Connexis Service Integrator can interface to any geographic content provider. The chart below shows the high-level structure of the Connexis TSP platform.
NGTP 2.0 Architecture
  • The Dispatcher is a land-side component that receives data from the vehicle and acts as a switchboard for the data and voice traffic between the vehicle and the back‑end infrastructure. It is neutral as to communications technology, able to receive data via any communications protocol. It routes IP data streams to the Service Integrator through the Service Handler.
  • The Service Handler is used to make service authorization decisions and per-user service execution logic customizations.
  • The Service Integrator contains the engine for processing all data services, the engine for managing data formats, and the core business logic to integrate services and results provided by the content service provider, call center, and web portal subsystems.