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

However, the processing of such information in order to negotiate the best possible features used in the<br />

communications network is beyond the aim of this protocol.<br />

From the point of view of packet format <strong>and</strong> message exchange, this protocol is an extension of the Port Solver<br />

protocol (PSP). It uses reserved fields in Port Solver Messages (PSMs) to place node capabilities information, <strong>and</strong><br />

shall not prevent the ordinary working of the PSP protocol. Some additions shall be applied to the PSM exchange<br />

mechanism in order to fulfill the features of the Capabilities Exchange protocol.<br />

The Capabilities Exchange protocol shall be flexible enough, not only to provide the exchange of specific<br />

capabilities from different vendors, but also to allow the exchange of a st<strong>and</strong>ard set of minimum capabilities<br />

common for all vendors. Moreover, it shall be easily extensible to include new capabilities, which shall not prevent<br />

backwards compatibility.<br />

This protocol should be efficient, regarding the channel use, to minimize the impact of the overhead of the protocol<br />

in the application data throughput of the whole network.<br />

9.1.4.5.2 Protocol<br />

The protocol is composed by two main stages:<br />

• First stage: Two nodes shall exchange the information about the maximum capabilities they can perform<br />

<strong>and</strong> the capabilities they are running at that time. In this stage, it is used an ACK-based protocol whose<br />

objective is to fill two local tables in each node indexed by <strong>MAC</strong> address:<br />

o Node Capability Table (NCT): It shall contain the maximum capabilities of each known node.<br />

o Performed Capability Table (PCT): It shall contain the capabilities that each known node is running<br />

at that time.<br />

The implementation of these two tables should be done in a single table with the contents described in<br />

section 0 <strong>and</strong> 0. The two tables are divided into four sections:<br />

o Common capabilities<br />

o Chip related capabilities<br />

o Reference Design related capabilities<br />

o Firmware related capabilities<br />

The first section (Common) shall be common for all systems, independent of the vendor. The last three ones<br />

(Chip, Reference Design <strong>and</strong> Firmware related) shall depend on the vendor. The maximum number of<br />

entries of each section shall be 64, with an unlimited size per entry.<br />

• Second stage: It shall take place only if the running capabilities of a node change. This node shall indicate<br />

all nodes the new capabilities that it is performing at that time. This second stage may be either ACK-based<br />

or not, with a first information message <strong>and</strong> a received ACK from the destination, depending on the content<br />

of the ACK expected field. If it is 1, an ACK is expected. If not, no ACK is expected from the receiver.<br />

9.1.4.5.3 Messages<br />

Submission page 219 UPA-OPERA

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

Saved successfully!

Ooh no, something went wrong!