Process Models
The TDMA model uses the following process models.
Table 223: TDMA Process Models
| Process | Description |
|---|---|
| tdma_config | This process model resides in TDMA configuration object and serves as the user interface for defining all global parameters, such as definition of all TDMA profiles and TDMA networks that exist in the scenario. The tdma_config process creates a tdma_vnc_child child process for each TDMA network that is defined in the system. |
| tdma_dispatch | This is the parent process for TDMA functionality; it defines TDMA attributes and common statistics. Depending on whether or not controller functionality is enabled on this node, tdma_dispatch spawns one of the following child processes: • tdma_controller if controller functionality is enabled • tdma_mac if controller functionality is not enabled |
| tdma_vnc_child | This process serves as a virtual controller for the TDMA network. A separate process is created for each distributed (and without infrastructure) TDMA network definition. The tdma_vnc_child process performs the following tasks: • Collecting the timing and other parameters of the TDMA from the attributes of the tdma_config process model. • Creating the (empty) graph of the network and publishing the system information in the Process Registry. • Execution of the timeslot allocation algorithm at the start of each frame to calculate the slots allocated to each node based on the current requests from the nodes and the current topology of the network. • Creating frame allocation reports when receiving the corresponding interrupt from the parent tdma_config process. |
| tdma_controller | This process serves as a controller for the centralized TDMA network. A separate process is created for each TDMA network definition. The presence of a controller automatically results in centralized operation of the TDMA network. The tdma_controller process performs the following tasks: • Collecting the timing and other parameters of the TDMA from the attributes of the tdma_config process model. • Creating the (empty) graph of the network and publishing the system information in the Process Registry. • Accepting slot request messages from associated TDMA clients. • Executing the timeslot allocation algorithm at the start of each frame to calculate the slots allocated to each node based on the current requests from the nodes and the current topology of the network. • Sending the frame allocation map along with a beacon message to the associated clients. • Creating frame allocation reports when receiving the corresponding interrupt from the parent tdma_config process. |
| tdma_mac | This process model is responsible for necessary channel access, queuing and packetization operations to send the data (from higher layers or from network) over the channel. This process operates directly below the standard ARP process. The tdma_mac process performs the following tasks: • Initialization: The process model finds the controller process that controls its network from the process registry and accesses the pointer to the network’s information structure. The controller process is the tdma_controller process if one is running, otherwise it is the tdma_vnc_child process. • Hello messages: In a distributed network, the process periodically sends broadcast Hello messages to notify its neighbor nodes of its presence. It also processes incoming Hello packets from other nodes to update the list of its neighbors. • Higher-layer packets: Packets coming from the higher layer will be stored in the segmentation buffer and will be dequeued during transmit timeslots. • Slot requests: The client calculates the number of packets in its queue and the required number of slots. If the client is part of a centralized network, it sends explicit slot request messages in the control slots at the end of the frame to the controller. If the client is part of a distributed network then it registers its slot requirement with the tdma_vnc_child process. • Slot allocation and packet transmission: If the client is part of a centralized network, it gets an explicit slot allocation map as a control message from the controller for that frame. If the client is part of a distributed network, the client can look up its slot allocation from the vnc_child process. Based on the available slots and the packets in the queue, the client sets up its Send interrupts. • After each transmission, the process checks whether there is any more data in the transmit buffer. If there is more data to send, it finds its next assigned slot and schedules a SEND interrupt for that time. • Handoff: In a distributed network the client listens to HELLO messages from other nodes to either continue to be part of the existing network or form/join a new network. If the client is part of a centralized network, it relies on the beacon messages from the controller device to determine whether or not a handoff is needed. |