ISO 20078-2:2019

ISO 20078-2:2019 pdf free.Road vehicles – Extended vehicle (ExVe) web services -Access.
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
— IEC Electropedia: available at
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)[] based web service interface using Hypertext Transfer Protocol Secure (HTTPS)[1i[2iLI] based on Transport Layer Security (TLS) to give the Accessing Party secure Access to Resources provided by the Offering Party.
The REST based web services interface implementation shall use the Hypertext Transfer Protocol Secure (HTTPS) as transport protocol with Transport Layer Security (TLS]. .
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.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.EXAMPLE Fuel level could be an example of a single data item Resource and vehicle position an aggregate consisting of several data items (e.g. latitude, longitude, sample time), lock and un-lock the vehicle a functionality. REQ_ 04_ 02_ 06 The Offering Party should have the possibility to extend Resources, but shall not be able to reduce Resources. Thus by REQ_ 04 02. _06 it is not possible to remove data items from a Resource, other than through an update of the underlying use case specification. It is however possible to add data items to a Resource (i.e. versioning).NOTE 1
If all Resources in a web service are granted, full Access to the web service is given. NOTE 2
If no Resource in a web service is granted, no Access to the web service is given. NOTE 3
If a subset of the Resources in a web service is granted, partial Access to the web service is given;
there might be cases where no Access can be given, due to how the web service is structured.
REQ_ 04_ 06_ 04 The web service specification shall not be changed in any way, due to granting, denying, ignoring, or revoking Access of included Resources. NOTE 4 The web service specification handles that only a subset of the included Resources might be granted.To avoid that clients put excessive load on the server side interface, rate limitation could be imposed on server requests. When rate limitations are applied, a number of HTTP headers are used in order to allow a client to be informed about the current rate limitations for the service. Rate limits are applied to intervals, in each interval there is a limited amount of requests.ISO 20078-2 pdf download.

Leave a Reply

Your email address will not be published. Required fields are marked *