Processing method and device of charging request, and start code for charging service
Patent Information
- Application Number
- CN202310945679.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2023-04-18
- Publication Date
- 2026-09-18
- Estimated Expiration
- 2043-04-18
AI Technical Summary
[0003]而现有技术中,充电枪的二维码通常是充电服务运营商根据电力运营商提供的每一个充电枪的身份标识信息生产的,也就是说每个二维码与一个特定的充电枪具有对应关系,这样工作人员在进行二维码的张贴时,需要从逐张核实二维码与充电枪的对应关系,极大的降低了工作人员的工作效率,甚至出现由于张贴错误导致的“张冠李戴”的现象
[0091]This application designs a charging service system, which includes a startup code, a charging server, and a front-end application. The startup code is affixed to an appropriate location on the corresponding charging gun, and the front-end application can be deployed on a user's mobile terminal, etc. The charging service system can connect to a charging pile management system. The charging service system is user-facing, providing charging services to devices waiting to be charged; the charging pile management system is user-facing, primarily responsible for managing the charging guns at charging piles within the charging area. In this application's charging service system, each charging gun has an interoperability code containing supplier identification information representing the charging gun's identity. The correspondence between the startup code and the charging gun can be established through the startup code... The activation code is established with the interoperability code affixed to the charging gun. This correspondence is not formed by pulling or editing the information of the interoperability code. That is, the activation code does not directly include the information of the interoperability code. Instead, the activation code has a unique resource location identifier. An activation code can establish a correspondence with any interoperability code through this unique resource location identifier. Furthermore, when the activation code is affixed to any charging gun, after establishing a correspondence between the activation code and the interoperability code of that charging gun, a correspondence is established between the activation code and the charging gun. After establishing the correspondence between all charging guns and their respective activation codes, this correspondence is preloaded into the charging server of the charging service system. When charging a device, the user scans and parses the activation code of a charging gun in a charging pile at the charging station using a front-end application. The user obtains a unique resource location identifier (RMI) indicated by the activation code. The front-end application generates a charging request containing the RMI based on the unique RMI and sends it to the charging server. The charging server uses the pre-loaded correspondence between the activation code and the charging gun, and the unique RMI of the charging request, to determine the identification information of the charging gun indicated by the charging request on the supply side. This information is then sent to the charging pile management system. The charging pile management system activates the corresponding target charging gun based on the supply side identification information to charge the device. In the charging request processing method provided in this application, when deploying activation codes, the staff of the charging service operator do not need to search for a specific activation code from a pile of activation codes when affixing an activation code to a charging gun. They can simply select any one to affix, which greatly improves the efficiency of charging station construction and avoids the possibility of incorrect activation code affixing. It also avoids charging failures caused by inconsistent gun codes, greatly improves the efficiency and accuracy of charging gun activation code deployment, and further improves the user's charging efficiency and user experience. Moreover, the algorithm is simple, has low computing power requirements, is highly practical, and has a wide range of applications.
Smart Images

Figure CN117218765B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of new energy technology, specifically to a method and apparatus for processing charging requests, and a startup code for charging services. Background Technology
[0002] With the widespread use of new energy vehicles, the demand for charging is increasing. In existing technologies, taking the charging service for new energy vehicles as an example, each charging gun at a charging station typically has a QR code, which users can scan to initiate the charging service. During the construction of charging stations, staff need to affix the QR codes to the appropriate locations on the charging guns.
[0003] In existing technologies, the QR codes on charging guns are usually produced by charging service operators based on the identification information of each charging gun provided by the power operator. In other words, each QR code corresponds to a specific charging gun. As a result, when staff post the QR codes, they need to verify the correspondence between each QR code and the charging gun, which greatly reduces the efficiency of the staff and may even lead to the phenomenon of "misattribution" due to incorrect posting. Summary of the Invention
[0004] In response to the above-mentioned situation, this application proposes a charging request processing method and apparatus, and a startup code for charging services, to overcome or partially overcome the shortcomings of the prior art.
[0005] In a first aspect, embodiments of this application provide a method for processing charging requests. This method is applied to the charging server of a charging service system and includes:
[0006] The system receives a charging request from a target charging gun sent by a front-end application. The charging request is generated by the front-end application parsing the activation code of the charging gun in the scanned charging pile and based on the unique resource location identifier indicated by the obtained activation code. The correspondence between the activation code of a charging gun and the charging gun is established based on the activation code and the interoperability code that represents the identity of the charging gun, and the activation code does not contain interoperability code information.
[0007] Based on the preloaded correspondence between the startup code and the charging gun, the supplier identification information of the charging gun indicated by the charging request is determined and sent to the charging pile management system to start the target charging gun to charge the device to be charged.
[0008] Optionally, in the above-described method for processing charging requests, the charging service system is also communicatively connected to the charging operation management system; the correspondence between the activation code and the charging pile is established according to the following method:
[0009] The charging operation management system parses the scanned activation code to obtain the unique resource location identifier indicated by the activation code;
[0010] The charging operation management system parses the interconnection code of the scanned charging gun to obtain the supplier identification information of the charging gun;
[0011] Establish a mapping relationship between the unique resource location identifier and the supplier identification information, so as to establish a correspondence between the activation code and the charging gun.
[0012] Optionally, in the above-mentioned charging request processing method, the charging request of the target charging gun carries a unique resource location identifier, which includes at least charging service provider information, charging gun server identifier information, and configuration information.
[0013] The determination of the supplier identification information of the charging gun indicated by the charging request, based on the pre-loaded correspondence between the startup code and the charging gun, includes:
[0014] The server identifier information of the charging gun is retrieved from the correspondence between the startup code and the charging gun to determine the supplier identifier information corresponding to the server identifier information of the charging gun, which is then used as the supplier identifier information of the charging gun indicated by the charging request.
[0015] Optionally, in the above-described method for processing charging requests, the supplier identification information of the charging gun is at least one of the following: charging gun ID number, charging gun account, charging gun unique code, and charging gun exclusive number.
[0016] Optionally, the above-mentioned method for processing charging requests also includes:
[0017] Before sending the supply end identification information of the target charging gun to the charging pile management system, the verification information of the target charging gun is collected, and the availability of the target charging gun is verified based on the verification information.
[0018] If the verification result is successful, the supplier identification information is sent to the charging pile management system to activate the target charging gun.
[0019] Optionally, in the above-described method for processing charging requests, the step of collecting verification information of the target charging gun and verifying the availability of the target charging gun based on the verification information includes:
[0020] Extract the data to be verified from the verification information. The data to be verified includes at least one of the following: the supplier identification information of the charging gun, the equipment authentication interface, the status availability, the commissioning status, the operating price strategy, and the fault code.
[0021] Based on the preset charging gun verification rules, each item in the data to be verified is verified separately. If all verification results are passed, the verification result of the usability of the target charging gun is determined to be passed.
[0022] Optionally, in the above-described method for processing charging requests, the step of verifying each item in the data to be verified based on preset charging gun verification rules includes:
[0023] Determine whether the supplier identification information of the charging gun conforms to the preset format rules and is consistent with the supplier identification information of the charging gun indicated by the charging request;
[0024] If so, then determine whether the device authentication interface is valid;
[0025] If so, determine whether the stated availability status is available;
[0026] If so, then determine whether the commissioning status is "currently in operation";
[0027] If so, determine whether the operating pricing strategy has been acquired;
[0028] If so, determine whether the target charging gun is faulty based on the preloaded fault configuration file and the fault code;
[0029] If not, the verification result for the availability of the target charging gun is deemed to be passed;
[0030] The above verification steps can be executed in a different order.
[0031] Optionally, the above-mentioned method for processing charging requests also includes:
[0032] Before sending the supplier identification information of the target charging gun to the charging pile management system, or before collecting the verification information of the target charging gun and verifying the availability of the target charging gun based on the verification information, the charging pile management system sends a plug-in signal. The plug-in signal is generated when a user inserts the charging gun of a charging pile into the charging port of the device to be charged, and is collected and sent to the charging service system by the charging pile management system.
[0033] Based on the insertion signal, it is determined that the candidate charging gun indicated by the insertion signal has been inserted into the charging port of the device to be charged;
[0034] Determine whether the supplier identification information of the candidate charging gun and the target charging gun are consistent. If they are consistent, proceed to the step of sending the supplier identification information of the target charging gun to the charging pile management system, or collecting the verification information of the target charging gun and verifying the availability of the target charging gun based on the verification information.
[0035] Optionally, in the above-mentioned method for processing charging requests, the front-end application can be any one of a merchant client, a personal user client, a mini-program, or a public account.
[0036] Secondly, embodiments of this application also provide a charging request processing apparatus, the charging request processing apparatus comprising:
[0037] The receiving unit is used to receive a charging request from a target charging gun sent by a front-end application. The charging request is generated by the front-end application parsing the activation code of the charging gun in the scanned charging pile and based on the unique resource location identifier indicated by the obtained activation code. The correspondence between the activation code of a charging gun and the charging gun is established based on the activation code and the interoperability code that represents the identity of the charging gun, and the activation code does not contain interoperability code information.
[0038] The activation unit is used to determine the supplier identification information of the charging gun indicated by the charging request based on the correspondence between the preloaded activation code and the charging gun, and send it to the charging pile management system to activate the target charging gun to charge the device to be charged.
[0039] Thirdly, this application embodiment also provides a startup code for charging services, the startup code having a unique resource location identifier;
[0040] The activation code has a pre-established one-to-one correspondence with the unique resource location identifier and the interoperability code that represents the identity of the charging gun, and the activation code does not include the interoperability code information.
[0041] The activation code is used by users to scan through a front-end application to activate the corresponding charging gun during the charging service system's provision of charging services to the device to be charged.
[0042] Optionally, in the above-mentioned activation code for charging services, the correspondence between the activation code and the interoperability code is established through a mapping method.
[0043] Optionally, in the aforementioned activation code for charging services, the correspondence between the activation code and the interoperability code is established through the charging operation management system according to the following method:
[0044] Parse the scanned startup code to obtain the unique resource location identifier indicated by the startup code;
[0045] The interconnection code of the scanned charging gun is parsed to obtain the supplier identification information of the charging gun;
[0046] Establish a mapping relationship between the unique resource location identifier and the supplier identification information, so as to establish a correspondence between the activation code and the interconnection code.
[0047] Optionally, in the aforementioned startup code for charging services, the unique resource location identifier includes at least charging service provider information, charging gun server identifier information, and configuration information. The mapping relationship between the unique resource location identifier and the supplier identifier information is established by establishing a mapping relationship between the charging gun server identifier information and the supplier identifier information.
[0048] Fourthly, embodiments of this application also provide a method for deploying a charging gun activation code, the method being applied to a charging operation management system, the charging operation management system being communicatively connected to a charging service system; the method for deploying the charging gun activation code includes:
[0049] Take any one of the multiple candidate startup codes as the target startup code. After the target startup code is attached to a charging gun, the unique resource location identifier indicated by the target startup code is obtained by scanning.
[0050] By scanning and parsing the interoperability code affixed to a charging gun, the supplier identification information of the charging gun can be obtained;
[0051] Establish a mapping relationship between the unique resource location identifier and the supplier identification information, so as to establish a correspondence between the activation code and the charging gun.
[0052] Optionally, in the above-described method for deploying the charging gun startup code, the unique resource location identifier includes at least the charging service provider information, the charging gun server identifier information, and the configuration information.
[0053] The supplier identification information of the charging gun is at least one of the following: charging gun ID number, charging gun account, charging gun unique code, and charging gun exclusive number.
[0054] Fifthly, embodiments of this application also provide a device for deploying a charging gun activation code, the device comprising:
[0055] The first scanning unit is used to take any one of the multiple candidate startup codes as the target startup code, and after the target startup code is attached to a charging gun, it obtains the unique resource location identifier indicated by the target startup code by scanning.
[0056] The second scanning unit is used to obtain the supplier identification information of the charging gun by scanning and parsing the interoperability code affixed to a charging gun;
[0057] The mapping establishment unit is used to establish a mapping relationship between the unique resource location identifier and the supplier identification information, so as to establish a correspondence between the activation code and the charging gun.
[0058] Sixthly, this application embodiment also provides a charging service system, which includes a front-end application, a startup code, and a charging server. The front-end application and the charging server are communicatively connected. The charging service system communicates with a charging pile management system, which is responsible for managing at least one charging pile in at least one charging station. The charging service system controls the charging guns of the charging piles in the charging station to charge the devices to be charged through the charging pile management system.
[0059] The front-end application parses the activation code of the charging gun in the scanned charging pile to obtain the unique resource location identifier indicated by the activation code. The correspondence between the activation code of a charging gun and the charging gun is established based on the activation code and the interoperability code that represents the identity of the charging gun, and the activation code does not contain interoperability code information.
[0060] The front-end application generates a charging request for the target charging gun based on the determined unique resource location identifier and sends it to the charging server.
[0061] The charging server is used to determine the supplier identification information of the charging gun indicated by the charging request based on the correspondence between the preloaded activation code and the charging gun, and send it to the charging pile management system to start the target charging gun to charge the device to be charged.
[0062] Optionally, in the above-mentioned charging service system, the charging service system is also communicatively connected to the charging operation management system; the correspondence between the activation code and the charging gun is established according to the following method:
[0063] The charging operation management system is used to parse the scanned activation code to obtain the unique resource location identifier indicated by the activation code;
[0064] The charging operation management system is used to parse the interconnection code of the scanned charging gun to obtain the supplier identification information of the charging gun.
[0065] Establish a mapping relationship between the unique resource location identifier and the supplier identification information, so as to establish a correspondence between the activation code and the charging gun.
[0066] Optionally, in the above-mentioned charging service system, the charging request of the target charging gun carries a unique resource location identifier, which includes at least charging service provider information, charging gun server identification information, and configuration information.
[0067] The charging server is used to search the charging gun server identification information in the correspondence between the startup code and the charging gun, and determine the supplier identification information corresponding to the charging gun server identification information, which is then used as the supplier identification information of the charging gun indicated by the charging request.
[0068] Optionally, in the above-mentioned charging service system, the supplier identification information of the charging gun is at least one of the following: charging gun ID number, charging gun account, charging gun unique code, and charging gun exclusive number.
[0069] Optionally, in the above charging service system, the charging server is further configured to collect the verification information of the target charging gun before sending the supplier identification information of the target charging gun to the charging pile management system, and to verify the availability of the target charging gun based on the verification information.
[0070] If the verification result is successful, the supplier identification information is sent to the charging pile management system to activate the target charging gun.
[0071] Optionally, in the above charging service system, the charging server is used to extract data to be verified from the verification information. The data to be verified includes at least one of the following: supplier identification information of the charging gun, equipment authentication interface, status availability, commissioning status, operating price strategy, and fault code.
[0072] Based on the preset charging gun verification rules, each item in the data to be verified is verified separately. If all verification results are passed, the verification result of the usability of the target charging gun is determined to be passed.
[0073] Optionally, in the above charging service system, the charging server is used to determine whether the supplier identification information of the charging gun conforms to a preset format rule and is consistent with the supplier identification information of the charging gun indicated by the charging request.
[0074] If so, then determine whether the device authentication interface is valid;
[0075] If so, determine whether the stated availability status is available;
[0076] If so, then determine whether the commissioning status is "currently in operation";
[0077] If so, determine whether the operating pricing strategy has been acquired;
[0078] If so, determine whether the target charging gun is faulty based on the preloaded fault configuration file and the fault code;
[0079] If not, the verification result for the availability of the target charging gun is deemed to be passed;
[0080] The above verification steps can be executed in a different order.
[0081] Optionally, in the above-mentioned charging service system, before the charging server sends the supplier identification information of the target charging gun to the charging pile management system, or before collecting the verification information of the target charging gun and verifying the availability of the target charging gun based on the verification information, it receives a gun insertion signal pushed by the charging pile management system. The gun insertion signal is generated when a user inserts a charging gun of a charging pile into the charging port of the device to be charged, and is collected and pushed to the charging service system by the charging pile management system.
[0082] Based on the insertion signal, it is determined that the candidate charging gun indicated by the insertion signal has been inserted into the charging port of the device to be charged;
[0083] Determine whether the supplier identification information of the candidate charging gun and the target charging gun are consistent. If they are consistent, proceed to the step of sending the supplier identification information of the target charging gun to the charging pile management system, or collecting the verification information of the target charging gun and verifying the availability of the target charging gun based on the verification information.
[0084] Optionally, in the above-mentioned charging service system, the charging pile management system includes a charging pile server and at least one charging pile operating system that are connected in communication. Each of the charging pile operating systems is connected to a plurality of charging piles, and the charging pile server is connected in communication to the charging server of the charging service system.
[0085] The charging server is used to send the supplier identification information of the target charging gun to the charging pile server, so that the charging pile server forwards it to the corresponding charging pile operating system, so that the charging pile operating system controls the corresponding charging gun to start, in order to charge the device to be charged.
[0086] Optionally, in the above charging service system, the charging server communicates with the charging pile server through an interconnection protocol, and the charging server and the charging pile server exchange information through an interface; the charging pile server communicates with the operating system of each charging pile through a direct connection protocol.
[0087] Optionally, in the above charging service system, the front-end application can be any one of a merchant client, a personal user client, a mini-program, or a public account.
[0088] In a seventh aspect, embodiments of this application also provide an electronic device, including: a processor; and a memory arranged to store computer-executable instructions, which, when executed, cause the processor to perform any of the charging methods or the deployment method of the charging gun activation code described above.
[0089] Eighthly, embodiments of this application also provide a computer-readable storage medium storing one or more programs that, when executed by an electronic device including multiple applications, cause the electronic device to perform any of the charging methods or the deployment method of the charging gun activation code described above.
[0090] The above-described technical solutions adopted in the embodiments of this application can achieve the following beneficial effects:
[0091] This application designs a charging service system, which includes a startup code, a charging server, and a front-end application. The startup code is affixed to an appropriate location on the corresponding charging gun, and the front-end application can be deployed on a user's mobile terminal, etc. The charging service system can connect to a charging pile management system. The charging service system is user-facing, providing charging services to devices waiting to be charged; the charging pile management system is user-facing, primarily responsible for managing the charging guns at charging piles within the charging area. In this application's charging service system, each charging gun has an interoperability code containing supplier identification information representing the charging gun's identity. The correspondence between the startup code and the charging gun can be established through the startup code... The activation code is established with the interoperability code affixed to the charging gun. This correspondence is not formed by pulling or editing the information of the interoperability code. That is, the activation code does not directly include the information of the interoperability code. Instead, the activation code has a unique resource location identifier. An activation code can establish a correspondence with any interoperability code through this unique resource location identifier. Furthermore, when the activation code is affixed to any charging gun, after establishing a correspondence between the activation code and the interoperability code of that charging gun, a correspondence is established between the activation code and the charging gun. After establishing the correspondence between all charging guns and their respective activation codes, this correspondence is preloaded into the charging server of the charging service system. When charging a device, the user scans and parses the activation code of a charging gun in a charging pile at the charging station using a front-end application. The user obtains a unique resource location identifier (RMI) indicated by the activation code. The front-end application generates a charging request containing the RMI based on the unique RMI and sends it to the charging server. The charging server uses the pre-loaded correspondence between the activation code and the charging gun, and the unique RMI of the charging request, to determine the identification information of the charging gun indicated by the charging request on the supply side. This information is then sent to the charging pile management system. The charging pile management system activates the corresponding target charging gun based on the supply side identification information to charge the device. In the charging request processing method provided in this application, when deploying activation codes, the staff of the charging service operator do not need to search for a specific activation code from a pile of activation codes when affixing an activation code to a charging gun. They can simply select any one to affix, which greatly improves the efficiency of charging station construction and avoids the possibility of incorrect activation code affixing. It also avoids charging failures caused by inconsistent gun codes, greatly improves the efficiency and accuracy of charging gun activation code deployment, and further improves the user's charging efficiency and user experience. Moreover, the algorithm is simple, has low computing power requirements, is highly practical, and has a wide range of applications. Attached Figure Description
[0092] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:
[0093] Figure 1 A schematic diagram of the structure of a charging service system according to an embodiment of this application is shown;
[0094] Figure 2 A schematic diagram illustrating an application scenario according to an embodiment of this application is shown;
[0095] Figure 3 A flowchart illustrating a method for processing a charging request according to an embodiment of this application is shown;
[0096] Figure 4 A flowchart illustrating a method for deploying a charging gun activation code according to an embodiment of this application is shown.
[0097] Figure 5 A flowchart illustrating the verification of the availability of a target charging gun according to an embodiment of this application is shown.
[0098] Figure 6 A flowchart illustrating a method for processing a charging request according to another embodiment of this application is shown;
[0099] Figure 7 A schematic diagram of a charging request processing apparatus according to an embodiment of this application is shown;
[0100] Figure 8 A schematic diagram of a device for deploying a charging gun activation code according to an embodiment of this application is shown.
[0101] Figure 9 This is a schematic diagram of the structure of an electronic device according to an embodiment of this application. Detailed Implementation
[0102] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0103] The technical solutions provided by the various embodiments of this application are described in detail below with reference to the accompanying drawings.
[0104] Currently, the charging industry primarily relies on users scanning QR codes to initiate charging services. Therefore, during the construction of charging stations, staff need to deploy activation codes on the charging guns. In existing technology, the QR codes on charging guns are typically produced by the charging service operator based on the identification information of each charging gun provided by the power operator. This means each QR code corresponds to a specific charging gun. Consequently, when affixing a QR code to a charging gun, staff need to verify the correspondence between each QR code and the charging gun from a pool of codes until they find the correct one. This reduces the efficiency of deploying the charging gun activation codes and can even lead to incorrect QR code affixing.
[0105] Therefore, this application provides a method and apparatus for processing charging requests, a startup code for charging services, a method and apparatus for deploying charging gun startup codes, and a charging service system. The charging request processing method of this application can be implemented through the charging service system. Figure 1 A schematic diagram of the structure of a charging service system according to an embodiment of this application is shown. Figure 1 It can be seen that the charging service system 100 includes a charging server 110, a front-end application 120, and a startup code 130. The startup code 130 is affixed to the charging gun. The charging server 110 and the front-end application 120 are communicatively connected. In some embodiments of this application, the front-end application can be presented in the form of, but is not limited to, a merchant client (B-end client), a personal user client (C-end client), a mini-program, a public account, etc. The front-end application 120 can be deployed on the user's terminal device, such as a mobile phone, a tablet computer, etc. The charging server 110 is equipped with a charging request processing device 700 that can implement the charging request processing method of this application. Figure 7 ).
[0106] Users can charge their devices by scanning the charging gun's activation code using the front-end application 120. Please refer to [further details]. Figure 1 The charging service system 100 can connect to the charging pile management system 200. Specifically, the charging service system 100 can communicate with the charging pile management system 200 through a pre-agreed interconnection protocol, and data exchange can be achieved by calling an interface. The charging pile management system 200 can manage one or multiple charging piles in a charging station. The charging service system 100 controls the charging guns of the charging piles in the charging station through the charging pile management system 200 to charge the devices to be charged.
[0107] More specifically, in some embodiments of this application, the charging pile management system 200 includes a charging pile server 210 and at least one charging pile operating system 220 connected in communication. Each charging pile operating system 220 connects to several charging piles, and the charging pile server 210 manages the charging piles through the charging pile operating system 220. Externally, the charging pile server 210 is connected in communication with the charging server 110 of the charging service system 100, enabling communication between the charging service system 100 and the charging pile management system 200. In practical scenarios, a charging pile is typically equipped with two charging guns, and the charging pile operating system 220 can manage each charging gun.
[0108] The charging server 110 communicates with the charging pile server 210 through an interconnection protocol. The interconnection protocol defines the communication specifications between the charging server 110 and the charging pile server 210, and the two can exchange information through an interface. The charging pile server 210 communicates with each charging pile operating system 220 through a direct connection protocol, such as the WLAN direct connection protocol.
[0109] Figure 2 A schematic diagram illustrating an application scenario according to an embodiment of this application is shown. Figure 2 As can be seen, a user service company can be understood as an agent company that purchases electricity for users. In other words, the charging station operator does not directly deal with users, but is a user service company. Specifically, the user service company purchases electricity from the charging station operator and then sells it to users, which can be individual users or corporate users.
[0110] Figure 1 The charging service system 100 shown can be deployed at user service companies (charging service operators), and the charging pile management system 200 can be deployed at charging station operators (power operators). More specifically, the front-end application 120 of the charging service system 100 can be deployed on users' mobile terminals, such as mobile phones. The charging server 110, as the back-end server of the front-end application 120, is connected to the charging pile server 210 of the charging pile management system 200. The charging pile server 210 is typically deployed at charging station operators and is connected to the charging pile operating systems 220 deployed at various charging stations of the charging station operators. It should be noted that... Figure 2 The scenarios shown are merely illustrative examples and do not constitute any limitation on this application. The deployment of the charging service system 100 can be carried out according to actual needs, and this application does not impose any limitations.
[0111] An interoperability code is affixed to an appropriate location on the charging gun. This interoperability code is provided and deployed by the charging station operator and is mainly used for the management of the charging gun. It is an existing resource and can represent the identity information of the charging gun. Specifically, it is usually embodied in the form of supplier identification information. In some embodiments, the supplier identification information of the charging gun is at least one of the following: charging gun ID number, charging gun account, charging gun unique code, and charging gun exclusive number.
[0112] In the aforementioned charging service system, activation code 130 is an activation code used for charging services. The activation code has a unique resource location identifier. The activation code can establish a one-to-one correspondence with the interoperability code of the charging gun through its unique resource location identifier, and the activation code does not include the interoperability code information. The charging activation code is used by the user to scan through the front-end application to activate the corresponding charging gun during the process of the charging service system providing charging services to the device to be charged.
[0113] The activation code for charging services is provided by the charging service provider. In some embodiments, it can be generated and printed using the snowflake algorithm. The activation code has a unique resource location identifier (RROI), which can be, but is not limited to, a URL address. The correspondence between the activation code and the charging gun can be established by the activation code and the interoperability code affixed to the charging gun. This correspondence is not formed by extracting or editing the information from the interoperability code; that is, the activation code does not directly include the information from the interoperability code. Instead, the unique resource location identifier of the activation code is used to establish a correspondence with the interoperability code. This allows one activation code to be associated with any interoperability code. Furthermore, when the activation code is affixed to any charging gun, after establishing a correspondence between the activation code and the interoperability code of that charging gun, a correspondence is established between the activation code and that charging gun.
[0114] In some embodiments of this application, the correspondence between the activation code and the interconnection code in the above-mentioned activation code for charging service is established through a mapping method.
[0115] More specifically, in the aforementioned activation code for charging services, the correspondence between the activation code and the interoperability code is established through the charging operation management system according to the following method:
[0116] The charging operation management system parses the scanned activation code to obtain the unique resource location identifier indicated by the activation code; the charging operation management system parses the scanned interoperability code of the charging gun to obtain the supplier identification information of the charging gun; the charging operation management system then establishes a mapping relationship between the unique resource location identifier and the supplier identification information to establish a correspondence between the activation code and the interoperability code.
[0117] In some embodiments, the unique resource location identifier includes at least charging service provider information, charging gun server identifier information, and configuration information. The mapping relationship between the unique resource location identifier and the supplier identifier information is established by establishing a mapping relationship between the charging gun server identifier information and the supplier identifier information.
[0118] In some embodiments of this application, the unique resource location identifier includes at least charging service provider information, charging gun server identification information, and configuration information; the unique resource location identifier includes at least charging service provider information, charging gun server identification information, and configuration information, etc. The charging service provider information, charging gun server identification information, and configuration information can be, but are not limited to, represented in the form of a string of codes, such as the charging gun server identification information included in the startup code being 123; a startup code can establish a one-to-one correspondence with any interoperability code representing the identity of a charging gun through a mapping method using the charging gun server identification information. For example, if the code representing the supplier identification information of a charging gun in the interoperability code of a charging gun is 897, assuming the mapping relationship is 123 = 897 ("=" indicates a mapping relationship), when the startup code is affixed to a charging gun, the startup code establishes a correspondence with the identity information of the charging gun. After establishing the correspondence between all charging guns and their respective startup codes, this correspondence is preloaded into the charging server of the charging service system.
[0119] The charging process for users can be summarized as follows: The user scans and parses the activation code of a charging gun in a charging pile at the charging station using a front-end application to obtain a unique resource location identifier indicated by the activation code. The front-end application generates a charging request containing the unique resource location identifier based on the determined unique resource location identifier and sends it to the charging server. The charging server, based on the pre-loaded correspondence between the activation code and the charging gun, determines the charging gun identification information indicated by the charging request according to the unique resource location identifier of the charging request and sends it to the charging pile management system. The charging pile management system starts the corresponding target charging gun to charge the device to be charged based on the charging gun identification information.
[0120] The following section provides a more detailed explanation of this application from the perspective of the charging service provider 110. Figure 3 This diagram illustrates a flowchart of a charging request processing method according to an embodiment of this application. The charging method of this application can... Figure 1 The charging service system 100 shown implements, from Figure 3 It can be seen that this application includes at least steps S310 to S320:
[0121] Step 310: Receive a charging request from the target charging gun sent by the front-end application. The charging request is generated by the front-end application parsing the activation code of the charging gun scanned by the charging gun and based on the unique resource location identifier indicated by the obtained activation code. The correspondence between the activation code of a charging gun and the charging gun is established based on the activation code and the interoperability code that represents the identity of the charging gun, and the activation code does not contain interoperability code information.
[0122] It should be noted that the charging equipment in this application can use any new energy equipment and devices, such as charging cars, charging electric vehicles, charging robots, etc. For ease of explanation, the following will use a charging vehicle as an example.
[0123] When a user drives their vehicle to a charging station, that station is marked as the target charging station, and the vehicle can then proceed to the charging station. Figure 1 The charging service system shown charges the target charging station. Specifically, it can activate the front-end application 120 deployed on the user's mobile terminal to charge the vehicle.
[0124] An activation code is pre-affixed to an appropriate location on each charging gun in the target charging station. The user scans the activation code of a charging gun, usually a QR code, using a front-end application 120. The scanned activation code is then parsed to obtain the unique resource location identifier it indicates. Various information represented by the unique resource location identifier can be obtained. In some embodiments, this may include, but is not limited to, charging service provider information, charging gun server identification information, and configuration information. Then, a charging request for the target charging gun is generated based on this information. The charging request carries at least the charging gun server identification information.
[0125] As mentioned earlier, the correspondence between the activation code and the charging gun is established based on the activation code and the interoperability code that identifies the charging gun. The interoperability code is provided by the charging station operator (such as State Grid) and affixed to the charging gun. Each interoperability code stores the supplier identification information of the corresponding charging gun. The interoperability code is generated according to the communication protocol between the charging service system 100 and the charging pile management system 200, and can usually be recognized by the charging pile management system 200.
[0126] A unique resource location identifier (RROID) for a startup code contains server-side identification information for the charging gun, and an interoperability code for the charging gun contains supplier-side identification information for the charging gun. It's important to note that the server-side identification information in the startup code and the supplier-side identification information in the interoperability code are different; the startup code does not directly contain the information in the interoperability code. The relationship between the two can be established through mapping or other methods. For example, for a charging gun, its server-side identification information might be a randomly generated code in a specific format, such as 123. The supplier-side identification information is set by the charging station operator, and its specific form is not limited. The supplier-side identification information could be at least one of the following: charging gun ID number, charging gun account, charging gun unique code, or charging gun exclusive number. For charging guns where a correspondence between the startup code and the interoperability code has been established, the server-side identification information and the supplier-side identification information can be mapped, such as 123 = a charging gun ID number, where "=" indicates a mapping relationship.
[0127] After scanning the startup code, the front-end application determines the unique resource location identifier contained therein, and further generates a charging request for the target charging gun. In some embodiments of this application, the charging request carries the unique resource location identifier contained in the startup code. The unique resource location identifier at least contains the charging gun server identifier information of the target charging gun. In other embodiments, the unique resource location identifier may also contain charging service provider information and configuration information, and the charging request is sent to the charging server.
[0128] The charging server receives the charging request from the target charging gun and parses the charging request to obtain the information contained therein. This information includes at least the server identification information contained in the unique resource location identifier of the target charging gun, and may also include other information indicated by the unique resource location identifier, such as charging service provider information and configuration information.
[0129] Step 320: Based on the correspondence between the preloaded startup code and the charging gun, determine the supplier identification information of the charging gun indicated by the charging request, and send it to the charging pile management system to start the target charging gun to charge the device to be charged.
[0130] The charging server preloads a mapping between activation codes and charging guns. This mapping can essentially be understood as the correspondence between the server-side identification information contained in the activation code and the supplier-side identification information contained in the interoperability code of the charging gun. This mapping can be presented in the form of, but is not limited to, a configuration file. After receiving a charging request, the charging server searches the mapping between the activation code and the charging gun based on the charging gun server-side identification information to determine the supplier-side identification information corresponding to the charging gun server-side identification information, which is then used as the supplier-side identification information of the charging gun indicated by the charging request. Specifically, after obtaining the server-side identification information of the target charging gun, the charging server searches the configuration file to obtain the corresponding supplier-side identification information. This supplier-side identification information represents the identity of the target charging gun, which can be understood as which charging gun in which charging station and which charging pile. After determining the supplier identification information of the charging gun, the charging server sends a charging instruction carrying the supplier identification information to the charging pile management system. The charging pile management system then activates the target charging gun indicated by the supplier identification information according to the charging instruction, thereby realizing the charging of the device to be charged.
[0131] After determining the supplier identification information of the charging gun, the charging server 110 sends the supplier identification information to the charging pile management system 200. The charging pile management system 200 then starts the target charging gun to charge the device based on the supplier identification information. After charging is completed, the charging pile management system 200 can return the charging result to the charging server 110 of the charging service system 100 for display on the front-end application 120.
[0132] Please refer to Figure 1 Specifically, the charging server 110 sends the supplier identification information of the target charging gun to the charging pile server 210 of the charging pile management system 200. The charging pile server 210 then sends the information to the corresponding charging pile operating system 220, which controls the corresponding charging gun to start according to the charging request of the target charging gun, so as to charge the device to be charged.
[0133] During the above process, the charging server 110 communicates with the charging pile server 210 according to the interconnection protocol. Specifically, the charging server 110 and the charging pile server 210 exchange information through an interface; the charging pile server 210 communicates with each charging pile operating system 220 according to the direct connection protocol.
[0134] Depend on Figure 3As shown in the method, this application designs a charging service system. This system includes a startup code, a charging server, and a front-end application. The startup code is affixed to an appropriate location on the corresponding charging gun. The front-end application can be deployed on a user's mobile terminal, etc. The charging service system can connect to a charging pile management system. The charging service system is user-oriented, providing charging services to devices waiting to be charged. The charging pile management system is user-oriented, primarily responsible for managing the charging guns at charging piles within the charging area. In this application's charging service system, each charging gun has an interoperability code containing supplier identification information representing the charging gun's identity. The correspondence between the startup code and the charging gun is shown. An interoperability code can be established between the activation code and the interoperability code affixed to the charging gun. This correspondence is not formed by extracting or editing the information of the interoperability code; that is, the activation code does not directly include the information of the interoperability code. Instead, the activation code has a unique resource location identifier. An activation code can establish a correspondence with any interoperability code through this unique resource location identifier. Furthermore, when the activation code is affixed to any charging gun, after establishing a correspondence between the activation code and the interoperability code of that charging gun, a correspondence is established between the activation code and that charging gun. After establishing the correspondence between all charging guns and their respective activation codes, this correspondence is preloaded into the charging server of the charging service system. When charging a device, the user scans and parses the activation code of a charging gun in a charging pile at the charging station using a front-end application. The user obtains a unique resource location identifier (RMI) indicated by the activation code. The front-end application generates a charging request containing the RMI based on the unique RMI and sends it to the charging server. The charging server uses the pre-loaded correspondence between the activation code and the charging gun, and the unique RMI of the charging request, to determine the identification information of the charging gun indicated by the charging request on the supply side. This information is then sent to the charging pile management system. The charging pile management system activates the corresponding target charging gun based on the supply side identification information to charge the device. In the charging request processing method provided in this application, when deploying activation codes, the staff of the charging service operator do not need to search for a specific activation code from a pile of activation codes when affixing an activation code to a charging gun. They can simply select any one to affix, which greatly improves the efficiency of charging station construction and avoids the possibility of incorrect activation code affixing. It also avoids charging failures caused by inconsistent gun codes, greatly improves the efficiency and accuracy of charging gun activation code deployment, and further improves the user's charging efficiency and user experience. Moreover, the algorithm is simple, has low computing power requirements, is highly practical, and has a wide range of applications.
[0135] In some embodiments of this application, the charging service system is also communicatively connected to the charging operation management system; the correspondence between the activation code and the charging gun is established according to the following method: the charging operation management system is used to parse the scanned activation code to obtain the unique resource location identifier indicated by the activation code. In some embodiments, the activation code is generated by the charging service terminal based on the snowflake algorithm and sent to the charging operation management system, and the activation code has a unique resource location identifier; the charging operation management system is used to parse the interconnection code of the scanned charging gun to obtain the supplier identification information of the charging gun; and establish a mapping relationship between the unique resource location identifier and the supplier identification information to establish the correspondence between the activation code and the charging gun.
[0136] Please refer to this again. Figure 1 In some embodiments of this application, Figure 1 The charging service system 100 shown can also be connected to the charging operation management system 300. The charging operation management system 300 is designed for the operation and maintenance personnel of charging service companies. Through the charging operation management system 300, the activation codes of charging piles can be deployed and managed.
[0137] Specifically, the charging service system 100 generates many activation codes with unique resource location identifiers based on the snowflake algorithm, and sends the relevant information of the activation codes to the charging operation management system 300. The operation and maintenance personnel of the charging service company can export and print these activation codes from the charging operation management system 300, and then take them to the charging stations for deployment and posting.
[0138] Regarding the deployment of the startup code, this application provides a method for deploying a charging gun startup code. Figure 4 A flowchart illustrating a method for deploying a charging gun activation code according to an embodiment of this application is shown. Figure 4 As can be seen, the method is applied to the charging operation management system 300, and this embodiment includes at least steps S410 to S430:
[0139] Step S410: Select any one of the multiple candidate start codes as the target start code. After the target start code is affixed to a charging pile, obtain the unique resource location identifier indicated by the target start code by scanning.
[0140] Step S420: Obtain the supplier identification information of the charging gun by scanning and parsing the interoperability code affixed to a charging gun.
[0141] Step S430: Establish a mapping relationship between the unique resource location identifier and the supply end identifier information of the charging gun, so as to establish a correspondence between the activation code and the charging gun.
[0142] Before the charging service company's maintenance personnel post and deploy activation codes, they can export and print numerous activation codes generated by the charging service system 100 from the charging operation management system 300. When posting an activation code for a charging pile, they can select one from multiple activation codes as the target activation code, then post the target activation code on the charging pile. The charging operation management system 300 then scans the target activation code, obtaining a unique resource location identifier from it. This identifier is further parsed to extract information such as the charging service provider's information and the charging gun's server-side identifier. Finally, the charging operation management system is used to process the information generated by the charging station... The station operator has already scanned the interoperability code posted on the charging pile. The supplier identification information of the charging gun is parsed from the interoperability code, and then a mapping is established between the two. Specifically, a mapping relationship is established between the server identification information of the charging gun and the supplier identification information of the charging gun. The mapping relationship can be automatically generated by a certain algorithm, such as using a mapping function or Mybatis statements to establish a one-to-one mapping relationship. This application does not limit this, and existing technologies can be referred to to establish the mapping relationship. After establishing the mapping relationship between the server identification information of the charging gun and the supplier identification information of the charging gun, the correspondence between the activation code and the charging gun is established.
[0143] The unique resource location identifier includes at least the charging service provider information, the charging gun server identifier information, and the configuration information; the charging gun supplier identifier information is at least one of the following: charging gun ID number, charging gun account, charging gun unique code, and charging gun exclusive number.
[0144] To ensure high availability of the charging gun and prevent it from becoming unusable after startup, some embodiments of this application include a step of verifying the availability of the target charging gun. Specifically, in some embodiments of this application, the charging server also collects verification information of the target charging gun before sending the supplier identification information of the target charging gun to the charging pile management system, and verifies the availability of the target charging gun based on the verification information. If the verification result is successful, the supplier identification information is sent to the charging pile management system to start the target charging gun, that is, to notify the charging pile management system to start the target charging gun to enable charging of the charging equipment.
[0145] After determining the supplier identification information of the target charging gun based on the charging request sent by the front-end application 120, the charging server 110 can verify the availability of the target charging gun based on its verification information. This verification is necessary because the charging gun may malfunction or become unavailable due to network issues. To ensure the target charging gun is functioning correctly, the charging server 110 collects its verification information and verifies its availability. If the verification passes, the subsequent charging steps proceed; if the verification fails, the user is prompted to replace the charging gun.
[0146] The content and rules for verification can be configured according to actual business needs, and this application does not impose any restrictions, such as verifying whether the connection is successful, whether the target charging gun is in operation, etc.
[0147] If the verification result fails, the user needs to be prompted to replace the charging gun; if the verification result passes, the charging pile management system 200 is notified to start the target charging gun to charge the charging equipment. Specifically, the charging server 110 generates a charging gun start command and sends it to the charging pile server 210. The charging pile server 210 forwards the charging gun start command to the charging pile operating system 220 where the target charging gun is located. The charging pile operating system 220 controls the target charging pile to start according to the start command, thereby charging the equipment to be charged.
[0148] It should be noted that when the charging server 110 and the charging pile server 210 interact via an interface, it is best to verify the legitimacy of the exchanged information to ensure its security. For example, after the charging server 110 sends a charging gun start command to the charging pile server 210, the charging pile server 210 can verify the charging gun start request according to preset filtering rules. If the verification passes, the process proceeds to the next step; if the verification fails, the charging gun start request can be ignored or a warning can be issued.
[0149] In some embodiments of this application, in the above method, the step of verifying the availability of the target charging gun based on the verification information includes: extracting data to be verified from the verification information, wherein the data to be verified includes at least one of the following: charging gun supplier identification information, device authentication interface, status availability, commissioning status, operating price strategy, and charging gun obstacle code; verifying each item in the data to be verified based on preset charging gun verification rules, and if the verification results are all passed, then the verification result of the availability of the target charging gun is determined to be passed.
[0150] The method for verifying the availability of the target charging gun can be set according to actual needs. In some embodiments of this application, the data to be verified includes one or more of the following: charging gun supplier identification information, device authentication interface, status availability, commissioning status, operating price strategy, and charging gun obstacle code. Then, a preset charging gun verification rule is used to verify each item in the data to be verified. When there are multiple data items to be verified, the verification process can be parallel or serial. Since the overall verification result is only passed if all verification items pass, this application recommends using a serial method to verify each data item to be verified. In this way, if any data item fails the verification, the verification result of the availability of the target charging gun can be directly determined as failed, without the need to verify other data items.
[0151] In some embodiments of this application, in the above method, the step of verifying each item in the data to be verified based on preset charging gun verification rules can be performed in the following verification steps without changing the order: determining whether the charging gun supplier identification information conforms to preset format rules and is consistent with the charging gun supplier identification information indicated by the charging request; if so, determining whether the device authentication interface is valid; if so, determining whether the status availability is available; if so, determining whether the commissioning status is in operation; if so, determining whether the operating price strategy has been acquired; if so, determining whether the target charging gun has a fault based on the preloaded fault configuration file and the fault code; if not, determining that the verification result of the availability of the target charging gun is passed.
[0152] Figure 5 This illustration shows a flowchart of verifying the availability of a target charging gun according to one embodiment of this application. Figure 5 As can be seen, this embodiment includes:
[0153] The data to be verified is extracted from the verification information, including the charging gun ID, device authentication interface, status availability, commissioning status, and operating price strategy.
[0154] Determine whether the charging gun's identity ID conforms to the preset format rules and is consistent with the identity ID of the charging gun indicated in the recharge request. If not, determine that the verification result of the target charging gun's availability is unsuccessful.
[0155] If yes, then determine whether the device authentication interface is valid; if not, then determine that the verification result of the target charging gun's availability is unsuccessful.
[0156] If yes, then determine whether the availability status is available; if not, then determine that the verification result of the availability of the target charging gun is unsuccessful.
[0157] If yes, then determine whether the commissioning status is "in operation"; if not, then determine that the verification result of the availability of the target charging gun is "failed".
[0158] If yes, then determine whether the operating pricing strategy has been obtained; if not, then determine that the verification result for the availability of the target charging gun is unsuccessful.
[0159] If so, determine if the fault code exists in the preloaded fault configuration file; if so, determine if the verification result of the target charging gun's availability is failed.
[0160] If not, the verification result for the availability of the target charging gun is passed.
[0161] It should be noted that this application does not restrict the verification order of charging gun supplier identification information, equipment authentication interface, status availability, commissioning status, operating pricing strategy, and fault codes. The order of each piece of data to be verified will not affect the final availability verification result. Figure 5 This is merely an illustrative example; this application is not limited to this single case, and verification of other sequences is also possible. Figure 5 Similarly, we will not exhaustively list them.
[0162] In some embodiments of this application, the method further includes: before sending the supplier identification information of the target charging gun to the charging pile management system, or before collecting the verification information of the target charging gun and verifying the availability of the target charging gun based on the verification information, receiving a plug-in signal pushed by the charging pile management system, wherein the plug-in signal is generated when a user inserts a charging gun of a charging pile into the charging port of the device to be charged, and is collected and pushed to the charging service system by the charging pile management system; determining, based on the plug-in signal, that the charging gun of the candidate charging gun indicated by the plug-in signal has been inserted into the charging port of the charging vehicle; determining whether the supplier identification information of the candidate charging gun and the target charging gun are consistent, and if they are consistent, proceeding to the step of sending the supplier identification information of the target charging gun to the charging pile management system, or before collecting the verification information of the target charging gun and verifying the availability of the target charging gun based on the verification information.
[0163] To further confirm that the charging gun inserted into the charging vehicle (here referred to as the candidate charging gun) matches the target charging gun identified by scanning, the charging server 110 can verify the consistency between the candidate charging gun and the target charging gun before sending the supplier identification information of the target charging gun to the charging pile management system 200 or proceeding to the step of collecting the verification information of the target charging gun and verifying the availability of the target charging gun based on the verification information. If they match, the subsequent process is initiated; if they do not match, a prompt is displayed to remind the user to replace the charging gun.
[0164] Specifically, after a user inserts a charging gun into the charging port of a vehicle, the charging pile operating system 220 deployed at the target charging station generates a charging gun insertion signal in response to the operation and sends the signal to the charging pile server 210. The charging pile server 210 then pushes the signal to the charging server 110. After receiving the start command from the target charging gun, the charging server 110 compares the identity information of the candidate charging gun indicated by the insertion signal with the identity information of the target charging gun scanned by the user. If they match, the process proceeds to the next step, either sending the start command of the target charging gun to the charging pile management system 200 or collecting the verification information of the target charging gun and verifying its availability. If they do not match, a prompt appears on the front-end application 120, reminding the user to replace the charging gun.
[0165] Figure 6 A flowchart illustrating a method for processing a charging request according to another embodiment of this application is shown. Figure 6 As can be seen, this embodiment includes:
[0166] After the user plugs in the charging gun, the front-end application scans the activation code affixed to the appropriate location on the charging gun, parses the scanned activation code to obtain the unique resource location identifier, generates a charging request for the target gun based on the unique resource location identifier, and sends it to the charging server.
[0167] After detecting that a user has plugged in a charging gun, the charging pile operating system can push the ID of the charging gun that the user actually plugged in (candidate gun ID) to the charging pile server, and then the charging pile server can push it to the charging server.
[0168] When the charging server receives a charging request from the target gun in the front-end application, it parses the charging request, determines the target gun ID, and verifies the consistency between the candidate gun ID and the target gun ID.
[0169] If they match, the charging server retrieves the verification information of the target charging gun from the charging pile server and verifies the availability of the target gun based on the verification information.
[0170] If the verification passes, the charging server generates and sends a start command to the charging pile server. The start command contains the supplier identification information of the target gun. The charging pile server verifies the validity of the interface information of the start command. If it passes, the charging pile server sends the start command to the charging pile operating system.
[0171] The charging pile operating system controls the corresponding charging gun to start, and after completing the charging of the vehicle, it returns the charging status to the charging pile server.
[0172] The charging station server generates a bill based on the charging status and returns it to the charging server.
[0173] The charging server sends the bill to the front-end application to remind the user to pay.
[0174] Figure 7 A schematic diagram of a charging request processing apparatus according to an embodiment of this application is shown. Figure 7 It can be seen that the charging request processing device 700 includes:
[0175] The receiving unit 710 is used to receive a charging request from a target charging gun sent by a front-end application. The charging request is generated by the front-end application parsing the activation code of the charging gun in the scanned charging pile and based on the unique resource location identifier indicated by the obtained activation code. The correspondence between the activation code of a charging gun and the charging gun is established based on the activation code and the interoperability code that represents the identity of the charging gun, and the activation code does not contain the interoperability code information.
[0176] The activation unit 720 is used to determine the charging gun identification information indicated by the charging request based on the correspondence between the preloaded activation code and the charging gun, and send it to the charging pile management system to activate the target charging gun to charge the device to be charged.
[0177] In some embodiments of this application, in the above-described charging request processing apparatus, the charging service system is also communicatively connected to the charging operation management system; the correspondence between the activation code and the charging pile is established by the following method: the charging operation management system parses the scanned activation code to obtain the unique resource location identifier indicated by the activation code; the charging operation management system parses the scanned interconnection code of the charging gun to obtain the charging gun identification information of the charging pile; a mapping relationship is established between the unique resource location identifier and the charging gun identification information to establish the correspondence between the activation code and the charging gun.
[0178] In some embodiments of this application, in the charging request processing apparatus described above, the charging request of the target charging gun carries a unique resource location identifier, which includes at least charging service provider information, charging gun server identifier information, and configuration information; the activation unit 720 is used to search the charging gun server identifier information in the correspondence between the activation code and the charging gun, and determine the supplier identifier information corresponding to the charging gun server identifier information, which is used as the supplier identifier information of the charging gun indicated by the charging request.
[0179] In some embodiments of this application, in the above-mentioned charging request processing device, the supplier identification information of the charging gun is at least one of the following: charging gun ID number, charging gun account, charging gun unique code, and charging gun exclusive number.
[0180] In some embodiments of this application, the charging request processing device further includes: a verification unit, configured to, in response to the charging request of the target charging gun, collect verification information of the target charging gun, and verify the availability of the target charging gun based on the verification information; if the verification result is passed, proceed to the step of determining the supplier identification information of the charging gun indicated by the charging request based on the pre-loaded correspondence between the startup code and the charging gun, and sending it to the charging pile management system.
[0181] In some embodiments of this application, in the above-described charging request processing apparatus, the verification unit is used to extract data to be verified from the verification information. The data to be verified includes at least one of the following: supplier identification information of the charging gun, device authentication interface, status availability, commissioning status, operating price strategy, and fault code. Based on preset charging gun verification rules, each item in the data to be verified is verified separately. If all verification results are passed, the verification result of the availability of the target charging gun is determined to be passed.
[0182] In some embodiments of this application, in the above-mentioned charging request processing device, the verification unit is used to determine whether the supplier identification information of the charging gun conforms to a preset format rule and is consistent with the supplier identification information of the charging gun indicated by the charging request; if so, it determines whether the device authentication interface is valid; if so, it determines whether the status availability is available; if so, it determines whether the commissioning status is in operation; if so, it determines whether the operating price strategy has been acquired; if so, it determines whether the target charging gun has a fault based on the pre-loaded fault configuration file and the fault code; if not, it determines that the verification result of the availability of the target charging gun is passed; the above verification steps can be executed in a different order.
[0183] In some embodiments of this application, in the above-described charging request processing apparatus, the verification unit is further configured to receive a charging gun insertion signal pushed by the charging pile management system before the steps of sending the supplier identification information of the target charging gun to the charging pile management system or collecting the verification information of the target charging gun and verifying the availability of the target charging gun based on the verification information. The charging gun insertion signal is generated when a user inserts a charging gun from a charging pile into the charging port of the device to be charged, and is collected by the charging pile management system and pushed to the charging service system. Based on the charging gun insertion signal, the unit determines that the candidate charging gun indicated by the signal has been inserted into the charging port of the device to be charged. It then determines whether the supplier identification information of the candidate charging gun is consistent with that of the target charging gun. If they are consistent, the unit proceeds to the steps of sending the supplier identification information of the target charging gun to the charging pile management system or collecting the verification information of the target charging gun and verifying the availability of the target charging gun based on the verification information.
[0184] In some embodiments of this application, in the above-described charging request processing device, the front-end application is any one of a merchant client, a personal user client, a mini-program, or a public account.
[0185] It should be noted that the above-mentioned charging request processing device can implement the aforementioned charging request processing method one by one, and will not be described again.
[0186] Figure 8 A schematic diagram of a deployment device for a charging gun activation code according to an embodiment of this application is shown. Figure 8 It can be seen that the deployment device 800 for the charging gun activation code includes:
[0187] The first scanning unit 810 is used to take any one of the multiple candidate startup codes as the target startup code, and after the target startup code is attached to a charging gun, it obtains the unique resource location identifier indicated by the target startup code by scanning.
[0188] The second scanning unit 820 is used to obtain the supplier identification information of the charging gun by scanning and parsing the interoperability code affixed to a charging gun.
[0189] The mapping establishment unit 830 is used to establish a mapping relationship between the unique resource location identifier and the supplier identification information, so as to establish a correspondence between the start code and the charging gun.
[0190] In some embodiments of this application, in the above-mentioned charging gun activation code deployment device, the unique resource location identifier includes at least charging service provider information, charging gun server identifier information, and configuration information; the charging gun supplier identifier information is at least one of the following: charging gun ID card number, charging gun account, charging gun unique code, and charging gun exclusive number.
[0191] It should be noted that the above-mentioned charging gun activation code deployment device can implement the aforementioned charging gun activation code deployment method, and will not be described again.
[0192] Figure 9 This is a schematic diagram of the structure of an electronic device according to an embodiment of this application. Please refer to it. Figure 9 At the hardware level, the electronic device includes a processor, and optionally also includes an internal bus, a network interface, and memory. The memory may include main memory, such as high-speed random-access memory (RAM), or non-volatile memory, such as at least one disk drive. Of course, the electronic device may also include other hardware required for other business operations.
[0193] The processor, network interface, and memory can be interconnected via an internal bus, which can be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, or an EISA (Extended Industry Standard Architecture) bus, etc. This bus can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 9 The symbol is represented by a single double-headed arrow, but this does not mean that there is only one bus or one type of bus.
[0194] Memory is used to store programs. Specifically, programs may include program code, which includes computer operation instructions. Memory may include main memory and non-volatile memory, and provides instructions and data to the processor.
[0195] The processor reads the corresponding computer program from non-volatile memory into main memory and then runs it, forming a deployment device for the charging device or charging gun startup code at the logical level. The processor executes the program stored in memory and specifically performs the aforementioned method.
[0196] The above is as stated in this application. Figure 7 or Figure 8The method executed by the charging request processing device or the charging gun activation code deployment device disclosed in the illustrated embodiments can be applied to a processor or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. In implementation, each step of the above method can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor can be a general-purpose processor, including a Central Processing Unit (CPU), a Network Processor (NP), etc.; it can also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of this application can be directly embodied as being executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software module can reside in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.
[0197] The electronic device can also perform Figure 7 or Figure 8 The illustrated embodiment discloses a method executed by a charging request processing device or a charging gun activation code deployment device, and implements the charging request processing device or the charging gun activation code deployment device in... Figure 7 or Figure 8 The functions of the embodiments shown are not described in detail here.
[0198] This application also proposes a computer-readable storage medium that stores one or more programs, the programs including instructions that, when executed by an electronic device including multiple applications, enable the electronic device to perform... Figure 7 or Figure 8 The method executed by the charging request processing device or the charging gun activation code deployment device disclosed in the illustrated embodiment is specifically used to execute the aforementioned method.
[0199] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
[0200] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.
[0201] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.
[0202] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.
[0203] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.
[0204] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.
[0205] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.
[0206] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.
[0207] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
[0208] The above description is merely an embodiment of this application and is not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.
Claims
1. A method for processing charging requests, characterized in that, The charging request processing method is applied to the charging server of the charging service system, and the charging request processing method includes: The system receives a charging request from a target charging gun sent by a front-end application. The charging request is generated by the front-end application parsing the activation code of the charging gun in the charging pile and scanning it, and based on the unique resource location identifier indicated by the obtained activation code. The correspondence between the activation code of a charging gun and the charging gun is established by the charging operation management system based on the unique resource location identifier indicated by the activation code and the interoperability code that represents the identity of the charging gun. The activation code does not contain interoperability code information. The interoperability code is affixed to an appropriate position on the charging gun to represent the identity information of the charging gun. Based on the preloaded correspondence between the startup code and the charging gun, the supplier identification information of the charging gun indicated by the charging request is determined and sent to the charging pile management system to start the target charging gun to charge the device to be charged. The activation code is provided by the charging service company, and the charging service system is deployed on the charging service company. The interoperability code is provided by the charging station operator, and the charging pile management system is deployed on the charging station operator. The charging service system communicates with the charging pile management system and with the charging operation management system, but the charging operation management system does not communicate with the charging pile management system. The correspondence between the activation code and the charging pile is established according to the following method: The charging operation management system parses the scanned activation code to obtain the unique resource location identifier indicated by the activation code; The charging operation management system parses the interconnection code of the scanned charging gun to obtain the supplier identification information of the charging gun; Establish a mapping relationship between the unique resource location identifier and the supplier identification information, so as to establish a correspondence between the activation code and the charging gun.
2. The method for processing charging requests according to claim 1, characterized in that, The charging request of the target charging gun carries a unique resource location identifier, which includes at least charging service provider information, charging gun server identifier information, and configuration information. The determination of the supplier identification information of the charging gun indicated by the charging request, based on the pre-loaded correspondence between the startup code and the charging gun, includes: The server identifier information of the charging gun is retrieved from the correspondence between the startup code and the charging gun to determine the supplier identifier information corresponding to the server identifier information of the charging gun, which is then used as the supplier identifier information of the charging gun indicated by the charging request.
3. The method for processing charging requests according to claim 1, characterized in that, The supplier identification information of the charging gun is at least one of the following: charging gun ID number, charging gun account, charging gun unique code, and charging gun exclusive number.
4. The method for processing charging requests according to claim 1, characterized in that, The method further includes: Before sending the supply end identification information of the target charging gun to the charging pile management system, the verification information of the target charging gun is collected, and the availability of the target charging gun is verified based on the verification information. If the verification result is successful, the supplier identification information is sent to the charging pile management system to activate the target charging gun.
5. The method for processing charging requests according to claim 4, characterized in that, The step of collecting the verification information of the target charging gun and verifying the availability of the target charging gun based on the verification information includes: Extract the data to be verified from the verification information. The data to be verified includes at least one of the following: the supplier identification information of the charging gun, the equipment authentication interface, the status availability, the commissioning status, the operating price strategy, and the fault code. Based on the preset charging gun verification rules, each item in the data to be verified is verified separately. If all verification results are passed, the verification result of the usability of the target charging gun is determined to be passed.
6. The method for processing charging requests according to claim 5, characterized in that, The method, based on preset charging gun verification rules, verifies each item in the data to be verified, including: Determine whether the supplier identification information of the charging gun conforms to the preset format rules and is consistent with the supplier identification information of the charging gun indicated by the charging request; If so, then determine whether the device authentication interface is valid; If so, determine whether the stated availability status is available; If so, then determine whether the commissioning status is "currently in operation"; If so, determine whether the operating pricing strategy has been acquired; If so, determine whether the target charging gun is faulty based on the preloaded fault configuration file and the fault code; If not, the verification result for the availability of the target charging gun is deemed to be passed; The above verification steps can be executed in a different order.
7. The method for processing charging requests according to claim 4, characterized in that, The method further includes: Before sending the supplier identification information of the target charging gun to the charging pile management system, or before collecting the verification information of the target charging gun and verifying the availability of the target charging gun based on the verification information, the charging pile management system sends a plug-in signal. The plug-in signal is generated when a user inserts the charging gun of a charging pile into the charging port of the device to be charged, and is collected and sent to the charging service system by the charging pile management system. Based on the insertion signal, it is determined that the candidate charging gun indicated by the insertion signal has been inserted into the charging port of the device to be charged; Determine whether the supplier identification information of the candidate charging gun and the target charging gun are consistent. If they are consistent, proceed to the step of sending the supplier identification information of the target charging gun to the charging pile management system, or collecting the verification information of the target charging gun and verifying the availability of the target charging gun based on the verification information.
8. The method for processing a charging request according to any one of claims 1 to 7, characterized in that, The front-end application can be any one of the following: merchant client, personal user client, mini-program, or public account.
9. A charging request processing apparatus, characterized in that, The charging request processing device includes: The receiving unit is used to receive a charging request from a target charging gun sent by a front-end application. The charging request is generated by the front-end application parsing the activation code of the charging gun in the charging pile and scanning it, and based on the unique resource location identifier indicated by the obtained activation code. The correspondence between the activation code of a charging gun and the charging gun is established by the charging operation management system based on the unique resource location identifier indicated by the activation code and the interoperability code that represents the identity of the charging gun. The activation code does not contain interoperability code information. The interoperability code is affixed to an appropriate position on the charging gun to represent the identity information of the charging gun. The activation unit is used to determine the supplier identification information of the charging gun indicated by the charging request based on the correspondence between the preloaded activation code and the charging gun, and send it to the charging pile management system to activate the target charging gun to charge the device to be charged. The activation code is provided by the charging service company, and the charging service system is deployed on the charging service company. The interoperability code is provided by the charging station operator, and the charging pile management system is deployed on the charging station operator. The charging service system communicates with the charging pile management system and with the charging operation management system, but the charging operation management system does not communicate with the charging pile management system. The correspondence between the activation code and the charging pile is established according to the following method: The charging operation management system parses the scanned activation code to obtain the unique resource location identifier indicated by the activation code; The charging operation management system parses the interconnection code of the scanned charging gun to obtain the charging gun identification information of the charging pile; Establish a mapping relationship between the unique resource location identifier and the charging gun identifier information, so as to establish a correspondence between the activation code and the charging gun.
10. The charging request processing apparatus according to claim 9, characterized in that, The charging request of the target charging gun carries a unique resource location identifier, which includes at least charging service provider information, charging gun server identifier information, and configuration information. The activation unit is used to search the charging gun server identification information in the correspondence between the activation code and the charging gun, and determine the supplier identification information corresponding to the charging gun server identification information, which is then used as the supplier identification information of the charging gun indicated by the charging request.
11. The charging request processing apparatus according to claim 9, characterized in that, The supplier identification information of the charging gun is at least one of the following: charging gun ID number, charging gun account, charging gun unique code, and charging gun exclusive number.
12. The charging request processing apparatus according to claim 9, characterized in that, The device further includes: a verification unit for collecting verification information of the target charging gun before sending the supply end identification information of the target charging gun to the charging pile management system, and verifying the availability of the target charging gun based on the verification information; If the verification result is successful, the supplier identification information is sent to the charging pile management system to activate the target charging gun.
13. The charging request processing apparatus according to claim 12, characterized in that, The verification unit is used to extract data to be verified from the verification information. The data to be verified includes at least one of the following: the supplier identification information of the charging gun, the equipment authentication interface, the status availability, the commissioning status, the operating price strategy, and the fault code. Based on the preset charging gun verification rules, each item in the data to be verified is verified separately. If all verification results are passed, the verification result of the usability of the target charging gun is determined to be passed.
14. The charging request processing apparatus according to claim 13, characterized in that, The verification unit is used to determine whether the supplier identification information of the charging gun conforms to the preset format rules and is consistent with the supplier identification information of the charging gun indicated by the charging request. If so, then determine whether the device authentication interface is valid; If so, determine whether the stated availability status is available; If so, then determine whether the commissioning status is "currently in operation"; If so, determine whether the operating pricing strategy has been acquired; If so, determine whether the target charging gun is faulty based on the preloaded fault configuration file and the fault code; If not, the verification result for the availability of the target charging gun is deemed to be passed; The above verification steps can be executed in a different order.
15. The charging request processing apparatus according to claim 12, characterized in that, The verification unit is also used to receive a plug-in signal pushed by the charging pile management system before sending the supply end identification information of the target charging gun to the charging pile management system, or before collecting the verification information of the target charging gun and verifying the availability of the target charging gun based on the verification information. The plug-in signal is generated when a user inserts the charging gun of a charging pile into the charging port of the device to be charged, and is collected by the charging pile management system and pushed to the charging service system. Based on the insertion signal, it is determined that the candidate charging gun indicated by the insertion signal has been inserted into the charging port of the device to be charged; Determine whether the supplier identification information of the candidate charging gun and the target charging gun are consistent. If they are consistent, proceed to the step of sending the supplier identification information of the target charging gun to the charging pile management system, or collecting the verification information of the target charging gun and verifying the availability of the target charging gun based on the verification information.
16. The charging request processing apparatus according to any one of claims 9 to 15, characterized in that, The front-end application can be any one of the following: merchant client, personal user client, mini-program, or public account.
17. A startup code for charging services, characterized in that, The startup code has a unique resource location identifier; The activation code is pre-established through the charging operation management system based on the unique resource location identifier and the interoperability code that represents the identity of the charging gun, and the activation code does not include the interoperability code information. The interoperability code is affixed to the appropriate location on the charging gun; The activation code is used by users to scan through a front-end application to activate the corresponding charging gun during the charging service system's process of providing charging services to the device to be charged. The activation code is provided by the charging service company, and the charging service system is deployed on the charging service company. The interoperability code is provided by the charging station operator, and the charging pile management system is deployed on the charging station operator. The charging service system communicates with the charging pile management system and with the charging operation management system, but the charging operation management system does not communicate with the charging pile management system. The correspondence between the activation code and the interoperability code is established through the charging operation management system according to the following method: Parse the scanned startup code to obtain the unique resource location identifier indicated by the startup code; The interconnection code of the scanned charging gun is parsed to obtain the supplier identification information of the charging gun; Establish a mapping relationship between the unique resource location identifier and the supplier identification information, so as to establish a correspondence between the activation code and the interconnection code.
18. The activation code for charging services according to claim 17, characterized in that, The unique resource location identifier includes at least charging service provider information, charging gun server identifier information, and configuration information. The mapping relationship between the unique resource location identifier and the supplier identifier information is established by establishing a mapping relationship between the charging gun server identifier information and the supplier identifier information.
19. A method for deploying a charging gun activation code, characterized in that, The method for deploying the charging gun activation code is applied to the charging operation management system, which is communicatively connected to the charging service system. The activation code is provided by the charging service company, and the charging service system is deployed at the charging service company. The interoperability code is provided by the charging station operator, and the charging pile management system is deployed at the charging station operator. The charging service system communicates with the charging operation management system, but the charging operation management system does not communicate with the charging pile management system. The method for deploying the charging gun activation code includes: One of the multiple candidate activation codes is taken as the target activation code. After the target activation code is affixed to a charging pile, the unique resource location identifier indicated by the target activation code is obtained by scanning. The candidate activation codes are generated by the charging service system. By scanning and parsing the interoperability code affixed to a charging gun, the supplier identification information of the charging gun can be obtained; the interoperability code is affixed to an appropriate location on the charging gun. Establish a mapping relationship between the unique resource location identifier and the supplier identification information of the charging gun, so as to establish a correspondence between the activation code and the charging gun.
20. The method for deploying the charging gun activation code according to claim 19, characterized in that, The unique resource location identifier includes at least the charging service provider information, the charging gun server identifier information, and the configuration information; The supplier identification information of the charging gun is at least one of the following: charging gun ID number, charging gun account, charging gun unique code, and charging gun exclusive number.
21. A device for deploying a charging gun activation code, characterized in that, The device for deploying the charging gun activation code is deployed in the charging operation management system, which is communicatively connected to the charging service system. The activation code is provided by the charging service company, and the charging service system is deployed at the charging service company. The interoperability code is provided by the charging station operator, and the charging pile management system is deployed at the charging station operator. The charging service system communicates with the charging operation management system, but the charging operation management system does not communicate with the charging pile management system. The device for deploying the charging gun activation code includes: The first scanning unit is used to take any one of a plurality of candidate activation codes as the target activation code. After the target activation code is attached to a charging gun, the unique resource location identifier indicated by the target activation code is obtained by scanning. The candidate activation codes are generated by the charging service system. The second scanning unit is used to obtain the supplier identification information of a charging gun by scanning and parsing an interoperability code affixed to a charging gun; the interoperability code is affixed to an appropriate position on the charging gun. The mapping establishment unit is used to establish a mapping relationship between the unique resource location identifier and the supplier identification information, so as to establish a correspondence between the activation code and the charging gun.
22. The device for deploying the charging gun activation code according to claim 21, characterized in that, The unique resource location identifier includes at least the charging service provider information, the charging gun server identifier information, and the configuration information; The supplier identification information of the charging gun is at least one of the following: charging gun ID number, charging gun account, charging gun unique code, and charging gun exclusive number.
23. A charging service system, characterized in that, The charging service system includes a front-end application, a startup code, and a charging server. The front-end application and the charging server are communicatively connected. The charging service system communicates with a charging pile management system. The charging pile management system is responsible for managing at least one charging pile in at least one charging station. The charging service system controls the charging guns of the charging piles in the charging station to charge the devices to be charged through the charging pile management system. The front-end application parses the activation code of the charging gun in the charging pile and obtains the unique resource location identifier indicated by the activation code. The correspondence between the activation code of a charging gun and the charging gun is established by the charging operation management system based on the unique resource location identifier indicated by the activation code and the interoperability code that represents the identity of the charging gun. The activation code does not contain interoperability code information. The interoperability code is affixed to an appropriate position on the charging gun to represent the identity information of the charging gun. The front-end application generates a charging request for the target charging gun based on the determined unique resource location identifier and sends it to the charging server. The charging server is used to determine the supplier identification information of the charging gun indicated by the charging request based on the correspondence between the preloaded activation code and the charging gun, and send it to the charging pile management system to start the target charging gun to charge the device to be charged. The activation code is provided by the charging service company, the charging service system is deployed by the charging service company, the interoperability code is provided by the charging station operator, and the charging pile management system is deployed by the charging station operator. The charging service system is also communicatively connected to the charging operation management system, which does not communicate with the charging pile management system; the correspondence between the activation code and the charging gun is established according to the following method: The charging operation management system is used to parse the scanned activation code to obtain the unique resource location identifier indicated by the activation code; The charging operation management system is used to parse the interconnection code of the scanned charging gun to obtain the supplier identification information of the charging gun. Establish a mapping relationship between the unique resource location identifier and the supplier identification information, so as to establish a correspondence between the activation code and the charging gun.
24. The charging service system according to claim 23, characterized in that, The charging request of the target charging gun carries a unique resource location identifier, which includes at least charging service provider information, charging gun server identifier information, and configuration information. The charging server is used to search the charging gun server identification information in the correspondence between the startup code and the charging gun, and determine the supplier identification information corresponding to the charging gun server identification information, which is then used as the supplier identification information of the charging gun indicated by the charging request.
25. The charging service system according to claim 23, characterized in that, The supplier identification information of the charging gun is at least one of the following: charging gun ID number, charging gun account, charging gun unique code, and charging gun exclusive number.
26. The charging service system according to claim 23, characterized in that, The charging server is also used to collect the verification information of the target charging gun before sending the supplier identification information of the target charging gun to the charging pile management system, and to verify the availability of the target charging gun based on the verification information. If the verification result is successful, the supplier identification information is sent to the charging pile management system to activate the target charging gun.
27. The charging service system according to claim 26, characterized in that, The charging server is used to extract data to be verified from the verification information. The data to be verified includes at least one of the following: supplier identification information of the charging gun, device authentication interface, status availability, commissioning status, operating price strategy, and fault code. Based on the preset charging gun verification rules, each item in the data to be verified is verified separately. If all verification results are passed, the verification result of the usability of the target charging gun is determined to be passed.
28. The charging service system according to claim 27, characterized in that, The charging server is used to determine whether the supplier identification information of the charging gun conforms to the preset format rules and is consistent with the supplier identification information of the charging gun indicated by the charging request. If so, then determine whether the device authentication interface is valid; If so, determine whether the stated availability status is available; If so, then determine whether the commissioning status is "currently in operation"; If so, determine whether the operating pricing strategy has been acquired; If so, determine whether the target charging gun is faulty based on the preloaded fault configuration file and the fault code; If not, the verification result for the availability of the target charging gun is deemed to be passed; The above verification steps can be executed in a different order.
29. The charging service system according to claim 26, characterized in that, The charging server is also used to receive a plug-in signal pushed by the charging pile management system before sending the supplier identification information of the target charging gun to the charging pile management system, or before collecting the verification information of the target charging gun and verifying the availability of the target charging gun based on the verification information. The plug-in signal is generated when a user inserts a charging gun of a charging pile into the charging port of the device to be charged, and is collected and pushed to the charging service system by the charging pile management system. Based on the insertion signal, it is determined that the candidate charging gun indicated by the insertion signal has been inserted into the charging port of the device to be charged; Determine whether the supplier identification information of the candidate charging gun and the target charging gun are consistent. If they are consistent, proceed to the step of sending the supplier identification information of the target charging gun to the charging pile management system, or collecting the verification information of the target charging gun and verifying the availability of the target charging gun based on the verification information.
30. The charging service system according to any one of claims 23 to 29, characterized in that, The charging pile management system includes a charging pile server and at least one charging pile operating system connected in communication. Each charging pile operating system is connected to a number of charging piles, and the charging pile server is connected in communication to the charging server of the charging service system. The charging server is used to send the supplier identification information of the target charging gun to the charging pile server, so that the charging pile server forwards it to the corresponding charging pile operating system, so that the charging pile operating system controls the corresponding charging gun to start, in order to charge the device to be charged.
31. The charging service system according to claim 30, characterized in that, The charging server communicates with the charging pile server via an interconnection protocol, and the charging server and the charging pile server exchange information through an interface; the charging pile server communicates with the operating system of each charging pile via a direct connection protocol.
32. The charging service system according to any one of claims 23 to 29, characterized in that, The front-end application can be any one of the following: merchant client, personal user client, mini-program, or public account.
33. An electronic device, comprising: processor; as well as A memory configured to store computer-executable instructions, characterized in that, when executed, the executable instructions cause the processor to perform the method according to any one of claims 1 to 8 or any one of claims 19 to 20.
34. A computer-readable storage medium storing one or more programs, characterized in that, When the one or more programs are executed by an electronic device including multiple applications, the electronic device causes the electronic device to perform the method according to any one of claims 1 to 8 or any one of claims 19 to 20.
Citation Information
Patent Citations
Shared washing machine binding system and method based on three-dimensional barcode
CN109243100A
Electric vehicle and charging management method and device thereof
CN109376889A
Charging control system, method and electric vehicle
CN112977116A