Asset management system and method

Abstract

The application discloses an asset management system and method, the system comprises: an asset map modeling module, a transfer range analysis module, a transfer module, a right change module; wherein: the asset map modeling module is used for acquiring target asset data corresponding to a transferor; determining a target asset map according to the target asset data; the transfer range analysis module is used for acquiring first transfer information of a transferee for the target asset data; determining a target transfer range according to the first transfer information and the target asset map; the transfer module is used for determining second transfer information according to the target transfer range; acquiring target feedback information of the transferee for the second transfer information; the right change module is used for changing the ownership of the corresponding components in the target asset data to the transferee according to the second transfer information and the target asset map when the target feedback information includes consent to transfer. By using the application, the consistency of the right of ownership transfer of assets is improved.

Description

Technical Field

[0001] This application relates to the field of asset management technology, and in particular to an asset management system and method. Background Technology

[0002] With the rapid development of aircraft leasing, used aircraft transfer, and asset package transfer businesses, ownership transfer transactions of hierarchical aviation assets are becoming increasingly frequent. However, aviation assets have typical hierarchical characteristics. A single aircraft usually contains high-value related components such as engines, auxiliary power units, and landing gear. These components have complex subordinate relationships with the fuselage, and the ownership entities can be independent of each other, continuously increasing the complexity and management difficulty of ownership transfer.

[0003] Currently, the transfer of ownership of aviation assets generally adopts a processing method that combines contractual terms with manual verification. However, the manual sorting of the scope of asset transfer and the execution of ownership changes on a transaction-by-transaction basis are prone to problems such as asset errors and omissions and asynchronous updates of ownership, resulting in poor consistency of asset ownership status at different levels and making it difficult to meet the compliance and risk control requirements of aviation asset transfer.

[0004] Therefore, how to improve the consistency of ownership in the transfer of assets has become an urgent problem to be solved. Summary of the Invention

[0005] This application provides an asset management system and method that improves the consistency of ownership during asset transfer.

[0006] In a first aspect, embodiments of this application provide an asset management system, including: an asset map modeling module, a transfer scope analysis module, a transfer module, and an ownership change module; wherein: The asset graph modeling module is used to acquire the target asset data corresponding to the transferor; determine the target asset graph based on the target asset data; the target asset graph is a directed attribute graph, which includes the graph nodes of the target main component and its related components corresponding to the target asset data, as well as directed edges representing the hierarchical subordinate relationship between components; each graph node carries the ownership information and transfer constraint marker of the corresponding component; The transfer scope analysis module is used to obtain the first transfer information of the transferee regarding the target asset data; and to determine the target transfer scope based on the first transfer information and the target asset map. The transfer module is used to determine second transfer information based on the target transfer scope; and to obtain target feedback information from the transferee regarding the second transfer information; the target feedback information includes any one of the following: consent to transfer, or disagreement with transfer; The ownership transfer module is used to transfer the ownership of the corresponding component in the target asset data to the transferee based on the second transfer information and the target asset map when the target feedback information includes consent to transfer.

[0007] Secondly, embodiments of this application provide an asset management method applied to the system described in the first aspect, the method comprising: The target asset data corresponding to the transferor is obtained through the asset graph modeling module; the target asset graph is determined based on the target asset data; the target asset graph is a directed attribute graph, which includes the graph nodes of the target main component and its related components corresponding to the target asset data, as well as directed edges representing the hierarchical subordinate relationship between components; each graph node carries the ownership information and transfer constraint mark of the corresponding component; The transfer scope analysis module obtains the first transfer information of the transferee regarding the target asset data; based on the first transfer information and the target asset map, the target transfer scope is determined. The transfer module determines second transfer information based on the target transfer scope; it obtains target feedback information from the transferee regarding the second transfer information; the target feedback information includes any one of the following: agreement to transfer, disagreement to transfer; When the target feedback information includes consent to transfer, the ownership change module, based on the second transfer information and the target asset map, changes the ownership of the corresponding components in the target asset data to the transferee.

[0008] Thirdly, embodiments of this application provide an electronic device, including: a processor, a memory, a communication interface, and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the processor, and the programs include instructions for performing the steps in the second aspect of embodiments of this application.

[0009] Fourthly, embodiments of this application provide a computer-readable storage medium storing a computer program for electronic data interchange, wherein the computer program causes a computer to perform some or all of the steps described in the second aspect of embodiments of this application.

[0010] Fifthly, embodiments of this application provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program operable to cause a computer to perform some or all of the steps described in the second aspect of embodiments of this application. The computer program product may be a software installation package.

[0011] Implementing this application will have the following beneficial effects: As can be seen, the asset management system and method described in this application construct a target asset map through an asset map modeling module, which uniformly and structurally maps multi-level assets such as complete machines, subsystems, and components, forming a unique and complete asset ownership data benchmark, avoiding information bias caused by traditional data fragmentation. Then, the transfer scope analysis module accurately analyzes the transfer requirements based on the hierarchical relationship of the target asset map, automatically matching the corresponding target transfer scope, eliminating the problem of omission or exceeding the scope of transfer due to manual judgment. After confirmation by the transferee, the ownership change module synchronously completes the ownership update of all assets in the target transfer scope, realizing the synchronous change and unified retention of the ownership status of related assets at different levels, effectively avoiding the ownership fragmentation and data inconsistency problems caused by traditional single-point changes, thereby improving the consistency of ownership transfer of assets. Attached Figure Description

[0012] To more clearly illustrate the technical solutions in the embodiments of this application or the background art, the accompanying drawings used in the embodiments of this application or the background art will be described below.

[0013] Figure 1 This is a schematic diagram of the structure of an asset management system provided in an embodiment of this application; Figure 2 This is a flowchart of a method for determining a target asset map provided in an embodiment of this application; Figure 3 This is a schematic diagram of a target asset map provided in an embodiment of this application; Figure 4 This is a schematic diagram of another asset management system provided in the embodiments of this application; Figure 5 This is a schematic diagram of the structure of another asset management system provided in the embodiments of this application; Figure 6 This is a flowchart of an asset management method provided in an embodiment of this application; Figure 7 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application; Figure 8 This is a schematic diagram of the structure of a computer-readable storage medium provided in an embodiment of this application. Detailed Implementation

[0014] 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. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present application.

[0015] The terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish different objects, not to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or apparatuses.

[0016] It should be understood that the term "and / or" in this document is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this document indicates that the preceding and following related objects are in an "or" relationship. In the embodiments of this application, "multiple" refers to two or more.

[0017] In the embodiments of this application, "at least one item" or its similar expression refers to any combination of these items, including any combination of a single item or a plurality of items. "One or more" means one or more, while "multiple" means two or more. For example, "at least one item" of a, b, or c can represent the following seven cases: a, b, c; a and b; a and c; b and c; a, b, and c. Each of a, b, and c can be an element or a set containing one or more elements.

[0018] In this application, the term "connection" refers to various connection methods, such as direct connection or indirect connection, to achieve communication between devices. This application does not impose any limitations on this.

[0019] In this document, the term "embodiment" 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 this phrase 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.

[0020] The electronic devices described in this application embodiment may include smartphones (such as Android phones, iOS phones, Windows Phones, etc.), tablet computers, PDAs, laptops, video matrices, monitoring platforms, mobile internet devices (MIDs), or wearable devices, etc. The above are merely examples and not exhaustive, and include but are not limited to the above devices.

[0021] Of course, the aforementioned electronic devices can also serve as asset management systems.

[0022] The following describes the relevant content, concepts, meanings, technical issues, technical solutions, and beneficial effects involved in the embodiments of this application.

[0023] Please see Figure 1 , Figure 1 This is a schematic diagram of the structure of an asset management system provided in an embodiment of this application; it can be seen that the asset management system (hereinafter referred to as the system) may include: an asset map modeling module, a transfer scope analysis module, a transfer module, and an ownership change module; wherein: The asset graph modeling module is used to acquire the target asset data corresponding to the transferor; determine the target asset graph based on the target asset data; the target asset graph is a directed attribute graph, which includes the graph nodes of the target main component and its related components corresponding to the target asset data, as well as directed edges representing the hierarchical subordinate relationship between components; each graph node carries the ownership information and transfer constraint mark of the corresponding component.

[0024] In this embodiment of the application, the target main component can be an aircraft, and the associated components of the target main component can include at least one of the following: power engine system, avionics system, landing gear system, hydraulic system, fuel system, engine high-pressure blades, airborne positioning module, flight control components, main landing gear wheels, hydraulic pump, fuel sensor, etc., which are not limited here.

[0025] It should be explained that, in some embodiments, the target main component is not limited to aircraft, but can also be other physical assets with clear multi-level subordinate assembly relationships that support the construction of hierarchical directed attribute asset graphs, such as trains, ships, etc., which are not limited here.

[0026] In a specific embodiment, the asset mapping modeling module is used to obtain the target asset data corresponding to the transferor, as follows: Step 1: Identity and Authorization Verification The system receives the transferor's identity credentials, verifies the transferor's holding rights to the target entity components, and only allows the retrieval of corresponding asset data when the transferor is the registered owner of the asset, blocking unauthorized access requests.

[0027] Step 2, Asset Index Matching: Using the transferor's identity identifier (e.g., ID number) as the search keyword, the system's backend asset registration database is queried to filter out all asset entries whose ownership field is bound to the transferor's identity identifier, and an asset index list to be retrieved is generated.

[0028] Step 3: Target Asset Selection: Display all assets in the asset index list, receive selection instructions input by the transferor, and identify the single target entity component (e.g., a single aircraft) corresponding to this transfer of ownership.

[0029] Step 4: Retrieve complete asset data in layers: Based on the unique identifier of the selected target component, retrieve all associated data hierarchically: (1) Basic data of main components: asset identification, model / type, factory information, registration ownership, and global transfer constraint mark; (2) Basic data of related components at all levels: identification of each subsystem and component, hierarchical subordination identification, independent ownership information, and single component transfer constraint mark; (3) Supporting related business data: historical ownership change records, maintenance ledgers, and filing and transfer restriction clauses.

[0030] Step 5: Data straightening and output: Duplicate and invalid redundant fields are removed, a unified structured format is adopted, and integrated to form complete target asset data that can be used to construct an asset map.

[0031] Then, a target asset map can be constructed based on the target asset data.

[0032] In some embodiments, the target asset data includes: the target main component and a associated components corresponding to the target main component; a is an integer greater than 1; see [link to relevant documentation]. Figure 2 , Figure 2 This is a flowchart of a method for determining a target asset map according to an embodiment of this application. As can be seen, in determining the target asset map based on the target asset data, the asset map modeling module specifically performs the following steps: S11. Obtain the target ownership information and target transfer constraint mark corresponding to the target main component; S12. Obtain the ownership information and transfer constraint flags corresponding to the a associated components; S13. Based on the a ownership information, the a transfer constraint markers, the target ownership information and the target transfer constraint markers, map the a associated components and the target main component as graph nodes to obtain a+1 graph nodes; S14. Determine the hierarchical subordinate relationship data between the a associated components and the target main component; S15. Based on the hierarchical subordinate relationship data and the a+1 graph nodes, determine the target asset graph.

[0033] In this embodiment of the application, the target asset data may include not only the target main component and a related components, but also the ownership information and transfer constraint mark corresponding to each component.

[0034] In a specific embodiment, the target ownership information and target transfer constraint mark corresponding to the target main component are obtained; the ownership information and transfer constraint mark corresponding to a related components are obtained; specifically, the target asset data can be traversed, firstly the data entry corresponding to the target main component is located, and the target ownership information and target transfer constraint mark stored in the data entry are read; then the a related component data entries in the target asset data that have a direct or indirect hierarchical subordinate relationship with the target main component are traversed, and the ownership information and transfer constraint mark corresponding to each related component are extracted one by one, so as to obtain a ownership information and a transfer constraint mark respectively.

[0035] Next, based on 'a' ownership information, 'a' transfer constraint markers, target ownership information, and target transfer constraint markers, 'a' related components and the target main component can be mapped to graph nodes, resulting in 'a+1' graph nodes. Specifically, a globally unique graph node identifier can be assigned to the target main component and each related component. The ownership information and transfer constraint markers corresponding to each component are written into the corresponding node as attribute fields, completing the binding and mounting of attributes and nodes. Among them, the target main component corresponds to 1 top-level root node, and 'a' related components each correspond to 'a' child nodes, resulting in a total of 'a+1' independent graph nodes. Each node corresponds one-to-one with an asset component, and the node attributes are consistent with the component data.

[0036] Then, the hierarchical subordinate relationship data between the a related components and the target main component is determined. Specifically, the pre-set upper-level assembly main component identifier field in the data of each related component can be read. This field clearly records the upper-level component to which the component belongs. Using the unique identifier of the target main component as the top-level benchmark, the upper-level identifiers of each related component are matched one by one to identify the direct upper-level component of each related component, forming a subordinate relationship pair of "upper-level component-lower-level component". For multi-level subordinate scenarios, the upper-level identifiers are matched iteratively level by level to sort out the complete hierarchical link from the target main component to the first-level related component, and then to the second-level and lower-level related components, and finally obtain the set of hierarchical subordinate relationships between all components, that is, the hierarchical subordinate relationship data.

[0037] Finally, based on the hierarchical dependency data and a+1 graph nodes, the target asset graph is determined. Specifically, the a+1 graph nodes are used as the vertex set of the directed attribute graph, and the hierarchical dependency data is transformed into a set of directed edges. Each directed edge points from a higher-level component node to a lower-level component node, representing the hierarchical dependency relationship between components. Extended attributes such as dependency type and assembly time can be attached to the directed edges according to business needs. Finally, the vertex set and the directed edge set are structurally encapsulated to form a complete directed attribute graph, i.e., the target asset graph.

[0038] In some embodiments, the specific settings for the graph nodes and directed edges of the target asset graph are as follows: Each graph node corresponds one-to-one with an asset component. Each graph node's attributes include at least: a unique asset identifier, asset type, current ownership entity (i.e., ownership information), and transfer constraint markers. The unique asset identifier uniquely identifies the corresponding asset entity, such as the fuselage serial number or engine manufacturing serial number. The asset type distinguishes the asset's category, including aircraft, engines, auxiliary power units (APUs), landing gear, and other component categories. The current ownership entity records the current owner of the asset. The transfer constraint marker indicates the asset's transfer constraints, such as "can be transferred independently," "cannot be transferred independently, must be transferred along with component xx," or "cannot be transferred independently, must be transferred along with a superior subordinate component." The target asset graph may only include directed edges of the CONTAINS class. CONTAINS directed edges point from parent nodes to child nodes, representing the relationships between assets. For example, if an aircraft includes engines, the aircraft can be the parent node and the engine the child node.

[0039] In this way, by extracting the ownership and transfer constraints of the main body and related components separately and binding them to independent graph nodes, and constructing an asset graph by combining hierarchical subordinate relationships, the ownership and transfer constraints are collected in a hierarchical and refined manner. Based on standardized hierarchical associations, a unified asset data benchmark is formed, which provides accurate basis for the analysis of transfer scope, compliance verification, and batch ownership changes, reduces the problems of transfer omissions and changes beyond the scope, and improves the consistency and compliance of ownership transfer.

[0040] In some embodiments, please refer to Figure 3 , Figure 3 This is a schematic diagram of a target asset map provided in an embodiment of this application. As can be seen, the target asset map includes three layers, as detailed below: First level (top-level parent node): Node 1: The entire core asset (e.g., the complete machine) is the highest-level node, which is divided into 3 second-level sub-nodes and controls the overall ownership of the asset.

[0041] Second level (first-level child nodes): Node 21: The first sub-component of Node 1, which itself contains two third-level sub-components; Node 22: The second sub-component of Node 1, with no lower-level child nodes, and is an independent second-level component; Node 23: The third sub-component of Node 1, which itself contains a third-level sub-component.

[0042] Third layer (lower-level components under second-level child nodes): Nodes 31 and 32: Both belong to node 21 and are the underlying components contained in node 21; Node 33: Belongs to node 23 and is a low-level component contained in node 23.

[0043] The topological relationships (dependent links) of the target asset map are as follows: Node 1 - Node 21 - Node 31, Node 32; Nodes 1-22 (no child nodes); Node 1-Node 23-Node 33.

[0044] In some embodiments, node 1 may represent the entire aircraft; the aircraft includes an aviation power system, an airborne avionics control unit, and a landing gear assembly; Node 21 can represent the aero-engine system (engine assembly); Node 31 represents the engine turbine; Node 32 represents the engine combustion chamber; that is, the aero-engine system contains two core components: the engine turbine and the engine combustion chamber.

[0045] Node 22 represents the airborne avionics main control unit. This unit is packaged as an integral module at the factory and no longer disassembles the underlying components, so there are no lower-level sub-nodes.

[0046] Node 23 represents the landing gear assembly; Node 33 represents the main landing gear strut.

[0047] The transfer scope analysis module is used to obtain the first transfer information of the transferee regarding the target asset data; and to determine the target transfer scope based on the first transfer information and the target asset map.

[0048] In this embodiment of the application, the transfer scope parsing module is used to receive the first transfer information submitted by the transferee for the target asset data; the first transfer information may include: the transferee's identity certificate and the request for transfer of ownership of the first component; the validity and transferee qualification of the transferee's identity certificate are verified, and unauthorized or invalid transfer applications are blocked; after the verification is passed, the target transfer scope can be determined according to the first transfer information and the target asset map.

[0049] In some embodiments, please refer to Figure 4 , Figure 4This is a schematic diagram of another asset management system provided in the embodiments of this application. It can be seen that, in addition to the asset map modeling module, the transfer scope analysis module, the transfer module, and the ownership change module, the asset management system may also include a human-computer interaction module, through which the transferee can manually input the first transfer information.

[0050] It should be noted that the transferor can also manually input the target asset data through the human-computer interaction module.

[0051] In some embodiments, the first transfer information includes: a request for transfer of ownership of a first component; and in determining the target transfer scope based on the first transfer information and the target asset map, the transfer scope parsing module is specifically used for: S21. Based on the target asset map, determine the reference transfer scope corresponding to the ownership transfer request of the first component; the reference transfer scope includes b related components; b is a positive integer less than or equal to a; S22. Determine the b transfer constraint markers corresponding to the b associated components; S23. Based on the b transfer constraint markers, determine c related components among the b related components that cannot be transferred individually; c is a positive integer less than or equal to b; S24. Based on the target asset map and the b transfer constraint markers, determine d associated components that have associated transfers with the c associated components; d is a positive integer less than a, and the sum of c and d is less than or equal to a; S25. Determine the target transfer range based on the b associated components and the d associated components.

[0052] In this embodiment of the application, the transfer constraint mark is used to mark the transfer constraint rules of the asset, such as "can be transferred separately", "cannot be transferred separately, must be transferred together with xx component", "cannot be transferred separately, must be transferred together with the superior subordinate component", etc., which are not limited here.

[0053] In a specific embodiment, the ownership transfer request of the first component can be analyzed based on the target asset map to determine the reference transfer scope; then, b transfer constraint markers corresponding to b related components can be determined. Specifically, b unique asset identifiers corresponding to these b related components can be obtained first, and b map nodes corresponding one-to-one with the b unique asset identifiers can be located in the target asset map. The attribute fields of each map node can be traversed, and the transfer constraint markers stored in the node can be extracted one by one. Each related component corresponds to an independent transfer constraint marker, and finally b transfer constraint markers are obtained.

[0054] Next, based on the b transfer constraint markers, we can determine c related components that cannot be transferred individually among the b related components. Specifically, we can traverse the b transfer constraint markers and match each transfer constraint marker with a preset set of markers that cannot be transferred individually to obtain c matching transfer constraint markers; and determine the c related components that correspond to the c transfer constraint markers among the b related components.

[0055] In some embodiments, the b transfer constraint markers can be traversed to find the transfer constraint markers that are not "transferable individually", resulting in c transfer constraint markers. The c associated components that correspond to the c transfer constraint markers among the b associated components can then be determined.

[0056] Then, based on the target asset map and b transfer constraint markers, d related components that have related transfers with c related components can be identified; finally, based on the b related components and d related components, the target transfer scope can be determined. Specifically, the b related components and d related components can be merged and deduplicated to obtain the target transfer scope.

[0057] In this way, the reference transfer scope applied for by the transferee is determined by the target asset graph, and the components that cannot be transferred alone are identified by the transfer constraint marks of each component node. Based on the directed edges of the graph, the related components that need to be transferred are automatically retrieved and integrated to form a compliant target transfer scope. This can automatically supplement the supporting assets required by the transfer constraints, avoid the problem of missing the binding assets or transferring beyond the scope, ensure that the transfer scope complies with the ownership restrictions of each asset, and improve the compliance and consistency of ownership transfer.

[0058] In some embodiments, regarding the determination of the reference transfer scope corresponding to the first component ownership transfer request based on the target asset map, the transfer scope parsing module is specifically used for: S31. Determine the first component data corresponding to the first component ownership transfer request; S32. Determine at least one map node in the target asset map corresponding to the first component data; S33. For each of the at least one graph node, starting from that graph node, traverse the target asset graph to obtain e graph nodes; e is an integer greater than or equal to b and less than or equal to a; the e graph nodes correspond to e associated components. S34. Based on the a ownership information, verify the transfer rights of the transferor for each of the e associated components to obtain e transfer rights; each transfer right includes any of the following: can be transferred individually, or has restricted transfer. S35. Based on the e transfer rights, determine f associated components that can be transferred individually and g associated components that are restricted from transfer among the e associated components; where f and g are natural numbers, and f + g = e; S36. Based on the f associated components and the g associated components, determine the b associated components.

[0059] In this embodiment of the application, the first component data corresponding to the first component ownership transfer request can be determined. Specifically, at least one unique asset identifier carried in the first component ownership transfer request is parsed to determine the asset data in the target asset data corresponding to this at least one unique asset identifier, that is, the first component data. Then, at least one graph node corresponding to the first component data in the target asset graph can be determined. Specifically, the target asset graph can be traversed to obtain at least one graph node corresponding to the above-mentioned at least one unique asset identifier.

[0060] Next, for each graph node in at least one graph node, starting from that graph node, traverse downwards along the directed edges of the target asset graph, collecting all associated graph nodes along the traversal path. After removing duplicate nodes, e graph nodes are obtained. Then, based on a ownership information, the transferor's transfer rights for each of the e associated components are verified, resulting in e transfer rights. Specifically, the ownership object of each of the e associated components is extracted from the a ownership information, resulting in e ownership objects (i.e., e ownership objects). The identity identifiers of these e ownership objects are compared with the identity identifier of the transferor. If they match, the transfer rights are determined to be "transferable individually"; otherwise, the transfer rights are determined to be "restricted transfer", thus obtaining e transfer rights.

[0061] Next, based on the e transfer permissions, we can determine f related components that can be transferred individually and g related components that are restricted from transfer among the e related components. Specifically, we iterate through the e transfer permissions, divide the components with the transfer permission of "can be transferred individually" into f components that can be transferred individually, and divide the components with the transfer permission of "restricted transfer" into g components that are restricted from transfer. Finally, based on the f related components and the g related components, we can determine b related components.

[0062] In this way, by traversing the target asset graph from the component node corresponding to the transfer request to obtain all related components, and then combining the ownership information to batch verify the transfer permissions and classify the transferable and restricted transfer components, the compliant reference transfer components can be screened out. This can completely cover all the bound related components of the requested asset at one time, accurately distinguish the transfer permission status, and screen out assets without disposal permissions or subject to transfer restrictions in advance, so as to avoid the situation where the transfer scope includes assets that cannot be disposed of.

[0063] In some embodiments, regarding the determination of the b associated components based on the f associated components and the g associated components, the transfer scope resolution module is specifically used for: S41. Determine the g ownership objects corresponding to the g associated components; S42. Obtain g feedback messages from the g ownership objects in response to the request for transfer of ownership of the first component; each feedback message includes any one of the following: consent to transfer, disagreement to transfer; S43. Based on the g feedback messages, determine h related components among the g related components that agree to the transfer; h is a natural number less than or equal to g, and h + f = b; S44. Determine the b associated components based on the h associated components and the f associated components.

[0064] In this embodiment of the application, firstly, g ownership objects corresponding to g associated components are determined. Specifically, the ownership object of each component in the g associated components can be extracted from a ownership information to obtain g ownership objects (i.e., g ownership objects). Next, g feedback information from the g ownership objects regarding the request for ownership transfer of the first component can be obtained. Specifically, the system can push transfer inquiry notices to the g ownership objects respectively and receive feedback information returned by each ownership object to obtain g feedback information.

[0065] Then, based on the g feedback messages, h related components that agree to the transfer can be identified from among the g related components. Specifically, the g feedback messages are traversed, the information indicating agreement to the transfer is filtered out, and the corresponding related components are matched among the g related components to obtain h related components that have obtained the license to transfer the ownership object. Finally, based on the h related components and f related components, b related components can be identified. Specifically, the h related components and f related components can be merged and deduplicated to obtain b related components.

[0066] In this way, by first identifying the ownership entities corresponding to the restricted transferable components and soliciting their opinions on the transfer, the related components that have obtained permits are screened out. Then, by combining the components that can be transferred separately to form a list of compliant reference transferable components, the restrictions on asset ownership and the disposal intentions of third-party ownership entities can be taken into account. Assets that have not obtained transfer permits are filtered out, ensuring that all b related components selected have the legal conditions for transfer and improving the compliance of the scope of transfer determination.

[0067] In some embodiments, regarding the determination of d associated components that have associated transfers with the c associated components based on the target asset map and the b transfer constraint markers, the transfer scope parsing module is specifically used for: S51. Determine the c map nodes in the target asset map that correspond to the c associated components; S52. For each of the c graph nodes, starting from that graph node, traverse the target asset graph to obtain h graph nodes; h is a natural number less than a. S53. Determine the h associated components corresponding to the h map nodes; S54. Determine the d associated components based on the h associated components and the b transfer constraint tags.

[0068] In this embodiment, the unique asset identifier corresponding to each of the c associated components can be extracted from the target asset data to obtain c unique asset identifiers; the unique asset identifier field in the node attributes is matched in the target asset graph to locate c graph nodes that correspond one-to-one with the c associated components; then, for each of the c graph nodes, starting from that graph node, the directed edges of the target asset graph are traversed downwards to collect all associated graph nodes on the traversal path, and after deduplication of duplicate nodes, h graph nodes are obtained.

[0069] Next, h associated components corresponding to h graph nodes can be extracted from a transfer constraint markers. Finally, based on the h associated components and b transfer constraint markers, d associated components are determined. Specifically, the transfer constraint markers corresponding to each of the c associated components are extracted from the b transfer constraint markers, resulting in c transfer constraint markers. Based on the c transfer constraint markers and h associated components, d associated components are determined. Specifically, a candidate component set can be extracted from the c transfer constraint markers. For example, assuming c=2, the c transfer constraint markers are: "Cannot be transferred alone, must be transferred together with motor X" and "Cannot be transferred alone, must be transferred together with oil tank Y and oil pump T". The corresponding candidate component set includes: motor X, oil tank Y, and oil pump T. Then, the candidate component set and h associated components are merged and deduplicated to obtain d associated components.

[0070] In this way, by automatically mining related components through graph traversal and filtering incremental components by combining transfer constraints, we can effectively avoid omissions in manual sorting, while filtering out duplicate and conflicting components, thereby improving the accuracy, compliance and processing efficiency of the transfer scope determination.

[0071] In some embodiments, regarding the determination of d associated components that have associated transfers with the c associated components based on the target asset map and the b transfer constraint markers, the transfer scope parsing module is specifically used for: For each of the c related components, extract the corresponding transfer constraint tag from the b transfer constraint tags, and then retrieve the related component in the target asset map based on the transfer constraint tag: If the transfer constraint is marked as "cannot be transferred separately, must be transferred together with component xx", the unique asset identifier of component xx can be obtained. By matching and searching the node attributes of all nodes in the target asset graph, the graph node corresponding to component xx can be directly located without traversing along the edges. Component xx is the associated component that needs to be transferred synchronously.

[0072] If the transfer constraint is marked as "cannot be transferred alone, must be transferred together with the superior subordinate component", since the directed edges of the CONTAINS class point from the superior parent node to the subordinate child node, representing a subordinate relationship, we take the currently non-transferable associated component node as the starting node, trace upwards in the direction of the CONTAINS class directed edges, find the superior assembly component node to which the associated component belongs, and the corresponding component is the associated component that needs to be transferred synchronously.

[0073] All retrieved related components are deduplicated to obtain d related transfer components that need to be included in the transfer scope (i.e., d related components).

[0074] The transfer module is used to determine second transfer information based on the target transfer scope; obtain target feedback information from the transferee regarding the second transfer information; the target feedback information includes any one of the following: agreeing to the transfer, or disagreeing with the transfer.

[0075] In this embodiment of the application, the transfer module generates second transfer information, which includes a request for the transfer of ownership of the second component and transfer constraints, based on the target transfer scope, and pushes it to the transferee; after viewing the second transfer information, the transferee submits target feedback information.

[0076] In some embodiments, the transferee may manually input target feedback information through the human-computer interaction module.

[0077] The ownership change module is used to generate a first prompt message when the target feedback information includes disagreement with the transfer. This first prompt message is used to prompt the transferee that they do not agree to the transfer and request the transferor to re-initiate the transfer. For example, the first prompt message can be "The transferee does not agree to the transfer. Please confirm again."

[0078] The ownership transfer module is used to transfer the ownership of the corresponding component in the target asset data to the transferee based on the second transfer information and the target asset map when the target feedback information includes consent to transfer.

[0079] In some embodiments, the second transfer information includes: a request for transfer of ownership of a second component; and in the process of transferring ownership of the corresponding asset in the target asset data to the transferee based on the second transfer information and the target asset map, the ownership change module is specifically used for: S61. Determine the second component data corresponding to the second component ownership transfer request; S62. Determine the i map nodes in the target asset map that correspond to the data of the second component; i is a positive integer less than or equal to a; S63. After obtaining the electronic signature confirmations of the transferor and the transferee regarding the second transfer information, update the i ownership information corresponding to the i graph nodes.

[0080] In a specific embodiment, the second component data corresponding to the second component ownership transfer request is determined. Specifically, the method for obtaining the second component data can be the same as the method for obtaining the first component data, and is not limited here. Then, i graph nodes in the target asset graph corresponding to the second component data can be determined. Specifically, the second component data may include i unique asset identifiers. The target asset graph is traversed to obtain i graph nodes corresponding to the i unique asset identifiers.

[0081] Next, the system can generate an electronic contract for the second transfer information and push the electronic contract to the transferor and transferee respectively, so that both parties can sign the electronic signature to confirm the transfer. After obtaining the electronic signature confirmation of the transferor and transferee for the second transfer information, the system updates the i ownership information corresponding to the i graph nodes. Specifically, it retrieves the ownership information fields corresponding to the i graph nodes, replaces the original ownership subject identifier in each ownership information field with the transferee's identity identifier, and completes the persistent update of the ownership data of all i graph nodes.

[0082] If the electronic signature confirmation of the second transfer information is not obtained from the transferor and the transferee, it means that the two parties have not reached a transfer agreement. The system retains the current second transfer information, electronic contract and signing record, and generates a second prompt message. The second prompt message is used to inform the transferor that the signing process of this transfer has not been completed. The transfer scope can be readjusted as needed and new second transfer information can be generated to initiate signing confirmation.

[0083] In this way, by accurately matching the nodes corresponding to the components to be transferred through the target asset map, all components to be changed are identified, avoiding omissions in asset ownership changes; ownership updates are only executed after both parties have completed electronic signature confirmation, ensuring that the change operation is based on the mutual agreement of both parties, guaranteeing the legality and validity of the ownership change, and achieving automated and accurate asset ownership changes, reducing the risk of errors from manual matching. In some embodiments, please refer to Figure 5 , Figure 5This is a schematic diagram of another asset management system provided in this application embodiment. It can be seen that, in addition to the asset map modeling module, transfer scope analysis module, transfer module, ownership change module, and human-computer interaction module, the asset management system also includes: a distributed ownership evidence storage module; wherein: The ownership change module is further configured to generate an ownership change record after the ownership of the corresponding component in the target asset data is changed to the transferee. Specifically, the ownership change module can obtain all component data of this transfer, electronic contract information signed by both parties, ownership subject before and after the change, change timestamp, transfer constraint clauses, and other information, and integrate this information into an ownership change record in a first preset format. The first preset format may include any of the following: JSON format, PDF format, XML format, etc., without limitation.

[0084] The ownership distributed evidence storage module is used to upload the ownership change record to a preset blockchain network for storage. Specifically, the preset blockchain network can be preset in advance or be the default.

[0085] In some embodiments, the ownership distributed evidence storage module is further configured to generate a graph change record when a graph node of the target asset graph changes, and upload the graph change record to the preset blockchain network for storage. Specifically, when a graph node of the target asset graph changes, the ownership distributed evidence storage module can extract information such as the changed node identifier, the node ownership information before the change, the node ownership information after the change, the change operation timestamp, and the identity information of the operating entity, integrate this information into a graph change record in a second preset format, and upload the graph change record to the preset blockchain network for evidence storage. The second preset format can be preset in advance or defaulted to.

[0086] It should be explained that the second preset format can be the same as or different from the first preset format.

[0087] In summary, the asset management system described in this application constructs a target asset map through an asset map modeling module, uniformly mapping multi-level assets such as complete machines, subsystems, and components to form a unique and complete asset ownership data benchmark, avoiding information bias caused by traditional data fragmentation. Next, the transfer scope analysis module, relying on the hierarchical relationships of the target asset map, accurately analyzes transfer requirements and automatically matches the corresponding target transfer scope, eliminating issues of omissions or exceeding the scope of transfer due to manual judgment. After confirmation by the transferee, the ownership change module synchronously updates the ownership of all assets within the target transfer scope, achieving synchronized changes and unified retention of ownership status for related assets at different levels. This effectively avoids the ownership fragmentation and data inconsistency problems caused by traditional single-point changes, thereby improving the consistency of asset ownership transfer.

[0088] Please see Figure 6 , Figure 6 This is a flowchart of an asset management method provided in an embodiment of this application; it can be seen that the asset management method is applied to any asset management system as described in the above embodiments, and the method includes: S1. Obtain the target asset data corresponding to the transferor through the asset graph modeling module; determine the target asset graph based on the target asset data; the target asset graph is a directed attribute graph, which includes the graph nodes of the target main component and its associated components corresponding to the target asset data, as well as directed edges representing the hierarchical subordinate relationship between components; each graph node carries the ownership information and transfer constraint mark of the corresponding component; S2. Obtain the first transfer information of the transferee regarding the target asset data through the transfer scope parsing module; determine the target transfer scope based on the first transfer information and the target asset map; S3. Determine the second transfer information based on the target transfer scope through the transfer module; obtain the target feedback information from the transferee regarding the second transfer information; the target feedback information includes any one of the following: agree to the transfer, disagree to the transfer; S4. When the target feedback information includes consent to transfer, the ownership change module changes the ownership of the corresponding component in the target asset data to the transferee according to the second transfer information and the target asset map.

[0089] In specific implementations, the asset management method described in the embodiments of the present invention can also execute other implementation methods described in the asset management system provided in the embodiments of the present invention, which will not be repeated here.

[0090] Please see Figure 7 , Figure 7 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. The electronic device may include a processor, a memory, a communication interface, and one or more programs. The processor, memory, and communication interface can be interconnected via a bus. The one or more programs are stored in the memory and configured to be executed by the processor. In this embodiment, the programs include steps for performing some or all of the steps in the method embodiments described above.

[0091] The processor can be a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute the various exemplary logic blocks, cells, and circuits described in conjunction with the disclosure of this application. The processor can also be a combination that implements computational functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc. The communication unit can be a communication interface, transceiver, transceiver circuit, etc., and the storage unit can be a memory.

[0092] The memory can be volatile or non-volatile, or a combination of both. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), used as an external cache. By way of example, but not limitation, many forms of random access memory (RAM) are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate synchronous DRAM (DDR SDRAM), enhanced synchronous DRAM (ESDRAM), synchronous linked DRAM (SLDRAM), and direct rambus RAM (DR RAM).

[0093] It is understood that electronic devices may include more or fewer structural elements than those shown in the above block diagram, such as power modules, physical buttons, Wi-Fi modules, speakers, Bluetooth modules, sensors, display modules, etc., without limitation.

[0094] Please see Figure 8 , Figure 8 This is a schematic diagram of the structure of a computer-readable storage medium provided in an embodiment of this application. As can be seen, the computer-readable storage medium stores a computer program that causes a computer to perform some or all of the steps of any of the methods described in the above method embodiments. The computer includes an electronic device.

[0095] This application also provides a computer program product, which includes a non-transitory computer-readable storage medium storing a computer program operable to cause a computer to perform some or all of the steps of any of the methods described in the above method embodiments. The computer program product may be a software installation package, and the computer may include an electronic device.

[0096] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential to this application.

[0097] In the above embodiments, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.

[0098] In the several embodiments provided in this application, it should be understood that the disclosed apparatus can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of the units described above 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 devices or units may be electrical or other forms.

[0099] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. This program can be stored in a computer-readable storage medium, and when executed, it can include the processes described in the above method embodiments. The aforementioned storage medium includes various media capable of storing program code, such as ROM or random access memory (RAM), magnetic disks, or optical disks.

[0100] The steps of the methods or algorithms described in the embodiments of this application can be implemented in hardware or by a processor executing software instructions. The software instructions can consist of corresponding software modules, which can be stored in RAM, flash memory, ROM, EPROM, electrically erasable programmable read-only memory (EEPROM), registers, hard disk, portable hard disk, read-only optical disk (CD-ROM), or any other form of storage medium well known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Furthermore, the ASIC can reside in a terminal device or management device. Alternatively, the processor and storage medium can exist as discrete components in the terminal device or management device.

[0101] Those skilled in the art will recognize that, in one or more of the examples above, the functions described in the embodiments of this application can be implemented, in whole or in part, by software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, in the form of a computer program product. This computer program product includes one or more computer instructions. When these computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated.

[0102] The aforementioned computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media.

[0103] The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital video discs (DVDs)), or semiconductor media (e.g., solid-state disks (SSDs)).

[0104] The modules / units included in the various devices and products described in the above embodiments can be software modules / units, hardware modules / units, or a combination of both. For example, for devices and products applied to or integrated into a chip, all modules / units can be implemented using hardware methods such as circuits, or at least some modules / units can be implemented using software programs that run on a processor integrated within the chip, while the remaining (if any) modules / units can be implemented using hardware methods such as circuits. For devices and products applied to or integrated into a chip module, all modules / units can be implemented using hardware methods such as circuits. Different modules / units can be located in the same component (e.g., chip, circuit module, etc.) or different components of the chip module, or at least some modules / units can be implemented using hardware methods such as circuits. The implementation is achieved through a software program that runs on the processor integrated within the chip module. The remaining modules / units (if any) can be implemented using hardware methods such as circuits. For various devices and products applied to or integrated into terminal equipment, each of their modules / units can be implemented using hardware methods such as circuits. Different modules / units can be located in the same component (e.g., chip, circuit module, etc.) or different components within the terminal equipment. Alternatively, at least some modules / units can be implemented through a software program that runs on the processor integrated within the terminal equipment, while the remaining modules / units (if any) can be implemented using hardware methods such as circuits.

[0105] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of the embodiments of this application. It should be understood that the above descriptions are merely specific embodiments of the embodiments of this application and are not intended to limit the protection scope of the embodiments of this application. Any modifications, equivalent substitutions, improvements, etc., made on the basis of the technical solutions of the embodiments of this application should be included within the protection scope of the embodiments of this application.

Claims

1. An asset management system, characterized in that, include: The module includes an asset mapping modeling module, a transfer scope analysis module, a transfer module, and a ownership change module; among which: The asset graph modeling module is used to acquire the target asset data corresponding to the transferor; determine the target asset graph based on the target asset data; the target asset graph is a directed attribute graph, which includes the graph nodes of the target main component and its related components corresponding to the target asset data, as well as directed edges representing the hierarchical subordinate relationship between components; each graph node carries the ownership information and transfer constraint marker of the corresponding component; The transfer scope analysis module is used to obtain the first transfer information of the transferee regarding the target asset data; and to determine the target transfer scope based on the first transfer information and the target asset map. The transfer module is used to determine second transfer information based on the target transfer scope; and to obtain target feedback information from the transferee regarding the second transfer information; the target feedback information includes any one of the following: consent to transfer, or disagreement with transfer; The ownership transfer module is used to transfer the ownership of the corresponding component in the target asset data to the transferee based on the second transfer information and the target asset map when the target feedback information includes consent to transfer.

2. The system as described in claim 1, characterized in that, The target asset data includes: the target main component and a associated components corresponding to the target main component; where a is an integer greater than 1. In determining the target asset map based on the target asset data, the asset map modeling module is specifically used for: Obtain the target ownership information and target transfer constraint mark corresponding to the target main component; Obtain the ownership information and transfer constraint tags corresponding to the a associated components; Based on the a ownership information, the a transfer constraint markers, the target ownership information, and the target transfer constraint markers, the a associated components and the target main component are mapped to graph nodes to obtain a+1 graph nodes; Determine the hierarchical relationship data between the a associated components and the target main component; Based on the hierarchical subordinate relationship data and the a+1 graph nodes, the target asset graph is determined.

3. The system as described in claim 2, characterized in that, The first transfer information includes: a request for the transfer of ownership of the first component; In determining the target transfer scope based on the first transfer information and the target asset map, the transfer scope parsing module is specifically used for: Based on the target asset map, determine the reference transfer scope corresponding to the ownership transfer request of the first component; the reference transfer scope includes b related components; b is a positive integer less than or equal to a; Determine the b transfer constraint tags corresponding to the b associated components; Based on the b transfer constraint markers, determine c related components among the b related components that cannot be transferred individually; c is a positive integer less than or equal to b; Based on the target asset map and the b transfer constraint markers, determine d associated components that have associated transfers with the c associated components; d is a positive integer less than a, and the sum of c and d is less than or equal to a; The target transfer range is determined based on the b associated components and the d associated components.

4. The system as described in claim 3, characterized in that, In determining the reference transfer scope corresponding to the ownership transfer request of the first component based on the target asset map, the transfer scope parsing module is specifically used for: Determine the first component data corresponding to the first component ownership transfer request; Determine at least one map node in the target asset map corresponding to the data of the first component; For each of the at least one graph node, starting from that graph node, the target asset graph is traversed to obtain e graph nodes; e is an integer greater than or equal to b and less than or equal to a; the e graph nodes correspond to e associated components. Based on the a ownership information, the transferor's transfer rights for each of the e associated components are verified to obtain e transfer rights; each transfer right includes any of the following: can be transferred individually, or transfer is restricted; Based on the e transfer permissions, determine f related components that can be transferred individually from the e related components, and g related components whose transfer is restricted; where f and g are natural numbers, and f + g = e; Based on the f associated components and the g associated components, the b associated components are determined.

5. The system as described in claim 4, characterized in that, In determining the b associated components based on the f associated components and the g associated components, the transfer range parsing module is specifically used for: Determine the g ownership objects corresponding to the g associated components; Obtain g feedback messages from the g ownership objects in response to the request for transfer of ownership of the first component; each feedback message includes any one of the following: consent to transfer, disagreement with transfer; Based on the g feedback messages, determine h related components among the g related components that agree to the transfer; h is a natural number less than or equal to g, and h + f = b; Based on the h associated components and the f associated components, the b associated components are determined.

6. The system according to any one of claims 3-5, characterized in that, In determining, based on the target asset map and the b transfer constraint markers, the d associated components that have related transfers with the c associated components, the transfer scope parsing module is specifically used for: Identify c map nodes in the target asset map that correspond to the c associated components; For each of the c graph nodes, starting from that graph node, the target asset graph is traversed to obtain h graph nodes; h is a natural number less than a. Determine the h associated components corresponding to the h map nodes; The d associated components are determined based on the h associated components and the b transfer constraint tags.

7. The system according to any one of claims 1-5, characterized in that, The second transfer information includes: a request for the transfer of ownership of the second component; In the process of transferring ownership of the corresponding assets in the target asset data to the transferee based on the second transfer information and the target asset map, the ownership change module is specifically used for: Determine the second component data corresponding to the second component ownership transfer request; Identify i nodes in the target asset map that correspond to the data of the second component; i is a positive integer less than or equal to a; After obtaining the electronic signature confirmations from the transferor and the transferee regarding the second transfer information, the i ownership information corresponding to the i graph nodes is updated.

8. The system according to any one of claims 1-5, characterized in that, The system further includes: a distributed ownership evidence storage module; wherein: The ownership change module is also used to generate an ownership change record after the ownership of the corresponding component in the target asset data is changed to the transferee; The ownership distributed evidence storage module is used to upload the ownership change records to a preset blockchain network for storage.

9. The system as described in claim 8, characterized in that, The ownership distributed evidence storage module is also used to generate a graph change record when a graph node of the target asset graph changes, and upload the graph change record to the preset blockchain network for storage.

10. An asset management method, characterized in that, Applied to the system as described in any one of claims 1-9, the method comprises: The target asset data corresponding to the transferor is obtained through the asset graph modeling module; the target asset graph is determined based on the target asset data; the target asset graph is a directed attribute graph, which includes the graph nodes of the target main component and its related components corresponding to the target asset data, as well as directed edges representing the hierarchical subordinate relationship between components; each graph node carries the ownership information and transfer constraint mark of the corresponding component; The transfer scope analysis module obtains the first transfer information of the transferee regarding the target asset data; based on the first transfer information and the target asset map, the target transfer scope is determined. The transfer module determines second transfer information based on the target transfer scope; it obtains target feedback information from the transferee regarding the second transfer information; the target feedback information includes any one of the following: agreement to transfer, disagreement to transfer; When the target feedback information includes consent to transfer, the ownership change module, based on the second transfer information and the target asset map, changes the ownership of the corresponding components in the target asset data to the transferee.

Images