{"id":230868,"date":"2024-10-19T15:01:36","date_gmt":"2024-10-19T15:01:36","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-iso-15638-52013\/"},"modified":"2024-10-25T09:18:24","modified_gmt":"2024-10-25T09:18:24","slug":"bs-iso-15638-52013","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-iso-15638-52013\/","title":{"rendered":"BS ISO 15638-5:2013"},"content":{"rendered":"
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
13<\/td>\n | 1 Scope 2 Conformance <\/td>\n<\/tr>\n | ||||||
14<\/td>\n | 3 Normative references <\/td>\n<\/tr>\n | ||||||
15<\/td>\n | 4 Terms and definitions <\/td>\n<\/tr>\n | ||||||
17<\/td>\n | 5 Symbols (and abbreviated terms) <\/td>\n<\/tr>\n | ||||||
18<\/td>\n | 6 General overview and framework 6.1 General overview 6.1.1 Context 6.1.1.1 Framework and architecture <\/td>\n<\/tr>\n | ||||||
22<\/td>\n | 6.1.1.2 Data creation process and architecture <\/td>\n<\/tr>\n | ||||||
23<\/td>\n | 6.1.1.3 Commands 6.1.1.4 IVS requirements 6.1.2 ROAM 6.1.2.1 ROAM framework and architecture <\/td>\n<\/tr>\n | ||||||
29<\/td>\n | 6.1.2.2 TARV supported LDTs <\/td>\n<\/tr>\n | ||||||
30<\/td>\n | 7 System requirements 7.1 Communications requirements <\/td>\n<\/tr>\n | ||||||
31<\/td>\n | 7.4 7Host management centre (HMC) requirements 8 Generic vehicle data requirements 8.1 Data provision 8.1.1 Location of on-board data 8.1.2 Naming of \u2018Apps\u2019 <\/td>\n<\/tr>\n | ||||||
32<\/td>\n | 8.1.3 Local data trees 8.1.4 C-ITS LDT 8.1.5 TARV LDT <\/td>\n<\/tr>\n | ||||||
33<\/td>\n | 8.1.6 Recent data archive 8.2 Commands for vehicle data 8.2.1 GET TARV LDT data <\/td>\n<\/tr>\n | ||||||
34<\/td>\n | 8.2.2 GET C-ITS LDT data 8.2.3 CREATE core application data <\/td>\n<\/tr>\n | ||||||
36<\/td>\n | 8.2.4 GET core application data 8.2.5 GET Archive 8.3 Presentation of the \u2018basic vehicle data\u2019 concept 8.3.1 Data format version <\/td>\n<\/tr>\n | ||||||
37<\/td>\n | 8.3.2 Message identifier 8.3.3 Prime service provider identifier 8.3.4 Application service provider identifier <\/td>\n<\/tr>\n | ||||||
38<\/td>\n | 8.3.5 Session control data <\/td>\n<\/tr>\n | ||||||
39<\/td>\n | 8.3.6 Vehicle unique identifier 8.3.7 Vehicle class identification 8.3.8 VIN number 8.3.9 Propulsion storage type <\/td>\n<\/tr>\n | ||||||
40<\/td>\n | 8.3.10 Time and timestamp (UTC sec) 8.3.11 Location 8.3.11.1 General <\/td>\n<\/tr>\n | ||||||
41<\/td>\n | 8.3.11.2 Position latitude 8.3.11.3 Position longitude <\/td>\n<\/tr>\n | ||||||
42<\/td>\n | 8.3.11.4 Position altitude 8.3.11.5 Number of satellites present 8.3.11.6 Location\/direction degree of trust 8.3.12 Error estimation (covariance matrix) <\/td>\n<\/tr>\n | ||||||
43<\/td>\n | 8.3.13 Direction of travel <\/td>\n<\/tr>\n | ||||||
44<\/td>\n | 8.3.14 Ignition status 8.3.15 Other movement sensors 8.3.16 IVS identification <\/td>\n<\/tr>\n | ||||||
45<\/td>\n | 8.3.16.1 ISO 14816 CS1 definition (IVS identification data concept) 8.3.16.2 Country code definition 8.3.16.3 Issuer identifier definition 8.3.16.4 Service number definition 8.3.17 Manufacturer identification <\/td>\n<\/tr>\n | ||||||
46<\/td>\n | 8.3.17.1 CS2 definition (manufacturer identification data concept) 8.3.17.2 Manufacturer Identifier definition 8.3.17.3 Service number definition 8.3.18 Driver(s) identification 8.3.18.1 Jurisdiction identification <\/td>\n<\/tr>\n | ||||||
47<\/td>\n | 8.3.18.2 User authorisation 8.3.19 Trailer identification 8.3.20 Load data 8.4 Organisation of the TARV LDT <\/td>\n<\/tr>\n | ||||||
49<\/td>\n | 9 Additional data provision options for \u2018core application data\u2019 and regulated applications 9.1 General <\/td>\n<\/tr>\n | ||||||
51<\/td>\n | 9.2 Additional data options for \u2018core application data\u2019 9.2.1 Accelerometer data <\/td>\n<\/tr>\n | ||||||
52<\/td>\n | 9.2.2 Gyroscope data 9.2.3 Camera\/video data 9.2.3.1 Still camera data 9.2.3.2 Video data 9.2.4 Vehicle speed data <\/td>\n<\/tr>\n | ||||||
53<\/td>\n | 9.2.5 Alarm status data and records <\/td>\n<\/tr>\n | ||||||
54<\/td>\n | 9.3 Distributed directory service (DDS) requirements 10 Test requirements <\/td>\n<\/tr>\n | ||||||
55<\/td>\n | 11 Marking, labelling and packaging <\/td>\n<\/tr>\n | ||||||
56<\/td>\n | 12 Declaration of patents and intellectual property <\/td>\n<\/tr>\n | ||||||
58<\/td>\n | 12.1.1 Issuer: 12.1.2 Issuer register: 12.1.3 General 12.1.4 Responsibilities <\/td>\n<\/tr>\n | ||||||
66<\/td>\n | B.2 CVIS 3.1.2\u00a0Application programming interface <\/td>\n<\/tr>\n | ||||||
97<\/td>\n | CTP 2.1.1 Instigated Core Data using 2G <\/td>\n<\/tr>\n | ||||||
99<\/td>\n | CTP 2.1.2 Interrogated Core Data using 2G <\/td>\n<\/tr>\n | ||||||
101<\/td>\n | CTP 2.1.3 Interrogated Core Data using 5.9GHz and responding using 2G or 3G <\/td>\n<\/tr>\n | ||||||
103<\/td>\n | CTP 2.2.1 Instigated Core Data using 3G <\/td>\n<\/tr>\n | ||||||
105<\/td>\n | CTP 2.2.2 Interrogated at 5.9 GHz and send of Core Data using 3G <\/td>\n<\/tr>\n | ||||||
107<\/td>\n | CTP 2.3.1 Instigated Core Data using 802.11p (WAVE) 5.9 GHz <\/td>\n<\/tr>\n | ||||||
109<\/td>\n | CTP 2.3.2 Interrogated Core Data using 802.11p (WAVE) 5.9 GHz <\/td>\n<\/tr>\n | ||||||
111<\/td>\n | CTP 2.4.1 Instigated Core Data using Mesh WiFi <\/td>\n<\/tr>\n | ||||||
113<\/td>\n | CTP 2.4.2 Interrogated Core Data using Mesh WiFi <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Intelligent transport systems. Framework for collaborative Telematics Applications for Regulated commercial freight Vehicles (TARV) – Generic vehicle information<\/b><\/p>\n |