INtellECT® Service Creation Environment / Freely Definable Service Orchestration
The SCE does not impose architecture on you:
You can run SCE services independently side-by-side without any interference by defining for each service separate triggers.
You can run SCE services independently while implementing some common functions to be used by multiple services as subservices which are not triggered directly but expose their functionality as an SCE internal API to be invoked by other services. For example, a central Call Barring SCE service can be used by multiple other SCE services.
You can build any SCE service to be both triggered directly from the network and be invoked by other SCE services, allowing for Service Interaction and Service Chaining.
You can also invoke services hosted on external systems (SIP Application Server, legacy SCP or Web Service) from within an SCE service to include your existing services into your Interaction/Chaining Model. In this case, the SCE acts towards the triggering network as SCP or SIP-Application Server, and towards the external application server as SSP or S-CSCF and you can include in your application the capability to relay messages back and forth between both sessions.
You can implement a service broker based model, where one SCE Service acts as Service Broker, the only service to be triggered by the network and the one service centralizing call control functionality, whereas all other services expose their business logic as SCE-internal API to be invoked from within the Service Broker.
You can mix these models and implement a Service Broker model for services where heavy interaction is required, while running other services independently.