CN101754132A - White list management system and method as well as business operation support system proxy server - Google Patents

Abstract

The invention relates to a white list management system, method and BOSS proxy server. The system includes a BOSS system for authenticating the white list of business systems, one or several business systems; it also includes: a BOSS proxy server, connected to the business system and the BOSS system respectively, for receiving business The new white list submitted by the system, and synchronizing the new white list to the BOSS system; and receiving the white list passed by the BOSS system after authenticating the new white list, and sending the white list passed through the authentication Synchronized to the business system; the business system adds the white list that passes the authentication to the white list library in the business system. The invention realizes that the white list library in the BOSS system can be updated automatically in a timely and accurate manner according to the white list of the business system, and can also reduce the pressure on the industry gateway to use the white list library to authenticate the target mobile phone number.

Description

Whitelist management system, method, and business operation support system proxy server

technical field

The invention relates to the field of data services, in particular to a whitelist management system and method for group products and a BOSS proxy server.

Background technique

Group customer business is one of the main business models of value-added services. All telecom operators have invested a lot of manpower and material resources in the group customer business to launch products that meet the needs of group customers. Among them, the group's short message products have the characteristics of high service penetration rate and high user utilization rate. However, with the development of the business, the problem of the imperfect management mechanism of the target mobile phone number in the group's short message business has gradually been exposed and become more prominent, resulting in more and more serious complaints about spam text messages. Therefore, telecom operators conduct unified and standardized management of value-added services such as group SMS group sending through the "white list" management method. However, due to the differences between the new "white list" management method and the original business management mechanism, especially the mobile agent server (Mobile Agent Server, referred to as MAS) business, due to the BOSS (Business Operation Support System) in the original business management mechanism ) system is not allowed to provide an interface to the external network environment, so the MAS business does not have a direct interface with the BOSS system, so how to realize the "white list" data transfer between the MAS system and the BOSS system has become the main technical bottleneck in the implementation of the "white list" management mechanism one.

At present, the group's SMS products are managed by two technical means: "white list" and enterprise real name (SMS signature). Among them, the "white list" is uniformly managed by the industry gateway (Industry Application GateWay/IAGW, hereinafter referred to as the industry gateway). The business system will synchronize the "white list" to the BOSS system, and the BOSS system will synchronize the "white list" to the industry gateway after status authentication. Authenticate. For example, for MAS business, since there is no direct interface to the BOSS system, the business system of the MAS business will synchronize the "white list" to the BOSS system, and the "white list" can only be manually imported into the BOSS system. Entered into the BOSS system; when the business system of the MAS business sends a text message through the industry gateway, the industry gateway conducts status authentication through the "white list".

Since the MAS business manually imports the "white list" data into the BOSS system, it cannot guarantee the timeliness and accuracy of the "white list" in the BOSS system, and it also greatly increases the number of operators' account managers or related personnel. workload. In addition, when the business system of the MAS business sends a short message, because the business system cannot obtain the "white list" in the BOSS system, it cannot authenticate the target mobile phone number through the "white list", and can only be authenticated by the industry gateway through the "white list". "White list" to authenticate the target mobile phone number, which has led to an increase in the authentication pressure of the "white list" of industry gateways.

Contents of the invention

The purpose of the present invention is to address the defects of the above-mentioned prior art, propose a whitelist management system, method and business operation support system (BOSS) proxy server of group products, and realize that the whitelist library in the BOSS system can be processed according to the whitelist of the business system. Timely and accurate automatic updates.

In order to achieve the above object, according to an embodiment of the present invention, a whitelist management system is proposed, including a BOSS system, one or several business systems; it also includes: a BOSS proxy server, and the business system and the BOSS system Respectively connect to receive the new white list submitted by the business system, and synchronize the new white list to the BOSS system; and receive the white list passed after the BOSS system authenticates the new white list, and send the new white list The white list that passes the authentication is synchronized to the business system; the business system adds the white list that passes the authentication to a white list library in the business system.

In order to achieve the above object, according to an embodiment of the present invention, a whitelist management method is proposed, which includes: the business system synchronizes the newly added whitelist to the BOSS system through the BOSS proxy server; Authentication; the BOSS system synchronizes the whitelist passed through the authentication to the business system through the BOSS proxy server; the business system adds the whitelist passed through the authentication to the whitelist database in the business system.

In order to achieve the above object, according to an embodiment of the present invention, a BOSS proxy server is proposed, which includes: a synchronization module, which is used to receive the newly added whitelist submitted by the business system, and synchronize the newly added whitelist to the BOSS system and receiving the white list passed after the BOSS system authenticates the newly added white list, and synchronizing the authenticated white list to the service system.

The BOSS proxy server introduced in the present invention realizes the automation of the synchronization between the business system and the white list in the BOSS system. The white list in the business system is imported into the BOSS system by manual input, thus reducing the workload of the operator's account manager or related personnel; further, the present invention realizes that the white list library of the business system can When the business system performs business operations on the target mobile phone number through the industry gateway, the business system can choose to authenticate the target mobile phone number through the white list library, because it can be done without industry The gateway uses the whitelist library to authenticate the target mobile phone number, so it can reduce the pressure on the industry gateway to use the whitelist library to authenticate the target mobile phone number.

Description of drawings

FIG. 1 is a schematic structural diagram of Embodiment 1 of a whitelist management system;

FIG. 2 is a schematic structural diagram of Embodiment 2 of a whitelist management system;

Fig. 3 is a schematic structural diagram of Embodiment 1 of a BOSS proxy server;

Fig. 4 is a schematic structural diagram of a second embodiment of a BOSS proxy server;

Fig. 5 is a schematic structural diagram of Embodiment 3 of a BOSS proxy server;

FIG. 6 is a schematic flowchart of Embodiment 1 of a whitelist management system;

FIG. 7 is a schematic flowchart of Embodiment 2 of a whitelist management system.

Detailed ways

FIG. 1 is a schematic structural diagram of Embodiment 1 of a whitelist management system according to the present invention. Embodiment 1 of the whitelist management system, as shown in Figure 1, includes a BOSS system, one or several business systems (only one business system is drawn in Figure 1), and also includes a BOSS proxy server, which implements a business The interface to the system and the interface to the BOSS system.

The BOSS proxy server is used to receive the new white list submitted by the business system, and synchronize the new white list to the BOSS system; and receive the white list passed by the BOSS system after authenticating the new white list, and send the new white list that has passed the authentication The whitelist is synchronized to the business system. The newly added white list is a white list other than the current white list library in the business system.

The business system adds the authenticated white list to the white list library in the business system.

Among them, the white list passed by the BOSS system after the authentication of the newly added white list is the user terminal number in the BOSS system whose user status in the newly added white list meets the set conditions.

The whitelist management system in this embodiment may also include: an industry gateway, configured to receive user terminal numbers in the newly added whitelist from the BOSS system whose user status meets the set conditions. Before the business system performs business operations on the target mobile phone number through the industry gateway, it first needs to authenticate the target mobile phone number, and then perform business operations on the target mobile phone number that has passed the authentication. There are two methods:

(1) Authenticate the target mobile phone number through the whitelist library in the industry gateway.

(2) Authenticate the target mobile phone number through the white list library in the service system.

If the case (1) is used, the target mobile phone number is authenticated through the white list of the industry gateway. Generally, since multiple business systems correspond to one industry gateway, then when multiple business systems have requests for authentication of the target mobile phone number , then it will cause the authentication pressure of the industry gateway; if the situation (2) is adopted, the authentication of the target mobile phone number is distributed to the corresponding business system, then the authentication pressure of the industry gateway can be reduced (including avoided) .

In this embodiment, the BOSS proxy server implementing the interface to the business system and the interface to the BOSS system is introduced to realize the automation of whitelist synchronization between the business system and the BOSS system. Specifically, the whitelist library in the BOSS system can be based on the business system Timely and accurate automatic update of the whitelist in the business system, since the whitelist in the business system does not need to be imported into the BOSS system by manual input, thus reducing the workload of the operator's account manager or related personnel; further, this embodiment Realized that the whitelist database of the business system can be automatically updated in a timely and accurate manner according to the whitelist passed back by the BOSS system. When the business system performs business operations on the target mobile phone number through the industry gateway, the business system can choose to pass The white list library is used to authenticate the target mobile phone number. Since the industry gateway does not need to use the white list library to authenticate the target mobile phone number, it can reduce the pressure on the industry gateway to use the white list library to authenticate the target mobile phone number.

FIG. 2 is a schematic structural diagram of Embodiment 2 of a whitelist management system according to the present invention. The difference between this embodiment and the first embodiment of the whitelist management system is that the industry gateway in this embodiment is used to receive the user terminal numbers in the newly added whitelist from the BOSS system whose user status meets the set conditions, and The received user terminal number is added to the local white list library corresponding to the business system, and the white list successfully entered is sent back to the BOSS system; the BOSS system uses the successfully entered white list from the industry gateway as authentication The passed whitelist is sent to the BOSS proxy server.

The business system takes the MAS business system as an example. When the MAS business system sends a text message, it first conducts whitelist authentication on the target mobile phone number that sends the text message, that is, judges whether the target mobile phone number exists in the white list database of the MAS business system. (i.e. the address book of the MAS business system), if it exists in the whitelist library of the MAS business system, it indicates that the target mobile phone number has passed the authentication, and sends a short message to the target mobile phone number passed through the authentication through the industry gateway; If it does not exist in the whitelist database of the MAS business system, the target mobile phone number must be added to the whitelist database of the MAS business system after being processed through the whitelist import process before the target mobile phone number can be registered. SMS sending operation. In this way, it is possible to avoid sending a large number of short messages with numbers other than the white list library of the business system as the target mobile phone number to the industry gateway for authentication, thereby reducing (including avoiding) the authentication of the target mobile phone number by the white list library of the industry gateway pressure.

In this embodiment, the white list synchronized to the business system is further limited, that is, the BOSS returns the white list that has been authenticated and successfully added to the white list library corresponding to the business system in the industry gateway to the BOSS proxy server, and the BOSS The proxy server is synchronized to the business system, and the business system will add the white list that has passed the authentication and successfully added to the white list database to the white list database in the business system, so as to ensure that the business system can not only realize the white list in the BOSS system Synchronized automatic update can also realize synchronous automatic update with the white list in the industry gateway. When the business system performs business operations on the target mobile phone number through the industry gateway, it can ensure that the white list library of the business system is selected to perform the target mobile phone number. Authentication is used to replace the accuracy of authentication when using the whitelist library of the industry gateway to authenticate the target mobile phone number.

The embodiment of the present invention also provides a BOSS proxy server. The BOSS proxy server includes: a synchronization module, configured to receive the newly added whitelist submitted by the business system, and synchronize the newly added whitelist to the BOSS system; Whitelist, and synchronize the authenticated whitelist to the business system.

FIG. 3 is a schematic structural diagram of Embodiment 1 of a BOSS proxy server. As shown in Figure 3, the synchronization module in the BOSS proxy server in this embodiment includes: a first synchronization module, which is used to receive the newly added whitelist submitted by the business system, and synchronize the newly added whitelist to the BOSS system; The second synchronization module is configured to receive the whitelist passed by the BOSS system after authenticating the newly added whitelist, and synchronize the authenticated whitelist to the business system.

Wherein the second synchronization module receives the white list that the BOSS system has passed the authentication of the newly added white list, and synchronizes the white list that has passed the authentication to the business system. The white list in the white list library corresponding to the business system in the gateway will synchronize the white list that has passed the authentication and successfully added to the white list library corresponding to the business system in the industry gateway to the business system.

FIG. 4 is a schematic structural diagram of Embodiment 2 of a BOSS proxy server. As shown in Figure 4, in addition to including the first synchronization module and the second synchronization module in Embodiment 1 of the BOSS proxy server, it also includes: a database connected to the first synchronization module and the second synchronization module respectively for storing The new white list that needs to be synchronized from each business system to the BOSS system and the white list that needs to be synchronized from the BOSS system to each business system after authentication.

FIG. 5 is a schematic structural diagram of Embodiment 3 of a BOSS proxy server. As shown in Figure 5, with respect to the second embodiment of the BOSS proxy server, the BOSS bring server in this embodiment also includes: an ftp server, which is created by the BOSS proxy server to provide the BOSS system and each business system through Access the interface of the BOSS proxy server through ftp. It can cooperate with the ftp server to assign a user name and password for the BOSS system and each business system. After the user information is created by the administrator, the operator will be notified manually. The BOSS system and each business system can log in to the BOSS proxy server through ftp.

The database can be organized in the following two forms:

(1) Establish a sub-database based on each business system, use the index query interface to use the identification information of the business system as an index, and query the sub-database corresponding to the business system from the sub-database corresponding to the business system, which needs to be synchronized to the BOSS from the business system The white list of the system and the white list that needs to be synchronized from the BOSS system to the business system.

Specifically, the database includes: a sub-database corresponding to each business system, and an index query interface connected to each sub-database;

Each subdatabase includes:

The E2B folder is used to store the white list that needs to be synchronized from the business system corresponding to the sub-database to the BOSS system;

The B2E folder is used to store the whitelist that needs to be synchronized from the BOSS system to the business system corresponding to the sub-database;

The index query interface is used to use the identification information of the business system as an index to query the white list corresponding to the business system that needs to be synchronized from the business system to the BOSS system from the sub-database corresponding to the business system and the white list that needs to be synchronized from the BOSS system to the Whitelist of business systems.

(2) Establish a B2E folder sub-database based on the data that the BOSS system needs to synchronize to the business system, and establish an E2B folder sub-database based on the data that the business system needs to synchronize to the BOSS system. The index query interface uses the identification information of the business system as an index to query The business system corresponds to the white list that needs to be synchronized from the business system to the BOSS system and the white list that needs to be synchronized from the BOSS system to the business system.

Specifically, the database includes:

The E2B folder sub-database is used to store the white list that needs to be synchronized from each business system to the BOSS system;

The B2E folder sub-database is used to store the white list that needs to be synchronized from the BOSS system to each business system;

The index query interface is connected to the E2B folder sub-database and the B2E folder sub-database respectively, and is used to use the identification information of the business system as an index to query the white list corresponding to the business system that needs to be synchronized from the business system to the BOSS system And the white list that needs to be synchronized from the BOSS system to the business system.

The above-mentioned database may also include: an authentication information verification library, which is used to verify whether the authentication information of the business system is correct when the business system synchronizes the newly added white list to the BOSS system through the BOSS proxy server. If it is correct, it is allowed to add the white list Synchronize to the E2B folder corresponding to the business system; it is also used to verify whether the authentication information of the business system is correct when the BOSS system synchronizes the whitelist that passed the authentication to the business system through the BOSS proxy server. The white list in the B2E folder corresponding to the business system is synchronized to the business system.

FIG. 6 is a schematic flowchart of Embodiment 1 of a whitelist management method. As shown in Figure 6, including:

Step 61, the business system submits the new white list to the BOSS proxy server;

Step 62, the BOSS proxy server synchronizes the newly added white list to the BOSS system;

Step 63, the BOSS system authenticates the newly added white list;

Step 64, the BOSS system synchronizes the whitelist that has passed the authentication to the industry gateway;

Step 65, the BOSS system synchronizes the whitelist that has passed the authentication to the BOSS proxy server;

Step 66, the BOSS proxy server synchronizes the whitelist passed through the authentication to the business system;

Step 67, the business system adds the white list that has passed the authentication to the white list database in the business system;

Step 68, the service system performs service operations on the target mobile phone number through the industry gateway.

Among them, in step 68, the business system performs business operations on the target mobile phone number through the industry gateway, including: the business system authenticates the target mobile phone number according to the white list database in the business system, and performs business on the target mobile phone number through the industry gateway. operate.

In this embodiment, the BOSS proxy server implementing the interface to the business system and the interface to the BOSS system is introduced to realize the automation of whitelist synchronization between the business system and the BOSS system. Specifically, the whitelist library in the BOSS system can be based on the business system Timely and accurate automatic update of the whitelist in the business system, since the whitelist in the business system does not need to be imported into the BOSS system by manual input, thus reducing the workload of the operator's account manager or related personnel; further, this embodiment Realized that the whitelist database of the business system can be automatically updated in a timely and accurate manner according to the whitelist passed back by the BOSS system. When the business system performs business operations on the target mobile phone number through the industry gateway, the business system can choose to pass The white list library is used to authenticate the target mobile phone number. Since the industry gateway does not need to use the white list library to authenticate the target mobile phone number, it can reduce the pressure on the industry gateway to use the white list library to authenticate the target mobile phone number.

FIG. 7 is a schematic flowchart of Implementation 2 of a whitelist management method. As shown in Figure 7, including:

Step 71, the business system submits the new white list to the BOSS proxy server;

Step 72, the BOSS proxy server synchronizes the newly added white list to the BOSS system;

Step 73, the BOSS system authenticates the newly added white list;

Step 74, the BOSS system synchronizes the whitelist that has passed the authentication to the industry gateway;

Step 75, the industry gateway adds the whitelist that has passed the authentication to the whitelist library corresponding to the business system in the industry gateway; specifically, the industry gateway receives the user whose user status meets the set conditions in the newly added whitelist from the BOSS system Terminal number, adding the received user terminal number to the local white list database corresponding to the business system; step 76, returning the white list successfully added to the white list database to the BOSS system;

Step 77, the BOSS system synchronizes the white list that has passed the authentication and successfully added to the white list library to the BOSS proxy server;

Step 78, the BOSS proxy server synchronizes the whitelist passed through the authentication to the business system;

Step 79, the business system adds the white list that has passed the authentication and successfully added to the white list database to the white list database in the business system;

Step 710, the service system performs service operations on the target mobile phone number through the industry gateway.

Wherein in step 710, the business system performs business operations on the target mobile phone number through the industry gateway, including: the business system authenticates the target mobile phone number according to the whitelist database in the business system, and performs business on the target mobile phone number through the industry gateway. operate. The business system takes the MAS business system as an example. When the MAS business system sends a text message, it first conducts whitelist authentication on the target mobile phone number that sends the text message, that is, judges whether the target mobile phone number exists in the white list database of the MAS business system. (i.e. the address book of the MAS business system), if it exists in the whitelist library of the MAS business system, it indicates that the target mobile phone number has passed the authentication, and sends a short message to the target mobile phone number passed through the authentication through the industry gateway; If it does not exist in the whitelist database of the MAS business system, the target mobile phone number must be added to the whitelist database of the MAS business system after being processed through the whitelist import process before the target mobile phone number can be registered. SMS sending operation. In this way, it is possible to avoid sending a large number of short messages with numbers other than the white list library of the business system as the target mobile phone number to the industry gateway for authentication, thereby reducing (including avoiding) the authentication of the target mobile phone number by the white list library of the industry gateway pressure. In this embodiment, the white list synchronized to the business system is further limited, that is, the BOSS returns the white list that has been authenticated and successfully added to the white list library corresponding to the business system in the industry gateway to the BOSS proxy server, and the BOSS The proxy server is synchronized to the business system, and the business system will add the white list that has passed the authentication and successfully added to the white list database to the white list database in the business system, so as to ensure that the business system can not only realize the white list in the BOSS system Synchronized automatic update can also realize synchronous automatic update with the white list in the industry gateway. When the business system performs business operations on the target mobile phone number through the industry gateway, it can ensure that the white list library of the business system is selected to perform the target mobile phone number. Authentication is used to replace the accuracy of authentication when using the whitelist library of the industry gateway to authenticate the target mobile phone number.

In the embodiment of the whitelist management method, the new whitelist of the business system is synchronized to the BOSS system through the BOSS proxy server for synchronizing to the BOSS system through the database in the BOSS proxy server; Synchronizing to the business system by the BOSS proxy server is to synchronize to the business system by the database in the BOSS proxy server; The BOSS system synchronizes to the white list of the business system.

Wherein said business system will increase the white list by BOSS proxy server synchronously to the BOSS system and include: the business system will add the white list to the corresponding E2B folder of this business system in the database; BOSS proxy server will E2B folder The white list is synchronized to the BOSS system;

Wherein, the BOSS system synchronizing the white list passed through the authentication to the business system through the BOSS proxy server includes: the BOSS system returns the white list passed through the authentication to the B2E folder corresponding to the business system in the database; The white list in the folder is synchronized to the BOSS system.

The BOSS proxy server mentioned in the above-mentioned embodiments is specifically: a server deployed in a telecom operator’s intranet environment. The server implements an interface to the BOSS system and simultaneously implements an interface to an external network MAS system. The interface follows the requirements of the telecom operator. The relevant interface specification of the "white list" management mechanism. The following describes in detail (1) the function of the BOSS proxy server, (2) the specific construction method of the BOSS proxy server, and (2) taking the MAS business system as an example to control the "white list" of sending short messages for the MAS business.

(1) Functions of BOSS proxy server

Through the BOSS proxy server, the requirement of automatic synchronization of "white list" data from the MAS business system to the BOSS system is realized, and the problem that the BOSS system cannot provide an interface to the external network environment is also solved. The main functions of the BOSS proxy server include:

The MAS business system can submit "white list" files to the BOSS system through the BOSS proxy server;

The MAS business system can obtain the "white list" file sent by the BOSS system through the BOSS proxy server;

The BOSS system can obtain the "white list" file submitted by the MAS business system through the BOSS proxy server;

The BOSS system can send the "white list" file to the MAS business system to the EC/MAS through the BOSS proxy server;

Different MAS business systems have their own directory permissions. It is not possible to read and write files of other MAS to ensure data security.

(2) The specific construction method of the BOSS proxy server

Create an ftp server by "BOSS Proxy Server". Assign a user name and password to the BOSS system and each MAS business system. After the user information is created by the administrator, the MAS business operator will be notified manually. After each MAS business system logs in to the "BOSS proxy server" through ftp, you can view the Go to two folders dedicated to this MAS system - E2B folder and B2E folder. The E2B folder is used to store the files submitted by the MAS system to BOSS. The B2E folder is used to store files sent from the BOSS system to the MAS system.

The BOSS system and each MAS business system log in to the "BOSS Proxy Server" every 15 minutes, extract and upload the corresponding whitelist files in their respective directories.

"BOSS Proxy Server" extracts the "white list" file uploaded by MAS from the E2B directory of each MAS every 15 minutes, cuts it into the E2B directory of the BOSS system, and then extracts the BOSS system from the B2E directory of the BOSS system to return Cut the whitelist file for each MAS into the B2E directory of the corresponding MAS.

(3) "White list" control of sending text messages under MAS business:

After the MAS business system receives the "white list" through the "BOSS proxy server", when the business system sends a short message, it must first perform "white list" authentication on the mobile phone number sent. Its implementation method is to use the "white list" received from the "BOSS proxy server" as the address book of the business system. When the user sends a short message through the business system, he can only select the target mobile phone number from the address book. When a user wants to send a text message to a new target mobile phone number, he must go through the "white list" import process and add the new target mobile phone number to the system address book before he can send a text message to the new target mobile phone number. In this way, a large number of short messages with numbers other than the "white list" as the target mobile phone number are sent to the industry gateway for authentication, and the pressure on the "white list" authentication of the industry gateway is reduced.

Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: it can still be Modifications are made to the technical solutions described in the foregoing embodiments, or equivalent replacements are made to some of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the various embodiments of the present invention.

Claims (25)

1. a white list management system comprises the BOSS system that is used for the white list of operation system is carried out authentication, and one or several operation systems is characterized in that, also comprise:

The BOSS acting server is connected respectively with described operation system and described BOSS system, is used to receive the newly-increased white list that operation system is submitted to, and will described newly-increased white list synchronously to the BOSS system; And receive the white list that the BOSS system passes through after to described newly-increased white list authentication, and give operation system synchronously with the white list that described authentication is passed through;

The white list that described operation system is passed through described authentication joins the white list storehouse in this operation system.

2. system according to claim 1 is characterized in that, the white list that described BOSS system passes through after to newly-increased white list authentication meets the user terminal number that imposes a condition for the User Status in the BOSS system in the newly-increased white list.

3. system according to claim 1, it is characterized in that, described system also comprises the industry gateway, the described newly-increased white list User Status that is used for receiving from the BOSS system meets the user terminal number that imposes a condition, the user terminal number that receives is joined local white list storehouse corresponding to described operation system, and the white list that success is put in storage returns the system to BOSS;

The white list that described BOSS system will pass through as authentication from the white list of the successful warehouse-in of industry gateway is sent to the BOSS acting server.

4. according to the arbitrary described system of claim 1-3, it is characterized in that the white list storehouse of described operation system is used to deposit the scope of the target mobile phones number that can use described operation system visit.

5. according to the arbitrary described system of claim 1-3, it is characterized in that, described BOSS acting server comprises: database is used to store each operation system and gives the white list that passes through after the authentication of described each operation system to the newly-increased white list and the BOSS system synchronization of BOSS system synchronously.

6. system according to claim 5 is characterized in that, described database comprises: the subdata base corresponding with each operation system, the search index interface that is connected with each subdata base;

Comprise in each subdata base:

The E2B file is used to store the newly-increased white list that needs to give from this subdata base corresponding service system synchronization the BOSS system;

The B2E file, being used to store needs to give the white list that passes through after the authentication of this subdata base corresponding service system from the BOSS system synchronization;

The search index interface, the identifying information that is used for operation system is an index, and the need of this operation system correspondence of inquiry are given the newly-increased white list of BOSS system synchronously and need be given the white list that passes through after the authentication of this operation system from the BOSS system synchronization from this operation system from the subdata base of this operation system correspondence.

7. system according to claim 5 is characterized in that, described database comprises:

E2B folder database is used to store the newly-increased white list that needs to give synchronously from each operation system the BOSS system;

B2E folder database, being used to store needs to give the white list that passes through after the authentication of each operation system from the BOSS system synchronization;

The search index interface, be connected respectively with described B2E folder database with described E2B folder database, the identifying information that is used for operation system is an index, inquires about the need of this operation system correspondence and gives the newly-increased white list of BOSS system synchronously and need give the white list that passes through after the authentication of this operation system from the BOSS system synchronization from this operation system.

8. system according to claim 7, it is characterized in that, described database also comprises: operation system checking storehouse, be used for when operation system is given the BOSS system with the newly-increased white list of this operation system synchronously by the BOSS acting server, the BOSS acting server verifies whether the information of this operation system is correct, if correct, permission will increase white list newly synchronously to the E2B folder database in the newly-increased white list of this operation system correspondence; When the white list that also is used for passing through when authentication is given operation system synchronously by the BOSS acting server, whether the authentication information of verifying this operation system is correct, if correct, permission with the newly-increased white list of this operation system correspondence in the B2E folder database of this operation system correspondence synchronously to this operation system.

9. according to the arbitrary described system of claim 1-8, it is characterized in that described BOSS acting server comprises: the ftp server is used to provide BOSS system and each operation system to visit the interface of BOSS acting server by the ftp mode.

10. according to the arbitrary described system of claim 1-8, it is characterized in that described operation system is: the MAS operation system.

11. a white list management method is characterized in that, comprising:

Operation system will increase white list newly and give the BOSS system synchronously by the BOSS acting server;

The BOSS system carries out authentication to described newly-increased white list;

The BOSS system gives operation system with the white list that described authentication is passed through synchronously by the BOSS acting server;

The white list that operation system is passed through described authentication joins the white list storehouse in this operation system.

12. method according to claim 11 is characterized in that, the BOSS system carries out described newly-increased white list also comprising after the authentication:

The BOSS system gives the industry gateway synchronously with the white list that authentication is passed through;

Operation system is carried out business operation by the industry gateway to the target mobile phones number.

13. method according to claim 12 is characterized in that, operation system is carried out business operation by the industry gateway to the target mobile phones number and is comprised:

Operation system is carried out authentication according to the white list storehouse in this operation system to the target mobile phones number, carries out business operation by the target mobile phones number that the industry gateway passes through authentication.

14. method according to claim 12, it is characterized in that, the described white list that authentication is passed through also comprises after giving the industry gateway synchronously: the industry gateway receives and meets the user terminal number that imposes a condition from User Status in the described newly-increased white list of BOSS system, the user terminal number that receives is joined local white list storehouse corresponding to described operation system, will successfully put white list in storage and return system to BOSS;

The white list that described BOSS system passes through authentication by the BOSS acting server to operation system is synchronously: will from the successful warehouse-in of industry gateway the white list that passes through as authentication of white list give operation system synchronously by the BOSS acting server.

15., it is characterized in that the white list storehouse of described operation system is used to deposit the scope of the target mobile phones number that can use described operation system visit according to arbitrary described method among the claim 11-14.

16., it is characterized in that described operation system will increase white list newly and give the BOSS system for giving the BOSS system by the database synchronization in the BOSS acting server synchronously by the BOSS acting server according to arbitrary described method among the claim 11-14; The white list that described BOSS system passes through authentication is to give operation system by the database synchronization in the BOSS acting server synchronously to operation system by the BOSS acting server; Described database, being used to store needs to give the newly-increased white list of BOSS system synchronously and need give the white list that passes through after the authentication of each operation system from the BOSS system synchronization from each operation system.

17. method according to claim 16 is characterized in that,

Described operation system will increase white list newly and comprise for synchronously the BOSS system by the BOSS acting server:

Operation system will increase the E2B file that white list is committed to this operation system correspondence in the database newly;

The BOSS acting server is given the BOSS system synchronously with the newly-increased white list in the E2B file;

The white list that described BOSS system passes through authentication comprises to operation system synchronously by the BOSS acting server:

The white list that the BOSS system passes through authentication returns to the B2E file of this operation system correspondence in the database;

The BOSS acting server is given the BOSS system synchronously with the white list in the B2E file.

18. method according to claim 17 is characterized in that,

When described operation system will increase white list newly and be committed to the E2B file of this operation system correspondence in the database, also comprise: whether the authentication information of verifying this operation system is correct, if correct, permission will increase white list newly synchronously to the E2B file of this operation system correspondence;

The white list that described BOSS system passes through authentication also comprises when returning to the B2E file of this operation system correspondence in the database: whether the authentication information of verifying this operation system is correct, if correct, permission with the white list in the B2E file of this operation system correspondence synchronously to this operation system.

19., it is characterized in that BOSS system and each operation system are visited the BOSS acting server by the ftp mode according to the arbitrary described method of claim 11-14.

20., it is characterized in that described operation system is: the MAS operation system according to the arbitrary described method of claim 11-14.

21. a business operation support system proxy server is characterized in that, comprising:

Synchronization module is used to receive the newly-increased white list that operation system is submitted to, and gives the BOSS system synchronously with described newly-increased white list; And

Receive the white list that the BOSS system passes through after to described newly-increased white list authentication, and give operation system synchronously the white list that described authentication is passed through.

22. business operation support system proxy server according to claim 21 is characterized in that, described synchronization module comprises:

First synchronization module is used to receive the newly-increased white list that operation system is submitted to, and gives the BOSS system synchronously with described newly-increased white list;

Second synchronization module is used to receive the white list that the BOSS system passes through after to described newly-increased white list authentication, and gives operation system synchronously with the white list that described authentication is passed through.

23. business operation support system proxy server according to claim 22, it is characterized in that, described second synchronization module, receive the BOSS system to described newly-increased white list authentication by and successfully join white list in the white list storehouse of this operation system correspondence of the trade network Central Shanxi Plain, with authentication by and the white list that successfully joins in the white list storehouse of this operation system correspondence of the trade network Central Shanxi Plain give operation system synchronously.

24. business operation support system proxy server according to claim 21 is characterized in that, described business operation support system proxy server also comprises:

Database is connected with described synchronization module, and being used to store needs to give the newly-increased white list of BOSS system synchronously and need give the white list that passes through after the authentication of each operation system from the BOSS system synchronization from each operation system.

25. business operation support system proxy server according to claim 21, it is characterized in that, described business operation support system proxy server also comprises: the ftp server is used to provide BOSS system and each operation system to visit the interface of BOSS acting server by the ftp mode.

Images