Twin-bus-controller protocol for fibre optic networks

Ron Yu, John J. Metzner, Asok Ray

    Research output: Contribution to journalArticle

    1 Citation (Scopus)

    Abstract

    A new Data Link Layer protocol, named the Twin-Bus-Controller (TBC) protocol, is proposed for a fibre optic network with unidirectional bus topology. The TBC protocol operates on a contention-based, time-division multiplexing scheme, and is managed by two centralized bus controllers. These controllers, which also function as network managers cooperate with each other to control and coordinate the activities on the twin bus. The IBC protocol has the capability to perform at a very high network utilization, and uses simple hardware at all stations except the two bus controllers. This arrangement provides a relatively inexpensive means to accommodate a large number of stations. Heterogeneous data consisting of real-time sensor and control signals, voice and video data, and non-real-time data such as those due to accounting and administration, can be simultaneously handled by the TBC protocol. The TBC protocol maintains global queues for all different types of data, and each class of data has a bounded delay. Furthermore, any new type of data can be added easily to the network without shutting it down or affecting those stations that are unrelated to the new data. A finite-state-machine model has been used to describe the TBC protocol. Performance of the TBC protocol has been evaluated by statistical analysis as well as via simulation for multiple classes of data traffic. Performance of the TBC protocol has been compared with that of Buzznet and Fasnet. The TBC protocol can be directly applied to diverse computer communication systems, e.g. office, manufacturing, and banking environments.

    Original languageEnglish (US)
    Pages (from-to)598-607
    Number of pages10
    JournalComputer Communications
    Volume14
    Issue number10
    DOIs
    StatePublished - Jan 1 1991

    Fingerprint

    Fiber optic networks
    Network protocols
    Controllers
    Time division multiplexing
    Finite automata
    Statistical methods
    Communication systems
    Managers
    Topology
    Hardware

    All Science Journal Classification (ASJC) codes

    • Computer Networks and Communications

    Cite this

    Yu, Ron ; Metzner, John J. ; Ray, Asok. / Twin-bus-controller protocol for fibre optic networks. In: Computer Communications. 1991 ; Vol. 14, No. 10. pp. 598-607.
    @article{3ef831f41d2548c49eaff413c5d65ae5,
    title = "Twin-bus-controller protocol for fibre optic networks",
    abstract = "A new Data Link Layer protocol, named the Twin-Bus-Controller (TBC) protocol, is proposed for a fibre optic network with unidirectional bus topology. The TBC protocol operates on a contention-based, time-division multiplexing scheme, and is managed by two centralized bus controllers. These controllers, which also function as network managers cooperate with each other to control and coordinate the activities on the twin bus. The IBC protocol has the capability to perform at a very high network utilization, and uses simple hardware at all stations except the two bus controllers. This arrangement provides a relatively inexpensive means to accommodate a large number of stations. Heterogeneous data consisting of real-time sensor and control signals, voice and video data, and non-real-time data such as those due to accounting and administration, can be simultaneously handled by the TBC protocol. The TBC protocol maintains global queues for all different types of data, and each class of data has a bounded delay. Furthermore, any new type of data can be added easily to the network without shutting it down or affecting those stations that are unrelated to the new data. A finite-state-machine model has been used to describe the TBC protocol. Performance of the TBC protocol has been evaluated by statistical analysis as well as via simulation for multiple classes of data traffic. Performance of the TBC protocol has been compared with that of Buzznet and Fasnet. The TBC protocol can be directly applied to diverse computer communication systems, e.g. office, manufacturing, and banking environments.",
    author = "Ron Yu and Metzner, {John J.} and Asok Ray",
    year = "1991",
    month = "1",
    day = "1",
    doi = "10.1016/0140-3664(91)90049-7",
    language = "English (US)",
    volume = "14",
    pages = "598--607",
    journal = "Computer Communications",
    issn = "0140-3664",
    publisher = "Elsevier",
    number = "10",

    }

    Twin-bus-controller protocol for fibre optic networks. / Yu, Ron; Metzner, John J.; Ray, Asok.

    In: Computer Communications, Vol. 14, No. 10, 01.01.1991, p. 598-607.

    Research output: Contribution to journalArticle

    TY - JOUR

    T1 - Twin-bus-controller protocol for fibre optic networks

    AU - Yu, Ron

    AU - Metzner, John J.

    AU - Ray, Asok

    PY - 1991/1/1

    Y1 - 1991/1/1

    N2 - A new Data Link Layer protocol, named the Twin-Bus-Controller (TBC) protocol, is proposed for a fibre optic network with unidirectional bus topology. The TBC protocol operates on a contention-based, time-division multiplexing scheme, and is managed by two centralized bus controllers. These controllers, which also function as network managers cooperate with each other to control and coordinate the activities on the twin bus. The IBC protocol has the capability to perform at a very high network utilization, and uses simple hardware at all stations except the two bus controllers. This arrangement provides a relatively inexpensive means to accommodate a large number of stations. Heterogeneous data consisting of real-time sensor and control signals, voice and video data, and non-real-time data such as those due to accounting and administration, can be simultaneously handled by the TBC protocol. The TBC protocol maintains global queues for all different types of data, and each class of data has a bounded delay. Furthermore, any new type of data can be added easily to the network without shutting it down or affecting those stations that are unrelated to the new data. A finite-state-machine model has been used to describe the TBC protocol. Performance of the TBC protocol has been evaluated by statistical analysis as well as via simulation for multiple classes of data traffic. Performance of the TBC protocol has been compared with that of Buzznet and Fasnet. The TBC protocol can be directly applied to diverse computer communication systems, e.g. office, manufacturing, and banking environments.

    AB - A new Data Link Layer protocol, named the Twin-Bus-Controller (TBC) protocol, is proposed for a fibre optic network with unidirectional bus topology. The TBC protocol operates on a contention-based, time-division multiplexing scheme, and is managed by two centralized bus controllers. These controllers, which also function as network managers cooperate with each other to control and coordinate the activities on the twin bus. The IBC protocol has the capability to perform at a very high network utilization, and uses simple hardware at all stations except the two bus controllers. This arrangement provides a relatively inexpensive means to accommodate a large number of stations. Heterogeneous data consisting of real-time sensor and control signals, voice and video data, and non-real-time data such as those due to accounting and administration, can be simultaneously handled by the TBC protocol. The TBC protocol maintains global queues for all different types of data, and each class of data has a bounded delay. Furthermore, any new type of data can be added easily to the network without shutting it down or affecting those stations that are unrelated to the new data. A finite-state-machine model has been used to describe the TBC protocol. Performance of the TBC protocol has been evaluated by statistical analysis as well as via simulation for multiple classes of data traffic. Performance of the TBC protocol has been compared with that of Buzznet and Fasnet. The TBC protocol can be directly applied to diverse computer communication systems, e.g. office, manufacturing, and banking environments.

    UR - http://www.scopus.com/inward/record.url?scp=0026377516&partnerID=8YFLogxK

    UR - http://www.scopus.com/inward/citedby.url?scp=0026377516&partnerID=8YFLogxK

    U2 - 10.1016/0140-3664(91)90049-7

    DO - 10.1016/0140-3664(91)90049-7

    M3 - Article

    AN - SCOPUS:0026377516

    VL - 14

    SP - 598

    EP - 607

    JO - Computer Communications

    JF - Computer Communications

    SN - 0140-3664

    IS - 10

    ER -