Software-defined charging pile system implementation method, system, charging pile and equipment

Abstract

The present application relates to the technical field of charging pile system development, and provides a method, system, charging pile and device for implementing a software-defined charging pile system, obtaining configuration requirement information of the charging pile system, the configuration requirement information including at least one type of functional requirement; determining the target functional module to be configured from the functional module library based on the configuration requirement information, the target functional module corresponding to the type of functional requirement; for each target functional module, configuring the target functional module based on the functional requirement corresponding to the functional module to obtain the configured target functional module; in the case that the necessary functional modules are not missing in each configured target functional module, splicing each configured target functional module to obtain a charging pile system. By adopting the above technical solution, the charging pile system can be freely combined at the software level through functional modules, so that it is easy to realize efficient and flexible configuration of the charging pile system, and form a customized system that meets customer needs.

Description

Technical Field

[0001] The present application relates to the technical field of charging pile system development, and in particular to a method, system, charging pile and equipment for implementing a software-defined charging pile system. Background Art

[0002] With the rapid development of the new energy industry, users' demands for charging piles are becoming increasingly diversified and complex. In order to meet the needs of different user groups and application scenarios, the design of charging pile systems has become more and more complex and diversified.

[0003] The charging pile system in related technologies mainly defines product functions and module configurations through hardware and firmware. This approach lacks flexibility and is difficult to adapt to rapidly developing customer and market demands. Therefore, how to achieve efficient and flexible configuration of the charging pile system has become a technical problem that needs to be solved urgently. Summary of the invention

[0004] In order to facilitate efficient and flexible configuration of a charging pile system, the present application provides a method, system, charging pile and device for implementing a software-defined charging pile system.

[0005] In the first aspect, the present application provides a method for implementing a software-defined charging pile system, which adopts the following technical solution:

[0006] A method for implementing a software-defined charging pile system, the method comprising:

[0007] Acquire configuration requirement information of the charging pile system, where the configuration requirement information includes at least one type of functional requirement;

[0008] Determining a target functional module to be configured from a functional module library based on the configuration requirement information, wherein the target functional module corresponds to a type of the functional requirement;

[0009] For each of the target functional modules, configuring the target functional module based on the functional requirements corresponding to the functional module to obtain a configured target functional module;

[0010] Determine whether necessary functional modules are missing in each of the configured target functional modules;

[0011] In the case that the necessary functional modules are not missing in each of the configured target functional modules, each of the configured target functional modules is spliced ​​together to obtain the charging pile system.

[0012] By adopting the above technical solution, the target functional modules can be determined according to the configuration information, and the target functional modules can be configured based on the functional requirements. Finally, the configured target functional modules can be spliced ​​to obtain the charging pile system. In this way, the charging pile system can be freely combined at the software level through functional modules, which can facilitate the efficient and flexible configuration of the charging pile system and form a customized system that meets customer needs.

[0013] Optionally, the determining whether necessary functional modules are missing in each of the configured target functional modules includes:

[0014] In the case where the necessary functional modules are missing from each of the configured target functional modules, determining the missing necessary functional modules as supplementary functional modules;

[0015] configuring the supplementary function module to obtain a configured supplementary function module;

[0016] The post-configuration target function modules and the post-configuration supplementary function modules are spliced ​​together to obtain the charging pile system.

[0017] By adopting the above technical solution, necessary functional modules can be automatically supplemented when the user does not customize them, which can help avoid errors in the generation process of the charging pile system and also help ensure the effectiveness of the ultimately generated charging pile system.

[0018] Optionally, the charging pile system is obtained by splicing the post-configuration target function modules and the post-configuration supplementary function modules, including:

[0019] Splicing each of the configured target function modules and the configured supplementary function modules to obtain a spliced ​​system;

[0020] Performing a functional test on the spliced ​​system to determine whether the spliced ​​system has functional abnormalities;

[0021] In the case where the system after splicing has a functional abnormality, determining whether the abnormal function corresponds to the post-configuration supplementary function module;

[0022] In the case where the function with the abnormality corresponds to the post-configuration supplementary function module, determining a reference requirement corresponding to the abnormal supplementary function module with the abnormality;

[0023] The abnormal supplementary function module is configured based on the reference requirement to regenerate the configured supplementary function module corresponding to the abnormal supplementary function module, and the step of returning to execute splicing each of the configured target function modules and the configured supplementary function module to obtain a spliced ​​system, and performing a functional test on the spliced ​​system to determine whether there is any functional abnormality in the spliced ​​system.

[0024] By adopting the above technical solution, when a functional abnormality of the spliced ​​system is detected, the functional abnormality of the spliced ​​system can be automatically processed to regenerate the spliced ​​system, which can help improve the degree of automation in the charging pile system generation process.

[0025] Optionally, the reference requirements corresponding to the abnormal supplementary function module determined to have an abnormality include:

[0026] Determine whether there is a first association module in each of the configured target function modules that has an association relationship with the abnormal supplementary function module;

[0027] In the case where the first association module exists, the reference requirement is determined based on the functional requirement corresponding to the first association module.

[0028] By adopting the above-mentioned technical solution, when there is a first associated module with the abnormal supplementary functional module in the configured functional module, the reference requirements can be determined based on the functional requirements corresponding to the first associated module. This can help match the reference requirements with the functional requirements of the first associated module, thereby avoiding module functional abnormalities caused by functional conflicts between functional modules with associated relationships.

[0029] Optionally, the configuration target function modules are spliced ​​together to obtain the charging pile system, including:

[0030] Splicing each of the configured target functional modules to obtain a spliced ​​system;

[0031] Performing a functional test on the spliced ​​system to determine whether the spliced ​​system has functional abnormalities;

[0032] In the case that the spliced ​​system has a functional abnormality, determining an abnormal target functional module corresponding to the function with the abnormality from each of the configured target functional modules;

[0033] Determine, from each of the configured target function modules, a second association module that has an association relationship with the abnormal target function module;

[0034] For each of the second association modules, determining whether the functional requirement corresponding to the second association module matches the functional requirement corresponding to the abnormal target functional module;

[0035] When the functional requirement corresponding to the second associated module does not match the functional requirement corresponding to the abnormal target functional module, matching abnormality prompt information corresponding to the second associated module and the abnormal target functional module is output to prompt the matching abnormality between the modules.

[0036] By adopting the above technical solution, the cause of the system functional abnormality can be determined when the system has functional abnormality after splicing, so as to guide the correction of the system generation process to regenerate a system without functional abnormality, which can help improve the efficiency of system generation.

[0037] Optionally, the configuration target function modules are spliced ​​together to obtain the charging pile system, including:

[0038] Determining the dependency relationship between each of the configured target functional modules;

[0039] Constructing a dependency tree between each of the configured target function modules based on the dependency;

[0040] Based on the dependency tree, each of the configured target functional modules is spliced ​​to obtain the charging pile system.

[0041] By adopting the above technical solution, the various functional modules can be spliced ​​based on the dependency relationship between the configured functional modules, which can help ensure that the various modules in the charging pile system can exchange information as needed, and further help ensure that the charging pile system can achieve the required functions.

[0042] In the second aspect, the present application provides a charging pile system, which adopts the following technical solution:

[0043] A charging pile system is generated based on any one of the software-defined charging pile system implementation methods provided in the first aspect.

[0044] In a third aspect, the present application provides a charging pile, which adopts the following technical solution:

[0045] A charging pile, in which a charging pile system runs, and the charging pile system is generated based on any one of the software-defined charging pile system implementation methods provided in the first aspect.

[0046] Optionally, the charging pile includes at least one board interface, and the board interface is used to connect an expansion board. The operation of the charging pile system also includes:

[0047] When it is detected that a first expansion board is inserted into the board interface, identifying board identification information corresponding to the first expansion board;

[0048] Acquire a first expansion module corresponding to the first expansion board based on the board identification information;

[0049] Loading the first expansion module into the charging pile system to run the first expansion module in the charging pile system;

[0050] and / or,

[0051] When it is detected that a second expansion board is pulled out from the board interface, determining a second expansion module corresponding to the second expansion board;

[0052] The second expansion module is uninstalled from the charging pile system to stop running the second expansion module in the charging pile system.

[0053] By adopting the above technical solution, the charging pile system can detect the plugging and unplugging of the expansion card board and synchronously update the recharging pile system according to the plugging and unplugging situation, so that the charging pile system matches the plugging and unplugging status of the expansion card board, thereby ensuring that the function of the expansion card board can be realized and reducing the impact of useless expansion modules on the operation of the charging pile system, which can help ensure the stable and efficient operation of the charging pile system.

[0054] In a fourth aspect, the present application provides an electronic device, which adopts the following technical solution:

[0055] An electronic device, comprising:

[0056] at least one processor;

[0057] Memory;

[0058] At least one application, wherein the at least one application is stored in a memory and configured to be executed by at least one processor, and the at least one application is configured to: execute any one of the software-defined charging pile system implementation methods provided in the first aspect.

[0059] In summary, the present application includes at least one of the following beneficial technical effects:

[0060] 1. The target functional modules can be determined according to the configuration information, and the target functional modules can be configured based on the functional requirements. Finally, the configured target functional modules can be spliced ​​to obtain the charging pile system. In this way, the charging pile system can be freely combined at the software level through functional modules, so as to facilitate the efficient and flexible configuration of the charging pile system and form a customized system that meets customer needs;

[0061] 2. After obtaining the configured target functional module, it will be determined whether the necessary functional modules are missing in the configured target functional module, and only when it is determined that the necessary functional modules are not missing will the configured target functional modules be spliced ​​to obtain the charging pile system. This can help avoid errors in the generation process of the charging pile system, and can also help ensure the effectiveness of the finally generated charging pile system. BRIEF DESCRIPTION OF THE DRAWINGS

[0062] Figure 1 It is a flowchart of a method for implementing a software-defined charging pile system provided in an embodiment of the present application;

[0063] Figure 2 It is a flow chart of a charging pile system generation method provided in an embodiment of the present application;

[0064] Figure 3 It is a flowchart of another method for implementing a software-defined charging pile system provided in an embodiment of the present application;

[0065] Figure 4 It is a flow chart of another charging pile system generation method provided in an embodiment of the present application;

[0066] Figure 5 It is a flow chart of a charging pile system operation mode provided in an embodiment of the present application;

[0067] Figure 6 It is a structural schematic diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0068] In order to make the purpose, technical solutions and advantages of this application more clear, the following Figure 1-6 It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0069] The embodiment of the present application discloses a method for implementing a software-defined charging pile system. Based on the concept of software-defined product (Software Rapid Development Platform, SDP), corresponding functional modules (such as NFC module, 4G module, Wi-Fi module, LED module, electric control system module, POS machine module) can be matched according to the user's configuration requirements, and the matching functional modules can be combined into a charging pile system, so that flexible configuration of the charging pile system can be achieved.

[0070] The charging pile system obtained by the software-defined charging pile system implementation method provided in this embodiment runs on the charging pile and is used to control the charging pile to charge the electric vehicle. In some embodiments, the charging pile operation and maintenance management platform is implemented in the cloud. At this time, the charging pile system can reserve a management interface of the cloud platform. Correspondingly, the operation and maintenance management platform is integrated into the charging pile system through the reserved management interface to remotely monitor, maintain, update and diagnose the charging pile, especially to monitor the status of each module of the charging pile in real time.

[0071] refer to Figure 1 , a method for implementing a software-defined charging pile system includes the following steps:

[0072] Step 101, obtaining configuration requirement information of the charging pile system.

[0073] The configuration requirement information includes at least one type of functional requirement. Specifically, the types of functional requirements include: communication protocol requirements with the vehicle, networking requirements, electronic control system requirements, user interaction requirements, fee settlement requirements, function expansion requirements, remote monitoring and management requirements, etc.

[0074] To more clearly illustrate the content of the required configuration information, the following three configuration requirement information examples are used for illustration:

[0075] Example 1: Implement the combined application of OCPP1.6 protocol with NFC module, 4G module, and LED module to provide standardized charging services and support remote data update and diagnosis functions.

[0076] Example 2, integrating OCPP2.0.1 protocol with Wi-Fi module, electronic control system, and POS module to provide payment and charging functions, and perform remote maintenance through the operation and maintenance management platform.

[0077] Example 3: To support future V2G and V2H functions, the system designs corresponding interfaces that are compatible with the ISO15118 protocol and support bidirectional energy transmission.

[0078] It should be noted that the above examples are only illustrative. In actual implementation, the different functional requirements in the above examples can be combined into new configuration requirements, or corresponding configuration information can be added or deleted according to actual needs. This embodiment does not limit the content of the requirement information.

[0079] Optionally, configuration requirement information is generated by users operating a requirement configuration page. The requirement configuration page includes optional requirement parameters corresponding to different requirement types. In this way, corresponding requirement configuration information can be generated by selecting requirement parameters under the required requirement type, which can help generate configuration requirement information and improve the accuracy of configuration requirement information.

[0080] In one example, only functional requirements that require custom configuration may be given in the configuration requirement information. For functional requirements not given by the user, the system may refer to the configuration requirement information for settings, or may use the default settings. This may help improve the automation level of the system and thereby reduce the difficulty of use for users.

[0081] Step 102: Determine the target functional module that needs to be configured from the functional module library based on the configuration requirement information.

[0082] The target functional module corresponds to the type of functional requirement. Specifically, the functional module includes at least one of a protocol management module, a plug-in module, a functional extension module, a management interface module, and the like.

[0083] The protocol management module is responsible for managing the communication protocols between the charging pile system and the vehicle, including OCPP1.6, OCPP2.0.1, ISO15118, etc.

[0084] The plug-in module is used to meet the personalized needs of users. Specifically, the plug-in module may further include: a networking module, an electronic control module, an interactive module, a fee settlement module, etc.

[0085] The function expansion module is used to meet the user's demand for the expansion of the charging pile system function. In some embodiments, the function expansion module provides modules such as a V2H module and a V2G module.

[0086] It should be supplemented that, in actual implementation, the functional modules can be divided according to actual needs, and this embodiment does not limit the division method of the functional modules.

[0087] In one example, each functional module is stored independently in a Git repository or as a Git submodule. Further, the functional modules can be standardized through a directory structure to facilitate searching and calling the modules.

[0088] Step 103 : for each target functional module, configure the target functional module based on the functional requirements corresponding to the functional module to obtain a configured target functional module.

[0089] Specifically, the process of configuring the target functional module is the process of realizing the personalized customization of the function. In one example, for the protocol management module, the functional requirements may include OCPP1.6, and the protocol management module needs to be configured so that the configured protocol management module can support the OCPP1.6 protocol. In another example, for the networking module, the functional requirements may include 4G and WiFi, and the networking module needs to be configured so that the configured networking module can support both 4G and WiFi protocols.

[0090] In one example, configuring a target functional module based on the functional requirements corresponding to the functional module includes: obtaining a configuration program corresponding to the functional requirements; and loading the configuration program into the target functional module to implement the configuration of the target functional module. The configuration programs corresponding to different functional requirements are pre-set.

[0091] In another example, the function module may also be pre-integrated with programs required to implement different functional requirements, and in this case, during the configuration process, only the corresponding functions of the function module need to be activated through the configuration parameters corresponding to the functional requirements to complete the configuration of the function module. This makes it easier to configure the function module.

[0092] Furthermore, in the process of configuring the functional module, it is necessary not only to configure the function of the module but also to configure the data interface of the module. For example, the type and / or quantity of the data interface of the module under different functional requirements may be different. At this time, the interface can be configured accordingly based on the preset interface configuration rules to ensure the availability of the functional module.

[0093] In actual implementation, for each functional module, sub-functional modules of the functional module under different functional requirements can also be pre-set, so that in the process of configuring the target functional module, the sub-functional modules of the target functional module under the configuration parameters can be determined as the configured target functional module. This can help improve the efficiency of the configuration of the target functional module.

[0094] Optionally, each configured target functional module can be compiled and tested separately to ensure that the module can work properly and achieve the required functions.

[0095] Step 104 , determining whether necessary functional modules are missing in each configured target functional module.

[0096] Among them, the necessary functional modules refer to the functional modules that are essential to the charging pile system, such as protocol management module, human-computer interaction module, etc.

[0097] It should be noted that since the demand configuration information may only reflect the functional content that the user wishes to customize, the demand configuration information may not be able to fully configure the necessary functions of the system, which may lead to the lack of necessary functional modules in the target functional modules, which may affect the construction of the charging pile system. Therefore, it is necessary to determine whether the necessary functional modules are missing in the target functional modules after configuration before building the charging pile system based on the target functional modules.

[0098] In one example, the types of necessary functional modules are preset.

[0099] In another example, considering that there may be dependencies between functional modules, for example, the fee settlement module needs to rely on the management interface module to manage the fee settlement through the management platform. Based on this, the functional modules that the configured target module depends on can be identified as necessary functional modules. In actual implementation, the dependencies of functional modules can be recorded in the description file of the functional modules. Specifically, the description file can be a module.json or YAML file, which is used to describe the module function, version, dependency, entry and other parameters.

[0100] In one example, taking the OCPP1.6 module as an example, its description file includes the following contents:

[0101] {

[0102] "name":"OCPP1.6",

[0103] "type":"protocol",

[0104] "version":"1.0.0",

[0105] "dependencies": ["TCU system","light board"],

[0106] "entry":"ocpp1_6.so"

[0107] }

[0108] Step 105 , when necessary functional modules are not missing in each of the configured target functional modules, each of the configured target functional modules is spliced ​​to obtain a charging pile system.

[0109] Optionally, splicing the configured target function modules is actually to establish communication between the configured target function modules with interaction requirements. In actual implementation, the communication between the configured target function modules can be achieved through event-driven (such as MQTT) or message queue (such as ZeroMQ). Furthermore, the system provides an RPC interface between modules to ensure a unified calling method. In actual implementation, communication connections can also be established between function modules through ordinary data interfaces.

[0110] Optionally, each configured target function module is spliced, including: determining the dependency relationship of each configured target function module; constructing a dependency tree between each configured target function module based on the dependency relationship; splicing each configured target function module based on the dependency tree to obtain a charging pile system.

[0111] The dependency relationship is used to indicate the relationship between the configured target functional module and other modules. Generally speaking, when the configured functional module needs to interact with other modules (for example, it needs to obtain data from other modules), it is determined that the configured functional module has a dependency relationship with the module. In one example, the dependency relationship is pre-stored in the description file corresponding to the functional module and can be obtained by parsing the description file.

[0112] The dependency tree is used to reflect the dependency relationship between the target function modules after configuration. Through the dependency tree, we can clearly know the data interaction requirements between different target function modules after configuration, so that the splicing of the function modules after configuration can be realized through the data interaction requirements between the function modules after configuration.

[0113] In one example, each configured target functional module is spliced ​​based on a dependency tree to obtain a charging pile system, including: automatically generating a CMake or Bazel build script according to the dependency tree to generate the charging pile system based on the built script.

[0114] To help you understand the process of building a dependency tree, the following example is used to illustrate the process of building a dependency tree. In this example, the TCU system, light board, OCPP1.6, and Web configuration tool need to be integrated.

[0115] After parsing the description files of the target functional modules after the configuration of different modules, the following dependency relationships can be obtained:

[0116] {

[0117] "modules": ["TCU","Light Board","OCPP1.6","WebConfig"],

[0118] "dependencies": {

[0119] "TCU": [],

[0120] "Light Board": ["TCU"],

[0121] "OCPP1.6": ["TCU","Light Board"],

[0122] "WebConfig": ["CCU"]

[0123] }

[0124] }

[0125] Correspondingly, the corresponding dependency tree is as follows:

[0126] CCU

[0127] └── TCU

[0128] ├── Light board

[0129] └── OCPP1.6

[0130] In actual implementation, the various functional modules can also be layered to obtain a system architecture diagram of the charging pile system. Accordingly, in the process of splicing the various configured target functional modules, the configured target functional modules can be spliced ​​in combination with the hierarchical relationship of the functional modules in the system architecture diagram, which makes it easier to replace and maintain the system modules.

[0131] In one example, the charging pile system is divided into six layers. The first layer includes the operation and maintenance management platform; the second layer includes APP and Web configuration tools; the third layer is the protocol layer, including OCPP protocol, ISO 15118 protocol, etc.; the fourth layer is the control layer, including TCU system, CCU system, etc.; the fifth layer is the plug-in layer, including light board, 4G, Wi-Fi, card swiping board, etc.; the fifth layer includes modules and hardware related to secure startup.

[0132] The implementation principle of a method for implementing a software-defined charging pile system in an embodiment of the present application is as follows: obtaining configuration requirement information of the charging pile system, the configuration requirement information includes at least one type of functional requirement; determining the target functional module to be configured from the functional module library based on the configuration requirement information, the target functional module corresponding to the type of functional requirement; for each target functional module, configuring the target functional module based on the functional requirement corresponding to the functional module to obtain the configured target functional module; determining whether necessary functional modules are missing in each configured target functional module; in the case that necessary functional modules are not missing in each configured target functional module, splicing each configured target functional module to obtain a charging pile system. By adopting the above technical solution, the target functional module can be determined according to the configuration information, and the target functional module can be configured based on the functional requirement, and finally the configured target functional modules can be spliced ​​to obtain a charging pile system, so that the charging pile system can be freely combined at the software level through the functional modules, so that it is easy to realize the efficient and flexible configuration of the charging pile system, and form a customized system that meets customer needs.

[0133] In addition, after obtaining the configured target functional module, it will be determined whether the necessary functional modules are missing in the configured target functional module, and the configured target functional modules will be spliced ​​to obtain the charging pile system only when it is determined that the necessary functional modules are not missing. This can help avoid errors in the generation process of the charging pile system, and can also help ensure the effectiveness of the ultimately generated charging pile system.

[0134] In some embodiments, reference Figure 2In step 105, each configured target functional module is spliced ​​to obtain a charging pile system, including the following steps:

[0135] Step 201, splicing each configured target functional module to obtain a spliced ​​system.

[0136] Specifically, the specific implementation of step 201 can be similar to the specific implementation of step 105 described above, and will not be repeated here.

[0137] Step 202: Perform a functional test on the spliced ​​system to determine whether there is any functional abnormality in the spliced ​​system.

[0138] In actual implementation, the content of the functional test may include at least one of the following two parts. The first part is to verify the basic functions of the charging pile system to test whether the system can operate normally after splicing; the second part is to test the functional requirements corresponding to the functional requirements in the configuration requirement information to test whether the system can meet the functional requirements specified by the user after splicing.

[0139] Optionally, the function test of the spliced ​​system includes: running the spliced ​​system in a simulated operating environment to perform a function test on the spliced ​​system. In actual implementation, the spliced ​​system can also be imported into the charging pile to perform a function test on the spliced ​​system based on the actual operating effect of the charging pile.

[0140] It should be noted that the functional testing process can be achieved through automated testing programs. For example, CI / CD tools (such as GitHub Actions and Jenkins) are used to automatically complete the build and test. In this case, the tester needs to pre-set the functions to be tested and the corresponding qualified conditions for the functions. Alternatively, the tester can directly operate the spliced ​​system to test the spliced ​​system. In this case, the tester will determine and output whether there is any functional abnormality.

[0141] Step 203: When there is a functional abnormality in the spliced ​​system, determine the abnormal target functional module corresponding to the abnormal function from each configured target functional module.

[0142] In this implementation manner, since various functions of the system are implemented by different configured target function modules, the abnormal target function module can be located based on the abnormal function.

[0143] Optionally, when there is no functional abnormality in the spliced ​​system, it means that the spliced ​​system can meet the usage requirements. At this time, the spliced ​​system can be directly used as the final charging pile system.

[0144] Step 204: determine, from each configured target functional module, a second associated module that has an associated relationship with the abnormal target functional module.

[0145] The association relationship between the functional modules may be pre-set based on the type of the functional modules, or may be determined by the data interaction relationship between the functional modules. This embodiment does not limit the method for determining the association relationship.

[0146] In one example, a configured template function module that has data interaction with the abnormal target function module is determined as the second associated module.

[0147] In another example, a module function module that has a dependency relationship with the abnormal target function module and is recorded in a description file corresponding to the abnormal target function module is determined as a second associated module.

[0148] Step 205: for each second associated module, determine whether the functional requirement corresponding to the second associated module matches the functional requirement corresponding to the abnormal target functional module.

[0149] Optionally, determining whether the functional requirements corresponding to the second association module match the functional requirements corresponding to the abnormal target functional module includes: determining whether the functional requirements corresponding to the second association module and the functional requirements corresponding to the abnormal target functional module meet preset conflict rules; if so, determining that the functional requirements corresponding to the second association module and the functional requirements corresponding to the abnormal target functional module do not match; if not, determining that the functional requirements corresponding to the second association module and the functional requirements corresponding to the abnormal target functional module match.

[0150] The conflict rules are pre-set according to the functional conflicts between different functional modules. For example, for the TCU module and the light board module, the conflict rules may include that the version of the TCU module cannot support the display mode corresponding to the light board module, and if the conflict rules are met, the light board module may not display normally.

[0151] Step 206, when the functional requirement corresponding to the second associated module does not match the functional requirement corresponding to the abnormal target functional module, output matching abnormality prompt information corresponding to the second associated module and the abnormal target functional module to prompt matching abnormality between the modules.

[0152] The abnormal prompt information is used to prompt that there is a conflict in functional requirements between the second associated module and the abnormal target functional module. Further, the abnormal prompt information may include the conflict rule based on which the mismatch is determined, which can help to handle the functional conflict between modules.

[0153] Optionally, when the functional requirements corresponding to each second associated module match the functional requirements corresponding to the abnormal target functional module, prompt information indicating that a configuration error exists in the abnormal target functional module is directly output.

[0154] Since the functional requirements corresponding to each second associated module match the functional requirements corresponding to the abnormal target functional module, it means that the abnormality of the abnormal target functional module is not caused by the conflict of functional requirements between modules. The reasons for the functional abnormality include not only the conflict between modules but also the configuration errors of the module itself. Therefore, after excluding the functional abnormality caused by the conflict between modules, it can be determined that there is a configuration error in the abnormal target functional module.

[0155] In addition, since there are many factors that lead to module configuration errors, such as: functional requirement parsing errors, exceptions in the configuration process, etc., it is difficult to eliminate them one by one, and therefore it is difficult to directly determine that there is a configuration error in the module. The above technical solution predicts module errors by excluding other possible methods. This can help to ensure the accuracy of the abnormal cause judgment while reducing the difficulty of abnormal cause judgment.

[0156] In the above implementation, after each configured target functional module is spliced, the spliced ​​system can be functionally tested, and when a functional abnormality is determined, the matching relationship between the functional requirements corresponding to the abnormal target functional module and the functional requirements corresponding to its second associated module can be verified. In this way, when a functional abnormality occurs in the spliced ​​system, the cause of the functional abnormality can be determined, thereby guiding the correction of the system generation process to regenerate a system without functional abnormalities, which can help improve the efficiency of system generation.

[0157] In some embodiments, reference Figure 3 , step 104, after determining whether necessary functional modules are missing in each configured target functional module, the following steps are also included:

[0158] Step 301: when necessary function modules are missing from each of the configured target function modules, the missing necessary function modules are determined as supplementary function modules.

[0159] Step 302: configure the supplementary function module to obtain a configured supplementary function module.

[0160] In one example, the supplementary function module is configured based on a preset configuration mode corresponding to the supplementary function module.

[0161] Step 303, splicing each configured target functional module and the configured supplementary functional module to obtain a charging pile system.

[0162] Specifically, the specific implementation of step 303 can be similar to the specific implementation of step 105 described above, and will not be repeated here.

[0163] In the above technical solution, when it is determined that a necessary functional module is missing, the missing necessary functional module will be determined as a supplementary module, and after the supplementary functional module is configured, the configured target functional module and the configured supplementary functional module will be spliced ​​to obtain a charging pile system. In this way, the necessary functional modules can be automatically supplemented when the user does not customize them, which can help avoid errors in the generation process of the charging pile system and also help ensure the effectiveness of the finally generated charging pile system.

[0164] For further reference, Figure 4 The above step 303, splicing each configured target function module and the configured supplementary function module to obtain a charging pile system, includes the following steps:

[0165] Step 401, splicing each configured target functional module and the configured supplementary functional module to obtain a spliced ​​system.

[0166] Specifically, the specific implementation of step 401 can be similar to the specific implementation of step 105 described above, and will not be repeated here.

[0167] Step 402, performing a functional test on the spliced ​​system to determine whether there is any functional abnormality in the spliced ​​system.

[0168] Specifically, the specific implementation of step 402 can be similar to the specific implementation of step 202 described above, and will not be repeated here.

[0169] Step 403: When there is a functional abnormality in the system after splicing, determine whether the abnormal function corresponds to the post-configuration supplementary function module.

[0170] In this implementation manner, since each function of the system is implemented by a post-configuration target function module and a post-configuration supplementary function module, the abnormal target function module or the supplementary function module can be located based on the abnormal function.

[0171] Furthermore, since the configuration mode of the target functional module is specified in the configuration requirement information, the configuration mode of the second supplementary functional module is automatically determined, so the category of the module corresponding to the abnormal function is helpful to determine the cause of the functional abnormality.

[0172] Optionally, when the abnormal function does not correspond to the supplementary function module after configuration, it means that the abnormal function corresponds to the target function module after configuration. At this time, the cause of the functional abnormality can be further determined based on the methods in the above steps 203 to 206, or the cause of the abnormality can be determined based on other methods. This embodiment does not limit this.

[0173] Step 404 , in the case where the function with the exception corresponds to the post-configuration supplementary function module, determining the reference requirement corresponding to the abnormal supplementary function module with the exception.

[0174] Specifically, when there is an abnormal function corresponding to the supplementary function module after configuration, it means that the abnormality is caused by the supplementary function module after configuration. Since the supplementary function module is automatically configured, it is highly likely that the functional abnormality is caused by the configuration error of the supplementary function module. Therefore, when there is an abnormal function corresponding to the supplementary function module after configuration, it is necessary to reconfigure the supplementary function module.

[0175] In one example, determining the reference requirements corresponding to the abnormal supplementary function module with an abnormality includes: determining whether there is a first associated module in each configured target function module that has an associated relationship with the abnormal supplementary function module; if there is a first associated module, determining the reference requirements based on the functional requirements corresponding to the first associated module. This can help match the reference requirements with the functional requirements of the first associated module, thereby avoiding module function abnormalities caused by functional conflicts between the associated function modules.

[0176] The association relationship between the functional modules may be pre-set based on the type of the functional modules, or may be determined by the data interaction relationship between the functional modules. This embodiment does not limit the method for determining the association relationship.

[0177] In one example, a post-configuration template function module that has data interaction with the abnormal supplement function module is determined as the first associated module.

[0178] In another example, a module function module recorded in a description file corresponding to the abnormal supplementary function module and having a dependency relationship with the abnormal target function module is determined as a first associated module.

[0179] Optionally, determining the reference requirement based on the functional requirement corresponding to the first associated module includes: determining the reference requirement based on the functional requirement corresponding to the first associated module and the conflict rule between the first associated module and the abnormal supplementary functional module, so that there is no conflict between the reference requirement and the functional requirement corresponding to the first module.

[0180] Among them, the conflict rules are pre-set according to the functional conflicts between the functions of different functional modules. For example: for the TCU module and the light board module, the conflict rules may include that the version of the TCU module cannot support the display mode corresponding to the light board module. At this time, when the abnormal target functional module is the light board module, it is necessary to select the version of the TUC module from the versions other than the version of the TCU module that cannot support the display mode corresponding to the light board module according to the conflict rules, so that the version of the TUC module can indicate the display mode corresponding to the light board module.

[0181] In another example, the supplementary function module has more than two preset configuration modes, and each preset configuration mode corresponds to different configuration parameters. At this time, when the supplementary function module is determined to be an abnormal function module, the configuration parameters corresponding to the preset configuration mode different from the configuration mode used before (for example: the last time) can be determined as reference configuration parameters. In this way, a reasonable preset configuration mode can be selected by switching the preset configuration modes.

[0182] Furthermore, when no functional abnormality occurs in the system after splicing, the preset configuration method used by each supplementary functional module after configuration can be recorded, and when the functional module is determined as a supplementary functional module again, the recorded preset configuration method is preferentially used to configure the supplementary functional module. This can help reduce the probability of functional abnormality in the system after splicing.

[0183] Step 405, configure the abnormal supplementary function module based on the reference requirements to regenerate the configured supplementary function module corresponding to the abnormal supplementary function module, return to execute the step of splicing the various configured target function modules and the configured supplementary function modules to obtain the spliced ​​system, and perform functional testing on the spliced ​​system to determine whether there is any functional abnormality in the spliced ​​system, that is, return to execute steps 401 and 402.

[0184] Specifically, the manner of configuring the abnormal supplementary functional module based on the reference requirement refers to the manner of configuring the target functional module based on the functional requirement corresponding to the functional module in the above step 103, which will not be described in detail in this embodiment.

[0185] In the above technical scheme, when it is determined that there is a functional abnormality in the spliced ​​system and the abnormal function corresponds to the supplementary function module, the reference requirement corresponding to the abnormal supplementary function module can be determined, and the supplementary function module can be configured based on the reference requirement to reconfigure the abnormal supplementary function module. In this way, the functional abnormality in the spliced ​​system can be automatically processed to regenerate the spliced ​​system, which can help improve the degree of automation in the charging pile system generation process.

[0186] An embodiment of the present application also provides a charging pile, in which a charging pile system runs. The charging pile system is generated based on any one of the software-defined charging pile system implementation methods provided in the above method embodiments.

[0187] Furthermore, the charging pile includes at least one card board interface, which is used to connect an expansion board. The expansion board is used to implement corresponding expansion functions, such as a card swiping board for implementing a card swiping function. Through the card board interface, users can insert the required body station board according to actual needs so that the charging pile can implement the corresponding function, which can help better meet the diverse needs of users.

[0188] In some embodiments, reference Figure 5 The operation of the charging pile system also includes:

[0189] Step 501: When it is detected that a first expansion board is inserted into a board interface, board identification information corresponding to the first expansion board is identified.

[0190] In one example, the board identification information is used to uniquely identify the board, that is, different boards correspond to different board identification information, so that it is convenient to customize the expansion board according to the actual needs of the user.

[0191] In another example, the board identification information is used to uniquely identify the board type, that is, the board identification information of different types of boards is different.

[0192] Optionally, identifying the board identification information corresponding to the board includes: receiving a data packet sent by the first expansion board through the board interface; parsing the content of the data packet to obtain the board identification information. The data packet includes the board identification information. In actual implementation, the data packet may also include data generated or collected by the board, such as card data collected by the card swiping board.

[0193] Optionally, the board interface and expansion card board use a standard bus (such as CAN, Ethernet, SPI, I²C, USB) to achieve communication.

[0194] In one example, the insertion detection of the first expansion card board of the module is implemented through a hardware interrupt (GPIO signal) or a protocol (such as a USB hot-plug mechanism).

[0195] In another example, an insertion detection sensor is provided at the card board interface to detect whether an expansion card board has been inserted into the card board interface. In this way, when the signal from the insertion detection sensor indicates that the state of the card board interface has changed from no expansion card board inserted to an expansion card board inserted, the charging pile system determines that a first expansion board has been inserted into the card board interface.

[0196] Step 502: Acquire a first expansion module corresponding to a first expansion board based on the board identification information.

[0197] The expansion module corresponds to the board identification information. In one example, the board identification information

[0198] Optionally, the extension module is pre-stored in an extension module library, and acquiring the first extension module corresponding to the first extension module based on the board identification information includes: searching the extension module library for the first extension module corresponding to the board identification information.

[0199] Among them, the expansion module library can be stored locally in the charging pile and updated regularly, or it can also be stored in the cloud. When the expansion module library is stored in the cloud, the charging pile system needs to generate a module acquisition request based on the board identification information to obtain the first expansion module corresponding to the first expansion board from the cloud.

[0200] Step 503: Load the first expansion module into the charging pile system to run the first expansion module in the charging pile system.

[0201] Optionally, loading the first extension module into the charging pile system includes: loading the first extension module into the charging pile system based on a dependency relationship of the first extension module.

[0202] The dependency relationship is used to indicate the dependency relationship between the expansion module and the functional module, for example, the expansion module corresponding to the card swiping board can depend on the CCU system module. In actual implementation, the dependency relationship is pre-stored in the description information of the expansion module.

[0203] In an example, taking the card swiping version as an example, the description information of the extension module corresponding to the card swiping version is as follows:

[0204] {

[0205] "name":"Card swiping board",

[0206] "type":"payment",

[0207] "dependencies": ["CCU system"],

[0208] "entry":"card_reader.so"

[0209] }

[0210] During the actual loading process, the charging pile system will ensure that the CCU system has been loaded, and then call the load() method of card_reader.so to initialize the card swiping function.

[0211] In the above implementation, when the charging pile system detects that the first expansion board is inserted, it will automatically load the first expansion module corresponding to the first expansion board into the charging pile system. In this way, the charging pile system can be automatically and synchronously updated when the charging pile is inserted with the first expansion board, thereby ensuring that the first expansion board can be normally identified and used, which can help improve the user experience.

[0212] In some other embodiments, continue to refer to Figure 5 The operation of the charging pile system also includes:

[0213] Step 504: when it is detected that the second expansion board is pulled out of the board interface, determine a second expansion module corresponding to the second expansion board.

[0214] In one example, determining the second expansion module corresponding to the second expansion board includes: determining the expansion module corresponding to the board interface corresponding to the second expansion board as the second expansion module corresponding to the second expansion board; or determining the expansion module corresponding to the board identification information of the second expansion board as the second expansion module.

[0215] Step 505: Uninstall the second expansion module from the charging pile system to stop running the second expansion module in the charging pile system.

[0216] In one example, uninstalling the second extension module from the charging pile system includes: calling an uninstall function (eg, unload() function) corresponding to the second extension module.

[0217] In the above implementation, when the charging pile system detects that the second expansion board is pulled out, it will automatically uninstall the second expansion module corresponding to the second expansion board from the charging pile system. In this way, the charging pile system can be updated synchronously when the second expansion module is pulled out from the charging pile, thereby reducing the impact of useless expansion modules on the operation of the charging pile system, which can help ensure the stable and efficient operation of the charging pile system.

[0218] An embodiment of the present application also provides a charging pile system, which is generated based on the software-defined charging pile system implementation method provided in the above method embodiment and can be used in the charging pile provided in the above embodiment.

[0219] The present application also provides an electronic device. Figure 6 As shown, Figure 6The electronic device 600 shown includes: a processor 601 and a memory 603. The processor 601 and the memory 603 are connected, such as through a bus 602. Optionally, the electronic device 600 may also include a transceiver 604. It should be noted that in actual applications, the transceiver 604 is not limited to one, and the structure of the electronic device 600 does not constitute a limitation on the embodiments of the present application.

[0220] Processor 601 may be a CPU (Central Processing Unit), a general-purpose processor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It may implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. Processor 601 may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and the like.

[0221] The bus 602 may include a path to transmit information between the above components. The bus 602 may be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus. The bus 602 may be divided into an address bus, a data bus, etc. For ease of representation, Figure 6 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0222] The memory 603 may be a ROM (Read Only Memory) or other types of static storage devices that can store static information and instructions, a RAM (Random Access Memory) or other types of dynamic storage devices that can store information and instructions, or an EEPROM (Electrically Erasable Programmable Read Only Memory), a disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program codes in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto.

[0223] The memory 603 is used to store the application code for executing the solution of the present application, and the execution is controlled by the processor 601. The processor 601 is used to execute the application code stored in the memory 603 to implement the contents shown in the above method embodiment.

[0224] The electronic devices include, but are not limited to, mobile terminals such as mobile phones, laptop computers, PDAs (personal digital assistants), PADs (tablet computers), etc., and fixed terminals such as digital TVs, desktop computers, etc. It can also be a server terminal, etc. Figure 6 The electronic device shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0225] It should be understood that although the steps in the flowchart of the accompanying drawings are shown in sequence according to the instructions of the arrows, these steps are not necessarily performed in the order indicated by the arrows. Unless otherwise clearly stated in this document, the execution of these steps is not strictly limited in order and can be performed in other orders.

[0226] The above are only some implementation methods of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A method for implementing a software-defined charging pile system, characterized in that: The method comprises: Acquire configuration requirement information of the charging pile system, where the configuration requirement information includes at least one type of functional requirement; Determining a target functional module to be configured from a functional module library based on the configuration requirement information, wherein the target functional module corresponds to a type of the functional requirement; For each of the target functional modules, configuring the target functional module based on the functional requirements corresponding to the functional module to obtain a configured target functional module; Determine whether necessary functional modules are missing in each of the configured target functional modules; In the case that the necessary functional modules are not missing in each of the configured target functional modules, each of the configured target functional modules is spliced ​​to obtain the charging pile system; The determining whether necessary functional modules are missing in each of the configured target functional modules comprises: In the case where the necessary functional modules are missing from each of the configured target functional modules, determining the missing necessary functional modules as supplementary functional modules; configuring the supplementary function module based on a preset configuration mode corresponding to the supplementary function module to obtain a configured supplementary function module, wherein the preset configuration modes have more than two and are switched when it is determined that the supplementary function module is an abnormal function module; Splicing each of the configured target function modules and the configured supplementary function modules to obtain a spliced ​​system; Performing a functional test on the spliced ​​system to determine whether the spliced ​​system has functional abnormalities; In the case that the system after splicing has a functional abnormality, determining whether the abnormal function corresponds to the post-configuration supplementary function module; In the case where the abnormal function corresponds to the post-configuration supplementary function module, determining whether there is a first associated module in each of the post-configuration target function modules that has an associated relationship with the abnormal supplementary function module; In the case where the first association module exists, determining a reference requirement based on a functional requirement corresponding to the first association module and a conflict rule between the first association module and the abnormal supplementary functional module, so that there is no conflict between the reference requirement and the functional requirement corresponding to the first association module, wherein the conflict rule is pre-set according to functional conflicts between different functional modules; The abnormal supplementary function module is configured based on the reference requirement to regenerate the configured supplementary function module corresponding to the abnormal supplementary function module, and the step of returning to execute splicing each of the configured target function modules and the configured supplementary function module to obtain a spliced ​​system, and performing a functional test on the spliced ​​system to determine whether there is any functional abnormality in the spliced ​​system.

2. The method according to claim 1, characterized in that The above-mentioned charging pile system is obtained by splicing the above-mentioned configured target functional modules, including: Splicing each of the configured target functional modules to obtain a spliced ​​system; Performing a functional test on the spliced ​​system to determine whether the spliced ​​system has functional abnormalities; In the case that the spliced ​​system has a functional abnormality, determining an abnormal target functional module corresponding to the function with the abnormality from each of the configured target functional modules; Determine, from each of the configured target function modules, a second association module that has an association relationship with the abnormal target function module; For each of the second association modules, determining whether the functional requirement corresponding to the second association module matches the functional requirement corresponding to the abnormal target functional module; When the functional requirement corresponding to the second associated module does not match the functional requirement corresponding to the abnormal target functional module, matching abnormality prompt information corresponding to the second associated module and the abnormal target functional module is output to prompt the matching abnormality between the modules.

3. The method according to claim 1, characterized in that The above-mentioned charging pile system is obtained by splicing the above-mentioned configured target functional modules, including: Determining the dependency relationship between each of the configured target functional modules; Constructing a dependency tree between each of the configured target function modules based on the dependency; Based on the dependency tree, each of the configured target functional modules is spliced ​​to obtain the charging pile system.

4. A charging pile system, characterized in that: The charging pile system is generated based on the software-defined charging pile system implementation method described in any one of claims 1 to 3.

5. A charging pile, characterized in that: A charging pile system is running in the charging pile, and the charging pile system is generated based on the software-defined charging pile system implementation method according to any one of claims 1 to 3.

6. The charging pile according to claim 5, characterized in that: The charging pile includes at least one board interface, and the board interface is used to connect to an expansion board. The operation process of the charging pile system also includes: When it is detected that a first expansion board is inserted into the board interface, identifying board identification information corresponding to the first expansion board; Acquire a first expansion module corresponding to the first expansion board based on the board identification information; Loading the first expansion module into the charging pile system to run the first expansion module in the charging pile system; and / or, When it is detected that a second expansion board is pulled out from the board interface, determining a second expansion module corresponding to the second expansion board; The second expansion module is uninstalled from the charging pile system to stop running the second expansion module in the charging pile system.

7. An electronic device, characterized in that: The electronic device comprises: at least one processor; Memory; At least one application, wherein the at least one application is stored in a memory and configured to be executed by at least one processor, and the at least one application is configured to: execute the software-defined charging pile system implementation method described in any one of claims 1 to 3.

Images