CN108235308B

CN108235308B - Data reporting method and device, mobile terminal and computer readable medium

Info

Publication number: CN108235308B
Application number: CN201711445555.7A
Authority: CN
Inventors: 张建都
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2017-12-27
Filing date: 2017-12-27
Publication date: 2021-06-15
Anticipated expiration: 2037-12-27
Also published as: CN108235308A

Abstract

The embodiment of the application discloses a data reporting method, a data reporting device, a mobile terminal and a computer readable medium, wherein the method comprises the following steps: acquiring information of an application program corresponding to data to be reported; acquiring a data acquisition component corresponding to the data to be reported according to the information of the application program corresponding to the data to be reported; and sending the data to be reported to a server according to the data acquisition component. Therefore, different application programs adopt different data acquisition components to acquire data and send the data to the server according to different information, and the flexibility and diversity of data acquisition of the application programs are improved.

Description

Data reporting method and device, mobile terminal and computer readable medium

Technical Field

The present application relates to the field of information processing technologies, and in particular, to a data reporting method and apparatus, a mobile terminal, and a computer readable medium.

Background

At present, mobile terminals such as mobile phones and tablet computers are increasingly popularized, the functions of the mobile terminals are also increasingly powerful, people can make calls and send short messages by using the mobile terminals, can also watch webpages, send microblogs and the like by using the mobile terminals, a large amount of information related to users and data generated by the mobile terminals during operation can be stored in the mobile terminals, and the behaviors of the users and the operation conditions of the mobile terminals can be analyzed by collecting the data.

The existing data acquisition method is to unify data interfaces of different applications so as to realize the acquisition of data of various applications by using one interface, but the acquisition mode is too single.

Disclosure of Invention

The application provides a data reporting method, a data reporting device, a mobile terminal and a computer readable medium, so as to overcome the defects.

In a first aspect, an embodiment of the present application provides a data reporting method, including: acquiring information of an application program corresponding to data to be reported; acquiring a data acquisition component corresponding to the data to be reported according to the information of the application program corresponding to the data to be reported; and sending the data to be reported to a server according to the data acquisition component.

In a second aspect, an embodiment of the present application further provides a data reporting apparatus, including: the device comprises a first acquisition unit, a second acquisition unit and a sending unit. The first obtaining unit is used for obtaining the information of the application program corresponding to the data to be reported. And the second acquisition unit is used for acquiring the data acquisition component corresponding to the data to be reported according to the information of the application program corresponding to the data to be reported. And the sending unit is used for sending the data to be reported to a server according to the data acquisition component.

In a third aspect, an embodiment of the present application further provides a mobile terminal, which includes a memory and a processor, where the memory is coupled with the processor. The memory stores instructions that, when executed by the processor, cause the processor to: acquiring information of an application program corresponding to data to be reported; acquiring a data acquisition component corresponding to the data to be reported according to the information of the application program corresponding to the data to be reported; and sending the data to be reported to a server according to the data acquisition component.

In a fourth aspect, the present application also provides a computer-readable medium having program code executable by a processor, where the program code causes the processor to execute the above method.

According to the data reporting method and device, the mobile terminal and the computer readable medium provided by the embodiment of the application, firstly, information of an application program corresponding to data to be reported is obtained, a data acquisition component corresponding to the data to be reported is determined according to the information of the application program corresponding to the data to be reported, and then the data to be reported is sent to a server through the data acquisition component. Therefore, different application programs adopt different data acquisition components to acquire data and send the data to the server according to different information, and the flexibility and diversity of data acquisition of the application programs are improved.

Additional features and advantages of embodiments of the present application will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by the practice of embodiments of the present application. The objectives and other advantages of the embodiments of the application may be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

Fig. 1 shows an application scenario diagram of a data reporting method and apparatus provided in the embodiment of the present application;

fig. 2 is a flowchart illustrating a method for reporting data according to an embodiment of the present application;

fig. 3 is a flowchart illustrating a method for reporting data according to another embodiment of the present application;

fig. 4 shows a block diagram of a data reporting apparatus according to an embodiment of the present application;

fig. 5 is a block diagram of a data reporting apparatus according to another embodiment of the present application;

fig. 6 shows a schematic structural diagram of a mobile terminal provided in an embodiment of the present application;

fig. 7 shows a block diagram of modules of a mobile terminal according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. The components of the embodiments of the present application, generally described and illustrated in the figures herein, can be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of the present application, presented in the accompanying drawings, is not intended to limit the scope of the claimed application, but is merely representative of selected embodiments of the application. All other embodiments, which can be derived by a person skilled in the art from the embodiments of the present application without making any creative effort, shall fall within the protection scope of the present application.

It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures. Meanwhile, in the description of the present application, the terms "first", "second", and the like are used only for distinguishing the description, and are not to be construed as indicating or implying relative importance.

Fig. 1 shows an application scenario diagram of the data reporting method and apparatus provided in the embodiment of the present application. As shown in fig. 1, a user terminal 1 and a server 2 are located in a wireless network or a wired network, and the user terminal 1 and the server 2 perform data interaction.

In the embodiment of the present application, the user terminal 1 may be a mobile terminal device, and may include, for example, a smart phone, a tablet computer, an e-book reader, a laptop portable computer, a vehicle-mounted computer, a wearable mobile terminal, and the like.

In some embodiments, the client is installed within the user terminal 1. Specifically, the client may be an application installed in the user terminal 1. The operation of the user aiming at the client and the operation data of the client can be reported to the server. Specifically, data corresponding to the client may be sent to the server through the SDK component or the system acquisition component.

Wherein the SDK component is installed in the client, bound with the client and can be updated along with the update of the client. The SDK component is used for providing an access interface for other application programs to access data of the client, and can also actively acquire the data of the client and send the data to other clients or terminals. The System acquisition component is an acquisition tool carried by a System of the user terminal, and for example, the System acquisition tool can be a Data Collection System (DCS), and is generally updated according to the update of the System.

The server 2 is provided with a storage space for storing data of the client, for managing, storing user data, and providing user services. The server 2 may be an individual server, or a server cluster, or a local server, or a cloud server.

In some embodiments, the SDK component is used to collect data of clients bound to it, and the system collection component can collect data of various clients within the user terminal. In the current data acquisition, data interfaces of different applications are often unified so as to realize the acquisition of data of various applications by using one interface, but the acquisition mode is too single.

Therefore, in order to overcome the above-mentioned drawbacks, please refer to fig. 2, which shows that the present application provides a data reporting method for improving the diversity of data acquisition. Specifically, the method comprises the following steps: s201 to S203.

S201: and acquiring information of an application program corresponding to the data to be reported.

The application program is installed in the mobile terminal, a local storage space is arranged in the mobile terminal and used for storing the data to be reported of the application program, and the information of the application program corresponds to the data to be reported, wherein the information of the application program can be the identification, the type and the like of the application program. The data to be reported includes running data of the application program, for example, start or exit of the application program, and also includes operation behavior data of the user for the application program, for example, closing a certain interface or inputting certain information. As an implementation manner, a plurality of buried points are set in the application program, each buried point represents an operation behavior of a user for the application program or an operation state of the application program, for example, the start of the application program is used as one buried point, the user opens a certain interface of the application program as one buried point, and when the behaviors occur, that is, the buried points are triggered, corresponding data can be stored in a local storage space corresponding to the application program, and the corresponding data is stored locally as data to be reported of the application program.

Therefore, when the data of the application program to be collected is determined, the information of the application program corresponding to the data to be reported is obtained according to the corresponding relation between the data in the local storage space and the application program.

S202: and acquiring a data acquisition component corresponding to the data to be reported according to the information of the application program corresponding to the data to be reported.

As an embodiment, the information of the application program may be an identifier of the application program, wherein the identifier may be a name or a package name. As an embodiment, a correspondence table between the identifiers of the applications and the data acquisition components may be preset, where the correspondence table includes the identifiers of the multiple applications and the data acquisition component corresponding to the identifier of each application. As shown in table 1:

identification of applications	Type of application	Data acquisition assembly
			APK1	System applications	DCS
APK2	Third party applications	SDK
			APK3	Third party applications	SDK
APK4	Third party applications	SDK

Therefore, according to the correspondence table, a data acquisition component corresponding to the identifier of the application program corresponding to the data to be reported is searched in the correspondence table, for example, the data acquisition component corresponding to the application program of the identifier APK1 is a DCS, that is, a system acquisition component, and the data acquisition component corresponding to the application program of the identifier APK2 is an SDK component.

As another embodiment, a data acquisition component is configured for the application program corresponding to the data to be reported according to whether the type of the application program is a self-upgrade type. Specifically, the acquiring the data acquisition component corresponding to the data to be reported according to the information of the application program corresponding to the data to be reported includes: judging whether the type of the application program belongs to a self-upgrading type; if so, setting the data acquisition component corresponding to the data to be reported as an SDK component; and if not, setting the data acquisition component corresponding to the data to be reported as a system acquisition component.

The self-upgrading type application program can be upgraded by itself when an operating system of the mobile terminal is not upgraded, and system applications and the system belong to a strong coupling relation and generally cannot be upgraded automatically or do not have the automatic upgrading capability, such as a camera, and the self-upgrading type application program is strongly dependent on hardware and a system of the mobile terminal. Thus, applications belonging to the system application type may be defined as non-self-upgrade type, while third party applications are defined as self-upgrade type. If the type of the application program corresponding to the data to be reported belongs to a self-upgrade type, setting the data acquisition assembly corresponding to the data to be reported as an SDK assembly, and if the type of the application program corresponding to the data to be reported belongs to a non-self-upgrade type, setting the data acquisition assembly corresponding to the data to be reported as a system acquisition assembly.

S203: and sending the data to be reported to a server according to the data acquisition component.

And if the data acquisition component corresponding to the data to be reported is the SDK component, acquiring the data to be reported through the SDK component, and sending the acquired data to be reported to a server. As an implementation manner, it may be determined whether an application corresponding to the data to be reported meets a preset reporting condition, and if so, the data to be reported is collected by the SDK component, and the collected data to be reported is sent to the server.

Specifically, the application program is installed in the mobile terminal, and the SDK component is bound to the application program and used for collecting and reporting data of the application program. The SDK component determines whether the application satisfies a preset reporting condition according to a preset policy, for example, the SDK component may send data of the application to the server according to a preset interval. Specifically, when it is determined that a time interval between the current time and the time point of the last data transmission satisfies a preset interval, it is determined that the application satisfies a preset reporting condition.

Or, when the data length of the data to be reported of the application program meets a certain value, the data of the application program is sent to the server. Specifically, the data length of the data to be reported of the application program at the current moment is obtained; judging whether the data length is larger than a preset length or not; and if so, judging that the application program meets the preset reporting condition.

It should be noted that the data in the data to be reported is related to the history of the SDK component collecting and sending the data of the application program, for example, after the application program is started, the generated data a is stored locally, and the SDK component sends a to the server as the data to be reported, and then, as the application program continues to run, data B is generated, the data in the local storage space of the application program are a and B, but the data a has already been sent to the server, and the data to be reported this time is B.

A preset length is preset, wherein the data length may be a byte number of data, for example, 3 mbytes, or may be a number of pieces of data, for example, 30 pieces. And the SDK component can monitor the data length of the data to be reported of the application program in real time. For example, after the SDK component sends the data of the application program to the server for the last time, the length of the data to be reported is 0, the data length of the data to be reported of the application program is gradually increased and continuously accumulated along with the operation of the application program, and after the data is accumulated to the preset length, the SDK component determines that the application program meets the preset reporting condition. Therefore, after the SDK component sends the data of the application program for the last time, and after the data length of the current data to be reported is accumulated to a certain length, the preset reporting condition is met, and then the operation of sending the data to be reported of the application program to the server can be executed.

As another embodiment, it may also be determined that the application satisfies the preset reporting condition when the state of the application is in a certain state. Specifically, whether the state of the application program is switched from a running state to a background state is monitored; and if the situation that the state of the application program is switched from the running state to the background state is monitored, judging that the application program meets the preset reporting condition.

The application program state comprises an operating state, a background state and an exit state, wherein the operating state is that the application program runs on a display interface of the mobile terminal, for example, if an activity of the application degree is in a timeout state, the application program is in the operating state, when a user clicks a home key or a screen locking key, the application program enters the background state, and at the moment, the application program runs in a system background. If the process of the application is completely killed, the application enters an exit state. When the application program is switched from the running state to the background state, it indicates that the user may use the application program within a period of time, that is, data stored locally by the application program may not change within a period of time, and when the application program enters the background, the data to be reported of the application program may be reported, that is, when it is monitored that the state of the application program is switched from the running state to the background state, it is determined that the application program meets a preset reporting condition.

And if the data acquisition component corresponding to the data to be reported is a system acquisition component, acquiring the data to be reported of the application program through the system acquisition component, and sending the acquired data to be reported to a server.

Specifically, the DCS component sends all the data to be reported of the application program received within a preset time interval to the server. Wherein the preset time interval is a preset time interval, such as 12 hours or 2 hours. The DCS module records the time for sending the data to be reported to the server in the sending record every time, the time for sending the data to be reported to the server last time is obtained in the sending record and recorded as historical time, all the data to be reported in a preset time interval after the historical time is obtained by taking the historical time as a starting point, and all the data to be reported received in the preset time interval are sent to the server.

It should be noted that the mobile terminal may include multiple application programs, each application program corresponds to one SDK component, and each SDK component sends data to be reported of the application program to the server when determining that the corresponding application program meets the preset reporting condition. The DCS component can continuously acquire data to be reported of different application programs in a preset time interval, and then sends the data to be reported of all the application programs received in the preset time interval to the server.

In addition, when the type of the application program is judged to be a self-upgrade type, the data to be reported is collected through the SDK component, the collected data to be reported is sent to the system collection component, and then the received data to be reported is sent to the server through the system collection component.

Referring to fig. 3, it is shown that a data reporting method is provided in the present application, and the method is used for improving diversity of data acquisition. Specifically, the method comprises the following steps: s301 to S310.

S301: and acquiring information of an application program corresponding to the data to be reported.

S302: and judging whether the type of the application program belongs to a self-upgrading type.

S303: and setting the data acquisition component corresponding to the data to be reported as an SDK component.

And if the type of the application program belongs to a self-upgrade type, setting the data acquisition assembly corresponding to the data to be reported as an SDK assembly. Specifically, an SDK component may be set in an application corresponding to the data to be reported, and an SDK component is installed in the application, where the SDK component is used to collect data of the application.

S304: and monitoring whether a data reporting request of the application program is received.

The data reporting request of the application program is a request for instructing the SDK to send data to be reported of the application program, and specifically, the data reporting request may be an operation of a user based on a reporting key of the application program, that is, after the user clicks the reporting key of a certain interface of the application program, the SDK component monitors that the data reporting request of the application program is received.

As another embodiment, the manner of monitoring, by the SDK component, whether the data reporting request of the application program is received may also be that, if the SDK component monitors that a preset event corresponding to the application program occurs, it is determined that the data reporting request of the application program is received.

The preset event is an operation behavior or an operation state corresponding to the application program preset by a user, and when the SDK component monitors that the operation behavior or the operation state corresponding to the application program occurs, the SDK component indicates that the SDK component monitors that the preset event occurs. For example, if the preset event is that a floating window of the application program is clicked, when the user clicks the floating window, it is determined that the preset event corresponding to the application program occurs, and the data to be reported at this time includes data related to the clicking operation of the floating window. Specifically, the predetermined event may be the aforementioned buried point.

S305: and judging whether the received data reporting request is a data reporting request acquired for the first time after the application program is started at this time.

The mobile terminal stores data records corresponding to the application programs, wherein the data records comprise the starting times of the application programs, the starting time, the quitting time, the time for sending the data to be reported each time and the like.

When detecting that the application program is in a running state, it indicates that the application program has been started, and when the starting time of this start is obtained, and then when the currently obtained data reporting request is obtained, it is determined whether there are other data reporting requests between the starting time and the time of the currently obtained data reporting request, and if not, it is determined that the currently obtained data reporting request is the data reporting request that is obtained for the first time after this start of the application program, and the operation of S309 is executed. If the request exists, it is determined that the currently acquired data reporting request is not the data reporting request acquired for the first time after the application program is started this time, that is, is not the data reporting request acquired for the first time, and the operation of S306 is executed.

S306: and acquiring historical sending time of last sending the data to be reported of the application program to the server through the SDK component.

Specifically, the time for sending the data to be reported of the application program to the system acquisition component last time is obtained in the data record corresponding to the application program and is used as the historical sending time.

S307: and acquiring the time interval between the time of the data reporting request received this time and the historical sending time.

S308: and judging whether the time interval is larger than a preset time threshold value or not.

The preset time threshold is set by the user according to the requirement of actual data reporting, and may be, for example, 5 minutes. If the time interval is greater than the preset time threshold, executing S309, if the time interval is not greater than the preset time threshold, ending the method, or returning to executing S307, or of course, reporting data through other logic, for example, acquiring the data length of the data to be reported of the application program at the current time; judging whether the data length is greater than the preset length, if so, executing S309, where a specific implementation manner may refer to the foregoing embodiment, that is, when the preset time threshold is not reached, but the data length is already greater than the preset length, executing S309.

S309: and collecting the data to be reported through the SDK component, and sending the collected data to be reported to a server.

S310: and setting the data acquisition component corresponding to the data to be reported as a system acquisition component.

And if the type of the application program does not belong to a self-upgrading type, namely a non-self-upgrading type, setting the data acquisition component corresponding to the data to be reported as a system acquisition component. Specifically, a management list of a system acquisition component is stored in the mobile terminal, a plurality of identifiers of application programs are stored in the management list, wherein data to be reported corresponding to the application program of each identifier are acquired through the system acquisition component, if the type of the application program does not belong to a self-upgrading type, the identifier of the application program is added to the management list, and the data acquisition component of the data to be reported of the application program is the system acquisition component.

S311: and collecting all data to be reported generated by the application program within a preset time interval through the system collecting assembly, and sending the collected data to be reported to a server.

It should be noted that, for the parts not described in detail in the above steps, reference may be made to the foregoing embodiments, and details are not described herein again.

Referring to fig. 4, a data reporting apparatus 400 for improving diversity of data acquisition is provided in the embodiment of the present application. Specifically, the apparatus includes: a first acquisition unit 401, a second acquisition unit 402 and a transmission unit 403.

A first obtaining unit 401, configured to obtain information of an application program corresponding to data to be reported.

A second obtaining unit 402, configured to obtain, according to information of an application program corresponding to the data to be reported, a data acquisition component corresponding to the data to be reported.

A sending unit 403, configured to send the data to be reported to a server according to the data acquisition component.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

Referring to fig. 5, a data reporting apparatus 500 for improving diversity of data collection is provided in the embodiment of the present application. Specifically, the apparatus includes: a first acquisition unit 501, a second acquisition unit 502 and a transmission unit 503.

A first obtaining unit 501, configured to obtain information of an application program corresponding to data to be reported.

A second obtaining unit 502, configured to obtain, according to information of an application corresponding to the data to be reported, a data acquisition component corresponding to the data to be reported.

Specifically, the second acquiring unit 502 includes: a type judging subunit 5021, a first setting subunit 5022, and a second setting subunit 5023.

A type determining subunit 5021, configured to determine whether the type of the application program belongs to a self-upgrade type.

A first setting subunit 5022, configured to set the data acquisition component corresponding to the data to be reported as an SDK component if the data acquisition component corresponds to the data to be reported.

A second setting subunit 5023, configured to set the data acquisition component corresponding to the data to be reported as a system acquisition component if the data to be reported is not the system acquisition component.

A sending unit 503, configured to send the data to be reported to a server according to the data acquisition component.

Specifically, the transmitting unit 503 includes: a monitoring sub-unit 5031, a first determining sub-unit 5032, a first obtaining sub-unit 5033, a second obtaining sub-unit 5034, a second determining sub-unit 5035, a first sending sub-unit 5036, and a second sending sub-unit 5037.

A monitoring subunit 5031, configured to monitor whether a data reporting request of the application is received.

A first determining sub-unit 5032, configured to determine whether the received data reporting request is a data reporting request that is first obtained after the application is started this time.

A first obtaining sub-unit 5033, configured to obtain historical sending time for sending, to the server, the data to be reported of the application program last time through the SDK component.

A second obtaining sub-unit 5034, configured to obtain a time interval between the time of the data reporting request received this time and the historical sending time.

A second determining sub-unit 5035, configured to determine whether the time interval is greater than a preset time threshold.

The first sending subunit 5036 is configured to collect the data to be reported by using the SDK component, and send the collected data to be reported to the server.

A second sending subunit 5037, configured to collect, by the system acquisition component, all data to be reported generated by the application program within a preset time interval, and send the collected data to be reported to the server.

Referring to fig. 6, based on the method and apparatus, the embodiment of the present application further provides a mobile terminal 100, which includes an electronic body 10, where the electronic body 10 includes a housing 12 and a main display 120 disposed on the housing 12. The housing 12 may be made of metal, such as steel or aluminum alloy. In this embodiment, the main display 120 generally includes a display panel 111, and may also include a circuit or the like for responding to a touch operation performed on the display panel 111. The Display panel 111 may be a Liquid Crystal Display (LCD) panel, and in some embodiments, the Display panel 111 is a touch screen 109.

Referring to fig. 7, in an actual application scenario, the mobile terminal 100 may be used as a smart phone terminal, in which case the electronic body 10 generally further includes one or more processors 102 (only one is shown in the figure), a memory 104, an RF (Radio Frequency) module 106, an audio circuit 110, a sensor 114, an input module 118, and a power module 122. It will be understood by those skilled in the art that the structure shown in fig. 7 is merely illustrative and is not intended to limit the structure of the electronic body 10. For example, the electronics body section 10 may also include more or fewer components than shown in FIG. 7, or have a different configuration than shown in FIG. 6.

Those skilled in the art will appreciate that all other components are peripheral devices with respect to the processor 102, and the processor 102 is coupled to the peripheral devices through a plurality of peripheral interfaces 124. The peripheral interface 124 may be implemented based on the following criteria: universal Asynchronous Receiver/Transmitter (UART), General Purpose Input/Output (GPIO), Serial Peripheral Interface (SPI), and Inter-Integrated Circuit (I2C), but the present invention is not limited to these standards. In some examples, the peripheral interface 124 may comprise only a bus; in other examples, the peripheral interface 124 may also include other elements, such as one or more controllers, for example, a display controller for interfacing with the display panel 111 or a memory controller for interfacing with a memory. These controllers may also be separate from the peripheral interface 124 and integrated within the processor 102 or a corresponding peripheral.

The memory 104 may be used to store software programs and modules, and the processor 102 executes various functional applications and data processing by executing the software programs and modules stored in the memory 104. The memory 104 may include high speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid state memory. In some examples, the memory 104 may further include memory located remotely from the processor 102, which may be connected to the electronic body portion 10 or the primary display 120 via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The RF module 106 is configured to receive and transmit electromagnetic waves, and achieve interconversion between the electromagnetic waves and electrical signals, so as to communicate with a communication network or other devices. The RF module 106 may include various existing circuit elements for performing these functions, such as an antenna, a radio frequency transceiver, a digital signal processor, an encryption/decryption chip, a Subscriber Identity Module (SIM) card, memory, and so forth. The RF module 106 may communicate with various networks such as the internet, an intranet, a wireless network, or with other devices via a wireless network. The wireless network may comprise a cellular telephone network, a wireless local area network, or a metropolitan area network. The Wireless network may use various Communication standards, protocols, and technologies, including, but not limited to, Global System for Mobile Communication (GSM), Enhanced Mobile Communication (Enhanced Data GSM Environment, EDGE), wideband Code division multiple Access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Wireless Fidelity (WiFi) (e.g., Institute of Electrical and Electronics Engineers (IEEE) standard IEEE 802.10A, IEEE802.11 b, IEEE802.1 g, and/or IEEE802.11 n), Voice over internet protocol (VoIP), world wide mail Access (Microwave for Wireless Communication), Wi-11 Wireless Access (wimax), and any other suitable protocol for instant messaging, and may even include those protocols that have not yet been developed.

The audio circuitry 110, earpiece 101, sound jack 103, microphone 105 collectively provide an audio interface between a user and the electronic body portion 10 or the main display 120. Specifically, the audio circuit 110 receives sound data from the processor 102, converts the sound data into an electrical signal, and transmits the electrical signal to the earpiece 101. The earpiece 101 converts the electrical signal into sound waves that can be heard by the human ear. The audio circuitry 110 also receives electrical signals from the microphone 105, converts the electrical signals to sound data, and transmits the sound data to the processor 102 for further processing. Audio data may be retrieved from the memory 104 or through the RF module 106. In addition, audio data may also be stored in the memory 104 or transmitted through the RF module 106.

The sensor 114 is disposed in the electronic body portion 10 or the main display 120, examples of the sensor 114 include, but are not limited to: light sensors, operational sensors, pressure sensors, gravitational acceleration sensors, and other sensors.

Specifically, the light sensors may include a light sensor 114F, a pressure sensor 114G. Among them, the pressure sensor 114G may detect a pressure generated by pressing on the mobile terminal 100. That is, the pressure sensor 114G detects pressure generated by contact or pressing between the user and the mobile terminal, for example, contact or pressing between the user's ear and the mobile terminal. Accordingly, the pressure sensor 114G may be used to determine whether contact or pressing has occurred between the user and the mobile terminal 100, as well as the magnitude of the pressure.

Referring to fig. 6 again, in the embodiment shown in fig. 6, the light sensor 114F and the pressure sensor 114G are disposed adjacent to the display panel 111. The light sensor 114F may turn off the display output when an object is near the main display 120, for example, when the electronic body portion 10 moves to the ear.

As one of the motion sensors, the gravity acceleration sensor can detect the magnitude of acceleration in various directions (generally three axes), detect the magnitude and direction of gravity when stationary, and can be used for applications (such as horizontal and vertical screen switching, related games, magnetometer attitude calibration), vibration recognition related functions (such as pedometer, tapping) and the like for recognizing the attitude of the mobile terminal 100. In addition, the electronic body 10 may further be configured with other sensors such as a gyroscope, a barometer, a hygrometer and a thermometer, which are not described herein again.

In this embodiment, the input module 118 may include the touch screen 109 disposed on the main display 120, and the touch screen 109 may collect touch operations of the user (for example, operations of the user on or near the touch screen 109 using any suitable object or accessory such as a finger, a stylus, etc.) and drive the corresponding connection device according to a preset program. Optionally, the touch screen 109 may include a touch detection device and a touch controller. The touch detection device detects the touch direction of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch detection device, converts the touch information into touch point coordinates, sends the touch point coordinates to the processor 102, and can receive and execute commands sent by the processor 102. In addition, the touch detection function of the touch screen 109 may be implemented by various types, such as resistive, capacitive, infrared, and surface acoustic wave.

The main display 120 is used to display information input by a user, information provided to the user, and various graphic user interfaces of the electronic body section 10, which may be composed of graphics, text, icons, numbers, video, and any combination thereof, and in one example, the touch screen 109 may be provided on the display panel 111 so as to be integrated with the display panel 111.

The power module 122 is used to provide power supply to the processor 102 and other components. Specifically, the power module 122 may include a power management system, one or more power sources (e.g., batteries or ac power), a charging circuit, a power failure detection circuit, an inverter, a power status indicator light, and any other components associated with the generation, management, and distribution of power within the electronic body portion 10 or the primary display 120.

The mobile terminal 100 further comprises a locator 119, the locator 119 being configured to determine an actual location of the mobile terminal 100. In this embodiment, the locator 119 implements the positioning of the mobile terminal 100 by using a positioning service, which is understood to be a technology or a service for obtaining the position information (e.g., longitude and latitude coordinates) of the mobile terminal 100 by using a specific positioning technology and marking the position of the positioned object on an electronic map.

It should be understood that the mobile terminal 100 described above is not limited to a smartphone terminal, but it should refer to a computer device that can be used in mobility. Specifically, the mobile terminal 100 refers to a mobile computer device equipped with an intelligent operating system, and the mobile terminal 100 includes, but is not limited to, a smart phone, a smart watch, a tablet computer, and the like.

To sum up, according to the data reporting method, the data reporting device, the mobile terminal, and the computer readable medium provided in the embodiments of the present application, information of an application program corresponding to data to be reported is first obtained, a data acquisition component corresponding to the data to be reported is determined according to the information of the application program corresponding to the data to be reported, and then the data to be reported is sent to a server through the data acquisition component. Therefore, different application programs adopt different data acquisition components to acquire data and send the data to the server according to different information, and the flexibility and diversity of data acquisition of the application programs are improved.

In the description herein, reference to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the application. In this specification, the schematic representations of the terms used above are not necessarily intended to refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, various embodiments or examples and features of different embodiments or examples described in this specification can be combined and combined by one skilled in the art without contradiction.

Furthermore, the terms "first", "second" and "first" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one such feature. In the description of the present application, "plurality" means at least two, e.g., two, three, etc., unless specifically limited otherwise.

Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process, and the scope of the preferred embodiments of the present application includes other implementations in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the present application.

The logic and/or steps represented in the flowcharts or otherwise described herein, e.g., an ordered listing of executable instructions that can be considered to implement logical functions, can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. For the purposes of this description, a "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: an electrical connection (mobile terminal) having one or more wires, a portable computer diskette (magnetic device), a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disc read-only memory (CDROM). Additionally, the computer-readable medium could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via for instance optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner if necessary, and then stored in a computer memory.

It should be understood that portions of the present application may be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, the various steps or methods may be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, any one or combination of the following techniques, which are known in the art, may be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application specific integrated circuit having an appropriate combinational logic gate circuit, a Programmable Gate Array (PGA), a Field Programmable Gate Array (FPGA), or the like.

It will be understood by those skilled in the art that all or part of the steps carried by the method for implementing the above embodiments may be implemented by hardware related to instructions of a program, which may be stored in a computer readable storage medium, and when the program is executed, the program includes one or a combination of the steps of the method embodiments. In addition, functional units in the embodiments of the present application may be integrated into one processing module, or each unit may exist alone physically, or two or more units are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. The integrated module, if implemented in the form of a software functional module and sold or used as a stand-alone product, may also be stored in a computer readable storage medium.

The storage medium mentioned above may be a read-only memory, a magnetic or optical disk, etc. Although embodiments of the present application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present application, and that variations, modifications, substitutions and alterations may be made to the above embodiments by those of ordinary skill in the art within the scope of the present application.

Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, and not to limit the same; although the present application has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not necessarily depart from the spirit and scope of the corresponding technical solutions in the embodiments of the present application.

Claims

1. A data reporting method is characterized by comprising the following steps:

acquiring information of an application program corresponding to data to be reported, wherein the information of the application program comprises the type of the application program, and the application program is installed in the mobile terminal;

judging whether the type of the application program belongs to a self-upgrading type, wherein the self-upgrading type of the application program can be upgraded under the condition that an operating system of the mobile terminal is not upgraded, and the non-self-upgrading type of the application program is upgraded along with the upgrading of the operating system;

if so, setting a data acquisition component corresponding to the data to be reported as an SDK component, wherein the SDK component is installed in the application program and is updated along with the update of the application program;

if not, setting the data acquisition component corresponding to the data to be reported as a system acquisition component, updating the system acquisition component according to the update of the operating system, and enabling the system acquisition component to have the authority of acquiring all application programs in the mobile terminal;

and sending the data to be reported to a server according to the data acquisition component.

2. The method of claim 1, wherein sending the data to be reported to a server according to the data collection component comprises:

if the data acquisition component corresponding to the data to be reported is an SDK component, judging whether an application program corresponding to the data to be reported meets a preset reporting condition;

and if so, acquiring the data to be reported through the SDK component, and sending the acquired data to be reported to a server.

3. The method of claim 2, wherein the determining whether the application corresponding to the data to be reported meets a preset reporting condition comprises:

monitoring whether a data reporting request of the application program is received or not;

judging whether the received data reporting request is a data reporting request acquired for the first time after the application program is started;

and if so, judging that the application program meets the preset reporting condition.

4. The method of claim 3, further comprising:

if not, acquiring historical sending time for sending the data to be reported of the application program to the server last time through the SDK component;

acquiring a time interval between the time of the received data reporting request and the historical sending time;

judging whether the time interval is greater than a preset time threshold value or not;

5. The method of claim 2, wherein the determining whether the application corresponding to the data to be reported meets a preset reporting condition comprises:

acquiring the data length of the data to be reported of the application program at the current moment;

judging whether the data length is larger than a preset length or not;

6. The method of claim 1, wherein sending the data to be reported to a server according to the data collection component comprises:

if the data acquisition component corresponding to the data to be reported is a system acquisition component, acquiring all the data to be reported generated by the application program within a preset time interval through the system acquisition component, and sending the acquired data to be reported to a server.

7. A data reporting apparatus, comprising:

the mobile terminal comprises a first acquisition unit, a second acquisition unit and a processing unit, wherein the first acquisition unit is used for acquiring information of an application program corresponding to data to be reported, the information of the application program comprises the type of the application program, and the application program is installed in the mobile terminal;

the second acquisition unit is used for judging whether the type of the application program belongs to a self-upgrading type, wherein the self-upgrading type application program can be upgraded under the condition that an operating system of the mobile terminal is not upgraded, and the non-self-upgrading type application program is upgraded along with the upgrading of the operating system; if so, setting a data acquisition component corresponding to the data to be reported as an SDK component, wherein the SDK component is installed in the application program and is updated along with the update of the application program; if not, setting a data acquisition component corresponding to the data to be reported as a system acquisition component, wherein the system acquisition component is an acquisition tool carried by the operating system and is updated according to the updating of the operating system, and the system acquisition component has the authority of acquiring all application programs in the mobile terminal;

and the sending unit is used for sending the data to be reported to a server according to the data acquisition component.

8. A mobile terminal comprising a memory and a processor, the memory coupled to the processor; the memory stores instructions that, when executed by the processor, cause the processor to perform the method of any of claims 1-6.

9. A computer-readable medium storing program code executable by a processor, the program code causing the processor to perform the method of any one of claims 1-6.