This new architecture reduces the influence of a single TSP on the vehicle manufacturer as the system architecture is broken down into individual components and common standards allow different suppliers to provide different parts of the system to BMW.

BMW says NGTP v2 provides technology-neutral interfaces that promote flexible implementation of new services. Although BMW has promoted the NGTP concept for use by other vehicle manufacturers, no other carmakers have started to use the concept so far.

BMW has led the development of the NGTP concept in an attempt to free itself from restrictive and expensive client/service provider relationships with TSPs. NGTP was launched with the aim of acting as a common standard to allow vehicle manufacturers to change service providers without being tied to proprietary technology, or to use multiple service providers.

A presentation from the NGTP group describing v2 lists BMW, WirelessCar, Ygomi and Navteq as participants. This is first time that Navteq has been publicly listed as a member of NGTP, however there are strong ownership ties between Ygomi and Navteq through Russ Shields.

NGTP was formerly known as a ‘Protocol’ but is now named a ‘Pattern.’ The Pattern name is an attempt to indicate that NGTP provides a general reusable solution that is open to new requirements. It is supposed to differentiate NGTP from traditional standards.