Tiêu chuẩn iso ts 21219 25 2017

detailed hargingPark oca-tion Detailed hargingPark ocation 0.1 Detailed g olocation referenc -ing information for charging park entry, charging park e it or single charging stations.. Ta

Application identification

In TPEG specifications, the term "application" refers to specific subsets of the TPEG structure, each defining a limited vocabulary for particular message types, such as parking or road traffic information Each TPEG application is assigned a unique identifier known as the Application IDentification (AID), which is established whenever a new application is created and documented in ISO/TS 21219-1.

The application identification number in the TPEG2-SNI application, as defined by ISO/TS 21219-9, is essential for processing TPEG content and ensures that information is directed to the correct application decoder.

Version number signalling

Version numbering is used to track the separate versions of an application through its development and deployment The differences between these versions can have an impact on client devices.

The version numbering principle is defined in ISO/TS 21219-1.

Table 1 shows the current version numbers for signalling EMI within the SNI application ISO/TS 21219-9.

Table 1 — Current version numbers for signalling of EMI major version number 1 minor version number 0

Ordered components

TPEG2-EMI mandates a specific sequence for its components, starting with the Message Management Container (MMC) as depicted in Figure 1 If the message is a cancellation, the MMC is the sole component In other cases, it is succeeded by one or more Application Data Container components that contain the relevant application-specific information.

Figure 1 — Composition of TPEG messages

Extension

The fixed component order does not hinder the expansion of EMI, allowing future applications to add or replace components while maintaining backward compatibility An EMI decoder is designed to identify and bypass any unknown components.

TPEG Service Component Frame

EMI makes use of the “Service Component Frame with dataCRC and messageCount” according to ISO/TS 21219-5 (TPEG2-SFW).

Overview

In Clause 6, the main structure of EMI and its capabilities are explained.

The EMI design differentiates between static information, which typically has a low refresh rate, and dynamic information, characterized by a high refresh rate.

EMI structuring considerations

Information aggregation level: Charging parks, charging stations,

EMI must equip end users with essential information to locate suitable and available charging points for their electric vehicles From the user's perspective, it is adequate to receive details about the charging station's physical location that aligns with their needs, rather than specifics about which individual charging point is available at that station.

EMI aggregates information at the charging park or station level to manage the high number of charging points within a TPEG service This method ensures that not all descriptive data needs to be transmitted, promoting efficient use of the transmission channel.

End users seeking to reserve a specific charging point at a charging station will find detailed information essential To enhance user experience, EMI facilitates a request and response session that enables reservations for individual charging points within charging stations or parks For more details, refer to section 6.2.3.

Static vs dynamic information: Charging park information, charging

An EMI service provider must deliver substantial data to a TPEG client while maintaining a low transmission data rate The conventional TPEG model, where each message corresponds to a single content item, is inadequate for EMI, as it would delay the provision of usable data to clients lacking prior information, such as transit users Therefore, a transmission approach that combines high repetition rates for minimal content with lower repetition rates for more detailed information is essential.

EMI encompasses both static information, like descriptive details about charging parks, and frequently updated data, such as availability status It is essential for EMI to maintain high information quality to accommodate varying repetition rates.

EMI enables service providers to flexibly manage their transmissions based on data volume and available data rates A TPEG message can include either partial or complete details for a charging park or station When data rates are limited, service providers may opt to aggregate descriptive information at the charging park level, combining this typically static information with location data.

Charging parks and stations provide dynamic availability information stored in compact data structures for faster transmission TPEG messages with this availability data do not include location details Instead, TPEG clients utilize ID keys to integrate availability information with other relevant data for charging parks and stations.

Request and response

EMI facilitates a request and response session to reserve a ChargingPoint that aligns with the end user's needs and the vehicle's specifications, effectively communicating the necessary parameters to a reservation service typically provided by an EM provider.

A sample EMI request message is illustrated in Figure 5 The request must either directly reference the charging station or indicate a nearby point for locating an available charging station It is essential to include one of three options for location referencing in the request message.

— internal TPEG reference (parkID_Key and optionally stationID_Key);

— external reference (stationExternalID, e.g EVSE ID);

— coordinates of a point (longitude, latitude) and optionally parkOperator and/or providerExternalID.

A sample EMI response message illustrates the use of the reservationConfirmed attribute, which indicates the status of a reservation request If the request is not confirmed, the reservationFreeText attribute provides additional information When the request is confirmed, it is advisable to utilize the venueExternalID and reservationID to clearly identify the reservation, whether it pertains to a charging station or a charging point.

Pricing information

The pricing and billing models in the electromobility market significantly differ from traditional fuel pricing, as well as among themselves This variation is primarily due to the diverse range of business actors involved in the charging ecosystem, along with their unique relationships and business models.

End-users engage in a business relationship with an EM provider through a contract that dictates billing terms This agreement resembles a mobile phone contract and can vary in structure, including options such as prepaid plans that may offer differentiated rates based on vehicle type or power consumption, flat rates, and other formats.

Charging park operators require end users to identify themselves using customer cards issued by their EM providers Instead of billing the end users directly, these operators receive payments from the EM providers through roaming agreements, which enable users to access charging infrastructure regardless of the on-site provider The infrastructure and power providers maintain business relationships with multiple EM providers, establishing wholesale pricing that remains transparent to end users, who only need to consider their contract with their specific EM provider.

For end users, it is crucial to understand that their customer card from the EM provider allows them to identify and authorize themselves at charging stations, enabling usage and billing.

The charging park operator is unaware of the agreements between the end user and their energy management provider, making it difficult to predict the costs that the end user may incur.

Charging options can vary significantly between users, and some charging parks may provide services independent of any electric mobility (EM) provider, leading to different billing methods Various billing models may be implemented in these cases, though this list is not exhaustive.

— Based on usage (e.g per hour, …)

— “Buying costumers” can charge for free or get a price reduction

— Dependent on maximum current (“slow” vs “fast” charging)

TPEG EMI must accommodate various flexible billing models, which are often incompatible with one another Supporting all these options within a single, rigid data structure poses significant challenges and risks, particularly the potential emergence of new, unforeseen billing models by providers that such a structure would not be able to address.

EMI serves as a reference point for pricing, helping end users identify maximum and minimum prices, differentiate between standard and premium offers, and compare charging stations Additional details, such as special promotions, can be provided in free text.

EMI message structure

The top-level structure of an EMI message, as shown in Figure 7, is intended to convey either descriptive information, which is mostly static, or availability information, which is primarily dynamic, for a charging park or charging station.

The following types of information can be transmitted in an EMI message:

— Information on a charging park (typically: capacity, site description, etc.) Pricing/billing information can be included.

— Information on charging stations belonging to the charging park (typically: available connector types, supported vehicle types, vehicle size restrictions).

— Availability information for a charging park (number of free places).

— Availability information for a charging station (e.g the number of free places per connector type).

— Location information on a charging park (in addition to the obligatory coordinates in the LocationReferencingContainer), optionally enhanced by location information for charging stations.

Charging park information should be transmitted in an EMI message with a long expiry time due to its stability for a given service EMI messages can reference availability information using parkID_Key and stationID_Key This system enables the transmission of both full and partial descriptive information for charging parks and stations, which can be recombined in the TPEG receiver Consequently, service providers can adjust the amount of information and repetition rate of EMI messages to match the available data rate for their services.

The following is the minimum information needed for a TPEG client to present useful information to its user:

— ChargingParkInformation containing the parkID_Key and a minimal ChargingParkSiteDesription (parkName and the name of the parkOperator), ideally complemented by the

— ChargingParkAvailabilityVector containing a timestamp and minimal information on the ChargingParkAvailability (parkID_Key and overall number of freePlacesForPark).

The ChargingParkInformation attributes enable end users to choose suitable charging parks and allow TPEG clients to automatically filter out parks that do not meet the user's specific needs.

Figure 7 — Main structure of an EMI message

Figure 8 — Structure of EMI ChargingParkSiteDescriptionThe data structure ChargingParkSiteDescription extends the ChargingParkInformation with more detailed descriptive information on the ChargingPark; see Figure 8.

Figure 9 — Structure of EMI ChargingStationInformation

Charging stations can be detailed for each charging park, as illustrated in Figure 9 This data structure is crucial as it specifies the supported connector types for each charging station, enabling the TPEG client to filter options based on the socket compatibility with the user's vehicle Additionally, other attributes can be utilized to exclude charging stations that do not meet the user's needs or the specifications of their electric vehicle.

Figure 10 — Structure of EMI ChargingParkAvailability

A service provider has the option to present availability information either at the charging park level or the individual charging station level When opting for aggregation at the charging park level, the service provider will display the total number of available charging spots within that park.

Service providers must indicate the availability of charging stations by specifying the number of available charging spots for each connector type, aggregated across all charging points at the respective station.

Charging stations often feature multiple connectors of various types, leading to a total number of available connector spaces that can significantly exceed the available parking spaces It is essential for service providers to meticulously calculate these figures at different levels to ensure accuracy.

Figure 11 — Structure of EMI Request

The UML class structure of the EMI Request message is shown in Figure 11 The EMI response is contained in the main EMI message (see Figure 7).

In Annex A, the TPEG binary representation of this EMI service data frame structure is defined In Annex B, the TPEG-ML representation for EMI is specified.

EMIMessage

The overall EMI message container is defined in Table 2.

The MMC specification outlines a component dedicated to message management, ensuring that the sender generates transmission data that allows for clear interpretation over time, even in scenarios with disrupted reception The ChargingParkAvailabilityVector component provides dynamic information about the availability of charging stations across multiple parks In contrast, the ChargingParkInformation component conveys static details about a charging park and can be transmitted infrequently Additionally, the ReservationResponse component is used to communicate responses to reservation requests The DetailedChargingParkLocation offers precise geolocation information for charging park entry, exit, or individual stations, while the ChargingParkLocation provides a geographic reference for a charging park, though it is not applicable for the availability vector.

MessageManagementContainerLink

The MessageManagementContainerLink is the MessageManagementContainer from the TPEG2-MMC toolkit in ISO/TS 21219-6.

ChargingParkLocation

The ChargingParkLocation is the Geographic Coverage location reference, Location Referencing Container from the TPEG-LRC toolkit in ISO/TS 18234-11.

ChargingParkAvailabilityVector

Table 3 shows the component that groups information on the availability of charging stations within one or more charging parks This can be highly dynamic information.

The article discusses the timing information for the latest valid data on charging park availability, identified as "timeStamp." It highlights the "chargingParkAvailability" type, which provides details on the availability of charging spots at specific charging parks, with the option to break down the information to individual charging stations Additionally, it includes a "vectorLabel" that offers a brief description of the charging parks associated with this vector, such as all charging parks located in Garmisch-Partenkirchen.

ChargingParkInformation

Table 4 shows the component to transmit largely static information on a charging park This component can be sent with a low repetition rate.

The parkID_Key is an internal identifier for a charging park, essential for end-user devices or applications to access detailed information about the park's location and availability, as well as reservation responses The chargingParkSiteDescription provides additional background information about the charging park The chargingParkCapacity indicates the total number of available charging spots, while the electricityLabel identifies the energy source used, such as renewable energy UserType specifies the types of users allowed to utilize the charging park, and facilityType denotes whether the park is private or public Reservability indicates if reservations for charging spots are possible, and pricingInformation outlines the various flexible billing models supported at the charging park, along with the paymentMethodType for transactions.

This charging park supports multiple payment methods, allowing for flexibility in transactions Additional information, such as promotional offers related to billing options, can also be provided Furthermore, static information about the charging station is available to enhance user experience.

ChargingStationInformation

Table 5 shows the component to transmit static information on a charging station This component may be sent with a low repetition rate.

Name Type Multiplicity Description stationID_Key IntUnLoMB 1 EMI internal identifier for a charging station With- in a charging park (identified by its parkID_Key) the stationID_Key uniquely identifies a charging station.

The stationID_Key is essential for end-user devices or applications to access comprehensive charging station information, including location and ChargingStationAvailability data, along with the optional ReservationResponse The stationExternalId serves as an external identifier for the charging station, such as the EVSE ID, while the connectorType provides details on the supported connector types at the station Additionally, the stationType indicates the specific type of charging station, and the vehicleType outlines the compatible vehicle types for charging Lastly, sizeRestrictions specify any limitations on vehicle sizes allowed to park and charge at the station.

DetailedChargingParkLocation

Table 6 shows the detailed geolocation referencing information for charging park entry, charging park exit or single charging stations.

The parkID_Key is an internal identifier for a charging park, designated as IntUnLoMB with a multiplicity of 1 This key is essential for end-user devices or applications to integrate information about the charging park, including its detailed location and availability data, as well as the optional ReservationResponse.

The article discusses the components related to the charging park's entry and exit locations, specifically highlighting the parkEntryLocation and parkExitLocation, which provide additional information about the entry and exit roads Additionally, it mentions the detailedChargingStationLocation, a container component that holds comprehensive location details for multiple charging stations.

ParkEntryLocation

The ParkEntryLocation is the component to encode a charging park entrance road/ramp as a Location Referencing Container from the TPEG-LRC toolkit in ISO/TS 18234-11.

ParkExitLocation

The ParkExitLocation is the component to encode a charging park exit road/ramp as a Location Referencing Container from the TPEG-LRC toolkit in ISO/TS 18234-11.

DetailedChargingStationLocation

Table 7 shows the location reference information for the location of the charging station.

The stationID_Key is an internal identifier for a charging station, uniquely distinguishing it within a charging park identified by parkID_Key This key is essential for end-user devices or applications to access comprehensive charging station information, including detailed location, ChargingStationAvailability data, and optionally, the ReservationResponse.

Ordered components detailedStationLocation StationLocation 1 Location reference for the charging station.

StationLocation

The StationLocation is the component to encode a charging station location as a Location Referencing Container from the TPEG-LRC toolkit in ISO/TS 18234-11.

EMIMessageRequest

Table 8 shows the overall EMIMessageRequest container.

Ordered components mmt MessageManagementContainerLinkRequest 1 This component is specified in the MMC specification It contains all and only information related to message management.

The sender must ensure that the message management information is clear and interpretable over time, particularly in scenarios where the transmission channel may experience disturbances The application information includes a ReservationRequest component, which is used to transmit a reservation request.

MessageManagementContainerLinkRequest

The MessageManagementContainerLinkRequest is the MessageManagementContainer from the TPEG-MMC toolkit in ISO/TS 21219-6.

ReservationRequest

Table 9 defines the component to transmit a ReservationRequest.

The authentication ID is a short string that uniquely identifies the user making a reservation request, with the authentication process facilitated by the customer card provided by the EM provider The payment method type is specified as emi004.

The payment method(s) supported by the requesting user must align with those available at the charging park to facilitate proper billing for the reservation Additionally, the connector type(s) compatible with the electric vehicle involved in the reservation request should be specified If available, an external identifier for the charging station, such as the EVSE ID, can be provided, although no additional geographical information is required for the request.

The parkID_Key is an internal identifier, represented as an IntUnLoMB type, that indicates a charging park for which a reservation is being requested Typically, this identifier is used alongside the stationID_Key to specify the charging station within the designated charging park.

The parkID_Key is essential for end-user devices or applications to integrate charging park information, including detailed locations and ChargingParkAvailability data, along with the optional ReservationResponse The stationID_Key serves as an internal identifier for a specific charging station within a charging park, which is identified by the parkID_Key When making a reservation request, both the stationID_Key and the corresponding parkID_Key must be specified to uniquely identify the charging station within the designated charging park.

The stationID_Key is essential for end-user devices or applications to access charging station information, including detailed location and availability data, as well as optional ReservationResponse The longitude and latitude coordinates, both required for reservation requests, pinpoint the exact location of the desired charging point Additionally, the parkOperator identifies the charging park operator involved in the reservation process.

The Reservation Request for a charging point operated by a specific provider may include longitude and latitude coordinates It can also incorporate an external identifier for the electromobility provider, such as the EVSE ID, and an identifier for the vehicle, like the car number plate Additionally, the request may specify the vehicle type and the user type involved in the reservation process.

The article outlines key attributes related to vehicle reservations, including the estimated arrival time, which indicates when the vehicle is expected to reach the requested location It also specifies the estimated pickup time, detailing when the vehicle will be collected from the reservation site Additionally, size restrictions are noted, defining the dimensions of the vehicle that can be reserved.

ReservationResponse

Table 10 shows the component to transmit the response to a reservation request The component shall contain all relevant information on a charging station for which a reservation request can be confirmed.

The reservation response includes several key attributes: the reservation timestamp, which indicates the exact time the response is provided; a boolean value confirming whether the reservation is successful; an optional external identifier for the charging point or station, recommended for positive responses; and a unique identifier for the reservation itself.

For a positive reservation response, it is recommended to use the parkID_Key, which serves as the internal identifier for the confirmed charging park This key, along with the stationID_Key, allows end-user devices or applications to access comprehensive information about the charging park, including its location and availability The stationID_Key uniquely identifies the specific charging station within the designated charging park, ensuring clarity and precision in reservation details.

The stationID_Key enables end-user devices or applications to integrate charging station information, including detailed locations and ChargingStationAvailability data, along with the optional ReservationResponse.

The reservation details for a charging point include the earliest available time, referred to as arrivalTime, which is a DateTime value and can be optional (0 1) Additionally, the latest time for vehicle removal, known as pickupTime, is also a DateTime value and may be optional (0 1) Furthermore, any extra information related to the reservation, such as cancellation policies or billing for unused time, can be provided in the reservationFreeText field, which is a LocalizedShortString and is likewise optional (0 1).

ChargingParkAvailability

Table 11 presents the components used to convey the availability of charging spots at a designated charging park, highlighting the dynamic nature of this information Additionally, the availability details can be further specified down to individual charging stations and points.

The parkID_Key is an internal identifier for a charging park, utilized by end-user devices or applications to access comprehensive charging park information, including detailed location and ChargingParkAvailability data, as well as the optional ReservationResponse Additionally, the freePlacesForPark provides real-time data on the total number of available charging spots within the park, reflecting potentially dynamic changes.

The number of available charging places does not necessarily equal the sum of the free places for each connector type, as a single charging station can have multiple connectors per parking spot The timestamp for the parking availability indicates the date and time when the latest valid information was provided Additionally, the minimal waiting time represents the estimated minutes an end user may need to wait if no charging places are available Furthermore, the charging station availability provides optional information on the availability of each charging station within the charging park, which may contain multiple stations.

ChargingStationAvailability

Table 12 shows the component to transmit information on the availability of a charging station at a specific charging park.

Name Type Multiplicity Description stationID_Key IntUnLoMB 1 EMI internal identifier for a charging station Within a charging park (identified by its parkID_Key), the stationID_Key uniquely identifies a charging station.

The stationID_Key is essential for end-user devices or applications to integrate charging station information, including detailed locations and availability data, along with the optional ReservationResponse The freePlacesForConnectorType provides real-time data on the number of available charging spots for each connector type at the station, which can change frequently Additionally, the minGuaranteedAmperage indicates the minimum current available, ensuring users are informed about the charging capabilities.

Ampere which is currently guaran- teed by the charging park operator This information can be used by an end user or end-user device to estimate charging time.

FreePlacesForConnectorType

Table 13 shows the component to transmit dynamic information on a charging station specifying the number of available charging places per connector type at this charging station.

The article provides essential information about charging station data, including the number of available charging places for a specific connector type, identified as "IntUnLoMB" with a multiplicity of 1 It also defines the connector type as "emi002" and includes a waiting time qualifier, "emi003," which is applicable only when a waiting time is present Additionally, it estimates the waiting time in minutes for users when no charging places are available, quantified by the waiting time quantifier.

ChargingParkSiteDescription

Table 14 shows the component to transmit further background information on a charging park.

The charging park, identified by its unique name and operated by a specific operator, provides essential details such as operator contact information and the park's address in local languages The operator's logo and an external identifier for the electromobility provider may also be included Users can assess the financial viability of using the charging park by checking for roaming agreements with their electromobility provider; if their provider is not listed as a roaming partner, the park may not be a cost-effective option Additionally, the charging park's opening hours and associated services, such as park-and-ride and public transportation access, are available, along with any further descriptive information to enhance user understanding.

Logo

Table 15 shows the component to transmit operator Logo either as link or as favicon.

The article outlines the specifications for a logo, detailing its attributes such as name, type, and multiplicity It includes the mime type as a short string, with an optional URL link to the logo Additionally, it specifies the favicon's length, which can be up to 1,024 bytes, and provides the contents of the favicon, also limited to a maximum of 1,024 bytes.

OperatorContactInformation

Table 16 shows the general information (e.g phone, fax, email, website) to contact the operator of this charging park.

Name Type Multiplicity Description operatorContactType emi011: ContactType 0 1 Contact type operatorContactText ShortString 0 1 Text containing phone number, etc.

SizeRestrictions

Table 17 shows the applicable size restrictions on vehicles allowed to park and charge at this charging station.

The vehicle specifications include the maximum dimensions: length, width, and height, measured in centimetres, with the maximum length, width, and height defined as IntUnLoMB values ranging from 0 to 1 Additionally, the maximum weight of the vehicle is specified in kilogrammes as a Weight value, also within the 0 to 1 range Furthermore, the minimal required length of the charging cable is indicated in centimetres, represented as an IntUnLoMB value from 0 to 1.

PricingInformation

Table 18 shows the information on pricing and billing models at this charging park EMI supports many different, flexible billing models.

The article outlines key attributes related to pricing information, including the acquisition timestamp, which indicates when the last valid pricing data was published It specifies the unit price resolution, detailing the number of decimal points used Additionally, it discusses the price qualifier that qualifies the price information and the price per delivery unit, which may be influenced by the qualifier The billing model is defined as the unit for which unit prices are provided, and the currency type indicates the supported currency types for payments at the charging park.

Table 19 enumerates the types of billing models offered at this facility.

Code Reference-English “word” Comment Example

001 price per KWh kilowatt-hour; unit, KWh

Table 20 enumerates the list of connector types supported at this facility, including (wherever appropriate) the technical maximum for supported charging current.

026 CCS (EU IEC 62196), DC + AC

Table 21 enumerates a list of qualifiers.

emi004: PaymentMethodType

Table 22 enumerates the applicable methods of payment accepted at this facility.

011 customer loyalty card In the UK, also known as “agen- cy card”; in North America as

“reward card” or “club card”.

emi005: FacilityType

Table 23 enumerates a list of facility types.

emi006: AssociatedServiceType

emi007: UserType

Table 25 enumerates a list of user types.

emi008: StationType

Table 26 enumerates a list of station types.

emi009: VehicleType

Table 27 enumerates a list of vehicle types.

emi010: Reservability

Table 28 enumerates a list of reservability types.

emi011: ContactType

Table 29 enumerates a list of contact types.

Annex A (normative) TPEG application, TPEG-Binary Representation

A.1.1 List of generic component IDs

:(0), : ID of this component

(lengthComp), : Number of bytes in this component

(lengthAttr), : Number of bytes in attributes ordered {

(mmt), : This component is specified in the

MMC specification It contains all and only information related to message management.

The sender must ensure that the message management information allows for unambiguous interpretation over time and in scenarios with potential reception disturbances specific to the transmission channel The component \$(chargingParkAvailabilityVector)\$ consolidates dynamic information regarding the availability of charging stations across one or more charging parks The \$(chargingParkInformation)[0 1]\$ component transmits static information about a charging park, typically sent at a low repetition rate The \$(reservationResponse)[0 1]\$ component conveys the response to a reservation request Additionally, the \$(detailedChargingParkLocation)[0 1]\$ provides precise geolocation information for charging park entry, exit, or individual charging stations, while the \$(chargingParkLocation)[0 1]\$ offers a geographic coverage reference for a charging park, which is not applicable for the availability vector.

:External; : See MessageManagementContainer specification. A.1.4 ChargingParkLocation

:External; : See LocationReferencingContainer specification. A.1.5 ChargingParkAvailabilityVector

(lengthAttr), : Number of bytes in attributes

(timeStamp), : Provides timing information for the latest valid information on the Table A.1 (continued)

(n), n *(chargingParkAvailability), : Information on the availability of charging places at a specific charging park Optionally, the availability information may be broken down to the level of charging stations.

BitArray(selector), if (bit 0 of selector is set)

(vectorLabel); : Description of charging parks belonging to this vector (e.g all charging parks in Garmisch-Partenkirchen). A.1.6 ChargingParkInformation

The parkID_Key serves as the internal identifier for a charging park, enabling end-user devices or applications to access comprehensive information about the charging park, including its precise location, availability data, and, if applicable, the ReservationResponse.

(chargingParkSiteDescription), : Further background information on this charging park.

(chargingParkCapacity), : Total number of available charging places at this charging park. if (bit 1 of selector is set)

(n), n *(electricityLabel), : Identifier for the electricity provided at this charging park, by which (renewable) energy source the electricity is generated.

} if (bit 2 of selector is set)

(n), n *(userType), : Information on types of users that are permitted to make use of this charging park (e.g all users, custom- ers, etc.).

(facilityType), : Type of charging park (e.g private or public). if (bit 4 of selector is set)

(reservability), : Information as to whether reservation of a charging place is possible at this charging park. if (bit 5 of selector is set)

(n), n *(pricingInformation), : Information on pricing and billing models at this charging park EMI supports many different flexible billing models.

(n), n *(paymentMethodType), : Payment methods supported at this charging park.

(n), n *(freeText), : May contain additional information regarding the billing options (such as promotional offers) at this charging park.

} ordered { n *(chargingStationInformation) : Static information on a charging station.

(stationID_Key), : EMI internal identifier for a charging station Within a charging park (identified by its parkID_Key), the stationID_Key uniquely identifies a charging station.

The stationID_Key shall be used by an end-user device or application to combine charging station information, detailed charging station location and ChargingStationAvailability

(stationExternalId), : External identifier for the charging station, if applicable (e.g based on the EVSE ID). if (bit 1 of selector is set)

(n), n *(connectorType), : Information on the connector type(s) supported at this charging station.

(stationType), : Information on the station type for this charging station. if (bit 3 of selector is set)

(n), n *(vehicleType), : Information on the vehicle type(s) that are supported for using this charging station.

(sizeRestrictions); : Applicable size restrictions on vehicles permitted to park and charge at this charging station.

The parkID_Key serves as the internal identifier for a charging park, enabling end-user devices or applications to access comprehensive information about the charging park, including its location and availability It may also include the ReservationResponse Additionally, the data structure provides details on the entry and exit locations of the charging park, as well as a container for detailed location information regarding multiple charging stations.

:External ; : See LocationReferencingContainer specification. A.1.10 ParkExitLocation

:External ; : See LocationReferencingContainer specification. A.1.11 DetailedChargingStationLocation

(stationID_Key), : EMI internal identifier for a charging station Within a charging park (identified by its parkID_Key), the stationID_Key uniquely identifies a charging station.

The stationID_Key enables an end-user device or application to integrate information about charging stations, including their detailed locations and availability data, along with the optional ReservationResponse.

(detailedStationLocation) : Location reference for the charging station.

:External ; : See LocationReferencingContainer specification. A.1.13 EMIMessageRequest

(lengthAttr), : Number of bytes in attributes ordered {

(mmt), : This component is specified in the

MMC specification It contains all and only information related to message management.

The sender must ensure that the message management information is clear and interpretable over time, particularly in scenarios where the transmission channel may experience disturbances The component responsible for this is the \$(applicationInformation)[0 1]\$, which is used to transmit a reservation request.

Request(15)>:External; : See MessageManagementContainer specification.

The authentificationId is a unique identifier that verifies the user initiating the reservation request, with authentication managed through the customer card provided by the EM provider.

The payment method(s) supported by the requesting user must align with those accepted by the charging park to ensure accurate billing for the reservation.

(connectorType), : Information on the connector type(s) supported by the electric vehicle for which the reservation request is carried out.

The external identifier for the charging station, referred to as (stationExternalId), is used when requesting a reservation, particularly if it is known based on the EVSE ID There is no need for additional geographical identification information for this request, provided that bit 1 of the selector is set.

The EMI internal identifier, referred to as (parkID_Key), is used to specify a charging park for which a reservation is being requested Additionally, the Reservation Request typically includes the stationID_Key to pinpoint the specific charging station within that charging park.

The parkID_Key enables an end-user device or application to integrate charging park information, detailed location data, and ChargingParkAvailability, along with the optional ReservationResponse if bit 2 of the selector is activated.

The stationID_Key serves as the internal identifier for a charging station when making a reservation, and it must be used alongside the parkID_Key Within a charging park, which is identified by the parkID_Key, the stationID_Key uniquely distinguishes each charging station.

The stationID_Key enables end-user devices or applications to integrate charging station information, detailed location data, and ChargingStationAvailability, along with the optional ReservationResponse if bit 3 of the selector is activated.

The longitude of a location for a reservation request is specified by IntSi24 and must be used alongside latitude Together, these coordinates pinpoint the exact location for reserving a charging point This requirement applies only when bit 4 of the selector is activated.

The latitude of a location for a reservation request is specified by IntSi24 It must be used in conjunction with longitude to accurately identify the location of a charging point that needs to be reserved.

The charging park operator is identified as (parkOperator), which can be combined with longitude and latitude when a Reservation Request is made for a specific charging point operated by that operator, provided that bit 6 of the selector is set.

(providerExternalId), : External identifier for the electromobility provider, if applicable (e.g based on the EVSE ID). if (bit 7 of selector is set)

(vehicleId), : Identifier for the vehicle, if applicable (e.g based on the car number plate). if (bit 8 of selector is set)

(vehicleType), : Information on the vehicle type for which the reservation request is performed. if (bit 9 of selector is set)

(userType), : Information on type(s) of user that is carrying out the reservation request. if (bit 10 of selector is set)

(estimatedArrivalTime), : Estimated time of arrival at the location at which a reservation is requested. if (bit 11 of selector is set)

(estimatedPickupTime), : Estimated time at which the vehicle will be retrieved from the location at which a reservation is requested. if (bit 12 of selector is set)

(sizeRestrictions); : Dimensions of the vehicle for which a reservation is requested.

:(17), : ID of this component.

(reservationTimeStamp), : Time at which the reservation response is given.

(reservationConfirmed), : True, if reservation is confirmed; otherwise, false. if (bit 1 of selector is set)

Tiêu đề	Intelligent Transport Systems — Traffic And Travel Information (Tti) Via Transport Protocol Experts Group, Generation 2 (Tpeg2) — Part 25: Electromobility Charging Infrastructure (Tpeg2-Emi)
Trường học	ISO
Chuyên ngành	Intelligent Transport Systems
Thể loại	technical specification
Năm xuất bản	2017
Thành phố	Geneva

Định dạng
Số trang	70
Dung lượng	2,12 MB