WO2022044226A1 - Communication system, communication method, communication device, and program - Google Patents

Communication system, communication method, communication device, and program Download PDF

Info

Publication number
WO2022044226A1
WO2022044226A1 PCT/JP2020/032477 JP2020032477W WO2022044226A1 WO 2022044226 A1 WO2022044226 A1 WO 2022044226A1 JP 2020032477 W JP2020032477 W JP 2020032477W WO 2022044226 A1 WO2022044226 A1 WO 2022044226A1
Authority
WO
WIPO (PCT)
Prior art keywords
packet
multipath
user terminal
option
service server
Prior art date
Application number
PCT/JP2020/032477
Other languages
French (fr)
Japanese (ja)
Inventor
智彦 池田
聖 成川
拓也 阿部
Original Assignee
日本電信電話株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 日本電信電話株式会社 filed Critical 日本電信電話株式会社
Priority to JP2022545173A priority Critical patent/JPWO2022044226A1/ja
Priority to PCT/JP2020/032477 priority patent/WO2022044226A1/en
Publication of WO2022044226A1 publication Critical patent/WO2022044226A1/en

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic control in data switching networks
    • H04L47/10Flow control; Congestion control
    • H04L47/34Flow control; Congestion control ensuring sequence integrity, e.g. using sequence numbers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/24Multipath
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic control in data switching networks
    • H04L47/10Flow control; Congestion control
    • H04L47/19Flow control; Congestion control at layers above the network layer
    • H04L47/193Flow control; Congestion control at layers above the network layer at the transport layer, e.g. TCP related

Definitions

  • the present disclosure relates to communication systems, communication methods, communication devices and programs for establishing multipath.
  • the transmitting side After establishing a TCP (Transmission Control Protocol) connection in the conventional MPTCP (Multipath TCP), the transmitting side stores the sequence number in the TCP option area, and separates and transmits. The receiving side read this sequence number and rearranged it to make the data consistent.
  • TCP Transmission Control Protocol
  • MPTCP Multipath TCP
  • the option area of TCP is used to establish a connection and send / receive data, the service used is limited to the TCP protocol, so that there is a problem in versatility.
  • the multipath technology was limited to the TCP protocol because it was premised on the use of TCP. Therefore, the purpose is to eliminate the dependence by the TCP protocol (L4) by realizing the multipath technology in L3 which is lower than the TCP / IP layer.
  • the communication system of the present disclosure is A communication system in which a service server and a user terminal are connected via a plurality of networks.
  • the service server and the user terminal have multiple interfaces connected via different networks.
  • One of the service server and the user terminal Divide one packet and Multipath information including the sequence number for restoring the one packet is stored in the header area of the IP packet.
  • the divided data obtained by dividing the one packet is transmitted from a plurality of interfaces.
  • the other of the service server and the user terminal Receive IP packets from multiple interfaces Read the multipath option information from the header area of the received IP packet and read it. Based on the sequence number included in the information of the multipath option, the divided data is integrated into the one packet.
  • the communication method of this disclosure is It is a method executed by a communication system in which a service server and a user terminal are connected via a plurality of networks.
  • the service server and the user terminal have multiple interfaces connected via different networks.
  • One of the service server and the user terminal Divide one packet and Multipath information including the sequence number for restoring the one packet is stored in the header area of the IP packet.
  • the divided data obtained by dividing the one packet is transmitted from a plurality of interfaces.
  • the other of the service server and the user terminal Receive IP packets from multiple interfaces Read the multipath option information from the header area of the received IP packet and read it. Based on the sequence number included in the information of the multipath option, the divided data is integrated into the one packet.
  • the communication device of the present disclosure is A communication device that is connected to other communication devices via multiple networks. With multiple interfaces connected to different networks, A transmission function that transmits divided data divided from one packet using multiple interfaces, A reception function that integrates divided data transmitted using multiple interfaces into the same packet, and Equipped with The transmission function is Divide one packet and Multipath information including the sequence number for restoring the one packet is stored in the header area of the IP packet. Using the IP packet, the divided data obtained by dividing the one packet is transmitted from a plurality of interfaces. The reception function is Receive IP packets from multiple interfaces Read the multipath option information from the header area of the received IP packet and read it. Based on the sequence number included in the information of the multipath option, the divided data is integrated into the one packet.
  • the program of the present disclosure is a program for realizing a computer as each functional unit provided in the communication device according to the present disclosure, and each step provided in the communication method executed by the communication device according to the present disclosure is performed by the computer. It is a program to be executed by.
  • the multipath technology can be realized without depending on the TCP protocol, and the multipath technology can be applied to services such as UDP and SIP.
  • An example of the system configuration of the present disclosure is shown.
  • An example of configuring an IP packet is shown.
  • the functional block diagram which concerns on this embodiment is shown. It is a flowchart which shows an example of the flow from the transmission of data to the reception between a user terminal 93 and a service server 93.
  • An example of the sequence of the flow management units 24 and 34 at the time of path establishment is shown. This is an operation example of the scheduler.
  • An example of an option area in an IP packet is shown.
  • An example of the IPv6 option storage area is shown.
  • An example of the IPv4 option storage area is shown.
  • An implementation example using an existing system is shown.
  • FIG. 1 shows an example of the system configuration of the present disclosure.
  • the service server 92 and the user terminal 93 establish a multipath by using a plurality of carrier networks 81 to 83.
  • MPTCP technology uses a packet scheduler after establishing a multipath by the option area of the TCP header, compares the RTT of each interface (hereinafter, may be referred to as "IF"), and sets the priority transmission order for each IF. decide. Based on this, the transmitting side arranges the sequence number in the TCP option area and transmits the packet. The receiver receives the packet, aligns the sequence numbers, and receives it.
  • the packet scheduler is realized by the MPTCP compatible kernel. Multipath establishment and sequence number placement / integration are realized by the TCP option.
  • the technique of the present disclosure is a function conventionally realized by MPTCP using TCP. Establishment of multipath (first technology) and Arrangement of sequence numbers, matching (second technology), Is realized by L3 without depending on the protocol. Specifically, the present disclosure realizes data transmission / reception by storing the data stored in the TCP option area in the IP header of the IP packet as shown in FIG.
  • FIG. 3 shows a functional block diagram according to the present embodiment.
  • the service server 92 includes IP communication units 21 and 22, an IP header area setting unit 23, a flow management unit 24, a scheduler 25, and an application control unit 26.
  • the user terminal 93 includes IP communication units 31 and 32, an IP header area setting unit 33, a flow management unit 34, a scheduler 35, and an application control unit 36.
  • the communication device of the present disclosure that is, the service server 92 and the user terminal 93 can also be realized by a computer and a program, and the program can be recorded on a recording medium or provided through a network.
  • the schedulers 25 and 35 separate and reintegrate data.
  • the schedulers 25 and 35 determine the priority order for each IF and determine the transmission IF of each packet.
  • a packet sequence number is determined in accordance with this, and instructions are given to the IP header area setting units 23 and 33.
  • the schedulers 25 and 35 are reintegrated based on the sequence numbers read by the IP header area setting units 23 and 33.
  • the flow management units 24 and 34 manage the main flow and the sub flow. After confirming the correspondence between the user terminal 93 and the service server 92 in the main flow, the subflow construction is started. The main flow and the sub flow are linked.
  • the IP header area setting units 23 and 33 read and write the IP header area based on the instructions of the flow management units 24 and 34.
  • the IP header area setting units 23 and 33 store each flow option in the IP header based on the instructions of the schedulers 25 and 35 and the flow management units 24 and 34.
  • the IP header area setting units 23 and 33 transmit the flow option information from the IP header to the flow management units 24 and 34. Other than that, it is transmitted to the schedulers 25 and 35.
  • the flow option information is the information described in the IP header for multipath packet matching, and includes, for example, the sequence number of the packet and which path of the multipath the received packet is.
  • the IP communication units 21, 22, 31, and 32 are IP communication units for each IF.
  • the method of associating the main flow and the sub-flow in the flow management units 24 and 34 is arbitrary, but for example, at the start of packet transmission, the transmitting side transmits the packet number correspondence table for each flow to the receiving side. As a result, the receiving side can link the main flow and the sub flow and sort the received packets separately.
  • the distribution rule for each path is that the sequence numbers 1 to 1000 are transmitted from the subflow 1 and the sequence numbers 1001 to 2000 are transmitted as the subflow 2.
  • the transmission / reception packet separation and matching system are established. For example, when the packet numbers common to the original packets are received by a plurality of IFs, the schedulers 25 and 35 detect the use of the plurality of IFs.
  • FIG. 4 is a flowchart showing an example of a flow from transmission of data to reception between the user terminal 93 and the service server 93.
  • FIG. 4 is a flowchart showing an example of a flow from transmission of data to reception between the user terminal 93 and the service server 93.
  • an example of transmission from the user terminal 93 to the service server 92 will be described, but the same applies to the case of transmission from the service server 92 to the user terminal 93.
  • the sender performs the following operations.
  • the scheduler 35 acquires a packet from the application control unit 36 (S111) and detects the use of a plurality of IFs (S112)
  • the multipath establishment scheme is started (S113).
  • the scheduler 35 determines the priority of the IF. According to this priority, the scheduler 35 divides the original packet acquired from the application control unit 36 and determines to which IF it is transmitted (S114). Further, the flow management unit 34 determines the flow option to be stored in the IP header (S115).
  • the flow option is, for example, a main flow session establishment option for establishing a main flow, a subflow session establishment option for establishing a subflow, and a sequence number for storing a sequence number used for separating / integrating signal packets. Storage option.
  • the IP header area setting unit 33 stores the sequence number and the flow option in the IP header (S116). After that, the IP communication units 31 and 32 use the IP packet to transmit the divided data divided in step S114 toward the receiving side (S117).
  • the receiving side performs the following operations.
  • the IP header area setting unit 23 reads the IP header (S122).
  • the sequence number and the flow option can be read from the IP header, and after confirming that the flow is multipath flow from the description of the flow option (S123), the IP header area setting unit 23 establishes the main flow to the flow management unit 24. Notify the content of the option to be used (S124).
  • the scheduler 25 reintegrates the divided data based on the sequence number, restores the original packet, and transmits the divided data to the application control unit 26 (S125). As described above, when the application control unit 26 receives the data (S126), the transmission / reception between the user terminal 93 and the service server 92 is completed.
  • FIG. 5 shows an example of the sequence of the flow management units 24 and 34 at the time of path establishment.
  • the user terminal A transmits an authentication key notification (Key-A) (S211).
  • the service server B detects that it has received the authentication key notification from the user terminal A, it transmits an authentication key notification (Key-B) (S212).
  • the user terminal A confirms that the authentication keys A and B match, and transmits an authentication key notification (Key-A, Key-B) (S213).
  • the user terminal A transmits a main flow notification (S221).
  • This notification includes information on the IP addresses of Token and IF2.
  • the service server B identifies the main session by Token, calculates the authentication code B using Key-B, and transmits the authentication code notification (S222).
  • This authentication code notification includes the authentication code B of the service server B and the IP-B which is the IP address of the service server B.
  • the user terminal A calculates the authentication code A from the Key-A and transmits the authentication code notification (authentication code A
  • step S222 MPTCP compatibility is confirmed in parallel with the TCP session operation by using the TCP option area.
  • step S222 the user terminal A transmits HMAC-B calculated from Key-B and authenticates.
  • step S223 the service server B transmits the HMAC-A calculated from the Key-A and authenticates the HMAC-A.
  • step S223 conventionally, if the user terminal and the service server support MPTCP, an MPTCP session is established and a subsession is established.
  • the flow management units 24 and 34 establish the main flow and subflow at L3. Regardless of whether the connection is established or not, the subflow process is started after exchanging the authentication key notification by the IP option. By associating the main flow and the subflow with the authentication key, appropriate packet division and integration can be performed.
  • the authentication code for example, HMAC (Hash-based Message Authentication Code) can be exemplified.
  • the schedulers 25 and 35 manage the sequence number and the option storage area. Sequence management: The schedulers 25 and 35 store the sequence number of each packet transmitted using multipath. Before transmitting the data of each packet from each IF, the IP header area setting units 23 and 33 store the sequence number in the IP header. This is a centralized sequence number between multipaths, and the receiving side can consolidate packets between multipaths by confirming this.
  • FIG. 7 shows an example of the option storage area.
  • the IP header contains an option storage area.
  • the IP header of 12 to 60 Byte includes an option number storage area (1Byte), a storage area of length N (1Byte), and an option value storage area (1Byte).
  • the IP header area setting units 23 and 33 store flow options and sequence numbers in the option storage area of the IP header.
  • the identifier indicating the main flow session establishment option is stored in the option number storage area, and Key-A and Key-B shown in FIG. 5 are stored in the option value storage area.
  • the identifier indicating the subflow session establishment option is stored in the option number storage area, and the Token, IF2-IP, IP-B, and authentication codes A and B shown in FIG. 5 are stored in the option value storage area. do.
  • the sequence number storage option the identifier indicating the sequence number storage option is stored in the option number storage area, and the sequence number is stored in the option value storage area.
  • FIG. 8 shows an example of the IPv6 option storage area (see, for example, Non-Patent Document 2).
  • An IPv6 packet has an area called an IPv6 extension header that reads only a specified destination. Since only the specified destination is read in this area, the relay node does not malfunction even if arbitrary data is stored. Therefore, it can be replaced freely. Therefore, by inserting an arbitrary flow option in this area, the multipath is established (first technique) and the sequence number is stored (second technique) between the user terminal 93 and the service server 92. You may.
  • FIG. 9 shows an example of the IPv4 option storage area.
  • An IPv4 header option is present in an IPv4 packet (see, for example, Patent Document 1).
  • the value to be inserted in this area is defined as an optional value, and if any value is stored, the relay node may malfunction. Therefore, the IP header area setting units 23 and 33 are provided with an option final position designation display function.
  • the option final position specification display function specifies the area for inputting the specified option value, and inserts an arbitrary value after it. Store multipath options in this area. As a result, the relay node can read the value input by the option final position designation display function by the IP header area setting units 23 and 33 of the destination device on the receiving side without causing a malfunction.
  • FIG. 10 shows an implementation example using an existing system.
  • the MPTCP kernel divides and integrates packets by the scheduler 15. Therefore, the scheduler 15 (kernel implementation), that is, the schedulers 25 and 35 of the present embodiment can be realized by utilizing the existing implementation of MPTCP.
  • the IP conversion unit / IP header storage unit 17 converts the IP header format and stores it in the IP header. Therefore, the TCP option area setting unit 13, that is, the IP header area setting units 23 and 33 of the present embodiment can be realized by utilizing the conventional MPTCP function.
  • This disclosure can be applied to the information and communication industry.
  • IP communication unit 23 IP header area setting unit 24
  • Flow management unit 25 35: Scheduler 26, 36: Application control unit 81, 82, 83: Carrier network 92: Service Server 93: User terminal

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The objective of the present disclosure is to realize multipath technology in L3, which is a lower layer than a TCP/IP layer, thereby eliminating dependency due to the TCP protocol. The present disclosure provides a communication system in which a service server and a user terminal are connected by way of a plurality of networks, wherein: the service server and the user terminal are provided with a plurality of interfaces that are connected by way of different networks; one of the service server and the user terminal divides one packet, stores multipath information including a sequence number for restoring the one packet in a header area of one or more IP packets, and uses the IP packets to transmit divided data, obtained by dividing the one packet, from the plurality of interfaces; and the other of the service server and the user terminal receives each IP packet from the plurality of interfaces, reads multipath option information from the header area of the received IP packet, and integrates the divided data into the one packet on the basis of the sequence numbers contained in the multipath option information.

Description

通信システム、通信方法、通信装置及びプログラムCommunication systems, communication methods, communication devices and programs
 本開示は、マルチパスを確立するための通信システム、通信方法、通信装置及びプログラムに関する。 The present disclosure relates to communication systems, communication methods, communication devices and programs for establishing multipath.
 従来MPTCP(Multipath TCP)においてTCP(Transmission Control Protocol)コネクション確立後、送信側はTCPオプション領域にシーケンス番号を格納し、分離、送信を行う。受信側はこのシーケンス番号を読み取り、並び替えることでデータの整合を取っていた。従来MPTCPにおいてはTCPのオプション領域を利用し、コネクション確立、データ送受信を行うため利用サービスがTCPプロトコルに限定されるため汎用性に問題があった。 After establishing a TCP (Transmission Control Protocol) connection in the conventional MPTCP (Multipath TCP), the transmitting side stores the sequence number in the TCP option area, and separates and transmits. The receiving side read this sequence number and rearranged it to make the data consistent. Conventionally, in MPTCP, since the option area of TCP is used to establish a connection and send / receive data, the service used is limited to the TCP protocol, so that there is a problem in versatility.
特開2005-328427号公報Japanese Unexamined Patent Publication No. 2005-328427
 TCPの利用を前提にしているためマルチパス技術はTCPプロトコルに限定されるという問題があった。そこでマルチパス技術をTCP/IP層よりも下層のL3で実現することでTCPプロトコル(L4)による依存をなくすことを目的とする。 There was a problem that the multipath technology was limited to the TCP protocol because it was premised on the use of TCP. Therefore, the purpose is to eliminate the dependence by the TCP protocol (L4) by realizing the multipath technology in L3 which is lower than the TCP / IP layer.
 本開示の通信システムは、
 サービスサーバ及び利用者端末が複数のネットワークを介して接続されている通信システムであって、
 サービスサーバ及び利用者端末は、異なるネットワークを介して接続されている複数のインタフェースを備え、
 サービスサーバ及び利用者端末の一方が、
 1つのパケットを分割し、
 IPパケットのヘッダ領域に、前記1つのパケットを復元するためのシーケンス番号を含むマルチパスの情報を格納し、
 当該IPパケットを用いて、前記1つのパケットが分割された分割データを、複数のインタフェースから送信し、
 サービスサーバ及び利用者端末の他方が、
 複数のインタフェースからIPパケットを受信し、
 受信したIPパケットのヘッダ領域からマルチパスオプションの情報を読み出し、
 マルチパスオプションの情報に含まれるシーケンス番号に基づき、前記分割データを前記1つのパケットに統合する。
The communication system of the present disclosure is
A communication system in which a service server and a user terminal are connected via a plurality of networks.
The service server and the user terminal have multiple interfaces connected via different networks.
One of the service server and the user terminal
Divide one packet and
Multipath information including the sequence number for restoring the one packet is stored in the header area of the IP packet.
Using the IP packet, the divided data obtained by dividing the one packet is transmitted from a plurality of interfaces.
The other of the service server and the user terminal
Receive IP packets from multiple interfaces
Read the multipath option information from the header area of the received IP packet and read it.
Based on the sequence number included in the information of the multipath option, the divided data is integrated into the one packet.
 本開示の通信方法は、
 サービスサーバ及び利用者端末が複数のネットワークを介して接続されている通信システムが実行する方法であって、
 サービスサーバ及び利用者端末は、異なるネットワークを介して接続されている複数のインタフェースを備え、
 サービスサーバ及び利用者端末の一方が、
 1つのパケットを分割し、
 IPパケットのヘッダ領域に、前記1つのパケットを復元するためのシーケンス番号を含むマルチパスの情報を格納し、
 当該IPパケットを用いて、前記1つのパケットが分割された分割データを、複数のインタフェースから送信し、
 サービスサーバ及び利用者端末の他方が、
 複数のインタフェースからIPパケットを受信し、
 受信したIPパケットのヘッダ領域からマルチパスオプションの情報を読み出し、
 マルチパスオプションの情報に含まれるシーケンス番号に基づき、前記分割データを前記1つのパケットに統合する。
The communication method of this disclosure is
It is a method executed by a communication system in which a service server and a user terminal are connected via a plurality of networks.
The service server and the user terminal have multiple interfaces connected via different networks.
One of the service server and the user terminal
Divide one packet and
Multipath information including the sequence number for restoring the one packet is stored in the header area of the IP packet.
Using the IP packet, the divided data obtained by dividing the one packet is transmitted from a plurality of interfaces.
The other of the service server and the user terminal
Receive IP packets from multiple interfaces
Read the multipath option information from the header area of the received IP packet and read it.
Based on the sequence number included in the information of the multipath option, the divided data is integrated into the one packet.
 本開示の通信装置は、
 複数のネットワークを介して他の通信装置と接続されている通信装置であって、
 異なるネットワークに接続されている複数のインタフェースと、
 1つのパケットから分割された分割データを、複数のインタフェースを用いて送信する送信機能と、
 複数のインタフェースを用いて送信された分割データを前記1つのパケットに統合する受信機能と、
 を備え、
 前記送信機能は、
 1つのパケットを分割し、
 IPパケットのヘッダ領域に、前記1つのパケットを復元するためのシーケンス番号を含むマルチパスの情報を格納し、
 当該IPパケットを用いて、前記1つのパケットが分割された分割データを、複数のインタフェースから送信し、
 前記受信機能は、
 複数のインタフェースからIPパケットを受信し、
 受信したIPパケットのヘッダ領域からマルチパスオプションの情報を読み出し、
 マルチパスオプションの情報に含まれるシーケンス番号に基づき、前記分割データを前記1つのパケットに統合する。
The communication device of the present disclosure is
A communication device that is connected to other communication devices via multiple networks.
With multiple interfaces connected to different networks,
A transmission function that transmits divided data divided from one packet using multiple interfaces,
A reception function that integrates divided data transmitted using multiple interfaces into the same packet, and
Equipped with
The transmission function is
Divide one packet and
Multipath information including the sequence number for restoring the one packet is stored in the header area of the IP packet.
Using the IP packet, the divided data obtained by dividing the one packet is transmitted from a plurality of interfaces.
The reception function is
Receive IP packets from multiple interfaces
Read the multipath option information from the header area of the received IP packet and read it.
Based on the sequence number included in the information of the multipath option, the divided data is integrated into the one packet.
 具体的には、本開示のプログラムは、本開示に係る通信装置に備わる各機能部としてコンピュータを実現させるためのプログラムであり、本開示に係る通信装置が実行する通信方法に備わる各ステップをコンピュータに実行させるためのプログラムである。 Specifically, the program of the present disclosure is a program for realizing a computer as each functional unit provided in the communication device according to the present disclosure, and each step provided in the communication method executed by the communication device according to the present disclosure is performed by the computer. It is a program to be executed by.
 本開示によれば、マルチパス技術をTCPプロトコルに依存することなく実現することができ、UDPやSIP等のサービスにもマルチパス技術を適用することが可能となる。 According to the present disclosure, the multipath technology can be realized without depending on the TCP protocol, and the multipath technology can be applied to services such as UDP and SIP.
本開示のシステム構成の一例を示す。An example of the system configuration of the present disclosure is shown. IPパケットの構成例を示す。An example of configuring an IP packet is shown. 本実施形態に係る機能ブロック図を示す。The functional block diagram which concerns on this embodiment is shown. 利用者端末93-サービスサーバ93間でデータを送信してから受信するまでの流れの一例を示すフローチャートである。It is a flowchart which shows an example of the flow from the transmission of data to the reception between a user terminal 93 and a service server 93. パス確立時におけるフロー管理部24及び34のシーケンスの一例を示す。An example of the sequence of the flow management units 24 and 34 at the time of path establishment is shown. スケジューラの動作例である。This is an operation example of the scheduler. IPパケットにおけるオプション領域の一例を示す。An example of an option area in an IP packet is shown. IPv6オプション格納領域の一例を示す。An example of the IPv6 option storage area is shown. IPv4オプション格納領域の一例を示す。An example of the IPv4 option storage area is shown. 既存システムを利用した実装例を示す。An implementation example using an existing system is shown.
 以下、本開示の実施形態について、図面を参照しながら詳細に説明する。なお、本開示は、以下に示す実施形態に限定されるものではない。これらの実施の例は例示に過ぎず、本開示は当業者の知識に基づいて種々の変更、改良を施した形態で実施することができる。なお、本明細書及び図面において符号が同じ構成要素は、相互に同一のものを示すものとする。 Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. The present disclosure is not limited to the embodiments shown below. Examples of these implementations are merely examples, and the present disclosure can be implemented in various modified and improved forms based on the knowledge of those skilled in the art. In addition, the components having the same reference numerals in the present specification and the drawings shall indicate the same components.
(本開示のポイント)
 図1に本開示のシステム構成の一例を示す。本開示の通信システムは、サービスサーバ92及び利用者端末93が複数のキャリアネットワーク81~83を用いてマルチパスを確立する。
(Points of this disclosure)
FIG. 1 shows an example of the system configuration of the present disclosure. In the communication system of the present disclosure, the service server 92 and the user terminal 93 establish a multipath by using a plurality of carrier networks 81 to 83.
 従来MPTCP技術はTCPヘッダのオプション領域によりマルチパスを確立後、パケットスケジューラを利用し、各インタフェース(以下、「IF」と称する場合がある。)のRTTを比較し、IFごとに優先送信順位を決定する。送信側は、これに基づいて、TCPオプション領域にシーケンス番号を配置し、パケットを送信する。受信側は、パケットを受け取り、シーケンス番号の順序の整合を取り、受信する。これらの処理のうち、パケットスケジューラはMPTCP対応カーネルにより実現している。マルチパス確立とシーケンス番号配置・統合はTCPオプションにより実現している。 Conventionally, MPTCP technology uses a packet scheduler after establishing a multipath by the option area of the TCP header, compares the RTT of each interface (hereinafter, may be referred to as "IF"), and sets the priority transmission order for each IF. decide. Based on this, the transmitting side arranges the sequence number in the TCP option area and transmits the packet. The receiver receives the packet, aligns the sequence numbers, and receives it. Of these processes, the packet scheduler is realized by the MPTCP compatible kernel. Multipath establishment and sequence number placement / integration are realized by the TCP option.
 本開示の技術は、従来MPTCPがTCPを利用して実現していた機能である、
 マルチパスの確立(第1の技術)と、
 シーケンス番号の配置、整合(第2の技術)と、
 を、L3によってプロトコル依存なしに実現する。
 具体的には、本開示は、TCPオプション領域に格納していたデータを図2に示すようなIPパケットにおけるIPヘッダに格納することでデータ送受信を実現する。
The technique of the present disclosure is a function conventionally realized by MPTCP using TCP.
Establishment of multipath (first technology) and
Arrangement of sequence numbers, matching (second technology),
Is realized by L3 without depending on the protocol.
Specifically, the present disclosure realizes data transmission / reception by storing the data stored in the TCP option area in the IP header of the IP packet as shown in FIG.
(本開示による効果)
 L3レイヤでマルチパスの前記第1及び第2の技術を実現することで、TCPプロトコルに依存することなく、シームレスハンドーオーバーを実現できる。これにより、UDP(User Datagram Protocol)、SIP(Session Initiation Protocol)等のサービスにもマルチパス技術を適用でき、利用者端末93がキャリアネットワーク81から82に切り替わる際のハンドオーバー時にも安定した通信ができるようになる。
(Effect of this disclosure)
By realizing the first and second technologies of multipath in the L3 layer, seamless handover can be realized without depending on the TCP protocol. As a result, multi-pass technology can be applied to services such as UDP (User Datagram Protocol) and SIP (Session Initiation Protocol), and stable communication can be achieved even during handover when the user terminal 93 switches from carrier network 81 to 82. become able to.
(第1の実施形態)
 図3に、本実施形態に係る機能ブロック図を示す。サービスサーバ92は、IP通信部21及び22、IPヘッダ領域設定部23、フロー管理部24、スケジューラ25、アプリケーション制御部26を備える。利用者端末93は、IP通信部31及び32、IPヘッダ領域設定部33、フロー管理部34、スケジューラ35、アプリケーション制御部36を備える。本開示の通信装置、すなわちサービスサーバ92及び利用者端末93は、コンピュータとプログラムによっても実現でき、プログラムを記録媒体に記録することも、ネットワークを通して提供することも可能である。
(First Embodiment)
FIG. 3 shows a functional block diagram according to the present embodiment. The service server 92 includes IP communication units 21 and 22, an IP header area setting unit 23, a flow management unit 24, a scheduler 25, and an application control unit 26. The user terminal 93 includes IP communication units 31 and 32, an IP header area setting unit 33, a flow management unit 34, a scheduler 35, and an application control unit 36. The communication device of the present disclosure, that is, the service server 92 and the user terminal 93 can also be realized by a computer and a program, and the program can be recorded on a recording medium or provided through a network.
 スケジューラ25、35は、データの分離、再統合を行う。
 送信側の場合、スケジューラ25、35は、IFごとの優先順位を決定し、各パケットの送信IFを決定する。これに合わせてパケットのシーケンス番号を決定し、IPヘッダ領域設定部23、33へ指示する。
 受信側の場合、スケジューラ25、35は、IPヘッダ領域設定部23、33で読み取ったシーケンス番号を基に再統合する。
 フロー管理部24、34は、メインフロー、サブフローを管理する。メインフローで利用者端末93-サービスサーバ92間の対応確認後、サブフロー構築を開始する。メインフローとサブフローの紐づけを行っている。
 IPヘッダ領域設定部23、33は、フロー管理部24、34の指示を基にIPヘッダ領域の読取・書込を行う。
 送信側の場合、IPヘッダ領域設定部23、33は、スケジューラ25、35、フロー管理部24、34の指示を基に各フローオプションをIPヘッダに格納する。
 受信側の場合、IPヘッダ領域設定部23、33は、IPヘッダからのフローオプションの情報をフロー管理部24、34へ伝送。それ以外はスケジューラ25、35へ伝送する。ここで、フローオプションの情報は、マルチパスのパケット整合をとるためのIPヘッダ記載の情報であり、例えば、パケットのシーケンス番号、届いたパケットがマルチパスのうちのどのパスなのかを含む。
 IP通信部21、22、31、32は、IFごとのIP通信部である。
The schedulers 25 and 35 separate and reintegrate data.
On the transmitting side, the schedulers 25 and 35 determine the priority order for each IF and determine the transmission IF of each packet. A packet sequence number is determined in accordance with this, and instructions are given to the IP header area setting units 23 and 33.
On the receiving side, the schedulers 25 and 35 are reintegrated based on the sequence numbers read by the IP header area setting units 23 and 33.
The flow management units 24 and 34 manage the main flow and the sub flow. After confirming the correspondence between the user terminal 93 and the service server 92 in the main flow, the subflow construction is started. The main flow and the sub flow are linked.
The IP header area setting units 23 and 33 read and write the IP header area based on the instructions of the flow management units 24 and 34.
On the transmitting side, the IP header area setting units 23 and 33 store each flow option in the IP header based on the instructions of the schedulers 25 and 35 and the flow management units 24 and 34.
On the receiving side, the IP header area setting units 23 and 33 transmit the flow option information from the IP header to the flow management units 24 and 34. Other than that, it is transmitted to the schedulers 25 and 35. Here, the flow option information is the information described in the IP header for multipath packet matching, and includes, for example, the sequence number of the packet and which path of the multipath the received packet is.
The IP communication units 21, 22, 31, and 32 are IP communication units for each IF.
 フロー管理部24、34におけるメインフローとサブフローの紐づけ方法は任意であるが、例えば、パケット送信開始時に送信側は受信側へフローごとのパケット番号対応表を送信する。それによって、受信側はメインフロー、サブフローを紐づけし別々に受け取ったパケットを並び替えることができる。なお、ここではパスごとの振り分けのルールはシーケンス番号1~1000番目をサブフロー1から送信、シーケンス番号1001~2000をサブフロー2と送るものとする。このデータ送信開始時に送信側から送られるパケット番号対応表に基づいて、送受信のパケット分離、整合体制が確立される。例えば、オリジナルのパケットが共通するパケット番号を複数のIFで受信した場合、スケジューラ25、35は複数IFの利用を検知する。 The method of associating the main flow and the sub-flow in the flow management units 24 and 34 is arbitrary, but for example, at the start of packet transmission, the transmitting side transmits the packet number correspondence table for each flow to the receiving side. As a result, the receiving side can link the main flow and the sub flow and sort the received packets separately. Here, it is assumed that the distribution rule for each path is that the sequence numbers 1 to 1000 are transmitted from the subflow 1 and the sequence numbers 1001 to 2000 are transmitted as the subflow 2. Based on the packet number correspondence table sent from the transmitting side at the start of this data transmission, the transmission / reception packet separation and matching system are established. For example, when the packet numbers common to the original packets are received by a plurality of IFs, the schedulers 25 and 35 detect the use of the plurality of IFs.
(送受信フロー)
 図4は、利用者端末93-サービスサーバ93間でデータを送信してから受信するまでの流れの一例を示すフローチャートである。以下では利用者端末93からサービスサーバ92に送信する例について説明するが、サービスサーバ92から利用者端末93に送信する場合も同様である。
(Transmission / reception flow)
FIG. 4 is a flowchart showing an example of a flow from transmission of data to reception between the user terminal 93 and the service server 93. Hereinafter, an example of transmission from the user terminal 93 to the service server 92 will be described, but the same applies to the case of transmission from the service server 92 to the user terminal 93.
 送信側は以下の動作を実行する。
 スケジューラ35がアプリケーション制御部36からパケットを取得し(S111)、複数IFの利用を検知すると(S112)、マルチパス確立スキームが開始される(S113)。
 このスキーム開始後、スケジューラ35はIFの優先度を決定する。この優先度に従い、スケジューラ35は、アプリケーション制御部36から取得したオリジナルのパケットを分割し、どのIFに送信するのか決定する(S114)。
 また、フロー管理部34はIPヘッダに格納するフローオプションを決定する(S115)。フローオプションは、例えば、メインフローを確立するためのメインフローセッション確立オプション、サブフローを確立するためのサブフローセッション確立オプション、及び信号パケットの分離・統合を行うために使用するシーケンス番号を格納するシーケンス番号格納オプションである。
 スケジューラ35とフロー管理部34の指示を受けて、IPヘッダ領域設定部33はシーケンス番号、フローオプションをIPヘッダに格納する(S116)。
 その後、IP通信部31、32が、当該IPパケットを用いて、ステップS114で分割された分割データを、受信側に向けて送信する(S117)。
The sender performs the following operations.
When the scheduler 35 acquires a packet from the application control unit 36 (S111) and detects the use of a plurality of IFs (S112), the multipath establishment scheme is started (S113).
After starting this scheme, the scheduler 35 determines the priority of the IF. According to this priority, the scheduler 35 divides the original packet acquired from the application control unit 36 and determines to which IF it is transmitted (S114).
Further, the flow management unit 34 determines the flow option to be stored in the IP header (S115). The flow option is, for example, a main flow session establishment option for establishing a main flow, a subflow session establishment option for establishing a subflow, and a sequence number for storing a sequence number used for separating / integrating signal packets. Storage option.
In response to the instructions of the scheduler 35 and the flow management unit 34, the IP header area setting unit 33 stores the sequence number and the flow option in the IP header (S116).
After that, the IP communication units 31 and 32 use the IP packet to transmit the divided data divided in step S114 toward the receiving side (S117).
 受信側は以下の動作を実行する。
 IP通信部21、22はIPパケットを受信後(S121)、IPヘッダ領域設定部23がIPヘッダの読み込みを行う(S122)。IPヘッダからシーケンス番号及びフローオプションを読み込むことができ、フローオプションの記載からマルチパスフローであることを確認したら(S123)、IPヘッダ領域設定部23は、フロー管理部24へメインフローの確立に用いるオプション内容を通知する(S124)。
 その後、スケジューラ25は分割された分割データを、シーケンス番号を基に再統合を行い、オリジナルのパケットに復元し、アプリケーション制御部26へ送信する(S125)。
 以上、アプリケーション制御部26がデータを受信することで(S126)、利用者端末93、サービスサーバ92間送受信が完了する。
The receiving side performs the following operations.
After the IP communication units 21 and 22 receive the IP packet (S121), the IP header area setting unit 23 reads the IP header (S122). The sequence number and the flow option can be read from the IP header, and after confirming that the flow is multipath flow from the description of the flow option (S123), the IP header area setting unit 23 establishes the main flow to the flow management unit 24. Notify the content of the option to be used (S124).
After that, the scheduler 25 reintegrates the divided data based on the sequence number, restores the original packet, and transmits the divided data to the application control unit 26 (S125).
As described above, when the application control unit 26 receives the data (S126), the transmission / reception between the user terminal 93 and the service server 92 is completed.
 図5に、パス確立時におけるフロー管理部24及び34のシーケンスの一例を示す。
 利用者端末Aが認証キー通知(Key-A)を送信する(S211)。サービスサーバBは、利用者端末Aから認証キー通知を受け取ったことを検知すると、認証キー通知(Key-B)を送信する(S212)。利用者端末Aは、認証キーA及びBが一致することを確認し、認証キー通知(Key-A,Key-B)を送信する(S213)。これにより、サブフロープロセスが開始される。
 利用者端末Aは、メインフロー通知を送信する(S221)。この通知には、Token、及びIF2のIPアドレスの情報が含まれる。サービスサーバBは、Tokenによりメインセッションを特定し、Key-Bを用いて認証コードBを算出し、認証コード通知を送信する(S222)。この認証コード通知には、サービスサーバBの認証コードB、及びサービスサーバBのIPアドレスであるIP-Bが含まれる。利用者端末Aは、Key-Aから認証コードAを算出し、認証コード通知(認証コードA)を送信する(S223)。
FIG. 5 shows an example of the sequence of the flow management units 24 and 34 at the time of path establishment.
The user terminal A transmits an authentication key notification (Key-A) (S211). When the service server B detects that it has received the authentication key notification from the user terminal A, it transmits an authentication key notification (Key-B) (S212). The user terminal A confirms that the authentication keys A and B match, and transmits an authentication key notification (Key-A, Key-B) (S213). This starts the subflow process.
The user terminal A transmits a main flow notification (S221). This notification includes information on the IP addresses of Token and IF2. The service server B identifies the main session by Token, calculates the authentication code B using Key-B, and transmits the authentication code notification (S222). This authentication code notification includes the authentication code B of the service server B and the IP-B which is the IP address of the service server B. The user terminal A calculates the authentication code A from the Key-A and transmits the authentication code notification (authentication code A) (S223).
 従来は、各ステップにおいて、TCPオプション領域を利用することでTCPセッション動作に並行して、MPTCP対応確認を行う。例えば、ステップS222において、利用者端末Aは、Key-Bから算出したHMAC-Bを送信し、認証する。そしてステップS223において、サービスサーバBは、Key-Aから算出したHMAC-Aを送信し、認証する。このように、従来は、利用者端末-サービスサーバ間がMPTCP対応しているならば、MPTCPセッションを確立し、サブセッションを確立する。 Conventionally, in each step, MPTCP compatibility is confirmed in parallel with the TCP session operation by using the TCP option area. For example, in step S222, the user terminal A transmits HMAC-B calculated from Key-B and authenticates. Then, in step S223, the service server B transmits the HMAC-A calculated from the Key-A and authenticates the HMAC-A. As described above, conventionally, if the user terminal and the service server support MPTCP, an MPTCP session is established and a subsession is established.
 フロー管理部24及び34は、L3でメインフロー、サブフロー確立を行う。コネクション確立有無に関わらず、IPオプションによる認証キー通知のやり取り後、サブフロープロセスを開始する。認証キーによってメインフローとサブフローの関連付けを行うことで、適切なパケット分割、統合ができるようになる。認証コードは、例えばHMAC(Hash-based Message Authentication Code)が例示できる。 The flow management units 24 and 34 establish the main flow and subflow at L3. Regardless of whether the connection is established or not, the subflow process is started after exchanging the authentication key notification by the IP option. By associating the main flow and the subflow with the authentication key, appropriate packet division and integration can be performed. As the authentication code, for example, HMAC (Hash-based Message Authentication Code) can be exemplified.
 図6を参照しながら、スケジューラの動作例を説明する。スケジューラ25及び35は、シーケンス番号及びオプション格納領域の管理を行う。
 シーケンス管理:スケジューラ25及び35は、マルチパスを用いて送信する各パケットのシーケンス番号を格納する。各IFから各パケットのデータ送信前に、IPヘッダ領域設定部23、33はIPヘッダにシーケンス番号を格納する。これはマルチパス間で一元化されたシーケンス番号であり、受信側はこれを確認することでマルチパス間でのパケットを統合することができる。
An operation example of the scheduler will be described with reference to FIG. The schedulers 25 and 35 manage the sequence number and the option storage area.
Sequence management: The schedulers 25 and 35 store the sequence number of each packet transmitted using multipath. Before transmitting the data of each packet from each IF, the IP header area setting units 23 and 33 store the sequence number in the IP header. This is a centralized sequence number between multipaths, and the receiving side can consolidate packets between multipaths by confirming this.
 図7に、オプション格納領域の一例を示す。IPヘッダには、オプション格納領域が含まれる。例えば、12~60ByteのIPヘッダに、オプション番号格納領域(1Byte)、長さNの格納領域(1Byte)、オプション値の格納領域(1Byte)を含む。IPヘッダ領域設定部23、33は、フローオプション、シーケンス番号をIPヘッダのオプション格納領域に格納する。 FIG. 7 shows an example of the option storage area. The IP header contains an option storage area. For example, the IP header of 12 to 60 Byte includes an option number storage area (1Byte), a storage area of length N (1Byte), and an option value storage area (1Byte). The IP header area setting units 23 and 33 store flow options and sequence numbers in the option storage area of the IP header.
 例えば、メインフローセッション確立オプションの場合、メインフローセッション確立オプションを示す識別子をオプション番号格納領域に格納し、図5に示すKey-A,Key-Bをオプション値の格納領域に格納する。サブフローセッション確立オプションの場合、サブフローセッション確立オプションを示す識別子をオプション番号格納領域に格納し、図5に示すToken,IF2-IP,IP-B,認証コードA,Bをオプション値の格納領域に格納する。シーケンス番号格納オプションの場合、シーケンス番号格納オプションを示す識別子をオプション番号格納領域に格納し、シーケンス番号をオプション値の格納領域に格納する。 For example, in the case of the main flow session establishment option, the identifier indicating the main flow session establishment option is stored in the option number storage area, and Key-A and Key-B shown in FIG. 5 are stored in the option value storage area. In the case of the subflow session establishment option, the identifier indicating the subflow session establishment option is stored in the option number storage area, and the Token, IF2-IP, IP-B, and authentication codes A and B shown in FIG. 5 are stored in the option value storage area. do. For the sequence number storage option, the identifier indicating the sequence number storage option is stored in the option number storage area, and the sequence number is stored in the option value storage area.
(IPv6拡張ヘッダ)
 図8に、IPv6オプション格納領域の一例を示す(例えば、非特許文献2参照。)。IPv6パケットにはIPv6拡張ヘッダと呼ばれる指定した宛先しか読み込みを行わない領域が存在する。この領域では指定した宛先しか読み込みを行わないので、任意のデータを格納したとしても中継ノードが誤作動を行うことはない。そのため、自由に付け替えが可能である。そこで、この領域に任意のフローオプションを挿入することで、利用者端末93及びサービスサーバ92間で、マルチパスの確立(第1の技術)、及びシーケンス番号の格納(第2の技術)を行ってもよい。
(IPv6 extension header)
FIG. 8 shows an example of the IPv6 option storage area (see, for example, Non-Patent Document 2). An IPv6 packet has an area called an IPv6 extension header that reads only a specified destination. Since only the specified destination is read in this area, the relay node does not malfunction even if arbitrary data is stored. Therefore, it can be replaced freely. Therefore, by inserting an arbitrary flow option in this area, the multipath is established (first technique) and the sequence number is stored (second technique) between the user terminal 93 and the service server 92. You may.
(IPv4オプション格納領域)
 図9に、IPv4オプション格納領域の一例を示す。IPv4パケットにはIPv4ヘッダオプションが存在する(例えば、特許文献1参照。)。この領域に挿入する値はオプション値として定められており、任意の値を格納すると中継ノードが誤作動を起こす恐れがある。そこで、IPヘッダ領域設定部23、33は、オプション最終位置指定表示機能を備える。オプション最終位置指定表示機能は、指定のオプション値を入力する領域を指定し、その後ろに任意の値を挿入する。この領域にマルチパスオプションを格納する。これにより、中継ノードは誤作動を行うことなく、受信側である宛先機器のIPヘッダ領域設定部23、33がオプション最終位置指定表示機能の入力した値を読み取ることができる。
(IPv4 option storage area)
FIG. 9 shows an example of the IPv4 option storage area. An IPv4 header option is present in an IPv4 packet (see, for example, Patent Document 1). The value to be inserted in this area is defined as an optional value, and if any value is stored, the relay node may malfunction. Therefore, the IP header area setting units 23 and 33 are provided with an option final position designation display function. The option final position specification display function specifies the area for inputting the specified option value, and inserts an arbitrary value after it. Store multipath options in this area. As a result, the relay node can read the value input by the option final position designation display function by the IP header area setting units 23 and 33 of the destination device on the receiving side without causing a malfunction.
 図10に、既存システムを利用した実装例を示す。スケジューラ15によるパケットの分割、統合はMPTCPカーネルが行っている。このため、MPTCPの既存実装を活用し、スケジューラ15(カーネル実装)すなわち本実施形態のスケジューラ25、35を実現することができる。また従来のMPTCP機能のTCPオプション領域設定部13により受け取ったオプション情報を基に、IP変換部/IPヘッダ格納部17がIPヘッダフォーマットに変換し、IPヘッダに格納する。このため、従来のMPTCP機能を活用し、TCPオプション領域設定部13すなわち本実施形態のIPヘッダ領域設定部23、33を実現することができる。 FIG. 10 shows an implementation example using an existing system. The MPTCP kernel divides and integrates packets by the scheduler 15. Therefore, the scheduler 15 (kernel implementation), that is, the schedulers 25 and 35 of the present embodiment can be realized by utilizing the existing implementation of MPTCP. Further, based on the option information received by the TCP option area setting unit 13 of the conventional MPTCP function, the IP conversion unit / IP header storage unit 17 converts the IP header format and stores it in the IP header. Therefore, the TCP option area setting unit 13, that is, the IP header area setting units 23 and 33 of the present embodiment can be realized by utilizing the conventional MPTCP function.
 本開示は情報通信産業に適用することができる。 This disclosure can be applied to the information and communication industry.
21、22、31、32:IP通信部
23、33:IPヘッダ領域設定部
24、34:フロー管理部
25、35:スケジューラ
26、36:アプリケーション制御部
81、82、83:キャリアネットワーク
92:サービスサーバ
93:利用者端末
21, 22, 31, 32: IP communication unit 23, 33: IP header area setting unit 24, 34: Flow management unit 25, 35: Scheduler 26, 36: Application control unit 81, 82, 83: Carrier network 92: Service Server 93: User terminal

Claims (4)

  1.  サービスサーバ及び利用者端末が複数のネットワークを介して接続されている通信システムであって、
     サービスサーバ及び利用者端末は、異なるネットワークを介して接続されている複数のインタフェースを備え、
     サービスサーバ及び利用者端末の一方が、
     1つのパケットを分割し、
     IPパケットのヘッダ領域に、前記1つのパケットを復元するためのシーケンス番号を含むマルチパスの情報を格納し、
     当該IPパケットを用いて、前記1つのパケットが分割された分割データを、複数のインタフェースから送信し、
     サービスサーバ及び利用者端末の他方が、
     複数のインタフェースからIPパケットを受信し、
     受信したIPパケットのヘッダ領域からマルチパスオプションの情報を読み出し、
     マルチパスオプションの情報に含まれるシーケンス番号に基づき、前記分割データを前記1つのパケットに統合する、
     通信システム。
    A communication system in which a service server and a user terminal are connected via a plurality of networks.
    The service server and the user terminal have multiple interfaces connected via different networks.
    One of the service server and the user terminal
    Divide one packet and
    Multipath information including the sequence number for restoring the one packet is stored in the header area of the IP packet.
    Using the IP packet, the divided data obtained by dividing the one packet is transmitted from a plurality of interfaces.
    The other of the service server and the user terminal
    Receive IP packets from multiple interfaces
    Read the multipath option information from the header area of the received IP packet and read it.
    Based on the sequence number included in the information of the multipath option, the divided data is integrated into the one packet.
    Communications system.
  2.  サービスサーバ及び利用者端末が複数のネットワークを介して接続されている通信システムが実行する方法であって、
     サービスサーバ及び利用者端末は、異なるネットワークを介して接続されている複数のインタフェースを備え、
     サービスサーバ及び利用者端末の一方が、
     1つのパケットを分割し、
     IPパケットのヘッダ領域に、前記1つのパケットを復元するためのシーケンス番号を含むマルチパスの情報を格納し、
     当該IPパケットを用いて、前記1つのパケットが分割された分割データを、複数のインタフェースから送信し、
     サービスサーバ及び利用者端末の他方が、
     複数のインタフェースからIPパケットを受信し、
     受信したIPパケットのヘッダ領域からマルチパスオプションの情報を読み出し、
     マルチパスオプションの情報に含まれるシーケンス番号に基づき、前記分割データを前記1つのパケットに統合する、
     通信方法。
    It is a method executed by a communication system in which a service server and a user terminal are connected via a plurality of networks.
    The service server and the user terminal have multiple interfaces connected via different networks.
    One of the service server and the user terminal
    Divide one packet and
    Multipath information including the sequence number for restoring the one packet is stored in the header area of the IP packet.
    Using the IP packet, the divided data obtained by dividing the one packet is transmitted from a plurality of interfaces.
    The other of the service server and the user terminal
    Receive IP packets from multiple interfaces
    Read the multipath option information from the header area of the received IP packet and read it.
    Based on the sequence number included in the information of the multipath option, the divided data is integrated into the one packet.
    Communication method.
  3.  複数のネットワークを介して他の通信装置と接続されている通信装置であって、
     異なるネットワークに接続されている複数のインタフェースと、
     1つのパケットから分割された分割データを、複数のインタフェースを用いて送信する送信機能と、
     複数のインタフェースを用いて送信された分割データを前記1つのパケットに統合する受信機能と、
     を備え、
     前記送信機能は、
     1つのパケットを分割し、
     IPパケットのヘッダ領域に、前記1つのパケットを復元するためのシーケンス番号を含むマルチパスの情報を格納し、
     当該IPパケットを用いて、前記1つのパケットが分割された分割データを、複数のインタフェースから送信し、
     前記受信機能は、
     複数のインタフェースからIPパケットを受信し、
     受信したIPパケットのヘッダ領域からマルチパスオプションの情報を読み出し、
     マルチパスオプションの情報に含まれるシーケンス番号に基づき、前記分割データを前記1つのパケットに統合する、
     通信装置。
    A communication device that is connected to other communication devices via multiple networks.
    With multiple interfaces connected to different networks,
    A transmission function that transmits divided data divided from one packet using multiple interfaces,
    A reception function that integrates divided data transmitted using multiple interfaces into the same packet, and
    Equipped with
    The transmission function is
    Divide one packet and
    Multipath information including the sequence number for restoring the one packet is stored in the header area of the IP packet.
    Using the IP packet, the divided data obtained by dividing the one packet is transmitted from a plurality of interfaces.
    The reception function is
    Receive IP packets from multiple interfaces
    Read the multipath option information from the header area of the received IP packet and read it.
    Based on the sequence number included in the information of the multipath option, the divided data is integrated into the one packet.
    Communication device.
  4.  請求項3に記載の装置に備わる各機能部としてコンピュータを実現させるためのプログラム。 A program for realizing a computer as each functional unit provided in the device according to claim 3.
PCT/JP2020/032477 2020-08-27 2020-08-27 Communication system, communication method, communication device, and program WO2022044226A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
JP2022545173A JPWO2022044226A1 (en) 2020-08-27 2020-08-27
PCT/JP2020/032477 WO2022044226A1 (en) 2020-08-27 2020-08-27 Communication system, communication method, communication device, and program

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2020/032477 WO2022044226A1 (en) 2020-08-27 2020-08-27 Communication system, communication method, communication device, and program

Publications (1)

Publication Number Publication Date
WO2022044226A1 true WO2022044226A1 (en) 2022-03-03

Family

ID=80354939

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2020/032477 WO2022044226A1 (en) 2020-08-27 2020-08-27 Communication system, communication method, communication device, and program

Country Status (2)

Country Link
JP (1) JPWO2022044226A1 (en)
WO (1) WO2022044226A1 (en)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2000253058A (en) * 1999-02-26 2000-09-14 Nec Corp Transfer destination decision processor
JP2006165952A (en) * 2004-12-07 2006-06-22 Hitachi Ltd Packet repeater system and packet communication network

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2000253058A (en) * 1999-02-26 2000-09-14 Nec Corp Transfer destination decision processor
JP2006165952A (en) * 2004-12-07 2006-06-22 Hitachi Ltd Packet repeater system and packet communication network

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
A. FORD PEXIP C. RAICIU U. POLITEHNICA OF BUCHAREST M. HANDLEY U. COLLEGE LONDON O. BONAVENTURE U. CATHOLIQUE DE LOUVAIN C. PAASCH: "TCP Extensions for Multipath Operation with Multiple Addresses; rfc8684.txt", TCP EXTENSIONS FOR MULTIPATH OPERATION WITH MULTIPLE ADDRESSES; RFC8684.TXT, no. 8684, 8684, 31 March 2020 (2020-03-31), pages 1 - 43, XP015137994 *
SUN LIYANG; TIAN GUIBIN; ZHU GUANYU; LIU YONG; SHI HANG; DAI DAVID: "Multipath IP Routing on End Devices: Motivation, Design, and Performance", 2018 IFIP NETWORKING CONFERENCE (IFIP NETWORKING) AND WORKSHOPS, 14 May 2018 (2018-05-14), pages 1 - 9, XP033540916, DOI: 10.23919/IFIPNetworking.2018.8696893 *

Also Published As

Publication number Publication date
JPWO2022044226A1 (en) 2022-03-03

Similar Documents

Publication Publication Date Title
US11088942B2 (en) Method of QUIC communication via multiple paths
US7492762B2 (en) Method for dynamic flow mapping in a wireless network
US7630368B2 (en) Virtual network interface card loopback fastpath
US7206288B2 (en) Methods and apparatus for characterizing a route in fibre channel fabric
JP4627669B2 (en) Packet transfer apparatus and transfer control method thereof
US6778495B1 (en) Combining multilink and IP per-destination load balancing over a multilink bundle
JP5097620B2 (en) Multipath communication system
JP4794312B2 (en) Automatic detection of pseudowire peer addresses in Ethernet-based networks
US20160380966A1 (en) Media Relay Server
JP2005537764A (en) Mechanism for providing QoS in a network using priority and reserve bandwidth protocols
WO2000048374A1 (en) Method and apparatus for switching high-speed multimedia content packets with compressed internet protocol header
KR20030094851A (en) Apparatus for providing QoS on IP router and method for forwarding VoIP traffic
US10015091B2 (en) Method of low-bandwidth data transport
JP2000115278A (en) Method and system for mss spoofing
US20060218300A1 (en) Method and apparatus for programmable network router and switch
JP5941887B2 (en) Edge router switching method and system, edge router and redundancy management device
JP2008537421A (en) Method for establishing a connection in a communication system
US6985496B2 (en) Communication management device and communication management method
US20030065741A1 (en) Concurrent bidirectional network communication utilizing send and receive threads
CN112398754B (en) Data transmission method, device, medium, electronic equipment and network access equipment
WO2022044226A1 (en) Communication system, communication method, communication device, and program
US20010052025A1 (en) Router setting method and router setting apparatus
CN100393039C (en) Network administration method for no-IP address device
EP1491004A1 (en) Method for path mtu discovery on ip network and apparatus thereof
CN113612698A (en) Data packet sending method and device

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 2022545173

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20951479

Country of ref document: EP

Kind code of ref document: A1