OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ocpp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] (OCPP-87) Write Change Request: offline started/stopped transactions


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

Reinier Lamers commented on OCPP-87:
------------------------------------

I miss two things in the CR in its current form:
 * That besides authorization with the Local Authorization List, also presumptive offline authorization is possible
 * A definition of what "off-line" really means.

I think the latter point is the most difficult. A charge point may for example not have a physical connection at all (no SIM or no cable plugged in), or have an IP address but not be able to reach the Central System, or be able to reach the Central System over HTTP only to consistently get HTTP 500 Internal Server Error responses. Each of these situations can be informally called "offline", but the way charge points behave in them is in my experience often very different.

If we want to be interoperable on off-line behavior, we also have to be interoperable on when a Charge Point exhibits this behavior and when it doesn't. We could say that for the purposes of transaction authorization, a Charge Point is offline when it has not received any response (whether positive or negative) to its Authorization request for a given period of time.

Or I think we can also side-step the issue completely by instead of adding an "offline" boolean flag, adding a "authorizationMethod" field, which can have the values "Online", "AuthorizationCache", "LocalAuthList" or "PresumptiveOffline". In that case, when the Central System gets one of the latter three values, the Central System knows that the transaction was started without the Central System being involved.





> Write Change Request:  offline started/stopped transactions
> -----------------------------------------------------------
>
>                 Key: OCPP-87
>                 URL: https://issues.oasis-open.org/browse/OCPP-87
>             Project: OASIS OCPP Electric Vehicle Charging Equipment Data Exchange TC
>          Issue Type: Task
>         Environment: New ideas (OCA list)	
>            Reporter: Jonel Timbergen
>            Assignee: Robert de Leeuw
>            Priority: Trivial
>
> Write CR for marking offline started/stopped transactions, and submit to TC



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


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]