State machine-based product page interface configuration method and computer device

Abstract

Embodiments of the present application relate to the field of interface configuration, and particularly relate to a product page interface configuration method based on a state machine and a computer device. A specific implementation of the method includes: a connector service system determining connector configuration information; a template processing service system obtaining an upstream interface request message and an upstream interface response message from a server; the template processing service system configuring request parameter template information; the template processing service system configuring response parameter template information; the template processing service system determining the request parameter template information and the response parameter template information as template configuration information; a rule engine service system configuring rule set configuration information; a state machine service system obtaining the connector configuration information, the template configuration information and the rule set configuration information from the server; and the state machine service system configuring state machine definition configuration information. The implementation can save a large amount of development cost, improve the maintainability of interface logic, reduce the connection period, and improve production efficiency.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of interface configuration, and specifically to a state machine-based product page interface configuration method and computer device. Background Art

[0002] As internet product businesses rapidly expand, platforms often need to connect to multiple upstream systems (insurance companies or intermediaries). Each upstream system's interface may contain both common and unique logic. Existing practices often require significant manpower and resources to develop the access logic for each upstream system individually through hard-coding. This results in multiple implementations of the same logic, each with its own unique naming conventions. This incurs significant development costs and makes subsequent maintenance and expansion difficult. Summary of the Invention

[0003] The content of this application is used to briefly introduce concepts that will be described in detail in the detailed description section below. The content of this application is not intended to identify key features or essential features of the technical solution for which protection is sought, nor is it intended to limit the scope of the technical solution for which protection is sought.

[0004] Some embodiments of the present application propose a state machine-based product page interface configuration method, a computer device, and a computer-readable storage medium to solve one or more of the technical problems mentioned in the above background technology section.

[0005] In the first aspect, some embodiments of the present application provide a state machine-based product page interface configuration method, which is applied to a product page interface configuration system. The above-mentioned product page interface configuration system includes: a connector service system, a template processing service system, a rule engine service system, and a state machine service system. The method includes: the above-mentioned connector service system determines the connector configuration information in response to receiving the upstream service identifier sent by the management terminal, and stores the above-mentioned connector configuration information in the server, wherein the above-mentioned connector configuration information includes: an upstream interface request message and an upstream interface response message; the above-mentioned template processing service system obtains the upstream interface request message and the upstream interface response message from the above-mentioned server; the above-mentioned template processing service system configures the request parameter template information based on the above-mentioned upstream interface request message to perform Format conversion processing; the above-mentioned template processing service system configures the response parameter template information based on the above-mentioned upstream interface response message to perform format conversion processing on the above-mentioned upstream interface response message; the above-mentioned template processing service system determines the above-mentioned request parameter template information and the above-mentioned response parameter template information as template configuration information, and stores the above-mentioned template configuration information in the above-mentioned server; the above-mentioned rule engine service system configures the rule set configuration information, and stores the above-mentioned rule set configuration information in the above-mentioned server; the above-mentioned state machine service system obtains the connector configuration information, template configuration information and rule set configuration information from the above-mentioned server; the above-mentioned state machine service system configures the state machine definition configuration information based on the above-mentioned connector configuration information, the above-mentioned template configuration information and the above-mentioned rule set configuration information, and stores the above-mentioned state machine definition configuration information in the server.

[0006] In a second aspect, the present application also provides a computer device, comprising a processor, a memory, and a computer program stored in the memory and executable by the processor, wherein when the computer program is executed by the processor, it implements the method described in any implementation of the first aspect.

[0007] In a third aspect, the present application further provides a computer-readable storage medium, on which a computer program is stored, wherein when the computer program is executed by a processor, the method described in any implementation of the first aspect is implemented.

[0008] The above various embodiments of the present application have the following beneficial effects: through the product page interface configuration method based on the state machine of some embodiments of the present application, a large amount of development cost can be saved, the maintainability of the interface logic is improved, the connection period is reduced, and the production efficiency is improved. Specifically, the reason why a large amount of cost needs to be invested and subsequent maintenance and expansion are difficult to start is that a large amount of manpower and material resources are needed to separately develop the access logic of each upstream system through hard coding, resulting in multiple implementations of the same logic with different names. Based on this, the product page interface configuration method based on the state machine of some embodiments of the present application first determines the connector configuration information in response to receiving the upstream service identifier sent by the management terminal, and stores the connector configuration information into the server. The connector configuration information includes upstream interface request messages and upstream interface response messages. In this way, different upstream services can be connected through the connector service system. Second, the template processing service system obtains the upstream interface request messages and the upstream interface response messages from the server. Then, the template processing service system configures request parameter template information based on the upstream interface request messages to perform format conversion processing on the upstream interface request messages. Then, the template processing service system configures response parameter template information based on the upstream interface response messages to perform format conversion processing on the upstream interface response messages. Then, the template processing service system determines the request parameter template information and the response parameter template information as template configuration information, and stores the template configuration information into the server. In this way, the data structure of the upstream interface request messages and the upstream interface response messages can be converted into the system built-in data structure through the template processing service system, without the need to maintain the system internally, reducing external code intrusion. Then, the rule engine service system configures rule set configuration information, and stores the rule set configuration information into the server. In this way, the business rules can be defined in a declarative manner through the rule engine service system without modifying the core code of the application. Then, the state machine service system obtains the connector configuration information, the template configuration information and the rule set configuration information from the server. Finally, the state machine service system configures state machine definition configuration information based on the connector configuration information, the template configuration information and the rule set configuration information, and stores the state machine definition configuration information into the server. In this way, the upstream service can be associated with the connector through the state machine service system to execute the upstream service in the order of the linked list, and the rule set configuration information is associated to automatically complete the business process.Therefore, by establishing an interface to the adaptation layer (i.e., the connector service system), encapsulating the common logic existing in the interface access into components, and configuring the calling sequence of different interfaces into a state machine, when a new upstream system is accessed, only the components that do not exist in the system need to be implemented, and the message template and interface calling state machine are configured according to the requirements of the upstream interface, which can save a lot of development cost, improve the maintainability of the interface logic, reduce the interface period, and improve the production efficiency. BRIEF DESCRIPTION OF DRAWINGS

[0009] The above and other features, aspects, and advantages of the present embodiments will become more apparent with reference to the following detailed description when taken in conjunction with the accompanying drawings. Throughout the drawings, similar reference signs indicate similar elements or parts. It should be understood that the drawings are schematic and elements and parts are not necessarily to scale.

[0010] Figure 1 is a flowchart of some embodiments of a state machine-based product page interface configuration method according to the present application;

[0011] Figure 2 is a structural schematic diagram of some embodiments of a product page interface configuration system according to the present application;

[0012] Figure 3 is a structural schematic diagram of a computer device suitable for implementing some embodiments of the present application. DETAILED DESCRIPTION

[0013] Embodiments of the present application will be described in more detail with reference to the drawings. Although some embodiments of the present application are shown in the drawings, it should be understood that the present application can be implemented in various forms, and should not be interpreted as being limited to the embodiments set forth herein. On the contrary, these embodiments are provided so that the present application can be more thoroughly and completely understood. It should be understood that the drawings and embodiments of the present application are only for illustrative purposes, and are not intended to limit the scope of protection of the present application.

[0014] In addition, it should be further noted that only the parts related to the present application are shown in the drawings for ease of description. The embodiments in the present application and the features in the embodiments can be combined with each other without conflict.

[0015] It should be noted that the terms "first", "second", etc. mentioned in the present application are only used to distinguish different devices, modules or units, and are not intended to limit the functions performed by these devices, modules or units or the mutual dependency therebetween.

[0016] It should be noted that the adjectives "one", "multiple" mentioned in the present application are illustrative and not limiting, and those skilled in the art should understand that, unless otherwise explicitly indicated in the context, it should be understood as "one or more".

[0017] The names of the messages or information exchanged between multiple devices in the embodiments of the present application are only used for illustrative purposes and are not used to limit the scope of these messages or information.

[0018] The present application will be described in detail below with reference to the accompanying drawings and in combination with embodiments.

[0019] Figure 1 The process 100 of some embodiments of the state machine-based product page interface configuration method according to the present application is shown. The state machine-based product page interface configuration method is applied to a product page interface configuration system, which includes: a connector service system, a template processing service system, a rule engine service system, and a state machine service system, and includes the following steps:

[0020] Step 101: The connector service system determines connector configuration information in response to receiving an upstream service identifier sent by a management terminal, and stores the connector configuration information in a server.

[0021] In some embodiments, the connector service system determines the connector configuration information in response to receiving the upstream service identifier sent by the management terminal, and stores the connector configuration information in the server. The connector configuration information may include: an upstream interface request message and an upstream interface response message. Here, the upstream service identifier can uniquely identify an upstream service (for example, the upstream service can be an insurance service). The server can be used to store the connector configuration information. The upstream interface request message can be a request message representing at least one user information (for example, user name, user age, user attribute value (user assets), user flow attribute value (user insurance amount required)), etc.) that is desired to be obtained from the upstream service. The upstream interface response message can be a response message representing the receipt of a response request message sent by the upstream service.

[0022] Here, the product page interface configuration system can refer to Figure 2 . Figure 2 The following is a schematic diagram showing the structure of some embodiments of the product page interface configuration system according to the present application. Figure 2As mentioned above, the product page interface configuration system 200 may include a connector service system 201, a template processing service system 202, a rule engine service system 203, and a state machine service system 204. The connector service system 201 may be used to configure connector configuration information to connect to upstream services, and store the connector configuration information in a server. The template processing service system 202 may be used to obtain upstream interface request messages and upstream interface response messages from a server, configure request parameter template information and response parameter template information to perform format conversion processing on upstream interface request messages and upstream interface response messages, and store the request parameter template information and response parameter template in a server. The rule engine service system 203 may be used to configure rule set configuration information, and store the rule set configuration information in a server. The state machine service system 204 may be used to obtain connector configuration information, template configuration information, and rule set configuration information from a server, configure state machine definition configuration information, and store the state machine definition configuration information in a server.

[0023] In practice, in response to receiving the upstream service identifier sent by the management terminal, the connector service system may determine the connector configuration information through the following steps:

[0024] The first step is to determine upstream service connection information in response to receiving the upstream service identifier sent by the management terminal. In practice, in response to receiving the upstream service identifier sent by the management terminal, the connector service system may determine the preset protocol, upstream path, upstream domain name, and upstream request method as the upstream service connection information. Here, the preset protocol may be HTTP (Hypertext Transport Protocol). The upstream path may be the path of the upstream service. The upstream domain name may be the domain name of the upstream service. The upstream request method may be the GET (Query Request) method.

[0025] The second step is to configure the connector parameter information corresponding to the above-mentioned upstream service connection information. In practice, the above-mentioned connector service system can determine the connector identifier, public parameter information, and request header information as the connector parameter information corresponding to the above-mentioned upstream service connection information. Here, the connector identifier can uniquely identify a connector. The connector can be used to connect to the upstream service. The public parameter information may include but is not limited to at least one of the following: the number of connections and the connection duration. The number of connections can represent the number of upstream services that the connector has connected to. The connection duration can represent the length of time the connector is connected to the upstream service. The request header information may include but is not limited to at least one of the following: the request path and the request domain name. The request path can represent the path between the connector and the upstream service to be connected. The request domain name can represent the domain name of the connector and the upstream service to be connected.

[0026] The third step is to perform binding processing on the upstream service connection information and the connector parameter information to generate connector binding information. In practice, in response to determining that the upstream service connection information and the connector parameter information meet the preset binding conditions, the connector service system can determine the upstream service connection information and the connector parameter information as connector binding information. Here, the preset binding conditions can be: the upstream path and upstream domain name included in the upstream service connection information are the same as the request path and request domain name included in the request header information included in the upstream connector parameter information, and the number of connections included in the public parameter information included in the upstream connector parameter information is less than or equal to the preset number of connections. For example, the preset number of connections can be 5.

[0027] The fourth step is to encrypt the above connector binding information to generate connector configuration information.

[0028] In practice, the connector service system may encrypt the connector binding information to generate connector configuration information through the following steps:

[0029] The first step is to determine a first prime number and a second prime number. In practice, the connector service system may randomly determine the first prime number and the second prime number. The first prime number and the second prime number may be unequal prime numbers.

[0030] In the second step, the product of the first prime number and the second prime number is determined as the modulus.

[0031] The third step is to determine the Euler parameter based on the first prime number and the second prime number. In practice, the connector service system can determine the Euler parameter by the following steps: first, determining the difference between the first prime number and a preset value as the first prime number difference. Second, determining the difference between the second prime number and the preset value as the second prime number difference. Then, determining the product of the first prime number difference and the second prime number difference as the Euler parameter. For example, the preset value can be 1.

[0032] In the fourth step, a first public key is determined based on the Euler parameter. In practice, in response to determining that the first public key is coprime with the Euler parameter and the first public key is smaller than the Euler parameter, the connector service system may randomly generate the first public key.

[0033] Step 5: Based on the first public key and the modulus, the connector binding information is encrypted first to generate first connector encrypted information. In practice, the connector service system can perform the first encryption on the connector binding information to generate first connector encrypted information by following these steps: First, vectorize the connector binding information using a preset vectorization algorithm to generate a connector binding vector. Second, raise the connector binding vector to the first public key power as the initial connector encrypted information. Next, perform the modulus modulo operation on the initial connector encrypted information to obtain the remainder, which is then determined as the first connector encrypted information.

[0034] Step 6: Determine the second key. In practice, the connector service system may randomly determine the second key of a preset length. For example, the preset length may be 128 bits.

[0035] In the seventh step, padding is performed on the first connector encrypted information to generate connector padding information. In practice, the connector service system may pad the first connector encrypted information using a preset padding algorithm to generate the connector padding information. For example, the preset padding algorithm may be the PKCS7 (Public Key Message Syntax Standard) padding algorithm. The length of the connector padding information may be an integer multiple of a preset length, for example, 128 bits.

[0036] Step 8: Group the connector fill information to generate a connector group information set. In practice, the connector service system may group the connector fill information using a preset grouping algorithm to generate the connector group information set. For example, the preset grouping algorithm may be to group each piece of connector fill information of a preset length as connector group information to generate the connector group information set.

[0037] In step nine, based on the second key, a second encryption process is performed on each connector group information in the connector group information set to generate second connector encrypted information, thereby obtaining a second connector encrypted information set. In practice, the connector service system may use a preset encryption algorithm and the second key to perform a second encryption process on each connector group information in the connector group information set to generate second connector encrypted information, thereby obtaining a second connector encrypted information set. For example, the preset encryption algorithm may be the Advanced Encryption Standard (AES) algorithm.

[0038] In step 10, the second connector encrypted information in the second connector encrypted information set is concatenated to generate connector configuration information. In practice, the connector service system may concatenate the second connector encrypted information in the second connector encrypted information set in order from left to right to generate connector configuration information.

[0039] The relevant content of step 101, as an inventive feature of an embodiment of this application, addresses the following technical issue: "Reduced security of product page interface configuration." Factors that often reduce the security of product page interface configuration include: when the connector service system configures connector configuration information to connect to upstream services, directly storing the configured but unencrypted connector configuration information on the server can lead to the leakage of the connector configuration information when the server is attacked. Addressing these factors can improve the security of product page interface configuration. To achieve this, the present application first encrypts the connector binding information using a first public key determined based on a first prime number and a second prime number. This improves the security of the connector binding information. Then, a second encryption is performed on each connector group information in the connector group information set using a second key, and the second encrypted connector encrypted information set is encrypted using a key to obtain the connector configuration information. This allows the encrypted first connector encrypted information to be encrypted in blocks, further improving the security of the connector binding information. Therefore, the connector binding information can be encrypted twice using the first public key and the second key, increasing the security of the connector configuration information. This further improves the security of the product page interface configuration.

[0040] Step 102: The template processing service system obtains an upstream interface request message and an upstream interface response message from the server.

[0041] In some embodiments, the template processing service system obtains the upstream interface request message and the upstream interface response message from the server. In practice, the template processing service system may obtain the upstream interface request message and the upstream interface response message from the server via a wired connection or a wireless connection.

[0042] It should be noted that the above wireless connection methods may include but are not limited to 3G / 4G connection, WiFi connection, Bluetooth connection, WiMAX connection, Zigbee connection, UWB (ultra wideband) connection, and other wireless connection methods currently known or to be developed in the future.

[0043] At step 103, the template processing service system configures the request parameter template information based on the upstream interface request message to perform format conversion processing on the upstream interface request message.

[0044] In some embodiments, the template processing service system configures the request parameter template information based on the upstream interface request message to perform format conversion processing on the upstream interface request message.

[0045] In practice, based on the upstream interface request, the template processing service system can configure the request parameter template information by the following steps:

[0046] Firstly, the upstream interface request message is split to generate upstream interface request message header information and upstream interface request message body information. In practice, the template processing service system can split the upstream interface request message into upstream interface request message header information and upstream interface request message body information. The upstream interface request message header information can represent the message header of the upstream interface request message. The upstream interface request message body information can represent the message body of the upstream interface request message. Here, the upstream interface request message can represent the information to be obtained from the upstream service. The upstream interface request message header information can represent the path of the upstream service. The upstream interface request message body information can represent at least one user information (e.g., user name, user age, user address, etc.) to be obtained.

[0047] Secondly, the upstream interface request message body information is data-divided to generate a set of upstream interface request message division information. In practice, the template processing service system can perform data division processing on the upstream interface request message body information by a preset data division algorithm to generate a set of upstream interface request message division information. For example, the preset data division algorithm can be to determine each user information represented in the upstream interface request message body information as an upstream interface request message division information.

[0048] Thirdly, a set of upstream interface data corresponding to the set of upstream interface request message division information is obtained from a storage terminal corresponding to the upstream interface request message header information. The upstream interface data in the set of upstream interface data corresponds to the upstream interface request message division information in the set of upstream interface request message division information. Here, the storage terminal can be a terminal for storing the set of upstream interface data. The upstream interface data in the set of upstream interface data can represent the data to be obtained by the upstream interface request message division information.

[0049] In the fourth step, each upstream interface data item in the upstream interface data set is encrypted to generate upstream interface encrypted data, thereby obtaining an upstream interface encrypted data set. In practice, the specific implementation of encrypting each upstream interface data item in the upstream interface data set to generate upstream interface encrypted data, and the resulting technical effects, can be found in step 101 of the above embodiment and are not further described here.

[0050] The fifth step is to fuse the upstream interface request message partition information set and the upstream interface encrypted data set to generate an upstream interface mapping information set.

[0051] Step 6: Determine the upstream interface mapping information set as request parameter template information.

[0052] Step 104 : The template processing service system configures response parameter template information based on the upstream interface response message to perform format conversion processing on the upstream interface response message.

[0053] In some embodiments, the template processing service system configures response parameter template information based on the upstream interface response message to perform format conversion processing on the upstream interface response message. In practice, the specific implementation method of the template processing service system configuring the response parameter template information based on the upstream interface response message and the resulting technical effects can be referred to step 103 in the above embodiment and will not be repeated here.

[0054] In step 105 , the template processing service system determines the request parameter template information and the response parameter template information as template configuration information, and stores the template configuration information in the server.

[0055] In some embodiments, the template processing service system determines the request parameter template information and the response parameter template information as template configuration information, and stores the template configuration information in the server.

[0056] Step 106: The rule engine service system configures rule set configuration information, and stores the rule set configuration information in the server.

[0057] In some embodiments, the rule engine service system configures rule set configuration information and stores the rule set configuration information in the server.

[0058] In practice, the above rule engine service system can configure the rule set configuration information through the following steps:

[0059] In the first step, in response to receiving a rule definition identifier from a management terminal, a preset rule filling list is sent to the management terminal to receive the completed rule filling information from the management terminal. The rule definition identifier may represent the business rules that the management terminal intends to establish for the upstream service. The preset rule filling list may be a list of business rules to be filled in. The rule filling information may represent at least one business rule filled in by the management terminal.

[0060] The second step is to perform data cleaning on the rule filling information to generate rule cleaning information. In practice, the rule engine service system can delete the information representing the empty space from the rule filling information to obtain the rule cleaning information.

[0061] The third step is to standardize the rule-cleaned information to generate standardized rule information. In practice, the rule engine service system can standardize the rule-cleaned information using a preset standardization algorithm to generate standardized rule information. For example, the preset standardization algorithm can be a JsonPath (query language) algorithm. Thus, the preset standardization algorithm can be used to convert the rule-cleaned information representing a first data format into standardized rule information representing a second data format. For example, the first data format can be JSON (JavaScript Object Notation, a lightweight data exchange format). The second data format can be Context.

[0062] The fourth step is to classify the standardized rule information to generate a rule classification information set. In practice, the rule engine service system may classify the standardized rule information using a preset classification algorithm to generate the rule classification information set. For example, the preset classification algorithm may include: first, determining the information representing each business rule included in the standardized rule information as rule classification information to obtain a rule classification information set. Second, determining each piece of rule classification information corresponding to the same upstream rule in the rule classification information set as a rule classification information group to obtain a rule classification information set. The rule classification information in the rule classification information set may include, but is not limited to, rule categories. Rule categories may include, but are not limited to, first rule categories and second rule categories. For example, the first rule category may represent native (fields present in the standardized rule information, such as user age greater than or equal to 18). The second rule category may represent variable (fields not present in the standardized rule information, such as the ratio of a user attribute value to a user flow attribute value greater than or equal to 10). Here, each piece of rule classification information in the rule classification information set is connected. The connection relationship between each piece of rule classification information may be: the rule classification information representing the first rule category is the parent node of the rule classification information representing the second rule category.

[0063] Step 5: Construct a rule information forest based on the rule classification information set. In practice, the rule engine service system can construct a rule information forest based on the rule classification information set using a preset forest construction algorithm. For example, the preset forest construction algorithm can be: construct a rule information tree for each rule classification information set in the rule classification information set, using the rule classification information as nodes and the connections between the rule classification information as edges, to generate a rule information forest.

[0064] Step 6: Determine the above rule information forest as rule set configuration information.

[0065] Optionally, the rule engine service system may further perform the following steps:

[0066] In the first step, in response to receiving a rule update identifier from a management terminal, a preset rule update list is sent to the management terminal to receive the completed rule update information sent by the management terminal. The rule update identifier may indicate that the management terminal wishes to update the rule set configuration information. The preset rule update list may be a list of business rules to be filled in. The rule update information may indicate at least one business rule that the management terminal has filled in and wishes to update.

[0067] The second step is to perform data cleaning on the rule update information to generate target rule cleaning information. In practice, the rule engine service system can delete the information representing the null from the rule update information to obtain the target rule cleaning information.

[0068] The third step is to perform standardization processing on the target rule cleaning information to generate target rule standardized information. In practice, the rule engine service system can perform standardization processing on the target rule cleaning information using the preset standardization algorithm to generate target rule standardized information.

[0069] The fourth step is to classify the target rule standardization information to generate a target rule classification information set. In practice, the rule engine service system can classify the target rule standardization information using the preset classification algorithm to generate a target rule classification information set.

[0070] Step 5: Construct a target rule information forest based on the target rule classification information set. In practice, the rule engine service system can construct a target rule information forest based on the target rule classification information set using the preset forest construction algorithm. The target rule information forest can include at least one target rule information tree. The target rule information tree included in the target rule information forest can correspond to the rule information tree included in the rule information forest.

[0071] Step 6: Based on the target rule information forest, the rule information forest is updated. In practice, for each rule information tree included in the rule information forest, in response to determining that a target rule information tree corresponding to the rule information tree exists in the target rule information forest, the rule engine service system may update the rule information tree to the target rule information tree corresponding to the rule information tree, thereby updating the rule information forest.

[0072] In the seventh step, the updated rule information forest is determined as the rule set configuration information to update the rule set configuration information.

[0073] Step 107: The state machine service system obtains connector configuration information, template configuration information, and rule set configuration information from the server.

[0074] In some embodiments, the state machine service system obtains the connector configuration information, template configuration information, and rule set configuration information from the server. In practice, the state machine service system may obtain the connector configuration information, template configuration information, and rule set configuration information from the server via a wired connection or a wireless connection.

[0075] Step 108: The state machine service system configures state machine definition configuration information based on the connector configuration information, the template configuration information, and the rule set configuration information, and stores the state machine definition configuration information in a server.

[0076] In some embodiments, the state machine service system configures the state machine definition configuration information based on the connector configuration information, the template configuration information, and the rule set configuration information, and stores the state machine definition configuration information in a server.

[0077] In practice, based on the connector configuration information, the template configuration information, and the rule set configuration information, the state machine service system may configure the state machine definition configuration information through the following steps:

[0078] The first step is to configure the state machine information corresponding to the connector configuration information. In practice, the state machine service system can determine the state machine identifier as the state machine information corresponding to the connector configuration information. Here, the state machine identifier can uniquely identify a state machine.

[0079] The second step is to configure state machine chain relationship information corresponding to the state machine information, template configuration information, and rule set configuration information. In practice, the state machine service system may define the state machine information, template configuration information, and rule set configuration information that meet preset corresponding conditions as state machine chain relationship information. The preset corresponding condition may be that the template configuration information and the rule set configuration information correspond to the same upstream service.

[0080] The third step is to perform binding processing on the state machine information, the state machine chain relationship information, and the preset product information to generate state machine binding information. In practice, in response to determining that the state machine information, the state machine chain relationship information, and the preset product information meet the preset state machine binding conditions, the state machine service system determines the state machine information, the state machine chain relationship information, and the preset product information as state machine binding information. The preset state machine binding conditions may be: the state machine identifier included in the state machine information is the same as the state machine identifier included in the state machine chain relationship information, and the product identifier included in the state machine chain relationship information is the same as the product identifier included in the preset product information. The preset product information may include, but is not limited to, at least one of the following: product identifier, product information. The product identifier can uniquely identify a product (e.g., an insurance product). The product information may include, but is not limited to, at least one of the following: product attribute value (insurance amount), product term (insurance start time to insurance expiration time).

[0081] The fourth step is to encrypt the state machine binding information to generate the state machine definition configuration information. In practice, the specific implementation of encrypting the state machine binding information to generate the state machine definition configuration information and the technical effects thereof can be referred to step 101 in the above embodiment and will not be repeated here.

[0082] The above-described embodiments of the present application have the following beneficial effects: The state machine-based product page interface configuration method of some embodiments of the present application can save significant development costs, improve the maintainability of interface logic, reduce docking cycles, and improve production efficiency. Specifically, the reason for the high investment cost and the difficulty of subsequent maintenance and expansion is that it requires a lot of manpower and material resources to develop the access logic of each upstream system separately through hard-coding, resulting in multiple implementations of the same logic with different names. Based on this, some embodiments of the present application provide a state machine-based product page interface configuration method. First, in response to receiving an upstream service identifier sent by a management terminal, the connector service system determines connector configuration information and stores the connector configuration information on a server. The connector configuration information includes an upstream interface request message and an upstream interface response message. Thus, different upstream services can be connected through the connector service system. Second, the template processing service system obtains the upstream interface request message and the upstream interface response message from the server. Then, based on the upstream interface request message, the template processing service system configures request parameter template information to perform format conversion processing on the upstream interface request message. Then, the template processing service system configures response parameter template information based on the upstream interface response message to perform format conversion processing on the upstream interface response message. Then, the template processing service system determines the request parameter template information and the response parameter template information as template configuration information, and stores the template configuration information in the server. Thus, the template processing service system can convert the data structures of the upstream interface request message and the upstream interface response message into system-built data structures, eliminating the need for internal system maintenance and reducing external code intrusion. Then, the rule engine service system configures rule set configuration information and stores the rule set configuration information in the server. Thus, business rules can be defined in a declarative manner through the rule engine service system without modifying the core code of the application. Then, the state machine service system obtains connector configuration information, template configuration information, and rule set configuration information from the server. Finally, the state machine service system configures state machine definition configuration information based on the connector configuration information, template configuration information, and rule set configuration information, and stores the state machine definition configuration information in the server. Therefore, the state machine service system can be used to associate upstream services with connectors so that upstream services can be executed in the order of the linked list and associated with rule set configuration information to achieve automated completion of business processes.Therefore, by establishing an interface docking adaptation layer (i.e., a connector service system), the common logic in interface access can be encapsulated into components, and the calling sequence of different interfaces can be configured as a state machine. Then, when connecting to a new upstream system, it is only necessary to implement the components that do not exist in the system and configure the message template and interface call state machine according to the upstream docking requirements. This can save a lot of development costs, improve the maintainability of interface logic, shorten the docking cycle, and improve production efficiency.

[0083] This application also provides a computer device 300. Figure 3 As shown, computer device 300 includes a bus 301, a processor 302, a memory 303, and a communication interface 304. Processor 302, memory 303, and communication interface 304 communicate with each other via bus 301. Computer device 300 can be a server or a terminal device. It should be understood that this application does not limit the number of processors and memories in computer device 300.

[0084] The bus 301 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 3 The bus 301 may include a path for transmitting information between various components of the computer device 300 (eg, memory 303, processor 302, communication interface 304).

[0085] The processor 302 may include any one or more processors such as a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP), or a digital signal processor (DSP).

[0086] The memory 303 may include volatile memory, such as random access memory (RAM). The memory 303 may also include non-volatile memory, such as read-only memory (ROM), flash memory, hard disk drive (HDD), or solid state drive (SSD).

[0087] Memory 303 stores executable program code, which processor 302 executes to implement the functions of the aforementioned acquisition module, sampling module, determination module, and mixing module, thereby implementing the aforementioned state machine-based product page interface configuration method. Specifically, memory 303 stores instructions for executing the aforementioned state machine-based product page interface configuration method.

[0088] The communication interface 304 uses a transceiver module such as, but not limited to, a network interface card or a transceiver to implement communication between the computer device 300 and other devices or a communication network.

[0089] An embodiment of the present application also provides a chip, which includes a processor and a data interface. The processor reads instructions stored in a memory through the data interface to execute the above-mentioned state machine-based product page interface configuration method.

[0090] Embodiments of the present application also provide a computer-readable storage medium. This computer-readable storage medium can be any available medium capable of being stored by a computing device, or a data storage device such as a data center that contains one or more available media. This available medium can be a magnetic medium (e.g., a floppy disk, hard disk, or magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive). This computer-readable storage medium includes instructions that instruct the computing device to execute the aforementioned state machine-based product page interface configuration method.

[0091] The technical features of the above embodiments can be combined arbitrarily. In order to make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0092] The above examples are only used to illustrate the technical solutions of the present application, but not to limit the same; although the present application has been described in detail with reference to the foregoing examples, it should be understood by those of ordinary skill in the art that the technical solutions recorded in the foregoing examples can be modified, or some technical features thereof can be replaced by equivalent ones; and these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the protection scope of the technical solutions of the embodiments of the present application.

Claims

1. A state machine-based product page interface configuration method, applied to a product page interface configuration system, the product page interface configuration system comprising: Connector service system, template processing service system, rule engine service system, and state machine service system, including: The connector service system determines connector configuration information in response to receiving the upstream service identifier sent by the management terminal, and stores the connector configuration information in the server, wherein the connector configuration information includes: an upstream interface request message and an upstream interface response message; The template processing service system obtains an upstream interface request message and an upstream interface response message from the server; The template processing service system configures request parameter template information based on the upstream interface request message to perform format conversion processing on the upstream interface request message; The template processing service system configures response parameter template information based on the upstream interface response message to perform format conversion processing on the upstream interface response message; The template processing service system determines the request parameter template information and the response parameter template information as template configuration information, and stores the template configuration information in the server; The rule engine service system configures rule set configuration information, and stores the rule set configuration information in the server; The state machine service system obtains connector configuration information, template configuration information and rule set configuration information from the server; The state machine service system configures state machine definition configuration information based on the connector configuration information, the template configuration information and the rule set configuration information, and stores the state machine definition configuration information in a server; The configuring of the request parameter template information based on the upstream interface request message includes: Splitting the upstream interface request message to generate upstream interface request message header information and upstream interface request message body information; Performing data segmentation processing on the upstream interface request message body information to generate an upstream interface request message segmentation information set; Acquiring an upstream interface data set corresponding to the upstream interface request message classification information set from a storage terminal corresponding to the upstream interface request message header information, wherein the upstream interface data in the upstream interface data set corresponds to the upstream interface request message classification information in the upstream interface request message classification information set; Encrypting each upstream interface data in the upstream interface data set to generate upstream interface encrypted data, thereby obtaining an upstream interface encrypted data set; fusing the upstream interface request message division information set and the upstream interface encryption data set to generate an upstream interface mapping information set; The upstream interface mapping information set is determined as request parameter template information.

2. The method for configuring a product page interface based on a state machine according to claim 1, wherein: The determining the connector configuration information in response to receiving the upstream service identifier sent by the management terminal includes: In response to receiving the upstream service identifier sent by the management terminal, determining upstream service connection information; Configuring connector parameter information corresponding to the upstream service connection information; Performing binding processing on the upstream service connection information and the connector parameter information to generate connector binding information; The connector binding information is encrypted to generate connector configuration information.

3. The product page interface configuration method based on a state machine according to claim 1, wherein: The configuring state machine definition configuration information based on the connector configuration information, the template configuration information, and the rule set configuration information includes: Configuring state machine information corresponding to the connector configuration information; Configuring state machine chain relationship information corresponding to the state machine information, the template configuration information, and the rule set configuration information; Binding the state machine information, the state machine chain relationship information, and the preset product information to generate state machine binding information; The state machine binding information is encrypted to generate state machine definition configuration information.

4. The method for configuring a product page interface based on a state machine according to claim 1, wherein: The configuration rule set configuration information includes: In response to receiving the rule definition identifier sent by the management terminal, sending the preset rule filling list to the management terminal, so as to receive the filled rule filling information sent by the management terminal; Performing data cleaning on the rule filling information to generate rule cleaning information; performing standardization processing on the rule cleaning information to generate rule standardization information; Classifying the rule standardization information to generate a rule classification information set; constructing a rule information forest based on the rule classification information set; The rule information forest is determined as rule set configuration information.

5. A computer device, wherein: The computer device comprises a processor, a memory, and a computer program stored in the memory and executable by the processor, wherein when the computer program is executed by the processor, the steps of the method according to any one of claims 1 to 4 are implemented.

6. A computer-readable storage medium, wherein: The computer-readable storage medium stores a computer program, wherein when the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 4 are implemented.

Images