A power service data processing method, device and computer equipment

Abstract

Embodiments of the present disclosure provide a power service data processing method, device and computer equipment, comprising: dividing an external enterprise database into a first database and a second database; matching a first target field in the grid database with a second target field in the first database; determining power service data corresponding to the power enterprise name based on the matching result of the first target field and the second target field; and updating the power service data corresponding to the power enterprise name to the grid database. Thus, by dividing the external enterprise database and matching it with the power enterprise in the grid database, the data loss in the grid database is effectively supplemented by the external enterprise database, the authenticity and effectiveness of the data in the grid database are ensured, and the data management efficiency is improved.

Description

Technical Field

[0001] The embodiments of this disclosure relate to the field of data processing technology, and more specifically, to a method, apparatus, and computer equipment suitable for processing power service data. Background Technology

[0002] The power grid database stores service data from power companies in various provinces, providing them with electricity services. In practice, the service data from power companies is automatically filled in and recorded in the power grid database by the companies themselves when they first apply for electricity.

[0003] However, the service data of power companies is stored in the power grid database through direct reporting, and the data is not updated in a timely manner, which affects the validity of the data and makes the data management efficiency of the power grid database low. Summary of the Invention

[0004] The embodiments described herein provide a method, apparatus, and computer device for processing power service data, overcoming the aforementioned problems.

[0005] Firstly, based on the content of this disclosure, a method for processing electricity service data is provided, including:

[0006] The external enterprise database is divided into a first database and a second database. The first database is used to describe a provincial database, and the second database is used to describe other provincial databases that are not the stated provincial database.

[0007] The first target field in the power grid database is matched with the second target field in the first database. The first target field is used to describe the field containing the name of the power company included in the power grid database, and the second target field is used to describe the field containing the name of the power company included in the external enterprise database.

[0008] Based on the matching results of the first target field and the second target field, the power service data corresponding to the power company name is determined;

[0009] Update the power service data corresponding to the power company name to the power grid database.

[0010] Secondly, according to the present disclosure, an apparatus for processing electricity service data is provided, comprising:

[0011] The partitioning module is used to partition an external enterprise database into a first database and a second database. The first database is used to describe a provincial database, and the second database is used to describe other provincial databases that are not the stated provincial database.

[0012] The matching module is used to match a second target field in the power grid database with a first target field in the first target field, wherein the first target field is used to describe the field containing the names of power companies included in the power grid database, and the second target field is used to describe the field containing the names of power companies included in the external enterprise database.

[0013] The determination module is used to determine the power service data corresponding to the power company name based on the matching result of the first target field and the second target field;

[0014] The update module is used to update the power service data corresponding to the power company name to the power grid database.

[0015] Thirdly, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps of the power service data processing method as described in any of the above embodiments.

[0016] The power service data processing method provided in this application divides an external enterprise database into a first database and a second database. The first database describes a provincial database, and the second database describes other provincial databases. A first target field in the power grid database is matched with a second target field in the first database. The first target field describes the name of the power company included in the power grid database, and the second target field describes the name of the power company included in the external enterprise database. Based on the matching result of the first and second target fields, the power service data corresponding to the power company name is determined. The power service data corresponding to the power company name is then updated in the power grid database. In this way, by dividing the external enterprise database and then matching it with the power companies in the power grid database, the method effectively supplements the missing data in the power grid database using the external enterprise database, ensuring the authenticity and validity of the data in the power grid database and improving data management efficiency.

[0017] The above description is merely an overview of the technical solutions of the embodiments of this application. In order to better understand the technical means of the embodiments of this application and to implement them in accordance with the contents of the specification, and to make the above and other objects, features and advantages of the embodiments of this application more obvious and understandable, specific implementation methods of this application are described below. Attached Figure Description

[0018] To more clearly illustrate the technical solutions of the embodiments of this disclosure, the accompanying drawings of the embodiments will be briefly described below. It should be understood that the drawings described below only relate to some embodiments of this disclosure and are not intended to limit this disclosure, wherein:

[0019] Figure 1This is a flowchart illustrating a method for processing power service data provided in an embodiment of this disclosure;

[0020] Figure 2 This is a schematic diagram illustrating the flow of power service data provided in an embodiment of this disclosure;

[0021] Figure 3 This is a schematic diagram of the structure of a power service data processing device provided in an embodiment of this disclosure.

[0022] Figure 4 This is a schematic diagram of the structure of a computer device provided in an embodiment of this disclosure.

[0023] It should be noted that the elements in the attached diagram are schematic and not drawn to scale. Detailed Implementation

[0024] To make the objectives, technical solutions, and advantages of the embodiments of this disclosure clearer, the technical solutions of the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this disclosure. All other embodiments obtained by those skilled in the art based on the described embodiments of this disclosure without creative effort are also within the scope of protection of this disclosure.

[0025] Unless otherwise defined, all terms used herein (including technical and scientific terms) shall have the same meaning as commonly understood by one of ordinary skill in the art to which this subject matter pertains. It will be further understood that terms such as those defined in commonly used dictionaries shall be interpreted as having the meaning consistent with their meaning in the context of the specification and in the relevant art, and shall not be interpreted in an idealized or overly formal form unless otherwise explicitly defined herein. As used herein, the statement of “connecting” or “coupling” two or more parts together shall mean that these parts are directly joined together or joined through one or more intermediate components.

[0026] The term "embodiment" as used herein means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of the phrase "embodiment" in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0027] In this document, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A exists, A and B exist simultaneously, or B exists. Additionally, the character " / " generally indicates that the preceding and following related objects have an "or" relationship. Terms such as "first" and "second" are only used to distinguish one component (or part of a component) from another component (or another part of a component).

[0028] In the description of this application, unless otherwise stated, "multiple" means two or more (including two), and similarly, "multiple groups" means two or more (including two groups).

[0029] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings.

[0030] Figure 1 This is a flowchart illustrating a method for processing electricity service data provided in an embodiment of this disclosure, as shown below. Figure 1 As shown, the specific process of processing electricity service data includes:

[0031] S110. Divide the external enterprise database into the first database and the second database.

[0032] The external enterprise database can be a database of an organization that stores electricity service data, such as organization A. The first database can be used to describe a provincial database, for example, the first database can be the database of province B. The second database can be used to describe other provincial databases that are not provincial databases, for example, the second database can be a combination of databases from multiple provinces other than province B.

[0033] It should be noted that the provincial database mentioned above (such as the database of Province B) refers to the provincial database of the power grid that needs to be supplemented / updated.

[0034] In some embodiments, before matching a first target field in the power grid database with a second target field in the first database, where the first target field describes the name of the power company included in the power grid database, the method in this embodiment further includes: filtering out fields of corresponding document types in the power grid database, where document types include: business licenses; and matching the unified social credit code in the business licenses to update the power grid database.

[0035] Prior to the aforementioned filtering operation, external data can be imported into the shared layer of the power grid database middleware DWS layer based on its service-oriented architecture to synchronously extract power service data from the power company's data management model. For example... Figure 2As exemplarily shown, the corresponding power service data can be obtained from the external enterprise database 22 through the communication connection between the intranet management terminal 21 in the power grid data source and the external data source, and then used by the power grid database 23.

[0036] For example, by filtering the "document type (such as business license)" field in the power grid database, multiple power companies with "business licenses" can be obtained. Then, the "unified social credit code" in each power company is matched with the "unified social credit code" field in the target province (such as Province B). Thus, by performing data preprocessing on the data in the power grid database, the data regularity of the power grid database can be achieved.

[0037] In some embodiments, before matching a first target field in the power grid database with a second target field in the first database, where the first target field describes the name of the power company included in the power grid database, the method in this embodiment further includes:

[0038] Based on the format standards of external enterprise databases, the symbol format of the first target field in the power grid database is converted to obtain the first target field with the same standard format as the external enterprise database.

[0039] In the power grid database, the first target field is a field with a symbol identifier, which may include: dot identifier, bracket identifier, horizontal line identifier, etc.

[0040] Before performing symbol format conversion on the first target field in the power grid database, symbol recognition can be performed on all fields in the power grid database to identify the first target field with symbol identification.

[0041] When the symbol identifier of the first target field is a dot identifier, and the external enterprise database does not contain a dot identifier, the symbol format of the first target field in the power grid database is converted based on the format standard of the external enterprise database to obtain a first target field with the same standard format as the external enterprise database. This may include: deleting the dot identifier of the first target field in the power grid database based on the format standard of the external enterprise database to obtain a first target field with the same standard format as the external enterprise database.

[0042] When the symbol identifier of the first target field is a bracket identifier, and the external enterprise database does not contain bracket identifiers, the symbol format of the first target field in the power grid database is converted based on the format standard of the external enterprise database to obtain a first target field with the same standard format as the external enterprise database. This may include: deleting the bracket identifier of the first target field in the power grid database based on the format standard of the external enterprise database to obtain a first target field with the same standard format as the external enterprise database.

[0043] When the symbol identifier for the first target field is a hyphen, and the external enterprise database does not contain a hyphen identifier, the symbol format of the first target field in the power grid database is converted based on the format standard of the external enterprise database to obtain a first target field with the same standard format as the external enterprise database. This can include: deleting the hyphen identifier from the first target field in the power grid database based on the format standard of the external enterprise database to obtain a first target field with the same standard format as the external enterprise database. Thus, symbol standardization processing is performed on the first target field in the power grid database to unify the format standards of the power grid database and the external enterprise database, effectively enabling subsequent matching operations.

[0044] S120, Match the first target field in the power grid database with the second target field in the first database.

[0045] The first target field describes the names of power companies included in the power grid database, while the second target field describes the names of power companies included in the external enterprise database. Matching the power company names in the power grid database with the power company names in the first database (included in the external enterprise database) is possible.

[0046] It should be noted that in the process of field matching, matching can be based on field similarity, semantic similarity, etc., and this disclosure does not specifically limit the field matching principle.

[0047] S130. Based on the matching results of the first target field and the second target field, determine the power service data corresponding to the power company name.

[0048] S140. Update the power service data corresponding to the name of the power company to the power grid database.

[0049] Specifically, when the first target field and the second target field are matched based on the matching results of the first target field and the second target field, it can be determined that the first target field in the power grid database and the second target field in the first database are the same field. The power service data corresponding to "Power Company Name" is the same as the power service data corresponding to "Power Enterprise Name". The power service data corresponding to "Power Enterprise Name" in the power grid database is supplemented / updated based on the power service data corresponding to "Power Company Name" in the external enterprise database.

[0050] If, based on the matching results of the first target field and the second target field, it is determined that the first target field does not match the second target field, then the first target field can be matched with other target fields to obtain the external field that matches the field of the power company name.

[0051] In some embodiments, updating the power service data corresponding to the power company name to the power grid database includes: responding to a data query request for the power company name in the power grid database, displaying the current service data corresponding to the power company name; and updating the current service data corresponding to the power company name in the power grid database based on the write operation of the determined power service data corresponding to the power company name.

[0052] Specifically, after matching with external enterprise databases to determine the power service data corresponding to a power company name, the current service data corresponding to that "power company name" in the power grid database can be updated to compensate for missing data or update erroneous data. Thus, by writing the power service data corresponding to the determined power company name, the current service data corresponding to that power company name in the power grid database is updated, improving the data integrity of the power grid database.

[0053] It should be noted that the write operation based on the power service data corresponding to the determined power company name can be understood as performing automatic read / write / intelligent reading operations on the power service data corresponding to the determined power company name, thereby effectively improving the data update efficiency of the power grid database.

[0054] In this disclosure, an external enterprise database is divided into a first database and a second database. The first database describes a provincial database, and the second database describes other provincial databases. A first target field in the power grid database is matched with a second target field in the first database. The first target field describes the name of the power company included in the power grid database, and the second target field describes the name of the power company included in the external enterprise database. Based on the matching result of the first and second target fields, the power service data corresponding to the power company name is determined. The power service data corresponding to the power company name is then updated in the power grid database. Thus, by dividing the external enterprise database and matching it with the power companies in the power grid database, data gaps in the power grid database are effectively supplemented by the external enterprise database, ensuring the authenticity and validity of the data in the power grid database and improving data management efficiency.

[0055] In some embodiments, the external enterprise database is divided into a first database and a second database, including: assigning power companies in the external enterprise database that contain target province information to the first database, wherein the target province information corresponds to the province database and includes: the enterprise's registered address, actual business address, or the province identifier field corresponding to the enterprise's registered address; and assigning the remaining power companies in the power grid database to the second database.

[0056] For example, power companies in the external enterprise database that correspond to Province B are classified into the first database, while power companies in other provinces besides Province B are classified into the second database. This effectively distinguishes the provincial information in the external enterprise database that needs to be updated.

[0057] Specifically, the process involves classifying power companies in the external enterprise database that contain information about the target province into the first database. This includes comparing the registered addresses and / or actual business addresses of companies in the external enterprise database, classifying power companies whose registered addresses and actual business addresses contain the target keywords into the first database, where the target keywords include: target province, cities included in the target province, districts included in the city, or counties included in the district; and adding power companies that belong to the province identifier field to the first database, where the province identifier field is a non-Chinese field.

[0058] For example, power companies in the external enterprise database whose registered addresses and / or actual business addresses contain keywords related to the target province, the city included in the target province, the district included in the city, or the county included in the district are grouped into the first database. Among the remaining power companies in the external enterprise database, those whose registered address's province identifier field consists of the initials of the target province's name are added to the first database to create a first database containing the same province information from the external enterprise database.

[0059] It should be noted that the abbreviation of the target province's name can be in the form of uppercase letters, lowercase letters, or a combination of uppercase and lowercase letters.

[0060] In some embodiments, based on the matching results of the first target field and the second target field, the power service data corresponding to the power company name is determined, including:

[0061] If the field for the name of a power company in the power grid database does not match any of the fields for the names of all companies in the first database, then the field for the name of the power company is matched with the field for the former names of all companies in the first database. If the field for the name of the power company does not match any of the fields for the former names of companies, then the field for the name of the power company is matched with the fields for the names of power companies and the fields for the former names of companies contained in the second database. If the field for the name of the power company does not match any of the fields for the names of power companies or the fields for the former names of companies contained in the second database, then the power service data corresponding to the name of the power company is determined based on the fuzzy matching of the name of the power company.

[0062] Specifically, when the field of the power company name in the power grid database matches the field of any company name C in the first database, it can be determined that the power company name in the power grid database and the company name C in the first database belong to the same company. The power service data corresponding to company name C in the first database can then be added to / updated to the power company data corresponding to the power company name in the power grid database.

[0063] When the field of the power company name matches the field of any former name D of the company, it can be determined that the power company name in the power grid database and the former name D of the company in the first database belong to the same company. The power service data corresponding to the former name D of the company in the first database can be added / updated to the power company data corresponding to the power company name in the power grid database.

[0064] The field of the power company name is matched with the field of the power company name E / former name field F contained in the second database. When the field of the power company name matches the field of the power company name E contained in the second database, it can be determined that the power company name in the power grid database and the power company name E in the second database belong to the same company. The power service data corresponding to the power company name E in the second database can be added / updated to the power company data corresponding to the power company name in the power grid database.

[0065] When the field for the power company name matches the field for the former name of the company in the second database, it can be determined that the power company name in the power grid database and the former name of the company in the second database belong to the same company. The power service data corresponding to the former name of the company in the second database can then be added / updated to the power company data corresponding to the power company name in the power grid database. This effectively obtains the power service data corresponding to the power company name.

[0066] The process of determining the power service data corresponding to a power company name based on fuzzy matching of the power company name may include: performing fuzzy matching on the power company name to obtain multiple fuzzy matching companies; filtering the registration information of each fuzzy matching company to obtain the matching company corresponding to the power company name, wherein the registration information includes: registration address and / or industry; and determining the power service data corresponding to the matching company as the power service data corresponding to the power company name.

[0067] Fuzzy matching can be performed based on the text information of the power company name to obtain multiple fuzzy matching companies. The registered address and / or industry of each fuzzy matching company can be filtered to determine the power service data corresponding to the power company name.

[0068] When filtering by registered address and / or industry, each fuzzy match company can be filtered based on the target province / city included in the target province / district included in the city / county included in the district to obtain multiple filtered companies. Then, for each filtered company, the industry can be filtered based on the service industry corresponding to the power company name to obtain matching companies corresponding to the power company name, thereby enriching the power service data in the power grid database.

[0069] It should be noted that after filtering by industry based on the service sector corresponding to the name of the power company, each company can be further filtered by its establishment / registration date to obtain companies with a higher degree of matching with the name of the power company.

[0070] Figure 3 This is a schematic diagram of the structure of a power service data processing device provided in this embodiment. The power service data processing device may include: a division module 310, a matching module 320, a determination module 330, and an update module 340.

[0071] The partitioning module 310 is used to partition an external enterprise database into a first database and a second database. The first database is used to describe a provincial database, and the second database is used to describe other provincial databases that are not the stated provincial database.

[0072] The matching module 320 is used to match a second target field in the power grid database with a first target field in the power grid database. The first target field is used to describe the field containing the names of power companies included in the power grid database, and the second target field is used to describe the field containing the names of power companies included in the external enterprise database.

[0073] The determination module 330 is used to determine the power service data corresponding to the power company name based on the matching result of the first target field and the second target field.

[0074] The update module 340 is used to update the power service data corresponding to the name of the power company to the power grid database.

[0075] In this embodiment, optionally, the partitioning module 310 is specifically used for:

[0076] The power companies in the external enterprise database that contain information corresponding to the target province are assigned to the first database. The target province information corresponds to the province database and includes: the company's registered address, actual business address, or the province identifier field corresponding to the company's registered address. The remaining power companies in the power grid database are assigned to the second database.

[0077] In this embodiment, optionally, the partitioning module 310 is specifically used for:

[0078] By comparing the registered addresses and / or actual business addresses of the enterprises in the external enterprise database, the power companies corresponding to the registered addresses and actual business addresses containing the target keywords are assigned to the first database. The target keywords include: target province, city included in the target province, district included in the city, or county included in the district. Power companies belonging to the province identifier field are added to the first database. The province identifier field is a non-Chinese field.

[0079] In this embodiment, optionally, the determining module 330 is specifically used for:

[0080] When the field of the power company name in the power grid database does not match any of the fields of all company names in the first database, the field of the power company name is matched with the fields of all former company names in the first database; when the field of the power company name does not match any of the fields of all former company names, the field of the power company name is matched with the fields of the power company names and former company names contained in the second database; when the field of the power company name does not match any of the fields of the power company names or former company names contained in the second database, the power service data corresponding to the power company name is determined based on the fuzzy matching of the power company name.

[0081] In this embodiment, optionally, the determining module 330 is specifically used for:

[0082] Fuzzy matching is performed on the name of the power company to obtain multiple fuzzy matching companies; registration information is filtered for each fuzzy matching company to obtain the matching company corresponding to the name of the power company, wherein the registration information includes: registration address and / or industry; the power service data corresponding to the matching company is determined to be the power service data corresponding to the name of the power company.

[0083] In this embodiment, optionally, a conversion module is also included.

[0084] The conversion module is used to perform symbol format conversion on the first target field in the power grid database based on the format standard of the external enterprise database, so as to obtain the first target field with the same standard format as the external enterprise database.

[0085] In this embodiment, optionally, a filtering module is also included.

[0086] The filtering module is used to filter out fields of corresponding document types in the power grid database, including: business license;

[0087] The matching module 320 is also used to match the unified social credit code in the business license in order to update the power grid database.

[0088] In this embodiment, optionally, the update module 340 is specifically used for:

[0089] In response to a data query request for the name of the power company in the power grid database, the current service data corresponding to the name of the power company is displayed; based on the write operation of the power service data corresponding to the determined name of the power company, the current service data corresponding to the name of the power company in the power grid database is updated.

[0090] The power service data processing apparatus provided in this disclosure can execute the above-described method embodiments. For its specific implementation principle and technical effects, please refer to the above-described method embodiments. It will not be repeated here.

[0091] This application also provides a computer device. Please refer to the following for details. Figure 4 , Figure 4 This is a basic structural block diagram of the computer device in this embodiment.

[0092] The computer device includes a memory 410 and a processor 420 that are interconnected via a system bus. It should be noted that only a computer device with components 410-420 is shown in the figure; however, it should be understood that it is not required to implement all the shown components, and more or fewer components may be implemented alternatively. Those skilled in the art will understand that the computer device described herein is a device capable of automatically performing numerical calculations and / or information processing according to pre-set or stored instructions, and its hardware includes, but is not limited to, microprocessors, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), digital signal processors (DSPs), embedded devices, etc.

[0093] Computer devices can include desktop computers, laptops, handheld computers, and cloud servers. These devices allow for human-computer interaction with users through keyboards, mice, remote controls, touchpads, or voice-activated devices.

[0094] The memory 410 includes at least one type of readable storage medium, which includes non-volatile memory or volatile memory, such as flash memory, hard disk, multimedia card, card-type memory (e.g., SD or DX memory), random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, magnetic disk, optical disk, etc. RAM may include static RAM or dynamic RAM. In some embodiments, the memory 410 may be an internal storage unit of a computer device, such as the hard disk or RAM of the computer device. In other embodiments, the memory 410 may also be an external storage device of the computer device, such as a plug-in hard drive, SmartMediaCard (SMC), SecureDigital (SD) card, or FlashCard. Of course, the memory 410 may include both internal and external storage units of the computer device. In this embodiment, the memory 410 is typically used to store the operating system and various application software installed on the computer device, such as the program code of the methods described above. Furthermore, the memory 410 can also be used to temporarily store various types of data that have been output or will be output.

[0095] Processor 420 is typically used to perform overall operations of a computer device. In this embodiment, memory 410 is used to store program code or instructions, including computer operation instructions, and processor 420 is used to execute the program code or instructions stored in memory 410 or process data, such as program code that runs the methods described above.

[0096] In this article, the bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. This bus system can be divided into address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used to represent it in the diagram, but this does not indicate that there is only one bus or one type of bus.

[0097] Another embodiment of this application also provides a computer-readable medium, which may be a computer-readable signal medium or a computer-readable medium. A processor in a computer reads computer-readable program code stored in the computer-readable medium, enabling the processor to execute the functional actions specified in each step or combination of steps in the above method; and to generate means for implementing the functional actions specified in each block or combination of blocks in the block diagram.

[0098] Computer-readable media include, but are not limited to, electronic, magnetic, optical, electromagnetic, infrared memory or semiconductor systems, devices or apparatuses, or any suitable combination thereof, wherein the memory is used to store program code or instructions, the program code including computer operation instructions, and the processor is used to execute the program code or instructions of the above-described methods stored in the memory.

[0099] The definitions of memory and processor can be found in the description of the foregoing computer device embodiments, and will not be repeated here.

[0100] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0101] In the various embodiments of this application, the functional units or modules can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0102] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0103] In the claims, any reference signs placed between parentheses should not be construed as limiting the claims. The word "comprising" as described in this application does not exclude the presence of elements or steps not listed in the claims. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. This application can be implemented by means of hardware comprising several different elements and by means of a suitably programmed computer. In the unit claims listing several means, several units of these means may be embodied by the same item of hardware. The use of "first," "second," and "third," etc., does not indicate any order and these words should be interpreted as names. Unless otherwise specified, the steps in the above embodiments should not be construed as limiting the order of execution.

[0104] The above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A method of processing electric service data, characterized by, The method comprises the following steps: dividing an external enterprise database into a first database and a second database, the first database being used to describe a province database, and the second database being used to describe other province databases other than the province database; matching a second target field in the first database based on a first target field in a power grid database, the first target field being used to describe a field of power enterprise names included in the power grid database, and the second target field being used to describe a field of power company names included in the external enterprise database; determining power service data corresponding to the power enterprise names based on a matching result of the first target field and the second target field; updating the power service data corresponding to the power enterprise names into the power grid database; wherein the step of dividing the external enterprise database into the first database and the second database comprises: dividing power enterprises with target province information corresponding to the target province information into the first database, the target province information corresponding to the province database, and the target province information including an enterprise registration address, an actual business address, or a province identifier field corresponding to the enterprise registration address; and dividing the remaining other power enterprises in the power grid database into the second database; the step of determining the power service data corresponding to the power enterprise names based on the matching result of the first target field and the second target field comprises: when the field of the power enterprise names in the power grid database does not match the field of all enterprise company names in the first database, matching the field of the power enterprise names with the field of all enterprise former names in the first database; when the field of the power enterprise names does not match the field of all enterprise former names, matching the field of the power enterprise names with the field of power company names and the field of enterprise former names included in the second database; when the field of the power enterprise names does not match the field of power company names or the field of enterprise former names included in the second database, determining the power service data corresponding to the power enterprise names based on fuzzy matching of the power enterprise names.

2. The method of claim 1, wherein, the step of dividing the power enterprises with the target province information corresponding to the target province information in the external enterprise database into the first database comprises: comparing the enterprise registration address and / or the actual business address in the external enterprise database, and dividing the power enterprises with the target key words in the enterprise registration address and the actual business address into the first database, the target key words including a target province, a city included in the target province, a district included in the city, or a county included in the district; adding the power enterprises belonging to the province identifier field corresponding to the power enterprises to the first database, the province identifier field being a non-Chinese field.

3. The method of claim 1, wherein, the step of determining the power service data corresponding to the power enterprise names based on the fuzzy matching of the power enterprise names comprises: performing fuzzy matching on the power enterprise names to obtain a plurality of fuzzy matching enterprises; The registration information includes a registered address and / or an industry to which the registration information belongs. The power service data corresponding to the matched enterprise is determined as the power service data corresponding to the power enterprise name.

4. The method of claim 1, wherein, The method further includes: The first target field in the power grid database is subjected to symbol format conversion based on a format standard of the external enterprise database, so as to obtain a first target field in the same standard format as the external enterprise database.

5. The method of claim 1, wherein, The method further includes: The fields of the corresponding certificate types in the power grid database are screened out, and the certificate types include a business license. The unified social credit code in the business license is matched to update the power grid database.

6. The method of claim 1, wherein, The method further includes: In response to a data query request of the power enterprise name in the power grid database, current service data corresponding to the power enterprise name is displayed. Based on the write operation of the power service data corresponding to the power enterprise name, the current service data corresponding to the power enterprise name in the power grid database is updated.

7. An apparatus for processing electric service data, characterized by comprising: The method further includes: The external enterprise database is divided into a first database and a second database, the first database is used to describe a province database, and the second database is used to describe other province databases other than the province database. The first target field in the power grid database is matched with the second target field in the first database, the first target field is used to describe a field of a power enterprise name included in the power grid database, and the second target field is used to describe a field of a power company name included in the external enterprise database. Based on the matching result of the first target field and the second target field, the power service data corresponding to the power enterprise name is determined. The power service data corresponding to the power enterprise name is updated into the power grid database. The division module is specifically configured to: The power enterprises in the external enterprise database that contain target province information corresponding to the power enterprise name are divided into the first database, the target province information corresponds to the province database, and the target province information includes an enterprise registered address, an actual business address, or a province identifier field corresponding to the enterprise registered address. The determination module is specifically configured to: When the field of the power enterprise name in the power grid database does not match the field of all enterprise company names in the first database, the field of the power enterprise name is matched with the field of all enterprise former names in the first database; when the field of the power enterprise name does not match all the fields of the enterprise former names, the field of the power enterprise name is matched with the field of the power company name and the field of the enterprise former name contained in the second database; when the field of the power enterprise name does not match the field of the power company name or the field of the enterprise former name contained in the second database, the power service data corresponding to the power enterprise name is determined based on fuzzy matching of the power enterprise name.

8. A computer device, comprising: The power service data processing method comprises a memory and a processor, the memory stores a computer program, and the processor executes the computer program to realize the steps of the power service data processing method according to any one of claims 1 to 6.

Images