Scheme 1: BOSS adds a data center for content business management.
Implementation scheme: Expand the scope of supporting network and directly add content management platform as a subsystem of BOSS. At the same time, the business data distribution agent between BOSS and various business platforms is added. The BOSS system directly controls the billing gateway of each business platform to generate bills. All business service flows generated by the user portal are digested inside the BOSS. This scheme can simplify the level of mobile service platform and make the service management data interface directly based on BOSS standard. The problem is transferred to the support network accordingly, which makes the support network have to consider a lot of business logic implementation details. This huge and comprehensive architecture has the risk of "the ship is too big to turn around".
Scheme 2: Keep the overall structure of the existing service network/supporting network unchanged, and set up sub-data centers in parallel with MISC for all major services.
Implementation scheme: At present, MISO system can't respond to the demand of 3G service development in time. First of all, try to build other parallel sub-data centers and work according to the current business service flow interaction mode between MISC system and BOSS. This scheme can solve some emergency platform construction problems that cannot be solved in time for various reasons, and explore the advantages and disadvantages of various schemes in parallel. Of course, there is a waste of investment in repeated construction, and there is also a problem of heavy workload brought about by the unified transformation of the system in the future.
Scheme 3: Improve the existing MISO core management system and portal, and add routing agents/billing gateway agents for various platform services.
Implementation scheme: This is a scheme that can be implemented smoothly compared with the current network architecture. In fact, at present, the interface specification between MISC system and related systems has been improved, and the addition of routing rule setting module and charging gateway proxy module for content charging has been preliminarily considered. In this scheme, a mobile data information center is established outside BOSS, which provides user management, subscription relationship management, access authentication and content directory management services for most data services, and carries out daily content operation for sP/cF development interface. The risk lies in the current development mode and efficiency of MISt system, and whether the timetable for implementing relevant interface specifications from top to bottom can be completed on time. In addition, the data center will produce massive data, and daily operation and maintenance need more energy, and these resources are still lacking.