Mobile messaging technologies and services sms ems and mms phần 10 ppsx

TheWireless Village embedded client is a dedicated application embedded in a mobile device.This client communicates with the server over the Client Server Protocol CSP.. The Server-Mobil

† Presence and Instant Messaging Protocol (PRIM)

† SIP for Instant Messaging and Presence Leveraging Extensions (SIMPLE)

SIMPLE is an IMPS protocol based on the Session Initiation Protocol (SIP) [RFC-3261] and

is particularly well suited for UMTS phase 2 SIMPLE defines a mechanism for subscribing

to a service which manages subscriber status changes over a SIP network

The Wireless Village Initiative was recently set up by several manufacturers to considerthe support of IMPS in the mobile environment The prime objective of this initiative is todevelop an industry standard to guarantee interoperability between various IMPS servicesthat could be deployed in the near future The IMPS model, proposed by the Wireless Village,includes four primary features:

† Presence: this feature manages information such as device availability (e.g mobile devicehas been switched on/off, voice call under progress), user status (e.g available, not avail-able, having a meeting), user location, mobile device capabilities, personal status/moods(e.g happy, angry), etc To ensure confidentiality, presence information is providedaccording to user instructions only

† Immediate Messaging: this feature allows the exchange of messages delivered neously to the recipient(s) This means that, upon sending by the originator, the message isperceived as being immediately delivered to the message recipient(s) Compared withtraditional messaging services, instant messaging allows the establishment of interactivemessaging sessions between users These sessions are usually displayed using a threadedconversational interface, also known as chat

instanta-† Groups: this feature allows users to create and manage their own groups The manager of agroup can invite other users to chat with the group members Network operators can creategeneral interest groups

† Shared Content: this feature provides users with storage zones where pictures, audio andother multimedia contents can be posted and retrieved These contents can be sharedamong several users during group messaging sessions

The general architecture of the Wireless Village initiative solutions is depicted in Figure 7.1

In the architecture shown in the figure, the Wireless Village server is a central element Thisserver manages the following services: presence, instant messaging, groups and contentsharing Two types of Wireless Village clients can communicate with the server: the WirelessVillage embedded client and the Wireless Village Command Line Interface (CLI) client TheWireless Village embedded client is a dedicated application embedded in a mobile device.This client communicates with the server over the Client Server Protocol (CSP) On the otherhand, the Wireless Village CLI client uses text messages (e.g SMS) to communicate with theserver using the Command Line Protocol (CLP) A CLI client is usually a legacy mobiledevice Two Wireless Village servers, located in the same provider domain or in two distinctprovider domains, can communicate with the Server-Server Protocol (SSP) A WirelessVillage server may also be connected to a proprietary IMPS system via a proprietary gateway

In this configuration, the gateway transcodes SSP instructions into instructions supported bythe proprietary system, and vice versa The Server-Mobile Core Network Protocol (SMCNP)allows the server to obtain presence information and service capabilities from the mobile corenetwork In addition, the SMCNP can also be used for authentication and authorization ofusers, clients and servers

Wireless Village technical specifications can be downloaded from village.org.

http://www.wireless-7.2 Mobile Email

Email is the de facto messaging service on the Internet However, due to the bandwidthlimitations of mobile systems and the fact that mobile devices are seldom permanentlyconnected to the network, Email is not widely used in the mobile telecommunicationsdomain Nevertheless, several manufacturers have designed Email clients for mobile devicesusing standard Internet messaging protocols such as the Post Office Protocol-3 (POP3),defined in [RFC-1939] and the Interactive Mail Access Protocol (IMAP), defined in [RFC-1730] These solutions have the advantage of allowing mobile subscribers to communicateseamlessly with remote Internet users (using the same message formats and server accessprotocols) However, these solutions have proven to be very impractical to use without aminimum adaptation to the constraints of mobile devices and networks The major barriers tothe success of these solutions are the ‘pull’ model for retrieving messages which requiresfrequent accesses to the Email server and the fact that server access protocols are not resourceefficient

In order to offer an Email service adapted to the requirements of mobile subscribers, thecompany Research in Motion (RIM) designed a set of extensions for the existing Emailservice This extended Email service, offered to subscribers under the denomination ‘Black-berry service’, bypasses Email inadequacies to the mobile domain by enabling:

† a ‘push’ model for message retrieval

† a compression of messages

† an encryption of messages

Two main configurations are available for the Blackberry service The first configuration

Figure 7.1 General Wireless Village architecture

limits the impact on existing Email architectures by integrating a ‘desktop’ Blackberryapplication (the Blackberry desktop redirector) in the user’s personal computer used foraccessing Email messages When the user is on the move, the desktop application interceptsincoming messages, compresses them, encrypts them and pushes them to the Blackberrydevice via a mobile network The other way round, the user can compose a new message withthe Blackberry device The message is compressed and encrypted by the device and sent viathe mobile network to the desktop application The desktop application receives the message(by polling the Email server), decompresses and decrypts it and sends it normally to themessage recipients as if the message had been sent out directly by the user from his/herpersonal computer A more sophisticated configuration of the Blackberry service consists ofinstalling an extension to the Email server itself (the Blackberry enterprise server) Basically,

in the second configuration, the user’s personal computer does not have to be left runningwhen the user is on the move With this configuration, messaging functions performed by thedesktop application in the first configuration are performed here by the server extension Inaddition, this configuration also allows the synchronization of calendaring and schedulingdata between shared corporate databases and remote Blackberry devices The enterpriseconfiguration of the Blackberry service is depicted in Figure 7.2

The Blackberry service is already available in North America and is currently beingdeployed in other countries in Europe (United Kingdom and France) The service fulfilsparticularly well the needs of itinerant professional users, who avoid using laptop computerswhile on the move (because of long dial-up time for accessing Email servers, etc.) TheMultimedia Messaging Service (MMS), described in the previous chapter, targets the massmarket by supporting a messaging service, similar to the Email service, with small handsets

On the other hand, the Blackberry service targets the professional market with devices

Figure 7.2 The Blackberry service configuration

designed as Personal Digital Assistants More information can be obtained on the Blackberryservice from Research in Motion (RIM) at http://www.rim.com and Blackberry service athttp://www.blackberry.net.

7.3 IMS Messaging

Chapter 1 introduced the two phases for UMTS The second phase of UMTS is built on theIP-based Multimedia Service (IMS) based on the Session Initiation Protocol (SIP) for session/call management The 3GPP recently initiated work on messaging services based on acombination of IMS service capabilities (e.g presence) and already defined messagingservices (SMS, EMS and MMS) The scope of this work initially consists of identifying(in the release 6 timeframe) the requirements for messaging services in the IMS environment.These requirements will be detailed in the technical report [3GPP-22.940]

A TP-PID Values for Telematic Interworking

For enabling SMS interworking with various telematic devices, the set of protocol identifiers(TP-Protocol-Identifier) listed in Table 1 can be used

Table 1 Protocol identifiers for telematic interworking

TP-PID value (hex) Description

0x20 Type of telematic device is defined by the message

destination or originator address

0x21 Telex (or teletex reduced to telex format)

0x24 Voice telephone (i.e conversion to speech)

0x25 European Radio Messaging System (ERMES)

0x26 National paging system (type known to the service centre)

0x2D Universal Computer Interface (UCI)

0x2E…0x2F Reserved (2 values)

0x30 Message handling facility (type known to the service centre)

0x31 Public X.400-based message handling system

0x33…0x37 Reserved (5 values)

0x38…0x3E SC specific use (7 values)

0x3F GSM or UMTS mobile station The SMSC converts the

short message into a coding scheme which isunderstandable by the GSM/UMTS mobile station

B Numeric and Alphanumeric Representations/SMS

Various numeric values can be assigned to the parameters of an SMS TPDU In this context,numeric values can be represented in three different ways:

† 1st rule: octets with the lowest octet indexes contain the most significant bits

† 2nd rule: bits with the highest bit indexes are the most significant bits

The example in Figure 1 shows how the decimal number 987 351 is represented

B.2 Octet Representation

With the octet representation, a numeric value is represented with one or more completeoctets where each octet represents one decimal digit The only rule to apply is that octets withthe lowest octet indexes contain the most significant decimal digits Each octet can take thevalues listed in Table 2 All other octet values are reserved The example in Figure 2 showshow the decimal value 43 is represented

Figure 1 Integer representation/example

B.3 Semi-octet Representation

With the semi-octet representation, a numeric value is represented with one or more octets (4 bits) For such a representation, the following rules apply:

half-† 1st rule: octets with the lowest octet indexes contain the most significant decimal digits

† 2nd rule: within one octet, the half-octet with bits numbered 0–3 represents the mostsignificant digit

Each half-octet can take the values listed in Table 3 The example in Figure 3 shows how thedecimal value 431 is represented with four semi-octets

Figure 2 Octet representation/example

Table 2 Octet representation

Octet value Decimal digit

C Character Sets and Transformation Formats

C.1 GSM 7-bit Default Alphabet

Table 4 presents all the characters in the GSM 7-bit default alphabet Each character isrepresented with a septet (7 bits) for which the most significant bit is b7 and the leastsignificant bit is b1

Table 3 Semi-octet representation

Half-octet value Decimal digit

Table 4 GSM 7 bit alphabet (first table)a

C.3 Universal Character Set

The ISO has defined in [ISO-10646] the Universal Character Set (UCS), a multi-octet acter set for representing most of the world’s writing symbols Two encoding methods areavailable for UCS:

char-† UCS2: a two-octet per symbol encoding

† UCS4: a four-octet per symbol encoding

UCS2 and UCS4 are difficult to use in systems on 7-bit and 8-bit transport To cope with thesedifficulties, UCS transformation formats have been developed These formats are defined inthe following sections

C.4 UCS Transformation Formats

The most commonly used UCS Transformation Formats (UTF) are:

† UTF8 [RFC-2279]: this transformation format is 8-bit aligned and has the key istic of preserving the US-ASCII value range UTF8 encodes UCS2 and UCS4 with one ormore octets per symbol (1 to 6 octets)

character-† UTF16: this transformation format is 16-bit aligned UTF16 transforms UCS4 symbolsinto pairs of UCS2 values

Symbols represented by one octet in UTF8 are US-ASCII characters In this configuration,the most significant bit of the octet is set to 0 For other symbols represented with n octets,then the n most significant bits of the first octet representing the symbol are set to 1 Forremaining octets, the most significant bit is set to 1 and the second most significant bit is set to

0 Table 7 summarizes the relationships between UTF8 and UCS4:

Table 7 Relationships between UTF8 and UCS4

UTF8 octet sequence

(binary)

UCS4 range (hexadecimal) Description

0xxxxxxx 0000 0000 to 0000 007F Used to encode US-ASCII symbols

over 1 octet110xxxxx 10xxxxxx 0000 0080 to 0000 07FF Used to encode symbols over 2 octets1110xxxx 10xxxxxx

10xxxxxx 0000 0800 to 0000 FFFF Used to encode symbols over 3 octets11110xxx 10xxxxxx

10xxxxxx 10xxxxxx 0001 0000 to 001F FFFF Used to encode symbols over 4 octets111110xx 10xxxxxx

D iMelody Grammar

The iMelody format is used in EMS and MMS messaging systems The BNF grammar of theiMelody format (version 1.2) is given below:

<imelody-object> = "BEGIN:IMELODY"< cr> < line-feed>

"VERSION:"< version> < cr><line-feed>

"FORMAT:"< format> < cr><line-feed>

["NAME:"< characters-not-lf>< cr> feed>]

<["COMPOSER:"< characters-not-lf> < cr>< feed>]

line-["BEAT:"< beat> < cr> <line-feed> ]["STYLE:"< style> < cr> <line-feed> ]["VOLUME:"< volume> < cr> < line-feed> ]

"MELODY:"< melody> < cr><line-feed>

< basic-note> = "c" | "d" | "e" | "f" | "g" | "a" | "b"

< flat-note> = "&d" | "&e" | "&g" | "&a" | "&b"

< led> = "ledoff" | "ledon"

< vibe> = "vibeon" | "vibeoff"

< backlight> = "backon" | "backoff"

< full-note> = [< octave-prefix> ] < note> < duration>

[< duration-specifier> ]

< silence> = < rest> < duration> [< duration-specifier]

< repeat> = "("{<silence> | < full-note> | <led> | < vib> |

< volume> | < backlight> }+ "@" < repeat-count>[< volume-modifier> ] ")"

<repeat-count> = "0" | "1" | "2" | …

<melody> = {<silence> | <full-note> | <led> | < vib> |

< repeat> |< volume> | <backlight> }+

< characters-no-lf> = Any character in the US-ASCII character-set

except<line-feed>

E MMS Binary Encoding for MMS PDUs

The process of representing the parameters of an MMS PDU in a binary form for transfer overthe MM1 interface is called encapsulation and is defined in [WAP-209] for MMS 1.0 and[WAP-276] for MMS 1.1 Table 8 gives a summary of binary representations for all MMSPDU parameters

Table 8 Encapsulation of MMS PDU parameters

number

Binary encoding

[WAP-203].

ind

m-notification-0x82 (decimal 130)

ind

0x82 (decimal 130)

Deleted without being read

0x81 (decimal 129)

Accepted text only

0x83 (decimal 131) X-Mms-Reply-Charging-

Deadline

Internet links/organizations involved in the development of standards

European Telecommunications Standard Institute (ETSI) http://www.etsi.org

International Telecommunication Union (ITU) http://www.itu.org

Internet Engineering Task Force http://www.ietf.org

MIDI Manufacturers Association (MMA) http://www.midi.org

Third Generation Partnership Project (3GPP) http://www.3gpp.org

World Wide Web Consoritum (W3C) http://www.w3c.org

Open Mobile Alliance (OMA) http://www.openmobilealliance.org

Documents

3GPP Documents

[3GPP-11.11] 3GPP TR 11.11: Specification of the SIM-ME interface

[3GPP-21.101] 3GPP TS 21.101: 3rd generation mobile system release 1999 specifications.[3GPP-21.102] 3GPP TS 21.102: 3rd generation mobile system release 4 specifications.[3GPP-21.103] 3GPP TS 21.103: 3rd generation mobile system release 5 specifications.[3GPP-21.900] 3GPP TR 21.900: 3GPP working methods

[3GPP-21.905] 3GPP TR 21.905: Vocabulary for 3GPP specifications

[3GPP-21.910] 3GPP TS 21.910: Multi-mode UE issues: categories, principles and procedures.[3GPP-22.060] 3GPP TS 22.060: General Packet Radio Service (GPRS), stage 1

[3GPP-22.105] 3GPP TS 22.105: Services and service capabilities

[3GPP-22.121] 3GPP TS 22.121: The Virtual Home Environment (VHE), stage 1

[3GPP-22.127] 3GPP TS 22.127: Open Service Access (OSA), stage 1

[3GPP-22.140] 3GPP TS 22.140: Multimedia Messaging Service (MMS), stage 1

[3GPP-22.141] 3GPP TS 22.141: Presence service, stage 1

[3GPP-22.228] 3GPP TS 22.228: Service requirements for the IP multimedia core network

subsys-tem, stage 1

[3GPP-22.940] 3GPP TS 22.940: IMS messaging, stage 1

[3GPP-23.002] 3GPP TS 23.002: Network architecture

[3GPP-23.011] 3GPP TS 23.011: Technical realization of supplementary services

[3GPP-23.038] 3GPP TS 23.038: Alphabets and language-specific information

[3GPP-23.039] 3GPP TR 23.039: Interface protocols for the connection of SMSCs to SMEs

[3GPP-23.040] 3GPP TS 23.040: Technical realization of the Short Message Service (SMS).[3GPP-23.042] 3GPP TS 23.042: Compression algorithm for text messaging services.

[3GPP-23.060] 3GPP TS 23.060: General Packet Radio Service (GPRS), stage 2

[3GPP-23.101] 3GPP TS 23.101: General UMTS architecture

[3GPP-23.127] 3GPP TS 23.127: Virtual Home Environment/Open Service Access, stage 2.[3GPP-23.140] 3GPP TS 23.140: Multimedia Messaging Service (MMS), stage 2

[3GPP-23.228] 3GPP TS 23.228: IP multimedia subsystem, stage 2

[3GPP-23.841] 3GPP TS 23.841: Presence service, stage 2

[3GPP-24.011] 3GPP TS 24.011: Point-to-point SMS support on mobile radio interface.[3GPP-26.140] 3GPP TS 26.140: Multimedia Messaging Service, media formats and codecs.[3GPP-26.233] 3GPP TS 26.233: Transparent end-to-end packet-switched streaming service.[3GPP-26.234] 3GPP TS 26.234: End-to-end transparent streaming service, protocols and codecs.[3GPP-27.005] 3GPP TS 27.005: Use of DTE-DCE interface for CBS

[3GPP-31.102] 3GPP TS 31.102: Characteristics of the USIM application

[3GPP-31.111] 3GPP TS 31.111: USIM Application Toolkit (USAT)

[3GPP-32.200] 3GPP TS 32.200: Charging management, charging principles

[3GPP-32.235] 3GPP TS 32.235: Charging management, charging data description for application

International Telecommunication Union (ITU) documents

[ITU-E.164] ITU-T E.164: The international public telecommunication numbering plan, ITU,

May 1997

[ITU-E.212] ITU-T E.212: The international identification plan for mobile terminals and mobile

users, ITU, November 1998

[ITU-H.263] ITU-T H.263: Video coding for low bit rate communication, ITU, February 1998.[ITU-I.130] ITU-T I.130: Method for the characterization of telecommunication services

supported by an ISDN and network capabilities of an ISDN, ITU, November 1988

IETF documents

[RFC-821] Simple Mail Transfer Protocol (SMTP), August 1982

[RFC-822] Standard for the format of ARPA Internet text messages, August 1982 Note that

this RFC is replaced by [RFC-2822]

[RFC-1730] Internet Message Access Protocol (IMAP), version 4, December 1994

[RFC-1766] Tags for the identification of languages, March 1995

[RFC-1806] Communicating presentation information in Internet messages: The

Content-Disposition header, June 1995

[RFC-1889] RTP: A Transport Protocol for Real-Time Applications, January 1996

[RFC-1939] (STD 0053) Post Office Protocol (POP), version 3, May 1996

[RFC-2026] The Internet Standards Process – Revision 3, October 1996

[RFC-2045] MIME Part 1: Format of Internet message bodies, November 1996

[RFC-2046] MIME Part 2: Media types, November 1996

[RFC-2047] MIME Part 3: Message header extensions for non-ASCII text, November 1996.[RFC-2048] MIME Part 4: Registration procedures, November 1996

[RFC-2049] MIME Part 5: Conformance criteria and examples, November 1996

[RFC-2279] UTF-8, a transformation format of ISO 10646, January 1998