|Publication number||US7209442 B1|
|Application number||US 09/894,958|
|Publication date||Apr 24, 2007|
|Filing date||Jun 27, 2001|
|Priority date||Jun 27, 2001|
|Also published as||US7639620, US20070150927|
|Publication number||09894958, 894958, US 7209442 B1, US 7209442B1, US-B1-7209442, US7209442 B1, US7209442B1|
|Inventors||John T. Chapman|
|Original Assignee||Cisco Technology, Inc.|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (24), Non-Patent Citations (3), Referenced by (61), Classifications (15), Legal Events (3)|
|External Links: USPTO, USPTO Assignment, Espacenet|
The present application is related to U.S. patent application Ser. No. 09/490,761, filed on Jan. 24, 2000, now U.S. Pat. No. 7,065,779 and U.S. patent application Ser. No. 09/606,503, filed Jun. 28, 2000, now U.S. Pat. No. 7,113,484 which claims priority under 35 USC 119(e) from U.S. Provisional Patent Application Ser. No. 60/159,085, filed on Oct. 13, 1999. The present application is also related to U.S. Pat. No. 7,139,923, filed concurrently herewith, naming Chapman, et. al., as inventors. Each of these applications is incorporated herein by reference in its entirety for all purposes.
This invention relates to digital computer network technology. More specifically, the present invention relates a new fiber node configuration to be implemented in cable networks.
Broadband access technologies such as cable, fiber optic, and wireless have made rapid progress in recent years. Recently there has been a convergence of voice and data networks which is due in part to US deregulation of the telecommunications industry. In order to stay competitive, companies offering broadband access technologies need to support voice, video, and other high-bandwidth applications over their local access networks. For networks that use a shared access medium to communicate between subscribers and the service provider (e.g., cable networks, wireless networks, etc.), providing reliable high-quality voice/video communication over such networks is not an easy task.
One type of broadband access technology relates to cable modem networks. A cable modem network or “cable plant” employs cable modems, which are an improvement of conventional PC data modems and provide high speed connectivity. Cable modems are therefore instrumental in transforming the cable system into a full service provider of video, voice and data telecommunications services. Digital data on upstream and downstream channels of the cable network is carried over radio frequency (“RF”) carrier signals. Cable modems convert digital data to a modulated RF signal for upstream transmission and convert downstream RF signal to digital form. The conversion is done at a subscriber's facility. At a Cable Modem Termination System (“CMTS”), located at a Head End of the cable network, the conversions are reversed. The CMTS converts downstream digital data to a modulated RF signal, which is carried over the fiber and coaxial lines to the subscriber premises. The cable modem then demodulates the RF signal and feeds the digital data to a computer. On the return path, the digital data is fed to the cable modem (from an associated PC for example), which converts it to a modulated RF signal. Once the CMTS receives the upstream RF signal, it demodulates it and transmits the digital data to an external source.
The Head End 102 is typically connected to one or more hubs 104. Each hub is configured to service one or more fiber nodes 106 in the cable network. Each fiber node is, in turn, configured to service one or more subscriber groups 110. Each subscriber group typically comprises about 500 to 2000 households. A primary function of the fiber nodes 106 is to provide an optical-electronic signal interface between the Head End 102 and the plurality of cable modems residing at the plurality of subscriber groups 110.
Communication between the Head End 102, hub 104, and fiber node 106 a is typically implemented using modulated optical signals which travel over fiber optic cables. More specifically, during the transmission of modulated optical signals, multiple optical frequencies are modulated with data and transmitted over optical fibers such as, for example, optical fiber links 103 and 105 a,b of
As shown in
In the reverse direction, the cable modems transmit electrical signals via the coaxial line 209 to the fiber node 200. The upstream electrical signals from the cable modems are received at the diplexor 210, and passed to the upstream amplifier 206. The upstream electrical signals are then passed from the amplifier 206 to an electric-to-optical signal converter, which converts the upstream electric signals into radio frequency wavelength modulated optical signals which are then transmitted to the Head End via upstream RF fiber 207.
Typically, the use of RF modulated optical signals in the cable network 100 only allows for very narrow opportunities to transmit IP packets. This is because most of the bandwidth of the RF modulated optical signal is used for DOCSIS related signaling between the Head End 102 and plurality of cable modems.
As a result, most conventional cable networks are not equipped to handle increased data flows relating to new and emerging broadband network applications such as video-on-demand, telephony, etc. Accordingly, there exists a continual need to improve access network configurations in order to accommodate new and emerging network applications and technologies.
According to different embodiments of the present invention, at least one packet fiber node may be provided for use in an access network such as, for example, a cable network. The packet fiber node may differ from conventional RF fiber nodes deployed in a cable network in that the packet fiber node is configured to communicate with the Head End of the network using baseband optical signals rather than frequency modulated optical signals.
According to a specific embodiment of the present invention, a packet fiber node may include at least one processor, memory, a first interface for communicating with the Head End of the access network, and a second interface for communicating with at least a portion of network nodes. In embodiments where the access network corresponds to a cable network, the network nodes will correspond to cable modems. The packet fiber node is configured to communicate with the Head End using baseband optical signals, and is further configured to communicate with at least a portion of the network nodes using modulated electrical signals. In accordance with specific embodiments of the present invention, one or more packet fiber nodes may be deployed in a cable network to service a plurality of subscriber groups which are serviced by a single, conventional RF fiber node.
An alternate embodiment of the present invention is directed to a packet fiber node which comprises a diplexor, at least one interface, and a distributed cable modem termination system (DCMTS). The packet fiber node may be configured to communicate with the Head End using baseband optical signals. Additionally, the packet fiber node may be configured to not include components for communicating with the Head End using frequency modulated optical signals. According to a specific embodiment, the packet fiber node may be configured to perform functions relating to DOCSIS MAC scheduling operations and/or functions relating to layer 1 and layer 2 protocols.
Another embodiment of the present invention is directed to a method for performing communication in a cable network. The cable network includes a Head End which communicates with a plurality of different cable modem groups using at least one upstream channel and at least one downstream channel. Spatial reuse of the upstream and/or downstream channel frequencies may be implemented using at least one packet fiber node. According to a specific embodiment, the same channel frequency may be used to communicate with at least 2 different cable modem groups which are serviced by a common RF fiber node.
Additional objects, features and advantages of the various aspects of the present invention will become apparent from the following description of its preferred embodiments, which description should be taken in conjunction with the accompanying drawings.
As the number of cable network subscribers increases, increased bandwidth demands are continuously being placed upon the cable network. In order to accommodate these increased demands in bandwidth, continual efforts are undertaken to increase bandwidth availability in the network, preferably by utilizing existing infrastructure.
According to different embodiments of the present invention, a plurality of different techniques are described for providing increased bandwidth availability to selected nodes in an access network. For example, according to one implementation, a baseband packet-over-fiber communication system may be implemented for providing increased data bandwidth and link budget to network nodes.
As commonly known to one having ordinary skill in the art, baseband optical signals may be transmitted over an optical fiber at a higher frequency than RF modulated optical signals. As a result, the available bandwidth of an optical fiber carrying baseband optical signals may be significantly greater than the available bandwidth of RF modulated optical signals traveling over the same optical fiber. Thus, one solution for increasing available bandwidth in the cable network is to modify conventional RF modulated optical communication equipment to include additional equipment for performing baseband optical communication.
However, this approach is undesirable since a substantial amount of infrastructure supporting RF modulated optical signals has already been installed in most conventional cable networks. Such infrastructure may generally be referred to as legacy RF cable network componentry. Thus, rather than converting all existing cable network infrastructure from RF fiber to baseband fiber, a preferred approach for increasing bandwidth availability in the cable network is to implement a solution which is compatible with the legacy RF cable network components.
Currently, extensive research is being conducted for arriving at a preferred technique for integrating baseband optical communication with broadband (e.g. RF modulated) optical communication in a single fiber node which is also configured to support (1) legacy RF downstreams, (2) legacy RF upsteams (3) packet baseband downstream communication, and (4) packet baseband upstream communication. One such technique is shown in
As shown in
According to a specific embodiment, the functionality of the DCMTS may include all or a portion of the functionality provided by a conventional CMTS, with the exception that the DCMTS communicates with the Head End using baseband optical signals.
According to the embodiment of
One advantage of including a DCMTS in a selected fiber node is that the DCMTS is able to provide additional bandwidth between the Head End 302 and that fiber node. Another advantage of including a DCMTS in selected fiber nodes is that the DCMTS may perform, at a relatively local level, at least a portion of the scheduling or MAC functions typically performed by the CMTS at the Head End (e.g. 302) of the cable network.
For example, according to different embodiments, the DCMTS may be configured to perform downstream modulation, upstream demodulation, ranging, registration, generation of channel MAP messages, generation and termination of MAC messages, encryption/decryption, and other functions, such as those, described, for example, with respect to
In the reverse direction, electrical signals from the cable modems are transmitted via coax line 409 to the diplexor 410. The upstream signals are then passed from the diplexor 410 to the splitter 414. The splitter 414 separates the upstream signals, passing a first portion of the upstream signals to the DCMTS 430, and passing a second portion of the upstream signals to the Head End via components 406 and 408. According to a specific embodiment, the DCMTS 430 and CMTS (at the Head End) may each receive a copy of the upstream spectrum, and extract desired signals from selected portions of the upstream spectrum.
Although modified cable network of
One solution for addressing this latter problem of providing increased bandwidth capacity to the plurality of subscriber groups 310 is to increase the number of fiber nodes servicing the plurality of subscriber groups. An example of this is shown in
One problem with the cable network configuration of
Another drawback to the configuration of
Additionally, because each conventional fiber node must be modified to include a DCMTS and broadband fiber capabilities, deployment of the cable network 350 of
Contrary to efforts in the cable industry to implement a modified fiber node which is capable of supporting both baseband and broadband fiber optic communication, an alternate embodiment of the present invention departs from conventional wisdom by dividing the problem, whereby two distinct types of fiber nodes are implemented in the cable network. This is shown, for example, in
According to the embodiment of
As shown in
As shown in
In the embodiment of
In addition to being configured to receive baseband optical signals, the packet fiber nodes 520 may also be configured to receive electrical signals from the RF fiber nodes via coax lines (e.g. 507A, 507B). Such electrical signals may include, for example, clock or other timing reference signals and/or timestamp synchronization signals.
One advantage of creating a separate packet fiber node 600 is that it is less costly and easier to implement than the modified fiber node described, for example, in
Another advantage of the packet fiber node implementation is that the packet fiber node may be used as a component for deploying fiber to the home, in the MSO environment. For example, a packet fiber node may initially utilize a DCMTS to push the IP layer deep into the network. Thereafter, the DCMTS may be removed, and the packet fiber node may then be used as a platform to deliver fiber directly to the home. Additionally, by designing a cable network to include separate packet fiber nodes as shown, for example, in
An additional advantage of the packet fiber node implementation of the present invention as shown, for example, in
By way of illustration, let us assume that CMTS 120 of
CMTS and DCMTS Configurations
Electrical upstream data signals (packets) arriving via lines 710 are demodulated by a receiver 714, and then passed to MAC layer block 730. A primary purpose of MAC layer 730 is to encapsulate, with MAC headers, downstream packets and decapsulate, of MAC headers, upstream packets. In one embodiment, the encapsulation and decapsulation proceed as dictated by the above-mentioned DOCSIS standard for transmission of data or other information. The MAC headers include addresses to specific modems (if sent downstream) or to the CMTS (if sent upstream) by a MAC layer block 730 in DCMTS 700. Note that the cable modems also include MAC addressing components. In the cable modems, these components encapsulate upstream data with a header containing the MAC address of the DCMTS and/or CMTS.
MAC layer block 730 includes a MAC layer hardware portion and a MAC layer software portion. The MAC layer hardware portion includes a MAC controller 734, and may also include a processor 735. According to a specific implementation, the processor 735 may be configure to perform functions relating to MAP routing, load balancing, etc. The MAC layer software portion may include software relating to DOCSIS MAC functionality 784, MAP routing functionality 783 (if desired), load balancing functionality 785 (if desired), etc. The MAC layer hardware and software portions operate together to provide the above-described functionality. In a preferred embodiment, MAC hardware portion 734 is distinct from a general-purpose microprocessor 755, and is dedicated to performing some MAC layer functions.
In specific DCMTS configurations, the hardware portions of the physical layer 732 and MAC layer 730 reside on physical line cards 720 within the DCMTS. The DCMTS may include a plurality of distinct line cards which service particular cable modems in the network. Each line card may be configured to have its own unique hardware portions of the physical layer 732 and MAC layer 730.
After MAC layer block 730 has processed the upstream information, it is then passed to network layer block 744. According to a specific implementation, the network layer block 744 includes tunneling software 782 for causing the upstream information packet to be tunneled to via the optical fiber interface 702 to the CMTS. According to an alternate embodiment, the DCMTS may be configured to communicate with the Head End and other DCMTS devices via a standardized IP protocol.
According to a specific embodiment, the optical fiber interface 702 may also include a laser and optical-electrical signal conversion componentry for converting optical signal into electrical signals and vice-versa. In the specific embodiment of
When a packet is received at the optical fiber interface 702 from the CMTS, the network layer 744 passes the packet to MAC layer 730. MAC block 700 then transmits information via a one-way communication medium to downstream modulator and transmitter 706. Downstream modulator and transmitter 706 takes the data (or other information) in a packet structure and converts it to modulated downstream frames, such as MPEG or ATM frames, on the downstream carrier using, for example, QAM64 modulation. Other methods of modulation may also be used such as, for example, QAM256 modulation, CDMA (Code Division Multiple Access), OFDM (Orthogonal Frequency Division Multiplexing), FSK (FREQ Shift Keying), etc. The return data is likewise modulated using, for example, QAM16 or QSPK. According to a specific embodiment, the modulated data is converted from IF electrical signals to RF electrical signals (or vice-versa) using one or more electrical signal converters (not shown).
Note that alternate embodiments of the DCMTS (not shown) may not include network layer 744. In such embodiments, a DCMTS device may include only a physical layer and a MAC layer, which are responsible for modifying a packet according to the appropriate standard for transmission of information over a cable modem network. The network layer 744 of these alternate embodiments of DCMTS devices may be included, for example, as part of a conventional router for a packet-switched network. In a specific embodiment, the network layer of the DCMTS is configured as a line card coupled to a standard router that includes the physical layer block 732 and MAC layer block 730. Using this type of configuration, the DCMTS is able to send and/or receive IP packets to and from the optical fiber interface 702 using tunneling software block 782. According to an alternate embodiment, the DCMTS may be configured to include all or a selected portion of the functionality implemented at a conventional CMTS. In this latter embodiment, the DCMTS devices may be configured to handle conventional CMTS functionality, and may be aggregated via a router or switch at the Head End (illustrated, for example, in
As shown in
According to a specific embodiment, the procedures employed by the DCMTS during registration and pre-registration are performed at the MAC layer of the DCMTS logic. Thus, in DCMTS 700, most of the registration operations would be performed by the hardware and software provided for MAC layer logic 730. Additionally, the operations associated with obtaining an IP address for cable modems may be implemented at the network layer level 744.
In a specific embodiment, the DCMTS systems of this invention may be specially configured CMTSs or routers such as, for example, specially configured models in the uBR-7200 series and uBR-10012 series of CMTSs available from Cisco Systems, Inc. of San Jose, Calif. In an alternative embodiment, the invention may be implemented on a general-purpose network host machine such as a personal computer or workstation. Further, the invention may be at least partially implemented on a card (e.g., an interface card) for a network device or a general-purpose computing device.
Although the system shown in
Regardless of network device's configuration (for cable plants or otherwise), it may employ one or more memories or memory modules (e.g., memory 757) configured to store program instructions for the network operations and other functions of the present invention described herein. The program instructions may specify an operating system and one or more applications, for example. Such memory or memories may also be configured to store data structures or other specific non-program information described herein.
As shown in
As shown in the embodiment of
According to a specific embodiment, Routing Engine A may be configured or designed to include a plurality of functionally different modules or components, including, for example, a Forwarding Processor (FP) Module 811 a adapted to provide packet forwarding functionality; a Route Processor (RP) Module 803 a adapted to implement routing or forwarding operations; a utility component 802 a adapted to provide system clock and timestamp functionality; etc. The routing engine components provide may be configured to provide layer one, layer two, layer three and layer four functionality as well as quality of service (QoS) functionality.
According to a specific implementation, the RP Module 803 a may be configured as a processor-based routing system comprising functionality incorporated within a typical router, such as, for example, specially configured router models 1600, 2500, 2600, 3600, 4500, 4700, 7200, 7500, 10012, and 12000 available from Cisco Systems, Inc. of San Jose, Calif. For example, as shown in the embodiment of
The RP processor 805 a may be configured to construct and load routing tables used by the FP Module 811 a. The processor 805 a may also be configured or designed to perform configuration management functions of the routing engine 801 a, and to communicate with neighboring peer, standby, and/or backup routers to exchange protocol data units used to construct the routing tables in accordance with conventional routing algorithms. It will be apparent to those skilled in the art that other memory types, including various computer readable media, may be used for storing and executing program instructions pertaining to the operation of the routing engine.
Interface circuitry 827 a may be coupled to the respective interface circuitry 833 a, 833 b of line cards 831 a, 831 b. According to a specific implementation, interface circuitry 827 a may be configured to reside on a backplane logic circuit 823 a of the routing engine. In one example, the backplane logic circuit 823 a is embodied as a high performance, application specific integrated circuit (ASIC). An example of a backplane logic circuit that may be advantageously used with the present invention is disclosed in co-pending and commonly owned U.S. patent application Ser. No. 09/791,063, filed on Feb. 22, 2001, the entirety of which is hereby incorporated by reference for all purposes.
According to a specific embodiment, the backplane logic circuit (which, according to a specific implementation, may be configured as an ASIC), may be configured to further interface the line cards to a packet buffer 825 a and a forwarding engine 821 a of the FP Module 811 a. The packet buffer 825 a may include memory which is configured to store packets as the forwarding engine 821 a performs its packet forwarding functions. For example, the packet buffer may be used to store low priority data packets while high priority, low latency voice packets are forwarded by the forwarding engine to a data network interface 835 a. According to various embodiments, the FP Module 811 may comprise a processor 813 a and memory 815 a for handling transport layer 817 and network layer 819 functionality. In one implementation, the processor 813 a may be configured to track accounting, port, and billing information for various users on a cable modem network 851. The processor 813 a may also be configured to maintain desired service flow or session state information in memory 815 a such as, for example, for voice calls initiated over the cable modem network. The FP Module 811 a may also be configured to provide transaction compacting functionality, data parcel tunneling functionality, switching functionality, and other functionality described herein.
According to a specific implementation, Routing Engine A 801 a may be connected to Routing Engine B 801 b via at least one link 846, such as, for example, a backplane line or system bus. Routing engine redundancy may be provided by designating one of the routing engines as the working or primary routing engine and designating the other routing engine(s) as the redundant or standby routing engine(s). When configured as a working routing engine, the Routing Engine A may perform all appropriate forwarding and routing functions. When a failure occurs at the working routing engine, the redundant routing engine (e.g. Routing Engine B) may then take over the operations of the working routing engine. Thereafter, when Routing Engine A recovers, it may assume the functions of the redundant routing engine, or it may take over the functions of the working routing engine.
According to different embodiments of the present invention, one or more of the routing engines may be configured to communicate with a plurality of line cards (e.g. 831, 835) via point-to-point links. For example, as shown in
According to a specific embodiment, the plurality of line cards may include different types of line cards which have been specifically configured to perform specific functions. For example, Line Card A 831 a may correspond to radio-frequency (RF) line card which has been configured or designed to transmit and receive RF modulated optical signals. Line Card B 831 b may correspond to baseband line card which has been configured or designed to transmit and receive baseband optical signals. Additionally, line cards 835 may correspond to network interface cards which have been configured or designed to interface with different types of external networks (e.g. WANs, LANs,) utilizing different types of communication protocols (e.g. Ethernet, Frame Relay, ATM, TCP/IP, etc). For example, the data network interface 835 a functions as an interface component between external data sources and the cable system. The external data sources transmit data to the data network interface 835 a via, for example, optical fiber, microwave link, satellite link, or through various media. A data network interface may include hardware and software for interfacing to various networks. According to various embodiments, a data network interface may be implemented on a line card as part of a conventional router for a packet-switched network. Using this type of configuration, the CMTS is able to send and/or receive IP packets to and from the data network interface using, for example, network layer software 819 a.
According to a specific implementation, the operations associated with obtaining an IP address for cable modems may be implemented by the network layer software. This may involve the CM communicating with a DHCP server (not shown) via a data network interface, for example.
As shown in
According to a specific embodiment, the point-to-point links 841, 843 may be configured as clock forwarded links such that each point-to-point link comprises at least one data wire for transporting data signals and at least one clock wire for carrying clock signals. However, it will be understood to those skilled in the art that the clock forwarding technique may be scaled to accommodate other clock forwarding arrangements such as, for example, connections comprising a plurality or data signals and/or clock signals. Additionally, according to a specific embodiment, each line card may be configured to provide at least one communication interface between the routing engines (801 a, 801 b) and a portion of the cable network. The data network interface 835 a may couple the routing engine 801 a to an external data network 855 such as, for example, the Internet.
According to one embodiment, all or selected lines cards, routing engines and/or data network interfaces may be configured to use at least one common dedicated line or backplane (e.g. 845). According to other embodiments, the routing engines 801 a, 801 b may have an additional dedicated connection(s) for supporting redundancy. In a specific implementation, the backplane may be configured as an Ethernet medium that is shared by the CMTS. When the line cards are inserted into the backplane, they communicate with the routing engines over the lines 845 in accordance with a “capabilities” exchange that identifies the types of line cards and their various characteristics/parameters.
According to a specific implementation, during initialization of the CMTS, the routing engines 801 a and 801 b negotiate for working routing engine status over the backplane. Assertion of working status causes the line cards 831 to configure their respective interface circuitry to communicate with the designated working routing engine (e.g. Routing Engine A 801 a). The Routing Engine A 801 a then configures the CMTS and line cards, establishes routing relationships, and initiates traffic forwarding operations. The redundant routing engine 801 b may complete a self-test and perform initialization of its various functions. The two routing engine assemblies may then exchange conventional negotiation messages (which may include, for example, health and status messages) via the backplane lines 845. According to a specific implementation, the exchanged messages are defined by an Enhanced High System Availability (EHSA) negotiation algorithm available from Cisco Systems, Inc. of San Jose, Calif. The redundant routing engine may also request transaction information from the working routing engine.
When the redundant routing engine 801 b detects that the primary routing engine has failed, the redundant routing engine may take over as the new working routing engine, and initiate a “cutover” operation to thereby cause the line card interface circuitry (e.g. 833 a, 833 b) to identify and communicate with the new working routing engine 801 b. The new working routing engine 801 b may then access and retrieve state information (such as, for example, telephone call state information, service flow state information, etc.) stored on selected line cards in order to maintain existing service flows.
Prior to a failure situation, the redundant routing engine 801 b may be configured to monitor the status of the working routing engine 801 a, and may further be configured or designed to receive updated configuration, transaction and/or state information, which may then be stored in an appropriate location in the redundant routing engine 801 b.
The line cards may further comprise circuitry for “looping” packets back onto the redundant routing engine 801 b over the point-to-point links. This allows the redundant routing engine 801 b to send and receive test packets to evaluate its own operation in addition to the operation of the dedicated lines prior to the occurrence of a system failure.
Although the system shown in
Regardless of the network device's configuration (for cable plants or otherwise), it may employ one or more memories or memory modules (e.g., memory 807 a, 815 a, etc.) configured to store program instructions for the network operations and other functions of the present invention described herein. The program instructions may specify an operating system and one or more applications, for example. Such memory or memories may also be configured to store data structures, or other specific non-program information described herein.
Because such information and program instructions may be employed to implement the systems/methods described herein, the present invention relates to machine-readable media that include program instructions, state information, etc. for performing various operations described herein. Examples of machine-readable media include, but are not limited to, magnetic media such as hard disks, floppy disks, and magnetic tape; optical media such as CD-ROM disks; magneto-optical media such as floptical disks; and hardware devices that are specially configured to store and perform program instructions, such as read-only memory devices (ROM) and random access memory (RAM). Aspects of the invention may also be embodied in a carrier wave travelling over an appropriate medium such as airwaves, optical lines, electric lines, etc. Examples of program instructions include both machine code, such as produced by a compiler, and files containing higher level code that may be executed by the computer using an interpreter.
It will be appreciated that, according to specific embodiments, the packet fiber node of the present invention may be implemented in a variety of different cable network configurations. For example, according to one embodiment, as shown, for example, in
It will be appreciated that, according to specific embodiments, at least a portion of functions described herein which are performed by the DCMTS (e.g.
According to a specific embodiment, communication of IP packets between the Head End complex 952 and the plurality of packet fiber nodes 955 may be accomplished without the use of a tunneling protocol. In such an embodiment, communication between network devices may be accomplished using, for example, a standardized IP protocol. Additionally, as shown in the embodiment of
It will be appreciated by one having ordinary skill in the art that the technique of the present invention may be implemented in any computer network having a standardized protocol for utilizing a central termination system (e.g. Head End) to schedule timeslots for remote stations or nodes on a return (or upstream) channel. In wireless networks, the central termination system may be referred to as a Head End or wireless base station. In satellite networks, the central termination system may be referred to as a master controlling station.
Although several preferred embodiments of this invention have been described in detail herein with reference to the accompanying drawings, it is to be understood that the invention is not limited to these precise embodiments, and that various changes and modifications may be effected therein by one skilled in the art without departing from the scope of spirit of the invention as defined in the appended claims.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US5604735||May 12, 1995||Feb 18, 1997||Finisar Corporation||High speed network switch|
|US5784597||Sep 22, 1995||Jul 21, 1998||Hewlett-Packard Company||Communications network system including acknowledgement indicating successful receipt of request for reserved communication slots and start time for said reserved communication slots|
|US5931954||Jan 13, 1997||Aug 3, 1999||Kabushiki Kaisha Toshiba||I/O control apparatus having check recovery function|
|US5933420||Apr 30, 1996||Aug 3, 1999||3Com Corporation||Method and apparatus for assigning spectrum of a wireless local area network|
|US5963557 *||Apr 11, 1997||Oct 5, 1999||Eng; John W.||High capacity reservation multiple access network with multiple shared unidirectional paths|
|US6023769||Sep 17, 1998||Feb 8, 2000||Apple Computer, Inc.||Method and apparatus for synchronizing an imprecise time clock maintained by a computer system|
|US6078595||Aug 28, 1997||Jun 20, 2000||Ascend Communications, Inc.||Timing synchronization and switchover in a network switch|
|US6101180||Nov 12, 1997||Aug 8, 2000||Starguide Digital Networks, Inc.||High bandwidth broadcast system having localized multicast access to broadcast content|
|US6233246||Dec 30, 1996||May 15, 2001||Compaq Computer Corporation||Network switch with statistics read accesses|
|US6381214||Oct 9, 1998||Apr 30, 2002||Texas Instruments Incorporated||Memory-efficient leaky bucket policer for traffic management of asynchronous transfer mode data communications|
|US6418324||Sep 17, 1997||Jul 9, 2002||Padcom, Incorporated||Apparatus and method for transparent wireless communication between a remote device and host system|
|US6490727 *||Oct 7, 1999||Dec 3, 2002||Harmonic, Inc.||Distributed termination system for two-way hybrid networks|
|US6510162||May 27, 1998||Jan 21, 2003||3Com Corporation||System and method for managing channel usage in a data over cable system|
|US6556591||Jul 19, 2001||Apr 29, 2003||Conexant Systems, Inc.||Method and apparatus for upstream burst transmission synchronization in cable modems|
|US6697970||Aug 28, 2000||Feb 24, 2004||Nortel Networks Limited||Generic fault management method and system|
|US6698022||Dec 15, 1999||Feb 24, 2004||Fujitsu Limited||Timestamp-based timing recovery for cable modem media access controller|
|US6763032||Feb 10, 2000||Jul 13, 2004||Broadcom Corporation||Cable modem system with sample and packet synchronization|
|US6771606||Jun 29, 2000||Aug 3, 2004||D-Link Corp.||Networking switching system on-line data unit monitoring control|
|US20020010750||Apr 27, 2001||Jan 24, 2002||Airsys Atm Sa||Redundant input/output management device, notably for data routing|
|US20020136203 *||Oct 24, 2001||Sep 26, 2002||Valentino Liva||Enhanced fiber nodes with CMTS capability|
|US20020161924||Apr 30, 2001||Oct 31, 2002||Perrin Robert E.||Method and apparatus for routing data over a computer network|
|US20020198967||Jun 22, 2001||Dec 26, 2002||Iwanojko Bohdan T.||Configuration parameter sequencing and sequencer|
|US20030214943||Aug 9, 2002||Nov 20, 2003||Microsoft Corporation||Method for switching protocols transparently in multi-user applications|
|US20050018697||Dec 2, 2003||Jan 27, 2005||Hybrid Networks, Inc.||High-speed internet access system|
|1||3COM, "High-Speed Cable Internet Solutions," http://www.3com.com/cablenow/pdf/7125dsht.pdf, 4 pages (Dec. 1999).|
|2||Cable Television Laboratories, Inc., Interim Specification, "Data-Over-Cable Service Interface Specifications, Radio Frequency Interface Specification, SP-RFIv1.1-I02-990731," Jul. 30, 1999, 352 pages.|
|3||Cable Television Laboratories, Inc., Interim Specification, "Data-Over-Cable Service Interface Specifications, Radio Frequency Interface Specification, SP-RFIv1.1-I04-000407," Apr. 7, 2000, 376 pages.|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US7490345 *||Jun 4, 2004||Feb 10, 2009||Terayon Communications Systems, Inc.||Upstream only linecard with front end multiplexer for CMTS|
|US7532627||May 23, 2005||May 12, 2009||Cisco Technology, Inc.||Wideband upstream protocol|
|US7539208||May 20, 2005||May 26, 2009||Cisco Technology, Inc.||Timing system for modular cable modem termination system|
|US7583704||Jun 10, 2003||Sep 1, 2009||Carl Walker||Synchronizing separated upstream and downstream channels of cable modem termination systems|
|US7620836||May 3, 2006||Nov 17, 2009||Cisco Technology, Inc.||Technique for synchronizing network devices in an access data network|
|US7630361||Mar 20, 2006||Dec 8, 2009||Cisco Technology, Inc.||Method and apparatus for using data-over-cable applications and services in non-cable environments|
|US7639617||May 17, 2005||Dec 29, 2009||Cisco Technology, Inc.||Upstream physical interface for modular cable modem termination system|
|US7639620||Mar 6, 2007||Dec 29, 2009||Cisco Technology, Inc.||Packet fiber node|
|US7646786||Dec 30, 2004||Jan 12, 2010||Cisco Technology, Inc.||Neighbor discovery in cable networks|
|US7656890||Jul 10, 2006||Feb 2, 2010||Cisco Technology, Inc.||Downstream channel change technique implemented in an access network|
|US7672230||Jul 10, 2006||Mar 2, 2010||Cisco Technology, Inc.||Downstream channel change technique implemented in an access network|
|US7672332||May 19, 2006||Mar 2, 2010||Cisco Technology, Inc.||Map routing technique implemented in access networks|
|US7688828||May 17, 2005||Mar 30, 2010||Cisco Technology, Inc.||Downstream remote physical interface for modular cable modem termination system|
|US7701951||Mar 6, 2006||Apr 20, 2010||Cisco Technology, Inc.||Resource reservation and admission control for IP network|
|US7720101||May 20, 2005||May 18, 2010||Cisco Technology, Inc.||Wideband cable modem with narrowband circuitry|
|US7792034 *||Oct 31, 2005||Sep 7, 2010||Broadcom Corporation||Hierarchical flow-level multi-channel communication|
|US7805073 *||Apr 28, 2006||Sep 28, 2010||Adc Telecommunications, Inc.||Systems and methods of optical path protection for distributed antenna systems|
|US7817553||May 10, 2005||Oct 19, 2010||Cisco Technology, Inc.||Local area network services in a cable modem network|
|US7835274||May 25, 2005||Nov 16, 2010||Cisco Technology, Inc.||Wideband provisioning|
|US7864686||May 20, 2005||Jan 4, 2011||Cisco Technology, Inc.||Tunneling scheme for transporting information over a cable network|
|US8068516 *||Feb 9, 2005||Nov 29, 2011||Bigband Networks, Inc.||Method and system for exchanging media and data between multiple clients and a central entity|
|US8081659||Jul 2, 2008||Dec 20, 2011||Cisco Technology, Inc.||Map message expediency monitoring and automatic delay adjustments in M-CMTS|
|US8094661||Mar 31, 2009||Jan 10, 2012||Comcast Cable Communications, Llc||Subscriber access network architecture|
|US8102854||Aug 15, 2008||Jan 24, 2012||Cisco Technology, Inc.||Neighbor discovery proxy with distributed packet inspection scheme|
|US8135273||Aug 24, 2010||Mar 13, 2012||Adc Telecommunications, Inc.||Systems and methods of optical path protection for distributed antenna systems|
|US8149833||May 24, 2005||Apr 3, 2012||Cisco Technology, Inc.||Wideband cable downstream protocol|
|US8428063 *||Mar 26, 2010||Apr 23, 2013||Comcast Cable Communications, Llc||Access network architecture having dissimilar access sub-networks|
|US8537680||Jul 30, 2010||Sep 17, 2013||Broadcom Corporation||Hierarchical flow-level multi-channel communication|
|US8576842||Jul 28, 2011||Nov 5, 2013||Cisco Technology, Inc.||Transmission of multi-channel MPEG|
|US8805182||Jan 19, 2012||Aug 12, 2014||Adc Telecommunications Inc.||Systems and methods of optical path protection for distributed antenna systems|
|US8953445||Sep 16, 2013||Feb 10, 2015||Broadcom Corporation||Hierarchical flow-level multi-channel communication|
|US8989221||Jun 4, 2012||Mar 24, 2015||Cisco Technology, Inc.||System and method for discovering and verifying a hybrid fiber-coaxial topology in a cable network environment|
|US9036654||Sep 12, 2014||May 19, 2015||SMG Holdings—Anova Technologies, LLC||Packet sharing data transmission system and relay to lower latency|
|US9118496||Dec 7, 2011||Aug 25, 2015||Comcast Cable Communications, Llc||Subscriber access network architecture|
|US9130769||Sep 12, 2012||Sep 8, 2015||Cisco Technology, Inc.||Upstream external PHY interface for data and control plane traffic|
|US9143349 *||Sep 19, 2008||Sep 22, 2015||Lantiq Deutschland Gmbh||Configurable media access controller|
|US9143808||Sep 14, 2012||Sep 22, 2015||Cisco Technology, Inc.||Multi-channel MPEG between headend and fiber node|
|US9231817||Mar 1, 2013||Jan 5, 2016||Comcast Cable Communications, Llc||Access network architecture having dissimilar access sub-networks|
|US9246700||Sep 12, 2012||Jan 26, 2016||Cisco Technology, Inc.||Generic control protocol|
|US9246701||Sep 12, 2012||Jan 26, 2016||Cisco Technology, Inc.||Downstream device architecture and control|
|US9313095||Sep 12, 2012||Apr 12, 2016||Cisco Technology, Inc.||Modular headend architecture with downstream multicast|
|US9419862||Feb 26, 2015||Aug 16, 2016||Cisco Technology, Inc.||System and method for discovering and verifying a hybrid fiber-coaxial topology in a cable network environment|
|US20050010958 *||Jun 4, 2004||Jan 13, 2005||Rakib Shlomo Selim||Upstream only linecard with front end multiplexer for CMTS|
|US20050265376 *||May 23, 2005||Dec 1, 2005||Chapman John T||Wideband upstream protocol|
|US20050265397 *||May 17, 2005||Dec 1, 2005||Cisco Technology, Inc.||Upstream physical interface for modular cable modem termination system|
|US20060168612 *||May 20, 2005||Jul 27, 2006||Cisco Technology, Inc.||Timing system for modular cable modem termination system|
|US20060251097 *||Jul 10, 2006||Nov 9, 2006||Cisco Technology, Inc.||Downstream channel change technique implemented in an access network|
|US20060271988 *||Mar 20, 2006||Nov 30, 2006||Chapman John T||Method and apparatus for using data-over-cable applications and services in non-cable environments|
|US20070098007 *||Oct 31, 2005||May 3, 2007||Broadcom Corporation||Hierarchical flow-level multi-channel communication|
|US20070195824 *||May 17, 2005||Aug 23, 2007||Cisco Technology, Inc.||Upstream physical interface for modular cable modem termination system|
|US20070206607 *||Mar 6, 2006||Sep 6, 2007||Chapman John T||Resource reservation and admission control for IP network|
|US20070264009 *||Apr 28, 2006||Nov 15, 2007||Adc Telecommunications, Inc.||Systems and methods of optical path protection for distributed antenna systems|
|US20080298277 *||Aug 15, 2008||Dec 4, 2008||Cisco Technology, Inc.||Neighbor discovery proxy with distributed packet inspection scheme|
|US20100002719 *||Jul 2, 2008||Jan 7, 2010||Cisco Technology, Inc.||Map message expediency monitoring and automatic delay adjustments in m-cmts|
|US20100074263 *||Sep 19, 2008||Mar 25, 2010||Charles Bry||Configurable Media Access Controller|
|US20100246582 *||Mar 31, 2009||Sep 30, 2010||Comcast Cable Communications, Llc||Subscriber Access Network Achitecture|
|US20100254386 *||Mar 26, 2010||Oct 7, 2010||Comcast Cable Communications, Llc||Access network architecture having dissimilar access sub-networks|
|US20100296511 *||Jul 30, 2010||Nov 25, 2010||Broadcom Corporation||Hierarchical Flow-Level Multi-Channel Communication|
|US20160099778 *||Oct 1, 2014||Apr 7, 2016||Arris Enterprises, Inc.||Upstream interference eliminating transmission of digital baseband signal in an optical network|
|WO2005122580A2 *||May 26, 2005||Dec 22, 2005||Terayon Communication Systems, Inc.||Upstream only linecard with front end multiplexer for cmts|
|WO2005122580A3 *||May 26, 2005||Apr 24, 2008||Yehuda Azenkot||Upstream only linecard with front end multiplexer for cmts|
|U.S. Classification||370/235, 370/229, 370/352, 725/129|
|Cooperative Classification||H04L45/60, H04Q2011/0064, H04Q11/0071, H04L45/58, H04L45/28, H04Q11/0067|
|European Classification||H04L45/58, H04L45/28, H04L45/60, H04Q11/00P4C|
|Dec 4, 2001||AS||Assignment|
Owner name: CISCO TECHNOLOGY, INC., CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:CHAPMAN, JOHN T.;REEL/FRAME:012341/0901
Effective date: 20011016
|Oct 25, 2010||FPAY||Fee payment|
Year of fee payment: 4
|Oct 24, 2014||FPAY||Fee payment|
Year of fee payment: 8