03.11.2012 Views

Medium Access Control (MAC) and Physical Layer (PHY) - CISE

Medium Access Control (MAC) and Physical Layer (PHY) - CISE

Medium Access Control (MAC) and Physical Layer (PHY) - CISE

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

4-June-07 P1901_PRO_016_r0<br />

port using HURTO modulation. In the other cases, the multi-port request will result in several consecutive LLC<br />

service requests related to each unicast local port, or in the use of a native multicast local port.<br />

3. Broadcasts loop back avoidance: on the reception path, upon reception of a packet over the broadcast local port<br />

(127), the module shall discard any packet which is detected as previously transmitted (that is, the <strong>MAC</strong> address<br />

contained in the PB field of the packet is equal to the <strong>MAC</strong> address of the node).<br />

4. On the reception path, upon reception of a packet over the broadcast local port (127), the local port passed<br />

within the Eth.ind primitive shall be the one assigned to the remote node from which the request was received.<br />

7 BRIDGING FUNCTION<br />

7.1 General<br />

The bridging function interconnects bridge ports. There are two types of bridge ports: BPL ports <strong>and</strong> non-BPL ports<br />

<strong>and</strong> the management port. BPL ports are the bridge ports that represent a remote PL unit <strong>and</strong> are directly mapped<br />

onto the completed entries of the Port Solver Table. Non-BPL ports are any other external ports of the unit (e.g.<br />

Ethernet, USB, WIFI,…).<br />

The bridging function is based in st<strong>and</strong>ards IEEE 802.1D <strong>and</strong> IEEE 802.1Q as described below.<br />

From a bridging st<strong>and</strong>point, the convergence layer is seen as a set of bridge ports called “BPL ports” which are both<br />

transmission <strong>and</strong> reception unicast <strong>and</strong> native multicast ports. The bridging block of a node h<strong>and</strong>les as many BPL<br />

unicast ports as there completed entries in the Port Solver Table of this node, in addition to the native multicast<br />

ports that has a valid value in such Port Solver Table. The identifier of a BPL port corresponds to the value of the<br />

local port attached to a remote node, that can be a native multicast or an unicast port. The status (open/close) <strong>and</strong> the<br />

identifier of the BPL ports are mapped onto the status <strong>and</strong> identifiers of the local ports defined in the Port Solver<br />

Table.<br />

There is also a BPL management entity that can access all the ports in the same conditions as the higher layer<br />

entities as described in IEEE 802.1D.<br />

*Note: The port solver table includes complete entries <strong>and</strong> incomplete entries. Complete entries correspond to local<br />

port which are associated to solved remote port <strong>and</strong> <strong>MAC</strong> addresses. Incomplete entries correspond to local ports<br />

which associated unicast remote port are still not solved via the Port Solver Protocol.A complete entry may have<br />

an additional native multicast remote port associated.<br />

7.2 IEEE 802.1D conformance<br />

The bridging function shall conform to:<br />

a) IEEE Std 802.1D, with Basic Filtering Services support requirements<br />

Submission page 173 UPA-OPERA

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!