This is the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

Identifier
Full qualified VSS Path: Vehicle.Driver.Identifier
Description: Identifier attributes based on OAuth 2.0.
flowchart LR Vehicle-->Driver Driver-->Identifier

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.Driver.Identifier

Signal Information

The vehicle signal Vehicle.Driver.Identifier is a Branch.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Driver.Identifier is 89705397069c5ec58d607318f2ff0ea8

Children

This vehicle signal is a branch or structure and thus has sub-pages:

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by COVESA to define a syntax and a catalog for vehicle signals. The source code and releases can be found in the VSS github repository.

1 - Issuer
Full qualified VSS Path: Vehicle.Driver.Identifier.Issuer
Description: Unique Issuer for the authentication of the occupant. E.g. https://accounts.funcorp.com.
flowchart LR Vehicle-->Driver Driver-->Identifier Identifier-->Issuer

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Driver.Identifier.Issuer
[get]  OK
Vehicle.Driver.Identifier.Issuer: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Driver.Identifier.Issuer Foo
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.Driver.Identifier.Issuer

Data Type & Unit
Path Vehicle.Driver.Identifier.Issuer VSS: Addressing nodes
Data type string VSS: Datatypes

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Driver.Identifier.Issuer is a Sensor.

The vehicle signal Vehicle.Driver.Identifier.Issuer is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Driver.Identifier.Issuer is ee7988d26d7156d2a030ecc506ea97e7

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by COVESA to define a syntax and a catalog for vehicle signals. The source code and releases can be found in the VSS github repository.

Supported datatypes

The following is a list of VSS supported built-in datatypes:

Name Type Min Max
uint8 unsigned 8-bit integer 0 255
int8 signed 8-bit integer -128 127
uint16 unsigned 16-bit integer 0 65535
int16 signed 16-bit integer -32768 32767
uint32 unsigned 32-bit integer 0 4294967295
int32 signed 32-bit integer -2147483648 2147483647
uint64 unsigned 64-bit integer 0 2^64 - 1
int64 signed 64-bit integer -2^63 2^63 - 1
boolean boolean value 0/false 1/true
float floating point number -3.4e -38 3.4e 38
double double precision floating point number -1.7e -300 1.7e 300
string character string n/a n/a

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

2 - Subject
Full qualified VSS Path: Vehicle.Driver.Identifier.Subject
Description: Subject for the authentication of the occupant. E.g. UserID 7331677.
flowchart LR Vehicle-->Driver Driver-->Identifier Identifier-->Subject

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Driver.Identifier.Subject
[get]  OK
Vehicle.Driver.Identifier.Subject: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Driver.Identifier.Subject Foo
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.Driver.Identifier.Subject

Data Type & Unit
Path Vehicle.Driver.Identifier.Subject VSS: Addressing nodes
Data type string VSS: Datatypes

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Driver.Identifier.Subject is a Sensor.

The vehicle signal Vehicle.Driver.Identifier.Subject is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Driver.Identifier.Subject is b41ec688af265f10824bc9635989ac55

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by COVESA to define a syntax and a catalog for vehicle signals. The source code and releases can be found in the VSS github repository.

Supported datatypes

The following is a list of VSS supported built-in datatypes:

Name Type Min Max
uint8 unsigned 8-bit integer 0 255
int8 signed 8-bit integer -128 127
uint16 unsigned 16-bit integer 0 65535
int16 signed 16-bit integer -32768 32767
uint32 unsigned 32-bit integer 0 4294967295
int32 signed 32-bit integer -2147483648 2147483647
uint64 unsigned 64-bit integer 0 2^64 - 1
int64 signed 64-bit integer -2^63 2^63 - 1
boolean boolean value 0/false 1/true
float floating point number -3.4e -38 3.4e 38
double double precision floating point number -1.7e -300 1.7e 300
string character string n/a n/a

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.