CN117689083A - Method, device, system and medium for managing solar power - Google Patents
Method, device, system and medium for managing solar power Download PDFInfo
- Publication number
- CN117689083A CN117689083A CN202410083349.XA CN202410083349A CN117689083A CN 117689083 A CN117689083 A CN 117689083A CN 202410083349 A CN202410083349 A CN 202410083349A CN 117689083 A CN117689083 A CN 117689083A
- Authority
- CN
- China
- Prior art keywords
- data
- electric quantity
- industry
- daily load
- electricity consumption
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 41
- 230000005611 electricity Effects 0.000 claims abstract description 131
- 238000007726 management method Methods 0.000 claims description 36
- 238000004590 computer program Methods 0.000 claims description 10
- 238000012216 screening Methods 0.000 claims description 7
- 238000012549 training Methods 0.000 claims description 6
- 238000006243 chemical reaction Methods 0.000 claims description 4
- 230000006870 function Effects 0.000 description 32
- 238000010586 diagram Methods 0.000 description 11
- 238000004458 analytical method Methods 0.000 description 9
- 238000004364 calculation method Methods 0.000 description 7
- 238000005516 engineering process Methods 0.000 description 7
- 230000008569 process Effects 0.000 description 5
- 230000004044 response Effects 0.000 description 4
- 238000004891 communication Methods 0.000 description 3
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000001514 detection method Methods 0.000 description 3
- 238000011161 development Methods 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 239000011159 matrix material Substances 0.000 description 2
- 238000011160 research Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000004422 calculation algorithm Methods 0.000 description 1
- 238000004140 cleaning Methods 0.000 description 1
- 238000013527 convolutional neural network Methods 0.000 description 1
- 238000007405 data analysis Methods 0.000 description 1
- 238000013499 data model Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000007613 environmental effect Effects 0.000 description 1
- 238000001914 filtration Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002085 persistent effect Effects 0.000 description 1
- 231100000279 safety data Toxicity 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/04—Forecasting or optimisation specially adapted for administrative or management purposes, e.g. linear programming or "cutting stock problem"
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/242—Query formulation
- G06F16/2433—Query languages
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F18/00—Pattern recognition
- G06F18/20—Analysing
- G06F18/24—Classification techniques
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06N—COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
- G06N3/00—Computing arrangements based on biological models
- G06N3/02—Neural networks
- G06N3/04—Architecture, e.g. interconnection topology
- G06N3/0464—Convolutional networks [CNN, ConvNet]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
- G06Q50/06—Energy or water supply
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- General Engineering & Computer Science (AREA)
- Economics (AREA)
- Health & Medical Sciences (AREA)
- Strategic Management (AREA)
- Human Resources & Organizations (AREA)
- Computational Linguistics (AREA)
- Evolutionary Computation (AREA)
- Artificial Intelligence (AREA)
- General Business, Economics & Management (AREA)
- Mathematical Physics (AREA)
- Tourism & Hospitality (AREA)
- General Health & Medical Sciences (AREA)
- Databases & Information Systems (AREA)
- Life Sciences & Earth Sciences (AREA)
- Marketing (AREA)
- Bioinformatics & Cheminformatics (AREA)
- Computing Systems (AREA)
- Biophysics (AREA)
- Biomedical Technology (AREA)
- Public Health (AREA)
- Water Supply & Treatment (AREA)
- Computer Vision & Pattern Recognition (AREA)
- Bioinformatics & Computational Biology (AREA)
- Primary Health Care (AREA)
- Evolutionary Biology (AREA)
- Software Systems (AREA)
- Molecular Biology (AREA)
- Development Economics (AREA)
- Game Theory and Decision Science (AREA)
- Entrepreneurship & Innovation (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention relates to the technical field of centralized management of power grid business data, in particular to a method, a device, a system and a medium for managing daily electricity. Calculating electric quantity data of a user according to daily load data, wherein the daily load data at least comprises: daily load data curves of different industries and daily load curves of different areas; the function display field is marked for the electric quantity data, and at least comprises: industry type, user number and current day electric quantity, and acquiring industry electric quantity inquiry information, wherein the industry electric quantity inquiry information comprises: and inquiring in the electric quantity data of the marking function display field according to the electric quantity inquiry information of the industry to obtain target display data. The electricity consumption in the marketing business system and the electricity consumption information acquisition system can be directly extracted, the problems of large workload and low efficiency of a traditional manual mode of a local market company are solved, and the management efficiency of the electricity consumption information of a user is improved.
Description
Technical Field
The invention relates to the technical field of centralized management of power grid business data, in particular to a method, a device, a system and a medium for managing daily electricity.
Background
The electric power industry is an important basic industry for national economic development and is also an important guarantee for national economic development. However, along with the shortage of energy, the continuous improvement of environmental protection requirements and the continuous increase of power demands of users, the contradiction between power supply and demand is increasingly prominent, the power resource is reasonably and effectively utilized, and the power management mode is improved, so that the method is an important task in front of the power department.
In the prior art, the analysis of electric quantity data in the electric power industry mainly depends on manual operation, and multi-dimensional electric quantity data analysis is realized through a mode of extracting data in a plurality of systems. This way increases labor cost and workload, and makes management efficiency of electric quantity lower, so how to improve management efficiency of electric quantity is a problem to be solved.
Disclosure of Invention
In view of this, the embodiments of the present application provide a method, an apparatus, a device, and a medium for managing solar power, so as to solve the problem of low power management efficiency.
In a first aspect, an embodiment of the present application provides a method for managing solar power, where the method includes:
acquiring daily load data of a user, and calculating electric quantity data of the user according to the daily load data, wherein the daily load data at least comprises: daily load data curves of different industries and daily load curves of different areas;
marking a function presentation field for the charge data, the function presentation field comprising at least: industry type, number of users and current day power;
acquiring industry electricity quantity inquiry information, wherein the industry electricity quantity inquiry information comprises: one or more of unit type, power supply unit, industry type and industry classification;
and inquiring in the electric quantity data of the marking function display field according to the industry electric quantity inquiry information to obtain target display data.
In a second aspect, an embodiment of the present application provides a management apparatus for solar electricity, including:
the first acquisition module is used for acquiring daily load data of a user, calculating electric quantity data of the user according to the daily load data, wherein the daily load data at least comprises: daily load data curves of different industries and daily load curves of different areas;
the marking module is configured to mark a function presentation field for the electrical quantity data, where the function presentation field includes at least: industry type, number of users and current day power;
the second acquisition module is used for acquiring industry electric quantity inquiry information, wherein the industry electric quantity inquiry information comprises: one or more of unit type, power supply unit, industry type and industry classification;
and the query module is used for querying the electric quantity data of the marking function display field according to the industry electric quantity query information to obtain target display data.
In a third aspect, an embodiment of the present application provides a solar power management system, where the management system includes an application server cluster, an Ngnix server, a database server, a PC end device, and a big data platform, at least one server in the application server cluster is connected to the gnix server, at least one server in the application server cluster is connected to the database server, the database server is connected to the big data platform, and the PC end device is connected to at least one server in the application server cluster, where the servers in the application server cluster implement the management method as described above when executing.
In a fourth aspect, embodiments of the present application provide a computer-readable storage medium storing a computer program that, when executed by a processor, implements the management method according to the first aspect.
Compared with the prior art, the invention has the beneficial effects that:
acquiring daily load data of a user, and calculating electric quantity data of the user according to the daily load data, wherein the daily load data at least comprises: daily load data curves of different industries and daily load curves of different areas; the function display field is marked for the electric quantity data, and at least comprises: industry type, user number and current day electric quantity, and acquiring industry electric quantity inquiry information, wherein the industry electric quantity inquiry information comprises: and inquiring in the electric quantity data of the marking function display field according to the electric quantity inquiry information of the industry to obtain target display data. In the method, the electricity consumption in the marketing business system and the electricity consumption information acquisition system can be directly extracted, the problems of large workload and low efficiency of a traditional artificial mode of a city company are solved, and the management efficiency of the electricity consumption information of a user is improved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings that are needed in the description of the embodiments of the present invention will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present invention, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a flow chart of a method for managing solar electricity according to an embodiment of the present application;
FIG. 2 is an interface schematic diagram of an industry electricity information statistics provided in an embodiment of the present application;
FIG. 3 is a block diagram of a technical architecture in a daily power management system according to an embodiment of the present application;
FIG. 4 is a block diagram of a data architecture in a daily power management system according to an embodiment of the present application;
FIG. 5 is a block diagram of a deployment architecture in a solar management system in accordance with one embodiment of the present application;
fig. 6 is a block diagram of a solar power management device according to an embodiment of the present application.
Description of the embodiments
The following description of the embodiments of the present invention will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all embodiments of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
It should be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It should also be understood that the term "and/or" as used in this specification and the appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes such combinations.
As used in this specification and the appended claims, the term "if" may be interpreted as "when..once" or "in response to a determination" or "in response to detection" depending on the context. Similarly, the phrase "if a determination" or "if a [ described condition or event ] is detected" may be interpreted in the context of meaning "upon determination" or "in response to determination" or "upon detection of a [ described condition or event ]" or "in response to detection of a [ described condition or event ]".
In addition, in the description of the present application and the appended claims, the terms "first," "second," "third," and the like are used merely to distinguish between descriptions and are not to be construed as indicating or implying relative importance.
Reference in the specification to "one embodiment" or "some embodiments" or the like means that a particular feature, structure, or characteristic described in connection with the embodiment is included in one or more embodiments of the application. Thus, appearances of the phrases "in one embodiment," "in some embodiments," "in other embodiments," and the like in the specification are not necessarily all referring to the same embodiment, but mean "one or more but not all embodiments" unless expressly specified otherwise. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless expressly specified otherwise.
It should be understood that the sequence numbers of the steps in the following embodiments do not mean the order of execution, and the execution order of the processes should be determined by the functions and the internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.
In order to illustrate the technical solution of the present application, the following description is made by specific examples.
Referring to fig. 1, a flow chart of a method for managing daily electricity according to an embodiment of the present application, as shown in fig. 1, the method for managing daily electricity may include the following steps:
s101: acquiring daily load data of a user, and calculating electric quantity data of the user according to the daily load data, wherein the daily load data at least comprises: daily load data curves of different industries and daily load curves of different regions.
In step S101, daily load data of a user is obtained, and electric quantity data of the user is calculated according to the daily load data, wherein the daily load data is corresponding daily load curve data, the magnitude of a load value in the curve data represents the electric quantity load at each moment, and the electric quantity data of the user is obtained through calculation, and the daily load data at least comprises: the daily load data curves of different industries and the daily load curves of different regions are real-time power consumption of different regions.
In this embodiment, when daily load data of a user is acquired, data in a source system may be acquired in real time, and coincidence data of each moment is acquired, where the source system is any system that can acquire an electricity load, for example, an electricity consumption information acquisition system, an influence service system, and the like.
In this embodiment, the daily load data at least includes: the daily load data curves of the branch industries and the daily load data curves of the branch areas and the daily load curves of the branch areas, wherein the daily load data curves of the branch industries are real-time electricity consumption of different industries, for example, the marketing industry and the government industry, the daily load curves of the marketing industry and the daily load curves of the government industry can be obtained, the electricity consumption fluctuation of the corresponding industry in one day can be intuitively displayed, the electricity consumption of the industry is conveniently analyzed, the electricity consumption rule of the industry is conveniently determined, so that a power supply enterprise can better perform power supply service according to the corresponding electricity consumption rule, for example, if the business is operated at night, the electricity consumption at night is generally larger than the daytime electricity consumption, and when the corresponding daily load curve of the business is obtained, the rule can be analyzed according to the daily load curve, and the power supply enterprise can provide more power supply to the business at night.
The load curves of the different areas are real-time electricity consumption of the different areas, for example, a daily load curve of the commercial area and a daily load curve of the residential area can be obtained, the corresponding daily load curve can be visually displayed, the fluctuation of the electricity consumption of the corresponding area in one day can be conveniently analyzed, the electricity consumption of the area is conveniently determined, and the electricity consumption rule of the area can be conveniently and well used by a power supply enterprise according to the corresponding electricity consumption rule.
And calculating the electric quantity data of the user according to the daily load data, and calculating through an integral formula during calculation to obtain the electric quantity data corresponding to each day. After the daily electric quantity data of the user are obtained, the monthly electric quantity data can be calculated according to the daily electric quantity data of the user, and the annual electric quantity data of the user can be calculated according to the daily electric quantity data of the user.
When calculating the electric quantity data of the user according to the daily load data, other methods can be used for calculation, and the real-time example is not limited.
Optionally, acquiring daily load data of the user includes:
calling real-time daily load data in the electricity consumption information acquisition system by using a preset technical interface layer;
and calling historical electricity consumption data in the marketing business system by using a preset technical interface layer.
In this embodiment, the real-time daily load data in the electricity consumption information acquisition system is called by using a preset technical interface layer, and the historical electricity consumption data and the cost corresponding to the historical electricity consumption in the marketing business system are called by using the preset technical interface layer. The interface in the preset technical interface layer may be a Java native programming interface technology, and in the embodiment of the present invention, the Java native programming interface technology is applied, so that real-time daily load data in the electric information acquisition system and historical electricity consumption data in the marketing service system may be invoked in real time. Among other things, java native programming interface technology is part of the JDK (Java development kit), which allows Java code to use code and code libraries written in the C/C++ language.
And calling an interface function in the dynamic link library by applying Java local interface technology so as to call the data information in real time through a functional interface in the dynamic link library. The Java local interface technology is applied, so that the display of the data information is realized, and the efficiency of data transmission and display is improved.
In another implementation, real-time daily load data in the electric information acquisition system and historical electricity consumption data in the marketing business system are called in real time through a WebService interface technology.
Optionally, acquiring daily load data of the user includes:
invoking real-time daily load data in the electricity consumption information acquisition system through a technical interface layer built in the Ngnix server;
historical electricity consumption data in the marketing business system is called through a technical interface layer built in the Ngnix server.
In this embodiment, real-time daily load data and historical electricity consumption data are called through a technology interface layer built in the Ngnix server. The corresponding data is called in real time by using the ngnix server to carry out a load balancing mechanism, and the called real-time daily load data and the historical power consumption data can be sent to a redis (remote dictionary service) in a server. Redis is a key-value storage system, data is stored in a memory, incremental operation of the data is supported, full operation can be avoided when the data is queried, rich data operations such as push/pop and add/remove are supported, the operations are all atomic, and the problem of inconsistent data is avoided. The Ngnix server is internally provided with a load balancing module, so that the load balancing of data distribution can be conveniently realized according to different application scenes.
Real-time daily load data and historical electricity consumption data can also be sent to a Cassandra database, wherein Cassandra is an open source distributed NoSQL database system. The method is originally developed by Facebook and is used for storing simple format data such as inboxes, a fully distributed architecture of Google BigTable data model and Amazon Dynamo is integrated, the Facebook opens Cassandra in 2008, and after that, the Cassandra has good expandability, the method is adopted by well-known Web 2.0 websites such as Digg and Twitter, and becomes a popular distributed structured data storage scheme. Cassandra is a hybrid, non-relational database, similar to BigTable of Google. The main functions of the method are richer than Dynamo (distributed Key-Value storage system), and the method is the most abundant in functions in non-relational databases and most similar to relational databases. The supported data structure is very loose and is in a json-like bjson format, so more complex data types can be stored. The Presto query engine is a Master-Slave architecture, and consists of a Coordinator node, a Discovery Server node, and a plurality of workbench nodes, wherein the Discovery Server is usually embedded in the Coordinator node. The Coordinator is responsible for analyzing SQL sentences, generating an execution plan and distributing execution tasks to the workbench nodes for execution.
It should be noted that, to save resources, the secure operation platform and the nginx service are deployed in the same virtual machine and in the management network. Of course, in other embodiments, the secure operating platform may be deployed in a different virtual machine than the nginx service.
After calculating the electric quantity data of the user according to the daily load data, the method further comprises the following steps:
training a prediction model of the daily electricity consumption of the user according to the historical electricity consumption data and a preset time interval to obtain a trained daily electricity consumption prediction model;
predicting the daily electricity consumption of the user by using the trained daily electricity consumption prediction model to obtain predicted electricity consumption;
and acquiring the actual power consumption of the user on the same day, calculating the difference between the predicted power consumption and the actual power consumption, and generating power consumption early warning information if the difference is larger than a preset threshold.
In the embodiment, according to the historical electricity consumption data and a preset time interval, training a prediction model of the daily electricity consumption of a user to obtain a trained daily electricity consumption prediction model; according to the historical electricity consumption data and a preset time interval, constructing sequence data of the historical time electricity consumption, and converting the sequence data of the historical time electricity consumption into visualized time sequence data; converting the time sequence data into matrix data, extracting data trend characteristics of the matrix data by adopting a convolutional neural network model supporting input of multivariate data, constructing a joint time sequence data trend prediction model based on a conditional random field according to the data trend characteristics, namely a prediction model, and training the prediction model by using visualized time sequence data to obtain a trained daily electric quantity prediction model. And predicting the daily electricity consumption of the user by using the trained daily electricity consumption prediction model, and inputting time series data to be predicted into the trained daily electricity consumption prediction model during prediction, wherein the time series data to be predicted is time series data formed by a plurality of continuous days, and outputting the predicted electricity consumption. And acquiring the actual electricity consumption of the user on the same day, calculating the difference between the predicted electricity consumption and the actual electricity consumption, and if the difference is larger than a preset threshold, namely the predicted electricity consumption exceeds the fluctuation range of the daily electricity consumption, generating electricity consumption early warning information and sending the early warning information to the user. So as to prevent according to the corresponding early warning information.
102: the function display field is marked for the electric quantity data, and at least comprises: industry type, number of users, and current day power.
In this embodiment, the function display field is marked for the electric quantity data, and the function display field at least includes: industry type, user number and current day electric quantity, wherein the function display fields are used for quickly obtaining data obtained after electric quantity analysis and management, and each function display field represents an electric quantity analysis result to be displayed.
In this embodiment, a function display field is marked for the electric quantity data, so that the display field can be displayed on a corresponding front-end interface, and when the front-end interface is configured, the configuration of the JOSN component described by the front-end interface is sequentially acquired; the JOSN component configuration is located in the JOSN configuration described by the front-end interface. First, the configuration of the JOSN component described by the front-end interface needs to be acquired sequentially. It should be noted that the JOSN component configuration is located in the JOSN configuration described in the front-end interface. The abstract type of the JOSN component configuration is obtained to determine the node object identification of the JOSN component configuration based on the abstract type. And determining the node object identification of the JOSN component configuration according to the abstract type by acquiring the abstract type of the JOSN component configuration. Specifically, in one or more embodiments of the present specification, determining a node object identifier of a JOSN component configuration based on an abstract type specifically includes: acquiring a node acquisition instruction of a preset JSON configuration processor; the node acquisition instruction is as follows: the getNodeByType then inputs the abstract type field into the node get instruction, thereby getting the node object identifier configured by the JOSN component. Further, in one or more embodiments of the present disclosure, before obtaining the abstract type of the JOSN component configuration to determine the node object identifier of the JOSN component configuration based on the abstract type, the method further includes: determining an initial type of JOSN configuration described by a front-end interface; wherein, the initial types include: object, array, number, string, boolean. Determining a type abstraction rule of the initial type based on the field length and the field attribute of each initial type so as to abstract the initial type based on the type abstraction rule to obtain an abstract type; wherein the abstract types include: simple type, node list.
In a certain application scenario, when abstract is performed on the JSON type, nodes configured by JSON are mainly divided into the following types: an object, an array, a number, a character string and a Boolean are set as a type abstract rule that "number, character string and Boolean" are abstract as simple types, "the object" is abstract as a node type, and "the array" is abstract as a node list, so that the abstract rule is abstract as three classes based on the type abstract rule: simple type (number, string, boolean), node (object), node list (array). By abstracting the types, since the simple type can be described with the basic type number, string, bool of the basic type with TypeScript, etc., the abstraction can be mainly made for the nodes and the node list. It should be further noted that the node class includes: original node object, other higher level node objects. The node list class includes: the original node list object.
And acquiring the corresponding node object from a preset node object memory based on the node object identification. In order to smoothly convert JSON configuration into abstract node objects, in the embodiment of the present disclosure, corresponding node objects are obtained in a preset node object memory according to node object identifiers. Further, in one or more embodiments of the present disclosure, before the preset node object memory acquires the corresponding node object based on the node object identifier, the method further includes: determining the corresponding relation between the node object identification and the corresponding node object; establishing a key value pair of the node object identifier and the corresponding node object based on the corresponding relation; and storing the corresponding node object in a preset node object memory so as to acquire the node object corresponding to the node object identification in the preset node memory based on the key value pair.
And assigning the corresponding node object based on the value configured by the JOSN component to obtain the assigned node object. To avoid the problem of poor performance and ease of use in modifying JSON configurations because layer-by-layer lookup is required when the JSON level is deep. The specification firstly carries out assignment on the corresponding node object according to the value configured by the JOSN component so as to obtain the assigned node object.
And iteratively acquiring the attributes of the assigned node objects to judge whether the JOSN component configuration is completed or not based on the abstract types corresponding to the attributes so as to be converted into the corresponding node objects. In order to convert all JSON configurations into objects, in the embodiment of the present disclosure, the attributes of the node objects after assignment are obtained iteratively, so as to determine, based on the abstract type corresponding to the attributes, whether the jsn component configuration is abstract, so as to convert the JSON component configuration into the corresponding node objects.
Optionally, the function display field further includes a last year current day power, a ratio of the current day power to the last year current day power, a month current month power to the last year current month power, a current year power, a last year power, and a ratio of the current year power to the last year power. Referring to fig. 2, an interface schematic diagram of an industry electricity information statistics table provided in an embodiment of the present application includes function fields of the last year electricity, the same ratio of the current day, the same ratio of the current month electricity, the same ratio of the last year and the current month electricity, the same ratio of the current year and the same ratio of the current month electricity, the same ratio of the last year and the same ratio of the current year electricity, and each function field is displayed in a list form.
S103: acquiring industry electricity quantity inquiry information, wherein the industry electricity quantity inquiry information comprises: one or more of unit type, power supply unit, industry type, industry classification.
In step S103, industry electricity quantity query information is acquired, wherein the query information may be at least one of a unit type or a power supply unit or an industry type or an industry classification.
In this embodiment, referring to fig. 2, an interface schematic diagram of an industry electric quantity information statistics table provided in the embodiment of the present application is shown. The system comprises one or more of inquiry information capable of being inquired, unit type, power supply unit, industry type and industry classification. And inputting the query information into an interface of the system, and determining electric quantity data corresponding to the query information according to the input query information so as to display the corresponding electric quantity data in a data column.
S104: and inquiring in the electric quantity data of the marking function display field according to the industry electric quantity inquiry information to obtain target display data.
In step S104, according to the industry electricity quantity inquiry information, inquiry is performed in the electricity quantity data of the marking function display field, so as to obtain target display data. The target display data are corresponding data after the electric quantity data are managed.
In this embodiment, according to the industry electricity quantity inquiry information, the electricity quantity data satisfying the inquiry information is inquired in the electricity quantity data of the marking function display field, and the corresponding data is displayed, for example, the electricity quantity data of the marketing industry is inquired, and the corresponding electricity quantity data is the electricity quantity data of the marketing industry, that is, the target display data. And displaying the electric quantity data corresponding to the marketing industry.
Optionally, according to the industry electricity quantity inquiry information, inquiring in the electricity quantity data of the marking function display field to obtain target display data includes:
screening electric quantity data meeting industry electric quantity inquiry information by utilizing a preset data summarizing layer;
summarizing the electric quantity data meeting the electric quantity inquiry information of the industry by utilizing a preset public summarizing layer to obtain summarized electric quantity data;
and converting the format of the collected electric quantity data by utilizing a preset standard data layer to obtain standard format data of the collected electric quantity data, wherein the standard format data is target display data.
In this embodiment, the preset data summarizing layer is utilized to screen the electric quantity data meeting the electric quantity query information of the industry, and when screening, the screening can be performed piece by piece based on the corresponding query information. Summarizing the electric quantity data meeting the electric quantity inquiry information of the industry by utilizing a preset public summarizing layer to obtain summarized electric quantity data, and performing format conversion on the summarized electric quantity data by utilizing a preset standard data layer to obtain standard format data of the summarized electric quantity data, wherein the standard format data is target display data.
Referring to fig. 3, a structural diagram of a technical architecture in a solar management system according to an embodiment of the present application is shown. The system comprises a storage module, a service module, an interface module and a front-end module. The storage module may include a cache unit, a persistent storage unit, and the like. The service module comprises an inter-service communication unit, a service treatment unit and an access control unit, the interface module comprises an Nginx interface server, and the front-end module comprises a WEB unit.
Referring to fig. 4, a block diagram of a data architecture in a daily electricity management system according to an embodiment of the present application includes a source system module, a data access module, and a daily electricity lean management analysis module. The source system module comprises an electricity consumption information acquisition system and a marketing business acquisition system, the data access muzzle comprises a technical interface layer, a standard data layer, a data converging layer and a public summarizing layer, and the daily electricity quantity lean management analysis module comprises a marketing big data platform, a daily calculation daily kernel unit, an electricity quantity statistics analysis unit and a load statistics analysis unit. The public summary layer is used for all data sets, the data summary layer is used for the data needed by the primary screening system, the standard data layer is used for processing the data into a page display form, and the technical interface layer is used for data pushing or calling interfaces. And the electricity consumption information acquisition system acquires the user electricity consumption representation value, pushes the user electricity consumption representation value to the marketing day calculation day core platform for electricity consumption calculation, pushes the user electricity consumption representation value to the marketing big data platform for service data cleaning processing, and displays different dimensionalities of result data in the daily electricity consumption lean management analysis research system. The load data is directly transferred to the load data interface of the acquisition system by the daily electricity lean management analysis research system, so that the data pushing time is shortened, and the real-time performance of load monitoring is greatly improved.
Referring to fig. 5, a structure diagram of a deployment architecture in a solar power management system according to an embodiment of the present application includes a PC end user, an application server cluster, an Ngnix server, a mysql database server, a PC end device, and a big data platform, at least one server in the application server cluster is connected to the gnix server, at least one server in the application server cluster is connected to the database server, the database server is connected to the big data platform, the PC end device is connected to at least one server in the application server cluster, the application server cluster calculates real-time daily load data called by the Ngnix server, the big data platform stores real-time daily load data, and the big data platform includes historical power consumption data and collected data, that is, the historical power consumption data and the real-time daily load data. The mysql database stores data such as electric quantity and the like pushed by a big data platform, archive data (user archive, unit information archive, group archive and industry archive) and the like, and data filtering is carried out between a PC end user and the server cluster, the Ngnix server and the mysql database through a firewall, and the filtered safety data is displayed on the PC end.
Acquiring daily load data of a user, and calculating electric quantity data of the user according to the daily load data, wherein the daily load data at least comprises: daily load data curves of different industries and daily load curves of different areas; the function display field is marked for the electric quantity data, and at least comprises: industry type, user number and current day electric quantity, and acquiring industry electric quantity inquiry information, wherein the industry electric quantity inquiry information comprises: and inquiring in the electric quantity data of the marking function display field according to the electric quantity inquiry information of the industry to obtain target display data. In the method, the electricity consumption in the marketing business system and the electricity consumption information acquisition system can be directly extracted, the problems of large workload and low efficiency of a traditional artificial mode of a city company are solved, and the management efficiency of the electricity consumption information of a user is improved.
Fig. 6 shows a block diagram of a structure of a daily electricity management device according to an embodiment of the present application, referring to fig. 6, the management device 60 includes:
the first obtaining module 61 is configured to obtain daily load data of a user, calculate electric quantity data of the user according to the daily load data, where the daily load data at least includes: daily load data curves of different industries and daily load curves of different areas;
the marking module 62 is configured to mark the function presentation field for the power data, where the function presentation field includes at least: industry type, number of users and current day power;
the second obtaining module 63 is configured to obtain industry electricity quantity query information, where the industry electricity quantity query information includes: one or more of unit type, power supply unit, industry type and industry classification;
and the query module 64 is configured to query the electric quantity data in the tag function display field according to the industry electric quantity query information to obtain target display data.
Optionally, the first obtaining module 61 includes:
the first calling unit is used for calling real-time daily load data in the electricity consumption information acquisition system by utilizing a preset technical interface layer.
And the second calling unit is used for calling the historical electricity consumption data in the marketing business system by utilizing a preset technical interface layer.
Optionally, the first obtaining module 61 includes:
the third calling unit is used for calling real-time daily load data in the electricity consumption information acquisition system through a technical interface layer built in the Ngnix server;
and the fourth calling unit is used for using the historical electricity consumption data in the marketing business system through a technical interface layer built in the Ngnix server.
Optionally, the query module 64 includes:
and the screening unit is used for screening the electric quantity data meeting the electric quantity inquiry information of the industry by utilizing a preset data summarizing layer.
And the summarizing unit is used for summarizing the electric quantity data meeting the electric quantity inquiry information of the industry by utilizing a preset public summarizing layer to obtain the summarized electric quantity data.
The conversion unit is used for carrying out format conversion on the collected electric quantity data by utilizing a preset standard data layer to obtain standard format data of the collected electric quantity data, wherein the standard format data is target display data.
Optionally, the management device 60 further includes:
and the training module is used for training the prediction model of the daily electricity consumption of the user according to the historical electricity consumption data and the preset time interval to obtain a trained daily electricity consumption prediction model.
And the prediction module is used for predicting the daily electricity consumption of the user by using the trained daily electricity consumption prediction model to obtain predicted electricity consumption.
The calculation module is used for obtaining the actual electricity consumption of the user on the same day, calculating the difference between the predicted electricity consumption and the actual electricity consumption, generating electricity consumption early warning information if the difference is larger than a preset threshold value, and sending the early warning information to the user.
It should be noted that, because the content of information interaction and execution process between the modules is based on the same concept as the method embodiment of the present application, specific functions and technical effects thereof may be referred to in the method embodiment section, and details are not repeated herein.
The management system for the daily electricity quantity comprises an application server cluster, an Ngnix server, a database, a PC end and a big data platform, wherein at least one server in the application server cluster is connected with the gnix server, at least one server in the application server cluster is connected with the database server, the database server is connected with the big data platform, the PC end is connected with at least one server in the application server cluster, and the management method for the daily electricity quantity is realized when the application server cluster is executed.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-described division of the functional units and modules is illustrated, and in practical application, the above-described functional distribution may be performed by different functional units and modules according to needs, i.e. the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-described functions. The functional units and modules in the embodiment may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit, where the integrated units may be implemented in a form of hardware or a form of a software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working process of the units and modules in the above device may refer to the corresponding process in the foregoing method embodiment, which is not described herein again. The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the present application implements all or part of the flow of the method of the above-described embodiments, and may be implemented by a computer program to instruct related hardware, where the computer program may be stored in a computer readable storage medium, where the computer program, when executed by a processor, may implement the steps of the method embodiments described above. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, executable files or in some intermediate form, etc. The computer readable medium may include at least: any entity or device capable of carrying computer program code, a recording medium, a computer Memory, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), an electrical carrier signal, a telecommunications signal, and a software distribution medium. Such as a U-disk, removable hard disk, magnetic or optical disk, etc. In some jurisdictions, computer readable media may not be electrical carrier signals and telecommunications signals in accordance with legislation and patent practice.
The present application implementing all or part of the flow of the method of the above embodiment may also be implemented by a computer program product, which when run on a computer device causes the computer device to execute the steps of the method embodiment described above.
In the foregoing embodiments, the descriptions of the embodiments are emphasized, and in part, not described or illustrated in any particular embodiment, reference is made to the related descriptions of other embodiments.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
In the embodiments provided in this application, it should be understood that the disclosed apparatus/computer device and method may be implemented in other ways. For example, the apparatus/computer device embodiments described above are merely illustrative, e.g., the division of modules or units is merely a logical functional division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection via interfaces, devices or units, which may be in electrical, mechanical or other forms.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed over a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
The above embodiments are only for illustrating the technical solution of the present application, and are not limiting thereof; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present application, and are intended to be included in the scope of the present application.
Claims (10)
1. A method for managing solar electricity, the method comprising:
acquiring daily load data of a user, and calculating electric quantity data of the user according to the daily load data, wherein the daily load data at least comprises: daily load data curves of different industries and daily load curves of different areas;
marking a function presentation field for the charge data, the function presentation field comprising at least: industry type, number of users and current day power;
acquiring industry electricity quantity inquiry information, wherein the industry electricity quantity inquiry information comprises: one or more of unit type, power supply unit, industry type and industry classification;
and inquiring in the electric quantity data of the marking function display field according to the industry electric quantity inquiry information to obtain target display data.
2. The method of claim 1, wherein the function presentation field further comprises a last year current day power, a ratio of the current day power to the last year current day power, a month current day power, a last year current month power, a ratio of the month current day power to the last year current month power, a current year current power, a last year current power, and a ratio of the current year current day power to the last year current day power.
3. The method of managing as set forth in claim 1, wherein the acquiring daily load data of the user includes:
calling real-time daily load data in the electricity consumption information acquisition system by using a preset technical interface layer;
and calling historical electricity consumption data in the marketing business system by using a preset technical interface layer.
4. A method of managing as set forth in claim 3, wherein said acquiring daily load data of the user includes:
invoking real-time daily load data in the electricity consumption information acquisition system through a technical interface layer built in the Ngnix server;
historical electricity consumption data in the marketing business system is called through a technical interface layer built in the Ngnix server.
5. The method of claim 3, wherein the querying in the power data of the tag function presentation field according to the industry power query information to obtain target presentation data comprises:
screening electric quantity data meeting the electric quantity inquiry information of the industry by utilizing a preset data summarizing layer;
summarizing the electric quantity data meeting the electric quantity inquiry information of the industry by utilizing a preset public summarizing layer to obtain summarized electric quantity data;
and carrying out format conversion on the summarized electric quantity data by utilizing a preset standard data layer to obtain standard format data of the summarized electric quantity data, wherein the standard format data is target display data.
6. The method of managing according to claim 3, wherein after calculating the power data of the user from the daily load data, further comprising:
training a daily electricity consumption prediction model of the user according to the historical electricity consumption data and a preset time interval to obtain a trained daily electricity consumption prediction model;
predicting the daily electricity consumption of the user by using the trained daily electricity consumption prediction model to obtain predicted electricity consumption;
and acquiring the actual power consumption of the user on the same day, calculating the difference between the predicted power consumption and the actual power consumption, and generating power consumption early warning information if the difference is larger than a preset threshold.
7. A solar power management apparatus, the apparatus comprising:
the first acquisition module is used for acquiring daily load data of a user, calculating electric quantity data of the user according to the daily load data, wherein the daily load data at least comprises: daily load data curves of different industries and daily load curves of different areas;
the marking module is configured to mark a function presentation field for the electrical quantity data, where the function presentation field includes at least: industry type, number of users and current day power;
the second acquisition module is used for acquiring industry electric quantity inquiry information, wherein the industry electric quantity inquiry information comprises: one or more of unit type, power supply unit, industry type and industry classification;
and the query module is used for querying the electric quantity data of the marking function display field according to the industry electric quantity query information to obtain target display data.
8. The daily electricity management device as recited in claim 7 wherein the first acquisition module comprises:
the first calling module is used for calling real-time daily load data in the electricity consumption information acquisition system by utilizing a preset technical interface layer;
and the second calling module is used for calling the historical electricity consumption data in the marketing business system by utilizing a preset technical interface layer.
9. A solar power management system, wherein the management system comprises an application server cluster, an Ngnix server, a database server, a PC end device and a big data platform, at least one server in the application server cluster is connected with the Ngnix server, at least one server in the application server cluster is connected with the database server, the database server is connected with the big data platform, the PC end device is connected with at least one server in the application server cluster, and the management method according to any one of claims 1 to 6 is implemented when the servers in the application server cluster execute.
10. A computer-readable storage medium storing a computer program, characterized in that the computer program, when executed by a processor, implements the management method according to any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410083349.XA CN117689083A (en) | 2024-01-19 | 2024-01-19 | Method, device, system and medium for managing solar power |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410083349.XA CN117689083A (en) | 2024-01-19 | 2024-01-19 | Method, device, system and medium for managing solar power |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117689083A true CN117689083A (en) | 2024-03-12 |
Family
ID=90132227
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202410083349.XA Pending CN117689083A (en) | 2024-01-19 | 2024-01-19 | Method, device, system and medium for managing solar power |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117689083A (en) |
-
2024
- 2024-01-19 CN CN202410083349.XA patent/CN117689083A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106067080B (en) | Configurable workflow capabilities are provided | |
| CN112181960B (en) | Intelligent operation and maintenance framework system based on AIOps | |
| CN111240662A (en) | Spark machine learning system and learning method based on task visual dragging | |
| CN110168518A (en) | Prepare and arrange the user interface of the data for subsequent analysis | |
| CN104915793A (en) | Public information intelligent analysis platform based on big data analysis and mining | |
| CN112749194A (en) | Visualized data processing method and device, electronic equipment and readable storage medium | |
| US20140082013A1 (en) | Query templates for queries in data stream management systems | |
| CN106709012A (en) | Method and device for analyzing big data | |
| CN105243528A (en) | Financial IT system graphical centralized reconciliation system and method under big data environment | |
| CN113420009B (en) | Electromagnetic data analysis device, system and method based on big data | |
| CN114416855A (en) | Visualization platform and method based on electric power big data | |
| CN106202566A (en) | A kind of magnanimity electricity consumption data mixing based on big data storage system and method | |
| CN110442620A (en) | A kind of big data is explored and cognitive approach, device, equipment and computer storage medium | |
| CN111061733A (en) | Data processing method and device, electronic equipment and computer readable storage medium | |
| CN108345658A (en) | Algorithm calculates decomposing process, server and the storage medium of track | |
| CN114218218A (en) | Data processing method, device and equipment based on data warehouse and storage medium | |
| CN115564071A (en) | Method and system for generating data labels of power Internet of things equipment | |
| CN109871393A (en) | A kind of access method based on label system | |
| CN108694448A (en) | PHM platforms | |
| CN111340404A (en) | Method and device for constructing index system and computer storage medium | |
| CN113687825B (en) | Method, device, equipment and storage medium for constructing software module | |
| CN113642301A (en) | Report generation method, device and system | |
| Duan | Analysis of ERP enterprise management information system based on cloud computing mode | |
| CN109033196A (en) | A kind of distributed data scheduling system and method | |
| CN117689083A (en) | Method, device, system and medium for managing solar power |
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 |