Early Warning Fault Identification and Isolation System for a Two-Way Cable Network
First Claim
1. A method of determining an operational status of a segment of a hybrid fiber coax (HFC) cable network comprising:
- accessing a ping datastore to acquire ping data associated with a plurality of subscriber premises units (SPUs) connected to the HFC network through a common node, wherein the ping data comprise for each SPU of the plurality of SPUs a ratio of a number of ping responses to a number of ping queries;
selecting from the ping data associated with the plurality of SPUs a primary SPU, wherein the primary SPU has the highest ratio of ping responses to ping queries and wherein the primary SPU is associated with a primary SPU IP address; and
selecting from the ping data associated with the plurality of SPUs a secondary SPU, wherein the secondary SPU has the second highest ratio of ping responses to ping queries and wherein the secondary SPU is associated with a secondary SPU IP address;
pinging the primary SPU IP address;
determining whether a response from the ping is received from the primary SPU;
when a response from the ping is received from the primary SPU, then setting a primary SPU operational status of the primary SPU to responsive;
when a response from the ping is not received from the primary SPU, pinging the secondary SPU IP address;
determining whether a response from the ping is received from the secondary SPU;
when a response from the ping is received from the secondary SPU, then setting a secondary SPU operational status of the secondary SPU to responsive and setting a node operational status of the common node to responsive;
when a response from the ping is not received from the secondary SPU, then setting the secondary SPU operational status of the secondary SPU to non-responsive and setting the node operational status of the common node to non-responsive; and
determining an operational status of a network component upstream from the common node based on the node operational status of all nodes serviced by the upstream network component.
7 Assignments
0 Petitions
Accused Products
Abstract
A system and method for determining an operational status of a segment of a hybrid fiber coax (HFC) cable network. Subscriber premises units (SPUs) connected to the HFC cable network are “pinged” and their responses recorded. The two most responsive SPUs in each node of the HFC cable network are identified. The most responsive SPU is added to a primary ping list and the next most responsive SPU is added to a secondary ping list. The SPUs on the primary list are “pinged” and their responses recorded. If an SPU on the primary list fails to respond, the secondary SPU associated with the node is pinged. If both the primary and secondary SPU associated with a node fail to respond to the “ping,” the node is identified as non-responsive. If all of the nodes associated with a modulator (or a demodulator) are identified as non-responsive, the modulator (or demodulator) is identified as “non-responsive.” Additionally, network devices are pinged and their responses noted. Using the responsiveness of nodes and network devices, faults in segments in an HFC cable network can be identified and located.
-
Citations
16 Claims
-
1. A method of determining an operational status of a segment of a hybrid fiber coax (HFC) cable network comprising:
-
accessing a ping datastore to acquire ping data associated with a plurality of subscriber premises units (SPUs) connected to the HFC network through a common node, wherein the ping data comprise for each SPU of the plurality of SPUs a ratio of a number of ping responses to a number of ping queries; selecting from the ping data associated with the plurality of SPUs a primary SPU, wherein the primary SPU has the highest ratio of ping responses to ping queries and wherein the primary SPU is associated with a primary SPU IP address; and selecting from the ping data associated with the plurality of SPUs a secondary SPU, wherein the secondary SPU has the second highest ratio of ping responses to ping queries and wherein the secondary SPU is associated with a secondary SPU IP address; pinging the primary SPU IP address; determining whether a response from the ping is received from the primary SPU; when a response from the ping is received from the primary SPU, then setting a primary SPU operational status of the primary SPU to responsive; when a response from the ping is not received from the primary SPU, pinging the secondary SPU IP address; determining whether a response from the ping is received from the secondary SPU; when a response from the ping is received from the secondary SPU, then setting a secondary SPU operational status of the secondary SPU to responsive and setting a node operational status of the common node to responsive; when a response from the ping is not received from the secondary SPU, then setting the secondary SPU operational status of the secondary SPU to non-responsive and setting the node operational status of the common node to non-responsive; and determining an operational status of a network component upstream from the common node based on the node operational status of all nodes serviced by the upstream network component. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8)
-
-
9. A system for determining an operational status of a segment of a hybrid fiber coax (HFC) cable network comprising:
-
a plurality of nodes; a ping list generator, wherein for each node of the plurality of nodes the ping list generator is configured for; accessing a ping datastore to acquire ping data associated with a plurality of subscriber premises units (SPUs) connected to the HFC network through a common node, wherein the ping data comprise for each SPU of the plurality of SPUs a ratio of a number of ping responses to a number of ping queries; selecting from the ping data associated with the plurality of SPUs a primary SPU, wherein the primary SPU has the highest ratio of ping responses to ping queries and wherein the primary SPU is associated with a primary SPU IP address; adding the primary SPU IP address to a primary SPU ping list; selecting from the ping data associated with the plurality of SPUs a secondary SPU, wherein the secondary SPU has the second highest ratio of ping responses to ping queries and wherein the secondary SPU is associated with a secondary SPU IP address; and adding the secondary SPU IP address to a secondary SPU ping list; an SPU pinger, wherein the SPU pinger is configured for; receiving from the ping list generator the primary SPU ping list and the secondary SPU ping list; pinging the primary IP address of each primary SPU on the primary SPU ping list; setting an SPU operational status of the primary SPU as responsive when a response from the ping is received; and setting the SPU operational status of the primary SPU as non-responsive when the response from the ping is not received; pinging a secondary IP address of a secondary SPU on the secondary SPU ping list when instructed by a results processor; setting an SPU operational status of the secondary SPU as responsive when the response from the ping is received; and setting the SPU operational status of the secondary SPU as non-responsive when the response from the ping is not received; the results processor, wherein the results processor is configured for; determining an SPU operational status of the primary SPU; setting a node operational status of the common node associated with the pinged SPU to responsive when the primary SPU operational status is responsive; instructing the SPU pinger to ping the secondary IP address of the secondary SPU associated with the common node and to set an operation status of the secondary SPU when the primary SPU operational status of the primary SPU associated with the common node is non-responsive; determining an SPU operational status of the secondary SPU; setting the node operational status to responsive when the secondary SPU operation status is responsive; and setting the node operational status to non-responsive when the secondary SPU operational status is non-responsive; and a final results processor, wherein the final results processor is configured for determining an operational status of a network component upstream from the common node based on the node operational status of all nodes serviced by the upstream network component. - View Dependent Claims (10, 11, 12, 13, 14, 15, 16)
-
Specification