WO2012126228A2

WO2012126228A2 - Integrated value-added service system and method supporting multi-service integration

Info

Publication number: WO2012126228A2
Application number: PCT/CN2011/077585
Authority: WO
Inventors: 张玲东; 张超; 赵庆春; 郭亚梅
Original assignee: 中兴通讯股份有限公司
Priority date: 2011-03-22
Filing date: 2011-07-25
Publication date: 2012-09-27
Also published as: CN102694926A; CN102694926B; WO2012126228A3

Abstract

Disclosed are an integrated value-added service system and method supporting multi-service integration. The system comprises: a public transaction processing subsystem, configured to process common public transactions of various services; several service subsystems, each service subsystem corresponding to a service, and each service subsystem being configured to process particular transactions in the corresponding service thereof. The public transaction processing subsystem comprises a unified operation maintenance unit, configured to provide unified operation and maintenance for the service subsystems. The present invention extracts common parts of different service systems, so as to provide multiple service platforms with unified maintenance measures such as unified configuration, unified management, unified charging, and unified log and report unit, thereby effectively reducing the development cost and deployment cost, reducing the development period, achieving overall reduction of costs with respect to hardware, software and operation and maintenance, and achieving the objective of reducing CAPEX and OPEX.

Description

Integrated value-added service system and method supporting multi-service integration

The present invention relates to the field of communication technologies, and in particular, to a comprehensive value-added service system and method for supporting multi-service convergence. Background technique

With the rapid development of wireless communication technology and the emergence of telecom operations into the business era, national operators must carry out a variety of services to improve the ARPU (Average Revenue Per User) value. On the other hand, they face The task of reducing CAPEX (Capital Expenditure) and OPEX (Operating Expense), especially in emerging markets where the size of the site is small but the business is relatively complete, the deployment of new services, and In the expansion or replacement of existing services on the existing network, the principle of cost reduction must be followed to achieve the goal of maximizing revenue with minimum investment.

Figure 1 is a schematic diagram of an existing value-added service system architecture. As can be seen from Figure 1, in the prior art, the service platform built by the operator is still in an independent and separate construction mode. Each business has its own system, regardless of its size and function, and has its own business processing unit. Secondly, it also includes the functional modules needed to support the operation of its own business, such as operation and maintenance, user management, statistical analysis, billing management, Log reports, interface machines, user portals, and more. In addition, individual services also have their own unique functional modules, such as the Media Service module of the VMS (Voice Mail Service) service, and the CP portal of the LBS (Location Based Service) system.

It can be seen that in the prior art, in addition to the service processing unit, each service platform needs to separately deploy the public units such as operation and maintenance, user management, billing, and log of each service. The drawbacks of this scheme are becoming increasingly prominent: 1. The repeated construction of common modules between such service platforms directly leads to an increase in hardware costs and a waste of backup resources;

2. Maintenance costs increase, maintenance difficulty increases, and it is difficult to update and replace;

3. The development of these services also has the problem of repeated development of functional modules, wasting a lot of resources, and increasing the cost of software development. Summary of the invention

The technical problem to be solved by the present invention is to provide an integrated value-added service system and method for supporting multi-service convergence, which is used to solve the problem of waste of resources and high cost of various service platforms in the prior art.

To solve the above technical problem, in one aspect, the present invention provides a comprehensive value-added service system supporting multi-service convergence, where the system includes: a public transaction processing subsystem, and more than one service sub-system;

a common transaction processing subsystem, configured to handle common transactions common to various services; each service subsystem corresponds to a service, and each service subsystem is set to handle transactions unique to the corresponding service;

The public transaction processing subsystem includes:

The unified operation and maintenance unit is set to provide unified operation and maintenance for each service subsystem. Further, the public transaction processing subsystem includes:

The unified scheduling unit is set to perform scheduling management for each service subsystem.

Further, the public transaction processing subsystem includes:

The unified user management unit is set to manage the user data of various services in a unified manner. Further, the public transaction processing subsystem includes:

A unified user portal unit, set up to provide a unified user portal for a variety of businesses.

Further, the public transaction processing subsystem includes:

The unified log report unit is set to manage detailed business log reports generated by various services during business processing. Further, the public transaction processing subsystem includes:

The unified billing management unit is set to perform unified management of billing for various services.

Further, the public transaction processing subsystem includes:

The integrated interface unit is configured to provide a unified interface for communication between various services and external network elements. Further, the public transaction processing subsystem includes:

The unified signaling front-end unit is configured to implement message interaction between various services and the core network. In another aspect, the present invention also provides an integrated value-adding method for supporting multi-service convergence, the method comprising:

The public affairs of various services are handled by the public transaction processing subsystem;

The transactions unique to each service are processed by the service subsystem corresponding to the service to be processed, wherein each service subsystem corresponds to one service;

The common transaction processing subsystem provides unified operation and maintenance for each business subsystem.

Further, the public transaction includes one or more of the following items: unified operation and maintenance, unified scheduling management, unified user management, unified user portal, unified log, unified charging, unified interface, and unified signaling. deal with.

The beneficial effects of the present invention are as follows:

The invention extracts the common parts of different service systems, realizes unified maintenance, uniform management, unified billing, unified log report unit and other unified maintenance means of multiple service platforms, thereby effectively reducing development costs and subordinate costs, and shortening The development cycle has achieved a comprehensive reduction in hardware, software, and operation and maintenance costs, and has achieved the goal of reducing CAPEX and OPEX. DRAWINGS

Figure 1 is a schematic diagram of an existing value-added service system architecture;

2 is a schematic structural diagram of an integrated value-added service system supporting multi-service convergence in an embodiment of the present invention;

3 is a frame of an integrated value-added service system supporting multi-service convergence in an embodiment of the present invention; Schematic diagram

4 is a schematic diagram of relationships between units of an integrated value-added service system supporting multi-service convergence in an embodiment of the present invention;

FIG. 5 is a schematic diagram of an application of an integrated value-added service system supporting multi-service convergence in a network according to an embodiment of the present invention. detailed description

In order to solve the problem of waste of resources and high cost of various service platforms in the prior art, the present invention provides an integrated value-added service system and method for supporting multi-service convergence. The present invention will be further described in detail below with reference to the accompanying drawings and embodiments. It is understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

As shown in FIG. 2, an embodiment of the present invention relates to an integrated value-added service system supporting multi-service convergence, including: a public transaction processing subsystem 101, and a plurality of service subsystems 102;

The public transaction processing subsystem 101 is configured to process common transactions common to various services; wherein, the public transaction includes unified operation and maintenance of various services, unified scheduling management, unified user management, unified user portal, unified log report, and unified accounting Fees, unified interfaces, and unified signaling processing, etc., may be one or more of the above. Public affairs can also be shared by several businesses, not all of them.

A number of business subsystems 102 are used to handle transactions unique to various services. Each of the services corresponds to a service subsystem 102, and each transaction except the public transaction is processed by the corresponding service subsystem 102. The affairs unique to each business refer to the affairs of various businesses except public affairs. The embodiment of the present invention mainly provides a platform for supporting multi-service convergence. For a specific service, a public transaction is completed by a public transaction processing subsystem, and a specific transaction is completed by its own service subsystem. Therefore, The unique business of a specific business is no longer described in detail.

Since the system includes multiple service subsystems 102, it is necessary to 102 performs unified operation and maintenance management, such as device management, configuration information management, fault management, operation log, rights management, signaling tracking, failure observation, performance statistics, online help, and personalized tool management of each service subsystem. Therefore, the public transaction processing subsystem 101 includes a unified operation and maintenance unit 1011 for providing unified operation and maintenance for each service subsystem.

The present embodiment will be described in detail below with reference to FIG. 3. As seen in FIG. 3, an integrated value-added service system supporting multi-service convergence in this embodiment includes a public transaction processing subsystem 201 and a service subsystem 202.

The service subsystem 202 includes modules related to its business processing in each service and special function modules not available in the public transaction processing subsystem 201, such as a CP portal of the LBS service, a media server of the VMS service, and the like. The service of the service subsystem 202 includes but is not limited to: SMSC (Short Message Service Center), MMSC (Multimedia Message Service Center), WAP GW (Wireless Application Protocol Gate Way), SPAM ( Stupid person advertesing method, LBS (location service), VMS (voicemail), USSD (Unstructured Supplementary Service Data), SMGW (Short Message Gate Way), ASP ( Application Service Provider, OTA (Over-the-Air Technology, over-the-air) and various business subsystems that provide other value-added service functions.

The public transaction processing subsystem 201 includes: a unified operation and maintenance unit, a unified user management unit, a unified user portal unit, a unified scheduling unit, a unified log 4 table unit, a unified charging management unit, an integrated interface unit, and a unified signaling front. Machine unit.

Unified operation and maintenance unit provides a unified operation and maintenance service platform for each service subsystem, including: device management, configuration information management, fault management, operation log, rights management, signaling tracking, failure observation, performance statistics, online help, and Personality tool management of the business subsystem, etc. Unified user management unit to uniformly store and manage user data of all services. Supports all customers' unified access, supports BOSS (Business & Operation Support System), 0CS (Online Charging System), Blilling (billing) and other opening and closing channels.

The unified user portal unit provides a unified WEB/WAP user portal for each business user, supports single sign-on, and interacts with the unified user management unit to realize functions such as querying, setting, modifying, and managing address information of user information.

The unified scheduling unit provides the following functions: registration, logout, monitoring, management, etc. of host resources; management and subordinates of software versions of each service subsystem; loading, unloading, starting, and suspending of each service; monitoring and processing of each service processing capability Load balancing for each service load situation; manual disaster recovery and automatic disaster recovery for each service processor.

The unified log 4 table unit collects the detailed service logs generated by each service subsystem during the business process, parses the service logs into the database, generates the original data of the service logs, and provides data for log query, performance statistics, and report presentation. source.

Unified billing management unit, divided into prepaid interface and bill interface. The prepaid interface uniformly encapsulates the charging requests of each service subsystem into prepaid interactive messages and interacts with the prepaid center to support various mainstream charging protocols. The billing interface uniformly collects the original log files of each service subsystem, and converts the bills into the specified format according to the format of the billing format of the operator's billing system, and provides the bill to the operator's billing system for billing settlement.

The integrated interface unit integrates various communication protocols to provide a unified export for communication between each service and external network elements.

The unified signaling front-end unit integrates the signaling processing of each service subsystem, and simultaneously supports message distribution to each service processor, and performs balanced distribution when the service subsystem is multi-node.

The relationship between the various units will be described in detail below with reference to FIG. In Figure 4, the dotted arrow indicates the human-computer interaction relationship, the single solid arrow indicates the message interaction, and the double solid arrow indicates the number. According to the flow interaction relationship. As can be seen from the figure, the system of the present invention includes: a unified billing management unit

302. The unified user portal unit 304, the unified user management unit 306, the unified operation and maintenance unit 308, the service engines (service subsystems) 310, the unified log server unit 312, the unified scheduling unit 314, and the unified signaling front-end unit 316, integrated interface unit unit 318 nine parts.

The unified billing management unit 302 further includes two parts, namely, a prepaid interface machine and a billing interface machine, which respectively process prepaid requests and postpaid requests. The prepaid interface machine receives the prepaid request message from each service engine 310, performs charging request encapsulation according to the interface specification, and interacts with the external prepaid system to complete the prepaid function of each service. The prepaid interface machine is designed to layer the interface layer and the service layer. The interface layer is responsible for the maintenance of the protocol link and the unified protocol interface for external encapsulation. The specific service logic in the protocol package is the responsibility of each service. The service and interface machine are encapsulated. AVP's internal messaging. The bill interface machine uniformly collects the original documents of each service subsystem, converts the bills into the specified format according to the format of the operator billing system, and then provides the billing solution to the external operator billing system. The unified billing management unit 302 performs regular backup and delete management on the original bill file, and implements the alarm function of the alarm information related to the billing system, including the service log file collection failure alarm and the hard disk space shortage alarm.

The unified user portal unit 304 provides users with a unified style of self-service portal Web and WAP operation interfaces. Users only need to log in to the unified portal through the user number (or nickname) and password to experience multiple service operation management functions in one stop. The unified user portal unit 304 interacts with the unified user management unit 306 and the service engine 310 to receive user requests, and implements functions such as querying, setting, address book management, and overhead users of the user information.

The unified user management unit 306 integrates the information of each service user, performs centralized storage, and establishes a reasonable user information database table by using the user number as an index. The unified user management unit 306 encapsulates the unified interface for opening, closing, and user-related information, and provides service acceptance functions, and supports various open and sell channels such as WEB mode, short message mode, and operation and maintenance mode. The unified user management unit 306 encapsulates the user information calling interface with each service engine 310, the unified user portal unit 304, and the unified operation. The maintenance unit 308 and other common subsystem modules perform message interaction, and support each module to invoke, query, set, and modify user information. At the same time, the unified user management unit 306 records the service logs for various interactive accesses, and reports them to the unified log reporting unit 312 for centralized management.

The unified operation and maintenance unit 308, the specific maintenance functions include: device management, management of all network element information in the system, and management of the operation status of the network elements in the operation and maintenance system; configuration management, providing a unified configuration interface for various configurations of the system For example, service parameter configuration, system parameter configuration, etc.; fault management, collecting operational information of each service subsystem and module, and presenting them in a centralized manner, for maintenance personnel to refer to and assist in locating faults, and providing various means for users to view current alarms and historical alarms. Provides an interface for users to complete various alarm processing functions; tool management, providing a higher level of fault location means, such as signaling tracking, performance data statistics, etc.; operation log, the system needs to put the administrator through the operation and maintenance system to the system All kinds of operation logs are recorded for later auditing; rights management, providing complete rights management functions, including operator management, role management, authority assignment, etc.; online help, providing online help for system operators.

Further, the unified operation and maintenance unit 308 is divided into three layers, namely: a network element layer, a service layer, and a web browser layer. The NE layer includes network element management data collection functions, such as collection of alarm data and collection of performance statistics. Service layer, operation and maintenance server (OmmServer), operation and maintenance portal Web server (OmmPortal), operation and maintenance database. OmmServer mainly interacts with the managed network elements through the message mechanism to obtain management data, and processes or stores the data. The OmmPortal operation and maintenance portal is a B/S framework operation portal, which runs in the web container and is remotely located. The browser is accessed through the HyperText Transfer Protocol (HTTP), which interacts with OmmServer, processes business logic, and accesses databases. The web browser layer provides a portal for the unified operation and maintenance unit, and performs various operation and maintenance interface functions through the browser. The business engine 310 interacts with other public units to provide core business functions, including SMSC (SMS), MMSC (MMS), WAP GW (SPA Gateway), SPAM (Garbage Monitoring Service), LBS (Location Service), VMS ( Voicemail), USSD (unstructured supplementary data service), SMGW (SMS Gateway), ASP (Value Added Service Platform), OTA (over the air), etc. Of course, the service engine 310 is not limited to the above-listed business systems, and all value-added services of a similar system organization structure can be integrated according to the solution of the present invention.

The unified log reporting unit 312 collects log CDR files from each service engine 310 and unified user data management 306, and parses various types of service log CDRs into the database to generate log data and performance statistics. And report presentations provide data sources. The unified log report unit 312 logically includes an FTP interface machine, a log storage module, a log presentation data processing module, a log presentation module, a report data preprocessing module (optional), a report presentation data processing module, a report presentation module, and a network management intermediate data. Statistics module, etc. The log presentation module and the report presentation module are uniformly embedded in the unified operation and maintenance unit 308 portal.

The unified scheduling unit 314 manages and schedules host resources in the system to maximize device utilization. Specifically, it includes the following functions: registration, logout, monitoring, management, etc. of all host resources of the system; management and subordinates of software versions of each service subsystem; loading, unloading, starting, and suspending of each service; monitoring and processing of processing capabilities of each service engine Load balancing for each service engine load situation; manual disaster recovery and automatic disaster tolerance for each service engine.

Further, the unified scheduling unit 314 includes a scheduling management module, a scheduling center module, and an automatic sub-module module. The scheduling management module is integrated on the portal of the unified operation and maintenance unit 308, and mainly includes information display of the host resources, version management, and page operation and maintenance of the functions related to the unified scheduling. The dispatching center module is responsible for the process control of the entire unified scheduling subsystem, performing message interaction with the operation and maintenance, automatic subordinates, physical hosts, and offloading devices, and managing physical host resources and service node information. The automatic sub-module module provides a unified interface to each service, and completes loading, unloading, starting, and suspending operations of each service. The unified signaling front-end unit 316 fuses each service signaling processing to implement all functions of the front-end machine, and is responsible for message interaction between each service engine and the core network. Supports message distribution to each service engine, and supports balanced distribution of multiple nodes when the service is multi-node.

The integrated interface unit 318 encapsulates various communication protocols such as SMPP, SGIP, CMPP, and HTTP, and is called by each service engine and related public subsystems to provide a unified exit for communication with external network elements.

The integrated value-added service system supporting multi-service convergence in the embodiment of the present invention is applied in the network as shown in FIG. 5. The integrated value-added service system supporting multi-service convergence is a converged multi-service platform, including SMSC, MMSC, WAPGW, and ASP. , USSD, VMS and other business platforms. For external connection, the south can connect to CDMA (Code Division Multiple Access), GSM (Global System of Mobile communication), WCDMA (Wideband Code Division Multiple Access), TD -SCDMA (Time Division-Synchronous Code Division Multiple Access), NGN (Next Generation Network), PSTN (Public Switched Telephone Network), and other different networks. The northbound can connect to other external business systems such as SMSC, MMSC, WAPGW, ASP, E-GW (email GW, email gateway) already existing in the network. Further, as an indispensable support for the service system, the integrated value-added service system supporting multi-service convergence is also connected to the IN/OCS, HLR (Home Location Register)/HSS (Home Subscriber Server), Auxiliary network elements such as NMS (Network Management System), BOSS, NPDB (Number Portability database), Provisioning (Supply).

In addition, the present invention also relates to an integrated value-adding method for supporting multi-service convergence, the method comprising:

The public affairs of various services are handled by the public transaction processing subsystem; The transactions unique to each service are processed by the service subsystem corresponding to the service to be processed, wherein each service subsystem corresponds to one service;

The common transaction processing subsystem and the service subsystem in the method are the same in function and structure as the public transaction processing subsystem and the service subsystem in the foregoing embodiment, and will not be described in detail herein.

As can be seen from the foregoing embodiments, the present invention effectively reduces the common maintenance of multiple service platforms by implementing common parts of different service systems, such as unified configuration, unified management, unified charging, and unified log reporting units. Development costs and subordinate costs, shortened the development cycle, achieved a comprehensive reduction in hardware, software, and operation and maintenance costs, and achieved the goal of reducing CAPEX and OPEX.

While the preferred embodiments of the present invention have been disclosed for purposes of illustration, those skilled in the art will recognize that various modifications, additions and substitutions are possible, and the scope of the invention should not be limited to the embodiments described above.

Claims

Claim

An integrated value-added service system supporting multi-service convergence, wherein the system comprises: a public transaction processing subsystem and one or more service subsystems;

The public transaction processing subsystem includes:

The unified operation and maintenance unit is set to provide unified operation and maintenance for each service subsystem.

2. The integrated value-added service system supporting multi-service convergence according to claim 1, wherein the public transaction processing subsystem comprises:

3. The integrated value-added service system supporting multi-service convergence according to claim 2, wherein the public transaction processing subsystem comprises:

The unified user management unit is set to manage the user data of various services in a unified manner.

The integrated value-added service system supporting multi-service convergence according to any one of claims 1 to 3, wherein the public transaction processing subsystem comprises:

The unified log report unit is set to manage detailed business log reports generated by various services during business processing.

6. The integrated value-added service system supporting multi-service convergence according to claim 1, wherein the public transaction processing subsystem comprises:

7. The integrated value-added service system supporting multi-service integration as claimed in claim 1, 2, 3 or 6. The public transaction processing subsystem includes:

The integrated interface unit is configured to provide a unified interface for communication between various services and external network elements.

8. The integrated value-added service system supporting multi-service convergence according to claim 1, 2, 3 or 6, wherein the public transaction processing subsystem comprises:

The unified signaling front-end unit is configured to implement message interaction between various services and the core network.

9. A comprehensive value-adding method for supporting multi-service integration, wherein the method comprises: processing a common transaction of various services by a public transaction processing subsystem;

10. The integrated value-adding method for supporting multi-service convergence according to claim 9, wherein the public transaction comprises one or more of the following: unified operation and maintenance, unified scheduling management, unified user management, unified user Portal, unified log reporting, unified billing, unified interface, and unified signaling processing.