WO2021114890A1

WO2021114890A1 - Access request distribution method and related device

Info

Publication number: WO2021114890A1
Application number: PCT/CN2020/122919
Authority: WO
Inventors: 席维成
Original assignee: 平安科技（深圳）有限公司
Priority date: 2020-07-30
Filing date: 2020-10-22
Publication date: 2021-06-17
Also published as: CN111914150A

Abstract

The present application relates to the technical field of computers, and provides an access request distribution method and related device. In the access request distribution method, a first access request is received from a requesting terminal; the access type of the requesting terminal is determined according to the first access request; if the access type of the requesting terminal is a webpage request, then a target system is determined from among a plurality of systems according to a service identifier of the first access request; a COOKIE identifier is returned to the requesting terminal by means of the target system, causing the requesting terminal to store the COOKIE identifier; a second access request carrying a COOKIE identifier is received from the requesting terminal; the second access request is distributed to the target system according to the COOKIE identifier in the second access request. The present application can be applied to fields such as smart cities, and thus can promote the construction of smart cities. The present application distributes access requests, balancing the access pressure of a system to be accessed, improving the stability of the system to be accessed.

Description

Access request shunt method and related equipment

This application claims to be submitted to the Chinese Patent Office on July 30, 2020. The application number is 202010754519.4. The application titled "Access request shunting method and related equipment" is the priority of the Chinese patent application, the entire content of which is incorporated into this application by reference.

Technical field

This application relates to the field of computer technology, and in particular to a method, device, computer equipment, and computer-readable storage medium for offloading access requests.

Background technique

Currently, the systems to be visited that provide access services include multiple systems. For example, smart city systems include smart government systems, smart medical systems, and smart transportation systems. The inventor realizes that the amount of data in the access request to the system to be accessed is too large, which increases the pressure on the system to be accessed, causing the server to be prone to problems such as interruption, unresponsiveness, response timeout, and response time being too long, resulting in the stability of the system to be accessed reduce.

How to improve the stability of the system to be accessed has become a problem to be solved.

Summary of the invention

In view of the above, it is necessary to propose a method, device, computer equipment, and computer-readable storage medium for shunting access requests, which can shunt access requests, balance the access pressure of the system to be accessed including multiple systems, and improve the system to be accessed The stability.

The first aspect of the present application provides a method for offloading access requests, and the method for offloading access requests includes:

Receiving the first access request from the requesting end;

Judging the access type of the requesting end according to the first access request;

When the access type of the requesting end is a web page request, determining a target system from multiple systems according to the service identifier of the first access request;

Returning the COOKIE identifier to the requesting terminal through the target system, so that the requesting terminal stores the COOKIE identifier;

Receiving a second access request carrying the cookie identifier from the requesting end;

The second access request is diverted to the target system according to the COOKIE identifier in the second access request.

A second aspect of the present application provides an access request distribution device, the access request distribution device including:

The first receiving module is configured to receive the first access request from the requesting end;

A judging module, configured to judge the access type of the requesting end according to the first access request;

A determining module, configured to determine a target system from multiple systems according to the service identifier of the first access request when the access type of the requesting end is a web page request;

The return module is used to return the COOKIE identifier to the requesting terminal through the target system, so that the requesting terminal stores the COOKIE identifier;

A second receiving module, configured to receive a second access request carrying the cookie identifier from the requesting end;

The offloading module is configured to offload the second access request to the target system according to the cookie identifier in the second access request.

A third aspect of the present application provides a computer device that includes a processor, and the processor is configured to execute computer-readable instructions stored in a memory to implement the following steps:

Receiving the first access request from the requesting end;

A fourth aspect of the present application provides a computer-readable storage medium having computer-readable instructions stored on the computer-readable storage medium, and when the computer-readable instructions are executed by a processor, the following steps are implemented:

Receiving the first access request from the requesting end;

This application receives the first access request of the requesting end; judges the access type of the requesting end according to the first access request; when the access type of the requesting end is a webpage request, according to the service identification of the first access request The target system is determined in the system; the cookie identifier is returned to the requesting terminal through the target system, so that the requesting terminal stores the cookie identifier; receiving the second access request carrying the cookie identifier from the requesting terminal; The COOKIE identifier in the second access request diverts the second access request to the target system. This application diverts different types of access requests, diverts the access requests to the target system, balances the access pressure of the system to be accessed including multiple systems, and improves the stability of the system to be accessed.

Description of the drawings

Fig. 1 is a flowchart of an access request offloading method provided by an embodiment of the present application.

Fig. 2 is a structural diagram of an access request shunting device provided by an embodiment of the present application.

Fig. 3 is a schematic diagram of a computer device provided by an embodiment of the present application.

Detailed ways

In order to be able to understand the above objectives, features and advantages of the application more clearly, the application will be described in detail below with reference to the accompanying drawings and specific embodiments. It should be noted that the embodiments of the application and the features in the embodiments can be combined with each other if there is no conflict.

In the following description, many specific details are set forth in order to fully understand the present application. The described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative work shall fall within the protection scope of this application.

Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the technical field of this application. The terms used in the specification of the application herein are only for the purpose of describing specific embodiments, and are not intended to limit the application.

Preferably, the access request shunting method of this application is applied to one or more computer devices. The computer device is a device that can automatically perform numerical calculation and/or information processing in accordance with pre-set or stored instructions. Its hardware includes, but is not limited to, a microprocessor and an application specific integrated circuit (ASIC) , Programmable Gate Array (Field-Programmable Gate Array, FPGA), Digital Processor (Digital Signal Processor, DSP), embedded equipment, etc.

This application can be used in many general or special computer system environments or configurations. For example: personal computers, server computers, handheld devices or portable devices, tablet devices, multi-processor systems, microprocessor-based systems, set-top boxes, programmable consumer electronic devices, network PCs, small computers, large computers, including Distributed computing environment for any of the above systems or equipment, etc. This application may be described in the general context of computer-executable instructions executed by a computer, such as a program module. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. This application can also be practiced in distributed computing environments. In these distributed computing environments, tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules can be located in local and remote computer storage media including storage devices.

The computer device may be a computing device such as a desktop computer, a notebook, a palmtop computer, and a cloud server. The computer device can interact with the user through a keyboard, a mouse, a remote control, a touch panel, or a voice control device.

Example one

FIG. 1 is a flowchart of a method for offloading access requests provided in Embodiment 1 of the present application. The access request shunting method is applied to computer equipment, and is used to shunt access requests, balance the access pressure of the system to be accessed including multiple systems, and improve the stability of the system to be accessed.

The access request distribution method specifically includes the following steps. According to different requirements, the sequence of the steps in the flowchart can be changed, and some of the steps can be omitted.

101. Receive a first access request from the requesting end.

The requesting terminal may include a mobile terminal or a PC terminal. The first access request of the mobile terminal can be received, or the first access request of the PC terminal can be received.

The first access request may include type identification, service identification, description information of the target data that needs to be requested, and the like.

In a specific embodiment, when the requester needs to provide services from multiple systems to be accessed, or needs to request target data, the requester sends all the data to one of the multiple systems through the offload server (computer equipment). The first access request. The first access request of the requesting end is received based on TCP (Transmission Control Protocol) or UDP (User Datagram Protocol).

102. Determine the access type of the requesting end according to the first access request.

When the first access request is received, the type identifier may be extracted from the first access request, and the access type of the requesting end may be determined according to the type identifier of the first access request.

The access type of the requester includes a web page request, an interface call request, and the like.

For example, when the type identifier of the first access request is "1", it is determined that the access type of the requesting end is an interface call request; when the type identifier of the first access request is "2", it is determined that the access type of the requesting end is a web page request. The type identification of the first access request may also include other character identifications.

103. When the access type of the requesting end is a web page request, determine a target system from multiple systems according to the service identifier of the first access request.

In a specific embodiment, the determining a target system from a plurality of systems according to the service identifier of the first access request includes:

Acquiring a service routing table, where the service routing table includes associated stored service identifiers and systems;

Using the service identifier of the first access request as a key to query the system associated with the service identifier of the first access request from the service routing table;

When a system associated with the service identifier of the first access request is queried from the service routing table using the service identifier of the first access request as a key, the queried system is determined as the target system.

For example, the business routing table stores the mapping relationship between the business identifier and the system as "yh=prd1, cx=prd2", where "yh" and "cx" are business identifiers, "=" is a one-to-one mapping relationship, and "prd1" "And "prd2" are systems (including system routing). The system can include a service system, a called system, and so on. Can the first visit request https://xxx.paic.com.cn/login? In biz=yh, the business ID of the first access request extracted according to the keyword "biz" is "yh", and the business routing table is queried from the business routing table with the first access request’s business ID "yh" as the key. The system associated with the business identity is "prd1". When the system associated with the service identifier of the first access request is "prd1" as the key of the service routing table query with the service identifier of the first access request, "prd1" is determined as the target system.

104. Return the COOKIE identifier to the requesting terminal through the target system, so that the requesting terminal stores the COOKIE identifier.

In a specific embodiment, the returning the COOKIE (data stored on the user's local terminal) identifier to the requesting end through the target system includes:

The first access request is forwarded to the target system, so that the target system generates the cookie identifier, and returns the cookie to the requesting end in response to the first access request.

When forwarding the first access request to the target system, the target system intercepts the first access request through the pre-interceptor of the target system, and recognizes the access in the first access request When the type is a web page request, the cookie identifier is generated, and the cookie identifier is written into the response information returned to the requester.

In another embodiment, the method for offloading access requests further includes:

When the system associated with the service ID of the first access request is not queried from the service routing table using the service ID of the first access request as a key, prompt information is returned to the requesting end to remind the access Something went wrong.

As in the above example, when the service ID of the first access request is "hh", the service ID "hh" of the first access request is used as the key, and the system associated with the service ID of the first access request is not queried from the service routing table. , Return a prompt message (such as 404) to the requester to remind the access error.

105. Receive a second access request carrying the COOKIE identifier from the requesting end.

In a specific embodiment, the first access request may be a same-domain cascading request of the first access request, and the second access request carries the cookie identifier.

When the requesting end receives the response information returned by the target system in response to the first access request, it writes the COOKIE identifier in the response information to the requesting end.

106. Offload the second access request to the target system according to the COOKIE identifier in the second access request.

In a specific embodiment, the offloading the second access request to the target system according to the cookie identifier in the second access request includes:

According to the target data description information in the second access request, determine whether the target data is stored locally on the requesting end;

When the requesting end stores the target data, returning a local read identifier to the requesting end, so that the requesting end can read the target data from the requesting end;

When the requesting end does not store the target data, the second access request is sent to the target system, and the target data is sent to the requesting end through the target system.

When the requesting end stores the target data, it returns a local read identifier to the requesting end, so that the requesting end reads the target data from the requesting end, so that the requesting end does not need to read the target data from the requesting end. The target system obtains the target data.

When the access type of the requesting end is an interface call request, the first access request is diverted to a designated system according to the service identifier of the first access request.

According to the access type of the requesting side, the requesting side's access request is diverted to different systems.

Acquiring the first time point when the first access request is received;

Acquiring a second time point when the second access request is received;

Calculating the time difference between the first time point and the second time point;

When the time difference exceeds the preset time difference, a reminder message of request timeout is sent to the requesting terminal to remind the requesting terminal to obtain the COOKIE identifier again.

The access request offloading method of the first embodiment receives the first access request of the requesting end; judges the access type of the requesting end according to the first access request; when the access type of the requesting end is a webpage request, according to the first access request The service identification of the service identifies the target system from multiple systems; the cookie identification is returned to the requesting end through the target system, so that the requesting end stores the cookie identification; receiving the requesting end’s second carrying the cookie identification 2. Access request; according to the COOKIE identifier in the second access request, the second access request is diverted to the target system. The first embodiment realizes the demand for the business to monopolize a system, and meets the requirements of the requesting side for system security and stability; isolates different request flows to different systems, and when the request volume on a certain system increases suddenly or the business fails , And also ensure that other systems are not affected. This application diverts different types of access requests, diverts the access requests to the target system, balances the access pressure of the system to be accessed including multiple systems, and improves the stability of the system to be accessed.

Example two

Fig. 2 is a structural diagram of an access request shunting device provided in the second embodiment of the present application. The access request shunting device 20 is applied to computer equipment. The access request shunting device 20 is used to shunt access requests, balance the access pressure of the system to be accessed including multiple systems, and improve the stability of the system to be accessed.

As shown in FIG. 2, the access request shunting device 20 may include a first receiving module 201, a judging module 202, a determining module 203, a returning module 204, a second receiving module 205, and a shunting module 206.

The first receiving module 201 is configured to receive the first access request from the requesting end.

The judging module 202 is configured to judge the access type of the requesting end according to the first access request.

The determining module 203 is configured to determine a target system from multiple systems according to the service identifier of the first access request when the access type of the requesting end is a web page request.

The return module 204 is configured to return the COOKIE identifier to the requesting terminal through the target system, so that the requesting terminal stores the COOKIE identifier.

In another embodiment, the return module is further configured to use the service identifier of the first access request as a key to find no information associated with the service identifier of the first access request from the service routing table. In the case of the system, a prompt message is returned to the requesting end to remind the access error.

The second receiving module 205 is configured to receive a second access request carrying the COOKIE identifier from the requesting end.

The offloading module 206 is configured to offload the second access request to the target system according to the cookie identifier in the second access request.

In another embodiment, the offloading module is further configured to offload the first access request to a designated system according to the service identifier of the first access request when the access type of the requesting end is an interface call request.

In another embodiment, the access request shunting device further includes a reminder module, configured to obtain the first time point when the first access request is received;

Acquiring a second time point when the second access request is received;

The access request shunting device 20 of the second embodiment realizes the demand for the business to monopolize a system, and meets the requirements of the requesting end for system security and stability; separates different request flows to different systems, when the request volume on a certain system In the event of a sudden increase or business failure, it is also ensured that other systems are not affected. In the second embodiment, different types of access requests are diverted, the access requests are diverted to the target system, the access pressure of the system to be accessed including multiple systems is balanced, and the stability of the system to be accessed is improved.

Example three

This embodiment provides a computer-readable storage medium having computer-readable instructions stored thereon. The computer-readable storage medium may be non-volatile or volatile. When the computer-readable instruction is executed by the processor, the steps in the embodiment of the access request offloading method are realized, for example, steps 101-106 shown in FIG. 1:

101. Receive a first access request from the requesting end;

102. Judging the access type of the requesting end according to the first access request;

103. When the access type of the requesting end is a web page request, determine a target system from multiple systems according to the service identifier of the first access request;

104. Return the COOKIE identifier to the requesting terminal through the target system, so that the requesting terminal stores the COOKIE identifier;

105. Receive a second access request carrying the cookie identifier from the requesting end;

Or, when the computer-readable instruction is executed by the processor, the function of each module in the above-mentioned device embodiment is realized, for example, the modules 201-206 in FIG. 2:

The first receiving module 201 is configured to receive the first access request from the requesting end;

The judging module 202 is configured to judge the access type of the requesting end according to the first access request;

The determining module 203 is configured to determine a target system from multiple systems according to the service identifier of the first access request when the access type of the requesting end is a web page request;

The return module 204 is configured to return the COOKIE identifier to the requesting terminal through the target system, so that the requesting terminal stores the COOKIE identifier;

The second receiving module 205 is configured to receive a second access request carrying the COOKIE identifier from the requesting end;

Example four

FIG. 3 is a schematic diagram of the computer equipment provided in the fourth embodiment of the application. The computer device 30 includes a memory 301, a processor 302, and computer-readable instructions 303 stored in the memory 301 and running on the processor 302, such as an access request shunt program. When the processor 302 executes the computer-readable instruction 303, the steps in the above-mentioned access request offloading method embodiment are implemented, for example, steps 101-106 shown in FIG. 1:

101. Receive a first access request from the requesting end;

Exemplarily, the computer-readable instruction 303 may be divided into one or more modules, and the one or more modules are stored in the memory 301 and executed by the processor 302 to complete the method. . The one or more modules may be a series of computer program instruction segments capable of completing specific functions, and the instruction segments are used to describe the execution process of the computer readable instruction 303 in the computer device 30. For example, the computer-readable instruction 303 can be divided into the first receiving module 201, the judging module 202, the determining module 203, the returning module 204, the second receiving module 205, and the shunting module 206 in FIG. 2. For the specific functions of each module, see实施例二。 Example two.

The computer device 30 may be a computing device such as a desktop computer, a notebook, a palmtop computer, and a cloud server. Those skilled in the art can understand that the schematic diagram 3 is only an example of the computer device 30, and does not constitute a limitation on the computer device 30. It may include more or less components than those shown in the figure, or combine certain components, or different components. For example, the computer device 30 may also include input and output devices, network access devices, buses, and so on.

The so-called processor 302 may be a central processing unit (Central Processing Unit, CPU), other general processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), Field-Programmable Gate Array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or the processor 302 can also be any conventional processor, etc. The processor 302 is the control center of the computer device 30, which uses various interfaces and lines to connect the entire computer device 30. Various parts.

The memory 301 may be used to store the computer-readable instructions 303, and the processor 302 executes or executes the computer-readable instructions or modules stored in the memory 301 and calls the data stored in the memory 301 to implement Various functions of the computer device 30. The memory 301 may mainly include a storage program area and a storage data area, where the storage program area may store an operating system, an application program required by at least one function (such as a sound playback function, an image playback function, etc.); the storage data area may Data and the like created in accordance with the use of the computer device 30 are stored. In addition, the memory 301 may include a hard disk, a memory, a plug-in hard disk, a smart memory card (Smart Media Card, SMC), a Secure Digital (SD) card, a flash memory card (Flash Card), at least one disk storage device, flash memory Devices, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), or other non-volatile/volatile storage devices.

If the integrated module of the computer device 30 is implemented in the form of a software function module and sold or used as an independent product, it may be stored in a computer-readable storage medium. The computer-readable storage medium may be non-volatile or volatile. Based on this understanding, this application implements all or part of the processes in the above-mentioned embodiments and methods, and can also be completed by instructing relevant hardware through computer-readable instructions, and the computer-readable instructions can be stored in a computer-readable storage medium. Here, when the computer-readable instruction is executed by the processor, it can implement the steps of the foregoing method embodiments. Wherein, the computer-readable instructions may be in the form of source code, object code, executable file, or some intermediate forms, etc. The computer-readable storage medium may include: any entity or device capable of carrying the computer-readable instructions, recording medium, U disk, mobile hard disk, magnetic disk, optical disk, read only memory (ROM), random access memory ( RAM).

In the several embodiments provided in this application, it should be understood that the disclosed system, device, and method can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the modules is only a logical function division, and there may be other division methods in actual implementation.

The modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical modules, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules can be selected according to actual needs to achieve the objectives of the solutions of the embodiments.

In addition, the functional modules in the various embodiments of the present application may be integrated into one processing module, or each module may exist alone physically, or two or more modules may be integrated into one module. The above-mentioned integrated modules can be implemented in the form of hardware, or in the form of hardware plus software functional modules.

The above-mentioned integrated modules implemented in the form of software functional modules may be stored in a computer-readable storage medium. The above-mentioned software function module is stored in a storage medium and includes several instructions to make a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor execute the access request described in each embodiment of this application Some steps of the shunt method.

For those skilled in the art, it is obvious that the present application is not limited to the details of the foregoing exemplary embodiments, and the present application can be implemented in other specific forms without departing from the spirit or basic characteristics of the application. Therefore, no matter from which point of view, the embodiments should be regarded as exemplary and non-limiting. The scope of this application is defined by the appended claims rather than the above description, and therefore it is intended to fall into the claims. All changes in the meaning and scope of the equivalent elements of are included in this application. Any associated diagram marks in the claims should not be regarded as limiting the claims involved. In addition, it is obvious that the word "including" does not exclude other modules or steps, and the singular does not exclude the plural. Multiple modules or devices stated in the system claims can also be implemented by one module or device through software or hardware. Words such as first and second are used to denote names, but do not denote any specific order.

Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the application and not to limit them. Although the application has been described in detail with reference to the preferred embodiments, those of ordinary skill in the art should understand that the technical solutions of the application can be Make modifications or equivalent replacements without departing from the spirit and scope of the technical solution of the present application.

Claims

A method for distributing access requests, the method for distributing access requests includes:

Receiving the first access request from the requesting end;

Judging the access type of the requesting end according to the first access request;

When the access type of the requesting end is a web page request, determining a target system from multiple systems according to the service identifier of the first access request;

Returning the COOKIE identifier to the requesting terminal through the target system, so that the requesting terminal stores the COOKIE identifier;

Receiving a second access request carrying the cookie identifier from the requesting end;

The second access request is diverted to the target system according to the COOKIE identifier in the second access request.
The access request distribution method according to claim 1, wherein the determining a target system from a plurality of systems according to the service identifier of the first access request comprises:

Acquiring a service routing table, where the service routing table includes associated stored service identifiers and systems;

Using the service identifier of the first access request as a key to query the system associated with the service identifier of the first access request from the service routing table;

When a system associated with the service identifier of the first access request is queried from the service routing table using the service identifier of the first access request as a key, the queried system is determined as the target system.
The access request distribution method according to claim 2, wherein the access request distribution method further comprises:

When the system associated with the service ID of the first access request is not queried from the service routing table using the service ID of the first access request as a key, prompt information is returned to the requesting end to remind the access Something went wrong.
The access request distribution method according to claim 1, wherein the access request distribution method further comprises:

When the access type of the requesting end is an interface call request, the first access request is diverted to a designated system according to the service identifier of the first access request.
The access request distribution method according to claim 1, wherein the returning the COOKIE identifier to the requesting end through the target system comprises:

The first access request is forwarded to the target system, so that the target system generates the cookie identifier, and returns the cookie to the requesting end in response to the first access request.
The access request offloading method according to claim 1, wherein the offloading the second access request to the target system according to the cookie identifier in the second access request comprises:

According to the target data description information in the second access request, determine whether the target data is stored locally on the requesting end;

When the requesting end stores the target data, returning a local read identifier to the requesting end, so that the requesting end can read the target data from the requesting end;

When the requesting end does not store the target data, the second access request is sent to the target system, and the target data is sent to the requesting end through the target system.
The access request distribution method according to claim 1, wherein the access request distribution method further comprises:

Acquiring the first time point when the first access request is received;

Acquiring a second time point when the second access request is received;

Calculating the time difference between the first time point and the second time point;

When the time difference exceeds the preset time difference, a reminder message of request timeout is sent to the requesting terminal to remind the requesting terminal to obtain the COOKIE identifier again.
An access request distribution device, wherein the access request distribution device includes:

The first receiving module is configured to receive the first access request from the requesting end;

A judging module, configured to judge the access type of the requesting end according to the first access request;

A determining module, configured to determine a target system from multiple systems according to the service identifier of the first access request when the access type of the requesting end is a web page request;

The return module is used to return the COOKIE identifier to the requesting terminal through the target system, so that the requesting terminal stores the COOKIE identifier;

A second receiving module, configured to receive a second access request carrying the cookie identifier from the requesting end;

The offloading module is configured to offload the second access request to the target system according to the cookie identifier in the second access request.
A computer device, wherein the computer device includes a processor, and the processor is configured to execute computer-readable instructions stored in a memory to implement the following steps:

Receiving the first access request from the requesting end;

Judging the access type of the requesting end according to the first access request;

When the access type of the requesting end is a web page request, determining a target system from multiple systems according to the service identifier of the first access request;

Returning the COOKIE identifier to the requesting terminal through the target system, so that the requesting terminal stores the COOKIE identifier;

Receiving a second access request carrying the cookie identifier from the requesting end;

The second access request is diverted to the target system according to the COOKIE identifier in the second access request.
The computer device according to claim 9, wherein the processor executes computer-readable instructions stored in the memory to realize the time when the target system is determined from a plurality of systems according to the service identifier of the first access request ,include:

Acquiring a service routing table, where the service routing table includes associated stored service identifiers and systems;

Using the service identifier of the first access request as a key to query the system associated with the service identifier of the first access request from the service routing table;

When a system associated with the service identifier of the first access request is queried from the service routing table using the service identifier of the first access request as a key, the queried system is determined as the target system.
11. The computer device of claim 10, wherein the processor executing the computer-readable instructions stored in the memory is further used to implement the following steps:

When the system associated with the service ID of the first access request is not queried from the service routing table using the service ID of the first access request as a key, prompt information is returned to the requesting end to remind the access Something went wrong.
9. The computer device of claim 9, wherein the processor executes the computer-readable instructions stored in the memory to further implement the following steps:

When the access type of the requesting end is an interface call request, the first access request is diverted to a designated system according to the service identifier of the first access request.
9. The computer device according to claim 9, wherein, when the processor executes the computer-readable instructions stored in the memory to realize the returning the COOKIE identifier to the requesting end through the target system, the method comprises:

The first access request is forwarded to the target system, so that the target system generates the cookie identifier, and returns the cookie to the requesting end in response to the first access request.
The computer device according to claim 9, wherein the processor executes computer-readable instructions stored in the memory to implement the shunting of the second access request according to the cookie identifier in the second access request To the target system, including:

According to the target data description information in the second access request, determine whether the target data is stored locally on the requesting end;

When the requesting end stores the target data, returning a local read identifier to the requesting end, so that the requesting end can read the target data from the requesting end;

When the requesting end does not store the target data, the second access request is sent to the target system, and the target data is sent to the requesting end through the target system.
9. The computer device of claim 9, wherein the processor executes the computer-readable instructions stored in the memory to further implement the following steps:

Acquiring the first time point when the first access request is received;

Acquiring a second time point when the second access request is received;

Calculating the time difference between the first time point and the second time point;

When the time difference exceeds the preset time difference, a reminder message of request timeout is sent to the requesting terminal to remind the requesting terminal to obtain the COOKIE identifier again.
A computer-readable storage medium having computer-readable instructions stored thereon, wherein the computer-readable instructions implement the following steps when executed by a processor:

Receiving the first access request from the requesting end;

Judging the access type of the requesting end according to the first access request;

When the access type of the requesting end is a web page request, determining a target system from multiple systems according to the service identifier of the first access request;

Returning the COOKIE identifier to the requesting terminal through the target system, so that the requesting terminal stores the COOKIE identifier;

Receiving a second access request carrying the cookie identifier from the requesting end;

The second access request is diverted to the target system according to the COOKIE identifier in the second access request.
15. The storage medium according to claim 16, wherein, when the computer-readable instructions are executed by the processor to implement the determination of the target system from a plurality of systems according to the service identifier of the first access request, the method comprises:

Acquiring a service routing table, where the service routing table includes associated stored service identifiers and systems;

Using the service identifier of the first access request as a key to query the system associated with the service identifier of the first access request from the service routing table;

When a system associated with the service identifier of the first access request is queried from the service routing table using the service identifier of the first access request as a key, the queried system is determined as the target system.
18. The storage medium of claim 17, wherein the computer-readable instructions are executed by the processor to further implement the following steps:

When the system associated with the service ID of the first access request is not queried from the service routing table using the service ID of the first access request as a key, prompt information is returned to the requesting end to remind the access Something went wrong.
15. The storage medium according to claim 16, wherein, when the computer-readable instructions are executed by the processor to realize the returning of the COOKIE identifier to the requesting end through the target system, the method comprises:

The first access request is forwarded to the target system, so that the target system generates the cookie identifier, and returns the cookie to the requesting end in response to the first access request.
The storage medium of claim 16, wherein the computer-readable instructions are executed by the processor to implement the offloading of the second access request to the cookie according to the COOKIE identifier in the second access request When the target system includes:

According to the target data description information in the second access request, determine whether the target data is stored locally on the requesting end;

When the requesting end stores the target data, returning a local read identifier to the requesting end, so that the requesting end can read the target data from the requesting end;

When the requesting end does not store the target data, the second access request is sent to the target system, and the target data is sent to the requesting end through the target system.