首页 > > > SAP_SPEC_V11(SIM_Access_Profile).pdf

SAP_SPEC_V11(SIM_Access_Profile).pdf

SAP_SPEC_V11(SIM_Access_Profile…

上传者: wusi524888 2014-03-30 评分1 评论0 下载0 收藏10 阅读量855 暂无简介 简介 举报

简介:本文档为《SAP_SPEC_V11(SIM_Access_Profile)pdf》,可适用于电子通讯领域,主题内容包含BLUETOOTHDOCDateYearMonthDayApprovedRevisionDocumentNoVrSAPSPECPreparedema符等。

BLUETOOTH DOC Date / Year-Month-Day Approved Revision Document No 2008-12-18 V11r00 SAP_SPEC Prepared e-mail address N.B. Car WG Car-feedback@bluetooth.org SIM ACCESS PROFILE Interoperability Specification Abstract: This document defines the features and procedures that are required for the SIM Access Profile. The scope of this profile includes the following layers/protocols/profiles: Bluetooth Baseband, Link Manager Protocol, L2CAP, Service Discovery Protocol, Serial Port Profile and the Generic Access Profile. BLUETOOTH SPECIFICATION Page 2 of 51 SIM Access Profile (SAP) 18 December 2008 Revision History Revision Date Comments 0.1 08-Sep-00 First draft 0.2 29-Nov-00 Alignment with Specification Description; Procedures described in more detail; Comments from Raghunandan Sanjeev added. 0.3 29-Jan-01 Serial Port and Generic Access Control Profile Interoperability Requirements rewritten; Comments from J. Pulido added. 0.31 05-Feb-01 Comments from P. Breyer and K. Ulery added. 0.4 13-Mar-01 Features and Procedures reorganized: - "Transfer of PPS result" removed, - "Card Holder Type" extended to "Card Reader Status", - "Verify CHV" added, - "Server initiated SIM reactivate" added. Parameter list and Message coding added. 0.45 04-Apr-01 Comments from Bilbao face-to-face meeting added. Document reorganized for better readability. 0.49 16-Apr-01 Test Strategy added. Renaming from Remote Authentication Access to SIM Access Profile done. Message coding changed. Proposal for 0.5 version. 0.50 (preBARB) 28-May-01 Editorial changes after Car WG review Proposal for review by BARB 0.50 19-Jun-01 Editorial changes after BARB review 0.60 20-July-01 Changes in the procedures after discussion in the July 19th phone conference 0.61 30-July-01 All changes accepted; other comments from WG members added 0.65 01-August-01 Editorial changes in document: Connection setup and Status Report procedures modified 0.66 29-August-01 State Machine introduced Better definitions of ResultCode and StatusChange added Payload of ERROR_RESP simplified Byte ordering conventions added 0.69 14-Sept-01 Changes in Sections 7.3 Link Manager Interoperability Requirements and 7.4 Link Control Interoperability Requirements Protocol Stack (Section 2.1) and Message Example (Section 5.4) added Editorial changes in Sections 4.6 - 4.8 and 4.13 0.699 26-Sept-01 Changes after comments from Raghu and Michael 0.70 27-Sept-01 Document approved as 0.70 by the Car Working Group BLUETOOTH SPECIFICATION Page 3 of 51 SIM Access Profile (SAP) 18 December 2008 0.80 20-Nov-01 Editorial changes: • Section "Profile Dependencies" moved from Section 2.1 to 1.2 • Editorial changes in Sections 1 and 2 Changes WRT. the features "Power SIM on/off", "Reset SIM" and "Transfer ATR". 0.81 17-Dec-01 Changes after review during San Francisco f-2-f meeting 0.90 21-Dec-01 Draft version for Working Group approval 0.90a 04-Jan-02 Further improvements of the 0.90 draft: "Power SIM off" procedure has been made optional 0.90b 10-Jan-02 Comments from Jesus Pulido on Rev. 0.90a incorporated 0.90c 01-Feb-02 Comments from BARB review incorporated 0.95VD 22-Mar-02 Voting Draft 0.95VD b 18-Apr-02 Voting Draft with changes in Security Section (2.5) 0.95VD c 16-May-02 Voting Draft with changes after BARB, BQRB and BTI review 0.95VD d 17-Sep-02 Updates to allow access to UICC as well 0.95VD e 03-Oct-02 Updated to use generic term for all cards; Updated to allow access to R-UIM also 0.95VD f 13-Nov-02 Changed generic term Module to Subscriber Module 1.00 VD 22-Dec-04 Voting Draft D10r01 02-Feb-05 Updated for technical editing D10r02 15-Feb-05 Updates after BARB review V10r03 12-May-05 Adopted by the BoD D11r04 30-Aug-07 Updates for core spec 2.1+EDR D11r05 15-May-08 Update SDP version number and solution for spec errata 2564 D11r06 16-May-08 Updates for errata 2564 D11r07 28-May-08 Change profile dependency chart and address TB comments D11r08-12 01-July-08 Minor corrections and comments addressed D11 12-Dec-08 Prepare for publication. V11r00 18-Dec-08 Adopted by the Bluetooth SIG Board of Directors Contributors Name Company Penny Breyer Cambridge Silicon Radio Ltd. Björn Bunte Nokia Corp. Lowell Campbell Denso Corp. Patrick Clauberg Nokia Corp. Christian Gehrmann Ericsson Mobile Communications AB Holger Krummel Nokia Corp. Holger Lenz Berner & Mattner Systemtechnik GmbH Tony Mansour Motorola, Inc. BLUETOOTH SPECIFICATION Page 4 of 51 SIM Access Profile (SAP) 18 December 2008 Ganesh Pattabiraman Qualcomm Inc. Jesus-Angel Gonzalez Pulido Ericsson España, S.A. Daniel S. Rokusek Motorola, Inc. Raghunandan Sanjeev Motorola, Inc. Burch Seymour Continental Automotive Systems Kazu Suzuki Denso Corp. Michael Svob Motorola, Inc. Yoichiro Takeuchi Toshiba Corp. Dmitri Toropov (owner) Siemens AG Patrick Reinelt Siemens AG Kreg Ulery Agere Systems Monica Wifvesson Ericsson Mobile Communications AB Joachim Mertz Berner & Mattner Disclaimer and Copyright Notice The copyright in this specification is owned by the Promoter Members of Bluetooth Special Interest Group (SIG), Inc. (“Bluetooth SIG”). Use of these specifications and any related intellectual property (collectively, the “Specification”), is governed by the Promoters Membership Agreement among the Promoter Members and Bluetooth SIG (the “Promoters Agreement”), certain membership agreements between Bluetooth SIG and its Adopter and Associate Members (the “Membership Agreements”) and the Bluetooth Specification Early Adopters Agreements (1.2 Early Adopters Agreements) among Early Adopter members of the unincorporated Bluetooth SIG and the Promoter Members (the “Early Adopters Agreement”). Certain rights and obligations of the Promoter Members under the Early Adopters Agreements have been assigned to Bluetooth SIG by the Promoter Members. Use of the Specification by anyone who is not a member of Bluetooth SIG or a party to an Early Adopters Agreement (each such person or party, a “Member”), is prohibited. The legal rights and obligations of each Member are governed by their applicable Membership Agreement, Early Adopters Agreement or Promoters Agreement. No license, express or implied, by estoppel or otherwise, to any intellectual property rights are granted herein. Any use of the Specification not in compliance with the terms of the applicable Membership Agreement, Early Adopters Agreement or Promoters Agreement is prohibited and any such prohibited use may result in termination of the applicable Membership Agreement or Early Adopters Agreement and other liability permitted by the applicable agreement or by applicable law to Bluetooth SIG or any of its members for patent, copyright and/or trademark infringement. THE SPECIFICATION IS PROVIDED “AS IS” WITH NO WARRANTIES WHATSOEVER, INCLUDING ANY WARRANTY OF MERCHANTABILITY, NONINFRINGEMENT, FITNESS FOR ANY PARTICULAR PURPOSE, SATISFACTORY QUALITY, OR REASONABLE SKILL OR CARE, OR ANY WARRANTY ARISING OUT OF ANY COURSE OF DEALING, USAGE, TRADE PRACTICE, PROPOSAL, SPECIFICATION OR SAMPLE. Each Member hereby acknowledges that products equipped with the Bluetooth technology ("Bluetooth products") may be subject to various regulatory controls under the laws and regulations of various governments worldwide. Such laws and regulatory controls may govern, among other things, the combination, operation, use, implementation and distribution of Bluetooth products. Examples of such laws and regulatory controls include, but are not limited to, airline regulatory controls, telecommunications regulations, technology transfer controls and health and safety regulations. Each Member is solely BLUETOOTH SPECIFICATION Page 5 of 51 SIM Access Profile (SAP) 18 December 2008 responsible for the compliance by their Bluetooth Products with any such laws and regulations and for obtaining any and all required authorizations, permits, or licenses for their Bluetooth products related to such regulations within the applicable jurisdictions. Each Member acknowledges that nothing in the Specification provides any information or assistance in connection with securing such compliance, authorizations or licenses. NOTHING IN THE SPECIFICATION CREATES ANY WARRANTIES, EITHER EXPRESS OR IMPLIED, REGARDING SUCH LAWS OR REGULATIONS. ALL LIABILITY, INCLUDING LIABILITY FOR INFRINGEMENT OF ANY INTELLECTUAL PROPERTY RIGHTS OR FOR NONCOMPLIANCE WITH LAWS, RELATING TO USE OF THE SPECIFICATION IS EXPRESSLY DISCLAIMED. BY USE OF THE SPECIFICATION, EACH MEMBER EXPRESSLY WAIVES ANY CLAIM AGAINST BLUETOOTH SIG AND ITS PROMOTER MEMBERS RELATED TO USE OF THE SPECIFICATION. Bluetooth SIG reserve the right to adopt any changes or alterations to the Specification as it deems necessary or appropriate. Copyright 2001–2008. Bluetooth SIG, Inc. All copyrights in the Bluetooth Specifications themselves are owned by Ericsson AB, Lenovo, Intel Corporation, Microsoft Corporation, Motorola, Inc., Nokia Corporation and Toshiba Corporation. *Other third-party brands and names are the property of their respective owners. BLUETOOTH SPECIFICATION Page 6 of 51 SIM Access Profile (SAP) 18 December 2008 Document Terminology The Bluetooth SIG has adopted Section 13.1 of the IEEE Standards Style Manual, which dictates use of the words ``shall’’, ``should’’, ``may’’, and ``can’’ in the development of documentation, as follows: • The word shall is used to indicate mandatory requirements strictly to be followed in order to conform to the standard and from which no deviation is permitted (shall equals is required to). • The use of the word must is deprecated and shall not be used when stating mandatory requirements; must is used only to describe unavoidable situations. • The use of the word will is deprecated and shall not be used when stating mandatory requirements; will is only used in statements of fact. • The word should is used to indicate that among several possibilities one is recommended as particularly suitable, without mentioning or excluding others; or that a certain course of action is preferred but not necessarily required; or that (in the negative form) a certain course of action is deprecated but not prohibited (should equals is recommended that). • The word may is used to indicate a course of action permissible within the limits of the standard (may equals is permitted). • The word can is used for statements of possibility and capability, whether material, physical, or causal (can equals is able to). BLUETOOTH SPECIFICATION Page 7 of 51 SIM Access Profile (SAP) 18 December 2008 Contents 1  Introduction .................................................................................................................................... 8  1.1  Scope ......................................................................................................................................... 8  1.2  Profile Dependencies ................................................................................................................ 8  1.3  Symbols and Conventions ......................................................................................................... 9  2  Profile Overview ........................................................................................................................... 11  2.1  Profile Stack............................................................................................................................. 11  2.2  Configuration and Roles .......................................................................................................... 11  2.3  User Requirements and Scenarios ......................................................................................... 12  2.4  Profile Fundamentals ............................................................................................................... 13  2.5  Bluetooth Security ................................................................................................................... 14  2.6  Conformance ........................................................................................................................... 15  3  Application Layer Features ......................................................................................................... 16  3.1  Feature Definitions .................................................................................................................. 16  4  Procedures ................................................................................................................................... 18  4.1  Connect ................................................................................................................................... 18  4.2  Disconnect Initiated by the Client ............................................................................................ 21  4.3  Disconnect Initiated by the Server ........................................................................................... 21  4.4  Transfer APDU ........................................................................................................................ 22  4.5  Transfer ATR ........................................................................................................................... 23  4.6  Power SIM Off ......................................................................................................................... 24  4.7  Power SIM On ......................................................................................................................... 25  4.8  Reset SIM ................................................................................................................................ 26  4.9  Report Status ........................................................................................................................... 28  4.10  Transfer Card Reader Status .................................................................................................. 29  4.11  Error Response ....................................................................................................................... 30  1.12  Set Transport Protocol ............................................................................................................. 30  4.12  State Machine .......................................................................................................................... 31  4.13  Bluetooth Link Loss ................................................................................................................. 33  5  Message and Parameters ............................................................................................................ 34  5.1  Message Formats .................................................................................................................... 34  1.13  Message Coding ...................................................................................................................... 35  5.2  Parameter IDs and Coding ...................................................................................................... 40  5.3  Example ................................................................................................................................... 43  6  Service Discovery Procedures ................................................................................................... 44  7  Serial Port Profile Interoperability Requirements ..................................................................... 45  7.1  RFCOMM Interoperability Requirements ................................................................................ 45  7.2  L2CAP Interoperability Requirements ..................................................................................... 45  7.3  Link Manager (LM) Interoperability Requirements .................................................................. 45  7.4  Link Control (LC) Interoperability Requirements ..................................................................... 45  8  Generic Access Profile Interoperability Requirements ............................................................ 46  8.1  Modes ...................................................................................................................................... 46  8.2  Security Aspects ...................................................................................................................... 46  8.3  Idle Mode Procedures ............................................................................................................. 47  9  References .................................................................................................................................... 48  10  List of Acronyms and Abbreviations ......................................................................................... 49  11  List of Figures .............................................................................................................................. 50  12  List of Tables ................................................................................................................................ 51  BLUETOOTH SPECIFICATION Page 8 of 51 SIM Access Profile (SAP) 18 December 2008 1 Introduction 1.1 Scope This SIM Access Profile defines the protocols and procedures that shall be used to access a GSM SIM card, a UICC card or an R-UIM card via a Bluetooth link. Unless otherwise specified the term “Subscription module” shall be used to refer to the GSM SIM card, a UICC card or an R-UIM card. With the SIM Access Profile, the user can personalize his/her car-embedded phone with a subscription module in an external device, which is connected via a Bluetooth wireless link. The external device can either be a simple SIM card holder or a portable phone, which is brought into the car. The SIM Access Profile builds on the well-defined interface between the telephone and a subscription module (see [3] and [6]). It also enables multiple card operations as defined in [4], [8] and [11]. 1.2 Profile Dependencies Figure 1.1 shows the Bluetooth profile structure and the dependencies of the profiles. A profile is dependent upon another profile if it re-uses parts of that profile, by implicitly or explicitly referencing it. Dependency is illustrated in the figure below: a profile has dependencies on the profile(s) in which it is contained directly or indirectly. Figure 1.1: Profile Dependencies BLUETOOTH SPECIFICATION Page 9 of 51 SIM Access Profile (SAP) 18 December 2008 1.3 Symbols and Conventions 1.3.1 Requirement Status Symbols In this document, the following symbols are used: "M" for mandatory to support (used for capabilities that shall be used in the profile); "O" for optional to support (used for capabilities that can be used in the profile); "C" for conditional support (used for capabilities that shall be used in case a certain other capability is supported); "X" for excluded (used for capabilities that may be supported by the unit but shall never be used in the profile if this is the only active profile); "N/A" for not applicable (in the given context it is impossible to use this capability). Some excluded capabilities are capabilities that, according to the relevant Bluetooth specification, are mandatory. These are features that may degrade operation of devices following this profile. Therefore, these features should not be activated while a unit is operating as a unit within this profile. 1.3.2 Signaling Diagram Conventions The following arrows are used in diagrams describing procedures (see Figure 1.2

编辑推荐

  • 名称/格式
  • 评分
  • 下载次数
  • 资料大小
  • 上传时间

用户评论

0/200
    暂无评论
上传我的资料

相关资料

资料评价:

/ 51
所需积分:1 立即下载
返回
顶部
举报
资料
关闭

温馨提示

感谢您对爱问共享资料的支持,精彩活动将尽快为您呈现,敬请期待!