[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=64441#comment-64441 ] 

Franc Buve commented on OCPP-12:
--------------------------------

If it is important to make sure, that you gather all meter value messages for one transaction, then OCPP 1.6 already supports the bundling of all transaction information in a single message. That is the purpose of the optional TransactionData element with all meter values in the StopTransaction.
If you already do real-time rating of a transaction, then repeating all meter values at the end of transaction might be considered a bit redundant, but it is supported.

We have been doing real-time rating of transactions for quite some time now and missing one or two meter values does not affect the rating. If you miss a meter value, then the next meter value is simply considered as an interval of twice the duration, because you always calculate the difference with respect to the last received meter value. Out-of-order meter values are easily recognized by their timestamp. We can choose to either ignore them or to trigger a recalculation over all meter values.

I don’t see an added value for message sequence numbers in this case.

Regards,
-Franc


> 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)