1 / 20

Network Simulator - 2

Network Simulator - 2. Project Made by Min-Soo Kim and Kang-Yong Lee Ajou University, Division of Information & Computer Engineering 2003/06/09. Index. Purpose & Necessity Sample Network Architecture Proposed Network Architecture How to Implement Advantages & Drawbacks

jemma
Download Presentation

Network Simulator - 2

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Network Simulator - 2 Project Made by Min-Soo Kim and Kang-Yong Lee Ajou University, Division of Information & Computer Engineering 2003/06/09

  2. Index Purpose & Necessity Sample Network Architecture Proposed Network Architecture How to Implement Advantages & Drawbacks Project Schedule Implementation Core Source  Packet  Link Layer  Channel  MAC Layer 9. Simulation Environment 10. Simulation Video 11. Simulation Result

  3. 1. Purpose & Necessity • We will modify the network architectures which are assumed by sample NS-2 code. • Existing Network Architecture in sample code  Physically flat network architecture.  All nodes and routers have channel with homogeneous capability (link). • Proposed scheme  In real world, there is non-homogeneous channel capacity (link).  We consider routers and nodes which have group concept.  and all routers can communicate with each other, directly

  4. n1 n2 n7 R n4 n3 R n5 R n6 2. Existing Network Architecture n# : Node R : Router : Network (Ethernet)

  5. 3. Proposed Network Architecture n1 Group 1 n2 n7 R n4 Group 2 n3 R n5 Group 3 R n6 Group 4 : New Added Channel

  6. 4. How to Implement – Data structure Node Information – Routing module Group Membership Table - Routing module maintains group membership table which contains nodes ID in the same physical group Packet header - packet • Additional define a new packet field • channel mode (for channel layer) • in common header field

  7. 4. How to Implement – Algorithm Channel Routing Module • If destination node is not • located in • same physical group with router ? • Set the group field value to New channel mode else • Set the group field value To Normal mode Receives packet to transmit from upper layer Inter group traffic or Intra group traffic (Using channel field) ? Existing scheme New Added Channel - Delay control

  8. 5. Advantages & Drawbacks • Advantages  Reducing the number of packets  Guarantees good QoS - High transmission speed (through New added-Channel) - More reliable transmission (high delivery ratio) • Drawbacks  Additional overheads - Packet size is increasing (header field - channel field) - All routers must maintain the information of group member - All routers must equip two link  Potential bottleneck problem at the router

  9. 6. Project Schedule 5 / 24 5 / 26 5 / 28 6 / 1 6 / 3 6 / 5 6 / 7 Specific Design L , K Packet structure analysis K L Link, Channel analysis Coding - packet K Coding – Link, channel L Coding - routing L, K Debugging & Simulation L, K Result Analysis L, K L : By Kang-Yong Lee K : By Min-Soo Kim

  10. recv(p) arpresolve(p); 7. Implementation – Original Concept • 기존 LAN 에서의 Packet forwarding  one lanrouter object per a LAN  For every node on the LAN, the LL has a pointer to the lanrouter Direction ->Up sendUp(p) sendUp(p) Direction ->Down sendDown(p) YES lanrouter_->next_hop (p) ? next_hop(packet *p) NO schedule (downtarget_, p, delay_) LL::sendDown()

  11. arpresolve(p) 7. Implementation – Proposed Concept(1) • Before forwarding a packet, if “I am a router”, send the packet through “Direct Channel” to another router Direction ->Down sendDown(p) Modified part YES YES lanrouter_->next_hop (p)? Am I router ? Inter or Intra NO Inter NO Send the packet to other router through Direct Channel Intra next_hop(packet *p) Send the packet to other router through Normal Channel schedule(downtarget_, p, delay_) LL::sendDown()

  12. 7. Implementation – Proposed Concept(2) • Channel part Channel::sendUp() Received packet NORMAL_CHANNEL cmn_hdr->channel_type() DIRECT_CHANNEL Set the variables characterizing Normal Channel Set the variables characterizing Direct Channel Modified part

  13. 7. Implementation – Proposed Concept(3) • MAC layer Received packet NO DIRECT_CHANNEL cmn_hdr->channel_type() Am I router ? YES NORMAL_CHANNEL packet::free(p) Modified part Mac-802_3::recv()

  14. 8. Core Source – Packet • Add the new packet field : which_Channel_ New packet header field

  15. 8. Core Source – Link Layer • Distinguish the packet transmission type : Inter ? or Intra ? Set the channel type to use

  16. 8. Core Source – Channel • Characterizing “Direct Channel” : delay Set the delay of channel Send packet

  17. 8. Core Source – mac layer • Packet Drop or Receive ? If I am not a router, I must drop the packets which are received by Direct Channel. Because I don’t have the Direct Channel Link

  18. 9. Simulation Environment • Simulation Environment  The number of Node : 12 nodes  The number of Group : 4 physical groups  Simulation Time : 5 sec  Packet Size data packet : 1000 bytes ack packet : 40 bytes  Simulation Scenario * source : node 0 TCP Reno Agent * destination : node 14 TCP Sink Agent

  19. 10. Simulation Video • Other Meterials

  20. 11. Simulation Result • Simulation Result  Transmission Reliability (Received pkt / Transmitted packet) Original scheme : (1166/1181) = 0.9872 Proposed scheme : (1172/1184) = 0.9898  Transmission Time (End-to-End delay) Original scheme : 0.008 (sec) Proposed scheme : 0.005 (sec)

More Related