Request for distribution methods, devices, storage media and electronic devices

Abstract

This invention discloses a request distribution method, apparatus, storage medium, and electronic device. The method includes: receiving a query request, wherein the query request includes a user identifier, and the user identifier includes a data center location identifier; determining a target data center corresponding to the query request based on the data center location identifier; and sending the query request to a user center server corresponding to the target data center to query user data corresponding to the user identifier. The above technical content, by determining the target data center through the data center location identifier in the user identifier and sending the request to the user center server corresponding to the target data center, achieves automatic distribution of query requests. Compared with existing technologies, this invention does not require the development of a dedicated request interface, and user data can be added at any time through the user identifier, improving the flexibility of request distribution.

Description

Technical Field

[0001] This invention relates to the field of resource allocation technology, and in particular to a request distribution method, apparatus, storage medium, and electronic device. Background Technology

[0002] In some hybrid cloud application scenarios, such as data-sensitive scenarios like healthcare and government affairs, different organizations may use different cloud vendors, and the servers may be located in different regions.

[0003] To enable data exchange between different hybrid clouds and different vendors, the existing technology typically adopts the following approach: develop a dedicated local data request interface to separate data from different regions and data centers in the process. When data from a specific region is needed, the corresponding interface is called.

[0004] However, by developing dedicated interfaces, upstream systems need to be aware of the specific interfaces of downstream systems and invest R&D resources in business process redesign. Furthermore, when a new region or data center needs to be added, the entire business chain needs to be adjusted, which is inflexible. Summary of the Invention

[0005] This invention provides a request distribution method, apparatus, storage medium, and electronic device to achieve improved flexibility in request distribution without the need for dedicated request interface development.

[0006] In a first aspect, embodiments of the present invention provide a request distribution method, comprising: receiving a query request, wherein the query request includes a user identifier, and the user identifier includes a data center location identifier;

[0007] The target data center corresponding to the query request is determined based on the data center location identifier;

[0008] The query request is sent to the user center server corresponding to the target data center to query the user data corresponding to the user identifier.

[0009] Secondly, embodiments of the present invention also provide a request distribution apparatus, comprising:

[0010] A request receiving module is used to receive query requests, wherein the query request includes a user identifier, and the user identifier includes a computer room location identifier;

[0011] The data center determination module is used to determine the target data center corresponding to the query request based on the data center location identifier.

[0012] The request distribution module is used to send the query request to the user center server corresponding to the target data center in order to query the user data corresponding to the user identifier.

[0013] Thirdly, embodiments of the present invention also provide an electronic device, the electronic device comprising:

[0014] One or more processors;

[0015] Storage device for storing one or more programs.

[0016] When the one or more programs are executed by the one or more processors, the one or more processors implement any of the request dispatch methods described in the embodiments of the present invention.

[0017] Fourthly, embodiments of the present invention also provide a storage medium containing computer-executable instructions, which, when executed by a computer processor, are used to perform any of the request dispatch methods described in the embodiments of the present invention.

[0018] This invention receives a query request, which includes a user identifier, and the user identifier includes a data center location identifier; determines the target data center corresponding to the query request based on the data center location identifier; and sends the query request to the user center server corresponding to the target data center to retrieve the user data corresponding to the user identifier. The above technical content, by determining the target data center through the data center location identifier in the user identifier and sending the query request to the user center server corresponding to the target data center, achieves automatic distribution of query requests. Compared with existing technologies, this invention does not require the development of a dedicated request interface, and the automatic distribution method based on user identifiers allows for the addition of users at any time, improving the flexibility of request distribution. Attached Figure Description

[0019] To more clearly illustrate the technical solutions of exemplary embodiments of the present invention, the accompanying drawings used in describing the embodiments are briefly introduced below. Obviously, the accompanying drawings described are only a portion of the drawings of the embodiments to be described in this invention, and not all of the drawings. For those skilled in the art, other drawings can be obtained from these drawings without any creative effort.

[0020] Figure 1 This is a flowchart illustrating a request distribution method provided in Embodiment 1 of the present invention;

[0021] Figure 2 This is a flowchart illustrating a request distribution method provided in Embodiment 2 of the present invention;

[0022] Figure 3 This is a schematic diagram of a request distribution method provided in Embodiment 2 of the present invention;

[0023] Figure 4 This is a flowchart illustrating a request distribution method provided in Embodiment 3 of the present invention;

[0024] Figure 5 This is a schematic diagram of the structure of a request distribution device provided in Embodiment 4 of the present invention;

[0025] Figure 6 This is a schematic diagram of the structure of an electronic device provided in Embodiment 5 of the present invention. Detailed Implementation

[0026] The present invention will now be described in further detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and not intended to limit it.

[0027] It should also be noted that, for ease of description, the accompanying drawings show only the parts relevant to the invention and not all of them. Before discussing exemplary embodiments in more detail, it should be mentioned that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although the flowcharts describe the operations (or steps) as sequential processes, many of the operations can be performed in parallel, concurrently, or simultaneously. Furthermore, the order of the operations can be rearranged. The process can be terminated when its operation is completed, but it may also have additional steps not included in the drawings. The process may correspond to a method, function, procedure, subroutine, subprogram, etc.

[0028] Example 1

[0029] Figure 1 This is a flowchart of a request distribution method provided in Embodiment 1 of the present invention. This embodiment is applicable to the automatic distribution of query requests in a hybrid cloud environment. The method can be executed by the request distribution device provided in this embodiment, which can be implemented by software and / or hardware and can be configured on an electronic computing device, such as a cloud server. Specifically, it includes the following steps:

[0030] S110. Receive a query request, wherein the query request includes a user identifier, and the user identifier includes a computer room location identifier.

[0031] The query request can be a data query request initiated by a user through the user center of the current data center, where the current data center refers to the local data center currently used by the user. Cloud providers include, but are not limited to, Alibaba Cloud, Tencent Cloud, China Telecom, AWS (China), and Huawei Cloud. It should be noted that the scenarios applied in this embodiment of the invention can include medical or government scenarios. Different institutions may use different cloud providers, be located in different regions, and use different data centers to store data. The query request may include, but is not limited to, a user identifier and requested data. The user identifier is a unique identifier for the queried user, and user data can be accurately matched through the user identifier. The user identifier includes, but is not limited to, a data center location identifier, which can be the location identifier of the data center where the user data is stored.

[0032] Optionally, the data center location identifier includes a vendor code, a region code, and a data center code. The vendor code refers to the code of the cloud vendor whose business system is deployed, and can be represented by a preset number of digits; for example, 10 can represent Alibaba Cloud, 11 represents Tencent Cloud, and 12 represents Huawei Cloud. The region code refers to the geographical location code of the cloud vendor's data center, and can also be represented by a preset number of digits. For example, the geographical location can be divided by city; for instance, 0001 can represent Beijing, and 0002 can represent Shanghai. The data center code can be a specific number for the data center. It is understood that within the same region, a cloud vendor may have multiple data centers, which can be distinguished by their numbers.

[0033] Optionally, the user identifier also includes a random number of preset digits. The random number is a randomly generated multi-digit data set, and by setting the random number, it is possible to distinguish between multiple user data sets within the same computer room.

[0034] S120. Determine the target data center corresponding to the query request based on the data center location identifier.

[0035] The target data center refers to the data center where the user data corresponding to the user identifier is stored.

[0036] Specifically, in some embodiments, the location of the target data center can be directly determined by the data center location identifier, and the query request can be sent to the user center server corresponding to the target data center, enabling cloud access to data from each data center; in another embodiment, the location of the data center can be determined based on the data center location identifier to determine whether the user data corresponding to the query request is in the current data center, and the target data center can be determined based on the determination result, which can ensure the local storage of critical data while meeting the operational needs of the cloud.

[0037] S130. Send the query request to the user center server corresponding to the target computer room to query the user data corresponding to the user identifier.

[0038] The user center server refers to the server used by the user center system. User data can be queried through the user center server, specifically by querying user data in the user database using SQL.

[0039] This invention provides a request distribution method. It involves receiving a query request, wherein the query request includes a user identifier, and the user identifier includes a data center location identifier; determining the target data center corresponding to the query request based on the data center location identifier; and sending the query request to the user center server corresponding to the target data center to query the user data corresponding to the user identifier. This method, by determining the target data center through the data center location identifier in the user identifier and sending the query request to the user center server corresponding to the target data center, achieves automatic distribution of query requests. Compared with existing technologies, this invention does not require the development of a dedicated request interface, and the automatic distribution method based on user identifiers allows for the addition of users at any time, improving the flexibility of request distribution.

[0040] Example 2

[0041] Figure 2 This is a flowchart illustrating a request distribution method according to Embodiment 2 of the present invention. Based on the above embodiments, the step of "determining the target data center corresponding to the query request based on the data center location identifier" is further refined. For a detailed description of its implementation, please refer to the technical solution below. Technical terms that are the same as or corresponding to those in the above embodiments will not be repeated here. Figure 2 As shown, the method of this embodiment of the invention specifically includes the following steps:

[0042] S210. Receive a query request, wherein the query request includes a user identifier, and the user identifier includes a computer room location identifier.

[0043] S220. Based on the data center location identifier, determine whether the user data corresponding to the query request is in the current data center. If so, determine the current data center as the target data center.

[0044] The current data center refers to the local cloud provider's data center where the user initiates the query request.

[0045] Specifically, if the identifier of the current data center is the same as the data center location identifier, then the current data center is identified as the target data center, and it indicates that the user data corresponding to the query request is stored in the local data center. The identifier of the current data center includes the vendor code, the region code, and the data center code.

[0046] S230. If not, the query request will be sent to the target data center according to the data center location identifier.

[0047] If the identifier corresponding to the current data center is different from the data center location identifier, it indicates that the user data requested in the query is not stored in the local data center and needs to be remotely accessed from other cloud providers.

[0048] Specifically, based on the vendor code, region code, and data center code in the data center location identifier, the data center where the user data corresponding to the user identifier is located is determined, and this data center is identified as the target data center. The query request received by the local data center user center is then sent to the remote target data center.

[0049] Based on the above embodiments, after the query request is sent to the target data center according to the data center location identifier, the user center of the target data center is used to determine whether the user data corresponding to the query request is in the current data center based on the data center location identifier.

[0050] For example, Figure 3 This is a schematic diagram illustrating request distribution in an embodiment of the present invention. Cloud vendor B's user center receives a query request from a user and extracts the user identifier from the query request. Further, it determines whether the user data corresponding to the user identifier is stored in the current data center. If so, the data center is designated as the target data center, and the data is queried using the query request. If not, the query request is sent to cloud vendor A's user center, where it is again determined whether the user data corresponding to the user identifier is stored in the current data center. Specifically, the user identifier is extracted from the query request, and the user data corresponding to the user identifier is determined based on the user identifier. If so, the data center is designated as the target data center, and the data is queried using the query request. In this embodiment of the present invention, performing a second determination on the user identifier can prevent the occurrence of request sending errors.

[0051] It should be noted that the user center is unaware that the query request is forwarded. Therefore, every time the user center receives a query request, it will determine whether the user data corresponding to the user identifier is stored in the current data center.

[0052] S240. Send the query request to the user center server corresponding to the target computer room to query the user data corresponding to the user identifier.

[0053] This invention provides a request distribution method. It involves receiving a query request, where the query request includes a user identifier, and the user identifier includes a data center location identifier. Based on the data center location identifier, it determines whether the user data corresponding to the query request is in the current data center. If so, the current data center is designated as the target data center; otherwise, the query request is sent to the target data center according to the data center location identifier. The query request is then sent to the user center server corresponding to the target data center to retrieve the user data corresponding to the user identifier. This method, by determining the target data center through the data center location identifier in the user identifier and sending the query request to the user center server corresponding to the target data center, achieves automatic distribution of query requests. Compared with existing technologies, this invention eliminates the need for developing a dedicated request interface and allows for the addition of users at any time through automatic distribution based on user identifiers, thus improving the flexibility of request distribution.

[0054] Example 3

[0055] Figure 4 This is a flowchart illustrating a request distribution method according to Embodiment 3 of the present invention. The embodiments of the present invention can be combined with the optional solutions in the above embodiments. Optionally, in this embodiment, before receiving a query request, the method further includes: receiving a registration request, wherein the registration request includes user source information and regional information, and the user source information includes vendor information and data center information; and generating a user identifier based on the user source information and regional information.

[0056] like Figure 4 As shown, the method of this embodiment of the invention specifically includes the following steps:

[0057] S310. Receive a registration request, the registration request including user source information and region information, the user source information including manufacturer information and data center information.

[0058] The registration request is triggered when a user registers an account. The registration request includes user source information and regional information. The user source information includes vendor information and data center information. Vendor information refers to the cloud vendor's information, data center information refers to the data center number information, and regional information refers to the geographical location of the data center used during registration, which can be obtained through the IP address.

[0059] S320. Generate a user identifier based on the user source information and region information.

[0060] For example, user source information and regional information are encoded, that is, the vendor, region and data center are represented in the form of numerical codes. For example, the number 10 can be used to represent the cloud vendor, the number 350303 can be used to represent the region, and 01 can be used to represent the data center. Then, a random number of preset digits is added and arranged in sequence to form the user identifier.

[0061] Based on the above embodiments, after generating a user identifier based on the user source information and region information, the method further includes: obtaining user data to be stored, and sending the user data and the corresponding user identifier to the database server corresponding to the user identifier, so that the database server associates and stores the user data with the corresponding user identifier.

[0062] The user data to be stored can be the user information filled in during user registration. The database server can be used to store the user data and establish a connection with the user identifier.

[0063] In this embodiment of the invention, the database server associates and stores user data with corresponding user identifiers, which facilitates subsequent data retrieval by user identifier and improves data search efficiency.

[0064] S330. Receive a query request, wherein the query request includes a user identifier, and the user identifier includes a computer room location identifier.

[0065] S340. Determine the target data center corresponding to the query request based on the data center location identifier.

[0066] S350. Send the query request to the user center server corresponding to the target computer room to query the user data corresponding to the user identifier.

[0067] This invention provides a request distribution method. It receives a registration request, which includes user source information and regional information. The user source information includes vendor information and data center information. A user identifier is generated based on the user source information and regional information. This method achieves automatic generation of the user identifier and provides a user identifier containing vendor information, regional information, and data center information for subsequent request distribution. Further, it receives a query request, which includes a user identifier and a data center location identifier. The target data center corresponding to the query request is determined based on the data center location identifier. The query request is then sent to the user center server corresponding to the target data center to query the user data corresponding to the user identifier. The above technical content, by determining the target data center through the data center location identifier in the user identifier and sending the query request to the user center server corresponding to the target data center, achieves automatic distribution of query requests. Compared with existing technologies, this invention does not require the development of a dedicated request interface, and the automatic distribution of user identifiers allows for the addition of users at any time, improving the flexibility of request distribution.

[0068] Example 4

[0069] Figure 5This is a schematic diagram of a request distribution device according to Embodiment 4 of the present invention. The request distribution device provided in this embodiment can be implemented by software and / or hardware, and can be configured in a terminal and / or server to implement the request distribution method in the embodiments of the present invention. The device may specifically include: a request receiving module 410, a data center determination module 420, and a request distribution module 430.

[0070] The system includes a request receiving module 410 for receiving a query request, wherein the query request includes a user identifier, and the user identifier includes a data center location identifier; a data center determination module 420 for determining the target data center corresponding to the query request based on the data center location identifier; and a request distribution module 430 for sending the query request to the user center server corresponding to the target data center to query the user data corresponding to the user identifier.

[0071] This invention provides a request distribution device that receives query requests, wherein the query request includes a user identifier, and the user identifier includes a data center location identifier; determines the target data center corresponding to the query request based on the data center location identifier; and sends the query request to the user center server corresponding to the target data center to query the user data corresponding to the user identifier. The above technical content, by determining the target data center through the data center location identifier in the user identifier and sending the query request to the user center server corresponding to the target data center, achieves automatic distribution of query requests. Compared with the prior art, this invention does not require the development of a dedicated request interface, and the automatic distribution method based on user identifiers allows for the addition of users at any time, improving the flexibility of request distribution.

[0072] Based on any optional technical solution in the embodiments of the present invention, the data center location identifier may optionally include a manufacturer code, a region code, and a data center code.

[0073] Based on any optional technical solution in the embodiments of the present invention, the user identifier may optionally include a random number of preset lengths.

[0074] Based on any optional technical solution in the embodiments of the present invention, the computer room determination module 420 may optionally be used for:

[0075] Based on the data center location identifier, determine whether the user data corresponding to the query request is in the current data center. If so, determine the current data center as the target data center.

[0076] If not, the query request will be sent to the target data center based on the data center location identifier.

[0077] Based on any optional technical solution in the embodiments of the present invention, optionally, after the query request is sent to the target data center according to the data center location identifier, the user center of the target data center is used to determine whether the user data corresponding to the query request is in the current data center based on the data center location identifier.

[0078] Based on any optional technical solution in the embodiments of the present invention, optionally, before receiving the query request, the device may also be used for:

[0079] Receive a registration request, the registration request including user source information and region information, the user source information including manufacturer information and data center information;

[0080] A user identifier is generated based on the user's source information and region information.

[0081] Optionally, based on any of the optional technical solutions in the embodiments of the present invention, the device may also be used for:

[0082] The system retrieves user data to be stored and sends the user data and the corresponding user identifier to the database server corresponding to the user identifier, so that the database server associates and stores the user data with the corresponding user identifier.

[0083] The request distribution apparatus provided in the embodiments of the present invention can execute the request distribution method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0084] Example 5

[0085] Figure 6 This is a schematic diagram of the structure of an electronic device provided in Embodiment 5 of the present invention. Figure 6 A block diagram is shown of an exemplary electronic device 12 suitable for implementing embodiments of the present invention. Figure 6 The electronic device 12 shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of the present invention.

[0086] like Figure 6 As shown, the electronic device 12 is represented in the form of a general-purpose computing device. The components of the electronic device 12 may include, but are not limited to: one or more processors or processing units 16, system memory 28, and bus 18 connecting different system components (including system memory 28 and processing unit 16).

[0087] Bus 18 represents one or more of several bus architectures, including a memory bus or memory controller, a peripheral bus, a graphics acceleration port, a processor, or a local bus using any of the various bus architectures. For example, these architectures include, but are not limited to, the Industry Standard Architecture (ISA) bus, the Micro Channel Architecture (MAC) bus, the Enhanced ISA bus, the Video Electronics Standards Association (VESA) local bus, and the Peripheral Component Interconnect (PCI) bus.

[0088] Electronic device 12 typically includes a variety of computer system readable media. These media can be any available media that can be accessed by electronic device 12, including volatile and non-volatile media, removable and non-removable media.

[0089] System memory 28 may include computer system readable media in the form of volatile memory, such as random access memory (RAM) 30 and / or cache memory 32. Electronic device 12 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, storage system 34 may be used to read and write non-removable, non-volatile magnetic media (… Figure 6 Not shown; usually referred to as a "hard drive"). Although Figure 6 Not shown, a disk drive for reading and writing to a removable non-volatile disk (e.g., a "floppy disk") and an optical disk drive for reading and writing to a removable non-volatile optical disk (e.g., a CD-ROM, DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to bus 18 via one or more data media interfaces. System memory 28 may include at least one program product having a set (e.g., at least one) of program modules configured to perform the functions of the embodiments of the present invention.

[0090] A program / utility 36 having a set (at least one) of program modules 26 may be stored, for example, in system memory 28. Such program modules 26 include, but are not limited to, an operating system, one or more application programs, other program modules, and program data. Each or some combination of these examples may include an implementation of a network environment. Program modules 26 typically perform the functions and / or methods described in the embodiments of the present invention.

[0091] Electronic device 12 can also communicate with one or more external devices 14 (e.g., keyboard, pointing device, display 24, etc.), and with one or more devices that enable a user to interact with the electronic device 12, and / or with any device that enables the electronic device 12 to communicate with one or more other computing devices (e.g., network card, modem, etc.). This communication can be performed through input / output (I / O) interface 22. Furthermore, electronic device 12 can also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public networks, such as the Internet) via network adapter 20. Figure 6 As shown, network adapter 20 communicates with other modules of electronic device 12 via bus 18. It should be understood that, although... Figure 6 As not shown, other hardware and / or software modules may be used in conjunction with electronic device 12, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0092] The processing unit 16 executes various functional applications and data processing by running programs stored in the system memory 28, such as implementing a request distribution method provided in this embodiment.

[0093] Example 6

[0094] Embodiment 6 of the present invention also provides a storage medium containing computer-executable instructions, which, when executed by a computer processor, are used to perform a request dispatch method, the method comprising:

[0095] Receive a query request, wherein the query request includes a user identifier, and the user identifier includes a data center location identifier;

[0096] The target data center corresponding to the query request is determined based on the data center location identifier;

[0097] The query request is sent to the user center server corresponding to the target data center to query the user data corresponding to the user identifier.

[0098] The computer storage medium of this invention can be any combination of one or more computer-readable media. A computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples (a non-exhaustive list) of computer-readable storage media include: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this document, a computer-readable storage medium can be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

[0099] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, capable of sending, propagating, or transmitting programs for use by or in connection with an instruction execution system, apparatus, or device.

[0100] Program code contained on a computer-readable medium may be transmitted using any suitable medium, including—but not limited to—wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.

[0101] Computer program code for performing the operations of embodiments of the present invention can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, and conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0102] Note that the above description is merely a preferred embodiment of the present invention and the technical principles employed. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and various obvious changes, readjustments, and substitutions can be made without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in detail through the above embodiments, the present invention is not limited to the above embodiments, and may include many other equivalent embodiments without departing from the concept of the present invention, the scope of which is determined by the scope of the appended claims.

Claims

1. A request dispatching method, characterized in that, include: Receive a query request, wherein the query request includes a user identifier, and the user identifier includes a data center location identifier; The target data center corresponding to the query request is determined based on the data center location identifier; wherein, the target data center is the data center where the user data corresponding to the user identifier is stored; The query request is sent to the user center server corresponding to the target data center to query the user data corresponding to the user identifier; Determining the target data center corresponding to the query request based on the data center location identifier includes: Based on the data center location identifier, determine whether the user data corresponding to the query request is in the current data center. If so, determine the current data center as the target data center. If not, the query request will be sent to the target data center based on the data center location identifier; After the query request is sent to the target data center based on the data center location identifier, the user center of the target data center is used to determine whether the user data corresponding to the query request is in the current data center based on the data center location identifier; Before receiving a query request, the method further includes: Receive a registration request, the registration request including user source information and region information, the user source information including manufacturer information and data center information; A user identifier is generated based on the user source information and region information; After generating a user identifier based on the user source information and region information, the method further includes: The system retrieves user data to be stored and sends the user data and the corresponding user identifier to the database server corresponding to the user identifier, so that the database server associates and stores the user data with the corresponding user identifier.

2. The method according to claim 1, characterized in that, The location identifier for the computer room includes the manufacturer code, the region code, and the computer room code.

3. The method according to claim 2, characterized in that, The user identifier also includes a random number of preset digits.

4. A request distribution device, characterized in that, include: A request receiving module is used to receive query requests, wherein the query request includes a user identifier, and the user identifier includes a computer room location identifier; The data center determination module is used to determine the target data center corresponding to the query request based on the data center location identifier; wherein, the target data center is the data center where the user data corresponding to the user identifier is stored; The request distribution module is used to send the query request to the user center server corresponding to the target data center in order to query the user data corresponding to the user identifier; The computer room determination module can be used for: Based on the data center location identifier, determine whether the user data corresponding to the query request is in the current data center. If so, determine the current data center as the target data center. If not, the query request will be sent to the target data center based on the data center location identifier; Wherein, after the query request is sent to the target data center according to the data center location identifier, the user center of the target data center is used to determine whether the user data corresponding to the query request is in the current data center based on the data center location identifier; Before receiving a query request, the device is also used to: Receive a registration request, the registration request including user source information and region information, the user source information including manufacturer information and data center information; A user identifier is generated based on the user source information and region information; The device is also specifically used for: The system retrieves user data to be stored and sends the user data and the corresponding user identifier to the database server corresponding to the user identifier, so that the database server associates and stores the user data with the corresponding user identifier.

5. An electronic device, characterized in that, The electronic device includes: One or more processors; Storage device for storing one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors implement the request dispatch method as described in any one of claims 1-3.

6. A storage medium containing computer-executable instructions, characterized in that, The computer-executable instructions, when executed by a computer processor, are used to perform the request dispatch method as described in any one of claims 1-3.

Images