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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

4-June-07 P1901_PRO_016_r0<br />

RUN_CAP_MSG message<br />

This message shall contain information about the capabilities that a node is running at that time. Additionally, by<br />

means of the MESSAGE_MODE field, a change of previous sent running capabilities can be indicated. Four are the<br />

supported message modes that apply only to a running capabilities set from a concrete node:<br />

Info mode with ACK: Indicates that the following sections contain information about the maximum <strong>and</strong> running<br />

capabilities, <strong>and</strong> that an ACK is required for this message.<br />

Info mode without ACK: Indicates that the following sections contain information about the maximum <strong>and</strong> running<br />

capabilities, <strong>and</strong> that NO ACK is required for this message.<br />

Change Mode with ACK: Indicates that the running capabilities have changed <strong>and</strong> are sent in the following section.<br />

An ACK of this message is expected by the sender.<br />

Change Mode without ACK: Indicates that the running capabilities have changed <strong>and</strong> are sent in the following<br />

section. No ACK of this message is expected by the sender.<br />

The running capabilities are transmitted by means of a field that indicates what is the default value for the<br />

capabilities that are not included explicitly in this message (highest possible capability of the node or lower possible<br />

capability of the node), <strong>and</strong> several two fields groups where the first one is a reference to a capability in the NCT<br />

(including section <strong>and</strong> position) <strong>and</strong> the second field is the value related to this capability. The number of groups<br />

describing each of the running capabilities that are different from the default value shall be set in the<br />

NUM_RUN_CAP field.<br />

If a value for a capability is longer than a byte, the same reference shall be sent followed by the first byte, then the<br />

same reference followed by the second byte <strong>and</strong> so on, up to complete the number of desired bytes for the capability<br />

value.<br />

In the following figure it is shown an example of a Running Capability section carrying running capabilities from N<br />

nodes, where the first set contain an explicit description of three running capabilities <strong>and</strong> the Nth set contains a<br />

description of four running capabilities.<br />

MSG_TYPE = 0x2<br />

#CAP_SET = N<br />

L<strong>MAC</strong>_SET<br />

MSG__MODE<br />

DEF_MODE<br />

#RUN_CAP<br />

CAP_REF_1<br />

CAP_VALUE_1<br />

CAP_REF_2<br />

CAP_VALUE_2<br />

...<br />

Figure 105 Example of Running Capability Section<br />

CAP_REF_i<br />

CAP_VALUE_i<br />

Submission page 226 UPA-OPERA<br />

L<strong>MAC</strong>_SET<br />

MSG__MODE<br />

DEF_MODE<br />

#RUN_CAP<br />

CAP_REF_1<br />

CAP_VALUE_1<br />

CAP_REF_2<br />

CAP_VALUE_2<br />

...<br />

CAP_REF_i<br />

CAP_VALUE_1

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

Saved successfully!

Ooh no, something went wrong!