Power business data tracing method, system, equipment and medium
By using horizontal and vertical pointers to update the entity association network in the power metering system, the problem of insufficient traceability of power business data has been solved, and accurate traceability and data management throughout the entire life cycle have been achieved.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- GUANGDONG POWER GRID CO LTD
- Filing Date
- 2025-12-10
- Publication Date
- 2026-04-10
AI Technical Summary
Existing technologies lack records of the dynamic binding relationships between entities in the power metering system, resulting in poor accuracy when tracing power business data and an inability to fully restore historical states.
By updating the historical evolution chain and multi-dimensional entity association network in the same data structure using horizontal and vertical pointers, the entity association relationships at the target historical moment can be reconstructed, enabling accurate traceability of power business data.
Ensure full lifecycle management of power business data, achieve accurate traceability from single entities to multi-dimensional relationships, avoid logical gaps in the reconstruction of historical states, and provide reliable data support.
Smart Images
Figure CN121836088A_ABST
Abstract
Description
Technical Field
[0001] This invention application relates to the field of power grid data management, and in particular to a method, system, device and medium for tracing power business data. Background Technology
[0002] With the accelerated construction of new power systems, power grid data management faces unprecedented complexity adjustments. The power metering system has evolved from a traditional single-meter management model to a complex network structure encompassing multiple levels and dimensions, including user entities, metering points, energy meters, transformers, and data acquisition terminals. Against this backdrop, the time-series and correlation characteristics of power archive data are becoming increasingly prominent, placing higher demands on data traceability capabilities.
[0003] With increasingly stringent requirements for data traceability, the core of the electricity metering system lies in establishing dynamic, inter-entity relationships. However, current technologies lack the ability to dynamically bind relationships between entities. The core feature of the electricity metering system is the formation of a dynamically bound "chain of responsibility" between entities. When business operations occur and business data is changed, the existing technology lacks the record of the relationship between entities and the evolution process (only the state data at the last moment is recorded). This results in relatively coarse and inaccurate data when tracing back the data. Summary of the Invention
[0004] This invention application provides a method, system, device, and medium for tracing power business data, in order to solve the technical problem of how to improve the accuracy of tracing results for power business data.
[0005] To address the aforementioned technical problems, this invention provides a method for tracing power business data, comprising: In response to a business operation request, the business operation request is parsed to obtain status change information; Based on the state change information, the historical evolution chain of the corresponding entity is updated by the horizontal pointer, and the preset multidimensional entity association network is updated by the vertical pointer to obtain the target association network; wherein, the horizontal pointer and the vertical pointer are pre-configured in the same data structure; In response to a tracing request for target power business data, the historical state changes of the entity are obtained through an updated historical evolution chain; based on the target association network, the entity association relationship at the target historical moment is reconstructed, thereby realizing the tracing of the target power business data.
[0006] As a preferred embodiment, before updating the preset multidimensional entity association network via vertical pointers, the method further includes: Construct the multidimensional entity association network with measurement points as the core; The dimensions of each entity defined in the multidimensional entity association network include time dimension, spatial dimension and state dimension; The time dimension includes creation time, activation time, modification time, and deactivation time; the spatial dimension includes sibling entity relationships and hierarchical entity relationships; the state dimension includes current state, historical state, and expected state.
[0007] As a preferred embodiment, parsing the business operation request to obtain status change information includes: The business operation request is parsed to obtain the business fields; The status change information is obtained by comparing the business fields with the historical fields.
[0008] As a preferred embodiment, parsing the business operation request to obtain business fields includes: Semantic extraction is performed on the business operation request to obtain the corresponding key parameters, relationship parameters, and configuration parameters; wherein, the key parameters include the transformation ratio, accuracy level, and verification period, the relationship parameters include the bound metering point identifier and the associated user identifier, and the configuration parameters include the installation location and communication parameters; Based on the key parameters, relationship parameters, and configuration parameters, the fields are extracted to obtain the business fields.
[0009] As a preferred embodiment, before updating the historical evolution chain of the corresponding entity via the horizontal pointer, the method further includes: The data source of the business operation request is verified to determine whether the data source has the necessary operation permissions. When it is determined that the user has the operation permission, the identity of the user who issued the business operation request is determined, and the user identity is compared with a preset permission matrix table; When a user's identity is in the preset permission matrix table, the user's identity is verified to determine whether the corresponding user has the permission to modify the entity corresponding to the business operation request and its associated entities; When it is determined that the user has the authority to modify the entity corresponding to the business operation request and its associated entities, the business operation request is verified using power business rules.
[0010] As a preferred embodiment, the step of responding to a traceability request for target power business data by tracing the historical state changes of the entity through an updated historical evolution chain includes: In response to a traceability request for target power business data, obtain the traceability time range; Based on the aforementioned time interval, the updated historical evolution chain is traversed to identify multiple key change points. An index is established based on the multiple key change time points to obtain the historical state changes of the entity.
[0011] As a preferred embodiment, before updating the historical evolution chain of the corresponding entity via the horizontal pointer, the method further includes: An operation identifier corresponding to the business operation request is generated by a preset transaction coordinator; wherein the operation identifier records the operation type code, timestamp, and sequence number.
[0012] Accordingly, this invention application also provides a power business data traceability system, including a parsing module, an updating module, and a traceability module; wherein, The parsing module is used to respond to a business operation request, parse the business operation request, and obtain status change information. The update module is used to update the historical evolution chain of the corresponding entity through horizontal pointers and update the preset multi-dimensional entity association network through vertical pointers based on the state change information to obtain the target association network; wherein, the horizontal pointers and the vertical pointers are pre-configured in the same data structure; The tracing module is used to respond to the tracing request of the target power business data, and to obtain the historical state changes of the entity through the updated historical evolution chain; based on the target association network, to reconstruct the entity association relationship at the target historical moment, thereby realizing the tracing of the target power business data.
[0013] As a preferred embodiment, the traceability system further includes a network construction module, which is used before updating the preset multidimensional entity association network via vertical pointers: Construct the multidimensional entity association network with measurement points as the core; The dimensions of each entity defined in the multidimensional entity association network include time dimension, spatial dimension and state dimension; The time dimension includes creation time, activation time, modification time, and deactivation time; the spatial dimension includes sibling entity relationships and hierarchical entity relationships; the state dimension includes current state, historical state, and expected state.
[0014] As a preferred embodiment, the parsing module parses the business operation request to obtain status change information, including: The parsing module parses the business operation request to obtain the business fields; The status change information is obtained by comparing the business fields with the historical fields.
[0015] As a preferred embodiment, the parsing module parses the business operation request to obtain business fields, including: The parsing module performs semantic extraction on the business operation request to obtain the corresponding key parameters, relationship parameters, and configuration parameters; wherein, the key parameters include the transformation ratio, accuracy level, and verification period, the relationship parameters include the bound metering point identifier and the associated user identifier, and the configuration parameters include the installation location and communication parameters; Based on the key parameters, relationship parameters, and configuration parameters, the fields are extracted to obtain the business fields.
[0016] As a preferred embodiment, before updating the historical evolution chain of the corresponding entity via the horizontal pointer, the method further includes: The data source of the business operation request is verified to determine whether the data source has the necessary operation permissions. When it is determined that the user has the operation permission, the identity of the user who issued the business operation request is determined, and the user identity is compared with a preset permission matrix table; When a user's identity is in the preset permission matrix table, the user's identity is verified to determine whether the corresponding user has the permission to modify the entity corresponding to the business operation request and its associated entities; When it is determined that the user has the authority to modify the entity corresponding to the business operation request and its associated entities, the business operation request is verified using power business rules.
[0017] As a preferred embodiment, the step of responding to a traceability request for target power business data by tracing the historical state changes of the entity through an updated historical evolution chain includes: In response to a traceability request for target power business data, obtain the traceability time range; Based on the aforementioned time interval, the updated historical evolution chain is traversed to identify multiple key change points. An index is established based on the multiple key change time points to obtain the historical state changes of the entity.
[0018] As a preferred embodiment, before updating the historical evolution chain of the corresponding entity via the horizontal pointer, the method further includes: An operation identifier corresponding to the business operation request is generated by a preset transaction coordinator; wherein the operation identifier records the operation type code, timestamp, and sequence number.
[0019] Accordingly, this application also provides a terminal device, including a processor, a memory, and a computer program stored in the memory and configured to be executed by the processor, wherein the processor executes the computer program to implement the power business data traceability method.
[0020] Accordingly, this application also provides a computer-readable storage medium, the computer-readable storage medium including a stored computer program, wherein, when the computer program is executed, it controls the device where the computer-readable storage medium is located to execute the power business data tracing method.
[0021] Compared with the prior art, this invention application has the following beneficial effects: This invention provides a method, system, device, and medium for tracing power business data. The tracing method includes: responding to a business operation request, parsing the business operation request to obtain state change information; based on the state change information, updating the historical evolution chain of the corresponding entity through a horizontal pointer, and updating a preset multi-dimensional entity association network through a vertical pointer to obtain a target association network; wherein the horizontal pointer and the vertical pointer are pre-configured in the same data structure; responding to a tracing request for target power business data, tracing the historical state changes of the entity through the updated historical evolution chain; and reconstructing the entity association relationship at the target historical moment based on the target association network, thereby realizing the tracing of the target power business data. Existing technologies lack a correlation mechanism when modifying power business data, resulting in the limitation of "single entity" data. This invention addresses this issue by updating the historical evolution chain and the preset multi-dimensional entity association network using horizontal and vertical pointers within the same data structure during modification. This ensures the complete restoration of the association state at any historical moment during tracing. Furthermore, this technical concept, by covering modification and tracing, guarantees data management throughout the entire lifecycle of power business scenarios, enabling precise tracing of power metering ledgers from single entities to multi-dimensional relationships, and from the current state to any historical node. This provides reliable data support for metering dispute resolution and anomaly analysis. Further, the vertical pointer is used to update the multi-dimensional entity association network (e.g., updating the business relationships of multiple entities), while the horizontal pointer synchronously records the historical evolution chain of entities (e.g., changes in the entity's own time sequence). This unifies the time dimension and the spatial dimension (entity association). When a modification occurs based on a business operation request, the modification trajectory of each entity can be accurately linked through the horizontal and vertical pointers, avoiding logical gaps in historical state reconstruction caused by scattered modification records and ensuring spatiotemporal consistency during tracing. Attached Figure Description
[0022] Figure 1 This is a flowchart illustrating an embodiment of the power business data tracing method provided in this application.
[0023] Figure 2 This is a schematic diagram of an embodiment of the power business data traceability system provided in this application. Detailed Implementation
[0024] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.
[0025] Example 1 Please refer to Figure 1 , Figure 1 The present invention provides a method for tracing power business data, comprising steps S101 to S103; wherein each step is described in detail below: Step S101: In response to the business operation request, the business operation request is parsed to obtain status change information.
[0026] In this embodiment, the method for tracing power business data can be applied to computer devices, including but not limited to smartphones, laptops, tablets, desktop computers, as well as physical servers and cloud servers connected to display units.
[0027] The aforementioned display unit can be used to display the results of power business data tracing.
[0028] Users can externally input the above-mentioned business operation request, which is used to operate on at least one target entity (such as replacing an electricity meter). In some specific application scenarios, when operating on the target entity, the change in the state of the target entity may also involve adjustments to the states of some related entities.
[0029] Before step S102, an operation identifier corresponding to the business operation request can be generated by a preset transaction coordinator; wherein, the operation identifier records the operation type code, timestamp, and sequence number. This operation identifier allows tracing a unique path corresponding to the business operation.
[0030] In some examples, the operation identifier can be represented as OP_ID=[operation type code][timestamp][serial number], where, Operation type codes can be two characters, such as "UC" for update / change and "QT" for traceability / query. The timestamps mentioned above can be represented by 17 characters (e.g., year, month, day, hour, minute, second, millisecond, microsecond), and the sequence number can be a four-digit sequential number used to process multiple requests within the same microsecond.
[0031] Before step S102, operations such as operation source verification, operation identity verification, entity permission matching, business rule verification, and operation log recording can be performed sequentially. For example, the data source of the business operation request is verified to determine whether the data source has operation permissions; if operation permissions are determined, the identity of the user issuing the business operation request is determined, and the user identity is compared with a preset permission matrix table; if the user identity is in the preset permission matrix table, the user identity is verified to determine whether the corresponding user has permission to modify the entity corresponding to the business operation request and its associated entities; if it is determined that the user has permission to modify the entity corresponding to the business operation request and its associated entities, the business operation request is verified according to power business rules (e.g., meter replacement requires the corresponding metering point status to be "pending replacement"). Regardless of whether the result of any of the above types of verification, validation, or inspection is successful or not, the complete verification, validation, or inspection process and result can be recorded.
[0032] In some preferred embodiments, parsing the business operation request to obtain status change information includes: parsing the business operation request to obtain business fields; and comparing the business fields with historical fields to obtain the status change information.
[0033] The method for obtaining the business fields specifically involves: employing a multi-level difference detection algorithm to perform semantic extraction on the business operation request, thereby obtaining corresponding key parameters, relationship parameters, and configuration parameters; wherein, the key parameters include the ratio, accuracy level, and verification period; the relationship parameters include the bound metering point identifier and the associated user identifier; and the configuration parameters include the installation location and communication parameters; and based on the key parameters, relationship parameters, and configuration parameters, field extraction is performed to obtain the business fields.
[0034] For example, key parameters (groups) can be represented as ["ratio", "accuracy level", "verification cycle"], relationship parameters (groups) can be represented as ["binding metering point ID", "associated user ID"], and configuration parameters (groups) can be represented as ["installation location", "communication parameters"].
[0035] Based on the above, the fields are categorized into key parameters, relational parameters, and configuration parameters according to the characteristics of the power business. Differentiated and targeted processing strategies can be adopted for each group. In some application scenarios, the business impact level of changes to key parameters can be automatically assessed, providing a basis for subsequent risk control.
[0036] In addition, in some other preferred embodiments, the above-mentioned field comparison can be used to obtain the state before the change and the new state after the change, thereby obtaining the above-mentioned state change information, generating a change difference set containing three operation types: ADD, DELETE and UPDATE, and storing the change difference set instead of the complete record in historical data for retrieval at any time.
[0037] Step S102: Based on the state change information, update the historical evolution chain of the corresponding entity through the horizontal pointer and update the preset multi-dimensional entity association network through the vertical pointer to obtain the target association network.
[0038] In this step, the horizontal pointer and the vertical pointer are pre-configured in the same data structure.
[0039] In some preferred embodiments, the data structure described above may include a head node, data blocks, and a tail node. The data block may include a data header, change subject, change differences, and change proof. The data header may include the corresponding change ID, timestamp, forward pointer, and operation type.
[0040] Preferably, before updating the preset multidimensional entity association network via vertical pointers, the method further includes: Construct a multi-dimensional entity association network with measurement points as the core; wherein, the dimensions of each entity defined in the multi-dimensional entity association network include time dimension, spatial dimension and state dimension; the time dimension includes creation time, activation time, change time and deactivation time; the spatial dimension includes sibling entity association relationship and superior-subordinate entity association relationship; the state dimension includes current state, historical state and expected state.
[0041] For example, the aforementioned peer-to-peer entity relationships can refer to adjacent metering points, and the entities can be users, metering points, electricity meters, etc. The aforementioned hierarchical entity relationships can be the relationship between users and metering points, or the relationship between transformer substations and metering points, or the relationship between metering points and electricity meters, current transformers, and terminals.
[0042] When updating this multidimensional entity association network, each entity relationship record can include information such as relationship identifier (uniquely identifying a pair of entity relationships), subject entity identifier (corresponding to the relationship initiator), object entity identifier (corresponding to the relationship receiver), relationship type (such as 1-to-1, 1-to-many, many-to-many), effective time (relationship start time), termination time (relationship end time), and operation context (operation information for creating / modifying the relationship).
[0043] In some preferred embodiments, when using this multidimensional entity association network for data writing, business change requests or business operation requests can be decomposed into multiple atomic relationship changes, thereby achieving parallel processing; furthermore, a precise time point is determined for each atomic relationship change, and relationship records are added or updated in the spatiotemporal association matrix, and a relationship chain is constructed through the preceding relationship identifier and the following relationship identifier.
[0044] For example, when the electricity meter is replaced, the original "metering point-meter A" relationship is marked with the termination time, and the new "metering point-meter B" relationship is recorded with the effective time. In this way, the two relationships can be associated through operation_id, indicating that they are two aspects of the same business operation request.
[0045] The aforementioned multidimensional entity association network can be used to maintain transaction tables, entity tables, and relationship tables, as well as the correspondence between these three tables. For example, terminals, electricity meters, and terminal-electricity-meter relationships are associated with relationship tables. Transaction tables represent information such as users, terminals, electricity meters, other entities, operators, time, and hash chains. The atomic relationships mentioned above mean that there are no primary or foreign key relationships between transaction tables, entity tables, and relationship tables, thus transactions generated by parallel updates to multiple tables are atomic. For some business operation requests, such as changes to electricity meters, a series of entity changes will inevitably be triggered. Power terminal equipment is not an isolated entity; state changes are either maintained through relationship tables or by maintaining upstream and downstream identifiers through their respective entity tables.
[0046] This implementation uses a multi-dimensional entity association network to solve the problem of traditional methods being unable to express dynamic binding relationships. Through time anchors and relationship chains, it ensures that the complete responsibility chain between entities can be accurately reconstructed at any point in time, supporting precise temporal traceability. Compared with existing technologies, this model does not rely on static foreign keys, but dynamically maintains relationships through time and spatial dimensions, which is more in line with the actual business characteristics of power archives.
[0047] Step S103: In response to the traceability request of the target power business data, the historical state changes of the entity are obtained by tracing through the updated historical evolution chain; based on the target association network, the entity association relationship at the target historical moment is reconstructed, thereby realizing the traceability of the target power business data.
[0048] In this step, the aforementioned traceability request can be input from outside the user. For the target power business data, the historical state changes of the corresponding entity can be traced through the updated historical evolution chain. Through the target association network, the entity association relationship at the target historical moment or interval can be reconstructed, thereby achieving fine-grained traceability.
[0049] When tracing in step S103, parallel processing can be used to filter the flow of the target time interval; at the same time, hash verification can be used to prevent tampering, and backward index completion can be used to associate new and old entities.
[0050] In some preferred embodiments, the step of responding to a tracing request for target power business data and tracing the historical state changes of the entity through an updated historical evolution chain includes: In response to a traceability request for target power business data, the traceability time interval is obtained; based on the traceability time interval, the updated historical evolution chain is traversed to identify multiple key change time points; based on the multiple key change time points, an index is established to obtain the historical state changes of the entity.
[0051] In some preferred embodiments, a composite index structure, such as a four-dimensional cross-index structure, can be used during the tracing process, thereby enabling efficient querying without the need for a caching strategy.
[0052] For example, the four-dimensional cross-index structure includes time indexes (such as year partitions, month partitions, day partitions, and time partitions), entity indexes (such as entity type indexes or entity identifier indexes), relationship indexes (such as relationship type indexes or relationship path indexes), and operation indexes (such as operation type indexes or operator indexes).
[0053] The above relationship types can refer to inclusion, association, and replacement, and the relationship path index can be represented as entity A → entity B → entity C.
[0054] Each time data is written or changed, the four-dimensional cross-index structure can be updated synchronously, and a hash code can be generated based on the four-dimensional cross-index structure for subsequent data tracing, such as "Hash[time index + entity index + relationship index + operation index]".
[0055] In addition, the index can be reorganized during daily off-peak hours to optimize query paths. By combining a multi-dimensional entity association network, a complete path for changes such as meter removal / replacement in the electricity metering ledger can be constructed, simplifying the traversal path, providing backward index completion capabilities, and reproducing the electricity metering ledger operation records based on the transaction model at specific time points.
[0056] Furthermore, indexes for frequently queried regions can be preloaded based on historical query patterns; and tiered storage can be employed, such as storing recent data in high-speed storage and historical data in ordinary storage. In addition, some application examples can implement a two-phase time-space locking protocol to ensure the atomicity and consistency of collaborative changes among multiple entities.
[0057] Accordingly, such as Figure 2As shown, this invention application also provides a power business data traceability system 200, including a parsing module 201, an updating module 202, and a traceability module 203; wherein, The parsing module 201 is used to respond to a business operation request, parse the business operation request, and obtain status change information. The update module 202 is used to update the historical evolution chain of the corresponding entity through horizontal pointers and update the preset multi-dimensional entity association network through vertical pointers based on the state change information to obtain the target association network; wherein, the horizontal pointers and the vertical pointers are pre-configured in the same data structure; The traceability module 203 is used to respond to the traceability request of the target power business data, and to obtain the historical state changes of the entity through the updated historical evolution chain; based on the target association network, to reconstruct the entity association relationship at the target historical moment, thereby realizing the traceability of the target power business data.
[0058] As a preferred embodiment, the traceability system 200 further includes a network construction module, which is used before updating the preset multidimensional entity association network via vertical pointers: Construct the multidimensional entity association network with measurement points as the core; The dimensions of each entity defined in the multidimensional entity association network include time dimension, spatial dimension and state dimension; The time dimension includes creation time, activation time, modification time, and deactivation time; the spatial dimension includes sibling entity relationships and hierarchical entity relationships; the state dimension includes current state, historical state, and expected state.
[0059] As a preferred embodiment, the parsing module 201 parses the business operation request to obtain status change information, including: The parsing module 201 parses the business operation request to obtain the business fields; The status change information is obtained by comparing the business fields with the historical fields.
[0060] As a preferred embodiment, the parsing module 201 parses the business operation request to obtain business fields, including: The parsing module 201 performs semantic extraction on the business operation request to obtain the corresponding key parameters, relationship parameters and configuration parameters; wherein, the key parameters include the ratio, accuracy level and verification period, the relationship parameters include the bound metering point identifier and the associated user identifier, and the configuration parameters include the installation location and communication parameters. Based on the key parameters, relationship parameters, and configuration parameters, the fields are extracted to obtain the business fields.
[0061] As a preferred embodiment, before updating the historical evolution chain of the corresponding entity via the horizontal pointer, the method further includes: The data source of the business operation request is verified to determine whether the data source has the necessary operation permissions. When it is determined that the user has the operation permission, the identity of the user who issued the business operation request is determined, and the user identity is compared with a preset permission matrix table; When a user's identity is in the preset permission matrix table, the user's identity is verified to determine whether the corresponding user has the permission to modify the entity corresponding to the business operation request and its associated entities; When it is determined that the user has the authority to modify the entity corresponding to the business operation request and its associated entities, the business operation request is verified using power business rules.
[0062] As a preferred embodiment, the step of responding to a traceability request for target power business data by tracing the historical state changes of the entity through an updated historical evolution chain includes: In response to a traceability request for target power business data, obtain the traceability time range; Based on the aforementioned time interval, the updated historical evolution chain is traversed to identify multiple key change points. An index is established based on the multiple key change time points to obtain the historical state changes of the entity.
[0063] As a preferred embodiment, before updating the historical evolution chain of the corresponding entity via the horizontal pointer, the method further includes: An operation identifier corresponding to the business operation request is generated by a preset transaction coordinator; wherein the operation identifier records the operation type code, timestamp, and sequence number.
[0064] Accordingly, this application also provides a terminal device, including a processor, a memory, and a computer program stored in the memory and configured to be executed by the processor, wherein the processor executes the computer program to implement the power business data traceability method.
[0065] The processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor can be a microprocessor or any conventional processor. The processor is the control center of the terminal, connecting various parts of the terminal via various interfaces and lines.
[0066] The memory can be used to store the computer program. The processor implements various functions of the terminal by running or executing the computer program stored in the memory and calling the data stored in the memory. The memory may mainly include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function (such as sound playback function, image playback function, etc.), etc.; the data storage area may store data created according to the use of the mobile phone (such as audio data, phonebook, etc.). In addition, the memory may include high-speed random access memory, and may also include non-volatile memory, such as hard disk, memory, plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, at least one disk storage device, flash memory device, or other volatile solid-state storage device.
[0067] Accordingly, this application also provides a computer-readable storage medium, the computer-readable storage medium including a stored computer program, wherein, when the computer program is executed, it controls the device where the computer-readable storage medium is located to execute the power business data tracing method.
[0068] Wherein, if the modules of the device / terminal equipment / system integration are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments of the present invention can also be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when the computer program is executed by a processor, it can implement the steps of the various method embodiments described above. Wherein, the computer program includes computer program code, which can be in the form of source code, object code, executable file, or some intermediate form, etc. The computer-readable medium can include: any entity or device capable of carrying the computer program code, recording medium, USB flash drive, portable hard drive, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signal, telecommunication signal, and software distribution medium, etc.
[0069] Compared with the prior art, this invention application has the following beneficial effects: This invention provides a method, system, device, and medium for tracing power business data. The tracing method includes: responding to a business operation request, parsing the business operation request to obtain state change information; based on the state change information, updating the historical evolution chain of the corresponding entity through a horizontal pointer, and updating a preset multi-dimensional entity association network through a vertical pointer to obtain a target association network; wherein the horizontal pointer and the vertical pointer are pre-configured in the same data structure; responding to a tracing request for target power business data, tracing the historical state changes of the entity through the updated historical evolution chain; and reconstructing the entity association relationship at the target historical moment based on the target association network, thereby realizing the tracing of the target power business data. Existing technologies lack a correlation mechanism when modifying power business data, resulting in the limitation of "single entity" data. This invention addresses this issue by updating the historical evolution chain and the preset multi-dimensional entity association network using horizontal and vertical pointers within the same data structure during modification. This ensures the complete restoration of the association state at any historical moment during tracing. Furthermore, this technical concept, by covering modification and tracing, guarantees data management throughout the entire lifecycle of power business scenarios, enabling precise tracing of power metering ledgers from single entities to multi-dimensional relationships, and from the current state to any historical node. This provides reliable data support for metering dispute resolution and anomaly analysis. Further, the vertical pointer is used to update the multi-dimensional entity association network (e.g., updating the business relationships of multiple entities), while the horizontal pointer synchronously records the historical evolution chain of entities (e.g., changes in the entity's own time sequence). This unifies the time dimension and the spatial dimension (entity association). When a modification occurs based on a business operation request, the modification trajectory of each entity can be accurately linked through the horizontal and vertical pointers, avoiding logical gaps in historical state reconstruction caused by scattered modification records and ensuring spatiotemporal consistency during tracing.
[0070] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of the present invention. It should be understood that the above descriptions are merely specific embodiments of the present invention and are not intended to limit the scope of protection of the present invention. In particular, it should be noted that any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention for those skilled in the art.
Claims
1. A method for tracing power business data, characterized in that, include: In response to a business operation request, the business operation request is parsed to obtain status change information; Based on the state change information, the historical evolution chain of the corresponding entity is updated by the horizontal pointer, and the preset multidimensional entity association network is updated by the vertical pointer to obtain the target association network; wherein, the horizontal pointer and the vertical pointer are pre-configured in the same data structure; In response to a tracing request for target power business data, the historical state changes of the entity are obtained through an updated historical evolution chain; based on the target association network, the entity association relationship at the target historical moment is reconstructed, thereby realizing the tracing of the target power business data.
2. The method for tracing power business data as described in claim 1, characterized in that, Before updating the preset multidimensional entity association network via vertical pointers, the following is also included: Construct the multidimensional entity association network with measurement points as the core; The dimensions of each entity defined in the multidimensional entity association network include time dimension, spatial dimension and state dimension; The time dimension includes creation time, activation time, modification time, and deactivation time; the spatial dimension includes sibling entity relationships and hierarchical entity relationships; the state dimension includes current state, historical state, and expected state.
3. The method for tracing power business data as described in claim 1, characterized in that, The step of parsing the business operation request to obtain status change information includes: The business operation request is parsed to obtain the business fields; The status change information is obtained by comparing the business fields with the historical fields.
4. The method for tracing power business data as described in claim 3, characterized in that, The step of parsing the business operation request to obtain business fields includes: Semantic extraction is performed on the business operation request to obtain the corresponding key parameters, relationship parameters, and configuration parameters; wherein, the key parameters include the transformation ratio, accuracy level, and verification period, the relationship parameters include the bound metering point identifier and the associated user identifier, and the configuration parameters include the installation location and communication parameters; Based on the key parameters, relationship parameters, and configuration parameters, the fields are extracted to obtain the business fields.
5. The method for tracing power business data as described in claim 1, characterized in that, Before updating the historical evolution chain of the corresponding entity via the horizontal pointer, the following is also included: The data source of the business operation request is verified to determine whether the data source has the necessary operation permissions. When it is determined that the user has the operation permission, the identity of the user who issued the business operation request is determined, and the user identity is compared with a preset permission matrix table; When a user's identity is in the preset permission matrix table, the user's identity is verified to determine whether the corresponding user has the permission to modify the entity corresponding to the business operation request and its associated entities; When it is determined that the user has the authority to modify the entity corresponding to the business operation request and its associated entities, the business operation request is verified using power business rules.
6. The method for tracing power business data as described in claim 1, characterized in that, The process of responding to a traceability request for target power business data, and obtaining the historical state changes of the entity through an updated historical evolution chain, includes: In response to a traceability request for target power business data, obtain the traceability time range; Based on the aforementioned time interval, the updated historical evolution chain is traversed to identify multiple key change points. An index is established based on the multiple key change time points to obtain the historical state changes of the entity.
7. A method for tracing power business data as described in any one of claims 1 to 6, characterized in that, Before updating the historical evolution chain of the corresponding entity via the horizontal pointer, the following is also included: An operation identifier corresponding to the business operation request is generated by a preset transaction coordinator; wherein the operation identifier records the operation type code, timestamp, and sequence number.
8. A traceability system for power business data, characterized in that, It includes a parsing module, an update module, and a tracing module; among which, The parsing module is used to respond to a business operation request, parse the business operation request, and obtain status change information. The update module is used to update the historical evolution chain of the corresponding entity through horizontal pointers and update the preset multi-dimensional entity association network through vertical pointers based on the state change information to obtain the target association network; wherein, the horizontal pointers and the vertical pointers are pre-configured in the same data structure; The tracing module is used to respond to the tracing request of the target power business data, and to obtain the historical state changes of the entity through the updated historical evolution chain; based on the target association network, to reconstruct the entity association relationship at the target historical moment, thereby realizing the tracing of the target power business data.
9. A terminal device, characterized in that, It includes a processor, a memory, and a computer program stored in the memory and configured to be executed by the processor, wherein the processor, when executing the computer program, implements the method for tracing power business data as described in any one of claims 1 to 7.
10. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored computer program, wherein, when the computer program is executed, it controls the device on which the computer-readable storage medium is located to perform the power business data tracing method as described in any one of claims 1 to 7.