[OASIS Issue Tracker] (OCPP-18) Generation of transaction IDs

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/OCPP-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=64314#comment-64314 ] 

Li Sibo commented on OCPP-18:
-----------------------------

About Transaction ID, Our engineers recommend to have two seperated ID fields, e.g. TransactionID and RemoteTransactionID.

The first one is generated locally by EVSE, and the later one was created through center system. For transaction initiated by Center System, it carries the RemoteTransactionID through RemoteStartTransaction, and in the response, if the EVSE successfully started transaction and both RemoteTransactionID and local TransactionID need to be send back in the TransactionStarted message.

There are several consideration for this:
1) Both EVSE and CS should have ability to create transaction ID in their own scope. Seperated fields can avoid confusion.
2) EVSE should be able to operate offline. It could become offline during charging process, and casue some mapping issue for center system after it get back online. 

> Generation of transaction IDs
> -----------------------------
>
>                 Key: OCPP-18
>                 URL: https://issues.oasis-open.org/browse/OCPP-18
>             Project: OASIS OCPP Electric Vehicle Charging Equipment Data Exchange TC
>          Issue Type: Task
>         Environment: 2.0 RC 2 (old version) improvements
>            Reporter: Jonel Timbergen
>            Assignee: William Cox
>            Priority: Trivial
>
> For generating transaction IDs in the Charge Point: how should this be done, provide generally used methods input to TC.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)