CN116089237A - Method, medium, program product and access point for debug log information collection - Google Patents

Abstract

The present disclosure relates to a method, a medium, a program product and an access point for collecting debugging log information. The method includes: receiving, by the access point, configuration information from a remote server, the configuration information being used to configure the access point to collect debug log information related to a network problem occurring in a network in which the access point is located; collecting the debugging log information based on the configuration information; and sending, by the access point, a log file storing the debugging log information to the remote server. Through the above solution, the network server can configure the access point according to the network problem to automatically collect and upload the debugging log information, and the debugging log information in the log file can be remotely accessed to solve the network problem in the network, thereby saving manpower and time.

Description

Method, medium, program product and access point for debug log information collection

technical field

The present disclosure generally relates to the field of communication networks, and more particularly, to a method, medium, program product and access point for collecting debugging log information in the field of communication networks.

Background technique

Due to the popularization of various LAN technologies, enterprises, schools, shopping malls, families, etc. have all deployed LANs within their physical range, and enabled various terminal devices to connect to external networks through access points (APs) in the LAN. . For example, a large number of terminal devices such as laptops, desktop computers, mobile phones, home appliances, and game consoles can be connected to devices such as Wi-Fi routers, Wi-Fi extenders, home gateways, mobile Access points such as broadband routers, and then access to the Internet to enjoy various application services.

The AP at the user's location may encounter various network problems. For example, a terminal device connected to an AP cannot connect to a packet data network such as the Internet and thus cannot access the Internet, or a terminal device cannot access the Internet stably and often goes offline, or the user perceives that the uplink and/or downlink data rate is too small, Or the terminal device cannot connect to the Wi-Fi network, etc. When a user suffers from these problems, the user usually reports to the network operator that provides network access services, so that the network operator can solve the corresponding problem.

The network operator who receives the report usually sends maintenance personnel to the user's residence to debug the AP on site to find network problems. Due to some requirements such as data security, after the AP is released for sale to users, compared with the debug data stream seen in the debugging phase before the release of the AP (also called debug load), you can see it after release A lot of debug log (debug log) information is missing in the debug data stream (also called official load), which makes it difficult for maintenance personnel who go to the site to obtain enough debug log information to analyze network problems. Therefore, the maintenance personnel who go to the residence may need to manually upgrade the official load in the AP to the debug load to obtain the permission to execute debugging commands, and then try to execute different debugging commands to obtain the required debugging log information. Since maintenance personnel have to go to the site for debugging to find specific network problems, this method is very time-consuming and wastes manpower.

Therefore, it is desirable to provide a way to automatically collect debugging log information for analyzing network problems after a network problem occurs without requiring maintenance personnel to go to the site, thereby saving time and manpower.

Contents of the invention

Some aspects of this disclosure relate to an access point. The access point may include: a memory storing instructions; and a processor configured to execute the instructions stored in the memory to cause the access point to perform the following operations. The operations include: receiving configuration information from a remote server, the configuration information being used to configure the access point to collect debug log information related to a network problem (issue) that occurs in a network on which the access point is located; based on the configuration Information collects the debug log information in a log file; and sends the log file storing the debug log information to the remote server, so that the remote server accesses the debug log information in the log file to solve the problem in the network A network problem occurred.

In some embodiments, the debug log information may include information related to the configuration and connection of the access point as well as information related to one or more end devices connected to the access point.

In some embodiments, when the network problem includes a particular end device connected to the access point being unable to connect to the packet data network, the debug log information further includes Address Resolution Protocol (ARP) packets associated with the particular end device, Internet Information of at least one of a Control Message Protocol (ICMP) packet and a Dynamic Host Configuration Protocol (DHCP) packet.

In some embodiments, the debug log information may meet the information level indicated by the configuration information.

In some embodiments, the debug log information is generated by one or more modules in the access point indicated by the configuration information.

In some embodiments, the processor may be further configured to perform the following operations: periodically detect the size of the log file; when the log file reaches a predetermined maximum size, send the log file to the remote server; and create a new log file to store newly collected debug log information.

In some embodiments, the processor may be further configured to: in response to receiving the configuration information, request the remote server to send password data for verifying the legitimacy of the remote server; receiving cryptographic data; determining that the cryptographic data is correct; and collecting the debug log information based on the configuration information in response to determining that the cryptographic data is correct.

In some embodiments, the processor is further configured to refuse to collect the debug log information when it is determined that the cryptographic data is incorrect.

Other aspects of the present disclosure relate to a method, non-transitory computer readable medium, and computer program product for debug log information collection. They can all implement the operations that the access point described above can perform.

Description of drawings

In order to better understand the present disclosure, and to show how it may be practiced, reference will now be made to the accompanying drawings, by way of example, in which:

Fig. 1 shows a schematic diagram of an example of network connections in a scenario of debugging log information collection according to an embodiment of the present disclosure.

FIG. 2 shows a block diagram of an exemplary configuration of the access point in FIG. 1 according to an embodiment of the present disclosure.

Fig. 3 shows a flowchart of a method for collecting debug log information according to an embodiment of the present disclosure.

Fig. 4 shows a flowchart of another method for collecting debug log information according to an embodiment of the present disclosure.

Detailed ways

The following detailed description is made with reference to the accompanying drawings, and is provided to assist in a comprehensive understanding of various example embodiments of the present disclosure. The following description includes various details to aid in understanding, but these are to be regarded as examples only and not for the purpose of limiting the disclosure, which is defined by the appended claims and their equivalents. Words and phrases used in the following description are used only to enable a clear and consistent understanding of the present 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.

Referring first to FIG. 1 , a schematic diagram of an example of network connections in a scenario of debugging log information collection according to an embodiment of the present disclosure is described.

As shown in FIG. 1 , an access point (AP) 110 is located in a user's residence 100 such as a house, factory, office, etc., and the AP 110 builds a network 150, more specifically, a local area network, in the area where its signal reaches. The network 150 where the AP 110 is located may be a wireless local area network supporting, for example, an 802.11 protocol, such as a Wi-Fi network. The AP 110 can enable terminal devices in the network 150 to access the external network 130. n terminal devices 120-1 to 120-n (n is an integer greater than or equal to 1) within the coverage of the network 150 can be connected to the external network 130 by connecting to the AP 110. The terminal devices 120-1 to 120-n can be connected to the AP 110 wirelessly by adopting the 802.11 protocol or the like, or can be connected to the AP 110 by cable or the like. These terminal devices may be one or more of smart phones, tablet computers, notebook computers, desktop computers, smart home appliances with Internet functions, etc., and they can enjoy network services provided by the external network 130 via the AP 110. The AP 110 can be connected to the external network 130 in a wired manner to send and receive data to and from the external network. The external network 130 may be a network including a packet data network such as the Internet or a private network, and devices capable of connecting to the external network 130 may interact with the AP 110, or may interact with the terminal devices 120-1 to 120-n via the AP 110 .

AP 110 in FIG. 1 may have the exemplary configuration shown in FIG. 2 . Although a device for enabling a terminal device to access an external network is referred to herein as an access point (AP), the AP 110 may be, for example, a hardware electronic device that may combine the functions of a modem, an access point, and/or a router. This disclosure also contemplates that AP 110 may include, but is not limited to, a smart media device (SMD) or IP/QAM set-top box (STB) capable of decoding audio/video content and playing content provided by an over-the-top (OTT) provider or multiple system operator (MSO). ) function.

As shown in FIG. 2, the AP 110 includes a user interface 20, a network interface 21, a power supply 22, a wide area network (WAN) interface 23, a memory 24, and a controller 26. User interface 20 may include, but is not limited to, push buttons, keyboards, keypads, liquid crystal display (LCD) devices, cathode ray tube (CRT) devices, thin film transistor (TFT) devices, light emitting diode (LED) devices, high definition (HD) devices Or other similar display devices, including display devices with touch screen capabilities, to allow interaction between the user and the AP 110. Network interface 21 may include various network cards and circuitry implemented in software and/or hardware to enable communication with wireless extender devices and client devices using one or more wireless protocols, such as any Institute of Electrical and Electronics Engineers (IEEE) 802.11 Wi-Fi protocol, Bluetooth protocol, Bluetooth Low Energy (BLE), or any short-range protocol that operates according to a wireless technology standard to exchange data over short distances using any licensed or unlicensed frequency band, Radio Frequency for Consumer Electronics (RF4CE) protocol, ZigBee protocol, Z-wave protocol or IEEE802.15.4 protocol, the licensed or unlicensed frequency band is, for example, Citizen Broadband Radio Service (CBRS) frequency band, 2.4GHz frequency band, 5GHz frequency band, or 6GHz frequency band.

Power supply 22 supplies power to the internal components of AP 110 via internal bus 27. The power source 22 may be a self-contained power source, such as a battery pack, that has an interface for being powered by an electrical charger connected to an outlet (eg, directly or through another device). Power source 22 may also include a rechargeable battery that is removable to allow replacement, such as a nickel cadmium (NiCd), nickel metal hydride (NiMH), lithium (Li) ion, or Li polymer battery. If the AP 110 is a modem or a gateway device, it may include a WAN interface 23, which may include various network cards and circuits implemented in software and/or hardware to realize communication between the router device and an Internet service provider or MSO. communication.

Memory 24 includes a single memory or one or more memories or memory locations, including but not limited to Random Access Memory (RAM), Dynamic Random Access Memory (DRAM), Static Random Access Memory (SRAM), Read Only Memory (ROM) ), Electrically Erasable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Flash memory, logic blocks of Field Programmable Gate Arrays (FPGAs), hard disks, or any other layers of the memory hierarchy . Memory 24 may be used to store any type of instructions, software or algorithms, including software 25 for controlling the general functions and operation of AP 110.

Controller 26 controls the general operation of AP 110 and performs management functions related to other devices in the network, such as extenders and client devices. The controller 26 may include, but is not limited to, a central processing unit (CPU), a hardware microprocessor, a hardware processor, a multi-core processor, a single-core processor, a microcontroller, an application-specific integrated circuit (ASIC), a digital signal processor (DSP) ), or other similar processing devices capable of executing any type of instructions, algorithms, or software for controlling the operations and functions of the AP 110 according to embodiments described in this disclosure. Controller 26 , such as a processor, may include various implementations of digital circuitry, analog circuitry, or mixed-signal (combination of analog and digital) circuitry that perform functions in a computing system. Controller 26 may include, for example, a circuit such as an integrated circuit (IC), a portion or circuit of a single processor core, an entire processor core, a single processor, a programmable hardware device such as an FPGA, and/or include multiple processor system.

Communications may be established between components of AP 110 (e.g., 20-22, 24, and 26) using internal bus 27.

Returning to FIG. 1 , the remote server 140 may be located at the office of the network operator that provides the network access service for the terminal devices 120 - 1 to 120 - n , and of course may also be located at other places, such as the home of maintenance personnel. The remote server 140 can be connected to the AP 110 through the external network 130, or can be connected to the AP 110 through the network operator's private network (not shown). The connection relationship between the remote server 140 and the AP 110 is not particularly limited, as long as the remote server 140 can send information to the AP 110 and receive information from the AP 110.

Although only one AP 110 is shown in the user's residence 100 in FIG. Multiple APs 110 provide more complete coverage, and the remote server 140 can be connected with multiple APs 110 of different users to be able to communicate with more APs 110 to collect more debug log information of APs 110, thereby helping to judge Network issues at multiple APs 110.

When one or more of the terminal devices 120-1 to 120-n cannot access the Internet, or when one or more of the terminal devices 120-1 to 120-n are often offline and need to repeatedly connect to the AP 110 or the external network 130 , or when the communication speed of one or more of the terminal devices 120-1 to 120-n is significantly reduced and the normal speed cannot be restored, or when other abnormal Internet access occurs, the user usually calls the network operator Report network 150 related network issues. A network operator who is aware of the above problems can use the method provided by the embodiment of the present disclosure to use the interaction between the remote server 140 and the AP 110 to remotely and automatically collect debugging log information related to the network problem to help maintenance personnel The network problem analysis avoids the problem in the prior art that maintenance personnel have to go to the user's residence to waste time and manpower, and improves the efficiency of obtaining debugging log information. In the following, a method for collecting debugging log information according to an embodiment of the present disclosure will be described in detail.

A flowchart of a method 300 for collecting debug log information is shown in FIG. 3 . The method 300 can be executed by the access point to remotely collect debugging log information when a network problem occurs in the network where the access point is located, so that network problem analysis can be performed without requiring maintenance personnel to go to the user's residence or the like. In the description of FIG. 3 , reference will be made to the network connection example in FIG. 1 to help those skilled in the art better understand the content of the present disclosure.

In S310, the access point receives configuration information from the remote server, the configuration information is used to configure the access point to collect debugging log information related to network problems occurring in the network where the access point is located.

After any of the above-mentioned network problems occurs in the network 150 in which the terminal equipment is provided with the access service by the AP 110, the user can report the problem to the network operator. It is also possible that AP 110 automatically reports network problems it senses. In response to the occurrence of a network problem, the remote server 140 sends configuration information to the AP 110 that can configure the AP 110 to automatically collect debug log information related to the network problem occurring in the network 150. The debugging log information may be log information generated during the debugging process for network problems.

The configuration information can be sent to the AP 110 in the form of control instructions or messages, so as to trigger the AP 110 to automatically collect debugging log information for network problem analysis, for example, by calling a program pre-stored in the AP 110. For example, the configuration information can be sent from the remote server 140 to the AP 110 through the existing MIB (Management Information Base) or TR069 to configure the AP 110 to collect debug log information related to network problems.

The debug log information collected by remote server 140 configuration AP 110 may include information related to access point configuration and connection as well as information related to one or more end devices connected to AP 110. Information related to access point configuration and connection may include at least one of Wi-Fi profile information, ATOM routing information, ifconfig output information, and bridging information. Among them, the Wi-Fi profile information can indicate the configuration parameter information of the AP 110 itself, the ATOM routing information can indicate the routing forwarding information of the AP 110, the ifconfig output information can indicate the network interface information of the AP 110, and the bridge information can indicate the physical location of the AP 110. connection relationship. The information related to one or more terminal devices connected to the AP 110 may be information related to all terminal devices currently connected to the AP 110, or may be information related to one or more specific terminal devices. The information may include at least one of device information of the terminal device and radio statistical information. The device information can include the MAC (Media Access Control) address, type, and supported protocol of the terminal device, and the radio statistics can include the reference signal received power (RSRP), transmitted signal strength, current rate, and occupancy of the terminal device. Bandwidth, information exchanged with APs, etc.

Information related to one or more terminal devices connected to the AP 110 may be collected periodically, for example, every 20 seconds. The collected information can be stored in log files. Information about access point configuration and connections, since they usually remain unchanged, can be saved in log files at the beginning of the commissioning process instead of being periodically instrumented and logged. Of course, it can also be saved in a log file at a larger period (for example, every 10 minutes, 30 minutes, 1 hour, etc.).

No matter what the network problem occurs, the above-mentioned information related to the configuration and connection of the access point and the information related to one or more terminal devices connected to the AP 110 can be collected by the AP 110 to help in problem analysis. In addition, the above two types of information are not limited to the specific forms listed above, and may also be in other forms conceivable by those skilled in the art.

When the network problem includes that a specific terminal device connected to the AP 110 cannot connect to the packet data network, the remote server 140 can configure the AP 110 to not only collect the above-mentioned information related to the configuration and connection of the access point, but also related to one or more devices connected to the AP 110. Terminal equipment related information, and AP 110 can also be configured to collect ARP (Address Resolution Protocol, Address Resolution Protocol) grouping, ICMP (Internet ControlMessage Protocol, Internet Control Message Protocol) grouping and DHCP (Dynamic Host ConfigurationProtocol, dynamic host configuration protocol) information in at least one of the packets.

For example, if the network problem is that the terminal device 120-1 can connect to the AP 110, but it cannot access the Internet and thus cannot receive network services from the external network 130, then the remote server 140 can send configuration information to the AP 110 to instruct the AP 110 to not only collect Wi -Fi profile information, ATOM routing information, ifconfig output information, bridging information, and the device type, data rate, occupied bandwidth, etc. corresponding to the MAC address of the terminal device 120-1, and the collection is associated with the MAC address of the terminal device 120-1 information such as header information of at least one of the ARP packet, ICMP packet, and DHCP packet. When collecting information such as header information, the AP 110 can monitor only ARP packets, only ICMP packets, only DHCP packets, and only monitor ARP packets for the MAC address of the terminal device 120-1 that cannot access the Internet in different embodiments. Packets and ICMP packets, monitor ARP packets and DHCP packets, monitor ICMP packets and DHCP packets, or monitor ARP packets, ICMP packets, and DHCP packets. The header information of the monitored packets can be stored in the log file to help analyze the reasons for not being able to access the Internet.

The configuration information sent by the remote server 140 to the AP 110 may indicate what information level debug log information needs to be collected by the AP 110. For example, debug log information can involve three levels, which are error level, warning level and normal level. Error level debug log messages correspond to messages that appear when the AP 110 is unable to perform an operation. The debug log information at the warning level corresponds to the information that exists when the operation data is abnormal, and it includes the debug log information at the error level. Common-level debug log information corresponds to all debug log information generated by the AP 110 during debugging. It includes warning level debug log information and error level debug log information.

For another example, the debug log information can involve FATAL (fatal), ERROR (error), WARNING (warning), INFO (information), DEBUG (debugging), TRACE ALL according to the severity of the information. (Track all) these six levels. These levels contain more and more debug log information respectively. For example, when presenting the debug log information of the latter level, besides presenting the debug log information of this level, the debug log information of all previous levels can also be presented. The debug log information at the FATAL level corresponds to the information that needs to restart the relevant service or module or AP device when it occurs; the debug log information at the ERROR level corresponds to the information that an error occurs but the current process or service can continue; the WARNING level The debug log information corresponds to the information given when certain conditions are not met; the debug log information at the INFO level corresponds to some process information in the service; the debug log information at the DEBUG level is more than that at the INFO level, and also includes some call relationship information ;The debug log information of TRACE ALL level corresponds to all the information that can be displayed during the debugging process. Those skilled in the art can understand that more or fewer levels can be set for debugging log information according to actual needs.

Due to the needs of security, etc., the user of the AP may not want the remote server 140 to collect all the debug log information of the AP 110, so the remote server 140 can be requested to only collect the debug log information of a specific level (for example, error level or warning level), thereby Remote server 140 may configure AP 110 to collect corresponding levels of debug log information in response to the request.

The configuration information sent by the remote server 140 to the AP 110 may also indicate which module or modules the AP 110 needs to collect debug log information. Multiple hardware or software modules well known to those skilled in the art may exist in the AP 110, such as a Wi-Fi module, an RPC (Remote Procedure Call, remote procedure call) module, and the like. Different network problems may require collecting debug log information from different modules. The remote server 140 may determine which module or modules need to enable the collection of debugging log information according to specific network problems, so as to make the collected debugging log information more accurate. Alternatively, it may be determined according to specific network problems which module or modules the collection of debug log information may be disabled, so as to avoid collecting too much debug log information and hindering the analysis of network problems.

In S320, the access point collects debugging log information related to network problems based on the configuration information.

In response to receiving the configuration information, the AP 110 can collect the basic information of the local area network, the grouping information for a certain MAC address, the debugging log information of a certain module and/or the debugging log information of a certain level, etc. included in the configuration information, by calling The program for collecting information automatically collects the corresponding debugging log information. The collection of this information may continue on a periodic basis. Different periods may be used to collect different information. The collected information can be collectively stored in log files.

In S330, the access point sends the log file storing the debugging log information to the remote server.

The AP 110 can send log files to the remote server 140 through TFTP (Trivial File Transfer Protocol, simple file transfer protocol), so that the maintenance personnel at the remote server 140 can analyze network problems.

According to the above technical solution, after a network problem occurs in the network where the AP 110 is located, the remote server 140 sends configuration information to the AP 110 to configure the AP 110 to automatically collect debugging log information related to the network problem, so that the AP 110 can automatically collect the debugging log information The information is sent to remote server 140 for analysis. This automatic remote collection of debugging log information avoids the trouble of maintenance personnel going to the user's residence to collect modulation log information on site, saving time and manpower. In addition, since it is possible to control which debug log information AP 110 needs to collect through configuration information, more useful information can be obtained in the debug data flow after AP 110 is released, and more targeted debug log information can be obtained , thus facilitating the analysis of network problems.

FIG. 4 shows a flowchart of a method 400 for collecting debug log information according to an embodiment of the present disclosure. The difference between the method 400 and the method 300 mainly lies in the following two points: first, before the access point collects the debugging log information, it is necessary to judge whether the remote server is legal; File upload.

In S410, the access point receives configuration information from the remote server, the configuration information is used to configure the access point to collect debugging log information related to network problems occurring in the network where the access point is located. This step is basically the same as S310.

In S420, in response to receiving the configuration information, the access point requests the remote server to send password data for verifying the legitimacy of the remote server.

The password data can be the data agreed in advance by the AP 110 and the remote server 140, or the data generated by the AP 110 and the remote server 140 in real time according to a common algorithm, or the data that the legal remote server 140 connects to the network every day when the AP 110 connects to it. Send (for example, send by MIB or TR069) to the data that AP 110 saves at 130 o'clock, this makes every day password data all different. Regardless of the password data generated in any way, the AP 110 can determine whether the server is a legitimate server based on the password data. When the server is the server of the network operator providing the access service through the AP 110, the server is a legal server capable of collecting debug log information.

In S430, the cryptographic data is received by the AP 110 from the remote server.

In S440, the AP 110 determines whether the received password data is correct.

For example, AP 110 may compare received cryptographic data with cryptographic data that confirms that remote server 140 is legitimate. When the two match, the received password data is correct, so the AP 110 determines that the remote server 140 is legal, so that the remote server 140 can be provided with debug log information. Conversely, when the two do not match, the received password data is incorrect, so the AP 110 determines that the remote server 140 is illegal, so there is no need to collect debug log information.

In S450, when the access point determines that the received password data is correct, the access point collects debugging log information based on the configuration information. This step is basically the same as S320.

In S455, when the access point determines that the received password data is incorrect, the access point refuses to collect the debugging log information. At this time, the access point may discard the received configuration information.

In S460, the access point stores the collected debugging log information in a log file.

In S470, the access point periodically detects the size of the log file.

AP 110 may detect the size of the log file, for example, every 10 seconds, 20 seconds, 30 seconds, etc. When the size of the log file reaches a predetermined maximum size (eg, 0.5MB, 1MB, 1.5MB, etc.), the AP 110 may send the log file to the remote server 140.

In S480, in response to determining that the log file has reached a predetermined maximum size, the AP 110 sends the log file to the remote server.

In S490, the access point creates a new log file to store newly collected debugging log information.

After the size of the existing log file reaches the maximum value, the AP 110 can create a new log file to store newly collected debug log information.

Those skilled in the art can understand that not all steps in the above methods may appear in one embodiment at the same time, and they can be flexibly combined to be implemented in different embodiments. Although the AP 110 is shown as only collecting the debug log information in S450, the AP 110 may continuously collect the debug log information without being affected by other steps after determining that the password data is correct. In addition, although S490 is shown to be executed after S480, the access point may execute S490 as long as the size of the log file reaches the maximum size.

Through the execution of the above method, the remote server 140 can not only configure the AP 110 to automatically collect and upload debugging log information according to network problems to save manpower and time, but also provide a security mechanism to prevent the debugging log information from being uploaded to an illegal server, thereby enhancing network security. In addition, since the file is uploaded only when the log file storing the debugging log information meets the predetermined maximum size, the timeliness of collecting the debugging log information and the resource occupied by the transmission can be taken into account.

The present disclosure can be implemented as any combination of apparatuses, systems, integrated circuits and computer programs on a non-transitory computer readable medium. One or more processors may be implemented as an integrated circuit (IC), application specific integrated circuit (ASIC), or large scale integrated circuit (LSI), system LSI, super LSI, or super LSI that performs some or all of the functions described in this disclosure components.

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 in the figures. For example, one or more memories store software or algorithms in executable instructions, and one or more processors can be associated with a set of instructions for executing the software or algorithms to be executed by remote server 140 over a network according to embodiments described in this disclosure. Problem Configure the AP 110 to automatically collect and upload debug log information, which can save manpower and time needed to collect debug logs for network problem analysis.

Software and computer programs (also called programs, software applications, applications, components, or code) include machine instructions for programmable processors and can be written in high-level procedural languages, object-oriented programming languages, functional programming languages , logic programming language or assembly language or machine language. The term "computer-readable medium" means any computer program product, means or device for providing machine instructions or data to a programmable data processor, such as a magnetic disk, optical disk, solid state storage device, memory and programmable logic device (PLD) , including a computer-readable medium for receiving machine instructions as computer-readable signals.

By way of example, a computer readable medium may include 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 devices, magnetic disk storage devices or other magnetic storage devices, or can be used to carry or store required computer-readable program code in the form of instructions or data structures and can be read by general or special purpose computers or general-purpose or any other medium accessed by a dedicated processor. Disk or disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disc and blu-ray Data is copied optically. Combinations of the above should also be included within the scope of computer-readable media.

In one or more embodiments, use of the words "capable", "capable of", "operable to" or "configured to" refers to some device, logic, hardware and/or element. The subject matter of the present disclosure is provided as examples of apparatuses, systems, methods and programs for implementing 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 implementations of the components and functions of the present disclosure may be accomplished with any emerging technology that may replace any of the above-described implementations.

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 figures in a particular order, this should not be construed 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 the desired the result of. In certain situations, multitasking and parallel processing can be advantageous.

Claims (20)

1. An access point comprising: a memory storing instructions; and a processor configured to execute instructions stored in the memory to cause the access point to: receiving configuration information from a remote server for configuring the access point to collect debug log information related to network problems occurring in the network on which the access point is located; collecting the debug log information in a log file based on the configuration information; and Sending the log file storing the debugging log information to the remote server, so that the remote server accesses the debugging log information in the log file to solve network problems occurring in the network. 2. The access point of claim 1, wherein: The debug log information includes information related to the configuration and connection of the access point, and information related to one or more terminal devices connected to the access point. 3. The access point of claim 2, wherein: When the network problem includes a particular end device connected to an access point being unable to connect to a packet data network, the debug log information further includes Address Resolution Protocol (ARP) packets, Internet Control information of at least one of a text protocol (ICMP) packet and a dynamic host configuration protocol (DHCP) packet. 4. The access point of claim 1 , wherein: The debug log information meets the information level indicated by the configuration information, or The debugging log information is generated by one or more modules in the access point indicated by the configuration information. 5. The access point of claim 1, wherein the processor is further configured to: Periodically detect the size of the log file; sending the log file to the remote server when the log file reaches a predetermined maximum size; and Create a new log file to store newly collected debug log information. 6. The access point of claim 1, wherein the processor is further configured to: in response to receiving the configuration information, requesting the remote server to send cryptographic data for verifying the validity of the remote server; receiving cryptographic data from the remote server; determining that said cryptographic data is correct; and In response to determining that the password data is correct, collecting the debug log information based on the configuration information. 7. The access point of claim 6, wherein the processor is further configured to refuse to collect the debug log information when the cryptographic data is determined to be incorrect. 8. A method for debugging log information collection, comprising: receiving, by the access point, configuration information from the remote server for configuring the access point to collect debug log information related to network problems occurring in the network on which the access point is located; collecting, by the access point, the debug log information in a log file based on the configuration information; and The access point sends the log file storing the debugging log information to the remote server, so that the remote server accesses the debugging log information in the log file to solve network problems occurring in the network. 9. The method of claim 8, wherein, Collecting the debug log information includes collecting information related to the configuration and connection of the access point, and information related to one or more terminal devices connected to the access point. 10. The method of claim 9, wherein, When collecting the debug log information includes collecting debug log information about network problems including information about a specific terminal device connected to an access point being unable to connect to a packet data network, the debug log information further includes information related to the specific Information about at least one of ARP packets, ICMP packets, and DHCP packets associated with the terminal device. 11. The method of claim 8, wherein, collecting the debug log information includes collecting debug log information meeting the information level indicated by the configuration information, or Collecting the debugging log information includes collecting debugging log information generated by one or more modules in the access point indicated by the configuration information. 12. The method of claim 8, further comprising: periodically detecting the size of the log file by the access point; sending, by the access point, the log file to the remote server when the log file reaches a predetermined maximum size; and A new log file is created by the access point to store newly collected debug log information. 13. The method of claim 8, further comprising: in response to receiving the configuration information, requesting, by the access point, the remote server to send cryptographic data for authenticating the remote server; receiving, by the access point, cryptographic data from the remote server; determining, by the access point, that the cryptographic data is correct; and In response to determining that the cryptographic data is correct, the debug log information is collected by the access point based on the configuration information. 14. The method of claim 13, further comprising: When it is determined that the password data is incorrect, refuse to collect the debugging log information. 15. A non-transitory computer readable medium storing instructions that, when executed by a processor, cause the processor to perform operations comprising: receiving configuration information from a remote server for configuring the access point to collect debug log information related to network problems occurring in the network on which the access point is located; collecting the debug log information in a log file based on the configuration information; and and sending the log file storing the debugging log information to the remote server, so that the remote server accesses the debugging log information in the log file to solve network problems occurring in the network. 16. The non-transitory computer readable medium of claim 15, wherein: collecting the debug log information includes collecting debug log information meeting the information level indicated by the configuration information, or Collecting the debugging log information includes collecting debugging log information generated by one or more modules in the access point indicated by the configuration information. 17. The non-transitory computer readable medium of claim 15 , wherein the instructions, when executed by a processor, cause the processor to further perform operations comprising: Periodically detect the size of the log file; sending the log file to the remote server when the log file reaches a predetermined maximum size; and Create a new log file to store newly collected debug log information. 18. The non-transitory computer readable medium of claim 15 , wherein the instructions, when executed by a processor, cause the processor to further perform operations comprising: in response to receiving the configuration information, requesting the remote server to send cryptographic data for verifying the validity of the remote server; receiving cryptographic data from the remote server; determining that said cryptographic data is correct; and In response to determining that the password data is correct, collecting the debug log information based on the configuration information. 19. The non-transitory computer readable medium of claim 18 , wherein the instructions, when executed by a processor, cause the processor to further perform operations comprising: When it is determined that the password data is incorrect, refuse to collect the debugging log information. 20. A computer program product, comprising computer instructions, characterized in that, when the computer instructions are executed by a processor, the method according to any one of claims 8-14 is implemented.

Images