1. OMA Overview & OMA IMPS and OMA POC
ITRI, CCL, K100
廖彥彰

2. 大綱
OMA overview
OMA IMPS
OMA PoC

3. OMA Overview

4. OMA 開放行動聯盟(Open Mobile Alliance；OMA)成立於2002年6月，是由行動通訊產業所發起、成立的組織
最初是由Open Mobile Architecture發起成立該聯盟，並由WAP Forum制定聯盟架構
整合了
Location Interoperability Forum (LIF)
SyncML Initiative
MMS-IOP (Multimedia Messaging Service Interoperability Process)
Wireless Village
Mobile Gaming Interoperability (MGIF)
Mobile Wireless Internet Forum (MWIF)

5. What is OMA ?
為了創造一個行動服務(Mobile Service)規格訂定的中心，提升行動服務的互通性(Interoperability)
No matter what device or operating system you have, no matter what service you have, no matter what carrier you use, you can communicate and exchange information

6. OMA’s Goals 依據市場與客戶的需求，制定高品質及且得到回響的標準與規格。 成立互通性測試中心，包含多種不同標準的互通測試。
保持與其他國際標準組織(如：IETF, 3GPP, 3GPP2, W3C, JCP)的合作關係，以確保標準的互通性。
提供OMA成員最大的利益
Mobile Operators
Wireless Vendors
Content Providers
Information Technology Companies

7. OMA Organization
Messaging
PoC

8. OMA Release Program
Phase 1 : 候選發行(Candidate Enabler Release)，根據市場需求，由OMA會員所訂定且審查過的標準
Phase 2 : 驗證發行(Approved Enabler Release)，經過測試，證實所提供的產品或服務能彼此互通的標準
Phase 3 : 互通性發行(Interoperability Release)，二個以上OMA所訂定的標準通過第二階段的互通性測試，並且這些標準間能夠完成互通性測試

9. OMA Enabler Status Phase 1 : OMA Billing framework version 1.1
OMA Browsing version 2.1
OMA Client provisioning version 1.1
OMA Digital Rights Management (DRM) version 1.0
OMA Domain Name Server (DNS) version 1.0
OMA Download version 1.0
OMA Notification version 1.0
OMA IMPS version 1.2
OMA Multimedia Messaging (MMS) version 1.1
OMA Multimedia Messaging (MMS) version 1.2
OMA User Agent Profile version 1.1
OMA Device Management version 1.1.2
OMA Games Services version 1.0

10. OMA Enabler Status Phase 2 : OMA IMPS version 1.1
OMA Data Synchronization version 1.1.2
OMA SyncML Common Enablers version 1.1.2

11. OMA Enabler Status
Phase 3 :
None

12. OSA Service Architecture

13. OSA Architecture

14. OSA VS OMA OSA : OMA : Middleware Architecture Public API
Mobile Service
Interoperability between services
OMA services can use OSA to implement

15. OMA IMPS

16. OMA IMPS History Version 1.0 : Wireless Village Feb. 2002
1st Interop：Jul. 2002, 170 supporters
2nd Interop：September 2002, 193 supporters
Version 1.1：OMA, Nov. 2002
3rd Interop (OMA 1st Interop): Dec. 2002
22 client products
20 server products
Version 1.2 : Feb. 2003
IMPS CSP Interop : June 2003, ~300 supporters
9 client products
8 server products
4th : November 2003 (USA) : Version 1.1
5th : March 2004 (USA) : Version 1.1, Version 1.2
IMPS Version 1.2 : Phase 1  Phase 2

17. IMPS Architecture

18. IMPS in iB3G MSN Server ICQ Server SIMPLE Server HLR/HSS CSCF GMLC
MSN Client
ICQ Client
Internet
SIMPLE Client
MSN Server
ICQ Server
SIMPLE Server
Cellular Network
HLR/HSS
CSCF
GMLC
Network Agent
SMCNP
MSC
SSP
SGSN
GGSN
IMPS Server
IMPS Server
SSP
WLAN
WLAN
IMPS Client
Cellular
IMPS Client

19. WV Architecture Component
WV Server : Contain more than one Service Ekements
Service Access Point (SAP)
Authentication and Authorization
Service discovery
Service relay
User profile management
Instant Messaging Service Element
Presence Service Element
Group Service Element
Content Service Element
WV Embedded Client :
Need capability negotiation with WV Server
WV CLI Client :
Use command line interface

20. IMPS Server Architecture
WV Server2
CLI Client
IM Service
Group Service
CSP
CLP
IMPS Client
Service Access Point
SSP
SMCNP
WV Server1
IMPS Client
Service Access Point
CSP
Mobile
Core Network
IM Service
Presence Service
Group Service
Content Service

21. IMPS Protocol Stack Security IPSec, WTLS Session HTTP, SIP, WSP/WTP
SMS
Transport
TCP, UDP, WDP
IP over 2.5G/3G Wireless
Mobile IP
Application
CSP / SSP / CLP

22. Protocol Stack of CSP Symmetric : SMS Asymmetric Data Channel :
CIR Channel :
TCP/IP
UDP/IP
HTTP
Application : CSP
Session
HTTP, HTTPS
Session
WSP
Transport : TCP
Transport : WAP

23. Logical Model of CSP Symmetric Asymmetric Symmetric Channel
WV Client
WV Server
Asymmetric
CIR Channel
WV Client
WV Server
Data Channel
---- Request
Response ---
CIR : Communication Initiation Request

24. CSP Transport call flow
Server
Data Channel
Server
CIR Channel
Client
Client
Server
CIR Message
POST-req
POST-req (PollRequest)
POST-resp
POST-resp (NotifyReq)
POST-req (Status)
POST-resp (empty)

25. CSP Session Management (1)
The WV session is a framework in which the WV services are provided to the WV client
Lifetime of a session
A session is established when
The client logs in
A session is terminated when
The client logs out
SAP decides to disconnet the session
However, session may be re-established in some cases
Ex: Re-authentication
The WV session is transport-independent
The client device may turned on/off and the session may still be continued

26. CSP Session Management (2)
Session-ID
Used to identify a session
Assigned by the server at login phase
Session Cookie
Assigned by the client at login phase
Used by server to trigger communications (CIR)
Version
The client and the server MUST use the same version of the WV protocol
Authentication
Done at login phase
Valid throughout the session h

27. CSP Transaction Management (1)
A WV transaction is a basic communication mechanism between a WV client and a WV SAP
Consists of a request and a response primitive
Exceptions: disconnect, 4 way login
A transaction may originate from either WV client or WV SAP
The initiative entity will allocate a transaction ID
The response of a request message should be received within 20 seconds
Resend

28. CSP Transaction Management (2)…
General Transaction
Keep Alive
Disconnect (S  C)
Get Service Provider

29. Login Transaction 2-Way Login 4-Way Login
C  S : (Login-Request) ClientID + Password + SessionCookie
S  C : (Login-Response) SessionID
4-Way Login
C  S : (Login-Request) ClientID + (DigestSchema +) + SessionCookie
S  C : (Login-Response) Noce + DigestSchema
C  S : (Login-Request) DigestBytes

30. Session and Transaction
CSP Session
CSP Transaction
User Login
Capability Negotiation
Message Notification
Log out
Data Channel
CIR Channel
WSP/HTTP(S) Request
WSP/HTTP(S) Reply

31. CSP format XML base Special namespace
<WV-CSP-Message xmlns = “
<Session>
<SessionDescriptor>
<SessionType>Inband</SessionType>
</SessionDescriptor>
</Session>
<Transaction>
…..
</Transaction>
</WV-CSP-Message>

32. OMA 變革 IM MMSG IMPS PAG (Presence, availability and group management )
Working Group
Sub Working Group
Work Item
2003
2004
IMPS
PAG
(Presence, availability and
group management  )
WV IMPS IM
MWG
(Messaging working group)
SIP/SIMPLE IM
MMSG

33. 參考文獻
[1] “WV-040 System Architecture Model Version 1.2”, Open Mobile Alliance, Version 2003-Feb-21, OMA-IMPS-WV-Arch-v1_ C
[2] “Enabler Release Definition for IMPS Version 1.2”, Open Mobile Alliance, Version 2003-Feb-21, OMA-ERELD-IMPS-v1_ C
[3]  “WV-041 Features and Functions Version 1.2”, Open Mobile Alliance, Version 2003-Feb-21, OMA-IMPS-WV-Features_Functions-v1_ C
[4]  “WV-042 Client-Server Protocol Session and Transactions Version 1.2”, Open Mobile Alliance, Version 2003-Feb-21, OMA-IMPS-WV-CSP-v1_ C
[5] “WV-043 Client-Server Protocol DTD and Examples Version 1.2”, Open Mobile Alliance, Version 2003-Feb-21, OMA-IMPS-WV-CSP_DTD-v1_ C
[6] “WV-044 Client-Server Protocol Transport Bindings Version 1.2”, Open Mobile Alliance, Version 2003-Feb-21, OMA-IMPS-WV-CSP_Transport-v1_ C

34. 參考文獻
[7] “WV-045 Client-Server Protocol Data Types Version 1.2”, Open Mobile Alliance, Version 2003-Feb-21, OMA-IMPS-WV-CSP_DataTypes-v1_ C
[8] “WV-047 Client-Server Protocol Binary Definition and Examples Version 1.2”, Open Mobile Alliance, Version 2003-Feb-21, OMA-IMPS-WV-CSP_WBXML-v1_ C
[9] “WV-048 Client-Server Protocol Static Conformance Requirement Version 1.2”, Open Mobile Alliance, Version 2003-Feb-21, OMA-IMPS-WV-CSP_SCR-v1_ C
[10] “WV-049 Presence Attributes Version 1.2”, Open Mobile Alliance, Version 2003-Feb-21, OMA-IMPS-WV-PA-v1_ C
[11] “WV-050 Presence Attribute DTD and Examples Version 1.2”, Open Mobile Alliance, Version 2003-Feb-21, OMA-IMPS-WV-PA_DTD-v1_ C
[12] “WV-051 Command Line Protocol Version 1.2”, Open Mobile Alliance, Version 2003-Feb-21, OMA-IMPS-WV-CLP-v1_ C
[13] “WV-052 SSP - Server-Server Protocol Semantics Document Version 1.2”, Open Mobile Alliance, Version 2003-Feb-21, OMA-IMPS-WV-SSP-v1_ C

35. 備註
IMPS Presence Attribute

36. OMA PoC

37. OMA PoC History
PoC (Push-to-talk over cellular) first announce by Ericsson, Motorola, Siemens and Nokia at Aug
OMA form the PoC working group at Nov
Integrate with 3GPP, IETF
OMA IMPS - draft version

38. What is Push-to-talk ?
Mobile phone user can only push one button to talk with another person or a group.

39. Example of PoC

40. PoC Architecture

41. Functional entities (1/2)
PoC Client
Mobile terminals used to access PoC service
PoC Server
PoC session handling and SIP session handling
Floor control functionality and media distribution
Policy handling(e.g. access control, availability status)
Provides participants information and charging reports
QoS
Group and List Management Server (GLMS)
List management operations (e.g. create, modify, retrieve and delete contact, group and access lists)
Provides storage for contact, group and access lists

42. Functional entities (2/2)
SIP/IP Core
Includes a number of SIP proxies and SIP registrars
Routes SIP signaling
Discovery and address resolution services
SIP compression
Authentication and authorization of PoC Client
Maintain registration state
Provides charging reports
Presence Server
Provides availability information

43. Interface Interface Is : PoC Client – SIP/IP Core
Interface If : SIP/IP Core – PoC Server
SIP
Interface It : PoC Client - PoC Server
Interface Itn : PoC Server - PoC Server
RTP and XCON
Interface Im : PoC Client - GLMS
Interface Ik : PoC Server – GLMS
Interface Ipl : presence Server – GLMS
Interface Ips : SIP/IP Core – Presence Server
SIP/SIMPLE base

44. GLMS - Contact List Address book
A contact list contains the IDs of other PoC users or PoC group
A user may have one or more contact lists
Attribute :
ID : In SIP URI format or TEL
Display name
Default contact list (Yes or No)
Type (User or Group)
all entries within a contact list MUST have the same type
List of user or group ID

45. GLMS - Group List Group ID : In SIP URI format Display name
Membership (open/restricted)
Open – any user may join the group
Restricted – only member can join
Group reject list (membership = open)
Group member
Max number of participant
Talk type (chat/instant)

46. GLMS – Access List There are two and only two access lists per user
A user reject list
A user accept list
When “Do-not-disturb” is on, the access lists are not checked.

47. Access List

48. Floor Control
The method that UEs to have and to release the resource in the PoC server
Floor Idle : PoC Server notify UEs the resource is free
Floor Request : UE request media resource to PoC Server
Floor Grant : PoC Server notify agreed to the request UE
Floor Deny : PoC Server notify rejected to the request UE
Floor Taken : PoC Server notify all other UEs, a resource has been granted to another UE.
Floor Release : UE notify PoC Server to release the resource
Floor Revoke :PoC Server cancel the resource from UE

49. PoC Client Floor Control state transition diagram
U: UE (PoC client); S: Send; R: Receive

50. PoC Server Floor Control state transition diagram

51. Types of Group Talk (1) Ad-hoc PoC group session
PoC user invites selected users to establish an ad-hoc PoC group session
When a group discussion is need without planning it in advance
The ad-hoc group id is temporary

52. Types of Group Talk (2) Pre-arranged PoC group session
Group is pre-defined, and have member list
One of the members invite all other group member
Each invited member can either accept or reject
During an ongoing instant group talk session
Users in the session can invite other members
Member users not in the session can join the session

53. Types of Group Talk (3)
Chat PoC group session : Join a active PoC session
Open group : any user can join the group
Restricted group :
Creator can manage the member list
Only member can join the chat
A user joins the group buy select the group from group list
A joined user can invite another member to join the group

54. POC Session Setup POC Client (inviter) POC Server POC Client (invitee)
On-demand session
Pre-established session
Auto answer
Manual answer
Confirmed indication
Unconfirmed indication

55. Types of PoC Session On-demand session Pre-established session
PoC Client Send INVITE to SIP/IP Core when it want to initialize a POC session
Pre-established session
PoC Client establish SIP session when it power on
PoC Client send REFER to SIP/IP Core when it want to initialize a POC session

56. Types of Answer Mode
Auto answer
Manual answer

57. Types of PoC Indication
Confirmed indication
The right-to-speak indication is given to the inviting PoC Client when one of the invited PoC Client has accepted the invitation
Unconfirmed indication
The right-to-speak indication is given to the inviting PoC Client when the invited PoC Client is registered and uses automatic answer

58. Call Flow 1: Pre-establish session

59. Call Flow 2: Confirmed indication using on-demand session (Caller)

60. Call Flow 2: Confirmed indication using on-demand session (Callee)

61. Call Flow 3: Unconfirmed indication using on-demand session (Caller)

62. Call Flow 3: UnConfirmed indication using on-demand session (Callee)

63. Call Flow 4: Unconfirmed indication using pre-established session (Caller)

64. Call Flow 4: Unconfirmed indication using pre-established session (Callee)

65. Q&A