All the MCOP API definitions are licensed under Apache 2.0

The MCOP SDK has been released with a dual GPLv3/commercial license, in order to allow different commercial possibilities. But any vendor can use the open MCOP API definition and provide an alternative SDK with and MCOP compatible API.

No. All the APIs are licensed under Apache 2.0. (Multinode architecture benefits)


In MCOP we focus on the definition of the open APIs to foster innovation and reduce integration burden in MCPTT compliant UEs. 

All the API definitions are technology neutral, but in order to validate them we have developed a sample SDK and Plugins for Android platform only. So far there are not agreed plans to extend the SDK to other platforms, but we welcome other third parties to provide their own SDK using MCOP APIs.

All the API definitions are technology neutral, so that any other stake holder is able to provide compatible SDK/integration components in any programming languages. Existing MCOP codebase uses both, native C libraries and Java upper layers.

Current MCOP SDK version codebase has only the API > 17 limitation, so no specific version is considered as prerequisite.

3GPP Rel-13 (The MCOP SDK is based on 3GPP Rel-13, but the MCOP API definitions are extended to newer releases.)

During the project we've been continously monitoring the activities in the most relevant Standards Developing Organisations (SDOs) like 3GPP, ETSI, OMA, etc.

MCOP is focused on 3GPP Rel-13 compliance. Therefore the activities in 3GPP on the eMBMS API, CAPIF and RAN5 MCPTT conformance tests have been considered first.

During the project we've been continously monitoring the activities in most relevant Standards Developing Organisations (SDOs). CAPIF has a different scope than the MCOP API , as it focuses on the network northbound API. But we are following the MBMS API activities in 3GPP SA6.

MCOP focuses on a "regular" UE. Although being an open API it could be ported for a Control Room as well. Extensions to the API may be necessary to support certain Control Room functions which are not available to "regular" UEs.

The MCOP SDK provides IP layer connectivity, and the underlying integration API supports Mission Critical grade LTE capabilities. This makes it posible to connect clients via IP. In fact, the MCOP Online Testing Platform provides and on-line testbed for such clients.

Yes. MCPTT is defined as an overlay signalling (and media) application on top of IMS/SIP using the application server paradigm with specific anchors for LTE for MC capabilities. That means that it would work over any IP network, but mission critical capabilities (such as QPP - prioritised bearers MC QCIs 65/69 etc... and multicast capabilities) will get lost, not being able to provide MC service.