Providing a configuration file to a communication device

[0002] This invention relates to providing a configuration file to a communication device such as a modem.

[0003] In the case of a cable modem that couples cable television (“CATV”) cable to a personal computer (“PC”), for example, a configuration file is sent on the cable from a cable modem termination system (“CMTS”) to the cable modem. The configuration file includes configuration information that defines the modem's access to services on the cable network, such as an amount of bandwidth that will be available to the modem.

[0004] In general, in one aspect of the invention, a configuration file is provided to a communication device. Identification information associated with the communication device is received and configuration information is retrieved from a database based on the identification information. A configuration file is generated from the configuration information and it is then provided to the communication device.

[0005] Among the advantages of the invention may be one or more of the following. The configuration file can be custom-tailored rather than using an existing file. Consequently, there is less chance that the communication device will receive the wrong configuration file. Authentication may also be included to further reduce the chances that the wrong configuration file will be received.

[0006] Other features and advantages of the invention will become apparent from the following description and the claims.

[0007] FIG. 1 shows a network system according to one embodiment of the invention.

[0008] FIG. 2 shows an architecture of a CMTS according to one embodiment of the invention.

[0009] FIG. 3 shows a process for providing a configuration file to a communication device according to one embodiment of the invention.

[0010] FIG. 4 shows a process for authenticating a request for a configuration file according to one embodiment of the invention.

[0011] FIG. 5 shows a structure of a configuration file according to one embodiment of the invention.

[0012] FIG. 1 shows a network system 1. Network system 1 includes processing device 2, modem 4, broadband network 5, CMTS 6, and external network 7 such as the Internet.

[0013] Broadband network 5 is an existing CATV cable network with connections to CMTS 6 and subscribers' homes (not shown). Hybrid fiber coaxial cable (“HFC”) is the primary physical transmission medium of broadband network 5. Signals run in standard fiber-optic cables from a central location such as CMTS 6 to locations near the subscriber. From there, standard coaxial cables run into the subscribers' homes.

[0014] In one embodiment, modem 4 is a DOCSIS (“Data-Over-Cable Service Interface Specifications”) compliant cable modem (see “Data-Over-Cable Interface Specifications: Radio Frequency Interface Specification”, SP-RFlv1.1-l01-990311 (Mar. 11, 1999)). Modem 4 includes a standard coaxial receptacle 9 for interfacing to broadband network 5. Through this interface, modem 4 transmits data from processing device 2 to broadband network 5 (upstream) and from broadband network 5 to processing device 2 (downstream). In FIG. 1, modem 4 is a PCI (“Peripheral Component Interconnect”) bus add-in card on processing device 2; however a stand-alone modem with a local processor may be used instead.

[0015] Processing device 2 includes a processor 12 and a memory 10 for storing code 11 (see view 14). Examples of processing devices are a personal computer (“PC”) (depicted), a settop box, and a digital television. Processor 12 executes code 11 to communicate with modem 4, to include cryptographic certificate(s) in requests sent from modem 4 (see below), and to generate digital signatures for the certificates. A digital signature is created by generating a hash value of a certificate's body (e.g., text) and encrypting the hash using the modem's private key. In a stand-alone modem, these functions may be performed in the modem itself.

[0016] CMTS 6 interfaces external network 7 to broadband network 5 and thus to cable modems on broadband network 5. CMTS is usually controlled by a CATV company, which also controls the broadband network. FIG. 2 shows the architecture of CMTS 6.

[0017] CMTS 6 includes upstream demodulator 15, downstream modulator 16, and router 19. Computer 20 is shown as external to CMTS 6, though it may be internal as well. Upstream demodulator 15 mediates data flow from broadband network 5 to router 19; and downstream modulator 16 mediates data flow from router 19 to broadband network 5. Router 19 routes data packets among upstream demodulator 15, downstream modulator 16, computer 20, and external network 7. Router 19 includes a memory 21 which stores routing code 22 and a processor 24 which executes the routing code (see view 25).

[0018] Computer 20 includes a processor 26 and a memory 27 (see view 23). Memory 27 stores a database 29 which, if necessary, can span several computers. Database 29 includes configuration information for modem 4 and other modems on broadband network 5. This configuration information can be compiled manually or through an “on-line sign-up sheet” such as an HTML (“HyperText Mark-up Language”) form that is filled-out by a user during a first connection of a modem to broadband network 5. In database 29, configuration parameters are indexed to identification information for a corresponding modem. This identification information may be the IP (“Internet Protocol”) address or the MAC (“Media Access Control”) address of the modem, or any other type of identification information such as information contained in a digital certificate.

[0019] The configuration information in database 29 describes the services that a modem is entitled to, and is sufficient to allow the modem to connect to, and operate on, the network. It includes one or more of the following for each modem on the broadband network 5: network access configuration setting, DOCSIS 1.0 class of service configuration setting, upstream service flow configuration setting, downstream service flow configuration setting, downstream frequency configuration setting, upstream channel ID (“IDentifier”) configuration setting, baseline privacy configuration setting, software upgrade file name configuration setting, upstream packet classification setting, SNMP (“Simple Network Management Protocol”) write-access control, SNMP MIB (“Management Information Base”) object, software server IP address, CPE (“Customer Premise Equipment”) Ethernet MAC address, maximum number of CPEs, maximum number of classifiers, privacy enable configuration setting, payload header suppression, TFTP (“Trivial File Transfer Protocol”) server timestamp, TFTP server provisioned modem address, pad configuration settings, telephone settings options, and vendor-specific configuration settings. DOCSIS 1.0 class of service configuration setting, upstream service flow configuration setting, and downstream service flow configuration setting specify amounts of bandwidth allocated to modem 4 on broadband network 5.

[0020] Memory 27 also stores code 30, which is comprised of instructions for execution by processor 26. Code 30 includes smart TFTP server 31, authentication server 32, SNMP manager 34, SQL (“Simple Querying Language”) server 35, and DHCP (“Dynamic Host Configuration Protocol”) server 36. SNMP manager 34 is provided for IP-based modem-network management. SQL server 35 manages access to database 29. Authentication server 32 verifies that requests for a configuration file from modem 4 actually did originate from modem 4. DHCP server 36 provides an address and the modem's configuration file name to smart TFTP server 31. Smart TFTP server 31 generates a configuration file for modem 4 from configuration information in database 29 and protects its content by generating a message integrity checksum which is embedded in the file. Smart TFTP server 31 then provides that configuration file to modem 4.

[0021] FIG. 3 shows a process for providing a configuration file to modem 4 using code 30. To begin, modem 4 issues a standard TFTP request for a configuration file to CMTS 6. This may be done when modem 4 is first connected to broadband network 5 or at a subsequent re-initialization. CMTS 6 receives the request in 301 and routes the request through upstream demodulator 15 and router 19 to computer 20, where the request is processed.

[0022] The request includes minimum identification information for modem 4, such as modem 4's source IP address and maybe its MAC address (for example, if smart TFTP server 31 is implemented on router 19 and the source MAC address is available). A standard TFTP request does not contain authentication information. Therefore, an additional mechanism is used for authentication.

[0023] More specifically, smart TFTP server 31 issues an SNMP query to modem 4 requesting authentication information. The SNMP query is addressed using modem 4's address in its original TFTP request. The SNMP query can be issued directly, or through SNMP manager 34. Modem 4 replies to the SNMP query with a certificate containing authentication information, which can be verified by authentication server 32, and then used to reference information in database 29 by issuing an SQL query to SQL server 35. The certificate may be an ITU (International Telecommunication Union) X.509 standard certificate.

[0024] Alternatively, a request for authentication information may be made through DOCSIS Baseline Privacy Plus (“BPI+”) MAC messaging. To do this, smart TFTP server 31 accesses a MAC messaging mechanism in CMTS 6. This can be done by encapsulating MAC messages in IP protocol frames.

[0025] Regardless of the communication method, once modem 4 supplies the certificate, it may be checked internally in smart TFTP server 31 or presented to authentication server 32 for verification. The certificate is encrypted, and contains a body, which may be plain text or the like, and a digital signature. The digital signature is generated by hashing the contents of the body using a standard hashing algorithm, such as MD5 (Message Digest 5).

[0026] Authentication server 32 determines if the request is authentic 302, meaning that it actually originated from modem 4, based on the authentication information in the certificate. FIG. 4 shows an authentication process.

[0027] To begin, authentication server 32 decrypts 401 the certificate using a public key that corresponds to the private key used for encryption. It then independently generates 402 a hash value from the body of the certificate. This generated hash value is compared 403 to the decrypted digital signature (hash value). If there is a match in 404, the request is deemed authentic in 405. Otherwise, the request is deemed not to be authentic in 406.

[0028] As an alternative to the FIG. 4 process, authentication server 32 may simply instruct SQL server 35 to locate, in database 29, an identifier of modem 4, such as its IP address, serial number, or MAC address. If the identifier is located, the request is deemed authentic, otherwise it is not. If database 29 indexes configuration information by MAC address, authentication of this type requires a mapping between the modem's MAC and IP addresses.

[0029] Returning to FIG. 3, if authentication server 32 determines that the request is not authentic, smart TFTP server 31 denies 303 the request. Denial may mean simply ignoring the request or instructing SNMP server 35 to issue a message indicating that the request has been denied. If the request is authentic, smart TFTP server 31 retrieves 304 configuration information for modem 4 from database 29.

[0030] Once the configuration information has been retrieved, smart TFTP server 31 generates 305 a configuration file for modem 4. A structure of a configuration file 37 is shown in FIG. 5.

[0031] Configuration file 37 includes parameters 39 that correspond to one or more of the foregoing modem configuration settings. It includes a type (i.e., an identity), a length, and a value for each parameter. Configuration file 37 also includes types, lengths, and values for CM MIC (“Message Integrity Checksum”) 40 and CMTS MIC 41. These checksum values are calculated based on the configuration settings in file 37. CM MIC 40 is used by modem 4 to ensure that the parameters in configuration file 37 were not altered during transmission from CMTS 6. CMTS MIC 41 is used to authenticate modem 4 to CMTS 6 during its registration. Finally, configuration file 37 includes an end of data marker 42.

[0032] Returning to FIG. 3, after the configuration file is generated, smart TFTP server 31 provides 306 the configuration file to modem 4 using standard TFTP protocol. Upon receipt, modem 4 configures 307 itself in accordance with the configuration file settings. Alternatively, modem 4 may provide the configuration file to processor 12 which then configures the modem based on the configuration file settings.

[0033] Other embodiments of the invention are within the scope of the following claims. For example, the processes of FIGS. 3 and 4 may be implemented by code running on processor 24 in router 19. Also, although the invention is described in the context of a DOCSIS-compliant cable modem and CMTS, it can be used with any type of communication device that receives a configuration file from a central location and that require reliable authentication. Depending upon the device, different (in terms of both content and structure) configuration parameters than those above may be used.