EP1635493A1 - Synchronisation des composants distribués dans un réseau câble modem - Google Patents

Synchronisation des composants distribués dans un réseau câble modem Download PDF

Info

Publication number
EP1635493A1
EP1635493A1 EP05011363A EP05011363A EP1635493A1 EP 1635493 A1 EP1635493 A1 EP 1635493A1 EP 05011363 A EP05011363 A EP 05011363A EP 05011363 A EP05011363 A EP 05011363A EP 1635493 A1 EP1635493 A1 EP 1635493A1
Authority
EP
European Patent Office
Prior art keywords
hub
downstream transmitter
clock
upstream receiver
head end
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Withdrawn
Application number
EP05011363A
Other languages
German (de)
English (en)
Inventor
Bruce J. Currivan
Alexander G. Macinnis
Thomas J. Kolze
Richard S. Prodan
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Broadcom Corp
Original Assignee
Broadcom Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US11/031,568 external-priority patent/US7630357B2/en
Priority claimed from US11/061,147 external-priority patent/US7697546B2/en
Application filed by Broadcom Corp filed Critical Broadcom Corp
Publication of EP1635493A1 publication Critical patent/EP1635493A1/fr
Withdrawn legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/41—Structure of client; Structure of client peripherals
    • H04N21/426—Internal components of the client ; Characteristics thereof
    • H04N21/42607—Internal components of the client ; Characteristics thereof for processing the incoming bitstream
    • H04N21/4263—Internal components of the client ; Characteristics thereof for processing the incoming bitstream involving specific tuning arrangements, e.g. two tuners
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J3/00—Time-division multiplex systems
    • H04J3/02—Details
    • H04J3/06—Synchronising arrangements
    • H04J3/062—Synchronisation of signals having the same nominal but fluctuating bit rates, e.g. using buffers
    • H04J3/0632—Synchronisation of packets and cells, e.g. transmission of voice via a packet network, circuit emulation service [CES]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2801—Broadband local area networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/41—Structure of client; Structure of client peripherals
    • H04N21/426—Internal components of the client ; Characteristics thereof
    • H04N21/42676—Internal components of the client ; Characteristics thereof for modulating an analogue carrier signal to encode digital information or demodulating it to decode digital information, e.g. ADSL or cable modem
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J3/00—Time-division multiplex systems
    • H04J3/02—Details
    • H04J3/06—Synchronising arrangements
    • H04J3/0635—Clock or time synchronisation in a network
    • H04J3/0682—Clock or time synchronisation in a network by delay compensation, e.g. by compensation of propagation delay or variations thereof, by ranging
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L7/00—Arrangements for synchronising receiver with transmitter
    • H04L7/04—Speed or phase control by synchronisation signals
    • H04L7/041—Speed or phase control by synchronisation signals using special codes as synchronising signal
    • H04L2007/045—Fill bit or bits, idle words

Definitions

  • the invention relates generally to communication systems and, more particularly, it relates to cable modem communication systems.
  • CMTSs Cable Modem Termination Systems
  • CMs serviced Cable Modems
  • a cable modem network plant i.e., hybrid fiber-coaxial media that communicatively couples these devices.
  • the CMTS services data communications for the CMs via downstream transmissions from the CMTS to the CMs and upstream transmissions from the CMs to the CMTS.
  • the Data Over Cable Service Interface Specification (DOCSIS) typically governs the transmission and receipt of signals of the cable modem communication system.
  • DOCSIS supports Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), and Code Division Multiple Access (CDMA) operations. Ranging and registering operations are performed to manage the timing of communications between the CMTS and the CMs.
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • CDMA Code Division Multiple Access
  • CM communications systems continues to evolve.
  • One evolution of the structure of cable modem communication systems includes distributing the CMTS across differing devices that intercouple via a packet data network. Operation of the CM communication system requires synchronization of the distributed CMTS components. Because the packet data network introduces significant jitter, it would likely be impractical to use the packet data network to meet the accuracy required for synchronization of CMTS components without adding excessive latency. Thus, a need exists for synchronizing the distributed CMTS components while meeting all system requirements.
  • a method for synchronizing operation of distributed cable modem termination system components comprising:
  • the ranging operations are supported by a plurality of cable modems for which the headend, the downstream transmitter hub, and the upstream receiver hub together provide data service.
  • the ranging operations are supported by a dedicated clock synchronization cable modem.
  • establishing packet flow synchronization between the head end and the downstream transmitter hub comprises enabling a control loop associated with the downstream transmitter hub that is responsive to timing information of the head end received across the packet data network.
  • establishing packet flow synchronization between a head end and a downstream transmitter hub comprises:
  • the rate intended to prevent overflow of the buffer of the downstream transmitter hub is based upon both a clock specification of the clock of the head end and a clock specification of the clock of the downstream transmitter hub.
  • synchronizing the clock of the upstream receiver hub with the clock of the downstream transmitter hub comprises the upstream receiver hub adjusting its clock to correspond to the clock of the downstream transmitter hub.
  • synchronizing the clock of the upstream receiver hub with the clock of the downstream transmitter hub comprises the downstream transmitter hub adjusting its clock to correspond to the clock of the upstream receiver hub upon receipt of adjustment information from the upstream receiver hub.
  • a method for synchronizing operation of distributed cable modem termination system components comprising:
  • the ranging operations are supported by a plurality of cable modems for which the headend, the downstream transmitter hub, and the upstream receiver hub together provide data service.
  • the ranging operations are supported by a dedicated clock synchronization cable modem.
  • regulating packet data flow from a head end to a downstream transmitter hub in an attempt to avoid overflow and underflow of a buffer of the downstream transmitter hub includes enabling a control loop associated with the downstream transmitter hub that is responsive to timing information of the head end received across the packet data network.
  • the method further comprises preventing underflow of the buffer of the downstream transmitter hub by the downstream transmitter forming and transmitting null data frames.
  • synchronizing the clock of the upstream receiver hub with the clock of the downstream transmitter hub comprises the upstream receiver hub adjusting its clock to correspond to the clock of the downstream transmitter hub.
  • synchronizing the clock of the upstream receiver hub with the clock of the downstream transmitter hub comprises the downstream transmitter hub adjusting its clock to correspond to the clock of the upstream receiver hub upon receipt of adjustment information from the upstream receiver hub.
  • a distributed cable modem termination system comprising:
  • the system further comprises a plurality of cable modems that are operable to support the ranging operations and which receive data service from the headend, the downstream transmitter hub, and the upstream receiver hub.
  • system further comprises a dedicated clock synchronization cable modem operable to support the ranging operations.
  • system further comprises a control loop associated with the downstream transmitter hub that is responsive to timing information of the head end received across the packet data network to establish the packet flow synchronization there between.
  • the rate to prevent overflow of the buffer of the downstream transmitter hub is based upon both a clock specification of the clock of the head end and a clock specification of the clock of the downstream transmitter hub.
  • the upstream receiver hub is operable to synchronize its clock with the clock of the downstream transmitter hub by adjusting its clock to correspond to the clock of the downstream transmitter hub.
  • the downstream transmitter hub is operable to synchronize its clock with the clock of the upstream receiver hub by adjusting its clock to correspond to the clock of the upstream receiver hub upon receipt of adjustment information from the upstream receiver hub.
  • a distributed cable modem termination system comprising:
  • the system further comprises a plurality of cable modems that are operable to support the ranging operations and which receive data service from the headend, the downstream transmitter hub, and the upstream receiver hub.
  • system further comprises a dedicated clock synchronization cable modem operable to support the ranging operations.
  • system further comprises a control loop associated with the downstream transmitter hub responsive to timing information of the head end received across the packet data network and operable to regulate downstream data flow from the headend to the downstream transmitter hub.
  • the head end transmits data to the downstream transmitter hub at a rate that is based upon both a clock specification of the clock of the head end and a clock specification of the clock of the downstream transmitter hub.
  • the upstream receiver hub is operable to synchronize its clock with the clock of the downstream transmitter hub by adjusting its clock to correspond to the clock of the downstream transmitter hub.
  • the downstream transmitter hub is operable to synchronize its clock with the clock of the upstream receiver hub by adjusting its clock to correspond to the clock of the upstream receiver hub upon receipt of adjustment information from the upstream receiver hub.
  • a method for synchronizing operation of distributed cable modem termination system components including a head end, a downstream transmitter hub, and an upstream receiver hub comprising:
  • establishing packet flow synchronization between the head end and the downstream transmitter hub comprises enabling a control loop associated with the downstream transmitter hub that is responsive to timing information of the head end received across the packet data network.
  • establishing packet flow synchronization between a head end and a downstream transmitter hub comprises:
  • the rate intended to prevent overflow of the buffer of the downstream transmitter hub is based upon both a clock specification of a clock of the head end and a clock specification of the clock of the downstream transmitter hub.
  • FIG. 1 is a system diagram illustrating a cable modem communication system having distributed Cable Modem Termination System (CMTS) head end components.
  • the distributed CMTS includes a head end 102 and distributed hubs 108.
  • Each of the distributed hubs 108 services a respective Data Over Cable System Interface Specification (DOCSIS) Physical Layer (PHY) domain 104 and 106.
  • DOCSIS PHY domain 104 and 106 services a plurality of cable modems (CMs) 110.
  • the head end 102 couples to the hubs 108 via a media 114.
  • the head end 102 transfers data to, and receives data from the cable modems 100 via the hubs 108 and the media 114.
  • DOCSIS Data Over Cable System Interface Specification
  • PHY Physical Layer
  • CMs cable modems
  • Synchronization of transmissions within the PHY domains 104 and 106 is a requirement.
  • burst transmissions (both upstream and downstream) within each DOCSIS PHY domain 104 and 106 must be sent at accurate times (100 ns level) to avoid collision.
  • timing is even more critical because synchronization to the symbol level is required. Thus, a more stringent synchronization on the order of 1 ns is required.
  • the head end 102 could maintain a reference clock, e.g., operating at 10.24 MHz.
  • the hubs 108 could then lock their clocks to the reference clock of the head end 102 via link 114.
  • Each CM 110 could then lock its clock to the downstream symbol clock, which is synchronized to the 10.24 MHz reference clock. Ranging operations could then be employed to adjust the offsets of the clocks of the CMs 110 to within 1 ns, typically. Once ranged, a CM 110 should not drift off in time, due to the closed-loop synchronous aspects of the system. However, to allow for changes in the cable modem network plant propagation delay as temperature, wind and other factors vary, ranging is repeated every 30 seconds, or more often, for each CM 110. With this synchronization enacted, the entire DOCSIS PHY 104 and/or 106 are synchronous.
  • link 114 does not support synchronization to the reference clock of the head end 102, these operations cannot be performed.
  • the operations of the present invention overcome this problem.
  • packet data flow downstream from the headend to each hub is managed to in an attempt to avoid transmit buffer overflow or underflow.
  • the clocks of various components of the hubs 108 are synchronized using ranging operations so that collisions within DOCSIS PHY domains 104 and 106 themselves are avoided.
  • symbol timing drift over time may be employed to synchronize clocks of the hubs 108.
  • FIG. 2 is a system diagram illustrating a cable modem communication system constructed according to the present invention having distributed CMTS components inter-coupled by a packet data network 202.
  • a distributed CMTS includes a head end 102 and a hub 108 that includes a downstream transmitter hub 214 and an upstream receiver hub 216.
  • the head end 102, the downstream transmitter hub 214, and the upstream receiver hub 216 couple to one another via the packet data network 202.
  • the packet data network 202 may be an Ethernet network or another type of packet data network.
  • the downstream transmitter hub 214 and the upstream receiver hub 216 of the hub 108 may reside in differing facilities. However, in other embodiment the downstream transmitter hub 214 and the upstream receiver hub 216 may be located in a single facility.
  • the downstream transmitter hub 214 and the upstream receiver hub 216 couple to cable modem network plant 210.
  • CMs 110 also couple to cable modem network plant 210.
  • the cable modem network plant 210 may be a hybrid fiber coaxial cable modem network 210 or another type of cable modem network plant that's generally known.
  • the distributed CMTS services data communications between data network 112 and CMs 110 via the cable modem network plant 210.
  • the distributed CMTS operates according to the DOCSIS specification, in some embodiments.
  • the DOCSIS MAC uses TDMA, FDMA, and/or S-CDMA to service data communications with the CMs 110 across the cable modem network plant 210.
  • the downstream transmitter hub 214 includes a clock (timing base) 206.
  • the upstream receiver hub 216 includes clock (timing base) 208.
  • the clocks (timing bases) 206, and 208 of the downstream transmitter hub 214 and the upstream receiver hub 216, respectively, should be sufficiently synchronized to satisfy the timing requirements of the DOCSIS specification.
  • the clocks 206 and 208 of the distributed CMTS components are sufficiently synchronized so that the timing requirements of the DOCSIS standards are met.
  • the terms "clocks” and “timing bases” are used interchangeably herein when referring to mechanisms within the downstream transmitter hub 214 and the upstream receiver hub 216 for keeping a system time or other time reference.
  • the packet data network 202 has a limited ability to distribute accurate timing information due to its inherent jitter.
  • the head end 102 may include a clock (timing base) 204.
  • One possibility for maintaining system time in the distributed CMTS structure of FIG. 2 is to transfer timing information from the head end 102 to the downstream transmitter hub 214 and the upstream receiver hub 216 over the packet data network 202 using time stamps.
  • the downstream transmitter hub 214 and the upstream receiver hub 216 would smooth the jitter caused by the packet data network 202 and recover the timing base clock from the timestamps, typically employing a filter to smooth the time stamps.
  • an analysis may assume the following typical parameters:
  • N 1 x 10 8 timestamps may have to be averaged to achieve smoothing of 1 x 10 4 .
  • This would require a smoothing time constant of 1 x 10 8 sec/100 1 x 10 6 sec, or 11.6 days, which is impractical.
  • the packet data network 202 In order to use the packet data network 202 to distribute timing information, the packet data network would have to have a jitter limit of approximately 17 us, which is not currently feasible.
  • packet data flow from the head end 102 to the downstream transmitter hub 214 is substantially synchronized in an attempt to avoid overflow and underflow of a transmit buffer of the downstream transmitter hub 214. These operations will be described with reference to FIG. 6. Alternately, packet data flow from the head end 102 to the downstream transmitter hub 214 may be substantially synchronized using a control loop within the downstream transmitter hub 214 stimulated by time stamps transmitted from the head end 102. These operations will be described further with reference to FIG. 5.
  • the clocks 206 and 208 of the downstream transmitter hub 214 and the upstream receiver hub 216 are substantially synchronized.
  • synchronization is performed using ranging operations supported by at least one cable modem communicatively coupled to both the upstream receiver hub and the downstream transmitter hub via cable modem network plant. These operations are described further with reference to FIGs. 3 thru 4.
  • Another technique for synchronizing the clock 208 of the upstream receiver hub 216 to the clock 206 of the downstream transmitter hub includes detecting clock drift based upon changes in alignment of symbols received by the upstream receiver hub 216 when supporting S-CDMA operations. This technique will be described further with reference to FIG. 7.
  • FIG. 3 is a flow chart illustrating operation according to an embodiment of the present invention. Operation commences in initializing the head end 102, the downstream transmitter hub 214, and the upstream receiver hub 216 for operation (step 302). With this step complete, operation continues in establishing packet flow synchronization between the head end 102 and the downstream transmitter hub 214 (step 304). Techniques for performing packet flow synchronization are described further with reference to FIGs. 5 and 6. These operations may further be described herein as regulating packet data flow from the head end 102 to the downstream transmitter hub 214.
  • synchronizing the clock 208 of the upstream receiver hub 216 with the clock 206 of the downstream transmitter hub 206 is performed using ranging operations supported by at least one CM 110 coupled to both the upstream receiver hub 216 and to the downstream transmitter hub 214 via the cable modem network plant 210.
  • the ranging operations are supported by a plurality of CMs 110 for which the head end 102, the downstream transmitter hub 214, and the upstream receiver hub 216 together provide data service. Normally, ranging is done every 15 seconds or so for each CM 110, so tens to hundreds of time-of-arrival measurements are made each second. With another embodiment, the ranging operations are supported by a dedicated clock synchronization CM.
  • the dedicated clock synchronization CM may be ranged at a high rate, perhaps 10 to 100 times per second.
  • the ranging operations are employed to synchronize the clocks 206 and 208 of the downstream transmitter hub 214 and the upstream receiver hub 216, respectively.
  • data bursts may be used in addition to ranging bursts to glean additional information; if data bursts arrive early or late at the receiver hub, that can help define a trend, which implies a frequency offset in the reference clocks, which can then be trimmed out.
  • step 308 Operation of FIG. 3 continues in servicing the CMs, according to one or more aspects of the DOCSIS specification (step 308).
  • the operations of step 308 continue until it is determined that adjustment of the clock 206 of the downstream transmitter hub 214 and/or of the clock 208 of the upstream receiver hub is required (step 310).
  • step 310 When adjustment of the clocks 206 and 208 of the downstream transmitter hub 214 and of the upstream receiver hub 216, respectively (as determined at step 310) is/are required, operation returns to step 306. Otherwise, operation proceeds to step 312 where it is determined whether adjustment of the packet flow synchronization of the head end 102 with the downstream transmitter hub 214 is required. If so operation returns from step 312 to step 304. If not, operation proceeds from step 312 to step 308 where service of the CM continues.
  • FIG. 3 may be performed in varying orders that may differ from the order of operations presented in FIG. 3. Synchronization of the clocks 206 and 204 of the downstream transmitter hub 214 and the head end 102, respectively, may occur during the packet flow synchronization of the head end with the downstream transmitter hub 214 and/or during the time period the CMs are serviced. Typically, maintaining synchronization, both packet flow synchronization and clock synchronization, is ongoing and may be performed at any time.
  • FIG. 4 is a flow chart illustrating a first embodiment of the present invention for synchronizing clocks of a downstream transmitter hub and an upstream receiver hub (step 306 of FIG. 3). Operation commences by transmitting ranging bursts from the downstream transmitter hub 214 to a dedicated clock synchronization CM or to one or a plurality of CMs (step 402).
  • the dedicated clock synchronization CM or the one or a plurality of CMs receive the ranging bursts from the downstream transmitter hub 214, process the ranging bursts, and transmit the ranging bursts to the upstream receiver hub 216 (step 404).
  • the upstream receiver hub 216 receives the ranging bursts and analyzes the ranging bursts to estimate the clock frequency difference between its clock 208 and the clock 206 of the downstream transmitter hub 214 (step 406).
  • the clock drift may manifest itself over time such that adjustments of the upstream receiver hub 216 clock 208 or the downstream transmitter hub 214 clock 206 may be performed at a regular interval, at a non-regular interval, or when the drift exceeds a threshold.
  • the upstream receiver hub 216 adjusts its clock 208 if necessary or alternatively directs the downstream transmitter hub 214 to adjust its clock 206, if necessary (step 408).
  • FIG. 5 is a block diagram illustrating an embodiment of the present invention for establishing packet flow synchronization between a head end and a downstream transmitter hub. Shown in FIG. 5 are the head end 102, the clock 204 of the head end 102, the downstream transmitter hub 214, the clock 206 of the downstream transmitter hub 214, and the packet data network 202. According to the embodiment of step 304 of FIG. 3 a control loop 502 may be employed to establish packet flow synchronization between the head end 102 and the downstream transmitter hub 214. In such embodiment, the control loop 502 is associated with the downstream transmitter hub 206 and is responsive to timing information (time stamps) of the head end 102 clock 204 received across the packet data network 202.
  • timing information time stamps
  • Control loops are generally known and will not be described further herein except as how they relate to the present invention. Because the packet data network 202 is jittery, the control loop 502 may be employed to synchronize the downstream transmitter hub clock 214 with the head end clock 204 over time with adequate precision for some supported operations, e.g., 100 ns required for TDMA operation. The latency introduced by the control loop 502 may be excessive for some applications. Further, the time to lock the control loop 502 may be excessive for some applications. Thus, while the control loop 502 is not sufficient to synchronize the head end clock 204 with the downstream transmitter hub clock 206 in all cases, the control loop 502 is typically sufficient to establish packet flow synchronization between the head end 102 and the downstream transmitter hub 214.
  • the head end 102 uses the control loop 502 to transmit time stamps (TS) with packet data. These time stamps are shown to travel along path 504 from the clock (timing base) 204 to the clock (timing base) 206.
  • the TS indicate instantaneous values of the clock (time base) 204 of the head end 102, the time base being driven by the clock 204.
  • the control loop 502 of the downstream transmitter hub 214 compares the values of TS at the time they are received with the transmitter hub's 214 own clock (timing base) 206.
  • the downstream transmitter hub 214 clock (timing base) 206 may be initialized to the value of the first TS when the first TS is received, and subsequently operated in a closed loop with the clock (timing base) 204 of the head end 102 by comparing subsequent TS with the timing base 206.
  • the result of the comparison between a received TS and the timing base 206 can be filtered and scaled to give desired loop performance characteristics.
  • the filter is a form of low pass filter, either an FIR filter or IIR filter.
  • the filter may resemble an integrator, although the filter response may be somewhat different from a pure integrator (another zero and pole) in order to ensure loop stability.
  • the scaling of the filter result i.e. multiplication by a constant, can control the loop gain.
  • Such loops can be designed for high gain i.e. quick response or low gain i.e. slow response.
  • the loop can be designed for variable gain i.e. variable response, so as to achieve lock with the head end 102 clock 204 frequency quickly using high gain and also to achieve very low variations in transmitter hub 214 clock frequency once locked has been achieved, or partially achieved.
  • FIG. 6 is a flow chart illustrating another embodiment for establishing packet flow synchronization between a head end and a downstream transmitter hub according to the present invention.
  • the operations of FIG. 6 correspond to steps 304 and 308 of FIG. 3.
  • Operation commences with, based upon clock frequency specifications of the head end 102 and of the downstream transmitter hub 214, determining a maximum packet data flow rate that should prevent overflow of a transmit buffer of the downstream transmitter hub 214 (step 602).
  • the operations of step 602 would typically be performed in a design process and be later implemented.
  • Operation continues with the head end 102 transmitting packet data from the head end at a rate that that does not exceed the packet data flow rate (step 604).
  • the downstream transmitter hub 214 receives the packet data, forms the packet data into data frames, and transmits the data frames to the CMs 110 according to the DOCSIS specification, for example. At some time, if the downstream transmitter hub 214 may be transmitting packet data at a greater rate than it is receiving packet data from the head end 102, downstream transmitter hub 214 transmit buffer underflow may occur. Thus, at step 606 the downstream transmitter hub 214 determines whether a downstream transmitter hub 214 transmit buffer underflow has occurred or is about to occur, i.e. if the transmit buffer becomes empty or nearly empty. If a downstream transmitter hub buffer becomes empty, or if it is about to go empty, the downstream transmitter hub transmits one or more null data frames to cure the underflow situation (step 608), i.e.
  • the downstream transmitter hub 214 forms and transmits data frames carrying packet data to serviced CMs without insertion of null frames (step 610).
  • the downstream transmitter hub 214 forms and transmits data frames carrying packet data to serviced CMs with the insertion of null frames (step 610) as appropriate to prevent or cure underflow conditions.
  • the relationship of the data rate demand from the head end 102 to the downstream transmitter hub 214 data rate, and the prevalence of null packets are design variables with multiple solutions.
  • the network delay between the head end 102 and the downstream transmitter hub 2114
  • the head end 102 data rate can be almost equal to the downstream transmitter hub 214 rate, with the required difference being determined by the maximum difference between the clock rates of the head end 102 and the downstream transmitter hub 214.
  • each clock has a worst case tolerance of 5 ppm
  • the total worst case difference is 10 ppm
  • this rate depends on the actual relative frequencies of the head end and hub and is not independent of that relationship.
  • the rate of inserted null data frames is doubled to approximately 0.5 packets/second.
  • the downstream transmitter hub 214 determines when to insert null data frames.
  • the downstream transmitter hub 214 receives data packets from the head end 102, frames it, and transmits it as soon as possible. Whenever the transmitter hub 214 does not have enough data in its input buffer to be able to form a complete data frame, it sends a null data frame.
  • the delay of data traversing the receive buffer trends towards zero. The delay can increase when the network delay changes from a relatively long delay to a relatively short delay. As long as the downstream transmitter hub 214 data rate is greater than the head end 102 data rate, the transmitter hub 214 will normally remove data from the buffer faster than data enters the buffer, and so the buffer fullness tends towards zero over the long term.
  • data can be transmitted from the head end 102 to the downstream transmitter hub 214 with such classifications indicated.
  • the downstream transmitter hub 214 can prioritize the transmission of data according to the classification of data type, e.g. transmitting higher priority data in its buffer before transmitting lower priority data. This minimizes the additional delay imposed by the buffer on the more delay-sensitive data.
  • FIG. 7 is a flow chart illustrating operation according to another embodiment of the present invention for synchronizing CMTS components. Operation commences in initializing the head end 102, the downstream transmitter hub 214, and the upstream receiver hub 216 for operation (step 702). With this step complete, operation continues in establishing packet flow synchronization between the head end 102 and the downstream transmitter hub 214 (step 704). Techniques for performing packet flow synchronization were described with reference to FIGs. 5 and 6. These operations may further be described herein as regulating packet data flow from the head end 102 to the downstream transmitter hub 214.
  • Operation continues with the downstream transmitter hub 214 transmitting downstream Code Division Multiple Access (CDMA) communications to a plurality of serviced cable modems 110 (step 706), e.g., downstream transmissions. Then, operation proceeds with the upstream receiver hub receiving upstream CDMA communications from the plurality of serviced cable modems (step 708). The upstream receiver hub then determines a drift in alignment, if any, of symbols of the upstream communications received from the plurality of serviced cable modems with respect to a timing base of the upstream receiver hub (step 710). The measured drift in alignment is then used to adjust the frequency of the upstream receiver clock (Step 712).
  • CDMA Code Division Multiple Access
  • step 714 it is determined whether adjustment of the packet flow synchronization of the head end 102 with the downstream transmitter hub 214 is required. If so operation returns from step 714 to step 704. If not, operation proceeds from step 714 to step 706 where service of the CM continues.
  • the operations of FIG. 7 may be performed in varying orders that may differ from the order of operations presented in FIG. 7. Typically, maintaining synchronization, both packet flow synchronization and clock synchronization, is ongoing and may be performed at any time.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Computer Hardware Design (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Synchronisation In Digital Transmission Systems (AREA)
EP05011363A 2004-09-14 2005-05-25 Synchronisation des composants distribués dans un réseau câble modem Withdrawn EP1635493A1 (fr)

Applications Claiming Priority (5)

Application Number Priority Date Filing Date Title
US60966304P 2004-09-14 2004-09-14
US62978104P 2004-11-20 2004-11-20
US63553104P 2004-12-11 2004-12-11
US11/031,568 US7630357B2 (en) 2004-09-14 2005-01-06 Synchronization of distributed cable modem network components
US11/061,147 US7697546B2 (en) 2004-09-14 2005-02-18 Synchronization of distributed cable modem network components

Publications (1)

Publication Number Publication Date
EP1635493A1 true EP1635493A1 (fr) 2006-03-15

Family

ID=34936937

Family Applications (1)

Application Number Title Priority Date Filing Date
EP05011363A Withdrawn EP1635493A1 (fr) 2004-09-14 2005-05-25 Synchronisation des composants distribués dans un réseau câble modem

Country Status (3)

Country Link
US (1) US7826491B2 (fr)
EP (1) EP1635493A1 (fr)
CN (1) CN1819510B (fr)

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8473638B2 (en) * 2008-05-02 2013-06-25 James Aweya Method and apparatus for time and frequency transfer in communication networks
CN101431795B (zh) * 2008-11-29 2012-10-10 中兴通讯股份有限公司 时间同步方法和装置
US9887855B2 (en) 2010-01-22 2018-02-06 Alcatel-Lucent Usa, Inc. Virtual converged cable access platforms for HFC cable networks
US8644706B2 (en) 2010-01-22 2014-02-04 Gainspeed, Inc. Distributed cable modem termination system with software reconfigurable MAC and PHY capability
US8935739B1 (en) 2010-01-22 2015-01-13 Gainespeed, Inc. Distributed CCAP cable modem termination system
US8311412B2 (en) * 2010-01-22 2012-11-13 Selim Shlomo Rakib Distributed cable modem termination system
US9584869B2 (en) 2010-01-22 2017-02-28 Gainspeed, Inc. Virtual CCAP cable modem termination system with software reconfigurable MAC
FR2967535B1 (fr) * 2010-11-15 2012-11-02 Alcatel Lucent Procede de synchronisation d'horloges maitre et esclave d'un reseau a commutation de paquets et a liaisons agregees entre noeuds, et dispositifs de synchronisation associes
CN102845024B (zh) * 2011-03-19 2015-06-17 加速有限公司 分布式电缆调制解调器终端系统
CN104836712B (zh) * 2011-03-19 2018-10-09 加速有限公司 分布式电缆调制解调器终端系统
EP2715956B1 (fr) * 2011-05-27 2019-09-11 Cisco Technology, Inc. Synchronisation de précision dans un système de spécification d'interface de service de données par câble (docsis)
US10362081B2 (en) * 2013-08-30 2019-07-23 Citrix Systems, Inc. Methods and systems for quantifying the holistic quality of experience for internet multimedia
US20150078405A1 (en) * 2013-09-18 2015-03-19 Alcatel Lucent Canada Inc. Monitoring clock accuracy in asynchronous traffic environments

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2001019005A1 (fr) * 1999-09-03 2001-03-15 Broadcom Corporation Systeme et procede destine a la synchronisation et a la distribution d'informations de synchronisation telephoniques sur un reseau modem cable
US20010033611A1 (en) * 1998-05-06 2001-10-25 Michael Grimwood Apparatus and method for synchronizing an SCDMA upstream or any other type upstream to an MCNS downstream or any other type downstream with a different clock rate than the upstream
US20020129378A1 (en) * 2001-03-08 2002-09-12 Cloonan Thomas J. Method and apparatus for controlling traffic loading on a cable modem termination system
US20040095963A1 (en) * 2002-11-15 2004-05-20 Rakib Selim Shlomo Process for sharing an upstream among multiple downstreams
US20040163120A1 (en) * 1999-02-12 2004-08-19 Broadcom Corporation Cable modem system with sample and packet synchronization

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6307868B1 (en) * 1995-08-25 2001-10-23 Terayon Communication Systems, Inc. Apparatus and method for SCDMA digital data transmission using orthogonal codes and a head end modem with no tracking loops
US6594305B1 (en) * 1998-06-30 2003-07-15 Cisco Technology, Inc. Media access layer ping protocol for diagnosing cable modem links
US6501809B1 (en) * 1999-03-19 2002-12-31 Conexant Systems, Inc. Producing smoothed clock and data signals from gapped clock and data signals
US6526070B1 (en) * 1999-10-09 2003-02-25 Conexant Systems, Inc. Method and apparatus for upstream burst transmissions synchronization in cable modems
US7639617B2 (en) * 2001-06-27 2009-12-29 Cisco Technology, Inc. Upstream physical interface for modular cable modem termination system
US7262645B2 (en) * 2002-12-19 2007-08-28 Broadcom Corporation System and method for adjusting the phase of a frequency-locked clock
US7697546B2 (en) * 2004-09-14 2010-04-13 Broadcom Corporation Synchronization of distributed cable modem network components

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20010033611A1 (en) * 1998-05-06 2001-10-25 Michael Grimwood Apparatus and method for synchronizing an SCDMA upstream or any other type upstream to an MCNS downstream or any other type downstream with a different clock rate than the upstream
US20040163120A1 (en) * 1999-02-12 2004-08-19 Broadcom Corporation Cable modem system with sample and packet synchronization
WO2001019005A1 (fr) * 1999-09-03 2001-03-15 Broadcom Corporation Systeme et procede destine a la synchronisation et a la distribution d'informations de synchronisation telephoniques sur un reseau modem cable
US20020129378A1 (en) * 2001-03-08 2002-09-12 Cloonan Thomas J. Method and apparatus for controlling traffic loading on a cable modem termination system
US20040095963A1 (en) * 2002-11-15 2004-05-20 Rakib Selim Shlomo Process for sharing an upstream among multiple downstreams

Also Published As

Publication number Publication date
US20060056323A1 (en) 2006-03-16
US7826491B2 (en) 2010-11-02
CN1819510B (zh) 2011-05-18
CN1819510A (zh) 2006-08-16

Similar Documents

Publication Publication Date Title
EP1635493A1 (fr) Synchronisation des composants distribués dans un réseau câble modem
US7630357B2 (en) Synchronization of distributed cable modem network components
JP4326140B2 (ja) ケーブルモデムのメディアアクセス制御装置のタイミング回復方法
US6510150B1 (en) Method of MAC synchronization in TDMA-based wireless networks
US7120123B1 (en) Pre-equalization technique for upstream communication between cable modem and headend
US9301310B2 (en) Robust techniques for upstream communication between subscriber stations and a base station
US7403547B2 (en) Method and system for synchronizing separated edge QAM devices located remotely from a CMTS
US7139283B2 (en) Robust techniques for optimal upstream communication between cable modem subscribers and a headend
US6937568B1 (en) Adaptive rate shaping to prevent overflow
US7697546B2 (en) Synchronization of distributed cable modem network components
US8687754B2 (en) Method and system for transmitting isochronous voice in a wireless network
US20040101077A1 (en) Method for synchronization through accelerated advance of counters
CN1878054B (zh) Ip网络传送基站用时钟参考的装置和方法
US11362751B2 (en) Timing adjustment for distributed network architecture
US20220248069A1 (en) Adaptive video slew rate for video delivery
US20030014763A1 (en) Method and apparatus facilitating synchronization in a broadband communications system
US12126433B2 (en) Timing adjustment for distributed network architecture

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU MC NL PL PT RO SE SI SK TR

AX Request for extension of the european patent

Extension state: AL BA HR LV MK YU

17P Request for examination filed

Effective date: 20060915

AKX Designation fees paid

Designated state(s): DE FR GB

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: BROADCOM CORPORATION

17Q First examination report despatched

Effective date: 20071121

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20141201