SMS Signaling For Roaming Billing
SMS Signaling For Roaming Billing
SMS Signaling For Roaming Billing
*age 2 of 1,
&ontents
1. Introduction......................................................................................................................3 2. Existing Signaling............................................................................................................4 3. Proposed Solution............................................................................................................9 4. Glossary.........................................................................................................................17 5. Appendix !AP "ayer Identi#ier.................................................................................1$
*age 3 of 1,
1. Introduction
%&e 'oice and S!S (or)ing Group *'S(G+ o# t&e ,-G I.% is /or)ing to address t&e issues in0ol0ed /it& International S&ort !essage Ser0ice *S!S+ .oa1ing 2illing. 3# particular interest &as 4een t&e need to ensure t&at t&e &o1e operator is a4le to c&arge its su4scri4ers at a rate /&ic& accurately re#lects t&e di##erent intercarrier /&olesale rates t&at 1ay 4e c&arged 4y t&e operator5s indi0idual roa1ing partners. %&ere are se0eral 4road options possi4le and6or a0aila4le #or deli0ery o# t&e necessary in#or1ation *identi#ication o# t&e ser0ing operator+ to t&e &o1e operator. 2ased on expressed operator pre#erence *and t&e #act t&at so1e ot&er options are already a0aila4le+7 t&e 'S(G &as #ocused on t&e use o# t&e existing internet/or) A8SI941 signaling to carry t&e necessary in#or1ation to t&e &o1e operator5s !essage ,enter *!,7 a)a S!S,+. %&e 4illing record generated 4y t&e !, is used #or su4scri4er 4illing. Gi0en t&is general approac&7 t&ere are a nu14er o# para1eters /it&in t&e rele0ant signaling 1essages t&at could 4e used to carry t&e necessary in#or1ation. At t&e :une 2;;< I.%7 operators expressed t&eir pre#erence #or t&e use o# a transport9layer identi#ier *e.g. point code7 ,alling Party Address+ to speci#y t&e ser0ing net/or). %&is docu1ent descri4es t&is approac& in #urt&er detail7 including 1odi#ications to acco11odate di##erent signaling 1et&ods *point code routing and Glo4al %itle %ranslation+. (&en point code routing is used7 t&ere are t/o locations #or t&e ser0ing net/or) identi#ier7 and operator #eed4ac) on t&e pre#erred approac& is in0ited. An appendix descri4es an alternati0e approac& using A8SI941 para1eters to identi#y t&e ser0ing net/or).
*age - of 1,
2. Existing Signaling
!ost ,-!A operators today connect to t&eir international roa1ing partners 0ia a .oa1ing Ser0ice Pro0ider *.SP+. %&e .SP can represent all re1ote net/or) ele1ents as a single identity. %&is arrange1ent greatly si1pli#ies t&e con#iguration re=uire1ents in t&e operator5s net/or)7 &o/e0er in t&e process t&e identity o# t&e ser0ing net/or) can 4e 1as)ed #ro1 t&e &o1e operator #or S!S.
2.1.
!any operators today use Point ,ode *P,+ routing #or signaling to and #ro1 t&e .SP. %&e P,s are 1eaning#ul only /it&in a gi0en net/or)6country. %&e .oa1ing Ser0ice Pro0ider *.SP+ is assigned a point code inside eac& o# its custo1er net/or)s7 and uses leased lines to connect 4ac) to its o/n pre1ises. All roa1ing signaling to and #ro1 an operator5s roa1ing partners is 0ia t&e single .SP point code. %&is arrange1ent is s&o/n in >igure 1 4elo/.
%&e #ollo/ing su4sections s&o/ speci#ic scenarios rele0ant #or S!S. In eac& case t&ere 1ay 4e one or 1ore Signaling %rans#er Points *S%Ps+ present 4et/een t&e .SP and t&e indicated operator net/or) ele1ent t&ese S%Ps do not 1odi#y t&e tra0ersing 1essage in any /ay. %&e Signaling ,onnection ,ontrol Part *S,,P+ layer o# t&e 1essages is assu1ed to &a0e ,alled and ,alling Party Addresses eit&er containing P,s t&at 1atc& t&e -estination and 3riginating Point ,odes *respecti0ely+ toget&er /it& a Su4syste1 8u14er *SS8+7 or SS8 only. %&e S,,P routing indicator indicates t&at routing is 4ased on t&e !%P P, and t&e SS8.
*age
of 1,
*age 6 of 1,
*age . of 1,
2.2.
So1e operators use Glo4al %itle %ranslation *G%%+ to route calls t&roug& t&eir net/or)7 and to and #ro1 t&e .SP. Alt&oug& t&e use o# G%% can allo/ t&e trans#er o# 1essages 4et/een net/or)s /it&out )no/ledge o# eac& ot&er5s !%P P, allocations7 as used today #or ,-!A international roa1ing t&e .SP is still present as a P, t&at appears AinsideB t&e operator5s net/or)C G%% is used as a tool to si1pli#y routing ta4les in nodes o# large net/or)s. S%Ps6S,,P .elay points in t&e operator5s net/or) route t&e 1essage7 c&anging t&e !%P addresses accordingly. %&e #ollo/ing su4sections &ig&lig&t di##erences 4et/een Point ,ode and Glo4al %itle routing.
*age ! of 1,
*age , of 1,
3. $ro%osed Solution
As stated a4o0e7 t&e approac& pre#erred 4y operators is #or t&e .SP to 1odi#y an address para1eter in a transport layer *!%P and6or S,,P+ to identi#y t&e ser0ing net/or). %&e 1essage /ill appear to t&e &o1e operator to 4e co1ing #ro1 *or going to+ a di##erent location #or eac& ser0ing operator7 rat&er t&an Eust to t&e single .SP location as today. !any !,s today include t&e #ar end transport layer in#or1ation in t&eir 4illing record. I# t&is in#or1ation is set to a 0alue t&at is speci#ic to t&e ser0ing operator7 a &o1e operator can potentially i1ple1ent a per9ser0e c&arging sc&e1e /it& no 1odi#ications to t&eir !,s. %&is /as t&e pri1ary reason #or t&e operator pre#erence #or t&is approac& *see t&e 1eeting 1inutes #or 1ore detail+. %&e di##erences 4et/een t&e existing point code and G% routing sc&e1es necessitate di##erent approac&es to incorporate ser0ing net/or) in#or1ation #or operators /&o use t&ese sc&e1es.
3.1.
>or operators using point code routing7 t&e proposed approac& is to replace t&e single .SP point code /it& a P, t&at is speci#ic to t&e ser0ing operator. %&e set o# roa1ing partner P,s /ould 4e uni=ue to eac& &o1e operator *#or exa1ple7 S!S tra##ic #or 3perator 15s su4scri4ers roa1ing in 3perator 25s net/or) 1ay appear to 3perator 1 to use point code A *a point code assigned to t&e .SP #or t&is purpose 4y 3perator 1+7 /&ile S!S tra##ic #or 3perator 35s su4scri4ers roa1ing in 3perator 25s net/or) appears to 3perator 3 to use point code 2+. %&is arrange1ent is illustrated in >igure $ 4elo/.
%&e #ollo/ing su4sections s&o/ t&e c&anges to speci#ic scenarios. 8ote t&at Point ,odes can 4e carried in 4ot& t&e !%P and S,,P layers7 leading to so1e options regarding
*age 10 of 1,
/&ere to place t&e ser0e9speci#ic 0alue. Except /&ere noted7 t&e S,,P point codes are assu1ed to eit&er 4e a4sent7 or t&e sa1e as t&eir !%P counterparts.
*age 11 of 1,
As an alternati0e7 t&e .SP could 1odi#y t&e S,,P ,gPA P,7 /&ile lea0ing t&e 3P, untouc&ed. %&is 1ay represent a si1pler de0elop1ent e##ort #or t&e .SP t&an t&e !%P 1odi#ication discussed a4o0e. %&e resulting 1essaging is s&o/n in >igure 11 4elo/C
%&e .eturn .esult addressing is identical to t&e !%P 1odi#ication case. Alt&oug& it /ould 4e con0enient i# t&e .eturn .esult /ere to use t&e .SP *generic+ P, at t&e !%P layer *t&ere4y a0oiding t&e need #or S%P routing ta4les to include t&e ser0e9speci#ic P,s+7 t&is is unli)ely to 4e t&e case #or real9/orld !,s. %&e reason is t&at t&e internal pri1iti0e used to pass t&e recei0ed 1essage #ro1 t&e S,,P layer up to t&e application can only carry a single point code. I#7 as &ere7 4ot& !%P and S,,P carry a *di##erent+ P,7 only t&at #ro1 S,,P /ill 4e preser0ed. (&en t&e application sends t&e return 1essage7 it /ill 4e directed to t&e P, seen 4y t&e application. 2ot& S,,P and !%P /ill use t&is P, #or t&eir respecti0e destination address para1eters. %&is arrange1ent is s&o/n in >igure 12 4elo/C
*age 12 of 1,
>or t&e &o1e operator7 t&e S,,P 1odi#ication approac& 1ay 1ean t&at no S%P gate/ay screening c&anges are re=uired *unless gate/ay screening 6 access 1ediation is used t&at c&ec)s t&e S,,P ,gPA+. Alt&oug& t&e use o# di##erent !%P and S,,P P,s 1ay 4e so1e/&at unusual7 t&ere s&ould 4e no pro4le1 transporting t&ese 1essages t&roug& t&e operator5s net/or)7 as t&e S,,P layer is not exa1ined 4y S%Ps. %&e generation o# a 4illing record is presu1a4ly a #unction o# t&e application7 rat&er t&an t&e signaling transport layers. %&e point code included in t&e 4illing record s&ould t&ere#ore 4e t&e one carried in S,,P7 /&ic& /ill gi0e t&e desired e##ect o# identi#ying t&e ser0ing net/or).
*age 13 of 1,
*age 1- of 1,
3.2.
>or operators using Glo4al %itle *G%+ routing to signal to6#ro1 t&e .SP7 a ser0e9speci#ic Glo4al %itle is used instead o# a Point ,ode. %&e !, 1ust include t&e S,,P ,alled6,alling Party Address Glo4al %itle in its 4illing record to ena4le !%6!3 ser0e9 speci#ic 4illing7 respecti0ely. %&e #ollo/ing su4sections discuss c&anges #or indi0idual scenarios.
*age 1 of 1,
*age 16 of 1,
3.3.
Discussion
%&e solution descri4ed a4o0e s&ould 1eet operators5 needs #or ser0e9speci#ic 4illing #or S!S roa1ing. 3perators using P, routing and t&ose using G% routing re=uire di##erent solutions7 4ot& o# /&ic& 1ust 4e supported 4y t&e .SP. %/o options are s&o/n #or P, routing. %&e S,,P 1odi#ication approac& is pre#erred on t&e assu1ption t&at t&is is easier #or t&e .SPs to i1ple1ent *and 1ay also re=uire #e/er Gate/ay Screening c&anges on t&e part o# t&e &o1e operator+. %&e re=uire1ents on t&e !, 4illing record s&ould 4e t&e sa1e #or eit&er option.
*age 1. of 1,
4. #lossar(
,-G ,dPA ,gPA -P, G% G%% @". I!SI I.% !AP !, !,, !8, !3 !S, !S,I!% !%P 3P, P, .SP S,,P S!-PP S!S S!S?3A S!S, S!S83% S!S.EF SS8 %>A %>P 'S(G ,-!A -e0elop1ent Group ,alled Party Address ,alling Party Address -estination Point ,ode Glo4al %itle Glo4al %itle %ranslation @o1e "ocation .egister International !o4ile Station Identity International .oa1ing %ea1 !o4ile Application Part !essage ,enter *a)a S!S,+ !o4ile ,ountry ,ode !o4ile 8et/or) ,ode !o4ile93riginated !o4ile S/itc&ing ,enter !o4ile S/itc&ing ,enter Identi#ication !o4ile9%er1inated !essage %rans#er Part 3riginating Point ,ode Point ,ode .oa1ing Ser0ice Pro0ider Signaling ,onnection ,ontrol Part S!S -eli0ery Point to Point S&ort !essage Ser0ice S!S?3riginatingAddress S&ort !essage Ser0ice ,enter *a)a !,+ S!S 8oti#ication S!S .e=uest Su49Syste1 8u14er %rans#er Allo/ed %rans#er Pro&i4ited 'oice G S!S (or)ing Group
*age 1! of 1,
%&e para1eters descri4ed 4elo/ 1eet 1any 4ut not all o# t&ese criteria. >or t&e In0o)e7 custo1 0alues o# t&e S!S?3riginatingAddress *S!S?3A+ are used to identi#y t&e ser0ing net/or). In#or1ation a0aila4le at t&e ti1e o# /riting indicates t&at /&ile so1e operators 1ay populate t&is para1eter7 no9one is exa1ining it /&en recei0ed at t&e !,. (&et&er it is included on !, 4illing records is un)no/n. %&e exact #or1at o# t&e identi#ier is largely uni1portant7 and is le#t #or #uture speci#ication i# re=uired. An !S,I-9li)e 0alue or !,,9!8, /ould see1 to 4e logical candidates. >or t&e .eturn .esult7 A8SI941 .e0 E *#ollo/ing IS9725+ allo/s t&e presence o# t&e !S,I- para1eter in t&e 1essage. Alt&oug& intended #or 3%ASP usage7 t&e !, could 4e 1odi#ied to include t&is 0alue in t&e 4illing record *no #urt&er !, action on t&is para1eter is re=uired+. A single !S,I- per ser0ing operator /ould 4e de#ined and ad0ised 4y t&e .SP. %&e ser0e9speci#ic 0alues c&osen are assu1ed to 4e co11on #or all &o1e operators using t&is solution. %&is is in contrast to t&e transport9layer solution in t&e 1ain 4ody o# t&e docu1ent7 in /&ic& a #ull set o# per9ser0ing roa1ing partner 0alues is 1aintained 4y t&e .SP #or eac& participating &o1e operator.
*age 1, of 1,
>igure 1$ and >igure 19 4elo/ s&o/ t&e c&anges to t&e S!-PP6s1dpp operation #or !39 and !%9S!S. P, routing is assu1ed in t&e diagra17 4ut t&e !AP layer c&anges apply e=ually to G% routing. All ot&er operations are unc&anged #ro1 t&e existing arrange1ent.