CN111782490A - Data acquisition method and device - Google Patents
Data acquisition method and device Download PDFInfo
- Publication number
- CN111782490A CN111782490A CN201910272225.5A CN201910272225A CN111782490A CN 111782490 A CN111782490 A CN 111782490A CN 201910272225 A CN201910272225 A CN 201910272225A CN 111782490 A CN111782490 A CN 111782490A
- Authority
- CN
- China
- Prior art keywords
- preset
- page
- component
- determining
- target page
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3438—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment monitoring of user actions
Landscapes
- Engineering & Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- User Interface Of Digital Computer (AREA)
Abstract
The invention discloses a data acquisition method and a data acquisition device, wherein the method comprises the following steps: determining each preset component related to user interaction behavior contained in a target application, monitoring the life cycle of each preset component, and determining a page corresponding to the preset component in the current state as a target page; determining each preset view control contained in a preset component corresponding to the target page, and monitoring each preset view control to determine a user interaction event corresponding to the target page; and acquiring user behavior data corresponding to the target application according to the target page and the user interaction event corresponding to the target page. The method can automatically collect data, not only improves the efficiency, but also avoids the problem of untimely updating of the buried points caused by product iteration. The method can comprehensively collect the user behavior data without the participation of developers, thereby reducing the workload of the developers.
Description
Technical Field
The invention relates to the technical field of internet, in particular to a data acquisition method and a data acquisition device.
Background
With the rapid development of the mobile internet, the App application function is continuously enriched and improved, and the user behavior data of the application is legally collected, so that the application function is improved, the user behavior is analyzed, the user portrait is established, and personalized marketing recommendation is realized. At present, the mode of collecting user behavior data is mainly a manual point burying mode. Manual embedding refers to adding more lines of code for acquiring data on top of the originally complex code logic for the purpose of data analysis. For example, in order to obtain the number of clicks of a product, a code for collecting related information such as a product name and a click time needs to be added so as to collect data information corresponding to a click event when the click event occurs.
However, the inventor finds that the implementation manner in the prior art at least has the following defects in the process of implementing the invention: in the iterative process of the product, once the buried point logic is not changed in time according to the iterated code, the accuracy of the subsequently collected user behavior data is affected, and even the application is easy to fail. Therefore, in a scene with frequent product updating iterations, the manual point burying mode easily causes destructive influence on the product. Moreover, manual embedding needs to be realized manually by a developer, and the method is complex to operate, large in workload and low in efficiency.
Disclosure of Invention
In view of the above, the present invention has been made to provide a data acquisition method and apparatus that overcomes or at least partially solves the above problems.
According to an aspect of the present invention, there is provided a data acquisition method including:
determining each preset component related to user interaction behavior contained in a target application, monitoring the life cycle of each preset component, and determining a page corresponding to the preset component in the current state as a target page;
determining each preset view control contained in a preset component corresponding to the target page, and monitoring each preset view control to determine a user interaction event corresponding to the target page;
and acquiring user behavior data corresponding to the target application according to the target page and the user interaction event corresponding to the target page.
According to another aspect of the present invention, there is provided a data acquisition apparatus comprising:
the component monitoring module is suitable for determining each preset component which is contained in the target application and is associated with the user interaction behavior, monitoring the life cycle of each preset component, and determining a page corresponding to the preset component of which the current state belongs to the preset state as a target page;
the control monitoring module is suitable for determining each preset view control contained in a preset component corresponding to the target page and monitoring each preset view control so as to determine a user interaction event corresponding to the target page;
and the acquisition module is suitable for acquiring user behavior data corresponding to the target application according to the target page and the user interaction event corresponding to the target page.
According to still another aspect of the present invention, there is provided an electronic apparatus including: the system comprises a processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface complete mutual communication through the communication bus;
the memory is used for storing at least one executable instruction, and the executable instruction enables the processor to execute the operation corresponding to the data acquisition method.
According to still another aspect of the present invention, a computer storage medium is provided, where at least one executable instruction is stored in the storage medium, and the executable instruction causes a processor to perform operations corresponding to the data acquisition method.
According to the data acquisition method and device provided by the invention, each preset component related to the user interaction behavior in the target application can be determined, and the monitoring is carried out aiming at the life cycle of each preset component, so that the page corresponding to the preset component with the current state belonging to the preset state is determined as the target page; and then, determining each preset view control contained in the preset assembly corresponding to the target page, monitoring aiming at each preset view control to determine a user interaction event corresponding to the target page, and acquiring user behavior data according to the target page and the user interaction event. Therefore, the method can automatically determine the current target page in an operable state by monitoring the life cycle of the preset component, and can automatically determine the user interaction operation received by the target page by monitoring the preset view control corresponding to the target page, so that the user behavior data can be automatically collected, manual point burying is not needed, the data can be automatically collected, the efficiency is improved, and the problem that the point burying is not timely updated due to product iteration is avoided.
The foregoing description is only an overview of the technical solutions of the present invention, and the embodiments of the present invention are described below in order to make the technical means of the present invention more clearly understood and to make the above and other objects, features, and advantages of the present invention more clearly understandable.
Drawings
Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:
FIG. 1 shows a schematic flow diagram of a data acquisition method according to an embodiment of the invention;
FIG. 2 shows a schematic flow diagram of a data acquisition method according to another embodiment of the invention;
FIG. 3 shows a schematic structural diagram of a data acquisition device according to yet another embodiment of the present invention;
fig. 4 shows a schematic structural diagram of an electronic device according to the present invention.
Detailed Description
Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
Fig. 1 shows a schematic flow diagram of a data acquisition method according to an embodiment of the invention, as shown in fig. 1, the method comprising:
step S110: determining each preset component related to the user interaction behavior in the target application, monitoring the life cycle of each preset component, and determining a page corresponding to the preset component in the current state as a target page.
The target application refers to an application which needs to acquire user behavior data, and the application can be various applications such as android application. The preset components associated with the user interaction behavior refer to: and components, such as Activity components (Activities) or Fragment components (fragments), which can provide user interaction functions to trigger user interaction events. By monitoring each preset component, whether the page corresponding to the preset component is determined as the target page can be determined according to which state of the preset component in the life cycle currently.
Specifically, a page corresponding to a preset component of which the current state belongs to the preset state is determined as a target page. The preset state mainly refers to a state that enables a corresponding page to be in a user operable state, such as a creation state and a recovery state. By this step, the page in the current screen which can receive the user operation event can be automatically determined as the target page.
Step S120: and determining each preset view control contained in the preset assembly corresponding to the target page, and monitoring each preset view control to determine a user interaction event corresponding to the target page.
In the previous step, the page capable of receiving the user operation event is determined as the target page, and accordingly, in this step, in order to monitor the specific user operation event received by each target page, monitoring needs to be performed for each preset view control included in the preset component corresponding to the target page. Wherein, presetting view controls means: controls that can trigger user interaction events, for example, various types of controls that can trigger click events, slide events. Specifically, each user operation event received in the target page is triggered by the corresponding preset view control, and accordingly, each user interaction event can be captured by monitoring the preset view control.
Step S130: and acquiring user behavior data corresponding to the target application according to the target page and the user interaction event corresponding to the target page.
Aiming at a target page, information such as a page name, display time, display duration and the like of the target page can be acquired; for the user interaction event corresponding to the target page, information such as an operation object, operation time and the like of each user interaction event can be acquired, and accordingly, user behavior data corresponding to the target application can be acquired according to the information.
Therefore, the method can automatically determine the current target page in an operable state by monitoring the life cycle of the preset component, and can automatically determine the user interaction operation received by the target page by monitoring the preset view control corresponding to the target page, so that the user behavior data can be automatically collected, manual point burying is not needed, the data can be automatically collected, the efficiency is improved, and the problem that the point burying is not timely updated due to product iteration is avoided. The method can comprehensively collect the user behavior data without the participation of developers, thereby reducing the workload of the developers.
Fig. 2 shows a schematic flow diagram of a data acquisition method according to another embodiment of the invention. As shown in fig. 2, the method includes:
step S210: and determining various preset components related to the user interaction behaviors and contained in the target application.
The target application in this embodiment is an android application. Specifically, the following manners may be adopted to determine the preset components associated with the user interaction behavior contained in the target application:
firstly, an activity component which is contained in the target application, is used for interacting with a user and contains a user interface is determined as a first type of preset component. The first type of preset component mainly refers to an Activity component, namely an Activity component. Specifically, an Activity component is a component including a user interface, and is mainly used for interacting with a user, and an application may include zero or more Activity components.
And then, determining a fragment component contained in the target application and realized based on the first type of preset components as a second type of preset components. The second type of preset component mainly refers to a Fragment component, i.e., a Fragment component. In the process of implementing the invention, the inventor finds that most events in the android application occur in the Activity component and the Fragment component, so that the user behavior data can be effectively collected by monitoring the Activity component and the Fragment component. The Activity component is a heavyweight component, the Fragment component is a convenient and light component, and the application running speed can be increased and the memory can be saved by combining the Activity component and the Fragment component. In a specific implementation, the Fragment component is implemented based on an Activity component, and may also be referred to as a subcomponent of the Activity component.
And finally, determining the first-class preset components and/or the second-class preset components as the preset components which are contained in the target application and are associated with the user interaction behavior. In actual conditions, the purpose of collecting user behavior data can be achieved by monitoring only one type of preset component, and the collected user behavior data can be more comprehensive by monitoring two types of preset components. One or both of the two types of listening preset components may be determined by one skilled in the art based on the type of user behavior data to be collected.
Step S220: monitoring the life cycle of each preset component, and determining a page corresponding to the preset component with the current state belonging to the preset state as a target page.
Monitoring the life cycles of the Activity component and the Fragment component can determine the page displayed by the current screen, and further count the page opened by the user or the data information such as how long the user stays on a certain page. During specific implementation, the life cycle of each preset component is monitored through a preset life cycle callback interface.
First, introduce the way an Activity component listens:
specifically, the method monitors the life cycle of the Activity component through a life cycle callback interface of the Activity lifecycle servers, wherein the interface contains abstract methods of all the life cycles of the Activity component, and the life cycle of the Activity component can be monitored by realizing the interface and realizing corresponding life cycle methods, and specifically comprises the following steps:
the method comprises the following steps: the self-definition ActivityLifecycleCallbackListener realizes the self-ActivityLifecycleCallbackets interface class and realizes the onActivityCreated method, the onActivityResummed method and the onActivityStoppped method of the ActivityLifecycleCallbackets interface class. Wherein the onactycreated method is used to create an Activity component, the onactyresurmed method is used to restore the Activity component, and the onactystopped method is used to stop the Activity component.
Step two: the self-definition Myapplication inherits the self-Application, and registers a monitoring implementation class, namely, a new ActivityLifecycleCallbacknowledger () in an onCreate () method function so as to implement monitoring operation.
Step three: in an application tag of an android manifest.
Wherein the onActityResummed method indicates that Activity components are revealed to the user, visible to the user; the onactive stopped method indicates that the Activity component has stopped and is not visible to the user. Accordingly, the name and the entering time of the Activity component are recorded in the onactitresummed method, and the name and the leaving time of the Activity component are recorded in the onactitystopped method, thereby enabling statistics of which page the user has opened and how long the user stays on a certain page.
Next, a monitoring method of the Fragment component is introduced, which specifically includes the following steps:
the method comprises the following steps: and self-defining a JGFragmentLifecycleCallbacks class to inherit from the FragmentLifecycleCallbacks class, and rewriting an onFragmentStarted method and an onFragmentStoppped method of the parent class so as to facilitate statistics. The Fragment lifecycle callbacks class is a callback interface for monitoring the lifecycle of the Fragment component. The onFragmentStarted method and the onFragmentStoppped method are respectively used for realizing the starting operation and the stopping operation of the Fragment component, and the state of the Fragment component can be determined by monitoring the two methods.
Step two: acquiring Fragment manager of the current Activity component in an Activities Created method of Activities lifecycleCallbacksLister class for monitoring the Activity component, and registering a self-defined JGFragmentLifecycleCallbacks instance in the Fragment manager to realize the monitoring of the life cycle of the Fragment component.
Through the above operation, monitoring for the preset component can be realized, so that the preset component of which the current state belongs to the preset state is obtained, and a page corresponding to the preset component of which the current state belongs to the preset state is determined as a target page. Wherein, the preset state includes: create, restore and/or stop states; correspondingly, when the page corresponding to the preset component of which the current state belongs to the preset state is determined as the target page, firstly, the page corresponding to the preset component of which the current state belongs to the preset state is determined as a candidate target page; then, a page in a user operable state among the candidate target pages is determined as a target page. Therefore, by monitoring which state of each preset component in the life cycle, the page corresponding to the preset component with the state changed into the preset state can be used as a candidate target page, and then the page in the user operable state is selected as the target page. Wherein, the operable state is that: a state that is shown in front of the screen (rather than hidden in the background) and is capable of receiving user interaction events. For example, assume that a first page and a second page are displayed in the front end of the screen in a split-screen manner, and when the user clicks the second page, the first page is in an inactive state (i.e., an inoperable state) and the second page is in an active state (i.e., an operable state). Correspondingly, the second page is determined as a target page, so that the user interaction event received in the second page can be monitored.
In addition, after the page corresponding to the preset component of which the current state belongs to the preset state is determined as the target page, the page identifier, the display time, the closing time, the display duration and/or the display order of each target page are further determined, so that page attribute data corresponding to each target page are obtained. Accordingly, the user behavior data in this embodiment includes page attribute data. The relevant information of each page presented on the screen can be determined by the page attribute data.
Step S230: and determining each preset view control contained in the preset assembly corresponding to the target page, and monitoring each preset view control to determine a user interaction event corresponding to the target page.
Wherein, presetting view controls means: controls capable of receiving user interaction events, such as click button controls, slider controls, input box controls, and the like. The inventor finds that each user interaction event in the target page is triggered through the preset view control in the process of implementing the invention, so that the user interaction event corresponding to the target page can be determined in a mode of monitoring the preset view control. In specific implementation, the preset view control can be determined in various ways.
In a first implementation manner, each control included in a preset component corresponding to a target page is traversed, and a control of which the control type is matched with a preset view type is determined as a preset view control. The implementation mode mainly screens the controls matched with the preset View types based on the control types to monitor, and mainly monitors list type views. The preset view type refers to a view control type capable of generating an event, and includes: list class view type, etc. Specifically, all View controls in the Activity component, such as a ListView control, a cyclerview control, a ViewPager control, a TabLayout control, and the like, which may cause an event, are scanned, and a snoop is added to the View controls, so as to determine which View control in the target page the user clicks.
In order to count the name of the View control clicked by the user and the specific click position, all View controls in the Activity component need to be scanned, and the View controls which may have click events are extracted and monitored. The View control with high frequency of occurrence mainly comprises a ListView control and a RecycleView control, and the two list class View controls need to be monitored so as to know which position of the list is clicked by a user.
The monitoring steps for the ListView control are as follows: firstly, scanning all View controls of an Activity component, and intercepting if the View controls are found to be ListView instances; then, the self-definition class OnitemeClickListenerProxy realizes the self-ItemeClickListener, the OnitemeLongClickListener and the OnitemeSelectedListener, rewrites the methods of onItemClick, onItemLongClick and onItemSelected, and adds the monitoring logic in the methods; finally, setting agents for the OnitemeClickListener, OnitemeLongClickListener and OnitemeSelectedListener methods of the ListView control as the user-defined OnitemeClickListenerProxy type instances. The monitoring of the ListView control can be completed through the operation. Accordingly, if a user clicks a certain row of the list, an oneItemClick or a oneItemLongClick or a oneItemSelect method of the OnitemClickListenerProxy is called, and the behavior data of the user can be counted through the methods.
The monitoring steps for the RecycleView control are as follows: firstly, scanning all View controls of an Activity component, and if the View controls are found to be instances of RecyclerView, intercepting the View controls; then, the self-defining class ItemTouchHelperGesturilListener inherits from SimpleOnGesturilener and rewrites the onSingleTapUp and onLongPress methods of the parent class; finally, the self-definition class OnRecycleItemClickListener realizes the self-OnItemTouchListener, realizes the onInterceptTouchent and onTouchent methods, and creates a GestureDetectore Complet instance to transmit the instance of ItemTouchHelperGesturListener into the instance; invoking addOnItemTouchListener method of the RecycleView instance, wherein the addOnItemTouchListener method imports an instance of an OnRecycleItemClickListener. Therefore, the monitoring of the RecyclerView control is completed by utilizing the GesturListener class (gesture monitoring class, namely a gesture monitoring interface), if a user clicks a certain row of the RecyclerView, the method of onSingleTapUp or onLongPress in the ItemTouchHelperGesturgeListener class can be called back, and the behavior data of the user can be counted by the methods. Therefore, each preset view control can be monitored through the preset gesture monitoring interface.
In a second implementation manner, traversing each control included in a preset component corresponding to the target page, and determining a control with a control attribute matched with a preset interaction attribute as a preset view control. The realization mode mainly carries out screening based on the attribute of the control, mainly screens the control capable of interacting with the user, and mainly realizes the monitoring of the View of the click event. Wherein, presetting interaction attributes comprises: clickable attributes, slideable attributes, and/or long press attributes, among other types of interactable attributes. The method is mainly used for monitoring all clickable views, and comprises the following specific steps: firstly, scanning all View controls of an Activity component, and intercepting the View controls if the properties of the View controls are isclicable or isLongclicable; then, the self-defining class OnclickListenerProxy realizes the self-OnclickListener and realizes the onClick method; the self-definition class OnLongListenerProxy realizes the self-OnLongClickListener and realizes the onLongClick method; and finally, acquiring the OnClickListener and the OnLongClickListener of the View through reflection, and respectively setting the agents as the user-defined OnClickListenerProxy and the OnLongListenerProxy. Accordingly, if the user triggers a click event, the onclicktriencer method in the onclicktrienerproxy (for monitoring click events) or the onlongclicktriencer method in the onlongrienerproxy (for monitoring long-press events) is called back, and the behavior data of the user can be counted through the methods.
The two implementation modes can be used independently or in combination. When the two are used in combination, they may be executed simultaneously or sequentially, for example, the first implementation may be executed first, and then the second implementation may be executed.
Step S240: and acquiring user behavior data corresponding to the target application according to the target page and the user interaction event corresponding to the target page.
Aiming at a target page, information such as a page name, display time, display duration and the like of the target page can be acquired; for the user interaction event corresponding to the target page, information such as an operation object, operation time and the like of each user interaction event can be acquired, and accordingly, user behavior data corresponding to the target application can be acquired according to the information. The user behavior data specifically includes: event attribute information of a user interaction event corresponding to the target page; wherein the event attribute information includes: event type, event time, and event object, etc.
Therefore, the invention monitors the life cycle of the Activity component and the Fragment component, scans all the View controls which may have events in the Activity component, and monitors the View controls to achieve the aim of data acquisition. The components and the controls to be monitored are determined according to the types and functions of the components and the controls, so that the components and the controls related to the user interaction events can be automatically brought into a monitoring range without manual point burying, and the aim of automatically acquiring user behavior data on the premise of no point burying is fulfilled.
In the step of monitoring the Activity component, an Application class (namely Myapplication) is customized, and a name is added in an android manifest xml file, namely the name of the customized class is added, so that the customized Application class can be inserted into an Application program in a code inserting mode, and the collection of user behavior data can be automatically realized without the participation of a developer. The mode is a technical scheme of no buried point based on an android platform, user behavior data can be automatically and comprehensively collected, and workload of developers is reduced.
Fig. 3 shows a schematic structural diagram of a data acquisition apparatus according to another embodiment of the present invention, as shown in fig. 3, the apparatus includes:
the component monitoring module 31 is adapted to determine each preset component associated with a user interaction behavior included in the target application, monitor a life cycle of each preset component, and determine a page corresponding to the preset component in a current state belonging to a preset state as a target page;
a control monitoring module 32, adapted to determine each preset view control included in a preset component corresponding to the target page, and monitor for each preset view control to determine a user interaction event corresponding to the target page;
the collecting module 33 is adapted to collect user behavior data corresponding to the target application according to the target page and the user interaction event corresponding to the target page.
Optionally, the component listening module is specifically adapted to:
determining an activity component which is contained in the target application, is used for interacting with a user and contains a user interface as a first type of preset component; and/or the presence of a gas in the gas,
determining a fragment component contained in the target application and realized based on the first type of preset component as a second type of preset component;
and determining the first type of preset components and/or the second type of preset components as the preset components which are contained in the target application and are associated with the user interaction behaviors.
Optionally, the component listening module is specifically adapted to:
monitoring the life cycle of each preset component through a preset life cycle callback interface, and acquiring the preset component of which the current state belongs to the preset state;
and determining the page corresponding to the preset component of which the current state belongs to the preset state as a target page.
Optionally, the preset state includes: create, restore and/or stop states; and the component listening module is specifically adapted to:
determining a page corresponding to a preset component of which the current state belongs to a preset state as a candidate target page;
and determining the page in the operable state of the user in the candidate target pages as a target page.
Optionally, the component listening module is further adapted to:
determining page identification, display time, closing time, display duration and/or display sequence of each target page to obtain page attribute data corresponding to each target page; the user behavior data comprises the page attribute data.
Optionally, the control listening module is specifically adapted to:
traversing each control contained in a preset assembly corresponding to the target page, and determining the control with the control type matched with a preset view type as the preset view control; and/or the presence of a gas in the gas,
traversing each control contained in a preset assembly corresponding to the target page, and determining the control with the control attribute matched with a preset interaction attribute as the preset view control;
wherein the preset view type includes: a list class view type; the preset interaction attribute comprises: clickable properties and/or long press properties.
Optionally, the control listening module is specifically adapted to: and monitoring each preset view control through a preset gesture monitoring interface.
Optionally, the user behavior data includes: event attribute information of the user interaction event corresponding to the target page; wherein the event attribute information includes: event type, event time, and event object.
The specific structure and the working principle of each module may refer to the description of the corresponding step in the method embodiment, and are not described herein again.
The embodiment of the application provides a nonvolatile computer storage medium, wherein the computer storage medium stores at least one executable instruction, and the computer executable instruction can execute the data acquisition method in any method embodiment.
Fig. 4 is a schematic structural diagram of an electronic device according to an embodiment of the present invention, and the specific embodiment of the present invention does not limit the specific implementation of the electronic device.
As shown in fig. 4, the electronic device may include: a processor (processor)402, a Communications Interface 404, a memory 406, and a Communications bus 408.
Wherein:
the processor 402, communication interface 404, and memory 406 communicate with each other via a communication bus 408.
A communication interface 404 for communicating with network elements of other devices, such as clients or other servers.
The processor 402 is configured to execute the program 410, and may specifically perform relevant steps in the above embodiments of the domain name resolution method.
In particular, program 410 may include program code comprising computer operating instructions.
The processor 402 may be a central processing unit CPU, or an application specific Integrated circuit asic, or one or more Integrated circuits configured to implement an embodiment of the present invention. The electronic device comprises one or more processors, which can be the same type of processor, such as one or more CPUs; or may be different types of processors such as one or more CPUs and one or more ASICs.
And a memory 406 for storing a program 410. Memory 406 may comprise high-speed RAM memory, and may also include non-volatile memory (non-volatile memory), such as at least one disk memory.
The program 410 may be specifically configured to cause the processor 402 to perform the operations in the above-described method embodiments.
The algorithms and displays presented herein are not inherently related to any particular computer, virtual machine, or other apparatus. Various general purpose systems may also be used with the teachings herein. The required structure for constructing such a system will be apparent from the description above. Moreover, the present invention is not directed to any particular programming language. It is appreciated that a variety of programming languages may be used to implement the teachings of the present invention as described herein, and any descriptions of specific languages are provided above to disclose the best mode of the invention.
In the description provided herein, numerous specific details are set forth. It is understood, however, that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.
Similarly, it should be appreciated that in the foregoing description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure and aiding in the understanding of one or more of the various inventive aspects. However, the disclosed method should not be interpreted as reflecting an intention that: that the invention as claimed requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the detailed description are hereby expressly incorporated into this detailed description, with each claim standing on its own as a separate embodiment of this invention.
Those skilled in the art will appreciate that the modules in the device in an embodiment may be adaptively changed and disposed in one or more devices different from the embodiment. The modules or units or components of the embodiments may be combined into one module or unit or component, and furthermore they may be divided into a plurality of sub-modules or sub-units or sub-components. All of the features disclosed in this specification (including any accompanying claims, abstract and drawings), and all of the processes or elements of any method or apparatus so disclosed, may be combined in any combination, except combinations where at least some of such features and/or processes or elements are mutually exclusive. Each feature disclosed in this specification (including any accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.
Furthermore, those skilled in the art will appreciate that while some embodiments described herein include some features included in other embodiments, rather than other features, combinations of features of different embodiments are meant to be within the scope of the invention and form different embodiments. For example, in the following claims, any of the claimed embodiments may be used in any combination.
The various component embodiments of the invention may be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. Those skilled in the art will appreciate that a microprocessor or Digital Signal Processor (DSP) may be used in practice to implement some or all of the functionality of some or all of the components in an electronic device according to embodiments of the present invention. The present invention may also be embodied as apparatus or device programs (e.g., computer programs and computer program products) for performing a portion or all of the methods described herein. Such programs implementing the present invention may be stored on computer-readable media or may be in the form of one or more signals. Such a signal may be downloaded from an internet website or provided on a carrier signal or in any other form.
It should be noted that the above-mentioned embodiments illustrate rather than limit the invention, and that those skilled in the art will be able to design alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The invention may be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means may be embodied by one and the same item of hardware. The usage of the words first, second and third, etcetera do not indicate any ordering. These words may be interpreted as names.
The invention also discloses A1. a data acquisition method, which comprises the following steps:
determining each preset component related to user interaction behavior contained in a target application, monitoring the life cycle of each preset component, and determining a page corresponding to the preset component in the current state as a target page;
determining each preset view control contained in a preset component corresponding to the target page, and monitoring each preset view control to determine a user interaction event corresponding to the target page;
and acquiring user behavior data corresponding to the target application according to the target page and the user interaction event corresponding to the target page.
A2. The method according to a1, wherein the determining each preset component associated with the user interaction behavior included in the target application includes:
determining an activity component which is contained in the target application, is used for interacting with a user and contains a user interface as a first type of preset component; and/or the presence of a gas in the gas,
determining a fragment component contained in the target application and realized based on the first type of preset component as a second type of preset component;
and determining the first type of preset components and/or the second type of preset components as the preset components which are contained in the target application and are associated with the user interaction behaviors.
A3. The method according to a1 or 2, wherein the monitoring the lifecycle of each preset component, and determining a page corresponding to a preset component in a current state belonging to a preset state as a target page includes:
monitoring the life cycle of each preset component through a preset life cycle callback interface, and acquiring the preset component of which the current state belongs to the preset state;
and determining the page corresponding to the preset component of which the current state belongs to the preset state as a target page.
A4. The method according to any one of a1-3, wherein the preset states include: create, restore and/or stop states; and the determining, as the target page, the page corresponding to the preset component of which the current state belongs to the preset state specifically includes:
determining a page corresponding to a preset component of which the current state belongs to a preset state as a candidate target page;
and determining the page in the operable state of the user in the candidate target pages as a target page.
A5. The method according to any one of a1-4, wherein, after determining the page corresponding to the preset component of which the current state belongs to the preset state as the target page, the method further includes:
determining page identification, display time, closing time, display duration and/or display sequence of each target page to obtain page attribute data corresponding to each target page; the user behavior data comprises the page attribute data.
A6. The method according to any one of a1-5, wherein the determining each preset view control included in the preset component corresponding to the target page includes:
traversing each control contained in a preset assembly corresponding to the target page, and determining the control with the control type matched with a preset view type as the preset view control; and/or the presence of a gas in the gas,
traversing each control contained in a preset assembly corresponding to the target page, and determining the control with the control attribute matched with a preset interaction attribute as the preset view control;
wherein the preset view type includes: a list class view type; the preset interaction attribute comprises: clickable properties and/or long press properties.
A7. The method according to any one of a1-6, wherein the listening for the respective preset view control includes: and monitoring each preset view control through a preset gesture monitoring interface.
A8. The method of any of a1-7, wherein the user behavior data includes: event attribute information of the user interaction event corresponding to the target page; wherein the event attribute information includes: event type, event time, and event object.
B9. A data acquisition device comprising:
the component monitoring module is suitable for determining each preset component which is contained in the target application and is associated with the user interaction behavior, monitoring the life cycle of each preset component, and determining a page corresponding to the preset component of which the current state belongs to the preset state as a target page;
the control monitoring module is suitable for determining each preset view control contained in a preset component corresponding to the target page and monitoring each preset view control so as to determine a user interaction event corresponding to the target page;
and the acquisition module is suitable for acquiring user behavior data corresponding to the target application according to the target page and the user interaction event corresponding to the target page.
B10. The apparatus of B9, wherein the component listening module is specifically adapted to:
determining an activity component which is contained in the target application, is used for interacting with a user and contains a user interface as a first type of preset component; and/or the presence of a gas in the gas,
determining a fragment component contained in the target application and realized based on the first type of preset component as a second type of preset component;
and determining the first type of preset components and/or the second type of preset components as the preset components which are contained in the target application and are associated with the user interaction behaviors.
B11. The apparatus according to B9 or 10, wherein the component listening module is specifically adapted to:
monitoring the life cycle of each preset component through a preset life cycle callback interface, and acquiring the preset component of which the current state belongs to the preset state;
and determining the page corresponding to the preset component of which the current state belongs to the preset state as a target page.
B12. The apparatus of any of B9-11, wherein the preset states include: create, restore and/or stop states; and the component listening module is specifically adapted to:
determining a page corresponding to a preset component of which the current state belongs to a preset state as a candidate target page;
and determining the page in the operable state of the user in the candidate target pages as a target page.
B13. The apparatus of any of B9-12, wherein the component listening module is further adapted to:
determining page identification, display time, closing time, display duration and/or display sequence of each target page to obtain page attribute data corresponding to each target page; the user behavior data comprises the page attribute data.
B14. The apparatus according to any of B9-13, wherein the control listening module is specifically adapted to:
traversing each control contained in a preset assembly corresponding to the target page, and determining the control with the control type matched with a preset view type as the preset view control; and/or the presence of a gas in the gas,
traversing each control contained in a preset assembly corresponding to the target page, and determining the control with the control attribute matched with a preset interaction attribute as the preset view control;
wherein the preset view type includes: a list class view type; the preset interaction attribute comprises: clickable properties and/or long press properties.
B15. The apparatus according to any of B9-14, wherein the control listening module is specifically adapted to: and monitoring each preset view control through a preset gesture monitoring interface.
B16. The apparatus of any of B9-15, wherein the user behavior data comprises: event attribute information of the user interaction event corresponding to the target page; wherein the event attribute information includes: event type, event time, and event object.
C17. An electronic device, comprising: the system comprises a processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface complete mutual communication through the communication bus;
the memory is used for storing at least one executable instruction, and the executable instruction causes the processor to execute the operation corresponding to the data acquisition method of any one of A1-8.
D18. A computer storage medium having at least one executable instruction stored therein, the executable instruction causing a processor to perform operations corresponding to the data acquisition method of any one of a 1-8.
Claims (10)
1. A method of data acquisition, comprising:
determining each preset component related to user interaction behavior contained in a target application, monitoring the life cycle of each preset component, and determining a page corresponding to the preset component in the current state as a target page;
determining each preset view control contained in a preset component corresponding to the target page, and monitoring each preset view control to determine a user interaction event corresponding to the target page;
and acquiring user behavior data corresponding to the target application according to the target page and the user interaction event corresponding to the target page.
2. The method of claim 1, wherein the determining respective preset components associated with user interaction behavior contained in the target application comprises:
determining an activity component which is contained in the target application, is used for interacting with a user and contains a user interface as a first type of preset component; and/or the presence of a gas in the gas,
determining a fragment component contained in the target application and realized based on the first type of preset component as a second type of preset component;
and determining the first type of preset components and/or the second type of preset components as the preset components which are contained in the target application and are associated with the user interaction behaviors.
3. The method according to claim 1 or 2, wherein the monitoring for the life cycle of each preset component, and the determining, as the target page, the page corresponding to the preset component in the current state belonging to the preset state comprises:
monitoring the life cycle of each preset component through a preset life cycle callback interface, and acquiring the preset component of which the current state belongs to the preset state;
and determining the page corresponding to the preset component of which the current state belongs to the preset state as a target page.
4. The method according to any one of claims 1-3, wherein the preset state comprises: create, restore and/or stop states; and the determining, as the target page, the page corresponding to the preset component of which the current state belongs to the preset state specifically includes:
determining a page corresponding to a preset component of which the current state belongs to a preset state as a candidate target page;
and determining the page in the operable state of the user in the candidate target pages as a target page.
5. The method according to any one of claims 1 to 4, wherein after determining the page corresponding to the preset component of which the current state belongs to the preset state as the target page, the method further comprises:
determining page identification, display time, closing time, display duration and/or display sequence of each target page to obtain page attribute data corresponding to each target page; the user behavior data comprises the page attribute data.
6. The method according to any one of claims 1-5, wherein the determining each preset view control contained in the preset component corresponding to the target page comprises:
traversing each control contained in a preset assembly corresponding to the target page, and determining the control with the control type matched with a preset view type as the preset view control; and/or the presence of a gas in the gas,
traversing each control contained in a preset assembly corresponding to the target page, and determining the control with the control attribute matched with a preset interaction attribute as the preset view control;
wherein the preset view type includes: a list class view type; the preset interaction attribute comprises: clickable properties and/or long press properties.
7. The method according to any one of claims 1-6, wherein said listening for said respective preset view controls comprises: and monitoring each preset view control through a preset gesture monitoring interface.
8. A data acquisition device comprising:
the component monitoring module is suitable for determining each preset component which is contained in the target application and is associated with the user interaction behavior, monitoring the life cycle of each preset component, and determining a page corresponding to the preset component of which the current state belongs to the preset state as a target page;
the control monitoring module is suitable for determining each preset view control contained in a preset component corresponding to the target page and monitoring each preset view control so as to determine a user interaction event corresponding to the target page;
and the acquisition module is suitable for acquiring user behavior data corresponding to the target application according to the target page and the user interaction event corresponding to the target page.
9. An electronic device, comprising: the system comprises a processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface complete mutual communication through the communication bus;
the memory is used for storing at least one executable instruction, and the executable instruction causes the processor to execute the operation corresponding to the data acquisition method of any one of claims 1-7.
10. A computer storage medium having stored therein at least one executable instruction for causing a processor to perform operations corresponding to the data acquisition method of any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910272225.5A CN111782490A (en) | 2019-04-04 | 2019-04-04 | Data acquisition method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910272225.5A CN111782490A (en) | 2019-04-04 | 2019-04-04 | Data acquisition method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111782490A true CN111782490A (en) | 2020-10-16 |
Family
ID=72755161
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910272225.5A Pending CN111782490A (en) | 2019-04-04 | 2019-04-04 | Data acquisition method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111782490A (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112364267A (en) * | 2020-10-21 | 2021-02-12 | 杭州大搜车汽车服务有限公司 | Front-end data acquisition method and device |
| CN113254338A (en) * | 2021-05-25 | 2021-08-13 | 深圳前海微众银行股份有限公司 | Test case generation method, device and equipment |
| CN113282865A (en) * | 2021-06-24 | 2021-08-20 | 广州欢网科技有限责任公司 | Page access data acquisition method and device |
| CN113434800A (en) * | 2021-06-28 | 2021-09-24 | 青岛海尔科技有限公司 | Data processing method and device |
-
2019
- 2019-04-04 CN CN201910272225.5A patent/CN111782490A/en active Pending
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112364267A (en) * | 2020-10-21 | 2021-02-12 | 杭州大搜车汽车服务有限公司 | Front-end data acquisition method and device |
| CN112364267B (en) * | 2020-10-21 | 2023-04-07 | 杭州大搜车汽车服务有限公司 | Front-end data acquisition method and device |
| CN113254338A (en) * | 2021-05-25 | 2021-08-13 | 深圳前海微众银行股份有限公司 | Test case generation method, device and equipment |
| CN113282865A (en) * | 2021-06-24 | 2021-08-20 | 广州欢网科技有限责任公司 | Page access data acquisition method and device |
| CN113434800A (en) * | 2021-06-28 | 2021-09-24 | 青岛海尔科技有限公司 | Data processing method and device |
| CN113434800B (en) * | 2021-06-28 | 2023-06-09 | 青岛海尔科技有限公司 | Data processing method and device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111782490A (en) | Data acquisition method and device | |
| US11119897B2 (en) | System and method of handling complex experiments in a distributed system | |
| US10996947B2 (en) | Diagnosing production applications | |
| US9372782B1 (en) | Dynamic tracing framework for debugging in virtualized environments | |
| US8122292B2 (en) | Debugging of business flows deployed in production servers | |
| US20150006961A1 (en) | Capturing trace information using annotated trace output | |
| CN111488109A (en) | Method, device, terminal and storage medium for acquiring control information of user interface | |
| CN114880159B (en) | Data processing method, device, equipment and storage medium | |
| CN115422063A (en) | Low-code interface automation system, electronic equipment and storage medium | |
| US20180316587A1 (en) | Automated analysis and recommendations for highly performant single page web applications | |
| CN111831542A (en) | API application debugging method and device and storage medium | |
| US11580228B2 (en) | Coverage of web application analysis | |
| CN113220403B (en) | Method and device for h5 intercepting Android return event and electronic equipment | |
| CN112559525B (en) | Data checking system, method, device and server | |
| US20140123126A1 (en) | Automatic topology extraction and plotting with correlation to real time analytic data | |
| CN107451038B (en) | Hardware event acquisition method, processor and computing system | |
| CN108228319A (en) | A kind of Semantics Reconstruction method based on more bridges | |
| CN112015714A (en) | Database-based data model generation method and device | |
| WO2020073200A1 (en) | Program debugging method and system | |
| CN110311806A (en) | A kind of mobile applications interface operating lag diagnostic method, system and terminal | |
| US10496524B2 (en) | Separating test coverage in software processes using shared memory | |
| CN113467867B (en) | Information processing method, information processing device, electronic equipment and storage medium | |
| GB2560749A (en) | Trace data representation | |
| CN113239251A (en) | Processing method of buried point data, related device and storage medium | |
| CN111444057A (en) | Page performance data acquisition method and device and computing equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |