Mapping association method for digital assets and physical places in distributed environment

Abstract

The invention relates to a mapping association method for digital assets and physical places in a distributed environment, and the method comprises the steps: setting a local server in a physical place as a storage point of an anchoring place ID, and combining a dynamic association updating mechanism of a cloud server for the information change of network connection equipment, so as to achieve the mapping association of the digital assets and the physical places when the network environment of the physical place is changed. The stability and continuity of the place ID are kept, and the problem that the mapping relation between the digital assets and the physical place is interrupted due to the change of the place ID is avoided; meanwhile, based on the stable place ID, the terminal computer ID is generated in combination with the local unique identification information of the client terminal, thereby ensuring that the specific client terminal in the specific physical place is uniquely and accurately identified and positioned in the distributed environment. A reliable identification basis is provided for subsequent digital asset unified management, remote operation and maintenance, data analysis and other applications, and the management efficiency and the data accuracy are improved.

Description

Technical Field

[0001] The present invention relates to the technical field of computer network management, and in particular to a method for uniquely and stably mapping and associating digital assets with physical locations and internal terminals thereof in a distributed environment. Background Art

[0002] In modern IT management, especially in scenarios with a large number of dispersed terminals, such as chain internet cafes, distributed offices, and IoT device management, accurately and efficiently uniquely and persistently mapping each digital asset (such as terminal configuration, software license, operational data, etc.) to its corresponding physical entity (such as a specific physical location or a specific terminal device within that location) is the basis for effective remote monitoring, asset management, policy deployment, and troubleshooting.

[0003] However, in practice, establishing and maintaining such precise mappings faces many challenges: First, traditional location identification methods may rely on certain characteristics of the location's network environment, such as the router's IP address, MAC address, or specific network topology. However, in actual operations, these network parameters may change due to equipment replacement (such as router upgrades or faulty replacements), network configuration adjustments (such as subnet division and VLAN changes), or ISP dynamic IP allocation policies. Once these key location identification parameters change, the location identifier generated based on them will also change, disrupting the original mapping between digital assets and the physical location. This makes it impossible to trace historical data back to the correct location, resulting in asset statistics deviations and the inability to accurately distribute management policies to the target location, seriously affecting the continuity and accuracy of management.

[0004] Secondly, in large-scale deployed terminals, relying solely on hardware MAC addresses may encounter MAC address conflicts, especially in virtualized environments or when manually modified or when the MAC address changes due to network card replacement. The computer name, IP address, etc. may also change due to reasons such as reinstalling the system and reallocating the network. This results in the terminal computer identifier being unstable or lacking uniqueness globally, or the uniqueness within the location to which it belongs being difficult to guarantee. Therefore, accurate management of specific terminals will be difficult to achieve. Summary of the Invention

[0005] In order to solve the above problems, the present application provides a mapping association method between digital assets and physical places in a distributed environment that ensures continuous and accurate mapping between digital assets and physical entities.

[0006] To achieve the above objectives, the present application provides a method for mapping and associating digital assets with physical locations in a distributed environment. The method is performed by a system including a client on a terminal computer, a local server, and a cloud server, and includes the following steps: S1. When the client terminal does not hold a valid location ID, it collects the current network connection device information of the physical location where it is located and sends the current network connection device information to the cloud server. The current network connection device information includes at least the MAC address and gateway IP address of the router in the physical location; S2. The cloud server determines or generates a location ID corresponding to the physical location based on the received information about the current network connection device; S3. The cloud server sends the location ID to a local server deployed in the physical location. The local server stores and records the location ID as the anchor location ID of the physical location. S4. When the client terminal starts or needs to report information, it obtains the stored anchor location ID from the local server and recollects information about the current network connection device that represents its physical location; S5. The client terminal acquires the anchor location ID and re-collects the current network connection device information and sends it to the cloud server; S6. After the cloud server receives the anchor place ID and the re-collected current network connection device information, if the re-collected current network connection device information is inconsistent with the previously recorded network connection device information used to generate or determine the anchor place ID, updating the association between the anchor place ID and the new current network connection device information in the cloud server, but keeping the anchor place ID itself unchanged; S7. The cloud server generates a terminal computer ID of the client terminal based on the location ID determined or maintained in the previous step and the local unique identification information of the client terminal; S8. Use a combined identifier consisting of the site ID and the terminal computer ID to uniquely identify a specific client terminal in a specific physical site in the distributed environment.

[0007] Preferably, in step S2, the cloud server calculates and generates or determines the place ID based on the current network connection device information, specifically including: Combining the MAC address of the router and the IP address of the gateway to form a first characteristic character string; Performing a hash operation on the first characteristic character string to obtain a first hash value; The cloud server queries its database to see if there is a place ID associated with the first hash value: If so, determining that the associated location ID is the location ID of the current physical location; If it does not exist, a new place ID is generated, and the new place ID is associated with the first hash value and stored.

[0008] Preferably, in step S7, the local unique identification information of the client terminal includes at least one of a computer name of the client terminal, a MAC address of the client terminal, and an IP address of the client terminal, or a combination thereof.

[0009] Preferably, in step S7, the cloud server calculates and generates the terminal computer ID, specifically including: Combining the location ID, the computer name of the client terminal, the MAC address of the client terminal, and the IP address of the client terminal to form a second characteristic string; A hash operation is performed on the second characteristic character string to obtain a second hash value, and the second hash value is used as the terminal computer ID.

[0010] Preferably, in step S4, if the client terminal fails to obtain the anchor place ID from the local server, the client terminal executes step S1 to request the cloud server to determine the place ID.

[0011] Preferably, the local server is a server device deployed inside the physical location and located in the same local area network as the client terminal.

[0012] Preferably, it also includes: When the local server in the physical place is replaced or redeployed, it is allowed to assign the anchor place ID stored in the local server before the replacement to the new local server for inheritance through a preset management operation.

[0013] Preferably, the digital assets include but are not limited to the hardware configuration information and software installation list of the client terminal.

[0014] The mapping and association method for digital assets and physical places in a distributed environment designed in the present application, by establishing a local server in the physical place as a storage point for the anchor place ID, and combining the cloud server's dynamic association and update mechanism for changes in network connection device information, can maintain the stability and continuity of the place ID when the network environment of the physical place changes, thereby avoiding the problem of interruption of the mapping relationship between digital assets and physical places due to changes in the place identification; at the same time, based on the stable place ID, the terminal computer ID is generated in combination with the local unique identification information of the client terminal, ensuring the unique and accurate identification and positioning of a specific client terminal in a specific physical place in a distributed environment, providing a reliable identification basis for subsequent applications such as unified management of digital assets, remote operation and maintenance, and data analysis, thereby improving management efficiency and data accuracy. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 This is a flowchart of a method for mapping and associating digital assets with physical locations in a distributed environment provided by an embodiment of the present application. DETAILED DESCRIPTION

[0016] The preferred embodiments of the present application are described below in conjunction with the accompanying drawings. It should be understood that the preferred embodiments described herein are only used to illustrate and explain the present application and are not used to limit the present application.

[0017] like Figure 1 As shown, this embodiment describes a method for mapping and associating digital assets with physical locations in a distributed environment, which is performed by a system including a client on a terminal computer, a local server, and a cloud server. The local server is a server device deployed within the physical location and is located on the same local area network as the client terminal.

[0018] Specifically, the mapping association method mainly includes the following steps: S1. When the client terminal does not have a valid location ID, it collects the current network connection device information of the physical location where it is located and sends the current network connection device information to the cloud server.

[0019] Specifically, when a client on a terminal computer first starts up and attempts to establish communication with the cloud server, or when the client determines that it does not have a location ID or that the location ID it holds is invalid (for example, if the locally cached location ID has expired or verification fails), the client proactively collects network connection device information for its current physical location. Once collected, the client sends this network connection device information to the cloud server via the network as the basis for requesting identification or allocation of a location ID. In specific implementations, this current network connection device information includes at least the MAC address and gateway IP address of the router within the physical location.

[0020] S2. The cloud server determines or generates a location ID corresponding to the physical location based on the received current network connection device information. This location ID should be unique throughout the distributed system and is used to identify a specific physical location, such as a specific internet cafe.

[0021] In specific implementation, the cloud server calculates and generates or determines the place ID based on the current network connection device information, specifically including: combining the MAC address of the router and the gateway IP address to form a first feature string; performing a hash operation on the first feature string to obtain a first hash value; the cloud server queries its database whether there is a place ID associated with the first hash value.

[0022] If so, the associated place ID is determined to be the place ID of the current physical place. That is, if such an association is found and the place ID is valid, the cloud server determines that the existing place ID is the place ID of the physical place where the client is currently located.

[0023] If it does not exist, a new place ID is generated, and the new place ID is associated with the first hash value and stored. That is, if no association is found, or the associated place ID is invalid, it indicates that this is a new, unidentified physical place, or the network characteristics have completely changed and there is no local anchor ID reported. In this case, the cloud server will generate a new, globally unique place ID, for example, through database sequence auto-increment, UUID generation, etc., and then associate this newly generated place ID with the calculated first hash value, and store this association in the database for subsequent queries.

[0024] S3. The cloud server sends the venue ID to a local server deployed at the physical venue. The local server stores and records the venue ID as the anchor venue ID for the physical venue. This serves as a preferred source for subsequent clients to obtain venue IDs and as a stable credential for the venue's identity.

[0025] S4. When the client terminal is started or needs to report information, it retrieves the stored anchor location ID from the local server and recollects the current network connection device information representing the physical location. During subsequent operations, such as each time the client terminal is started, or before reporting status or performing an operation to the cloud server, the client will first attempt to retrieve the previously stored anchor location ID from the local server at its physical location. Regardless of whether the anchor location ID is successfully retrieved, the client will recollect the network connection device information for the current physical location.

[0026] In a specific implementation, if the client terminal fails to obtain the anchor place ID from the local server, the client terminal executes step S1 to request the cloud server to determine the place ID.

[0027] S5. The client terminal sends the acquired anchor location ID and the re-collected current network connection device information to the cloud server.

[0028] S6. After the cloud server receives the anchor place ID and the re-collected current network connection device information, if the re-collected current network connection device information is inconsistent with the previously recorded network connection device information used to generate or determine the anchor place ID, the cloud server updates the association between the anchor place ID and the new current network connection device information in the cloud server, while keeping the anchor place ID unchanged. Specifically, if the client reports a valid anchor place ID, the cloud server will use this anchor place ID as the basis for identifying the physical place. At this time, if the re-collected current network connection device information reported with it, such as the new router MAC or gateway IP address, is inconsistent with the original network connection device information associated with the anchor place ID recorded in the cloud server database, indicating that the network equipment at the physical place may have been replaced or the configuration has changed, the cloud server will update the corresponding association between the anchor place ID and the new current network connection device information in its database. Importantly, during this update process, the place ID itself remains unchanged, thereby ensuring the continuity and stability of place identification, even if the network hardware changes.

[0029] S7. The cloud server generates a terminal computer ID for the client terminal based on the location ID determined or maintained in the previous step and the local unique identification information of the client terminal. In this embodiment, the local unique identification information of the client terminal includes at least one of the client terminal's computer name, the client terminal's MAC address, and the client terminal's IP address, or a combination thereof. In environments such as internet cafes, computer names and IP addresses are typically fixed after diskless systems are deployed to facilitate statistics.

[0030] In a specific implementation, the cloud server calculates and generates the terminal computer ID by combining the location ID, the client terminal's computer name, the client terminal's MAC address, and the client terminal's IP address to form a second characteristic string; performing a hash operation on the second characteristic string to obtain a second hash value, and using the second hash value as the terminal computer ID. The cloud server will store the correspondence between this terminal computer ID and the original information, or directly use the hash value as the ID.

[0031] S8. Use a combined identifier consisting of the location ID and the terminal computer ID to uniquely identify a specific client terminal in a specific physical location in the distributed environment. That is, by combining the terminal computer ID generated in step S7 with the location ID to which it belongs, for example, by splicing the two or associating them through specific rules, a combined identifier is formed. This combined identifier can adopt a format such as "location ID-terminal computer ID" to uniquely identify the specific client terminal in a specific physical location in the entire distributed environment. Based on this unique identification, the system can perform subsequent digital asset management, remote operation, data statistics, etc. In this embodiment, the digital assets include but are not limited to the hardware configuration information and software installation list of the client terminal.

[0032] In some embodiments, when a local server within the physical location is replaced or redeployed, the anchor location ID stored by the local server before the replacement is assigned to the new local server for inheritance through a preset management operation. This allows a system administrator to manually assign and migrate the anchor location ID stored and recorded by the local server before the replacement to the new or redeployed local server for continued use through a management interface or preset management operation, such as providing an input interface when installing new local server software. This allows the location's identity to be inherited even if the local server is replaced.

[0033] The mapping and association method between digital assets and physical places in a distributed environment provided by the embodiment of the present application, by establishing a local server in the physical place as a storage point for the anchor place ID, and combining the cloud server's dynamic association and update mechanism for changes in network connection device information, can maintain the stability and continuity of the place ID when the network environment of the physical place changes, thereby avoiding the problem of interruption of the mapping relationship between digital assets and physical places due to changes in the place identification; at the same time, based on the stable place ID, combined with the local unique identification information of the client terminal, a terminal computer ID is generated, ensuring the unique and accurate identification and positioning of a specific client terminal in a specific physical place in a distributed environment, providing a reliable identification basis for subsequent applications such as unified management of digital assets, remote operation and maintenance, and data analysis, thereby improving management efficiency and data accuracy.

[0034] In the description of this application, it should be noted that the terms "vertical", "up", "down", "horizontal", etc. indicate orientations or positional relationships based on the orientations or positional relationships shown in the accompanying drawings. They are only for the convenience of describing this application and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation. Therefore, they cannot be understood as limitations on this application.

[0035] It should also be noted that, in the description of this application, unless otherwise expressly specified or limited, the terms "disposed," "installed," "connected," and "connected" should be understood in a broad sense. For example, they can refer to fixed connections, detachable connections, or integral connections; they can refer to mechanical connections or electrical connections; they can refer to direct connections or indirect connections through an intermediate medium; and they can refer to internal connections between two components. Those skilled in the art will understand the specific meanings of the above terms in this application based on specific circumstances.

[0036] Finally, it should be noted that the above description is merely a preferred embodiment of the present application and is not intended to limit the present application. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art may still modify the technical solutions described in the aforementioned embodiments or substitute equivalents for some of the technical features therein. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included within the scope of protection of the present application.

Claims

1. A method for mapping and associating digital assets with physical locations in a distributed environment, the method being executed by a system comprising a client on a terminal computer, a local server, and a cloud server, characterized in that: The following steps are involved: S1. When the client terminal does not hold a valid location ID, it collects the current network connection device information of the physical location where it is located and sends the current network connection device information to the cloud server. The current network connection device information includes at least the MAC address and gateway IP address of the router in the physical location; S2. The cloud server determines or generates a location ID corresponding to the physical location based on the received information about the current network connection device; S3. The cloud server sends the location ID to a local server deployed in the physical location. The local server stores and records the location ID as the anchor location ID of the physical location. S4. When the client terminal starts or needs to report information, it obtains the stored anchor location ID from the local server and recollects information about the current network connection device that represents its physical location; S5. The client terminal acquires the anchor location ID and re-collects the current network connection device information and sends it to the cloud server; S6. After the cloud server receives the anchor place ID and the re-collected current network connection device information, if the re-collected current network connection device information is inconsistent with the previously recorded network connection device information used to generate or determine the anchor place ID, updating the association between the anchor place ID and the new current network connection device information in the cloud server, but keeping the anchor place ID itself unchanged; S7. The cloud server generates a terminal computer ID of the client terminal based on the location ID determined or maintained in the previous step and the local unique identification information of the client terminal; S8. Use a combined identifier consisting of the site ID and the terminal computer ID to uniquely identify a specific client terminal in a specific physical site in the distributed environment.

2. The method for mapping and associating digital assets with physical locations in a distributed environment according to claim 1, characterized in that: In step S2, the cloud server calculates and generates or determines the location ID based on the current network connection device information, specifically including: Combining the MAC address of the router and the IP address of the gateway to form a first characteristic character string; Performing a hash operation on the first characteristic character string to obtain a first hash value; The cloud server queries its database to see if there is a place ID associated with the first hash value: If so, determining that the associated location ID is the location ID of the current physical location; If it does not exist, a new place ID is generated, and the new place ID is associated with the first hash value and stored.

3. The method for mapping and associating digital assets with physical locations in a distributed environment according to claim 1, characterized in that: In step S7, the local unique identification information of the client terminal includes at least one of a computer name of the client terminal, a MAC address of the client terminal, and an IP address of the client terminal, or a combination thereof.

4. The method for mapping and associating digital assets with physical locations in a distributed environment according to claim 3, characterized in that: In step S7, the cloud server calculates and generates the terminal computer ID, specifically including: Combining the location ID, the computer name of the client terminal, the MAC address of the client terminal, and the IP address of the client terminal to form a second characteristic string; A hash operation is performed on the second characteristic character string to obtain a second hash value, and the second hash value is used as the terminal computer ID.

5. The method for mapping and associating digital assets with physical locations in a distributed environment according to claim 1, characterized in that: In step S4, if the client terminal fails to obtain the anchor place ID from the local server, the client terminal executes step S1 to request the cloud server to determine the place ID.

6. The method for mapping and associating digital assets with physical locations in a distributed environment according to claim 1, characterized in that: The local server is a server device deployed inside the physical location and located in the same local area network as the client terminal.

7. The method for mapping and associating digital assets with physical locations in a distributed environment according to any one of claims 1 to 6, characterized in that: Also includes: When the local server in the physical place is replaced or redeployed, it is allowed to assign the anchor place ID stored in the local server before the replacement to the new local server for inheritance through a preset management operation.

8. The method for mapping and associating digital assets with physical locations in a distributed environment according to claim 1, characterized in that: The digital assets include but are not limited to the hardware configuration information and software installation list of the client terminal.

Images