The original paper is in English. Non-English content has been machine-translated and may contain typographical errors or mistranslations. ex. Some numerals are expressed as "XNUMX".
Copyrights notice
The original paper is in English. Non-English content has been machine-translated and may contain typographical errors or mistranslations. Copyrights notice
Récemment, les demandes d'applications adressées au réseau sont devenues plus multiformes. Des services de communication d'application à application hautement fonctionnels, tels que l'agrégation de bande passante, la communication tolérante aux pannes et les réseaux tolérants aux retards/interruptions (DTN), ont été développés indépendamment dans la couche réseau, la couche transport et la couche application. En conséquence, la superposition des protocoles est devenue compliquée. Cet article propose d'insérer la couche 5 (L5) entre la couche application et la couche transport pour séparer les politiques de communication et les mécanismes de communication afin de rendre la superposition de protocoles plus claire. La couche de transport (L4) fournit des mécanismes de communication de bout en bout tels qu'un flux d'octets fiable tandis que L5 met en œuvre des politiques de communication telles que l'agrégation de bande passante en combinant les mécanismes de communication dans L4. Cet article propose cinq types de chemins L5 comme politiques de communication : (1) le chemin groupé L5 pour l'agrégation de bande passante ou la communication tolérante aux pannes, (2) le chemin L5 épissé spatialement pour la communication avec les boîtiers de médiation, (3) le chemin L5 épissé temporellement chemin pour DTN, (4) le chemin groupé épissé L5 et (5) le chemin groupé L5 sur le chemin épissé spatialement. Une application peut sélectionner et utiliser un chemin L5 approprié en fonction des circonstances du réseau via une API commune. Un prototype de L5 est implémenté dans l'espace utilisateur Linux sous forme de bibliothèque pour faciliter le déploiement et la maintenance. Une évaluation montre que le temps d'établissement des chemins L5 est suffisamment court et que les performances des chemins L5 sont comparables ou supérieures aux technologies existantes.
Hiroki WATANABE
Keio University
Takao KONDO
Keio University
Kunitake KANEKO
Keio University
Fumio TERAOKA
Keio University
The copyright of the original papers published on this site belongs to IEICE. Unauthorized use of the original or translated papers is prohibited. See IEICE Provisions on Copyright for details.
Copier
Hiroki WATANABE, Takao KONDO, Kunitake KANEKO, Fumio TERAOKA, "Inserting Layer-5 to Provide Applications with Richer Functions through Common API" in IEICE TRANSACTIONS on Communications,
vol. E101-B, no. 9, pp. 1967-1981, September 2018, doi: 10.1587/transcom.2017EBP3390.
Abstract: Recently, application demands placed on the network have become more multifaceted. Highly functional application-to-application communication services such as bandwidth aggregation, fault tolerant communication, and delay/disruption tolerant networking (DTN) were developed independently in the network layer, the transport layer, and the application layer. As a result, protocol layering has become complicated. This paper proposes to insert Layer-5 (L5) between the application layer and the transport layer to separate communication policies and communication mechanisms to make protocol layering clearer. The transport layer (L4) provides end-to-end communication mechanisms such as reliable byte stream while L5 realizes communication policies such as bandwidth aggregation by combining the communication mechanisms in L4. This paper proposes five types of L5-paths as communication policies: (1) the L5 bundled path for bandwidth aggregation or fault tolerant communication, (2) the L5 spatially-spliced path for communication with middleboxes, (3) the L5 temporally-spliced path for DTN, (4) the L5 spliced-bundled path, and (5) the L5 bundled over spatially-spliced path. An application can select and use an appropriate L5-path depending on the network circumstances through a common API. A prototype of L5 is implemented in the Linux user space as a library to make deployment and maintenance easier. An evaluation shows that establishment time of L5-paths is short enough and performance of L5-paths is comparable or superior to existing technologies.
URL: https://global.ieice.org/en_transactions/communications/10.1587/transcom.2017EBP3390/_p
Copier
@ARTICLE{e101-b_9_1967,
author={Hiroki WATANABE, Takao KONDO, Kunitake KANEKO, Fumio TERAOKA, },
journal={IEICE TRANSACTIONS on Communications},
title={Inserting Layer-5 to Provide Applications with Richer Functions through Common API},
year={2018},
volume={E101-B},
number={9},
pages={1967-1981},
abstract={Recently, application demands placed on the network have become more multifaceted. Highly functional application-to-application communication services such as bandwidth aggregation, fault tolerant communication, and delay/disruption tolerant networking (DTN) were developed independently in the network layer, the transport layer, and the application layer. As a result, protocol layering has become complicated. This paper proposes to insert Layer-5 (L5) between the application layer and the transport layer to separate communication policies and communication mechanisms to make protocol layering clearer. The transport layer (L4) provides end-to-end communication mechanisms such as reliable byte stream while L5 realizes communication policies such as bandwidth aggregation by combining the communication mechanisms in L4. This paper proposes five types of L5-paths as communication policies: (1) the L5 bundled path for bandwidth aggregation or fault tolerant communication, (2) the L5 spatially-spliced path for communication with middleboxes, (3) the L5 temporally-spliced path for DTN, (4) the L5 spliced-bundled path, and (5) the L5 bundled over spatially-spliced path. An application can select and use an appropriate L5-path depending on the network circumstances through a common API. A prototype of L5 is implemented in the Linux user space as a library to make deployment and maintenance easier. An evaluation shows that establishment time of L5-paths is short enough and performance of L5-paths is comparable or superior to existing technologies.},
keywords={},
doi={10.1587/transcom.2017EBP3390},
ISSN={1745-1345},
month={September},}
Copier
TY - JOUR
TI - Inserting Layer-5 to Provide Applications with Richer Functions through Common API
T2 - IEICE TRANSACTIONS on Communications
SP - 1967
EP - 1981
AU - Hiroki WATANABE
AU - Takao KONDO
AU - Kunitake KANEKO
AU - Fumio TERAOKA
PY - 2018
DO - 10.1587/transcom.2017EBP3390
JO - IEICE TRANSACTIONS on Communications
SN - 1745-1345
VL - E101-B
IS - 9
JA - IEICE TRANSACTIONS on Communications
Y1 - September 2018
AB - Recently, application demands placed on the network have become more multifaceted. Highly functional application-to-application communication services such as bandwidth aggregation, fault tolerant communication, and delay/disruption tolerant networking (DTN) were developed independently in the network layer, the transport layer, and the application layer. As a result, protocol layering has become complicated. This paper proposes to insert Layer-5 (L5) between the application layer and the transport layer to separate communication policies and communication mechanisms to make protocol layering clearer. The transport layer (L4) provides end-to-end communication mechanisms such as reliable byte stream while L5 realizes communication policies such as bandwidth aggregation by combining the communication mechanisms in L4. This paper proposes five types of L5-paths as communication policies: (1) the L5 bundled path for bandwidth aggregation or fault tolerant communication, (2) the L5 spatially-spliced path for communication with middleboxes, (3) the L5 temporally-spliced path for DTN, (4) the L5 spliced-bundled path, and (5) the L5 bundled over spatially-spliced path. An application can select and use an appropriate L5-path depending on the network circumstances through a common API. A prototype of L5 is implemented in the Linux user space as a library to make deployment and maintenance easier. An evaluation shows that establishment time of L5-paths is short enough and performance of L5-paths is comparable or superior to existing technologies.
ER -