1 / 16

MMS Update CDG IRT – Las Vegas

MMS Update CDG IRT – Las Vegas. 12/01/2005 Bryan Gurganus bryang@qualcomm.com. Agenda. MMS CRX and Addressing Taskforce (MMS CAT) MMS Inter-carrier using MMS Hub Provider – Today’s Solution MMS Inter-carrier using CRX (Focus of MMS CAT) ENUM/DNS using common GSM/CDMA structure

zora
Télécharger la présentation

MMS Update CDG IRT – Las Vegas

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. MMS UpdateCDG IRT – Las Vegas 12/01/2005 Bryan Gurganus bryang@qualcomm.com

  2. MMS Update December 01, 2005 Agenda • MMS CRX and Addressing Taskforce (MMS CAT) • MMS Inter-carrier using MMS Hub Provider – Today’s Solution • MMS Inter-carrier using CRX (Focus of MMS CAT) • ENUM/DNS using common GSM/CDMA structure • Other issues • Preliminary look at MMS Roaming

  3. MMS Update December 01, 2005 MMS CRX and Addressing Taskforce (MMS CAT) • Cooperative effort between CDG MMS Team and IRT to identify and document CRX and address resolution requirements for supporting inter-carrier MMS (CDMACDMA and CDMAGSM) • Status: • 11/16 – Taskforce announcement and call for participation • 11/22 – First conference call to identify various issues • 01/04 – Next conference call scheduled for 1:00pm (PST) • Participants:  Aicent  Alltel  Bell Mobility  Comverse  Neustar  Pelephone  Qualcomm  Sprint-Nextel  Syniverse  Telus  TNZ  Verisign  Verizon • To participate or be added to the email list, please contact: bryang@qualcomm.com • MMS inter-carrier versus roaming…journal correction

  4. MMS Update December 01, 2005 CRX Network CRX Roaming Interconnect Network PDSN PDSN • CRX networks provide transport, billing, and AAA services to facilitate roaming between CDMA carriers • CRX network is a private, secure network inaccessible from the Internet • CRX-CRX peering has been addressed by CRX peering taskforce

  5. MMS HubProvider MMSC MMSC MMS Update December 01, 2005 Current Inter-carrier Solution: MMS Hub Provider MM4 MM4 CRX Roaming Interconnect Network MM1 MM1 PDSN PDSN • Providers such as LightSurf (acquired by Verisign) and Mobile 365 offer MM4 interconnect between both CDMA and GSM operators • This is the current solution being used by carriers such as Verizon, Sprint-Nextel, Telus, Bell Mobility, etc… • Transcoding and MM4 signaling conversion, if needed

  6. MMS HubProvider MMSC MMSC MMS Update December 01, 2005 Address Resolution: the problem MM4 MM4 CRX Roaming Interconnect Network MM1 MM1 PDSN PDSN • User dials recipient’s MDN but MM4 message requires • Mailbox address of recipient for SMTP RCPT TO • IP address of MM4 interface on recipient MMSC for Destination IP address

  7. MMS Update December 01, 2005 Address Resolution using MMS Hub Provider • Originating MMSC performs MNP query on the dialed number but offloads resolution of recipient mailbox and destination IP address to hub provider • Hub provider maintains private address resolution infrastructure • For example: • Originating MMSC sends MM4 message to the IP address of the MMS hub provider with a mailbox address that includes the recipient number and hub provider domain name • Hub provider extracts the recipient number and uses a private ENUM/DNS structure to determine mailbox address of recipient and IP address of MM4 interface on recipient MMSC • Since each MMS Hub provider uses private address resolution, each one must maintain databases/tables to support address resolution for all connecting carriers • What about future applications that require address resolution?

  8. MMS Update December 01, 2005 Inter-carrier MMS Solution using CRX MMSC MMSC MM4 MM4 CRX Network MM1 MM1 PDSN PDSN • Operator already has connectivity to CRX for roaming • Extend the use of CRX networks to support transport and address resolution for MMS and future applications such as PoC, IMS, etc… • Bill-and-keep billing (or lack thereof) between CDMA partners • Transcoding performed by recipient MMSC as needed

  9. MMS Update December 01, 2005 Inter-standard MMS using CRX CRX-GRX Peering GSM Network MMSC GRX Network MM4 GSM Network CRX Network MM1 CDMA Network PDSN CDMA Network • CRX-GRX peering required to support inter-standard MMS • 3GPP3GPP2 transcoding done by CRX (e.g. QCELPAMR) • Wholesale billing (not bill-and-keep in GSM since only originator pays) • ENUM/DNS address resolution across CDMA and GSM

  10. MMS Update December 01, 2005 ENUM/DNS Address Resolution • User dials recipient’s MDN but MM4 message requires • Mailbox address of recipient for SMTP RCPT TO • IP address of MM4 interface on recipient MMSC for Destination IP address • ENUM resolves dialed MDN (E.164 number) to recipient mailbox address: • Reformat for query: e.g. +1-868-651-1234 4.3.2.1.1.5.6.8.5.8.1.e164enum.net • Query ENUM server to find NAPTR resource record with “E2U+mms:mailto” service IDs or referral NS record to another name server • NAPTR record contains preferred list of URIs: e.g. mailto:+18586511234/TYPE=PLMN@mms.foo_telecom.net • URI includes domain name of recipient MMSC (e.g. mms.foo_telecom.net) • DNS to resolve domain name to IP address: • Query DNS server using domain name (e.g. mms.foo_telecom.net) to get IP address of the recipient MMSC MM4 interface: e.g. 192.20.40.10

  11. org net mccxxx 3gppnetwork GPRS mncxxx mncxxx.mccxxx.gprs. APN1 e164enum mms 4.4 (UK) 6.8 (CN) 1 (NANP) ENUM 6.2.9. 6.2.9.6.8.e164enum.net. 6.5.4.3.2.1 4.3.2.1.2.3.8.8.0.4 8.7.8.6.7.7 6.5.5.3.2.1 MMS Update December 01, 2005 GSM Structure • GSMA provides private DNS structure used by GSM carriers and GRXs • “3gppnetwork.org” is being added for use by future services(protects public root server from searching for unknown suffix) • “e164enum.net” is being added to support ENUM CRX/GRX Root DNS Root Note: diagram adapted from Private DSN presentation by James Yu and Richard Xu grx gprs Local DNS

  12. org mccxxx 3gppnetwork GPRS cdma mncxxx mncxxx.mccxxx.gprs. APN1 def mms CDMA abc.def.cdma.net. abc qrs xyz MMS Update December 01, 2005 CDG-GSMNA Joint MMS Team Proposed Solution • CDMA operators use the GSMA DNS/ENUM structure: • Would allow E.164 and DNS address resolution across CDMA and GSM • Common “e164enum.net” suffix for both CDMA and GSM ENUM • New suffix for CDMA DNS (“cdma.net” is shown as an example only) CRX/GRX Root DNS Root grx gprs net Local DNS e164enum 4.4 (UK) 6.8 (CN) 1 (NANP) ENUM 6.2.9. 6.2.9.6.8.e164enum.net. 6.5.4.3.2.1 4.3.2.1.2.3.8.8.0.4 8.7.8.6.7.7 6.5.5.3.2.1

  13. MMS Update December 01, 2005 CDG-GSMNA Joint MMS Team Proposed Solution • Scalable and manageable • Tier-2: local ENUM/DNS servers at each operator • Tier-1: slave root servers at each CRX/GRX • Tier-0: common master servers serving both CDMA and GSM • Extensible • same structure can be used with additional NAPTR record types to support features beyond MMS • Secure • Closed structure not accessible from the public Internet • Enables worldwide interoperability • No viable alternative has been identified

  14. MMS Update December 01, 2005 Other issues • Would CRX/GRX address structure and peering be accessible to current MMS interconnect providers like LightSurf and Mobile365? • Should taskforce address SLA terms (e.g. QoS) between carriers and CRXs? • Should taskforce address billing between carriers and CRXs?

  15. MMS Update December 01, 2005 Preliminary MMS Roaming Analysis • User agents always interact with their home network MMSC • For SIP architecture, home MMSC must be accessible to UA from visited network (i.e. public IP address and firewall configuration) • Notification of MMS message to roaming UA • WAP push mechanism with SMS notification sent by home PPG • SMS roaming is a prerequisite • MMS message retrieval by roaming UA • Data session between UA and their home MMSC to retrieve message • Packet data roaming is a prerequisite • Billing • Wholesale billing for data bandwidth used in visited network • Bill-and-keep for MMS message itself? What about inter-standard?

  16. Thank You bryang@qualcomm.com

More Related