CN117714088B

CN117714088B - Data reporting method and electronic equipment

Info

Publication number: CN117714088B
Application number: CN202310534288.XA
Authority: CN
Inventors: 左小川
Original assignee: Honor Device Co Ltd
Current assignee: Honor Device Co Ltd
Priority date: 2023-05-11
Filing date: 2023-05-11
Publication date: 2024-08-06
Anticipated expiration: 2043-05-11
Also published as: CN117714088A

Abstract

The application provides a data reporting method and electronic equipment, and relates to the technical field of terminals. The application provides a data reporting method, which comprises the following steps: the first server synchronizes a first report request newly added by a second shared database of the second electronic device; the first electronic equipment acquires a first report request from a first server and adds the first report request to a first shared database; acquiring a first service identifier from a first shared database; if the first service identifier is detected to meet the preset condition, determining first reporting data of the first electronic equipment according to the first service identifier; and reporting the first reporting data to the second server. By adopting the method, the accuracy of the data reported by the multiple devices can be improved, and the accuracy of the data positioning fault based on the data reported by the multiple devices in the later period of the Beta server can be improved.

Description

Data reporting method and electronic equipment

Technical Field

The present application relates to the field of terminal technologies, and in particular, to a method for reporting data and an electronic device.

Background

With the continuous development of mobile terminals, each user has a plurality of devices at the same time. Typically multiple devices of the same user are managed by a unified account of the user (e.g., an account of the user logging into the cell phone). When a plurality of devices of a user are in the same short-range wireless communication network, if a certain device (called a master device) under the account reports device data (such as log data) to a server, the master device can inform other devices (called slave devices) in the same network to report the respectively acquired device data to the server through a short-range wireless communication technology so as to enable service personnel or the server to analyze the data, determine a fault reason and timely solve the fault. The near field communication technology includes: wi-Fi (WIRELESS FIDELITY, "wireless fidelity") technology, bluetooth technology, etc.

However, when the short-range wireless communication network fails, it is easy to cause that the slave devices in the same network cannot receive the notification of the reported device data sent by the master device, so that the device data received by the server is inaccurate, and the service personnel cannot accurately analyze the failure of the device. In addition, if a plurality of data under the same account are not in the same short-distance wireless communication network, a plurality of devices under the account cannot report the device data to the server at the same time, so that the device data received by the server is incomplete, and analysis faults of service personnel are affected. For example, when the user a uses a mobile phone in a company, the user's bracelet and tablet are located in the home of the user a, and when the user a's mobile phone reports device data, the user's bracelet and tablet will not report the respective device data because they are in a different network from the mobile phone. It can be seen that how to accurately acquire device data reported by multiple devices is a problem to be solved.

Disclosure of Invention

In order to solve the technical problems, the application provides a data reporting method and electronic equipment, which can improve the accuracy of reporting data by multiple devices.

In a first aspect, the present application provides a method for reporting data, which is applied to a first electronic device, where the first electronic device and a second electronic device are in a ring device environment of a first trust ring corresponding to a first account, and the first electronic device and the second electronic device are both logged in to the first account, where the method includes: receiving a first report request sent by a first server, wherein the first report request comprises a first service identifier, and the first service identifier is used for indicating identification information of data reported by each online device in the same batch in a ring device environment of a first trust ring; the first report request is obtained from the second shared database by the first server after the second electronic device newly adds the first report request in the second shared database; adding a first report request in a first shared database of the first electronic device; acquiring the first service identifier from a first shared database; if the first service identifier is detected to meet the preset condition, determining first reporting data of the first electronic equipment according to the first service identifier; and reporting the first reporting data to the second server.

In this way, the first electronic device and the second electronic device are in the environment of the ring device of the first trust ring corresponding to the first account, and the first electronic device and the second electronic device are both logged in to the first account, i.e. the first electronic device and the second electronic device are online devices in the first trust ring. The second electronic device synchronizes the newly added first service identifier to the first server (such as a server where the glowing account is located) through the second shared database, the first server synchronizes the first service identifier to the first electronic device, and the first electronic device can acquire the first report request through the far-field communication (i.e. the remote communication mode, such as a 4G 5G network) mode by using the distributed synchronization first service identifier, so that the report request generated by the second electronic device can be acquired without the first electronic device and the second electronic device being in the same local area network, thereby increasing the use scene of the multi-device report fault related data. Meanwhile, as the first electronic equipment acquires the first reporting request through the first server, the problem that the first electronic equipment cannot acquire the first reporting request due to the fact that the second electronic equipment adopts the local area network to send the first reporting request fails is avoided, the data (i.e. reporting data) which are reported by the multiple equipment in a sharing way are enriched, the accuracy of the data related to the fault which are reported by the multiple equipment in the sharing way is improved, and the second server is more beneficial to locating faults based on the data related to the fault which are reported by the multiple equipment in the sharing way. In addition, as the first server is the server corresponding to the first account, that is, no additional equipment is needed, and the cost of far-field communication between the first electronic equipment and the second electronic equipment is not increased.

According to a first aspect, if it is detected that the first service identifier meets a preset condition, before determining, according to the first service identifier, first reporting data of the first electronic device, the method further includes: receiving a first report request sent by second electronic equipment through a first network, wherein the first electronic equipment and the second electronic equipment are both in the first network, and the first network is a short-range wireless communication network; and acquiring the first service identifier from the first reporting request. Therefore, the first electronic equipment can also receive the first reporting request sent by the second electronic equipment through the first network at the same time, and the first reporting request can be received through the first network quickly, so that the first electronic equipment can acquire the first reporting request through two different transmission modes, the speed of the first reporting request can be improved when the first network is normal, and the problem that the first reporting request cannot be received by the first electronic equipment can be avoided when the first network fails.

According to a first aspect, after acquiring the first service identity, the method comprises: inquiring whether the first electronic equipment reports the data with the identification information being the first service identification to the second server according to the first service identification; if the fact that the first service identifier meets the preset condition is detected, the first service identifier is determined to meet the preset condition; if the reported first service identifier is detected, determining that the first service identifier does not meet the preset condition. Therefore, the first electronic device can avoid repeatedly reporting the data with the same fault type to the second server, and the second server is reduced to store the data with the same fault type.

According to a first aspect, after reporting the first reporting data to the second server, the method further comprises: and marking the first service identifier to indicate that the first electronic equipment reports the identifier information as the data of the first service identifier. Therefore, the first electronic equipment can instruct the first electronic equipment to report the identification information as the data of the first service identification in a mode of marking the first service identification, and the marking mode is simple.

According to a first aspect, marking a first service identifier to indicate that a first electronic device has reported identification information as data of the first service identifier includes: storing a first service identifier in a first local database of the first electronic device, wherein the first local database is used for recording the identifier information of data reported each time; according to the first service identifier, querying whether the first electronic device has reported the data with the identifier information being the first service identifier to the second server includes: inquiring whether a first service identifier exists in a first local database; if the first service identifier is not queried, determining that the first electronic equipment does not report the identifier information to the second server as the data of the first service identifier; if the first service identifier is queried, determining that the first electronic equipment reports the identifier information to the second server as the data of the first service identifier. In this way, the first electronic device can quickly determine whether the data with the single number being the first service identifier has been reported.

According to a first aspect, determining first reporting data of a first electronic device according to a first service identifier includes: collecting first log information of a first electronic device; and generating first reporting data according to the first log information and the first service identifier, wherein the first service identifier is used as the identification information of the first log information. Therefore, the identification information of the first log information reported by the first electronic equipment is the first service identification, so that the subsequent second server can conveniently acquire data reported by different equipment based on the first service identification.

According to a first aspect, before receiving the first report request sent by the first server, the method further includes: detecting that the first electronic equipment is changed from an offline state to an online state, and updating an online list, wherein the online list is used for storing equipment identifiers of online equipment in a ring equipment environment in a first trust ring; registering a first sense fence of a first shared database; whether a first sensing fence is triggered is detected, the first sensing fence trigger being used to indicate that data stored in a first shared database has changed. Thus, the first electronic device timely updates the online list and subscribes to the first sensing fence so that changes (such as increasing data or decreasing data) of the first shared database can be timely sensed.

According to a first aspect, the method further comprises: if the first electronic equipment is detected to be changed from the online state to the offline state, deleting the equipment identifier of the first electronic equipment from the online list; the first sensing fence is released. In this way, the first electronic device releases the first sensing fence, avoiding unnecessary power consumption.

In a second aspect, the present application provides a method for reporting data, which is applied to a second electronic device, where the second electronic device and at least one first electronic device are in a ring device environment of a first trust ring corresponding to a first account, and the first electronic device and the second electronic device are both logged in to the first account, where the method includes: responding to a reporting operation input by a user, and newly adding a first reporting request in a second shared database of second electronic equipment, wherein the first reporting request comprises a first service identifier, and the first service identifier is used for indicating identification information of data reported by each online equipment in the same batch in a ring equipment environment of a first trust ring; the second electronic device informs the first server to acquire a first report request from the second shared database, and the first server sends the first report request to each online first electronic device in the ring device environment of the first trust ring; the first electronic equipment receives a first report request, adds the first report request in a first shared database and acquires a first service identifier from the first shared database; if the first service identifier is detected to meet the preset condition, the first electronic device determines first reporting data of the first electronic device according to the first service identifier; the first electronic equipment reports first report data to a second server; collecting second log information of second electronic equipment; and generating second reporting data according to the first service identifier and the second log information, and reporting the second reporting data to a second server.

The second aspect corresponds to an implementation of the first aspect. The technical effects corresponding to the implementation manner of the second aspect may be referred to the technical effects corresponding to the implementation manner of the first aspect, which are not described herein.

According to a second aspect, the first electronic device and the second electronic device are both in a first network, the first network being a short-range wireless communication network; the method further comprises the steps of: responding to the reporting operation input by the user, and sending a first reporting request to the first electronic equipment through a first network; the first electronic equipment receives a first reporting request sent by the second electronic equipment, acquires a first service identifier from the first reporting request, and determines first reporting data of the first electronic equipment according to the first service identifier when the first electronic equipment detects that the first service identifier meets a preset condition; the first electronic device reports the first reporting data to the second server. Therefore, the second electronic equipment can also simultaneously send the first reporting request to the first electronic equipment through the first network, and the first electronic equipment can receive the first reporting request through the first network quickly, so that the second electronic equipment can transmit the first reporting request through two different transmission modes, the speed of sending the first reporting request to the first electronic equipment can be improved when the first network is normal, and the problem that the first reporting request cannot be received by the first electronic equipment can be avoided when the first network fails.

According to a second aspect, after reporting the second reporting data to the second server, the method further comprises: and marking the first service identifier to indicate that the second electronic equipment reports the identifier information as the data of the first service identifier. Thus, the second electronic equipment is convenient to inquire whether the identification information is the data of the first service identification or not.

According to a second aspect, marking the first service identifier to indicate that the second electronic device has reported the identifier information as data of the first service identifier includes: and storing the first service identifier in a second local database of the second electronic equipment, wherein the second local database is used for recording the identification information of the data reported by the second electronic equipment each time. Therefore, the identification information of the reported data is marked in a mode of storing the second local database, so that the method is convenient and quick.

According to a second aspect, in response to a reporting operation input by a user, newly adding a first reporting request in a second shared database of a second electronic device, including: responding to the reporting operation input by the user, and determining a first service identifier; inquiring whether a first service identifier exists in the second local database, and if the first service identifier does not exist, generating a first reporting request according to the first service identifier; and newly adding the first reporting request in a second shared database of the second electronic equipment. In this way, the second electronic device may perform the deduplication operation first, so as to avoid repeatedly transmitting the first reporting request to other devices.

According to a second aspect, the method further comprises: if the online equipment in the ring equipment environment in the first trust ring is detected to change, updating an online list stored in the second electronic equipment, wherein the online list is used for storing equipment identifiers of the online equipment in the ring equipment environment in the first trust ring; before sending the first report request to the first electronic device, the method further includes: responding to the reporting operation, and inquiring whether the equipment identifier of the first electronic equipment exists in the online list; and when detecting that the device identifier of the first electronic device exists in the online list, determining to execute the step of sending a first reporting request to the first electronic device. In this way, the second electronic device may avoid sending the first reporting request to the offline device, resulting in unnecessary power consumption.

In a third aspect, the present application provides a method for reporting data, which is applied to a system for reporting data, where the system includes a first electronic device, a second electronic device, a first server and a second server, where the first electronic device and the second electronic device are in a ring device environment of a first trust ring corresponding to a first account; the method comprises the following steps: the second electronic equipment responds to first information input by a user on a first service interface of the second electronic equipment, and the first information is displayed and used for indicating abnormal information of the second electronic equipment; responding to the reporting operation input by the user, the second electronic equipment acquires a first service identifier from the second server, wherein the first service identifier is determined by the second server based on the first information; the second electronic device adds a first report request in a second shared database of the second electronic device, wherein the first report request comprises a first service identifier; the second electronic device informs the first server to acquire a first reporting request from the second shared database; the first server sends a first report request to each online first electronic device in the ring device environment of the first trust ring; the first electronic equipment receives a first report request; the first electronic equipment adds a first report request in a first shared database; the first electronic equipment acquires a first service identifier from a first shared database; if the first electronic equipment detects that the first service identifier meets the preset condition, determining first reporting data of the first electronic equipment according to the first service identifier; the first electronic equipment reports first report data to a second server; the second electronic equipment collects second log information of the second electronic equipment; the second electronic equipment generates second report data according to the first service identifier and the second log information, and reports the second report data to the second server; the second server receives second report data sent by the second electronic equipment and first report data sent by the first electronic equipment.

In a fourth aspect, the present application provides an electronic device, comprising: one or more processors; a memory; and one or more computer programs, wherein the one or more computer programs are stored on the memory, which when executed by the one or more processors, cause the electronic device to perform the first aspect and the method of data reporting corresponding to any implementation of the first aspect.

Any implementation manner of the fourth aspect and any implementation manner of the fourth aspect corresponds to any implementation manner of the first aspect and any implementation manner of the first aspect, or corresponds to any implementation manner of the second aspect and any implementation manner of the second aspect. The technical effects corresponding to any implementation manner of the fourth aspect may be referred to the technical effects corresponding to any implementation manner of the first aspect, or the technical effects corresponding to any implementation manner of the second aspect, or the second aspect are not described herein.

In a fifth aspect, the present application provides a computer readable medium storing a computer program, where the computer program when executed on an electronic device causes the electronic device to perform a method for reporting data corresponding to any implementation manner of the first aspect or the first aspect.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the description of the embodiments of the present application will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

FIG. 1 is a schematic diagram illustrating device information in a trust ring corresponding to a current user account;

FIG. 2 is a schematic diagram of an exemplary illustrated bill of lading page;

FIG. 3 is a schematic diagram illustrating reporting of data by multiple devices in a trust ring;

Fig. 4 is a schematic structural view of an exemplary illustrated electronic device;

FIG. 5 is a software architecture diagram of an exemplary electronic device;

FIG. 6 is a flow chart illustrating a method of data reporting;

FIG. 7 is a flow chart illustrating one method of initiating a bill of lading;

FIG. 8 is a software architecture diagram of an exemplary electronic device;

FIG. 9 is another software architecture diagram of an exemplary electronic device;

FIG. 10 is a schematic diagram of an exemplary illustrated electronic device update online list;

FIG. 11 is a flow chart illustrating deduplication of an electronic device;

Fig. 12 is a scene diagram illustrating an example of device a initiating a data report.

Detailed Description

The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all embodiments of the application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.

The term "and/or" is herein merely an association relationship describing an associated object, meaning that there may be three relationships, e.g., a and/or B, may represent: a exists alone, A and B exist together, and B exists alone.

The terms first and second and the like in the description and in the claims of embodiments of the application, are used for distinguishing between different objects and not necessarily for describing a particular sequential order of objects. For example, the first target object and the second target object, etc., are used to distinguish between different target objects, and are not used to describe a particular order of target objects.

In embodiments of the application, words such as "exemplary" or "such as" are used to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" or "e.g." in an embodiment should not be taken as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete fashion.

In the description of the embodiments of the present application, unless otherwise indicated, the meaning of "a plurality" means two or more. For example, the plurality of processing units refers to two or more processing units; the plurality of systems means two or more systems.

Before the technical scheme of the embodiment of the application is described, an application scene of the embodiment of the application is described first. A user usually owns a plurality of devices, and in order to facilitate the user to manage the data of the plurality of owning devices, the data can be managed through a trust ring corresponding to the user account.

The trust ring corresponding to the user account can be created by a certain device of the user, and a trust ring application is arranged in the electronic device and is used for creating and managing the trust ring for the user account, wherein the management of the trust ring comprises but is not limited to: adding devices to the trust ring, deleting devices from the trust ring, deleting the trust ring, freezing the trust ring, etc. For example, assume that the glowing account number of device a is account number 1, and that device a initiates registration with the trust ring cloud (i.e., server), creating trust ring 1 for account number 1. After trust ring 1 is created by device a, the user may add other devices of the user, such as device B and device C, to trust ring 1 via device a.

Fig. 1 is a schematic diagram illustrating device information of an on-ring device of a trust ring corresponding to a current user account. If the user does not log in the user account, the user account can be logged in first. As shown in fig. 1a, the display interface 101 is a setup page, and the user clicks on the "login glowing account" control in the page 101, and jumps to the login interface 102, as shown in fig. 1 b. The user may enter an account name and password in the login interface 102 to log in to the user account. As shown in fig. 1c, the account interface 103 displays the account number of the glowing account logged in by the user, for example, the account interface display 158 2 xxxxx is the account name of the glowing account number, and the mobile phone jumps to the display interface 104, for example, 1d, in response to the operation that the user clicks the account number. The number of ring devices in the trust ring corresponding to the current user account is displayed in the display interface 104. When the user clicks the control of "my device", the mobile phone jumps to interface 105, which displays detailed device information (such as the model of the device) of the device in the trust ring corresponding to the user account, and as shown in fig. 1e, device a (i.e. glowing V40), device B (i.e. glowing V30) and device C (i.e. tablet in fig. 1 e) are included in the trust ring 1 corresponding to the current user account. The device a, the device B, and the device C are in a ring device environment of the trust ring 1.

There may be interactions between devices that are typically in the same trust ring. For example, the mobile phone can be connected with a sound box, a watch, a bracelet and the like, the intelligent sound box can also be connected with an air conditioner, a television, a desk lamp and the like, and a user can control a plurality of devices through one mobile phone. However, when the mobile phone detects that a task (such as a task that the mobile phone turns on a desk lamp) fails, the user can apply for a bill of lading operation through the mobile phone. The handset may submit data related to the failure to a test (Beta) server and notify other devices on the same trust ring and on the same local area network to initiate a bill of lading operation at the same time. Other devices initiate bill of lading operations including: and responding to a bill of lading request sent by the device A through a short-range wireless communication network (such as a Wi-Fi network), collecting log information of the current device, and reporting the collected log information to a Beta server.

This example, in conjunction with fig. 2 and 3, specifically illustrates the process of device a initiating a near field bill of lading.

The trust ring 1 corresponding to the current user account comprises: device a, device B, and device C. As shown in fig. 3, the devices a, B, and C are in a first network, which may be a local area network, such as a Wi-Fi network. If device a fails, device a may initiate a bill of lading request. As shown in fig. 2, the mobile phone (e.g., the device a in fig. 2) displays a bill of lading interface, and the user may input problem description information in the input box, e.g., if the device a plays a video, a problem of blocking occurs, or if a system application is started, a problem of flashing occurs.

As shown in fig. 2, in response to the user clicking the "bill of lading" control, the device a reports the input problem description information to a test server (such as a Beta server in fig. 3), and the Beta server may allocate identification information, such as single number 1, for the data of the batch of to-be-filed bill of lading according to the problem description information. The device a may collect log information of the device a (denoted as data a), and upload the data a and the element number 1 to the Beta server. Meanwhile, the device a sends a report request to other devices which are in the first network and belong to the same trust ring, wherein the report request may include a single number 1; when device B and device C receive the report request through the first network, log information (respectively noted as data B and data C) may be collected separately. And the device B reports the single number 1 and the data B to the Beta server, and the device C reports the single number 1 and the data C to the Beta server.

The Beta server receives the data A, the data B and the data C, and integrates the data A, the data B and the data C according to the single number 1, so that the reasons of the faults with the single number 1 can be analyzed and positioned through the data A, the data B and the data C later.

As shown in fig. 3, when the first network fails, such as the network is unstable, the device a fails to send the report request to the device B, so that the device B fails to receive the report request, and the device B fails to report the data B (i.e., the data corresponding to the single number 1) to the Beta server, thereby failing to accurately locate the failure by the Beta server.

The embodiment of the application provides a data reporting method, wherein an electronic device can increase a shared database, and a master device (such as a device A in fig. 3) adds a reporting request to the shared database of the master device; the master device notifies an internet of things (Internet of Things, "IoT") server (hereinafter IoT cloud) to obtain a report request from the master device's shared database. The IoT cloud distributes the report request newly added by the master device to the shared database of each slave device (such as device B and device C in fig. 3), so that each slave device can receive the report request newly added by the master device, the problem that the slave device cannot collect log information in time due to the local area network fault where the master device and the slave device are located is avoided, and the accuracy of reporting data of the Beta server by multiple devices is improved. Meanwhile, by adopting the method in the example, the master equipment and the slave equipment do not need to be in the same local area network, the application scene of the data reporting Beta server is increased, and fault data acquired by the Beta server are further enriched. The master device and the slave device in this example are electronic devices, and the type of the master device may be different from the type of the slave device, or may be the same as the type of the slave device, which is not specifically limited in this example.

Fig. 4 is a schematic structural diagram of an electronic device 100 according to an embodiment of the present application. It should be understood that the electronic device 100 shown in fig. 4 is only one example of an electronic device, and that the electronic device 100 may have more or fewer components than shown in the figures, may combine two or more components, or may have different component configurations. The various components shown in fig. 4 may be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and/or application specific integrated circuits.

The electronic device 100 may include: processor 110, external memory interface 120, internal memory 121, universal serial bus (universal serial bus, USB) interface 130, charge management module 140, power management module 141, battery 142, antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, audio module 170, speaker 170A, receiver 170B, microphone 170C, headset interface 170D, sensor module 180, keys 190, motor 191, indicator 192, camera 193, display 194, and subscriber identity module (subscriber identification module, SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor, a gyroscope sensor, a barometric sensor, a magnetic sensor, an acceleration sensor, a distance sensor, a proximity sensor, a fingerprint sensor, a temperature sensor, a touch sensor, an ambient light sensor, a bone conduction sensor, and the like.

Fig. 5 is a software configuration block diagram of the electronic device 100 according to the embodiment of the present application.

The layered architecture of the electronic device 100 divides the software into several layers, each with a distinct role and division of labor. The layers communicate with each other through a software interface. In some embodiments, the Android system is divided into three layers, an application layer, an application framework layer and a kernel layer from top to bottom. It will be appreciated that the layers and components contained in the layers in the software structure of fig. 5 do not constitute a particular limitation of the electronic device 100. In other embodiments of the application, electronic device 100 may include more or fewer layers than shown and may include more or fewer components per layer, as the application is not limited.

As shown in fig. 5, the application layer may include a series of application packages. The application packages may include applications for reporting, PC (Personal Computer, "personal computer") housekeeper, WLAN applications, gallery, short message, talk, navigation, bluetooth, camera, etc. The application framework layer provides an application programming interface (application programming interface, API) and programming framework for the application of the application layer. The application framework layer includes a number of predefined functions.

As shown in FIG. 5, the application framework layer may include a window manager, resource manager, content provider, view system, phone manager, notification manager, and the like.

The window manager is used for managing window programs. The window manager can acquire the size of the display screen, judge whether a status bar exists, lock the screen, intercept the screen and the like.

The resource manager provides various resources for the application program, such as localization strings, icons, pictures, layout files, video files, and the like.

The content provider is used to store and retrieve data and make such data accessible to applications. The data may include video, images, audio, calls made and received, browsing history and bookmarks, phonebooks, etc.

The view system includes visual controls, such as controls to display text, controls to display pictures, and the like. The view system may be used to build applications. The display interface may be composed of one or more views. For example, a display interface including a text message notification icon may include a view displaying text and a view displaying a picture.

The telephony manager is used to provide the communication functions of the electronic device 100. Such as the management of call status (including on, hung-up, etc.).

The notification manager allows the application to display notification information in a status bar, can be used to communicate notification type messages, can automatically disappear after a short dwell, and does not require user interaction. Such as notification manager is used to inform that the download is complete, message alerts, etc. The notification manager may also be a notification in the form of a chart or scroll bar text that appears on the system top status bar, such as a notification of a background running application, or a notification that appears on the screen in the form of a dialog window. For example, a text message is prompted in a status bar, a prompt tone is emitted, the electronic device vibrates, and an indicator light blinks, etc.

Fig. 6 is a flowchart illustrating a method of reporting data, the method of reporting data including the steps of:

step 600: the first electronic device receives a first report request sent by a first server.

In this example, the first electronic device is a slave device, which is a device for receiving a report request in the same trust ring, such as device B in fig. 3. The second electronic device is a master device, which is a device for sending a report request in the same trust ring, such as device a in fig. 3. In different application scenarios, the same electronic device can be used as a master device or a slave device. In this example, the master device and the slave device are both exemplified by a mobile phone.

The first trust ring corresponding to the first account number may include: a master device and a plurality of (e.g., two or more) slave devices. The first account may be an account for logging into the electronic device, such as a glowing account. The primary device has logged into the first account, and the server corresponding to the first account is a first server (e.g., ioT cloud).

And the main equipment responds to the reporting operation input by the user and acquires the problem description information input by the user. The reporting operation may be clicking a preset button (e.g., a "bill of lading" button), double clicking a screen, etc. The problem description information is used for describing abnormal problems of the equipment, such as information of time when the application flash back occurs, application name, version information, operation of a user and the like. After the master device obtains the problem description information, the problem description information may be uploaded to a second server (e.g. Beta server in fig. 3), and the second server determines, according to the problem description information, identification information of data to be reported in the batch.

For example, the user inputs "application flashing back" in the question description box of the device a, and when the user clicks the "bill of lading" button in the bill of lading page, the device a acquires the question description information input by the user and uploads the question description information to the Beta server. The Beta server acquires the problem description information, and allocates a corresponding single number for the problem description information, wherein the single number is used as an index of data to be reported in the batch of the equipment A. Because the reasons for the same faults when the multiple devices are used may be the same, the data to be reported by the master device and the slave device in the batch adopt the same identification information, so that the subsequent Beta server can integrate the data reported by the batch, and the fault reasons can be more accurately positioned.

The master device acquires the identification information (i.e. the first service identification) to be reported in the batch, and can trigger the acquisition device A to acquire log information. Optionally, the master device may trigger to collect log information of the device a when detecting a reporting operation input by the user.

After obtaining the first service identifier, the master device may generate a first report request, where the first report request includes: and a first service identifier. Optionally, the first report request may further include: information of the master device. The master device has a shared database (i.e., a second shared database) disposed therein. Alternatively, the shared database of the master device may be provided in the device attributes of the master device. The device attribute of the master device is an attribute of a trust ring application in the master device. The shared database of the primary device may synchronize stored data with other devices in the trust ring through a first server (e.g., an IoT cloud).

The master device adds a first report request to a shared database of the master device. For example, assuming that the device a is a master device, a new bill of lading list is stored in the shared database of the device a, when the master device generates a first report request, the first report request may be added to the new bill of lading list, that is, a new bill number is added to the new bill of lading list. Optionally, the new bill of lading list may also contain information of the host device.

When the data of the shared database of the master device changes, the first server (such as an IoT cloud) may be notified to synchronize the data of the shared database of the master device, and the first server obtains the first report request from the shared database of the master device. For example, single number No.1 is added to the shared database of the master device, and the first server is notified that the shared database of the master device has newly added information. The first server responds to the received notification, the single number NO.1 is obtained from the shared database of the main device, and the first server sends the single number NO.1 to other online devices in the trust ring, wherein the online devices are devices which have logged in the first account. The single number No.1 is obtained from the shared database of the device.

Step 601: a first report request is added to a first shared database of a first electronic device.

For example, a first report request may be added to the first shared database by the device management service module of the slave device.

Step 602: the first electronic device obtains a first service identifier from a first shared database.

Illustratively, a device management service of the slave device (i.e., the first electronic device) may subscribe to a first sense fence of the first shared database to detect whether the first sense fence triggers to indicate whether data stored in the first shared data changes. When a single number is newly added to a first shared database of the slave device, the first sensing fence is triggered, and a device management service of the slave device transmits the newly added single number to a multi-device management module of a far-field bill of lading module of the slave device. The multi-device management module of the slave device forwards the newly added single number to a following bill of lading module (hereinafter referred to as a fourth following bill of lading module) of the Beta single management module, and the fourth following bill of lading module acquires the newly added single number (i.e. the first service identifier).

Step 603: if the first service identifier is detected to meet the preset condition, determining first reporting data of the first electronic equipment according to the first service identifier.

In some embodiments, when the multi-device management module of the slave device acquires the new added single number, the new added single number is transmitted to a following bill of lading module (hereinafter referred to as a fourth following bill of lading module) of a far-field bill of lading module of the slave device, and the fourth following bill of lading module of the slave device determines whether the first service identifier meets a preset condition. The fourth follow-up bill of lading module of the slave device determines that the first service identifier meets the preset condition, the first service identifier can be transmitted to the follow-up bill of lading module (hereinafter referred to as a third follow-up bill of lading module) of the near-field bill of lading module of the slave device, the third follow-up bill of lading module indicates to collect the log information of the current slave device according to the first service identifier, the newly added single number is used as the single number of the log information, and the log information, the newly added single number and the corresponding relation between the log information and the newly added single number are used as the first report data.

In other embodiments, the multi-device management module of the slave device obtains the new added single number and forwards the new added single number to the fourth following bill of lading module, where the fourth following bill of lading module of the slave device may compare the new added single number with the locally stored single number of the proposed bill, and if the new added single number does not exist in the locally stored single number of the proposed bill, it is determined that the first service identifier meets the preset condition, and step 604 is executed. If the fourth follow-up bill of lading module detects that the newly added bill of lading number exists in the locally stored bill of lading numbers, the fourth follow-up bill of lading module determines that the first service identifier does not meet the preset condition, and the fourth follow-up bill of lading module can discard the first service identifier and does not execute the operation of reporting data, namely does not execute the operation of follow-up bill of lading.

Step 604: and reporting the first reporting data to the second server.

For example, the slave device may detect whether the current slave device is in a Wi-Fi network, and if so, report the first report data to a second server (e.g., a Beta server). And if the slave device detects that the current slave device is not in the Wi-Fi network, caching the first reporting data, and when the slave device detects that the Wi-Fi network is accessed, reporting the first reporting data to the second server.

Optionally, after determining to report the first report data to the second server, if it is detected that the current slave device is not connected to the Wi-Fi network and the user is connected to the mobile communication network (such as a 4G or 5G network), the slave device may display a network authorization prompt message to indicate whether the user is authorized to report the first report data through the current mobile network. And when the slave equipment receives the authorization authority of the user, reporting the first reporting data to the second server through the mobile communication network. And if the slave device does not receive the authorization authority of the user, caching the first reporting data, and reporting the first reporting data to the second server through the Wi-Fi network after the slave device detects that the Wi-Fi network is accessed. Optionally, the slave device may also obtain the authorization information of the user in advance before executing step 601, so as to avoid the problem that the first report data cannot be timely reported to the second server.

In this example, the master device can synchronize the newly added single number to other online devices in the trust ring through the shared database set in the trust ring, instead of sending the newly added single number by using the local area network, so that the problem that the report request sent by the master device cannot reach the slave device when the local area network fails is avoided. Meanwhile, the data is synchronized between the shared database of the trust ring of the master device and the shared database of the slave device through the first server, so that the master device and the slave device do not need to be in the same local area network, the data can be reported, and the use scene of the data reporting is improved.

In some embodiments, in order to increase the speed of obtaining the reporting request by the slave device, the master device may send the reporting request to the online device in the same trust ring through the short-range wireless communication network at the same time when adding the first service identifier to the second shared data, and if the time when the reporting request sent by the master device is received by the slave device is earlier than the time when the reporting request is obtained by the slave device from the first shared database, the slave device performs the data reporting operation based on the reporting request sent by the master device. And if the time when the slave device receives the report request sent by the master device is over the time when the slave device acquires the report request from the first shared database, the slave device performs data report operation based on the report request acquired by the first shared database. In this example, the near-field bill of lading operation and the far-field bill of lading operation are executed simultaneously by the master device, so that the speed of acquiring the bill of lading request by the slave device can be increased, and the problem that the report request cannot reach the slave device in time when the near-field network fails can be avoided. In this example, the near field bill of lading operation performed by the host device includes: the method comprises the steps that a master device responds to reporting operation input by a user, and a first reporting request is sent to an online device of a trust ring corresponding to a first account through a short-range wireless communication network (such as a Wi-Fi network); the master device collects log information of the master device and reports the log information of the master device and the first service identifier to the second server. The far field bill of lading operation performed by the master device includes: the method comprises the steps that a primary device responds to reporting operation input by a user, and a first reporting request is added in a second shared database of the primary device; the first server is informed to acquire a first report request from the second shared database, and the first server synchronously transmits the first report request to the shared database of the online equipment of the trust ring corresponding to the first account; the master device collects log information of the master device and reports the log information of the master device and the first service identifier to the second server.

The process by which the master device performs both near field and far field bill of lading operations is described below with particular reference to the accompanying drawings.

Fig. 7 is a flow chart illustrating one example of data reporting. The master device is exemplified by device a and the slave device is exemplified by device B. The master device and the slave device are in a first network, which may be a local area network, such as a Wi-Fi network, a bluetooth network, or the like. The master device and the slave device are in an on-loop device environment of a trust loop of a first account. The data reporting process comprises the following steps:

step 701: the master device determines to initiate a bill of lading request.

Illustratively, the host device responds to a report operation input by the user, which may be a user clicking a bill of lading button of the display interface, such as the "bill of lading" control in fig. 2. The master device sends the problem description information to the Beta server (i.e. the second server) to obtain the first service identifier, and the process of obtaining the first service identifier may refer to the related description in step 600, which is not described herein.

And the master equipment generates a first report request according to the first service identifier, wherein the first report request comprises the first service identifier. The master device determines that a bill of lading request is initiated and may perform both step 702 and step 703, i.e., both near field bill of lading operation and far field bill of lading operation.

Step 702: the master device performs a near field bill of lading operation.

In one example, the far field bill of lading module of the master device may subscribe to a second awareness fence to detect whether the number of online devices in the trust ring has changed. When the second sense fence is triggered, the far-field bill of lading module of the master device determines that the number of online devices in the trust ring has changed, and the far-field bill of lading module of the master device may obtain an online list from a first server (e.g., ioT cloud) that is used to store device identifications of the online devices in the first trust ring. The online list is transmitted by the far field bill of lading module to the near field bill of lading module of the host device.

The near field bill of lading module of the master device identifies the online device in the first network according to the device identification in the online list, and sends a first report request to the online device in the first network.

Fig. 8 is a schematic diagram of a software architecture of an exemplary electronic device. In this example, the master device may employ a software architecture as shown in fig. 8. The process by which the master device initiates a near field bill of lading operation is described below in connection with fig. 8.

As shown in fig. 8, the test center (i.e., beta Club) of the bill of lading application includes bill of lading pages, which may be in the form shown in fig. 2 or in other patterns, without limitation. When the bill of lading page of the master device detects the report operation input by the user, the report problem description information is reported to the Beta server, and the Beta server returns the first service identification (marked as No. 1) of the data to be reported of the master device in the batch. The IF-1 interface is the interface between BetaClub and the dimension service module. The bill of lading page transmits the first service identification to the dimension measuring service module through the IF-1 interface, the near field bill of lading module obtains the first service identification, and a first report request is generated. The initiating bill of lading module of the near field bill of lading module (hereinafter referred to as the first initiating bill of lading module) sends a first report request to the online device in the trust ring. It can be understood that the first initiation bill module transmits the first reporting request to the near field communication module through the two-end reporting module, and the near field communication module sends the first reporting request to the online device of the first trust ring through the local area network. The double-end reporting module is used for data communication in a service layer. Wherein the near field module is not shown in fig. 8.

Step 703: the master device performs far field bill of lading operations.

Illustratively, with continued reference to FIG. 8, the first originating bill of lading module of the host device transmits the first report request to the multi-device management module of the far-field bill of lading module over the IF-2 interface. The IF-2 interface is an interface provided by a far field bill of lading module. The multi-device management module forwards the first report request to a device management service module through an IF-4 interface, the device management service module adds the first report request to a second shared database of the device management service module, the device management service module senses that the second shared database is changed, and notifies a first server (such as an IoT cloud) to acquire the first report request in the second shared database. The first server (i.e., ioT cloud) obtains a first report request from the second shared data office. The second shared database may communicate with the first server using a D2D (Device-to-Device) communication module.

Similarly, when the master device performs the near-field bill of lading operation and the far-field bill of lading operation simultaneously, the corresponding slave device may perform the bill of lading operation according to the time when the first report request is received. For example, if the time of receiving the report request sent by the master device is earlier than the time of the slave device obtaining the report request from the first shared database, the slave device executes a near-field bill-of-lading operation; and if the slave device receives the report request sent by the master device at a time later than the time when the slave device acquires the report request from the first shared database, the slave device executes far-field bill of lading operation.

In this example, the slave device may also employ a software structure as shown in fig. 8. The process of initiating a near field bill of lading operation and a far field bill of lading operation from a device is described below in connection with fig. 8.

If the slave device receives a first report request sent by the master device through the first network, the slave device reports data in a near-field bill of lading mode.

Specifically, as shown in fig. 8, the slave device receives a first report request sent by the master device through the near field communication module, and the near field communication module transmits the first report request to the near field bill of lading module of the slave device through the two-end report module. A following bill of lading module (hereinafter referred to as a third following bill of lading module) in a near field bill of lading module of the slave device acquires a first service identifier from a first report request, the third following bill of lading module detects whether the first service identifier exists in a first local database of the slave device, if not, the third following module can acquire log information of the slave device and takes the log information and the first service identifier, and a corresponding relation between the first service identifier and the log information as first report data. The third following module reports the data to the Beta server (Beta server is not shown in fig. 8) through the two-end reporting module and the near field communication module.

In one example, the IoT cloud synchronizes the first reporting data to the first shared database of the slave device when synchronizing the first reporting request of the shared database of the master device (i.e., the second shared database). The slave device detects that the data of the first shared database is changed and transmits the data to the far-field bill of lading module through the IF-4 interface. The multi-device management module of the far-field bill of lading module obtains the first report request. And if the slave device receives the report request sent by the master device, the slave device determines to execute far-field bill of lading operation when the slave device acquires the report request from the first shared database.

The multi-device management module forwards the first report request to a follow-up bill of lading module (hereinafter referred to as a fourth follow-up bill of lading module) in the Beta single management module. Detecting whether a first service identifier exists in the first local database by a fourth follow-up bill of lading module, and discarding the first service identifier by the fourth follow-up bill of lading module if the first service identifier exists; IF the first service identifier does not exist, the acquired first service identifier can be transmitted to a third follow-up bill of lading module through an IF-3 interface, and the IF-3 interface is an interface provided by a double-end reporting module and comprises a far-field bill of lading module to initiate or follow the bill of lading. And acquiring log information of the slave equipment by a third follow-up bill of lading module according to the first service identifier, and taking the log information, the first service identifier and the corresponding relation of the log information and the first service identifier as first reporting data. And the third following module reports the data to the Beta server through the double-end reporting module and the near field communication module.

In some embodiments, the electronic device may also employ a software architecture as shown in FIG. 9. The electronic device shown in fig. 9 may be a master device or a slave device.

As shown in fig. 9, the test center (i.e., beta Club) of the bill of lading application includes a bill of lading page. When the bill of lading service of the main equipment detects the reporting operation input by the user, the problem description information is reported to the Beta server, and the Beta server returns a first service identifier (marked as No. 1) of the data to be reported of the main equipment. The IF-1 interface is the interface between BetaClub and the dimension service module. The bill of lading page transmits the first service identification to the dimension measuring service module through the IF-1 interface, and the near field bill of lading module (namely the log acquisition service module) acquires the first service identification to generate a first report request. The first initiation bill module transmits a first reporting request to the double-end reporting module through the IF-5 interface, the double-end reporting module transmits the first reporting request to the near field communication module, and the near field communication module transmits the first reporting request to the online equipment of the first trust ring through the local area network. The IF-5 interface is used for communication between the dimension measurement service module of the service layer and the dimension measurement service module of the local layer.

Meanwhile, the first initiation bill of lading module of the master device transmits the first report request to the multi-device management module of the far-field bill of lading module through the IF-2 interface. The IF-2 interface is an interface provided by a far field bill of lading module. The multi-device management module forwards the first report request to the Beta single management module, an initiation bill of lading module (hereinafter referred to as a second bill of lading module) in the Beta single management module transmits the first report request to the device management service module through the IF-4 interface, and the device management service module adds the first report request to a first shared database of the device management service module and notifies an IoT cloud to synchronize the newly added first report request in the first shared database. Wherein in this example, the IF-4 interface is an interface provided by a device management (DEVICEMANAGER) service module.

Similar to fig. 8, the slave device receives the first report request sent by the master device through the near field communication module, and the near field communication module transmits the first report request to the near field bill of lading module of the slave device through the two-end report module. The following bill of lading module (hereafter called third following bill of lading module) of the near field bill of lading module of the slave device obtains the first business label from the first report request, and detect whether there is the first business label in the first local database of the slave device, if not, the third following module can gather the journal information of the slave device, and regard the journal information and the first business label as the first report data. The third following module reports the data to the Beta server (not shown in fig. 9) through the two-end reporting module and the near field communication module.

In one example, the IoT cloud synchronizes the first reporting data to the first shared database upon obtaining the first reporting request to the shared database of the master device. The device management service of the slave device detects that the data of the first shared database is changed, and transmits the first report request to the far-field bill of lading module through the IF-4 interface. A follow-up bill of lading module (hereinafter referred to as a fourth follow-up bill of lading module) in the Beta bill management module acquires a first service identifier, detects whether the first service identifier exists in a first local database, and discards the first service identifier by the fourth follow-up bill of lading module if the first service identifier exists; IF the first service identifier does not exist, the acquired first service identifier can be transmitted to a third follow-up bill of lading module through the IF-3 interface, the third follow-up bill of lading module collects log information of the slave device according to the first service identifier, and the log information and the first service identifier are used as first reporting data. And the third following module reports the data to the Beta server through the double-end reporting module and the near field communication module. The IF-3 interface is used for initiating a bill of lading, captureRelativeDeviceLog grabbing a log following bill of lading and the like for captureLogWithPara provided by the log acquisition service module.

In this example, if the slave device receives a first report request sent by the master device through the first network and determines that the first service identifier does not exist in the first local database, an operation of a near-field bill of lading is adopted, and if the slave device firstly obtains the first report request from the first shared database and determines that the first service identifier does not exist in the first local database, an operation of a far-field bill of lading is executed.

In some embodiments, the slave device may update the online list in time, and sense changes in the shared database in time, the process of updating the online list is shown in fig. 10.

Step 1000: the slave device judges whether a notification of the change of the first shared database is received, if so, judges whether to execute the operation of following the bill of lading according to the first service identifier. If the received notification indicates that the number of the online devices of the trust ring is changed, the slave device judges whether the devices are online or offline.

For example, a slave device may subscribe to a first sense fence that triggers a change in data in a first shared database and a second sense fence that triggers a change in the number of devices that indicate online devices in a first trust ring. The slave device's multi-device management module receives a notification sent by the first or second sense fence when the first or second sense fence triggers. The multi-device management module detects whether the notification is a notification indicating a change of the first shared database according to the received notification, and if so, performs step 1001. If the slave device detects a notification as a notification indicating a change in the number of devices of the online devices in the first trust ring, then the determination proceeds to step 1004.

Step 1001: the slave device judges whether to execute the operation of following the bill of lading according to the first service identifier. .

For example, the slave device may detect whether the time at which the first report request is acquired from the first shared database is earlier than the time at which the first report request is acquired from the master device. If the slave device detects that the time of acquiring the first report request from the first shared database is later than the time of acquiring the first report request from the master device, step 1002 is executed; if the slave device detects that the time of acquiring the first report request from the first shared database is earlier than the time of acquiring the first report request from the master device, it is determined to execute step 1003.

Step 1002: the slave device performs a near field bill of lading operation.

The description of this step may refer to the description of the slave device performing the near field bill of lading operation in fig. 8, and will not be repeated here.

Step 1003: the slave device performs a far field bill of lading operation.

The related description of this step may refer to the description of the slave device performing the far field bill of lading operation in fig. 8, and will not be described herein.

Step 1004: the slave device determines whether the first trust ring is online or offline by the device.

Illustratively, the slave device obtains, according to the notification, a device identifier of the device in the first trust ring with a changed state, and then performs step 1005. For example, when the device a detects that the device B changes from an upper line state to an offline state, the device a acquires a device identifier of the device B; if the device A detects that the device C is changed from the offline state to the online state, the device A acquires the device identification of the device C.

Step 1005: the slave device updates the node list.

If the device identification of the offline device is obtained from the device, deleting the identification of the offline device from the node list, and releasing the first perception fence. If the equipment identification of the online equipment is obtained from the equipment, adding the equipment identification of the newly added online equipment into the node list, and subscribing the sensing fence of the shared database of the online equipment so as to obtain the data change of the shared database of the newly added online equipment in real time.

In some embodiments, in order to avoid collision of near field bill of lading operations with far field bill of lading operations, deduplication processing may be added. The process of the deduplication process is shown in fig. 11, and includes:

step 1101: the slave device detects whether a new list number exists in the reported problem list, and if so, the flow of the bill of lading of the slave device is ended. If not, step 1102 is performed.

In this example, taking the first report request sent by the master device through the first network as an example, the slave device obtains a new single number (i.e. the first service identifier) from the first report request, obtains a reported problem list from a local database of the slave device, detects whether the reported problem list has the new single number, and if so, indicates that the slave device has reported the same data as the single number, so as to end the bill lifting process of the slave device. If not, step 1102 is performed.

Step 1102: the slave adds the new ticket number to the reported list of problem tickets and performs step 1103.

Step 1103: the slave initiates an operation to follow the bill of lading.

The slave device may collect log information of the slave device, report the new number and the log information as first report data to the Beta server, and upload the Beta server through the first network.

It may be understood that when the slave device determines that a new single number does not exist in the reported problem list, the slave device may also report the first report data first, and then add the new single number to the reported problem list.

Similarly, if the slave device preferentially acquires the first report request from the first shared data, it can detect whether a new single number exists in the reported problem list, if so, the process is ended, if not, the far-field bill lifting operation is executed, that is, the slave device can add the new single number to the reported problem list, and acquire log information of the slave device. The slave device reports the log information and the new single number to the Beta server, and the reported network can be a first network or a mobile network.

As shown in fig. 12, devices a, B, and C are in the ring device environment of the trust ring 1. And device a, device B, and device C are all in a first network, which is a Wi-Fi network. Device a may obtain an online list of current devices from the IoT cloud, including a device identification of device a, a device identification of device B, and a device identification of device C. Device B subscribes to a sense fence of the shared database in device B (denoted as sense fence B), and device C subscribes to a sense fence of the shared database in device B (denoted as sense fence C).

When the user is tested to have a page jam problem in the process of using the device A, the user inputs the problem description on a bill of lading page of the device A, and for example, the problem description can comprise information such as page jam time, application of page jam, operation when page jam occurs and the like. The user inputs the problem description, clicks a bill of lading button, and the device A responds to the bill of lading operation of the user, reports the problem description to the Beta server, and the Beta server assigns a unique trouble ticket number A (marked as No. 1) to the problem description.

The device a executes S10, and collects own log information (noted as log information a) according to No.1, and the device a uses the log information a, no.1 and the correspondence between the log information a and No.1 as report data 1. Device a may send the report data 1 to the Beta server over the Wi-Fi network.

In step S11, no.1 is written into a shared database (denoted as shared data a) of device a, and device a notifies the Iot cloud to acquire No.1 from shared database a of device a.

Meanwhile, the device A acquires a current online device list, and respectively sends the report request to other online devices except the device A in the online list, namely the device A executes S12, the device A sends the report request to the device C through a Wi-Fi network, and executes S13, and the device A sends the report request to the device B through the Wi-Fi network.

The Iot cloud acquires the No.1 in the shared database A, and executes step S14, and the Iot cloud issues the No.1 to the device B. Meanwhile, the Iot cloud executes step S15, and the Iot cloud issues No.1 to the device C.

Because the first network is unstable, the device a fails to send a report request to the device B through the Wi-Fi network. The device B does not receive the report request sent by the device a. The device B receives the report request sent by the IoT cloud and writes the received No.1 into the shared database B. The device B acquires a reported problem list from the local database B when detecting that the new number No.1 is added in the shared database B, inquires whether No.1 exists in the reported problem list, and can acquire log information B of the device B and take the log information B, the No.1 and the corresponding relation between the log information B and the No.1 as reported data 2 of the device B if detecting that the No.1 exists in the reported problem list. The device B may perform step S16 of reporting the reporting data 2 to the Beta server via the first network.

The moment when the device C receives the report request sent by the device A is recorded as T1, the device C receives No.1 issued by the Iot cloud, and the No.1 is written into the shared database C. The moment when the equipment C detects that the new number No.1 is added in the shared database C is marked as T2, because T1 is earlier than T2, the equipment C does not acquire the number No.1 from the shared database C, but acquires the log information C of the equipment C according to the report request sent by the main equipment, and takes the log information C, the number No.1 and the corresponding relation between the log information C and the number No.1 as report data 3 of the equipment C. The device C may perform step S17 to report the report data 2 to the Beta server via the first network.

In this example, when the first network fails, since the device B may obtain the newly added single number from the Iot cloud, it is ensured that the device B will not leak to report the problem of reporting the data 1, so that the information about the page blocking acquired by the Beta server is more abundant, and the accuracy of subsequent fault location is improved.

It will be appreciated that the electronic device, in order to achieve the above-described functions, includes corresponding hardware and/or software modules that perform the respective functions. The present application can be implemented in hardware or a combination of hardware and computer software, in conjunction with the example algorithm steps described in connection with the embodiments disclosed herein. Whether a function is implemented as hardware or computer software driven hardware depends upon the particular application and design constraints imposed on the solution. Those skilled in the art may implement the described functionality using different approaches for each particular application in conjunction with the embodiments, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

The present embodiment also provides a computer storage medium, where computer instructions are stored, and when the computer instructions are executed on an electronic device, the electronic device is caused to execute the related method steps to implement the method for reporting data in the foregoing embodiment. The storage medium includes: a U-disk, a removable hard disk, a Read Only Memory (ROM), a random access memory (random access memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

The present embodiment also provides a computer program product, which when run on a computer, causes the computer to perform the above-mentioned related steps to implement the method for reporting data in the above-mentioned embodiments.

The electronic device, the computer storage medium, the computer program product, or the chip provided in this embodiment are used to execute the corresponding methods provided above, so that the beneficial effects thereof can be referred to the beneficial effects in the corresponding methods provided above, and will not be described herein.

Any of the various embodiments of the application, as well as any of the same embodiments, may be freely combined. Any combination of the above is within the scope of the application.

The embodiments of the present application have been described above with reference to the accompanying drawings, but the present application is not limited to the above-described embodiments, which are merely illustrative and not restrictive, and many forms may be made by those having ordinary skill in the art without departing from the spirit of the present application and the scope of the claims, which are to be protected by the present application.

Claims

1. The method for reporting data is characterized by being applied to a first electronic device, wherein the first electronic device and a second electronic device are in a ring device environment of a first trust ring corresponding to a first account, and the first electronic device and the second electronic device are both logged in to the first account, and the method comprises the following steps:

Receiving a first report request sent by a first server, wherein the first report request comprises a first service identifier, and the first service identifier is used for indicating identification information of data reported by each online device in the same batch in a ring device environment of the first trust ring; the first report request is obtained from a second shared database by the first server after the second electronic device newly adds the first report request in the second shared database;

Adding the first report request in a first shared database of the first electronic equipment;

acquiring the first service identifier from the first shared database;

If the first service identifier is detected to meet a preset condition, determining first reporting data of the first electronic equipment according to the first service identifier;

And reporting the first reporting data to a second server.

2. The method of claim 1, wherein if the first service identifier is detected to satisfy a preset condition, before determining the first reporting data of the first electronic device according to the first service identifier, the method further comprises:

Receiving a first report request sent by the second electronic equipment through a first network, wherein the first electronic equipment and the second electronic equipment are both positioned in the first network, and the first network is a close range wireless communication network;

and acquiring the first service identifier from the first reporting request.

3. A method according to claim 1 or 2, characterized in that after the first service identity is acquired, the method comprises:

Inquiring whether the first electronic equipment reports the data with the identification information being the first service identification to the second server according to the first service identification;

if the fact that the first service identifier meets the preset condition is detected, the first service identifier is determined to meet the preset condition;

If the reported first service identifier is detected, determining that the first service identifier does not meet a preset condition.

4. A method according to claim 3, wherein after reporting the first reporting data to a second server, the method further comprises:

And marking the first service identifier to indicate that the first electronic equipment reports the identifier information as the data of the first service identifier.

5. The method of claim 4, wherein marking the first service identifier to indicate that the first electronic device has reported data for the first service identifier as identifying information, comprises:

Storing the first service identifier in a first local database of the first electronic device, wherein the first local database is used for recording the identifier information of the data reported each time;

according to the first service identifier, inquiring whether the first electronic device has reported the data with the identifier information being the first service identifier to the second server includes:

Inquiring whether the first service identifier exists in the first local database;

If the first service identifier is not queried, determining that the first electronic equipment does not report the identifier information to the second server as the data of the first service identifier;

If the first service identifier is queried, determining that the first electronic equipment reports the identifier information to the second server as the data of the first service identifier.

6. The method of claim 1, wherein determining the first reporting data of the first electronic device based on the first service identification comprises:

Collecting first log information of the first electronic equipment;

And generating the first reporting data according to the first log information and the first service identifier, wherein the first service identifier is used as the identification information of the first log information.

7. The method according to claim 1 or 2, wherein prior to said receiving the first report request sent by the first server, the method further comprises:

Detecting that the first electronic equipment is changed from an offline state to an online state, and updating an online list, wherein the online list is used for storing equipment identifiers of online equipment in a ring equipment environment in the first trust ring;

registering a first sense fence of the first shared database;

detecting whether the first sensing fence is triggered, wherein the first sensing fence trigger is used for indicating that data stored in the first shared database changes.

8. The method of claim 7, wherein the method further comprises:

If the first electronic equipment is detected to be changed from an online state to an offline state, deleting the equipment identifier of the first electronic equipment from the online list;

and releasing the first sensing fence.

9. The method for reporting data is characterized by being applied to a second electronic device, wherein the second electronic device and at least one first electronic device are in a ring device environment of a first trust ring corresponding to a first account, and the first electronic device and the second electronic device are both logged in to the first account, and the method comprises the following steps:

Responding to a reporting operation input by a user, and newly adding a first reporting request in a second shared database of the second electronic equipment, wherein the first reporting request comprises a first service identifier, and the first service identifier is used for indicating the identification information of data reported by each online equipment in the same batch in a ring equipment environment of the first trust ring;

The second electronic device informs a first server to acquire the first report request from the second shared database, and the first server sends the first report request to each online first electronic device in a ring device environment of the first trust ring; the first electronic equipment receives the first report request, adds the first report request in a first shared database and acquires the first service identifier from the first shared database; if the first service identifier is detected to meet a preset condition, the first electronic device determines first reporting data of the first electronic device according to the first service identifier; the first electronic equipment reports the first reporting data to a second server;

collecting second log information of the second electronic equipment;

And generating second reporting data according to the first service identifier and the second log information, and reporting the second reporting data to the second server.

10. The method of claim 9, wherein the first electronic device and the second electronic device are both in a first network, the first network being a short-range wireless communication network;

The method further comprises the steps of:

Responding to a reporting operation input by a user, and sending the first reporting request to the first electronic equipment through the first network; the first electronic equipment receives the first reporting request sent by the second electronic equipment, acquires the first service identifier from the first reporting request, and determines first reporting data of the first electronic equipment according to the first service identifier when the first electronic equipment detects that the first service identifier meets a preset condition; and the first electronic equipment reports the first reporting data to the second server.

11. The method according to claim 9 or 10, wherein after reporting the second reporting data to the second server, the method further comprises:

And marking the first service identifier to indicate that the second electronic equipment reports the identifier information as the data of the first service identifier.

12. The method of claim 11, wherein marking the first service identifier to indicate that the second electronic device has reported data for the first service identifier as identification information, comprises:

and storing the first service identifier in a second local database of the second electronic equipment, wherein the second local database is used for recording the identification information of the data reported by the second electronic equipment each time.

13. The method of claim 12, wherein in response to a reporting operation entered by a user, newly adding a first reporting request in a second shared database of the second electronic device, comprises:

responding to the reporting operation input by the user, and determining the first service identifier;

querying whether the first service identifier exists in the second local database,

If the first service identifier does not exist, generating the first reporting request according to the first service identifier;

And newly adding a first reporting request in a second shared database of the second electronic equipment.

14. The method according to claim 10, wherein the method further comprises:

If the online equipment in the ring equipment environment in the first trust ring is detected to change, updating an online list stored in the second electronic equipment, wherein the online list is used for storing equipment identifiers of the online equipment in the ring equipment environment in the first trust ring;

before sending the first report request to the first electronic device, the method further includes:

responding to the reporting operation, and inquiring whether the equipment identifier of the first electronic equipment exists in the online list;

And when detecting that the equipment identifier of the first electronic equipment exists in the online list, determining to execute the step of sending the first reporting request to the first electronic equipment.

15. The data reporting method is characterized by being applied to a data reporting system, wherein the system comprises a first electronic device, a second electronic device, a first server and a second server, and the first electronic device and the second electronic device are in a ring device environment of a first trust ring corresponding to a first account; the method comprises the following steps:

The second electronic equipment responds to first information input by a user on a first service interface of the second electronic equipment, and the first information is displayed and used for indicating abnormal information of the second electronic equipment;

Responding to the reporting operation input by the user, the second electronic equipment acquires a first service identifier from the second server, wherein the first service identifier is determined by the second server based on the first information;

The second electronic equipment adds a first reporting request in a second shared database of the second electronic equipment, wherein the first reporting request comprises a first service identifier;

The second electronic device informs a first server to acquire the first report request from the second shared database;

The first server sends the first report request to each online first electronic device in a ring device environment of the first trust ring;

the first electronic device receives the first report request;

the first electronic device adds the first report request in a first shared database;

The first electronic equipment acquires the first service identifier from the first shared database;

If the first electronic equipment detects that the first service identifier meets a preset condition, determining first reporting data of the first electronic equipment according to the first service identifier;

the first electronic equipment reports the first reporting data to a second server;

The second electronic equipment collects second log information of the second electronic equipment;

The second electronic equipment generates second report data according to the first service identifier and the second log information, and reports the second report data to the second server;

and the second server receives second reporting data sent by the second electronic equipment and first reporting data sent by the first electronic equipment.

16. An electronic device, comprising:

A memory and a processor, the memory coupled with the processor;

The memory stores program instructions that, when executed by the processor, cause the electronic device to perform the method of data reporting of any one of claims 1 to 14.

17. A computer readable storage medium comprising a computer program, characterized in that the computer program, when run on an electronic device, causes the electronic device to perform the method of data reporting according to any one of claims 1 to 14.