
NGTP 2.0 Compendium
Version 1.0
This work is licensed under the Creative Commons Attribution Share Alike (by-sa) License.
To view a copy of this license, visit http://creativecommons.org/licenses/by-sa/3.0/legalcode
Architecture
n-
, because NGTP should provide
a task-based (role-based) view and not an organisational or physical view on the telematics
architecture.
n-
tegrating the services with the help of Content Providers, Call Centres and so on.
Center). This is again due to the fact that NGTP does not want to define an architecture
based on organizational responsibilities, but on tasks. The Call Center node in the NGTP ar-
chitecture is to be seen only as the Call Center service, any Call Center application is pro-
vided by the service integrator. Of course a real Call Center can obtain both roles and provide
its own application. The interface
any more (see next paragraph).
Interface ,gets the content through Interface
7
Interface 8 has been introduce
the data for the Call Center may have a-
directly to the Call Center.
Interface 9 is reserved for additional other (proprietary) services or interfaces.
Protocol
The ASN.1 files have been re-structured in a common part, a dispatcher part and a service
part (ASN.1 files are not mandatory and are only one possible format for the protocol)
The common part includes general and reusable message structures that can be imported in
other ASN.1 files
The dispatcher files provide message structures for dispatching the messages between the
interfaces
The service part contains all application service data that are provided by an OEM
Wording
The use of pattern instead of protocol in NGTP as the technically more correct term
Term operations instead of methods, corresponding to the pattern concept
Service Provider (SP) instead of Telematics Service Provider (TSP) to reflect the task-based
view (in contrast to an organisational view) and the technology neutral connectivity for ser-
vices
Further oulook
While the NGTP 2.0 pattern described here still focuses on voice based services, different patterns for
other kinds of services, e.g. web-based data-only services, are currently being discussed in the NGTP
group and will be incorporated in future releases of NGTP.