System and method for determining whether DOCSIS-enabled devices in a HFC cable network are co-located

1. A co-location processor for a hybrid-fiber-coax (HFC) cable network comprising:

a co-location alert manager; and

a co-location agent, wherein the co-location agent is adapted for:

acquiring a first ranging offset value associated with a first DOCSIS-enabled device (DED) and a second ranging offset value associated with a second DED, wherein the first and second DEDs are associated with a subscriber account;

applying a first normalization factor to the first ranging offset value to obtain a first normalized ranging offset value and applying a second normalization factor to the second ranging offset value to obtain a second normalized ranging offset value;

determining a “delta” offset value equal to the absolute value of the difference between the first normalized ranging offset value and the second normalized ranging offset value;

determining whether the delta offset value exceeds a predetermined threshold;

sending an alert to the co-location alert manager if the delta offset value exceeds a predetermined threshold;

acquiring a first cable MAC domain identifier associated with the first DED and a second MAC domain identifier associated with the second DED:

determining whether the first MAC domain identifier differs from the second MAC domain identifier; and

sending an alert to the alert manager if the first MAC domain identifier differs from the second MAC domain identifier.

2. The co-location processor of claim 1 , wherein a DED comprises a standalone cable modem.

3. The co-location processor of claim 1 , wherein a DED comprises a component within a device connectable to the HFC cable network.

4. The co-location processor of claim 1 , wherein the co-location agent is further adapted for acquiring subscriber account data for the subscriber account, wherein subscriber account data comprises a subscriber account number, a first MAC address associated with the first DED and a second MAC address associated with the second DED.

5. The co-location processor of claim 4 , wherein the first and second ranging offset values are acquired from a cable modem termination system using the first and second MAC addresses.

6. The co-location processor of claim 4 , wherein the alert manager is adapted for:

receiving an alert from the co-location agent; and

routing the alert to a customer support center, wherein the customer support center is associated with the subscriber account number.

7. The co-location processor of claim 1 , wherein the co-location agent is further adapted for:

sending a confirmation command to the first and second DEDs;

receiving a first response from the first DED to the first confirmation command and a second response from the second DED to the second confirmation command;

determining from the first and second response whether the first DED and second DED are co-located; and

sending a confirmed alert to the co-location alert manager if the first DED and second DED are not co-located.

8. A cable theft of service alert system comprising:

a co-location agent, wherein the co-location agent is adapted for:

acquiring a first ranging offset value associated with a first DOCSIS-enabled device (DED) and a second ranging offset value associated with a second DED, wherein the first and second DEDs are associated with a subscriber account;

applying a first normalization factor to the first ranging offset value to obtain a first normalized ranging offset value and applying a second normalization factor to the second ranging offset value to obtain a second normalized ranging offset value;

determining a “delta” offset value equal to the absolute value of the difference between the first normalized ranging offset value and the second normalized ranging offset value; and

creating a discrepancy record comprising the DED values and the delta offset values if the delta offset value exceeds a predetermined threshold; and

a rules engine adapted for:

receiving the discrepancy record associated with the subscriber;

receiving subscriber account data from a subscriber datastore;

applying a theft rule to the delta offset values and the subscriber account data;

determining whether a theft of service has occurred;

sending an alert to a theft of service server if the theft of service has occurred;

acquiring a first cable MAC domain identifier associated with the first DED and a second MAC domain identifier associated with the second DED:

determining whether the first MAC domain identifier differs from the second MAC domain identifier; and

sending an alert to the alert manager if the first MAC domain identifier differs from the second MAC domain identifier.

9. The cable theft of service alert system of claim 8 , wherein a DED comprises a standalone cable modem.

10. The cable theft of service alert system of claim 8 , wherein a DED comprises a component within a device connectable to the HFC cable network.

11. The cable theft of service alert system of claim 8 , wherein the co-location agent is further adapted for acquiring subscriber account data for the subscriber account, wherein subscriber account data comprises a subscriber account number, a first MAC address associated with the first DED and a second MAC address associated with the second DED.

12. The cable theft of service alert system of claim 11 , wherein the first and second ranging offset values are acquired from a cable modem termination system using the first and second MAC addresses.

13. The cable theft of service alert system of claim 11 , wherein the alert manager is adapted for:

receiving an alert from the co-location agent; and

routing the alert to a customer support center, wherein the customer support center is associated with the subscriber account number.

14. The cable theft of service alert system of claim 8 , wherein the co-location agent is further adapted for:

sending a confirmation command to the first and second DEDs;

receiving a first response from the first DED to the first confirmation command and a second response from the second DED to the second confirmation command;

determining from the first and second response whether the first DED and second DED are co-located; and

sending a confirmed alert to the co-location alert manager if the first DED and second DED are not co-located.

15. A method for confirming that DOCSI-compliant devices operating in a hybrid-fiber-coax (HFC) cable network are co-located comprising:

acquiring a first ranging offset value associated with a first DOCSIS-enabled device (DED) and a second ranging offset value associated with a second DED, wherein the first and second DEDs are associated with a subscriber account;

applying a first normalization factor to the first ranging offset value to obtain a first normalized ranging offset value and apply a second normalization factor to the second ranging offset value to obtain a second normalized ranging offset value;

determining a “delta” offset value equal to the absolute value of the difference between the first normalized ranging offset value and the second normalized ranging offset value;

determining whether the delta offset value exceeds a predetermined threshold;

sending an alert to a co-location alert manager if the delta offset value exceeds the predetermined threshold;

acquiring a first cable MAC domain identifier associated with the first DED and a second MAC domain identifier associated with the second DED;

determining whether the first MAC domain identifier differs from the second MAC domain identifier; and

sending an alert to the alert manager if the first MAC domain identifier differs from the second MAC domain identifier.

16. The method for confirming that DOCSIS-compliant devices operating in an HFC cable network are co-located of claim 15 , wherein a DED comprises a standalone DED.

17. The method for confirming that DOCSJS-compliant devices operating in an HFC cable network of claim 15 are co-located, wherein a DED comprises a component within a device connectable to the HFC cable network.

18. The method for confirming that DOCSJS-compliant devices operating in an HFC cable network are co-located of claim 15 further comprising acquiring subscriber account data for the subscriber account, wherein subscriber account data comprises a subscriber account number, a first MAC address associated with the first DED and a second MAC address associated with the second DED.

19. The method for confirming that DOCSIS-compliant devices operating in an HFC cable network are co-located of claim 18 , wherein the acquiring the first ranging offset value associated with the first DOCSIS-enabled device (DED) and the second ranging offset value associated with the second DED comprises polling a cable modem termination system using the first and second MAC addresses.

20. The method for confirming that DOCSIS-compliant devices operating in an HFC cable network are co-located of claim 15 further comprising:

sending a confirmation command to the first and second DEDs;

receiving a first response from the first DED to the first confirmation command and a second response from the second DED to the second confirmation command;

determining from the first and second response whether the first DED and second DED are co-located; and

sending a confirmed alert to the co-location alert manager if the first DED and second DED are not co-located.