Link event guiding method, device, electronic device and storage medium

Abstract

The embodiments of the present disclosure provide a link event guiding method, device, electronic device and computer-readable storage medium, which relate to the field of Internet technology. The link event guiding method includes: sending a link request and receiving a link message in response to the link request; storing event information of the current container in the current data pool; obtaining the current event identifier of the unexecuted current event according to the link message; if the current data pool includes the current event identifier, executing the current event to display the prompt view corresponding to the current event. The solution provided by the embodiments of the present disclosure can improve the versatility of link event execution and can be applied to a variety of scenarios or platforms.

Description

Background Art

[0002] With the development of the Internet, the company's business output ports such as websites, H5 sites (H5 is a collection of technologies for making interactive webpage effects, i.e. H5 is the web page for mobile terminals), and mobile apps (applications) have accumulated functions and businesses for many years, and their functions have become more and more complete, but also more and more complicated and bloated. Although the function entrance is relatively clear and the functions are relatively complete, the functions are relatively independent.

[0003] This phenomenon is particularly evident in applications on mobile devices. Here, we take the mobile APP installed on the mobile device as an example. Therefore, when the user enters a certain page of the APP for the first time, when operating a new function for the first time, the user needs to be guided to operate. However, the function guidance operation in the related technology can only be applied to a single application scenario.

[0004] It should be noted that the information disclosed in the above background technology section is only used to enhance the understanding of the background of the present disclosure, and therefore may include information that does not constitute the prior art known to ordinary technicians in the field. Summary of the invention

[0005] The purpose of the present disclosure is to provide a link event guidance method, device, electronic device and computer-readable storage medium, thereby overcoming the problem of insufficient versatility of function guidance operations due to limitations and defects of related technologies, at least to a certain extent.

[0006] Other features and advantages of the present disclosure will become apparent from the following detailed description, or may be learned in part by the practice of the present disclosure.

[0007] According to one aspect of the present disclosure, a link event guidance method is provided, comprising: sending a link request and receiving a link message in response to the link request; storing event information of a current container in a current data pool; obtaining a current event identifier of an unexecuted current event according to the link message; and if the current event identifier is included in the current data pool, executing the current event to display a prompt view corresponding to the current event.

[0008] According to one aspect of the present disclosure, a link event guiding device is provided, comprising: a link event acquisition module, configured to send a link request and receive a link message in response to the link request; a container event storage module, configured to store event information of a current container in a current data pool; a current event acquisition module, configured to obtain a current event identifier of an unexecuted current event according to the link message; and a link event execution module, configured to execute the current event if the current data pool includes the current event identifier, so as to display a prompt view corresponding to the current event.

[0009] According to one aspect of the present disclosure, an electronic device is provided, comprising: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to execute any one of the link event guiding methods described above by executing the executable instructions.

[0010] According to one aspect of the present disclosure, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the link event guiding method described in any one of the above is implemented.

[0011] In the link event guidance method, device, electronic device and computer-readable storage medium provided by this exemplary embodiment, by sending a link request and receiving a link message in response to the link request, the current event identifier of the current event that has not been executed can be obtained according to the link message, and the event information of the current container is stored in the current data pool, and the current event identifier is compared with the data in the current data pool. If the current data pool includes the current event identifier, the current event can be executed to realize the function of displaying the prompt view corresponding to the current event, that is, the solution provided by the embodiment of the present disclosure, and a set of link platform event guidance solutions that are universal for all platforms and all containers or interfaces (the entire interface or full screen) are designed and developed, which can realize universal guidance services in multiple scenarios.

[0012] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] The accompanying drawings herein are incorporated into the specification and constitute a part of the specification, illustrate embodiments consistent with the present disclosure, and together with the specification are used to explain the principles of the present disclosure. Obviously, the accompanying drawings described below are only some embodiments of the present disclosure, and for ordinary technicians in this field, other accompanying drawings can be obtained based on these accompanying drawings without creative work.

[0014] Figure 1 The system architecture diagram for implementing the method in the exemplary embodiment of the present disclosure is schematically shown.

[0015] Figure 2 The diagram schematically shows a first method in an exemplary embodiment of the present disclosure.

[0016] Figure 3 A specific flow chart for establishing association relationships between events in an exemplary embodiment of the present disclosure is schematically shown.

[0017] Figure 4The following is a schematic diagram schematically showing the method of sending link data in an exemplary embodiment of the present disclosure.

[0018] Figure 5 The following is a schematic diagram schematically showing a second method in an exemplary embodiment of the present disclosure.

[0019] Figure 6 A specific flow chart for implementing function guidance in an exemplary embodiment of the present disclosure is schematically shown.

[0020] Figure 7 A schematic diagram schematically illustrates an operation interface for implementing function guidance in an exemplary embodiment of the present disclosure.

[0021] Figure 8 A block diagram schematically shows a first device in an exemplary embodiment of the present disclosure.

[0022] Fig. 9 A block diagram schematically shows a second device in an exemplary embodiment of the present disclosure.

[0023] Fig.10 A block diagram of a link platform in an exemplary embodiment of the present disclosure is schematically shown.

[0024] Fig.11 The following schematically shows a flow chart of a link event guiding method in an exemplary embodiment of the present disclosure.

[0025] Fig.12 The flowchart schematically shows another link event guiding method in an exemplary embodiment of the present disclosure.

[0026] Fig.13 The flowchart schematically shows another link event guiding method in an exemplary embodiment of the present disclosure.

[0027] Fig.14 Schematically shows the Fig.13 Flowchart of an exemplary embodiment of step S1310.

[0028] Fig.15 Schematically shows the Fig.13 Flowchart of an exemplary embodiment of step S1320.

[0029] Fig.16 Schematically shows the Fig.13 Flowchart of an exemplary embodiment of step S1330.

[0030] Fig.17 A module diagram of a link event guiding device in an exemplary embodiment of the present disclosure is schematically shown.

[0031] Fig.18 A schematic diagram schematically illustrates an electronic device in an exemplary embodiment of the present disclosure.

[0032] Fig.19 A schematic diagram schematically illustrates a computer-readable storage medium in an exemplary embodiment of the present disclosure. DETAILED DESCRIPTION

[0033] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in a variety of forms and should not be construed as being limited to the examples set forth herein; on the contrary, these embodiments are provided so that the present disclosure will be more comprehensive and complete, and the concepts of the example embodiments are fully conveyed to those skilled in the art. The described features, structures, or characteristics may be combined in one or more embodiments in any suitable manner. In the following description, many specific details are provided to provide a full understanding of the embodiments of the present disclosure. However, those skilled in the art will appreciate that the technical solutions of the present disclosure may be practiced while omitting one or more of the specific details, or other methods, components, devices, steps, etc. may be adopted. In other cases, known technical solutions are not shown or described in detail to avoid obscuring various aspects of the present disclosure.

[0034] In addition, the accompanying drawings are only schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the figures represent the same or similar parts, and their repeated description will be omitted. Some of the block diagrams shown in the accompanying drawings are functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities can be implemented in software form, or implemented in one or more hardware modules or integrated circuits, or implemented in different networks and / or processor devices and / or microcontroller devices.

[0035] First, the terms mentioned in the embodiments of the present disclosure are defined and explained.

[0036] Event: The basic unit of sending operation controls.

[0037] Buried event: An event that assigns a value to the event attribute actionID (event identifier).

[0038] Empty event: An event without a value assigned to the event attribute actionID. It can be identified by the field "_nullactionid_".

[0039] Container: A collection of all events in the current interface. In other words, it is impossible to trigger regular events other than containers in the current page, so the modal floating frame is also a container.

[0040] Container interface: The interface drawn together by UI elements in the container.

[0041] Developer mode: The reporting strategy mode used during the development phase.

[0042] Online mode: The mode during the online operation of the background in the APP or website.

[0043] Graph database: a database that stores data in the form of a graph structure. It stores application data in the form of nodes, relationships, and attributes. Just as RDBMS (Relational Database Management System) stores data in the form of "rows and columns" of a table, GDBMS (Generalized Data Base Management System) stores data in the form of a graph.

[0044] Neo4j: is a graph database. It stores structured data on the network instead of in tables. It is an embedded, disk-based, fully transactional Java persistence engine.

[0045] Node: Here refers to a data unit in the graph database.

[0046] Link: A link consists of a set of events that can complete a guidance service. A set of links represents a guidance service. A guidance service represents a meaningful function.

[0047] In the related art, in order to solve the problem of relatively independent functions, guidance operations can be performed through masks (static templates), novice guidance, dynamic guidance, etc. Among them, the mask refers to when the user first enters a relatively complex operation or a new function, a mask pops up to guide the user how to operate. Static templates are often composed of pictures with arrows and instructions to indicate user operations. When the user clicks a certain position according to the prompt, the mask disappears. Novice guidance is to preset the function guidance path in the APP in advance, and enter the guidance process when the user installs it for the first time or triggers it for the first time. Dynamic guidance is a function guidance service system that is dynamically issued by the path server based on function requests. It is used more in game apps. Because the game scenes are relatively fixed, guidance for a certain scene is often provided to newcomers.

[0048] However, although masks and novice guides can realize guidance services, their data is fixed and not flexible enough. Although the data of dynamic guidance services is more flexible, the implementation is not clear enough and the functions are relatively simple. It is a simple functional guidance service. In the implementation of dynamic guidance, the guidance logic and game logic are often written together, and the dynamic guidance is not separated as an independent service.

[0049] In this example implementation, a system architecture for implementing the method is first provided. Figure 1 As shown, the system architecture 100 may include terminal devices 101, 102, 103, a network 104 and a server 105. The network 104 is used to provide a medium for communication links between the terminal devices 101, 102, 103 and the server 105. The network 104 may include various connection types, such as wired, wireless communication links or optical fiber cables, etc.

[0050] The user can use the terminal devices 101, 102, 103 to interact with the server 105 through the network 104 to receive or send request instructions, etc. Various communication client applications can be installed on the terminal devices 101, 102, 103, such as image processing applications, shopping applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc.

[0051] The terminal devices 101 , 102 , and 103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers, and desktop computers.

[0052] The server 105 may be a server that provides various services, such as a backend management server (only an example) that provides support for shopping websites browsed by users using the terminal devices 101, 102, and 103. The backend management server may analyze and process the received data such as product information query requests, and feed back the processing results (such as prompt views - only an example) to the terminal device.

[0053] based on Figure 1 In the system architecture, this example implementation provides a method that can be applied to scenarios such as guiding and recommending complex functions. Figure 2 As shown, the method in this exemplary embodiment is described in detail with the server as the execution subject.

[0054] In step S210, the event corresponding to the user is read according to the event tracking point reported by the client, and the event is reviewed.

[0055] In this exemplary embodiment, event tracking refers to adding event attributes to the controls of the application APP, that is, assigning values ​​to the event attributes. Event refers to the basic unit of sending operation controls. According to the specific functions in the business scenario, the types of events include but are not limited to dynamic events, static events and custom events. Among them: dynamic events refer to events whose functions may change during the online operation of the program, such as different types of entrances to an APP; static events refer to events whose functions will not change during the online program, such as the setting entrance of an APP; custom events refer to events whose functions change due to users, and the custom events corresponding to each user may be different, such as an APP homepage activity or advertising entrance.

[0056] Event attributes include but are not limited to several aspects: event identification number actionID, which is used to ensure uniqueness within the container and is set by the developer. Event type actionType, such as static event, dynamic event, custom event, the default is static event. containerID container identification number, composed of container name + container type containerType. Event level level (first-level entry, second-level entry, etc.). Event function keyword description key, which may include event importance classification (main function, auxiliary description function), and may also include editing rules (the more commonly used, the more important function description is placed in front). Pointers to the next few events nextActions and comments used by developers.

[0057] After completing the event tracking, the client can report the event tracking to the server. The server can receive data reports from the client and organize the received data (event attributes). Specifically, the container identification number containerID and the event identification number actionID in the event attributes can be spliced ​​to form a preset identification number, and the preset identification number is used as a unique ID for the event to avoid duplication. Furthermore, the preset identification number and the received data can also be stored in a temporary database. The temporary database is used for temporary storage, and the data needs to be edited. After the official release, the data will be deleted from the temporary database.

[0058] After receiving the reported data, the event can be read according to the preset identification number and the universal unique identifier, and keywords can be configured for the event. The function of UUID (Universally Unique Identifier) ​​is to represent the unique identification of the user, and each user can correspond to a UUID that does not conflict with others. In this way, an event corresponding to each user can be read according to the preset identification number and UUID. After reading the user's event, the keyword key of the event can be configured according to the corresponding rules. Among them, the corresponding rules can be defined by the user himself according to actual needs, as long as the configured keywords can describe the meaning or significance of the event.

[0059] Further, the event can be audited, specifically referring to judging whether the event is correct according to the function of the reference version and the keyword, and processing the event according to the judgment result. The reference version refers to the latest version to be released by a certain APP. Specifically, the function of the latest version to be released by the APP can be compared, and the received event can be determined according to the keyword of the function of the latest version and the keyword corresponding to the received data to determine whether the received event is correct, so as to process the event according to the judgment result of whether the event is correct. If the event is judged to be incorrect, the incorrect event tracking point is deleted, and the correct event tracking point is released. For example, if the keyword of the event does not match the function of the reference version, the event is determined to be incorrect, and the wrong event tracking point for the event is deleted and updated to the correct event tracking point. If there is an abnormal state such as a broken link or redundancy between the events, the abnormal state of the broken link is reported. For example, if there is a broken link between event 1 and event 2, the situation of the broken link between event 1 and event 2 is supplemented. Similarly, if there is redundancy between event 2 and event 3, the redundant chain between event 2 and event 3 is supplemented. If the event is correct and there is no abnormal state, it is not processed.

[0060] In step S220, a correlation relationship between the reviewed events is established and the correlation relationship is stored in a database.

[0061] In this exemplary embodiment, the association relationship is used to describe the relationship between different events. By establishing the association relationship between the audited events, erroneous events can be avoided, and multiple events can be executed according to the association relationship to provide convenience for users. The database refers to a graph database, which is a database that stores data in the form of a graph structure. It stores the data of the application in the form of nodes, relationships, and attributes. In this exemplary embodiment, the Neo4j graph database is used as an example for explanation.

[0062] Figure 3 A schematic diagram for establishing association relationships between events is shown schematically in FIG. Figure 3 As shown in , the specific steps include:

[0063] In step S310, the database is linked, wherein the database may be, for example, a Neo4j graph database.

[0064] In step S320, a node is created in the database for each event, and an index is created for the node corresponding to each event.

[0065] In this step, a node refers to a data unit in a graph database, and each event can correspond to a node. Specifically, a corresponding node can be created in the graph database for each stored event. Furthermore, a one-to-one index can be created for each node. An index is a separate, physical storage structure that sorts the values ​​of one or more columns in a database table. The index provides pointers to the data values ​​stored in a specified column of the table, and then sorts these pointers according to the sort order you specify. The database uses the index to find a specific value, and then follows the pointer to find the row containing the value. In this exemplary embodiment, the required nodes can be easily found from the database through the index, and then the events can be found based on the nodes.

[0066] In step S330, the sequence of the events is stored, and the association relationship is established between the events according to the sequence.

[0067] In this step, since there is a sequence between events, after one event is executed, the next event is waiting to be executed; when the next event is triggered, the next event will be executed. Therefore, the execution sequence of multiple events can be stored in combination with the index, and then the association relationship between events can be established in the graph database according to the sequence of events.

[0068] By using a graph database to store events and the sequence between events, and then establishing associations between multiple events based on the sequence, the established associations can be made more accurate, thereby facilitating the generation of links.

[0069] In step S230, based on the received link request sent by the client, link data matching the link request is determined in combination with the association relationship in the database and sent to the client, so that the client can perform corresponding functions according to the link data.

[0070] In this exemplary embodiment, a link request refers to a request for determining appropriate link data. Link data is used to represent a group of events that can complete certain functions (such as guidance services, recommendations). In other words, one link data represents a guidance service, and one guidance service represents a function. In this exemplary embodiment, the guidance function is mainly used as an example for description.

[0071] Figure 4 A schematic diagram of determining link data is shown schematically in FIG. Figure 4 As shown in , it specifically includes the following steps S410 to S430, wherein:

[0072] In step S410, an event node matching the link request is determined according to a keyword in the link request.

[0073] In this step, when a link request sent by a client is received, a keyword in the link request, such as keyword 1, may be first obtained. Further, the obtained keyword may be compared with the keyword configured for all events stored in the graph database to determine the event node of the event corresponding to the link request according to whether the keyword matches. For example, if keyword 1 successfully matches keyword 11 of event 1, the event node corresponding to the determined link request may be the node corresponding to event 1.

[0074] In step S420, the node matching degree between the keyword and the keywords of the adjacent nodes of the event node is calculated.

[0075] In this step, the keywords of the adjacent nodes refer to other nodes adjacent to the node of the current event in the graph database, that is, the keywords of the events represented by the adjacent nodes. It should be noted that the number of adjacent nodes can be multiple. For example, event 1 can be used as the current event, and the node of event 1 can be used as the current node, such as keyword 1. The adjacent node can be, for example, node 2, and its corresponding event can be event 2; the adjacent node can also be node 3, and its corresponding event can be event 3; the adjacent node can also be node 4, and its corresponding event can be event 4. Furthermore, the obtained keyword 1 can be compared with the keywords of event 2, event 3 and event 4 to determine the node matching degree between the keywords, and the matching degree here can also be understood as similarity.

[0076] In step S430, a target node is selected according to the node matching degree, and a path between the target node and the current container is determined by a shortest path algorithm to determine the link data.

[0077] In this step, the target node refers to the node that is finally determined. Specifically, the target node can be determined according to the order of matching degree from large to small to ensure the accuracy of the determined target node. For example, the order of matching degree between keyword 1 and the keywords of event 2, event 3 and event 4 from large to small is event 4> event 2> event 3, then the node corresponding to event 4 can be determined as the target node.

[0078] On this basis, the path between the target node and the current container can be calculated. The container refers to the collection of all events in the current interface. In other words, it is impossible to trigger regular events other than the container in the current page. For example, the modal floating frame also belongs to the container. The current container refers to the collection of all events that are associated with the current event. Specifically, it can be based on the shortest path algorithm or the optimal path algorithm, etc. Here, the shortest path algorithm is used as an example for explanation.

[0079] The shortest path algorithm refers to the path starting from a vertex in the graph database and reaching another vertex along the edge of the graph. The path with the smallest sum of weights on each edge is called the shortest path. For this step, the target node refers to a vertex, and the current container refers to another vertex, so a shortest path can be determined. After determining the shortest path, the shortest path can be used as link data corresponding to the link request, and the link data can be sent to the client. In this way, the client can obtain accurate link data and execute corresponding functions according to the accurate link data, such as executing guidance functions, etc., to achieve interoperability and flexibility between functions.

[0080] pass Figure 4 The method in the embodiment can obtain link data that meets the link request by determining the target node and the shortest path, thereby improving the accuracy of determining the link data.

[0081] In addition, this exemplary embodiment also provides another method with the client as the execution subject. Figure 5 As shown, the method in this exemplary embodiment is described in detail.

[0082] In step S510, the event tracking point is reported to the server so that the server creates an association relationship between the events corresponding to the event tracking point.

[0083] In this exemplary embodiment, the event tracking point has been described in step S210 and will not be repeated here. The specific method for the client to report the event tracking point to the server may include the following two methods: First, if the event attribute is a static event, the event is automatically collected according to the click jump operation, and the collected event is reported. That is to say, during the development and debugging process, the clicks, jumps, etc. in the function development process of the developer are automatically collected to complete the collection of static events, and the collected events are reported. This reporting mode can be understood as a developer mode. Second, if the event attribute is the dynamic event or the custom event, the event is collected and reported when the user clicks the event or the container loads the event. That is to say, the reporting of dynamic events and custom events is completed online. When the user enters the container, the container loads the event or the user clicks the event, the event collection task is completed and reported. This reporting mode can be understood as an online mode.

[0084] It should be added that for developer mode and online mode, the information reported when reporting event tracking points is the same, and can include event attributes. For example, the reported information mainly includes actionID, actionType, containerID, and nextActions.

[0085] By reporting event tracking points to the server, the server can read the user's corresponding events based on the event tracking points to establish associations between events. Reporting event tracking points to the server in different ways (developer mode or online mode) can improve the accuracy and efficiency of information reporting.

[0086] In step S520, a link request is determined according to the function type, and the link request is sent to the server to obtain the association relationship and link data corresponding to the link request.

[0087] In this exemplary embodiment, the function type includes but is not limited to a guide function, a game function and a recommendation function. Based on this, determining the link request according to the function type includes the following situations: the first, if it is the guide function, the link request includes an optimal link from the current container to the target function entrance. The target function entrance can be a function to be processed in the next step or a function to be implemented. If it is a guide function, the optimal link data for the current container to reach the target function entrance can be determined according to the steps in step S410 to step S430, that is, a group of events (i.e. link data) to be executed from the container corresponding to the current event to the function entrance to be implemented is determined. The second, if it is the game function, the link request includes multiple link data under the game scene, and the link data is made to meet the needs of continuous jumps under the game scene through conditional data. Wherein, conditional data refers to restriction data. In other words, several link data under a certain game scene can be requested, and some restriction data can be added to make the link data meet the needs of continuous jumps under the game scene. The third type is that if it is the recommended function, the link request includes the optimal path from the current container to the target function entrance, and the optimal path does not exceed four steps. The optimal path here refers to a simplified and fast optimal path from the current container to the target function entrance, and the optimal path does not exceed four steps, so as to achieve fast recommendation through the optimal path.

[0088] After determining the corresponding link request through the function type, the link request can be sent to the server, so that the server can issue the corresponding link data according to the association between the events and the corresponding link request, and further return the link data to the client, so that the client can obtain the link data corresponding to the association and the link request. In this example, the function type can be used to obtain an accurate link request that meets the actual situation, so that the obtained link data can be more accurate.

[0089] In step S530, the link data is parsed, and corresponding functions are executed according to preset rules of the link data.

[0090] In this exemplary embodiment, after obtaining the link data sent by the server, the link data can be parsed to make it meet the format that can be used by the client. Further, the corresponding function can be executed according to the preset rules of the link data. The preset rules refer to: using the unique preset identification number generated by the event identifier actionID and the container identifier containerID as the event ID, and generating a linked list according to the event ID. In this way, the link data can be obtained according to the link composed of the event ID. Based on this, all corresponding events can be executed in sequence according to the event ID contained in the link data, and then the corresponding function is completed by executing the event. By executing the corresponding function according to the preset rules, the order of event execution and the accuracy of event execution can be guaranteed. Specifically, controlling the execution of the corresponding function according to the preset rules of the link data includes: automatically executing the link data according to the preset rules to execute the corresponding function, that is, the client executes multiple events in sequence according to the order of the event ID, thereby realizing the function corresponding to the event in the link data. In addition, the user can also be prompted to execute the link data through a mask to execute the corresponding function. The mask is a special container that covers the current container. The user can be prompted how to operate through the mask, such as using clicks, sliding gestures, etc. You can also add game elements and create game scenes through masks. In addition, you can add richer elements to the masks to improve the user experience.

[0091] In this exemplary embodiment, through the link data, a connection can be established between functions to provide functional intercommunication; in addition, based on the link data, multiple functions can be realized to improve diversity.

[0092] Figure 6 The flowchart for implementing the function guidance is schematically shown. Figure 6 As shown in , it mainly includes the following steps.

[0093] In step S610, the user initiates a function search request, which may be, for example, how to reach "telephone customer service".

[0094] In step S620, the APP provides guidance based on the link data corresponding to the user's search function request.

[0095] In step S630, the user operates according to the instructions of the APP.

[0096] In step S640, the APP reaches the location of the target function entrance desired by the user.

[0097] In this exemplary embodiment, by finding link data corresponding to a function request to guide the user, function guidance can be flexibly implemented and the diversity of functions is improved.

[0098] Figure 7 A schematic diagram of an operation interface for implementing function guidance is shown schematically in FIG. Figure 7 As shown in the figure, the current container is "Customer Service" and the target function required by the user is "Telephone Customer Service". First, the mask can be used to prompt the user to click the location, such as prompting the user to click Figure 7 (A) "Customer Service" and then prompt the user to click Figure 7 (B) "Telephone customer service" can complete the function guidance. It should be noted that the location where the user is prompted to click can be marked, such as by marking with a fixed style, etc. In addition, elements such as clouds, lawns, and puppies can be presented on the operation interface as game elements, and game scenes can be established based on these game elements to improve user experience.

[0099] The present disclosure also provides a device. Figure 8 As shown, the device 800 may include: an event reading module 801 , a relationship establishing module 802 , and a link determining module 803 .

[0100] Among them, the event reading module 801 can be used to read the event corresponding to the user according to the event tracking point reported by the client, and review the event. The relationship establishment module 802 can be used to establish the association relationship between the reviewed events and store the association relationship in the database. The link determination module 803 can be used to determine the link data matching the link request according to the received link request and the association relationship in the database, and send it to the client, so that the client can perform the corresponding function according to the link data.

[0101] The present disclosure also provides another device. Fig. 9 As shown, the device 900 may include: an event tracking reporting module 901, a link request determination module 902 and a function execution module 903.

[0102] Among them, the event embedding reporting module 901 can be used to report the event embedding to the server, so that the server can create an association relationship between the events corresponding to the event embedding. The link request determination module 902 can be used to determine the link request according to the function type, and send the link request to the server to obtain the association relationship and the link data corresponding to the link request. The function execution module 903 can be used to parse the link data and execute the corresponding function according to the preset rules of the link data.

[0103] It should be noted that the specific details of each module in the above device have been described in detail in the corresponding method embodiment, so they will not be repeated here.

[0104] In addition, this exemplary embodiment also provides a link platform system, referring to Fig.10 As shown in , the system 1000 mainly includes a client 1001 and a server 1002. Like general platform services, this platform also has a module for registering an account and registering an application. The following is a detailed introduction to some technical modules of this platform:

[0105] The main functions of the client 1001 include but are not limited to event tracking, reporting event tracking, link request, event link analysis, event link execution and mask display. The main functions of the server 1002 include but are not limited to registering an account, registering an application, and storing it in the general database MySQL, collecting data after reporting event tracking, event review and configuration to obtain the correlation between events and store it in the graphic database neo4j, and event delivery service.

[0106] Based on the link platform, functional modules can be established to provide functional intercommunication and traffic intercommunication. Based on the link platform, in terms of business, function guidance, link games (map games), intelligent recommendation services, and intelligent guidance services can be realized based on the link platform.

[0107] In the above embodiments, although the client can implement relatively flexible and configurable guidance through the link platform service, these ways of guiding user behavior can only implement guidance services in fixed scenarios (such as APP startup page, novice guidance, etc.), and cannot be universal in multiple scenarios (multiple scenarios here refer to that each interface within the application can use the guidance service provided by the disclosed embodiment, such as novice guidance, activity guidance, new function guidance, and all possible function guidance). That is, the application scenario of conventional guidance services is single. The following describes the event execution (guidance plan) in detail using a certain platform as an example.

[0108] Fig.11 A flowchart of a link event guiding method in an exemplary embodiment of the present disclosure is schematically shown. Fig.11As shown, the link event guiding method provided by the embodiment of the present disclosure may include the following steps.

[0109] In step S1110, a link request is sent, and a link message in response to the link request is received.

[0110] In an exemplary embodiment, sending a link request and receiving a link message in response to the link request may include: sending the link request to a server; receiving the link message returned by the server; parsing the link message to generate dictionary data; and storing the dictionary data in a singleton object.

[0111] In step S1120, event information of the current container is stored in the current data pool.

[0112] In an exemplary embodiment, the event information of the current container includes an event identifier and an event pointer of the event of the current container; wherein, storing the event information of the current container in the current data pool may include: setting the current data pool and the backup data pool in the singleton object; collecting the event identifier and the event pointer of the event of the current container; and storing the event identifier and the event pointer of the event of the current container as a key-value pair in the current data pool.

[0113] In step S1130, a current event identifier of the unexecuted current event is obtained according to the link message.

[0114] In step S1140, if the current data pool includes the current event identifier, the current event is executed to display a prompt view corresponding to the current event.

[0115] In an exemplary embodiment, the method may further include: transferring the data in the current data pool to the backup data pool.

[0116] In an exemplary embodiment, the method may further include: if the current data pool does not include the current event identifier, determining whether the backup data pool includes the current event identifier; if the backup data pool includes the current event identifier, executing the current event to display a prompt view corresponding to the current event.

[0117] In an exemplary embodiment, the method may further include: generating an event execution completion notification; and marking the current event as an executed event according to the event execution completion notification.

[0118] In an exemplary embodiment, the method may further include: if the current event is the last event of the link message, generating a link execution completion notification; and clearing the current data pool and the backup data pool according to the link execution completion notification.

[0119] In an exemplary embodiment, executing the current event to display a prompt view corresponding to the current event may include: obtaining a current event pointer corresponding to the current event identifier; obtaining the event type, event position and event size of the current event according to the current event pointer; determining the operation identifier of the prompt view according to the event type of the current event, determining the display position of the prompt view according to the event position, and determining the display size of the prompt view according to the event size.

[0120] In an exemplary embodiment, the prompt view may be a modal view or a non-modal view.

[0121] The link event guidance method provided by the embodiment of the present disclosure sends a link request and receives a link message in response to the link request, so that the current event identifier of the unexecuted current event can be obtained according to the link message, and the event information of the current container is stored in the current data pool, and the current event identifier is compared with the data in the current data pool. If the current data pool includes the current event identifier, the current event can be executed to realize the function of displaying the prompt view corresponding to the current event, that is, the solution provided by the embodiment of the present disclosure, and a set of link platform event guidance solutions that are universal for all platforms and all containers or interfaces (the entire interface or full screen) are designed and developed, which can realize universal guidance services in multiple scenarios.

[0122] Fig.12 The flowchart of another link event guidance method in the exemplary embodiment of the present disclosure is schematically shown. In the embodiment of the present disclosure, the link is composed of events. When the user triggers the guidance in some way (for example, voice, text search, etc. initiates a link request), the client needs to parse the events one by one, and then prompt the user through a certain display method, and finally guide the user behavior. The user operation process is as follows Fig.12 shown.

[0123] In step S1210, the user sees the operation indicator.

[0124] In the disclosed embodiment, the operation mark is a mark that instructs the user how to operate, and can be any one or a combination of a circle, a small hand, an arrow, etc., and the indicator mark has a certain action.

[0125] In step S1220, the user performs an operation according to the identifier.

[0126] In the disclosed embodiment, the user's operation is not limited to clicking, but may also be sliding, double-clicking, etc.

[0127] In step S1230, the user arrives at the designated location.

[0128] Combine the following Figure 13-16 Describe the detailed solution: Link execution (event guidance) is different from conventional static templates and dynamic guidance. It must be processed uniformly for the link to achieve the purpose of applying the same processing logic to multiple scenarios. The event guidance service is separated from the specific business application. As an independent service, the implementation and design must be universal and provide an interface for business implementation. The following is the logic of link execution for a certain platform.

[0129] Fig.13 The flowchart schematically shows another link event guiding method in an exemplary embodiment of the present disclosure.

[0130] like Fig.13 As shown, the link event guiding method provided by the embodiment of the present disclosure may include the following steps.

[0131] In step S1310, the link unit sends a link request to the server, receives a link message returned by the server, and stores the link after parsing the link message.

[0132] In step S1320, the event unit completes the collection of current container events.

[0133] In step S1330 , the execution unit implements the execution operation of the link event.

[0134] In step S1340, the display unit displays a prompt view for the user to operate.

[0135] In the disclosed embodiment, the display unit mainly realizes the display of the prompt view of how the user operates. The execution unit can obtain the current event pointer of the current event to be executed according to the link stored by the link unit and the event information of the current container stored by the event unit, and can obtain the event type, event location and event size of the current event according to the current event pointer.

[0136] Among them, the user is prompted to slide, click, etc. according to the event type. For example: if it is a scroll view type, a slide prompt is displayed, and if it is a button type, a click operation prompt is displayed. The position of the prompt view is displayed according to the event position. The size of the clickable area of ​​the prompt view is displayed according to the event size.

[0137] Specifically, the prompt view can be implemented in the following two ways.

[0138] Prompt view implementation method 1:

[0139] The prompt view is a non-modal view (the area around the prompt view (i.e., the area outside the event display area) is clickable). At this time, when the user clicks the prompt view, the event can be transparently transmitted to the event control corresponding to the link event, so that the event can be executed. At this time, the link unit is notified that the current event has been executed. For example, you can refer to Figure 7 GUI interface, Customer Service->Customer Service Telephone Process.

[0140] Prompt view implementation method 2:

[0141] The prompt view is a modal view (the area outside the prompt view cannot pass events through the system). It can be divided into the following two situations.

[0142] 1) Events can implement a unified action method. If you already know the pointer to the event object, you can use reflection (for example, string reflection function) to call or execute it. For example, events A and B have the same name for their corresponding action events.

[0143] 2) If the event does not implement a unified action method, you can also set the prompt view position to pass the event, while other areas cannot pass the event to achieve transparent transmission of the event, that is, the event has a corresponding position and area on the prompt view. It is clickable only in the area, not outside the area. For example, Figure 7 On the interface, the area outside the circle of the corresponding customer service phone number cannot be clicked. Implementation method: Draw the support and non-support event response areas according to the position and size range of the prompt view and the size of the entire container (current container).

[0144] Fig.14 Schematically shows the Fig.13 Flowchart of an exemplary embodiment of step S1310.

[0145] like Fig.14 As shown, step S1310 provided in the embodiment of the present disclosure may include the following steps.

[0146] In step S1311, the client sends a link request to the server.

[0147] In step S1312, the client parses the link message returned by the server in response to the link request, and converts the link message into dictionary data.

[0148] In the disclosed embodiment, the link message can be parsed using a system method or a third-party framework (such as SBJson (a JSON (JavaScript Object Notation, JS object notation) parser and generator implemented in Objective-C)), etc.), and the purpose of link parsing is to convert the binary link message returned by the server into dictionary data in text format.

[0149] In step S1313, the dictionary data is stored in a singleton object constructed by the singleton pattern, so as to be used when the link is executed later.

[0150] It should be noted that the dictionary data is not limited to being stored in a singleton object constructed by the singleton mode. However, in the disclosed embodiment, because the execution of the link is across containers, it cannot be bound to the container and is not suitable for local storage, which will affect the read and write efficiency and does not require persistent storage.

[0151] In the embodiment of the present disclosure, when a notification of obtaining a link event is received, the event is returned in order from the beginning to the end, and the first event that has not been executed is returned. When the user triggers an event, after the event is executed, the next event execution will be entered (the event is displayed and is in a waiting state for a response). Figure 7 Take the Customer Service->Customer Service Phone number of for example. When the Customer Service button is clicked, the event corresponding to the Customer Service is executed and the Customer Service Phone number event is entered.

[0152] In the disclosed embodiment, when an event execution completion notification is received, the unexecuted event corresponding to the current or event execution completion notification is marked as executed. The event execution engine monitors the execution of each event, and when it is detected that the event execution is completed, the event execution completion notification is sent. Monitoring can be achieved through an event responder chain. The link is composed of events. The execution of the link is one event at a time. Each event can change from an unexecuted state to an executed state.

[0153] Fig.15 Schematically shows the Fig.13 Flowchart of an exemplary embodiment of step S1320. In the disclosed embodiment, the event unit is used to complete the collection of current container events. The implementation of the link platform first tracks the events. The main task of tracking is to associate the event control with the actionID, that is, to add an attribute actionID to the event control. In the process of event collection, the method that is universal to multiple platforms (because the characteristics of a certain platform are not used, the implementation scheme adopts the logic that can be implemented on all platforms) is as follows:

[0154] like Fig.15 As shown, step S1320 provided in the embodiment of the present disclosure may include the following steps.

[0155] In step S1321, the event pointer and actionID of the current container are collected through a global class method.

[0156] In the disclosed embodiment, a class method is a concept in object-oriented programming. A class method can be called globally. Here, the class method takes an event and an actionID as parameters.

[0157] In step S1322, data is saved by adding two dictionary or enumeration type attributes to the singleton object.

[0158] Take adding two dictionaries as an example, one as the current data pool and the other as the backup data pool. The advantage of using dictionaries as storage here is that it is conducive to improving the efficiency of data reading and provides a general event storage and execution solution.

[0159] In step S1323, the event pointer and actionID of the current container are stored in the current data pool.

[0160] In the embodiment of the present disclosure, the storage is performed in a format that takes actionID as key and the event pointer corresponding to actionID as value. The singleton object includes a data pool and provides method support.

[0161] In the disclosed embodiment, when an event execution completion notification is received from the execution unit, the data in the current data pool (referring to the set of all events in the current container that are dynamically collected or saved) is transferred to the backup data pool. The so-called transfer here refers to cutting and copying the data in the current data pool to the backup data pool, that is, the current data pool does not have the data after the transfer. If the current data pool has been backed up, the backup is abandoned. The purpose of processing the data in this way is to meet the needs of the execution unit for the execution operation of the event.

[0162] In the embodiment of the present disclosure, when a link execution completion notification is received from the execution unit, which means that the last event in the link is executed, the current data pool and the backup data pool are cleared.

[0163] Fig.16 Schematically shows the Fig.13 Flow chart of an exemplary embodiment of step S1330. In the embodiment of the present disclosure, the execution unit implements the execution operation of the link event. When the link event is executed, it is executed in a forward-to-backward order. Fig.16 Event 1 and event 2 in the figure are both part of the link. When the last event of the link is completed, the event unit is notified that the link has been completed.

[0164] like Fig.16As shown, step S1330 provided in the embodiment of the present disclosure may include the following steps.

[0165] In step S1331, the link event to be currently executed, for example, event 1, is obtained from the link unit.

[0166] In step S1332, determine whether event 1 is executed; if event 1 is not executed, return to step S1331; if event 1 is executed, obtain the link event to be executed currently from the link unit, such as event 2.

[0167] In the embodiment of the present disclosure, the execution of event 1 in the link is taken as an example for illustration.

[0168] First, determine whether the current data pool in the event unit is empty; if the current data pool is empty, it means that the container where event 1 is located, that is, the current container, is the same container as the previously executed event, because after the previously executed event is completed, the data in the current data pool will be moved to the backup data pool. Therefore, when the next event, that is, event 1 here, is executed again, the current data pool is empty, and the actionID of event 1 is compared with the data key in the backup data pool in the event unit. If the current data pool is not empty, the actionID of event 1 is compared with the data key in the current data pool in the event unit. That is, the current event can be found from different data pools.

[0169] If there is an event with the key corresponding to the actionID of event 1 in the current data pool or the backup data pool, the event data corresponding to the key in event 1 and the event unit are merged and stored in a data model, and then event 1 is passed to the display unit. The data model (a concept in program development) is used to store events, and the event type, event location, event size and other information corresponding to event 1 can be obtained from the event object (an instance of the event data model, used to display or prompt user operations). In addition, the event unit can also be notified that the current event 1 has been executed.

[0170] It should be noted that the event data mentioned here refers to data from two different data sources. One is from the link request and only contains the actionID. The event data in the data pool (current data pool and backup data pool) comes from the events collected locally when the APP is running. It not only contains the actionID, but also the event pointer. Through the event pointer, you can get information such as event location, event size, and event type. The data merging process is actually the process of finding the corresponding event. Find the corresponding event data and then display it for execution.

[0171] If there is no event with the key actionID corresponding to event 1 in the current data pool and the backup data pool, it is caused by an abnormal situation. At this time, the display unit is notified that an abnormality has occurred.

[0172] Fig.17 A module diagram of a link event guiding device in an exemplary embodiment of the present disclosure is schematically shown.

[0173] like Fig.17 As shown, the link event guiding device 1700 provided by the embodiment of the present disclosure may include a link event acquiring module 1710 , a container event storing module 1720 , a current event acquiring module 1730 and a link event executing module 1740 .

[0174] Among them, the link event acquisition module 1710 can be configured to send a link request and receive a link message in response to the link request. The container event storage module 1720 can be configured to store the event information of the current container in the current data pool. The current event acquisition module 1730 can be configured to obtain the current event identifier of the unexecuted current event according to the link message. The link event execution module 1740 can be configured to execute the current event if the current data pool includes the current event identifier to display the prompt view corresponding to the current event.

[0175] In an exemplary embodiment, the link event acquisition module 1710 may include: a link request sending unit, which can be configured to send the link request to the server; a link message receiving unit, which can be configured to receive the link message returned by the server; a link message parsing unit, which can be configured to parse the link message and generate dictionary data; and a link event storage unit, which can be configured to store the dictionary data in a singleton object.

[0176] In an exemplary embodiment, the event information of the current container may include an event identifier and an event pointer of the event of the current container. The container event storage module 1720 may include: a data pool setting unit, which may be configured to set the current data pool and the backup data pool in the singleton object; a container event collection unit, which may be configured to collect the event identifier and the event pointer of the event of the current container; and a container event storage unit, which may be configured to store the event identifier and the event pointer of the event of the current container as a key-value pair in the current data pool.

[0177] In an exemplary embodiment, the link event directing device 1700 may further include: a container event backup module, which may be configured to transfer the data in the current data pool to the backup data pool.

[0178] In an exemplary embodiment, the link event guiding device 1700 may also include: a backup search module, which can be configured to determine whether the backup data pool includes the current event identifier if the current data pool does not include the current event identifier; an event execution module, which can be configured to execute the current event if the backup data pool includes the current event identifier to display a prompt view corresponding to the current event.

[0179] In an exemplary embodiment, the link event guiding device 1700 may further include: an event execution notification generating module, which may be configured to generate an event execution completion notification; and an event status marking module, which may be configured to mark the current event as an executed event according to the event execution completion notification.

[0180] In an exemplary embodiment, the link event guiding device 1700 may also include: a link execution notification generation module, which can be configured to generate a link execution completion notification if the current event is the last event of the link message; a data pool clearing module, which can be configured to clear the current data pool and the backup data pool according to the link execution completion notification.

[0181] In an exemplary embodiment, the link event execution module 1740 may include: an event pointer acquisition unit, which can be configured to acquire a current event pointer corresponding to the current event identifier; an event information acquisition unit, which can be configured to acquire the event type, event position and event size of the current event based on the current event pointer; a prompt view determination unit, which can be configured to determine the operation identifier of the prompt view based on the event type of the current event, determine the display position of the prompt view based on the event position, and determine the display size of the prompt view based on the event size.

[0182] In an exemplary embodiment, the prompt view may be a modal view or a non-modal view.

[0183] It should be noted that the specific details of each module in the above-mentioned link event guiding device have been described in detail in the corresponding link event guiding method embodiment, so they will not be repeated here.

[0184] It should be noted that, although several modules or units of the device for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to the embodiments of the present disclosure, the features and functions of two or more modules or units described above can be embodied in one module or unit. On the contrary, the features and functions of one module or unit described above can be further divided into multiple modules or units to be embodied.

[0185] In addition, although the steps of the method in the present disclosure are described in a specific order in the drawings, this does not require or imply that the steps must be performed in this specific order, or that all the steps shown must be performed to achieve the desired results. Additionally or alternatively, some steps may be omitted, multiple steps may be combined into one step, and / or one step may be decomposed into multiple steps, etc.

[0186] In an exemplary embodiment of the present disclosure, an electronic device capable of implementing the above method is also provided.

[0187] Those skilled in the art will appreciate that various aspects of the present disclosure may be implemented as systems, methods or program products. Therefore, various aspects of the present disclosure may be specifically implemented in the following forms, namely: complete hardware implementation, complete software implementation (including firmware, microcode, etc.), or a combination of hardware and software, which may be collectively referred to herein as "circuits", "modules" or "systems".

[0188] Refer to the following Fig.18 1800 according to this embodiment of the present disclosure is described. Fig.18 The electronic device 1800 shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

[0189] like Fig.18 As shown, the electronic device 1800 is in the form of a general computing device. The components of the electronic device 1800 may include but are not limited to: at least one processing unit 1810, at least one storage unit 1820, and a bus 1830 connecting different system components (including the storage unit 1820 and the processing unit 1810).

[0190] The storage unit stores a program code, which can be executed by the processing unit 1810, so that the processing unit 1810 performs the steps according to various exemplary embodiments of the present disclosure described in the above “Exemplary Method” section of this specification. For example, the processing unit 1810 can perform the following steps: Fig.11 Follow the steps shown in .

[0191] The storage unit 1820 may include a readable medium in the form of a volatile storage unit, such as a random access storage unit (RAM) 18201 and / or a cache storage unit 18202 , and may further include a read-only storage unit (ROM) 18203 .

[0192] The storage unit 1820 may also include a program / utility 18204 having a set (at least one) of program modules 18205, such program modules 18205 including but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment.

[0193] Bus 1830 may represent one or more of several types of bus structures, including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus architectures.

[0194] The display unit 1840 may be a display with a display function, so as to display the processing result obtained by the processing unit 1810 executing the method in this exemplary embodiment through the display. The display includes but is not limited to a liquid crystal display or other displays.

[0195] The electronic device 1800 may also communicate with one or more external devices 2000 (e.g., keyboards, pointing devices, Bluetooth devices, etc.), may also communicate with one or more devices that enable a user to interact with the electronic device 1800, and / or communicate with any device that enables the electronic device 1800 to communicate with one or more other computing devices (e.g., routers, modems, etc.). Such communication may be performed via an input / output (I / O) interface 1850. Furthermore, the electronic device 1800 may also communicate with one or more networks (e.g., a local area network (LAN), a wide area network (WAN), and / or a public network, such as the Internet) via a network adapter 1860. As shown, the network adapter 1860 communicates with other modules of the electronic device 1800 via a bus 1830. It should be understood that, although not shown in the figure, other hardware and / or software modules may be used in conjunction with the electronic device 1800, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0196] Through the description of the above implementation, it is easy for those skilled in the art to understand that the example implementation described here can be implemented by software, or by software combined with necessary hardware. Therefore, the technical solution according to the implementation of the present disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, including several instructions to enable a computing device (which can be a personal computer, a server, a terminal device, or a network device, etc.) to execute the method according to the implementation of the present disclosure.

[0197] In an exemplary embodiment of the present disclosure, a computer-readable storage medium is also provided, on which a program product capable of implementing the above method of the present specification is stored. In some possible implementations, various aspects of the present disclosure may also be implemented in the form of a program product, which includes a program code, and when the program product is run on a terminal device, the program code is used to enable the terminal device to execute the steps according to various exemplary implementations of the present disclosure described in the above "Exemplary Method" section of the present specification.

[0198] refer to Fig.19 As shown, a program product 1900 for implementing the above method according to an embodiment of the present disclosure is described, which can adopt a portable compact disk read-only memory (CD-ROM) and include program code, and can be run on a terminal device, such as a personal computer. However, the program product of the present disclosure is not limited thereto. In this document, a readable storage medium can be any tangible medium containing or storing a program, which can be used by or in combination with an instruction execution system, an apparatus or a device.

[0199] The program product may use any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples (non-exhaustive list) of readable storage media include: an electrical connection with one or more wires, a portable disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0200] Computer readable signal media may include data signals propagated in baseband or as part of a carrier wave, in which readable program code is carried. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Readable signal media may also be any readable medium other than a readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0201] The program code embodied on the readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wired, optical cable, RF, etc., or any suitable combination of the foregoing.

[0202] Program code for performing the operations of the present disclosure may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java, C++, etc., and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user computing device, partially on the user device, as a separate software package, partially on the user computing device and partially on a remote computing device, or entirely on a remote computing device or server. In cases involving a remote computing device, the remote computing device may be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device (e.g., through the Internet using an Internet service provider).

[0203] In addition, the above-mentioned figures are only schematic illustrations of the processes included in the method according to the exemplary embodiments of the present disclosure, and are not intended to be limiting. It is easy to understand that the processes shown in the above-mentioned figures do not indicate or limit the time sequence of these processes. In addition, it is also easy to understand that these processes can be performed synchronously or asynchronously, for example, in multiple modules.

[0204] Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary technical means in the art that are not disclosed in the present disclosure. The specification and examples are to be considered as exemplary only, and the true scope and spirit of the present disclosure are indicated by the claims.

[0205] Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. This application is intended to cover any modification, use or adaptation of the present disclosure, which follows the general principles of the present disclosure and includes common knowledge or customary techniques in the art that are not disclosed in the present disclosure. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present disclosure are indicated by the appended claims.

[0206] It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. A link event guiding method, characterized in that: include: Sending a link request and receiving a link message in response to the link request, which includes: sending the link request to a server; receiving the link message returned by the server; parsing the link message to generate dictionary data; storing the dictionary data in a singleton object; Store the event information of the current container in the current data pool; Acquire a current event identifier of a current event that has not been executed according to the link message; If the current event identifier is included in the current data pool, the current event is executed to display the prompt view corresponding to the current event, which includes: obtaining a current event pointer corresponding to the current event identifier; obtaining the event type, event position and event size of the current event according to the current event pointer; determining the operation identifier of the prompt view according to the event type of the current event, determining the display position of the prompt view according to the event position, and determining the display size of the prompt view according to the event size.

2. The link event guiding method according to claim 1, characterized in that: The event information of the current container includes an event identifier and an event pointer of the event of the current container; wherein the event information of the current container is stored in the current data pool, including: Setting the current data pool and the backup data pool in the singleton object; Collecting event identifiers and event pointers of events of the current container; The event identifier and event pointer of the event of the current container are stored in the current data pool as a key-value pair.

3. The link event guiding method according to claim 2, characterized in that: The method further comprises: The data in the current data pool is transferred to the backup data pool.

4. The link event guiding method according to claim 2, characterized in that: The method further comprises: If the current data pool does not include the current event identifier, determining whether the backup data pool includes the current event identifier; If the backup data pool includes the current event identifier, the current event is executed to display a prompt view corresponding to the current event.

5. The link event guiding method according to claim 2, characterized in that: The method further comprises: Generate event execution completion notification; The current event is marked as an executed event according to the event execution completion notification.

6. The link event guiding method according to claim 2, characterized in that: The method further comprises: If the current event is the last event of the link message, generating a link execution completion notification; According to the link execution completion notification, the current data pool and the backup data pool are cleared.

7. The link event guiding method according to claim 1, characterized in that: The prompt view is a modal view or a non-modal view.

8. A link event guiding device, characterized in that: include: The link event acquisition module is configured to send a link request and receive a link message in response to the link request, which includes: sending the link request to the server; receiving the link message returned by the server; parsing the link message to generate dictionary data; storing the dictionary data in a singleton object; A container event storage module, configured to store event information of a current container in a current data pool; A current event acquisition module, configured to acquire a current event identifier of an unexecuted current event according to the link message; The link event execution module is configured to execute the current event if the current event identifier is included in the current data pool to display the prompt view corresponding to the current event, which includes: obtaining a current event pointer corresponding to the current event identifier; obtaining the event type, event position and event size of the current event according to the current event pointer; determining the operation identifier of the prompt view according to the event type of the current event, determining the display position of the prompt view according to the event position, and determining the display size of the prompt view according to the event size.

9. An electronic device, characterized in that: include: processor; as well as A memory, configured to store executable instructions of the processor; The processor is configured to execute the link event guiding method according to any one of claims 1 to 7 by executing the executable instructions.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the link event guiding method according to any one of claims 1 to 7 is implemented.

Images