CN108228433B - Electronic equipment, and method and device for counting visit time and stay time of mobile application - Google Patents
Electronic equipment, and method and device for counting visit time and stay time of mobile application Download PDFInfo
- Publication number
- CN108228433B CN108228433B CN201611154874.8A CN201611154874A CN108228433B CN 108228433 B CN108228433 B CN 108228433B CN 201611154874 A CN201611154874 A CN 201611154874A CN 108228433 B CN108228433 B CN 108228433B
- Authority
- CN
- China
- Prior art keywords
- log
- mobile application
- visit
- leaving
- server
- 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.)
- Active
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/3466—Performance evaluation by tracing or monitoring
- G06F11/3476—Data logging
-
- 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/3409—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 for performance assessment
- G06F11/3419—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 for performance assessment by assessing time
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)
- Telephonic Communication Services (AREA)
Abstract
The disclosure relates to a mobile application visit dwell time statistical method and a device, wherein the method comprises the following steps: when the starting of a preset mobile application is monitored, collecting a starting log of the preset mobile application; when the preset mobile application leaves the front end, collecting a leaving log of the preset mobile application and sending the leaving log to a server; receiving the leaving log through the server and judging whether the currently received leaving log and the leaving log stored on the server belong to the same visit; when the currently received departure log and the departure log stored on the server belong to the same visit, covering the departure log stored on the server with the currently received departure log; and calculating the visit stay time of the preset mobile application through the starting log and the leaving log stored on the server. The log collection amount is reduced, and the visit retention time is more accurate; when the page is crashed or abnormal, the visit time staying duration can be accurately counted.
Description
Technical Field
The disclosure relates to the technical field of mobile internet, in particular to a mobile application visit stay time statistical method, a mobile application visit stay time statistical device and electronic equipment.
Background
At present, a mobile APP (Application) has become an important marketing entrance of a company, and in order to better perform objective, accurate and visual description on a target user and thus make a dedicated marketing scheme, the collection of behavior data of the user on the APP also becomes more important. During the analysis of the operation and maintenance APP, it is concerned how long the user stays in one visit after the user arrives at the APP, what the user visits in the visit, and for what reason the user leaves the APP. In the prior art, information about how long a user stays after coming to an APP for one visit can be obtained through visit stay duration statistics.
The existing mobile application visit dwell time statistical method comprises the following steps:
embedding an SDK (Software Development Kit) in an APP (application), simultaneously performing log embedding on each page, recording a request log of the page when each page is loaded, recording the request time of the page in the request log, and taking the difference between the request time of the last page and the request time of the first page in the same visit as the visit stay time; the method has the basic principle that the open time of each page is tracked and recorded through the SDK and the log embedded point, and the open time difference between the first page and the last page in the visit is used as the visit stay time. The disadvantages of this method include: embedding points in all pages in an APP, and calling an SDK (software development kit) to acquire log information of a current page when the page starts; a large number of logs are needed to be analyzed to find out the first page and the last page in the same visit, and then the time difference is calculated; the state of the last page leaving cannot be captured, the accurate leaving time of the last page cannot be obtained, and the visiting time staying time is inaccurate.
Embedding an SDK tool in the APP, simultaneously performing log embedding on each page, recording a request log of each page when each page is opened, recording a leaving log of a current page and the request log of a new page when a new page is opened, and summarizing access time stay duration according to the stay duration of the current page (namely the difference between the starting time and the ending time of the page); the method has the basic principle that the open time and the close time of each page are tracked and recorded through the SDK and the log embedded point, the stay time of each page is calculated, and the visit stay time is obtained by summarizing the stay time of each page. The disadvantages of this method include: embedding points in all pages in an APP, and calling an SDK (software development kit) to acquire log information of a current page when the page starts and ends; it needs to analyze through a large amount of logs to find the first page and the last page in the same visit, and then calculate the time difference.
From the above, it is necessary to provide a new mobile application visit duration statistical scheme.
It is to be noted that the information disclosed in the above background section is only for enhancement of understanding of the background of the present disclosure, and thus may include information that does not constitute prior art known to those of ordinary skill in the art.
Disclosure of Invention
An object of the present disclosure is to provide a mobile application visit duration statistical method, a mobile application visit duration statistical apparatus and an electronic device, thereby overcoming, at least to some extent, one or more problems caused by the limitations and disadvantages of the related art.
According to one aspect of the disclosure, a mobile application visit dwell time statistical method is provided, and the mobile application visit dwell time statistical method includes:
when monitoring that a preset mobile application is started, collecting a starting log of the preset mobile application;
when the preset mobile application leaves the front end, collecting a leaving log of the preset mobile application and sending the leaving log to a server;
receiving the leaving log through the server and judging whether the leaving log received currently and the leaving log stored on the server belong to the same visit time or not;
when the currently received departure log and the departure log stored on the server belong to the same visit, covering the departure log stored on the server by using the currently received departure log; and
and calculating the visit dwell time of the preset mobile application through the starting log and the leaving log stored on the server.
In an exemplary embodiment of the present disclosure, the start log includes device identification information, access time information, and start time of a terminal device running the preset mobile application;
the leaving log comprises equipment identification information, access time information, starting time and leaving time of the terminal equipment running the preset mobile application.
In an exemplary embodiment of the present disclosure, the device identification information includes one or more of a hardware address, a mobile device international identity code, and a device identification code.
In an exemplary embodiment of the present disclosure, it is determined whether the currently received departure log and the departure log stored on the server belong to the same visit through the device identification information and the visit information.
In an exemplary embodiment of the present disclosure, the visit dwell time of the preset mobile application is calculated according to the start time in the start log and the departure time in the departure log stored on the server.
In an exemplary embodiment of the present disclosure, the preset mobile application leaving the front end includes one or more of the preset mobile application being closed, turned to run in the background, or actively killed.
According to another aspect of the present disclosure, there is also provided a mobile application visit duration statistic apparatus, including:
the system comprises a first log acquisition unit, a second log acquisition unit and a first log processing unit, wherein the first log acquisition unit is used for acquiring a starting log of a preset mobile application when the starting of the preset mobile application is monitored;
the second log acquisition unit is used for acquiring the leaving log of the preset mobile application and sending the leaving log to a server when the fact that the preset mobile application leaves the front end is monitored;
the visit judging unit is used for receiving the leaving log through the server and judging whether the leaving log received currently and the leaving log stored on the server belong to the same visit;
the log storage unit is used for covering the leaving log stored on the server by using the leaving log received currently when the leaving log received currently and the leaving log stored on the server belong to the same visit; and
and the duration calculation unit is used for calculating the visit stay duration of the preset mobile application through the starting log and the leaving log stored on the server.
In an exemplary embodiment of the present disclosure, the start log includes device identification information, access time information, and start time of a terminal device running the preset mobile application;
the leaving log comprises equipment identification information, access time information, starting time and leaving time of the terminal equipment running the preset mobile application.
In an exemplary embodiment of the present disclosure, the device identification information includes one or more of a hardware address, a mobile device international identity code, and a device identification code.
In an exemplary embodiment of the disclosure, the visit number determining unit determines, through the device identification information and the visit number information, whether the currently received departure log and a departure log stored on the server belong to the same visit number.
In an exemplary embodiment of the disclosure, the duration calculation unit calculates the visit dwell duration of the preset mobile application according to the start time in the start log and the departure time in the departure log stored on the server.
In an exemplary embodiment of the present disclosure, the preset mobile application leaving the front end includes one or more of the preset mobile application being closed, turned to run in the background, or actively killed.
According to another aspect of the present disclosure, there is also provided an electronic device including:
a processor; and
a memory for storing executable instructions of the processor;
wherein the processor is configured to perform a mobile application visit dwell duration statistical method according to any one of the above via execution of the executable instructions.
According to the mobile application visit stay time counting method and the mobile application visit stay time counting device, the visit stay time of the preset mobile application is calculated and obtained according to the starting log and the latest departure log by collecting the starting log and the departure log and only including the latest departure log; on one hand, the logs are collected only when the preset movement is started or leaves the front end, so that the collection amount of the logs is reduced, and the computing resources required by operation can be reduced. On the other hand, the currently received departure log is overlaid on the departure log stored on the server, and the departure log stored on the server is the latest departure log, so that the storage capacity of the server is reduced, and the trouble of searching the latest departure log from a plurality of data can be avoided. On the other hand, the visit stay time of the preset mobile application is calculated through the start log and the leave log stored in the server of the same visit, and the start log and the leave log are accurately collected, so that the visit stay time calculated according to the start log and the leave log is more accurate. In another aspect, since the server stores the start log and the latest departure log, the departure time of the page can be accurately counted even when the page is crashed or the page is abnormal.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure. It is to be understood that the drawings in the following description are merely exemplary of the disclosure, and that other drawings may be derived from those drawings by one of ordinary skill in the art without the exercise of inventive faculty.
Fig. 1 schematically shows a flowchart of a mobile application visit dwell duration statistical method according to an example embodiment of the present disclosure.
Fig. 2 schematically shows a flowchart of a mobile application visit dwell duration statistical method for an android system according to an example embodiment of the present disclosure.
Fig. 3 schematically illustrates a mobile application visit dwell duration statistical method for an iOS system flowchart according to an example embodiment of the present disclosure.
Fig. 4 schematically illustrates a block diagram of a mobile application visit duration statistics apparatus according to an example embodiment of the present disclosure.
Fig. 5 schematically illustrates a block diagram of an electronic device of an example embodiment of the disclosure.
Detailed Description
Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many different forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the disclosure. One skilled in the relevant art will recognize, however, that the subject matter of the present disclosure can be practiced without one or more of the specific details, or with other methods, components, devices, steps, and the like. In other instances, well-known technical solutions have not been shown or described in detail to avoid obscuring aspects of the present disclosure.
Furthermore, the drawings are merely schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and thus their repetitive description will be omitted. Some of the block diagrams shown in the figures are functional entities and do not necessarily correspond to physically or logically separate entities. These functional entities may be implemented in the form of software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor devices and/or microcontroller devices.
In an example embodiment of the present disclosure, a mobile application visit dwell duration statistical method is first provided. Referring to fig. 1, the method for counting the visit time dwell time of the mobile application includes the following steps:
step S1, when monitoring that a preset mobile application is started, collecting a starting log of the preset mobile application;
step S2, when the preset mobile application leaves the front end, collecting the leaving log of the preset mobile application and sending the leaving log to a server;
step S3, receiving the leaving log through the server and judging whether the leaving log received currently and the leaving log stored on the server belong to the same visit;
step S4, when judging that the leaving log received currently and the leaving log stored on the server belong to the same visit, covering the leaving log stored on the server by using the leaving log received currently;
step S5, calculating the visit stay duration of the preset mobile application according to the start log and the leave log stored in the server.
According to the mobile application visit dwell time statistical method in the exemplary embodiment, on one hand, the logs are collected only when the preset mobile application is started or leaves the front end, so that the collection amount of the logs is reduced, and the computing resources required by operation can be reduced. On the other hand, the currently received departure log is overlaid on the departure log stored on the server, and the departure log stored on the server is the latest departure log, so that the storage capacity of the server is reduced, and the trouble of searching the latest departure log from a plurality of data can be avoided. On the other hand, the visit stay time of the preset mobile application is calculated through the start log and the leave log stored in the server of the same visit, and the start log and the leave log are accurately collected, so that the visit stay time calculated according to the start log and the leave log is more accurate. In another aspect, since the server stores the start log and the latest departure log, the departure time of the page can be accurately counted even when the page is crashed or the page is abnormal.
Next, the mobile application visit duration statistical method in the present exemplary embodiment will be further explained.
In step S1, when it is detected that a preset mobile application is started, a start log of the preset mobile application is collected.
In this example embodiment, an SDK tool may be embedded in the preset movement of the mobile device in advance, and a code that the application is closed, changed to run in the background, or actively killed is loaded in the SDK, and when the user closes, changes the application to run in the background, or actively kills the application, the code is executed to complete the collection of the start log and the leave log. The preset mobile application refers to an application which needs to acquire visit dwell time information. The start log of the preset mobile application may include device identification information, access information, start time, and the like of the terminal device running the preset mobile application; the start log may also include an end time, where the end time is equal to the start time. The device identification information may include one or more of a hardware address (MAC address), an International Mobile Equipment Identity (IMEI), an equipment identity (OpenUDID), and the like. The access time refers to a complete access which is actively killed by the user from the open application; the access information may be the label information of the complete access, and may be labeled as 1, 2, 3 … …, which is only an illustration and is not a limitation of the access information. In addition, in other exemplary embodiments of the present disclosure, the start log may also include other information, which is not particularly limited in this exemplary embodiment.
Referring to fig. 2, taking a mobile device of the android system as an example, when it is monitored by an SDK tool that a preset mobile application is started, the SDK tool may collect a hardware address of the preset mobile application and/or an international identity code of the mobile device, access information, and start time, and send the information to a server. Referring to fig. 3, taking the mobile device of the iOS system as an example, when it is monitored that a preset mobile application is started through the SDK tool, the SDK tool may collect the device identification code, access information, and start time of the preset mobile application, and send the information to the server. When the preset mobile application is started, the information of the mobile equipment is determined through one or more of the hardware address, the international identity code of the mobile equipment and the equipment identification code, and the access information and the starting time are recorded in the server.
In step S2, when it is monitored that the preset mobile application leaves the front end, a leaving log of the preset mobile application is collected and sent to a server.
In this example embodiment, the preset mobile application leaving the front end may include one or more of the preset mobile application being closed, turned to run in the background, or being actively killed, etc. The departure log of the preset mobile application may include device identification information, access information, start time, departure time, and the like of the terminal device running the preset mobile application. The device identification information may include one or more of a hardware address, an international mobile equipment identity, a device identification number, and the like. In addition, in other exemplary embodiments of the present disclosure, the leaving log may also include other information, and the preset mobile application leaving front end may include other information, which is not particularly limited in this exemplary embodiment.
Referring to fig. 2, taking a mobile device of an android system as an example, when a user uses a return key, a home key, or the preset application is in a background state, or the like, the SDK tool monitors that the preset mobile application is one or more of closed, converted into background running, or actively killed, and the like, and then may acquire a hardware address of the preset mobile application and/or an international identity code of the mobile device, access information, start time, leave time, and the like through the SDK tool, and send the information to the server. Referring to fig. 3, taking a mobile device of the iOS system as an example, when a user uses a home key or when a preset mobile application is in a background state, etc., and the SDK tool monitors that the preset mobile application is one or more of closed, converted into a background running, or actively killed, etc., the SDK tool may collect a device identification code, access information, start time, leave time, etc., of the preset mobile application, and send the information to the server.
In the above process, since the log is collected only when the preset movement should be started or left from the front end, the collection amount of the log is reduced, so that the computational resources required for operation can be reduced.
In step S3, the server accepts the departure log and determines whether the currently received departure log and the departure log stored on the server belong to the same visit.
In this exemplary embodiment, for example, the server may determine, through the device identification information and the visit information included in the departure log, whether the currently received departure log and the departure log stored on the server belong to the same visit. The device identification information may include one or more of a hardware address, an international mobile equipment identity, a device identification number, and the like.
Referring to fig. 2, taking a mobile device of an android system as an example, when a hardware address or/and an international identity code of the mobile device and visit information are consistent, a server determines that a currently received departure log and a departure log stored on the server belong to the same visit; and in the case of a difference, the server judges that the currently received departure log and the departure log stored on the server do not belong to the same visit. Referring to fig. 3, taking the mobile device of the iOS system as an example, when the device identification code and the visit information are consistent, the server determines that the currently received departure log and the departure log stored on the server belong to the same visit; and in the case of a difference, the server judges that the currently received departure log and the departure log stored on the server do not belong to the same visit.
In step S4, when it is determined that the currently received departure log and the departure log stored on the server belong to the same visit, the departure log stored on the server is overwritten with the currently received departure log.
For example, in the present exemplary embodiment, when the departure log is received for the first time, the server directly stores the departure log, and when the departure log is received for the second time, the server compares the received departure log for the second time with the received departure log for the first time through step S3, determines whether the received departure log is the same visit, and if the received departure log is determined to be the same visit, overwrites the received departure log for the first time stored on the server with the received departure log for the second time that is currently received; and when the leaving log is received for the third time, judging and covering again until the visit is finished.
The currently received leaving log is overlaid on the leaving log stored on the server, and the leaving logs stored on the server are the latest leaving log, so that the storage capacity of the server is reduced; and the trouble of finding the latest departure log from a large number of data can be avoided.
In step S5, the visit dwell time of the preset mobile application is calculated by the start log and the departure log stored on the server.
In this example embodiment, the server may calculate the visit dwell time of the preset mobile application according to the start time in the start log and the departure time in the departure log stored on the server. Specifically, the difference between the leaving time in the leaving log stored on the server and the starting time in the starting log is the visit dwell time of the preset mobile application.
Compared with the prior art, in the embodiment of the present invention, the visit time stay of the preset mobile application is calculated by the start log and the leave log stored in the server of the same visit, and both the start log and the leave log are accurately collected, so that the visit time stay calculated according to the start log and the leave log is more accurate. Since the server stores the start log and the latest departure log, the departure time of the page can be accurately counted even when the page is crashed or the page is abnormal.
Further, the present exemplary embodiment further provides a mobile application visit duration statistical apparatus corresponding to the mobile application visit duration statistical method. Referring to fig. 4, the mobile application visit time dwell duration counting apparatus includes a first log collection unit 1, a second log collection unit 2, a visit time judgment unit 3, a log storage unit 4, and a duration calculation unit 5. Wherein:
the first log collection unit 1 may be configured to collect a start log of a preset mobile application when it is monitored that the preset mobile application is started.
The second log collecting unit 2 may be configured to collect a leaving log of the preset mobile application and send the leaving log to a server when it is monitored that the preset mobile application leaves the front end.
The visit judging unit 3 may be configured to receive the departure log through the server and judge whether the currently received departure log and the departure log stored in the server belong to the same visit.
The log storage unit 4 may be configured to, when it is determined that the currently received departure log and the departure log stored on the server belong to the same access time, overwrite the departure log stored on the server with the currently received departure log.
The duration calculation unit 5 may be configured to calculate the visit dwell duration of the preset mobile application according to the start log and the leave log stored in the server.
In this example embodiment, the start log may include device identification information, access information, start time, and the like of the terminal device running the preset mobile application; the departure log may include device identification information, access information, start time, departure time, and the like of the terminal device running the preset mobile application.
In this example embodiment, the device identification information may include one or more of a hardware address, an international mobile equipment identity, a device identification number, and the like.
In this exemplary embodiment, the visit determining unit 3 may determine whether the currently received departure log and the departure log stored on the server belong to the same visit by using the device identification information and the visit information. And judging that the mobile terminal belongs to the same access time under the condition that the equipment identification information and the access time information are consistent, and judging that the mobile terminal does not belong to the same access time under the condition that only one is inconsistent.
In this example embodiment, the duration calculation unit 5 may calculate the visit dwell duration of the preset mobile application according to the start time in the start log and the departure time in the departure log stored on the server.
In this example embodiment, the preset mobile application leaving the front end may include one or more of the preset mobile application being closed, turned to run in the background, or being actively killed, etc.
The specific details of each module in the mobile application visit duration statistical apparatus have been described in detail in the corresponding virtual object motion control method, and therefore are not described herein again.
It should be noted that although in the above detailed description several modules or units of the mobile application visit duration statistics apparatus are mentioned, this division is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit, according to embodiments of the present disclosure. Conversely, the features and functions of one module or unit described above may be further divided into embodiments by a plurality of modules or units.
Moreover, although the steps of the methods of the present disclosure are depicted in the drawings in a particular order, this does not require or imply that the steps must be performed in this particular order, or that all of the depicted steps must be performed, to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step execution, and/or one step broken down into multiple step executions, etc.
Referring to fig. 5, an electronic device 600 to which the above-described trusted process identification applies may include one or more of the following components: processing component 602, memory 604, power component 606, multimedia component 608, audio component 610, input/output (I/O) interface 612, sensor component 614, and communication component 616.
The processing component 602 generally controls overall operation of the electronic device 600, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. The processing component 602 may include one or more processors 620 to execute instructions to perform all or a portion of the steps of the methods described above. Further, the processing component 602 can include one or more modules that facilitate interaction between the processing component 602 and other components. For example, the processing component 602 can include a multimedia module to facilitate interaction between the multimedia component 604 and the processing component 602.
The memory 604 is configured to store various types of data to support operation at the device 600. Examples of such data include instructions for any application or method operating on the electronic device 600, contact data, phonebook data, messages, pictures, videos, and so forth. The memory 604 may be implemented by any type or combination of volatile or non-volatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks.
The multimedia component 608 includes a screen that provides an output interface between the electronic device 600 and a user. In some embodiments, the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive an input signal from a user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 608 includes a front facing camera and/or a rear facing camera. The front camera and/or the rear camera may receive external multimedia data when the device 600 is in an operating mode, such as a shooting mode or a video mode. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.
The audio component 610 is configured to output and/or input audio signals. For example, the audio component 610 includes a Microphone (MIC) configured to receive external audio signals when the electronic device 600 is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signal may further be stored in the memory 604 or transmitted via the communication component 616. In some embodiments, audio component 610 further includes a speaker for outputting audio signals.
The I/O interface 612 provides an interface between the processing component 602 and peripheral interface modules, which may be keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to: a home button, a volume button, a start button, and a lock button.
The sensor component 614 includes one or more sensors for providing status assessment of various aspects of the electronic device 600. For example, the sensor component 614 may detect an open/closed state of the device 600, the relative positioning of components, such as a display and keypad of the electronic device 600, the sensor component 614 may also detect a change in the position of the electronic device 600 or a component of the electronic device 600, the presence or absence of user contact with the electronic device 600, orientation or acceleration/deceleration of the electronic device 600, and a change in the temperature of the electronic device 600. The sensor assembly 614 may include a proximity sensor configured to detect the presence of a nearby object without any physical contact. The sensor assembly 614 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 614 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
The communication component 616 is configured to facilitate communications between the electronic device 600 and other devices in a wired or wireless manner. The electronic device 600 may access a wireless network based on a communication standard, such as WiFi, 2G or 6G, or a combination thereof. In an exemplary embodiment, the communication component 616 receives broadcast signals or broadcast related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 616 further includes a Near Field Communication (NFC) module to facilitate short-range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, Ultra Wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.
In an exemplary embodiment, the electronic device 600 may be implemented by one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), controllers, micro-controllers, microprocessors or other electronic components for performing the above-described methods.
Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which may be a personal computer, a server, a mobile terminal, or a network device, etc.) to execute the method according to the embodiments of the present disclosure.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
Claims (14)
1. A mobile application visit dwell duration statistical method is characterized by comprising the following steps:
when monitoring that a preset mobile application is started, acquiring a starting log of the preset mobile application through an SDK (software development kit) embedded in the preset mobile application;
when the preset mobile application leaves the front end, acquiring a leaving log of the preset mobile application through an SDK embedded in the preset mobile application and sending the leaving log to a server; receiving the leaving log through the server and judging whether the leaving log received currently and the leaving log stored on the server belong to the same visit time or not;
when the currently received departure log and the departure log stored on the server belong to the same visit, covering the departure log stored on the server by using the currently received departure log; and
and calculating the visit dwell time of the preset mobile application through the starting log and the leaving log stored on the server.
2. The mobile application visit dwell duration statistical method of claim 1, wherein:
the starting log comprises equipment identification information, access time information and starting time of the terminal equipment running the preset mobile application;
the leaving log comprises equipment identification information, access time information, starting time and leaving time of the terminal equipment running the preset mobile application.
3. The method of claim 2, wherein the device identification information comprises one or more of a hardware address, an international mobile equipment identity (IMSI) code, and a device Identification (IED) code.
4. The method as claimed in claim 2, wherein the device identification information and the visit information are used to determine whether the currently received departure log and the departure log stored in the server belong to the same visit.
5. The method of claim 2, wherein the visit dwell time of the predetermined mobile application is calculated according to the start time in the start log and the departure time in the departure log stored on the server.
6. The method of claim 1, wherein the preset mobile application leaving front end comprises one or more of the preset mobile application being turned off, turned to run in the background, or actively killed.
7. A mobile application visit dwell duration statistical apparatus, comprising:
the system comprises a first log acquisition unit, a second log acquisition unit and a third log acquisition unit, wherein the first log acquisition unit is used for acquiring a starting log of a preset mobile application through an SDK (software development kit) embedded in the preset mobile application when the starting of the preset mobile application is monitored;
the second log acquisition unit is used for acquiring a leaving log of the preset mobile application through an SDK (software development kit) embedded in the preset mobile application and sending the leaving log to a server when the preset mobile application is monitored to leave the front end;
the visit judging unit is used for receiving the leaving log through the server and judging whether the leaving log received currently and the leaving log stored on the server belong to the same visit;
the log storage unit is used for covering the leaving log stored on the server by using the leaving log received currently when the leaving log received currently and the leaving log stored on the server belong to the same visit; and
and the duration calculation unit is used for calculating the visit stay duration of the preset mobile application through the starting log and the leaving log stored on the server.
8. The device of claim 7, wherein:
the starting log comprises equipment identification information, access time information and starting time of the terminal equipment running the preset mobile application;
the leaving log comprises equipment identification information, access time information, starting time and leaving time of the terminal equipment running the preset mobile application.
9. The apparatus of claim 8, wherein the device identification information comprises one or more of a hardware address, an international mobile equipment identity (IMSI) code, and a device Identification (IED) code.
10. The apparatus of claim 8, wherein the visit determining unit determines whether the currently received departure log and a departure log stored in the server belong to the same visit according to the device identification information and the visit information.
11. The mobile application visit dwell duration statistic device of claim 8, wherein the duration calculating unit calculates the visit dwell duration of the preset mobile application according to the start time in the start log and the departure time in the departure log stored on the server.
12. The mobile application visit dwell duration statistic apparatus of claim 7, wherein the preset mobile application departure front end comprises one or more of the preset mobile application being turned off, turned to background running, or actively killed.
13. An electronic device, comprising:
a processor; and
a memory for storing executable instructions of the processor;
wherein the processor is configured to execute the mobile application visit dwell duration statistical method of any one of claims 1-6 via execution of the executable instructions.
14. A storage medium having executable instructions stored thereon, wherein the executable instructions are executable by a computing device to implement a mobile application visit dwell duration statistical method as claimed in any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611154874.8A CN108228433B (en) | 2016-12-14 | 2016-12-14 | Electronic equipment, and method and device for counting visit time and stay time of mobile application |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611154874.8A CN108228433B (en) | 2016-12-14 | 2016-12-14 | Electronic equipment, and method and device for counting visit time and stay time of mobile application |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108228433A CN108228433A (en) | 2018-06-29 |
| CN108228433B true CN108228433B (en) | 2021-05-25 |
Family
ID=62651104
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201611154874.8A Active CN108228433B (en) | 2016-12-14 | 2016-12-14 | Electronic equipment, and method and device for counting visit time and stay time of mobile application |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108228433B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112165458B (en) * | 2020-09-07 | 2023-04-18 | 中国联合网络通信集团有限公司 | Real-name authentication method, device and terminal |
| CN117632688A (en) * | 2024-01-25 | 2024-03-01 | 太平金融科技服务（上海）有限公司 | Data processing method, device, equipment and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103023984A (en) * | 2012-11-23 | 2013-04-03 | 青岛海信传媒网络技术有限公司 | Terminal application server and application log filtering method thereof |
| CN103078954A (en) * | 2013-01-28 | 2013-05-01 | 广东欧珀移动通信有限公司 | Remote monitoring method of mobile terminal, mobile terminal and control terminal |
| CN104615525A (en) * | 2013-11-01 | 2015-05-13 | 腾讯科技（深圳）有限公司 | Method and device for detecting running time of application programs in mobile terminal |
| CN104850409A (en) * | 2015-06-05 | 2015-08-19 | 北京京东尚科信息技术有限公司 | Webpage staying duration statistic method |
| CN106201841A (en) * | 2016-06-24 | 2016-12-07 | 青岛海信移动通信技术股份有限公司 | The statistical method of a kind of application program service data and device |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9144075B2 (en) * | 2012-06-13 | 2015-09-22 | All Purpose Networks LLC | Baseband data transmission and reception in an LTE wireless base station employing periodically scanning RF beam forming techniques |
| US9697545B1 (en) * | 2014-03-11 | 2017-07-04 | Vmware, Inc. | Service monitor for monitoring and tracking the performance of an application running on different mobile devices |
| CN105188060A (en) * | 2015-10-12 | 2015-12-23 | 深圳竹云科技有限公司 | Mobile terminal-oriented single sign-on (SSO) authentication method and system |
-
2016
- 2016-12-14 CN CN201611154874.8A patent/CN108228433B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103023984A (en) * | 2012-11-23 | 2013-04-03 | 青岛海信传媒网络技术有限公司 | Terminal application server and application log filtering method thereof |
| CN103078954A (en) * | 2013-01-28 | 2013-05-01 | 广东欧珀移动通信有限公司 | Remote monitoring method of mobile terminal, mobile terminal and control terminal |
| CN104615525A (en) * | 2013-11-01 | 2015-05-13 | 腾讯科技（深圳）有限公司 | Method and device for detecting running time of application programs in mobile terminal |
| CN104850409A (en) * | 2015-06-05 | 2015-08-19 | 北京京东尚科信息技术有限公司 | Webpage staying duration statistic method |
| CN106201841A (en) * | 2016-06-24 | 2016-12-07 | 青岛海信移动通信技术股份有限公司 | The statistical method of a kind of application program service data and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108228433A (en) | 2018-06-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20170300503A1 (en) | Method and apparatus for managing video data, terminal, and server | |
| EP3316136B1 (en) | Method and device for evaluating system fluency, and ue | |
| CN109298995B (en) | Performance test method and device, electronic equipment and storage medium | |
| CN104866409A (en) | Method and apparatus for monitoring memory leakage | |
| CN104836924A (en) | Number marking method and device | |
| CN105404576A (en) | Anomaly information acquisition method and apparatus | |
| CN103914337A (en) | Service calling method, device and terminal | |
| CN111614990B (en) | Method and device for acquiring loading duration and electronic equipment | |
| CN107316207B (en) | Method and device for acquiring display effect information | |
| CN112256563A (en) | Android application stability testing method and device, electronic equipment and storage medium | |
| CN108965606B (en) | Method and device for determining ambient temperature | |
| CN108228433B (en) | Electronic equipment, and method and device for counting visit time and stay time of mobile application | |
| CN104932970A (en) | Monitoring method and device of memory leakage | |
| CN107158685B (en) | Exercise verification method and apparatus | |
| CN105657658A (en) | Gathering event processing method and apparatuses | |
| CN110213062B (en) | Method and device for processing message | |
| CN111611470A (en) | Data processing method and device and electronic equipment | |
| CN113420205B (en) | Method and device for determining shared source account, terminal equipment and server | |
| CN106354595B (en) | Mobile terminal, hardware component state detection method and device | |
| CN110866147B (en) | Method, apparatus and storage medium for classifying live broadcast application | |
| CN113568543A (en) | Information processing method, information processing device, electronic equipment and storage medium | |
| CN113568828A (en) | Abnormal terminal equipment identification method and device, electronic equipment and storage medium | |
| CN108418878B (en) | Notification message pushing method and device, readable storage medium and electronic equipment | |
| CN106155863A (en) | Terminal anticipatory behavior control method and terminal | |
| CN112231132A (en) | Application program jamming positioning method and device, electronic equipment and medium |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |