JSRs: Java Specification Requests
JSR 233: J2EE Mobile Device Management and Monitoring Specification
Reason: Withdrawn at the request of the Specification Lead.
JCP version in use: 2.7
Java Specification Participation Agreement version in use: 2.0
This JSR defines an extension of the J2EE platform for the purposes of remotely monitoring and managing the software on mobile devices.
Please direct comments on this JSR to the Spec Lead(s)
This JSR has been Withdrawn
The following information has been updated from the original JSR:
2.11 Please describe the anticipated schedule for the development of this specification.The following dates are preliminary:
Expert Group Formation: November 2003
Original Java Specification Request (JSR)
Section 1. Identification
Submitting Member: Sun Microsystems, Inc.
Name of Contact Person: Andre Kruetzfeldt
E-Mail Address: firstname.lastname@example.org
Telephone Number: +1 650 352 4754
Fax Number: +1 650 352 4754
Specification Lead: Andre Kruetzfeldt, Christopher David
E-Mail Address: email@example.com, firstname.lastname@example.org
Telephone Number: +1 650 352 4754, +46 8 631 1161
Fax Number: +1 650 352 4754
Initial Expert Group Membership:
Supporting this JSR:
Section 2: Request
2.1 Please describe the proposed Specification:
There is considerable interest in the Java Community in writing software applications that remotely manage the configuration and software residing on mobile devices. Currently, part of such a software application deals with the system integration task of building a particular set of business policies into such a system, and part of such a software application deals with the systems level details of how the management and monitoring can be supported for a heterogeneous class of mobile devices.
The proposed specification will define an extension to the J2EE platform to support management functionality with in J2ME based mobile devices; and will not depend on specific configurations or profiles of J2ME.
* Initiate reprovisioning of the platform software and libraries on devices on the wireless network, including provisioning new software and
* libraries, upgrading existing software and libraries to fix bug to get the new version, remove software and libraries.
* Initiate dynamic reconfiguration of the software and libraries, modifying default settings and configuration parameters and supporting security policies,
* initiate reprovisioning of new application level software onto the device, and remove, upgrade, version manage it.
* Provide a view of the software and application stack configuration of the remote device, including a dependency resolution mechanism.
* Monitor application usage on mobile devices,
for mobile devices supporting standard protocols for such purposes.
This functionality can be made accessible to various participants, e.g. Mobile Equipment OEM, Carrier, or even End User, under specific access roles.
This extension will not store the individual software components, but will contain the needed rule sets that will lead to the above described behaviour. To support the storage and delivery of the individual components, systems like provisioning servers will receive a notification from this extension and trigger the needed steps. Both access roles and management rules will than allow the enablement of such software applications on mobile devices.
The same kind of notification will be used to communicate monitoring information to network based management software applications.
2.2 What is the target Java platform? (i.e., desktop, server, personal, embedded, card, etc.)
2.3 What need of the Java community will be addressed by the proposed specification?
This proposal addresses a number of needs of different verticals in the Java Community. Enterprises who are in the process of enabling their workforces to use mobile devices to access enterprise services, such as sales and field force automation applications, wish to streamline management of the standard software configurations and application sets on those mobile devices in a remote, centralized and automated manner. They may wish to repurpose mobile devices for different employees by remotely reconfiguring the software and application stack thereon.
Carriers wish to be able to provide comprehensive customer support for software services running on fleets of mobile devices, to provide fault diagnostic support and a streamlined way to correct software defects on the mobile device remotely on behalf of the consumer.
2.4 Why isn't this need met by existing specifications?
The related technologies that this proposal will consider are listed in section 3. Currently, there is no support in the J2EE platform for remotely managing and monitoring software and applications residing on mobile devices.
JSR 160 defines a remote client API for interacting with such agents, this does only cover Java based management systems that comply with JSR 3 ? Java(TM) Management Extensions Specification -. It will be an option for the server side management APIs. Mobile devices do not support JSR 3 or JSR 160; and OMA DM is the method of choice. JSR 232 ? Mobile Operational Management - defines a management environment for J2ME Connected Device Configuration, but it does not define the server infrastructure.
JSR 124 defines a J2EE extension to enable user initiated discovery and delivery of software applications to a variety of devices. A reuse of matching APIs out of JSR 124 will reduce the complexity of this specification.
2.5 Please give a short description of the underlying technology or technologies:
We expect that this specification will leverage adapters for existing network protocols for management such as:
* OMA OTA
* OMA DS
* OMA DM
* OMA UAProf
* J2ME MIDP OTA
* J2ME WMA
and may work with other standards bodies to enhance or create new protocols.
2.6 Is there a proposed package name for the API Specification? (i.e., javapi.something, org.something, etc.)
2.7 Does the proposed specification have any dependencies on specific operating systems, CPUs, or I/O devices that you know of?
2.8 Are there any security issues that cannot be addressed by the current security model?
TBD by the expert group.
2.9 Are there any internationalization or localization issues?
2.10 Are there any existing specifications that might be rendered obsolete, deprecated, or in need of revision as a result of this work?
2.11 Please describe the anticipated schedule for the development of this specification.NOTE that this section has been updated from this original request.
The following dates are preliminary:
Expert Group Formation: November 2003
2.12 Please describe the anticipated working model for the Expert Group working on developing this specification.
The primary means of communication will be email, with conference calls and face-to-face meetings scheduled as needed.
2.13 Please describe how the RI and TCK will de delivered, i.e. as part of a profile or platform edition, or stand-alone, or both. Include version information for the profile or platform in your answer.
2.14 Please state the rationale if previous versions are available stand-alone and you are now proposing in 2.13 to only deliver RI and TCK as part of a profile or platform edition (See sections 1.1.5 and 1.1.6 of the JCP 2 document).
2.15 Please provide a description of the business terms for the Specification, RI and TCK that will apply when this JSR is final.
In line with the Java Community Process version 2.5, the following is a summary of Sun's anticipated principal license terms and conditions for the JSR, J2EE Mobile Device Management and Monitoring Specification.
Sun Microsystems, Inc., will make this JSR's TCK and RI available for licensing separately:
Sun will make this JSR's TCK available on a stand-alone basis at no charge, without support or any trademark license rights, to qualified not-for-profit entities (including not-for-profit academic institutions) and qualified individuals engaged in efforts to create compatible implementations of the Specification. All other use is deemed commercial. Sun will make this JSR's TCK available for commercial use for an annual license and support fee.
Sun will make this JSR's binary RI available for evaluation purposes through a free download, without support. Sun will also make this JSR's RI source available for commercial use for an additional licensing and support fee.
Section 3: Contributions
3.1 Please list any existing documents, specifications, or implementations that describe the technology. Please include links to the documents if they are publicly available.
JavaTM Management Extensions (JMX) Remote API 1.0
J2EE Client Provisioning Specification
JavaTM Management Extensions (JMXTM) Specification
WBEM Services Specification
Wireless Messaging API
Data Sync API
Event Tracking API for J2ME
Open Mobile Alliance
3.2 Explanation of how these items might be used as a starting point for the work.
Section 4: Additional Information (Optional)
4.1 This section contains any additional information that the submitting Member wishes to include in the JSR.