CN110225099B - Data processing method, front-end client, back-end server and storage medium - Google Patents
Data processing method, front-end client, back-end server and storage medium Download PDFInfo
- Publication number
- CN110225099B CN110225099B CN201910422734.1A CN201910422734A CN110225099B CN 110225099 B CN110225099 B CN 110225099B CN 201910422734 A CN201910422734 A CN 201910422734A CN 110225099 B CN110225099 B CN 110225099B
- Authority
- CN
- China
- Prior art keywords
- service
- gateway
- request
- service request
- target
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/148—Migration or transfer of sessions
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The embodiment of the invention discloses a data processing method, a front-end client, a back-end server and a storage medium, wherein the method comprises the following steps: the front-end client sends a network switching request to the first gateway; the first gateway verifies the network switching request and sends the network switching request to a back-end server according to a verification result; the back-end server switches the current network of the front-end client to a target network corresponding to the target IP address according to the target IP address carried by the received network switching request; the front-end client sends a service request to the second gateway; the second gateway verifies the service request and sends the service request to a back-end server according to a verification result; and the back-end server sends the service request to a service component corresponding to the service request for service logic processing, and returns the service logic processing result to the front-end client through a second gateway so as to improve the data processing efficiency.
Description
Technical Field
The present invention relates to the field of data processing technologies, and in particular, to a data processing method, a front end client, a back end server, and a storage medium.
Background
Currently, a traditional architecture includes a front-end client and a back-end server, where the front-end client and the back-end server are related to each other, and the back-end server includes multiple functions, and all the functions are in the same item. In a communication network, when a terminal performs an intranet-extranet switching in such a framework, a service request often involves a plurality of background calls, a plurality of interfaces need to be modified, the operation is complex, the efficiency is low, and the user experience is poor. How to more effectively improve the efficiency of data processing has become an important point of research.
Disclosure of Invention
The embodiment of the invention provides a data processing method, a front-end client, a back-end server and a storage medium, which can realize network switching and service logic processing through a hierarchical gateway and improve the efficiency of data processing.
In a first aspect, an embodiment of the present invention provides a data processing method, applied to a data processing system, where the data processing system includes a front end client, a first gateway, a second gateway, and a back end server, where the front end client is connected to the back end server through the first gateway and the second gateway, the first gateway is a network switching gateway, and the second gateway is a service request forwarding gateway, and the method includes:
The front-end client sends a network switching request to the first gateway, wherein the network switching request carries a target IP address of a network to be switched;
after receiving the network switching request, the first gateway verifies the network switching request and sends the network switching request to the back-end server according to a verification result;
the back-end server switches the current network of the front-end client to a target network corresponding to the target IP address according to the received target IP address, and sends a switching success message to the front-end client through the first gateway;
the front-end client sends a service request to the second gateway after receiving the switching success message sent by the back-end server;
after receiving the service request, the second gateway verifies the service request and sends the service request to the back-end server according to a verification result;
and the back-end server sends the service request to a service component corresponding to the service request for service logic processing, and returns the service logic processing result to the front-end client through the second gateway.
Further, the network switching request also carries a target identifier of the front-end client; after receiving the network switching request, the first gateway verifies the network switching request and sends the network switching request to the back-end server according to a verification result, and the method comprises the following steps:
after receiving the network switching request, the first gateway verifies the target identifier carried in the network switching request with the identifier of the terminal in a preset blacklist database;
and if the target identification is not matched with the identification of the terminal in the preset blacklist database as a result of verification, the first gateway determines that the network switching request is successfully verified, and sends the network switching request to the back-end server.
Further, after the first gateway determines that the verification of the network switching request is successful, before the network switching request is sent to the back-end server, the method further includes:
the first gateway detects a target IP address carried by the network switching request;
if the target IP address is detected to be legal, triggering the first gateway to execute the step of sending the network switching request to the back-end server;
If the target IP address is detected to be illegal, the first gateway refuses to send the network switching request to the back-end server and returns prompt information to the front-end client to prompt a user that the target IP address is illegal.
Further, before the back-end server switches the current network of the front-end client to the target network corresponding to the target IP address according to the received target IP address, the method further includes:
the back-end server reads the current IP address of the front-end client which sends the network switching request;
the back-end server compares the current IP address of the front-end client with the target IP address carried in the network switching request;
if the back-end server compares the current IP address of the front-end client with the target IP address, the back-end server sends prompt information to the front-end client, wherein the prompt information is used for prompting a user that the current IP address of the front-end client is the same as the target IP address;
and if the comparison result shows that the current IP address of the front-end client is different from the target IP address, the back-end server executes the step of switching the current network of the front-end client to the target network corresponding to the target IP address according to the acquired target IP address.
Further, the service request also carries a target service identifier; after receiving the service request, the second gateway verifies the service request and sends the service request to the back-end server according to the verification result, and the method comprises the following steps:
after receiving the service request, the second gateway determines the service type requested by the service request according to a target service identifier carried by the service request;
verifying the service request according to the service type requested by the service request;
and if the verification results in that the service type requested by the service request is matched with the preset type, the second gateway sends the service request to the back-end server.
Further, the back-end server sends the service request to a service component corresponding to the service request for service logic processing, including:
the back-end server determines a business service component corresponding to the target business identifier according to the corresponding relation between the preset business identifier and the business service component;
and the back-end server sends the service request to a service component corresponding to the target service identifier for service logic processing.
Further, the back-end server sends the service request to a service component corresponding to the service request for service logic processing, including:
the back-end server determines at least one business service component corresponding to the function of the business request according to the business request;
the back-end server determines a service component with the maximum service logic processing capacity according to the service logic processing capacity of the at least one service component;
and the back-end server sends the service request to the service component with the largest service logic processing capacity.
In a second aspect, embodiments of the present invention provide a front-end client comprising a data interface, a user interface, a processor, and a memory, the data interface, the user interface, the processor, and the memory being interconnected, wherein,
the user interface is used for outputting the service processing result acquired by the memory;
the memory is used for storing a computer program comprising program instructions, the processor is configured to call the program instructions to perform the steps of:
sending a network switching request to a first gateway so that the first gateway verifies the network switching request and sends the network switching request to the back-end server according to a verification result;
And sending a service request to a second gateway so that the second gateway verifies the service request, and sending the service request to the back-end server for service logic processing according to a verification result.
In a third aspect, embodiments of the present invention provide a server comprising a data interface, a user interface, a processor, and a memory, the data interface, the user interface, the processor, and the memory being interconnected, wherein,
the user interface is used for outputting the service processing result acquired by the memory;
the memory is used for storing a computer program comprising program instructions, the processor is configured to call the program instructions to perform the steps of:
sending a network switching request to a first gateway so that the first gateway verifies the network switching request and sends the network switching request to the back-end server according to a verification result;
and sending a service request to a second gateway so that the second gateway verifies the service request, and sending the service request to the back-end server for service logic processing according to a verification result.
In a fourth aspect, embodiments of the present invention provide a computer readable storage medium storing a computer program for execution by a processor to implement the method of the first aspect described above.
According to the embodiment of the invention, the front-end client sends the network switching request to the first gateway, and after the first gateway successfully verifies the network switching request, the network switching request is sent to the back-end server, so that the back-end server switches the current network of the front-end client to the target network requested by the network switching request. After the network switching is successful, a service request is sent to a second gateway through a front-end client, and after the service request is verified successfully by the second gateway, the service request is sent to a back-end server, so that the back-end server sends the service request to a service component corresponding to the service request for service logic processing. By the implementation mode, the mutual independence of network switching and service logic processing can be realized, and the efficiency of network switching and the efficiency of service data processing are improved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for the description of the embodiments will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a schematic diagram of a data processing system according to an embodiment of the present invention;
FIG. 2 is an interactive schematic flow chart of a data processing method according to an embodiment of the present invention;
FIG. 3 is a schematic block diagram of a front-end client provided by an embodiment of the present invention;
fig. 4 is a schematic block diagram of a backend server according to an embodiment of the present invention.
Detailed Description
The following description of the embodiments of the present invention will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all embodiments of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
The data processing method provided by the embodiment of the invention can be executed by a data processing system, wherein a front-end client of the data processing system, a first gateway, a second gateway and a back-end server are adopted, and in some embodiments, the front-end client is connected with the back-end server through the first gateway and the second gateway, and the first gateway is a network switching gateway and is used for switching an internal network and an external network; in some embodiments, the second gateway is a service request forwarding gateway, and is configured to forward a service request. In some embodiments, the front-end client may be disposed on a smart terminal such as a mobile phone, a computer, a tablet, a smart watch, etc.
Referring to fig. 1, fig. 1 is a schematic diagram of a data processing system according to an embodiment of the present invention. The system comprises: a front-end client 11, a first gateway 12, a second gateway 13 and a back-end server 14. In this system architecture, when the front-end client 11 receives a network switching request, the front-end client 11 may send a network switching request to the first gateway 12, where the network switching request carries a target IP address of a network to be switched. In some embodiments, the network switching request may be sent to the front-end client 11 by a user, or may be triggered by the front-end client 11 according to a preset trigger condition, which is not limited in the embodiments of the present invention. The first gateway may verify the network switching request after receiving the network switching request, and send the network switching request to the backend server 14 according to the result of the verification. The backend server 14 may switch the current network of the front-end client to a target network corresponding to the target IP address according to the received target IP address, and send a handover success message to the front-end client through the first gateway 12. The front-end client 11 may send a service request to the second gateway 13 after receiving the handover success message sent by the back-end server 14. The second gateway 13 may verify the service request after receiving the service request, and send the service request to the back-end server 14 according to the result of the verification. The backend server 14 may send the service request to a service component corresponding to the service request to perform service logic processing, and return a result of service logic processing to the front-end client 11 through the second gateway 13.
The data processing method according to the embodiment of the present invention is schematically described below with reference to the drawings.
Referring to fig. 2, fig. 2 is an interactive schematic flowchart of a data processing method according to an embodiment of the present invention, and as shown in fig. 2, the method may be performed by a data processing system, and a specific explanation of the data processing system is as described above, which is not described herein. Specifically, the method of the embodiment of the invention comprises the following steps.
S201: the front-end client sends a network switching request to the first gateway, wherein the network switching request carries a target IP address of a network to be switched.
In the embodiment of the invention, the front-end client can send a network switching request to the first gateway, wherein the network switching request carries the target IP address of the network to be switched.
S202: and after receiving the network switching request, the first gateway verifies the network switching request and sends the network switching request to the back-end server according to a verification result.
In the embodiment of the invention, after receiving the network switching request, the first gateway can verify the network switching request and send the network switching request to the back-end server according to the verification result. Therefore, according to the embodiment, the network switching request sent by the front-end client is verified through the first gateway, so that information leakage can be prevented, and the safety of data interaction in the network switching process is improved.
In an embodiment, the network switching request further carries a target identifier of the front end client, and after receiving the network switching request, the first gateway may verify the target identifier carried in the network switching request with an identifier of a terminal in a preset blacklist database. If the target identification is not matched with the identification of the terminal in the preset blacklist database as a result of verification, the first gateway can determine that the network switching request is successfully verified and send the network switching request to the back-end server.
For example, assuming that the target identifier carried in the network switching request is 1, after receiving the network switching request, the first gateway may verify the target identifier 1 carried in the network switching request with the identifier of the terminal in the preset blacklist database. If the target identifier 1 is not matched with the identifiers of all the terminals in the preset blacklist database as a result of verification, the first gateway can determine that the network switching request is successfully verified and send the network switching request to the back-end server.
In one embodiment, after the first gateway determines that the verification of the network switching request is successful, before sending the network switching request to the backend server, the first gateway may detect a target IP address carried by the network switching request, and if the target IP address is detected to be legal, trigger the first gateway to perform a step of sending the network switching request to the backend server; if the target IP address is detected to be illegal, the first gateway can refuse to send the network switching request to the back-end server and return prompt information to the front-end client to prompt the user that the target IP address is illegal, so that the user can send the network switching request carrying the target IP address to the front-end client again.
For example, assuming that the target IP address carried in the network switching request is 14.110.45.120, after determining that the network switching request is successfully verified, the first gateway may detect the target IP address 14.110.45.120 carried in the network switching request before sending the network switching request to the backend server, and if it is detected that the target IP address 14.110.45.120 is legal, the first gateway may be triggered to send the network switching request to the backend server.
For another example, assuming that the target IP address carried in the network handover request is 198.110.40.120, the first gateway may detect the target IP address 198.110.40.120 carried in the network handover request before sending the network handover request to the backend server after determining that the network handover request is successfully authenticated, and if it is detected that the target IP address 198.110.40.120 is not legal, the first gateway may reject sending the network handover request to the backend server and return a prompt message to the front-end client to prompt the user that the target IP address 198.110.40.120 is not legal, so that the user may send the network handover request carrying a new target IP address to the front-end client again.
S203: and the back-end server switches the current network of the front-end client to a target network corresponding to the target IP address according to the received target IP address, and sends a switching success message to the front-end client through the first gateway.
In the embodiment of the invention, the back-end server can switch the current network of the front-end client to the target network corresponding to the target IP address according to the received target IP address, and send a successful switching message to the front-end client through the first gateway.
In one embodiment, before the backend server switches the current network of the front-end client to the target network corresponding to the target IP address according to the received target IP address, the backend server may read the current IP address of the front-end client that sends the network switching request, for example, the backend server reads the current IP address of the front-end client that sends the network switching request as 10.110.45.120. After the back-end server reads the current IP address of the front-end client, the current IP address of the front-end client may be compared with the target IP address carried in the network switching request, and whether the current IP address is the same as the target IP address may be determined by comparing.
In some embodiments, if the comparison results in that the current IP address of the front-end client is the same as the target IP address, the back-end server may send a prompt message to the front-end client, where the prompt message is used to prompt the user that the current IP address of the front-end client is the same as the target IP address, so that the user determines the accuracy of the target IP address according to the prompt message, if the user determines that the target IP address is accurate, the current network is the switched network, and if the user determines that the target IP address is inaccurate, the user may send a network switching request carrying the accurate IP address to the front-end client again, so as to avoid that the user sends an incorrect IP address to cause the network switching request to fail.
For example, assuming that the target IP address received by the backend server is 14.110.45.120, if the backend server reads that the current IP address of the front-end client is 14.110.45.120, it may be determined that the current IP address of the front-end client is the same as the target IP address, and the backend server may send a prompt message to the front-end client, where the prompt message is used to prompt the user that the current IP address 14.110.45.120 of the front-end client is the same as the target IP address 14.110.45.120. By the implementation mode, the user can conveniently check the accuracy of the target IP address according to the prompt information, if the user determines that the target IP address is accurate, the current network can be determined to be the switched network, and if the user determines that the target IP address is inaccurate, the user can send the network switching request carrying the accurate IP address to the front-end client again, so that the network switching request failure caused by the fact that the user sends the wrong IP address is avoided.
In some embodiments, if the comparison results in that the current IP address of the front-end client is different from the target IP address, the back-end server may switch the current network of the front-end client to a target network corresponding to the target IP address according to the obtained target IP address.
For example, assuming that the target IP address carried in the network handover request is 14.110.45.120, if the current IP address of the front-end client is 10.110.45.120, the back-end server may compare the current IP address 10.110.45.120 of the front-end client with the target IP address 14.110.45.120 carried in the network handover request, and if the back-end server compares that the current IP address 10.110.45.120 of the front-end client is different from the target IP address 14.110.45.120, the current network corresponding to the IP address 10.110.45.120 of the front-end client may be switched to the target network corresponding to the target IP address 14.110.45.120 according to the obtained target IP address 14.110.45.120.
S204: and the front-end client sends a service request to the second gateway after receiving the switching success message sent by the back-end server.
In the embodiment of the invention, the front-end client can send the service request to the second gateway after receiving the switching success message sent by the back-end server. In some embodiments, after receiving the handover success message sent by the back-end server, if a service request sent based on a user operation is received, the front-end client may send the service request to the second gateway in the network environment after the handover is successful, so that the second gateway may forward the service request to the back-end server.
In one embodiment, after the front-end client receives the handover success message sent by the back-end server, if the front-end client can receive a service request, the front-end client can send the service request to the second gateway. In some embodiments, the service request may be sent by the user to the second gateway through the front end client, or may be sent by another terminal to the front end client, so that the front end client sends the service request to the second gateway.
In one embodiment, the front-end client may receive the service request sent based on the user operation in any network environment, and after receiving the service request, send the service request to the second gateway in the current network environment.
S205: and the second gateway verifies the service request after receiving the service request, and sends the service request to the back-end server according to the verification result.
In the embodiment of the invention, after receiving the service request, the second gateway can verify the service request and send the service request to the back-end server according to the verification result.
In some embodiments, the second gateway may be a service forwarding gateway with functions of authentication, monitoring, load balancing, buffering, request fragmentation and management, static response processing, and the like. In some embodiments, the service request may include a query request, an image processing request, and the like, and the embodiment of the present invention does not limit the service request.
In one embodiment, the service request may carry a target identifier of a front-end client, and the second gateway may perform identity verification on the front-end client according to the target identifier of the front-end client after receiving the service request. When the second gateway performs identity verification, whether a target identifier carried by the service request is matched with a pre-stored terminal identifier with access right or not can be detected, and if the target identifier is detected to be matched with the pre-stored terminal identifier with access right, the second gateway can be determined that the identity verification of the front-end client is successful; if the target identifier is not matched with the pre-stored terminal identifier with the access right, the second gateway can be determined to fail to verify the identity of the front-end client, the second gateway refuses to forward the service request to a back-end server, and prompt information is sent to the front-end client so as to prompt a user that the front-end client has no access right.
In one embodiment, the service request further carries a target service identifier; after receiving the service request, the second gateway can determine the service type requested by the service request according to the target service identifier carried by the service request, verify the service request according to the service type requested by the service request, and if the service type requested by the service request is verified to be matched with the preset type, the second gateway can send the service request to the back-end server. In some embodiments, the preset type refers to a service type supported by each service component in the backend server.
Therefore, the service request sent by the front-end client is verified through the second gateway, so that information leakage can be prevented, and the security of data interaction is improved.
In particular, it may be illustrated that, assuming that a service request sent by a front-end client to a second gateway is a query request, the second gateway may perform authentication such as identity authority on the query request after receiving the query request, and if the authentication is successful, the second gateway may send the query request to the back-end server.
In one embodiment, after receiving the service request, the second gateway may determine a service type requested by the service request according to a target service identifier carried by the service request, and verify the service request according to the service type requested by the service request, and if verification fails, the second gateway may send a message of verification failure to the front-end client, so that after the front-end client receives the message of verification failure, the service request may be cancelled, or the service request may be sent to the second gateway again.
In one embodiment, after receiving the service request, the second gateway may perform identity verification on the target identifier of the front end client carried in the service request, if the second gateway performs identity verification on the target identifier successfully, the second gateway may further determine, according to the target service identifier carried in the service request, a service type requested by the service request, and verify the service request according to the service type requested by the service request, and if verification is successful, the second gateway may send the service request to the back end server.
S206: and the back-end server sends the service request to a service component corresponding to the service request for service logic processing, and returns the service logic processing result to the front-end client through the second gateway.
In the embodiment of the invention, the back-end server can send the service request to the service component corresponding to the service request for service logic processing, and return the service logic processing result to the front-end client through the second gateway, so that a user can check the service logic processing result through the front-end client. In some embodiments, the backend server includes a plurality of business service components therein, each business service component having a different business logic processing capability.
In one embodiment, when the back-end server sends the service request to the service component corresponding to the service request to perform service logic processing, the service component corresponding to the target service identifier may be determined according to a preset correspondence between the service identifier and the service component, and the service request is sent to the service component corresponding to the target service identifier to perform service logic processing.
For example, assuming that the target service identifier is service 1, if the back-end server determines that the service component corresponding to the target service identifier service 1 is component 1 according to the preset correspondence between the service identifier and the service component, the back-end server may send the service request to the service component 1 corresponding to the target service identifier service 1 for service logic processing.
In one embodiment, when the back-end server sends the service request to the service component corresponding to the service request to perform service logic processing, at least one service component corresponding to the function of the service request may be determined according to the service request, and the service component with the largest service logic processing capability may be determined according to the service logic processing capability of the at least one service component, and the back-end server may send the service request to the service component with the largest service logic processing capability.
For example, assuming that the target service identifier is service 1, if the back-end server determines that the service component corresponding to the target service identifier service 1 includes component 1, component 2 and component 3 according to the preset correspondence between the service identifier and the service component, the back-end server may acquire service logic processing capabilities of the components 1, 2 and 3, and if the back-end server determines that the service logic processing capability of the component 3 is maximum, the back-end server may send the service request to the component 3 with the maximum service logic processing capability.
In one embodiment, when the back-end server sends the service request to the service component corresponding to the service request to perform service logic processing, at least one service component corresponding to the service request function may be determined according to the service request. The back-end server can acquire the load pressure of the at least one business service component, and determine the business service component with the minimum load pressure according to the load pressure of the at least one business service component, and the back-end server can send the business request to the business service component with the minimum load pressure for business logic processing so as to improve the processing efficiency of the business request.
For example, assuming that the target service identifier is service 2, if the back-end server determines that the service component corresponding to the target service identifier service 2 includes component 2, component 3 and component 4 according to the preset correspondence between the service identifier and the service component, the back-end server may obtain the load pressures of the component 2, component 3 and component 4, and if the back-end server determines that the load pressure of the component 4 is minimum, the service request may be sent to the component 3 with the minimum load pressure for service logic processing, so as to improve the processing efficiency of service 2.
According to the embodiment of the invention, the front-end client sends the network switching request to the first gateway, and after the first gateway successfully verifies the network switching request, the network switching request is sent to the back-end server, so that the back-end server switches the current network of the front-end client to the target network requested by the network switching request. After the network switching is successful, a service request is sent to a second gateway through a front-end client, and after the service request is verified successfully by the second gateway, the service request is sent to a back-end server, so that the back-end server sends the service request to a service component corresponding to the service request for service logic processing. By the implementation mode, the mutual independence of network switching and service logic processing can be realized, and the efficiency of network switching and the efficiency of service data processing are improved.
In particular, referring to fig. 3, fig. 3 is a schematic block diagram of a front-end client according to an embodiment of the present invention. The front-end client of the embodiment of the invention as shown in the figure comprises: a data interface 301, a user interface 302, a processor 303 and a memory 304, the data interface 301, the user interface 302, the processor 303 and the memory 304 being interconnected, wherein,
The user interface 302 is configured to output the service processing result obtained by the memory 304;
the memory 304 is used for storing a computer program comprising program instructions, the processor 303 being configured to invoke the program instructions to perform the steps of:
sending a network switching request to a first gateway so that the first gateway verifies the network switching request and sends the network switching request to the back-end server according to a verification result;
and sending a service request to a second gateway so that the second gateway verifies the service request, and sending the service request to the back-end server for service logic processing according to a verification result.
In the embodiment of the invention, the front-end client can send the network switching request to the first gateway, and after the first gateway successfully verifies the network switching request, the first gateway sends the network switching request to the back-end server so that the back-end server switches the current network of the front-end client to the target network requested by the network switching request. After the network switching is successful, a service request is sent to a second gateway through a front-end client, and after the service request is verified successfully by the second gateway, the service request is sent to a back-end server, so that the back-end server sends the service request to a service component corresponding to the service request for service logic processing. By the implementation mode, the mutual independence of network switching and service logic processing can be realized, and the efficiency of network switching and the efficiency of service data processing are improved.
Referring to fig. 4, fig. 4 is a schematic block diagram of a backend server according to an embodiment of the present invention. The server in the present embodiment as shown in the drawings may include: one or more processors 401; one or more input devices 402, one or more output devices 403, and a memory 404. The processor 401, the input device 402, the output device 403, and the memory 404 are connected by a bus 405. The memory 404 is used for storing a computer program comprising program instructions, and the processor 401 is used for executing the program instructions stored in the memory 404. Wherein the processor 401 is configured to invoke said program instruction execution:
receiving a network switching request sent by a front-end client through a first gateway, wherein the network switching request carries a target IP address of a network to be switched;
switching the current network of the front-end client to a target network corresponding to the target IP address;
receiving a service request sent by the front-end client through a second gateway;
and sending the service request to a service component corresponding to the service request for service logic processing, and returning the service logic processing result to the front-end client through the second gateway.
In the embodiment of the invention, the server can receive the network switching request sent by the front-end client through the first gateway, the network switching request carries the target IP address of the network to be switched, the current network of the front-end client is switched to the target network corresponding to the target IP address, the service request sent by the front-end client through the second gateway is received, the service request is sent to the service component corresponding to the service request for service logic processing, and the service logic processing result is returned to the front-end client through the second gateway. By the implementation mode, the mutual independence of network switching and service logic processing can be realized, and the efficiency of network switching and the efficiency of service data processing are improved.
It should be appreciated that in embodiments of the present invention, the processor 401 may be a central processing unit (CenSral Processing UniS, CPU), which may also be other general purpose processors, digital signal processors (DigiSal Signal Processor, DSPs), application Specific Integrated Circuits (ASICs), off-the-shelf programmable gate arrays (Field-Programmable GaSe Array, FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The input device 402 may include a touch pad, microphone, etc., and the output device 403 may include a display (LCD, etc.), speaker, etc.
The memory 404 may include read only memory and random access memory and provide instructions and data to the processor 401. A portion of memory 404 may also include non-volatile random access memory. For example, memory 404 may also store information of device type.
In a specific implementation, the processor 401, the input device 402, and the output device 403 described in the embodiments of the present invention may execute the implementation described in the method embodiment of the data processing method provided in the embodiments of the present invention, and may also execute the implementation of the front-end client and the back-end server described in the embodiments of the present invention, which are not described herein again.
The embodiment of the invention also provides a computer readable storage medium, and the computer readable storage medium stores a computer program, and when the computer program is executed by a processor, the data processing method described in the embodiment of the invention is realized, and is not described herein.
Those of ordinary skill in the art will appreciate that the elements and algorithm steps described in connection with the embodiments disclosed herein may be embodied in electronic hardware, in computer software, or in a combination of the two, and that the elements and steps of the examples have been generally described in terms of function in the foregoing description to clearly illustrate the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention is essentially or a part contributing to the prior art, or all or part of the technical solution may be embodied in the form of a software product stored in a readable storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned readable storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
While the invention has been described with reference to certain preferred embodiments, it will be understood by those skilled in the art that various changes and substitutions of equivalents may be made and equivalents will be apparent to those skilled in the art without departing from the scope of the invention.
Claims (9)
1. The data processing method is characterized by being applied to a data processing system, wherein the data processing system comprises a front-end client, a first gateway, a second gateway and a back-end server, the front-end client is connected with the back-end server through the first gateway and the second gateway, the first gateway is a network switching gateway, and the second gateway is a service request forwarding gateway, and the method comprises the following steps:
the front-end client sends a network switching request to the first gateway, wherein the network switching request carries a target IP address of a network to be switched;
after receiving the network switching request, the first gateway verifies the network switching request and sends the network switching request to the back-end server according to a verification result;
the back-end server switches the current network of the front-end client to a target network corresponding to the target IP address according to the received target IP address, and sends a switching success message to the front-end client through the first gateway;
the front-end client receives a service request sent based on user operation in any network environment, and after receiving the service request, sends the service request to the second gateway in the current network environment, wherein the current network environment comprises a network before switching or the target network;
After receiving the service request, the second gateway verifies the service request and sends the service request to the back-end server according to a verification result, wherein the second gateway is a service forwarding gateway with monitoring, load balancing, caching, request fragmentation and management and static response processing functions;
the service request also carries a target service identifier; after receiving the service request, the second gateway verifies the service request and sends the service request to the back-end server according to the verification result, and the method comprises the following steps:
after receiving the service request, the second gateway determines the service type requested by the service request according to a target service identifier carried by the service request;
verifying the service request according to the service type requested by the service request;
if the service type requested by the service request is verified to be matched with a preset type, the second gateway sends the service request to the back-end server, wherein the preset type refers to the service type supported by each service component in the back-end server;
After receiving the service request, the second gateway verifies the service request, including:
detecting whether a target identifier carried by the service request is matched with a prestored terminal identifier with access right, and if so, determining that the identity verification of the second gateway on the front-end client is successful; if the target identification is not matched with the prestored terminal identification with access right, determining that the identity verification of the front-end client by the second gateway fails, refusing to forward the service request to the back-end server by the second gateway, and sending prompt information to the front-end client to prompt a user that the front-end client has no access right;
and the back-end server sends the service request to a service component corresponding to the service request for service logic processing, and returns the service logic processing result to the front-end client through the second gateway.
2. The method of claim 1, wherein the network handover request further carries a target identifier of the front-end client; after receiving the network switching request, the first gateway verifies the network switching request and sends the network switching request to the back-end server according to a verification result, and the method comprises the following steps:
After receiving the network switching request, the first gateway verifies the target identifier carried in the network switching request with the identifier of the terminal in a preset blacklist database;
and if the target identification is not matched with the identification of the terminal in the preset blacklist database as a result of verification, the first gateway determines that the network switching request is successfully verified, and sends the network switching request to the back-end server.
3. The method of claim 2, wherein after the first gateway determines that the network switch request was successfully authenticated, before sending the network switch request to the backend server, further comprising:
the first gateway detects a target IP address carried by the network switching request;
if the target IP address is detected to be legal, triggering the first gateway to execute the step of sending the network switching request to the back-end server;
if the target IP address is detected to be illegal, the first gateway refuses to send the network switching request to the back-end server and returns prompt information to the front-end client to prompt a user that the target IP address is illegal.
4. The method of claim 1, wherein before the backend server switches the current network of the front-end client to a target network corresponding to the target IP address according to the received target IP address, further comprising:
the back-end server reads the current IP address of the front-end client which sends the network switching request;
the back-end server compares the current IP address of the front-end client with the target IP address carried in the network switching request;
if the back-end server compares the current IP address of the front-end client with the target IP address, the back-end server sends prompt information to the front-end client, wherein the prompt information is used for prompting a user that the current IP address of the front-end client is the same as the target IP address;
and if the comparison result shows that the current IP address of the front-end client is different from the target IP address, the back-end server executes the step of switching the current network of the front-end client to the target network corresponding to the target IP address according to the acquired target IP address.
5. The method of claim 1, wherein the back-end server sending the service request to a service component corresponding to the service request for service logic processing, comprising:
The back-end server determines a business service component corresponding to the target business identifier according to the corresponding relation between the preset business identifier and the business service component;
and the back-end server sends the service request to a service component corresponding to the target service identifier for service logic processing.
6. The method of claim 4, wherein the back-end server sending the service request to a service component corresponding to the service request for service logic processing, comprising:
the back-end server determines at least one business service component corresponding to the function of the business request according to the business request;
the back-end server determines a service component with the maximum service logic processing capacity according to the service logic processing capacity of the at least one service component;
and the back-end server sends the service request to the service component with the largest service logic processing capacity.
7. A front-end client comprising a data interface, a user interface, a processor and a memory, said data interface, user interface, processor and memory being interconnected, wherein,
The user interface is used for outputting the service processing result acquired by the memory;
the memory is used for storing a computer program comprising program instructions, the processor is configured to call the program instructions to perform the steps of:
a network switching request is sent to a first gateway, wherein the network switching request carries a target IP address of a network to be switched, so that the first gateway verifies the network switching request and sends the network switching request to a back-end server according to a verification result;
receiving a service request sent based on user operation in any network environment, and after receiving the service request, sending the service request to a second gateway in the current network environment, so that the second gateway verifies the service request after receiving the service request, and sends the service request to the back-end server for service logic processing according to a verification result, wherein the second gateway is a service forwarding gateway with monitoring, load balancing, buffering, request fragmentation and management and static response processing functions; the service request also carries a target service identifier; after receiving the service request, the second gateway verifies the service request, and sends the service request to the back-end server for service logic processing according to a verification result, including:
After receiving the service request, the second gateway determines the service type requested by the service request according to a target service identifier carried by the service request;
verifying the service request according to the service type requested by the service request;
if the service type requested by the service request is verified to be matched with a preset type, the second gateway sends the service request to the back-end server, wherein the preset type refers to the service type supported by each service component in the back-end server;
after receiving the service request, the second gateway verifies the service request, including:
detecting whether a target identifier carried by the service request is matched with a prestored terminal identifier with access right, and if so, determining that the identity verification of the second gateway on the front-end client is successful; if the target identification is not matched with the prestored terminal identification with the access right, determining that the identity verification of the front-end client by the second gateway fails, refusing to forward the service request to the back-end server by the second gateway, and sending prompt information to the front-end client to prompt a user that the front-end client has no access right.
8. A back-end server comprising a processor, an input device, an output device, and a memory, the processor, the input device, the output device, and the memory being interconnected, wherein the memory is configured to store a computer program comprising program instructions, the processor being configured to invoke the program instructions to perform the steps of:
receiving a network switching request sent by a front-end client through a first gateway, wherein the network switching request carries a target IP address of a network to be switched;
switching the current network of the front-end client to a target network corresponding to the target IP address, and sending a switching success message to the front-end client through the first gateway;
receiving a service request sent by the front-end client through a second gateway, wherein the second gateway is a service forwarding gateway with monitoring, load balancing, caching, request fragmentation and management and static response processing functions; the service request also carries a target service identifier; after receiving the service request, the second gateway verifies the service request and sends the service request to the back-end server according to a verification result;
After receiving the service request, the second gateway verifies the service request, and sends the service request to the back-end server for service logic processing according to a verification result, including:
determining the service type requested by the service request according to a target service identifier carried by the service request; verifying the service request according to the service type requested by the service request; if the service type requested by the service request is verified to be matched with a preset type, the second gateway sends the service request to the back-end server, wherein the preset type refers to the service type supported by each service component in the back-end server;
after receiving the service request, the second gateway verifies the service request, including:
detecting whether a target identifier carried by the service request is matched with a prestored terminal identifier with access right, and if so, determining that the identity verification of the second gateway on the front-end client is successful; if the target identification is not matched with the prestored terminal identification with access right, determining that the identity verification of the front-end client by the second gateway fails, refusing to forward the service request to the back-end server by the second gateway, and sending prompt information to the front-end client to prompt a user that the front-end client has no access right;
And sending the service request to a service component corresponding to the service request for service logic processing, and returning the service logic processing result to the front-end client through the second gateway.
9. A computer readable storage medium, characterized in that the computer readable storage medium stores a computer program, which is executed by a processor to implement the method of any of claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910422734.1A CN110225099B (en) | 2019-05-20 | 2019-05-20 | Data processing method, front-end client, back-end server and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910422734.1A CN110225099B (en) | 2019-05-20 | 2019-05-20 | Data processing method, front-end client, back-end server and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110225099A CN110225099A (en) | 2019-09-10 |
| CN110225099B true CN110225099B (en) | 2023-10-24 |
Family
ID=67821566
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910422734.1A Active CN110225099B (en) | 2019-05-20 | 2019-05-20 | Data processing method, front-end client, back-end server and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110225099B (en) |
Families Citing this family (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112532513A (en) * | 2019-09-19 | 2021-03-19 | 上海淘票儿信息科技有限公司 | Gateway and service data processing method |
| CN112540858B (en) * | 2019-09-23 | 2023-10-27 | 华为云计算技术有限公司 | Task processing method, server, client and system |
| CN111324843A (en) * | 2020-02-17 | 2020-06-23 | 政采云有限公司 | Front-end request processing method, device, equipment and readable storage medium |
| CN111552987A (en) * | 2020-04-16 | 2020-08-18 | 重庆富民银行股份有限公司 | Page access authority control method |
| CN111901357B (en) * | 2020-08-06 | 2023-08-11 | 腾讯科技（深圳）有限公司 | Remote network connection method, system, computer device and storage medium |
| CN112105069B (en) * | 2020-09-22 | 2023-04-28 | 云南电网有限责任公司电力科学研究院 | Internet edge computing wireless network switching method and system |
| CN112565337B (en) * | 2020-11-06 | 2022-09-30 | 北京奇艺世纪科技有限公司 | Request transmission method, server, client, system and electronic equipment |
| CN112449012B (en) * | 2020-11-17 | 2024-04-05 | 中国平安财产保险股份有限公司 | Data resource scheduling method, system, server and read storage medium |
| CN113434175B (en) * | 2021-06-29 | 2024-02-27 | 平安科技（深圳）有限公司 | Data processing method, device, storage medium and equipment |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2011044725A1 (en) * | 2009-10-14 | 2011-04-21 | 华为技术有限公司 | Network selection method, network device and network system |
| CN105813153A (en) * | 2014-12-31 | 2016-07-27 | 中国电信股份有限公司 | Internetwork switching method, Internetwork switching system and network element |
| CN107396423A (en) * | 2017-07-26 | 2017-11-24 | 腾讯科技（深圳）有限公司 | Method for network access and device, storage medium and electronic installation |
| CN107645508A (en) * | 2017-10-16 | 2018-01-30 | 深圳市买买提乐购金融服务有限公司 | A kind of data handling system, method, client and server |
-
2019
- 2019-05-20 CN CN201910422734.1A patent/CN110225099B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2011044725A1 (en) * | 2009-10-14 | 2011-04-21 | 华为技术有限公司 | Network selection method, network device and network system |
| CN105813153A (en) * | 2014-12-31 | 2016-07-27 | 中国电信股份有限公司 | Internetwork switching method, Internetwork switching system and network element |
| CN107396423A (en) * | 2017-07-26 | 2017-11-24 | 腾讯科技（深圳）有限公司 | Method for network access and device, storage medium and electronic installation |
| CN107645508A (en) * | 2017-10-16 | 2018-01-30 | 深圳市买买提乐购金融服务有限公司 | A kind of data handling system, method, client and server |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110225099A (en) | 2019-09-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110225099B (en) | Data processing method, front-end client, back-end server and storage medium | |
| CN109492378B (en) | Identity verification method based on equipment identification code, server and medium | |
| US11005989B1 (en) | Validating automatic number identification data | |
| CN109561085B (en) | Identity verification method based on equipment identification code, server and medium | |
| US10476833B2 (en) | Warning method and apparatus, and processing server | |
| CN106550031B (en) | The method and device of data backup | |
| CN109688186B (en) | Data interaction method, device, equipment and readable storage medium | |
| US9569607B2 (en) | Security verification method and apparatus | |
| US20140258128A1 (en) | Method for managing fund security and mobile terminal | |
| US20130160094A1 (en) | OTA Bootstrap Method and System | |
| CN109117616B (en) | Verification method and device, electronic equipment and computer readable storage medium | |
| CN105050061A (en) | Method and device for sending messages on the basis of user voiceprint information | |
| CN110730446A (en) | Login method, terminal and computer storage medium | |
| EP3993471B1 (en) | Sim swap scam protection via passive monitoring | |
| WO2015193629A1 (en) | Detecting porting or redirection of a mobile telephone number | |
| CN108494765B (en) | Account processing method and device and computer readable storage medium | |
| CN107743114B (en) | Network access method, device and system | |
| CN112346874B (en) | Abnormal volume processing method and device based on cloud platform | |
| CN112149097B (en) | Identity authentication method, device, equipment and storage medium | |
| CN114630323A (en) | Voice call service processing method and device and computer readable storage medium | |
| CN104660480A (en) | An account number abnormality processing method, device and system | |
| CN106302558B (en) | Service processing method and device | |
| CN110417615B (en) | Check switch control method, device and equipment and computer readable storage medium | |
| US20160371676A1 (en) | Checking the validity of a transaction via the location of a terminal | |
| CN113225756B (en) | Network residing method, device, terminal and computer readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |