Sim Guideline Wib 1 3 Equipped Sim Cards PDF

SIM Guideline
Wib 1.3 equipped (U) SIM cards
Document number: 90-294

Revision: 1.6 2011-06-08
© 2011 Giesecke & Devrient 3S AB. Proprietary/Confidential. All rights reserved.

SIM Guideline
Contents
1 Introduction _______________________________________________________ 5
1.1 Target audience .................................................................................... 5
1.2 Purpose of the document ..................................................................... 5
1.3 Abbreviations ........................................................................................ 5
1.4 Terminology .......................................................................................... 6
1.5 References ............................................................................................. 7
2 SmartTrust Certified Wib __________________________________________ 8
3 Wib 1.3____________________________________________________________ 9
3.1 New features ......................................................................................... 9
3.1.1 Downloadable Wib plug-ins ....................................................... 9
3.1.2 Graphics ....................................................................................... 9
3.1.3 Enhanced wait for response state .............................................. 9
3.1.4 Unified menu file structure......................................................... 9
3.1.5 Addressing with script identifier .............................................. 10
3.1.6 Bookmarking ............................................................................. 10
3.1.7 Enhanced variable support ....................................................... 10
3.1.8 Timer management ................................................................... 10
3.2 Wib Plug-ins ........................................................................................ 10
3.2.1 Downloading of the plug-ins.................................................... 11
3.2.2 Keys for the security plug-ins.................................................... 11
3.2.3 Prompt texts .............................................................................. 11
3.2.4 Other plug-in parameters ......................................................... 11
3.3 Icons..................................................................................................... 11
3.3.1 Icons with menu items and bookmarks ................................... 12
3.4 Wib events .......................................................................................... 12
3.4.1 SIM Toolkit events ..................................................................... 12
3.4.2 SIM internal events .................................................................... 12
3.5 Menu ................................................................................................... 13
3.5.1 Menu structure .......................................................................... 13
3.5.2 Size of menu file ........................................................................ 14
3.6 Wib bytecode ...................................................................................... 14
3.7 Wib script ............................................................................................ 15
3.8 Script addressing ................................................................................. 15
3.8.1 Relative addressing mode ......................................................... 15
3.8.2 Absolute addressing mode ....................................................... 15
3.8.3 Wiblet-URI and timer expiration .............................................. 16
3.9 User interface during the server request and response.................... 16
3.9.1 Sending info .............................................................................. 16
3.9.2 Wait-for-response state ............................................................ 16
3.9.3 User alert during the Wait-For-Response state........................ 17
-2-
SIM Guideline
3.10 Message routing information .......................................................... 17

3.10.1 TAR ........................................................................................... 18
3.10.2 SMSC address ........................................................................... 19
3.10.3 Account number ...................................................................... 19
3.11 Transport layer security .................................................................... 19
3.11.1 Security configurations ........................................................... 19
3.12 UDHI support .................................................................................... 20
3.13 Unicode support ............................................................................... 21
3.14 Error handling ................................................................................... 21
3.14.1 Error codes ............................................................................... 21
3.15 Bookmarking..................................................................................... 24
3.15.1 Storing of bookmarks ............................................................. 25
3.15.2 Presentation and navigation .................................................. 25
3.15.3 Management of Bookmarks ................................................... 25
4 G&D SmartTrust solutions _________________________________________ 27

4.1 G&D SmartTrust device management ............................................... 27
5 Ordering Wib equipped (U)SIM cards _______________________________ 28

5.1 Right card type.................................................................................... 28
5.2 Required EEPROM Memory ................................................................ 28
5.3 Other important issues ....................................................................... 29
5.3.1 Wib plug-ins............................................................................... 29
5.3.2 Customer specific Wib events ................................................... 29
5.3.3 Menu titles ................................................................................. 29
5.3.4 Wiblets ....................................................................................... 29
5.3.5 Icons ........................................................................................... 30
5.3.6 Services and solutions ............................................................... 30
5.3.7 Addressing mechanism ............................................................. 30
5.3.8 Wib client server communication ............................................. 30
5.3.9 Error codes ................................................................................. 31
5.3.10 Variable storage space ............................................................ 31
5.3.11 Automatic Refresh ................................................................... 31
6 Wib parameters on the SIM card ___________________________________ 32

6.1 EFTAR 6F1A ............................................................................................ 32
6.1.1 File structure .............................................................................. 32
6.1.2 TAR configurations in different DP version ............................. 33
6.1.3 Recommended values ............................................................... 34
6.2 EFError Text 6F02 ....................................................................................... 34
6.2.1 File structure .............................................................................. 34
6.3 EFBytecode 6F03 ....................................................................................... 36
6.3.1 File structure .............................................................................. 37
6.4 EFSMS Header 6F04, message routing........................................................ 38
-3-
SIM Guideline
6.4.1 File structure .............................................................................. 38

6.5 EFSC 6F1B, Security configuration ....................................................... 39
6.5.1 Coding of 'Counters' ................................................................. 41
6.5.2 Coding of 'Outgoing SPI-Kic-KID' ............................................. 41
6.5.3 Coding of 'Incoming SPI-Kic-KID list' ........................................ 41
6.5.4 Coding of 'Kic key set' .............................................................. 42
6.5.5 Coding of 'KID key set' .............................................................. 43
6.6 EF03.48 Counter 6F06 ................................................................................... 44
6.6.1 File structure .............................................................................. 44
6.7 EFVersion Information 6F07 ............................................................................. 45
6.7.1 File structure .............................................................................. 45
6.7.2 Coding of the manufacturer identifier .................................... 46
6.8 EFWibConfiguration 6F08 ............................................................................... 46
6.8.1 File structure .............................................................................. 46
6.8.2 Recommended value ................................................................. 47
6.9 EFEventConfig 6F0B .................................................................................... 47
6.10 EFText 6F1C .......................................................................................... 49
6.10.1 Defined text fields ................................................................... 51
6.10.2 Recommended values ............................................................. 52
6.11 EFMenu 6F18 ......................................................................................... 53
6.11.1 Recommended value ............................................................... 56
6.12 EFScriptAddress 6F1D ................................................................................. 56
6.12.1 Examples of the EFScriptAddress file usage .................................... 58
6.13 EFMenuTitle 6F1E .................................................................................... 60
6.14 Reserved file identifiers .................................................................... 61
7 OTA functionality _________________________________________________ 62
8 SIM data import __________________________________________________ 63
Annex A - Example profile for Wib 1.3 cards without Unicode

(Informative) ___________________________________________________ 64
Example profile for Wib 1.3 ..................................................................... 66
-4-
SIM Guideline
1 Introduction
1.1 Target audience
This document is meant to be used by G&D SmartTrust
customers to order SmartTrust Wib™ 1.3 equipped (U)SIM
cards.
G&D SmartTrust has specified Wib. The Wib specifications
are meant for SIM vendors only. All information G&D
SmartTrust customers need to know about Wib functionality
and configuration is included in this document and other
G&D SmartTrust Product Specifications.
This document requires some knowledge about the
functionality of SmartTrust Delivery Platform, DP.
Overview of the SmartTrust Delivery Platform is described
in the System Description [1].
1.2 Purpose of the document

Before the operator can order Wib 1.3 equipped (U)SIM
cards there are number of parameters and choices regarding
Wib configurations to be defined.
This document includes generic guidelines about Wib 1.3
specific functions and parameters, like available Wib 1.3
equipped SIM card types, menu structure, configurations of
Wib related plug-ins and other Wib functionality. The
content of this document is informative.
In addition this document specifies the structure of Wib 1.3
related files in section “G&D SmartTrust solutions” on page
27. Recommended values are defined in separate paragraphs
in that section.
This document also includes guidelines for OTA access
conditions of the files on the SIM and introduces the
mechanisms to import SIM related data into the database in
the G&D SmartTrust Delivery Platform.
An example of the coding of all Wib 1.3 related files exists
in Annex A.
1.3 Abbreviations
3DES2 3DES algorithm with 2 keys
DP SmartTrust Delivery Platform
IMSI International Mobile Subscriber Identity
-5-
SIM Guideline
KIc Key and algorithm Identifier for ciphering

KID Key and algorithm Identifier for redundancy check, Cryptographic
Checksum and Digital Signature
MSISDN Mobile Station International ISDN number
OTA Over The Air
PLMN Public Land Mobile Network
RFM Remote File Management
RFU Reserved for Future Use
SPI Security Parameter Indicator
TAR Toolkit Application Reference
UCS2 Universal two byte coded Character Set
UDHI User Data Header Indicator
UTF-8 UCS Transformation Format 8, character set where one character is
defined with 1-6 bytes
Wib SmartTrust Wib™, a SIM based interpreter
WIG Wireless Internet Gateway
WSM Wireless Service Management
1.4 Terminology
Script Synonymous to Wib script
Wib bytecode A compact sequence of Wib commands executed by
Wib
Wib command A Wib bytecode command
Wib command Several Wib commands that logically belong together
sequence and occur one after the other
Wiblet Synonym for Wib script
Wib script A Wib command sequence
-6-
SIM Guideline
1.5 References
[1] System Description - Delivery Platform, doc. no: 90-362
[2] Specification – RFM and RAM Implementation, doc. no: 90-074
[3] Specification - WIG WML v. 5, doc. no: SALC/UG/Spec/09:877776
[4] GSM 03.38, Alphabets and language-specific information, version 7.2.0
[5] GSM 03.40, Technical realization of the SMS-PP, version 7.4.0
[6] 3GPP TS 03.48, SIM Toolkit Secure Messaging, version 8.8.0
[7] GSM 04.11, Point-to-Point short message support on mobile radio
interface, version 7.0.0
[8] 3GPP TS 11.11, Specification of the Subscriber Identity Module – Mobile
Equipment (SIM – ME) interface, version 8.8.0
[9] 3GPP TS 11.14, Specification of the SIM Application Toolkit for the
Subscriber Identity Module – Mobile Equipment (SIM – ME) interface,
version 8.10.0
[10] Developer‟s Guide - Deployment of Wib Services – Wireless Internet
Gateway and Wireless Service Management, doc. no: 90-287
[11] References - Input File Format Specification, SIM Data Import, doc. no:
90-063
[12] Developer‟s Guide - Development of Wib Services - Universal Gateway
and Wireless Service Management, doc. no: 90-291
[13] Standard Event Specification – –SmartTrust Wib™, SmartTrust
[14] Specification - SmartTrust Wib™, Manufacturer Identity Allocation, doc.
no: 90-384
-7-
SIM Guideline
2 SmartTrust Certified Wib

The SmartTrust Certified Program is designed to support
SIM/USIM vendors looking to implement the SmartTrust
Wib™ equipped (U)SIM cards by offering software
developer toolkit, current international specifications,
developer support, testing and final certification.
In order to ensure full interoperability with SmartTrust®
software platforms SmartTrust recommends it’s customers
to select SIM / USIM cards that are SmartTrust Certified™
cards.
The SmartTrust Certified trademark ensures Operator that
the card is tested by a (U)SIM independent party, is
interoperable and of high quality. Operators can easily find
available information online of cards and/or vendors with
certified SIM cards on the G&D SmartTrust official web
page:
http://www.smarttrust.com/support_services/
services_certified_list.asp
Only vendors that have certified (U)SIM cards are permitted
to offer these cards with the SmartTrust Certified
trademark. For all SmartTrust Certified™ cards there is a
test summary available on request from each SIM vendor.
SmartTrust Certified™ (U)SIM card products and versions
are tested individually and identified by order/ article
number and mask version number in a public available list.
-8-
SIM Guideline
3 Wib 1.3
The development of Wib 1.3 services are defined detailed in
Guidelines – Development of Wib Services [12] and WIG
WML Specification – version 4 [3].
3.1 New features

Wib 1.3 includes several new and more advanced features
than earlier Wib versions. New commands and features
supported by Wib 1.3 are defined shortly in this chapter.
The new features are defined more carefully in the WML
specification [3] and/or in this document.
3.1.1 Downloadable Wib plug-ins

It is possible to install and remove downloadable plug-ins in
Wib 1.3. Wib plug-ins can be downloaded Over-The-Air if
downloadable plug-ins are supported on the card.
3.1.2 Graphics
Wib 1.3 has support for graphics through (U)SIM
application toolkit icons as defined in section “Icons” on
page 11.
3.1.3 Enhanced wait for response state

Wib 1.3 includes new possibilities to give user various
status information in between dynamic server request and
response from the Web server. The different status
information is called sending info, intermediate info and
receiving info. It is possible to define a default text in the
(U)SIM and/or define the service specific texts in the wiblet.
It is also possible to switch off the status information. All
status information texts can include icons. This feature is
defined more carefully in section “User interface during the
server request and response” on page 16.
3.1.4 Unified menu file structure

Wib 1.3 introduces a standard menu file format. It means
that the operator does not need to purchase separate (U)SIM
vendor support for their proprietary solution. The unified
menu file structure also provides the possibility to use
absolute addressing, which makes the menu and wiblet
management more efficient in the air-interface.
-9-
SIM Guideline
3.1.5 Addressing with script identifier

Addressing with script identifier gives the possibility for
modular application development and more efficient service
management in Wib 1.3. This feature further optimizes the
application footprint on (U)SIM card and the client/server
communication payload over the air.
3.1.6 Bookmarking
Bookmarking is an optional feature in Wib 1.3. With the
bookmarking feature the end-users can save service
bookmarks on the go when a service is executed and access
them later on from the “MyBookmarks” menu item.
3.1.7 Enhanced variable support

Enhanced variable support offers the possibility to give
variable destination addresses to Setup Call and Send Short
message functionality. It is also possible to execute add and
subtract calculations on variables values.
3.1.8 Timer management

Timer management offers a possibility to build applications
with timers as defined in the WML specification [3].
3.2 Wib Plug-ins

All plug-ins are additional features for standard Wib 1.3.
Plug-ins can be used with all Wib versions. However,
solutions using one or several plug-ins can have
requirements on the used Wib version.
DP 6.1 and later can activated and de-activate plug-ins on
the Wib 1.3 equipped (U)SIM card.
Wib plug-ins can be created by SmartTrust or other parties
like (U)SIM vendors or operators. The support for required
plug-ins needs to be requested from the (U)SIM vendor.
It is possible to define customer specific plug-ins based on
customer requirements. Contact SmartTrust for further
information.
Most of the plug-ins includes parameters and functions to be
defined before the card manufacturing. That information is
defined in the appropriate plug-in specification.
- 10 -
SIM Guideline
3.2.1 Downloading of the plug-ins

It is possible to download plug-ins over the air to Wib 1.3
cards. Downloadable plug-ins is an optional feature in Wib
1.3. If you want to have the possibility to download plug-ins
on Wib cards, please, contact your (U)SIM vendor to ensure
that their Wib 1.3 cards support this feature.
Note that you also have to allocate free memory for the
plug-ins, which will be downloaded to the Wib card after the
card distribution.
All downloaded plug-ins need to be activated on the card
before they can be used by Wib.
3.2.2 Keys for the security plug-ins

Security plug-ins are related to the encryption keys. The
number of keys depends on the used plug-ins and the
customers' needs. If symmetric plug-ins are used, it is
required to have at least one key per content provider. G&D
SmartTrust recommends storing keys for at least 16 content
providers.
Keys are stored in a (U)SIM vendor specific key file. Size of
the key file depends on the number of stored keys and key
type. For example one 3DES2 key is 16 byte long (=2 DES
keys, each 8 byte).
3.2.3 Prompt texts

Several plug-ins have a prompt texts related to the PIN
request or other interaction with the user. Prompt texts have
to be defined as specified in the appropriate plug-in
specification.
3.2.4 Other plug-in parameters

The plug-ins can also have some plug-in specific parameters
to be defined. Those parameters are specified in the
appropriate plug-in specification.
3.3 Icons
It is possible to create graphical user interfaces with Wib 1.3
by using the SIM toolkit icon functionality. The used icons
are stored as images in the EFIMG and Image Instance data
files as defined in 3GPP TS 11.11 [8].
- 11 -
SIM Guideline
Several Wib commands and the menu items have the

possibility to refer to the stored icons as defined in the
WML specification [3] and section “EFMenu 6F18” on page
53.
3.3.1 Icons with menu items and bookmarks

Icon identifier „01‟h is used as a default icon with the menu
items and bookmarks. If at least one menu item has an icon
identifier, any menu item not having an icon identifier
stored is presented in the menu using the default icon
identifier „01‟h. If at least one bookmark entry has an icon
identifier, any bookmark entry not having an icon identifier
stored and the “Remove bookmark” menu item is presented
in the menu using the default icon identifier „01‟h. If not all
icon identifiers are set to be self-explanatory, the icon list
qualifier is set to “not self-explanatory”.
If the icons are planned to be used, it is highly
recommended to define a generic icon with icon identifier
„01‟h for the menu items and bookmarks which do not have
any dedicated icon.
3.4 Wib events

It is possible to start the execution of a Wib script by
different SIM toolkit events, but also by SIM internal
events.
Events are defined in the EFEventConfig file as defined in
section “EFEventConfig 6F0B” on page 47. Event is activated
when Wib script to be executed as a result of the event is
defined in the EFEventConfig file.
3.4.1 SIM Toolkit events

Wib can be triggered by all SIM toolkit events defined in
3GPP TS 11.14 [9]. Wib enables only SIM toolkit events
that are supported by the handset according to the
TERMINAL PROFILE.
Some SIM toolkit events provide additional data, which is
stored in specific variables at start of the event triggered
Wib execution as defined in [12].
3.4.2 SIM internal events

The SIM internal events shall be generated by Wib. In
addition to the Startup event Wib can also support customer
specific events, which are defined outside of this document.
- 12 -
SIM Guideline
Startup event
The startup event is generated after the SIM initialization as
defined in the Wib Event Specification  Start-Up event
[13]. Startup event is used in the G&D SmartTrust‟s device
management solution as defined in section “G&D
SmartTrust device management” on page 27.
Network Available event

The Network Available event is an optional event for Wib
1.3.
The Network Available event is generated when the network
is available after SIM initialization. This is considered to be
the case when calling PROVIDE LOCAL INFORMATION
proactive SIM command with a command qualifier asking
for location information returns a successful TERMINAL
RESPONSE including the location information. The
network available event shall never be generated before the
start-up event. The event supplies the location information
as data.
3.5 Menu
When the mobile is powered on the (U)SIM card collects
the information from Wib menu configuration files and
launches the SET UP MENU toolkit command with the
main menu title, top level menu items if at least one top
level menu item exist on the card.
3.5.1 Menu structure

Menu
Phone book
Messages
.
.
SIM Browser
Fun
Movies
Music
WIB menu
Sport
.
.
- 13 -
SIM Guideline
The main menu title “SIM Browser” can be stored in the

EFMenuTitle file as defined in section “EFMenuTitle 6F1E” on
page 60 or the (U)SIM vendor can have their own
mechanism to store the main menu title.
Top level menu items (Fun, Sport, …) are stored in EFMenu
file as defined in section “EFMenu 6F18” on page 53.
Lower level menu items are stored in EFBytecode file as
defined in Guidelines - Deployment of Wib Services [10].
All submenus, services and the content of the EFBytecode file
are defined with DP before the (U)SIM cards are ordered.
The detailed procedure is defined in Guidelines -
Deployment of Wib Services [10].
With SmartTrust Delivery Platform it is possible to
download, delete and update menu items and services after
the card distribution.
3.5.2 Size of menu file

The size of the menu file depends on
 Maximum number of service items in top level of Wib
menu1
 Maximum length of service titles in top level of Wib
menu
To ensure the scalability of the system in the future it is
good to have some empty top level menu items on the
(U)SIM card. It is recommended to have at least 10 top level
menu item fields in the menu file.
3.6 Wib bytecode

Wib based services are created with the WML and
converted to be a Wib bytecode before sending or storing to
Wib. Bytecodes are stored in the EFBytecode file on the
(U)SIM.
The larger the Bytecode file is, the more wiblets can be
downloaded on Wib card!
The structure of EFBytecode file is defined in section
“EFBytecode 6F03” on page 36.
1
The total size of data in SET UP MENU command is limited, e.g. for an average length of 10 bytes per
text string the maximum amount of items is 18.
- 14 -
SIM Guideline
3.7 Wib script

The maximum size of one Wib script is the size of EFBytecode
file.
SmartTrust Delivery Platform creates a unique script
identifier for all created scripts. The script identifier is used
to address the script from the EFScriptAddress file and to
identify wiblets in SmartTrust Delivery Platform.
All Wib scripts are stored in the EFBytecode file, refer to
section “EFBytecode 6F03” on page 36.
3.8 Script addressing

A script can be addressed by an ordinal or a script identifier
depending on the addressing mechanism.
The addressing mechanism of menu selections and Wib
events depends on the used addressing mode: absolute
addressing or relative addressing. The used addressing mode
file for menu selection and Wib event is configured in the
EFMenu file. It is recommended to use the absolute address
mode for Wib1.3 cards.
Execution of local scripts (with a wiblet-URI as defined in
WIG WML [3]) and timer expiration use script identifier to
address the script to be executed as defined in section
“Wiblet-URI and timer expiration” on page 16.
3.8.1 Relative addressing mode

The item identifier input in menu selection and Wib event is
interpreted as an ordinal of the script in EFBytecode file.
Example:
If a menu item with item identifier 3 is selected the Wib
starts to execute third script in the EFBytecode file.
3.8.2 Absolute addressing mode

The item identifier input in menu selection and Wib event is
interpreted as an ordinal of the script address in EFScriptAddress
file.
EFScriptAddress stores the absolute addresses of all scripts
contained in EFBytecode. The actual address in EFScriptAddress
points to the physical position of each script. The first byte
of the address is most significant. The first byte in the
EFBytecode file is addressed with value „'0000‟h.
- 15 -
SIM Guideline
3.8.3 Wiblet-URI and timer expiration

When a local script is to be executed from another script
(through a Wiblet-URI in WIG WML [3]), a script identifier
is used to point out the script to be executed. Timer
Expiration points to the address defined by the earlier script,
which has set the timer on. Wib checks the absolute address
of the requested script from the EFScriptAddress file and starts
to execute requested script.
3.9 User interface during the server request and response

The purpose of this behaviour is to inform the user that Wib
has sent the server request and it is waiting for the response.
It is also meant to prevent the user from using the menus to
start executing other Wib service while a server response is
expected to be received from the network.
Server request Server response
Sending info intermediate info receiving info

1/4 2/4 3/4 4/4
sending state intermediate state receiving state
waiting-for-response state
3.9.1 Sending info

When the server request is sent to the server the user can be
informed with the sending information. Default sending
information text and/or icon is defined in EFText file.
Wiblet can replace the default text with wiblet specific
sending information. Refer to WML specification [3] for the
details.
3.9.2 Wait-for-response state

As default the wait-for-response state is entered when the
server request is sent to the server with Pull TAR. If Wib
execution is initiated by an event or as a result of timer
expiration, the wait-for-response state is not entered unless
it is separately requested by the wiblet.
It can be defined in the wiblet if the wait-for-response state
is entered or not.
When Wib is in the wait-for-response state it shall block the
user to start other wiblet through menu selections.
- 16 -
SIM Guideline
Intermediate info
The intermediate info is shown to the user after the sending
info until Wib starts to receive the response message. The
default intermediate info text and/or icon are stored in the
EFText file.
Wiblet can replace the default text with a wiblet specific
intermediate info. Refer to WML specification [3] for the
details.
Receiving info
If the incoming server response consists of concatenated
short messages, Wib shall display the receiving info.
The receiving info is shown to the user when Wib is
receiving the server response messages. The default
receiving info text and/or icon is stored in the EFText file.
The receiving info is shown to the user when Wib is
receiving the server response messages. The default
receiving info text and/or icon is stored in the EFText file.
The receiving info can be displayed in fraction mode
“Receiving 1/3” or percentage mode “Received 33%”.
Recommended is to use the percentage mode to display the
receiving info.
3.9.3 User alert during the Wait-For-Response state

If the user tries to start another wiblet through menu
selections during the wait-for-response state Wib alerts the
user and optionally displays a text and/or icon to inform the
user that menu selection is not allowed during the wait-for-
response state. Wib shall after a number of users retries,
specified by the persevere-counter in EFWibConfiguration, exit
the wait-for-response state and again allow menu selections.
The alert information is displayed if the default text and/or
icon is stored in EFText file or a wiblet specific text/and or
icon
3.10 Message routing information

Message routing information is stored in 2 files on the
(U)SIM. EFTAR file includes incoming and outgoing TAR
values and EFSMS Header includes other addressing
information.
- 17 -
SIM Guideline
3.10.1 TAR
In outgoing messages TAR, Toolkit Application Reference,
is used to address DP. In incoming messages TAR is used to
address Wib.
TAR values are defined in the EFTAR file, refer to section

“EFTAR 6F1A” on page 32. At least one TAR value shall be
defined for all different TAR types: pull, push and
administration.
Usage of TAR values

The value of the current TAR depends on the following
issues:
The default pull TAR is used when the server bound
message is sent as a result of executing menu initiated, event
initiated or timer expiration initiated script.
Push TAR is used if a server bound message is sent as a
result of incoming script with a Push TAR.
Admin TAR is used for the administrative purposes.
Wib validates only messages which include a TAR value
defined in the EFTAR file.
Administrative TAR
A separated administrative operation mode, indicated by a
Admin TAR type, is dedicated for the administrative
purposes.
Administrative mode enables an entity with administrator
privileges to perform tasks like adding new plug-ins and
perform menu management.
Relation between the used TAR value and security configuration

A security configuration shall be configured for each TAR
as defined in section “Supported security levels” on page 19.
In DP5 the used security level is combined to the TAR
value, thus different security levels used in the DP have to
have separate TAR values.
In DP6 the security settings are specified per card profile,
i.e. cards belonging to different card profiles may have the
same TAR but different security settings.
It is not possible to configure admin TAR to operate without
any security (with security level L0 as defined in section
“Supported security levels” on page 19).
- 18 -
SIM Guideline
3.10.2 SMSC address

SMSC number to be used by Wib shall be defined in the
EFSMS Header file, refer to section “EFSMS Header 6F04, message
routing” on page 38.
The SMSC address defined for Wib should be differentiated
from the regular SMSC address to ensure the easy
installation for future expansions (For example, use a
dedicated SMSC for the Wib traffic or use the SmartTrust
DP High Speed Messaging Package), without having to
change the SMSC address on the (U)SIM cards.
3.10.3 Account number

Account number is used to address the Delivery Platform.
Account number is the destination address in the short
message. It is needed to define the used account number in
EFSMS Header file, refer to section EFSMS Header 6F04, message
routing.
3.11 Transport layer security
3.11.1 Security configurations

Wib uses 3GPP TS 03.48 security in the transport layer as
defined in 3GPP 03.48 [6]. The used security level (SPI,
KIC and KID), algorithm and counter, needs to be defined
for all incoming and outgoing messages of each TAR value.
Wib 1.3 can use separate counters for incoming messages
and outgoing messages. The counter values are stored in
EF03.48 Counter file. The sequence number counting must be
activated in SPI field of the appropriate security
configuration.
Wib 1.3 uses key sets containing up to 16 keys for the
ciphering and integrity/authentication keys. Key sets are
addressed with the KIc and KID [6].
Supported security levels

Wib 1.3 supports following 03.48 security levels[6]:
Level SPI KIc KID Description

L3 16 x5 y0 Replay protection: Counter greater
00 Authentication: ISO/IEC 9797 Algorithm 4, padding
method 3
Ciphering: Triple DES
- 19 -
SIM Guideline
This security level ensures protection against replay and

interleaving attacks as well as message authentication and
message confidentiality.
L2 15 x5 00 Replay protection: Counter greater
00 Authentication: CRC32
Ciphering: Triple DES

interleaving attacks as well as message authentication and
message confidentiality.
L1 12 x7 y3 Replay protection: Counter greater
00 Authentication: MAC derived from ISO/IEC 9797
Algorithm 3, padding method 1
Ciphering: None

interleaving attacks as well as message authentication.
L0 00 00 00 Replay protection: None
00 Authentication: None
Ciphering: None
This security level should be used for testing only, since it

provides no protection whatsoever.
The most significant nibble of KIc, denoted x, is the KIc

index and refers to a key in the ciphering key set. Similarly,
the most significant nibble of KID, denoted y, is the KID
index and refers to a key in the authentication key set.
L3 security level is only supported by DP6.
3.12 UDHI support

UDHI bit in the short message header is used to define that
the user data header exists in the short message. Some
(U)SIM vendors ask how UDHI should be configured on the
(U)SIM. As default the UDHI bit shall be set to „true‟ in
Wib cards.
If SMSC does not support short messages where the User
Data Header is indicated, it might be possible to set the
UDHI bit to „false‟ on Wib cards, to make the SMSC deliver
the messages without problems.
- 20 -
SIM Guideline
3.13 Unicode support

UCS2 is the Unicode nomenclature type, which is used in
(U)SIM cards and GSM mobiles. Wib 1.3 supports UCS2 as
default in addition to the 7-bit GSM default alphabet
characters as specified in GSM TS 03.38 [4].
3.14 Error handling

If an error occurs the Wib displays an error message for the
user and exists. In addition to the error text the error
message can also include detailed error information, if so
configured.
The detailed error information includes an error code, Wib
command tag and terminal Response general result value or
file identifier depending of the happened error.
The error codes are defined in section “Error codes” below.
Wib Command is the function Wib was executing when
error occurred. Terminal response general result value is
displayed if a proactive SIM command caused the error.
When Wib failed to access file, the file identifier of the file
that could not be accessed is given.
It is possible to define a generic error text (error code „DF‟)
that replaces the error texts which are not defined separately
in the EFErrorText file. The detailed error information can be
displayed with the generic error text.
Possible error codes are defined in the table below. The
error code is displayed using hexadecimal formatting.
3.14.1 Error codes
File access errors
Error code Error text (Example) Comments

(range 1-1F)
'01'h Failed to find/read EFBytecode
'02'h Failed to find/read EFTAR
'03'h Failed to access/read EFErrorText
'04'h Failed to find/read EFSMSHeader
'05'h Failed to read key file
'06'h Failed to find/read
EFVersionInformation
'1F'h Failed to access file
- 21 -
SIM Guideline
Wib command errors

(range 20-
3F)
'20'h Unknown Wib command found
'21'h Variable substitution failed
'23'h Out of variable memory
'25'h SMS TPDU Tag in incoming
SMS not found
'26'h Creation of SELECT ITEM Error code '33' can be used
failed instead of this error code
'27'h Encryption/decryption failed
'28'h Out of buffer space
'29'h Plug-in not found The called plug-in does not
exist on the (U)SIM card or
the name of the plug-in is
wrong
'2A'h Bad format on proactive SIM Error code '40' or '46' can be
command used instead of this error code
'2B'h “Goto” out of bounds Skip, Select Item, Check
Terminal Profile or Branch
on variable value is pointing
outside the current script.
'2C'h E2PROM memory problem
'2D'h Command error in client bound This error code can be
message replaced with other error
codes
'2E'h Configuration error
'2F'h Set Return TAR Value Application tries to change
not allowed from Pull or Push TAR to the
Admin TAR. Or the target
TAR is not defined in EFTAR.
'30'h Script not found
'31'h Timer management failure.
'32'h Return from script not allowed
'33'h Invalid input data to Wib
command
'34'h Invalid incoming message An error occurs in the 03.48
message processing.
- 22 -
SIM Guideline
ME errors

(range 40-
5F)
'40'h Proactive SIM command The following result codes in
rejected by ME TERMINAL RESPONSE:
'31, '32', '33', '34', '35', '36',
'37' and '39'.
'41'h Wrong type of command Wib expected a terminal
returned by ME in terminal response for another
response command type
'42'h Get Input did not return a string
'43'h No item identifier was returned
by ME in the terminal response
to a Select Item
'44'h Temporary error occurred in ME returned a temporary
application. Please try again error. The following result
later. codes in TERMINAL
RESPONSE: '20', '21', '25'
and '26'.
'45'h Error in format of received SM
'46'h Command not supported by the The following result code in
mobile TERMINAL RESPONSE:
'30' or the command type is
not defined in TERMINAL
PROFILE.
Plug-in errors
Error code
(range 60-
7F)
'60'h Invalid input parameter(s)
'61'h Input out of bounds
'62'h Output overflow
'63'h RSA error
'64'h Illegal operation
'65'h Integrity error
'66'h PIN length error
- 23 -
SIM Guideline
3.14.1.1 Default errors
'DF'h Error in application occurred. User friendly error text

Please call support.
3.14.1.2 Proprietary errors

(U)SIM vendors proprietary error codes may be added in the
„E0‟h-„FF‟h series.
3.15 Bookmarking
The bookmarking feature provides a way of storing the
wiblet bookmarks. Wiblet bookmarks are similar to the
bookmarks in the internet browsers.
Bookmarking is an optional feature in Wib 1.3. It is
configured in the EFMenu file weather the bookmarking
feature is available for the end user or not. The stored
bookmarks are available for the user in Wib menu. The
bookmarks are stored in a separate memory area. The size of
bookmarks memory area is defined by the operator. The size
of one bookmark can be up to 512 bytes, but normally one
bookmark requires much less memory. All Wib 1.3 cards,
that support the bookmarking feature, are able to support at
least 1.5kB memory area for the bookmarks. Larger
bookmarking storage can be requested from the (U)SIM
vendor.
Following bookmarking related text strings are configurable
and stored in EFText file.
Tag Purpose Example

Text controls the name that the “My Bookmarks”
'02'h
bookmark feature has in the menu.
Text controls the question that Wib “Do you want to store this
'03'h asks the user to find out if the as a bookmark?”
current data is bookmarked.
Text controls the name that the “Name of bookmark?”
'04'h
bookmark is stored under.
Text controls the name that the “Remove bookmark”
'05'h
remove bookmark list item has.
Text controls the text to be “Error – bookmark cannot
'06'h displayed to the end-user when a be stored”
bookmark cannot be stored.
Text for a positive answer “Store”
'07'
alternative in a selection.
- 24 -
SIM Guideline
Text for a negative answer “Don‟t store”

'08'
alternative in a selection.
Text that is displayed when “Bookmark name already
attempting to store a new bookmark exists. Please choose
'0C'h
with the same name as an existing another one.”
one.
3.15.1 Storing of bookmarks

The possibility for bookmarking is indicated in the wiblet.
Only the server requests to be sent to the server can be
bookmarked.
If bookmarking is enabled and bookmark is not already
stored, Wib asks, using the storage-query-string, if the user
wishes to store it as a bookmark. The user is presented with
two options “Store”/”Don‟t store”. If the answer is “Store”,
Wib prompts the user for a name to store the data under.
If the name for the new entry is already in use, Wib informs
the user and thereafter prompts the user for a new name.
Thereafter Wib stores the bookmark to the bookmark
storage.
If the size of the bookmark to store is larger than the free
space in the bookmark storage, an error message is
displayed to the end-user.
3.15.2 Presentation and navigation

“Bookmark” menu entry is in the end of Wib Menu. The
name of the menu entry is stored in the EFText file. When the
menu entry is selected, Wib presents the stored bookmarks
in a list for the end-user to select one of them.
If none of bookmark entries have an icon identifier stored,
no icons is used in the presentation of this list. If at least one
bookmark entry has an icon identifier, any bookmark entry
not having an icon identifier stored and the remove
bookmark item is presented in the menu using the default
icon identifier '01'h. If not all icons of the menu entries are
self-explanatory, the icon list qualifier is set to “not self-
explanatory”.
3.15.3 Management of Bookmarks

Wib provides an interface for the end-user to remove
bookmarked data in an easy and user-friendly way.
- 25 -
SIM Guideline
Remove bookmark menu item exists in the last position of

the bookmark list in the menu. The name of the menu item
is stored in EFText file.
When the remove bookmark item has been selected, Wib
presents the stored bookmarks in a list for the end-user to
select one of them to be removed. The presentation of icons
in this list is the same as in the list including the remove
bookmark item.
The bookmark selected in the list is removed from the
bookmark storage and the space is freed.
- 26 -
SIM Guideline
4 G&D SmartTrust solutions

Some G&D SmartTrust solutions have requirements on the
used card type. It is important to identify even the future
needs before ordering the (U)SIM cards.
4.1 G&D SmartTrust device management

G&D SmartTrust has developed a (U)SIM based device
management solution. To be able to use the device
management solution the *PAD plug-in must exist on the
Wib 1.3 card. In addition the startup event shall be activated
to call device management wiblet.
The PAD plug-in shall have at least 200 bytes memory in
the PAD area to be used by G&D SmartTrust device
management solution. It is recommended to reserve at least
500 bytes PAD area to be used by PAD plug-in.
G&D SmartTrust provides the device management wiblet
together with other device management components
- 27 -
SIM Guideline
5 Ordering Wib equipped (U)SIM cards
5.1 Right card type

The available features and implementations varies a lot
between different (U)SIM vendors and their products. For
example the usage of the EEPROM memory depends on the
implementations. In most of the cases all EEPROM memory
is not available for the operators usage. The (U)SIM vendors
can also use part of the EEPROM memory to implement
additional features and functions for the (U)SIM card.
Earlier it was typical that the operator decided the used
(U)SIM card type based on the size of EEPROM and card
price.
Nowadays it is much more complex to find the most suitable
card type. Therefore the operator should list all their (U)SIM
card requirements and ask the (U)SIM vendor to offer the
suitable (U)SIM platforms with technical descriptions and
price lists. Based on all that information the operator can
select the most suitable (U)SIM card for their purposes.
5.2 Required EEPROM Memory

The required EEPROM memory amount on the SIM
depends on the operator‟s needs and the SIM vendors‟
implementations. For example, if Wib implementation is in
the EEPROM memory it is required to have more EEPROM
memory on the card than if Wib is implemented in the
ROM. To get an exact figure of the card implementation,
contact a (U)SIM vendor of your choice.
The required EEPROM memory on the SIM can be counted
roughly as below:
 GSM application
– 3k GSM network parameters.
– 5-20k phone book, service dialing numbers, short
messages and other corresponding data.
 Wib implementation
–Wib functionality if not implemented in ROM (size
depends of SIM vendor).
–Wib parameters 1-2k, refer to section “Wib parameters
on the SIM card” on page 32.
–Bytecode file 8-12k for services without Unicode and
20-32k for Unicode services.
- 28 -
SIM Guideline
 Required plug-ins, refer to section “Wib Plug-ins” on

page 10.
–plug-in functionality if not implemented in ROM (size
depends of SIM vendor).
–plug-in related files, see appropriate plug-in
specification.
The recommendation is to have at least 32k – 64k EEPROM
memory on the SIM card for the above listed features. For
cards with many Unicode services the recommendation is to
have at least 64k EEPROM memory.
5.3 Other important issues
5.3.1 Wib plug-ins

Wib plug-ins are additional features in Wib 1.3 as defined in
section “Wib Plug-ins” on page 10. The support for Wib
plug-ins can be requested from the (U)SIM vendor.
5.3.2 Customer specific Wib events

It is possible to have customer specific Wib events as
defined in section “Wib events” on page 12. The support for
customer specific events can be requested from the (U)SIM
card vendor.
5.3.3 Menu titles

It is important to define the number of possible top level
menu items in the EFMenu file and the size of EFBytecode file as
defined in sections “Network Available event” on page 13
and “Wib bytecode” on page 14.
In addition the menu title of the main menu must be defined.
5.3.4 Wiblets
The wiblets to be stored on the card shall be defined
according to Guidelines - Deployment of Wib Services [10]
before ordering cards.
It is important to define enough large EFBytecode file for the
wiblets to be stored on the card.
It is also important to be able to address all wiblets in the
EFBytecode file. The EFScriptAddress file should include memory
for all needed Script Addresses.
- 29 -
SIM Guideline
5.3.5 Icons
The icon related files EFIMG and Image Instance data files
must be defined on the (U)SIM card that it is possible to use
the icons. Each icon is stored in an own Image Instance data
file.
If icons are downloaded over-the-air, EFIMG and Image
Instance data files shall already exist on the card.
It is important to ensure that the EFIMG file has enough many
records and Image Instance data files are enough big for the
icons to be downloaded.
Note that icon identifier „01‟h is used as default icon for the
menu items and bookmarks as defined in section “Icons
with menu items and bookmarks” on page 12.
5.3.6 Services and solutions

Services and solutions might have requirements on the used
Wib version, plug-ins, Wib events and other features. It is
very important to identify those requirements before
selecting the used card type.
5.3.7 Addressing mechanism

The selected addressing mechanism has impacts on the
efficiency of the menu and wiblet management over-the-air.
The absolute addressing mechanism saves the amount of
short messages when downloading and deleting the wiblets
on the WIG equipped (U)SIM card.
DP 6.1 or later is required when using absolute addressing
mode.
5.3.8 Wib client server communication

Short messages are used to transport data between Wib and
SmartTrust Delivery platform.
Wib 1.3 supports concatenated short messages in both
directions. Wib shall be able to handle at least five
concatenated short message from Wib to the network and
Wib shall be able to receive at least seven concatenated
short messages.
It is possible to request even longer concatenated messages
from the (U)SIM vendor.
- 30 -
SIM Guideline
The amount of supported concatenated short messages is a

configurable value in the SmartTrust Delivery Platform. The
supported length of the concatenated messages is defined in
the SIM data import file as defined in section “SIM data
import” on page 63 and in the Import File Format
Specification [11].
5.3.9 Error codes

Select the specific error codes to be displayed for the user.
The generic error code with tag 'DF'h can be displayed with
all other error cases.
5.3.10 Variable storage space

The minimum size of the variable storage is 1000 bytes, but
even larger variable storage can be requested from the
(U)SIM vendor.
5.3.11 Automatic Refresh

Some cards support Automatic Refresh functionality after
an Over-The-Air download. That function may disturb large
OTA downloads like WSM downloads (downloads of Wib
services). Therefore G&D SmartTrust recommends not
setting on the Automatic Refresh functionality on the card.
It is much better that the SmartTrust Delivery Platform
sends a Refresh command after the last update message. All
cards supporting 03.48 RFM protocol support that Refresh
form.
- 31 -
SIM Guideline
6 Wib parameters on the SIM card

A number of files are used to define the behavior of Wib.
Files used by Wib are defined in this chapter. The files are
stored in the DF2700 directory under the Master File, MF.
This chapter describes how Wib specific files are used by
Wib and how the files should be configured to work with
the G&D SmartTrust products. All plug-in specific files are
defined in the appropriate plug-in specification.
There are several ways to configure Wib related files. G&D
SmartTrust has made some recommendations for some of
the parameters. Recommended values are defined in a
separate section under the appropriate file.
There are several ways to configure Wib related files.
G&D SmartTrust has made some recommendations for
some of the parameters. Recommended values are defined
in a separate chapter under the appropriate file.
6.1 EFTAR 6F1A

The EFTAR file contains at least 3 TAR values. Incoming
messages that does not contain TAR value listed in any of
the records of this file are discarded.
Records 1, 2 and 3 of this file shall always contain a Pull, a
Push and an Admin TAR, in that order. They are referred to
as the „default‟ entries for the specific TAR type.
Each used record shall have a unique TAR value.
6.1.1 File structure

Identifier: '6F1A' Structure: linear fixed Mandatory
Record length : 5 bytes Update activity: low
Access Conditions:
READ ADM
UPDATE ADM
INVALIDATE ADM
REHABILITATE ADM
Bytes Description M/ Length

O
1 TAR type M 1 byte
2-4 TAR value M 3 bytes
5 SC index M 1 byte
- 32 -
SIM Guideline
Coding:
Field Contents Coding

TAR type As explained in section '00'h = Pull
“EFTAR 6F1A” on page 32. '01'h = Push
'02'h = Administration
'03'h … 'FF'h = RFU
TAR value Toolkit Application As defined in 3GPP
Reference. TS 03.48 [6]
SC index Index of related SC '01'h refers to the first
contained in EFSC SC, '02'h to the
second, and so on.
It is possible to configure at least 48 different TAR values

for Wib 1.3 if required.
Not used records are coded with 'FF…FF'.
6.1.2 TAR configurations in different DP version

In DP 5 is it possible to configure other TAR values than the
default values, but the values need to be same for all SIM
cards managed by the SmartTrust Delivery Platform.
In DP 6 it is possible to configure different TAR values for
different card profiles. TAR values are configured in the
SIM data Import file [11].
As default DP 5 and 6.0 are configured with following
values:
'00 00 01'h for Pull TAR
'00 00 02'h for Push TAR
As default DP 6.1 and later is configured with following
values:
'BF FF 01'h for Pull TAR
'BF FF 02'h for Push TAR
Note 1: It is possible to use other TAR values as well, but in
that case SmartTrust Delivery Platform requires to be re-
configured to support those values instead of the default.
Note 2: When SmartTrust Delivery Platform is upgraded the
old TAR values are used in the new system automatically.
- 33 -
SIM Guideline
Admin TAR is not yet used by the SmartTrust Delivery

Platform.
6.1.3 Recommended values

Following TAR values are recommended for different TAR
types:
'BF FF 01'h for Pull TAR
'BF FF 02'h for Push TAR
'BF FF 03'h for Admin TAR
Admin TAR is not yet used by SmartTrust Delivery
platform, but it needs to be configured on the card for the
future usage.
It is important to ensure that the operator has allocated the
same TAR values in different cards for same purposes!
It is recommended to configure some empty records in
EFTAR file for TAR values which are possible downloaded
over-the-air later.
6.2 EFError Text 6F02

If an error occurs when Wib is executing a bytecode string,
the error message is displayed to the user as defined in
section “Error handling” on page 21. All error messages to
be displayed for the user are stored in the EFError Text file. The
error messages include an error text and possible detailed
error information.
If the error message exists with length zero, the error
message is not displayed by Wib.
To be able to reconfigure the system the OTA access
conditions of EFTAR file should be set to “OTA updateable”.

Identifier: '6F02' Structure: transparent Mandatory
File size: X bytes Update activity: low
Access Conditions:
READ ADM
UPDATE ADM
INVALIDATE ADM
REHABILITATE ADM
O
- 34 -
SIM Guideline
1 to A Error #1 M A
A+1 to Error #2 M B
A+B
: : : :
A+…+1 to Error #n M N
A+…+N
A+…+N+ End mark value '00'h M 1
1
A+…Z+1 Padding ('FF'…'FF') O Z
Coding of each error field:
Field Contents Coding Length

Length Length of the 2+X 1
following bytes
Error Code According to section 1
“Error codes” on
page 21.
DCS Data Coding According to GSM 1
Scheme 03.38 [4] .
Error Message Displayed error According to the X
message in case of Data Coding
an error. Scheme.
At least the generic error message with error code 'DF' shall
be defined in this file, unless all individual error codes used
by Wib implementation are defined.
Error message consist of an error text and detailed error
information, if included.
Detailed error information is included into the error message
with escape sequence "%D". To be able to use the actual '%'
in its original form it must be preceded with an extra '%', i.e.
"%%".
Detailed error information is displayed as a string of
hexadecimal numbers on the form “ErrorCode
WibCommand TerminalResponse/FileIdentifier”. Wib
command defines the function Wib was executing when
error happened. Terminal Response is displayed if the error
happened during executing a proactive SIM command and
File Identifier is displayed if Wib failed to access file.
Example 1:
- 35 -
SIM Guideline
Wib tries to send an outgoing message, but the request is

rejected by the ME. If the error text in EFErrorText is “Failed
to connect to the network: %D”, Wib displays “Failed to
connect to the network: 40 01 21” to the user. In that string,
40 means proactive SIM command rejected by ME, 01 is
Wib command tag for an outgoing message sending and 21
is a TERMINAL RESPONSE general result received from
ME.
Example 2:
Wib executes an incorrect script addressing. If the error text
in EFErrorText is “Script not found %D”, Wib displays “Script
not found 1A 30” to the user.
Example 3:
Wib tries to access the file 2700/6FA3 that is not on the card
and it is not connected to a specific Wib command. If the
error text in EFErrorText is “File access failure. %D”, Wib
displays “File access failure. 1F XX 2700/6FA3” to the
user.

The minimum size of the error file with generic text is
recommended to be at least 100 bytes without Unicode text
and 200 bytes with Unicode text. The file size must be
increased if error specific texts are defined in the file.
It is recommended to select which specific error texts are
displayed for the user. Most of the specific error texts can be
replaced with the generic error text with code 'DF'h.
It is recommended to use error texts defined in section
“Error codes” on page 21 or translations of defined error
texts in required language.
When generic error code 'DF'h is used, it is recommended to
use detailed error information. Otherwise it is not possible to
find out what caused the error.
The generic error message can be coded as “Error %D” for
example.
To be able to update the error codes later, the OTA access
condition for EFErrorText file shall be set to “OTA
updateable”.
6.3 EFBytecode 6F03

EFBytecode file contains all scripts that may be run by Wib
when the user selects a menu item in the Wib menu.
- 36 -
SIM Guideline
If predefined wiblets are stored in the SIM card during the

personalization, the content of the Bytecode file is created
with the WSM bytecode generator as defined in the
Guidelines - Deployment of Wib Services [10].

This file contains locally stored scripts that may be run by
Wib.
Identifier: '6F03' Structure: transparent Mandatory

File size: Z bytes Update activity: low
Access Conditions:
READ ADM
UPDATE ADM
INVALIDATE ADM
REHABILITATE ADM

O
1 to Z Bytecode M Z
The content of the bytecode file is created according to

Empty file is coded as „FF…FF‟.

The minimum size of the bytecode file is recommended to
be 8-12 kB without Unicode services and 20-32kB with
Unicode services.
It is recommended to store wiblets on the SIM during the
personalization. It is highly recommended to have some
empty space in the file for new wiblets to be downloaded
afterwards.
To be able to download new wiblets to the SIM the OTA
access condition for the bytecode file and menu file(s) must
be set to “OTA updateable”.
- 37 -
SIM Guideline
6.4 EFSMS Header 6F04, message routing

Routing related information, like SMSC number and
account number for a server request, is stored in EFSMS Header
6F04.
When Wib is sending a request to the server there are some
SMS parameters required for the message to reach the
server. Those are defined in this file.

This file continues the SMS header to be used with the
outgoing messages.
Identifier: '6F04' Structure: linear fixed Mandatory

Record length: 27 bytes Update activity: low
Access Conditions:
READ ADM
UPDATE ADM
INVALIDATE ADM
REHABILITATE ADM

O
1 to 12 TP-Destination Address M 12 bytes
13 to 24 TS-Service Centre Address M 12 bytes
25 TP-Protocol Identifier M 1 byte
26 TP-Data Coding Scheme M 1 byte
27 TP-Validity Period M 1 byte
Coding:

TP-Destination As defined for SM-TL address Unused nibbles are set
Address fields in GSM TS 03.40 [5] . to F.
TS-Server As defined for RP-Destination Unused nibbles are set
Centre Address address Centre Address in to F.
GSM TS 04.11 [7].
TP-Protocol Protocol Identifier As defined in
Identifier GSM TS 03.40 [5]
- 38 -
SIM Guideline
TP-Data Coding Data Coding Scheme As defined in

Scheme GSM TS 03.38 [4]
TP-Validity As defined [5] for the relative As defined in
Period time format. GSM TS 03.40 [5]
Only one record is used in EFSMS Header file.

PID and DCS can get several values, for example:
PID „00‟h
DCS „F6‟h 8 bit data
Recommended validity period is 1-2 hours, from „0B‟h to
„17‟h.
To ensure the flexibility of the card in the future it is
recommended to set the OTA access condition for EFSMS
Header to “OTA updateable”.
6.5 EFSC 6F1B, Security configuration

The communication security between Wib and WIG relies
on the standard 3GPP TS 03.48 [6]. All transport security
related issues (except counters and keys) are defined in this
file.
Parameters in this file are used when Wib creates outgoing
messages and validates the security configurations of the
incoming message.
Since the card implementation has some impacts on the
coding of this file it is best to configure this file together
with the (U)SIM vendor of your choice.
Identifier: '6F1B' Structure: transparent Mandatory

File size: A+B+…+N+X bytes Update activity: low
Access Conditions:
READ ADM
UPDATE ADM
INVALIDATE ADM
REHABILITATE ADM

O
- 39 -
SIM Guideline
1 to A SC #1 M A
A+1 to A+B SC #2 M B
… … M …
A+B+…+1 SC #n M N
to
A+…+N
A+B+…+N+ End mark M 1
1
The end mark is coded 'FF'h. The file contents after the end
mark is undefined.
Each SC shall be coded according to:

Tag Tag matching the '30'h 1
BER encoding of
the tag of the
SEQUENCE
ASN.1 type.
Length of SC The length of 10+A+B+C+D 1
following fields
(including padding)
Counters Reference to According to section 4
counters for “Coding of
incoming and 'Counters'” on page
outgoing messages. 41.
Outgoing SPI- SPI-Kic-KID to be According to section 6
Kic-KID used in outgoing “Coding of
GSM 03.48 'Outgoing SPI-Kic-
messages. KID'” on page 41.
Incoming SPI- List of acceptable According to section A
Kic-KID list SPI-Kic-KID “Coding of
combinations for 'Incoming SPI-Kic-
incoming KID list'” on page
messages. 41.
Kic key set References to Kic According to section B='02'h…'
keys. “Coding of 'Kic key 22'h
set'” on page 42.
- 40 -
SIM Guideline
KID key set References to KID According to section C='02'h…'

keys. “Coding of 'KID key 22'h
set'” on page 43.
Padding Optional padding. 'FF FF … FF', as D
many as necessary.
6.5.1 Coding of 'Counters'

Tag '80'h 1
Length '02'h 1
Outgoing Ref. to the The ref. is a record 1
counter outgoing message ID, pointing to a
counter. record in
EF03.48Counter
Incoming Ref. to the The ref. is a record 1
counter incoming message ID, pointing to a
counter. record in
EF03.48Counter.
6.5.2 Coding of 'Outgoing SPI-Kic-KID'

Tag '81'h 1
Length '04'h 1
SPI The SPI bytes. Coding according to 2
3GPP TS 03.48 [6]
chapter 5.1.1.
Kic The Kic byte. Coding according to 1
3GPP TS 03.48 [6]
chapter 5.1.2.
KID The KID byte. Coding according to 1
[6] 3GPP TS 03.48
chapter 5.1.3.
6.5.3 Coding of 'Incoming SPI-Kic-KID list'

Tag '82'h 1
Length Total length of all 4*k 1
value bytes.
SPI-Kic-KID Coded as defined 4
entry #0 below.
- 41 -
SIM Guideline

entry #1 below.
: : : :
entry #k below.
Each 'SPI-Kic-KID entry' in the list shall be coded

according to:

SPI The SPI bytes. Coding according to 2
3GPP TS 03.48 [6]
chapter 5.1.1.
Kic The Kic byte. Coding according to 1
3GPP TS 03.48 [6]
chapter 5.1.2. High
nibble is to be
ignored.
KID The KID byte. Coding according to 1
3GPP TS 03.48 [6]
chapter 5.1.3. High
nibble is to be
ignored.
6.5.4 Coding of 'Kic key set'

Tag '83'h 1
Length Total length of the 2*m 1
following fields.
Kic #1 Kic index of key #1 Value in range '00'h 1
to '0F'h.
Key ref. #1 Kic key reference 1
#1, pointing to the
key in the key file.
Kic #2 Kic index of key Value in range '00'h 1
#2. to '0F'h.
Key ref. #2 Kic key reference 1
#2, pointing to the
: : : :
- 42 -
SIM Guideline
Kic #m (Note) Kic index of key Value in range '00'h 1

#m to '0F'h.
Key ref. #m Kic key reference (U)SIM vendor 1
#m, pointing to the specific
Note: m is less than or equal to 16
The value part does not have to contain more Kic/key

reference Pairs than need. The length must always reflect
the true length of the value-list.
6.5.5 Coding of 'KID key set'

Tag '84'h 1
Length Total length of 2*p 1
following fields.
KID #1 KID index of key Value in range '00'h 1
#1 to '0F'h.
Key ref. #1 KID key reference 1
#1, pointing to the
KID #2 KID index of key Value in range '00'h 1
#2. to '0F'h.
Key ref. #2 KID key reference 1
#2, pointing to the
: : : :
KID #p (Note) KID index of key Value in range '00'h 1
#p to '0F'h.
Key ref. #p KID key reference (U)SIM vendor 1
#p, pointing to the specific.
Note: p is less than or equal to 16
The value part does not have to contain more KID/key

reference Pairs than needed. The length must always reflect
the true length of the value-list.

G&D SmartTrust recommends selecting one of the security
- 43 -
SIM Guideline
levels L1-L3 for incoming and outgoing messaging as

defined in section “Supported security levels” on page 19.
It is recommended to think if it is required to be able to
update the security configuration information over-the-air. If
yes, the OTA access condition for EFSC file shall be set to
“OTA updateable”.
6.6 EF03.48 Counter 6F06

This file contains all counters required by the security
configurations.

Record length: 5 bytes Update activity: High
Access Conditions:
READ ADM
UPDATE ADM
INVALIDATE ADM
REHABILITATE ADM

O
1 to 5 Counter (CNTR) M 5 bytes
Coding of counter:

CNTR Counter As defined in 3GPP
03.48 [6].

It is recommended to define following counter start values:
'00 00 00 00 01'h for outgoing messages
'00 00 00 00 00'h for incoming messages.
The minimum amount of the records/counters in the EF03.48
Counter file depends on the security configurations in the EFSC
file.
It is not recommended to update the counter information
- 44 -
SIM Guideline
over-the-air.
6.7 EFVersion Information 6F07

The version information file contains Wib version as well as
information of the plug-ins on the card.

Identifier: '6F07' Structure: transparent Optional
File size: X bytes, X>=5 Update activity: low
Access Conditions:
READ ADM
UPDATE ADM
INVALIDATE ADM
REHABILITATE ADM

O
1 Manufacturer identifier M 1
2-4 Wib version number M 3
5 Number of following plug-in entries M 1
6 to A+5 Plug-in #1 O A
6+A to Plug-in #2 O B
5+A+B
: : : :
6+…+N to Plug-in #n O N
5+A+…+N
6+A+…+N Padding bytes ('FF'…'FF'h) O Y
to
5+A+…N+Y
Manufacturer identifier is defined in section “Coding of the

manufacturer identifier” on page 46.
Coding of Wib version number:

Main version First number of Hexadecimal 1
Wib version
- 45 -
SIM Guideline
Sub-version Second number of Hexadecimal 1

Wib version
Manufacturer Manufacturer Proprietary 1
specific Wib specific Wib
version version
For example Wib 1.3 shall be coded 01 03 01, when the

manufacturer specific version is '01'h.
Coding of the plug-in field:

Length Length of the plug- Length (X) 1
in name
Plug-in name Plug-in name used According to X
in the Plug-In Wib appropriate plug-in
command specification
Plug-in version Manufacturer Manufacturer 3
specific plug-in specific coding
version
6.7.2 Coding of the manufacturer identifier

Please refer to [14] for coding of manufacturer identifier.

Since Wib 1.3 can support downloadable plug-ins it is
recommended to allocate enough memory for the
information of all later downloaded plug-ins.
Since Wib 1.3 can support downloadable plug-ins it is
recommended to allocate enough memory for the
information of all later downloaded plug-ins.
6.8 EFWibConfiguration 6F08

This file is used to define Wib configurations.

Identifier: '6F08' Structure: Transparent Mandatory
File size: X bytes, X>=1 Update activity: low
Access Conditions:
READ ADM
- 46 -
SIM Guideline
UPDATE ADM
INVALIDATE ADM
REHABILITATE ADM

O
1 Persevere counter initial value M 1
Coding:

Persevere Number of user Hexadecimal 1
counter initial alerts before Wib number.
value exits the wait for
response state.
When Wib is in the wait-for-response state and waiting for a

response from the WIG server and the user tries to start
Wib, a warning tone is issued by Wib. If the user retries
starting Wib a few times, the selection is finally accepted.
This counter indicates how many times a tone is played
before Wib exits the wait-for-response state. If counter is set
to '00' the function is disabled, if '01', Wib is started on the
second attempt etc.
With the alert tone it is also possible to display an alpha
identifier for the user. The alpha identifier to be displayed is
defined in EFText file.
6.8.2 Recommended value

The persevere counter is often set to 3 ('03'h).
To be able to update the persevere counter over-the-air, the
OTA access condition for EFWibConfiguration file shall be set to
6.9 EFEventConfig 6F0B

This file contains the event handling mode and a list of
events, each connected to a script in the EFBytecode. The
EFEventConfig file shall exist on the card to be able to use,
activate and deactivate Wib events. The file contains event-
script-id pairs, one after the other, until an end mark (event
type 'FF'h) occurs. Each event type shall not occur more
- 47 -
SIM Guideline
than once in the list.
Identifier: '6F0B' Structure: Transparent Optional

File size: n*3+4 bytes Update activity: low
Access Conditions:
READ ADM
UPDATE ADM
INVALIDATE ADM
REHABILITATE ADM

O
1 to 3 Event handling mode M 3
4 to 6 Event #1 M 3
: : : :
(n)*3 +1 to Event #n 3
(n+1)*3
(n+1)*3+1 End-Mark M 1
The end-mark is coded 'FF'h. The file contents after the end-
mark is undefined.
Coding of event handling mode:
Event handling mode defines if the event handling
functionality is enabled or disabled.
'FE 00 00'h Event handling is persistently enabled.
'FF 00 00'h Event handling is persistently disabled.
Coding of event entries #1…#n:

Event type Defined the type of According to 3GPP 1
expected event TS 11.14 [9].
Additional event
type identifiers:
„80‟h: Startup event
'81'h…'8F'h:
reserved
'90'.. 'A0': reserved
for customer-specific
- 48 -
SIM Guideline
events
'A1'h…'FD'h:
reserved for
SmartTrust
'FE'h and 'FF':
Reserved
Item identifier Item identifier '00'h: Event is not 1
address to the active
script to be
executed when the Other values depend
event occurs. on the used
addressing mode as
described in sections
“Relative addressing
mode” on page 15
and “Absolute
addressing mode” on
page 15.
Length of event Length of the Length X. 1
specific following field
parameter
Event specific Event specific According to event X
parameters parameters description. Often
not used.

The minimum size of the event configuration file is
recommended to be 60 bytes.
Events are queued if Wib is busy when event occurs. The
events are executed in the same order where they are
defined in the EFEventConfig file. Therefore it is recommended
to think about the order of the defined events.
The unused bytes after the end mark are set to 'FF…FF'h.
To be able to activate and de-activate the events over-the-
air, OTA access conditions of EFEventConfig file shall be set to
6.10 EFText 6F1C

This file contains prompt texts to be displayed to the user in
different situations. The usage for each entry is predefined
for a specific purpose and specified in this file.
- 49 -
SIM Guideline
If the Text TLV has length zero, a null text may be

displayed to the user depending on the prompt text and the
behavior of used proactive command.
Most of the cards do not provide any Display Text proactive
command if Length of TLV is empty or alpha identifier is a
null string.
If Sending Information TLV with Tag '01' has zero length
the alpha identifier is not included into the Send Short
Message proactive command and the mobile may give
information to the user concerning what is happening.
If Sending Information TLV with Tag '01' has an alpha
identifier with length zero the mobile should not give any
information to the user on the fact that the ME is sending a
short message.
Identifier: '6F1C' Structure: transparent Mandatory

File size: X bytes Update activity: low
Access Conditions:
READ ADM
UPDATE ADM
INVALIDATE ADM
REHABILITATE ADM

O
1 to A Text #1 O A
A+1 to Text #2 O B
A+B
: : : :
A+…+1 to Text #n O N
A+…+N
A+…+N+ End mark M 1
1
The end mark is coded 'FF'h. The file contents after the end-
mark is undefined.
The unused bytes after the end mark are set to 'FF…FF'h.
All text fields are coded according to the table below:
- 50 -
SIM Guideline
Field Contents Coding M/ Lengt

O h
Tag Identifies the text According to M 1
object section “Defined
text fields” below.
Length Length of the (5+X) or (2+X) M 1

following fields
Alpha Id Tag '00'h O 1
Length of the Length of the alpha Length (X) 1
alpha identifier identifier '00'h means that
the alpha identifier
is a null object
Alpha identifier Text to display According to X
EFADN
Icon Tag '01'h O 1
Icon qualifier Icon qualifier According to 1
3GPP TS 11.14 [9]
Icon identifier EFIMG record According to 1
number 3GPP TS 11.14 [9]
For UCS2 support only the coding scheme with first octet
set to '80'h is supported by Wib. Coding schemes with first
octet set to '81'h or '82'h may be supported by Wib.
6.10.1 Defined text fields

Tag Usage
'01'h Default sending information text and/or icon to be used
when issuing a server request
As defined in section “Sending info” on page 16.
'02'h Bookmarking menu item text and/or icon as defined in
section “Presentation and navigation” on page 25.
'03'h Bookmarking saving request text and/or icon to request if
the user wants to store the available bookmark as defined
in section “Storing of bookmarks” on page 25.
'04'h Text and/or icon for the bookmark to be stored as defined
in section “Storing of bookmarks” on page 25.
'05'h Menu item text and/or icon to remove stored bookmark as
defined in section “Management of Bookmarks” on page
25.
- 51 -
SIM Guideline
'06'h Text and/or icon to inform the user that the bookmark can't
be stored as defined in section “Storing of bookmarks” on
page 25.
'07'h Text and/or icon to be used when positive answering text,
like "“Store", is required as defined in section “Storing of
bookmarks” on page 25.
'08'h Text and/or icon to be used when negative answering text,
like "Don‟t store", is required as defined in section
“Storing of bookmarks” on page 25.
'09'h Default text and/or icon to alert user that Wib is in the
wait-for-response state as defined in section “User alert
during the Wait-For-Response state” on page 17.
'0A'h Default text and/or icon to be used as receiving info as
defined in section “Receiving info” on page 17.
'0B'h Default text and/or icon to be used as intermediate info as
defined in section “Intermediate info” on page 17.
'0C'h Text and/or icon to inform the user that the bookmark
name is already reserved as defined in section “Storing of
bookmarks” on page 25.
'0D'h…'7F'h RFU
'80'h - 'FD'h Implementation specific texts.
'FE'h Non-used Text.
Tag 'FE'h indicates that the TLV is not used.

The Text TLVs may occur in the file in any order.
The receiving info text may contain escape characters %C,
%T and %P, where C is the order of the current short
message being received, T is the total number of short
messages expected and P is the percentage of messages
received.
For example if the alpha identifier for receiving-info
contains the text “Receiving…(%C/%T)” then the resulting
screen display shall be “Receiving… (1/3)” when the first
message of three has been received. If the Alpha Identifier
contains the text “Receiving %P%%”, the resulting display
shall be “Receiving 33%” after reception of the first
message out of three.”

For example the following values can be stored in the EFText
file:
- 52 -
SIM Guideline
Tag Text
'„01'‟h Sending request...
'‟02'h My Bookmarks
'03'h Do you want to store this as a bookmark?"„
'‟04'h Name of bookmark?"
'‟05'h Remove bookmark„
'‟06'h Error - bookmark cannot be stored„
'‟07'h Store
'‟08'h Don‟t store
'‟09'h Please wait„
'‟0A'h Receiving %P%% „
'‟0B'h Waiting for response„
'‟0C'h Bookmark name already exists. Please
choose another one.
The unused bytes after the end mark are set to 'FF FF'.
To be able to update the prompt texts over-the-air, the OTA
access condition for EFText file shall be set to “OTA
updateable”.
The minimum size of the text file is recommended to be 400
bytes if bookmark is enabled. For text in UCS2 the size of
the file is recommended to be at least 800 bytes.
It is recommended to use percentage format for progress
information in the receiving info prompt text. The
percentage format gives user much better understanding
about the status of downloading.
6.11 EFMenu 6F18

This file contains the menu data to be used as input for
preparation of a SET UP MENU proactive SIM command.
The contents of this file will determine the top level menu
items in Wib menu and which script is to be executed when
the user selects a top level menu item.

Record length: Z bytes (Z  7) Update activity: low
- 53 -
SIM Guideline
Access Conditions:
READ ADM
UPDATE ADM
INVALIDATE ADM
REHABILITATE ADM
Description of the first record

O
1 RFU M 1
2 Bookmarking Indication M 1
3 SET UP MENU parameter M 1
4 Icon identifier for the main menu text M 1
5 Icon qualifier for the main menu text M 1
6 Icon list qualifier for the item list M 1
7 to Z+6 RFU M Z bytes
Description of the remaining records
O
1 Item status M 1
2 Item identifier M 1
3 Menu ordinal M 1
4 RFU M 1
5 Icon identifier M 1
6 Menu text length M 1
7 to X+6 Menu text M X
x+7 to Padding with "FF" O Z
X+Z+6
Coding of the first record:
Field Content and coding

Bookmarking '00'h: Bookmarking is enabled
Indication '01'h: Bookmarking is disabled
'02'-'FF'h: RFU
- 54 -
SIM Guideline
SET UP '00': The main menu is generated, SETUP MENU is

MENU issued by the SIM
parameter 'XX': (other value than '00'): No main menu (SETUP
MENU) is generated by the SIM.
Icon identifier EFIMG record number according to 3GPP TS 11.14 [9].
for the main '00' = Icon not used.
menu text
Icon qualifier According to 3GPP TS 11.14 [9].
for the main
menu text
Icon list According to 3GPP TS 11.14 [9].
qualifier for
the item list
Coding of the remaining records:
Field Content and coding

Item Status Indicator of whether the entry shall be included in the
menu.
'00'h, do not include in menu
'02'h, included in menu
Item identifier The item identifier to be associated with this menu entry.
The interpretation is defined by the addressing mode as
specified in section “Script addressing” on page 15.
Menu ordinal '00'h = Menu ordinal not used.
Icon Identifier EFIMG record number according to 3GPP TS 11.14 [9].
'00' = Icon not used.
Menu text The number of bytes in the menu text.
length
Menu text Field is either coded with unpacked 7-bit GSM default
characters or with the first UCS2 coding scheme
described in GSM 11.11 Annex B.
It means that if the first byte of the menu text is „80h‟, the
remaining octets are 16-bit UCS2 characters. If it is less
than „80h‟, all octets in the menu text, including the first
byte, is coded with unpacked 7-bit GSM default alphabet
characters.
The number of entries, in the file, with item status '02'h,

shall not exceed 25.
- 55 -
SIM Guideline
Note: The number of records in this file will limit the

maximum number of applications in EFBytecode. Further, the
total length of data in SET UP MENU proactive SIM
command is limited, for example if the average length of the
text strings is 10 bytes, the maximum amount of items is 18.
Records that are not used shall be at the end of the file and
contain "FF" bytes. This means that the first empty record is
the end of the menu.
6.11.1 Recommended value

It is important to define enough many records and enough
long space for the menu text in EFMenu file. It is
recommended to have 12 menu items (total 13 records in the
menu file) and reserve 16 characters long space for each
menu text in EFMenu file with record length 22 characters.
If the menu text should be in Unicode it is recommended to
have 8 menu items (total 9 records in the menu file) and
reserve 12 character long space for each menu text, which
means record length 30 bytes.
To be able to download wiblets over-the-air, the OTA
access condition for EFMenu file shall be set to "OTA
updateable".
6.12 EFScriptAddress 6F1D

EFScriptAddress file provides a uniform way to map script
identifiers with script addresses. DP creates a script
identifier for each script as defined in Guidelines -
Deployment of Wib Services [10]. This file identifies the
address of the script in the EFBytecode file.
The usage of the EFScriptAddress file is defined in section
“Script addressing” on page 15.
The content of this file shall be generated as defined in
Identifier: '6F1D' Structure: transparent Mandatory

File size: A*N+2 bytes Update activity: low
Access Conditions:
READ ADM
UPDATE ADM
INVALIDATE ADM
REHABILITATE ADM
- 56 -
SIM Guideline

O
1 Address mode configuration M 1
2 Length (Y) of Script address M 1
3 to 2+A Script item #1 M A
3+A to Script item #2 M A
2+2*A
: : : :
3+(n-1)*A to Script item #n M A
2 +n*A
Coding:

Address mode Script addressing „00‟h, Relative 1
configuration mode addressing for menu
and events.
„01‟h, Relative
addressing for menu.
Absolute addressing
for events.
'02'h Absolute
addressing for menu.
Relative addressing
for events.
'03'h Absolute
addressing for menu
and events.
'04'h…'FF'h RFU
Length (Y) of Number of bytes 1
Script Address used in an absolute
script address.
Coding of Script item:
- 57 -
SIM Guideline
Script identifier Identifier to be According to [10]. 4

used for top-level
services according
to [10].
Script address Absolute address of According to [10]. Y
the length bytes
preceding a script
EFBytecode according
to [10].
The size of this file will limit the maximum number of

accessible scripts in EFBytecode when using absolute
addressing mode and when executing local scripts from
other scripts or from timer expirations.
6.12.1 Examples of the EFScriptAddress file usage
Absolute addressing mode for menu selection and Wib events
EFBytecode
Free space
Length bytes
Script
’0000’ ’00C5’ ’01A5’
EFScriptAddress
EFEventConfig EFMenu
'0302'
'02' '02' ’0000061C0000’ ’02’ ”Balance”
’00001A0301A5’ ’01’ ”MyBank”
’00003E0500C5’
There are 3 scripts in the EFBytecode file. Call disconnected

event with event identifier '02'h is activated in the
EFEventConfig file and the EFMenu file has 2 menu items:
Balance and My Bank.
If call disconnected event occurs, Wib checks which script
is defined in the second field of the EFScriptAddress file and
starts to execute the script in the EFBytecode file with script
identifier 00001A03 and position '01A5'h.
- 58 -
SIM Guideline
If "Balance" is selected in the menu with menu item

identifier 2, Wib checks which script is defined in the
second field of the EFScriptAddress file and starts to execute
script in the EFBytecode file with script identifier 00001A03
and position '01A5'h.
If "MyBank" is selected in the menu with menu item
identifier 1, Wib checks which script is defined in the first
field of the EFScriptAddress file and starts to execute script in
the EFBytecode file with script identifier 0000061C, which
starts from the beginning of the EFBytecode file.
The third script in the EFBytecode file, with script identifier
00003E05 and position '00C5'h is not addressed by Wib
menu or Wib events. But it can be addressed by other script
through a Wiblet-URI as specified in the WML specification
[3].
Direct calling of Script Identifier
EFBytecode
Free space
Length bytes
Script
’0000’ ’00C5’ ’01A5’
EFScriptAddress
'XX02'
’0000061C0000’
’00001A0301A5’
’00003E0500C5’
There are 3 entries in the EFScriptAddress file. Each entry

consists on 4 bytes script identifier and 2 bytes absolute
address of the script in the EFBytecode file.
If the Script Identifier points to the script with script identity
0000061C, Wib starts to execute the first script in the
EFBytecode file with position '0000'h.
00003E05, Wib starts to execute the second script in the
EFBytecode file with position '00C5'h.
00001A03, Wib starts to execute the third script in the
- 59 -
SIM Guideline
EFBytecode file with position '01A5'h.

It is recommended that the size of the EFScriptAddress file is at
least 5% of EFBytecode file size. As an example: If the size of
EFBytecode file is 10.000 bytes, the size of EFScriptAddress file
should be at least 500 bytes, which is equivalent to 83 script
items when the script address length is 2 bytes.
It is recommended to use absolute addressing for menu and
event management.
The content of the EFScriptAddress file is generated as defined
in the Guidelines - Deployment of Wib Services [10].
The unused script item fields are set to 'FF…FF'.
To be able to downloaded wiblets over-the-air, the OTA
access condition for EFScriptAddress file shall be set to "OTA
updateable".
6.13 EFMenuTitle 6F1E

This file contains Wib menu title of the main menu to be
used by Wib together with EFMenu.
Identifier: '6F1E' Structure: linear fixed Optional

Record length: Y bytes Update activity: low
Access Conditions:
READ ADM
UPDATE ADM
INVALIDATE ADM
REHABILITATE ADM
Description of the first record

O
1 RFU M 1
2 RFU M 1
3 Menu text length M 1
4 to X+6 Menu text M X
x+7 to Padding with 'FFh O Z
X+Z+6
- 60 -
SIM Guideline
Coding:

Menu text The number of bytes in the
length menu text.
Menu text According to EFADN in
3GPP TS 11.11 [8].

G&D SmartTrust recommends using EFMenuTitle file for the
main menu title. It is recommended to reserve at least 16
bytes for the menu text.
To be able to update the main menu, the OTA access
condition for EFMenuTitle file shall be set to “OTA
updateable”.
6.14 Reserved file identifiers

The file identifiers 6F00 to 6F4F are reserved for use in
specifications made by G&D SmartTrust.
- 61 -
SIM Guideline
7 OTA functionality
There are situations in the SIM card life cycle where there is
a need to update the card using OTA technology.
The recommended OTA protocol is RFM, Remote File
Management as defined in the RFM implementation
specification [2].
To allow download of wiblets on Wib, OTA access
conditions for the Menu files, EFBytecode file, EFScriptAddress
file and EFEventConfig file must be set to OTA updateable. To
ensure the flexibility of SmartTrust DP and Wib in the
future it is recommended to have all Wib files except key
files in DF2700 OTA updateable.
To allow ordinary OTA update for files in SIM and USIM
application on the card it is recommended to be able to
update all files on the cards except key files and probably
some other files like ICCID.
For all OTA updateable files, OTA access conditions shall
be chosen. Used key set, key length and algorithm depends
on the SIM vendor implementations. Refer to RFM
implementation specification [2] for details.
It is recommended to use a TAR value in range B0 00 10 to
B0 00 1F for the SIM updating and B0 00 01 and B0 00 20
to B0 01 1F for the USIM updating.
- 62 -
SIM Guideline
8 SIM data import

The SmartTrust Delivery Platform needs lot of detailed
information of the SIM cards before the cards can be
managed by the system.
All SIM card related data is imported into the system with
SIM data import files. The import files are created by the
SIM vendors.
The format of the SIM import data is defined in the Import
file format specification [11].
- 63 -
SIM Guideline
Annex A - Example profile for Wib 1.3 cards

without Unicode
(Informative)
This annex provides an example on how to define Wib files
with following configurations:
File Requirement
EFTAR 6F1A Pull TAR = BF FF 01
Push TAR = BF FF 02
Admin TAR = BF FF 03
2 empty records
Pull and Push TAR has the same security configuration
Pull TAR‟s security configuration in Rec 1 in EFSC
Push TAR‟s security configuration in Rec 1 in EFSC
Admin TAR‟s security configuration in Rec 2 in EFSC
EFError Text 6F02 Generic error code DF with detailed error information
EFBytecode 6F03 Size of EFBytecode file is 16kB
File is empty
EFSMS Header 6F04 Account number (destination address) is 12345
Service Centre address is +46 12 34 56 78 90
PID is 00
DCS is F6
Validity period is 1h
EFSC 6F1B SC #1 includes security configuration for Pull and Push TARs
with security level L1, SC2 #2 includes security configurations
for Admin TAR has with security level L2.
SC #3 includes security configuration with security level 3. It is
reserved for future usage.
EF03.48Counter 6F06 6 different counters.
EFVersion Information 6F07 Setec card , version 1

Wib 1.3
ENCR plug-in, version 1
DECR plug-in, version 2
EFWibConfiguration 6F08 3 tone warnings before Wib exits the wait for response state
EFEventConfig 6F0B No events are activated.
Total file size, 60 bytes.
- 64 -
SIM Guideline
EFText 6F1C 01: "Sending request ..." 19 characters

02: "My Bookmarks" 12 characters
03: "Do you want to store this as a bookmark?" 40 characters
04: "Name of bookmark?" 17 characters
05: "Remove bookmark" 15 characters
06: "Error - bookmark cannot be stored" 33 characters
07: "Store" 5 characters
08: "Don‟t store" 11 characters
09: "Please wait" 11 characters
0A: "Receiving (%C/%T)" 17 characters
0B: "Waiting for response..." 23 characters
0C: "Bookmark name already exists. Please choose another one.
56 characters
8 Padding bytes
EFMenu 6F18 Bookmarking enabled
The main menu is generated
No icons
No active Menu items
12 menu items
Each menu item is 16 bytes long
EFScriptAddress Absolute addressing for menu and events
6F1D 800 bytes
EFMenuTitle 6F1E “SIM Menu” text is used as menu title
- 65 -
SIM Guideline
Example profile for Wib 1.3

FILE RECORD SIZE CONTENT COMMENTS
Name Id Type Count Size Data Total Personalization data
TAR 6F 1A Linear fixed 5 5 25 Rec 1: 00 BF FF 01 01h Pull TAR
Rec 2: 01 BF FF 02 01h Push TAR
Rec 3: 02 BF FF 03 02h Admin TAR
Rec 4: FF FF FF FF FFh Not used
Rec 5: FF FF FF FF FFh Not used
Pull and Push TARs in records 1
and 2 uses first security
configuration in EFSC. Admin
TAR uses second security
configuration in EFSC.
Error 6F 02 Transparent 100 100 0A DF 04 45 72 72 6F 72 20 25 44 00 Generic error code DF: Error %D
FF FF FFh
Byte Code 6F 03 Transparent 16 000 16 000 FF…FFh Empty
SMS Header 6F 04 Linear fixed 1 27 27 05812143F5FFFFFFFFFFFFFF079153 Destination address: 12345
4850025283FFFFFFFF00F608h SMSC address: +461234567890
PID: 00
DCS: F6h, 8-bit data
Validity period: 0B = 60min
- 66 -
SIM Guideline
Security 6F 1B Transparent 96 96 30 1E 80 02 01 02 81 04 12 00 07 03 Security level L1 for Pull TAR

Configuration 82 04 12 00 07 03 83 02 00 01 84 02 00 and Push TAR
01 FF FF FF FF FF FF
30 1E 80 02 03 04 81 04 15 00 05 00 Security level 2 for Admin TAR
82 04 15 00 05 00 83 02 00 01 84 00
FF FF FF FF FF FF FF FF
30 1E 80 02 05 06 81 04 16 00 05 00 Security level 3, not used with the
82 04 16 00 05 00 83 02 00 01 84 02 00 existing configuration
02 FF FF FF FF FF FF
03.48 Counter 6F 06 Linear fixed 6 5 30 Rec 1: 00 00 00 00 01h Sending counter has value 1 and
Rec 2: 00 00 00 00 00h receiving counter has value 0.
Rec 3--6: 00 00 00 00 00h
Version 6F 07 Transparent 30 30 01 010301 02 04 454E4352 000001 04 Setec card, Wib version 1.3,
information 44454352 000002 FF FF FF FF FF FF ENCR and DECR plug-ins
FF FF FFh
Wib 6F 08 Transparent 1 1 03h 3 trials before browser exits the

configuration wait state
Event config 6F 0B Transparent 60 60 FF 00 00 FF FF … FF FFh No events defined
- 67 -
SIM Guideline
Text 6F 1C Transparent 315 315 01 15 00 13 53 65 6E 64 69 6E 67 20 01: "Sending request ..." 19

72 65 71 75 65 73 74 20 2E 2E 2E characters
02 0E 00 0C 4D 79 20 42 6F 6F 6B 6D 02: "My Bookmarks" 12
61 72 6B 73 characters
03 2A 00 28 44 6F 20 79 6F 75 20 77
61 6E 74 20 74 6F 20 73 74 6F 72 65 03: "Do you want to store this as a
20 74 68 69 73 20 61 73 20 61 20 62 6F bookmark?" 40 characters
6F 6B 6D 61 72 6B 3F
04 13 00 11 4E 61 6D 65 20 6F 66 20
42 6F 6F 6B 6D 61 72 6B 3F 04: "Name of bookmark?" 17
05 11 00 0F 52 65 6D 6F 76 65 20 42 characters
6F 6F 6B 6D 61 72 6B 05: "Remove bookmark" 15
06 23 00 21 45 72 72 6F 72 20 2D 20 characters
62 6F 6F 6B 6D 61 72 6B 20 63 61 6E 06: "Error - bookmark cannot be
6E 6F 74 20 62 65 20 73 74 6F 72 65 stored" 33 characters
64
07 07 00 05 53 74 6F 72 65 07: "Store" 5 characters
08 0D 00 0B 44 6F 6E 27 74 20 73 74 08: "Don‟t store" 11 characters
6F 72 65
09 0D 00 0B 50 6C 65 61 73 65 20 77 09: "Please wait" 11 characters
61 69 74
0A 13 00 11 52 65 63 65 69 76 69 6E 0A: "Receiving (%C/%T)" 17
67 20 28 25 43 2F 25 54 29 characters
0B 19 00 17 57 61 69 74 69 6E 67 20 0B: "Waiting for response..." 23
66 6F 72 20 72 65 73 70 6F 6E 73 65 characters
2E 2E 2E
0C 3A 00 38 42 6F 6F 6B 6D 61 72 6B 0C: "Bookmark name already
20 6E 61 6D 65 20 61 6C 72 65 61 64 exists. Please choose another one.
- 68 -
SIM Guideline
79 20 65 78 69 73 74 73 2E 20 50 6C 56 characters
65 61 73 65 20 63 68 6F 6F 73 65 20
61 6E 6F 74 68 65 72 20 6F 6E 65 2E
FF Padding
FF FF FF FF FF FF FF FFh
Menu 6F 18 Linear fixed 13 22 286 Rec 1: 00 00 00 00 00 00 00…00h Bookmarking is enabled
Rec 2-13: FF …FFh The main menu is generated
No icons
No defined menu items
Script Address 6F 1D Transparent 800 800 03 02 FF … FFh Absolute addressing used for
menu and event management
Length of script address 2 bytes
Menu Title 6F 1E Linear fixed 19 19 00 00 08 53 49 4D 20 4D 65 6E 75 FF SIM Menu
FF FF FF FF FF FF FFh
- 69 -

Sim Guideline Wib 1 3 Equipped Sim Cards PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Sim Guideline Wib 1 3 Equipped Sim Cards PDF

Uploaded by

Copyright:

Available Formats

SIM Guideline

Wib 1.3 equipped (U) SIM cards

Document number: 90-294

© 2011 Giesecke & Devrient 3S AB. Proprietary/Confidential. All rights reserved.

2 SmartTrust Certified Wib __________________________________________ 8

3.10 Message routing information .......................................................... 17

4 G&D SmartTrust solutions _________________________________________ 27

5 Ordering Wib equipped (U)SIM cards _______________________________ 28

6 Wib parameters on the SIM card ___________________________________ 32

6.4.1 File structure .............................................................................. 38

7 OTA functionality _________________________________________________ 62

8 SIM data import __________________________________________________ 63

Annex A - Example profile for Wib 1.3 cards without Unicode

1.2 Purpose of the document

KIc Key and algorithm Identifier for ciphering

2 SmartTrust Certified Wib

3.1 New features

3.1.1 Downloadable Wib plug-ins

3.1.3 Enhanced wait for response state

3.1.4 Unified menu file structure

3.1.5 Addressing with script identifier

3.1.7 Enhanced variable support

3.1.8 Timer management

3.2 Wib Plug-ins

3.2.1 Downloading of the plug-ins

3.2.2 Keys for the security plug-ins

3.2.3 Prompt texts

3.2.4 Other plug-in parameters

Several Wib commands and the menu items have the

3.3.1 Icons with menu items and bookmarks

3.4 Wib events

3.4.1 SIM Toolkit events

3.4.2 SIM internal events

Network Available event

3.5.1 Menu structure

The main menu title “SIM Browser” can be stored in the

3.5.2 Size of menu file

3.6 Wib bytecode

3.7 Wib script

3.8 Script addressing

3.8.1 Relative addressing mode

3.8.2 Absolute addressing mode

3.8.3 Wiblet-URI and timer expiration

3.9 User interface during the server request and response

Sending info intermediate info receiving info

3.9.1 Sending info

3.9.2 Wait-for-response state

3.9.3 User alert during the Wait-For-Response state

3.10 Message routing information

TAR values are defined in the EFTAR file, refer to section

Usage of TAR values

Relation between the used TAR value and security configuration

3.10.2 SMSC address

3.10.3 Account number

3.11 Transport layer security

3.11.1 Security configurations

Supported security levels

Level SPI KIc KID Description

This security level ensures protection against replay and

This security level ensures protection against replay and

This security level ensures protection against replay and

This security level should be used for testing only, since it

The most significant nibble of KIc, denoted x, is the KIc