Thread: [In development] Brainstorm: MMS Support
View Single Post
Performer is offline Performer
2009-10-19 , 15:09
Posts: 18 | Thanked: 18 times | Joined on Oct 2009 @ Russia
#61
Originally Posted by Framstag View Post
It's about 1 1/2 ago I looked at MMS/IMS integration. But I'm sure that the provider will want all the old devices out their to still work - and their definitely do not SIP. So if we assume that legacy device support will continue for 5-10 years we should not care about SIP now.
It we talking about feature development of the platform we should bear in mind. See requirements of 3GPPr6.
Originally Posted by Framstag View Post
MMS for the device is TCP/IP for retrieval and PUSH (IP, SMS but possibly also SIP in future) for sending.
Just the opposite: SMS and HTTP for the reception, HTTP for the transfer. For IMS-solutions - SIP in both cases.
Originally Posted by Framstag View Post
GRX is something that is not relevant for the device. GRX is used (as above mentioned) for inter-operator communication between providers, in the MMSC case communication between MMSC.
Course GRX and the device does not interact directly. Subject GRX mentioned in the explanation of the need to use private IP-based networks. Please read carefully.
Originally Posted by Framstag View Post
From the view of the device it does use SMS and IP roaming.

AFAIK there is no device lock-out. Every device that can handle the procotol should be able to do MMS.
Realy? But what you will say about MMS notification by WAP-Push indicators and MMS transmission in roaming?

For example the typical high-level use-case of MMS delivery in roaming:
1. MMSC has MMS for subscrier B. MMSC sends WAP-Push indicator by SMS to UA.
2. UA receives WAP-Push and asks subscriber to retreive MMS.
3. Subscriber accepts UA-request.
4. UA initiates PDP-context to MMS APN.
5. SGSN of guest network opens Gn tunnel thru GRX to GGSN of home network responsible for MMS APN
Now UA has IP from IP-space of home MMS pool.
6. GGSN sends the pair of MSISDN and IP to WAPGW by RADIUS Accounting-Start message.
7. UA sends HTTP-request for MMSC using message URL from WAP-Push indicator. UA uses WAPGW as proxy and open PDP-context as interface.
8. WAPGW transmits request to MMSC. WAPGW puts additional HTTP-header with MSISDN to request.
9. MMSC receives request and sends message content as response. If MMSC has content adaptation feature MMSC adapts content of the message to UA capable format using HTTP-header User-Agent form HTTP-request to determinate parameters of adaptation/transcoding.
Last edited by Performer; 2009-10-19 at 15:12.
 

The Following User Says Thank You to Performer For This Useful Post: