Multi-connection system and method for service using internet protocol

• US 9,762,546 B2
• Filed: 06/27/2014
• Issued: 09/12/2017
• Est. Priority Date: 06/27/2013
• Status: Active Grant

• Current Assignee: Jeong Hoan Seo, Young Suk Lim
• Original Assignee: Jeong Hoan Seo, Young Suk Lim
• Inventors: Seo, Jeong Hoan, Lim, Young Suk
• Primary Examiner(s): LYNCH, SHARON S
• Application Number:
  US14/392,329
• Publication Number:
  US 20160173452A1
• Time in Patent Office: 1,173 Days
• CPC Class Codes: H04L 12/6418 Hybrid transport
• CPC Class Codes: H04L 41/0668 by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
• CPC Class Codes: H04L 45/24 Multipath
• CPC Class Codes: H04L 45/36 Backward learning
• CPC Class Codes: H04L 47/34 ensuring sequence integrity, e.g. using sequence numbers
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 61/5007 Internet protocol [IP] addresses
• CPC Class Codes: H04L 63/0281 Proxies
• CPC Class Codes: H04L 63/1458 Denial of Service
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/141 Setup of application sessions admission control or resource allocation in data switching networks H04L47/70
• CPC Class Codes: H04L 67/2866 Architectures; Arrangements
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 69/14 Multichannel or multilink protocols

Abstract

Disclosed are a multi-connection system (MCS) and method for a service using an Internet protocol. The MCS includes a plurality of proxies; an MCS client to receive a packet to be transmitted from the client to the server, generate MCS packets by adding an MCS sequence identification (ID) to the packet, and sequentially and respectively transmit the MCS packets to the plurality of proxies, wherein a number of MCS packets corresponds to a number of pieces of proxy access information connected to the plurality of proxies or a set number of pieces of proxy access information; and an MCS server to respectively receive the MCS packets from the plurality of proxies; extract the MCS sequence IDs from the MCS packets, compare the extracted MCS sequence IDs with MCS sequence IDs stored beforehand; store the extracted MCS sequence IDs, generate server-receivable packets from the MCS packets, and transmit the server-receivable packets to the server when the extracted MCS sequence IDs are not identical to the stored MCS sequence IDs; and block the MCS packets from being transmitted to the server when the extracted MCS sequence IDs are identical to the stored MCS sequence IDs.

Claims

1. A multi-connection system (MCS) configured to connect a client and a server in a multi-connection manner for a service using an Internet protocol, the MCS comprising:

a plurality of proxies;

an MCS client, configured such that when the client transmits forward packets to the server, the MCS client is configured to;

receive the forward packets from the client including a forward packet;

assign forward packet transmission priorities by assigning a forward packet transmission priority to each of the plurality of proxies, and

generate a forward MCS packet by adding a forward MCS sequence identification (ID) to the forward packet;

generate a plurality of forward MCS packets by reproducing the forward MCS packet by adding forward MCS sequence IDs to forward packets;

sequentially and respectively transmit the plurality of forward MCS packets to the plurality of proxies according to the forward packet transmission priorities,

wherein each forward packet transmission priority is set based on a time when the MCS client transmits a device-checking packet to each of the plurality of proxies and receives a response from each of the plurality of proxies, and

a number of the plurality of forward MCS packets corresponds to;

a number of the plurality of proxies;

or

a set number of pieces of proxy access information; and

the forward MCS sequence IDs added to the plurality of forward MCS packets are identical to each other; and

an MCS server device comprising a processor and memory configured to;

respectively receive the forward MCS packet from one of the plurality of proxies;

extract the forward MCS sequence ID from the forward MCS packet;

store the forward MCS sequence ID in the MCS server device in response to determining that a same forward MCS sequence ID as the forward MCS sequence ID is not stored;

generate a server-receivable packet from the forward MCS packet;

transmit the server-receivable packet to the server;

discard the forward MCS packet in response to determining that a same forward MCS sequence ID as the forward MCS sequence ID is stored in the MCS server device;

receive backward packets from the server including a backward packet, the backward packet sent from the server to the client;

generate a backward MCS packet by adding a backward MCS sequence identification (ID) to the backward packet;

generate a plurality of backward MCS packets by reproducing the backward MCS packet by adding backward MCS sequence IDs to the backward Packets; and

sequentially and respectively transmit the plurality of backward MCS packets to the plurality of proxies;

wherein;

a number of the plurality of backward MCS packets corresponds to;

a number of the plurality of proxies;

or

a set number of pieces of proxy access information; and

the backward MCS sequence IDs added to the plurality of backward MCS packets are identical to each other;

wherein the MCS client is further configured to;

respectively receive the backward MCS packet from one of the plurality of proxies;

detect and replace one of the plurality of proxies that failed with a new proxy corresponding to the proxy access information;

extract the backward MCS sequence ID from the backward MCS packet;

store the backward MCS sequence ID in the MCS client in response to determining that a same backward MCS sequence ID as the backward MCS sequence ID is not stored in the MCS client;

generate a client-receivable packet from the backward MCS packet;

transmit the client-receivable packet to the client; and

discard the backward MCS packet in response to determining that the same backward MCS sequence ID as the backward MCS sequence ID is stored in the MCS client.

2. The MCS of claim 1, wherein the MCS client is further configured to:

transmit a query requesting proxy access information to a domain name server (DNS) which uses or provides pieces of proxy access information;

receive the pieces of proxy access information from the DNS; and

use the pieces of proxy access information as the set number of pieces of proxy access information.

3. The MCS of claim 1, wherein the MCS client is further configured to:

store the set number of pieces of proxy access information in the MCS client by forming sessions with the plurality of proxies, and

generate the plurality of forward MCS packets corresponding to the set number of pieces of proxy access information by reproducing the forward MCS packet.

4. The MCS of claim 1, wherein, the MCS server device is further configured to:

assign backward packet transmission priorities by assigning a backward packet transmission priority to each of the plurality of proxies; and

sequentially and respectively transmit the plurality of backward MCS packets to the plurality of proxies according to each of the backward packet transmission priorities;

wherein each backward packet transmission priority is set based on an order in which individual packets of the plurality of forward MCS packets are received by the MCS server device from each of the plurality of proxies.

5. The MCS of claim 1, wherein the MCS client comprises a software program installed in the client or a software program installed in a device separate from the client.

6. The MCS of claim 1, wherein the MCS client comprises an MCS client device.

7. A method for a service using an Internet protocol using a multi-connection system (MCS) configured to connect a client and a server in a multi-connection manner, the method comprising:

receiving forward packets including a forward packet at a MCS client from the client;

generating with the MCS client, a forward MCS packet by adding a forward MCS sequence identification (ID) to the forward packet;

generating, with the MCS client, a plurality of forward MCS packets by reproducing the forward MCS packet by adding forward MCS sequence IDs to the forward packets, wherein a number of the plurality of forward MCS packets corresponds to a number of a plurality of proxies connected to the MCS or a set number of pieces of proxy access information, and the forward MCS sequence IDs added to the plurality of forward MCS packets are identical to each other;

assigning forward packet transmission priorities by assigning a forward packet transmission priority to each of the plurality of proxies with the MCS client, and

sequentially and respectively transmitting individual packets of the plurality of forward MCS packets, with the MCS client, to each of the plurality of proxies according to each of the forward packet transmission priorities, wherein each forward packet transmission priority is set based on a time when the MCS client transmits a device-checking packet to each of the plurality of proxies and receives a response from each of the plurality of proxies;

transmitting, with individual proxies of the plurality of proxies, each forward MCS packet of the plurality of forward MCS packets received from the MCS client to an MCS server device connected to the plurality of proxies;

receiving the forward MCS packet at the MCS server device from an individual proxy of the plurality of proxies;

extracting the forward MCS sequence ID included in the forward MCS packet with the MCS server device;

storing the forward MCS sequence ID with the MCS server device in response to determining that the same forward MCS sequence ID as the forward MCS sequence ID is not stored in the MCS server device;

generating a server-receivable packet from the forward MCS packet with the MCS server device;

transmitting the server-receivable packet with the MCS server device to the server;

discarding, with the MCS server device, the forward MCS packet received from the individual proxy of the plurality of proxies in response to determining that the same forward MCS sequence ID as the forward MCS sequence ID is stored in the MCS server device;

receiving backward packets including a backward packet at the MCS server device from the server;

generating, with the MCS server device, a backward MCS packet by adding a backward MCS sequence ID to the backward packet;

generating, with the MCS server device, a plurality of backward MCS packets by reproducing the backward MCS packet by adding backward MCS sequence IDs to the backward packets, wherein a number of the plurality of backward MCS packets corresponds to the number of the plurality of proxies or the set number of pieces of proxy access information, and the backward MCS sequence IDs added to the plurality of backward MCS packets are identical to each other; and

sequentially and respectively transmitting, with the MCS server device, the plurality of backward MCS packets to the plurality of proxies;

transmitting, with individual proxies of the plurality of proxies, the backward MCS packet received from the MCS server device to the MCS client;

extracting the backward MCS sequence ID included in the backward MCS packet received from one of the plurality of proxies with the MCS client;

storing the backward MCS sequence ID in response to determining that a same backward MCS sequence ID as the backward MCs sequence ID is not stored in the MCS client;

generating a client-receivable packet from the backward MCS packet with the MCs client;

transmitting the client-receivable packet to the client with the MCS client; and

discarding the backward MCS packet received from the one of the plurality of proxies with the MCS client in response to determining that a same backward MCS sequence ID as the backward MCS sequence ID is stored in the MCS client,

wherein when one of the plurality of proxies fails, the MCS client detects and replaces the one of the plurality of proxies that failed with a new proxy corresponding to the proxy access information.

8. The method of claim 7, further comprising storing the set number of pieces of proxy access information in the MCS client by forming sessions with the plurality of proxies with the MCS client, and wherein the generating the plurality of forward MCS packets comprises generating a plurality of forward MCS packets corresponding to the set number of pieces of proxy access information by reproducing the forward MCS packet.

9. The method of claim 7, further comprising:

assigning backward packet transmission priorities by assigning a backward packet transmission priority to each of the plurality of proxies with the MCS server device; and

wherein the sequentially and respectively transmitting of individual packets of the plurality of backward MCS packets to each of the plurality of proxies occurs according to each of the backward packet transmission priorities;

wherein each backward packet transmission priority is set based on an order in which the plurality of forward MCS packets are received at the MCS server device from each of the plurality of proxies.

10. The method of claim 7, further comprising

transmitting a query with the MCS client requesting proxy access information to a domain name server (DNS) which uses or provides pieces of proxy access information,

receiving the pieces of proxy access information from the DNS, and

using the pieces of proxy access information as the set number of pieces of proxy access information.

11. The method of claim 7, wherein the MCS client comprises a software program installed in the client or a software program installed in a device separate from the client.

12. The method of claim 7, wherein the MCS client comprises an MCS client device.