Software Component Update in SCOMO-OMA
1 Short Description
Bernard is a device User and very interested in keeping his phone free of viruses.
He is subscribed to “Mobile Security Forces Co.” and this service provider installs always the latest antivirus software upgrades on his phone as soon as they are available. This way Bernard has better protection against malicious mobile device viruses.
2 Actors
o End User
o Device
o Service Provider (Mobile Security Forces Co. in this example)
o Device Management System
2.1 Actor Specific Issues
o End User: The End User wants to have the newest release of antivirus software.
o Service Provider: The Service Provider assigns what software component should be installed by default on a specific Device type. The provider is authorised to define and change the default software on a Device type.
o Device Management System: The Device Management System issues and handles the commands in the service.
2.2 Actor Specific Benefits
o End User: End User has good protection against malicious mobile device viruses.
o Service Provider: The Service Provider is able to deliver the software component updates into the Device.
o Device Management System: The Device Management System is able to manage the software component in the Device.
3 Pre-conditions
• Installed software component on a Device is to have added functionality applied or is to be enhanced for security or performance reasons.
• Device is capable of interfacing with the Device Management system.
• Security constraints imposed by Device Management System and any DM Client are met.
4 Post-conditions
• All software component updates targeted at the device have been delivered and installed.
• Device and all purchased services are fully operational.
5 Normal Flow
1. The Device Management System issues a request to the Device to install software component updates.
2. The Device issues a request to the User for authorization to install updates.
3. Upon confirmation by the User, the Device sends the response to the Device Management System.
4. The Device Management System initiates software component download and update..
5. The Device sends a confirmation back to the Device Management System.
6 Alternative Flow 1
1. The device initiates a session with the Device Management System to request software component update.
2. The Device Management System has detailed information of the software component available in the device, e.g. whether each software component has been installed/removed, what version the software component is, whether updates should be done promptly or later on.
3. The Device Management System will selectively issue a request to the Device that has outdated software component version.
7 Alternative Flow II
1. In the Normal Flow above it turns out that component of antivirus software (that are about to be updated) requires an update of another component (e.g. a special version of Application X).
2. The Device Management System signals to the device that these components must either be both successfully installed or none of them should.
3. The Device respects the signal and treats both updates as if they were one. Unless update of both components succeeds – the operation is canceled and an error status is sent back to the server, indicating the problem.
Software Component Installation in SCOMO-OMA
1 Short Description
Arnold is a device User and very interested in the latest mobile applications.
He is subscribed to “Fun Applications Co.” and this service provider installs always the newest applications on his phone as soon as they are available.
2 Actors
o End User
o Device
o Service Provider (Fun Applications Co. in this example)
o Device Management System
2.1 Actor Specific Issues
o End User: The End User wants to have the newest applications on his device.
o Service Provider: The Service Provider assigns what application software should be installed by default on a specific Device type. The provider is authorised to define and change the default software on a Device type.
o Device ManagementSystem: The Device Management System issues and handles the commands in the service. Note that the Device Management System can reside under different authorities, such as service provider itself or network operator, depending on the infrastructure.
2.2 Actor Specific Benefits
o End User: End User is able to use the latest version of services.
o Device: Device receives the latest software component/s.
o Service Provider: The Service Provider is able to deliver the software components into the Device.
o Device ManagementSystem: The Device Management System is able to manage the application in the Device.
3 Pre-conditions
• Device is capable of interfacing with the Device Management System.
• Security constraints imposed by Device Management System and the Device are met.
4 Post-conditions
• The software component targeted at the device has been delivered and installed.
5 Normal Flow
1. The Service Provider sends via Device Management System a command to the Device to install a software component.
2. The Device issues a request to the User for authorization to install upgrades.
3. Upon confirmation by the User, the Device sends the response to the Device Management System.
4. The Device Management System initiates the software component download, install, and execution.
5. The Device sends a confirmation back to the Device Management System.
6 Alternative Flow
The device initiates a session with the Device Management System to request software component installation.
The device informs the user of the SW characteristics before download and installation.(price, providers, compatibility, QoS, characteristics...)
The device Management system may interact with an external management authority in order to coordinate the procedures with other software components.
Terminology and Conventions of SCOMO-OMA
| Device | In this context, a Device is a voice and/or data terminal that uses a Wireless Bearer for data transfer. Device types may include (but are not limited to): mobile phones (GSM, CDMA, 3GSM, etc.), data-only terminals, PDAs, laptop computers, PCMCIA cards for data communication, unattended data-only Devices (e.g., vending machines), and smart cards if associated with these Devices. If within a particular context an associated smart card should not be regarded as part of a Device this is marked explicitly. |
| Device Reporting | The process that a Device sends specific information to a Device Management System in the network. This can occur as a response to a query (pull) or it can occur autonomously in response to a state change in the Device (push). The information that is sent may either be parameters, configuration capabilities of the Device, or data that has been collected, stored, and assembled for later processing (e.g., performance metrics). |
| Device Management | Management of the Device configuration and other managed objects of Devices from the point of view of the various Management Authorities. Device Management includes: - Setting initial configuration information in Devices - Subsequent updates of persistent information in Devices - Retrieval of management information from Devices Processing events and alarms generated by Devices |
| Device Management System | A background system capable to interact with a (set of) Device(s) for the purpose of Device Management. |
| Enterprise | A business with deployment and Management Authority for WLAN Bearers, Local Wired Bearers, computers, Devices, software, and employees. |
| Management Authority | An entity that has the right to perform a specific Device Management function on a Device or manipulate a given data element or parameter. For example, the Network Operator, handset manufacturer, enterprise, or Device owner may be the authority or share authority for managing the Device. One Management Authority may own all Device resources or may share or delegate all or parts of these with/to other Management Authorities |
| Network Operator | An entity that is licensed and allocated frequency to operate a public mobile wireless telecommunications network for the purpose of providing publicly available commercial services. |
| Service Provider | An entity that provides and administers a service to a Subscriber and/or User. The Network Operator is often a Service Provider. |
| Subscriber | A Subscriber is an entity (e.g. a user) that is engaged in a Subscription with a service provider. [OMADICT] |
| Software Component Management Object | A management tree object defined for software components which will be used for delivering and managing software components within client device. |
| Software Component Activation | The process which results in services or resources a software component embodies to be made accessible to other entities or resources (including the end-user). |
| Software Component Deactivation | The process which results in services or resources a software component embodies to be made inaccessible to other entities or resources (including the end-user). . |
| SCOMO Operations | Download, Install, Update, Remove, Activate and Deactivate operations which may be invoked on a Software Component MO as well as inventory queries. |
| User | An entity which uses services. Example: a person using a device as a portable telephone.[OMADICT] |