System and method for monitoring upstream and downstream transmissions in cable modem system

Abstract

A network monitor includes means for monitoring downstream traffic from a cable modem termination system (CMTS) to a cable modem (CM), means for monitoring upstream traffic from the CM to the CMTS, and means for identifying a data format used by the CMTS and the CM for bi-directional communication.

Description

BACKGROUND OF THE INVENTION

[0002] 1. Field of the Invention

[0003] The present invention relates to a network monitor, and more particularly, to a bidirectional network monitor/analyzer for use in a modem communications system.

[0004] 2. Related Art

[0005] Cable Modems and Cable Modem Termination Systems that conform to the DOCSIS 2.0 standard (Data Over Cable System Interface Specification 2.0, which is incorporated herein by reference) have been in operation in North America and Europe since the latter part of the 1990's. DOCSIS is an evolving standard and therefore modifications to formats and operation parameters are appropriate and expected as this standard develops. One such addition is the adoption of Synchronous Code Division Multiple Access (SCDMA) as a valid format for data transmission within DOCSIS 2.0. The hardware to support this standard is not currently fully developed. Concurrently, there is a need for system analytical tools that address SCDMA transmissions.

SUMMARY OF THE INVENTION

[0006] The present invention is directed to a cable network monitor that substantially obviates one or more of the problems and disadvantages of the related art.

[0007] There is provided a network monitor including means for monitoring downstream traffic from a cable modem termination system (CMTS) to a cable modem (CM), means for monitoring upstream traffic from the CM to the CMTS, and means for identifying a data format used by the CMTS and the CM for bi-directional communication.

[0008] Additional features and advantages of the invention will be set forth in the description that follows, and in part will be apparent from the description, or may be learned by practice of the invention. The advantages of the invention will be realized and attained by the structure particularly pointed out in the written description and claims, as well as in the appended drawings.

[0009] It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory and are intended to provide further explanation of the invention as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

[0010] The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description serve to explain the principles of the invention. In the drawings:

[0011] FIG. 1 illustrates a block diagram of a cable modem communications system;

[0012] FIG. 2 illustrates a block diagram of one embodiment of the present invention;

[0013] FIG. 3 illustrates a block diagram of an FPGA used in the present invention; and

[0014] FIG. 4 illustrates an SCDMA receiver architecture.

DETAILED DESCRIPTION OF THE INVENTION

[0015] Reference will now be made in detail to the preferred embodiments of the present invention, examples of which are illustrated in the accompanying drawings.

[0016] The system analyzer of the present invention may be a fully operational stand alone system that is also capable of operating as a fully functional DOCSIS 2.0 CMTS.

[0017] It can provide ranging and registering signaling for the DOCSIS 2.0 CM's on its plant, timing and synchronization for multiple (for example, dual) upstream channels conforming to the DOCSIS 2.0 SCDMA format and all the necessary maintenance signaling for providing continuous cable modem service using ATDMA (Advanced Time Division Multiple Access)/SCDMA. In addition to the support and supervisory node functions, the system can detect and parse downstream and upstream messages from another CMTS operating without any knowledge of the system's presence on the line. This system functions as a monitor that can parse UCD (upstream channel descriptor) and UCD2 messages, MAP's, TimeStamps, TimeStamp snapshots and record in memory all PDU's in the system memory for processing “off-line” or anytime such processing is desired. The monitoring functions of the system can synchronize the monitoring system to the CMTS that is controlling the signal path, without alerting the CMTS to its presence or requiring intervention from the CMTS. It can then enable the monitoring system to capture upstream bursts conforming to the SCDMA/ATDMA standard. There is currently no SCDMA monitoring system that can use the timing and control signaling communication between a CMTS and CM to self-synchronize itself to that system. Once self-synchronized to the CMTS-CM's present, the monitor can then analyze upstream bursts which are destined for reception by the CMTS only. The system can also be a fully functioning headend, while performing monitoring tasks.

[0018] One embodiment of the invention includes a MAC (Media Access Controller) chip, a QAM (Quadrature Amplitude Modulation) modulator, a QAM demodulator and a burst receiver chip, a dual core Si-Byte™ processor, a Xilinx™ high density FPGA (Field Programmable Gate Array) and an ACE (Active Computing Element) programming interface. The system includes a plurality of software—hardware interfaces, many of which share core processing resources and in some cases are interchangeable. For example, many mathematical functions can be done via processor execution of compiled C++ code. These same functions can be ported into hardware to accelerate the computations and reduce load on the software processor resources. Some of the functions are:

[0019] “Monitor and Range Process”—The function of listening to downstream UCD messages and upstream ranging responses in order to compute offsets required to “center” the monitoring device at the proper “propagation-time-location” relative to the CMTS and CM from which the communications have come from. The system also has an ability to range CM's that are located downstream from the system, (and an ability to range CM's between the system and CMTS.)

[0020] “Soft-PHY co-processor”—The functions of having a flexible boundary between hardware and software functions such that they are interchangeable and re-configurable for the purpose of data path processing. The system architecture allows the processing time (software loading) to be reduced and improved as the product is manufactured and deployed in the field. This operation may be implemented by calls to functions via PCI-DMA (direct memory access) transactions. Calls to hardware functions are made via DMA to different locations than calls to software DSP functions. In this way, the system can be easily programmed to access functions differently as they become available. This also applies to data crossing the PCI bus to implement a soft data-process, hard MAC data flow system, with upgrade features.

[0021] Dual Processor Architecture—CMTS functions are implemented using one partition and DSP functions using another.

[0022] Dual Function CMTS Monitor—The system is a fully functional CMTS while being able to simultaneously “listen” to another CMTS mastering the system timing. In this way, the monitor can be “slaved” to the master CMTS without any physical (i.e., wired) connection other than the physical plant coaxial cable.

[0023] Time Synchronization of Slave to Master using UCD and SYNC Message monitoring: commonly assigned patent application Ser. Nos. 09/653,155 and 06/235,008 disclose synchronization of multiple CMTS's using a physical wired connection and a software-controlled self-loading register, respectively, and are incorporated by reference herein. This allows for slave CMTS synchronization of the monitoring system using the UCD type 2 1messages and SYNC type messages contained in the DOCSIS data stream.

[0024] Self-Stimulation Mode—The system can provide a canned burst of data (programmable) on an RF upstream channel fully encoded using SCDMA formats. This burst is used to provide calibration (interpolation, offset) data to the CMTS that allows for upstream channel parameters to be determined empirically. This function will be useful in the absence of “known” channel parameters.

[0025] Real Time System—The system operates in real time, however has visibility into soft functions (math, parsing) as well as allowing for data to be processed in any order or at any time. All data is marked with arrival time embedded and can be re-ordered or processed as desired (filtered, re-sent, etc).

[0026] Virtual Machine—The system can be placed anywhere on the cable plant. Currently, the, system is designed to “learn” its location relative to a CMTS and CM's that it is located between. The system can also “learn” its location relative to CM's that are located between itself and the CMTS.

[0027] The system can monitor upstream SCDMA bursts while not being a supervisory provisioning node on the same plant that controls the CM SCDMA bursts. In addition, the system allows for a slave CMTS to synchronize to other master CMTS' that are located very far away.

[0028] The advantage of the invention is in being able to monitor SCDMA upstream and downstream data for the purpose of establishing whether or not the system is conforming to proper SCDMA formats per the DOCSIS 2.x standard. The system is fully programmable and configurable and can be upgraded in functionality to apply to future DOCSIS standard additions.

[0029] FIG. 1 illustrates an example of a cable modem system of the present invention. As shown in FIG. 1, a cable modem termination system (CMTS) 101 functions as a headend at the cable plant. The cable plant can also have a number of slave CMTS's 102a, 102b. The master and slave CMTS's 101, 102a, 102b have RF connections 103 to connect to the coax or fiberoptic cables 105. Downstream of the CMTS 101 are the cable modems (CM's) 104a, 104b . . . 104f. The cable modems 104a-104f communicate with the CMTS 101 in a bidirectional manner, for example, using a DOCSIS protocol. The bidirectional communication may be in any number of formats and modulation schemes, including SCDMA, ATDMA, QAM, QPSK (Quadrature Phase Shift Key), etc. The network monitor 106 is positioned as a third party to the bidirectional traffic on the cable 105, such that neither the CMTS 101 nor the cable modems 104 need to be aware of its presence. Alternatively, the network monitor of the present invention may function as a slave CMTS 107, as shown on FIG. 1. The slave CMTS 107 includes the necessary hardware, contained in a hybrid system to provide the necessary time generation counter (TGC) synchronization and SCDMA system timing synchronization based on only downstream and ethernet traffic. In other words, no physical timing interface (hardwire, bits etc.) would be required at the distant location. The slave CMTS 107 could be remotely located anywhere on a plant to perform CMTS headend functions specific to that location or district, without being known by the Master CMTS (unless desired).

[0030] FIG. 2 shows an example of one embodiment of the network monitor 106 of the present invention. As shown on FIG. 2, the network monitor 106 includes a PCI bridge 201, which is a data interface to the software domain, for example, to a laptop computer that a technician in the field might have, to software programs that may be downloaded into the network monitor 106, to any additional memory that may be used to store and/or record the data, any other peripheral storage and/or display devices, etc.

[0031] PCI bridge 201 also includes a bidirectional interface to a Si-Byte™ processor 218. The Si-Byte™ processor 218 functions as a system CPU, and includes a dual MIPS™-based processor, large shared memory, 3 Ethernet ports, an interface to the PCI, and other miscellaneous interfaces. One processor core is used to perform the CMTS function. The other processor core is used to perform a soft upstream burst demodulator function.

[0032] The PCI bridge 201 also includes a bidirectional interface to a DOCSIS CMTS media access control (MAC) 206 and to a control and processing FPGA (field programmable gate array) 207.

[0033] The CMTS function of the network monitor 106 includes several different system processing functions. This includes DOCSIS management (ranging, registration, etc), packet processing (performing a half bridge and potential routing functions), and overall system management (system health, configuration, etc).

[0034] The network monitor 106 includes Test Point Access 202 to provide a capability for a Test Interface to the network monitor 106. It may also be referred to as a Diagnostic Port Interface, or Monitor Port.

[0035] The soft upstream burst demodulation is used to recover data in the cable upstream and convert the RF data into data that can be used. The processor 218 is assisted by an FPGA 207 and associated hardware to collect and do some processing functions. The processing functions may be split between the two processing elements (the FPGA 207 and the processor card 218), but can be shifted completely to hardware (FPGA or ASIC). The second processor will then perform as a packet processing engine.

[0036] The FPGA 207 includes the control logic used to run the network analyzer 106. It also includes a bidirectional interface to the media access controller (MAC) 206. The media access controller is a standard MAC such as that found in cable modem systems. The FPGA 207 includes core function implementation, such as DSP functions, hardware controller, and soft interface controller, as discussed below.

[0037] The MAC 206 also includes a bidirectional interface to an upstream SDRAM 204 and another bidirectional interface to a downstream SDRAM 205. Each provides a capability of a data storage module, with the ability to store traffic for post process staging interface. The upstream SDRAM 204 is normally used for storage of such information as encryption keys, data used for maintenance operations, data used for formatting operations, etc. The downstream SDRAM 205 is used to store such information as PDU (packet) data, bandwidth allocation map data, overflows from FIFO's, etc.

[0038] The network monitor 106 includes an external synchronization block 203, which can receive a clock signal from an external source, such as a 163.84 MHz clock commonly used in many DOCSIS systems. The external synchronization block 203 may be referred to as a slave time base synchronizer, a time reference calibrator, or a slave time base controller.

[0039] The network analyzer 106 also includes a clock synchronization block 209, which includes phase lock loops, and provides phase coherent clocks by which all the MAC and PHY processing hardware time its operations. It provides a 163.84 MHz clock to a burst demodulator 210, and an 81.92 MHz clock to the FPGA 207. The clock synchronization block 209 may be referred to generically as a time synchronizer, a master clock controller, a master time base reference, or a master time base source.

[0040] The FPGA 207 also includes a bidirectional bus to a waveform SDRAM (ARB SDRAM) 208, and to an arbitrary waveform generator 212. The ARB SDRAM is essentially a memory that functions as waveform storage unit. It may also be referred to as a coefficient storage unit, or a channel parameter storage unit.

[0041] The arbitrary waveform generator 212 can generate a digital waveform based on samples and/or coefficients received from the FPGA 207. To generate such a waveform, the FPGA 207 loads the waveform coefficients/samples from the ARB SDRAM 208, and downloads them to the arbitrary waveform generator 212. The arbitrary waveform generator 212 then outputs the waveform to an RF amplifier 216 (which is a line driver for a cable modem system, and may be referred to more generically as a gain increase block, optical amplifier, or a data launcher), and then out to the cable 105. The waveform generator 212 functions as DSP waveform generator, or a “canned waveform launcher,” such that it is a calibration stimulus block for the system, with the capability to launch a waveform into the cable plant, so that the waveform is received back and channel characteristics and offsets can be determined.

[0042] The network monitor 106 also includes the burst demodulator 210, which is connected to an RF analog front end (AFE) 214.

[0043] The analog front end 214 receives a signal from the cable 105. The analog front end 214 includes digital and analog filters necessary to preprocess the RF signal. After the preprocessing, the analog front end 214 outputs a digital signal to the burst demodulator 210. The burst demodulator 210 has the capability to process any of DOCSIS supported modulation schemes and data formats, including SCDMA, TDMA, ATDMA, CDMA, as well as M-QAM and QPSK data formats. The burst demodulator 210 is connected by a bidirectional bus to the MAC controller 206 and to the FPGA 207. The burst demodulator 210 can output baseband data, as well as the individual in phase and quadrature (I and Q) components to the FPGA 210 for processing.

[0044] The network monitor 106 includes a QAM modulator 211. The QAM modulator 211 is connected to an RF amplifier (line driver) 215, which in turn is connected to the cable 105. The QAM modulator, upon command from the MAC controller 206 and the FPGA 207 can output data onto the cable 105 in the desired data format and modulation scheme. Thus, the QAM modulator 211 takes baseband DOCSIS data and modulates it up to the IF frequency for input into an RF UP converter 278. The RF UP converter 278 converts the IF frequency input to the RF frequency that is output onto the cable 105. The QAM modulator also performs the functions of a QPSK modulator, and may be referred to more generically as an optical modulator, a data modulator, or an encoded modulator.

[0045] The network analyzer 106 also includes a QAM demodulator 213, which is connected to an RF tuner 217. The RF tuner 217 may be referred to as a channel decoder, a channel selector, an optical tuner (for optical channels), or an optical de-multiplexor.

[0046] The QAM demodulator 213 takes a downstream signal from the CMTS 101, and demodulates it so as to triangulate the position of the network monitor 106. Thus, by listening to the bidirectional traffic on the cable 105, the network monitor 106 can compute its own location relative to the other participants in the two-way communications traffic (i.e., the cable modems 104 and the CMTS 101).

[0047] The arbitrary waveform generator 212 creates a “canned” waveform for purposes of calibration. With the use of a canned waveform from the waveform generator 212 the network monitor 106 can run a waveform through a cable plant, and calibrate proper settings for receiving it. Thus, the canned waveform can function as a fixed test signal, which can be used for self-calibration. After the self-calibration, the network monitor 112 is calibrated to receive other bursts from the cable modems and the CMTS 101.

[0048] The network monitor 106 can listen to correction messages from the CMTS 101 and the messages from the cable modems 104. With self-triggering, it can compute its own offset, so that it knows when to listen to within one nanosecond accuracy. It also knows “how” to listen, i.e., which modulation scheme and which data format is used by the participants in the bidirectional communications traffic on the cable 105. Thus, the network monitor can function as a “third party” to the communications, such that neither the cable modem 104 nor the CMTS 101 needs to be aware of its presence.

[0049] The network monitor 106 includes the monitoring functions of a supervisory node of a DOCSIS system, without itself being a supervisory node. The network monitor 106 is able to compute its offset (i.e., to range itself, or determine the distance to both the cable modem 104 and the CMTS 101) by listening to the cable modem 104 and the CMTS 101, and particularly to the offsets (ranging information) transmitted by the CMTS 101. Thus, it is able to determine its own distance to the CMTS 101 and the cable modem 104.

[0050] Further, with reference to FIGS. 3 and 4, the FPGA 207 includes the following functions:

[0051] DEMOD 210: Received RF signal is demodulated and filtered to produce the base band I and Q data sampled at 4× symbol rate.

[0052] A CORRELATOR 304: A correlator is used to detect the presence of a Preamble during initial ranging. It also determines the best symbol sample position for passing the I and Q symbols to the SCDMA Receiver Process 402. The correlator 304 may be implemented in the FPGA 207.

[0053] DESPREADER 302: the despreader 302 de-spreads the received I and Q symbols. This is required when spreader on mode is used. This function is currently implemented in FPGA 207.

[0054] DMA 301, 303: Direct Memory Access (DMA) provides a fast way of passing the data from the FPGA to the SCDMA Receiver Process 402 (implemented in software). The Receiver Process is a software implementation using Si-byte Processor 218.

[0055] FRAME INFO GENERATOR 401: The SCDMA Receiver Process is performed one frame at a time, unless it is a spreader off mode where a complete burst is process at a time. The Frame Info Generator (implemented in software) provides information to the receiver on the frame it is about to process. The information include spreader mode, number of burst in the frame, preamble length, data payload length, start and end of the frame, burst profile number, etc.

[0056] SPREADER OFF PREAMBLE PROCESS (INITIAL RANGING): During initial ranging spreader off mode is used. This function estimates the carrier frequency offset, carrier phase offset, Gain, and sample timing offset.

[0057] SPREADER ON PREAMBLE PROCESS: Similar to spreader off preamble process, this function also estimates the Gain and carrier frequency and phase offsets.

[0058] SPREADER ON PROCESS: Again this function is similar to the above preamble on process, however, the different is that in this case there is no preamble presence.

[0059] DEROTATOR: The estimated carrier frequency and phase offsets are use in this function to derotate the I and Q symbols in the frame.

[0060] DEFRAMER: The deframer reconstructs the ordering of data to the original form as prior to framing in the transmitter. Locations of coded and uncoded symbols are recorded for Viterbi decoder to be used later.

[0061] VITERBI DECODER: This function performs the Trellis Coded Modulation (TCM) decoding. Based on the information given by the deframer on the locations of coded and uncoded symbols, output data is reconstructed to reflect the original form.

[0062] DESCRAMBLER: The decoded data are then descrambled by this function.

[0063] RS DECODER: The descrambled data are then passed to a Reed Solomon Decoder to possibly correct some received data error.

[0064] STIMULATOR 310: The basic premise of the stimulator block is to provide a means for creating, formatting and transmitting modulated data on a DOCSIS 2.0 modulated system or plant. The stimulator block is implemented in the Processing and Control FPGA (Field Programmable Gate Array) 207 within the DOCSIS 2.0 CMTS and Monitoring System. The interfaces include:

[0065] 1. Internal DMA Block—This block allows software to transfer blocks of data across the PCI interface into the Stimulator memory, which consists of 64MB of SDRAM. The transferred data is formatted in 14 bit raw sample values, which are fetched out of memory and forwarded to an external DAC device.

[0066] 2. Control Interface—This interface consists of three control signals (Preload, Go, and Block Type) for the Stimulator Block, which are controlled by the internal Map Window Generator Block, and is used for timing and initiating data transfers from the stimulator memory to an external DAC device. The Preload is used to begin fetching data from memory (as declared by the Block Type signaling) and store into a FIFO to queue up for forwarding to the DAC on a precisely synchronized and controlled boundary. The Go is used to begin the data transfer out of the FIFO and forward to the 14 bit interface on the external DAC.

[0067] 3. DAC Interface—This interface consists of the 14 bit data and clock interface to the DAC. The function of this interface relies on a Digital Signal Processing (DSP) algorithm in software which is capable of creating and processing data packets into a raw sample format which is utilized by the external DAC for RF modulating and transmitting the data onto a DOCSIS 2.0 system or plant.

[0068] This functionality is utilized for two purposes in the DOCSIS 2.0 CMTS and Monitoring System:

[0069] 1. It allows pre-formatted data to be stored in Stimulator Memory and utilized within a calibration and diagnostic process for self checking functionality.

[0070] 2. It allows the system the flexibility to receive and process incoming data and then utilize the software DSP algorithm to format a data response and DMA the data block into the Stimulator Memory for transmission onto the plant through the external DAC interface.

[0071] The network monitor 106 is able to monitor the bidirectional traffic on the cable 105, so as to determine which standard is being used for communication, and whether the bidirectional communication is in compliance with the DOCSIS standard, particularly DOCSIS 2.0. It is able to listen to the bidirectional traffic without the normal ranging/registering procedures required for conventional CM/CMTS bidirectional communication. The network monitor 106 is able to listen to any cable modem without participation of the CMTS 101, and without the knowledge of the CMTS 101.

[0072] It is able to do so without precalibration. The network monitor 106 is able to listen to the bidirectional traffic on the cable 105, in particular, to the registering/ranging information being exchanged between the CMTS 101 and the cable modem 104.

[0073] It is also able to itself function as a CMTS, which is particularly useful in the field. Thus, with the network monitor 106 of the present invention, a technician can set up a “portable” headend in the field, which is particularly useful for testing and diagnostic purposes. The network monitor 106 can also synchronize itself to a CMTS that is any arbitrary distance away, for example, to another network monitor 106 that is in the field, or to a conventional CMTS 101. It is auto-synchronizing, i.e., it does not need to be told what the clock information is. Rather, it is able to auto-lock itself to the clock used by the cable modem, by listening to the registering communications between the cable modem 104 and the CMTS 101. The network monitor 106 can make the same correction as told by the CMTS 101 to the cable modem 104 during the ranging process, and can add its own additional offset, as required.

[0074] The network monitor 106 can record the data from the network, and store it for later use. It can analyze the data to make sure that it can perform diagnostics on the data to confirm whether or not the bidirectional traffic conforms to a particular standard (e.g., DOCSIS 2.0). It can display the recorded data on a CRT, or store it to a file. The type of data displayed or stored can include type of messages being exchanged, error types, noise relative to location, etc. The network monitor 106 can also display such data by subscriber ID. It can verify data destined for the CMTS 101. The network monitor 106 can listen to and record traffic in both directions (upstream and downstream) without being registered on the network.

[0075] The network monitor code includes code to configure the RF tuner and the QAM demodulator 213 to tune and acquire downstream lock of the QAM signal. Once QAM lock is obtained, the downstream QAM core is initialized to initiate the flow of data packets to the downstream monitor buffer descriptor (BD) ring. A polling loop can check the BD ring to determine if any packets have arrived. Once it is determined that a packet has arrived, it is pulled from the ring and queued for delivery to the packet processing thread “TriageThread”. The “TriageThread” checks to see if the packet is a MAC management message and if so, what type it is.

[0076] If the message is a MAC management message and its type is UCD, two further checks are performed: one to determine if the upstream channel in the UCD matches the channel of interest (set by user input) and the other to determine if the change count of the UCD has changed. If the UCD change count is different and the channel matches, the software programs upstream parameters and programs the FPGA 207 to prepare for SCDMA burst capture.

[0077] If the message is a MAC management message, its type is MAP and the channel in the message matches the upstream channel of interest, additional processing to setup the mapping/scheduling software to anticipate SCDMA transmissions at the proper times is performed.

[0078] A TDMA scheduling routine can be modified to create a frame-aware SCDMA scheduler. SCDMA frame boundaries and switching between the types of SCDMA traffic, spreader on and spreader off, add complexity to the scheduler that do not exist in TDMA systems. The FPGA 207 provides snapshot registers of the three relevant SCDMA system counters, ticks, minislots and frames. Each time a grant is to be allocated, the scheduler calculates the next frame boundary from the three counters and the current minislot to be mapped. Subsequent minislots, if any, are mapped to NULL, and the grant is mapped at the frame boundary. All time is mapped and every non-NULL grant begins on a frame boundary, successfully mitigating the SCDMA requirements while maintaining compliance.

[0079] The “syneCounters” function initializes network monitor 106 SCDMA frame registers and synchronizes them with the 10.24 Mhz CMTS timestamp counter. The frame registers “FrameSizeReg”, “MinislotsPerFrameReg”, and “MinislotSizeReg” are initialized using configuration parameters 1) the number of spreading intervals per frame (Ks), 2) the symbol modulation rate (BaudRate, where 0=5.12 Mhz, 1=2.56 Mhz, 2=1.28 Mhz), 3) the codes per minislot (Cms), and 4) the number of active codes (P). The registers are initialized as:

[0080] FrameSizeReg=2 * 128 * Ks * (2**BaudRate)

[0081] MinislotsPerFrameReg=P/Cms

[0082] MinislotSizeReg=2 * Cms * Ks * (2**BaudRate)

[0083] Synchronization begins with a reading of the CMTS timestamp counter (tgcCurr), immediately followed by initialization of snapshot frame registers “FrameSnapReg”, “MinislotSnapReg”, and “TGCSnapReg” as:

[0084] FrameSnapReg=0×FE;

[0085] MinislotSnapReg=(P * (tgccurr−(tgcCurr Modulo FrameSizeReg)))/(128 *MinislotSizeReg)+(5 * MinislotsPerFrameReg);

[0086] TGCSnapReg=tgcCurr−(tgcCurr Modulo FrameSizeReg)+(5 * FrameSizeReg);

[0087] The network monitor 106 TGC snapshot control register is initialized to accept an external synchronization pulse from the CMTS, and the CMTS TGC control register is configured to trigger an external pulse at CMTS time (TGCSnapReg−2), where 2 is the transmission time between the CMTS and Network monitor 106 hardware. When the CMTS timestamp counter reaches (TGCSnapReg−2), the CMTS triggers an external pulse, causing Network monitor 106 to initialize its FrameCounter, MinislotCounter, and TGCCounter registers with the values in the snapshot registers. Note that the initial frame count has no significance at synchronization time, and that synchronization will occur approximately 5 frames beyond the initial timestamp reading.

[0088] It will be appreciated that the various receivers and transmitters that are shown as separate blocks in the block diagram of FIG. 2 can be combined into a single chip. For example, the burst receiver 210 and the QAM demodulator 213 can be combined into a single receiver. Similarly, the analog front end functions may be integrated into the receiver. The Si-Byte processor 218 and the FPGA 207 can also be combined into a single processor, or CPU. The waveform generator 212 can also be integrated into the CPU.

[0089] It will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined in the appended claims. Thus, the breadth and scope of the present invention should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents.

Claims

1. A network monitor comprising: means for monitoring downstream traffic from a cable modem termination system (CMTS) to a cable modem (CM); means for monitoring upstream traffic from the CM to the CMTS; and means for identifying a data format used by the CMTS and the CM for bi-directional communication.

2. The network monitor of claim 1, wherein the means for monitoring includes a burst demodulator.

3. The network monitor of claim 1, further including means for calculating offsets from the CMTS and the CM.

4. The network monitor of claim 1, wherein the means for monitoring downstream traffic includes a QAM demodulator.

5. The network monitor of claim 1, further including: means for receiving a calibration waveform; and means for calculating offsets based on the calibration waveform received by the means for receiving the calibration waveform.

6. The network monitor of claim 3, further including means for calculating an additional offset after calculating offsets from the CMTS and the CM.

7. The network monitor of claim 1, further including means for monitoring registration information being exchanged between the CMTS and the CM.

8. The network monitor of claim 1, further including means for monitoring offset information provided by the CMTS to the CM.

9. The network monitor of claim 1, further including means for storing the upstream and downstream traffic.

10. The network monitor of claim 1, further including means for displaying information about the upstream and downstream traffic.

11. The network monitor of claim 1, further including means for verifying whether the upstream and downstream traffic conforms to the DOCSIS standard.

12. The network monitor of claim 1, further including a media access controller connected to the means for monitoring downstream traffic, the means for monitoring upstream traffic and the means for identifying a data format.

13. The network monitor of claim 1, wherein the data format is M-QAM.

14. The network monitor of claim 1, wherein the data format is QPSK.

15. The network monitor of claim 1, wherein the upstream and downstream traffic is modulated in accordance with an SCDMA modulation scheme.

16. The network monitor of claim 1, wherein the upstream and downstream traffic is modulated in accordance with an ATDMA modulation scheme.

17. The network monitor of claim 1, wherein the upstream and downstream traffic is modulated in accordance with a TDMA modulation scheme.

18. The network monitor of claim 1, wherein the upstream and downstream traffic is modulated in accordance with an FDMA modulation scheme.

19. The network monitor of claim 1, wherein the network monitor functions as a supervisory node without registering with the CMTS.

20. The network monitor of claim 1, wherein the network monitor monitors the upstream and downstream traffic without registering with the CMTS.

21. A network analyzer comprising: means for monitoring downstream traffic from a headend to a modem; means for monitoring upstream traffic from the modem to the headend; and means for identifying a data format used by the headend and the modem for bi-directional communication.

22. The network analyzer of claim 21, wherein the means for monitoring the upstream traffic includes a burst demodulator.

23. The network analyzer of claim 21, further including means for calculating offsets from the headend and the modem.

24. The network analyzer of claim 21, wherein the means for monitoring downstream traffic includes a QAM demodulator.

25. The network analyzer of claim 21, further including: means for receiving a calibration waveform; and means for calculating offsets based on the calibration waveform received by the means for receiving the calibration waveform.

26. The network analyzer of claim 25, further including means for calculating an additional offset after calculating offsets from the headend and the modem.

27. The network analyzer of claim 21, further including means for monitoring registration information being exchanged between the headend and the modem.

28. The network analyzer of claim 21, further including means for monitoring offset information provided by the headend to the modem.

29. The network analyzer of claim 21, further including means for storing the upstream and downstream traffic.

30. The network analyzer of claim 21, further including means for displaying information about the upstream and downstream traffic.

31. The network analyzer of claim 21, further including means for verifying whether the upstream and downstream traffic conforms to the DOCSIS standard.

32. The network analyzer of claim 21, further including a media access controller connected to the means for monitoring downstream traffic, the means for monitoring upstream traffic and the means for identifying a data format.

33. The network analyzer of claim 21, wherein the data format is M-QAM.

34. The network analyzer of claim 21, wherein the data format is QPSK.

35. The network analyzer of claim 21, wherein the upstream and downstream traffic is modulated in accordance with an SCDMA modulation scheme.

36. The network analyzer of claim 21, wherein the upstream and downstream traffic is modulated in accordance with an ATDMA modulation scheme.

37. The network analyzer of claim 21, wherein the upstream and downstream traffic is modulated in accordance with a TDMA modulation scheme.

38. The network analyzer of claim 21, wherein the upstream and downstream traffic is modulated in accordance with an FDMA modulation scheme.

39. The network analyzer of claim 21, wherein the network analyzer functions as a supervisory node without registering with the headend.

40. The network analyzer of claim 21, wherein the network analyzer monitors the upstream and downstream traffic without registering with the headend.

41. A network monitor comprising: a controller; a media access controller (MAC) connected to the controller; a burst demodulator that receives upstream communications from a cable modem and outputs digital data to the controller and to the MAC; and a QAM demodulator that receives downstream communications from a headend, wherein the controller ranges the network monitor without registering with the headend.

42. The network monitor of claim 41, further including upstream random access memory connected to the MAC.

43. The network monitor of claim 41, further including downstream random access memory connected to the MAC.

44. The network monitor of claim 41, wherein the controller is a field programmable gate array.

45. The network monitor of claim 41, further including a waveform generator.

46. The network monitor of claim 45, further including a memory storing coefficients for use by the waveform generator to generate a waveform.

47. The network monitor of claim 45, wherein the waveform generator can launch a predetermined waveform such that the controller can calculate its offset from the headend.

48. The network monitor of claim 47, wherein the offset is calculated to within 1 nanosecond.

49. The network monitor of claim 41, wherein the controller monitors registration information being exchanged between the headend and the modem.

50. The network monitor of claim 41, wherein the controller monitors offset information provided by the headend to the modem.

51. The network monitor of claim 41, further including a PCI bridge that connects to an external software source.

52. The network monitor of claim 41, further including a PCI bridge that connects to an external display.

53. The network monitor of claim 52, wherein the controller can display information about the upstream and downstream traffic on the external display through the PCI bridge.

54. The network monitor of claim 41, further including a PCI bridge that connects to an external memory for storing any one of the upstream communications and the downstream communications.

55. The network monitor of claim 41, wherein the controller can verify whether any one of the upstream communications and the downstream communications conforms to the DOCSIS standard.

56. The network monitor of claim 41, wherein the controller can identify a data format of any one of the upstream communications and the downstream communications datastream.

57. The network monitor of claim 41, wherein any one of the upstream communications and the downstream communications datastream is M-QAM.

58. The network monitor of claim 41, wherein any one of the upstream communications and the downstream communications is QPSK.

59. The network monitor of claim 41, wherein any one of the upstream communications and the downstream communications is in accordance with an SCDMA modulation scheme.

60. The network monitor of claim 41, wherein any one of the upstream communications and the downstream communications is in accordance with an ATDMA modulation scheme.

61. The network monitor of claim 41, wherein any one of the upstream communications and the downstream communications is in accordance with a TDMA modulation scheme.

62. The network monitor of claim 41, wherein any one of the upstream communications and the downstream communications is in accordance with an FDMA modulation scheme.

63. The network monitor of claim 41, wherein the network monitor functions as a supervisory node without registering with the headend.

64. The network monitor of claim 41, wherein the network monitor monitors the upstream and downstream communications without registering with the headend.

65. The network monitor of claim 41, wherein the burst demodulator outputs baseband data to the controller.

66. The network monitor of claim 41, wherein the burst demodulator outputs I and Q components of the upstream communication to the controller.

67. The network monitor of claim 41, wherein the network monitor can function as a slave CMTS.

68. A cable traffic verification system comprising: a controller; a media access controller (MAC) connected to the controller; a receiver that receives a data stream and outputs digital data to the controller and to the MAC, wherein the controller performs ranging based on the digital data without registering with a headend.

69. A network monitor comprising: a master control unit; a media access controller (MAC) connected to the master control unit; a burst receiver that receives bursts from a modem and outputs digital data to the master control unit and to the MAC; and a QAM demodulator that receives downstream traffic from a headend and outputs digital downstream traffic to the master control unit, wherein the master control unit performs ranging based on the digital data and the digital downstream traffic.

70. A network analyzer comprising: a central processing unit; a receiver that receives analog upstream traffic and outputs digital upstream traffic to the central processing unit; and a demodulator that receives analog downstream traffic and outputs digital downstream traffic to the central processing unit, wherein the network analyzer listens to the analog upstream traffic and the analog downstream traffic without other network participants being aware of its presence.

71. A slave CMTS comprising: a processor; a media access controller (MAC) connected to the processor; a receiver that receives analog upstream traffic and outputs digital upstream traffic to the processor and to the MAC; a demodulator that receives analog downstream traffic and outputs digital downstream traffic to the processor; and a transmitter of modulated data to a network.

72. A network analyzer comprising: a central processing unit; a receiver that receives analog upstream traffic and outputs digital upstream traffic to the central processing unit; and a demodulator that receives analog downstream traffic and outputs digital downstream traffic to the central processing unit, wherein the central processing unit identifies registration information transmitted between a headend and a modem without registering with the headend.

73. A network analyzer comprising: a central processing unit; a media access controller (MAC) connected to the central processing unit; a receiver that receives analog upstream traffic and outputs digital upstream traffic to the central processing unit and to the MAC; and a demodulator that receives analog downstream traffic and outputs digital downstream traffic to the central processing unit, wherein the network analyzer can auto-range itself by launching a test transmission into the network.

74. A network analyzer comprising: a central processing unit; a media access controller (MAC) connected to the central processing unit; a receiver that receives analog upstream traffic and outputs digital upstream traffic to the central processing unit and to the MAC; and a demodulator that receives analog downstream traffic and outputs digital downstream traffic to the central processing unit, wherein the network analyzer auto-locks to a clock used by a modem by monitoring the upstream traffic.

75. A network analyzer comprising: a central processing unit; a media access controller (MAC) connected to the central processing unit; a receiver that receives analog upstream traffic and outputs digital upstream traffic to the central processing unit and to the MAC; and a demodulator that receives analog downstream traffic and outputs digital downstream traffic to the central processing unit, wherein the network analyzer auto-synchronizes to the analog upstream traffic.

76. A bi-directional communications traffic monitor comprising: a system controller; a burst receiver that receives analog upstream traffic and outputs digital upstream traffic to the system controller and to a MAC; and a demodulator that receives analog downstream traffic and outputs digital downstream traffic to the system controller, wherein the network monitor listens to the analog upstream traffic and the analog downstream traffic without other network participants being aware of its presence.

77. A method of monitoring network traffic comprising the steps of: monitoring downstream traffic from a cable modem termination system (CMTS) to a cable modem (CM); monitoring upstream traffic from the CM to the CMTS; and identifying a data format used by the CMTS and the CM for bi-directional communication.

78. A method of monitoring network traffic comprising the steps of: receiving bi-directional traffic; processing the bi-directional traffic to convert it to a digital signal; and ranging based on the digital signal without registering with a headend.

79. A method of monitoring network traffic comprising the steps of: receiving bi-directional traffic; processing the bi-directional traffic to convert it to digital traffic; and identifying a data format used by network participants for the digital traffic.

80. A method of monitoring cable modem network traffic comprising the steps of: monitoring registering information exchanged between a modem and a headend; identifying subscriber ID and ranging information transmitted by the headend; and calculating actual offsets to the headend and the modem based on the ranging information.

81. A method of monitoring network traffic comprising the steps of: receiving bi-directional traffic; processing the bi-directional traffic to convert it to digital form; and verifying conformity to a predetermined standard by network participants for the digital traffic.