1、 November 2011 Bereich InnovationPreisgruppe 7DIN Deutsches Institut fr Normung e. V. Jede Art der Vervielfltigung, auch auszugsweise, nur mit Genehmigung des DIN Deutsches Institut fr Normung e. V., Berlin, gestattet.ICS 35.240.60Zur Erstellung einer DIN SPEC knnen verschiedene Verfahrensweisen her
2、angezogen werden: Das vorliegende Dokument wurde nach den Verfahrensregeln einer PAS erstellt.!$uFo“1823576www.din.deDDIN SPEC 91286Elektromobilitt Schemata fr Identifikatoren fr E-Roaming Contract ID und EVSE ID; Text EnglischElectric mobility Schemes of identifiers for E-Roaming Contract ID and El
3、ectric Vehicle Supply Equipment ID; Text in EnglishAlleinverkauf der Spezifikationen durch Beuth Verlag GmbH, 10772 Berlin www.beuth.deGesamtumfang 9 SeitenDIN SPEC 91286:2011-11 Foreword This document aims to be the base for further international standardization of identification schemes in order t
4、o allow for a user-friendly and efficient transnational electric mobility experience. We thank all the participants of the “Fachgruppe Interoperabilitt” within the accompanying research of the research program “Information and Communication Technology for Electric Mobility” for their valuable input.
5、 Despite significant efforts to assure the correctness and precision of technical and non-technical descriptions, the preparing committee cannot take any warranty for the content of this document. By applying the content of this document, the user declares to be aware of the fact that the members of
6、 the preparing committee cannot be liable for any resulting damage or loss. The preparation of this document was coordinated by the following editors: Jonas Fluhr (FIR at RWTH Aachen e. V.) as chairman; Peter Laing (FIR at RWTH Aachen e. V.) as scientific advisor. The following persons (companies) w
7、ere part of the preparing committee: Nikolai Dahlem (BTC AG); Dr. Stefan Ferber (Bosch Software Innovations GmbH); Dr. Andreas Harth (Karlsruhe Institute of Technology); Dr. Jrg Heuer (Siemens AG); Markus Spiekermann (Move About GmbH); Stephan Voit (RWE Effizienz GmbH); Andreas Wagner (Karlsruhe Ins
8、titute of Technology). Introduction A number of research projects with focus on information and communication technology (ICT) for electric mobility revealed the need for inter-organizationally standardized identifiers of selected entities around an electrically motorized individual traffic (E-Mobil
9、ity). In particular, the charging and discharging of Electric Vehicles (EV) at an Electric Vehicle Supply Equipment (EVSE) within an existing contract requires a fundamental set of identifiers that are guaranteed to be unique beyond organizational borders. Considering two main communication scenario
10、s in relation with EVSE (see A.1), the unique identification of the following entities is required or useful for efficient inter-organizational E-Roaming processes: E-Mobility Operator, EVSE Operator, Contract and EVSE. In order to guarantee the uniqueness of these identifiers, a central issuing aut
11、hority and coordinated assigning process is needed. However, these issues are not addressed in this document. 2 DIN SPEC 91286:2011-11 1 Scope This document defines schemes that allow deriving identifiers for objects in the area of E-Mobility. The schemes can be used at human machine interfaces as w
12、ell as for pure machine-to-machine communication. The schemes aim to be used within communication as defined by standards such as the currently developed ISO/IEC 15118. Two schemes are defined: Identifiers derived from the first scheme identify the contract between an E-Mobility Operator and its cus
13、tomer. Identifiers derived from the second scheme identify an EVSE of an EVSE Operator. 2 Normative references The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition o
14、f the referenced document (including any amendments) applies. DIN EN ISO 3166-1:2007: Codes for the representation of names of countries and their subdivisions Part 1: Country codes (Alpha-2-Code) ITU-T E.164 (11/2010), Series E: Overall Network Operation, Telephone Service, Service Operation and Hu
15、man Factors : International operation Numbering plan of the international telephone service ISO/IEC 10646-1:2000, Universal Multiple-Octet Coded Character Set (UCS) Part 1: Architecture and Basic Multilingual Plane, Annex D (UTF-8), zurckgezogen! Nachfolger ISO/IEC 10646:2011 ISO/IEC 15118-1, Ed. 1.
16、0, 2. Committee Draft: Road vehicles Vehicle to grid communication interface Part 1: General information and use-case definition ISOC RFC 2141:1997: URN Syntax ISOC RFC 3406:2002: Uniform Resource Names (URN) Namespace Definition Mechanisms ISOC RFC 3629:2003: UTF-8, a transformation format of ISO 1
17、0646 ISOC RFC 3986:2005: Uniform Resource Identifier (URI): Generic Syntax ISOC RFC 5234:2008: Augmented BNF for Syntax Specifications: ABNF 3 Terms and definitions For the purposes of this document, the terms and definitions given in ISO/IEC 15118-1, 2. Committee Draft and the following apply. 3.1
18、contract ID (EVCOID) unique identifier of a contract that is used to enable charging and related services (incl. billing) 3.2 E-Roaming charging or discharging of Electric Vehicles (EV) at an Electric Vehicle Supply Equipment (EVSE) via an existing contract between an E-Mobility Operator that is not
19、 the EVSE Operator of this EVSE 3.3 E-Mobility electrically propelled road traffic 3 DIN SPEC 91286:2011-11 3.4 E-Mobility Operator legal entity that the customer has a contract with for all services related to the EV in front of EVSE NOTE The customer can also be an EV(-fleet) operator that has own
20、 end customers. Services other than energy supply are possible. 3.5 Electric Vehicle (EV) any vehicle propelled by an electric motor drawing current from a rechargeable storage battery or from other portable energy storage devices (rechargeable, using energy from a source off the vehicle such as a r
21、esidential or public electric service), which is manufactured primarily for use on public streets, roads or highways 3.6 Electric Vehicle Supply Equipment (EVSE) conductors, including the phase(s), neutral and protective earth conductors, the EV couplers, attached plugs, and all other accessories, d
22、evices, power outlets or apparatuses installed specifically for the purpose of delivering energy from the premises wiring to the EV and allowing communication between them as necessary NOTE 1 For this purpose the EVSE may also include communication to secondary actors. NOTE 2 For systems with multip
23、le charge outlets, communication described in this standard may apply for each charge-outlet 3.7 Electric Vehicle Supply Equipment ID (EVSEID) unique identifier of an EVSE, consisting at least of Spot Operator ID and Power Outlet ID 3.8 EVSE Operator operates an EVSE; synonym to “Spot Operator” 3.9
24、Identifier (ID) a sequence of characters embodying the information required to distinguish what is being identified from all other things within its scope of identification (see RFC 3986) 3.10 Power Outlet ID unique identifier of a power outlet to the vehicle 3.11 Provider ID unique identifier of an
25、 E-Mobility Operator 3.12 Spot Operator ID unique identifier of an EVSE operator 4 Abbreviations AAA Authentication, Authorization and Accounting ABNF Augmented Backus-Naur Form E-Mobility Electric Mobility 4 DIN SPEC 91286:2011-11 EV Electric Vehicle EVSE Electric Vehicle Supply Equipment EVCOID El
26、ectric Vehicle Contract Identifier EVSEID Electric Vehicle Supply Equipment Identifier GLN Global Location Number HTTP Hypertext Transfer Protocol ICD International Code Designator ICT Information and Communication Technology ID Identifier UTF UCS (Universal Character Set / Unicode) Transformation F
27、ormat URN Uniform Resource Name RDF Resource Description Framework 5 Specifications of identifiers 5.1 Recommendations The identifiers could be persistent during the life of the identified entity. NOTE Since these IDs could not change, tracking and profiling of charging habits is possible for interm
28、ediate systems. Therefore, confidential information (e. g. personal user data) linked to the identifiers should never be communicated together with the identifier. The choice of identifiers by E-Mobility Operator or EVSE Operator must not directly reveal confidential information about Contracts and
29、EVSE to third parties. Through a simple mapping, organizations can continue to use already existing internal schemes of identifiers for the contracts of customers or EVSE. 5.2 EVCOID Specification 5.2.1 EVCOID Syntax The EVCOID must match the following structure (the notation corresponds to the augm
30、ented Backus-Naur Form (ABNF) as defined in RFC 5234): = with 2 ALPHA ; two character country code according to DIN EN ISO-3166-1 (Alpha-2-Code) = 3 (ALPHA / DIGIT) ; three alphanumeric characters = 6 (ALPHA / DIGIT) ; six alphanumeric characters 5 DIN SPEC 91286:2011-11 = 1 DIGIT ; see 5.2.3 for it
31、s computation ALPHA = %x41-5A / %x61-7A ; according to RFC 5234 (7-Bit ASCII) DIGIT = %x30-39 ; according to RFC 5234 (7-Bit ASCII) = *1 ( “*” / “-” ) ; optional separator An example for a valid EVCOID therefore is “DE8AA123A563”. 5.2.2 EVCOID Semantics The must be interpreted case insensitive, i.e.
32、 “DE8AA123A563” is exactly the same ID as “De8aa123A563”. A star (“*“) or hyphen (“-“) can be used between the elements , , and in communication with users of EV or EVSE to allow for better reading, spelling and typing. An example for such an illustration is “DE*8AA*123A56*3”. If the illustration wi
33、th stars is chosen, stars must be set at all three (3) spaces. Each has a fixed length of twelve characters excluding the optional stars or fifteen characters including the optional separators. While the must be assigned by a central issuing authority, each provider with an assigned can chose the wi
34、thin the above mentioned rules freely. 5.2.3 Calculation of the check digit A unique value is determined for each of the first 11 character of the . While the numbers (DIGIT) keep their value, the letters (ALPHA) are mapped to values from A=10 to Z=35. NOTE Intermediate stars are not considered. The
35、 mapping is case insensitive, i.e. “D” as well as “d” maps to the value 13. In the resulting , each digit is multiplied with the weight 2 (“2 to the power of ”) where represents the position of the digit in the and starts with number zero. The resulting products are summed up to . NOTE There are at
36、least 11 (if only numbers are used in the ) and at most 22 (if only letters are used in the ) resulting products. Finally, is taken “modulo 11”. The result of this modulo-computation is a number between “0” and “10”. The numbers between “0” and “9” are taken as , the for “10” is the letter “X”. NOTE
37、 Check digits based on the modulo-11 principle are able to identify single typing errors as well as singled transposed characters. EXAMPLE Mapping the 11 characters “DEA2ZG8L16P” to values results in the “131410235168211625” and consequently to the “1040699”. The modulo-11 computation results to the
38、 “0” and the “DEA2ZG8L16P0”. 5.3 EVSEID Specification 5.3.1 EVSEID Syntax The EVSEID must match the following structure (the notation corresponds to the augmented Backus-Naur Form (ABNF) as defined in RFC 5234): 6 DIN SPEC 91286:2011-11 = “*” “*” with = 1 * 3 DIGIT ; up to three digits according to
39、country code for geographic areas in ITU-T E.164:11/2010 = 3 * 6 DIGIT ; between three and six digits = 1 * 32 (1 * DIGIT) “*”) ; sequence of digits and stars DIGIT = %x30-39 ; according to RFC 4234(7-Bit ASCII) EXAMPLE An example for a valid EVSEID is “+49*123*456*789” with “+49” indicating Germany
40、, “123” representing a particular Spot Operator and “456*789” representing one of its power outlets. NOTE In contrast to the EVCOID, no check digit is specified for the EVSEID in this document (see A.2). 5.3.2 EVSEID Semantics Each has a variable length with at least five characters (one digit , thr
41、ee digits , one digit ) and at most forty-one characters (three digits , six digits , thirty-two digits ). While the must be assigned by a central issuing authority, each operator with an assigned can chose the within the above mentioned rules freely. 5.4 Usage of Identifiers in IT Systems The IT sy
42、stems handling the specified identifiers should be able to cope with identifiers with a length of up to 255 characters, since future enhancements of this standard may require this. The encoding of the identifiers in IT systems should be UTF-8 (see ISO/IEC 10646-1:2000, RFC 3629). NOTE UTF-8 allows f
43、or true international interoperability in case of enhancements of the defined identifiers for non-latin alphabet. 7 DIN SPEC 91286:2011-11 8 Annex A (informative) Supplementary Explanation A.1 Need for unique identification Currently, two communication scenarios are targeted in context with authenti
44、cation, authorization and accounting (AAA) of EV at EVSE (see Figure A.1). Figure A.1 Communication scenarios with possible steps of data exchange for AAA In scenario A, the EV User (or its EV on behalf of him) passes all information needed for AAA through the EVSE (A1) to the EVSE Operator (A2). Th
45、e EVSE Operator forwards the information to the E-Mobility Operator and requests AAA for the EV User (A3). If the response (A4) is positive, the EVSE Operator unlocks the EVSE for charging (A5). In scenario B, the EV User directly connects to the E-Mobility Operator (B1) and requests AAA for a parti
46、cular EVSE. If successful, the E-Mobility Operator requests the EVSE Operator (B2) to unlock remotely the particular EVSE for charging (B3). In relation to these communication scenarios, Table A.1 reveals that identifying the E-Mobility Operator and EVSE Operator inter-organizationally (each in one
47、of communication scenarios) is indispensable. Table A.1 Need for uniqueness of identifiers Identifiers Scenario A Scenario B E-Mobility Operator Required EVSE Operator needs to know which E-Mobility Operator to contact AAA Optional E-Mobility Operator could always be identified by the EVSE Operator
48、due to AAA-Request EV User (via Contract) Optional Proprietary ID for EV / User could always be identified by the issuing E-Mobility Operator Optional Proprietary ID for EV / User could always be identified by the issuing E-Mobility Operator EVSE Optional Proprietary ID for EVSE could always be iden
49、tified by the issuing EVSE Operator Optional Proprietary ID for EVSE could always be identified by the issuing EVSE Operator EVSE Operator Optional EVSE Operator could always be identified by the E-Mobility Operator due to AAA-Request Required E-Mobility Operator needs to know which EVSE Operator to contact for AAA DIN SPEC 91286:2011-11 9 Nevertheless, the inter-organizationally standardized identification of contracts between an EV User and its E-Mobility Operator or of the EVSE of an EVSE Operators is desirable due to efficiency and end customer us
