Settings and Message Storage in the SIM

The internal architecture of a SIM card is organized around a processor and there are the following three different types of memory:
1- Read Only Memory (ROM): this memory contains the card operating system along with one or more applications.
2- Electrically Erasable Programmable Read Only Memory (EEPROM): this memory contains all parameters defined by the GSM/3GPP technical specifications and data manipulated by applications. Information saved in this memory is persistently stored even if the mobile station has been powered off.
3- Random Access Memory (RAM): this memory contains data manipulated by applications. Information stored in this memory is lost when the mobile station is powered off.

The storage structure of a SIM card is based on a hierarchy of folders and files. The root folder is known as the Master File (MF), a normal folder is known as a Dedicated File (DF), and a file is known as an Elementary File (EF).

Structure of a Message Segment

Transport Protocol Data Unit


Message Types
SMS-SUBMIT, SMS-SUBMIT-REPORT, SMS-DELIVERY-REPORT, SMS-STATUS-REPORT, SMS-COMMAND.
Text Coding Schemes
The two text coding schemes that can be used in SMS are the GSM 7-bit default alphabet defined in [3GPP-23.038] and the Universal Character Set (UCS2) defined in [ISO-10646].








Text Compression In theory, the text part of a message may be compressed [3GPP-23.042]. However, none of the handsets currently available on the market support text compression. A message with compressed text cannot be displayed properly by an MS that does not support text decompression.

Message Classes
In addition to its type, a message belongs to a class. The TP-Data-Coding-Scheme (TP-DCS) parameter of the TPDU indicates the class to which the message belongs. It has to be noted that in most cases, a message does not belong to any of the four classes. In this situation the message is known as a no-class message and is usually handled as a class 1 or 2 message by the receiving SME.













Coding Groups
A message may belong to one of three coding groups. The coding group indicates what the receiving SME should do with the message once it has been read or interpreted.














Protocol Identifiers
The protocol identifier indicates how the receiving messaging application should handle an incoming Message (normal case, ME data download, SIM data download, etc.).

SMS - Protocol Layers

The SMS protocol stack is composed of four layers: the application layer, the transfer layer, the relay layer, and the link layer. The application layer is implemented in SMEs in the form of software applications that send, receive, and interpret the content of messages (e.g., message editor, games, etc.). The application layer is also known as SM-AL for Short-Message-Application-Layer. At the transfer layer, the message is considered as a sequence of octets containing information such as message length, message originator or recipient, date of reception, etc. The transfer layer is also known as the SM-TL for Short-Message-Transfer-Layer. The relay layer allows the transport of a message between various network elements. The relay layer is also known as the SM-RL for Short-Message-Relay-Layer. The link layer allows the transmission of the message at the physical level. For this purpose, the message is protected to cope with low-level channel errors. The link layer is also known as the SM-LL for Short-Message-Link-Layer. For transport purposes, an application maps the message content and associated delivery instructions onto a Transfer Protocol Data Unit (TPDU) at the transfer layer. ATPDU is composed of various parameters indicating the type of the message, specifying whether or not a status report is requested, containing the text part of the message, etc.

SMS Interworking between Mobile Networks
For this purpose, operators have commercial agreements. Each mobile network counts the number of messages being sent from another network. After a given period of time, these counts are compared and there is a commercial settlement between operators.

Message Structure
A message refers to the subscriber’s perception of the message composed of text and/or elements such as pictures, melodies, etc. For transport purposes and due to limitations at the transfer layer, an application may need to segment the message into several pieces called message segments.


SME-SMSC Transactions/Submit, Deliver, Report, and Command
At the transfer layer, six types of transactions can occur between an SME and an SMSC:

• SMS-SUBMIT: this transaction corresponds to the submission of a message segment from the SME to the SMSC. Upon submission of the message segment, the SMSC acknowledges the submission with the SMS-SUBMIT-REPORT transaction.

• SMS-DELIVER: this transaction corresponds to the delivery of a message segment from the SMSC to the SME. Upon delivery of the message segment, the SME acknowledges the delivery with the SMS-DELIVER-REPORT transaction.

• SMS-STATUS-REPORT: this transaction corresponds to the transfer of a status report from an SMSC back to an SME.

• SMS-COMMAND: this transaction corresponds to the request from an SME, usually an external SME, for the execution of a specific command by the SMSC.

SMS Basic Features

SMS encompasses a number of basic features. This includes message submission, message delivery, handling of status reports, requests for command execution, reply path, etc. These features are presented in the following sections.

Message Submission and Delivery
Message Sending: Mobile-originated messages are messages which are submitted from an MS to an SMSC. These messages are addressed to other SMEs such as other mobile users or Internet hosts. This feature is also known as the Short Message-Mobile Originated (SM-MO).
Message Delivery: Mobile-terminated messages are messages delivered by the SMSC to the MS. Nearly all GSM handsets support message reception. This feature is also known as Short Message Mobile Terminated (SM-MT). In GSM, messages are sent over SDCCH or SACCH channels whereas, in GPRS, short messages are sent over PDTCH channels.

Status Reports
It is possible for an originator SME to request that a status report be generated upon delivery of the short message to the recipient SME. The status report indicates to the originator whether or not the short message has been successfully delivered to the recipient SME.

Reply Path
This feature is sometimes used by operators to allow the message recipient to provide a reply message ‘‘free of charge’’ for the message recipient. Additionally, for networks supporting several SMSCs, operators sometimes use this feature to get reply messages to be returned to a particular SMSC. For example, an operator could have several SMSCs but only one connected to the Email gateway. In this configuration, if a message is originated from the Internet domain, then the operator uses the reply path to indicate that any message reply associated with this Email-originated message should be submitted to the SMSC connected to the Email gateway.

Addressing Modes
With SMS, several modes are possible for addressing message recipients. The most common addressing mode consists of using the Mobile Station ISDN Number (MSISDN) in the [ITU-E.164] format (e.g., ?33612345678). An optional addressing feature of SMS consists of conveying sub-addressing information as part of a message. For instance, a mobile handset may request a weather forecast update by sending a message to an application server. The identification of the requested service (e.g., service 64) can be specified as part of the sub-addressing information.

Validity Period
A message originator has the possibility of indicating a validity period for a message. This validity period defines the deadline after which the message content is to be discarded. If a message has not been delivered to the message recipient before the expiry date, then the network usually discards the message without further attempts to deliver it to the recipient.

SMS Use Cases

Short Message Service

The Short Message Service (SMS) is a basic service allowing the exchange of short text messages between subscribers. The first short text message is believed to have been transferred in 1992 over signaling channels of a European GSM network.

Service Description
Developed as part of the GSM Phase 1 ETSI technical specifications, the Short Message Service (SMS) allows mobile stations and other network-connected devices to exchange short text messages.

SMS Use Cases
SMS was intended to be a means of exchanging limited amounts of information between two mobile subscribers. This limited capability has become a building block for the development of more compelling services ranging from the download of ringtones to professional applications such as remote monitoring or fleet tracking.

Consumer Applications Based on SMS
Person-to-Person Messaging: This is the original use case for which SMS has been designed. This use case relates to the exchange of a short text message between two mobile subscribers. With SMS, the two most well known predictive text input algorithms are T9 from Tegic and ZI from ZI corporation.
Information Services: This is probably one of the most common use cases in the machine-to-person scenario. With information services, weather updates and financial reports can be prepared by value-added service providers and pushed to mobile handsets with SMS.
Voice Message and Fax Notifications: This use case is widely supported in GSM mobile networks. This use case relates to the reception of messages containing notifications for voice messages and fax waiting in a remote message inbox.
Internet Email Alerts: With Email alerts via SMS, subscribers are notified that one or more Email messages are waiting to be retrieved. Such an alert usually contains the address of the message originator along with the message subject and the first few words from the Email message body.
Download Services: It has become popular for mobile subscribers to customize their mobile handset. This can be done by associating ringtones to persons in the phone contact directory.
Chat Applications: During a chat session, several users can exchange messages in an interactive fashion. All messages exchanged during a session are kept in chronological order in a chat history. In the chat history, messages sent from a recipient are differentiated from messages sent from other users. Several existing mobile chat applications are based on SMS for the transport of messages.
Smart Messaging: Smart Messaging is a proprietary service developed by Nokia. This service enables the exchange of various objects via SMS. This includes the transfer of Internet configuration
parameters, business cards for PIM updates, etc.

Corporate Applications Based on SMS
Vehicle Positioning: The Global Positioning System (GPS) is a technology for determining global positions on Earth. A GPS receiver coupled to a handset, built-in or as an accessory, can provide the location of a person or equipment. This location information can be formatted in a short message and sent to a remote server via SMS. The server interprets locations received from several handsets and displays them on associated geographical maps.
Remote Monitoring: Messages can transport information about the state of remote devices. For instance, system administrators can be notified by a short message that a server is running low of resources or that a fault has been detected on a remote computer.

Operator Applications Based on SMS
Operators have used SMS as a building block for enabling the realization of several services including the ones listed below.
SIM Lock: Operators sometimes require handsets to be locked and usable with only one specific SIM. After a minimal subscription period, the user may request the operator to deactivate the lock in order to be able to use the mobile handset with another SIM (from the same operator or from another operator). If the operator agrees on the lock being deactivated, then the operator sends a short message containing a code allowing the device to be unlocked.
SIM Updates: With SMS, operators can remotely update parameters stored in the SIM. This is performed by sending one or more messages with new parameters to a mobile device. In the past, operators have used this method for updating voice mail access numbers, customer service profiles (determining which network services are accessible to the subscriber), operator name for display in idle mode on the device screen, and address book entries.
Message Waiting Indicator: Operators have used SMS as a simple way to update message waiting indicators on the receiving handset. With this mechanism, a short message contains the type of indicator (voice mail, etc.) to be updated along with the number of waiting messages.
WAP Push: The SMS can be used as a bearer for realizing theWAP push. With this configuration, a WSP protocol data unit or the URI of the content to be retrieved is encoded in a short message and sent to the receiving device. Upon reception of such a message, the WAP microbrowser intercepts the message, interprets the pushed content, and presents the content to the subscriber.

Standardization

Standardization of telecommunications technologies and associated service enablers is of key importance for the development of communicating systems in a multi-vendor environment. Many parties such as operators, manufacturers, third party application developers, and sometimes regulators collaborate in the scope of standardization activities to produce technical specifications that are widely endorsed for the development of commercial solutions.

• Third Generation Partnership Project (3GPP): 3GPP is not a standardization development organization in its own right but rather a joint project between several regional standardization bodies from Europe, North America, Korea, Japan, and China. The prime objective of 3GPP is to develop UMTS technical specifications. It is also responsible for maintaining existing GSM specifications and developing further GSM extensions (e.g., GPRS).
• Third Generation Partnership Project 2 (3GPP2): 3GPP2 is another standardization partnership project established out of the International Telecommunication Union’s (ITU) International Mobile Telecommunications ‘‘IMT-2000’’ initiative. The role of 3GPP2 is to produce specifications for services deployed in several North American and Asian markets with focus on next generation CDMA networks.
• GSM Association (GSMA): GSMA is a global trade organization that represents the interest of several hundreds of GSM mobile operators.
• Internet Engineering Task Force (IETF): IETF is a large community of academic and industrial contributors that defines the protocols primarily used on the Internet. Messaging services in the mobile world also rely on several IETF protocols.
• World Wide Web Consortium (W3C): W3C is a standardization body that concentrates on the development of protocols and formats to be used in the World Wide Web. Well-known formats and protocols published by W3C are the Hypertext Transfer Protocol (HTTP) and the eXtensible Markup Language (XML).
• WAP Forum: the Wireless Application Protocol (WAP) Forum was a joint project for the definition of WAP technical specifications. WAP Forum: the Wireless Application Protocol (WAP) Forum was a joint project for the definition of WAP technical specifications.
• Open Mobile Alliance (OMA): OMA is a standardization forum established in June 2002. Activities of several existing standardization bodies including the ones of the WAP Forum (MMS and others) have been transferred to OMA. OMA is therefore actively involved in maintaining MMS standards designed by the WAP Forum and producing new standards for next generations of MMS devices.

Wireless Application Protocol

The Wireless Application Protocol (WAP) is the result of a collaborative work between many wireless industry players, carried out in the scope of the WAP Forum. The forum, launched in 1997 by Nokia, Phone.Com (now Openwave), Motorola, and Ericsson produced technical specifications enabling the support of applications over various wireless platforms (GSM, GPRS, UMTS, etc.).

Introduction to WAP
The WAP technology is an enabler for building applications (e.g., browsing, messaging, etc.) that run seamlessly over various wireless platforms. focus on the following aspects:
• Interoperability: applications developed by various parties and hosted on devices, produced by different manufacturers, interoperate in a satisfactory manner.
• Scalability: mobile network operators are able to scale services to subscribers’ needs.
• Efficiency: the framework offers a quality of service suited to the capabilities of underlying wireless networks.
• Reliability: the framework represents a stable platform for deploying services.
• Security: the framework ensures that user data can be safely transmitted over a serving mobile network, which may not always be the home network. This includes the protection of services and devices and the confidentiality of subscriber data.
In line with these considerations, the WAP technology provides an application model close to the World Wide Web model. The web model includes the following key elements:
• Standard naming model: objects available over the web are uniquely identified by Uniform Resource Identifiers (URIs).
• Content type: objects available on the web are typed. Consequently, web browsers can correctly determine the type of a specific content.
• Standard content format: web browsers support a number of standard content formats such as the HyperText Markup Language (HTML).
• Standard content format: web browsers support a number of standard content formats such as the HyperText Markup Language (HTML).
the web model, as it is, does not efficiently cope with constraints of today’s mobile networks and devices. To cope with these constraints, the WAP model leverages the web model by adding the following improvements:
• The push technology allows content to be pushed directly from the server to the mobile device without any prior explicit request from the user.
• The adaptation of content to the capabilities of WAP devices relies on a mechanism known as the User Agent Profile (UAProf).
• The support of advanced telephony features by applications, such as the handling of calls (establishment and release of calls, placing a call on hold, or redirecting the call to another user, etc.).
• The External Functionality Interface (EFI ) allows ‘‘plug-in’’ modules to be added to browsers and applications hosted in WAP devices in order to increase their overall capabilities.
• The persistent storage allows users to organize, access, store, and retrieve content from/to remote locations.
• The Multimedia Messaging Service (MMS) is a significant added value of the WAP model over the web model. It relies on generic WAP mechanisms such as the push technology and the UAProf to offer a sophisticated multimedia messaging service to mobile users.

The WAP model uses the standard naming model and content types defined in the web model. In addition, the WAP model includes the following:
• Standard content formats: browsers in the WAP environment, known as microbrowsers, support a number of standard content formats/languages including the Wireless Markup Language (WML) and the eXtensible HTML (XHTML). WML and XHTML are both applications of the eXtensible Markup Language (XML).
• Standard protocols: microbrowsers communicate according to protocols that have been optimized for mobile networks, including the Wireless Session Protocol (WSP) and HTTP from the web model.

WAP Architecture
The WAP device can communicate with remote servers directly or via a number of intermediary proxies and gateways. The primary function of proxies/gateways is to optimize the transport of content from servers to WAP devices.

Push Technology
With push technology, a server is able to push some data to the WAP device with no prior explicit request from the client. In the push framework, the push initiator initiates the push transaction. The push initiator, usually an application server (e.g., web server, MMS center, etc.) transmits the content to be pushed along with XML-formatted delivery instructions to a Push Proxy Gateway (PPG).
The PPG then delivers the push content to the WAP device. The push initiator interacts with the PPG using the Push Access Protocol (PAP). On the other side, the PPG uses the Push Over The Air (OTA) protocol (based on WSP or HTTP) to deliver the push content to the WAP device.

User Agent Profile
The objective of this specification is to define a method for describing the capabilities of clients and the preferences of subscribers. For this purpose, the user agent profile is formatted using a Resource Description Framework (RDF) schema in accordance with Composite Capability/Preference Profiles (CC/PP).
UAProf is composed of the following components:
• Hardware platform: this component gathers a set of properties indicating the hardware capabilities of a device (screen size, etc.).
• Software platform: this component groups a set of properties indicating the software capabilities of a device (operating system, supported image formats, etc.).
• Browser user agent: this component gathers properties characterizing the Internet Browser capabilities.
• Network characteristics: this component informs on network and environment Characteristics such as the bearer capacity.
• WAP characteristics: this component advertises WAP browsing capabilities of the device. This includes information on the configuration of the WML browser and so on.
• Push characteristics: this component indicates push capabilities of the device. This includes the set of supported content types, the maximum message size that can be handled, and whether or not the device can buffer push messages.
• MMS characteristics: this component describes the device capabilities for retrieving and rendering multimedia messages (MMS version, maximum message size, supported content types, etc.).