Default empty constructor, and is present only to support virtual function table export.

This function member closes a RMobileSmartCardEap sub-session. The Close() request also attempts to release this instance's lock on the <AID,EAPType> (DF_EAP).

Delayed construction of heap stored data members.

This function is used by RMobileSmartCardEap::Open() to convert the TAID (which is binary data) to a string that can be passed through ETel. The conversion changes the binary data to a string of hexadecimal semi-octets.

RMobileSmartCardEap::Open()

Called internally when RMobileSmartCardEap instance is no longer required, to ensure clean up of data members from memory.

The authentication status is obtained from the EAP supporting UICC application's EF_EAPSTATUS. It specifies the current state of authentication in the DF_EAP.

Retrieves the generated key stored in EF_EAPKEYS of the DF_EAP (see section 7.1 of ETSI TS 102.310 v6.2.0).

Synchronous request to get the current status of the DF_EAP. This state value is held by the platform to ensure exclusive access to a DF_EAP; it is NOT a state of any Smart Card Application file.

This method allows the client to retrieve the user identity data to be used for an EAP based authentication. The client will specify which identity type they want to read by setting the aRequestIdType parameter to the appropriate enumeration value. The user Id data is returned as a packaged instance of TEapUserIdentityV6 within the aUserId.

An example base band functionality that would be used to service this request is the +CEPR (see section 8.48 of 3GPP TS 27.007 v6.8.0) AT- command, which returns "identity" and "pseudonym" as two of its defined values.

EF_PUId and EF_Ps hold these identities (specified in sections 7.3 and 7.4, respectively, of ETSI TS 102.310 v6.2.0).

Initialises access to the DF_EAP. This will ensure the aAID and aEapType given in the RMobileSmartCardEap::Open() exist and are accessible. If for any reason the sub-session is inaccessible, the client can request a notification for state changes using RMobileSmartCardEap::NotifyEapMethodAccessStatusChange() .

Returns whether this RMobileSmartCardEap instance has ownership of its corresponding DF_EAP.

Notifies the client when the EAP method's (DF_EAP's) access status changes.

The status begins as EEapMethodAvailable when the DF_EAP is first used; before RMobileSmartCardEap::InitialiseEapMethod() is called by the client. EEapMethodInUseApplicationActive state is given after the first client initialises... various cases cause transformations to states EEapMethodUnableToInitialise or EEapMethodInUseApplicationInactive.

This function opens a RMobileSmartCardEap sub-session from RMobilePhone that will refer to the application referenced by aAID. It will be assumed that the application exists and contains a DF_EAP for the aEapType specified. The client must call RMobileSmartCardEap::InitialiseEapMethod() to ensure correct functionality of this sub-session.

Relinquishes ownership of the DF_EAP, to allow other clients to use it. Although the request completes relatively quickly, it will set the server's process running to attempt a deactivate on the sub-session's corresponding application. The deactivate will allow future clients to initialise the application, which should reset all its DF_EAP states.

The initial state change of the sub-session will be EEapMethodUnableToInitialise, as the request completes without waiting for the application's deactivation. After the sub-session is able to deactivate the app, the state will change to EEapMethodAvailable.

The server will make a decision on deactivating the application based on whether there are other sub-session open to the same application (but different EAP types/ DF_EAP). Only when the application is no longer in use, that the server will deactivate it.

Notifications can be posted using RMobileSmartCardEap::NotifyEapMethodAccessStatusChange() to observe such state changes.

Returns the character that corresponds to the value of its parameter (base 17!).

Authentication status of the EAP supporting UICC application (See section 7.2 of ETSI TS 102.310 v6.2.0). One of these values is returned on completion of an RMobileSmartCardEap::GetAuthenticationStatus() request.

RMobileSmartCardEap::GetAuthenticationStatus()

TEapKeyV6 should be used to request one of (currently) two keys available on the EF_EAPKEYS of the UICC application (see section 7.1 of ETSI TS 102.310 v6.2.0). This enumeration type should be used in RMobileSmartCardEap::GetEapKey() to specify the key to be retrieved.

RMobileSmartCardEap::TEapKeyV6 RMobileSmartCardEap::GetEapKey()

Status of the DF_EAP this subsession refers to. The status is basically an indication of whether the DF is in use by another sub- session client instance.

NotifyEapMethodAccessStatusChange() will give a notification when the status changes.

Status will change when the first client calls InitialiseEapMethod() on this sub-session. When the same client calls ReleaseEapMethod() (or Close() ), the status will change again. This allows mutually exclusive access to the DF_EAP. All other RMobileSmartCardEap hanles will get an error if they attempt to make requests that access the same DF_EAP.

RMobileSmartCardEap::NotifyEapMethodAccessStatusChange() RMobileSmartCardEap::ReleaseEapMethod() RMobileSmartCardEap::InitialiseEapMethod()

TEapUserIdType should be used to request an identity from EF_PUId or EF_Ps, when making an RMobileSmartCardEap::GetUserIdentity() request. (See sections 7.3 and 7.4, respectively, of ETSI TS 102.310 v6.2.0, and RFC2486 - The Network Access Identifier).

RMobileSmartCardEap::GetUserIdentity() RMobileSmartCardEap::TEapUserIdentityV6

A typedef'd packaged TEapKeyV6 for passing through a generic API method.

A typedef'd buffer to hold the EAP type for the subsequent authentication that will be carried out on the Smart Card Application.

The value specified must correspond to the pre-allocated type identifiers for various EAPs (see http://www.iana.org/assignments/eap-numbers ). Some known values are given in etelmm.h.

The type must be specified in hexadecimal format, where each character represents one semi-octet.

KETelSmartCardEapTypeMD5 KETelSmartCardEapTypeTLS KETelSmartCardEapTypeSIM KETelSmartCardEapTypeAKA KETelSmartCardEapTypeTTLS RMobileSmartCardEap::Open()

A typedef'd packaged TEapUserIdentityV6 for passing through a generic API method.

Pointer Holder for the RMobileSmartCardEap sub-session requests.

True if this object is the first to request InitialiseEapMethod() on its <AID,EAPType> when the status is EEapMethodAvailable. I.e. True only for the instance of RMobileSmartCardEap that successfully passes the Wait() on iSemaphore.

Semaphore is actually owned by TSY, and used by all instances of RMobileSmartCardEap to stop multiple access to the same EAP method on any one application.