DOCSEARCHbyAlgolia
Submit Docs

SK Electlink CSMS Documentation

website·Indexed 30 days ago

https://csms-docs.skelectlink.co

Technical documentation for the Charging Station Management System (CSMS) operated by SK Electlink. It provides guidelines for EVSE integration, covering OCPP v1.6 and v2.1 protocols, custom message implementations, security profiles (TLS/Certificates), and specific use cases such as Plug & Charge (PnC), V2G, demand response, and user authentication.

Tokens
45.6K
Snippets
129
Records
263
Agent score
50%

What's inside SK Electlink

  1. Overview of SK Electlink OCPP Protocol Support

    SK Electlink is a member of the OCA (Open Charge Alliance) and supports the OCPP protocol. They ensure stable charging infrastructure operation through strict adherence to these standards.

  2. Overview of CSMS Advertisement Distribution

    The CSMS provides functionality to manage and distribute advertisement content to be displayed on charger HMIs. The system uses a Pull-based mechanism where the charger requests profiles and media files via OCPP DataTransfer. The CSMS can also force a profile update by sending a TriggerMessage to the charger. This functionality is common for both OCPP v1.6 and v2.1 sessions using the com.skelectlink vendor ID.

  3. Overview of Plug and Charge (PnC) Technology

    Plug and Charge (PnC) is an automated charging technology that allows an electric vehicle (EV) to start charging and complete payment automatically upon connecting the charging cable, without requiring separate authentication steps or physical membership cards.

    Key characteristics include:

    • No Card: No need to issue or carry membership cards.
    • No Touch: No manual operation required other than connecting the cable.
    • Secure Charging: Secure communication between the EV and charging infrastructure based on digital certificates.

  4. Overview of SK Electlink Screen Capture functionality

    The screen capture feature allows the CSMS to automatically capture specific HMI screens on a charger and upload them to a server for remote verification. This functionality is implemented using custom DataTransfer messages and is compatible with both OCPP v1.6 and v2.1 sessions. The process follows a 'reserved snapshot request' model where the charger waits for a specific screen ID to be rendered before capturing and uploading the image.

  5. Overview of the SK Electlink Charging Station Management System (CSMS) Documentation

    This documentation provides essential information and guidelines for the operation and development of electric vehicle (EV) charging infrastructure managed by SK Electlink Co., Ltd. It is designed for developers and operators to understand the OCPP (Open Charge Point Protocol) based management system, including system architecture, custom messages, data types, and practical implementation cases.

  6. Overview of Plug & Charge (PnC) Roles

    Plug & Charge allows an EV to be automatically authenticated based on a Contract Certificate when the charging cable is connected, enabling seamless charging and billing. The key roles are:

    • Customer: Joins MO service, registers vehicle, agrees to PnC, and manages connector connection/disconnection.
    • Mobility Operator (MO): Manages customer contracts, collects PCIDs, generates eMAIDs, maps membership cards to eMAIDs, and issues/renews contract certificates.
    • EV: Stores OEM Provisioning and Contract Certificates; provides ISO 15118 authentication based on PCID/eMAID.
    • EVSE: Handles ISO 15118 sessions, relays certificate installation requests, and controls charging based on PnC results.
    • CSMS: Processes PnC requests from EVSE, verifies certificate status, and manages transaction start/end.

  7. ScreenCaptureResult request fields

    The ScreenCaptureResult message provides the following metadata about the capture event:

    • screenId (String, Required): The identifier of the captured screen (must match the trigger).
    • capturedAt (DateTime, Required): The actual time of capture (UTC, ISO 8601).
    • uploadStatus (String, Required): The result of the HTTP upload (Uploaded or UploadFailed).

  8. Understand the EV charging transaction lifecycle

    The charging transaction follows a six-step state transition process:

    1. Cable Connection/Authentication: User starts authentication; the connector is occupied.
    2. Transaction Start: Transaction begins after successful authentication.
    3. Energy Supply: EV begins receiving power.
    4. Periodic Updates: Data is transmitted repeatedly based on the MeterValueSampleInterval.
    5. Charging Completion: Energy supply stops due to completion or user request.
    6. Transaction End: Settlement data is finalized.
    7. Cable Disconnection: Connector is released and the system returns to the main screen.

  9. Understand SK Electlink CSMS Security Profile Requirements

    All charger manufacturers must adhere to the following security profiles to ensure secure communication with the SK Electlink CSMS. Failure to comply may result in restricted integration.

    • Security Profile 0 or 1: Unencrypted WebSocket. Not supported for new integrations.
    • Security Profile 2: TLS 1.2 minimum (TLS 1.3 recommended). This is the minimum requirement for integration.
    • Security Profile 3: TLS 1.2 minimum (TLS 1.3 recommended) with Client-Side Certificates. Recommended for enhanced security.

  10. Use AdMediaType for advertising media file details

    The AdMediaType structure is used in the response of the GetAdMedia message to provide detailed information about an advertising media file, including its download URL and MIME type.
    interface AdMediaType {
  mediaKey: string;    // Media file identification key (UUID)
  fileName: string;    // Original filename
  contentType: string; // MIME type (e.g., image/jpeg)
  fileSize: number;    // File size in bytes
  uri: string;         // Media file download URL
}

  11. Manage Credentials for Security Profile 2 (SP2) Onboarding

    Chargers using SP2 must follow this workflow to transition from manufacturer credentials to operational credentials:

    1. Initial Connection: The charger must attempt the first connection to the CSMS using the factory-assigned Manufacturer Credentials (provided by SK Electlink).
    2. Credential Injection: After a successful BootNotification, the CSMS will inject operational credentials into the EVSE using ChangeConfiguration (OCPP 1.6) or SetVariables (OCPP 2.x).
    3. Reconnection: The charger must store these operational credentials securely and reconnect to the CSMS using the new credentials.

  12. Implement Plug & Charge (PnC) fallback to MAC authentication

    If Plug & Charge fails, the EVSE must provide a fallback procedure. For SK Electlink integration, the EVSE should prioritize attempting MAC authentication:

    • DC Fallback: If failure occurs before Authorize, perform ISO 15118 DC flow Step_E/F, switch to Only EIM mode, and attempt MAC authentication.
    • AC Fallback: If failure occurs before Authorize, perform ISO 15118 AC flow Step_E/F, switch to Only EIM mode, and attempt MAC authentication.
    • AC Communication Failure: If communication is interrupted during charging (ChargingStatus), the EVSE may perform Step_E/F and BC (Basic Charging) and is recommended to provide MAC authentication fallback.

    If MAC authentication fails because the MAC address is unregistered, the EVSE should proceed to the MAC registration process.