1 / 6

Transport Plane and Domains Review of 3016-9 design Scott Cadzow, C3L/ETSI-STF194

Transport Plane and Domains Review of 3016-9 design Scott Cadzow, C3L/ETSI-STF194. Transport Plane. Transport plane offers many technologies in different domains Packet transport: IP Packet switching: ATM, X.25 Circuit switching: ISDN/SS7 Service domains offer many services

nusa
Download Presentation

Transport Plane and Domains Review of 3016-9 design Scott Cadzow, C3L/ETSI-STF194

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. Transport Plane and Domains Review of 3016-9 design Scott Cadzow, C3L/ETSI-STF194

  2. Transport Plane • Transport plane offers many technologies in different domains • Packet transport: IP • Packet switching: ATM, X.25 • Circuit switching: ISDN/SS7 • Service domains offer many services • Need to correlate the transport and service • Transport domain independence • Transport domain addressing cannot be guaranteed to be contiguous across all networks

  3. Transport domain functionality

  4. The role of ICFs • To allow transport domains to interwork • To provide session portability between transport domains Transport plane ICF ICF Transport Domain#2 Transport Domain#1 … • Need data to allow ICFs to pull traffic from one transport domain and put it into the next • ICF acts to make transport plane homogeneous

  5. Functional model of transport domain • TU represents the service domain • TFE1 represents the domain transport resource manager • TFE2 represents the transport flow handling at ingress • TFE3 represents the transport flow handling at egress

  6. Bearer Identity • Contained in the payload of the transport domain • Extracted by the ICF • Has to be unique end-to-end • Used with bearer descriptor to characterise transport domain • Signalling exchanges bearer-id, traffic routes on bearer-id • Route is defined during signalling phase as virtual circuit Header Payload Bearer-id Payload Native transport header Payload

More Related