Template



Liaison Statement

|TITLE: |OMA OPEN CONNECTION MANAGER API (OPENCMAPI) | PUBLIC CONFIDENTIAL LS[1] |

|DATE: |8TH DECEMBER 2011 |

|TO: |IETF MULTIPLE INTERFACES TERMINAL GROUP (MIF) |

|SOURCE: |CONTENT DELIVERY WORKING GROUP OF OPEN MOBILE ALLIANCE |

|SEND REPLIES TO: |OMA-LIAISON@MAIL. |

|CONTACT(S): |THIERRY BERISOT, OPENCMAPI SWG CHAIR, THIERRY.BERISOT@TELEKOM.DE |

|ATTACHMENTS: |N/A |

1. OVERVIEW

Content Delivery Working Group of Open Mobile Alliance (OMA) is very pleased to inform IETF Multiple Interfaces Terminal Group (MIF) about scope and latest status regarding the Open Connection Manager API (OpenCMAPI) Enabler v1.0 being specified in OMA.

The Open Connection Manager API Work Item was formally agreed by OMA in February 2011.

The agreed Open Connection Manager API Work Item Description (WID_0218) can be obtained from the following URL:



The aim of the OMA Open Connection Manager API enabler v1.0 is to address:

▪ all connectivity and connection management aspects relevant such as:

o Connection/Disconnection

o All relevant elements related to the connection or the device and more specifically all elements necessary and useful to be provided to any UI and user experience or to any application needing information status on the connection.

o Additional services such as SMS, USSD, GPS… when associated to connection management and relevant for the device considered

o Data service especially PUSH service configuration on the device side.

The intention is that this API is:

▪ OS independent

▪ Supporting Multi-Instance (several applications/services can use it in parallel if necessary)

▪ Supporting management of different types of network (e.g. GERAN, UTRAN, CDMA2000, E-UTRAN, WLAN)

▪ Applicable to different types of devices requiring access to mobile internet such as Mobile Broadband devices, Wireless routers, M2M, Smartphones, Tablets, Cloud Devices…

The specification of the Open Connection Manager API is in good progress in OMA and should be technically finalized by end of this year or early 2012.

Note:

The Requirement Document (RD) and the Architecture Document (AD) of Open CM API Release 1.0 can be found respectively from the following links:





2. Requested Action(s)

• OMA CD WG aims at ensuring best coordination with IETF Multiple Interfaces Terminal (MIF) Group on Open Connection Manager API and would be glad to provide any further detailed information that IETF Multiple Interfaces Terminal (MIF) Group would request on this area.

• OMA CD WG would also welcome any information from IETF Multiple Interfaces Terminal (MIF) Group on any Open Connection Manager API related work.

3. Conclusion

• OMA CD WG aims at ensuring best coordination with IETF Multiple Interfaces Terminal (MIF) Group on Open Connection Manager API and would be glad to provide any further detailed information that IETF Multiple Interfaces Terminal (MIF) Group would request on this area.

• OMA CD WG would also welcome any information from IETF Multiple Interfaces Terminal (MIF) Group on any Open Connection Manager API related work.

• Next OMA CD WG meeting is 20th– 24th of February 2012 in Barcelona, Spain.

• OMA CD working group would like to thank IETF for their cooperation.

-----------------------

[1] If the “Confidential LS” box is selected, this liaison statement is intended to be Confidential per agreement by OMA and the addressed organization. Neither side should make this communication available to non-members.

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download