CN114071798A - Access point device, method, apparatus, and medium - Google Patents

Access point device, method, apparatus, and medium Download PDF

Info

Publication number
CN114071798A
CN114071798A CN202010790735.4A CN202010790735A CN114071798A CN 114071798 A CN114071798 A CN 114071798A CN 202010790735 A CN202010790735 A CN 202010790735A CN 114071798 A CN114071798 A CN 114071798A
Authority
CN
China
Prior art keywords
access point
client device
jitter
point device
cause
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202010790735.4A
Other languages
Chinese (zh)
Inventor
陈立丹
王莉
文华
夏小建
周鸿�
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Arris Enterprises LLC
Original Assignee
Arris Enterprises LLC
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Arris Enterprises LLC filed Critical Arris Enterprises LLC
Priority to CN202010790735.4A priority Critical patent/CN114071798A/en
Priority to EP21755271.0A priority patent/EP4193797A1/en
Priority to PCT/US2021/042961 priority patent/WO2022031460A1/en
Priority to US17/384,082 priority patent/US11785481B2/en
Publication of CN114071798A publication Critical patent/CN114071798A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup
    • H04W76/19Connection re-establishment
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W24/00Supervisory, monitoring or testing arrangements
    • H04W24/02Arrangements for optimising operational condition
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/20Manipulation of established connections
    • H04W76/25Maintenance of established connections
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04BTRANSMISSION
    • H04B17/00Monitoring; Testing
    • H04B17/30Monitoring; Testing of propagation channels
    • H04B17/309Measuring or estimating channel quality parameters
    • H04B17/318Received signal strength
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W24/00Supervisory, monitoring or testing arrangements
    • H04W24/08Testing, supervising or monitoring using real traffic
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W68/00User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H04W68/005Transmission of information for alerting of incoming communication
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W84/00Network topologies
    • H04W84/02Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/10Small scale networks; Flat hierarchical networks
    • H04W84/12WLAN [Wireless Local Area Networks]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W88/00Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08Access point devices

Abstract

The present disclosure relates to access point devices, methods, apparatuses, and media. The access point device includes: a memory having instructions stored thereon; a processor configured to execute instructions stored on the memory to cause the access point device to: determining an unstable client device, a connection between the unstable client device and the access point device being repeatedly disconnected; determining a cause of jitter for the client device based on a disconnect message between the access point device and the client device; and performing an operation for stopping shaking corresponding to the shaking cause.

Description

Access point device, method, apparatus, and medium
Technical Field
The present disclosure relates to access point devices, methods, apparatuses, and media.
Background
In existing Wi-Fi systems, a client device may encounter connection problems in layer 2 connections for some reason. These include improper active disconnection of an Access Point (AP) device, active disconnection of a client device due to background scanning, poor signal of a client device, and Access Point device anomalies (e.g., the Access Point device stops broadcasting). When such connection problems are encountered, the client device may jitter, i.e., the connection between the client device and the access point device is repeatedly disconnected.
Disclosure of Invention
The present disclosure provides a technical solution capable of discovering a cause of jitter of a client device and solving the jitter.
Some aspects of the present disclosure relate to an access point device. The access point device includes: a memory having instructions stored thereon; a processor configured to execute instructions stored on the memory to cause the access point device to: determining an unstable client device, a connection between the unstable client device and the access point device being repeatedly disconnected; determining a cause of jitter for the client device based on a disconnect message between the access point device and the client device; and performing an operation for stopping shaking corresponding to the shaking cause.
In some embodiments, determining an unstable client device comprises: determining a number of jitters of the client device, the number of jitters indicating a number of times that a time interval of two adjacent disconnections of the connection of the client device with the access point device is less than a first predetermined time period; and determining that the client device is an unstable client device if the number of jitters is greater than a jitter threshold.
In some embodiments, the cause of jitter comprises one of an access point device active disconnect, a client device background scan, a client device signal difference, and an access point device anomaly.
In some embodiments, determining the cause of jitter for the client device based on the disconnect message comprises: and under the condition that the disconnection message indicates that the connection between the client device and the access point device is disconnected by the access point device, determining that the jitter reason is the active disconnection of the access point device.
In some embodiments, in the case that the cause of jitter is an active disconnection of an access point device, performing an operation for stopping jitter corresponding to the cause of jitter includes: determining the reason of the jitter as the continuous times of the active disconnection of the access point equipment; and under the condition that the reason of the jitter is that the continuous times of the active disconnection of the access point equipment are greater than the active disconnection threshold value, stopping actively disconnecting the client equipment within a second preset time period.
In some embodiments, determining the cause of jitter for the client device based on the disconnect message comprises: determining that the disconnect message indicates that the connection between the client device and the access point device was disconnected by the client device; determining that an uplink received signal strength at the access point device is greater than a disconnect received signal strength threshold; and determining that the cause of jitter is a client device background scan if the client device is not an expander and an access point device anomaly if the client device is an expander.
In some embodiments, in the case that the cause of jitter is a client device background scan, performing an operation corresponding to the cause of jitter for stopping jitter comprises: ceasing steering operation of the client device for a third predetermined period of time.
In some embodiments, determining the cause of jitter for the client device based on the disconnect message comprises: determining that the disconnect message indicates that the connection between the client device and the access point device was disconnected by the client device; determining that an uplink received signal strength at the access point device is less than a disconnect received signal strength threshold; and determining that the cause of jitter is a client device signal difference.
In some embodiments, in the case that the cause of jitter is a client device signal difference, performing an operation for stopping jitter corresponding to the cause of jitter comprises: in the event that the client device is an expander, a notification of expander signal differences is issued.
In some embodiments, in the case that the cause of jitter is a client device signal difference, performing an operation for stopping jitter corresponding to the cause of jitter comprises: in the event that the client device is not an expander, increasing the transmit power of the access point device or moving the client device to a better-signal channel.
In some embodiments, determining the cause of jitter for the client device based on the disconnect message comprises: determining that the disconnect message indicates that the connection between the client device and the access point device was disconnected by the client device; determining that all client devices connected to the access point device are disconnected; and determining that the cause of jitter is an access point device anomaly.
In some embodiments, in the case that the cause of jitter is an abnormality of an access point device, performing an operation for stopping jitter corresponding to the cause of jitter includes: the access point device is restarted.
In some embodiments, the processor further executes the instructions to cause the access point device to: and sending the jitter reason to the cloud.
Other aspects of the disclosure relate to a method performed by an access point device. The method comprises the following steps: determining an unstable client device, a connection between the unstable client device and the access point device being repeatedly disconnected; determining a cause of jitter for the client device based on a disconnect message between the access point device and the client device; and performing an operation for stopping shaking corresponding to the shaking cause.
Other aspects of the disclosure relate to a non-transitory computer-readable medium having instructions stored thereon that, when executed by a processor of an access point device, cause the processor to: determining an unstable client device, a connection between the unstable client device and the access point device being repeatedly disconnected; determining a cause of jitter for the client device based on a disconnect message between the access point device and the client device; and performing an operation for stopping shaking corresponding to the shaking cause.
Other aspects of the present disclosure relate to an apparatus for wireless communication, comprising means for performing the method of the present disclosure.
Drawings
For a better understanding of the present disclosure, and to show how the same may be carried into effect, reference will now be made, by way of example, to the accompanying drawings, in which:
FIG. 1 shows a Wi-Fi system according to an embodiment of the disclosure;
fig. 2 shows a block diagram of an example of an access point device in accordance with an embodiment of the present disclosure.
Fig. 3 illustrates a method performed by an access point device in accordance with an embodiment of the disclosure;
FIG. 4 illustrates a flow for determining an unstable client device according to an embodiment of the present disclosure;
fig. 5 shows a flow for stopping jitter of a client device in case a connection between the client device and an access point device is disconnected by the access point device, according to an embodiment of the present disclosure;
fig. 6 illustrates a flow of stopping jitter of a client device in a case where a connection between the client device and an access point device is disconnected by the client device, according to an embodiment of the present disclosure;
fig. 7 illustrates a flow of stopping jitter of a client device in the event that the client device disconnects from a 5GHz channel of an access point device in accordance with an embodiment of the disclosure;
fig. 8 illustrates a flow of stopping jitter of a client device in the event that the client device disconnects from a 2.4GHz channel of an access point device in accordance with an embodiment of the disclosure; and
note that like reference numerals refer to corresponding parts throughout the drawings. Further, multiple instances of the same part are specified by a common prefix separated from the instance number by a dash.
Detailed Description
The following detailed description is made with reference to the accompanying drawings and is provided to assist in a comprehensive understanding of various exemplary embodiments of the disclosure. The following description includes various details to aid understanding, but these details are to be regarded as examples only and are not intended to limit the disclosure, which is defined by the appended claims and their equivalents. The words and phrases used in the following description are used only to provide a clear and consistent understanding of the disclosure. In addition, descriptions of well-known structures, functions, and configurations may be omitted for clarity and conciseness. Those of ordinary skill in the art will recognize that various changes and modifications of the examples described herein can be made without departing from the spirit and scope of the disclosure.
Fig. 1 shows a Wi-Fi system 100 according to an embodiment of the present disclosure. Wi-Fi system 100 includes one or more client devices 101, an extender 102, an access point device 103, and a network 104 (e.g., LAN, WAN, etc.). The one or more client devices 101 may include, but are not limited to, personal computers, laptop computers, cell phones, internet of things (IoT) devices, and the like. Access point device 103 may wirelessly communicate with one or more client devices 101, either directly or via extender 102, using wireless communications compatible with the IEEE 802.11 standard. Thus, the wireless communication may occur in, for example, the 2.4GHz, 5GHz, 6GHz, and/or 60GHz frequency bands. (Note that IEEE 802.11ad communications over the 60GHz band are sometimes referred to as "WiGig". in this discussion, these embodiments are also encompassed by "Wi-Fi"). However, a wide variety of frequency bands may be used. The access point device 103 may provide access to the network 104 (e.g., via an ethernet protocol) and may be a stand-alone access point device, may be included with a router and/or modem as a gateway device, or may be implemented on a client device.
Fig. 2 shows a block diagram of an example of an access point device 200 according to an embodiment of the present disclosure. Access point device 103 and/or expander 102 may be implemented in accordance with the architecture of access point device 200. This access point device 200 includes a processing subsystem 210, a memory subsystem 212, and a networking subsystem 214. Processing subsystem 210 includes one or more devices configured to perform computing operations. For example, processing subsystem 210 may include one or more microprocessors, ASICs, microcontrollers, programmable logic devices, Graphics Processor Units (GPUs), and/or one or more Digital Signal Processors (DSPs).
Memory subsystem 212 includes one or more devices for storing data and/or instructions for processing subsystem 210 and networking subsystem 214. For example, memory subsystem 212 may include Dynamic Random Access Memory (DRAM), Static Random Access Memory (SRAM), and/or other types of memory (sometimes collectively or individually referred to as "computer-readable storage media"). In some embodiments, instructions for use in memory subsystem 212 of processing subsystem 210 include: one or more program modules or sets of instructions (such as program instructions 222 or operating system 224), which may be executed by processing subsystem 210. Note that one or more computer programs may constitute a computer program mechanism. Further, instructions in the various modules in memory subsystem 212 may be implemented as follows: a high-level programming language, an object-oriented programming language, and/or in assembly or machine language. Further, the programming language may be compiled or interpreted, e.g., configurable or configured (used interchangeably in this discussion), to be executed by processing subsystem 210.
Additionally, memory subsystem 212 may include mechanisms for controlling access to memory. In some embodiments, memory subsystem 212 includes a memory hierarchy that includes one or more caches coupled to memory in access point device 200. In some of these embodiments, one or more of the caches are located in processing subsystem 210.
In some embodiments, memory subsystem 212 is coupled to one or more high capacity mass storage devices (not shown). For example, the memory subsystem 212 may be coupled to a magnetic or optical drive, a solid state drive, or another type of mass storage device. In these embodiments, the access point device 200 may use the memory subsystem 212 for fast-access storage of frequently used data, while the mass storage device is used to store infrequently used data.
Networking subsystem 214 includes one or more devices configured to couple to and communicate over a wired and/or wireless network (i.e., to perform network operations), including: control logic 216, interface circuitry 218, and one or more antennas 220 (or antenna elements). (although fig. 2 includes one or more antennas 220, in some embodiments, the access point device 200 includes one or more nodes, such as node 208, e.g., a pad, that may be coupled to the one or more antennas 220. thus, the access point device 200 may or may not include one or more antennas 220.) for example, the networking subsystem 214 may include a bluetooth networking system, a cellular networking system (e.g., a 3G/4G/5G network, such as UMTS, LTE, etc.), a USB networking system, a networking system based on the standards described in IEEE 802.11 (e.g., a Wi-Fi networking system), an ethernet networking system, a wide area network interface circuit, an interface circuit for connecting to the internet (e.g., via an Internet Service Provider (ISP) or via Multiple System Operator (MSO) equipment), and/or another networking system.
Networking subsystem 214 includes hardware processors, controllers, radios/antennas, jacks/plugs, and/or other devices for coupling to, communicating over, and processing network system data and events for each supported network system. Note that the mechanisms sometimes used to couple to, communicate over, and process data and events on the network for each network system are collectively referred to as the "network interfaces" of the network systems.
Within access point device 200, processing subsystem 210, memory subsystem 212, and networking subsystem 214 are coupled together using bus 228. Bus 228 may include electrical, optical, and/or electro-optical connections that subsystems may be used to communicate commands, data, and the like. Although only one bus 228 is shown for clarity, different embodiments may include different numbers or configurations of electrical, optical, and/or electro-optical connections among the subsystems.
In some embodiments, access point device 200 includes a display subsystem 226 for displaying information on a display, which may include a display driver and a display, such as a liquid crystal display, multi-touch screen, or the like.
Access point device 200 may be (or may be included in) any electronic device having at least one network interface. For example, access point device 200 may be (or may be included in): desktop computers, laptop computers, sub-notebooks/netbooks, servers, computers, mainframe computers, cloud-based computers, tablet computers, smartphones, cellular phones, smart watches, wearable devices, consumer electronics, portable computing devices, access points, transceivers, controllers, radio nodes, routers, switches, communication devices, access points, test devices, gateway devices, set-top boxes, smart media devices, and/or other electronic devices.
Although access point device 200 is described using specific components, in alternative embodiments, different components and/or subsystems may be present in access point device 200. For example, access point device 200 may include one or more additional processing subsystems, memory subsystems, networking subsystems, and/or display subsystems. Additionally, one or more of the subsystems may not be present in the access point device 200. Further, in some embodiments, access point device 200 may include one or more additional subsystems not shown in fig. 2. Additionally, although separate subsystems are shown in fig. 2, in some embodiments some or all of a given subsystem or component may be integrated into one or more of the other subsystems or components in access point device 200. For example, in some embodiments, program instructions 222 are included in operating system 224 and/or control logic 216 is included in interface circuitry 218.
Although the discussion herein uses Wi-Fi and/or ethernet communication protocols as illustrative examples, in other embodiments a wide variety of communication protocols, and more generally, communication technologies may be used. Thus, communication techniques may be used in various network interfaces. Further, while some of the operations in the foregoing embodiments are implemented in hardware or software, in general, the operations in the foregoing embodiments may be implemented in a variety of configurations and architectures. Accordingly, some or all of the operations in the foregoing embodiments may be performed in hardware, software, or both. For example, at least some of the operations in the communication techniques may be implemented using program instructions 222, an operating system 224 (such as a driver for the interface circuit 218), or in firmware in the interface circuit 218. Alternatively or additionally, at least some operations in the communication techniques may be implemented in hardware in a physical layer, such as interface circuit 218.
Fig. 3 illustrates a method 300 performed by an access point device in accordance with an embodiment of the disclosure. In step S302, the access point device determines an unstable client device. The connection between the unstable client device and the access point device is repeatedly disconnected. In step S304, the access point device determines a cause of jitter of the client device based on the disconnection message between the access point device and the client device. The cause of jitter may include one of an access point device active disconnect (type I), a client device background scan (type II), a client device signal difference (type III), and an access point device anomaly (type IV). In step S306, the access point device performs an operation for stopping jitter corresponding to the cause of jitter. If the cause of jitter is that the access point device is actively disconnected (type I), measures need to be taken to stop the access point device from actively disconnecting the client device. If the cause of jitter is a client device background scan (type II), indicating that the client device is inclined to connect to a particular channel, then measures need to be taken to stop the access point device from steering the client device. If the cause of jitter is a poor client device signal (type III), measures need to be taken to improve the signal quality of the client device. If the cause of jitter is an anomaly in the access point device (type IV), the access point device needs to be restarted to resume the connection.
In addition, the access point device may also record the jitter cause of the client device in the MIB, TR69, or App or send the jitter cause of the client device to the cloud for further analysis and optimization. Specific implementations of the method 300 are described below in conjunction with fig. 4-8.
Fig. 4 shows a flow 400 for determining an unstable client device according to an embodiment of the disclosure.
At step S402, the access point device determines that its connection with the client device is disconnected. At step S404, the access point device determines whether the time interval between two adjacent disconnections of its connection with the client device is less than a first predetermined time period T1. The first predetermined time period T1 may be defined by the administrator to specify a minimum time interval for two adjacent connections to be allowed. If the time interval between two adjacent disconnections of the connection between the access point device and the client device is less than the first predetermined time period T1, the client device is considered to be jittered once and the flow 400 proceeds to step S406. Otherwise, the flow 400 returns to step S402. In step S406, the access point device determines whether the number of jitters of the client device is greater than a jitter threshold. The jitter threshold refers to the number of jitters required to treat the client device as an unstable client device. If the number of jitters of the client device is greater than the jitter threshold, the process 400 proceeds to step S410. In step S410, the client device is considered as an unstable client device. Otherwise, the flow 400 proceeds to step S408. In step S408, the number of jitters of the client device is increased once.
Fig. 5 shows a flow 500 for stopping jitter of a client device in the event that a connection between the client device and an access point device is broken by the access point device, in accordance with an embodiment of the present disclosure.
In step S502, the access point device determines whether its connection with the client device is disconnected by the access point device based on the disconnection message between the access point device and the client device. In some embodiments of the present disclosure, if the connection between the access point device and the client device is disconnected by the access point device, the access point device may determine that the cause of the jitter is the active disconnection of the access point device (type I) immediately after step S502, and then perform an operation for stopping the jitter by performing the following steps S504 to S508.
In some embodiments of the present disclosure, if the connection between the access point device and the client device is broken by the access point device, the flow 500 proceeds to step S504. In step S504, the access point device determines whether the cause of jitter is whether the consecutive number of times the access point device actively disconnects is greater than an active disconnection threshold. The active disconnect threshold specifies a maximum number of times the access point device can actively disconnect the client device. If the jitter cause is that the number of consecutive times that the access point device is actively disconnected is greater than the active disconnection threshold, the process 500 proceeds to step S506. In step S506, the access point device determines that the cause of the jitter is the active disconnection (type I) of the access point device, and stops actively disconnecting the client device for a second predetermined time period T2. The second predetermined time period T2 is a predetermined time period that prevents the access point device from actively disconnecting the client device. Otherwise, the flow 500 proceeds to step S508. In step S508, the access point device determines only that the cause of jitter is an active disconnection of the access point device (type I).
Fig. 6 shows a flow 600 of stopping jitter of a client device in the event that a connection between the client device and an access point device is broken by the client device, in accordance with an embodiment of the present disclosure.
In step S602, the access point device determines whether its connection with the client device is disconnected by the client device based on the disconnection message between the access point device and the client device. If the connection between the access point device and the client device is broken by the client device, the flow 600 proceeds to step S604. In step S604, the access point device determines whether the client device is an expander.
If it is determined in step S604 that the client device is an extender, the flow 600 proceeds to step S606. In step S606, the access point device determines whether the uplink received signal strength (e.g., uplink RSSI) at the access point device is greater than a disconnect received signal strength threshold (e.g., disconnect RSSI threshold). As discussed herein, uplink received signal strength at an access point device refers to the strength of a signal received by the access point device from a client device. The disconnect received signal strength threshold is a received signal strength value that triggers disconnection of the client device. If the uplink received signal strength at the access point device is greater than the disconnected received signal strength threshold, the process 600 proceeds to step S612. In step S612, the access point device determines that the cause of the jitter is an access point device abnormality (type IV), and restarts the access point device. By restarting the access point device, the access point device can be enabled to recover by itself when the access point device is abnormal.
If the uplink received signal strength at the access point device is not greater than the disconnected received signal strength threshold, the process 600 proceeds to step S608. In step S608, the access point device determines that the cause of jitter is a client device signal difference (type III), and issues a notification of the expander signal difference. The notification may be sent to the cloud, a controller of the access point device, or displayed on a display of the access point device to notify a manager of the expander of the signal difference received by the access point device from the expander. The extender manager may adjust the extender position or perform maintenance on the extender to improve the signal quality of the extender.
If it is determined in step S604 that the client device is not an extender, the flow 600 proceeds to step S610. In step S610, the access point device determines whether all client devices are disconnected. If all client devices are disconnected, process 600 proceeds to step S612. In step S612, the access point device determines that the cause of the jitter is an access point device abnormality (type IV), and restarts the access point device. By restarting the access point device, the access point device can be enabled to recover by itself when the access point device is abnormal.
If not all client devices are disconnected, flow 600 proceeds to step S614 and step S616. In step S614, the access point device determines whether the client device is disconnected from the 5GHz channel. If the client device is disconnected from the 5GHz channel, process 600 proceeds to C, and thereafter proceeds to the process illustrated in fig. 7. At step S616, the access point device determines whether the client device is disconnected from the 2.4GHz channel. If the client device is disconnected from the 2.4GHz channel, process 600 proceeds to D, and then proceeds to the process illustrated in fig. 8.
Fig. 7 shows a flow 700 for stopping jitter of a client device in the event that the client device disconnects from a 5GHz channel of an access point device in accordance with an embodiment of the disclosure. In step S702, the access point device determines whether the uplink received signal strength (e.g., uplink RSSI) at the access point device is greater than a 5GHz disconnect received signal strength threshold (e.g., a 5GHz disconnect RSSI threshold). If the uplink received signal strength at the access point device is greater than the 5GHz disconnect received signal strength threshold, then the flow 700 proceeds to step S704. In step S704, the access point device determines that the cause of jitter is client device background scanning (type II) and stops steering the client device to the 5GHz channel for a third predetermined time period T3.
In some embodiments of the present disclosure, if it is determined in step S702 that the uplink received signal strength at the access point device is not greater than the 5GHz disconnect received signal strength threshold, it may be determined immediately after step S702 that the cause of jitter is a client device signal difference (type III), and then an operation for stopping jitter is performed by performing the following steps S706 to S714.
In some embodiments of the present disclosure, if it is determined in step S702 that the uplink received signal strength at the access point device is not greater than the 5GHz disconnect received signal strength threshold, flow 700 proceeds to step S706. At step S706, the access point device determines whether its transmission power reaches a maximum transmission power. If the transmit power of the access point device does not reach the maximum transmit power, the flow 700 proceeds to step S708. At step S708, the access point device increases its transmit power to improve the signal quality of the client device. If the transmit power of the access point device has reached the maximum transmit power, the process 700 proceeds to step S710.
At step S710, the access point device determines whether it currently has active traffic (i.e., ongoing traffic). If the access point device does not currently have active traffic, the flow 700 proceeds to step S712. This way, it is possible to avoid that subsequently performed operations for stopping jitter affect the active traffic of the access point device.
At step S712, the access point device determines whether it is operating on a poor-signal 5GHz channel, e.g., a 5GHz low power channel. If the access point device is operating in a 5GHz channel with poor signal, process 700 proceeds to step S714. In step S714, the access point device determines that the cause of jitter is a client device signal difference (type III) and moves to a better-signal 5GHz channel, e.g., a 5GHz high power channel. If the access point device is not operating in a 5GHz channel with poor signal, process 700 proceeds to step S716. In step S716, the access point device merely determines that the cause of jitter is a client device signal difference (type III).
Fig. 8 shows a flow 800 for stopping jitter of a client device in the event that the client device disconnects from a 2.4GHz channel of an access point device in accordance with an embodiment of the disclosure. At step S802, the access point device determines whether the uplink received signal strength (e.g., uplink RSSI) at the access point device is greater than a 2.4GHz disconnect received signal strength threshold (e.g., a 2.4GHz disconnect RSSI threshold). If the uplink received signal strength at the access point device is greater than the 2.4GHz disconnect received signal strength threshold, the process 800 proceeds to step S804. In step S804, the access point device determines that the cause of jitter is client device background scanning (type II), and stops steering the client device to 2.4GHz for a third predetermined time period T3.
In some embodiments of the present disclosure, if it is determined in step S802 that the uplink received signal strength at the access point device is not greater than the 2.4GHz disconnect received signal strength threshold, it may be determined immediately after step S802 that the cause of jitter is a client device signal difference (type III), and then an operation for stopping jitter is performed by performing the following steps S806 to S814.
In some embodiments of the present disclosure, if it is determined in step S802 that the uplink received signal strength at the access point device is not greater than the 2.4GHz disconnect received signal strength threshold, the flow 800 proceeds to step S806. At step S806, the access point device determines whether its transmission power reaches the maximum transmission power. If the transmit power of the access point device does not reach the maximum transmit power, the process 800 proceeds to step S808. At step S808, the access point device increases its transmit power to improve the signal quality of the client device. If the transmit power of the access point device has reached the maximum transmit power, the process 800 proceeds to step S810.
At step S810, the access point device determines whether it currently has active traffic (i.e., ongoing traffic). If the access point device does not currently have active traffic, the process 800 proceeds to step S812. This way, it is possible to avoid that subsequently performed operations for stopping jitter affect the current active traffic of the access point device.
In step S812, the access point device determines whether it is operating in a 2.4GHz channel with poor signal, e.g., a 2.4GHz edge channel. If the access point device is operating in a 2.4GHz channel with poor signal, process 800 proceeds to step S814. In step S814, the access point device determines that the cause of jitter is client device signal difference (type III) and moves to a better signal channel, e.g., channel 6 at 2.4 GHz. If the access point device is not operating in a 2.4GHz channel with poor signal, process 800 proceeds to step S816. In step S816, the access point device determines only that the cause of jitter is a client device signal difference (type III).
Flow 700 in fig. 7 and flow 800 in fig. 8 may avoid ping-pong effects of the client device (i.e., switching back and forth between 2.4GHz, 5GHz, or other channels) to some extent, thereby making the connection between the client device and the access point device more stable. Further, flow 700 in fig. 7 and flow 800 in fig. 8 may make the connection between the client device and the access point device more stable by moving the access point device to a better-signal channel without affecting the active traffic of the access point device.
The present disclosure may be implemented as any combination of apparatus, systems, integrated circuits, and computer programs on non-transitory computer readable media. One or more processors may be implemented as an Integrated Circuit (IC), an Application Specific Integrated Circuit (ASIC), or a large scale integrated circuit (LSI), a system LSI, or a super LSI, or as an ultra LSI package that performs some or all of the functions described in this disclosure.
The present disclosure includes the use of software, applications, computer programs or algorithms. Software, applications, computer programs, or algorithms may be stored on a non-transitory computer readable medium to cause a computer, such as one or more processors, to perform the steps described above and depicted in the figures. For example, one or more memories store software or algorithms in executable instructions and one or more processors may associate a set of instructions to execute the software or algorithms to provide monitoring and installation enhancements in any number of wireless networks according to embodiments described in this disclosure.
Software and computer programs (which may also be referred to as programs, software applications, components, or code) include machine instructions for a programmable processor, and may be implemented in a high-level procedural, object-oriented, functional, logical, or assembly or machine language. The term "computer-readable medium" refers to any computer program product, apparatus or device, such as magnetic disks, optical disks, solid state storage devices, memories, and Programmable Logic Devices (PLDs), used to provide machine instructions or data to a programmable data processor, including a computer-readable medium that receives machine instructions as a computer-readable signal.
By way of example, computer-readable media can comprise Dynamic Random Access Memory (DRAM), Random Access Memory (RAM), Read Only Memory (ROM), electrically erasable read only memory (EEPROM), compact disk read only memory (CD-ROM) or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to carry or store desired computer-readable program code in the form of instructions or data structures and which can be accessed by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Disk or disc, as used herein, includes Compact Disc (CD), laser disc, optical disc, Digital Versatile Disc (DVD), floppy disk and blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.
In one or more embodiments, use of the terms "can," "operable" or "configured" refer to some apparatus, logic, hardware, and/or element that is designed to be used in a specified manner. The subject matter of the present disclosure is provided as examples of apparatus, systems, methods, and programs for performing the features described in the present disclosure. However, other features or variations are contemplated in addition to the features described above. It is contemplated that the implementation of the components and functions of the present disclosure may be accomplished with any emerging technology that may replace the technology of any of the implementations described above.
Additionally, the above description provides examples, and does not limit the scope, applicability, or configuration set forth in the claims. Changes may be made in the function and arrangement of elements discussed without departing from the spirit and scope of the disclosure. Various embodiments may omit, substitute, or add various procedures or components as appropriate. For example, features described with respect to certain embodiments may be combined in other embodiments.
Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In some cases, multitasking and parallel processing may be advantageous.

Claims (20)

1. An access point device, comprising:
a memory having instructions stored thereon;
a processor configured to execute instructions stored on the memory to cause the access point device to:
determining an unstable client device, a connection between the unstable client device and the access point device being repeatedly disconnected;
determining a cause of jitter for the client device based on a disconnect message between the access point device and the client device; and
and executing the operation for stopping the jitter corresponding to the jitter cause.
2. The access point device of claim 1, wherein determining unstable client devices comprises:
determining a number of jitters of the client device, the number of jitters indicating a number of times that a time interval of two adjacent disconnections of the connection of the client device with the access point device is less than a first predetermined time period; and
determining that the client device is an unstable client device if the number of jitters is greater than a jitter threshold.
3. The access point device of claim 1, wherein the cause of jitter comprises one of an access point device active disconnect, a client device background scan, a client device signal difference, and an access point device anomaly.
4. The access point device of claim 1, wherein determining the cause of jitter for the client device based on the disconnect message comprises:
and under the condition that the disconnection message indicates that the connection between the client device and the access point device is disconnected by the access point device, determining that the jitter reason is the active disconnection of the access point device.
5. The access point device according to claim 1, wherein, in the case that the cause of jitter is an active disconnection of the access point device, performing an operation for stopping jitter corresponding to the cause of jitter comprises:
determining the reason of the jitter as the continuous times of the active disconnection of the access point equipment; and
and under the condition that the reason of the jitter is that the continuous times of the active disconnection of the access point equipment are greater than the active disconnection threshold value, stopping actively disconnecting the client equipment within a second preset time period.
6. The access point device of claim 1, wherein determining the cause of jitter for the client device based on the disconnect message comprises:
determining that the disconnect message indicates that the connection between the client device and the access point device was disconnected by the client device;
determining that an uplink received signal strength at the access point device is greater than a disconnect received signal strength threshold; and
determining the cause of jitter as a client device background scan if the client device is not an expander, and determining the cause of jitter as an access point device anomaly if the client device is an expander.
7. The access point device of claim 1, wherein, in the case that the cause of jitter is a client device background scan, performing an operation for stopping jitter corresponding to the cause of jitter comprises:
ceasing steering operation of the client device for a third predetermined period of time.
8. The access point device of claim 1, wherein determining the cause of jitter for the client device based on the disconnect message comprises:
determining that the disconnect message indicates that the connection between the client device and the access point device was disconnected by the client device;
determining that an uplink received signal strength at the access point device is less than a disconnect received signal strength threshold; and
determining that the cause of jitter is a client device signal difference.
9. The access point device of claim 1, wherein, in the event that the cause of jitter is a client device signal difference, performing an operation corresponding to the cause of jitter for stopping jitter comprises:
in the event that the client device is an expander, a notification of expander signal differences is issued.
10. The access point device of claim 1, wherein, in the event that the cause of jitter is a client device signal difference, performing an operation corresponding to the cause of jitter for stopping jitter comprises:
in the event that the client device is not an expander, increasing the transmit power of the access point device or moving the client device to a better-signal channel.
11. The access point device of claim 1, wherein determining the cause of jitter for the client device based on the disconnect message comprises:
determining that the disconnect message indicates that the connection between the client device and the access point device was disconnected by the client device;
determining that all client devices connected to the access point device are disconnected; and
determining that the cause of the jitter is an anomaly of the access point device.
12. The access point device according to claim 1, wherein, in a case where the cause of jitter is an abnormality of the access point device, performing an operation for stopping jitter corresponding to the cause of jitter includes:
the access point device is restarted.
13. The access point device of claim 1, wherein the processor further executes the instructions to cause the access point device to:
and sending the jitter reason to the cloud.
14. A method performed by an access point device, the method comprising:
determining an unstable client device, a connection between the unstable client device and the access point device being repeatedly disconnected;
determining a cause of jitter for the client device based on a disconnect message between the access point device and the client device; and
and executing the operation for stopping the jitter corresponding to the jitter cause.
15. The method of claim 14, wherein determining unstable client devices comprises:
determining a number of jitters of the client device, the number of jitters indicating a number of times that a time interval of two adjacent disconnections of the connection of the client device with the access point device is less than a first predetermined time period; and
determining that the client device is an unstable client device if the number of jitters is greater than a jitter threshold.
16. The method of claim 14, wherein performing an operation corresponding to the cause of jitter for stopping jitter comprises one or more of:
determining the number of times that the connection is disconnected by the access point device if the cause of the jitter is the active disconnection of the access point device, and stopping the active disconnection of the client device within a second predetermined time period if the number of times that the connection is disconnected by the access point device is greater than an active disconnection threshold;
stopping steering operation on the client device within a third predetermined time period if the cause of jitter is client device background scanning;
in the event that the cause of jitter is a client device signal difference and the client device is an expander, issuing a notification of an expander signal difference;
in the event that the cause of jitter is a client device signal difference and the client device is not an expander, increasing the transmit power of the access point device or moving the client device to a better signal channel; and
and restarting the access point equipment under the condition that the jitter reason is the abnormity of the access point equipment.
17. A non-transitory computer readable medium having instructions stored thereon, which when executed by a processor of an access point device, cause the processor to:
determining an unstable client device, a connection between the unstable client device and the access point device being repeatedly disconnected;
determining a cause of jitter for the client device based on a disconnect message between the access point device and the client device; and
and executing the operation for stopping the jitter corresponding to the jitter cause.
18. The non-transitory computer-readable medium of claim 17, wherein determining an unstable client device comprises:
determining a number of jitters of the client device, the number of jitters indicating a number of times that a time interval of two adjacent disconnections of the connection of the client device with the access point device is less than a first predetermined time period; and
determining that the client device is an unstable client device if the number of jitters is greater than a jitter threshold.
19. The non-transitory computer-readable medium of claim 17, wherein performing operations for stopping jitter corresponding to the cause of jitter comprises one or more of:
determining the number of times that the connection is disconnected by the access point device if the cause of the jitter is the active disconnection of the access point device, and stopping the active disconnection of the client device within a second predetermined time period if the number of times that the connection is disconnected by the access point device is greater than an active disconnection threshold;
stopping steering operation on the client device within a third predetermined time period if the cause of jitter is client device background scanning;
in the event that the cause of jitter is a client device signal difference and the client device is an expander, issuing a notification of an expander signal difference;
in the event that the cause of jitter is a client device signal difference and the client device is not an expander, increasing the transmit power of the access point device or moving the client device to a better signal channel; and
and restarting the access point equipment under the condition that the jitter reason is the abnormity of the access point equipment.
20. An apparatus for wireless communication, comprising means for performing the method of any of claims 14-16.
CN202010790735.4A 2020-08-07 2020-08-07 Access point device, method, apparatus, and medium Pending CN114071798A (en)

Priority Applications (4)

Application Number Priority Date Filing Date Title
CN202010790735.4A CN114071798A (en) 2020-08-07 2020-08-07 Access point device, method, apparatus, and medium
EP21755271.0A EP4193797A1 (en) 2020-08-07 2021-07-23 Avoiding frequent disconnection of wlan terminal
PCT/US2021/042961 WO2022031460A1 (en) 2020-08-07 2021-07-23 Avoiding frequent disconnection of wlan terminal
US17/384,082 US11785481B2 (en) 2020-08-07 2021-07-23 Access point device, method, apparatrus and medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010790735.4A CN114071798A (en) 2020-08-07 2020-08-07 Access point device, method, apparatus, and medium

Publications (1)

Publication Number Publication Date
CN114071798A true CN114071798A (en) 2022-02-18

Family

ID=77338915

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010790735.4A Pending CN114071798A (en) 2020-08-07 2020-08-07 Access point device, method, apparatus, and medium

Country Status (4)

Country Link
US (1) US11785481B2 (en)
EP (1) EP4193797A1 (en)
CN (1) CN114071798A (en)
WO (1) WO2022031460A1 (en)

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2002077453A (en) * 2000-09-01 2002-03-15 Nippon Telegr & Teleph Corp <Ntt> Communication line connecting method of connection-type communication system, user station and center station
CN101146337B (en) * 2006-09-15 2011-04-20 华为技术有限公司 Random access method and system for new access nodes
WO2009012618A1 (en) * 2007-07-25 2009-01-29 Alcatel Shanghai Bell Co., Ltd. A method of transmitting data between a base station and a mobile station and a base station of realizing the method
JP5283925B2 (en) 2008-02-22 2013-09-04 キヤノン株式会社 COMMUNICATION DEVICE, COMMUNICATION DEVICE COMMUNICATION METHOD, PROGRAM, AND STORAGE MEDIUM
US8762546B2 (en) * 2011-12-13 2014-06-24 Motorola Mobility Llc Method and apparatus for adaptive network heartbeat message for TCP channel
US8767695B2 (en) * 2012-06-27 2014-07-01 Google Inc. Measurement-based network selection
US10164858B2 (en) 2016-06-15 2018-12-25 Time Warner Cable Enterprises Llc Apparatus and methods for monitoring and diagnosing a wireless network
CN107223323B (en) * 2016-09-01 2020-11-10 深圳前海达闼云端智能科技有限公司 Network diagnosis method, cloud intelligent robot, network equipment and special network
CN111343655B (en) * 2020-02-28 2024-02-23 深圳市信锐网科技术有限公司 Implementation method of wireless network, implementation device of wireless network and storage medium

Also Published As

Publication number Publication date
EP4193797A1 (en) 2023-06-14
US11785481B2 (en) 2023-10-10
US20220046434A1 (en) 2022-02-10
WO2022031460A1 (en) 2022-02-10

Similar Documents

Publication Publication Date Title
US10334655B2 (en) Electronic apparatus in wireless communication system and mobility measurement method that performs node transfer in response to radio link failure
CN111213407B (en) Apparatus and method for selective probe response suppression based on probe history
US11510138B2 (en) Network slice quota management
US11716272B2 (en) Remedial action based on monitored wireless throughput
CN114258053A (en) Wireless device and method for automatic recovery from failure
US20220210704A1 (en) Communication apparatus, control method, and storage medium
US20220110015A1 (en) Capability management for concurrency mode control
CN111526030B (en) Information processing method and device
WO2018201318A1 (en) Signal measurement method and related equipment
CN114071798A (en) Access point device, method, apparatus, and medium
WO2021145810A1 (en) Conditional reconfiguration
EP4171131A1 (en) Alternative detection of multi-band electronic devices
WO2023071561A1 (en) Radio link failure processing method, and terminal, base station, system, device and medium
EP3291591B1 (en) Method for service transmission and transmission device
EP3849233A1 (en) Detecting network coverage holes and selective client steering
US20230199499A1 (en) Core network node, mec server, external server, communication system, control method, program, and non-transitory recording medium having recorded thereon program
CN113055833B (en) Service optimization method, base station and application layer equipment
US20220308863A1 (en) Cloud-based computer with runtime-mapped software versions
US20230291638A1 (en) Zero-Touch Provisioning of an Access Point by a Switch
US20220113982A1 (en) Selective switching of an active partition in an electronic device
US20230079551A1 (en) Processing of controller-state-message queries
CN114980091A (en) Network device, method, and computer-readable medium for accessing external network
CN114244636A (en) Gateway device, wireless extender, method, apparatus and medium
CN113973065A (en) Electronic device, method, and storage medium for monitoring connection status of client device
WO2023060016A1 (en) High-availability connections using dynamic transparent bridging

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination