| Author |
Message
|
| messbrok |
 Posted: Tue Mar 21, 2006 12:21 pm Post subject: Telecom Project Architecture |
 |
|
Newbie
Joined: 21 Mar 2006
Posts: 3
|
Guys,
This is more of a general question. I am looking for an example architecture(rather diagram) of telecom domain which utilizes middleware.
Could someone pls tell me where i can find this.
Thanks. |
|
| Back to top |
|
 |
| vennela |
| Posted: Tue Mar 21, 2006 12:33 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
Most likely you may not find one.
The best bet for you is to understand your problem and explain it here and somebody might help you in architecting it, or point you in the right direction to look for information. |
|
| Back to top |
|
|
| messbrok |
| Posted: Tue Mar 21, 2006 12:43 pm Post subject: |
|
|
Newbie
Joined: 21 Mar 2006
Posts: 3
|
Actually i would like to know the key components of telecom sector which directly or indirectly connect to Middleware hub.
I am from healthcare sector and planning to move to telecom. But i have no idea'bt it.
Thanks. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Mar 21, 2006 12:46 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I think all key components of the telecom sector could directly or indirectly connect to a middleware hub.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| wschutz |
| Posted: Tue Mar 21, 2006 12:48 pm Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
|
| Back to top |
|
|
| messbrok |
| Posted: Tue Mar 21, 2006 1:06 pm Post subject: |
|
|
Newbie
Joined: 21 Mar 2006
Posts: 3
|
Thanks Wayne,
But i could not find the required. I would just like to know the key components(their names) that are part of the telecom sector.
Ex: Component that handles billing etc. In other words, name/type of entities that constitute a typical telecom sector.
Many thanks. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Mar 21, 2006 1:16 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| wschutz wrote: |
| Google might help ... |
Good luck!
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| jbanoop |
| Posted: Tue Mar 21, 2006 11:10 pm Post subject: |
|
|
Chevalier
Joined: 17 Sep 2005
Posts: 401
Location: SC
|
Hi messbrok,
Here goes my two cents.. (sorry bt the diagram...) I am not sure about typical tecom projects but as for the one I am aware of, the middleware talks with a billing system (the billing solution will differ obviously for different providers), the mediation agency (usually a central agency specific to the country/region), a crm (usually the customer facing app would be the CRM), an erp (depends..), and mostly very many home grown solutions/implementations for interacting with ATM recharges and things like that ..
Also pre-paid and postpaid might have different systems as backends which would bean ur middleware will end up talking to these as well ...
so to make a long answer short .. it depends ..
hope this helps,
Regards,
Anoop |
|
| Back to top |
|
|
| brin_seb |
| Posted: Wed Mar 22, 2006 7:50 am Post subject: OSS, BSS, eTOM, ITU...... |
|
|
Novice
Joined: 10 Jun 2003
Posts: 24
Location: Luxembourg
|
Find enclosed some informations...
eTOM :
The Enhanced Telecom Operations Map® (eTOM) describes the enterprise processes required by a service provider and analyses them to different levels of detail according to their significance and priority for the
business.
International Telecommunication Union Recommendations M.3050.x
M.3050.0 Introduction - 07/04
M.3050.1 The business process framework - 06/04
M.3050.2 Process decompositions and descriptions
M.3050.3 Representative process flows - 06/04
M.3050.4 B2B integration - 06/04
M.3050 Supplement 1 : eTOM - ITIL application note - 05/04
M.3050 Supplement 2 : Public B2B Business Operations Map (BOM) - 05/04
M.3050 Supplement 3 : eTOM to M.3400 mapping - 06/04
IT Infrastructure Library
OSS/J
The OSS through Javaâ„¢ Initiative defines a set of APIs, with client
access either by tightly or loosely coupled mechanisms, to foster an OSS
component market. The goals of the initiative are to develop, through the Java Community ProcessSM (JCP) program, API specifications, reference
implementations, and technology compatibility kits, for OSS integration
and deployment.
JSR 144 - OSS Common API v1.2
JSR 89 - OSS Service Activation API v0.8
JSR 90 - OSS Quality of Service API v1.0
JSR 91 - OSS Trouble Ticket API v1.0
JSR 130 - OSS IP Billing API v1.1
JSR 142 - OSS Inventory API v1.0
JSR 210 - OSS Service Quality Management API v0.9
JSR 251 - OSS Pricing API
JSR 254 - OSS Discovery API
JSR 263 - OSS Fault Management API
JSR 264 - OSS Order Management API v0.5
JSR 285 - OSS Performance Management API |
|
| Back to top |
|
|
| vennela |
| Posted: Wed Mar 22, 2006 8:31 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| messbrok wrote: |
I am from healthcare sector and planning to move to telecom. But i have no idea'bt it.
Thanks. |
If you tell the healthcare key components, then maybe someone will understand what you actually mean and tell you |
|
| Back to top |
|
|
|
|
