bcc ss mobile
TRANSCRIPT
-
7/25/2019 Bcc Ss Mobile
1/30
-
7/25/2019 Bcc Ss Mobile
2/30
Functions of BCCS
Provisioning
Billing
Customer Care
-
7/25/2019 Bcc Ss Mobile
3/30
BCCS BLOCK DIAGRAM
WAN
TCP/IP
CSR
CSR
CSR
OM
BP
OMDatabase
Customer
DATABASE
Connect
VU
Mediation
CDR
Storae
MSC
IN
UMS
WAP
IN
MSCs
WAP
UMS
SMSC
TCP/IP
!TAM
TCP/IP
TCP/IP
TCP/IP
-
7/25/2019 Bcc Ss Mobile
4/30
Level 2 RouterCisco 2621
LAN SwitchCisco 2950
PC/Terminal
P Printer
Connectivit! toLevel 1 router
CSR CONNECTIVITY SCHEMATIC
"thernet #ort Serial #ort
LAN ca$le
"1 at each location%s $ac&e' u# with %S(N )R%
Servers locate' atPune
Central Switch"1 Conver
ter
-
7/25/2019 Bcc Ss Mobile
5/30
Ahmedabad
Nagpur Raipur
Bhopal
Pune
5 CSRNode!onne!"ed
5 CSRNode!onne!"ed
5 CSRNode!onne!"ed
5 CSRNode
!onne!"ed
5 CSRNode
!onne!"ed
Ring ne"#or$ %or CSR!onne!"i&i"'
-
7/25/2019 Bcc Ss Mobile
6/30
250 CSR sites are connectin* centrall! at Pune vialevel1 routers connecte' in rin*+ The level1 routers
are connecte' $etween Pune, Na*#ur, Ahme'a$a',)ho#al - Rai#ur+
All the CSR locations are connecte' to level1 routervia 1 "1 lin&, 'e#en'in* on their re*ion+
Activities 'one at CSR locations are.Provisionin*+)illin* inormation or the customers+
(u#licate $illin*+)oo&in*+Allocation o Plan+Pre#ai' - Post#ai'+
Collections+
-
7/25/2019 Bcc Ss Mobile
7/30
5505 S/
Cen"ral Rou"er ()*
MSC Ne"#or$ diagram
MSC Rou"er
+)5 Rou"er
MSC,o!a"ion-.
Pune
Aurangabad
Nagpur
AhmedabadRa/$o"
Sura"
Bhopal
Raipur
Billing-er&er-
-
7/25/2019 Bcc Ss Mobile
8/30
SC Networ& is connecte' to 3 locations within thewest 4one+Pune, Auran*a$a', Na*#ur, Ahme'a$a', Ra&ot, Surat,)ho#al - Rai#ur+
The connectivit! 'ia*ram or the same is *iven $elow."ach SC location is connecte' with 1 "1 lin& - %S(N
as a $ac&u#+The "1 lin& is connecte' to the SC router - thenconnecte' to 25 router+The 25 router is connecte' to the switch where all
the C(R7s are collecte'+All the locations are connecte' at Pune to the CentralRouter+The Central Router is connecte' to the )illin* Serversvia Cisco switch+
All the C(R7s are urther sen' to )illin* Servers or
-
7/25/2019 Bcc Ss Mobile
9/30
ARBOR/OM
An order Management System which
supports order handling.
It supports workflow management
activities for products and services.
It is used in tandem with arbor/B.
-
7/25/2019 Bcc Ss Mobile
10/30
ORDR
!Central Conce"t of OM# !very order is associated with a master Account.
Master Account may be an e"isting account from Bas a new or pending account in #M.
An order consists of one or more items.
A single order can contain any combination of new$modified or disconnected service.
!"amples of order
a. %reate new Accountsb. Add products & services
c. %hange products & services.
d. 'iscontinue products or services.
-
7/25/2019 Bcc Ss Mobile
11/30
S$stem Arc%itecture
#M system architecture routes all
communications between the user interface
()*I+ and the database through a middlelayer.
#M is built around a ,'BMS (relational
database management system+ that contains
all orders and account information as well assystem configuration information.
-
7/25/2019 Bcc Ss Mobile
12/30
S$stem Arc%itecture
Cont&'((
#M servers and databases are logical
entities and they need not be uni-uely
associated with physical database.
-
7/25/2019 Bcc Ss Mobile
13/30
)et*or+ "rovisioning *or+flo*
he network provisioning process
begins when the %S, commits an
order0 comprised of one of moreproducts associated with network
provisioning related workflow items. he
se-uence of state transitions occurringfor each of the product level workflow
items associated with the new order.
-
7/25/2019 Bcc Ss Mobile
14/30
ORDR FLO,
BP
CSR OMCONNECT
VUSWITC"
#$ ICC i%es
an order
&$ Order ets inserted
into a tab'e in OM
Database
($ Pro%mr )ic*s u)
t+e order and sends it
to connect VU
,$ Pro%u)dater
u)dates t+e status o-
order as com)'eted$
#.$ Arbor u)dated
t+en u)dates t+e
order in t+e BP
$ T+e order is0ueued in t+e
connectVU -or
res)ecti%e 1W
2$ Order is sent to
t+e NE3S4itc+5
-or )ro%isionin$
6$ CVU com)'etes
t+e order and
sends
ac*no4'edement
to OM$
7$ T+e order etse8ecuted in t+e
s4itc+$
9$ S4itc+ sends an
ac* bac* to CVU$
#
(#.
6
2
9
-
7/25/2019 Bcc Ss Mobile
15/30
Ro'e o- Mediation
: Co''ects CDRs -rom %arious NEs
: !i'ters t+e CDRs 3A''o4in a'' ; on'< bi''ab'e
CDRs to t+e Bi''in S
-
7/25/2019 Bcc Ss Mobile
16/30
1low of %',s1low of %',s
Mediation SystemBILLDATS
MSC BPL MSC AHM
WAP
UMS
IN
SMSC
ARBOR BILLING SYSTEM
MSC Pune
TAM TAMTAM
TCP!IP
TCP!IP
TCP!IP
TCP!IP
TCP!IP
-
7/25/2019 Bcc Ss Mobile
17/30
Si=e o- CDRs: In MSC > #&. ? &.. B
-
7/25/2019 Bcc Ss Mobile
18/30
Ana' 22
: Su))'ementar< CDRs > #&
: Au8i''ar< CDRs > ((
-
7/25/2019 Bcc Ss Mobile
19/30
CDRs in BP
: On'< &2>&. o- t+e CDRs are ab'e to ma*eit to t+e Bi''in S
-
7/25/2019 Bcc Ss Mobile
20/30
T+e CDRs in BP
: MTC > 6 > 2&
: MOC > &. > &2 : RMR > >2
: VPN > .>&
: REST > .>&
: SMS > #6 ? &.
-
7/25/2019 Bcc Ss Mobile
21/30
Sa'ient Con-iurations: A'' t+e %oice ca'' detai's 3Bot+ )re)aid and
)ost)aid5 are co''ected -rom MSC
: T+e CDRs -rom IN are not used b< t+ebi''in -or an< )ur)ose 3 A't+ou+ t+e< are
not re0uired -or bi'' eneration )ur)ose5
-
7/25/2019 Bcc Ss Mobile
22/30
Sa'ient Con-iuration 3Contd $$5
: A'' t+e SMS CDRs are co''ected -rom
SMSC e8ce)t t+e MT>SMS o- Inroamers
: T+e ca'' detai' records o- DATA ca''s arebein co''ected -rom MSC$
-
7/25/2019 Bcc Ss Mobile
23/30
Prob'ems in Mediation oic
T+e )rob'ems arises 4+en mediation is unab'e
to do its ob o- sendin a'' t+e bi''ab'eCDRs and on'< t+e bi''ab'e CDRs to t+e
bi''in s
-
7/25/2019 Bcc Ss Mobile
24/30
Prob'ems in Mediation oic $$#$ Mediation +as been unab'e to )ro)er'