Abstract: In one embodiment, an inverter system is disclosed. The system includes a plurality of inverter circuits, each inverter circuit configured to provide a respective alternating current (AC) signal to an output. The system further includes a plurality of rectifier circuits configured to supply respective direct current (DC) signals to the plurality of inverter circuits, and an alternator comprising inductively-coupled windings and configured to provide respective AC power to the plurality of rectifier circuits. The plurality of rectifier circuits are synchronous rectifier circuits configured to drive the alternator in reverse to transfer power to another one of the plurality of rectifier circuits via the respective windings.

Abstract: An isolated bus inverter system including inverter circuits and a controller. The inverter circuits include a switching array to provide a polyphase alternating current (AC) signal to an output. Each of the inverter circuits includes an energy source isolated from the other inverter circuits of the inverter circuits or a reference isolated from the other inverter circuits of the inverter circuits. The controller is configured to generate timing signals for the inverter circuits to generate the AC signals for the output based on DC signals received from one or more rectifier circuits.

Abstract: The SACK scoreboard is used in slow recovery and the SACK scoreboard and an application programmed timeout are used to determine the initial CWND in slow recovery. The CWND is calculated so that all packets will be recovered before the application times out. A new socket option is provided for an application to program an application timeout (say APP_TO). This value is used in conjunction with the RTT (round trip time) to determine the initial CWND value to insure completion before timeout. Along with the timeout, the application can also set the mode as “soft,” where the CWND value is set to “1” as conventional but when that packet is ACKed, the CWND value is increased immediately to a modified calculated value to allow timely recovery.

Abstract: After sending M consecutive DUP ACKs, M generally being three, the TCP receiver generates DUP ACKs every N packets, with N greater than one, with the eventually transmitted DUP ACK containing SACK information. After receiving the third DUP ACK the TCP transmitter uses the positive acknowledgements provided in the SACK information in the TCP header to inflate the congestion window. With the reduced DUP ACKs from the TCP receiver to the TCP transmitter, the impact of TCP DUP ACKs on the data rate from the TCP receiver to the TCP transmitter is substantially reduced.

Abstract: After sending M consecutive DUP ACKs, M generally being three, the TCP receiver generates DUP ACKs every N packets, with N greater than one, with the eventually transmitted DUP ACK containing SACK information. After receiving the third DUP ACK the TCP transmitter uses the positive acknowledgements provided in the SACK information in the TCP header to inflate the congestion window. With the reduced DUP ACKs from the TCP receiver to the TCP transmitter, the impact of TCP DUP ACKs on the data rate from the TCP receiver to the TCP transmitter is substantially reduced.

Abstract: The SACK scoreboard is used in slow recovery and the SACK scoreboard and an application programmed timeout are used to determine the initial CWND in slow recovery. The CWND is calculated so that all packets will be recovered before the application times out. A new socket option is provided for an application to program an application timeout (say APP_TO). This value is used in conjunction with the RTT (round trip time) to determine the initial CWND value to insure completion before timeout. Along with the timeout, the application can also set the mode as “soft,” where the CWND value is set to “1” as conventional but when that packet is ACKed, the CWND value is increased immediately to a modified calculated value to allow timely recovery.

Abstract: A TCP layer that is able to defeat or disable retransmit and recovery operations upon request from a diagnostic program. This allows the missing packets and the like to be determined by the diagnostic program as the TCP layer will not hide the packet loss by doing retransmission operations. The TCP layer otherwise operates normally, allowing better analysis of the operation of the TCP layer and the network.

Abstract: A system and method for sharing a WAN TCP tunnel between multiple flows without having head of the line blocking problem is disclosed. When a complete but out of order PDU is stuck behind an incomplete PDU in a TCP tunnel, the complete but out of order PDU is removed from the tunnel. To do that, first the boundaries of the PDUs of the different flows are preserved and the TCP receive window advertisement is increased. The receive window is opened when initially receiving out-of-order data. As out-of-order complete PDUs are pulled out of the receive queue, to address double counting, place holders are used in the receive queue to indicate data that was in the queue. As out-of-order data PDUs are pulled out of the queue the window advertisement is increased. This keeps the sending side from running out of TX window and stopping transmission of new data.

Abstract: After sending M consecutive DUP ACKs, M generally being three, the TCP receiver generates DUP ACKs every N packets, with N greater than one, with the eventually transmitted DUP ACK containing SACK information. After receiving the third DUP ACK the TCP transmitter uses the positive acknowledgements provided in the SACK information in the TCP header to inflate the congestion window. With the reduced DUP ACKs from the TCP receiver to the TCP transmitter, the impact of TCP DUP ACKs on the data rate from the TCP receiver to the TCP transmitter is substantially reduced.

Abstract: When in Fast Recovery, Extended Fast Recovery operation starts a timer on the retransmission of each packet. The time expires in one adjusted round trip time. If there has not been an acknowledgement for the retransmitted packet and the Extended Fast Recovery timer expires, it is assumed that the retransmitted packet was lost and must be retransmitted again. Extended Fast Recovery operation keeps retransmitting the packet, once every adjusted round trip time, until an acknowledgement is received or the slow recovery timer expires. Segment Timing is an addition to Extended Fast Recovery where every sent packet is timed separately from the time of first transmission, not just retransmitted packets.

Abstract: Periodically retransmitting of multiply lost TCP/IP packets until either an ACK is received or the timeout finally occurs. By retransmitting the packet more than the once as done with prior art SACK approaches, there is a possibility of not having to wait until the timeout period elapses if one of the other retransmissions successfully transits the network. If the packet is successfully received and acknowledged before the timeout period ends, then the more extensive timeout procedures need not be invoked and traffic is much less affected.