1 / 9

+code Dialing Implementation Considerations

+code Dialing Implementation Considerations. Alain Bouvier alain.bouvier@ericsson.com CDG International Roaming Team Meeting Kauai, December 13-14, 2004. +code Dialing – General Considerations. For the +code dialing feature to be used, it must be supported by the Mobile Station;

hasad
Télécharger la présentation

+code Dialing Implementation Considerations

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. +code DialingImplementation Considerations Alain Bouvier alain.bouvier@ericsson.com CDG International Roaming Team Meeting Kauai, December 13-14, 2004

  2. +code Dialing – General Considerations • For the +code dialing feature to be used, it must be supported by the Mobile Station; • The international dialing enhancements specified in TIA/EIA/IS-875 required for +code dialing have impacts on the MSC for Call Origination and on the HLR for Calling Number Identification (CNI) & Callback; • The +code dialing “Call Origination” and “CNI & Callback” functions are independent: • For +code dialing “Call Origination” to be supported, the O-MSC must comply with TIA/EIA/IS-875 and the O-MS must support +code dialing; • For “CNI & Callback” complete support, the T-MS must support +code dialing and his home HLR must comply with TIA/EIA/IS-875; • It is strongly recommended to provisioned the MDN in the international format as per E.164.

  3. O-MS: Originating Mobile Station IAC: International Access Code : +code supported : +code not supported : IS-875 compliant : IS-875 non compliant + + + + IS-875 IS-875 IS-875 IS-875 A) MSC The MSC processes the general nature of the call. IAC required for international calls. B) MSC The MSC processes the general nature of the call. IAC required for international calls. IS-875 C) MSC +code not used: the MSC processes the general nature of the call. IAC required for intl calls. +code used: call can not be completed as dialed. + D) MSC +code not used: the MSC processes the national nature of the call. IAC required for intl calls. +code used: the MSC processes the intl nature of the call. IS-875 + +code Dialing – Call Origination Behavior Under Partial Network Support Behavior when some network elements support the +code dialing feature while others don’t. O-MS O-MSC

  4. T-MS: Terminating Mobile Station NSN: National Significant Number CC: Country Code : +code supported : +code not supported : IS-875 supported : IS-875 not supported + + + + IS-875 IS-875 IS-875 IS-875 A) HLR The MS displays NSN or CC NSN. In both cases, automatic callback does not work (editing required). B) HLR The MS displays CC NSN. Automatic callback does not work (editing required). IS-875 C) HLR The MS displays either NSN in which case automatic callback does not work (editing required) or +CC NSN in which case automatic callback does work. + D) HLR The MS displays +CC NSN. Automatic callback does work. IS-875 + +code Dialing – CNI & Callback Behavior Under Partial Network Support Behavior when some network elements support the +code dialing feature while others don’t. Intl Roaming Subscriber HLR T-MS

  5. +code Dialing – IS-2000 Rev A Compliant MS • For International calls, the MS must set the dialed MDN NUMBER_TYPE=001, however, as per IS-2000 Rev A, the NUMBER_TYPE parameter is only defined/used if DIGIT_MODE=1 (ASCII codes). • Consequently, the MS must set DIGIT_MODE = 1 (ASCII codes) for voice calls*. * Most MS currently set DIGIT_MODE=0 (4-bit DTMF codes) for voice calls and DIGIT_MODE=1 (8-bit ASCII codes) for circuit switch data calls.

  6. +code Dialing – IS-2000 Rev C Compliant MS • It is planned to support the NUMBER_TYPE parameter for DIGIT_MODE=0 (BCD codes);

  7. 2 Roaming Country 1 3 Other Country 4 1 MS Orig. Home Country – MS Term. Home Country 2 MS Orig. Home Country – MS Term. Intl Roaming 3 MS Orig. Other Country – MS Term. Home Country 4 MS Orig. Other Country – MS Term. Intl Roaming +code Dialing – Call Flows HLR Home Country

  8. MDN_A=86 137 48503251 MDN_B=81 9027826543 4 Serving Network – Intl Roaming Orig. Network – Other Country MSID_B=441 23 1234567890 MSID_A=460 27 1234567890 + + A B BS O-MSC HLR S-MSC BS DIAL +IN=+81 9027826543 SEND 1 Origination(DM=BCD, MSID_A, [CdPN=IN, NT=INTL]) 2 CM ServReq(MSID_A, [CdPN=IN, TON=INTL]) 3 NoAI determination LOQREQ(CgPNString1[MDN_A], DGTSDIAL=IN) 3.1 4 CNI Editing ROUTREQ(CgPNString1[MDN_A], MSID_B) 4.1 5 routreq(TLDN) 6 locreq(CgPNString1[MDN_A], TERMLIST, REDIND) 7 IAM(CgPNString1[MDN_A]) 8 AssignReq(MSinfo) 9 Alert([CgPN=MDN_A, NT=INTL], PI) 10 +86 13748503251 CNI Display 10.1 11 Origination([CdPN=86 13748503251, NT=INTL]) 12 13 14 MS Orig. Other Country – MS Term. Roaming Country IN: International Number (E.164) DM: DIGIT_MODE MSID: MS Identity MDN: Mobile Directory Number NT: NUMBER_TYPE TON: Type Of Number NoAI: Nature of Address Indicator CdPN: Called Party Number CgPN: Calling Party Number PI: Presentation Information CNI: Calling Number Identification

  9. ? TAKING YOU FORWARD ? QUESTIONS ?

More Related