Charging Solution Description
1
PURPOSE AND SCOPE.................................................................................................................................................... .3
1.1 2
Network topology.........................................................................................................................................................3
ERICSSON CHARGING SYSTEM............................................................................................................................. .....4
2.1 2.2
Introduction...................................................................................................................................................................4 Charging System Network Elements............................................................................................................................5
2.2.1 Data Point (SDP Prepaid)...........................................................................................................................6 2.2.2 Service Administrative System (MINSAT).............................................................................................................................8 2.2.3 !ar"in" ontro# Node (N)................................................................................................................................$ 2.2.% Interactive &oice 'esponse System (M*I&').....................................................................................................1+ 2.2., Acco-nt Inormation and 'ei## System (AI')........................................................................................................12 2.2.6 Acco-nt /inder (A/)..............................................................................................................................................1% 2.2.0 &o-c!er Server (&S)............................................................................................................................................... 1% 2.3 ssociated network elements......................................................................................................................................15 !achine"!achine #!2!$ Inter%aces..........................................................................................................................1& 2.4 ny 'ime Interrogation #'I$...........................................................................................................................................................1( )nstructured Supplementary Ser*ice +ata #)SS+$..........................................................................................................................1( )nstructured Supplementary Ser*ice +ata #)SS+$..........................................................................................................................1( !o,ile Num,er -orta,ility #!N-$...................................................................................................................................................2
/i#e Transer Protoco# (/TP).............................................................................................................................................. 2+ -stomer Administrative Interace (AI)............................................................................................................................2+ Administration omm-nication Interace Protoco# (AIP)................................................................................................21 ser omm-nication Inte"ration Protoco# (IP)............................................................................................................21 MTTP..........................................................................................................................................................................21 2.5 Signalling....................................................................................................................................................................22 2.,.1 SS and SI4T'AN...............................................................................................................................................23 3
OFFERED CHARGING SOLUTION FOR TELCO X.................................................................................................24
3.1 +imensioning /igures.................................................................................................................................................24 3.1.1 Proposed Net5or Arc!itect-re..............................................................................................................................2% 3.1.2 SDP.........................................................................................................................................................................2% 3.1.3 N........................................................................................................................................................................2, 3.1.% AI'..........................................................................................................................................................................26 3.1., &S...........................................................................................................................................................................20 3.1.6 MINSAT..................................................................................................................................................................20 3.1.0 S-mmary.................................................................................................................................................................20 3.2 0%%ered /eatures..........................................................................................................................................................2 3.3 Ser*ices.......................................................................................................................................................................43 3.3.1 Airtime Transer.....................................................................................................................................................%3 3.3.2 SA (Service A5are !ar"in" ontro#) 3.+........................................................................................................%3 3.4 usiness -rocesses......................................................................................................................................................44 3.%.1 S-7scri7er Provisionin".........................................................................................................................................%% 3.%.2 Postpaid to Prepaid process and visa versa...........................................................................................................%0 3.%.3 /orced Disconnection............................................................................................................................................%$
3.%.% 3.%., 3.%.6
&o-c!er Provisionin".............................................................................................................................................%$ &o-c!er creation #oadin" and stat-s c!an"e.........................................................................................................,+ &o-c!er oadin"....................................................................................................................................................,2
3.4..1 3.4..2
3.%.0
oucher atch Input /ile............................................................................................................................................... 52 oucher atch eport /ile.............................................................................................................................................54
&o-c!er State c!an"e............................................................................................................................................. ,,
3.4.&.1
CS3 oucher State and 6i%ecycle................................................................................................................................... 55
3.%.8 S-7scri7er ieyc#e..............................................................................................................................................,0 3.5 ccount Structures in Charging system......................................................................................................................5( 3.,.1 Acco-nt 'ei##.........................................................................................................................................................62 3. End")ser communication...........................................................................................................................................2
3.6.1 3.6.2 3.6.3
Acco-nt 'ei##.........................................................................................................................................................62 9a#ance In:-iryNotiication..................................................................................................................................63 !ar"in" System initiated voice anno-ncements...................................................................................................63
3..3.1 3..3.2 3..3.3 3..3.4
Call Set"up nnouncements...........................................................................................................................................3 In"Call nnouncement...................................................................................................................................................4 End"o%"Call nnouncement........................................................................................................................................... 4 !andatory announcements............................................................................................................................................5
3.& Charging...................................................................................................................................................................... 3.0.1 !ar"ed Services....................................................................................................................................................66 3. Customer Care.............................................................................................................................................................& 3.( eports........................................................................................................................................................................( 3.1 + and C+ generation.............................................................................................................................................( 3.11 3.12 3.13 3.14
oaming......................................................................................................................................................................&1 07! -rocedures........................................................................................................................................................ &2 6icense !anagement..................................................................................................................................................&3 /ault !anagement.......................................................................................................................................................&3
4
TERMINOLOGY...................................................................................................................................................... ........ 75
5
REFERENCES...................................................................................................................................................................77
1
PurposeandScope The purpose of this document is providing a high level description of the different functionali ties that will constitute the Ericsson Charging System 3.0 (CS3.0) solution for TELC ! . "escription of functionalities and su#$systems included in this document may vary in future depending in the decisions ta%en during negotiation phase.
1.1
Network topology &ind #elow overview description of each main element on the networ%' SC Server' Ericsson edia *' Ericsson +SC' Ericsson +SC ,L-' lcatel ,LSS/$S/' Ericsson SCC' Ericssson S$C' Ericsson SS$C' ,uawei -+T' ,uawei Ericsson Charging System will #e used for real$time charging of the services. Ericsson Charging System is capa#le to charge all cases for postpaid and prepaid su#scri#ers #ut postpaid #usiness processes and rules need to #e discussed with the Customer to fulfill the #usiness reuirements.
2 2.1
Ericsson Charging System Introduction
Charging System is a cost$efficient charging solution suita#le for operators with up to 31 million su#scri#ers. Charging System ma%es it possi#le for a networ% operator to charge in real$ time for events and sessions in the mo#ile networ%. These events and sessions can for e2ample #e voice calls Short essage Service (SS) or events using eneral 4ac%et -adio Service (4-S). 5t is also possi#le to allow service authori6ation and service$aware charging including session control.
Each su#scri#er is connected to an account which can #e refilled for e2ample #y using a voucher. *ith the decoupling of the traffic flow from the administrative system the operator is provided with a clean administration$ and provisioning interface &acilitating the integration with #usiness$support systems. Charging System is constructed as a decoupled architecture for all mar%et segments with highlights li%e Su#scri#er Segmentation Service fferings Su#scri#er Segmentation ccount roup 5dentity Community Charging and Enhanced End of Call 7SS" /otification. 4owerful tools for tariff management mar%et segmentation #onus$ and loyalty programs as well as for statistics generation are provided and will ena#le TELC ! to' •
5ncrease revenue from e2isting services
•
Create revenue from new services
•
Stimulate usage
•
Strengthen competitiveness
See System Description Charging System 3.0 in C45 Li#rary for further general information.
2.2
Charging System Network Elements +elow diagram shows general Charging System elements. 5n the figure #elow Ericsson ulti ediation is shown in different colour #ecause TELC ! is not yet decided to include it. +ut in any case a mediation system should #e in the total solution in order to handle C"collection formatti ng and distri#uting it to post$processing system. E can also handle postpaid roaming cases #y processing T4 files using E-S (Ericsson -oaming Solutions) module on it. So that final diagram could change depending on decisions ta%en after this document is delivered.
/i"-re;
Charging System consists of the following networ% elements'
2.2.1
Service Data Point SDP Prepaid!
The S"4 networ% element contains the data#ase with su#scri#er and account information. The traffic functions of the S"4 include rating of calls and events post$processing of Call "etail -ecords (C"-) and initiation of 7SS"$ and SS$notifications. The S"4 also provides the evaluation logic reuired for the call$control performed #y the SC4 or CC/. S"4 is also used to trigger the setup of a 7SS" Call$#ac% Call.
The S"4 holds and administers the following data' • • •
Su#scri#er and ccount data Service Class data nnouncement Class data
• • • • • • • • • •
7sage ccumulators data Tariff and Charging nalysis data Su#scri#er Life$Cycle data "edicated ccounts data &amily and &riends data 7SS" and SS /otification data 4romotion 4lan data ,L- #loc%ing data Community data Segmentation data
The standard S"4 configuration is developed with two identically euipped servers. The figure contains SC4s to demonstrate the connection to elements in the SS8 networ%. E2amples of elements connected through the L/ are also shown. The Sun anagement Center server is a Sun wor%station which is also used for installation and maintenance of the system. &or e2ample it can #e used to run the graphical user interfaces. The main tas% is however to e2ecute the alarm monitoring software for hardware alarms. The S"4 cluster is a 7/5! #ased system running on Sun Solaris 9. 5t is #ased on two identically euipped Sun servers. Each server #y itself is not fault tolerant although many hardware components are redundant. 5nstead the S"4 cluster is designed to allow for failures to happen and the capacity of the cluster is enough to allow one machine to fail and still #e a#le to manage all traffic that is generated #y the SC4s and other surrounding networ% elements. Each server in an S"4 cluster supports up to 1 5S- #oards. Each 5S- #oard supports :; SS8 LSSL lin%s or ; SS8 ,SSL lin%s. n S"4 cluster with one 5S- #oard per server supports <1= SS8 lin%s. dditional SS8 signalling capacity can #e o#tained #y using S5T-/ on a dedicated Ethernet port or #y adding a second 5S- #oard.
2.2.2
"dministrative System #INS"$!
o#ile 5/ Service dministration Tool (5/ST) is responsi#le for all su#scri#er administration in Charging System. 5/ST is the software application that is used #y networ% operators to manage the Charging System service. The 5/ST client interface consists primarily of a >ava client which can #e run on 7/5! or the *indows operating systems. There is also an pplication 4rogramming 5nterface (45) server that runs on 7/5! and supports a programmatic interface (licensa#le). The >ava client encompasses the following areas of management'
Customer Care dministration +atch dministration ar%eting Statistics peration and aintenance ( and ) dministration
/o traffic is handled #ut interaction in real$time with other systems for provisioning and updates is possi#le through the e2ternal interfaces provided.
t su#scri#er provisioning and removal "5/ may interact #oth with the & and S"4. There is an option to connect e2ternal systems for e2ample ,Lvia E to "5/ for the su#scri#er administration support. 5/ST communicates with the other Charging System networ% elements as follows'
2.2.%
Charging Control Node CCN!
The CC/ logic is a#le to handle Circuit Switched calls and data for CS
• • • • • • • • • • • •
•
5nterrogation of the S"4 cting as SC& and SC4 for CS
The CC/ is also responsi#le for the following lists and administration' +arred Location /um#ers List of SC$addresses (only for C4v<) List of @L- num#ers and Location /um#ers that #elong to the ,4L/ /um#er normali6ation apping of /um#er 4orta#ility 5nformation • • •
• •
and +$num#er *hite lists Configuration data for S"4 selection Configuration data for C"- generation Configuration data for num#er conversions (for e2ample country codes nationalAinternational prefi2es) Configuration data for call control • • • •
•
2.2.&
Interactive 'oice ( esponse S ystem )#*+I'(!
The 5nteractive @oice -esponse (5@-) is a voice #ased self$service application for refill account #alance and life cycle inuiries language settings su#scription changes etc. The 5@- provides recorded menu options (voice prompts) to the su#scri#er. The su#scri#er responds #y pressing the specified %eys on the mo#ile device ("T& signaling).
/i"-re; I&' connections
EricssonBs @!L 5@- pplication is #ased on the @!L (@oice !L) standard. The application can inter wor% with any media platform supporting the standard. Ericsson has verified its @!L 5@- pplication inter wor%ing with ,4 penCall edia 4latform (C4) which supports the standard and Ericsson.s reuirements on a media server.
pplication Server @!L 5@- pplication Configuration anagement
Callflow pplication
Log management
S/4
Statistics management >+oss *e# Server
larm management ,TT4
SS
C4 4latform @oice!L 5nterpreter
S/4
Call Control
Signaling Soft"S4 S54
5S"/
5S74
r i ber can uset he I VR t o change andenqu i r e about ount acc The subsc I nf or mat i on . Th e I VR canal so be use d f or ge t t i ng i n con t act i t h w t he
Cust om er ar Ce. y B sendi ng announcem ent s andv oi ce pr om pt s t o t he subscr i berandr ecei vi ng Dual Tone Mul t i Fr equ ency t one s ( DTMF) n i r esp onse ,t he I VR hel ps h t e su bscr i ber i n t he i nt er act i on f or acco unt updat es an d enq ui r i esab ou t ac co un t bal an ce - an d exp i r y d ae t s.
fter the *elcome message the su#scri#er is presented with the main menu' •
• • • • • •
2.2.,
+alance with the options' $ ain ccount 5nuiry with "edicated ccount +alance 5nuiry $ ccumulator 5nuiry @alue @oucher 5nuiry Transfer to CS Language Change S5S"/ -eadout dvertising nnouncement -efill
"ccount In-ormation and (e-ill System "I(!
The 5- system contains logic for refilling su#scri#er accounts. 5t performs the calculations needed for e2tend ing e2piry dates and adding money to the su#scri#er accounts. The 5- system also provides information related to the su#scri#er accounts. The 5- system can handle refills initiated from many different sources #oth in the SS8 networ% and in the 54 networ%. The 5- system is connected to the 5@-(s) the S"4(s) the @S the & and to the "5/ system. 5t can also #e connected to the SS for fault management using the T!& alarm adaptation unit in the SS. The 5- system consists of one or several 5- servers. Each 5- server is in itself an autonomous system consisting of #oth hardware and software. "eploying multiple 5- servers provide redundancy while at the same time increasing capacity. /o information a#out the su#scri#ers is stored on any of the 5- servers. ny 5- server is therefore a#le to handle reuests from any su#scri#er at any time. +usiness data can #e synchroni6ed #etween the 5- servers. The clients of the 5- system that is the "5/ the 5@-(s) and the ,L-(s) may at their own discretion route communication data to two or more 5servers in order to #enefit from the capacity and redundancy provided. -euests to refill prepaid accounts are routed to the 5- system. The 5system calculates the refill data and then updates the account in the S"4. &or voucher #ased refills the 5- system consults the @oucher Server system. -euests for o#taining account information such as #alances and e2piry dates are also routed to the 5- system which then o#tains the reuired information from the account in the S"4.
5t is also possi#le for the su#scri#er to refill the account using a specific 7SS" service code together with an activation code. The activation code is used for identification of the uniue refill voucher in the @S. 5- supports the following 7nstructured Supplementary Service "ata (7SS") functions' •
7SS" @oucher -efill
•
7SS" Enuiry
The 5- is also responsi#le for the following' • • •
dministration of 4romotions -efill configurations dministration of 7SS"$communication
This includes administration of te2t$messages and signalling configuration. 2.2.
"ccount /inder "/!
The AF enabl es u sa ge of mul t i pl e SDPs.I ti s co l l oca t ed wi t h AI R.
2.2.0
'oucher Server 'S!
The @S system is a su#system in Charging System that stores and manages vouchers. The @S can wor% as a stand$alone system or it can cooperate with the 5- server and the S"4 to perform a full voucher refill function. The @S offers generation storing and administration of vouchers. Security is o#tained #y encrypting the voucher activation num#er in the data#ase.
*hen su#scri#ers want to refill their prepaid accounts a reuest to do so is routed to the 5- system. The 5- system reuests the @S system to reserve a voucher for the su#scri#er. 5f the voucher is availa#le and has not e2pired the @S system returns voucher data to the 5- system which then proceeds to calculate refill data. The 5- system then updates the su#scri#ers account in the S"4. 5f the update of the account was successful the 5- system reuests the @S system to commit the usage of the voucher. The voucher is now used and cannot #e used again. Should the update of the account fail the 5- system instead reuests the @S system to roll#ac% the reservation of the voucher. The voucher is now availa#le for usage again.
The VS i s r es po nsi bl e f or he t ad mi ni st r at i on of vo uc he r s wi t h f ol l ow i ng admi ni st r at i ons: @oucher eneration 5mport of voucher$#atches generated #y a third$party source
2.%
4urging of @ouchers and @oucher history +atch State Changes 5ndividual @oucher State Changes -eporting Enuiries of @oucher 5nformation
"ssociated network elements ssociated networ% elements that can #e integrated with CS30'
•
Ericsson Multi Activation (EMA)
Er i cs so n Mul t i Act i va t i on pr ovi des t he oper at or s wi t h a uni f or m machi net omachi ne i nt er f ace bet ween busi nesssy sem t and net wor k el ement s t hat st or e su bscr i pt i onr el at ed i nf or mat i on. t I m ay be use d f or se r vi ceco nt r ol bar r i ng and f or ADMI N pr ov i si oni ng. I t ca n be co l oca t ed wi t h sm al lMI NSAT. •
Multi Mediation Solution (EMM)
Er i cs so n Mul t i Medi at i on, i s afle xb i l e i nt er f aceuse df or handl i ng of t he Cal l Det ai l Reco r ds( CDRs) od pr uce d byCha r gi ngSyst em f or ur f t he r pr oce ssi ng i n ot her ne t wor k el ement s.A Mul t i Medi at i on so l ut i on i s nece ssa r y f or h t e pr oce ssi ng of Cal l hi st or y.The Cal l Hi st or y f eat ur e i s av ai l abl e when usi ng MI NSATasad mi ni st r at i onsyst em . A Mul t i Medi at i on so l ut i on i s n ece ssa r y o f rt he f eat ur e CDR Pr oce ssi ng. The Mul t i Med i at i on Sol ut i on fil t er s Cha r gi ng Syst em CDRs t o be ha nd l ed f or Offli ne ch ag r i ng , andr ef or mat t ed co pes i oft hese l ec t edCDRs a r e se ntona uni fie di nt er f acet ot he SDP wher e ch ar gi ng anal ysi s a t ke s p l ace . For Rea l Ti me Cha r gi ng , Mul t i Med i at i onwi l l co nve r ti nco mi ng messa gesi n Par l ayi nt o SCAPDi am et err eq ue st s. •
Home Location Register (HLR)
Al l Char gi ngSyst em su bs ci r pt i on s ar e st or edi n t heHom e Lo ca t i onRegi st er ( HLR ) ,j ust i ke lor di na r y po st pa i d su bscr i pt i ons.he T SDP use s t heHLR f or bar r i ng of ce r t ai n se r vi ce s, or f e xa mpl e, e t r mi nat i ng ca l l s t o a Char gi ng Sys t em account .
Mobile Services Switching entre!"isitor Location Register (MS!"LR) •
Al l ci r cu i t sw i t ch ed ca l l s o t be ch ar ged byChar gi ng Syst em ar e r out ed byan MSC t o an SSF or gsm SSF.Ci r cui t S wi t ched Mobi l eor i gi nat i ng SMSs ha nd l edby ha Cr gi ngSyst em , ar e ou rt edt o he t gsm SSF. •
Service Switching #unction (SS#)
The SSF i ni t i at es e sr vi ceexe cu t i on i n t he PSL, and r ece i ve s n i st r uct i ons r f om t he P SL on how t o h andl e t he c al l . The SSF su per vi se s ca l l s a nd r epor t s ca l l du r at i ont ot he P SL.TheSSF i s n omal r l y nt ieg r at ed i nt he( G) MSC/ VLR . •
Serving $%RS Su&&ort 'ode (S$S')
The SGSN ha nd l es al l pa cket da t a ser vi cesi n t he mob i l e net wor k.Thi s i ncl ud es mob i l i t y man ag em en t u schas i nt er sys t em ha nd overi t hi w n an d r oa mi ngbe t wee nmob i l e n ew tor ks an d og li cal l i nk an mag em en t . TheSGSN i s r esp on si bl e f or st e ab l i shm en t , m od i ficat i on an d r el ea se of en d use r P DP co next ts a ndf orha nd l i ngofpa cket sw i t ch edSMS. I t wi l l be i nt egr at ed i nt he CGSN. •
$atewa $%RS Su&&ort 'ode ($$S')
TheGGSN con t act s he t Cha r gi ngSyst em f orr at i ngan d ch ar gi ng . TheGGSN pr ovi desnant ier f aceet w been t he G SSN ( t ow ar ds he t MSs)and Packe t Dat a Net wor ks( PDNs) , su chas h t e I nt er net , co r por at e i nt r anet s,and pr i va t e dat a net wor ks .I t wi l l be i nt egr at ed i n t he CGSN.
2.&
#achine+#achine #2#! Inter-aces The achine to achine interfaces #etween the networ% elements in Charging System are e2plained #elow. ISDN ser Part ISP!
5S74 is the Signalling System /o. 8 (SS8) protocol that provides the signalling functions reuired to support #asic #earer services. 5t is used #etween SC and ,4$5@- or @!L$5@-. 5t is also used #etween ()SC and stand$alone SS4. C"#E* "pplication Protocol C"P!
C4 is an SS8$#ased protocol used for the communication #etween gsmSS&AgprsSS& gsmSC& and gsmS-&. Charging System supports three different versions of C4' 1. C4v<
Charging System uses C4v< together with 5/4 CS
Charging System uses C4v1 for CS n$line Cost and Credit Control (CEL ph1 #ased). riginating forwarded and terminating calls are supported #oth in ,4L/ and @4L/. Call setup announcements can #e played through an assisting gsmSS& in ,4L/ in case the gsmS-& in the visited SCA@L- in @4L/ cannot provide the proper announcements. 5n$ call announcements are not supported #y C4v1 #ut a tone can #e played 30 seconds #efore call cut$off instead. The gsmSC& function for C4v1 in Charging System is provided in ,4L/ #y either SC4$T 5/S CC/ or a com#ination of those networ% elements. %. C4v3
Charging System uses C4v3 for SS -eal$time Charging +ased on CEL 4h3 and for 4-S -eal$time Charging +ased on CEL 4h3. Circuit and pac%et switc hed originating SS as well as 4-S is supported #oth in ,4L/ and @4L/. The gsmSC& function for C4v3 in Charging System is provided #y the CC/ in ,4L/. Ericsson (eal $ime Charging Protocol E($C!
Charging System uses E-TC for CS and SS n$line Cost and Credi t Control (Ericsson 4roprietary E-TCA-TCf). riginating forwarded and terminating circuit switched calls and srcinating and terminating SS are supported in ,4L/. -oaming terminating calls are supported if the gSC is located in the ,4L/. The reas on to use E-TC is that capacity is gained in the SC server compared to usage of CEL #ased n$line charging control services. nnouncements with E-TC are handled the same way as announcements with C4v1. E-TC is #ased on the "iameter Credit Control #ut has #een adapted to #e a#le to #e sent with TC4ASS8 as a #earer. Diameter Service Charging "pplication Protocol SC"P!
"iameter Service Charging pplication is a vendor specific application that run as an application on the "iameter #ase protocol. The "iameter #ase protocol is understood and supported #y application servers residing in the service networ%. The application servers will e2ecute internet application services and service ena#lers will #e a#le to provide the application servers with interfaces and interwor%ing capa#ilities with Charging System through CC/. The "iameter interface can #e used to connect to the nline ediation. *ightweight Directory "ccess Protocol *D"P!
The L"4 interface is used #etween two S"4s or #etween S"4 and an e2ternal data#ase in order to fetch community data for the non$charged su#scri#er. L"4 is used for provisioning and management of 4SL and #etween E and CC/ for su#scri#er provisioning. Diameter Service (ating "pplication Protocol S("P!
"iameter Service -ating pplication is a vendor specific application that run as an application on the "iameter #ase protocol. "iameter Service -ating pplication is used #etween S/ or SS/ and CC/ for Service ware Charging and Control (SCC).
#oile "pplication Part #"P!
4 is an SS8$#ased protocol used for data deliveries #etween different networ% elements. 4 provides the signalling procedures reuired for information e2change #etween entities in the S networ%. To support CEL 4 version 3 or later is reuired #etween'
the @L- and ,Lthe SC and ,L-
ny Time 5nterrogation (T5) T5 is an operation used for ueries from CC/ and Charging System 5/ to the ,L- in order to retrieve location information for a specified su#scri#er. 7nstructured Supplementary Service "ata (7SS") (ETS5) 4 is used for sending and receiving 7SS"$operations #etween the ,L- and 5- for -efill and enuiry and #etween ,L- and S"4 for 7SS" End$of$Call notifications. The protocol used is #ased on 344 TS 19.001 and used for #oth 7SS" reuests initiated #y S as well as 7SS"s initiated #y networ%. (ETS5) 4 is also used #etween ,L- and S"4 for triggering a 7SS" Call #ac% call. nly phase 1 mo#iles (or higher) is supported. Note that the ,L- must for mo#ile initiated 7SS" (that is for enuiries refill
and call$#ac%) #e a#le to provide an S5S"/ to the Charging System. The ,L- must for networ% initia ted 7SS" (that is notificati ons) #e a#le to accept an S5S"/ as the only su#scri#er identifier. Alcatel HLR in the Network should support SSD operation. Ericsson adaptation o- #"P
The Ericsson variants of the 4$signalling protocol with propriety e2tensions are protocols defined to transfer data for the Ericsson proprietary services.
7nstructured Supplementary Service "ata (7SS") Ericssons adaptation of 4 E4 is used for sending and receiving 7SS"$operations #etween the ,L- and 5- for -efill and enuiry and #etween ,L- and S"4 for 7SS" End$of$Call notifications. The protocols used are E4 version < and 1. E4 version < can #e used for 7SS" reuests initiated #y S while E4 version 1 can #e used for S as well as 7SS"s initiated #y networ%. E4 is also used #etween ,L- and S"4 for triggering a 7SS" Call #ac% call.
o#ile /um#er 4orta#ility (/4) T5 with Ericsson proprietary e2tensions is used for ueries from 4SL Charging System 5/ and CC/ to the o#ile /um#er 4orta#ility data#ase located in &/-. Intelligent Network "pplication Protocol IN"P CS13!
5/4 CS
L is a language used for communication with e2changes. The command language for !E is an application of the 5T7$T$L. There are also some additional functions which have not #een defined #y 5T7$T. L is for e2ample used for the following' +arring and 7n#arring of services through S"4 and ,L- with communication over TC4A54. num#er of activities for e2ample installation and removal of su#scri#ers through 5/ST and ,L- or E and ,L- with communication over TC4A54 or !.1D. 4rovisioning and anagement of Charging System 5/ and 5/$5@Services through SS and SC4 with communication over TC4A54 or !.1D. Life Cycle notification to e2ternal system.
/ile $rans-er Protocol /$P!
&T4 is a protocol in the TC4A54 family used for transferring files #etween machines running TC4A54. &T4 is used for the following' &T4 over TC4A54 is used for transport of C"-s #etween SC4 4SL CC/ S"4 5- "*S the ulti ediation solution and "5/.
Transport of num#er lists #etween the S"4 and the ulti ediation solution for #atch files on the 5- S"4 @S and "5/ as well as for sending #alance threshold notification$files to e2ternal entities.
Customer "dministrative Inter-ace C"I!
Ericssons C5 is an interface #etween a Customer dministration System (CS) and Charging System networ% elements. C5 is used for the following' 5t ma%es it possi#le to send commands through a TC4A54 or !.1D connection. C5 over TC4A54 is provided in 5/ST for su#scri#er administration. The 5/ST 45 is #ased on a C5 service model and allows client applications to access the 5/ST system in order to insert modify or delete data. The 5/ST interface uses a synta2 #ased on C5. 5t is not a full implementation of the C5 interface and it uses functions that are not part of C5. Communication #etween S"4 and E in order to access ,L-. +arring and 7n#arring of services through S"4$,L- with communication over TC4A54. num#er of activities for e2ample installation and removal of su#scri#ers through 5/ST$,L- with communication over TC4A54 or !.1D. 4rovisioning and anagement of Charging System 5/ and 5/$5@- (SC4$T) Services through SS$SC4 with communication over TC4A54 or !.1D. 4rovisioning and anagement of 4SL. &amily and &riends.
Customer Care "PI CC+"PI4CC+"D#IN!
CC 45 is used on 5/ST. The 5/ST 45 is implemented as a C5$ service model and ena#les client applications to communicate with the 5/ST system to perform su#scri#er provisioning and customer care tas%s. The 5/ST 45 server can #e configured as a networ% service on 7/5!. "dministration Communication Inter-ace Protocol "CIP!
C54 is #ased on !L$-4C over ,TT4. C54 is intended as an option to integrate an e2ternal system for su#scription administration of Charging System. ser Communication Integration Protocol CIP!
7C54 is #ased on !L$-4C over ,TT4. E2ternal refill support and e2traction of account details from Charging System is provided through 7C54. 'oucher Server Integration Protocol + "dministrative 'SIP+"!
@S54$ is an !L over ,TT4 #ased protocol which ma%es it easy to integrate with a central integration point within a networ%. The protocol supports administrative and refill related services.
)#*45$$P
!LA,TT4 is used in the communication #etween 5- and #oth the administrative system 5/ST and SCS. 5t is used #etween ,4$5@- or @!L$5@- and 5- for refill and enuiries. 5t is also used for voucher enuiries #etween @S and #oth 5/ST and SCS as well as #etween 5and @S for refill. (emote Procedure Call (PC!
The -4C protocol is used #oth #y 5/ST and SCS for administration of account$ and su#scri#er data and for user communication through S"4. Domain Name Service DNS!
The "/S protocol is used for loo%$up of S"4$identity and address in the &. 5/ST and SCS uses "/S also to update the &. Short #essage Peer to Peer S#PP!
The S44 protocol is used for the signaling #etween S"4 and SS$SC in order to achieve SS notification.
2.,
Signalling The transition from T" #ased SS8 signalling to 54 #ased signalling is also occurring within Charging System similar to the core networ%. 5n Charging System 3.0 a num#er of new 54 #ased protocols are used and the introduction of new 54 #ased protocols is also planned for future releases. &igure #elow provides an overview of the SS8 and 54 #ased interfaces in Charging System 3.0
2.,.1
5SS* and SI6$("N
,SSL and S5T-/ have #een introduced in a phased manner to Charging System. The primary o#ective is to alleviate the limitations that narrow#and SS8 lin%s (LSSL) give in terms of signaling capacity. *ith ,SSL or S5T-/ the operator can fully utilise the node capacities. nother #enefit of ,SSL and S5T-/ compared to traditional LSSL is that the num#er of lin%s will #e reduced which will lead to less maintenance and configuration. /ote that the introduction of ,SSL or S5T-/ may reuire a reconfiguration of the SS8 networ%. &or instance ST4 Sw and signaling relay functions must #e considered as well as the 54 #ac%#one in case of S5T-/. 5n summary all !E #ased nodes the o#ile$w SS/ and the S"4 supports all three signaling types. ,4$5@- supports only LSSL. 5t should #e noted that the nodes that support more than one signaling type may have restrictions if and how these can #e mi2ed. S"4 5- and CC/ support ,SSL and S5T-/ in C4:.
%
7--ered Charging Solution -or $E*C7 )
%.1
Dimensioning /igures The Charging System service is used in different ways for different mar%ets depending on the charging strategy of the operator. The traffic model aims at descri#ing the #ehavior of the Charging System su#scri#ers or technically the freuency$distri#ution of Charging System traffic cases. 5t is assumed that standard or average traffic model is used in the TELC ! /etwor% and dimension calculations are performed #ased on this assumption
%.1.1
Proposed N etwork " rchitecture
%.1.2
SDP
The S"4 holds the su#scri#er data (service class account value account life cycle data su#scri#er status and so on). *hen any charged activity is going to #e made in the networ% a dialogue to the S"4 is necessary. ost reuests from customer care and all user initiated reuests through 5@- or 7SS" is also processed #y the S"4. The S"4 load during pea% hour depends on many parameters and operator traffic account model. The impact on the Charging System from the traffic cases a#ove varies depending on the functions that are activated and the traffic mi2. The num#er of transactions that can #e processed #y the Charging System thus depends on the usage. The capacity of the S"4 at the C47 load regulation limit is given using the default traffic model. The standard S"4 includes two clustered Sun /etra T1000 servers.
Ericsson Standard S"4 (S7/ /etra T1000 C =$core <.1,6 <:+ 12<;:+) can supports appro2imately ;00 callAsec. (<;;0 F +,C ) !N" Standard SD# is o$$ered to %"LC! & %.1.%
.
CCN
CC/ is responsi#le for call control of circuit switched calls and data 4-S SS and content #ased services communications. The CC/ logic is a#le to handle CS
"I(
The 5- node(s) handles all refills and enuiries in the networ%. The following traffic cases and features affect the load in 5-' •
@oucher and value voucher refill from 5@-
•
Enuiry from 5@-
•
7SS" @oucher and @alue @oucher -efill
•
7SS" Enuiry
•
7C54 traffic
•
dustments
•
+atch files
•
7se of "edicated ccounts
•
ETS5 4 7SS" -efill
•
ETS5 4 7SS" Enuiry
Standard 5- or co$located with & runs single /etra T1000 <100,6 T< = cores with = + memory. "imensioning figures are' n average of <0 "Asu#scri#ers' <30 refillsAs with no other traffic or 310 enuiriesAs with no other traffic an average of D "Asu#scri#er' <30 refillsAs with no other traffic or 3D0 enuiriesAs with no other traffic *ith an average of 0 "Asu#scri#er' <30 refillsAs with no other traffic or ;00 enuiriesAs with no other traffic &rom a capacity point of view it does not matter is the refill or enuiry is e2ecuted via 5@- or 7SS" %wo standards A-RA/ Ser*er are o$$ered to %"LC! &+ two ser*er pro*ide redundancy. %.1.,
'S
The @oucher Server contains the voucher data#ase and handles all voucher refills in the networ%. ll voucher refills through customer care or 5@- in the networ% impacts the @oucher Server. The @S load per su#scri#er consists of the following traffic cases'
@oucher refills @alue voucher refills
Standalone @S node as a two T1000 servers cluster with redundant dis% arrays and ; C47s per server. Standard @S capacity is <:0 refillsAs /ote that this is the dimensioning limit for the dis% system. a2imum num#er of vouchers' $ 310 with 3D<0 "is% rray
!N" Colocated 1SA-R is o$$ered. %.1.
#INS"$
The following traffic cases and features affect the load on 5/ST'
Customer care activities via 75
-euests from e2ternally integrated applications via CC 45
"ata record processing for ccount ,istory and Call ,istory
+atch processing (installations su#scri#er data changes deletions)
A medium '-NSA% Con$iguration is o$$ered to %"LC! &.
%.1.0
Summary
ccording to dimensioning calculation following networ% elements are offered to TELC ! and this proect will include installation integration and testing of following networ% elements'
Node
S"4(cluster)
%.2
Numer
<
S8*evel
S"4;.;
58types
T1000
5/ST
<
5/STD.:
edium@;;0
CC/
1
CC/ D.<
/S4 D.0 idi
@S
<
@S 1.3
5-A&
1
5- 1.1
!L$5@-
<
@!L$5@-<.1
T1000 T1000 ,4C4
7--ered /eatures +elow ta#le lists the features availa #le on CS3.0 and which ones are offered for TELC !.
BasicFeatures
Wib lleUsed
Account Grouping
Yes
A/B -number White number list Account History
Yes Yes
BalanceDependentTariff
Yes
Balance Threshold Notification to !ternal "ystem
Yes
Batch #efill
Yes
$all History
Yes
$"%nline$ostand$redit$ontrol&$"'()
Yes
Dedicated Accounts
Yes
nhanced"ubscriber"egmentation
Yes
mu Adaptation nhanced*oucher"ecurity +amily and +riends ,ersonalied "er.ice %ffering ar0et "egmentation ulti user account
Yes Yes Yes Yes Yes
Number ,lan $hange ,eriodic"er.ice+eeDeduction
Yes
,re-Acti.atedAccounts
Yes
#ealtime1ifecycle#eporting
Yes
#echarge ,romotions
Yes
"creening
Yes
"nap "hot #eport Tool "tatisticsDataHistory&2N"AT) "ubscriberAdministrationAD
Yes Yes Yes
TariffanagementApplication
Yes
Toll-free Numbers
Yes
*alue *oucher *oucher Generation
Yes Yes
Optional Features Bonuson2ncoming$alls
8ill e sed Yes
$A1 ,h' $A1 ,h3
Yes
$D# processing
Yes
$ommunity $harging
Yes
Account Admin $ommunication 2ntegration ,rotoco
Yes
nhanced ser.ice fee deduction
Yes Yes
!ternalAlarmHandling G,#" #ealtime $harging based on $A1 ,h4
Yes
5ser$ommunication2ntegration,rotocol
Yes
*oice 61 2*#
Yes
obileNumber,ortability7AT2based
Yes
Negati.e Balance
Yes
%pen $harging 2nterface &Diameter)
Yes
"$ $harging i/f on $$N ,remium #efill
Yes Yes
#atingfor+le!ibleBearer$harging
Yes
"" #ealtime $harging based on $A1 ,h4
Yes
""#ealtime$hargingbasedon$"'( Tariff and Bonus &TBA5/BBA5)
Based
on
Yes Accumulated
5sage Yes
5""DBalance2n8uiry7Notification 9nsat$ustomer$areA,2
Yes Yes
"elf "er.ice $harging
Yes
5""D $allbac0
Yes
*N% "upport
Yes
5""D refill
Yes
"escriptions of offered feature can #e found in following ta#le'
/eature
Service Description $ype
SSD 9alance
5ncrease
*ith /otifications information on upcoming
In:uiry; Noti-ications < (e-ill
usage
and awarded #onuses can #e sent to a su#scri#er after a su#scri#er has performed a transaction. 5n this way you can increase the su#scri#er usage. 7SS" end of event notifications can #e tailored for different su#scri#er segments different services and individual su#scri#ers hence adding more user value as users only receive notifications that are relevant to them.
SSD Call 9ack
-oaming
*hen using 7SS" Call#ac% the Charging System su#scri#er dials a 7SS" service code followed #y the +$num#er for e2ample J<13J=<13;D:8K where J<13J is the service code for roaming calls.
6P(S (ealtime Charging
-oaming
Charging may #e #ased on #oth location (for roaming su#scri#ers) and the dialed destination. CEL 4h 3 supports uniue toll$free and Hallowed num#erI lists uniue announcements for roaming su#scri#ers #arring of roaming areas charging of forwarding and terminating leg.
S#S+#7 (ealtime Charging; C"P%
-oaming
SS$ -ealtime Charging #ased on CEL 4h 3 adds roaming capa#ilities to CS SS. Charging can #e #ased on SS$C ddress or Called 4arty /um#er. llowed and +arred Lists over SS$Cs prevent fraud. The feature wor%s in a multi vendor networ% #ut Ericsson SCA@Lsupport in the networ% is reuired.
#oile Numer Portaility
Loyalty
Ena#les operators to distinguish #etween on net and off net calls and allows su#scri#ers to maintain their S5S"/ when switching networ% operators
Negative 9alance
Loyalty
/egative +alance Ena#les su#scri#ers to #e allowed a credit on the account "e#t *arning announcement "efined per Service Class Configura#le race 4eriod +alance "ependent Tariff Ena#le the operator to apply different tariffs depending on the account #alance. The account #alance at call set$up determines the tariff for the whole call. Configura#le call set$up announcement
9onus on Incoming Calls
5ncrease 7sage
The feature is implemented as a negative tariff in the tariff tree allowing the system to credit the su#scri#er account every time a call has #een received.
Community Charging
Loyalty
CheaperAdifferent tariff within the same community *or%s for #oth pre$paid and post$paid su#scri#ers *or%s for all services (Circuit switched voice SS S 4-S) Special notification (#y means of 7SS" End$of$Call) when calling inside community 5ndependent of Service Class Support for Service &ee "eduction ,andles up to 9 million su#scri#ers per community ,andles up to <0 communities Selection of "edicated ccount depending on community ultiple Communities per account (up to 3) Tool to increase' customer loyalty and reduce churn increase on$net usage increase usage of content e.g. foot#all goal streaming service to mem#ers of a foot#all clu# community. 5mproved segmentation possi#ilities. Tool to reach low$spending su#scri#er segments e.g. students
7pen Charging Inter-ace ased on
Content
Diameter
any different types of content$#ased services can #e charged for for e2ample' oal services *eather services Tic%et reservations -ing$tone download Comic strips
ser Communication IP
System
The protocol can #e used for the following' ccumulator inuiry +alance inuiry (main and dedicated accounts) -efill Standard @oucher -efill @alue @oucher 5nuiry @alue @oucher -efill 4ositive dustment (ain ? dedicated accounts) including setting of supervision e2piry date and Service &ee e2piry date
"dmin Communication IP
System
#'N7
System
C54 is an open interface to Charging system for administrative functions. This interface can #e used for admin functionalities li%e create A modify su#scription so on.. o#ile @irtual /etwor% perator Support. Can have different system views and access for different Service 4roviders.
Premium (e-ill
5ncrease 7sage
llows the su#scri#er to simultaneously change the Service Class and refill the account. Service Class change can #e performed #y Customer Care through a premium refill through a value voucher refill or through 7C54
Enhanced Service /ee Deduction
5ncrease 7sage
&or a su#scri#er who has su#scription for push out message and family M friends discount operator can charge a monthly service fee for message and uarterly service fee new for family M friends. To ma%e service launch more attractive it is possi#le to suppress first service fee deduction. Su#scri#er pays a wee%ly fee to have access to o#ile T@ service first wee% fee is free of charge as promotion for the new service. n operator launches a summer campaign with discounted roaming rate. &or su#scri#ers who sign up for this campaign a service fee will #e deducted monthly within 3 months period say from >uly
#insat Customer Care "PI
System
The primary purpose of the 45 is to allow operators to integrate legacy customer care application systems with Charging System. 5t may also #e used #y #espo%e third party applications which need access to the functions made availa#le through the 45.
Sel- Service Charging
5ncrease 7sage
CS 7n+line cost and Credit Control Ericsson CS13! 9atch (e-ill
System
'oucher Security
System
System
Numer Plan Change System
perator has the possi#ility to charge a su#scri#er when he is performing self services li%e &amily and &riends administration su#scription change or #alance inuiry. Charge different rates for different actions. dditional 5@- call flow config will #e reuired. ain Charging System feature ena#les the operators to perform real$time charging with session supervision for all call cases. -efill su#scri#er accounts using a #atch file allows operator ma%e #ul% refill for the su#scri#ers for several reasons. @oucher security feature ma%e voucher activation codes encrypted. This allows the operator to %eep the voucher data in secure. /um#er 4lan Change offers an efficient way to change num#er series hence simplifying administration of S5S"/ num#er series. The #atch o#s can #e e2ecuted during low traffic periods without any distur#ances in the service. n operator decides to change the num#er series starting with DDD to starting with 1DDD
Pre+"ctivated "ccounts
System
Snap+Shot (eport
-eports
$ool
"49+numer 8hite *ist
Screening < $oll+ /ree Numers
The 4re$activated ccounts feature allows new su#scri#ers to activate their accounts without having to ma%e a specific Hactivate accountI call to the 5@-G the account is activated on the first session initiated #y the new su#scri#er. "epending on the operatorBs system configuration various su#scri#er accesses to a new account can trigger activation of the account' srcinating calls including toll free calls calls to the 5@- or 7SS" access. The Snap$Shot -eport Tool provides operators with an instant view of selected information in the account data#ase in the S"4. The feature is delivered with a num#er of predefined reports which simplifies generating of su#scri#er and account statistics. 5t is also possi#le to add customi6ed reports for specific purposes. The reports support #usiness related decisions and the report format ena#les the data to #e smoothly imported into e2ternal tools li%e spreadsheet applications. E2amples n administrator wants to chec% the total de#t among su#scri#ers who are allowed /egative +alance and chooses the predefined report for total negative #alance.
System
System
The +$/um#er *hite list contains the num#ers to ta2i$companies to allow su#scri#ers to call a ta2i also when technical pro#lems prevents access to the S"4. ne operator allows calls to fi2ed phones #ut not to mo#ile phones. ne operator uses the o#ile /um#er 4orta#ility support to allow on net calls #ut not off$net calls. The Screening M Toll$&ree /um#ers feature allows the operator to #ar specific num#ers or num#er series and to define num#ers availa#le free of charge in a controlled way. 5t is possi#le to use separate lists for su#scri#ers in different Service Classes that is to configure the call limitations differently for different target groups. E2amples The num#er series <1 is #arred in the #arring list. 5f <13 is defined in the allowing list all num#ers in the num#er series <1 are #arred e2cept for those in the num#er series <13.
$ari-- #anagement "pplication
System
The Tariff anagement pplication provides advanced rating capa#ilities and offers sophisticated mar%et segmentation possi#ilities as well as a secure tariff management. Tariff structures are edited and tested offline using a user$friendly 75. Tariffs are #uilt in a tree$structure with nodes #ranches and leaves. The nodes hold the conditions for determining which #ranch to follow. The #ranch is used when specific conditions apply for e2ample charging #ased on location where the #ase station 5" is used as a #ranching condition.
'oucher 6eneration
System
/amily and /riends
Loyalty
#arket Segmentation System
#ulti+ser "ccount
5ncrease 7sage
The @oucher eneration feature ena#les operators to employ a personali6ed and secure voucher administration system. 5t guarantees uniueness of the generated voucher data as serial num#ers and activation codes are uniue within the @oucher Server. @oucher administration is performed in a user$friendly 75. &amily and &riends (&a&) ena#les discount rates for favorite num#ers and num#er series defined for #oth srcinating and terminating calls and SS. &a& can #e used for #oth single and multi$user accounts. ulti$user accounts may contain #oth a general and individual &a& lists. These lists arethe chec%ed withon priority hence ensuring that num#ers the lists are rated correctly. The Service Class concept is an advanced mar%et segmentation tool a means to offer customi6ed customer agreements to different su#scri#er groups. The Service Class includes all availa#le parameters for a customer agreementG specifies included services life cycle properties tariff plan currency language etc. ttract families small enterprises and other types of small groups with ulti 7ser ccounts. -ating and deduction from the common account is performed in parallel. ll su#scri#ers has authority to refill the account and to perform inuiries towards the account #ut only one aster Su#scri#er has authority to add and remove su#$su#scri#ers. 5f the aster Su#scri#er is removed all su#$su#scri#ers are removed.
Dedicated "ccounts
5ncrease 7sage
"edicated ccounts are powerful tools in the promotion program as they ena#le operators to promote #oth su#scri#er$ #ehavior for e2ample refill and usage of specific services for e2ample 4-S S SS or content$#ased services li%e a news su#scription. Campaigns n operator wants to promote S usage during Christmas and offers <00 S for a #argain price. Su#scri#ers sign up for the Christmas Campaign #y refilling their accounts using a specific voucher with the value D0 plus a promotion of <0 percent. The result of the refill (value DD) is placed on a "edicated ccount for S with an e2piry date after the Christmas holidays (>anuary =). fter this date the "edicated ccount is deleted. Stimulate -efill and 7sage n operator uses -efill +ased 4romotions to promote refill among su#scri#ers in the Student Service Class and at the same time stimulate usage. n each refill Student su#scri#ers are granted a
(e-ill Promotions
(ealtime *i-ecycle (eporting
5ncrease 7sage
System
-efill 4romotions is #eneficial for #oth the su#scri#er and the operator. 5t is an important element in the operatorBs customer loyalty strategy. s -efill 4romotions can #e awarded in real time it is possi#le to immediately notify the su#scri#er a#out the reward hence increasing satisfaction. E2amples The following are e2amples of promotion plans for -efill 4romotions' 4romotion 4lan <' 30 refills of any value during one calendar year e2tend the service supervision period with one month. 5f the su#scri#er performs 90 refills of any value during the same year the su#scri#er is reallocated to 4romotion 4lan D. 4romotion 4lan D'
anuary awards the su#scri#er with e2tra <00 monetary units. 4romotion 4lan 3' -efills with an amount e2ceeding <00 monetary units on arch <8th year !!!! e2tends the service supervision e2piry date with two months the Service &ee 4eriod with 10O and an e2tra 10O of the refill value is added to the account. 4romotion 4lan ;' -efill the account at least
Service /ee Deduction
'alue 'oucher
5ncrease 7sage
5ncrease 7sage
Service fees are instruments to help operators to fast launch new services with secured charging. Service fees can #e used as a segmentation tool for pac%ages with different services and tariffs. The automatic deduction is networ% efficient as it can #e made during low traffic periods. 5f the account #alance does not cover the service fee the su#scri#er can immediately #e #arred from either the premium service or all services. The interval #etween the deductions is configura#le #y the operator and hence it can #e tailored to #est fit each offered service. E2amples o#ile Terminating SS is a typical way to use service fees' Su#scri#ers receives for e2ample daily stoc% e2change information soccer results etc. The operator charges a service fee in advance and the fee is deducted from the su#scri#erBs account for e2ample each month. su#scri#er has access to a service with ring tones for download. 7p to five downloads are free every wee% and the user pays a service fee to use this service. The service fee is deducted from the account in advance every month. high volume su#scri#er is connected to a service which give the su#scri#er lower tariffs at daytime wee%days. The service fee is deducted from the account in advance every wee%. n operator uses the /egative +alance feature. ccounts allowing negative #alance are charged with a monthly service fee. The @alue @oucher feature provides a user$ friendly way of changing the content of the su#scription for e2ample get access to supplementary services or lower tariffs. @alue @oucher lowers load on Customer Care as su#scri#ers are a#le to change their su#scriptions #y a simple self$ provision action using the 5@- or a 7SS" service. @alueand @ouchers the same way throughare thedistri#uted same channels as any other voucher. E2amples Su#scri#er #uys a @alue @oucher to get a lower roaming tariff effective during his two wee% vacation a#road. This @alue @oucher performs a temporary Service Class changeG after the predefined period the su#scri#er returns to the permanent Service Class.
Su#scri#er + #uys a @alue @oucher to get access to an SS oal Service offered #y the operator during the Soccer *orld Championship. This @alue @oucher performs a temporary Service Class change to a premium Service Class. fter the championship the su#scri#er returns to the permanent Service Class. Su#scri#er C #uys a @alue @oucher to permanently switch to a Service Class allowing /egative +alance on the account.
9alance Dependent $ari--s
5ncrease 7sage
+alance "ependent Tariffs ena#les the operator do define multiple tariffs #ased on multiple account #alance levels including negative #alance.+alance "ependent Tariffs increases the rating fle2i#ility. The feature can #e used to stimulate refill through a lower rate at high account #alance and a higher rate at negative account #alance. E2ample The tariff is higher when there is #alance is negative on the account and lower when the account #alance is more than P30.
9alance $hreshold Noti-ication to E=ternal System
System
+alance notifications at specified thresholds ena#le e2tended user communication and services. "epending on implementation this feature can for e2ample #e used to trigger an automatic refill to send a #alance notification over SS to the su#scri#er or to #loc% e2ternal services. 5n 4-S environments a Hlow #alanceI notification can prevent a download to #e started and then to #e cut off due to an empty account. The thresholds used in +alance Threshold /otification to E2ternal System are fully configura#le #y the operator. E2amples n operator has implemented a #an% interface and uses a low #alance threshold to trigger an automatic refill for customer segments which uses this function. nother operator uses the feature to send low #alance notifications over SS to su#scri#ers. third operator uses +alance Threshold /otification to notify e2ternal service providers when an account runs low to ena#le the partner to #ar the su#scription until the user refills the account.
"ccount 6rouping
Personali>ed Service 7--ering
System
5ncrease 7sage
ccount rouping ena#les selected su#scri#ers from a single Service Class or from several Service Classes to #e grouped together in an ccount roup. rouping can #e #ased on for e2ample department in a company. The account group id is written to "-s which ena#les a post$processing system to filter out the specific account group for reporting purposes or to create hierarchic account structures. E2amples n operator uses ccount rouping to segment their enterprise customers. The employees at the enterprises #elong to different Service Classes #ut the operator wants to #e a#le to report on department level. The parameters are written to the "- which is sent to the post$processing system. 5t is now possi#le for the operator to generate reports on department level in the company. The 4ersonali6ed Service fferings feature enhances the already powerful Service Class concept and ena#les even more fle2i#le mar%et segmentation. The srcinal Service Class concept held all service and su#scri#er related parameters in the Service Class. This has #een an advanced method to group services and tie the services to su#scri#ers in a fle2i#le way. The increased possi#ilities to offer new value adding services to the su#scri#ers has however led to a continuously increasing num#er of Service Classes to cover various com#ination of services. The feature also improves rating and 7SS" message fle2i#ility as rating and type of 7SS" message can #e differentiated for different su#scri#ers. /ew campaigns can #e implemented faster and easier as the su#scri#er parameter can #e used to find for e2ample su#scri#ers from any Service Class who has activated S services. 5t is also easier to handle several offerings and campaigns at the same time which increases the segmentation possi#ilities. The parameter can #e used to identify post$ paid and prepaid su#scri#ers in the same Service Class
%.%
Services
%.%.1
"irtime $rans-er
The irtime Transfer Service will #e implemented during launch
•
Charging System 3 will only #e responsi#le for validating and updating su#scri#erBs account. Every other function remains the responsi#ility of TELC !
•
TELC ! needs to develop an e2ternal application using 7C54 interface to interface with the 5- server. "etails of 7C54 can #e found in LE! documentation. -eference' irBs programmer guide$ 7C54 .
%.%.2
S"CC Service "ware Charging Control! %.?
SCC 3.0 will #e configured in a num#er of ways depending on TELC ! needs and legacy reuirements. Con-igurations
S/ -; handles the inspection and classification of the data flows passing the 4-S networ%. The S/ -; is the enforcement point of the policies applied for #oth charging and access control. S/ -; 5mplements the 4olicy and Charging Enforcement &unction (4CE&) nline ediation D handles charging mediation in real time towards an e2ternal charging system (5t also offers rating functionality as well as active #alance management in order to complement the functionality offered #y the e2ternal online charging system.) Charging system will #e used for policy rating and charging N7$E@ *hen Ericsson Charging System ;.0 #ecomes availa#le it will support
the Ericsson y? interface and hence it will #e possi#le to connect without using the online mediation component of Ericsson ulti ediation D.
&igure <
SCC 3.0 "iagram
%.&
9usiness Processes
%.&.1
SuscrierP rovisioning
This chapter descri#es the su#scri#er provisioning process to follow in CS3.0 solution. 5n Ericsson CS30 solution if there is more than one S"4 on the networ% pre$ provisioning of the & should #e performed. The function of & is to map S5S"/ to S"4 for 54 #ased traffic li%e refill and #alance inuiry in CS3.0. The whole provisioning process is initiated from 5/ST node. See #elow the description of the flow. <. Create +atch provisioning files. +atch provisioning files can #e produced on 5/ST as follows' a. enerate & #atch provisioning file (only applica#le when more than one S"4 is in place). This can #e done using the 75 screen or the command line. &rom this point onwards the su#scri#ers are assigned to an S"4. The following parameters are passed' utput file name Start S5S"/ of range -ange (/um#er of su#scriptions) End S5S"/ • • • •
•
S"4 5" #. enerate Su#scri#er #atch provisioning file.
This can #e done from the 75 screen or the command line. The following parameters are passed' utput file name /um#er of master records Start 5S5 Start S5 • • • • • • • • • • •
Start S5S"/ +usiness 4lan Language +loc% Status 4romotion 4lan data (optional) S"4 ther optional fields
&ind #elow su#scri#er provisioning file format specification' /ield
Instruction
S5S"/ num#er aster num#er 5S5num#er S5num#er
/o more than 1= digits. /o more than 1= digits. ptional. /omorethan1=digits. /omorethan1=digits.
47F< 47F1 4lan5" S"4 Language 4romotion 4lan 4romotion Start "ate
/omorethan1=digits.ptional. /omorethan1=digits.ptional. /omorethan;characters. /omorethan;characters.ptional. /o more than < digit. (0$D). ptional. /o more than ; characters. ptional. /o more than = digits. QQQQ"". ptional. /o more than = digits. QQQQ"". ptional. SET R CLE-.
4romotion End "ate Temporary +loc%ing Status Community roup 5" Service ffering 4lan 5" ccount roup 5" 7SS" EC/ Code rganisation 5"
/o more than ; characters. ptional. /o more than ; characters. ptional. /o more than <0 digits. ptional. /o m ore t han 1 di gits. @ alid v alues < $99. ptional /o more than <0 digits. ptional.
c. 4rovision on &(only applica#le when mor e than one S"4 is in place) The #atch previously generated is processed either using the 75 screen or the command line interface. The su#scri#ers are installed in the & node. d. 4rovisioning of su#s cri#ers The #atch previously generated is processed either using the 75 screen or the command line interface. The su#scri#ers are loaded in the insat ,Land S"4. Note@ Since TELC ! will use lcatel ,L- in the /etwor% E (Ericsson
ulti ctivation) needs to #e used in complete 7ser 4rovisioning solution. E has an interface to lcatel ,L- So that through E it is possi#le to send provisioning command to the ,L- from 5/ST. *hen E is in place the su#scri#ers will #e loaded on the ,L- via E using the 5/STS@ command. lso #arring of su#scri#ers on the ,L- for outgoing and incoming calls will #e initiated #y the S"4 towards the ,L- via E according to the changes in the lifecycle. lternatively a Customer dmin System (CS)Care needs #e developed address all provisioning needs. pen Customer 45to(CC$45) can #e to used in CS system development. anual installation of individual su#scri#ers can #e performed via 5/ST. 5n this case there is no #atch processing. The data is filled in on the 5/ST 75 screen and e2ecuted directly. ,owever if used the & should have #een previously provisioned.
&igure 1 5nterfaces for provisioning without E and &
&igure 3 5nterfaces for provisioning with E and &
%.&.2
Postpaid to Prepaid process and visa versa
&igure ;
4ostpaid to prepaid flow.
&igure D
%.&.%
4repaid to postpaid migration flow
/orced Disconnection
The following shows the forced disconnections at TELC ! and the figure #elow illustrates the flow for forced disconnections for su#scri#ers in CS 3.0.
5n addition to this flow ,L- profiles should also #e changed. Start
LifeCycle"isconnection
Type of "isconnection
4reto4ostConversion
5f Su#scri#er is e2pired and mar%ed for "isconnection 5/ST will delete S5S"/ from 5/ST and S"4 through m#d #atch process
5n this case TELC ! will have to prepare a file and put it in the specified directory for which they want to delete in 5/ST.
S" utility will process the prepared file.
S" process will delete the S5S"/ from 5/ST and S"4.
-esponse file will #e generated with the filename with a sign.
End
%.&.&
'oucher Provisioning
This chapter descri#es the voucher provisioning process to follow in CS3.0 solution. 5n CS3.0 offers generation and loading of new vouchers using #atch files@oucher from @SServer 75. The process will #e' <. @ouchers +atch file generation 1. @ouchers +atch file loading in H7navaila#leI status 3. Send file to manufacturer
;. Change vouchers status to Hvaila#leI once the physical vouchers are ready to sell. nly impact in provisioning process is the format of the #atch file generated if @S is used for such generation. @oucher manufacturer should #e a#le to e2tract reuired information from new file format. ll relevant fields reuired to create the voucher are included in CS3.0 file format' group$id S/ 45/ value E2piration date currency and language. /ot included fields' peration creation date #onus validity e2tension. See 4rotocol essage Specification $ @oucher +atch &ile in C45 li#rary for further information on new format. +onus and validity e2tension is not included in the voucher #ut is part of the system configuration on 5-. +oth values will #e decided upon usage depending on 5- configuration. 45/ code #ecomes encrypted when loading the vouchers into @S data#ase #ut in CS30 @S +lowfish encryption algorithm will #e used. 5n case there is need to access the 45/ code (for instance if a voucher gets damaged and the complete 45/ code cannot #e read) 45/ code is still availa#le in voucher generation files in @S. %.&.,
'oucher creation; loading and status change CS %.? Proposed Process
<. @oucher dministrator uses the @oucher Server we#$interface secured via username and 45/ allowing access to @oucher 4in generation feature on the @oucher Server. 1. The @oucher eneration feature on the @oucher Server generates a "T file with a full <; digit random 45/. 3. The "T file is "ES encrypted. ;. The "ES encrypted file is stored on the @oucher Server file system for loading #y a @oucher Server perator whom can load the file on the Ericsson @oucher Server. D. The @oucher Server perator loads the file onto the Ericsson @oucher Server. :. nce the "T file is loaded the system generates a L"E" file which is still "ES encrypted and a -4T file showing the status of the @ouchers i.e. Success or &ailure of the vouchers reuested to have #een loaded. 8. The "ES encrypted L"E" files is 44 encrypted for safe transportation. =. The 44 encrypted L"E" file which is still "ES encrypted is securely emailed or transported to the distri#utor or @oucher printer.
9. The trusted distri#utor and @oucher printer are a#le to decrypt 44 using the pu#lic %ey the L"E" fileG which still reuires the "ES %ey for decryption of the actual data. 4lease see the diagram #elow.
%.&.
'oucher *oading The file with created vouchers is stored in the varAoptAvsAftpA#atchfilesAvoucher directory in the @S. 7ploading of @ouchers into @oucher Server system is 75 #ased. 7sing the @S front$end application voucher files can #e uploaded with a +atch 5". The #atch 5" will #e used as a uniue identifier of each individual file. -esponse file will #e generated and has the status of each #atch file process.
Start
@oucher will #e generated outside of EAAA @S system
+y using the front$ end 75 the voucher #atch file . will #e uploaded and a response file will generated.
End
3.;.:.<
@oucher +atch 5nput &ile The @oucher +atch 5nput file contains two parts $ a header part for data that is common to all voucher entries and a contents part where voucher entries are specified.
,eader 4art
Element
$ype
#andatory
total_number_of_vouchers /umeric
activation_code_length
/umeric
currency
lphanumeric
-ecord 4art
Element
$ype
activation_code /umeric
#andatory
serial_number
lphanumeric
value
/umeric
voucher_group
lphanumeric
expiry_date
"ate
agent
lphanumeric
extension_text_1 String
extension_text_2 String
extension_text_3 String
3.;.:.1
@oucher +atch -eport &ile The @oucher +atch -eport &ile reports the outcome of the voucher #atch file after attempting to load the vouchers. 5t consists of a content part detailing the voucher for which loading was unsuccessful and a trailer record for the overall result of the load.
-eport 4art This record can either e2ist for the entire file if the file failed to #e validated due to format errors or per reected records if the file format is accepta#le #ut e2ecution for individual records causes errors.
Element
$ype
#andatory
error_code
/umeric
serial_number lphanumeric
Trailer 4art
Element
$ype
processed_records /umeric batch_status
lphanumeric
batch_error_code /umeric
#andatory
%.&.0
'oucher State change
3.;.8.<
CS3 @oucher State and Lifecycle
user can initiate a state change o# in the @oucher Server. This o# will change all vouchers in either a serial num#er range or a #atch to a specified state. voucher state change report file contains the result of a state change o#. voucher state change report file must always consist of one header and one trailer record. &or every voucher that the state was not changed in the selection there will #e one voucher state change record. @oucher state change report files are named as follows' STTEC,/EUQQQQ""ThhmmssUS.-4T where QQQQ""Thhmmss corresponds to the date and time the file was generated and S is a seuence num#er to ma%e sure that two files do not have the same name. 5f there will #e more than <0 state change o#s during one second there will #e two digits of seuence num#er. &igure #elow illustrates possi#le state transitions for a voucher.
%.&.A
Suscrier *i-eCycle
This chapter descri#es the su#scri#er lifecycle that is used in CS3.0.
The Lifecycle service scenarios of a Charging System account depends on the settings for the following account data' ccount @alue Service &ee 4eriod Service -emoval 4eriod Supervision 4eriod Credit Clearance 4eriod See #elow the description of the periods that can #e configured related to the Su#scri#er Lifecycle' •
Service &ee 4eriod The Serv ice &ee period is the time period for which a service is granted to the su#scri#er. *hen the service fee period e2pires all traffic services are #loc%ed even if there is credit left on the account. The service fee period is set at account activation and can #e com#ined with an account refill #ut it can also #e handled separately. The service fee can also #e deducted in advance automatically prolonging the service fee period. *hen the service fee period has e2pired the service state of the account can #e changed. riginating or terminating services or #oth can also #e #arred in the ,L-.
•
Service -emoval 4eriod *hen the Service &ee 4eriod e2pires the account is set for Service -emoval. 5f no service fee is placed within this grace period the account will #e removed from the operator networ%. 5f a new service fee refill is made while the account is set for service removal it will automatically #e reactivated.
•
Supervision 4eriod The supervision period is the time period during which a service is availa#le to the su#scri#er #efore a refill has to #e made. The Supervision period is restarted at each refill. *hen the superv ision period has e2pir ed the servi ce state of the account can #e changed. riginating or terminating services or #oth can also #e #arred in the ,L-.
•
Credit Clearance 4eriod *hen the supervision period has e2pired the account is set for credit clearance. *hen the credit clearance period has e2pired the account #alance will if positive #e set to 6ero. ,owever de#ts will not #e cleared. 5f a refill is made while the account is in credit clearance the account will automatically #e re$activated.
&ind #elow diagram descri#ing lifecycle for CS3.0 su#scriptions in TELC !'
Ericsson CS3.0 solution handles D states for su#scri#ers lifecycle'
•
Installed' the su#scri#er is crea ted on the syste mG the accou nt is pre$
activated and can ma%e or receive voice call and SS. The account will #e activated and Supervision 4eriod and Service &ee 4eriod get an initial value upon any of the following events' &irst srcinating 5/ Service event triggered' srcinating voice call
SS or S. ccount -efill or Standard @oucher refill through 5@- 7SS" +atch or Customer Care. &irst call to the 5@- menu &irst 7SS" enuiry ccount adustment from Customer care with e2piry dates update $emporary 9locked@ n account can #e temporary #loc%ed #y the system or #y Customer Care. This implies that the account is temporarily #arred and cannot #e accessed #y the su#scri#er. /o incoming or outgoing services are possi#le. -efill of the account is not possi#le. This status can #e reached after the -emoval 4eriod is ended or #y manual operation from 5/ST. "ctive@ su#scri#er is a#le to access any availa#le service (outgoing or incoming voice calls and SS data servicesetc..). The only limitation for access to any service is the credit availa#le in the account. Passive@ Su#scri#er is a#le to access not charged services' incoming
•
•
•
•
is free not a#le to access charged(this services' srcinating calls SS or S S. #ut nly services are availa#le includes 5@- for refill). Su#scription changes to this state when Supervision 4eriod ends. fter Credit Clearance 4eriod ends the account is cleared. No Service@ Su#scri#er is not a#le to receive calls SS or S neither is a#le to srcinate calls SS or S. nly free services are availa#le (including 5@- for refill). Su#scri#er comes into this status after the Service &ee 4eriod e2pires. fter the -emoval 4eriod e2pires su#scri#er is automatically deleted from CS3.0 solution.
/TE' for any of the previous statuses it is possi#le that the account #alance is in the minimum limit. 5f this is the case access to any charged service is denied.
%.,
"ccount Structures in Charging system Charging System account can have one or several su#scri#ers associated to it. su#scri#er is someone who uses Charging System accounts to pay for services. The su#scri#er canuser #e either ownerSee of an account the master su#scri#er or a su#ordinate of the the account. &igure #elow. The identity of the su#scri#er in Charging System is the national (significant) mo#ile num#er which is derived from the S5S"/ num#er.
5t is the master su#scri#er who controls which su#ordinate su#scri#ers are allowed to use the account. 4rocedures for authentication of the master su#scri#er at the customer care center have to #e esta#lished #y the networ% operator. su#ordinate su#scri#er is allowed to use the monetary value of the account to its full e2tent together with other su#ordinate su#scri#ers and the master su#scri#er. ll su#scri#ers connected to an account are allowed to refill the account. The procedure for provisioning and disconnection of a su#scri#er is descri#ed in verall uide Su#scri#er 4rovisioning in C45.
n account consists of a master account and optionally one or more su#ordinated accounts. #aster "ccount
ll accounts have a master account this is where the su#scri#ers account #alance is stored. The master account #alance on a Charging System account corresponds to a monetary value. Dedicated "ccounts
The dedicated accounts are activated in Service Class data for all accounts in that Service Class and initiatedAcreated #y refill or adustment. "edicated accounts are associated with a master account. master su#scri#er can have up to <0 different dedicated accounts for different types of activities for e2ample one for voice calls SS or 4-S. configura#le list will decide which dedica ted account to use if there are multipl e dedicated accounts. The main account state must #e in active service in order to #e a#le to access the value of the dedicated account. 5f for e2ample a dedicated account e2ists for SS and monetary units are allocated to it Charging System will primarily use this dedicated account when charging for SS. *hen a dedicated account has #een emptied there are two possi#le ways to handle charging' • •
The main account is used for the remainder of the charged event. The service is interrupted
The #ehavior in this case is configura#le in the Service Class. Each dedicated account can either have an e2piry date or #e set in state active until further notice. 5f an e2piry date is defined for a dedicated account the account is only accessi#le if the session #egins #efore this e2piry date. general setting (service options) defines how e2piry dates are interpreted in the data#ase. 5t can #e set to allow usage of a service on the e2piry date (the service e2pires the day after) or it can #e set to indicate the day when the service e2pire. *hen e2piry dates are account used andthe when e2ample is activated towards the dedicated newfor e2piry date ais promotion verified against the already stored one. The e2piry date with the latest date will #e used. 5t is possi#le to configure whether the "edicated ccount shall #e cleared at e2piry date or not. 5n case clearing is not done the amount present at e2piry date will #e availa#le in case a new e2piry date is set. The cleared amount is reported in a "ata -ecord ("-). sage "ccumulators
The usage accumulators are used for the function +onus +ased on ccumulated 7sage. The operator has the possi#ility to define five (D) usage accumulators for different activity types per su#scri#er account. usage accumulator consists of a counter and a time stamp indicating when the usage accumulator will ne2t #e reset to the initial value. The time #etween resets is defined in the Service Class data. 5t is possi#le to #oth increase and decrease usage accumulators. The usage accumulator is also used for the function Tariffs +ased on ccumulated 7sage. %.,.1
"ccount (e-ill
refill to a Charging System account can #e done through ccount -efill through Customer Care through a +atch through Standard @oucher -efill or @alue @oucher -efill as illustrated in #elow'
5@-
7SS"
ccount -efill
CustomerCare CC$ 45 insat
in
7C54
2
2
2
Standard @oucher -efill
2
!
!
2
2
@alue @oucher -efill
2
!
!
2
2
The vouc her is considered as cash and the value lies with the hidden information. ll voucher information is stored on the @S. refill with a @alue @oucher will initiate a Service Class change. refill with a Standard voucher will add monetary units to an account and e2tend the service fee$ and supervision periods.
%.
End+ser communication This chapter descri#es the different methods for communication to the end user in CS3.0 solution.
%..1
"ccount (e-ill I'(
5@- refill function will #e availa#le in CS3.0 #y dialing the 5@- num#er and indicating the 45/ code for a voucher. SSD
7SS" refill will #e availa#le in CS3.0 #y sending 7SS" string li%e' J<1
Certain CC perators will #e a#le to perform manual refills when reuired depending on 5/ST assigned profiles.
%..2
9alance I n:uiry4Noti-ication
Su#scri#ers can o#tain information a#out #alance #y using following paths' I'(
Call to 5@- for #alance inuiry will #e availa#le in CS3.0 solution.
SSD
7SS" inuiry will #e availa#le in CS3.0 solution #y sending +alance 5nuiry 7SS" string li%e' J<13K. Call to Customer Care
7pon su#scr i#er reuest CC perators can use 5/ST 75 to o#tain su#scri#ers information and notify to su#scri#ers.
%..%
Charging S ystem i nitiated v oice a nnouncements
Some voice communication announcements in Ericsson Charging System Solution are initiated #y the system itself #y S"4 node. ll used voice announcements must #e stored #y TELC ! in the announcement machine in the SC. &ind #elow description of announcements that will #e availa#le. 3.:.3.<
Call Set$up nnouncements Call set$up announcements are the announcements played #efore the call is set up towards the called party. The different %inds of call set$up announcements are as follows' •
*elcome nnouncements' These announcements su#scri#er to Charging System and are played once.
welcome
a
•
•
•
5nformation nnouncements' These announcements inform the su#scri#er a#out the account #alance. Special announcements such as advertisements can also #e played. *arning nnouncements' The su#scri#er has the possi#ility to #e warned in case the account or e2piry dates are a#out to reach a limit that will result in call cut$off or another restriction in using the account. 5t is possi#le to play warning ann oun cem ent s as a one t . +arring 5nformation nnouncements in case a su#scri#er is #arred ng t he su bsc r i pt i on at al l , from either reaching a specific num#er or usi i ti s p ossi bl e t o pl ayan announce ment t o i nf or m t he su bscr i ber about t hi s .
3.:.3.1
5n$Call nnouncement Charging System has one in$call announcement $ a warning to the su#scri#er when approaching the account limit after which the call will #e cut off. The time #etween the warning and the depletion of the account is configura#le in one$second steps #etween the minimum of one second and a ma2imum of :0 seconds. The in$call announcement is played to the Charging System su#scri#er. "uring the announcement the other party is put on hold and the call is still charged. Therefore the announcement will not last long and it is normally reali6ed as a tone. The 5n$Call nnouncement will #e played for TELC ! configura#le HsecondsI #efore call disconnection for ,4L/ calls.
3.:.3.3
End$of$Call nnouncement Charging System has one end$of$call announcement $ the call cut$off announcement which is played immediately #efore disconnec tion of a call. 5t is used to inform the su#scri#er that there is either not enough money on the account for the call to continue or that the su#scri#erBs credit limit has #een reached. The call cut$off announcem ent is played to the su#scri#er that has run out of funds. "uring the call cut$off announcement the other party is disconnected. fter the announcement has #een played the remaining call party is immediately disconnected. /ote' 5f C4v1 is used no cut$off announcement will #e played.
3.:.3.;
andatory announcements &ind #elow list of mandatory announcements that will #e configured in Ericsson Charging System solution for TELC !. These announcements should #e recorded in SC.
C ode
Announcement
WhenPlayed
6050,
Barred due to no
Call does not have Active
`You are barred because
6150
Active Service
6055, 6155
you have no Active Service.' `You are barred because you have !o Service.'
6060, 6160
Barred due to no service !o Active and no "assive Service# $%erator barring o& service
Service needed. though it is Call does not have "assive service though it is needed.
6065, 6165
Account too lo &or call
`Your service is barred. "lease contact the service %rovider.' `Your account is too lo &or the call.'
60+0, 61+0 60+5, 61+5
estination nu*ber in barring list arning o& cut/o&& tone
Active service or %assive service or both disabled &lag set. (oney ta)en &ro* account is not enough &or a 1 second call -he called nu*ber is on the barring list A con&igurable ti*e be&ore the call ill be cut o&& hen account is
600, 610
-er*inating callSubscriber not reachable
`-he destination you are trying to call is not reachable'
605, 615
Announce*ent call cut/o&&
e*%ty active or %assive hen service is not got though needed at ter*inating call hen the called %arty is disconnected due to that account is e*%ty
is
at
UsedPhrase
`You are not alloed to call this nu*ber.' -one arning o& call cut/ o&&#
`-he call ill be disconnected due to lac) o& *oney.'
nnouncement code num#ers from :
%.0
Charging Charging analysis is performed using a rating structure. The rating structure has the form of a selection tree and usually consists of several conditions resulting in tariffs with rates and possi#le additional fees. See e2ample #elow'
%.0.1
Charged Services
Charging for services descri#ed in this chapter will #e performed in real time. 5f a service or event for some reason cannot #e charged using online charging Charging System has the possi#ility to charge the su#scri#ersB accounts offline #y collecting and post$processing C"-s. &ind #elow additional information regarding each one of these services' $ utgoing voice calls are charged in ,4L/ using CS
%.A
CustomerCare Customer Care personnel will receive complains or reuests from customers and will #e a#le to chec% account status account history and call history. perations that will #e performed #y CC from 5/ST' ccount Status uery ccount ,istory uery Call ,istory uery 4ersonal details uery' /ame address Social securityX • • • •
perations that will #e performed #y perations people upon CC reuest from 5/ST'
• • • • • • •
S5 Swap +alance enuiry anual dustments ccount Status uery ccount ,istory uery Call ,istory uery 4ersonal details administration' /ame address Social security num#erX
• • • • •
Service changes (Service Class language..) &a& administration -emove 5@- #arring @oucher 5nuiryA-efill Su#scri#er -e$activation
perations performed #y perations people upon CC reuest from ,Lcommand line interface' •
,L- services activation$deactivation' utgoing$5ncoming voice calls SS 5nternational calls call diversion call line identification etc.
ll descri#ed operations performed with current system #y CC people and #y perations people will #e availa#le in CS30 system through 5/ST. eneral enu screen can #e found #elow'
/TE' ccess to different functions in 5/ST can #e controlled through different access profiles depending on the user role. &or instance' CC operator CC supervisor etc. So that part of the operations currently performed #y perations people could also #e performed #y CC people. which could speed up process to handle complains and reuests from su#scri#ers.
%.B
(eports A number of st at i st i csand r epor t s c an be gener at ed f r om t he dat a ava i l abl e i n Char gi ng Syst em. The st at i st i csf ocu s on st at i st i ca l co unt er s,wher eas t he r epor t s f ocu s on busi ness-ndasu bscr i ber r el at ed i nf or mat i on. For a det ai l ed ov er vi ew of t he st at i st i csand r epor t s gener at ed i n Char gi ng Syst em, r ef er t o t he Over al l Gui de St at i st i csan d Gen er at i on i n CPI , Ref er enc e alsowhi ch
includes references to the respective networ% element 7serBs uides where information a#out administration of statistics and reports generation can #e found.
enerally following Statistics and reports can #e created for Charging System 3.0. • •
Service "ata 4oint (S"4) Statistics and -eports Charging Control /ode (CC/) Statistics and -eports
• • •
• • • •
%.1?
ccount 5nformation and -efill (5-) Statistics @oucher Server (@S) Statistics and -eports o#ile 5ntelligent /etwor% Su#scri#er dministration Tool (5/ST) Statistics and -eports 5ntelligent /etwor%$5nteraction @oice -esponse (5/$5@-) Statistics 5/ Service Statistics and Call -eports ,ewlett 4ac%ard (,4)$5@- Statistics @oice E2tensi#le ar%up Language 5@- (@!L 5@-) Statistics and -eports
D( and CD( generation 5n Ericsson CS3.0 solution it is possi#le to generate "etail -ecords in SCASS& CC/ 5- system and the S"4 depending on the traffic cases and operatorBs choice of configuration. 5n addition to the more traditional call and account adustment related "etail -ecords Charging System also provides "etail -ecord types that report a certain account event for e2ample' ccount created Connected to or removed from a multi$user account S5S"/ change Lifecycle change /egative #alance #arred @alue voucher e2piry and @oucher error. 5n standard Ericsson Charging Solution C"-s are routed to E (Ericsson ultiediation)system which5/ST will doin order properto provide formatting and re$sending to administrative call history for su#scri#ers as well as the other post$processing system li%e #illing systems "ata*are ,ouse Systems etc.
C"-s will #e generated from following different nodes in the CS 3.0 solution'
The following "- types can #e generated on CC/'
•
CCN CD( s contains the standard call data togeth er with charging
information (ccount #alance #efore and after etc) for @oice SS &a2 "ata records with -NSer*iceData"*ent'odule •
is also #eing used for real$time charging of riginating SS when roaming via the C4 v3 interface. Therefore the only C"-s generated will #e of type SC/S'SCS'!Record
"-s should #e routed to E (Ericsson ulti ediation) which will do proper formatting and re$sending to administrative system 5/ST in order to provide account history for su#scri#ers. "-s will #e generated from following different nodes in the CS3.0 solution' The following C"- and "- types can #e generated on S"4' C"-4rocessed This record contains data for a post processed session. ccountdustment This record contains data for a #alance adustment transaction. /egative+alance This record contains data a#out when a negative #alance has occurred. +onusdustment This record contains data for an #onus transaction. Service&ee"eduction This record contains data a#out a service fee deduction. LifeCycleChange This record contains data a#out the life cycle handling.
/egative+alance+arred This record contains data a#out an account that has #een #arred due to negative #alance. @alue@oucherE2piry This record contains account data a#out the status when a value voucher e2pires. The following "- types can #e generated on 5-' dustment-ecord This record contains "- data for a #alance adustment transaction. 4romotion-ecord This record contains "- data for an offline promotion transaction. -efill-ecord This record contains "- data for refill and voucher refill transactions. @alue@oucher-ecord This record contains "- data for a service class change transaction that is initiated #y a value voucher refill. Error-ecord This record contains "- data for an unsuccessful transaction. ,ot #illing will #e availa#le through C"- processing feature. 5t will #e used in case any service cannot #e charged in real time or for C"- post$processing in case on networ% failure. &or such functionality C"-s will #e sent from E to S"4 which will perform the proper charge to the su#scri#erBs accounts. &urther information regarding C"-s format can #e found in C45 li#rary documentation for CS3.0' !*erall 2uide CDR Con$iguration+ Detailed Record #arameter List+ Data Record !utput SD#+ Detailed Record #arameter List+ Charging System CCN CDR+ Detailed Record #arameter List+ Data Record !utput A-R+ Detailed Record #arameter List+ CCNCDR
/TE' additional C"-s can #e generated in CC/ S/ and C in when data services are activated.
%.11
(oaming TELC ! will use following roaming ena#lers in order to provide roaming services to su#scri#ers' o o
Camel ph 1 for voice calls Camel ph 3 for riginating SS
/TE' 7SS" C+ feature will #e used for roaming in the @4L/ which Camel is not supported.
%.12
7<# Procedures ain operation procedures are related to su#scri#ers and voucher provisioning and have #een descri#ed in previous chapters. "aily wee%ly and monthly maintenance routines and peration procedures are defined in !*erall 2uide Charging System Administration in C45 li#rary for CS3.0 solution. &ollowing user interfaces can #e used as part of the standa rd Ericsson Charging System 3.0 implementation'
SDP ser Inter-ace
ll S"4 administration such as tariff handling service class administration and software administration is performed through a >ava$#ased 75. See S"4 sers 2uide Ser*ice Class Administration and SD# sers 2uide Selection %ree Administration in C45 li#rary for detailed information.
"D#IN ser Inter-ace
Su#scri#er administration in the dministration Systems is performed through #rowser$#ased ,TLA>ava$script 75s. See '-NSA% sers 2uide 4atch and Ser*ice Administration in C45 for detailed information. CCN ser Inter-aces
CC/ anager ,ow to create and maintain the configuration of a CC/ using the CC/ anager raphical 7ser 5nterfac e (75) is descri#ed in the CCN 'anager ser 2uide in C45 li#rary. 5t also descri#es how to view configuration data for a particular service in the system. /ode anagement Tool#o2 &or the operation and maintenance of the TS4 platform the /ode anagement Tool#o2 is also used. The >!plorer L"4 #rowser is the 75 for managing the CC/ service and its features. The #rowser is started from the M Tool#o2 which is delivered with the TS4. The >!plorer L"4 #rowser provides a hierarchical tree structure view which shows the installed services and features on the pplication Server. 5t ena#les the System dministrator to add or delete services and features and it offers the possi#ility to search for a specific o#ect.
I'( ser Inter-ace
The ,4$5@- functions such as call flows are managed #y a >ava #ased we# 75. "I( ser Inter-ace
ll administration of the 5- system is performed #y using a >ava$#ased 75. Through the 5- user interfac e it is also possi#le to access a num#er of files in the &. See A-R sers 2uide Ser*ice Con$iguration Administration in C45 li#rary for detailed information 'S ser Inter-ace
ll @S administration is performed #y using a >ava$#ased 75. See 1S sers 2uide 1oucher Administration in C45 li#rary for detailed information
%.1%
*icense #anagement License manage ment in Charging System is related to #oth the allowed num#er of su#scri#ers and the right to use optional features. The commercial agreements are enforced #y a license server which manages a set of license %eys. The license %ey is encrypted and located in a Sentinel$license server located in one of the S"4s. The networ% elements involved are S"4 5- and @S. "5/ provides its own licensing depending related to #oth num#er of su#scri#ers and functionalities used. 5t is possi#le to run Charging System on trial without a license for seven days ena#ling test of for e2ample e x t r a c apac i t y. 5nitial license configuration is done at installation. &or more information a#out license management see Charging System Administration in C45 li#rary.
%.1&
!*erall 2uide
/ault #anagement The purpose of fault management is to report detected failures and to limit the failures effect on the networ% performance as far as possi#le. ll networ% elements automatically create and send alarms and events to the Ericsson peration$ and Support System (SS) which provides a centrali6ed alarm view of a mo#ile networ%. +elow picture shows a diagram of connections from different nodes in Ericsson CS3.0 to Ericsson SS for fault management.
Each alarm or event is descri#ed per networ% element in its own Alarm and "*ent Description document which can #e found in the C45 li#rary. Ericsson SS offer s several inter faces to #e used for networ% elements issuing alarms. "ependent on networ% element type the networ% elements in Charging System uses two different alarm interfaces'
• •
TS Te2t &ile daptation (T!&) Simple /etwor% anagement 4rotocol (S/4)
&or Solaris #ased networ% elements the hardware and the operating system are supervised #y a solution #ased on SunC. "etected faults are processed #y a Charging System specific application on the SunC server and sent to the Ericsson SS using T!&. &or TS4 #ased networ% elements one alarm interface is supported S/4.
&
$erminology 5& -47 SCS +,C C C5 CEL CC CC$45 CC+S CC/ C"C45 C4S CS CS
ccount 5nformation and -efill ccount &inder verage -evenue 4er 7ser dministration System for Charging Systems +usy ,our Call ttempt Customer daptation Customer dministration 5 nterface Customi6ed pplication for o#ile Enhanced Logic CustomerCare Customer Carer pplication 5nterface 4rotocol Customer Care and +illing System Charging Control /ode Call "ata -ecord Customer 4roduct 5nformation Calls 4er Second Charging system CS
!L
,
E2tensi#le mar%$up language
(e-erences Y
S"4 7sers ui de Se lection Tree dministration -ef . 1A< DD3$CS,
Y1Z
7SS" 7ser Event /otification &en" -ef. 10< :01A<
Y3Z
5/ST 7sers uide Service anagement and Statistics -ef. 3A
Y;Z
5/ST 4rogrammers uide Customer Care 45 DA
YDZ
verall uide C"- Configuration -ef. ;A
Y:Z
"etailed -ecord 4arameter List "ata -ecord utput S"4 -ef. <90 D9$&Q 301 11A< 7en.
Y8Z
"etailed -ecord 4arameter List Charging System 5/A4SL C"- -ef.
Y=Z
<90 D9$&Q 301 1:A< 7en. "etailed -ecord 4arameter List "ata -ecord utput 5- -ef. <90 D9$&Q 301 3DA< 7en.
Y9Z
"etailed -e cord 4arameter Li st CC/$C"- -ef. <9 0 D9$&Q 301 09A< 7en.
Y<0Z
verall uide Charging System dministration -ef.
Y<
@S 7sers uide @oucher dministration -ef.
Y<1Z
5/ST D.1 7sers uide Service anagement and Statistics -ef. 3A
