Mms

Table of Contents
PRODUCT DESCRIPTION ALCATEL 1 >

Alcatel 5315 Nextenso MMS Proxy Relay
Release 2.0
Last update: November 19
th
2002
Product Description
Table of Contents
> 2 ALCATEL PRODUCT DESCRIPTION

1 Highlights and Benefice................................................................................................................... 4
2 Description....................................................................................................................................... 4
3 Software Architecture....................................................................................................................... 5
3.1 Components Description........................................................................................................................5
3.2 MMx Interfaces......................................................................................................................................6
1.1 Additional interfaces. .............................................................................................................................6
3.3 Proxylets description...............................................................................................................................7
3.3.1 MMS CODEC Proxylet...................................................................................................................7
3.3.2 MM7 Codec proxylet.....................................................................................................................7
3.3.3 MMS Access Control Proxylet.........................................................................................................8
3.3.4 MMS Content adaptor Proxylet......................................................................................................9
3.3.5 MMS Relay Proxylet.....................................................................................................................10
3.4 Store & Forward...................................................................................................................................11
1.2 Notification Control Function................................................................................................................12
1.3 Mail Server..........................................................................................................................................12
4 End-Users Data Base...................................................................................................................... 12
4.1 LDAP server.........................................................................................................................................12
4.2 Database Provisioning .........................................................................................................................12
4.2.1 Web Service Provisioning ............................................................................................................13
4.2.2 Mass provisioning.......................................................................................................................13
4.2.3 Self-provisioning.........................................................................................................................13
4.2.4 Subscription definition.................................................................................................................13
4.2.5 Subscription general attributes.....................................................................................................14
1.3.1 Phone attributes..........................................................................................................................14
4.2.6 MMBox attributes........................................................................................................................14
4.3 UaProf maintenance............................................................................................................................14
4.4 End-User management........................................................................................................................15
5 End-user profile management........................................................................................................ 15
6 VAS Support................................................................................................................................... 15
6.1 Authentication & authorization..............................................................................................................15
6.2 Charging information..........................................................................................................................16
7 Operator Services........................................................................................................................... 16
7.1 Billing and CDR...................................................................................................................................16
7.2 Statistics..............................................................................................................................................17
7.3 Operation and Maintenance................................................................................................................18
Table of Contents
1.3.2 Monitoring.................................................................................................................................19
1.3.3 MMS configuration parameters....................................................................................................19
7.3.1 Features inherited from Nextenso Proxy Platform..........................................................................19
8 Nextenso Proxy Platform................................................................................................................ 19
9 IOT.................................................................................................................................................. 21
10 Performances........................................................................................................................... 21
2 Operating system and minimal hardware requirements................................................................ 21
11 Annex A: Scope Of Compliance................................................................................................ 22
11.1 MM Submission And Retrieval ..........................................................................................................24
11.2 Addressing And Routing..................................................................................................................25
11.3 Storage...........................................................................................................................................26
11.4 Interfaces........................................................................................................................................26
11.5 Formats And Conversions................................................................................................................27
11.6 User Profile Management................................................................................................................27
11.7 OAM..............................................................................................................................................28
1.1. VAS Support........................................................................................................................................28
1.2. IOTs....................................................................................................................................................29
1.3. Miscellaneous......................................................................................................................................29
12 Annex B: Environmental compliance........................................................................................ 30
12.1 Environment Characteristics.............................................................................................................30
12.2 Environmental Requirements............................................................................................................30
1 Highlights and Benefice
> Works with any legacy WAP gateway that has a PAP compliant push proxy and that supports WSP 1.3
encoding
> Compliant with any legacy mail server
> Runs on a PC under Linux
> Fully compliant with the 3GPP architecture and the Open Mobile Alliance specifications
> Relies on the Nextenso Proxy platform
2 Description

Alcatel MMS Proxy Relay is the core component of Alcatel 8685 Multimedia Messaging Services. This is the
only required component to MMS enable a mobile network. It respects the 3GPP architecture as described in
TS23.140 V540 and the WAP Forum specifications WAP-205-MMSArchOverview-20010425-a (WAP 205 April
2001), WAP-206-MMSCTR-20020115-a (WAP 206 J anuary 2002), WAP-209- MMSEncapsulation-
20020105-a (WAP 209 J anuary 2002).
WAP Gateway: WAP 1.2 avec SAR, WSP 1.3 encoding, MMS encoding WAP 209.

Added in an existing infrastructure that has a WAP Gateway, a Push Proxy Gateway, and an E-mail server
(optional) Alcatel MMS Proxy Relay provides the required functionalities so that end-users registered in the
same mobile network, or in a foreign MMS enabled mobile network, can exchange MMs. It also allows
machine-to-person messaging for web-based MMS Applications.
P
u
s
h

P
r
o
x
y
W
A
P

G
a
t
e
w
a
y
N
x

M
M
S

p
r
o
x
y

R
e
l
a
y
E
-
m
a
i
l

S
e
r
v
e
r

(
o
p
t
i
o
n
a
l
)

Figure 1: General Overview

Alcatel MMS Proxy Relay is part of A8685 Alcatel Multimedia Messaging Services, which also implements the
Alcatel MMBox for providing network storage functionalities as well as unified access to the messages and the
Alcatel MMS Apps-in-a-Box. As such, the MMS Proxy Relay can be bundled with other Alcatel products such as
Nextenso WAP Gateway, Nextenso Push Proxy Gateway, Nextenso Charging Proxy for implementing various
billing policies
See A8685 Alcatel Multimedia Messaging Services Product Description for more details, or respective PDS for
each product.
3 Software Architecture

3.1 Components Description

Nextenso MMS Proxy Relay is based on Nextenso Proxy platform and is composed of the following proxylets:
>
> MMS CODEC Proxylet encodes and decodes MM,
> MM7 CODEC Proxylet is used when a VAS application sends an MMS,
> MMS Addressing Control Proxylet checks the access rights of the end-users
> MMS Access Control Proxylet to check the access rights of the end-users,
> MMS Content Adaptor to format the retrieved MM depending on the recipient devices and based on the
UAProf information,
> MMS Relay proxylet does the relevant address translation and encodes the MM in a valid MIME format
prior to delivery, and processes the delivery on the matching interface (e.g. mm2, MM3, or mm4),

M
M
S

A
c
c
e
s
s

C
o
n
t
r
o
l
M
M
S

A
c
c
e
s
s

C
o
n
t
r
o
l
M
M
S

C
O
D
E
C
M
M
S

C
O
D
E
C
M
M
S

R
e
l
a
y
M
M
S

R
e
l
a
y
M
M
S

C
o
n
t
e
n
t

A
d
a
p
t
o
r
M
M
S

C
o
n
t
e
n
t

A
d
a
p
t
o
r
Alcatel MMS Proxy Relay
M
M
7

C
O
D
E
C
M
M
7

C
O
D
E
C

Figure 2: Nextenso MMS Proxy Relay Proxylet Set

3.2 MMx Interfaces
Nextenso MMS Proxy Relay implements the following interfaces as described in the 3GPP specification.

Interface
Description Protocol
MM1 Interface between the MMS User Agent and the
MMS Relay/Server
HTTP
WAP 2.0
MM2
Interface between the MMS Relay and the MMS
Server
SMTP
MM3 Interface between the MMS Relay/Server and
external messaging systems
SMTP, IMAP4,
POP3
MM4 Interface between the MMS Relay/Server and
foreign MMS Relay/Server
SMTP
MM5 Interface between the MMS Relay/Server and the
Home Location Register (HLR)
DNS-ENUM
MMS User Database
LDAP, Java API
Value-Added Services (VAS) applications
SOAP/HTTP
MM8 Interface between the MMS Relay/server and a
billing system
XML/HTTP

1.1 Additional interfaces.
Configuration, alarms : HTML
Statistics and alarms :SNMP
Provisioning : HTML (web), RLOGIN (mass), MM6 (LDAP)
Billing : FTP for CDR collection, MM8 for real time prepaid


Figure 3: Nextenso MMS Proxy Relay mm Interfaces

3.3 Proxylets description

Each proxylet of Alcatel MMS proxy relay is a component with a dedicated function, as described bellow.

3.3.1 MMS CODEC Proxylet

This proxylet encodes and decodes MM before forwarding it to other proxylets :
- The body of a MM received by the WAP GW is encoded. The proxylet decodes it and converts it into a
standard MIME formatted message.
- When delivering a message to a MMS user Agent, this proxylet performs the encoding of the MM, and
forwards it to the WAP GW.

3.3.2 MM7 Codec proxylet

This proxylet is the VAS proxylet (Value added Services). It handles the VAS traffic and provides the access
point to Value Added Services. It receives incoming requests in http and forwards them in the relay for delivery.
It enables VASP (Value added Services Providers) to send/receive MM to/from the MMS Proxy Relay.
LDAP
M
M
S

A
c
c
e
s
s

C
o
n
t
r
o
l
M
M
S

A
c
c
e
s
s

C
o
n
t
r
o
l
M
M
S

C
O
D
E
C
M
M
S

C
O
D
E
C
M
M
S

R
e
l
a
y
M
M
S

R
e
l
a
y
M
M
S

C
o
n
t
e
n
t

A
d
a
p
t
o
r
M
M
S

C
o
n
t
e
n
t

A
d
a
p
t
o
r
Alcatel MMS Proxy Relay
M
M
7

C
O
D
E
C
M
M
7

C
O
D
E
C
MM6
MM3 (in)
MM4 (in)
MM1 (in)
MM7
HTTP
SOAP
MM3 (out)
MM4 (out)
MM1 (out)

Figure 4: MM7 Codec Proxylet

3.3.3 MMS Access Control Proxylet

The purpose of this proxylet consists into checking the profile of the originator of the MM. This proxylet is
retrieving the information from the LDAP database, which contains the end-user profile information, using the
end-user MSISDN.
The proxylet checks MM senders rights before allowing a submission :
- It checks if the sender is known and active
- If may auto provision the sender if the sender is unknown, and authorized to be auto provisioned

M
M
7

C
O
D
E
C
M
M
7

C
O
D
E
C
MM7
HTTP
SOAP
A
c
c
e
s
s

C
o
n
t
r
o
l
A
c
c
e
s
s

C
o
n
t
r
o
l
mm6
LDAP
User User
d.b. d.b.
mm1
http

Figure 5: MMS Access Control Proxylet

This proxylet is also in charge of updating the end-user profile information when a MM is processed.

3.3.4 MMS Content adaptor Proxylet

The purpose of this proxylet is to adapt the content of a MM according to the receivers terminal capacities.
When a receiver is trying to fetch a MM, the content adaptation proxylet uses the UaProf of the receivers
terminal to determine the capacities of the device. Depending on these capacities and on the multimedia
content of the MM, a set of content adaptation operation is performed in order to make sure that the receiver
will see the MM properly.

> The content adaptation proxylet can perform the picture adaptation itself. The matrix bellow shows the
supported conversions. Moreover, the content adaptor proxylet has the capacity to resize and rotate
pictures, if need be.
? Bmp Gif Jpg Tiff Wbmp Png
Bmp
Gif
Jpg
Tiff
Wbmp
Png

Figure 6: Picture Conversion Matrix (yellow cells indicate what is converted in what)


Content adaptation regarding sound conversion is depicted in the matrix below :

? Amr Mp3 Wav Pcm Midi eMelodie
Amr
Mp3
Wav
Pcm
Midi
eMelodie

Figure 7: Sound Conversion Matrix (yellow cells indicate what is converted in what)

3.3.5 MMS Relay Proxylet

The purpose of this proxylet consists into proceeding to the delivery of the MM, depending whether the receiver
is in the same PLMN or not, but also depending on the end-user preferences (typically, if a receiver wants to
have the MM forwarded to his MMBox or an external mail account).

In case the receiver is in an external PLMN, the proxylet forwards the MM over the mm4 interface. In case of
delivery failure, it handles the return notification.
The MMS Relay proxylet is also in charge of handling the lawful interception feature.


Figure 8: MMS Relay Proxylet
??

MMS Addressing is included in the MMS Relay Proxylet

This proxylet performs the static address resolution, i.e. :
- Based on the MSISDN of the sender, looks for the prefix associated internet domain name in the
conversion table,
- Concatenates the internet domain to the MSISDN before forwarding it to the Store and Forward.

3.4 Store & Forward
The Store and Forward performs the MMS service logic.
On receipt of a MM, it :
- Stores it in the Store and Forward Buffer, and eventually makes a copy in the MMBox according to
subscription settings.
- Triggers a notification request for recipients belonging to the MMSE. The notification request type is based
on the subscribers handset capabilities (legacy / MMS capable)
- Route forward MM when recipients belong to an external MMSE. (MM4)
- Delivers MM to recipients
- Forwards MM to an email address according to the subscription setting (MM3)
LDAP
M
M
S

R
e
l
a
y
M
M
S

R
e
l
a
y
MM6
MM3 (in)
MM4 (in)
MM1 (in)
MM3 (out)
MM4 (out)
MM1 (out)
- Generates delivery reports
- Manages MM expiry time

MM are received by the Store and Forward on the following streams :
- MM1 or MM7. In that case the stream comes from the MMS Proxylets.
- MM4 or MM3. In that case, the stream comes from the Mail server.

??
1.2 Notification Control Function
??
The NCF is a notification engine, which :
- Triggers notification requests to Delivery Services (such as PAP or SMS), at the requested time,
- Programs further attempts when Delivery Services are not available.

It is triggered by the Store and Forward.
??
??
??
1.3 Mail Server
The Mail Server is based on Courier and includes several components which perform :
- The SMTP server, enabling to receive an incoming SMTP stream (MM3, MM4)
- The IMAP/POP server, enabling to deliver MM on an email interface. This interface is used by the
Universal Mail Client (Web access to retrieve MM from MMBox).
??
??
??

4 End-Users Data Base

4.1 LDAP server
The LDAP Server stores the subscribers which are handled by the MMS Proxy Relay.
For each subscriber, it stores many attributes which describe the subscription settings.

4.2 Database Provisioning

The LDAP database holds the end-users information (such as his MSISDN, mail address, etc.) of the customers
of the operator, as well as their preferences. Typically, this information is going to be used to check the end-
users profiles and make the mapping between the MSISDN and a mail address.
There a three models for database provisioning:
> Web service provisioning
> Mass provisioning
> Self-provisioning
>
4.2.1 Web Service Provisioning

The Web Service Provisioning is designed for user per user provisioning.
It can be accessed from any Web browser by addressing the Web Service Provisioning URL, over a secured
HTTPS connection.
Access control to the application is achieved by a login / password authentication.

This application provides the following provisioning features :
- Create a new subscriber (based on a Profile or quality of service)
- Query the database to get information about an existing subscriber
- Update a subscription
- Delete a subscription.

4.2.2 Mass provisioning

Mass provisioning is designed to add many new subscribers in the database.
It is run on a command mode, and based on a LDIF file (LDAP is internally used to store the subscribers).

To add new subscribers, the following steps are done :
- firstly, create the LDIF file containing the list of subscribers to add. For each, a Profile and a MSISDN is at
least required.
- Secondly, connect to the server (rlogin with login and password control), and run an LDAP command to
take into account the LDIF file.

4.2.3 Self-provisioning

In that case, the end-user is provisioned when sending his first MM. When sending the first MM, the Access
Control proxylet checks whether the subscriber is registered in the operators network and, if thats the case,
provisions the MSISDN and the UAProf in the database. Following this operation a notification is sent to the
originator of the MM to advise him that he can access and complete his profile on-line, through the Web or
the WAP interface.

4.2.4 Subscription definition

Each subscription includes attributes which are gathered in 3 categories :
- Subscription general attributes
- Phone attributes
- Mmbox attributes

4.2.5 Subscription general attributes

- Common name
- Account status
- Profile ID, referencing a subscription profile
- Languages list
- Web access login
- Web access password
- Email address
- Lawful interception indication
- Lawful interception copy address list
- Email forwarding indication
- Email forwarding address
- Subscription creation date
- Subscription expiration date

1.3.1 Phone attributes
- Phone number (MSISDN)
- Phone type
- UA Prof
- Phone capabilities
- Phone mobile model
- Description

4.2.6 MMBox attributes
- Fraudulent access number
- IMAP login
- IMAP password
- Mail store home directory
- Mail store Mmbox path
- Mmbox quota
- Mmbox name
- Display name
- Reply to address
- Signature

4.3 UaProf maintenance

Each time that an end-user sends a MM, the UAProf of his terminal is checked against the information stored
in the database. If need be, the UAProf information is updated in the database.
This allows having up-to-date information on the end-user terminal capacities, which is required when
receiving a MM.

4.4 End-User management

The operator has the capacity to access the end-user profiles database through a dedicated web-based
interface.
As an example, it allows him to manage the end-users by blocking the MM sending and receiving for an end-
user that hasnt paid.
This interface is also used by the customer care and support department to handle end-users support.
Typically, when an end-user calls the help line, the support team can access and update his profile through
this web-based interface.

5 End-user profile management

Alcatel MMS Proxy Relay has a Web based interface that allows each end-user to access his profile information
and make some modification.
J2EE App. Server
(ex: Apache/Tomcat)
User User
d.b. d.b.
End End- -User User
Profile Profile
Management Management

Figure 9: End-User profile Management

6 VAS Support

Alcatel MMS Proxy relay supports the delivery of MMs that are not end-user originated, but rather service
originated, as well as sending a MM to a service, instead of another user-agent.
This feature is provided through the MM7 interface, as described in the 3GPP specification, and is
implemented in the MM7 Codec Proxylet.

6.1 Authentication & authorization

Each VAS that wishes to send a MM to a user-agent in the MMSE of the operator is authenticated. Each VAS
that is allowed to send MM is listed in a configuration file by a unique id, therefore, when a VAS tries to send a
MM, it has to send its id, which is then check against the id stored in the configuration file, thus allowing, or
not the MM to be processed.
The authorization process is also established at this moment.

6.2 Charging information

The MM7 Codec Proxylet also has the capacity to handle billing information. These information are handled
by Alcatel MMS Proxy Relay to logs that can be processed in the purpose of post-paid billing.
In the case of a VAS requiring pre-payment, Nextenso Charging Proxy is required: billing information are then
forwarded to the charging proxy and will acknowledge, or not the MM delivery. In case of success an
acknowledgement is sent to the VAS originator, in case of failure, a notification failure is sent to the VAS
originator.

7 Operator Services

7.1 Billing and CDR

Alcatel MMS Proxy Relay generates CDRs that can be processed by a billing system, in order to handle post-
paid billing.
The CDR are conform to 3GPP 32 235 5.0.0.

Please refer to 3GPP 32.235, for the list of fields available in CDR.

CDR are gathered in CDR files which can be collected with a FTP connection (login / password required).
These files are syslog files and thus are located in a dedicated directory, have a configurable maximum size,
and are periodically (period is configurable) removed to prevent from disk saturation.

The CDR generation is activated on the configurable trigger points as shown below.
Two cases are considered:
- Either when the originator and recipient proxy relay are same, i.e., no MM4 routing is required
- Or the originator and recipient proxy relay are different, i.e., MM4 routing is required

In addition, offered in conjunction with A5326 Nextenso Charging Proxy, Alcatel MMS Proxy Relay offers:
> Prepaid billing with any Prepaid system.
> Content-based billing: this allows having different billing policies depending on the content/size/type/
of the MMS. Typically a MM containing only text will be billed in a different way than a MM with
multimedia content.
P
u
s
h

P
r
o
x
y
W
A
P

G
a
t
e
w
a
y
N
x

M
M
S

p
r
o
x
y

R
e
l
a
y
E
-
m
a
i
l

S
e
r
v
e
r

(
o
p
t
i
o
n
a
l
)
N
x

C
h
a
r
g
i
n
g

P
r
o
x
y

Figure 10: Nextenso MMS Proxy Relay and Nextenso Charging Proxy

For more details about the prepaid billing capacities, refer to A5326 Nextenso Charging Proxy Product
Description.

7.2 Statistics

Statistical information are provided through SNMP.

Statistic informations concern :
> For MM1 interface :
> Number of MM received from mobiles
> Number of MM retrieved by mobiles
> Number of Delivery Reports
> Number of delivery acknowledgement
> Number of submission requests failed (for MM1 and MM7)
> Number of retrieval request failed (for MM1 and MM7)
> For notifications
> Number of PAP notifications sent to the Push Proxy Gateway
> Number of PAP requests failed
> Number of SMS notifications sent
> Number of SMS notifications failed
> Number of notification response received
> For MM3
> Number of MM sent to MM3 (SMTP out)
> Number of MM received (SMTP in)
> For MM4
> Number of MM routed to MM4 interface (SMTP out)
> Number of MM4 messages received (SMTP in)
> For MM6
> Number of MM6 lookups requests to the user database
> Number of MM6 lookups failed
> For MM7
> Number of submission requests received on the MM7 inetrface
> Number of cancel requests received on the MM7 inetrface
> Number of replace requests received on the MM7 inetrface
> Number of MM routed to a VAS
> System usage
> Number of MM write attemps to the Store & FW and number of failed
> Number of MM currently stored in Store & FW
> Number of messages expired
> Average size of MM crossing through the MMS Proxy Relay
> Occupancy rate of the Store & FW buffer
> Number of subscribers
> Number of content adapatation requests and failed

7.3 Operation and Maintenance

Operation and maintenance consist in :
- Platform and service monitoring
- Platform and service configuration

1.3.2 Monitoring

The monitoring consists in :
- Alarms
- Logs
- Statistics
- CDRs
- Data (backup and restore)
- Monitoring

1.3.3 MMS configuration parameters

The MMS Proxy Relay is built upon the Proxy Platform.
The following applications can be parametrized :
- Proxy
- Store & Forward
- Notification

7.3.1 Features inherited from Nextenso Proxy Platform
Alcatel MMS Proxy Relay embeds Nextenso Proxy Platform in order to perform its operations on the data
stream. It thus inherits from properties brought by Nextenso Proxy Platform.

7.3.1.1 Administration
Nextenso Proxy Platform provides a graphical Web interface that enables both system administration
(deployment, upgrades) and business administration (provisioning, configuration).
7.3.1.2 SNMP Agent
The SNMP Agent provided by Nextenso Proxy Platform allows alerts monitoring and system administration of
any proxy application.

8 Nextenso Proxy Platform

Based on the Nextenso Proxy Platform, the Alcatel MMS Proxy Relay benefits from the properties of the
Nextenso Proxy Platform.
8.1.1.1 Requests handling
> HTTP requests catching with source, destination, URL, header
> HTTP response catching with source, destination, header, body
8.1.1.2 Performance
For instance, on Intel servers with 1 CPU at 1 GHz, 512 MB memory, Nextenso Proxy Platform offers the
following performances:
> Stacks
?? WAP stack: 2500+ requests per second
?? HTTP stack: 3000-8000 requests per second
?? SMS stack: 500+ requests per second
> Agents (running no proxylets)
?? WAP Agent: 300-400 requests per second
?? HTTP Agent: 300-500 requests per second
?? SMS Agent: 250+ requests per second
NB: The performances of an agent depend on the number and the nature of the proxylets that run in this
agent.

8.1.1.3 Security
Nextenso Proxy Platform supports many encryption mechanisms such as WTLS and SSL.
In order to provide a very high security level, it is possible to deploy the software components in several distinct
security zones.
8.1.1.4 Multi-protocols
> WAP 1.1 stack
> WAP 1.2.1 stack
> WAP 2.0 stack
> WAP Push OTA
> HTTP 1.1 stack
> SMS-C interface (SMPP, CIMD2)
> Radius
8.1.1.5 Scalability and high availability
Nextenso Proxy Platform allows deploying multi-servers platform with load-balancing and fail-over
mechanisms in order to reach carrier grade availability rates.

9 IOT
So far Nextenso MMS Proxy Relay has been tested with the following MMS enabled devices, and ensures
interoperability between them:
- Nokia 7650
- Siemens S55
- Mitsubishi M330
- Sony Ericsson T68
- MyX5 Sagem
- Microsoft SPV
- Panasonic GD 87
- Alcatel One Touch 535

Alcatel MMS Proxy Relay architecture being flexible, it makes it easy to support new terminals, by adding the
required functionalities, if need be, thus ensuring the IOT.

10 Performances

One server based on a mono-processor configuration with a 1Ghz CPU, 1Go of memory and 20Gb of hard
disk space has the capacity to handle 20 MMS/second.

2 Operating system and minimal hardware requirements
The minimal hardware requirement for a mono-machine configuration of Nextenso Proxy Platform is:
> Intel server with Intel Pentium III at 1 GHz
> 512 Mbytes memory
> 10 Gbytes hard disk
> Linux Redhat 7.2
> J DK 1.3.


11 Annex A: Scope Of Compliance
The scope of this document is to provide the Alcatel MMS Solution road map, and its compliance to standards.
Alcatel MMS Solution complies with:
> 3GPP specifications:
?? TS23.140 V540
?? TS22.140 V530
> WAP forum specifications:
?? WAP 205 April 2001 (20010425-a)
?? WAP 206 J anuary 2002 (20020115-a)
?? WAP 209 J anuary 2002 (20020105-a)
> IETF:
?? RFC 2821: "Simple Mail Transfer Protocol"
?? RFC 2822: "Internet Message Format"
?? RFC 2045: "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message
Bodies"
?? RFC 2046: "Multipurpose Internet Mail extension (MIME) Part Two: Media Types"
?? RFC 2047: "Multipurpose Internet Mail Extensions (MIME) Part Three: Message Header Extensions
for N on-ASCI I -Text"
?? RFC 2048: "Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures"
?? RFC 2049: "Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and
Examples"
?? RFC 1939: "Post Off ice Protocol - Version 3"
?? RFC 2060: "IMAP4, Internet Message Access Protocol - Version 4 Rev1
?? RFC 2076: "Common Internet Message Headers"
?? RFC 2421 (Sept. 1998): "Voice Profile for Internet Mail - release 2, VPIM"
?? RFC 2616: "Hypertext Transfer Protocol, HTTP/1.1"
The feature list refers to functionality defined by the 3GPP. Additional features of the Alcatel solution are also
proposed.
Features are gathered in domains:
> MM submission and retrieval
> Addressing and routing
> Storage
> Interfaces
> Format and conversions
> Operations and Maintenance
The level of Support is stated accordingly the TS23.140 V5.2.0 3GPP specification:
> O for Optional;
> R for Recommended;
> M for Mandatory.
The column Reference makes the explicit reference to the relevant chapter in TS23.140 V5.2.0 3GPP
specification.
Optional means that the feature is delivered as an option inside the MMS Solution.
CDE stands for Customized Development Engineering, and means that the feature requires special analysis
and eventually customized developments in regard to the network or service interoperability context.

Note : features available in 1.0 and 1.1 are of course available in 2.0.

11.1 MM Submission And Retrieval
MM SUBMISSION AND
RETRIEVAL
Features

MMS
Relay/Server
Comments
Functionality
Support Ref.
MMS
Solution
Release
Component

Indicate Recipients Address(es) in MM

M (7.1.1) 1.0 MMS PR

Indicate Originators Address in MM

M (7.1.1) 1.0 MMS PR

Message Time Stamp M
(7.1.1)
(7.1.3)
1.0 MMS PR
Message Delivery Time (earliest desired
time of delivery)
O (7.1.1) 2.0 MMS PR

Message Expiry Time M
(7.1.1)
(7.1.2)
1.1 MMS PR

Indication of MIME content type of the
message
M (7.1.3) 1.0 MMS PR
Further MM Qualifications (e.g. priority,
message class, subject)
O
(7.1.1)
(7.1.3)
2.0 MMS PR Priority, message class, subject
MM submission M (7.1.1) 1.0 MMS PR
MM Notification M
(5.2)
(7.1.2)
(71.2.1)
1.0 MMS PR
WAP Push based.
A WAP Push Proxy Gateway is
required in the operators
environment.
MM Rejection M (7.1.2.1) 1.1 MMS PR
MM Retrieval M
(5.2)
(7.1.2.1)
(7.1.2)
1.0 MMS PR
MM Retrieval via WEB interface
Not
specified
1.0 MMS PR Optional Feature
MM Forwarding without Retrieval O
(5.2)
(7.1.4)
2.x MMS PR
According to WAP forum
specification availability
MM Forwarding to MMBox O (7.1.1) 2.0 MMS PR Automatic copy in the CMS
MM Forwarding to external mail server O (7.1.12) 2.0 MMS PR
Automatic copy in the external
email server
Submit MM to external MMSE O (7.2) 1.0 MMS PR MM4
Notify originator of external MMSE
delivery failure
O (7.1.11) 2.0 MMS PR MM4

MMS
Relay/Server
MMS
Solution
Release
Component Comments
Functionality
Support Ref.
Forwarding Count M (7.1.4) 2.x MMS PR
Only applicable if forwarding w/o
retrieval supported
List of Forwarding Addresses R
(7.1.3)
(7.1.4)
2.x MMS PR
Only applicable if forwarding w/o
retrieval supported
Delivery Report M
(7.1.1)
(7.1.3)
(7.1.5)
2.0 MMS PR
Read Reply Report M
(7.1.1)
(7.1.3)
(7.1.6)
2.0 MMS PR
Streaming O 7.1.7) 2.x MMBox Audio & Video
Prepaid Service O (7.1.8) 2.0

charging proxy
Standard feature for Alcatel
Prepaid.
On CDE for interoperability with
other Prepaid systems (INAP,
XML, )
Reply Charging O
(5.2)
(7.1.10)
2.x charging proxy
According to 3GPP and WAP
forum specifications
Assign Message ID M (7.1.1) 1.0 MMS PR
11.2 Addressing And Routing
MMS
Relay/Server
MMS
Solution
Release
Component Comment
Functionality
Support Ref.
Single & multiple recipient M (7.2.2) 2.0 MMS PR
Addressing type M (7.2.1) 1.0 MMS PR
Support FRC822 address
Support PLMN address
Address parsing M (7.2) 2.x MMS PR
Address format error notification O (7.2) 2.0 MMS PR
Address resolution M
(7.1.1)
(7.2)
1.0 MMS PR
Identify if receiver(s) is/are a
recipient in the same PLMN, in a
different PLMN, a VAS.
Supported address types: PLMN
and RFC822
Support a request in
an MM that the MM
originators address
be hidden from the
recipient MMS UA.
O
(5.2)
(7.1.1)
(6.1.9)
1.1 MMS PR
Address Hiding
Ensuring that
senders address is
not shown to the
recipient MMS User
Agent.
M
(4.3) (5.2)
(7.1.1)
(7.1.2.1)
(7.1.3)
(7.1.9)
1.1 MMS PR
Only applicable if the MM
originator has requested her
address to be hidden from the
recipient MMS User Agent
Address translation (MSISDN to IP-
routable)

M
(4.3) (5.2)
(7.2)
(7.2.2)
1.1
static
2.0
ENUM
MMS PR
1.1 Internal static table method
2.0 Based on ENUM on project
basis
Number portability O (7.2.2) 2.0 MMS PR
Based on MAP on project basis
2.x ENUM implementation
11.3 Storage
MMS
Relay/Server
MMS
Solution
Release
Component Comment
Functionality
Support Ref.
Temporary message store for delivery M
(5.2)
(7.1.1)
(7.1.2)
(7.1.3)
1.0 MMS PR
The MMS Proxy Relay stores
messages until they are
delivered. This is a temporary
storage
Persistent network message store
(Alcatel storage)
O
(5.2)
(7.1.12)

1.1
Unlimited
2.0
Unlimited
MMBox

1.1 2.0 Unlimited with
Centralized Message Store
(CMS)
Feature of this message store :
Standard feature of an email
server :
?? inbox
?? compose
?? FW (to email, to MM)
?? Sent box
?? Address book
?? Notification
Persistent network message store
(external storage)
O
(5.2)
(7.1.12)
1.1 MMS PR
The MMS Proxy Relay forwards
the MM to an external email
server
11.4 Interfaces
MMS
Relay/Server
MMS
Solution
Release
Component
Comment
Functionality
Support Ref.

MM1: User Agent interfaces M
(6.3)
(7.2.1)
(8.1)
1.0 MMS PR
WAP1.2 for sending and
receiving
WAP Push for notification (SMS
bearer)
SMS notification for legacy
support
MM3: inter working with external server O (6.5) (8.3) 1.0
MM4: Inter working with other MMS
systems
M
(6.6)
(7.2.2)
1.1 MMS PR SMTP interface
MM5: HLR O
(6.7)
(8.5)
2.0 MMS PR
Optional Feature
Implementation on project basis
based on MAP. Requires SS7
stack on MMS PR.
MM6: MMS User Databases O
(6.8)
(8.6)
1.0
internal
1.1
external
MMS PR LDAP based
MM7: MMS VAS Applications O
(6.9)
(7.2.3)
(8.7)
1.0
SMTP

2.0
3GPP
MMS PR
1.0 Not specified in 3GPP R4,
SMTP available
2.0 Compliant with 3GPP R5
specifications (SOAP)

MM8: interface between MMS Relay
server and billing system
O (8.8) 2.0
Charging
Proxy
Through Charging Proxy
11.5 Formats And Conversions
MMS
Relay/Server
MMS
Solution
Release
Component
Comments
Functionality
Support Ref.

Formats conversions

Image M
(5.1)
(7.1.3.1)
2.0 MMS PR
Transcoding: J PEG, GIF, GIF89a,
WBMP, PNG, TIFF, PBM
Other conversions: size, color
scheme, rotation, frame
Speech M
(5.1)
(71.3.1)
2.0 MMS PR
Transcoding : AMR, MP3, PCM
WAV, G711, MIDI
Video M (5.1) 2.x MMS PR H263, MPEG4, AVI, H324
MM deletion based on
user profile or filtering
information
O (5.2)
1.1
System
2.0 User
MMS PR
1.1 System profile (storage
capacity)
1.2 User settable profile
(WEB/WAP)
Optional Feature
Data adaptation
based on user profile
and/or MMS User
Agent capabilities
O (6.1.2) 2.0 MMS PR Based on UAProf
Message
Management &
Data adaptation
Media type
conversion
O (5.1) 2.0 MMS PR
For legacy support :
- SMS notification with URL
(when UMC provided) or
text extracted
- Text extracted from MM
(when no UMC provided)
Negotiation of the capabilities of recipient
MMS User Agent
O (5.1) 2.0 MMS PR
Based on UAProf (initiated by
PP GW) and not static.
11.6 User Profile Management
MMS
Relay/Server
MMS
Solution
Release
Component Comment
Functionality
Support Ref.
End user Profile 1.1 MMS PR
Automatic copy + where
Email client interface
Voice Messaging bundle (case
of Alcatel Voice mail)
Profile for persistent storage 1.1 MMBox
Persistent storage + Web
Mailbox
LDAP repository 2.0 MMS PR
Block web domains O (5.4) 2.1 MMS PR
2.0: User settable profile
(WEB/WAP)
Block users
Not
specified
2.1 MMS PR
Not specified in 3GPP
On CDE for operator dependent
Solutions
Provide Web interface for end-user profile
management
2.0 MMS PR

11.7 OAM
MMS
Relay/Server
MMS
Solution
Release
Component
Comment
Functionality
Support Ref.
Enabling/disabling MMS function O (5.1) 1.1 MMS PR
Administrator feature: Frozing a
user account
User profile management O (5.4) 1.1 MMS PR 1.1: System predefined profiles
End-users provisioning
-Batch provisioning: export operator
database to Proxy Relay database +
synchro process for new users
-Self provisioning: end-user is provisioned
when sending first MMS

Not
specified
1.0 MMS PR
Activate end-users self-provisioning
Not
specified
2.0 MMS PR
End-user provisioning on first
sending of MMS
Lawful Interception
Not
specified
2.0 MMS PR
Not specified in 3GPP
On CDE for operator dependent
Solutions
Statistics
Not
specified
2.0 MMS PR
Provide traffic statistics on MMx
interfaces
Alarms monitoring
Not
specified
2.0 MMS PR
Provide alarm monitoring
interfaces on MM Relay/server
Log files
Not
specified
2.0 MMS PR
Provide log functionalities for
logging:
. System messages
. Alarms
. All MM processed by MMS
Relay/Server
Generating call data records (CDR) R (4.2) (5.2) 1.1
MMS PR

Binary encoded files.
Other formats and customization
on CDE

1.1. VAS Support

MMS
Relay/Server
MMS
Solution
Release
Component
Comment
Functionality
Support Ref.
Authentication O (7.1.13)
2.0
MMS PR
Authenticate vAS prior to MM
delivery
Authorization O (7.1.13)
2.0
MMS PR Authorize VAS to send MMs
Confidentiality O (7.1.13)
2.0
MMS PR Data encryption

1.2. IOTs
MMS
Relay/Server
MMS
Solution
Release
Component
Comment
Functionality
Support Ref.
MM1 WAP GW 2.0 MMS PR CDE if no bundle WAP GW
MM1 handsets 2.0 MMS PR
Support of Nokia 7650, T68i,
Sony Ericsson, Panasonic G87
and Microsoft SPV
MM4 2.0 MMS PR
Compliance towards
conformance document
MM7 2.x MMS PR
2.0 relies on SOAP interface.
2.x wide interoperability tested

1.3. Miscellaneous
MMS
Relay/Server
MMS
Solution
Release
Component
Comment
Functionality
Support Ref.
Scalability
Not
Specified

2.0 MMS PR
MMBox

High availability
Not
Specified

2.0
MMS PR
MMBox
Process duplication, watch
dog, message bus inter
process
Anti-spam filter
Not
Specified

2.x
MMS PR Access control
Digital right management
Not
Specified

2.x
MMS PR
Virus checking
Not
Specified

2.x
MMS PR

12 Annex B: Environmental compliance
12.1 Environment Characteristics
The Alcatel MMS Solution complies with the following operating environment specifications:
Environment Characteristic Document
Climatic environment CSEI 11.10
Electromagnetic environment CSEI 12.10
Electromagnetic compatibility NF C98 020
Electrostatic environment CSEI 31-21
Electrical overload tests CESI 31-21
Electrical safety ENGO-950
Personal safety NF C98-010
12.2 Environmental Requirements
The Alcatel MMS Solution environmental requirements are as follows:
Characteristic Tolerances
Ambient temperature Must be between 10 and 27C
Temperature variation Must not vary by more than 5 per hour.
(Average computed over a 5-minute period).
Hygrometry Between 5 and 85 %.
Rate of hygrometry Must not vary by more than 10% per hour.
Humidity Between 1 and 25 g/m
3

www.alcatel.com
Alcatel and Alcatel logo are registered trademarks of Alcatel. All other trademarks are the property of their respective
owners. Alcatel assumes no responsibility for the accuracy of the information presented, which is subject to change without
notice. 2002, Alcatel, Paris. All right reserved.

Mms

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Mms

Uploaded by

Copyright:

Available Formats

Table of Contents

PRODUCT DESCRIPTION ALCATEL 1 >

You might also like