BS ISO 15638-1:2012:2013 Edition
$215.11
Intelligent transport systems. Framework for collaborative Telematics Applications for Regulated commercial freight Vehicles (TARV) – Framework and architecture
Published By | Publication Date | Number of Pages |
BSI | 2013 | 120 |
This part of ISO 15638 provides the following for cooperative telematics applications for regulated commercial freight vehicles (4.37):
-
A framework (4.20) for the provision of cooperative telematics application services for regulated commercial freight vehicles;
-
A description of the concept of operation, regulatory aspects and options and the role models;
-
A conceptual architecture (4.7) using an on-board platform and wireless communications to a regulator (4.25) or his agent;
-
References for the key documents on which the architecture (4.7) is based;
-
Details of the architecture (4.7) of the facilities layer;
-
A taxonomy of the organisation of generic procedures;
-
Common terminology for the ISO 15638 family of standards.
This part of ISO 15638 is based on a (multiple) service provider (4.39) oriented approach.
ISO 15638 has been developed for use in the context of regulated commercial freight vehicles. There is nothing however to prevent a jurisdiction extending or adapting the scope to include other types of regulated vehicles, as it deems appropriate.
NOTE The specific ‘approval’ procedures for specific application services are a matter for the jurisdiction (4.24) and are outside the scope of this (or any) part of 15638. However approval authorities (4.6) are encouraged to use the guidance of ISO 17000 and ISO/IEC 17065:2012 when developing and implementing such procedures.
PDF Catalog
PDF Pages | PDF Title |
---|---|
11 | 1 Scope 2 Conformance |
12 | 3 Normative references |
13 | 4 Terms and definitions |
17 | 5 Abbreviated terms |
20 | 6 General overview and framework 6.1 Objective 6.2 National variations |
21 | 6.3 Mandatory, optional and cooperative issues 6.4 Specification of service provision 6.5 Architecture options 6.6 Approval of service providers |
22 | 7 Concept of operations 7.1 General 7.2 Statement of the goals and objectives of the system 7.3 Strategies, tactics, policies, and constraints affecting the system 7.4 Organisations, activities, and interactions among participants and stakeholders 7.5 Clear statement of responsibilities and authorities delegated 7.6 Operational processes for the system |
23 | 7.6.1 Service requirements definition 7.7 Appointment of an approval authority (regulatory) 7.8 Role of service provider 7.9 User 7.10 Application service |
24 | 8 Conceptual architecture framework 8.1 General 8.2 Actors |
26 | 8.3 Service definition |
28 | 8.4 Role model architecture 8.4.1 General 8.4.2 Jurisdictions |
29 | 8.4.3 Service provider(s) |
31 | 8.4.4 Application services |
32 | 8.4.5 The IVS equipment installer |
33 | 8.4.6 The IVS equipment maintainer 8.4.7 Approval authority (regulatory) 8.4.8 Certification authority (digital) |
34 | 8.4.9 Service provider approval 8.4.10 Application service approval 8.4.11 in-vehicle system (IVS) approval |
35 | 8.4.11.1 IVS type approval 8.4.11.1.1 VS instantiated as an OBU 8.4.11.1.2 IVS instantiated not as an OBU 8.4.11.1.3 IVS attributes |
36 | 8.4.11.1.3.1 Central processing unit 8.4.11.1.3.2 Data storage means 8.4.11.1.3.3 Data input means 8.4.11.1.3.4 Connectivity means to/from auxiliary equipment 8.4.11.1.3.5 Communications means |
37 | 8.4.11.1.3.6 Power supply 8.4.12 Other aspects 8.4.12.1 Thick/thin client 8.4.13 Users |
39 | 8.4.14 Application service provision 9 Conceptual architecture elaboration |
47 | 10 Taxonomy |
48 | 11 The communications architecture 12 Interoperability and the TARV-ROAM ‘facilities’ layer 12.1 Interoperability with other cooperative ITS systems |
51 | 12.2 TARV-ROAM ‘facilities layer’ architecture 12.2.1 General summary of TARV-ROAM provisions 12.2.2 Acknowledgements |
52 | 12.3 ROAM framework and architecture 12.3.1 ROAM overview |
53 | 12.3.2 ROAM OSGi® JAVA® environment |
55 | 12.3.3 ROAM application layers 12.3.4 ROAM ‘App’ library and data pantry 12.3.5 Providing Apps ‘on the fly’ 12.3.6 ROAM execution infrastructure |
56 | 12.3.7 TARV-ROAM actors and IVS component decomposition |
57 | 12.3.7.1 OEM_Environment 12.3.7.2 TARV-ROAM application service 12.3.7.3 TARV-ROAM certification authority (digital) |
58 | 12.3.7.4 TARV-ROAM approval authority (regulatory) 12.3.7.5 TARV-ROAM Communication subsystem/Wireless_Medium/Media 12.3.7.6 TARV_gateway 12.3.7.7 TARV-ROAM_host_platform 12.3.7.8 TARV-ROAM_host 12.3.7.9 TARV-ROAM HMC (Host Management Centre) operator 12.3.7.10 TARV-ROAM jurisdiction 12.3.7.11 TARV-ROAM native application 12.3.7.12 TARV-ROAM native system |
59 | 12.3.7.13 TARV-ROAM roadside system 12.3.7.14 TARV_router 12.3.7.15 TARV-ROAM service centre 12.3.7.16 TARV-ROAM service centre operator 12.3.7.17 TARV-ROAM service provider 12.3.7.18 TARV_unit/ TARV_IVS 12.3.7.19 TARV user 12.3.7.20 TARV-ROAM vehicle |
60 | 12.4 OSGi® (open services gateway initiative) 12.4.1 OSGi® framework 12.4.2 Layering |
61 | 12.4.3 Modules 12.4.4 JAR files 12.4.5 OSGi® services |
62 | 12.4.6 OSGi® deployment 12.4.7 OSGi® implementations |
63 | 12.4.8 OSGi® high level composite architecture 12.4.8.1 Security 12.4.8.2 Module layer 12.4.8.3 Life cycle layer 12.4.8.4 Service layer |
64 | 12.4.8.5 Framework service registry 12.4.8.6 OSGi® interactions 12.4.8.7 OSGi® services 12.4.8.8 OSGi® bundles |
65 | 12.4.8.8.1 Installed 12.4.8.8.2 Resolved |
66 | 12.4.8.8.3 Starting 12.4.8.8.4 Stopping 12.4.8.8.5 Active 12.4.8.8.6 Uninstalled 12.4.9 Importing and exporting packages 12.4.10 OSGi® system services |
67 | 12.4.11 Further information on OSGI® |
68 | 12.5 TARV-ROAM layered architecture and the role of OSGi® 12.5.1 TARV layered architecture |
69 | 12.5.2 High level elaboration of TARV-ROAM communication architecture |
70 | 12.5.3 TARV-ROAM service platform components 12.5.3.1 OSGi® application manager 12.5.3.2 OSGi® authentication broker 12.5.3.3 OSGi® authorization broker |
71 | 12.5.3.4 OSGi® data distribution service (DDS) client 12.5.3.5 OSGi® execution environment 12.5.3.6 OSGi® framework 12.5.3.7 OSGi® identity manager 12.5.3.8 OSGi® local data tree 12.5.3.9 OSGi® local dynamic map 12.5.3.10 OSGi® management agent 12.5.3.11 OSGi® secure communication 12.5.3.12 OSGi® secure module 12.5.3.13 OSGi® standard services 12.6 Host management centre (HMC) |
73 | 12.7 Local data tree (LDT) 12.7.1 General framework and architecture |
75 | 12.7.2 LDT actors |
76 | 12.7.3 LDT admin layer 12.7.4 LDT admin interface 12.7.5 LDT plug-ins 12.7.6 Data providers layer |
77 | 12.7.7 Corehandler 12.7.8 CellProvider 12.7.9 LDTNode 12.7.10 Access control 12.7.11 LDTAdmin 12.7.12 LDTNodeValueListener 12.7.13 LDTPlugin |
78 | 12.7.14 Device node command 12.7.15 Core handler 12.7.16 CellProvider 12.7.17 Cell listener 12.7.18 Cell 12.7.19 Data cell 12.7.20 Complex cell |
79 | 12.7.21 String descriptor 12.7.22 Measurement 12.7.23 StateDataCell 12.7.24 State 12.7.25 Remote method cell 12.8 TARV supported LDTs |
81 | 12.9 Distributed directory service (DDS) 12.10 Typical use case examples |
84 | 13 Privacy issues 13.1 General issues of privacy 13.2 Personal privacy |
85 | 13.3 Commercial privacy 13.4 Communications privacy 13.5 TARV-ROAM privacy |
86 | 14 Quality of service requirements 15 Test requirements |
87 | 16 Marking, labelling and packaging 17 Declaration of patents and intellectual property |