Detailed Description
Fig. 1 is a service platform-based business processing method according to an exemplary embodiment in the prior art.
As shown in fig. 1, the user terminal calls a uniform service platform interface address and sends a service request to the platform. Through the domain name conversion function of the service platform, one data center in the service platform can be assigned to distribute the service request, and the data center can store the routing strategy, so that the data center can distribute a target data center for the service request according to the service attribute and forward the service request to the corresponding target data center. In this process, when the user terminal performs service processing, it needs to rely on a designated data center, and the center needs to distribute the request service, which increases the network time consumption of the whole data processing process, and when the center fails, it will affect the whole distributed system.
In the scheme provided by the embodiment of the invention, the appointed data center serving as the centralized node is removed during service processing, and the data center information matched with the appointed data center is acquired in advance through the user terminal, so that the user terminal can directly interact with the data center, and the dependence degree on the appointed service center in the service processing process is reduced.
Fig. 2 is a flowchart illustrating a service processing method according to an exemplary embodiment of the present invention.
FIG. 2A is a diagram illustrating a service platform architecture of a business processing system in accordance with an exemplary embodiment of the present invention.
As shown in fig. 2A, the method provided in this embodiment can be applied to the service platform architecture shown in fig. 2A. The service platform can comprise a user terminal and a plurality of data centers, and the user terminal can be connected with the data centers through a domain name resolution server or directly connected with the data centers through a network. The user terminal can be connected with a plurality of data centers through a network or can be connected with one of the data centers.
Step 201, the user terminal determines a target data center according to the routing parameter.
The service processing method provided by the implementation is executed by the user terminal, and the user terminal can be arranged at the cooperation mechanism side of the access service platform. For example, if the agency a purchases a service provided by the service platform, software packaged with the method provided in this embodiment may be installed in a terminal owned by the agency a, and an account password may be assigned to the software. The user terminal may be an electronic device with a computing function, such as a computer, a tablet computer, and the like, and may specifically be a server of the agency a.
The user terminal may obtain a routing parameter in advance, where the routing parameter includes information of a data center to which the user terminal may access, and specifically may be an IP (Internet Protocol, Protocol for interconnection between networks) address of the data center. For example, the service platform is provided with 10 data centers, the data centers that the user terminal can access include center 1 and center 2, and the routing parameters include IP addresses of centers 1 and 2.
Specifically, a plurality of data centers may be set in the service platform, and the data centers may store operation parameters, where the operation parameters include information of the data centers that each user terminal can access. The data center may be a device owned by the service provider and capable of storing data and processing services of the user terminal. After the service is purchased by the partner organization, the corresponding data center can be determined according to the content purchased by the partner organization. The data center which can be accessed by the user terminal can be determined according to the position of the user terminal and the position of each data center set by the cooperation mechanism, so that the length of a network link connected with the user terminal and the data center is reduced. And if the traffic is large, a plurality of data centers can be set for the cooperation mechanism.
Further, the user terminal may obtain the routing parameters from the first data center. The user terminal may specifically send an access request to a domain name resolution server (DNS server), where the access request includes a domain name and is used to request to access a data center corresponding to the domain name. For the user, the specific address of each data center does not need to be known, and only the domain name needs to be known. For the data center side, each data center is a device corresponding to the domain name, but each data center does not need to be exposed to the outside, and only the domain name needs to be exposed to the outside and can be accessed to the data center according to the domain name.
The DNS server is provided with a corresponding relation between a domain name and an IP address, can find the corresponding IP address of the first data center according to the domain name, and sends the access request to the first data center. The access request may further include an identifier of the user terminal, the first data center finds, according to the identifier of the user terminal, data center information corresponding to the user terminal from the stored operating parameters, may determine a routing parameter according to the data center information, and feeds back the routing parameter to the user terminal.
In actual application, each data center can store the same operating parameters, a first data center can be set, a domain name is set in the DNS server to correspond to the IP of the first data center, and if the first data center fails, any other data center can be upgraded to the first data center. So that the system can also operate normally after the first data center fails.
The user terminal can determine the target data center according to the acquired routing parameters. The user terminal does not need to acquire the routing parameters before the service starts each time, and can determine a target data center according to the routing parameters as long as the routing parameters are stored in the user terminal. The routing parameters include data center information accessible to the user terminal, and each data center can process the service of the user terminal, but the data centers do not need to process the same service one by one, so that the user terminal can determine a target data center from the accessible data centers and process the current service request by the target center.
In one embodiment, the routing parameters may further include a weight parameter, so that the user terminal can determine the target center in the accessible data center according to the weight parameter. In another embodiment, the accessible data centers in the routing parameters may be in the form of a list, and the user terminal may determine the target data center in the order in the list, for example, the first accessible data center may be determined as the target data center.
Specifically, the first data center and the target data center may be the same or different.
Step 202, the user terminal sends a service request to the target data center, so that the target data center returns a service processing result.
Further, the user terminal may obtain an IP address of the target data center through the routing parameter, and send the service request to the IP address as the target address, thereby sending the service request to the target data center.
In practical application, the service request further includes a source address, which is used for storing the address of the user terminal sending the service request. After receiving the service request, the target data center may process the service request. For example, the service request may be to obtain commodity information on shelf today, and the target data center may obtain corresponding commodity information and return the commodity information to the user terminal.
The target data center can obtain the source address in the service request as the target address, and then send the service processing result, thereby feeding back the service processing result to the user terminal.
The user terminal side obtains the routing parameters in advance and can directly determine the data center for processing the service request, so that the data center does not need to be appointed to distribute the service request, a central node in a service platform framework in the prior art is taken out, the time consumed by the central node for calculating and distributing the service request can be reduced, and potential safety hazards brought to the whole system by the central node can be avoided.
The method provided by the present embodiment is used for processing services, and the method is executed by a device provided with the method provided by the present embodiment, and the device is generally implemented in a hardware and/or software manner.
The service processing method provided by the embodiment comprises the steps that a user terminal determines a target data center according to a routing parameter; the user terminal sends a service request to the target data center so that the target data center returns a service processing result; the routing parameters are acquired by the user terminal from the first data center in advance. In the method provided by this embodiment, since the user terminal obtains the routing parameter in advance, the user terminal can directly interact with the data center based on the routing parameter to perform service processing, and the central node is not required to distribute the service request sent by the user terminal, so that the time consumed by the central node in calculating and distributing the service request is reduced, and potential safety hazards brought to the whole system by the central node can be avoided.
Fig. 3 is a flowchart illustrating a service processing method according to another exemplary embodiment of the present invention.
As shown in fig. 3, the service processing method provided in this embodiment includes:
step 301, a user terminal sends an obtaining request for obtaining a routing parameter to a domain name resolution server, where the obtaining request includes a domain name, so that the domain name resolution server determines a first data center according to the domain name, and sends the obtaining request to the first data center, so that the first data center obtains the routing parameter corresponding to the user terminal, and sends the routing parameter to the user terminal.
The user terminal may determine whether the user terminal stores the routing parameter, for example, a file for storing the routing parameter may be set in the user terminal, and the content in the file may be read, and if the content is empty, it may be determined that the routing parameter is not stored in the user terminal. When the user terminal is accessed to the service platform for the first time, the inside of the user terminal has no routing parameters, and after the user terminal is accessed to the service platform, if the inside data is empty, the situation that the routing parameters are lost can also be caused.
Specifically, if the user terminal does not store the routing parameters therein, the user terminal cannot determine the IP addresses of the data centers, and cannot be directly connected to the data centers. Therefore, the domain name resolution server can be connected with the data center, and the routing parameters can be acquired.
Further, the user terminal may send an acquisition request for acquiring the routing parameter to the domain name resolution server. The user terminal cannot determine the IP address of the data center, but can acquire the external domain name of the data center and add domain name information to the acquisition request. The domain name resolution server stores the corresponding relation between the domain name and the IP address. When the service platform is provided with a plurality of data centers, the IP address of one of the data centers can be specified to correspond to the domain name, and the corresponding relation is written into the domain name resolution server.
In actual application, after receiving the acquisition request, the domain name resolution server may read the domain name information included therein, and determine the IP address corresponding to the domain name based on the correspondence between the domain name and the IP address. And then sending the acquisition request to a first data center corresponding to the IP address.
The service platform comprises a plurality of data centers, wherein the data centers are arranged on the service platform, and the service platform comprises operation parameters, wherein the operation parameters comprise a data center list which can be accessed by each user terminal and a database which can be accessed by each user terminal, so that the first data center can determine the routing parameters of the user terminal which sends the acquisition request based on the operation parameters.
Specifically, when sending a message, the data frame may include basic information such as a destination address and a source address. The first data center can determine the IP address of the user terminal according to the source address in the acquisition request, and further directly send the routing parameters to the user terminal.
Further, it is possible that the operating parameters in the data center are updated. For example, if one of the data centers is off-shelf due to a failure or other reasons, the accessible data center list of the user terminal should not include the off-shelf data center. At this point, the operating parameters in the data center may be updated. For example, the accessible data centers of the user terminal a are a and b, wherein a is off-shelf, and then the accessible data center corresponding to the user terminal a in the operation parameters of the data center is modified into b. Specifically, the operating parameters of one of the data centers may be modified, and the operating parameters may be synchronized from the one data center to the other data centers. The modified data center may be a master data center and the other data centers slave data centers. In the domain name resolution server, the domain name of the service platform corresponds to the IP address of the main data center.
After the data in the data center is modified, the routing parameters in the user terminal are also information before modification. Therefore, after the user terminal acquires the routing parameter, the routing parameter may also be timed and synchronized, and a specific implementation manner may be step 3021 or step 3022. If the embodiment of step 3021 is used, it may be performed at any time after step 301. If the embodiment of step 3022 is adopted, it may be performed after step 303.
Step 3021, the user terminal sends a synchronization request for synchronizing the routing parameters to the first data center according to the preset frequency, so that the first data center feeds back the current routing parameters.
In practical application, when the first data center feeds back the routing parameter to the user terminal for the first time, the sending message may include a source address, that is, an IP address of the first data center. The user terminal may record this address and periodically send a synchronization request for synchronizing the routing parameters to the first data center based on this address.
After receiving the synchronization request, the first data center may determine a routing parameter corresponding to the synchronization request according to a source address in the request; or the user terminal identifier encapsulated in the synchronization request may be acquired, the routing parameter corresponding to the terminal identifier is determined, and then the current routing parameter, that is, the latest routing parameter, is fed back to the user terminal.
The user terminal may periodically send a synchronization request to the first data center according to a preset frequency. The preset frequency can be set according to requirements, such as once every 5 minutes, once every 10 minutes, and the like.
Step 3022, the user terminal sends a synchronization request for synchronizing the routing parameters to the target data center according to the preset frequency, so that the target data center feeds back the current routing parameters.
Specifically, in the method provided in this embodiment, each data center stores an operation parameter, and the latest operation parameter may be synchronized from the master data center to each slave data center, and the data center may determine the routing parameter of the user terminal according to the operation parameter.
Further, after the user terminal obtains the routing parameters, the target data center may be determined according to the routing parameters, and the specific determination method is similar to step 201. At this time, the user terminal may determine the IP address of the target data center, and may directly send a synchronization request for synchronizing the routing parameters to the target data center according to the IP address, so that the target data center feeds back the current routing parameters.
In fig. 3, steps 2021, 2022 are illustrated at the same time, but in practical applications, only one of the embodiments may be selected.
Step 303, the user terminal determines the target data center according to the routing parameter.
Step 304, the user terminal sends a service request to the target data center, so that the target data center returns a service processing result.
The steps 303-304 are similar to the steps 201-202 in terms of specific principles and implementation, and are not described herein again.
If the user terminal receives the error message fed back by the target data center after the user terminal sends the service request to the target data center, the user terminal continues to execute step 301.
If the operation parameters in the data center are updated and the user terminal starts to perform service processing without synchronizing the routing parameters, the situation that the routing parameters in the user terminal are not synchronized with the operation parameters of the data center may exist, and at this time, the user terminal performs service processing according to the currently stored routing parameters, and the situation of error reporting may exist. For example, the user terminal requests the data center for the synchronization routing parameters at 10:20 and sends a synchronization request to the data center every 5 minutes, i.e., the next time the synchronization routing parameters are applied is 10: 25. If the operation parameters are updated in the data center at 10:21, and if the user terminal initiates a service request according to the routing parameters at 10:23, there may be a case of error reporting due to inconsistency between the routing parameters and the operation parameters.
Specifically, after receiving the service request, the target data center may determine whether the service request of the user terminal can be processed according to the operation parameter. For example, the user terminal includes accessible data centers a, b and c in the routing parameters synchronized at 10:20, and when a service request is initiated at 10:23, the determined target data center is c and the service request is sent to c. At 10:21, the operation parameters are updated in the data center, wherein the accessible data centers corresponding to the user terminals are updated to be a and b. Then c, after receiving the service request, comparing according to the operation parameters to determine whether the service can be processed for the user terminal, if the determination result is that the service cannot be processed, sending an error message to the user terminal, and specifically sending a message requiring the user terminal to use correct routing parameters for service processing.
Further, after receiving the error message, the user terminal may determine that the data center reports an error due to the routing parameter error, and therefore, step 301 may be continuously performed, so as to obtain the latest routing parameter. By carrying out service identification and interception in the data center, the user terminal can be controlled to send the service request to the matched data center.
Fig. 4 is a flowchart illustrating a service processing method according to another exemplary embodiment of the present invention.
Step 401, the target data center receives a service request sent by a user terminal, wherein the user terminal determines the target data center according to the routing parameter.
The method provided by the embodiment can be applied to the service platform architecture shown in fig. 2A.
The service processing method provided by the implementation is executed by a target data center, and the data center can be a device owned by a service provider and can store data and process the service of a user terminal. In a service platform architecture, multiple data centers may be provided.
First, the user terminal may obtain a routing parameter from a first data center among the plurality of data centers in advance, and determine a target data center according to the routing parameter.
The user terminal may specifically send an access request to a domain name resolution server (DNS server), where the access request includes a domain name and is used to request to access a data center corresponding to the domain name. For the user, the specific address of each data center does not need to be known, and only the domain name needs to be known. For the data center side, each data center is a device corresponding to the domain name, but each data center does not need to be exposed to the outside, and only the domain name needs to be exposed to the outside and can be accessed to the data center according to the domain name.
The DNS server is provided with a corresponding relation between a domain name and an IP address, can find the corresponding IP address of the first data center according to the domain name, and sends the access request to the first data center. The access request may further include an identifier of the user terminal, the first data center finds, according to the identifier of the user terminal, data center information corresponding to the user terminal from the stored operating parameters, may determine a routing parameter according to the data center information, and feeds back the routing parameter to the user terminal.
In actual application, each data center can store the same operating parameters, a first data center can be set, a domain name is set in the DNS server to correspond to the IP of the first data center, and if the first data center fails, any other data center can be upgraded to the first data center. So that the system can also operate normally after the first data center fails.
The user terminal can determine the target data center according to the acquired routing parameters. The user terminal does not need to acquire the routing parameters before the service starts each time, and can determine a target data center according to the routing parameters as long as the routing parameters are stored in the user terminal. The routing parameters include data center information accessible to the user terminal, and each data center can process the service of the user terminal, but the data centers do not need to process the same service one by one, so that the user terminal can determine a target data center from the accessible data centers and process the current service request by the target center.
In one embodiment, the routing parameters may further include a weight parameter, so that the user terminal can determine the target center in the accessible data center according to the weight parameter. In another embodiment, the accessible data centers in the routing parameters may be in the form of a list, and the user terminal may determine the target data center in the order in the list, for example, the first accessible data center may be determined as the target data center.
Specifically, the first data center and the target data center may be the same or different.
Further, the user terminal may obtain an IP address of the target data center through the routing parameter, and send the service request to the IP address as the target address, thereby sending the service request to the target data center. The target data center can directly receive the service request sent by the user terminal, and a central node in the service platform is not required to forward the service request, so that the service of the user terminal can be processed under the decentralized condition.
Step 402, the target data center determines whether to process the service request according to the pre-stored operation parameters, and if not, sends an error message to the user terminal.
The service platform may store operation parameters in each data center, where the operation parameters include data center information that each user terminal can access. After the service is purchased by the partner organization, the corresponding data center can be determined according to the content purchased by the partner organization. The data center which can be accessed by the user terminal can be determined according to the position of the user terminal and the position of each data center set by the cooperation mechanism, so that the length of a network link connected with the user terminal and the data center is reduced. And if the traffic is large, a plurality of accessible data centers can be set for the cooperation mechanism.
Specifically, the target data center may identify the service request and determine whether the service request can be processed. According to the operation parameters, whether the target data center is an accessible data center of the user terminal or not can be determined, and specifically, the user terminal identifier and/or the source address included in the service request can be obtained, so that whether the user terminal has the right to use the target data center or not can be determined.
Further, a database identifier accessible by each user terminal may also be set in the operation parameter, and accordingly, the service request sent by the user terminal may also carry the database identifier to be accessed. The target data center can identify whether the database to be accessed by the user terminal currently is in the authority range of the user terminal.
In actual application, if the user terminal does not have the data processing by using the target data center or the authority of accessing the database in the service request, determining not to process the current service request, and returning an error message to the user terminal.
In one case, the accessible data center corresponding to the user terminal has been changed, but the routing parameter in the user terminal is not updated, which may cause the target data center to return an error message, at this time, the user terminal may be further prompted with information that the address of the target data center is incorrect, so that the user terminal may obtain the routing parameter from the first data center again, re-determine the target data center according to the routing parameter, and further send a service request to the new target data center again.
In another case, it may be that the target data center requested to be accessed by the user terminal is down or for other reasons, and at this time, the target data center may also be caused to return an error message. At this time, a message that the current target data center is unavailable and the target center is replaced can be prompted to the user terminal, so that the user terminal can determine the target data center again according to the routing parameters, and further send a service request to a new target data center again.
The method provided by the present embodiment is used for processing services, and the method is executed by a device provided with the method provided by the present embodiment, and the device is generally implemented in a hardware and/or software manner.
The service processing method provided by the embodiment comprises the steps that a target data center receives a service request sent by a user terminal, wherein the user terminal determines the target data center according to a routing parameter; and the target data center determines whether to process the service request according to the preset operation parameters, and if not, sends an error message to the user terminal. In the method provided by this embodiment, the user terminal can determine the target data center according to the routing parameters, so that the target data center can directly receive the service request sent by the user terminal, and the service request does not need to be distributed by the central node, thereby reducing the network time consumption for calculating and allocating the service request by the central node, and avoiding the potential safety hazard brought by the central node to the whole system.
Fig. 5 is a flowchart illustrating a service processing method according to still another exemplary embodiment of the present invention.
As shown in fig. 5, the service processing method provided in this embodiment includes:
step 501, a target data center receives synchronous operation parameters of a first data center, and updates prestored operation parameters according to the received operation parameters.
In the method provided by this embodiment, the service platform may be provided with a plurality of data centers, and one first data center may be set therein as a master data center, and the other data centers may be set therein as slave data centers. When the operation parameters need to be adjusted, the operation parameters in the main data center can be modified, and then the main data center synchronizes the updated operation parameters to other data centers.
Specifically, the target data center may be a slave data center in the service platform, and when the operation parameters in the first data center are updated, the target data center may receive new operation parameters synchronized by the first data center.
Further, the first data center stores updated operating parameters. When the operation parameters need to be adjusted, only the operation parameters in the first data center may be modified, so as to update the operation parameters in the first data center, and then the operation parameters are synchronized to other slave data centers based on the updated operation parameters, and each slave operation center may receive the operation parameters sent by the first data center and update the stored operation parameters.
Step 502, receiving a synchronization request of synchronizing routing parameters sent by a user terminal, and feeding back the latest routing parameters to the user terminal according to the operation parameters synchronized by the first data center.
In practical application, the user terminal may determine the target data center according to the routing parameters stored in the user terminal, and send a synchronization request for synchronizing the routing parameters to the target data center. After receiving the synchronization request, the target data center may determine a routing parameter corresponding to the user terminal according to the currently stored operation parameter, that is, the operation parameter synchronized to the target data center by the first data center, and feed back the routing parameter to the user terminal.
The target data center can determine a routing parameter corresponding to the source address according to the source address in the request; or the user terminal identifier encapsulated in the synchronization request may be acquired, the routing parameter corresponding to the terminal identifier is determined, and then the current routing parameter, that is, the latest routing parameter, is fed back to the user terminal.
Specifically, the user terminal may send an acquisition request for acquiring the routing parameters to the domain name resolution server, so that the domain name resolution server determines the first data center according to the domain name in the acquisition request, and sends the acquisition request to the first data center, so that the first data center acquires the routing parameters corresponding to the user terminal, and sends the routing parameters to the user terminal. The first data center stores operation parameters, and the operation parameters may include routing parameters corresponding to each user terminal, so that the first data center may determine the routing parameters according to the operation parameters and send the routing parameters to the user terminals.
Further, after the user terminal obtains the routing parameters, the target data center can be determined according to the routing parameters. The routing parameters include data center information accessible to the user terminal, and each data center can process the service of the user terminal, but the data centers do not need to process the same service one by one, so that the user terminal can determine a target data center from the accessible data centers and process the current service request by the target center.
In one embodiment, the routing parameters may further include a weight parameter, so that the user terminal can determine the target center in the accessible data center according to the weight parameter. In another embodiment, the accessible data centers in the routing parameters may be in the form of a list, and the user terminal may determine the target data center in the order in the list, for example, the first accessible data center may be determined as the target data center.
After the user terminal determines the target data center, a synchronization request for synchronizing the routing parameters can be sent to the target data center according to the preset frequency. In the method provided by this embodiment, each data center stores operating parameters, and the latest operating parameters can be synchronized from the first data center to each slave data center, so that the operating parameters stored in the target data center are latest, so that the target data center can determine the latest routing parameters according to the latest operating parameters.
Step 503, the target data center receives a service request sent by the user terminal, wherein the user terminal determines the target data center according to the routing parameter.
The timing of steps 502 and 503 is not limited.
Step 504, the target data center determines whether to process the service request according to the preset operation parameters, and if not, sends an error message to the user terminal.
The steps 503 and 504 are similar to the specific principles and implementation of the steps 401 and 402, and are not described herein again.
Fig. 6 is a block diagram of a service processing apparatus according to an exemplary embodiment of the present invention.
As shown in fig. 6, the service processing apparatus provided in this embodiment includes:
a determining module 61, configured to determine a target data center according to the routing parameter;
a service request sending module 62, configured to send a service request to the target data center, so that the target data center returns a service processing result;
the routing parameters are acquired by the service processing device from the first data center in advance.
The service processing apparatus provided in this embodiment includes: the determining module is used for determining a target data center according to the routing parameters; the service request sending module is used for sending a service request to the target data center so as to enable the target data center to return a service processing result; the routing parameters are acquired by the service processing device from the first data center in advance. In the device provided by this embodiment, since the device obtains the routing parameter in advance, the device can directly interact with the data center based on the routing parameter to perform service processing, and the central node is not required to distribute the service request sent by the device, so that the time consumed by the central node to calculate and distribute the service request is reduced, and potential safety hazards brought to the entire system by the central node can be avoided.
The specific principle and implementation of the service processing apparatus provided in this embodiment are similar to those of the embodiment shown in fig. 2, and are not described here again.
Fig. 7 is a block diagram illustrating a service processing apparatus according to another exemplary embodiment of the present invention.
As shown in fig. 7, on the basis of the embodiment shown in fig. 6, the apparatus provided in this embodiment further includes:
an obtaining request sending module 63, configured to send an obtaining request for obtaining a routing parameter to a domain name resolution server, where the obtaining request includes a domain name, so that the domain name resolution server determines, according to the domain name, a first data center in which the routing parameter is stored, and sends the obtaining request to the first data center, so that the first data center obtains the routing parameter corresponding to the user terminal, and sends the routing parameter to the user terminal.
The device further comprises:
a synchronization request sending module 64, configured to send a synchronization request for synchronizing routing parameters to the first data center according to a preset frequency, so that the first data center feeds back current routing parameters.
The apparatus may further include another synchronization request sending module 65, configured to send a synchronization request for synchronizing the routing parameters to the target data center according to a preset frequency, so that the target data center feeds back the current routing parameters.
The apparatus further includes a receiving module 66, wherein if the service request sending module 62 sends the service request to the target data center, the receiving module 66 receives an error message fed back by the target data center;
the obtaining request sending module 63 continues to send the obtaining request for obtaining the routing parameters to the domain name resolution server.
The specific principle and implementation of the service processing apparatus provided in this embodiment are similar to those of the embodiment shown in fig. 3, and are not described here again.
Fig. 8 is a block diagram illustrating a service processing apparatus according to still another exemplary embodiment of the present invention.
As shown in fig. 8, the service processing apparatus provided in this embodiment includes:
a service request receiving module 81, configured to receive a service request sent by a user terminal, where the user terminal determines a service processing apparatus according to a routing parameter;
a service processing module 82, configured to determine whether to process the service request according to a pre-stored operation parameter, and if not, a message sending module 83 sends an error message to the user terminal.
The service processing apparatus provided in this embodiment includes: the service request receiving module is used for receiving a service request sent by a user terminal, wherein the user terminal determines a service processing device according to the routing parameter; and the service processing module is used for determining whether to process the service request according to the prestored operation parameters, and if not, the message sending module sends an error message to the user terminal. In the device provided by this embodiment, the user terminal can determine the service processing device according to the routing parameter, so that the service processing device can directly receive the service request sent by the user terminal, and the service request does not need to be distributed by the central node, thereby reducing the network time consumption for calculating and allocating the service request by the central node, and avoiding the potential safety hazard brought by the central node to the whole system.
The specific principle and implementation of the service processing apparatus provided in this embodiment are similar to those of the embodiment shown in fig. 4, and are not described here again.
Fig. 9 is a block diagram illustrating a service processing apparatus according to still another exemplary embodiment of the present invention.
As shown in fig. 9, on the basis of the embodiment shown in fig. 8, the apparatus provided in this embodiment further includes:
a parameter synchronization module 84, configured to receive the operation parameter synchronized by the first data center, and update a prestored operation parameter according to the received operation parameter;
and the first data center stores the updated operating parameters.
The device, still include:
a synchronization request receiving module 85, configured to receive a synchronization request for synchronizing routing parameters sent by the user terminal, and feed back the latest routing parameters to the user terminal according to the operation parameters synchronized by the first data center.
The specific principle and implementation of the service processing apparatus provided in this embodiment are similar to those of the embodiment shown in fig. 5, and are not described here again.
Fig. 10 is a block diagram of a service processing device according to an exemplary embodiment of the present invention.
As shown in fig. 10, the service processing device provided in this embodiment includes:
a memory 1001;
a processor 1002; and
a computer program;
wherein the computer program is stored in the memory 1001 and configured to be executed by the processor 1002 to implement any of the traffic processing methods described in fig. 2-3.
Fig. 11 is a block diagram illustrating a service processing device according to another exemplary embodiment of the present invention.
As shown in fig. 10, the service processing device provided in this embodiment includes:
a memory 1101;
a processor 1102; and
a computer program;
wherein the computer program is stored in the memory 1101 and configured to be executed by the processor 1102 to implement any of the traffic processing methods described in fig. 4-5.
The present embodiments also provide a computer-readable storage medium, having stored thereon a computer program,
the computer program is executed by a processor to implement any of the traffic processing methods as described in fig. 2-3.
The present embodiments also provide a computer-readable storage medium, having stored thereon a computer program,
the computer program is executed by a processor to implement any of the traffic processing methods as described in fig. 4-5.
Those of ordinary skill in the art will understand that: all or a portion of the steps of implementing the above-described method embodiments may be performed by hardware associated with program instructions. The program may be stored in a computer-readable storage medium. When executed, the program performs steps comprising the method embodiments described above; and the aforementioned storage medium includes: various media that can store program codes, such as ROM, RAM, magnetic or optical disks.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solution of the present invention, and not to limit the same; while the invention has been described in detail and with reference to the foregoing embodiments, it will be understood by those skilled in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present invention.