CN115374378A - Method and device for generating application navigation service information - Google Patents

Abstract

The present specification provides a method and an apparatus for generating application navigation service information, where the application navigation service information is used to indicate a skip logic between pages included in an application, and the method includes: acquiring page jump data respectively reported by at least one part of clients of the application, wherein the page jump data is generated by the corresponding client in response to a page jump operation implemented by a local user in the application, and the page jump operation is used for triggering a page jump entry to realize page jump; and summarizing the acquired page jump data, and generating the application navigation service information according to the summarized page jump data.

Description

Method and device for generating application navigation service information

Technical Field

The present disclosure relates to the field of internet technologies, and in particular, to a method and an apparatus for generating application navigation service information.

Background

With the rise of mobile applications, more and more functions supported by application programs are increased and the size of the applications is enlarged, and further, a plurality of third-party applications run in the same large-scale application in a form similar to a small program, so that a user can easily realize corresponding functions without additionally downloading the third-party applications. However, when there are a large number of pages in an application to provide different functions, it is difficult for a user to quickly and accurately find a function portal desired by the user.

Disclosure of Invention

In view of the above, the present specification provides a method for generating application navigation service information to solve the deficiencies in the related art.

Specifically, the specification is realized through the following technical scheme:

according to a first aspect of embodiments of the present specification, there is provided a method for generating application navigation service information, where the application navigation service information is used to indicate jump logic between pages included in an application, the method including:

acquiring page jump data respectively reported by at least one part of clients of the application, wherein the page jump data is generated by responding to a page jump operation implemented by a local user in the application by the corresponding client, and the page jump operation is used for triggering a page jump entry to realize page jump;

and summarizing the acquired page jump data, and generating the application navigation service information according to the summarized page jump data.

According to a second aspect of embodiments of the present specification, there is provided an apparatus for generating application navigation service information indicating a logic of jumping between pages included in an application, the apparatus including:

a page jump data obtaining unit, configured to obtain page jump data respectively reported by at least a part of clients of the application, where the page jump data is generated by a corresponding client in response to a page jump operation implemented by a local user in the application, and the page jump operation is used to trigger a page jump entry to implement page jump;

and the navigation service information generating unit is used for summarizing the acquired page jump data and generating the application navigation service information according to the summarized page jump data.

According to a third aspect of embodiments herein, there is provided a computer readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of the method according to the first aspect.

According to a fourth aspect of embodiments herein, there is provided an electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of the method according to the first aspect when executing the program.

In the technical scheme provided by the specification, the application navigation service information is generated by acquiring and summarizing page jump data sent by the application client, so that an application developer does not need to pay extra labor and time cost to acquire and maintain the application navigation service information, the timeliness of the application navigation service information is ensured, and the operation experience of a user is improved.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the specification.

Drawings

Fig. 1 is a schematic structural diagram of an application navigation service information generation system according to an exemplary embodiment of the present specification;

FIG. 2 is a flow diagram illustrating a method of generating application navigation service information in accordance with an exemplary embodiment of the present description;

FIG. 3 is a diagram illustrating a method of generating application navigation service information in accordance with an exemplary embodiment of the present description;

4A-4C are diagrams illustrating a method for generating application navigation service information in the form of a directed tree in accordance with an exemplary embodiment of the present description;

FIG. 5 is a diagram illustrating various functional modules and corresponding functional level navigation service information in accordance with an exemplary embodiment of the present description;

FIG. 6 is a diagram illustrating an application interface jump relationship in an exemplary embodiment of the present description;

FIG. 7 is a schematic block diagram of an electronic device shown in an exemplary embodiment of the present description;

fig. 8 is a schematic structural diagram illustrating an apparatus for generating application navigation service information according to an exemplary embodiment of the present specification.

Detailed Description

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present specification. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the specification, as detailed in the appended claims.

The terminology used in the description herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the description. As used in this specification and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.

It should be understood that although the terms first, second, third, etc. may be used herein to describe various information, these information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, the first information may also be referred to as second information, and similarly, the second information may also be referred to as first information, without departing from the scope of the present specification. The word "if" as used herein may be interpreted as "at" \8230; "or" when 8230; \8230; "or" in response to a determination ", depending on the context.

In the related art, an organization and assurance form is generally adopted, for example, a unified knowledge center is constructed, and related navigation service information is manually collected and maintained, so that a path for entering a certain function entrance is provided for a user. However, when facing a "super application" which has a huge number of users, can carry various third-party applications to run, and is ecologically exploded, the following problems exist in this way: 1. for the super application supporting the running of the independent third-party application, each independent third-party application is developed and operated by an independent organization, the upgrading iteration is concurrent, and meanwhile, when the application of the organization party of the independent third-party application is upgraded, the application navigation service information of the organization party of the independent third-party application cannot be timely and accurately synchronized with the super application; this often results in the user getting the application navigation service information as outdated error information; 2. according to the desire of upgrading the application of the user or the application version condition adapted to the model of the user, the application versions used by different users are often different, and the super application also needs to provide corresponding application navigation service information for users with different versions, so that the management and maintenance of the application navigation service information corresponding to multi-version application are difficult; 3. the independent third-party application may also be a super application, which results in high coupling between the super application and the independent third-party application, and a complicated and inefficient application navigation service information synchronization process.

The application navigation service information may also be referred to as "guide information" for short, and may be used to indicate a jump logic between pages included in an application. For example, according to the application navigation service information of 'home page-setting-personal data-modifying user name', the user can directly know how to quickly and accurately enter a target page related to modifying the user name when browsing the home page, so that the energy and time cost of the user for searching the target page in other unrelated pages are avoided, and the use experience of the user in the application is improved.

To solve the above-described problems in the related art, the present specification provides a scheme of generating application navigation service information, which is implemented based on an application navigation service information generating system such as that shown in fig. 1. Fig. 1 is a schematic structural diagram of an application navigation service information generation system according to an exemplary embodiment of the present disclosure. As shown in fig. 1, may include a client group 11, a server 12.

The client group 11 contains one or more sets of electronic devices hosting any of the applications. In the system operation process, any client in the client group 11 may upload the page data information corresponding to any application to the server 12, and at the same time, may send a problem related to the application navigation service information input by the user to the server 12, and receive the corresponding application navigation service information. Among them, the user can use an electronic device such as the following types as the client: a mobile phone, a tablet device, a notebook computer, a pda (Personal Digital Assistants), a wearable device (such as smart glasses, a smart watch, etc.), and one or more embodiments of the present disclosure are not limited thereto.

The server 12 may be a physical server comprising a separate host, or the server 12 may be a virtual server carried by a cluster of hosts. In the operation process of the system, the server 12 maintains application navigation service information, may generate new application navigation service information according to page jump data from the client group 11, and returns application navigation service information that may solve a problem of application navigation service information initiated by any client in the client group 11. For example: when the client 1 in the client group 11 uploads the page jump data with the posted reimbursement page to the server 12, so that the server 12 generates the application navigation service information "home page-property-reimbursement", and when the client in the client group 11 issues a problem that the content is "i want to reimburse" to the server 12, the server 12 may extract the keyword "reimbursement" from the keyword "by using a natural language processing technology, match the application navigation service information" home page-property-reimbursement "in the existing application navigation service information, and return the matched application navigation service information to the client group 11 in the form of a path.

The technical solution of the present specification is explained below with reference to the embodiment shown in fig. 2. Fig. 2 is a flowchart illustrating a method for generating application navigation service information according to an exemplary embodiment of the present specification, where the application navigation service information is used to indicate jump logic between pages included in an application, as shown in fig. 2, and the method may include the following steps:

s201, page jump data respectively reported by at least a part of the clients of the application are obtained, the page jump data are generated by the corresponding clients in response to the page jump operation implemented in the application by a local user, and the page jump operation is used for triggering a page jump entry to realize page jump.

When the local user executes the page jump operation in the application, the corresponding client can generate page jump data corresponding to the page jump operation and send the page jump data to the server. The page jump operation may be used to trigger a page jump entry of a specific page in the application to realize jumping from the specific page to another page, and the page jump entry may exist in the form of a button, a hyperlink text, or a third-party control, which is not limited in this specification. For example: when a local user clicks a button named 'setup' in the main page of the application, the local user may jump to a corresponding system setup page and generate page jump data for describing the page jump operation. In addition, the time for sending the page jump data to the server is not limited in this specification, and the page jump data may be directly sent after being generated, or may be sent after every other preset period, or may be sent once after being accumulated to a preset number.

The page jump data can be acquired by a data acquisition device related to the client.

In an embodiment, a client is provided with a buried point component, which is a lightweight data component and can be used for collecting page jump operations implemented by a local user in the application and generating corresponding buried point data, i.e., enabling a server to obtain the buried point data respectively reported by the buried point components of at least a part of the clients of the application. The data embedding method comprises the steps of embedding data into a data file, wherein different data fields can be generated according to preset data generation rules in the data embedding data so as to adapt to functional requirements under different use scenes.

In one aspect, the data generation rule at least defines an application identification field, an application version field, a root page field, a current page field, a jump page field, and a page jump entry field. The application identification field is used for representing the identity ID of the application, and the identity ID of each application is globally unique; the application version field is used for representing the version number ID of the application of the currently uploaded buried point data, and the version number ID is unique in the same application and can be customized by an application organization party; the root page field is used to represent the root page ID of the application, i.e. the main page, from which all sub-pages and functions start; the current page field is used for representing a current page ID when the buried point data is uploaded, and because the operation of uploading the buried point data can be triggered when a local user clicks a page jump entry, each page jump entry can be considered to belong to a page, and the ID of the page is the current page ID; the skip page field is used for representing a page id which is skipped after a user clicks a page skip entry; the page jump entry field is used for representing the ID number of the page jump entry clicked by the user, and the ID number is unique in the application and can be customized by the application organization party. It will be understood by those skilled in the art that each page in the application has a globally unique ID, except for the pages corresponding to the root page field, the current page field, and the jumped page field, and that the full path of the page may be used as each page ID.

On the other hand, because the user is hard to perceive and memorize the value of the page jump entry field, the data generation rule can also define the page jump entry name field clicked by the user to improve the readability of the final application navigation service information, for example, the application navigation service information can be displayed to the user in the form of a path "X-Y-Z", wherein X, Y and Z respectively correspond to one page jump entry name field, and the field can enable the user to quickly and accurately find the corresponding page jump entry in the corresponding page. In addition, in the case where the above-mentioned buried point component corresponds to only a specific application, the application version field of the buried point data generated by the application is fixed, and therefore, the generation of the application version field may not be necessary.

Fig. 3 is a diagram illustrating a method of generating application navigation service information in accordance with an exemplary embodiment. The application version number is v1, the application version number includes 4 pages "page1", "page2", "page3" and "page4",6 page jump entries "enter" to "enter f", wherein, assuming that "page1" is the main page of the application, each page is respectively provided with a corresponding page jump entry, and each page jump entry respectively has a unique page jump relationship (i.e. a connection line 1-6 in fig. 3), so that a local user can jump to other uniquely corresponding pages after triggering any page jump entry in a clicking manner and the like.

Taking the generation of the buried point data by a client as an example. The technical solution related to the above embodiment in this specification is explained in detail with reference to fig. 3:

firstly, assuming that the data generation rule defines an application version field, a root page field, a current page field, a page jump entry field and a jump page field, when a local user triggers a page jump entry "enter" in a main interface "page1" in a button clicking manner to jump to "page2", a buried point component in a corresponding client can generate buried point data "< v1, page1, page1, enter a, page2>" according to the page jump operation and the data generation rule to represent a page jump relationship 1, and assuming that the user successively clicks the page jump entries "enter b", "enter c", "enter d", "enter" and "enter f", 5 pieces of similar buried point data can be regenerated to represent a page jump relationship 2-6.

And then, the corresponding client uploads all the generated buried point data to the server together. As will be understood by those skilled in the art, within a particular application, the application identification is fixed, and the application version can be updated continuously over time, so that the "unique buried point data determined according to the application identification and the page jump entry field" can be used as the deduplication logic of the buried point component, so that the buried point component performs deduplication operations on all the buried point data. In other words, once the data of the buried point at the specific page jump inlet under a certain version of the application is successfully uploaded, the data does not need to be uploaded repeatedly subsequently, so that the performance of the client and the occupied network bandwidth are optimized, and meanwhile, when the application is updated and the version number is upgraded, the data of the buried point at the page jump inlet is uploaded again.

S202, summarizing the acquired page jump data, and generating the application navigation service information according to the summarized page jump data.

Even if the page jump data in the same client terminal has been subjected to the duplicate removal operation once, different client terminals may upload the same page jump data, so the server may perform the duplicate removal operation again on the page jump data from different client terminals before summarizing the page jump data uploaded by all the client terminals, so as to ensure the validity of all the contents in the finally obtained page jump data.

The application navigation service information can be represented as different data structures according to actual requirements.

In an embodiment, the application navigation service information may be presented in a form of a character string text, which is similar to a data type of the page jump data, so that a developer does not need to perform further processing operation, and the implementation threshold is low.

In another embodiment, the application navigation service information may be in the form of a directed tree, and page jump entries in pages included in the application are regarded as nodes in the tree structure, and directed edges between the nodes in the tree structure may correspond to page jump relationships between corresponding pages. In this embodiment, since the process of connecting to any node by the root node in the directed tree is similar to the process of accessing to other pages from the main page in the application, the application navigation service information in the form of the directed tree has better readability for developers. Meanwhile, the determination of the jump entry of the target page and the backtracking operation of the functional level navigation service information are facilitated.

In order to facilitate the construction of the application navigation service information in the form of the directed tree, the client may add, to each piece of page jump data, a page identifier of a page before the jump, an entry identifier of a page jump entry included in the page before the jump, and a page identifier of a page after the jump. And the process of generating the application navigation service information is equivalent to establishing corresponding nodes aiming at the entry identifiers contained in the page jump data, generating directed edges pointing to the nodes corresponding to the page jump entries in the page after the jump from the nodes corresponding to the page jump entries in the page before the jump to form a directed graph, and then converting the directed graph into the application navigation service information in a directed tree form.

Fig. 4A-4C are diagrams illustrating a spanning tree format of application navigation service information in accordance with an illustrative embodiment.

Wherein the nodes and edges of the directed graph in FIG. 4A are generated based on the page jump data of FIG. 3.

In the following, the generation of the buried point data by a client is taken as an example. The technical solution related to the foregoing embodiment of "converting a directed graph into application navigation service information in a directed tree form" in this specification is described in detail with reference to fig. 4A to 4C:

first, as shown in fig. 4A, all nodes in the tree are constructed in advance, that is, the page jump entry in fig. 3 is a node of the tree, the entry identifier of the page jump entry is a unique id of the tree node, the above 6 pieces of page jump data are traversed, and entraid-entrfid is taken, so as to finally obtain 6 nodes, and other fields are used as the attached attributes of the nodes. All edges between nodes are constructed simultaneously, i.e., if the contents of the nextPageId field of node enterA is equal to the contents of the curPageId field of node enterB, then node enterA to node enterB will have a directed edge. Since there may be multiple page jump entries in a page, the number of the above directional edges may be greater than or equal to 6. When all edges are constructed, a directed graph is formed as shown in fig. 4A.

Then, as shown in fig. 4B, a virtual root node root is set in the graph, and the root node contains an attribute < version, rootPageId >, wherein the root node points to an enter contained in the rootPageId; based on the embodiment of fig. 3, the root node is < v1, page1Id >, and the root node points to nodes enterA and enterB.

Next, as shown in fig. 4C, the directed graph is converted into a directed tree, that is, the shortest paths from other nodes to the root node are obtained by using the shortest path algorithm of the directed graph, any one of the paths may be selected when the paths are the same, then the edges where the paths are located are retained, and all the remaining edges are deleted from the directed graph, so that the guided tree required by the patent can be obtained. Of course, the present specification does not limit the specific implementation manner of the shortest path algorithm, and those skilled in the art may determine different shortest path algorithms such as Dijkstra (Dijkstra) or florouid (Floyd-Warshall) according to actual situations.

The summary can be divided into sub-module summary and sub-version summary according to different applications and different versions in the same application.

When the application comprises a main function module where the main page is located and at least one slave function module, the server can acquire application navigation service information for each function module based on a sub-module summarizing mode.

In one embodiment, the server can perform sub-module summarization on the acquired page jump data according to the function module to which the server belongs; respectively generating corresponding function level navigation service information aiming at the page jump data corresponding to each function module; establishing a mapping relation between the functional level navigation service information corresponding to the main functional module and the functional level navigation service information corresponding to each slave functional module; the application navigation service information comprises all functional level navigation service information.

Fig. 5 is a diagram illustrating various functional modules and corresponding functional level navigation service information in accordance with an exemplary embodiment.

The application comprises a master function module 510, and slave function modules 520, 530, 540.

In the following, each function module in the application generates corresponding function-level navigation service information as an example. The technical solution related to the above embodiment in this specification is described in detail with reference to fig. 5:

in one embodiment, it is assumed that the server does not have any existing application navigation service information at this time. The server may determine whether the page jump data is from the master function module 510 or the slave function module 520, 530, or 540 according to the application identifier carried in the page jump data. Then when the server receives 4 pieces of page jump data and the 4 pieces of page jump data are respectively from the master function module 510 and the slave function modules 520, 530, and 540, then the server may generate function-level navigation service information 511, 521, 531, 541 respectively corresponding to the master function module 510 and the slave function modules 520, 530, and 540 according to the page jump data. Wherein the root node of the functional level navigation service information of the slave functional modules 520, 530, 540 may be associated with the functional level navigation service information of the corresponding master functional module 510, such that the application navigation service information of the corresponding slave functional modules 520, 530, 540 comprises the functional level navigation service information of the master functional module 510 in addition to the respective functional level navigation service information.

The server can also acquire application navigation service information aiming at each functional module based on a mode of sub-version summarization.

In one embodiment, multiple versions of any functional module may exist. The server can perform version summarizing on the page jump data corresponding to any one functional module; and respectively generating functional level navigation service information corresponding to any functional module aiming at the page jump data of each version.

In the following, the generation of corresponding function-level navigation service information by using multiple versions of function modules in an application is taken as an example. The technical solution related to the above embodiment in this specification is explained in detail with reference to fig. 5:

in one embodiment, it is assumed that the server does not have any existing application navigation service information at this time. The server can judge the version number of the functional module which uploads the page jump data according to the application version information carried in the page jump data. Then, when the server receives 2 pieces of page jump data, and the 2 pieces of page jump data come from the first version "V1" and the second version "V2" of the main function module 510, respectively, then the server may generate the function-level navigation service information 511, 512 corresponding to the "V1" and "V2" versions of the main function module, respectively, according to the page jump data.

The sub-module summarization and the sub-version summarization can be carried out simultaneously, so that the server can return application navigation service information corresponding to different functional modules with different versions in the application aiming at the application navigation request of the local user.

In an embodiment, after receiving an application navigation request initiated by the local user from a main page of an application, the server may determine, according to version information of each function module in the client of the local user, a corresponding candidate set of function level navigation service information, where the candidate set includes all function level navigation service information matched with the version information. And then, according to the attribute information of the page jump entry contained in each piece of functional level navigation service information in the functional level navigation service information candidate set, the server can determine the target page jump entry matched with the query request. Then backtracking in the functional level navigation service information corresponding to the target page jump entry until reaching a root page jump entry in the functional level navigation service information; and the functional level navigation service information does not have a page jump entry which can jump to the page where the root page jump entry is located. The following describes a process of the server processing a search request of a user with reference to the jump relationship of the application interface shown in fig. 6: assuming that at least 5 interfaces 610-650 exist in a certain version of an application, and each page has a corresponding page jump entry to jump the application to another interface, when a local user inputs a problem of "how to reset a password" in a search box 611 of an interface 610, the corresponding client may upload the problem and version information of a master function module and a slave function module of the application to a server, and the server determines all function-level navigation service information matching the version information according to the version information. Meanwhile, the server may extract keywords "reset" and "password" from the above problems according to a natural language processing technique, perform similarity calculation on the page jump entries included in all the functional level navigation service information, and select one or more matched page jump entries according to the similarity, where the server may obtain a "modified password" 631 similar to the page jump entry in the interface 630 according to an algorithm of the similarity calculation.

In an embodiment, if the page where the root page jump entry is located is the main page, responding to the application navigation request according to a path formed in the backtracking process. In the following, the application navigation service information corresponding to the main function module is queried by the local user as an example. The technical solutions in the embodiments mentioned above in this specification are explained in detail with reference to fig. 5 and 6: when two local users a and b use applications including the primary function modules 511 and 512 of the "V1" and "V2" versions respectively and both initiate application navigation requests including primary function module version information and the question "how to exit the account", the server may return a path "primary page-my (i.e., page jump entry 613) -account management (i.e., page jump entry 621) -exit the account (i.e., page jump entry 632)" to the local user a. Assume that the main function module 512 changes the name of the page jump entry 621 of the reimbursement application from "account management" to "account center" after updating. The server may return a path "home page-my-account center-exit the account" to the local user b as a response message to the application navigation request.

If the page where the root page jump inlet is located is not the main page, continuously backtracking in the functional level navigation service information corresponding to the main functional module according to the mapping relation between the functional level navigation service information corresponding to the target page jump inlet and the functional level navigation service information corresponding to the main functional module until the root page jump inlet in the functional level navigation service information is reached; and responding to the application navigation request according to the path formed by the backtracking process. In the following, the example is taken that the local user queries the application navigation service information corresponding to the slave function module. The technical solutions in the embodiments mentioned above in this specification are explained in detail with reference to fig. 5 and 6: assuming that wealth 612 is a third party applet in the application described above, when the local user A uses the master function module 511 containing the "V1" version and the slave function module 533 containing the "V3" version and initiates an application navigation request containing version information for the master function module, the slave function module, and the question "how to reimburse". The server may find a target page jump entry 651 named "reimbursement application" for the function-level navigation service information of the function module, and take a path "main page-bill management (i.e., page jump entry 640) -reimbursement application" formed in the backtracking process of the function-level navigation service information corresponding to the target page jump entry as a first path. And then, according to the mapping relation between the functional level navigation service information corresponding to the target page skip entry and the functional level navigation service information corresponding to the main function module, continuously backtracking in the functional level navigation service information corresponding to the main function module, and obtaining a path 'main page-wealth communication (namely, a page skip entry 612)' formed in the backtracking process as a second path. The final server can return a path 'main page-wealth and wealth communication-bill management-reimbursement application' which is obtained by combining the first path and the second path to the local user A as response information of the application navigation request.

According to the embodiment, the method for generating the application navigation service information in the specification has the advantages that the server can automatically construct the unified knowledge center and maintain the corresponding application navigation service information in a mode of uploading page jump data by the client, manual communication synchronization of an organization side of the application is not relied on, and a large amount of labor cost and time cost are saved. Meanwhile, the application navigation service information in the description can be obtained by summarizing the page jump data, and the function level navigation service information in the application navigation service information can support multiple versions of each function module in the same application, so that a user can accurately obtain a service guide path which accords with the version number of each function module in the application, and the user experience and the application range of the application are improved. Besides the preset data generation rule related in the embedded point assembly, the coupling of the master function module and the slave function module in the application is reduced, so that the modules are independent from each other, do not influence each other, do not depend on any other, and can be automatically and iteratively upgraded.

FIG. 7 is a schematic block diagram of an electronic device in an exemplary embodiment. Referring to fig. 7, at the hardware level, the electronic device includes a processor, an internal bus, a network interface, a memory, and a non-volatile memory, but may also include other required hardware. The processor reads the corresponding computer program from the nonvolatile memory into the memory and runs the computer program to form a device for generating the application navigation service information on a logic level. Of course, besides the software implementation, this specification does not exclude other implementations, such as logic devices or combination of software and hardware, and so on, that is, the execution subject of the following processing flow is not limited to each logic unit, and may be hardware or logic devices.

The present specification also provides an embodiment of an apparatus for generating application navigation service information, corresponding to the aforementioned embodiment of the method for generating application navigation service information.

Referring to fig. 8, fig. 8 is a schematic diagram illustrating a structure of an apparatus for generating application navigation service information according to an exemplary embodiment. As shown in fig. 8, the application navigation service information is used to indicate a jump logic between pages included in the application, and the apparatus may include:

a page jump data obtaining unit 801, configured to obtain page jump data respectively reported by at least a part of clients of the application, where the page jump data is generated by a corresponding client in response to a page jump operation implemented by a local user in the application, and the page jump operation is used to trigger a page jump entry to implement page jump;

and a navigation service information generating unit 802, configured to summarize the obtained page jump data, and generate the application navigation service information according to the summarized page jump data.

Optionally, the client is provided with a buried point component, and the buried point component is configured to collect a page jump operation performed by the local user in the application to generate corresponding buried point data; the page jump data obtaining unit 801 is specifically configured to:

and acquiring buried point data respectively reported by the buried point components of at least one part of the clients of the application.

Optionally, the application navigation service information is in a directed tree form, nodes in the tree structure are page jump entries in pages included in the application, and directed edges between the nodes in the tree structure correspond to page jump relationships between corresponding pages.

Optionally, each piece of page jump data includes a page identifier of a page before the jump, an entry identifier of a page jump entry included in the page before the jump, and a page identifier of a page after the jump; the navigation service information generating unit 802 is specifically configured to:

establishing corresponding nodes aiming at the entry identifiers contained in the page jump data, and generating directed edges pointing to the nodes corresponding to the page jump entries in the page after the jump from the nodes corresponding to the page jump entries in the page before the jump so as to form a directed graph;

and converting the directed graph into the application navigation service information in a directed tree form.

Optionally, the application includes a master function module where the master page is located and at least one slave function module; the navigation service information generating unit 802 is specifically configured to:

according to the function module, the acquired page jump data is summarized in sub-modules;

respectively generating corresponding functional level navigation service information aiming at the page jump data corresponding to each functional module; establishing a mapping relation between the functional level navigation service information corresponding to the main functional module and the functional level navigation service information corresponding to each slave functional module; wherein the application navigation service information comprises all functional level navigation service information.

Optionally, multiple versions exist in any functional module, and the navigation service information generating unit 802 is specifically configured to:

the summarizing the acquired page jump data comprises the following steps: performing version summarizing on the page jump data corresponding to any functional module;

the generating the application navigation service information according to the summarized page jump data comprises the following steps: and respectively generating functional level navigation service information corresponding to any functional module aiming at the page jump data of each version.

Optionally, the apparatus further comprises:

an application navigation request response unit 803, configured to receive an application navigation request initiated by the local user from a main page of the application;

determining a corresponding function level navigation service information candidate set according to the version information of each function module in the client of the local user, wherein the candidate set comprises all function level navigation service information matched with the version information;

determining a target page jump entry matched with the query request according to attribute information of page jump entries contained in each functional level navigation service information in the functional level navigation service information candidate set;

backtracking in the functional level navigation service information corresponding to the target page jump entry until a root page jump entry in the functional level navigation service information is reached; the functional level navigation service information does not have a page jump entry which can jump to a page where the root page jump entry is located;

if the page where the root page jump inlet is located is the main page, responding to the application navigation request according to a path formed in the backtracking process;

if the page where the root page jump inlet is located is not the main page, according to the mapping relation between the functional level navigation service information corresponding to the target page jump inlet and the functional level navigation service information corresponding to the main functional module, continuously backtracking in the functional level navigation service information corresponding to the main functional module until the root page jump inlet in the functional level navigation service information is reached; and responding to the application navigation request according to the path formed by the backtracking process.

Embodiments of the subject matter and the functional operations described in this specification can be implemented in: digital electronic circuitry, tangibly embodied computer software or firmware, computer hardware including the structures disclosed in this specification and their structural equivalents, or a combination of one or more of them. Embodiments of the subject matter described in this specification can be implemented as one or more computer programs, i.e., one or more modules of computer program instructions, encoded on a tangible, non-transitory program carrier for execution by, or to control the operation of, data processing apparatus. Alternatively or additionally, the program instructions may be encoded on an artificially generated propagated signal, e.g., a machine-generated electrical, optical, or electromagnetic signal, that is generated to encode and transmit information to suitable receiver apparatus for execution by the data processing apparatus. The computer storage medium may be a machine-readable storage device, a machine-readable storage substrate, a random or serial access memory device, or a combination of one or more of them.

The processes and logic flows described in this specification can be performed by one or more programmable computers executing one or more computer programs to perform corresponding functions by operating on input data and generating output. The processes and logic flows can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).

Computers suitable for executing computer programs include, for example, general and/or special purpose microprocessors, or any other type of central processing unit. Generally, a central processing unit will receive instructions and data from a read-only memory and/or a random access memory. The basic components of a computer include a central processing unit for implementing or executing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks. However, a computer does not necessarily have such a device. Moreover, a computer may be embedded in another device, e.g., a mobile telephone, a Personal Digital Assistant (PDA), a mobile audio or video player, a game console, a Global Positioning System (GPS) receiver, or a portable storage device such as a Universal Serial Bus (USB) flash drive, to name a few.

Computer-readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media and memory devices, including by way of example semiconductor memory devices (e.g., EPROM, EEPROM, and flash memory devices), magnetic disks (e.g., an internal hard disk or a removable disk), magneto-optical disks, and CD ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.

While this specification contains many specific implementation details, these should not be construed as limitations on the scope of any invention or of what may be claimed, but rather as descriptions of features specific to particular embodiments of particular inventions. Certain features that are described in this specification in the context of separate embodiments can also be implemented in combination in a single embodiment. In other instances, features described in connection with one embodiment may be implemented as discrete components or in any suitable subcombination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.

Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In some cases, multitasking and parallel processing may be advantageous. Moreover, the separation of various system modules and components in the embodiments described above should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.

Thus, particular embodiments of the subject matter have been described. Other embodiments are within the scope of the following claims. In some cases, the actions recited in the claims can be performed in a different order and still achieve desirable results. Further, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some implementations, multitasking and parallel processing may be advantageous.

The above description is only a preferred embodiment of the present disclosure, and should not be taken as limiting the present disclosure, and any modifications, equivalents, improvements, etc. made within the spirit and principle of the present disclosure should be included in the scope of the present disclosure.

Claims (10)

1. A method for generating application navigation service information, wherein the application navigation service information is used for indicating jump logic between pages included in an application, the method comprising:

acquiring page jump data respectively reported by at least one part of clients of the application, wherein the page jump data is generated by the corresponding client in response to a page jump operation implemented by a local user in the application, and the page jump operation is used for triggering a page jump entry to realize page jump;

and summarizing the acquired page jump data, and generating the application navigation service information according to the summarized page jump data.

2. The method according to claim 1, wherein the client is provided with a buried point component for collecting page jump operations performed by the local user within the application to generate corresponding buried point data; the acquiring of the page jump data respectively reported by at least a part of the clients of the application includes:

and acquiring buried point data respectively reported by the buried point components of at least one part of the clients of the application.

3. The method of claim 1, wherein the application navigation service information is in the form of a directed tree, wherein nodes in the tree structure are page jump entries in pages included in the application, and wherein directed edges between nodes in the tree structure correspond to page jump relationships between corresponding pages.

4. The method of claim 3, wherein each piece of page jump data includes a page identifier of a page before the jump, an entry identifier of a page jump entry included in the page before the jump, and a page identifier of a page after the jump; the generating the application navigation service information comprises:

establishing corresponding nodes aiming at the entry identifiers contained in the page jump data, and generating directed edges pointing to the nodes corresponding to the page jump entries in the page after the jump from the nodes corresponding to the page jump entries in the page before the jump so as to form a directed graph;

and converting the directed graph into the application navigation service information in a directed tree form.

5. The method according to claim 1, wherein the application comprises a master function module where a master page is located and at least one slave function module;

the summarizing the acquired page jump data comprises the following steps: according to the function module, the acquired page jump data is summarized in sub-modules;

the generating the application navigation service information according to the summarized page jump data comprises the following steps: respectively generating corresponding functional level navigation service information aiming at the page jump data corresponding to each functional module; establishing a mapping relation between the functional level navigation service information corresponding to the main functional module and the functional level navigation service information corresponding to each slave functional module; wherein the application navigation service information comprises all functional level navigation service information.

6. The method of claim 5, wherein there are multiple versions of any functional module;

the summarizing the acquired page jump data comprises the following steps: performing version-based summarization on page jump data corresponding to any functional module;

the generating the application navigation service information according to the summarized page jump data comprises the following steps: and respectively generating functional level navigation service information corresponding to any functional module aiming at the page jump data of each version.

7. The method of claim 6, further comprising:

receiving an application navigation request initiated by the local user from a main page of the application;

determining a corresponding candidate set of functional level navigation service information according to the version information of each functional module in the client of the local user, wherein the candidate set comprises all functional level navigation service information matched with the version information;

determining a target page jump entry matched with the query request according to attribute information of page jump entries contained in each functional level navigation service information in the functional level navigation service information candidate set;

backtracking in the functional level navigation service information corresponding to the target page jump entry until a root page jump entry in the functional level navigation service information is reached; wherein, the functional level navigation service information does not have a page jump entry which can jump to the page where the root page jump entry is located;

if the page where the root page jump inlet is located is the main page, responding to the application navigation request according to a path formed in the backtracking process;

if the page where the root page jump inlet is located is not the main page, according to the mapping relation between the functional level navigation service information corresponding to the target page jump inlet and the functional level navigation service information corresponding to the main functional module, continuously backtracking in the functional level navigation service information corresponding to the main functional module until the root page jump inlet in the functional level navigation service information is reached; and responding to the application navigation request according to the path formed by the backtracking process.

8. An apparatus for generating application navigation service information, wherein the application navigation service information is used for indicating jump logic between pages included in an application, the apparatus comprising:

a page jump data obtaining unit, configured to obtain page jump data respectively reported by at least a part of clients of the application, where the page jump data is generated by a corresponding client in response to a page jump operation implemented by a local user in the application, and the page jump operation is used to trigger a page jump entry to implement page jump;

and the navigation service information generating unit is used for summarizing the acquired page jump data and generating the application navigation service information according to the summarized page jump data.

9. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 7.

10. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the steps of the method according to any of claims 1 to 7 are performed when the program is executed by the processor.

Images