WO2015171953A1

WO2015171953A1 - Method and system for high bandwidth, multi-consumer data and video distribution equipment

Info

Publication number: WO2015171953A1
Application number: PCT/US2015/029782
Authority: WO
Inventors: James D. LUCIANO; Philip COADY
Original assignee: Luciano James D
Priority date: 2014-05-07
Filing date: 2015-05-07
Publication date: 2015-11-12

Abstract

Methods and systems for distributing signals, including video and data signals, to multiple consumers, with high bandwidth (BW) throughput data signals are disclosed herein. A headend may receive an input gigabit Ethernet (GBE) signal over a GBE port and determine to operate in a first mode or a second mode, wherein operating in the first mode complies with Multimedia over Coax Alliance (MoCA) 1.1 and operating in the second mode complies with MoCA 2.0. The headend may convert the input GBE signal to an output MoCA 1.1 compliant signal on a condition that operating in a first mode has been determined and convert the input GBE signal to an output MoCA 2.0 compliant signal on a condition that operating in a second mode has been determined. The headend may transmit the output MoCA 1.1 or MoCA 2.0 compliant signal to a consumer premises equipment over coaxial cable.

Description

METHOD AND SYSTEM FOR HIGH BANDWIDTH, MULTI-CONSUMER DATA AND VIDEO DISTRIBUTION EQUIPMENT

CROSS REFERENCE TO RELATED APPLICATION

[0001] This application claims the benefit of U.S. Provisional Application No. 61/989,793, filed May 7, 2014, the contents of which is hereby incorporated by reference herein.

FIELD OF INVENTION

£0002) The disclosed embodiments are generally directed to methods and systems for distributing signals, including video and data signals, to multiple consumers, with high bandwidth (BW) throughput data signals.

BACKGROUND

[0003) Multimedia over Coax Alliance (MoCA) equipment provides for the distribution of high quality digital transmissions throughout facilities with coaxial cable, including facilities with legacy or existing coaxial cable. For example, MoCA equipment may provide high quality multimedia content transmissions over the existing coaxial cable in a residence. MoCA equipment may be used by cable, satellite and telecommunications service providers, and allows customers to receive broadband digital media content via satellite, cable, telephony or Internet network connections.

[0004] Under MoCA, consumers may use advanced data and video equipment and applications, such as integrated in-home multimedia distribution services including multi-room high definition (HD) digital video recorders (DVRs). Headend equipment, consumer premises equipment (CPE) and media centers may be used as MoCA compliant equipment. Media centers may store, manage and maintain the rights to content. Also, media centers may then communicate the content or distribute the content to other media appliances in a residence. Headends may distribute data and video signals to one or more CPEs. SUMMARY

[0005] Methods and systems for distributing signals, including video and data signals, to multiple consumers, with high bandwidth (BW) throughput data signals are disclosed herein. The methods and systems disclosed herein may include remote management, configuration, control and maintenance.

[0006] A headend may receive an input gigabit Ethernet (GBE) signal over a GBE port and determine to operate in a first mode or a second mode, wherein operating in the first mode complies with Multimedia over Coax Alliance (MoCA) 1.1 and operating in the second mode complies with MoCA 2.0. The headend may convert the input GBE signal to an output MoCA 1.1 compliant signal on a condition that operating in a first mode has been determined and convert the input GBE signal to an output MoCA 2.0 compliant signal on a condition, that operating in a second mode has been determined.

[0007} The headend may transmit the output MoCA 1.1 compliant signal on a condition that operating in a first mode has been determined and the output MoCA 2.0 compliant signal on a condition that operating in a second mode has been determined. The headend may transmit the MoCA 1.1 or 2,0 signals to a plurality of pieces of consumer premises equipment (CPE) over coaxial cable.

[0008] The headend may transmit the output MoCA 1.1 compliant signal on one of the 1000 megahertz (MHz), 1150 MHz, 1325 MHz or 1500 MHz channels and receive the received input MoCA 1.1 compliant signal on one of the 1000 MHz, 1150 MHz, 1325 MHz or 1500 MHz channels. The headend may transmit the output MoCA 2.0 compliant signal on one of the 425 MHz, 625 MHZ, 825 MHz, 1025 MHz, 1225 MHz, 1425 MHz or 1625 MHz channels and receive the received input MoCA 2.0 compliant signal on one of the 425 MHz, 625 MHZ, 825 MHz, .1025 MHz, 1225 MHz, 1425 MHz or 1625 MHz channels.

[0009] The headend may also receive from a CPE an input MoCA 1.1 compliant signal on a condition that operating in a first mode has been determined and an input MoCA 2.0 compliant signal on a condition that operating in a second mode has been determined. The headend may convert the MoCA 1.1 or 2.0 signal to a GBE signal and transmit the GBE signal over a GBE part. The CPE may autosync with the headend.

BRIEF DESCRIPTION OF THE DRAWINGS

[0010] A more detailed understanding may be had from the following description, given by way of example in conjunction with the accompanying drawings wherein:

[0011] Figure 1. is a system diagram of an example signal distribution network system in which one or more disclosed embodiments may be implemented;

[0012] Figure 2 is a system diagram of example headend and CPE traffic flow assumptions;

[0013] Figure 3 is a system diagram of another consumer premises equipment (CPE) with Wi-Fi;

[0014] Figure 4 is a diagram of an example four port L2 CPE without Wi-Fi;

[0015] Figure 5 is a diagram of an example two port L2 CPE without Wi-Fi;

[0016] Figure 6 is a system level block diagram of an example Ethernet over coaxial cable (EoC) two channel system;

[0017] Figure 7 is a system level block diagram of an example EoC four channel system:

[0018] Figure 8 is a system diagram of example headend and CPE traffic flow assumptions;

[0019] Figure 9 is a diagram of an example CPE diplexing scheme;

[0020] Figure 10 is a diagram of an example headend diplexing scheme;

[0021] Figure 1.1 is a diagram of a view of an example four port 1-2 CPE housing rear faceplate;

[0022] Figure 12 is a diagram of a view of an example L3 CPE housing rear faceplate; [0023] Figure 13 is a diagram of a view of an example headend/two port L2 CPE housing front faceplate;

[0024] Figure 14 is a diagram of a view of an example four port L2 CPE housing front faceplate;

[0025] Figure 15 is a diagram of a view of an example L3 CPE housing front faceplate;

[0026] Figure 16 is a diagram of an example headend printed wiring board (PWB) general layout;

[0027] Figure 17 is a diagram of an example four port L2 CPE PWB genera] layout;

[0028] Figure IS is a diagram of an example two port L2 CPE PWB general layout:

[0029] Figure 19 is a diagram of an example of a headend network status screen;

[0030] Figure 20 is a diagram of an example of a headend port settings screen;

[0031] Figure 21 is a diagram of an example radio frequency (RF) settings screen:

[0032] Figure 22 is a diagram of an example cable television (CATV) configuration screen;

[0033] Figure 23 is a diagram of an example 802.1P-DSCP value screen;

[0034] Figure 24 is a diagram of an example firmware upgrade screen;

[0035] Figure 25 is a diagram of CPE configure screen:

[0036) Figure 26 is a diagram of a CPE RF settings screen;

[0037] Figure 27 is a diagram of a CPE status screen; and

[0038] Figure 28 a diagram of a CPE details screen.

DETAILED DESCRIPTION

[0039) Figure 1 is a system diagram of an example signal distribution system in which one or more disclosed embodiments may be implemented. An input data signal may be received from the Internet 120 and/or other networks, and may be routed through a router 132, which may include a firewall. The input data signal may be received through an Internet service provider (ISP), such as a cable television (CATV) service provider or a telecommunications provider. The input data signal may be transmitted via a fiber optic cable or other signaling infrastructure to the router 132. The router 132 may be located in central wiring room 130 of the building. The input data signal may be a gigabit Ethernet (GBE) signal, which may then be routed through a GBE switch 137 to a headend 140. In an example, transmission of the input data signal to the headend 140 may be controlled by a remote management station 110. The input data signal may include high bandwidth (BW) signals. The headend 1.40 may also receive a CATV video signal from a CATV hard line drop 122. Also, the headend 140 may receive a video signal from a video on demand (VoD) server.

[0040] The data signal received by the headend 140 may be an Ethernet signal. In an example, the data signal may be a GBE signal and may be received by the headend 140 via a GBE port. The headend 1.40 may convert the GBE signal to an Ethernet over coaxial cable (EoC) signal. In a further example, the data signal may be received by the headend via a fiber port. In an example, the headend 140 may be located in central wiring room 130 of a large building, such as an office building, apartment building or hotel, and may transmit the data and CATV video signals to one or more CPEs, 360, 170, 180 located in different offices, apartments or hotel rooms. Each CPE 160, 170, 180 may be used by a different subscriber or customer. The headend 140 may transmit the EoC signal over an RF coaxial cable backbone 150 to the CPEs. The RF coaxial cable backbone 150 may include the coaxial cable infrastructure of the large building.

[0041] In addition, the headend 140 may receive one or more data signals from one or more CPEs over the coaxial cable backbone and transmit the one or more data signals to the Internet 120. Specifically, the headend 140 may receive and EoC signal from one or more CPEs, convert the EoC signal to a GBE signal, and transmit the GBE signal to the Internet.

[0042] The backbone 150 may be the existing coaxial cable in a building. A challenge for CATV operators is delivering enough BW to a Multi Dwelling Unit. Using example disclosed herein, operator do not need to install Ethernet cable and may use the existing coaxial cable and deliver enough BW to their customers. Additionally, methods and systems disclosed herein may be used to deliver BW in any coaxial cable environment, including those in the hospitality, residential, medical, and like fields. In many developing countries, mostly or only coaxial cable is used.

[0043] As disclosed herein, the headend 140 may transport large amounts of data over the coaxial cable infrastructure symmetrically in an intelligent, manner. Also, as disclosed herein, the headend 140 and CPEs 160, 170, 180 may be remotely monitored, configured and managed, such as from a network operations center (NOC) which may simplify installations, service and support. Further, as disclosed herein, the headend 140 and CPEs 160, 170, 180 may be pre-programmable, multichannel and multi-frequency.

[0044] As used herein, a CPE may refer to a modem, a cable modem, an adapter, a subscriber box or a gateway, and these terms may be used interchangeably. A CPE may also have router functionality. As used herein, a headend may refer to multichannel data and video distribution equipment, and these terms may be used interchangeably.

[0045] The data signal transmitted by the headend 340 to the CPEs, 160, 170, 180 may be an Ethernet over coaxial cable (EoC) signal. The headend may transmit the CATV signal along with the EoC signals, such as EoC A and EoC B via the backbone 150. Further, the data signal may be a Multimedia over Coax Alliance (MoCA) compliant signal. As an example, the headend and CPEs may operate in MoCA 1,1 EoC mode, As a further example, the headend and CPEs may operate in MoCA 2.0 EoC mode.

f0046] The CPEs, 160, 170, 180 may contain up to four Ethernet ports. One Ethernet port may contain a power over Ethernet (PoE) port.. The CPEs, 160, 170, 180 may send an output data signal via the Ethernet ports to various user devices, such as, for example a personal computer, laptop computer, voice over internet protocol (VoIP) telephone, internet protocol television (IPTV) set top box (STB) and the like. The CPEs 160, 170, 180 may also receive data signals via the Ethernet ports from the user devices. The CPEs, 160. 170. 180 may also output the CATV video signal to the STB.

[0047] The headend 140 may manage BW control to each of the CPEs 160, 170. 180. A CPE may manage its ports and each port may be secured from the others. Further, each CPE may offer BW control to each individual port. For example, if 20 MB BW is allocated to a CPE, the CPE may then control how much BW is allocated to each port. Various combinations of BW allocations may be used. For example, the CPE may allocate 5 MB BW to each of the four ports, or 11 MB to a first port and 3 MB BW to each of the remaining three ports. As a further example, the CPE may allocate 8 MB BW to a first port, 1 MB BW to a second port, 4 MB BW to a third port and 7 MB BW to a fourth port.

[0048] Further, in an example, the CPE may include autosync and channel sensing capability. The CPE may autosync to the headend by available frequency, without manual configuration. Accordingly, the CPE may transmit an autosync signal to the headed. Further the CPE may automatically select and connect to an EoC or MoCA channel without operator intervention or configuration. In addition, the CPE may operate as a Layer 2 <L2) CPE or a Layer 3 (L3) CPE or both.

[0049] In a further example, the headend may include a built-in amplifier, which may balance out the line frequency signal imbalances. The built-in amplifier may include an active 15 decibel (dB) amplifier.

[0050] As disclosed herein, the headend may amplify the CATV signal in both the upstream and the downstream, and the headend amplifier may be remotely manageable. Further, the headend may multiplex the EoC signal or signals with the CATV signal Also, the headend and CPE may embed Ethernet switch stacking which may reduce the amount of required Infrastructure for multiple Head End/Network Controllers. In addition, the headend and CPE may use programmable diplexers that may allow for software upgrade from 175 megabits per second (Mb/s) to 400/500 Mb/s per channel frequency. As disclosed herein, the headend and CPE may include a software/hardware alarm for monitoring EoC signal quality. Further, the monitoring may determine cable infrastructure plant faults. In an example, the headend and CPE may provide embedded software that allows the end user/customer of record to be alarmed if their signal strength is increased or decreased from their requirement ranges or ranges. The technology/software may notify the designated support team of the issue prior to their customers knowing about the issue, thereby allowing for proactive troubleshooting to begin.

[0051] The EoC headend may use a system on a chip (SoC) platform. For example, the headend may use Free scale's i.MXGLS platform SoC. Further, the headend maybe feature rich and support up to up to 128 CPE nodes (up to 64 CPEs per channel), 802.1q VLANs and IP multicast filtering. The headend design may operate in a MoCA 1.1 based EoC mode or a MoCA 2.0 based EoC mode.

[0052] The headend device also may allow a headend user to implement multicast IPTV, VoD, VoIP, among other services since this design comes with low latency and high throughput of the EoC system inherited in its MoCA capabilities. In this way, the headend leverages existing coaxial cable infrastructure to implement a network backbone to reduce costs and time to install.

[0053] Features of the headend include the following. Each headend may provide two EoC RF channels and may support dual GBE ports. Each EoC RF channel may provide 175 Mbps aggregate media access control (MAC) throughput in one mode and 400 Mbps MAC throughput in another mode. Up to two headends may coexist on the coaxial cable plant. The EoC network per coax may support aggregate MAC throughput of up to 1.6 Gb/s and up to 126 EoC CPEs. Also, the headend may support 802.1q VLANs and IP multicast filtering.

[0054] One example variant of CPE is a four port Ethernet CPE and another variant is a two port. 10/100/1000 Mb/s Ethernet. CPE. The Ethernet ports of each CPE may belong to an aggregate of up to 1024 VLANs. In an example, one Ethernet port of a CPE supports PoE. Further, the Ethernet switch of each CPE may provide loop detection and mitigation. Both CPE variants support a PoE part, IGMP snooping, loop detection and mitigation. The CPE design may operate in a MoCA 1.1 based EoC mode or a MoCA 2.0 based EoC mode.

[0055] The CPE device also may allow a CPE user to implement multicast IPTV, Vol), VoIP, among other services since this design comes with low latency and high throughput of the EoC system inherited in its MoCA capabilities. In this way. the CPE leverages existing coaxial cable infrastructure to implement a network backbone to reduce costs and time to install.

[0056] Features of the CPE include the following. Each CPE may automatically connect to an EoC channel without operator intervention or configuration. Further each CPE may provide 175 Mbps aggregate MAC throughput in one mode and 400 Mbps MAC throughput in another mode.

[0057] Figure 2 is a system diagram of example headend and CPE traffic flow assumptions. The headend 240 and CPEs 262, 264, 266 may be used within the signal distribution system illustrated in Figure 1. Figure 2 illustrates the traffic flow assumptions for a solution utilizing an L3 headend device 240 and L3 CPE devices 262, 264, 266. The CPE devices 262, 264. 266 may also be L2 CPEs. In an example scenario, the headend device 240 may be responsible only for traffic shaping/rate limiting. The internet group management protocol (IGMP) snooping, multicast filtering and virtual local area network (VLAN) tag removal may occur on the CPE devices 262, 264, 266 in an adjunct L2 managed switch (L2 CPE) or via the Wi-Fi host in the L3 CPE as required (using either software or hardware). The requirement for an L2 switch in the L3 CPE may be dependent upon the capabilities of the Wi-Fi host. In an example, no L2 switch may be used.

[0058] As shown in Figure 2, the EoC headend 240 may receive data signals from the Internet 220 via the VOD server/multicast router 230. The router 230 may provide Ethernet signals 235 to the EoC headend 240. The Ethernet signals 235 may be multicast Hows, a combined unicast multicast flow and/or a broadcast flow. The multicast traffic may be sent as broadcast by the headend. The headend 240 may also transmit Ethernet signals 235 to the router 230. which in turn may transmit data signals to the Internet 220. The router 230 may also provide video data and other data to the headend 240. Further, the headend 240 may receive a CATV signal 215 from a cable operator network 210. Network 210 may be a multi-system operator (MSO) network. The headend 240 may transmit the flows 242, 244, 246, which may include both EoC and CATV signals, over the premise cable plant 250 to CPEs 262, 264, 266 located in client rooms 252, 254, 256. The headend 240 may also receive EoC signals over the premise cable plant 250 from CPEs 262, 264, 266. £0059] Figure 3 is a diagram of an example CPE with Wi-Fi. The CPE in Figure 3 may receive an EoC and CATV signal via F connector 330 and output a CATV signal via F connector 350. In an example, when the CPE operates in MoCA 1.1 mode, the EoC signal may be an EoC MoCA 1.1 signal 360, transmitted on the 1000 megahertz (MHz), 1150 MHz, 1325 MHz or 1500 MHz channels. In a further example, when the CPE operates in MoCA 2.0 mode, the EoC signal may be an EoC MoCA 2.0 signal 370, transmitted on the 425 MHz, 625 MHZ, 825 MHz, 1025 MHz. 1225 MHz, 1425 MHz or 1625 MHz channels. In an example, the CPE may also transmit an EoC signal to the headend via F connector 330.

[0060J In an example, the CPE may support a single GBE port 310 for IPTV service delivery and a dual band concurrent Wi-Fi subsystem for triple play services delivery. In an example, the Wi-Fi host 320 may have the ability to do all required Ethernet filtering/VLAN traffic modifications in hardware or software. If the Wi-Fi 320 host cannot do this required filtering, then an additional L2 Ethernet switch may have to be used to connect the EoC device to the Wi-Fi host 320. Unintended traffic may be filtered prior to delivery to the end user via the host or additional L2 switch, if required. Programmable diplexer 340 control may be achieved via host general purpose input/output (GPIO) control. In an example, the Wi-Fi host 320 may use flash memory 322 and/or data double rate type 3 (DDKS) memory 324.

[0061] Figure 4 is a diagram of an example four port L2 CPE without Wi-Fi. The CPE in Figure 4 may receive an EoC and CATV signal via F connector 430 and output, a CATV signal via F connector 450. In an example, when the CPE operates in MoCA 1,1 mode, the EoC signal may be an EoC MoCA 1.1 signal 460, transmitted on the 1000 megahertz (MHz), 1150 MHz, 1325 MHz or 1500 MHz channels. In a further example, when the CPE operates in MoCA 2.0 mode, the EoC signal may be an EoC MoCA 2.0 signal 470, transmitted on the 425 MHz, 625 MHZ, 825 MHz, 1.025 MHz, 1225 ΜΙΪκ, 1425 MHz or 1625 MHz channels. In an example, the CPE may also transmit an EoC signal to the headend via F connector 430.

[0062] The CPE architecture shown in Figure 4 has four GBE ports 412, 4.14. 416, 418 which may be optimized for VoIP, IPTV and HSIA delivery. The L2 switch 420 may be used to add Ethernet traffic management requirements (e.g., IGMP snooping, multicast filtering, Vi-AN tag insertion/removal and the like). Unintended multicast traffic may be filtered prior to delivery to the end user via the L2 Ethernet switch 420. At least one of the four Ethernet ports 4.12. 414, 416, 418 may be capable of powering VoIP telephones (e.g., Cisco) or Wireless access points (e.g., Ruckus). The CPE of Figure 4 may support IEEE 802.3af Class 3 PoE. The PoE circuitry may be a population option. Programmable Diplexer 440 control may be implemented via XC1028 GPIO pins. In an example, the CPE may use a boot flash 422.

[0063J Figure 5 is a diagram of an example two port L2 CPE without Wi-Fi. The CPE in Figure 5 may receive an EoC and CATV signal via F connector 530 and output a CATV signal via F connector 550. la an example, when the CPE operates in MoCA 1.1 mode, the EoC signal may be an EoC MoCA 1.1 signal 560, transmitted on the 1000 megahertz (MHz), 1150 MHz, 1325 MHz or 1500 MHz channels. In a further example, when the CPE operates in MoCA 2.0 mode, the EoC signal may be an EoC MoCA 2.0 signal 570, transmitted on the 425 MHz, 625 MHZ, 825 MHz, 1025 MHz, 1225 MHz, 1425 MHz or 1625 MHz channels. In an example, the CPE may also transmit an EoC signal to the headend via F connector 530.

[0064) The CPE architecture shown in Figure 5 has two GBE ports, 512, 514 which may be optimized for VoIP, IPTV and HSIA delivery. The L2 switch 520 may be used to add Ethernet traffic management requirements (e.g., IGMP snooping, multicast filtering, VLAN tag insertion/removal and the like). Unintended multicast traffic may be filtered prior to delivery to the end user via the L2 Ethernet switch 520. At least one of the two Ethernet ports may be capable of powering VoIP telephones (e.g., Cisco) or Wireless access points (e.g., Ruckus). The CPE of Figure 5 may support IEEE 802.3af. Class 3 PoE. The PoE circuitry may be a population option. Programmable Diplexer 540 control may be implemented via XC1028 GPIO pins.

[0065] Figure 6 is a system level block diagram of an example EoC two channel system. Figure illustrates an example two channel EoC deployment, using optimized hardware. In an example, the system in Figure 6 may deliver up to 350 Mbps in MoCA 1,1 mode or 800 gigabits per second (Gb/s) in MoCA 2.0 mode (MoCA 2.0 mode shown for example).

[0066] In an example, the headend 640 may receive a data signal from the Internet 620 through the service provider backbone 626, premise highspeed internet access (HSIA) gateway 632 and Ethernet switch 637. The headend 640 may also receive a private branch exchange (PBX) signal from PBX 624 through the service provider backbone 626, premise HSIA gateway 632 and Ethernet switch 637. The headend may also send signals back to the Internet 620 and PBX 624 through the service provider backbone 626, premise HSIA gateway 632 and Ethernet switch 637. An integrator management console 6.1.0 may manage the data transmission and reception to and from the Internet 620. The headend 637, which may be located in a premise headend location 630, such as a basement, may receive GBE signals from the Ethernet switch 637 and transmit GBE signals to the Ethernet switch 637. The headend may also receive CATV and IP services from a MSO distribution plant.622.

[0067] The headend 640 may transmit the EoC and CATV signals over the property cable coax plant 650 to CPEs 662, 664, 666 located in client rooms 652, 654, 656. The headend 640 may also receive EoC signals over the premise cable plant 660 from CPEs 662, 664, 666.

[0068] Figure 7 is a system level block diagram of an example EoC four channel system. Figure 7 illustrates an example four channel, fully implemented EoC deployment, using optimized hardware. In an example, the system in Figure 7 may delivery up to 700 Mbps in MoCA 1.1 mode or 1.6 Gb/a in MoCA 2.0 mode (MoCA 1.1 mode shown for example).

[0069] The headends 740, 745, which may be located in a premise headend location 730, such as a basement, may each receive GBE signals from the Ethernet switch 737 and transmit GBE signals to the Ethernet switch 737. In addition, the headends 740, 745 may transmit and receive GBE signals between each other. The headends 740, 745 may transmit the SoC and CATV signals over the property cable coax plant 750 to CPEs 761, 762, 764, 766. 768 located in client rooms 751, 752, 754, 756, 758. The headends 740, 745 may also receive EoC signals over the premise cable plant 750 from CPEs 761, 762, 764, 766, 768.

[0070] Figure 8 is a system diagram of example headend and CPE traffic flow assumptions. Figure 8 illustrates the traffic flow assumptions for a solution utilizing a L3 headend 840 and L2 CPE devices 862, 864, 866. In an example, the headend 840 may be responsible for traffic shaping/rate limiting. The Ethernet signals may be multicast flows, a combined unicast multicast flow and/or a broadcast flow. The multicast traffic may be sent as broadcast by the headend 840. The IGMP snooping, multicast filtering and VLAN tag removal may occur on the CPE devices 862, 864, 866 in a L2 managed Ethernet switch integrated circuit CIO. The headend 840 may transmit the flows, which may include both EoC and CATV signals, over the premise cable plant to CPEs 862, 864, 866 located in client rooms 852, 854, 856. The headend 840 may also receive EoC signals over the premise cable plant from CPEs 862, 864, 866.

[0071] Figure 9 is a diagram of an example CPE dipiexing scheme. In an example, a CPE using the dipiexing scheme of Figure 9 may ensure future upgradability. In an example, the CPE may be upgraded from a MoCA 1.1 based EoC CPE to a MoCA 2.0 baaed EoC CPE. In an example, band pass filters, RP switches and splitters are available from MURATA, GPIO control may select either the MoCA 1,1 based EoC path or the MoCA 2.0 based EoC path. [0072] In an example, the ViXS EoC Chipset 910 may receive an EoC signal from a headend though F-Conn 985, by way of a matching network 980, bandpass filter 970, RF switch (SP2T) 960, RF switches (SP4T) 952, 954 and bandpass filters for either the MoCA 1.1 based EoC path (1000 MHz, 1.150 MHz, 1325 MHz and 1500 MHz) or the MoCA 2.0 based EoC path (1625 MHz, 1450 MHz, 1225 MHz and 1025 MHz). The EoC signal may be a MoCA 1.1 signal or a MoCA 2.0 signal. The EoC signal may continue on through the RF switches (SP4T) 934, 984 and RF switch (SP2T) 920 to ViXS EoC Chipset 910. The processor chipset 910 may determine to operate in MoCA .1.1 mode or MoCA 2,0 mode. The chipset 910 may convert the MoCA 1.1 signal to an Ethernet output signal on a condition that operating in MoCA 1.1. mode has been determined. The chipset 910 may convert the MoCA 2.0 signal to an Ethernet output signal on a condition that operating in MoCA 2.0 mode has been determined. The Ethernet output signal may then be sent to Ethernet ports (not shown). The ViXS EoC Chipset 910 may receive Ethernet input signals from the Ethernet ports (not shown) and transmit EoC signals back in the opposite direction. Specifically, the EoC signals may be MoCA 1.1 compliant signals, and the chipsets 1010, 1015 may convert the Ethernet input signals to MoCA 1.1 signals on a condition that operating in MoCA 1.1 mode has been determined. Also, the EoC signals may be MoCA 2.0 compliant signals, and the chipsets 1010, 1015 may convert the Ethernet input signals to MoCA 2.0 signals on a condition that operating in MoCA 2.0 mode has been determined. Further, the CATV signal may travel from the matching network 980 to the CATV bandpass filter 990 to F-Conn 995 for use by the user.

[0073] Figure 10 is a diagram of an example headend diplexing scheme. In an example, a headend using the diplexing scheme of Figure 10 may ensure future upgradability. In an example, the headend may be upgraded from a MoCA 1.1 based EoC headend to a MoCA 2.0 based EoC headend. In Figure 10, the optionally populated OS CATV amp is also shown for reference. Band pass filters, CATV US, CATV OS, RF switches and splitters are available from MURATA. The US and OS CATV amplifier block diagram is for illustrative purposes only and not meant to imply implementation details. GPIO control may select either the MoCA 1.1 based EoC path or the MoCA 2.0 based EoC path.

[0074] In an example, a 5 port Ethernet switch 1005 may receive GBE data signals from a router through RJ45 Conns .1002, 1004 and transmit a GBE data signals to each ViXS EoC chipset 1010, 1015. The processor chipsets 1010, 1015 may determine to operate in MoCA 1.1 mode or MoCA 2.0 mode. The chipsets 1010, 1015 may convert the GBE data signals to EoC signals. Specifically, the EoC signals may be MoCA 1.1 compliant signals, and the chipsets 1010, .1015 may convert the GBE data signals to MoCA 1.1 signals on a condition that operating in MoCA 1.1 mode has been determined. Also, the EoC signals may be MoCA 2.0 compliant signals, and the chipsets 1010, 1015 may convert the GBE data signals to MoCA 2.0 signals on a condition that operating in MoCA 1.1 mode has been determined.

[0075] ViXS EoC Chipset 1010 may transmit an EoC signal to F-Gonn 1085, by way of switch (SP2T) 1020. RF switches (SP4T) 1032, 1.025 and bandpass filters for either the MoCA 1.1 based EoC path (1000 MHz, 1150 MHz. 1325 MHz and 1500 MHz) or the MoCA 2.0 based EoC path (1625 MHz. 1450 MHz. 1225 MHz and 1025 MHz). The EoC signal may continue on through the RF switches (SP4T) 1052, 1054, RF switch (SP2T) 1060, splitter 1069, bandpass filter 1070, matching network 1080 to F-Conn 1085. F-Conn 1085 may also receive a CATV signal from the CATV bandpass 1090 by way of matching network 1080. F-Conn 1085 may send the EoC and CATV signal to the CPEs via coaxial cable.

[0076] The ViXS EoC Chipsets 1010, 1015 may receive EoC signals back in the opposite direction. The chipsets 1010, 1015 may convert the EoC signals to GBE signals. Specifically, the EoC signals may be MoCA 1.1 compliant signals, and the chipsets 1010, 1015 may convert the MoCA 1.1 signals to GBE data signals on a condition that operating in MoCA 1.1 mode has been determined. Also, the EoC signals may be MoCA 2.0 compliant signals, and the chipsets 1010, 1015 may convert the MoCA 2.0 signals to GBE data signals on a condition that operating in MoCA 2.0 mode has been determined. The headend may include a switch and one or more Ethernet to coaxial microchips. The Ethernet to coaxial microchips may be MoCA microchips.

[0077] Figure 11 is a diagram of a view of an example four port L2 CPE housing rear faceplate. Screw house may be used to affix the faceplate to the clamshell. An extruded clamshell may be used for the housing. The faceplate may allow for CATV 1110 and CATV and EoC 1120 connections as well as four Ethernet ports 1132, 1134, 1136, 1138.

[0078] Figure 12 is a diagram of a view of an example L3 CPE housing rear faceplate. Depending upon housing tooling selections, this board may or may not share common port locations with the Headend and L2 CPE devices. The faceplate may allow for CATV 1210 and CATV and EoC 1220 connections as well as an Ethernet port 1230.

[0079] Figure 13 is a diagram of a view of an example headend/two port E-2 CPE housing front faceplate. Screw house may be used to affix the faceplate to the clamshell. The faceplate may allow for indicator lights, such as light emitting diodes (LEDs), to indicate power 1310, the coaxial cable link transmissions 1320, and transmissions over the Ethernet ports 1330, 1340. The faceplate may be used for a headend or for a two port L2 CPE.

[0080] Figure .1.4 is a diagram of a view of an example four port L2 CPE housing front faceplate. Screw house may be used to affix the faceplate to the clamshell. The faceplate may allow for indicator lights, such as LEDs, to indicate power 1410, the coaxial cable link transmissions 1420, and transmissions over the Ethernet port s 1430, 1440, 1450, 1460.

[0081] Figure 15 is a diagram of a view of an example L3 CPE housing front faceplate. In an example, the board may or may not share common port locations. The faceplate may allow for indicator lights, such as LEDs, to indicate power 1510, the coaxial cable link transmissions 1520, transmissions over the Ethernet ports 1530 and wireless transmissions over the 2.4 GHz band 1540 and the 5 GHz band 1.550.

[0082] Figure 16 is a diagram of an example headend printed wiring board (PWB) general layout. In an example, mounting holes may be in same position as in the CPE devices, if a PEM Stud approach is used to affix the PWB to housing. The board dimensions may be the same as those of the CPE device. In an example, the board may rely on an external power supply. In another example, the layout may be adjusted accordingly if power supply is internal. The RF shield may be ulti<compartmental as required and may contain the EoC RF XCVRs 1620. 1.625 and tbe diplexers/combiners 161.0. The host switch 1640 may operate at 10 Mb/s, 100 Mb/s and 1000 Mb/s on the physical (PHY) layer, and may connect to the EoC basebands 1630, 1635.

[0083] Figure 1? is a diagram of an example four port L2 CPE PWB general layout In an example, mounting holes may be in same position as in the headend devices, if a P.EM Stud approach is used to affix the PWB to housing, The board dimensions may be the same as in the headend device. In an example, the board may rely on an external power supply. In another example, the layout may be adjusted accordingly if power supply is internal. The RF shield may contain the EoC RF XCVRs 1720 and the diplexers/combiners 17.10. The host switch 1740 may operate at 10 Mb/s, 100 Mb/s and 1000 Mb/s on the PHY layer, and may connect to the EoC baseband 1730.

[0084] Figure 18 is a diagram of an example two port L2 CPE PWB general layout In an example, mounting holes may be in same position as in the headend devices, if a PEM Stud approach is used to affix the PWB to housing. The board dimensions may be the same as in the headend device. In an example, the board may rely on an external brick power supply. In another example, the layout may be adjusted accordingly if power supply is internal. In a further example, if a PoE option is used, the board layout may be used for an L3 CPE. The RF shield may contain the EoC RF XCVRs 1820 and the diplexers/combiners 1810. The host switch 1840 may operate at 10 Mb/s, 100 Mb/s and 1000 Mb/s on the PHY layer, and may connect to the EoC baseband 1830.

[0085) Figure 19 is a diagram of an example of a headend network status screen. A headend network status screen may be shown as a dashboard screen, which may be the default page that appears when user logs in to the graphical user interface (GUI). The dashboard may indicate the current status of the Headend in terms of active connections (ETH1 1902, ETH2 1904), its network information 1910 and RF statue (RFIDl 1906. RFID2 1908). A connector status of green may be indicated when Ethernet port 1, ETH1 1902, or Ethernet port2, ETEI2 1904, is connected. The network information 1910 may include the MAC ID, IP Mode, IP Address, subnet mask, gateway and DNS. The RF status may apply for Link 1, RFIDl 1906, and Link 2. RFID2 1908. The RF status may indicate may indicate grey when links are disabled, red when links are down, green when links are up and orange when links are in an unknown state. Further, the dashboard may indicate the current firmware version of the GUI and the user type, such as admin.

[0086] Figure 20 is a diagram of an example of a headend port .settings screen. A user may navigate to the port settings screen by clicking Headend Network Configuration 2002 and then clicking Port. Setting 2005. In the port settings screen as shown in Figure 20, a user may manually configure uplink port flow control 2020, port speed 2030 (with, for example, 10 Mb/s, 100 Mbte and 1000 Mb/s options), duplex state 2040 and auto negotiation 2050. The default port speed is 1000 Mb/s. A user may click Reset Port 2060 to reset the port settings. When complete, the user may click Save 2070. In addition, the port status 2010 may indicate the current, port status (speed/duplex) for the Ethernet ports which are in active state.

[0087] Figure 21 is a diagram of an example RF settings screen. A user may click on Headend configuration 2102 and then has the option of choosing RF Settings 2104, CATV Configuration, IGMP Snooping, CPE VLAN, 802.1P- DSCP and Data Forwarding. If the user clicks on RF Settings 2104, the user navigates to the RF settings screen shown in Figure 21. The user also navigates to the RF settings screen by default after clicking on Headend configuration. At the RF settings screen shown in Figure 21, the user may enable or disable the EoC Channel RF State 2120. The user may also select the XC Frequency 2.1.30, which refers to the frequency selection for an internal RF switch to select the proper bandpass filter, as seen in Figure 10, The user may select the XC Frequency 2130 from a drop down box. In an example of operation in MoCA 1.1 mode, the user may select from values for 1000, 1150, 1325 and 1500 representing 1000 MHz, 1150 MHz, 1325 MHz and 1500 MHz, respectively. By default, Link I may operate at 1500 MHz and link 2 at 1000 MHz in MoCA 1.1 mode. In an example of operation in MoCA 2.0 mode, the user may select from values for 425, 625, 825, 1025, 1225, 1425 or 3625 representing 425 MHz, 625 MHZ, 825 MHz, 1.025 MHz, 1225 MHz, 1425 MHz or 1625 MHz, respectively. By default. Link 1 may operate at 425 MHz and Link 2 at 1625 MHz in MoCA 2.0 mode. The user may also enable or disable each link under White Listing 2140.

[0088] Also, the user may select the PHY Rate 2150 that each link will operate at. . In an example of operation in MoCA 1.1 mode, the user may select from values ranging from 0 through 235 Mb/s for the PHY rate. In an example of operation in MoCA 2.0 mode, the user may select from values ranging from 0 to 500 Mh/s for the PHY rate.

[0089] In addition, the user may select the Channel. Mask 2160 from a drop down box. The Channel Mask 2.160 refers to the frequency on which the RF is transmitted to the CPEs. In an example of operation in MoCA 1.1 mode, the user may select from values for 1000, 1150, 1325 and 1500 representing 1000 MHz, 1150 MHz, 1325 MHz and 1500 MHz, respectively. By default, Link 1 may operate at 1500 MHz and Link 2 at 3.000 MHz in MoCA 3.1 mode. In an example of operation in MoCA 2.0 mode, the user may select from values for 425, 625. 825, 1025, 1225, 1425 or 1625 representing 425 MHz, 625 MHZ, 825 MHz, 1025 MHz, 1225 MHz, 1425 MHz or 1625 MHz, respectively. By default, Link 1 may operate at 425 MHz and Link 2 at 1625 MHz in MoCA 2.0 mode,

[0090] Figure 22 is a diagram of an example CATV configuration screen. The user may navigate to this screen by clicking CATV configuration 2204 under Headend Configuration 2202. The user may adjust, upstream CATV frequency amplification ranging from -27 dB to 32 dB in steps of 1dB. The user may select, the Current Leνel 2220 of the Upstream Amplifier, which may be set from 0-3. The user may set the upstream Gain 2230, which may range from -27 dB to 32 dB. Further, the user may adjust downstream CATV frequency amplification ranging from -13.5 dB to 18 dB in steps of 0.5 dB. The user may set the downstream Gain 2250, which may range from -13.5 dB to 18 dB. When the user is ready, the user may click Save 2270 to save the changes.

[0091] Figure 23 is a diagram of an example 802.1P-DSCP value screen. The user may navigate to the 802.1 P-DSCP value screen by clicking 802.1 P- DSCP 2307 tinder Headend Configuration 2302. The differentiated services code point (DSCP) to 802.1p feature facilitates the insertion of a priority, ranging from 0-7, to the VLAN tag, based on the DSCP value of the Internet Protocol type of service (IPToS) in the packet arriving at an Ethernet port, which may be destined to be transmitted to the CPEs. The user may configure the DSCP value ranging from 0-63 to any of the priorities ranging from 0-7. The user may configure the DSCP value for each priority by clicking on the drop down boxes in the From column 2320 and To column 2330. In an example, a DSCP value already assigned for a priority may not be assigned for another priority-

[0092] Figure 24 is a diagram of an example firmware upgrade screen. The user may navigate to the firmware upgrade screen by clicking Firmware Upgrade 2412 under System Tools 2410. The user may also reach this screen by default after clicking System Tools 2410. The user may upgrade the firmware used by the headend by clicking on the Choose File button 2430 and selecting an upgrade file from a local system. The user may then click on an "UPLOAD FILE" button (not shown). The user may then view an "Upgrade" 2450 indication, showing that the upgrade was successful.

[0093] Figure 25 is a diagram of CPE configure screen. Using CPE management features, the user may manage and configure the CPE. The user may also add a CPE using this section. The CPE management section has four sub-sections: CPE Configure, Status, Loopback Detect and User MAC list. The user may navigate to the CPE configure screen by clicking CPE Configure 2512 under CPE Management 2510. This screen allows the user to add a CPE under a different. MoCA unit in Link 1 and Link 2. For example, the user may click Add 2560 to a CPE. Also, the user may enable or disable whitelisting of CPE by clicking the Whitelisting box 2520. Whitelisting of a CPE may be enabled/disabled only if the whitelisting is enabled in the headend. Clicking the Whitelisting box 2520 adds the CPE to the whitelist in the headend. A CPE may be deleted by clicking the delete box 2540.

[0094] Figure 26 is a diagram of a CPE RF settings screen, litis screen allows the user to Input the information about the CPE which the user may want to add under MoCA unit in link 1 or Link2, The user may reach this screen after clicking Add 2560 in Figure 25. The user may add the name 2620 of the CPE, MAC address 2630 of the CPE and may select the PHY rate 2650 for the CPE. The added CPE may be enabled or disabled via selecting the radio button under EoC Channel RFstate 2640. The user may configure the VLAN ID and its priority 2660 of the 4 available ports of the CPE. When ready, the user may click on the Save button 2670 to save the settings of the RF settings screen.

[0095] Figure 27 is a diagram of a CPE status screen. The user may navigate to the CPE status screen by clicking Statue 2714 under CPE Management 2710. This screen allows the user to check the statue of the CPE. The user may also reboot the CPE by clicking on the reboot button 2720 of the screen. The information which the user may view via this screen are as follows: CPE Name, MAC information, SW Version details and Uptime for the CPE. The details button 2730 available on this page enables user to view detailed information about a particular CPE.

[0096] Figure 28 is a diagram of a CPE details screen. The user may reach this screen after clicking the details button 2730 shown in Figure 27. In the CPE details screen, the user may view important information 2820 regarding the CPE such as; MoCA Unit, MAC Address, Link Status, MoCA Version, Network version, LOF, Phy Rate and statistics 2830 related to Rx and Tx packets.

[0097] Although examples, features and elements are described above in particular combinations, one of ordinary skill in the art will appreciate that each example, feature or element may be used alone or in any combination with the other examples, features and elements. In addition, the methods described herein may be implemented in a computer program, software, or firmware incorporated in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted over wired or wireless connections) and computer-readable storage media, such as non- transitory computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs).

* * *

Claims

CLAIMS What is claimed is:

1. A method for use in a headend communications device, the method comprising:

receiving, by the headend, an input gigabit Ethernet (GBE) signal over a GBE port;

determining, by the headend, to operate in a first mode or a second mode, wherein operating in the first mode complies with Multimedia over Coax Alliance (MoCA) 1.1 and operating in the second mode complies with MoCA 2.0;

converting, by the headend, the received input GBE signal to an output MoCA 1.1 compliant signal on a condition that operating in a first mode has been determined:

converting, by the headend, the received input GBE signal to an output MoCA 2.0 compliant signal on a condition that operating in a second mode has been determined;

transmitting, by the headend, the output MoCA 1.1 compliant signal on a condition that operating in a first mode has been determined;

transmitting, by the headend, the output MoCA 2.0 compliant signal on a condition that operating in a second mode has been determined;

receiving, by the headend, an input MoCA 1.1 compliant signal on a condition that operating in a first mode has been determined: and

receiving, by the headend, an input MoCA 2.0 compliant signal on a condition that operating in a second mode has been determined.

2. The method of claim 1 further comprising:

converting, by the headend, the received input MoCA 1.1 compliant signal to an output GBE signal on a condition that operating in a first mode has been determined;

converting, by the headend, the received input MoCA 2.0 compliant signal to an output GBE signal on a condition that operating in a second mode has been determined; and

transmitting, by the headend, the output GBE signal.

3. The method of claim 1 wherein the transmitted output MoCA 1.1 compliant signal is transmitted on one of 3.000 megahertz (MHz), 1150 MHz, 1325 MHz or 1500 MHz channels and the received input MoCA 1.1 compliant signal is received on one of the 1000 MHz, 1150 MHz, 1325 MHz or 1500 MHz channels.

4. The method of claim 1 wherein the transmitted output MoCA 2.0 compliant signal is transmitted on one of 425 MHz, 625 MHZ, 825 MHz, 1025 MHz. 1225 MHz, 1425 MHz or 1625 MHz channels and the received input MoCA 2.0 compliant signal is received on one of the 425 MHz, 625 MHZ, 825 MHz, 1025 MHz, 1225 MHz, 1425 MHz or 1625 MHz channels.

5. The method of claim 1 wherein the transmitted output MoCA 1.1 or MoCA 2.0 signals are transmitted via coaxial cable to a plurality of pieces of consumer premises equipment (CPE).

6. The method of claim I further comprising:

receiving, by the headend, an autosync signal from a CPE.

7. A headend communications device comprising:

a GBE port configured to receive an input gigabit Ethernet (GBE) signal;

a processor configured to determine to operate in a first mode or a second mode, wherein operating in the first mode complies with Multimedia over Coax Alliance (MoCA) 1.1 and operating in the second mode complies with MoCA 2.0;

the processor further configured to convert the received input GBE signal to an output MoCA 1.1 compliant signal on a condition that operating in a first mode has been determined;

the processor further configured to convert the received input GBE signal to an output MoCA 2.0 compliant signal on a condition that operating in a second mode has been determined;

an F-Conn configured to transmit the output MoCA 1.1 compliant signal on a condition that operating in a first mode has been determined; the F-Conn further configured to transmit the output MoCA 2.0 compliant signal on a condition that operating in a second mode has been determined;

the F-Conn further configured to receive an input MoCA 1.1 compliant signal on a condition that operating in a first mode has been determined; and the F-Conn further configured to receive an input MoCA 2.0 compliant signal on a condition that operating in a second mode has been determined.

8. The headend communications device of claim 7 further comprising:

the processor further configured, to convert the received input MoCA 1.1 compliant signal to an output GBE signal on a condition that operating in a first mode has been determined;

the processor further configured to convert the received input MoCA 2.0 compliant signal to an output GBE signal on a condition that operating in a second mode has been determined; and

the GBE port further configured to transmit the output GBE signal.

9. The headend communications device of claim 7 wherein the transmitted output MoCA 1.1 compliant signal is transmitted on one of 1000 megahertz (MHz), 1150 MHz, 1325 MHz or 1500 MHz channels and the received input MoCA. 1.1 compliant signal is received on one of the 1000 MHz, 1150 MHz, 1325 MHz or 1500 MHz channels.

10. The headend communications device of claim 7 the transmitted output MoCA 2.0 compliant signal is transmitted on one of 425 MHz. 625 MHZ, 820 MHz, 1025 MHz, 1225 MHz, .1425 MHz or 1625 MHz channels and the received input MoCA 2.0 compliant signal is received on one of the 425 MHz. 625 MHZ, 825 MHz, 1025 MHz, 1225 MHz, 1425 MHz or 1625 MHz channels.

11. The headend communications device of claim 7 wherein the transmitted output MoCA 1.1 or MoCA 2.0 signals are transmitted via coaxial cable to a plurality of pieces of consumer premises equipment (CPE).

12. The headend communications device of claim 7 further comprising:

the F-Conn further configured to receive an autosync signal from a CPE.

13. A method for use in a consumer premises equipment (CPE) device, the method comprising:

determining, by the CPE, to operate in a first mode or a second mode, wherein operating in the first mode complies with Multimedia over Coax Alliance (MoCA) 1.1 and operating in the second mode complies with MoCA 2.0;

receiving, by the CPE, an input MoCA 1.1 compliant signal on a condition that operating in a first mode has been determined; receiving, by the CPE, an input MoCA 2.0 compliant signal on a condition that operating in a second mode has been determined:

converting, by the CPE, the input MoCA 1.1 compliant signal to an output Ethernet signal on a condition that operating in a first mode has been determined:

converting, by the CPE, the input MoCA 2.0 compliant signal to an ouput Ethernet signal on a condition that operating in a second mode has been determined;

transmitting, by the CPE, the output Ethernet signal; and

receiving, by the CPE, an input Ethernet signal.

14 , The method of claim 13 further comprising:

converting, by the CPE, the input Ethernet signal to an output MoCA 1.1 compliant signal on a condition that operating in a first mode has been determined;

converting, by the CPE, the input Ethernet signal to an output MoCA 2.0 compliant signal on a condition that operating in a second mode has been determined;

transmitting, by the CPE, the output MoCA 1.1 compliant signal on a condition that operating in a first mode has been determined; and

transmitting, by the CPE, the output MoCA 2.0 compliant signal on a condition that operating in a second mode has been determined.

15. The method of claim 13 wherein the received input MoCA 1.1 compliant signal is received on one of 1000 MHz, 1150 MHz. 1325 MHz or 1500 MHz channels.

16. The method of claim 13 wherein the received input MoCA 2.0 compliant signal is received on one of 425 MHz, 625 MHZ, 825 MHz, 1025 MHz, 1225 MHz, 1425 MHz or 1625 MHz channels.

17. The method of claim .13 wherein the received MoCA 1.1 or MoCA 2.0 signals are received via coaxial cable.

18. The method of claim 13 further comprising:

determining, by the CPE, to autosync with a headend, and

transmitting, by the CPE, an autosync signal to the headend.

19. A consumer premises equipment (CPE) device comprising:

a processor configured to determine to operate in a first mode or a second mode, wherein operating in the first mode complies with Multimedia over Coax Alliance (MoCA) 1.1 and operating in the second mode complies with. MoCA 2.0;

a. F-Conn configured to receive an input MoCA 1.1. compliant signal on a condition that, operating in a first mode has been determined;

an F-Conn configured to receive an input MoCA 2.0 compliant signal on a condition that operating in a second mode has been determined; the processor further configured to convert the input MoCA 1.1 compliant signal to an output Ethernet signal on a condition that operating in a first mode has been determined;

the processor further configured to convert the input MoCA 2.0 compliant signal to an ouput Ethernet signal on a condition that operating in a second mode has been determined;

an Ethernet port configured to transmit the output Ethernet signal; and the Ethernet port further configured to receive an input Ethernet signal.

20. The CPE device of claim 19 further comprising:

the processor further configured to convert the input Ethernet signal to an output MoCA 1.1 compliant signal on a condition that operating in a first mode has been determined;

the processor further configured to convert the input Ethernet signal to an output MoCA 2.0 compliant signal on a condition that operating in a second mode has been determined;

the F-Conn further configured to transmit the output MoCA 1.1 compliant signal on a condition that operating in a first mode has been determined; and

the F-Conn further configured to transmit the output MoCA 2.0 compliant signal on a condition that operating in a second mode has been determined.

21. The CPE device of claim 19 wherein the received input MoCA 1.1 compliant signal is received on one of 1000 MHz, 1150 MHz. 1325 MHz or 1500 MHz channels.

22. The CPE device of claim 19 wherein the received input MoCA 2.0 compliant, signal is received on one of 425 MHz, 625 MHZ, 825 MHz, 1025 MHz, 1225 MHz, 1425 MHz or 1625 MHz channels.

23. The CPE device of claim 19 wherein the received MoCA 1.1 or MoCA 2.0 signals are received via coaxial cable.

24. The CPE device of claim .19 further comprising:

the processor further configured to determine to autosync with a headend, and

the F-Conn further configured to transmit an autosync signal to the headend.