TSAT 3000 - Telemetry and data transfer via SATellite
TSAT 3000 Configuration Parameter Description, January 2013 Page 56 of 124
Acknowledge Queue
Sent Secure-Link packets are temporary stored in this queue, and removed when acknowledge from
remote unit is received. Timeout (or request for retransmission) will make a copy of packet and put
in Retransmission-Queue.
• HUB: One queue for each Link. RT: One queue.
• Max size of each
queue is defined by LCC_WINDOW_SIZE packets.
• Max total size of all
queues is defined by LCC_RETRANS_QUE_SIZE packets.
Retransmission Queue
Secure-Link packets scheduled for retransmission (timeout or request) are stored in this queue.
Queue will be emptied before any packet from Priority-Transmission-Queue is sent to Satellite Link.
• One queue.
• Size cannot be larger than Acknowledge-Queue. Typically only one packet for each Link.
Secure-Link RX Queue
Secure-Link packets received out-of-order from Satellite Link, are stored in this queue until the lost
packets have been received. The packets will then be passed on to the system in correct order.
Non-Secure-Link packets are bypassing.
• HUB: One queue for each Link. RT: One queue.
• Remote unit cannot send more than
LCC_WINDOW_SIZE packets out-of-sequence. Hence, no
more than this number of packets may be stored in each queue.
Packetizer RX Queue
Large application packets will be split into smaller link-packets when packet is sent from Priority-
Transmission-Queue. Such packets are concatenated and stored in Packetizer-RX-Queue until the
last link-packet in sequence is received, and the complete application packet sent to ROUTE.
Non-Packetized packets are bypassing.
• One queue for each (current) packetized sequence. Remote unit cannot send more than one
sequence from each PORT (and each Priority) at the same time. Hence, the HUB could typically
have many currently ongoing sequences (waiting for the last packet), while the RT will typically
have lesser
• Max size of each queue is defined by the largest Application packet:
PORT_MAX_PKT_SIZE [n].
Some Management-packets may be as large as 10 kByte.
COM and SOCKET Send Queue
All packets to COM or SOCKET are stored in this queue prior to transmission.
• One queue for each Priority-0 … 7, and one set of queues for each connection.
• High-priority-queues are emptied before low-priority-queues.
•
STREAM + ADAPTER: Max total size of all queues is defined by PORT_TX_QUEUE_SIZE [n] bytes.
SERVICE: Max total size of all queues is PORT_TX_QUEUE_SIZE [n] x (Number of Priorities) bytes.
NETWORK Send Queue
All packets to IP-NETWORK are stored in this queue prior to transmission.
• One queue.
• Size is defined by IPSAT module.
COM, SOCKET and NETWORK Receive Buffers
•
STREAM + ADAPTER + NETWORK: CCU will stop reading from these buffers when PORT is flow-
controlled – Defined by
PORT_PRIORITY [n] and number of packets in Priority Transmission
Queue. See also
LCC_TX_QUE_SIZE.
•
SERVICE: CCU will never stop reading from Receive buffer. Flow-control is handled by remote
NMS application.
To Next Page
Loading...