Configuration method of wireless access point, and system

Abstract

The invention discloses a configuration method of a wireless access point, and a system. The method comprises the following steps that an access controller AC receives a notification which is sent by an AP and which indicates whether the AP has a soft definition network (SDN) pipeline forwarding capability, and, if the AC determines that the AP has the SDN pipeline forwarding capability according to the notification, attribute information, which comprises identification information and address information, of the AP is sent to an SDN configuration management device, and the SDN configuration management device takes the AP as SDN forwarding equipment to perform configuration according to the attribute information.

Description

technical field [0001] The present invention relates to the communication field, in particular to an AP configuration method and system. Background technique [0002] At present, the application layer protocol on the host side of the TCP / IP-based Internet architecture can be easily and flexibly modified and deployed, so the application layer software has been developed by leaps and bounds, and the functions of the application layer have been greatly enriched. But on the other hand, although the design of the protocol at the network layer is simple, it is not scalable and difficult to modify, which leads to the following two problems: On the one hand, many fatal loopholes exposed at the Internet network layer have been difficult to fix for a long time and Improvements, such as network management is difficult to deploy, network security problems are becoming more and more serious, best-effort forwarding strategies cannot provide the quality of service required by users, multic...

AI Technical Summary

Problems solved by technology

But on the other hand, although the design of the protocol at the network layer is simple, it is not scalable and difficult to modify, which leads to the following two problems: On the one hand, many fatal loopholes exposed at the Internet network layer have been difficult to fix for a long time and Improvements, such as network management is difficult to deploy, network security problems are becoming more and more serious, best-effort forwarding strategies cannot provide the quality of service required by users, multicast is difficult to deploy and apply, etc.; Change requirements are difficult to achieve, such as the difficulty of transitioning from IPv4 to IPv6, the increasingly ubiquitous mobility and heterogeneity of access devices pose challenges to network reliability and differentiated service capabilities, and routing is facing scalability issues in large-scale networks Applications such as cloud computing and content distribution put forward new requirements for network forwarding efficiency, etc.

But its flaws are: (1) A certain repair only solves a local problem in a small area; (2) The existing improvement may introduce short-term benefits but be destructive in the long run, such as NAT, or local benefits will damage the whole (3) It may not be easy for a patch to be "compatible" with future modifications; (4) After multiple patches, the Internet has become more and more "thick", complex, and inflexible, beyond the simple design of the Internet. The bearing capacity of the architecture; (5) Some inherent problems in the traditional Internet architecture are difficult to fundamentally solve

However, the shortcomings of this solution are: (1) Since the new network may not be compatible with the existing Internet, the infrastructure of the original network needs to be completely replaced, so there are problems with network deployment and smooth transition; (2) How to establish a new system structure, and whether the establishment of a new architecture can solve the problems faced by the current and future networks is also very risky; (3) It is necessary to rebuild a test network suitable for the new architecture, and the evolution cost is high

From the analysis of various network equipment upgrade cases in the past, the closer the product is to the user side, the more difficult it is to achieve a large-scale simultaneous upgrade. Because the basic network usually rarely deploys enough redundant resources, the lower the network level is, the lower the network level is. more obvious

Images