Method and system for collecting access network data

Abstract

This disclosure provides a method and system for collecting data from an access layer device. The method includes the following steps: establishing an access layer connection between a data collection device and the access layer device, wherein the data collection device and the access layer device are capable of communicating with each other; collecting key indicators related to the health and performance status of the access layer connection based on the collected data; analyzing the collected key indicators to assess a service quality; and generating a report or a notification based on the analyzed key indicators.

Description

Method and System for Collecting Access Network Data This application claims the priority and benefit of U.S. Provisional Application No. 63 / 521,103, filed on June 15, 2023, the entire disclosure of which is incorporated herein by reference. This disclosure generally relates to the field of access layer devices of Internet service providers. In particular, it relates to a software application that uses an application programming interface (API) through a data collection device to collect data of access layer devices. In today's digital age, Internet service providers (ISPs) face an increasing demand for efficient network quality monitoring and assessing the health of customer services. Customers' expectations for flawless Internet services are constantly rising, and any brief service interruption or performance degradation can lead to dissatisfaction. However, traditional network quality monitoring methods face multiple challenges, especially in large-scale network environments. Traditionally, ISPs use centralized servers to monitor and diagnose the health of customer connections. These servers use the Simple Network Management Protocol (SNMP) to communicate with each individual modem to collect relevant performance data. However, this method faces several major challenges, such as high resource requirements, time-consuming processes, and the gap between customer expectations and reality. SNMP is a messaging protocol that uses operator identification numbers (OIDs) to collect various metrics from modems. Each OID corresponds to a specific network metric, such as temperature, signal strength, etc. These OIDs are essentially key value pairs used to identify and record modem performance data. Given that each modem has hundreds of thousands of OIDs, the centralized server must communicate with each modem individually to collect the required data. This process is extremely resource-intensive because the server needs to handle a large number of data requests and responses. In an ISP network with hundreds of thousands or even millions of users, this method becomes particularly challenging. In addition to being resource-intensive, the data collection process is also very time-consuming. Since the centralized server must query each modem one by one, the entire process may take hours or even longer. Therefore, ISPs can usually collect data only once or twice a day, which means they can only obtain a daily snapshot of network performance. This makes it difficult to capture instantaneous but important network events in real time. Furthermore, customers' expectations for Internet services often exceed the technical capabilities of ISPs. Even if a network problem lasts only for a few minutes, customers expect ISPs to quickly identify and resolve the problem. However, limited by the frequency and speed of data collection, ISPs may not be able to obtain the necessary data in real time to diagnose and resolve these short-term problems, resulting in a decline in customer satisfaction. Therefore, there is a need for an automated system for collecting access network data to provide an accurate and real-time view of in-depth service quality. To solve the above technical problems, the present disclosure provides a method and system capable of directly collecting key indicators from access layer devices to provide accurate and real-time service quality information. Specifically, the present disclosure provides the following technical solutions. In one aspect, the present disclosure provides a method for collecting data from an access layer device, including: establishing an access layer link between a data collection device and the access layer device, where the data collection device and the access layer device can communicate with each other; collecting key indicators related to the health and performance status of the access layer link based on the collected data; analyzing the collected key indicators to evaluate service quality; and generating a report or notification based on the analyzed key indicators. In some specific embodiments, the data collection device is a router, and the access layer device is a cable modem, an optical network terminal (ONT), or a fixed wireless access modem. In some specific embodiments, the access layer link is a TCP / IP link. In some specific embodiments, a network configuration using a sub-interface that allows direct and isolated communication is used between the data collection device and the access layer device. In some specific embodiments, the access layer device is connected to the data collection device through a private (RFC1918) sub-network separate from other devices connected to the data collection device. In some specific embodiments, the method further includes: mapping each key indicator collected to illustrate the health and performance status of the access layer link to a network service, which is prepared to respond to an application programming interface (API) request from the data collection device; and collecting data from the access layer device using an application programming interface (API) implemented on the data collection device. In some specific embodiments, the API is triggered from a cloud system to the data collection device. In another aspect, the present disclosure further provides a system for facilitating data collection from an access layer device, where: an access layer link is established between a data collection device and the access layer device, where the data collection device and the access layer device can communicate with each other; key indicators related to the health and performance status of the access layer link are collected based on the collected data; the collected key indicators are analyzed to evaluate service quality; and a report or notification is generated based on the analyzed key indicators. In some specific embodiments, the system is a software application running as a program on the access layer device. In some specific embodiments, each key indicator collected to illustrate the health and performance status of the access layer link is mapped to a network service, which is prepared to respond to application programming interface (API) requests from the data collection device; and the application programming interface (API) implemented on the data collection device is used to collect data from the access layer device. In some specific embodiments, the software application prompts the following steps: connecting to the access layer device from the data collection device in a secure manner; collecting data from the access layer device through the API; and forwarding instructions of the management system to the access layer device for the purpose of speed testing or restarting the access layer device. In another aspect, the present disclosure further provides a system for collecting data from an access layer device, including: a data collection device capable of communicating with the access layer device to establish an access layer link between the data collection device and the access layer device; an application programming interface (API) implemented on the data collection device and configured to communicate with the access layer device and collect data; and a software application executed on the data collection device and configured to use the API and collect key indicators related to the health and performance status of the access layer link based on the collected data. In some specific embodiments, the data collection device further includes: a memory module configured to store the collected key indicators; and a communication module configured to transmit reports or notifications generated based on the key indicators to a management entity. In some specific embodiments, the data is returned from the access layer device to the data collection device in JSON format. To more clearly explain the embodiments of the present disclosure or the solutions in the prior art, specific embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. Apparently, the drawings described below are only some embodiments of the present disclosure. Based on these drawings, those of ordinary skill in the art can obtain other drawings and adopt other embodiments without creative efforts. Referring to FIG. 1, which is a schematic diagram of a system for collecting data from an access layer device according to an aspect of the present disclosure, system 10 includes an access layer device 100, a data collection device 200, an application programming interface (API) 300, and a software application (not shown). The data collection device 200 is capable of communicating with the access layer device 100 to establish an access layer link 120 therebetween. In some embodiments, the access layer device 100 may be a wired modem, an optical network terminal (ONT), or a fixed wireless access modem, which is connected to an access network 400 provided by an Internet service provider (ISP) via a physical link 110 for accessing the Internet 500. In some embodiments, the data collection device 200 is a router. In some embodiments, the access layer link 120 is a physical link, such as a TCP / IP link. The application programming interface (API) 300 is implemented on the data collection device 200 and is configured to communicate with the access layer device 100 and collect data from the access layer device 100. The software application runs on the data collection device 200 and is configured to use the API 300 and collect key metrics related to the health and performance status of the access layer link 120 based on the collected data. In some embodiments, the network link between the access layer device 100 and the data collection device 200 supports two functions on a single physical link, using wide area network (WAN) and local area network (LAN) interfaces through logical sub-interfaces. This innovative approach enables enhanced data collection, secure communication, and efficient network management. More specifically, the Ethernet interface of the data collection device 200 acts as a WAN interface, similar to a wireless data collection device 200 connected to the access layer device 100 via an Ethernet cable. This link executes the Dynamic Host Configuration Protocol (DHCP) to connect to the service provider's network and serves as the default data collection device 200 for all user devices connected to the data collection device 200. Using a private (RFC 1918) IPv4 address, this secondary logical interface allows the data collection device 200 to manage LAN traffic. This interface ensures that the data collection device 200 can communicate directly with the access layer device 100 through a secure and isolated subnet. The Ethernet interface enables the transmission of data from the data collection device 200 to the ISP and the Internet 500 as a bridge. This sub-interface joins the LAN of the data collection device 200, allowing the access layer device 100 itself to communicate directly with the data collection device 200. This setup allows for seamless data collection and reporting, effectively managing traffic using the internal routing table of the data collection device 200. In some specific embodiments, the data collection device 200 may further include a memory module 210 and a communication module 220. The memory module 210 is configured to store the collected metrics, and the communication module 220 is configured to transmit reports or notifications generated based on the key metrics to the management entity. Therefore, the data collection device 200 can wirelessly transmit data to the cloud on the Internet 500 or access the network 400. In some specific embodiments, the system 10 prompts the data collection device 200 to perform a firmware upgrade on the access layer device 100. In addition, data is returned from the access layer device 100 to the data collection device 200 in the JavaScript object notation (JSON) format. Further, another aspect of the present disclosure provides a method for collecting data from an access layer device. Referring to FIG. 2, which is a flowchart of a method for collecting data from an access layer device according to an embodiment of the present disclosure, the method includes the following steps: In step S21, an access layer link 120 is established between the data collection device 200 and the access layer device 100. In step S22, based on the collected data, key metrics related to the health and performance status of the access layer link 120 are collected. In step S23, the collected key metrics are analyzed to evaluate the service quality. In step S24, a report or notification is generated based on the analyzed key metrics. In some specific embodiments, referring to FIG. 1, the data collection device 200 is capable of communicating with the access layer device 100 such that an access layer link 120 is established between the data collection device 200 and the access layer device 100. In some specific embodiments, the access layer device 100 is a wired modem, an optical network terminal (ONT), or a fixed wireless access modem, which is connected to the access network 400 provided by an Internet service provider (ISP) through a physical link 110 to access the Internet 500. In some specific embodiments, the data collection device 200 is a router. In some specific embodiments, the access layer link 120 is a physical link, such as a TCP / IP link. In some specific embodiments, the network link between the access layer device 100 and the data collection device 200 supports two functions on a single physical link, using WAN and LAN interfaces through a logical sub-interface. This innovative approach enables enhanced data collection, secure communication, and efficient network management. More particularly, the Ethernet interface of the data collection device 200 serves as a WAN interface, similar to the wireless data collection device 200 being connected to the access layer device 100 via an Ethernet cable. This connection performs DHCP to connect to the service provider's network and serves as the default data collection device 200 for all user devices connected to the data collection device 200. Using a private (RFC 1918) IPv4 address, this secondary logical interface allows the data collection device 200 to manage local area network (LAN) traffic. This interface ensures that the data collection device 200 can communicate directly with the access layer device 100 through a secure and isolated subnet. The Ethernet interface facilitates the transmission of data from the data collection device 200 to the ISP and the Internet 500 as a bridge. This sub-interface joins the LAN of the data collection device 200, enabling the access layer device 100 itself to communicate directly with the data collection device 200. This setup allows for seamless data collection and reporting, effectively managing traffic using the internal routing table of the data collection device 200. Further, referring to FIG. 3, which is a flowchart of the step S22 of collecting key indicators according to another embodiment of the present disclosure. In FIG. 3, step S22 includes the following steps: In step S221, the access layer device 100 maps each key indicator collected to illustrate the health and performance status of the access layer link 120 to the network service 400, which is prepared to respond to the application programming interface (API) 300 request from the data collection device 200. In step S222, data is collected from the access layer device 100 using the application programming interface (API) 300 implemented on the data collection device 200. In some specific embodiments, the API 300 is triggered from a cloud system to the data collection device 200 or a local data collection agency. The application programming interface (API) 300 is implemented on the data collection device 200 and configured to communicate with the access layer device 100 and collect data from the access layer device 100. A software application is executed on the data collection device 200 and configured to utilize the API 300 and collect key indicators related to the health and performance status of the access layer link 120 based on the collected data. Further, another aspect of the present disclosure provides a system for facilitating data collection from the access layer device 100. In this system, an access layer link 120 is established between the data collection device 200 and the access layer device 100; key indicators related to the health and performance status of the access layer link 120 are collected based on the collected data; the collected key indicators are analyzed to evaluate the service quality; and a report or notification is generated based on the analyzed key indicators. In some specific embodiments, the system is a software application that operates as a program running on the access layer device 100. Further, referring to FIG. 4, which is a flowchart of a software application for prompting data collection from an access layer device according to an embodiment of the present disclosure. In FIG. 4, the software application prompts the following steps: In step S41, connect to the access layer device 100 from the data collection device 200 in a secure manner. In step S42, collect data from the access layer device 100 through the API. In step S43, for the purpose of speed testing or restarting the access layer device 100, forward the instructions of the management system to the access layer device 100. In some specific embodiments, referring to FIG. 1, the data collection device 200 can communicate with the access layer device 100 with each other, thereby establishing an access layer link 120 between the data collection device 200 and the access layer device 100. In some specific embodiments, the access layer device 100 can be a wired modem, an optical network terminal (ONT), or a fixed wireless access modem, which is connected to the access network 400 provided by an Internet service provider (ISP) through a physical link 110 to access the Internet 500. In some specific embodiments, the data collection device 200 is a router. In some specific embodiments, the access layer link 120 is a physical link, such as a TCP / IP link. In some specific embodiments, the network link between the access layer device 100 and the data collection device 200 supports two functions on a single physical link, using WAN and LAN interfaces through logical sub-interfaces. This innovative approach enables enhanced data collection, secure communication, and effective network management. More specifically, the Ethernet interface of the data collection device 200 serves as a WAN interface, similar to a wireless data collection device 200 connected to the access layer device 100 through an Ethernet cable. This link executes DHCP to connect to the service provider's network and serves as the default data collection device 200 for all user devices connected to the data collection device 200. Using a private (RFC 1918) IPv4 address, this secondary logical interface allows the data collection device 200 to manage LAN traffic. This interface ensures that the data collection device 200 can communicate directly with the access layer device 100 through a secure and isolated subnet. The Ethernet interface enables the transmission of data from the data collection device 200 to the ISP and the Internet 500 as a bridge. This sub-interface joins the LAN of the data collection device 200, enabling the access layer device 100 itself to communicate directly with the data collection device 200. This setup allows for seamless data collection and reporting, effectively managing traffic using the internal routing table of the data collection device 200. In some specific embodiments, each key metric collected to illustrate the health and performance status of the access layer link 120 is mapped to a network service, which is prepared to respond to application programming interface (API) requests from the data collection device 200, and the application programming interface (API) 300 implemented on the data collection device 200 is used to collect data from the access layer device 100. Compared with the prior art, the present disclosure provides at least one or more of the following beneficial effects. First, the ISP can adopt an innovative solution to transfer data collection and processing from a centralized server to edge devices (such as the access layer device 100), significantly improving the efficiency and accuracy of data collection. Second, the concept of edge computing involves assigning the tasks of data collection and preliminary processing to individual access layer devices 100. In this way, each access layer device 100 can autonomously and regularly report its performance data to a centralized location, whether it is a cloud server or another data collection point. This method reduces the burden on the centralized server and allows for more frequent data collection. In addition, by enabling the access layer device 100 to report data by itself, the ISP can achieve real-time network monitoring. Each access layer device 100 can automatically report its performance metrics at a preset interval or immediately when an anomaly is detected. This enables the ISP to identify and resolve network problems more promptly, thereby improving customer satisfaction. Different from daily snapshot data, this decentralized data collection method provides a more comprehensive coverage. The ISP can obtain detailed and continuous data, allowing for more accurate network performance analysis and better prediction of potential problems. Last but not least, since data collection and preliminary processing are performed by the access layer device 100, the centralized server only needs to process the filtered and organized data, significantly reducing system resource requirements. This effective utilization of resources not only improves data collection efficiency but also reduces operating costs. It should be noted that the above embodiments can be freely combined as needed. They are only the preferred embodiments of the present disclosure. It should be pointed out that for those skilled in the art, several improvements and modifications can be made without departing from the concept of the present disclosure. These improvements and modifications should also be included within the scope of the present disclosure. 10: System 100: Access layer device 110: Physical link 120: Access layer link 200: Data collection device 210: Memory module 220: Communication module 300: Application programming interface 400: Access network 500: Internet S21~S24, S221~S222, S41~S43: Steps The above technical features, advantages, and embodiments of the present disclosure will become more readily apparent to those of ordinary skill in the art after referring to the following detailed description and the accompanying drawings. FIG. 1 is a schematic diagram of a system for collecting data from an access layer device according to an embodiment of the present disclosure; FIG. 2 is a flowchart of a method for collecting data from an access layer device according to an embodiment of the present disclosure; FIG. 3 is a flowchart of steps for collecting key indicators according to another embodiment of the present disclosure; and FIG. 4 is a flowchart of a software application for prompting data collection from an access layer device according to an embodiment of the present disclosure. 10: System 100: Access layer device 110: Physical link 120: Access layer link 200: Data collection device 210: Memory module 220: Communication module 300: Application interface 400: Access network 500: Internet

Claims

1. A method for collecting data from an access layer device, comprising: An access layer connection is established between a data collection device and an access layer device, wherein the data collection device and the access layer device are able to communicate with each other; based on the collected data, key indicators related to the health and performance status of the access layer connection are collected; the collected key indicators are analyzed to assess a service quality; and based on the analyzed key indicators, a report or a notification is generated.

2. The method as described in claim 1, further comprising: Each key metric collected to describe the soundness and performance status of the access layer connection is mapped to a network service that is prepared to respond to application interface (API) requests from the data collection device; and to collect data from the access layer device using an application interface (API) implemented on the data collection device.

3. The method as described in request item 2, wherein the API is triggered from a cloud system to the data collection device.

4. The method of claim 1, wherein a network configuration using one of the sub-interfaces that allows for direct and isolated communication is used between the data collection device and the access layer device.

5. The method of claim 1, wherein the access layer device is connected to the data collection device using a private (RFC1918) subnet separate from other devices connected to the data collection device.

6. A system for facilitating data collection from an access layer device, wherein: An access layer connection is established between a data collection device and an access layer device, wherein the data collection device and the access layer device are able to communicate with each other; based on the collected data, key indicators related to the health and performance status of the access layer connection are collected; the collected key indicators are analyzed to assess a service quality; and based on the analyzed key indicators, a report or a notification is generated.

7. The system as described in claim 6, wherein the system is a software application, as a program running on the access layer device.

8. The system as described in claim 6, wherein: Each key metric collected to illustrate the health and performance status of the access layer connection is mapped to a network service that is prepared to respond to application interface (API) requests from the data collection device. An application programming interface (API) implemented on the data collection device is used to retrieve data from the access layer device.

9. The system as described in claim 8, wherein the API is triggered from a cloud system to the data collection device.

10. The system as claimed in claim 6, wherein a network configuration using one of the sub-interfaces that allows for both direct and isolated communication is used between the data collection device and the access layer device.

11. The system as claimed in claim 6, wherein the access layer device is connected to the data collection device using a private (RFC1918) subnet separate from other devices connected to the data collection device.

12. The system as claimed in claim 7, wherein the software application causes the following steps: securely connecting from the data collection device to the access layer device; collecting data from the access layer device via an API; and forwarding instructions from a management system to the access layer device for the purpose of a speed test or restarting the access layer device.

13. A system for collecting data from an access layer device, comprising: A data collection device capable of communicating with the access layer device to establish an access layer connection between the data collection device and the access layer device; An application programming interface (API) is implemented on the data collection device and configured to communicate with the access layer device and receive data; And a software application that runs on the data collection device and is configured to use the API and key metrics related to the health and performance status of the access layer connection based on the collected data.

14. The system as claimed in claim 13, wherein the data collection device further comprises: A memory module configured to store the collected key metrics; And a communication module configured to transmit a report or notification based on the key metric to a management entity.

15. The system as claimed in claim 13, wherein the system causes the data collection device to perform a firmware upgrade on the access layer device.

16. The system as described in claim 13, wherein the data is returned from the access layer device to the data collection device in a JSON format.

17. The system as claimed in claim 13, wherein a network configuration using one of the sub-interfaces that allows for both direct and isolated communication is used between the data collection device and the access layer device.

18. The system as claimed in claim 13, wherein the access layer device is connected to the data collection device using a private (RFC1918) subnet separate from other devices connected to the data collection device.

Images