NGTP2.0原版完整文件.docx

《NGTP2.0原版完整文件.docx》由会员分享，可在线阅读，更多相关《NGTP2.0原版完整文件.docx（44页珍藏版）》请在淘文阁 - 分享文档赚钱的网站上搜索。

1、The NGTP Group2010-10-01NGTP 2.0 CompendiumVersion 1.0Page 2 of 44NGTP 2.0CompendiumThis 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/legalcodeRevision HistoryDateVersionDescrip

2、tionAuthor2010-03-010.01Initial versionNGTP Group2010-03-110.03Initial version revisedNGTP Group2010-03-260.06Rework architecture descriptionNGTP Group2010-03-310.07Rework according to the comments from mr. DitzellNGTP Group2010-04-010.08Rework according to the comments from mr. ZollerNGTP Group2010

3、-04-200.12Rework according to the comments from WCarNGTP Group2010-04-300.151st draft version for initial reviewNGTP Group2010-05-110.172nd draft for reviewNGTP Group2010-05-200.183rd draft for (final) reviewNGTP Group2010-07-290.20Ready for external reviewNGTP Group2010-10-011.0Rework according to

4、external reviewNGTP GroupThe NGTP Group2010-10-01NGTP 2.0 CompendiumVersion 1.0Page 3 of 44Table of ContentsThis 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/legalcode1 Introduc

5、tion61.1 Motivation for the NGTP Group61.2 About NGTP 2.071.3 About this compendium92 Glossary and abbreviations103 Basic-Pattern: Architecture overview123.1 Short description / summary123.2 Main design concepts143.3 Communication concept163.3.1 Trigger concept163.3.2 Operations164 Basic-Pattern: NG

6、TP components / building blocks174.1 Telematics Unit (TU)174.1.1 Short description / summary174.1.2 Design principles174.1.3 Related interfaces174.2 Dispatcher (DSPT)184.2.1 Short description / summary184.2.2 Design principles184.2.3 Related interfaces194.2.4 Events194.3 Service Handler (SH)204.3.1

7、Short description / summary204.3.2 Design principles204.3.3 Related interfaces204.4 Service Integrator (SI)204.4.1 Short description / summary204.4.2 Design principles214.4.3 Related interfaces214.5 Public Safety Answering Point (PSAP)214.5.1 Short description / summary214.5.2 Design principles224.5

8、.3 Related interfaces224.6 Call Center (CC)224.6.1 Short description / summary224.6.2 Design principles224.6.3 Related interfaces234.7 Other Services (OS)234.7.1 Short description / summary234.7.2 Design principles234.7.3 Related interfaces234.8 Provisioning Data Provider (PDP)234.8.1 Short descript

9、ion / summary234.8.2 Design principles244.8.3 Related interfaces244.9 Customer Data Provider (CDP)244.9.1 Short description / summary244.9.2 Design principles244.9.3 Related interfaces254.10 Content Provider (CP)254.10.1 Short description / summary254.10.2 Design principles264.10.3 Related interface

10、s265 Basic-Pattern: NGTP interfaces275.1 Interface 1 (TU DSPT)285.1.1 Short description / summary285.1.2 Connected blocks285.1.3 Operations285.1.4 NGTP message format285.2 Interface 2 (DSPT SH)305.2.1 Short description / summary305.2.2 Connected blocks305.2.3 Operations305.3 Interface 3 (PDP DSPT)31

11、5.3.1 Short description / summary315.3.2 Connected blocks325.3.3 Operations325.4 Interface 4 (CDP SH)325.4.1 Short description / summary325.4.2 Connected blocks325.4.3 Operations335.5 Interface 5 (SI PSAP)335.5.1 Short description / summary335.5.2 Connected blocks335.5.3 Operations345.6 Interface 6

12、(SH SI)345.6.1 Short description / summary345.6.2 Connected blocks355.6.3 Operations355.7 Interface 7 (CP SI)365.7.1 Short description / summary365.7.2 Connected blocks365.7.3 Operations375.8 Interface 8 (SI CC)375.8.1 Short description / summary375.8.2 Connected blocks375.8.3 Operations385.9 Propri

13、etary Interface (SI OS)385.9.1 Short description / summary385.9.2 Connected blocks385.9.3 Operations386 General aspects396.1 Security396.2 Logging406.3 Monitoring417 Getting started428 Further references441 Introduction1.1 Motivation for the NGTP GroupHistorically, vehicle manufacturers have offered

14、 customers proprietary services and have been de- pendent on a single Service Provider (SP) for delivery of these services in a specific market. This sup- ply chain inflexibility made it difficult for providers to gain economies of scale and advance their offer- ings.A more open and standardized app

15、roach to delivering services has clear benefits for the marketplace, but previous standardization efforts focused on replacing existing protocols, rather than integrating them, which met barriers to adoption.With the proliferation of new technologies (e.g., UMTS, Wi-Fi, VoIP), it is likely that futu

16、re in-vehicle devices will access services using multiple methods and technologies. The NGTP Group concluded that the telematics industry would greatly benefit from a technology-neutral pattern to expand the op- tions for delivering services. If possible, NGTP recommends using existing standards and

17、 technologies (see also the NGTP message format) where applicable, instead of re-invention.So NGTP provides the vehicle manufacturers a wider range of service offerings and service providers to cooperate with and the service providers have the possibility to re-use their solutions.The NGTP Solution

18、Open and Adaptable ConnectivityNGTP (Next Generation Telematics Pattern) is a new approach for delivering over-the-air services to in-vehicle devices and handsets alike, with the focus on open interfaces across the entire service de- livery chain.NGTPs developers set the following six objectives: Pr

19、ovide a technology-neutral pattern and consistent interface and protocol for telematics ser- vices; Reduce barriers to collaboration and implementation; Enable adoption of new technologies as they come online; Support legacy systems for connectivity throughout the service life of a vehicle; Gain wid

20、e acceptance and encourage innovation through an open approach; Increase the value proposition for vehicle manufacturers, service providers, content providers, and motorists.NGTP will enable vehicle manufacturers to use the best offerings from a variety of partners while maintaining a consistent dri

21、ver experience. The new pattern will also allow service providers and con- tent providers to re-use the same basic services like session management or a voice/data matching to multiple vehicle manufacturers. Moreover, the NGTP architecture enables an easy integration of leg- acy systems, allowing ol

22、der and newer vehicles alike to access new telematics offerings.NGTP accommodates the EUs pending eCall initiative, and the patterns open architecture will ac- commodate future industry trends.In order to foster collaboration and innovation, the specifications that constitute NGTP are public under a

23、 Creative Commons licence. The NGTP Group will work with the telematics community to communi- cate the specifications and support testing and potential adoption of NGTP.1.2 About NGTP 2.0NGTP is neither a traditional standard nor a product. NGTP aims to provide a general reusable solu- tion to a com

24、monly occurring problem. In the software development community this is called a design pattern. This is why the use of “pattern” instead of “protocol” in the NGTP 2.0 abbreviation more cor- rectly describes the vision behind NGTP. Design patterns can speed up development by providing tested and prov

25、en development paradigms while at the same time being open and flexible to new re- quirements.A standard is an established norm, a formal document that establishes uniform engineering, and to achieve this, very detailed specifications are required. Standards provide compatibility at the expense of f

26、lexibility. The NGTP Group believes that flexibility is more important and has chosen the pattern approach.Since publishing NGTP 1.0 in January 2008, the NGTP Group established real world implementations based on the NGTP pattern and received a lot of interest from the telematics industry. There are

27、 two main reasons for publishing the successor of the 1.0 publication now:1. The implementation of NGTP based telematics services and the telematics technologies have further evolved. The NGTP Group wants to share the experiences and best practices to NGTP and incorporate them in a new version 2.0.2

28、. The 1.0 documentation describes the architecture in horizontal “layers”. As the stakeholder are implementing NGTP in a vertical way (by building blocks), the NGTP Group decided to re- structure the documentation by explaining each building block with its interfaces. That comes in line with some ch

29、anges in wording for an overall much more comprehensive documenta- tion.Therefore the 2.0 release is not a kind of new pattern but incorporates a new view on the pattern and some extensions. NGTP 1.0 is still a valid pattern. That means that all solutions built up on NGTP 1.0 require no or only mini

30、mal changes to comply the NGTP 2.0 specification. There is no kind of migra- tion from release 1.0 to 2.0 necessary.Changes from NGTP 1.0 to 2.0Figure 1 Changes from NGTP 1.0 to NGTP 2.0Architecture Organisational building block TSP“ has been removed from architecture and replaced by in- frastructur

31、e blocks Service Handler“ and Service Integrator“, because NGTP should provide a task-based (role-based) view and not an organisational or physical view on the telematics architecture. The Service Handler“ enriches the data for the Service Integrator“ that is responsible for in- tegrating the servic

32、es with the help of Content Providers, Call Centres and so on. Interface 6(a) connects to the Service Integrator“ now (formerly: direct connection to Call Center). This is again due to the fact that NGTP does not want to define an architecture based on organizational responsibilities, but on tasks.

33、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 has been renamed by 6“ as there wont b

34、e an Interface 6b any more (see next paragraph). Interface 6b has been removed as the Service Integrator“,gets the content through Interface 7 Interface 8 has been introduced for connecting the Call Center via the Service Integrator“ as the data for the Call Center may have to be enriched and integr

35、ated by the Service Integra- tor“ before routing 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 a

36、re 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 servi

37、ce data that are provided by an OEMWording 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 (i

38、n contrast to an organisational view) and the technology neutral connectivity for ser- vicesFurther oulookWhile 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

39、in the NGTP group and will be incorporated in future releases of NGTP.1.3 About this compendiumThe NGTP 2.0 compendium is intended for all interested members of the telematics industry. It gives an overview on the architecture, the building blocks and the interfaces of basic-pattern of NGTP 2.0. In

40、order to service as a technology neutral pattern, which is independent from customer specific require- ments, the level of detail is kept to the point where the principles of the solutions become clear and a flexible connectivity of NGTP based implementations is assured. Hence this is not a technica

41、l specifi- cation but rather a semantic description of NGTP.To keep the compendium in this compact size, the examples are summarized in an additional docu- ment. They show additional details of real world implementations and provide some ideas about the possible solutions that are inherent to this p

42、attern.The compendium is accompanied by the following appendixes: NGTP examples NGTP release processes NGTP in a nutshell (presentation)The compendium was jointly developed by members of the NGTP Group and is published under a creative commons licence. Any feedback and comments are highly welcome an

43、d can be provided by registered users onwww.ngtp.org2 Glossary and abbreviationsTerm / abbre- viationExplanationAPIApplication Programmer Interface, an interface implemented by a software program to enable its interaction with other softwareASN.1Abstract Syntax Notation One is a standard and flexibl

44、e notation that describes data structures for representing, encoding, transmitting, and decoding dataCCCall CenterCCACal Center AgentCDPCustomer Data ProviderCPContent ProviderDSPTDispatcher, one of the main NGTP componentsECallEmergency callMSDminimum set of dataNGTPNext Generation Telematics Patte

45、rn(formally: Next Generation Telematics Protocol)OperationInterface methods on a business levelOSOther Services, any other possible telematics services delivered via the SIPDPProvisioning Data ProviderPOIPoint of interest, a GPS location e.g. the current location of a vehicle. A GPS POI contains at

46、minimum the latitude and longitude of the related locationPSAPPublic Safety Answering Point, a Call Center for answering emergency calls for po- lice, firefighting and ambulance servicesSHService Handler, one of the main NGTP componentsSIService Integrator, one of the main NGTP componentsSPService P

47、roviderTSPTelematics Service ProviderTUTelematics Unit, sometimes also called TCU (Telecommunication Control Unit) e.g. mobile phones, navigation devices, communication units in vehicles UMTSUniversal Mobile Telecommunications System is one of the third-generation (3G) mobile telecommunications technologies, which is also being developed into a 4G technology.