IEEE 1609.11 2011
$44.42
IEEE Standard for Wireless Access in Vehicular Environments (WAVE)– Over-the-Air Electronic Payment Data Exchange Protocol for Intelligent Transportation Systems (ITS)
Published By | Publication Date | Number of Pages |
IEEE | 2011 | 62 |
New IEEE Standard – Active. This standard specifies the electronic payment service layer and profile for Payment and Identity authentication, and Payment Data transfer for Dedicated Short Range Communication (DSRC) based applications in Wireless Access in Vehicular Environments. This standard defines a basic level of technical interoperability (vehicle-to-roadside) for electronic payment equipment, i.e., onboard unit (OBU) and roadside unit (RSU) using WAVE. It does not provide a full solution for interoperability, and it does not define other parts of the electronic payment system, other services, other technologies and non-technical elements of payment interoperability. This standard is not intended to define technology and processes to activate and store data into the OBU (personalization), nor the applications using the payment service.
PDF Catalog
PDF Pages | PDF Title |
---|---|
1 | IEEE Std 1609.11-2010 Front Cover |
3 | Title page |
6 | Introduction Notice to users Laws and regulations Copyrights Updating of IEEE documents Errata |
7 | Interpretations Patents Participants |
9 | Contents |
10 | Important Notice 1. Overview 1.1 Scope |
11 | 1.2 Purpose 1.3 Document organization 2. Normative references |
12 | 3. Definitions, acronyms, and abbreviations 3.1 Definitions |
13 | 3.2 Acronyms and abbreviations |
14 | 4. General description |
16 | 5. Payment Service overview 5.1 Payment Service functions |
17 | 5.2 MIB maintenance 6. Types of systems using EPS 6.1 Modes of EPS information exchange 6.1.1 Introduction 6.1.2 Direct EPS communication mode |
18 | 6.1.3 Indirect EPS communication mode |
19 | 6.2 Payer and payee approval types 6.2.1 Introduction 6.2.2 Payer response approval types |
20 | 6.2.3 Payee action approval types 6.2.4 Payer action approval types |
22 | Annex A (normative) Profile for Electronic Fee Collection (EFC) systems per ISO 14906 and ISO 15628 A.1 Introduction A.2 General description |
24 | A.3 WIAL and WAVE services A.3.1 Introduction A.3.2 GET_SECURE |
26 | A.3.3 SET_SECURE |
28 | A.3.4 Payee WIAL |
29 | A.3.5 Payer WIAL |
30 | A.4 Interfaces A.4.1 Overview |
32 | A.4.2 General Payment Service primitives A.4.2.1 Overview A.4.2.2 PS-Encrypt.request A.4.2.2.1 Function A.4.2.2.2 Semantics of the service primitive |
33 | A.4.2.2.3 When generated A.4.2.2.4 Effect of receipt A.4.2.3 PS-Encrypt.confirm A.4.2.3.1 Function |
34 | A.4.2.3.2 Semantics of the service primitive A.4.2.3.3 When generated A.4.2.3.4 Effect of receipt A.4.2.4 PS-Decrypt.request A.4.2.4.1 Function A.4.2.4.2 Semantics of the service primitive |
35 | A.4.2.4.3 When generated A.4.2.4.4 Effect of receipt A.4.2.5 PS-Decrypt.confirm A.4.2.5.1 Function A.4.2.5.2 Semantics of the service primitive |
36 | A.4.2.5.3 When generated A.4.2.5.4 Effect of receipt A.4.2.6 PS-CalculateMessageAuthenticationCode.request A.4.2.6.1 Function A.4.2.6.2 Semantics of the service primitive |
37 | A.4.2.6.3 When generated A.4.2.6.4 Effect of receipt A.4.2.7 PS-CalculateMessageAuthenticationCode.confirm A.4.2.7.1 Function A.4.2.7.2 Semantics of the service primitive |
38 | A.4.2.7.3 When generated A.4.2.7.4 Effect of receipt A.4.2.8 PS-StoreKey.request A.4.2.8.1 Function A.4.2.8.2 Semantics of the service primitive |
39 | A.4.2.8.3 When generated A.4.2.8.4 Effect of receipt A.4.2.9 PS-StoreKey.confirm A.4.2.9.1 Function A.4.2.9.2 Semantics of the service primitive A.4.2.9.3 When generated |
40 | A.4.2.9.4 Effect of receipt A.4.2.10 PS-RetrieveKeyMaterial.request A.4.2.10.1 Function A.4.2.10.2 Semantics of the service primitive A.4.2.10.3 When generated A.4.2.10.4 Effect of receipt A.4.2.11 PS-RetrieveKeyMaterial.confirm A.4.2.11.1 Function |
41 | A.4.2.11.2 Semantics of the service primitive A.4.2.11.3 When generated A.4.2.11.4 Effect of receipt A.4.2.12 PS-GenerateKeyMaterial.request A.4.2.12.1 Function A.4.2.12.2 Semantics of the service primitive |
42 | A.4.2.12.3 When generated A.4.2.12.4 Effect of receipt A.4.2.13 PS-GenerateKeyMaterial.confirm A.4.2.13.1 Function A.4.2.13.2 Semantics of the service primitive |
43 | A.4.2.13.3 When generated A.4.2.13.4 Effect of receipt A.4.3 Payer Payment Service primitives A.4.3.1 PAYERPS-GetPaymentData.request A.4.3.1.1 Function A.4.3.1.2 Semantics of the service primitive A.4.3.1.3 When generated A.4.3.1.4 Effect of receipt A.4.3.2 PAYERPS-GetPaymentData.confirm A.4.3.2.1 Function |
44 | A.4.3.2.2 Semantics of the service primitive A.4.3.2.3 When generated A.4.3.2.4 Effect of receipt A.4.3.3 PAYERPS-SaveReceipts.request A.4.3.3.1 Function |
45 | A.4.3.3.2 Semantics of the service primitive A.4.3.3.3 When generated A.4.3.3.4 Effect of receipt A.4.3.4 PAYERPS-SaveReceipts.confirm A.4.3.4.1 Function A.4.3.4.2 Semantics of the service primitive |
46 | A.4.3.4.3 When generated A.4.3.4.4 Effect of receipt A.4.4 Payee Payment Service primitives A.4.4.1 PAYEEPS-MakePayment.request A.4.4.1.1 Function A.4.4.1.2 Semantics of the service primitive |
47 | A.4.4.1.3 When generated A.4.4.1.4 Effect of receipt A.4.4.2 PAYEEPS-MakePayment.confirm A.4.4.2.1 Function A.4.4.2.2 Semantics of the service primitive |
48 | A.4.4.2.3 When generated A.4.4.2.4 Effect of receipt A.5 EFC EPS transactions |
50 | A.6 Keying material A.6.1 Approved algorithms A.6.1.1 Encryption |
51 | A.6.1.2 Authentication A.6.1.3 Key derivation A.6.2 Payer A.6.3 Payee |
53 | Annex B (informative) Examples of Electronic Fee Collection (EFC) systems per ISO 14906 and ISO 15628 B.1 Introduction B.2 Example EFC transaction |
57 | B.3 Example of an EFC system that uses small zones and un-augmented location determination, with high-speed payers B.3.1 Introduction B.3.2 Payer and payee approval types B.3.3 Payee WIAL B.3.4 Payer WIAL |
58 | B.3.5 EPS EFC transaction guidelines B.3.6 Payer application data |
59 | B.3.7 Example Protocol Implementation Conformance Statement (PICS) proforma |
61 | Annex C (normative) Protocol Implementation Conformance Statement (PICS) proforma |