# US 10,873,526 B2 · Flow aggregation and routing for multi-connectivity client devices > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,873,526 B2 - Document ID: US10873526B2 - Status: Granted - Kind: B2 - Application number: 16/314,509 - Filed: 2017-07-07 - Published: 2019-05-30 - Granted: 2020-12-22 - Earliest claimed: 2016-07-08 - Assignees: Alcatel Lucent - Applicants: Alcatel Lucent - Inventors: Subramanian Vasudevan; Satish Kanugovi - Web page: https://patentgrep.com/patent/US10873526B2 ## CPC - H04L 45/245: {Link aggregation, e.g. trunking} - H04L 47/41: by acting on aggregated flows or links - H04L 69/14: Multichannel or multilink protocols - H04L 69/24: Negotiation of communication capabilities - H04W 76/15: Setup of multiple wireless link connections - H04W 88/182: {Network node acting on behalf of an other network entity, e.g. proxy} - H04L 47/2441: relying on flow classification, e.g. using integrated services [IntServ] - Y02D 30/50: in wire-line communication networks, e.g. low power modes or reduced link rate - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) - Y02D: CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE ## Abstract Aspects relating to managing flow aggregation and routing for a multi-connectivity client device are described herein. In an implementation, a method for managing flow aggregation and routing for the client device includes establishing connection with a network communication engine based on connection parameters. The method further includes exchanging communication capabilities of the client device and a multi-access bearer proxy, with the network communication engine through a predefined communication protocol. The method further includes negotiating a set of communication standards for managing flow aggregation and routing of data packets, with the network communication engine based on the exchanged communication capabilities, where the set of communication standards comprises at least one flow aggregation and routing protocol. ## Claims ### Claim 1 A method for managing flow aggregation and routing of data packets for a multi-connectivity client device, the method comprising: establishing, by a client connection engine of the multi-connectivity client device that supports a plurality of different flow aggregation and routing protocols, a connection with a network communication engine based on connection parameters, wherein the network communication engine manages a multi-access bearer proxy, wherein the multi-access bearer proxy handles uplink and downlink data packet routing of the client device and wherein the multi-access bearer proxy supports one or more flow aggregation and routing protocols; transmitting information regarding communication capabilities of the client device to the network communication engine and receiving information regarding communication capabilities of the multi-access bearer proxy from the network communication engine through a predefined communication protocol; and determining, in conjunction with said network communication engine and based on the transmitted and received information regarding communication capabilities, a set of communication standards for managing the flow aggregation and routing of data packets, wherein said determining includes determining flow aggregation and routing protocols that are common to (i) the plurality of different flow aggregation and routing protocols supported by the multi-connectivity client device and (ii) the one or more flow aggregation and routing protocols supported by the multi-access bearer proxy, and selecting for the set of communication standards to comprise at least one common flow aggregation and routing protocol. ### Claim 2 (depends on 1) The method as claimed in claim 1, further comprising receiving proxy parameters corresponding to the determined set of communication standards, and wherein the proxy parameters include at least parameters corresponding to the at least one common flow aggregation and routing protocol. ### Claim 3 (depends on 2) The method as claimed in claim 2, further comprising communicating with the multi-access bearer proxy to setup a connection corresponding to the at least one common flow aggregation and routing protocol, wherein the communicating comprises at least sharing values corresponding to the multi-access bearer proxy parameters. ### Claim 4 (depends on 1) The method as claimed in claim 1, wherein the at least one common flow aggregation and routing protocol is one of a generic routing encapsulation tunneling protocol and a multipath transmission protocol. ### Claim 5 (depends on 1) The method as claimed in claim 1, wherein the connection parameters comprise at least one of link quality, distance from the client device, and pre-provisioned entry. ### Claim 6 A method performed by a network communication engine for managing flow aggregation and routing of data packets for a multi-connectivity client device, the method comprising: establishing a connection with a client connection engine of the multi-connectivity client device that supports multiple different flow aggregation and routing protocols, wherein the client connection engine manages uplink and downlink data packet routings of the client device; transmitting information regarding communication capabilities of a multi-access bearer proxy corresponding to the client device toward the client connection engine and receiving information regarding communication capabilities of the client device from the client connection engine through a predefined communication protocol, wherein the multi-access bearer proxy supports one or more flow aggregation and routing protocols; and determining, in conjunction with the client connection engine, a set of communication standards for managing the flow aggregation and routing of data packets, based on the transmitted and received information regarding communication capabilities, wherein said determining includes determining flow aggregation and routing protocols that are common to (i) the plurality of different flow aggregation and routing protocols supported by the multi-connectivity client device and (ii) the one or more flow aggregation and routing protocols supported by the multi-access bearer proxy, and selecting for the set of communication standards to comprise at least one common flow aggregation and routing protocol. ### Claim 7 (depends on 6) The method as claimed in claim 6, further comprising communicating the at least one common flow aggregation and routing protocol to the multi-access bearer proxy for establishing uplink and downlink channels for the client device. ### Claim 8 (depends on 6) The method as claimed in claim 6, further comprising transmitting proxy parameters corresponding to the determined set of communication standards towards the client connection engine, wherein the proxy parameters include at least parameters corresponding to the common at least one flow aggregation and routing protocol. ### Claim 9 (depends on 6) The method as claimed in claim 6, wherein the communication capabilities of the multi-access bearer proxy comprise a flow aggregation and routing protocol for distribution of data packets between the client device and the proxy. ### Claim 10 (depends on 6) The method as claimed in claim 6, wherein the set of communication standards further comprises a configuration mode, the configuration mode defining a combination of a core network, and an uplink access and a downlink access utilized for routing of data packets. ### Claim 11 A multi-connectivity client device comprising: at least one processor; at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the multi-connectivity client device to at least exchange data with an associated target terminal; a client connection engine implemented with or coupled to the at least one processor, the client connection engine being configured to: establish a connection with a network communication engine based on connection parameters, wherein the network communication engine is configured to manage a multi-access bearer proxy, wherein the multi-access bearer proxy is configured to handle uplink and downlink data packet routing of the client device, and wherein the multi-access bearer proxy is configured to support one or more flow aggregation and routing protocols; transmit information regarding communication capabilities of the client device including information identifying a plurality of different flow aggregation and routing protocols supported by the client device and receive information regarding communication capabilities of the multi-access bearer proxy from the network communication engine through a predefined communication protocol; and determine, in conjunction with the network communication engine, a set of communication standards for managing flow aggregation and routing of data packets, based on the transmitted and received information regarding communication capabilities, wherein the set of communication standards comprises at least one flow aggregation and routing protocol. ### Claim 12 (depends on 11) The client device as claimed in claim 11, wherein the client connection engine is further configured to report available network links and paths and link quality of available network links and paths, for routing of data packets toward the network communication engine. ### Claim 13 A network connection engine for managing a multi-access bearer proxy corresponding to a multi connectivity client device, the network connection engine comprising: at least one network connection engine processor; at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one network connection processor, cause the network connection engine to at least manage an associated multi-access bearer proxy; a communication module implemented with or coupled to the at least one network connection processor, the communication module being configured to: establish a connection with a client connection engine of the client device, the client device being configured to support a plurality of different flow aggregation and routing protocols, wherein the client connection engine is configured to manage uplink and downlink data packet routings of the client device; and transmit information regarding communication capabilities of the multi-access bearer proxy toward the client connection engine and receive information regarding communication capabilities of the client device from the client connection engine through a predefined communication protocol; and a negotiating module implemented with or coupled to the at least one network connection processor, the negotiating module being configured to determine, in conjunction with the client connection engine, a set of communication standards for managing flow aggregation and routing of data packets based on the transmitted and received information regarding communication capabilities; wherein said determining includes determining flow aggregation and routing protocols which are common to (i) the plurality of different flow aggregation and routing protocols supported by the client device and (ii) the one or more flow aggregation and routing protocols supported by the multi-access bearer proxy and selecting for the set of communication standards to comprises at least one flow aggregation and routing protocol. ### Claim 14 (depends on 13) The network communication engine as claimed in claim 13, wherein the at least one common flow aggregation and routing protocol is one of a generic routing encapsulation tunneling protocol and a multipath transmission protocol. ### Claim 15 (depends on 13) The network communication engine as claimed in claim 13, the network communication engine being further configured to transmit proxy details toward the client connection engine for establishing uplink and downlink channels.