A tower site intelligent matching method, device, equipment and medium
By employing encryption and multi-party secure computation technologies, the problems of privacy and low resource utilization in communication infrastructure site matching are solved, achieving efficient and secure site matching and supporting the real-time needs of low-altitude economic services.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- CHINA TOWER CO LTD
- Filing Date
- 2026-03-09
- Publication Date
- 2026-07-24
AI Technical Summary
Existing communication infrastructure site matching schemes suffer from issues related to privacy, intelligence, resource utilization, and scenario adaptability, failing to meet the high security and real-time requirements of low-altitude economic services.
By acquiring encrypted deployment requirement packages and capability profiles of tower sites, multi-party secure computation (MPC) technology is used for matching, combined with the GISHASH spatial matching algorithm, to make the location information of the demand party invisible, thereby shortening the response time and improving the matching accuracy.
It reduces the risk of data leakage, improves matching efficiency and accuracy, supports high-concurrency requests, and meets the needs of low-altitude economic operations.
Smart Images

Figure CN122458034A_ABST
Abstract
Description
Technical Field
[0001] This application belongs to the field of data processing technology, and specifically relates to a method, device, equipment and medium for intelligent matching of tower sites. Background Technology
[0002] In recent years, the low-altitude economy has developed rapidly, with emerging businesses such as drone logistics, low-altitude communications, and smart cities driving a surge in demand for communication infrastructure. Communication infrastructure service providers need to efficiently respond to customer needs for mounting communication equipment, video conferencing services, or computing power services on base stations.
[0003] Currently, traditional communication infrastructure site matching solutions require customers to provide precise location information, which poses a risk of data leakage and does not meet the high data security requirements of low-altitude economic services. Furthermore, manual site selection relies on experience-based judgment, which is not only slow in response but also difficult to meet the real-time requirements of low-altitude economic services.
[0004] Therefore, there is an urgent need for a technical solution that can effectively address the issues of privacy, intelligence, resource utilization, and scenario adaptability in existing technologies. Summary of the Invention
[0005] This application provides a method, apparatus, device, and medium for intelligent matching of tower sites, which can solve the technical problems of poor privacy, intelligence, resource utilization, and scenario adaptability in the existing communication infrastructure site matching process.
[0006] To achieve the above objectives, this application provides the following technical solution: A method for intelligent matching of tower sites includes: Obtain the encrypted deployment requirements package and build a capability profile for each tower site; Based on the deployment requirement package and the capability profile, several successfully matched target tower sites and their drift coordinates are obtained.
[0007] Furthermore, in one embodiment, the deployment requirements package includes: geographical scope, nest type, hardware capability hard constraints, and compatibility requirements.
[0008] Furthermore, in one embodiment, the capability profile includes: the nest's physical and infrastructure capabilities, network communication capabilities, environmental and airspace capabilities, operational service capabilities, and dynamic update capabilities.
[0009] Furthermore, in one embodiment, obtaining a plurality of successfully matched target tower sites based on the deployment requirement package and the capability profile includes: Based on the comparison and filtering of the data in the capability profile and the data in the deployment requirement package, several tower sites that are initially qualified in terms of capability are obtained. Select any unselected tower site from a number of tower sites that have initially met the requirements, and denote it as the initial target tower site. Calculate the encrypted distance between the initial target tower site and the encrypted fuzzy center point; If the encrypted distance is less than or equal to the service radius of the tower site, then the initial target tower site is determined to be a successfully matched target tower site, and the drift coordinates of the successfully matched target tower site are output. This process continues until all qualified tower sites have been selected, resulting in several successfully matched target tower sites and their drift coordinates.
[0010] Further, in one embodiment, the comparison and filtering based on the data in the capability profile and the data in the deployment requirement package to obtain several tower sites that are initially qualified include: For any unselected tower site's capability profile, check whether the power supply capacity in the capability profile is greater than or equal to the minimum power supply in the deployment requirement package; Detect whether the available platform area in the capability profile is greater than or equal to the minimum platform area in the deployment requirement package; Check whether the list of supported models in the deployment requirement package is a subset of the list of verified supported models in the capability profile; If the power supply capacity in the capability profile is greater than or equal to the minimum power supply in the deployment requirement package, and the available platform area in the capability profile is greater than or equal to the minimum platform area in the deployment requirement package, and the list of supported models in the deployment requirement package is a subset of the list of verified supported models in the capability profile, then the tower site corresponding to the capability profile is determined to be a tower site with preliminary capability qualification. Until all tower sites have had their capability profiles selected, a number of tower sites that have initially met the capability requirements have been obtained.
[0011] Further, in one embodiment, before outputting the drift coordinates of the successfully matched target tower site, the following steps are included: The real coordinates of the successfully matched target tower site are randomly offset geographically to obtain the drift coordinates of the successfully matched target tower site.
[0012] Furthermore, in one embodiment, the method further includes: Calculate the first hash value of the deployment requirement package, the second hash value of the capability profile, and the third hash value of the target tower site ID; Write the first hash value, the second hash value, and the third hash value into the blockchain.
[0013] Based on the same inventive concept, this application also provides a smart matching device for iron tower sites, the device comprising: The information acquisition module is configured to acquire the encrypted deployment requirement package and build a capability profile for each tower site. The tower site matching module is configured to obtain several successfully matched target tower sites and their drift coordinates based on the deployment requirement package and the capability profile.
[0014] Based on the same inventive concept, this application also provides an electronic device, including: a memory and a processor; the processor is used to read and execute a computer program stored in the memory to implement the steps of the aforementioned intelligent matching method for iron tower sites.
[0015] Based on the same inventive concept, this application also provides a computer storage medium storing computer-executable instructions, which, when executed, implement the steps of the aforementioned intelligent matching method for iron tower sites.
[0016] Compared with the prior art, this application has the following advantages: By using Multi-Party Secure Computation (MPC) technology, the location information of the demand side is made "usable but not visible," which reduces the risk of data leakage compared to traditional methods. Furthermore, the spatial matching algorithm based on GISHASH shortens the response time of a single site query to within 10 seconds, improves the matching accuracy, and increases efficiency several times compared to manual review. It supports high-concurrency requests and supports low-altitude economic needs such as communication equipment, video link services, and computing power services.
[0017] This application solves the technical problems of poor privacy, intelligence, resource utilization and scenario adaptability in the existing communication infrastructure site matching process.
[0018] Other features and advantages of this application will be set forth in the description which follows, and will be apparent in part from the description, or may be learned by practicing the application. The objectives and other advantages of this application may be realized and obtained by means of the structures pointed out in the description, claims and drawings. Attached Figure Description
[0019] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0020] Figure 1A flowchart illustrating the method provided in the embodiments of this application; Figure 2a This is a schematic diagram illustrating the process of constructing and deploying a requirement package according to an embodiment of this application; Figure 2b This is a schematic diagram illustrating the process of constructing a tower capability profile according to an embodiment of this application; Figure 2c This is a schematic diagram of the capability hard constraint filtering process according to an embodiment of this application; Figure 2d This is a schematic diagram of the encrypted space reachability verification process according to an embodiment of this application; Figure 2e This is a schematic diagram of the real-time evidence storage process according to an embodiment of this application; Figure 3 for Figure 1 A detailed flowchart of step S20; Figure 4 This is a schematic diagram of the functional modules of an embodiment of the intelligent matching device for iron tower sites according to this application; Figure 5 This is a schematic diagram of the structure of an electronic device according to an embodiment of this application. Detailed Implementation
[0021] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0022] To address the shortcomings of existing technologies, refer to Figure 1 This application discloses a method for intelligent matching of tower sites, including: Step S10: Obtain the encrypted deployment requirement package and construct a capability profile for each tower site; In this embodiment, refer to Figure 2a Obtain the structured and encrypted deployment requirements package submitted by the operator. The deployment requirements package includes: geographical scope, nesting type, hardware capability constraints, and compatibility requirements.
[0023] Geographic range: Defined by a “fuzzy center point” (such as a coordinate with a slight GeoHash offset) and a “service radius” (such as 5km), without revealing the precise target center.
[0024] Nest type: Select from a predefined enumeration list, such as LOGISTICS, INSPECTION, EMERGENCY, and UAM (Urban Air Traffic). The nest type of the drone determines the preference weight for subsequent matching.
[0025] Hardware capability hard constraints: clearly quantified minimum requirements, including: minimum power supply (kW), minimum platform area (㎡), and minimum network bandwidth (Mbps).
[0026] Compatibility requirements: List of supported models (e.g., ["DJI M3D", "EH216-S"]), and optional requirements such as: whether redundant backup power supply is required, and whether an edge computing server is required.
[0027] Before leaving the operator's terminal, the aforementioned structured deployment requirement package has its sensitive fields (especially the "fuzzy center point") encrypted using the Secure Multi-Party Computation (SMPC) protocol to generate an encrypted deployment requirement package Enc(D). Then, the encrypted deployment requirement package Enc(D) is submitted to the platform's MPC node cluster.
[0028] Reference Figure 2b The platform establishes and maintains a structured capability profile (T) for each tower site. This capability profile focuses on the engineering parameters of the tower deployment, mainly including: the physical and infrastructure capabilities of the tower, network communication capabilities, environmental and airspace capabilities, operational service capabilities, and dynamic update capabilities.
[0029] The physical and infrastructure capabilities of the hive include: platform load capacity (tons), available platform area (㎡), power supply capacity and protection level (kW), and lightning protection level.
[0030] Network communication capabilities: including access type (5G / fiber), measured uplink bandwidth (Mbps) and network latency (ms).
[0031] Environmental and airspace capabilities: including 3D point cloud data of surrounding obstacles (from LiDAR scanning or oblique photogrammetry modeling), historical meteorological data (annual average wind speed, number of rainy days), and electromagnetic interference spectrum measurements.
[0032] Operational service capabilities: This includes a list of verified supported drone models, the theoretical maximum number of times a drone can be landed, and whether edge servers have been deployed.
[0033] Dynamic update capability: The profile data is not static. The capability profile of the tower site is updated by updating network capabilities, environmental factors, and the list of supported models. Among them, network capabilities and environmental factors (such as electromagnetic interference) are updated periodically through IoT sensors; the list of supported models is updated after each successful deployment of a new model.
[0034] Furthermore, in one embodiment, the capability profile can be extended to include dynamic factors such as weather and airspace approval status.
[0035] Step S20: Based on the deployment requirement package and the capability profile, obtain several successfully matched target tower sites and their drift coordinates.
[0036] In some specific embodiments, reference is made to Figure 3 Step S20 includes: Step S201: Based on the data in the capability profile, compare and filter the data in the deployment requirement package to obtain a number of tower sites that are initially qualified in terms of capability. In some specific embodiments, step S201 includes: For any unselected tower site's capability profile, check whether the power supply capacity in the capability profile is greater than or equal to the minimum power supply in the deployment requirement package; Detect whether the available platform area in the capability profile is greater than or equal to the minimum platform area in the deployment requirement package; Check whether the list of supported models in the deployment requirement package is a subset of the list of verified supported models in the capability profile; If the power supply capacity in the capability profile is greater than or equal to the minimum power supply in the deployment requirement package, and the available platform area in the capability profile is greater than or equal to the minimum platform area in the deployment requirement package, and the list of supported models in the deployment requirement package is a subset of the list of verified supported models in the capability profile, then the tower site corresponding to the capability profile is determined to be a tower site with preliminary capability qualification. Until all tower sites have had their capability profiles selected, a number of tower sites that have initially met the capability requirements have been obtained.
[0037] Step S202: Select any unselected tower site from a number of tower sites that have initially met the requirements, and record it as the initial target tower site. Step S203: Calculate the encrypted distance between the initial target tower site and the encrypted fuzzy center point; Step S204: If the encrypted distance is less than or equal to the service radius of the tower site, then the initial target tower site is determined to be a successfully matched target tower site, and the drift coordinates of the successfully matched target tower site are output. Step S205 continues until all qualified tower sites have been selected, resulting in several successfully matched target tower sites and their drift coordinates.
[0038] In this embodiment, based on the encrypted deployment requirement package and the capability profile of the tower site, the platform's MPC secure computing environment is used to obtain several successfully matched target tower sites and their drift coordinates. The entire process does not disclose the precise location of the requirement or the precise coordinates of the tower.
[0039] Specifically, refer to Figure 2c Phase 1: Hard constraint filtering of capabilities (pure attribute matching, no need to decrypt location).
[0040] Principle: While the system is encrypted, the data in the encrypted deployment requirement package Enc(D) is directly compared with the data in the capability profile Profile(T). This stage only involves numerical comparison and set inclusion checks, as follows: The platform's MPC nodes iterate through the capability profiles of each tower site. For each tower site's capability profile (Profile(T), the following are calculated and determined: whether the power supply capacity in the capability profile is greater than or equal to the minimum power supply in the deployment requirement package; whether the available platform area in the capability profile is greater than or equal to the minimum platform area in the deployment requirement package; and whether the list of supported models in the deployment requirement package is a subset of the list of verified supported models in the capability profile.
[0041] All towers that do not meet any of the hard constraints are eliminated, and a preliminary list of tower sites with preliminary capability is generated (List_Capable). Specifically, if the power supply capacity in the capability profile is greater than or equal to the minimum power supply in the deployment requirement package, and the available platform area in the capability profile is greater than or equal to the minimum platform area in the deployment requirement package, and the list of supported models in the deployment requirement package is a subset of the list of verified supported models in the capability profile, then the tower site corresponding to the capability profile is determined to be a tower site with preliminary capability. This process continues until the capability profiles of all tower sites have been selected, resulting in a number of tower sites with preliminary capability.
[0042] Reference Figure 2d Phase Two: Encrypted Space Reachability Verification (MPC Secure Distance Calculation).
[0043] Input: The list of tower sites that are initially qualified in the List_Capable, and their encrypted precise coordinates Enc(Location_T); the encrypted fuzzy center point Enc(Center_D) and service radius Radius_D in the encrypted deployment requirement package Enc(D).
[0044] Core computation: Under the protection of the MPC protocol, any unselected tower site is chosen from a pool of preliminarily qualified tower sites, and the encrypted distance Enc(Dist) between it and the encrypted obfuscated center point is securely calculated. The calculation employs an encrypted version of the algorithm, such as Euclidean distance or spherical distance.
[0045] Security comparison: Continuing in the encrypted state, determine whether the encrypted distance Enc(Dist) is less than or equal to the service radius Radius_D. This comparison is implemented using an encrypted comparison protocol (such as the comparison circuit in the GSW or CKKS scheme).
[0046] Secondary anonymization: For tower sites determined to be "reachable," i.e., tower sites whose encrypted distance Enc(Dist) is less than or equal to the service radius Radius_D, a random geographical offset is applied to the coordinates before outputting their true coordinates (e.g., superimposing a random vector within the range [-50m, +50m] onto the true coordinates), generating "drift coordinates." Furthermore, differential privacy can be used to replace coordinate drift.
[0047] Result: Output the successfully matched target tower sites and their drift coordinates. This process continues until all tower sites in the list List_Capable, which represents the initial qualified tower sites, have been selected. The result is a list List_Matched of successfully matched tower sites, containing their drift coordinates and complete capability profile (T) information (excluding precise coordinates).
[0048] Furthermore, in one embodiment, federated learning can be used instead of MPC to achieve privacy-preserving matching. The matching engine can integrate reinforcement learning to achieve long-term load optimization.
[0049] In this embodiment, an encrypted deployment requirement package is obtained, and a capability profile for each tower site is constructed. Based on the deployment requirement package and the capability profile, several successfully matched target tower sites and their drift coordinates are obtained. Through multi-party secure computation (MPC) technology, the location information of the requesting party is made "usable but invisible," reducing the risk of data leakage compared to traditional methods. Furthermore, the spatial matching algorithm based on GISHASH shortens the response time for a single site query to within 10 seconds, improving matching accuracy and increasing efficiency several times compared to manual review. It supports high-concurrency requests and addresses the low-altitude economic needs of communication equipment, video conferencing services, and computing power services. This embodiment solves the technical problems of poor privacy, intelligence, resource utilization, and scenario adaptability in the existing communication infrastructure site matching process.
[0050] Furthermore, in one embodiment, the method further includes: Calculate the first hash value of the deployment requirement package, the second hash value of the capability profile, and the third hash value of the target tower site ID; Write the first hash value, the second hash value, and the third hash value into the blockchain.
[0051] In this embodiment, refer to Figure 2e Summary information of key steps is stored in real time to ensure the compliance and auditability of the process. The stored information includes: submission of the encrypted deployment requirement package Enc(D), invocation of the capability profile (Profile(T)) for each tower site, filtering of hard constraints in phase one, verification of reachability in the encrypted space in phase two, and final manual review and confirmation by the operator. The hash value of the current state (such as the hash of the requirement package or the hash of the site ID list) is recorded on the blockchain. This blockchain-based notarization covers the entire lifecycle, forming an immutable site selection operation log. Any party (operator, platform provider, regulator) can verify the integrity and consistency of the entire site selection decision-making process afterward, meeting regulatory requirements for data security and process auditing, and ensuring the traceability of the operation.
[0052] Based on the same inventive concept, this application also provides a smart matching device for iron tower sites.
[0053] In one embodiment, reference is made to Figure 4 , Figure 4 This is a functional module diagram of an embodiment of the intelligent matching device for iron tower sites according to this application. Figure 4 As shown, the intelligent matching device for tower sites includes: The information acquisition module 10 is configured to acquire the encrypted deployment requirement package and build a capability profile for each tower site. The tower site matching module 20 is configured to obtain several successfully matched target tower sites and their drift coordinates based on the deployment requirement package and the capability profile.
[0054] Furthermore, in one embodiment, the deployment requirements package includes: geographical scope, nest type, hardware capability hard constraints, and compatibility requirements.
[0055] Furthermore, in one embodiment, the capability profile includes: the nest's physical and infrastructure capabilities, network communication capabilities, environmental and airspace capabilities, operational service capabilities, and dynamic update capabilities.
[0056] Furthermore, in one embodiment, the tower site matching module 20 is configured to: Based on the comparison and filtering of the data in the capability profile and the data in the deployment requirement package, several tower sites that are initially qualified in terms of capability are obtained. Select any unselected tower site from a number of tower sites that have initially met the requirements, and denote it as the initial target tower site. Calculate the encrypted distance between the initial target tower site and the encrypted fuzzy center point; If the encrypted distance is less than or equal to the service radius of the tower site, then the initial target tower site is determined to be a successfully matched target tower site, and the drift coordinates of the successfully matched target tower site are output. This process continues until all qualified tower sites have been selected, resulting in several successfully matched target tower sites and their drift coordinates.
[0057] Furthermore, in one embodiment, the tower site matching module 20 is configured to: For any unselected tower site's capability profile, check whether the power supply capacity in the capability profile is greater than or equal to the minimum power supply in the deployment requirement package; Detect whether the available platform area in the capability profile is greater than or equal to the minimum platform area in the deployment requirement package; Check whether the list of supported models in the deployment requirement package is a subset of the list of verified supported models in the capability profile; If the power supply capacity in the capability profile is greater than or equal to the minimum power supply in the deployment requirement package, and the available platform area in the capability profile is greater than or equal to the minimum platform area in the deployment requirement package, and the list of supported models in the deployment requirement package is a subset of the list of verified supported models in the capability profile, then the tower site corresponding to the capability profile is determined to be a tower site with preliminary capability qualification. Until all tower sites have had their capability profiles selected, a number of tower sites that have initially met the capability requirements have been obtained.
[0058] Furthermore, in one embodiment, the tower site matching module 20 is configured to: The real coordinates of the successfully matched target tower site are randomly offset geographically to obtain the drift coordinates of the successfully matched target tower site.
[0059] Optionally, in one embodiment, the evidence storage module of the intelligent matching device for tower sites is configured to: Calculate the first hash value of the deployment requirement package, the second hash value of the capability profile, and the third hash value of the target tower site ID; Write the first hash value, the second hash value, and the third hash value into the blockchain.
[0060] The functions of each module in the above-mentioned intelligent tower site matching device correspond to the steps in the above-mentioned intelligent tower site matching method embodiment, and their functions and implementation processes will not be described in detail here.
[0061] Based on the same inventive concept, embodiments of this application also provide an electronic device, the structure of which is as follows: Figure 5 As shown, it includes: a memory and a processor, wherein the processor is used to read and execute the computer program stored in the memory to implement the aforementioned intelligent matching method for iron tower sites.
[0062] Based on the same inventive concept, this application also provides a computer storage medium storing computer-executable instructions, which, when executed, implement the aforementioned intelligent matching method for iron tower sites.
[0063] Finally, it should be noted that while some processes described in the embodiments of this application include multiple operations or steps that appear in a specific order, it should be understood that these operations or steps may not be executed in the order they appear in the embodiments of this application, or may be executed in parallel. The sequence number of the operation is only used to distinguish different operations, and the sequence number itself does not represent any execution order. In addition, these processes may include more or fewer operations, and these operations or steps may be executed sequentially or in parallel, and these operations or steps may be combined.
[0064] Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.
Claims
1. A method for intelligent matching of tower sites, characterized in that, include: Obtain the encrypted deployment requirements package and build a capability profile for each tower site; Based on the deployment requirement package and the capability profile, several successfully matched target tower sites and their drift coordinates are obtained.
2. The method according to claim 1, characterized in that, The deployment requirements package includes: geographical scope, nest type, hardware capability constraints, and compatibility requirements.
3. The method according to claim 1, characterized in that, The capability profile includes: the nest's physical and infrastructure capabilities, network communication capabilities, environmental and airspace capabilities, operational service capabilities, and dynamic update capabilities.
4. The method according to any one of claims 1 to 3, characterized in that, Based on the deployment requirement package and the capability profile, several successfully matched target tower sites are obtained, including: Based on the comparison and filtering of the data in the capability profile and the data in the deployment requirement package, several tower sites that are initially qualified in terms of capability are obtained. Select any unselected tower site from a number of tower sites that have initially met the requirements, and denote it as the initial target tower site. Calculate the encrypted distance between the initial target tower site and the encrypted fuzzy center point; If the encrypted distance is less than or equal to the service radius of the tower site, then the initial target tower site is determined to be a successfully matched target tower site, and the drift coordinates of the successfully matched target tower site are output. This process continues until all qualified tower sites have been selected, resulting in several successfully matched target tower sites and their drift coordinates.
5. The method according to claim 4, characterized in that, The data in the capability profile is compared and filtered with the data in the deployment requirement package to obtain several tower sites that are initially qualified, including: For any unselected tower site's capability profile, check whether the power supply capacity in the capability profile is greater than or equal to the minimum power supply in the deployment requirement package; Detect whether the available platform area in the capability profile is greater than or equal to the minimum platform area in the deployment requirement package; Check whether the list of supported models in the deployment requirement package is a subset of the list of verified supported models in the capability profile; If the power supply capacity in the capability profile is greater than or equal to the minimum power supply in the deployment requirement package, and the available platform area in the capability profile is greater than or equal to the minimum platform area in the deployment requirement package, and the list of supported models in the deployment requirement package is a subset of the list of verified supported models in the capability profile, then the tower site corresponding to the capability profile is determined to be a tower site with preliminary capability qualification. Until all tower sites have had their capability profiles selected, a number of tower sites that have initially met the capability requirements have been obtained.
6. The method according to claim 4, characterized in that, Before outputting the drift coordinates of the successfully matched target tower site, the process includes: The real coordinates of the successfully matched target tower site are randomly offset geographically to obtain the drift coordinates of the successfully matched target tower site.
7. The method according to claim 1, characterized in that, The method further includes: Calculate the first hash value of the deployment requirement package, the second hash value of the capability profile, and the third hash value of the target tower site ID; Write the first hash value, the second hash value, and the third hash value into the blockchain.
8. A smart matching device for iron tower sites, characterized in that, The device includes: The information acquisition module is configured to acquire the encrypted deployment requirement package and build a capability profile for each tower site. The tower site matching module is configured to obtain several successfully matched target tower sites and their drift coordinates based on the deployment requirement package and the capability profile.
9. An electronic device, characterized in that, include: Memory, processor; The processor is configured to read and execute the computer program stored in the memory to implement the steps of the intelligent matching method for iron tower sites as described in any one of claims 1-7.
10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed, implement the steps of the intelligent matching method for iron tower sites as described in any one of claims 1-7.