A microservices-based SaaS platform and method for electricity market user management

Abstract

This application provides a method, apparatus, computer-readable medium, and electronic device for electricity market user management based on a microservices architecture. The method includes: acquiring user information based on a microservices architecture; cleaning the user information based on its corresponding data type to obtain cleaned data; determining user attributes based on the cleaned data; classifying users based on these attributes; determining the group type for each user; and generating electricity service strategies for each group type. This process closely aligns with actual user information, defining and classifying users through user attributes, and using this classification for electricity management, thereby improving the efficiency of electricity management and ensuring the sustainable development of electricity use.

Description

Technical Field

[0001] This application relates to the field of computer technology, and more specifically, to a method, apparatus, computer-readable medium, and electronic device for managing electricity market users based on a microservices architecture. Background Technology

[0002] With the development of power systems and residential electricity consumption, we need to implement scientific and effective management of the electricity market in practical applications. However, current electricity market management methods often fail to achieve rational allocation and management of electricity, leading to an imbalance between electricity load and demand, wasting power system resources, and affecting sustainable development. Therefore, there is an urgent need for a management method for electricity market users to avoid the problem of low electricity management efficiency. Summary of the Invention

[0003] Embodiments of this application provide a method, apparatus, computer-readable medium, and electronic device for electricity market user management based on a microservices architecture, which can at least partially solve the problem of low efficiency in electricity management.

[0004] Other features and advantages of this application will become apparent from the following detailed description, or may be learned in part from practice of this application.

[0005] According to one aspect of this application, a method for managing electricity market users based on a microservice architecture is provided, comprising: acquiring user information based on the microservice architecture, wherein the user information includes electricity consumption information, identity information, and location information; cleaning the user information based on the data type corresponding to the user information to obtain cleaned data; determining user attributes based on the cleaned data; classifying the users based on the user attributes to determine the group type corresponding to each user; and generating an electricity service strategy for the group type.

[0006] In this application, based on the aforementioned scheme, the step of obtaining user information based on a microservice architecture includes: obtaining the user's identity information and location information through user registration information in the microservice architecture; and obtaining the user's electricity consumption information within a preset period through a pre-set power sensor.

[0007] In this application, based on the aforementioned scheme, the step of cleaning the user information based on the data type corresponding to the user information to obtain cleaned data includes: detecting the data type corresponding to the user information; determining the cleaning parameters corresponding to each data type based on the data type corresponding to the user information; and cleaning the user information using the cleaning parameters to obtain cleaned data.

[0008] In this application, based on the aforementioned scheme, determining user attributes based on the cleaned data includes: determining the corresponding average parameter based on the cleaned data; and determining user attributes based on the average parameter.

[0009] In this application, based on the aforementioned scheme, after determining the user attributes based on the cleaned data, the method further includes: updating the user attributes according to the user information generated in real time.

[0010] In this application, based on the aforementioned scheme, after generating the power service strategy for the group type, the method further includes: sending the power service strategy to the management platform for testing.

[0011] In this application, based on the aforementioned scheme, after sending the power service policy to the management platform for testing, the method further includes: collecting user feedback information after the user applies the power service policy; and updating the power service policy based on the user feedback information.

[0012] According to one aspect of this application, a microservices-based SaaS platform for electricity market user management is provided, comprising:

[0013] The acquisition unit is used to acquire user information based on a microservice architecture, wherein the user information includes electricity consumption information, identity information, and location information;

[0014] The cleaning unit is used to clean the user information based on the data type corresponding to the user information to obtain cleaned data;

[0015] An attribute unit is used to determine user attributes based on the cleaning data;

[0016] A classification unit is used to classify users based on the user attributes and determine the group type corresponding to each user;

[0017] A strategy unit is used to generate power service strategies for the group type.

[0018] In this application, based on the aforementioned scheme, the step of obtaining user information based on a microservice architecture includes: obtaining the user's identity information and location information through user registration information in the microservice architecture; and obtaining the user's electricity consumption information within a preset period through a pre-set power sensor.

[0019] In this application, based on the aforementioned scheme, the step of cleaning the user information based on the data type corresponding to the user information to obtain cleaned data includes: detecting the data type corresponding to the user information; determining the cleaning parameters corresponding to each data type based on the data type corresponding to the user information; and cleaning the user information using the cleaning parameters to obtain cleaned data.

[0020] In this application, based on the aforementioned scheme, determining user attributes based on the cleaned data includes: determining the corresponding average parameter based on the cleaned data; and determining user attributes based on the average parameter.

[0021] In this application, based on the aforementioned scheme, after determining the user attributes based on the cleaned data, the method further includes: updating the user attributes according to the user information generated in real time.

[0022] In this application, based on the aforementioned scheme, after generating the power service strategy for the group type, the method further includes: sending the power service strategy to the management platform for testing.

[0023] In this application, based on the aforementioned scheme, after sending the power service policy to the management platform for testing, the method further includes: collecting user feedback information after the user applies the power service policy; and updating the power service policy based on the user feedback information.

[0024] According to one aspect of this application, a computer-readable medium is provided having a computer program stored thereon, which, when executed by a processor, implements a power market user management method based on a microservice architecture as described in the above embodiments.

[0025] According to one aspect of this application, an electronic device is provided, comprising: one or more processors; and a storage device for storing one or more programs, which, when executed by the one or more processors, cause the one or more processors to implement a microservices-based electricity market user management method as described in the above embodiments.

[0026] According to one aspect of this application, a computer program product or computer program is provided, comprising computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform a microservices-based electricity market user management method provided in the various alternative implementations described above.

[0027] In the technical solution of this application, user information is obtained based on a microservice architecture; the user information is cleaned according to the data type corresponding to the user information to obtain cleaned data; user attributes are determined based on the cleaned data, and users are classified according to the user attributes to determine the group type corresponding to each user, so as to generate power service strategies for the group type. The above process closely follows the actual information of users, realizes the definition and classification of users through user attributes, and uses this to carry out power management, thereby improving the efficiency of power management and ensuring the sustainable development of power use.

[0028] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description

[0029] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application. It is obvious that the drawings described below are merely some embodiments of this application, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort.

[0030] Figure 1-a The flowchart illustrating a microservices-based electricity market user management method according to one embodiment of this application is shown.

[0031] Figure 1-b A schematic diagram of a microservice architecture according to an embodiment of this application is shown.

[0032] Figure 2 A flowchart illustrating data cleaning according to one embodiment of this application is shown.

[0033] Figure 3 The illustration shows a schematic diagram of a microservices-based SaaS platform for electricity market user management according to an embodiment of this application.

[0034] Figure 4 A schematic diagram of the structure of a computer system suitable for implementing the electronic device of the present application is shown. Implementation

[0035] Exemplary embodiments will now be described more fully with reference to the accompanying drawings. However, these exemplary embodiments can be implemented in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided to make this application more comprehensive and complete, and to fully convey the concept of the exemplary embodiments to those skilled in the art.

[0036] Furthermore, the described features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. Numerous specific details are provided in the following description to give a thorough understanding of embodiments of this application. However, those skilled in the art will recognize that the technical solutions of this application can be practiced without one or more of the specific details, or other methods, components, apparatuses, steps, etc., can be employed. In other instances, well-known methods, apparatuses, implementations, or operations are not shown or described in detail to avoid obscuring various aspects of this application.

[0037] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities can be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0038] The flowcharts shown in the accompanying drawings are merely illustrative and do not necessarily include all content and operations / steps, nor do they necessarily have to be performed in the described order. For example, some operations / steps can be broken down, while others can be combined or partially combined; therefore, the actual execution order may change depending on the specific circumstances.

[0039] The implementation details of the technical solutions in the embodiments of this application are described in detail below:

[0040] Figure 1-a A flowchart illustrating a microservices-based electricity market user management method according to an embodiment of this application is shown. (Refer to...) Figure 1-a As shown, this method for managing electricity market users based on a microservice architecture includes at least steps S110 to S150, which are detailed below:

[0041] In step S110, user information is obtained based on a microservice architecture, wherein the user information includes electricity consumption information, identity information, and location information.

[0042] Among them, such as Figure 1-b The diagram illustrates a microservice architecture (only basic components are shown; business components and middleware components are not). To address the platform's business complexity and scalability, this embodiment selects a Spring Cloud microservice platform as the primary technical support platform, while also meeting the requirements of high availability and high scalability. The microservice platform includes the following main components:

[0043] (1) Service Registration Component: This component aggregates services scattered across various locations. The aggregated information may include the name, address, and quantity of the service provider. Each component has a listening device, and when the status of a service within the component changes, it reports this to the centralized component for status updates. The platform uses the Spring Cloud Eureka component to build a registration center. The registration center is an independent service and adopts a distributed deployment scheme to ensure high availability.

[0044] Service discovery component: When a service caller requests a service, it first obtains information about the components (IP, port, etc.) that can provide that service from the registry center. Then, it selects a provider of the service through a custom strategy to access it, thus invoking the service. This process is called service discovery, and the platform provides a client-side load balancing solution using Ribbon + EurekaClient to implement service discovery.

[0045] API Gateway: API Gateway is also a reverse proxy service developed based on Zuul. In addition, some custom attachment information has been added to support the operation of other components such as distributed tracing. At present, API Gateway only provides services to the intranet and adopts a 4-node cluster deployment to meet the millions of interface calls of the entire platform every day.

[0046] Configuration management component: An independent service built on Spring Cloud Config, which stores the configuration files of all services in a Git repository, and also has a copy of the Git repository on the local machine of the service. Even if the remote repository is inaccessible, it will not affect the normal operation of the configuration service.

[0047] Link tracing component: By collecting access logs from both internal and external Zuul gateways and combining them with AccessId for big data analysis, it generates the link of all requests, providing operations and maintenance personnel with the ability to quickly locate the problem.

[0048] Based on the above business architecture (the middleware components and business components are not shown) and the microservice platform, and taking into account factors such as system performance, reliability, compatibility, scalability, and security, services are divided according to the principle of high cohesion and low coupling to achieve independent operation of business.

[0049] In one embodiment of this application, user identity and location information are obtained through user registration information in a microservice architecture; and power consumption information of the user within a preset period is obtained through a pre-set power sensor. In this embodiment, user information includes power consumption information, identity information, and location information.

[0050] In this embodiment, Software as a Service (SaaS) enables users to connect and use the service via the Internet, and to manage electricity users through a cloud-based application.

[0051] In practical applications, user registration information, including user identity and location information, is pre-obtained through a microservice architecture. In this embodiment, microservice architecture is a technology for deploying applications and services in the cloud, which can run on its own and communicate with HTTP APIs through lightweight devices.

[0052] In this embodiment, a power sensor is pre-installed, allowing the user to obtain power consumption information within a preset period. This power consumption information may include the amount of electricity consumed and the duration of use within a specific time period.

[0053] In step S120, the user information is cleaned based on the data type corresponding to the user information to obtain cleaned data.

[0054] In one embodiment of this application, after obtaining user information, the data type corresponding to the user information is determined, and the user information is cleaned based on the data type to obtain cleaned data.

[0055] In one embodiment of this application, such as Figure 2 As shown, based on the data type corresponding to the user information, the user information is cleaned to obtain cleaned data, including:

[0056] S210, detect the data type corresponding to the user information;

[0057] S220, based on the data type corresponding to the user information, determine the cleaning parameters corresponding to each data type;

[0058] S230, The user information is cleaned using the cleaning parameters to obtain cleaned data.

[0059] In this embodiment, the data type corresponding to the user information is detected in advance. The data types include battery type, identity type, and location type. The data types in this embodiment can be represented by data identifiers.

[0060] After obtaining the data type corresponding to the user information, we determine the cleaning parameters for each data type. We calculate the data identifier by performing text matching between the data identifier and the parameter identifiers stored in the database. With the parameter identifier stored in the database Correlation coefficient between for:

[0061] in, Indicates the identification factor. This indicates the number of characters in the data identifier and parameter identifier. This represents the character number in the data identifier and parameter identifier. After calculating the correlation coefficient, the data identifier corresponding to the highest correlation coefficient is selected as the target identifier. This then determines the target identifier corresponding to the data identifier, and subsequently obtains the cleaning parameters corresponding to the target identifier.

[0062] In this embodiment, the cleaning parameters are used to represent the baseline data corresponding to each data identifier, and are used to calibrate the relevant data to obtain more accurate and reasonable data. After obtaining the cleaning parameters, the data is then processed using these parameters. User information Perform data cleaning to obtain cleaned data. :

[0063] {C}_{n}=γ\cdot {log}_{2}\left [ {{Cea}_{-}par\cdot {U}_{n}-{\left ( {\sum{^{m}_{n=1}{U}_{n}}} \right ) / m}} \right ]

[0064] in, This indicates the data number in the user information and cleaned data. This indicates the number of characters in the user information. This represents the cleaning factor. It should be noted that the above calculations are based on character operations on the quantified user information. The above process cleans the data using the cleaning parameters corresponding to this data type and incorporates the mean of the current user information, ensuring the reliability and accuracy of the data cleaning results.

[0065] In step S130, user attributes are determined based on the cleaning data.

[0066] In one embodiment of this application, after obtaining the cleaned data, we determine the corresponding average parameter based on the cleaned data, and then determine the user attributes based on the average parameter.

[0067] In this embodiment, after calculating the cleaning data, based on this set of cleaning parameters... Determine the corresponding average parameter :

[0068]

[0069] This embodiment pre-defines the threshold range of average parameters corresponding to user attributes. User attributes in this embodiment can include high-power-consuming users, ordinary-power-consuming users, etc.

[0070] After calculating the average parameter, a target range corresponding to the average parameter is determined based on a preset threshold range, and the attribute corresponding to this target range is taken as the user attribute. Furthermore, the user attributes corresponding to each user can be determined through the above method, and users belonging to the same user attribute are grouped into one group type for unified management.

[0071] In one embodiment of this application, after determining the user attributes based on the cleaned data, the method further includes: updating the user attributes according to the user information generated in real time.

[0072] In this embodiment, after the user attributes are determined, the user attributes can be re-determined based on the actual real-time user information generated in subsequent applications, thereby achieving real-time updates of the user attributes.

[0073] In step S140, the users are classified based on the user attributes to determine the group type corresponding to each user.

[0074] In one embodiment of this application, after determining user attributes, users with the same attributes are grouped into one category, and the group type corresponding to each user is determined, thus completing the user classification. This allows for unified management and maintenance of users within the same category in the future.

[0075] In step S150, a power service strategy is generated for the group type.

[0076] In one embodiment of this application, after determining the group type, a power service strategy is determined for the group type. The power service strategy is then sent to the management platform for testing.

[0077] In this embodiment, after generating the power service policy, it is sent to the management platform for testing. During testing, user feedback is collected after applying the power service policy. The power service policy is then updated based on this feedback, ensuring its reliability and usability.

[0078] In the technical solution of this application, user information is obtained based on a microservice architecture; the user information is cleaned according to the data type corresponding to the user information to obtain cleaned data; user attributes are determined based on the cleaned data, and users are classified according to the user attributes to determine the group type corresponding to each user, so as to generate power service strategies for the group type. The above process closely follows the actual information of users, realizes the definition and classification of users through user attributes, and uses this to carry out power management, thereby improving the efficiency of power management and ensuring the sustainable development of power use.

[0079] The following describes an embodiment of the apparatus described in this application, which can be used to execute a microservice-based electricity market user management method according to the above embodiments of this application. It is understood that the apparatus can be a computer program (including program code) running on a computer device, for example, the apparatus is application software; the apparatus can be used to execute the corresponding steps in the method provided in the embodiments of this application. For details not disclosed in the apparatus embodiments of this application, please refer to the above embodiments of a microservice-based electricity market user management method.

[0080] Figure 3 A block diagram of a microservices-based SaaS platform for electricity market user management according to an embodiment of this application is shown.

[0081] Reference Figure 3 As shown, a microservices-based electricity market user management SaaS platform according to an embodiment of this application includes:

[0082] The acquisition unit 310 is used to acquire user information based on a microservice architecture, wherein the user information includes electricity consumption information, identity information, and location information;

[0083] The cleaning unit 320 is used to clean the user information based on the data type corresponding to the user information to obtain cleaned data;

[0084] Attribute unit 330 is used to determine user attributes based on the cleaning data;

[0085] The classification unit 340 is used to classify the users based on the user attributes and determine the group type corresponding to each user;

[0086] Strategy unit 350 is used to generate power service strategies for the group type.

[0087] In this embodiment, Software as a Service (SaaS) enables users to connect and use the service via the Internet, and to manage electricity users through a cloud-based application.

[0088] In this application, based on the aforementioned scheme, the step of obtaining user information based on a microservice architecture includes: obtaining the user's identity information and location information through user registration information in the microservice architecture; and obtaining the user's electricity consumption information within a preset period through a pre-set power sensor.

[0089] In this application, based on the aforementioned scheme, the step of cleaning the user information based on the data type corresponding to the user information to obtain cleaned data includes: detecting the data type corresponding to the user information; determining the cleaning parameters corresponding to each data type based on the data type corresponding to the user information; and cleaning the user information using the cleaning parameters to obtain cleaned data.

[0090] In this application, based on the aforementioned scheme, determining user attributes based on the cleaned data includes: determining the corresponding average parameter based on the cleaned data; and determining user attributes based on the average parameter.

[0091] In this application, based on the aforementioned scheme, after determining the user attributes based on the cleaned data, the method further includes: updating the user attributes according to the user information generated in real time.

[0092] In this application, based on the aforementioned scheme, after generating the power service strategy for the group type, the method further includes: sending the power service strategy to the management platform for testing.

[0093] In this application, based on the aforementioned scheme, after sending the power service policy to the management platform for testing, the method further includes: collecting user feedback information after the user applies the power service policy; and updating the power service policy based on the user feedback information.

[0094] In the technical solution of this application, user information is obtained based on a microservice architecture; the user information is cleaned according to the data type corresponding to the user information to obtain cleaned data; user attributes are determined based on the cleaned data, and users are classified according to the user attributes to determine the group type corresponding to each user, so as to generate power service strategies for the group type. The above process closely follows the actual information of users, realizes the definition and classification of users through user attributes, and uses this to carry out power management, thereby improving the efficiency of power management and ensuring the sustainable development of power use.

[0095] Figure 4 A schematic diagram of the structure of a computer system suitable for implementing the electronic device of the present application is shown.

[0096] It should be noted that, Figure 4The computer system 400 of the electronic device shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of this application.

[0097] like Figure 4 As shown, the computer system 400 includes a Central Processing Unit (CPU) 401, which can perform various appropriate actions and processes based on programs stored in Read-Only Memory (ROM) 402 or programs loaded from storage portion 408 into Random Access Memory (RAM) 403, such as performing the methods described in the above embodiments. Various programs and data required for system operation are also stored in RAM 403. The CPU 401, ROM 402, and RAM 403 are interconnected via bus 404. An Input / Output (I / O) interface 405 is also connected to bus 404.

[0098] The following components are connected to I / O interface 405: an input section 406 including a keyboard, mouse, etc.; an output section 407 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 408 including a hard disk, etc.; and a communication section 409 including a network interface card such as a LAN (Local Area Network) card, modem, etc. The communication section 409 performs communication processing via a network such as the Internet. A drive 410 is also connected to I / O interface 405 as needed. A removable medium 411, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on drive 410 as needed so that computer programs read from it can be installed into storage section 408 as needed.

[0099] Specifically, according to embodiments of this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program including a computer program for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 409, and / or installed from removable medium 411. When the computer program is executed by central processing unit (CPU) 401, it performs various functions defined in the system of this application.

[0100] It should be noted that the computer-readable medium shown in the embodiments of this application can be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two. A computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), flash memory, optical fiber, portable compact disc read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this application, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this application, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying a computer-readable computer program. The transmitted data signal can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. The computer-readable signal medium can also be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The computer program contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to wireless, wired, etc., or any suitable combination thereof.

[0101] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. Each block in a flowchart or block diagram may represent a module, segment, or portion of code, which contains one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0102] The units described in the embodiments of this application can be implemented in software or hardware, and the described units can also be located in a processor. The names of these units do not necessarily limit the specific unit itself.

[0103] According to one aspect of this application, a computer program product or computer program is provided, comprising computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the methods provided in the various alternative implementations described above.

[0104] In another aspect, this application also provides a computer-readable medium, which may be included in the electronic device described in the above embodiments; or it may exist independently and not assembled into the electronic device. The computer-readable medium carries one or more programs, which, when executed by the electronic device, cause the electronic device to perform the methods described in the above embodiments.

[0105] It should be noted that although several modules or units for the device used to perform actions have been mentioned in the detailed description above, this division is not mandatory. In fact, according to the embodiments of this application, the features and functions of two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided and embodied by multiple modules or units.

[0106] Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solutions according to the embodiments of this application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, USB flash drive, external hard drive, etc.) or on a network, including several instructions to cause a computing device (such as a personal computer, server, touch terminal, or network device, etc.) to execute the methods according to the embodiments of this application.

[0107] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the embodiments disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein.

[0108] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. A method for managing electricity market users based on a microservice architecture, characterized in that, include: User information is obtained based on a microservice architecture, wherein the user information includes electricity consumption information, identity information, and location information; Based on the data type corresponding to the user information, the user information is cleaned to obtain cleaned data; User attributes are determined based on the cleaning data; The users are classified based on the user attributes to determine the group type corresponding to each user; Generate power service strategies for the aforementioned group types; Specifically, based on the data type corresponding to the user information, the user information is cleaned to obtain cleaned data, including: Detect the data type corresponding to the user information; Based on the data type corresponding to the user information, the cleaning parameters corresponding to each data type are determined; specifically, the data identifier representing the data type is matched with the parameter identifier stored in the database to calculate the data identifier. With the parameter identifier stored in the database Correlation coefficient between for: ; in, The identifier factor is represented by k, which represents the number of characters in the data identifier and parameter identifier, and i represents the character number in the data identifier and parameter identifier. Based on the correlation coefficient, the target identifier corresponding to the data identifier is obtained, and then the cleaning parameters corresponding to the target identifier are obtained; By the cleaning parameters User information Perform data cleaning to obtain cleaned data. for: ; Where n represents the data number in the user information and cleaned data, and m represents the number of characters in the user information. Indicates the cleaning factor; Determining user attributes based on the cleaning data includes: Based on cleaning data Determine the corresponding average parameter for: User attributes are determined based on the average parameters.

2. The method according to claim 1, characterized in that, Retrieving user information based on a microservice architecture includes: By using user registration information in the microservice architecture, we can obtain the user's identity and location information; The system obtains the user's electricity consumption information within a preset period using a pre-set power sensor.

3. The method according to claim 1, characterized in that, After determining user attributes based on the cleaning data, the process also includes: User attributes are updated based on real-time user information.

4. The method according to claim 1, characterized in that, After generating the power service strategy for the aforementioned group type, the following is also included: The power service strategy is sent to the management platform for testing.

5. The method according to claim 4, characterized in that, After sending the power service policy to the management platform for testing, the process also includes: Collect user feedback information after the user applies the described power service strategy; The power service strategy is updated based on the usage feedback information.

6. A power market user management SaaS platform based on a microservice architecture, characterized in that, include: The acquisition unit is used to acquire user information based on a microservice architecture, wherein the user information includes electricity consumption information, identity information, and location information; The cleaning unit is used to clean the user information based on the data type corresponding to the user information to obtain cleaned data; An attribute unit is used to determine user attributes based on the cleaning data; A classification unit is used to classify users based on the user attributes and determine the group type corresponding to each user; A strategy unit is used to generate power service strategies for the group type; Specifically, based on the data type corresponding to the user information, the user information is cleaned to obtain cleaned data, including: Detect the data type corresponding to the user information; Based on the data type corresponding to the user information, the cleaning parameters corresponding to each data type are determined; specifically, the data identifier representing the data type is matched with the parameter identifier stored in the database to calculate the data identifier. With the parameter identifier stored in the database Correlation coefficient between for: ;in, The identifier factor is represented by k, which represents the number of characters in the data identifier and parameter identifier, and i represents the character number in the data identifier and parameter identifier. Based on the correlation coefficient, the target identifier corresponding to the data identifier is obtained, and then the cleaning parameters corresponding to the target identifier are obtained; By the cleaning parameters User information Perform data cleaning to obtain cleaned data. for: Where n represents the data number in the user information and cleaned data, and m represents the number of characters in the user information. Indicates the cleaning factor; Determining user attributes based on the cleaning data includes: Based on cleaning data Determine the corresponding average parameter for: User attributes are determined based on the average parameters.

7. A computer-readable medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements a power market user management method based on a microservice architecture as described in any one of claims 1 to 5.

8. An electronic device, characterized in that, include: One or more processors; A storage device for storing one or more programs, which, when executed by one or more processors, cause the one or more processors to implement a power market user management method based on a microservice architecture as described in any one of claims 1 to 5.

Images