IDEAS home Printed from https://ideas.repec.org/a/gam/jftint/v16y2024i4p122-d1368912.html
   My bibliography  Save this article

SDN-Based Secure Common Emergency Service for Railway and Road Co-Existence Scenarios

Author

Listed:
  • Radheshyam Singh

    (Department of Electrical and Photonics Engineering, Technical University of Denmark, 2800 Kgs Lyngby, Denmark
    These authors contributed equally to this work.)

  • Leo Mendiboure

    (COSYS-ERENA, University Gustav Eiffel, IFSTTAR, F-33067 Bordeaux, France
    These authors contributed equally to this work.)

  • José Soler

    (Department of Electrical and Photonics Engineering, Technical University of Denmark, 2800 Kgs Lyngby, Denmark)

  • Michael Stübert Berger

    (Department of Electrical and Photonics Engineering, Technical University of Denmark, 2800 Kgs Lyngby, Denmark)

  • Tidiane Sylla

    (Department GEII-ISA, University of Sciences, Techniques and Technologies of Bamako, 33067 Bordeaux, France)

  • Marion Berbineau

    (COSYS-LEOST Lab, University Gustave Eiffel, IFSTTAR, 59650 Villeneuve d’Ascq, France)

  • Lars Dittmann

    (Department of Electrical and Photonics Engineering, Technical University of Denmark, 2800 Kgs Lyngby, Denmark)

Abstract

In the near future, there will be a greater emphasis on sharing network resources between roads and railways to improve transportation efficiency and reduce infrastructure costs. This could enable the development of global Cooperative Intelligent Transport Systems (C-ITSs). In this paper, a software-defined networking (SDN)-based common emergency service is developed and validated for a railway and road telecommunication shared infrastructure. Along with this, the developed application is capable of reducing the chances of distributed denial-of-service (DDoS) situations. A level-crossing scenario is considered to demonstrate the developed solution where railway tracks are perpendicular to the roads. Two cases are considered to validate and analyze the developed SDN application for common emergency scenarios. In case 1, no cross-communication is available between the road and railway domains. In this case, emergency message distribution is carried out by the assigned emergency servers with the help of the SDN controller. In case 2, nodes (cars and trains) are defined with two wireless interfaces, and one interface is reserved for emergency data communication. To add the DDoS resiliency to the developed system the messaging behavior of each node is observed and if an abnormality is detected, packets are dropped to avoid malicious activity.

Suggested Citation

  • Radheshyam Singh & Leo Mendiboure & José Soler & Michael Stübert Berger & Tidiane Sylla & Marion Berbineau & Lars Dittmann, 2024. "SDN-Based Secure Common Emergency Service for Railway and Road Co-Existence Scenarios," Future Internet, MDPI, vol. 16(4), pages 1-17, April.
  • Handle: RePEc:gam:jftint:v:16:y:2024:i:4:p:122-:d:1368912
    as

    Download full text from publisher

    File URL: https://www.mdpi.com/1999-5903/16/4/122/pdf
    Download Restriction: no

    File URL: https://www.mdpi.com/1999-5903/16/4/122/
    Download Restriction: no
    ---><---

    Corrections

    All material on this site has been provided by the respective publishers and authors. You can help correct errors and omissions. When requesting a correction, please mention this item's handle: RePEc:gam:jftint:v:16:y:2024:i:4:p:122-:d:1368912. See general information about how to correct material in RePEc.

    If you have authored this item and are not yet registered with RePEc, we encourage you to do it here. This allows to link your profile to this item. It also allows you to accept potential citations to this item that we are uncertain about.

    We have no bibliographic references for this item. You can help adding them by using this form .

    If you know of missing items citing this one, you can help us creating those links by adding the relevant references in the same way as above, for each refering item. If you are a registered author of this item, you may also want to check the "citations" tab in your RePEc Author Service profile, as there may be some citations waiting for confirmation.

    For technical questions regarding this item, or to correct its authors, title, abstract, bibliographic or download information, contact: MDPI Indexing Manager (email available below). General contact details of provider: https://www.mdpi.com .

    Please note that corrections may take a couple of weeks to filter through the various RePEc services.

    IDEAS is a RePEc service. RePEc uses bibliographic data supplied by the respective publishers.