A VLAN resource management method, device, equipment, medium and product

Abstract

The application discloses a VLAN resource management and control method, device, equipment, medium and product, and relates to the technical field of communication. The method comprises the following steps: collecting the number of access terminals and the bandwidth occupation rate of each VLAN in a VLAN resource pool in real time; wherein the VLAN resource pool divides corresponding VLAN subsets for each network area; determining the load weight corresponding to each VLAN based on the number of access terminals and the bandwidth occupation rate of each VLAN; for any VLAN, when the load weight of the VLAN exceeds a first threshold value, creating a new VLAN in the network area corresponding to the VLAN and adding the new VLAN to the VLAN resource pool; for any VLAN, when the load weight of the VLAN is lower than a second threshold value and there is a redundant VLAN in the resource pool, deleting the redundant VLAN; when a new terminal accesses, assigning the VLAN to which the new terminal belongs according to the access position of the new terminal; when a terminal roams between access points, switching the terminal to the VLAN with the lowest load weight in the target roaming area according to the VLAN load weight of the target roaming area. The method can realize accurate management and control of VLAN resources.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a VLAN resource management method, apparatus, device, medium and product. Background Technology

[0002] With the rapid development of wireless communication technology, high-density open Wi-Fi scenarios such as large venues, commercial complexes, and transportation hubs are increasingly common, leading to an explosive growth in terminal access. This places higher demands on network load balancing, resource utilization, and roaming experience. Virtual Local Area Networks (VLANs), as a primary technology for network resource isolation and management, effectively divide network domains, reduce broadcast storms, and improve network security. They have become a key means of network resource management in high-density Wi-Fi (Wireless Fidelity) scenarios, and their rational scheduling and dynamic management directly determine the overall network operating efficiency and user experience.

[0003] Currently, VLAN resource management in high-density Wi-Fi scenarios mostly adopts a static configuration mode. This involves pre-allocating a fixed number of VLANs based on estimated load, assigning a fixed number of VLANs to different physical areas, and pre-setting the number of access terminals and bandwidth limits for each VLAN. When a terminal connects, it is assigned to a designated VLAN according to fixed rules, and when a terminal roams, only a simple access point switch is performed, maintaining the original VLAN configuration. However, existing VLAN resource management solutions have significant limitations, such as inability to adapt to the dynamic load characteristics of high-density Wi-Fi scenarios, inaccurate load assessment, and poor overall network stability. Ultimately, they cannot achieve precise management of VLAN resources.

[0004] Therefore, there is an urgent need for a method that can achieve precise management and control of VLAN resources. Summary of the Invention

[0005] This application provides a VLAN resource management method, device, equipment, medium, and product that can achieve precise management and control of VLAN resources.

[0006] To achieve the above objectives, this application adopts the following technical solution: Firstly, this application provides a VLAN resource management method, including: The system collects the number of access terminals and bandwidth utilization rate of each VLAN in the VLAN resource pool in real time. The VLAN resource pool is divided into corresponding VLAN subsets for each network area, and each VLAN subset corresponds to a preset threshold for the number of access terminals and the bandwidth utilization rate. The load weight of each VLAN is determined based on the number of access terminals and bandwidth utilization of each VLAN. For any VLAN, when the load weight of the VLAN exceeds the first threshold, a new VLAN is created in the network area corresponding to the VLAN and added to the VLAN resource pool; For any VLAN, if the VLAN's load weight is lower than the second threshold and there are redundant VLANs in the VLAN resource pool, delete the redundant VLAN. When a new terminal connects, the VLAN to which the new terminal belongs is assigned according to the location of the new terminal. When a terminal roams between access points, it is switched to the VLAN with the lowest load weight in the target roaming area, based on the VLAN load weight of that area.

[0007] In some possible implementations, the VLAN of the new terminal is assigned based on its access location, including: Determine the network area to which the new terminal belongs based on its access location; Based on the network region to which the new terminal belongs, the new terminal will be assigned to the VLAN with the lowest load weight within that network region.

[0008] In some possible implementations, the load weight is calculated by weighting the ratio of the number of access terminals to the threshold number of access terminals in the corresponding VLAN, and the ratio of the bandwidth utilization rate to the threshold bandwidth utilization rate of the corresponding VLAN.

[0009] In some possible implementations, redundant VLANs are removed, including: When the load weight of any VLAN is lower than the second threshold and the number of idle VLANs in the VLAN resource pool exceeds the preset maximum number of idle VLANs, the terminals in the VLAN will be migrated to the target VLAN in the same network area whose load weight is lower than that VLAN and not higher than the third threshold. After the migration is completed, the VLAN will be deleted.

[0010] In some possible implementations, the terminal is switched to the VLAN with the lowest load in the area, including: Receive terminal roaming information uploaded by the access point; wherein, the terminal roaming information includes the location and signal strength of the target access point associated with the terminal after roaming; Based on the load weight of each VLAN within the network area to which the target access point belongs, the VLAN with the lowest load weight is selected as the target VLAN; Update the traffic forwarding rules to seamlessly switch the terminal to the target VLAN and assign the terminal the IP address corresponding to the target VLAN.

[0011] Among the possible implementations are: When the load weight of any VLAN exceeds the first threshold, some terminals within the VLAN will be migrated to other VLANs in the same network area whose load weight is not higher than the fourth threshold, until the load weight of the VLAN drops below the first threshold. Among them, the migrated terminals will prioritize low-priority service terminals, which will be determined based on the terminal service type or user level.

[0012] Secondly, this application provides a VLAN resource management device, comprising: The acquisition module is used to collect the number of access terminals and bandwidth utilization rate of each VLAN in the VLAN resource pool in real time. The VLAN resource pool is divided into corresponding VLAN subsets for each network area, and each VLAN subset corresponds to a preset threshold for the number of access terminals and the bandwidth utilization rate. The weight determination module is used to determine the load weight of each VLAN based on the number of access terminals and bandwidth utilization of each VLAN. The management module is used to create a new VLAN and add it to the VLAN resource pool in the network area corresponding to any VLAN when the VLAN's load weight exceeds the first threshold; to delete the redundant VLAN when the VLAN's load weight is lower than the second threshold and there is a redundant VLAN in the VLAN resource pool; to assign a VLAN to a new terminal when it accesses the network, based on the new terminal's access location; and to switch the terminal to the VLAN with the lowest load weight in the roaming target area when it roams between access points.

[0013] Thirdly, this application provides a computing device, including a memory and a processor; The memory stores one or more computer programs, the one or more computer programs including instructions; when the instructions are executed by the processor, the computing device performs the method as described in any one of the first aspects.

[0014] Fourthly, this application provides a computer-readable storage medium for storing a computer program for performing the method as described in any one of the first aspects.

[0015] Fifthly, this application provides a computer program product comprising one or more computer instructions, wherein when the computer instructions are executed by a computer, the computer performs the method as described in any one of the first aspects.

[0016] As can be seen from the above technical solution, this application has at least the following beneficial effects: In this application, by collecting the number of access terminals and bandwidth utilization of each VLAN in the VLAN resource pool in real time, real-time and quantifiable raw data support is provided for all subsequent VLAN resource scheduling operations. This completely eliminates the subjectivity of judging load based on experience in the traditional mode, and enables load management and resource scheduling to have a data-driven and scientific decision-making basis. At the same time, VLAN resources are uniformly pooled and managed globally, and dedicated VLAN subsets are divided according to network areas. Thresholds for the number of access terminals and bandwidth utilization are preset for each subset. This not only realizes fine-grained regional management of VLAN resources, avoids cross-regional load interference, and adapts to the characteristics of uneven terminal distribution and drastic load fluctuations in high-density scenarios, but also clarifies the unified quantitative benchmark for subsequent load status judgment, eliminates judgment bias between different areas and different VLANs, and improves the consistency and accuracy of overall scheduling.

[0017] The load weight of each VLAN is determined based on the number of access terminals and bandwidth utilization, successfully integrating load data from two different dimensions into a unified quantitative indicator. This eliminates the measurement discrepancies between different data, enabling horizontal comparison and vertical tracking of the load level of each VLAN. It solves the problem that a single indicator cannot fully reflect the actual load of a VLAN. The load weight comprehensively considers the two core load dimensions of terminal access and bandwidth usage, which can more realistically and comprehensively reflect the actual carrying pressure of the VLAN. It avoids the one-sidedness of only looking at the number of terminals and ignoring bandwidth saturation or only looking at bandwidth and ignoring terminal overload. This makes subsequent scheduling decisions such as expansion, deletion, and terminal allocation more in line with the actual network operation status. At the same time, this load weight becomes the main judgment indicator for subsequent VLAN resource scheduling operations throughout the entire process, making the overall solution form a complete closed loop of data collection, quantitative analysis, and decision execution, and promoting the upgrade of VLAN load management towards intelligence and automation.

[0018] To address different scenarios—load weight exceeding and falling below thresholds—the system executes operations to create new VLANs and delete redundant VLANs, enabling elastic and dynamic scheduling of VLAN resources. When a VLAN load weight exceeds the first threshold, a new VLAN is created in the corresponding network area and added to the resource pool. This allows for on-demand resource expansion, quickly offloading terminal and bandwidth pressures from overloaded VLANs, and effectively solving the problems of VLAN overload, bandwidth saturation, and transmission congestion in high-density scenarios. Furthermore, the new VLAN is created only in the corresponding area, avoiding resource waste and cross-regional network interference caused by indiscriminate expansion. The new VLAN added to the resource pool can also be continuously scheduled and reused according to load changes, improving resource flexibility. When a VLAN load weight falls below the second threshold and redundancy exists, the redundant VLAN is deleted. This promptly reclaims idle resources and releases them to the global resource pool, allowing idle resources to be used by other areas with high loads. This improves VLAN resource utilization globally, solving the problem of idle resources in non-hotspot areas caused by fixed resource configurations in traditional models. Timely cleanup of redundant VLANs also reduces network device maintenance costs, simplifies VLAN resource management complexity, reduces manual maintenance pressure, and the threshold-based determination method avoids accidental VLAN deletion due to temporary load fluctuations, ensuring network service stability.

[0019] Differentiated VLAN allocation and switching operations are implemented for two scenarios: new terminal access and terminal roaming. This optimizes the entire terminal access experience and achieves precise load balancing at both the terminal access and mobility stages. When a new terminal accesses, it is assigned to the VLAN of its respective network area based on its access location. This avoids cross-regional data forwarding caused by terminals accessing different areas, significantly reducing the forwarding pressure on the network core layer, improving data transmission efficiency, and reducing latency and packet loss caused by cross-regional forwarding. At the same time, it is assigned to the VLAN with the lowest load weight based on the load status within the region, preventing a single VLAN from becoming overloaded due to continuous new terminal access from the source of terminal access, thus achieving regional load balancing. VLAN load balancing: When terminals roam between access points, they are switched to the VLAN with the lowest load based on the VLAN load weight of the roaming target area. This enables seamless terminal roaming, synchronously updating traffic forwarding rules and IP addresses, ensuring uninterrupted network connectivity and smooth transmission during terminal movement. It adapts to the high mobility of terminals in high-density scenarios, while avoiding sudden overload of a single VLAN in the target area caused by a large number of terminals roaming simultaneously. This ensures load stability in the roaming target area, extending load balancing management from static terminal access to dynamic terminal movement, achieving dynamic load balancing across all scenarios and time periods in high-density open Wi-Fi environments. Ultimately, it enables precise management of VLAN resources.

[0020] It should be understood that the descriptions of technical features, technical solutions, beneficial effects, or similar language in this application do not imply that all features and advantages can be achieved in any single embodiment. Rather, it is understood that the description of a feature or beneficial effect means that a specific technical feature, technical solution, or beneficial effect is included in at least one embodiment. Therefore, the descriptions of technical features, technical solutions, or beneficial effects in this specification do not necessarily refer to the same embodiment. Furthermore, the technical features, technical solutions, and beneficial effects described in this embodiment can be combined in any suitable manner. Those skilled in the art will understand that embodiments can be implemented without one or more specific technical features, technical solutions, or beneficial effects of a particular embodiment. In other embodiments, additional technical features and beneficial effects may be identified in specific embodiments that do not embody all embodiments. Attached Figure Description

[0021] Figure 1 An application environment diagram of a VLAN resource management method provided in this application embodiment; Figure 2 A flowchart illustrating a VLAN resource management method provided in an embodiment of this application; Figure 3 A structural diagram of a VLAN resource management device provided in an embodiment of this application; Figure 4 This is a schematic diagram of a computing device provided in an embodiment of this application. Detailed Implementation

[0022] The terms "first," "second," and "third," etc., used in this application specification and accompanying drawings are used to distinguish different objects, not to limit a specific order.

[0023] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of the terms "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0024] To ensure clarity and conciseness in the description of the following embodiments, a brief introduction to the related technologies is given first: Virtual LAN (VLAN) is a technology that creates virtual workgroups by logically rather than physically dividing devices within a local area network into segments. It can effectively isolate network traffic, reduce broadcast storms, improve network security and management efficiency, and is the basic unit for network resource partitioning and management in high-density Wi-Fi scenarios.

[0025] A VLAN resource pool is a collection of flexible resources that provides global and centralized management of all available VLAN resources in a network. It breaks away from the traditional fixed VLAN allocation model and can dynamically create, delete, and reuse VLAN resources based on real-time network load, thereby achieving global scheduling and optimized configuration of resources.

[0026] Network area division is a process that divides the entire network into multiple independent network partitions based on the physical layout of high-density Wi-Fi scenarios and the coverage of access points (APs). Each partition corresponds to a dedicated subset of VLANs, enabling fine-grained regional management of VLAN resources and avoiding network load pressure caused by cross-regional data forwarding.

[0027] Load weight is a unified quantitative indicator calculated by standardizing and weighting the two main dimensions of the number of access terminals and bandwidth utilization. It is used to measure the actual load level of a single VLAN and is the main basis for determining VLAN overload, idleness and resource scheduling.

[0028] Terminal roaming is the network behavior of a terminal that has been connected to the network seamlessly switching from the currently connected access point to another access point within the coverage area while moving. It is a typical feature of high-density scenarios such as large venues and transportation hubs, and it places high demands on the dynamic adaptation capability of VLAN resources.

[0029] In high-density open Wi-Fi scenarios such as large venues, commercial complexes, and transportation hubs, the number of terminal accesses experiences explosive growth, uneven distribution, and high mobility. Network load exhibits significant dynamism and suddenness. VLANs, as the primary means of network resource management, directly determine network operating efficiency and user experience. Existing technologies often employ static configuration or semi-static optimization modes for VLAN resource management. The design flaws of these solutions prevent them from adapting to the dynamic load characteristics of high-density scenarios, primarily in three aspects: First, resource configuration is fixed. Traditional solutions pre-allocate fixed VLAN resources based on scenario-estimated load, lacking elastic expansion and idle resource reclamation mechanisms. When terminals are concentrated in hotspot areas, VLAN overload is easily triggered, while a large number of VLANs remain idle in non-hotspot areas, resulting in low resource utilization. The root cause lies in the failure to achieve global pooling and dynamic scheduling of VLAN resources. Second, load assessment is one-sided. Some semi-static solutions rely solely on the number of access terminals or... Using bandwidth utilization as a single indicator to judge load status without comprehensively considering the dual burden of terminal access and bandwidth usage can easily lead to misjudgment of load, resulting in a disconnect between management decisions and the actual network operation status. Thirdly, terminal scheduling is rigid. New terminal access is assigned VLANs according to fixed rules without taking into account the real-time VLAN load in the area for optimal allocation. When terminals roam, only the access point is switched without readjusting the VLANs, which can easily cause sudden VLAN overload in the target area. At the same time, cross-regional terminal access will increase the data forwarding pressure of the core layer, resulting in network latency and packet loss. The essence is that a dynamic VLAN allocation and switching mechanism based on terminal location and regional load has not been established.

[0030] The aforementioned issues ultimately prevent existing VLAN resource management solutions from achieving network load balancing in high-density scenarios. This not only results in a significant waste of VLAN resources but also leads to problems such as bandwidth saturation, transmission bottlenecks, and roaming disconnections, drastically reducing network service quality and user experience. To address this, this application proposes a dynamic management solution based on VLAN resource pools. Through pooled management, comprehensive load weight determination, elastic resource scheduling, and dynamic terminal allocation / switching, this solution resolves the pain points of existing technologies and achieves refined management of VLAN resources in high-density Wi-Fi scenarios.

[0031] In view of this, embodiments of this application provide a VLAN resource management method. To make the technical solution of this application clearer and easier to understand, the application scenarios of the technical solution of this application are described below with reference to the accompanying drawings. Figure 1 As shown, this figure is an application environment diagram provided by an embodiment of this application.

[0032] In this application environment, server 104 is responsible for the entire process of real-time collection, load calculation, dynamic scheduling, and management and control decision-making of VLAN resources across the entire network. Terminal 102 establishes a two-way communication connection with server 104. On the one hand, it can send management and control instructions such as network area division rules, various load threshold configurations, and initial parameters of VLAN resource pools to server 104. On the other hand, server 104 will simultaneously push information such as the real-time load status of VLANs across the entire network, resource scheduling records, terminal access / roaming allocation results, and abnormal load alarms to terminal 102, so that operation and maintenance personnel can monitor the network operation status in real time and flexibly adjust the management and control policies through terminal 102 according to actual needs.

[0033] To make the technical solution of this application clearer and easier to understand, the following describes a VLAN resource management method provided by this application embodiment, using server 104 as the execution subject of the VLAN resource management method, in conjunction with the above application scenario. Figure 2 As shown, this figure is a flowchart illustrating a VLAN resource management method provided in an embodiment of this application. The VLAN resource management method includes: S201. Real-time collection of the number of access terminals and bandwidth utilization rate of each VLAN in the VLAN resource pool.

[0034] The VLAN resource pool is a subset of VLANs for each network area, and each VLAN subset corresponds to a preset threshold for the number of access terminals and a threshold for bandwidth utilization.

[0035] A VLAN resource pool is a collection of flexible resources that provides unified and centralized management of all VLAN (Virtual Local Area Network) resources in a network. It is not a single VLAN, but rather an integration of all available VLAN resources, which can dynamically create, delete, and reuse VLANs based on network load.

[0036] A network area is an independent network partition defined by the physical layout or network coverage of a high-density open Wi-Fi scenario, such as the grandstand area or entrance area of ​​a large stadium, or different floors of a commercial complex. The network load of each area is independently counted and managed.

[0037] A VLAN subset is a group of VLAN resources that are separately divided from the VLAN resource pool for each network area and are dedicated to serving that area. Each VLAN subset is independent of the others and only carries the terminal access needs of the corresponding network area, avoiding the network load pressure caused by cross-regional data forwarding.

[0038] The access terminal threshold is the maximum number of access terminals preset for a single VLAN within each VLAN subset, and it is one of the quantitative indicators for judging whether a VLAN is overloaded.

[0039] The bandwidth utilization threshold is the maximum bandwidth usage limit preset for a single VLAN within each VLAN subset. It works in conjunction with the access terminal number threshold to determine the load status of the VLAN.

[0040] The number of access terminals refers to the number of smart terminals (mobile phones, computers, tablets, etc.) that are actually connected to a certain VLAN.

[0041] Bandwidth utilization rate is the ratio of the bandwidth actually used by a VLAN to the total preset bandwidth capacity of that VLAN.

[0042] For example, to collect load data for all VLANs within the VLAN resource pool in real time, and with the collection process deeply integrated with pre-defined network area and VLAN subset partitioning rules, the overall VLAN resources are first managed in a unified pool to create a flexible VLAN resource pool. Based on the actual network layout of a high-density open Wi-Fi scenario, the VLAN resource pool is divided into multiple VLAN subsets corresponding to different physical areas. For each VLAN subset, a threshold for the number of access terminals and a threshold for bandwidth utilization are preset for each individual VLAN. These two thresholds serve as the criteria for subsequently determining whether the VLAN load is overloaded or idle. During the collection phase, the system continuously and in real-time acquires two key load data points for each VLAN in the VLAN resource pool: the current actual number of access terminals and the bandwidth utilization rate of that VLAN. This provides accurate, real-time, and fundamental data support for subsequent calculation of VLAN load weights, dynamic VLAN resource scheduling, and load balancing adjustments.

[0043] S202. Determine the load weight corresponding to each VLAN based on the number of access terminals and bandwidth utilization rate of each VLAN.

[0044] Optionally, the load weight is calculated by weighting the ratio of the number of access terminals to the threshold number of access terminals in the corresponding VLAN, and the ratio of the bandwidth utilization rate to the threshold bandwidth utilization rate of the corresponding VLAN.

[0045] Load weight is a unified quantitative indicator that comprehensively measures the actual load level of a single VLAN. It is calculated by standardization and weighting based on two main load dimensions: the number of access terminals and bandwidth utilization. The value directly reflects the VLAN load level and is the main basis for subsequent load judgment and resource scheduling.

[0046] Weighted combination calculation is a method of calculating the final load weight by assigning preset weight coefficients to two standardized load proportions (the proportion of access terminals and the proportion of bandwidth utilization) and then summing them by weight. It can emphasize different load dimensions according to the needs of the scenario.

[0047] For example, to eliminate measurement discrepancies across different data dimensions and achieve accurate comparison and judgment of VLAN load levels, the system, after acquiring the actual number of access terminals and bandwidth utilization rate of each VLAN in the VLAN resource pool in real time, first standardizes these two data points: dividing the actual number of access terminals in a single VLAN by its access terminal threshold yields the access terminal percentage; dividing the actual bandwidth utilization rate of that VLAN by its bandwidth utilization threshold yields the bandwidth utilization percentage. Then, according to pre-defined weight allocation rules, corresponding weight coefficients are configured for these two percentages, and a weighted summation is performed to calculate the load weight value unique to each VLAN. This calculation method integrates information from two main load dimensions—terminal access and bandwidth usage—and adapts to the load management needs of high-density open Wi-Fi scenarios through weight coefficients. This ensures that the calculated load weight accurately reflects the actual load status of the VLAN, providing a direct and quantitative basis for comparison and judgment in subsequent load balancing adjustments and dynamic VLAN resource scheduling.

[0048] For example, the calculation process for the unique load weight corresponding to a single VLAN can be represented as: Load weight = α × percentage of connected terminals + β × bandwidth utilization Where α is the weighting coefficient corresponding to the proportion of access terminals; β is the weighting coefficient corresponding to the proportion of bandwidth utilization; the settings of α and β can be adjusted according to different load dimensions based on the needs of the scenario, such as α=0.6, β=0.4.

[0049] S203. For any VLAN, when the load weight of the VLAN exceeds the first threshold, create a new VLAN in the network area corresponding to the VLAN and add it to the VLAN resource pool.

[0050] The first threshold is a pre-defined load weight threshold, which is a quantitative standard for determining whether a VLAN is overloaded. When the VLAN load weight exceeds this value, subsequent resource expansion scheduling operations are triggered. For example, the first threshold is 80%.

[0051] The corresponding network area is a dedicated network partition (such as the grandstand area of ​​a large stadium or the waiting area of ​​a transportation hub) that is pre-defined for high-density Wi-Fi scenarios to which the overloaded VLAN belongs. It is also the service area that the VLAN is allocated from the VLAN resource pool. The new VLAN will only serve this area.

[0052] Creating a new VLAN is a process where the system automatically generates a brand new virtual LAN resource unit as a new network bearer node, specifically used to offload the terminal and bandwidth load of the overloaded VLAN in the corresponding network area.

[0053] Adding a VLAN to a VLAN resource pool means incorporating the newly created VLAN into a globally unified VLAN resource pool for centralized management. The new VLAN will be included in the VLAN subset of the corresponding area, and its load data will be collected in real time and used in load weight calculation. The resources can also be scheduled and reused in subsequent scenarios as they change.

[0054] For example, load balancing in overloaded areas is achieved by automatically creating new VLANs, ensuring load distribution across network areas. All operations are based on the global management logic of the VLAN resource pool. After calculating the load weights of all VLANs, the system checks the load status of each VLAN in the VLAN resource pool. If the load weight of any VLAN exceeds a pre-set first threshold, it is determined that the VLAN is overloaded and can no longer stably handle terminal access demands. At this point, the system immediately triggers an automatic expansion mechanism, automatically creating a new VLAN within the network area served by the overloaded VLAN. This new VLAN is directly incorporated into the global VLAN resource pool for unified management, becoming part of the VLAN subset for that network area. The new VLAN will take over some of the terminal access demands in that area, diverting terminal and bandwidth pressure from the original overloaded VLAN. This achieves elastic scheduling of VLAN resources, allowing the overall load of the corresponding network area to return to a reasonable range, avoiding bandwidth saturation, transmission bottlenecks, and other problems.

[0055] S204. For any VLAN, if the load weight of the VLAN is lower than the second threshold and there is a redundant VLAN in the VLAN resource pool, delete the redundant VLAN.

[0056] One possible approach is to migrate the terminals within a VLAN to a target VLAN in the same network area when the load weight of any VLAN is lower than a second threshold and the number of idle VLANs in the VLAN resource pool exceeds a preset maximum idle number threshold. The VLAN is then deleted after the migration is complete.

[0057] The second threshold is a pre-set load weight threshold, which is a quantitative standard for determining whether a VLAN is in an idle state. When the VLAN load weight is lower than this value, it is determined that the load is too low and there is idle resources. For example, the second threshold is 20%.

[0058] Redundant VLANs are VLANs in the VLAN resource pool whose load weight is below the second threshold, which have been idle for a long time, and whose deletion will not affect the normal network service of the corresponding network area. They are cleaned up for resource reuse.

[0059] Idle VLANs are VLANs in the VLAN resource pool that do not carry any terminal access needs and are in an idle and ready-to-use state. This includes VLANs that have been migrated due to idle load but have not yet been deleted.

[0060] The maximum number of idle VLANs threshold is the upper limit of the number of idle VLANs preset for the VLAN resource pool. It is an auxiliary criterion for triggering the deletion of redundant VLANs, so as to avoid resource waste caused by too many idle VLANs in the resource pool.

[0061] The third threshold is a pre-set load weight threshold, a quantitative standard for determining whether a target VLAN has the capacity to accept terminals. A threshold below this value indicates that the VLAN load is moderate and can safely receive migrated terminals, avoiding overload after acceptance. The third threshold is greater than or equal to the second threshold. For example, the third threshold is 60%.

[0062] The target VLAN is a VLAN that belongs to the same network area as the redundant VLAN, has a load weight lower than the redundant VLAN to be deleted and not higher than the third threshold, and is capable of taking over the normal operation of terminals within the redundant VLAN.

[0063] For example, by deleting redundant VLANs to release idle resources, elastic reuse of VLAN resources is achieved, avoiding resource waste within the resource pool. The deletion operation is performed under the premise of ensuring uninterrupted network service. The system performs load status detection on each VLAN in the VLAN resource pool. When the load weight of any VLAN is detected to be lower than a second threshold, a second determination is made based on the number of idle VLANs in the resource pool: if the number of idle VLANs exceeds a preset maximum idle number threshold, the VLAN is determined to be redundant, triggering the resource reclamation and deletion process. To avoid terminal network interruption during deletion, the system first selects VLANs with load weights lower than the redundant VLAN and not higher than a third threshold within the same network area as the redundant VLAN as target VLANs. Then, all terminals in the redundant VLAN are smoothly migrated to the target VLAN, and the terminal traffic forwarding rules and IP address configurations are updated synchronously to ensure unaffected terminal access. After all terminals have been migrated, the system removes the redundant VLAN from the VLAN subset of the corresponding network area and officially deletes the VLAN. The resources it occupies are released back to the VLAN resource pool as global idle resources for scheduling use by other overloaded network areas, thereby achieving dynamic optimization of the VLAN resource pool and improving overall resource utilization.

[0064] S205. When a new terminal is connected, the VLAN to which the new terminal belongs is assigned according to the access location of the new terminal.

[0065] One possible approach is to determine the network region to which the new terminal belongs based on its access location; and then, based on the network region to which the new terminal belongs, assign the new terminal to the VLAN with the lowest load weight within that network region.

[0066] Among them, the new terminals are smart terminals that are accessing this high-density open Wi-Fi network for the first time and have not yet been assigned a dedicated VLAN and corresponding IP address, such as mobile phones, computers, tablets, IoT devices, etc.

[0067] The access location is the physical location where a new terminal initiates a Wi-Fi access request. This location corresponds to a unique access point (AP) in the network and is the main basis for dividing network areas.

[0068] The network area is a pre-defined exclusive network partition matched according to the AP corresponding to the new terminal's access location. Each network area has a corresponding subset of VLANs and only supports the terminal access needs within that area.

[0069] The VLAN with the lowest load weight is a subset of the VLANs in the network area to which the new terminal belongs. The VLAN with the smallest load weight value means that the current terminal access volume and bandwidth utilization of this VLAN are at the lowest level in the area, and it has sufficient resources to accommodate the new terminal.

[0070] For example, VLANs can be allocated through location matching and load balancing, reducing network pressure from cross-regional data forwarding and balancing the load across VLANs, preventing a single VLAN from becoming overloaded due to continuous new terminal access. When a new terminal initiates a Wi-Fi access request, the system first locates its corresponding access point (AP) based on the terminal's access location and determines the network area to which the new terminal belongs based on the preset matching relationship between the AP and the network area. Then, the system retrieves real-time load weight data for all VLANs within the subset of VLANs in that network area and selects the VLAN with the lowest load weight as the target VLAN. Finally, the new terminal is assigned to this target VLAN, and the core switch dynamically assigns it a dedicated IP address, completing the entire VLAN allocation process for the new terminal. This allocation method ensures that new terminals always access the VLAN with the most abundant resources in their respective areas, guaranteeing both access speed and network experience, while also achieving load balancing of VLANs within the area from the source of terminal access, preventing bandwidth saturation and transmission bottlenecks in local VLANs due to excessive terminal access.

[0071] S206. When a terminal roams between access points, the terminal is switched to the VLAN with the lowest load weight in the roaming target area according to the VLAN load weight of the roaming target area.

[0072] One possible approach is to receive terminal roaming information uploaded by an access point; wherein the terminal roaming information includes the location and signal strength of the target access point associated with the terminal after roaming; based on the load weight of each VLAN in the network area to which the target access point belongs, the VLAN with the lowest load weight is selected as the target VLAN; the traffic forwarding rules are updated to seamlessly switch the terminal to the target VLAN, and the terminal is assigned an IP address corresponding to the target VLAN.

[0073] Optionally, when the load weight of any VLAN exceeds the first threshold, some terminals within the VLAN are migrated to other VLANs in the same network area whose load weight is not higher than the fourth threshold, until the load weight of the VLAN drops below the first threshold; wherein, the migrated terminals are preferentially selected as low-priority service terminals, and the low-priority service terminals are determined according to the terminal service type or user level.

[0074] Terminal roaming is the process by which a terminal that has been connected to the network switches from the currently connected access point (AP) to another access point (AP) within the coverage area while moving, and still maintains the network connection. It is a common terminal behavior in high-density open Wi-Fi scenarios.

[0075] The roaming target area is a pre-defined network partition to which the new target access point (AP) associated with the terminal after roaming belongs. It is the main basis for VLAN reassignment after the terminal roams.

[0076] Terminal roaming information is data uploaded to the system by the access point (AP) when a terminal roams. The core data includes the location of the target access point (to determine the network area after roaming) and the signal strength (to ensure the stability of the terminal's network connection).

[0077] Traffic forwarding rules are system-preset rules used to specify the transmission path of terminal data in the network. They need to be updated synchronously when switching VLANs to ensure that terminal data can be forwarded normally in the new VLAN.

[0078] The fourth threshold is a pre-set load weight threshold, a quantitative standard for determining whether a VLAN in the same area has the capacity to handle the load. A threshold below this value indicates that the VLAN has remaining resources and can accept terminals migrated from overloaded VLANs, preventing itself from becoming overloaded. The fourth threshold is less than or equal to the first threshold. For example, the fourth threshold is 60%.

[0079] Low-priority service terminals are those that can be prioritized for load migration based on their service type (e.g., low priority for general browsing and short videos, and high priority for high-definition live streaming and industrial data transmission) or user level. Migrating these terminals has a smaller impact on user experience.

[0080] For example, the two main operations of seamless VLAN switching during terminal roaming and proactive load balancing during VLAN overload both revolve around load balancing in high-density open Wi-Fi scenarios. They not only ensure network stability during terminal roaming but also solve the problem of sudden VLAN overload, making them an important part of load balancing and roaming collaborative scheduling.

[0081] Seamless VLAN handover process for terminal roaming: When a terminal roams between different access points, the system first receives the terminal roaming information uploaded in real time by the access point (AP). Based on the target access point location, the system accurately matches the network area to which the terminal belongs after roaming (roaming target area). Then, the system retrieves the real-time load weight data of all VLANs in the roaming target area and selects the VLAN with the lowest value as the target VLAN, ensuring that the terminal accesses the VLAN with the most abundant resources in the area. Next, the system automatically updates the terminal's traffic forwarding rules, completing the seamless handover of the terminal to the target VLAN. At the same time, the core switch reassigns a dedicated IP address corresponding to the target VLAN to the terminal. The entire process is uninterrupted, ensuring network smoothness after the terminal roams and avoiding sudden load pressure on a certain VLAN in the target area after the terminal roams.

[0082] Active load balancing process for VLAN overload: This process is an optional supplementary load balancing operation. When the system detects that the load weight of any VLAN exceeds the first threshold (overload judgment standard), it will trigger an active load balancing mechanism. First, within the same network area to which the overloaded VLAN belongs, other VLANs with load weights no higher than the fourth threshold are selected as load balancing targets to ensure that the target VLAN has sufficient resources to accommodate terminals. Then, low-priority service terminals in the area are selected first (based on service type and user level) and migrated from the overloaded VLAN to the selected target VLAN. The terminal migration operation continues until the load weight of the original overloaded VLAN drops below the first threshold and returns to the normal load level. This achieves accurate load balancing within the same network area, avoiding bandwidth saturation, transmission lag, and other problems caused by single VLAN overload. At the same time, by prioritizing the migration of low-priority service terminals, the impact of load adjustment on user experience is minimized.

[0083] Overall, the two operations work together to solve the problem of sudden changes in regional load caused by terminal roaming and to deal with sudden VLAN overload. From the two dimensions of terminal movement and load anomaly, dynamic and precise control of VLAN load in high-density open Wi-Fi scenarios is achieved, ensuring the stability and smoothness of the overall network.

[0084] Based on the above, the VLAN resource management method provides real, real-time, and quantifiable raw data support for all subsequent VLAN resource scheduling operations by collecting the number of access terminals and bandwidth utilization of each VLAN in the VLAN resource pool in real time. This completely eliminates the subjectivity of judging load based on experience in the traditional mode, and allows load management and resource scheduling to have a data-driven and scientific decision-making basis. At the same time, it performs global pooling and unified management of VLAN resources, divides dedicated VLAN subsets according to network areas, and presets access terminal number and bandwidth utilization thresholds for each subset. This not only achieves fine-grained regional management of VLAN resources, avoids cross-regional load interference, and adapts to the characteristics of uneven terminal distribution and drastic load fluctuations in high-density scenarios, but also clarifies the unified quantitative benchmark for subsequent load status judgment, eliminates judgment deviations between different regions and different VLANs, and improves the consistency and accuracy of overall scheduling.

[0085] The load weight of each VLAN is determined based on the number of access terminals and bandwidth utilization, successfully integrating load data from two different dimensions into a unified quantitative indicator. This eliminates the measurement discrepancies between different data, enabling horizontal comparison and vertical tracking of the load level of each VLAN. It solves the problem that a single indicator cannot fully reflect the actual load of a VLAN. The load weight comprehensively considers the two core load dimensions of terminal access and bandwidth usage, which can more realistically and comprehensively reflect the actual carrying pressure of the VLAN. It avoids the one-sidedness of only looking at the number of terminals and ignoring bandwidth saturation or only looking at bandwidth and ignoring terminal overload. This makes subsequent scheduling decisions such as expansion, deletion, and terminal allocation more in line with the actual network operation status. At the same time, this load weight becomes the main judgment indicator for subsequent VLAN resource scheduling operations throughout the entire process, making the overall solution form a complete closed loop of data collection, quantitative analysis, and decision execution, and promoting the upgrade of VLAN load management towards intelligence and automation.

[0086] To address different scenarios—load weight exceeding and falling below thresholds—the system executes operations to create new VLANs and delete redundant VLANs, enabling elastic and dynamic scheduling of VLAN resources. When a VLAN load weight exceeds the first threshold, a new VLAN is created in the corresponding network area and added to the resource pool. This allows for on-demand resource expansion, quickly offloading terminal and bandwidth pressures from overloaded VLANs, and effectively solving the problems of VLAN overload, bandwidth saturation, and transmission congestion in high-density scenarios. Furthermore, the new VLAN is created only in the corresponding area, avoiding resource waste and cross-regional network interference caused by indiscriminate expansion. The new VLAN added to the resource pool can also be continuously scheduled and reused according to load changes, improving resource flexibility. When a VLAN load weight falls below the second threshold and redundancy exists, the redundant VLAN is deleted. This promptly reclaims idle resources and releases them to the global resource pool, allowing idle resources to be used by other areas with high loads. This improves VLAN resource utilization globally, solving the problem of idle resources in non-hotspot areas caused by fixed resource configurations in traditional models. Timely cleanup of redundant VLANs also reduces network device maintenance costs, simplifies VLAN resource management complexity, reduces manual maintenance pressure, and the threshold-based determination method avoids accidental VLAN deletion due to temporary load fluctuations, ensuring network service stability.

[0087] Differentiated VLAN allocation and switching operations are implemented for two scenarios: new terminal access and terminal roaming. This optimizes the entire terminal access experience and achieves precise load balancing at both the terminal access and mobility stages. When a new terminal accesses, it is assigned to the VLAN of its respective network area based on its access location. This avoids cross-regional data forwarding caused by terminals accessing different areas, significantly reducing the forwarding pressure on the network core layer, improving data transmission efficiency, and reducing latency and packet loss caused by cross-regional forwarding. At the same time, it is assigned to the VLAN with the lowest load weight based on the load status within the region, preventing a single VLAN from becoming overloaded due to continuous new terminal access from the source of terminal access, thus achieving regional load balancing. VLAN load balancing: When terminals roam between access points, they are switched to the VLAN with the lowest load based on the VLAN load weight of the roaming target area. This enables seamless terminal roaming, synchronously updating traffic forwarding rules and IP addresses, ensuring uninterrupted network connectivity and smooth transmission during terminal movement. It adapts to the high mobility of terminals in high-density scenarios, while avoiding sudden overload of a single VLAN in the target area caused by a large number of terminals roaming simultaneously. This ensures load stability in the roaming target area, extending load balancing management from static terminal access to dynamic terminal movement, achieving dynamic load balancing across all scenarios and time periods in high-density open Wi-Fi environments. Ultimately, it enables precise management of VLAN resources.

[0088] The above text combined Figures 1 to 2The VLAN resource management method provided in the embodiments of this application has been described in detail. The apparatus and equipment provided in the embodiments of this application will be described below with reference to the accompanying drawings.

[0089] This application also provides a VLAN resource management device, such as... Figure 3 As shown in the figure, this is a schematic diagram of a VLAN resource management device provided in an embodiment of this application. The device includes: The acquisition module 301 is used to collect the number of access terminals and bandwidth utilization rate of each VLAN in the VLAN resource pool in real time. The VLAN resource pool is divided into corresponding VLAN subsets for each network area, and each VLAN subset corresponds to a preset threshold for the number of access terminals and a threshold for bandwidth utilization rate. The weight determination module 302 is used to determine the load weight of each VLAN based on the number of access terminals and bandwidth utilization of each VLAN. The management module 303 is used to create a new VLAN and add it to the VLAN resource pool in the network area corresponding to any VLAN when the load weight of the VLAN exceeds the first threshold; to delete the redundant VLAN when the load weight of any VLAN is lower than the second threshold and there is a redundant VLAN in the resource pool; to assign the VLAN to which the new terminal belongs based on the access location of the new terminal; and to switch the terminal to the VLAN with the lowest load weight in the roaming target area based on the VLAN load weight in that area when the terminal roams between access points.

[0090] In some possible implementations, the control module 303 is specifically used for: Determine the network area to which the new terminal belongs based on its access location; Based on the network region to which the new terminal belongs, the new terminal will be assigned to the VLAN with the lowest load weight within that network region.

[0091] In some possible implementations, the load weight is calculated by weighting the ratio of the number of access terminals to the preset access terminal threshold of the corresponding VLAN, and the ratio of the bandwidth utilization rate to the preset bandwidth utilization rate threshold of the corresponding VLAN.

[0092] In some possible implementations, the control module 303 is specifically used for: When the load weight of any VLAN is lower than the second threshold and the number of idle VLANs in the VLAN resource pool exceeds the preset maximum number of idle VLANs, the terminals in the VLAN will be migrated to the target VLAN in the same network area whose load weight is lower than that VLAN and not higher than the third threshold. After the migration is completed, the VLAN will be deleted.

[0093] In some possible implementations, the control module 303 is specifically used for: Receive terminal roaming information uploaded by the access point; wherein, the terminal roaming information includes the location and signal strength of the target access point associated with the terminal after roaming; Based on the load weight of each VLAN within the network area to which the target access point belongs, the VLAN with the lowest load weight is selected as the target VLAN; Update the traffic forwarding rules to seamlessly switch the terminal to the target VLAN and assign the terminal the IP address corresponding to the target VLAN.

[0094] In some possible implementations, the VLAN resource management device also includes: The migration module is used to migrate some terminals within any VLAN to other VLANs in the same network area whose load weight is no higher than the fourth threshold when the load weight of any VLAN exceeds the first threshold, until the load weight of the VLAN drops below the first threshold. Among them, the terminals to be migrated are preferentially selected as low-priority service terminals, which are determined according to the terminal service type or user level.

[0095] The VLAN resource management device according to the embodiments of this application can correspondingly execute the method described in the embodiments of this application, and the other operations and / or functions of each module / unit of the VLAN resource management device are respectively for implementing Figure 2 For the sake of brevity, the corresponding processes of each method in the illustrated embodiments will not be described in detail here.

[0096] This application also provides a computing device. For example... Figure 4 As shown in the figure, this is a schematic diagram of a computing device provided in an embodiment of this application. The computing device 400 includes a bus 401, a processor 402, a communication interface 403, and a memory 404. The processor 402, the memory 404, and the communication interface 403 communicate with each other via the bus 401.

[0097] Bus 401 can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of representation, Figure 4 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0098] Processor 402 can be any one or more of the following processors: central processing unit (CPU), graphics processing unit (GPU), microprocessor (MP), or digital signal processor (DSP).

[0099] Communication interface 403 is used for communication with external devices.

[0100] Memory 404 may include volatile memory, such as random access memory (RAM). Memory 404 may also include non-volatile memory, such as read-only memory (ROM), flash memory, hard disk drive (HDD), or solid state drive (SSD).

[0101] The memory 404 stores executable code, and the processor 402 executes the executable code to perform the aforementioned VLAN resource management method.

[0102] Specifically, in achieving Figure 3 In the case of the illustrated embodiment, and Figure 3 When the modules or units of the VLAN resource management device described in the embodiment are implemented through software, the execution... Figure 3 The software or program code required for the functions of each module / unit can be partially or wholly stored in the memory 404. The processor 402 executes the program code corresponding to each unit stored in the memory 404 to execute the aforementioned VLAN resource management method.

[0103] This application also provides a computer-readable storage medium. The computer-readable storage medium can be any available medium that a computing device can store, or a data storage device such as a data center containing one or more available media. The available medium can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state drives). The computer-readable storage medium includes instructions that instruct the computing device to execute the aforementioned VLAN resource management method.

[0104] This application also provides a computer program product comprising one or more computer instructions. When the computer instructions are loaded and executed on a computing device, all or part of the processes or functions described in this application are generated.

[0105] The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions may be transmitted from one website, computer, or data center to another website, computer, or data center via wired (e.g., coaxial cable, fiber optic) or wireless (e.g., infrared, wireless, microwave, etc.) means.

[0106] When the computer program product is executed by a computer, the computer performs any of the aforementioned VLAN resource management methods. The computer program product can be a software installation package; when any of the aforementioned VLAN resource management methods needs to be used, the computer program product can be downloaded and executed on the computer.

[0107] The descriptions of the processes or structures corresponding to the above figures each have their own emphasis. For parts of a process or structure that are not described in detail, please refer to the relevant descriptions of other processes or structures.

[0108] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions within the technical scope disclosed in this application should be covered within the scope of protection of this application.

Claims

1. A VLAN resource management method, characterized in that, The method includes: The number of access terminals and bandwidth utilization rate of each VLAN in the VLAN resource pool are collected in real time; wherein, the VLAN resource pool is a VLAN subset divided into corresponding VLANs for each network area, and each VLAN subset corresponds to a preset threshold for the number of access terminals and a threshold for bandwidth utilization rate; The load weight of each VLAN is determined based on the number of access terminals and bandwidth utilization of each VLAN. For any VLAN, when the load weight of the VLAN exceeds the first threshold, a new VLAN is created in the network area corresponding to the VLAN and added to the VLAN resource pool; For any VLAN, if the load weight of the VLAN is lower than the second threshold and there is a redundant VLAN in the VLAN resource pool, the redundant VLAN is deleted. When a new terminal connects, the VLAN to which the new terminal belongs is assigned according to the connection location of the new terminal; When a terminal roams between access points, it is switched to the VLAN with the lowest load weight in the target roaming area, based on the VLAN load weight of that area.

2. The method according to claim 1, characterized in that, The step of allocating the VLAN for the new terminal based on its access location includes: Based on the access location of the new terminal, determine the network area to which the new terminal belongs; Based on the network region to which the new terminal belongs, the new terminal is assigned to the VLAN with the lowest load weight within that network region.

3. The method according to claim 1, characterized in that, The load weight is calculated by weighting the ratio of the number of access terminals to the threshold number of access terminals in the corresponding VLAN, and the ratio of the bandwidth utilization rate to the threshold bandwidth utilization rate of the corresponding VLAN.

4. The method according to claim 1, characterized in that, Deleting the redundant VLAN includes: When the load weight of any VLAN is lower than the second threshold and the number of idle VLANs in the VLAN resource pool exceeds the preset maximum number of idle VLANs, the terminals in the VLAN are migrated to a target VLAN in the same network area whose load weight is lower than that VLAN and not higher than the third threshold. After the migration is completed, the VLAN is deleted.

5. The method according to claim 1, characterized in that, The step of switching the terminal to the VLAN with the lowest load in the area includes: Receive terminal roaming information uploaded by the access point; wherein, the terminal roaming information includes the location and signal strength of the target access point associated with the terminal after roaming; Based on the load weight of each VLAN within the network area to which the target access point belongs, the VLAN with the lowest load weight is selected as the target VLAN; Update the traffic forwarding rules to seamlessly switch the terminal to the target VLAN and assign the terminal the IP address corresponding to the target VLAN.

6. The method according to claim 1, characterized in that, The method further includes: When the load weight of any VLAN exceeds the first threshold, some terminals within the VLAN will be migrated to other VLANs in the same network area whose load weight is not higher than the fourth threshold, until the load weight of the VLAN drops below the first threshold; wherein, the migrated terminals are preferentially selected as low-priority service terminals, and the low-priority service terminals are determined according to the terminal service type or user level.

7. A VLAN resource management and control device, characterized in that, The device includes: The acquisition module is used to collect the number of access terminals and bandwidth utilization rate of each VLAN in the VLAN resource pool in real time; wherein, the VLAN resource pool is divided into corresponding VLAN subsets for each network area, and each VLAN subset corresponds to a preset threshold for the number of access terminals and a threshold for bandwidth utilization rate. The weight determination module is used to determine the load weight of each VLAN based on the number of access terminals and bandwidth utilization of each VLAN. The management module is used to: for any VLAN, when the load weight of the VLAN exceeds a first threshold, create a new VLAN in the network area corresponding to the VLAN and add it to the VLAN resource pool; for any VLAN, when the load weight of the VLAN is lower than a second threshold and there is a redundant VLAN in the VLAN resource pool, delete the redundant VLAN; when a new terminal accesses the network, assign the VLAN to which the new terminal belongs based on the access location of the new terminal; when a terminal roams between access points, switch the terminal to the VLAN with the lowest load weight in the roaming target area based on the VLAN load weight in that area.

8. A computing device, characterized in that, Including memory and processor; The memory stores one or more computer programs, the one or more computer programs including instructions; when the instructions are executed by the processor, the computing device performs the method as described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store a computer program for performing the method as described in any one of claims 1 to 6.

10. A computer program product, characterized in that, The computer program product includes one or more computer instructions that, when executed by a computer, perform the method as described in any one of claims 1 to 6.

Images