CN113630263B - Service data management method and device - Google Patents

Service data management method and device Download PDF

Info

Publication number
CN113630263B
CN113630263B CN202010382498.8A CN202010382498A CN113630263B CN 113630263 B CN113630263 B CN 113630263B CN 202010382498 A CN202010382498 A CN 202010382498A CN 113630263 B CN113630263 B CN 113630263B
Authority
CN
China
Prior art keywords
service
service data
group
fragment
data
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.)
Active
Application number
CN202010382498.8A
Other languages
Chinese (zh)
Other versions
CN113630263A (en
Inventor
李超
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Asiainfo Technologies China Inc
Original Assignee
Asiainfo Technologies China Inc
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Asiainfo Technologies China Inc filed Critical Asiainfo Technologies China Inc
Priority to CN202010382498.8A priority Critical patent/CN113630263B/en
Publication of CN113630263A publication Critical patent/CN113630263A/en
Application granted granted Critical
Publication of CN113630263B publication Critical patent/CN113630263B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

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/1432—Metric aspects
    • H04L12/1435—Metric aspects volume-based
    • 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/1442—Charging, metering or billing arrangements for data wireline or wireless communications at network operator level
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/185—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast with management of multicast group membership
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/70—Administration or customization aspects; Counter-checking correct charges
    • H04M15/765—Linked or grouped accounts, e.g. of users or devices
    • H04M15/7652—Linked or grouped accounts, e.g. of users or devices shared by users

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

The invention discloses a method and a device for managing service data, which are used for acquiring a service record query request, performing first locking processing on the service data of a first service corresponding to a group identifier of a first group, acquiring the current value of the service data of the first service corresponding to the group identifier of the first group, performing first unlocking processing on the service data of the first service corresponding to the group identifier of the first group, acquiring the usage of a first user in the used service data of the first service, performing second locking processing on the service data of the first service corresponding to the group identifier of the first group when the current value is not less than the usage of the used service data of the first service, modifying the current value of the service data of the first service corresponding to the group identifier of the first group according to the usage, and performing second unlocking processing on the service data of the first service corresponding to the group identifier of the first group, so that the processing efficiency of using records of a plurality of data can be effectively improved.

Description

Method and device for managing service data
Technical Field
The present invention relates to the field of data management, and in particular, to a method and an apparatus for managing service data.
Background
With the development of data management technology, the management technology of business data is continuously improved.
Currently, many large-scale enterprises usually handle corresponding group packages when handling the services of data resources such as internet traffic or duration of landline call with an operator. The data resource owned by the group package, i.e. the group data resource, can be owned and used by each member in the group. For the group data resource of each group package, a corresponding service record is recorded in the database of the server. Each service record includes the remaining group data resources in the corresponding group package.
After any member in the group uses the group data resource, the client device can correspondingly generate a data usage record (such as a call ticket), and the prior art can query the group data resource of the corresponding service record in the database according to the data usage record generated by the client device, lock the queried service record (the service record cannot process other data usage records corresponding to the service record during the locking period), calculate the group data resource which needs to be updated by the service record, update the group data resource in the service record, and unlock the service record after the updating is finished.
However, when the data resource in a group package is used by the members in the group for multiple times in a short time to generate multiple data usage records corresponding to the same service record, the prior art needs to process one data usage record before processing the other data usage record, and the processing efficiency is low.
Disclosure of Invention
In view of the above problems, the present invention provides a method and an apparatus for managing service data, which overcome or at least partially solve the above problems, and the technical solution is as follows:
a method for managing service data, a first device at least stores a service record of a first service, the service record of the first service at least includes: the group identification and the service data of the first service correspond to the group identification, and the method comprises the following steps:
acquiring a service record query request, wherein the service record query request carries a group identifier of a first group;
performing first locking processing on service data of a first service corresponding to the group identifier of the first group;
obtaining a current value of service data of a first service corresponding to the group identifier of the first group;
performing first unlocking processing on the service data of the first service corresponding to the group identifier of the first group;
obtaining the usage amount of a first user in the used service data of the first service;
when the current value is not less than the usage amount in the used service data of the first service, performing second locking processing on the service data of the first service corresponding to the group identifier of the first group;
modifying the current value of the service data of the first service corresponding to the group identifier of the first group according to the usage amount;
and performing second unlocking processing on the service data of the first service corresponding to the group identifier of the first group.
Optionally, the first device stores a summary table, where at least a total service record of the first service is stored in the summary table, where the total service record of the first service at least includes: a group identification and total service data of the first service, the group identification corresponding to the total service data of the first service,
the performing a first locking process on the service data of the first service corresponding to the group identifier of the first group includes:
performing first locking processing on total service data of a first service corresponding to the group identifier of the first group;
the obtaining of the current value of the service data of the first service corresponding to the group identifier of the first group includes:
obtaining a current value of total service data of a first service corresponding to the group identifier of the first group;
the performing of the first unlocking process on the service data of the first service corresponding to the group identifier of the first group includes:
and performing first unlocking processing on the total service data of the first service corresponding to the group identifier of the first group.
Optionally, the first device further stores a fragment table, where the fragment table at least includes the fragment service record group of the first service, the fragment service record group of the first service includes at least two fragment service records of the first service, and each fragment service record of the first service at least includes a corresponding one: the group identifier and the fragment service data of the first service, the initial value of each fragment service data of the first service corresponding to the group identifier of the first group is equal to the initial value of the total service data of the first service corresponding to the group identifier of the first group,
when the current value is not less than the usage amount in the used service data of the first service, performing a second locking process on the service data of the first service corresponding to the group identifier of the first group, including:
when the current value is not less than the usage amount in the used service data of the first service, determining a target fragment service record to be updated from each fragment service record of the first service corresponding to the group identifier of the first group;
performing second locking processing on the fragment service data recorded by the target fragment service;
the modifying, according to the usage amount, the current value of the service data of the first service corresponding to the group identifier of the first group includes:
modifying the current value of the fragment service data in the target fragment service record according to the usage amount;
the performing of the second unlocking processing on the service data of the first service corresponding to the group identifier of the first group includes:
and performing second unlocking processing on the fragment service data recorded by the target fragment service.
Optionally, the method further includes:
and modifying the current value of the total service data of the first service corresponding to the group identifier of the first group according to the modification of the current value of each fragment service data of the first service corresponding to the group identifier of the first group.
Optionally, the modifying the current value of the fragment service data in the target fragment service record according to the usage amount includes:
determining whether the current value of the fragment service data in the target fragment service record is not less than the usage amount in the used service data, if so, subtracting the usage amount in the used service data from the current value of the fragment service data in the target fragment service record, and taking the calculation result as the current value of the fragment service data in the target fragment service record;
otherwise, modifying the current value of the fragment service data in the target fragment service record to 0, and modifying the current values of other fragment service data of the first service corresponding to the group identifier of the first group, so that the sum of the current modification amount of the current value of the fragment service data in the target fragment service record and the current modification amount of the current value of the other fragment service data is equal to the usage amount in the used service data.
A management device for service data, a first device at least stores a service record of a first service, the service record of the first service at least includes: the group identification and the service data of the first service correspond to the group identification, and the device comprises: the device comprises a request obtaining unit, a first locking unit, a first obtaining unit, a first unlocking unit, a second obtaining unit, a second locking unit, a first modifying unit and a second unlocking unit, wherein:
the request obtaining unit is configured to obtain a service record query request, where the service record query request carries a group identifier of a first group;
the first locking unit is configured to perform first locking processing on service data of a first service corresponding to the group identifier of the first group;
the first obtaining unit is configured to obtain a current value of service data of a first service corresponding to the group identifier of the first group;
the first unlocking unit is used for performing first unlocking processing on the service data of the first service corresponding to the group identifier of the first group;
the second obtaining unit is configured to obtain a usage amount of the first user in the used service data of the first service;
the second locking unit is configured to perform second locking processing on the service data of the first service corresponding to the group identifier of the first group when the current value is not less than the usage amount in the used service data of the first service;
the first modifying unit is configured to modify a current value of service data of a first service corresponding to the group identifier of the first group according to the usage amount;
the second unlocking unit is configured to perform second unlocking processing on the service data of the first service corresponding to the group identifier of the first group.
Optionally, the first device stores a summary table, where at least a total service record of the first service is stored in the summary table, and the total service record of the first service at least includes: a group identification and total service data of the first service, the group identification corresponding to the total service data of the first service,
the first locking unit is specifically configured to:
performing first locking processing on total service data of a first service corresponding to the group identifier of the first group;
the first obtaining unit is specifically configured to:
obtaining a current value of total service data of a first service corresponding to the group identifier of the first group;
the first unlocking unit is specifically configured to:
and performing first unlocking processing on the total service data of the first service corresponding to the group identifier of the first group.
Optionally, the first device further stores a fragment table, where the fragment table at least includes the fragment service record group of the first service, the fragment service record group of the first service includes at least two fragment service records of the first service, and each fragment service record of the first service at least includes a corresponding one: the group identifier and the fragment service data of the first service, the initial value of each fragment service data of the first service corresponding to the group identifier of the first group is equal to the initial value of the total service data of the first service corresponding to the group identifier of the first group,
the second locking unit specifically includes: a first determination unit and a locking processing unit, wherein:
the first determining unit is configured to determine, when the current value is not less than the usage amount in the used service data of the first service, a target fragment service record to be updated from each fragment service record of the first service corresponding to the group identifier of the first group;
the locking processing unit is used for carrying out second locking processing on the fragment service data recorded by the target fragment service;
the first modification unit is specifically configured to:
modifying the current value of the fragment service data in the target fragment service record according to the usage amount;
the second unlocking unit is specifically configured to:
and performing second unlocking processing on the fragment service data recorded by the target fragment service.
Optionally, the apparatus further comprises: a second modification unit to:
and modifying the current value of the total service data of the first service corresponding to the group identifier of the first group according to the modification of the current value of each fragment service data of the first service corresponding to the group identifier of the first group.
Optionally, the first modifying unit is specifically configured to:
determining whether the current value of the fragment service data in the target fragment service record is not less than the usage amount in the used service data, if so, subtracting the usage amount in the used service data from the current value of the fragment service data in the target fragment service record, and taking the calculation result as the current value of the fragment service data in the target fragment service record;
otherwise, modifying the current value of the fragment service data in the target fragment service record to 0, and modifying the current values of other fragment service data of the first service corresponding to the group identifier of the first group, so that the sum of the current modifier of the current value of the fragment service data in the target fragment service record and the current modifier of the current values of other fragment service data is equal to the usage in the used service data.
The invention provides a method and a device for managing service data, which are characterized in that a service record query request is obtained, first locking processing is carried out on service data of a first service corresponding to a group identifier of a first group, a current value of the service data of the first service corresponding to the group identifier of the first group is obtained, first unlocking processing is carried out on the service data of the first service corresponding to the group identifier of the first group, the usage of a first user in the used service data of the first service is obtained, when the current value is not less than the usage of the used service data of the first service, second locking processing is carried out on the service data of the first service corresponding to the group identifier of the first group, the current value of the service data of the first service corresponding to the group identifier of the first group is modified according to the usage, second unlocking processing is carried out on the service data of the first service corresponding to the group identifier of the first group, and the service data is not locked in a stage of calculating a value which the service data needs to be checked and reduced, so that the service record containing the service data can carry out effective processing on other pieces of service data in the calculation stage, and can improve the efficiency of using records of a plurality of pieces of service data; and the second locking processing can be used for locking the service record by the used service data obtained this time in the process of modifying the current value of the service data in the service record, so that the accuracy of the data is ensured, writing conflict and other situations are prevented, and the second unlocking processing can be used for timely unlocking the service record after modifying the current value of the service data in the service record, so that the method can be used for processing other used service data, and the processing efficiency of the use records of a plurality of data is further improved.
The above description is only an overview of the technical solutions of the present invention, and the present invention can be implemented in accordance with the content of the description so as to make the technical means of the present invention more clearly understood, and the above and other objects, features, and advantages of the present invention will be more clearly understood.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
Fig. 1 is a flowchart illustrating a method for managing service data according to an embodiment of the present invention;
fig. 2 is a flowchart illustrating another method for managing service data according to an embodiment of the present invention;
fig. 3 is a flowchart illustrating another method for managing service data according to an embodiment of the present invention;
fig. 4 is a schematic structural diagram illustrating a service data management apparatus according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram illustrating another management apparatus for service data according to an embodiment of the present invention;
fig. 6 is a schematic structural diagram illustrating another management apparatus for service data according to an embodiment of the present invention.
Detailed Description
Exemplary embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the invention are shown in the drawings, it should be understood that the invention can be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art.
This embodiment proposes a method for managing service data, where a first device at least stores a service record of a first service, and the service record of the first service at least includes: as shown in fig. 1, the method may include the following steps:
s10, obtaining a service record query request, wherein the service record query request carries a group identifier of a first group;
the first device may be a server device (e.g., a server), or may be a switch or a base station.
The first service may be multiple types of communication services, such as: traffic type services, call duration type services, short message number type services, and the like, which are not limited in the present invention. It will be appreciated that there may be a variety of types of traffic, for example: traffic type services are a number of different services, such as: 100G traffic packet traffic per month, 50G traffic packet traffic active in the month, etc.
Wherein, a group may include a plurality of users, and the group may be an organization, etc., for example: a company uniformly orders a group call duration service for mobile phones of employees, and each employee of the company shares 10000 minutes of free calling call duration every month. The group identifier may be a unique identifier of the group, i.e. the present invention may uniquely determine a group according to a group identifier. In practical applications, the group identifier may be composed of one or more of numbers, letters, symbols, and other characters, which is not limited in the present invention.
In practical application, when a certain group subscribes to a service, the invention can correspondingly establish a service record to record the relevant information of the service subscribed by the group.
The service data may record group data resources in the corresponding service.
Specifically, the present invention may store the service record in a data table of a database of the first device.
It should be noted that the service record may further include information such as a service type and a validity period.
Specifically, the first service may be a periodic service (e.g., a service that is active every month) or may be a one-time service (e.g., a service that is active only in the month). When the first service subscribed by the first group is valid, the service data corresponding to the first service and the first group in the data table is initialized to an initial value, regardless of the periodic service or the one-time service. The initial value may be a preset initial value of the first service, for example: the first service is a periodic service, and the initial value of the first service is initialized to 100G at the beginning of each month if the flow rate of the first service is 100G per month.
It will be appreciated that as the user uses the service, the initial value of the total service data will gradually decrease and will no longer be the initial value, at which point the initial value becomes the current value.
It should also be noted that the service record may be commonly owned and used by members of the group subscribing to the service. When any member in the group uses the subscribed service, the service data of the corresponding service record can be updated accordingly.
Optionally, in the method for managing other service data provided in this embodiment, before step S10, the method may further include:
acquiring used service data of a first user;
determining a group identifier of a first group to which the first user belongs, wherein the first group comprises a plurality of users.
Specifically, after the first user uses a certain service, the present invention generates the used service data of the service accordingly. The used service data is a data usage record generated after the first user uses a certain service.
Specifically, after the used service data is obtained, the group identifier of the first group to which the first user belongs may be determined according to the identity identifier of the first user. For example, if the third zhang is an employee of the company a, and the identity of the third zhang is a mobile phone number of the third zhang, it can be determined that the third zhang belongs to the company a according to the mobile phone number of the third zhang. Specifically, when transacting business for a group, a correspondence between the group identity of the group and the identity of the user in the group may be established. The invention can determine the group identification of the first group to which the first user belongs according to the corresponding relation.
The identity of the first user may be stored in the used service data of the first user, for example: the used service data of the first user is a traffic usage record of the first user, and the traffic usage record carries: the mobile phone number, the used traffic, the time period, and the like of the first user to indicate which user uses how much traffic in which time period, so as to perform a subtraction on the used traffic from the group according to the traffic usage record, for example: company A transacts the group traffic service, employees of company A share the free traffic of 100G, zhang III is employees of company A, and if 1G is used, the free traffic of company A is reduced to 99G.
In practical application, the invention can also group users according to service types, and divide users sharing the same type of service data into a group. For example: company a has 100 employees, wherein 30 employees are web promoter employees, and 70 employees are telephone promoter employees, the 30 employees can be handled with a traffic service that they can share, for example, the 30 employees share 100G free traffic, so that the 30 employees sharing the free traffic can be divided into a group. Accordingly, another 70 employees may be transacted with a calling service they can share, for example, the 70 employees share 10000 minutes of free calling, so that the 70 employees sharing free calling can be divided into another group.
Specifically, after determining the group identifier of the first group to which the first user belongs, the present invention may generate a service record query request according to the group identifier of the first group, so as to query the service data of the first service corresponding to the group identifier of the first group to which the first user belongs and the first service used by the first user.
S20, performing first locking processing on the service data of the first service corresponding to the group identifier of the first group;
specifically, when the used service data is service data of a certain type, if the first group to which the first user belongs only subscribes to a service of the certain type, the present invention may determine that the used service data belongs to the subscribed service of the certain type, and query the current value of the corresponding service data. For example: the company A only orders the B flow service shared by the employees for the employees, and does not order other flow services, so that when the used service data generated after the employee of the company A uses three flows is obtained, the used service data can be determined to belong to the B flow service according to the service type of the used service data, and then the current value of the service data of the B flow service of the company A is inquired.
When the used service data is a certain type of service data, if a first group to which the first user belongs subscribes a plurality of services of the type, the present invention may determine one of the services of the type as a service to which the used service data belongs according to a preset selection mode. The preset selection mode may be a sequence of use. For example: company A orders the flow business B and flow business C shared by employees, and the preset selection mode is as follows: firstly, the B flow service is used, then, the C flow service is used, when the invention obtains the used service data generated after the employee of the company A uses three flows, the current value of the service data of the B flow service of the company A can be firstly inquired, whether the current value is not less than the usage amount in the used service data is judged, and if the current value is less than the usage amount, the current value of the service data of the C flow service of the company A is inquired.
Specifically, before obtaining the service data of the first service corresponding to the group identifier of the first group, the present invention needs to perform a first locking process on the service data in advance.
Specifically, the first locking processing can be performed on the service data of the service record through the first locking processing on the service record. The invention can use the existing scheme to perform the first locking processing on the business record.
It should be noted that, during the locking of the service data of the service record of the first service, the service data that has undergone the first locking process may be processed (including reading and updating) only according to the used service data obtained this time, but the service data that has undergone the first locking process cannot be processed according to other used service data.
S30, obtaining a current value of the service data of the first service corresponding to the group identifier of the first group;
s40, performing first unlocking processing on the service data of the first service corresponding to the group identification of the first group;
specifically, after the current value of the service data of the first service corresponding to the group identifier of the first group is obtained, the first unlocking processing may be performed on the service data without waiting until the service data completes the update of the used service data. Wherein the first unlocking process corresponds to the first locking process.
It should be noted that, after the first unlocking processing is performed on the service data of the first service corresponding to the group identifier of the first group, the present invention may use the service record containing the service data to process other used service data.
S50, obtaining the usage amount of a first user in the used service data of the first service;
s60, when the current value is not less than the usage amount in the used service data of the first service, performing second locking processing on the service data of the first service corresponding to the group identifier of the first group;
when the current value is smaller than the usage amount in the used service data of the first service, judging whether the group identifier of the first group to which the first user belongs corresponds to other services with the same type as the first service, and if so, inquiring the current value of the service data of the other services corresponding to the group identifier of the first group.
It should be noted that, when the current value is not less than the usage amount in the used service data of the first service, it is indicated that the service data of the first service corresponding to the group identifier of the first group may satisfy the processing of the used service data this time.
Specifically, the present invention may perform the second locking process on the service data of the first service corresponding to the group identifier of the first group before updating the service data of the first service.
The second locking processing is similar to the locking principle of the first locking processing, and when the service data of the first service corresponding to the group identifier of the first group is in the second locking processing period, the service data which is subjected to the second locking processing can be processed (including reading and updating) only according to the current used service data, but the service data which is subjected to the second locking processing cannot be processed according to other used service data.
S70, modifying the current value of the service data of the first service corresponding to the group identifier of the first group according to the usage amount;
optionally, in the method for managing other service data provided in this embodiment, step S70 may specifically be:
and when the current value of the service data of the first service corresponding to the group identifier of the first group is not less than the usage amount in the used service data of the first service, subtracting the usage amount in the used service data from the current value, and taking the calculation result as the current value of the service data of the first service corresponding to the group identifier of the first group.
For example: the current remaining flow value of the group flow service handled by company a is 20G flow, employee a uses 1G flow in the group flow service for three times, that is, the current value 20G of the group flow service is greater than the current amount 1G of the group flow service for three times, 1G can be subtracted from the current value 20G of the group flow service, and the calculation result 19G can be used as the current value of the group flow service.
Optionally, in the method for managing other service data provided in this embodiment, step S70 may also specifically be:
and when the current value of the service data of the first service corresponding to the group identifier of the first group is not less than the usage amount in the used service data of the first service, reducing the current value core to zero, and taking the zero as the current value of the service data of the first service corresponding to the group identifier of the first group.
For example: the current remaining flow value of the group flow service handled by company a is 2G flow, the employee of company a uses 3G flow in the group flow service for the second three times, that is, the current value 2G of the group flow service is smaller than the usage amount 3G of the group flow service for the second three times, 2G can be subtracted from the current value 2G of the group flow service, and the calculation result 0G can be used as the current value of the group flow service.
And S80, performing second unlocking processing on the service data of the first service corresponding to the group identifier of the first group.
Wherein the second unlocking process corresponds to the second locking process.
Specifically, the present invention may modify the current value of the service data of the service record of the first service according to the usage amount, and then perform the second unlocking process. After the second unlocking processing is carried out, the unlocked service record can be used for processing other used service data.
Through the second locking processing, the invention can ensure that the business record is locked by the used business data obtained at this time in the process of modifying the current value of the business data in the business record, thereby ensuring the accuracy of the data and preventing the situations of writing conflict and the like. Meanwhile, the invention can also unlock the business record in time after modifying the current value of the business data in the business record through the second unlocking treatment, thereby leading the invention to be used for processing other used business data.
It should be noted that, after querying the service data of the service record of the first service corresponding to the first group identifier, the present invention performs the first locking process on the queried service data, and performs the first unlocking process on the service data after obtaining the current value of the service data, and then does not perform the locking at the stage of calculating the value of the service data that needs to be verified and subtracted, and performs the second locking process on the service data before updating the service data according to the value that needs to be verified and subtracted. Compared with the prior art, the method and the device have the advantages that the business data is not locked at the stage of calculating the value of the business data to be verified, so that the business records containing the business data can process other used business data at the calculation stage, and the processing efficiency of a plurality of data use records is effectively improved.
The management method for service data provided in this embodiment includes performing, by obtaining a service record query request, a first locking process on service data of a first service corresponding to a group identifier of a first group, obtaining a current value of the service data of the first service corresponding to the group identifier of the first group, performing a first unlocking process on the service data of the first service corresponding to the group identifier of the first group, obtaining a usage amount of a first user in used service data of the first service, performing, when the current value is not less than the usage amount in the used service data of the first service, a second locking process on the service data of the first service corresponding to the group identifier of the first group, modifying, according to the usage amount, the current value of the service data of the first service corresponding to the group identifier of the first group, performing a second unlocking process on the service data of the first service corresponding to the group identifier of the first group, and not locking the service data in a stage of calculating a value that the service data needs to be checked and subtracted, so that service records including the service data can be processed by other pieces of effective data, and the efficiency of the service records can be improved; and the service record can be locked by the used service data obtained this time in the process of modifying the current value of the service data in the service record through the second locking processing, so that the accuracy of the data is ensured, the situations of writing conflict and the like are prevented, and the service record can be unlocked in time after the current value of the service data in the service record is modified through the second unlocking processing, so that the method can be used for processing other used service data, and the processing efficiency of the use records of a plurality of data is further improved.
Based on the steps shown in fig. 1, this embodiment further provides another service data management method, as shown in fig. 2, where the first device stores a summary table and a fragmentation table, where the summary table at least stores a total service record of the first service, and the total service record of the first service at least includes: the group identifier corresponds to the total service data of the first service, the fragment table at least includes a fragment service record group of the first service, the fragment service record group of the first service includes at least two fragment service records of the first service, and each fragment service record of the first service at least includes corresponding ones: the group identifier is equal to the initial value of the total service data of the first service corresponding to the group identifier of the first group.
The service record in the method shown in fig. 1 may be a total service record or a fragment service record.
Wherein, step S20 may specifically be:
and carrying out first locking processing on the total service data of the first service corresponding to the group identifier of the first group.
Specifically, the present invention may set a summary table and a fragment table in a database of the first device. The summary table and the fragment table can be data tables in the database.
Wherein, the total service data can record the group data resource in the corresponding service.
Wherein, the total table stores total service data of at least one service of at least one group, for example: the group is company a, company a subscribes two services, namely a traffic B service and a traffic C service, and then the summary table can store the total service data of the traffic B service of company a and the total service data of the traffic C service of company a. Each total service record in the total table may include total service data of a group in a service. Specifically, each total service record may include the corresponding: group identification, service identification and total service data.
Specifically, the present invention can determine the service identifier of the service to which the used service data of the user belongs and the group identifier of the group to which the user belongs, and further query the total service data corresponding to the determined service identifier and group identifier from the summary table. Of course, the service identification in the summary table is not necessary, for example: when the total table has a plurality of tables and only one service data of each service is stored in each table, the service identifier does not need to be stored in the total table. At this time, the present invention may determine to store the summary table of the service data of the service to which the used service data belongs according to the service type of the service to which the used service data belongs, and then query the corresponding total service data through the group identifier of the group to which the user belongs.
Each fragment service record group in the fragment table may correspond to one total service record in the total table. Specifically, the total service data in one total service record may be split to obtain a plurality of fragment service data, each fragment service data obtained by the splitting may be located in one fragment service record, and the fragment service record in which the plurality of fragment service data are obtained by the splitting forms one fragment service record group corresponding to the total service record. Specifically, after adding, the data of each fragment service in a fragment service record group may be equal to the total service data in the total service record corresponding to the fragment service record group. Of course, similar to the general table, the fragment table may also store the service identifier, and the service identifier is not necessarily in the fragment table.
Optionally, the total service record in the total table may further include a total record identifier, and the total record identifier in each total service record may be different. The master record identification may be a primary key in a master table.
Optionally, the fragment service record in the fragment table may further include a fragment record identifier, and the fragment record identifier in each fragment service record may be different. The fragment record identification may be a primary key in the fragment table.
Because there are many kinds of business, the invention can set up the summary table and correspondent fragment table separately to each kind of business separately, for example: setting a first summary table for storing service data of a first service, and setting a first fragmentation table for storing the service data of the first service; setting a second summary table for storing service data of a second service, and setting a second fragmentation table for storing the service data of the second service, wherein the first summary table and the second summary table are different; the first and second fragmentation tables are different. For convenience of understanding, the following examples illustrate the first summary table and the first fragmentation table, respectively:
for example: the first service may be a B-traffic service, and the first total table may be as shown in table 1 or table 2.
Table 1, B flow service summary table
Group identification Total traffic data
Company A 20G
Company B 10G
Table 2, B flow service summary table
Group identification Service identification Total traffic data
Company A B flow service 20G
Company B B flow service 10G
Table 1 and table 2 are both a B traffic service general table, and both store service data of a B traffic service, and table 1 integrates service data of B traffic services of companies a and B into one table, so that for a B traffic service, whether a company a or a company B, the general service data of the B traffic service can be determined by a group identifier. The differences between table 2 and table 1 are: the service identity is also included in table 2. The total service data in table 2 can be further verified as the service data of which service by the service identifier. Of course, both table 1 and table 2 can determine which service is the total service data in the total table by the table name. Namely: the service identity is not necessarily in the summary table.
For example: the first traffic may be B traffic and the first fragmentation table may be as shown in table 3 or table 4.
Table 3, B flow service fragment table
Group identification Slicing service data
Company A 10G
Company A 10G
Company B 8G
Company B 2G
Table 4, B flow service fragment table
Group identification Service identification Slicing service data
Company A B flow service 10G
Company A B flow service 10G
Company B B flow service 8G
Company B B flow service 2G
Table 3 is a fragmentation table corresponding to the summary table shown in table 1, and table 4 is a fragmentation table corresponding to the summary table shown in table 2. The sum of the fragment service data of the B traffic service corresponding to the group identifier "company a" in table 3 is equal to the total service data of the B traffic service corresponding to the group identifier "company a" in table 1. Correspondingly, the sum of the fragment service data corresponding to the group identifier "company a" and corresponding to the service identifier "B traffic service" in table 4 is equal to the total service data corresponding to the group identifier "company a" and corresponding to the service identifier "B traffic service" in table 2. The difference between table 4 and table 3 is that: the service identity is also included in table 4.
Of course, since there are a plurality of groups, the present invention may also separately set a summary table and a corresponding fragment table for each group, for example: setting a third general table for storing the service data of the first group, and setting a third fragment table for storing the service data of the first group; setting a fourth general table for storing the service data of the second group, and setting a fourth fragment table for storing the service data of the second group, wherein the third general table is different from the fourth general table; the third and fourth segment tables are different.
For convenience of understanding, the following examples respectively illustrate the third summary table and the third segment table:
for example: the group of the first group is identified as company a and the third summary table may be as shown in table 5 or table 6.
TABLE 5 general Table of company A
Service identification Total traffic data
B flow service 20G
C traffic service 30G
TABLE 6, general Table of company A
Group identification Service identification Total traffic data
Company A B flow service 20G
Company A C flow service 30G
Tables 5 and 6 are the general tables of company a, which both store the service data of company a, and tables 5 and 6 both integrate the service data of the B traffic service and the C traffic service of company a into one table, so that for company a, no matter the B traffic service or the C traffic service, the corresponding general service data can be determined by the service identifier. The difference between tables 5 and 6 is that: the group identification is also included in table 6. By means of the group identification, it is further possible to verify which group the total service data in table 6 is. Of course, both table 5 and table 6 can determine which group of service data the total service data in the total table is by table name.
For example: the first group may be company a and the third shard table may be as shown in table 7 or table 8.
TABLE 7, A division Table
Service identification Slicing service data
B flow service 10G
B flow service 10G
C flow service 18G
C traffic service 12G
TABLE 8, A company slicing Table
Group identification Service identification Slicing service data
Company A B flow service 10G
Company A B flow service 10G
Company A C flow service 18G
Company A C traffic service 12G
Table 7 is a fragmentation table corresponding to the summary table shown in table 5, and table 8 is a fragmentation table corresponding to the summary table shown in table 6. The sum of the fragmented service data corresponding to the service identifier "B traffic service" in table 7 is equal to the total service data corresponding to the service identifier "B traffic service" in table 5. Correspondingly, the sum of the fragment service data corresponding to the group identifier "company a" and corresponding to the service identifier "B traffic service" in table 8 is equal to the total service data corresponding to the group identifier "company a" and corresponding to the service identifier "B traffic service" in table 6. The differences between table 8 and table 7 are: the group identification is also included in table 8.
Of course, the present invention may also separately set a summary table and a corresponding fragment table for each group and each service, for example: setting a fifth general table for storing service data of the first service of the first group, and setting a fifth fragment table for storing service data of the first service of the first group; setting a sixth summary table for storing the service data of the first service of the second group, and setting a sixth fragmentation table for storing the service data of the first service of the second group; setting a seventh general table for storing the service data of the second service of the first group, and setting a seventh fragment table for storing the service data of the second service of the first group; and setting an eighth general table for storing the service data of the second service of the second group, and setting an eighth fragment table for storing the service data of the second service of the second group.
The present invention can set the service data of multiple services of multiple groups in one summary table, as shown in table 9.
TABLE 9 summary
Group identification Service identification Total traffic data
Company A B flow service 20G
Company D C traffic service 30G
The present invention can set the service data of multiple services of multiple groups in one fragmentation table, as shown in table 10.
Table 10, slicing table
Group identification Service identification Slicing service data
Company A B flow service 10G
Company A B flow service 10G
Company D C flow service 18G
Company D C traffic service 12G
Specifically, the total service record may further include information such as a service type and an effective period. The fragmented service record may also contain information such as service type, validity period, etc.
In practical application, when a certain group subscribes to a service, the invention can correspondingly establish a total service record to record the relevant information of the service subscribed by the group.
Specifically, no matter whether the first service is a periodic service or a one-time service, when the first service subscribed by the first group becomes effective, the total service data corresponding to the first service and the first group in the total table is initialized to the initial value. The initial value may be a preset initial value of the first service, for example: the first service is a periodic service, and the initial value of the first service is initialized to 100G at the beginning of each month if the flow rate of the first service is 100G each month. Similar to the general table, the fragment service data corresponding to the first service and the first group in the fragment table may also be initialized to their respective initial values. After each initialization, the initial value of each fragment service data of the first service corresponding to the group identifier of the first group is equal to the initial value of the total service data of the first service corresponding to the group identifier of the first group.
It will be appreciated that as the user uses the service, the initial value of the total service data will gradually decrease and will no longer be the initial value, at which point the initial value becomes the current value.
It should be noted that the total service record can be commonly owned and used by the members of the group subscribing to the service. The invention can establish a plurality of corresponding fragment service records according to the total service record, and distribute the total service data in the total service record to the fragment service data in the corresponding plurality of fragment service records for recording. When any member in the group uses the subscribed service, the fragment service data in the corresponding at least one fragment service record can be updated accordingly, and further, the total service data in the total service record can be updated according to the corresponding fragment service data.
Specifically, after the used service data of the user is obtained, the present invention may perform the first locking process according to the total service data of the first service corresponding to the group identifier of the first group to which the user belongs.
Wherein, step S30 may specifically be:
and obtaining the current value of the total service data of the first service corresponding to the group identifier of the first group.
Specifically, when the used service data is a certain type of service data, if the first group to which the first user belongs only subscribes to one service of the type, the present invention may determine that the used service data belongs to the subscribed service of the type, and query the current value of the corresponding total service data.
When the used service data is a certain type of service data, if a first group to which the first user belongs subscribes a plurality of services of the type, the present invention may determine one of the services of the type as a service to which the used service data belongs according to a preset selection mode. The preset selection mode may be a sequence of use.
Wherein, step S40 may specifically be:
and performing first unlocking processing on the total service data of the first service corresponding to the group identifier of the first group.
Wherein, step S60 may specifically include:
s61, when the current value is not less than the usage amount in the used service data of the first service, determining a target fragment service record to be updated from each fragment service record of the first service corresponding to the group identifier of the first group;
when the current value is smaller than the usage amount in the used service data of the first service, judging whether the group identifier of the first group to which the first user belongs corresponds to other services with the same type as the first service, and if so, inquiring the current value of the total service data of the other services corresponding to the group identifier of the first group.
And when the current value is not less than the usage amount in the used service data of the first service, the total service data of the first service corresponding to the group identifier of the first group can meet the processing of the used service data. At this time, the present invention does not directly perform the subtraction in the total service data, but determines the target fragment service record to be updated from each fragment service record of the first service corresponding to the group identifier of the first group, and processes the used service data in the fragment service data of the target fragment service record. Since there are multiple fragment service records corresponding to the first group and the first service, the used service data of different users can be processed in different part of fragment service records. When one used service data is processed each time, only part of the fragment service records need to be locked, and all the fragment service records and the total service records do not need to be locked, so that a plurality of used service data can be processed at the same time, and the processing efficiency is high.
Specifically, the present invention may determine the target fragment service record to be updated from the fragment service records of the first service corresponding to the group identifier of the first group according to a preset selection manner. The preset selection mode can be as follows: random selection, sequential selection according to the size of the current value of the fragment service data in the fragment service record, and the like.
S62, carrying out second locking processing on the fragment service data recorded by the target fragment service;
specifically, the present invention can perform the second locking processing only on the target fragment service record that needs to be updated, and does not need to perform the second locking processing on the total service record corresponding to the target fragment service record and other fragment service records in the total service record. When the current value of the fragment service data in the target fragment service record is smaller than the usage amount in the used service data and other fragment service records need to be updated according to the usage amount in the used service data, the invention also performs second locking processing on other fragment service records needing to be updated.
Wherein, step S70 may specifically be:
and modifying the current value of the fragment service data in the target fragment service record according to the usage amount.
Optionally, in the method for managing other service data provided in this embodiment, the modifying, according to the usage amount, the current value of the fragment service data in the target fragment service record may specifically include:
determining whether the current value of the fragment service data in the target fragment service record is not less than the usage amount in the used service data, if so, subtracting the usage amount in the used service data from the current value of the fragment service data in the target fragment service record, and taking the calculation result as the current value of the fragment service data in the target fragment service record;
otherwise, modifying the current value of the fragment service data in the target fragment service record to 0, and modifying the current values of other fragment service data of the first service corresponding to the group identifier of the first group, so that the sum of the current modifier of the current value of the fragment service data in the target fragment service record and the current modifier of the current values of other fragment service data is equal to the usage in the used service data.
Specifically, the present invention can determine whether the current value of the fragment service data in the target fragment service record is not less than the usage amount in the used service data, and if so, can determine that the fragment service data in the target fragment service record can be used for processing the used service data. For example, a user uses 100 megabits of traffic to watch a video, the fourth fragmentation service record is selected as a target fragmentation service record, and the current value of the fragmentation service data of the fourth fragmentation service record is greater than 100 megabits, so that the fragmentation service data of the fourth fragmentation service record can be used for processing the 100 megabits of traffic used by the user. Specifically, the current value of the fragment service data of the fourth fragment service record may be subtracted by 100 megabytes. When the current value of the fragment service data in the target fragment service record is less than the usage amount in the used service data, it indicates that the current value of the fragment service data in the target fragment service record cannot meet the processing of the used service data, and at this time, the invention can use the target fragment service record and other fragment service records to process the used service data together.
It is to be understood that the above-mentioned value of the reduction of the fragmented service data is only an optional example. Specifically, the present invention may also determine the value to be subtracted of each fragment service data according to the size relationship of each fragment service data. Such as: the invention can firstly control the minimum fragment service data to be reduced to 0, namely, the minimum fragment service data is controlled to be completely used for consuming the usage amount of the used service data, then the minimum fragment service data is selected from the rest fragment service data to be used for consuming the usage amount of the rest used service data, and the like in turn until all the fragment service data completely consume the usage amount of the used service data.
It should be noted that, when the fragment service record is in a fragment state, that is, the value of the fragment service data in the fragment service record is smaller than the minimum data consumption unit that can be used to process the usage amount of the used service data, the fragment service data in the fragment service record cannot be used to consume the usage amount of the used service data. To this end, optionally, in the method for managing other service data provided in this embodiment, the method may further include:
and concentrating the first sliced service data with the current value smaller than the preset allowable threshold value into second sliced service data, wherein the first sliced service data and the second sliced service data belong to the same service and correspond to the same group identifier.
The preset allowable threshold may be a minimum data consumption unit that allows the fragmented service data to be used for processing the usage amount of the used service data. Of course, the preset allowable threshold may also be determined by a technician according to the actual situation, and the present invention is not limited thereto.
It should be noted that, because the first fragment service data and the second fragment service data belong to the same service and correspond to the same group identifier, the first fragment service data and the second fragment service data respectively correspond to different fragment service records in the same fragment service record group, for example, the first fragment service data corresponds to a first fragment service record in the first fragment service record group, and the second fragment service data corresponds to a second fragment service record in the first fragment service record group.
Specifically, the first fragmentation service data is fragmentation service data recorded by a fragmentation service in a fragmentation state; the second fragment service data may be fragment service data recorded by another fragment service in a fragment state, and the second fragment service data may also be fragment service data recorded by a fragment service not in a fragment state, that is, a current value of the second fragment service data may be smaller than a preset allowable threshold, or may not be smaller than the preset allowable threshold.
Specifically, the present invention may centralize the first fragment service data into the second fragment service data whose current value is not less than the preset allowable threshold, so that the fragment service data (i.e. the first fragment service data) in the fragment service record in the original fragment state may be used as part of the service data in the fragment service data (i.e. the second fragment service data) in the fragment service record not in the fragment state to consume the used service data, thereby improving the utilization rate of the fragment service data. For example, when the preset allowable threshold is 20, the current value of the first tile service data is 3, and the current value of the second tile service data is 100, the first tile service data cannot be used alone for consuming the usage amount of the used service data, the present invention may centralize the first tile service data with the current value of 3 into the second tile service data with the current value of 100, and then, the current value of the first tile service data is zero, and the current value of the second tile service data is 103, which is the sum of 100 and 3, so that the first tile service data which is originally smaller than the preset allowable threshold and has the value of 3 may now be used as a part of the service data in the second tile service data with the current value of 103 to consume the usage amount of the used service data.
Specifically, the present invention may also centralize the first fragment service data into the second fragment service data whose current value is smaller than the preset allowable threshold, so that the fragment service data (i.e., the first fragment service data) in the fragment state fragment service record is centralized into the fragment service data (i.e., the second fragment service data) in another fragment state fragment service record, so that the current value of the fragment service data recorded by the fragment service data after the fragment service data has been centralized, i.e., the current value of the second fragment service data is not smaller than the preset allowable threshold, thereby enabling the fragment service data recorded by the two fragment services in the fragment state to be used for consuming the used service data together, and improving the utilization rate of the fragment service data. For example, when the preset allowable threshold is 20, the current value of the first sliced service data is 8, and the current value of the second sliced service data is 12, neither the first sliced service data nor the second sliced service data can be used alone to consume the usage amount of the used service data, the present invention may collect the current value 8 of the first sliced service data into the current value 12 of the second sliced service data, and then the current value of the first sliced service data is 0, and the current value of the second sliced service data is the sum of 12 and 8, that is, 20, so that the first sliced service data and the second sliced service data that cannot be used alone to consume the used service data can be used together to consume the usage amount of the used service data by the second sliced service data, which is not less than the preset allowable threshold and has the current value of 20.
In practical application, the present invention can centralize all the fragment service data whose current value is smaller than the preset allowable threshold value into one fragment service data whose current value is smaller than or not smaller than the preset allowable threshold value, so that the fragment service data recorded by all the fragment services in the fragment state can be centralized into one fragment service data, and are used for consuming the usage amount of the used service data together.
Optionally, the present invention may also centralize part or all of the fragmented service data of the second fragmented service data into the first fragmented service data whose current value is smaller than the preset allowable threshold.
Specifically, when the current value of the second fragmented service data is not less than the preset allowable threshold, the present invention may divide a certain number of partial fragmented service data from the second fragmented service data according to the difference between the first fragmented service data and the preset allowable threshold, for example, the number of the partial fragmented service data is equal to the difference, or the number of the partial fragmented service data is equal to the sum of the difference and the integral multiple of the preset allowable threshold, and centralize the partial fragmented service data into the first fragmented service data, so that the current value of the first fragmented service data is not less than the preset allowable threshold, that is, the first fragmented service data may be used alone to consume the usage amount of the used service data, thereby improving the utilization rate of the fragmented service data.
Specifically, when the current value of the second fragmented service data is not less than the preset allowable threshold, the present invention may also directly collect all fragmented service data of the second fragmented service data into the first fragmented service data, so that the second fragmented service data may be used as a part of the first fragmented service data and used for consuming the usage amount of the used service data together, and further, the first fragmented service data, which originally cannot consume the used service data alone, may now be used for processing the usage amount of the used service data, thereby improving the utilization rate of the fragmented service data.
Specifically, after the used service data is processed by the fragmented service data, the corresponding total service data may be modified according to the modification of the current value of the fragmented service data.
Specifically, when the fragment service data of another fragment service record corresponding to the same total service record as the target fragment service record is modified, the present invention may determine another fragment service record to be modified in advance according to a preset selection manner, for example: the fragmentation service data to be modified is determined according to the size of the fragmentation service data, and the smaller fragmentation service data can be determined as the fragmentation service data to be modified.
Specifically, when the current value of the total service data of the first service corresponding to the group identifier of the first group is smaller than the usage amount in the used service data, the present invention may reduce the total service data core of the first service to zero, and remind the user that the usage amount in the used service data of this time exceeds the total service data of the first service.
It should be noted that, when the current value of the total service data is not updated synchronously with the corresponding fragment service data, the query result of the total service data of the first service in step S30 cannot represent the sum of the current values of the corresponding fragment service data in real time. When the value of the query result of the total service data of the first service in step S30 is not less than the usage amount of the current used service data, and the sum of the current values of the actually corresponding fragment service data is less than the usage amount of the current used service data, the present invention may remind the user that the usage amount of the current used service data exceeds the total service data of the first service after the corresponding fragment service data is checked to be zero.
Optionally, step S80 may specifically be:
and performing second unlocking processing on the fragment service data recorded by the target fragment service.
Wherein the second unlocking process corresponds to the second locking process.
The method for managing service data provided by this embodiment can lock only the corresponding target fragment service record, and does not need to lock other fragment service records corresponding to the target fragment service record and having the same total service record.
Based on the steps shown in fig. 2, this embodiment further proposes another method for managing service data, as shown in fig. 3, the method may further include:
s90, modifying the current value of the total service data of the first service corresponding to the group identifier of the first group according to the modification of the current value of each fragment service data of the first service corresponding to the group identifier of the first group.
Specifically, the present invention can update the current value of the corresponding total service data according to the current value of the fragment service data in each fragment service record.
Optionally, the present invention may periodically update the current value of the corresponding total service data according to the current value of the fragment service data in each fragment service record, for example, every 1 day;
optionally, the present invention may update the current value of the corresponding total service data when the current values of the fragment service data in each fragment service record are all zero.
Optionally, the present invention may update the current value of the corresponding total service data according to the current value of the fragment service data in each fragment service record when the data resource is consumed by a certain value.
It should be noted that the specific time for updating the total service data according to the fragmented service data is not limited in the present invention.
It should be noted that, before updating the total service data of a certain total service record, the present invention may lock the total service data of the total service record, and after the update is completed, unlock the total service data of the total service record.
The method for managing the service data, provided by the embodiment, can determine the updating time of the total service record, and improve the quality of service data management.
Based on the steps shown in fig. 2, the present embodiment further proposes another method for managing service data, and the first device and the second device may be used to execute the steps in the method.
The first device may be a server device (e.g., a server), or may be an exchange or a base station. The second device may be a client device.
Optionally, when the first device is a server device and the second device is a client device, the scheme of the present invention is as follows:
step S10 may specifically include:
the method comprises the steps that client equipment obtains used service data of a first user;
the client device determining a group identifier of the first group to which the first user belongs, wherein the first group comprises a plurality of users;
and the client equipment sends a service record query request for the current value of the total service data of the first service corresponding to the group identifier of the first group to the server equipment.
Step S20 may specifically be:
and the server-side equipment determines the current value of the service data of the first service corresponding to the group identifier of the first group according to the received service record query request, and performs first locking processing on the service data of the first service corresponding to the group identifier of the first group.
Step S30 may specifically be:
and the server equipment returns the current value of the service data of the first service corresponding to the group identifier of the first group to the client equipment.
Step S40 may specifically be:
and the server-side equipment performs first unlocking processing on the service data of the first service corresponding to the group identifier of the first group.
Step S50 may specifically be:
the client device determines the usage amount of the first user in the used service data of the first service.
Step S60 may specifically include:
when the current value is not less than the usage amount in the used service data of the first service, the client device determines a target fragment service record to be updated from each fragment service record of the first service corresponding to the group identifier of the first group;
the client device sends the usage amount and the fragment identifier of the target fragment service record to the server device;
and the server side equipment performs second locking processing on the fragment service data recorded by the target fragment service according to the received fragment identifier recorded by the target fragment service.
Specifically, the fragment service record may further include a fragment identifier. The invention can uniquely determine a fragment service record according to a fragment identifier in each fragment service record corresponding to a total service record.
Specifically, the client device and the server device may determine the target fragment service record through the fragment identifier of the target fragment service record.
Step S70 may specifically be:
and the server side equipment modifies the current value of the fragment service data of the target fragment service record according to the usage amount.
Step S80 may specifically be:
and the server-side equipment performs second unlocking processing on the fragment service data recorded by the target fragment service.
It should be noted that, in this solution of the present invention, by concentrating the operation logic in the client device, the operation logic in the server device is reduced as much as possible, and thus the operation load of the server device can be reduced.
Optionally, in the management method of other service data provided in this embodiment, the present invention may also centralize the operation logic in the server device, and reduce the operation logic in the client device as much as possible, where the following scheme is adopted:
optionally, step S60 may specifically include:
the client equipment sends the usage amount and the group identification of the first group to the server equipment;
when the current value is not less than the usage amount in the used service data of the first service, the server device determines a target fragment service record to be updated from each fragment service record of the first service corresponding to the group identifier of the first group;
and the server-side equipment performs second locking processing on the fragment service data recorded by the target fragment service.
It should be noted that, in the present invention, the server device is used to replace the client device to execute the step of determining the target segment record, which may reduce some operation logics for the client device, thereby reducing the operation burden of the client device.
The method for managing the service data provided by the embodiment can centralize some operation logics in the client device, thereby reducing the operation burden of the server device; some operation logics can be centralized in the server-side equipment, and the operation burden of the client-side equipment is reduced.
Corresponding to the method shown in fig. 1, this embodiment proposes a service data management apparatus, as shown in fig. 4, a first device at least stores a service record of a first service, where the service record of the first service at least includes: the group identification and the service data of the first service correspond to the group identification, and the device comprises: a request obtaining unit 100, a first locking unit 200, a first obtaining unit 300, a first unlocking unit 400, a second obtaining unit 500, a second locking unit 600, a first modifying unit 700, and a second unlocking unit 800, wherein:
the request obtaining unit 100 is configured to obtain a service record query request, where the service record query request carries a group identifier of a first group;
the first device may be a server device (e.g., a server), or may be a switch or a base station. The first service may be a plurality of types of communication services. It will be appreciated that there may be a variety of types of traffic.
Wherein, a group may include a plurality of users, and the group may be an organization, and the like. The group identifier may be a unique identifier of the group, that is, the present invention may uniquely determine a group according to a group identifier. In practical applications, the group identifier may be composed of one or more of numbers, letters, symbols, and other characters, which is not limited in the present invention.
The service data may record group data resources in the corresponding service.
Specifically, the present invention may store the service record in a data table of a database of the first device.
Specifically, the first service may be a periodic service or a one-time service. Whether the service is a periodic service or a one-time service, when the first service subscribed by the first group is effective, service data corresponding to the first service and the first group in the data table is initialized to an initial value. The initial value may be a preset initial value of the first service.
Optionally, in the management device for other service data provided in this embodiment, the method may further include: a third obtaining unit and a second determining unit, wherein:
the third obtaining unit is configured to obtain used service data of the first user;
the second determining unit is configured to determine a group identifier of a first group to which the first user belongs, where the first group includes multiple users.
Specifically, when the first user uses a certain service, the present invention generates the used service data of the service correspondingly. The used service data is a data usage record generated after the first user uses a certain service.
Specifically, after the used service data is obtained, the group identifier of the first group to which the first user belongs may be determined according to the identity identifier of the first user.
Specifically, after determining the group identifier of the first group to which the first user belongs, the present invention may generate the service record query request according to the group identifier of the first group, so as to query the service data of the first service corresponding to the group identifier of the first group to which the first user belongs and the first service used by the first user.
The first locking unit 200 is configured to perform first locking processing on service data of a first service corresponding to the group identifier of the first group;
specifically, before obtaining the service data of the first service corresponding to the group identifier of the first group, the present invention needs to perform a first locking process on the service data in advance.
Specifically, the first locking processing can be performed on the service data of the service record through the first locking processing on the service record. The invention can use the existing scheme to perform the first locking processing on the business record.
The first obtaining unit 300 is configured to obtain a current value of service data of a first service corresponding to a group identifier of the first group;
the first unlocking unit 400 is configured to perform first unlocking processing on service data of a first service corresponding to the group identifier of the first group;
specifically, after the current value of the service data of the first service corresponding to the group identifier of the first group is obtained, the first unlocking processing may be performed on the service data without waiting until the service data completes the update of the used service data. Wherein the first unlocking process corresponds to the first locking process.
The second obtaining unit 500 is configured to obtain a usage amount of the first user in the used service data of the first service;
the second locking unit 600 is configured to perform a second locking process on the service data of the first service corresponding to the group identifier of the first group when the current value is not less than the usage amount in the used service data of the first service;
when the current value is smaller than the usage amount in the used service data of the first service, judging whether the group identifier of the first group to which the first user belongs corresponds to other services with the same type as the first service, and if so, inquiring the current value of the service data of the other services corresponding to the group identifier of the first group.
It should be noted that, when the current value is not less than the usage amount in the used service data of the first service, it is indicated that the service data of the first service corresponding to the group identifier of the first group may satisfy the processing of the used service data this time.
Specifically, the present invention may perform the second locking process on the service data of the first service corresponding to the group identifier of the first group before updating the service data of the first service.
The first modifying unit 700 is configured to modify, according to the usage amount, a current value of service data of a first service corresponding to the group identifier of the first group;
optionally, in the management apparatus for other service data provided in this embodiment, the first modifying unit 700 may be specifically configured to:
and when the current value of the service data of the first service corresponding to the group identifier of the first group is not less than the usage amount in the used service data of the first service, subtracting the usage amount in the used service data from the current value, and taking the calculation result as the current value of the service data of the first service corresponding to the group identifier of the first group.
Optionally, in the management apparatus for other service data provided in this embodiment, the first modifying unit 700 may also be specifically configured to:
and when the current value of the service data of the first service corresponding to the group identifier of the first group is not less than the usage amount in the used service data of the first service, reducing the current value core to zero, and taking the zero as the current value of the service data of the first service corresponding to the group identifier of the first group.
The second unlocking unit 800 is configured to perform a second unlocking process on the service data of the first service corresponding to the group identifier of the first group.
Wherein the second unlocking process corresponds to the second locking process.
Specifically, the present invention may modify the current value of the service data of the service record of the first service according to the usage amount, and then perform the second unlocking process. After the second unlocking processing is carried out, the unlocked service record can be used for processing other used service data.
The management device for the service data, which is provided by the embodiment, can effectively improve the processing efficiency of a plurality of data use records, and can lock the service records by the used service data obtained this time in the process of modifying the current values of the service data in the service records through the second locking process, so that the accuracy of the data is ensured, and the situations such as writing conflict are prevented.
Based on the apparatus shown in fig. 4, this embodiment proposes another apparatus for managing service data, as shown in fig. 5, the first device stores a summary table and a fragmentation table, where the summary table at least stores a total service record of the first service, and the total service record of the first service at least includes: the group identifier corresponds to the total service data of the first service, the fragment table at least includes a fragment service record group of the first service, the fragment service record group of the first service includes at least two fragment service records of the first service, and each fragment service record of the first service at least includes corresponding ones: the group identifier is equal to the initial value of the total service data of the first service corresponding to the group identifier of the first group.
The service record may be a total service record or a fragment service record.
The first locking unit 200 may be specifically configured to:
performing first locking processing on total service data of a first service corresponding to the group identifier of the first group;
specifically, the present invention may set a summary table and a fragment table in a database of the first device. The summary table and the fragment table can be data tables in the database.
Wherein, the total service data can record the group data resource in the corresponding service.
Wherein, the total table stores the total service data of at least one service of at least one group. Each total service record in the total table may include total service data of a group in a service. Specifically, each total service record may include the corresponding: group identification, service identification and total service data.
Each fragment service record group in the fragment table may correspond to one total service record in the total table. Specifically, the total service data in one total service record may be split to obtain a plurality of fragment service data, each fragment service data obtained by splitting may be located in one fragment service record, and the fragment service record in which the plurality of fragment service data are obtained by splitting forms one fragment service record group corresponding to the total service record. Specifically, after adding, the data of each fragment service in a fragment service record group may be equal to the total service data in the total service record corresponding to the fragment service record group. Of course, similar to the general table, the fragment table may also store the service identifier, and the service identifier is not necessarily in the fragment table.
Optionally, the total service record in the total table may further include a total record identifier, and the total record identifier in each total service record may be different. The master record identification may be a primary key in the master table.
Optionally, the fragment service record in the fragment table may further include a fragment record identifier, and the fragment record identifiers in the fragment service records may be different. The fragment record identifier may be a primary key in the fragment table.
In practical application, when a certain group subscribes to a service, the invention can correspondingly establish a total service record to record the relevant information of the service subscribed by the group.
Specifically, after the used service data of the user is obtained, the present invention may perform the first locking process according to the total service data of the first service corresponding to the group identifier of the first group to which the user belongs.
The first obtaining unit 300 may specifically be configured to:
obtaining a current value of total service data of a first service corresponding to the group identifier of the first group;
the first unlocking unit 400 may be specifically configured to:
and performing first unlocking processing on the total service data of the first service corresponding to the group identifier of the first group.
The second locking unit 600 may specifically include: a first determining unit 610 and a locking processing unit 620, wherein:
the first determining unit 610 is configured to determine, when the current value is not less than the usage amount in the used service data of the first service, a target fragment service record to be updated from each fragment service record of the first service corresponding to the group identifier of the first group;
when the current value is smaller than the usage amount in the used service data of the first service, judging whether the group identifier of the first group to which the first user belongs corresponds to other services with the same type as the first service, and if so, inquiring the current value of the total service data of the other services corresponding to the group identifier of the first group.
And when the current value is not less than the usage amount in the used service data of the first service, the total service data of the first service corresponding to the group identifier of the first group can meet the processing of the used service data. When one used service data is processed each time, only part of the fragment service records need to be locked, and all the fragment service records and the total service records do not need to be locked, so that a plurality of used service data can be processed at the same time, and the processing efficiency is higher.
The locking processing unit 620 is configured to perform second locking processing on the fragment service data recorded by the target fragment service;
specifically, the present invention may only perform the second locking processing on the target fragment service record that needs to be updated, and does not need to perform the second locking processing on the total service record corresponding to the target fragment service record and other fragment service records in the total service record. When the current value of the fragment service data in the target fragment service record is smaller than the usage amount in the used service data and other fragment service records need to be updated according to the usage amount in the used service data, the invention also performs second locking processing on other fragment service records needing to be updated.
The first modifying unit 700 may be specifically configured to:
modifying the current value of the fragment service data in the target fragment service record according to the usage amount;
optionally, in the management apparatus for other service data provided in this embodiment, the first modifying unit 700 may be specifically configured to:
determining whether the current value of the fragment service data in the target fragment service record is not less than the usage amount in the used service data, if so, subtracting the usage amount in the used service data from the current value of the fragment service data in the target fragment service record, and taking the calculation result as the current value of the fragment service data in the target fragment service record;
otherwise, modifying the current value of the fragment service data in the target fragment service record to 0, and modifying the current values of other fragment service data of the first service corresponding to the group identifier of the first group, so that the sum of the current modification amount of the current value of the fragment service data in the target fragment service record and the current modification amount of the current value of the other fragment service data is equal to the usage amount in the used service data.
It should be noted that, when the fragment service record is in a fragment state, that is, the value of the fragment service data in the fragment service record is smaller than the minimum data consumption unit that can be used to process the usage amount of the used service data, the fragment service data in the fragment service record cannot be used to consume the usage amount of the used service data. To this end, optionally, in the management device for other service data provided in this embodiment, the method may further include: a data concentration unit, the data concentration unit operable to:
and concentrating the first sliced service data with the current value smaller than the preset allowable threshold value into second sliced service data, wherein the first sliced service data and the second sliced service data belong to the same service and correspond to the same group identifier.
The preset allowable threshold may be a minimum data consumption unit of an amount of usage of the fragmented service data for processing the used service data. Of course, the preset allowable threshold may also be determined by a technician according to the actual situation, and the present invention is not limited thereto.
Optionally, the data concentration unit may also be configured to: and concentrating part or all of the fragmented service data of the second fragmented service data into the first fragmented service data of which the current value is smaller than a preset allowable threshold value.
Specifically, after the used service data is processed by the fragmented service data, the corresponding total service data may be modified according to the modification of the current value of the fragmented service data.
The second unlocking unit 800 is specifically configured to:
and performing second unlocking processing on the fragment service data recorded by the target fragment service.
Wherein the second unlocking process corresponds to the second locking process.
The service data management device provided in this embodiment may lock only the corresponding target fragment service record, but does not lock other fragment service records corresponding to the same total service record as the target fragment service record.
Based on the apparatus shown in fig. 5, this embodiment further proposes another apparatus for managing service data, and as shown in fig. 6, the apparatus may further include: a second modifying unit 900, the second modifying unit 900 may be configured to:
and modifying the current value of the total service data of the first service corresponding to the group identifier of the first group according to the modification of the current value of each fragment service data of the first service corresponding to the group identifier of the first group.
Specifically, the present invention may update the current value of the corresponding total service data according to the current value of the fragment service data in each fragment service record. It should be noted that the specific time for updating the total service data according to the fragmented service data is not limited in the present invention.
It should be noted that, in the present invention, before updating the total service data of a certain total service record, the total service data of the total service record may be locked, and after the update is finished, the total service data of the total service record may be unlocked.
The management device for the service data provided by this embodiment can determine the update time of the total service record, and improve the management quality of the service data.
Corresponding to the method shown in fig. 2, the present embodiment further provides another service data management apparatus, which can use the first device and the second device to perform the relevant process.
The first device may be a server device (e.g., a server), or may be a switch or a base station. The second device may be a client device.
Optionally, when the first device is a server device and the second device is a client device, the scheme of the present invention is as follows:
the method comprises the steps that client equipment obtains used service data of a first user;
and the server-side equipment determines the current value of the service data of the first service corresponding to the group identifier of the first group according to the received service record query request, and performs first locking processing on the service data of the first service corresponding to the group identifier of the first group.
And the server equipment returns the current value of the service data of the first service corresponding to the group identifier of the first group to the client equipment.
And the server-side equipment performs first unlocking processing on the service data of the first service corresponding to the group identifier of the first group.
The client device determines the usage amount of the first user in the used service data of the first service.
When the current value is not less than the usage amount in the used service data of the first service, the client device determines a target fragment service record to be updated from each fragment service record of the first service corresponding to the group identifier of the first group;
the client device sends the usage amount and the fragment identifier of the target fragment service record to the server device;
and the server-side equipment performs second locking processing on the fragment service data recorded by the target fragment service according to the received fragment identifier of the target fragment service record.
And the server-side equipment modifies the current value of the fragment service data of the target fragment service record according to the usage amount.
And the server-side equipment carries out second unlocking processing on the fragment service data recorded by the target fragment service.
Specifically, the fragment service record may further include a fragment identifier. The invention can uniquely determine a piece of fragment service record according to a fragment identifier in each fragment service record corresponding to a total service record.
Specifically, the client device and the server device may determine the target fragment service record through the fragment identifier of the target fragment service record.
It should be noted that, in this solution of the present invention, by concentrating the operation logic in the client device, the operation logic in the server device is reduced as much as possible, and thus the operation load of the server device can be reduced.
Optionally, in the management apparatus for other service data provided in this embodiment, the present invention may also centralize the operation logic in the server device, and reduce the operation logic in the client device as much as possible, where the following scheme is adopted:
when the current value is not less than the usage amount in the used service data of the first service, the client device determines a target fragment service record to be updated from each fragment service record of the first service corresponding to the group identifier of the first group, the client device sends the usage amount and the fragment identifier of the target fragment service record to the server device, and the server device performs second locking processing on the fragment service data of the target fragment service record according to the received fragment identifier of the target fragment service record, which may be specifically set as:
the client equipment sends the usage amount and the group identification of the first group to the server equipment;
when the current value is not less than the usage amount in the used service data of the first service, the server device determines a target fragment service record to be updated from each fragment service record of the first service corresponding to the group identifier of the first group;
and the server-side equipment performs second locking processing on the fragment service data recorded by the target fragment service.
It should be noted that, in the present invention, the server device is used to replace the client device to execute the determination process on the target fragment record, which may reduce some operation logics for the client device, thereby reducing the operation burden of the client device.
The management device for the service data provided by this embodiment can centralize some operation logics in the client device, thereby reducing the operation burden of the server device; some operation logics can be centralized in the server-side equipment, and the operation burden of the client-side equipment is reduced.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrases "comprising a," "8230," "8230," or "comprising" does not exclude the presence of additional identical elements in the process, method, article, or apparatus comprising the element.
The above are merely examples of the present application and are not intended to limit the present application. Various modifications and changes may occur to those skilled in the art to which the present application pertains. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims (10)

1. A method for managing service data is characterized in that a first device at least stores a service record of a first service, and the service record of the first service at least comprises: a group identifier and service data of the first service, wherein the group identifier corresponds to the service data of the first service, and the method comprises the following steps:
acquiring a service record query request, wherein the service record query request carries a group identifier of a first group;
performing first locking processing on service data of a first service corresponding to the group identifier of the first group;
obtaining a current value of service data of a first service corresponding to the group identifier of the first group;
performing first unlocking processing on service data of a first service corresponding to the group identifier of the first group;
obtaining the usage amount of a first user in the used service data of the first service;
when the current value is not less than the usage amount in the used service data of the first service, performing second locking processing on the service data of the first service corresponding to the group identifier of the first group;
modifying the current value of the service data of the first service corresponding to the group identifier of the first group according to the usage amount;
and performing second unlocking processing on the service data of the first service corresponding to the group identifier of the first group.
2. The method according to claim 1, wherein the first device maintains a summary table, and the summary table at least maintains a total service record of the first service, and the total service record of the first service at least includes: a group identifier corresponding to total service data of the first service, and total service data of the first service,
the performing a first locking process on the service data of the first service corresponding to the group identifier of the first group includes:
performing first locking processing on total service data of a first service corresponding to the group identifier of the first group;
the obtaining of the current value of the service data of the first service corresponding to the group identifier of the first group includes:
obtaining a current value of total service data of a first service corresponding to the group identifier of the first group;
the performing of the first unlocking process on the service data of the first service corresponding to the group identifier of the first group includes:
and performing first unlocking processing on the total service data of the first service corresponding to the group identifier of the first group.
3. The method according to claim 2, wherein the first device further maintains a fragmentation table, the fragmentation table at least includes a fragmentation service record group of the first service, the fragmentation service record group of the first service includes at least two fragmentation service records of the first service, and each fragmentation service record of the first service at least includes a corresponding one: the group identifier and the fragment service data of the first service, the initial value of each fragment service data of the first service corresponding to the group identifier of the first group is equal to the initial value of the total service data of the first service corresponding to the group identifier of the first group,
when the current value is not less than the usage amount in the used service data of the first service, performing a second locking process on the service data of the first service corresponding to the group identifier of the first group, including:
when the current value is not less than the usage amount in the used service data of the first service, determining a target fragment service record to be updated from each fragment service record of the first service corresponding to the group identifier of the first group;
performing second locking processing on the fragment service data recorded by the target fragment service;
the modifying, according to the usage amount, the current value of the service data of the first service corresponding to the group identifier of the first group includes:
modifying the current value of the fragment service data in the target fragment service record according to the usage amount;
the second unlocking processing is performed on the service data of the first service corresponding to the group identifier of the first group, and includes:
and carrying out second unlocking processing on the fragment service data recorded by the target fragment service.
4. The method of claim 3, further comprising:
and modifying the current value of the total service data of the first service corresponding to the group identifier of the first group according to the modification of the current value of each fragment service data of the first service corresponding to the group identifier of the first group.
5. The method according to claim 3, wherein said modifying the current value of the fragment service data in the target fragment service record according to the usage amount comprises:
determining whether the current value of the fragment service data in the target fragment service record is not less than the usage amount in the used service data, if so, subtracting the usage amount in the used service data from the current value of the fragment service data in the target fragment service record, and taking the calculation result as the current value of the fragment service data in the target fragment service record;
otherwise, modifying the current value of the fragment service data in the target fragment service record to 0, and modifying the current values of other fragment service data of the first service corresponding to the group identifier of the first group, so that the sum of the current modifier of the current value of the fragment service data in the target fragment service record and the current modifier of the current values of other fragment service data is equal to the usage in the used service data.
6. A service data management apparatus, wherein a first device at least stores a service record of a first service, and the service record of the first service at least includes: a group identifier and service data of the first service, wherein the group identifier corresponds to the service data of the first service, and the apparatus comprises: the device comprises a request obtaining unit, a first locking unit, a first obtaining unit, a first unlocking unit, a second obtaining unit, a second locking unit, a first modifying unit and a second unlocking unit, wherein:
the request obtaining unit is configured to obtain a service record query request, where the service record query request carries a group identifier of a first group;
the first locking unit is configured to perform first locking processing on service data of a first service corresponding to the group identifier of the first group;
the first obtaining unit is configured to obtain a current value of service data of a first service corresponding to the group identifier of the first group;
the first unlocking unit is used for performing first unlocking processing on the service data of the first service corresponding to the group identifier of the first group;
the second obtaining unit is configured to obtain a usage amount of the first user in the used service data of the first service;
the second locking unit is configured to perform second locking processing on the service data of the first service corresponding to the group identifier of the first group when the current value is not less than the usage amount in the used service data of the first service;
the first modifying unit is configured to modify, according to the usage amount, a current value of service data of a first service corresponding to the group identifier of the first group;
the second unlocking unit is configured to perform second unlocking processing on the service data of the first service corresponding to the group identifier of the first group.
7. The apparatus according to claim 6, wherein the first device maintains a summary table, and the summary table at least maintains a total service record of the first service, and the total service record of the first service at least includes: a group identifier corresponding to total service data of the first service, and total service data of the first service,
the first locking unit is specifically configured to:
performing first locking processing on total service data of a first service corresponding to the group identifier of the first group;
the first obtaining unit is specifically configured to:
obtaining a current value of total service data of a first service corresponding to the group identifier of the first group;
the first unlocking unit is specifically configured to:
and performing first unlocking processing on the total service data of the first service corresponding to the group identifier of the first group.
8. The apparatus according to claim 7, wherein the first device further maintains a fragment table, the fragment table at least includes a fragment service record group of the first service, the fragment service record group of the first service includes at least two fragment service records of the first service, and each fragment service record of the first service at least includes a corresponding one: the group identifier and the fragment service data of the first service, the initial value of each fragment service data of the first service corresponding to the group identifier of the first group is equal to the initial value of the total service data of the first service corresponding to the group identifier of the first group,
the second locking unit specifically includes: a first determination unit and a locking processing unit, wherein:
the first determining unit is configured to determine, when the current value is not less than the usage amount in the used service data of the first service, a target fragment service record to be updated from each fragment service record of the first service corresponding to the group identifier of the first group;
the locking processing unit is used for carrying out second locking processing on the fragment service data recorded by the target fragment service;
the first modifying unit is specifically configured to:
modifying the current value of the fragment service data in the target fragment service record according to the usage amount;
the second unlocking unit is specifically configured to:
and performing second unlocking processing on the fragment service data recorded by the target fragment service.
9. The apparatus of claim 8, further comprising: a second modification unit to:
and modifying the current value of the total service data of the first service corresponding to the group identifier of the first group according to the modification of the current value of each fragment service data of the first service corresponding to the group identifier of the first group.
10. The apparatus according to claim 8, wherein the first modification unit is specifically configured to:
determining whether the current value of the fragment service data in the target fragment service record is not less than the usage amount in the used service data, if so, subtracting the usage amount in the used service data from the current value of the fragment service data in the target fragment service record, and taking the calculation result as the current value of the fragment service data in the target fragment service record;
otherwise, modifying the current value of the fragment service data in the target fragment service record to 0, and modifying the current values of other fragment service data of the first service corresponding to the group identifier of the first group, so that the sum of the current modification amount of the current value of the fragment service data in the target fragment service record and the current modification amount of the current value of the other fragment service data is equal to the usage amount in the used service data.
CN202010382498.8A 2020-05-08 2020-05-08 Service data management method and device Active CN113630263B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010382498.8A CN113630263B (en) 2020-05-08 2020-05-08 Service data management method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010382498.8A CN113630263B (en) 2020-05-08 2020-05-08 Service data management method and device

Publications (2)

Publication Number Publication Date
CN113630263A CN113630263A (en) 2021-11-09
CN113630263B true CN113630263B (en) 2023-04-14

Family

ID=78377225

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010382498.8A Active CN113630263B (en) 2020-05-08 2020-05-08 Service data management method and device

Country Status (1)

Country Link
CN (1) CN113630263B (en)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105208571A (en) * 2015-08-11 2015-12-30 北京奇虎科技有限公司 Calibration method and device for utilization amount of communication service
CN105813047A (en) * 2014-12-31 2016-07-27 中国移动通信集团吉林有限公司 Flow regulation and control method, device and system
CN106250487A (en) * 2016-07-29 2016-12-21 杭州华三通信技术有限公司 A kind of database concurrency control method and device
WO2017161522A1 (en) * 2016-03-23 2017-09-28 华为技术有限公司 Method, apparatus and system for collecting statistics of amount of flow usage
CN107635219A (en) * 2017-09-30 2018-01-26 中国联合网络通信集团有限公司 Service package sharing method and device
CN108881043A (en) * 2018-05-18 2018-11-23 中国联合网络通信集团有限公司 Distribution method, device, equipment and the storage medium of portfolio in shared set meal

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105813047A (en) * 2014-12-31 2016-07-27 中国移动通信集团吉林有限公司 Flow regulation and control method, device and system
CN105208571A (en) * 2015-08-11 2015-12-30 北京奇虎科技有限公司 Calibration method and device for utilization amount of communication service
WO2017161522A1 (en) * 2016-03-23 2017-09-28 华为技术有限公司 Method, apparatus and system for collecting statistics of amount of flow usage
CN106250487A (en) * 2016-07-29 2016-12-21 杭州华三通信技术有限公司 A kind of database concurrency control method and device
CN107635219A (en) * 2017-09-30 2018-01-26 中国联合网络通信集团有限公司 Service package sharing method and device
CN108881043A (en) * 2018-05-18 2018-11-23 中国联合网络通信集团有限公司 Distribution method, device, equipment and the storage medium of portfolio in shared set meal

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
张朝贵.基于一体化网络的分布式流量分析系统的设计与实现.《中国优秀硕士学位论文全文数据库》.2015,全文. *

Also Published As

Publication number Publication date
CN113630263A (en) 2021-11-09

Similar Documents

Publication Publication Date Title
US20180359200A1 (en) System and method for facilitating the growth of a mobile community
US7882245B2 (en) Presence service access device, presence service system and method for publishing and acquiring presence information
CN101771723A (en) Data synchronization method
CN107659739B (en) List distribution method and device
CN105282328A (en) Method and device for task prompting during communication
CN102202060A (en) Method for importing group members
CN107276970A (en) One kind is unbinded, binding method and device
CN107870982A (en) Data processing method, system and computer-readable recording medium
CN107277188B (en) Method, client, server and service system for determining IP address attribution information
CN108881500B (en) Configuration method and configuration device of domain name protection system
CN101778131A (en) Data synchronization system
US7133913B2 (en) Information routing
CN113630263B (en) Service data management method and device
CN108632078B (en) Configuration acquisition method
CN101742394B (en) Electronic work order priority level adjustment method and electronic work order executing method and device
CN107656943B (en) Task query method and server
CN113630432A (en) Service data management method and device
CN110659271A (en) Data deletion optimization method and terminal
CN108076130B (en) Cross-platform user management method and device for mobile Internet
CN112636959B (en) Network slice privacy number service guarantee system and method for distinguishing service types
CN110310145B (en) Product multi-dimensional configuration method, device, computer equipment and storage medium
CN111815339B (en) Marketing information pushing method and device
CN107690037B (en) List distribution method and device
CN100490480C (en) Method for processing user identification alternation
CN113452558B (en) Service processing method, device and system

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
GR01 Patent grant
GR01 Patent grant