ISO 20078-2:2019 pdf download – Road vehicles – Extended vehicle (ExVe) web services
1 Scope
This document defines how to access Resources on a Web services interface of an Offering Party using the Hypertext Transfer Protocol Secure (HTTPS). For such an access, the Representational State Transfer (REST) architectural pattern is chosen as a common way to format Resource paths. Some specific extensions to this pattern are defined to allow for asynchronous Resource requests, such as,for example, forcing readouts of data from a connected vehicle.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content constitutes requirements of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.
ISO 20078-1:2019, Road vehicles — Extended vehicle (ExVe) web services — Part 1: Content
ISO 20078-3, Road vehicles — Extended vehicle (ExVe) web services — Part 3: Security
3 Terms, definitions and abbreviated terms
3.1 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO 20078-1 apply.
ISO and IEC maintain terminological databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https: //www .iso .org/obp
— IEC Electropedia: available at http: //www .electropedia .org/
3.2 Abbreviated terms
For the purposes of this document, the abbreviated terms given in ISO 20078-1 apply.
4 Representational State Transfer based Interface
4.1 General
The following defines the requirements on a Representational State Transfer (REST) [3] based web service interface using Hypertext Transfer Protocol Secure (HTTPS) [1][2][8] based on Transport Layer Security (TLS) to give the Accessing Party secure Access to Resources provided by the Offering Party.
Due to REQ_04_01_05 each request-response pair are handled independently from one another. Each client request by the Accessing Party contains all information required by the server of the Offering Party to successfully respond to the request, including a representation of the client state when necessary.
NOTE 1 This holds true even when the Resource is only available one time on a connected vehicle (e.g. “odometers”).”
The Resources, the Resource Groups or the Containers, and how to apply those on a specific presentation or application layer of the Accessing Party are described in ISO 20078-1. How an Accessing Party authenticates and how it is authorized for Access to Resources is described in ISO 20078-3.
There are two primary elements defining an URI; Entities and Resources (Table 2). Entities are the fundamental objects representing e.g. vehicles, ECUs, drivers and fleets. Resources are the actual data, aggregated information or functions associated with an entity and a specific use case.