...
5.1 Over-the-air updates
5.1.1 OMA DM
The OMA DM protocol, is used by leading Mobile Network Operators (MNOs) like AT&T, NTT DOCOMO, SoftBank, Sprint, T-Mobile US and Verizon Wireless. The MNOs use the OMA DM protocol to manage mobile devices on their network. The following are some of the use cases MNOs have deployed:
- Provisioning: Initial device configuration (aka Bootstrap) and enabling and disabling device features
- Device Configuration: Modifications of various settings and parameters of the device
- Software Upgrades: Enable Over-the-air (OTA) software update including Firmware Update (FUMO) and system and applications components (SCOMO)
- Fault Management: Allow querying the device status and report device errors
The OMA DM protocol is designed with interoperability and security in mind:
- Interoperability is achieved by the work of the OMA Interoperability (IOP) work group. The IOP work group specify and maintain the required processes, policies and test programs in addition to running regular test-fests where different vendors can attend and test their client and server software.
- Security is important because devices are exposed to software attacks. The OMA DM protocol was designed with security features like device authentication and challenges.
The OMA DM protocol allow manufacturers and service providers to continuously increase the usefulness and value of connected devices throughout their entire lifecycle. They are able to optimize device performance, deliver unique insights, facilitate rollout of innovative services and contribute to increased ARPU.
In recent years, with the introduction of the connected car, the term “mobile device” is extended to include the “large mobile device” of the automotive industry. Many car OEMs select to use the OMA DM protocol to manage the configuration and software of the cars they are building. This enables car manufacturers to capitalize on the full business potential of connected cars by enhancing driver experience with rapid deployment of value-added in-car services, and minimizing costs through improved efficiency and a reduction in recalls.
5.2 Device APIs
needs to be made generic - not OMA-centric Through OMA enablers focused on device APIs, we can enable automotive (Auto) systems to offer API services to apps running in app environments provided by the Auto system. Such API services can enable apps to access vehicle information/services or other connected devices. These OMA enabler APIs are based upon the Generic Open Terminal API (GotAPI) \[GotAPI\] enabler framework described in section 6.2.
...