Electric vehicle charging session data management

Abstract

According to an example embodiment, there is provided a back-end system for managing and providing charging session data. The back-end system may obtain, from a receipt portal apparatus, information identifying an electric vehicle charging station; initiate a receipt retrieval session in response to receiving the information identifying the electric vehicle charging station; receive a charging transaction request associated with the electric vehicle charging station, the charging transaction request comprising data associated with a payment card; determine that there is an existing receipt retrieval session associated with the electric vehicle charging station; determine partial payment card data based on the data associated with the payment card; determine, from a charge data storage, charging session data associated with a user based at least in part on the partial payment card data, the charge data storage storing charging event data associated with at least one user, the charging event data associated with a user comprising prior charging session data relating to at least one charging session in at least one the electric vehicle charging station and partial payment card data associated with the user; and provide at least part of the charging session data associated with the user.

Description

[0001] ELECTRIC VEHICLE CHARGING SESSION DATA MANAGEMENT TECHNICAL FIELD

[0002] The present disclosure generally relates to electric vehicle charging stations and their management . In particular, the present disclosure relates to a solution for managing and providing charging session data relating to charging sessions provided by electric vehicle charging stations .

[0003] BACKGROUND

[0004] Electric vehicles are charged using charging stations that generally require a customer to register an account with an electric mobility service provider and use a mobile application or a radio frequency identification (RFID) card provided by the various service providers . Some charging stations have a physical card payment terminal that enables electric vehicle drivers to pay for the charging directly using a physical card . Thi s al so removes the need to regi ster an account with the service provider and the need to use mobile appli cations .

[0005] However, a standard has not yet been defined on how the physical card payment terminals work for the charging stations , and as hundreds of different charging station manufacturers have their own proprietary way to handle physical card payments , it becomes difficult for the customer to obtain charging receipts without using the applications provided by the service providers .

[0006] As many charging station manufacturers or their service providers have not implemented methods to provide receipts of the charging events , for example , with receipt printers , the service providers have focused on providing the receipts of the charging events via the service provider specific mobile applications .

[0007] Furthermore , if a customer has not registered with the service providers directly, unregistered customers may not have a way to acquire the receipts associated with the charging events .

[0008] SUMMARY

[0009] The scope of protection sought for various example embodiments of the disclosure is set out by the independent claims . The example embodiments and features , i f any, described in this specification that do not fall under the scope of the independent claims are to be interpreted as examples useful for understanding various example embodiments of the disclosure .

[0010] The disclosure herein provides apparatuses , a system, methods and a computer programs for managing customer information and charging event information of electric vehicles on any existing charging station, and providing a driver of an electric vehicle the possibility to acquire charging event information without registering with an electric mobility provider and using their own proprietary application .

[0011] According to a first aspect , there is provided a back-end system for managing and providing charging session data . The back-end system comprises at least one processor and at least one memory including program code . The at least one memory with the program code are configured to , when executed by the at least one processor, cause the back-end system to at least to : obtain, from a receipt portal apparatus , information identifying an electric vehicle charging station ; initiate a receipt retrieval session in response to receiving the information identifying the electric vehicle charging station ; receive a charging transaction request associated with the electric vehicle charging station, the charging transaction request comprising data associated with a payment card; determine that there is an existing receipt retrieval session associated with the electric vehicle charging station ; determine partial payment card data based on the data associated with the payment card; determine , from a charge data storage , charging session data associated with a user based at least in part on the partial payment card data , the charge data storage storing charging event data associated with at least one user, the charging event data associated with a user comprising prior charging session data relating to at least one charging session in at least one the electric vehicle charging station and partial payment card data as sociated with the user ; and provide at least part of the charging session data associated with the user .

[0012] In an implementation form of the first aspect , the at least one memory with the program code are configured to , when executed by the at least one proces sor, cause the back-end system at least to transmit the at least part of the charging session data associated with the user to the receipt portal apparatus .

[0013] In an implementation form of the first aspect , the data associated with the payment card comprises a monetary transaction identifier, and wherein the at least one memory with the program code are configured to , when executed by the at least one processor, cause the back-end system at least to determine the partial payment card data based on the monetary transaction identifier .

[0014] In an implementation form of the first aspect , the at least one memory with the program code are configured to , when executed by the at least one proces sor, cause the back-end system at least to obtain, from the receipt portal apparatus , an email address ; and transmit the at least part of the charging sess ion data associ ated with the user to the email address .

[0015] In an implementation form of the first aspect , the at least one memory with the program code are configured to , when executed by the at least one proces sor, cause the back-end system at least to obtain, from the receipt portal apparatus , an indication to receive future receipts via email ; link the email address with the partial payment card data associated with the user ; and transmit the at least part of the charging session data associated with the user to the email address .

[0016] In an implementation form of the first aspect , the at least one memory with the program code are configured to , when executed by the at least one proces sor, cause the back-end system at least to obtain, from the receipt portal apparatus , an indication to receive a periodical summary of charging session data ; link the email address with the partial payment card data associated with the user ; and transmit the at least part of the charging session data associated with the user to the email address periodically .

[0017] In an implementation form of the first aspect , the at least one memory with the program code are configured to , when executed by the at least one proces sor, cause the back-end system at least to obtain, from the receipt portal apparatus , an indication to stay logged in ; generate a login token in response to obtaining the indication, the login token comprising a unique identifier ; link the login token with the partial payment card data associated with the user ; and transmit the login token to the receipt portal apparatus .

[0018] In an implementation form of the first aspect , the at least one memory with the program code are configured to , when executed by the at least one proces sor, cause the back-end system at least to obtain, from the receipt portal apparatus , the login token ; determine , from the charge data storage , the partial payment card data linked to the login token; determine , based on the partial payment card data, charging session data associated with a user ; and transmit the charging session data to the receipt portal apparatus .

[0019] In an implementation form of the first aspect , the at least one memory with the program code are configured to , when executed by the at least one proces sor, cause the back-end system at least to generate a unique key as sociated with the user ; associate the unique key with the partial payment card data associated with the user ; and transmit an accessible link associated with the unique key to the receipt portal apparatus with the at least part of the charging session data associated with the user to the receipt portal apparatus .

[0020] In an implementation form of the first aspect , the at least one memory with the program code are configured to , when executed by the at least one proces sor, cause the back-end system at least to receive an indi cation that the link associated with the unique key has been accessed; determine , from the charge data storage , the partial payment card data linked to the unique key; determine , based on the partial payment card data, charging session data associated with a user ; and transmit the charging session data .

[0021] According to a second aspect , there is provided a receipt portal apparatus comprising at least one processor and at least one memory including program code . The at least one memory with the program code are configured to , when executed by the at least one proces sor, cause the back-end system to at least to : obtain information identifying an electric vehicle charging station ; transmit the information identifying the electric vehicle charging station to a back-end system to initiate a receipt retrieval session at the back-end system; receive , from the back-end system, at least part of charging ses sion data as sociated with the user ; and display the at least part of charging session data associated with the user via a graphical user interface .

[0022] In an implementation form of the second aspect , the at least one memory with the program code are configured to , when executed by the at least one proces sor, cause the receipt portal apparatus at least to provide , via the graphical user interface , an instruction to show a payment card at a payment terminal associated with the electric vehicle charging station .

[0023] In an implementation form of the second aspect , the at least one memory with the program code are configured to , when executed by the at least one proces sor, cause the receipt portal apparatus at least to request , via the graphical user interface , a user to input an email address in order to receive future receipts automatically; and transmit the email addres s to the back- end system .

[0024] In an implementation form of the second aspect , the at least one memory with the program code are configured to , when executed by the at least one proces sor, cause the receipt portal apparatus at least to transmit to the back-end system an indication to stay logged in ; receive a login token from the back-end system; and store the login token for subsequently obtaining charging session data associated with a user in a memory .

[0025] In an implementation form of the second aspect , the at least one memory with the program code are configured to , when executed by the at least one proces sor, cause the receipt portal apparatus at least to obtain the login token from the memory; transmit the login token to the back-end system; receive , from the back- end system, at least part of charging ses sion data as sociated with the user in response to transmitting the login token ; and di splay the at least part of charging session data associated with the user via the graphical user interface .

[0026] In an implementation form of the second aspect , the at least one memory with the program code are configured to , when executed by the at least one proces sor, cause the receipt portal apparatus at least to receive a link with the at least part of the charging session data associated with the user, the link enabling a subsequent access to the sess ion data associated with the user ; and display the link via the graphical user interface . In an implementation form of the second aspect , the at least one memory with the program code are configured to , when executed by the at least one proces sor, cause the receipt portal apparatus at least to access the link; in response to accessing the link, receive at least part of the charging session data associated with the user ; and display at least part of the charging session data associated with the user via the graphical user interface .

[0027] According to a third aspect , there is provided a system comprising a back-end system of the first as pect configured to be in communication with at least one electric vehicle charging station ; a receipt portal apparatus of the second aspect communicatively connected to the back-end system; and a charge data storage communicatively connected to the back-end system .

[0028] According to a fourth aspect , there is provided a method comprising : obtaining, from a receipt portal apparatus , information identifying an electric vehicle charging station ; initiating a receipt retrieval session in response to receiving the information identifying the electric vehicle charging station ; receiving a charging transaction request associated with the electric vehicle charging station, the charging transaction request comprising data associated with a payment card; determining that there is an existing receipt retrieval session associated with the electric vehicle charging station ; determining partial payment card data based on the data associated with the payment card; determining, from a charge data storage , charging session data associated with a user based at least in part on the partial payment card data, the charge data storage storing charging event data associated with at least one user, the charging event data as sociated with a user comprising prior charging session data relating to at least one charging session in at least one the electric vehicle charging station and partial payment card data associated with the user ; and providing at least part of the charging session data associated with the user .

[0029] According to a fifth aspect , there is provided a method comprising : obtaining information identifying an electric vehicle charging station ; transmitting the information identifying the electric vehicle charging station to a back-end system to initiate a receipt retrieval session at the back-end system; receiving, from the back-end system, at least part of charging sess ion data associated with the user ; and causing display of the at least part of charging session data associated with the user via a graphical user interface .

[0030] According to a sixth aspect , there is provided a computer program comprising program code configured to perform the method according to the f irst or second aspect , when the computer program is executed on a computer .

[0031] According to a seventh aspect , there is provided a computer-readable medium comprising a computer program comprising program code configured to perform the method according to the first or second aspect , when the computer program is executed on a computer .

[0032] According to an eighth aspect , there is provided a back-end system for managing and providing charging session data . The back-end system comprises means for : obtaining, from a receipt portal apparatus , information identifying an electric vehicle charging station ; initiating a receipt retrieval session in response to receiving the information identifying the electric vehicle charging station ; receiving a charging transaction request associated with the electric vehicle charging station, the charging transaction request comprising data associated with a payment card; determining that there is an existing receipt retrieval session associated with the electric vehicle charging station ; determining partial payment card data based on the data associated with the payment card; determining, from a charge data storage , charging session data associated with a user based at least in part on the partial payment card data, the charge data storage storing charging event data associated with at least one user, the charging event data as sociated with a user comprising prior charging session data relating to at least one charging session in at least one the electric vehicle charging station and partial payment card data associated with the user ; and providing at least part of the charging session data associated with the user .

[0033] According to a ninth aspect , there is provided a receipt portal apparatus compri sing means for : obtaining information identifying an electric vehicle charging station ; transmitting the information identifying the electric vehicle charging station to a back- end system to initiate a receipt retrieval session at the back-end system; receiving, from the back-end system, at least part of charging sess ion data associated with the user ; and causing display of the at least part of charging session data associated with the user via a graphical user interface . DESCRIPTION OF THE DRAWINGS

[0034] The accompanying drawings , which are included to provide a further understanding of the example embodiments and constitute a part of this specification, illustrate example embodiments and together with the description help to explain the principles of the example embodiments . In the drawings :

[0035] FIG . 1 illustrates a method for managing and providing charging session data according to an example embodiment .

[0036] FIG . 2 illustrates a method for providing charging session data according to an example embodiment .

[0037] FIG . 3 illustrates an example of a back-end system configured to practice one or more example embodiments .

[0038] FIG . 4 illustrates an example of a receipt portal apparatus configured to practice one or more example embodiments .

[0039] FIG . 5A illustrates a diagram for storing charging session data according to an example embodiment .

[0040] FIG . 5B illustrates a diagram for storing charging session data according to an example embodiment .

[0041] FIG . 5C illustrates a diagram for managing and providing charging session data according to an example embodiment .

[0042] FIG . 5D illustrates a diagram for managing and providing charging session data according to an example embodiment . FIG . 5E illustrates a diagram for managing and providing charging session data according to an example embodiment .

[0043] FIG . 5F illustrates a diagram for managing and providing charging session data according to an example embodiment .

[0044] FIG . 6 illustrates exemplary screenshots provided by the receipt portal .

[0045] FIG . 7 illustrates a diagram for managing and providing charging session data according to an example embodiment .

[0046] FIG . 8 illustrates a diagram for managing and providing charging session data according to an example embodiment .

[0047] FIG . 9 illustrates a diagram how a database architecture may be implemented to handle the data required by the back-end system and the receipt portal apparatus according to an example embodiment .

[0048] Like reference numerals are used to designate like parts in the accompanying drawings .

[0049] DETAILED DESCRIPTION

[0050] Reference will now be made in detail to example embodiments , examples of which are illustrated in the accompanying drawings . The detailed description provided below in connection with the appended drawings is intended as a description of the present examples and is not intended to represent the only forms in which the present disclosure may be constructed or utili zed . The description sets forth the functions of the example and the sequence of steps for constructing and operating the example . However, the same or equivalent functions and sequences may be accomplished by different example embodiments .

[0051] Example embodiments disclosed herein relate to managing charging session data relating to at least one charging session of at least one electric vehicle charging station, EVCS , and providing the charging session data to a driver of an electric vehicle .

[0052] Normally electric mobility service providers enable a provision of charging receipts via their mobile applications as most existing EVCSs with integrated payment terminals do not provide any receipts to users .

[0053] Further, some electric vehicle drivers may not prefer using an application or cannot register their credit cards to a system provided by the EVCS manufacturer or electric mobility provider . Some EVCS manufacturers may enable a payment via an integrate payment card terminal . However, there is no standard on how these integrated card payment terminals work, and there are hundreds of different EVCS manufacturers and they all have their own proprietary ways to implement the payment functionality . Many of the EVCS manufacturers have not implemented a way for providing receipts for payments done with the payment card terminals , and at the same time EVCSs do not have receipt printers or any other ways to provide electronic receipts . This means that the users may not even have the possibility of receiving receipts relating to their charging events .

[0054] The description and the claims set forth a solution that enables a user of an electric vehicle , when using a payment card for paying for a charging event , to obtain electronic receipts without a need to use any electric mobility service applications or registrate for a service . Furthermore , the description and claims set forth methods how apparatuses and systems are to be configured to execute the desired outcome .

[0055] FIG . 1 illustrates a method for managing and providing charging session data according to an example embodiment . The method may be implemented by a back-end system managing the charging session data .

[0056] At 100 , information identifying an electric vehicle charging station may be obtained from a receipt portal apparatus . The receipt portal apparatus may provide a receipt portal that enables a user to obtain receipts of charging sessions provided by at least one electric vehicle charging station .

[0057] At 102 , a receipt retrieval session may be initiated in response to receiving the information identifying the electric vehicle charging station . The information identifying the electric vehicle charging station may be , for example , a unique identifier of the station or a serial number of the station .

[0058] At 104 , a charging transaction request associated with the electric vehicle charging station may be received, the charging transaction request comprising data associated with a payment card . The charging transaction request may be received from the electric vehicle charging station, and the data associated with the payment card may compri se , for example , payment car data, partial payment card data or a monetary transaction identifier .

[0059] At 106 it may be determined that there is an existing receipt retrieval session associated with the electric vehicle charging station . The determination may be made based on the earlier obtained information identifying the electric vehicle charging station and the transaction request originating from the same electric vehicle charging station .

[0060] At 108 , partial payment card data may be determined based on the data associated with the payment card . The partial payment card data may have already been received from the electric vehicle charging station with the charging transaction request . Alternatively, if the charging transaction request included a monetary transaction identifier, the partial payment card data may be determined based on the monetary transaction identifier from a payment service provider .

[0061] At 110 , charging session data associated with a user may be determined from a charge data storage based at least in part on the partial payment card data . The charge data storage may store charging event data associated with at least one user, and the charging event data associated with a user may comprise prior charging session data relating to at least one charging session in at least one the electric vehicle charging station and partial payment card data associated with the user . In other words , the charge data storage stores data separately for each user , and the partial payment card data of the user is stored with each charging session data .

[0062] At 112 , at least part of the charging session data associated with the user may be provided . The at least part of the charging session data may refer, for example , to the latest charging session or to a plurality of charging sessions . In an example embodiment , the at least part of the charging session data associated with the user may be transmitted to the receipt portal apparatus for display to the user .

[0063] FIG . 2 illustrates a method for providing charging session data according to an example embodiment . The method may be implemented by a receipt portal apparatus providing a receipt portal .

[0064] At 200 , information identifying an electric vehicle charging station may be obtained . A user may have opened the receipt portal with his / her mobile device and identified the electric vehicle charging station to the receipt portal . In another example embodiment , the receipt portal may instruct the user to scan a QR code associated with the electric vehicle charging station .

[0065] At 202 , the information identifying the electric vehicle charging station may be transmitted to a back-end system to initiate a receipt retrieval session at the back-end system . Based on thi s information, the back-end system now knows that the user is located at the electric vehicle charging station . Additionally, the receipt portal may provide , via a graphical user interface , an instruction to show a payment card at a payment terminal associated with the electric vehicle charging station .

[0066] At 204 , at least part of charging session data associated with the user may be received from the back- end system . The charge data storage may store charging event data associated with at least one user, and the charging event data associated with a user may comprise prior charging session data relating to at least one charging session in at least one the electric vehicle charging station and partial payment card data associated with the user . In other words , the charge data storage stores data separately for each user, and the partial payment card data of the user is stored with each charging session data .

[0067] At 206 , the at least part of the charging session data associated with the user may be displayed via the graphical user interface . The at least part of the charging session data associated with the user may refer, for example , to the latest charging sess ion or to a plurality of charging sessions associated with the user .

[0068] FIG . 3 illustrates an example of a back-end system 300 configured to practice one or more example embodiments . The back-end system 300 may comprise a computer, a server, or in general a device configured to implement functionality described herein, for example , the functionality discussed relating to FIG . 1 . The back-end system 300 may comprise at least one processor 302 . The at least one processor 302 may comprise , for example , one or more of various processing devices , such as for example a co-processor, a microprocessor, a controller, a digital signal processor ( DSP) , a processing circuitry with or without an accompanying DSP, or various other processing devices including integrated circuits such as , for example , an application specific integrated circuit (AS IC) , a field programmable gate array ( FPGA) , a microcontroller unit (MCU) , a hardware accelerator, a special-purpose computer chip, or the like .

[0069] The back-end system 300 may further comprise at least one memory 304 . The memory 304 may be configured to store , for example , computer program code or the like, for example operating system software and application software. The memory 304 may comprise one or more volatile memory devices, one or more non-volatile memory devices, and / or a combination thereof. For example, the memory may be embodied as magnetic storage devices (such as hard disk drives, magnetic tapes, etc.) , optical magnetic storage devices, or semiconductor memories (such as mask ROM, PROM (programmable ROM) , EPROM (erasable PROM) , flash ROM, RAM (random access memory) , etc.) . The memory 304 is provided as an example of a (non-transi- tory) computer readable medium. The term "non-transi- tory, " as used herein, is a limitation of the medium itself (i.e., tangible, not a signal ) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM) .

[0070] The back-end system 300 may further comprise a communication interface 308 configured to enable the back-end system 300 to transmit and / or receive information .

[0071] When the back-end system 300 is configured to implement some functionality, some component and / or components of the back-end system 300, such as for example the at least one processor 302 and / or the at least one memory 304, may be configured to implement this functionality. Furthermore, when the at least one processor 302 is configured to implement some functionality, this functionality may be implemented using program code 306 comprised, for example, in the at least one memory 304.

[0072] The functionality described herein may be performed, at least in part, by one or more computer program product components such as software components. According to an example embodiment, the back-end system 300 comprises a processor or processor circuitry, such as for example a microcontroller, configured by the program code 306 , when executed, to execute the embodiments of the operations and functionality described herein . The program code 306 i s provided as an example of instructions which, when executed by the at least one processor 302 , cause performance of the back-end system 300 .

[0073] Alternatively, or in addition, the functionality described herein can be performed, at least in part , by one or more hardware logic components . For example , and without limitation, illustrative types of hardware logic components that can be used include field-programmable gate arrays (FPGAs ) , application-specific integrated circuits (AS ICs ) , application-specific standard products (ASSPs ) , system-on-a-chip systems ( SOCs ) , complex programmable logic devices (CPLDs ) , graphics processing units (GPUs ) , or the like .

[0074] The back-end system 300 may be configured to perform method ( s ) described herein or comprise means for performing method ( s ) described herein . In one example , the means may compri se the at least one processor 302 , the at least one memory 304 including program code 306 configured to , when executed by the at least one processor 302 , cause the back-end system 300 to perform the method ( s ) .

[0075] Although the back-end system 300 is illustrated as a single device , it is appreciated that , wherever applicable , functions of the back-end system 300 may be distributed to a plurality of devices .

[0076] FIG . 4 illustrates an example of a receipt portal apparatus 400 configured to practice one or more example embodiments . The receipt portal apparatus 400 may comprise a computer, a server, or in general a device configured to implement functionality described herein, for example, the functionality discussed relating to FIG. 2. The receipt portal apparatus 400 may comprise at least one processor 402. The at least one processor 402 may comprise, for example, one or more of various processing devices, such as for example a co-processor, a microprocessor, a controller, a digital signal processor (DSP) , a processing circuitry with or without an accompanying DSP, or various other processing devices including integrated circuits such as, for example, an application specific integrated circuit (ASIC) , a field programmable gate array (FPGA) , a microcontroller unit (MCU) , a hardware accelerator, a special-purpose computer chip, or the like.

[0077] The receipt portal apparatus 400 may further comprise at least one memory 404. The memory 404 may be configured to store, for example, computer program code or the like, for example operating system software and application software. The memory 404 may comprise one or more volatile memory devices, one or more non-volatile memory devices, and / or a combination thereof. For example, the memory may be embodied as magnetic storage devices (such as hard disk drives, magnetic tapes, etc.) , optical magnetic storage devices, or semiconductor memories (such as mask ROM, PROM (programmable ROM) , EPROM (erasable PROM) , flash ROM, RAM (random access memory) , etc.) . The memory 404 is provided as an example of a (non-transitory) computer readable medium. The term "non-transitory, " as used herein, is a limitation of the medium itself (i.e., tangible, not a signal ) as opposed to a limitation on data storage pers istency ( e . g . , RAM vs . ROM) .

[0078] The receipt portal apparatus 400 may further comprise a communication interface 408 configured to enable the receipt portal apparatus 400 to transmit and / or receive information .

[0079] When the receipt portal apparatus 400 is configured to implement some functionality, some component and / or components of the receipt portal apparatus 400 , such as for example the at least one processor 402 and / or the at least one memory 404 , may be configured to implement this functionality . Furthermore , when the at least one processor 402 is configured to implement some functionality, this functionality may be implemented using program code 406 comprised, for example , in the at least one memory 404 .

[0080] The functionality described herein may be performed, at least in part , by one or more computer program product components such as software components . According to an example embodiment , the receipt portal apparatus 400 comprises a processor or processor circuitry, such as for example a microcontroller, configured by the program code 406 , when executed, to execute the embodiments of the operations and functionality described herein . The program code 406 is provided as an example of instructions which, when executed by the at least one processor 402 , cause performance of the receipt portal apparatus 400 .

[0081] Alternatively, or in addition, the functionality described herein can be performed, at least in part , by one or more hardware logic components . For example , and without limitation, illustrative types of hardware logic components that can be used include field-programmable gate arrays (FPGAs ) , application-specific integrated circuits (AS ICs ) , application-specific standard products (ASSPs ) , system-on-a-chip systems ( SOCs ) , complex programmable logic devices (CPLDs ) , graphics processing units (GPUs ) , or the like .

[0082] The receipt portal apparatus 400 may be configured to perform method ( s ) described herein or comprise means for performing method ( s ) described herein . In one example , the means may comprise the at least one processor 402 , the at least one memory 404 including program code 406 configured to , when executed by the at least one processor 402 , cause the receipt portal apparatus 400 to perform the method ( s ) .

[0083] Although the receipt portal apparatus 400 is illustrated as a single device, it is appreciated that , wherever applicable , functions of the receipt portal apparatus 400 may be distributed to a plurality of devices .

[0084] FIGS . 5A and 5B illustrate a diagram for storing charging session data according to an example embodiment . When intending to charge an electric vehicle at an electric vehicle charging station 506 , a user 502 may present his / her payment card to a payment terminal 500 . The payment terminal 500 may validate 508 that the payment card can be used to pay for a charging session and start 510 the charging session on the electric vehicle charging station 504 , when the validation is successful . The electric vehicle charging station 504 then sends the charging session details 512 to a back-end system 300 . The charging session details may comprise charge details and a monetary transaction identifier issued by a payment service provider . Alternatively, the charging session details may comprise charge details and partial payment card data . The partial payment card data may comprise the following :

[0085] - BIN (Bank identification number) identifying the financial institution that issued the card

[0086] - Partial PAN ( Primary Account Number) , usually the last four digits of the PAN of the payment card

[0087] - Expiration year and month of the payment card

[0088] - a PAN fingerprint and payment card fingerprint .

[0089] I f only a monetary transaction identifier is sent form the electric vehicle charging station 500 , the back-end system may 300 fetch the partial payment card data from a payment service provider system .

[0090] The back-end system 300 links the partial payment card data and the charging session details associated with the user and stores the information to a charge data storage 506 . In other words , each charging session of a user is linked to the partial payment card data associated with the user . Even though FIG . 5B illustrates an example relating only to a single user and a single electric vehicle charging station 504 , the charge data storage 506 may store information relating to a plurality of users using a plurality of charging stations .

[0091] FIGS . 5C and 5D illustrate a diagram for managing and providing charging session data according to an example embodiment . When a user 502 wishes to have a receipt for a charging session or sessions , the user 502 may open a receipt portal provided by a receipt portal apparatus 400 either on a web portal or on a mobile application using a mobile device 520 . The receipt portal may as k the user 502 to identify 522 the electric vehicle charging station 504 where the user is at . In an example embodiment , this can be done by entering a unique electric vehicle charging station identi fier or by scanning a QR code show in an electric vehicle charging station screen or a sticker . In an example embodiment, the user action can be done at any electric vehicle charging station at any time . The electric vehicle charging station 504 may be the one that was used for charging or some other electric vehicle charging station . Additionally, the user action can be performed at any time , also days or weeks after charging . When the electric vehicle charging station 504 has been identified, the receipt portal may send 524 an indication of a new receipt retrieval session for the electric vehicle charging station 504 to the back-end system 300 .

[0092] At 526, the receipt portal may ask the user to present a payment card to the payment terminal 500 associated with the electric vehicle charging station 504 . The payment terminal 500 validates 528 the payment card and sends the transaction and partial payment card data to the electric vehicle charging station 504 . The electric vehicle charging station 504 sends 530 the partial payment card data or a monetary transaction identifier to the back-end system 300 . Normally, the back-end system 300 would start a new charging transaction . However, instead of starting a new charging transaction, the back-end system 300 detects 532 that there is an existing receipt retrieval session associated with the electric vehicle charging station 504 , and due to this , the back-end system 300 does not authori ze the start of a new charging transaction on the electric vehicle charging station 504 .

[0093] At 534 , the back-end system may determine the partial payment card data . In an example embodiment , the partial payment card data was already received from the electric vehicle charging station 504 at 530 . In another example embodiment , if the transaction information at 530 included the monetary transaction identifier, the back-end system 300 may be configured to retrieve the partial payment card data from a payment service provider using the monetary transaction identifier .

[0094] The back-end system 300 may then link the partial payment card data to the receipt retrieval session to identify user . The back-end system 300 then determines 536 charging session data including one or more charging sessions paid with the same partial payment card data . The back-end system 300 then sends 538 the charging session data to the receipt portal apparatus 400 , and the receipt portal apparatus 400 displays 540 the charging session data via the receipt portal to the user . As a result , the user can see one or more receipts made with the given payment card . In an example embodiment , the receipt portal may provide only the receipt relating to the latest charging session . In another example embodiment , the receipt portal may provide receipts relating to the multiple charging sessions . For example , the receipt portal may provide receipts of charging sessions performed during the past month . The solution discussed above enables a solution in which a receipt retrieval is not tied to any specific electric vehicle charging station . Instead, any electric vehicle charging station can be used to start the receipt retrieval session .

[0095] FIG . 5E illustrates a diagram for managing and providing charging session data according to an example embodiment . The solution illustrated in FIG . 5E is similar to the one i llustrated in FIG . 5D . The difference is that the charging session data is sent in an email to the user of the mobile device 502 .

[0096] At 542 , the receipt portal instructs the user to input hi s / her email addres s via the receipt portal . Then at 544 , when the electric vehicle charging station 504 has been identified, the receipt portal may send 544 an indication of a new receipt retrieval session for the electric vehicle charging station 504 and the email address to the back-end system 300 . At 546 , the back-end system 300 may link the partial payment card data to the email address . At 548 , instead of providing the charging session data to the receipt portal apparatus 400 , the back-end system 300 may transmit the charging session data in an email to the mobile device 502 . In another example embodiment , the charging session data may be provided both by the receipt portal and the emai l sent to the mobile device 502 . The remaining steps of FIG . 5E have already been discussed with respect to FIG . 5D .

[0097] In an example embodiment , the receipt portal may ask at 542 whether the user would like to receive monthly summaries of charging sessions . I f the user provides the indication, the receipt portal apparatus 400 may transmit at 544 also the indication to the back-end system 300 , and the back-end system 300 stores the indication to the charge data storage 506 with the user' s email address . When the month then changes , the back- end system gathers 300 all charge session data linked to the email address and partial payment card data, creates a summary report of charging session data, and sends the summary report in an email to the user' s email address .

[0098] FIG . 5F illustrates a diagram for managing and providing charging session data according to an example embodiment . The solution illustrated in FIG . 5F is similar to the one i llustrated in FIG . 5D . The difference is that the user indicates an email address to which future receipts are to be automatically sent .

[0099] At 550 , the receipt portal displays the charging session data and also asks the user to provide an email address to which future receipts are to be automatically sent . At 552 , the receipt portal apparatus 400 sends the email address to the back-end system 300 , and at 554 , the back-end system 300 links the partial payment card data to the email address . Now the user' s email address is stored in the charge data storage 506 with the charging session data associated with the user, and future receipts may be automatically sent to the email address .

[0100] In an example embodiment , the receipt portal may ask at 550 whether the user would like to receive monthly summaries of charging sessions . I f the user provides the indication, the receipt portal apparatus 400 may transmit at 552 also the indication to the back-end system 300 , and the back-end system 300 stores the indication to the charge data storage 506 with the user' s email address . When the month then changes , the back- end system 300 gathers all charge session data linked to the email address and partial payment card data, creates a summary report of charging session data, and sends the summary report in an email to the user' s email address .

[0101] FIG . 6 illustrates exemplary screenshots provided by the receipt portal . The user 502 uses his / her mobile device 520 to access a receipt portal . The first screenshot 600 indicates that the receipt portal first as ks the user 502 to scan a QR code as sociated with an electric vehicle charging station or enter an electric vehicle charging station identifier via the receipt portal . The second screenshot 602 instructs the user 502 to show his / her payment card to the payment terminal associated with the electric vehicle charging station . The third screenshot 604 provides receipts relating to one or more charging session associated with the user 502 .

[0102] FIG . 7 illustrates a diagram for managing and providing charging session data according to an example embodiment . In an example embodiment , the steps illustrated in FIG . 7 may be performed after performing the steps illustrated in FIG . 5D .

[0103] When the charging session data is displayed by the charging portal to the user at 540 , the receipt portal may ask the user to confirm if the user wants to stay logged in and to show all future charging sess ion data, i . e . receipts , with the browser the user is using or a mobile application the user i s using . I f the user provides a confirmation to stay logged in at 700 , the receipt portal apparatus 400 at 702 sends an indication associated with the confirmation to the back-end system 300 . In response to the indication, the back-end system 300 generates at 704 a login token, which may comprise a JSON Web Token, JWT , or other similar token technol ogies . At 706 , the back-end system 300 associates to the login token with the partial payment card data of the user and stores the association to the charge data storage 506 .

[0104] At 708 , the back-end system 300 sends the generated login token to the receipt portal apparatus 400 . At 710 , the receipt portal apparatus 400 stores the login token to the browser or mobile application that that the user is using . Then, when the user later accesses the receipt portal again using the browser or the mobile application, the receipt portal checks if a login token is stored in the browser or the mobile application . I f there is , at 712 the receipt portal retrieves the stored login token, and at 714 sends the login token to the back-end system 300 . When using the login token, the receipt portal does not require the user to present a payment card on a payment card terminal to identify the user .

[0105] At 716 , the back-end system 300 determines the partial payment card data based on the received login token . At 718 , the back-end system 300 determines charging sess ion data from the charge data storage 506 , and at 720 sends the charging sess ion data to the receipt portal apparatus 400 . In an example embodiment , the charging ses sion data may include only the receipt relating to the latest charging session . In another example embodiment , the charging session data may include receipts relating to the multiple charging sessions . For example, the charging session data may include receipts of charging sessions performed during the past month, or all receipts stored in the charge data storage 506 for the user.

[0106] At 722, the receipt portal may display the charging session data received from the back-end system 300.

[0107] In the solution illustrated in FIG. 7, as the login token is anonymous, the user does not have to create a user account with a username and password, or provide any personal information in order to obtain charging session data.

[0108] FIG. 8 illustrates a diagram for managing and providing charging session data according to an example embodiment. The steps 800-804 may be performed by the back-end system 300 before the charging session data is sent at 538 to the receipt portal apparatus 400.

[0109] At 800, the back-end system 300 may generate a unique key, and at 802 the back-end system 300 may associate the unique key with the partial payment card data associated with the user in the charge data storage 506. At 804, the back-end system 300 may generate a link that includes the unique key. The link may be in the form of a web address, for example, https: / / chge.eu / re- ceipts / K29JsjO2iSi, where "K29JsjO2iSi" is the unique key linked to the partial payment card data of the user.

[0110] At 806, the back-end system 300 sends the link to the receipt portal apparatus 400. In an example embodiment, the link may be sent together with the charging session data at 538. At 808, the receipt portal may display the link to the user, for example, with the charging session data displayed at 540. The user may save the link for later access with the mobile device of the user, or with any other device. In other words, the later access via the link is not tied to any specific device .

[0111] At 810, the user may access the link using any device, for example, using a web browser of the mobile device 502. The link may refer to the receipt portal, and at 812 the receipt portal apparatus 812 sends a request for charging session data to the back-end system 300. The request includes the unique key. Based on the unique key, at 814 the back-end system 300 is able to find the matching partial payment card data and the charging session data linked to the partial payment card data from the charge data storage 506.

[0112] At 816, the back-end system 300 sends the charging session data to the receipt portal apparatus 400. The receipt portal apparatus 400 displays the charging session data at 818 via the receipt portal to the user. The user may be provided with the charging session data, i.e. the receipts, without having to authenticate again, simply by using a unique link generated when the receipt portal was used for the first time .

[0113] In an example embodiment, as an additional security option, expiration of the link may be enabled. For example, the link may be set to be valid only, for example, for 30 days or some other configurable time. In another example embodiment, the user may be able to set a password that is needed to open the link later. Even if somebody else would get access to the link, an additional password is needed to obtain the charging session data. FIG . 9 illustrates a diagram how a database 920 ( comprising the charge data storage 506 ) architecture may be implemented to handle the data required by the back-end system 300 and the receipt portal apparatus 400 according to an example embodiment . A monthly summary of report 900 of the charging events may comprise a plurality of charge session receipts 902 . Each charge session receipt may comprise one charge session information 904 , each charge session information 904 may have one associated charging station 906 . Each receipt retrieval session 908 may comprise one associated charging station 906 and one partial payment card detail 910 , i . e . partial payment card data .

[0114] Each login token 912 may have one partial payment card information 910 and each permanent link key 914 may have one partial payment card information 910 . Additionally, each monthly summary report requirement 916 may have one driver email address 918 , and each driver email address 918 may have one partial payment card information 910 .

[0115] One or more of the examples and embodiments discussed above may enable a secure solution as it only allows the payment card owners to see receipts . Further, one or more of the examples and embodiments discussed above may enable a solution that works with any electric vehicle charging station hardware from any vendor . This enables a provision of receipts on a different electric vehicle charging station where you charged . Further, one or more of the examples and embodiments discussed above may enable a solution that works at any location . A receipt may be provided from a different electric vehicle charging station than the one where you charged your electric vehicle . Further, one or more of the examples and embodiments discussed above may enable a solution that works at any time . It is possible to provide a receipt also relating to old charges , even if not remembering when and where exactly the charging was made . Further, one or more of the examples and embodiments discussed above may enable a solution in which, once the user has been identified in a web service or mobile application, it is possible to deliver optional functionalities like automatic receipt emails or monthly summary reports .

[0116] The operations of the methods described herein may be carried out in any suitable order, or simultaneously where appropriate . Additionally, individual blocks may be deleted from any of the methods without departing from the spirit and scope of the subj ect matter described herein . Aspects of any of the example embodiments described above may be combined with aspects of any of the other example embodiments described to form further example embodiments without losing the effect sought .

[0117] The term ' comprising ' is used herein to mean including the method, blocks or elements identified, but that such blocks or elements do not comprise an exclusive list and a method or apparatus may contain additional blocks or elements .

[0118] Any range or device value given herein may be extended or altered without losing the effect sought . Also , any example embodiment may be combined with another example embodiment unless explicitly disallowed .

[0119] Although the subj ect matter has been described in language specific to structural features and / or acts , it is to be understood that the subj ect matter defined in the appended claims is not necessarily limited to the specific features or acts described above . Rather, the specific features and acts described above are disclosed as examples of implementing the claims and other equivalent features and acts are intended to be within the scope of the claims .

[0120] It will be understood that the benefits and advantages described above may relate to one example embodiment or may relate to several example embodiments . The example embodiments are not limited to those that solve any or all of the stated problems or those that have any or al l of the stated benefits and advantages . It will further be understood that reference to ' an ' item may refer to one or more of those items .

[0121] It will be understood that the above description is given by way of example only and that various modif ications may be made by those s kil led in the art . The above specification, examples and data provide a complete description of the structure and use of exemplary embodiments . Although various example embodiments have been described above with a certain degree of particularity, or with reference to one or more individual example embodiments , those skilled in the art could make numerous alterations to the disclosed example embodiments without departing from the spirit or scope of thi s specification .

Claims

CLAIMS :

1. A back-end system (300) for managing and providing charging session data, the back-end system (300) comprising: at least one processor (302) ; at least one memory (304) including program code (306) ; wherein the at least one memory with the program code are configured to, when executed by the at least one processor, cause the back-end system (300) at least to: obtain, from a receipt portal apparatus (400) , information identifying an electric vehicle charging station (504) ; initiate a receipt retrieval session in response to receiving the information identifying the electric vehicle charging station (504) ; receive a charging transaction request associated with the electric vehicle charging station (504) , the charging transaction request comprising data associated with a payment card; determine that there is an existing receipt retrieval session associated with the electric vehicle charging station (504) ; determine partial payment card data based on the data associated with the payment card; determine, from a charge data storage (506) , charging session data associated with a user based at least in part on the partial payment card data, the charge data storage (506) storing charging event data associated with at least one user, the charging event data associated with a user comprising prior charging session data relating to at least one charging sessionin at least one the electric vehicle charging station (504) and partial payment card data associated with the user; and provide at least part of the charging session data associated with the user.

2. The back-end system (300) of claim 1, wherein the at least one memory with the program code are configured to, when executed by the at least one processor, cause the back-end system (300) at least to: transmit the at least part of the charging session data associated with the user to the receipt portal apparatus (400) .

3. The back-end system (300) of claim 1 or 2, wherein the data associated with the payment card comprises a monetary transaction identifier, and wherein the at least one memory with the program code are configured to, when executed by the at least one processor, cause the back-end system (300) at least to: determine the partial payment card data based on the monetary transaction identifier.

4. The back-end system (300) of any of claims 1 - 3, wherein the at least one memory with the program code are configured to, when executed by the at least one processor, cause the back-end system (300) at least to : obtain, from the receipt portal apparatus (400) , an email address; and transmit the at least part of the charging session data associated with the user to the email address.

5. The back-end system (300) of claim 4, wherein the at least one memory with the program code are configured to, when executed by the at least one processor, cause the back-end system (300) at least to: obtain, from the receipt portal apparatus (400) , an indication to receive future receipts via email ; link the email address with the partial payment card data associated with the user; and transmit the at least part of the charging session data associated with the user to the email address.

6. The back-end system (300) of claim 4, wherein the at least one memory with the program code are configured to, when executed by the at least one processor, cause the back-end system (300) at least to: obtain, from the receipt portal apparatus (400) , an indication to receive a periodical summary of charging session data; link the email address with the partial payment card data associated with the user; and transmit the at least part of the charging session data associated with the user to the email address periodically .

7. The back-end system (300) of any of claims 1 - 3, wherein the at least one memory with the program code are configured to, when executed by the at least one processor, cause the back-end system (300) at least to :obtain, from the receipt portal apparatus (400) , an indication to stay logged in; generate a login token in response to obtaining the indication, the login token comprising a unique identifier; link the login token with the partial payment card data associated with the user; and transmit the login token to the receipt portal apparatus (400) .

8. The back-end system (300) of claim 7, wherein the at least one memory with the program code are configured to, when executed by the at least one processor, cause the back-end system (300) at least to: obtain, from the receipt portal apparatus (400) , the login token; determine, from the charge data storage, the partial payment card data linked to the login token; determine, based on the partial payment card data, charging session data associated with a user; and transmit the charging session data to the receipt portal apparatus (400) .

9. The back-end system (300) of any of claims 2 - 3, wherein the at least one memory with the program code are configured to, when executed by the at least one processor, cause the back-end system (300) at least to : generate a unique key associated with the user; associate the unique key with the partial payment card data associated with the user; andtransmit an accessible link associated with the unique key to the receipt portal apparatus (400) with the at least part of the charging session data associated with the user to the receipt portal apparatus (400) .

10. The back-end system (300) of claim 9, wherein the at least one memory with the program code are configured to, when executed by the at least one processor, cause the back-end system (300) at least to: receive an indication that the link associated with the unique key has been accessed; determine, from the charge data storage (506) , the partial payment card data linked to the unique key; determine, based on the partial payment card data, charging session data associated with a user; and transmit the charging session data.

11. A receipt portal apparatus (400) comprising : at least one processor (402) ; at least one memory (404) including program code (406) ; wherein the at least one memory (404) with the program code (406) are configured to, when executed by the at least one processor (402) , cause the receipt portal apparatus (400) at least to: obtain information identifying an electric vehicle charging station (504) ; transmit the information identifying the electric vehicle charging station (50) to a back-end system(300) to initiate a receipt retrieval session at the back-end system (300) ; receive, from the back-end system (300) , at least part of charging session data associated with the user; and display the at least part of charging session data associated with the user via a graphical user interface .

12. The receipt portal apparatus (400) of claim 11, wherein the at least one memory (404) with the program code (406) are configured to, when executed by the at least one processor (402) , cause the receipt portal apparatus (400) at least to: provide, via the graphical user interface, an instruction to show a payment card at a payment terminal associated with the electric vehicle charging station (504) .

13. The receipt portal apparatus (400) of claim 11 or 12, wherein the at least one memory (404) with the program code (406) are configured to, when executed by the at least one processor (402) , cause the receipt portal apparatus (400) at least to: request, via the graphical user interface, a user to input an email address in order to receive future receipts automatically; and transmit the email address to the back-end system (300) .

14. The receipt portal apparatus (400) of any of claims 11 - 13, wherein the at least one memory (404)with the program code (406) are configured to, when executed by the at least one processor (402) , cause the receipt portal apparatus (400) at least to: transmit to the back-end system (300) an indication to stay logged in; receive a login token from the back-end system (300) ; and store the login token for subsequently obtaining charging session data associated with a user in a memory .

15. The receipt portal apparatus (400) of claim 14, wherein the at least one memory (404) with the program code (406) are configured to, when executed by the at least one processor (402) , cause the receipt portal apparatus (400) at least to: obtain the login token from the memory; transmit the login token to the back-end system (300) ; receive, from the back-end system (300) , at least part of charging session data associated with the user in response to transmitting the login token; and display the at least part of charging session data associated with the user via the graphical user interface .

16. The receipt portal apparatus (400) of any of claims 11 - 13, wherein the at least one memory (404) with the program code (406) are configured to, when executed by the at least one processor (402) , cause the receipt portal apparatus (400) at least to:receive a link with the at least part of the charging session data associated with the user, the link enabling a subsequent access to the session data associated with the user; and display the link via the graphical user interface .

17. The receipt portal apparatus (400) of any of claims 11 - 13, wherein the at least one memory (404) with the program code (406) are configured to, when executed by the at least one processor (402) , cause the receipt portal apparatus (400) at least to: access the link; in response to accessing the link, receive at least part of the charging session data associated with the user; and display at least part of the charging session data associated with the user via the graphical user interface .

18. A system comprising: a back-end system (300) of any of claims 1 - 10 configured to be in communication with at least one electric vehicle charging station (504) ; a receipt portal apparatus (400) of any of claims 11 - 17 communicatively connected to the back- end system (300) ; and a charge data storage (506) communicatively connected to the back-end system (300) .

19. A method comprising:obtaining, from a receipt portal apparatus ( 400 ) , information identifying an electric vehicle charging station ( 504 ) ; initiating a receipt retrieval session in response to receiving the information identifying the electric vehicle charging station ( 504 ) ; receiving a charging transaction request associated with the electric vehicle charging station ( 504 ) , the charging transaction request comprising data associated with a payment card; determining that there is an existing receipt retrieval session associated with the electric vehicle charging station ( 504 ) ; determining partial payment card data based on the data associated with the payment card; determining, from a charge data storage ( 506 ) , charging session data associated with a user based at least in part on the partial payment card data, the charge data storage storing charging event data associated with at least one user, the charging event data associated with a user comprising prior charging session data relating to at least one charging session in at least one the electric vehicle charging station and partial payment card data associated with the user ; and providing at least part of the charging session data associated with the user .20 . A method comprising : obtaining information identifying an electric vehicle charging station ( 504 ) ; transmitting the information identifying the electric vehicle charging station to a back-end system(300) to initiate a receipt retrieval session at the back-end system (300) ; receiving, from the back-end system (300) , at least part of charging session data associated with the user; and causing display of the at least part of charging session data associated with the user via a graphical user interface.

21. A computer program comprising program code configured to perform the method according to any of claims 19 - 20, when the computer program is executed on a computer.

22. A computer-readable medium comprising a computer program comprising program code configured to perform the method according to any of claims 19 - 20, when the computer program is executed on a computer.

Images