CN114598559A - Data processing method and device, electronic equipment and computer readable storage medium - Google Patents
Data processing method and device, electronic equipment and computer readable storage medium Download PDFInfo
- Publication number
- CN114598559A CN114598559A CN202110832989.2A CN202110832989A CN114598559A CN 114598559 A CN114598559 A CN 114598559A CN 202110832989 A CN202110832989 A CN 202110832989A CN 114598559 A CN114598559 A CN 114598559A
- Authority
- CN
- China
- Prior art keywords
- communication data
- data
- version number
- communication
- processing
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 38
- 238000004891 communication Methods 0.000 claims abstract description 529
- 238000012545 processing Methods 0.000 claims abstract description 170
- 238000000034 method Methods 0.000 claims abstract description 83
- 238000004590 computer program Methods 0.000 claims description 8
- 230000008569 process Effects 0.000 abstract description 41
- 238000010586 diagram Methods 0.000 description 5
- 230000007246 mechanism Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 238000005034 decoration Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
- H04L12/1403—Architecture for metering, charging or billing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
- H04L12/141—Indication of costs
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
- H04L12/1432—Metric aspects
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
- H04L12/1432—Metric aspects
- H04L12/1435—Metric aspects volume-based
Abstract
The embodiment of the application provides a data processing method and device, electronic equipment and a computer readable storage medium, and relates to the field of data processing. According to the embodiment of the application, the first communication data and the version number thereof are locked only in the sub-process of updating the first communication data in the charging processing process, the first communication data are inquired in the charging processing of the communication ticket, and the client side does not need to be locked in the two sub-processes of charging operation according to the first communication data, so that the charging processing can be performed in parallel on other communication tickets of the inquired object, namely, the first communication data can be inquired in parallel and the charging operation and the like can be performed when the first communication ticket is charged. The data processing method provided by the embodiment of the application realizes the parallel processing of the ticket charging and improves the processing efficiency of the ticket charging.
Description
Technical Field
The present application relates to the field of data processing technologies, and in particular, to a data processing method and apparatus, an electronic device, and a computer-readable storage medium.
Background
In the field of communication services, the same user may generate call bills of multiple service types at the same time point, such as corresponding call bills generated when the user browses videos, web pages and the like, and therefore, the charging system needs to charge the call bills in real time. In addition, in a large enterprise, a group service, a traffic pool shared by multiple persons, and other services, multiple telephone bills may be generated at the same time, and the charging system needs to charge the telephone bills generated at the same time in real time.
In the related art, when the charging system performs charging processing on the ticket, the charging system usually performs a processing mode based on long transactions, that is, the service data is locked in the whole processing process. The long transaction mechanism causes that all the telephone bills under the account can only be processed in sequence, and the conditions of overstocked service telephone bills, overtime on-line message processing and incapability of processing the telephone bills in time exist. With the increase of charging service types and the development of group and group services, the requirement on the real-time performance of online charging is improved, so the scheme can not meet the service requirements more and more.
Disclosure of Invention
The object of the present application is to solve at least one of the above-mentioned technical drawbacks, in particular the inefficient data processing.
According to an aspect of the present application, there is provided a data processing method including:
receiving a first data request, and determining a query object in the first data request;
acquiring first communication data of the query object and a first version number of the first communication data; wherein the first communication data comprises historical communication data within a target billing period;
receiving a second data request, acquiring a second version number of the first communication data, and locking the first communication data and/or the second version number;
and processing the first communication data according to the first version number and the second version number, and unlocking the first communication data and/or the second version number.
Optionally, the processing the first communication data according to the first version number and the second version number includes:
acquiring first target communication data in the second data request; the first target communication data is determined by performing first data processing according to the second communication data and the first communication data;
if the first version number is the same as the second version number, performing update processing on the first communication data, wherein the update processing includes updating the first communication data into the first target communication data;
and if the first version number is different from the second version number, performing second data processing on the first communication data according to whether a rate jump point exists between the first communication data and second target communication data.
Optionally, the performing, according to whether a rate jump point exists between the first communication data and the second target communication data, second data processing on the first communication data includes:
if the rate trip point does not exist, performing the updating processing on the first communication data, wherein the updating processing comprises updating the first communication data into the second target communication data;
if the rate jump point exists, sending indication information to a client; wherein the indication information indicates the client to resend the first data request and update the first target communication data.
Optionally, after receiving the first data request, the method further includes:
and locking the first communication data and the first version number of the first communication data.
Optionally, after querying the first communication data and the first version number of the first communication data, the method further comprises:
and unlocking the first communication data and the first version number of the first communication data.
According to another aspect of the present application, there is provided a data processing method including:
sending a first data request to a server, wherein the first data request comprises a query object identifier;
receiving first communication data of the query object and a first version number of the first communication data fed back by a server; wherein the first communication data comprises historical communication data within a target billing period;
performing operation processing according to the second communication data and the first communication data to determine first target communication data;
and sending a second data request to a server, wherein the second data request comprises the first target communication data and the first version number of the first communication data.
Optionally, the method further comprises: receiving the updated first communication data sent by the server, and generating a charging reminding message according to the updated first communication data.
According to another aspect of the present application, there is provided a data processing apparatus comprising:
the first receiving module is used for receiving a first data request and determining a query object in the first data request;
the acquisition module is used for acquiring first communication data of the query object and a first version number of the first communication data; wherein the first communication data comprises historical communication data within a target billing period;
a second receiving module, configured to receive a second data request, obtain a second version number of the first communication data, and lock the first communication data and/or the second version number;
and the data processing module is used for processing the first communication data according to the first version number and the second version number and unlocking the first communication data and/or the second version number.
According to another aspect of the present application, there is provided a data processing apparatus comprising:
the first sending module is used for sending a first data request to a server, wherein the first data request comprises a query object identifier;
the receiving module is used for receiving the first communication data of the query object and the first version number of the first communication data fed back by the server; wherein the first communication data comprises historical communication data within a target billing period;
the operation module is used for performing operation processing according to the second communication data and the first communication data to determine first target communication data;
and the second sending module is used for sending a second data request to a server, wherein the second data request comprises the first target communication data and the first version number of the first communication data.
According to another aspect of the present application, there is provided an electronic device including:
one or more processors;
a memory;
one or more applications, wherein the one or more applications are stored in the memory and configured to be executed by the one or more processors, the one or more programs configured to: performing a data processing method as claimed in any one of the above.
For example, a fifth aspect of the present application provides a computing device comprising: the processor, the memory and the communication interface complete mutual communication through the communication bus;
the memory is used for storing at least one executable instruction, and the executable instruction enables the processor to execute the corresponding operation of the data processing method as shown in the first or second aspect of the application.
According to yet another aspect of the application, a computer-readable storage medium is provided, the computer program, when executed by a processor, implementing a data processing method as defined in any one of the above.
For example, in a fourth aspect of the embodiments of the present application, a computer-readable storage medium is provided, on which a computer program is stored, and the computer program, when executed by a processor, implements the data processing method shown in the first aspect of the present application.
According to an aspect of the application, a computer program product or computer program is provided, comprising computer instructions, the computer instructions being stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions to cause the computer device to perform the methods provided in the various alternative implementations of the first aspect or the second aspect described above. .
The beneficial effect that technical scheme that this application provided brought is:
according to the embodiment of the application, the first communication data and the version number thereof are locked only in the sub-process of updating the first communication data in the charging processing process, the first communication data are inquired in the charging processing of the communication ticket, and the client side does not need to be locked in the two sub-processes of charging operation according to the first communication data, so that the charging processing can be performed in parallel on other communication tickets of the inquired object, namely, the first communication data can be inquired in parallel and the charging operation and the like can be performed when the first communication ticket is charged. The data processing method provided by the embodiment of the application realizes the parallel processing of the ticket charging and improves the processing efficiency of the ticket charging.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings used in the description of the embodiments of the present application will be briefly described below.
Fig. 1 is a schematic flowchart of a data processing method according to an embodiment of the present disclosure;
fig. 2 is a schematic scene diagram of a first example provided in an embodiment of the present application;
fig. 3 is a schematic view of a second example scenario provided in an embodiment of the present application;
fig. 4 is a schematic scene diagram of a third example provided in the embodiment of the present application;
fig. 5 is a second flowchart illustrating a data processing method according to an embodiment of the present application;
fig. 6 is a third schematic flowchart of a data processing method according to an embodiment of the present application;
fig. 7 is a fourth schematic flowchart of a data processing method according to an embodiment of the present application;
fig. 8 is a schematic structural diagram of a data apparatus according to an embodiment of the present application;
fig. 9 is a second schematic structural diagram of a data apparatus according to an embodiment of the present application;
fig. 10 is a schematic structural diagram of an electronic device for data processing according to an embodiment of the present application.
Detailed Description
Reference will now be made in detail to embodiments of the present application, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to the same or similar elements or elements having the same or similar function throughout. The embodiments described below with reference to the drawings are exemplary only for the purpose of explaining the present application and are not to be construed as limiting the present application.
As used herein, the singular forms "a", "an", "the" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. It will be understood that when an element is referred to as being "connected" or "coupled" to another element, it can be directly connected or coupled to the other element or intervening elements may also be present. Further, "connected" or "coupled" as used herein may include wirelessly connected or wirelessly coupled. As used herein, the term "and/or" includes all or any element and all combinations of one or more of the associated listed items.
To make the objects, technical solutions and advantages of the present application more clear, embodiments of the present application will be described in further detail below with reference to the accompanying drawings.
The following describes the technical solutions of the present application and how to solve the above technical problems with specific embodiments. The following several specific embodiments may be combined with each other, and details of the same or similar concepts or processes may not be repeated in some embodiments. Embodiments of the present application will be described below with reference to the accompanying drawings.
An execution subject of the method may be any electronic device, for example, the method may be applied to a server or a terminal device with data processing capability, and optionally, the method may be executed by the server, as shown in fig. 1, which is a flowchart of the data processing method provided in the embodiment of the present application, and the method may include:
step S101: receiving a first data request, and determining a query object in the first data request.
Specifically, the data processing method of the embodiment of the application can be applied to a scenario of communication ticket charging processing of a communication service, and in the scenario, a user usually generates various types of communication tickets when performing the communication service. For example, when a user makes a call, a call ticket consuming the call duration or consuming the data traffic is generated; for another example, when a user browses a video or a web page, a call ticket consuming data traffic may be generated, and therefore, for a communication call ticket of the user, in a process of charging communication data such as a call duration of the communication call ticket and communication data traffic, a server may perform communication data processing in the charging processing process through the data processing method according to the embodiment of the present application.
In the following, taking the first communication ticket as an example, the whole process of the charging processing of the first communication ticket is introduced, and the charging processing process of the first communication ticket may include the following three sub-processes:
sub-process 1: historical communication data (the historical communication data is the first communication data in the embodiment of the present application) is queried. The process may be executed by the server, that is, after responding to a request for querying the historical communication data sent by the client, that is, after receiving a first data request in the embodiment of the present application, the server may obtain the historical communication data of a query object, that is, the first communication data related to the embodiment of the present application, according to a charging object related to the first communication ticket in the first data request, that is, the query object related to the embodiment of the present application.
And a sub-process 2: and (6) calculating the charging. The process can be executed by a client, the client can receive historical communication data fed back by a server, and then charging operation is carried out according to the historical communication data and the communication consumption data of the first communication ticket, so that target communication data obtained by adding the communication consumption data of the first communication ticket into the historical communication data is obtained.
And a sub-process 3: and updating historical communication data. The process can be executed by the server, and after the client executes the charging operation, the historical communication data is updated, namely, the target communication data obtained by adding the communication consumption data of the first communication ticket into the historical communication data is used as new historical communication data.
Specifically, in step S101, the server first receives a first data request, where the first data request is a request for querying data, which is sent to the server by the client according to a generated first communication ticket when the client generates the first communication ticket. The first data request may include an inquiry object identifier, where the inquiry object is a charging object related to a communication ticket of a user, for example, the charging object may be a user account of the user, and the user account may include an SIM card account of the user, an APP account used by the user, and the like. In addition, the charging object may also be an associated communication account of the user, for example, the associated communication account of the user may be a primary card account, a secondary card account, an enterprise account to which the user belongs, a group account, and the like associated with the user.
Step S102: acquiring first communication data of the query object and a first version number of the first communication data; wherein the first communication data comprises historical communication data within a target billing period.
Specifically, first communication data of the query object and a first version number of the first communication data may be obtained according to an identifier of the query object, where the first communication data includes historical communication data in a target charging period.
The target charging period may be determined according to the usage duration of the service package corresponding to the query object, for example, when the usage duration of the service package (call duration or data traffic, etc.) corresponding to the query object is 1 month, the target charging period may be 1 month. Further, the first communication data may include a plurality of pieces of historical communication data within the target charging period; or historical accumulated communication data within the target billing period, i.e., the sum of all communication data within the target billing period.
The version number of the first communication data may be used to characterize a record of updating or processing the first communication data, that is, after the first communication data is updated or processed each time, the corresponding version number is updated accordingly, optionally, for example, each time the first communication data is updated, the corresponding version number may be increased by 1 accordingly to update to a new version number. Therefore, it can be understood that whether the first communication data is updated or processed can be determined by the version number of the first communication data. In this embodiment of the application, the first version number of the first communication data may include a version number corresponding to the first communication data when the query object is queried after the first data request is received.
Step S103: and receiving a second data request, acquiring a second version number of the first communication data, and locking the first communication data and/or the second version number.
Specifically, in the scenario of the communication data charging process of the communication service, the second data request is after the first data request, and there is a time interval between the second data request and the first data request. The second data request may be sent after the client performs charging operation on the first communication data of the first communication ticket, and is used to request the server to update the first communication data.
Since there is a time interval between the first data request and the second data request, there may be a problem that since the parallel charging process is performed for other tickets of the same query object, so that there occurs a case where the first communication data is processed or updated, and the version number corresponding to the first communication data is changed, and therefore, when a second data request is received, a second version number of the first communication data at the moment is obtained, and locking processing is carried out on the first communication data and/or the second version number, so that aiming at the charging processing of the current call ticket, after the first communication data and/or the second version number are/is locked, the first communication data and/or the second version number can be prevented from being processed or updated when other call tickets of the same query object are subjected to parallel charging processing.
Step S104: and processing the first communication data according to the first version number and the second version number, and unlocking the first communication data and/or the second version number.
Specifically, in a scenario of communication data charging processing of a communication service, if the first communication data of the query object is locked in the whole charging processing process, for example, the first communication data and/or the first version number is locked in step S102 of querying the first communication data, and is not unlocked until the first communication data is processed in step S104 (it is determined whether the first communication data is updated), in the charging processing process of the first communication ticket, other tickets of the query object cannot be subjected to parallel charging processing.
And the present application performs locking processing on the first communication data and/or the second version number only when receiving a second data request, and determines whether to perform update processing on the first communication data according to whether the first version number and the second version number are the same, that is, according to whether the first version number and the second version number are the same. Therefore, in the embodiment of the application, the first communication data and/or the second version number are/is locked only in the sub-process of updating the first communication data in the charging process, and the first communication data is inquired in the charging process of the first communication ticket, and the client performs the charging operation according to the first communication data without locking, so that the charging process can be performed in parallel on other communication tickets of the inquired object, that is, the first communication data can be inquired in parallel and the charging operation can be performed when the first communication ticket performs the charging process. The data processing method provided by the embodiment of the application realizes the parallel processing of the ticket charging and improves the processing efficiency of the ticket charging.
In an optional embodiment, said processing said first communication data according to said first version number and said second version number comprises:
acquiring first target communication data in the second data request; the first target communication data is determined by performing first data processing according to the second communication data and the first communication data;
if the first version number is the same as the second version number, performing update processing on the first communication data, wherein the update processing includes updating the first communication data into the first target communication data;
and if the first version number is different from the second version number, performing second data processing on the first communication data according to whether a rate jump point exists between the first communication data and second target communication data.
Specifically, the second communication data may include communication consumption data of the first communication ticket, for example, the communication consumption data may be data of voice call duration, communication data traffic, and the like, which are related to the first communication ticket, and in a specific scenario, if the first communication ticket is generated by making a call, the communication consumption data may be communication duration data; if the first communication ticket is generated by browsing videos, the communication consumption data can be data traffic consumed by browsing the videos.
The first data processing may include performing charging operation processing on the second communication data and the first communication data, for example, calculating an accumulated call duration or an accumulated data traffic according to the second communication data and the first communication data.
Further, if the first version number is the same as the second version number, it indicates that the first communication data and the first version number of the first communication data are queried for the first communication ticket until the second version number of the first communication data is obtained, and between the two processing procedures, the first communication data is not changed (for example, the first communication data is processed and updated) due to the charging processing of other tickets of the query object, in other words, in the process of charging the first communication ticket, no other communication ticket of the same query object exists, and the charging processing is performed in parallel with the first communication ticket, that is, the charging processing procedure for the first communication ticket does not conflict with other communication tickets, so that when the first version number is the same as the second version number, the first communication data can be updated, that is, the first communication data is updated to the first target communication data, and when the first communication data is updated, a version number corresponding to the first communication data may be updated accordingly, for example, the version number may be increased by 1.
The data processing method in the embodiment of the application is based on an optimistic lock mechanism, that is, it is assumed that the probability of occurrence of concurrent operations of communication ticket charging processing for the same query object is extremely low, and therefore, when the communication ticket charging processing is performed, the probability of processing communication data (for example, first communication data in the embodiment of the application) of the query object is very low, and therefore, the cost for checking whether the first version number is the same as the second version number is far less than the cost for locking the first communication data when all the communication tickets are charged, and therefore, the processing mechanism based on the optimistic lock in the embodiment of the application improves the efficiency of the communication ticket charging processing.
On the other hand, if the first version number is different from the second version number, it is indicated that the first communication data and the first version number of the first communication data are inquired for the first communication ticket until the second version number of the first communication data is obtained, and between the two processing procedures, the charging processing of the other ticket with the inquiry object changes the first communication data (the inquiry object is the inquiry object corresponding to the first communication ticket), in other words, in the charging processing of the first communication ticket, the other communication tickets with the same inquiry object exist, and the charging processing is performed in parallel with the first communication ticket only. In this case, second data processing is performed on the first communication data according to whether or not there is a rate jump point between the first communication data and the second target communication data. The rate jump point is a corresponding communication data value when the communication rate is non-uniformly changed. The second target communication data is determined according to the first communication data and the second communication data corresponding to the second version number.
In an optional embodiment, the performing, according to whether a rate jump point exists between the first communication data and the second target communication data, the second data processing on the first communication data includes:
if the rate trip point does not exist, performing the updating processing on the first communication data, wherein the updating processing comprises updating the first communication data into the second target communication data;
if the rate jump point exists, sending indication information to a client; wherein the indication information indicates the client to resend the first data request and update the first target communication data.
In the embodiment of the present application, if the first version number is different from the second version number, it indicates that there is a charging processing procedure for other communication tickets of the same query object, and the charging processing procedure and the first communication ticket perform parallel charging processing. In this case, whether parallel processing of the charging processing procedures of other communication tickets of the same query object conflicts with the charging processing procedure of the first communication ticket, that is, whether the charging processing of the first communication ticket is wrong or not, may be determined by judging whether a rate jump point exists between the first communication data and the second target communication data.
In case one, if the rate jump point does not exist between the first communication data and the second target communication data, it indicates that the charging processing of other communication tickets of the same query object is processed in parallel, and the charging processing of the first communication ticket is not wrong, and the first communication data may be updated.
Specifically, it should be noted that, since the first version number is different from the second version number, the first communication data is the first communication data corresponding to the second version number. And at this time, because the rate jump point does not exist between the first communication data and the second target communication data, the consumption data respectively corresponding to the first ticket and the other parallel-processed tickets are all contained in the same rate interval, and therefore, the processing sequence of the first ticket and the other parallel-processed tickets does not influence the final charging result.
Specifically, it can be explained by an example that, for example, the ticket a consumes 2M data traffic, the ticket b consumes 3M data traffic, and the rates of the data traffic consumed by the tickets a and b are both 0.29 yuan/M, so that when the tickets a and b are subjected to parallel charging processing, the sequence of charging the tickets a and b has no influence on the charging results of the two tickets.
And if the rate jump point exists, the parallel processing of the charging processing processes of other communication bills of the same query object is shown, which can cause the charging processing of the first communication bill to be wrong, the charging processing of the first bill needs to be carried out again, namely, indication information is sent to a client, and the indication information indicates the client to resend the first data request and update the first target communication data.
Whether a rate jump point exists between the first communication data and the second target communication data is explained through a call ticket parallel processing scene in an actual scene as follows:
scene one: and when the communication data consumed by the call ticket crosses the maximum communication data volume contained in the fixed package, determining whether a rate jump point exists between the first communication data and the second target communication data, wherein the rate jump point is the maximum communication data volume contained in the package.
In an actual communication scenario, a package ordered by a user usually includes a certain amount of fixed package communication data, for example, a fixed package includes a call duration of 100 minutes and a data flow of 1000M, and in a process of charging a communication ticket, communication data in the fixed package is often consumed first, so that a maximum value of communication data included in the package is a rate jump point for the communication data in the fixed package. In the above example, the 100 th minute of the call duration and the 1000 th M of the data traffic are the rate jump points, that is, the call duration is greater than 100 minutes, the data traffic exceeds 1000M, and the communication rate is changed. (the above example is only illustrative, and therefore, for convenience of explanation, in the embodiment of the present application, the call duration is explained in units of 1 minute, and the data traffic is explained in units of 1M.)
As a first example, referring to fig. 2, an inquiry object X corresponds to 1000M fixed package data traffic, and for the inquiry object X, it is assumed that a ticket 1 and a ticket 2 are generated, where the ticket 1 consumes 10M data traffic and the ticket 2 consumes 20M data traffic. And the call ticket 1 and the call ticket 2 are subjected to parallel charging processing, and for the call ticket 2, when the server inquires the first communication data, the first communication data of the first version number is found to be 980M. When the call ticket 2 is subjected to charging processing, the call ticket 1 is also subjected to charging processing, and the first communication data is updated, so that for the call ticket 2, when the server acquires the second version number of the first communication data, the acquired second version number is inconsistent with the first version number, and therefore, whether a rate jump point exists between the first communication data and the second target communication data is determined under the condition.
When the ticket 1 is charged, since the ticket 1 consumes 10M data traffic, after the ticket 1 is charged, the first communication data corresponding to the second version number is 980M +10M 990M, so that after the ticket 1 is charged, on the basis of the first communication data corresponding to the second version number, the determined second target communication data is 990M +20M 1010M for the ticket 2. In this case, a rate trip point 1000M exists between the first communication data 990M corresponding to the second version number and the second target communication data 1010M, so after 1000M, the consumed communication data will be consumed data outside the fixed package, which results in a change of the charge, and therefore, in this case, the parallel charging processing of the ticket 1 will affect the correctness of the charging processing of the ticket 2, and therefore, the charging processing of the ticket 2 needs to be re-executed, that is, the indication information is sent to the client; the indication information indicates the client to resend the first data request and update the first target communication data.
Scene two: the communication data consumed by the call ticket is the communication data outside the fixed package.
As a second example, in conjunction with fig. 3, it is assumed that outside the fixed package, the tariff situation for the consumed traffic data is the charging mode shown in the figure, i.e. within 600M, 10 dollars are charged per 100M, 600M to 1G are calculated as 60 dollars. In the charging mode, it is assumed that a call ticket 3 is generated, the flow data consumed by the call ticket 3 is 170M, and the first communication data inquired by the server when receiving the first data request is 240M for the call ticket 3, if the first version number and the second version number acquired in the charging process of the call ticket 3 are different, that is, other call tickets 4 and the call ticket 3 perform parallel charging processing together, it is necessary to determine whether the parallel-processed call ticket 4 affects the charging processing of the call ticket 3, that is, whether the parallel-processed call ticket 4 causes a charging error of the call ticket 3.
Specifically, the second target communication data may be determined according to the first communication data corresponding to the second version number queried for the ticket 3 and the second communication data consumed by the ticket 3, that is, the second target communication data after the second communication data consumed by the ticket 3 is accumulated is determined on the basis of the first communication data after the parallel processing of the ticket 4 is completed, and if a rate jump point exists between the first communication data and the second target communication data, the first communication data is updated.
Taking the data flow consumed by the parallel processed call ticket 4 as an example of 60M, the call ticket 4 consumes 60M on the basis of 240M original first communication data, so after the call ticket 4 completes the charging processing, the updated first communication data is 300M, the first communication data (300M) at this time is the first communication data corresponding to the second version number acquired by the server for the call ticket 3, and according to the first communication data 300M corresponding to the second version number and the 170M consumed by the call ticket 3, the second target communication data, namely 300M +170M 470M, can be obtained, between the first communication data 300M corresponding to the second version number and the second target communication data 470M, there is no rate jump point, namely 500M (the next charging point affecting the charge of the call ticket 3 in the charging process of the call ticket 3), so that the first communication data can be updated, i.e. the first communication data is updated to 470M.
As a third example, in connection with fig. 4, it is assumed that outside the fixed package, the tariff case for the consumed data traffic is the charging mode shown in the figure, i.e., 0.29 dollars per M, 10 dollars per 100 meters, 600 meters to 1 gram is calculated as 60 dollars. In the charging mode, it is assumed that a call ticket 5 is generated, the data traffic consumed by the call ticket 5 is 10M, and for the call ticket 5, the first communication data queried when the server receives the first data request is 240M, if the first version number obtained in the charging process of the call ticket 5 is different from the second version number, that is, the call ticket 6 and the call ticket 5 perform parallel charging processing, since the charging interval of the call ticket 5 is 240M-250M, in the charging mode of this example, the next trip point of the call ticket 5 is 300M, therefore, when the data traffic consumed by the call ticket 6 that is processed in parallel is less than 50M (i.e., 300M-250M), the total accumulated data traffic does not cross over the trip point of the rate after the data traffic consumed by the call ticket 6 is accumulated in the parallel processing with the call ticket 5, therefore, the parallel charging processing of the call ticket 6 does not influence the charging processing of the call ticket 5.
In an optional embodiment, after receiving the first data request, the method further comprises:
and locking the first communication data and the first version number of the first communication data.
In an optional embodiment, after querying the first communication data and the first version number of the first communication data, the method further comprises:
and unlocking the first communication data and the first version number of the first communication data.
With reference to fig. 5, in a first sub-process of the ticket charging process, that is, in the process of querying the first communication data, the locking may also be performed for the sub-process, after receiving the first data request, the locking is performed on the first communication data and the first version number of the first communication data, and after querying the first communication data and the first version number of the first communication data, the unlocking is performed on the first communication data and the first version number of the first communication data.
Therefore, in the embodiment of the application, when the dialog list a finishes querying the first communication data, other call tickets, such as the call ticket B, can continue querying the first communication data and perform charging processing, thereby realizing parallel charging processing.
In addition, in other embodiments of the present application, in a first sub-process of the bill charging process, that is, in a process of querying the first communication data, the first communication data in the process is not locked, and only for an update process of the first communication data, when a second data request is received, the first communication and a second version number of the first communication data are respectively locked, as shown in fig. 6, the second version number may be first locked, and if the first version number is the same as the second version number or the rate jump point does not exist between the first communication data and the second target communication data after verification, and the first communication data needs to be updated, the first communication data is locked until the first communication data is unlocked after the update process of the first communication data is completed.
According to the embodiment of the application, the first communication data and/or the second version number are/is locked only in the sub-process of updating the first communication data in the charging processing process, the first communication data are inquired in the charging processing of the first communication ticket, and the client side does not need to be locked in the two processes of charging operation according to the first communication data, so that the charging processing can be performed in parallel on other communication tickets of the inquired object, namely, the first communication data can be inquired in parallel and the charging operation and the like can be performed when the first communication ticket is charged. The data processing method provided by the embodiment of the application realizes the parallel processing of the ticket charging and improves the processing efficiency of the ticket charging.
An embodiment of the present application provides a data processing method, where an execution subject of the method may be a client, as shown in fig. 7, which is a flowchart of the data processing method provided in the embodiment of the present application, and the method may include:
step S701: and sending a first data request to a server, wherein the first data request comprises a query object identifier.
The first data request is a data query request sent to the server aiming at the generated first communication ticket when the first communication ticket is generated. The first data request may include an inquiry object identifier, where the inquiry object is a charging object related to a communication ticket of a user, for example, the charging object may be a user account of the user, and the user account may include an SIM card account of the user, an APP account used by the user, and the like. In addition, the charging object may also be an associated communication account of the user, for example, the associated communication account of the user may be a primary card account, a secondary card account, an enterprise account to which the user belongs, a group account, and the like associated with the user.
Step S702: receiving first communication data of the query object and a first version number of the first communication data fed back by a server; wherein the first communication data comprises historical communication data within a target billing period.
The target charging period may be determined according to the usage duration of the service package corresponding to the query object, for example, when the usage duration of the service package (call duration or data traffic, etc.) corresponding to the query object is 1 month, the target charging period may be 1 month. Further, the first communication data may include a plurality of pieces of historical communication data within the target charging period; or historical accumulated communication data within the target billing period, i.e., the sum of all communication data within the target billing period.
The version number of the first communication data may be used to characterize a record of updating or processing the first communication data, that is, after the first communication data is updated or processed each time, the corresponding version number is updated accordingly, optionally, for example, each time the first communication data is updated, the corresponding version number may be increased by 1 accordingly to update to a new version number. Therefore, it can be understood that whether the first communication data is updated or processed can be determined by the version number of the first communication data. In this embodiment of the application, the first version number of the first communication data may include a version number corresponding to the first communication data when the server receives the first data request and queries the query object.
Step S703: and performing operation processing according to the second communication data and the first communication data to determine first target communication data.
Specifically, the second communication data may include communication consumption data of the first communication ticket, for example, the communication consumption data may be data of voice call duration, communication data traffic, and the like, which are related to the first communication ticket, and in a specific scenario, if the first communication ticket is generated by making a call, the communication consumption data may be communication duration data; if the first communication ticket is generated by browsing videos, the communication consumption data can be data traffic consumed by browsing the videos.
The arithmetic processing may include performing a summation operation based on the second communication data and the first communication data to determine first target communication data.
Step S704: and sending a second data request to a server, wherein the second data request comprises the target communication data and the first version number of the first communication data.
Specifically, in the scenario of the communication data charging process of the communication service, the second data request is after the first data request, and there is a time interval between the second data request and the first data request. The second data request may be sent after the client performs charging operation on the first communication data of the first communication ticket, and is used to request the server to update the first communication data.
In an optional embodiment, the first communication data after update processing sent by the server is received, and the charging reminder message is generated according to the first communication data after update processing.
Specifically, after the charging processing of the first communication ticket is completed, a charging reminding message is generated according to the updated first communication data, so as to feed back the communication consumption condition to the user.
According to the embodiment of the application, the first communication data and/or the second version number are/is locked only in the sub-process of updating the first communication data in the charging processing process, the first communication data are inquired in the charging processing of the first communication ticket, and the client side does not need to be locked in the two processes of charging operation according to the first communication data, so that the charging processing can be performed in parallel on other communication tickets of the inquired object, namely, the first communication data can be inquired in parallel and the charging operation and the like can be performed when the first communication ticket is charged. The data processing method provided by the embodiment of the application realizes the parallel processing of the ticket charging and improves the processing efficiency of the ticket charging.
An embodiment of the present application provides a data processing apparatus, and as shown in fig. 8, the apparatus 80 may include:
a first receiving module 801, configured to receive a first data request, and determine a query object in the first data request;
an obtaining module 802, configured to obtain first communication data of the query object and a first version number of the first communication data; wherein the first communication data comprises historical communication data within a target billing period;
a second receiving module 803, configured to receive a second data request, obtain a second version number of the first communication data, and lock the first communication data and/or the second version number;
a data processing module 804, configured to process the first communication data according to the first version number and the second version number, and unlock the first communication data and/or the second version number.
In an optional embodiment, the data processing module is specifically configured to:
acquiring first target communication data in the second data request; the first target communication data is determined by performing first data processing according to the second communication data and the first communication data;
if the first version number is the same as the second version number, performing update processing on the first communication data, wherein the update processing includes updating the first communication data into the first target communication data;
and if the first version number is different from the second version number, performing second data processing on the first communication data according to whether a rate jump point exists between the first communication data and second target communication data.
In an optional embodiment, the data processing module is specifically configured to:
if the rate trip point does not exist, performing the updating processing on the first communication data, wherein the updating processing comprises updating the first communication data into the second target communication data;
if the rate jump point exists, sending indication information to a client; wherein the indication information indicates the client to resend the first data request and update the first target communication data.
In an optional embodiment, the apparatus may further comprise: and the locking module is used for locking the first communication data and the first version number of the first communication data after the first data request is received.
In an optional embodiment, the apparatus may further comprise: and the unlocking module is used for unlocking the first communication data and the first version number of the first communication data after inquiring the first communication data and the first version number of the first communication data.
An embodiment of the present application provides a data processing apparatus, and as shown in fig. 9, the apparatus 90 may include:
a first sending module 901, configured to send a first data request to a server, where the first data request includes a query object identifier;
a receiving module 902, configured to receive first communication data of the query object and a first version number of the first communication data fed back by a server; wherein the first communication data comprises historical communication data within a target billing period;
an operation module 903, configured to perform operation processing according to the second communication data and the first communication data, and determine first target communication data;
a second sending module 904, configured to send a second data request to a server, where the second data request includes the first target communication data and the first version number of the first communication data.
In an optional embodiment, the apparatus may further comprise: and the reminding module is used for receiving the updated first communication data sent by the server and generating a charging reminding message according to the updated first communication data.
The data processing apparatus of this embodiment can execute the data processing method shown in the above embodiments of this application, and the implementation principles thereof are similar, and are not described herein again.
According to the embodiment of the application, the first communication data and the version number thereof are locked only in the sub-process of updating the first communication data in the charging processing process, the first communication data are inquired in the charging processing of the communication ticket, and the client side does not need to be locked in the two sub-processes of charging operation according to the first communication data, so that the charging processing can be performed in parallel on other communication tickets of the inquired object, namely, the first communication data can be inquired in parallel and the charging operation and the like can be performed when the first communication ticket is charged. The data processing method provided by the embodiment of the application realizes the parallel processing of the ticket charging and improves the processing efficiency of the ticket charging.
An embodiment of the present application provides an electronic device, which includes: a memory and a processor; at least one program stored in the memory for execution by the processor, which when executed by the processor, implements: according to the embodiment of the application, the first communication data and the version number thereof are locked only in the sub-process of updating the first communication data in the charging processing process, the first communication data are inquired in the charging processing of the communication ticket, and the client side does not need to be locked in the two sub-processes of charging operation according to the first communication data, so that the charging processing can be performed in parallel on other communication tickets of the inquired object, namely, the first communication data can be inquired in parallel and the charging operation and the like can be performed when the first communication ticket is charged. The data processing method provided by the embodiment of the application realizes the parallel processing of the ticket charging and improves the processing efficiency of the ticket charging.
In an alternative embodiment, an electronic device is provided, as shown in fig. 10, the electronic device 4000 shown in fig. 10 comprising: a processor 4001 and a memory 4003. Processor 4001 is coupled to memory 4003, such as via bus 4002. Optionally, the electronic device 4000 may further include a transceiver 4004, and the transceiver 4004 may be used for data interaction between the electronic device and other electronic devices, such as transmission of data and/or reception of data. In addition, the transceiver 4004 is not limited to one in practical applications, and the structure of the electronic device 4000 is not limited to the embodiment of the present application.
The Processor 4001 may be a CPU (Central Processing Unit), a general-purpose Processor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array) or other Programmable logic device, a transistor logic device, a hardware component, or any combination thereof. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. The processor 4001 may also be a combination that performs a computational function, including, for example, a combination of one or more microprocessors, a combination of a DSP and a microprocessor, or the like.
The Memory 4003 may be a ROM (Read Only Memory) or other types of static storage devices that can store static information and instructions, a RAM (Random Access Memory) or other types of dynamic storage devices that can store information and instructions, an EEPROM (Electrically Erasable Programmable Read Only Memory), a CD-ROM (Compact Disc Read Only Memory) or other optical Disc storage, optical Disc storage (including Compact Disc, laser Disc, optical Disc, digital versatile Disc, blu-ray Disc, etc.), a magnetic Disc storage medium or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to these.
The memory 4003 is used for storing application program codes (computer programs) for executing the present scheme, and is controlled by the processor 4001 to execute. Processor 4001 is configured to execute application code stored in memory 4003 to implement what is shown in the foregoing method embodiments.
Among them, electronic devices include but are not limited to: mobile phones, notebook computers, multimedia players, desktop computers, and the like.
The present application provides a computer-readable storage medium, on which a computer program is stored, which, when running on a computer, enables the computer to execute the corresponding content in the foregoing method embodiments.
According to the embodiment of the application, the first communication data and the version number thereof are locked only in the subprocess of updating the first communication data in the charging processing process, and locking is not needed in two subprocesses of inquiring the first communication data in the charging processing of the communication ticket and carrying out charging operation by the client according to the first communication data, so that the charging processing can be carried out in parallel on other communication tickets of the inquired object, namely, the first communication data can be inquired in parallel and the charging operation and the like can be carried out when the first communication ticket is subjected to the charging processing. The data processing method provided by the embodiment of the application realizes the parallel processing of the ticket charging and improves the processing efficiency of the ticket charging.
It should be understood that, although the steps in the flowcharts of the figures are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and may be performed in other orders unless explicitly stated herein. Moreover, at least a portion of the steps in the flow chart of the figure may include multiple sub-steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, which are not necessarily performed in sequence, but may be performed alternately or alternately with other steps or at least a portion of the sub-steps or stages of other steps.
The foregoing is only a partial embodiment of the present invention, and it should be noted that, for those skilled in the art, various modifications and decorations can be made without departing from the principle of the present invention, and these modifications and decorations should also be regarded as the protection scope of the present invention.
Claims (11)
1. A data processing method is applied to a server side, and is characterized in that the method comprises the following steps:
receiving a first data request, and determining a query object in the first data request;
acquiring first communication data of the query object and a first version number of the first communication data; wherein the first communication data comprises historical communication data within a target billing period;
receiving a second data request, acquiring a second version number of the first communication data, and locking the first communication data and/or the second version number;
and processing the first communication data according to the first version number and the second version number, and unlocking the first communication data and/or the second version number.
2. The data processing method of claim 1, wherein the processing the first communication data according to the first version number and the second version number comprises:
acquiring first target communication data in the second data request; the first target communication data is determined by performing first data processing according to the second communication data and the first communication data;
if the first version number is the same as the second version number, performing update processing on the first communication data, wherein the update processing includes updating the first communication data into the first target communication data;
and if the first version number is different from the second version number, performing second data processing on the first communication data according to whether a rate jump point exists between the first communication data and second target communication data.
3. The data processing method according to claim 2, wherein the second data processing on the first communication data according to whether or not there is a rate jump point between the first communication data and the second target communication data includes:
if the rate trip point does not exist, performing the updating processing on the first communication data, wherein the updating processing comprises updating the first communication data into the second target communication data;
if the rate jump point exists, sending indication information to a client; wherein the indication information indicates the client to resend the first data request and update the first target communication data.
4. The data processing method of claim 1, wherein after receiving the first data request, the method further comprises:
and locking the first communication data and the first version number of the first communication data.
5. The data processing method of claim 4, wherein after querying the first communication data and the first version number of the first communication data, the method further comprises:
and unlocking the first communication data and the first version number of the first communication data.
6. A data processing method is applied to a client, and is characterized by comprising the following steps:
sending a first data request to a server, wherein the first data request comprises a query object identifier;
receiving first communication data of the query object and a first version number of the first communication data fed back by a server; wherein the first communication data comprises historical communication data within a target billing period;
performing operation processing according to the second communication data and the first communication data to determine first target communication data;
and sending a second data request to a server, wherein the second data request comprises the first target communication data and the first version number of the first communication data.
7. The data processing method of claim 1, wherein the method further comprises:
receiving the updated first communication data sent by the server, and generating a charging reminding message according to the updated first communication data.
8. A data processing apparatus, comprising:
the first receiving module is used for receiving a first data request and determining a query object in the first data request;
the acquisition module is used for acquiring first communication data of the query object and a first version number of the first communication data; wherein the first communication data comprises historical communication data within a target billing period;
a second receiving module, configured to receive a second data request, obtain a second version number of the first communication data, and lock the first communication data and/or the second version number;
and the data processing module is used for processing the first communication data according to the first version number and the second version number and unlocking the first communication data and/or the second version number.
9. A data processing apparatus, comprising:
the first sending module is used for sending a first data request to a server, wherein the first data request comprises a query object identifier;
the receiving module is used for receiving the first communication data of the query object and the first version number of the first communication data fed back by the server; wherein the first communication data comprises historical communication data within a target billing period;
the operation module is used for performing operation processing according to the second communication data and the first communication data to determine first target communication data;
and the second sending module is used for sending a second data request to a server, wherein the second data request comprises the first target communication data and the first version number of the first communication data.
10. An electronic device, characterized in that the electronic device comprises:
one or more processors;
a memory;
one or more applications, wherein the one or more applications are stored in the memory and configured to be executed by the one or more processors, the one or more programs configured to: performing the data processing method according to any one of claims 1 to 7.
11. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the data processing method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110832989.2A CN114598559A (en) | 2021-07-22 | 2021-07-22 | Data processing method and device, electronic equipment and computer readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110832989.2A CN114598559A (en) | 2021-07-22 | 2021-07-22 | Data processing method and device, electronic equipment and computer readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114598559A true CN114598559A (en) | 2022-06-07 |
Family
ID=81814415
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110832989.2A Pending CN114598559A (en) | 2021-07-22 | 2021-07-22 | Data processing method and device, electronic equipment and computer readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114598559A (en) |
Citations (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060064408A1 (en) * | 2004-09-17 | 2006-03-23 | Fujitsu Limited | Program, method and apparatus for database management, and recording medium |
| WO2012055192A1 (en) * | 2010-10-25 | 2012-05-03 | 中兴通讯股份有限公司 | Method and apparatus for terminal updating network locking |
| JP2014178831A (en) * | 2013-03-14 | 2014-09-25 | Nec Corp | Information processor, database access method, and program |
| CN106294090A (en) * | 2016-08-03 | 2017-01-04 | 五八同城信息技术有限公司 | A kind of data statistical approach and device |
| CN106484321A (en) * | 2016-09-08 | 2017-03-08 | 华为数字技术（成都）有限公司 | A kind of date storage method and data center |
| CN107846288A (en) * | 2016-09-19 | 2018-03-27 | 中国电信股份有限公司 | For realizing the methods, devices and systems of charging |
| CN108270581A (en) * | 2016-12-31 | 2018-07-10 | 中国移动通信集团湖北有限公司 | Shared resource charge processing method and device |
| CN108829413A (en) * | 2018-05-07 | 2018-11-16 | 北京达佳互联信息技术有限公司 | Data-updating method, device and computer readable storage medium, server |
| WO2019127916A1 (en) * | 2017-12-29 | 2019-07-04 | 北京奇虎科技有限公司 | Data read/write method and device implemented on the basis of distributed consensus protocol |
| CN110046172A (en) * | 2018-12-29 | 2019-07-23 | 阿里巴巴集团控股有限公司 | In line computation data processing method and system |
| CN110333944A (en) * | 2019-04-19 | 2019-10-15 | 中国联合网络通信集团有限公司 | Call bill data method for processing business and equipment |
| CN110888889A (en) * | 2018-08-17 | 2020-03-17 | 阿里巴巴集团控股有限公司 | Data information updating method, device and equipment |
| CN111177121A (en) * | 2019-12-26 | 2020-05-19 | 平安普惠企业管理有限公司 | Order data feedback method and device, computer equipment and storage medium |
| CN112181481A (en) * | 2020-09-29 | 2021-01-05 | 北京达佳互联信息技术有限公司 | Authority updating method and device of version management system |
| CN112445783A (en) * | 2020-12-16 | 2021-03-05 | 中国联合网络通信集团有限公司 | Method, device and server for updating database |
| CN112990823A (en) * | 2021-03-29 | 2021-06-18 | 武汉虹信技术服务有限责任公司 | Method, system and storage medium for realizing inventory management |
-
2021
- 2021-07-22 CN CN202110832989.2A patent/CN114598559A/en active Pending
Patent Citations (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060064408A1 (en) * | 2004-09-17 | 2006-03-23 | Fujitsu Limited | Program, method and apparatus for database management, and recording medium |
| WO2012055192A1 (en) * | 2010-10-25 | 2012-05-03 | 中兴通讯股份有限公司 | Method and apparatus for terminal updating network locking |
| JP2014178831A (en) * | 2013-03-14 | 2014-09-25 | Nec Corp | Information processor, database access method, and program |
| CN106294090A (en) * | 2016-08-03 | 2017-01-04 | 五八同城信息技术有限公司 | A kind of data statistical approach and device |
| CN106484321A (en) * | 2016-09-08 | 2017-03-08 | 华为数字技术（成都）有限公司 | A kind of date storage method and data center |
| WO2018045758A1 (en) * | 2016-09-08 | 2018-03-15 | 华为技术有限公司 | Data storage method and data centre |
| CN107846288A (en) * | 2016-09-19 | 2018-03-27 | 中国电信股份有限公司 | For realizing the methods, devices and systems of charging |
| CN108270581A (en) * | 2016-12-31 | 2018-07-10 | 中国移动通信集团湖北有限公司 | Shared resource charge processing method and device |
| WO2019127916A1 (en) * | 2017-12-29 | 2019-07-04 | 北京奇虎科技有限公司 | Data read/write method and device implemented on the basis of distributed consensus protocol |
| CN108829413A (en) * | 2018-05-07 | 2018-11-16 | 北京达佳互联信息技术有限公司 | Data-updating method, device and computer readable storage medium, server |
| CN110888889A (en) * | 2018-08-17 | 2020-03-17 | 阿里巴巴集团控股有限公司 | Data information updating method, device and equipment |
| CN110046172A (en) * | 2018-12-29 | 2019-07-23 | 阿里巴巴集团控股有限公司 | In line computation data processing method and system |
| CN110333944A (en) * | 2019-04-19 | 2019-10-15 | 中国联合网络通信集团有限公司 | Call bill data method for processing business and equipment |
| CN111177121A (en) * | 2019-12-26 | 2020-05-19 | 平安普惠企业管理有限公司 | Order data feedback method and device, computer equipment and storage medium |
| CN112181481A (en) * | 2020-09-29 | 2021-01-05 | 北京达佳互联信息技术有限公司 | Authority updating method and device of version management system |
| CN112445783A (en) * | 2020-12-16 | 2021-03-05 | 中国联合网络通信集团有限公司 | Method, device and server for updating database |
| CN112990823A (en) * | 2021-03-29 | 2021-06-18 | 武汉虹信技术服务有限责任公司 | Method, system and storage medium for realizing inventory management |
Non-Patent Citations (1)
| Title |
|---|
| 张伟燕, 吴志杰, 夏涛: "利用版本号保护数据库一致性的EJB设计模式", 信息与电子工程, no. 02, 30 June 2004 (2004-06-30), pages 2 - 3 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108711047B (en) | Automatic repayment method, system and terminal equipment | |
| CN110910230A (en) | Accounting method, accounting system and storage medium | |
| CN110489418B (en) | Data aggregation method and system | |
| CN109614263B (en) | Disaster tolerance data processing method, device and system | |
| CN111104401A (en) | System and method for storing data in array and linked list based integrated structure | |
| CN107194712B (en) | Method and device for recording change information of shared account and method and system for supplementing account of internal account | |
| CN111651522A (en) | Data synchronization method and device | |
| CN111210345B (en) | Signature method and device based on block chain network transaction and terminal equipment | |
| CN114598559A (en) | Data processing method and device, electronic equipment and computer readable storage medium | |
| CN106156185A (en) | A kind of service request performs the querying method of state, Apparatus and system | |
| CN114626948A (en) | Block chain transaction accounting method and device, electronic equipment and storage medium | |
| CN112950171A (en) | Bank business processing system and method | |
| CN113822704A (en) | Method and device for calculating discount cost, electronic equipment and readable storage medium | |
| CN112634006A (en) | Account checking processing method and device, electronic equipment and storage medium | |
| CN111367634A (en) | Information processing method, information processing device and terminal equipment | |
| CN113055401B (en) | Enterprise business authorization processing method and device | |
| CN111882310B (en) | Data comparison method, device and equipment and computer readable storage medium | |
| CN113766442B (en) | Telephone traffic resource sharing method and device, computing equipment and storage medium | |
| CN113806379B (en) | Rating method, device, equipment and computer medium based on threshold optimistic lock | |
| CN110648208B (en) | Group identification method and device and electronic equipment | |
| CN108256989B (en) | Data display method and system of fund preparation system | |
| CN116629996A (en) | Data processing method, device, electronic equipment and readable storage medium | |
| CN117611179A (en) | Transaction request processing method, device, server and storage medium | |
| CN113448754A (en) | Account checking method and device and electronic equipment | |
| CN114255120A (en) | Updating method of collection-promoting data and related device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |