A flow splitting method, system and device

Abstract

The present invention discloses a diversion method, system and device. When a business processing request is received, if the business processing request includes a user's diversion identifier, the business processing is performed according to the business processing request. If the business processing request does not include the user's diversion identifier, the user's diversion identifier is determined based on the user's identity identifier and the currently used diversion rule table, and the diversion identifier is returned to the client. When the client initiates the business processing request again, it will carry the diversion identifier and send the business processing request to the data center corresponding to the diversion identifier. In the currently used diversion rule table, by using the administrative division code of the registered place of the enterprise as the diversion identifier of the enterprise or the enterprise's employees, and the administrative division code of the household registration place of the flexible employment personnel as the user's diversion identifier, the diversion identifier of the enterprise and the employees of the enterprise is made the same, thereby improving the disaster recovery capability and meeting the business processing demands of the enterprise, the enterprise employees and the flexible employment personnel.

Description

Technical Field

[0001] The present invention relates to the field of disaster recovery systems, and in particular to a traffic diversion method, system and device. Background Art

[0002] In the tax system, in order to improve the disaster recovery ability of the system, multiple data centers are usually set up. When some of the data centers fail, users can still handle business through other data centers. In order to avoid multiple data centers modifying the data of the same user, resulting in data inconsistency, it is necessary to divert users so that each data center can only modify the data of the users diverted to itself. The prior art usually diverts based on natural person identity or enterprise identity. The natural person identity includes employees of enterprises and flexible employees. If diverted based on natural person identity, when an enterprise handles business, since different employees are diverted to different data centers, a large number of cross-data center calls will be generated, resulting in performance degradation. And if some data centers fail, the business of all employees still cannot be handled, and the disaster recovery ability is low. While diverting based on enterprise identity as the diversion identifier cannot meet the handling requirements of flexible employees. Summary of the Invention

[0003] The purpose of the present invention is to provide a traffic diversion method, system and device, which will not cause cross-data center calls due to different employees being diverted to different data centers when an enterprise handles business on behalf of its employees, resulting in system performance degradation, improving the disaster recovery ability, and at the same time meeting the business handling requirements of enterprises, enterprise employees and flexible employees.

[0004] To solve the above technical problems, the present invention provides a traffic diversion method, which is applied to a data center in an application system. The traffic diversion method includes:

[0005] S11: When receiving a service handling request sent by a client, determine whether the service handling request includes a user's diversion identifier. If so, enter S13; if not, enter S12;

[0006] S12: Obtain the user's identity identifier, determine the user's diversion identifier based on the user's identity identifier and the currently used diversion rule table, and return the diversion identifier to the client so that the client can carry the diversion identifier when sending the service handling request and send the service handling request to the data center corresponding to the diversion identifier, and return to S11; the rules of the currently used diversion rule table include that when the user is an enterprise or an employee of the enterprise, the administrative division code of the enterprise's registration place is used as the user's diversion identifier; when the user is a flexible employee, the administrative division code of the household registration place of the flexible employee is used as the user's diversion identifier;

[0007] S13: Conduct business processing according to the said business processing request.

[0008] Preferably, obtaining the identity identifier of the said user includes:

[0009] Judge whether the said user has logged in to the said client;

[0010] If so, obtain the identity identifier of the said user according to the said user's login information;

[0011] If not, prompt the said user to log in to the said client and return to the step of judging whether the said user has logged in to the said client.

[0012] Preferably, it further includes:

[0013] S31: When obtaining the update permission, read the employment relationship table of natural persons and enterprises and the said currently used diversion rule table. The employment relationship table of natural persons and enterprises includes the employees of the said enterprise and the employment relationship of the said enterprise, the administrative division code of the registered place of the said enterprise, and the administrative division code of the household registration place of the said flexible employees;

[0014] S32: Judge whether the diversion identifiers of the enterprises, employees of the enterprises, and flexible employees in the said currently used diversion rule table are all the same as the administrative division codes of the registered place of the enterprise, the registered place of the enterprise where the employees of the enterprise work, and the household registration place of the flexible employees recorded in the employment relationship table of natural persons and enterprises. If they are not all the same, enter S33; if they are all the same, enter S31;

[0015] S33: Determine the administrative division codes of the registered place of the enterprise to be changed, the registered place of the enterprise where the employees of the enterprise work, and the household registration place of the flexible employees. The administrative division codes of the registered place of the enterprise to be changed, the registered place of the enterprise where the employees of the enterprise work, and the household registration place of the flexible employees refer to the administrative division codes of the registered place of the enterprise, the registered place of the enterprise where the employees of the enterprise work, and the household registration place of the flexible employees recorded in the employment relationship table of natural persons and enterprises that are different from the diversion identifiers of the enterprises, employees of the enterprises, and flexible employees recorded in the said currently used diversion rule table;

[0016] S34: Judge whether the ratio of the total number of the administrative division codes of the registered place of the enterprise to be changed, the registered place of the enterprise where the employees of the enterprise work, and the household registration place of the flexible employees to the total number of the diversion identifiers of the enterprises, employees of the enterprises, and flexible employees recorded in the said currently used diversion rule table reaches a preset ratio. If so, enter S35;

[0017] S35: Update the diversion identifier of the records in the currently used diversion rule table based on the administrative division codes of the registered address of the enterprise with the change, the registered address of the enterprises where the employees of the enterprise work, and the household registration place of the flexible employees, and synchronize the updated diversion rule table to other data centers in the application system.

[0018] Preferably, updating the diversion identifier of the records in the currently used diversion rule table based on the administrative division codes of the registered address of the enterprise with the change, the registered address of the enterprises where the employees of the enterprise work, and the household registration place of the flexible employees, and synchronizing the updated diversion rule table to other data centers in the application system includes:

[0019] When updating the currently used diversion rule table and synchronizing the updated diversion rule table to other data centers in the application system, divert the business handling requests received during the update period to the designated data center;

[0020] Update the administrative division codes of the registered address of the enterprise with the change, the registered address of the enterprises where the employees of the enterprise work, and the household registration place of the flexible employees as the diversion identifiers of the enterprise with the change, the employees of the enterprise, and the flexible employees to the currently used diversion rule table;

[0021] Synchronize the updated diversion rule table to other data centers in the application system, and end the update after the synchronization is completed.

[0022] Preferably, when the number of diversion rule tables is 2, updating the diversion identifier of the records in the currently used diversion rule table based on the administrative division codes of the registered address of the enterprise with the change, the registered address of the enterprises where the employees of the enterprise work, and the household registration place of the flexible employees, and synchronizing the updated diversion rule table to other data centers in the application system includes:

[0023] Empty the currently unused diversion rule table;

[0024] Write the administrative division codes of the registered address of the enterprise with the change, the registered address of the enterprises where the employees of the enterprise work, and the household registration place of the flexible employees as the diversion identifiers of the enterprise with the change, the employees of the enterprise, and the flexible employees into the currently unused diversion rule table;

[0025] Write the diversion identifiers in the currently used diversion rule table that are the same as the administrative division codes of the registered address of the enterprises, the enterprises where the employees of the enterprise work, and the household registration place of the flexible employees recorded in the natural person and enterprise employment relationship table into the currently unused diversion rule table;

[0026] Use the currently used traffic splitting rule table as the new unused traffic splitting rule table, and use the currently unused traffic splitting rule table as the new currently used traffic splitting rule table;

[0027] Synchronize the new currently used traffic splitting rule table to other data centers in the application system, and end the update after synchronization is completed;

[0028] When using the currently used traffic splitting rule table as the new unused traffic splitting rule table, using the currently unused traffic splitting rule table as the new currently used traffic splitting rule table, and synchronizing the new currently used traffic splitting rule table to other data centers in the application system, split the received business processing request to the designated data center.

[0029] Preferably, update the traffic splitting identifier of the records in the currently used traffic splitting rule table based on the administrative division codes of the registered address of the changed enterprise, the registered address of the enterprises where the employees of the enterprise work, and the household registration address of the flexible employees, including:

[0030] During the business off-peak period, update the traffic splitting identifier of the records in the currently used traffic splitting rule table based on the administrative division codes of the registered address of the changed enterprise, the registered address of the enterprises where the employees of the enterprise work, and the household registration address of the flexible employees.

[0031] Preferably, when receiving a business processing request sent by the client, it further includes:

[0032] Judge whether the business processing request includes the rule identifier of the user; wherein, the rule identifier is used to represent the traffic splitting rule table to which the traffic splitting identifier belongs when the client stores the traffic splitting identifier, and the rule identifiers of different traffic splitting rule tables are different;

[0033] If it includes the rule identifier of the user, judge whether the traffic splitting rule table corresponding to the rule identifier is consistent with the currently used traffic splitting rule table;

[0034] If they are consistent, enter S13;

[0035] If they are inconsistent, enter S12;

[0036] If it does not include the rule identifier of the user, then enter S12;

[0037] After determining the traffic splitting identifier of the user based on the identity identifier of the user and the currently used traffic splitting rule table, it further includes:

[0038] Return the rule identifier corresponding to the currently used traffic splitting rule table to the client so that the client can carry the rule identifier when sending the business processing request.

[0039] Preferably, before determining the traffic splitting identifier of the user based on the identity identifier of the user and the currently used traffic splitting rule table, it further includes:

[0040] Determine whether the identity identifier of the user is included in the currently used traffic splitting rule table;

[0041] If so, enter the step of determining the traffic splitting identifier of the user based on the identity identifier of the user and the currently used traffic splitting rule table;

[0042] If not, split the service handling request to a specified data center.

[0043] The present invention also provides a traffic splitting system, including:

[0044] A traffic splitting identifier determination unit, configured to, when receiving a service handling request sent by a client, determine whether the service handling request includes a traffic splitting identifier of a user. If so, trigger a service handling unit; if not, trigger a traffic splitting identifier determination unit;

[0045] The traffic splitting identifier determination unit is configured to obtain the identity identifier of the user, determine the traffic splitting identifier of the user based on the identity identifier of the user and the currently used traffic splitting rule table, and return the traffic splitting identifier to the client so that the client carries the traffic splitting identifier when sending the service handling request and sends the service handling request to a data center corresponding to the traffic splitting identifier, and trigger the traffic splitting identifier determination unit; wherein, the currently used traffic splitting rule table includes, when the user is an enterprise or an employee of the enterprise, using the administrative division code of the registration place of the enterprise as the traffic splitting identifier of the user; when the user is a flexible employee, using the administrative division code of the household registration place of the flexible employee as the traffic splitting identifier of the user;

[0046] A service handling unit, configured to handle a service according to the service handling request.

[0047] The present invention also provides a traffic splitting device, including:

[0048] A memory, configured to store a computer program;

[0049] A processor, configured to implement the steps of the above-mentioned traffic splitting method as claimed in the claims when executing the computer program.

[0050] The present invention provides a diversion method and related components. When a business processing request is received, if the business processing request includes a user's diversion identifier, the business processing is performed according to the business processing request. If the business processing request does not include the user's diversion identifier, the diversion identifier of the user is determined based on the user's identity identifier and the currently used diversion rule table, and the diversion identifier is returned to the client. When the client initiates the business processing request again, it will carry the diversion identifier and send the business processing request to the data center corresponding to the diversion identifier. In the diversion rule table currently used, when the user is an enterprise or an employee of the enterprise, the administrative division code of the enterprise's registered place is used as the user's diversion identifier; when the user is a flexible employment person, the administrative division code of the household registration place of the flexible employment person is used as the user's diversion identifier. The diversion identifier of the enterprise and the employee of the enterprise is the same. When the enterprise handles business for employees, cross-data center calls will not be generated due to different employees being diverted to different data centers, resulting in a decrease in system performance, improving disaster recovery capabilities, and also meeting the business processing demands of enterprises, enterprise employees and flexible employment personnel. BRIEF DESCRIPTION OF THE DRAWINGS

[0051] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the prior art and the drawings required for use in the embodiments are briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0052] Figure 1 A flow chart of a diversion method provided by the present invention;

[0053] Figure 2 A schematic structural diagram of a flow diversion system provided by the present invention;

[0054] Figure 3 A schematic structural diagram of a flow diversion device provided by the present invention. DETAILED DESCRIPTION

[0055] The core of the present invention is to provide a diversion method, system and equipment. When an enterprise handles business for its employees, cross-data center calls will not be generated due to different employees being diverted to different data centers, causing system performance to decline, thereby improving disaster recovery capabilities and meeting the business handling demands of enterprises, their employees and flexible employment personnel.

[0056] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are some, but not all, of the embodiments of the present invention. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention.

[0057] The shunting method is applied to a data center in an application system. The shunting method includes:

[0058] S11: When receiving a service handling request sent by a client, determine whether the service handling request includes a shunting identifier of the user. If so, proceed to S13; if not, proceed to S12.

[0059] S12: Obtain the identity identifier of the user, determine the shunting identifier of the user based on the identity identifier of the user and the currently used shunting rule table, and return the shunting identifier to the client so that the client can carry the shunting identifier when sending a service handling request and send the service handling request to the data center corresponding to the shunting identifier, then return to S11. The rules of the currently used shunting rule table include: when the user is an enterprise or an employee of an enterprise, use the administrative division code of the enterprise's registration place as the shunting identifier of the user; when the user is a flexible employee, use the administrative division code of the household registration place of the flexible employee as the shunting identifier.

[0060] S13: Handle the service according to the service handling request.

[0061] For details, please refer to Figure 1 , Figure 1 which is a flowchart of a shunting method provided by the present invention.

[0062] To improve the disaster tolerance of the application system and at the same time meet the service handling requirements of enterprise employees and flexible employees, in this embodiment, when the service handling request initiated by the user from the client does not carry the shunting identifier of the user, the data center will return the shunting identifier of the user to the client based on the currently used shunting rule table, so that the client can connect to the data center corresponding to the shunting identifier. The rules in the currently used shunting rule table include that enterprises and their employees have the same shunting identifier, while flexible employees also have a separate shunting identifier.

[0063] It should be noted that when a user initiates a business processing request from the client, if the user is processing a business through the client for the first time, the client does not store the user's diversion identifier, and the business processing request initiated by the client will not include the user's diversion identifier. The client will connect to the preset data center according to the preset configuration. The data center is not necessarily the data center corresponding to the user's diversion identifier. Therefore, the user cannot directly process the business in the data center, otherwise it may cause the user's data to be modified in multiple data centers, resulting in data inconsistency. For example, when the enterprise first processes a business for an employee, it connects to the Shanghai data center, and the employee connects to the Beijing data center when processing the business and the data center corresponding to the employee's diversion identifier is the Beijing data center. If the employee processes the business in the Beijing data center, and the enterprise processes the business for the employee in the Shanghai data center, the employee's data will be modified in both data centers, resulting in data inconsistency. Therefore, the user should only process the business in the data center corresponding to its diversion identifier. If the user is not processing the business through the client for the first time, the user's diversion identifier will be stored in the client, and the business processing request initiated by the user from the client will carry the diversion identifier. The client will connect to the data center corresponding to the diversion identifier according to the diversion identifier.

[0064] Specifically, when the data center receives a business processing request initiated by a user from a client, the data center will determine whether the business processing request includes a diversion identifier. If the business processing request includes a diversion identifier, it means that the client has been connected to the data center corresponding to the user's diversion identifier, and the data center will perform business processing according to the business processing request; if the business processing request does not include a diversion identifier, the data center will obtain the user's identity identifier, determine the user's diversion identifier based on the user's identity identifier and the currently used diversion rule table, and return the diversion identifier to the client. The rules of the currently used diversion rule table include that when the user is an enterprise or an employee of the enterprise, the administrative division code of the enterprise's registered place is used as the user's diversion identifier; when the user is a flexible employment personnel, the administrative division code of the household registration place of the flexible employment personnel is used as the user's diversion identifier. When the user sends a business processing request again through the client, the diversion identifier will be carried and the business processing request will be sent to the data center corresponding to the diversion identifier. When the diversion identifier is returned to the client, the diversion identifier can be, but is not limited to, stored in the client Cookie. In addition, if an employee of an enterprise is employed in multiple enterprises at the same time, the enterprise last reported to the data center in the currently used diversion rule table will be used as the employee's employment enterprise.

[0065] In summary, in this embodiment, by using the administrative division code of the registered location of the enterprise as the shunt identifier for the enterprise and its employees, the shunt identifiers of the enterprise and its employees are the same. When the enterprise handles business on behalf of its employees, cross-data center calls will not occur due to different employees being shunted to different data centers, which may cause a decline in system performance. This improves the disaster tolerance ability. At the same time, the administrative division code of the household registration location of flexible employees is used as the shunt identifier for flexible employees, meeting the business handling requirements of enterprises, enterprise employees, and flexible employees.

[0066] Based on the above embodiment:

[0067] As a preferred embodiment, obtaining the identity identifier of the user includes:

[0068] Determine whether the user has logged in to the client;

[0069] If so, obtain the identity identifier of the user according to the user's login information;

[0070] If not, prompt the user to log in to the client and return to the step of determining whether the user has logged in to the client.

[0071] Considering that some services can be handled without the user logging in, when the data center receives a service handling request, the user may not have logged in to the client yet. If the service handling request does not include a shunt identifier, the data center needs to obtain the identity identifier of the user. Since obtaining the identity identifier of the user requires the user to log in to the client, in this embodiment, the data center will determine whether the user has logged in to the client. If so, it will obtain the identity identifier of the user based on the user's login information. If the user has not logged in, it will prompt the user to log in to the client and return to the step of determining whether the user has logged in to the client.

[0072] As a preferred embodiment, it further includes:

[0073] S31: When obtaining the update permission, read the employment relationship table of natural persons and enterprises and the currently used shunt rule table. The employment relationship table of natural persons and enterprises includes the employment relationship between the employees of the enterprise and the enterprise, the administrative division code of the registered location of the enterprise, and the administrative division code of the household registration location of flexible employees;

[0074] S32: Determine whether the shunt identifiers of the enterprise, the employees of the enterprise, and flexible employees in the currently used shunt rule table are the same as the administrative division codes of the registered location of the enterprise, the registered location of the enterprise where the employees of the enterprise are employed, and the household registration location of flexible employees recorded in the employment relationship table of natural persons and enterprises. If they are not the same, enter S33; if they are the same, enter S31;

[0075] S33: Determine the administrative division codes of the registered address of the enterprise with changes, the registered addresses of the enterprises where the employees of the enterprise work, and the household registration addresses of the flexible employees. The administrative division codes of the registered address of the enterprise with changes, the registered addresses of the enterprises where the employees of the enterprise work, and the household registration addresses of the flexible employees refer to the administrative division codes of the registered address of the enterprise, the registered addresses of the enterprises where the employees of the enterprise work, and the household registration addresses of the flexible employees that are different from the diversion identifiers of the enterprises, the employees of the enterprises, and the flexible employees recorded in the currently used diversion rule table in the natural person and enterprise employment relationship table;

[0076] S34: Determine whether the ratio of the total number of the administrative division codes of the registered address of the enterprise with changes, the registered addresses of the enterprises where the employees of the enterprise work, and the household registration addresses of the flexible employees to the total number of the diversion identifiers of the enterprises, the employees of the enterprises, and the flexible employees recorded in the currently used diversion rule table reaches a preset ratio. If so, proceed to S35;

[0077] S35: Update the diversion identifiers recorded in the currently used diversion rule table based on the administrative division codes of the registered address of the enterprise with changes, the registered addresses of the enterprises where the employees of the enterprise work, and the household registration addresses of the flexible employees, and synchronize the updated diversion rule table to other data centers in the application system.

[0078] Considering the mobility issues of employees leaving or joining the enterprise, the employment relationship between the employees and the enterprise may change over time. Therefore, it is necessary to update the diversion identifiers in the currently used diversion rule table. However, it is too wasteful of the processing capacity of the data center to update when only the diversion identifiers of individual enterprises and employees need to be changed. In this embodiment, it is determined whether an update is required by comparing whether the ratio of the enterprises, the employees of the enterprises, and the administrative division codes of the household registration addresses of the flexible employees with different diversion identifiers recorded in the currently used diversion rule table to those recorded in the natural person and enterprise employment relationship table reaches a preset ratio. After reaching the preset ratio, the currently used diversion rule table is updated.

[0079] Specifically, when the data center obtains the update permission, it will read the administrative division codes of the registered addresses of the enterprises recorded in the natural person and enterprise employment relationship table, the registered addresses of the enterprises where the employees of the enterprises work, and the household registration addresses of the flexible employees. Then, it will determine whether the diversion identifiers of the enterprises, the employees of the enterprises, and the flexible employees recorded in the currently used diversion rule table are the same as the administrative division codes of the registered addresses of the enterprises recorded in the natural person and enterprise employment relationship table, the registered addresses of the enterprises where the employees of the enterprises work, and the household registration addresses of the flexible employees. If they are all the same, it means that the diversion identifiers in the currently used diversion rule table do not need to be updated, and S31 is returned. If they are not all the same, the data center will determine the administrative division codes of the registered addresses of the enterprises that have changed, the registered addresses of the enterprises where the employees of the enterprises work, and the household registration addresses of the flexible employees, and determine whether the ratio of the total number of the administrative division codes of the registered addresses of the enterprises that have changed, the registered addresses of the enterprises where the employees of the enterprises work, and the household registration addresses of the flexible employees to the total number of the diversion identifiers of the enterprises, the employees of the enterprises, and the flexible employees recorded in the currently used diversion rule table reaches a preset ratio, such as 10%. If the preset ratio is not reached, it means that the total number of the registered addresses of the enterprises that have changed, the registered addresses of the enterprises where the employees of the enterprises work, and the household registration addresses of the flexible employees is small and does not need to be updated, and S31 is returned. If the preset ratio is reached, it means that the total number of the registered addresses of the enterprises that have changed, the registered addresses of the enterprises where the employees of the enterprises work, and the household registration addresses of the flexible employees is large. The data center that has obtained the update permission will update the diversion identifiers recorded in the currently used diversion rule table based on the administrative division codes of the registered addresses of the enterprises that have changed, the registered addresses of the enterprises where the employees of the enterprises work, and the household registration addresses of the flexible employees, and synchronize the updated diversion rule table to other data centers in the application system. The registered addresses of the enterprises that have changed, the registered addresses of the enterprises where the employees of the enterprises work, and the household registration addresses of the flexible employees here include, but are not limited to, the changes in the registered addresses due to the relocation of the enterprises, the changes in the enterprises where the employees work due to the employment or resignation of the enterprise employees, and the changes in the household registration addresses due to the household registration migration of the flexible employees.

[0080] In addition, the update permission here can be periodically opened to any data center. For example, the update permission is opened to the Beijing data center every day or every month, and after the update is completed in the Beijing data center, the updated diversion rule table is synchronized to other data centers in the application system.

[0081] It should also be noted that when determining the administrative division codes of the registered addresses of the enterprises undergoing changes, the registered addresses of the enterprises where the employees of the enterprises work, and the household registration addresses of the flexible employees, in order to facilitate the subsequent update of the currently used traffic diversion rule table, it is possible but not limited to store the administrative division codes of the registered addresses of the enterprises undergoing changes, the registered addresses of the enterprises where the employees of the enterprises work, and the household registration addresses of the flexible employees by creating a temporary traffic diversion rule change table, and delete the traffic diversion rule change table after the update is completed or it is determined that no update is required.

[0082] In summary, in this embodiment, when the data center obtains the update permission, it determines whether it is necessary to update the currently used traffic diversion rule table by judging whether the total number of the registered addresses of the enterprises undergoing changes, the registered addresses of the enterprises where the employees of the enterprises work, and the household registration addresses of the flexible employees reaches a preset ratio. After the update of the currently used traffic diversion rule table is completed, the updated traffic diversion rule table is synchronized to other data centers in the application system, ensuring the real-time nature of the traffic diversion identifiers in the traffic diversion rule table.

[0083] As a preferred embodiment, based on the administrative division codes of the registered addresses of the enterprises undergoing changes, the registered addresses of the enterprises where the employees of the enterprises work, and the household registration addresses of the flexible employees, the traffic diversion identifiers of the records in the currently used traffic diversion rule table are updated, and the updated traffic diversion rule table is synchronized to other data centers in the application system, including:

[0084] When updating the currently used traffic diversion rule table and synchronizing the updated traffic diversion rule table to other data centers in the application system, the business handling requests received during the update time period are diverted to the designated data center;

[0085] The administrative division codes of the registered addresses of the enterprises undergoing changes, the registered addresses of the enterprises where the employees of the enterprises work, and the household registration addresses of the flexible employees are updated as the traffic diversion identifiers of the enterprises undergoing changes, the employees of the enterprises, and the flexible employees in the currently used traffic diversion rule table;

[0086] The updated traffic diversion rule table is synchronized to other data centers in the application system, and the update ends after the synchronization is completed.

[0087] When the existing technology updates the currently used traffic diversion rule table, the data center stops handling services for the update. Considering that the time for updating the traffic diversion identifiers of the records in the currently used traffic diversion rule table is relatively long, if the service handling is stopped, it may cause the user's services to not be handled in a timely manner. To solve the above problems, in this embodiment, when updating the currently used traffic diversion rule table and synchronizing the updated traffic diversion rule table to other data centers in the application system, the service handling requests initiated by users from the client will not be diverted to the data center corresponding to the traffic diversion identifier for handling. The data center diverts the service handling requests received during the update period to a designated data center. The data center that obtains the update permission updates the administrative division codes of the registered addresses of the changed enterprises, the registered addresses of the enterprises where the employees of the enterprises work, and the household registration addresses of the flexible employees as the traffic diversion identifiers of the changed enterprises, enterprise employees, and flexible employees to the currently used traffic diversion rule table and synchronizes the updated traffic diversion rule table to other data centers in the application system, and ends the update after the synchronization is completed. After the update is completed, the service handling requests initiated by users from the client will be diverted to the data center corresponding to the traffic diversion identifier for handling.

[0088] In summary, in this embodiment, by diverting the service handling requests to a designated data center when updating the currently used traffic diversion rule table, the data center can be updated without stopping handling services, ensuring that the user's services can be handled in a timely manner.

[0089] As a preferred embodiment, when the number of traffic diversion rule tables is 2, updating the traffic diversion identifiers of the records in the currently used traffic diversion rule table based on the administrative division codes of the registered addresses of the changed enterprises, the registered addresses of the enterprises where the employees of the enterprises work, and the household registration addresses of the flexible employees, and synchronizing the updated traffic diversion rule table to other data centers in the application system, includes:

[0090] Empty the currently unused traffic diversion rule table;

[0091] Write the administrative division codes of the registered addresses of the changed enterprises, the registered addresses of the enterprises where the employees of the enterprises work, and the household registration addresses of the flexible employees as the traffic diversion identifiers of the changed enterprises, enterprise employees, and flexible employees into the currently unused traffic diversion rule table;

[0092] Write the traffic diversion identifiers in the currently used traffic diversion rule table that are the same as the administrative division codes of the registered addresses of the enterprises, the registered addresses of the enterprises where the employees of the enterprises work, and the household registration addresses of the flexible employees recorded in the natural person and enterprise employment relationship table into the currently unused traffic diversion rule table;

[0093] Use the currently used traffic diversion rule table as the new currently unused traffic diversion rule table, and use the currently unused traffic diversion rule table as the new currently used traffic diversion rule table;

[0094] Synchronize the new currently used traffic diversion rule table to other data centers in the application system, and end the update after synchronization is completed;

[0095] When using the currently used traffic diversion rule table as the new currently unused traffic diversion rule table, using the currently unused traffic diversion rule table as the new currently used traffic diversion rule table, and synchronizing the new currently used traffic diversion rule table to other data centers in the application system, divert the received service handling requests to the specified data center.

[0096] Considering that if only one traffic diversion rule table is set, during the update, it is necessary to first divert the received service handling requests to the specified data center, then update the traffic diversion identifier of the user in the currently used traffic diversion rule table, and then synchronize it to other data centers, causing the received service handling requests to be diverted to the specified data center for a long time, putting pressure on the processing capacity of the specified data center and causing system failures. To solve the above problems, in this embodiment, the number of traffic diversion rule tables is 2. During the update, the data center first updates the traffic diversion identifier in the currently unused traffic diversion rule table, and after completion, diverts the received service handling requests to the specified data center, enables the currently unused traffic diversion rule table, and completes the update after synchronizing the data to other data centers.

[0097] Specifically, during the update, since the currently unused shunt rule table stores the previously saved shunt identifiers, directly editing the currently unused shunt rule table may cause data chaos. Therefore, it is necessary to empty the currently unused shunt rule table, and write the administrative division codes of the registered addresses of the changed enterprises, the registered addresses of the enterprises where the employees of the enterprises work, and the household registration addresses of the flexible employees as the shunt identifiers of the changed enterprises, the employees of the enterprises, and the flexible employees into the currently unused shunt rule table; write the shunt identifiers in the currently used shunt rule table that are the same as the administrative division codes of the registered addresses of the enterprises, the registered addresses of the enterprises where the employees of the enterprises work, and the household registration addresses of the flexible employees recorded in the natural person and enterprise employment relationship table into the currently unused shunt rule table, so that the currently unused shunt rule table includes the new shunt identifiers of the enterprises, the employees of the enterprises, and the flexible employees recorded in the natural person and enterprise employment relationship table. Then, use the currently used shunt rule table as the new currently unused shunt rule table, use the currently unused shunt rule table as the new currently used shunt rule table, and complete the update after synchronizing the data to other data centers. And only when using the currently used shunt rule table as the new currently unused shunt rule table, using the currently unused shunt rule table as the new currently used shunt rule table and synchronizing the data to other data centers, shunt the received business processing requests to the designated data center.

[0098] In summary, by setting up two shunt rule tables, when updating the currently unused shunt rule table, it is not necessary to shunt the business processing requests to the designated data center. Only when switching between the currently unused shunt rule table and the currently used shunt rule table and synchronizing the data to other data centers, shunt the business processing requests to the designated data center, which shortens the time for shunting the business processing requests to the designated data center, makes the possibility of failure smaller, improves the stability of the system, and at the same time speeds up the update speed.

[0099] As a preferred embodiment, updating the shunt identifiers recorded in the currently used shunt rule table based on the administrative division codes of the registered addresses of the changed enterprises, the registered addresses of the enterprises where the employees of the enterprises work, and the household registration addresses of the flexible employees includes:

[0100] During the business off-peak period, update the shunt identifiers recorded in the currently used shunt rule table based on the administrative division codes of the registered addresses of the changed enterprises, the registered addresses of the enterprises where the employees of the enterprises work, and the household registration addresses of the flexible employees.

[0101] Considering that when updating the currently used traffic splitting rule table and synchronizing the new currently used traffic splitting rule table to other data centers in the application system, splitting the service handling requests received during the update period to the specified data center will cause pressure on the processing capacity of the specified data center and result in failures. To solve the above problems, in this embodiment, during the business low period, that is, when the number of service handling requests is small, such as during the night when the number of service handling requests is small, the traffic splitting identifier of the records in the currently used traffic splitting rule table is updated based on the administrative division codes of the registered addresses of the changed enterprises, the registered addresses of the enterprises where the employees of the enterprises work, and the household registrations of the flexible employees, so that the update can proceed smoothly and at the same time reduce the processing pressure on the specified data center.

[0102] As a preferred embodiment, when receiving a service handling request sent by a client, it further includes:

[0103] Judge whether the service handling request includes the rule identifier of the user; wherein, the rule identifier is used to represent the traffic splitting rule table to which the traffic splitting identifier belongs when the client stores the traffic splitting identifier, and the rule identifiers of different traffic splitting rule tables are different;

[0104] If it includes the rule identifier of the user, judge whether the traffic splitting rule table corresponding to the rule identifier is consistent with the currently used traffic splitting rule table;

[0105] If they are consistent, enter S13;

[0106] If they are inconsistent, enter S12;

[0107] If it does not include the rule identifier of the user, then enter S12;

[0108] After determining the traffic splitting identifier of the user based on the identity identifier of the user and the currently used traffic splitting rule table, it further includes:

[0109] Return the rule identifier corresponding to the currently used traffic splitting rule table to the client so that the client can carry the rule identifier when sending a service handling request.

[0110] Considering that after the traffic splitting identifier in the current traffic splitting rule table is updated, the traffic splitting identifier saved by the client also needs to be updated. In this embodiment, by storing the rule identifier in the client, it is judged whether the traffic splitting identifier of the client needs to be updated and the traffic splitting identifier and rule identifier saved by the client are updated.

[0111] Specifically, after receiving a service handling request, the data center will also determine whether the request includes the user's rule identifier. If it includes the rule identifier, it will determine whether the shunt rule table corresponding to the rule identifier is the same as the currently used shunt rule table. If they are the same, it means that the shunt identifier saved by the client must be the same as the user's shunt identifier in the currently used shunt rule table, and there is no need to update the shunt identifier and rule identifier stored by the client. It can directly enter S13. If they are not the same, it means that the currently used shunt rule table has been updated, and the shunt identifier saved by the client may not be the same as the user's shunt identifier in the currently used shunt rule table. Therefore, it is necessary to enter S12 to update the user's shunt identifier and rule identifier, and return the new shunt identifier and rule identifier to the client so that the client can carry the rule identifier and shunt identifier when sending a service handling request. If the request does not include the rule identifier, it means that the user is sending a service handling request through the client for the first time. Enter S12 to determine the user's shunt identifier and rule identifier and return them to the client.

[0112] In summary, in this embodiment, the data center returns the rule identifier to the client so that the client can carry the rule identifier when initiating a service handling request. And when receiving a service handling request, it judges whether the shunt identifier and rule identifier need to be updated through the rule identifier, ensuring that the shunt identifier of the client can be updated in a timely manner.

[0113] As a preferred embodiment, before determining the user's shunt identifier based on the user's identity identifier and the currently used shunt rule table, it further includes:

[0114] Judge whether the currently used shunt rule table includes the user's identity identifier;

[0115] If so, enter the step of determining the user's shunt identifier based on the user's identity identifier and the currently used shunt rule table;

[0116] If not, divert the service handling request to the designated data center.

[0117] Considering that the identity identifiers of some users have not been written into the currently used shunt rule table yet, in order to ensure that these users can also handle services, in this embodiment, before determining the user's shunt identifier based on the user's identity identifier and the currently used shunt rule table, the data center will also judge whether the currently used shunt rule table includes the user's identity identifier. If not, it means that the user's identity identifier and shunt identifier have not been written into the currently used shunt rule table yet, and the data center will divert the service handling request to the designated data center for handling so that the user can handle the service; if so, then determine the user's shunt identifier based on the user's identity identifier and the currently used shunt rule table.

[0118] In summary, by diverting the service handling requests of users whose identity identifiers have not been written into the currently used diversion rule table to a specified data center, more users can successfully handle services.

[0119] The present invention also provides a diversion system, including:

[0120] A diversion identifier determination unit 21, configured to, when receiving a service handling request sent by a client, determine whether the service handling request includes a user's diversion identifier. If so, trigger the service handling unit 23; if not, trigger the diversion identifier determination unit 22;

[0121] A diversion identifier determination unit 22, configured to obtain the user's identity identifier, determine the user's diversion identifier based on the user's identity identifier and the currently used diversion rule table, and return the diversion identifier to the client so that the client can carry the diversion identifier when sending a service handling request and send the service handling request to the data center corresponding to the diversion identifier, and trigger the diversion identifier determination unit 21; wherein, the currently used diversion rule table includes using the administrative division code of the enterprise's registration place as the user's diversion identifier when the user is an enterprise or an employee of the enterprise; using the administrative division code of the household registration place of the flexible employment personnel as the user's diversion identifier when the user is a flexible employment personnel;

[0122] A service handling unit 23, configured to handle services according to the service handling request.

[0123] For details, please refer to Figure 2 , Figure 2 which is a schematic structural diagram of a diversion system provided by the present invention.

[0124] For the relevant introduction to this diversion system, please refer to the above embodiments, and the present application will not elaborate here.

[0125] The present invention also provides a diversion device, including:

[0126] A memory 31, configured to store a computer program;

[0127] A processor 32, configured to implement the steps of the above diversion method as claimed when executing the computer program.

[0128] For details, please refer to Figure 3 , Figure 3 which is a schematic structural diagram of a diversion device provided by the present invention.

[0129] For the relevant introduction to this diversion device, please refer to the above embodiments, and the present application will not elaborate here.

[0130] In the present specification, the various embodiments are described in a progressive manner. Each embodiment focuses on the differences from other embodiments, and the same or similar parts among the embodiments can be referred to each other. For the devices disclosed in the embodiments, since they correspond to the methods disclosed in the embodiments, the description is relatively simple, and the relevant parts can be referred to the description of the method part.

[0131] It should be noted that in this specification, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the term "comprising", "including" or any other variation thereof is intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements not only includes those elements but also includes other elements not expressly listed, or further includes elements inherent to such process, method, article or device. Without further limitation, an element defined by the phrase "comprising an..." does not exclude the existence of additional identical elements in the process, method, article or device comprising the said element.

Claims

1. A flow splitting method, characterized in that, Applied to the data center in an application system, the traffic splitting method includes: S11: When receiving a service handling request sent by a client, determine whether the service handling request includes the traffic splitting identifier of a user. If so, proceed to S13; if not, proceed to S12. S12: Obtain the identity identifier of the user, determine the traffic splitting identifier of the user based on the identity identifier of the user and the currently used traffic splitting rule table, and return the traffic splitting identifier to the client so that the client carries the traffic splitting identifier when sending the service handling request and sends the service handling request to the data center corresponding to the traffic splitting identifier, then return to S11. The rules of the currently used traffic splitting rule table include that when the user is an enterprise or an employee of the enterprise, the administrative division code of the registration place of the enterprise is used as the traffic splitting identifier of the user; when the user is a flexible employee, the administrative division code of the household registration place of the flexible employee is used as the traffic splitting identifier of the user. S13: Handle the service according to the service handling request. Among them, when determining the administrative division codes of the registration place of the changed enterprise, the registration place of the enterprise where the employee of the enterprise works, and the household registration place of the flexible employee, create a temporary traffic splitting rule change table to store the administrative division codes of the registration place of the changed enterprise, the registration place of the enterprise where the employee of the enterprise works, and the household registration place of the flexible employee, and delete the traffic splitting rule change table after the update is completed or it is determined that no update is required. Among them, the method further includes: comparing whether the ratio of the traffic splitting identifiers of the enterprises, the employees of the enterprises, and the flexible employees recorded in the currently used traffic splitting rule table to the administrative division codes of the registration place of the enterprises, the registration place of the enterprises where the employees of the enterprises work, and the household registration place of the flexible employees recorded in the natural person and enterprise employment relationship table reaches a preset ratio to determine whether an update is required; and updating the currently used traffic splitting rule table after reaching the preset ratio. When the number of traffic splitting rule tables is 2, the data center updates the traffic splitting identifiers in the currently unused traffic splitting rule table, splits the received service handling request to the designated data center after completion, enables the currently unused traffic splitting rule table, and synchronizes the data to other data centers to complete the update.

2. The flow splitting method according to claim 1, characterized in that, Obtaining the identity identifier of the user includes: Determining whether the user logs in to the client; If so, obtaining the identity identifier of the user according to the login information of the user; If not, prompting the user to log in to the client and returning to the step of determining whether the user logs in to the client.

3. The flow splitting method according to claim 2, characterized in that, Comparing whether the ratio of the traffic splitting identifiers of the enterprises, the employees of the enterprises, and the flexible employees recorded in the currently used traffic splitting rule table to the administrative division codes of the registration place of the enterprises, the registration place of the enterprises where the employees of the enterprises work, and the household registration place of the flexible employees recorded in the natural person and enterprise employment relationship table reaches a preset ratio to determine whether an update is required; Updating the currently used traffic splitting rule table after reaching the preset ratio includes: S31: When obtaining the update permission, read the employment relationship table of natural persons and enterprises and the currently used traffic diversion rule table. The employment relationship table of natural persons and enterprises includes the employees of the enterprise and their employment relationships with the enterprise, the administrative division code of the enterprise's registration location, and the administrative division code of the household registration location of the flexible employees; S32: Determine whether the enterprise, the employees of the enterprise, and the traffic diversion identifiers of the flexible employees in the currently used traffic diversion rule table are all the same as the administrative division codes of the enterprise's registration location, the registration location of the enterprises where the employees of the enterprise work, and the household registration location of the flexible employees recorded in the employment relationship table of natural persons and enterprises. If they are not all the same, proceed to S33; if they are all the same, proceed to S31; S33: Determine the administrative division codes of the registration location of the enterprise to be changed, the registration location of the enterprises where the employees of the enterprise work, and the household registration location of the flexible employees. The administrative division codes of the registration location of the enterprise to be changed, the registration location of the enterprises where the employees of the enterprise work, and the household registration location of the flexible employees refer to the administrative division codes of the enterprise's registration location, the registration location of the enterprises where the employees of the enterprise work, and the household registration location of the flexible employees recorded in the employment relationship table of natural persons and enterprises that are different from the enterprise, the employees of the enterprise, and the traffic diversion identifiers of the flexible employees recorded in the currently used traffic diversion rule table; S34: Determine whether the ratio of the total number of the administrative division codes of the registration location of the enterprise to be changed, the registration location of the enterprises where the employees of the enterprise work, and the household registration location of the flexible employees to the total number of the enterprise, the employees of the enterprise, and the traffic diversion identifiers of the flexible employees recorded in the currently used traffic diversion rule table reaches a preset ratio. If it does, proceed to S35; S35: Update the traffic diversion identifiers of the records in the currently used traffic diversion rule table based on the administrative division codes of the registration location of the enterprise to be changed, the registration location of the enterprises where the employees of the enterprise work, and the household registration location of the flexible employees, and synchronize the updated traffic diversion rule table to other data centers in the application system.

4. The flow splitting method according to claim 3, characterized in that, Updating the traffic diversion identifiers of the records in the currently used traffic diversion rule table based on the administrative division codes of the registration location of the enterprise to be changed, the registration location of the enterprises where the employees of the enterprise work, and the household registration location of the flexible employees, and synchronizing the updated traffic diversion rule table to other data centers in the application system includes: When updating the currently used traffic diversion rule table and synchronizing the updated traffic diversion rule table to other data centers in the application system, divert the business handling requests received during the update period to the designated data center; Update the administrative division codes of the registration location of the enterprise to be changed, the registration location of the enterprises where the employees of the enterprise work, and the household registration location of the flexible employees as the traffic diversion identifiers of the enterprise to be changed, the employees of the enterprise, and the flexible employees to the currently used traffic diversion rule table; Synchronize the updated traffic diversion rule table to other data centers in the application system, and end the update after the synchronization is completed.

5. The flow splitting method according to claim 3, characterized in that, When the number of shunt rule tables is 2, the data center updates the shunt identifiers in the currently unused shunt rule table, and after completion, shunts the received business processing requests to the specified data center, enables the currently unused shunt rule table, and completes the update after synchronizing the data to other data centers, including: Empty the currently unused shunt rule table; Write the administrative division codes of the registered addresses of the changed enterprises, the registered addresses of the enterprises where the employees of the enterprises work, and the household registration locations of the flexible employees as the shunt identifiers of the changed enterprises, enterprise employees, and flexible employees into the currently unused shunt rule table; Write the shunt identifiers in the currently used shunt rule table that are the same as the administrative division codes of the registered addresses of the enterprises, the enterprises where the employees of the enterprises work, and the household registration locations of the flexible employees recorded in the natural person and enterprise employment relationship table into the currently unused shunt rule table; Use the currently used shunt rule table as the new currently unused shunt rule table, and use the currently unused shunt rule table as the new currently used shunt rule table; Synchronize the new currently used shunt rule table to other data centers in the application system, and end the update after the synchronization is completed; When using the currently used shunt rule table as the new currently unused shunt rule table, using the currently unused shunt rule table as the new currently used shunt rule table, and synchronizing the new currently used shunt rule table to other data centers in the application system, shunt the received business processing requests to the specified data center.

6. The flow splitting method according to claim 5, characterized in that, Update the shunt identifiers recorded in the currently used shunt rule table based on the administrative division codes of the registered addresses of the changed enterprises, the registered addresses of the enterprises where the employees of the enterprises work, and the household registration locations of the flexible employees, including: During the business low season, update the shunt identifiers recorded in the currently used shunt rule table based on the administrative division codes of the registered addresses of the changed enterprises, the registered addresses of the enterprises where the employees of the enterprises work, and the household registration locations of the flexible employees.

7. The flow splitting method according to claim 6, characterized in that, When receiving a business processing request sent by the client, it also includes: Judge whether the business processing request includes the rule identifier of the user; wherein, the rule identifier is used to represent the shunt rule table to which the shunt identifier belongs when the shunt identifier is stored in the client, and the rule identifiers of different shunt rule tables are different; If it includes the rule identifier of the user, judge whether the shunt rule table corresponding to the rule identifier is consistent with the currently used shunt rule table; If they are consistent, enter S13; If they are inconsistent, enter S12; If it does not include the rule identifier of the user, then enter S12; After determining the shunt identifier of the user based on the identity identifier of the user and the currently used shunt rule table, it also includes: Return the rule identifier corresponding to the currently used shunt rule table to the client so that the client can carry the rule identifier when sending the business processing request.

8. The flow splitting method according to any one of claims 1 to 7, characterized in that, Before determining the shunt identifier of the user based on the identity identifier of the user and the currently used shunt rule table, it further includes: Determine whether the identity identifier of the user is included in the currently used shunt rule table; If so, enter the step of determining the shunt identifier of the user based on the identity identifier of the user and the currently used shunt rule table; If not, shunt the service handling request to the designated data center.

9. A flow splitting system, characterized in that, It includes: A shunt identifier determination unit, configured to, when receiving a service handling request sent by a client, determine whether the service handling request includes a shunt identifier of a user. If so, trigger the service handling unit; if not, trigger the shunt identifier determination unit; The shunt identifier determination unit is configured to obtain the identity identifier of the user, determine the shunt identifier of the user based on the identity identifier of the user and the currently used shunt rule table, and return the shunt identifier to the client so that the client carries the shunt identifier when sending the service handling request and sends the service handling request to the data center corresponding to the shunt identifier, and trigger the shunt identifier determination unit; wherein, the currently used shunt rule table includes that when the user is an enterprise or an employee of the enterprise, the administrative division code of the registered place of the enterprise is used as the shunt identifier of the user; when the user is a flexible employee, the administrative division code of the household registration place of the flexible employee is used as the shunt identifier of the user; A service handling unit, configured to handle the service according to the service handling request; The shunt identifier determination unit is further configured to, when determining the administrative division codes of the registered place of the changed enterprise, the registered place of the enterprise where the employee of the enterprise works, and the household registration place of the flexible employee, create a temporary shunt rule change table to store the administrative division codes of the registered place of the changed enterprise, the registered place of the enterprise where the employee of the enterprise works, and the household registration place of the flexible employee, and delete the shunt rule change table after the update is completed or it is determined that no update is required; The shunt identifier determination unit is further configured to compare whether the proportion of the shunt identifiers of the enterprises, the employees of the enterprises, and the flexible employees recorded in the currently used shunt rule table that are different from the administrative division codes of the registered place of the enterprise, the registered place of the enterprise where the employee of the enterprise works, and the household registration place of the flexible employee recorded in the natural person and enterprise employment relationship table reaches a preset proportion to determine whether an update is required; after reaching the preset proportion, update the currently used shunt rule table; when the number of shunt rule tables is 2, the data center updates the shunt identifiers in the currently unused shunt rule table, shunts the received service handling request to the designated data center after completion, enables the currently unused shunt rule table, and synchronizes the data to other data centers to complete the update.

10. A flow splitting device, characterized in that, It includes: A memory, configured to store a computer program; A processor, configured to implement the steps of the shunt method according to any one of claims 1 to 8 when executing the computer program.

Images