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 />

The second section shall include the data themselves <strong>and</strong> can contain the maximum capabilities of either one or<br />

several nodes.<br />

Each set of maximum capabilities shall be preceded by the <strong>MAC</strong> address of the node that can perform this set of<br />

capabilities.<br />

The different maximum capabilities that can be present in a BPL cell shall be divided into two different groups:<br />

• Common capabilities (vendor independent capabilities)<br />

• Vendor dependent capabilities<br />

Common capabilities shall be always sent in the messages. They are sent by means of a variable-length set of fields,<br />

whose contents <strong>and</strong> meaning will be determined by the protocol.<br />

The vendor dependent capabilities shall be divided themselves in capabilities associated with:<br />

• Chip version.<br />

• Reference design.<br />

• Firmware.<br />

Common capabilities shall not require a division among chip, firmware or reference design related capabilities,<br />

because these capabilities shall be the same for all types of nodes <strong>and</strong> vendors.<br />

On the other h<strong>and</strong>, vendor dependent capabilities shall be divided into the three described sections, because a<br />

solution may present different vendors for each part of the system; one vendor for the chip, other for the firmware<br />

<strong>and</strong> a third one for the reference design, <strong>and</strong> each vendor may sent its own information inside the vendor dependent<br />

section.<br />

The Maximum Capabilities section of the MAX_CAP_MSG message shall follow this division also, with two main<br />

sections, where the first one shall be the common capabilities section <strong>and</strong> the second one the vendor dependent<br />

section.<br />

The common capabilities section shall be simply composed by a first field of length in bytes, <strong>and</strong> a second variablelength<br />

field that shall include the fields that will be determined by the protocol. There are up to 64 entries in the<br />

NCT <strong>and</strong> PCT for common capabilities.<br />

The vendor dependent capabilities section shall be subdivided into three main subsections: Chip, Reference Design<br />

<strong>and</strong> Firmware. For each subsection, two possible schemes of sending capabilities shall be allowed: Indexed <strong>and</strong><br />

Enumerated.<br />

When using the Indexed scheme, it is only required to send a part of sender’s NCT to fill the entire NCT in the<br />

receiver.<br />

The second one shall be simply an enumeration of each of the capabilities that a node has.<br />

Submission page 222 UPA-OPERA

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

Saved successfully!

Ooh no, something went wrong!