Initializing, provisioning, and managing devices

Information

  • Patent Grant
  • 12047230
  • Patent Number
    12,047,230
  • Date Filed
    Thursday, November 4, 2021
    3 years ago
  • Date Issued
    Tuesday, July 23, 2024
    4 months ago
Abstract
A method of initializing, provisioning, and managing a cable modem and a customer premise equipment device includes sending a customized configuration file to the cable modem. The configuration file contains service provisioning information and further includes information indicative of a network address type for the customer premise equipment device. A message is passed from the cable modem to the customer premise equipment device indicative of the network address type. The customer premise equipment device is provided with a network address in accordance with the network address type indicated in the message. In this way, the customer premise equipment device knows what kind of address to obtain, and excessive transactions are avoided.
Description
BACKGROUND OF THE INVENTION
1. Field of the Invention

The invention relates to a method of initializing, provisioning, and managing a cable modem and a customer premise equipment device. The invention further relates to a subscriber gateway device for connecting to a provider network.


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. In certain applications, it is desirable for both the cable modem and the set-top box to each have a network address. 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 where the provider network is an Internet protocol (IP) network utilizing IPv4 addressing, the cable modem can obtain an IP address in a 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.


Although the traditional IPv4 networks have been used for many applications that have been successful, this addressing approach has certain limitations, for example, the number of addresses available. There is a desire to utilize a more advanced addressing technique such as, for example, IPv6.


DOCSIS 3.0 does provide a way to initialize, provision, and manage a cable modem connected to an IPv4 or an IPv6 provider network. During initialization, the CMTS initializes the cable modem such that the cable modem obtains an appropriate IP address. However, in this approach, a customer premise equipment device such as a set-top box connected to the cable modem that needs to dynamically obtain an address is not made aware of the address type of the provider network. In order for the set-top box to obtain a network address, the set-top box could sequentially make requests for different types of addresses until eventually an address of the correct type is requested and obtained. For example, a set-top box could request an IPv4 address, and if there is no response, request an IPv6 address. Unfortunately, in a large network, these transactions create significant excessive and unwanted network traffic.


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 the customer premise equipment device is informed as to the proper network address type of the network so as to avoid unnecessary transactions which become very significant in a large network implementation.


SUMMARY OF THE INVENTION

In accordance with the invention, 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 accordance with the invention, the method further comprises passing a message from the cable modem to the customer premise equipment device indicative of the network address type. According to the invention, the configuration file, in addition to containing service provisioning information, further includes information indicative of a network address type for the customer premise equipment device. This further information may be included in a number of custom fields in the configuration file. Adding these custom fields to the configuration file as contemplated by the invention allows the configuration file to indicate the network address type for the customer premise equipment device. The customer premise equipment device receives the message passed from the cable modem, and is provided with a network address in accordance with the network address type indicated in the message.


According to the invention, the customer premise equipment device, in turn, does not create excessive network transactions in attempting to obtain its network address. This is achieved by including custom information in the configuration file sent to the cable modem from the network server. This configuration file typically includes various service provisioning information, and in accordance with the invention, additionally includes network address type information for the customer premise equipment device.


At the more detailed level, the invention comprehends additional features. In one aspect, the customer premise equipment device is a network addressable set-top box. The method further comprises requesting a network address for the set-top box in accordance with the network address type indicated in the message. The set-top box and the cable modem may be both embedded in a subscriber gateway.


The provider network connected to the CMTS may be an Internet protocol (IP) network. In this way, the network address type indicated in the configuration file is a type of IP address. For example, the network address type may be indicated as either IPv4 or IPv6. In this way, the embedded set-top box in the subscriber gateway (or other CPE device) knows whether to attempt to obtain an IPv4 address or an IPv6 address, avoiding unnecessary network transactions in order to obtain a network address.


In one aspect of the invention, the provider network includes a dynamic host configuration protocol (DHCP) server. The customer premise equipment device requests a network address in accordance with the network address type indicated in the message by sending a request to the DHCP server.


In preferred embodiments of the invention, the cable modem has a hardware address, for example, a media access control (MAC) address. The network address type for the CPE device indicated by information in the configuration file sent from the network server is based at least in part on the hardware address of the cable modem. That is, configuration files may be customized on a per-modem basis. For example, some set-top boxes may be using IPv4 while others are using IPv6. The provider is able to select a network address type for each customer premise equipment device. This allows a granular approach to implementing the network addressing scheme, and avoids the need to use a single type of addressing for the entire network.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 illustrates a network diagram in accordance with a preferred embodiment of the invention; and



FIG. 2 illustrates initializing, provisioning, and managing a cable modem and a customer premise equipment device in the preferred embodiment of the invention.





DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

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. Further illustrated in FIG. 1, CMTS 20 connects to the provider 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, a preferred 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 is provided with a network address. In more detail, the cable modem is initialized and provisioned using a suitable technique such as known DOCSIS techniques. At block 54, the cable modem 14 receives the cable modem configuration file, for example, from trivial file transfer protocol (TFTP) server 64. At block 56, services are configured. 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, in accordance with the invention, the configuration file sent to the cable modem includes service provisioning information and further includes information indicative of a network address type for the embedded set-top box 16 (or other CPE device). The inclusion of this network address type information in the configuration file is a customization to the configuration file in accordance with the invention that has many advantages. This customization may take place by, for example, adding custom fields to the configuration file. According to the invention, cable modem 14 passes a message to the set-top box 16 indicating the network address type. The message passing is indicated at block 58 in FIG. 2. The message passing may take any appropriate form. For example, a direct, dedicated connection between embedded cable modem 14 and embedded set-top box 16 may be used for the message passing. Depending on the application, other approaches may be appropriate, for example, when the CPE device is something other than an embedded set-top box.


At block 60, the message is received, and at block 62, the network address is requested in accordance with the network address type indicated in the message.


It is appreciated that the invention, by customizing the configuration file, provides a way for the embedded set-top box or other CPE device behind the cable modem to make an appropriate request for a network address from the provider network 30. By informing the embedded set-top box 16 of the appropriate network address type, excessive and unnecessary transactions may be avoided. The significance of avoiding these unnecessary transactions increases in a larger network. For example, IP network 30 may be an IPv4, IPv6, or mixed IPv4 and IPv6 network. Suitable techniques for initializing and provisioning the cable modem are used to give the cable modem an appropriate network address. However, in order for the set-top box or other CPE device to be aware of the type of address to request, the cable modem must pass a message to the CPE device as described above.


In a preferred embodiment of the invention, the provider network may take a granular approach to migrating CPE devices between network address types. For example, the network may simultaneously support IPv4 and IPv6 addressing. In this example, for each cable modem/CPE device pair, the network address type for the CPE device is related to the hardware address of the cable modem by the provider. Accordingly, the configuration file sent to a particular cable modem indicates the appropriate network address type for the CPE device paired with the particular cable modem.


It is appreciated that embodiments of the invention may involve any suitable underlying initializing and provisioning technique with a customized configuration file. 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 of the invention 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: sending, by a server and to a gateway, a configuration file specifying a network address type corresponding to a first protocol of a plurality of protocols, wherein the configuration file is configured to cause the gateway to send, to customer premises equipment connected via a network to the gateway, a message specifying the network address type; andreceiving, by the server and from the customer premises equipment, a request for a network address of the specified network address type.
  • 2. The method of claim 1, wherein the configuration file comprises one or more fields indicating that the network address type corresponding to the first protocol should be used for the customer premises equipment.
  • 3. The method of claim 1, further comprising: determining, based on a hardware address of the gateway, the network address type corresponding to the first protocol.
  • 4. The method of claim 3, wherein the hardware address is a media access control address.
  • 5. The method of claim 1, wherein the first protocol is one of Internet Protocol version 4 or Internet Protocol version 6.
  • 6. The method of claim 1, wherein the configuration file comprises information for provisioning services via the gateway.
  • 7. The method of claim 1, further comprising, prior to the sending, provisioning, by the server, the gateway with a network address of the network address type.
  • 8. The method of claim 1, wherein the configuration file indicates: a first network address type associated with a first hardware address, anda second network address type associated with a second hardware address.
  • 9. A method comprising: receiving, from a network server, a gateway configuration file specifying a network address type corresponding to a first protocol of a plurality of protocols;processing, by a first device, the gateway configuration file; andsending, from the first device and to a second device, a message instructing the second device to use the network address type corresponding to the first protocol when requesting, from the network server, a network address for the second device.
  • 10. The method of claim 9, wherein the network address type corresponding to the first protocol is based at least in part on a hardware address of the first device.
  • 11. The method of claim 10, wherein the hardware address is a media access control address.
  • 12. The method of claim 9, wherein the first protocol is a version of Internet Protocol (“IP”).
  • 13. The method of claim 12, wherein the version of IP is one of version 4 and version 6.
  • 14. The method of claim 9, comprising: establishing, by the first device, a connection, wherein the first device receives a communication from the second device and forwards the communication via the connection.
  • 15. The method of claim 9, wherein the gateway configuration file comprises service-provisioning information.
  • 16. A method comprising: initializing a connection between a gateway and a modem termination system;receiving, by the gateway, a configuration file from a network server, wherein the configuration file contains service provisioning information and information indicative of a network address type for a customer premise equipment device; andsending a message from the gateway to the customer premise equipment device indicative of the network address type informing the customer premise equipment device which one of a plurality of protocol versions to use when requesting a network address.
  • 17. The method of claim 16, wherein the network address type indicated in the configuration file is a type of Internet Protocol (“IP”) address, the method further comprising: determining an IP address type from the network address type.
  • 18. The method of claim 17, wherein the determining comprises: including an instruction in the message instructing the customer premise equipment device to use either an IP version 4 address type or an IP version 6 type when requesting the network address.
  • 19. The method of claim 16, wherein the gateway has a hardware address, and wherein the network address type indicated by information in the configuration file is based at least in part on the hardware address of the gateway.
  • 20. The method of claim 19, further comprising: establishing a plurality of network address types;for a plurality of gateway and customer premise equipment device pairs, selecting a network address type for each customer premise equipment device; andrelating the network address type for each customer premise equipment device to the hardware address of the gateway in the respective pair.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 16/197,758, filed Nov. 21, 2018, which is a continuation of U.S. patent application Ser. No. 13/429,962, filed Mar. 26, 2012, now U.S. Pat. No. 10,171,293, which is a continuation of U.S. patent application Ser. No. 11/603,396 filed Nov. 22, 2006, now U.S. Pat. No. 8,149,847, which claims the benefit of U.S. Provisional Application No. 60/739,472 filed Nov. 23, 2005 and U.S. Provisional Application No. 60/791,803 filed Apr. 13, 2006. The entire disclosures of all priority applications are hereby incorporated by reference in their entireties.

US Referenced Citations (193)
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
6070246 Beser May 2000 A
6308289 Ahrens et al. Oct 2001 B1
6351773 Fijolek et al. Feb 2002 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
6598057 Synnestvedt et al. Jul 2003 B1
6603758 Schmuelling et al. Aug 2003 B1
6636485 Fijolek et al. Oct 2003 B1
6654387 Beser et al. Nov 2003 B1
6657991 Akgun et al. Dec 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
6768743 Borella 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
6996621 Borella et al. Feb 2006 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
7092397 Chandran et al. Aug 2006 B1
7107326 Fijolek et al. Sep 2006 B1
7120139 Kung et al. Oct 2006 B1
7127049 Godse et al. Oct 2006 B2
7142510 Beddus Nov 2006 B1
7158543 Garakani et al. Jan 2007 B1
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
7353021 Ejzak et al. Apr 2008 B2
7356841 Wilson et al. Apr 2008 B2
7372809 Chen et al. May 2008 B2
7373660 Guichard et al. May 2008 B1
7415603 Woundy et al. Aug 2008 B2
7443883 Seiden Oct 2008 B2
7467214 Chin Dec 2008 B2
7484234 Heaton et al. Jan 2009 B1
7496485 Elfadel et al. Feb 2009 B2
7496652 Pezzutti Feb 2009 B2
7502841 Small 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, III et al. Dec 2010 B2
7881225 Siripunkaw et al. Feb 2011 B2
8015271 McKeown et al. Sep 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
8493987 Siripunkaw et al. Jul 2013 B2
8914522 Rao et al. Dec 2014 B2
20010038690 Palmer et al. Nov 2001 A1
20010049732 Raciborski et al. Dec 2001 A1
20010051980 Raciborski et al. Dec 2001 A1
20010053159 Bunn et al. Dec 2001 A1
20020010865 Fulton et al. Jan 2002 A1
20020012320 Ogier 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
20020066033 Dobbins 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
20030018805 Meyerson Jan 2003 A1
20030067896 Chuah et al. Apr 2003 A1
20030069965 Ma et al. Apr 2003 A1
20030076848 Bremler-Barr et al. Apr 2003 A1
20030106067 Hoskins et al. Jun 2003 A1
20030135578 Banga et al. Jul 2003 A1
20030145075 Weaver et al. Jul 2003 A1
20030179742 Ogier et al. Sep 2003 A1
20030200548 Baran et al. Oct 2003 A1
20030236914 Liu Dec 2003 A1
20040024912 Fukao et al. Feb 2004 A1
20040037316 Choi et al. Feb 2004 A1
20040048609 Kosaka Mar 2004 A1
20040095923 Ejzak et al. May 2004 A1
20040103308 Paller May 2004 A1
20040153665 Browne Aug 2004 A1
20040177133 Harrison et al. Sep 2004 A1
20040179508 Thubert 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
20040214576 Myers et al. Oct 2004 A1
20040226051 Carney et al. Nov 2004 A1
20040242233 Lutgen Dec 2004 A1
20050002388 Gao Jan 2005 A1
20050005154 Danforth Jan 2005 A1
20050034115 Carter et al. Feb 2005 A1
20050047442 Volpe et al. Mar 2005 A1
20050055595 Frazer et al. Mar 2005 A1
20050055708 Gould et al. Mar 2005 A1
20050060749 Hong et al. Mar 2005 A1
20050078668 Wittenberg et al. Apr 2005 A1
20050078688 Sharma et al. Apr 2005 A1
20050114518 McMahon et al. May 2005 A1
20050122976 Poli et al. Jun 2005 A1
20050123001 Craven et al. Jun 2005 A1
20050204168 Johnston et al. Sep 2005 A1
20050220126 Gervais et al. Oct 2005 A1
20050232304 Quigley Oct 2005 A1
20050233742 Karaoguz et al. Oct 2005 A1
20050246757 Relan et al. Nov 2005 A1
20060002294 Chapman et al. Jan 2006 A1
20060031436 Sakata et al. Feb 2006 A1
20060031921 Danforth et al. Feb 2006 A1
20060059092 Burshan et al. Mar 2006 A1
20060085833 Kwon Apr 2006 A1
20060095951 Kwon May 2006 A1
20060104232 Gidwani May 2006 A1
20060123118 Choe et al. Jun 2006 A1
20060159100 Droms Jul 2006 A1
20060173977 Ho et al. Aug 2006 A1
20060184640 Hatch Aug 2006 A1
20060191005 Muhamed et al. Aug 2006 A1
20060206586 Ling et al. Sep 2006 A1
20060223497 Gallagher et al. Oct 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
20060293962 Malobrodsky et al. Dec 2006 A1
20070011725 Sahay et al. Jan 2007 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
20070183363 Liden Aug 2007 A1
20070183405 Bennett Aug 2007 A1
20070214265 Zampiello et al. Sep 2007 A1
20080034071 Wilkinson et al. Feb 2008 A1
20080060064 Wynn et al. Mar 2008 A1
20080064349 Flask et al. Mar 2008 A1
20080141369 Butti et al. Jun 2008 A1
20080189778 Rowley Aug 2008 A1
20080209537 Wong et al. Aug 2008 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
20100083362 Francisco Apr 2010 A1
20100296441 Barkan Nov 2010 A1
20110026536 Siripunkaw et al. Feb 2011 A1
20130091534 Gilde et al. Apr 2013 A1
20150012970 Toksvig et al. Jan 2015 A1
Foreign Referenced Citations (1)
Number Date Country
2005079000 Aug 2005 WO
Non-Patent Literature Citations (15)
Entry
ISR issued in PCT/US08/081422, mail date Dec. 23, 2008.
EP Search Report 08 84 6111, dated Feb. 7, 2011.
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.
Canadian Office Action—Canadian Application 2568740—Dated Jan. 26, 2015.
Canadian Office Action—CA 2,568,741—Mailing Date: Feb. 18, 2015.
Canadian Office Action, dated Mar. 26, 2015—CA 2,700,625.
Response to Canadian Office Action—CA 2,568,740—Dated Jul. 13, 2015.
Response to Canadian Office Action—CA Appl. 2,568,741—submitted Aug. 18, 2015.
Canadian Office Action—CA Appl. 2,568,743—dated Apr. 2, 2015.
Response to Canadian Office Action—CA 2,700,625—Dated Sep. 14, 2015.
Response to Canadian Office Action—CA 2,568,743—Dated Oct. 1, 2015.
Canadian Office Action—CA Appl. 2,700,625—dated Feb. 26, 2016.
Canadian Office Action—CA 2,568,741—Mailed May 10, 2016.
Sep. 17, 2018—Canadian Office Action—CA 2,700,625.
Related Publications (1)
Number Date Country
20220060376 A1 Feb 2022 US
Provisional Applications (2)
Number Date Country
60791803 Apr 2006 US
60739472 Nov 2005 US
Continuations (3)
Number Date Country
Parent 16197758 Nov 2018 US
Child 17518630 US
Parent 13429962 Mar 2012 US
Child 16197758 US
Parent 11603396 Nov 2006 US
Child 13429962 US