Friday, November 19, 2010

SMS

Short Message Service (SMS) is the text communication service component of phone, web or mobile communication systems, using standardized communications protocols that allow the exchange of short text messages between fixed line or mobile phone devices. SMS text messaging is the most widely used data application in the world, with 2.4 billion active users, or 74% of all mobile phone subscribers.[citation needed] The term SMS is used as a synonym for all types of short text messaging as well as the user activity itself in many parts of the world.
SMS as used on modern handsets was originated from radio telegraphy in radio memo pagers using standardized phone protocols and later defined as part of the Global System for Mobile Communications (GSM) series of standards in 1985[1] as a means of sending messages of up to 160 characters[2], to and from GSM mobile handsets.[3] Since then, support for the service has expanded to include other mobile technologies such as ANSI CDMA networks and Digital AMPS, as well as satellite and landline networks.[citation needed] Most SMS messages are mobile-to-mobile text messages though the standard supports other types of broadcast messaging as well.

History

[edit] Initial concept

SMS messages sent monthly in USA (billion)
The idea of adding text messaging to the services of mobile users was latent in many communities of mobile communication services at the beginning of the 1980s. The first action plan of the CEPT Group GSM, approved in December 1982, requested "The services and facilities offered in the public switched telephone networks and public data networks... should be available in the mobile system".[4] This target includes the exchange of text messages either directly between mobile stations, or transmitted via Message Handling Systems widely in use since the beginning of the 1980s.[5]
The SMS concept was developed in the Franco-German GSM cooperation in 1984 by Friedhelm Hillebrand and Bernard Ghillebaert.[6] The innovation in SMS is Short. The GSM is optimized for telephony, since this was identified as its main application. The key idea for SMS was to use this telephony-optimized system, and to transport messages on the signaling paths needed to control the telephony traffic during time periods when no signaling traffic existed. In this way, unused resources in the system could be used to transport messages at minimal cost. However, it was necessary to limit the length of the messages to 128 bytes (later improved to 140 bytes, or 160 seven-bit characters) so that the messages could fit into the existing signaling formats.
This concept allowed SMS to be implemented in every mobile station by updating its software. This concept was instrumental for the implementation of SMS in every mobile station ever produced and in every network from early days. Hence, a large base of SMS capable terminals and networks existed when the users began to utilize the SMS.[7] A new network element required was a specialized short message service center, and enhancements were required to the radio capacity and network transport infrastructure to accommodate growing SMS traffic.

[edit] Early development

The technical development of SMS was a multinational collaboration supporting the framework of standards bodies, and through these organizations the technology was made freely available to the whole world. This is described and supported by evidence in the following sections.[8]
The first proposal which initiated the development of SMS was made by a contribution of Germany and France into the GSM group meeting in February 1985 in Oslo[9]. This proposal was further elaborated in GSM subgroup WP1 Services (Chairman Martine Alvernhe, France Telecom) based on a contribution from Germany. There were also initial discussions in the subgroup WP3 network aspects chaired by Jan Audestad (Telenor). The result was approved by the main GSM group in a June '85 document which was distributed to industry.[10] The input documents on SMS had been prepared by Friedhelm Hillebrand (Deutsche Telekom) with contributions from Bernard Ghillebaert (France Télécom).
SMS was considered in the main GSM group as a possible service for the new digital cellular system. In GSM document "Services and Facilities to be provided in the GSM System",[1] both mobile-originated and mobile-terminated short messages appear on the table of GSM teleservices.
The discussions on the GSM services were concluded in the recommendation GSM 02.03 "TeleServices supported by a GSM PLMN".[11] Here a rudimentary description of the three services was given:
  1. Short message Mobile Terminated (SMS-MT)/ Point-to-Point: the ability of a network to transmit a Short Message to a mobile phone. The message can be sent by phone or by a software application.
  2. Short message Mobile Originated (SMS-MO)/ Point-to-Point: the ability of a network to transmit a Short Message sent by a mobile phone. The message can be sent to a phone or to a software application.
  3. Short message Cell Broadcast.
The material elaborated in GSM and its WP1 subgroup was handed over in Spring 1987 to a new GSM body called IDEG (the Implementation of Data and Telematic Services Experts Group), which had its kickoff in May 1987 under the chairmanship of Friedhelm Hillebrand (German Telecom). The technical standard known today was largely created by IDEG (later WP4) as the two recommendations GSM 03.40 (the two point-to-point services merged together) and GSM 03.41 (cell broadcast).
WP4 created a Drafting Group Message Handling (DGMH), which was responsible for the specification of SMS. It was chaired by Finn Trosby (Telenor). DGMH had about five to eight participants (Finn Trosby mentions as a contributor Alan Cox of Vodafone). The first action plan[12] mentions for the first time the Technical Specification 03.40 “Technical realisation of the Short Message Service”. Responsible editor was Finn Trosby. The first draft of the technical specification was completed in November 1987 [13] A comprehensive description [14].
The work on the draft specification continued in the following few years, where Kevin Holley of Cellnet (now Telefonica O2 UK) played a leading role. Besides the completion of the main specification GSM 03.40, the detailed protocol specifications on the system interfaces also needed to be completed.

[edit] Support in other architectures

The Mobile Application Part (MAP) of the SS7 protocol included support for the transport of Short Messages through the Core Network from its inception.[15] MAP Phase 2 expanded support for SMS by introducing a separate operation code for Mobile Terminated Short Message transport.[16] Since Phase 2, there have been no changes to the Short Message operation packages in MAP, although other operation packages have been enhanced to support CAMEL SMS control.
From 3GPP Releases 99 and 4 onwards, CAMEL Phase 3 introduced the ability for the Intelligent Network (IN) to control aspects of the Mobile Originated Short Message Service,[17] while CAMEL Phase 4, as part of 3GPP Release 5 and onwards, provides the IN with the ability to control the Mobile Terminated service.[18] CAMEL allows the gsmSCP to block the submission (MO) or delivery (MT) of Short Messages, route messages to destinations other than that specified by the user, and perform real-time billing for the use of the service. Prior to standardized CAMEL control of the Short Message Service, IN control relied on switch vendor specific extensions to the Intelligent Network Application Part (INAP) of SS7.

[edit] Early implementations

The first SMS message[19] was sent over the Vodafone GSM network in the United Kingdom on 3 December 1992, from Neil Papworth of Sema Group (now Airwide Solutions) using a personal computer to Richard Jarvis of Vodafone using an Orbitel 901 handset. The text of the message was "Merry Christmas".[20]
The first commercial deployment of a short message service center (SMSC) was by Aldiscon (now Acision) with Telia (now TeliaSonera) in Sweden in 1993[21], followed by Fleet Call (now Nextel)[citation needed] in the US, Telenor in Norway[citation needed] and BT Cellnet (now O2 UK)[citation needed] later in 1993. All first installations of SMS gateways were for network notifications sent to mobile phones, usually to inform of voice mail messages. The first commercially sold SMS service was offered to consumers, as a person-to-person text messaging service by Radiolinja (now part of Elisa) in Finland in 1993. It should be noted that most early GSM mobile phone handsets did not support the ability to send SMS text messages, and Nokia was the only handset manufacturer whose total GSM phone line in 1993 supported user-sending of SMS text messages.
Initial growth was slow, with customers in 1995 sending on average only 0.4 messages per GSM customer per month.[22] One factor in the slow takeup of SMS was that operators were slow to set up charging systems, especially for prepaid subscribers, and eliminate billing fraud which was possible by changing SMSC settings on individual handsets to use the SMSCs of other operators[citation needed].
Over time, this issue was eliminated by switch billing instead of billing at the SMSC and by new features within SMSCs to allow blocking of foreign mobile users sending messages through it. By the end of 2000, the average number of messages reached 35 per user per month,[22] and by Christmas Day 2006, over 205 million messages were sent in the UK alone.[23]
It is also alleged that the fact that roaming customers, in the early days, rarely received bills for their SMSs after holidays abroad had a boost on text messaging as an alternative to voice calls.[citation needed]

[edit] Text messaging outside GSM

SMS was originally designed as part of GSM, but is now available on a wide range of networks, including 3G networks. However, not all text messaging systems use SMS, and some notable alternative implementations of the concept include J-Phone's SkyMail and NTT Docomo's Short Mail, both in Japan. Email messaging from phones, as popularized by NTT Docomo's i-mode and the RIM BlackBerry, also typically uses standard mail protocols such as SMTP over TCP/IP.

[edit] SMS today

In 2008, 4.1 trillion SMS text messages were sent. SMS has become a massive commercial industry, worth over 81 billion dollars globally as of 2006.[24] The global average price for an SMS message is 0.11 USD, while the cost to providers approaches zero. Mobile networks charge each other so-called interconnect fees of at least $0.04US (£0.03) when connecting between different phone networks.[25]

[edit] Technical details

[edit] GSM

The Short Message Service – Point to Point (SMS-PP) is defined in GSM recommendation 03.40.[3] GSM 03.41 defines the Short Message Service – Cell Broadcast (SMS-CB), which allows messages (advertising, public information, etc.) to be broadcast to all mobile users in a specified geographical area.[26]
Messages are sent to a Short message service center (SMSC) which provides a "store and forward" mechanism. It attempts to send messages to the SMSC's recipients. If a recipient is not reachable, the SMSC queues the message for later retry.[27] Some SMSCs also provide a "forward and forget" option where transmission is tried only once. Both mobile terminated (MT, for messages sent to a mobile handset) and mobile originating (MO, for those sent from the mobile handset) operations are supported. Message delivery is "best effort", so there are no guarantees that a message will actually be delivered to its recipient, but delay or complete loss of a message is uncommon. Users may request delivery reports to confirm that messages reach the intended recipients, either via the SMS settings of most modern phones, or by prefixing each message with *0# or *N#.

[edit] Message size

Transmission of short messages between the SMSC and the handset is done whenever using the Mobile Application Part (MAP) of the SS7 protocol. Messages are sent with the MAP MO- and MT-ForwardSM operations, whose payload length is limited by the constraints of the signaling protocol to precisely 140 octets (140 octets = 140 * 8 bits = 1120 bits). Short messages can be encoded using a variety of alphabets: the default GSM 7-bit alphabet, the 8-bit data alphabet, and the 16-bit UTF-16 alphabet.[28] Depending on which alphabet the subscriber has configured in the handset, this leads to the maximum individual short message sizes of 160 7-bit characters, 140 8-bit characters, or 70 16-bit characters (including spaces). GSM 7-bit alphabet support is mandatory for GSM handsets and network elements,[28] but characters in languages such as Arabic, Chinese, Korean, Japanese or Cyrillic alphabet languages (e.g. Russian, Serbian, Bulgarian, etc.) must be encoded using the 16-bit UTF-16 character encoding (see Unicode). Routing data and other metadata is additional to the payload size.
Larger content (concatenated SMS, multipart or segmented SMS, or "long SMS") can be sent using multiple messages, in which case each message will start with a user data header (UDH) containing segmentation information. Since UDH is part of the payload, the number of available characters per segment is lower: 153 for 7-bit encoding, 134 for 8-bit encoding and 67 for 16-bit encoding. The receiving handset is then responsible for reassembling the message and presenting it to the user as one long message. While the standard theoretically permits up to 255 segments,[29] 6 to 8 segment messages are the practical maximum, and long messages are often billed as equivalent to multiple SMS messages. See concatenated SMS for more information. Some providers have offered length-oriented pricing schemes for messages, however, the phenomenon is disappearing.

[edit] sms Gateway providers

SMS gateway providers facilitate SMS traffic between businesses and mobile subscribers, including mission-critical messages, SMS for enterprises, content delivery, and entertainment services involving SMS, e.g. TV voting. Considering SMS messaging performance and cost, as well as the level of messaging services, SMS gateway providers can be classified as aggregators or SS7 providers.
The aggregator model is based on multiple agreements with mobile carriers to exchange two-way SMS traffic into and out of the operator's SMSC, also known as local termination model. Aggregators lack direct access into the SS7 protocol, which is the protocol where the SMS messages are exchanged. SMS messages are delivered to the operator's SMSC, but not the subscriber's handset; the SMSC takes care of further handling of the message through the SS7 network.
Another type of SMS gateway provider is based on SS7 connectivity to route SMS messages, also known as international termination model. The advantage of this model is the ability to route data directly through SS7, which gives the provider total control and visibility of the complete path during SMS routing. This means SMS messages can be sent directly to and from recipients without having to go through the SMSCs of other mobile operators. Therefore, it is possible to avoid delays and message losses, offering full delivery guarantees of messages and optimized routing. This model is particularly efficient when used in mission-critical messaging and SMS used in corporate communications.

[edit] Interconnectivity with other networks

Message Service Centers communicate with the Public Land Mobile Network (PLMN) or PSTN via Interworking and Gateway MSCs.
Subscriber-originated messages are transported from a handset to a Service Center, and may be destined for mobile users, subscribers on a fixed network, or Value-Added Service Providers (VASPs), also known as application-terminated. Subscriber-terminated messages are transported from the Service Center to the destination handset, and may originate from mobile users, from fixed network subscribers, or from other sources such as VASPs.
On some carriers non-subscribers can send messages to a subscriber's phone using an Email-to-SMS gateway. Additionally, many carriers, including AT&T, T-Mobile[30], Sprint[31], and Verizon Wireless[32], offer the ability to do this through their respective websites.
For example, an AT&T subscriber whose phone number was 555-555-5555 would receive e-mails from 5555555555@txt.att.net as text messages. AT&T subscribers can easily reply to these SMS messages, and the SMS reply is sent back to the original email address. Sending email to SMS is free for the sender, but the recipient is subject to the standard delivery charges. Only the first 1600 characters of an email message can be delivered to a phone, and only 160 characters can be sent from a phone.
Text-enabled fixed-line handsets are required to receive messages in text format. However, messages can be delivered to non-enabled phones using text-to-speech conversion.[33]
Short messages can send binary content such as ringtones or logos, as well as Over-the-air programming (OTA) or configuration data. Such uses are a vendor-specific extension of the GSM specification and there are multiple competing standards, although Nokia's Smart Messaging is common. An alternative way for sending such binary content is EMS messaging, which is standardized and not dependent on vendors.
SMS is used for M2M (Machine to Machine) communication. For instance, there is an LED display machine controlled by SMS, and some vehicle tracking companies use SMS for their data transport or telemetry needs. SMS usage for these purposes is slowly being superseded by GPRS services due to their lower overall cost[citation needed]. GPRS is offered by smaller telco players as a route of sending SMS text to reduce the cost of SMS texting internationally.[34]

[edit] AT commands

Many mobile and satellite transceiver units support the sending and receiving of SMS using an extended version of the Hayes command set, a specific command language originally developed for the Hayes Smartmodem 300-baud modem in 1977.[citation needed]
The connection between the terminal equipment and the transceiver can be realized with a serial cable (i.e. USB), a Bluetooth link, an infrared link, etc. Common AT commands include AT+CMGS (send message), AT+CMSS (send message from storage), AT+CMGL (list messages) and AT+CMGR (read message).[35]
However, not all modern devices support receiving of messages if the message storage (for instance the device's internal memory) is not accessible using AT commands.

[edit] Premium-rated short messages

Short messages may be used to provide premium rate services to subscribers of a telephone network.
Mobile-terminated short messages can be used to deliver digital content such as news alerts, financial information, logos and ring tones. The first premium-rate media content delivered via the SMS system was the world's first paid downloadable ringing tones, as commercially launched by Saunalahti (later Jippii Group, now part of Elisa Group) in 1998. Initially only Nokia branded phones could handle them. By 2002 the ringtone business globally had exceeded one billion US dollars of service revenues, and nearly 5 billion dollars by 2008[citation needed].
The Value-added service provider (VASP) providing the content submits the message to the mobile operator's SMSC(s) using a TCP/IP protocol such as the short message peer-to-peer protocol (SMPP) or the External Machine Interface (EMI). The SMSC delivers the text using the normal Mobile Terminated delivery procedure. The subscribers are charged extra for receiving this premium content; the revenue is typically divided between the mobile network operator and the VASP either through revenue share or a fixed transport fee. Submission to the SMSC is usually handled by a third party such as Itelebill, Zong or Daopay.
Mobile-originated short messages may also be used in a premium-rated manner for services such as televoting. In this case, the VASP providing the service obtains a short code from the telephone network operator, and subscribers send texts to that number. The payouts to the carriers vary by carrier; percentages paid are greatest on the lowest-priced premium SMS services. Most information providers should expect to pay about 45% of the cost of the premium SMS up front to the carrier. The submission of the text to the SMSC is identical to a standard MO Short Message submission, but once the text is at the SMSC, the Service Center (SC) identifies the Short Code as a premium service. The SC will then direct the content of the text message to the VASP, typically using an IP protocol such as SMPP or EMI. Subscribers are charged a premium for the sending of such messages, with the revenue typically shared between the network operator and the VASP. Short codes only work within one country, they are not international.
An alternative to inbound SMS is based on long numbers (international number format, e.g. +44 762 480 5000), which can be used in place of short codes for SMS reception in several applications, such as TV voting, product promotions and campaigns. Long numbers work internationally, allow businesses to use their own numbers, rather than short codes which are usually shared across a lot of brands. Additionally, long numbers are non-premium inbound numbers.

[edit] SMS in satellite phone networks

All commercial satellite phone networks except ACeS and OptusSat support SMS[citation needed]. While early Iridium handsets only support incoming SMS, later models can also send messages. The price per message varies for different networks. Unlike some mobile phone networks, there is no extra charge for sending international SMS or to send one to a different satellite phone network. SMS can sometimes be sent from areas where the signal is too poor to make a voice call.
Satellite phone networks usually have web-based or email-based SMS portals where one can send free SMS to phones on that particular network. Other commercial service providers such as Targlets[36] allow for SMS on the +881 and +882 numbering plan prefix. Some other providers also cover the +870 plan.

[edit] Vulnerabilities

The Global Service for Mobile communications (GSM), with the greatest worldwide number of users, succumbs to several security vulnerabilities. In the GSM, only the airway traffic between the Mobile Station (MS) and the Base Transceiver Station (BTS) is optionally encrypted with a weak and broken stream cipher (A5/1 or A5/2). The authentication is unilateral and also vulnerable. There are also many other security vulnerabilities and shortcomings[37]. Such vulnerabilities are inherent to SMS as one of the superior and well-tried services with a global availability in the GSM networks. SMS messaging has some extra security vulnerabilities due to its store-and-forward feature, and the problem of fake sms that can be conducted via the Internet. When a user is roaming, SMS content passes through different networks, perhaps including the Internet, and is exposed to various vulnerabilities and attacks. Another concern arises when an adversary gets access to a phone and reads the previous unprotected messages [38].
In October 2005, researchers from Pennsylvania State University published an analysis of vulnerabilities in SMS-capable cellular networks.[39] The researchers speculated that attackers might exploit the open functionality of these networks to disrupt them or cause them to fail, possibly on a nationwide scale.

[edit] SMS spoofing

The GSM industry has identified a number of potential fraud attacks on mobile operators that can be delivered via abuse of SMS messaging services. The most serious of threats is SMS Spoofing. SMS Spoofing occurs when a fraudster manipulates address information in order to impersonate a user that has roamed onto a foreign network and is submitting messages to the home network. Frequently, these messages are addressed to destinations outside the home network – with the home SMSC essentially being “hijacked” to send messages into other networks.
The only sure way of detecting and blocking spoofed messages is to screen incoming mobile-originated messages to verify that the sender is a valid subscriber and that the message is coming from a valid and correct location. This can be implemented by adding an intelligent routing function to the network that can query originating subscriber details from the HLR before the message is submitted for delivery. This kind of intelligent routing function is beyond the capabilities of legacy messaging infrastructure.

MMS

Multimedia Messaging Service, or MMS, is a standard way to send messages that include multimedia content to and from mobile phones. It extends the core SMS (Short Message Service) capability that allowed exchange of text messages only up to 160 characters in length.
The most popular use is to send photographs from camera-equipped handsets, although it is also popular as a method of delivering news and entertainment content including videos, pictures, text pages and ringtones.
The standard is developed by the Open Mobile Alliance (OMA), although during development it was part of the 3GPP and WAP groups.

History

The immediate predecessor to the MMS is the Japanese picture messaging system Sha-Mail introduced by J-Phone in 2001. It validated the concept of camera phone users willing to send picture messages from one phone to another.
Early MMS deployments were plagued by technical issues and frequent consumer disappointments, such as having sent an MMS message, receiving a confirmation it had been sent, being billed for the MMS message, to find that it had not been delivered to the intended recipient. Pictures would often arrive in the wrong formats, and other media elements might be removed such as a video clip arriving without its sound.
At the MMS World Congress in 2004 in Vienna, all European mobile operator representatives who had launched MMS, admitted their MMS services were not making money for their networks. Also on all networks at the time, the most common uses were various adult oriented services that had been deployed using MMS.
China was one of the early markets to make MMS a major commercial success partly as the penetration rate of personal computers was modest but MMS-capable cameraphones spread rapidly. The chairman and CEO of China Mobile said at the GSM Association Mobile Asia Congress in 2009 that MMS in China is now a mature service on par with SMS text messaging.
Europe's most advanced MMS market has been Norway and in 2008 the Norwegian MMS usage level had passed 84% of all mobile phone subscribers. Norwegian mobile subscribers average one MMS sent per week.
By 2008 worldwide MMS usage level had passed 1.3 billion active users[1] who generated 50 billion MMS messages[2] and produced annual revenues of 26 billion dollars.[3]

[edit] Technical description

MMS messages are delivered in a completely different way from SMS. The first step is for the sending device to encode the multimedia content in a fashion similar to sending a MIME e-mail (MIME content formats are defined in the MMS Message Encapsulation specification). The message is then forwarded to the carrier's MMS store and forward server, known as the MMSC. If the receiver is on another carrier, the relay forwards the message to the recipient's carrier using the Internet.[4]
Once the MMSC has received a message, it first determines whether the receiver's handset is "MMS capable", that is it supports the standards for receiving MMS. If so, the content is extracted and sent to a temporary storage server with an HTTP front-end. An SMS "control message" containing the URL of the content is then sent to the recipient's handset to trigger the receiver's WAP browser to open and receive the content from the embedded URL. Several other messages are exchanged to indicate status of the delivery attempt.[5] Before delivering content, some MMSCs also include a conversion service that will attempt to modify the multimedia content into a format suitable for the receiver. This is known as "content adaptation".
If the receiver's handset is not MMS capable, the message is usually delivered to a web based service from where the content can be viewed from a normal internet browser. The URL for the content is usually sent to the receiver's phone in a normal text message. This behaviour is usually known as the "legacy experience" since content can still be received by a phone number, even if the phone itself does not support MMS.
The method for determining whether a handset is MMS capable is not specified by the standards. A database is usually maintained by the operator, and in it each mobile phone number is marked as being associated with a legacy handset or not. It can be a bit hit and miss since customers can change their handset at will and this database is not usually updated dynamically.
E-mail and web-based gateways to the MMS (and SMS) system are common. On the reception side, the content servers can typically receive service requests both from WAP and normal HTTP browsers, so delivery via the web is simple. For sending from external sources to handsets, most carriers allow MIME encoded message to be sent to the receiver's phone number with a special domain. An example of this would be PTN@messaging.carrier.com, where PTN is the public telephone number. Typically the special domain name is carrier specific.

[edit] Challenges

There are some interesting challenges with MMS that do not exist with SMS:

Handset configuration can cause problems sending and receiving MMS messages.
  • Content adaptation: Multimedia content created by one brand of MMS phone may not be entirely compatible with the capabilities of the recipient's MMS phone. In the MMS architecture, the recipient MMSC is responsible for providing for content adaptation (e.g., image resizing, audio codec transcoding, etc.), if this feature is enabled by the mobile network operator. When content adaptation is supported by a network operator, its MMS subscribers enjoy compatibility with a larger network of MMS users than would otherwise be available.
  • Distribution lists: Current MMS specifications do not include distribution lists nor methods by which large numbers of recipients can be conveniently addressed, particularly by content providers, called Value-added service providers (VASPs) in 3GPP. Since most SMSC vendors have adopted FTP as an ad-hoc method by which large distribution lists are transferred to the SMSC prior to being used in a bulk-messaging SMS submission, it is expected that MMSC vendors will also adopt FTP.
  • Bulk messaging: The flow of peer-to-peer MMS messaging involves several over-the-air transactions that become inefficient when MMS is used to send messages to large numbers of subscribers, as is typically the case for VASPs. For example, when one MMS message is submitted to a very large number of recipients, it is possible to receive a delivery report and read-reply report for each and every recipient. Future MMS specification work is likely to optimize and reduce the transactional overhead for the bulk-messaging case.
  • Handset Configuration: Unlike SMS, MMS requires a number of handset parameters to be set. Poor handset configuration is often blamed as the first point of failure for many users. Service settings are sometimes preconfigured on the handset, but mobile operators are now looking at new device management technologies as a means of delivering the necessary settings for data services (MMS, WAP, etc.) via over-the-air programming (OTA).
  • WAP Push: Few mobile network operators offer direct connectivity to their MMSCs for content providers. This has resulted in many content providers using WAP push as the only method available to deliver 'rich content' to mobile handsets. WAP push enables 'rich content' to be delivered to a handset by specifying the URL (via binary SMS) of a pre-compiled MMS, hosted on a content provider's web server. A consequence is that the receiver who pays WAP per kb or minute (as opposed to a flat monthly fee) pays for receiving the MMS, as opposed to only paying for sending one, and also paying a different rate.
Although the standard does not specify a maximum size for a message, 300 kB is the current recommended size used by networks due to some limitations on the WAP gateway side.[citation needed]

[edit] Interfaces


MMSC Reference Architecture
  • MM1: the 3GPP interface between MMS User Agent and MMS Center
  • MM2: the 3GPP interface between MMS Relay and MMS Server
  • MM3: the 3GPP interface between MMS Center and external servers
  • MM4: the 3GPP interface between MMS Centers
  • MM5: the 3GPP interface between MMS Center and HLR
  • MM6: the 3GPP interface between MMS Center and user databases
  • MM7: the 3GPP interface between MMS VAS applications and MMS Center
  • MM8: the 3GPP interface between MMS Center and the billing systems
  • MM9: the 3GPP interface between MMS Center and an online charging system
  • MM10: the 3GPP interface between MMS Center and a message service control function
  • MM11: the 3GPP interface between MMS Center and an external transcoder

GPRS

General packet radio service (GPRS) is a packet oriented mobile data service on the 2G and 3G cellular communication systems global system for mobile communications (GSM). The service is available to users in over 200 countries worldwide. GPRS was originally standardized by European Telecommunications Standards Institute (ETSI) in response to the earlier CDPD and i-mode packet switched cellular technologies. It is now maintained by the 3rd Generation Partnership Project (3GPP).[1][2].
It is a best-effort service, as opposed to circuit switching, where a certain quality of service (QoS) is guaranteed during the connection. In 2G systems, GPRS provides data rates of 56-114 kbit/second.[3] 2G cellular technology combined with GPRS is sometimes described as 2.5G, that is, a technology between the second (2G) and third (3G) generations of mobile telephony[4]. It provides moderate-speed data transfer, by using unused time division multiple access (TDMA) channels in, for example, the GSM system. GPRS is integrated into GSM Release 97 and newer releases.
GPRS usage charging is based on volume of data, either as part of a bundle or on a pay as you use basis. An example of a bundle is up to 5Gb per month for a fixed fee. Usage above the bundle cap is either charged for per megabyte or disallowed. The pay as you use charging is typically per megabyte of traffic. This contrasts with circuit switching data, which is typically billed per minute of connection time, regardless of whether or not the user transfers data during that period.

Services offered

GPRS extends the GSM circuit switched data capabilities and makes the following services possible:
If SMS over GPRS is used, an SMS transmission speed of about 30 SMS messages per minute may be achieved. This is much faster than using the ordinary SMS over GSM, whose SMS transmission speed is about 6 to 10 SMS messages per minute.

[edit] Protocols supported

GPRS supports the following protocols:[citation needed]
  • internet protocol (IP). In practice, mobile built-in browsers use IPv4 since IPv6 is not yet popular.
  • point-to-point protocol (PPP). In this mode PPP is often not supported by the mobile phone operator but if the mobile is used as a modem to the connected computer, PPP is used to tunnel IP to the phone. This allows an IP address to be assigned dynamically to the mobile equipment.
  • X.25 connections. This is typically used for applications like wireless payment terminals, although it has been removed from the standard. X.25 can still be supported over PPP, or even over IP, but doing this requires either a network based router to perform encapsulation or intelligence built in to the end-device/terminal; e.g., user equipment (UE).
When TCP/IP is used, each phone can have one or more IP addresses allocated. GPRS will store and forward the IP packets to the phone even during handover. The TCP handles any packet loss (e.g. due to a radio noise induced pause).

[edit] Hardware

Devices supporting GPRS are divided into three classes:
Class A
Can be connected to GPRS service and GSM service (voice, SMS), using both at the same time. Such devices are known to be available today.
Class B
Can be connected to GPRS service and GSM service (voice, SMS), but using only one or the other at a given time. During GSM service (voice call or SMS), GPRS service is suspended, and then resumed automatically after the GSM service (voice call or SMS) has concluded. Most GPRS mobile devices are Class B.
Class C
Are connected to either GPRS service or GSM service (voice, SMS). Must be switched manually between one or the other service.
A true Class A device may be required to transmit on two different frequencies at the same time, and thus will need two radios. To get around this expensive requirement, a GPRS mobile may implement the dual transfer mode (DTM) feature. A DTM-capable mobile may use simultaneous voice and packet data, with the network coordinating to ensure that it is not required to transmit on two different frequencies at the same time. Such mobiles are considered pseudo-Class A, sometimes referred to as "simple class A". Some networks are expected to support DTM in 2007.
Huawei E220 3G/GPRS Modem
USB 3G/GPRS modems use a terminal-like interface over USB 1.1, 2.0 and later, data formats V.42bis, and RFC 1144 and some models have connector for external antenna. Modems can be added as cards (for laptops) or external USB devices which are similar in shape and size to a computer mouse, or nowadays more like a pendrive.

[edit] Addressing

A GPRS connection is established by reference to its access point name (APN). The APN defines the services such as wireless application protocol (WAP) access, short message service (SMS), multimedia messaging service (MMS), and for Internet communication services such as email and World Wide Web access.
In order to set up a GPRS connection for a wireless modem, a user must specify an APN, optionally a user name and password, and very rarely an IP address, all provided by the network operator.

[edit] Coding schemes and speeds

The upload and download speeds that can be achieved in GPRS depend on a number of factors such as:
  • the number of BTS TDMA time slots assigned by the operator
  • the channel encoding used.
  • the maximum capability of the mobile device expressed as a GPRS multislot class

[edit] Multiple access schemes

The multiple access methods used in GSM with GPRS are based on frequency division duplex (FDD) and TDMA. During a session, a user is assigned to one pair of up-link and down-link frequency channels. This is combined with time domain statistical multiplexing; i.e., packet mode communication, which makes it possible for several users to share the same frequency channel. The packets have constant length, corresponding to a GSM time slot. The down-link uses first-come first-served packet scheduling, while the up-link uses a scheme very similar to reservation ALOHA (R-ALOHA). This means that slotted ALOHA (S-ALOHA) is used for reservation inquiries during a contention phase, and then the actual data is transferred using dynamic TDMA with first-come first-served scheduling.

[edit] Channel encoding

Channel encoding is based on a convolutional code at different code rates and GMSK modulation defined for GSM. The following table summarises the options:
 Coding
scheme
 Speed
(kbit/s)
CS-1 8.0
CS-2 12.0
CS-3 14.4
CS-4 20.0
The least robust, but fastest, coding scheme (CS-4) is available near a base transceiver station (BTS), while the most robust coding scheme (CS-1) is used when the mobile station (MS) is further away from a BTS.
Using the CS-4 it is possible to achieve a user speed of 20.0 kbit/s per time slot. However, using this scheme the cell coverage is 25% of normal. CS-1 can achieve a user speed of only 8.0 kbit/s per time slot, but has 98% of normal coverage. Newer network equipment can adapt the transfer speed automatically depending on the mobile location.
In addition to GPRS, there are two other GSM technologies which deliver data services: circuit-switched data (CSD) and high-speed circuit-switched data (HSCSD). In contrast to the shared nature of GPRS, these instead establish a dedicated circuit (usually billed per minute). Some applications such as video calling may prefer HSCSD, especially when there is a continuous flow of data between the endpoints.
The following table summarises some possible configurations of GPRS and circuit switched data services.
 Technology   Download (kbit/s)   Upload (kbit/s)   TDMA Timeslots allocated 
CSD 9.6 9.6 1+1
HSCSD 28.8 14.4 2+1
HSCSD 43.2 14.4 3+1
GPRS 80.0 20.0 (Class 8 & 10 and CS-4) 4+1
GPRS 60.0 40.0 (Class 10 and CS-4) 3+2
EGPRS (EDGE) 236.8 59.2 (Class 8, 10 and MCS-9) 4+1
EGPRS (EDGE) 177.6 118.4 (Class 10 and MCS-9) 3+2

[edit] Multislot Class

The multislot class determines the speed of data transfer available in the Uplink and Downlink directions. It is a value between 1 to 45 which the network uses to allocate radio channels in the uplink and downlink direction. Multislot class with values greater than 31 are referred to as high multislot classes.
A multislot allocation is represented as, for example, 5+2. The first number is the number of downlink timeslots and the second is the number of uplink timeslots allocated for use by the mobile station. A commonly used value is class 10 for many GPRS/EGPRS mobiles which uses a maximum of 4 timeslots in downlink direction and 2 timeslots in uplink direction. However simultaneously a maximum number of 5 simultaneous timeslots can be used in both uplink and downlink. The network will automatically configure the for either 3+2 or 4+1 operation depending on the nature of data transfer.
Some high end mobiles, usually also supporting UMTS also support GPRS/EDGE multislot class 32. According to 3GPP TS 45.002 (Release 6), Table B.2, mobile stations of this class support 5 timeslots in downlink and 3 timeslots in uplink with a maximum number of 6 simultaneously used timeslots. If data traffic is concentrated in downlink direction the network will configure the connection for 5+1 operation. When more data is transferred in the uplink the network can at any time change the constellation to 4+2 or 3+3. Under the best reception conditions, i.e. when the best EDGE modulation and coding scheme can be used, 5 timeslots can carry a bandwidth of 5*59.2 kbit/s = 296 kbit/s. In uplink direction, 3 timeslots can carry a bandwidth of 3*59.2 kbit/s = 177.6 kbit/s.[5]

[edit] Multislot Classes for GPRS/EGPRS

 Multislot Class   Downlink TS   Uplink TS   Active TS 
1 1 1 2
2 2 1 3
3 2 2 3
4 3 1 4
5 2 2 4
6 3 2 4
7 3 3 4
8 4 1 5
9 3 2 5
10 4 2 5
11 4 3 5
12 4 4 5
30 5 1 6
31 5 2 6
32 5 3 6
33 5 4 6
34 5 5 6

[edit] Attributes of a multislot class

Each multislot class identifies the following:
  • the maximum number of Timeslots that can be allocated on uplink
  • the maximum number of Timeslots that can be allocated on downlink
  • the total number of timeslots which can be allocated by the network to the mobile
  • the time needed for the mobile phone to perform adjacent cell signal level measurement and get ready to transmit
  • the time needed for the MS to get ready to transmit
  • the time needed for the MS to perform adjacent cell signal level measurement and get ready to receive
  • the time needed for the MS to get ready to receive.
The different multislot class specification is detailed in the Annex B of the 3GPP Technical Specification 45.002 (Multiplexing and multiple access on the radio path)

[edit] Usability

The maximum speed of a GPRS connection offered in 2003 was similar to a modem connection in an analog wire telephone network, about 32-40 kbit/s, depending on the phone used. Latency is very high; round-trip time (RTT) is typically about 600-700 ms and often reaches 1 s. GPRS is typically prioritized lower than speech, and thus the quality of connection varies greatly.
Devices with latency/RTT improvements (via, for example, the extended UL TBF mode feature) are generally available. Also, network upgrades of features are available with certain operators. With these enhancements the active round-trip time can be reduced, resulting in significant increase in application-level throughput speeds.

Monday, November 8, 2010

3G spectrum

3G Spectrum

When you read about radio spectrum this means a range of radio frequencies. The bandwidth of a radio signal is defined as being the difference between the upper and lower frequencies of the signal. For example, in the case of a voice signal having a minimum frequency of 300 hertz (Hz) and a maximum frequency of 3,300 Hz, the bandwidth is 3,000 Hz (3 KHz).
The amount of bandwidth needed for 3G services could be as much as 15-20 MHz. Compare this with the bandwidth of 30-200 KHz used for current 2G communication and you can see that there is as much as a 500-fold increase in the amount of bandwidth required. Now you can appreciate why radio spectrum has become such a precious and scarce resource in the information age - everybody from television broadcasters to the military wants spectrum, and it is in short supply. Michael Powell, the chairman of the U.S. Federal Communications Commission (FCC), has suggested that spectrum demand "is going to forever outstrip supply". The telecoms operators have had to buy 3G spectrum from governments around the world, and those governments - realising that they own a precious, valuable resource - have sought to sell that spectrum at the highest possible price.
Radio spectrum is often organised (and sold) as paired spectrum - a bit of spectrum in a lower frequency band, and a bit of spectrum in an upper frequency band (see the section on 3G Technology for an explanation of paired spectrum). Paired spectrum is often specified in a form like "2x15MHz" meaning 15MHz in a lower band and 15MHz in an upper band. This technique of two users talking to each other on two separate frequencies is called Frequency Division Duplex, or FDD (see the section on 3G Technology for an explanation of FDD). W-CDMA is an FDD technique (i.e., it requires paired spectrum) whereas TD-CDMA is a TDD technique (i.e., it can use unpaired spectrum).

Europe

CDMA2000 1X is very flexible in its spectrum requirements being designed to operate on all existing allocated spectrum for wireless communications. Unfortunately, the same cannot be said for UMTS which is quite specific about its spectrum requirements (this has resulted in the recent European bidding wars for UMTS spectrum). It has been suggested that choosing the rigid spectrum requirement for UMTS was a political move, aimed at creating a new export engine for Europe. CDMA2000's spectrum flexibility is one reason why the operational 3G systems have so far used CDMA2000 1X (also because CDMA2000 systems are being implemented on existing CDMA (CDMAone) networks).
UMTS specifies the bands 1900-2025 MHz and 2110-2200 MHz for 3G transmission. The satellite service uses the bands 1980-2010 MHz (uplink), and 2170-2200 MHz (downlink). This leaves the 1900-1980 MHz, 2010-2025 MHz, and 2110-2170 MHz bands for terrestrial UMTS (see the diagram below):


Terrestrial UMTS Bands
Diagram based on UK Official Licence Auction Site: Information Memorandum (3G Mobile Appendix)

As can be seen from the diagram, UMTS FDD is designed to operate in paired frequency bands, with uplink in the 1920-1980 MHz band, and downlink in the 2110-2170 MHz band. UMTS TDD is left with the unpaired frequency bands 1900-1920 MHz, and 2010-2025 MHz.
The UK Government auctioned five licences in these UMTS bands (for details, see the official UK licence auction site). After 150 rounds of bidding, the licences were sold for extraordinary sums (let's just say the "Buy-2-Get-1-Free" offer did not prove popular ...):


Licence Name Frequencies Winner Final Amount Bid
Licence A (reserved for a new entrant to the industry) 2x15 MHz paired spectrum plus 5 MHz unpaired spectrum Hutchison 3G £4,384,700,000
Licence B 2x15 MHz paired spectrum Vodafone £5,964,000,000
Licence C 2x10 MHz paired spectrum plus 5 MHz unpaired spectrum BT £4,030,100,000
Licence D 2x10 MHz paired spectrum plus 5 MHz unpaired spectrum One2One £4,003,600,000
Licence E 2x10 MHz paired spectrum plus 5 MHz unpaired spectrum Orange £4,095,000,000


It is possible to show the position of these licences (A, B, C, D, and E) in the paired spectrum diagram (you can see that some licences were for 10 MHz and some licences were for 15 MHz):



Why did these licences go for so much money? One answer is that the auction was very cleverly structured. Read about Professor Ken Binmore and his game theory. Professor Binmore explains how Sotheby's mistakenly auctioned American satellite transponders in sequential fashion, as if they were selling paintings. As a result, the transponders went for wildly different prices. This is clearly not ideal if you want to raise the maximum total amount of money at your auction. By using many rounds of bidding, Professor Binmore's auction design ensured that the final winning bids were quite close in value - pulling in loadsamoney for the UK Government.

USA

As has just been explained, in Europe and Asia the choice of frequency band for implementing UMTS was clear. However, these frequency bands were not available in the U.S., so at the World Radio Conference (WRC-2000) in Instanbul, Turkey in May 2000, three frequency bands were suggested for implementing UMTS in the United States. The bands suggested were:
  • the 806-890 MHz band (now being used for cellular and other mobile services),
  • the 1710-1885 MHz band (largely used by the U.S. Department of Defense),
  • the 2500-2690 MHz band (used by commercial users for instructional TV and wireless data providers).
As you can see, the problem for the U.S. was that all of the suggested bands were currently being used for other purposes. This was a worry for the U.S. - would this prove to be a major hindrance for the adoption of 3G in the U.S., thus allowing Europe and Asia to take the lead? As a result, on October 13th, 2000, President Clinton issued a Presidential Memorandum which initiated a study into the availability of extra spectrum in the USA.
On March 30th, 2001, the FCC produced their final report into the possibility of using the 2500-2690 MHz band for 3G transmission (for more details, see the FCC 3G site). Basically, they thought that the TV industry was very heavily entrenched in this band and it would take between $10.2 billion and $30.4 billion to relocate the incumbent users.
The NTIA (National Communications and Information Administration) was given the task of evaluating the 1755-1850 MHz band for possible 3G transmission (for more details, see the NTIA 3G site). The NTIA reported that the U.S. Army and Navy have refused to move their communications to another frequency band. As a result of the September 11th attacks, there was considerable resistance to any further reduction in military spectrum.
A new plan, known as the "3G Viability Assessment", was proposed to consider the availability of the 1710-1770 MHz band, and the 2110-2170 MHz band. The result of that assessment is that 45MHz of space in the 1710-1755 MHz band and 45 Mhz of space in the 2110-2170 band is to be made available for 3G services.

social media buttons