Find JSRs
Submit this Search


Ad Banner
 
 
 
 

Summary  |  Proposal  |  Detail (Summary & Proposal)
JSRs: Java Specification Requests
JSR 257: Contactless Communication API

Stage Access Start Finish
Maintenance Release 2 Download page 31 Oct, 2011  
Maintenance Draft Review 2 Download page 15 Mar, 2011 14 Apr, 2011
Maintenance Release Download page 10 Jul, 2009  
Maintenance Draft Review Download page 16 Mar, 2009 20 Apr, 2009
Final Release Download page 17 Oct, 2006  
Final Approval Ballot View results 21 Aug, 2006 05 Sep, 2006
Proposed Final Draft Download page 07 Apr, 2006  
Public Review Ballot View results 15 Nov, 2005 21 Nov, 2005
Public Review Download page 18 Oct, 2005 21 Nov, 2005
Early Draft Review Download page 13 May, 2005 12 Jun, 2005
Expert Group Formation   09 Nov, 2004 08 Mar, 2005
JSR Review Ballot View results 26 Oct, 2004 08 Nov, 2004
Status: Maintenance
JCP version in use: 2.7
Java Specification Participation Agreement version in use: 2.0


Description:
This specification will define J2ME Optional Packages for contactless communication, one package for bi-directional communication and the other for accessing read-only information.

Please direct comments on this JSR to the Spec Lead(s)
Team

Specification Leads
  Kimmo Loytana North Sixty-One Ltd
Star Spec Lead Jaana Majakangas Nokia Corporation
Expert Group
  Esmertec AG FeliCa Networks, Inc Gemalto
  LG Electronics Inc. Matsushita Electric Industrial Co., Ltd. Motorola
  NEC Corporation Nokia Corporation North Sixty-One Ltd
  Orange France SA Philips Electronics UK Ltd Samsung Electronics Corporation
  Semacode Corporation Sun Microsystems, Inc.

Updates to the Original JSR

The following information has been updated from the original proposal.

2012.08.22: The following section has been updated.

2.18 Please provide a description of the business terms for the Specification, RI and TCK that will apply when this JSR is final.

TCK:
- Available free of charge to qualified not-for-profit organizations and individuals in accordance with the JSPA, solely for developing and testing their own implementations and not allowing to test any third party or commercial for-profit implementations.
- The TCK is licensed, in line with the MSA licensing principles, with a flat fee of USD 50 000 for a license term of 3 years. This includes all maintenance updates and releases, if any. The license will be worldwide, non-exclusive and will be granted on an AS IS basis without any warranties or indemnities given and with the exclusion of all indirect and consequential damages. Major new releases, from new follower JSR, are subject to a separate license fee.
- The license grant will be for a term of not less than three (3) years.
- A license allowing licensees to test implementations on behalf of third parties as a free or for-fee commercial service under certain conditions shall be available. This right may result in a higher license fee.

2012.08.21: North Sixty-One has become the co-Maintenance Lead.

Maintenance Lead: Kimmo Löytänä

E-Mail Address: jsr257@northsixtyone.com

Telephone Number: -

Fax Number: -

2009.07.09:

2.18 Please provide a description of the business terms for the Specification, RI and TCK that will apply when this JSR is final.


Specification license for implementation
RI license
Tck license


Original Java Specification Request (JSR)

Identification | Request | Contributions

Section 1. Identification

Submitting Member: Nokia Corporation

Name of Contact Person: Kimmo Loytana

E-Mail Address: kimmo.loytana@nokia.com

Telephone Number: +358 40 527 6423

Fax Number: +358 7180 70530


Specification Lead: Jaana Majakangas

E-Mail Address: jaana.majakangas@nokia.com

Telephone Number: +358 40 539 7497

Fax Number: +358 7180 70530


Initial Expert Group Membership:

Supporting this JSR:

Nokia Corporation
Philips Electronics
Siemens AG
Sony Ericsson Mobile Communications AB
Symbian Ltd



Section 2: Request

2.1 Please describe the proposed Specification:

Contactless communication can be used to provide a small amount of information to applications from some other medium, for example, links to some content or identifiers for services etc. Contactless communication can be based on e.g. Radio Frequency Identification (RFID), Near Field Communication (NFC) or bar codes.

NFC mode can be used for exchanging small amounts of information between two NFC enabled devices. RFID readers and tags do not need a visual contact but only close proximity between the reader terminal device and the tag. Some RFID tags can be also written and the data contained in them updated. Bar codes can be printed e.g. in adverts in magazines and newspapers, or on product packaging or for use at points of sale.

The API is targeted for resource-constrained devices such as mobile phones or consumer electronic devices and it must be memory-efficient.

This JSR will define two optional packages in a way that it is possible for a device to implement either read-only contactless communication (e.g. bar code reading) or bi-directional contactless communication (e.g. NFC) or both of them.

2.2 What is the target Java platform? (i.e., desktop, server, personal, embedded, card, etc.)

JavaTM 2, Micro Edition.

The minimum requirement is the J2ME Connected, Limited Device Configuration (CLDC).

This Optional Package should be usable with any J2ME Profile based on the minimum Configuration as well as Profiles based on the Connected Device Configuration (CDC).

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.

The JSR is targeting to JavaTM 2, Micro Edition only. There is no relationship with the other Java platform editions.

2.4 Should this JSR be voted on by both Executive Committees?

No. The Executive Committee with responsibility for the J2ME specifications is required to vote on this JSR.

2.5 What need of the Java community will be addressed by the proposed specification?

This specification will define a standardized way to utilize contactless communication in J2ME applications.

2.6 Why isn't this need met by existing specifications?

There are no standardized APIs for contactless communication based for example on RFID, NFC or bar codes in Java applications currently.

General Connection Framework in MIDP2.0/CLDC1.1 provides a common framework for I/O operations can connect to external resources. This JSR may be based on using the Generic Connection Framework.

2.7 Please give a short description of the underlying technology or technologies:

RFID is a technology that allows inexpensive tags to contain a small amount of data. These tags can be read and optionally also written by devices using radio frequency communication in close proximity of the tag. Since it is using RF communication, the device does not need a visual contact with the tag. The tag contains a microchip and an antenna. These may be for example laminated inside self-adhesive labels that may be used in similar places as barcodes, but do not need to be visible.

Near Field Communication (NFC) mode can be used for contactless communication between two devices. NFC is a new standard for wireless connectivity between devices in close proximity.

Bar codes are a very common way to encode a small amount of data in a machine-readable way in printed material. Bar codes can be read using several different kinds of optical reader technologies. One possibility in mobile phones is to utilize the camera that is now integrated in many mobile phones.

2.8 Is there a proposed package name for the API Specification? (i.e., javapi.something, org.something, etc.)

javax.microedition.contactless

2.9 Does the proposed specification have any dependencies on specific operating systems, CPUs, or I/O devices that you know of?

Devices must support some form of contactless communication.

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.

Early Draft Review: Q1/2005
Public Review Draft: Q2/2005
Final Specification: Q4/2005

2.14 Please describe the anticipated working model for the Expert Group working on developing this specification.

We expect to have a geographically distributed expert group, so e-mail is the primary communication method. Teleconferences and face-to-face meetings may be organized as needed and as appropriate.

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 provide status updates on the JSR Community Update Page on a monthly basis. These will include at least updates to the anticipated schedule, status of the specification and possible open issues where input is requested from the wider community.

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.

The RI and TCK will be delivered as standalone packages.

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).

Not applicable

2.18 Please provide a description of the business terms for the Specification, RI and TCK that will apply when this JSR is final.

These terms only represent the initial commercial terms to be used and remain subject to the execution of final legal agreements covering the subject matter hereof to be determined by Nokia at its sole discretion.

We will license to all interested parties. Independent implementations will be allowed - TCK and RI will be licensed separately.

For the TCK we will charge a single one-time fee of max US $50,000 and an annual maintenance fee, max US $20,000 for a term of four years. The TCK will include both the binary environment and the source code for the test suite. The maintenance fee covers limited basic support, first level TCK appeals process, bug fixes when available and updates, which are due to changes in the Specification. Major new releases (esp. from new follower JSR) might be subject to an additional single one-time fee.

Using the TCK for testing of implementations on behalf of third parties will be allowed, though, be subject to a higher fee, which is capped at the sum of license fees due in accordance with license fees as described above in this section, if the third parties would have directly licensed the TCK from Nokia.

For the RI in source code form we will charge a one-time access fee, and an annual maintenance fee. Maintenance covers bug fixes, updates and new releases necessary due to specification changes, and when made generally available by the specification lead.

The binary license is free of charge.





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.

Near Field Communication Forum ( http://www.nfc-forum.org/)

3.2 Explanation of how these items might be used as a starting point for the work.

NFC Forum specifies protocols that can be used with this JSR.