Service request decision-making method, device and equipment

By combining the static and dynamic characteristics of the client, simplified decision-making is generated, and the problem of poor decision-making flexibility in the existing technology is solved, and more efficient service request decision-making is achieved.

CN119232799AActive Publication Date: 2024-12-31BEIJING ZITIAO NETWORK TECH CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202310780911.X
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-06-28
Publication Date
2024-12-31
Estimated Expiration
2043-06-28

AI Technical Summary

Technical Problem

In the prior art, when a server decides whether to respond to a client service request, it only relies on the static characteristics of the client, resulting in poor decision flexibility and inability to fully utilize the client's performance.

Method used

By receiving service requests sent by the client, determine the static and dynamic characteristics of the client, combine the logical relationship between static decision conditions and dynamic decision conditions, generate simplified decisions, and send them to the client to make it generate a response based on dynamic characteristics. result.

Benefits of technology

Improves the flexibility of service request decision making, makes full use of client performance, and enhances the accuracy and adaptability of decisions.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119232799A_ABST
    Figure CN119232799A_ABST
Patent Text Reader

Abstract

The invention discloses a service request decision-making method, device and equipment, and aims to improve the flexibility of service request decision-making. Client static features are first determined through a service request. Then obtaining a decision corresponding to the service request, wherein the decision comprises a static decision condition, a first dynamic decision condition and a logical relationship among the decision conditions; and according to a matching result of the static characteristics of the client and the static decision-making conditions and a logical relationship between the decision-making conditions, simplifying the decision-making to generate a simplified decision-making. And if the simplified decision comprises at least one second dynamic decision condition, sending the simplified decision to the client, so that the client generates a decision result indicating whether the service request can be responded or not according to the dynamic characteristics of the client and the second dynamic decision condition.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of Internet technology, and in particular to a service request decision method, device and equipment. Background Art

[0002] In Internet applications, the client will initiate a service request to the server to request a response to a certain service. Due to the limitation of client performance, the server will make a decision to determine whether the client can respond to the service request. Currently, the server generally makes corresponding decisions based on the static characteristics of the client. However, this decision-making method has poor flexibility and cannot fully utilize the performance of the client. Summary of the invention

[0003] In view of this, embodiments of the present application provide a service request decision method, apparatus, and device to improve the flexibility of service request decision making.

[0004] To solve the above problems, the technical solutions provided in the embodiments of the present application are as follows:

[0005] In a first aspect, an embodiment of the present application provides a service request decision method, the method comprising:

[0006] Receiving a service request sent by a client, and determining static characteristics of the client through the service request;

[0007] Obtaining a decision corresponding to the service request, the decision including decision conditions and logical relationships between the decision conditions; the decision conditions including static decision conditions and a first dynamic decision condition;

[0008] According to the matching result between the static feature of the client and the static decision condition, and the logical relationship between the decision conditions, simplify the decision to generate a simplified decision;

[0009] If the simplified decision includes a second dynamic decision condition, sending the simplified decision to the client, so that the client generates a decision result indicating whether the service request can be responded to according to a matching result between the client dynamic feature and the second dynamic decision condition;

[0010] If the simplified decision includes a plurality of second dynamic decision conditions and the logical relationships between the second dynamic decision conditions, the simplified decision is sent to the client, so that the client generates a decision result indicating whether the service request can be responded to according to the matching result between the client dynamic feature and the second dynamic decision conditions, and the logical relationships between the second dynamic decision conditions;

[0011] The second dynamic decision condition is at least one of the first dynamic decision conditions.

[0012] In a second aspect, an embodiment of the present application provides a service request decision device, the device comprising:

[0013] A determination unit, configured to receive a service request sent by a client, and determine a static feature of the client through the service request;

[0014] A first acquisition unit, configured to acquire a decision corresponding to the service request, wherein the decision includes a decision condition and a logical relationship between the decision conditions; the decision condition includes a static decision condition and a first dynamic decision condition;

[0015] A generating unit, configured to simplify the decision according to the matching result between the static feature of the client and the static decision condition, and the logical relationship between the decision conditions, and generate a simplified decision;

[0016] A first sending unit, configured to send the simplified decision to the client if the simplified decision includes a second dynamic decision condition, so that the client generates a decision result indicating whether the service request can be responded to according to a matching result between the client dynamic feature and the second dynamic decision condition;

[0017] a second sending unit, configured to send the simplified decision to the client if the simplified decision includes a plurality of second dynamic decision conditions and a logical relationship between the second dynamic decision conditions, so that the client generates a decision result indicating whether the service request can be responded to according to a matching result between the client dynamic feature and the second dynamic decision condition and the logical relationship between the second dynamic decision conditions;

[0018] The second dynamic decision condition is at least one of the first dynamic decision conditions.

[0019] In a third aspect, an embodiment of the present application provides a service request decision device, comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the service request decision method as described above is implemented.

[0020] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, in which instructions are stored. When the instructions are executed on a terminal device, the terminal device executes the service request decision method as described above.

[0021] It can be seen that the embodiments of the present application have the following beneficial effects:

[0022] After receiving the service request sent by the client, the embodiment of the present application first determines the static characteristics of the client through the service request. Then the decision corresponding to the service request is obtained, which includes the static decision condition, the first dynamic decision condition and the logical relationship between the decision conditions. According to the matching results of the static characteristics of the client and the static decision conditions, and the logical relationship between the decision conditions, the decision is simplified to generate a simplified decision. If the simplified decision includes at least one second dynamic decision condition, the simplified decision is sent to the client so that the client can generate a decision result indicating whether it can respond to the service request based on the dynamic characteristics of the client and the second dynamic decision condition. In this way, in the process of generating the decision result, the static characteristics of the client that are fixed and unchanged and the dynamic characteristics of the client that change in real time are combined, so that the performance of the client can be fully utilized and the flexibility of the service request decision is improved. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] Figure 1 A schematic diagram of an exemplary application scenario provided for an embodiment of the present application;

[0024] Figure 2 A flowchart of a service request decision method provided in an embodiment of the present application;

[0025] Figure 3 A flowchart for generating a simplified decision-making process provided in an embodiment of the present application;

[0026] Figure 4 A schematic diagram of generating a simplified decision provided in an embodiment of the present application;

[0027] Figure 5 Another schematic diagram of generating a simplified decision provided in an embodiment of the present application;

[0028] Figure 6 A schematic diagram of a service request decision device provided in an embodiment of the present application;

[0029] Figure 7 A schematic diagram of a device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0030] In order to make the above-mentioned purposes, features and advantages of the embodiments of the present application more obvious and easy to understand, the embodiments of the present application are further described in detail below in conjunction with the accompanying drawings and specific implementation methods.

[0031] In order to facilitate understanding and explanation of the technical solution provided by the embodiments of the present application, the background technology of the embodiments of the present application will be described below.

[0032] In Internet applications, the client will initiate a service request to the server to request a response to a service. For example, the client requests to record at the highest recording resolution, or the client requests to play the video at the highest playback resolution. Due to the performance limitations of the client, the server will make a decision on the service request to determine whether the client can respond to the service request.

[0033] Currently, servers generally make decisions based on the static features of the client. For example, the server pre-sets the correspondence between the device model and the recording resolution that can be enabled, so that the client can only record at the highest recording resolution when it is installed on a high-end device. However, the state of the client changes at any time. For example, when recording a video, even high-end devices may experience freezes when the highest recording resolution is applied when the processor is heavily loaded. On the contrary, low-end devices can smoothly record at the highest recording resolution when the processor is lightly loaded and there is almost no background occupancy, which can also enhance the user experience. Therefore, the server only makes decisions based on the static features of the client, which is less active and cannot fully utilize the performance of the client.

[0034] Based on this, the embodiments of the present application provide a service request decision method, device and equipment. When making a service request decision, the server makes a decision based on the static characteristics of the client that are fixed and unchanged, and the client makes a decision based on the dynamic characteristics of the client that change in real time, thereby making full use of the performance of the client and improving the flexibility of the service request decision.

[0035] In order to facilitate understanding of the service request decision method provided in the embodiment of the present application, Figure 1 See the example scenario shown in the figure. Figure 1 As shown, this figure is a schematic diagram of an exemplary application scenario provided in an embodiment of the present application.

[0036] The embodiment of the present application can be applied to a server that makes service request decisions. When a client needs to request a response to a certain service from a server, it triggers sending a service request to the server. The server can receive the service request sent by the client and determine the static features of the client through the service request. Then obtain the decision corresponding to the service request, which includes a static decision condition, a first dynamic decision condition, and a logical relationship between the decision conditions. Match the static features of the client with the static decision conditions, simplify the decision, and generate a simplified decision. If the simplified decision includes at least one second dynamic decision condition, send the simplified decision to the client so that the client generates a decision result indicating whether the service request can be responded to based on the dynamic features of the client and the second dynamic decision condition. In addition, if the simplified decision is a decision result indicating whether the service request can be responded to, the decision result is directly sent to the client. Thus, the server makes a service request decision based on the static features of the client that are fixed and unchanged, and the client makes a service request decision based on the dynamic features of the client that change in real time, so that the performance of the client can be fully utilized and the flexibility of the service request decision is improved.

[0037] Those skilled in the art will understand that Figure 1 The framework diagram shown is only an example in which the embodiments of the present application can be implemented. The scope of application of the embodiments of the present application is not limited by any aspect of the framework.

[0038] To facilitate understanding of the present application, a service request decision method provided in an embodiment of the present application is described below with reference to the accompanying drawings.

[0039] See also Figure 2 As shown, this figure is a flow chart of a service request decision method provided by an embodiment of the present application, such as Figure 2 As shown, the method may include S201-S205:

[0040] S201: receiving a service request sent by a client, and determining static features of the client through the service request.

[0041] When the client needs to request a response to a service from the server, it triggers the sending of a service request to the server. For example, when the client needs to record a video, it generates a service request and sends it to the server by selecting the required resolution for video recording and initiating a video recording request. The service request generally carries basic information about the client, such as the device model, client version, and operating system type of the client's device. The service request may also carry relevant information about the requested service, such as the service type, requested service parameters, etc. Specifically, the service type may be a recording service, a playback service, etc., and the requested service parameters may be a requested recording resolution, a requested playback resolution, etc.

[0042] After receiving the service request sent by the client, the server parses the service request and obtains the static features of the client. The static features of the client can be understood as the fixed features of the client, such as device hardware information, such as CPU model, running memory capacity, etc.

[0043] In a possible implementation, S201 receives a service request sent by a client, and a specific implementation of determining the static characteristics of the client through the service request may include:

[0044] A1: Receive the service request sent by the client and obtain the basic information of the client from the service request.

[0045] When the server receives the service request sent by the client, it can obtain the basic information of the client carried in the service request. In order to save the communication overhead between the client and the server, the information carried by the basic information of the client is generally limited. The server also needs to further determine the static characteristics of the client based on the basic information of the client.

[0046] A2: Determine the client static features corresponding to the client basic information based on the mapping relationship of the client basic information.

[0047] In the embodiment of the present application, the server may be pre-set with mapping relationships between different client basic information and client static features, such as the mapping relationship between device model and hardware information. Thus, the server can obtain the client static features corresponding to the client basic information according to the mapping relationship of the client basic information. That is, the server can obtain more diverse client static features through service requests.

[0048] S202: Obtain a decision corresponding to the service request, where the decision includes decision conditions and logical relationships between decision conditions; the decision conditions include static decision conditions and a first dynamic decision condition.

[0049] The server is pre-set with decisions corresponding to different service requests. For example, a decision on whether a device with certain hardware information can record at the highest resolution. The decision result is generally a binary classification result of yes or no.

[0050] A decision includes decision conditions and the logical relationship between decision conditions. The logical relationship between decision conditions generally refers to being established through AND logic or being established through OR logic. For example, a decision includes decision conditions C1, C2, and C3. When the logical relationship between the decision conditions is that C1, C2, and C3 are all true, the decision is true, that is, the logical relationship between the decision conditions is established through AND logic. For another example, a decision includes decision conditions C1, C2, and C3. When the logical relationship between the decision conditions is that C1, C2, or C3 is true, the decision is true, that is, the logical relationship between the decision conditions is established through OR logic.

[0051] The decision conditions include static decision conditions and first dynamic decision conditions. The static decision conditions can be matched with the static features of the client, and the server obtains a matching result of whether the static features of the client match the corresponding static decision conditions. The dynamic decision conditions can be matched with the dynamic features of the client, and the client obtains a matching result of whether the dynamic features of the client match the corresponding dynamic decision conditions. In this embodiment, the dynamic decision condition included in the decision is the first dynamic decision condition.

[0052] S203: Simplify the decision according to the matching result between the static features of the client and the static decision conditions, and the logical relationship between the decision conditions, and generate a simplified decision.

[0053] The server can match the static features of the client with the corresponding static decision conditions to obtain a matching result, and then simplify the decision according to the logical relationship between the decision conditions to generate a simplified decision. If the matching of the static features of the client cannot directly determine whether the client can respond to the service request, it means that the dynamic features of the client need to be matched with the dynamic decision conditions, and a simplified decision including at least one second dynamic decision condition is generated.

[0054] In the process of generating a simplified decision, the decision may be pruned according to the matching results between the static features of the client and the static decision conditions, and some decision conditions may be removed. Then the simplified decision includes a second dynamic decision, or includes multiple second dynamic decision conditions and the logical relationship between the second dynamic decision conditions, and the second dynamic decision condition is at least one of the first dynamic decision conditions. On the one hand, the server has completed the matching between the static features of the client and the static decision conditions, so the simplified decision no longer includes the static decision conditions. On the other hand, according to the matching results between the static features of the client and the static decision conditions, and the logical relationship between the decision conditions, it has been determined that some dynamic decision conditions cannot be met, and these dynamic decision conditions are also removed from the decision, so that the number of second dynamic decision conditions included in the simplified decision is less than or equal to the number of first dynamic decision conditions.

[0055] In an embodiment of the present application, S203 simplifies the decision based on the matching results between the static features of the client and the static decision conditions, as well as the logical relationship between the decision conditions. The specific implementation process of generating a simplified decision can be found in subsequent embodiments and will not be repeated here.

[0056] S204: If the simplified decision includes a second dynamic decision condition, the simplified decision is sent to the client, so that the client generates a decision result indicating whether the service request can be responded to according to the matching result between the client dynamic feature and the second dynamic decision condition.

[0057] S205: If the simplified decision includes multiple second dynamic decision conditions and logical relationships between the second dynamic decision conditions, the simplified decision is sent to the client so that the client generates a decision result indicating whether the service request can be responded to based on the matching results between the client dynamic characteristics and the second dynamic decision conditions, and the logical relationships between the second dynamic decision conditions.

[0058] The simplified decision is sent to the client. When the simplified decision includes a second dynamic decision condition, the client needs to obtain the current client dynamic features corresponding to the second dynamic decision condition. The client dynamic features can be understood as the features of the client that are currently changing in real time, such as processor temperature, processor load, memory load, power, battery load, behavior markers, etc. Further, the client matches the client dynamic features with the corresponding second dynamic decision condition, and generates the final decision result based on the matching result.

[0059] Similarly, when the simplified decision includes a second dynamic decision condition and a logical relationship between the second dynamic decision conditions, the client needs to obtain the current client dynamic feature corresponding to the second dynamic decision condition. The client matches the client dynamic feature with the corresponding second dynamic decision condition, and generates a final decision result based on the matching result and the logical relationship between the second dynamic decision conditions.

[0060] When the decision result indicates that the client can respond to the service request, the client responds to the service request, and when the decision result indicates that the client cannot respond to the service request, the client cannot respond to the service request.

[0061] In a possible implementation, after S203, the process further includes: if the simplified decision is a decision result indicating whether the service request can be responded to, sending the decision result to the client.

[0062] The server can match the static features of the client with the corresponding static decision conditions to obtain a matching result, and then simplify the decision according to the logical relationship between the decision conditions to generate a simplified decision. If the decision can be simplified by matching the static features of the client to directly obtain the judgment result of whether the client can respond to the service request, a simplified decision is generated. In this case, the simplified decision generated is directly a decision result for indicating whether the service request can be responded to.

[0063] The decision result is sent to the client. If the client receives the decision result, when the decision result indicates that the client can respond to the service request, the client responds to the service request. When the decision result indicates that the client cannot respond to the service request, the client cannot respond to the service request.

[0064] To facilitate understanding, the above-mentioned embodiments are further described by way of examples.

[0065] The client sends a service request to the server to record the video at the highest recording resolution. The server obtains the decision corresponding to the service request: when the device processor is H1 and the processor temperature is less than 40 degrees, the video can be recorded at the highest recording resolution, otherwise the video can only be recorded at the default resolution. Among them, the device processor is H1 as a static decision condition, the processor temperature is less than 40 degrees as the first dynamic decision condition, and the logical relationship between the decision conditions is established through the AND logic.

[0066] The server obtains the client static feature "device processor CPU" according to the service request. If the CPU is not H1, a simplified decision is directly generated as the decision result, that is, video recording cannot be performed at the highest recording resolution. If the CPU is H1, a simplified decision is generated, and the simplified decision includes the second dynamic decision condition that the processor temperature is less than 40 degrees.

[0067] Send the decision result or simplified decision to the client. When the client receives a simplified decision including the second dynamic decision condition, the client dynamic feature "current processor temperature" is obtained to determine whether the current processor temperature is less than 40 degrees. When the processor temperature is less than 40 degrees, a decision result is generated that the video can be recorded at the highest recording resolution, and the client records the video at the highest recording resolution. When the processor temperature is not less than 40 degrees, a decision result is generated that the video cannot be recorded at the highest recording resolution, and the client can only record the video at the default recording resolution. When the client receives a simplified decision as a decision result, the client can only record the video at the default recording resolution.

[0068] In this way, the service request decision can be made by the server and the client in collaboration, which can combine the performance indicators of the device dimension with the device status at the current time to complete the combined decision, making the decision more flexible.

[0069] Based on the description of S201-S205, after receiving the service request sent by the client, the embodiment of the present application first determines the static characteristics of the client through the service request. Then the decision corresponding to the service request is obtained, which includes the static decision condition, the first dynamic decision condition and the logical relationship between the decision conditions. According to the matching results of the static characteristics of the client and the static decision conditions, and the logical relationship between the decision conditions, the decision is simplified to generate a simplified decision. If the simplified decision includes at least one second dynamic decision condition, the simplified decision is sent to the client so that the client can generate a decision result indicating whether the service request can be responded to based on the dynamic characteristics of the client and the second dynamic decision condition. In this way, in the process of generating the decision result, the static characteristics of the client that are fixed and unchanged and the dynamic characteristics of the client that change in real time are combined, so that the performance of the client can be fully utilized and the flexibility of the service request decision is improved.

[0070] See also Figure 3 As shown, a flowchart of generating a simplified decision is shown. In a possible implementation, S203 simplifies the decision according to the matching result between the static feature of the client and the static decision condition, and the logical relationship between the decision conditions. The specific implementation of generating the simplified decision may include S301-S305:

[0071] S301: Match the static features of the client with the corresponding static decision conditions to generate a matching result.

[0072] After obtaining the static features of the client, the static decision conditions corresponding to the static features of the client are identified from the decision and matched to generate a matching result. For example, if the static feature of the client is "device processor", the static decision condition "device processor is H1" can be identified from the decision and matched to generate a matching result of "whether the device processor is H1".

[0073] In a possible implementation, the static features of the client and the static decision conditions may be matched by a matching model, such as a neural network model, a deep learning model, etc. Then S301 matches the static features of the client with the corresponding static decision conditions, and the specific implementation of generating the matching result may include:

[0074] If the static decision condition corresponding to the client static feature is a model judgment decision condition, the client static feature is input into the matching model of the corresponding static decision condition to obtain a matching result of whether the client static feature matches the corresponding static decision condition.

[0075] When the static decision condition is a model-judged decision condition, it means that the pre-established matching model is required to match the static features of the client with the static decision condition. Then the static features of the client are input into the matching model of the corresponding static decision condition, and the matching result of whether the static features of the client match the corresponding static decision condition is obtained from the output of the matching model. For example, if the static features of the client are "client account information" and the corresponding static decision condition is "the client account is a high-quality account", the static features of the client can be input into the matching model of the corresponding static decision condition, and the matching result of "whether the client account is a high-quality account" can be obtained from the matching model.

[0076] S302: According to the matching results and the logical relationship between the decision conditions, the corresponding decision conditions in the decision are removed.

[0077] According to the matching results, the unreachable logical relationship branches in the decision can be directly removed. After the removal, the decision only includes the potentially reachable dynamic decision conditions and their logical relationships.

[0078] In a possible implementation, the specific implementation of S302 removing the corresponding decision conditions in the decision according to the matching result and the logical relationship between the decision conditions may include:

[0079] If the matching result makes the corresponding logical relationship unsatisfied, the logical relationship corresponding to the matching result is determined as an unreachable logical relationship, and the decision condition associated with the unreachable logical relationship is removed from the decision;

[0080] If the matching result satisfies the corresponding logical relationship, the logical relationship corresponding to the matching result is determined as a reachable logical relationship, and the static decision condition associated with the reachable logical relationship is removed from the decision.

[0081] In the embodiment of the present application, if the matching result of a static decision condition makes the corresponding logical relationship unsatisfied, then other decision conditions associated with the logical relationship do not need to be matched, and the decision conditions associated with the logical relationship can be removed from the decision. Figure 4 As shown in FIG. 1 , it is a schematic diagram of generating a simplified decision, assuming that C1 is the first dynamic decision condition, C2 is the static decision condition, and the logical relationship between C1 and C2 is AND logic. When the matching result of C2 is false, the logical relationship between C1 and C2 must be false. At this time, the logical relationship is an unreachable logical relationship, and the decision conditions C1 and C2 associated with the logical relationship are removed from the decision.

[0082] If the matching result of a static decision condition can satisfy the corresponding logical relationship, the static decision condition associated with the logical relationship is removed from the decision, so that the decision after removal only contains the dynamic decision condition. Figure 4 As shown, when the matching result of C2 is true, the logical relationship between C1 and C2 may be true. At this time, the logical relationship is a reachable logical relationship. The static decision condition C2 associated with the logical relationship is removed from the decision. The decision after removal only includes C1. At this time, C1 is changed to the second dynamic decision condition C1.

[0083] For example, see Figure 5 As shown, it is another schematic diagram for generating simplified decisions. Assume that C1, C4, and C5 are the first dynamic decision conditions, C2 and C3 are static decision conditions, the logical relationship between C1 and C2 is AND logic, the logical relationship between C3 and C4 is AND logic, and the logical relationship between the two AND logics and C5 is OR logic. When the matching result of C3 is false, the logical relationship corresponding to C3 is not satisfied, and the logical relationship is an unreachable logical relationship. The decision conditions C3 and C4 associated with the logical relationship are removed from the decision. When the matching result of C2 is true, the logical relationship corresponding to C2 may be satisfied, and the logical relationship is a reachable logical relationship. The static decision condition C2 associated with the logical relationship is removed from the decision. And OR logic is also a reachable logical relationship, and the first dynamic decision condition C5 can be retained. Then the decision after removal includes C1 and C5, and the logical relationship between C1 and C5 is OR logic. At this time, C1 and C5 are the second dynamic decision conditions.

[0084] S303: If there are no remaining decision conditions in the decision after the corresponding decision conditions in the decision are removed, a simplified decision is obtained as the decision result.

[0085] When there are no remaining decision conditions in the decision after removal, it means that the decision result can be obtained directly. For example, see Figure 4 As shown in FIG. 1 , when both decision conditions C1 and C2 are removed from the decision, it means that the decision is false, and the decision result can be directly obtained. At this time, a simplified decision is obtained as the decision result.

[0086] S304: If there is a remaining first dynamic decision condition in the decision after the corresponding decision conditions in the decision are removed, the remaining first dynamic decision condition in the decision is determined as the second dynamic decision condition to obtain a simplified decision including a second dynamic decision condition.

[0087] S305: If there are multiple remaining first dynamic decision conditions in the decision after the corresponding decision conditions in the decision are removed, the remaining first dynamic decision conditions in the decision are determined as second dynamic decision conditions, and the logical relationship between the second dynamic decision conditions is obtained to obtain a simplified decision including multiple second dynamic decision conditions and the logical relationship between the second dynamic decision conditions.

[0088] If there is one remaining first dynamic decision condition in the simplified decision, the remaining first dynamic decision condition in the decision is determined as the second dynamic decision condition, and a simplified decision including one second dynamic decision condition is obtained. If there are multiple remaining first dynamic decision conditions in the simplified decision, the remaining first dynamic decision conditions in the decision are determined as the second dynamic decision conditions and the logical relationship between the second dynamic decision conditions is obtained as the simplified logic. At this time, it means that the decision result cannot be directly obtained by matching the static decision conditions, and the client needs to make further decisions based on the simplified decision including the second dynamic decision condition.

[0089] In an embodiment of the present application, the decision can be pruned, and finally a simplified logic is obtained that only includes the second dynamic decision condition or only includes the second dynamic decision condition and its logical relationship, or a decision result that directly determines whether the decision is valid, thereby enabling the server and the client to collaborate in completing the service request decision.

[0090] In addition, the embodiment of the present application can also perform AB experiments on the decision to obtain a better decision. In a possible implementation, the specific implementation of S202 obtaining the decision corresponding to the service request may include: obtaining the first version decision or the second version decision corresponding to the service request.

[0091] Based on this, a service request decision method provided in an embodiment of the present application may also include:

[0092] B1: After the client responds to the service request, the response evaluation parameters of the first version decision or the second version decision are obtained.

[0093] B2: According to the response evaluation parameters of the first version decision or the second version decision, determine the first version decision or the second version decision as the decision corresponding to the service request.

[0094] When setting a decision, sometimes you may not be able to determine which version of the decision is better, for example, whether it is better to allow the client to record at the highest recording resolution when the processor temperature is less than 40 degrees, or to allow the client to record at the highest recording resolution when the processor temperature is less than 45 degrees. You can pre-set multiple versions of the policy and conduct AB experiments on different versions of the decision to determine the better version of the decision. In actual applications, clients can be divided into different groups, and each group of clients uses a version of the decision to make service request decisions.

[0095] Specifically, for example, the decision is divided into a first version decision and a second version decision, and the client can be divided into two groups. After receiving the service request sent by the client, the server obtains the first version decision or the second version decision corresponding to the service request as the decision corresponding to the service request according to the group to which the client belongs, and then executes the steps S203-S205 of the embodiment of the present application. After the client responds to the service request, the response evaluation parameters of the first version decision or the second version decision can be obtained from the client. The response evaluation parameters are relevant service response evaluation parameters when the client responds to the service request, such as response time, response effect parameters, etc.

[0096] According to the response evaluation parameters of the first version decision or the second version decision obtained from different clients, by comparing the response evaluation parameters of the first version decision or the second version decision, it can be determined which version of the decision, the first version decision or the second version decision, is better, and the better decision is determined as the decision corresponding to the service request finally used.

[0097] In an embodiment of the present application, AB experiments may also be performed on different versions of decisions to obtain better decisions, thereby further improving the effectiveness of service request decisions.

[0098] In addition, the embodiment of the present application can also perform a grayscale test on the decision before the decision is updated to determine whether to update the decision. In a possible implementation, the specific implementation of S202 obtaining the decision corresponding to the service request may include: when the client is determined to be the target client through the service request, obtaining the update version decision corresponding to the service request.

[0099] Based on this, a service request decision method provided in an embodiment of the present application may also include:

[0100] C1: After the client responds to the service request, obtain the response evaluation parameters of the update version decision;

[0101] C2: Determine whether to determine the update version decision as the decision corresponding to the service request based on the response evaluation parameter of the update version decision.

[0102] When it is necessary to update the decision version, if the new version of the decision needs a safety guarantee to be widely used, in the embodiment of the present application, it is possible to first observe the volume according to a certain ratio and time, and let some clients use the new version of the decision first. If there is no abnormal situation, the decision version can be updated.

[0103] In actual applications, some clients can be selected from the clients as target clients, for example, 10% of the clients are randomly selected as target clients. After the server receives the service request sent by the client, if the client belongs to the target client, the update version decision corresponding to the service request is obtained as the decision corresponding to the service request, and then the steps S203-S205 of the embodiment of the present application are executed. After the client responds to the service request, the response evaluation parameters of the update version decision can be obtained from the client. The response evaluation parameters are relevant service response evaluation parameters when the client responds to the service request, such as response time, response effect parameters, etc. According to the response evaluation parameters of the update version decision obtained from different target clients, it can be determined whether the update version decision is determined as the decision corresponding to the service request that is finally used.

[0104] In an embodiment of the present application, a grayscale release experiment can also be performed on the decision to update the version to ensure the security of the decision when performing a version update.

[0105] Based on a service request decision method provided by the above method embodiment, an embodiment of the present application also provides a service request decision device, which will be described below in conjunction with the accompanying drawings.

[0106] See also Figure 6 As shown in FIG. 1 , this figure is a schematic diagram of the structure of a service request decision device provided in an embodiment of the present application. Figure 6 As shown, the service request decision device includes:

[0107] The determining unit 601 is used to receive a service request sent by a client, and determine a static feature of the client through the service request;

[0108] A first acquisition unit 602 is used to acquire a decision corresponding to the service request, wherein the decision includes a decision condition and a logical relationship between the decision conditions; the decision condition includes a static decision condition and a first dynamic decision condition;

[0109] A generating unit 603, configured to simplify the decision according to the matching result between the static feature of the client and the static decision condition, and the logical relationship between the decision conditions, and generate a simplified decision;

[0110] A first sending unit 604 is configured to send the simplified decision to the client if the simplified decision includes a second dynamic decision condition, so that the client generates a decision result indicating whether the service request can be responded to according to a matching result between the client dynamic feature and the second dynamic decision condition;

[0111] The second sending unit 605 is configured to send the simplified decision to the client if the simplified decision includes multiple second dynamic decision conditions and the logical relationship between the second dynamic decision conditions, so that the client generates a decision result indicating whether the service request can be responded to according to the matching result between the client dynamic feature and the second dynamic decision condition and the logical relationship between the second dynamic decision conditions;

[0112] The second dynamic decision condition is at least one of the first dynamic decision conditions.

[0113] In a possible implementation manner, the device further includes:

[0114] The third sending unit is configured to send the decision result to the client if the simplified decision is a decision result indicating whether the service request can be responded to.

[0115] In a possible implementation, the generating unit includes:

[0116] A matching subunit, used to match the client static features with corresponding static decision conditions to generate a matching result;

[0117] A removal subunit, used for removing corresponding decision conditions in the decision according to the matching result and the logical relationship between the decision conditions;

[0118] A first determining subunit is used to obtain a simplified decision as a decision result if there are no remaining decision conditions in the decision after removing the corresponding decision conditions in the decision;

[0119] A second determining subunit is configured to determine the remaining first dynamic decision condition in the decision as a second dynamic decision condition if there is a remaining first dynamic decision condition in the decision after the corresponding decision condition in the decision is removed, so as to obtain a simplified decision including a second dynamic decision condition;

[0120] The third determination subunit is used to determine the remaining first dynamic decision conditions in the decision as second dynamic decision conditions if there are multiple remaining first dynamic decision conditions in the decision after the corresponding decision conditions in the decision are removed, and obtain the logical relationship between the second dynamic decision conditions to obtain a simplified decision including multiple second dynamic decision conditions and the logical relationship between the second dynamic decision conditions.

[0121] In a possible implementation manner, the removal subunit is specifically used for:

[0122] If the matching result causes the corresponding logical relationship to be unsatisfied, determining the logical relationship corresponding to the matching result as an unreachable logical relationship, and removing the decision condition associated with the unreachable logical relationship from the decision;

[0123] If the matching result satisfies the corresponding logical relationship, the logical relationship corresponding to the matching result is determined as a reachable logical relationship, and the static decision condition associated with the reachable logical relationship is removed from the decision.

[0124] In a possible implementation manner, the matching subunit is specifically used for:

[0125] If the static decision condition corresponding to the client static feature is a model judgment decision condition, the client static feature is input into the matching model of the corresponding static decision condition to obtain a matching result of whether the client static feature matches the corresponding static decision condition.

[0126] In a possible implementation manner, the determining unit includes:

[0127] The receiving and sending subunit is used to receive the service request sent by the client and obtain the basic information of the client from the service request;

[0128] The fourth determining subunit is configured to determine the static characteristics of the client corresponding to the basic information of the client according to the mapping relationship of the basic information of the client.

[0129] In a possible implementation manner, the first acquiring unit is specifically configured to:

[0130] Obtaining a first version decision or a second version decision corresponding to the service request;

[0131] The device also includes:

[0132] A second acquiring unit, configured to acquire a response evaluation parameter of the first version decision or the second version decision after the client responds to the service request;

[0133] A determining unit is used to determine the first version decision or the second version decision as a decision corresponding to the service request according to a response evaluation parameter of the first version decision or the second version decision.

[0134] In a possible implementation manner, the first acquiring unit is specifically configured to:

[0135] When the client is determined to be a target client through the service request, obtaining an update version decision corresponding to the service request;

[0136] The device also includes:

[0137] A third acquisition unit, configured to acquire a response evaluation parameter of the update version decision after the client responds to the service request;

[0138] A judging unit is used to judge whether to determine the update version decision as the decision corresponding to the service request according to the response evaluation parameter of the update version decision.

[0139] Based on a service request decision method provided in the above method embodiment, the present application also provides an electronic device, including: one or more processors; a storage device, on which one or more programs are stored, when the one or more programs are executed by the one or more processors, the one or more processors implement the service request decision method described in any of the above embodiments.

[0140] Reference below Figure 7 , which shows a schematic diagram of the structure of an electronic device 1300 suitable for implementing the embodiment of the present application. The terminal device in the embodiment of the present application may include but is not limited to mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (portable android devices), PMPs (Portable Media Players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs (televisions), desktop computers, etc. Figure 7 The electronic device shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0141] like Figure 7As shown, the electronic device 1300 may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 1301, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1302 or a program loaded from a storage device 1306 into a random access memory (RAM) 1303. In the RAM 1303, various programs and data required for the operation of the electronic device 1300 are also stored. The processing device 1301, the ROM 1302, and the RAM 1303 are connected to each other via a bus 1304. An input / output (I / O) interface 1305 is also connected to the bus 1304.

[0142] Typically, the following devices may be connected to the I / O interface 1305: an input device 1306 including, for example, a touch screen, a touch pad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; an output device 1307 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a storage device 1306 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 1309. The communication device 1309 may allow the electronic device 1300 to communicate with other devices wirelessly or by wire to exchange data. Although Figure 7 The electronic device 1300 is shown with various devices, but it should be understood that it is not required to implement or possess all the devices shown. More or fewer devices may be implemented or possessed instead.

[0143] In particular, according to an embodiment of the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present application includes a computer program product, which includes a computer program carried on a non-transitory computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication device 1309, or installed from the storage device 1306, or installed from the ROM 1302. When the computer program is executed by the processing device 1301, the above-mentioned functions defined in the method of the embodiment of the present application are executed.

[0144] The electronic device provided in the embodiment of the present application and the service request decision method provided in the above embodiment belong to the same inventive concept. The technical details not fully described in this embodiment can be referred to the above embodiment, and this embodiment has the same beneficial effects as the above embodiment.

[0145] Based on a service request decision method provided in the above method embodiment, an embodiment of the present application provides a computer-readable medium on which a computer program is stored, wherein when the program is executed by a processor, the service request decision method as described in any of the above embodiments is implemented.

[0146] It should be noted that the computer-readable medium in the embodiment of the present application may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to, an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In an embodiment of the present application, a computer-readable storage medium may be any tangible medium containing or storing a program that may be used by or in combination with an instruction execution system, device or device. In an embodiment of the present application, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, in which a computer-readable program code is carried. This propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. The computer readable signal medium may also be any computer readable medium other than a computer readable storage medium, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer readable medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination of the above.

[0147] In some embodiments, the client and the server may communicate using any currently known or future developed network protocol such as HTTP (HyperText Transfer Protocol), and may be interconnected with any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), an internet (e.g., the Internet), and a peer-to-peer network (e.g., an ad hoc peer-to-peer network), as well as any currently known or future developed network.

[0148] The computer-readable medium may be included in the electronic device, or may exist independently without being incorporated into the electronic device.

[0149] The computer-readable medium carries one or more programs. When the one or more programs are executed by the electronic device, the electronic device executes the service request decision method.

[0150] The computer program code for performing the operation of the embodiment of the present application can be written in one or more programming languages ​​or a combination thereof, and the above-mentioned programming languages ​​include but are not limited to object-oriented programming languages-such as Java, Smalltalk, C++, and also include conventional procedural programming languages-such as "C" language or similar programming languages. The program code can be executed completely on the user's computer, partially on the user's computer, as an independent software package, partially on the user's computer and partially on the remote computer, or completely on the remote computer or server. In the case of a remote computer, the remote computer can be connected to the user's computer through any type of network-including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computer (for example, using an Internet service provider to connect through the Internet).

[0151] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0152] The units involved in the embodiments described in this application may be implemented by software or hardware, wherein the name of the unit / module does not, in some cases, constitute a limitation on the unit itself.

[0153] The functions described above herein may be performed at least in part by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), and the like.

[0154] In the context of the present application embodiment, machine-readable medium can be a tangible medium that can contain or store a program for use by an instruction execution system, device or equipment or used in combination with an instruction execution system, device or equipment. Machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. Machine-readable medium can include but is not limited to electronic, magnetic, optical, electromagnetic, infrared or semiconductor systems, devices or equipment, or any suitable combination of the above. More specific examples of machine-readable storage media can include electrical connections based on one or more lines, portable computer disks, hard disks, random access memories (RAM), read-only memories (ROM), erasable programmable read-only memories (EPROM or flash memory), optical fibers, portable compact disk read-only memories (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the above.

[0155] It should be noted that the various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments, and the same or similar parts between the various embodiments can be referred to each other. For the system or device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts can be referred to the method part description.

[0156] It should be understood that in the present application, "at least one (item)" means one or more, and "plurality" means two or more. "And / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the objects associated before and after are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

[0157] It should also be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.

[0158] The steps of the method or algorithm described in conjunction with the embodiments disclosed herein may be implemented directly using hardware, a software module executed by a processor, or a combination of the two. The software module may be placed in a random access memory (RAM), a memory, a read-only memory (ROM), an electrically programmable ROM, an electrically erasable programmable ROM, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

[0159] The above description of the disclosed embodiments enables those skilled in the art to implement or use the present application. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments shown herein, but will conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A service request decision method, characterized in that: The method comprises: Receiving a service request sent by a client, and determining static characteristics of the client through the service request; Obtaining a decision corresponding to the service request, the decision including decision conditions and logical relationships between the decision conditions; the decision conditions including static decision conditions and a first dynamic decision condition; According to the matching result between the static feature of the client and the static decision condition, and the logical relationship between the decision conditions, simplify the decision to generate a simplified decision; If the simplified decision includes a second dynamic decision condition, sending the simplified decision to the client, so that the client generates a decision result indicating whether the service request can be responded to according to a matching result between the client dynamic feature and the second dynamic decision condition; If the simplified decision includes a plurality of second dynamic decision conditions and the logical relationships between the second dynamic decision conditions, the simplified decision is sent to the client, so that the client generates a decision result indicating whether the service request can be responded to according to the matching result between the client dynamic feature and the second dynamic decision conditions, and the logical relationships between the second dynamic decision conditions; The second dynamic decision condition is at least one of the first dynamic decision conditions.

2. The method according to claim 1, characterized in that: The method further comprises: If the simplified decision is a decision result indicating whether the service request can be responded to, the decision result is sent to the client.

3. The method according to claim 1, characterized in that The step of simplifying the decision according to the matching result between the static feature of the client and the static decision condition, and the logical relationship between the decision conditions, to generate a simplified decision includes: Matching the client static features with corresponding static decision conditions to generate a matching result; According to the matching result and the logical relationship between the decision conditions, the corresponding decision conditions in the decision are removed; If after removing the corresponding decision conditions in the decision, there are no remaining decision conditions in the decision, a simplified decision is obtained as the decision result; If there is a remaining first dynamic decision condition in the decision after the corresponding decision condition in the decision is removed, the remaining first dynamic decision condition in the decision is determined as the second dynamic decision condition to obtain a simplified decision including a second dynamic decision condition; If there are multiple remaining first dynamic decision conditions in the decision after the corresponding decision conditions in the decision are removed, the remaining first dynamic decision conditions in the decision are determined as second dynamic decision conditions, and the logical relationship between the second dynamic decision conditions is obtained to obtain a simplified decision including multiple second dynamic decision conditions and the logical relationship between the second dynamic decision conditions.

4. The method according to claim 3, characterized in that The removing corresponding decision conditions in the decision according to the matching result and the logical relationship between the decision conditions includes: If the matching result causes the corresponding logical relationship to be unsatisfied, determining the logical relationship corresponding to the matching result as an unreachable logical relationship, and removing the decision condition associated with the unreachable logical relationship from the decision; If the matching result satisfies the corresponding logical relationship, the logical relationship corresponding to the matching result is determined as a reachable logical relationship, and the static decision condition associated with the reachable logical relationship is removed from the decision.

5. The method according to claim 3, characterized in that: The matching of the client static features with the corresponding static decision conditions to generate a matching result includes: If the static decision condition corresponding to the client static feature is a model judgment decision condition, the client static feature is input into the matching model of the corresponding static decision condition to obtain a matching result of whether the client static feature matches the corresponding static decision condition.

6. The method according to claim 1, characterized in that The receiving a service request sent by a client, and determining a static feature of the client through the service request, includes: Receive a service request sent by a client, and obtain basic information of the client from the service request; The client static features corresponding to the client basic information are determined based on the mapping relationship of the client basic information.

7. The method according to any one of claims 1 to 6, characterized in that: The obtaining a decision corresponding to the service request includes: Obtaining a first version decision or a second version decision corresponding to the service request; The method further comprises: After the client responds to the service request, obtaining a response evaluation parameter of the first version decision or the second version decision; According to the response evaluation parameter of the first version decision or the second version decision, the first version decision or the second version decision is determined as the decision corresponding to the service request.

8. The method according to any one of claims 1 to 6, characterized in that: The obtaining a decision corresponding to the service request includes: When the client is determined to be a target client through the service request, obtaining an update version decision corresponding to the service request; The method further comprises: After the client responds to the service request, obtaining a response evaluation parameter of the update version decision; According to the response evaluation parameter of the update version decision, it is determined whether to determine the update version decision as the decision corresponding to the service request.

9. A service request decision device, characterized in that: The device comprises: A determination unit, configured to receive a service request sent by a client, and determine a static feature of the client through the service request; A first acquisition unit, configured to acquire a decision corresponding to the service request, wherein the decision includes a decision condition and a logical relationship between the decision conditions; the decision condition includes a static decision condition and a first dynamic decision condition; A generating unit, configured to simplify the decision according to the matching result between the static feature of the client and the static decision condition, and the logical relationship between the decision conditions, and generate a simplified decision; A first sending unit, configured to send the simplified decision to the client if the simplified decision includes a second dynamic decision condition, so that the client generates a decision result indicating whether the service request can be responded to according to a matching result between the client dynamic feature and the second dynamic decision condition; a second sending unit, configured to send the simplified decision to the client if the simplified decision includes a plurality of second dynamic decision conditions and a logical relationship between the second dynamic decision conditions, so that the client generates a decision result indicating whether the service request can be responded to according to a matching result between the client dynamic feature and the second dynamic decision condition and the logical relationship between the second dynamic decision conditions; The second dynamic decision condition is at least one of the first dynamic decision conditions.

10. A service request decision device, characterized in that: include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the service request decision method according to any one of claims 1 to 8 is implemented.

11. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores instructions, and when the instructions are executed on the terminal device, the terminal device executes the service request decision method according to any one of claims 1 to 8.

Citation Information

Patent Citations

  • Record pair decision method and device

    CN104268135A

  • Risk control decision method and device, computer equipment and storage medium

    CN114693192A