Analog hpna hub and network including anaolg hpna hub

The disclosed technique relates to communication networks in general, and to MxU network architectures, in particular.

BACKGROUND OF THE DISCLOSED TECHNIQUE

MxU networking architecture is known in the art and is used to provide communication services to a site (e.g., an apartment building) which includes a plurality of substantially independent sections (e.g., a plurality of apartments), each associated with a different subscriber. In general, the MxU networking architecture defines a separate local area network (LAN) for each of the sections.

MxU networks which are based Home Phoneline Networking Alliance (HPNA), use the telephone lines of the telephone wire network, already installed in the MxU. Each of the LANs includes the telephone wires which are associated with a selected section (e.g., apartment) and a plurality of HPNA nodes coupled with the telephone outlets. Telephone network voice communication and data communication services can be used simultaneously, using a technique known as frequency division multiplexing (FDM). Accordingly, data signals are transmitted using a different (higher) frequency than voice data signals, whereby these signals, can be separated using a frequency splitter.

Reference is now made to Figure 1, which is a schematic illustration of an apartment building network, generally referenced 10, which is known in the art. It is noted that Figure 1 is not drawn to scale.

Apartment building network 10 includes intra-apartment networks APT₁ (referenced 120, ^APT2 (referenced 12₂) and APT_N(referenced 12_N), and gateways G! (referenced 22^, G₂ (referenced 222) and G_N (referenced 22n). Gateways 22-!, 22₂ and 22n are mounted on a

002167ILD1 platform 16. A broadband source 20 couples each of gateways 22!, 22₂ and 22_n with a wide area network (WAN) such as the Internet, via a broadband link such as xDSL, cable, fiber-optic, satellite, Local Multipoint

Distribution System (LMDS), and the like.

Each of intra-apartment networks 12!, 12₂ and 12_N includes several network nodes (not shown). Each one of gateways 22-!, 22₂ and 22_n is coupled with a respective one of intra-apartment networks 121, 12₂and 1 2_n, via respective telephone wires 14-!, 14₂ and 14_N. Each one of the gateways 22₁22₂_ז and 22_N, and a respective one of intra-apartment networks 12!, 12₂ and 12_N, together form a respective one of local-area networks (LAN) 14.!, 14₂ and 14_N. Each of LANs 14₁14₂_ז and 14_N is further coupled with telephone service lines 24!, 24₂ and 24_N, respectively.

Reference is now made to Figure 2A and 2B. Figures 2A and 2B schematically illustrate an apartment building network, generally referenced 40, which is known in the art. Figures 2A and 2B show a first and second example of NEXT in an MxU network, respectively. It is noted that Figures 2A and 2B are not drawn to scale.

With reference to Figure 2A, apartment building network 40 includes intra-apartment networks APT! (referenced 42!), APT₂(referenced 42₂) and APT_N (referenced 42_N), gateways G! (referenced 521), G2 (referenced 52₂) and G_N (referenced 52_N), and phone wires 54!, 54₂ and 54_N. A wire binder 48 runs from a basement 44 of the apartment building, to the vicinity of intra-apartment networks 42!, 42₂ and 42_N. A platform 46 is located in basement 44. Gateways 52!, 52₂ and 52_N are mounted on platform 46. A broadband source 50 couples each of gateways 52!, 52₂ and 52_N with a WAN such as the Internet, via a broadband link such as xDSL, cable, fiber-optic, satellite, Local Multipoint Distribution System (LMDS), and the like.

Each of intra-apartment networks 42!, 42₂ and 42_N includes several network nodes (not shown), as shall be described in further detail with reference to Figure 2C. Each one of gateways 52!, 52₂ and 52_N is -2002167ILD1 coupled with a respective one of intra-apartment networks 42!, 42₂ and 42_n, via respective phone wires 54!, 54₂ and 54_N. Each combination of one of the gateways 52!, 52₂ and 52_N, the respective one of phone wires 54!, 54₂ and 54_N, and the respective one of intra-apartment networks 42-!, 42₂and 42_n, together form a respective one of local-area networks (LANs) 45!, 45₂ and 45_N. Phone wires 54!, 54₂ and 54_N are bound together in binder 48.

Gateway 52! transmits a data signal 56 to intra-apartment network 42!. Simultaneously, intra-apartment network 42₂ transmits another data signal 58 to gateway 52₂. In a region 62, located in the vicinity of platform 46, an electrical disturbance 60, associated with data signal 56 (from phone wire 54!), is induced in phone wire 54₂, causing an interference in data signal 58.

It is noted that conventionally, the distance between intra-apartment network 42₂ and region 62 is significantly greater than the distance between gateway 52! and region 62. Therefore, data signal 58 undergoes a significantly greater attenuation than data signal 56, before these data signals reach region 62, and hence, electrical disturbance 60 may cause a significant interference in data signal 58. This effect is known as near-end crosstalk (NEXT). It is noted that the transfer of disturbance 60 from phone wire 54! to phone wire 54₂ is a cumulative effect, which takes place all along phone wires 54! and 54₂, with a primary contribution occurring in region 62.

With reference to Figure 2B, gateway 52! transmits a data signal 70 to intra-apartment network 42!. Simultaneously, intra-apartment network 42₂ transmits another data signal 72 to gateway 52₂. In a region 76, located in the vicinity of intra-apartment networks 42! and 42₂, an electrical disturbance 74, associated with data signal 72 (from phone wire 54₂), is induced in phone wire 54!, causing an interference in data signal 70.

ILD1

It is noted that conventionally, the distance between gateway 52_דand region 76 is significantly greater than the distance between intra-apartment network 42! and region 76. Therefore, data signal 70 undergoes a significantly greater attenuation than data signal 72, before these data signals reach region 76, and hence, electrical disturbance 74 may cause a significant interference in data signal 70.

Reference is further made to Figure 2C, which is an illustration in detail of intra-apartment networks 42! and 42₂ of apartment building network 40 (Figures 2A and 2B) and a portion of the binder 48. Figure 2C shows a third example of NEXT in an MxU network. It is noted that Figure 2C is not drawn to scale.

Intra-apartment network 42! includes network nodes 80!, 80₂and 8Ο3. Nodes 80!, 80₂ and 80₃ are coupled there between via phone wire 54!. Intra-apartment network 42₂ includes nodes 82! and 82₂. Nodes 82! and 82₂ are coupled there between via phone wire 54₂.

Gateway 52₂ (Figure 2A) transmits a data signal 86, through phone wire 54₂, toward intra-apartment network 42₂. Simultaneously, node 80! transmits another data signal 88 toward node 80₂.

It is noted that conventionally, data signal 88 includes a header with source and target attributes. All of the nodes of LAN 45! (Figure 2A) receive data signal 88, but only the target node, which is specified in the source-target attributes (i.e., node 80₂) addresses and decodes the data signal. It is noted that in the description that follows and the accompanying drawings, except for the present example, data signals are only shown on their path to their intended receiving node.

Data signal 88 passes through phone wire 54! toward binder 48. In a region 84 in the vicinity of intra-apartment networks 42! and 42₂, an electrical disturbance 92, associated with data signal 88 (from phone wire 54!), is induced in phone wire 54₂, causing an interference in data signal 86. Similarly as in the example set forth in Figures 2A and 2B, electrical disturbance 92 may cause a significant interference in data signal 86.

ILD1

SUMMARY OF THE DISCLOSED TECHNIQUE

It is an object of the disclosed technique to provide a novel

HPNA MxU hub, which is operative to share and exchange network resources, and which overcomes the disadvantages of the prior art.

In accordance with the disclosed technique, there is thus provided an analog HPNA hub including at least one group of coils. Each group of coils includes a plurality of coils, inducing HPNA signals there between. The analog HPNA hub further includes a plurality of filters. Each of the filters is coupled with a respective one of the coils, and further coupled, via respective telephone wiring, with at least a respective HPNA node. Each of the filters enables transmission of HPNA data signals there through, and prevents transmission of conventional telephony signals there through.

In accordance with another aspect of the disclosed technique, there is provided an HPNA network, the network including at least one analog HPNA hub, and at least one group of HPNA nodes. Each group is associated with a respective one of the analog HPNA hubs. Each analog HPNA hub includes a plurality of coils, for inducing HPNA signals there between. Each analog HPNA hub further includes a plurality of filters. Each filter is coupled with a respective one of the coils, and further coupled, via respective telephone wiring, with at least an HPNA node in the respective group. Each of the filters enables transmission of HPNA data signals there through, and prevents transmission of conventional telephony signals there through.

ILD1

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosed technique will be understood and appreciated more fully from the following detailed description taken in conjunction with the drawings in which:

Figure 1 is a schematic illustration of an apartment building network, which is known in the art;

Figure 2A is a schematic illustration of an apartment building network which is known in the art, showing a first example of NEXT in an Mxll network;

Figure 2B is a schematic illustration of the apartment building network of Figure 2A, showing a second example of NEXT in an MxU network;

Figure 2C is an illustration in detail of two of the intra-apartment networks of the apartment building of Figures 2A and 2B and a portion of the binder, showing a third example of NEXT in an MxU network;

Figure 3 is a schematic illustration of an MxU network, constructed and operative in accordance with an embodiment of the disclosed technique;

Figure 4 is a schematic illustration of an apartment building network, constructed and operative in accordance with another embodiment of the disclosed technique;

Figure 5 is a schematic illustration of an apartment building network, constructed and operative in accordance with a further embodiment of the disclosed technique;

Figure 6A is a schematic illustration of a timeslot scheme sequence, constructed in accordance with another embodiment of the disclosed technique;

Figure 6B is a schematic illustration of a timeslot scheme sequence, constructed in accordance with a further embodiment of the disclosed technique;

ILD1

Figure 6C is a schematic illustration of a timeslot scheme sequence, constructed in accordance with another embodiment of the disclosed technique;

Figure 7A is an illustration in detail of two of the intra-apartment networks of the MxU network of Figure 3, and a portion of the binder, operating during a downstream timeslot, in accordance with a further embodiment of the disclosed technique;

Figure 7B is an illustration in detail of two of the intra-apartment networks of the MxU Figure 3, and a portion of the binder, operating during an upstream+HN timeslot, in accordance with another embodiment of the disclosed technique;

Figure 7C is an illustration in detail of two of the intra-apartment networks of the MxU Figure 3, and a portion of the binder, operating during an miscellaneous timeslot, in accordance with a further embodiment of the disclosed technique, and

Figure 8 is a schematic illustration of a method for reducing NEXT in an MxU network, operative in accordance with another embodiment of the disclosed technique;

Figure 9 is a schematic illustration of an MxU network, constructed and operative in accordance with a further embodiment of the disclosed technique;

Figure 10 is an illustration in detail of the analog HPNA hub and a plurality of phone wires of Figure 9;

Figure 11 is a schematic illustration of an analog HPNA hub, constructed and operative in accordance with another embodiment of the disclosed technique, and a plurality of phone wires;

Figure 12 is a schematic illustration of an analog HPNA hub, constructed and operative in accordance with a further embodiment of the disclosed technique, and a plurality of phone wires;

ILD1

Figure 13 is a schematic illustration of an apartment building network, constructed and operative in accordance with another embodiment of the disclosed technique; and

Figure 14 is a schematic illustration of a network, constructed 5 and operative in accordance with a further embodiment of the disclosed technique.

ILD1

DETAILED DESCRIPTION OF THE EMBODIMENTS

The disclosed technique overcomes the disadvantages of the prior art by providing a novel analog HPNA hub for an MxU network, which enables data signal transmissions between different HPNA local (i.e., intra-apartment) networks of the MxU network to pass there through, while preventing conventional telephony transmissions between the HPNA local networks, from passing there through.

In the description that follows, the terms MDU (multi-dwelling unit), MTU (multi-tenant unit), MCU (multi-company unit), MHU (multihospitality unit), MPU (multi-public unit), MEU (multi-embedded unit), are generally termed MxU. An MxU may be an apartment building, a condominium complex, a hotel, a motel, a resort, an office building, an industrial park, a college or university campus dormitory, a hospital, an airport, a train station, a convention center, a shopping mall, an airplane, a ship, and the like.

Reference is now made to Figure 3, which is a schematic illustration of an MxU network, generally referenced 100, constructed and operative in accordance with an embodiment of the disclosed technique. It is noted that Figure 3 is not drawn to scale. In the present example, MxU network 100 is an apartment building network. It is noted, however, that the disclosed technique is applicable for any type of MxU network.

In the description that follows, the term phone wire is defined as a line which can be used for communicating conventional telephony signals and HPNA signals. A phone wire can be constructed by twisting together two insulated copper wires.

Apartment building network 100 includes intra-apartment networks APT₁ (referenced 112!), APT₂ (referenced 112₂) and APT_N(referenced 112_N), gateways G! (referenced 122!), G₂ (referenced 122₂) and G_n (referenced 122_N), and phone wires 124₁124₂_י and 124_N. A wire binder 118 runs from a basement 114 of the apartment building, to the vicinity of intra-apartment networks 112!, 112₂ and 112_N. A platform 116 -9002167ILD1 and a synchronizer 126 are located in communication room 114. Gateways G1, G₂, and G_N, referenced 122!, 122₂ and 122_N, respectively, are mounted on platform 116. A broadband source 120 couples gateways 122₁122₂_ז and 122_N with a wide area network (WAN) such as xDSL, cable, fiber-optic, satellite, Local Multipoint Distribution System (LMDS), and the like. Synchronizer 126 is coupled with gateways 122₁122₂_י and 122_N.

In the present example, communication room 114 is a basement. It is noted, however, that the communication room 114 may be any physical space housing the gateways of the network, such as a basement, a cupboard, a cabinet, and the like. Phone wires 124-!, 124₂and 124_n are bound together in binder 118.

Platform 116 provides access to gateways 122122₂ ,!־ and 122_N, by multiplexing the broadband source 120. It is noted that platform 116 may further provide other functions to gateways 122-!, 122₂ and 122_N, such as routing, switching, dynamic IP address assignment, voice access, power, and the like. For example, platform 116 may be a Digital Subscriber Line Access Multiplexer (DSLAM), a Next Generation Digital Loop Carrier (NGDLC), and the like.

Each of intra-apartment networks 112!, 112₂ and 112_N includes several network nodes (not shown), as shall be described in further detail with reference to Figures 7A and 7B. Each combination of one of the gateways 122₁122₂_ז and 122_N, the respective one of phone wires 124!, 124₂ and 124_N, and the respective one of intra-apartment networks 112!, 112₂ and 112_N, together form a respective one of local-area networks (LANs) 115!, 1152 and 115_N.

Data signals transmitted from one of the gateways 122!, 122₂ or 122_n, to the respective intra-apartment network, are known as downstream data signals. Data signals transmitted from one of the intra-apartment networks 112!, 112₂ and 112_N, to the respective gateway, are known as upstream data signals. Data signals transmitted and -10002167ILD1 received within one of the intra-apartment networks, are known as home networking (HN) data signals.

Each of gateways 122!, 122₂ and 122_N operates as a master node of the respective one of LANs 115!, 115₂ and 115_N (i.e., each gateway is a LAN-master). In other words, each gateway enables or disables all of the nodes in the respective LAN to transmit data signals. Synchronizer 126 synchronizes all of the gateways 122!, 122₂ and 122_N, so that all of the LANs 115!, 115₂ and 115_N, transmit upstream, downstream and HN data signals in synchrony, as shall be described in further detail with reference to Figures 6A and 6B.

It is noted that synchronizer 126 may generally be coupled with gateways 122!, 122₂ and 122_N via wired or wireless connections. It is further noted that synchronizer 126 may generally be located in various locations inside or outside of basement 114, and inside the apartment building or at a remote location.

Reference is now made to Figure 4, which is a schematic illustration of an apartment building network, generally referenced 140, constructed and operative in accordance with another embodiment of the disclosed technique. According to the architecture of network 140, the synchronizer is incorporated within one of the LAN-masters, whereby this LAN-master operates as a master relative to the other LAN-masters of the network.

Apartment building network 140 includes intra-apartment networks APT! (referenced 152!), APT₂ (referenced 152₂) and APT_N(referenced 152_N), gateways G! (referenced 162!), G₂ (referenced 162₂) and G_n (referenced 162_N), and phone wire 164!, 164₂ and 164_N. A wire binder 158 runs from a basement 154 to the vicinity of intra-apartment networks 152!, 152₂ and 152₃. Gateways 162!, 162₂ and 162_N are mounted on a platform 156. A broadband source 160 couples gateways 162!, 162₂ and 162_N with a WAN. The combinations of intra-apartment networks 152!, 152₂ and 152₃, phone wires 164!, 164₂ and 164_N and -11002167ILD1 gateways 162!, 162₂ and 162_N form LANs 155!, 155₂ and 155_N, similarly as in apartment building network 100 of Figure 3.

Gateways 162!, 162₂ and 162_N are coupled there between via a synchronicity link 166. It is noted that synchronicity link 166 may be wired or wireless. Gateway 162! operates as a master gateway to the rest of the gateways, which operate as slave gateways (i.e., gateway 162! controls when the other gateways, and the nodes of their respective LANs, transmit data signals). Gateway 162! synchronizes all of the LANs to transmit upstream, downstream and HN data signals in synchrony, as shall be described in further detail with reference to Figures 6A and 6B.

Reference is now made to Figure 5, which is a schematic illustration of an apartment building network, constructed and operative in accordance with a further embodiment of the disclosed technique. Apartment building network 170 includes intra-apartment networks APT! (referenced 152!), APT₂ (referenced 152₂) and APT_N (referenced 152_N), gateways G! (referenced 162!), G₂ (referenced 162₂) and G_N (referenced 1 62_n), and phone wires 164!, 164₂ and 164_N. A wire binder 188 runs from a basement 174 to the vicinity of intra-apartment networks 182!, 182₂ and 182₃. Gateways 192!, 192₂ and 192_N are mounted on a platform 186. A broadband source 190 couples gateways 192!, 192₂ and 192_N with a WAN. The combinations of intra-apartment networks 182!, 182₂ and 182₃, phone wires 184!, 184₂ and 184_N and gateways 192!, 192₂ and 192_N form LANs 185!, 1852 arid 185_N, similarly as in apartment building network 100 of Figure 3. However, gateway 192! does not operate as the master node of LAN 185!. Rather, a node 194 of intra-apartment network 182! is the LAN-master node of LAN 185!.

LAN-master node 194 and gateways 192₂ and 192_N are coupled there between via a synchronicity link 196. Gateway 192_N operates as a master gateway to the rest of the LANs, similarly as gateway 162!. However, gateway 192_N synchronizes LAN 185! through LAN-master node 194 (and not through gateway 192!).

ILD1

It is noted that alternatively, LAN-master node 194 may be linked directly to master gateway 192_N. Further alternatively, a synchronizer such as synchronizer 126 of Figure 3, may be applied to an apartment building network similar to apartment building network 170. Accordingly, LAN-master 194 is coupled to that synchronizer. It is further noted that the disclosed technique may similarly be applied to an MxU network wherein a plurality of LAN-master nodes are not gateways.

Reference is now made to Figure 6A, which is a schematic illustration of a timeslot scheme sequence 200, constructed in accordance with another embodiment of the disclosed technique. Sequence 200 includes cyclic timeslot schemes, of which two schemes 202 and 206 are shown. Timeslot scheme 202 includes timeslots 204! and 204₂. Timeslot scheme 206 includes timeslots 208! and 208₂. Timeslots 204! and 208! are allocated for downstream communication. Timeslots 204₂ and 208₂ are allocated for upstream communication and HN communication.

In the example set forth in Figure 3, synchronizer 126 instructs gateways 122!, 122₂ and 122_N and the nodes of their respective LANs that timeslots 204! and 208! are allocated for downstream communication only. Accordingly, only gateways 122!, 122₂ and 122_N shall be able to transmit signals within their respective LANs 115!, 115₂ and 115_N, during timeslots 2041 and 208!. Synchronizer 126 further instructs gateways 122!, 122₂and 1 22_n and the nodes of their respective LANs, that timeslots 204₂ and 208₂ are allocated for upstream and HN communication only. Accordingly, only the nodes of intra-apartment networks 112!, 112₂ and 112_N shall be able to transmit signals within their respective LANs 115!, 115₂ and 115_N, during timeslots 204₂ and 208₂.

For example, synchronizer 126 of Figure 3 may include a clock (also known as a sync clock), which is coupled with all of the LAN-master nodes. The LAN-master nodes transmit data only during a certain part of the clock cycle (e.g., during the high level period of the cycle). Thus, the

ILD1

LAN-master nodes are synchronized with the clock, and hence are synchronized there between.

It is noted that the timeslot scheme may be determined dynamically. Accordingly, the timeslot scheme may change according to the conditions present in MxU network 100, such as the bandwidth used by each network node or LAN, the amount of upstream, downstream and HN communication, and the like. It is further noted that various other timeslot schemes may be employed, such as a timeslot scheme allocating separate timeslot for each LAN or group of LANs, a timeslot scheme involving only those LANs found interfering, and the like.

Reference is now made to Figure 6B, which is a schematic illustration of a timeslot scheme sequence 210, constructed in accordance with a further embodiment of the disclosed technique. Sequence 210 includes repeating timeslot schemes, of which two schemes 212 and 216 are shown. Timeslot scheme 212 includes timeslots 214!, 214₂ and 214₃. Timeslot scheme 216 includes timeslots 218!, 218₂ and 218₃. Timeslots 214! and 218! are allocated for downstream communication. Timeslots 2142 and 2182 are allocated for upstream communication and HN communication (also referred to as upstream+HN). Timeslots 214₃ and 218₃ are allocated for other communication.

In the example set forth in Figure 3, during timeslots 214₃ and 218₃, synchronizer 126 instructs gateways 122!, 122₂ and 122_N and the nodes of their respective LANs, not to generate upstream, downstream, or HN data signals. For example, timeslot 214₃ may be used for communication through the network, using a different communication specification, as shall be described with reference to Figure 7C.

Reference is now made to Figure 6C, which is a schematic illustration of a timeslot scheme sequence 220, constructed in accordance with another embodiment of the disclosed technique. Scheme sequence 220 includes timeslots 222 and 224. Timeslot 222 includes transmission /2 opportunity (TXOP) 225 and gap 226. Timeslot 224 includes TXOPs 227!,

2272 and 227₃, and gap 228.

Timeslot 222 is similar to timeslot 204! of Figure 6A, allocated for downstream communication. Timeslot 224 is similar to timeslot 204₂(Figure 6A), allocated for upstream+HN communication. TXOP 225 is allocated for the transmission of a specific data packet or packets, in the downstream direction. Gap 226 separates between TXOP 225 and TXOP 227!. Each of TXOP 227!, 227₂ and 227₃ is allocated for specific upstream or HN transmission, such as a specific data stream or a specific network node or group of nodes. Gap 228 separates between TXOP 227₃ and the next timeslot scheme (i.e., the next cycle). It is noted that a system according to the disclosed technique may generally operate using different types of TXOPs and gaps, such as those described in US Patent application publication no. 2003/0198246, which is hereby incorporated by reference.

Reference is now made to Figure 7A, 7B and 7C. Figure 7A is an illustration in detail of intra-apartment networks 112! and 112₂ of Figure 3, and a portion ofthe binder 118, operating during a downstream timeslot such as timeslot 204! of Figure 6A, in accordance with a further embodiment of the disclosed technique. Figure 7B is an illustration in detail of intra-apartment networks 112! and 112₂ of Figure 3, and a portion of the binder 118, operating during an upstream+HN timeslot such as timeslot 204₂ of Figure 6A, in accordance with another embodiment of the disclosed technique. Figure 7C is an illustration in detail of intra-apartment networks 112! and 112₂ of Figure 3, and a portion of the binder 118, operating during an miscellaneous timeslot such as timeslot 214₃ of Figure 6B, in accordance with a further embodiment of the disclosed technique. Intra-apartment network 112! includes network nodes 230!, 230₂ and 230₃. Intra-apartment network 112₂ includes network nodes 232!, 232₂, 232₃ and 232₄. Nodes 232!, 232₂, 232₃ and 232₄ are coupled there between via phone wire 124₂. It is noted intra-apartment networks 112!

/2 and 1122 may further include various other elements, such as additional nodes and wires, switches, and the like.

Each of network nodes 230!, 230₂, 230₃, 232!, 232₂, 232₃ and 232₄ may be any point in the network which can transmit and receive data, such as a computer, a printer, an intercom, a digital telephone, an electrical appliance, and the like. Nodes 230!, 230₂, 230₃, 232₂, and 232₃transmit and receive data according to a single, synchronous, predetermined first communication specification, such as HPNA3. Nodes 230!, 230₂, 2303, 232₂, and 232₃ may operate according to a synchronous Media Access Control (MAC) as described in the above mentioned US Patent application publication no. 2003/0198246.

Node 2324 transmits and receives data according to a second communication specification, such as HPNA2. It is noted that the second communication specification may be either synchronous or asynchronous. Node 232! is capable of transmitting and receiving data signals of both the first and the second communication specification.

With reference to Figure 7A, gateway 122! transmits a data signal 234 through phone wire 124!, toward node 230₃ of intra-apartment network 112!. Simultaneously, gateway 122₂ transmits another data signal 236 toward node 232₂ of intra-apartment network 112₂.

With reference to Figure 7B, node 230! of intra-apartment network 112! transmits a first data signal 250 through phone wire 124!, toward node 230₂. Node 230₃ of intra-apartment network 112! transmits a second data signal 252 through phone wire 124!, toward gateway 122!. Node 232₂ of intra-apartment network 112₂ transmits a third data signal 254 through phone wire 124₂, toward node 232₃. Node 232₂ of intra-apartment network 112₂ transmits a fourth data signal 256 through phone wire 124₂, toward gateway 122₂. Data signals 250 and 252 are transmitted synchronously, within LAN 115! (Figure 3), during at least one upstream+HN timeslot. Similarly, data signals 254 and 256 are transmitted synchronously, within LAN 115₂ (Figure 3), during at least one

ILD1 upstream+HN timeslot. With reference to Figure 7C, network node 232₄ transmits a data signal 270 through phone wire 124₂ to network node 232!.

It is noted that synchronizer 126 (Figure 3) may restrict network node 232! to transmit only during the miscellaneous timeslot, by creating conditions in network 100, which enable network node 232! to transmit data signals only during the miscellaneous timeslot. For example, HPNA2 legacy units (i.e., nodes operating solely according to an older communication specification, and not according to later communication specification such as HPNA3 units), detect the various properties of the network (e.g., voltage, current, frequency spectrum) in order to determine if other nodes are transmitting. An HPNA2 node can transmit signals when it detects that no HPNA signal is being transmitted on the communication line. Hence, either the synchronizer (when directly coupled with the LANs) or the LAN-master nodes, can apply the appropriate signals on the network to prevent legacy units transmitting, during the downstream timeslots and the upstream+HN timeslots. Similarly, during the miscellaneous timeslot, either the synchronizer or the LAN-master nodes, can instruct all of the advanced (non-legacy) nodes, not to produce HPNA signals on the communication line, thereby allowing legacy units to transmit.

Reference is now made to Figure 8, which is a schematic illustration of a method for reducing NEXT in an MxU network, operative in accordance with another embodiment of the disclosed technique. In procedure 300, a timeslot scheme is defined. The timeslot scheme includes a plurality of timeslots, each being allocated for a selected type of signal transmission (i.e., upstream, downstream, HN, miscellaneous, or a certain combination thereof). In the example set forth in Figures 3, 6A and 6B, a timeslot scheme such as 204! or 214! is either embedded in synchronizer 116 or defined in real-time thereby. It is noted that alternatively, other sources may define the timeslot scheme, such as a node of MxU network 100, an external node of the WAN, a user of MxU -17002167ILD1 network 100, and the like. In the example set forth in Figure 6A, timeslot

204! is allocated for downstream transmission, and timeslot 204₂ is allocated for upstream and HN transmission.

In procedure 302, MxU LAN-masters are synchronized according to the timeslot scheme. The synchronization causes all of the nodes in each of the LANs to operate as defined in the timeslot scheme. With reference to Figure 3, synchronizer 116 instructs each one of the LAN-master nodes of MxU network 100 to regulate their respective LANs according to the selected timeslot scheme. Accordingly, gateways 122_1י122₂ and 122_N are allowed to transmit upstream signals only during timeslot 204.!. Similarly, the nodes of intra-apartment networks 112.!, 112₂and 112_n are allowed to transmit upstream+HN signals only during timeslot 204₂.

In procedure 304, signals of a selected type are transmitted, during each of the respective timeslots. With reference to Figure 3, gateways 122.!, 122₂ and 122_N transmit upstream signals only during timeslot 204! and the nodes of intra-apartment networks 112!, 112₂ and 112_n transmit upstream+HN signals only during timeslot 204₂. It is noted that procedure 304 is applied repetitively.

In procedure 306, conditions on the network are controlled, thereby enabling transmission of data signals of special types, such as legacy communication signals. In the example set forth in Figures 3 and 5B, synchronizer 126 produces no HPNA signals on the MxU network, during the downstream and upstream+HN timeslots, and an appropriate HPNA signal during miscellaneous timeslot 214₃. The HPNA signal indicates to legacy units that they are not allowed to transmit, as long as they detect it.

It is noted that procedure 306 is optional, and may be omitted in certain networks. For example, in a network comprising solely of nodes operating according to a single communication specification (i.e., non-legacy nodes), there may be no need to control the conditions on the -18002167ILD1 network. It is noted that when applying procedure 306, it has to be integrated with procedure 304, so that both procedures are provided simultaneously. Timeslot scheme 212 (Figure 6B) is an example for integrating both procedures 304 and 306.

Reference is now made to Figure 9, which is a schematic illustration of an MxU network, generally referenced 400, constructed and operative in accordance with a further embodiment of the disclosed technique. It is noted that Figure 9 is not drawn to scale. In the present example, MxU network 400 is an apartment building network. It is noted, however, that the disclosed technique is applicable for any type of MxU network.

Apartment building network 400 includes intra-apartment networks APT! (referenced 406!), APT₂ (referenced 406₂) and APT_N(referenced 406_N), a gateway 402, and an analog HPNA hub 404. Each of intra-apartment networks 406!, 406₂ and 406_N includes a plurality of network nodes (not shown). A broadband source 412 couples gateway 402 with a wide area network (WAN) such as the Internet, via a broadband link such as xDSL, cable, fiber-optic, satellite, Local Multipoint Distribution System (LMDS), and the like. Analog HPNA hub 404 is coupled with intra-apartment networks 406!, 406₂ and 406_N, through phone wires 408!, 408₂ and 408_N, respectively. Analog HPNA hub 404 is further coupled with gateway 402. Analog HPNA hub 404 enables data signal transmissions between intra-apartment networks 406!, 406₂ and 406_N, to pass there through. Thus, gateway 402 and intra-apartment networks 406!, 406₂ and 406_n together form a local-area network (LAN).

Analog HPNA hub 404 is further coupled with external telephone lines 410!, 410₂ and 410_N. External telephone lines 410!, 410₂ and 410_Nprovide the intra-apartment networks 406!, 406₂ and 406_N, respectively, with conventional telephony service. External telephone lines 410!, 410₂and 410_N couple network 400 with a telephony exchange system such as /2 a telephone company central office (CO) switch, a public branch exchange (PBX) system , and the like.

It is noted that each of external telephone lines 410!, 410₂ and 410_N may, alternatively, be coupled directly with the respective phone wire 408!, 408₂ and 408_N. Analog HPNA hub 404 prevents conventional telephony transmissions between intra-apartment networks 406!, 406₂ and 406_n, from passing there through.

It is noted that a security mechanism may be incorporated in MxU network 400. For example, in accordance with the techniques disclosed in the above mentioned US Patent application publication no. 2003/0198246, the HPNA nodes of the network may use encryption and decryption keys. Accordingly, the network nodes encrypt and decrypt the transmitted and received data packets, respectively. These techniques may be applied in various communication protocol layers.

Reference is now made to Figure 10, which is an illustration in detail of the analog HPNA hub 404 of Figure 9, and phone wires 408!, 408₂ and 408_N. Analog HPNA hub 404 includes coils 442, 452452₂ ,!׳ and 452_n, a core 444, and filters F! (referenced 454!), F₂ (referenced 454₂) and F_n (referenced 454_N).

Coil 442 is coupled with gateway 402 (Figure 9). Each filter 454, is coupled with a respective coil 452!, telephone line 410! and with phone wire 408!. Coil 442 and coils 452!, 452₂ and 452_N are wound around core 444. It is noted that Figure 10 provides a schematic representation of core 444, coil 442 and coils 452!, 452₂ and 452_N.

A signal passing through one of the coils 442, 452!, 452₂ and 452_n is induced in the rest of the coils 442, 452!, 452₂ and 452_N. Core 444 enhances this electrical induction between coils 442, 452!, 452₂ and 452_N. Thus, the combination of core 444 and coils 442, 452!, 452₂ and 452_N, generally referenced 456, effectively operates as a transformer between gateway 402 (Figure 9) and phone wires 408!, 408₂ and 408_N. It is noted

ILD1 that transformer 456 provides DC isolation between gateway 402 (Figure

9) and phone wires 408!, 408₂ and 408_N.

It is noted that various types of transformers may be incorporated in hub 404, instead of transformer 456. It is further noted that the transformer used in hub 404, may be core-less. For example, coils 442, 452!, 452₂ and 452_N may be intertwined there between, whereby electrical induction occurs without the use of a core. It is still further noted that the hub may include a plurality of cores, as shall be shown herein below with reference to Figure 12.

Each filter 454, prevents conventional telephony transmissions signals between twisted pair 408!, telephone line 410, and coil 452, from passing there through, while allowing data transmissions between twisted pair 408,, telephone line 410! and coil 452, to pass there through. Thus, conventional telephony transmissions do not interfere there between in Mxll network 400.

Reference is now made to Figure 11, which is a schematic illustration of an analog HPNA hub 504, constructed and operative in accordance with another embodiment of the disclosed technique, and a plurality of phone wires 508!, 508₂ and 508_N. Analog HPNA hub 504 may be incorporated in an MxU network (not shown), generally similar to MxU network 400 (Figure 9). The MxU network includes phone wires 508!, 508₂and 508_n, generally similar to phone wires 408!, 408₂ and 408_N (Figure 9), reaching a plurality of apartment networks (not shown).

Analog HPNA hub 504 includes coils 520, 522, 542, 532!, 532₂and 532_n, a core 544, and capacitors 524, 546!, 546₂, 546_N, 548!, 548₂and 548_n. Coil 542 is coupled with a gateway (not shown) of the MxU network. Capacitor 524 is coupled with an external telephone line 510!, and connected in series between coils 520 and 522. Coils 520 and 522 are further coupled with twisted pair 508! and with capacitors 546! and 548!. Each coil 532! is connected in series between the respective pair of capacitors 546, and 548,. The pair of capacitors 546! and 548! is further -21002167ILD1 coupled with a phone wire 508! and with coil 532!. Each pair of capacitors

546! and 548!, wherein i is an integer between 2 and N, is further coupled with respective phone wire 508! and a respective external telephone line

510,.

Each pair of capacitors 546, and 548! operates as a high-pass filter, similar to filters 454, (Figure 10). For example, the capacitance of each of capacitors 546, and 548! may be 5nF. Accordingly, these capacitors shall provide a rejection of 55dB to conventional telephony signals (i.e., these signals shall undergo a 562-fold amplitude attenuation when passing through the filters). Thus, hub 504 enables data transmissions between the intra-apartment networks of the MxU network to pass there through, while preventing conventional telephony transmissions between the intra-apartment networks from passing there through. The combination of capacitor 524 and coils 520 and 522, serves as an HPNA isolation filter. Accordingly, the combination of capacitor 524 and coils 520 and 522, substantially attenuates HPNA signals transmitted there through. This substantially reduces the risk of misinterpreting a signal transmitted from external telephone line 510!, as an HPNA signal. For example, NEXT interference from a nearby VDSL line may be substantially eliminated. It is noted that a similar filter may be coupled with each of filters 410₂ and 410_N. The values of the inductance of coils 520 and 522 and the capacitance of capacitor 524 may be, for example, 100 uH, 100 uH and 15nF, respectively.

Reference is now made to Figure 12, which is a schematic illustration of an analog HPNA hub 550, constructed and operative in accordance with a further embodiment of the disclosed technique, and a plurality of phone wires 588!, 588₂ and 588_N. Analog HPNA hub 550 may be incorporated in an MxU network (not shown), generally similar to MxU network 400 (Figure 9). The MxU network includes phone wires 588!, 588₂and 588_n, generally similar to phone wires 408!, 408₂ and 408_N (Figure 9), reaching a plurality of apartment networks (not shown).

ILD1

Analog HPNA hub 550 includes coils 582!, 582₂ and 582_N, 592!, 592₂ and 592_N, cores 594!, 594₂ and 594_N, and capacitors 596!, 596₂, 596_n, 5981, 598₂ and 598_N. Coils 592!, 592₂ and 592_N are coupled with a gateway (not shown) of the MxU network. Each coil 582! is connected in series between the respective pair of capacitors 596! and 598,. Each pair of capacitors 596! and 598, is further coupled with a respective external telephone line 560! and respective phone wire 588!.

Each coil 582! and each coil 592,, is wound around a respective core 594,. Thus, data signals can be communicated between the network apartments, and the gateway. However, data signals communicated directly between the apartments, without the use of the gateway, shall twice undergo the attenuation experienced by data signals communicated between the apartments and the gateway. Parameters of the network, such as the threshold for the allowed data signal amplitudes (i.e., the amplitudes beneath which the signals are regarded as noise) and the number of windings on each coil, may be predetermined so that the twice attenuated signals are beneath the allowed threshold. Thus, the apartments are effectively disabled to communicate there between directly through a core. Rather, the apartments can communicate there between, through the gateway. Since the gateway can monitor and filter some of the data signals, this enhances security in the MxU network.

It is noted that the apartments of the MxU may be divided into groups of apartments, wherein the apartments of each group are allowed to communicate directly there between, while apartments of different groups are effectively disabled to communicate directly there between. For example, coils 592! and 592₂, and one of coils 582!, 582₂, may be wound about a single core (i.e., a single core replaces cores 594! and 594₂, and a single coil replaces coils 592! and 592₂), while the rest of the coils of hub 550 are wound about another single core.

Reference is now made to Figure 13, which is a schematic illustration of an apartment building network, generally referenced 600, -23002167ILD1 constructed and operative in accordance with another embodiment of the disclosed technique. Apartment building network 600 includes intra-apartment networks APT! ! (referenced 606!), APT₂₁! (referenced 6062) and APT_N ! (referenced 606_N), APT!₂ (referenced 608!), APT₂,₂(referenced 608₂) and APT_M,2 (referenced 608_M). Apartment building network 600 further includes analog HPNA hubs 602 and 604, gateways G! (referenced 612) and G₂ (referenced 614), and phone wires 620!, 620₂, 620_N, 622!, 622₂ and 622_M. Gateways 612 and 614 are mounted on a platform 626. A broadband source 610 couples gateways 612 and 614 with a WAN.

Phone wires 620!, 620₂ and 620_N couple hub 602 with intra-apartment networks 606!, 606₂ and 606_N, respectively. Phone wires 622!, 622₂ and 622_M couple hub 604 with intra-apartment networks 608!, 6082 and 608_M, respectively. A binder 624 runs from the vicinity of hubs 602 and 604, to the vicinity of intra-apartment networks 606!, 606₂, 606_N, 608!, 6082 and 608_M. Binder 624 binds together phone wires 620!, 620₂, 620_n, 6221,6222 and 622_M.

Hub 602 is further coupled with gateway 612, external telephone lines 616!, 616₂ and 616_N and with phone wire 620!, 620₂, 620_N. Hub 604 is further coupled with gateway 614, external telephone lines 618!, 618₂and 618_m and with phone wires 622!, 622₂, 622_M.

Hubs 602 and 604 are generally similar to hub 404 (Figure 10). Hub 602 enables data signal transmissions between intra-apartment networks 606!, 606₂ and 606_N to pass there through, thereby coupling those intra-apartment networks in a LAN 628. Hub 602 further prevents conventional telephony transmissions between intra-apartment networks 6061, 6062 and 606_N from passing there through. Similarly, analog HPNA hub 604 couples intra-apartment networks 608!, 608₂ and 608_M in another LAN 630, and further prevents conventional telephony transmission between those apartments from passing there through.

ILD1

Gateways 612 and 614 operate similarly to gateways 162₁162₂_לand 162_n of Figure 4 (i.e., in the example of Figure 13, the number of gateways is equal to two). Gateway 612 operates as a master gateway to gateway 614, which operates as a slave gateway. Gateway 612 instructs the nodes of LANs 628 and 630, to operate according to a selected timeslot scheme, thereby reducing NEXT in network 600.

It is noted that an MxU network may similarly be constructed with a greater number gateways and hubs. Accordingly, one gateway operates as a master gateway, and the rest of the gateways operate as slave gateways, similarly as in the example set forth in Figure 4.

Reference is now made to Figure 14, which is a schematic illustration of a network, generally referenced 700, constructed and operative in accordance with a further embodiment of the disclosed technique. Network 700 may be installed in an apartment, an office, and the like. Network 700 includes HPNA nodes N! (referenced 730), N₂(referenced 732), N₃ (referenced 734), N₄ (referenced 736), N₅ (referenced 738), and N₆ (referenced 740), telephony devices 718, 720 and 722, an exchange system 702, an analog HPNA hub 712, external telephone lines 704, 706 and 708, and internal telephone lines 714 and 716.

Telephony devices 718, 720 and 722 are devices able to transmit and receive conventional telephony signals, such as telephones, facsimile machines, dial-up modems and the like. In the present example, telephony devices 718, 720 and 722 are telephones.

Exchange system (e.g., a PABX, a PBX) 702 is a device capable of managing telephony communications between telephone lines coupled therewith. In the present example, exchange system 702 is a private automatic branch exchange (PABX).

PABX 702 is coupled with external telephone lines 704 and 706. Internal telephone line 714 couples PABX 702 with telephone 718 and with HPNA node 734. Internal telephone line 716 couples PABX 702 with telephone 720 and with HPNA nodes 736 and 738. External telephone -25206705/2 line 708 is coupled with HPNA node 740 and with telephone 722. It is noted that nodes 736 and 738 may be coupled there between in an HPNA LAN, even without using an analog HPNA hub such as hub 712 and the novel architecture of network 700. As shall be shown herein below, the novel architecture of network 700 links all of the nodes 730, 732, 734, 736, 738 and 740 together in an HPNA LAN.

Analog HPNA hub 712 is generally similar to analog HPNA hub 404 (Figure 10). Analog HPNA hub 712 includes coils 750, 752, 754, 756 and 758, filters F! (referenced 742), F₂ (referenced 744) and F₃(referenced 746) and a core 748. Each of filters 742, 744 and 746 is generally similar to filters 454!, 454₂ and 454_N of Figure 10. Each of coils 750, 752, 754, 756 and 758 is generally similar to coils 452!, 452₂ and 452_n of Figure 10.

Coils 750 and 752 are directly coupled with HPNA nodes 730 and 732, respectively. Coils 754, 756 and 758 are coupled with filters 742, 744 and 746. Filter 742 is further coupled with external telephone line 708. Filters 744 and 746 are further coupled with internal telephone lines 714 and 716, respectively.

PABX 702 enables conventional telephony signals between telephones 718, 720 and 722 to pass there through. It is noted that conventionally, PABX 702 exhibits internal low pass filtering and therefore, does not enable high frequency data communication signals (e.g., HPNA transmissions) between the internal telephone lines to pass there through. Hub 712 enables data signal transmissions between nodes 730, 732, 734, 736, 738 and 740 to pass there through, and prevents conventional telephony transmissions from passing there through.