1 / 18

ENUM for MMS Routing over MM4 I/F

ENUM for MMS Routing over MM4 I/F. James Yu NeuStar, Inc. 3GPP2 TSG-N WG2 December 9 to December 13, 2002. B’s MMSC. A’s MMSC. Message Delivery without MNP. 2. 3. 1. A. B. 1. A sends a message to B and the message is sent to A’s MMSC.

dutch
Download Presentation

ENUM for MMS Routing over MM4 I/F

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. ENUM for MMS Routing over MM4 I/F James YuNeuStar, Inc.3GPP2 TSG-N WG2December 9 to December 13, 2002

  2. B’s MMSC A’s MMSC Message Delivery without MNP 2 3 1 A B 1. A sends a message to B and the message is sent to A’s MMSC. 2. A’s MMSC examines the first N digits (e.g.., 1+NPA+NXX) of B to determines the address of B”s MMSC by a local table lookup and sends the message to B’s MMSC. 3. B’s MMSC delivers the message to B or sends a notification to B.

  3. B’s MMSC A’s MMSC Message Delivery with MNP Using ENUM ENUM 2 3 4 5 1 A B 1. A sends a message to B and the message is sent to A’s MMSC. 2. A’s MMSC sends B’s telephone number (TN) in the ENUM query. 3. The ENUM process returns the NAPTR RRs. 4. A’s MMSC retrieves the NPATR RR associated with the “mms” that contains the domain name about B’s MMSC, obtains the IP address of the domain name and sends the message to B’s MMSC. 5. B’s MMSC delivers the message to B or sends a notification to B.

  4. MNP Implementations • Three categories at country code (CC) level - All NP info. available (e.g., centralized NPAC) to the Tier 1 Registry - NP info. known to the code range holder (CRH) - No MNP

  5. ENUM Scheme • “Private ENUM ” instead of “end user ENUM” (e.g., do not use e164.arpa) • Combine WNP with ENUM at Tier 1 Registry • Two solutions, need to determine which one to use 1. NAPTR RRs at the MDN level 2. NAPTR RRs at the code range/RP level

  6. Logical ENUM Hierarchy - Tier 1 Has All MNP Info.NAPTR RRs at the MDN Level Root . NS RR Tier 0 Registry foo.foo NS RR NS RR NS RR Tier 1 Registry … … x.x.foo.foo 1.foo.foo x.x.x.foo.foo NS RR/MNP NS RR/MNP Tier 2 Registry [Carrier] … 4.3.2.1.3.3.5.2.0.2.1.foo.foo 5.4.3.2.3.3.5.2.0.2.1.foo.foo

  7. DNS-ENUM Query - Tier 1 Has All MNP Info.NAPTR RRs at the MDN Level Root Tier 0 Registry 4.3.2.1.3.3.5.2.0.2.1.foo.foo Orig. MMSC Tier 1 Registry NS RRs 4.3.2.1.3.3.5.2.0.2.1.foo.foo NAPTR RRs Tier 2 Registry (Carrier) Note: The DNS-ENUM process is the same when the country does not support MNP.

  8. Logical ENUM Hierarchy - Tier 1 Has No MNP Info.NAPTR RRs at the MDN Level Root . NS RR Tier 0 Registry foo.foo NS RR NS RR NS RR Tier 1 Registry … … x.foo.foo x.x.foo.foo x.x.x.foo.foo NS RR NS RR Tier 2 Registry [CRH] … z.z.z.z.x.x.foo.foo y.y.y.y.x.x.foo.foo NS RR/MNP Tier 2 Registry [Carrier] x.x.x.x.x.y.y.y.y.x.x.foo.foo

  9. DNS-ENUM Query - Tier 1 Has No MNP Info.NAPTR RRs at the MDN Level Root Tier 0 Registry 9.8.7.3.3.3.1.1.1.c.c.foo.foo Tier 1 Registry Orig. MMSC NS RRs 9.8.7.3.3.3.1.1.1.c.c.foo.foo NS RRs Tier 2 Registry (CRH) 9.8.7.3.3.3.1.1.1.c.c.foo.foo NAPTR RRs Tier 2 Registry (Carrier)

  10. Logical ENUM Hierarchy - Tier 1 Has All MNP InfoNAPTR RRs at the Code Range/RP Level Root . NS RR Tier 0 Registry foo1.foo foo2.foo NS RR NS RR Tier 1 Registry … … x.x.foo1.foo x.x.foo2.foo 1.foo1.foo 1.foo2.foo x.x.x.foo1.foo x.x.x.foo2.foo CNAME RR/MNP CNAME RR/MNP Tier 2 Registry [Carrier] … 4.4.5.2.0.2.1.foo2.foo 3.3.5.2.0.2.1.foo2.foo

  11. DNS-ENUM Query - Tier 1 Has All MNP Info.NAPTR RRs at the Code Range/RP Level Root Tier 0 Registry 4.3.2.1.3.3.5.2.0.2.1.foo1.foo Orig. MMSC Tier 1 Registry CNAME RR & NS RRs 4.4.5.2.0.2.1.foo2.foo NAPTR RRs Tier 2 Registry (Carrier) Note: The DNS-ENUM process is the same when the country does not support MNP.

  12. Logical ENUM Hierarchy - Tier 1 Has No MNP Info.NAPTR RRs at the Code Range/RP Level Root . NS RR Tier 0 Registry foo1.foo foo2.foo NS RR NS RR NS RR … … Tier 1 Registry c.c.foo1.foo c.c.foo2.foo x.foo1.foo x.foo2.foo x.x.x.foo1.foo x.x.x.foo2.foo NS RR NS RR … Tier 2 Registry [CRH] z.z.z.x.x.x.c.c.foo1.foo y.y.y.x.x.x.c.c.foo1.foo NS RR (foo2.foo) CNAME RR/MNP Tier 2 Registry [Carrier] v.v.v.x.x.x.c.c.foo2.foo

  13. DNS-ENUM Query - Tier 1 Has No MNP Info. NAPTR RRs at the Code Range/RP Level Root Tier 0 Registry 2. 9.8.7.3.3.3.1.1.1.c.c.foo1.foo 3. NS RRs Orig. MMSC Tier 1 Registry 6. 4.4.4.2.2.2.c.c.foo2.foo 7. NS RRs 4. 9.8.7.3.3.3.1.1.1.c.c.foo1.foo 5. CNAME RR Tier 2 Registry (CRH) 8. 4.4.4.2.2.2.c.c.foo2.foo 9. NAPTR RRs Tier 2 Registry (Carrier)

  14. NAPTR RRs at MDN Level vs. at Code Range/RP Level

  15. Discussion • NAPTR RRs at the MDN level • Carrier can assign resources on a per MDN basis • “Not found” for unassigned MDN • Zone file administration effort is significant (e.g., for ported-in MDN) • NAPTR RRs at the code range/RP level • Carrier can only assign resources on a per code range/RP basis • Zone file administration is very simple • MDN information can be conveyed in application layer message or in the URL when the host names of the servers are found

  16. Discussion (Cont’d) • Querying the called party’s HLR for IMSI/MIN information over SS7 network will not work for N.A. because NP database in the N.A. does not have the point code/subsystem number information • It is not just between two 3GPP systems where querying the HLR for IMSI over SS7 will work. It can be from 3GPP MMSC to 3GPP2 MMSC!

  17. URL Examples - Code Range Level • sip server (e.g., sip.neustar.biz) found via DNS-ENUM sip:+1-202-533-1234@sip.neustar.biz • mail server (e.g., mail.xyz.biz) found via DNS-ENUM mailto:12025331234@mail.xyz.biz May be no need to have the NAPTR RRs at the MDN level?

  18. Next Steps • Decide which one, at MDN level or at code range/RP level, is to be adopted for DNS-ENUM scheme • Revise Annex G of N.P0042/PN-xxxx v0.07 • Define NAPTR RRs for MMS and other applications (e.g., SMS) • Determine whether, how and when to implement the scheme

More Related