Device-specific pre-provisoining access-limiting for a modem and a consumer premise equipment device

Abstract
A method of initializing, provisioning, and managing a cable modem and a customer premise equipment device includes, prior to receiving the configuration file for the cable modem, providing an equipment identification message containing a description of the customer premise equipment device connected to the cable modem. In the case where the cable modem has yet to be provisioned, the configuration file received from the network server is a particular access-limiting configuration file that is selected from a group of access-limiting configuration files. The selection of the particular access-limiting configuration file is based on the description of the customer premise equipment device in the equipment identification message. This allows different devices to have different network restrictions or different walled gardens.
Description
BACKGROUND

1. Field


Features herein relate to a method of initializing, provisioning, and managing a cable modem and a customer premise equipment device. The features further relate to cable modem configuration files, including the use of an access-limiting configuration file in a case where the cable modem has yet to be provisioned. The access-limiting configuration file restricts network access from the cable modem until the cable modem is provisioned.


2. Background Art


The modern hybrid fiber coax (HFC) network in its typical implementation includes fiber from the head end to the local network fiber node, and includes coax cable for the final signal distribution through a neighborhood. Modern two-way HFC infrastructures are capable of sending gigabytes of data per second to small pockets of homes in a narrowcast way.


Product and service offerings over broadband networks, including cable networks, have expanded in recent years. The cable networks are now used for additional products and services, for example, many cable networks now offer high speed data service in addition to video programming. In the modern HFC network, head end infrastructure may include a cable modem termination system (CMTS) for providing data over cable services in addition to video quadrature amplitude modulation (QAM) infrastructure for providing video content. The video QAMs may connect to various content sources, while the CMTS connects subscribers to the provider network. The provider network may include a variety of infrastructure for providing various services. For example, the provider network may include Domain Name System (DNS) servers, dynamic host configuration protocol (DHCP) servers, voice over Internet protocol (VoIP) gateways and soft switches for connecting to phone networks, among other systems for providing services to subscribers. Further, advances in network technology allow some functionality to be provided from locations upstream or downstream of the traditional head end.


At a subscriber location, a cable modem and a customer premise equipment device such as a set-top box communicate with the head end over the HFC network. Traditionally, the cable modem utilizes known initializing and provisioning techniques to obtain a network address and establish a connection to the provider network. For example, the data-over-cable service interface specifications (DOCSIS) specify various protocols for managing the connection of a cable modem to a CMTS. In a traditional application, the cable modem can obtain an IP address in an known manner, and customer premise equipment connected to the HFC network through the cable modem may obtain an IP address, for example, by utilizing DHCP.


In an existing method of initializing a cable modem, the cable modem connection to the CMTS is initialized, the cable modem is provided with a network address, and the cable modem receives a cable modem configuration file from a network server. The configuration file contains service provisioning information. In order to configure services, the cable modem passes certain contents of the configuration file to the CMTS, and the CMTS passes certain identifiers back to the cable modem.


Typically, a service provider restricts or limits access to the network by a cable modem until the service provider validates the cable modem through a provisioning process. In one approach, the service provider maintains a list of hardware addresses for validated cable modems. When a cable modem attempts to initialize, if the hardware address is in the list of valid cable modem hardware addresses, the cable modem is allowed normal access to network resources. In the case where a cable modem has yet to be provisioned, a restricted environment may be provided for the cable modem.


One approach to providing this restricted environment, referred to as a walled garden, involves a single, special configuration file provided in all cases where the cable modem has yet to be provisioned. This special configuration file restricts network access from the cable modem. After the cable modem is provisioned, the cable modem would then receive a regular configuration file as opposed to the special configuration file that keeps the cable modem within the walled garden. Although existing methods of initializing cable modems can limit network access for cable modems that have not been validated, a more comprehensive approach is needed as additional products and services are added in a modern HFC network.


For the foregoing reasons, there is a need for a method of initializing, provisioning, and managing a cable modem and a customer premise equipment device in which, in a case where the cable modem has yet to be provisioned, there is greater flexibility in providing restricted access.


SUMMARY OF THE DISCLOSURE

A method of initializing, provisioning, and managing a cable modem and a customer premise equipment device is provided. The customer premise equipment device is connected to the cable modem. The cable modem is connected to a cable modem termination system (CMTS). The CMTS is connected to a provider network.


The method includes initializing the cable modem connection to the CMTS, providing the cable modem with a network address, and the cable modem receiving a cable modem configuration file from a network server. The configuration file contains service provisioning information. The cable modem passes certain contents of the configuration file to the CMTS, and the CMTS passes certain identifiers back to the cable modem. These initial steps for initializing and provisioning the cable modem may take place in any suitable way.


In a case where the cable modem has yet to be provisioned, the configuration file is in access-limiting configuration file. The access-limiting configuration file restricts network access from the cable modem until the cable modem is provisioned. Prior to receiving the configuration file, the cable modem provides an equipment identification message. The equipment identification message contains a description of the customer premise equipment device connected to the cable modem. For example, when the customer premise equipment device is a network addressable set-top box, the equipment identification message describes the customer premise equipment device as the network addressable set-top box.


The configuration file received from the network server, in the case where the cable modem has yet to be provisioned, is a particular access-limiting configuration file that is selected from a group of access-limiting configuration files. The selection of the particular access-limiting configuration file from the group is based on the description of the customer premise equipment device in the equipment identification message.


Different customer premise equipment devices may have corresponding different access-limiting configuration files for use when provisioning has not yet occurred. For example, a subscriber gateway including an embedded set-top box and an embedded cable modem may receive a specific access-limiting configuration file when the cable modem has yet to be provisioned. On the other hand, some other customer premise equipment device may receive a different access-limiting configuration file when its cable modem has yet to be provisioned. In this way, different devices receive corresponding different restrictions to network resources when they are in the unprovisioned state. Put another way, different devices find themselves in different walled gardens.


It is appreciated that the equipment identification message may take any suitable form. As well, any suitable approach may be used to assure that the appropriate configuration file is received from the network server. For example, a trivial file transfer protocol (TFTP) server may serve the configuration files. Earlier in the initialization process, the cable modem is provided with the location of the server and appropriation configuration file to fetch. This appropriate configuration file is determined based on the equipment identification message provided by the cable modem during cable modem initialization.


Additional features may be used as well. In one aspect, the access-limiting configuration file restricts access from the cable modem and directs any network content requests to a provisioning server. In some embodiments, various approaches may be taken to restrict network access, depending on the application. For example, when the network is an Internet protocol (IP) network including Domain Name System (DNS) servers, IP filtering and/or address resolution manipulation may be used to restrict access to the network, that is, to keep the device within its walled garden. For example, IP filtering may assure that only certain resources may be reached. For example, network address resolution manipulation may redirect all network content requests to the provisioning server.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 illustrates a network diagram in accordance with an embodiment described herein; and



FIG. 2 illustrates initializing, provisioning, and managing a cable modem and a customer premise equipment device in an embodiment herein.





DETAILED DESCRIPTION

In FIG. 1, the hybrid fiber coax (HFC) network 10 provides service to a plurality of subscribers. Each subscriber has a subscriber gateway 12. The subscriber gateway 12 is in the form of a next-generation set-top box and includes an embedded cable modem 14 and an embedded set-top box 16. The head end equipment includes cable modem termination system (CMTS) 20 and a plurality of video quadrature amplitude modulation (QAM) systems 22. Connector 18 illustrates the distribution of content from video QAMs 22 and data over cable from CMTS 20 over HFC network 10. In general, the HFC forward path spectrum includes a plurality of channels. Video QAMs 22 provide programming on the channels. Some channels are reserved for data over cable connections provided by CMTS 20. Video QAMs 22 receive content from any number of sources such as content sources 24.


It is appreciated that the architecture for the head end may vary. In FIG. 1, CMTS 20 connects to the provider Internet protocol (IP) network 30. Various services are provided to the subscribers; IP network 30 includes the appropriate infrastructure for the needed services. As shown, the network may include Domain Name System (DNS) server 32, dynamic host configuration protocol (DHCP) server 34, and voice over Internet protocol (VoIP) gateway 36 and soft switch 38 for connecting to a telephone network 40. The various servers may be located at the head end, or may be located at other locations connected to the provider network 30. Also, illustrated is trivial file transfer protocol (TFTP) server 64 which serves the configuration files.


With reference to FIGS. 1 and 2, an example embodiment of initializing, provisioning, and managing a cable modem and a customer premise equipment device is illustrated. The customer premise equipment device is depicted as an embedded set-top box 16, but may take other forms.


At block 50, the cable modem connection to the CMTS 20 is initialized. At block 52, the cable modem 14 advertises the description of the customer premise equipment device 16. This is the providing of the equipment identification message. At block 54, the cable modem 14 is provided with a network address. In more detail, the cable modem 14 is initialized and provisioned using a suitable technique such as known DOCSIS techniques. At block 56, the cable modem 14 receives the cable modem configuration file, for example, from trivial file transfer protocol (TFTP) server 64. Specifically, in the case where the cable modem 14 has yet to be provisioned, a particular access-limiting configuration file that is selected from a group of access-limiting configuration files is received. The selection of the particular access-limiting configuration file from the group is based on the description of the customer premise equipment 16 in the equipment identification message. In this way, different devices may have different restrictions. Put another way, different devices have different walled gardens 66.


For example, one possible implementation is that each kind of CPE device has its own particular access-limiting configuration file that is used when the CPE device's cable modem is not yet provisioned to provide its own particular walled garden. In a straight forward implementation, each device's walled garden 66 contains only network resources related to device provisioning (possibly including self-provisioning). Further, in this example, a set-top box would be in a walled garden designed specifically for set-top boxes, while some other device would be in a walled garden designed specifically for that device. For example, a walled garden for STBs could contain access to certain video servers while some other device has a walled garden that does not include such access. Embodiments include device-specific walled gardens implemented via device specific configuration files that are selected based on an equipment identification message that advertises a description of a connected CPE device.


After the cable modem 14 receives the cable modem configuration file, services are configured. In the case where the cable modem 14 has yet to be provisioned, services, if any, are configured at block 58. At this point, the cable modem 14 has completed initialization, and is a manageable network element in the operator's IP network.


Generally, the initializing and provisioning may take place according to DOCSIS standards or any other suitable approach involving a downloaded configuration file; however, the configuration file sent to the cable modem includes service provisioning information and further, in the case where the cable modem has yet to be provisioned, the configuration file is a particular access-limiting configuration file that is selected from a group of access-limiting configuration files. Put another way, different devices have different walled gardens or different network restrictions. This approach has many advantages. The equipment identification message may be provided in any appropriate way such that the cable modem can be notified of the appropriate configuration file to download from the network server. For example, the cable modem may advertise the description of the CPE device, that is, provide an equipment identification message, during a suitable dynamic configuration technique. A dynamic configuration response may include the name and location of the needed access-limiting configuration file.


It is appreciated that embodiments may involve any suitable underlying initializing and provisioning technique with different devices being provided with different access-limiting configuration files, that is, different devices having different walled gardens. Further, the cable modem and CMTS may take a variety of forms and the type of cable plant is not limited to coax cable or HFC arrangements.


While embodiments have been illustrated and described, it is not intended that these embodiments illustrate and describe all possible forms of the invention. Rather, the words used in the specification are words of description rather than limitation, and it is understood that various changes may be made without departing from the spirit and scope of the invention.

Claims
  • 1. A method comprising: receiving a request for access provisioning from a device in an unprovisioned state on a network managed by a computing apparatus;identifying a plurality of different pieces of consumer-premise equipment to be serviced by the device; andtransmitting a plurality of device-specific configuration files to the device, each configuration file indicating a different walled garden for a corresponding one of the plurality of different pieces of consumer-premise equipment to be serviced by the device while the device is in the unprovisioned state.
  • 2. The method of claim 1, the transmitting further comprising transmitting different configuration files for different classes of the consumer-premise equipment.
  • 3. The method of claim 1, wherein each different walled garden permits a different level of network access for a different class of the consumer-premise equipment while the device is in the unprovisioned state.
  • 4. The method of claim 3, wherein while the device is in the unprovisioned state, one of the plurality of different walled gardens grants a first class of the consumer-premise equipment limited access to video-computing devices, and another of the plurality of different walled gardens denies a second class of the consumer-premise equipment access to the video-computing devices.
  • 5. The method of claim 1, wherein the device is a cable modem, the method further comprising granting network access to a first consumer-premise equipment of the plurality of different pieces of the consumer-premise equipment, the first consumer-premise equipment serviced by the cable modem before the cable modem is fully provisioned for network access.
  • 6. The method of claim 5, wherein the first consumer-premise equipment is a set-top box.
  • 7. The method of claim 6, wherein the network access granted to the set-top box before the cable modem is fully provisioned includes access to a video-computing device.
  • 8. The method of claim 7, wherein network access granted to non-set top-box consumer-premise equipment to be serviced by the cable modem does not include access to the video-computing device.
  • 9. The method of claim 1, wherein the device and at least one of the consumer-premise equipment are both embedded in a single device.
  • 10. A method comprising: identifying a plurality of different types of user devices to be serviced by a first computing device;transmitting a provisioning request to a second computing device, the request identifying the plurality of different types of user devices; andbefore receiving full provisioning from the second computing device, receiving, by the first computing device, a plurality of configuration files, each of the plurality of configuration files providing a different walled garden for a corresponding one of the plurality of different types of user devices.
  • 11. The method of claim 10, wherein each of the plurality of configuration files is associated with a plurality of different classes of user devices.
  • 12. The method of claim 10, wherein a plurality of different walled gardens permits a different level of network access for a different class of user device before the first computing device receives full provisioning.
  • 13. The method of claim 12, wherein each of the different walled gardens grants limited access for a first class of user device to video-computing devices, and denies access for a second class of user device to the video-computing devices.
  • 14. The method of claim 10, wherein the first computing device is a cable modem configured to provide network access to a first user device serviced by the cable modem before the cable modem is fully provisioned for network access, first user device being one of the plurality of different types of user devices.
  • 15. The method of claim 14, wherein the first user device is a set-top box.
  • 16. The method of claim 15, wherein the network access provided to the set-top box before the cable modem is fully provisioned includes access to a video-computing device.
  • 17. The method of claim 16, wherein network access provided to non-set top-box consumer-premise equipment to be serviced by the cable modem before the cable modem is fully provisioned does not include access to the video-computing devices.
  • 18. The method of claim 15, wherein the set-top box and cable modem are both embedded in a subscriber-gateway computing device.
  • 19. A method comprising: identifying, by a first computing device, a plurality of different user devices to be serviced by the first computing device;transmitting, by the first computing device, a provisioning request to a second computing device, the provisioning request identifying the plurality of different user devices; andbefore receiving full provisioning from the second computing device, receiving a plurality of configuration files, each of the plurality of configuration files providing a different walled garden for a corresponding one of the plurality of different user devices.
  • 20. The method of claim 19, further comprising granting, by the second computing device, a different level of network access to each of the plurality of different user devices serviced by the first computing device before the first computing device is fully provisioned.
RELATED APPLICATION

The present application is a Continuation of co-pending U.S. patent application Ser. No. 12/974,750, filed Dec. 21, 2010, entitled “Customer Premise Equipment Device-Specific Access-Limiting For a Cable Modem and a Customer Premise Equipment Device,” which is a Continuation of U.S. Pat. No. 7,881,225, Issue date Feb. 1, 2011 and filed Nov. 22, 2006, entitled “Customer Premise Equipment Device-Specific Access-Limiting For A Cable Modem And A Customer Premise Equipment Device,” which claims priority to U.S. Provisional Application No. 60/739,472, filed on Nov. 23, 2005, and U.S. Provisional Application No. 60/791,803, filed Apr. 13, 2006. Each of the above identified applications and/or patents are hereby incorporated by reference in its entirety.

US Referenced Citations (127)
Number Name Date Kind
5440632 Bacon et al. Aug 1995 A
5666293 Metz et al. Sep 1997 A
5845077 Fawcett Dec 1998 A
6023464 Woundy Feb 2000 A
6308289 Ahrens et al. Oct 2001 B1
6393585 Houha et al. May 2002 B1
6501750 Shaffer et al. Dec 2002 B1
6529910 Fleskes Mar 2003 B1
6553568 Fijolek et al. Apr 2003 B1
6560203 Beser et al. May 2003 B1
6570855 Kung et al. May 2003 B1
6574796 Roeck et al. Jun 2003 B1
6577642 Fijolek et al. Jun 2003 B1
6636485 Fijolek et al. Oct 2003 B1
6654387 Beser et al. Nov 2003 B1
6658000 Raciborski et al. Dec 2003 B1
6690655 Miner et al. Feb 2004 B1
6693878 Daruwalla et al. Feb 2004 B1
6715075 Loukianov Mar 2004 B1
6751299 Brown et al. Jun 2004 B1
6768722 Katseff et al. Jul 2004 B1
6822955 Brothers et al. Nov 2004 B1
6831921 Higgins Dec 2004 B2
6836806 Raciborski et al. Dec 2004 B1
6857009 Ferreria et al. Feb 2005 B1
6865613 Millet et al. Mar 2005 B1
6904460 Raciborski et al. Jun 2005 B1
6917675 Lazarus et al. Jul 2005 B2
6952428 Necka et al. Oct 2005 B1
7007080 Wilson Feb 2006 B2
7035270 Moore, Jr. et al. Apr 2006 B2
7039432 Strater et al. May 2006 B2
7058055 Mugica et al. Jun 2006 B2
7065047 Boxall et al. Jun 2006 B2
7085814 Gandhi et al. Aug 2006 B1
7120139 Kung et al. Oct 2006 B1
7127049 Godse et al. Oct 2006 B2
7213062 Raciborski et al. May 2007 B1
7272846 Williams et al. Sep 2007 B2
7285090 Stivoric et al. Oct 2007 B2
7293078 Danforth Nov 2007 B2
7293282 Danforth et al. Nov 2007 B2
7308700 Fung et al. Dec 2007 B1
7334258 Ford et al. Feb 2008 B1
7337217 Wang Feb 2008 B2
7356841 Wilson et al. Apr 2008 B2
7372809 Chen et al. May 2008 B2
7415603 Woundy et al. Aug 2008 B2
7443883 Seiden Oct 2008 B2
7496652 Pezzutti Feb 2009 B2
7502841 Small et al. Mar 2009 B2
7512969 Gould et al. Mar 2009 B2
7526538 Wilson Apr 2009 B2
7539193 Pfeffer et al. May 2009 B2
7568220 Burshan Jul 2009 B2
7600003 Okmianski et al. Oct 2009 B1
7609619 Naseh et al. Oct 2009 B2
7617517 Kay Nov 2009 B2
7647617 Bartfeld et al. Jan 2010 B2
7693171 Gould Apr 2010 B2
7710865 Naseh et al. May 2010 B2
7747772 Raciborski et al. Jun 2010 B2
7769886 Naseh et al. Aug 2010 B2
7836092 Alaniz et al. Nov 2010 B2
7839870 Siripunkaw et al. Nov 2010 B2
7848234 McKinnon Dec 2010 B2
7881225 Siripunkaw et al. Feb 2011 B2
8041824 Maeng Oct 2011 B1
8042132 Carney et al. Oct 2011 B2
8050194 Siripunkaw et al. Nov 2011 B2
8108911 Datla et al. Jan 2012 B2
20010038690 Palmer et al. Nov 2001 A1
20010049732 Raciborski et al. Dec 2001 A1
20010051980 Raciborski et al. Dec 2001 A1
20020010865 Fulton et al. Jan 2002 A1
20020013948 Aguayo et al. Jan 2002 A1
20020042819 Reichert et al. Apr 2002 A1
20020061012 Thi et al. May 2002 A1
20020103931 Mott Aug 2002 A1
20020106017 Dombkowski et al. Aug 2002 A1
20020116721 Dobes et al. Aug 2002 A1
20020147819 Miyakoshi et al. Oct 2002 A1
20020152384 Shelest et al. Oct 2002 A1
20030014764 Saladino et al. Jan 2003 A1
20030069965 Ma et al. Apr 2003 A1
20030106067 Hoskins et al. Jun 2003 A1
20030200548 Baran et al. Oct 2003 A1
20040024912 Fukao et al. Feb 2004 A1
20040037316 Choi et al. Feb 2004 A1
20040177133 Harrison et al. Sep 2004 A1
20040179539 Takeda et al. Sep 2004 A1
20040190699 Doherty et al. Sep 2004 A1
20040213278 Pullen et al. Oct 2004 A1
20040226051 Carney et al. Nov 2004 A1
20050034115 Carter et al. Feb 2005 A1
20050047442 Volpe et al. Mar 2005 A1
20050055595 Frazer et al. Mar 2005 A1
20050060749 Hong et al. Mar 2005 A1
20050078668 Wittenberg et al. Apr 2005 A1
20050122976 Poli et al. Jun 2005 A1
20050123001 Craven et al. Jun 2005 A1
20050204168 Johnston et al. Sep 2005 A1
20050246757 Relan et al. Nov 2005 A1
20060031436 Sakata et al. Feb 2006 A1
20060031921 Danforth et al. Feb 2006 A1
20060159100 Droms et al. Jul 2006 A1
20060173977 Ho et al. Aug 2006 A1
20060184640 Hatch Aug 2006 A1
20060206586 Ling et al. Sep 2006 A1
20060256799 Eng Nov 2006 A1
20060271772 Woundy et al. Nov 2006 A1
20060271946 Woundy et al. Nov 2006 A1
20060285544 Taylor et al. Dec 2006 A1
20070016762 Ho Jan 2007 A1
20070130471 Walker Pina et al. Jun 2007 A1
20070133409 McKinnon et al. Jun 2007 A1
20070174471 Van Rossum Jul 2007 A1
20070177526 Siripunkaw et al. Aug 2007 A1
20070180484 Siripunkaw et al. Aug 2007 A1
20070183405 Bennett Aug 2007 A1
20080285544 Qiu et al. Nov 2008 A1
20090005066 Florkey et al. Jan 2009 A1
20090063833 Ho Mar 2009 A1
20090125958 Siripunkaw et al. May 2009 A1
20090238349 Pezzutti Sep 2009 A1
20100064356 Johnston et al. Mar 2010 A1
20110026536 Siripunkaw et al. Feb 2011 A1
Non-Patent Literature Citations (4)
Entry
ISR issued in PCT/US06/45184, mail date Oct. 29, 2007.
International Preliminary Report on Patentability issued in PCT/US06/45184, mail date May 27, 2008.
ISR issued in PCT/US08/081422, mail date Dec. 23, 2008.
EP Search Report 08 84 6111, dated Feb. 7, 2011.
Related Publications (1)
Number Date Country
20120017234 A1 Jan 2012 US
Provisional Applications (2)
Number Date Country
60739472 Nov 2005 US
60791803 Apr 2006 US
Continuations (2)
Number Date Country
Parent 12974750 Dec 2010 US
Child 13238105 US
Parent 11603761 Nov 2006 US
Child 12974750 US