Network television user operation data acquisition method and system

Abstract

The invention discloses a network television user operation data acquisition method and system, and mainly relates to the technical field of network television data processing. Comprising the following steps: creating a new page, performing plug-in packaging in the page, and generating a unique identifier of a recommendation bit according to the packaged plug-in; when the user browses, jumps or clicks the recommendation position on the page, carrying the identifier; s2, monitoring the loading condition of the DOM, and packaging the operation into the plug-in in the step S1; when the plug-in monitors the identifier, assembling the automatically acquired and processed set top box and user account information with the pit identifier, and converting the assembled information into a JSON (JavaScript Object Notation) string; and the plug-in reports the assembled JSON string to a server through a network request. The method has the advantages that effective data of effective scenes are screened from numerous reporting scenes of user behaviors, the problem of code dispersion is solved in the information reporting process, meanwhile, the version iteration code modification amount is reduced, and the iteration period is shortened.

Description

Technical Field

[0001] The present invention relates to the technical field of network television data processing, and specifically to a method for collecting network television user operation data based on dynamic granularity. Background Art

[0002] The products of IPTV services will further develop in the aspects of diversification of service content, diversification of video forms, and multi-screen interaction in the future. At present, the end-users of IPTV services mainly receive live broadcasts and film and television programs. However, the demands of household users for audio-visual products are far more than just live TV and film and television programs. As the number of users gradually saturates, the IPTV content operation department will further explore the potential of users and provide more vertical and segmented content and local characteristic content on IPTV content, including education and training, healthcare and wellness, tourism and leisure, local services, etc. Based on the large number of IPTV users, the data generated by users using IPTV is increasing continuously. How to screen effective data from these large amounts of data has become the top priority for predicting user preferences and behaviors and delivering appropriate video content, related services, and products to users.

[0003] At present, the granularity of some user information collection systems is too detailed. For example, which page the user enters, what element browsing operations are performed on the page, the posters displayed in the page recommendation positions, the playback in small windows, etc., and all data is reported to the server, increasing the pressure on the data analysis system, and the analysis results may also be deviated, which may lead to the introduction and delivery of inappropriate video content, related services, and products by the content operation department, reducing the viewing experience of users. Therefore, collecting data according to an appropriate granularity is a problem that needs to be solved.

[0004] In addition, in the EPG page environment, collecting user operation data, the specific scenarios include: page jump, content playback, product ordering, etc. How to collect effective information and solve the problem of scattered code and reduce the version iteration cost in the process is also a problem that needs to be solved.

[0005] Therefore, there is an urgent need for a method for collecting network television user operation data based on dynamic granularity to solve the above problems. Summary of the Invention

[0006] The purpose of the present invention is to provide a method for collecting network television user operation data based on dynamic granularity, which realizes screening effective data of effective scenarios among many reported scenarios of user behaviors, solves the problem of scattered code in the process of information reporting, and at the same time reduces the amount of code modification in version iteration and shortens the iteration cycle.

[0007] To achieve the above object, the present invention is realized through the following technical solutions: On the one hand, a method for collecting network television user operation data is provided, including the following steps: Step S1: Create a new page, introduce the encapsulated plugin in the page, use addEventListener to add a DOMContentLoaded event to monitor the DOM loading situation, and encapsulate this operation in the plugin. Generate a unique identifier for the recommended position according to the encapsulated plugin. Step S2: Carry the identifier in Step S1 when the user browses, jumps, or clicks on the recommended position on the page. Step S3: When the plugin in Step S1 detects the identifier in Step S2, it will automatically obtain the processed set-top box and user account information, assemble them with the pit identifier, and convert them into a JSON string. Step S4: The plugin reports the assembled JSON string to the server through a network request.

[0008] Preferably, in Step S1, generating the unique identifier for the recommended position is specifically as follows: Create a new page, perform plugin encapsulation in the page, and generate a unique identifier for the recommended position according to the page identifier of the new page and the position of the recommended position. The identifier is used to subsequently track and analyze the interaction between the user and the recommended position.

[0009] Preferably, in Step S1, monitoring the DOM loading situation is specifically as follows: If the DOM loading is completed, continue with the subsequent reporting operation. If the DOM is not loaded yet, but it is detected that the user stays on the current page for more than 3 seconds, continue with the subsequent reporting operation and end the monitoring. If it is detected that the user leaves the current page before the DOM loading is completed, it indicates that the page life cycle has ended and no data is reported.

[0010] Preferably, after the DOM loading is completed, it is determined whether to report according to the user behavior and the page life cycle, including: Execute data reporting 2 seconds after the DOM loading is completed without waiting for the loading of other resources on the page to complete. If the user does not stay on the page for another 2 seconds after the DOM loading is completed, it is regarded as invalid data and no data reporting is executed.

[0011] Preferably, Step S2 is specifically as follows: Set a parameter in the URL. The parameter is used to represent the data that needs to be reported for the user behavior. The value of the parameter represents the generated recommended position identifier. Set a probe object, and when the above parameter is monitored, the object executes the reporting action.

[0012] Preferably, in Step S3, the assembly with the pit identifier is specifically as follows: Define a unique and non-repeating identifier for each reporting scenario, which is used to determine the parameter names corresponding to the parameter values of each scenario behavior; When initializing the page, define a selection container. Each item in the container corresponds to a reporting scenario, i.e., key-value, where the key represents the scenario identifier and the value represents the assembled JSON string; When the object performs a reporting action, traverse the selection container, obtain the corresponding reporting information, and then perform subsequent network requests.

[0013] Preferably, step S4 is specifically as follows: Report the obtained reporting information to the server through a network request and perform a callback after the reporting.

[0014] On the other hand, provide a data collection system based on the above-mentioned network TV user operation data collection method, which is characterized by including: An identifier generation module that creates a new page, introduces a packaged plugin in the page, uses addEventListener to add a DOMContentLoaded event to monitor the DOM loading situation, and at the same time encapsulates this operation in the plugin, and generates a unique identifier for the recommended position according to the packaged plugin; An identifier recording module for carrying the identifier when the user browses, jumps, or clicks on the recommended position on the page; A JSON string conversion module for automatically obtaining the processed set-top box and user account information after the plugin detects the identifier, assembling them with the pit identifier, and converting them into a JSON string; A data reporting module for the plugin to report the assembled JSON string to the server through a network request.

[0015] Compared with the prior art, the beneficial effects of the present invention are as follows: The present invention encapsulates a probe data reporting proxy plugin that integrates event listening, data assembly, data reporting, and heartbeat in combination with the web page life cycle. Users only need to introduce this plugin when developing the page, and the page probe ID will be automatically generated, and data reporting will be automatically completed when the page jumps, reducing code dispersion during the reporting process of each page and avoiding code injection problems; the present invention adopts a lightweight data collection strategy to collect and filter valid information among numerous user behaviors; at the same time, the present invention adopts a listening callback mechanism to avoid data underreporting. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1 is the method flow chart of the present invention; Figure 2 is the method flow timing diagram of the present invention; Figure 3 is the system structure schematic diagram of the present invention. Detailed implementation manners

[0017] The present invention will be further described below in conjunction with specific embodiments. It should be understood that these embodiments are only used to illustrate the present invention and not to limit the scope of the present invention. In addition, it should be understood that after reading the content taught by the present invention, those skilled in the art can make various changes or modifications to the present invention, and these equivalent forms also fall within the scope defined by the present application.

[0018] In the present invention, terms such as "upper", "lower", "left", "right", "front", "rear", "vertical", "horizontal", "side", "bottom", etc. indicate the orientation or positional relationship based on the orientation or positional relationship shown in the drawings. They are only relationship words determined for the convenience of describing the structural relationship of each component or element of the present invention, and do not specifically refer to any component or element in the present invention, and should not be construed as a limitation to the present invention.

[0019] Embodiment: As Figure 1-2 shown, the present embodiment provides a method for collecting network TV user operation data, including the following steps: S1: Create a new page, and perform plug-in encapsulation in the page. The plug-in is used to combine with the web page life cycle, listen for callbacks, identify valid behavior data, then process and assemble the corresponding behavior data according to the data collection specification, and finally report it. According to the encapsulated plug-in, generate a unique identifier for the recommended position; S2: Carry the identifier in step S1 when the user browses, jumps, or clicks on the recommended position on the page; S3: Use addEventListener to add a DOMContentLoaded event to listen for the DOM loading situation, and encapsulate this operation in the plug-in in step S1; S4: When the plug-in in step S3 detects the identifier in step S2, it will automatically obtain the processed set-top box and user account information, assemble them with the pit position identifier, and convert them into a JSON string; S5: The plug-in reports the assembled JSON string to the server through a network request.

[0020] Among them, the method for creating a new page and automatically generating a unique identifier for the recommended position according to the encapsulated method in step S1 is: Generate a unique identifier for the recommended position by automatically numbering according to the page identifier of the new page and the position of the recommended position, that is, the row and column where it is located. This identifier is used for subsequent tracking and analysis of the interaction between the user and the recommended position.

[0021] In step S2, the method for carrying the identifier when the user browses, jumps, or clicks on the recommended position on the page is: Agree on a URL parameter to represent that data needs to be reported for this behavior. The parameter value is the recommendation position identifier generated previously. When the user browses the page, jumps to other pages, or clicks on the recommendation position, it is necessary to ensure that these operations contain the previously generated recommendation position identifier, which is achieved through the URL parameter. Instantiate a probe object, and when this parameter is monitored, the instantiated object performs the reporting action.

[0022] Step S3 is specifically as follows: “FUNCTION domReady(): / / Define the actual fn() to be executed fn = FUNCTION: SET timeout for 2000ms: CALL probeInit() IF browser supports addEventListener THEN / / Handling for modern browsers ADD event listener for "DOMContentLoaded": WHEN event triggers: REMOVE this event listener SET initDoFlag = TRUE EXECUTE fn() / / Here, probeInit() will be executed 2 seconds later / / Parallel 3 - second timeout fallback solution SET timeout for 3000ms: IF initDoFlag is NOT TRUE THEN CALL probeInit() / / Call directly (without the 2 - second delay of fn) ELSE IF browser supports attachEvent THEN / / Handling for IE browsers ATTACH event handler for "onreadystatechange": WHEN readyState becomes "complete": DETACH this event handler EXECUTE fn() / / Execute probeInit() 2 seconds after startup / / IE-specific doScroll detection method IF document supports doScroll AND not in iframe THEN TRY: PERFORM doScroll('left') EXECUTE fn() / / Execute probeInit() 2 seconds after startup CATCH error: WAIT 20ms THEN RETRY this check” The above pseudocode indicates: If the DOM is loaded, continue with subsequent reporting operations; If the DOM is not loaded, but it is detected that the user has stayed on the current page for more than 3 seconds, continue with subsequent reporting operations and end the monitoring; If it is detected that the user leaves the current page before the DOM is loaded, it indicates the end of the page life cycle and no data is reported; After the DOM is loaded, determine whether to report according to user behavior and page life cycle, including: 2 seconds after the DOM is loaded, without waiting for the loading of other resources on the page, perform data reporting; If the user does not stay on the page for another 2 seconds after the DOM is loaded, it is regarded as invalid data and no data reporting is performed.

[0023] In step S4, the specific assembly with the pit identifier is as follows: Define a unique and non-repeating identifier for each reporting scenario to determine the parameter name corresponding to each scenario behavior parameter; When initializing the page, define a selection container. Each item in the container corresponds to a reporting scenario, that is, key-value, where the key represents the scenario identifier and the value represents the assembled JSON string; When the object performs a reporting action, traverse the selection container, obtain the corresponding reporting information, and then perform subsequent network requests; Report the obtained reporting information to the server through a network request and perform a callback after reporting.

[0024] As Figure 3 shown, this embodiment also provides a data collection system based on the above network TV user operation data collection method, including: An identification generation module, configured to: create a new page, encapsulate plugins in the page, and generate a unique identifier for the recommended position according to the encapsulated plugins; An identification recording module, configured to: carry the identifier when the user browses, jumps, or clicks on the recommended position of the page; A DOM loading condition monitoring module, configured to: use addEventListener to add a DOMContentLoaded event to monitor the DOM loading condition, and encapsulate this operation in the plugin; A JSON string conversion module, configured to: when the plugin detects the identifier, automatically obtain the processed set-top box and user account information, assemble them with the pit position identifier, and convert them into a JSON string; A data reporting module, configured to: report the assembled JSON string to the server through a network request by the plugin.

[0025] The above is a specific description of the preferred embodiment of the present invention, but the present invention is not limited to the described embodiment. Those skilled in the art can make various equivalent deformations or substitutions without departing from the spirit of the present invention, and these equivalent deformations or substitutions are all included in the scope defined by the claims of this application.

Claims

1. A method for collecting user operation data of an Internet TV, characterized in that: The following steps are involved: Step S1: Create a new page and introduce the encapsulated plug-in into the page. Use addEventListener to add the DOMContentLoaded event to monitor the DOM loading status. Encapsulate this operation in the plug-in and generate a unique identifier for the recommended position based on the encapsulated plug-in. Step S2: When the user browses, jumps to, or clicks on a recommended location on a page, the identifier in step S1 is carried; Step S3: When the plug-in in step S1 detects the identifier in step S2, it automatically obtains the processed set-top box and user account information, assembles it with the pit identifier, and converts it into a JSON string; Step S4: The plug-in reports the assembled JSON string to the server via a network request.

2. The method for collecting user operation data of an Internet TV according to claim 1, characterized in that: In step S1, a unique identifier of the recommended position is generated, specifically: A new page is created and the plug-in is encapsulated in the page. A unique identifier of the recommendation position is generated according to the page identifier of the new page and the position of the recommendation position. The identifier is used for subsequent tracking and analysis of the interaction between the user and the recommendation position.

3. The method for collecting user operation data of an Internet TV according to claim 1, characterized in that: In step S1, monitoring the DOM loading situation is specifically as follows: If DOM loading is complete, continue with the subsequent reporting operations; If the DOM is not loaded, but the user stays on the current page for more than 3 seconds, the subsequent reporting operation will continue and the monitoring will end; If the user leaves the current page before DOM loading is completed, it means that the page life cycle ends and no data is reported.

4. The method for collecting user operation data of an Internet TV according to claim 3, characterized in that: When the DOM is loaded, determine whether to report based on user behavior and page life cycle, including: 2 seconds after DOM loading is completed, data reporting is performed without waiting for other resources on the page to be loaded; If the user does not stay on the page for 2 seconds after DOM loading is completed, it will be considered invalid data and no data reporting will be performed.

5. The method for collecting user operation data of an Internet TV according to claim 1, characterized in that: The step S2 is specifically as follows: a parameter is set in the URL, the parameter is used to represent the data of the user behavior that needs to be reported, the value of the parameter represents the generated recommendation position identifier, and a probe object is set. When the above parameter is monitored, the object performs a reporting action.

6. The method for collecting user operation data of an Internet TV according to claim 1, characterized in that: In step S3, the assembly with the pit mark is specifically as follows: Define a unique and non-repetitive identifier for each reported scenario to determine the parameter name corresponding to each scenario behavior parameter; When the page is initialized, a selection container is defined, each entry of the container corresponds to a reporting scenario, that is, key-value, where key represents the scenario identifier and value represents the assembled JSON string; When the object performs a reporting action, it traverses the selected container and obtains the corresponding reporting information before making subsequent network requests.

7. The method for collecting user operation data of an Internet TV according to claim 1, characterized in that: The step S4 is specifically: The acquired reporting information is reported to the server through a network request, and a callback is performed after the reporting.

8. A data collection system based on the method for collecting user operation data of Internet TV according to claim 1, characterized in that: include: The logo generation module creates a new page and introduces the encapsulated plug-in into the page. It uses addEventListener to add the DOMContentLoaded event to monitor the DOM loading status. It also encapsulates this operation in the plug-in and generates a unique logo for the recommendation position based on the encapsulated plug-in. The identification recording module is used to carry the identification when the user browses, jumps or clicks the recommended position on the page; The JSON string conversion module is used to: when the plug-in detects the identifier, it will automatically obtain the processed set-top box and user account information, assemble it with the pit identifier, and convert it into a JSON string; Data reporting module, used for: The plug-in reports the assembled JSON string to the server through a network request.

Images