1 / 7

Application Architecture

Application Architecture . Gold Team Pete Perlegos Matthew Caesar Jim Chou Sridhar Machiraju Per Johannson. PSTN. Base Station. WLAN. Example Applications (telephony):. Seamless handoff of call connections between networks. Universally locatable by different networks.

harper
Download Presentation

Application Architecture

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. Application Architecture Gold Team Pete Perlegos Matthew Caesar Jim Chou Sridhar Machiraju Per Johannson

  2. PSTN Base Station WLAN Example Applications (telephony): • Seamless handoff of call connections between networks. • Universally locatable by different networks. • Billing and accounting across networks

  3. Content Provider Example Applications (multimedia streaming): • Overlay network to support real time streaming. • Transcoding of streams to match transmission medium and user preferences.

  4. Network/Business Architecture Application/Content Providers Network Service Operators Network Access Providers API • Cellular: • QoS • Mobility... Cellular_2 • Billing • Authentication (single) • User profile/status • - position, devices • - service selection • QoS Policy • Traffic Metering • Performance Monitoring • Multi-access • Transcoding • Content Adaptation Cellular_n • Streaming media • Gaming • Messaging • Multi-device call • … WLAN_1 WLAN_2 WLAN_n Home (DSL) 1 Peering or Brokering? Home (DSL) 2 Home (DSL)_n Peering or Brokering? • Transit (IP) • QoS • Performance Monitoring

  5. Application API • (As shown by the iMode model) Different commercial entities should provide a piece of the puzzle • Functionality should be neither too fine (as with companies that have failed recently), • nor too coarse (as in the telephone world). • “Semi-transparency” – programmers can customize lower levels by overriding defaults • More applications become feasible with support at lower layers • Service providers can allow their service to be dynamically customized by the programmer

  6. API Characteristics • Expressive: functionality supported on multiple levels • Simple: Implemented as “hooks” (callback functions) at overlay nodes • Scalable: Interfaces aggregated for higher layers, application code multicasted to lower layers • Supports highly dynamic mobility, highly time variable resources, and varied allocation of capacity • Three levels • Service • Path • Link Aggregate Functionality Service Paths Links Disburse Payment

  7. API Architecture QoS Support Security Accounting Application Wide-area Service Content Adaptation Directory Service Performance Monitoring Diameter Congestion Usage Monitoring Intserv,FEC Shortest- Path Active Probing SSL Smart- Market Usage Aggregation Path WFQ Best- connected Channel Monitoring IPSec Auctions Traffic Monitoring Link Measure- ment Authent- ication Pricing Billing QoS Selection

More Related