Infrastructure management of vehicle charging points and their system (Machine-translation by Google

专利摘要:
Infrastructure management of vehicle loading points and their system. The invention relates to a system for managing at least one network of charging points comprising at least one management server, at least one database for storing information related to the charging points, of said network, supplying power to electric vehicles, at least one hardware and software architecture comprising a set of modules for the management of the users and the configuration of the loading points or park of charging points, at least one memory for storing data and a processor for executing a program stored in the memory to implement the functionalities of each module, said management system being characterized in that it provides at least one interface to a load point operator to manage and configure its own network of charging points and at least one user interface, the user interface comprising communication tools that allow the user to choose at least one type of connector and a type of load point protocol, corresponding to a given vehicle, of the infrastructure of the load point operator. (Machine-translation by Google Translate, not legally binding)
公开号:ES2718648A2
申请号:ES201631735
申请日:2016-12-30
公开日:2019-07-03
发明作者:Diaz Juan Guinea；Calzada Carlos Recio；Hernando Jorge Gonzalez；Vega Zorayda Guerrero；Lopez Luis Maximiliano Andres；Del Rio José Alberto Gonzalez；Rodriguez Silvia María Cid；Pereda Antonio Javier Garcia；Matesanz Roberto Navarro；Hernandez David Alonso；Seoane Celestino Güemes；Jacue Miguel Angel Rodriguez；Manuel De Briz David De；Delgado Pablo Garcia-Arista；Gorostiaga Juan Perales；Pena Julio Estevez；Trobo Enrique Diaz；Monferrer Marta Alberto；Bellon Ignacio Lopez；Castano Fernando Parrilla
申请人:Atos Worldgrid SL；
IPC主号:

专利说明:

[0001]
[0002] DESCR
[0003]
[0004] AC points infrastructure management
[0005]
[0006] Field of the Invention
[0007]
[0008] The present invention relates to the field of electric vehicles and, more precisely, infrastructure.
[0009]
[0010] Background of the Invention Vehicles like other vehicles, which work
[0011] liquid fuels), the electric vehicles stations, which provide the energy needed for said stations are not numerous, the num will promote the installation of said electric vehicles service station (EVSE). "chargers", although this is not technical
[0012] A bank for electric vehicles of e 2014/062909, which teaches a driver with points. However, this document is restricted to a single operator and does not teach networks of banks belonging to several ope
[0013] Although there are large banks occupied by one electric vehicle at a time, a service provider (PU operator) In addition, each operator would like to be able to know those who do not have a subscription.
[0014]
[0015] In addition, operators would appreciate a sis installation of new loaders, for loaders, to facilitate the update of m IPCIÓN
[0016]
[0017] RGA of vehicles and its system
[0018]
[0019] of charging point infrastructure to a system for managing said
[0020]
[0021] Today, electricity is increasingly used and, by means of fossil fuels (which means tricos, they need infrastructure, such as the saria for their operation. Despite the fact that more and more electric vehicles are large banks or equipment parks of EVSEs are commonly called camente precise.
[0022]
[0023] This type is disclosed in WO document issued to charging points and controlling said stra only the constitution of a bank how to constitute and manage a plurality of radores.
[0024]
[0025] EVSE s, and some or all of them could be a user would like to be independent of a charge number) for charging your vehicle. supply electricity to users, even to
[0026]
[0027] issue with flexibility that would allow obtaining a park or a bank of aterial and network configuration.
[0028]
[0029] Explanation of the invention.
[0030] The present invention has as an object obvi by offering means for controlling a load park comprising a set
[0031]
[0032] This objective is achieved by means of a system of charging points comprising at least or data for storing related information by providing power to electric vehicles software comprising at least one module monitoring and / or maintenance of the charging invention, or at least one module of « reser by computer to manage the computer process (1) comprising at least one exchange of information with the point d user or mobile device, at least one m to execute a program stored in that of each module, said computer system being executable of the module «interface point for an operator of the charging point network of load points and save it in the memory only accessible to the operator or the user executable by computer of the communication module", with a user interface user choose remotely at least one given tip, and at least one communication with an operator's p (5a, 5b) for the reception of dic a reservation in the r ed under the control of the system
[0033]
[0034] According to another feature, the "reserve" instructions on the server allow the functions
[0035] • lock a connector within a pu a specific identification card and last or
[0036] For certain disadvantages of the prior art, a network of charging points or a charging point network is flexible.
[0037]
[0038] ma for the management of at least one network of n management server, at least one database with the load points, of said network, s, at least one hardware architecture and "load point" for the configuration and / o detailed property list of the rva points »which includes executable instructions reservation of the charging point, architecture of the media (6a, 6b) for the charging (4) and / or an external system and / or an emoria to store data and a memory processor to implement the management functionalities characterized in that the load code »(1a) provides at least one a (5a, 5b) to manage and configure its own management system server in a river part of the operator's client or serva instructions "which provides at least one interface comprising tools to allow the connector po, which corresponds to a vehicle along with the infrastructure network load, has information in the system and to proceed further and management
[0039]
[0040] Computer executable actions of the module of:
[0041]
[0042] No charge, to be used only through the reservation period;
[0043]
[0044] • remotely block a d connector by means of the information contained in the ta for a period of reservation time, by remote communication, and then unlock by means of the identification card used p
[0045]
[0046] According to another characteristic, the "charge point" instru controls:
[0047] remote management of charging points through said charging points, or
[0048] the follow-up of the changes of state of the monitoring of the availability of the load.
[0049]
[0050] According to another feature, the "load point" instruments provide an easy CP of load parks and management with the establishment and memorization for AC (IDcp) and the location of the CP sites of a connector present in each CP of a park
[0051]
[0052] According to another feature, a system is characterized by the fact that the detailed configuration information comprises a section comprising at least one or more of: the ide name assigned to the CP that can be resolved domain), the language chosen for the CP, the con CP (for time conversion) and address form or tab for C location
[0053]
[0054] According to another feature, the information during configuration comprises a s "tab" stored in the memory of the CP manufacturer, the protocol used for CP, the IP address of the CP.
[0055] e a charging point, to be used only the specific user identification card of a remote device or an interface to the connector chosen at the charging point to block said connector.
[0056]
[0057] module executable ctions
[0058]
[0059] is the execution of remote actions in
[0060]
[0061] e the points load or
[0062] s communications within those points of
[0063]
[0064] Computer-executable actions of the management interface module to allow the grouping of the connectors (or pins) CP by means of a park of a list of park CP identifiers and associated with each CP a list of e.
[0065]
[0066] According to claim 1, the loading point generated during the general data or "tab", which section CP (IDcp), the host name or the r with a DNS system (touch name server, the location of the CP, the time zone of the data to be supported by the CP; a section P.
[0067]
[0068] ation of the charge point generated hardware parameter (HW) or system parameter that includes information about the CP, the firmware reference, the model of the According to another feature, the information during configuration comprises one that is memorized in the memory system that inform how the management system interacts with different OCPP interpretations and behavior.
[0069]
[0070] According to another characteristic, the information during configuration comprises a section memory of the system and comprising the maximum amperage ID (allowed), the state, the connector), the identifier of the program reservation
[0071]
[0072] According to another feature, the information during configuration allows the user to axis the CP, and choose the parameter to be configured in the management system awaits the response of the CP
[0073]
[0074] According to another characteristic, the pa understand, for example:
[0075] • Pulse interval,
[0076] • Connection expiration,
[0077] • Restart retries,
[0078] • Id charge point,
[0079] • Proximity contact retries, • Proximity blocking retries, • Blink repetition,
[0080] • Light intensity,
[0081] • Sample interval of medic value
[0082]
[0083] According to another characteristic, the "administration" arq that comprises instructing the management system knows that a load point sends a request PDU of configurable pul pulse interval; After re the management system must respond with a detailed action of the generated charging point additional configuration or “tab” cludes additional configuration signals that it holds with the CP (4) to facilitate the definition of winds with different CP manufacturers .
[0084]
[0085] Detailed description of the charging point generated by the connector ion or «tab» stored in the connector, the type of the connector, the voltage / the recharge model (recharge mode of the mada in the connector.
[0086]
[0087] Detailed ation of the generated charging point to perform a remote configuration on demand in a combination of "Parameters" while a waiting clock is displayed.
[0088]
[0089] radars included in this tab can
[0090]
[0091] ion.
[0092]
[0093] The project also includes a module of computer-executable s to allow a charging point is still connected, a point of lagation after a time interval after a pulsation request PDU, a pulse confirmation; the answer of The PDU will contain the current system time used by the charging point to synchronize
[0094]
[0095] According to another characteristic, the «reservation» instructions of the management system, request a reservation request now at a specific car point a connector to be reserved; and with a reservation confirmation PDU upon request, it coincides with a reservation at the point of replacing the reservation with the new reservation at which it coincides with no reservation at the point d returning the status value "ACCEPTED" if your cargo will return to "BUSY" if the point occupied; The charging point must also be charged or the connector has been reserved for the charging point and must return to "FAILURE" fault status.
[0096]
[0097] According to another feature, the «reservation» instructions of the management system, unloading of cargo accepts the reservation request, and incoming identification tags in the incoming identification co-label or the identification tag or identification tag
[0098]
[0099] According to another characteristic, when the «charge point» module, reserves are set on connector 0; if the identifier then the loading point must not re ensure that at any time du remains available for the ide tag
[0100]
[0101] According to another characteristic, of this computer of the «reserve» module, a reservoir when (i) a transaction is initiated for the identification matrix matrix and in the management connector, which is recommended to be its internal clock.
[0102]
[0103] Computer-executable ctions of the module a reservation by sending a rga PDU with the management system option waiting for a response from the charging point now; if the identifier of the reservation in the one of load, then the point of load will have the request; if the reservation identifier does not load, then the charging point must succeed when reserving a connector; the charging point or the specified connector are returned to "BUSY" when the point of the same or other identification tag; the if the charging point or the connector are in
[0104]
[0105] The module's executable computer actions show the following behavior: if the ntonces point, it will deny the load for all the reserved onectors, except when the matrix identification eta coincide with the reserve matrix cation.
[0106]
[0107] Zero connector reservation parameter supported to "TRUE", the load point supported by the connector in the reservation request is 0, to serve a specific connector, but the reservation is valid, a reserved ntification connector.
[0108]
[0109] In accordance with the instructions executable by rva, the reserved identification tag or the reserved label or any connector shall be terminated at the point of loading. Reserved connector identifier is 0, or (ii the expiration date, or (ii) when "NOT AVAILABLE" is set.
[0110]
[0111] According to another feature, the «reserve» instructions allow the connector system to be requested when the charging point sends a
[0112]
[0113] According to another feature, then in the CPO support service, an operator request to unlock the connector when the connector is unlocked.
[0114]
[0115] According to another feature, the i provide upon receiving a request PDU must respond with a confirm reply PDU will indicate if the loading point was ca transaction in progress in the specific transaction connector for the first time.
[0116]
[0117] According to another feature, the "administration" arq that includes application configuration instruction and defined different functions supported by said arq
[0118]
[0119] According to another feature, the "energy" arq which comprises instructions executes energy consumption monitoring.
[0120]
[0121] According to another characteristic, the “monitoring” arq for the supervision of the transactions and events system.
[0122]
[0123] According to another feature, the "users" arq which includes instructions eg user of the electric vehicle.
[0124] i) when the specified time is reached in ce the charging point or connector in "FAIL" or
[0125]
[0126] Computer executable actions of the management module that a load point unlocks a connector unlock request PDU.
[0127]
[0128] of a call from the drivers of the EV rador could manually activate the sending of charging point, forcing a new attempt to
[0129]
[0130] computer executable instructions will unlock the connector, the charging point unlock the connector; the peace PDU to unlock its connector; or if there was an ico, then the loading point will end the
[0131]
[0132] Uitectura also includes a module of computer-executable ions for the number of permits along with its association with uitecture.
[0133]
[0134] The uitecture also includes a module of computer tables for recovery and
[0135]
[0136] uitectura also includes an ema module as a whole, communications,
[0137]
[0138] uitectura also includes a module of computer equibles for the management of According to another characteristic, the “reports” arq that includes instructions axis reports related to the operation of the
[0139]
[0140] According to another feature, the module executable by computer to:
[0141] configure the firmware that will be sent to a white list or list of charge points according to the configuration manage and configure the way to group l manage the operators of car points of charge point to users, giving access to a subset of the functionalities
[0142]
[0143] According to another feature, the "administration" (1f) instruments will send a list PDU to a loading point. The update request PDU (complete or differential) and the number associated to the local authorization list upon receipt of a send request PDU wait for a response from the local list list point; The PDU response will indicate if the local authorization list. If the status and update was differential, then the local authorization system completes with a type of act
[0144]
[0145] According to another feature, a computer-executable mode for load-balanced analysis and management of operations.
[0146]
[0147] According to another characteristic, a module executable by computer to send notifies to take corrective measures in case of a sit of load points.
[0148] uitectura also includes a module of computer cutables for the production of charging points.
[0149]
[0150] of "administration" includes instructions
[0151]
[0152] set of charge points to update, or RFID targets to be sent to said charge point set, or
[0153] the charging points, or
[0154] external ga to delegate the maintenance of said operators of external load points to the architecture.
[0155]
[0156] The computer executable module and local list submission request to send the local list submission unit will contain the type of version number that the loading point must after it has been updated; After the local list, the management system must accept the update of the error or version disparity with a loading point sending PDU and the type of management ema should try to send the complete update list.
[0157]
[0158] The "energy" module includes instructions on the stability of the power supply network, the loading rations of the charging points.
[0159]
[0160] "monitoring" includes instructions to actors or operators that may unexpectedly occur within the infrastructure According to another feature, the computer executable module for the geolocalised camera and a location device, for a quick and visual idea of the states of the
[0161]
[0162] According to another feature, the module executable by computer for criticality storage, in the memory of the architecture, configuration of each event to suggest action
[0163]
[0164] According to another characteristic, the configuration of the loading point allows the execution of additional action on the loading points.
[0165]
[0166] According to another feature, a mod executable by computer to create, read, ac stored in a system memory and pr RFID card or similar to a loading point and surpassed by the user before loading the vehicle
[0167]
[0168] According to another feature, the mod executable by computer for the external system delegation, for example, to a final authorization check of the operad
[0169]
[0170] According to another feature, the mod executable by computer to provide white list distribution to the car points reduce the amount of data to be transferred in the m
[0171]
[0172] According to another feature, a computer-executable mod for exporting reports to provide tools to the "monitoring" option comprises instructions for events, by means of at least one providing a load point operator with load points.
[0173]
[0174] "Monitoring" includes instructions for events with a parameter of, and to take into account criticality and corrective ions.
[0175]
[0176] Duration of each event, through the operator and orders immediately to perform any
[0177]
[0178] "Users" module includes instructions to update and delete the information of a user to provide access control through a process to manage the authorization to be an item.
[0179]
[0180] "Users" module includes instructions on the final authorization check to another bank, in case the or service is not available.
[0181]
[0182] The "users" module includes instructions to administer user groups and to keep it at the loading points for a transaction or operation.
[0183]
[0184] The "reports" module includes data instructions, data analysis and generation of information for your organization and analysis.
[0185]
[0186] According to another feature, the computer executable mod to provide retrieve only the interesting information from a
[0187]
[0188] According to another feature, a module executable by computer for the definition of administrator.
[0189]
[0190] According to another feature, the module executable by computer for system configuration and interface customization
[0191]
[0192] According to another feature, the computer executable mode to allow state of the charging points from the «reserveable» charging state.
[0193]
[0194] According to another feature, the computer executable mode to verify that it reaches the planned reservation periods and, follow-up of the reservation steps and any
[0195]
[0196] According to another feature, the web services system with exchange operations
[0197]
[0198] According to another feature, the management system includes:
[0199] • a charging point service for direct requests to the charging points;
[0200] • a peer RFID checking service to initiate load transactions;
[0201] • a c session report service related to the flow of transactions • a reservation report service for reservation,
[0202] The "reports" section includes instructions to access different tools that allow a specific group of users.
[0203]
[0204] of "administration" includes instructions and internal events and data management of the
[0205]
[0206] "administration" comprises instructions with attributes that affect the end-user behavior z.
[0207]
[0208] «reserve» module includes instructions the operator of the load points change the «direct» load do to the state of the points
[0209]
[0210] «reservation» module includes instructions reservations do not overlap and that the user creates internal events to make an unexpected incident or abnormal situation.
[0211]
[0212] EMA de Gestión provides a set of information with third-party systems.
[0213]
[0214] next to services, provided by said
[0215]
[0216] ar any information or to send orders
[0217]
[0218] to confirm if some users are authorized
[0219]
[0220] it communicates load information to external systems;
[0221] notify all status changes of the • a whitelist service to distribute RFID cards to all background load points.
[0222]
[0223] Brief description of the drawings
[0224]
[0225] Other features and advantages of the present reading of the following description, given with r - Figure 1 is a schematic representation of embodiment;
[0226] - Figure 2 represents the function of the management system software c according to co - Figure 3 is a schematic representation of the hardware architecture and its embodiment;
[0227] - Figure 4 represents a screen of an in for the location of charging points, of ac - Figure 5 represents a screen of the "charging point" module of the user's mobile architecture, according to a mode - Figure 6 represents a screen of the "load point" page of the architecture of ac - Figure 7 represents a screen of the architecture "energy" module of ac - Figure 8 represents a screen of
[0228] «Reports» of the architecture, according to - Figure 9 represents a screen of an inf of «reports» of the architecture, according to a mo - Figure 10 represents a screen of a by the module «reports» of the architecture - Figures 11 and 12 represent the infrastructure panel of a realization point operator;
[0229] - Figure 13 represents an architecture screen, according to another way of reacting asynchronously a white list of the network of the charging point operator in
[0230]
[0231] and invention will appear more clearly with the reference to the attached drawings, in which:
[0232] Ethics of the management system according to a
[0233]
[0234] components of the hardware architecture and an embodiment;
[0235] ethics of the software layer and software possibilities of the management system according to
[0236]
[0237] Terfaz GIS (geographic information system) according to an embodiment;
[0238] detail page of the load points of the a, either in the server or in the operator or in realization;
[0239] detail of the module load point according to another embodiment;
[0240] charge detail istro provided by the sane with an embodiment;
[0241] a report provided by the module of an embodiment;
[0242] form of events provided by the module of realization;
[0243] report of the latest events provided, in accordance with another embodiment;
[0244] those of a panel of reports of the state of the given load (CPO), according to a mode of
[0245]
[0246] the interface of the «users» module of the lization;
[0247]
[0248] - Figure 14 represents a screen of the in by the "administration" module of the embodiment;
[0249] - Figure 15 represents an information screen about the load park according to - Figure 16 represents an information screen about the direction of an embodiment park;
[0250] - Figure 17 represents a screen of the provides information on the point of car - Figure 18 represents a screen d information about the connectors used embodiment;
[0251] - Figures 19a and 19b represent the open loading point screens) that can be sent according to an embodiment;
[0252] - Figures 20a and 20b represent the pant (open load point protocol) that pr configuration of the protocol of a car point - Figures 21a and 21b represent the screens that provide information on the reservation reserve of the last ones to according to an embodiment.
[0253]
[0254] Embodiment of the invention
[0255]
[0256] The present invention relates to a system minus a charging point operator (C plurality of charging points for vehicles such as a country.
[0257]
[0258] With said management system, the operator remote operations.
[0259]
[0260] In some embodiments, the load system (CPs) comprising at least one terfaz of the architecture provided management tables, according to another mode of
[0261]
[0262] the general data section that contains an embodiment;
[0263] the address section that provides the charge or point eu, according to a mode of
[0264]
[0265] hardware parameter section (HW) that ga, in one embodiment;
[0266] e the connector section that provides two for a given load point, according to a
[0267]
[0268] The operations of OCPP (r protocol remotely to a given load point,
[0269]
[0270] beyond the communication section of OCPP, it opts for the different options about the given rga, according to an embodiment;
[0271] llas, respectively, of the reservation section of a loading point and the section of events events related to the loading points,
[0272]
[0273] a for the management of at least one network of the PO), said network consisting of an electric network, being located in such territory
[0274]
[0275] load point (CPO) can perform
[0276]
[0277] of managing at least one network of management vidor points (2, figure 1), at least one database (3) for storing information on said network, providing power to hardware and software vehicle (1, figure 2) that it purchases (1a) comprising instructions executable monitoring and / or maintenance of an inve recharge, a module «energy» (1b) for energy, a "monitoring" module ((for example, high temperature, block overload failure, etc.), communications, t "users" (not shown) for example management via an RFID, a module related to the operation of
[0278] «Administration» (1f) for the configuration together with its association with different functions «reservation» module (not shown) qu computer to manage the SOAP web service reservation process (for a computer protocol comprising at least some exchange of information with the user or mobile device point, at least one m to execute a program stored in that of each module, being characterized by computer executable of the «pu interface for a load point operator network of load points network and save it in the memory being which only the op can access by providing the executable instructions minus a communication interface, with a web service) that comprises remote tooling at least one type of connector that communicates with a point in the network inf 5b, figure 1) for the reception of said informa reserve in the network under the control of the system of
[0279]
[0280] For the reservation of a charging point (4), one or provided by the instructions executes n related to the charging points (4), in the electrical, at least one architecture of at least one module of "charging point" s by computer for the configuration and / or detailed asset inventory of recovery points and consumption monitoring 1c) for general system monitoring eo of the connection, grounding fault, transactions and events, a electric vehicle user module (EVu), by "reports" (1e) to produce reports charging points (CP), an application module and the definition of authorizations are admitted by said system, or at least one eu comprises instructions executable by rva of each load point (CP), through simple object access), media architecture (6a, 6b) for the load (CP) and / or an external system and / or an emoria for store data and a memory processor p To implement the functionalities of this management system because the loading code »(1a) provides at least one (5a, 5b) to manage and configure your own management system server in a part of the viewer or the customer user of the operator or computer from the «reserve» module to the user interface (for example, a tas interface to allow the user to choose in response to a given vehicle, and at least one load operator structure (CPO) (5th, rmation in the system and to proceed to an e management.
[0281]
[0282] You can choose one of the computer functionalities of the «reserve» module, allowing said instructions to execute functionalities, for example, of:
[0283]
[0284] • block a connector within a point a specific identification card and d or
[0285] • remotely block a u connector using the information contained in it for a period of time of remote communication interface reservation, and charging via the identification card
[0286]
[0287] An administrator through the module «functionalities for the operation ad load points. In some way of performing
[0288]
[0289] • configure the firmware that will be sent update memorizing the firmware and communication that will be used for said • provide the white list or list of card charging points (4) depending on the configuration • manage and configure the form of graphical interface group to allow that a selected, or
[0290] • Manage the operators of points of maintenance of the load point (4) to external load points (5a, 5b) architecture access (1).
[0291] •
[0292] In some embodiment, the module of some master data tables. These tabl permits along with their association with diferent present invention.
[0293] by computer, on the server, the
[0294]
[0295] loading (4), to be used only during the reservation period;
[0296]
[0297] n charging point (4), to be used only user-specific identification card a, by means of a remote device or one or unlock the connector chosen at the ion point used to block said connector.
[0298]
[0299] administration »(1f), you can activate an equated set of a loading point (4) or a parking lot, these functionalities include:
[0300]
[0301] to a set of charge points for a list of charge points and update links, or
[0302] etas RFID to be sent to said set of charge point settings (4), or
[0303] for the load points (4), offering an administrator to group the load points
[0304]
[0305] and external load (5a, 5b) to delegate the users, said operators having a subset of the functionalities of the
[0306]
[0307] "administration" (f) includes the management of applications that can be configured and define the roles supported by the architecture of the In some embodiments, the module features:
[0308]
[0309] Management of at least one master table
[0310] Definition of roles and permits,
[0311] Event definition and event search:
[0312] all events generated by the comprehensive command network, which provides almost real-time information (available, busy, re-connected, ground fault, overload
[0313]
[0314] By white list, we refer to a limitation list, an RFID card, to which access or special recognition is granted. Accept recognized.
[0315]
[0316] By firmware, we refer to a software or example: a computer, an interface to program a router, etc.) to allow said hardwar
[0317]
[0318] The management system is a complete load solution (CP). With said management system a plurality of CPOs (5a, 5b) connecting remote operations of their CPs (4) including real-time control, reducing operational time.
[0319]
[0320] The management system allows authorization and load transactions and collection of billing transactions. On the other hand, the C management reserve.
[0321]
[0322] The management system also manages all cargo and transmitted to the comprehensive management system, which provides real ace information (available, busy, reserved, etc.).
[0323] or "administration" also includes
[0324]
[0325] : The system of the present invention manages load loads, providing a picture of the status of the servo load points, high temperature, rga blocking failure, etc.).
[0326]
[0327] or registration of entities, for example and without providing a privilege, service, mobility, will list entities approved, and / or
[0328]
[0329] a program integrated in a hardware (by application love (API), a hard disk, re work.
[0330]
[0331] For the management and control of n-point networks, a charging point operator (CPO) or its networks to the system can perform the configuration, supervision, monitoring and maintenance and saving costs
[0332]
[0333] Authentication of the end user, the management of load detail records (CDR) for CP purposes is fully managed by the system of
[0334]
[0335] the events generated by each stion network, providing a dashboard of the states of the CPs (4) in time The CPO (5a, 5b) can generate reports r power consumption, usu charging patterns
[0336]
[0337] The management system has an in interface that provide information about the details network of a CP (4). A third party system to
[0338]
[0339] The management system is a remote comp solution of the charging points.
[0340]
[0341] In some embodiments, the system features:
[0342]
[0343] • the configuration of the load point fl "load point" to support different open load point of the supplier said module and to provide a view c • in addition, the management system with communication configurations, such as general p) , CP with dynamic IP (hypertext transfer protocol (http) protocol, • a module that supports all or necessary through a CPO: update
[0344] communication monitoring, following event messages, remote operations b of the infrastructure and the state (example: white list;
[0345] • a module (module of «point of c instructions executable by computer, the i grouped in loading and management parks by establishing and memorizing CPs identifiers (4) (IDcp) and located to each CP a list of connectors present • booking engine for expiration, authorization, blocking of points related to cargo transactions, years, etc.
[0346]
[0347] Tegration that publishes a set of services charging points, such as obtaining all those authorized can access those interfaces.
[0348]
[0349] litto for centralized management and control
[0350]
[0351] Management can provide the following
[0352]
[0353] lexible is provided by the module of interpretations and versions of r protocol (OCPP) memorized in the system by means of an inherent and unified infrastructure;
[0354] Turn on a module to support different roxies, GPRS (Internet radio packet service), CP with fixed IP, secure connection of different OCPPP contexts, etc .;
[0355] maintenance maintenance of the CP (4) of the firmware, change of remote configuration, protocol messages, garlic demand management, detailed reports on the use of load and CDR), and management of the
[0356]
[0357] load ») that provides, through its easy-to-manage interface to allow the CP (4) to complete the CP connectors (or plugs) for each park from a list of n of the CP sites of a park and associated in each CP of a park;
[0358] ation of the following capacities: o optional charging, change of status of notification, group management, with reservation to non-bookable according to or etc .;
[0359] • The web interface is compatible with the l • Different browsing profiles of web pages are considered current profiles are generated: Global administrator operator of external company;
[0360] • A module for the management of the EVu necessary to access the said infrastructure are: RFID cards, user groups (valid and without active transactions).
[0361]
[0362] On the one hand, the management system is capable of charging points regardless of its v communications (1 ', shown by eg management system allows integration with relevant, such as CDRs (detail records
[0363]
[0364] On the other hand, the management system offers information to the user of the electric, mobile (App) vehicle.
[0365]
[0366] For example and without limitation, an architecture depicted in Figure 3. The architecture (1 ') p • a layer for the management of different load points d (for example: fast loader park),
[0367] • a connectivity layer (3 ') that purchased system and mobile point infrastructure (GSM) or universal machine-to-machine communication system (M2 • a layer of adapters (4') that includes a charging point (for example: such as IEC CP mutation (from one that can occupy the CP and average reserves),
[0368]
[0369] location;
[0370] Web user. The options and fields dynamically depending on the profile. The l, aggregator, operator, EV user and
[0371]
[0372] or, including loading authorization processes. The concepts involved through RFID, CP status and validation of
[0373]
[0374] z to integrate with different ersion providers of the OCPP protocol and example architecture in Figure 3). On the other hand, said n third parties for the exchange of cargo information) for billing purposes.
[0375]
[0376] ece a service layer to provide either through the web or the application
[0377]
[0378] (software part) of the management system can include several layers:
[0379] e load (2 ') comprising a load configuration, independent load points, or
[0380]
[0381] therefore the means for communication between the cargo (for example: global system for mobile telecommunications (UMTS), an M), or the Internet),
[0382] turns on different operator protocols from -15118),
[0383]
[0384] • a layer of tools (5 ') that are provided or managed by web access, databases),
[0385] • a layer of main systems (6 ') pair comprises, for example, the GIS support p
[0386]
[0387] The flow of information between each layer of the communication (7 '), for example, an interface
[0388]
[0389] In some embodiments, the "load point" module instructions (1a):
[0390] • remote management of the remote c points at said load points (4), by blocking command of the CPs for an interval reception of information from the CP in the power grid, load balancing and tran • tracking and memorization of l (4), for example, which receive the status of ocu • monitoring the availability of cargo (4).
[0391]
[0392] The «load point» module (1a) has the following actions:
[0393] • maintenance of an inventory of charging point infrastructure;
[0394] • execution on demand of shares according to different criteria;
[0395] • an integration with GIS applications for example, figure 4);
[0396] • centralized administration management;
[0397] • manage CP reserves created • interoperability to comply with OCPP and other planned ones, such as IEC-1511 turns on tools to access load point structure services (for example,
[0398]
[0399] to the integration of the third-party interface, which focuses on the location of the charging points.
[0400]
[0401] Architecture is obtained by means of message-oriented media.
[0402]
[0403] computer executable ions of the control of the
[0404]
[0405] arga (4) through the execution of example actions, by sending the orders of or of time within a time frame or the action with the consumption of energy, information, cargo fillings, or
[0406] changes in the status of load points pation or failure of load points, or
[0407] e communications within those points
[0408]
[0409] to provide at least one or more
[0410]
[0411] and detailed and updated assets of the
[0412]
[0413] remote in load point groups of
[0414]
[0415] (geographic information system) (see,
[0416]
[0417] firmware and distribution updates
[0418]
[0419] by end users;
[0420] different standard protocols (currently 8).
[0421]
[0422] Figure 4 shows, for example, the screen search, with your mobile device or Ipad, a pu of a given operator in a specific region loading, corresponding to the request, blue circles and the address (40a) of a co you can get through a zoo function choose a charging point or a point park
[0423]
[0424] The detail of the information in the management system is described in a sample page in figures 5 and 6.
[0425]
[0426] The loading point detail page,
[0427] provides access to all the example information, in figure 6), configuration, connected specific list of the updated vehicle d of the vehicle (shown, for example, exchanged OCPP messages and events.
[0428]
[0429] On the other hand, this page allows the CP axis for the following topics: Operations OR
[0430]
[0431] The detailed information of the charging point p • a section of general data or «p figures 6 and 15): this section includes the id or name assigned to the CP that can be domain names), the language chosen for the CP's time (for time conversion) • an address section or tab (q 16) for the location of the CP;
[0432] • a section of parameters of hardw example, in figures 6 and 17): this section p of the CP, the protocol used for the CP, the IP address of the CP, etc.
[0433] • an additional section of configuring additional configuration indicators from a GIS interface. A user can recharge or park physical charging points (for example, in Europe). The points on a map in groups (4a, 4b) as a given set of loading points or park are included in the GIS. Once the user s load, he can proceed to a reservation.
[0434]
[0435] rga (4) and the operations managed by the ina details of the loading point, as
[0436]
[0437] shown for example in figure 5, in a CP: address (shown, by tores of different types and association with a regular form in each new presentation in figure 7), health checks, reservations,
[0438]
[0439] on demand operations in the CPP and software configuration (SW).
[0440]
[0441] You can understand:
[0442] tin »(shown, for example, in the entity (ID) of the CP (4), the name of the host resolved with a DNS system (server of the CP, contact, location of the CP, zone and format of data supported by the CP;
[0443] which is shown, for example, in figures 6 and
[0444]
[0445] are (HW) or "tab" (shown, may include information on the manufacturer's firmware reference, the CP model, the
[0446]
[0447] ion or "tab": this tab includes the e shape how the management system interacts with the CP (4). This setting at CP level. These indicators facilitate OCPP behaviors. The OCP protocol about how the CP should behave CP behaviors are possible and correct them to provide a unified view of different indicators introduced in the CP behavior according to different CP manufacturers.
[0448] • A connector section or “tab” this tab can include in the memory of the maximum voltage / amperage (allowed) recharge of the connector), the identifier of the re will be used to send messages to the CPs of an • operations section OCPP or “figures 19a and 19b): in this tab, the user demands in the CP. The user can choose operation ». While the esp management system waits and, if there is an error, a successful operation is shown, Figure 20b is shown, indicating a network operation message and delivered by the remote CP in which it is
[0449]
[0450] OCPP operations may include or Exchange availability;
[0451] Clear cache;
[0452] Remote transaction start;
[0453] Remote transaction stop;
[0454] Restart;
[0455] Get diagnosis;
[0456] Unlock connector;
[0457]
[0458] Each operation message sent to an entry. The meaning of the parameters is dicional, it provides great flexibility to a definition of the different interpretations and P does not provide detailed descriptions at some points. Therefore, different os. The management system deals with all of the CP network. This tab includes the management system to configure each real experience in integration with
[0459]
[0460] (shown, for example, in Figure 18): system, the connector ID, the type of connector, the status, the recharge model (serva mode provided on the connector. This information a park and check its operation;
[0461] tab ”(shown, for example, in the Aryans you can execute remote operations under the operation in the combination“ Select was the response of the CP, a message clock is shown as, for example, in Figure 20a. If the CP response, as, for example, on the successful receipt received by the OCPP through the request for an operation.
[0462]
[0463] perations such as, for example:
[0464]
[0465] CP needs specific parameters such as the same as OCPP 1.2 or 1.5, depending on the CP protocol. Depending on the operation dynamically to the system memory
[0466]
[0467] The management system verifies the type, the content
[0468]
[0469] In some embodiments, the status point and of any relevant fact that there is nothing to report, the point of loading in predefined interval. Under circumstances, the management system has (any) reason. What can a management system do if the last status notification it received could be expected The same can be pre-diagnosed. The problem in these situations is covered by existing messages. The probl The loading point has the information, but management would like an update.
[0470]
[0471] The activation message request makes loading point, to send management initiation messages indicates what the message is that of requested, the management system can indicate request. The message request ID of the connector is appearing, it is not relevant for the message requested must still be sent.
[0472]
[0473] Conversely, if the connector ID is relevant "for all permitted values of the status notification ID (request) of the load co ID. A request for a notification of multiple status notifications: the notification notification for each One of its connectors.
[0474]
[0475] In some embodiments, the activation point, before sending the activation (response) message the selected load point n, the management system asks for the necessary input parameters.
[0476]
[0477] or and the format of each parameter.
[0478]
[0479] Cargo informs the management system of its production during normal operation. If I do not send at least one message of pulsation in an evil this is fine, but what happens if the nes to doubt the last known state A firmware update is ongoing and the much longer than reasonably guntar for the progress of a request is not that the necessary information is not motto is strictly a time issue.
[0480] he has no way of knowing that the system of
[0481]
[0482] The management system may request the load point (s). In the request, the system is to receive. For each of these messages r optionally to which connector this link applies: if the identity of the specified connector, message, must be ignored. In such cases, the
[0483]
[0484] e, but absent, this should be construed as a connector. "For example, a request for a nector = 0 is a request for the state of the state point without the connector ID is a request for the charging point itself and a
[0485]
[0486] load will first send the response to the requested message. In the confirmation the message will indicate if it will be sent or not, returning "ACCEPTED" or "REJECTED". It is the shipping point. If the requested message is reloaded, it will return "NOT IMPLEMENTED".
[0487]
[0488] The messages that the loading point marks occur the situation in which, between the desired acceptance, that same message is sent from cases, the message sent can only be considered
[0489]
[0490] The mechanism of the activation message does not e The messages that it activates should only give information activated in this way, for example, it must be what can be measured configured in the measured settings. The messages of initiation of the trans left out of this mechanism because no nature describes a transition.
[0491]
[0492] In some embodiments, the system to unlock a connector. To do this, message, a PDU (protocol data unit
[0493]
[0494] The purpose of this message is to help disconnect your cable from the charging point of the connector cable. When a CPO conduit, an operator could manually activate connector to the charging point, forcing a Hopefully this time the connector will disconnect the cable and leave.
[0495]
[0496] The connector unlocking request is not from a running transaction; In this case, it's in place.
[0497]
[0498] Upon receipt of a request PDU, it will respond with a confirmation PDU. The answer will indicate if the charging point was fully charged, the one that accepts or rejects the request is not implemented or has not been implemented.
[0499]
[0500] as "ACCEPTED" must be sent. It could be the request and the actual sending of the bido message to normal operations. In those cases that comply with the request.
[0501]
[0502] It is intended to recover historical data. current mation. A message of measured values evolve the most recent measurements of any key figuration of sampled data of action value and transaction stop have been related to the state, but by their
[0503]
[0504] of management can request a charging point the management system must send, as only) request for unlocking the connector
[0505]
[0506] EV drivers who have problems in the event of a malfunction of the retention of an EV call the help desk to send a request to unlock the new attempt to unlock the connector. unlock and the EV driver can
[0507]
[0508] be used to stop remotely and must use the remote stop transaction
[0509]
[0510] and unlocking the connector, the unlocking charging point of the connector. The peace PDU unlock your connector.
[0511]
[0512] If there was a transaction in progress, the transaction will end first, as described above.
[0513]
[0514] The request for unlocking the connector is withholding the cable in the connector, not to
[0515]
[0516] In some embodiments, the infor also understand:
[0517]
[0518] • a soft user configuration section can execute a remote configuration the parameter to be configured in a combination d awaits the response of the CP, a relay tab can be shown, for example:
[0519] - Pulse interval,
[0520] - Connection expiration,
[0521] - Reset retries,
[0522] - Id charge point,
[0523] - Proximity contact retries, - Proximity blocking retries, - Blink repetition,
[0524] - Intensity of light,
[0525] - Sample interval of medic value
[0526]
[0527] The parameters need the new configuration value is the same as OCPP 1.2 management system uses the configuration to be necessary input parameters. The system the content and format of each parameter;
[0528]
[0529] • Does a health check section show health of communications asce memorizes and shows the time stamp of the specific ector, then the loading point screens in the transaction stop.
[0530]
[0531] intended only to unlock the lock unlock a gateway to the connector.
[0532]
[0533] Detailed charging point can
[0534]
[0535] tware (SW) or "tab": in this tab the on demand in the CP. The user can choose e "Parameters". While the loj management system is waiting. The parameters included in this
[0536]
[0537] ion.
[0538]
[0539] configuration as input. The meaning of or 1.5, depending on the CP protocol. The aforementioned to dynamically ask the management is willing to verify the type,
[0540]
[0541] Communication health or "tab" for ndentes and descendants. This tab also last messages exchanged;
[0542]
[0543] • a reserve section or "tab" (stored in the system so that the
[0544] related to reservations;
[0545] • a section of trazabilid messages last messages exchanged with OCPP detailed on the exchange of the OCPP with the request and response and messages of only link xml on the screen, the message with popup window;
[0546] • an event section or “tab” (to show the latest related events
[0547]
[0548] In some embodiments, a server connected to a database (3), relative to said load points (CPs) and the base of (shown as a continuous line in the figure
[0549] as dashed line in figure 1), for example
[0550]
[0551] The network may comprise several limitation operators, the network may comprise a CPO charging points, CPO-A and CPO-B, which are r CP-B) or a park of charging points compu CP ¹ -A for CP ⁿ -A for CPO-A and CP ¹ -B load points or point operators the same geographical region. For example, and if loading points may be located, charging point infrastructure can and has an interface, provided by the system, accessing the management server (2) of the loading or park system. The configuration consists of charging point infrastructure. The CP manufacturer info (4), the type of communication connector for monitoring the CP (you can access or configure your own check, before any modification a given CP (4) or given CPO (5a, 5b), that the or shown, for example, in figure 21a) system can display all the information
[0552]
[0553] ad or "tab" is memorized to show them with that CP. This tab includes information l CP: name of the operation, time stamps and response. If the user presses the full OCPP XML, it is shown as a
[0554]
[0555] shown, for example, in Figure 21b) with that CP.
[0556]
[0557] dor (2, figure 1) of the management system is at the load points (4). The connection between data can be a cable connection (6b) 1) or a wireless connection (6a) (shown by GPRS, wifi, etc.
[0558]
[0559] of load points (CPO). For example and without -A (5a) and a CPO-B (5b), each operator responsible for managing a CP (CP-A or these for several load points, for example, at CP ^m -A. charging points, the cargo park are not necessarily in limitation, the CPO-A and its infrastructure in France, while the CPO-B and its star located in Spain.Each CPO (A and B) issue of management, which can be used for management to configure their own points in giving information about each CP (4) of the rmation can include, for example, the res, the protocol and also the means of 4) or the CP park . Each CPO (A or B) only to load point network. The server (2) of the data stored and related to the modification order refers exactly to a network equipment of said CP, for example CP identifier that must include the tot checking a correspondence list in the access of each operator is secure by means of (2) the management system, by means of m given by the CPO ( 5a, 5b) and stores them. The will be used for the CPs. The CPO (5a, 5b)
[0560] charge point protocols. The list of each CP park can be used by means of an interface, depending on the characteristics
[0561]
[0562] In some embodiments, the functions include the analysis of the stability of load balancing and the management of tran
[0563]
[0564] The management of the operations of load purchases and monitoring of the transactions, in order to provide information in real time to the ope The «energy» module (1b) can also be
[0565]
[0566] • the management of detail record of car with other main computer systems billing ...);
[0567] • a vehicle support to the network (V2G distribution management (DMS) to help
[0568]
[0569] Through the vehicle-to-grid system, we plug-in electric, such as electric cars, communicate with the power grid to sell the electricity supply in the network or media
[0570]
[0571] A detailed load record (which shows information about the type of connector that starts and ends the charging process, the load number, the identity of the users (option of the charging point (4, figure 1).
[0572] , checking the CPO identifier with the size or part of the CPO identifier or between the CP and CPO identifiers, even if it has an encryption or identification key. The «monitoring» module server collects the data l server (2) comprises all the protocol that can choose and update several connectors or ectors and the protocol associated with each CP (4) or the users of electric vehicles, by teristics of Your vehicles
[0573]
[0574] The “energy” module (1b) supply network of the charging points, the load systems.
[0575]
[0576] Renders authorization, control, storage of cargo and the energy consumed for the point of charge (5a, 5b).
[0577] provide:
[0578]
[0579] rga (CDR), storage and integration (customer relationship management (CRM),
[0580]
[0581] ): ability to integrate with the systems to ensure the stability of the network.
[0582]
[0583] we refer to a system in which the citrus vehicles (BEVs) and plug-in hybrids (PHEVs), response services on demand by accelerating their loading speed.
[0584]
[0585] For example, in Figure 7) it may contain the power consumption, the RFID date that is used to access point a), the operator (5a, 5b, Figure 1) or the location In some embodiments, the functions include sending notifications to take corrective action in case of
[0586] charging point infrastructure (4).
[0587] The functionalities of the «monitor module
[0588]
[0589] • the geolocation of events, by location, to provide an operator with the states of loading points;
[0590] • the storage of temperature events, connection blocking failure, architecture memory (1), taking into account to suggest corrective actions soul • the configuration of each event, immediately measured execution of orders to perform load.
[0591]
[0592] The management system also generates unexpected ev. For example, and without limitation: reci CP not available (4). The last events related details of the loading point (see figure 10).
[0593]
[0594] The management system implements a basic process to the upward communications communications are checked in second p and the time buffers with configurable through the CPO (5a, 5b).
[0595]
[0596] The management system ensures that cad less once a day for each CP (4).
[0597]
[0598] The events (shown, for example, in the communications figurine of the CP (4), to notify the communication does not work, the CP (4) considers the “monitoring” module (1c) s actors or operators (5a, 5b ) that an unexpected situation may occur in the
[0599]
[0600] ation »(1c) also include:
[0601]
[0602] io of at least one camera and a charging point device a quick and visual idea of
[0603]
[0604] with a critical parameter (for example, high ground connection, overload, etc.), in the account the criticality and configuration of each dinner in a database;
[0605] before the operator of the loading point, allows the ar some additional action on the points of
[0606]
[0607] Internal entities to notify of situations of a start transaction message from a swim with a CP (4) are shown on the page of
[0608]
[0609] supervision that verifies the status of the CP (4) in and down with the CP network. You are on a periodic basis. The periodicity considered within these verifications are
[0610]
[0611] A communication check is made at
[0612]
[0613] a 9) are generated when any change or change of status to the CPO is verified (5a, 5b). If any was "KO" as a state of communication global. On the other hand, if both communicate communication status of the CP is "OK".
[0614]
[0615] The CPO (5a, 5b) can be seen, for example, in Figures 11 and 12), in a manner of its infrastructure.
[0616]
[0617] The «users» module is an opci electrical module (EVu), including the charging infrastructure process, its status within the
[0618]
[0619] In some embodiments, the "users" faces comprise:
[0620]
[0621] • user management, which includes creating, reading, updating and deleting information d • providing access control via radio frequency) or similar and the authoring process • delegation of roaming purpose checking), for example, a basin final authorization check of the operad • user group management (eg load points to reduce the amount of data •
[0622] If, during the access control to an RFID card or the RFID card, a credit card is not used for the transaction
[0623]
[0624] Figure 13 shows an example of a boxes to fill with, for example, a name
[0625]
[0626] In some embodiments, the predefined report module d. They are related c as consumption, load profiles, provided by the module «reports» (s (ascending and descending) are successful, the
[0627]
[0628] on a control board (shown, by visual, an overview of the status of the CPs
[0629]
[0630] ional for the management of the vehicle user authorization necessary to access the system and the validation of those users, etc.
[0631]
[0632] cteristics or functionalities of the module
[0633]
[0634] classic operations about your information: e a user;
[0635] by means of an RFID card (identification by curl to be overcome before loading the vehicle; final authorization to another external system (with bank card, in case the service is not available;
[0636] plo, fleets) and white list distribution to transferred coughs.
[0637]
[0638] given charging point, the user does not have one correctly due to a defect, it can substitute said RFID card.
[0639]
[0640] to user interface. The interface includes user, date of birth, etc.
[0641]
[0642] and "reports" (1e, figure 1) includes a set with the activity at the loading points, such etc. The characteristics or functionalities (1e) include:
[0643]
[0644] • data analysis and generation of the operator for your organization and maximum / minimum analysis, status and use of points • provide flexible and classic reports, such as PDF, Excel and others;
[0645] • support for decision-making m that allows retrieving only the int information • orientation of an end user: any information independently of its management shows the information of several m example, figure 8);
[0646] • export of raw data.
[0647]
[0648] In some embodiments, the module d a master table. These tables, for example necessary for the configuration of the applied association with the different functions, admitted the functionalities of the module “administering internal events and the management of data from
[0649]
[0650] The "administration" module can provide
[0651]
[0652] • an attribute configuration that customize the end user interface. By "reserveable" corresponding to points d corresponding to a load point that
[0653] use for efficient use of the network or of an administrator • manage to read, update and delete;
[0654] • a management and configuration of:
[0655] - a firmware that is sent to a joint with the new image file (firmware);
[0656] - a white list or card list
[0657] Transfer of the list can be complete or CP);
[0658] reports to provide tools to the isis (load profile, events, consumption and load, ...);
[0659] Customizable. The output includes formats
[0660]
[0661] by means of the access to different teresante tools for a specific group;
[0662] Any user can easily access the technical views. In addition, the aneras system (lists, summaries and GIS, see, for
[0663]
[0664] e "administration" (1f) includes a management of 7a and 7b, which are shown in figure 14, which are the definition and definition of permits along with their rights through the management system. On the other hand, traction »(1f) includes the definition of administrators.
[0665]
[0666] ionar features such as:
[0667]
[0668] affect the behavior of the system and, for example, and without limitation, such load attributes that can be reserved or "direct" are not capable of being reserved or the user interface can be;
[0669] r classic operations such as create,
[0670]
[0671] number of CPs. The CP (4) will update its firmware
[0672]
[0673] RFID to be sent to a set of CPs (the differential, depending on the configuration of the - a grouping and load park for • external users of the CPO: a CPO (5th, to the users. The external users of the CP characteristics of the management system.
[0674]
[0675] In some embodiments, the local authorization system will have a point of identity tags, identification tags replace the current list at the point of loading to apply to the current list at the point of loading.
[0676]
[0677] The management system will send a sun PDU to a charging point. The update request PDU (complete or differential) and the number associated to the local authorization list after
[0678]
[0679] Upon receipt of a request PDU to respond with a confirmation PDU of (protocol data unit) will indicate whether the local authorization list p. If the status is update (that is, the type of management update should try to send the list of
[0680] "complete" update.
[0681]
[0682] From now on, a loading point that is «reserveable» (rCP) and a loading point qu loading «direct» (dCP).
[0683]
[0684] In some embodiments, the functions allow the operator from charging points ((dCP) to "reserve" charging points (rCP).
[0685]
[0686] The management system verifies that the planned reservation periods are reserved. The system for tracking the reservation steps and any user not identified within the deadline.
[0687] By grouping the CPs (4).
[0688] 5b) can delegate the maintenance of the CP (4) Or they only have access to a subset of the
[0689]
[0690] ema management can send a list of ga can use for ion authorization. The list can be a complete list for or it can be a differential list with changes
[0691]
[0692] Local list submission legality to send the local list submission list will contain the type of version number that the loading point owes is that it has been updated.
[0693]
[0694] sending local list, the loading point must send local list. The response from the PDU charging unit has accepted the update of "Failure" or "Version disparity" and the type of ion) was "differential", then the local authorization system completes with the type of
[0695]
[0696] e can reserve will be called charging point and cannot be reserved, it will be called point of
[0697]
[0698] "reserve" module units include CPO) change the "direct" load points
[0699]
[0700] s do not overlap and that the user arrives in the management creates internal events to perform an unforeseen incident or abnormal situation, such as Detailed reservation information for each charging point. "
[0701]
[0702] In some embodiments, the architecture with limited information exchange operations, to roaming services such as Kiwhi Pass or authorization delegation legacy systems. The set of being comprises a point loading service, a session report, a reservation service, whitelist.
[0703]
[0704] You can access the authorized point d service that interacts with the architecture by sending direct orders to the CP (4). The operations include:
[0705]
[0706] • obtain information from the CP: provided with the input identifier of the CP;
[0707] • CP status request: provide CP input identifier;
[0708] • Search charging points by distance entry and distance and returns all CPs
[0709]
[0710] The architecture, by means of the service of pun operation in real time with the systems h load (CP), such as:
[0711] • remote boot transaction:
[0712] remote start This action is useful for int • remote stop transaction: it is remote. This action is useful for integrating • unlocking plug: this pin operation.
[0713] connector is shown on the page "detail of
[0714]
[0715] tura provides a set of web services n with third-party systems, for example and without or Hubject or Ladenetz, billing systems n users (and their RFID cards) for other vices, provided by the architecture, RFID checking service, a service a reservation report service and a service
[0716]
[0717] and charge through any external system to request any information or for ions to request information about the CP (4)
[0718]
[0719] ona detailed information of the CP of agreement
[0720]
[0721] iona the status of the CP according to the
[0722]
[0723] a: takes into account the GPS coordinates of s that are available within the relationship.
[0724]
[0725] To load, it also allows the integration of erected, forwarding orders to the points of
[0726]
[0727] this operation requests the transaction of egraciones with mobile applications;
[0728] operation requests the stop transaction s with mobile applications;
[0729] request the unlocking operation of the The RFID verification service is a management that is published through a system and configuration is at a CPO level (5a, 5b
[0730]
[0731] If the local user authorization, within the yes is responsible for confirming whether users load.
[0732]
[0733] The session report service, consume web service that is published by an external systems if the related information c • send the detailed load log the load transaction (user, start, stop • send progress status changes, error) .
[0734]
[0735] The management system publishes the reservation web service to facilitate automated access for • reservation: this operation requests the request can be accepted, rejects alternative), or marked as scheduled concurrent other reservation,
[0736] • reservation update: this specific reservation operates. The request can be from alternative CPs), or marked as concurrent, has scheduled another reservation,
[0737] • cancel the reservation: this operation ca • reservation search: this operation the details,
[0738] • reservation search: this operation some specific criteria.
[0739]
[0740] The reservation reporting service, used published by an external system. The web service configur, consumed by the xterno system. Its use and location is configurable. The ).
[0741]
[0742] Stema management, is not activated, this web service are authorized to initiate transactions of
[0743]
[0744] or by the management system, it is also an external stema. This web service communicates to on the flow of cargo transactions:
[0745] (CDR) with detailed information about ion, CP, connector and consumption);
[0746] the load transaction (start, stop,
[0747]
[0748] Reserve with the main operations of ara:
[0749] Programming a new reservation. He gives it (which provides a CP list because in that period of time the RFID has
[0750]
[0751] tion requests to update some data of an eptada, rejected (which provides an entity list because in that period of time the RFID
[0752]
[0753] reserve a previous reservation,
[0754] look for a specific reservation and get all
[0755]
[0756] returns a list of reservations that meet
[0757]
[0758] By the management system, it is a ration web service is at a CPO level. System management uses this web service to notify (reserved, confirmed, error, canceled, expi
[0759]
[0760] The white list service is published through white list distribution to the CPs. This RFID cards and is responsible for distributing the CPs of the CPO network in the background.
[0761]
[0762] In some embodiments, the reservation system now at a loading point for a specific identification tag.
[0763]
[0764] To request a reservation, the ges system now to a loading point. The management system
[0765]
[0766] Upon receipt of a request PDU respond with a re-confirmation PDU
[0767]
[0768] If the identification of the reservation (identifies coincides with a reservation at the point of loading the reservation or reservations with the new reservation or r
[0769]
[0770] If the reservation ID does not match then the charging point must return when booking a connector. The specified dev connector load point is busy. The
[0771] "BUSY" when the point or connector identification tag. The connector recharge point is in the fault state AVAILABLE "if the charging point or connector charge point will return" REJECTED "if e
[0772]
[0773] If the charging point accepts the request to re-enter the incoming identification tags on the incoming identification tag or the identification tag or identification tag, all changes to the status of the reservation (irate, busy, completed, occupied).
[0774]
[0775] you the management system to automate the web service receives a new whitelist in an asynchronous way this white list for all
[0776]
[0777] management can issue a request PDU reserve a connector for use through a
[0778]
[0779] tion will send a reservation request PDU tion can specify a connector to reserve.
[0780]
[0781] Reserve now, the charging point should be served now.
[0782]
[0783] dor of the reservation or reservations) in the request to, then the loading point must replace reservations in the request.
[0784]
[0785] with no reservation at the point of loading, the status value "ACCEPTED" if it succeeds will forget "BUSY" if the point of loading or the point of charge must also return to charge has been reserved for the same or another to be returned " FAIL "if the load point or lo. The charging point must return "NO to is in the unavailable state. It is configured to not accept reservations.
[0786]
[0787] Serva will then deny the load for all reserved connector, except when the matrix identification eta match the reserve matrix cation.
[0788]
[0789] When the configuration key "Connector" TRUE ", the charging point supports re connector in the reservation request is 0, or specific connector, but it will ensure the reservation validity, a connector remains reserved. If the configuration key" C set or not to "FALSE", the car point
[0790]
[0791] If the matrix identification tag in the continuation, to determine the label of the incoming identification tag, the authorization point or authorization cache. If authorization caching is not done, then the authorization point (authorization request) for the management. The confirmation response of (parent identity).
[0792]
[0793] The reservation will be terminated at the point for the reserved identification label reserved connector or any connector when or (ii) when the specified expiration time is reached), or (iii) when the AVAILABLE p is established ".
[0794]
[0795] If a transaction is initiated for the load label, it will send the identification of the res transaction (start of transaction request reservation is terminated.
[0796]
[0797] When a reservation expires, the connector recharging point becomes available. The charging point notify the management system that the connector
[0798]
[0799] If the charging point has implemented a c a reserve configuration PDU now, zero reserve supported "is set to servas on connector 0. If the identifier of the nces the charging point shall not reserve one of which at any time during The EC available for the onector zero reserve ID tag supported "has been returned" REJECTED ".
[0800]
[0801] Reservation has a value (which is optional), to matrix dentification that is associated with a cargo one you can search your local list in the local authorization list or load you must send a request for an incoming identification tag to the authorization system contains the matrix identifier
[0802]
[0803] of load when: (i) a transaction is initiated or the matrix identification label and in the do the identifier of the reserved connector is 0, located on the expiration date (period of load point or connector in "FAIL" or "NO
[0804]
[0805] of reserved identification, then the erva point in the PDU of start request of the n) to notify the management system that the
[0806]
[0807] ga will terminate the reservation and will have to send a status notification for reserved is now available.
[0808]
[0809] Aché de authorization, then, upon receiving the charging point you must update the entry of cache, if the identification tag is not of identification tag identification information) of the response as described
[0810]
[0811] In some embodiments, a configurable time interval point for allowing charging point is still connected.
[0812]
[0813] The charging point will send a PDU from soli management system knows that a charge point
[0814]
[0815] Upon receipt of a request PDU, respond with a current pulse configuration of the management system, which is recommended to synchronize its internal clock.
[0816]
[0817] The loading point may omit the sending of a PDU has been sent to the management system This implies that a management system must each time a PDU has been received, from the push request.
[0818] With JSON (JavaScript object notation) it is mandatory. However, for synchronization a pulse every 24 hours.
[0819]
[0820] The management system also offers a set • interoperability, using the standard system in its interfaces (web services with open load point protocol (OCPP)
[0821] at all levels in all parts and blocking of suppliers and facilitates the integration • guaranteed security to distingut (transport layer security) to communications, encryption of sensitive data and information in the web interface;
[0822] tá in the local authorization list, with the citation value (information related to the ibe tag in the authorization cache.
[0823]
[0824] loading sends a pulse after a go that the management system knows that a
[0825]
[0826] Pressing key to make sure the a is still active.
[0827]
[0828] d press, the management system must be on. The response PDU will contain the store time that is used by the point of
[0829]
[0830] na Pulse request PDU when another within the configured pulse interval. assume the availability of a charging point the same way you would when receiving a PDU
[0831]
[0832] About WebSocket, sending beats not ation of time is advised to send at least
[0833]
[0834] along with features such as:
[0835] ema management protocols communication n electromobility stakeholders and with CPs) to boost interoperability involved. The use of standards avoids the company's n;
[0836] The levels ranging from the use of TLS to the use of digital certificates in the database and access restricted to the • traceability to guarantee what infrastructure and critical messages, for error;
[0837] • a multi-language function for any language. This feature was applied to messages sent to the end user, registered
[0838] • an integration platform
[0839] control cargo infrastructure;
[0840] • rich client interfaces and graphics the large amount of information generate information of the points of loading in tie avoiding the searches of complex data;
[0841] • software as a service (SaaS), to save costs and ensure information function. A SaaS is a soft model installed on remote servers instead of e
[0842]
[0843] The management system may also include charge point manufacturers. This process demonstrates the integration of its open c products, such as the management system. A manufacturer of the charging point will get a c management system. This certification allows the validation process to include an s in order to confirm the correct integration of the management system and the load points).
[0844]
[0845] The present application describes various features of the figures and / or various modes of realization of the technical characteristics of one mode with characteristics of another opposite embodiment, or unless the combination does not include technical problems mentioned in the techniques described in a mode In effect, all changes will be stored to ensure a complete reversal in case of
[0846]
[0847] ensure that the solution can be adapted to different levels: the user interface, ros, etc .;
[0848]
[0849] and gateway to manage and
[0850]
[0851] to provide a visual system, due to a, that allows you to see at a glance all the real mpo (geolocation, status, alarms ...)
[0852]
[0853] , the management system is offered as a complete SaaS with secure access to the commercial ware in which said software is a user's computer.
[0854]
[0855] A validation process oriented towards them allows the manufacturers of charge points on a charge point control system once the integration has been verified, the certificate that demonstrates compatibility with the use of a management system seal.
[0856] erie of activities to be carried out by both parties n between the two technological platforms (the
[0857]
[0858] Technical characteristics and advantages with reference to n. Those skilled in the art will understand that the given embodiment may in fact be combined with ion, unless expressly stated to be provided by a solution to at least one of these applications. In addition, the given ation characteristics can be isolated from the others. technical characteristics of this embodiment, contrary.
[0859]
[0860] It should be obvious to those skilled in the technical embodiment in many specific invention ways as claimed. In conse they should be considered as illustrations, but scope of the appended claims, and given above.
[0861] unless explicitly stated
[0862]
[0863] Since the present invention allows ways of not departing from the scope of application of the present invention, the present embodiments can be modified in the area defined by the invention should not be limited to the details

权利要求:
Claims (10)
[1]
1. A "reserve" module comprising computer-executable instructions for managing the reservation process of at least one charging point of at least one network of charging points managed by a system comprising at least one management server (2 ), at least one database (3) for storing information related to the charging points (4), of said network, at least one hardware and software architecture (1) comprising at least said "reserve" module, computer architecture (1) comprising at least one communication means (6a, 6b) for exchanging information with the charging point (4) and / or an external system and / or a user or mobile device, at least one memory for data storage and a processor to execute a program stored in memory to implement the functionalities of at least the "reserve" module, said module being characterized by the fact that, through the execution of its executable instructions by computer, provides at least one communication interface, with a user interface comprising tools to allow the user to remotely choose at least one type of connector that corresponds to a given vehicle, and at least one communication with a point-of-point infrastructure loading of the operator's network (5a, 5b) for the reception of said information in the charging system and to proceed with a reservation in the network under the control of the management system.
[2]
2. A "reserve" module according to claim 1, characterized in that by executing its executable instructions by computer, it disables on the server the functionalities of:
• block a connector inside a charging point (4), to be used only by means of a specific identification card and during the reservation period;
or
• remotely block a connector of a charging point (4), to be used only by the information contained in the user-specific identification card for a period of reservation time, by means of a remote device or a remote communication interface , and then unlock the connector chosen at the charging point (4) by means of the identification card used to block said connector.
[3]
3. A "reserve" module according to claim 1 or 2, characterized in that by executing its computer executable instructions triggers the following behavior: if the charging point accepts the reservation request, then, will deny the charge for all incoming identification tags on the reserved connector, except when an incoming identification tag or matrix identification tag matches the identification tag or matrix identification tag of the reservation.
[4]
4. A "reserve" module according to claim 1 or 2, characterized in that, by executing its computer executable instructions, it performs the following operations: when the zero-connector reservation parameter supported by a module of «Charging point», is set to "TRUE", the charging point supports reservations on connector 0; If the connector identifier in the reservation request is 0, then the charging point should not reserve a specific connector, but will ensure that at any time during the term of the reservation, a connector remains available for the identification tag reserved.
[5]
5. A "reserve" module according to claim 1 or 2, characterized in that, by executing its executable instructions by computer, it performs the following operations: terminating a reservation at the loading point, when (i) a transaction is initiated for the reserved identification tag or the matrix identification tag and on the reserved connector or any connector when the identifier of the reserved connector is 0, or (ii) when the specified time is reached on the date of expiration, or (ii) when the charging point or connector is set to "FAIL" or "NOT AVAILABLE".
[6]
6. A "reserve" module according to claim 1 or 2, characterized in that, by executing its executable instructions by computer, it enables the management system to request a charging point to unlock a connector when The charging point sends a protocol data unit, PDU, of the connector unlock request.
[7]
7. A "reserve" module according to claim 6, characterized in that after a call from the EV conductors in the assistance service of load point operator, CPO, an operator could manually activate the sending of a request to unlock the connector at the charging point, forcing a new attempt to unlock the connector.
[8]
8. A "reserve" module according to claim 7, characterized in that, by means of the execution of its executable instructions by computer, upon receiving a protocol data unit, PDU, of request for unlocking the connector, the charging point responds with a protocol data unit, PDU, unlock confirmation of the connector; The protocol data unit, PDU, response indicates whether the charging point was able to unlock its connector; or if there was an ongoing transaction in the specific connector, and the load point ends the transaction for the first time.
[9]
9. A "reserve" module according to claim 2 or 3 or 5 or 6, characterized in that, by executing its computer executable instructions, it enables the operator of charging points (5a, 5b) to Switch from the "direct" state of the charging points (4) to the "reserveable" state of the charging points (4).
[10]
10. A "reserve" module according to claim 2 or 3 or 5 or 6, characterized in that, by means of the execution of its executable instructions by computer, it verifies that the reservations do not overlap and that the user reaches the planned reservation periods and, internal events are created to track the reservation steps and any unexpected incident or abnormal situation.

类似技术:

---

公开号 | 公开日 | 专利标题

---

ES2674979B1|2019-04-09|Infrastructure management of vehicle charging points and their system

---

ES2718648A2|2019-07-03|Infrastructure management of vehicle charging points and their system |

---

CN105229986B|2019-02-12|Cross-domain services layer resource is propagated

---

CN103312660B|2016-06-22|A kind of service implementation method based on ability open platform and ability open platform

---

CN102479413B|2014-10-22|Network invoicing system and method thereof

---

CN107341925A|2017-11-10|Electric automobile networked system platform based on micro services and realize charging method

---

CN106652218A|2017-05-10|Time-sharing system and method for electric automobile and system service structure

---

CN103944968A|2014-07-23|Heterogeneous medical data information integration and sharing system based on home-based care for the aged

---

CN102684903A|2012-09-19|Management platform, system and method for realizing access of multiple cloud storage resource nodes

---

CN109948371A|2019-06-28|The method and relevant apparatus of letter of identity are provided for block chain node

---

CN104599086A|2015-05-06|Online storage cabinet grid inventory management and grid resource reservation method

---

CN106980971A|2017-07-25|T BOX, vehicle-mounted payment system and its method based on T BOX

---

CN107146124A|2017-09-08|A kind of implementation method, system and the device of electronics one-way ticket

---

CN104919483A|2015-09-16|Method, device and service provision means for authenticating a customer for a service to be provided by a service provision means

---

CN108881000A|2018-11-23|Gateway, third-party platform, payment system and method

---

US20140337172A1|2014-11-13|Fuel distribution network

---

CN106652220A|2017-05-10|Electrical vehicle time-sharing rental system and method, and system communication frame

---

CN101561847A|2009-10-21|Medical information system and medical information processing method

---

AU2014101665A4|2020-04-23|A residential management system

---

CN106652221A|2017-05-10|Cluster architecture type central server and electric vehicle time-sharing lease system and method

---

CN103714454A|2014-04-09|Queuing and payment system

---

Kobashi et al.2020|Smart city and ICT infrastructure with vehicle to X applications toward urban decarbonization

---

Vaidya et al.2018|Deployment of secure EV charging system using open charge point protocol

---

CN110049040A|2019-07-23|To the methods, devices and systems of the control authority authorization of smart machine

---

CN103685145A|2014-03-26|Security information interaction system, security information interaction device and security information interaction method

同族专利:

---

公开号 | 公开日

---

JP2018124987A|2018-08-09|

---

US20180189900A1|2018-07-05|

---

ES2718648R1|2019-07-19|

---

CN108268956A|2018-07-10|

---

BR102017028329A2|2019-01-08|

---

EP3342632A1|2018-07-04|

引用文献:

---

公开号 | 申请日 | 公开日 | 申请人 | 专利标题

---

---

US8085034B2|2008-10-31|2011-12-27|Yaniv Sirton|Managing charging of electric vehicles|

---

US20120173292A1|2011-01-05|2012-07-05|James Solomon|Reservable electric vehicle charging groups|

---

JP5814378B2|2011-09-05|2015-11-17|株式会社日立製作所|Reservation management device, reservation management program, reservation management system|

---

EP2578997B1|2011-10-07|2020-01-08|Hitachi, Ltd.|System for supporting a user of an electrically driven vehicle|

---

JP5986749B2|2012-01-18|2016-09-06|クラリオン株式会社|Reservation system, navigation device, charger and server|

---

US20140114448A1|2012-10-19|2014-04-24|Chris Outwater|Method and apparatus for sharing electric vehicle and electric appliance usage data|

---

US9475399B2|2013-02-20|2016-10-25|General Electric Company|Power conduit, charging device, and method of charging a power storage device|

---

US20160264011A1|2013-10-08|2016-09-15|Ayudante, Inc|Vehicle charging stand management system|

---

DE102014221754A1|2014-10-27|2016-04-28|Robert Bosch Gmbh|A method of performing an automatic parking operation of a vehicle|CN111216587A|2018-11-23|2020-06-02|北京嘀嘀无限科技发展有限公司|Power supply method, charging method, power supply equipment and equipment to be charged|

---

DE102019107071A1|2019-03-20|2020-09-24|Innogy Se|Charging station for charging electric vehicles|

---

WO2021000015A1|2019-07-02|2021-01-07|Jet Charge Pty Ltd|Electric vehicle charging system|

法律状态:
2018-04-26| FC2A| Grant refused|Effective date: 20180420 |

---

2019-07-03| BA2A| Patent application published|Ref document number: 2718648 Country of ref document: ES Kind code of ref document: A2 Effective date: 20190703 |

---

2019-07-19| EC2A| Search report published|Ref document number: 2718648 Country of ref document: ES Kind code of ref document: R1 Effective date: 20190712 |

---

2020-08-06| FC2A| Grant refused|Effective date: 20200731 |

优先权:

---

申请号 | 申请日 | 专利标题

---

ES201631735A|ES2718648R1|2016-12-30|2016-12-30|Infrastructure management of vehicle charging points and their system|ES201631735A| ES2718648R1|2016-12-30|2016-12-30|Infrastructure management of vehicle charging points and their system|

---

US15/849,796| US20180189900A1|2016-12-30|2017-12-21|Vehicle charging points infrastructure management and its system|

---

JP2017246374A| JP2018124987A|2016-12-30|2017-12-22|Management of vehicle charging point infrastructure and system therefor|

---

BR102017028329A| BR102017028329A2|2016-12-30|2017-12-27|allocation module|

---

CN201711476980.2A| CN108268956A|2016-12-30|2017-12-29|Vehicular charging point infrastructure management and its system|

---

EP17211158.5A| EP3342632A1|2016-12-30|2017-12-29|Vehicle charging points infrastructure management and its system|