| In the old service-driven way, a Service Provider (SP) always builds an individual service operation system for each kind of services. These systems support both service managements and service operations. The more kinds of services, the more operation systems. Finally, each service provider, even each service, has its own operation system. It makes a hurge waste of resources and is hard for manament to Telcom Operators. It also drags off the development and release of the new service.So, the Telcom Operators hope to build an open platform for operation of value added services. This kind of system should give service providers standard interfaces for interoperation or commmunication. But a lot of problems will occure at this time. Services from different SP have different logic, so how can we handle the execution of different logic? Services of different kinds have to access different gateways with different protocols, how can we make this transparent to the SP? With a hurge number of services running on the same platform, how to ensure the stability and reliability of the system? Is there a low-cost implementation?MasterSP is designed and implemented for an open and uniform operation platform. As a platform, it must supply many common service running related stuffs to the third-party SP. To build a more efficient platfrom, the Telcom Operators will undoutly want to solve these problems. This article will tell you how the MasterSP system does.At first, this article introduces the background and significance of those problems, make a feasibility analysis and propose a prelimitary design. Then this article illustrates the detail design and implementation of MasterSP system, especially the method to solve these problems, such as use workflow to build business logic, unify and easy the access of third-party SP with Parlay X Web Service interface, use open source softwares to control cost, choose JMS based distributed architecture to make the system more stable and so on. |
