View
3
Download
0
Category
Preview:
Citation preview
Dr. Fidel Liberal
Coordinator of the Mission Critical Open Platform (MCOP)
Mission Critical Open PlatformAddressing the MC apps challenge
“Before standardised
MCPTT”
• Single provider or point of contact
• e2e turnkey solution but …�Monolithic all-in-one apps
�Vendor lock-in, limited
innovation…
Towards..
Heterogenous
multi-vendor
Standard MCPTT
EUTRAN eMBMS EPC
IMS/SIP CORE
MVNO
Multi-vendor
MCPTT
APP
Developer
MCPTT
SERVICE
PROVIDER
MCPTT ASs
EMBMS MIDDLEWARE
OEM INTEGRATION
APPVENDOR
MCPTT CLIENT
GENERAL PURPOSE OS
LTE CHIPSET
CHIPSETMANUFACTURER
UE
VENDOR
OSVENDOR
PSOs
VendorsNo SIMaccess
No APNaccessProprietaryProprietary
Operating
System
Operating
System
Connection ManagerConnection Manager
Public APIPublic API
eMBMSeMBMS
Vendor specific Radio AccessVendor specific Radio Access
Radio Layer Access Radio Layer Access
SIMoperations
eMBMSoperations
ProSE
ProSEoperations
Monolithic
MCPTT Application
Monolithic
MCPTT Application
No SIMaccess
No APNaccessProprietaryProprietary
Proprietary Proprietary OS vendor
Proprietary
OS vendor
OAM(OTA)
Proprietary
OS vendor
defined
OAM(OTA)
Hardened
Platform
LTE
IMSI AUTH Different OAM &OTA procedures
Monolithic proprietary apps
Proprietary APIs to MC capabilities
Dependence on internal OS APIs� OEM only
No access to user level apps to SIM/others
How easy is developing
MCPTT apps
4/18
Multivendor environments
EMBMS MIDDLEWARE
LTE CHIPSETCHIPSET
MANUFACTURER
UE
VENDOR
1
OSVENDOR
GENERAL PURPOSE OS
LTE CHIPSET LTE CHIPSET
UE
VENDOR
n
GENERAL PURPOSE OS2
EMBMS MIDDLEWARE Other UE capabilities
GENERAL PURPOSE OSGENERAL PURPOSE OS1
MCPTT CLIENT A
UE
VENDOR
2
MCPTT CLIENT B MCPTT CLIENT C
No SIMaccess
No APNaccess
Proprietary Proprietary Proprietary
No SIMaccess
UE Integration burdenProject A
MCPTT CLIENT A
UE
VENDOR
1
UE
VENDOR
2
Project B
MCPTT CLIENT B
UE
VENDOR
3
MCPTT CLIENT C
Project C
MCPTT CLIENT D
UE
VENDOR
n
MCPTT CLIENT C
EMBMS MIDDLEWARE
LTE CHIPSETCHIPSET
MANUFACTURER
OSVENDOR
LTE CHIPSET LTE CHIPSET <10s
10s
<10s
10s
EMBMS MIDDLEWARE Other UE capabilities
MCPTT CLIENT A MCPTT CLIENT B MCPTT CLIENT C
• Hundreds of combinations
UE
VENDOR
1
UE
VENDOR
n
UE
VENDOR
2
No SIMaccess
No APNaccess
Proprietary Proprietary Proprietary
No SIMaccess
10s
UE Integration burden
GENERAL PURPOSE OS GENERAL PURPOSE OS2GENERAL PURPOSE OSGENERAL PURPOSE OS1
• Never-ending expensive effort
UE Integration burden
X
• Unbalanced relationship
UE Integration burden
MC UE Telco OS Chipset M(V)NO
Relative size of MC and commercial industries
EUTRAN eMBMS EPC
IMS/SIP CORE
MVNO
Multi-vendor
MCPTT
APP
Developer
MCPTT
SERVICE
PROVIDER
MCPTT ASs
EMBMS MIDDLEWARE
OEM INTEGRATION
APPVENDOR
MCPTT CLIENT
GENERAL PURPOSE OS
LTE CHIPSET
CHIPSETMANUFACTURER
UE
VENDOR
OSVENDOR
PSOs
VendorsNo SIMaccess
No APNaccessProprietaryProprietary
UE Integration burden
• Cross (re)certification
Service
tes ng &
cer fica on
Responder prac oner acceptance
Con nuous
tes ng of live
systems
Applica on
tes ng and
cer fica on
Terminal tes ng and
cer fica on
Protocol tes ng &
cer fica on
Wireless tes ng &
cer fica on
UE Integration burden• Hundreds of combinations (different release cycles)• Never-ending expensive effort
• Unbalanced relationship• Cross (re)certification
Lose-Lose for MC industry and users
How can A Mission Critical Open Platform help?
• Reduce integration burden
• Open APIs in the UE
• Foster innovation
• Easy tools:hide technology complexity
• Focus on each stakeholder’s needs
Proprietary
The MCOP approach
Operating
System
Operating
System
Connection ManagerConnection Manager
Public APIPublic API
eMBMSeMBMS
Vendor specific Radio AccessVendor specific Radio Access
Radio Layer Access Radio Layer Access
SIMoperations
eMBMSoperations
ProSE
ProSEoperations
Monolithic
MCPTT Application
Monolithic
MCPTT Application
No SIMaccess
No APNaccessProprietaryProprietary
Proprieta
ry
Proprieta
ry
OS vendor
Proprieta
ry
OS vendor
OAM(OTA)
Proprietary
OS vendor
defined
OAM(OTA)
LTE
IMSI AUTH Different OAM &OTA procedures
Operating
System
Operating
System
Connection ManagerConnection Manager
Public APIPublic API
eMBMSeMBMS
Vendor specific Radio AccessVendor specific Radio Access
Radio Layer Access Radio Layer Access
eMBMSoperations
ProSE
ProSEoperations
Hardened
Platform
MCOP Open Source SDKMCOP Open Source SDK
Demo APPDemo APP 3rd Party App 3rd Party App
MCOP Unified Open Application API
OAM(OTA)
OAM(OTA)
MC
OP
OA
M/O
TA
OP
EN
AC
CE
SS
Clear single interface
MCOP Integration API
The MCOP approach• How to build a successful MCOP?• Option 1) Start pushing APIs in standardization bodies
• Time scale
• Sustained and joint effort (several meetings)
• Option 2) Bring major vendors
• Conflicting interests
• Immature market: final business model still not clear
• “We believe it’s important but… I need to check with the managerial”
• … the MCOP Open approach
• ref:“Field of Dreams” (1989) imdb
“If you build it, they will come”
The MCOP approach
• Foster • MCPTT Open Source SDK + clean APIs
• As as possible• Technology neutral + flexible architecture
• Multiple deployment models• From Private LTE to Hybrid
• Build and make available open testbeds• Online
• MC-grade (live) e2e
• MC-Grade• Multicast (eMBMS)
• High priority bearers (MC-QCIs)
• Deployment/configuration/OAM
https://demo.mcopenplatform.org
“If you build it, they will come”
How it works• Technology neutral API definition OPEN, for ANY platform
• De-coupling/isolation for different business models
• Every component seamlessly provided by a different vendor
• Licensing and release cycles
• No constraint
• Access to prioritized resources
• OEM only if needed
• Mutual authentication framework
• Alignment with Android and under-standardization APIs
• Future-proof
«IRemoteService AIDL» «IRemoteService AIDL»
«Binder framework»
MCPTT Application MCOP SDK Plugin i,j,k…
Stub.Proxy Stub Stub.Proxy
IBinder
Kernel binder driver
Stub
OAM Certificate Whitelist
provisioning
Current status• Comprehensive 3GPP MCPTT Rel14 support
• 4th ETSI MCX Plugtest
• Multivendor
• Different GUIs
• Different SDKs
• Different eMBMS/Connectivity/Configuration
• Quick prototyping: Tailored app
• Head-up-display for firefighters
• Quick prototyping
GUI
SDK
plugins
GUI
SDK
XP8plugins
XP8plugins
APP
What’s next!!!!• Hand’s on trial
• Evolution / convergence of MCOP APIs
• MCData/MCVideo APIs COMING SOON
• Creating MCOP API steering committee
• Supporter program
Dr. Fidel Liberal
Coordinator of the Mission Critical Open Platform (MCOP)
Mission Critical Open PlatformAddressing the MC apps challenge
Recommended