Abnormal positioning method and device for shared data, electronic equipment and storage medium
By obtaining and judging the abnormality of shared data and determining the responsible equipment based on the abnormal attribution method, the problem of location problems and responsibility attributes when shared data is abnormal is solved, and the positioning efficiency and data transmission security of abnormal responsible equipment are improved.
Patent Information
- Application Number
- CN202411988700.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-12-31
- Publication Date
- 2025-05-30
AI Technical Summary
In the case of many interconnected devices, when there are abnormalities in shared data, it is difficult to quickly locate the source of problems and the responsibility, which affects the normal operation of the entire Internet.
By obtaining the target shared data, determine whether it is abnormal data, and determine the abnormal responsibility device based on the abnormal attribution method. Specific steps include obtaining target data, judging its abnormality, determining the method of attributing exceptions and responsible equipment.
It effectively improves the positioning efficiency of the device responsible for shared data abnormalities, and ensures the security of data transmission on the Internet and the accuracy of responsibility attribution.
Smart Images
Figure CN120066829A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of computer technology, and in particular, to a method, apparatus, electronic device, and storage medium for locating anomalies in shared data. Background Art
[0002] Currently, shared data can be obtained through interconnected devices or through a server. When there are many interconnected devices, the shared data is transmitted between the interconnected devices and the server. Once an anomaly occurs in the shared data, it is usually not possible to quickly locate the source of the problem and confirm the liability attribution. If the anomalous device responsible for the anomalous data cannot be effectively located, it will affect all devices on the interconnected network.
[0003] It can be seen that how to improve the effectiveness of locating the anomalous device responsible for shared data is a technical problem worthy of attention. Summary of the Invention
[0004] In view of this, to solve the above-mentioned part or all of the technical problems, embodiments of this application provide a method, apparatus, electronic device, and storage medium for locating anomalies in shared data.
[0005] In a first aspect, embodiments of this application provide a method for locating anomalies in shared data, the method comprising:
[0006] Obtain target shared data;
[0007] Determine whether the target shared data is anomalous shared data;
[0008] In the case where the target shared data is the anomalous shared data, based on the target shared data, determine the anomalous attribution method for the target shared data;
[0009] Based on the anomalous attribution method, determine the anomalous device responsible for the target shared data.
[0010] In a possible implementation, the determining, based on the anomalous attribution method, the anomalous device responsible for the target shared data includes:
[0011] In the case where the anomalous attribution method is the target attribution method, determine the anomalous path record of the target shared data, where the target attribution method indicates that the target shared data is anomalously attributed through the anomalous path record, and the anomalous path record indicates the transmission path when the target shared data is anomalous;
[0012] Based on the anomalous path record, determine the anomalous device responsible for the target shared data.
[0013] In a possible implementation, after determining the abnormal attribution method of the target shared data based on the target shared data, before determining the abnormal path record of the target shared data when the abnormal attribution method is the target attribution method, the method further includes:
[0014] Determine the device that produces the target shared data to obtain the production device of the target shared data;
[0015] Determine whether the production device is the abnormal responsible device for the target shared data.
[0016] In a possible implementation, when the abnormal attribution method is the target attribution method, determining the abnormal path record of the target shared data includes:
[0017] When the determination result indicates that the production device is not the abnormal responsible device for the target shared data and the abnormal attribution method is the target attribution method, determine the abnormal path record of the target shared data.
[0018] In a possible implementation, the starting node of the transmission path represents the device that determines that the target shared data is abnormal; and
[0019] Based on the abnormal path record, determining the abnormal responsible device for the target shared data includes:
[0020] Determine the starting node of the transmission path represented by the abnormal path record;
[0021] Determine the device represented by the starting node as the abnormal responsible device for the target shared data.
[0022] In a possible implementation, the target shared data and the abnormal path record are transmitted independently.
[0023] In a possible implementation, when the target shared data is the abnormal shared data, the method further includes:
[0024] Determine whether a data request for the target shared data is received;
[0025] When the data request is received, reject providing the target shared data.
[0026] In a second aspect, an embodiment of the present application provides an abnormal positioning device for shared data, and the device includes:
[0027] An acquisition unit, configured to acquire target shared data;
[0028] The first determination unit is configured to determine whether the target shared data is abnormal shared data;
[0029] The second determination unit is configured to, when the target shared data is the abnormal shared data, determine an abnormal attribution method of the target shared data based on the target shared data;
[0030] The third determination unit is configured to determine an abnormal responsible device of the target shared data based on the abnormal attribution method.
[0031] In a possible implementation manner, the determining the abnormal responsible device of the target shared data based on the abnormal attribution method includes:
[0032] When the abnormal attribution method is a target attribution method, determining an abnormal path record of the target shared data, where the target attribution method indicates that the target shared data is abnormally attributed through the abnormal path record, and the abnormal path record indicates a transmission path when the target shared data appears abnormally;
[0033] Determining the abnormal responsible device of the target shared data based on the abnormal path record.
[0034] In a possible implementation manner, after determining the abnormal attribution method of the target shared data based on the target shared data and before determining the abnormal path record of the target shared data when the abnormal attribution method is the target attribution method, the apparatus further includes:
[0035] The fourth determination unit is configured to determine a device that produces the target shared data to obtain a production device of the target shared data;
[0036] The fifth determination unit is configured to determine whether the production device is the abnormal responsible device of the target shared data.
[0037] In a possible implementation manner, the determining the abnormal path record of the target shared data when the abnormal attribution method is the target attribution method includes:
[0038] When the determination result indicates that the production device is not the abnormal responsible device of the target shared data and the abnormal attribution method is the target attribution method, determining the abnormal path record of the target shared data.
[0039] In a possible implementation manner, a start node of the transmission path represents a device that determines that the target shared data is abnormal; and
[0040] Determining the abnormal responsible device of the target shared data based on the abnormal path record includes:
[0041] Determining the starting node of the transmission path represented by the abnormal path record;
[0042] Determining the device represented by the starting node as the abnormal responsible device of the target shared data.
[0043] In a possible implementation manner, the target shared data and the abnormal path record are transmitted independently.
[0044] In a possible implementation manner, when the target shared data is the abnormal shared data, the device further includes:
[0045] A sixth determination unit, configured to determine whether a data request for the target shared data is received;
[0046] A rejection unit, configured to reject providing the target shared data when the data request is received.
[0047] In a third aspect, an embodiment of the present application provides an electronic device, including:
[0048] A memory, configured to store a computer program;
[0049] A processor, configured to execute the computer program stored in the memory, and when the computer program is executed, implement the method of any one of the embodiments of the abnormal location method of shared data in the first aspect of the present application.
[0050] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, implement the method of any one of the embodiments of the abnormal location method of shared data in the first aspect as described above.
[0051] In a fifth aspect, an embodiment of the present application provides a computer program product, the computer program product includes computer-readable code, and when the computer-readable code runs on a device, enables the processor in the device to implement the method of any one of the embodiments of the abnormal location method of shared data in the first aspect as described above.
[0052] The method for abnormal location of shared data provided by the embodiment of the present application can obtain target shared data. Then, it determines whether the target shared data is abnormal shared data. Next, when the target shared data is the abnormal shared data, based on the target shared data, it determines the abnormal attribution method of the target shared data. Subsequently, based on the abnormal attribution method, it determines the abnormal responsible device of the target shared data. Thus, the abnormal responsible device of the target shared data can be determined by adopting the abnormal attribution method corresponding to the target shared data. In this way, the effectiveness of locating the abnormal responsible device of shared data can be improved. BRIEF DESCRIPTION OF THE DRAWINGS
[0053] The accompanying drawings herein are incorporated into the specification and constitute a part of this specification, showing embodiments consistent with the present application, and are used together with the specification to explain the principles of the present application.
[0054] In order to more clearly illustrate the technical solutions in the embodiments of the present application or in the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, for those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.
[0055] One or more embodiments are illustrated by way of example in the pictures in the corresponding accompanying drawings. These exemplary illustrations do not constitute limitations on the embodiments. Elements with the same reference numerals in the drawings are represented as similar elements, unless otherwise stated, and the drawings in the figures do not constitute a proportional limitation.
[0056] Figure 1 Schematic flowchart of a method for abnormal location of shared data provided by an embodiment of the present application;
[0057] Figure 2 Schematic flowchart of another method for abnormal location of shared data provided by an embodiment of the present application;
[0058] Figure 3A Schematic diagram of an application scenario of a method for abnormal location of shared data provided by an embodiment of the present application;
[0059] Figure 3B Schematic flowchart of yet another method for abnormal location of shared data provided by an embodiment of the present application;
[0060] Figure 4 Schematic diagram of the structure of an abnormal location device for shared data provided by an embodiment of the present application;
[0061] Figure 5 Schematic diagram of the structure of an electronic device provided by an embodiment of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS
[0062] Various exemplary embodiments of the present application will now be described in detail with reference to the accompanying drawings. Obviously, the described embodiments are part of the embodiments of the present application, rather than all of the embodiments. It should be noted that: unless otherwise specifically stated, the relative arrangements of components and steps, numerical expressions and numerical values set forth in these embodiments do not limit the scope of the present application.
[0063] Those skilled in the art can understand that terms such as "first", "second", etc. in the embodiments of the present application are only used to distinguish different steps, devices or modules, etc., and do not represent any specific technical meaning, nor do they represent the logical order between them.
[0064] It should also be understood that in this embodiment, "a plurality of" may refer to two or more, and "at least one" may refer to one, two or more.
[0065] It should also be understood that for any component, data or structure mentioned in the embodiments of the present application, without clear definition or contrary indication in the context, it can generally be understood as one or more.
[0066] In addition, the term "and / or" in the present application is merely a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character " / " in the present application generally represents an "or" relationship between the associated objects before and after.
[0067] It should also be understood that the description of each embodiment of the present application emphasizes the differences between the embodiments, and the same or similar parts can be referred to each other. For the sake of brevity, they will not be elaborated one by one.
[0068] The following description of at least one exemplary embodiment is actually only illustrative and does not impose any limitation on the present application and its application or use.
[0069] Techniques, methods and devices known to those of ordinary skill in the relevant art may not be discussed in detail, but where appropriate, the above techniques, methods and devices should be regarded as part of the specification.
[0070] It should be noted that: like reference numerals and letters denote like items in the following drawings, and thus, once an item is defined in one drawing, it does not need to be further discussed in subsequent drawings.
[0071] It should be noted that, without conflict, the embodiments in the present application and the features in the embodiments may be combined with each other. For the convenience of understanding the embodiments of the present application, the following will refer to the accompanying drawings and describe the present application in detail in conjunction with the embodiments. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments in the present application without creative efforts belong to the scope of protection of the present application.
[0072] To solve the technical problem of how to improve the effectiveness of abnormal responsible device positioning for shared data in the prior art, the present application provides an abnormal positioning method, device, electronic device and storage medium for shared data, which can improve the effectiveness of abnormal responsible device positioning for shared data.
[0073] Figure 1 It is a schematic flowchart of an abnormal positioning method for shared data provided by an embodiment of the present application. This method can be applied to one or more electronic devices such as smart phones, laptops, desktop computers, portable computers, servers, etc. In addition, the execution subject of this method can be hardware or software. When the above execution subject is hardware, the execution subject can be one or more of the above electronic devices. For example, a single electronic device can execute this method, or multiple electronic devices can cooperate with each other to execute this method. When the above execution subject is software, this method can be implemented as multiple software or software modules, or can be implemented as a single software or software module. No specific limitation is made here.
[0074] As Figure 1 shown, the method specifically includes:
[0075] Step 101, obtain target shared data.
[0076] In this embodiment, the target shared data can be any shared data. The target shared data can be data accessed and used by multiple users, systems, application programs or devices. In addition, the target shared data can be data that can be transmitted to any other device, not restricted by device permissions, not restricted by privacy and security issues, has no features and does not belong to the data unique to a single device. As an example, the target shared data may include, but is not limited to: user's personal profile, documents jointly edited by multiple people, etc.
[0077] Step 102, determine whether the target shared data is abnormal shared data.
[0078] In this embodiment, the abnormal shared data may be the shared data with anomalies. Generally, during the process of transmitting the target shared data from one device to another, or during the production process of the target shared data, anomalies may occur to the target shared data. For example, the device that produces the target shared data itself may cause anomalies in the target shared data. For another example, the transmission between devices may result in inconsistent shared data before and after transmission, thus causing anomalies in the target shared data.
[0079] Here, multiple methods can be adopted to determine whether the target shared data is abnormal shared data.
[0080] As an example, it is possible to determine whether the target shared data is abnormal shared data by performing a data integrity check on the target shared data. Among them, a data integrity check can be performed on the target shared data through data verification (such as a hash algorithm).
[0081] Step 103, in the case where the target shared data is the abnormal shared data, based on the target shared data, determine the abnormal attribution method of the target shared data.
[0082] In this embodiment, the abnormal attribution method may represent a method for determining the abnormal responsible device of the target shared data.
[0083] The abnormal responsible device may represent the device determined to cause anomalies in the target shared data.
[0084] Here, multiple methods can be adopted to determine the abnormal attribution method of the target shared data based on the target shared data.
[0085] As an example, it is possible to determine the abnormal attribution method of the target shared data based on at least one of the data volume and data anomaly frequency of the target shared data.
[0086] In addition, other methods can also be adopted to determine the abnormal attribution method of the target shared data based on the target shared data.
[0087] For details, please refer to the following description and will not be elaborated here.
[0088] Step 104, based on the abnormal attribution method, determine the abnormal responsible device of the target shared data.
[0089] In this embodiment, after determining the abnormal attribution method of the target shared data, the abnormal responsible device of the target shared data can be further determined based on the abnormal attribution method.
[0090] As an example, the determined abnormal attribution method can be adopted to determine the abnormal responsible device of the target shared data.
[0091] In addition, other methods can be adopted to determine the abnormal responsible device of the target shared data based on the above abnormal attribution method. For specific details, please refer to the following description and will not be elaborated here.
[0092] In some optional implementation manners of this embodiment, when the target shared data is the abnormal shared data, the following steps may further be executed:
[0093] The first step is to determine whether a data request for the target shared data is received.
[0094] Among them, the above data request can be used to request to perform an operation on the target shared data. For example, the above data request can be used to request operations such as downloading and transmitting the target shared data.
[0095] The second step is to refuse to provide the target shared data when the data request is received.
[0096] It can be understood that in the above optional implementation manner, when a data request for the abnormal shared data is received, the target shared data can be refused to be provided. Thereby, the security of data transmission in the interconnected network can be guaranteed.
[0097] It should be noted that, without conflict, the technical features recorded in different optional implementation manners can be included in the same embodiment. For the sake of concise description, it will not be elaborated here.
[0098] The abnormal location method of the shared data provided by the embodiment of the present application can obtain the target shared data, and then determine whether the target shared data is the abnormal shared data. Then, when the target shared data is the abnormal shared data, based on the target shared data, determine the abnormal attribution method of the target shared data. Subsequently, based on the abnormal attribution method, determine the abnormal responsible device of the target shared data. Thus, the abnormal responsible device corresponding to the target shared data can be used to determine the abnormal responsible device of the target shared data. In this way, the effectiveness of locating the abnormal responsible device of the shared data can be improved.
[0099] Figure 2 It is a schematic flowchart of another abnormal location method of the shared data provided by the embodiment of the present application. As Figure 2 shown, this method specifically includes:
[0100] Step 201: Obtain the target shared data.
[0101] In this embodiment, step 201 is basically the same as Figure 1 step 101 in the corresponding embodiment and will not be elaborated here.
[0102] Step 202: Determine whether the target shared data is abnormal shared data.
[0103] In this embodiment, step 202 is basically the same as Figure 1 step 102 in the corresponding embodiment, and will not be elaborated here.
[0104] Step 203: When the target shared data is the abnormal shared data, based on the target shared data, determine the abnormal attribution method of the target shared data.
[0105] In this embodiment, step 203 is basically the same as Figure 1 step 103 in the corresponding embodiment, and will not be elaborated here.
[0106] Step 204: When the abnormal attribution method is the target attribution method, determine the abnormal path record of the target shared data, where the target attribution method indicates that the abnormal attribution of the target shared data is performed through the abnormal path record, and the abnormal path record indicates the transmission path when the target shared data appears abnormal.
[0107] In this embodiment, the abnormal path record may include multiple nodes. At least some of the nodes may represent the transmission devices of the target shared data that appears abnormal.
[0108] As a first example, when the abnormal path record represents the entire transmission path of the target shared data, the starting node of the transmission path represented by the abnormal path record may be the device that generates the target shared data (hereinafter referred to as the generating device), and the next node of each node (including the starting node) may represent the device to which the device represented by this node directly conveys (that is, without being transmitted by other devices) the target shared data. In this case, the devices represented by each node in the transmission path may judge whether the target shared data produced or received by it is abnormal shared data according to a preset policy. Once the device represented by a certain node judges that the target shared data produced or received by it is abnormal shared data, the device may be marked on the transmission path.
[0109] As a second example, the starting node of the transmission path represented by the abnormal path record may also be: among the nodes included in the entire path of transmitting the target shared data, the node corresponding to the device that first determines that the target shared data is abnormal shared data. The next node of each node (including the starting node) may represent the device to which the device represented by this node directly conveys (also without being transmitted by other devices) the target shared data.
[0110] Here, the devices represented by each node can perform the following two operations in parallel or serially: transmitting the target shared data and determining whether the target shared data produced or received by it is abnormal shared data.
[0111] Step 205: Based on the abnormal path record, determine the abnormal responsible device for the target shared data.
[0112] In this embodiment, after determining the abnormal path record, various methods can be used to determine the abnormal responsible device for the target shared data based on the abnormal path record.
[0113] As an example, in the case where the above abnormal path record represents the entire transmission path of the target shared data, the abnormal responsible device for the target shared data can be determined through the nodes marked on the transmission path represented by the abnormal path record.
[0114] In some alternative implementation manners of this embodiment, the starting node of the transmission path represents the device that determines that the target shared data is abnormal. That is, corresponding to the second example above.
[0115] In this case, the following method can be used to determine the abnormal responsible device for the target shared data based on the abnormal path record:
[0116] The first step: Determine the starting node of the transmission path represented by the abnormal path record.
[0117] The second step: Determine the device represented by the starting node as the abnormal responsible device for the target shared data.
[0118] It can be understood that in the above alternative implementation manner, in the case where the starting node of the transmission path represents the device that determines that the target shared data is abnormal, the device represented by the starting node of the transmission path can be directly determined as the abnormal responsible device for the target shared data. Thus, the determination efficiency of the abnormal responsible device for the target shared data can be improved.
[0119] In some alternative implementation manners of this embodiment, after determining the abnormal attribution method for the target shared data based on the target shared data, before determining the abnormal path record of the target shared data in the case where the abnormal attribution method is the target attribution method, the following steps can also be performed:
[0120] The first step: Determine the device that produces the target shared data to obtain the production device of the target shared data.
[0121] Among them, the production device can be the device that produces the target shared data.
[0122] In the second step, determine whether the production device is the abnormal responsible device for the target shared data.
[0123] It can be understood that if the production device is the abnormal responsible device for the target shared data, then the abnormal path record of the target shared data can be directly determined without using other methods to judge the abnormal responsible device of the target shared data. Thus, the determination efficiency of the abnormal responsible device for the target shared data can be improved when the production device is the abnormal responsible device for the target shared data.
[0124] In some application scenarios of the above optional implementation manners, when the determination result indicates that the production device is not the abnormal responsible device for the target shared data and the abnormal attribution method is the target attribution method, the abnormal path record of the target shared data can be determined.
[0125] It can be understood that in the above application scenarios, when the determination result indicates that the production device is not the abnormal responsible device for the target shared data and the abnormal attribution method is the target attribution method, the abnormal responsible device of the target shared data can be determined through the abnormal path record. Thus, the determination duration of the abnormal responsible device can be reduced when the production device is the abnormal responsible device for the target shared data, and the determination efficiency of the abnormal responsible device for the target shared data can be improved when the production device is the abnormal responsible device for the target shared data.
[0126] In some optional implementation manners of this embodiment, the target shared data and the abnormal path record are transmitted independently.
[0127] It can be understood that in the above optional implementation manners, the target shared data and the abnormal path record can be transmitted independently. Compared with the scheme of transmitting the target shared data and the abnormal path record simultaneously, the influence of the generation and transmission of the abnormal path record on the transmission efficiency of the target shared data can be reduced, and thus the transmission efficiency of the target shared data can be improved.
[0128] It should be noted that in addition to the above-mentioned content, this embodiment may also include Figure 1 the corresponding technical features described in the corresponding embodiments, so as to achieve Figure 1 the technical effects of the abnormal location method of the shared data shown, for details, please refer to Figure 1 the relevant descriptions. For the sake of concise description, it will not be elaborated here.
[0129] The abnormal location method of the shared data provided by the embodiment of the present application determines the abnormal responsible device of the target shared data through the abnormal path record of the target shared data, so that the abnormal responsible device of the target shared data can be determined more accurately and efficiently.
[0130] The embodiments of the present application will be described exemplarily below. However, it should be noted that the following content is only used to understand the technical solutions of the embodiments of the present application and does not constitute a limitation on the protection scope of the embodiments of the present application.
[0131] Currently, shared data can be obtained through interconnected devices or through a server. When there are many interconnected devices, the shared data is transmitted between the interconnected devices and the server. Once abnormal data appears, it is impossible to quickly locate the source of the problem and confirm the responsibility attribution. If the abnormal data cannot be quickly locked and resolved, it will affect all devices on the interconnected network.
[0132] In view of this, this solution monitors abnormal shared data by tracking the paths of shared data among different devices, so as to achieve the purpose of quickly querying the data source and determining the responsibility attribution of the problem. By tracking the paths of shared data among different devices, the shared data is further monitored and queried to ensure the security of data sharing and the certainty of data source responsibility during the interconnection process. In addition, different devices can be interconnected pairwise. Each device can upload shared data to the server, and each device can also download shared data from the server.
[0133] The following is an example. Suppose there are four interconnected devices A, B, C, and D, and on this basis, refer to Figure 3A and Figure 3B to illustrate this solution exemplarily.
[0134] When abnormal shared data appears on the server (i.e., the above-mentioned execution subject), it is first necessary to check whether it is caused by the corresponding own device (i.e., the above-mentioned production device). That is, assume that the abnormal data belongs to device B (i.e., the above-mentioned production device). First, check whether the shared data of device B is abnormal. If it is abnormal, the responsibility attribution is directly locked. That is, the device represented by the starting node is determined as the abnormal responsible device for the target shared data.
[0135] Among them, the shared data (i.e., the above-mentioned target shared data) refers to data that can be transmitted to any other device, is not restricted by device permissions, is not restricted by privacy and security issues, has no characteristics, and does not belong to a specific device. Data abnormality is divided into two situations. One is data error caused by the initial device (i.e., the above-mentioned production device) itself, and the other is data inconsistency before and after transmission between devices. Among them, the first type of data abnormality caused by the initial device itself is judged by the device itself, and the second type of abnormality caused by transmission is judged by recording path identifiers before and after the monitoring path.
[0136] The above-mentioned corresponding self-device refers to the device that initially generated the shared data. First, check whether this abnormal data is caused by the initial device itself. Since the data may be abnormal before it is shared and transmitted after being generated by the original device, this situation should be prioritized for investigation. If so, the liability attribution can be directly locked in.
[0137] If the shared data of the above-mentioned device B is normal, the liability attribution is achieved by tracing the path (i.e., the above-mentioned target liability attribution method).
[0138] When the shared data is abnormal, record the device where the abnormality occurs, that is, the starting point of the path (i.e., the above-mentioned starting node).
[0139] During the transmission of the abnormal data between devices, the path information of the data is simultaneously recorded to the next device and continuously accumulated and updated until a device uploads it to the server, and the corresponding path information (i.e., the above-mentioned abnormal path record) can be obtained. From this, the original source of the problem can be obtained, and the liability attribution object, that is, the abnormal liability device, can be determined.
[0140] After excluding the situation caused by the abnormality of the self-device, if device B undergoes one interconnection (i.e., the target shared data is transmitted between devices once), there will be corresponding path records (i.e., the above-mentioned abnormal path records), which are device A, device C, and device D. Then the corresponding abnormal path records can be respectively expressed as device B → device A, device B → device C, and device B → device D, indicating that data abnormalities occur to device A, device C, and device D during the interconnection, and the liability attribution is determined to be device A, device C, or device D.
[0141] If device B undergoes two interconnections (such as device B → device A → device C or device B → device D → device C), if abnormal data appears in device A or device D but is not found or reported by itself until it is interconnected to device C and then uploaded to the server, and the abnormal path record is device A → device C or device D → device C, then the liability attribution is determined to be device A or device D.
[0142] Here, when data abnormalities occur during the transmission process, abnormal path records can be started. What this means is that until a device reports to the server and the monitoring discovers an abnormal path record, the path source will be locked through the abnormal path record, thereby locking the attribution of the abnormal data. In the above example, when device B is transmitted to device A or device D and an abnormality occurs, the path is started to be recorded. If device A or device D is transmitted to the server immediately, the liability of device A or device D can be directly locked. If device A or device D is not transmitted to the server and then undergoes a second transmission to device C and is uploaded by device C, the liability of device A or device D can be determined through path record tracing.
[0143] If device B is interconnected three times (e.g., device B → device A → device D → device C or device B → device D → device A → device C), and if abnormal data appears in device A and device D but is not detected or reported by itself, it passes through device D or device A until it is interconnected to device C and then uploaded. The path record is device A → device D → device C or device D → device A → device C, then the liability attribution is determined to be device A or device D.
[0144] For other multiple interconnections (e.g., device B → device A → device D → device A → device C), the situation is similar to the above. If abnormal data appears in device A for the first time and is not uploaded until it is interconnected to device C, and the path record is device A → device D → device A → device C, then the liability attribution is determined to be device A.
[0145] Thus, regardless of the number of total interconnected devices, the device with liability attribution (i.e., the above abnormal liability device) can be determined by the same method as above.
[0146] It should be noted that, in addition to the content recorded above, this embodiment may also include the technical features described in the above embodiments, so as to achieve the technical effects of the above abnormal location method for shared data. For details, please refer to the above description. For the sake of concise description, it will not be elaborated here.
[0147] The abnormal location method for shared data provided by the embodiments of this application can effectively monitor the shared data transmission process, facilitate problem finding and liability division, and greatly improve the security of shared data and the convenience and speed of finding the root cause. It is applicable to the abnormal monitoring of interconnected devices and the liability attribution of interconnected device failure problems. In this solution, whenever abnormal shared data appears on the server, the path tracing method can be used to generate corresponding link information, which is convenient for saving data for subsequent reference and solution. At the same time, the abnormal data is blocked from being downloaded and transmitted to all interconnected devices, further ensuring the transmission security of the interconnected network.
[0148] Figure 4 It is a schematic structural diagram of an abnormal location device for shared data provided by the embodiments of this application. Specifically, it includes:
[0149] An acquisition unit 401, configured to acquire target shared data;
[0150] A first determination unit 402, configured to determine whether the target shared data is abnormal shared data;
[0151] A second determination unit 403, configured to, when the target shared data is the abnormal shared data, determine the abnormal liability attribution method of the target shared data based on the target shared data;
[0152] The third determination unit 404 is configured to determine the abnormal responsible device of the target shared data based on the abnormal attribution method.
[0153] In a possible implementation manner, the determining the abnormal responsible device of the target shared data based on the abnormal attribution method includes:
[0154] When the abnormal attribution method is the target attribution method, determining the abnormal path record of the target shared data, where the target attribution method indicates that the abnormal attribution of the target shared data is performed through the abnormal path record, and the abnormal path record indicates the transmission path when the target shared data is abnormal;
[0155] Based on the abnormal path record, determining the abnormal responsible device of the target shared data.
[0156] In a possible implementation manner, after determining the abnormal attribution method of the target shared data based on the target shared data, and before determining the abnormal path record of the target shared data when the abnormal attribution method is the target attribution method, the apparatus further includes:
[0157] A fourth determination unit (not shown in the figure) is configured to determine the device that produces the target shared data to obtain the production device of the target shared data;
[0158] A fifth determination unit (not shown in the figure) is configured to determine whether the production device is the abnormal responsible device of the target shared data.
[0159] In a possible implementation manner, the determining the abnormal path record of the target shared data when the abnormal attribution method is the target attribution method includes:
[0160] When the determination result indicates that the production device is not the abnormal responsible device of the target shared data, and the abnormal attribution method is the target attribution method, determining the abnormal path record of the target shared data.
[0161] In a possible implementation manner, the starting node of the transmission path indicates the device that determines that the target shared data is abnormal; and
[0162] The determining the abnormal responsible device of the target shared data based on the abnormal path record includes:
[0163] Determining the starting node of the transmission path represented by the abnormal path record;
[0164] Determining the device represented by the starting node as the abnormal responsible device of the target shared data.
[0165] In a possible implementation, the target shared data and the abnormal path record are transmitted independently.
[0166] In a possible implementation, when the target shared data is the abnormal shared data, the device further includes:
[0167] A sixth determination unit (not shown in the figure), configured to determine whether a data request for the target shared data is received;
[0168] A rejection unit (not shown in the figure), configured to reject providing the target shared data when the data request is received.
[0169] The abnormal location device for shared data provided in this embodiment may be the abnormal location device for shared data as shown in Figure 4 The abnormal location device for shared data can execute all steps of the above-mentioned abnormal location methods for each shared data, and further achieve the technical effects of the above-mentioned abnormal location methods for each shared data. For specific reference, please refer to the above relevant descriptions. For the sake of concise description, it will not be elaborated here.
[0170] Figure 5 FIG. is a schematic structural diagram of an electronic device provided in an embodiment of the present application. Figure 5 The electronic device 500 shown includes: at least one processor 501, a memory 502, at least one network interface 504, and other user interfaces 503. Each component in the electronic device 500 is coupled together through a bus system 505. It can be understood that the bus system 505 is used to realize the connection and communication between these components. In addition to the data bus, the bus system 505 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clear illustration, in Figure 5 All kinds of buses are labeled as the bus system 505.
[0171] Among them, the user interface 503 may include a display, a keyboard, or a pointing device (for example, a mouse, a trackball, a touchpad, or a touch screen, etc.).
[0172] It can be understood that the memory 502 in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synch link dynamic random access memory (SLDRAM), and direct rambus random access memory (DRRAM). The memory 502 described herein is intended to include, but is not limited to, these and any other suitable types of memory.
[0173] In some embodiments, the memory 502 stores the following elements, executable units, or data structures, or subsets thereof, or extended sets thereof: an operating system 5021 and an application program 5022.
[0174] Among them, the operating system 5021 includes various system programs, such as a framework layer, a core library layer, a driver layer, etc., and is used to implement various basic services and process hardware-based tasks. The application program 5022 includes various application programs, such as a media player and a browser, etc., and is used to implement various application services. The program for implementing the method of the embodiments of the present application may be included in the application program 5022.
[0175] In this embodiment, by calling the program or instruction stored in the memory 502, specifically, the program or instruction stored in the application program 5022, the processor 501 is used to execute the method steps provided by each method embodiment, for example, including:
[0176] Obtain target shared data;
[0177] Determine whether the target shared data is abnormal shared data;
[0178] In the case that the target shared data is the abnormal shared data, determine the abnormal attribution method of the target shared data based on the target shared data;
[0179] Determine the abnormal responsible device of the target shared data based on the abnormal attribution method.
[0180] The method disclosed in the embodiments of the present application above can be applied to or implemented by the processor 501. The processor 501 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the integrated logic circuit in the hardware of the processor 501 or the instructions in the form of software. The above processor 501 may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components. It can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc. The steps of the method disclosed in combination with the embodiments of the present application can be directly embodied as being executed and completed by a hardware decoding processor, or executed and completed by a combination of the hardware and software units in the decoding processor. The software unit may be located in a mature storage medium in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. This storage medium is located in the memory 502, and the processor 501 reads the information in the memory 502 and combines its hardware to complete the steps of the above method.
[0181] It will be appreciated that the embodiments described herein may be implemented in hardware, software, firmware, middleware, microcode, or any combination thereof. For hardware implementation, the processing unit may be implemented in one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), general purpose processors, controllers, microcontrollers, microprocessors, other electronic units for performing the above functions of this application, or any combination thereof.
[0182] For software implementation, the above-described technologies herein may be implemented by units that execute the above functions herein. The software code may be stored in a memory and executed by a processor. The memory may be implemented within the processor or externally to the processor.
[0183] The electronic device provided in this embodiment may be an electronic device as shown in Figure 5 which can execute all the steps of the above-described method for abnormal location of shared data, and thus achieve the technical effects of the above-described method for abnormal location of shared data. For specific reference, please refer to the above relevant descriptions. For the sake of brevity, it will not be elaborated herein.
[0184] The embodiments of this application also provide a storage medium (computer-readable storage medium). The storage medium stores one or more programs herein. Among them, the storage medium may include volatile memory, such as random access memory; the memory may also include non-volatile memory, such as read-only memory, flash memory, hard disk, or solid-state drive; the memory may also include a combination of the above types of memory.
[0185] When one or more programs in the storage medium can be executed by one or more processors to implement the above-described method for abnormal location of shared data executed on the electronic device side.
[0186] The above processor is used to execute the program for abnormal location of shared data stored in the memory to implement the following steps of the method for abnormal location of shared data executed on the electronic device side:
[0187] Obtain the target shared data;
[0188] Determine whether the target shared data is abnormal shared data;
[0189] When the target shared data is the abnormal shared data, based on the target shared data, determine the abnormal attribution method of the target shared data;
[0190] Based on the abnormal attribution method, determine the abnormal responsible device of the target shared data.
[0191] Those skilled in the art should further realize that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be implemented by electronic hardware, computer software, or a combination of the two. To clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described according to functions in the above description. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of this application.
[0192] The steps of the methods or algorithms described in combination with the embodiments disclosed herein can be implemented by hardware, software modules executed by a processor, or a combination of the two. The software modules can be placed in a random access memory (RAM), internal memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium well-known in the technical field.
[0193] It should be understood that the terms used herein are only for the purpose of describing specific example embodiments and are not intended to be limiting. Unless otherwise clearly specified in the context, the singular forms "a", "an", and "the" as used herein may also include the plural forms. The terms "comprising", "including", "containing", and "having" are inclusive and thus specify the presence of the stated features, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, steps, operations, elements, components, and / or combinations thereof. The method steps, processes, and operations described herein are not to be construed as necessarily requiring them to be executed in the specific order described or illustrated, unless the execution order is clearly specified. It should also be understood that alternative or additional steps may be used.
[0194] The above description is only a specific implementation manner of this application, enabling those skilled in the art to understand or implement this application. Various modifications to these embodiments will be obvious to those skilled in the art, and the general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application will not be limited to the embodiments shown herein, but will conform to the widest scope consistent with the principles and novel features claimed herein.
Claims
1. A method for locating anomalies in shared data, characterized in that: The method comprises: Get target shared data; Determining whether the target shared data is abnormal shared data; In a case where the target shared data is the abnormal shared data, determining, based on the target shared data, a method for attributing the abnormality of the target shared data; Based on the abnormality attribution method, the abnormality responsible device of the target shared data is determined.
2. The method according to claim 1, characterized in that The determining the abnormal responsible device of the target shared data based on the abnormal attribution mode includes: In the case where the abnormality attribution method is a target attribution method, determining an abnormal path record of the target shared data, wherein the target attribution method indicates that the target shared data is abnormally attributed through the abnormal path record, and the abnormal path record indicates a transmission path when the target shared data is abnormal; Based on the abnormal path record, the abnormal responsible device of the target shared data is determined.
3. The method according to claim 2, characterized in that After determining the abnormality attribution mode of the target shared data based on the target shared data, and before determining the abnormal path record of the target shared data when the abnormality attribution mode is the target attribution mode, the method further includes: Determine a device that produces the target shared data to obtain the device that produces the target shared data; It is determined whether the production device is an abnormal responsible device for the target shared data.
4. The method according to claim 3, characterized in that When the abnormality attribution mode is a target attribution mode, determining the abnormal path record of the target shared data includes: When the determination result indicates that the production device is not the abnormality responsible device of the target shared data, and the abnormality attribution method is the target attribution method, the abnormal path record of the target shared data is determined.
5. The method according to claim 2, characterized in that: The starting node of the transmission path represents a device that determines that the target shared data has an abnormality; as well as The determining, based on the abnormal path record, the abnormal responsible device of the target shared data comprises: Determining a starting node of the transmission path represented by the abnormal path record; The device represented by the starting node is determined as the abnormal responsible device of the target shared data.
6. The method according to claim 2, characterized in that The target shared data and the abnormal path record are transmitted independently.
7. The method according to any one of claims 1 to 6, characterized in that: In a case where the target shared data is the abnormal shared data, the method further includes: determining whether a data request for the target shared data is received; In case of receiving the data request, refusing to provide the target shared data.
8. A device for locating anomalies in shared data, characterized in that: The device comprises: An acquisition unit, used for acquiring target shared data; A first determining unit, configured to determine whether the target shared data is abnormal shared data; a second determining unit, configured to determine, when the target shared data is the abnormal shared data, based on the target shared data, an abnormal attribution method of the target shared data; The third determining unit is used to determine the abnormal responsible device of the target shared data based on the abnormal attribution method.
9. An electronic device, characterized in that: include: Memory for storing computer programs; A processor is used to execute a computer program stored in the memory, and when the computer program is executed, the method for locating anomalies in shared data of any one of claims 1 to 7 is implemented.
10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method for locating anomalies in shared data according to any one of claims 1 to 7 is implemented.