Techniques for establishing a communication connection between two network entities via different network flows

• US 10,530,644 B2
• Filed: 07/27/2017
• Issued: 01/07/2020
• Est. Priority Date: 07/29/2016
• Status: Active Grant

• Current Assignee: Deutsche Telekom AG
• Original Assignee: Deutsche Telekom AG
• Inventors: Amend, Markus, Bogenfeld, Eckard, Matz, Andreas Philipp
• Primary Examiner(s): Coby, Frantz
• Application Number:
  US15/660,984
• Publication Number:
  US 20180034691A1
• Time in Patent Office: 894 Days
• Field of Search: 709227, 709228, 709249, 370329, 370230-232, 370235, 370252
• CPC Class Codes: H04L 41/0806 for initial configuration or provisioning, e.g. plug-and-play
• CPC Class Codes: H04L 45/16 Multipoint routing
• CPC Class Codes: H04L 45/24 Multipath
• CPC Class Codes: H04L 47/15 in relation to multipoint traffic arrangements for broadcast or multicast in data networks H04L12/18
• CPC Class Codes: H04W 40/02 Communication route or path selection, e.g. power-based or shortest path routing
• CPC Class Codes: H04W 74/00 Wireless channel access

Abstract

A method for establishing a communication connection between a first network entity and a second network entity via at least two different network flows includes: transmitting a first request, by the first network entity, directed to the second network entity via a first network flow; transmitting at least one second request, by the first network entity, directed to the second network entity via at least one second network flow, wherein the at least one second request is transmitted by the first network entity before the first network entity receives a reply to the first request from the second network entity; and establishing the communication connection between the first network entity and the second network entity based on at least one of the first request or the at least one second request.

Claims

1. A method for establishing a communication connection between a first network entity and a second network entity via at least two different network flows, the method comprising:

transmitting a first request, by the first network entity, directed to the second network entity via a first network flow;

transmitting at least one second request, by the first network entity, directed to the second network entity via at least one second network flow, wherein the at least one second request is transmitted by the first network entity before the first network entity receives a reply to the first request from the second network entity; and

establishing the communication connection between the first network entity and the second network entity based on at least one of the first request or the at least one second request;

wherein the method further comprises;

enabling data communication, by the first network entity, responsive to a decision based on reception of the reply to the first request from the second network entity and/or reception of at least one reply to the at least one second request from the second network entity;

transmitting a first acknowledgement, by the first network entity, directed to the second network entity via the first network flow;

transmitting at least one second acknowledgement, by the first network entity, directed to the second network entity via the at least one second network flow; and

configuring, by the second network entity, a respective network flow of the first network flow and the at least one second network flow via which a respective acknowledgement of the first acknowledgement and the at least one second acknowledgement is first received by the second network entity as a primary network flow.

2. The method of claim 1, wherein the first request comprises information (MP_CAPABLE, Key_A) indicating that the first network flow is to be configured as a primary network flow;

and

wherein the at least one second request comprises information (MP_CAPABLE, Key_A) indicating that the at least one second network flow is to be configured as a primary network flow.

3. The method of claim 1, wherein the at least two different network flows are configured to couple the first network entity with the second network entity via a multipoint-to-point connection, a multipoint-to-multipoint connection, or a point-to-multipoint connection.

4. The method of claim 1, wherein transmitting the first request is initiated at the same time as transmitting the at least one second request.

5. The method of claim 1, further comprising:

configuring, by the second network entity, at least one network flow of the at least two different network flows other than the primary network flow as at least one secondary network flow, wherein at least one acknowledgement corresponding to the at least one other network flow is received after the respective acknowledgement corresponding to the primary network flow.

6. The method of claim 5, wherein the primary network flow is configured as a primary flow according to the multipath transport control protocol (MPTCP);

and

wherein the at least one secondary network flow is configured as at least one subsequent flow according to the MPTCP protocol.

7. The method of claim 1, further comprising:

transmitting at least one network flow reset signal, by the second network entity, directed to the first network entity via at least one network flow of the at least two different network flows other than the primary network flow, wherein transmitting the at least one network flow reset signal is responsive to the respective acknowledgement corresponding to the primary network flow.

8. The method of claim 7, further comprising:

transmitting at least one further second request, by the first network entity, directed to the second network entity via the at least one other network flow, wherein transmitting the at least one further second request is responsive to reception of the at least one network flow reset signal, by the first network entity.

9. The method of claim 8, wherein the at least one further second request comprises information (MP_JOIN, Token_KeyB, Random_A) indicating that the at least one other network flow is to be configured as at least one secondary network flow.

10. The method of claim 1, further comprising:

starting a timer, by the first network entity, responsive to transmitting the first request; and

transmitting the at least one second request, by the first network entity, responsive to expiration of the timer.

11. The method of claim 10, wherein the respective network flow configured as the primary network flow is a network flow of the at least one second network flow.

12. The method of claim 11, further comprising:

transmitting a further first request, by the first network entity, directed to the second network entity via the first network flow, wherein the further first request comprises information (MP_JOIN, Token_KeyB, Random_A) indicating that the first network flow is to be configured as a secondary network flow.

13. A first network entity for establishing a communication connection to a second network entity via at least two different network flows, the first network entity comprising:

at least one network interface configured to;

transmit a first request to the second network entity via a first network flow;

transmit at least one second request to the second network entity via at least one second network flow;

receive a reply to the first request from the second network entity; and

a processor configured to;

control the at least one network interface to transmit the at least one second request before receiving the reply to the first request from the second network entity; and

establish the communication connection to the second network entity based on at least one of the first request or the at least one second request;

wherein the first request comprises a SYN message according to the Multipath Transport Control Protocol (MTCP) standard; and

wherein the at least one second request comprises at least one SYN message according to the MTCP standard.

14. A second network entity for establishing a communication connection to a first network entity via at least two different network flows, the second network entity comprising:

at least one network interface configured to;

receive a first request from the first network entity via a first network flow;

receive at least one second request from the first network entity via at least one second network flow;

transmit to the first network entity a reply to the first request; and

transmit to the first network entity at least one reply to the at least one second request; and

a processor configured to;

control the at least one network interface to transmit the reply to the first request responsive to receiving the first request and to transmit the at least one reply to the at least one second request responsive to receiving the at least one second request; and

establish the communication connection to the first network entity based on at least one of the first request or the at least one second request;

wherein the first request comprises a SYN message according to the Multipath Transport Control Protocol (MTCP) standard; and

wherein the at least one second request comprises at least one SYN message according to the MTCP standard.