Presentation Outline
Recent developments in
middleware standardization for
mobile computing
Kimmo Raatikainen
University of Helsinki
Department of Computer Science
• Framework
• OMG
• IETF
• OMA
• W3C
• J2ME
• Liberty
• WS-I
• OASIS
• UPnP
• DLNA
• OSGi
kimmo.raatikainen@cs.helsinki.fi
http://www.cs.helsinki.fi/Kimmo.Raatikainen/
MiNEMA Summer School – Klagenfurt, Austria
© Kimmo Raatikainen
July 15, 2005
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
2
WWRF HighHigh-level Reference Model
Values
Safety
Belonging
Privacy
Framework
Control
Capabilities
Self-Actualisation
Ubiquity
Personalization
Human Capability
Augmentation
Ambient
Awareness
Adaptation
Consistency
App
WWRF Reference Model
App
App
Open APIs
UI
Support
Mobile Middleware
Internet Protocol Suite
Operating System
Computing and Communication
Hard- and Firmware
MiNEMA Summer School – Klagenfurt, Austria
© Kimmo Raatikainen
July 15, 2005
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Application
Open APIs
Generic
Service
Elements
Mobile
Middleware
Internet Protocol Suite
Posix API
Decice
Drivers
Mobile Middleware
Socket API
Internet Protocol Suite
System Call Interface / Posix API
Operating System
Decice Drivers
Computing and Communication hardware
Computing and Communication Hard- and Firmware
Kimmo Raatikainen
Application
Socket API
Decice
Drivers
Operating System
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Application
Open APIs
User Interaction Support
Context Modeling Tools
Trust and Privacy Support
Mobile Data
Management
Configuration
Management
Service
Discovery
Event
Notifications
Environment
Monitoring
UI Support
Execution Environment
4
Implementation View
Mobile Middleware
…
Kimmo Raatikainen
5
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
6
1
Software Artifacts
Key Functionalities
Security – Trust – Privacy
…
Mobility and Efficient Always-On Connectivity
Kimmo Raatikainen
…
Mobility and Efficient Always-On Connectivity
Interoperability
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Discovery
Middleware
Discovery
User Interaction
Security – Trust – Privacy
Internet Protocols
Context Sensitivity and Adaptation
Operating Systems
Context Sensitivity and Adaptation
Interoperability
7
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Standardization Jungle
Kimmo Raatikainen
8
Object Management Group
OMG Specifications
OMG Modeling Specifications
CORBA/IIOP Specifications
CORBA Security Specifications
IDL / Language Mapping Specifications
Specialized CORBA Specifications
OMG Embedded Intelligence Specifications
CORBAservices Specifications
CORBAfacilities Specifications
OMG Domain Specifications
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
9
MiNEMA Summer School – Klagenfurt, Austria
OMG 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
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
July 15, 2005
OMG Modeling Specifications
OMG Modeling and Metadata Specifications
–
© Kimmo Raatikainen
•
•
•
11
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®)
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
12
2
CORBA/IIOP Specifications
•
•
•
•
•
•
•
•
•
•
•
•
•
CORBA Security 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
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
• Authorization Token Layer Acquisition Service (ATLAS)
• Common Secure Interoperability (CSIv2)
• Security Service
• Resource Access Decision Facility
13
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
IDL / Language Mapping
Specifications
•
•
•
•
•
•
•
•
•
•
•
•
Kimmo Raatikainen
• Data Distribution
• Data Parallel Processing
• Dynamic Scheduling
• Lightweight Logging Service
• Minimum CORBA
• Online Upgrades
• Real-Time CORBA Architecture
• Unreliable Multicast
15
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
CORBA Embedded Intelligence
Specifications
•
•
•
•
•
•
•
•
Kimmo Raatikainen
Kimmo Raatikainen
16
CORBAservices Specifications
• Smart Transducers
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
14
Specialized CORBA Specifications
Ada
C
C++
COBOL
CORBA Scripting Language
IDL to Java
Java to IDL
Lisp
PL/1
Python
Smalltalk
XML
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
17
Additional Structuring
Mechanisms for the OTS
Collection Service
Concurrency Service
Enhanced View of Time
Event Service
Externalization Service
Licensing Service
Life Cycle 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
•
Management of Event
Domains
•
•
•
•
•
•
•
•
•
Naming Service
•
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
18
3
CORBAfacilities Specifications
OMG Domain Specifications
•
•
•
•
• Internationalization and Time
• Mobile Agent Facility
•
•
•
•
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
19
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
OMG Domain Specifications
•
•
•
•
•
•
•
•
•
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)
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
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)
Kimmo Raatikainen
20
OMG Domain Specifications
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
Kimmo Raatikainen
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
21
•
•
Telecom Service & Access
Subscription (TSAS)
Telemetry and Telecommand
Data (XTCE)
•
Utility Management Systems
(UMS) Data Access Facility
•
Wireless Access & Terminal
Mobility in CORBA (Telecom
Wireless)
Workflow Management
Facility
•
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
22
IETF Working Areas
• 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)
IETF
IETF Working Areas
IETF Working Groups
SIMPLE WG: SIP for Instant Messaging and
Presence Leveraging Extensions
MiNEMA Summer School – Klagenfurt, Austria
© Kimmo Raatikainen
July 15, 2005
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
24
4
IETF Working Groups …
… IETF Working Groups …
• 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 Discussion
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
25
… IETF Working Groups …
Kimmo Raatikainen
27
26
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
28
… IETF Working Groups
• 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
Kimmo Raatikainen
Kimmo Raatikainen
• 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; Multiprotocol
Label 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
… IETF Working Groups …
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
… IETF Working Groups …
• 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
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
• 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
29
• 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, Middlebox
Communication, 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
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
30
5
SIMPLE WG
RFCs from SIMPLE WG
• Applying the Session Initiation Protocol (SIP, RFC
3261) to Instant Messaging and Presence Services
• Based on SIP-Specific Event Notification (RFC 3265)
RFC 3856: A Presence Event Package for the Session
Initiation Protocol (SIP)
RFC 3857: A Watcher Information Event TemplatePackage 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
– SUBSCRIBE
– NOTIFY
– Usage tailored message formats and semantics
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
31
SIMPLE Work Recently Completed
• 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
33
• 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
Kimmo Raatikainen
SIMPLE Work in Progress (I-Ds)
Ds) …
• Relay Extensions for the Message Sessions Relay Protocol
(MSRP)
• Session Initiation Protocol (SIP) extension for Partial Notification of
Presence Information
… SIMPLE Work in Progress (I-Ds)
Ds)
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
32
• 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 Future
Time Intervals
• The Message Session Relay Protocol
• The Extensible Markup Language (XML) Configuration Access
Protocol (XCAP) – RFC Editor Queue
Kimmo Raatikainen
Kimmo Raatikainen
• CIPID: Contact Information in Presence Information Data Format
• Functional Description of Event Notification Filtering – RFC
Editor Queue
• An Extensible Markup Language (XML) Based Format for
Event Notification Filtering – RFC Editor Queue
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
35
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
34
Open Mobile Alliance
Overview
Technical Plenary Working Groups
WG Descriptions
Current Work Items
OMA Release Program
Candidate Enabler Releases
Approved Enabler Releases
Requirements Documents
OMA Service Environment
MiNEMA Summer School – Klagenfurt, Austria
© Kimmo Raatikainen
July 15, 2005
6
Overview
OMA Principles
• 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).
•
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 seamless
geographic and inter-generational roaming
•
• More than 300 companies:
– whole mobile value chain:
• mobile operators,information technology
companies,wireless vendors and application and content
providers.
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
37
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
End-to-end interoperability
Examples
of end-user
service
scenarios
MMS
Presence
Location
OMA
SyncML
MMS-IOP
Messaging/
imaging
Wireless
Village
LIF
OMA
Mobile
workplace
Terminals
Networks
Apps and
Servers
Content
& Media
OMA
Mobile
Infotainment
Operators
Wireless
Vendors
IT
Content
& Media
OMA
MiNEMA Summer School – Klagenfurt, Austria
© Kimmo Raatikainen
Across
enabling
technologies
Across
standards and
specification
forums
Across
services and
products
Across
companies of
end-to-end
value chain
July 15, 2005
WG Descriptions …
•
•
•
•
•
•
•
•
•
•
Architecture
Browser & Content
Data Synchronization
Developers Interest
Group
Device Management
Games Services
Interoperability
Location
Messaging
Mobile Commerce &
Charging
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
• Mobile Web Service
• Operations & Process
• Presence & Availability
• Push to Talk Over
Cellular
• Release and Planning
Management
• Requirements
• Security
Kimmo Raatikainen
40
… WG Descriptions …
• Architecture
• Developers Interest Group
– 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 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 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 SyncML
technology...
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
38
Technical Plenary Working Groups
Examples
Browsing
Kimmo Raatikainen
Kimmo Raatikainen
41
– 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....
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
42
7
… WG Descriptions …
… WG Descriptions …
• Games Services
• Location
– 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...
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
• 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.
43
… WG Descriptions …
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
44
• Presence & Availability
– 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...
– 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)…
• Operations & Process
• Push to Talk Over Cellular
– 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.
Kimmo Raatikainen
45
– 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…
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
• Release and Planning Management
46
• Architecture
– 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
– Utilization of IMS Capabilities
– Architecture Specification Development
• Data Synchronization
– Data Sync Maintenance and Enhancement
• Developers Interest Group
– The OMA Requirements Working Group specifies and
identifies interoperability and usability requirements within
OMA Working Groups...
– OMA Developers Requirements and Recommendations
• Device Management
• Security
– The OMA Security Working Group develops secure
communication protocols between mobile clients and servers
at transport and application layers, security and trust services
provided by/to mobile clients and servers...
Kimmo Raatikainen
Kimmo Raatikainen
Current Work Items …
… WG Descriptions
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
… WG Descriptions …
• Mobile Web Service
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
– 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...
47
– Device Management
– Web Services IF for Device Management
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
48
8
… Current Work Items …
… Current Work Items …
• Browser & Content
• Browser & Content (cont)
–
–
–
–
–
–
–
–
–
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
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
49
–
–
–
–
–
–
–
–
–
–
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
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
… Current Work Items …
Kimmo Raatikainen
50
… Current Work Items …
• Games Services
• Messaging
– 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
–
–
–
–
–
–
–
–
–
–
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
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
51
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
… Current Work Items …
Kimmo Raatikainen
52
… Current Work Items
• Mobile Web Services
• Requirements
– Mobile Web Services-General Analysis
– OWSER Network Identity Activity
– OWSER Network Identity Release 2
– Identity Management Framework
– Execution Policy Enforcement and Management
– OMA Service Provider Environment (OSPE) for Improving
Integration, Deployment and Management
– Browser Conformance for Interoperability
• Presence & Availability
– Presence Basic WSI
– Group Management
– SIMPLE Presence Services
• Security
– Application Layer Security Common Functions
– Smart Card Web Server
– Mobile Profile of Online Certificate Status Protocol
• Push to Talk Over Cellular
– Push to Talk Over Cellular
– On-Board Key Generation and Key Enrolment
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
53
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
54
9
Architecture Documents
OMA Release Program
•
• OMA Service Environment
OMA Phase 1: Candidate Enabler Releases
–
– Approved Version 1.0.1 – 14 Jun 2005
•
OMA Phase 2: Approved Enabler Releases
–
•
Kimmo Raatikainen
55
•
•
•
•
•
•
•
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
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
•
•
•
•
•
•
57
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
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Approved Enabler Releases
• OMA Data Synchronization
• OMA Device Management
• OMA Digital Rights Management
• OMA Download
• OMA IMPS
• OMA Multimedia Messaging Service
• OMA SyncML Common Specification
• OMA User Agent Profile
• OMA Web Services
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
Kimmo Raatikainen
56
… Candidate Enabler Releases
• 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.0
Kimmo Raatikainen
An OMA Interoperability Release includes multiple enablers that
have passed phase 2 with end-to-end interoperability test reports,
and information about use cases.
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Candidate Enabler Releases …
•
An Approved Enabler Release has passed phase 1, and associated
interoperability test cases generated by OMA.
OMA Phase 3: Interoperability Releases
–
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
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 Wireless Public Key Infrastructure
– V1.0
• XDM - OMA XML Document
Management Version 1.0
– V1.0
Kimmo Raatikainen
58
Requirements Documents …
V1.1.2
V1.1.2
V1.0
V1.0
V1.2, V1.1
V1.2, V1.1
V1.1.2
V1.1
V1.0
•
Architecture Requirements
•
BCAST Requirements
•
Charging Requirements
•
Client Side Content Screening Framework Requirements
–
–
–
–
Candidate Version 1.0
Candidate Version 1.0
Candidate Version 1.0
21-October 2003
03-February 2005
18-November 2004
18-November 2004
•
Device Management Requirements
•
Download Over-The-Air Requirements
•
Games Services Requirements
–
–
–
59
Approved Version 1.0
Candidate Version 1.0
Candidate Version 2.0
Candidate Version 1.0
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
02-September 2003
18-November 2004
23-March 2005
Kimmo Raatikainen
60
10
… Requirements Documents …
… Requirements Documents …
•
Identity Management Framework Requirements
•
MMS Requirements
•
In-Game Communications Requirements
•
OMA IMPS Delta Requirements
•
Instant Messaging Requirements
•
OMA Service Provider Environment Requirements
•
Location Enabler Release Requirements
•
Policy Evaluation, Enforcement and Management Requirements
•
Location Architecture Overview Requirements
•
Privacy for Mobile Services Requirements
–
–
–
–
–
•
Candidate Version 1.0
Candidate Version 1.0
Candidate Version 1.0
Candidate Version 1.0
02-February 2005
–
16-March 2004
–
18-November 2004
–
18-November 2004
–
18-November 2004
–
Mobile Location Service Requirements
–
•
Candidate Version 1.0
Candidate Version 1.0
–
Candidate Version 1.1
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Candidate Version 1.0
Candidate Version 1.0
14-June 2005
12-January 2005
04-November 2003
•
Secure User Plain Location Requirements
–
–
61
Candidate Version 1.0
18-November 2004
Push Security
13-November 2003
Kimmo Raatikainen
Candidate Version 1.3
30-September 2004
•
18-November 2004
Multimodal and Multi-device Services Requirements
Candidate Version 1.3
Candidate Version 1.0
Candidate Version 1.0
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
25-January 2005
30-September 2004
Kimmo Raatikainen
62
… Requirements Documents
•
–
•
Candidate Version 1.0
30-January 2005
STI Requirements
–
Candidate Version 1.0
SVG in the Mobile Domain Requirements
•
WAP Proxy-based Redirect Requirements
–
–
Candidate Version 1.0
Candidate Version 1.0
W3C Organization and Activities
Web Services Activity
Compound Document Formats
Device Independence
Mobile Web Initiative
Semantic Web
14-June 2004
•
•
World Wide Web Consortium
SIP Based Push Requirements
12-January 2005
03-June 2003
Wireless CSS Specification Requirements
–
Candidate Version 1.1
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
04-November 2004
Kimmo Raatikainen
63
MiNEMA Summer School – Klagenfurt, Austria
W3C in 7 points
1.
2.
3.
4.
5.
6.
7.
Read W3C … in 7 points Web page!
Kimmo Raatikainen
July 15, 2005
W3C Organization
Universal Access
Semantic Web
Trust
Interoperability
Evolvability
Decentralization
Cooler Multimedia!
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
© Kimmo Raatikainen
65
•
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.
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
66
11
Architecture Domain …
•
Document Object Model Activity
•
Extensible Markup Language (XML) Activity
–
–
–
–
–
–
–
–
•
… Architecture Domain
•
URI Activity
•
Web Services Activity
DOM Interest Group
–
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)
–
–
–
–
–
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
Internationalization (I18n) Core Working Group
Internationalization (I18n) Guidelines, Education & Outreach Working Group
Internationalization (I18n) Interest Group
Internationalization (I18n) Tag Set Working Group
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
67
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Interaction Domain …
•
Device Independence Activity
•
Graphics Activity
–
–
•
•
•
Device Independence Working Group
HTML Working Group
–
Hypertext Coordination Group
•
Style Activity
•
Synchronized Multimedia Activity
–
–
Math Activity
–
Multimodal Interaction Activity
–
HTML Activity
Quality Assurance
SYMM Working Group
Timed Text Working Group
•
XForms Activity
–
69
Cascading Style Sheets (CSS) Working Group
Voice Browser Activity
–
Kimmo Raatikainen
Multimodal Interaction Working Group
•
Math Interest Group
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Mobile Web Best Practice Working Group
MWI Device Description Working Group
•
–
SVG Working Group
–
68
Mobile Web Initiative Activity
–
–
Compound Document Formats Working Group
•
Kimmo Raatikainen
… Interaction Domain
Compound Document Formats Activity
–
URI Interest Group
Voice Browser Working Group
Xforms Working Group
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
70
Technology and Society Domain
• Patent Policy Activity
• Quality Assurance Activity
– Patents and Standards Interest Group
– QA Interest Group
• Privacy Activity
– QA Working Group
–
–
–
–
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
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
71
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
72
12
Web Accessibility Initiative (WAI)
Web Services Activity …
• WAI International Program Office
–
–
–
–
• Web Services Description Working Group
Education and Outreach Working Group
Research and Development Interest Group
WAI Coordination Group
WAI Interest 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
• WAI Technical Activity
–
–
–
–
–
• Web Services Addressing Working Group
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
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
– 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
73
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
… Web Services Activity
Kimmo Raatikainen
74
Compound Document Formats
• XML Protocol Working Group
• "Compound document" is the W3C term for a document
that combines multiple formats:
– Recommendations of XML-binary Optimized Packaging,
SOAP Message Transmission Optimization Mechanism and
Resource Representation SOAP Header Block.
– 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
• The Web Services Choreography Working Group
– Last Call Working Draft of Web Services Choreography
Description Language Version 1.0
• Web Services Description Working Group
– Compound Document by Reference Use Cases and
Requirements Version 1.0
• W3C Working Draft
– Last Call Working Draft of Assigning Media Types to Binary
Data in XML
• 4 April 2005
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
75
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Device Independence Architecture
Kimmo Raatikainen
76
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
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
77
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
78
13
DI Internal Documents
… DI 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
• 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 and
Protocol Requirements 1.0
– Latest version of a working draft
• Device Independence Scenario Repository
– Latest version of the device independence scenarios
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
79
DI Work Items
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
80
Mobile Web Initiative
• 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.
• 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)
• 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.
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
81
Mobile Web Best Practice WG
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
82
MWI Device Description Working Group
• 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
• to foster the provision and access to device
descriptions that can be used in support of Webenabled 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.
• Creation and establishment of the “mobileOK” trustmark.
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
83
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
84
14
Semantic Web Activity Specifications …
… Semantic Web Activity Specifications
•
•
Web Ontology Language (OWL) Use Cases and Requirements
•
OWL Web Ontology Language Reference
•
OWL Web Ontology Language Semantics and Abstract Syntax
•
OWL Web Ontology Language Overview
•
OWL Web Ontology Language Test Cases
•
OWL Web Ontology Language Guide
RDF/XML Syntax Specification (Revised)
–
W3C Recommendation, February 10, 2004
–
•
RDF Vocabulary Description Language 1.0: RDF Schema
•
RDF Primer
•
Resource Description Framework (RDF): Concepts and Abstract
Syntax
–
–
–
•
–
W3C Recommendation, February 10, 2004
–
W3C Recommendation, February 10, 2004
–
RDF Semantics
–
•
W3C Recommendation, February 10, 2004
–
W3C Recommendation, February 10, 2004
RDF Test Cases
–
–
W3C Recommendation, February 10, 2004
W3C Recommendation, February 10, 2004
W3C Recommendation, February 10, 2004
W3C Recommendation, February 10, 2004
W3C Recommendation, February 10, 2004
W3C Recommendation, February 10, 2004
W3C Recommendation, February 10, 2004
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
85
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
86
RDF Data Access
• SPARQL Protocol for RDF
Java 2 Platform,
Platform, Micro Edition
– 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.
•.
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
87
Java Technology
servers
MiNEMA Summer School – Klagenfurt, Austria
© Kimmo Raatikainen
July 15, 2005
J2ME Software Layer Stack
desktops
laptops
Java 2
Enterprise
Editon
set-top-box
Profiles
cellphone
smartphone
Java 2
Standard
Editon
PDA
communicator
Java 2
Micro Editon
Configuration
JavaCard
Java Virtual Machine
Java Platform
HotSpot
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
CVM
Kimmo Raatikainen
KVM
Card VM
89
Host Operation System
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
90
15
J2ME CLDC Technologies
Related Specifications
•
•
•
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/
•
•
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
•
•
•
•
•
•
•
•
•
•
•
•
•
91
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
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
J2ME 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
Kimmo Raatikainen
92
Other 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
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
93
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
94
… Other J2ME Technologies
• Developer and Testing Tools
– Sun Java Wireless Toolkit
– NetBeans Mobility Pack
– Java Device Test Suite
Liberty Alliance
• Developer Programs
–
–
–
–
Sun Developer Network Mobility Program
Sun Developer Network
Java Verification
Go-To-Market Services
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
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
95
MiNEMA Summer School – Klagenfurt, Austria
© Kimmo Raatikainen
July 15, 2005
16
Liberty Architecture
Liberty 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
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
97
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
• 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
99
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Liberty Alliance IDID-WSF 2.0
Specifications, Draft Release 1
Kimmo Raatikainen
Kimmo Raatikainen
100
Liberty Alliance IDID-SIS 1.0
Specifications
• Liberty ID-SIS Personal Profile Service Specification
• 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
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
98
Liberty Alliance IDID-WSF 1.1
Specifications
Liberty Alliance IDID-FF 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
Kimmo Raatikainen
•
•
•
•
•
•
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
101
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
102
17
Liberty 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
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
103
WSWS-I: Web Services
Interoperability Organization
MiNEMA Summer School – Klagenfurt, Austria
© Kimmo Raatikainen
WSWS-I in Nutshell
July 15, 2005
Goals
• 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
• 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
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
105
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Standard Web Services Stack
Additional
Capabilities
Management
Business
Process
Orchestration
Composable
Service
Elements
Additional
Capabilities
Management
Business
Process
Orchestration
Composition/Orchestration
Reliable
Messaging
106
Work Done in WSWS-I
Portals
WS-Security
Kimmo Raatikainen
Transactionality
Composable
Service
Elements
Portals
Composition/Orchestration
Reliable
Messaging
WS-Security
Transactionality
Messaging
Endpoint Identification, Publish/Subscribe
Messaging
Endpoint Identification, Publish/Subscribe
Description
XML Schema, WSDL, UDDI, SOAP with Attachments
Description
XML Schema, WSDL, UDDI, SOAP with Attachments
Invocation
XML, SOAP
Invocation
XML, SOAP
Transports
HTTP, HTTPS,Others
Transports
HTTP, HTTPS, Others
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
107
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
108
18
Deliverables …
… Deliverables
• Basic Profile
• Basic Security 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
– 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
• Attachments Profile 1.0
– Complements the Basic Profile 1.1 to add support for
conveying interoperable, SOAP with Attachments (SwA) with
SOAP messages
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
109
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
110
OASIS in Nutshell
OASIS: Organization for the
Advancement of Structured
Information Standards
MiNEMA Summer School – Klagenfurt, Austria
© Kimmo Raatikainen
• 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
July 15, 2005
OASIS Standards …
•
•
•
•
•
•
•
•
•
•
•
•
•
Kimmo Raatikainen
Kimmo Raatikainen
112
… 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)
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
• 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
113
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
114
19
… OASIS Standards
OASIS Work Areas
• 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
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
115
OASIS Committees …
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
116
… OASIS Committees …
• Web Services and SOA
• Law & Government
– 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
• Security
– OASIS develops security standards needed in e-business and
Web services applications. Members define foundational as
well as application-level specifications.
Kimmo Raatikainen
– 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
– OASIS members develop specifications that enable
enterprises of any size, in any geographical location, to
conduct business over the Internet.
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
• Web Services/SOA
• e-Commerce
• Security
• Law & Government
• Supply Chain
• Computing Mgmt
• Application Focus
• Document-Centric
• XML Processing
• Conformance/Interop
• Industry Domains
117
… OASIS Committees …
– 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.
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
118
… 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 vertical
industry, or on a specific function that can be applied across many
industries.
• Document-Centric Applications
• XML Processing
– Covering the spectrum of XML applications, OASIS technical
committees continue to work on the underlying architecture that
facilitates XML processing.
Kimmo Raatikainen
– 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
– 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.
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
• Conformance/Interop
119
– 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. They
provide input to OASIS TCs (and other organizations) that develop
pertinent specifications, and they recommend new efforts where
needed.
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
120
20
Technical Committees in Web
Services/SOA …
… Technical Committees in Web
Services/SOA …
• OASIS Asynchronous Service Access Protocol (ASAP) TC
• OASIS Translation Web Services TC
– Enabling the control of asynchronous or long-running Web services
• OASIS Electronic Business Service Oriented Architecture (ebSOA)
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
– Advancing architectural patterns for using Service Oriented
Architecture in electronic business
• OASIS Web Services Business Process Execution Language
(WSBPEL) TC
• OASIS Framework for Web Services Implementation (FWSI) TC
– Defining methods and functional components for broad, multiplatform, vendor-neutral cross-industry implementation of Web
services
– Enabling users to describe business process activities as Web
services and define how they can be connected to accomplish
specific tasks
• OASIS Open Building Information Exchange (oBIX) TC
• OASIS Web Services Composite Application Framework (WSCAF) TC
– Enabling mechanical and electrical control systems in buildings to
communicate with enterprise applications
• OASIS SOA Reference Model TC
– Defining an open framework for supporting coordinated and
transactional compositions of multiple Web services applications
– Developing a core reference model to guide and foster the creation
of specific, service-oriented architectures
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
121
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
… Technical Committees in Web
Services/SOA …
Kimmo Raatikainen
122
… Technical Committees in Web
Services/SOA
• OASIS Web Services Distributed Management (WSDM) TC
• OASIS Web Services Resource Framework (WSRF) TC
– Defining a Web services architecture to manage distributed
resources
– Defining an open framework for modeling and accessing stateful
resources using Web services
• OASIS Web Services for Remote Portlets (WSRP) TC
• OASIS Web Services Security (WSS) TC
– Standardizing presentation-oriented Web services for use by
aggregating intermediaries, such as portals
– Delivering a technical foundation for implementing security functions
such as integrity and confidentiality in messages implementing
higher-level Web services applications
• 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
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
123
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
124
UPnP Protocol Stack
UPnP
UPnPvendor
vendor
UPnP Forum
UPnP
UPnPForum
Forum
UPnP
UPnPDevice
DeviceArchitecture
Architecture
HTTPU/MU
HTTPU/MU GENA
GENA
SSDP
SSDP
SOAP
SOAP
HTTP
HTTP GENA
GENA
HTTP
HTTP
UDP
UDP
TCP
TCP
IP
IP
MiNEMA Summer School – Klagenfurt, Austria
© Kimmo Raatikainen
July 15, 2005
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
126
21
UPnP Standards
•
•
•
•
•
•
•
•
•
•
•
•
•
•
UPnP Specifications
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
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
• 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
127
UPnP Specifications …
• 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.
129
… UPnP Specifications
– 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). UUIDs
were originally used in the Network Computing System and
later in the Open Software Foundation's Distributed
Computing Environment.
Kimmo Raatikainen
– 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 scoped
unreliable multicast UDP. Provisions are made for the use of
intermediary arbiters, called subscription arbiters, which handle
routing notifications to their intended destination.
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
130
UPnP Documents
• UUIDs and GUIDs
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
128
• Simple Service Discovery Protocol (SSDP)
– 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.
Kimmo Raatikainen
Kimmo Raatikainen
… UPnP Specifications …
• Flexible XML Processing Profile (FXPP)
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
131
• 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
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
132
22
UPnP Documents …
… UPnP Documents
• UPnP™ Device Architecture v1.0.1 Draft
• UPnP™ DeviceType:V Device Template Version 1.01
– 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.
– Guidelines on how to specify a UPnP™ service.
• UPnP™ Device Architecture
• UPnP™ Device Checklist Version 1.01
– The UPnP™ Device Architecture (formerly known as the DCP
Framework) contained herein defines the protocols for
communication between controllers, or control points, and devices.
– Specified for UPnP™ Forum Working Committee use in
evaluating Template Design Complete (TDC) status for device
descriptions.
• 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.
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
– Guidelines on how to specify a UPnP™ device.
• UPnP™ ServiceType:V Service Template Version 1.01
Kimmo Raatikainen
133
• UPnP™ Service Checklist Version 1.01
– Specified for UPnP™ Forum Working Committee use in
evaluating Template Design Complete (TDC) status for
services descriptions.
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
134
Overview
Digital Living Network Alliance
aka Digital Home Working Group
MiNEMA Summer School – Klagenfurt, Austria
© Kimmo Raatikainen
July 15, 2005
DLNA Interoperability Guidelines
Media Formats
JPEG, LPCM, MPEG2
Device Discovery,
Control and Media
Management
UPnP AV 1.0
HTTP 1.0/1.1
Network Stack
IPv4 Protocol Suite
Network Connectivity
Wired: 802.3i, 802.3u
Wireless: 802.11a/b/g
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
136
Next 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
UPnP Device
Architecture 1.0
Media Transport
• 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.
• Version 1.1 to include smart remote capabilities
• Expansion to include mobile and handheld devices
such as cell phones and PDAs
137
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
138
23
OSGi Architecture
OSGi
aka Open Service Gateway Initiative
MiNEMA Summer School – Klagenfurt, Austria
© Kimmo Raatikainen
July 15, 2005
OSGi Framework
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.
Kimmo Raatikainen
Kimmo Raatikainen
140
OSGi Services
Execution environment is the
specification of the Java
environment.
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
141
• Framework Services
• System Services
– Permission Admin
– Package Admin
– Start Level
– Log Service
– Configuration Admin
Service
– Device Access Service
– User Admin Service
– IO Connector Service
– Preferences Service
• Protocol Services
– Http Service
– UPnP Service
– Jini Service
• Miscellaneous Services
– Wire Admin Service
– XML Parser Service
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
142
Links …
• Kimmo Raatikainen on mobile middleware,
http://www.cs.helsinki.fi/u/kraatika/papers.html#mmware
• Wireless World Research Forum, http://www.wireless-worldresearch.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/
Background
– 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/.
MiNEMA Summer School – Klagenfurt, Austria
© Kimmo Raatikainen
July 15, 2005
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
144
24
… Links …
… Links …
• UDDI Version 3, http://www.oasis-open.org/committees/uddispec/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.ht
ml.
• IBM, WebSphere® MQ,
http://www.ibm.com/software/integration/wmq/.
• Microsoft Message Queuing (MSMQ),
http://www.microsoft.com/windows2000/technologies/communicati
ons/msmq/
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
145
• 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/
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
146
… Links
• 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
MiNEMA Summer School – Klagenfurt, Austria – July 15, 2005
Kimmo Raatikainen
147
25