1 / 3

IMS/MMD in OMA

IMS/MMD in OMA. Kevin Holley OMA Req Chair.

avongara-kuron
Download Presentation

IMS/MMD in OMA

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IMS/MMD in OMA Kevin Holley OMA Req Chair

  2. OMA recognises that IMS provides a SIP based architecture defined by 3GPP and 3GPP2 that addresses the needs of mobile operators in terms of session management, security, mobility, QoS and charging. At the time being there are no other globally standardised SIP architectures. • If IMS is leveraged then these service enablers shall use the inherent IMS mechanisms, e.g. security, authentication, charging and QoS • No different behaviour at the applications level depending on the underlying SIP based network (i.e. IMS or other IETF compliant SIP). • Any non-IMS SIP based network is assumed to provide the same functionality as IMS. • OMA completed a Technical report on the usage of 3GPP/3GPP2 IMS in OMA. • A brief summary of the conclusions and recommendations is: Note that the term “IMS” means “IMS/MMD”

  3. Steps being followed in OMA under the IMSinOMA work item • OMA should identify IMS capabilities realising OMA service enablers. • OMA should develop specific Service Enablers that can interface to the IMS, can use IMS capabilities and can exploit the resources of their underlying network infrastructure via the IMS. • OMA should recommend to 3GPP/3GPP2 that enhancements to IMS Services (e.g. Presence and Messaging) beyond Release 6 be undertaken by OMA. • New IMS requirements should be communicated to 3GPP and 3GPP2. • The proposed way forward • OMA Architecture WG to take responsibility of IMS capabilities mapping for OMA enablers • Each OMA WG is responsible to study if their enablers benefit of IMS.

More Related