CN116523526B - Client group information updating method and device, terminal equipment and storage medium - Google Patents
Client group information updating method and device, terminal equipment and storage medium Download PDFInfo
- Publication number
- CN116523526B CN116523526B CN202310786666.3A CN202310786666A CN116523526B CN 116523526 B CN116523526 B CN 116523526B CN 202310786666 A CN202310786666 A CN 202310786666A CN 116523526 B CN116523526 B CN 116523526B
- Authority
- CN
- China
- Prior art keywords
- updating
- information
- client group
- tag set
- client
- 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
Links
- 238000000034 method Methods 0.000 title claims abstract description 41
- 238000004590 computer program Methods 0.000 claims description 12
- 238000012216 screening Methods 0.000 claims description 4
- 238000012545 processing Methods 0.000 abstract description 6
- 238000010586 diagram Methods 0.000 description 10
- 230000006870 function Effects 0.000 description 8
- 239000002699 waste material Substances 0.000 description 5
- 230000008859 change Effects 0.000 description 4
- 230000008569 process Effects 0.000 description 4
- 150000001875 compounds Chemical class 0.000 description 3
- 230000032683 aging Effects 0.000 description 2
- 239000002131 composite material Substances 0.000 description 2
- 230000001419 dependent effect Effects 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004140 cleaning Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000008676 import Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/01—Customer relationship services
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/02—Banking, e.g. interest calculation or account maintenance
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The application relates to the technical field of data processing, and provides a client group information updating method, a device, terminal equipment and a storage medium, wherein the method comprises the following steps: when the updating of the client group information is detected, judging whether the client group definition is changed or not; wherein the customer base is defined as a logical combination of at least one tag rule; if not, comparing the label set updating information in the label set with the client group definition updating information in the client group definition table; the tag set comprises a tag set table for storing tags of the same category; the client group definition update information includes first update information; if the first updating information is in the history information of the tag set updating information, updating a client group list; wherein the client group list comprises a client group definition to which each client belongs and the client group definition updating information. The embodiment of the application can effectively solve the problems of invalid update, slow update and the like.
Description
Technical Field
The present application relates to the field of data processing technologies, and in particular, to a method and apparatus for updating client group information, a terminal device, and a storage medium.
Background
In the prior art, the basic steps of client group definition generation are as follows: s1, pulling full user data from a plurality of bins; s2, cleaning the user label according to service requirements; s3, screening out target customer group definitions through logical combination of user tags. In the step of generating the customer group definition, the existing scheme has the following problems: 1. at present, most of the updating of the client group definition is timed updating, whether the bottom label is changed is not concerned, and the client group definition updating task executed regularly can cause invalid updating of the client group definition. 2. The guarantee of timeliness of the customer group definition is only dependent on the update frequency of the customer group definition, and the method for improving the timeliness of the customer group definition can cause a great amount of resource waste under the condition that the update frequency of the tag data is not high. When the magnitude of the client group definition is relatively large, the improvement of the update frequency of the client group definition can quickly reach the bottleneck. In an emergency, after the bottom label is updated, the customer group definition needs to be updated until the next task execution time or manual intervention. 3. The update of the client group definition needs to delete or replace the original client group definition, so that the client group definition is unavailable for a short time in the process of changing the client group definition, and the client experience is affected.
Disclosure of Invention
In view of the above, in order to solve at least one of the above problems, an embodiment of the present application provides a method, an apparatus, a terminal device, and a storage medium for updating customer group information, which can effectively solve the problems of invalid update, slow update, and the like.
In a first aspect, an embodiment of the present application provides a method for updating client group information, including:
when the updating of the client group information is detected, judging whether the client group definition in the client group definition table is changed or not;
if not, comparing the label set updating information in the label set with the client group definition updating information in the client group definition table; wherein the customer base is defined as a logical combination of at least one tag rule; the tag set comprises a tag set table for storing tags of the same category; the client group definition update information includes first update information;
if the first updating information is in the history information of the tag set updating information, updating a client group list; the client group list comprises client group definitions of each client and client group definition updating information, and the history information of the tag set updating information is updated information after the latest updating information of the tag set updating information is removed.
In some embodiments, the tag set update information is a data version of the tag set;
the client group definition updating information is a data version defined by the client group;
and if the first updating information is in the history information of the tag set updating information, updating the first updating information into the tag set updating information.
In some embodiments, the tag set further includes a tag set data state table corresponding to each of the tag set tables; the data version of the tag set is stored in the tag set data state table; before comparing the label set update information in the label set with the client group definition update information in the client group definition table, the method further comprises:
judging whether the numerical value of the tag rule in the tag set is updated or not;
if yes, screening the customer group definition to be updated according to the updated numerical value of the label rule, and recording the update information of the customer group definition corresponding to the current customer group definition;
and acquiring a corresponding tag set table according to the tag corresponding to the client group definition to be updated, and polling the tag set data state table corresponding to the tag set table.
In some embodiments, the data version of the tag set is a combination of the tag set update time and an N-bit increment integer;
the data version defined by the client group is a combination of a historical data version of the tag set and an M-bit increment integer.
In some embodiments, if the first update information is in the history information of the tag set update information, updating the client group list includes:
judging whether the data version defined by the client group is in a historical version of the data version of the tag set or not;
if yes, updating the client group definition to which each client belongs, and updating the first updating information into the data version of the current tag set.
In some embodiments, after determining whether the client group definition is changed, the method further includes:
and if so, updating the client group list according to the client group definition.
In some embodiments, the updating the customer group detail table includes:
updating the client group definition to which each client belongs, and adding 1 to the M-bit increment integer of the data version of the currently recorded client group definition.
In a second aspect, an embodiment of the present application provides a client group information updating apparatus, including:
the judging module is used for judging whether the client group definition in the client group definition table is changed or not when the update of the client group information is detected;
the comparison module is used for comparing the label set updating information in the label set with the client group definition updating information in the client group definition table if not; wherein the customer base is defined as a logical combination of at least one tag rule; the tag set comprises a tag set table for storing tags of the same category; the client group definition update information includes first update information;
the updating module is used for updating the client group list if the first updating information is in the history information of the tag set updating information; the client group list comprises client group definitions of each client and client group definition updating information, and the history information of the tag set updating information is updated information after the latest updating information of the tag set updating information is removed.
In a third aspect, an embodiment of the present application provides a terminal device, where the terminal device includes a processor and a memory, where the memory stores a computer program, and the processor is configured to execute the computer program to implement the client group information updating method described above.
In a fourth aspect, an embodiment of the present application provides a readable storage medium storing a computer program which, when executed on a processor, implements a client group information updating method according to the above.
The embodiment of the application has the following beneficial effects: in the embodiment of the application, when the client group information is updated, whether the client group definition is changed is judged firstly, if not, whether the numerical value of the tag rule in the tag set is changed is further judged, if so, the tag set updating information in the tag set is compared with the client group definition updating information in the client group definition table, and if the first updating information is in the history information of the tag set updating information, the client group detail table is updated. When the client group information is updated, the change condition of the bottom layer label is considered, the thought of updating the client group information is not active unconditional updating any more, and the client group information is updated only when the client group definition is updated and the numerical value updating state of the label rule is judged, so that the resource waste of unconditional updating of the client group with unchanged label is avoided.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the embodiments will be briefly described below, it being understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and other related drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a schematic flow chart of a client group information updating method according to an embodiment of the application;
FIG. 2 is a schematic diagram of a change of a data version defined by a client group according to an embodiment of the present application;
FIG. 3 is a schematic diagram illustrating a second flow chart of a client group information update method according to an embodiment of the present application;
fig. 4 is a schematic diagram illustrating a third flow chart of a client group information updating method according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of a client group information updating apparatus according to an embodiment of the application.
Detailed Description
The following description of the embodiments of the present application will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present application, but not all embodiments.
The components of the embodiments of the present application generally described and illustrated in the figures herein may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of the application, as presented in the figures, is not intended to limit the scope of the application, as claimed, but is merely representative of selected embodiments of the application. All other embodiments, which can be made by a person skilled in the art without making any inventive effort, are intended to be within the scope of the present application.
The terms "comprises," "comprising," "including," or any other variation thereof, are intended to cover a specific feature, number, step, operation, element, component, or combination of the foregoing, which may be used in various embodiments of the present application, and are not intended to first exclude the presence of or increase the likelihood of one or more other features, numbers, steps, operations, elements, components, or combinations of the foregoing. Furthermore, the terms "first," "second," "third," and the like are used merely to distinguish between descriptions and should not be construed as indicating or implying relative importance.
Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which various embodiments of the application belong. The terms (such as those defined in commonly used dictionaries) will be interpreted as having a meaning that is the same as the context of the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein in connection with the various embodiments of the application.
Some embodiments of the present application are described in detail below with reference to the accompanying drawings. The embodiments described below and features of the embodiments may be combined with each other without conflict.
In the prior art, in the process of updating the customer group definition, whether the underlying label is changed is not usually concerned, but a timing updating mode is simply adopted, so that invalid updating of the customer group is often caused. In addition, the guarantee of timeliness of the customer group definition is only dependent on the update frequency of the customer group information, and the method for improving the timeliness of the customer group can cause a great amount of resource waste under the condition that the update frequency of the tag data is not high. When the definition magnitude of the client group is relatively large, the updating frequency of the client group information can be improved to reach the bottleneck quickly. In an emergency, after the bottom label is updated, the client group needs to wait until the next task execution time or manual intervention.
Therefore, the embodiment of the application provides a method, a device, a terminal device and a storage medium for updating customer group information, wherein when the customer group information is updated, whether the customer group definition is changed is judged firstly, if not, whether the numerical value of a tag rule in a tag set is changed is further judged, if so, the tag set updating information in the tag set is compared with the customer group definition updating information in a customer group definition table, and if the first updating information is in the history information of the tag set updating information, the customer group detail table is updated. When the client group information is updated, the change condition of the bottom layer label is considered, the thought of updating the client group information is not active unconditional updating any more, and the client group information is updated only when the client group definition is updated and the numerical value updating state of the label rule is judged, so that the resource waste of unconditional updating of the client group with unchanged label is avoided.
Before the embodiments, the terms involved in the embodiments of the present application will be explained first.
Customer group definition: i.e. a consumer group or customer group corresponding to a certain market, such as a customer group corresponding to a certain investment product, a customer group corresponding to a certain financial product, a consumer group corresponding to a certain high-end vehicle, etc.
And (3) tag: refers to a description of a characteristic such as age, gender, deposit amount, credit amount, fixed asset, etc.
Wherein the customer base is defined as a logical combination of at least one tag rule.
Wherein the tag rule is a constraint of the tag, such as age >30, sex male, deposit >1000 ten thousand, etc.
The logical combination of the tag rules may be at least one composite tag rule and/or at least one single tag rule, wherein the composite tag rule is a logical combination of a plurality of single tag rules, and the single tag rule is the above-mentioned age >30, sex is male, deposit >1000 ten thousand, etc. For example, the label rule is A, B, C, D, E, and the compound label rule may be A and B, A or C, A and B and D, and the like. If the logical combination of the label rules is a logical relationship between at least one compound label rule and at least one single label rule, the logical combination can be (A and B) or C, (A or C) and E, etc.; the logical combination of the tag rules may be a logical relationship between at least one compound tag rule or at least one single tag rule, which may be a and B, (a or C) and E, D, E, etc.
The customer group definition may be (A and B) or C, (A or C) and E, D, A and D, etc.
For example, a is an age >30, B is a deposit >200 ten thousand, C is a loan <50 ten thousand, and then an age >30 and deposit >200 ten thousand and loan <50 ten thousand is a customer group of a financial product, that is, a customer group meeting the conditions of an age >30 and deposit >200 ten thousand and loan <50 ten thousand is considered as a financial product.
The label set classifies labels according to service functions, each classified label is called a label set, and the label set table with the same service attribute is stored in each label set. Such as business functions may be categorized by loan business, deposit business, etc. Taking the deposit label set as an example, the deposit label set comprises deposit more than 1 and deposit less than 10, deposit more than 10 and deposit less than 50 ten thousand and deposit more than 50 ten thousand.
Deposit label collection table
Further, it is explained that the embodiment of the present application may specifically implement a client group information updating method based on a client group information updating system, where the client group information updating system includes, but is not limited to, an operation interface, a tag storage unit, and a data source unit, where the operation interface is mainly used for tag definition, tag modification, client group definition, and the like, the tag storage unit is mainly used for tag storage, client group judgment, client group update, and the like, and the data source unit is mainly used for tag classification, data import, data synchronization, and the like. In short, the operation interface is an input interface used by a user, and operations such as label definition, customer group definition, modification and the like can be performed in the operation interface, when the data operated by the user in the operation interface is stored in the label storage unit, the data source module is used for providing big data. The above only enumerates some functional modules of the client group information updating system, and other functional modules may be further provided as needed in the specific use process, which are not enumerated here.
The method for updating the customer base information will be described with reference to specific embodiments.
Fig. 1 is a schematic flow chart of a client group information updating method according to an embodiment of the application. The client group information updating method comprises the following steps:
step S100, when the update of the client group information is detected, judging whether the client group definition in the client group definition table is changed or not; wherein the customer base is defined as a logical combination of at least one tag rule.
In this step, when the update of the client group information of the tag storage unit is detected, it is first determined whether the user modifies the client group definition in the client group definition table through the operation interface, and if the user modifies the client group definition, the client group definition table is updated according to the client group definition, that is, the client group definition to which each client belongs is updated (the client group definition table update is updated according to the latest client group definition), and the M-bit increment integer of the data version of the currently recorded client group definition is increased by 1. The client group list comprises client group definitions and client group definition updating information of each client, and further, the client group definition updating information is a data version of the client group definition.
An example table of customer group details is as follows:
the client group to which the client X belongs in the client group list example list is defined as "(A and B) or C", and the corresponding client group definition updating information is "2023052600000"; the client group to which the client Y belongs is defined as "a and E", and the corresponding client group defines update information as "2023052603002".
Step S200, if not, comparing the label set updating information in the label set with the client group definition updating information in the client group definition table.
If the client group definition is not changed and the client group information is updated, comparing the tag set updating information in the tag set with the client group definition updating information in the client group definition table, wherein the tag set comprises a tag set table for storing tags of the same category; each customer group definition corresponds to at least one label set table, and each label set table is that a data source unit classifies labels according to service functions first, and each type of label forms one label set table.
If the customer group is defined as deposit >200 ten thousand and loan <50 ten thousand, the customer group definition corresponds to two tag set tables, one is a deposit tag set table and one is a loan tag set table.
Further, the client group definition update information includes first update information and second update information. The first update information is updated according to the update of the tag set update information, the second update information is updated according to the change of the client group definition, and the second update information is that M bits increment integers. If the client group defines a plurality of tag set tables, the first update information is updated according to the latest tag set update information among the plurality of tag set update information.
Further, the tag set update information is a data version of the tag set. Further, a tag set data state table corresponding to each tag set table; the data version of the tag set is stored in a tag set data state table. Wherein the tag set data state table includes table name, updated state (whether the update is complete), data version of the tag set, and update time.
The following describes the defined logical relationship of the data version of the tag set of the data source unit and the data version defined by the client group of the tag storage unit.
The data version of the tag set is a combination of the tag set update time and an N-bit increment integer.
Specifically, N is greater than or equal to 2, taking N as an example and taking the combination of year and date as the update time of the tag set as defined by the combination of year and date, if the data version of a certain tag set table (deposit tag set table) starts at 26 days of 5 months of 2023, the data version of the tag set is 2023052600, if multiple updates on the same day increment by two-digit integers, that is, update on the basis of the version 2023052600, the data version of the tag set is 2023052601, and after the data is completely updated, the record state is modified to complete the update. The tag set data state table corresponding to the deposit tag set table is as follows:
the tag set data state table corresponding to the deposit tag set table is as follows:
the data version defined by the client group is a combination of a historical data version of the tag set and an M-bit increment integer.
As shown in fig. 2, specifically, taking M being 3 as an example, the data version of the customer group definition is the data version of the tag set+three-bit increment integer (increment from 000), the data version 2023052600000 of the customer group definition corresponding to the beginning version 2023052600 in the tag set data status table corresponding to the deposit tag set table, if the data version of the tag set is updated, the data version of the corresponding customer group definition also needs to be updated, if the data version of the tag set is updated from 2023052600 to 2023052601, the data version of the customer group definition is also updated to 2023052601000 (the last three bits are not updated with the update of the data version of the tag set), and if the data version of the customer group definition is changed at this time, the last three-bit increment of the data version of the customer group definition is 2023052601001. And when the data version of the client group definition is updated, the data version corresponds to an updating state, and is used for recording whether the client group definition is updated or not, and if so, the updating state is the updating completion. When the customer group judgment is performed, the user group list of the latest version in the finished state is selected as a basis, and the effective customer group list is definitely existed, so that the unavailable state in the process of updating the customer group is avoided.
In step S300, if the first update information is in the history information of the tag set update information, the client group list is updated.
The client group list comprises client group definitions and client group definition updating information of each client. The history information of the tag set update information is update information after the latest update information of the tag set update information is removed.
In this step, if the first update information defined by the client group is in the history information of the tag set update information, it is indicated that the tag set update information is updated, but the update information defined by the corresponding client group is not updated correspondingly, that is, the tag set update information is newer than the update information defined by the client group.
In some embodiments, as shown in fig. 3, step S300 includes sub-steps S310-S320:
step S310, it is determined whether the data version defined by the client group is in the history version of the data version of the tag set.
In this step, the data version of the updated tag set may be compared with the data version of the client group definition, as shown in fig. 2, and if the data version of the updated tag set is greater than the data version of the client group definition, it is indicated whether the data version of the client group definition is in the history version of the data version of the tag set.
Step S320, if yes, updating the client group definition to which each client belongs, and updating the first update information to the data version of the current tag set.
Specifically, if the data version of the client group definition is in a historical version of the data version of the tag set. The customer group detail table is updated. Updating the customer group definition to which each customer belongs according to the new value of the tag set and the relevant customer group definition, and updating the first updating information into the data version of the current tag set after the customer group definition to which each customer belongs is updated.
In some embodiments, as shown in fig. 4, before comparing the tag set update information in the tag set with the client group definition update information in the client group definition table, steps S400 to S600 are further included:
step S400, judging whether the numerical value of the tag rule in the tag set is updated.
The tag set further comprises a tag set data state table corresponding to each tag set table; the data version of the tag set is stored in a tag set data state table.
Taking the deposit label set table as an example, if 10 ten thousand is changed to 20 ten thousand, the numerical value of the label rule in the label set is updated.
The new deposit label set table is:
and S500, if yes, screening the customer group definition to be updated according to the numerical value of the updated label rule, and recording the customer group definition updating information corresponding to the current customer group definition.
Specifically, according to the numerical value of the updated label rule, the customer group definition needing to be updated is screened out, and the historical customer group definition only needs to be updated when the deposit is less than or equal to 10 ten thousand or 10< deposit less than or equal to 50 ten thousand. And recording the client group definition updating information corresponding to the current client group definition, namely the current client group definition data version of the historical client group definition.
Step S600, obtaining a corresponding tag set table according to the tag corresponding to the customer group definition which is updated as required, and polling the tag set data state table corresponding to the tag set table.
Specifically, the corresponding tag set table is obtained according to the tag corresponding to the client group definition which is updated as required, and the data versions of all tag sets in the tag set data state table corresponding to the tag set table are compared with the data versions of the client group definition one by one.
The thought of updating the client group information in the embodiment of the application is not active unconditional updating, but firstly judges whether the client group definition is changed or not, if so, updates the client group information table, if not, judges the updating of the numerical value of the tag rule in the tag set, and updates the client group information only when the numerical value is updated, thereby avoiding the resource waste of unconditional updating of the tag invariable client group information. Compared with the method for directly improving the updating frequency of the client group to improve the aging performance consumption of the client group, the method has the advantages that the polling monitoring of the updating state of the tag set table is greatly reduced, the upper limit of the polling frequency is higher in tolerance, and the corresponding aging performance can be obviously improved.
Fig. 5 is a schematic diagram of a configuration of a client group information updating apparatus according to an embodiment of the present application. The client group information updating apparatus 100 exemplarily includes:
a judging module 110, configured to judge whether the client group definition is changed when the update of the client group information is detected; wherein the customer base is defined as a logical combination of at least one tag rule.
A comparison module 120, configured to compare the tag set update information in the tag set with the client group definition update information in the client group definition table if not; the tag set comprises a tag set table for storing tags of the same category; the client group definition update information includes first update information.
An updating module 130, configured to update the customer group list if the first update information is in the history information of the tag set update information; the client group list comprises client group definitions and client group definition updating information of each client.
It can be understood that the apparatus of this embodiment corresponds to the client group information updating method of the above embodiment, and the options in the above embodiment are also applicable to this embodiment, so the description is not repeated here.
The present application also provides a terminal device, which exemplarily includes a processor and a memory, where the memory stores a computer program, and the processor executes the computer program, so that the terminal device performs the functions of the above-mentioned client group information updating method or each module in the above-mentioned client group information updating apparatus.
The processor may be an integrated circuit chip with signal processing capabilities. The processor may be a general purpose processor including at least one of a central processing unit (Central Processing Unit, CPU), a graphics processor (Graphics Processing Unit, GPU) and a network processor (Network Processor, NP), a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like that may implement or perform the methods, steps, and logic blocks disclosed in embodiments of the present application.
The Memory may be, but is not limited to, random access Memory (Random Access Memory, RAM), read Only Memory (ROM), programmable Read Only Memory (Programmable Read-Only Memory, PROM), erasable Read Only Memory (Erasable Programmable Read-Only Memory, EPROM), electrically erasable Read Only Memory (Electric Erasable Programmable Read-Only Memory, EEPROM), etc. The memory is used for storing a computer program, and the processor can correspondingly execute the computer program after receiving the execution instruction.
The present application also provides a readable storage medium storing a computer program for use in the above terminal device.
In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. The apparatus embodiments described above are merely illustrative, for example, of the flow diagrams and block diagrams in the figures, which illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
In addition, functional modules or units in various embodiments of the application may be integrated together to form a single part, or the modules may exist alone, or two or more modules may be integrated to form a single part.
The functions, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a smart phone, a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within the scope of the present application.
Claims (8)
1. A method for updating customer base information, comprising:
when the updating of the client group information is detected, judging whether the client group definition in the client group definition table is changed or not;
if the customer group definition is changed, updating the customer group detail table according to the customer group definition;
if the client group definition is not changed, comparing the label set updating information in the label set with the data version of the client group definition in the client group definition table; wherein the customer base is defined as a logical combination of at least one tag rule; the tag set comprises a tag set table for storing tags of the same category; the data version defined by the client group comprises first updating information and second updating information; the first updating information is updated according to the updating of the tag set updating information, the second updating information is updated according to the changing of the client group definition, and the second updating information is an M-bit increment integer;
if the first updating information is in the history information of the tag set updating information, updating a client group list; the client group list comprises client group definitions of each client and data versions of the client group definitions, and the historical information of the tag set update information is update information after the latest update information of the tag set update information is removed;
wherein the updating the client group list includes:
updating the client group definition of each client, judging if the client group definition is changed, and adding 1 to the M-bit increment integer of the data version of the currently recorded client group definition; and if the label set updating information is judged to be changed, updating the first updating information into the label set updating information of the current label set.
2. The method for updating client group information according to claim 1, wherein the tag set updating information is a data version of the tag set;
and if the first updating information is in the history information of the tag set updating information, updating the first updating information into the tag set updating information.
3. The method for updating client group information according to claim 2, wherein the tag set further comprises a tag set data state table corresponding to each of the tag set tables; the data version of the tag set is stored in the tag set data state table;
before comparing the tag set update information in the tag set with the data version of the client group definition in the client group definition table, the method further comprises:
judging whether the numerical value of the tag rule in the tag set is updated or not;
if yes, screening the customer group definition to be updated according to the updated numerical value of the label rule, and recording the update information of the customer group definition corresponding to the current customer group definition;
and acquiring a corresponding tag set table according to the tag corresponding to the client group definition to be updated, and polling the tag set data state table corresponding to the tag set table.
4. A customer group information updating method according to claim 2 or 3, wherein the data version of the tag set is a combination of the tag set update time and an N-bit increment integer;
the data version defined by the client group is a combination of a historical data version of the tag set and an M-bit increment integer.
5. The method for updating client group information according to claim 4, wherein updating the client group list if the first update information is in the history information of the tag set update information comprises:
judging whether the data version defined by the client group is in a historical version of the data version of the tag set or not;
if yes, updating the client group definition to which each client belongs, and updating the first updating information into the data version of the current tag set.
6. A client group information updating apparatus, comprising:
the judging module is used for judging whether the client group definition in the client group definition table is changed or not when the update of the client group information is detected;
the comparison module is used for updating the client group list according to the client group definition if the client group definition is changed;
the comparison module is also used for comparing the tag set updating information in the tag set with the data version of the client group definition in the client group definition table if the client group definition is not changed; the tag set comprises a tag set table for storing tags of the same category; the data version defined by the client group comprises first updating information and second updating information; the first updating information is updated according to the updating of the tag set updating information, the second updating information is updated according to the changing of the client group definition, and the second updating information is an M-bit increment integer;
the updating module is used for updating the client group list if the first updating information is in the history information of the tag set updating information; the client group list comprises client group definitions of each client and data versions of the client group definitions, and the historical information of the tag set update information is update information after the latest update information of the tag set update information is removed;
wherein the updating module updates the client group list, including:
updating the client group definition to which each client belongs, judging if the client group definition is changed, and adding 1 to the M-bit increment integer of the currently recorded client group definition updating information; and if the label set updating information is judged to be changed, updating the first updating information into the label set updating information of the current label set.
7. A terminal device, characterized in that the terminal device comprises a processor and a memory, the memory storing a computer program, the processor being adapted to execute the computer program to implement the client group information updating method of any of claims 1-5.
8. A readable storage medium, characterized in that it stores a computer program which, when executed on a processor, implements the client group information updating method according to any of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310786666.3A CN116523526B (en) | 2023-06-30 | 2023-06-30 | Client group information updating method and device, terminal equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310786666.3A CN116523526B (en) | 2023-06-30 | 2023-06-30 | Client group information updating method and device, terminal equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN116523526A CN116523526A (en) | 2023-08-01 |
| CN116523526B true CN116523526B (en) | 2023-09-19 |
Family
ID=87399791
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310786666.3A Active CN116523526B (en) | 2023-06-30 | 2023-06-30 | Client group information updating method and device, terminal equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116523526B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10121141B1 (en) * | 2014-06-25 | 2018-11-06 | Urban Airship, Inc. | Updating digital wallet assets |
| CN111538736A (en) * | 2020-03-11 | 2020-08-14 | 上海联蔚信息科技有限公司 | User label updating method and device |
| CN114003813A (en) * | 2021-10-29 | 2022-02-01 | 平安国际智慧城市科技股份有限公司 | Client grouping method, device, equipment and storage medium |
| CN115587247A (en) * | 2022-10-09 | 2023-01-10 | 咪咕文化科技有限公司 | Method, device and equipment for monitoring user label and storage medium |
| CN116205479A (en) * | 2022-11-30 | 2023-06-02 | 三一集团有限公司 | Customer risk level assessment method and device |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030233280A1 (en) * | 2002-06-12 | 2003-12-18 | Ncr Corporation | Methods and apparatus for ensuring accurate display of data by an electronic shelf label during an update |
-
2023
- 2023-06-30 CN CN202310786666.3A patent/CN116523526B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10121141B1 (en) * | 2014-06-25 | 2018-11-06 | Urban Airship, Inc. | Updating digital wallet assets |
| CN111538736A (en) * | 2020-03-11 | 2020-08-14 | 上海联蔚信息科技有限公司 | User label updating method and device |
| CN114003813A (en) * | 2021-10-29 | 2022-02-01 | 平安国际智慧城市科技股份有限公司 | Client grouping method, device, equipment and storage medium |
| CN115587247A (en) * | 2022-10-09 | 2023-01-10 | 咪咕文化科技有限公司 | Method, device and equipment for monitoring user label and storage medium |
| CN116205479A (en) * | 2022-11-30 | 2023-06-02 | 三一集团有限公司 | Customer risk level assessment method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN116523526A (en) | 2023-08-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20170139692A1 (en) | System for displaying notification dependencies between component instances | |
| CN110134689B (en) | Target group screening method and system based on main body object label change and computer equipment | |
| JP2022189877A (en) | RPA maintenance support device | |
| CN108920564B (en) | Talent management method based on block chain and terminal thereof | |
| CN109871593B (en) | Information inheritance method and device based on BIM platform and storage device | |
| CN111400294A (en) | Data anomaly monitoring method, device and system | |
| CN116523526B (en) | Client group information updating method and device, terminal equipment and storage medium | |
| US20220101464A1 (en) | Intellectual-Property Landscaping Platform | |
| CN112084262A (en) | Data information screening method and device, computer equipment and storage medium | |
| CN110110295B (en) | Large sample research and report information extraction method, device, equipment and storage medium | |
| CN111553803A (en) | Claims processing method and device | |
| US11809694B2 (en) | Intellectual-property landscaping platform with interactive graphical element | |
| CN113761082A (en) | Data visualization method, device and system | |
| CN114860362A (en) | Interface updating method and device | |
| US20220101462A1 (en) | Intellectual-Property Landscaping Platform | |
| CN110197383B (en) | Method and device for acquiring user set of client group | |
| CN114511314A (en) | Payment account management method and device, computer equipment and storage medium | |
| CN111709210A (en) | Method and device for generating component list, terminal equipment and storage medium | |
| CN112164433A (en) | Hospital background data processing method and system | |
| CN111597452A (en) | Method and device for adding label, electronic equipment and readable storage medium | |
| CN116501375B (en) | Data dictionary version management method, device, computer equipment and storage medium | |
| CN114880713B (en) | User behavior analysis method, device, equipment and medium based on data link | |
| CN116382924B (en) | Recommendation method and device for resource allocation, electronic equipment and storage medium | |
| CN113076237B (en) | Memory performance testing method and system and computer readable storage medium | |
| CN108846699B (en) | Demand matching method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |