Service processing method and device

Abstract

The embodiment of the invention provides a service processing method and device, and the method comprises the steps: carrying out the construction of a node link according to a target service node sequence in a plurality of service node sequences configured for the user access of a target service by a service party, and obtaining the node link, and aggregating the service nodes of each residual service node sequence to a node link to obtain a service node link diagram, and when the triggering elements in the service node link diagram are accessed, querying user access data mapped by the triggering elements and returning the user access data to the terminal of the service party. Therefore, on the basis of aggregating the plurality of service node sequences to obtain the service node link diagram, the visual display of the user access data is realized.

Description

TECHNICAL FIELD

[0001] The present document relates to the technical field of data processing, and particularly relates to a service processing method and device. BACKGROUND

[0002] With the continuous development and popularization of Internet technology, the application range of online services based on Internet technology is wider and wider, covering many service fields such as medical field, travel field and the like. The development of online services provides a convenient implementation means for user service processing. In the process of accessing these online services, the user may constantly jump, return and the like in the online services, thereby generating a series of service nodes. However, with the increasing diversification of user demand, the service of online services also faces certain challenges. SUMMARY

[0003] One or more embodiments of the present specification provide a service processing method, comprising: obtaining a plurality of service node sequences configured by a service party for user access of a target service. Node link is obtained based on a target service node sequence in the plurality of service node sequences. A node aggregation strategy is determined according to service node parameters of each remaining service node sequence in the plurality of service node sequences. The service nodes of the each remaining service node sequence are aggregated with the node link according to the node aggregation strategy, and a service node link graph is obtained. If an access request of a triggerable element in the service node link graph is detected, user access data mapped by the triggerable element is queried and returned to a terminal of the service party.

[0004] One or more embodiments of the present specification provide another service processing method, comprising: obtaining a service node link graph of a target service, and rendering and displaying a visual component. According to an access instruction of a visual element in the service node link graph, user access data mapped by the visual element is obtained from a server. A visual configuration object is generated based on the user access data, and the visual configuration object is displayed in the visual component. The service node link graph is obtained after aggregating a node link of a target service node sequence in a plurality of service node sequences and service nodes of each remaining service node sequence, and the plurality of service node sequences are configured by a service party for user access of the target service.

[0005] One or more embodiments of the present specification provide a service processing apparatus, comprising: a sequence acquisition module configured to acquire a plurality of service node sequences configured by a service party for user access of a target service. A link construction module configured to perform node link construction based on a target service node sequence in the plurality of service node sequences to obtain a node link. A policy determination module configured to determine a node aggregation policy according to service node parameters of each remaining service node sequence in the plurality of service node sequences. An aggregation module configured to aggregate service nodes of each remaining service node sequence with the node link according to the node aggregation policy to obtain a service node link graph. A data query module configured to query user access data mapped by a triggerable element in the service node link graph and return to a terminal of the service party if an access request of the triggerable element is detected.

[0006] One or more embodiments of the present specification provide another service processing apparatus, comprising: a rendering module configured to acquire a service node link graph of a target service and perform rendering and display of a visualization component. A data acquisition module configured to acquire user access data mapped by a visualization element in the service node link graph from a server according to an access instruction of the visualization element. A display module configured to generate a visual configuration object based on the user access data and display the visual configuration object in the visualization component. Wherein the service node link graph is obtained after aggregating a node link of a target service node sequence in a plurality of service node sequences with service nodes of each remaining service node sequence, and the plurality of service node sequences are configured by a service party for user access of the target service.

[0007] One or more embodiments of the present specification provide a service processing device, comprising: a processor; and a memory configured to store computer executable instructions that, when executed, cause the processor to: acquire a plurality of service node sequences configured by a service party for user access of a target service. Perform node link construction based on a target service node sequence in the plurality of service node sequences to obtain a node link. Determine a node aggregation policy according to service node parameters of each remaining service node sequence in the plurality of service node sequences. Aggregate service nodes of each remaining service node sequence with the node link according to the node aggregation policy to obtain a service node link graph. If an access request of a triggerable element in the service node link graph is detected, query user access data mapped by the triggerable element and return to a terminal of the service party.

[0008] One or more embodiments of the present specification provide another service processing device, comprising: a processor; and a memory configured to store computer executable instructions that, when executed, cause the processor to: acquire a service node link graph of a target service, and perform rendering and display of a visualization component. According to an access instruction of a visualization element in the service node link graph, acquire user access data mapped by the visualization element from a server. Generate a visual configuration object based on the user access data, and display the visual configuration object in the visualization component. Wherein the service node link graph is obtained after aggregating node links of a target service node sequence in a plurality of service node sequences and service nodes of each remaining service node sequence, the plurality of service node sequences being configured by a service party for user access of the target service.

[0009] One or more embodiments of the present specification provide a computer readable storage medium for storing computer executable instructions that, when executed, implement the following steps: acquire a plurality of service node sequences configured by a service party for user access of a target service. Obtain node links based on a target service node sequence in the plurality of service node sequences. Determine a node aggregation strategy according to service node parameters of each remaining service node sequence in the plurality of service node sequences. Aggregate service nodes of the each remaining service node sequence and the node links according to the node aggregation strategy, and obtain a service node link graph. If an access request of a triggerable element in the service node link graph is detected, query user access data mapped by the triggerable element and return to a terminal of the service party.

[0010] One or more embodiments of the present specification provide another computer readable storage medium for storing computer executable instructions that, when executed, implement the following steps: acquire a service node link graph of a target service, and perform rendering and display of a visualization component. According to an access instruction of a visualization element in the service node link graph, acquire user access data mapped by the visualization element from a server. Generate a visual configuration object based on the user access data, and display the visual configuration object in the visualization component. Wherein the service node link graph is obtained after aggregating node links of a target service node sequence in a plurality of service node sequences and service nodes of each remaining service node sequence, the plurality of service node sequences being configured by a service party for user access of the target service. BRIEF DESCRIPTION OF DRAWINGS

[0011] In order to more clearly illustrate the technical solutions in the one or more embodiments of the present specification or the prior art, the drawings needed to be used in the embodiment or prior art description will be briefly introduced as follows. Obviously, the drawings in the following description are only some embodiments described in the present specification, and for those skilled in the art, other drawings can also be obtained without creative labor on the basis of these drawings. Figure 1 A schematic diagram of a service processing method implementation environment provided for one or more embodiments of the present specification; Figure 2 A service processing method processing flowchart provided for one or more embodiments of the present specification; Figure 3 A schematic diagram of a service node link diagram provided for one or more embodiments of the present specification; Figure 4 A schematic diagram of a user churn path diagram provided for one or more embodiments of the present specification; Figure 5 A schematic diagram of a user conversion trend diagram provided for one or more embodiments of the present specification; Figure 6 A schematic diagram of a triggerable link segment of a preceding link segment provided for one or more embodiments of the present specification; Figure 7 A schematic diagram of a user access tag provided for one or more embodiments of the present specification; Figure 8 A service processing method processing flowchart applied to a medical service scenario provided for one or more embodiments of the present specification; Figure 9 Another service processing method processing flowchart provided for one or more embodiments of the present specification; Figure 10 Another service processing method processing flowchart applied to a medical service scenario provided for one or more embodiments of the present specification; Figure 11 A schematic diagram of a service processing device embodiment provided for one or more embodiments of the present specification; Figure 12 Another schematic diagram of a service processing device embodiment provided for one or more embodiments of the present specification; Figure 13 A structural schematic diagram of a service processing device provided for one or more embodiments of the present specification; Figure 14 Another structural schematic diagram of a service processing device provided for one or more embodiments of the present specification. DETAILED DESCRIPTION

[0012] In order to make the technical solution in one or more embodiments of the present specification better understood by those skilled in the art, the technical solution in one or more embodiments of the present specification will be clearly and completely described below in conjunction with the drawings in one or more embodiments of the present specification. Obviously, the described embodiments are only part of the embodiments of the present specification, rather than all the embodiments. Based on one or more embodiments of the present specification, all other embodiments obtained by those skilled in the art without creative labor should belong to the protection scope of the present document.

[0013] The service processing method provided by one or more embodiments of the present specification can be applied to the implementation environment of the target service, and the implementation environment at least includes Figure 1 , which comprises: The server 101; in addition, the implementation environment can also include the terminal 102 of the service party of the target service; Among them, the server 101 is used to construct node link based on the target service node sequence in the multiple service node sequences configured by the service party for the user access of the target service, aggregate the service nodes and node links of each remaining service node sequence to obtain the service node link graph, query the user access data that can trigger the element mapping in the service node link graph and return to the terminal 102; the server 101 can be one or more servers, a server cluster composed of several servers, or a cloud server of a cloud computing platform; The terminal 102 is used to obtain the user access data that can trigger the visual configuration object based on the user access data generated by the visual element mapping from the server according to the access instruction of the visual element in the service node link graph, and display the visual configuration object based on the user access data in the visual component; the terminal 102 can be a mobile phone, a personal computer, a tablet computer, an electronic book reader, a wearable device, a device based on AR (Augmented Reality, Augmented Reality) / VR (Virtual Reality, Virtual Reality) for information interaction, and a laptop computer, etc.

[0014] In the implementation environment, after the server 101 obtains the multiple service node sequences configured by the service party for the user access of the target service, the node link is constructed based on the target service node sequence to obtain the node link, the service nodes of each remaining service node sequence are aggregated to the node link to obtain the service node link graph, and the user access data that can trigger the element is queried and returned to the terminal 102 of the service party in the case that the element is accessed in the service node link graph, so as to realize the visual display of the user access data based on the aggregation of the multiple service node sequences to obtain the service node link graph.

[0015] One or more embodiments of the service processing method provided by the present specification are as follows: With reference to Figure 2 The service processing method provided by the embodiment can be applied to a server and specifically includes steps S202 to S210.

[0016] In step S202, a plurality of service node sequences configured by a service party for user access to a target service are obtained.

[0017] The target service in the embodiment refers to a target service corresponding to the service party. The target service can be a service in any field, such as a medical service, a medical insurance service, a travel service, a carbon reduction service, or a payment service. The target service can be an online service or an offline service, such as an offline payment service.

[0018] The plurality of service node sequences refer to a plurality of service node sequences that can be taken by a user to complete the same task in the target service. The service node sequence refers to a sequence composed of service nodes arranged in a certain order. The service node sequence can be formed by a user accessing the target service. Optionally, each service node sequence in the plurality of service node sequences is a service node sequence for a specific user type of the target service. The service node sequence can also be a service node path, that is, a service node sequence or a service node path composed of service nodes formed by a user accessing the target service, for example, the service node sequence is visiting a medical insurance account query, supplementing medical insurance, going to see, visiting a medical insurance area, and clicking to view the details of the insurance.

[0019] In actual application, different users can form different service node sequences in the process of accessing the target service. To this end, in order to understand the related service data of the target service from the overall dimension, the plurality of service node sequences can be aggregated. To meet the diversified aggregation needs of the target service, the plurality of service node sequences configured by the service party for user access to the target service can be obtained before the plurality of service node sequences are aggregated. Specifically, a terminal of the service party can obtain the plurality of service node sequences configured by the service party for user access to the target service and submit the plurality of service node sequences to the server. The server can obtain the plurality of service node sequences submitted by the terminal. Alternatively, the terminal of the service party can obtain the plurality of service node sequences configured by the service party for user access to the target service and submit the plurality of service node sequences to the server. The server can store the plurality of service node sequences and read the plurality of service node sequences configured by the service party for user access to the target service according to a reading period.

[0020] It should be noted that the obtaining the plurality of service node sequences configured for the user access of the target service by the service party can be replaced by obtaining the plurality of service node sequences for the user access of the target service, or can be replaced by obtaining the plurality of service node sequences configured for the user access of the target service, or can also be replaced by obtaining the plurality of service node sequences of the target service; the plurality of service node sequences can also be at least one service node sequence, and constitute a new implementation manner with other processing steps provided in the embodiment.

[0021] In step S204, the node link is constructed based on the target service node sequence in the plurality of service node sequences to obtain the node link.

[0022] The plurality of service node sequences configured for the user access of the target service by the service party are obtained, and in this step, the node link is constructed based on the target service node sequence in the plurality of service node sequences to obtain the node link, so as to realize the construction of the node link of the target service node sequence, and facilitate the subsequent aggregation of the service node.

[0023] The number of the target service node sequences can be one or more; optionally, the target service node sequence is selected from the plurality of service node sequences according to the arrangement order of the plurality of service node sequences, or is selected from the plurality of service node sequences according to the sequence parameters of each service node sequence in the plurality of service node sequences; the sequence parameters can include the number of service nodes included in each service node sequence and / or the number of pages to which the service nodes included in each service node sequence belong, and in addition, the sequence parameters can also be other types of parameters.

[0024] The node link refers to the node link obtained by connecting the service nodes in the target service node sequence according to the user access order.

[0025] In specific implementation, in order to improve the convenience of subsequent service node aggregation, the node link can be constructed based on the target service node sequence to obtain the node link, so that there is a reference in the subsequent service node aggregation process, and the aggregation of the service node is more flexible with the node link as the reference; specifically, the target service node sequence can be selected from the plurality of service node sequences, and the node link can be constructed based on the target service node sequence; in the process of selecting the target service node sequence from the plurality of service node sequences, the target service node sequence can be selected from the plurality of service node sequences according to the arrangement order of the plurality of service node sequences, or the target service node sequence can be selected from the plurality of service node sequences according to the sequence parameters of each service node sequence in the plurality of service node sequences.

[0026] In the process of constructing the node link based on the target service node sequence, in order to make the node link more clearly represent the node relationship between the service nodes, each link node can be constructed based on each service node in the target service node sequence, and the node link is obtained by connecting each link node according to the arrangement order of the service nodes; for example, each link node is constructed based on each service node in the order from left to right, and the node link is obtained by connecting each link node according to the arrangement order of the service nodes in the target service node sequence, such as the node link in Figure 3 Access medical insurance account query→Supplement medical insurance to see→Access medical insurance area→Click to view insurance details.

[0027] In actual application, there may be repeated service nodes in the service nodes in the target service node sequence in the process of accessing the target service, and for this purpose, in order to improve the simplicity of the node link, in the process of constructing the node link based on the target service node sequence, the node deployment field corresponding to the node type of the next service node can be used to detect the link node matched with the next service node in the node link to be updated, and the link node corresponding to the previous service node is connected based on the detected link node; if no matched link node is detected, the link node is constructed based on the next service node and connected with the link node corresponding to the previous service node. The node deployment field corresponding to the node type of the next service node can be determined based on the access device type and / or node attribute of the next service node, and specifically, if the access device type is a first device type, the service scene field of the next service node can be used as the node deployment field, and if the access device type is a second device type, the corresponding node deployment field is determined according to the node attribute of the next service node; the first device type herein can include a computer device type, such as a PC (Personal Computer) device type; the second device type can include a mobile terminal type other than the computer device type.

[0028] Step S206: determining a node aggregation strategy according to the service node parameters of each remaining service node sequence in the plurality of service node sequences.

[0029] In the above process of constructing the node link based on the target service node sequence in the plurality of service node sequences, in this step, the node aggregation strategy is determined according to the service node parameters of each remaining service node sequence in the plurality of service node sequences, so as to provide different node aggregation strategies for different service nodes to improve the flexibility of node aggregation.

[0030] The service node parameter of each remaining service node sequence refers to the node parameter of the service node of each remaining service node sequence. The service node parameter can include the access device type of the service node and / or the node attribute. The access device type refers to the device type used by the user when accessing the service node. The node attribute can be determined based on the node attribute field of the service node. The node aggregation policy refers to the aggregation policy of aggregating the service node to the node link.

[0031] The service node parameter of each remaining service node sequence refers to the node parameter of the service node of each remaining service node sequence. The service node parameter can include the access device type of the service node and / or the node attribute. The access device type refers to the device type used by the user when accessing the service node. The node attribute can be determined based on the node attribute field of the service node. The node aggregation policy refers to the aggregation policy of aggregating the service node to the node link.

[0032] In actual application, different users can form different service node sequences in the process of accessing the target service. In order to analyze the user access and user conversion of the target service as a whole, the plurality of service node sequences can be aggregated to obtain a service node link graph. In order to further improve the flexibility of node aggregation and meet the diversified needs of node aggregation, in an optional implementation provided by the embodiment, in the process of determining the node aggregation policy according to the service node parameters of each remaining service node sequence in the plurality of service node sequences, the node aggregation policy of the service node is determined according to the access device type and / or the node attribute of the service node of each remaining service node sequence. Specifically, the following operations can be performed: The node deployment field is determined according to the access device type and the node attribute of the service node of each remaining service node sequence. The node aggregation policy of the service node is determined based on the node deployment field.

[0033] The access device type of the service node refers to the device type used by the user when accessing the service node. The node attribute of the service node can be determined based on the node attribute field of the service node. The node deployment field refers to the field related to the deployment of the service node.

[0034] Specifically, in the process of determining the node aggregation policy of the service node based on the node deployment field, the strategy of matching the node based on the node deployment field can be used as the node aggregation policy of the service node.

[0035] In addition, in the process of determining the node aggregation policy according to the service node parameters of each remaining service node sequence in the plurality of service node sequences, the node deployment field can also be determined according to the access device type or the node attribute of the service node of each remaining service node sequence, and the node aggregation policy of the service node is determined based on the node deployment field.

[0036] On this basis, in an optional implementation of the embodiment, in the process of determining the node deployment field according to the access device type and the node attribute of the service node of each residual service node sequence, the following operation is performed: If the access device type is the first device type, the service scene field of the service node is taken as the node deployment field. If the access device type is the second device type, the corresponding node deployment field is determined according to the node attribute of the service node.

[0037] The first device type includes a computer device type, and the second device type can include a mobile terminal type, which can be a mobile terminal type other than the computer device type. The node attribute of the service node includes a page access attribute, a module access attribute, a payment attribute, or a component exposure attribute. The module access attribute includes a module exposure attribute or a module click attribute.

[0038] For example, if the access device type is the computer device type, the service scene field scene_id of the service node is taken as the node deployment field. If the access device type is the mobile terminal type, the corresponding node deployment field is determined according to the node attribute of the service node. In the process of determining the corresponding node deployment field according to the node attribute of the service node, if the node attribute of the service node is the page access attribute, the node deployment field of the service node is determined to be appId (application ID, application identifier), spma (sampling page model a, application level), spmb (sampling page model b, page level), and url (uniform resource locator, uniform resource locator). If the node attribute of the service node is the module access attribute, the node deployment field of the service node is determined to be appId, spma, spmb, url, and spmcd identifier {spm: "", name: ""}. If the node attribute of the service node is the payment attribute, the node deployment field of the service node is determined to be appId and spmcd identifier {spm: "", name: ""}. If the node attribute of the service node is the component exposure attribute, the node deployment field of the service node is determined to be appId.

[0039] The node attribute of the service node mentioned above includes a page access attribute, a module access attribute, a payment attribute, or a component exposure attribute. The node attribute of the service node can be determined based on the field value of the node attribute field of the service node. For example, if the node attribute field spmcd of the service node is empty and the action is expose, it is determined that the node attribute of the service node is the page access attribute. If the node attribute field spmcd of the service node is not empty and the action is expose and / or click, it is determined that the node attribute of the service node is the module access attribute. If the node attribute field xxx of the service node is a specific payment identifier, it is determined that the node attribute of the service node is the payment attribute. If the node Type of the node attribute field of the service node is group or single, and the action is expose, it is determined that the node attribute of the service node is the component exposure attribute.

[0040] In step S208, the service nodes and node links of each remaining service node sequence are aggregated according to the node aggregation strategy to obtain a service node link graph.

[0041] In the above, the node aggregation strategy is determined according to the service node parameters of each remaining service node sequence in the plurality of service node sequences. In this step, the service nodes and node links of each remaining service node sequence are aggregated according to the node aggregation strategy to obtain a service node link graph. In this way, the service-related analysis of the target service is conveniently realized through the service node link graph.

[0042] The service node link graph described in the embodiment refers to a service node link graph composed of one or more node links. The same link node in the service node link graph can only appear once. The service node link graph can have a ring structure. Multiple parallel service nodes under the same page node can be arranged in a left-right structure. Multiple serial service nodes under the same page node can be arranged in an up-down structure. Different page nodes can be arranged in a left-right structure. For example Figure 3 The service node link graph shown in the figure, one node link is access medical insurance account query→supplement medical insurance go and see→access medical insurance area→click to view insurance details. One node link is access my page→supplement medical insurance go and see→access medical insurance area→click to view insurance details. Another node link is access medical insurance area→click to supplement medical insurance→access supplement medical insurance introduction→click to make an appointment for insurance. The node links in the service node link graph are connected by lines of different colors.

[0043] In actual implementation, in order to avoid the repetition of service nodes in the service node link diagram, so as to make the service node link diagram more concise and clear, in an optional implementation provided by the embodiment, in the process of aggregating the service nodes and node links of each remaining service node sequence according to the node aggregation strategy to obtain the service node link diagram, the matching link node of the service node is detected from the link nodes contained in the node link according to the node deployment field corresponding to the node type of the service node, and the node connection is performed to obtain the service node link diagram. The following operations can be performed: The matching link node of the service node is detected from the link nodes contained in the node link according to the node deployment field corresponding to the node type of the service node. The node connection is performed based on the detected link node to obtain the service node link diagram.

[0044] On this basis, in order to improve the comprehensiveness of service node aggregation, in an optional implementation provided by the embodiment, after the above operation of detecting the matching link node of the service node from the link nodes contained in the node link according to the node deployment field corresponding to the node type of the service node, if no matching link node is detected, the link node corresponding to the service node is constructed in the node link according to the node deployment position corresponding to the service page where the service node is located, and the node connection is performed to obtain the service node link diagram. The following operations can also be performed: If no matching link node is detected, the node deployment position in the node link is determined based on the service page where the service node is located. The link node corresponding to the service node is constructed in the node link according to the node deployment position, and the node connection is performed to obtain the service node link diagram.

[0045] The service page where the service node is located refers to the page to which the service node belongs in the target service. The node deployment position refers to the deployment position of the service node in the node link.

[0046] Specifically, the link node with the same node deployment field as the next service node can be detected in the link nodes included in the node link, the detected link node is connected with the link node corresponding to the previous service node to obtain the service node link graph, if the detection result is empty, the node deployment position is determined in the node link based on the service page where the next service node is located, the link node corresponding to the next service node is constructed in the node link according to the node deployment position, and the constructed link node is connected with the link node corresponding to the previous service node to obtain the service node link graph; that is, for the service nodes of each remaining service node sequence, the node matching can be performed in the node link from front to back based on the node deployment field, and in the case of successful matching, the matched link node is connected with the link node corresponding to the previous service node to obtain the service node link graph. It should be noted that, in the process of detecting the link node matched with the service node in the link nodes included in the node link according to the node deployment field corresponding to the node type of the service node, and connecting the nodes based on the detected link node to obtain the service node link graph, for the first time, the link node with the same node deployment field as the next service node can be detected in the link nodes included in the first node link according to the node deployment field corresponding to the node type of the next service node, the detected link node is connected with the link node corresponding to the previous service node to obtain the second node link, if the next service node of the next service node is empty, the second node link can be used as the service node link graph, if the next service node is not empty, the link node matched with the next service node can be detected in the link nodes included in the second node link according to the node deployment field corresponding to the node type of the next service node of the next service node, the detected link node is connected with the link node corresponding to the next service node to obtain the third node link, if the next service node of the next service node is empty, the third node link is used as the service node link graph, if the next service node of the next service node is not empty, the detection and connection of the link node are continued according to the above execution process until the service node link graph is obtained.

[0047] After the service nodes and node links of each remaining service node sequence are aggregated according to the node aggregation strategy to obtain the service node link graph, the server can directly issue the service node link graph to the terminal of the service party, or the server can store the service node link graph, and in the case that the terminal of the service party submits an access request for the service node link graph, the service node link graph can be issued to the terminal; the terminal can obtain the service node link graph of the target service and render and display the visual component, specifically, the rendering and display of the visual component can be performed at a specific position of an upper layer of the service node link graph, and the specific position can be any position, such as an edge position, and the visual component can be a visual panel, a visual board or a visual window, in addition, the visual component can also be other types of components.

[0048] In step S210, if the access request of the triggerable element in the service node link graph is detected, the user access data mapped by the triggerable element is queried and returned to the terminal of the service party.

[0049] In the above, the service nodes and node links of each remaining service node sequence are aggregated according to the node aggregation strategy to obtain the service node link graph, and in the case that the access request of the triggerable element in the service node link graph is detected, the user access data mapped by the triggerable element is queried and returned to the terminal of the service party.

[0050] The triggerable element described in the embodiment refers to a link element that can be triggered in the service node link graph, and the triggerable element can include a triggerable link segment and / or a triggerable node in the service node link graph, and the user access data mapped by the triggerable element can include at least one of the following: a user churn path of a preceding link node of the triggerable link segment, a user access frequency of a user churn node in the user churn path, user conversion data of the preceding link node of the triggerable link segment, a link segment identifier of the preceding link segment, a user access index of the triggerable node, and an access relationship index of the triggerable node in the node link. In addition, the triggerable element can also include other types of link elements; the user access data refers to data related to the user access of the target service.

[0051] In specific implementation, the terminal of the service party can obtain the user access data mapped by the visual element according to the access instruction of the visual element in the service node link graph, and the server can query the user access data mapped by the triggerable element and return to the terminal of the service party; specifically, the terminal of the service party can obtain the access instruction of the visual element in the service node link graph submitted by the service party, generate an access request and send it to the server, and the server can query the user access data mapped by the triggerable element based on the access request sent by the terminal and return to the terminal.

[0052] In actual application, the service provider of the target service may have more interaction requirements or access requirements for the service node link graph. In order to improve the flexibility of accessing the service node link graph, the intuitiveness of user access data of the target service is improved through visualization, so as to facilitate the service provider to make further service decisions of the target service based on the visualized user access data. In the first optional implementation provided in the embodiment, in the process of querying the user access data of the triggerable element mapping, the user churn path of the preceding link node of the triggerable link segment in the service node link graph and / or the user access times of the user churn node in the user churn path can be queried. The following operations can be specifically performed: determining the preceding link node of the triggerable link segment in the service node link graph; querying the user churn path of the preceding link node and the user access times of the user churn node in the user churn path.

[0053] The triggerable link segment refers to the link segment between any two link nodes in the service node link graph, and the preceding link node refers to the link node at the front position of the triggerable link. For example, as shown in the service node link graph, Figure 3 the link segment 301 between the link nodes of accessing medical insurance area and clicking to view insurance details is a triggerable link segment, and the preceding link node of the triggerable link segment is the link node of accessing medical insurance area. The user churn path of the preceding link node refers to the user churn path generated from the preceding link node without user access according to the node link in the service node link graph, that is, the path formed from the user churn direction of the preceding link node. There is one or more user churn nodes in the user churn path, and the user access times of the user churn node can be the number of times the user churn node is accessed.

[0054] Specifically, the service provider can select to view the user churn path graph or view the user conversion trend graph in the access list after submitting the access instruction for the triggerable link segment, and can also select to view the user churn solution or user churn reason analysis.

[0055] The terminal of the service provider can obtain the user access data of the visual element mapping from the server according to the access instruction of the visual element in the service node link graph, and the terminal can generate a visual configuration object based on the user access data and display the visual configuration object in the visual component. The visual configuration object refers to visual configuration data, such as the user churn path graph of the preceding link node, the user conversion trend graph, and / or the user access label of the triggerable node. In addition, the visual configuration object can also include the dynamic rendering mark of the preceding link segment.

[0056] On the basis of querying the user churn path of the pre-link node and the user access times of the user churn node in the user churn path, the terminal of the service party can construct the user churn path graph of the pre-link node based on the user churn path and / or the user access times, and can also display the user churn path graph in the visualization component deployed in the upper layer of the service node link graph; in an optional implementation of the embodiment, after the terminal of the service party receives the user churn path and the user access times, the following operations are performed: constructing the user churn path graph of the pre-link node based on the user churn path and the user access times; displaying the user churn path graph in the visualization component deployed in the upper layer of the service node link graph.

[0057] Further, in order to more clearly display the user churn details such as the user churn proportion of each user churn node in the user churn path, so that the target service can mine the user churn reason from the fine-grained level of the user churn node, thereby improving the user churn situation and improving the user retention rate; in an optional implementation of the embodiment, in the process of constructing the user churn path graph of the pre-link node based on the user churn path and the user access times, the user churn path graph is constructed according to the previous user churn node, the next user churn node in the user churn path and the churn boundary information determined based on the user access times, and the following operations can be specifically performed: calculating the churn boundary information of the previous user churn node and the next user churn node according to the user access times of the next user churn node in the user churn path; constructing the user churn path graph based on the previous user churn node, the next user churn node and the churn boundary information.

[0058] The churn boundary information of the previous user churn node and the next user churn node can be the boundary shape of the previous user churn node and the next user churn node, such as the churn height, specifically the up-down height between the previous user churn node and the next user churn node.

[0059] Specifically, in the process of calculating the churn boundary information of the previous user churn node and the next user churn node according to the user access times of the next user churn node in the user churn path, the proportion of the user access times of the next user churn node in the user access times of the previous user churn node can be used to calculate the churn boundary shape of the previous user churn node and the next user churn node, and the user churn path graph is constructed based on the previous user churn node, the next user churn node and the churn boundary shape.

[0060] For example, after detecting the access request for the triggerable link segment 301 in the user node link graph, it is determined that the pre-link node of the triggerable link segment 301 is an access medical insurance special area, the user churn path of the pre-link node and the user access times of the user churn nodes in the user churn path are queried, the pre-link node is taken as the current link node, the user access times of the next user churn node of the pre-link node in the user churn path are calculated, the user churn boundary shape between the pre-link node and the next user churn node is calculated based on the user churn boundary shape, and the user churn boundary is constructed between the pre-link node and the next user churn node. In the case that the next user churn node of the next user churn node of the pre-link node exists, the user churn boundary shape between the next user churn node of the pre-link node and the next user churn node is calculated according to the user access times of the next user churn node of the next user churn node of the pre-link node, and the user churn path graph is obtained based on the user churn boundary between the next user churn node of the pre-link node and the next user churn node. Figure 4 As shown in the user churn path graph, the current node, i.e. the pre-link node, is an access commercial insurance special area, the next user churn node of the pre-link node includes a medical insurance code and a medical insurance channel homepage, the next user churn node of the medical insurance code includes a medical insurance channel homepage and a channel homepage, the next user churn node of the next user churn node of the access commercial insurance special area "medical insurance channel homepage" includes a medical insurance channel homepage and a channel homepage, and the next user churn node of the channel homepage includes a homepage. The user churn boundary shape or the user churn boundary height between adjacent user churn nodes is calculated based on the user access times of the adjacent user churn nodes.

[0061] In the specific implementation process, the user conversion data of the link node in the service node link graph is also crucial. The service provider of the target service can clearly show the user conversion rate based on the user conversion data, so as to provide services that are more in line with the needs of users based on the user conversion rate. In the second optional implementation provided in the embodiment, in the process of querying the user access data of the triggerable element mapping, the following operations are performed: According to the pre-link node of the triggerable link segment in the service node link graph, the user conversion data of the pre-link node is queried.

[0062] Optionally, the terminal of the service provider generates a user conversion trend graph of the pre-link node based on the user conversion data. The terminal of the service provider can generate a user conversion trend graph of the pre-link node based on the user conversion data of the pre-link node of the triggerable link segment in the service node link graph, and the user conversion trend graph can be displayed on the visualization component.

[0063] The user conversion data can include the number of user visits of the preceding link node and / or the number of user visits of the previous link node of the preceding link node of the service node link graph; and the user conversion trend chart can be a user conversion trend chart in a specific time period, such as a user conversion trend chart in the last 7 days. Figure 5 The user conversion trend chart shown in FIG. 6 is a user conversion trend chart in the last 7 days, and the user conversion rate can be shown in the user conversion trend chart.

[0064] In addition, the user conversion data of the node link can also be queried according to the node link in which the triggerable link segment is located in the service node link graph, that is, the number of user visits of the first link node and the last link node in the node link is queried, and the user conversion trend chart of the node link is generated based on the number of user visits of the two.

[0065] In actual application, the node links in the service node link graph are aggregated in one block, and the service party has a demand to view a certain node link in the service node link graph. In this regard, in order to flexibly enable the service party to view a certain node link and improve the intuitiveness of the node link in the service node link graph, the third optional embodiment provided in the embodiment provides that, in the process of querying the user access data of the triggerable element mapping, the link segment identifier of the preceding link segment of the triggerable link segment in the service node link graph is taken as the user access data, and the following operations can be performed: The preceding link segment of the triggerable link segment in the service node link graph is determined, and the link segment identifier of the preceding link segment is taken as the user access data.

[0066] Optionally, the terminal of the service party visually renders the preceding link segment corresponding to the link segment identifier in the service node link graph.

[0067] The preceding link segment of the triggerable link segment refers to the link segment before the triggerable link segment in the node link in which the triggerable link segment is located in the service node link graph.

[0068] Specifically, the triggerable link segment can be determined based on the hovering instruction of the service party on the triggerable link segment; in the process of visually rendering the preceding link segment corresponding to the link segment identifier in the service node link graph, the preceding link segment can be visually rendered according to a preset rendering element, and specifically, the preceding link segment can be rendered as a dashed line and dynamically displayed; for example, the triggerable link segment is 301 in FIG. 5, the preceding link segments of the triggerable link segment are 601, 602 and 603 as shown in FIG. 6, and the preceding link segments are rendered as dashed lines and dynamically displayed. Figure 3 Figure 6

[0069] ​​In addition, in an actual application scenario, the service party also has a demand for accessing the triggerable node in the service node link graph and timely understanding the user access index of the triggerable node. In the fourth optional implementation provided in the embodiment, in the process of querying the user access data of the triggerable element mapping, based on the triggerable node corresponding to the access request in the service node link graph, the user access index and / or the access relationship index of the triggerable node in the node link where the triggerable node is located are queried, and the following operations can be specifically performed: Based on the triggerable node corresponding to the access request in the service node link graph, the user access index of the triggerable node and / or the access relationship index of the triggerable node in the node link where the triggerable node is located are queried.

[0070] Optionally, the terminal of the service party generates the user access label of the triggerable node based on the user access index and / or the access relationship index.

[0071] The user access index of the triggerable node can include the user access times of the triggerable node, for example, the user access index is pv (page piew, page view) and uv (unique visitor, unique visitor number); the access relationship index of the triggerable node in the node link where the triggerable node is located refers to the access relationship index of the triggerable node in the node link, and the access relationship index can include the user access index and / or the user access proportion, and the user access proportion can include the proportion of the user access index of the triggerable node in the node link where the triggerable node is located in the total user access index of the triggerable node. The terminal of the service party can display the user access label in a visual component. The access request can be generated based on the hovering instruction of the triggerable node.

[0072] For example Figure 7 As shown in the figure, the triggerable node is to click to view the details of the insurance, the total pv of the triggerable node in the user access label is xx1, the total uv is xx2, the node link where the triggerable node is located in the service node link graph is node link 1, so the pv of the triggerable node in the node link 1 is xx3, the uv is xx5, the proportion of the pv of the triggerable node in the node link 1 is xx4, and the proportion of the uv of the triggerable node in the node link 1 is xx6.

[0073] It should be noted that the user data obtained by the present application is authorized by the user and does not involve user privacy.

[0074] It should be further explained that the steps S202 to S204 can be replaced by: according to the service policy, configuring a target service node sequence in a plurality of service node sequences of the target service, and performing node link construction to obtain a node link; the steps S206 to S208 can be replaced by: based on the service node parameters of each remaining service node in the plurality of service node sequences, aggregating the service nodes and the node links of each remaining service node to obtain a service node link graph; and the step S210 can be replaced by: querying the user access data that can trigger the element mapping in the service node link graph and returning to the terminal of the service party, or can be replaced by: querying the user access data that can trigger the element mapping in the service node link graph.

[0075] It should be further explained that each optional implementation and each feasible execution mode in the steps S202 to S210 provided by the embodiment can be independently executed as needed, or can be combined with each other and referred to each other, and each specific execution step in each optional implementation or each feasible execution mode can also be independently executed or executed in combination as needed. The execution condition of "if" or "under what circumstances" involved in each step or operation can be directly deleted, and the operation after the execution condition can be executed subsequently, and the embodiment does not make a specific limitation on this.

[0076] The implementation process of the service processing method provided above can be executed by a server, and the implementation process of another service processing method provided by the following method embodiment can be executed by a terminal of a service party, and the two can cooperate with each other in the execution process. Therefore, the above implementation process can refer to the corresponding content of the following another service processing method embodiment, and correspondingly, the following another service processing method embodiment can also refer to the corresponding content of the above method embodiment.

[0077] In summary, the service processing method provided in the embodiment can first construct node links according to a target service node sequence in a plurality of service node sequences configured by a service party for a target service, so as to realize subsequent node aggregation more flexibly and conveniently by using the constructed node links as a reference. Then, a node aggregation strategy is determined according to service node parameters of each remaining service node sequence in the plurality of service node sequences, and the service node and the node link are aggregated according to the node aggregation strategy of the service node of each remaining service node sequence to obtain a service node link graph. In this way, the flexibility of node aggregation is improved by providing different node aggregation strategies for different service nodes, so as to meet diversified node aggregation requirements. On this basis, user access data mapped by a triggerable element in the service node link graph is returned to a terminal, a visual configuration object is generated based on the user access data, and the visual configuration object is displayed on a visualization component. In this way, the visualization of the user access data is realized by interacting with the service node link graph, and the intuitiveness and convenience of the service party in accessing the user access data are improved.

[0078] The service processing method provided in the embodiment is further described below by taking an application of the service processing method in a medical service scenario as an example. Referring to Figure 8 , the service processing method applied in the medical service scenario specifically includes the following steps.

[0079] In step S802, a plurality of service node sequences configured by a service party for user access of a medical service are obtained.

[0080] In step S804, node links are constructed based on a target service node sequence in the plurality of service node sequences.

[0081] In step S806, a node deployment field is determined according to an access device type and a node attribute of a service node of each remaining service node sequence in the plurality of service node sequences.

[0082] In step S808, a link node matched with the service node is detected in link nodes contained in the node links according to the node deployment field.

[0083] In step S810, node connection is performed based on the detected link node to obtain a service node link graph.

[0084] In step S812, if an access request of a triggerable element in the service node link graph is detected, user access data mapped by the triggerable element is queried and returned to a terminal of the service party.

[0085] It should be noted that any one or any combination of steps S802 to S812 can be replaced by the corresponding technical means provided in steps S202 to S210 according to the needs of implementation and deployment, and any one or any combination of steps S802 to S812 can be combined into a new implementation manner according to the needs of implementation and deployment; and any one or any combination of steps S802 to S812 can also be combined with one or more steps provided in steps S202 to S210 to form a new implementation manner, or combined with one or more optional implementation manners provided in steps S202 to S210 to form a new implementation manner, which will not be described here.

[0086] One or more embodiments of another service processing method provided in the specification are as follows: With reference to Figure 9 The service processing method provided in the embodiment can be applied to a terminal of a service party, and specifically includes steps S902 to S906.

[0087] In step S902, a service node link diagram of a target service is obtained, and rendering and display of a visual component are performed.

[0088] Optionally, the service node link diagram is obtained after aggregating node links of a target service node sequence in a plurality of service node sequences and service nodes of each remaining service node sequence, and the plurality of service node sequences are configured by a service party for user access to the target service.

[0089] The target service in the embodiment refers to a target service corresponding to the service party. The target service can be a service in any field, such as a medical service, a medical insurance service, a travel service, a carbon reduction service, or a payment service. The target service can be an online service or an offline service, such as an offline payment service.

[0090] The plurality of service node sequences refer to a plurality of service node sequences that can be taken by a user to complete the same task in the target service. The service node sequence refers to a sequence composed of service nodes arranged in a certain order, and the service node sequence can be formed by a user accessing the target service. Optionally, each service node sequence in the plurality of service node sequences is a service node sequence for a specific user type of the target service. The service node sequence can also be a service node path, that is, a service node sequence or a service node path composed of service nodes formed by a user accessing the target service, for example, a service node sequence for accessing a medical insurance account query, supplementing medical insurance, going to see, accessing a medical insurance area, and clicking to view details of an insurance type.

[0091] In actual application, different users can form different service node sequences in the process of accessing the target service by the user, and in view of this, in order to understand the related service data of the target service from the overall dimension, the plurality of service node sequences can be aggregated, and in order to meet the diversified aggregation requirements of the target service, the plurality of service node sequences configured by the service party for the user access of the target service can be acquired before the plurality of service node sequences are aggregated, specifically, the terminal of the service party can acquire the plurality of service node sequences configured by the service party for the user access of the target service and submit to the server, the server can acquire the plurality of service node sequences submitted by the terminal, or the terminal of the service party can acquire the plurality of service node sequences configured by the service party for the user access of the target service and submit to the server, and the server can store the plurality of service node sequences and read the plurality of service node sequences configured by the service party for the user access of the target service according to the reading period.

[0092] In specific implementation, the service node link graph of the target service can be acquired and displayed, and the rendering and display of the visualization component can be performed; specifically, the service node link graph of the target service can be acquired, and the rendering and display of the visualization component can be performed on the upper layer of the service node link graph.

[0093] The server can acquire the plurality of service node sequences configured by the service party for the user access of the target service, and after that, the server can construct the node link of the target service node sequence in the plurality of service node sequences to obtain the node link, so as to realize the construction of the node link of the target service node sequence, and facilitate the subsequent aggregation of the service node.

[0094] The number of the target service node sequences can be one or more; optionally, the target service node sequence is selected and obtained in the plurality of service node sequences according to the arrangement order of the plurality of service node sequences, or is selected and obtained in the plurality of service node sequences according to the sequence parameters of each service node sequence in the plurality of service node sequences; the sequence parameters here can include the number of service nodes included in each service node sequence and / or the number of pages of the service nodes included in each service node sequence, in addition, the sequence parameters can also be other types of parameters. The node link refers to the node link obtained by connecting the service nodes in the target service node sequence according to the user access order.

[0095] In actual implementation, in order to improve the convenience of subsequent service node aggregation, the server can first construct node links based on the target service node sequence to obtain node links, so that there is a reference in the subsequent service node aggregation process, and the aggregation of service nodes is more flexible based on the node links. Specifically, the server can select a target service node sequence from multiple service node sequences, and construct node links based on the target service node sequence to obtain node links. In the process of selecting a target service node sequence from multiple service node sequences, the server can select a target service node sequence from multiple service node sequences according to the arrangement order of multiple service node sequences, or select a target service node sequence from multiple service node sequences according to the sequence parameters of each service node sequence in multiple service node sequences.

[0096] In the process of constructing node links based on the target service node sequence to obtain node links, in order to make the node links more clearly represent the node relationship between the service nodes, the server can construct each link node based on each service node in the target service node sequence, and connect each link node based on the arrangement order of the service nodes to obtain the node link. For example, construct each link node based on each service node in the order from left to right, and connect each link node based on the arrangement order of the service nodes in the target service node sequence to obtain the node link, such as the node link in Figure 3 Access medical insurance account query-supplement medical insurance to see-access medical insurance area-click to view the details of the insurance.

[0097] In actual application, in the process of accessing the target service, there may be a return operation, so there may be repeated service nodes in the service nodes in the target service node sequence. In this regard, in order to improve the simplicity of the node link, in the process of constructing the node link based on the target service node sequence, the server can detect the link node matched with the next service node in the to-be-updated node link based on the node deployment field corresponding to the node type of the next service node, connect the detected link node with the link node corresponding to the previous service node, and if no matched link node is detected, construct a link node based on the next service node and connect it with the link node corresponding to the previous service node. The node type of the latter service node corresponds to a node deployment field, which can be determined based on the access device type and / or node attribute of the latter service node. Specifically, if the access device type is a first device type, the service scenario field of the latter service node can be used as the node deployment field. If the access device type is a second device type, the corresponding node deployment field is determined according to the node attribute of the latter service node. The first device type can include a computer device type, such as a PC (Personal Computer) device type. The second device type can include a mobile terminal type other than the computer device type.

[0098] The server constructs a node link based on the target service node sequence in the plurality of service node sequences, and then determines a node aggregation strategy according to the service node parameters of each remaining service node sequence in the plurality of service node sequences. In this way, different node aggregation strategies are provided for different service nodes to improve the flexibility of node aggregation.

[0099] The remaining service node sequences refer to the remaining service node sequences in the plurality of service node sequences except the target service node sequence. Each remaining service node sequence can be one service node sequence or a plurality of service node sequences, i.e., the number of each remaining service node sequence can be one or more.

[0100] The service node parameters of each remaining service node sequence refer to the node parameters of the service nodes of each remaining service node sequence. The service node parameters can include the access device type and / or node attribute of the service nodes. The access device type refers to the device type used by the user when accessing the service node. The node attribute can be determined based on the node attribute field of the service node. The node aggregation strategy refers to the aggregation strategy of aggregating the service nodes to the node link.

[0101] In actual application, different users may form different service node sequences during service access to the target service. To analyze the user access and user conversion of the target service as a whole, the plurality of service node sequences can be aggregated to obtain a service node link graph. To further improve the flexibility of node aggregation and meet the diversified needs of node aggregation, the server can determine the node aggregation strategy of the service nodes according to the access device type and / or node attribute of the service nodes of each remaining service node sequence in the plurality of service node sequences. Specifically, the node deployment field can be determined according to the access device type and node attribute of the service nodes of each remaining service node sequence. The node aggregation strategy of the service nodes is determined based on the node deployment field.

[0102] The access device type of the service node refers to a device type used by a user when accessing the service node, and the node attribute of the service node can be determined based on the node attribute field of the service node. The node deployment field refers to a field related to the deployment of the service node.

[0103] Specifically, in the process of determining the node aggregation policy of the service node based on the node deployment field, the server can take the policy of matching the node based on the node deployment field as the node aggregation policy of the service node.

[0104] On this basis, in the process of determining the node deployment field according to the access device type and the node attribute of the service node of each remaining service node sequence, the server can perform the following operations: If the access device type is the first device type, the service scenario field of the service node is taken as the node deployment field. If the access device type is the second device type, the corresponding node deployment field is determined according to the node attribute of the service node.

[0105] The first device type includes a computer device type, and the second device type can include a mobile terminal type, which can be a mobile terminal type other than the computer device type. The node attribute of the service node includes a page access attribute, a module access attribute, a payment attribute, or a component exposure attribute. The module access attribute includes a module exposure attribute or a module click attribute.

[0106] The server determines the node aggregation policy according to the service node parameters of each remaining service node sequence in the plurality of service node sequences. After that, the server can aggregate the service nodes and node links of each remaining service node sequence according to the node aggregation policy to obtain a service node link graph. In this way, the service-related analysis of the target service can be conveniently realized through the service node link graph.

[0107] The service node link graph refers to a service node link graph composed of one or more node links. The same link node in the service node link graph can only appear once. The service node link graph can have a ring structure. Multiple parallel service nodes under the same page node can be arranged in a left-right structure. Multiple serial service nodes under the same page node can be arranged in an up-down structure. Different page nodes can be arranged in a left-right structure. For example Figure 3The service node link diagram shown, one of the node links is to access the medical insurance account query-supplement medical insurance to see-visit medical insurance zone-click to view the details of the insurance, one of the node links is to access my page-supplement medical insurance to see-visit medical insurance zone-click to view the details of the insurance, and the other node link is to access the medical insurance zone-click to supplement medical insurance-access to supplement medical insurance introduction-click to make an appointment for insurance, the node links in the service node link diagram are connected by lines of different colors.

[0108] In specific implementation, in order to avoid the repetition of service nodes in the service node link diagram, so that the service node link diagram is not simple enough, and the clarity of the service node link diagram is improved; in the process of aggregating the service nodes and node links of each remaining service node sequence according to the node aggregation strategy to obtain the service node link diagram, the server can detect the link nodes matched with the service nodes in the link nodes included in the node link according to the node deployment field corresponding to the node type of the service node, and connect the nodes to obtain the service node link diagram. Specifically, the following operations can be performed: Detect the link nodes matched with the service nodes in the link nodes included in the node link according to the node deployment field corresponding to the node type of the service node; Connect the nodes based on the detected link nodes to obtain the service node link diagram.

[0109] On this basis, in order to improve the comprehensiveness of service node aggregation, after the above operation of detecting the link nodes matched with the service nodes in the link nodes included in the node link according to the node deployment field corresponding to the node type of the service node, the server can also construct the link nodes corresponding to the service nodes in the node link according to the node deployment position corresponding to the service page where the service node is located, and connect the nodes to obtain the service node link diagram if no matched link node is detected. Specifically, the following operations can also be performed: If no matched link node is detected, determine the node deployment position in the node link based on the service page where the service node is located; Construct the link nodes corresponding to the service nodes in the node link according to the node deployment position, and connect the nodes to obtain the service node link diagram.

[0110] Among them, the service page where the service node is located refers to the page to which the service node belongs in the target service; the node deployment position refers to the deployment position of the service node in the node link.

[0111] Specifically, the server can detect, in the link nodes included in the node link, a link node having a same node deployment field as the next service node, connect the detected link node with a link node corresponding to the previous service node to obtain a service node link graph, if the detection result is empty, determine a node deployment position in the node link based on a service page where the next service node is located, construct a link node corresponding to the next service node in the node link according to the node deployment position, and connect the constructed link node with a link node corresponding to the previous service node to obtain the service node link graph; that is, for the service nodes of each remaining service node sequence, node matching can be performed in the node link from front to back based on the node deployment field, and if the matching is successful, the matched link node is connected with a link node corresponding to the previous service node to obtain the service node link graph. It should be noted that, in the process of detecting, in the link nodes included in the node link, a link node matching the service node according to the node deployment field corresponding to the node type of the service node, and connecting nodes based on the detected link node to obtain a service node link graph, the server can detect, in the link nodes included in the first node link, a link node having a same node deployment field as the next service node according to the node deployment field corresponding to the node type of the next service node for the first time, connect the detected link node with a link node corresponding to the previous service node to obtain a second node link, if the next service node of the next service node is empty, the server can take the second node link as the service node link graph, if the next service node is not empty, the server can detect, in the link nodes included in the second node link, a link node matching the next service node according to the node deployment field corresponding to the node type of the next service node of the next service node, connect the detected link node with a link node corresponding to the next service node to obtain a third node link, if the next service node of the next service node is empty, take the third node link as the service node link graph, if the next service node of the next service node is not empty, continue to detect and connect the link nodes according to the above execution process until the service node link graph is obtained.

[0112] After the service node and node link of each remaining service node sequence are aggregated according to the node aggregation strategy, the service node link graph is obtained, the server can directly issue the service node link graph to the terminal of the service party, or the server can store the service node link graph, and in the case that the terminal of the service party submits an access request for the service node link graph, the service node link graph can be issued to the terminal; the terminal can obtain the service node link graph of the target service, and render and display the visual component, specifically, the rendering and display of the visual component can be performed at a specific position of an upper layer of the service node link graph, the specific position can be any position, such as an edge position, and the visual component can be a visual panel, a visual board or a visual window, in addition, the visual component can also be other types of components.

[0113] In step S904, the user access data mapped by the visual element is obtained from the server according to the access instruction of the visual element in the service node link graph.

[0114] The triggerable element in the embodiment refers to a link element in the service node link graph that can be triggered, and the triggerable element can include a triggerable link segment and / or a triggerable node in the service node link graph. The user access data mapped by the triggerable element can include at least one of the following: a user churn path of a preceding link node of the triggerable link segment, a user access frequency of a user churn node in the user churn path, user conversion data of the preceding link node of the triggerable link segment, a link segment identifier of the preceding link segment, a user access indicator of the triggerable node, and an access relationship indicator of the triggerable node in the node link. In addition, the triggerable element can also include other types of link elements; and the user access data refers to data related to user access of the target service.

[0115] In specific implementation, the terminal of the service party can obtain the user access data mapped by the visual element from the server according to the access instruction of the visual element in the service node link graph, and the server can query the user access data mapped by the triggerable element and return to the terminal of the service party; specifically, the terminal of the service party can obtain the access instruction of the visual element in the service node link graph submitted by the service party, generate an access request and send it to the server, and the server can query the user access data mapped by the triggerable element based on the access request sent by the terminal and return to the terminal.

[0116] In actual application, the service provider of the target service may have more interaction requirements or access requirements for the service node link graph. In this regard, in order to improve the flexibility of accessing the service node link graph and improve the intuitiveness of user access data of the target service through visualization, the service provider can make further service decisions for the target service based on the visualized user access data; in the process of querying the user access data of the triggerable element mapping, the server can query the user churn path of the pre-link node of the triggerable link segment in the service node link graph and / or the user access times of the user churn node in the user churn path; the following operations can be specifically performed: determining the pre-link node of the triggerable link segment in the service node link graph; querying the user churn path of the pre-link node and the user access times of the user churn node in the user churn path.

[0117] The triggerable link segment refers to the link segment between any two link nodes in the service node link graph, and the pre-link node refers to the link node at the front position of the triggerable link, for example, Figure 3 The link segment 301 between the two link nodes of accessing the medical insurance area and clicking to view the details of the insurance product in the service node link graph shown in the figure is a triggerable link segment, and the pre-link node of the triggerable link segment is the link node of accessing the medical insurance area. The user churn path of the pre-link node refers to the user churn path generated from the pre-link node without user access according to the node link in the service node link graph, that is, the path formed by the user churn direction from the pre-link node. There is one or more user churn nodes in the user churn path, and the user access times of the user churn node can be the number of times the user churn node is accessed.

[0118] Specifically, the service provider can select to view the user churn path graph or view the user conversion trend graph in the access list after submitting the access instruction for the triggerable link segment, and can also select to view the user churn solution or user churn reason analysis.

[0119] In the specific execution process, the user conversion data of the link node in the service node link graph is also crucial. The service provider of the target service can clearly show the user conversion rate based on the user conversion data, so as to provide services that are more in line with the needs of users based on the user conversion rate; in the process of querying the user access data of the triggerable element mapping, the server can also perform the following operations: querying the user conversion data of the pre-link node according to the pre-link node of the triggerable link segment in the service node link graph; and / or, determining the pre-link segment of the triggerable link segment in the service node link graph, and taking the link segment identifier of the pre-link segment as the user access data; And / or, based on the triggerable node corresponding to the access request in the service node link graph, query the user access index of the triggerable node and / or the access relationship index of the triggerable node in the node link.

[0120] In step S906, the visual configuration object is generated based on the user access data, and the visual configuration object is displayed in the visualization component.

[0121] The terminal of the service party can obtain the user access data mapped by the visualization element from the server according to the access instruction of the visualization element in the service node link graph, and the terminal can generate a visual configuration object based on the user access data and display the visual configuration object in the visualization component; wherein the visual configuration object refers to the configuration data of visualization, such as the user churn path graph of the pre-link node, the user conversion trend graph and / or the user access label of the triggerable node, in addition, the visual configuration object can also include the dynamic rendering mark of the pre-link segment.

[0122] Based on the query of the user churn path of the pre-link node and the user access times of the user churn node in the user churn path, the terminal of the service party can construct the user churn path graph of the pre-link node based on the user churn path and / or the user access times, and also display the user churn path graph in the visualization component deployed in the upper layer of the service node link graph; after the terminal of the service party receives the user churn path and the user access times, the following operations are performed: Construct the user churn path graph of the pre-link node based on the user churn path and the user access times; Display the user churn path graph in the visualization component deployed in the upper layer of the service node link graph.

[0123] Further, in order to more clearly show the user churn details such as the user churn proportion of each user churn node in the user churn path, so that the target service can mine the user churn reason from the fine-grained level of the user churn node, thereby improving the user churn situation and improving the user retention rate; in the process of constructing the user churn path graph of the pre-link node based on the user churn path and the user access times, the terminal of the service party can construct the user churn path graph according to the previous user churn node, the next user churn node in the user churn path and the churn boundary information determined based on the user access times, and the specific operations can be performed as follows: According to the user access times of the next user churn node in the user churn path, calculate the churn boundary information of the previous user churn node and the next user churn node; Based on the previous user churn node, the next user churn node and the churn boundary information, construct the user churn path graph.

[0124] The loss boundary information of the previous user loss node and the next user loss node can be a boundary shape of the previous user loss node and the next user loss node, such as a loss height, specifically an up-down height between the previous user loss node and the next user loss node.

[0125] Specifically, in the process of calculating the loss boundary information of the previous user loss node and the next user loss node according to the user access times of the next user loss node in the user loss path, the terminal can calculate the loss boundary shape of the previous user loss node and the next user loss node according to the proportion of the user access times of the next user loss node in the user access times of the previous user loss node, and construct the user loss path graph based on the previous user loss node, the next user loss node, and the loss boundary shape.

[0126] For example, after detecting the access request for the triggerable link segment 301 in the user node link graph, it is determined that the previous link node of the triggerable link segment 301 is the access medical insurance area, the user loss path of the previous link node and the user access times of the user loss nodes in the user loss path are queried, the previous link node is taken as the current link node, the loss boundary shape of the previous link node and the next user loss node is calculated according to the user access times of the next user loss node of the previous link node in the user loss path, the loss boundary is constructed between the previous link node and the next user loss node based on the loss boundary shape, and in the case that the next user loss node exists for the next user loss node of the next user loss node, the loss boundary shape of the next user loss node and the next user loss node is calculated according to the user access times of the next user loss node of the next user loss node, and in the case that the next user loss node does not exist for the next user loss node, the loss boundary is constructed between the next user loss node and the next user loss node based on the loss boundary shape to obtain the user loss path graph as shown in Figure 4 The current node, i.e., the previous link node, is the access commercial insurance area, the next user loss node of the previous link node includes the medical insurance code, the medical insurance channel homepage, the next user loss node of the medical insurance code includes the medical insurance channel homepage, the channel homepage, and the like, the next user loss node of the next user loss node of the access commercial insurance area "medical insurance channel homepage" includes the medical insurance channel homepage, the channel homepage, the next user loss node of the channel homepage includes the homepage, and the loss boundary shape or the loss boundary height between adjacent user loss nodes is calculated based on the user access times of the adjacent user loss nodes.

[0127] After the preceding link node of the triggerable link segment in the service node link graph is determined, and the user conversion data of the preceding link node is queried, the terminal of the service party can generate a user conversion trend graph of the preceding link node based on the user conversion data of the preceding link node of the triggerable link segment in the service node link graph. The user conversion trend graph can be displayed on the visualization component.

[0128] The user conversion data can include the number of user visits to the preceding link node and / or the number of user visits to the previous link node of the preceding link node. The user conversion trend graph can be a user conversion trend graph in a specific time period, for example Figure 5 The user conversion trend graph shown in the above figure is a user conversion trend graph in the last 7 days. The user conversion rate can be displayed in the user conversion trend graph.

[0129] After the preceding link segment of the triggerable link segment in the service node link graph is determined, and the link segment identifier of the preceding link segment is used as the user access data, the terminal of the service party can visually render the preceding link segment corresponding to the link segment identifier in the service node link graph.

[0130] The preceding link segment of the triggerable link segment refers to the link segment before the triggerable link segment in the node link in the service node link graph.

[0131] Specifically, the triggerable link segment can be determined based on the hovering instruction of the service party on the triggerable link segment. In the process of visually rendering the preceding link segment corresponding to the link segment identifier in the service node link graph, the preceding link segment can be visually rendered according to a preset rendering element. Specifically, the preceding link segment can be rendered as a dashed line, and the dashed line can be dynamically displayed. For example, the triggerable link segment is 301 in the above figure, and the preceding link segments of the triggerable link segment are 601, 602 and 603 as shown in the above figure. These preceding link segments are rendered as dashed lines and dynamically displayed. Figure 3 Figure 6

[0132] After the triggerable node corresponding to the access request in the service node link graph is determined, and the user access index of the triggerable node and / or the access relationship index of the triggerable node in the node link are queried, the terminal of the service party can generate a user access label of the triggerable node based on the user access index and / or the access relationship index.

[0133] ​​The user access indicator of the triggerable node can include the number of user accesses of the triggerable node, for example, the user access indicator is pv (page view) and uv (unique visitor); the access relationship indicator of the triggerable node in the node link in which the triggerable node is located is the access relationship indicator of the triggerable node in the node link, and the access relationship indicator can include the user access indicator and / or the user access proportion, and the user access proportion can include the proportion of the user access indicator of the triggerable node in the node link in the total user access indicator of the triggerable node; the terminal of the service party can display the user access label in the visualization component; the access request can be generated based on the hovering instruction of the triggerable node.

[0134] For example Figure 7 As shown, the triggerable node is to click to view the insurance details, the total pv of the triggerable node in the user access label is xx1, the total uv is xx2, the node link in which the triggerable node is located in the service node link diagram is node link 1, so the pv of the triggerable node in the node link 1 is xx3, the uv is xx5, the proportion of the pv of the triggerable node in the node link 1 is xx4, and the proportion of the uv of the triggerable node in the node link 1 is xx6.

[0135] The application of the service processing method provided in the embodiment in the medical service scenario is taken as an example to further illustrate the service processing method provided in the embodiment, and the service processing method applied in the medical service scenario includes the following steps. Figure 10

[0136] In step S1002, the service node link diagram of the medical service is obtained, and the visualization component is rendered and displayed.

[0137] In step S1004, according to the access instruction of the triggerable link segment in the service node link diagram, the user churn path of the front link node of the triggerable link segment and the user access number of the user churn node in the user churn path are obtained from the server.

[0138] In step S1006, the user churn path diagram of the front link node is constructed based on the user churn path and the user access number.

[0139] In step S1008, the user churn path diagram is displayed in the visualization component.

[0140] Optionally, the service node link diagram is obtained after aggregating the node link of the target service node sequence in the plurality of service node sequences and the service nodes of each remaining service node sequence, and the plurality of service node sequences are configured by the service party based on the user access of the target service.

[0141] ​It should be noted that any one of steps S1002 to S1008 or a combination of any multiple steps can be replaced by the corresponding technical means provided in steps S902 to S906 according to the needs of implementation and deployment, and any one of steps S1002 to S1008 or a combination of any multiple steps can be combined into a new implementation manner according to the needs of implementation and deployment; and one or more steps provided in steps S1002 to S1008 form a new implementation manner, which can also be combined with one or more steps provided in steps S902 to S906 according to the actual deployment needs to form a new implementation manner, or combined with one or more optional implementation manners provided in steps S902 to S906 to form a new implementation manner, which will not be described here.

[0142] The service processing apparatus provided in the specification implements, for example: In the above embodiment, a service processing method is provided, and a service processing apparatus corresponding thereto is also provided, which will be described below with reference to the accompanying drawings.

[0143] Reference Figure 11 which shows a schematic diagram of an embodiment of the service processing apparatus provided in the present embodiment.

[0144] Since the apparatus embodiment corresponds to the method embodiment, the description is relatively simple, and the related parts can be referred to the corresponding description of the method embodiment provided above. The apparatus embodiment described below is only illustrative.

[0145] The present embodiment provides a service processing apparatus, which comprises: The sequence acquisition module 1102 is configured to acquire a plurality of service node sequences configured by a service party for user access of a target service; The link construction module 1104 is configured to perform node link construction based on a target service node sequence in the plurality of service node sequences to obtain a node link; The policy determination module 1106 is configured to determine a node aggregation policy according to service node parameters of each remaining service node sequence in the plurality of service node sequences; The aggregation module 1108 is configured to aggregate service nodes of each remaining service node sequence and the node link according to the node aggregation policy to obtain a service node link graph; The data query module 1110 is configured to query user access data mapped by a triggerable element if an access request of the triggerable element in the service node link graph is detected, and return the user access data to a terminal of the service party.

[0146] Another service processing apparatus provided in the specification implements, for example: In the above embodiment, another service processing method is provided, and another service processing device is also provided, which will be described below with reference to the accompanying drawings.

[0147] Referring to Figure 12 It shows a schematic diagram of an embodiment of a service processing device provided by the present embodiment.

[0148] Since the device embodiment corresponds to the method embodiment, it is described more simply, and the relevant part can be referred to the corresponding description of the method embodiment provided above. The device embodiment described below is only illustrative.

[0149] The present embodiment provides a service processing device, comprising: The rendering module 1202 is configured to obtain a service node link graph of a target service, and perform rendering and display of a visualization component; The data acquisition module 1204 is configured to acquire user access data mapped by a visualization element from a server according to an access instruction of the visualization element in the service node link graph; The display module 1206 is configured to generate a visual configuration object based on the user access data, and display the visual configuration object in the visualization component; The service node link graph is obtained after aggregating node links of a target service node sequence in a plurality of service node sequences with service nodes of each remaining service node sequence, and the plurality of service node sequences are configured by a service party for user access of the target service.

[0150] For the convenience of description, the above device is described as various modules or units in terms of functions. Of course, when implementing one or more of the present specification, the functions of each module or unit can be implemented in the same or more software and / or hardware, or the modules implementing the same function can be combined or implemented by a combination of multiple sub-modules or sub-units. The device embodiments described above are only illustrative, for example, the division of the units is only a logical function division, and actual implementation can have another division mode, for example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed.

[0151] The service processing device provided by the present specification is as follows: Corresponding to the above-described service processing method, based on the same technical concept, one or more embodiments of the present specification also provide a service processing device for executing the above-described service processing method, Figure 13 The structure diagram of the service processing device provided by one or more embodiments of the present specification is shown in the following figure.

[0152] This embodiment provides a service processing device, including: like Figure 13 As shown, the service processing device can vary significantly due to differences in configuration or performance. It may include one or more processors 1301 and memory 1302, and the memory 1302 may store one or more application programs or data. The memory 1302 may be temporary or persistent storage. The application programs stored in the memory 1302 may include one or more modules (not shown), each module may include a series of computer-executable instructions in the service processing device. Furthermore, the processor 1301 may be configured to communicate with the memory 1302 and execute the series of computer-executable instructions in the memory 1302 on the service processing device. The service processing device may also include one or more power supplies 1303, one or more wired or wireless network interfaces 1304, one or more input / output interfaces 1305, one or more keyboards 1306, etc.

[0153] In one specific embodiment, the service processing device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for use in the service processing device, and is configured to be executed by one or more processors. The one or more programs include computer-executable instructions for performing the following: Obtain the sequence of multiple service nodes configured by the service provider for user access to the target service; Node links are obtained by constructing node links based on the target service node sequence among the multiple service node sequences; The node aggregation strategy is determined based on the service node parameters of each remaining service node sequence in the plurality of service node sequences. According to the node aggregation strategy, the service nodes of each remaining service node sequence are aggregated with the node links to obtain a service node link graph; If an access request for a triggerable element is detected in the service node link graph, the user access data mapped to the triggerable element is queried and returned to the terminal of the service provider.

[0154] Another embodiment of the service processing device provided in this specification is as follows: Corresponding to the other service processing method described above, based on the same technical concept, one or more embodiments of this specification also provide another service processing device for executing the other service processing method provided above. Figure 14A structural schematic diagram of a service processing device provided for one or more embodiments of the present specification.

[0155] A service processing device provided by the present embodiment comprises: As shown in Figure 14 The service processing device can have great differences due to different configurations or performances, and can include one or more processors 1401 and memories 1402, and one or more storage applications or data can be stored in the memories 1402. The memory 1402 can be temporary storage or persistent storage. The application stored in the memory 1402 can include one or more modules (not shown in the figure), and each module can include a series of computer executable instructions in the service processing device. Further, the processor 1401 can be configured to communicate with the memory 1402 and execute a series of computer executable instructions in the memory 1402 on the service processing device. The service processing device can also include one or more power supplies 1403, one or more wired or wireless network interfaces 1404, one or more input / output interfaces 1405, one or more keyboards 1406, etc.

[0156] In one specific embodiment, the service processing device includes a memory and one or more programs, wherein one or more programs are stored in the memory, and one or more programs can include one or more modules, and each module can include a series of computer executable instructions in the service processing device, and the one or more programs configured to be executed by the one or more processors include computer executable instructions for: Obtaining a service node link diagram of a target service, and rendering and displaying a visualization component; According to the access instruction of the visualization element in the service node link diagram, obtaining user access data mapped by the visualization element from the server; Generating a visual configuration object based on the user access data, and displaying the visual configuration object in the visualization component; The service node link diagram is obtained by aggregating the node link of the target service node sequence in a plurality of service node sequences and the service nodes of each remaining service node sequence, and the plurality of service node sequences are configured by the service side for user access of the target service.

[0157] The computer readable storage medium provided by the present specification can be implemented as follows: According to the above description, a service processing method is provided based on the same technical concept, and one or more embodiments of the present specification also provide a computer readable storage medium.

[0158] The computer readable storage medium provided by the embodiment is used for storing computer executable instructions, and the computer executable instructions realize the following steps when executed: Obtain a plurality of service node sequences configured by a service party for user access of a target service; Construct node links based on a target service node sequence in the plurality of service node sequences to obtain node links; Determine a node aggregation strategy according to service node parameters of each remaining service node sequence in the plurality of service node sequences; Aggregate service nodes of the each remaining service node sequence and the node links according to the node aggregation strategy to obtain a service node link graph; If an access request of a triggerable element in the service node link graph is detected, query user access data mapped by the triggerable element and return to a terminal of the service party.

[0159] It should be noted that the embodiment of the computer readable storage medium in the present specification and the embodiment of the service processing method in the present specification are based on the same inventive concept, and therefore the specific implementation of the embodiment can be referred to the implementation of the corresponding method, and the repeated parts will not be described here.

[0160] Another computer readable storage medium embodiment provided by the present specification is as follows: Corresponding to another service processing method described above, based on the same technical concept, one or more embodiments of the present specification also provide another computer readable storage medium.

[0161] The computer readable storage medium provided by the embodiment is used for storing computer executable instructions, and the computer executable instructions realize the following steps when executed: Obtain a service node link graph of a target service, and render and display a visualization component; According to an access instruction of a visualization element in the service node link graph, obtain user access data mapped by the visualization element from a server; Generate a visual configuration object based on the user access data, and display the visual configuration object in the visualization component; The service node link graph is obtained after aggregating node links of a target service node sequence in a plurality of service node sequences and service nodes of each remaining service node sequence, and the plurality of service node sequences are configured by a service party for user access of the target service.

[0162] It should be noted that the embodiment of the computer program product in the specification is based on the same inventive concept as the embodiment of the service processing method in the specification, and therefore the specific implementation of the embodiment can refer to the implementation of the corresponding method, and the repeated parts will not be described herein.

[0163] The computer program product provided in the specification is implemented as follows: According to the service processing method described above, based on the same technical concept, one or more embodiments of the specification also provide a computer program product.

[0164] A computer program product includes computer programs / instructions that, when executed by a processor, implement the following steps: Obtain a plurality of service node sequences configured by a service party for user access of a target service; Based on a target service node sequence in the plurality of service node sequences, node link construction is performed to obtain a node link; According to the service node parameters of each remaining service node sequence in the plurality of service node sequences, a node aggregation strategy is determined; According to the node aggregation strategy, the service nodes of each remaining service node sequence are aggregated with the node link to obtain a service node link graph; If an access request of a triggerable element in the service node link graph is detected, the user access data mapped by the triggerable element is queried and returned to the terminal of the service party.

[0165] It should be noted that the embodiment of the computer program product in the specification is based on the same inventive concept as the embodiment of the service processing method in the specification, and therefore the specific implementation of the embodiment can refer to the implementation of the corresponding method, and the repeated parts will not be described herein.

[0166] Another computer program product provided in the specification is implemented as follows: According to another service processing method described above, based on the same technical concept, one or more embodiments of the specification also provide another computer program product.

[0167] A computer program product includes computer programs / instructions that, when executed by a processor, implement the following steps: Obtain a service node link graph of a target service, and perform rendering and display of a visual component; According to the access instruction of the visual element in the service node link graph, the user access data mapped by the visual element is obtained from the server; generate a visual configuration object based on the user access data, and perform display of the visual configuration object on the visualization component; The service node link diagram is obtained by aggregating node links of a target service node sequence and service nodes of each remaining service node sequence in a plurality of service node sequences configured by a service provider for user access of the target service.

[0168] It should be noted that the embodiment of another computer program product in the specification is based on the same inventive concept as the embodiment of another service processing method in the specification, and therefore the specific implementation of the embodiment can be referred to the implementation of the corresponding method, and the repeated parts will not be described.

[0169] Each embodiment in the specification is described in a progressive manner, and the same or similar parts between each embodiment can be referred to each other, and each embodiment focuses on the difference from other embodiments, such as the device embodiment, the equipment embodiment and the computer readable storage medium embodiment, which are similar to the method embodiment, so the description is relatively simple, and the related content in the device embodiment, the equipment embodiment and the computer readable storage medium embodiment can be referred to the part of the method embodiment.

[0170] Although the one or more embodiments of the specification provide method steps as described in the embodiments or flowcharts, it can be understood that the order of steps listed in the embodiments or flowcharts is only one of the many execution orders, and does not represent the only execution order, so when the method steps are involved in the claims, the change adjustment of the order of the steps or the parallel between the steps is also within the protection scope of the claims.

[0171] The specification uses specific words to describe the embodiments of the specification. As "one embodiment", "an embodiment", and / or "some embodiments" means a certain feature, structure or characteristic related to at least one embodiment of the specification. Therefore, it should be emphasized and noted that the "an embodiment" or "one embodiment" or "one alternative embodiment" mentioned in different positions in the specification does not necessarily refer to the same embodiment. In addition, the skilled in the art can combine and combine the different embodiments or examples described in the specification and the features of the different embodiments or examples without contradiction.

[0172] The above described embodiments of the present description have been described. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order and still achieve desirable results. Additionally, the processes depicted in the figures do not necessarily require the particular order shown, or sequential order, to achieve the desired results. In certain implementations, multitasking and parallel processing can be advantageous.

[0173] In the 1930s, it was clear to distinguish whether an improvement in a technology was in hardware (e.g., improvement in circuit structure of diodes, transistors, switches, etc.) or in software (e.g., improvement in method flow). However, as technology has evolved, many improvements in method flow today can be considered as direct improvements in hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that an improvement in a method flow cannot be implemented using hardware entity modules. For example, a programmable logic device (PLD) (e.g., a field programmable gate array (FPGA)) is an integrated circuit whose logic function is determined by user programming of the device. A digital system is "integrated" on a PLD by the designer programming it, rather than by ordering a chip manufacturer to design and fabricate a custom integrated circuit chip. Moreover, instead of manually fabricating integrated circuit chips, this programming is now mostly implemented using "logic compiler" software, which is similar to software compilers used in program development, and the original code before compilation is written in a specific programming language, which is called a hardware description language (HDL), and there are many HDLs, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc., and the most commonly used are VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should be aware that only a little logical programming of the method flow in the above-mentioned hardware description languages and programming into an integrated circuit can easily obtain a hardware circuit that implements the logical method flow.

[0174] The controller can be implemented in any suitable way, for example, the controller can take the form of a microprocessor or processor and a computer readable medium storing computer readable program code, such as software or firmware, executable by the (micro)processor, logic gates, switches, an application specific integrated circuit (ASIC), a programmable logic controller and an embedded microcontroller, examples of which include but are not limited to the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20 and Silicone Labs C8051F320, the memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also know that, in addition to implementing the controller in pure computer readable program code, it is also possible to implement the controller in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers and embedded microcontrollers, etc. to perform the same functions by logically programming the method steps. Such a controller can therefore be considered as a hardware component, and the means included therein for performing various functions can also be considered as structures within the hardware component. Alternatively, the means for performing various functions can even be considered as both a software module implementing the method and a structure within the hardware component.

[0175] The systems, apparatuses, modules or units illustrated by the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer can be a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0176] For the sake of description, the above apparatuses are described in various units by functions respectively. Of course, the functions of each unit can be implemented in the same or multiple software and / or hardware in implementing the embodiments of the present specification.

[0177] Those skilled in the art will understand that one or more embodiments of the present specification can be provided as a method, a system or a computer program product. Therefore, one or more embodiments of the present specification can take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present specification can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROMs, optical storage devices, etc.) containing computer usable program code.

[0178] The specification is presented with reference to flow diagrams and / or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the specification. It will be understood that each block of the flow diagrams and / or block diagrams, and combinations of blocks in the flow diagrams and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processing system or other programmable test processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable test processing apparatus, create means for implementing the functions specified in the flow diagrams and / or block diagrams block or blocks. Figure 1 The flow diagram and / or block diagram in the flow diagrams and / or block diagrams can represent one or more of any appropriate circuitry configured to perform the specified functions. In this regard, one or more flow diagrams and / or block diagrams in the flow diagrams and / or block diagrams can represent a device, such as a system, that is configured to perform specified functions, e.g., as described below in the discussion of the flow diagrams and / or block diagrams. Figure 1 The flow diagram and / or block diagram in the flow diagrams and / or block diagrams can represent one or more of any appropriate circuitry configured to perform the specified functions. In this regard, one or more flow diagrams and / or block diagrams in the flow diagrams and / or block diagrams can represent a device, such as a system, that is configured to perform specified functions, e.g., as described below in the discussion of the flow diagrams and / or block diagrams.

[0179] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable test processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instructions which implement the flow diagrams and / or block diagrams flow or flows and / or block or blocks specified in the flow diagrams and / or block diagrams. Figure 1 The flow diagram and / or block diagram in the flow diagrams and / or block diagrams can represent one or more of any appropriate circuitry configured to perform the specified functions. In this regard, one or more flow diagrams and / or block diagrams in the flow diagrams and / or block diagrams can represent a device, such as a system, that is configured to perform specified functions, e.g., as described below in the discussion of the flow diagrams and / or block diagrams. Figure 1 The flow diagram and / or block diagram in the flow diagrams and / or block diagrams can represent one or more of any appropriate circuitry configured to perform the specified functions. In this regard, one or more flow diagrams and / or block diagrams in the flow diagrams and / or block diagrams can represent a device, such as a system, that is configured to perform specified functions, e.g., as described below in the discussion of the flow diagrams and / or block diagrams.

[0180] These computer program instructions can also be loaded into a computer or other programmable test processing apparatus to cause a series of operational steps to be performed on the computer or other programmable test apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable test apparatus provide steps for implementing the flow diagrams and / or block diagrams flow or flows and / or block or blocks specified in the flow diagrams and / or block diagrams. Figure 1 The flow diagram and / or block diagram in the flow diagrams and / or block diagrams can represent one or more of any appropriate circuitry configured to perform the specified functions. In this regard, one or more flow diagrams and / or block diagrams in the flow diagrams and / or block diagrams can represent a device, such as a system, that is configured to perform specified functions, e.g., as described below in the discussion of the flow diagrams and / or block diagrams. Figure 1 Figure 1 The flow diagram and / or block diagram in the flow diagrams and / or block diagrams can represent one or more of any appropriate circuitry configured to perform the specified functions. In this regard, one or more flow diagrams and / or block diagrams in the flow diagrams and / or block diagrams can represent a device, such as a system, that is configured to perform specified functions, e.g., as described below in the discussion of the flow diagrams and / or block diagrams.

[0181] In one typical configuration, the computing device includes one or more processors (CPU's), input / output interfaces, network interfaces, and memory.

[0182] The memory can include non-persistent memory and / or persistent memory, such as flash memory, read-only memory (ROM), and / or the like, combined in one or more memory cards, in a storage device, such as a disk drive, hard drive, or solid state drive with non-volatile memory, or the like. The memory is an example of computer-readable media.

[0183] Computer-readable media includes permanent and non-permanent, movable and non-movable media that can be implemented by any method or technology to store information. The information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassette, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information accessible to a computing device. According to the definition herein, computer-readable media does not include transitory media such as modulated data signals and carriers.

[0184] It should also be noted that the terms "comprising", "containing", or any other variant thereof are intended to encompass non-exclusive inclusion, such that processes, methods, articles or devices that include a series of features are not limited to those features, but also include other features not explicitly listed or inherent to such processes, methods, articles or devices. Without more limitations, the feature defined by the statement "comprising a" does not exclude the presence of other identical features in the process, method, article or device comprising the feature.

[0185] One or more embodiments of the specification can be described in the general context of computer-executable instructions being executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. One or more embodiments of the specification can also be practiced in a distributed computing environment, in which tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules can be located in local and remote computer storage media, including storage devices.

[0186] Each embodiment in the specification is described in a progressive manner, and the same or similar parts between each embodiment can be referred to each other, and each embodiment focuses on the difference from other embodiments. In particular, for system embodiments, since they are basically similar to method embodiments, the description is relatively simple, and the relevant parts can be referred to the part of the method embodiment.

[0187] The above merely provides the example of the present document and is not intended to limit the present document. For those skilled in the art, the present document can have various modifications and changes. Any modification, equivalent replacement, improvement, etc. within the spirit and principle of the present document shall be included in the scope of claims of the present document.

Claims

1. A service processing method, comprising: obtaining a plurality of service node sequences configured by a service party for user access of a target service; constructing a node link based on a target service node sequence in the plurality of service node sequences to obtain a node link; determining a node aggregation strategy according to service node parameters of each remaining service node sequence in the plurality of service node sequences; aggregating service nodes of the each remaining service node sequence and the node link according to the node aggregation strategy to obtain a service node link graph; if an access request of a triggerable element in the service node link graph is detected, querying user access data mapped by the triggerable element and returning to a terminal of the service party. 2.The service processing method of claim 1, wherein the aggregating service nodes of the each remaining service node sequence and the node link according to the node aggregation strategy to obtain a service node link graph comprises: detecting a link node matching the service node from link nodes contained in the node link according to a node deployment field corresponding to a node type of the service node; connecting the link nodes to obtain the service node link graph based on the detected link nodes. 3.The service processing method of claim 1, wherein the querying user access data mapped by the triggerable element comprises: determining a preceding link node of a triggerable link segment in the service node link graph; querying a user churn path of the preceding link node and a user access frequency of a user churn node in the user churn path. 4.The service processing method of claim 3, wherein after the terminal of the service party receives the user churn path and the user access frequency, the terminal performs the following operations: constructing a user churn path graph of the preceding link node based on the user churn path and the user access frequency; displaying the user churn path graph in a visualization component deployed in an upper layer of the service node link graph. 5.The service processing method of claim 4, wherein the constructing a user churn path graph of the preceding link node based on the user churn path and the user access frequency comprises: calculating churn boundary information of a previous user churn node and a next user churn node in the user churn path according to the user access frequency of the next user churn node; constructing the user churn path graph based on the previous user churn node, the next user churn node, and the churn boundary information. 6.The service processing method of claim 1, wherein the querying user access data mapped by the triggerable element comprises: querying user conversion data of a preceding link node of a triggerable link segment in the service node link graph according to the preceding link node; wherein the terminal of the service party generates a user conversion trend graph of the preceding link node based on the user conversion data. 7.The service processing method of claim 1, wherein the querying user access data mapped by the triggerable element comprises: determine a preceding link segment of the triggerable link segment in the service node link graph, and take a link segment identifier of the preceding link segment as the user access data; wherein the terminal of the service party visually renders the preceding link segment corresponding to the link segment identifier in the service node link graph. 8.The service processing method of claim 1, wherein the querying the user access data of the triggerable element mapping comprises: querying a user access indicator of a triggerable node corresponding to the access request in the service node link graph and / or an access relationship indicator of the triggerable node under a node link in which the triggerable node is located; wherein the terminal of the service party generates a user access label of the triggerable node based on the user access indicator and / or the access relationship indicator. 9.The service processing method of claim 1, wherein the determining a node aggregation strategy according to service node parameters of each remaining service node sequence in the plurality of service node sequences comprises: determining a node deployment field according to an access device type and a node attribute of a service node of the each remaining service node sequence; and determining a node aggregation strategy of the service node based on the node deployment field. 10.The service processing method of claim 9, wherein the determining a node deployment field according to an access device type and a node attribute of a service node of the each remaining service node sequence comprises: if the access device type is a first device type, taking a service scenario field of the service node as the node deployment field; and if the access device type is a second device type, determining a corresponding node deployment field according to the node attribute of the service node. 11.The service processing method of claim 2, further comprising, after the sub-step of detecting a matched link node in the link node included in the node link according to the node deployment field corresponding to the node type of the service node: if no matched link node is detected, determining a node deployment position in the node link based on a service page in which the service node is located; and constructing a link node corresponding to the service node in the node link according to the node deployment position and performing node connection to obtain the service node link graph. 12.A service processing method, comprising: obtaining a service node link graph of a target service, and performing rendering and display of a visual component; obtaining user access data of a visual element mapping from a server according to an access instruction of the visual element in the service node link graph; generating a visual configuration object based on the user access data, and displaying the visual configuration object in the visual component; wherein the service node link graph is obtained after aggregating a node link of a target service node sequence in a plurality of service node sequences and service nodes of each remaining service node sequence, and the plurality of service node sequences are configured by a service party for user access of the target service.

13. The service processing method of claim 12, the visual element map user access data comprising: a user churn path of a preceding link node of the triggerable link segment and a user access frequency of a user churn node in the user churn path; and Correspondingly, the generating a visual configuration object based on the user access data comprises: constructing a user churn path graph of the front link node based on the user churn path and the user access times.

14. The service processing method of claim 12, the generating a visual configuration object based on the user access data comprises: generating a user conversion trend graph of the front link node based on the user conversion data of the front link node of the triggerable link segment in the service node link graph.

15. A service processing apparatus comprising: a sequence obtaining module configured to obtain a plurality of service node sequences of a service party for user access configuration of a target service; a link constructing module configured to construct a node link based on a target service node sequence of the plurality of service node sequences to obtain the node link; a strategy determining module configured to determine a node aggregation strategy according to service node parameters of each remaining service node sequence of the plurality of service node sequences; an aggregation module configured to aggregate service nodes of the each remaining service node sequence and the node link according to the node aggregation strategy to obtain a service node link graph; a data querying module configured to, if detecting an access request of a triggerable element in the service node link graph, query user access data mapped by the triggerable element and return the user access data to a terminal of the service party.

16. A service processing apparatus comprising: a rendering module configured to obtain a service node link graph of a target service and perform rendering and display of a visual component; a data obtaining module configured to obtain user access data mapped by a visual element from a server according to an access instruction of the visual element in the service node link graph; a display module configured to generate a visual configuration object based on the user access data and display the visual configuration object in the visual component; wherein the service node link graph is obtained after aggregating a node link of a target service node sequence of a plurality of service node sequences and service nodes of each remaining service node sequence, and the plurality of service node sequences are configured by a service party for user access of the target service.

17. A service processing device comprising: a processor; and a memory configured to store computer executable instructions that, when executed, cause the processor to: obtain a plurality of service node sequences of a service party for user access configuration of a target service; construct a node link based on a target service node sequence of the plurality of service node sequences to obtain the node link; determine a node aggregation strategy according to service node parameters of each remaining service node sequence of the plurality of service node sequences; aggregate service nodes of the each remaining service node sequence and the node link according to the node aggregation strategy to obtain a service node link graph; if detecting an access request of a triggerable element in the service node link graph, query user access data mapped by the triggerable element and return the user access data to a terminal of the service party.

18. A service processing device comprising: a processor; and and a memory configured to store computer-executable instructions that, when executed, cause the processor to: obtain a service node link graph of a target service, and perform rendering and display of a visualization component; obtain user access data mapped to a visualization element from a server according to an access instruction of the visualization element in the service node link graph; generate a visual configuration object based on the user access data, and display the visual configuration object in the visualization component; wherein the service node link graph is obtained after aggregating node links of a target service node sequence in a plurality of service node sequences with service nodes of each remaining service node sequence, the plurality of service node sequences being configured by a service party for user access of the target service. 19.A computer-readable storage medium configured to store computer-executable instructions that, when executed, implement the steps of the method of claim 1 or 12.

Images