 
Use of JCP site is subject to the
JCP Terms of Use and the
Oracle Privacy Policy
 |
|
 JSRs: Java Specification Requests
JSR 259: Ad Hoc Networking API
JCP version in use: 2.6 Java Specification Participation Agreement version in use: 2.0 Description: The purpose of this JSR is to define an API that enables communication between mobile devices in a peer-to-peer ad-hoc network environment. Please direct comments on this JSR to the Spec Lead(s) Team
This JSR has been Dormant The following information has been updated from the original JSR: 2009.07.06: The Maintenance Lead changed to Sun Microsystems. Specification Lead: Volker Bauche E-Mail Address: volker.bauche@sun.com Telephone Number: +49 89 46008 1049 Fax Number: - 2007.04.11: Jim Lee is the current temporarily acting Spec Lead.Updates to the Original Java Specification Request (JSR) 2005.10.18: The Spec Lead has changed from Siemens AG to BenQ Corporation. 2004.11.04: The title of the JSR was changed from "Ad-hoc API" to "Ad Hoc Networking API". Original Java Specification Request (JSR)
Identification |
Request |
Contributions
Section 1. Identification Submitting Member: Siemens AG Name of Contact Person: Jean-Yves Bitterlich E-Mail Address: Jean-Yves.Bitterlich@siemens.com Telephone Number: +49 89 722 58563 Fax Number: +49 89 722 35087 Specification Lead: Jean-Yves Bitterlich E-Mail Address: Jean-Yves.Bitterlich@siemens.com Telephone Number: +49 89 722 58563 Fax Number: +49 89 722 35087 Initial Expert Group Membership: Siemens Supporting this JSR: Siemens Section 2: Request
2.1 Please describe the proposed Specification:The purpose of this JSR is to define an API that enables communication between mobile devices in a bearer agnostic peer-to-peer ad-hoc network environment.
- Service registration - Service availability alert - Service and service capability inquiry - Remote service consumption 2.2 What is the target Java platform? (i.e., desktop, server, personal, embedded, card, etc.)The target Java platform is the J2ME. This optional package will run on both configurations CLDC and CDC and corresponding profiles (e.g. MIDP, IMP, FP?). 2.3 The Executive Committees would like to ensure JSR submitters think about how their proposed technology relates to all of the Java platform editions. Please provide details here for which platform editions are being targeted by this JSR, and how this JSR has considered the relationship with the other platform editions.This API targets J2ME. J2SE does not address this topic. 2.4 Should this JSR be voted on by both Executive Committees?No 2.5 What need of the Java community will be addressed by the proposed specification?Currently J2ME is lacking a Java API that allows a java application in a mobile device to dynamically join an ad-hoc network. This API will allow 3rd party developers to build P2P java applications for ad-hoc networks (but also for conventional networks) and improve the user experience (multi-part applications, multi-user gaming, ad-hoc service consumption, etc?). 2.6 Why isn't this need met by existing specifications?There is no API yet in any configuration, profile or optional package that supports access to ad-hoc environments for mobile devices, and enables discovery, publishing and service consumption.BR>
JSR 82 does not support for the BT PAN profile and therefore does not allow ad-hoc IP communication as proposed by this API. JSR 82 is moreover bearer specific. 2.7 Please give a short description of the underlying technology or technologies:There are a few mature technologies that support ad-hoc communication between mobile devices, and enable discovery, publishing, and service consumption, as for example UPnP, ZeroConf, JXTA, etc. This API enables access for the Java Application to the corresponding implementation, as listed above. 2.8 Is there a proposed package name for the API Specification? (i.e., javapi.something, org.something, etc.)Package: javax.microedition.* 2.9 Does the proposed specification have any dependencies on specific operating systems, CPUs, or I/O devices that you know of?These APIs will depend on the presence of a network I/O device. 2.10 Are there any security issues that cannot be addressed by the current security model?No 2.11 Are there any internationalization or localization issues?No 2.12 Are there any existing specifications that might be rendered obsolete, deprecated, or in need of revision as a result of this work?No 2.13 Please describe the anticipated schedule for the development of this specification.Expert Group Formation: Q4 2004 2.14 Please describe the anticipated working model for the Expert Group working on developing this specification.It is anticipated that a combination of email discussion, feedback on regular drafts, conference calls and face-to-face meetings will work well. 2.15 It is important to the success of the community and each JSR that the work of the Expert Group be handled in a manner which provides the community and the public with insight into the work the Expert Group is doing, and the decisions that the Expert Group has made. The Executive Committees would like to ensure Spec Leads understand the value of this transparency and ask that each JSR have an operating plan in place for how their JSR will address the involvement of the community and the public. Please provide your plan here, and refer to the Spec Lead Guide for a more detailed description and a set of example questions you may wish to answer in your plan.The expert group will remain open for new nominations until Early Draft Review (EDR). Interim drafts of the specification will be made available on the JSR community page. The schedule will be defined by the expert group. Additionally the observer alias will be used, to inform interested members of the community about progress and open issues in this JSR. The users@jsp-spec-public mailing list will be open to the public to discuss issues related to the JSP specification. 2.16 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.Due to the optional package character of this request, RI and TCK will be delivered as standalone products. 2.17 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).N/A 2.18 Please provide a description of the business terms for the Specification, RI and TCK that will apply when this JSR is final.We will license to all interested parties. 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.
- JSR 36: Connected Device Configuration (CDC) - JSR 37: Mobile Information Device Profile 1.0 (MIDP) - JSR 118: Mobile Information Device Profile 2.0 (MIDP) - JSR 195: Information Module Profile (IMP) - JSR 139: Connected, Limited Device Configuration Specification (CLDC 1.1) - JSR 228: Information Module Profile Next Generation (IMP-NG) - UPnP Forum: http://www.upnp.org - ZeroConf, http://www.zeroconf.org - JXTA, http://www.jxta.org 3.2 Explanation of how these items might be used as a starting point for the work.Due to the optional package character of the request, considerable cross-references towards configurations and profiles the package is based on are expected. |
|||||||||||||||||||||||||||||||||||||||
