Direct routing for roamer to roamer
This presentation is the property of its rightful owner.
Sponsored Links
1 / 32

Direct Routing for Roamer to Roamer PowerPoint PPT Presentation


  • 101 Views
  • Uploaded on
  • Presentation posted in: General

Direct Routing for Roamer to Roamer. CDG International Roaming Team. Contents. 1. Objective 2. Feature Description 3. Current Routing for Roamer to Roamer 4. Direct Routing for Roamer to Roamer 5. Numbering plan of DRRR 6. Interaction with other Features 7. Stage 2 Description

Download Presentation

Direct Routing for Roamer to Roamer

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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Direct routing for roamer to roamer

Direct Routingfor Roamer to Roamer

CDG International Roaming Team


Direct routing for roamer to roamer

Contents

1. Objective

2. Feature Description

3. Current Routing for Roamer to Roamer

4. Direct Routing for Roamer to Roamer

5. Numbering plan of DRRR

6. Interaction with other Features

7. Stage 2 Description

8. Requirements for DRRR

9. DRRR billing


Direct routing for roamer to roamer

1. Objective

  • Today, international charges both for caller and callee results in:

    • Roamers hesitate to call each other

    • Disadvantage against local rental mobile

  • Direct Routing will provide:

    • Lower charges to encourage roamers to call each other => Traffic Increase

    • Keep or Widen Home/Serve operator margin => Revenue Increase

    • Eliminate disadvantage against local rental mobile => Traffic/Revenue Increase


2 feature description

2. Feature Description

  • As for the present situation, in case of roamer(A) to roamer(B) calls, (A) has to make a international call to reach (B). ("trombone routing")

  • Direct Routing for Roamer to Roamer(DRRR) provides a direct routing from (A) to (B) instead of a trombone routing.

  • To provide this feature, (A) and (B) must be the same operator’s subscribers and they roam to the same country.

  • Roamer dials *77 + MDN to initiate DRRR.

  • Displayed number[*77-(CC)-MDN(A)] on the mobile (B) when the DRRR call is received (DRRR with CNIP)


3 current routing for roamer to roamer

O_MSC S_MSC STP Provider Gateway MSC HLR

call setup (IAC + CC+ MDN)

1 2 3 4 5 6 7 8

LOCREQ

ROUTREQ

ROUTREQ

routreq

routreq

locreq

call setup

3. Current Routing for Roamer to Roamer

O_MSC...MSC serving Originating roamer

S_MSC...MSC serving Terminating roamer


4 direct routing for roamer to roamer

O_MSC S_MSC STP Provider Gateway MSC HLR

REGNOT [MIN]

1 2 3 4 5 6 7 8 9

REGNOT [MIN]

regnot [profile(MDN)]

regnot [profile(MDN)]

Register MDN.

FEATREQ isn’t sent to HLR transparently at the case DGTSDIAL starts *77. And Direct Routing procedure shall be started.

FEATREQ[MIN, DGTSDIAL(*77+MDN)]

ROUTREQ [MIN, TERMTRIG]

routreq [TLDN]

ROUTREQ sends by the MIN that

was searched by MDN in DGTSDIAL.

featreq [FEATRESULT, TERMLIST]

call setup

O_MSC...MSC serving Originating roamer

S_MSC...MSC serving Terminating roamer

4. Direct Routing for Roamer to Roamer


Direct routing for roamer to roamer

Signaling Network

HLR

HLR

MSC/VLR

MSC/VLR

Serving Network

Home Network

Case 1

Roamer B

Roamer A

Network Boundary

MS

MS

5. Numbering plan of DRRR

  • Dialing for DRRR is [“*77”+(CC) +MDN]

  • Displayed number on the called party shall be able to call back directly to the calling party.(CNIP with DRRR)

Case 1

1)The Roamer A dials *77+(CC)+MDN B.

(e.g. *77-(81)-80-5066-9360)

2)The Roamer B displays *77+(CC)+MDN A

Notice) It depends on the Home Carrier’s decision whether CC is included or not.


Direct routing for roamer to roamer

6. Interaction with other Features

  • Call Delivery

    None identified

  • Call Forwarding - Busy (CFB)

    CFB shall not be invoked during DRRR. BT or Announcement.

  • Call Forwarding - No Answer (CFNA)

    CFNA shall not be invoked during DRRR. BT or Announcement.

  • Call Forwarding - Unconditional (CFU)

    CFU shall not be invoked during DRRR.

  • Call Forwarding to VMS

    Call Forwarding to VMS shall not be invoked during DRRR.


Direct routing for roamer to roamer

6. Interaction with other Features (continued)

  • VMS Retrieval

    None identified.

  • Short Messaging Service (SMS)

    None identified.

  • Call Waiting (CW)

    CW may be invoked after DRRR.

  • Cancel Call Waiting (CCW)

    None identified.

  • Three-way Calling (3WC)

    3WC may be invoked after DRRR.


Direct routing for roamer to roamer

O_MSC S_MSC STP Provider HLR

REGNOT [MIN_B]

1 2 3 4 5 6 7 8 9

mobile B

REGNOT [MIN_B]

regnot [profile(MDN_B, CFI)]

regnot [profile(MDN_B, CFI)]

FEATREQ [MIN_A, DGTSDIAL(*77-(CC)-MDN_B)]

mobile A

ROUTREQ [MIN_B, CPNSTRIG1_A]

routreq [TLDN]

featreq [FEATRESULT, TERMLIST]

call setup

mobile B

7. Stage 2 Description 1Successful DRRR Intersystem Termination

O_MSC...MSC serving Originating roamer

S_MSC...MSC serving Terminating roamer


Direct routing for roamer to roamer

7. Stage 2 Description 1 (continued)Successful DRRR Intersystem Termination

  • Serving MSC sends a REGNOT to STP Provider.

  • STP Provider forwards the REGNOT to HLR.

  • HLR sends a regnot with profile including MDN and CFI. When STP Provider receives the regnot, it registers the MDN_B and CFU-FA in CFI.

  • STP Provider forwards the regnot to Serving MSC.

  • The user dials *77-(CC)-MDN_B. Originating MSC sends a FEATREQ to STP Provider. STP Provider recognizes to initiate DRRR procedure because DGTSDIAL starts from *77. STP Provider searches the MDN_B value from GLR list and finds it. STP Provider confirms that CFU-FA is not “Authorized and activated”.

  • STP Provider sends a ROUTREQ with MIN_B that has been searched from GLR list and CPNSTRIG1_A that has been translated from MDN_A.

  • Serving MSC sends a routreq with TLDN.

  • STP Provider shall modify TLDN if needed. For example, Country Code shall be removed from “Destination Digits” and “Nature of Number” shall set to “National”. STP Provider sends a featreq with FEATRESULT that is successful and TERMLIST that is IntersystemTermination(TLDN).

  • Originating MSC sends IAM to Serving MSC. Mobile B displays *77-(CC)-MDN_A.


Direct routing for roamer to roamer

MSC STP Provider HLR

REGNOT [MIN_B]

1 2 3 4 5 6 7 8 9

mobile B

REGNOT [MIN_B]

regnot [profile(MDN_B, CFI)]

regnot [profile(MDN_B, CFI)]

FEATREQ [MIN_A, DGTSDIAL(*77-(CC)-MDN_B)]

mobile A

ROUTREQ [MIN_B, CPNSTRIG1_A]

routreq [TLDN]

featreq [FEATRESULT, TERMLIST]

call setup

mobile B

Stage 2 Description 2Successful DRRR Local Termination pattern 1


Direct routing for roamer to roamer

Stage 2 Description 2 (continued)Successful DRRR Local Termination pattern 1

  • 1-8. Same as the Stage 2 Description 1 step 1-8.

  • MSC setup a call. Mobile B displays *77-(CC)-MDN_A.


Direct routing for roamer to roamer

Stage 2 Description 3Successful DRRR Local Termination pattern 2

MSC STP Provider Gateway MSCHLR

REGNOT [MIN_B]

1 2 3 4 5 6 7

REGNOT [MIN_B]

regnot [profile(MDN_B, CFI)]

regnot [profile(MDN_B, CFI)]

FEATREQ[MIN_A, DGTSDIAL(*77-(CC)-MDN_B)]

featreq [FEATRESULT, TERMLIST(MIN_B, ESN_B), CPNSTRIG1_A]

call setup


Direct routing for roamer to roamer

Stage 2 Description 3 (continued)Successful DRRR Local Termination pattern 2

  • 1-5. Same as the Stage 2 Description 1 step 1-5.

  • STP Provider sends a featreq with FEATRESULT that is successful, TERMLIST that is LocalTermination including MIN_B and ESN_B and CPNSTRIG1_A that has been translated from MDN_A.

  • MSC setup a call. Mobile B displays *77-(CC)-MDN_A.


Direct routing for roamer to roamer

O_MSC S_MSC(old) STP Provider S_MSC(new) HLR

REGNOT [MIN_B]

1 2 3 4 5 6 7 8 9

mobile B

REGCANC [MIN_B]

REGCANC [MIN_B]

regcanc

regcanc

regnot

FEATREQ [MIN_A, DGTSDIAL(*77-(CC)-MDN_B)]

mobile A

featreq [FEATRESULT, ACCDEN(=No Page Response), ANNLIST]

call release

Stage 2 Description 4Unsuccessful DRRR with Call release

O_MSC...MSC serving Originating roamer

S_MSC...MSC serving Terminating roamer


Direct routing for roamer to roamer

Stage 2 Description 4 (continued)Unsuccessful DRRR with Call Release

  • A REGNOT is sent to HLR from new Serving MSC that is not in the same country as Originating MSC.

  • HLR sends a REGCANC to STP Provider.

  • STP Provider forwards the REGCANC to old Serving MSC.

  • Old Serving MSC sends a regcanc to STP Provider.

  • STP Provider forwards the regcanc to new Serving MSC.

  • HLR sends a regnot to Serving MSC.

  • The user dials *77-(CC)-MDN_B. Originating MSC sends a FEATREQ to STP Provider. STP Provider recognizes to initiate DRRR procedure because DGTSDIAL starts from *77. STP Provider searches the MDN_B value from GLR list and doesn’t find it.

  • STP Provider sends a featreq with FEATRESULT that is unsuccessful, ACCDEN that is 5 (No Page Response) and ANNLIST.

  • Originating MSC provides appropriate treatment based on ACCDEN and ANNLIST and releases a call.


Direct routing for roamer to roamer

O_MSC S_MSC STP Provider HLR

REGNOT [MIN_B]

1 2 3 4 5 6 7

mobile B

REGNOT [MIN_B]

regnot [profile(MDN_B, CFI)]

regnot [profile(MDN_B, CFI)]

FEATREQ [MIN_A, DGTSDIAL(*77-(CC)-MDN_B)]

mobile A

featreq [FEATRESULT, ACCDEN(=Termination Denied), ANNLIST]

call release

Stage 2 Description 5DRRR with CFU Activated

O_MSC...MSC serving Originating roamer

S_MSC...MSC serving Terminating roamer


Direct routing for roamer to roamer

Stage 2 Description 5 (continued)DRRR with CFU Activated

  • 1-4. Same as the Stage 2 Description 1 step 1-4.

  • The user dials *77-(CC)-MDN_B. Originating MSC sends a FEATREQ to STP Provider. STP Provider recognizes to initiate DRRR procedure because DGTSDIAL starts from *77. STP Provider searches the MDN value from GLR list and finds it. STP Provider confirms that CFU-FA is “Authorized and activated”.

  • STP Provider sends a featreq with FEATRESULT that is unsuccessful, ACCDEN that is 4 (Termination Denied) and ANNLIST.

  • Originating MSC provides appropriate treatment based on ACCDEN and ANNLIST and releases a call.


Direct routing for roamer to roamer

O_MSC S_MSC STP Provider Gateway MSC HLR

REGNOT [MIN_B]

12 34 5 6 7 8 9 10

mobile B

regnot [profile(MDN_B, CFI)]

FEATREQ[MIN_A, DGTSDIAL(*77-(CC)-MDN_B)]

mobile A

ROUTREQ [MIN_B]

busy

routreq [ACCDEN(=Busy)]

featreq [FEATRESULT, ACCDEN(=Busy), ANNLIST]

call release

Stage 2 Description 6DRRR with CFB Activated

O_MSC...MSC serving Originating roamer

S_MSC...MSC serving Terminating roamer


Direct routing for roamer to roamer

Stage 2 Description 6 (continued)DRRR with CFB Activated

  • 1-6. Same as the Stage 2 Description 1 step 1-6.

  • Serving MSC recognizes the terminating MS is Busy.

  • Serving MSC sends a routreq with ACCDEN that is 3 (Busy).

  • STP Provider sends a featreq with FEATRESULT that is unsuccessful, ACCDEN that is 3 (Busy) and ANNLIST.

  • Originating MSC provides appropriate treatment based on ACCDEN and ANNLIST and releases a call.


Direct routing for roamer to roamer

O_MSC S_MSC STP Provider Gateway MSC HLR

REGNOT [MIN_B]

1 2 3 4 5 6 7 8 9

mobile B

REGNOT [MIN_B]

regnot [profile(MDN_B, CFI)]

regnot [profile(MDN_B, CFI)]

FEATREQ[MIN_A, DGTSDIAL(*77-(CC)-MDN_B)]

mobile A

ROUTREQ [MIN_B, CPNSTRIG1_A]

routreq [TLDN]

featreq [FEATRESULT, TERMLIST]

call setup

Stage 2 Description 7DRRR with CFNA Activated

O_MSC...MSC serving Originating roamer

S_MSC...MSC serving Terminating roamer


Direct routing for roamer to roamer

O_MSC S_MSC STP Provider Gateway MSC HLR

No Answer

10 11 12 13 14 15 16

REDREQ [REDREASON(=No Answer)]

TRANUMREQ [REDREASON(=No Answer)]

tranumreq [ACCDEN(=Busy), ANNLIST]

redreq

call release

call release

Stage 2 Description 7 (continued)DRRR with CFNA Activated

O_MSC...MSC serving Originating roamer

S_MSC...MSC serving Terminating roamer


Direct routing for roamer to roamer

Stage 2 Description 7 (continued)DRRR with CFNA Activated

  • 1-9. Same as the Stage 2 Description 1 step 1-9.

  • The MS does not answer after alerting.

  • Serving MSC sends a REDREQ with REDREASON that is 2 (No Answer) to Originating MSC.

  • Originating MSC sends a TRANUMREQ with REDREASON that is 2 (NoAnswer) to STP Provider.

  • STP Provider sends a tranumreq with ACCDEN that is 3 (Busy) and ANNLIST.

  • Originating MSC sends a redreq to Serving MSC.

  • Originating MSC releases the inter-MSC call.

  • Originating MSC provides appropriate treatment based on ACCDEN and ANNLIST and releases a call.


Direct routing for roamer to roamer

ANSI-41-D Description of Serving MSC

4.14.1MSC Detecting Feature Request

12Send a FeatureRequest INVOKE to the HLR associated with the MS.

13Start the Feature Request Response Timer (FRRT).

14WAIT for Feature Request reponse:

15WHEN a RETURN RESULT is received:

15-1Stop timer (FRRT).

15-2IF the message can be processed:

15-2-1IF the MS is still connected:

15-2-1-11IF the TerminationList Parameter is received:

15-2-1-11-1Execute the “MSC Routing Points Of Return” task (see 3.2.6)

3.2.6MSC Routing Points of Return

3For all terminations in the TerminationList parameter

3-4IntersystemTermination:

3-4-1Execute the “MSC Route the Call Leg Externally” task (see 3.3.8)

3.3.8MSC Route the Call Leg Externally

27ELSE IntersystemTermination parameter is received.

27-1Set destination to the DestinationDigits parameter within the IntersystemTermiantion parameter.

31Process a call setup toward the destination via the route and selected carrier.


Direct routing for roamer to roamer

8. Requirements for DRRR

HLR

  • HLR sends regnot RR including MDN and CFU-FA in CFI.

    STP Provider

  • STP Provider has MDN and CFU-FA statusfor the roamer.

  • STP Provider supports DRRR procedure (refer to page 10 to 15) and the error treatment (refer to page 14 to 17).

  • STP Provider modifies TLDN that indicates International call.

    • Remove Country Code

    • Set to “National ” on “Nature of Number”

  • STP Provider supports the error treatment when CFU-FA in GLR list is “Authorize and activated”(refer to page 18 to 24 ).


Direct routing for roamer to roamer

8. Requirements for DRRR (continued)

  • MSC

  • When a roamer dials *77 + MDN, the MSC sends a FEATREQ to STP Provider.

  • Intersystem Termination shall be done when the MSC receives featreq

  • [TERMLIST(IntersystemTermination)].

  • Local Termination shall be done when the MSC receives featreq

  • [TERMLIST(LocalTermination)].


Direct routing for roamer to roamer

9. DRRR billing

Objective

  • DRRR service provides a special price (discount rate compare to TROMBONE routing) only for the Roamers who roam to the same area.

    • Call maker (Origination) is charged only for originating airtime, except international toll to homeland.

    • Call receiver (Termination) is charged only for terminating airtime, except international charge from homeland.

  • DIRECT-R Originating CIBER shall be different from TROMBONE-R in order to provide a discount rate for roamers who made the call.


Direct routing for roamer to roamer

* TO : Trombone-R Origination

* TI : Trombone-R International

* TT : Trombone-R Termination

TO

TO

TT

TI

CDR

CIBER

TT

Trombone Routing


Direct routing for roamer to roamer

* DO : Direct-R Origination

* DT : Direct-R Termination

CDR

CIBER

DO

DO

DT

DT

Direct Routing


Direct routing for roamer to roamer

DO

TO

Comparison of TO and DO CIBER

DIRECT ROUTING

ORIGINATION CIBER

TROMBONE ROUTING

ORIGINATION CIBER

VS

“SPECIAL FEATURE USED”

“D (International)” or

“N (CDMA)”

could be included.

“V (DRRR) ”

shall be included.


Direct routing for roamer to roamer

DT

TT

Comparison of TT and DT CIBER

DIRECT ROUTING

TERMINATION CIBER

TROMBONE ROUTING

TERMINATION CIBER

VS

NO any special difference.


  • Login