Page parsing method and device, electronic equipment and computer readable medium

Abstract

Embodiments of the present disclosure disclose a page parsing method and device, electronic equipment and a computer readable medium. A specific embodiment of the method comprises: generating a site identifier of a site corresponding to a target application, wherein the site is associated with each page contained in the target application; constructing a page identifier group according to each page associated with the site, wherein each page contains at least one page resource locator identifier, and each page corresponds to a page identifier in the page identifier group; for each page identifier in the page identifier group, generating a page resource locator identifier relationship table according to the page identifier and the corresponding page resource locator identifier; and generating a page parsing file according to the site identifier and each page resource locator identifier relationship table. The embodiment is related to big data, and can collect batched page resource locator identifier corresponding to the page access point data after the page access point data is collected, thereby improving the efficiency of the page access point data collection.

Description

TECHNICAL FIELD

[0001] Embodiments of the present disclosure relate to the field of computer, in particular to a page parsing method and device, electronic equipment and computer readable medium. BACKGROUND

[0002] In the context of fine operation, customer service, electric sales and other businesses are in the process of digital transformation, and improving work efficiency is a common challenge. Among them, efficiently mining the best work practice is of great significance. And the point is one of the important methods of digital analysis and efficiency improvement. At present, the way of data mining is usually: based on a unified point platform, adding points to each page and each function, and collecting point data through system online.

[0003] However, the above method usually has the following technical problems: due to the complexity of the page resource location identifier URL, the same page may contain different parameters, different routes, different parameter and route orders, and matching various complex URLs will cause the calculation amount to increase exponentially.

[0004] The above information disclosed in this BACKGROUND section is only for the purpose of enhancing the understanding of the background of the present inventive concepts, and therefore, it can contain information that is not prior art known to those of ordinary skill in the art in the country to which this patent belongs. SUMMARY

[0005] The summary of the present disclosure is used to introduce the concepts in a brief form, which will be described in detail in the specific embodiments section. The summary of the present disclosure is not intended to identify key or essential features of the claimed technical solutions, nor is it intended to limit the scope of the claimed technical solutions.

[0006] Some embodiments of the present disclosure propose a page parsing method, device, electronic equipment, computer readable medium and program product to solve the technical problems mentioned in the background section.

[0007] In a first aspect, some embodiments of the present disclosure provide a page parsing method, which comprises: generating a site identifier of a site corresponding to a target application, wherein the site is associated with each page contained in the target application; constructing a page identifier group according to each page associated with the site, wherein each page contains at least one page resource location identifier, and each page corresponds to a page identifier in the page identifier group; for each page identifier in the page identifier group, generating a page resource location identifier relationship table according to the page identifier and the corresponding page resource location identifier; and generating a page parsing file according to the site identifier and each page resource location identifier relationship table.

[0008] Optionally, the above method further includes: connecting the above-mentioned page parsing file to the content delivery network server corresponding to the above-mentioned target application.

[0009] Optionally, the above-mentioned construction of a page identifier group based on the various pages associated with the above-mentioned site includes: recording the page resource location identifiers contained in the various pages into the above-mentioned site; and generating a page identifier for each of the various pages based on the page resource location identifiers recorded in the above-mentioned site for each page.

[0010] Optionally, generating a page resource location identifier relationship table based on the page identifier and the corresponding page resource location identifier includes: determining each page resource location identifier in the site corresponding to the page identifier; performing hash processing on each page resource location identifier to generate a hash page resource location identifier, thus obtaining a hash page resource location identifier group; and performing mapping processing on the page identifier and the hash page resource location identifier group to generate a page resource location identifier relationship table.

[0011] Optionally, the above method further includes: in response to detecting an access operation to a target page, reading a corresponding page parsing file from the content delivery network server based on the site identifier corresponding to the target page, wherein the target page has been integrated with a tracking plugin; determining the access page resource location identifier corresponding to the access operation; determining whether there is a corresponding page resource location identifier relationship table in the various page resource location identifier relationship tables included in the page parsing file; and in response to determining that there is a corresponding page resource location identifier relationship table, uploading the page identifier contained in the page resource location identifier relationship table to an associated page data monitoring system.

[0012] Optionally, the above-mentioned hashing of each page resource location identifier in the various page resource location identifiers to generate a hash page resource location identifier includes: extracting the page resource location path string from the page resource location identifier; grouping each character in the page resource location path string according to a set delimiter character group to generate a page resource location path substring sequence; hashing each page resource location path substring in the page resource location path substring sequence to generate a hash page resource location path substring; and concatenating the generated hash page resource location path substrings to form a hash page resource location identifier.

[0013] Secondly, some embodiments of this disclosure provide a page parsing apparatus, comprising: a first generation unit configured to generate a site identifier for a site corresponding to a target application, wherein the site is associated with various pages included in the target application; a construction unit configured to construct a page identifier group based on the various pages associated with the site, wherein each page contains at least one page resource location identifier, and the pages in each page correspond to page identifiers in the page identifier group; a second generation unit configured to generate a page resource location identifier relationship table for each page identifier in the page identifier group, based on the page identifier and the corresponding page resource location identifier; and a third generation unit configured to generate a page parsing file based on the site identifier and the page resource location identifier relationship table.

[0014] Optionally, the page parsing apparatus further includes an access unit configured to access the page parsing file to the content delivery network server corresponding to the target application.

[0015] Optionally, the building unit is further configured to: input the page resource location identifiers contained in each of the above pages into the above site; and for each of the above pages, generate a page identifier based on the page resource location identifiers input into the above site.

[0016] Optionally, the second generation unit is further configured to: determine each page resource location identifier in the above-mentioned site corresponding to the above-mentioned page identifier; perform hash processing on each of the above-mentioned page resource location identifiers to generate hash page resource location identifiers, thereby obtaining a hash page resource location identifier group; and perform mapping processing on the above-mentioned page identifiers and the hash page resource location identifier group to generate a page resource location identifier relationship table.

[0017] Optionally, the second generation unit is further configured to: extract the page resource location path string from the page resource location identifier; group each character included in the page resource location path string according to the set delimiter character group to generate a page resource location path substring sequence; perform hash processing on each page resource location path substring in the page resource location path substring sequence to generate a hash page resource location path substring; and concatenate the generated hash page resource location path substrings to form a hash page resource location identifier.

[0018] Optionally, the page parsing apparatus further includes: a reading unit configured to, in response to detecting an access operation to a target page, read a corresponding page parsing file from the content delivery network server based on the site identifier corresponding to the target page, wherein the target page has been integrated with a tracking plugin; a first determining unit configured to determine an access page resource location identifier corresponding to the access operation; a second determining unit configured to determine whether there exists a page resource location identifier relationship table corresponding to the access page resource location identifier in the various page resource location identifier relationship tables included in the page parsing file; and an uploading unit configured to, in response to determining the existence of a page resource location identifier relationship table corresponding to the access page resource location identifier, upload the page identifier contained in the page resource location identifier relationship table to an associated page data monitoring system.

[0019] Thirdly, some embodiments of this disclosure provide an electronic device, including: one or more processors; and a storage device having one or more programs stored thereon, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the method described in any implementation of the first aspect above.

[0020] Fourthly, some embodiments of this disclosure provide a computer-readable medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the method described in any of the implementations of the first aspect above.

[0021] Fifthly, some embodiments of this disclosure provide a computer program product, including a computer program that, when executed by a processor, implements the method described in any of the implementations of the first aspect above.

[0022] The above embodiments of this disclosure have the following beneficial effects: the page parsing method of some embodiments of this disclosure reduces the amount of computation and improves the efficiency of data collection. Specifically, the reason for the exponential increase in computation is that, due to the complexity of the page resource location identifier URL, the same page may contain different parameters, different routes, and different parameter and route orders, matching various complex URLs. Based on this, the page parsing method of some embodiments of this disclosure first generates a site identifier for the site corresponding to the target application. The site is associated with each page contained in the target application. Thus, each page corresponding to the target application can be associated with the site in advance before accessing the data collection. This facilitates the establishment of the correspondence between page resource location identifiers and pages. Next, a page identifier group is constructed based on each page associated with the site. Each page contains at least one page resource location identifier, and each page corresponds to a page identifier in the page identifier group. This generates a unique identifier for each page. Then, for each page identifier in the page identifier group, a page resource location identifier relationship table is generated based on the page identifier and the corresponding page resource location identifier. Therefore, a relationship can be established between page resource location identifiers and page identifiers. Leveraging the uniqueness of page identifiers, data from all associated page resource location identifiers can be collected simultaneously during event tracking data collection. This improves the efficiency of page event tracking data collection. Finally, based on the aforementioned relationship table between site identifiers and various page resource location identifiers, a page parsing file is generated. This allows the relationship tables for page resource location identifiers corresponding to each page to be merged into a single file. Consequently, after event tracking is implemented on a page, event tracking data corresponding to page resource location identifiers can be collected in batches, further improving the efficiency of event tracking data collection. Attached Figure Description

[0023] The above and other features, advantages, and aspects of the embodiments of this disclosure will become more apparent from the accompanying drawings and the following detailed description. Throughout the drawings, the same or similar reference numerals denote the same or similar elements. It should be understood that the drawings are schematic, and elements are not necessarily drawn to scale.

[0024] Figure 1 This is a schematic diagram illustrating an application scenario of the page parsing method according to some embodiments of this disclosure;

[0025] Figure 2 This is a flowchart of some embodiments of the page parsing method according to this disclosure;

[0026] Figure 3 These are flowcharts of other embodiments of the page parsing method according to this disclosure;

[0027] Figure 4This is a schematic diagram of the structure of some embodiments of the page parsing apparatus according to the present disclosure;

[0028] Figure 5 This is a schematic diagram of the structure of an electronic device suitable for implementing some embodiments of the present disclosure. Detailed Implementation

[0029] Embodiments of this disclosure will now be described in more detail with reference to the accompanying drawings. While some embodiments of this disclosure are shown in the drawings, it should be understood that this disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this disclosure. It should be understood that the accompanying drawings and embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure.

[0030] It should also be noted that, for ease of description, only the parts relevant to the invention are shown in the accompanying drawings. Unless otherwise specified, the embodiments and features described in this disclosure can be combined with each other.

[0031] It should be noted that the concepts of "first" and "second" mentioned in this disclosure are used only to distinguish different devices, modules or units, and are not used to limit the order of functions performed by these devices, modules or units or their interdependencies.

[0032] It should be noted that the terms "a" and "a plurality of" used in this disclosure are illustrative rather than restrictive, and those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as "one or more".

[0033] The names of messages or information exchanged between multiple devices in the embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of such messages or information.

[0034] This disclosure will now be described in detail with reference to the accompanying drawings and embodiments.

[0035] Figure 1 This is a schematic diagram illustrating an application scenario of a page parsing method according to some embodiments of the present disclosure.

[0036] exist Figure 1In the application scenario, firstly, the computing device 101 can generate a site identifier 102 for the site corresponding to the target application. This site is associated with each page contained in the target application. Next, the computing device 101 can construct a page identifier group 103 based on the pages associated with the site. Each page contains at least one page resource location identifier, and each page corresponds to a page identifier in the page identifier group 103. Then, for each page identifier in the page identifier group 103, the computing device 101 can generate a page resource location identifier relationship table based on the page identifier and its corresponding page resource location identifier. Finally, the computing device 101 can generate a page parsing file 105 based on the relationship table 104 between the site identifier 102 and the page resource location identifiers.

[0037] It should be noted that the aforementioned computing device 101 can be either hardware or software. When the computing device is hardware, it can be implemented as a distributed cluster consisting of multiple servers or terminal devices, or as a single server or a single terminal device. When the computing device is software, it can be installed within the hardware devices listed above. It can be implemented as, for example, multiple software programs or software modules used to provide distributed services, or as a single software program or software module. No specific limitations are made here.

[0038] It should be understood that Figure 1 The number of computing devices shown is merely illustrative. Any number of computing devices can be used depending on implementation needs.

[0039] Continue to refer to Figure 2 The diagram illustrates a flow 200 of some embodiments of a page parsing method according to the present disclosure. This page parsing method includes the following steps:

[0040] Step 201: Generate the site identifier for the site corresponding to the target application.

[0041] In some embodiments, the execution body of the page parsing method (e.g., Figure 1The computing device 101 shown can generate a site identifier for the site corresponding to the target application. The site is associated with each page contained in the target application. Here, the target application can refer to the application for which data collection is to be performed. The site can be a storage area established by the executing entity corresponding to the target application. For example, a site can be divided into parent and child sites (sites and virtual directories), and the website structure can be designed according to requirements through site management. The site identifier can uniquely identify the site. Here, the executing entity of the page parsing method can be a system used for data collection. That is, a site corresponding to the target application can be created in the data collection system, and a site identifier can be generated. Here, the method of generating the site identifier is not limited. For example, it can be generated based on the application name of the target application. Then, each page contained in the target application can be associated under this site. For example, page path information can be associated with the pages under this site.

[0042] Step 202: Construct page identifier groups based on the pages associated with the above-mentioned sites.

[0043] In some embodiments, the aforementioned entity can construct a page identifier group based on the various pages associated with the aforementioned site. Each page contains at least one page resource locator identifier, and the pages within each page correspond to the page identifiers in the aforementioned page identifier group. That is, the aforementioned executing entity can directly generate a page identifier corresponding to each page. The page identifier can uniquely identify the page. The page resource locator identifier can refer to a resource locator (URL) within the page.

[0044] In some optional implementations of certain embodiments, the aforementioned execution entity may construct a page identifier group through the following steps:

[0045] The first step is to input the page resource location identifiers contained in each of the above pages into the above site. It should be noted that the input page resource location identifiers can be part of multiple page resource location identifiers contained in the page; or all page resource location identifiers; and certain paths or parameters in the page resource location identifiers can be set as variable parts. The areas set as variable parts can match any valid page resource location identifier value (URL value).

[0046] The second step is to generate a page identifier for each of the aforementioned pages, based on the page resource location identifiers entered into the aforementioned site. In other words, the aforementioned page resource location identifiers can be combined into a page identifier.

[0047] Step 203: For each page identifier in the above page identifier group, generate a page resource location identifier relationship table based on the above page identifier and the corresponding page resource location identifier.

[0048] In some embodiments, the execution entity may generate a page resource location identifier relationship table for each page identifier in the page identifier group, based on the page identifier and its corresponding page resource location identifier. That is, the page identifier can be mapped to each page resource location identifier included in the page corresponding to that page identifier to generate the page resource location identifier relationship table.

[0049] In some optional implementations of certain embodiments, the aforementioned execution entity may generate a page resource location identifier relationship table through the following steps:

[0050] The first step is to determine the resource location identifiers for each page in the aforementioned sites that correspond to the aforementioned page identifiers. That is, to determine the resource location identifiers for each page in the aforementioned sites that correspond to the aforementioned page identifiers.

[0051] The second step is to perform hash processing on each of the above page resource location identifiers to generate hash page resource location identifiers, thus obtaining a hash page resource location identifier group.

[0052] In practice, the second step above may include the following sub-steps:

[0053] The first sub-step involves extracting the page resource location path string from the aforementioned page resource location identifier. Here, the page resource location identifier can contain both the URL domain and the page resource location path string. For example, the page resource location identifier could be "https: / / xxx.xxx.xxx / path1 / :path2 / # / demo / :test?par1=d". And the page resource location path string could be " / path1 / :path2 / # / demo / :test?par1=d".

[0054] The second sub-step involves grouping the characters in the aforementioned page resource location path string according to the defined delimiter character groups to generate a sequence of page resource location path substrings. Here, the defined delimiter character groups can be pre-defined delimiter characters. For example, the delimiter character groups could be "?#:&=". For instance, the page resource location path string " / path1 / :path2 / # / demo / :test?par1=d" can be divided into " / path1 / ", ":path2 / ", "# / demo / ", ":test", "?par1", and "=d".

[0055] The third sub-step involves hashing each page resource location path substring in the above sequence to generate a hashed page resource location path substring. This hashing can be performed using a hash algorithm.

[0056] The fourth sub-step involves concatenating the generated hash page resource location path substrings into a hash page resource location identifier.

[0057] The third step is to map the aforementioned page identifiers to the hash page resource location identifier groups to generate a page resource location identifier relationship table. Here, mapping can refer to association linking.

[0058] Step 204: Generate a page parsing file based on the above table showing the relationship between site identifiers and resource location identifiers for each page.

[0059] In some embodiments, the execution entity can generate a page parsing file based on the relationship table between the site identifier and each page resource location identifier. That is, an empty page parsing file can be constructed with the site identifier as the filename. Then, the relationship table of each page resource location identifier is added to the empty page parsing file to obtain the page parsing file. Here, the page parsing file can be a JSON format configuration file.

[0060] The above embodiments of this disclosure have the following beneficial effects: the page parsing method of some embodiments of this disclosure reduces the amount of computation and improves the efficiency of data collection. Specifically, the reason for the exponential increase in computation is that, due to the complexity of the page resource location identifier URL, the same page may contain different parameters, different routes, and different parameter and route orders, matching various complex URLs. Based on this, the page parsing method of some embodiments of this disclosure first generates a site identifier for the site corresponding to the target application. The site is associated with each page contained in the target application. Thus, each page corresponding to the target application can be associated with the site in advance before accessing the data collection. This facilitates the establishment of the correspondence between page resource location identifiers and pages. Next, a page identifier group is constructed based on each page associated with the site. Each page contains at least one page resource location identifier, and each page corresponds to a page identifier in the page identifier group. This generates a unique identifier for each page. Then, for each page identifier in the page identifier group, a page resource location identifier relationship table is generated based on the page identifier and the corresponding page resource location identifier. Therefore, a relationship can be established between page resource location identifiers and page identifiers. Leveraging the uniqueness of page identifiers, data from all associated page resource location identifiers can be collected simultaneously during event tracking data collection. This improves the efficiency of page event tracking data collection. Finally, based on the aforementioned relationship table between site identifiers and various page resource location identifiers, a page parsing file is generated. This allows the relationship tables for page resource location identifiers corresponding to each page to be merged into a single file. Consequently, after event tracking is implemented on a page, event tracking data corresponding to page resource location identifiers can be collected in batches, further improving the efficiency of event tracking data collection.

[0061] Continue to refer to Figure 3 , Figure 3 A flow 300 of another embodiment of the page parsing method according to this disclosure is shown. The page parsing method includes the following steps:

[0062] Step 301: Generate the site identifier for the site corresponding to the target application.

[0063] Step 302: Construct page identifier groups based on the pages associated with the above-mentioned sites.

[0064] Step 303: For each page identifier in the above page identifier group, generate a page resource location identifier relationship table based on the above page identifier and the corresponding page resource location identifier.

[0065] Step 304: Generate a page parsing file based on the above table showing the relationship between site identifiers and resource location identifiers for each page.

[0066] In some embodiments, the content of steps 301-304 is the same as that of steps 201-204, and will not be described in detail here.

[0067] Step 305: Connect the above-mentioned page parsing file to the content delivery network server corresponding to the target application.

[0068] In some embodiments, the execution body of the page parsing method (e.g., Figure 1 The computing device 101 shown can connect the aforementioned page parsing file to the content delivery network server corresponding to the target application. The content delivery network server can refer to a CDN (Content Delivery Network) server, that is, the CDN server for the target application. In practice, Lua scripting language combined with Nginx can be used to connect the aforementioned page parsing file to the CDN server.

[0069] Step 306: In response to the detection of an access operation to the target page, the corresponding page parsing file is read from the content delivery network server according to the site identifier corresponding to the target page.

[0070] In some embodiments, the execution entity may, in response to detecting an access operation to the target page, read the corresponding page parsing file from the content delivery network server based on the site identifier corresponding to the target page. The target page is integrated with a tracking plugin. The tracking plugin may refer to a JavaScript SDK plugin. The access operation may refer to a user's selection operation to access the page. For example, access can be made by clicking on a page in the target application. The site identifier corresponding to the target page may be a site identifier set when integrating the tracking plugin, or it may be a pre-defined site identifier. That is, the page parsing file corresponding to the site identifier can be read from the content delivery network server.

[0071] Step 307: Determine the resource location identifier of the access page corresponding to the above access operation.

[0072] In some embodiments, the executing entity may determine the access page resource location identifier corresponding to the access operation. That is, the page resource location identifier triggered by the access operation is the access page resource location identifier.

[0073] Step 308: Determine whether there exists a corresponding page resource location identifier relationship table in the various page resource location identifier relationship tables included in the above-mentioned page parsing file.

[0074] In some embodiments, the executing entity may determine whether a page resource location identifier relationship table corresponding to the accessed page resource location identifier exists in the various page resource location identifier relationship tables included in the page parsing file. First, the accessed page resource location identifier may be hashed to generate a hashed accessed page resource location identifier. Then, it may be determined whether a page resource location identifier relationship table included in the various page resource location identifier relationship tables of the page parsing file contains a table containing a hashed page resource location identifier that is identical to the hashed accessed page resource location identifier.

[0075] Step 309: In response to determining that a page resource location identifier relationship table exists corresponding to the aforementioned accessed page resource location identifier, the page identifier contained in the aforementioned page resource location identifier relationship table is uploaded to the associated page data monitoring system.

[0076] In some embodiments, the executing entity may, in response to determining the existence of a page resource location identifier relationship table corresponding to the accessed page resource location identifier, upload the page identifier contained in the page resource location identifier relationship table to an associated page data monitoring system. Here, the associated page data monitoring system may refer to a monitoring server communicatively connected to the executing entity.

[0077] from Figure 3 It can be seen from this that, with Figure 2 Compared to the description of some corresponding embodiments, Figure 3 In some corresponding embodiments, the page parsing method process 300 can quickly determine the page identifier based on the page access operation. Therefore, the page resource location identifier relationship table can be used to collect data from the pages corresponding to the page identifier in batches.

[0078] Further reference Figure 4 As an implementation of the methods shown in the above figures, this disclosure provides some embodiments of a page parsing apparatus, which are similar to... Figure 2 Corresponding to the method embodiments shown, this page parsing device can be specifically applied to various electronic devices.

[0079] like Figure 4As shown, a page parsing apparatus 400 in some embodiments includes: a first generation unit 401, a construction unit 402, a second generation unit 403, and a third generation unit 404. The first generation unit 401 is configured to generate a site identifier for a site corresponding to a target application, wherein the site is associated with each page included in the target application; the construction unit 402 is configured to construct a page identifier group based on the pages associated with the site, wherein each page contains at least one page resource location identifier, and the pages in each page correspond to page identifiers in the page identifier group; the second generation unit 403 is configured to generate a page resource location identifier relationship table for each page identifier in the page identifier group, based on the page identifier and the corresponding page resource location identifier; the third generation unit 404 is configured to generate a page parsing file based on the relationship table between the site identifier and each page resource location identifier.

[0080] Optionally, the page parsing device 400 further includes an access unit configured to access the page parsing file to the content delivery network server corresponding to the target application.

[0081] Optionally, the construction unit 402 is further configured to: input the page resource location identifiers contained in each of the above pages into the above site; and for each of the above pages, generate a page identifier based on the page resource location identifiers input into the above site.

[0082] Optionally, the second generation unit 403 is further configured to: determine each page resource location identifier in the above-mentioned site corresponding to the above-mentioned page identifier; perform hash processing on each of the above-mentioned page resource location identifiers to generate hash page resource location identifiers, thereby obtaining a hash page resource location identifier group; and perform mapping processing on the above-mentioned page identifiers and the hash page resource location identifier group to generate a page resource location identifier relationship table.

[0083] Optionally, the second generation unit 403 is further configured to: extract the page resource location path string from the page resource location identifier; group the characters included in the page resource location path string according to the set delimiter character group to generate a page resource location path substring sequence; perform hash processing on each page resource location path substring in the page resource location path substring sequence to generate a hash page resource location path substring; and concatenate the generated hash page resource location path substrings to form a hash page resource location identifier.

[0084] Optionally, the page parsing device 400 further includes: a reading unit configured to, in response to detecting an access operation to a target page, read a corresponding page parsing file from the content delivery network server based on the site identifier corresponding to the target page, wherein the target page has been integrated with a tracking plugin; a first determining unit configured to determine an access page resource location identifier corresponding to the access operation; a second determining unit configured to determine whether there exists a page resource location identifier relationship table corresponding to the access page resource location identifier in the various page resource location identifier relationship tables included in the page parsing file; and an uploading unit configured to, in response to determining the existence of a page resource location identifier relationship table corresponding to the access page resource location identifier, upload the page identifier contained in the page resource location identifier relationship table to an associated page data monitoring system.

[0085] It is understandable that the units described in the page parsing device 400 and the reference Figure 2 The steps in the described method correspond to each other. Therefore, the operations, features, and beneficial effects described above for the method also apply to the page parsing device 400 and the units contained therein, and will not be repeated here.

[0086] The following is for reference. Figure 5 It illustrates electronic devices suitable for implementing some embodiments of this disclosure (e.g., Figure 1 The diagram shows the structure of the computing device 101)500. Electronic devices in some embodiments of this disclosure may include, but are not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 5 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments of this disclosure.

[0087] like Figure 5 As shown, the electronic device 500 may include a processing unit (e.g., a central processing unit, a graphics processing unit, etc.) 501, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 502 or a program loaded from a storage device 508 into a random access memory (RAM) 503. The RAM 503 also stores various programs and data required for the operation of the electronic device 500. The processing unit 501, ROM 502, and RAM 503 are interconnected via a bus 504. An input / output (I / O) interface 505 is also connected to the bus 504.

[0088] Typically, the following devices can be connected to I / O interface 505: input devices 506 including, for example, touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, gyroscopes, etc.; output devices 507 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 508 including, for example, magnetic tapes, hard disks, etc.; and communication devices 509. Communication device 509 allows electronic device 500 to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 5 An electronic device 500 with various devices is shown; however, it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed alternatively. Figure 5 Each box shown can represent a device or multiple devices as needed.

[0089] In particular, according to some embodiments of this disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, some embodiments of this disclosure include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device 509, or installed from a storage device 508, or installed from a ROM 502. When the computer program is executed by the processing device 501, it performs the functions defined in the methods of some embodiments of this disclosure.

[0090] It should be noted that, in some embodiments of this disclosure, the computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium may be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In some embodiments of this disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In some embodiments of this disclosure, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium can be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wires, optical fibers, RF (radio frequency), etc., or any suitable combination thereof.

[0091] In some implementations, clients and servers can communicate using any currently known or future-developed network protocol such as HTTP (Hypertext Transfer Protocol) and can interconnect with digital data communication (e.g., communication networks) of any form or medium. Examples of communication networks include local area networks (“LANs”), wide area networks (“WANs”), the Internet (e.g., the Internet of Things), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future-developed networks.

[0092] The aforementioned computer-readable medium may be included in the aforementioned electronic device; or it may exist independently and not assembled into the electronic device. The aforementioned computer-readable medium carries one or more programs that, when executed by the electronic device, cause the electronic device to: generate a site identifier for a site corresponding to a target application, wherein the site is associated with various pages included in the target application; construct a page identifier group based on the pages associated with the site, wherein each page contains at least one page resource location identifier, and the pages in each page correspond to page identifiers in the page identifier group; for each page identifier in the page identifier group, generate a page resource location identifier relationship table based on the page identifier and its corresponding page resource location identifier; and generate a page parsing file based on the site identifier and the page resource location identifier relationship table.

[0093] Computer program code for performing operations of some embodiments of this disclosure can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, and conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0094] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0095] The units described in some embodiments of this disclosure can be implemented in software or hardware. The described units can also be housed in a processor; for example, a processor may be described as including a first generation unit, a construction unit, a second generation unit, and a third generation unit. The names of these units do not necessarily limit the unit itself; for example, a construction unit may also be described as "a unit that constructs a page identifier group based on the various pages associated with the aforementioned site."

[0096] The functions described above in this document can be performed, at least in part, by one or more hardware logic components. For example, exemplary types of hardware logic components that can be used, without limitation, include: Field Programmable Gate Arrays (FPGAs), Application-Specific Integrated Circuits (ASICs), Application Standard Products (ASSPs), System-on-Chip (SoCs), Complex Programmable Logic Devices (CPLDs), and so on.

[0097] Some embodiments of this disclosure also provide a computer program product, including a computer program that, when executed by a processor, implements any of the page resolution methods described above.

[0098] The above description is merely a selection of preferred embodiments of this disclosure and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of the invention involved in the embodiments of this disclosure is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the above-described inventive concept. For example, technical solutions formed by substituting the above-described features with (but not limited to) technical features with similar functions disclosed in the embodiments of this disclosure.

Claims

1. A page parsing method, comprising: Generate a site identifier for the site corresponding to the target application, wherein the site is associated with each page contained in the target application; Based on the pages associated with the site, a page identifier group is constructed, wherein each page contains at least one page resource location identifier, and the pages in each page correspond to the page identifiers in the page identifier group; For each page identifier in the page identifier group, a page resource location identifier relationship table is generated based on the page identifier and the corresponding page resource location identifier; Based on the relationship table between the site identifier and the resource location identifier of each page, a page parsing file is generated; In response to the detection of an access operation to a target page, the corresponding page parsing file is read from the content delivery network server according to the site identifier corresponding to the target page, wherein the target page has been integrated with the event tracking plugin; Determine the access page resource location identifier corresponding to the access operation; Determine whether there exists a corresponding page resource location identifier relationship table in the page parsing file for each page resource location identifier; In response to the determination that a page resource location identifier relationship table exists corresponding to the accessed page resource location identifier, the page identifier contained in the page resource location identifier relationship table is uploaded to the associated page data monitoring system.

2. The method according to claim 1, wherein, The method further includes: The page parsing file is connected to the content delivery network server corresponding to the target application.

3. The method according to claim 1, wherein, The step of constructing a page identifier group based on the various pages associated with the site includes: The location identifiers of the page resources contained in each page are entered into the site; For each of the aforementioned pages, a page identifier is generated based on the page resource location identifiers entered into the site.

4. The method according to claim 1, wherein, The step of generating a page resource location identifier relationship table based on the page identifier and the corresponding page resource location identifier includes: Determine the location identifiers of each page resource in the site corresponding to the page identifier; Each page resource location identifier in the various page resource location identifiers is hashed to generate a hash page resource location identifier, thus obtaining a hash page resource location identifier group; The page identifier is mapped to the hash page resource location identifier group to generate a page resource location identifier relationship table.

5. The method according to claim 4, wherein, The step of hashing each page resource location identifier in the various page resource location identifiers to generate a hash page resource location identifier includes: Extract the page resource location path string from the page resource location identifier; Based on the set delimiter character group, the characters included in the page resource location path string are grouped and processed to generate a page resource location path substring sequence; Each page resource location path substring in the sequence of page resource location path substrings is hashed to generate a hash page resource location path substring. The generated hash page resource location path substrings are concatenated to form the hash page resource location identifier.

6. A page parsing device, comprising: The first generation unit is configured to generate a site identifier for a site corresponding to the target application, wherein the site is associated with each page contained in the target application; The building unit is configured to build a page identifier group based on the pages associated with the site, wherein each page contains at least one page resource location identifier, and the pages in each page correspond to the page identifiers in the page identifier group. The second generation unit is configured to generate a page resource location identifier relationship table for each page identifier in the page identifier group, based on the page identifier and the corresponding page resource location identifier. The third generation unit is configured to generate a page parsing file based on the relationship table between the site identifier and the resource location identifiers of each page; The reading unit is configured to, in response to the detection of an access operation to a target page, read the corresponding page parsing file from the content delivery network server according to the site identifier corresponding to the target page, wherein the target page has been integrated with the tracking plugin; The first determining unit is configured to determine the access page resource location identifier corresponding to the access operation; The second determining unit is configured to determine whether there exists a page resource location identifier relationship table corresponding to the accessed page resource location identifier in each page resource location identifier relationship table included in the page parsing file; The upload unit is configured to upload the page identifier contained in the page resource location identifier relationship table to the associated page data monitoring system in response to determining that a page resource location identifier relationship table corresponding to the accessed page resource location identifier exists.

7. An electronic device, comprising: One or more processors; A storage device on which one or more programs are stored; When the one or more programs are executed by the one or more processors, the one or more processors implement the method as described in any one of claims 1-5.

8. A computer-readable medium having a computer program stored thereon, wherein, When the computer program is executed by a processor, it implements the method as described in any one of claims 1-5.

9. A computer program product comprising a computer program that, when executed by a processor, implements the method according to any one of claims 1-5.

Images