Internet of Things equipment network planning method based on architectural space topology

Abstract

The invention belongs to the field of computer networks, and particularly relates to an Internet of Things equipment network planning method based on building space topology, which comprises the following steps: acquiring building space structure information and equipment deployment plan information, analyzing the total number of equipment and the total number of buildings to determine a two-layer or three-layer network hierarchical architecture, and generating a network topology structure; analyzing equipment density based on the three-dimensional equipment matrix, and automatically dividing equipment into a plurality of VLANs in combination with a preset broadcast domain threshold according to spatial position information and / or equipment types; based on the building number, the floor number and the room number in the spatial topology tree, generating an IP address with spatial semantics for each device; based on the number of the devices, the bandwidth requirements and the network topology structure, the specification and the number of the switches are determined; and generating a complete network deployment scheme comprising a network topological graph, a VLAN configuration table, an IP address allocation table, a bill of materials and a switch configuration script. According to the scheme, automatic planning of the network is realized.

Description

Technical Field

[0001] This application relates to the field of computer network technology, and specifically to a method for planning Internet of Things (IoT) device networks based on building spatial topology. Background Technology

[0002] With the rapid development and widespread application of IoT technology, smart communities, smart parks, smart hospitals, and smart campuses have become important carriers for digital transformation. These scenarios typically require the deployment of a large number of IoT terminal devices, including but not limited to access control devices, video surveillance equipment, medical intercom systems, environmental sensors, and smart healthcare terminals. For example, in a medium-sized smart community or hospital campus, the number of various IoT devices deployed can reach several thousand, widely distributed across multiple buildings, floors, and numerous individual rooms or functional areas.

[0003] As the infrastructure supporting the stable operation of IoT systems, the quality of network planning directly determines the reliability, performance, and long-term maintainability of the entire system. However, in current practical engineering project implementations, due to the lack of systematic, automated network planning methods closely integrated with physical space, the following typical problems commonly exist: Broadcast storm problem: In scenarios with dense device deployment, if the broadcast domain is too large, broadcast packets generated by Address Resolution Protocol (ARP) broadcasts, Dynamic Host Configuration Protocol (DHCP) requests, etc., will flood the network. For example, in a single Virtual Local Area Network (VLAN) containing more than 2,000 devices, every time a new device comes online or performs an address lookup, massive amounts of broadcast traffic will be generated, which can easily lead to network link congestion, switch overload, and in severe cases, even partial or complete network paralysis.

[0004] IP address conflicts and management chaos: Traditional IP address allocation relies heavily on manual planning and recording by network engineers. In projects with a large number of devices, long deployment cycles, and potential phased implementation, problems such as incomplete IP address allocation records, chaotic planning, and duplicate allocations are prone to occur. Address conflicts will directly lead to devices failing to register and go online or communication interruptions, and fault localization will be difficult.

[0005] Network connectivity issues: Due to reasons such as VLAN segmentation failing to adequately reflect the physical layout or business logic, incorrect Layer 3 routing configurations, and improper configuration of switch port operating modes and VLAN membership relationships, communication failures frequently occur between devices or between devices and servers. Troubleshooting these issues is cumbersome and severely impacts project delivery schedules and subsequent maintenance efficiency.

[0006] The problem of inefficient planning and deployment: Traditional network planning methods rely entirely on the manual experience of senior network engineers. Engineers need to repeatedly study building floor plans, manually design the physical and logical topology of the network, divide VLANs, plan IP address ranges, and select and configure network devices. The entire process is time-consuming, labor-intensive, and prone to configuration errors due to human oversight, making it difficult to ensure the consistency and standardization of the solution.

[0007] Currently, network management technologies and related research in the industry mainly focus on the post-construction management of existing networks, such as using tools like automatic network topology discovery, real-time status monitoring, traffic analysis, and fault diagnosis to maintain operational networks. However, these technologies lack the ability to conduct preventative planning based on the building's spatial structure from the initial project stage. Summary of the Invention

[0008] To achieve automated planning that includes a complete network deployment scheme, in a first aspect, embodiments of this application provide a method for planning IoT device networks based on building spatial topology, the method comprising: The system acquires building spatial structure information and equipment deployment plan information. The building spatial structure information is represented by a spatial topology tree to show the hierarchical relationship between buildings, floors and rooms. The equipment deployment plan information is recorded by a three-dimensional equipment matrix to show the number, type and bandwidth requirements of equipment under each spatial node. Based on the spatial topology tree and the three-dimensional device matrix, the total number of devices and the total number of buildings are analyzed to determine a two- or three-layer network hierarchy architecture. Based on the network hierarchy architecture and the spatial topology tree, a network topology structure is generated that defines the deployment locations and connection relationships of core switches, aggregation switches, and access switches. Based on the analysis of device density using the three-dimensional device matrix, combined with a preset broadcast domain threshold, and according to spatial location information and / or device type, the devices are automatically divided into multiple VLANs, and each VLAN is assigned a VLAN identifier based on its spatial location code. Based on the building number, floor number, and room number in the spatial topology tree, an IP address with spatial semantics is generated for each device, and IP address conflict detection is performed. Based on the number of devices and bandwidth requirements in the device deployment plan information, as well as the network topology, the specifications and quantities of the core switches, aggregation switches and access switches are automatically determined, and a selection list containing switch types, specifications, quantities and deployment locations is generated. Based on the network topology, VLAN division and identification, IP address allocation results, and the selection list, a complete network deployment plan is automatically generated, including a network topology diagram, VLAN configuration table, IP address allocation table, bill of materials, and switch configuration scripts.

[0009] In one possible implementation, the method further includes obtaining server deployment information; analyzing the total number of devices and buildings based on the spatial topology tree and the three-dimensional device matrix to determine a two- or three-layer network hierarchy architecture; and generating a network topology structure defining the deployment locations and connection relationships of core switches, aggregation switches, and access switches based on the network hierarchy architecture and the spatial topology tree, including: If the total number of devices is less than the first threshold and the total number of buildings is less than the second threshold, a two-layer network architecture is adopted, with the first layer being the access switch layer and the second layer being the aggregation switch layer or the core switch layer. If the total number of devices is not less than the first threshold or the total number of buildings is not less than the second threshold, a three-layer network architecture is adopted, with the first layer being the access switch layer, the second layer being the aggregation switch layer, and the third layer being the core switch layer. The access switch layer corresponds to rooms or areas with dense equipment, the aggregation switch layer corresponds to buildings or floors, and the core switch layer corresponds to the server room. The core switches are deployed in the server room, the aggregation switches are deployed in the building's weak current room or the floor's weak current room, and the access switches are deployed in the floor's weak current room or the nearest room. The core switches and aggregation switches have Layer 3 routing capabilities.

[0010] In one possible implementation, the step of analyzing device density based on the three-dimensional device matrix, combining a preset broadcast domain threshold, and automatically dividing devices into multiple VLANs according to spatial location information and device type, and assigning a VLAN identifier to each VLAN based on its spatial location code, includes: The device density is calculated based on the number of devices and the number of buildings / floors in the three-dimensional device matrix. If the device density does not exceed the preset broadcast domain threshold, each building / floor is determined as the VLAN division benchmark. In each building / floor, one device type corresponds to one VLAN.

[0011] In one possible implementation, the IP address conflict detection includes: Check if the newly generated IP address exists within the same network segment. If so, start from the newly generated IP address and search sequentially for the first available IP address to use as the device's IP address. Check if the device's IP address conflicts with the server's IP address. If so, re-plan the building's IP range and update all related dependencies. Check if the device's IP address is within a legal range. If not, increase the subnet mask corresponding to the VLAN where the device is located.

[0012] In one possible implementation, the automatic determination of the specifications and quantity of the core switch, aggregation switch, and access switch based on the number of devices and bandwidth requirements in the device deployment plan information, and the network topology, includes: The total number of ports of the access switches is determined based on the number of devices and the first redundancy value in the device deployment plan information; the number of access switches is determined based on the number of ports of each access switch. The total number of ports of the aggregation switches is determined based on the number of access switches and the second redundancy value; the number of aggregation switches is determined based on the number of ports of each aggregation switch; and the speed of each aggregation switch is determined based on the bandwidth requirements in the device deployment plan information. The total number of ports on the core switches is determined based on the number of aggregation switches and the second redundancy value. The number of core switches is then determined based on the number of ports on each core switch.

[0013] Secondly, embodiments of this application provide an Internet of Things (IoT) device network planning apparatus based on building spatial topology, the apparatus comprising: The acquisition module is used to acquire building space structure information and equipment deployment plan information. The building space structure information is represented by a spatial topology tree to show the hierarchical relationship between buildings, floors and rooms. The equipment deployment plan information is recorded by a three-dimensional equipment matrix to show the number, type and bandwidth requirements of equipment under each spatial node. The network topology module is used to analyze the total number of devices and the total number of buildings based on the spatial topology tree and the three-dimensional device matrix to determine a two- or three-layer network hierarchy architecture, and to generate a network topology structure that defines the deployment locations and connection relationships of core switches, aggregation switches and access switches based on the network hierarchy architecture and the spatial topology tree. The VLAN module is used to analyze device density based on the three-dimensional device matrix, combine a preset broadcast domain threshold, and automatically divide devices into multiple VLANs according to spatial location information and / or device type, and assign a VLAN identifier to each VLAN based on its spatial location code. The IP module is used to generate a spatially semantic IP address for each device based on the building number, floor number, and room number in the spatial topology tree, and to perform IP address conflict detection. The switch module is used to automatically determine the specifications and quantity of the core switch, aggregation switch and access switch based on the number of devices and bandwidth requirements in the device deployment plan information and the network topology, and generate a selection list including switch type, specifications, quantity and deployment location. The output module is used to automatically generate a complete network deployment plan based on the network topology, VLAN division and identification, IP address allocation results and the selection list, including a network topology diagram, VLAN configuration table, IP address allocation table, bill of materials and switch configuration scripts.

[0014] In one possible implementation, the acquisition module is further configured to acquire server deployment information, and the network topology module is specifically configured to: If the total number of devices is less than the first threshold and the total number of buildings is less than the second threshold, a two-layer network architecture is adopted, with the first layer being the access switch layer and the second layer being the aggregation switch layer or the core switch layer. If the total number of devices is not less than the first threshold or the total number of buildings is not less than the second threshold, a three-layer network architecture is adopted, with the first layer being the access switch layer, the second layer being the aggregation switch layer, and the third layer being the core switch layer. The access switch layer corresponds to rooms or areas with dense equipment, the aggregation switch layer corresponds to buildings or floors, and the core switch layer corresponds to the server room. The core switches are deployed in the server room, the aggregation switches are deployed in the building's weak current room or the floor's weak current room, and the access switches are deployed in the floor's weak current room or the nearest room. The core switches and aggregation switches have Layer 3 routing capabilities.

[0015] In one possible implementation, the VLAN module is specifically used for: The device density is calculated based on the number of devices and the number of buildings / floors in the three-dimensional device matrix. If the device density does not exceed the preset broadcast domain threshold, each building / floor is determined as the VLAN division benchmark. In each building / floor, one device type corresponds to one VLAN.

[0016] In one possible implementation, the IP module is specifically used for: Check if the newly generated IP address exists within the same network segment. If so, start from the newly generated IP address and search sequentially for the first available IP address to use as the device's IP address. Check if the device's IP address conflicts with the server's IP address. If so, re-plan the building's IP range and update all related dependencies. Check if the device's IP address is within a legal range. If not, increase the subnet mask corresponding to the VLAN where the device is located.

[0017] Thirdly, the present invention provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements any of the above-mentioned IoT device network planning methods based on building spatial topology.

[0018] This application provides a method for planning an IoT device network based on building spatial topology, comprising: acquiring building spatial structure information and device deployment plan information, wherein the building spatial structure information represents the hierarchical relationship of buildings, floors, and rooms using a spatial topology tree, and the device deployment plan information records the number, type, and bandwidth requirements of devices under each spatial node using a three-dimensional device matrix; based on the spatial topology tree and the three-dimensional device matrix, analyzing the total number of devices and the total number of buildings to determine a two- or three-layer network hierarchy architecture, and generating a network topology structure defining the deployment locations and connection relationships of core switches, aggregation switches, and access switches based on the network hierarchy architecture and the spatial topology tree; analyzing device density based on the three-dimensional device matrix, combining a preset broadcast domain threshold, and automatically... The system divides devices into multiple VLANs and assigns a VLAN identifier to each VLAN based on its spatial location. Based on the building number, floor number, and room number in the spatial topology tree, it generates a spatially semantic IP address for each device and performs IP address conflict detection. Based on the device deployment plan information, including the number of devices and bandwidth requirements, and the network topology, it automatically determines the specifications and quantity of core switches, aggregation switches, and access switches, generating a selection list containing switch types, specifications, quantities, and deployment locations. Based on the network topology, VLAN division and identification, IP address allocation results, and the selection list, it automatically generates a complete network deployment plan including a network topology diagram, VLAN configuration table, IP address allocation table, bill of materials, and switch configuration scripts. This achieves automated network planning. Attached Figure Description

[0019] Figure 1 A flowchart illustrating an IoT device network planning method based on building spatial topology, provided for an embodiment of this application; Figure 2 A schematic diagram of the system structure for implementing an IoT device network planning method based on building spatial topology; Figure 3This is a schematic diagram of the structure of an Internet of Things (IoT) device network planning device based on building space topology, provided as an embodiment of this application. Detailed Implementation

[0020] The present invention will be described in detail below through embodiments.

[0021] With the rapid development and widespread application of IoT technology, smart communities, smart parks, smart hospitals, and smart campuses have become important carriers for digital transformation. These scenarios typically require the deployment of a large number of IoT terminal devices, including but not limited to access control devices, video surveillance equipment, medical intercom systems, environmental sensors, and smart healthcare terminals. For example, in a medium-sized smart community or hospital campus, the number of various IoT devices deployed can reach several thousand, widely distributed across multiple buildings, floors, and numerous individual rooms or functional areas.

[0022] As the infrastructure supporting the stable operation of IoT systems, the quality of network planning directly determines the reliability, performance, and long-term maintainability of the entire system. However, in current practical engineering project implementations, due to the lack of systematic, automated network planning methods closely integrated with physical space, the following typical problems commonly exist: Broadcast storm problem: In scenarios with dense device deployment, if the broadcast domain is too large, broadcast packets generated by Address Resolution Protocol (ARP) broadcasts, Dynamic Host Configuration Protocol (DHCP) requests, etc., will flood the network. For example, in a single Virtual Local Area Network (VLAN) containing more than 2,000 devices, every time a new device comes online or performs an address lookup, massive amounts of broadcast traffic will be generated, which can easily lead to network link congestion, switch overload, and in severe cases, even partial or complete network paralysis.

[0023] IP address conflicts and management chaos: Traditional IP address allocation relies heavily on manual planning and recording by network engineers. In projects with a large number of devices, long deployment cycles, and potential phased implementation, problems such as incomplete IP address allocation records, chaotic planning, and duplicate allocations are prone to occur. Address conflicts will directly lead to devices failing to register and go online or communication interruptions, and fault localization will be difficult.

[0024] Network connectivity issues: Due to reasons such as VLAN segmentation failing to adequately reflect the physical layout or business logic, incorrect Layer 3 routing configurations, and improper configuration of switch port operating modes and VLAN membership relationships, communication failures frequently occur between devices or between devices and servers. Troubleshooting these issues is cumbersome and severely impacts project delivery schedules and subsequent maintenance efficiency.

[0025] The problem of inefficient planning and deployment: Traditional network planning methods rely entirely on the manual experience of senior network engineers. Engineers need to repeatedly study building floor plans, manually design the physical and logical topology of the network, divide VLANs, plan IP address ranges, and select and configure network devices. The entire process is time-consuming, labor-intensive, and prone to configuration errors due to human oversight, making it difficult to ensure the consistency and standardization of the solution.

[0026] Currently, network management technologies and related research in the industry mainly focus on the post-construction management of existing networks, such as using tools like automatic network topology discovery, real-time status monitoring, traffic analysis, and fault diagnosis to maintain operational networks. However, these technologies lack the ability to conduct preventative planning based on the building's spatial structure from the initial project stage.

[0027] Firstly, see [the following] Figure 1 This application provides an embodiment of an IoT device network planning method based on building spatial topology, the method comprising: S101, obtain building space structure information and equipment deployment plan information.

[0028] The building space structure information is represented by a spatial topology tree to show the hierarchical relationship between buildings, floors and rooms, and the equipment deployment plan information is recorded by a three-dimensional equipment matrix to show the number, type and bandwidth requirements of equipment under each spatial node.

[0029] The spatial topology tree format is Node{ id, type, parentId, children[]}, and the spatial hierarchy is a tree structure of building-floor-room, used for subsequent network hierarchy mapping. Building spatial structure information includes building information, floor information, room information, and spatial hierarchy relationships. Building information includes building number, building name, and building location. Floor information includes floor number, floor name, and the building it belongs to. Room information includes room number, room name, the floor it belongs to, and room area.

[0030] The 3D device matrix format is Device[b][f][r][type]. It contains device deployment plan information, including device type, quantity, location, and communication requirements. Device types include access control devices, monitoring devices, and medical equipment. The quantity of devices is the number deployed in each room. Device location refers to the building, floor, and room where the devices are located. Communication requirements include the communication relationships between devices and bandwidth requirements.

[0031] By constructing a unified data structure, a computable and verifiable technical relationship is formed between spatial information, equipment information, and network planning algorithms, ensuring that the algorithm of this invention has a clear technical implementation basis.

[0032] S102, based on the spatial topology tree and the three-dimensional device matrix, analyze the total number of devices and the total number of buildings to determine a two- or three-layer network hierarchy architecture, and based on the network hierarchy architecture and the spatial topology tree, generate a network topology structure that defines the deployment locations and connection relationships of core switches, aggregation switches and access switches.

[0033] In one example, if the total number of devices is less than the first threshold and the total number of buildings is less than the second threshold, a two-layer network architecture is adopted, with the first layer being the access switch layer and the second layer being the aggregation switch layer or the core switch layer. If the total number of devices is not less than the first threshold or the total number of buildings is not less than the second threshold, a three-layer network architecture is adopted, with the first layer being the access switch layer, the second layer being the aggregation switch layer, and the third layer being the core switch layer. The access switch layer corresponds to rooms or areas with dense equipment, the aggregation switch layer corresponds to buildings or floors, and the core switch layer corresponds to the server room. The core switches are deployed in the server room, the aggregation switches are deployed in the building's weak current room or the floor's weak current room, and the access switches are deployed in the floor's weak current room or the nearest room. The core switches and aggregation switches have Layer 3 routing capabilities.

[0034] Both the first and second thresholds can be set according to actual conditions. This application automatically maps the building's physical hierarchy to the network logical hierarchy. The network hierarchy mapping rules are as follows: the core layer corresponds to the server room, the aggregation layer corresponds to the building or floor, and the access layer corresponds to the room or densely populated area of ​​devices. The network hierarchy depth is determined based on the total number and distribution of devices. A two-layer architecture is used when the total number of devices is less than 100; a two-layer architecture is still used when the total number of devices is between 100 and 1000 and the number of buildings does not exceed 3; and a three-layer architecture is used when the total number of devices exceeds 1000 or the number of buildings exceeds 3. Recommended switch deployment locations: core switches are deployed in the server room, aggregation switches are deployed in the building's or floor's weak current room, and access switches are deployed in the floor's weak current room or in a nearby location within a room. The nearest location within a room can be within a 10-meter radius of the room. This ultimately generates a complete network topology structure tree, including core switches, aggregation switches, access switches, and their connections.

[0035] The two-layer and three-layer architecture switching logic adopted in this application is not based on manual experience, but on modeling link length, broadcast load, and switch forwarding performance. For example, when the number of devices exceeds approximately 1000 or the building is distributed across more than 3 buildings, if a two-layer architecture is still used, the average utilization rate of the uplink in the aggregation layer will increase from 35% to over 70%, significantly increasing the probability of link congestion. Link depth calculation based on spatial topology trees can automatically determine the shortest link path in the network, thereby selecting the most suitable network hierarchy. Through this mapping algorithm, the average network link latency in actual projects can be reduced by 20% to 35%, bottleneck nodes reduced by 40%, and network stability significantly improved.

[0036] S103, based on the three-dimensional device matrix, analyze the device density, combine the preset broadcast domain threshold, and according to the spatial location information and / or device type, automatically divide the devices into multiple VLANs, and assign a VLAN identifier to each VLAN based on its spatial location code.

[0037] Device density = Number of devices / Number of spatial units. For example, if there are 1000 devices, 2 buildings, and 10 floors, the device density would be 500 (building device density) and 50 (floor device density). The preset broadcast domain threshold is derived from actual traffic sampling of the actual project and is 200 devices.

[0038] VLAN partitioning strategy 1: Partition by building. When the number of devices in a building is less than 200, each building will have its own VLAN. VLAN partitioning strategy 2: Partition by floor. When the number of devices on a floor is less than 200, each floor will have its own VLAN. VLAN segmentation strategy 3: Segment by device type, with different types of devices such as access control, monitoring, and medical care assigned to different VLANs; VLAN segmentation strategy 4: Hybrid segmentation, which combines spatial location and device type for comprehensive segmentation.

[0039] In one example, the device density can be calculated based on the number of devices and the number of buildings / floors in the three-dimensional device matrix. If the device density does not exceed the preset broadcast domain threshold, each building / floor is determined as the VLAN division benchmark. In each building / floor, one device type corresponds to one VLAN.

[0040] Using the example of 1000 devices, since 500 (building device density) exceeds the preset broadcast domain threshold, while 50 (floor device density) does not, the floor is chosen as the VLAN segmentation basis. If the floor includes access control devices and monitoring devices, then two VLANs will be created. However, if there are 5 buildings, and the device density corresponding to 1000 devices is 200 (building device density), then the building is chosen as the VLAN segmentation basis. If the building includes access control devices, medical equipment, and monitoring devices, then three VLANs will be created.

[0041] For the case where each building is assigned a separate VLAN, the VLAN identifier can be obtained by VLAN_ID = 10 + building number. For example, Building 1 is VLAN 11, and Building 5 is VLAN 15. For the case where each floor is assigned a separate VLAN, the VLAN identifier can be obtained by VLAN_ID = 100 + building number × 10 + floor number. For example, the first floor of Building 1 is VLAN 111, the second floor of Building 1 is VLAN 112, and the first floor of Building 2 is VLAN 121. For the case of mixed VLANs, the VLAN identifier can be obtained by VLAN_ID = 1000 + building number × 100 + floor number × 10 + device type number. For example, the access control device on the first floor of Building 1 is VLAN 1111, and the monitoring device on the first floor of Building 1 is VLAN 1122.

[0042] By dynamically dividing VLANs by combining device density with broadcast domain thresholds, the variance of broadcast domain size can be reduced, thus decreasing the probability of broadcast storms.

[0043] S104. Based on the building number, floor number, and room number in the spatial topology tree, generate an IP address with spatial semantics for each device and perform IP address conflict detection.

[0044] IP address format: 10.Building number.Floor number.Room number. Example: The first device in Room 3, 2nd floor of Building 1 is 10.1.2.31, and the second device is 10.1.2.32. The first device in Room 8, 5th floor of Building 2 is 10.2.5.81.

[0045] The IP address conflict detection includes: Step 1: Check if the newly generated IP address exists within the same network segment. If so, start from the newly generated IP address and search sequentially for the first available IP address to use as the device's IP address. For example, after assigning an IP address of 10.1.5.31 to a device based on the building number, floor number, and room number, if it is found that this IP address already exists, then the search continues in the order of 10.1.5.32, 10.1.5.33, and so on, and the first available IP address is used as the device's IP address.

[0046] Step 2: Check if the device's IP address conflicts with the server's IP address. If so, re-plan the building's IP range and update all related dependencies. Based on the spatial allocation, the IP segment of Building 2 may be planned as 10.2.xx, which overlaps with the server IP segment 10.2.100.0 / 24. The system will shift the entire IP segment of Building 2, for example, from 10.2.xx to 10.3.xx; at the same time, all related dependencies will be updated, such as the IP addresses of all devices in Building 2, the corresponding VLAN gateway addresses, and the routing configuration scripts on the core switch and aggregation switch.

[0047] Step 3: Check if the device's IP address is within the legal range. If not, increase the subnet mask corresponding to the VLAN where the device is located.

[0048] When the number of devices does not exceed 254, the subnet mask is 255.255.255.0; when the number of devices is between 255 and 510, the subnet mask is 255.255.254.0; when the number of devices is between 511 and 1022, the subnet mask is 255.255.252.0.

[0049] For example, if 260 devices are planned for deployment on the second floor of Building 1, but the 10.1.2.0 / 24 network segment can only accommodate 254 devices, the system will attempt to expand the subnet mask from / 24 to / 23, changing the IP network segment to 10.1.2.0 / 23. The number of available addresses will increase from 254 to 510, ranging from 10.1.2.1 to 10.1.3.254. At this point, the floor number could be either 2 or 3, but to ensure IP address uniqueness, the device will be assigned an IP address from floor number 3. Although the floor information of the IP address is blurred, the VLAN to which the device belongs is absolutely clear, and the spatial information of the device can still be located through its VLAN.

[0050] Spatial semantic IP allocation is not a simple numbering rule, but rather a calculation result based on a spatial topology tree. Since IP addresses directly contain spatial information such as building, floor, and room, the system can quickly locate the physical space of a device without relying on ARP tables or MAC address lookups when a network failure occurs. Using the spatially aware IP allocation method of this application, the average time for single-device fault location is significantly shortened, troubleshooting efficiency is greatly improved, and network maintainability and stability are significantly enhanced.

[0051] S105, based on the number of devices and bandwidth requirements in the device deployment plan information, as well as the network topology, automatically determine the specifications and quantity of the core switch, aggregation switch and access switch, and generate a selection list including switch type, specifications, quantity and deployment location.

[0052] The access switches are 24- or 48-port gigabit switches, the aggregation switches are 24- or 48-port gigabit or 10-gigabit switches, supporting Layer 3 routing, and the core switches are 48-port 10-gigabit switches, supporting Layer 3 routing and advanced features.

[0053] In one example, the total number of ports of the access switch can be determined based on the number of devices and the first redundancy value in the device deployment plan information; the number of access switches can be determined based on the number of ports of each access switch. The total number of ports of the aggregation switches is determined based on the number of access switches and the second redundancy value; the number of aggregation switches is determined based on the number of ports of each aggregation switch; and the speed of each aggregation switch is determined based on the bandwidth requirements in the device deployment plan information. The total number of ports on the core switches is determined based on the number of aggregation switches and the second redundancy value. The number of core switches is then determined based on the number of ports on each core switch.

[0054] The first and second redundancy values ​​can be adjusted according to the actual situation. For example, the first redundancy value is 0.8, which allows the access switch to reserve 20% redundancy, and the second redundancy value is 0.7, which allows the aggregation switch to reserve 30% redundancy. When the calculated result of the total number of ports is not an integer, it is rounded up.

[0055] Assuming there are 800 HD cameras and 400 access control terminals, 1200 / 0.8=1500. For a 24-port access switch, 63 switches are needed, and for a 48-port access switch, 32 switches are needed. If 63 access switches are selected, the bandwidth requirement is calculated as follows: the total bandwidth for the cameras is 4×800=3200, and the total bandwidth for the access control is 1×400=400. Considering a 1.5 times margin, the total bandwidth requirement for the equipment is (3200+400)×1.5=5400Mbps. For a 48-port aggregation switch, 2 switches are needed, each handling 2700Mbps of traffic. Therefore, the aggregation switch speed is 10Gbps.

[0056] The above methods avoid technical problems such as insufficient backplane bandwidth and uplink congestion that may occur with manual equipment selection, making equipment selection more scientific and verifiable. This significantly reduces link congestion rates and decreases the need for network expansion.

[0057] S106. Based on the network topology, VLAN division and identification, IP address allocation results, and the selection list, automatically generate a complete network deployment plan that includes a network topology diagram, VLAN configuration table, IP address allocation table, bill of materials, and switch configuration scripts.

[0058] The network topology diagram displays the network structure in layers, annotates device connections, VLAN divisions, and IP network segments. The VLAN configuration table includes VLAN identifiers, VLAN names, a list of devices included in the VLAN, IP network segments, and gateway addresses. The IP address allocation table includes device names, device locations, IP addresses, subnet masks, gateway addresses, and VLAN identifiers. The bill of materials includes switch type (core / aggregation / access switch), specifications (number of ports, speed), quantity, deployment location, and reference models. The switch configuration scripts include port VLAN allocation (determining which ports different devices connect to on the switch), VLAN interface IP address configuration (creating a virtual Layer 3 interface for each VLAN that needs to communicate across network segments; its IP address is the default gateway for all devices within that VLAN, e.g., VLAN 151's gateway is 10.2.5.1 / 24, and VLAN 152's gateway is 10.2.6.1 / 24), and routing protocol configuration.

[0059] In addition, deployment guidance documents will be generated, including construction instructions such as equipment mounting and wiring diagrams, configuration loading steps, acceptance test checklists, and troubleshooting guides.

[0060] Since all VLAN, IP, routing, and port configurations are automatically generated by the algorithm and parameter consistency is ensured, common problems such as VLAN identifier conflicts, inconsistent IP network segments, and missing routing table configurations caused by manual configuration can be effectively avoided, significantly improving network deployment quality and stability.

[0061] See Figure 2 This is a system architecture diagram of this application, comprising three layers: an input layer, a core processing layer, and an output layer. The input layer is responsible for collecting building space information, including the hierarchical relationship of buildings, floors, and rooms; equipment deployment plans, including equipment types, quantities, locations, and communication requirements; and server information, including IP addresses and server room locations. The core processing layer is the core of the system, containing a space-device association model to establish the mapping relationship between space and devices; a space-network mapping algorithm to map the physical hierarchy of the building to the logical hierarchy of the network; an intelligent VLAN partitioning algorithm to automatically partition VLANs based on device density to prevent broadcast storms; a space-aware IP allocation algorithm to automatically allocate IP addresses based on spatial location; and a device selection recommendation engine to recommend switch specifications based on the number of devices and bandwidth requirements. The output layer generates a complete network deployment scheme, including a network topology diagram showing the hierarchical network structure and device connection relationships; a VLAN allocation table containing VLAN IDs and IP network segments; an IP address allocation table containing device names, locations, IP addresses, subnet masks, and gateways; a device BOM (Bill of Materials) list containing switch types, specifications, quantities, and deployment locations; and configuration scripts containing VLAN configuration, routing configuration, and port configuration commands.

[0062] Compared with the prior art, this application has the following beneficial effects: Preventative network problem resolution: By using intelligent VLAN segmentation and broadcast domain isolation, the network architecture is planned before device deployment, preventing network storms at the source; by using space-aware IP allocation and conflict detection, IP address conflicts are completely avoided; and by using automated configuration generation, human configuration errors are eliminated.

[0063] Significantly improve deployment efficiency: Network planning time is reduced from weeks to hours, improving efficiency by over 90%; no professional network engineers are needed, reducing labor costs by over 60%; configuration files are automatically generated, improving deployment efficiency by 80%.

[0064] Improve network stability and maintainability: Scientific VLAN segmentation and IP planning reduce network failure rate by 70%; complete topology documentation and configuration lists shorten troubleshooting time by 50%; standardized network architecture facilitates future expansion and maintenance.

[0065] Innovative Space-Network Mapping: It is the first to use building space topology as the core input for network planning, realizing automated mapping from physical space to network logic. IP addresses have spatial semantics, which facilitates management and fault location.

[0066] A complete solution: It not only outputs network topology diagrams, but also complete deployment plans, including VLAN segmentation, IP allocation, device selection, configuration scripts, and deployment documents, realizing full automation of the network planning process.

[0067] Wide range of applications: Suitable for various scenarios such as smart communities, smart parks, smart hospitals, and smart campuses; supports various IoT device types such as access control, monitoring, medical care, and elderly care; and can handle large-scale deployment scenarios with thousands of devices.

[0068] Secondly, embodiments of this application provide an Internet of Things (IoT) device network planning apparatus based on building spatial topology, the apparatus comprising: The acquisition module is used to acquire building space structure information and equipment deployment plan information. The building space structure information is represented by a spatial topology tree to show the hierarchical relationship between buildings, floors and rooms. The equipment deployment plan information is recorded by a three-dimensional equipment matrix to show the number, type and bandwidth requirements of equipment under each spatial node. The network topology module is used to analyze the total number of devices and the total number of buildings based on the spatial topology tree and the three-dimensional device matrix to determine a two- or three-layer network hierarchy architecture, and to generate a network topology structure that defines the deployment locations and connection relationships of core switches, aggregation switches and access switches based on the network hierarchy architecture and the spatial topology tree. The VLAN module is used to analyze device density based on the three-dimensional device matrix, combine a preset broadcast domain threshold, and automatically divide devices into multiple VLANs according to spatial location information and / or device type, and assign a VLAN identifier to each VLAN based on its spatial location code. The IP module is used to generate a spatially semantic IP address for each device based on the building number, floor number, and room number in the spatial topology tree, and to perform IP address conflict detection. The switch module is used to automatically determine the specifications and quantity of the core switch, aggregation switch and access switch based on the number of devices and bandwidth requirements in the device deployment plan information and the network topology, and generate a selection list including switch type, specifications, quantity and deployment location. The output module is used to automatically generate a complete network deployment plan based on the network topology, VLAN division and identification, IP address allocation results and the selection list, including a network topology diagram, VLAN configuration table, IP address allocation table, bill of materials and switch configuration scripts.

[0069] In one possible implementation, the acquisition module is further configured to acquire server deployment information, and the network topology module is specifically configured to: If the total number of devices is less than the first threshold and the total number of buildings is less than the second threshold, a two-layer network architecture is adopted, with the first layer being the access switch layer and the second layer being the aggregation switch layer or the core switch layer. If the total number of devices is not less than the first threshold or the total number of buildings is not less than the second threshold, a three-layer network architecture is adopted, with the first layer being the access switch layer, the second layer being the aggregation switch layer, and the third layer being the core switch layer. The access switch layer corresponds to rooms or areas with dense equipment, the aggregation switch layer corresponds to buildings or floors, and the core switch layer corresponds to the server room. The core switches are deployed in the server room, the aggregation switches are deployed in the building's weak current room or the floor's weak current room, and the access switches are deployed in the floor's weak current room or the nearest room. The core switches and aggregation switches have Layer 3 routing capabilities.

[0070] In one possible implementation, the VLAN module is specifically used for: The device density is calculated based on the number of devices and the number of buildings / floors in the three-dimensional device matrix. If the device density does not exceed the preset broadcast domain threshold, each building / floor is determined as the VLAN division benchmark. In each building / floor, one device type corresponds to one VLAN.

[0071] In one possible implementation, the IP module is specifically used for: Check if the newly generated IP address exists within the same network segment. If so, start from the newly generated IP address and search sequentially for the first available IP address to use as the device's IP address. Check if the device's IP address conflicts with the server's IP address. If so, re-plan the building's IP range and update all related dependencies. Check if the device's IP address is within a legal range. If not, increase the subnet mask corresponding to the VLAN where the device is located.

[0072] Thirdly, the present invention provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements any of the above-mentioned IoT device network planning methods based on building spatial topology.

[0073] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially as a computer program product. The computer program product includes one or more computer instructions. When the 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. The 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 website, computer, server, or data center 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. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid state disk (SSD)).

[0074] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0075] The various embodiments in this specification are described in a related manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the device embodiments are described simply because their systems are similar to the method embodiments; relevant parts can be referred to the descriptions of the method embodiments.

[0076] Although embodiments of the present invention have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present invention. Those skilled in the art can make changes to the above embodiments within the scope of the present invention without departing from the principles and spirit of the present invention.

Claims

1. A method for planning an Internet of Things (IoT) device network based on building spatial topology, characterized in that, The method includes: The system acquires building spatial structure information and equipment deployment plan information. The building spatial structure information is represented by a spatial topology tree to show the hierarchical relationship between buildings, floors and rooms. The equipment deployment plan information is recorded by a three-dimensional equipment matrix to show the number, type and bandwidth requirements of equipment under each spatial node. Based on the spatial topology tree and the three-dimensional device matrix, the total number of devices and the total number of buildings are analyzed to determine a two- or three-layer network hierarchy architecture. Based on the network hierarchy architecture and the spatial topology tree, a network topology structure is generated that defines the deployment locations and connection relationships of core switches, aggregation switches, and access switches. Based on the analysis of device density using the three-dimensional device matrix, combined with a preset broadcast domain threshold, and according to spatial location information and / or device type, the devices are automatically divided into multiple VLANs, and each VLAN is assigned a VLAN identifier based on its spatial location code. Based on the building number, floor number, and room number in the spatial topology tree, an IP address with spatial semantics is generated for each device, and IP address conflict detection is performed. Based on the number of devices and bandwidth requirements in the device deployment plan information, as well as the network topology, the specifications and quantities of the core switches, aggregation switches and access switches are automatically determined, and a selection list containing switch types, specifications, quantities and deployment locations is generated. Based on the network topology, VLAN division and identification, IP address allocation results, and the selection list, a complete network deployment plan is automatically generated, including a network topology diagram, VLAN configuration table, IP address allocation table, bill of materials, and switch configuration scripts.

2. The method according to claim 1, characterized in that, The method further includes obtaining server deployment information; analyzing the total number of devices and buildings based on the spatial topology tree and the three-dimensional device matrix to determine a two- or three-layer network hierarchy architecture; and generating a network topology structure defining the deployment locations and connection relationships of core switches, aggregation switches, and access switches based on the network hierarchy architecture and the spatial topology tree, including: If the total number of devices is less than the first threshold and the total number of buildings is less than the second threshold, a two-layer network architecture is adopted, with the first layer being the access switch layer and the second layer being the aggregation switch layer or the core switch layer. If the total number of devices is not less than the first threshold or the total number of buildings is not less than the second threshold, a three-layer network architecture is adopted, with the first layer being the access switch layer, the second layer being the aggregation switch layer, and the third layer being the core switch layer. The access switch layer corresponds to rooms or areas with dense equipment, the aggregation switch layer corresponds to buildings or floors, and the core switch layer corresponds to the server room. The core switches are deployed in the server room, the aggregation switches are deployed in the building's weak current room or the floor's weak current room, and the access switches are deployed in the floor's weak current room or the nearest room. The core switches and aggregation switches have Layer 3 routing capabilities.

3. The method according to claim 1, characterized in that, The process involves analyzing device density based on the three-dimensional device matrix, combining a preset broadcast domain threshold, and automatically dividing devices into multiple VLANs according to spatial location information and device type. Each VLAN is then assigned a VLAN identifier based on its spatial location code. This includes: The device density is calculated based on the number of devices and the number of buildings / floors in the three-dimensional device matrix. If the device density does not exceed the preset broadcast domain threshold, each building / floor is determined as the VLAN division benchmark. In each building / floor, one device type corresponds to one VLAN.

4. The method according to claim 1, characterized in that, The IP address conflict detection includes: Check if the newly generated IP address exists within the same network segment. If so, start from the newly generated IP address and search sequentially for the first available IP address to use as the device's IP address. Check if the device's IP address conflicts with the server's IP address. If so, re-plan the building's IP range and update all related dependencies. Check if the device's IP address is within a legal range. If not, increase the subnet mask corresponding to the VLAN where the device is located.

5. The method according to claim 1, characterized in that, The automatic determination of the specifications and quantity of the core switch, aggregation switch, and access switch based on the device deployment plan information, bandwidth requirements, and network topology includes: The total number of ports of the access switches is determined based on the number of devices and the first redundancy value in the device deployment plan information; the number of access switches is determined based on the number of ports of each access switch. The total number of ports of the aggregation switches is determined based on the number of access switches and the second redundancy value; the number of aggregation switches is determined based on the number of ports of each aggregation switch; and the speed of each aggregation switch is determined based on the bandwidth requirements in the device deployment plan information. The total number of ports on the core switches is determined based on the number of aggregation switches and the second redundancy value. The number of core switches is then determined based on the number of ports on each core switch.

6. A network planning device for Internet of Things (IoT) devices based on building spatial topology, characterized in that, The device includes: The acquisition module is used to acquire building space structure information and equipment deployment plan information. The building space structure information is represented by a spatial topology tree to show the hierarchical relationship between buildings, floors and rooms. The equipment deployment plan information is recorded by a three-dimensional equipment matrix to show the number, type and bandwidth requirements of equipment under each spatial node. The network topology module is used to analyze the total number of devices and the total number of buildings based on the spatial topology tree and the three-dimensional device matrix to determine a two- or three-layer network hierarchy architecture, and to generate a network topology structure that defines the deployment locations and connection relationships of core switches, aggregation switches and access switches based on the network hierarchy architecture and the spatial topology tree. The VLAN module is used to analyze device density based on the three-dimensional device matrix, combine a preset broadcast domain threshold, and automatically divide devices into multiple VLANs according to spatial location information and / or device type, and assign a VLAN identifier to each VLAN based on its spatial location code. The IP module is used to generate a spatially semantic IP address for each device based on the building number, floor number, and room number in the spatial topology tree, and to perform IP address conflict detection. The switch module is used to automatically determine the specifications and quantity of the core switch, aggregation switch and access switch based on the number of devices and bandwidth requirements in the device deployment plan information and the network topology, and generate a selection list including switch type, specifications, quantity and deployment location. The output module is used to automatically generate a complete network deployment plan based on the network topology, VLAN division and identification, IP address allocation results and the selection list, including a network topology diagram, VLAN configuration table, IP address allocation table, bill of materials and switch configuration scripts.

7. The apparatus according to claim 6, characterized in that, The acquisition module is also used to acquire server deployment information, and the network topology module is specifically used for: If the total number of devices is less than the first threshold and the total number of buildings is less than the second threshold, a two-layer network architecture is adopted, with the first layer being the access switch layer and the second layer being the aggregation switch layer or the core switch layer. If the total number of devices is not less than the first threshold or the total number of buildings is not less than the second threshold, a three-layer network architecture is adopted, with the first layer being the access switch layer, the second layer being the aggregation switch layer, and the third layer being the core switch layer. The access switch layer corresponds to rooms or areas with dense equipment, the aggregation switch layer corresponds to buildings or floors, and the core switch layer corresponds to the server room. The core switches are deployed in the server room, the aggregation switches are deployed in the building's weak current room or the floor's weak current room, and the access switches are deployed in the floor's weak current room or the nearest room. The core switches and aggregation switches have Layer 3 routing capabilities.

8. The apparatus according to claim 6, characterized in that, The VLAN module is specifically used for: The device density is calculated based on the number of devices and the number of buildings / floors in the three-dimensional device matrix. If the device density does not exceed the preset broadcast domain threshold, each building / floor is determined as the VLAN division benchmark. In each building / floor, one device type corresponds to one VLAN.

9. The apparatus according to claim 6, characterized in that, The IP module is specifically used for: Check if the newly generated IP address exists within the same network segment. If so, start from the newly generated IP address and search sequentially for the first available IP address to use as the device's IP address. Check if the device's IP address conflicts with the server's IP address. If so, re-plan the building's IP range and update all related dependencies. Check if the device's IP address is within a legal range. If not, increase the subnet mask corresponding to the VLAN where the device is located.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the method described in any one of claims 1-5.

Images