Sign In to Follow Application
View All Documents & Correspondence

Flow Aggregation And Routing For Multi Connectivity Client Devices

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.

Get Free WhatsApp Updates!
Notices, Deadlines & Correspondence

Patent Information

Application #
Filing Date
08 July 2016
Publication Number
02/2018
Publication Type
INA
Invention Field
COMMUNICATION
Status
Email
lsmds@lakshmisri.com
Parent Application
Patent Number
Legal Status
Grant Date
2024-02-06
Renewal Date

Applicants

ALCATEL LUCENT
148/152 route de la Reine 92100 Boulogne-Billancourt, France

Inventors

1. VASUDEVAN, Subramanian
Alcatel-Lucent USA Inc. 600-700 Mountain Avenue MURRAY HILL New Jersey, 07974-0636, United States of America
2. KANUGOVI, Satish
Alcatel-Lucent India Limited NAGAWARA VILLAGE,KASABA TALUK OUTER RING ROAD MANYATA EMBASSY BUSINESS PK BANGALORE 560045, India

Specification

Claims:1. A method for managing flow aggregation and routing of data packets for a multi-connectivity client device, the method comprising:
establishing connection with a network communication engine based on connection parameters, wherein the network communication engine manages a multi-access bearer proxy, and wherein the proxy handles uplink and downlink data packet routing of the client device;
exchanging communication capabilities of the client device and the proxy, with the network communication engine through a predefined communication protocol; and
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, wherein the set of communication standards comprises at least one flow aggregation and routing protocol.

2. The method as claimed in claim 1, further comprising receiving proxy parameters corresponding to the negotiated set of communication standards, and wherein the proxy parameters include at least parameters corresponding to the at least one flow aggregation and routing protocol.

3. The method as claimed in claim 2, further comprising communicating with the proxy to setup a connection corresponding to the at least one flow aggregation and routing protocol, wherein the communicating comprises at least sharing values corresponding to the proxy parameters.

4. The method as claimed in claim 1, wherein the flow aggregation and routing protocol is one of a Generic Routing Encapsulation (GRE) tunneling protocol and a Multipath Transmission Protocol (TCP) (MPTCP).

5. The method as claimed in claim 1, wherein the connection parameters comprises at least one of link quality, distance from the client device, and pre-provisioned entry.

6. A method for managing flow aggregation and routing of data packets for a multi-connectivity client device, the method comprising:
establishing connection with a client communication engine, wherein the client communication engine manages uplink and downlink data packet routings of the client device;
exchanging communication capabilities of a multi-access bearer proxy corresponding to the client device and communication capabilities of the client device, with the client communication engine through a predefined communication protocol; and
negotiating a set of communication standards for managing flow aggregation and routing of data packets, with the client communication engine based on the exchanged communication capabilities, wherein the set of communication standards comprises at least one flow aggregation and routing protocol.

7. The method as claimed in claim 6, further comprising communicating the at least one flow aggregation and routing protocol to the proxy for establishing uplink and downlink channels for the client device.

8. The method as claimed in claim 6, further comprising sharing proxy parameters corresponding to the negotiated set of communication standards with the client communication engine, wherein the proxy parameters include at least parameters corresponding to the at least one flow aggregation and routing protocol.

9. The method as claimed in claim 6, wherein the exchanging communication capabilities of the proxy comprises sharing choice of a flow aggregation and routing protocol for distribution of data packets between the client device and the proxy.

10. 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 and a downlink accesses utilized for routing of data packets.

11. A multi connectivity client device comprising:
a processor;
a client communication engine coupled to the processor, the client communication engine is to:
establish a connection with a network communication engine based on connection parameters, wherein the network communication engine manages a multi-access bearer proxy, and wherein the proxy handles uplink and downlink data packet routing of the client device;
exchange communication capabilities of the client device and the proxy, with the network communication engine through a predefined communication protocol; and
negotiate 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, wherein the set of communication standards comprises at least one flow aggregation and routing protocol.

12. The client device as claimed in claim 11, wherein the client communication engine further reports available network links and paths, and link quality of available network links and paths for routing of data packets, to the network communication engine.

13. A network connection engine for managing a multi-access bearer proxy corresponding to a multi connectivity client device, the network connection engine comprising:
a network connection engine processor;
a communication module coupled to the processor, the communication module is to:
establish a connection with a client communication engine, wherein the client communication engine manages uplink and downlink data packet routings of the client device; and
exchange communication capabilities of the proxy and the client device, with the client communication engine through a predefined communication protocol; and
a negotiating module coupled to the processor, the negotiating module is to negotiate a set of communication standards for managing flow aggregation and routing of data packets, with the client communication engine based on the exchanged communication capabilities, wherein the set of communication standards comprises at least one flow aggregation and routing protocol.

14. The network communication engine as claimed in claim 13, wherein the flow aggregation and routing protocol is one of a Generic Routing Encapsulation (GRE) tunneling protocol and a Multipath Transmission Protocol (TCP) (MPTCP).

15. The network communication engine as claimed in claim 13, further comprising sharing proxy details with the client communication engine for establishing uplink and downlink channels.
, Description:As Attached

Documents

Application Documents

# Name Date
1 201641023489-IntimationOfGrant06-02-2024.pdf 2024-02-06
1 Power of Attorney [08-07-2016(online)].pdf 2016-07-08
2 201641023489-PatentCertificate06-02-2024.pdf 2024-02-06
2 Form 5 [08-07-2016(online)].pdf 2016-07-08
3 Form 3 [08-07-2016(online)].pdf 2016-07-08
3 201641023489-Written submissions and relevant documents [02-02-2024(online)].pdf 2024-02-02
4 Drawing [08-07-2016(online)].pdf 2016-07-08
4 201641023489-FORM-26 [18-01-2024(online)].pdf 2024-01-18
5 Description(Complete) [08-07-2016(online)].pdf 2016-07-08
5 201641023489-FORM-26 [16-01-2024(online)].pdf 2024-01-16
6 Other Patent Document [03-08-2016(online)].pdf 2016-08-03
6 201641023489-Correspondence to notify the Controller [15-01-2024(online)].pdf 2024-01-15
7 201641023489-US(14)-HearingNotice-(HearingDate-18-01-2024).pdf 2023-12-20
7 201641023489-Form 1-080816.pdf 2016-08-18
8 201641023489-Correspondence-F1-080816.pdf 2016-08-18
8 201641023489-ABSTRACT [20-12-2022(online)].pdf 2022-12-20
9 201641023489-CLAIMS [20-12-2022(online)].pdf 2022-12-20
9 abstract 201641023489.jpg 2016-10-06
10 201641023489-FER_SER_REPLY [20-12-2022(online)].pdf 2022-12-20
10 REQUEST FOR CERTIFIED COPY [12-07-2017(online)].pdf 2017-07-12
11 201641023489-OTHERS [20-12-2022(online)].pdf 2022-12-20
11 Request For Certified Copy-Online.pdf 2017-07-14
12 201641023489-FORM 3 [10-01-2018(online)].pdf 2018-01-10
12 201641023489-PETITION UNDER RULE 137 [20-12-2022(online)].pdf 2022-12-20
13 201641023489-FORM 18 [12-06-2020(online)].pdf 2020-06-12
13 201641023489-FORM 3 [08-12-2022(online)].pdf 2022-12-08
14 201641023489-FER.pdf 2022-06-27
14 201641023489-MARKED COPIES OF AMENDEMENTS [29-01-2021(online)].pdf 2021-01-29
15 201641023489-AMMENDED DOCUMENTS [29-01-2021(online)].pdf 2021-01-29
15 201641023489-FORM 13 [29-01-2021(online)].pdf 2021-01-29
16 201641023489-AMMENDED DOCUMENTS [29-01-2021(online)].pdf 2021-01-29
16 201641023489-FORM 13 [29-01-2021(online)].pdf 2021-01-29
17 201641023489-MARKED COPIES OF AMENDEMENTS [29-01-2021(online)].pdf 2021-01-29
17 201641023489-FER.pdf 2022-06-27
18 201641023489-FORM 18 [12-06-2020(online)].pdf 2020-06-12
18 201641023489-FORM 3 [08-12-2022(online)].pdf 2022-12-08
19 201641023489-FORM 3 [10-01-2018(online)].pdf 2018-01-10
19 201641023489-PETITION UNDER RULE 137 [20-12-2022(online)].pdf 2022-12-20
20 201641023489-OTHERS [20-12-2022(online)].pdf 2022-12-20
20 Request For Certified Copy-Online.pdf 2017-07-14
21 201641023489-FER_SER_REPLY [20-12-2022(online)].pdf 2022-12-20
21 REQUEST FOR CERTIFIED COPY [12-07-2017(online)].pdf 2017-07-12
22 201641023489-CLAIMS [20-12-2022(online)].pdf 2022-12-20
22 abstract 201641023489.jpg 2016-10-06
23 201641023489-ABSTRACT [20-12-2022(online)].pdf 2022-12-20
23 201641023489-Correspondence-F1-080816.pdf 2016-08-18
24 201641023489-US(14)-HearingNotice-(HearingDate-18-01-2024).pdf 2023-12-20
24 201641023489-Form 1-080816.pdf 2016-08-18
25 Other Patent Document [03-08-2016(online)].pdf 2016-08-03
25 201641023489-Correspondence to notify the Controller [15-01-2024(online)].pdf 2024-01-15
26 Description(Complete) [08-07-2016(online)].pdf 2016-07-08
26 201641023489-FORM-26 [16-01-2024(online)].pdf 2024-01-16
27 Drawing [08-07-2016(online)].pdf 2016-07-08
27 201641023489-FORM-26 [18-01-2024(online)].pdf 2024-01-18
28 Form 3 [08-07-2016(online)].pdf 2016-07-08
28 201641023489-Written submissions and relevant documents [02-02-2024(online)].pdf 2024-02-02
29 Form 5 [08-07-2016(online)].pdf 2016-07-08
29 201641023489-PatentCertificate06-02-2024.pdf 2024-02-06
30 Power of Attorney [08-07-2016(online)].pdf 2016-07-08
30 201641023489-IntimationOfGrant06-02-2024.pdf 2024-02-06

Search Strategy

1 SearchHistoryAE_12-05-2023.pdf
1 SearchHistoryE_24-06-2022.pdf
2 SearchHistoryAE_12-05-2023.pdf
2 SearchHistoryE_24-06-2022.pdf

ERegister / Renewals

3rd: 22 Feb 2024

From 08/07/2018 - To 08/07/2019

4th: 22 Feb 2024

From 08/07/2019 - To 08/07/2020

5th: 22 Feb 2024

From 08/07/2020 - To 08/07/2021

6th: 22 Feb 2024

From 08/07/2021 - To 08/07/2022

7th: 22 Feb 2024

From 08/07/2022 - To 08/07/2023

8th: 22 Feb 2024

From 08/07/2023 - To 08/07/2024

9th: 22 Feb 2024

From 08/07/2024 - To 08/07/2025

10th: 09 Jun 2025

From 08/07/2025 - To 08/07/2026