CN104735103A - Method and device for managing distributed data and method and device for receiving distributed data - Google Patents

Abstract

The present invention relates to the field of communication technology, in particular to a method and device for managing and receiving distributed data, so as to solve the problem that different charging servers cannot share the resources of the charging servers in the existing distributed charging system. The resource utilization of each server is different, which leads to the problem that the resources of the accounting server in the accounting system cannot be effectively utilized. In the embodiment of the present invention, a sequence number is determined as the account identifier for the user identifier, a sequence number is assigned to each process, and the remainder obtained by dividing the sequence number of the account identifier by the total number of processes that can be run by all billing servers in the system is used as the remainder. The serial number of the process corresponding to the account ID; distribute all account IDs to each process approximately evenly, so that the number of users corresponding to each accounting server is approximately equal, realize rational use of accounting server resources in the system, and realize different accounting The load balancing between fee servers improves the resource utilization in the system.

Description

A method and device for managing and receiving distributed data

technical field

The invention relates to the field of communication technology, in particular to a method and device for managing and receiving distributed data.

Background technique

With the continuous improvement of people's living standards, the number of mobile communication users has increased rapidly year by year. How to process user consumption data in real time and quickly has attracted more and more attention from operators and users.

The billing processing method in the prior art is to configure a billing server for each city to perform billing according to the divided administrative cities in an administrative province. When the data server receives a piece of user data, it judges according to the user identification that the user data corresponds to the place where the user belongs, and sends the user data to the billing server corresponding to the place where the user belongs. The billing server corresponding to the place where the user belongs contains multiple storage spaces, and each storage space corresponds to a billing process; after receiving a piece of user data, the billing server determines the corresponding storage space according to the user data to perform billing processing. When the number of users in a city is large, or there are a lot of user data, the resources of the billing server corresponding to the city will be occupied at a high rate, or even insufficient resources; while the number of users in other cities is small , the resource utilization rate of the billing server corresponding to the city is low. In the existing billing processing method, different billing servers receive user data in different cities, and perform billing according to the billing strategy formulated by the city. When performing billing processing, these data need to be relied on for processing, so different The resources of the billing server cannot be shared.

Therefore, in the distributed charging system of the prior art, since the resources of the charging servers cannot be shared, resource utilization conditions of different charging servers are different, resulting in that the resources of the charging servers in the charging system cannot be effectively utilized.

Contents of the invention

The embodiment of the present invention provides a distributed data distribution and billing method and device to solve the problem of resource utilization of different billing servers in the distributed billing system of the prior art because the resources of the billing servers cannot be shared. The situation is different, resulting in the problem that the charging server resources in the charging system cannot be effectively utilized.

An embodiment of the present invention provides a method for distributing distributed data, the method comprising:

The data server receives the user data, and determines the corresponding account ID according to the user ID in the user data;

The data server determines the process of charging the user data according to the account identifier, determines the user identifier corresponding to the account identifier, and records the correspondence between the user identifier and the process;

The data server determines the billing server corresponding to the process, and sends the user data and the correspondence between the user ID and the process to the corresponding billing server;

Wherein the account identification is a serial number; the data server assigns a serial number to each process according to the total number of processes that all billing servers can run; the data server divides the account identification serial number by the process The remainder obtained from the total amount is used as the serial number of the process corresponding to the account identifier; the data server determines the billing server corresponding to the process according to the serial number of the process.

In the above embodiment, a sequence number is determined as the account identifier for the user ID of the user, a sequence number is assigned to each process, and the remainder obtained by dividing the sequence number of the account identifier by the total number of processes that can be run by all billing servers in the system As the serial number of the process corresponding to the account identifier; using the above method, all the accounts in the system are approximately evenly distributed to each process, so that the number of users corresponding to each accounting server is approximately equal, and the rational use of accounting in the system is realized. Billing server resources and load balancing between different billing servers are realized, which improves resource utilization in the system.

Further, the data server in the embodiment of the present invention determines the corresponding account identifier according to the user identifier in the user data, specifically including:

The data server pre-stores the corresponding relationship between the user ID and the account ID, and determines the account ID corresponding to the user ID in the user data according to the pre-stored corresponding relationship between the user ID and the account ID.

In the above embodiment, the data server pre-stores the correspondence between the user ID and the account ID, and after receiving the user data, determines the account ID corresponding to the user ID in the user data.

Embodiments of the present invention also include:

The data server changes the account ID corresponding to the user ID, determines the changed account ID corresponding to the user ID, and stores the corresponding relationship between the user ID and the changed account ID;

The data server determines the effective time of the corresponding relationship between the user ID and the changed account ID; before the effective time is reached, the data server determines that the user ID corresponds to the account ID before the change; when the effective time is reached, the data server determines the user ID Corresponding to the changed account ID.

In the above embodiment, the data server determines the effective time of the corresponding relationship between the user ID and the changed account ID, and determines when to determine the changed account ID based on the user ID according to the effective time. If the user changes the corresponding account this month, the data server will update the corresponding relationship between the user ID and the account ID immediately, but the original corresponding relationship between the user ID and the address of the storage space will still be used this month. The corresponding relationship between the ID and the changed account ID facilitates data monitoring of the account corresponding to the user.

In the embodiment of the present invention, the data server determines the corresponding account ID according to the user ID in the user data, specifically including:

The data server determines that the account identifier corresponding to the user identifier is not stored in the pre-stored correspondence between the user identifier and the account identifier, then the data server randomly generates a serial number, and uses the serial number as the account identifier corresponding to the user identifier .

In the above embodiment, when the user uses the user ID for the first time, the data server generates a serial number as an account, so as to determine the process of charging the user data according to the account ID.

Embodiments of the invention also include:

The data server determines that the number of billing servers has changed, re-determines the total number of processes that all billing servers can run, and reassigns a serial number to each process;

The data server divides the serial number of the account identifier by the total number of re-determined processes to obtain a remainder, and uses the remainder as the serial number of the updated process corresponding to the account identifier; the data server determines the process according to the serial number of the updated process Accounting server corresponding to this process.

In the above embodiment, after the billing system is expanded, the data server re-allocates accounts according to the total number of processes that the billing server can run after the billing, so that the servers in the billing system after the billing can achieve load balancing.

The embodiment of the present invention also provides a distributed data receiving method, the method comprising:

The billing server receives the user data sent by the data server and the corresponding relationship between the user ID and the process;

The billing server sends the user data to the process corresponding to the billing server according to the correspondence between the user identifier and the process;

The process of the charging server determines a corresponding charging rule according to the user identifier, and performs charging processing on the user data according to the determined charging rule.

In the above embodiment, the charging server determines the process for charging processing according to the correspondence between the user identifier and the process, and the process determines the charging rule for performing charging processing on user data according to the user identifier. Since all billing rules are stored in the process of the billing server, the user data can be billed according to the user ID of the received user data, avoiding that the billing server can only bill the user data in a fixed area The problem.

An embodiment of the present invention provides a distributed data management device, which includes:

The account identifier determination unit is configured to receive the user data, and determine the corresponding account identifier according to the user identifier in the user data;

The user data division unit is used to determine the process of charging the user data according to the account identifier, determine the user identifier corresponding to the account identifier, and record the corresponding relationship between the user identifier and the process;

The user data sending unit is configured to determine the billing server corresponding to the process, and send the user data and the correspondence between the user ID and the process to the corresponding billing server;

Wherein the account identification is a serial number; the user data division unit is also used for: assigning a serial number to each process according to the total number of processes that all billing servers can run; dividing the serial number of the account identification by the The remainder obtained from the total number of the above-mentioned processes is used as the serial number of the process corresponding to the account identifier; and the billing server corresponding to the process is determined according to the serial number of the process.

In the above embodiment, a sequence number is determined as the account identifier for the user ID of the user, a sequence number is assigned to each process, and the remainder obtained by dividing the sequence number of the account identifier by the total number of processes that can be run by all billing servers in the system As the serial number of the process corresponding to the account identifier; using the above method, all the accounts in the system are approximately evenly distributed to each process, so that the number of users corresponding to each accounting server is approximately equal, and the rational use of accounting in the system is realized. Billing server resources and load balancing between different billing servers are realized, which improves resource utilization in the system.

Further, the account identification determination unit described in the embodiment of the present invention is specifically used for:

The corresponding relationship between the user ID and the account ID is stored in advance, and the account ID corresponding to the user ID in the user data is determined according to the pre-stored corresponding relationship between the user ID and the account ID.

In the above embodiment, the data server pre-stores the correspondence between the user ID and the account ID, and after receiving the user data, determines the account ID corresponding to the user ID in the user data.

The account identification determination unit in the embodiment of the present invention is also used for:

Change the account ID corresponding to the user ID, determine the changed account ID corresponding to the user ID, store the corresponding relationship between the user ID and the changed account ID; determine the effectiveness of the corresponding relationship between the user ID and the changed account ID Time; before the effective time is reached, it is determined that the user ID corresponds to the account ID before the change; when the effective time is reached, it is determined that the user ID corresponds to the account ID after the change.

In the above embodiment, the data server determines the effective time of the corresponding relationship between the user ID and the changed account ID, and determines when to determine the changed account ID based on the user ID according to the effective time. If the user changes the corresponding account this month, the data server will update the corresponding relationship between the user ID and the account ID immediately, but the original corresponding relationship between the user ID and the address of the storage space will still be used this month. The corresponding relationship between the ID and the changed account ID facilitates data monitoring of the account corresponding to the user.

The account identification determination unit described in the embodiment of the present invention is specifically used for:

If it is determined that the account identifier corresponding to the user identifier is not stored in the pre-stored correspondence between the user identifier and the account identifier, a serial number is randomly generated, and the serial number is used as the account identifier corresponding to the user identifier.

In the above embodiment, when the user uses the user ID for the first time, the data server generates a serial number as an account, so as to determine the process of charging the user data according to the account ID.

The user data division unit described in the embodiment of the present invention is also used for:

Determine that the number of billing servers has changed, re-determine the total number of processes that all billing servers can run, and reassign a serial number to each process; divide the serial number of the account ID by the total number of re-determined processes to get a remainder, The remainder is used as the serial number of the updated process corresponding to the account identifier; and the billing server corresponding to the process is determined according to the serial number of the updated process.

In the above embodiment, after the billing system is expanded, the data server re-allocates accounts according to the total number of processes that the billing server can run after the billing, so that the servers in the billing system after the billing can achieve load balancing.

The embodiment of the present invention also provides a distributed data receiving device, which includes:

The data receiving unit is used to receive the user data sent by the data server and the corresponding relationship between the user identification and the process;

A data sending unit, configured to send user data to a process corresponding to the billing server according to the correspondence between the user identifier and the process;

The charging processing unit is configured to determine a corresponding charging rule according to the user identifier, and perform charging processing on the user data according to the determined charging rule.

In the above embodiment, the device determines the process for charging processing according to the correspondence between the user ID and the process, and the process determines the charging rule for charging user data according to the user ID. Since all billing rules are stored in the process of the device, user data can be billed according to the user ID of the received user data, avoiding the problem that the billing server can only bill user data in a fixed area .

In the embodiment of the present invention, a serial number is determined as the account identifier for the user ID of the user, a serial number is assigned to each process, and the serial number of the account identifier is divided by the total number of processes that can be run by all billing servers in the system to obtain The remainder is used as the sequence number of the process corresponding to the account identifier; using the above method, all accounts in the system are approximately evenly distributed to each process, so that the number of users corresponding to each billing server is approximately equal, and a reasonable utilization of the system is realized. Accounting server resources and load balancing between different accounting servers are realized, which improves resource utilization in the system.

Description of drawings

FIG. 1 is a schematic flow diagram of a method for managing distributed data in an embodiment of the present invention;

Fig. 2 is the schematic diagram of data migration in the embodiment of the present invention;

FIG. 3 is a schematic flowchart of a specific management method for distributed data in an embodiment of the present invention;

FIG. 4 is a schematic flowchart of a method for changing a process corresponding to a user ID in an embodiment of the present invention;

FIG. 5 is a schematic flowchart of a method for sending distributed data in an embodiment of the present invention;

FIG. 6 is a schematic flowchart of a method for receiving distributed data in an embodiment of the present invention;

FIG. 7 is a schematic diagram of a distributed data management device in an embodiment of the present invention;

FIG. 8 is a schematic diagram of a device for receiving distributed data in an embodiment of the present invention.

Detailed ways

The embodiment of the present invention provides a distributed data distribution and billing method and device. Since all accounts in the system are approximately evenly distributed to each process, the number of users corresponding to each billing server is approximately equal. Realize the reasonable use of the accounting server resources in the system, and realize the load balance between different accounting servers, and improve the resource utilization rate in the system.

Further description will be made below in conjunction with the accompanying drawings of the description.

As shown in Figure 1, it is a distributed data management method in the embodiment of the present invention, the method includes:

Step 101: The data server receives the user data, and determines the corresponding account ID according to the user ID in the user data;

Step 102: The data server determines the process of charging the user data according to the account ID, determines the user ID corresponding to the account ID, and records the correspondence between the user ID and the process;

Step 103: The data server determines the billing server corresponding to the process, and sends the user data and the correspondence between the user ID and the process to the corresponding billing server;

The account ID is a serial number; the data server assigns a serial number to each process according to the total number of processes that all accounting servers can run; the data server divides the serial number of the account ID by the total number of processes as the remainder. The serial number of the process corresponding to the account identifier; the data server determines the accounting server corresponding to the process according to the serial number of the process.

In step 101, the data server determines the corresponding account identifier according to the user identifier in the user data, specifically including:

The data server pre-stores the correspondence between the user ID and the account ID, and determines the account ID corresponding to the user ID in the user data according to the pre-stored correspondence between the user ID and the account ID. If the data server determines that the account ID corresponding to the user ID is not stored in the pre-stored correspondence between the user ID and the account ID, the data server randomly generates a serial number and uses the serial number as the account ID corresponding to the user ID.

Each user ID uniquely corresponds to an account ID, and each account ID corresponds to at least one user ID. The user ID is an ID uniquely corresponding to each terminal, for example, the phone number corresponding to a terminal can be used as a user ID; the data server can generate an account ID for a user ID. One account identifier can also correspond to multiple user identifiers. For example, for employees of a company, one terminal of each employee corresponds to one user identifier, and all user identifiers corresponding to all user terminals of all employees correspond to the same account identifier.

Preferably, step 101 also includes: the data server changes the account ID corresponding to the user ID, determines the changed account ID corresponding to the user ID, and stores the corresponding relationship between the user ID and the changed account ID; the data server determines the user The effective time of the corresponding relationship between the identifier and the changed account identifier; before the effective time is reached, the data server determines that the user identifier corresponds to the account identifier before the change; when the effective time is reached, the data server determines that the user identifier corresponds to the changed account identifier.

When the data server changes the account ID corresponding to the user ID, it also sets the effective time of the corresponding relationship between the user ID and the changed account ID, and the expiration time of the corresponding relationship between the user ID and the account ID before the change. The expiration time is abbreviated. Later than the effective time; before the effective time is reached, the data server determines that the user ID corresponds to the account ID before the change; after the effective time is reached, the data server determines that the user ID corresponds to the changed account ID, and simultaneously sends the user data to the account ID before the change The process corresponding to the account ID and the process corresponding to the changed account ID; when the expiration time is reached, the data server determines that the user ID corresponds to the changed account ID, and only sends the user data to the process corresponding to the changed account ID.

In step 102, the data server determines the process of charging the user data according to the account identifier, determines the user identifier corresponding to the account identifier, and records the corresponding relationship between the user identifier and the process, specifically including: the data server determines that all billing servers in the system The total number N of processes that can run, and assign a serial number to each process, the serial number is from 0 to N-1, where N is a positive integer; the data server determines the serial number of the account ID, and divides the serial number of the account ID by the process A remainder is obtained from the total number N, and the obtained remainder is used as the process corresponding to the account identifier, and the corresponding billing server is determined according to the number of the process. For example, there are 5 billing servers in the system, and there are 57 processes in total. The incoming program numbers of No. 1 billing server range from 0 to 11, the incoming program numbers of No. 24 to 35, the incoming program number of No. 4 billing server is from 36 to 47, and the incoming program number of No. 5 billing server is from 48 to 57. When the remainder corresponding to an account ID is 15, determine the number of the process corresponding to the account ID. The serial number is 15, and the process with the serial number 15 is located in the No. 2 billing server, then the billing server corresponding to the account ID is the No. 2 server; according to the user ID corresponding to the account ID, record the user ID and process corresponding to the account ID Correspondence between serial numbers. The number of processes running in each accounting server may be the same or different. The more processes that each accounting server can run, the better the scalability of the accounting system, but the processing capacity of each accounting server is limited. Therefore, the number of processes that each server can run depends on the current user's The quantity and processing capacity of the billing processor are determined.

In the embodiment of the present invention, the division method is preferably used to determine the process corresponding to each account ID. Other methods that can evenly distribute the account ID to each process are also applicable to the present invention, and will not be listed here.

Step 102 also includes: when the user ID changes the corresponding account ID, update the process corresponding to the user ID according to the account ID, and trigger the updated user ID and process when the corresponding relationship between the user ID and the changed account ID takes effect. The corresponding relationship between the user ID and the account ID before the change reaches the expiration time, triggering the invalidation of the corresponding relationship between the user ID and the process before the update; determine the user corresponding to the user ID in the original process corresponding to the user ID After all the data is processed, the user data corresponding to the user ID in the original process is migrated to the updated process.

Step 102 also includes: the data server determines that the number of accounting servers has changed, re-determines the total number of processes that all accounting servers can run, and redistributes a sequence number for each process; the data server divides the sequence number of the account identifier by the new A remainder is obtained from the determined total number of processes, and the remainder is used as the sequence number of the updated process corresponding to the account identifier; the data server determines the billing server corresponding to the process according to the sequence number of the updated process. The data server migrates the data in the pre-update process corresponding to the account identifier to the updated process corresponding to the account identifier.

Figure 2 is a schematic diagram of data migration in the embodiment of the present invention, where 21 is the storage space for storing user data corresponding to the user ID in the process before the change corresponding to the user ID, and 22 is the process after the change corresponding to the user ID The storage space for storing the user data corresponding to the user ID; T ₀ is the moment when the user ID changes the corresponding process, T ₁ is the effective time of the user ID and the changed process, and T ₂ is the invalidation time of the user ID and the process before the change ; 201 is the data migration preparation window, 202 is the data migration window, and 203 is the data cleaning window; at _T0 , the data server receives the information of the process corresponding to the user identification change, and prepares to transfer the user in the storage space MDB ₁ of the process before the change The user data corresponding to the identification is migrated. At this time, the data server still sends the user data to the process before the change; when the effective time T ₁ of the user ID and the process after the change is reached, the process before the change will store the data in the MDB ₁ The user data is migrated to _the storage space MDB ₂ of the changed process. At this time, the data server sends the user data to the process before the change and the process after the change at the same time; , the data server only sends the user data to the changed process at the same time, and cleans up the user data in the storage space MDB ₁ of the process before the change at the same time to complete the data migration.

As shown in Figure 3, it is a specific management method of distributed data in the embodiment of the present invention, the method includes:

Step 301: The data server randomly generates a serial number for the user ID as the account ID, and stores the corresponding relationship between the account ID and the user ID;

Step 302: the data server determines the total number of processes that all accounting servers can run, and assigns a serial number to each process;

Step 303: the data server determines the total amount of storage space included in the accounting server according to the amount of storage space divided by each accounting server;

Step 304: The data server divides the serial number of the account ID by the total number of processes to obtain the remainder as the serial number of the process corresponding to the account ID;

Step 305: the data server determines the corresponding billing server according to the sequence number of the process;

Step 306: The data server determines the corresponding relationship between the user ID and the process according to the corresponding relationship between the account ID and the user ID, and ends the process.

As shown in Figure 4, it is a method for changing the corresponding process of the user ID in the embodiment of the present invention, the method includes:

Step 401: The data server receives information about the account ID corresponding to the user ID change;

Step 402: The data server determines the changed account ID corresponding to the user ID;

Step 403: The data server sets the effective time of the changed account ID corresponding to the user ID, and the expiration time of the account ID before the change corresponding to the user ID;

Step 404: The data server determines the process corresponding to the changed account ID corresponding to the user ID; stores the corresponding relationship between the user ID and the changed process, and ends the process.

As shown in Figure 5, it is a method for sending distributed data in the embodiment of the present invention, the method includes:

Step 501: the data server receives user data;

Step 502: The data server judges whether the process corresponding to the user identifier in the user data has changed, if not, execute step 503, otherwise execute step 504;

Step 503: The data server sends the user data to the corresponding process according to the correspondence between the user ID and the process, and ends the process;

Step 504: The data server judges whether the effective time of the user ID and the changed process has been reached, if so, execute step 505, otherwise execute step 506;

Step 505: the data server sends the user data to the changed process, and ends the process;

Step 506: The data server sends the user data to the process before the change, and ends the process.

As shown in Figure 6, it is a distributed data receiving method in the embodiment of the present invention, the method includes:

Step 601: The billing server receives the user data sent by the data server and the corresponding relationship between the user ID and the process;

Step 602: The billing server sends the user data to the process corresponding to the billing server according to the correspondence between the user identifier and the process;

Step 603: The process of the charging server determines the corresponding charging rule according to the user identifier, and performs charging processing on the user data according to the determined charging rule.

Wherein in step 602, the billing server determines the process corresponding to the user ID according to the corresponding relationship between the user ID and the process stored in advance; the billing server receives the user data sent by the data server and the corresponding relationship between the user ID and the process, and determines the corresponding Process, send user data to the corresponding process.

In step 603, the process of the charging server determines the corresponding charging rule according to the user identification, and performs charging processing on the user data according to the determined charging rule; all charging rules are stored in each process, and according to the received user ID, determine the charging rule corresponding to the user ID, and perform charging processing on the received user data.

Based on the same inventive concept, an embodiment of the present invention also provides a distributed data management device. Since the problem-solving principle of the device is similar to a distributed data management method in the embodiment of the present invention, the implementation of the device can Refer to the implementation of the method, and the repetition will not be repeated.

As shown in Figure 7, it is a distributed data management device in the embodiment of the present invention, which includes:

An account identifier determining unit 701, configured to receive user data, and determine a corresponding account identifier according to the user identifier in the user data;

The user data division unit 702 is configured to determine the process of charging the user data according to the account identifier, determine the user identifier corresponding to the account identifier, and record the correspondence between the user identifier and the process;

The user data sending unit 703 is configured to determine the billing server corresponding to the process, and send the user data and the correspondence between the user ID and the process to the corresponding billing server;

Wherein the account identification is a serial number; the user data division unit 702 is also used for: according to the total number of processes that all charging servers can run, assign a serial number to each process; divide the serial number of the account identification by the process number The remainder obtained from the total amount is used as the serial number of the process corresponding to the account identifier; the billing server corresponding to the process is determined according to the serial number of the process.

The account identifier determining unit 701 is specifically configured to: pre-store the correspondence between the user identifier and the account identifier, and determine the account identifier corresponding to the user identifier in the user data according to the pre-stored correspondence between the user identifier and the account identifier. If it is determined that the account identifier corresponding to the user identifier is not stored in the pre-stored correspondence between the user identifier and the account identifier, a serial number is randomly generated and used as the account identifier corresponding to the user identifier.

Each user ID uniquely corresponds to an account ID, and each account ID corresponds to at least one user ID. The user ID is an ID uniquely corresponding to each terminal, for example, the phone number corresponding to a terminal can be used as a user ID; the data server can generate an account ID for a user ID. One account identifier can also correspond to multiple user identifiers. For example, for employees of a company, one terminal of each employee corresponds to one user identifier, and all user identifiers corresponding to all user terminals of all employees correspond to the same account identifier.

Preferably, the account identifier determining unit 701 is used to: change the account identifier corresponding to the user identifier, determine the changed account identifier corresponding to the user identifier, store the corresponding relationship between the user identifier and the changed account identifier; determine the user identifier The effective time of the corresponding relationship with the changed account ID; before the effective time is reached, it is determined that the user ID corresponds to the account ID before the change; when the effective time is reached, it is determined that the user ID corresponds to the changed account ID.

When changing the account ID corresponding to the user ID, at the same time set the effective time of the corresponding relationship between the user ID and the changed account ID, and the expiration time of the corresponding relationship between the user ID and the account ID before the change. The expiration time is slightly later than Effective time; before the effective time is reached, it is determined that the user ID corresponds to the account ID before the change; after the effective time is reached, it is determined that the user ID corresponds to the changed account ID, and the user data is simultaneously sent to the process corresponding to the account ID before the change and The process corresponding to the changed account ID; after the expiration time is reached, it is determined that the user ID corresponds to the changed account ID, and the user data is only sent to the process corresponding to the changed account ID.

The user data division unit 702 is specifically used for: the data server determines the total number N of processes that all accounting servers in the system can run, and assigns a serial number to each process, and the serial number is from 0 to N-1, wherein N is a positive integer; The data server determines the serial number of the account ID, divides the serial number of the account ID by the total number N of processes to obtain a remainder, uses the obtained remainder as the process corresponding to the account ID, and determines the corresponding billing server according to the process number. The number of processes running in each accounting server may be the same or different. The more processes that each accounting server can run, the better the scalability of the accounting system, but the processing capacity of each accounting server is limited. Therefore, the number of processes that each server can run depends on the current user's The quantity and processing capacity of the billing processor are determined.

In the embodiment of the present invention, the division method is preferably used to determine the process corresponding to each account ID. Other methods that can evenly distribute the account ID to each process are also applicable to the present invention, and will not be listed here.

The user data division unit 702 is also used for: when the user ID changes the corresponding account ID, update the process corresponding to the user ID according to the account ID, and trigger the updated user ID when the corresponding relationship between the user ID and the changed account ID takes effect. The corresponding relationship between the ID and the process takes effect; when the corresponding relationship between the user ID and the account ID before the change reaches the expiration time, the corresponding relationship between the user ID and the process before triggering the update becomes invalid; determine the corresponding user ID in the original process corresponding to the user ID After all the user data has been processed, the user data corresponding to the user ID in the original process is migrated to the updated process.

The user data division unit 702 is also used to: determine that the number of billing servers has changed, re-determine the total number of processes that all billing servers can run, and re-allocate a serial number for each process; divide the serial number of the account identifier by the newly determined A remainder is obtained from the total number of processes, and the remainder is used as the sequence number of the updated process corresponding to the account identifier; and the billing server corresponding to the process is determined according to the sequence number of the updated process. Migrate the data in the pre-update process corresponding to the account ID to the updated process corresponding to the account ID.

As shown in Figure 8, it is a distributed data receiving device in the embodiment of the present invention, which includes:

The data receiving unit 801 is configured to receive the user data sent by the data server and the corresponding relationship between the user ID and the process;

A data sending unit 802, configured to send user data to a process corresponding to the charging server according to the correspondence between the user identifier and the process;

The charging processing unit 803 is configured to determine a corresponding charging rule according to the user identifier, and perform charging processing on the user data according to the determined charging rule.

The data sending unit 802 is specifically configured to: determine the process corresponding to the user ID according to the pre-stored correspondence between the user ID and the process; receive the user data sent by the data server and the corresponding relationship between the user ID and the process, and determine the process corresponding to the user ID , to send user data to the corresponding process.

The billing processing unit 803 is specifically used for: the process of the billing server determines the corresponding billing rule according to the user identifier, and performs billing processing on the user data according to the determined billing rule; all billing rules are stored in each process , according to the received user ID, determine the charging rule corresponding to the user ID, and perform charging processing on the received user data.

Obviously, those skilled in the art can make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. Thus, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalent technologies, the present invention also intends to include these modifications and variations.

Claims (12)

1. a management method for distributed data, is characterized in that, the method comprises:

Data server receives user data, determines corresponding account identification according to the user ID in user data;

Described data server determines the process of this user data being carried out to charging process according to account identification, determines the user ID of account mark correspondence, the corresponding relation of record user identifications and process;

Described data server determines the accounting server that described process is corresponding, and described user data and user ID are sent to corresponding accounting server with the corresponding relation of process;

Wherein said account identification is a sequence number; The total quantity of the process that described data server can run according to whole accounting server is each course allocation sequence number; The remainder that the sequence number of account identification obtains divided by the total quantity of described process by described data server is as the sequence number of process corresponding to account mark; Described data server determines according to the sequence number of process the accounting server that this process is corresponding.

2. the method for claim 1, is characterized in that, described data server determines corresponding account identification according to the user ID in user data, specifically comprises:

Described data server prestores the corresponding relation of user ID and account identification, the account identification that the user ID determined in this user data according to the user ID prestored and the corresponding relation of account identification is corresponding.

3. method as claimed in claim 2, it is characterized in that, the method also comprises:

The account identification that described data server is corresponding to described user ID changes, and determines the account identification after the change that user ID is corresponding, the corresponding relation of the account identification after storing user ID and changing;

The entry-into-force time of the corresponding relation of described data server determination user ID and the account identification after changing; Before the received letter of acceptance time, the corresponding account identification before changing of described data server determination user ID; The received letter of acceptance time, the account identification after described data server determination user ID correspondence changes.

4. method as claimed in claim 2, is characterized in that, described data server determines corresponding account identification according to the user ID in user data, specifically comprises:

Described data server is determined not store account identification corresponding to this user ID in the corresponding relation of user ID and the account identification prestored, then described data server stochastic generation sequence number, using this sequence number as account identification corresponding to this user ID.

5. the method for claim 1, is characterized in that, the method also comprises:

The quantity of described data server determination accounting server changes, and redefines the total quantity of the process that whole accounting server can run, and is each course allocation sequence number again;

The sequence number of account identification is obtained a remainder divided by the total quantity of the process redefined by described data server, using the sequence number of this remainder as the process after renewal corresponding to account identification; Described data server determines according to the sequence number of the process after renewal the accounting server that this process is corresponding.

6. a method of reseptance for distributed data, is characterized in that, the method comprises:

Accounting server receives the user data of data server transmission and the corresponding relation of user ID and process;

User data is sent in process corresponding to accounting server according to user ID with the corresponding relation of process by described accounting server;

The process of described accounting server determines corresponding charging regulation according to user ID, carries out charging process according to the charging regulation determined to described user data.

7. a management devices for distributed data, is characterized in that, this device comprises:

Account identification determining unit, for receiving user data, determines corresponding account identification according to the user ID in user data;

User data division unit, for determining the process of this user data being carried out to charging process according to account identification, determines the user ID of account mark correspondence, the corresponding relation of record user identifications and process;

User data transmitting element, for determining the accounting server that described process is corresponding, is sent to corresponding accounting server by described user data and user ID with the corresponding relation of process;

Wherein said account identification is a sequence number; Described user data division unit also for: according to the total quantity of the process that whole accounting server can run, be each course allocation sequence number; The remainder obtained divided by the total quantity of described process by the sequence number of account identification is as the sequence number of process corresponding to account mark; The accounting server that this process is corresponding is determined according to the sequence number of process.

8. device as claimed in claim 7, is characterized in that, described account identification determining unit specifically for:

Prestore the corresponding relation of user ID and account identification, the account identification that the user ID determined in this user data according to the user ID prestored and the corresponding relation of account identification is corresponding.

9. device as claimed in claim 8, is characterized in that, described account identification determining unit also for:

The account identification corresponding to described user ID changes, and determines the account identification after the change that user ID is corresponding, the corresponding relation of the account identification after storing user ID and changing; The entry-into-force time of the corresponding relation of the account identification after determining user ID and changing; Before the received letter of acceptance time, determine the corresponding account identification before changing of user ID; The received letter of acceptance time, determine the account identification after the change of user ID correspondence.

10. device as claimed in claim 8, is characterized in that, described account identification determining unit specifically for:

Determine not store account identification corresponding to this user ID in the corresponding relation of user ID and the account identification prestored, then stochastic generation sequence number, using this sequence number as account identification corresponding to this user ID.

11. devices as claimed in claim 7, is characterized in that, described user data division unit also for:

Determining that the quantity of accounting server changes, redefine the total quantity of the process that whole accounting server can run, is each course allocation sequence number again; The sequence number of account identification is obtained a remainder divided by the total quantity of the process redefined, using the sequence number of this remainder as the process after renewal corresponding to account identification; Sequence number according to the process after renewal determines the accounting server that this process is corresponding.

The receiving system of 12. 1 kinds of distributed datas, is characterized in that, this device comprises:

Data receipt unit, for receiving the user data and the corresponding relation of user ID and process that data server sends;

Data transmission unit, for being sent in process corresponding to accounting server with the corresponding relation of process by user data according to user ID;

Charging processing unit, for determining corresponding charging regulation according to user ID, carries out charging process according to the charging regulation determined to described user data.