Open Mobile API Spec v3.0规范详解：手机应用与SIM/UICC/SE之间的通讯过程

5星 · 超过95%的资源需积分: 49 14 浏览量更新于2024-07-22 2 收藏 1.55MB PDF 举报

身份认证购VIP最低享 7 折!

30元优惠券

Open Mobile API Specification v3.0 规范 Open Mobile API Specification v3.0 规范是手机应用程序与手机 SIM/UICC/SE 之间进行通讯的过程的详细规范，提供了详细的 API 使用指南。该规范的主要目的是提供一个通用的 API 规范，以便手机应用程序与手机 SIM/UICC/SE 之间进行安全、可靠的通讯。该规范涵盖了通讯过程中的各个方面，包括安全、身份验证、移动性等。在该规范中，定义了多个类和接口，包括 SEService、Reader、Session、Channel 等，这些类和接口提供了通讯过程中的各个方面的功能。 SEService 类是手机应用程序与手机 SIM/UICC/SE 之间通讯的核心类，提供了多个方法来实现通讯过程中的各个方面的功能。Reader 类是手机应用程序与手机 SIM/UICC/SE 之间通讯的辅助类，提供了读取手机 SIM/UICC/SE 的信息的功能。Session 类是手机应用程序与手机 SIM/UICC/SE 之间通讯的会话类，提供了通讯过程中的会话管理功能。Channel 类是手机应用程序与手机 SIM/UICC/SE 之间通讯的通道类，提供了通讯过程中的数据传输功能。在该规范中，还定义了多个接口，包括 SEServiceCallback、ReaderCallback、SessionCallback 等，这些接口提供了通讯过程中的各个方面的回调功能。在该规范中，还提供了多个 API，包括 Transport API、Service Layer API 等，这些 API 提供了通讯过程中的各个方面的功能。 Transport API 是手机应用程序与手机 SIM/UICC/SE 之间通讯的基础 API，提供了通讯过程中的基本功能。Service Layer API 是手机应用程序与手机 SIM/UICC/SE 之间通讯的高级 API，提供了通讯过程中的高级功能。 Open Mobile API Specification v3.0 规范提供了手机应用程序与手机 SIM/UICC/SE 之间进行通讯的详细规范，涵盖了通讯过程中的各个方面的功能，包括安全、身份验证、移动性等，为手机应用程序与手机 SIM/UICC/SE 之间的通讯提供了一个通用的解决方案。知识点： 1. Open Mobile API Specification v3.0 规范的主要目的是提供一个通用的 API 规范，以便手机应用程序与手机 SIM/UICC/SE 之间进行安全、可靠的通讯。 2. 该规范涵盖了通讯过程中的各个方面，包括安全、身份验证、移动性等。 3. 该规范定义了多个类和接口，包括 SEService、Reader、Session、Channel 等，这些类和接口提供了通讯过程中的各个方面的功能。 4. 该规范提供了多个 API，包括 Transport API、Service Layer API 等，这些 API 提供了通讯过程中的各个方面的功能。 5. 该规范提供了一个通用的解决方案，为手机应用程序与手机 SIM/UICC/SE 之间的通讯提供了一个可靠的解决方案。请注意，该规范提供了一个通用的解决方案，为手机应用程序与手机 SIM/UICC/SE 之间的通讯提供了一个可靠的解决方案。如果您需要了解更多关于 Open Mobile API Specification v3.0 规范的信息，请访问 SIM Alliance 的官方网站。

资源详情

资源推荐

Securing the future of mobile services

Open Mobile API Specification

Security, Identity, Mobility

6.2.2 Class: SEService

The SEService realizes the communication to available SEs on the device.

This is the entry point of this API. It is used to connect to the infrastructure and get access to a

list of SE readers.

(a) Constructor: SEService(Context context, SEService.CallBack listener)

Establishes a new connection that can be used to connect to all the SEs available in the

system. The connection process can be quite long, so it happens in an asynchronous

way. It is usable only if the specified listener is called or if isConnected() returns true.

The call-back object passed as a parameter will have its serviceConnected() method

called when the connection actually happen.

Parameters:

context - the context of the calling application. Cannot be null.

listener - a SEService.CallBack object. Can be null.

(b) Method: Reader[] getReaders()

Returns the list of available SE readers. There must be no duplicated objects in the

returned list. All available readers shall be listed even if no card is inserted.

Return value:

The readers list, as an array of readers. If there are no readers the returned array is of

length 0.

Errors:

NullPointerError – if context is NULL.

IllegalStateError - if the SEService object is not connected.

Tells whether or not the service is connected.

Return value:

True if the service is connected.

(d) Method: void shutdown()

Releases all SE resources allocated by this SEService (including any binding to an

underlying service). As a result isConnected() will return false after shutdown() was called.

After this method call, the SEService object is not connected.

It is recommended to call this method in the termination method of the calling application

(or part of this application) which is bound to this SEService.

(e) Method: String getVersion()

Returns the version of the Open Mobile API Specification this implementation is based

on.

Return value:

String containing the Open Mobile API version (e.g. "3.0").

6.2.3 Class (or interface): SEService:CallBack

Interface to receive call-backs when the service is connected.

If the target language and environment allows it, then this shall be an inner interface of the

SEService class.

(a) Method: void serviceConnected(SEService service)

Called by the framework when the service is connected.

Parameters:

service - the connected service.

Securing the future of mobile services

Open Mobile API Specification

Security, Identity, Mobility

6.2.4 Class: Reader

Instances of this class represent SE readers supported by this device. These readers can be

physical devices or virtual devices. They can be removable or not. They can contain one SE that

can or cannot be removed.

(a) Method: String getName()

Return the name of this reader.

 If this reader is a SIM reader, then its name must be "SIM[Slot]"

 If the reader is a SD or micro SD reader, then its name must be “SD[slot]”

 If the reader is an embedded SE reader, then its name must be “eSE[slot]”

Slot is a decimal number without leading zeros. The numbering must start with 1 (e.g.

SIM1, SIM2, … or SD1, SD2, … or eSE1, eSE2, …). The slot number “1” for a reader is

optional (SIM and SIM1 are both valid for the first SIM-reader, but if there are two readers

then the second reader must be named SIM2). This applies also for other SD or SE

readers.

Return value:

The reader name, as a String.

(b) Method: SEService getSEService()

Return the SE service this reader is bound to.

Return value:

The SEService object.

Check if a SE is present in this reader.

Return value:

True if the SE is present, false otherwise.

(d) Method: Session openSession()

Connects to a SE in this reader.

This method prepares (initialises) the SE for communication before the session object is

returned (i.e. powers the SE by ICC ON if it is not already on).

There might be multiple sessions opened at the same time on the same reader. The

system ensures the interleaving of APDUs between the respective sessions.

Return value:

A Session object to be used to create channels.

Errors:

IOError - if something went wrong when communicating with the SE or the reader.

(e) Method: void closeSessions()

Close all the sessions opened on this reader. All the channels opened by all these

sessions will be closed.

6.2.5 Class: Session

Instances of this class represent a connection session to one of the SEs available on the device.

These objects can be used to get a communication channel with an applet in the SE. This channel

can be the basic channel or a logical channel.

(a) Method: Reader getReader()

Get the reader that provides this session.

Return value:

The reader object.

Securing the future of mobile services

Open Mobile API Specification

Security, Identity, Mobility

(b) Method: byte[] getATR()

Get the ATR of this SE.

The returned byte array can be null if the ATR for this SE is not available.

Return value:

The ATR as a byte array or null.

Close the connection with the SE. This will close any channels opened by this application

with this SE.

(d) Method: boolean isClosed()

Tells if this session is closed.

Return value:

True if the session is closed, false otherwise.

(e) Method: void closeChannels()

Close any channel opened on this session.

(f) Method: Channel openBasicChannel(byte[] aid, Byte P2)

Get access to the basic channel, as defined in the ISO/IEC 7816-4 specification (the one

that has number 0). The obtained object is an instance of the channel class.

If the AID is null, it means no applet is to be selected on this channel and the default applet

is used. If the AID is defined then the corresponding applet is selected.

Once this channel has been opened by a device application, it is considered as ’locked’

by this device application, and other calls to this method will return null, until the channel

is closed. Some SEs (like the UICC) might always keep the basic channel locked (i.e.

return null to applications), to prevent access to the basic channel, while some others

might return a channel object implementing some kind of filtering on the commands,

restricting the set of accepted command to a smaller set.

It is recommended for the UICC to reject the opening of the basic channel to a specific

applet, by always answering null to such a request.

For other SEs, the recommendation is to accept opening the basic channel on the default

applet until another applet is selected on the basic channel. As there is no other way than

a reset to select again the default applet, the implementation of the transport API should

guarantee that the openBasicChannel(null) command will return null until a reset occurs.

With the previous release (V2.05), it was not possible to set P2 value, this value was

always set to ‘00’. Except for specific needs it is recommended to keep P2 set to ‘00’. It is

recommended that the device allows all values for P2, however only the following values

are mandatory: ‘00’, ‘04’, ‘08’, ‘0C’ (as defined in [2]).

The implementation of the underlying SELECT command within this method shall be

based on ISO 7816-4 with following options:

CLA = ‘00’

INS = ‘A4’

P1=’04’ (Select by DF name/application identifier)

The select response data can be retrieved with byte[] getSelectResponse().

The API shall handle received status word as follows. If the status word indicates that the

SE was able to open a channel (e.g. status word ‘90 00’ or status words referencing a

warning in ISO-7816-4: ’62 XX” or “63 XX’) the API shall keep the channel opened and

the next getSelectResponse() shall return the received status word.

Securing the future of mobile services

Open Mobile API Specification

Security, Identity, Mobility

Other received status codes indicating that the SE was not able to open a channel shall

be considered as an error and the corresponding channel shall not be opened.

The function without P2 as parameter is provided for backwards compatibility and will fall

back to a select command with P2=’00’.

Parameters:

aid - the AID of the applet to be selected on this channel, as a byte array, or null if no

applet is to be selected.

P2 - the P2 parameter of the SELECT APDU executed on this channel.

Return value:

An instance of channel if available or null.

Errors:

IllegalParameterError - if the aid's length is not within 5 to 16 (inclusive).

IllegalStateError - if the SE session is used after being closed.

SecurityError - if the calling application cannot be granted access to this AID or the default

applet on this session.

NoSuchElementError – If the AID on the SE is not available or cannot be selected.

OperationNotSupportedError – if the given P2 parameter is not supported by the device.

IOError - if there is a communication problem to the reader or the SE.

(g) Method: Channel openBasicChannel(byte[] aid)

This method is provided to ease the development of mobile application and for compliancy

with existing applications. This method is equivalent to openBasicChannel(aid, P2=0x00).

(h) Method: Channel openLogicalChannel(byte[] aid, Byte P2)

Open a logical channel with the SE, selecting the applet represented by the given AID. If

the AID is null, which means no applet is to be selected on this channel, the default applet

is used. It's up to the SE to choose which logical channel will be used.

With the previous release (V2.05) it was not possible to set P2 value, this value was

always set to ‘00’. Except for specific needs it is recommended to keep P2 set to ‘00’. It is

recommended that the device allows all values for P2, however only the following values

are mandatory: ‘00’, ‘04’, ‘08’, ‘0C’ (as defined in [2]).

The implementation of the underlying SELECT command within this method shall be

based on ISO 7816-4 with the following options:

CLA = ‘01’ to ‘03’, ‘40 to 4F’

INS = ‘A4’

P1=’04’ (Select by DF name/application identifier)

The select response data can be retrieved with byte[] getSelectResponse().

The API shall handle received status word as follows. If the status word indicates that the

SE was able to open a channel (e.g. status word ‘90 00’ or status words referencing a

warning in ISO-7816-4: ’62 XX” or “63 XX’) the API shall keep the channel opened and

the next getSelectResponse() shall return the received status word.

Other received status codes indicating that the SE was not able to open a channel shall

be considered as an error and the corresponding channel shall not be opened.

In the case of a UICC it is recommended that the API rejects the opening of the logical

channel without a specific AID, by always answering null to such a request.

剩余76页未读，继续阅读

huhb

粉丝: 11
资源: 8

Open Mobile API Spec v3.0规范详解：手机应用与SIM/UICC/SE之间的通讯过程

OpenMobileAPI jar包

android open wps

Android NFC之Openmobileapi类加载写法

Open Mobile API specification 中文版

Global Platform card specification v2.3.1

OpenMobileAPI jar包（15,17,18,19,21）

OpenMobileAPI jar包(org.simalliance.openmobileapi.jar)

SIMalliance_OpenMobileAPI_v3_2.pdf

Open mobile api规范

openMobileAPI

OpenMobileAPI 15 17 18 19 21 jar包

numexpr-2.8.3-cp38-cp38-win_amd64.whl

ujson-5.3.0-cp311-cp311-win_amd64.whl

基于MATLAB车牌识别程序技术实现面板GUI.zip

RJFireWall-maste赛资源

msgpack-1.0.4-cp39-cp39-win_amd64.whl

基于 YOLOv11 的混凝土缺陷检测系统（包含详细的完整的程序和数据）

用 Python 实现简单网页爬虫并保存为CSV教程.txt

chompack-2.3.3-cp35-cp35m-win_amd64.whl

sparsesvd-0.2.2-cp38-cp38-win_amd64.whl

最新资源