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

Abstract

The present disclosure relates to methods, media, program products, and access points for debug log information collection. The method comprises the following steps: receiving, by the access point, configuration information from a remote server, the configuration information for configuring the access point to collect debug log information relating to network problems occurring in a network in which the access point is located; collecting, by an access point, the debug log information based on the configuration information; and transmitting, by an access point, a log file storing the debug log information to the remote server. According to the scheme, the network server can automatically collect and upload the debugging log information according to the network problem configuration access point, and the debugging log information in the log file can be remotely accessed to solve the network problem in the network, so that manpower and time are saved.

Description

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

Technical Field

The present disclosure relates generally to the field of communication networks, and more particularly, to methods, media, program products, and access points for debug log information collection in the field of communication networks.

Background

Due to the popularity of various lan technologies, enterprises, schools, shops, families, etc. all disputes place a lan within their own physical range, and enable various terminal devices to connect to an external network through an Access Point (AP) within the lan. For example, a large number of terminal devices such as notebook computers, desktop computers, mobile phones, home appliances, game console devices, etc. may connect through Wi-Fi to access points such as Wi-Fi routers, wi-Fi expanders (extenders), home gateways, mobile broadband routers, etc. in turn access the internet to enjoy various application services.

The AP at the user may experience 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 internet, or the terminal device cannot stably internet and often drops, or the uplink and/or downlink data rate perceived by the user is too small, or the terminal device cannot connect to a Wi-Fi network, and so on. When a user suffers from these problems, the user typically reports to the network operator providing the network access service to enable the network operator to solve the corresponding problem.

The network operator that received the report typically dispatches maintenance personnel to the customer premises to commission the AP in the field to discover network problems. Due to some requirements of data security, etc., when an AP is released for sale to a user, much debug log information is missing in the debug data stream (also referred to as an office load) that can be seen after release compared to the debug data stream (also referred to as a debug load) seen at the debug stage prior to release of the AP, which may make it difficult for maintenance personnel going to the field to obtain enough debug log information to analyze network problems. Thus, a maintenance person going to the residence may need to manually upgrade the office load to the debug load in the AP to obtain the right that the debug command can be executed, then attempt to execute a different debug command to obtain the required debug log information, etc. This approach is time consuming and labor consuming as maintenance personnel must go to the field to troubleshoot specific network problems.

It is therefore desirable to provide a way to automatically collect debug log information for analyzing network problems after they occur without maintenance personnel going to the site, so that time and labor can be saved.

Disclosure of Invention

Some aspects of the present disclosure relate to an access point. The access point may include: a memory storing instructions; and a processor configured to execute 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 for configuring an access point to collect debug log information relating to network problems (issuers) occurring in a network in which the access point is located; collecting the debug log information in a log file based on the configuration information; and sending a 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 network problems occurring in the network.

In some embodiments, the debug log information may include information related to access point configuration and connections and information related to one or more terminal devices connected to the access point.

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

In some embodiments, the debug log information may satisfy 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: periodically detecting the size of the log file; transmitting the log file to the remote server when the log file reaches a predetermined maximum size; and creating a new log file to store the newly collected debug log information.

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

In some embodiments, the processor is further configured to refuse to collect the debug log information when the cryptographic data is determined to be 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. Which may each perform operations that are executable by the access point.

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 schematic diagram of an example of network connection in a scenario of debug log information collection, according to an embodiment of the present disclosure.

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

FIG. 3 illustrates a flow chart of a method for debug log information collection in accordance with an embodiment of the present disclosure.

FIG. 4 illustrates a flow chart of another method for debug log information collection in accordance with an embodiment of the present disclosure.

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 example embodiments of the disclosure. The following description includes various details to aid in understanding, but these are to be considered merely examples 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 only intended to provide 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 present disclosure.

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

As shown in fig. 1, an Access Point (AP) 110 is located in a residence 100 of a user, 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 signals are coming. The network 150 in which the AP 110 is located may be a wireless local area network supporting, for example, the 802.11 protocol, such as a Wi-Fi network. AP 110 enables terminal devices in network 150 to access external network 130. N terminal devices 120-1 to 120-n (n is an integer of 1 or more) in the coverage area of the network 150 can be connected to the external network 130 by being connected to the AP 110. The terminal devices 120-1 to 120-n may be connected to the AP 110 in a wireless manner by employing an 802.11 protocol or the like, or may be connected to the AP 110 in a wired manner by a cable or the like. These terminal devices may be one or more of a smart phone, a tablet computer, a notebook computer, a desktop computer, an internet-enabled smart home appliance, etc., which may enjoy the network services provided by the external network 130 via the AP 110. The AP 110 may be connected to the external network 130 in a wired manner to transmit 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, a private network, or the like, and devices capable of connecting to the external network 130 may interact with the AP 110 or with the terminal devices 120-1 to 120-n via the AP 110.

The AP 110 in fig. 1 may have the exemplary configuration shown in fig. 2. Although the device for enabling the terminal device to access the external network is referred to herein as an Access Point (AP), the AP 110 may be a hardware electronic device that may combine the functions of a modem, an access point, and/or a router, for example. The present disclosure also contemplates that AP 110 may include, but is not limited to, the functionality of a Smart Media Device (SMD) or IP/QAM Set Top Box (STB) capable of decoding audio/video content and playing Over (OTT) provider or multi-system operator (MSO) provided content.

As shown in fig. 2, AP 110 includes a user interface 20, a network interface 21, a power source 22, a Wide Area Network (WAN) interface 23, a memory 24, and a controller 26. The user interface 20 may include, but is not limited to, push buttons, a keyboard, a keypad, a Liquid Crystal Display (LCD) device, a Cathode Ray Tube (CRT) device, a Thin Film Transistor (TFT) device, a Light Emitting Diode (LED) device, a High Definition (HD) device, or other similar display devices, including display devices with touch screen capabilities, to allow interaction between a user and the AP 110. The 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.11Wi-Fi protocol, bluetooth Low Energy (BLE), or any short range protocol operating according to a wireless technology standard to exchange data over short distances using any licensed or unlicensed frequency band, such as the Citizen Broadband Radio Service (CBRS) band, the 2.4GHz band, the 5GHz band, or the 6GHz band, a consumer electronics radio frequency (RF 4 CE) protocol, the ZigBee protocol, the Z-wave protocol, or the IEEE802.15.4 protocol.

The power supply 22 provides power to the internal components of the AP 110 via the internal bus 27. The power source 22 may be a stand alone power source, such as a battery pack, having an interface that is powered by an electrical charger connected to a socket (e.g., directly or through other devices). The power supply 22 may also include a rechargeable battery, such as a nickel cadmium (NiCd), nickel metal hydride (NiMH), lithium (Li) ion, or Li-polymer battery, that is removable to allow replacement. If the AP 110 is a modem or gateway device, it may include a WAN interface 23, and the WAN interface 23 may include various network cards and circuitry implemented in software and/or hardware to enable communication between the router device and an internet service provider or MSO.

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, a logic block of a Field Programmable Gate Array (FPGA), a hard disk, or any other layer of a 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 operations of AP 110.

The controller 26 controls the general operation of the AP 110 and performs management functions related to other devices in the network (e.g., expanders and client devices). 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 device capable of executing any type of instructions, algorithms, or software for controlling the operation and functions of AP 110 in accordance with embodiments described in this disclosure. The controller 26, such as a processor, may include various implementations of digital circuitry, analog circuitry, or mixed-signal (a combination of analog and digital) circuitry that performs functions in a computing system. Controller 26 may include, for example, circuitry 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 a system including multiple processors.

Internal bus 27 may be used to establish communications between components (e.g., 20-22, 24, and 26) of AP 110.

Returning to fig. 1, the remote server 140 may be located at an office of a network operator providing network access services for the terminal devices 120-1 to 120-n, but may also be located elsewhere, such as at the maintenance personnel's home, etc. Remote server 140 may be connected to AP 110 through external network 130, or may be connected to AP 110 through a private network of a network operator (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 transmit information to the AP 110 and receive information from the AP 110.

Although only one AP 110 is shown in fig. 1 and the remote server 140 is connected to one AP 110, it will be fully understood by those skilled in the art that two or more APs 110 may be provided in the user premises 100 to provide more complete coverage, and the remote server 140 may be connected to multiple APs 110 of different users to be able to communicate with more APs 110 to collect debug log information for more APs 110 to help determine network problems at the multiple APs 110.

When one or more of the terminal devices 120-1 to 120-n cannot surf the internet, or when one or more of the terminal devices 120-1 to 120-n are frequently dropped to require repeated connection 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 to fail to restore the normal speed, or when other surfing anomalies occur, the user typically reports the network problems associated with the network 150 to the network operator by making a call or the like. The network operator who knows the above problems can utilize the interaction between the remote server 140 and the AP 110 to remotely and automatically collect the debug log information related to the network problems by adopting the method provided by the embodiments of the present disclosure, so as to help maintenance personnel to analyze the network problems, thereby avoiding the problems of time and manpower waste caused by the maintenance personnel having to go to the residence of the user in the prior art, and improving the efficiency of obtaining the debug log information. Hereinafter, a method for collecting debug log information according to an embodiment of the present disclosure is described in detail.

A flowchart of a method 300 for collecting debug log information is shown in fig. 3. The method 300 may be performed by an access point to remotely collect debug log information when a network problem occurs in a network in which the access point is located, thereby enabling network problem analysis without requiring maintenance personnel to visit a customer premises or the like. In the description of fig. 3, reference will be made to the network connection example of fig. 1 to assist those skilled in the art in better understanding the present disclosure.

In S310, configuration information is received by the access point from the remote server, the configuration information being used to configure the access point to collect debug log information relating to network problems occurring in the network in which the access point is located.

After any of the network problems described above occur in the network 150 in which the AP 110 provides access services for the terminal devices therein, the user may report the problem to the network operator. It is also possible that the AP 110 automatically reports the network problems it senses. In response to the occurrence of a network problem, remote server 140 sends configuration information to AP 110 that can configure AP 110 to automatically collect debug log information related to the network problem occurring in network 150. These debug log information may be log information generated during the debugging process for network problems.

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

The debug log information collected by the remote server 140 configuring the AP 110 may include information related to access point configuration and connectivity as well as information related to one or more terminal devices connected to the AP 110. The information related to the access point configuration and connection may include at least one of Wi-Fi profile information, ATOM route information, ifonfig output information, and bridging information. The Wi-Fi profile information may indicate configuration parameter information of the AP 110 itself, the ATOM routing information may indicate routing forwarding information of the AP 110, the ifconfig output information may indicate network interface information of the AP 110, and the bridge information may indicate a physical connection relationship of the AP 110. The information about one or more terminal apparatuses connected to the AP 110 may be information about all terminal apparatuses currently connected to the AP 110, or information about a specific one or more terminal apparatuses therein. The information may include at least one of device information of the terminal device and radio statistics. The device information may include a MAC (Media Access Control, medium access control) address, type, supported protocol, etc. of the terminal device, and the radio statistics may include Reference Signal Received Power (RSRP), transmission signal strength, current rate, occupied bandwidth, information of interaction with the AP, etc. of the terminal device.

Information about one or more terminal devices connected to the AP 110 may be collected periodically, for example, every 20 seconds. The collected information may be stored in a log file. The information about the access point configuration and connection, as it is typically kept unchanged, can be saved in a log file at the beginning of the commissioning process without the need for periodic detection and logging. Of course, it may also be saved in a log file at a larger period (e.g., every 10 minutes, 30 minutes, 1 hour, etc.).

Whatever the network problem that arises, the information regarding access point configuration and connectivity, as well as information regarding one or more terminal devices connected to the AP 110, may be collected by the AP 110 to aid in problem analysis. Furthermore, the above two types of information are not limited to the specific forms listed above, but may be other forms as will occur to those of skill in the art.

When the network problem includes that a specific terminal device connected to the AP 110 cannot be connected to the packet data network, the remote server 140 may configure the AP 110 to collect not only the above-described information about the access point configuration and connection and information about one or more terminal devices connected to the AP 110, but also may configure the AP 110 to collect information about at least one of ARP (Address Resolution Protocol ) packets, ICMP (Internet Control Message Protocol, internet control message protocol) packets, and DHCP (Dynamic Host Configuration Protocol ) packets associated with the specific terminal device.

For example, if the network problem is that the terminal device 120-1 can connect to the AP 110, but it cannot surf the internet to receive network services from the external network 130, the remote server 140 may transmit configuration information to the AP 110 to instruct the AP 110 to collect not only Wi-Fi profile information, ATOM route information, ifonfig output information, bridging information, and device type, data rate, occupied bandwidth, etc. corresponding to the MAC address of the terminal device 120-1, but also information such as header information of at least one of ARP packets, ICMP packets, and DHCP packets associated with the MAC address of the terminal device 120-1. When collecting information such as header information, the AP 110 may in different embodiments monitor only ARP packets, only ICMP packets, only DHCP packets, both ARP and ICMP packets, both ICMP and DHCP packets, or both ARP, ICMP and DHCP packets for MAC addresses of non-network capable terminal devices 120-1. Header information of the monitored packets may be stored in a log file to help analyze the reasons for inability to surf the internet.

The configuration information sent by remote server 140 to AP 110 may indicate what information level debug log information needs to be collected by AP 110. For example, debug log information may relate to three levels, an error level, a warning level, and a general level, respectively. The debug log information of the error level corresponds to information that occurs when the AP 110 cannot perform a certain operation. The debug log information of the warning level corresponds to information existing when the operation data is abnormal, which includes debug log information of the error level. The general level of debug log information corresponds to all of the debug log information generated by the AP 110 during the debug process. Which includes debug log information at a warning level and debug log information at an error level.

As another example, DEBUG log information may relate to six levels, from most severe to least severe, of fault, ERROR, WARNING, INFO, DEBUG, TRACE ALL, depending on the severity of the information. These levels respectively contain more and more debug log information, for example, when the debug log information of the later level is presented, all the debug log information of the previous level may be presented in addition to the debug log information of the present level. The debug log information at the level of the FATAL corresponds to information that requires restarting of the associated service or module or AP device when it occurs; debug log information at the ERROR level corresponds to information that an ERROR occurred but that the current process or service may continue; debug log information at the WARNING level corresponds to information given when certain conditions are not met; the INFO level debug log information corresponds to some flow information in the service; DEBUG log information of the DEBUG level is more than that of the INFO level, and the DEBUG log information also comprises information of some calling relations; the TRACE ALL level debug log information corresponds to ALL information that can be displayed during the debug process. Those skilled in the art will appreciate that more or fewer levels of debug log information may be provided as desired.

Because of security, etc., the user of the AP may not wish the remote server 140 to collect all of the debug log information of the AP 110, the remote server 140 may be requested to collect only a specific level (e.g., error level or warning level) of debug log information, so that the remote server 140 may configure the AP 110 to collect the corresponding level of debug log information in response to the request.

The configuration information sent by remote server 140 to AP 110 may also indicate which module or modules of debug log information needs to be collected by AP 110. There may be a number of hardware or software modules in the AP 110, such as Wi-Fi modules, RPC (Remote Procedure Call ) modules, etc., as is well known to those skilled in the art. Different network problems may require collecting debug log information for different modules. Remote server 140 may determine which module or modules of debug log information collection need to be enabled based on specific network problems to make the collected debug log information more accurate. Alternatively, it may be determined which module or modules may be disabled for debug log information collection based on a particular network problem to avoid too much debug log information being collected to prevent analysis of the network problem.

In S320, debug log information related to network problems is collected by the access point based on the configuration information.

In response to receiving the configuration information, the AP 110 may automatically collect corresponding debug log information by calling a program for collecting information according to an instruction of collecting local area network basic information, packet information for a certain MAC address, certain module debug log information, and/or certain level debug log information, etc., included in the configuration information. The collection of this information may be done continuously in a periodic manner. Different periods may be used for different information collection. The collected information may be stored together in a log file.

In S330, a log file storing the debug log information is transmitted to the remote server by the access point.

AP 110 may send the log file to remote server 140 via TFTP (Trivial File Transfer Protocol, simple file transfer protocol) for network problem analysis by maintenance personnel at remote server 140.

According to the above-described technical solution, after a network problem occurs in the network where the AP 110 is located, the remote server 140 transmits configuration information to the AP 110 to configure the AP 110 to automatically collect debug log information related to the network problem, so that the AP 110 can transmit the automatically collected debug log information to the remote server 140 for analysis. The automatic remote debug log information collection method avoids the trouble that maintenance personnel go to a user residence and the like to collect the debug log information on site, and saves time and labor. In addition, since the configuration information can control which debug log information needs to be collected by the AP 110, more useful information can be obtained in the debug data stream after the AP 110 issues, and more targeted debug log information can be obtained, thereby facilitating analysis of network problems.

FIG. 4 illustrates a flow chart of a method 400 for debug log information collection in accordance with an embodiment of the present disclosure. The method 400 differs from the method 300 mainly in the following two points: firstly, judging whether a remote server is legal or not before an access point collects debugging log information; and secondly, uploading the file when the log file storing the debugging log information meets a certain condition.

In S410, configuration information is received by the access point from the remote server, the configuration information being used to configure the access point to collect debug log information relating to network problems occurring in the network in which the access point is located. This step is substantially the same as S310.

In response to receiving the configuration information, requesting, by the access point, the remote server to transmit cryptographic data for verifying the validity of the remote server, S420.

The password data may be data agreed in advance by the AP 110 and the remote server 140, may be data generated by the AP 110 and the remote server 140 according to a common algorithm in real time, or may be data that is sent by the legal remote server 140 to the AP 110 (for example, sent through MIB or TR 069) when the AP 110 is connected to the network 130 every day, which makes the password data of each day different. Regardless of the manner in which the cryptographic data is generated, the AP 110 may determine whether the server is a legitimate server based on the cryptographic data. When the server is a server of a network operator providing access service through the AP 110, the server is a legitimate server capable of collecting debug log information.

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

In S440, it is determined by the AP 110 whether the received password data is correct.

For example, the AP 110 may compare the received password data with password data that can confirm that the remote server 140 is legitimate. When the two match, the received password data is correct, and then the AP 110 determines that the remote server 140 is legitimate, so that debug log information can be provided to the remote server 140. Conversely, when the two do not match, the received password data is incorrect, and the AP 110 then determines that the remote server 140 is illegitimate, so that collection of debug log information is not required.

In S450, in case the access point determines that the received password data is correct, debug log information is collected by the access point based on the configuration information. This step is substantially the same as S320.

In S455, in case the access point determines that the received password data is incorrect, collecting the debug log information is refused by the access point. At this point, the access point may discard the received configuration information.

In S460, the collected debug log information is stored in a log file by the access point.

In S470, the size of the log file is periodically detected by the access point.

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 (e.g., 0.5MB, 1MB, 1.5MB, etc.), the AP 110 may send the log file to the remote server 140.

In S480, the log file is transmitted to the remote server by the AP 110 in response to determining that the log file reaches the predetermined maximum size.

In S490, a new log file is created by the access point to store the newly collected debug log information.

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

It will be appreciated by those skilled in the art that not all steps of the above-described methods need to be present in one embodiment at the same time, and that they may be flexibly combined to be implemented in different embodiments. Although the AP 110 is shown to collect the debug log information only in S450, the AP 110 may continuously collect the debug log information after determining that the password data is correct without being affected by other steps. Further, although S490 is shown as being performed after S480, the access point may perform 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 not only can configure the AP 110 to automatically collect and upload the debug log information according to the network problem, thereby saving manpower and time, but also can provide a security mechanism to prevent the debug log information from being uploaded to an illegal server, thereby enhancing network security. In addition, the file is uploaded when the log file storing the debug log information meets the preset maximum size, so that timeliness of the debug log information collection and resources occupied by transmission can be considered.

The present disclosure may 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 ultra LSI assembly 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. The software, application, computer program or algorithm 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 drawings. For example, the one or more memories store software or algorithms in executable instructions and the one or more processors may associate a set of instructions to execute the software or algorithms to automatically collect and upload debug log information by remote server 140 based on network problem configuration AP 110 in accordance with embodiments described in the present disclosure, thereby saving the manpower and time required to collect debug logs for network problem analysis.

The 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 memory devices, memory, and Programmable Logic Devices (PLDs), for providing machine instructions or data to a programmable data processor, including computer-readable media 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 that can be used to carry or store desired computer-readable program code in the form of instructions or data structures and that can be accessed by a general purpose or special purpose computer or 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, the use of the words "capable," "operable" or "configured" refers to some means, logic, hardware, and/or elements designed to be capable of use in a specified manner. The subject matter of the present disclosure is provided as examples of apparatuses, 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 any of the above-described implementation technologies.

In addition, the foregoing description provides examples without limiting 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, replace, or add various procedures or components as appropriate. For example, features described with respect to certain embodiments may be combined in other embodiments.

Similarly, although 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, 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, the configuration information being used to configure an access point to collect debug log information relating to network problems occurring in a network in 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 the network problem in the network.

2. The access point of claim 1, wherein,

the debug log information includes information related to access point configuration and connections, 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 that a particular terminal device connected to an access point cannot connect to a packet data network, the debug log information further includes information of at least one of an Address Resolution Protocol (ARP) packet, an Internet Control Message Protocol (ICMP) packet, and a Dynamic Host Configuration Protocol (DHCP) packet associated with the particular terminal device.

4. The access point of claim 1, wherein,

the debug log information satisfies the information level indicated by the configuration information, or

The debug 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 detecting the size of the log file;

transmitting the log file to the remote server when the log file reaches a predetermined maximum size; and

a new log file is created to store the 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 password data for verifying the validity of the remote server;

receiving password data from the remote server;

determining that the cryptographic data is correct; and

in response to determining that the cryptographic data is correct, the debug log information is collected 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 debug log information collection, comprising:

receiving, by the access point, configuration information from a remote server, the configuration information for configuring the access point to collect debug log information relating to network problems occurring in a network in which the access point is located;

collecting, by an access point, 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 by an access point, so that the remote server accesses the debugging log information in the log file to solve the network problem in the network.

9. The method of claim 8, wherein,

collecting the debug log information includes collecting information related to access point configuration and connections, 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 regarding network problems including information regarding a failure of a particular terminal device connected to an access point to connect to a packet data network, the debug log information further includes information of at least one of ARP packets, ICMP packets, and DHCP packets associated with the particular terminal device.

11. The method of claim 8, wherein,

collecting the debug log information includes collecting debug log information satisfying an information level indicated by the configuration information, or

Collecting the debug log information includes collecting debug 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, by an access point, a size of the log file;

transmitting, by an 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 the newly collected debug log information.

13. The method of claim 8, further comprising:

requesting, by an access point, the remote server to transmit password data for verifying the validity of the remote server in response to receiving the configuration information;

receiving, by an 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 the password data is determined to be incorrect, the debug log information is refused to be collected.

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, the configuration information being used to configure an access point to collect debug log information relating to network problems occurring in a network in 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 the network problem in the network.

16. The non-transitory computer readable medium of claim 15, wherein,

collecting the debug log information includes collecting debug log information satisfying an information level indicated by the configuration information, or

Collecting the debug log information includes collecting debug 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 the processor, cause the processor to further perform operations comprising:

periodically detecting the size of the log file;

transmitting the log file to the remote server when the log file reaches a predetermined maximum size; and

a new log file is created to store the newly collected debug log information.

18. The non-transitory computer-readable medium of claim 15, wherein the instructions, when executed by the processor, cause the processor to further perform operations comprising:

in response to receiving the configuration information, requesting the remote server to send password data for verifying the validity of the remote server;

receiving password data from the remote server;

determining that the cryptographic data is correct; and

in response to determining that the cryptographic data is correct, the debug log information is collected based on the configuration information.

19. The non-transitory computer-readable medium of claim 18, wherein the instructions, when executed by the processor, cause the processor to further perform operations comprising:

when the password data is determined to be incorrect, the debug log information is refused to be collected.

20. A computer program product comprising computer instructions which, when executed by a processor, implement the method according to any of claims 8-14.

Images