没有合适的资源?快使用搜索试试~ 我知道了~
NFCForum-TS-SNEP-1_0
资源推荐
资源详情
资源评论
Simple NDEF Exchange Protocol
Technical Specification
Version 1.0
2017-03-14
NFC Forum
TM
[SNEP]
RESTRICTIONS ON USE
This specification is copyright
c
2005-2017 by the NFC Forum, and was made available pursuant to a
license agreement entered into between the recipient (Licensee) and NFC Forum, Inc. (Licensor) and may
be used only by Licensee, and in compliance with the terms of that license agreement (License). If you are
not the Licensee, you may read this Specification, but are not authorized to implement or make any other
use of this specification. However, you may obtain a copy of this Specification and implementation rights at
the following page of Licensor’s website: http://nfc-forum.org/our-work/specifications-and-application-
documents/specifications/ nfc-forum-technical-specifications/ after entering into and agreeing to such
license terms as Licensor is then requiring. On the date that this specification was downloaded by Licensee,
the non-implementation terms of that license were as follows:
1. LICENSE GRANT.
Licensor hereby grants Licensee the right, without charge, to copy (for internal purposes only, except with
respect to the elements listed on Exhibit A) and share this Specification with Licensee’s members,
employees and (to the extent related to Licensees’ use of this Specification) consultants. This license grant
does not include the right to sublicense, modify or create derivative works based upon the Specification,
except for the elements listed in Exhibit A.
2. NO WARRANTIES.
THE SPECIFICATION IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE, ACCURACY, COMPLETENESS AND
NONINFRINGEMENT OF THIRD PARTY RIGHTS. IN NO EVENT SHALL LICENSOR, ITS
MEMBERS OR ITS CONTRIBUTORS BE LIABLE FOR ANY CLAIM, OR ANY DIRECT, SPECIAL,
INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING
FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT,
NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH
THE USE OR PERFORMANCE OF THE SPECIFICATION.
3. THIRD PARTY RIGHTS.
Without limiting the generality of Section 2 above, LICENSOR ASSUMES NO RESPONSIBILITY TO
COMPILE, CONFIRM, UPDATE OR MAKE PUBLIC ANY THIRD PARTY ASSERTIONS OF PATENT
OR OTHER INTELLECTUAL PROPERTY RIGHTS THAT MIGHT NOW OR IN THE FUTURE BE
INFRINGED BY AN IMPLEMENTATION OF THE SPECIFICATION IN ITS CURRENT, OR IN ANY
FUTURE FORM. IF ANY SUCH RIGHTS ARE DESCRIBED ON THE SPECIFICATION, LICENSOR
TAKES NO POSITION AS TO THE VALIDITY OR INVALIDITY OF SUCH ASSERTIONS, OR THAT
ALL SUCH ASSERTIONS THAT HAVE OR MAY BE MADE ARE SO LISTED.
4. TERMINATION OF LICENSE.
In the event of a breach of this Agreement by Licensee or any of its employees or members, Licensor shall
give Licensee written notice and an opportunity to cure. If the breach is not cured within thirty (30) days
after written notice, or if the breach is of a nature that cannot be cured, then Licensor may immediately or
thereafter terminate the licenses granted in this Agreement.
5. MISCELLANEOUS.
All notices required under this Agreement shall be in writing, and shall be deemed effective five days from
deposit in the mails. Notices and correspondence to the NFC Forum address as it appears below. This
Agreement shall be construed and interpreted under the internal laws of the United States and the
Commonwealth of Massachusetts, without giving effect to its principles of conflict of law.
NFC Forum, Inc.
401 Edgewater Place, Suite 600
Wakefield, MA, USA 01880
Contents
Contents
1 Introduction 1
1.1 Applicable Documents or References . . . . . . . . . . . . . . . . . . . . . . . . 1
1.2 Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.3 Name and Logo Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.4 Intellectual Property . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.5 Special Word Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.6 Acronyms and Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.7 Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2 Overview 3
2.1 SNEP Communication Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.2 SNEP Message Transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.3 SNEP Versioning Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3 Protocol Messages 7
3.1 SNEP Request Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.2 SNEP Response Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4 Request Codes 10
4.1 Continue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
4.2 Get . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
4.3 Put . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
4.4 Reject . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
5 Response Codes 12
5.1 Continue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
5.2 Success . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
5.3 Not Found . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
5.4 Excess Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
5.5 Bad Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
5.6 Not Implemented . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
5.7 Unsupported Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
5.8 Reject . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
6 NFC Forum Default SNEP Server 14
6.1 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
A Exhibit A 15
B Revision Histor y 16
Figures
Figure 1 SNEP Communication Model . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Figure 2 Illustration of a Put Request Carrying an NDEF Message . . . . . . . . . . . . 3
Figure 3 SNEP Message Fragmentation . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Figure 4 Fragmented Message Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Figure 5 Example Get Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Figure 6 Example Put Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Simple NDEF Exchange Protocol Page i
Tables
Figure 7 Request Message Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Figure 8 Version Field Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Figure 9 Response Message Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Figure 10 Contents of the Get Request Message . . . . . . . . . . . . . . . . . . . . . . . 10
Figure 11 Contents of the Put Request Message . . . . . . . . . . . . . . . . . . . . . . . 10
Tables
Table 1 Request Field Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Table 2 Response Field Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Table 3 Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Simple NDEF Exchange Protocol Page ii
剩余19页未读,继续阅读
资源评论
wjy_knife
- 粉丝: 0
- 资源: 21
上传资源 快速赚钱
- 我的内容管理 展开
- 我的资源 快来上传第一个资源
- 我的收益 登录查看自己的收益
- 我的积分 登录查看自己的积分
- 我的C币 登录后查看C币余额
- 我的收藏
- 我的下载
- 下载帮助
安全验证
文档复制为VIP权益,开通VIP直接复制
信息提交成功