Data Transmission
The following primitives are used for data transmission from the next higher layer. The result is indicated with confirm primitive. These responses are prepared with respect to its own requests for data transmission to the PHY layer.
MCPS-DATA.request : Requests the transmission of a data unit from the local SSCS entity. It prepares the corresponding MPDU from the incoming SPDU and this is passed on to the PHY layer for transmission.
MCPS-DATA.confirm : Reports the result of the request for the transmission of an SPDU over to a single peer SSCS entity.
2.6.2.2 Data Reception
The following primitives are used for data reception from the next lower layer(PHY). The PHY layer upon receiving a data packet informs the upper layer, with an indication about the received packet. And the MAC layer, after analyzing the indication primitive fields, informs the local SSCS entity of an incoming packet data frame, unless it is intended for itself.
MCPS-DATA.indication : The MCPS-DATA.indication primitive indicates the transfer of a data SPDU (i.e., MSDU) from the MAC sublayer to the local SSCS entity. This indicates the arrival of data from the peer SSCS to the local SSCS entity.
2.6.2.3 Association
The primitives that are used to associate a network node or to provide association services, as applicable to a coordinator, are presented here.
MLME-ASSOCIATE.request: The MLME-ASSOCIATE.request primitive allows a device to request an association with a coordinator. The association request is generated at the next higher layer, (generally the routing layer), however it is not part of this study. The conditions that determine the invoking of the association phase is not defined.
MLME-ASSOCIATE.indication: Indicates the reception of an association request command.
MLME-ASSOCIATE.response : This primitive is used to initiate a response to an MLMEASSOCIATE.indication primitive.
MLME-ASSOCIATE.confirm: The MLME-ASSOCIATE.confirm primitive is used to inform the next higher layer of the initiating device whether its request to associate was successful or unsuccessful.
2.6.2.4 Disassociation
Similar to the primitives described for the association phase, the following primitives are used for the disassociation. Their functionality is exactly inverse to that of their counterparts for the association.
MLME-DISASSOCIATE.request
MLME-DISASSOCIATE.indication
MLME-DISASSOCIATE.response
MLME-DISASSOCIATE.confirm
2.6.2.5 PAN Information Management
The following primitives are used to request and to reply back with information about a particular MAC PIB Value.
MLME-GET.request: The next higher layer issues this primitive to the MAC layer to request information about a particular, MAC PIB.
MLME-GET.confirm: This primitive is used by the MAC layer to reply back to the MLMEGET.request primitive received to it by the next higher layer.
MLME-SET.request: Request to set the indicated MAC PIB with the passed value.
MLME-SET.confirm: Returns the result of an attempt to set the indicated PIB value.
2.6.2.6 Orphaning
MLME-ORPHAN.indication: A primitive to indicate to the next higher layer of the presence of an orphan device in the network.
MLME-ORPHAN.response: It helps the next higher layer to respond to the MLMEORPHAN.indication message by the MAC layer. It indicates if the node in question is associated to the network.
2.6.2.7 Receiver Maintainence
The following primitives are used to maintain the receiver enable time.
MLME-RX-ENABLE.request : The next higher layer requests the MAC for the Receiver to be enabled for a finite amount of time.
MLME-RX-ENABLE.confirm : It reports the result of an attempt to enable the receiver.
2.6.2.8 Channel Scanning
These primitives are used to scan the communication channels to determine the presence or absence of PANs.
MLME-SCAN.request: The MLME-SCAN.request primitive is used to initiate a channel scan over a given list of channels. A device can use a channel scan to measure the energy on the channel, search for the coordinator with which it is associated, or search for all coordinators transmitting beacon frames within the POS of the scanning device.
MLME-SCAN.confirm: It reports back to the next higher channel of the result of the channel scan.
Primitives are functions offered by each layer. The four generic types of a primitive are Request, Indication, Response, and Confirm. The PHY layer is responsible for tasks like activating/deactivating the transceiver, CCA, ED, LQI management, Data transmission and reception. The primitives responsible for each of the above described mechanisms are presented and are explained in brief. The PHY primitives are followed by the MAC primitives.
The following primitives are used for data transmission from the next higher layer. The result is indicated with confirm primitive. These responses are prepared with respect to its own requests for data transmission to the PHY layer.
MCPS-DATA.request : Requests the transmission of a data unit from the local SSCS entity. It prepares the corresponding MPDU from the incoming SPDU and this is passed on to the PHY layer for transmission.
MCPS-DATA.confirm : Reports the result of the request for the transmission of an SPDU over to a single peer SSCS entity.
2.6.2.2 Data Reception
The following primitives are used for data reception from the next lower layer(PHY). The PHY layer upon receiving a data packet informs the upper layer, with an indication about the received packet. And the MAC layer, after analyzing the indication primitive fields, informs the local SSCS entity of an incoming packet data frame, unless it is intended for itself.
MCPS-DATA.indication : The MCPS-DATA.indication primitive indicates the transfer of a data SPDU (i.e., MSDU) from the MAC sublayer to the local SSCS entity. This indicates the arrival of data from the peer SSCS to the local SSCS entity.
2.6.2.3 Association
The primitives that are used to associate a network node or to provide association services, as applicable to a coordinator, are presented here.
MLME-ASSOCIATE.request: The MLME-ASSOCIATE.request primitive allows a device to request an association with a coordinator. The association request is generated at the next higher layer, (generally the routing layer), however it is not part of this study. The conditions that determine the invoking of the association phase is not defined.
MLME-ASSOCIATE.indication: Indicates the reception of an association request command.
MLME-ASSOCIATE.response : This primitive is used to initiate a response to an MLMEASSOCIATE.indication primitive.
MLME-ASSOCIATE.confirm: The MLME-ASSOCIATE.confirm primitive is used to inform the next higher layer of the initiating device whether its request to associate was successful or unsuccessful.
2.6.2.4 Disassociation
Similar to the primitives described for the association phase, the following primitives are used for the disassociation. Their functionality is exactly inverse to that of their counterparts for the association.
MLME-DISASSOCIATE.request
MLME-DISASSOCIATE.indication
MLME-DISASSOCIATE.response
MLME-DISASSOCIATE.confirm
2.6.2.5 PAN Information Management
The following primitives are used to request and to reply back with information about a particular MAC PIB Value.
MLME-GET.request: The next higher layer issues this primitive to the MAC layer to request information about a particular, MAC PIB.
MLME-GET.confirm: This primitive is used by the MAC layer to reply back to the MLMEGET.request primitive received to it by the next higher layer.
MLME-SET.request: Request to set the indicated MAC PIB with the passed value.
MLME-SET.confirm: Returns the result of an attempt to set the indicated PIB value.
2.6.2.6 Orphaning
MLME-ORPHAN.indication: A primitive to indicate to the next higher layer of the presence of an orphan device in the network.
MLME-ORPHAN.response: It helps the next higher layer to respond to the MLMEORPHAN.indication message by the MAC layer. It indicates if the node in question is associated to the network.
2.6.2.7 Receiver Maintainence
The following primitives are used to maintain the receiver enable time.
MLME-RX-ENABLE.request : The next higher layer requests the MAC for the Receiver to be enabled for a finite amount of time.
MLME-RX-ENABLE.confirm : It reports the result of an attempt to enable the receiver.
2.6.2.8 Channel Scanning
These primitives are used to scan the communication channels to determine the presence or absence of PANs.
MLME-SCAN.request: The MLME-SCAN.request primitive is used to initiate a channel scan over a given list of channels. A device can use a channel scan to measure the energy on the channel, search for the coordinator with which it is associated, or search for all coordinators transmitting beacon frames within the POS of the scanning device.
MLME-SCAN.confirm: It reports back to the next higher channel of the result of the channel scan.
Primitives are functions offered by each layer. The four generic types of a primitive are Request, Indication, Response, and Confirm. The PHY layer is responsible for tasks like activating/deactivating the transceiver, CCA, ED, LQI management, Data transmission and reception. The primitives responsible for each of the above described mechanisms are presented and are explained in brief. The PHY primitives are followed by the MAC primitives.
