An information interaction method and device

Abstract

The present disclosure provides an information interaction method and device, relates to the technical field of computers, and particularly relates to the technical field of data processing. The specific implementation scheme is: in response to a service request sent by a client, performing anomaly detection on the service request; if the service request is an abnormal request, sending first page information of a preset page to the client; receiving a rendering result fed back by the client after the client successfully renders the preset page based on the first page information; and sending a service request mark to the client, so that the client requests a service based on the service request mark. By applying the information interaction scheme provided in the present disclosure, malicious requests can be avoided by the server, thereby improving the utilization rate of server computing resources.

Description

Technical Field

[0001] This disclosure relates to the field of computer technology, particularly to the field of data processing technology, and especially to an information interaction method and apparatus. Background Technology

[0002] During the information exchange between the server and the client, the server can receive and respond to service requests from the client, providing services to the client. However, during this process, the server may receive a large number of malicious requests in a short period. If the server's computing resources are insufficient to handle these malicious requests, it may experience server crashes.

[0003] In existing technologies, when a server is unable to handle the received requests based on its own computing resources, the server's computing nodes can be temporarily expanded to increase the server's computing resources required to process the requests. Summary of the Invention

[0004] This disclosure provides an information interaction method and apparatus.

[0005] According to one aspect of this disclosure, an information exchange method is provided, applied to a server, comprising:

[0006] In response to a service request sent by the client, perform anomaly detection on the service request;

[0007] If the service request is an abnormal request, send the first page information of the preset page to the client;

[0008] Receive the rendering result returned by the client after successfully rendering the preset page based on the first page information;

[0009] A service request tag is sent to the client so that the client requests a service based on the service request tag.

[0010] According to another aspect of this disclosure, an information exchange method is provided, applied to a client, comprising:

[0011] Send a service request to the server;

[0012] Obtain the first page information of the preset page sent by the server after detecting that the service request is an abnormal request;

[0013] Render the preset page based on the information from the first page;

[0014] The server is then informed of the rendering result after successfully rendering the preset page.

[0015] Obtain the service request tag sent by the server after receiving the rendering result.

[0016] According to another aspect of this disclosure, an information interaction device is provided, applied to a server, comprising:

[0017] The anomaly detection module is used to perform anomaly detection on the service request sent by the client.

[0018] The first information sending module is used to send the first page information of a preset page to the client if the service request is an abnormal request.

[0019] The result receiving module is used to receive the rendering result fed back by the client after the client successfully renders the preset page based on the first page information;

[0020] The tag sending module is used to send a service request tag to the client so that the client requests a service based on the service request tag.

[0021] According to another aspect of this disclosure, an information interaction device is provided for use on a client, comprising:

[0022] The request sending module is used to send service requests to the server;

[0023] The first information acquisition module is used to acquire the first page information of the preset page sent by the server after detecting that the service request is an abnormal request;

[0024] The page rendering module is used to render the preset page based on the first page information;

[0025] The result feedback module is used to send the rendering result to the server after successfully rendering the preset page.

[0026] The tag acquisition module is used to obtain the service request tag sent by the server after receiving the rendering result.

[0027] According to another aspect of this disclosure, an electronic device is provided, comprising:

[0028] At least one processor; and

[0029] A memory communicatively connected to the at least one processor; wherein,

[0030] The memory stores instructions that can be executed by the at least one processor, which, when executed by the at least one processor, enables the at least one processor to perform any of the aforementioned information interaction methods.

[0031] According to another aspect of this disclosure, a non-transitory computer-readable storage medium is provided storing computer instructions, wherein the computer instructions are used to cause the computer to perform any of the above-described information interaction methods.

[0032] According to another aspect of this disclosure, a computer program product is provided, including a computer program that, when executed by a processor, implements any of the above-described information interaction methods.

[0033] As can be seen from the above, when using the solution provided in this embodiment for information interaction, the server sends the first page information of a preset page to the client when it detects that the service request is an abnormal request. When the client receives the first page information, if the client is a normal client, it can render based on the first page information. If the client is an abnormal client, it usually will not perform any further processing on the first page information. When the server receives the rendering result from the client, it indicates that the client is a normal client, and at this time, it can send a service request flag to the client. When the server does not receive any feedback from the client, it indicates that the client is an abnormal client, and at this time, it will not send a service request flag to the server. In this way, a normal client can request services from the server based on the service request flag, while an abnormal client cannot request services. It is evident that the information interaction solution provided in this embodiment can prevent abnormal clients from requesting services from the server, thereby improving the resource utilization rate of server computing resources.

[0034] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0035] The accompanying drawings are provided to better understand this solution and do not constitute a limitation of this disclosure. Wherein:

[0036] Figure 1a A flowchart illustrating the first information interaction method provided in this embodiment of the disclosure;

[0037] Figure 1b This is a schematic diagram of a first type of verification page provided in an embodiment of this disclosure;

[0038] Figure 1c This is a schematic diagram of a second verification page provided in an embodiment of this disclosure;

[0039] Figure 1d This is a schematic diagram of a client display page provided in an embodiment of the present disclosure;

[0040] Figure 2A flowchart illustrating the second information interaction method provided in this embodiment of the disclosure;

[0041] Figure 3 This is a schematic diagram of the structure of a first type of information interaction device provided in an embodiment of the present disclosure;

[0042] Figure 4 This is a schematic diagram of the structure of a second information interaction device provided in an embodiment of the present disclosure;

[0043] Figure 5 This is a block diagram of an electronic device used to implement the information method of the embodiments of this disclosure. Detailed Implementation

[0044] The exemplary embodiments of this disclosure are described below with reference to the accompanying drawings, including various details of the embodiments to aid understanding, and should be considered merely exemplary. Therefore, those skilled in the art will recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of this disclosure. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description.

[0045] In existing server-client communication processes, when a server receives a large number of malicious requests within a short period, it needs to dedicate significant computing resources to processing these requests, thus reducing the utilization rate of server computing resources. Furthermore, when the number of malicious requests is large, it is necessary to temporarily expand the server's computing nodes to increase the computing resources required to process the requests, thereby increasing the server's operating costs.

[0046] To address the aforementioned technical problems, this disclosure provides an information interaction method and apparatus, which will be described in detail below through specific embodiments.

[0047] See Figure 1a , Figure 1a This is a flowchart illustrating a first information interaction method provided in an embodiment of the present disclosure. In this embodiment, the information interaction method is applied to a server, and the method includes the following steps S101-S104.

[0048] Step S101: In response to the service request sent by the client, perform anomaly detection on the service request.

[0049] The aforementioned service request is used to request the server to provide services. For example, the aforementioned service request can be a search request, a video playback request, etc.

[0050] Specifically, when a normal client and server establish a communication connection, they can agree on the information that the service request sent by the client should include. However, when an abnormal client establishes a communication connection with the server, it usually does so by deciphering the communication interface provided by the server. In this case, the abnormal client and server usually do not agree on the information that should be included in the service request. After the server receives the service request sent by the client, it can check whether the service request carries the pre-agreed information to detect abnormalities. If the service request carries the pre-agreed information, it can be determined that the service request is normal, and further processing of the service request can be carried out. If the service request does not carry the pre-agreed information or carries incorrect information, it can be determined that the service request is abnormal.

[0051] In addition, existing anomaly detection technologies can be used to detect anomalies in service requests, which will not be elaborated here.

[0052] Step S102: If the service request is an abnormal request, send the first page information of the preset page to the client.

[0053] The aforementioned preset page can be a verification page that requests user verification, such as... Figure 1b , Figure 1c As shown, Figure 1b The page shown is a verification page that requests the user to enter the verification code displayed on the page. Figure 1c The page shown is a verification page that requests the user to answer the displayed question. The above-mentioned preset page can also be a blank page, or it can be any other preset page.

[0054] The aforementioned first page information may include the URL of the preset page, page information required by the client to render the preset page, and so on.

[0055] Specifically, the server can pre-store the first page information of a preset page. When the above service request is detected as an abnormal request, the stored first page information is sent to the client.

[0056] In addition, the server can store first page information for multiple preset pages, so that when sending first page information to the client, different preset first page information can be sent according to different clients.

[0057] For example, when performing anomaly detection on service requests, the probability of a client being a normal client can be determined. If the probability of a client being a normal client is relatively high, the first page information of a blank page can be sent to that client. If the probability of a client being a normal client is relatively low, the first page information of a verification page can be sent to that client.

[0058] Step S103: Receive the rendering result returned by the client after successfully rendering the preset page based on the first page information.

[0059] In one embodiment of this disclosure, when the preset page is a blank page, the rendering result may include a notification message indicating that the preset page has been successfully rendered; when the preset page is a verification page, the rendering result may include verification information entered by the user on the preset page.

[0060] Specifically, after the server sends the aforementioned first page information to the client, if the client is a normal client, the user can initiate a command to open the preset page. The client can then respond to the user's command, render the preset page based on the received first page information, and display the rendered page. The server can then obtain the rendering result from the client. However, if the client is an abnormal client, which typically only has the function of sending a large number of abnormal requests to the server, it will not process the first page information upon receiving it. Therefore, it will not render the preset page based on the first page information, and the server will not receive any feedback from the client. Thus, if the server receives the rendering result from the client, it can determine that the client is a normal client.

[0061] Step S104: Send a service request tag to the client so that the client requests the service based on the service request tag.

[0062] The aforementioned service request marker can be a preset marker common to different clients, or it can be a unique marker specific to each client. For example, the unique marker can be the client's device information, the user information of the user using the client, etc.

[0063] Specifically, receiving the rendering result from the client can be understood as the trigger condition for sending a service request flag. As mentioned in step S103 above, if the server receives the rendering result from the client, it can determine that the client is a normal client. At this point, a service request flag can be sent to the client, allowing the client to request service based on the service request flag.

[0064] In addition, when a normal client establishes a communication connection with the server, the server can obtain the client's unique information, such as device information and user information of the user using the client. Thus, if the server determines that the client sending the service request is a normal client, it can identify the unique information corresponding to that client from the stored unique information of each normal client, and send that unique information as a service request identifier to the client.

[0065] After receiving the aforementioned service request flag, if the user indicates that the service should be requested again, the client can generate a new service request carrying the aforementioned service request flag and send the generated new service request to the server to request the server to provide the service.

[0066] In this context, in one embodiment of this disclosure, when the server performs anomaly detection on the received request, it can detect whether the service request carries a service request tag; if not, it executes the step of sending the first page information of the preset page to the client.

[0067] Since clients typically send service requests to servers based on service request tags, when performing anomaly detection on received service requests, the server directly checks whether the service request carries a service request tag. This allows for accurate detection of whether a service request is abnormal, thereby improving the accuracy of information exchange.

[0068] As can be seen from the above, when using the solution provided in this embodiment for information interaction, the server sends the first page information of a preset page to the client when it detects that the service request is an abnormal request. When the client receives the first page information, if the client is a normal client, it can render based on the first page information. If the client is an abnormal client, it usually will not perform any further processing on the first page information. When the server receives the rendering result from the client, it indicates that the client is a normal client, and at this time, it can send a service request flag to the client. When the server does not receive any feedback from the client, it indicates that the client is an abnormal client, and at this time, it will not send a service request flag to the server. In this way, a normal client can request services from the server based on the service request flag, while an abnormal client cannot request services. It is evident that the information interaction solution provided in this embodiment can prevent abnormal clients from requesting services from the server, thereby improving the resource utilization rate of server computing resources.

[0069] When the preset page is a verification page, after the client renders the preset page based on the information of the first page, the user can enter verification information on the preset page. In this way, the rendering result returned by the client can include the verification information entered by the user on the preset page.

[0070] In one embodiment of this disclosure, under the above circumstances, when sending a service request flag to the client, it is possible to verify whether the verification information included in the rendering result is valid information. If the verification information is valid information, then a service request flag is sent to the client.

[0071] Specifically, when verifying whether the verification information included in the rendering result is valid, since the aforementioned preset page is pre-generated by the server, the server can record the correct verification result corresponding to the verification page. Thus, when the server obtains the verification information in the rendering result, it can compare the verification information with the correct verification result. If the verification information is the same as the correct verification result, it means that the verification information included in the rendering result is valid. At this time, a service request flag is sent to the client. Otherwise, it means that the verification information is not valid. At this time, the server can notify the client of verification failure or resend the page information of another preset page to the client so that the user can re-verify.

[0072] As can be seen from the above, when using the solution provided in this embodiment for information interaction, the rendering result returned by the client can include the verification information entered by the user on the preset page. In this way, when the server sends a service request flag to the client, it can verify whether the verification information included in the rendering result is valid. Only when the verification information is determined to be valid will the server send a service request flag to the client. This can verify whether the user is a normal user, thereby improving the security and reliability of information interaction.

[0073] After the client receives the service request flag sent by the server, the user can decide whether to request the service again based on their own needs.

[0074] To facilitate users requesting services again, in one embodiment of this disclosure, after sending a service request flag to the client, second page information of the trigger page can be sent to the client.

[0075] The trigger page is the page used to trigger service requests.

[0076] Specifically, the server can determine the triggering page in the client that triggers the service request, obtain the second page information of the triggering page, and then send the second page information to the client.

[0077] In one embodiment of this disclosure, the trigger page can be determined by either of the following two implementation methods.

[0078] In the first implementation, different service requests sent by the client typically correspond to pages displayed on the client. For example, a search service request corresponds to a search page, a video playback request corresponds to a video recommendation page, and so on. Therefore, when the server responds to the above service requests, it can determine the trigger page corresponding to the service request based on this correspondence.

[0079] In the second implementation, the client can record user behavior, generate a user behavior log, and send the user behavior log to the server. The behavior log can record the page information displayed by the client when the user generates a user behavior. In this way, when the user initiates a service request, the page currently displayed by the client is the trigger page. The client can record the page information of the trigger page and include it in the user behavior log before sending it to the server. The server can then determine the trigger page based on the user behavior log.

[0080] As can be seen from the above, when using the solution provided in this embodiment for information interaction, after sending a service request flag to the client, the server sends second page information of the trigger page to the client. This allows the client to render the trigger page based on the second page information and redisplay it on the client. If the user wishes to request the service again, they can immediately initiate the request again on the trigger page displayed on the client. Therefore, the information interaction solution provided in this embodiment improves user convenience.

[0081] In one embodiment of this disclosure, after receiving the rendering result from the client, the server can also send a third page of information to the client, which asks the user whether to return to the trigger page. In this way, after obtaining the reply information entered by the user on the query page, the server can determine whether to send the second page of information to the client based on the reply information. If the reply information entered by the user on the query page is a request to return to the trigger page, the server sends the second page of information to the client.

[0082] For example, such as Figure 1d The client-side display page shown is illustrated. Users can choose between "Yes" and "No" from the prompt page according to their needs. If the user selects "Yes", the client sends a request to the server for the response information of the trigger page. After receiving the response information, the server sends the second page information of the trigger page to the client.

[0083] In addition, the server can also send the page display duration of the aforementioned query page and the aforementioned second page information to the client, so that if the client does not obtain user input information when the aforementioned query page is displayed for longer than the aforementioned page display duration, it can directly render the aforementioned trigger page based on the aforementioned second page information.

[0084] Corresponding to the above-described information interaction method applied to the server, this disclosure also provides an information interaction method applied to the client.

[0085] In one embodiment of this disclosure, see [link to embodiment]. Figure 2 The present invention provides a flowchart of a second information interaction method. In this embodiment, the above information interaction method is applied to the client and includes the following steps S201-S205.

[0086] Step S201: Send a service request to the server.

[0087] The aforementioned service request is used to request the server to provide services. For example, the aforementioned service request can be a search request, a video playback request, etc.

[0088] Specifically, when a normal client and server establish a communication connection, they can agree on the information that the client needs to include in the service request sent when requesting a service. After receiving the user's instruction to request the server to provide services, the client can respond to the instruction, send a service request to the server, and generate a service request carrying the pre-agreed information when requesting services from the server.

[0089] Step S202: Obtain the first page information of the preset page sent by the server after detecting that the service request is an abnormal request.

[0090] The aforementioned preset page can be a verification page that requests user verification, a blank page, or other preset pages.

[0091] The aforementioned first page information may include the URL of the preset page, page information required by the client to render the preset page, and so on.

[0092] Specifically, on the client side, due to user error or the expiration of the validity period of the agreed information, the service request generated by the client may lack the pre-agreed information. In this case, when the server performs anomaly detection on the service request, it will determine the service request as an abnormal request and send the first page information of the preset page to the client.

[0093] Step S203: Render the preset page based on the information of the first page.

[0094] Specifically, after obtaining the first page information of the aforementioned preset page, the preset page can be rendered based on the first page information using existing page rendering technology, which will not be elaborated here.

[0095] Step S204: Send the rendering result to the server after successfully rendering the preset page.

[0096] Specifically, after the preset page is rendered, a notification message indicating that the preset page has been rendered successfully can be generated as the rendering result, and then the rendering result can be sent back to the server.

[0097] In one embodiment of this disclosure, when the preset page is a verification page, after the client finishes rendering the preset page, it can obtain the verification information entered by the user in the rendered preset page. In this way, when generating the rendering result, a rendering result containing the verification information can be generated.

[0098] Step S205: Obtain the service request tag sent by the server after receiving the rendering result.

[0099] The aforementioned service request marker can be a preset marker common to different clients, or it can be a unique marker specific to each client. For example, the unique marker can be the client's device information, the user information of the user using the client, etc.

[0100] Specifically, since abnormal clients usually have difficulty processing the information on the first page and even more difficulty in sending any results back to the server, the server can determine that the client that sent the service request is a normal client after receiving the rendering result, and thus send a service request tag to the client. In this way, the client can obtain the service request tag sent by the server after receiving the rendering result.

[0101] In addition, after receiving the aforementioned service request marker, if the client receives another instruction from the user to request the server to provide services, it can respond to that instruction by generating a service request carrying the service request marker.

[0102] As can be seen from the above, when using the solution provided in the embodiments of this disclosure for information interaction, if the server detects that the sent service request is an abnormal request, it can obtain the first page information of the preset page sent by the server. After rendering the preset page based on the first page information, it can send the rendering result back to the server, thereby obtaining the service request marker sent by the server after receiving the rendering result. Since abnormal clients usually have difficulty processing the first page information, they also have difficulty sending any result back to the server. Therefore, the server can determine whether the client that sent the service request is a normal client based on whether the rendering result is obtained. It can be seen that by applying the information interaction solution provided in the embodiments of this disclosure, the server can accurately distinguish between normal clients and abnormal clients, thereby providing accuracy in information interaction.

[0103] In one embodiment of this disclosure, when the preset page is a verification page, the rendering result may include the verification information entered by the user on the verification page. After obtaining the rendering result, the server can determine whether the verification information contained in the rendering result is valid based on the correct verification result corresponding to the verification page stored in its own database. If the server determines that the verification information is valid, it can obtain the service request tag sent by the server.

[0104] In this solution, after the server receives the rendering result from the client, it verifies whether the verification information in the rendering result is valid. The server can accurately determine whether the client is a normal client. Therefore, the information interaction solution provided by this embodiment can improve the security and reliability of information interaction.

[0105] In one embodiment of this disclosure, after obtaining the service request tag sent by the server, the second page information of the trigger page sent by the server can also be obtained, and the trigger page can be rendered based on the second page information.

[0106] The trigger page is the page used to trigger service requests.

[0107] Specifically, after obtaining the second page information of the aforementioned trigger page, the server can send this second page information to the client. Upon receiving this second page information, the client can use existing page rendering technology to render the trigger page based on the second page information.

[0108] The specific implementation method for the server to obtain the second page information of the trigger page can be found in the above embodiments, and will not be repeated here.

[0109] As can be seen from the above, when using the solution provided in this embodiment for information interaction, the trigger page is the page that triggers the service request. By obtaining the second page information of the trigger page and rendering the trigger page based on the second page information, the client can render the preset page and then render the trigger page again, which facilitates the user to request the server to provide services again. Therefore, the information interaction solution provided in this embodiment can improve the user's convenience in using the client.

[0110] Corresponding to the above-described information interaction method, this disclosure also provides an information interaction device.

[0111] In one embodiment of this disclosure, see [link to embodiment]. Figure 3 It provides the first information interaction device, applied to a server, including:

[0112] Anomaly detection module 301 is used to perform anomaly detection on the service request sent by the client in response to the service request;

[0113] The first information sending module 302 is used to send the first page information of a preset page to the client if the service request is an abnormal request.

[0114] The result receiving module 303 is used to receive the rendering result fed back by the client after successfully rendering the preset page based on the first page information;

[0115] The tag sending module 304 is used to send a service request tag to the client so that the client requests a service based on the service request tag.

[0116] As can be seen from the above, when using the solution provided in this embodiment for information interaction, the server sends the first page information of a preset page to the client when it detects that the service request is an abnormal request. When the client receives the first page information, if the client is a normal client, it can render based on the first page information. If the client is an abnormal client, it usually will not perform any further processing on the first page information. When the server receives the rendering result from the client, it indicates that the client is a normal client, and at this time, it can send a service request flag to the client. When the server does not receive any feedback from the client, it indicates that the client is an abnormal client, and at this time, it will not send a service request flag to the server. In this way, a normal client can request services from the server based on the service request flag, while an abnormal client cannot request services. It is evident that the information interaction solution provided in this embodiment can prevent abnormal clients from requesting services from the server, thereby improving the resource utilization rate of server computing resources.

[0117] In one embodiment of this disclosure, the tag sending module is specifically used for:

[0118] If the rendering result includes verification information entered by the user on the preset page, verify whether the verification information is valid.

[0119] If the verification information is valid, a service request flag is sent to the client.

[0120] As can be seen from the above, when using the solution provided in this embodiment for information interaction, the rendering result returned by the client can include the verification information entered by the user on the preset page. In this way, when the server sends a service request flag to the client, it can verify whether the verification information included in the rendering result is valid. Only when the verification information is determined to be valid will the server send a service request flag to the client. This can verify whether the user is a normal user, thereby improving the security and reliability of information interaction.

[0121] In one embodiment of this disclosure, the apparatus further includes:

[0122] The second information sending module is used to send second page information of the trigger page to the client after sending the service request flag to the client, wherein the trigger page is a page used to trigger the service request.

[0123] As can be seen from the above, when using the solution provided in this embodiment for information interaction, after sending a service request flag to the client, the server sends second page information of the trigger page to the client. This allows the client to render the trigger page based on the second page information and redisplay it on the client. If the user wishes to request the service again, they can immediately initiate the request again on the trigger page displayed on the client. Therefore, the information interaction solution provided in this embodiment improves user convenience.

[0124] In one embodiment of this disclosure, the anomaly detection module 301 is specifically used for:

[0125] Detect whether the service request carries a service request tag;

[0126] If not carried, then the step of sending the first page information of the preset page to the client is performed.

[0127] In this solution, since the client usually sends a service request to the server based on the service request tag, when the server performs anomaly detection on the received service request, it directly checks whether the service request carries a service request tag. This can accurately detect whether the service request is an abnormal request, thereby improving the accuracy of information exchange.

[0128] Corresponding to the information interaction device applied to the server described above, this disclosure also provides an information interaction device applied to the client.

[0129] In one embodiment of this disclosure, see [link to embodiment]. Figure 4 It provides a second information interaction device for client applications, including:

[0130] Request sending module 401 is used to send service requests to the server;

[0131] The first information acquisition module 402 is used to acquire the first page information of the preset page sent by the server after detecting that the service request is an abnormal request;

[0132] Page rendering module 403 is used to render the preset page based on the first page information;

[0133] The result feedback module 404 is used to send the rendering result after successfully rendering the preset page to the server.

[0134] The tag acquisition module 405 is used to acquire the service request tag sent by the server after receiving the rendering result.

[0135] As can be seen from the above, when using the solution provided in the embodiments of this disclosure for information interaction, if the server detects that the sent service request is an abnormal request, it can obtain the first page information of the preset page sent by the server. After rendering the preset page based on the first page information, it can send the rendering result back to the server, thereby obtaining the service request marker sent by the server after receiving the rendering result. Since abnormal clients usually have difficulty processing the first page information, they also have difficulty sending any result back to the server. Therefore, the server can determine whether the client that sent the service request is a normal client based on whether the rendering result is obtained. It can be seen that by applying the information interaction solution provided in the embodiments of this disclosure, the server can accurately distinguish between normal clients and abnormal clients, thereby providing accuracy in information interaction.

[0136] In one embodiment of this disclosure, the result feedback module is specifically used for:

[0137] Obtain the verification information entered by the user in the rendered preset page;

[0138] The server is then fed back a rendering result including the verification information.

[0139] The step of obtaining the service request tag sent by the server after receiving the rendering result includes:

[0140] Obtain the service request tag sent by the server after determining that the verification information is valid.

[0141] In this solution, after the server receives the rendering result from the client, it verifies whether the verification information in the rendering result is valid. The server can accurately determine whether the client is a normal client. Therefore, the information interaction solution provided by this embodiment can improve the security and reliability of information interaction.

[0142] In one embodiment of this disclosure, it further includes:

[0143] The second obtaining module is used to obtain second page information of the trigger page sent by the server after obtaining the service request tag sent by the server, wherein the trigger page is: a page used to trigger the service request;

[0144] The trigger page is rendered based on the information from the second page.

[0145] As can be seen from the above, when using the solution provided in this embodiment for information interaction, the trigger page is the page that triggers the service request. By obtaining the second page information of the trigger page and rendering the trigger page based on the second page information, the client can render the preset page and then render the trigger page again, which facilitates the user to request the server to provide services again. Therefore, the information interaction solution provided in this embodiment can improve the user's convenience in using the client.

[0146] The collection, storage, use, processing, transmission, provision, and disclosure of user personal information involved in the technical solution disclosed herein comply with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0147] According to embodiments of this disclosure, this disclosure also provides an electronic device, a readable storage medium, and a computer program product.

[0148] In one embodiment of this disclosure, an electronic device is provided, comprising:

[0149] At least one processor; and

[0150] A memory communicatively connected to the at least one processor; wherein,

[0151] The memory stores instructions that can be executed by the at least one processor, which, when executed by the at least one processor, enables the at least one processor to perform the aforementioned information interaction method.

[0152] In one embodiment of this disclosure, a non-transitory computer-readable storage medium storing computer instructions is provided, wherein the computer instructions are used to cause the computer to perform the above-described information interaction method.

[0153] In one embodiment of this disclosure, a computer program product is provided, including a computer program that, when executed by a processor, implements the above-described information interaction method.

[0154] Figure 5 A schematic block diagram of an example electronic device 500 that can be used to implement embodiments of the present disclosure is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the present disclosure described and / or claimed herein.

[0155] like Figure 5 As shown, device 500 includes a computing unit 501, which can perform various appropriate actions and processes based on a computer program stored in read-only memory (ROM) 502 or a computer program loaded from storage unit 508 into random access memory (RAM) 503. RAM 503 may also store various programs and data required for the operation of device 500. The computing unit 501, ROM 502, and RAM 503 are interconnected via bus 504. Input / output (I / O) interface 505 is also connected to bus 504.

[0156] Multiple components in device 500 are connected to I / O interface 505, including: input unit 506, such as keyboard, mouse, etc.; output unit 507, such as various types of monitors, speakers, etc.; storage unit 508, such as disk, optical disk, etc.; and communication unit 509, such as network card, modem, wireless transceiver, etc. Communication unit 509 allows device 500 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0157] The computing unit 501 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of the computing unit 501 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 501 performs the various methods and processes described above, such as information interaction methods. For example, in some embodiments, the information interaction method may be implemented as a computer software program tangibly contained in a machine-readable medium, such as storage unit 508. In some embodiments, part or all of the computer program may be loaded and / or installed on device 500 via ROM 502 and / or communication unit 509. When the computer program is loaded into RAM 503 and executed by the computing unit 501, one or more steps of the information interaction method described above may be performed. Alternatively, in other embodiments, the computing unit 501 may be configured to perform information interaction methods by any other suitable means (e.g., by means of firmware).

[0158] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), complex programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0159] The program code used to implement the methods of this disclosure may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on a machine, partially on a machine, as a standalone software package partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0160] In the context of this disclosure, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0161] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device for displaying information to the user (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor); and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the computer. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0162] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as a data server), or computing systems that include middleware components (e.g., an application server), or computing systems that include frontend components (e.g., a user computer with a graphical user interface or web browser through which a user can interact with embodiments of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., a communication network). Examples of communication networks include local area networks (LANs), wide area networks (WANs), and the Internet.

[0163] Computer systems can include clients and servers. Clients and servers are generally located far apart and typically interact via communication networks. Client-server relationships are created by computer programs running on the respective computers and having a client-server relationship with each other. Servers can be cloud servers, servers in distributed systems, or servers incorporating blockchain technology.

[0164] It should be understood that the various forms of processes shown above can be used to rearrange, add, or delete steps. For example, the steps described in this disclosure can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution disclosed in this disclosure can be achieved, and this is not limited herein.

[0165] The specific embodiments described above do not constitute a limitation on the scope of protection of this disclosure. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this disclosure should be included within the scope of protection of this disclosure.

Claims

1. An information exchange method, applied to a server, comprising: In response to a service request sent by a client, detect whether the service request carries a service request tag; If not carried, based on the probability that the client is a normal client, the first page information of one of the preset pages is sent to the client from the page information of a variety of preset pages that are pre-stored. The first page information includes the page URL of the preset page and the page information required by the client to render the preset page. After receiving the rendering result returned by the client after successfully rendering the preset page based on the first page information, the client is determined to be a normal client; A service request tag is sent to the client so that the client requests a service based on the service request tag.

2. The method according to claim 1, wherein, Sending a service request marker to the client includes: If the rendering result includes verification information entered by the user on the preset page, verify whether the verification information is valid. If the verification information is valid, a service request flag is sent to the client.

3. The method according to claim 1 or 2, wherein, After sending the service request tag to the client, the method further includes: Send the second page information of the trigger page to the client, wherein the trigger page is a page used to trigger the service request.

4. An information exchange method, applied to a client, comprising: Send a service request to the server; After the server detects that the service request does not carry a service request tag, it sends the first page information of one of the preset pages from the page information of a variety of preset pages in a pre-stored manner, based on the probability that the client is a normal client. The first page information includes the page URL of the preset page and the page information required by the client to render the preset page. Render the preset page based on the information from the first page; The server is then informed of the rendering result after successfully rendering the preset page. After the server receives the rendering result, it determines that the client is a normal client and sends a service request tag.

5. The method according to claim 4, wherein, The step of sending the rendering result to the server after successfully rendering the preset page includes: Obtain the verification information entered by the user in the rendered preset page; The server is then fed back a rendering result including the verification information. The step of obtaining the service request tag sent by the server after receiving the rendering result includes: Obtain the service request tag sent by the server after determining that the verification information is valid.

6. The method according to claim 4 or 5, wherein, After obtaining the service request tag sent by the server, the method further includes: Obtain the second page information of the trigger page sent by the server, wherein the trigger page is: a page used to trigger the service request; The trigger page is rendered based on the information from the second page.

7. An information interaction device applied to a server, comprising: The anomaly detection module is used to detect whether a service request tag is carried in the service request in response to a service request sent by the client. The first information sending module is used to send the first page information of one of the preset pages to the client from the page information of a variety of preset pages stored in advance, based on the probability that the client is a normal client, if the first page information is not carried. The first page information includes the page URL of the preset page and the page information required by the client to render the preset page. The result receiving module is used to receive the rendering result returned by the client after successfully rendering the preset page based on the first page information, and to determine that the client is a normal client; The tag sending module is used to send a service request tag to the client so that the client requests a service based on the service request tag.

8. The apparatus according to claim 7, wherein, The tag sending module is specifically used for: If the rendering result includes verification information entered by the user on the preset page, verify whether the verification information is valid. If the verification information is valid, a service request flag is sent to the client.

9. The apparatus according to claim 7 or 8, further comprising: The second information sending module is used to send second page information of the trigger page to the client after sending the service request flag to the client, wherein the trigger page is a page used to trigger the service request.

10. An information interaction device, applied to a client, comprising: The request sending module is used to send service requests to the server; The first information acquisition module is used to acquire, after the server detects that the service request does not carry a service request tag, the first page information of one of the preset pages sent from the page information of a variety of preset pages in a pre-stored manner, based on the probability that the client is a normal client. The first page information includes the page URL of the preset page and the page information required by the client to render the preset page. The page rendering module is used to render the preset page based on the first page information; The result feedback module is used to send the rendering result to the server after successfully rendering the preset page. The tag acquisition module is used to obtain the service request tag sent by the server after receiving the rendering result, determining that the client is a normal client.

11. The apparatus according to claim 10, wherein, The result feedback module is specifically used for: Obtain the verification information entered by the user in the rendered preset page; The server is then fed back a rendering result including the verification information. The step of obtaining the service request tag sent by the server after receiving the rendering result includes: Obtain the service request tag sent by the server after determining that the verification information is valid.

12. The apparatus according to claim 10 or 11, further comprising: The second obtaining module is used to obtain second page information of the trigger page sent by the server after obtaining the service request tag sent by the server, wherein the trigger page is: a page used to trigger the service request; The trigger page is rendered based on the information from the second page.

13. An electronic device, comprising: At least one processor; as well as A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-3 or 4-6.

14. A non-transitory computer-readable storage medium storing computer instructions, wherein, The computer instructions are used to cause the computer to perform the method according to any one of claims 1-3 or 4-6.

15. A computer program product comprising a computer program that, when executed by a processor, implements the method according to any one of claims 1-3 or 4-6.

Images