ISO TR 20078-4-2021 pdf free download – Road vehicles — Extended vehicle (ExVe) web services — Part 4: Control.
This document describes the processes of an offering party’s implementation to provide (1So 20078-2) access-controlled (ISo 20078-3) resources (1so 20078-1) to accessing parties. The processes aresummarized as: registration of different stakeholder as well as granting,denying and revoking ofaccess to resources.Those processes are held as examples of combining ISo 20078-1,ISO 20078-2 andISO 20078-3 and can vary depending on the actual implementation of the offering party.
2Normative references
The following documents are referred to in the text in such a way that some or all of their contentconstitutes requirements of this document. For dated references, only the edition cited applies.Forundated references, the latest edition of the referenced document (including any amendments) applies.ISO 20078-1,Road vehicles —Extended vehicle (ExVe) web services — Part 1:Content and definitions
3Terms and definitions
For the purposes of this document, the terms and definitions given in ISo 20078-1 apply.
IS0 and IEC maintain terminology databases for use in standardization at the following addresses:- ISo online browsing platform: available at https://www.iso.org/obp
―IEC Electropedia: available at https://www.electropedia.org/
4Roles
4.1 Resource owner
4.1.1 Resources
The resource owner is in control of the access to its resources. To control access, the resource owneruses the processes: granting, denying, ignoring and revoking.
Figure 2 displays an example for one accessing party.The accessing party or the offering party definescontainers, each identified by a unique container id(CID), to access resources of the offering party.The resource owner can individually grant, deny or revoke — at any time — access (1so 20078-3) toresources of defined containers (1so 2o078-1) in relation to a one or more vehicle identifiers (VINs)for not anonymized resources. Such decisions made by the resource owner are collectively called therequest permission processes. Possible states or outcomes of these processes are the following.
– Granted: a certain container is defined by the accessing or the offering party.The resource owner
grants access to the container (and if required in combination with a vehicle identifier) for theaccessing party.Through this grant process the resource owner verifies that both the resources, andthe purpose of data processing of the container are presented by the offering party; see Figure 15and]or Figures 16 and 17.
Denied: a certain container is defined by the accessing or the offering party.The resource ownerdenies the accessto the container for the accessing party.Because of this action, the resource ownerdoes not approve the accessto the resources and/or the purpose of data processing of the containerthat are presented by the offering party; see Figure 18.
Pending/ignored: a certain container is defined by the accessing party or the offering party andselected for a grant request. After starting the request, the resource owner does not continue toeither grant orto deny the request.The request stays pending as long as it is ignored by the resourceowner. If a pre-defined time passes, and the request has been ignored, it is denied by the offeringparty; see Figure 19.
Revoked: a certain container is defined by the accessing party or the offering party and was grantedby the resource owner.After a certain time, the resource owner revokes the access to resources ofthe container for the accessing party.This immediately denies any further access to resources forthe accessing party; see Figure 20.ISO TR 20078-4 pdf download