Reset control method of wireless access point, access point, switch and system
The wireless access point reset control method based on LLDP message and port status verification solves the problems of difficult access point fault repair and false restart in traditional methods, and realizes efficient and reliable access point recovery and network service quality improvement.
Patent Information
- Application Number
- CN202510943307.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-07-09
- Publication Date
- 2025-09-16
AI Technical Summary
Traditional wireless access points are difficult to repair, with manual repairs being costly and time-consuming. The heartbeat keepalive mechanism can easily lead to false restarts in high-data-throughput scenarios, reducing network service quality.
Through the Link Layer Discovery Protocol (LLDP) message, the switch receives the restart request information sent by the access point, combines the port connection status and quantity verification to ensure the uniqueness and power supply status of the target access point, and performs precise reset control.
It improves access point recovery efficiency, reduces network load, and improves network service quality and user experience.
Smart Images
Figure CN120659078A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of communication technology, and in particular to a reset control method for a wireless access point, an access point, a switch, and a system. Background Art
[0002] With the development of the internet, large-scale wireless network coverage is becoming increasingly common in public places. However, in traditional solutions, when an access point (AP) fails, the only way to repair it is to manually restart the AP after locating the fault. However, since APs are installed in scattered and difficult-to-access locations, manual repair is difficult, costly, and time-consuming, resulting in slow repair speeds.
[0003] Currently, related technologies determine whether an AP is in a faulty state based on a heartbeat keep-alive mechanism or through the interaction of switches with different network layer protocols, and trigger a restart of the AP when it is determined that the AP is in a faulty state. However, in scenarios with high data throughput, the heartbeat keep-alive mechanism and the interaction mechanism of different network layer protocols are easily affected by packet loss or delay, triggering unnecessary restarts, resulting in network interruption and reduced network service quality. Summary of the Invention
[0004] According to various embodiments of the present application, a reset control method for a wireless access point, an access point, a switch, and a system are provided; the problem of false restarts caused by packet loss or delays can be solved, the access point recovery efficiency can be improved, and the network load can be reduced.
[0005] In a first aspect, the present application provides a reset control method for a wireless access point, applied to a switch, the method comprising:
[0006] The method includes receiving a first LLDP message sent by a target access point, the first LLDP message including target access point information and restart request information; matching the target access point information with the neighbor information when the number of access points connected to the port in pre-stored neighbor information meets a preset number standard; obtaining status information of the port connected to the target access point when the target access point information is identical to the access point information in the neighbor information; and controlling the target access point to reset based on the restart request information when the status information indicates a power supply state.
[0007] Through the above method, the switch receives a first LLDP message containing restart request information sent by the access point, and further identifies the number of access points connected to the port. When the number meets a preset quantity standard, the switch matches the target access point information in the first LLDP message with the pre-stored neighbor information. After the match is successful, the switch again determines the status information of the port. When the status information is charging, it controls the access point to reset based on the restart request information. Based on the LLDP message containing restart request information actively sent by the access point, the problem of false restart caused by packet loss or delay of the heartbeat mechanism is solved. Cascading interference is eliminated through quantity judgment, and the uniqueness of the target access point is ensured through identity matching of access point information. And repeated operations are avoided by detecting the port status. Through the above three-level verification, the reliability of access point reset control is ensured, the access point recovery efficiency is improved, and the network load is reduced. The method has strong ease of use and practicality.
[0008] In a possible implementation of the first aspect, before receiving the first LLDP message sent by the target access point, the method further includes:
[0009] Receive a second LLDP message sent by an access point, where the second LLDP message includes access point information; store the access point information and port information connected to the access point as the neighbor information; wherein the second LLDP message is further used to update the neighbor information.
[0010] In a possible implementation manner of the first aspect, the method further includes: when the number of connected access points is 1, determining that the number of connected access points meets a preset number criterion.
[0011] In a possible implementation manner of the first aspect, after receiving the first LLDP message sent by the target access point, the method further includes:
[0012] When the number of connected access points is 0, status information of a port connected to the target access point is acquired; and when the status information indicates a power supply state, the target access point is controlled to be reset based on the restart information.
[0013] In a possible implementation manner of the first aspect, the method further includes: if the second LLDP message is not received within a preset time period, deleting the access point information and port information stored in the neighbor information.
[0014] In a possible implementation manner of the first aspect, after receiving the first LLDP message sent by the target access point, the method further includes:
[0015] Identify a message type field, a vendor identification field, a device type field, and a request information field in the first LLDP message; and determine the target access point information and the restart request information based on the message type field, the vendor identification field, the device type field, and the request information field.
[0016] In a second aspect, the present application provides a reset control method for a wireless access point, which is applied to a target access point. The method includes:
[0017] When fault information is detected and self-recovery fails, generating a first LLDP message; the first LLDP message includes target access point information and restart request information;
[0018] Sending the first LLDP message to the switch; wherein the first LLDP message is used to instruct the switch to match the target access point information with the neighbor information when the number of access points connected to the port in the pre-stored neighbor information meets a preset number standard, and if the target access point information is the same as the access point information in the neighbor information and the port is in a powered state, control the target access point to reset based on the restart request information;
[0019] After the switch control is powered off, a reset operation is performed.
[0020] In a possible implementation of the second aspect, generating the first LLDP message includes:
[0021] Generate a header field of the first LLDP message based on the fault information; the header field includes a message type field and an information length field, the message type field is used to indicate the type of the first LLDP message, and the information length field is used to indicate the length of the information field in the first LLDP message;
[0022] The information field of the first LLDP message is generated based on the fault information, the manufacturer identifier and the device type; the information field includes a manufacturer identifier field, a device type field and a request information field, and the request information field is used to indicate the restart request information.
[0023] In a third aspect, the present application provides a reset control device, applied to a switch, the reset control device comprising:
[0024] A receiving unit, configured to receive a first LLDP message sent by a target access point, where the first LLDP message includes target access point information and restart request information;
[0025] a matching unit, configured to match the target access point information with the neighbor information when the number of access points connected to the port in the pre-stored neighbor information meets a preset number standard;
[0026] a detection unit, configured to obtain status information of a port connected to the target access point when the target access point information is the same as the access point information in the neighbor information;
[0027] A control unit is configured to control the target access point to reset based on the restart request information when the status information indicates a power supply state.
[0028] In a fourth aspect, the present application provides a reset control device, applied to a target access point, the reset control device comprising:
[0029] A message generating unit, configured to generate a first LLDP message when fault information is detected and self-recovery fails; the first LLDP message includes target access point information and restart request information;
[0030] a message sending unit, configured to send the first LLDP message to the switch; wherein the first LLDP message is used to instruct the switch to match the target access point information with the neighbor information when the number of access points connected to the port in the pre-stored neighbor information meets a preset number standard, and to control the target access point to reset based on the restart request information if the target access point information is the same as the access point information in the neighbor information and the port is in a powered state;
[0031] The execution unit is configured to execute a reset operation after the switch is powered off.
[0032] In a fifth aspect, the present application provides a switch, comprising a memory and a processor, wherein the memory stores a computer program, and the processor implements any one of the methods in the first aspect when executing the computer program.
[0033] In a sixth aspect, the present application provides an access point, comprising a memory and a processor, wherein the memory stores a computer program, and the processor implements any one of the methods in the second aspect when executing the computer program.
[0034] In a seventh aspect, the present application provides a reset control system for a wireless access point, comprising the switch described in the fifth aspect and the access point described in the sixth aspect; the switch and the access point are communicatively connected based on a link layer discovery protocol.
[0035] In an eighth aspect, the present application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the method described in any one of the first aspect or the second aspect.
[0036] In a ninth aspect, the present application provides a computer program product, which, when executed on a device, enables the device to execute any of the methods in the first or second aspects above.
[0037] It can be understood that the beneficial effects of the second to ninth aspects mentioned above can be found in the relevant description of the first aspect mentioned above, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS
[0038] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.
[0039] Figure 1 A schematic diagram of the architecture of an access point reset control system provided in an embodiment of the present application;
[0040] Figure 2 A schematic diagram of the implementation flow of the reset control method for a wireless access point provided in an embodiment of the present application;
[0041] Figure 3 A schematic diagram of the structure of a first LLDP message provided in an embodiment of the present application;
[0042] Figure 4 A schematic diagram of the structure of the connection between the switch port and the access point provided in an embodiment of the present application;
[0043] Figure 5 A schematic diagram of the overall flow of the reset control method for a wireless access point provided in an embodiment of the present application;
[0044] Figure 6 A schematic diagram of the implementation flow of the reset control method for a wireless access point provided in an embodiment of the present application;
[0045] Figure 7 A schematic diagram of the structure of a reset control device for a wireless access point provided in an embodiment of the present application;
[0046] Figure 8 A schematic diagram of the structure of a reset control device for a wireless access point provided in an embodiment of the present application;
[0047] Figure 9A schematic diagram of the structure of a switch provided in an embodiment of the present application;
[0048] Figure 10 A schematic diagram of the structure of an access point provided in an embodiment of the present application. DETAILED DESCRIPTION
[0049] The following embodiments of the technical solution of the present application will be described in detail with reference to the accompanying drawings. The following embodiments are only used to more clearly illustrate the technical solution of the present application and are therefore only examples and are not intended to limit the scope of protection of the present application.
[0050] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the art to which this application belongs; the terms used herein are only for the purpose of describing specific embodiments and are not intended to limit this application; the terms "including" and "having" and any variations thereof in the specification and claims of this application and the above-mentioned figure descriptions are intended to cover non-exclusive inclusions.
[0051] In the description of the embodiments of this application, the technical terms "first" and "second" are used only to distinguish different objects and should not be understood to indicate or imply relative importance or implicitly specify the quantity, specific order, or primary and secondary relationship of the indicated technical features. In the description of the embodiments of this application, the meaning of "plurality" is more than two, unless otherwise clearly and specifically defined.
[0052] References herein to "embodiments" mean that a particular feature, structure, or characteristic described in connection with the embodiments may be included in at least one embodiment of the present application. The appearance of this phrase in various places in the specification does not necessarily refer to the same embodiment, nor does it constitute an independent or alternative embodiment that is mutually exclusive of other embodiments. It is understood, both explicitly and implicitly, by those skilled in the art that the embodiments described herein may be combined with other embodiments.
[0053] In the description of the embodiments of this application, the term "and / or" is simply a description of the association relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent the following three situations: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character " / " in this document generally indicates that the associated objects are in an "or" relationship.
[0054] Currently, the self-healing restart process of wireless access points relies on a heartbeat keepalive mechanism or a wireless access controller (AC). The heartbeat keepalive mechanism periodically monitors the AP's status to achieve fault recovery. A switch or management device periodically sends heartbeat detection packets to the access point, which then responds. If no response is received from the access point within multiple consecutive heartbeat cycles, the access point is considered to have entered a faulty state, triggering the self-healing mechanism. Therefore, in situations with high data throughput (such as heavy network traffic) or poor link quality, the heartbeat detection packets may not arrive or be properly processed in a timely manner due to packet loss or latency, causing the access point to be mistakenly identified as faulty and triggering an unnecessary restart. This erroneous restart can reduce network service quality, leading to frequent outages and a poor user experience. Mechanisms that rely on wireless controllers are not suitable for scenarios where only switches and access points exist.
[0055] In response to the above technical problems, the present application proposes a reset control method for wireless access points. By setting a link layer discovery protocol (LLDP) message containing restart request information, when an access point fails, the access point actively sends the LLDP message to the switch. The switch determines the access point that needs to be reset by judging the connection status of the current port and identifying and matching the LLDP message, and controls the access point to power off and perform the reset operation. This method effectively solves the problem of unnecessary restarts caused by repair packages or delays, and is applicable to scenarios where only switches and access points exist. The switch identifies and matches the received LLDP messages and detects the connection status of the ports, thereby improving the reliability and efficiency of access point reset control.
[0056] The specific implementation process of the reset control method for wireless access points is further described below through embodiments. First, the system architecture used by the reset control method is introduced.
[0057] See Figure 1 , Figure 1 This is a schematic diagram of the architecture of the access point reset control system provided in the embodiment of the present application; Figure 1As shown, the system includes a switch 10 and an access point 20. The switch 10 supports Power over Ethernet (POE), and can be referred to as a POE switch. The switch 10 is connected to the access point 20 via a port. The switch 10 and the access point 20 exchange information via a network cable based on a link layer protocol (such as LLDP), and power is supplied to the access point via the network cable, such as Power over Ethernet (PoE). Therefore, even if a fault in the access point causes problems with the Internet Protocol (IP) stack, communication can still be maintained via the network cable based on the link layer discovery protocol.
[0058] Exemplarily, the switch 10 may include multiple ports, each of which may be connected to different devices, such as access points, terminals, and other devices; each port may also be connected to one or more access points; the switch 10 stores information about the access points corresponding to each port, and may maintain device information about the connected access points in the form of neighbor information or a neighbor list.
[0059] Based on the above system architecture, the specific implementation process of the reset control method of the wireless access point is further described below through embodiments.
[0060] See Figure 2 , Figure 2 A schematic diagram of the implementation flow of the reset control method for a wireless access point provided in the embodiment of the application; the execution subject of the method can be Figure 1 The switch 10 shown in FIG. Figure 2 As shown, the method may include the following steps:
[0061] S201: Receive a first LLDP message sent by a target access point, where the first LLDP message includes target access point information and restart request information.
[0062] In some embodiments, the access point monitors whether it has any faults through a built-in monitoring mechanism, a log system, etc., and when a fault is detected, it first tries an internal recovery mechanism, such as automatically restarting the process through a software restart, or recording the error and recovering through a system log; if the access point fails to recover by itself and the fault cannot be eliminated, such as repeated process crashes or resource exhaustion, a first LLDP message is generated, and the switch receives the first LLDP message sent by the target access point through the network cable.
[0063] Exemplarily, the target access point may be the aforementioned access point that has experienced a fault and is unable to recover. The first LLDP message is a restart LLDP message, i.e., a message containing restart request information. The message also carries target access point information, i.e., device identification information, such as the MAC address of the target access point. The switch receives the first LLDP message sent by the target access point, parses the first LLDP message, and obtains the target access point information and the restart request information.
[0064] In some embodiments, before receiving the first LLDP message sent by the target access point, the method further includes: receiving a second LLDP message sent by the access point, the second LLDP message including access point information; and storing the access point information and port information connected to the access point as neighbor information.
[0065] The second LLDP message is also used to update neighbor information.
[0066] Exemplarily, the second LLDP message can be a common LLDP message, that is, a message used to notify the switch of the information of the connected access point; the access point can periodically send the second LLDP message to the switch, such as once every 30 seconds; after receiving the second LLDP message, the switch stores the access point information in the second LLDP message, such as the MAC address information of the access point, and stores the port information and the access point information connected to the port as neighbor information.
[0067] Exemplarily, the switch receives the second LLDP message periodically sent by the access point, and updates the access point information in the stored neighbor information based on the newly received second LLDP message. The switch may include ports, and each port maintains corresponding neighbor information in a list format.
[0068] In some embodiments, the method further includes: deleting the access point information and port information stored in the neighbor information when the second LLDP message is not received within a preset time period.
[0069] For example, under normal circumstances, the access point periodically sends a second LLDP message to the switch, such as at an interval of 30 seconds; if the switch does not receive the second LLDP message within a preset time period, such as more than three times the interval time (the default is 90 seconds), the neighbor information is not updated, and the switch considers that the access point is offline or invalid, and deletes the access point information corresponding to the access point in the neighbor information from the list.
[0070] In some embodiments, after receiving the first LLDP message sent by the target access point, the method further includes:
[0071] Identify the message type field, the vendor identification field, the device type field, and the request information field in the first LLDP message; and determine the target access point information and the restart request information based on the message type field, the vendor identification field, the device type field, and the request information field.
[0072] For example, Figure 3 The structural diagram of the first LLDP message shown in FIG. Figure 3 As shown in (a), the first LLDP message includes a header field and an information field; wherein, Figure 3 As shown in (b), the header field includes a message type field and an information length field. The message type field is used to indicate the type of the first LLDP message, and the information length field is used to indicate the length of the information field, for example, 4 bytes.
[0073] For example, Figure 3 As shown in (b), the information field includes a manufacturer identification field, a device type field, and a request information field; the manufacturer identification field is used to indicate the manufacturer to which the access point belongs; the device type field is used to indicate the device type of the device sending the first LLDP message, such as an access point device; and the request information field is used to indicate restart request information.
[0074] Exemplarily, an LLDP message may be composed of multiple Type-Length-Value (TLV) fields, wherein the first LLDP message is a restart LLDP message including a restart request private TLV; the first LLDP message carries information through a custom TLV field, i.e., the first LLDP message includes a private TLV field, and the extended function based on the private TLV field is defined as follows: Figure 3 The information carried in the information field.
[0075] Among them, Figure 3As shown in (c), the TLV type=127 in the header field is used to indicate that the first LLDP message is a message defined based on a private extended TLV, that is, to indicate the message type of the first LLDP message; the information length field (TLVinformation string length) can be defined as 4 bytes to indicate the total length of the subsequent information field; the manufacturer identification field (organizationally unique identifier, OUI) in the information field is used to indicate the identifier of the organization (or manufacturer) to which the access point belongs, for example, through OUI=0x00, 0x0a, 0xeb, indicating the TPLINK manufacturer, or other values can be used to indicate other manufacturers or organizations; the device type field is used to indicate the device type of the device sending the first LLDP message, for example, through organizationally defined subtype=0x1 to indicate that the device type is an access point device, or other values can be used to agree on corresponding other device types; the request information field (organizationally defined information The request information field (string) is used to represent the content of the request, such as a restart request. To prevent the value (plaintext) of this field from being exposed, the request information field can be represented in the form of a magic number. For example, the plaintext is mapped to a magic number (such as 0x69828079) to ensure the compatibility and security of the message.
[0076] Accordingly, when receiving the first LLDP message, the switch parses the first LLDP message, identifies each field in the first LLDP message, and verifies and confirms that the first LLDP message is an LLDP message requesting a restart.
[0077] By extending the LLDP protocol TLV unit (e.g., TLV = 127) and setting a private TLV structure containing a restart request identifier, the access point can actively trigger the restart process through a standard protocol message. The scalable TLV based on LLDP simplifies the implementation process. Furthermore, the unique identifier of the device manufacturer is embedded in the TLV, and the plaintext used to represent the request is mapped into a magic number to prevent the plaintext from being exposed, thus ensuring the compatibility and security of the message.
[0078] S202: When the number of access points connected to the port in the pre-stored neighbor information meets a preset number standard, match the target access point information with the neighbor information.
[0079] In the embodiment of the present application, in order to ensure that the switch accurately controls the target access point with a fault, it is necessary to re-determine the number of access points connected to the switch port, thereby eliminating interference from cascaded devices and avoiding erroneous reset control of other normal access points.
[0080] like Figure 4 The connection diagram of the switch and access point shown in the figure is that the target switch is a switch that supports POE function. Figure 4 In the scenario shown in (a) of Figure 1, the switch is directly connected to an access point. The switch port is connected to the access point (AP) via a network cable, which provides power to the access point and transmits data. In this scenario, the switch port corresponds to a neighboring device, namely the access point. Therefore, when the restart logic of the access point linkage reset is triggered, it can be confirmed that the reset control is directly effective for the access point.
[0081] However, if Figure 4 In the scenario shown in (b), the access points are connected to a switch through a POE intermediary device. The port of the target switch is connected to the port of the POE transparent transmission switch. Access point 1 (AP1) and access point 2 (AP2) are connected to the target switch through different ports of the POE transparent transmission switch. The POE transparent transmission switch is a simple switch that does not process messages and only forwards them. The corresponding power supply path is: the target switch supplies power to the POE transparent transmission switch, and the POE transparent transmission switch then supplies power to AP1 and AP2 respectively.
[0082] Because the POE transparent switch forwards all packets indiscriminately, the LLDP packets from AP1 and AP2 are both transmitted to the same port on the target switch, resulting in multiple LLDP neighbor devices appearing on that port. Suppose that AP1 experiences a problem and needs to be restarted, while AP2 is operating normally. According to conventional logic, when the target switch receives the restart LLDP packet from AP1 and determines that the relevant devices need to be powered off and restarted, the entire POE transparent switch will be powered off, causing both AP1 and AP2 to power off and restart simultaneously, affecting the healthy AP2.
[0083] To avoid the above situation, a topology verification is performed on the number of connected access points in the neighbor information list maintained by the switch port. Specifically, the number of connected access points is determined to meet a preset number standard. If the number of connected access points is 1, the number of connected access points is determined to meet the preset number standard. The access point is then authenticated and the target access point information is matched with the neighbor information. For example, the MAC address in the first LLDP message is compared with the MAC address of the neighbor information in the list maintained by the switch port to ensure the uniqueness of the target access point.
[0084] Accordingly, if the number of access points connected to a port is greater than one, it indicates a topology problem or interference from LLDP packets from other access points. Therefore, the POE port power-off reset operation is not performed to prevent accidental restarts. This ensures that only the device with the problem (such as AP1) is reset without affecting other normally functioning devices (such as AP2).
[0085] S203: When the target access point information is identical to the access point information in the neighbor information, obtain status information of the port connected to the target access point.
[0086] In an embodiment of the present application, to avoid repeated power-off operations on the access point, after identity verification, the actual power supply status of the switch port is continuously detected. For example, the switch port may be integrated with a current / voltage sensor to determine the port status information by detecting the voltage or current value, thereby confirming that the port is in a power supply state; or, through a command line query, confirm that the displayed port status information is in a power supply state.
[0087] In another scenario, because the switch continuously updates its stored neighbor information based on the second LLDP message sent by the access point, if it continues to fail to receive the second LLDP message from the access point, it deems the access point invalid and deletes the stored neighbor information from the list. For example, within a certain period of time, the switch port determines that the access point has not updated its LLDP information for a long time and deletes it from the list. With no neighbor device information in the list, the switch determines that the number of connected access points on the port is zero. The next second, the switch port receives a restart LLDP message from the access point.
[0088] In the case where the list determines that there are no neighbor devices, but the actual topology contains neighbor devices, even if the number of connected access points is 0, it can be determined that the number of connected access points meets the preset number standard. Furthermore, when the number of access points is determined to be 0 based on the list, the port status information is directly detected to further determine whether there are neighbor devices in the actual topology. For example, if the first LLDP packet is received and the data volume of the neighbor device is 0, and the port status information indicates that the port is in a powered state, it is determined that the actual topology contains a faulty neighbor device.
[0089] S204: When the state information indicates a power supply state, control the target access point to reset based on the restart request information.
[0090] In this embodiment of the present application, the switch identifies the request information field in the information field of the first LLDP message as a restart request. If the switch determines that the port status information indicates that the port is powered, it uses the POE module to power off the port, causing the target access point to perform a power-off restart. By detecting the actual power status of the port, repeated power-off operations are avoided.
[0091] like Figure 5 The overall implementation flow diagram of the reset control method for a wireless access point shown in the figure is based on the same implementation principle as the above embodiment and will not be repeated here. The overall process may include the following steps:
[0092] S501: Receive a restart LLDP message.
[0093] S502: Determine the number of port access points. If the number is 1, execute S503; if the number is 0, execute S504; if the number is greater than 1, end.
[0094] S503: Determine whether the MAC address in the restart LLDP message is the same as the MAC address in the neighbor information. If so, execute S504; if not, end.
[0095] S504, determine whether the port is in power supply state; if so, execute S505; if not, end.
[0096] S505: The POE power is cut off to reset the access point.
[0097] like Figure 6 As shown, the embodiment of the present application provides a schematic diagram of the implementation flow of the reset control method of the wireless access point; the execution subject of the method can be Figure 1 The access point 20 shown in FIG; based on the same implementation principle as the above embodiment, no further details will be given here; Figure 6 As shown, the method may include the following steps:
[0098] S601 : When fault information is detected and self-recovery fails, generate a first LLDP message; the first LLDP message includes target access point information and restart request information.
[0099] S602: Send a first LLDP message to the switch.
[0100] The first LLDP message is used to instruct the switch to match the target access point information with the neighbor information when the number of access points connected to the port in the pre-stored neighbor information meets the preset number standard, and to control the target access point to reset based on the restart request information if the target access point information is the same as the access point information in the neighbor information and the port is in a powered state.
[0101] S603: After the switch is powered off, a reset operation is performed.
[0102] In an embodiment of the present application, a switch receives a first LLDP message containing restart request information sent by an access point, further identifies the number of access points connected to a port, and when the number meets a preset quantity standard, matches the target access point information in the first LLDP message with pre-stored neighbor information. After a successful match, the switch again determines the port status information. When the status information is charging, the switch controls the access point to reset based on the restart request information. Based on the LLDP message containing restart request information actively sent by the access point, the problem of erroneous restart caused by packet loss or delay of the heartbeat mechanism is solved. Cascading interference is eliminated through quantity determination, and the uniqueness of the target access point is ensured through identity matching of access point information. Furthermore, repeated operations are avoided by detecting the port status. Through the above three levels of verification, the reliability of access point reset control is ensured, the access point recovery efficiency is improved, the network load is reduced, and the service quality and user experience are improved.
[0103] It should be understood that the size of the serial numbers of the steps in the above embodiments does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.
[0104] Corresponding to the reset control method of the wireless access point provided in the above embodiment, as shown in FIG. Figure 7 As shown, this is a structural diagram of a reset control device for a wireless access point provided in an embodiment of the present application. For ease of explanation, only the parts related to the embodiment of the present application are shown.
[0105] The reset control device of the wireless access point includes:
[0106] The receiving unit 71 is configured to receive a first LLDP message sent by a target access point, where the first LLDP message includes target access point information and restart request information;
[0107] a matching unit 72 configured to match the target access point information with the neighbor information when the number of access points connected to the port in the pre-stored neighbor information meets a preset number standard;
[0108] A detection unit 73 is configured to obtain status information of a port connected to the target access point when the target access point information is the same as the access point information in the neighbor information;
[0109] The control unit 74 is configured to control the target access point to reset based on the restart request information when the status information indicates a power supply state.
[0110] In one possible implementation, the receiving unit 71 is further used to receive a second LLDP message sent by the access point, where the second LLDP message includes access point information; the device also includes a storage unit, used to store the access point information and port information connected to the access point as the neighbor information; wherein the second LLDP message is also used to update the neighbor information.
[0111] In an implementation of the first aspect, the detection unit 73 is further configured to, when the number of connected access points is 1, determine whether the number of connected access points meets a preset number standard.
[0112] In an implementation of the first aspect, the detection unit 73 is further configured to, when the number of connected access points is 0, obtain status information of a port connected to the target access point; and the control unit 74 is configured to, when the status information indicates a power supply state, control the target access point to reset based on the restart information.
[0113] In an implementation of the first aspect, the storage unit is configured to delete the access point information and port information stored in the neighbor information if the second LLDP message is not received within a preset time period.
[0114] In an implementation of the first aspect, the apparatus further includes an identification unit configured to identify a message type field, a vendor identification field, a device type field, and a request information field in the first LLDP message; and determine target access point information and restart request information based on the message type field, the vendor identification field, the device type field, and the request information field.
[0115] Corresponding to the reset control method of the wireless access point provided in the above embodiment, as shown in FIG. Figure 8 As shown, this is a structural diagram of a reset control device for a wireless access point provided in an embodiment of the present application. For ease of explanation, only the parts related to the embodiment of the present application are shown.
[0116] The reset control device of the wireless access point includes:
[0117] The message generating unit 81 is configured to generate a first LLDP message when fault information is detected and self-recovery fails; the first LLDP message includes target access point information and restart request information;
[0118] a message sending unit 82 configured to send the first LLDP message to the switch; wherein the first LLDP message is configured to instruct the switch to match the target access point information with the neighbor information when the number of access points connected to the port in the pre-stored neighbor information meets a preset number standard, and to control the target access point to reset based on the restart request information if the target access point information is the same as the access point information in the neighbor information and the port is in a powered state;
[0119] The execution unit 83 is configured to execute a reset operation after the switch is powered off.
[0120] In one possible implementation, the message generation unit is further used to generate a header field of the first LLDP message based on the fault information; the header field includes a message type field and an information length field, the message type field is used to indicate the type of the first LLDP message, and the information length field is used to indicate the length of the information field in the first LLDP message; the information field of the first LLDP message is generated based on the fault information, the vendor identifier, and the device type; the information field includes a vendor identifier field, a device type field, and a request information field, and the request information field is used to indicate the restart request information.
[0121] Figure 9 FIG. 1 shows a schematic diagram of the hardware structure of the switch 10 .
[0122] like Figure 9 As shown, the switch 10 of this embodiment includes: at least one processor 91 ( Figure 9 Only one is shown), a memory 92, wherein the memory 92 stores a computer program 93 that can be run on the processor 91. When the processor 91 executes the computer program 93, the steps in the above method embodiment are implemented, such as Figure 2 Alternatively, when the processor 91 executes the computer program 93, the functions of the modules / units in the above-mentioned device embodiments are realized.
[0123] It should be understood that the structure illustrated in the embodiments of the present application does not constitute a specific limitation on the switch 10. In other embodiments of the present application, the switch 10 may include more or fewer components than illustrated, or may combine or separate certain components, or may have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.
[0124] The switch 10 may include, but is not limited to, a processor 91 and a memory 92. Those skilled in the art will appreciate that Figure 9This is only an example of the switch 10 and does not constitute a limitation on the switch 10. The switch 10 may include more or fewer components than shown in the figure, or a combination of certain components, or different components. For example, the server may also include an input sending device, a network access device, a bus, etc.
[0125] The processor 91 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.
[0126] Processor 91 may also include a memory for storing instructions and data. In some embodiments, the memory in processor 91 is a cache memory. This memory can store instructions or data that have just been used or are being recycled by processor 91. If processor 91 needs to use the same instruction or data again, it can directly access the memory. This avoids duplicate accesses, reduces processor 91's latency, and thus improves system efficiency.
[0127] In some embodiments, the memory 92 can be an internal storage unit of the switch 10, such as a hard drive or memory of the switch 10. The memory 92 can also be an external storage device of the switch 10, such as a plug-in hard drive, a Smart Media Card (SMC), a Secure Digital (SD) card, a flash memory card, etc. Furthermore, the memory 92 can include both the internal storage unit of the switch 10 and an external storage device. The memory 92 is used to store an operating system, application programs, a boot loader, data, and other programs, such as computer program code. The memory 92 can also be used to temporarily store data that has been sent or is about to be sent.
[0128] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.
[0129] Figure 10 FIG. 2 shows a schematic diagram of the hardware structure of the access point 20 .
[0130] like Figure 10 As shown, the access point 20 of this embodiment includes: at least one processor 101 ( Figure 10 Only one is shown), a memory 102, wherein the memory 102 stores a computer program 103 that can be run on the processor 101. When the processor 101 executes the computer program 103, the steps in the above method embodiment are implemented, such as Figure 6 Alternatively, when the processor 101 executes the computer program 103, the functions of the modules / units in the above-mentioned device embodiments are realized.
[0131] It should be noted that the structures of the above switches and access points are merely exemplary. Based on different application scenarios, other physical structures may also be included, and the physical structures of the switches and access points are not limited herein.
[0132] In the above embodiments, the description of each embodiment has its own focus. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant description of other embodiments.
[0133] An embodiment of the present application further provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, it can implement the steps in the above-mentioned various method embodiments.
[0134] An embodiment of the present application provides a computer program product. When the computer program product runs on a server, the server can implement the steps in the above-mentioned method embodiments when executing the computer program product.
[0135] If the integrated module / unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present application implements all or part of the process in the above-mentioned embodiment method, and can also be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium, and the computer program can implement the steps of the above-mentioned various method embodiments when executed by the processor. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form, etc. Computer-readable media may include: any entity or device that can carry computer program code, recording medium, U disk, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal and software distribution medium, etc.
[0136] The switches, access points, computer storage media, and computer program products provided in the above-mentioned embodiments of the present application are all used to execute the methods provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects corresponding to the methods provided above, and will not be repeated here.
[0137] The technical features of the above embodiments can be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.
[0138] It should be understood that the above is only to help those skilled in the art better understand the embodiments of the present application, and is not intended to limit the scope of the embodiments of the present application. Based on the above examples given, those skilled in the art can obviously make various equivalent modifications or changes. For example, certain steps in each embodiment of the above detection method may be unnecessary, or certain new steps may be added. Or a combination of any two or any multiple embodiments described above. Such modifications, changes, or combined solutions also fall within the scope of the embodiments of the present application.
[0139] It should also be understood that the division of the modes, situations, categories and embodiments in the embodiments of the present application is only for the convenience of description and should not constitute a special limitation. The features of various modes, categories, situations and embodiments can be combined without contradiction.
[0140] It should also be understood that in the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced to each other, and the technical features in different embodiments can be combined to form new embodiments according to their internal logical relationships.
[0141] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.
[0142] In the embodiments provided in this application, it should be understood that the disclosed devices / network equipment and methods can be implemented in other ways. For example, the device / network equipment embodiments described above are merely illustrative. For example, the division of the modules or units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.
[0143] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of the solution of this embodiment according to actual needs.
[0144] The above-described embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the various embodiments of the present application, and should all be included in the scope of protection of the present application.
[0145] Finally, it should be noted that 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 included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.
Claims
1. A reset control method for a wireless access point, characterized in that: Applied to a switch, the method includes: Receive a first LLDP message sent by a target access point, where the first LLDP message includes target access point information and restart request information; When the number of access points connected to the port in the pre-stored neighbor information meets a preset number standard, matching the target access point information with the neighbor information; When the target access point information is the same as the access point information in the neighbor information, acquiring status information of a port connected to the target access point; When the state information indicates a power supply state, the target access point is controlled to be reset based on the restart request information.
2. The method according to claim 1, characterized in that Before receiving the first LLDP message sent by the target access point, the method further includes: receiving a second LLDP message sent by the access point, where the second LLDP message includes access point information; storing the access point information and the port information connected to the access point as the neighbor information; The second LLDP message is also used to update the neighbor information.
3. The method according to claim 1, characterized in that The method further comprises: When the number of connected access points is 1, it is determined that the number of connected access points meets a preset number standard.
4. The method according to claim 1, wherein After receiving the first LLDP message sent by the target access point, the method further includes: When the number of connected access points is 0, obtaining status information of the port connected to the target access point; When the state information indicates a power supply state, the target access point is controlled to be reset based on the restart request information.
5. The method according to claim 2, characterized in that The method further comprises: If the second LLDP message is not received within a preset time period, the access point information and port information stored in the neighbor information are deleted.
6. The method according to any one of claims 1 to 5, characterized in that After receiving the first LLDP message sent by the target access point, the method further includes: Identify a message type field, a vendor identification field, a device type field, and a request information field in the first LLDP message; The target access point information and the restart request information are determined based on the message type field, the vendor identification field, the device type field, and the request information field.
7. A reset control method for a wireless access point, characterized in that: Applied to a target access point, the method includes: When fault information is detected and self-recovery fails, generating a first LLDP message; the first LLDP message includes target access point information and restart request information; Sending the first LLDP message to the switch; wherein the first LLDP message is used to instruct the switch to match the target access point information with the neighbor information when the number of access points connected to the port in the pre-stored neighbor information meets a preset number standard, and if the target access point information is the same as the access point information in the neighbor information and the port is in a powered state, control the target access point to reset based on the restart request information; After the switch control is powered off, a reset operation is performed.
8. The method according to claim 7, characterized in that The generating of the first LLDP message includes: Generate a header field of the first LLDP message based on the fault information; the header field includes a message type field and an information length field, the message type field is used to indicate the type of the first LLDP message, and the information length field is used to indicate the length of the information field in the first LLDP message; The information field of the first LLDP message is generated based on the fault information, the manufacturer identifier and the device type; the information field includes a manufacturer identifier field, a device type field and a request information field, and the request information field is used to indicate the restart request information.
9. A switch, characterized in that: The method comprises a memory and a processor, wherein the memory stores a computer program, and the processor implements the method according to any one of claims 1 to 6 when executing the computer program.
10. An access point, characterized in that: The method comprises a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the method according to any one of claims 7 to 8 is implemented.
11. A reset control system for a wireless access point, characterized in that: The method comprises the switch according to claim 9 and the access point according to claim 10; the switch and the access point are communicatively connected based on a link layer discovery protocol.
12. A computer program product, characterized in that When the computer program product is run on a device, the device is caused to execute the method according to any one of claims 1 to 6 or 7 to 8.