1 / 10

Dirk Kutscher Faisal Mir Rolf Winter <firstname.lastname>@neclab.eu

Mobile Communication Congestion Exposure Scenario http://datatracker.ietf.org/doc/draft-kutscher-conex-mobile/. Dirk Kutscher Faisal Mir Rolf Winter <firstname.lastname>@neclab.eu. Suresh Krishnan Ying Zhang <firstname.lastname>@ericsson.com. CONEX & Mobile Communications.

xuxa
Download Presentation

Dirk Kutscher Faisal Mir Rolf Winter <firstname.lastname>@neclab.eu

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. Mobile CommunicationCongestion Exposure Scenariohttp://datatracker.ietf.org/doc/draft-kutscher-conex-mobile/ Dirk Kutscher Faisal Mir Rolf Winter <firstname.lastname>@neclab.eu Suresh Krishnan Ying Zhang <firstname.lastname>@ericsson.com IETF-80, Prague

  2. CONEX & Mobile Communications • CONEX WG: Congestion exposure in a variety of use cases • WG to focus on use case where end hosts and network containing destination host are CONEX-enabled • Other networks need not be • Mobile communication networks • Well-defined roles for hosts, nodes, gateways • Well-defined network boundaries • Limited resources (wireless), fine-granular policing and accounting IETF-80, Prague

  3. Congestion in Mobile Communications • Moving from telephony to data networks • Historically: congestion considered a non-issue • Strict resource management and adequate resource provisioning • Also: best-effort traffic considered expendable IETF-80, Prague

  4. Congestion in Mobile Communications • Moving from telephony to data networks • Historically: congestion considered a non-issue • Strict resource management and adequate resource provisioning • Also: best-effort traffic considered expendable • Inconvenient news IETF-80, Prague

  5. Shared Resources in LTE S6a HSS PCRF MME S11 S1-MME Gx Rx Operator IP Services (IMS, PSS, etc) eNB S-GW P-GW UE Uu S1-U S5/S8 SGi IETF-80, Prague

  6. Shared Resources in LTE S6a HSS App UE Uplink IP Flows PCRF MME HTTP FTP P2P VOIP S11 S1-MME Gx Rx TFT Operator IP Services (IMS, PSS, etc) Traffic Filters eNB S-GW P-GW UE Uu S1-U S5/S8 SGi SDF Default NGBR Dedicated GBR Downlink EPS Bearers:QoS approachfor managing them IETF-80, Prague

  7. More Resource Management • Selected Traffic Offload • Mitigate congestion in core network by avoiding tunneling best-effort traffic to gateways, home networks etc. • 3GPP chartered to add DPI to policy framework • In fact already deployed in many networks IETF-80, Prague

  8. Assumptions for Our Work • It‘s really about capacity sharing • Static differentiation between „best-effort“ and „important“ traffic not useful for that: the Internet is best-effort • Need reasonable resource sharing and acceptable performance for all applications • Low delay just as important for good user experience • Mobile communication networks are used just as any other access network • Bulk background traffic, interactive applications – all in parallel, on shared links • Dynamic incentives to back-off will be useful IETF-80, Prague

  9. draft-kutscher-conex-mobile-00 • Describing 3GPP‘s EPS • Analyzing CONEX use cases in mobile communication networks • Traffic management • Incentivize scavenger transport • Accounting for congestion volume • Differential QoS • Partial vs. Full Deployment • CONEX in the EPS • Across operator domains • Within one operator network • Implementing CONEX mechanisms and policing functions • Implications for CONEX • What we should consider for the mechanism spec IETF-80, Prague

  10. Implications for CONEX • Consider dynamic path conditions • Wireless access, multi-access, mobility • Requirements for fine-granular resource control (wireless) • Tunneling • Traffic Offload • Roaming • IPv4? IETF-80, Prague

More Related