1 / 40

RGPS Metamodel Framework for Interaction between cloud and client

32N1891. RGPS Metamodel Framework for Interaction between cloud and client. HE Yangfan, HE Keqing, WANG Jian, WANG Chong SKLSE(WHU), P.R.China. Content. Background RGPS Metamodel Framework Interaction between Cloud and Client enabled by RGPS Standardization of RGPS. Content. Background

xiu
Download Presentation

RGPS Metamodel Framework for Interaction between cloud and client

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. 32N1891 RGPS Metamodel Framework for Interaction between cloud and client HE Yangfan, HE Keqing, WANG Jian, WANG Chong SKLSE(WHU), P.R.China

  2. Content Background RGPSMetamodel Framework Interaction between Cloud and Client enabled by RGPS Standardization of RGPS

  3. Content Background RGPSMetamodel Framework Interaction between Cloud and Client enabled by RGPS Standardization of RGPS

  4. Background of Cloud Computing • Drawbacks of current software application model • Unused parts of software, a waste of money… • Solution provided by cloud computing • Simplified client side & Data centers • Software is delivered by means of service—SaaS • Users just pay for each use of service, i.e. pay per use • On-demand service

  5. An example of cloud computing

  6. Basic types and main user groups of cloud computing applications Extra service： Improved function enabled by cloud service Cloud platform： Applications built on top of the platform SaaS: Applications run in cloud Local Deployment Client （From David Chappel, A Short Introduction To Cloud Platforms，2008）

  7. Various kinds of cloud • Different requirements lead to different kinds of cloud • Google：Application cloud • From improved searching engine to large scale infrastructure service • Amazon, SalesForce：Platform cloud • Brokered SaaS e- e-business platform • Providing infrastructure as service, on which people could build their own applications • IBM：Middleware cloud • Applications are supposed to be delivered on Internet by means of “service”. • Providing middleware based on Internet • Providing computing platform for sale • Blue Cloud • Microsoft：Windows on Internet？ • S+S • Azure • ……

  8. Standards for cloud computing • Various clouds Construction and connection of clouds should be well ensured. • Interfaces defined in current cloud computing resolutions are not compatible with each other. • E.g. IBM, Google. Salesforce… • ISO standards are needed in this field. • Standards about interoperation between cloud and client are missing. • People’s confidence cloud computing may be hampered. • Standards about interaction between cloud and client will be the focus in the competition between cloud services. RGPS will play an important role!

  9. R/G/P/S elements and cloud virtualization • Interaction between Cloud and Client • Cloud virtualization • Client-Role • Goal • Process • Services • Resource (Data/Components/Middleware/Devices/…) Harmonious interaction between people/web/service Virtualizations of people The world of Web (Semantic Web) The world of resource

  10. Virtualization based on RGPS End user Cloud image Service requirement R G P S Service requirement Cloud-client interaction R&R Developer Registry Applications delivered by means of “service” Repository Data center

  11. Relationship between RGPS/ROR/UDDI SaaS PaaS IaaS XaaS RGPS Registry Accounting Service End user UDDI MSDS Reg. Service Developer Part Retrieval Service ROR Registry Registry Registry Registry 11 Logistic Manufacturing Retails

  12. Content • Background • RGPSMetamodel Framework • Overview • RGPS vs. SSOA • Interaction between Cloud and Client enabled by RGPS • Standardization of RGPS

  13. RGPS metamodel framework R G P S

  14. Metamodel of Role and Goal 14

  15. Metamodel for process model registration 15

  16. Metamodel of Service Registration Capability_Related Interface_Related Interaction_Related

  17. Dynamic Context Profile Contextual Property Contextual Expectation Contextual Depend Object Process hasObject Atomic Process Composite Process P Input hasInput hasOutput Service Output Atomic Service Composite Service Operation hasOperation Message hasMessage Applying RGPS for Cloud Modeling Functional Goal: Sort Order consistsOf plays Actor Role Organization R Semantic Annotation prefers takesCharge Personal Goal Role Goal Entity Ontology Goal Nonfunctional Goal Functional Goal Operation Ontology G contributes achieves Context Ontology Domain Ontologies realizes S

  18. Process Atomic Process Composite Process P Service Atomic Service Composite Service From the Perspective of W5H consistsOf plays Actor Role Organization Who R prefers takesCharge Semantic Annotation Personal Goal Role Goal Entity Ontology Goal Why Nonfunctional Goal Functional Goal Operation Ontology G contributes achieves When Context Ontology What Where realizes Domain Ontologies How S

  19. Sam Chance, DOD,SRC,US,9th Open Forum on Metadata Registries,2006.3

  20. Kevin Keck, ISO/IEC SC32 Workshop,2008.9.4

  21. ? Kevin Keck,ISO/IEC SC32 Workshop, 2008.9.4

  22. ? Client (role) Registry ? Semantic Goal Registry Role layer is also an important addition! Kevin Keck,ISO/IEC SC32 Workshop, 2008.9.4

  23. Content • Background • RGPS Metamodel Framework • Interaction between Cloud and Client enabled by RGPS • Typical cases • RGPS based toolkit for cloud construction • Standardization of RGPS

  24. Role Model R G Goal Model P Process Model S Service Model RGPS based Cloud Selection Process (Case 1) Developer Atomic Process Operational Goal Upper Goal Model Sign Model Concept Model Selection Model Instance Operational Goal Process Service

  25. Role Model R G Goal Model P Process Model S Service Model RGPS based Cloud Selection Process (Case 2) Developer Atomic Process Process Model Sign Model Concept Model Selection Model Instance Atomic Process Service

  26. Role Model R G Goal Model P Process Model S Service Model RGPS based Cloud Selection Process (Case 3) End User Model Sign Model Concept Model Selection Model Instance

  27. Role Model R G Goal Model P Process Model S Service Model RGPS based Cloud Selection Process (Other Cases) All depend on user’s target! Model Sign Model Concept Model Selection Model Instance

  28. Cloud image based on RGPS Domain entity ontology Domain operation ontology Cloud image Domain problem ontology (DPO) Role model R Goal model G Process model P Service model S

  29. Weather forecasting service cloud image Cloud image for service

  30. Cloud Image and RGPS DPO Role Process Weather forecasting service cloud Goal Service

  31. O-RGPS based toolkitfor cloud construction (1/2) O-RGPS R G P S

  32. O-RGPS based toolkit for cloud construction (2/2) Transportation cloud image 32

  33. Content Background RGPS Metamodel Framework Interaction between Cloud and Client enabled by RGPS Standardization of RGPS

  34. SC32’s Scope • Standards for data management within and among local and distributed information systems environments. SC32 provides enabling technologies to promote harmonization data management facilities across sector-specific areas. Specifically, SC32 standards include: • reference models and frameworks for the coordination of existing and emerging standards; • definition of data domains, data types and data structures, and their associated semantics; • languages, services and protocols for persistent storage, concurrent access, concurrent update and interchange of data; • methods, languages, services and protocols to structure, organize and register metadata and other information resources associated with sharing and interoperability, including electronic commerce. from www.jtc1sc32.org

  35. Standards for interoperation between cloud and client RGPS MFI (ISO/IEC 19763) MFI Extension for Cloud Computing MFI-6Registry of Registries MFI-5Metamodel for process registration MFI-TROn-demand cloud selection based on RGPS and ROR MFI-8 Metamodel for Role and Goal Registration MFI-3Metamodel for ontology registration MFI-4Metamodel for model mapping MFI-7Metamodel for Service Registration

  36. ISO/IEC 19763-8: Metamodel for Role and Goal Registration From resolution of Wuhan Meeting, September, 2008

  37. MFI-TR: Using RGPS for on demand model selection On-demand cloud selection based on RGPS and ROR From resolution of Wuhan Meeting, September, 2008

  38. Summary • Standards about interaction between cloud and client will be the focus in the competition between cloud services. • SC32 should take a quick action to catch this opportunity! • Wuhan University has foundation for the research on cloud computing standards. • We need further support from ISO/IEC JTC1 SC32! • We request the subdivision of MFI-8 and TR in the SC32 plenary this year!

  39. RGPS & Cloud Computing Thank you!! Q&A heyangfan927@163.com hekeqing@sklse.org wangjian_sd@163.com wangchong_whu@yahoo.com.cn

  40. New caGrid Metadata needs for Service Discovery/use (NCI Chicago meeting) • Fault (extended to include Errors and error descriptions) • Service Taxonomy • Synchronous/asynchonous • Related Services • Service Dependency (especially if nested services, or workflow) • End Points • Preconditions • Post Conditions • Platform • Provenance (of Data service) (Boston F2F) • Reliability of Data • Currency of Data • Authoritativeness of Data (Analogous to Term. Service metadata?) • Authoritative source? (eg regulatory body?) • Quality of Service • Reliability of service • Minimum response time • Uptime • Known Limitations/Known Defects

More Related