This thread follows eTOM's Infrastructure Lifecycle Management  which deals with development and deployment of new infrastructure, assessing performance of the infrastructure and taking action to meet performance commitments.

SDF assumes SOA for rapid creation of services from re-usable components hence a first cut of required infrastructure could be:

- service creation environment

- service orchestration environment

- service execution environment

- registries/repositories

For these we need input on management related aspects (methodologies, best practices, examples):

- capacity planning

- performance management

- SLA management

- configuration management

- high availability

- security

- scalability

What other technology elements should be considered for SDF Infrastructure?

If you have examples, have built or have ideas on this topic feel free to post them here for consideration

 

Thoughts from RFPs: an EMS for SDF infrastructure. Is this the right approach?

Does this approach fit SOA management needs?   

Does the portal (e.g. Portal Dashboard) also fall under this heading, specifically the capability to determine how service requests are presented to the user ?

What happens to Throttle Manager (control of services / applications / enablers across all layers)?

Ranga, this is a very interesting problem if i understand it correctly that is:

The SDF will contain some enabler, let's say messaging, which after all is a connector implementing some protocol like SMPP with one or more messaging centrals (SMS-C). These network resources only see and AAA the connector.

The identity of any SDF service using the messaging enabler will be hidden to the network resources because of the enabler so there is no immediate way to know which application is using which messaging central and how much.Some consequences are that one can not monitor SLAs with network resources per application/SDF service or can not say what is the resource cost per revenue from each application/SDF service.

Is this what you meant?  

Johan, you mean Portal to present a menu of services that a subscriber can invoke from a mobile device for example or some form of Administrative/Monitoring Portal  for services performance?

1. Yes exactly

2.  For monitoring  / loading / administering components across layers - SMSC enabler, OSS/BSS enabler etc

Rgds

Lucia,

I thinnk portal is not only to prvide the menu of services to consumer, but also an interactive interface during the promotion of merchandising. For example: promote a relative pic downlod services when a subscriber is whatching a online soccer video.

Hi Lucia,

In SDF Messaging enablers will not only conect to different messaging centrals like SMS-C but also take care of the load balancing between different SMSC or alternate routing in case of congestions. As the throughput per account in SMSC is defined it is important to regulate the rate at which we push the messages to it.

Throttle manager actually helps in controlling the throughput per messaging account and also does load balancing, alternative routing.

In this context SDF cannot have simple enablers or what we say as API to connect to different elements but also a mechanism to control the rate at which we can communicate with the network elements.

 

Cheers

Suraj