关闭

关闭

关闭

封号提示

内容

首页 SAP_SPEC_V11(SIM_Access_Profile).pdf

SAP_SPEC_V11(SIM_Access_Profile).pdf

SAP_SPEC_V11(SIM_Access_Profile…

上传者: wusi524888 2014-03-30 评分 0 0 0 0 0 0 暂无简介 简介 举报

简介:本文档为《SAP_SPEC_V11(SIM_Access_Profile)pdf》,可适用于IT/计算机领域,主题内容包含BLUETOOTHDOCDateYearMonthDayApprovedRevisionDocumentNoVrSAPSPECPreparedema符等。

BLUETOOTHDOCDateYearMonthDayApprovedRevisionDocumentNoVrSAPSPECPreparedemailaddressNBCarWGCarfeedbackbluetoothorgSIMACCESSPROFILEInteroperabilitySpecificationAbstract:ThisdocumentdefinesthefeaturesandproceduresthatarerequiredfortheSIMAccessProfileThescopeofthisprofileincludesthefollowinglayersprotocolsprofiles:BluetoothBaseband,LinkManagerProtocol,LCAP,ServiceDiscoveryProtocol,SerialPortProfileandtheGenericAccessProfileBLUETOOTHSPECIFICATIONPageofSIMAccessProfile(SAP)DecemberRevisionHistoryRevisionDateCommentsSepFirstdraftNovAlignmentwithSpecificationDescriptionProceduresdescribedinmoredetailCommentsfromRaghunandanSanjeevaddedJanSerialPortandGenericAccessControlProfileInteroperabilityRequirementsrewrittenCommentsfromJPulidoaddedFebCommentsfromPBreyerandKUleryaddedMarFeaturesandProceduresreorganized:"TransferofPPSresult"removed,"CardHolderType"extendedto"CardReaderStatus","VerifyCHV"added,"ServerinitiatedSIMreactivate"addedParameterlistandMessagecodingaddedAprCommentsfromBilbaofacetofacemeetingaddedDocumentreorganizedforbetterreadabilityAprTestStrategyaddedRenamingfromRemoteAuthenticationAccesstoSIMAccessProfiledoneMessagecodingchangedProposalforversion(preBARB)MayEditorialchangesafterCarWGreviewProposalforreviewbyBARBJunEditorialchangesafterBARBreviewJulyChangesintheproceduresafterdiscussionintheJulythphoneconferenceJulyAllchangesacceptedothercommentsfromWGmembersaddedAugustEditorialchangesindocument:ConnectionsetupandStatusReportproceduresmodifiedAugustStateMachineintroducedBetterdefinitionsofResultCodeandStatusChangeaddedPayloadofERRORRESPsimplifiedByteorderingconventionsaddedSeptChangesinSectionsLinkManagerInteroperabilityRequirementsandLinkControlInteroperabilityRequirementsProtocolStack(Section)andMessageExample(Section)addedEditorialchangesinSectionsandSeptChangesaftercommentsfromRaghuandMichaelSeptDocumentapprovedasbytheCarWorkingGroupBLUETOOTHSPECIFICATIONPageofSIMAccessProfile(SAP)DecemberNovEditorialchanges:•Section"ProfileDependencies"movedfromSectionto•EditorialchangesinSectionsandChangesWRTthefeatures"PowerSIMonoff","ResetSIM"and"TransferATR"DecChangesafterreviewduringSanFranciscoffmeetingDecDraftversionforWorkingGroupapprovalaJanFurtherimprovementsofthedraft:"PowerSIMoff"procedurehasbeenmadeoptionalbJanCommentsfromJesusPulidoonRevaincorporatedcFebCommentsfromBARBreviewincorporatedVDMarVotingDraftVDbAprVotingDraftwithchangesinSecuritySection()VDcMayVotingDraftwithchangesafterBARB,BQRBandBTIreviewVDdSepUpdatestoallowaccesstoUICCaswellVDeOctUpdatedtousegenerictermforallcardsUpdatedtoallowaccesstoRUIMalsoVDfNovChangedgenerictermModuletoSubscriberModuleVDDecVotingDraftDrFebUpdatedfortechnicaleditingDrFebUpdatesafterBARBreviewVrMayAdoptedbytheBoDDrAugUpdatesforcorespecEDRDrMayUpdateSDPversionnumberandsolutionforspecerrataDrMayUpdatesforerrataDrMayChangeprofiledependencychartandaddressTBcommentsDrJulyMinorcorrectionsandcommentsaddressedDDecPrepareforpublicationVrDecAdoptedbytheBluetoothSIGBoardofDirectorsContributorsNameCompanyPennyBreyerCambridgeSiliconRadioLtdBjörnBunteNokiaCorpLowellCampbellDensoCorpPatrickClaubergNokiaCorpChristianGehrmannEricssonMobileCommunicationsABHolgerKrummelNokiaCorpHolgerLenzBernerMattnerSystemtechnikGmbHTonyMansourMotorola,IncBLUETOOTHSPECIFICATIONPageofSIMAccessProfile(SAP)DecemberGaneshPattabiramanQualcommIncJesusAngelGonzalezPulidoEricssonEspaña,SADanielSRokusekMotorola,IncRaghunandanSanjeevMotorola,IncBurchSeymourContinentalAutomotiveSystemsKazuSuzukiDensoCorpMichaelSvobMotorola,IncYoichiroTakeuchiToshibaCorpDmitriToropov(owner)SiemensAGPatrickReineltSiemensAGKregUleryAgereSystemsMonicaWifvessonEricssonMobileCommunicationsABJoachimMertzBernerMattnerDisclaimerandCopyrightNoticeThecopyrightinthisspecificationisownedbythePromoterMembersofBluetoothSpecialInterestGroup(SIG),Inc(“BluetoothSIG”)Useofthesespecificationsandanyrelatedintellectualproperty(collectively,the“Specification”),isgovernedbythePromotersMembershipAgreementamongthePromoterMembersandBluetoothSIG(the“PromotersAgreement”),certainmembershipagreementsbetweenBluetoothSIGanditsAdopterandAssociateMembers(the“MembershipAgreements”)andtheBluetoothSpecificationEarlyAdoptersAgreements(EarlyAdoptersAgreements)amongEarlyAdoptermembersoftheunincorporatedBluetoothSIGandthePromoterMembers(the“EarlyAdoptersAgreement”)CertainrightsandobligationsofthePromoterMembersundertheEarlyAdoptersAgreementshavebeenassignedtoBluetoothSIGbythePromoterMembersUseoftheSpecificationbyanyonewhoisnotamemberofBluetoothSIGorapartytoanEarlyAdoptersAgreement(eachsuchpersonorparty,a“Member”),isprohibitedThelegalrightsandobligationsofeachMemberaregovernedbytheirapplicableMembershipAgreement,EarlyAdoptersAgreementorPromotersAgreementNolicense,expressorimplied,byestoppelorotherwise,toanyintellectualpropertyrightsaregrantedhereinAnyuseoftheSpecificationnotincompliancewiththetermsoftheapplicableMembershipAgreement,EarlyAdoptersAgreementorPromotersAgreementisprohibitedandanysuchprohibitedusemayresultinterminationoftheapplicableMembershipAgreementorEarlyAdoptersAgreementandotherliabilitypermittedbytheapplicableagreementorbyapplicablelawtoBluetoothSIGoranyofitsmembersforpatent,copyrightandortrademarkinfringementTHESPECIFICATIONISPROVIDED“ASIS”WITHNOWARRANTIESWHATSOEVER,INCLUDINGANYWARRANTYOFMERCHANTABILITY,NONINFRINGEMENT,FITNESSFORANYPARTICULARPURPOSE,SATISFACTORYQUALITY,ORREASONABLESKILLORCARE,ORANYWARRANTYARISINGOUTOFANYCOURSEOFDEALING,USAGE,TRADEPRACTICE,PROPOSAL,SPECIFICATIONORSAMPLEEachMemberherebyacknowledgesthatproductsequippedwiththeBluetoothtechnology("Bluetoothproducts")maybesubjecttovariousregulatorycontrolsunderthelawsandregulationsofvariousgovernmentsworldwideSuchlawsandregulatorycontrolsmaygovern,amongotherthings,thecombination,operation,use,implementationanddistributionofBluetoothproductsExamplesofsuchlawsandregulatorycontrolsinclude,butarenotlimitedto,airlineregulatorycontrols,telecommunicationsregulations,technologytransfercontrolsandhealthandsafetyregulationsEachMemberissolelyBLUETOOTHSPECIFICATIONPageofSIMAccessProfile(SAP)DecemberresponsibleforthecompliancebytheirBluetoothProductswithanysuchlawsandregulationsandforobtaininganyandallrequiredauthorizations,permits,orlicensesfortheirBluetoothproductsrelatedtosuchregulationswithintheapplicablejurisdictionsEachMemberacknowledgesthatnothingintheSpecificationprovidesanyinformationorassistanceinconnectionwithsecuringsuchcompliance,authorizationsorlicensesNOTHINGINTHESPECIFICATIONCREATESANYWARRANTIES,EITHEREXPRESSORIMPLIED,REGARDINGSUCHLAWSORREGULATIONSALLLIABILITY,INCLUDINGLIABILITYFORINFRINGEMENTOFANYINTELLECTUALPROPERTYRIGHTSORFORNONCOMPLIANCEWITHLAWS,RELATINGTOUSEOFTHESPECIFICATIONISEXPRESSLYDISCLAIMEDBYUSEOFTHESPECIFICATION,EACHMEMBEREXPRESSLYWAIVESANYCLAIMAGAINSTBLUETOOTHSIGANDITSPROMOTERMEMBERSRELATEDTOUSEOFTHESPECIFICATIONBluetoothSIGreservetherighttoadoptanychangesoralterationstotheSpecificationasitdeemsnecessaryorappropriateCopyright–BluetoothSIG,IncAllcopyrightsintheBluetoothSpecificationsthemselvesareownedbyEricssonAB,Lenovo,IntelCorporation,MicrosoftCorporation,Motorola,Inc,NokiaCorporationandToshibaCorporation*OtherthirdpartybrandsandnamesarethepropertyoftheirrespectiveownersBLUETOOTHSPECIFICATIONPageofSIMAccessProfile(SAP)DecemberDocumentTerminologyTheBluetoothSIGhasadoptedSectionoftheIEEEStandardsStyleManual,whichdictatesuseofthewords``shall’’,``should’’,``may’’,and``can’’inthedevelopmentofdocumentation,asfollows:•Thewordshallisusedtoindicatemandatoryrequirementsstrictlytobefollowedinordertoconformtothestandardandfromwhichnodeviationispermitted(shallequalsisrequiredto)•Theuseofthewordmustisdeprecatedandshallnotbeusedwhenstatingmandatoryrequirementsmustisusedonlytodescribeunavoidablesituations•Theuseofthewordwillisdeprecatedandshallnotbeusedwhenstatingmandatoryrequirementswillisonlyusedinstatementsoffact•Thewordshouldisusedtoindicatethatamongseveralpossibilitiesoneisrecommendedasparticularlysuitable,withoutmentioningorexcludingothersorthatacertaincourseofactionispreferredbutnotnecessarilyrequiredorthat(inthenegativeform)acertaincourseofactionisdeprecatedbutnotprohibited(shouldequalsisrecommendedthat)•Thewordmayisusedtoindicateacourseofactionpermissiblewithinthelimitsofthestandard(mayequalsispermitted)•Thewordcanisusedforstatementsofpossibilityandcapability,whethermaterial,physical,orcausal(canequalsisableto)BLUETOOTHSPECIFICATIONPageofSIMAccessProfile(SAP)DecemberContents Introduction  Scope  ProfileDependencies  SymbolsandConventions  ProfileOverview  ProfileStack  ConfigurationandRoles  UserRequirementsandScenarios  ProfileFundamentals  BluetoothSecurity  Conformance  ApplicationLayerFeatures  FeatureDefinitions  Procedures  Connect  DisconnectInitiatedbytheClient  DisconnectInitiatedbytheServer  TransferAPDU  TransferATR  PowerSIMOff  PowerSIMOn  ResetSIM  ReportStatus  TransferCardReaderStatus  ErrorResponse  SetTransportProtocol  StateMachine  BluetoothLinkLoss  MessageandParameters  MessageFormats  MessageCoding  ParameterIDsandCoding  Example  ServiceDiscoveryProcedures  SerialPortProfileInteroperabilityRequirements  RFCOMMInteroperabilityRequirements  LCAPInteroperabilityRequirements  LinkManager(LM)InteroperabilityRequirements  LinkControl(LC)InteroperabilityRequirements  GenericAccessProfileInteroperabilityRequirements  Modes  SecurityAspects  IdleModeProcedures  References  ListofAcronymsandAbbreviations  ListofFigures  ListofTables BLUETOOTHSPECIFICATIONPageofSIMAccessProfile(SAP)DecemberIntroductionScopeThisSIMAccessProfiledefinestheprotocolsandproceduresthatshallbeusedtoaccessaGSMSIMcard,aUICCcardoranRUIMcardviaaBluetoothlinkUnlessotherwisespecifiedtheterm“Subscriptionmodule”shallbeusedtorefertotheGSMSIMcard,aUICCcardoranRUIMcardWiththeSIMAccessProfile,theusercanpersonalizehishercarembeddedphonewithasubscriptionmoduleinanexternaldevice,whichisconnectedviaaBluetoothwirelesslinkTheexternaldevicecaneitherbeasimpleSIMcardholderoraportablephone,whichisbroughtintothecarTheSIMAccessProfilebuildsonthewelldefinedinterfacebetweenthetelephoneandasubscriptionmodule(seeand)Italsoenablesmultiplecardoperationsasdefinedin,andProfileDependenciesFigureshowstheBluetoothprofilestructureandthedependenciesoftheprofilesAprofileisdependentuponanotherprofileifitreusespartsofthatprofile,byimplicitlyorexplicitlyreferencingitDependencyisillustratedinthefigurebelow:aprofilehasdependenciesontheprofile(s)inwhichitiscontaineddirectlyorindirectlyFigure:ProfileDependenciesBLUETOOTHSPECIFICATIONPageofSIMAccessProfile(SAP)DecemberSymbolsandConventionsRequirementStatusSymbolsInthisdocument,thefollowingsymbolsareused:"M"formandatorytosupport(usedforcapabilitiesthatshallbeusedintheprofile)"O"foroptionaltosupport(usedforcapabilitiesthatcanbeusedintheprofile)"C"forconditionalsupport(usedforcapabilitiesthatshallbeusedincaseacertainothercapabilityissupported)"X"forexcluded(usedforcapabilitiesthatmaybesupportedbytheunitbutshallneverbeusedintheprofileifthisistheonlyactiveprofile)"NA"fornotapplicable(inthegivencontextitisimpossibletousethiscapability)Someexcludedcapabilitiesarecapabilitiesthat,accordingtotherelevantBluetoothspecification,aremandatoryThesearefeaturesthatmaydegradeoperationofdevicesfollowingthisprofileTherefore,thesefeaturesshouldnotbeactivatedwhileaunitisoperatingasaunitwithinthisprofileSignalingDiagramConventionsThefollowingarrowsareusedindiagramsdescribingprocedures(seeFigure

用户评论(0)

0/200

精彩专题

上传我的资料

每篇奖励 +2积分

资料评价:

/10
仅支持在线阅读

意见
反馈

立即扫码关注

爱问共享资料微信公众号

返回
顶部