OSAS O UR S UPER A WESOME S CHEDULER Students : Yulia, Yaniv, - PowerPoint PPT Presentation

OSAS – O UR S UPER A WESOME S CHEDULER Students : Yulia, Yaniv, Shiran, Gilad & Roi Mentor: Tomer Supervisor: Hanoch Hanoch Sapoznikov Jan 2012 Lead of Worldwide Academic Relations Jan 2012

I NTRODUCTION  We provides to the client download/upload manager which will have the option to delay certain downloads/uploads.  Client revenue: will be rewarded by lowering package usage.  OSAS will be synchronized with an intended server that will have a clients tasks queue, dependent on clients demands and order of demands.  OSAS will automatically detect network loads and will schedule downloads/uploads according to current load, balancing network traffic.

O BJECTIVES  Manage downloads/uploads and connect to the company’s scheduler.  Manage the queuing server that will control the traffic of downloads/uploads.  Notify download/upload managers connected to it to start/resume transfers.

F EATURES  The server application side:  Add / Remove download/upload.  Force download/upload to complete (in cases customer doesn’t want to wait anymore).  Automatically detect loads and congestion.  Synchronize with current loads.  Fair queuing – clients with earlier requests will be prior to later requests (all depend also on customer deadline and traffic limitation).  Client application side:  Gives the client to chose when download/upload  Gives the client option to not use the service when he don’t want it  Raises awareness about the network overloading

M ETHODOLOGY  Server side:  Establish a protocol for the queuing of requests  Use existing congestion sensors/detector as an input to dynamically control downloads/uploads in terms of speed in real-time.  Client side:  Create a user friendly application that will integrate to client’s smartphone and be connected to company’s server.

M ILESTONES Requirements & Technology Research (Weeks 1-3) Deliverables: requirements document. Network analyzer that checks what we can improve at the network state High Level Design (Week 4-5) Design server application Design client application for iphone Design client application for android Detailed design (Weeks 6-8) Deliverable: detailed design document. Coding (Weeks 9-21) Deliverables: code + code documentation + JavaDoc Demonstration of working parts (Week 13 Midway meeting week of Apr 12): Use acquired info from network about load to balance network traffic Write the algorithm for making scheduling decisions Write the scheduler for the smart phone Testing (Weeks 22-25) Deliverables: final product code + release notes including known bugs, caveats and workarounds. Documentation (Week 26) Deliverables: Installation guide + User guide.

D EVELOPMENT E NVIRONMENT  Language: Java  IDE: Eclipse  Technologies:  For client side:  Smartphone app (android and iphone)  For server app:  Java  JEE  HTPS

F INAL D ELIVERABLES  Software  Well documented source code  Client app  Server app  Demo app  Tools for marketing  Documentation  Final Presentation  Release Notes  known bugs, caveats, workarounds.  Installation Guide  User Guide.

Thank you…