Transmission of packet data over a network with security protocol

An apparatus for an endpoint of a data communication session, the apparatus including at least one processor and at least one memory having processor-executable code in which the processor-executable code is configured to cause the endpoint at least to communicate packet data with another endpoint over a Secure Shell session, the apparatus comprising:

• a security protocol entity configured to use the Secure Shell protocol to authenticate the two end points of the Secure Shell session to each other after an initial key exchange;
• and
• a transport protocol entity configured to:
• establish at least two Transfer Control Protocol (TCP) subconnections for communication of data over the authenticated Secure Shell session,
• maintain at least one of the TCP subconnections for the duration of the Secure Shell session,
• control throughput via the Secure Shell session by selectively distributing said data over the at least two TCP subconnections, and
• transport said data in the Secure Shell session distributed on the at least two TCP subconnections,
• wherein the security protocol entity is further configured to change security parameters relating to a specific TCP subconnection during the Secure Shell session based on at least one key exchange message.

A system in a data network, the system comprising:

• a first node and a second node for communicating packet data over a Secure Shell session,
• the first node comprising:
• at least one processor,
• a security protocol entity containing instructions executable by the at least one processor, the security protocol entity configured to use the Secure Shell protocol to perform authentication with the second node after an initial key exchange, and
• a transport protocol entity configured to establish at least two Transfer Control Protocol (TCP) subconnections with the second node for communicating data over the authenticated Secure Shell session, maintain at least one of the TCP subconnections for the duration of the Secure Shell session, control throughput via the Secure Shell session by selectively distributing said data over the at least two TCP subconnections, and transport said data in the Secure Shell session distributed on the at least two TCP subconnections;
• and
• the second node comprising:
• at least one processor,
• a security protocol entity containing instructions executable by the at least one processor, the security protocol entity configured to use the Secure Shell protocol to perform authentication with the first node after an initial key exchange, and
• a transport protocol entity configured to establish at least two Transfer Control Protocol (TCP) subconnections with the first node for communicating data over the authenticated Secure Shell session, maintain at least one of the TCP subconnections for the duration of the Secure Shell session, control throughput via the Secure Shell session by selectively distributing said data over the at least two TCP subconnections, and transport said data in the Secure Shell session distributed on the at least two TCP subconnections,
• wherein the security protocol entity is further configured to change security parameters relating to a specific TCP subconnection during the Secure Shell session based on at least one key exchange message.

A computer program product embedded on a non-transitory computer-readable medium comprising:

• program code for controlling communication of packet data between two endpoints over a Secure Shell session, the program. code being configured to cause:
• authentication of the two end points to each other after an initial key exchange based on the Secure Shell protocol,
• establishment, for the authenticated endpoints, of at least two Transfer Control Protocol (TCP) subconnections for communication of data over the authenticated Secure Shell session,
• maintenance of at least one of the TCP subconnections for the duration of the Secure Shell session,
• control of throughput via the Secure Shell session by selectively distributing said data over the at least two TCP subconnections,
• transportation of said data in the Secure Shell session distributed on the at least two TCP subconnections, and
• change of security parameters relating to a specific TCP subconnection during the Secure Shell session using at least one key exchange message.