The FAQ section answers common questions about NGTP. If you have a question which is not in this section, please contact us.

Summary Messages

  1. BMW collaborated with Connexis and WirelessCar on NGTP because as the industry evolves, fresh approaches to implementation will be required to compliment existing solutions. Connexis is a Ygomi company, so the NGTP Group member does the business now under the name of Ygomi. In addition, the NGTP Group welcomes Navteq (now HERE) as a new member since 2010.
  2. The objective of the pattern is to create flexibility and scalability in the delivery of telematics for the benefit of all players i.e., vehicle manufacturers and their customers, telematics communications unit (TCUs) manufacturers, service integrators, service providers and content providers.
  3. Vehicle manufacturers can mix and match telematics service providers and content providers.
  4. Telematics service providers and content providers can sell similar services to multiple manufacturers.
  5. The pattern focuses on standardized interfaces across the entire telematics eco-system

What is the difference between NGTP and existing industry patterns?

  1. NGTP is not a new standard to replace ACP or GATS. Rather, it is a technology-neutral pattern for delivering services to customers;
  2. NGTP address the whole telematics eco-system, not only the communication interface to the car;
  3. NGTP introduces a vehicle manufacturer – and TSP-neutral “dispatcher”, or switchboard, providing a common, stable interface between the telematic units and all service providers;
  4. By offering flexible interfaces through the dispatcher, NGTP provides a way to provide connectivity for the service life of the vehicle (which has a product life-cycle of 10+ years) and access to new developments in the fast-paced field of consumer electronics;
  5. NGTP’s Creative Commons ShareAlike license facilitates innovation and the wider marketing of telematics services.


What is the business case for NGTP?

NGTP’s developers set the following six objectives:

  1. Provide a technology-neutral pattern and consistent interface and protocol for telematics services;
  2. Reduce barriers to collaboration and implementation;
  3. Enable adoption of new technologies as they come online;
  4. Support legacy systems for connectivity throughout the service life of a vehicle;
  5. Gain wide acceptance and encourage innovation through an open approach;
  6. Increase the value proposition for vehicle manufacturers, service providers, content providers, and motorists.

How much development time, thinking and testing went into NGTP?

  1. NGTP involved a great deal of effort, more than one person-year was devoted to strategic development, technical specifications and testing.
  2. The pattern was tested by Ygomi and WirelessCar, and then the specifications were given to another provider, ATX, and was successfully tested in this third environment. Now, Ygomi, WirelessCar, ATX and BMW are using the newest version in a productive environment.

Did anyone already implemented a system that meets the NGTP requirements?

  1. Several companies are interested in NGTP, some of them already have implemented NGTP.
  2. BMW has migrated most of its telematics business to NGTP

What kind of services have already been implemented based on NGTP?

At BMW, the services E-Call, Information Call / Concierge, Send2Car and Remote Services have been implemented already. WirelessCar has added more services.

Does NGTP support the Pan European eCall?

Yes, the NGTP pattern is compatible to the Pan European TPS eCall.

What is the difference between NGTP 1.0 and 2.0?

According to the initial feedback we received, the documentation has been completely revised and should be much clearer now. On the conceptual level only minor extensions or changes have been made.

Why changed the meaning of the P in NGTP from protocoll to pattern?

Because NGTP specifies much mor than only a protocol. The protocol is only one aspect, the other aspect is the architectural pattern with its components and interfaces.

Is NGTP a BMW pattern?

  1. No. BMW wants to guide the industry toward an open infrastructure because BMW wants to be open to cultivate innovation, creativity and more options.
  2. The team deliberately chose a Creative Commons license so this is not a BMW specific pattern. The Creative Commons license is a way to publish a pattern (in fact any specification) so that it is publicly available to all who want to develop proprietary applications pursuant to the pattern (so that the proprietary applications will work smoothly together – assuming they all follow the pattern).
  3. In fact, NGTP is not limited to the car. It can also be used with PNDs and other devices not embedded in the dashboard. NGTP is intended for the entire industry.
  4. However, BMW has already implemented NGTP successfully worldwide and will be BMW’s telematics pattern in the future.

When will BMW launch a car model with services based on NGTP?

The telematics technology in the latest unit of the telematics control is already based on NGTP.

Where does telematics rank in strategic priority for BMW?

  1. ConnectedDrive is a strategic initiative for BMW. Telematics services are an important part of the car.
  2. ConnectedDrive currently serves 1,000,000 customers in 10 countries, and we are expanding rapidly.
  3. We are a technology leader in telematics today, just as we are the technology leader in many other areas (e.g., alternative energy options like diesel and hydrogen; lighter weight materials such as carbon and titanium). But, we are constantly looking toward the future for new technologies to improve the pure driving pleasure our customers experience when driving a BMW.

How does NGTP work?

  1. NGTP promotes openess and flexibility. It does this by separating the components of the telematics delivery chain, and introducing a ‘dispatcher’. The dispatcher provides a single interface between the telematics unit (TU) in the vehicle and the other components of the delivery chain.
  2. Since all the interfaces are technology-neutral, the back-end components including the Service Handler and the Service Integrator, call centre and content provider can be easily interchanged.
  3. The pattern is flexible for use with all telematics service offerings and in any country.
  4. The open interface created by NGTP also enables OEMs to continously provide new services to both legacy vehicles and new models over the entire vehicle lifecycle.

Why is the dispatcher concept so unique?

  1. While it is possible to incorporate a dispatcher into the service chain using GATs, it is not built into the pattern.
  2. The new dispatcher feature is technology neutral. It can translate services from any provider to the telematics unit in the car. It decouples the TU specifics from the rest of the backend. It is the core component for enabling integration of various TU providers and various backend providers into one platform.

How are you able to offer services throughout the service lifecycle of the vehicle?

In terms of the fact that vehicle technology become quickly outdated NGTP’s flexibility offers customers the ability to conveniently access new services without the hassle of making technical adjustments inside the vehicle.

Is VoIP reliable for emergency call handling?

The NGTP specification recommends VoIP as a technology to deliver voice calls within the backend. The support of emergency call handling in VoIP based telephone networks has been adressed by the telecom industry. The protocols and procedures needed to enable this service exist and can be delivered today.

How do we find out more about adopting the NGTP pattern?

The website www.ngtp.org includes the information that is publically available.

Are there any requirements for the TU to communicate with a NGTP based backend?

The TU must use the NGTP protocol for communication.

What about missing operations inside the interfaces?

Missing operations can easily be added.

Are the interfaces parts of the components?

As the components communicate via interfaces, these are needed on both ends to exchange the necessary information.

Why can triggers only be sent by the dispatcher?

Separation of concerns. The task of the DSPT is to identify the correct recipient of an event based on rules/configuration from PDP. If also other NGTP components would take over this task, the overall complexity of the system and the risk of inconsistencies/redundancies would be much higher.

What is the benefit of the uni-directional communication concept?

Simplicity, Scalability, Robustness, Flexibility.

Where is the NGTP message format obligatory?

Between the Telematic Unit and the Dispatcher.

Where does NGTP store information about access rights or who is allowed to use which service?

Inside the CDP component (Customer Data Provider).

How does NGTP cover the management of the data stores like PDP (Provisioning Data Provider) or offline CP (Content Provider)?

This is not addressed by NGTP.

Is there any software for download and installation of a NGTP solution?

The NGTP specification is a high level specification, there are no ready-to-use runtime components provided by NGTP. But an ASN.1 sample implementation of the NGTP message format can be made available.

How can I use a NGTP based system for data streaming or browsing cases?

Future versions of NGTP will contain patterns for those use cases.

Is it allowed to merge components and drop interfaces?

Of course it is possible to merge components, but then some of the main advantages of NGTP like flexibility, scalability and interoperability across partners are given up.

Which programming languages can be used for software implementation?

Any. Since NGTP is a high level specification, it does not rely on specific programming languages or communication technologies.