Data auditing method and device

Abstract

The present disclosure relates to the field of wireless technology, and particularly relates to a data auditing method and device. The method comprises: in the case of performing an updating operation on a voice over long term evolution (VOLTE) data, sending the first voice over long term evolution (VOLTE) data to at least one node; receiving a data auditing request sent by a first node of the at least one node, wherein the data auditing request is generated by the first node in the case of determining that the first voice over long term evolution (VOLTE) data is inconsistent with second voice over long term evolution (VOLTE) data stored in the first node; in response to the data auditing request, sending a first voting request corresponding to the first voice over long term evolution (VOLTE) data to the at least one node, and determining target voice over long term evolution (VOLTE) data according to voting results sent by the at least one node for the first voting request. The present disclosure can improve the accuracy and efficiency of data auditing.

Description

Technical Field

[0001] This disclosure relates to the field of wireless technology, and in particular to a data auditing method and apparatus. Background Technology

[0002] With the development of science and technology, improving service quality and reducing the probability of user complaints have become the focus of user attention. For example, in the auditing of Voice over Long-Term Evolution (VOLTE) data, manual cross-departmental collaboration can be carried out, but this process is inefficient and time-consuming. Summary of the Invention

[0003] This disclosure provides a data auditing method and apparatus, which can improve the accuracy and efficiency of data auditing. The technical solution of this disclosure is as follows:

[0004] According to a first aspect of the present disclosure, a data auditing method is provided, comprising:

[0005] When performing an update operation on LTE Voice Bearer (VOLTE) data, first LTE Voice Bearer (VOLTE) data is sent to at least one node, wherein the at least one node includes at least one terminal and / or at least one core network element.

[0006] Receive a data audit request sent by the first node among the at least one nodes, wherein the data audit request is generated by the first node after determining that the first LTE Voice Bearer (VOLTE) data is inconsistent with the second LTE Voice Bearer (VOLTE) data stored in the first node;

[0007] In response to the data audit request, a first voting request corresponding to the first LTE Voice Bearer (VOLTE) data is sent to the at least one node, and the target LTE Voice Bearer (VOLTE) data is determined based on the voting results sent by the at least one node in response to the first voting request.

[0008] According to some embodiments, when performing an update operation on the VoLTE data, sending the first VoLTE data to at least one node includes:

[0009] When performing an update operation on the LTE Voice Bearer (VOLTE) data, a first sequence number corresponding to the update operation is generated, and a first version number corresponding to the first LTE Voice Bearer (VOLTE) data is generated.

[0010] Send the first serial number and the first version number to the at least one node.

[0011] According to some embodiments, determining the target LTE voice bearer VoLTE data based on the voting result sent by the at least one node in response to the first voting request includes:

[0012] If the first voting result sent by at least one node in response to the first voting request meets the result requirements, the first sequence number and the first version number are determined as target LTE Voice Bearer (VOLTE) data.

[0013] Store the target LTE Voice Bearer (VOLTE) data;

[0014] Send the target LTE Voice Bearer VoLTE data to the at least one node;

[0015] or

[0016] Send the target LTE Voice Bearer (VOLTE) data to a target node among the at least one nodes, wherein the target node is a node among the at least one nodes whose first voting result is not the preset result.

[0017] According to some embodiments, determining the target LTE voice bearer VoLTE data based on the voting result sent by the at least one node in response to the first voting request includes:

[0018] If the voting result sent by at least one node in response to the first voting request does not meet the result requirements, a second voting request is sent to at least one node, wherein the second sharding request includes a second sequence number and a second version number, the second sequence number being the previous sequence number adjacent to the first sequence number, and the second version number being the previous version number adjacent to the first version number;

[0019] If the second voting result sent by at least one node in response to the second voting request meets the result requirements, the second sequence number and the second version number are determined as target LTE Voice Bearer (VOLTE) data.

[0020] Store the target LTE Voice Bearer (VOLTE) data;

[0021] Send the target LTE Voice Bearer VoLTE data to the at least one node;

[0022] or

[0023] Send the target LTE Voice Bearer (VOLTE) data to a target node among the at least one node, wherein the target node is a node among the at least one node whose second voting result is not the preset result.

[0024] According to some embodiments, the method further includes:

[0025] Acquire and store the audit record of the first LTE voice bearer VoLTE data;

[0026] Upon receiving a call instruction from the terminal for the audit record, the audit record is sent to the terminal.

[0027] According to some embodiments, the method further includes:

[0028] Based on preset selection criteria, obtain the target LTE Voice Bearer (VOLTE) user identifier;

[0029] By acquiring data corresponding to any one of the at least one nodes, the VoLTE data corresponding to the target VoLTE user identifier is obtained.

[0030] According to a second aspect of the present disclosure, a data auditing apparatus is provided, comprising:

[0031] The data transmission unit is configured to transmit first LTE VoLTE data to at least one node when performing an update operation on LTE VoLTE data, wherein the at least one node includes at least one terminal and / or at least one core network element.

[0032] The request receiving unit is configured to receive a data audit request sent by the first node among the at least one node, wherein the data audit request is generated by the first node after determining that the first LTE Voice Bearer (VOLTE) data is inconsistent with the second LTE Voice Bearer (VOLTE) data stored in the first node;

[0033] The request sending unit is configured to, in response to the data audit request, send a first voting request corresponding to the first LTE Voice Bearer (VOLTE) data to the at least one node, and determine the target LTE Voice Bearer (VOLTE) data based on the voting results sent by the at least one node in response to the first voting request.

[0034] According to a third aspect of the present disclosure, a network device is provided, comprising:

[0035] processor;

[0036] Memory used to store the processor's executable instructions;

[0037] The processor is configured to execute the instructions to implement the data auditing method described in any one of the preceding aspects.

[0038] According to a fourth aspect of the present disclosure, a storage medium is provided that, when instructions in the storage medium are executed by a processor of a network device, enables the network device to perform the data auditing method described in any one of the preceding aspects.

[0039] According to a fifth aspect of the present disclosure, a computer program product is provided, including a computer program that, when executed by a processor, implements the method described in any one of the preceding aspects.

[0040] The technical solutions provided by the embodiments of this disclosure have at least the following beneficial effects:

[0041] In some or related embodiments, when performing an update operation on LTE VoLTE data, first LTE VoLTE data is sent to at least one node, wherein the at least one node includes at least one terminal and / or at least one core network element; a data audit request is received from a first node among the at least one node, wherein the data audit request is generated by the first node determining that the first LTE VoLTE data is inconsistent with second LTE VoLTE data stored in the first node; in response to the data audit request, a first voting request corresponding to the first LTE VoLTE data is sent to the at least one node, and the target LTE VoLTE data is determined based on the voting results sent by the at least one node in response to the first voting request. Therefore, a data audit mechanism can be provided to determine the target data through a voting mechanism, eliminating the need for manual intervention. This reduces the time spent on manual collaboration between departments, reduces manual audit costs, reduces inaccuracies in manual audits, improves the consistency of data stored by each node, and enhances the accuracy and efficiency of data audits.

[0042] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0043] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure, and are not intended to unduly limit this disclosure.

[0044] Figure 1 This is an overall flowchart illustrating a VoLTE service according to an exemplary embodiment;

[0045] Figure 2 This is a flowchart illustrating a data auditing method according to an exemplary embodiment;

[0046] Figure 3 This is a flowchart illustrating a data auditing method according to an exemplary embodiment;

[0047] Figure 4 This is a schematic diagram of the architecture of a data auditing system according to an exemplary embodiment;

[0048] Figure 5 This is a flowchart illustrating a data auditing method according to an exemplary embodiment;

[0049] Figure 6 This is a block diagram illustrating a data auditing apparatus according to an exemplary embodiment;

[0050] Figure 7 This is a block diagram illustrating a network device according to an exemplary embodiment. Detailed Implementation

[0051] To enable those skilled in the art to better understand the technical solutions of this disclosure, the technical solutions in the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings.

[0052] This disclosure provides data auditing methods and apparatus. In some embodiments, the terms "data auditing method" and "information processing method" and "communication method" can be used interchangeably; the terms "data auditing apparatus" and "information processing apparatus" and "communication apparatus" can be used interchangeably; and the terms "information processing system" and "communication system" can be used interchangeably.

[0053] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0054] In each of the disclosed embodiments, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of the embodiments are consistent and can be referenced by each other. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0055] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.

[0056] In this embodiment of the disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the," "the," "the," "the," "the," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun following the article can be understood as either a singular expression or a plural expression.

[0057] In the embodiments disclosed herein, "multiple" refers to two or more.

[0058] In some embodiments, the terms “at least one of”, “one or more”, “a plurality of”, “multiple”, etc., may be used interchangeably.

[0059] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.

[0060] In some embodiments, "terminal" or "terminal device" may be referred to as "user equipment (UE)," "user terminal," "mobile station (MS)," "mobile terminal (MT)," "subscriber station," "mobile unit," "subscriber unit," "wireless unit," "remote unit," "mobile device," "wireless device," "wireless communication device," "remote device," "mobile subscriber station," "access terminal," "mobile terminal," "wireless terminal," "remote terminal," "handset," "user agent," "mobile client," "client," etc.

[0061] In some embodiments, data, information, etc., may be obtained with the user's consent.

[0062] It should be noted that the terms "first," "second," etc., used in the specification, claims, and accompanying drawings of this disclosure are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this disclosure described herein can be implemented in orders other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this disclosure as detailed in the appended claims.

[0063] In some embodiments, Figure 1 This is an overall flowchart illustrating a VoLTE service according to an exemplary embodiment, such as... Figure 1As shown, a user's VoLTE function is generally initiated by Customer Relationship Management (CRM) for subscription / cancellation. After the service activation node performs protocol conversion, the converted Simple Object Access Protocol (SOAP) instructions are sent to the corresponding core network equipment Home Subscriber Server (HSS), VoLTE, and Telephone Number Mapping (ENUM) network elements. Then, the service activation department analyzes and integrates the network element-side instruction implementation results and returns the final order result to the CRM system, completing the subscription / cancellation process.

[0064] However, for tasks such as order creation and user status changes, it is necessary to maintain data consistency across multiple platform systems, including CRM, service activation, and network maintenance. For example, this could be accomplished through manual collaboration among multiple departments, which is inefficient, time-consuming, and lacks monitoring mechanisms, leading to a higher probability of user complaints.

[0065] Figure 2 This is a flowchart illustrating a data auditing method according to an exemplary embodiment, such as... Figure 2 As shown, this data auditing method can be used in data auditing scenarios and includes the following steps:

[0066] In step S11, when performing an update operation on the VoLTE data, the first VoLTE data is sent to at least one node, wherein the at least one node includes at least one terminal and / or at least one core network element.

[0067] According to some embodiments, the implementing entity of this disclosure may be, for example, a network device. The name of this network device is not limited. For example, the network device may also be called a server or a server cluster. This disclosure does not limit this.

[0068] In some embodiments, Voice over Long-Term Evolution (VOLTE) is based on the IP Multimedia Subsystem (IMS) network and uses profiles specifically designed for the control plane and media plane of voice services on LTE. This allows voice services (control and media planes) to be transmitted as data streams in the LTE data bearer network without the need to maintain and rely on the traditional circuit-switched voice network.

[0069] In some embodiments, the VoLTE data is data associated with the VoLTE bearer. An update operation may, for example, be an operation that updates the VoLTE data. This update operation is not specific to a particular fixed operation; for example, the update operation may change accordingly when the operation time changes.

[0070] In some instances, the first LTE VoLTE bearer data can be used to indicate the data stored by each node after an update operation. This first LTE VoLTE bearer data does not specifically refer to any fixed data. For example, when the data information in the first LTE VoLTE bearer data changes, the first LTE VoLTE bearer data can also change accordingly. For example, when the data audit time point changes, the first LTE VoLTE bearer data can also change accordingly.

[0071] According to some embodiments, at least one node may be, for example, a node storing VoLTE data, wherein the at least one node includes at least one terminal and / or at least one core network element. The core network element includes, but is not limited to, HSS, VoLTE network element, and ENUM network element. The terminal includes, but is not limited to, terminals corresponding to each province or service activation terminals.

[0072] In some embodiments, when performing an update operation on LTE VoLTE data, first LTE VoLTE data is sent to at least one node, wherein the at least one node includes at least one terminal and / or at least one core network element.

[0073] In step S12, a data audit request is received from the first node among the at least one node, wherein the data audit request is generated by the first node after determining that the first LTE Voice Bearer (VOLTE) data is inconsistent with the second LTE Voice Bearer (VOLTE) data stored in the first node;

[0074] According to some embodiments, the first node may be, for example, the node among at least one nodes that determines that the first LTE VoLTE data is inconsistent with the second LTE VoLTE data stored in the first node. This first node does not specifically refer to a fixed node. For example, the first node may change accordingly when its name changes. Similarly, the first node may change accordingly when the second LTE VoLTE data stored in the first node changes.

[0075] In some embodiments, the second LTE VoLTE data can be used, for example, to indicate the LTE VoLTE data stored in the node. The "second" in this second LTE VoLTE data is used to distinguish it from the first LTE VoLTE data and does not specifically refer to any fixed data. For example, when the specific data included in the second LTE VoLTE data changes, the second LTE VoLTE data can also change accordingly.

[0076] In some embodiments, when a network device sends first LTE VoLTE data to at least one node, any one of the at least one nodes can determine whether the first LTE VoLTE data is consistent with second LTE VoLTE data stored in that node. If it is determined that they are inconsistent, any node can send a data audit request to the network device.

[0077] According to some embodiments, a data audit request sent by a first node among the at least one node is received, wherein the data audit request is generated by the first node after determining that the first LTE Voice Bearer (VOLTE) data is inconsistent with the second LTE Voice Bearer (VOLTE) data stored in the first node.

[0078] In step S13, in response to the data audit request, a first voting request corresponding to the first LTE Voice Bearer (VOLTE) data is sent to the at least one node, and the target LTE Voice Bearer (VOLTE) data is determined based on the voting results sent by the at least one node in response to the first voting request.

[0079] According to some embodiments, a first voting request refers to a request instructing at least one node to vote on first LTE Voice Bearer (VoLTE) data. The "first" in the first voting request does not specifically refer to a fixed request. For example, the first voting request may change if the LTE Voice Bearer (VoLTE) data in the first voting request changes. The first voting request may also change if the transmission time point corresponding to it changes.

[0080] In some embodiments, the voting result may be, for example, the result sent by at least one node after receiving a first voting request and determining whether the first LTE VoLTE data is consistent with the second LTE VoLTE data stored in the node. This voting result is not specific to any particular fixed result. For example, the voting result may change accordingly when the second LTE VoLTE data stored in any node changes.

[0081] Optionally, the target LTE VoLTE data can refer to the same LTE VoLTE data stored across all nodes. This target LTE VoLTE data does not specifically refer to a particular fixed LTE VoLTE data set. For example, when the specific data corresponding to the target LTE VoLTE data changes, the target LTE VoLTE data can also change accordingly.

[0082] In some embodiments, for example, in response to the data audit request, a first voting request corresponding to the first LTE Voice Bearer (VOLTE) data may be sent to the at least one node, and the target LTE Voice Bearer (VOLTE) data may be determined based on the voting results sent by the at least one node in response to the first voting request.

[0083] In some or related embodiments, when performing an update operation on LTE VoLTE data, first LTE VoLTE data is sent to at least one node, wherein the at least one node includes at least one terminal and / or at least one core network element; a data audit request is received from a first node among the at least one node, wherein the data audit request is generated by the first node determining that the first LTE VoLTE data is inconsistent with second LTE VoLTE data stored in the first node; in response to the data audit request, a first voting request corresponding to the first LTE VoLTE data is sent to the at least one node, and the target LTE VoLTE data is determined based on the voting results sent by the at least one node in response to the first voting request. Therefore, a data audit mechanism can be provided to determine the target data through a voting mechanism, eliminating the need for manual intervention, reducing the time spent on manual collaboration between departments, reducing manual audit costs, reducing inaccuracies in manual audits, and improving the accuracy and efficiency of data audits.

[0084] Figure 3 This is a flowchart illustrating a data auditing method according to an exemplary embodiment, such as... Figure 3 As shown, this data auditing method can be used in data auditing scenarios and includes the following steps:

[0085] In step S21, when an update operation is performed on the LTE Voice Bearer (VOLTE) data, a first sequence number corresponding to the update operation is generated, and a first version number corresponding to the first LTE Voice Bearer (VOLTE) data is generated.

[0086] The specific process is as described above and will not be repeated here.

[0087] In some embodiments, the first sequence number is used to uniquely identify the current update operation. For example, different update operations may correspond to different sequence numbers. The "first" in the first sequence number is used to distinguish it from other sequence numbers and does not specifically refer to a fixed sequence number. For example, when the composition of the first sequence number changes, the first sequence number may also change accordingly. For example, when the VoLTE data corresponding to the update operation changes, the first sequence number may also change accordingly.

[0088] According to some embodiments, the first version number is used to uniquely identify the version number of LTE Voice Bearer (VoLTE) data. For example, different LTE VoLTE data may correspond to different version numbers. The "first" in the first version number is used to distinguish it from other version numbers, and the first version number does not specifically refer to a fixed version number.

[0089] For example, Figure 4 This is a schematic diagram of the architecture of a data auditing system according to an exemplary embodiment, such as... Figure 4 As shown, the data audit module in the network device is responsible for receiving and processing all write requests, and then replicating the updated data to each node system. During this process, the data audit module generates a unique sequence number (N1) for each update operation and sends it along with the latest version number (V1) to each node system. Each node stores the received sequence number (N1) and version number (V1) locally to determine whether the current data has expired or been tampered with. If a node determines that the data stored locally is inconsistent with the audit data, the network device can initiate a voting request to other nodes to determine which version or which data meets the requirements.

[0090] According to some embodiments, the method further includes:

[0091] Based on preset selection criteria, obtain the target LTE Voice Bearer (VOLTE) user identifier;

[0092] By acquiring data corresponding to any one of the at least one nodes, the VoLTE data corresponding to the target VoLTE user identifier is obtained.

[0093] According to some embodiments, the preset selection conditions may be set based on received condition setting instructions, or they may be default values; this disclosure does not limit this. The preset selection conditions may, for example, be used to determine the collected user identifier. The preset selection conditions do not specifically refer to a fixed condition. For example, when a condition modification instruction is received, the preset selection conditions may also change accordingly.

[0094] According to some embodiments, in Customer Relationship Management (CRM), target users who meet preset selection criteria can be collected. These preset selection criteria can be flexibly configured according to business needs, and the object collection module in the network device can select users who meet the criteria as the data collection targets for this data audit. Specifically, for example:

[0095] A: Collect CRM node database, users who have processed changes to product A within 2 days, and whose work orders failed with the first error code;

[0096] B: The data collection service opens the database and orders VoLTE through the VoLTE self-activation channel. The network equipment returns the second error code for the user whose construction error code is the second error code.

[0097] C: Collect the CRM node library, including all users who have ordered or canceled product A within a preset target number of days.

[0098] According to some embodiments, different nodes may correspond to different data acquisition methods. Specific acquisition methods are shown in Table 1, for example.

[0099] Table 1

[0100]

[0101] In step S22, the first sequence number and the first version number are sent to the at least one node, wherein the at least one node includes at least one terminal and / or at least one core network element;

[0102] The specific process is as described above and will not be repeated here.

[0103] Target nodes may include, for example, provincial CRM, service activation, HSS, VoLTE network elements, and ENUM network elements.

[0104] In step S23, a data audit request is received from the first node among the at least one node, wherein the data audit request is generated by the first node after determining that the first LTE Voice Bearer (VOLTE) data is inconsistent with the second LTE Voice Bearer (VOLTE) data stored in the first node;

[0105] The specific process is as described above and will not be repeated here.

[0106] In some embodiments, the first LTE VoLTE data may be, for example, a first sequence number (N1) and a first version number (V1), and the network device may send the first sequence number (N1) and the first version number (V1) to at least one node. For example, when the second LTE VoLTE data stored in node A is the first sequence number (N1) and the first version number (V1), node A does not send a data audit request. When the second LTE VoLTE data stored in node A is the second sequence number (N2) and the second version number (V2), node A may send a data audit request.

[0107] In step S24, in response to the data audit request, a first voting request corresponding to the first LTE Voice Bearer (VOLTE) data is sent to the at least one node, and the target LTE Voice Bearer (VOLTE) data is determined based on the voting results sent by the at least one node in response to the first voting request.

[0108] The specific process is as described above and will not be repeated here.

[0109] According to some embodiments, determining the target LTE voice bearer VoLTE data based on the voting result sent by the at least one node in response to the first voting request includes:

[0110] If the first voting result sent by at least one node in response to the first voting request meets the result requirements, the first sequence number and the first version number are determined as target LTE Voice Bearer (VOLTE) data.

[0111] Store the target LTE Voice Bearer (VOLTE) data;

[0112] Send the target LTE Voice Bearer VoLTE data to the at least one node;

[0113] or

[0114] The target LTE Voice Bearer (VOLTE) data is sent to a target node among the at least one node, wherein the target node is the node whose first voting result is not the preset result. Therefore, when the first sequence number and the first version number are determined to be the target LTE Voice Bearer (VOLTE) data, the target LTE Voice Bearer (VOLTE) data can be sent to at least one node. This provides a data auditing mechanism without requiring manual maintenance, reducing manual maintenance costs and improving the accuracy and efficiency of data auditing.

[0115] According to some embodiments, determining the target LTE voice bearer VoLTE data based on the voting result sent by the at least one node in response to the first voting request includes:

[0116] If the voting result sent by at least one node in response to the first voting request does not meet the result requirements, a second voting request is sent to at least one node, wherein the second sharding request includes a second sequence number and a second version number, the second sequence number being the previous sequence number adjacent to the first sequence number, and the second version number being the previous version number adjacent to the first version number;

[0117] If the second voting result sent by at least one node in response to the second voting request meets the result requirements, the second sequence number and the second version number are determined as target LTE Voice Bearer (VOLTE) data.

[0118] Store the target LTE Voice Bearer (VOLTE) data;

[0119] Send the target LTE Voice Bearer VoLTE data to the at least one node;

[0120] or

[0121] Send the target LTE Voice Bearer (VOLTE) data to a target node among the at least one node, wherein the target node is a node among the at least one node whose second voting result is not the preset result.

[0122] In some embodiments, Figure 5 This is a flowchart illustrating a data auditing method according to an exemplary embodiment, such as... Figure 5 As shown, the data audit module in the network device can initiate a voting election. Each node can return the status information and data anomaly information of the users in the node. The data audit module counts the returned votes and user status, and uses the user status with the highest score as the user's final status. Based on this status, it checks whether the user information returned by each system is normal. If the number of systems participating in the vote is greater than or equal to half of the total number of systems, the voting election is successful, and the data audit module determines the version number (V1) as the target version and stores the data [number:N1:V1]. If the number of systems participating in the vote is less than half of the total number of systems, the sequence number (N2) and version number (V2) are automatically incremented, and the voting election process is retried until the m-th voting election is successful, and finally the data [number:Nm:Vm] is stored.

[0123] In some embodiments, the voting result will be determined by the majority system results, which can improve the accuracy of data version determination. The data audit module will notify each node of the final election result: [User Number: 136XXXXXXXX, System Identifier: CRM, VoLTE Status: In Use, IMSI: 46000XXXXXX, Target System Current Status: In Use]. For systems with inconsistent data, after receiving the election result notification, a unified construction process will be triggered simultaneously to align the VoLTE data by resending work orders or resetting work orders to the system.

[0124] In some embodiments, based on data auditing and data collection results, if there are discrepancies between the data and the election results, the unified construction module in the network device automatically calls interfaces such as resend work orders, HLR reset, and VoLTE reset to send relevant instructions to the inconsistent nodes to perform construction, eliminate data differences, and achieve the goal of automatic auditing. For example:

[0125] Scenario 1: The data audit module determines that user A is a VoLTE user. The HSS platform has user information but lacks 92APNID (IMS APN). The unified construction module initiates a call to the BOSS system interface to send an HLR reset work order, re-signing the correct APN. Finally, user A signs up for 92APNID on the HSS platform, completing the audit.

[0126] Scenario 2: The data audit module determines that user B is a VoLTE user with IMSI = 4600xxxx111. The VoLTE platform has user account information, but the IMSI is 4600xxxx123, indicating an IMSI discrepancy. The unified construction module initiates a call to the BOSS system interface to send a VoLTE reset work order. The RMV_SUB command in the reset work order deletes IMSI = 4600xxxx123 and re-signs the contract with IMSI = 4600xxxx111. Ultimately, user B is a VoLTE user with IMSI = 4600xxxx111 on the VoLTE platform, completing the audit.

[0127] According to some embodiments, the method further includes:

[0128] Acquire and store the audit record of the first LTE voice bearer VoLTE data;

[0129] Upon receiving a request from a terminal for the audit record, the audit record is sent to the terminal. This improves the ease with which the terminal can access the audit record and facilitates the deployment of monitoring alerts.

[0130] In some or related embodiments, when performing an update operation on VoLTE data, a first sequence number corresponding to the update operation is generated, and a first version number corresponding to the first VoLTE data is generated; the first sequence number and the first version number are sent to the at least one node, wherein the at least one node includes at least one terminal and / or at least one core network element; therefore, the uniqueness of the data can be determined by the sequence number and the version number, reducing the repeated auditing process of the data, reducing the complexity of the data auditing steps, improving the data auditing steps, and improving the accuracy and efficiency of data auditing.

[0131] A block diagram of a data auditing apparatus is shown according to an exemplary embodiment. (Refer to...) Figure 6 The device 600 includes:

[0132] The data transmission unit 601 is configured to transmit first LTE VoLTE data to at least one node when performing an update operation on LTE VoLTE data, wherein the at least one node includes at least one terminal and / or at least one core network element.

[0133] The request receiving unit 602 is configured to receive a data audit request sent by the first node among the at least one node, wherein the data audit request is generated by the first node after determining that the first LTE Voice Bearer (VOLTE) data is inconsistent with the second LTE Voice Bearer (VOLTE) data stored in the first node;

[0134] The request sending unit 603 is configured to, in response to the data audit request, send a first voting request corresponding to the first LTE Voice Bearer (VOLTE) data to the at least one node, and determine the target LTE Voice Bearer (VOLTE) data based on the voting results sent by the at least one node in response to the first voting request.

[0135] According to some embodiments, the data sending unit 601, when sending first LTE VoLTE data to at least one node during an update operation on LTE VoLTE data, is specifically used for:

[0136] When performing an update operation on the LTE Voice Bearer (VOLTE) data, a first sequence number corresponding to the update operation is generated, and a first version number corresponding to the first LTE Voice Bearer (VOLTE) data is generated.

[0137] Send the first serial number and the first version number to the at least one node.

[0138] According to some embodiments, the data sending unit 601, when determining the target LTE voice bearer VoLTE data based on the voting results sent by the at least one node in response to the first voting request, is specifically used for:

[0139] If the first voting result sent by at least one node in response to the first voting request meets the result requirements, the first sequence number and the first version number are determined as target LTE Voice Bearer (VOLTE) data.

[0140] Store the target LTE Voice Bearer (VOLTE) data;

[0141] Send the target LTE Voice Bearer VoLTE data to the at least one node;

[0142] or

[0143] Send the target LTE Voice Bearer (VOLTE) data to a target node among the at least one nodes, wherein the target node is a node among the at least one nodes whose first voting result is not the preset result.

[0144] According to some embodiments, the data sending unit 601, when determining the target LTE voice bearer VoLTE data based on the voting results sent by the at least one node in response to the first voting request, is specifically used for:

[0145] If the voting result sent by at least one node in response to the first voting request does not meet the result requirements, a second voting request is sent to at least one node, wherein the second sharding request includes a second sequence number and a second version number, the second sequence number being the previous sequence number adjacent to the first sequence number, and the second version number being the previous version number adjacent to the first version number;

[0146] If the second voting result sent by at least one node in response to the second voting request meets the result requirements, the second sequence number and the second version number are determined as target LTE Voice Bearer (VOLTE) data.

[0147] Store the target LTE Voice Bearer (VOLTE) data;

[0148] Send the target LTE Voice Bearer VoLTE data to the at least one node;

[0149] or

[0150] Send the target LTE Voice Bearer (VOLTE) data to a target node among the at least one node, wherein the target node is a node among the at least one node whose second voting result is not the preset result.

[0151] According to some embodiments, the request sending unit 603 is further specifically used for:

[0152] Acquire and store the audit record of the first LTE voice bearer VoLTE data;

[0153] Upon receiving a call instruction from the terminal for the audit record, the audit record is sent to the terminal.

[0154] According to some embodiments, the data sending unit 601 is further specifically used for:

[0155] Based on preset selection criteria, obtain the target LTE Voice Bearer (VOLTE) user identifier;

[0156] By acquiring data corresponding to any one of the at least one nodes, the VoLTE data corresponding to the target VoLTE user identifier is obtained.

[0157] Regarding the apparatus in the above embodiments, the specific manner in which each module performs its operation has been described in detail in the embodiments related to the method, and will not be elaborated upon here.

[0158] In some or related embodiments, a data sending unit is used to send first LTE VoLTE data to at least one node when performing an update operation on LTE VoLTE data, wherein the at least one node includes at least one terminal and / or at least one core network element; a request receiving unit is used to receive a data audit request sent by a first node among the at least one node, wherein the data audit request is generated by the first node determining that the first LTE VoLTE data is inconsistent with second LTE VoLTE data stored in the first node; a request sending unit is used to respond to the data audit request, send a first voting request corresponding to the first LTE VoLTE data to the at least one node, and determine the target LTE VoLTE data based on the voting results sent by the at least one node in response to the first voting request. Therefore, a data audit mechanism can be provided to determine the target data through a voting mechanism, eliminating the need for manual intervention, reducing the time spent on manual collaboration between departments, reducing manual audit costs, reducing inaccuracies in manual audits, and improving the accuracy and efficiency of data audits.

[0159] Figure 7 This is a block diagram of a network device 700 provided in an embodiment of this disclosure. For example, network device 700 can be provided as a network device. See also... Figure 7The network device 700 includes a processing component 722, which further includes at least one processor, and memory resources represented by memory 732 for storing instructions, such as application programs, that can be executed by the processing component 722. The application programs stored in memory 732 may include one or more modules, each corresponding to a set of instructions. Furthermore, the processing component 722 is configured to execute instructions to perform any of the methods described above applied to the network device.

[0160] Network device 700 may also include a power supply component 727 configured to perform power management of network device 700, a wired or wireless network interface 750 configured to connect network device 700 to a network, and an input / output (I / O) interface 758. Network device 700 can operate on an operating system stored in memory 732, such as Windows Server™, Mac OS X™, Unix™, Linux™, Free BSD™, or similar.

[0161] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0162] The program code used to implement the methods of this disclosure may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on a machine, partially on a machine, as a standalone software package partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0163] In the context of this disclosure, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0164] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device for displaying information to the user (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor); and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the computer. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0165] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or middleware components (e.g., application servers), or frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), the Internet, and blockchain networks.

[0166] Computer systems can include clients and servers. Clients and servers are generally geographically separated and typically interact via communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. A server can be a cloud server, also known as a cloud computing server or cloud host, a hosting product within the cloud computing service ecosystem, addressing the shortcomings of traditional physical hosts and VPS (Virtual Private Server, or simply "VPS") services, such as high management difficulty and weak business scalability. Servers can also be servers for distributed systems or servers incorporating blockchain technology.

[0167] It should be understood that the various forms of processes shown above can be used to rearrange, add, or delete steps. For example, the steps described in this disclosure can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution disclosed in this disclosure can be achieved, and this is not limited herein.

[0168] The specific embodiments described above do not constitute a limitation on the scope of protection of this disclosure. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this disclosure should be included within the scope of protection of this disclosure.

Claims

1. A data auditing method, characterized in that, include: When performing an update operation on LTE Voice Bearer (VOLTE) data, first LTE Voice Bearer (VOLTE) data is sent to at least one node, wherein the at least one node includes at least one terminal and / or at least one core network element. Receive a data audit request sent by the first node among the at least one nodes, wherein the data audit request is generated by the first node after determining that the first LTE Voice Bearer (VOLTE) data is inconsistent with the second LTE Voice Bearer (VOLTE) data stored in the first node; In response to the data audit request, a first voting request corresponding to the first LTE Voice Bearer (VOLTE) data is sent to the at least one node, and the target LTE Voice Bearer (VOLTE) data is determined based on the voting results sent by the at least one node in response to the first voting request.

2. The method according to claim 1, characterized in that, When performing an update operation on the VoLTE data, sending the first VoLTE data to at least one node includes: When performing an update operation on the LTE Voice Bearer (VOLTE) data, a first sequence number corresponding to the update operation is generated, and a first version number corresponding to the first LTE Voice Bearer (VOLTE) data is generated. Send the first serial number and the first version number to the at least one node.

3. The method according to claim 2, characterized in that, The step of determining the target LTE voice bearer VoLTE data based on the voting results sent by at least one node in response to the first voting request includes: If the first voting result sent by at least one node in response to the first voting request meets the result requirements, the first sequence number and the first version number are determined as target LTE Voice Bearer (VOLTE) data. Store the target LTE Voice Bearer (VOLTE) data; Send the target LTE Voice Bearer VoLTE data to the at least one node; or Send the target LTE Voice Bearer (VOLTE) data to a target node among the at least one nodes, wherein the target node is a node among the at least one nodes whose first voting result is not a preset result.

4. The method according to claim 2, characterized in that, The step of determining the target LTE voice bearer VoLTE data based on the voting results sent by at least one node in response to the first voting request includes: If the voting result sent by at least one node in response to the first voting request does not meet the result requirements, a second voting request is sent to at least one node, wherein the second voting request includes a second sequence number and a second version number, the second sequence number being the previous sequence number adjacent to the first sequence number, and the second version number being the previous version number adjacent to the first version number; If the second voting result sent by at least one node in response to the second voting request meets the result requirements, the second sequence number and the second version number are determined as target LTE Voice Bearer (VOLTE) data. Store the target LTE Voice Bearer (VOLTE) data; Send the target LTE Voice Bearer VoLTE data to the at least one node; or Send the target LTE Voice Bearer (VOLTE) data to a target node among the at least one nodes, wherein the target node is a node among the at least one nodes whose second voting result is not a preset result.

5. The method according to claim 1, characterized in that, The method further includes: Acquire and store the audit record of the first LTE voice bearer VoLTE data; Upon receiving a call instruction from the terminal for the audit record, the audit record is sent to the terminal.

6. The method according to claim 1, characterized in that, The method further includes: Based on preset selection criteria, obtain the target LTE Voice Bearer (VOLTE) user identifier; By acquiring data corresponding to any one of the at least one nodes, the VoLTE data corresponding to the target VoLTE user identifier is obtained.

7. A data auditing device, characterized in that, include: The data transmission unit is configured to transmit first LTE VoLTE data to at least one node when performing an update operation on LTE VoLTE data, wherein the at least one node includes at least one terminal and / or at least one core network element. The request receiving unit is configured to receive a data audit request sent by the first node among the at least one node, wherein the data audit request is generated by the first node after determining that the first LTE Voice Bearer (VOLTE) data is inconsistent with the second LTE Voice Bearer (VOLTE) data stored in the first node; The request sending unit is configured to, in response to the data audit request, send a first voting request corresponding to the first LTE Voice Bearer (VOLTE) data to the at least one node, and determine the target LTE Voice Bearer (VOLTE) data based on the voting results sent by the at least one node in response to the first voting request.

8. A network device, characterized in that, include: processor; Memory used to store the processor's executable instructions; The processor is configured to execute the instructions to implement the data auditing method as described in any one of claims 1 to 6.

9. A storage medium storing instructions, characterized in that, When the instruction is executed on the communication device, the communication device performs the data auditing method as described in any one of claims 1 to 6.

10. A computer program product, characterized in that, It includes a computer program that, when executed by a processor, implements the data auditing method according to any one of claims 1 to 9.

Images