State Machine-Based Product Page Push Method and Computer Device

Abstract

Embodiments of the present application relate to the field of page push, and specifically to a product page push method and a computer device based on a state machine. A specific implementation of the method includes: obtaining product production process information and product page configuration information; configuring a product page editing model; performing disassembling processing to obtain a sequence of process status information; determining a sequence of process state machine element information; storing the sequence of process state machine element information in a product server; in response to receiving product page viewing request information sent by a user terminal, obtaining, from the product server, process state machine element information corresponding to the product page viewing request information as the to-be-pushed state machine element information; rendering the to-be-pushed state machine element information based on the product page editing model to generate product push page information, and sending the product push page information to the user terminal. This implementation improves the relevance of product pages of related products and improves the user experience.

Description

Technical Field

[0001] Embodiments of the present application relate to the field of page pushing, and specifically to a method for pushing product pages based on a state machine and a computer device. Background Art

[0002] In various Internet pushing methods related to insurance business, it is necessary to provide users with online insurance application pages. Due to the large number of insurance product categories, different inspection scales for products with different characteristics, and differences in pushing methods, there are significant differences in aspects such as insurance application steps, data filling, and information uploading. Currently, when pushing product pages, the commonly used method is to separately develop corresponding product page elements and product production (insurance application) steps for each product to generate product pages.

[0003] However, in practice, it is found that when pushing product pages in the above manner, the following technical problems often exist:

[0004] For the method of separately developing product page elements for each product, due to the large workload, multiple control terminals (central processing units) may need to be developed simultaneously, and the generated product pages are difficult to maintain uniformity, resulting in a reduction in the relevance of product pages of related products, and further reducing the user experience. Summary of the Invention

[0005] This section of the present application is used to briefly introduce concepts, which will be described in detail in the following detailed implementation section. This section of the present application is not intended to identify the key features or essential features of the claimed technical solution, nor is it intended to limit the scope of the claimed technical solution.

[0006] Some embodiments of the present application propose a method for pushing product pages based on a state machine, a computer device, and a computer-readable storage medium to solve one or more of the technical problems mentioned in the above background art section.

[0007] In a first aspect, some embodiments of the present application provide a method for pushing product pages based on a state machine. The method includes: obtaining product production process information and product page configuration information from an associated product server; configuring a product page editing model based on the above product page configuration information; performing a process state decomposition process on the above product production process information to obtain a sequence of process state information; determining, based on the above product page configuration information, process state machine element information corresponding to each piece of process state information in the above sequence of process state information to obtain a sequence of process state machine element information; storing the above sequence of process state machine element information in the above product server; in response to receiving product page viewing request information sent by a user terminal, obtaining, from the above product server, process state machine element information corresponding to the above product page viewing request information as the to-be-pushed state machine element information; rendering the above to-be-pushed state machine element information based on the above product page editing model to generate product push page information, and sending the above product push page information to the above user terminal.

[0008] In a second aspect, the present application further provides a computer device. The above computer device includes a processor, a memory, and a computer program stored on the above memory and executable by the above processor. When the above computer program is executed by the above processor, the method described in any implementation manner of the above first aspect is implemented.

[0009] In a third aspect, the present application further provides a computer-readable storage medium. A computer program is stored on the above computer-readable storage medium. When the above computer program is executed by a processor, the method described in any implementation manner of the above first aspect is implemented.

[0010] The above embodiments of the present application have the following beneficial effects: Through the state machine-based product page push method of some embodiments of the present application, the relevance of product pages of related products can be improved, and thus, the user experience is enhanced. Specifically, the reason for the reduced user experience is as follows: When developing product page elements for each product individually, due to the large workload, multiple control terminals (central processing units) may need to develop simultaneously, and the generated product pages are difficult to maintain uniformity, resulting in a decrease in the relevance of product pages of related products. Based on this, in the state machine-based product page push method of some embodiments of the present application, first, product production process information and product page configuration information are obtained from the related product server. Secondly, based on the above product page configuration information, a product page editing model is configured. In this way, a page editing model can be configured according to the unified product page configuration information to generate related product pages. Then, the process state of the above product production process information is disassembled to obtain a sequence of process state information. In this way, the action information and state information of each step of the product production process (insurance application process) can be obtained. Then, based on the above product page configuration information, the process state machine element information corresponding to each process state information in the above sequence of process state information is determined to obtain a sequence of process state machine element information. In this way, the product production process can be converted into a state machine to generate product pages. Next, the above sequence of process state machine element information is stored in the above product server. In this way, the generated state machine model can be stored in the server. Subsequently, in response to receiving the product page viewing request information sent by the user terminal, the process state machine element information corresponding to the above product page viewing request information is obtained from the above product server as the to-be-pushed state machine element information. In this way, the product generation steps that the user wants to view and operate can be selected. Finally, based on the above product page editing model, the above to-be-pushed state machine element information is rendered to generate product push page information, and the above product push page information is sent to the above user terminal. In this way, the product page information that the user wants to view and operate can be obtained. Therefore, some of the state machine-based product page push methods of the present application can disassemble the state of the product production process to obtain the state machine model corresponding to the product production process, and then, by using unified page components, render each action and state in the state machine model to obtain the final product push page for sending to the user terminal. In this way, a single control terminal can be used to develop multiple product pages, improving the relevance of the product pages, and thus, enhancing the user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] In combination with the accompanying drawings and with reference to the following specific embodiments, the above and other features, advantages and aspects of the embodiments of the present application will become more apparent. Throughout the drawings, the same or similar reference numerals denote the same or similar elements. It should be understood that the drawings are schematic and the elements and elements are not necessarily drawn to scale.

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

[0013] Figure 2 is a schematic diagram of a product page of some embodiments of a state machine-based product page push method according to the present application;

[0014] Figure 3 is a schematic structural diagram of a computer device suitable for implementing some embodiments of the present application. Specific Embodiments

[0015] The embodiments of the present application will be described in more detail below with reference to the accompanying 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 construed as limited to the embodiments set forth herein. On the contrary, these embodiments are provided to more thoroughly and completely understand the present application. It should be understood that the drawings and embodiments of the present application are only for exemplary purposes and are not used to limit the protection scope of the present application.

[0016] In addition, it should be noted that for the sake of convenience of description, only parts related to the relevant invention are shown in the drawings. Without conflict, the embodiments in the present application and the features in the embodiments can be combined with each other.

[0017] It should be noted that the concepts such as "first" and "second" mentioned in the present application are only used to distinguish different devices, modules or units, and are not used to limit the order of the functions executed by these devices, modules or units or the interdependent relationship.

[0018] It should be noted that the modifications of "one" and "multiple" mentioned in the present application are illustrative rather than restrictive. Those skilled in the art should understand that unless otherwise clearly specified in the context, it should be understood as "one or more".

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

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

[0021] Figure 1Flow 100 of some embodiments of the state machine-based product page push method according to the present application is shown. The state machine-based product page push method includes the following steps:

[0022] Step 101, obtain product production process information and product page configuration information from an associated product server.

[0023] In some embodiments, the execution subject of the state machine-based product page push method can obtain product production process information and product page configuration information from an associated product server in a wired connection or wireless connection manner. Among them, the above product server can be a server for storing product production process information and product page configuration information. The above product production process information can characterize the production process of a product. The above product page configuration information can include, but is not limited to, a page display component information set. The page display component information in the above page display component information set can include, but is not limited to, page components and page actions.

[0024] As an example, the above product can be an insurance business. The production process of the above product can be an insurance application process. The above insurance application process can include, but is not limited to, at least one of the following: selecting a product, filling in the basic information of the applicant (name, ID number, contact information), filling in the basic information of the insured, confirming information, making a payment, and generating a policy. The above page components can be, but are not limited to, at least one of the following: main menu, navigation bar, tab page, pagination button, drop-down menu, login account, select product, fill in basic information. The above page actions can be, but are not limited to, at least one of the following: "fill in", "select", "confirm". Specifically, the product page can refer to Figure 2 The schematic diagram of a product page shown in some embodiments of the state machine-based product page push method according to the present application. Figure 2 A product page 200 is shown. The above product page 200 can include: a page component 201 representing the "main menu", a page component 202 representing the "login account", a page component 203 representing the "select product", and a page component 204 representing the "fill in basic information".

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

[0026] Step 102, configure a product page editing model based on the product page configuration information.

[0027] In some embodiments, the above-mentioned execution entity may configure a product page editing model based on the above-mentioned product page configuration information. Among them, the above-mentioned product page configuration information may be input into the product page editing model, and the configured product page editing model is determined as the above-mentioned configured product page editing model. Here, the above-mentioned product page editing model may be an unconfigured page editor for generating product push page information.

[0028] Step 103: Perform a process status decomposition process on the product production process information to obtain a sequence of process status information.

[0029] In some embodiments, the above-mentioned execution entity may perform a process status decomposition process on the above-mentioned product production process information to obtain a sequence of process status information. Among them, the above-mentioned product production process information may be input into a process action recognition model to obtain a sequence of process status information. Here, each process status information in the above-mentioned sequence of process status information may be sorted in the order of action execution. Specifically, the above-mentioned process action recognition model may be a neural network model for recognizing verbs in the above-mentioned product production process information. The process status information in the above-mentioned sequence of process status information may include, but is not limited to: process action information and process event information. The above-mentioned process action information may represent an action. The above-mentioned process event information may represent the current event status of the process.

[0030] As an example, the above-mentioned process action recognition model may be, but is not limited to, at least one of the following: GPT (Generative Pre-Trained Transformer) model and BERT (Bidirectional Encoder Representations from Transformers) model. The above-mentioned process action information may be, but is not limited to, at least one of the following: information representing "select", information representing "fill in", information representing "confirm". The above-mentioned process event information may be, but is not limited to, at least one of the following: information representing "waiting to select a product", information representing "waiting to fill in basic information", or information representing "waiting to confirm information".

[0031] Step 104: Based on the product page configuration information, determine the process state machine element information corresponding to each process status information in the sequence of process status information to obtain a sequence of process state machine element information.

[0032] In some embodiments, the above-mentioned execution entity may determine the process state machine element information corresponding to each process status information in the above-mentioned sequence of process status information based on the above-mentioned product page configuration information to obtain a sequence of process state machine element information.

[0033] In some alternative implementations of some embodiments, the above-mentioned execution entity determines the process state machine element information corresponding to each process state information in the above-mentioned process state information sequence based on the above-mentioned product page configuration information, which may include the following steps:

[0034] First, perform state machine action configuration processing on the above-mentioned process state information to obtain process state machine action information. Among them, performing state machine action configuration processing on the above-mentioned process state information to obtain process state machine action information may be: First, generate a process state diagram corresponding to the above-mentioned process state information through a preset state diagram generation algorithm. Then, the above-mentioned process state diagram can be input into an initial state machine model to obtain the above-mentioned process state machine action information.

[0035] As an example, the above-mentioned preset state diagram generation algorithm may be, but is not limited to, at least one of the following: Graphviz (drawing tool) algorithm or StateChart (state chart) algorithm. The above-mentioned initial state machine model may be, but is not limited to, at least one of the following: FSM (Finite State Machine) model or HSM (Hierarchical State Machine) model.

[0036] Second, for each page display component information in the page display component information set included in the above-mentioned product page configuration information, perform component matching processing on the above-mentioned page display component information and the above-mentioned process state information to generate a component matching result. Among them, performing component matching processing on the above-mentioned page display component information and the above-mentioned process state information to generate a component matching result may be: In response to determining that the action information represented by the above-mentioned page display component information is the same as the action information represented by the above-mentioned process state information, determine the first preset matching information as the component matching result. In response to determining that the action information represented by the above-mentioned page display component information is different from the action information represented by the above-mentioned process state information, determine the second preset matching information as the component matching result.

[0037] As an example, the above-mentioned first preset matching information may be information representing "matching success". The above-mentioned second preset matching information may be information representing "matching failure".

[0038] Third, determine the component matching results that meet the preset component matching conditions and the corresponding page display component information among the generated component matching results as the target page display component information to obtain a target page display component information set. Among them, the above-mentioned preset component matching condition may be: the above-mentioned component matching result is information representing "matching success".

[0039] Step 4: Determine the input numerical range information corresponding to each piece of target page display component information in the above target page display component information set to obtain an input numerical range information set. Among them, for each piece of target page display component information in the above target page display component information set, a preset numerical range can be determined as the corresponding input numerical range information.

[0040] As an example, when the above target page display component information is a page component representing "input age", the preset numerical range can be (0, 70). When the above target page display component information is a page component representing "input contact information", the preset numerical range can be (9999999999, 19999999999).

[0041] Step 5: Perform a fusion process on the above process state machine action information, the above target page display component information set, and the above input numerical range information set to obtain the above process state machine element information. Among them, the above fusion process on the above process state machine action information, the above target page display component information set, and the above input numerical range information set to obtain the above process state machine element information can be: determining the above process state machine action information, the target page display component information set, and the input numerical range information set as the process state machine action information, target page display component information set, and input numerical range information set included in the above process state machine element information.

[0042] Step 105: Store the process state machine element information sequence in the product server.

[0043] In some embodiments, the above execution subject can store the above process state machine element information sequence in the above product server.

[0044] Step 106: In response to receiving the product page viewing request information sent by the user terminal, obtain the process state machine element information corresponding to the product page viewing request information from the product server as the to-be-pushed state machine element information.

[0045] In some embodiments, the above execution subject can, in response to receiving the product page viewing request information sent by the user terminal, obtain the process state machine element information corresponding to the above product page viewing request information from the above product server as the to-be-pushed state machine element information. Among them, the above product page viewing request information can include, but is not limited to: a product page viewing identifier and product page viewing action information. The above product page viewing identifier can represent that the above user terminal wants to view a product page. The above product page viewing action information can represent a product page execution action.

[0046] As an example, the above product page execution actions may be, but are not limited to, at least one of the following: "view insurance category", "select insurance category", or "fill in applicant information".

[0047] In some optional implementation manners of some embodiments, in response to receiving the product page viewing request information sent by the user terminal, the above execution entity obtains, from the above product server, the process state machine element information corresponding to the above product page viewing request information as the to-be-pushed state machine element information, which may include the following steps:

[0048] First step, based on the above product page viewing request information, generate page identification request information, and send the page identification request information to the storage terminal. Among them, the preset page request information may be determined as the page identification request information. The above preset request information may indicate that the above execution entity wants to determine that there is a page viewing identifier stored in the above storage terminal. The above page viewing identifier may indicate that the above user terminal has viewed the product page before the current moment.

[0049] Second step, in response to receiving the page viewing identifier sent by the above storage terminal, generate the product page request information corresponding to the page viewing identifier, and send the above product page request information to the product server. Among them, the preset session request information may be determined as the above product page request information. The above preset session request information may indicate that the above execution entity wants to conduct a session with the above product server.

[0050] Third step, in response to receiving the session identifier information sent by the above product server, obtain, from the above product server, the process state machine element information corresponding to the above product page request information as the to-be-pushed state machine element information. Among them, in response to receiving the session identifier information sent by the above product server, the process state machine element information in the above process state machine element information sequence that is the same as the process state machine element information characterized by the product page execution action information included in the above product page request information may be determined as the to-be-pushed state machine element information.

[0051] Optionally, the above execution entity may also perform the following steps:

[0052] First step, in response to determining that the page viewing identifier sent by the above storage terminal has not been received within a preset duration, send the preset initial session request information to the above product server, and receive the page viewing identifier from the above product server. Among them, the above preset initial session request information may be information indicating "wanting to establish a session with the product server".

[0053] As an example, the above preset duration may be, but is not limited to, at least one of the following: 10 milliseconds, 15 milliseconds, or 30 milliseconds.

[0054] In the second step, store the page view identifier in the above storage terminal.

[0055] Thereby, the above execution entity can establish a communication connection with the above product server for subsequent rendering and pushing of the page.

[0056] Step 107: Based on the product page editing model, perform rendering processing on the state machine element information to be pushed to generate product push page information, and send the product push page information to the above user terminal.

[0057] In some embodiments, the above execution entity can perform rendering processing on the state machine element information to be pushed based on the above product page editing model to generate product push page information, and send the product push page information to the above user terminal.

[0058] In some optional implementation manners of some embodiments, the above execution entity performing rendering processing on the state machine element information to be pushed based on the above product page editing model to generate product push page information may include the following steps:

[0059] In the first step, input the state machine element information to be pushed into the above product page editing model to obtain target product page information.

[0060] In the second step, send the above target product page information to the detection terminal, and read the page detection result corresponding to the above target product page information from the above detection terminal. Wherein, the above detection terminal may be a terminal for performing detection processing on the above target product page information to generate a page detection result. The above page detection result may be information indicating "detection passed" or information indicating "detection failed". Thereby, the product page can be further optimized by means of pre-detection and preview, and thus, the user experience can be further improved.

[0061] In the third step, in response to determining that the above page detection result meets a preset detection condition, determine the target product page information as the product push page information. Wherein, the above preset detection condition may be that the above page detection result is information indicating "detection passed".

[0062] Considering the problems of conventional solutions, in the face of the following technical problems: the information input on the page may contain sensitive information, and the security of a single desensitization method (for example, character replacement) is relatively low, which is likely to lead to the leakage of users' basic information, thereby reducing the security of page pushing and use. Combining the existing technical situation, the following solution can be determined.

[0063] Optionally, the above execution entity may also perform the following steps:

[0064] First step, in response to receiving the product page input information sent by the above user terminal, desensitize the above product page input information to obtain user desensitized information. Among them, the above product page input information can represent the information input by the user terminal.

[0065] As an example, the above user desensitized information may include, but is not limited to, at least one of the following: user age value and user contact information value.

[0066] Second step, perform input verification processing on the above user desensitized information to obtain an input verification result. Among them, the above input verification result can be information representing "verification passed" or information representing "verification failed".

[0067] As an example, performing the above input verification processing on the above user desensitized information to obtain an input verification result may include the following sub-steps:

[0068] The first sub-step is to determine the input numerical range information corresponding to the user age value included in the above user desensitized information from the input numerical range information set included in the product push page information as the first target numerical range information. Here, the input numerical range information in the above input numerical range information set, whose corresponding target page display component information is the page component representing "input age", can be determined as the above first target numerical range.

[0069] The second sub-step is to, in response to determining that the user age value included in the above user desensitized information is within the above first target numerical range, determine the first preset verification result as the first verification result. Here, the first preset verification result can be information representing "verification passed".

[0070] The third sub-step is to, in response to determining that the user age value included in the above user desensitized information is not within the above first target numerical range, determine the second preset verification result as the first verification result. Here, the second preset verification result can be information representing "verification failed".

[0071] The fourth sub-step is to determine the input numerical range information corresponding to the user contact information value included in the above user desensitized information from the input numerical range information set included in the product push page information as the second target numerical range information. Here, the input numerical range information in the above input numerical range information set, whose corresponding target page display component information is the page component representing "input contact information", can be determined as the above second target numerical range.

[0072] The fifth sub-step is to, in response to determining that the user contact information value included in the above user desensitized information is within the above second target numerical range, determine the first preset verification result as the second verification result.

[0073] The sixth sub-step, in response to determining that the user contact information value included in the above user desensitized information is not within the above second target numerical range, determines the second preset test result as the second test result.

[0074] The seventh sub-step, in response to determining that the above first test result meets the first preset input test condition and the above second test result meets the second preset input test condition, determines the first preset test result as the input test result. Among them, the above first preset test condition may be that the above first test result is information indicating "test passed". The above second preset test condition may be that the above second test result is information indicating "test passed".

[0075] The eighth sub-step, in response to determining that the above first test result does not meet the first preset input test condition or the above second test result does not meet the second preset input test condition, determines the second preset test result as the input test result.

[0076] The third step, in response to determining that the above input test result meets the preset test condition, sends the above user desensitized information to the product server and receives input feedback result information from the above product server. Among them, the above preset test condition may be that the above input test result is information indicating "test passed". The above input feedback result information may characterize the event status of the updated process of the above product server.

[0077] The fourth step, sends the above input feedback result information to the above user terminal. Thus, the user terminal can perform the next product production operation according to the updated event status.

[0078] In some optional implementation manners of some embodiments, the above execution subject performs desensitization processing on the above product page input information to obtain user desensitized information, which may include the following steps:

[0079] The first step, obtains desensitization rule information and a sensitive information sequence from the above product server. Among them, the above desensitization rule information may include at least one of the following: a first desensitization condition, a second desensitization condition, and a third desensitization condition. Each sensitive information in the above sensitive information sequence may characterize a type of sensitive information.

[0080] As an example, the above sensitive information may be at least one of the following: information indicating "user name" or information indicating "user ID number".

[0081] As an example, the above first desensitization condition may be: there is duplicate information among the various sensitive information. The above second desensitization condition may be: the sensitive information is information indicating the user ID number. The above third desensitization condition may be that the sensitive information is information indicating the user contact information.

[0082] In the second step, copy the input information of the above product page to obtain the copied information of the page input. Among them, the copied information after copying the input information of the above product page can be determined as the copied information of the page input.

[0083] In the third step, perform sensitive matching processing on the above copied information of the page input and the above sensitive information sequence to obtain a sequence of page sensitive matching information.

[0084] In the fourth step, based on the above desensitization rule information, perform desensitization processing on the above sequence of page sensitive matching information to obtain a sequence of page desensitized information.

[0085] In the fifth step, perform fusion processing on the above sequence of page desensitized information and the above input information of the product page to obtain user desensitized information. Among them, the above fusion processing of the above sequence of page desensitized information and the above input information of the product page to obtain user desensitized information can be: determining the above sequence of page desensitized information and the above input information of the product page as the sequence of page desensitized information and the input information of the product page included in the user desensitized information.

[0086] In some optional implementation manners of some embodiments, the above execution subject performs sensitive matching processing on the above copied information of the page input and the above sensitive information sequence to obtain a sequence of page sensitive matching information, which may include the following steps:

[0087] In the first step, perform segmentation processing on the above copied information of the page input to obtain a set of segmented information of the input copy. Among them, the above copied information of the page input can be segmented through a preset segmentation algorithm to obtain a set of segmented information of the input copy.

[0088] As an example, the above preset segmentation algorithm may be but is not limited to at least one of the following: BERT model algorithm or BiLSTM (Bidirectional Long Short-Term Memory) model algorithm.

[0089] In the second step, for each piece of segmented information of the input copy in the above set of segmented information of the input copy, perform the following sub-steps of segmented matching:

[0090] In the first sub-step, determine the similarity value between the above segmented information of the input copy and each piece of sensitive information in the above sensitive information sequence to obtain a group of sensitive information similarity values. Among them, the similarity value between the above segmented information of the input copy and each piece of sensitive information in the above sensitive information sequence can be determined through a preset similarity algorithm.

[0091] As an example, the above preset similarity algorithm may be but is not limited to at least one of the following: Pearson correlation coefficient algorithm or cosine similarity algorithm.

[0092] In the second sub-step, in response to determining that there is a sensitive information similarity value greater than a preset similarity value in the above-mentioned group of sensitive information similarity values, the above-mentioned input copy segmented information is determined as page-sensitive matching information.

[0093] As an example, the above-mentioned preset similarity value can be 0.8.

[0094] In the third step, each of the determined page-sensitive matching information is determined as a page-sensitive matching information sequence.

[0095] In some optional implementation manners of some embodiments, the above-mentioned execution subject performs a desensitization process on the above-mentioned page-sensitive matching information sequence based on the above-mentioned desensitization rule information to obtain a page desensitized information sequence, which may include the following steps:

[0096] In the first step, each page-sensitive matching information in the page-sensitive matching information sequence that satisfies the first desensitization condition included in the above-mentioned desensitization rule information is deleted from the page-sensitive matching information sequence to obtain a first desensitized information sequence.

[0097] In the second step, in response to determining that there is no page-sensitive matching information in the page-sensitive matching information sequence that satisfies the first desensitization condition included in the above-mentioned desensitization rule information, the page-sensitive matching information sequence is determined as the first desensitized information sequence.

[0098] In the third step, character replacement processing is performed on each first desensitized information in the first desensitized information sequence that satisfies the second desensitization condition included in the above-mentioned desensitization rule information to update the first desensitized information sequence, thereby obtaining a second desensitized information sequence. Among them, the above-mentioned character replacement processing performed on each first desensitized information in the first desensitized information sequence that satisfies the second desensitization condition included in the above-mentioned desensitization rule information may be replacing the first desensitized information with a preset character.

[0099] As an example, the above-mentioned preset character may be, but is not limited to, at least one of the following: "0", "#", or "*".

[0100] In the fourth step, in response to determining that there is no first desensitized information in the first desensitized information sequence that satisfies the second desensitization condition included in the above-mentioned desensitization rule information, the first desensitized information sequence is determined as the second desensitized information sequence.

[0101] In the fifth step, encryption processing is performed on each second desensitized information in the second desensitized information sequence that satisfies the third desensitization condition included in the above-mentioned desensitization rule information to update the second page desensitized information sequence, thereby obtaining a page desensitized information sequence. Among them, the encryption processing can be performed on each second desensitized information in the second desensitized information sequence that satisfies the third desensitization condition included in the above-mentioned desensitization rule information through a preset encryption algorithm.

[0102] As an example, the above preset encryption algorithm may be, but is not limited to, at least one of the following: RSA (Rivest-Shamir-Adleman) algorithm or AES (Advanced Encryption Standard) algorithm.

[0103] In the sixth step, in response to determining that there is no second desensitized information in the second desensitized information sequence that satisfies the third desensitized condition included in the above desensitized rule information, the second desensitized information sequence is determined as the page desensitized information sequence.

[0104] Thus, the collected user information can be segmented, the sensitive information in the user information can be identified, and different desensitization processes can be performed for different categories of sensitive information, while reducing the consumption of computing resources and improving the privacy of user information, thereby improving the security of page push and use.

[0105] The above-mentioned embodiments of the present application have the following beneficial effects: through the product page push method based on the state machine of some embodiments of the present application, the relevance of the product pages of the associated products can be improved, thereby improving the user experience. Specifically, the reason for the reduction in user experience is that the way of developing product page elements for each product separately may require multiple control terminals (central processing units) to develop simultaneously due to the large workload, and the generated product pages are difficult to maintain uniformity, resulting in a reduction in the relevance of the product pages of the associated products. Based on this, the product page push method based on the state machine of some embodiments of the present application first obtains product production process information and product page configuration information from the associated product server. Secondly, based on the above-mentioned product page configuration information, the product page editing model is configured. Thus, the page editing model can be configured according to the unified product page configuration information to generate the associated product page. Then, the process state disassembly processing of the above-mentioned product production process information is performed to obtain a process state information sequence. Thus, the action information and state information of each step of the product production process (insurance process) can be obtained. Then, based on the above-mentioned product page configuration information, the process state machine element information corresponding to each process state information in the above-mentioned process state information sequence is determined to obtain the process state machine element information sequence. Thus, the product production process can be converted into a state machine to generate a product page. Then, the above process state machine element information sequence is stored in the above product server. Thus, the generated state machine model can be stored in the server. Subsequently, in response to receiving the product page viewing request information sent by the user terminal, the process state machine element information corresponding to the above product page viewing request information is obtained from the above product server as the state machine element information to be pushed. Thus, the product generation step that the user wants to view and operate can be selected. Finally, based on the above product page editing model, the above state machine element information to be pushed is rendered to generate product push page information, and the above product push page information is sent to the above user terminal. Thus, the product page information that the user wants to view and operate can be obtained. Therefore, some state machine-based product page push methods of the present application can obtain the state machine model corresponding to the product production process by disassembling the state of the product production process, and then, by using a unified page component, each action and state in the state machine model is rendered to obtain the final product push page for sending to the user terminal. Thus, a single control terminal can be used to develop multiple product pages, which improves the relevance of the product pages, thereby improving the user experience.

[0106] The present application also provides a computer device 300. Figure 3As shown in the figure, the computer device 300 includes: a bus 301, a processor 302, a memory 303, and a communication interface 304. The processor 302, the memory 303, and the communication interface 304 communicate with each other through the bus 301. The computer device 300 can be a server or a terminal device. It should be understood that the number of processors and memories in the computer device 300 is not limited in this application.

[0107] The bus 301 can be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The bus can be divided into an address bus, a data bus, a control bus, etc. For the sake of convenience of representation, Figure 3 only one line is shown in the figure, but it does not mean that there is only one bus or one type of bus. The bus 301 can include a path for transmitting information between various components of the computer device 300 (for example, the memory 303, the processor 302, and the communication interface 304).

[0108] The processor 302 can include any one or more of a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP), or a digital signal processor (DSP).

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

[0110] The memory 303 stores executable program code, and the processor 302 executes the executable program code to implement the functions of the foregoing acquisition module, sampling module, determination module, and mixing module respectively, so as to implement the above-mentioned product page push method based on a state machine. That is, the memory 303 stores instructions for executing the above-mentioned product page push method based on a state machine.

[0111] 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 communication networks.

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

[0113] An embodiment of the present application also provides a computer-readable storage medium. The above-mentioned computer-readable storage medium can be any available medium that a computing device can store or a data storage device such as a data center that includes one or more available media. The above-mentioned available media can be magnetic media (for example, floppy disks, hard disks, magnetic tapes), optical media (for example, DVDs), or semiconductor media (for example, solid-state drives), etc. The computer-readable storage medium includes instructions that direct the computing device to execute the above-mentioned product page push method based on a state machine.

[0114] The technical features of the above-mentioned embodiments can be combined arbitrarily. For the sake of brevity of description, not all possible combinations of the technical features in the above-mentioned embodiments are described. However, as long as there is no contradiction in the combination of these technical features, it should be considered to be within the scope described in this specification.

[0115] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them; although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that they can still modify the technical solutions described in the foregoing embodiments, or perform equivalent replacements on some of the technical features; 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 product page push method based on a state machine, comprising: Obtaining product production process information and product page configuration information from an associated product server, wherein the product page configuration information includes: a set of page display component information; Configuring a product page editing model based on the product page configuration information; Performing a process state decomposition process on the product production process information to obtain a process state information sequence; Determining, based on the product page configuration information, the process state machine element information corresponding to each process state information in the process state information sequence to obtain a process state machine element information sequence; Storing the process state machine element information sequence in the product server; In response to receiving product page viewing request information sent by a user terminal, obtaining, from the product server, the process state machine element information corresponding to the product page viewing request information as the to-be-pushed state machine element information; Rendering the to-be-pushed state machine element information based on the product page editing model to generate product push page information, and sending the product push page information to the user terminal; In response to receiving product page input information sent by the user terminal, performing desensitization processing on the product page input information to obtain user desensitized information; Performing input verification processing on the user desensitized information to obtain an input verification result; In response to determining that the input verification result meets a preset verification condition, sending the user desensitized information to the product server, and receiving input feedback result information from the product server; Sending the input feedback result information to the user terminal; Wherein, the determining, based on the product page configuration information, the process state machine element information corresponding to each process state information in the process state information sequence includes: Performing state machine action configuration processing on the process state information to obtain process state machine action information; For each page display component information in the set of page display component information included in the product page configuration information, performing component matching processing on the page display component information and the process state information to generate a component matching result; Determining, as target page display component information, the component matching results that meet a preset component matching condition among the generated component matching results and the corresponding page display component information, to obtain a set of target page display component information; Determining the input numerical range information corresponding to each target page display component information in the set of target page display component information to obtain a set of input numerical range information; Performing fusion processing on the process state machine action information, the set of target page display component information, and the set of input numerical range information to obtain the process state machine element information.

2. The method for pushing product pages based on a state machine according to claim 1, wherein, The obtaining, in response to receiving product page viewing request information sent by a user terminal, the process state machine element information corresponding to the product page viewing request information as the to-be-pushed state machine element information includes: Generating page identification request information based on the product page viewing request information, and sending the page identification request information to a storage terminal; In response to receiving the page view identifier sent by the storage terminal, generate product page request information corresponding to the page view identifier, and send the product page request information to the product server; In response to receiving the session identifier information sent by the product server, obtain, from the product server, process status machine element information corresponding to the product page request information, as the to-be-pushed status machine element information.

3. The method for pushing product pages based on a state machine according to claim 2, wherein, The method further includes: In response to determining that the page view identifier sent by the storage terminal is not received within a preset duration, send preset initial session request information to the product server, and receive the page view identifier from the product server; Store the page view identifier in the storage terminal.

4. The method for pushing product pages based on a state machine according to claim 1, wherein, The rendering process of the to-be-pushed status machine element information based on the product page editing model to generate product push page information includes: Input the to-be-pushed status machine element information into the product page editing model to obtain target product page information; Send the target product page information to the detection terminal, and read the page detection result corresponding to the target product page information from the detection terminal; In response to determining that the page detection result meets the preset detection conditions, determine the target product page information as the product push page information.

5. The product page push method based on a state machine according to claim 1, wherein, The desensitization process of the product page input information to obtain user desensitized information includes: Obtain desensitization rule information and a sensitive information sequence from the product server; Perform a copy process on the product page input information to obtain a page input copy information; Perform a sensitive matching process on the page input copy information and the sensitive information sequence to obtain a page sensitive matching information sequence; Based on the desensitization rule information, perform a desensitization process on the page sensitive matching information sequence to obtain a page desensitized information sequence; Perform a fusion process on the page desensitized information sequence and the product page input information to obtain user desensitized information.

6. A computer device, wherein, The computer device includes a processor, a memory, and a computer program stored on 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-5 are implemented.

7. A computer-readable storage medium, wherein, A computer program is stored on a computer-readable storage medium, wherein when the computer program is executed by a processor, the steps of the method according to any one of claims 1-5 are implemented.

Images