Roaming method

Abstract

The invention relates to a roaming method for an electrical charging system with at least two subsystems. In the method, a charging data set is received through a communication module of a gateway device from a charging station assigned to the gateway device. The charging data set is forwarded by a peer-to-peer module assigned to the gateway device to a peer-to-peer application of a peer-to-peer network, and a roaming action is controlled by a roaming controlling means of the peer-to-peer application executed by at least a part of the nodes of the peer-to-peer network based on the received charging data set.

Claims

1. A roaming method for a charging system with at least two charging subsystems, wherein each of the at least two charging subsystems comprises a gateway device connectable to at least one charging station, wherein the at least two charging subsystems differ from each other in the used authentication process and/or the accounting process wherein the at least two charging subsystems are networked by at least one peer-to-peer network, the method comprising: receiving a charging data set through a communication module of a gateway device from a charging station assigned to the gateway device, forwarding the charging data set by a peer-to-peer module assigned to the gateway device to a peer-to-peer application of the peer-to-peer network, and controlling at least part of a roaming process by a roaming controlling means of the peer-to-peer application executed by at least two of the nodes of the peer-to-peer network based on the received charging data set, wherein the charging data set comprises at least one peer-to-peer identifier assigned to a user of a vehicle to be charged or discharged and/or a vehicle to be charged or discharged of a user, wherein controlling a roaming process comprises at least initiating an authentication action, wherein the authentication action comprises evaluating the validity of the peer-to-peer identifier, based on the peer-to-peer identifier, wherein the peer-to-peer application is a decentralized register or a shared database, and wherein data is stored by the peer-to-peer application with given proofs or signatures.

2. The roaming method according to claim 1, wherein a charging action is only released upon a provision of a positive authentication result by the peer-to-peer application to the charging station via the gateway device.

3. The roaming method according to claim 1, wherein the charging data set comprises at least one charging subsystem identifier, wherein controlling a roaming process comprises at least initiating a forwarding action for forwarding the charging data set to at least one further peer-to-peer module assigned to at least one further gateway device of a further charging subsystem based on at least the subsystem identifier.

4. The roaming method according to claim 3, wherein the received charging data set is forwarded by the further gateway device to a further server for further processing the charging data set.

5. The roaming method according to claim 1, wherein the charging data set comprises at least one peer-to-peer identifier assigned to a user of an electrical device, in particular, a vehicle and/or an electrical device, in particular, a vehicle of a user and at least one charging amount information, wherein controlling a roaming process comprises at least controlling an accounting process for the charging process related to the charging data set based on at least the charging amount information and the peer-to-peer identifier.

6. The roaming method according to claim 1, wherein the charging data set received from a charging station comprises at least one subsystem identifier, wherein the charging data set is forwarded by a routing module of the gateway device to the peer-to-peer application or to a server depending on the subsystem identifier.

7. The roaming method according to claim 1, wherein the method comprises: providing at least one electrical grid status data set related to the current status of the electrical grid to the peer-to-peer application, wherein the grid status data set indicates that the electrical grid is currently overloaded or underloaded, and controlling the exchange of electrical power between at least one charging station and at least one electrical vehicle by transmitting at least one set power data set from the peer-to-peer application to at least one gateway device, wherein the set power data set is based on the provided electrical grid status data set.

8. The roaming method according to claim 1, wherein the method comprises: receiving a registering message by a registration means of the peer-to-peer application from a peer-to-peer module assigned to an electrical vehicle and/or a peer-to-peer module assigned to a user of the electrical vehicle, wherein the electrical vehicle and/or the user of the electrical vehicle is registered in the peer-to-peer application by storing a peer-to-peer identifier of the electrical vehicle and/or a user of the electrical vehicle.

9. The roaming method according to claim 1, wherein the method comprises: generating a roaming transaction agreement about at least one roaming process, wherein the roaming transaction agreement comprises at least one of: roaming criterion, identifiers of authorized gateway device(s) and/or of authorized charging station(s), at least one identifier(s) assigned to the first charging subsystem, at least one further identifier assigned the further charging subsystem, registering rule(s), roaming algorithm(s), and grid control and/or dynamic pricing algorithms, wherein the at least one roaming process is controlled by the roaming controlling means at least based on the generated roaming transaction agreement.

10. The roaming method according to claim 9, wherein the method comprises conducting at least one roaming criterion transaction at least controlled by the roaming controlling means based on at least one roaming criterion of the generated roaming transaction agreement, wherein financial values in accordance with the roaming criterion are exchanged with a roaming criterion transaction via a cryptocurrency.

11. The roaming method according to claim 1, characterized in that the at least one peer-to-peer application is a block chain or decentral ledger comprising at least two blocks coupled to each other.

12. The roaming method according to claim 1, wherein the peer-to-peer network comprises only one validating node configured to perform a validation process one or more observing nodes configured to validate transactions to establish a trust level.

13. A charging system, comprising: at least one peer-to-peer network comprising at least one peer-to-peer application; a first charging subsystem with at least one first gateway device connected with at least one first charging station via a communication connection for receiving at least one charging data set from the first charging station, at least one first peer-to-peer module assigned to the first gateway device and configured to communicate with the peer-to-peer application, wherein the peer-to-peer application comprises a roaming controlling means executed by at least two of the nodes of the peer-to-peer network and configured to control a roaming process based on the charging data set provided to the peer-to-peer application by means of the first peer-to-peer module, wherein the charging data set comprises at least one peer-to-peer identifier assigned to a user of a vehicle to be charged or discharged and/or a vehicle to be charged or discharged of a user, wherein controlling a roaming process comprises at least initiating an authentication action, wherein the authentication action comprises evaluating the validity of the peer-to-peer identifier, based on the peer-to-peer identifier, wherein the peer-to-peer application is a decentralized register or a shared database, and wherein data is stored by the peer-to-peer application with given proofs or signatures.

14. A gateway device assigned to a charging subsystem of a charging system, in particular, a charging system according to claim 13, comprising: at least one communication module configured to receive at least one charging data set from at least one charging station, at least one peer-to-peer module configured to provide the charging data set to at least one peer-to-peer application such that a roaming process is controllable by a roaming controlling means executed by at least two of the nodes of the peer-to-peer network based on the provided charging data set, wherein the charging data set comprises at least one peer-to-peer identifier assigned to a user of a vehicle to be charged or discharged and/or a vehicle to be charged or discharged of a user, and wherein controlling a roaming process comprises at least initiating an authentication action, wherein the authentication action comprises evaluating the validity of the peer-to-peer identifier, based on at least the peer-to-peer identifier, wherein the peer-to-peer application is a decentralized register or a shared database, and wherein data is stored by the peer-to-peer application with given proofs or signatures.

15. A peer-to-peer application of a peer-to-peer network, the peer-to-peer application comprising: at least one roaming controlling means executable by at least two of the nodes of the peer-to-peer network and configured to control a roaming process based on a charging data set provided by at least one peer-to-peer module assigned to a gateway device, wherein the charging data set comprises at least one peer-to-peer identifier assigned to a user of a vehicle to be charged or discharged and/or a vehicle to be charged or discharged of a user, wherein controlling a roaming process comprises at least initiating an authentication action, wherein the authentication action comprises evaluating the validity of the peer-to-peer identifier, based on the peer-to-peer identifier, wherein the peer-to-peer application is a decentralized register or a shared database, and wherein data is stored by the peer-to-peer application with given proofs or signatures.

16. A roaming method for a charging system with at least two charging subsystems, wherein each of the at least two charging subsystems comprises a gateway device connectable to at least one charging station, wherein the at least two charging subsystems differ from each other in the used authentication process and/or the accounting process wherein the at least two charging subsystems are networked by at least one peer-to-peer network, the method comprising: receiving a charging data set through a communication module of a gateway device from a charging station assigned to the gateway device, forwarding the charging data set by a peer-to-peer module assigned to the gateway device to a peer-to-peer application of the peer-to-peer network, and controlling at least part of a roaming process by a roaming controlling means of the peer-to-peer application executed by at least two of the nodes of the peer-to-peer network based on the received charging data set, wherein the charging data set comprises at least one peer-to-peer identifier assigned to a user of a vehicle to be charged or discharged and/or a vehicle to be charged or discharged of a user, wherein controlling a roaming process comprises at least initiating an authentication action, wherein the authentication action comprises evaluating the validity of the peer-to-peer identifier, based on the peer-to-peer identifier, and wherein the at least one peer-to-peer application is a block chain or decentral ledger comprising at least two blocks coupled to each other.

17. A charging system, comprising: at least one peer-to-peer network comprising at least one peer-to-peer application; a first charging subsystem with at least one first gateway device connected with at least one first charging station via a communication connection for receiving at least one charging data set from the first charging station, at least one first peer-to-peer module assigned to the first gateway device and configured to communicate with the peer-to-peer application, wherein the peer-to-peer application comprises a roaming controlling means executed by at least two of the nodes of the peer-to-peer network and configured to control a roaming process based on the charging data set provided to the peer-to-peer application by means of the first peer-to-peer module, wherein the charging data set comprises at least one peer-to-peer identifier assigned to a user of a vehicle to be charged or discharged and/or a vehicle to be charged or discharged of a user, wherein controlling a roaming process comprises at least initiating an authentication action, wherein the authentication action comprises evaluating the validity of the peer-to-peer identifier, based on the peer-to-peer identifier, and wherein the at least one peer-to-peer application is a block chain or decentral ledger comprising at least two blocks coupled to each other.

18. A gateway device assigned to a charging subsystem of a charging system, in particular, a charging system according to claim 17, comprising: at least one communication module configured to receive at least one charging data set from at least one charging station, at least one peer-to-peer module configured to provide the charging data set to at least one peer-to-peer application such that a roaming process is controllable by a roaming controlling means executed by at least two of the nodes of the peer-to-peer network based on the provided charging data set, wherein the charging data set comprises at least one peer-to-peer identifier assigned to a user of a vehicle to be charged or discharged and/or a vehicle to be charged or discharged of a user, wherein controlling a roaming process comprises at least initiating an authentication action, wherein the authentication action comprises evaluating the validity of the peer-to-peer identifier, based on at least the peer-to-peer identifier, and wherein the at least one peer-to-peer application is a block chain or decentral ledger comprising at least two blocks coupled to each other.

19. A peer-to-peer application of a peer-to-peer network, the peer-to-peer application comprising: at least one roaming controlling means executable by at least two of the nodes of the peer-to-peer network and configured to control a roaming process based on a charging data set provided by at least one peer-to-peer module assigned to a gateway device, wherein the charging data set comprises at least one peer-to-peer identifier assigned to a user of a vehicle to be charged or discharged and/or a vehicle to be charged or discharged of a user, wherein controlling a roaming process comprises at least initiating an authentication action, wherein the authentication action comprises evaluating the validity of the peer-to-peer identifier, based on the peer-to-peer identifier, and wherein the at least one peer-to-peer application is a block chain or decentral ledger comprising at least two blocks coupled to each other.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

(1) In the figures:

(2) FIG. 1 shows a schematic view of an embodiment of a charging system according to prior art;

(3) FIG. 2 shows a schematic view of an embodiment of an electrical inlet and/or outlet system, in particular, a charging system according to the present invention;

(4) FIG. 3 shows a schematic view of a further embodiment of an electrical inlet and/or outlet system, in particular, a charging system according to the present invention;

(5) FIG. 4 shows a schematic view of a further embodiment of an electrical inlet and/or outlet system, in particular, a charging system according to the present invention;

(6) FIG. 5 shows a schematic view of an embodiment of a peer-to-peer application according to the present invention;

(7) FIG. 6 shows a schematic view of a further embodiment of an electrical inlet and/or outlet system, in particular, a charging system according to the present invention; and

(8) FIG. 7 shows a diagram of an embodiment of a method according to the present invention.

DETAILED DESCRIPTION

(9) Like reference numerals in different figures indicate like elements. The subsequent embodiments may be related to the charging of electoral vehicles. However, the depicted embodiments can be easily transferred to an electrical inlet and/or outlet system configured to exchange electrical power between an electrical device and an electrical grid by means of a charging station.

(10) FIG. 2 shows a first embodiment of an electrical inlet and/or outlet system, in particular, a charging system 200 according to the present application. The charging system 200 comprises a first charging subsystem 202.1. It shall be understood that the charging system 200 may comprise two or more subsystems.

(11) The first subsystem 202.1 comprise at least one gateway device 210. By way of example, two charging stations 204 are connected with the gateway device 210 by a wired and/or wireless communication connection 212. For instance, each charging station can comprise a communication module 206 configured to establish a communication with a communication module 208 of the gateway device 210 via the communication connection 212.

(12) The charging station 204 may be a conventional charging station 204. A charging station 204 may be connected with a (not shown) electrical grid. Each charging station 204 may comprise one or more means configured to establish an electrical connection with one or more (not shown) vehicles in order to charge e.g. a battery of the vehicle. In addition, a charging station may be configured to discharge a battery. In other words, a bidirectional power (or current) flow may be provided by a charging station.

(13) Further, the charging station 204 may comprise a meter or the like to measure the power supplied or received to/from a vehicle. The charging station may be also configured to receive an identifier (e.g. peer-to-peer identifier) of the vehicle and/or user of the vehicle. For instance, the identifier can be received from the vehicle via the charging cable. Alternatively or additionally, the charging station may comprise a user interface or a nearfield interface configured to receive at least one identifier assigned to the user and/or vehicle.

(14) The communication module 204 may be configured to transmit a charging data set to the gateway device 210. E.g. prior to starting a charging action, the charging station 204 may receive an identifier from the vehicle to be charged or a user of said vehicle. The received identifier can be forwarded in form of a charging data set to the gateway device 210.

(15) The gateway device 210 may be connected with a first server 214 via a wired and/or wireless communication connection 220. For instance, between two communication modules 216, 218 a communication connection can be established via the communication connection 220. The first server 214 may comprise an accounting module 222 configured to process the received charging data set. For instance, based on the received charging data set comprising e.g. a user identifier (e.g. peer-to-peer identifier or another identifier) and the exchanged energy amount and a stored user data set comprising e.g. a user identifier and user account data, the accounting module may invoice the user for the charged energy amount. Invoicing can be done in fiat currency and/or a crypto token. The accounting system may comprise a (user, vehicle, charging station and/or device) ID registry.

(16) Further, the depicted gateway device 210 comprises a routing module 240. The routing module 240 may be configured to route a charging data set received from one of the charging stations 204. Preferably, based on a received identifier assigned to a subsystem, the received charging data set may be forwarded to the first server or the peer-to-peer module. For instance, if the received subsystem identifier is assigned to the first subsystem 202.1 the received charging data set may be transmitted to the first server 214 for further processing (e.g. accounting or authenticating). If the received subsystem identifier is assigned to a further subsystem the received charging data set may be forwarded to the peer-to-peer module 238 in order to provide said data set to a peer-to-peer application 232. It shall be noted that according to other variants a routing module can be omitted. For instance, a charging data set can be always forwarded to both the peer-to-peer module and a connected server or only to the peer-to-peer module.

(17) In the present embodiment, the peer-to-peer module 238 assigned to the gateway device 210 is integrated in the gateway device 238.

(18) A substantial difference compared with prior art charging systems, such as charging system 100 according to FIG. 1, is that no central instance and/or third party organization is provided. In the present case, the charging system 200 comprises a peer-to-peer network 230 or a computer-computer network 230. The peer-to-peer network 230 comprises a plurality of nodes 236.1, 236.2, 236.3 and computers 236.1, 236.2, 236.3, respectively. A (roaming) peer-to-peer network 230 is characterized in the present case in that each node 236.1, 236.2, 236.3 and/or participant 238 is preferably connectable at least to every other node 236.1, 236.2, 236.3 and/or participant 230. For instance, at least one physical standard network (wired and/or wireless) can be used for connection. For communicating via the at least one physical standard network suitable transceiver modules may be arranged in the respective entities/devices.

(19) In addition, the computers 236.1, 236.2, 236.3 have equal rights, something which distinguishes them from a server-client structure.

(20) The depicted nodes 236.1, 236.2, 236.3 (each) comprise a peer-to-peer application 232. As can be seen from FIG. 2, the same peer-to-peer application 232 is preferably implemented on each node 236.1, 236.2, 236.3. This means, in particular, that the same content is comprised on each node 236.1, 236.2, 236.3 and that the same code can be executed on each node 236.1, 236.2, 236.3.

(21) The peer-to-peer application 232 may preferably be a public register 232 or a decentral ledger 232 that can, in particular, be inspected by all participants 236.1, 236.2, 236.3, 238 (not only the nodes 236.1, 236.2, 236.3) of the peer-to-peer network 230. Each node 236.1, 236.2, 236.3 preferably has the (entire) public register 232. It may also be envisaged that only part of the register can be provided on a node (light node). In a particularly preferred embodiment, the peer-to-peer application 232 may be a block chain 232 which will be explained in more details hereinafter. It shall be understood that the peer-to-peer network may comprise further nodes. In addition, it shall be understood that also a gateway device can be formed as a node of the peer-to-peer network.

(22) The peer-to-peer network 230 is configured to network two or more charging subsystems. The (roaming) peer-to-peer application 232 may be configured to manage and control a roaming process and roaming actions, respectively. In particular, the peer-to-peer application 232 may comprise a roaming controlling means 234. In particular, roaming actions related to a charging process of a vehicle at a charging station 204 is controlled by the peer-to-peer application 232 and the peer-to-peer network 230. In order to enable that a user or vehicle registered in another subsystem than the first subsystem 202.2 can use a charging station 204 of the first subsystem 202.1 the roaming controlling means 234 can control and/or conduct a roaming process e.g. including an authentication action and/or an accounting action and/or a forwarding action.

(23) A peer-to-peer module 238 is (generally) configured to communicate at least with the peer-to-peer network 230, i.e. the nodes 236.1, 236.2, 236.3 of the peer-to-peer network 230. In other words, the first peer-to-peer module 238 or the gateway device 210 corresponding and/or assigned to the respective peer-to-peer module 238 is at least a participant of the peer-to-peer network 230. Preferably, all participants 236.1, 236.2, 236.3, 238 (including all nodes) of the peer-to-peer network 230 are known to each participant 236.1, 236.2, 236.3, 238 of the peer-to-peer network 230.

(24) In the present case, the first peer-to-peer modules 238 is not a node of the peer-to-peer network 230 but only a participant 238. While nodes 236.1, 236.2, 236.3 or computers 236.1, 236.2, 236.3 in the peer-to-peer network 230 comprise at least a part of the peer-to-peer application 232 itself, a participant of a peer-to-peer network 230, like the present peer-to-peer module 238, does not comprise the peer-to-peer application 232. Such a peer-to-peer module 238 is configured to provide (only) access to the peer-to-peer application 232 e.g. via an API (application programming interface). Each peer-to-peer module 238 (also a node or light node) may comprise a decentral application and at least an API.

(25) In the case, the peer-to-peer module is formed as a node of the peer-to-peer network the peer-to-peer module (also) comprises at least partly the peer-to-peer application 232. It shall be understood that a peer-to-peer module 238 might be a node of the peer-to-peer network. It shall be understood that a peer-to-peer module 238 may have access or may be connected to a “gateway” running a node of the peer-to-peer network.

(26) The first peer-to-peer module 238 may comprise a communication connection to the routing module 240. The routing module 240, as explained above, may be configured to forward a charging data set to the peer-to-peer module 238 (e.g. based on a subsystem identifier).

(27) The peer-to-peer module 238 may transmit, e.g. write, said charging data set to the peer-to-peer application 232. In particular, the roaming controlling means 234 may be configured to further process the received charging data set. Further, the first peer-to-peer module 238 may be configured to receive data, e.g. a charging data set or an authentication result, from the peer-to-peer application 232. For instance, the peer-to-peer module 238 may receive one or more message(s) and/or may be allowed to read out data intended for said peer-to-peer module 238 (e.g. due to a respective identifier). For instance, a charging data set received from the peer-to-peer application 232 can be forwarded from the first gateway device 210 to the first server 214 for further processing (e.g. authenticating or accounting).

(28) The providing of the charging data set to a peer-to-peer module 238 may be caused or initiated by the roaming controlling means 234. The roaming controlling means 234 can be at least executed by a part (two or more) of the nodes 236.1, 236.2, 236.3 of the peer-to-peer network 230. Since at least a part (preferably, a plurality) of the nodes 236.1, 236.2, 236.3 is involved (and not only a single computer) a manipulation risk can be significantly reduced without needing a central instance, such as a server.

(29) FIG. 3 shows a schematic view of a further (more detailed) embodiment of a charging system 300 according to the present application. It shall be noted that mainly the differences between system 200 and system 300 will be explained.

(30) As can be seen from FIG. 3, the depicted charging system 300 comprises three different charging subsystems 302.1, 302.2, 302.3 (e.g. of three different providers). E.g. subsystem may be at least partly a proprietary system e.g. comprising different authentication mechanism and/or accounting mechanism. In order to enable a user or vehicle registered only in a first subsystem 302.2 to use also charging stations 304.2 and/or charging stations 304.3 the depicted subsystems 302.1, 302.2, 302.3 are networked by a peer-to-peer network 330 providing a roaming opportunity by means of the peer-to-peer application 332. It is noted that for sake of clarity only one node 336 is depicted. It shall be understood that the peer-to-peer network 330 comprises a plurality of nodes.

(31) Furthermore, a first peer-to-peer module 338.1 assigned to a first gateway device 310.1, a second peer-to-peer module 338.2 assigned to a second gateway device 310.2 and a third peer-to-peer module 338.3 assigned to a third gateway device 310.3 are provided. Each of the peer-to-peer modules 338.1, 338.2, 338.3 may be configured to communicate with the nodes 336 of the peer-to-peer network 330.

(32) In addition, a storage arrangement 344 controlled by the peer-to-peer application 332 is provided. Data can be stored in the peer-to-peer application 332 and/or in a storage arrangement 344 controlled by the peer-to-peer application 332. Preferably, the storage arrangement 344 comprising a plurality of decentral storage units 346 may be formed as a decentral file system (such as IPFS) or a decentral object store (such as storj) or a decentral distributed database (such as BigchainDB) controlled by the peer-to-peer application 332. For instance, details about all registered entities can be stored in the storage arrangement 344. Further, according to other variants of the present invention, a (not shown) off-chain computing device controlled by the peer-to-peer application 332, e.g. the roaming controlling means 334, can be provided e.g. for conduction an accounting action or creating a charging control message or the like. Algorithms, cognitive analytics, machine learning and/or artificial intelligence can be operated in an off-chain or edge device to optimize the exchanging process, in particular, the charging process from a grid and/or a fleet perspective.

(33) In an embodiment of the roaming system analysis of preferably all (to the peer-to-peer application known) charging transaction(s) and external data provided by a so called oracles (e.g. weather traffic conditions, etc.) to generate a charging demand forecast. This forecast can be exchanged with a grid control or SCADA device to improve operations of the underlying electrical grid system and/or generate control data sets or input for dynamic pricing algorithm(s). In a further embodiment the grid control or SCADA device may create this forecast by analyzing transactions in the peer-to-peer application.

(34) In a fleet management system analysis the transaction(s) of vehicles belonging to a fleet in order to optimize the fleet and/or create control data set(s). Control data set(s) can be exchanged between roaming system, fleet management system and grid control/SCADA device to further optimize the grid and/or a fleet.

(35) By way of example, an identifier list of all registered vehicles and/or users of devices, in particular, vehicles and/or charging station can be stored in the storage arrangement 344. During an authentication action (as will be described in more details hereinafter), a received peer-to-peer identifier can be compared by the peer-to-peer application 332 with the stored identifiers in the identifier list. If the peer-to-peer application 332 detects an identifier corresponding to the received peer-to-peer identifier a charging action and/or a further roaming action can be enabled. For instance, a release or lock message (depending on the authentication result) can be provided by the peer-to-peer application 332 to the corresponding gateway device 310, i.e. the gateway device 310 which has previously sent the charging data set to the peer-to-peer-application 332. Said gateway device 310 may forward the information to the charging station in order to release the supply (or receipt) of electrical power to (or from) a vehicle. In an embodiment said gateway device 310 can exchange message(s) with gateway device(s) of grid SCADA device(s), identity or vehicle fleet management systems.

(36) In addition, a grid monitoring entity 348 may be provided. The grid monitoring entity 348 may be configured to monitor the electrical grid. For instance, grid parameters, such as a grid frequency, grid voltage and/or grid current can be monitored e.g. at one or more measuring locations at the grid. Based on the (continuously) measured one or more grid parameter(s) a grid status data set can be generated by the grid monitoring entity 348. There may be several grid status data set(s) for different grid location areas.

(37) The grid status data set may be provided from a peer-to-peer module 350 assigned to the grid monitoring entity 348 to the peer-to-peer application 332. The peer-to-peer application may be configured to create set power data set(s) and may transmit one or more set power data set(s) to connected gateway devices 310.1, 310.2, 310.3. The one or more gateway device(s) 310.1, 310.2, 310.3 may forward a received set power data set to one or more connected charging station (e.g. also depending on the grid location area associated with the respective grid status data set). The charging station(s) may be configured to allow charging/discharging actions only within the power (and/or current limit(s)) set by the received set power data set. In an embodiment the controlling of charging/discharging actions may be based on dynamic pricing points and information, respectively.

(38) It may be also possible that the grid monitoring entity 348 may be configured—eventually in accordance to terms defined in a smart contract—to generate the set power data set(s). In this case, the roaming peer-to-peer network and its peer-to-peer application may (only) forward the one or more set power data set(s) to the respective one or more gateway devices. It shall be understood that the roaming system may only comprise a peer-to-peer application including users, vehicles, charging stations and devices and a grid monitoring system.

(39) FIG. 4 shows a further embodiment of a charging system according to the present invention. In order to avoid repetition, it is referred to the above described embodiments. In addition, the following is noted.

(40) The two exemplified charging stations 404.1 are connected with the electrical grid. By closing a switch 466, an electrical connection between the electrical source (grid) of the charging station 404.1 and the vehicle 454, 456 via a charging cable 458 (or via an inductive charging connection) can be established. As described above, prior to closing the switch 466 for enabling charging/discharging an authentication action might be necessary. For instance, a (vehicle) identifier, in particular, in form of a peer-to-peer identifier can be transmitted from a storage unit 460 of the vehicle 454 via the charging cable 458 to the charging station 404.1. Alternatively, a (user) identifier in form of a peer-to-peer identifier can be transmitted to a nearfield interface 468 (e.g. Bluetooth, NFC, infrared or WLAN interface) from a storage unit 464 of a mobile terminal 462 (e.g. mobile phone, tablet computer, smart watch, etc.). In another embodiment the peer-to-peer identifier may be transmitted from a device inside a vehicle or is retrieved from the peer-to-peer application (e.g. ID or Wallet on Blockchain).

(41) The charging station 404.1 may transmit a received peer-to-peer identifier to the roaming peer-to-peer network 430 via the gateway device 410.1. The roaming controlling means may e.g. conduct the authentication action based on the received peer-to-peer identifier and stored authorized peer-to-peer identifiers. The authentication result can be transmitted to the respective charging station 404.1 via the gateway device. Based on the received authentication result (positive or negative) the switch 466 may be closed (positive result) or not (negative result).

(42) Furthermore, as can be seen from FIG. 4, a further gateway device 410.2 of a further subsystem 402.2 may be also a node 436.2 of the peer-to-peer network 430. For instance, the gateway device 410.2 may have one or more powerful processors. In this case, the processing power provided can also be used by the peer-to-peer application 432, e.g. the roaming controlling means 434.

(43) FIG. 5 shows a schematic view of an embodiment of a peer-to-peer application 532 according to the present invention.

(44) The depicted peer-to-peer application 532 is a register or distributed ledger readable, in particular, by the participants of the peer-to-peer network. Thereby, data set(s) e.g. in form of messages can be written and/or read into/from the register 532 by a peer-to-peer module assigned to a gateway device and/or any other participants in the peer-to-peer network. In a preferred embodiment, the peer-to-peer application 532 may be a block chain 532.

(45) Hereinafter, it is assumed in the following description of the present embodiment that the at least one peer-to-peer application 532 is a block chain 532. However, the following remarks can be easily transferred to other peer-to-peer applications, such as a Directed Acyclic Graph (DAG). A directed acyclic graph, such as IOTA or Tangle, means that blocks (or nodes of the graph) are coupled to each other via directed edges. Thereby, direct means that the (all) edges have (always) a same direction similar to time. In other words, it is not possible to step back. Eventually, acyclic means that loops do not exist.

(46) In further embodiments of the peer-to-peer application the block chain can be a permissionless or permissioned block chain. In a specific case the block chain can be public, consortium or private block chain.

(47) In a further embodiment, the peer-to-peer application can be formed with multiple block chains which are connected via mechanisms such as side chains or smart contracts. Interoperability among block chains can be established.

(48) The block chain 532 is formed by at least one block 551, 553, 555, preferably by a plurality of interconnected blocks 551, 553, 555. The first block 451 may also be called genesis block 551. As can be seen, a block 553, 555 (except for the first block 551) refers to each previous block 551, 553. A new block can be created by a computationally intensive process (for example, so called “mining” or through another appropriate process, such as voting) and will be particularly provided to all participants of the peer-to-peer network. In a further embodiment a (centrally controlled) master or a set of master nodes node may be configured to create new blocks and/or validating transactions. All other nodes can be validation nodes only.

(49) The present block chain 532 is particularly adapted to receive messages, such as messages comprising charging data set(s) and/or set data set(s), registering data, authentication result(s), etc., from a peer-to-peer module of a previously described gateway device, (off-chain) computing entity or from another peer-to-peer device/unit of another participant of the peer-to-peer network. Further, the block chain 532 is particularly adapted to save these messages in the block chain 532. Furthermore, the block chain 532 is configured to generate messages e.g. based on an roaming process/action, an authentication or authorization process and/or caused by a peer-to-peer module and/or the execution of code of e.g. a roaming controlling means 534. In particular, the block chain 532 is at least configured to control and manage an inlet and/or outlet system, such as shown in FIG. 2, 3 or 4.

(50) In particular, a (newly) received message can be saved and published in the current block 555 of the block chain 532. Due to the configuration of a block chain 532 as a public register 532, said data message of e.g. a peer-to-peer module can be read by preferably all participants of the peer-to-peer network. Alternatively or additionally, data of a message may be stored on a decentral file service or distributed block chain database controlled by the block chain 532.

(51) As already described, in the present block chain 532 different types of messages and data sets, respectively, for example, within a smart contract (algorithm and/or storage at the block chain 532) can be processed and/or stored. In the present example, the block chain 532 comprises a roaming controlling means 534 in form of a smart contract 534. As previously described the roaming controlling means may be configured to at least control at least one roaming process comprising authentication action(s), forwarding action(s) and/or accounting action(s).

(52) Furthermore, in the block chain 532 one or more roaming transaction agreement(s) 574 may be stored. A roaming transaction agreement 574 may be generated between two (or more) subsystems in order to define the details of roaming process(es). An example of a generation of such a roaming transaction agreement 574 will be described in the following:

(53) A roaming transaction agreement 574 may comprise at least one of the following data: Identifier(s): One or more identifier(s) of the involved entities, such as subsystem identifiers of the subsystems, identifiers of the charging station(s), gateway device(s), etc. Roaming transaction criterion: Criterion that must be fulfilled for conducting a roaming process Roaming detail(s): Detail(s) about roaming process(es) (e.g. roaming algorithm(s), registering rule(s)

(54) The roaming transaction criterion may be e.g. an amount of cryptocurrency e.g. per charging action or charged/discharged energy amount which has to be transferred prior to, during and/or after the roaming action(s). Preferably, at least a part of the agreed amount of cryptocurrency can be locked by the peer-to-peer application 532 prior to a roaming action. In an embodiment the roaming transaction criterion may be a payment channel for streaming small amounts of crypto tokens per each time and/or data unit. It shall be understood that other transaction criteria and further information can be included in an roaming transaction agreement. More information/criteria can be, for example, a time stamp, an ID of the transaction and the like.

(55) In order to generate a roaming transaction agreement 574, a peer-to-peer module of a provider entity of a first subsystem and a peer-to-peer module of a provider entity of a further subsystem can exchange roaming request and response (acceptance) messages via the peer-to-peer application 574. A request message may comprise indications about the above data (identifications, transaction criteria).

(56) For instance, a provider entity of a first subsystem can send by a peer-to-peer module a (offer) message 576 to the peer-to-peer application 532 comprising data, such as an identifier assigned to the provider, available gateway devices and/or charging stations, geographic coordinates of the charging stations, identifier(s) of the charging stations, roaming algorithm(s) and/or at least one roaming transaction criterion.

(57) Another message 578 may be an acceptance message 578 of e.g. one or more further provider entities. An acceptance message 578 may comprise identical or at least similar data details as compared with a (offer) message 576. Additionally, the acceptance message 578 can comprise a reference indication to a previous message, such as the ID of the message 576. The acceptance message 578 can be provided by a further peer-to-peer module of a provider entity or by the peer-to-peer application (e.g. according to preset rules).

(58) If, for example, the acceptance message 578 comprises a higher or other transaction criterion and/or other desired roaming algorithms, the acceptance/request message 578 can be called a counter-offer message. This can be accepted by the peer-to-peer module of the first provider entity through an acceptance message. Based on this a peer-to-peer module of an entity may cause the generation of a roaming transaction agreement 574 about one or more roaming process(es). For instance, the roaming transaction agreement 574 can be used for every roaming process in which charging stations and/or gateway devices of the respective subsystems are involved.

(59) In particular, there can be multiple offer messages and/or request/accepting messages and/or messages. Each entity can give guidelines, according to which at least one roaming transaction agreement 574 or other agreements can be generated. In a preferably automated, such as iterative process, each request/offer message can be associated to an optimally corresponding acceptance message. The block chain 532 may be configured to generate, based on the messages of a peer-to-peer module, an roaming transaction agreement 574.

(60) Further, the roaming controlling means 534 may be configured to control at least one roaming action (and/or user) based on the one or more roaming transaction agreement(s) 574. The roaming controlling means 534 may be executed by at least part of the nodes of the peer-to-peer network for conducting a roaming action. For instance, based on a received peer-to-peer identifier and stored peer-to-peer identifiers of authorized users and/or vehicles, the peer-to-peer application 532, in particular, the roaming controlling means 534 may allow the conduction of a charging action. Only in the case the received identifier corresponds to one of the stored identifier, a positive authentication result can be transmitted to the respective charging for releasing the power flow between charging station and vehicle.

(61) Moreover, a block chain 534 may comprise a registration means 580 configured to register a (new) gateway device, charging station, vehicle, user, electrical device, fleet management system, central identification device, payment gateway, SCADA and/or grid control device, etc. in the block chain 534 as a smart asset or an individual user.

(62) FIG. 6 shows a schematic view of another embodiment of a charging system 600 of the invention. In the present embodiment only nodes and participants 610.1, 610.2, 636.1, 636.2, 654.2, 662.2 of the peer-to-peer network 630 are shown. In the present example, it is assumed that all nodes participants 610.1, 610.2, 636.1, 636.2, 654.2, 662.2 comprise the peer-to-peer application (not shown).

(63) The nodes 610.1, 610.2 may correspond to gateway devices and e.g. be formed by the respective peer-to-peer modules of gateway devices. The node 654.2 may be a vehicle realized by a peer-to-peer module of a vehicle, and 662.2 may be a mobile terminal. Nodes 636.1 and 636.2 may be other nodes. It shall be understood that nodes can be full, remote or light nodes. In further embodiments the nodes can comprise a central ID device with a peer-to-peer module, a SCADA or grid control device with a peer-to-peer module, a vehicle fleet management system and/or a payment gateway with ID registry, customer account management and/or a fiat/crypto token exchange service.

(64) As can be seen, two different types of peers or node computers 610.1, 610.2, 636.1, 636.2, 654.2, 662.2 are presently illustrated. All peers 610.1, 610.2, 636.1, 636.2, 654.2, 662.2 are comprised by the peer-to-peer network 630. In the present embodiment, however, only a part of the peers 610.1, 610.2, 636.1, 636.2, 654.2, 662.2 in the present case, the peers (nodes) 610.1, 636.1, check the validity of e.g. a roaming process, e.g. an authentication action, a forwarding action, accounting action and/or further data stored in the peer-to-peer application messages, such as agreements, instructions data set messages, and the like.

(65) Furthermore, only a part of the entire peers can be configured to store the peer-to-peer application and/or only a part of the peers can be configured to execute the algorithms of a smart/private contract. Since the validation/verification of e.g. identification data requires a considerable computational effort, it may be advantageous for reasons of efficiency, if only a part of the peers 610.1, 636.1, especially particularly powerful peers 610.1, 636.1, perform the validation and/or roaming controlling algorithms.

(66) Validation, analytics and optimization can be done on-chain or off-chain, as described hereinbefore. Off-chain validation and/or optimization can be managed by the peer-to-peer application, like the code on the block chain. Powerful means in particular a high computing power. In other words, in the present case a valid entry in the peer-to-peer application, such as a block chain, is assumed if (only) a part of the peers 610.1, 636.1 comes to a positive result. It shall be understood that only a single, especially particularly powerful peer can perform the validation, analytics and/or optimization process.

(67) Similarly, in an alternative (not shown) embodiment, a particularly large peer-to-peer network may be divided in two or more clusters. In a corresponding peer-to-peer network, for example, a validation will only be carried out by the members of one cluster (e.g. sharding of a block chain to improve the scalability). In a further embodiment the peer-to-peer application can be formed using multiple block chains. These block chains are connected via frameworks such as sidechains or smart contracts or interlegder.

(68) FIG. 7 shows an embodiment of a roaming method according to the present invention. The method can be used for operating a previously described charging system.

(69) In a first step 701, a first roaming action in form of an authentication action can be at least controlled by roaming controlling means. For instance, a received charging data set can comprise a peer-to-peer identifier of a vehicle (or user) which desires to conduct a charging action. The received peer-to-peer identifier can be compared with stored authorized peer-to-peer identifiers of a list (by means of the roaming controlling means). Only if a match can be found the authentication result is positive. Alternatively or additionally the authentication step can check whether an escrow payment is done or a real-time payment streaming connection (payment channel) is established. The authentication result can be transmitted from the peer-to-peer application via the respective gateway device and the respective charging station.

(70) In a next step 702, upon a positive authentication result the charging/discharging action can be conducted. For instance, a current can flow from the charging station to the vehicle and its battery for a specific time period. In case of a payment channel the decentral application (DAPP) of a charging entity may check whether the payment stream is continuing in accordance to the charged energy. In case the payment stream is interrupted the transfer of energy will be interrupted or reduced accordingly.

(71) After the charging action has been finished, a charging data set can be transmitted from the charging station to the gateway device. For instance, the charging station may transmit a charging data set comprising a subsystem identifier and charging amount information, e.g. the power supplied to the vehicle during the charging action.

(72) Based on the subsystem identifier, a routing module of the gateway device may forward the received charging data set in step 704. For instance, if the received subsystem identifier is assigned to the subsystem of said gateway device the gateway device may forward the charging data set to the connected server e.g. for accounting the charging amount information (step 705). If the received identifier indicates another subsystem the charging data set may be forwarded to the peer-to-peer application by means of the peer-to-peer module assigned to the gateway device.

(73) In step 706, the peer-to-peer application, in particular, the roaming controlling means, check, in particular, based on roaming algorithm(s) of a roaming transaction agreement whether the received charging data set should be forwarded (step 707), and if, to which further gateway device, or whether an accounting action should be conducted by the peer-to-peer application (step 708). The further gateway device may forward the received charging data set to the connected further server in step 707. Then, the further server may process the charging data set, e.g. may conduct an accounting action (step 709).

(74) In each accounting step 705, 708, 709, the respective accounting means may conduct the accounting action based on stored user data (including accounting data) and the received charging amount information and a peer-to-peer identifier (for assigning the received charging amount information to the correct user data).

(75) It shall be noted that the method can comprise further steps, such a registering step, roaming criterion transaction step, generation step of a roaming transaction agreement, etc. Further, it shall be understood that at least some of the steps can also be conducted at least partly in parallel. For instance, a charging action can be started prior to receiving an authentication result. Then, in dependence on the received authentication result, the charging action can be prosecuted or interrupted/stopped.

(76) All references, including publications, patent applications, and patents cited herein are hereby incorporated by reference to the same extent as if each reference were individually and specifically indicated to be incorporated by reference and were set forth in its entirety herein.

(77) The use of the terms “a” and “an” and “the” and similar referents in the context of describing the invention (especially in the context of the following claims) is to be construed to cover both the singular and the plural, unless otherwise indicated herein or clearly contradicted by context. The terms “comprising,” “having,” “including,” and “containing” are to be construed as open-ended terms (i.e., meaning “including, but not limited to,”) unless otherwise noted. Recitation of ranges of values herein are merely intended to serve as a shorthand method of referring individually to each separate value falling within the range, unless otherwise indicated herein, and each separate value is incorporated into the specification as if it were individually recited herein. All methods described herein can be performed in any suitable order unless otherwise indicated herein or otherwise clearly contradicted by context. The use of any and all examples, or exemplary language (e.g., “such as”) provided herein, is intended merely to better illuminate the invention and does not pose a limitation on the scope of the invention unless otherwise claimed. No language in the specification should be construed as indicating any non-claimed element as essential to the practice of the invention.

(78) Preferred embodiments of this invention are described herein, including the best mode known to the inventors for carrying out the invention. Variations of those preferred embodiments may become apparent to those of ordinary skill in the art upon reading the foregoing description. The inventors expect skilled artisans to employ such variations as appropriate, and the inventors intend for the invention to be practiced otherwise than as specifically described herein. Accordingly, this invention includes all modifications and equivalents of the subject matter recited in the claims appended hereto as permitted by applicable law. Moreover, any combination of the above-described elements in all possible variations thereof is encompassed by the invention unless otherwise indicated herein or otherwise clearly contradicted by context.