1 / 41

The Construction QoS Management Model for Distributed Stream Services Based on CORBA

The Construction QoS Management Model for Distributed Stream Services Based on CORBA. Chang-won Jeong* , Su-Chong Joo*, and Jae-Wan Lee**. *Dept. of Computer Engineering Won-Kwang University **Dept. of Information Communication Engineering, Kun-San National University, Korea

toan
Download Presentation

The Construction QoS Management Model for Distributed Stream Services Based on CORBA

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. The Construction QoS Management Model for Distributed Stream Services Based on CORBA Chang-won Jeong* , Su-Chong Joo*, and Jae-Wan Lee** *Dept. of Computer Engineering Won-Kwang University **Dept. of Information Communication Engineering, Kun-San National University, Korea scjoo@wonkwang.ac.kr

  2. Contents • Introduction • Research Backgrounds and Our Goals • Stream Services and Quality of Service(QoS) • Definitions and Needs • Stream Control Mechanisms • Related Works • Design : QoS Management Model • Object Module • User Control Model, QoS Management Module • Resources Negotiation, Adaptation, Monitoring Procedures • Implementation : QoS Management Model • IDL Definition • DB Scheme Design • QoS MIB • Stream Objects for QoS • Results of Our Models • Conclusions : Summary and Future Works

  3. Introduction • Research Background • Trends Text- Based Services toward Multimedia-Based Services • With An Advent of Distributed Object Computing Technology, Possible to develop Large Scaled Multimedia Applications • Requires Integrated Managements Model for Supporting Various Multimedia Services • Our Research Goal • Studies Integrated Management of Multimedia Stream Services in Distributed Object Computing Environment Based on CORBA • Suggests QoS Management Model Considering Resource Reservation , Negotiation, Adaptation Mechanisms • Ensuring Independent Distributed Platform • Easy to Implement User Distributed Applications • Reusable QoS Management Model

  4. Stream Services • Definition • Behaviors of Real-Time Services sending and receiving multimedia stream data such as Audio/Video on Peer-to-Peer, or Client/Server Environment Based on Internet or Intranet • Properties • Continuous Traffics • Real-Time Services • Sensitive Transfer Delay and Propagation • Interactions Between End-Systems • Requirements for Considering Stream Service • Supporting Control Mechanism for QoS • Supporting Synchronization Mechanism for Sending and Receiving Stream Data • Requiring Replay And Reproduction Methods • Providing Distributed Services among Heterogeneous Systems over Networks • Providing Data Compression Method for Saving Network Bandwidth

  5. QoS : Quality of Service • Definition • Says All Jobs Controlling for Maintaining Previous Promised Service of Quality in Accordance with SLA(Service Level Agreement) Between Requester And Provider, While Servicing Procedures are Executing. • Network ServiceEnd-to-End System • Needs • Multimedia And Level Services • Using Limited Resources • Services Among Multi-Users • Appropriate Control Mechanisms • Classification • User-Level QoS • Application-Level QoS • System and Network –Level QoS

  6. QoS Control Mechanism • Specification and Mapping • User-Centralized QoS Presentation, Supporting QoS Parameter Conversion Method Among Users, Applications, and End Systems • Resource Monitoring • Monitoring and Registering The QoS Parameters about Resources Use • Negotiation • Providing Negotiation MethodologyBetween End-to-End Systems • Resource Adaptation • Without Stopping Services, Maintaining A Sequences of Services through Readjust of QoS Parameters about Each Resources • Notification • Decides whether The Negotiated Service Can be Maintained or Not , If Not, It is necessary to Readjust of QoS Parameters about The Underlying Resources • Admission Control • Decides whether The Service Provides or Not • Resource reservation • Provides Network Resource Reservation functionality for maintaining Safe Services • Scheduling, Policing • Provide An Appropriate Scheduling Algorithm According to Negotiated Service Level Given Between Service Requester and Provider (Class of Service) • Traffic Control Via Dropping or Marking of Unnecessary Packets

  7. Research Institutes Contents ICSI’s CME Co-working over Mbone, Supporting User-Controlled QoS Distributed Application Development for Supporting QoS Using QuOs BBN’s QuO Project OMG A/V Streaming Std. Extending the Stream Technology of CORBA Spec. Development of Framework and API for Stream Services Microsoft & Sun Co. Research Institutes Contents KAIST, KTA Implementation of Object-Oriented Distributed Multimedia Application Systems Using CORBA Design of Stream Communication Service Based on CORBA Environments InHa University LG Institute Design And Implementation of Distributed Object Frameworks For Supporting Audio/Video Streaming Services A Study of Distributed Framework for Development of Multimedia Programs on CORBA BuSan University Related Works • Domestic Researches • Outside Country’s Researches

  8. User User User User Host Host Host Host COMMA COMMA COMMA COMMA Network Session Manager Connection Manager User Interface Media Service 1 QoS Mapper/Controller Service Manager Media Service 2 Resource Monitor/Controller Media Service n COMMA = Cooperative Multimedia Application Related Works’ Case 1: CME • Design Goals • Supporting Cooperation Environment for Co-work Project • QoS Control by User-Controlled Method

  9. Contract Contract Related Works’ Case 2: QuO(Quality Object) • Design Goals • Distributed Application Development for Supporting QoS Using QuOs Application Developer Client Object Logical Method Call SysCond SysCond Delegate Delegate SysCond SysCond SysCond QoS Designer SysCond SysCond ORB Proxy ORB Proxy Mechanism/Property Manager Mechanism Developer Specialized ORB Specialized ORB Network Client Server Network

  10. Related Works’ Case 3 : OMG A/V Streaming Spec. • Design Goals • Supporting Stream Services Without Modifying CORBA Spec. Stream Endpoint Flow data End-point (Source) Stream Interface Control Object Stream Interface Control Object Flow data End-point (Sink) Control and Management Objects client server server client server client stream control operation stream control operation data flow data flow Stream Adaptor Basic Object Adaptor Basic Object Adaptor Stream Adaptor ORB Core Stream Flow

  11. Related Works : Summary • Domestic Related Works • Work Trends • Developing Various Multimedia Control Algorithm for Saving Network Bandwidth • Focusing on Stream Services on CORBA Environments • Problems • Not Enough Works for Management of Multimedia Stream Services • Also, Not Enough Works of QoS Management Model • Being Suggested to Only Management Structures depended of Particular Applications • Foreign Related Works • Problems Focused of QoS • Suggesting Abstract Models • QoS Management Model with insufficient interoperability • QoS Management Model Depended on Distributed Platform • QoS Management Model Is difficult to extend or reuse

  12. Design : Our QoS Management Environment Various Applications VOD, Video Conferencing, Multicast Service, Remote Education Service QoSM MpO CnO MIO UCM UCM CO NO CO NO UIO SO UIO MO SO MO CORBA-Based Environments Application Interface Stream Object Stream Object Stream Flow

  13. Network Client System Server System Stream Receive Object Stream Send Object Stream flow control sampling Control System UCM 1 UCM 2 Service Service Monitor Monitor QoSM Control User Interface DBLogic DBLogic Notify Manager Interface Notify User Interface connect Mapper connect negotiation CORBA connection control adaptation control flow control flow stream flow UCM : User Control Module QoSM : QoS Management Module Design : QoS Management Model • Design Goals • Independent Distributed Platform, And QoS Management Structure • Providing User-Based QoS Control mechanism • Easy to Implementation of Various Stream Services • Supporting Conveniences to extend and reuse Based on OO technology

  14. Design : Components in Our Model • Definition of Object Module • Unit, As A Package Grouped by Related Objects • Consisting of One or More Objects And Interface Objects Managing Them • In Details, Divide functionally to Two User Control Modules(UCM) and A QoS Management Module(QoSM). They Interoperates One Another So That Given Conditions of QoS Are Met • Functionality • Supporting Simplicity of Message Flows among Objects • Providing A Single Interface • UCM, QoSM • User Control Module(UCM) • User Interface Object(UIO) • Manages Connect, Service, Monitor, Notify Objects in UCM, • How to Distribute messages among Them • QoS Management Module(QoSM) • Manager Interface Object(MIO) • Manages references of Control and Mapper Objects in QoSM • How to Distribute messages

  15. UCM Service Monitor CORBA DBLogic User Interface Notify connect Design : Objects in UCM • UCM: User Control Module • Provides Start, Stop And Reconfigure Functions for Stream Service Via Interactions • User Interface Object(UIO) • Provides Interfaces for Developing Distributed Applications, Manages Objects in UCM • Connect Object(CO) • Establishes and Releases with UCM in Side of Server(Provider) • Service Object(SO) • Controls Stream Services Between Stream Sending/Receiving Objects • Monitor Object(MO) • Registers Network Workload(bandwidth, packet delay time, transfer rate, delay rate) and System Workload(CPU, MM) to DB, For Doing This, Must Connect with DBS. • Notify Object(NO) • Analyzes The Registered Information above, Extracts Violated Situation of QoS, And Then Requests Resource Adaptation for Considering Violated Situation • DB Logic • Used by MO and BO.

  16. Design : Class Diagram of UCM

  17. QoSM Control Manager Interface Mapper CORBA Design : Objects in QoSM • QoS Management Module(QoSM) • Executes QoS Maintenance and Control Functions for Stream Services • Manager Interface Object(MIO) • Requests ICM to QoS Control, Manages Object in QoSM • Mapper Object(MO) • Provides Register, Update and Delete Functions of QoS MIB in Accordance with Stream Service Situation • Maintains and Manages System Catalog • Control Object(CoO) • Supports Negotiation and Adaptation by Request of UCM • Stream Send/Receive Objects • Objects or Application Programs Executing for Sending/Receiving Stream Packets

  18. Design : Class Diagram of QoSM

  19. UCM(receive) QoSM UCM(send) Design : QoS Control Mechanism(Negotiation) • Negotiation Methodology • UCM Receiving Stream Data Requests QoS Reconfigure Via User Interface Object • UIO Requests CoO(Control Object) to Negotiate QoS Level for Appropriate Stream Service Between End-to-End Systems • In This Time, CoO Checks Whether It May Provide Desiring QoS Level or Not by Applying Given QoS Levels of Network Resources and The Receiving System Resource • Finishing Negotiation, The Stream Sending Object Resets Negotiated QoS Level negotiation rule setup <frame rate> <resolution> <cpu> reconfigure <qos level> User Interface Object Control Object Stream Object read status <cpu> <memory> MIB List <qos level> <frame rate> <encoding> <resolution> : Mapper Object

  20. Design : Sequence Diagram of Negotiation UCM (send) UCM (receive) QoSM

  21. DB Design : QoS Control mechanism(Monitoring) • Monitoring Methodology • Monitoring Object Writes Monitoring Data Acquired by Stream Object to DB read status <frame rate> <encoding> <resolution> : write DB <frame rate> <encoding> <resolution> : JDBC & API Monitor Object Stream Object UCM(receive)

  22. Design : Sequence Diagram of Monitoring UCM (receive)

  23. DB adaptation rule violation detect setup <frame rate> <resolution> <cpu> adaptation <frame rate> <resolution> <cpu> read DB <frame rate> <resolution> <bit rate> JDBC & API Notify Object Control Object Stream Object read MIB List <qos level> <frame rate> <bit rate> <resolution> : Mapper Object UCM(receive) QoSM UCM(send) Design : QoS Control mechanism(Adaptation) • Adaptation Methodology • Reads Service Status Written by Monitoring Object From DB • After Analyzing Above Information, Checks Whether Negotiated QoS Is Violated or Not • If Violated, Notify Object Requests Resource Adaptation Methodology to Control Object Using Adaptation Message • Control Object Selects Appropriate QoS Level From QoS MIB, And Setup It to Stream Object

  24. Design : Sequence Diagram of Adaptation UCM (send) UCM (receive) QoSM

  25. QoSM Server(Sending Stream Data) Client(Receiving Stream Data) • Systems : Sun UltraSparc 1s, UltraSparc 2i • OS : Solaris 2.5(client), Solaris 2.7(server) • Middleware : OrbixWeb3.1c • Developing Tool: Java,JDK1.2.x, JMF API 2.0 • DB Engine : Mini SQL 1.0.16 • Additional Devices: Sun Camera, SunVideo/SunVideoPlus Capture Board UCM UCM UCM UltraSparc 2i Solaris 2.7 SunVideoPlus + Sun Camera UltraSparc 1s Solaris 2.5 SunVideo Stream flow Control flow Implementation : Developing Environment • Developing Environment

  26. Implementation : Data Structure of IDL // Service Staus Factor struct qosparam { float framerate; long resolution; float cpu; }; // catalog, QoS MIB Index typedef sequence<member> catalogList; typedef sequence<videoMIB> mibList; // forwarding declaration interface ManagerInterface; interface UserInterface; // User Information Structure struct member { string name; string ip; string hostname; }; // Video QoS MIB Structure struct videoMIB { long level; float framerate; string encode; string resolution; float cpu; long buffersize; long packetsize; };

  27. Implementation : IDL of User Control Model // IDL Definition of UCM interface UserInterface { // Attributes attribute Connect conManager; attribute Service servManager; attribute ManagerInterface miManager; // Operations boolean start(in string local, in string remote, in string manager, in string dbport); boolean stop(); boolean reconfigure(in long qoslevel); boolean refresh(); boolean start_media(in qosparam param); boolean setup_media(in qosparam param); boolean stop_media(); boolean rcall(in string local, in string remote, in string manager); }; // IDL Definition of Connect Object interface Connect { // Operations boolean start(in member receive, in member send); boolean stop(); boolean join(); boolean disjoin(); boolean initial(in UserInterface ui, in string manager); }; // IDL Definition of Service Object interface Service { // Operations void start(in boolean isSend, in long srate, in long drate, in qosparam param); boolean stop(); boolean setup(in qosparam param); boolean setup_notify(in long rate, in qosparam param); boolean setup_monitor(in long rate); qosparam getstatus(); boolean initial(in UserInterface ui, in string manager); };

  28. Implementation : IDL of QoSM boolean start(); boolean stop(); boolean negotiation(in long qoslevel); boolean adaptation(in long qoslevel, in qosparam param); boolean initial(in ManagerInterface mi, in string remote); }; // IDL Definition of Mapper Object interface Mapper { // Attributes attribute catalogList serverTbl; attribute mibList videoTbl; // Operations boolean start(); boolean stop(); boolean connect(in member receive, in member send); boolean disconnect(); boolean register(in member mem); boolean unregister(in member mem); catalogList getServerTbl(); mibList getVideoTbl(); boolean initial(in ManagerInterface mi, in string remote); }; // IDL Definition of QoSM interface ManagerInterface { // Attributes attribute Mapper mapManager; attribute Control ctlManager; attribute UserInterface uiManager; // Operations boolean start(in string local, in string remote, in string manager); boolean stop(); boolean connect(in member receive, in member send); boolean disconnect(); boolean negotiation(in long qoslevel); boolean adaptation(in long qoslevel, in qosparam param); catalogList getServerTbl(); }; // IDL Definition of Control Object interface Control { // Operations

  29. Implementation : DB Scheme for Monitoring • DB Engine • Use Mini SQL 1.0.16 (RDBMS) • Designs Control Routines Using imaginary JDBC 2.0 for Interconnecting with DBS • Schema Design Table Name Attribute Name Attribute Type Sample T_Monitor A_Counter Integer 251 A_Member Char(25) root@210.112.129.32 A_Compress Char10) Jpeg/rtp A_Framerate Real 15.0 A_Resolution Char(10) 160 x 120 A_Bitrate Integer 700,000 A_BufferSize Integer 270 A_PacketSize Integer 1024 A_Quality Real 1.0

  30. Implementation : Definition of QoS MIB • At Point of View of User Level QoS • Matching Between User-Level QoS And Application-Level QoS • Matching Between Application-Level QoS And System & Network-Level QoS class Frame Rate Resolution Bit Rate CPU class Service Quality 5 25 ~ 30 160 x 120 700,000 1.0 5 Excellent 5 25 ~ 30 160 x 120 650,000 1.0 4 Good 5 25 ~ 30 160 x 120 600,000 1.0 3 Fair 4 15 ~ 24 160 x 120 550,000 0.8 Frame Rate, Resolution 2 Poor 4 15 ~ 24 160 x 120 500,000 0.8 1 Bad 4 15 ~ 24 160 x 120 450,000 0.8 400,000 0.6 3 6 ~ 14 160 x 120 350,000 0.6 3 6 ~ 14 160 x 120 class Frame Rate Resolution Bit Rate, CPU 3 6 ~ 14 160 x 120 300,000 0.6 5 25 ~ 30 160 x 120 2 3 ~ 5 160 x 120 250,000 0.4 4 15 ~ 24 160 x 120 2 3 ~ 5 160 x 120 200,000 0.4 3 6 ~ 14 160 x 120 2 3 ~ 5 160 x 120 150,000 0.4 2 3 ~ 5 160 x 120 1 1 ~ 2 160 x 120 100,000 0.2 1 1 ~ 2 160 x 120

  31. Implementation : Stream Object • Interfaces of Stream Object • Interfaces : start, stop, setup, getStatus • Implemented Detailed Contents • Using JMF 2.0 API • JPEG : Stream Send/Receive Functions of Encoding Formats • H261, H263 : Receive Function of Encoding Formats • Supporting Resolutions of 160 X 120, 320 X 240 • Re-producing Stream Data And Capturing f 30 frames/Second • Sending/Receiving Stream Data Using RTP Protocol

  32. Executing Result : The Side of Client(1) • Users Can Adjust Service of Quality on Window of Client’s Side via Interfaces with QoSM suggested Register IP addresses of Client’s UCM, Server’s and QoSM on below Panel Register Users’ Individual Information, DB Connection Port and Stream Sending/Receiving Ports to above Panel

  33. Executing Result : The Side of Client(2) Left ProgressBar -> The QoS Level Receiving Current Service Right SliderBar -> Select The Desiring QoS Level The Parameters of Stream Receiving Status Shown on Right Screen; BitRate, FrameRate, Encoding, CPU capacity, Buffer Size

  34. Executing Result : The Side of Server(1) • Selecting Capture Board • If Service Connection is Success, Set Stream Object into The Sending Mode • In This Procedure, Selecting The Appropriate Service Device Out of Menu Shown on Capture DeviceBox The Panel is showing Capture Device Index Registered on Server In Panel, Select The parameters of Encoding Format, Size, maximum And Frame Rate Supporting by Capture Device

  35. Executing Result : The Side of Server(2) Encode Image Captured to JPEG(or H261, H263) File, And Then, Send RTP Packets Via Stream Object to Stream Object of Side of Client In This Window, Show Parameters of Receiving Status of Stream Data as follows; BitRate, FrameRate, Encoding, Resolution CPU Capacity, Buffer Size And etc.

  36. Executing Result : Monitoring DB Monitored Data Obtained by Monitor Object

  37. Executing Result : Negotiation Procedure Client Side Users Can Reset QoS Level Using Vertical Slide Bar Server Side Show A Procedure That Is Reset Appropriate QoS Level to Meet User Requirements Via Stream Object

  38. Executing Result : Adaptation Procedure Client Side Show A Status That Service is Not Met to QoS 4-Level Promised. That is, Appropriate Service is Not Supported. Server Side Adapt The existing QoS Level To Appropriate Low-Level Considering Current Network Situation

  39. Executing Client And Server Screens • Executing Screens Executing Screen of Client Side Executing Screen of Server Side

  40. Conclusions : Summaries • Trends Text- Based Services toward Multimedia-Based Services • Needs User-Centralized QoS • Specification of Analyzing QoS And Requirements • Supporting Independently Stream Services on Distributed • Suggested And Implemented QoS Management Model for Integrating Multimedia Service And QoS management • User Control Module(UCM) • QoS Management Module(QoSM) • Stream Object • Integration of Stream Technology And CORBA Technology

  41. Monitor Stream Service Application Application Stream Object Stream Object QoS Application Application Network Operation Service Object & ObjectGroup Object & ObjectGroup Object & ObjectGroup Distributed Computing Middleware Trader Trader Federation Trader Trader Future Works • Future Works • Extending the Management Structure Possible to Service for Multicasting • Supporting Multi-Stream Services • Adding Session Management to Our Model • Studying Interconnections Among Distributed Stream Objects Using Trading Service

More Related