[OASIS Issue Tracker] (OCPP-12) Write CR proposal to address how to handle large amounts of queued messages.

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

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

Li Sibo commented on OCPP-12:
-----------------------------

Just had a thorough discussion earlier with our engineers.

There are couple of things we propose to do differently:

1) In China, we are quite sensitive to reduce the data send through wireless. So in normal cases, if the Charger get offline, the MeterValue PDU will just not send anymore after the charger went online again. But of course, only Start/Stop Transactions(2 PDUs) will be send for an offline order. It means we abandoned MeterValues PDU for offline transactions. For detailed Meter Value information, it can be stored locally for a period of time, depend on the manufacturer, depending on their own choices.

2) Even for online transactions, We only send one copy of detailed data through MeterValues PDU, and we don't include same information in StopTransaction PDU anymore.

3) For offline transactions, payment will be calculated by chargers locally, we will carry the finalized payment information through StopTransaction PDU. 

4) We had discussion with engineers in ABB, in general, both of us agree that it is important to generate two transaction IDs, one for Charger, and the other for Central System. and all transaction related PDU will carry seperated fields for both IDs. This method can solve a lot of problems

> Write CR proposal to address how to handle large amounts of queued messages.
> ----------------------------------------------------------------------------
>
>                 Key: OCPP-12
>                 URL: https://issues.oasis-open.org/browse/OCPP-12
>             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: Li Sibo
>            Priority: Trivial
>
> set an expiry time on messages to be able to lower priority when message is considered not relevant any more.Reinier gave input to OCA: Optional queing of messages. Write CR proposal to address how to handle large amounts of queued messages.



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