Recent developments in middleware standardization for â€¢OMG

1

MiNEMA Summer School – Klagenfurt, Austria © Kimmo Raatikainen July 15, 2005

Recent developments in Recent developments in middleware standardization for middleware standardization for

mobile computingmobile computing

Kimmo RaatikainenUniversity of Helsinki

Department of Computer [email protected]

http://www.cs.helsinki.fi/Kimmo.Raatikainen/

MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005 Kimmo Raatikainen 2

PresentationPresentation OutlineOutline

• Framework• OMG• IETF• OMA• W3C• J2ME

• Liberty• WS-I• OASIS• UPnP• DLNA• OSGi


FrameworkFramework

WWRF Reference Model


Self-Actualisation

Safety BelongingControlPrivacy

Human CapabilityAugmentation

Values

Personalization AmbientAwareness

Adaptation

Ubiquity

Consistency

Capabilities

Computing and CommunicationHard- and Firmware

Operating System

Internet Protocol Suite

Mobile MiddlewareUI

Support

Open APIs

App App App

WWRF HighWWRF High--level Reference Modellevel Reference Model


MobileMiddleware

Computing and Communication Hard- and Firmware

Operating System


UI Support

Execution Environment

Environment

Monitoring

EventN

otifications

ServiceD

iscovery

ConfigurationM

anagement

Mobile D

ataM

anagement

Trust and Privacy Support

Context M

odeling Tools

GenericServiceElements…

Open APIs

Mobile MiddlewareMobile Middleware


Implementation ViewImplementation View

Computing and Communication hardware

Operating System

User Interaction Support


Application Application Application

Mobile Middleware

Socket API

Decice Drivers

Open APIsSocket API Posix API

DeciceDrivers

DeciceDrivers

System Call Interface / Posix API

2


Key Key FunctionalitiesFunctionalities

Security – Trust – Privacy

Interoperability

Context Sensitivity and Adaptation

Mobility and Efficient Always-On Connectivity

Discovery

…


Software ArtifactsSoftware Artifacts

Security – Trust – Privacy

Interoperability

Context Sensitivity and Adaptation

Mobility and Efficient Always-On Connectivity

Discovery

…

Operating System

s

Internet Protocols

Middlew

are

User Interaction


StandardizationStandardization JungleJungle


Object Management GroupObject Management Group

OMG SpecificationsOMG Modeling SpecificationsCORBA/IIOP Specifications

CORBA Security SpecificationsIDL / Language Mapping Specifications

Specialized CORBA Specifications OMG Embedded Intelligence Specifications

CORBAservices Specifications CORBAfacilities Specifications OMG Domain Specifications


OMG SpecificationsOMG Specifications

• OMG Modeling and Metadata Specifications– UML, MOF, XMI, CWM and Profile Specifications

• OMG Middleware Specifications– CORBA/IIOP Specifications – IDL / Language Mapping Specifications – Specialized CORBA Specifications – CORBA Component Model (CCM) Specification

• Platform Independent Model (PIM), Platform Specific Model (PSM) and Interface Specifications– CORBAservices Specifications – CORBAfacilities Specifications – OMG Domain Specifications – OMG Embedded Intelligence Specifications – OMG Security Specifications


OMG Modeling SpecificationsOMG Modeling Specifications

• Common Warehouse Metamodel (CWM™)• Common Warehouse Metamodel (CWM™) Metadata

Interchange Patterns (MIPS)• Meta-Object Facility (MOF™)• Software Process Engineering Metamodel (SPEM)• Unified Modeling Language™ (UML™)• UML Human-Usable Textual Notation (HUTN)• UML™ Profile for CORBA®• UML™ Profile for Enterprise Application Integration (EAI)• UML™ Profile for Enterprise Distributed Object Computing

(EDOC)• UML™ Profile for Schedulability, Performance and Time• UML™ Testing Profile• XML Metadata Interchage (XMI®)

3


CORBA/IIOP SpecificationsCORBA/IIOP Specifications

• Common Object Request Broker Architecture (CORBA/IIOP)• Common Secure Interoperability (CSIv2)• CORBA Component Model• CORBA-FTAM/FTP Interworking• CORBA / TC Interworking and SCCP-Inter ORB Protocol• CORBA-WSDL/SOAP Interworking• Deployment and Configuration of Component-based Distributed

Applications• Fault Tolerance• Firewall Traversal • Interworking between CORBA and TMN Systems• Online Upgrades• Wireless Access & Terminal Mobility in CORBA• WSDL/SOAP-CORBA Interworking


CORBA Security SpecificationsCORBA Security Specifications

• Authorization Token Layer Acquisition Service (ATLAS)• Common Secure Interoperability (CSIv2)• Security Service• Resource Access Decision Facility


IDL / Language Mapping IDL / Language Mapping SpecificationsSpecifications

• Ada• C• C++• COBOL• CORBA Scripting Language• IDL to Java• Java to IDL• Lisp• PL/1• Python• Smalltalk• XML


Specialized CORBA SpecificationsSpecialized CORBA Specifications

• Data Distribution• Data Parallel Processing• Dynamic Scheduling• Lightweight Logging Service• Minimum CORBA• Online Upgrades• Real-Time CORBA Architecture• Unreliable Multicast


CORBA Embedded Intelligence CORBA Embedded Intelligence SpecificationsSpecifications

• Smart Transducers


CORBAservicesCORBAservices SpecificationsSpecifications

• Additional Structuring Mechanisms for the OTS

• Collection Service• Concurrency Service• Enhanced View of Time• Event Service• Externalization Service• Licensing Service• Life Cycle Service• Management of Event

Domains• Naming Service

• Notification Service• Notification / JMS

Interworking• Persistent State Service • Property Service• Query Service• Relationship Service• Security Service• Telecoms Log Service• Time Service• Trading Object Service• Transaction Service

4


CORBAfacilitiesCORBAfacilities SpecificationsSpecifications

• Internationalization and Time• Mobile Agent Facility


OMG Domain SpecificationsOMG Domain Specifications

• Air Traffic Control• Audio / Visual Streams• Bibliographic Query Service• Biomolecular Sequence

Analysis (BSA)• Clinical Observations Access

Service (COAS)• Computer Aided Design

(CAD) Services• CORBA-FTAM/FTP

Interworking• CORBA / TC Interworking

and SCCP-Inter ORB Protocol

• Currency• Data Acquisition from

Industrial Systems (DAIS)• Distributed Simulation

Systems• Federated Charging• General Ledger• Gene Expression• Genomic Maps• GIOP Tunneling over

Bluetooth• Historical Data Acquisition

from Industrial Systems (HDAIS)



• Interworking between CORBA and TMN Systems

• Laboratory Equipment Control Interface Specification (LECIS)

• Lexicon Query Service• Lightweight Logging Service• Macromolecular Structure• Management of Event

Domains• Negotiation Facility• Notification / JMS

Interworking• Organizational Structure

(OSF)

• Party Management Facility• Person Identification Service

(PIDS)• PIM and PSM for SDO• Product Data Management

(PDM) Enablers• Public Key Infrastructure

(PKI)• Resource Access Decision

(RAD)• Surveillance User Interface

(Surveillance Manager)• Task and Session• Telecoms Log Service



• Telecom Service & Access Subscription (TSAS)

• Telemetry and TelecommandData (XTCE)

• Utility Management Systems (UMS) Data Access Facility

• Wireless Access & Terminal Mobility in CORBA (Telecom Wireless)

• Workflow Management Facility


IETFIETF

IETF Working AreasIETF Working Groups

SIMPLE WG: SIP for Instant Messaging and Presence Leveraging Extensions


IETF IETF WorkingWorking AreasAreas

• Applications Area (14 working groups)• General Area (2)• Internet Area (24)• Operations and Management Area (21)• Routing Area (15)• Security Area (20)• Transport Area (26)

5


IETF IETF WorkingWorking GroupsGroups ……

• Applications Area (14)– Atom Publishing Format and Protocol, Cross

Registry Information Service Protocol, Electronic Data Interchange-Internet Integration, Geographic Location/Privacy, Internet Message Access Protocol Extension, LDAP (v3) Revision, Enhancements to Internet email to support diverse service environments, Language Tag Registry Update, NNTP Extensions, Open Pluggable Edge Services, Sieve Mail Filtering Language, SIP for Instant Messaging and Presence Leveraging Extensions, Usenet Article Standard Update, WWW Distributed Authoring and Versioning

• General Area (2)– Intellectual Property Rights, New IETF Standards

Track DiscussionMiNEMA Summer School – Klagenfurt, Austria – July 15, 2005 Kimmo Raatikainen 26

…… IETF IETF WorkingWorking GroupsGroups ……• Internet Area (24)

– IPv6 over Low power WPAN, Dynamic Host Configuration, Detecting Network Attachment, DNS Extensions, Extensible Authentication Protocol, Host Identity Protocol, IP over DVB, IP over InfiniBand, IP over Resilient Packet Rings, IP Version 6 Working Group, Layer Two Tunneling Protocol Extensions, Layer 2 Virtual Private Networks, Layer 3 Virtual Private Networks, Multicast & Anycast Group Membership, Mobility for IPv4, Mobility for IPv6, MIPv6 Signaling and Handoff Optimization, Network Mobility, Network Time Protocol, Protocol for carrying Authentication for Network Access, Point-to-Point Protocol Extensions, Pseudo Wire Emulation Edge to Edge, Site Multihoming by IPv6 Intermediation, Transparent Interconnection of Lots of Links


…… IETF IETF WorkingWorking GroupsGroups ……

• Operations and Management Area (21)– Authentication, Authorization and Accounting;

ADSL MIB; Benchmarking Methodology; Bridge MIB; Control And Provisioning of Wireless Access Points; Distributed Management; Domain Name System Operations; Entity MIB; Global Routing Operations; Ethernet Interfaces and Hub MIB; Internet and Management Support for Storage; IP over Cable Data Network; IP Flow Information Export; MBONE Deployment; Site Multihoming in IPv6; Network Configuration; Operational Security Capabilities for IP Network Infrastructure; Packet Sampling; RADIUS EXTensions; Remote Network Monitoring; IPv6 Operations



• Routing Area (15)– Bidirectional Forwarding Detection; Common

Control and Measurement Plane; Forwarding and Control Element Separation; Inter-Domain Routing; IS-IS for IP Internets; Layer 1 Virtual Private Networks; Mobile Ad-hoc Networks; MultiprotocolLabel Switching; Open Shortest Path First IGP; Path Computation Element; Protocol Independent Multicast; Routing Protocol Security Requirements; Routing Area Working Group; Source-Specific Multicast; Virtual Router Redundancy Protocol



• Security Area (20)– Better-Than-Nothing Security, Credential and

Provisioning, Intrusion Detection Exchange Format, Extended Incident Handling, Integrated Security Model for SNMP, Kerberized Internet Negotiation of Keys, Kitten (GSS-API Next Generation), Kerberos WG, Long-Term Archive and Notary Services, IKEv2 Mobility and Multihoming, Multicast Security, An Open Specification for Pretty Good Privacy, Profiling Use of PKI in IPSEC, Public-Key Infrastructure (X.509), Securely Available Credentials, Simple Authentication and Security Layer, Secure Shell, S/MIME Mail Security, Security Issues in Network Event Logging, Transport Layer Security


…… IETF IETF WorkingWorking GroupsGroups

• Transport Area (26)– Audio/Video Transport, Behavior Engineering for Hindrance

Avoidance, Datagram Congestion Control Protocol, Emergency Context Resolution with Internet Technologies, Telephone Number Mapping, Internet Emergency Preparedness, IP Performance Metrics, IP Storage, IP Telephony, Media Gateway Control, MiddleboxCommunication, Multiparty Multimedia Session Control, Network File System Version 4, Next Steps in Signaling, Path MTU Discovery, Remote Direct Data Placement, Reliable Multicast Transport, Robust Header Compression, Reliable Server Pooling, Signaling Transport, Session Initiation Protocol, Session Initiation Proposal Investigation, Speech Services Control, TCP Maintenance and Minor Extensions, Transport Area Working Group, Centralized Conferencing

6


SIMPLE WGSIMPLE WG

• Applying the Session Initiation Protocol (SIP, RFC 3261) to Instant Messaging and Presence Services

• Based on SIP-Specific Event Notification (RFC 3265)– SUBSCRIBE– NOTIFY– Usage tailored message formats and semantics


RFCsRFCs fromfrom SIMPLE WGSIMPLE WG

RFC 3856: A Presence Event Package for the Session Initiation Protocol (SIP)

RFC 3857: A Watcher Information Event Template-Package for the Session Initiation Protocol (SIP)

RFC 3858: An Extensible Markup Language (XML) Based Format for Watcher Information

RFC 3994: Indication of Message Composition for Instant Messaging


SIMPLE SIMPLE WorkWork RecentlyRecently CompletedCompleted

• Functional Description of Event Notification Filtering – RFC Editor Queue

• An Extensible Markup Language (XML) Based Format for Event Notification Filtering – RFC Editor Queue

• The Extensible Markup Language (XML) Configuration Access Protocol (XCAP) – RFC Editor Queue

• Extensible Markup Language (XML) Formats for Representing Resource Lists – RFC Editor Queue

• An Extensible Markup Language (XML) Configuration Access Protocol (XCAP) Usage for Manipulating Presence Document Contents – RFC Editor Queue


SIMPLE SIMPLE WorkWork in in ProgressProgress ((II--DsDs) …) …

• CIPID: Contact Information in Presence Information Data Format• A Session Initiation Protocol (SIP) Event Notification

Extension for Resource Lists – IESG Evaluation• Timed Presence Extensions to the Presence Information Data

Format (PIDF) to Indicate Status Information for Past and FutureTime Intervals

• The Message Session Relay Protocol• Relay Extensions for the Message Sessions Relay Protocol

(MSRP)• Session Initiation Protocol (SIP) extension for Partial Notification of

Presence Information


…… SIMPLE SIMPLE WorkWork in in ProgressProgress ((II--DsDs))

• Presence Information Data format (PIDF) Extension for Partial Presence

• Partial Publication of Presence Information• User Agent Capability Extension to Presence Information Data

Format (PIDF)• A Data Model for Presence• Presence Authorization Rules• RPID: Rich Presence Extensions to the Presence Information Data

Format (PIDF)• An Extensible Markup Language (XML) Document Format for

Indicating Changes in XML Configuration Access Protocol (XCAP) Resources


Open Mobile AllianceOpen Mobile Alliance

OverviewTechnical Plenary Working Groups

WG DescriptionsCurrent Work Items

OMA Release ProgramCandidate Enabler ReleasesApproved Enabler ReleasesRequirements DocumentsOMA Service Environment

7


OverviewOverview

• consolidation of six industry forums– SyncML initiative,– Wireless Village,– Location Interoperability Foru (LIF),– WAP Forum,– Mobile Wireless Internet Forum (MWIF),and– Mobile Gaming Interoperability Forum (MGIF).

• More than 300 companies:– whole mobile value chain:

• mobile operators,information technology companies,wireless vendors and application and content providers.


OMA PrinciplesOMA Principles

• Products and services are based on open, global standards, protocols and interfaces and are not locked to proprietary technologies

• The applications layer is bearer agnostic (examples: GSM, GPRS, EDGE, CDMA, UMTS)

• The architecture framework and service enablers are independent of Operating Systems (OS)

• Applications and platforms are interoperable, providing seamlessgeographic and inter-generational roaming


EndEnd--toto--endend interoperabilityinteroperability

SyncML Wireless VillageMMS-IOP LIF

Across standards and

specification forumsOMA

Browsing MMS Presence LocationAcross

enabling technologies

OMA

Terminals Apps and ServersNetworks Content

& MediaAcross

services and productsOMA

ITOperators Wireless Vendors

Content & Media

Across companies of

end-to-end value chainOMA

Examplesof end-userservicescenarios

Messaging/ imaging

Mobileworkplace

Mobile Infotainment

Examples


Technical Plenary Working GroupsTechnical Plenary Working Groups

• Architecture • Browser & Content• Data Synchronization• Developers Interest

Group• Device Management• Games Services• Interoperability• Location• Messaging • Mobile Commerce &

Charging

• Mobile Web Service• Operations & Process • Presence & Availability • Push to Talk Over

Cellular• Release and Planning

Management• Requirements• Security


WG WG DescriptionsDescriptions ……

• Architecture – The OMA architecture Working Group is responsible for

defining the overall OMA architecture, advising and assisting the architecture specification work in work groups and assuring, through review, adherence of specification work to OMA architecture...

• Browser & Content– The Browser & Content Working Group is responsible for the

specification of application technologies used in the open mobile architecture...

• Data Synchronization– The Data Synchronization Working Group continues the work

originated in the former SyncML Initiative. The group continues development of specifications for data synchronization, and the development of other similar specifications, including but not limited to SyncMLtechnology...


…… WG WG DescriptionsDescriptions ……

• Developers Interest Group– The Developers Interest Working Group collects and

publishes data relevant to developers, provides a means for software developers to articulate and specify their needs to OMA and identifies missing or inconsistent developer interfaces..

• Device Management– The Device Management Working Group defines

management protocols and mechanisms that enable robust management of the life cycle of the device and its applications over a variety of bearers. The Device Management Working Group continues the work previously conducted in the former WAP Forum and SyncML initiatives....

8



• Games Services– The Games Services Working Group continues the work of

the Mobile Games Interoperability Forum (MGIF). The Games Services group is responsible for developing interoperability specifications, APIs and protocols for network enabled gaming, as well as, enabling game developers to develop and deploy mobile games to efficiently interoperate with OMA platforms and enable cost reduction for game developers, game platform owners and service providers...

• Interoperability– The OMA Interoperability (IOP) Working Group acts as a

center of excellence to identify, specify and maintain the required processes, policies and test programs for ensuring interoperability for OMA specified enablers and end-to-end services...



• Location– The OMA Location Working Group continues the work

originated in the Location Interoperability Forum (LIF). This group develops specifications to ensure interoperability of Mobile Location Services on an end-to-end basis...

• Messaging– The OMA Messaging Working Group is responsible for the

specification of messaging and related enabling technologies. The goal of Messaging Working Group is to specify a set of basic messaging features that may be used to enable specific messaging paradigms...

• Mobile Commerce & Charging– The MCC is specifying a charging enabler to support the

existing and emerging OMA enablers. This charging enabler defines the charging data triggers and the information flow from OMA enablers into an underlying charging system.



• Mobile Web Service– OMA's Mobile Web Services Working (MWS) Group is

responsible for developing a specification that defines the application of web services within the OMA architecture and ensure that the specification provides for the application of web services that is converged with the work of external activities...

• Operations & Process – The Operations and Process Committee of OMA provides

support on operational and process activities. From a Process perspective, the Operations and Process Committee develops and maintains the Process Materials by which the OMA Technical Plenary operates. This includes the review and analysis of the impacts of the process on the organization.



• Presence & Availability– The Presence and Availability Working Group has the goals of

specifying the service enablers to permit the deployment of interoperable mobile presence and availability services. “Presence and availability services” enable applications to exchange dynamic information (e.g. status, location, and capabilities) about resources (e.g. users and devices)…

• Push to Talk Over Cellular– The Push to talk over Cellular (PoC) WG is positioned to

develop application enabling specifications to permit the deployment of interoperable PoC services… The initial work of the Working Group will be focused on the tasks required to develop specifications for an open standard to enable adoption of PoC service over mobile networks…


…… WG WG DescriptionsDescriptions

• Release and Planning Management – The OMA Release Planning and Management Committee is a

committee of the OMA Technical Plenary responsible for planning and managing OMA Releases, defining OMA Releases based on OMA specifications and Interoperability Testing programmes, and defines the Release planning process...

• Requirements– The OMA Requirements Working Group specifies and

identifies interoperability and usability requirements within OMA Working Groups...

• Security – The OMA Security Working Group develops secure

communication protocols between mobile clients and servers at transport and application layers, security and trust servicesprovided by/to mobile clients and servers...


Current Work Items …Current Work Items …

• Architecture– Utilization of IMS Capabilities– Architecture Specification Development

• Data Synchronization– Data Sync Maintenance and Enhancement

• Developers Interest Group– OMA Developers Requirements and Recommendations

• Device Management– Device Management– Web Services IF for Device Management

9


…… Current Work Items …Current Work Items …

• Browser & Content– Ongoing Maintenance of MPG Specifications– OMA Browsing Maintenance– Multimodal and Multi-device Services– Mobile Broadcast– Client-Side Content Screening Framework– OMA Download OTA– Digital Rights Management-Release 2– WCSS Minimum Profile– Mobile Application URI Schemes for Telephony and Service

Linkage– Browser Conformance for Interoperability– SMIL for the Mobile Domain



• Browser & Content (cont)– SVG for the Mobile Domain– Object OMA Minimum Interoperability Profile– Browsing Enhancements– Browsing Maintenance– Client-Side Content Screening Framework– WAP Push Security– Session Initiation Protocol (SIP) Push OTA– Push Specification Maintenance– Standard Transcoding Interface– OMA UAProf Vocabulary Evolution– Interfaces for Common Functions



• Games Services– The Maintenance and Enhancement of the Games Services

Specification

• Location– OMA Location Architecture Overview– Secure User Plane Location (SUPL)

• Mobile Commerce & Charging– M-Commerce– Charging– WISPR to OMA-MCC-2004-0024-charging_work_split_WI– Maintenance of OMA Billing Framework



• Messaging– Minimum Interoperability Specification for MMS– IM Interworking Between Wireless Village and SIP/SIMPLE– Maintenance and Enhancements of IMPS 1.x– Interworking of Messaging Systems– Evolution of MMS v1.2 into MMS v1.3– MMS Maintenance– MMS Extensibility– Mobile E-mail WID– Additional MMS Service Aspects– Multimedia Messaging Services Global Interoperability– SIP/SIMPLE Based IM Service Definitions



• Mobile Web Services– Mobile Web Services-General Analysis– OWSER Network Identity Activity– OWSER Network Identity Release 2

• Presence & Availability– Presence Basic WSI– Group Management– SIMPLE Presence Services

• Push to Talk Over Cellular– Push to Talk Over Cellular


…… Current Work ItemsCurrent Work Items

• Requirements– Identity Management Framework– Execution Policy Enforcement and Management– OMA Service Provider Environment (OSPE) for Improving

Integration, Deployment and Management– Browser Conformance for Interoperability

• Security– Application Layer Security Common Functions– Smart Card Web Server– Mobile Profile of Online Certificate Status Protocol– On-Board Key Generation and Key Enrolment

10


Architecture DocumentsArchitecture Documents

• OMA Service Environment– Approved Version 1.0.1 – 14 Jun 2005


OMA Release ProgramOMA Release Program

• OMA Phase 1: Candidate Enabler Releases– A Candidate Enabler Release is an approved set of open technical

specifications forming an enabler that can be implemented in products and solutions, and which can be tested for interoperability.

• OMA Phase 2: Approved Enabler Releases– An Approved Enabler Release has passed phase 1, and associated

interoperability test cases generated by OMA.• OMA Phase 3: Interoperability Releases

– An OMA Interoperability Release includes multiple enablers that have passed phase 2 with end-to-end interoperability test reports, and information about use cases.


Candidate Enabler Releases …Candidate Enabler Releases …

• OMA Billing Framework– V1.0

• OMA Browsing– V2.3, V2.2, V2.1

• Browser Protocol Stack– V2.1

• OMA Client Provisioning– V1.1

• OMA Data Synchronization– V1.2

• OMA Device Management– V1.2

• OMA Digital Rights Management– V2.0

• OMA DNS– V1.0

• OMA Email Notification– V1.0

• OMA External Functionality Interface– V1.1

• OMA Games Services– V1.0

• IMS in OMA– V1.0

• OMA Mobile Location Protocol– V3.1

• OMA Mobile Location Service– V1.0

• On-Board Key Generation– V1.0

• OMA Online Certificate Status Protocol Mobile Profile

– V1.0MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005 Kimmo Raatikainen 58

…… Candidate Enabler ReleasesCandidate Enabler Releases

• OMA Presence Simple– V1.0

• OMA Push to talk Over Cellular V1.0

• OMA SyncML Common Specification– V1.2

• OMA Standard Transcoding Interface– V1.0

• OMA User Agent Profile– V2.0

• OMA vObject Minimum Interoperability Profile– V1.0

• OMA Wireless Public Key Infrastructure– V1.0

• XDM - OMA XML Document Management Version 1.0

– V1.0


Approved Enabler ReleasesApproved Enabler Releases

• OMA Data Synchronization V1.1.2• OMA Device Management V1.1.2• OMA Digital Rights Management V1.0• OMA Download V1.0 • OMA IMPS V1.2, V1.1• OMA Multimedia Messaging Service V1.2, V1.1• OMA SyncML Common Specification V1.1.2• OMA User Agent Profile V1.1• OMA Web Services V1.0


Requirements Documents …Requirements Documents …• Architecture Requirements

– Approved Version 1.0 21-October 2003• BCAST Requirements

– Candidate Version 1.0 03-February 2005• Charging Requirements

– Candidate Version 1.0 18-November 2004• Client Side Content Screening Framework Requirements

– Candidate Version 1.0 18-November 2004• Device Management Requirements

– Candidate Version 1.0 02-September 2003• Download Over-The-Air Requirements

– Candidate Version 2.0 18-November 2004• Games Services Requirements

– Candidate Version 1.0 23-March 2005

11


…… Requirements Documents …Requirements Documents …• Identity Management Framework Requirements

– Candidate Version 1.0 02-February 2005• In-Game Communications Requirements

– Candidate Version 1.0 16-March 2004• Instant Messaging Requirements

– Candidate Version 1.0 18-November 2004• Location Enabler Release Requirements

– Candidate Version 1.0 18-November 2004• Location Architecture Overview Requirements

– Candidate Version 1.0 18-November 2004• Mobile Location Service Requirements

– Candidate Version 1.0 18-November 2004• Multimodal and Multi-device Services Requirements

– Candidate Version 1.1 13-November 2003


…… Requirements Documents …Requirements Documents …• MMS Requirements

– Candidate Version 1.3 30-September 2004• OMA IMPS Delta Requirements

– Candidate Version 1.3 18-November 2004• OMA Service Provider Environment Requirements

– Candidate Version 1.0 14-June 2005• Policy Evaluation, Enforcement and Management Requirements

– Candidate Version 1.0 12-January 2005• Privacy for Mobile Services Requirements

– Candidate Version 1.0 04-November 2003• Push Security

– Candidate Version 1.0 25-January 2005• Secure User Plain Location Requirements

– Candidate Version 1.0 30-September 2004


…… Requirements DocumentsRequirements Documents

• SIP Based Push Requirements– Candidate Version 1.0 30-January 2005

• STI Requirements– Candidate Version 1.0 14-June 2004

• SVG in the Mobile Domain Requirements– Candidate Version 1.0 12-January 2005

• WAP Proxy-based Redirect Requirements– Candidate Version 1.0 03-June 2003

• Wireless CSS Specification Requirements– Candidate Version 1.1 04-November 2004


World Wide Web ConsortiumWorld Wide Web Consortium

W3C Organization and ActivitiesWeb Services Activity

Compound Document FormatsDevice IndependenceMobile Web Initiative

Semantic Web


W3C in 7 pointsW3C in 7 points

1. Universal Access2. Semantic Web3. Trust4. Interoperability5. Evolvability6. Decentralization7. Cooler Multimedia!

Read W3C … in 7 points Web page!


W3C OrganizationW3C Organization

• work organized into Activities• each Activity has its own structure but typically consists of

– Working Group(s),– Interest Group(s), and– Coordination Group.

• groups generally produce Recommendations and other technical reports as well as sample code.

• Important to every W3C Activity is Quality Assurance (QA).• Activities grouped into four "domains":

– Architecture,– Interaction,– Technology and Society, and– the Web Accessibility Initiative.

12


Architecture Domain …Architecture Domain …

• Document Object Model Activity– DOM Interest Group

• Extensible Markup Language (XML) Activity– XML Coordination Group– XML Core Working Group– XML Plenary Interest Group– XML Query Working Group– XML Schema Interest Group– XML Schema Working Group– XSL Working Group

• Internationalization Activity (I18N)– Internationalization (I18n) Core Working Group– Internationalization (I18n) Guidelines, Education & Outreach Working Group– Internationalization (I18n) Interest Group– Internationalization (I18n) Tag Set Working Group


…… Architecture DomainArchitecture Domain

• URI Activity– URI Interest Group

• Web Services Activity– Semantic Web Services Interest Group– Web Services Addressing Working Group– Web Services Coordination Group– Web Services Choreography Working Group– Web Services Description Working Group– XML Protocol Working Group


Interaction Domain …Interaction Domain …

• Compound Document Formats Activity– Compound Document Formats Working Group

• Device Independence Activity– Device Independence Working Group

• Graphics Activity– SVG Working Group

• HTML Activity– HTML Working Group– Hypertext Coordination Group

• Math Activity– Math Interest Group


…… Interaction DomainInteraction Domain

• Mobile Web Initiative Activity– Mobile Web Best Practice Working Group– MWI Device Description Working Group

• Multimodal Interaction Activity– Multimodal Interaction Working Group

• Style Activity– Cascading Style Sheets (CSS) Working Group

• Synchronized Multimedia Activity– SYMM Working Group– Timed Text Working Group

• Voice Browser Activity– Voice Browser Working Group

• XForms Activity– Xforms Working Group


Quality AssuranceQuality Assurance

• Quality Assurance Activity– QA Interest Group– QA Working Group


Technology and Society DomainTechnology and Society Domain

• Patent Policy Activity– Patents and Standards Interest Group

• Privacy Activity– P3P Coordination Group– P3P Interest Group– P3P Policy and Outreach Working Group– P3P Specification Working Group

• Semantic Web Activity– RDF Data Access Working Group– Semantic Web Interest Group– Semantic Web Best Practices and Deployment Working Group– Semantic Web Coordination Group

• XML Key Management Activity– XML Key Management Working Group

13


Web Accessibility Initiative (WAI)Web Accessibility Initiative (WAI)

• WAI International Program Office – Education and Outreach Working Group– Research and Development Interest Group– WAI Coordination Group– WAI Interest Group

• WAI Technical Activity– Authoring Tool Accessibility Guidelines Working Group– Evaluation and Repair Tools Working Group– Protocols and Formats Working Group– User Agent Accessibility Guidelines Working Group– Web Content Accessibility Guidelines Working Group


Web Services Activity …Web Services Activity …

• Web Services Description Working Group– Working Drafts of the Web Services Description Language

(WSDL) Version 2.0: Primer, Core Language, Adjuncts, SOAP 1.1 Binding.

– final Working Group Note of Describing Media Content of Binary Data in XML

• Web Services Addressing Working Group– 3rd public Working Draft of Web Services Addressing 1.0 -

WSDL Binding– Last Call Working Drafts of Web Services Addressing 1.0 -

Core and Web Services Addressing 1.0 - SOAP Binding


…… Web Services ActivityWeb Services Activity

• XML Protocol Working Group– Recommendations of XML-binary Optimized Packaging,

SOAP Message Transmission Optimization Mechanism and Resource Representation SOAP Header Block.

• The Web Services Choreography Working Group– Last Call Working Draft of Web Services Choreography

Description Language Version 1.0

• Web Services Description Working Group– Last Call Working Draft of Assigning Media Types to Binary

Data in XML


Compound Document FormatsCompound Document Formats

• "Compound document" is the W3C term for a document that combines multiple formats:

– XHTML, SVG, SMIL, Xforms, …

• CDF Working Group will specify the behavior of some format combinations, addressing the needs for an extensible and interoperable Web.

• Recent publication– Compound Document by Reference Use Cases and

Requirements Version 1.0• W3C Working Draft• 4 April 2005


Device Independence ArchitectureDevice Independence Architecture


DI Public Documents …DI Public Documents …

• Dynamic Properties Framework– W3C Last Call Working Draft published in November 2004

• Content Selection (DISelect) for Device Independence 1.0– W3C Last Call Working Draft published in May 2005

• Composite Capability/Preference Profiles (CC/PP): Structure and Vocabularies 1.0– W3C Recommendation published in January 2004

• Glossary of Terms for Device Independence– Latest published version of the Glossary January 2005

• Authoring Challenges for Device Independence– W3C Note published in September 2003

14


…… DI Public DocumentsDI Public Documents

• Device Independence Principles– W3C Note published in September 2003

• Authoring Techniques for Device Independence– W3C Working Group Note published in February

2004• Delivery Context Overview for Device Independence

– W3C Note published in January 2005• Core Presentation Characteristics: Requirements and

Use Cases– W3C Working Draft published in May 2003


DI Internal DocumentsDI Internal Documents

• Dynamic Properties Framework (DPF)– Latest internal version of the DPF working draft

• Language Profile for Device Independence 1.0– Latest internal version of the language profile working draft

• Content Selection (DISelect) for Device Independence 1.0– Latest internal version of the content selection working draft

• Core Presentation Characteristics– Latest internal version of the working draft

• Composite Capability/Preference Profiles (CC/PP): Processing andProtocol Requirements 1.0

– Latest version of a working draft• Device Independence Scenario Repository

– Latest version of the device independence scenarios


DI Work ItemsDI Work Items

• Delivery Context– The Delivery Context category encompasses a number of

work items associated with the information about the device and any user preferences that is used by systems that support device independence.

• Interfaces– The Interface category encompasses the data processing of

an application by modifying the information associated within an interactive session.

• Authoring for Device Independence– The Authoring for Device Independence category

encompasses a number of work items associated with authoring Web sites and applications that support access from a wide range of devices with a variety of delivery contexts.


Mobile Web InitiativeMobile Web Initiative

• launched 11 May 2005 • endeavor to make Web access from a mobile device as

simple, easy, and convenient as Web access from a desktop device.

• Mobile Web Initiative Working Groups– Mobile Web Best Practice (MWBP) Working Group– MWI Device Description Working Group (DDWG)


Mobile Web Best Mobile Web Best PracticePractice WGWG

• Dimensions of analysis associated with best– Valid markup– Content adaptation guidelines– User experience issues

• Definition the meaning of conformance to best practices• Development of mechanisms by which the level of conformance to

best practices can be assessed.• Creation of appropriate materials, for site builders and tools

vendors– Authoring guides– Informative tutorial-type material– Requirements for a validation tool or tools

• Creation and establishment of the “mobileOK” trustmark.


MWI Device Description Working GroupMWI Device Description Working Group

• to foster the provision and access to device descriptions that can be used in support of Web-enabled applications that provide an appropriate user experience on mobile devices.

• There are existing groups and fora that develop descriptive device and browser schemas and vocabularies.

• The scope of the DDWG is not to invent new ones but to make use of these already existing technologies and to package them specifically for the task of authoring and content adaptation.

15


Semantic Web Activity Specifications …Semantic Web Activity Specifications …

• RDF/XML Syntax Specification (Revised)– W3C Recommendation, February 10, 2004

• RDF Vocabulary Description Language 1.0: RDF Schema– W3C Recommendation, February 10, 2004

• RDF Primer– W3C Recommendation, February 10, 2004

• Resource Description Framework (RDF): Concepts and Abstract Syntax– W3C Recommendation, February 10, 2004

• RDF Semantics– W3C Recommendation, February 10, 2004

• RDF Test Cases– W3C Recommendation, February 10, 2004


…… Semantic Web Activity SpecificationsSemantic Web Activity Specifications

• Web Ontology Language (OWL) Use Cases and Requirements– W3C Recommendation, February 10, 2004

• OWL Web Ontology Language Reference– W3C Recommendation, February 10, 2004

• OWL Web Ontology Language Semantics and Abstract Syntax– W3C Recommendation, February 10, 2004

• OWL Web Ontology Language Overview– W3C Recommendation, February 10, 2004

• OWL Web Ontology Language Test Cases– W3C Recommendation, February 10, 2004

• OWL Web Ontology Language Guide– W3C Recommendation, February 10, 2004


RDF Data AccessRDF Data Access

• SPARQL Protocol for RDF– W3C Working Draft 27 May 2005

• SPARQL Variable Binding Results XML Format– Working Draft 27 May 2005

• SPARQL Query Language for RDF– Working Draft 19 April 2005

• RDF Data Access Use Cases and Requirements– Working Draft 25 March 2004.

• .


Java 2 Java 2 PlatformPlatform, , MicroMicro EditionEdition


Java Java TechnologyTechnology

HotSpot CVM KVM Card VM

Java Platform

Java 2Enter-prise

Editon

Java 2Standard

EditonJava 2

Micro Editon

serversdesktops

laptopsset-top-box

PDAcommunicator

smartphone

cellphone

JavaCard


J2ME Software J2ME Software LayerLayer StackStack

Host Operation System

Java Virtual Machine

Configuration

Profiles

16


RelatedRelated SpecificationsSpecifications

• Connected Device Configuration (CDC) and C Virtual Machine (CVM)

• Foundation Profile• Connected Limited Device Configuration (CLDC) and K Virtual

Machine (KVM)• Mobile Information Device Profile (MIDP)• J2ME Wireless Toolkit• Java TV™ Technology• Java Embedded Server™ Software• PersonalJava™ Application Environment

• http://java.sun.com/j2me/docs/


J2ME CLDC TechnologiesJ2ME CLDC Technologies

• Connected Limited Device Configuration (CLDC); JSR 30, JSR 139

• Mobile Information Device Profile (MIDP); JSR 37, JSR 118• Information Module Profile, (IMP); JSR 195• Java Technology for the Wireless Industry, (JTWI); JSR 185• Wireless Messaging API (WMA); JSR 120, JSR 205• Mobile Media API (MMAPI); JSR 135• Location API for J2ME; JSR 179• SIP API for J2ME; JSR 180• Security and Trust Services API for J2ME, (SATSA); JSR-177• Mobile 3D Graphics; JSR-184• J2ME Web Services APIs, (WSA); JSR 172• Bluetooth API (JSR-82, Motorola, Java Partner Site)• J2ME Content Handler API, (CHAPI); JSR 211


J2ME CDC TechnologiesJ2ME CDC Technologies

• Connected Device Configuration (CDC); JSR 36, JSR 218• Foundation Profile, (FP); JSR 46• Personal Basis Profile, (PBP); JSR 129• Personal Profile, (PP); JSR 62• J2ME RMI Optional Package, (RMI OP); JSR 66• JDBC Optional Package for CDC/Foundation Profile API; JSR

169


OtherOther J2ME Technologies …J2ME Technologies …

• Optimized Implementations– CDC HotSpot Implementation

• Java Card Technology– Java Card

• Consumer & Embedded Markets– J2EE Client Provisioning– Java Telephony API– Java Embedded Server Technology– PersonalJava Technology– Java TV API– JavaPhone API– Java Telematics Technology


…… OtherOther J2ME TechnologiesJ2ME Technologies

• Developer and Testing Tools– Sun Java Wireless Toolkit– NetBeans Mobility Pack– Java Device Test Suite

• Developer Programs– Sun Developer Network Mobility Program– Sun Developer Network– Java Verification– Go-To-Market Services


Liberty AllianceLiberty Alliance

This is not necessarily up-to-date since the forum Web site, http://www.projectliberty/org has been

under reconstruction since (at least) mid June 2005

17


LibertyLiberty ArchitectureArchitecture


Liberty SpecificationsLiberty Specifications

• ID-FF 1.2 (FINAL), the Identity Federation Framework • ID-WSF 1.1 (FINAL), the Identity Web Services

Framework • ID-WSF 2.0 (DRAFT), the Identity Web Services

Framework, Draft Release 1 • ID-WSF DST 2.0 (FINAL), the Data Services

Template • ID-SIS, a collection of Identity Services Interface

Specifications


Liberty Alliance IDLiberty Alliance ID--FF 1.2 SpecificationsFF 1.2 Specifications

• Liberty ID-FF Architecture Overview• Liberty ID-FF Bindings and Profiles Specification• Liberty ID-FF Protocols and Schema Specification• Liberty ID-FF Guidelines• Liberty ID-FF 1.2 Static Conformance Requirements,

Version 1.0


Liberty Alliance IDLiberty Alliance ID--WSF 1.1 WSF 1.1 SpecificationsSpecifications

• Liberty ID-WSF Discovery Service Specification• Liberty ID-WSF SOAP Binding Specification• Liberty ID-WSF Security Mechanisms Specification• Liberty ID-WSF Interaction Service Specification• Liberty ID-WSF Client Profiles Specification• Liberty ID-WSF 1.1 Static Conformance Requirements• Liberty ID-WSF Data Services Template Specification• Liberty ID-WSF Authentication Service Specification• Liberty ID-WSF Implementation Guidelines• Liberty ID-WSF Architecture Overview


Liberty Alliance IDLiberty Alliance ID--WSF 2.0 WSF 2.0 Specifications, Draft Release 1Specifications, Draft Release 1

• Liberty ID-WSF Security & Privacy Overview• Liberty ID-WSF Discovery Service Specification• Liberty ID-WSF SOAP Binding Specification• Liberty ID-WSF Security Mechanisms Specification• Liberty ID-WSF Interaction Service Specification • Liberty ID-WSF Data Services Template Specification• Liberty ID-WSF Architecture Overview• Liberty ID-WSF Client Profiles Specification• Liberty ID-WSF Authentication Service Specification• Liberty ID-WSF Draft Guidelines


Liberty Alliance IDLiberty Alliance ID--SIS 1.0 SIS 1.0 SpecificationsSpecifications

• Liberty ID-SIS Personal Profile Service Specification• Liberty ID-SIS Employee Profile Service Specification, Version 1.0• Liberty ID-SIS Contact Book Service Specification• Liberty ID-SIS Geolocation Service Specification• Liberty ID-SIS Presence Service Specification• Liberty ID-SIS Personal Profile Service Implementation Guidelines• Liberty ID-SIS Employee Profile Service Implementation

Guidelines• Liberty ID-SIS Contact Book Service Implementation Guidelines• Liberty ID-SIS Geolocation Service Implementation Guidelines• Liberty ID-SIS Presence Service Implementation Guidelines

18


Liberty Alliance Support DocumentsLiberty Alliance Support Documents

• Liberty Glossary• Liberty Trust Model Guidelines• Liberty Metadata Description and Discovery

Specification• Liberty Authentication Context Specification• Liberty Reverse HTTP Binding for SOAP Specification• Liberty Alliance Privacy and Security Best Practices

Document• Liberty Enumeration Registry Governance


WSWS--I: Web Services I: Web Services Interoperability OrganizationInteroperability Organization


WSWS--I in NutshellI in Nutshell

• An open industry effort chartered to promote Web Services interoperability across platforms, applications and programming languages.

• A standards integrator to help Web services advance in a structured, coherent manner

• Approximately 130 member organizations– 70% vendors, 30% end-user organizations– Strong non-U.S. membership, including very influential Japan

SIG


GoalsGoals

• Achieve Web services interoperability– Integrate specifications– Promote consistent implementations– Provide a visible representation of conformance

• Accelerate Web services deployment– Offer implementation guidance and best practices– Deliver tools and sample applications– Provide a implementer’s forum where developers can

collaborate• Encourage Web services adoption

– Build industry consensus to reduce early adopter risks– Provide a forum for end users to communicate requirements– Raise awareness of customer business requirements


Standard Web Services StackStandard Web Services Stack

Composition/OrchestrationBusiness Process

Orchestration

PortalsManagement

XML, SOAP

XML Schema, WSDL, UDDI, SOAP with Attachments

HTTP, HTTPS,Others

Invocation

Description

Transports

Composable Service

ElementsTransactionalityWS-Security Reliable

Messaging

Endpoint Identification, Publish/SubscribeMessaging

AdditionalCapabilities


Work Done in WSWork Done in WS--I I

Composition/OrchestrationBusiness Process

Orchestration

PortalsManagement

XML, SOAP

XML Schema, WSDL, UDDI, SOAP with Attachments

HTTP, HTTPS, Others

Invocation

Description

Transports

Composable Service

ElementsTransactionalityWS-Security Reliable

Messaging

Endpoint Identification, Publish/SubscribeMessaging

AdditionalCapabilities

19


Deliverables …Deliverables …

• Basic Profile– Basic Profile 1.0 and 1.1

• More than 200 interoperability issues resolved in the Basic Profile 1.0; conventions around messaging, description and discovery

– Simple SOAP Binding Profile 1.0• Derived from Basic Profile requirements related to

serialization of an envelope and its representation in the message

– Sample Applications and Testing Tools for the Basic Profile• Attachments Profile 1.0

– Complements the Basic Profile 1.1 to add support for conveying interoperable, SOAP with Attachments (SwA) with SOAP messages


…… DeliverablesDeliverables

• Basic Security Profile– Security Scenarios

• Document security risks in interoperable Web services, along with potential countermeasures

– Basic Security Profile 1.0• Addresses transport security, SOAP messaging security

and other security considerations for WS-I Profiles• Profiles OASIS’ Web Services Security specification


OASIS: Organization for the OASIS: Organization for the Advancement of Structured Advancement of Structured

Information StandardsInformation Standards


OASIS in NutshellOASIS in Nutshell

• Founded in 1993, OASIS has more than 4,000 participants representing over 600 organizations and individual members in 100 countries.

• not-for-profit, international consortium• drives the development, convergence, and adoption of

e-business standards


OASIS Standards …OASIS Standards …

• Application Vulnerability Description Language (AVDL) v1.0• Common Alerting Protocol v1.0• Darwin Information Typing Architecture (DITA) v1.0• Directory Services Markup Language (DSML) v2.0• DocBook v4.1• ebXML Collaborative Partner Profile Agreement (CPPA) v2• ebXML Message Service Specification v2.0• ebXML Registry Information Model (RIM) v2.0• ebXML Registry Information Model (RIM) v3.0• ebXML Registry Services Specification (RS) v2.0• ebXML Registry Services Specification (RS) v3.0• Extensible Access Control Markup Language (XACML) v1.0• eXtensible Access Control Markup Language TC v2.0 (XACML)


…… OASIS Standards …OASIS Standards …

• OpenDocument Format for Office Applications (OpenDocument) v1.0

• Security Assertion Markup Language (SAML) v1.0• Security Assertion Markup Language (SAML) v1.1• Security Assertion Markup Language (SAML) V2.0• Service Provisioning Markup Lanaguage (SPML) v1.0• Universal Description, Discovery and Integration (UDDI) v2.0• Universal Description, Discovery and Integration (UDDI) v3.0.2• Universal Business Language (UBL) v1.0• Universal Business Language Naming & Design Rules v1.0 (UBL

NDR)• WS-Reliability (WS-R) v1.1• Web Services for Remote Portlets (WSRP) v1.0

20


…… OASIS StandardsOASIS Standards

• Web Services Security v1.0 (WS-Security 2004)• Web Services Security SAML Token Profile v 1.0 and REL Token

Profile v1.0• WSDM Management Using Web Services v1.0 (WSDM-MUWS)• WSDM Management Using Web Services v1.0 (WSDM-MOWS)• XML Common Biometric Format (XCBF) v1.1


OASIS Work AreasOASIS Work Areas

• Web Services/SOA• e-Commerce• Security• Law & Government• Supply Chain• Computing Mgmt• Application Focus• Document-Centric• XML Processing• Conformance/Interop• Industry Domains


OASIS Committees …OASIS Committees …

• Web Services and SOA– Web services allow applications to communicate across

platforms and programming languages using standard protocols based on XML. OASIS members are defining many of the infrastructure standards that enable Web services as well as the implementation standards that are used in specific communities and across industries.

• e-Commerce– OASIS members develop specifications that enable

enterprises of any size, in any geographical location, to conduct business over the Internet.

• Security– OASIS develops security standards needed in e-business and

Web services applications. Members define foundational as well as application-level specifications.


…… OASIS Committees …OASIS Committees …

• Law & Government– OASIS provides a forum to unite international communities of

governments, legal professionals, and suppliers who share the common goal to advance the electronic exchange of information.

• Supply Chain– OASIS members advance a range of efforts to support procurement,

maintenance, and manufacturing functions within the supply chain.• Computing Management

– In a service-oriented architecture, the providers and consumers of services must communicate clearly about their availability and location, and the services themselves must be able to talk to and depend on each other. OASIS members work on many fronts to standardize the reliable management of distributed resources, utility computing and grid systems.


…… OASIS Committees …OASIS Committees …

• Application Focus– Some OASIS Technical Committees focus on developing standards

that meet the needs of a specific market or application area. These teams may concentrate on the unique requirements of one verticalindustry, or on a specific function that can be applied across many industries.

• Document-Centric Applications– From the consortium's roots as SGML Open, OASIS has been

devoted to the device- and media-independent creation and management of documents. Today, OASIS members work on structured information standards for documents that run the gamut from online catalogs to data sheets, from technical manuals to office memoranda, whether output to paper, CD-ROM, wireless devices, the Web, or all of the above.

• XML Processing– Covering the spectrum of XML applications, OASIS technical

committees continue to work on the underlying architecture that facilitates XML processing.


…… OASIS CommitteesOASIS Committees

• Conformance/Interop– To facilitate adoption, OASIS members develop guidelines, best

practices, test suites, and other tools that promote the interoperability and conformance of structured information standards.

• Industry Domains– Not all OASIS Committees develop standards as their primary goal.

OASIS Industry Domains provide forums that unite specific industries or communities of users, governments, vendors, industry groups, and other standards bodies. OASIS Industry Domains evaluate existing standards, articulate requirements, identify gaps, recognize overlaps, publish guidelines, and promote interoperability. Theyprovide input to OASIS TCs (and other organizations) that develop pertinent specifications, and they recommend new efforts where needed.

21


Technical Committees in Web Technical Committees in Web Services/SOA …Services/SOA …

• OASIS Asynchronous Service Access Protocol (ASAP) TC– Enabling the control of asynchronous or long-running Web services

• OASIS Electronic Business Service Oriented Architecture (ebSOA) TC

– Advancing architectural patterns for using Service Oriented Architecture in electronic business

• OASIS Framework for Web Services Implementation (FWSI) TC– Defining methods and functional components for broad, multi-

platform, vendor-neutral cross-industry implementation of Web services

• OASIS Open Building Information Exchange (oBIX) TC– Enabling mechanical and electrical control systems in buildings to

communicate with enterprise applications• OASIS SOA Reference Model TC

– Developing a core reference model to guide and foster the creation of specific, service-oriented architectures


…… Technical Committees in Web Technical Committees in Web Services/SOA …Services/SOA …

• OASIS Translation Web Services TC– Automating the translation and localization process as a Web service

• OASIS UDDI Specification TC– Defining a standard method for enterprises to dynamically discover

and invoke Web services• OASIS Web Services Business Process Execution Language

(WSBPEL) TC– Enabling users to describe business process activities as Web

services and define how they can be connected to accomplish specific tasks

• OASIS Web Services Composite Application Framework (WS-CAF) TC

– Defining an open framework for supporting coordinated and transactional compositions of multiple Web services applications


…… Technical Committees in Web Technical Committees in Web Services/SOA …Services/SOA …

• OASIS Web Services Distributed Management (WSDM) TC– Defining a Web services architecture to manage distributed

resources• OASIS Web Services for Remote Portlets (WSRP) TC

– Standardizing presentation-oriented Web services for use by aggregating intermediaries, such as portals

• OASIS Web Services Notification (WSN) TC– Advancing a pattern-based approach to allow Web services to

disseminate information to one another• OASIS Web Services Reliable Exchange (WS-RX) TC

– Advancing a protocol for reliable message exchange using Web services

• OASIS Web Services Reliable Messaging (WSRM) TC– WS-Reliability 1.1 provides a standard, interoperable way to

guarantee message delivery to applications or Web services


…… Technical Committees in Web Technical Committees in Web Services/SOAServices/SOA

• OASIS Web Services Resource Framework (WSRF) TC– Defining an open framework for modeling and accessing stateful

resources using Web services• OASIS Web Services Security (WSS) TC

– Delivering a technical foundation for implementing security functions such as integrity and confidentiality in messages implementing higher-level Web services applications


UPnP ForumUPnP Forum


UPnP Protocol StackUPnP Protocol Stack

UPnP Device ArchitectureUPnP Device ArchitectureUPnP Device Architecture

UDPUDPUDP

IPIPIP

HTTPU/MUHTTPU/MUHTTPU/MU GENAGENAGENA SSDPSSDPSSDP SOAPSOAPSOAP

HTTPHTTPHTTP

HTTPHTTPHTTP GENAGENAGENA

TCPTCPTCP

UPnP ForumUPnP ForumUPnP Forum

UPnP vendorUPnP vendorUPnP vendor

22


UPnP StandardsUPnP Standards

• Internet Gateway Device (IGD) V1.0• MediaServer V1.0 and MediaRenderer V1.0• Printer Device and Print Basic Service V1.0• Scanner (External Activity V1.0, Feeder V1.0, Scan• V1.0, Scanner V1.0)• Basic Device V1.0• HVAC V1.0• WLAN Access Point Device V1.0• Device Security V1.0 and Security Console V 1.0• Lighting Controls V1.0• Remote UI Client and Server V1.0• Quality of Service V1.0• Digital Security Camera V1.0• Printer Enhanced V1.0


UPnP SpecificationsUPnP Specifications

• Flexible XML Processing Profile (FXPP)• Dynamic Configuration of IPv4 link-local Addresses• Simple Service Discovery Protocol (SSDP)• Multicast and Unicast UDP HTTP Messages• General Event Notification Architecture (GENA)• UUIDs and GUIDs


UPnP Specifications …UPnP Specifications …

• Flexible XML Processing Profile (FXPP)– This document provides an independent reference for the

XML processing profile developed by the WebDAV WG in [RFC2518]. It does this by copying Section 14 and Appendix 4 as well as examples from Appendix 3 of [RFC2518] and editing out any WebDAV specific parts. This document also defines handling of unknown XML attributes.

• Dynamic Configuration of IPv4 link-local Addresses– This document describes a method by which a host may

automatically configure an interface with an IPv4 address in the 169.254/16 range that is valid for link-local communication on that interface. This is especially valuable in environments where no other configuration mechanism is available.


…… UPnP Specifications …UPnP Specifications …

• Simple Service Discovery Protocol (SSDP)– The Simple Service Discovery Protocol (SSDP) provides a

mechanism where by network clients, with little or no static configuration, can discover network services. SSDP accomplishes this by providing for multicast discovery support as well as server based notification and discovery routing.

• Multicast and Unicast UDP HTTP Messages– This document provides rules for encapsulating HTTP messages in

multicast and unicast UDP packets to be sent within a single administrative scope. No provisions are made for guaranteeing delivery beyond re-broadcasting.

• General Event Notification Architecture (GENA)– This document provides for the ability to send and receive

notifications using HTTP over TCP/IP and administratively scopedunreliable multicast UDP. Provisions are made for the use of intermediary arbiters, called subscription arbiters, which handle routing notifications to their intended destination.


…… UPnP SpecificationsUPnP Specifications

• UUIDs and GUIDs– This specification defines the format of UUIDs (Universally

Document Archive Unique IDentifier), also known as GUIDs(Globally Unique IDentifier). A UUID is 128 bits long, and if generated according to the one of the mechanisms in this document, is either guaranteed to be different from all other UUIDs/GUIDs generated until 3400 A.D. or extremely likely to be different (depending on the mechanism chosen). UUIDswere originally used in the Network Computing System and later in the Open Software Foundation's Distributed Computing Environment.


UPnP DocumentsUPnP Documents

• UPnP™ Device Architecture v1.0.1 Draft • UPnP™ Device Architecture• UPnP™ Device Architecture v1.0 Annex A - IPv6 • UPnP™ Vendor's Implementation Guide• UPnP™ DeviceType:V Device Template Version 1.01• UPnP™ ServiceType:V Service Template Version 1.01• UPnP™ Device Checklist Version 1.01• UPnP™ Service Checklist Version 1.01

23


UPnP Documents …UPnP Documents …

• UPnP™ Device Architecture v1.0.1 Draft – The proposed draft UPnP™ Device Architecture specification v1.0.1

consolidates a number of previously separate documents into a single document for consistency and ease of use.

• UPnP™ Device Architecture– The UPnP™ Device Architecture (formerly known as the DCP

Framework) contained herein defines the protocols for communication between controllers, or control points, and devices.

• UPnP™ Device Architecture v1.0 Annex A - IPv6 – UPnP™ Device Architecture v1.0 that specifies how to use UPnP™

v1 over IPv6. • UPnP™ Vendor's Implementation Guide

– This document contains clarifications to v1.0 of the UPnP™ Device Architecture that are likely to be of specific interest to vendors implementing control points and/or devices.


…… UPnP DocumentsUPnP Documents

• UPnP™ DeviceType:V Device Template Version 1.01– Guidelines on how to specify a UPnP™ device.

• UPnP™ ServiceType:V Service Template Version 1.01– Guidelines on how to specify a UPnP™ service.

• UPnP™ Device Checklist Version 1.01– Specified for UPnP™ Forum Working Committee use in

evaluating Template Design Complete (TDC) status for device descriptions.

• UPnP™ Service Checklist Version 1.01– Specified for UPnP™ Forum Working Committee use in

evaluating Template Design Complete (TDC) status for services descriptions.


Digital Living Network AllianceDigital Living Network Alliance

aka Digital Home Working Group


OverviewOverview

• A cross-industry organization of leading consumer electronics, computing industry and mobile device companies.

• Established in June 2003 by 17 companies• A wired and wireless interoperable network where

digital content such as music and videos can be seamlessly shared through personal computers (PCs), consumer electronics (CE) and mobile devices in and beyond the home.

• To enable the cross-industry convergence by establishing a platform of interoperability based on open and established industry standards.


DLNA Interoperability GuidelinesDLNA Interoperability Guidelines

JPEG, LPCM, MPEG2

UPnP AV 1.0

UPnP Device Architecture 1.0

HTTP 1.0/1.1

IPv4 Protocol Suite

Wired: 802.3i, 802.3uWireless: 802.11a/b/g

Media Formats

Device Discovery, Control and Media

Management

Media Transport

Network Stack

Network Connectivity


Next StepsNext Steps

• Upcoming addendums to address optional media formats

– Imaging: GIF, PNG, TIFF– Audio: MP3, WMA, AC-3, AAC, ATRAC3plus– Video: MPEG4 Part 2, MPEG4 Part 10, WMV-9

• Version 1.1 to include smart remote capabilities• Expansion to include mobile and handheld devices

such as cell phones and PDAs

24


OSGiOSGi

aka Open Service Gateway Initiative


OSGiOSGi ArchitectureArchitecture


OSGiOSGi FrameworkFrameworkExecution environment is the specification of the Java environment.

Modules layer defines the class loading policies.

Life Cycle layer adds bundles that can be dynamically installed, started, stopped, updated and uninstalled.

Service Registry provides a cooperation model for bundles that takes the dynamics into account.


OSGiOSGi ServicesServices

• Framework Services– Permission Admin – Package Admin – Start Level

• Protocol Services– Http Service – UPnP Service – Jini Service

• System Services– Log Service – Configuration Admin

Service – Device Access Service – User Admin Service – IO Connector Service– Preferences Service

• Miscellaneous Services– Wire Admin Service– XML Parser Service


BackgroundBackground


Links …Links …

• Kimmo Raatikainen on mobile middleware, http://www.cs.helsinki.fi/u/kraatika/papers.html#mmware

• Wireless World Research Forum, http://www.wireless-world-research.org/.

• Open Mobile Alliance, http://www.openmobilealliance.org/.• Mobile IT Forum, http://www.mitf.org/index_e.html. • W3C, http://www.w3.org/• FIPA, http://www.fipa.org/

– Quality of Service Specification and FIPA Device Ontology Specification

• Sun Microsystems, J2xE, http://java.sun.com/j2ee/, http://java.sun.com/j2se/, http://java.sun.com/j2me/

• Sun Microsystems, Jini Network Technology, http://www.sun.com/software/jini/.

25


…… Links …Links …

• UDDI Version 3, http://www.oasis-open.org/committees/uddi-spec/doc/tcspecs.htm.

• UPnP™ Forum, http://www.upnp.org/.• OMG, Model Driven Architecture, http://www.omg.org/mda/.• Microsoft® .NET Framework, http://www.microsoft.com/net/.• Sun Microsystems, Java Message Service (JMS),

http://java.sun.com/products/jms/.• Sun Microsystems, Sun Java System Message Queue,

http://wwws.sun.com/software/products/message_queue/index.html.

• IBM, WebSphere® MQ, http://www.ibm.com/software/integration/wmq/.

• Microsoft Message Queuing (MSMQ), http://www.microsoft.com/windows2000/technologies/communications/msmq/


…… Links …Links …

• Bea Systems, MessageQ™, http://www.bea.com/• TIBCO, ActiveEnterprise™,

http://www.tibco.com/solutions/products/default.jsp.• ObjectWeb Consortium, JORAM, http://joram.objectweb.org/.• xmlBlaster.org, Open Source for MOM, http://www.xmlblaster.org/.• Siena, http://www.cs.colorado.edu/serl/siena/• Opera Group at Cambridge UK (Cambridge Event Architecture),

http://www.cl.cam.ac.uk/Research/SRG/opera/• Scribe, http://www.research.microsoft.com/~antr/SCRIBE/• Elvin, http://elvin.dstc.edu.au/index.html• Echo, http://www.cc.gatech.edu/systems/projects/ECho/• Gryphon, http://www.research.ibm.com/gryphon/• Fuego Group at HIIT, http://www.hiit.fi/fc/fuego/


…… LinksLinks

• Liberty Alliance, http://www.projectliberty.org/• Digital Living Network Alliance, http://www.dlna.org/• Parlay Group, http://www.parlay.org/• OSGi Alliance, http://www.osgi.org/• Section Middleware in IEEE DS Online,

http://dsonline.computer.org/middleware/index.htm