CN110990303B - Data processing method and device for charging pile, storage medium and processor - Google Patents
Data processing method and device for charging pile, storage medium and processor Download PDFInfo
- Publication number
- CN110990303B CN110990303B CN201911072375.8A CN201911072375A CN110990303B CN 110990303 B CN110990303 B CN 110990303B CN 201911072375 A CN201911072375 A CN 201911072375A CN 110990303 B CN110990303 B CN 110990303B
- Authority
- CN
- China
- Prior art keywords
- layer
- service
- data
- processed
- module
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/10—Program control for peripheral devices
- G06F13/102—Program control for peripheral devices where the programme performs an interfacing function, e.g. device driver
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Power Sources (AREA)
- Stored Programmes (AREA)
- Charge And Discharge Circuits For Batteries Or The Like (AREA)
Abstract
The invention discloses a data processing method and device for a charging pile, a storage medium and a processor. The method is applied to different hardware platforms of a charging pile, data to be processed transmitted by the hardware platforms are obtained through a driving layer, a plurality of driving program interfaces are determined in the driving layer, the driving layer is used for shielding differentiation among the different hardware platforms and is used for providing the plurality of driving program interfaces for an intermediate layer; transmitting data to be processed to at least one functional interface in an intermediate layer through a plurality of driver interfaces, wherein the intermediate layer is used for shielding the difference among the drivers of different hardware platforms and providing at least one functional interface for a service layer; transmitting the data to be processed received by at least one functional interface to at least one service module in a service layer; and processing the data to be processed, which is received by the at least one functional module from the at least one service module, in the task layer. According to the invention, the effect of improving the data processing efficiency of the charging pile is achieved.
Description
Technical Field
The invention relates to the field of charging piles, in particular to a data processing method and device of a charging pile, a storage medium and a processor.
Background
At present, due to the reasons that the single chip microcomputer product item suitable for the charging pile is small in scale and difficulty, low in complexity, complex in application scene of the product and the like, people cannot pay attention to the development of a software framework suitable for the single chip microcomputer. Therefore, a software development framework suitable for a single chip microcomputer is not developed up to now.
In addition, an embedded platform (linux) of the charging pile is suitable for complex scenes and is not suitable for application scenes with limited singlechip resources.
The existing embedded development technology mainly performs special development for a specific chip platform, and after the development is completed, only the existing embedded development technology is used for a fixed chip platform and hardware. For example, when the STM32F104 chip is used for development, the chip cannot be directly applied to an LPC1778 platform, a linux embedded platform, and the like, and the chip can be used after engineering migration or redevelopment. The range of the usable chip of the charging pile is very wide, different developers have different familiarity degrees with the chip, so that the project is not beneficial to team collaborative development, the development difficulty is high, the software quality has high requirements on the quality of the developers, the same function needs to be developed on different hardware platforms for multiple times, the development is still needed again when the chip platform is replaced by the charging pile, a large amount of labor cost and time cost waste are caused, and the data processing efficiency of the charging pile is low.
To the problem of the low data processing efficiency of the charging pile in the prior art, an effective solution is not provided at present.
Disclosure of Invention
The invention mainly aims to provide a data processing method and device of a charging pile, a storage medium and a processor, so as to at least solve the problem of low data processing efficiency of the charging pile.
In order to achieve the above object, according to an aspect of the present invention, there is provided a data processing method of a charging pile. The method can comprise the following steps: be applied to different hardware platform that fill electric pile, include: acquiring data to be processed transmitted by a hardware platform through a driving layer, and determining a plurality of driving program interfaces in the driving layer, wherein the driving layer is used for shielding the differentiation between different hardware platforms and providing the plurality of driving program interfaces for a middle layer; transmitting data to be processed to at least one functional interface in an intermediate layer through a plurality of driver interfaces, wherein the intermediate layer is used for shielding the difference between drivers of different hardware platforms and providing at least one functional interface for a service layer, and the driver is provided by the driver layer; transmitting the data to be processed received by at least one functional interface to at least one service module in a service layer; and processing the data to be processed, which is received by at least one functional module from at least one service module, in the task layer, wherein at least one second functional module corresponds to at least one first functional module one to one.
Optionally, the processing, in the task layer, the to-be-processed data received by the at least one function module from the at least one service module includes: and processing the data to be processed, which are received by the at least two functional modules from the at least two service modules, in the task layer so as to perform data interaction between the at least two functional modules.
Optionally, transmitting the to-be-processed data to at least one functional interface in the middle layer through a plurality of driver interfaces includes: and calling the middle layer through the driver layer, and transmitting the data to be processed to at least one functional interface in the middle layer through a plurality of driver interfaces.
Optionally, transmitting the to-be-processed data received by the at least one functional interface to the at least one service module in the service layer includes: and calling the service layer through the middle layer, and transmitting the data to be processed received by the at least one functional interface to at least one service module in the service layer.
Optionally, the processing, in the task layer, the to-be-processed data received by the at least one function module from the at least one service module includes: and calling the task layer through the service layer, and processing the data to be processed, which is received by the at least one functional module from the at least one service module, in the task layer.
Optionally, the method further comprises at least one of: the multiple driver interfaces are independent from each other; at least one functional interface is independent; at least one service module is independent.
Optionally, the method further comprises at least one of: dividing the driving layer into a plurality of sub-driving layers which are allowed to be mutually called according to a first logic relationship; dividing the middle layer into a plurality of sub-middle layers which are allowed to be mutually called according to a second logic relationship; dividing the service layer into a plurality of sub-service layers which are allowed to be mutually called according to a third logic relation; and dividing the task layer into a plurality of subtask layers which allow mutual calling according to a fourth logic relationship.
In order to achieve the above object, according to another aspect of the present invention, there is also provided a data processing apparatus of a charging pile. The device is applied to and fills electric pile's different hardware platform, includes: the device comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is used for acquiring data to be processed transmitted by a hardware platform through a driving layer and determining a plurality of driving program interfaces in the driving layer, and the driving layer is used for shielding the differentiation between different hardware platforms and providing the plurality of driving program interfaces for a middle layer; the first transmission unit is used for transmitting data to be processed to at least one functional interface in the middle layer through a plurality of driver interfaces, wherein the middle layer is used for shielding the difference among the drivers of different hardware platforms and providing at least one functional interface for the service layer, and the driver is provided by the driver layer; the second transmission unit is used for transmitting the data to be processed received by the at least one functional interface to at least one service module in the service layer; and the processing unit is used for processing the data to be processed, which is received by the at least one functional module from the at least one service module, in the task layer, wherein the at least one second functional module corresponds to the at least one first functional module one to one.
The data processing method of the charging pile is applied to different hardware platforms of the charging pile, data to be processed transmitted by the hardware platforms are obtained through a driving layer, and a plurality of driving program interfaces are determined in the driving layer, wherein the driving layer is used for shielding differentiation among the different hardware platforms and is used for providing the plurality of driving program interfaces for a middle layer; transmitting data to be processed to at least one functional interface in an intermediate layer through a plurality of driver interfaces, wherein the intermediate layer is used for shielding the difference between drivers of different hardware platforms and providing at least one functional interface for a service layer, and the driver is provided by the driver layer; transmitting the data to be processed received by at least one functional interface to at least one service module in a service layer; and processing the data to be processed, which is received by the at least one functional module from the at least one service module, in the task layer. That is to say, the scheme divides the software program of the data processing method of the charging pile into a driving layer, a middle layer, a business layer and a task layer, determines the functions of each layer and the functions of the modules included in each layer, decoupling the program of the charging pile, being applicable to different hardware platforms, improving the stability, the robustness and the expandability of the program, and shortens the program development period, has simple maintenance, stable and reliable program operation and less program loopholes, avoids the problems that the project is not beneficial to team cooperation development due to very wide usable chip range of the charging pile and different familiarity of different developers on the chips, and the same function needs to be developed on different platforms for many times, the charging pile needs to be developed again when the chip platform is replaced, so that the charging pile has low efficiency of processing data on different hardware platforms, therefore, the technical effect of improving the efficiency of processing data of the charging pile on different hardware platforms is achieved.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this application, illustrate embodiments of the invention and, together with the description, serve to explain the invention and not to limit the invention. In the drawings:
fig. 1 is a flowchart of a data processing method of a charging pile according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of a software framework for a charging pole according to an example of the invention; and
fig. 3 is a schematic diagram of a data processing device of a charging pile according to an embodiment of the invention.
Detailed Description
It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict. The present invention will be described in detail below with reference to the embodiments with reference to the attached drawings.
In order to make the technical solutions better understood by those skilled in the art, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only partial embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
It should be noted that the terms "first," "second," and the like in the description and claims of this application and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It should be understood that the data so used may be interchanged under appropriate circumstances such that embodiments of the application described herein may be used. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
Example 1
According to the embodiment of the invention, the data processing method of the charging pile is provided, and the method is applied to different hardware platforms of the charging pile.
Fig. 1 is a flowchart of a data processing method of a charging pile according to an embodiment of the present invention. As shown in fig. 1, the method may include the steps of:
step S102, acquiring data to be processed transmitted by the hardware platform through the driving layer, and determining a plurality of driving program interfaces in the driving layer.
In the technical solution provided by step S102 of the present invention, the driver layer is used for shielding the differentiation between different hardware platforms, and is used for providing a plurality of driver interfaces to the middle layer.
In this embodiment, the charging pile has a real-time requirement, and decoupling between different layers can be realized by adopting a software layering technology based on a certain real-time operating system, where the real-time operating system may be an RTX5 real-time operating system of Keil, and is not limited herein.
This embodiment adopts software layering's technique to obtain the driver layer, this driver layer docks the hardware platform downwards, dock the intermediate level upwards, can obtain the pending data that the hardware platform transmitted through the driver layer, and shield the differentiation between the different hardware platforms of driver layer butt joint downwards in the driver layer, confirm to be used for providing unified a plurality of driver interface to the intermediate level of docking upwards, this a plurality of driver interface can be for the driver interface commonly used based on hardware, different hardware platforms can have the same driver interface, that is, to different hardware platforms, the driver layer of this embodiment is used for shielding the hardware differentiation, provide unified driver interface to the intermediate level.
And step S104, transmitting the data to be processed to at least one functional interface in the middle layer through a plurality of driver interfaces.
In the technical solution provided in step S104 of the present invention, after the to-be-processed data transmitted by the hardware platform is obtained through the driver layer, and the plurality of driver interfaces are determined in the driver layer, the to-be-processed data is transmitted to at least one functional interface in the intermediate layer through the plurality of driver interfaces, where the intermediate layer is used for shielding the differences between the drivers of different hardware platforms and is used for providing at least one functional interface to the service layer, and the driver is provided by the driver layer.
In this embodiment, the middle layer interfaces the driver layer downward and interfaces the service layer upward, the middle layer is configured to shield a difference between drivers of different hardware platforms, and is configured to provide at least one functional interface to the service layer, that is, the middle layer is configured to shield a difference between different drivers provided by the driver layer that interfaces downward and provide a unified at least one functional interface to the service layer that interfaces upward, where the functional interface is also an interface based on functionality, where the driver is provided by the driver layer, and data to be processed is transmitted to the at least one functional interface in the middle layer through a plurality of driver interfaces in the driver layer.
Step S106, the data to be processed received by at least one functional interface is transmitted to at least one service module in the service layer.
In the technical solution provided by step S106 of the present invention, after the to-be-processed data is transmitted to at least one functional interface in the middle layer through the plurality of driver interfaces, the to-be-processed data received by the at least one functional interface is transmitted to at least one service module in the service layer.
In this embodiment, the service layer is butted with the intermediate layer downward and the task layer upward, and can provide a complete function module to the task layer, and transmit the to-be-processed data received by at least one function interface to at least one service module in the service layer, where each function interface has a corresponding service module.
Step S108, processing the data to be processed received by at least one functional module from at least one service module in the task layer, wherein at least one second functional module corresponds to at least one first functional module one to one.
In the technical solution provided in step S108 of the present invention, after the to-be-processed data received by at least one functional interface is transmitted to at least one service module in the service layer, the to-be-processed data received by at least one functional module from at least one service module is processed in the task layer, where at least one second functional module corresponds to at least one first functional module one to one.
In this embodiment, the task layer interfaces the service layer downward, calls at least one service module in the service layer, and processes the received data through the function module corresponding to each service module to implement flow synchronization and data transmission between the function modules, thereby combining one function module.
When the software program of the data processing method of the charging pile is layered, the modules with large function relation and high logic association degree can be arranged in one layer, and the layers need to ensure that the interfaces are few and the transmitted data amount is small, so that the software program can be divided into the driving layer, the middle layer, the business layer and the task layer.
Through the steps S102 to S108, the software program of the data processing method for the charging pile is divided into the driver layer, the middle layer, the service layer and the task layer, so that the purpose of layering the software program is achieved, the functions of each layer and the functions of the modules included in each layer are clarified, decoupling the program of the charging pile, having fixed development mode and development flow, being applicable to different hardware platforms, avoiding the problems that the charging pile has a very wide range of usable chips, different developers have different familiarity with the chips, which causes the project to be unfavorable for team cooperation development, and the same function needs to be developed on different platforms for many times, the charging pile needs to be developed again when the chip platform is replaced, so that the charging pile has low efficiency of processing data on different hardware platforms, therefore, the technical effect of improving the efficiency of processing data of the charging pile on different hardware platforms is achieved.
The above method of this embodiment is further described below.
As an optional implementation manner, in step S108, the processing, in the task layer, the to-be-processed data received by the at least one function module from the at least one service module includes: and processing the data to be processed, which are received by the at least two functional modules from the at least two service modules, in the task layer so as to perform data interaction between the at least two functional modules.
In this embodiment, at least one functional module includes at least two functional modules, and this embodiment processes data to be processed received by the at least two functional modules in a task layer, completes messaging between the functional modules, and implements flow synchronization and data transmission between the functional modules, so that one functional module is combined to perform data interaction between the at least two functional modules.
As an optional implementation manner, in step S104, transmitting the data to be processed to at least one functional interface in the middle layer through the plurality of driver interfaces includes: and calling the middle layer through the driver layer, and transmitting the data to be processed to at least one functional interface in the middle layer through a plurality of driver interfaces.
In this embodiment, the software layers of the data processing method for the charging pile include the driver layer, the middle layer, the service layer, and the task layer, where the driver layer is located on the hardware platform, the middle layer is located on the driver layer, the service layer is located on the middle layer, and the task layer is located on the service layer, and no cross-layer call between layers is possible. The embodiment can directly call the middle layer through the driver layer, so that the plurality of driver interfaces transmit the data to be processed of the hardware platform to at least one functional interface in the middle layer.
As an optional implementation manner, step S106, transmitting the to-be-processed data received by the at least one functional interface to the at least one service module in the service layer includes: and calling the service layer through the middle layer, and transmitting the data to be processed received by the at least one functional interface to at least one service module in the service layer.
The service layer of the embodiment is located above the intermediate layer, and the service layer can be directly called through the intermediate layer, so that the data to be processed received by the at least one functional interface is transmitted to the at least one service module in the service layer.
As an optional implementation manner, in step S108, the processing, in the task layer, the to-be-processed data received by the at least one function module from the at least one service module includes: and calling the task layer through the service layer, and processing the data to be processed, which is received by the at least one functional module from the at least one service module, in the task layer.
The task layer of the embodiment is located above the service layer, and the task layer is directly called through the service layer, so that data to be processed is uploaded from the next layer to the next layer, the data to be processed, which is received by at least one functional module from at least one service module, is processed in the task layer, message receiving and sending among the functional modules are completed, flow synchronization and data transmission among the functional modules are realized, and the purpose of combining one functional module is achieved.
As an optional embodiment, the method further comprises at least one of: the multiple driver interfaces are independent from each other; at least one functional interface is independent; at least one service module is independent.
In the embodiment, after the software program of the charging pile is processed in a layered manner, a plurality of modules can be divided in each layer according to actual conditions, and the purpose of high code cohesion of the same function can be achieved by adopting a module dividing manner.
Optionally, the driver layer includes a plurality of driver interfaces, and the plurality of driver interfaces are independent from each other, that is, the driver interfaces cannot be called in a cross manner, so that the coupling degree between the plurality of driver interfaces is low; the middle layer comprises at least one functional interface, and the at least one functional interface is independent from each other, namely, the functional interfaces cannot be called in a cross mode, so that the coupling degree between the at least one functional interface is low; the service layer may include at least one service module, where the at least one service module is independent from each other, that is, the service modules cannot be cross-called, so that the at least one service module has a low coupling degree; the service layer comprises at least one service module, and the at least one service module is independent from each other, namely, the service modules cannot be called in a cross mode, so that the coupling degree between the at least one service module is low.
As an optional embodiment, the method further comprises at least one of: dividing the driving layer into a plurality of sub-driving layers which are allowed to be mutually called according to a first logic relationship; dividing the middle layer into a plurality of sub-middle layers which are allowed to be mutually called according to a second logic relationship; dividing the service layer into a plurality of sub-service layers which are allowed to be mutually called according to a third logic relation; and dividing the task layer into a plurality of subtask layers which allow mutual calling according to a fourth logic relationship.
In this embodiment, the layers of the software program may be further layered according to actual situations. Optionally, the embodiment divides the driver layer into a plurality of sub driver layers allowing mutual invocation according to the first logical relationship, that is, the plurality of sub driver layers may implement cross-layer invocation, but the modules included in each sub driver layer still cannot be invoked in a cross manner.
Optionally, the middle layer is divided into a plurality of sub-middle layers allowing mutual invocation according to the second logical relationship in this embodiment, that is, the plurality of sub-middle layers may implement cross-layer invocation, but the modules included in each sub-middle layer still cannot be invoked in a cross manner.
Optionally, in this embodiment, the service layer is divided into multiple sub-service layers allowing mutual invocation according to a third logical relationship, that is, multiple sub-service layers may implement cross-layer invocation, but modules included in each sub-service layer still cannot be invoked in a cross manner.
Optionally, in this embodiment, the task layer is divided into multiple subtask layers that allow mutual invocation according to a fourth logical relationship, that is, multiple subtask layers may implement cross-layer invocation, but all modules included in each subtask layer still cannot be invoked in a cross manner.
The data processing method of the charging pile in the embodiment can be a software framework based on a scene with limited resources of an embedded single-chip microcomputer, decoupling programs of the single-chip microcomputer by adopting a layering and module-dividing mode, and extracting a set of software framework suitable for embedded development, so that the efficiency, stability, reliability and robustness of software development are improved, and the difficulty of software development is reduced.
The embodiment can realize decoupling and combination among different layers by adopting a software layering technology based on an RTX5 real-time operating system of Keil aiming at the real-time requirement of the charging pile, can realize high cohesion of codes with the same function by adopting a module dividing mode in each layer, and confirms the responsibility of each layer to confirm the function of each module, including the same function of each hardware or software, and can also package the differentiation of each hardware platform to realize the application and team development of a plurality of hardware platforms, thereby avoiding the technical problems that the project is not beneficial to team cooperation development due to different familiarity of developers to chips, the same function needs to be developed on different hardware platforms for a plurality of times, the development needs to be carried out again when the chip platforms are changed, and the data processing efficiency of the charging pile on different hardware platforms is low, therefore, the efficiency of processing data of the charging pile on different hardware platforms is improved.
The software program development and maintenance of the charging pile are simple, the software program is layered and modularized, and the development efficiency is higher because different hardware platforms have fixed development modes and development flows; based on the function upgrade of the existing hardware platform, a new function is added according to the actual situation, so that the coding is easier, the existing code is less modified, and the maintenance efficiency is improved; because the software realizes modularization and the module coupling degree is low, the cooperative development of multiple persons becomes possible, and the team cooperation is efficient. In addition, in the related art, the hardware platform has many global variables, the software program cannot be clearly layered, the modules cannot be clearly divided, one set of codes can be maintained by only one person, new people are difficult to add, after the modules are divided and layered, the functions inside the modules are single, the logic is simple, the modules are clear to external interfaces, the requirement on the quality of developers is lower, and therefore stable codes are written out more easily, the stability, the robustness and the expandability of the program are improved through the method, the program development period is shortened, the maintenance is simple, the program operation is stable and reliable, and program vulnerabilities are few.
In the embodiment, the hardware platform is simple to cross, the hardware platform is easier to migrate, a 1778 platform and an STM32 platform are arranged on the exchange pile, a service layer and a task layer can be kept consistent, only a driving layer and a middle layer can be modified, so that code maximum efficiency multiplexing is achieved, the workload is mainly on the service layer and the task layer, and development efficiency can be greatly improved; the cross-software platform is simple, and the platform migration is easier.
It should be noted that the steps illustrated in the flowcharts of the figures may be performed in a computer system such as a set of computer-executable instructions and that, although a logical order is illustrated in the flowcharts, in some cases, the steps illustrated or described may be performed in an order different than presented herein.
Example 2
The data processing method of the charging pile according to the embodiment of the invention is described below with reference to a preferred embodiment.
For a long time, due to the reasons of small project scale and difficulty of a single chip microcomputer product, low product complexity, complex application scene of the product and the like, people do not pay attention to the development of a software framework suitable for the single chip microcomputer, so that a software development framework suitable for the single chip microcomputer is not developed yet.
The embedded linux is suitable for more complex scenes, but is not suitable for application scenes with limited singlechip resources.
In the related art, the embedded development technology is mainly developed specifically for a specific chip platform, and is only used for a fixed chip platform and hardware after the development is completed. For example, use STM32F104 chip to develop, then can't directly use LPC1778 platform, linux embedded platform etc., can only use after need carrying out engineering migration or developing again, and the usable chip range of filling electric pile is very wide, different developers are different to the familiarity degree of chip, lead to the project to be unfavorable for team collaborative development, thereby can't carry out team cooperation, the development degree of difficulty is high, software quality requires the high quality of development personnel, and the same function needs to develop on different platforms many times, also need develop again when filling electric pile change chip platform, cause a large amount of human costs and time cost extravagant.
In the embodiment, the software framework of the scene with limited resources of the embedded single-chip microcomputer is based on, the programs of the single-chip microcomputer are decoupled in a layering and module-dividing mode, and a set of software framework suitable for embedded development is extracted, so that the development efficiency, stability, reliability and robustness of software are improved, and the difficulty of software development is further reduced.
Fig. 2 is a schematic diagram of a software framework of a charging pile according to an example of the invention. As shown in fig. 2, in the software layering of this embodiment, the layers cannot be called across layers, the layers can be layered again, and the software program of the charging pile can be divided into four layers according to actual situations, including: the system comprises a driving layer, a middle layer, a business layer and a task layer.
In this embodiment, the charging post includes a microprocessor, which may include: STM32F103, STM32F105, LPC1778, LPC 1768.
The hardware peripheral hardware interface of the charging pile may include: CAN interface, UART interface, SPI interface, GPIO interface, TIMER interface, ADC interface, ADS1118 interface, etc.
The driver layer interfaces the hardware peripheral interface downwards, interfaces the middle layer upwards, may include drivers, may shield differences between different hardware interfacing downwards, may provide the same driver interface to the middle layer, may be a common driver interface based on hardware, and includes: CAN interface, UART interface, SPI interface, GPIO interface, TIMER interface, ADC interface, ADS1118 interface, etc.
The middle layer calls the driver layer downwards, and docks the service layer upwards, so as to shield the differentiation of the driver and provide the same functional interface for the service layer, that is, provide the same interface based on functionality for the service layer, which may include: SAE1939, smart cloud/general 4G SDK, charging module transceiving, contactor control feedback input, module protocol, analog quantity acquisition, electric meter/card reader and the like.
The service layer calls the middle layer downwards and is butted with the task layer upwards, a complete service module can be provided for the task layer, the service module comprises a pile cloud, a pile vehicle, an electric meter, human-computer interaction, parameter configuration, acquisition control, power control, a card reader and the like, and all the service modules are independent.
The task layer calls the hardware original data transmitted from the service modules of the service layer to complete message receiving and transmitting among the functional modules, combines the functional modules together to realize flow synchronization and data transmission among the functional modules, and the functional modules comprise pile clouds, pile vehicles, electric meters, human-computer interaction, parameter configuration, acquisition control, power control, card readers and the like which are in one-to-one correspondence with the task modules.
The embodiment can achieve decoupling and integration among different layers by adopting a software layering technology based on a real-time operating system (RTX 5) of Keil aiming at the real-time requirement of the charging pile, can achieve the purpose of high cohesion of the same function code by adopting a module dividing mode in each layer, defines the functions of each layer, confirms the functions of each module, and encapsulates the differentiation of each platform, thereby achieving multi-platform application and team development.
It should be noted that, when the software program of the charging pile is layered, the modules with large function relation and high logic association degree may be layered in the same layer, and interfaces between layers are as few as possible, and transmitted data are few.
The charging pile of the embodiment is simple to develop and maintain, software achieves layering and modularization, a fixed development mode and a development process are achieved, and development efficiency is higher; based on the function upgrade of the existing platform, the addition of new function codes according to the actual situation is easier, the modification of the existing codes is less, and the maintenance efficiency is higher; team cooperation is high-efficient, because software has realized the modularization, the module degree of coupling is low, make many people cooperation development become possible, in addition, old platform uses global variable many, fail to clearly carry out the layering to the software program, also fail to clearly divide the module, one set of code often only can be maintained alone, new person joins very difficultly, and after module division and layering, the inside function singleness of module, the logic is simple, it is clear with external interface, it is lower to develop personnel's quality requirement, thereby write out stable code more easily.
In the embodiment, the hardware platform is simple in crossing, the hardware platform is easier to migrate, a 1778 platform and an STM32 platform are arranged on the exchange pile, a service layer and a task layer can be kept consistent, only a driving layer and a middle layer are modified, so that code maximum efficiency multiplexing is achieved, the workload is mainly on the service layer and the task layer, and the development efficiency can be greatly improved; the cross-software platform is simple, and the platform migration is easier.
By the method, the embedded Linux and the single chip microcomputer program can adopt the same program architecture, the modules can be reused, and metering charging (an ammeter and a card reader) and pile cloud (a smart cloud, a high-quality and easy-charging universal 4G SDK) can be realized.
Example 3
The embodiment of the invention also provides a data processing device of the charging pile, and the data processing device of the charging pile can be applied to different hardware platforms of the charging pile. It should be noted that the data processing device of the charging pile of the embodiment may be used to execute the data processing method of the charging pile of the embodiment of the present invention.
Fig. 3 is a schematic diagram of a data processing device of a charging pile according to an embodiment of the invention. As shown in fig. 3, the data processing device 30 of the charging post may include: an acquisition unit 31, a first transmission unit 32, a second transmission unit 33 and a processing unit 34.
The obtaining unit 31 is configured to obtain, through a driver layer, to-be-processed data transmitted by a hardware platform, and determine a plurality of driver interfaces in the driver layer, where the driver layer is configured to shield a difference between different hardware platforms and provide the plurality of driver interfaces to an intermediate layer.
The first transmission unit 32 is configured to transmit data to be processed to at least one functional interface in an intermediate layer through a plurality of driver interfaces, where the intermediate layer is configured to shield a difference between drivers of different hardware platforms and is configured to provide the at least one functional interface to the service layer, and the driver is provided by the driver layer.
A second transmission unit 33, configured to transmit the to-be-processed data received by the at least one functional interface to at least one service module in the service layer.
The processing unit 34 is configured to process, in the task layer, to-be-processed data received by at least one functional module from at least one service module, where at least one second functional module corresponds to at least one first functional module one to one.
In this embodiment, the data processing apparatus of the charging pile may be applied to different hardware platforms of the charging pile, the obtaining unit 31 obtains data to be processed transmitted by the hardware platforms through a driver layer, and determines a plurality of driver interfaces in the driver layer, where the driver layer is configured to shield the differences between the different hardware platforms and provide the plurality of driver interfaces to an intermediate layer, the first transmitting unit 32 transmits the data to be processed to at least one functional interface in the intermediate layer through the plurality of driver interfaces, where the intermediate layer is configured to shield the differences between the drivers of the different hardware platforms and provide at least one functional interface to the service layer, the driver is provided by the driver layer, and the data to be processed received by the at least one functional interface is transmitted to at least one service module in the service layer through the second transmitting unit 33, the data to be processed, which is received by the at least one functional module from the at least one service module, is processed in the task layer by the processing unit 34. That is to say, the data processing device of the charging pile divides a software program of the data processing method of the charging pile into a driving layer, a middle layer, a business layer and a task layer, the functions of each layer and the functions of modules included in each layer are determined, the programs of the charging pile are decoupled, the data processing device can be applied to different hardware platforms, the problem that the usable chip range of the charging pile is very wide is solved, different developers have different familiarity with the chips, the project is not beneficial to team collaborative development, the same functions need to be developed on different platforms for many times, the development needs to be carried out again when the chip platforms are replaced by the charging pile, the technical problem that the efficiency of the charging pile for processing data on different hardware platforms is low is solved, and therefore the efficiency of the charging pile for processing data.
Example 4
According to an embodiment of the present invention, there is also provided a storage medium including a stored program, wherein the program executes the data processing method of the charging pile in embodiment 1.
Example 5
According to the embodiment of the invention, the processor is used for running a program, wherein the program executes the data processing method of the charging pile in the embodiment 1 during running.
It will be apparent to those skilled in the art that the modules or steps of the present invention described above may be implemented by a general purpose computing device, they may be centralized on a single computing device or distributed across a network of multiple computing devices, and they may alternatively be implemented by program code executable by a computing device, such that they may be stored in a storage device and executed by a computing device, or fabricated separately as individual integrated circuit modules, or fabricated as a single integrated circuit module from multiple modules or steps. Thus, the present invention is not limited to any specific combination of hardware and software.
The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (10)
1. A data processing method of a charging pile is characterized in that the data processing method is applied to different hardware platforms of the charging pile and comprises the following steps:
acquiring data to be processed transmitted by the hardware platform through a driving layer, and determining a plurality of driving program interfaces in the driving layer, wherein the driving layer is used for shielding the difference between different hardware platforms and providing the plurality of driving program interfaces for a middle layer;
transmitting the data to be processed to at least one functional interface in the middle layer through the plurality of driver interfaces, wherein the middle layer is used for shielding the difference between the drivers of different hardware platforms and providing the at least one functional interface to a service layer, and the driver is provided by the driver layer;
transmitting the data to be processed received by the at least one functional interface to at least one service module in the service layer;
and processing the data to be processed, which is received by at least one functional module from at least one service module, in a task layer, wherein at least one second functional module corresponds to at least one first functional module one to one, and the task layer is in butt joint with the service layer and is used for calling the at least one service module in the service layer.
2. The method of claim 1, wherein processing the to-be-processed data received by at least one functional module from the at least one business module in a task layer comprises:
and processing the data to be processed, which are received by the at least two functional modules from the at least two service modules, in the task layer so as to perform data interaction between the at least two functional modules.
3. The method of claim 1, wherein transmitting the data to be processed to at least one functional interface in the middle tier through the plurality of driver interfaces comprises:
and calling the intermediate layer through the driver layer, and transmitting the data to be processed to at least one functional interface in the intermediate layer through the plurality of driver interfaces.
4. The method of claim 1, wherein transmitting the pending data received by the at least one functional interface to at least one service module in the service layer comprises:
and calling the service layer through the intermediate layer, and transmitting the data to be processed received by the at least one functional interface to at least one service module in the service layer.
5. The method of claim 1, wherein processing the to-be-processed data received by at least one functional module from the at least one business module in a task layer comprises:
and calling the task layer through the service layer, and processing the data to be processed, which is received by the at least one functional module from the at least one service module, in the task layer.
6. The method of claim 1, further comprising at least one of:
the plurality of driver interfaces are independent from each other;
the at least one functional interface is independent from each other;
the at least one service module is independent from each other.
7. The method of claim 1, further comprising at least one of:
dividing the driving layer into a plurality of sub-driving layers which are allowed to be mutually called according to a first logic relationship;
dividing the middle layer into a plurality of sub-middle layers which are allowed to be mutually called according to a second logic relationship;
dividing the service layer into a plurality of sub-service layers which are allowed to be mutually called according to a third logic relation;
and dividing the task layer into a plurality of subtask layers which are allowed to be mutually called according to a fourth logic relationship.
8. The utility model provides a fill electric pile's data processing apparatus which characterized in that, is applied to the different hardware platform that fill electric pile, includes:
the device comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is used for acquiring data to be processed transmitted by the hardware platform through a driving layer and determining a plurality of driving program interfaces in the driving layer, and the driving layer is used for shielding the differentiation between different hardware platforms and providing the plurality of driving program interfaces for a middle layer;
a first transmission unit, configured to transmit the to-be-processed data to at least one functional interface in the middle layer through the multiple driver interfaces, where the middle layer is configured to shield a difference between drivers of different hardware platforms, and is configured to provide the at least one functional interface to a service layer, where the driver is provided by the driver layer;
a second transmission unit, configured to transmit the to-be-processed data received by the at least one functional interface to at least one service module in the service layer;
and the processing unit is used for processing the data to be processed, which is received by at least one functional module from at least one service module, in a task layer, wherein at least one second functional module corresponds to at least one first functional module one to one, and the task layer is butted with the service layer and is used for calling the at least one service module in the service layer.
9. A storage medium, comprising a stored program, wherein the program, when executed, controls an apparatus in which the storage medium is located to perform the method of any one of claims 1 to 7.
10. A processor, characterized in that the processor is configured to run a program, wherein the program when running performs the method of any of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911072375.8A CN110990303B (en) | 2019-11-05 | 2019-11-05 | Data processing method and device for charging pile, storage medium and processor |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911072375.8A CN110990303B (en) | 2019-11-05 | 2019-11-05 | Data processing method and device for charging pile, storage medium and processor |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110990303A CN110990303A (en) | 2020-04-10 |
| CN110990303B true CN110990303B (en) | 2021-05-25 |
Family
ID=70083210
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911072375.8A Active CN110990303B (en) | 2019-11-05 | 2019-11-05 | Data processing method and device for charging pile, storage medium and processor |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110990303B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111752543B (en) * | 2020-06-29 | 2023-09-01 | 国网北京市电力公司 | Intelligent electric automobile charging system and method based on android system architecture |
| CN113946370B (en) * | 2020-07-16 | 2024-02-06 | Oppo广东移动通信有限公司 | Driving system, information processing method, information processing apparatus, and storage medium |
| CN115576706A (en) * | 2021-06-21 | 2023-01-06 | 中兴通讯股份有限公司 | Method and device for interfacing with third-party system, electronic equipment and readable medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1909705A (en) * | 2005-08-05 | 2007-02-07 | 杭州波导软件有限公司 | Universal developing platform based on mobile terminal platform |
| CN104714824A (en) * | 2015-01-09 | 2015-06-17 | 青岛海信电器股份有限公司 | Starting method of application programs |
| CN107967223A (en) * | 2017-12-07 | 2018-04-27 | 郑州云海信息技术有限公司 | A kind of multiple product lines versatility code architecture system |
| CN109271154A (en) * | 2018-08-30 | 2019-01-25 | 深圳市合众金融设备服务有限公司 | Application development platform and its operation method |
| CN109976736A (en) * | 2019-03-21 | 2019-07-05 | 安徽典典科技发展有限责任公司 | Reduce the unified platform application framework of system business model complexity |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7904914B2 (en) * | 2008-09-30 | 2011-03-08 | Microsoft Corporation | On-the-fly replacement of physical hardware with emulation |
| CN101477463B (en) * | 2009-01-22 | 2012-12-26 | 北京赛科世纪数码科技有限公司 | Software platform and software development platform used for digital television set-top box |
| CN105721580B (en) * | 2016-02-18 | 2018-09-21 | 中国人民解放军63686部队 | Open boat-carrying remote technology supports the implementation method of system |
-
2019
- 2019-11-05 CN CN201911072375.8A patent/CN110990303B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1909705A (en) * | 2005-08-05 | 2007-02-07 | 杭州波导软件有限公司 | Universal developing platform based on mobile terminal platform |
| CN104714824A (en) * | 2015-01-09 | 2015-06-17 | 青岛海信电器股份有限公司 | Starting method of application programs |
| CN107967223A (en) * | 2017-12-07 | 2018-04-27 | 郑州云海信息技术有限公司 | A kind of multiple product lines versatility code architecture system |
| CN109271154A (en) * | 2018-08-30 | 2019-01-25 | 深圳市合众金融设备服务有限公司 | Application development platform and its operation method |
| CN109976736A (en) * | 2019-03-21 | 2019-07-05 | 安徽典典科技发展有限责任公司 | Reduce the unified platform application framework of system business model complexity |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110990303A (en) | 2020-04-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110990303B (en) | Data processing method and device for charging pile, storage medium and processor | |
| CN101710361B (en) | Distributed traffic simulating platform based on Service-Oriented Architecture (SOA) and simulating method thereof | |
| CN110460369B (en) | Satellite cluster-based on-satellite cloud computing platform and management method thereof | |
| CN103488775B (en) | A kind of calculating system processed for big data and computational methods | |
| CN102200913B (en) | Layered design method of model-based automatic transmission software development platform | |
| CN112966906B (en) | Centralized monitoring platform of spacecraft ground measurement and control station resource pool architecture | |
| CN105183452B (en) | Spring AOP-based remote protocol service system for monitoring power distribution equipment | |
| CN113268319A (en) | Business process customization and distributed process scheduling method based on micro-service architecture | |
| CN102520936A (en) | Method for realizing sharing of Socket communication service on Android platform | |
| CN106533723A (en) | Virtual resource scheduling method, device and system | |
| CN108446159A (en) | Mobile terminal dual system based on Docker containers realizes system and method | |
| CN102033745B (en) | For providing the system and method for service-oriented user interface Integration Bus | |
| CN113992713B (en) | Vehicle cloud communication method and device, electronic equipment and storage medium | |
| CN101216770A (en) | Workflow engine | |
| CN103455339A (en) | Execution method of general simulation assemblies | |
| CN106502164B (en) | A kind of photovoltaic DC-to-AC converter device based on dual microcontroller | |
| CN110324194B (en) | Method, apparatus, system and medium for load balancing | |
| CN110471664A (en) | A kind of heterogeneous software platform based on OSGi framework unifies interconnection method | |
| CN108874699B (en) | Method and device for using MTP (Multi-time transfer protocol) function by multiple systems and electronic equipment | |
| CN101169740A (en) | EJB component dynamic migration method | |
| CN102546637B (en) | Communication terminal and method thereof for realizing communication protocol | |
| CN115309700A (en) | Universal architecture implementation method for heterogeneous file service | |
| CN109388770A (en) | Web page generation method and device | |
| CN108399096A (en) | Multi-task scheduling time sequence monitoring method and system for battery management system | |
| CN104407907B (en) | A kind of method and system that web tab is converted into different application platforms code |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |