A configurable control method and system for CRM business repeat handling

Abstract

The application discloses a configurable control CRM business repeated handling method, comprising the following steps: receiving order creation request, obtaining time influence range and creation information; according to the time influence range and time granularity, the serial number of the influence time period is calculated; according to the creation information, the characteristic value is calculated; according to the serial number of the influence time period and the characteristic value, the characteristic node is generated; the application also discloses a configurable control CRM business repeated handling system; the application can prevent the same request from being repeatedly submitted, causing business repeated handling or abnormality. The characteristic value is obtained from the request parameter, and the unique characteristic node is composed of the time granularity. The unique check is realized by using the characteristic node table. The application eliminates the waste orders created due to repeated submission and the like in the previous system, improves the stability and efficiency of the system, and reduces the workload of system maintenance.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of telecommunication technology, in particular to a configurable control method and system for repeated handling of CRM business. BACKGROUND

[0002] The CRM business handling system in the telecommunication industry is extremely difficult to control repeated submission of business due to its complexity. When the system is jammed, there is a problem of twice submission of business by operators, which leads to failure of normal execution of the request submitted later, resulting in a large number of abnormal orders. In addition, due to the complexity of business, it takes a certain time for the order of business to land, and there is a problem of repeated error orders when the same business of the same user is handled by different channels. SUMMARY

[0003] The present application aims to provide a configurable control method and system for repeated handling of CRM business, which can solve the problem of generation of waste orders caused by repeated submission of CRM business by salespersons, and can also solve the problem of generation of waste orders caused by handling of the same business of the same user by different channels in a short time.

[0004] To solve the above technical problems, the present application provides a configurable control method for repeated handling of CRM business, comprising the following steps:

[0005] Receiving an order creation request, obtaining a time influence range and creation information;

[0006] Setting a time granularity, calculating the sequence number of the influence time period according to the time influence range and the time granularity;

[0007] Calculating a feature value according to the creation information;

[0008] Generating a feature node according to the sequence number of the influence time period and the feature value;

[0009] Inserting the feature node into a feature node table; if the insertion is successful, creating an order.

[0010] Preferably, the sequence number of the influence time period is calculated according to the time influence range and the time granularity, specifically comprising the following steps:

[0011] The time influence range includes a start time and a time influence period; the end time is calculated according to the start time, the time influence period and the time granularity;

[0012] The time period affected is obtained according to the start time and the end time;

[0013] The sequence number of the influence time period is obtained according to the time period affected and the time granularity.

[0014] Preferably, the start time is rounded down, and the end time is rounded up.

[0015] Preferably, according to the time period of the influence and the time granularity, a sequence number of the influence time period is obtained; specifically including the following steps:

[0016] In the influence time period, a sequence number of the influence time period is obtained every time interval of the time granularity.

[0017] Preferably, the time granularity is 5s.

[0018] Preferably, an order creation request is received, and time influence range and creation information are obtained; specifically including the following steps:

[0019] An order creation request is received, and the order creation request is subjected to idempotency check to exclude repeated order creation requests; and the time influence range and creation information of the order creation request passing the idempotency check are obtained.

[0020] Preferably, the feature node table includes a single-day table and a double-day table; and the feature node is inserted into the corresponding single-day table or double-day table according to the sequence number of the influence time period thereof.

[0021] Preferably, the method for configurable control of repeated handling of CRM business further includes the following steps:

[0022] The single-day table or double-day table in the feature node table used the previous day is cleaned up.

[0023] Preferably, the creation information includes business information and user information.

[0024] The business information includes an operation code op_code and a business identifier busi_id.

[0025] The user information includes a user code custIdType.

[0026] The feature value is: the operation code op_code, the business identifier busi_id, and the user code custIdType, which are sorted in order and then hashed.

[0027] The application also discloses a system for configurable control of repeated handling of CRM business, comprising:

[0028] An order receiving module is configured to receive an order creation request, and obtain time influence range and creation information.

[0029] A sequence number calculation module is configured to calculate a sequence number of an influence time period according to the time influence range and the time granularity.

[0030] A feature value calculation module is configured to calculate a feature value according to the creation information.

[0031] generating module, configured to generate a feature node according to the sequence number of the influence time period and the feature value;

[0032] a node inserting module, configured to insert the feature node into a feature node table.

[0033] Compared with the prior art, the present application has the following beneficial effects:

[0034] The present application can prevent the same request from being repeatedly submitted, causing business to be repeatedly handled or abnormal. The feature value is obtained from the request input parameter, and a unique feature node is formed together with the time granularity. The unique check is realized by using the feature node table.

[0035] The present application eliminates the waste orders created in the previous system due to repeated submission and the like, improves the stability and efficiency of the system, and reduces the workload of system maintenance. BRIEF DESCRIPTION OF DRAWINGS

[0036] The specific embodiments of the present application will be further described in detail below with reference to the accompanying drawings.

[0037] Figure 1 is a flowchart of a configurable control method for CRM business repeated handling. DETAILED DESCRIPTION

[0038] In the following description, a lot of specific details are set forth in order to facilitate a thorough understanding of the present application. However, the present application can be practiced in many different ways beyond the specific details disclosed herein, and the skilled in the art can make similar modifications without departing from the spirit of the present application, so the present application is not limited to the specific implementation disclosed below.

[0039] The terms used in one or more embodiments of the present specification are only for the purpose of describing specific embodiments, and are not intended to limit one or more embodiments of the present specification. The singular forms "a", "an" and "the" used in one or more embodiments of the present specification and the appended claims are also intended to include the plural forms, unless the context clearly indicates otherwise. It should also be understood that the term "and / or" used in one or more embodiments of the present specification means and includes any or all possible combinations of one or more associated listed items.

[0040] It should be understood that, although the terms first, second, etc. can be employed in describing various information in one or more embodiments of the present specification, the information should not be limited to such terms. These terms are only used to distinguish one piece of information from another piece of information of the same type. For example, without departing from the scope of one or more embodiments of the present specification, first can also be referred to as second, and similarly, second can also be referred to as first. Depending on the context, the word "if' as used herein can be interpreted as "when" or "upon" or "in response to determining".

[0041] As Figure 1 shown, a method for configurable control of CRM business repeated handling according to the present application comprises the following steps:

[0042] receiving an order creation request, obtaining a time impact range and creation information;

[0043] setting a time granularity, calculating the sequence number of the impact time period according to the time impact range and the time granularity;

[0044] calculating a characteristic value according to the creation information;

[0045] generating a characteristic node according to the sequence number of the impact time period and the characteristic value;

[0046] inserting the characteristic node into a characteristic node table; if successfully inserted, creating an order.

[0047] In this embodiment, the characteristic value is obtained from the request parameter, and the time granularity constitutes a unique characteristic string. The uniqueness check is realized by using the database primary key feature. The meaning of the characteristic node is that the characteristic should be unique in the following time period. Before order creation, the data is first inserted into the characteristic node table, and if successfully inserted, the order creation process is followed. If there is a primary key conflict when the characteristic node is recorded, it means that there is a repeated request before the current order creation request, and the order creation request is terminated, and it is prompted that repeated submission is prohibited. In this way, repeated submission of the same request can be prevented, and business repeated handling or abnormality can be caused.

[0048] The characteristic node IdempNode is embodied as a logical entity in the system, and includes the following main attributes:

[0049] Characteristic value ID (value): String, discrete data after hashing

[0050] Time period sequence number (TimeSeq): String, the system follows a unified rule to form an order of atomic time units; creation time (CreateTime): timestamp

[0051] Operation time (Optime): timestamp

[0052] The primary key feature is: feature value ID + time period sequence number (TimeSeq)

[0053] According to the data structure of the feature node, a feature node table of the database is built.

[0054] In the above embodiment, preferably, according to the creation information, the feature value is calculated, and the rule is specifically:

[0055] The creation information includes business information and user information, etc.; the business information includes an operation code op_code and a business identifier busi_id; and the user information includes a user code custIdType.

[0056] The feature value is: the business information and the user information are arranged in sequence and then hashed.

[0057] That is: the operation code op_code + the business identifier busi_id + the user code custIdType are sorted in sequence and then hashed.

[0058] The op_code is a specific business action code, which stores the action code corresponding to the crm system.

[0059] In the above embodiment, preferably, according to the time influence range and the time granularity, the sequence number of the influence time period is calculated, which specifically includes the following steps:

[0060] The time influence range includes a start time and a time influence period; and according to the start time, the time influence and the time granularity, the end time can be calculated.

[0061] According to the start time and the end time, the influence time period is obtained.

[0062] According to the influence time period and the time granularity, the sequence number of the influence time period is obtained.

[0063] In the above embodiment, preferably, according to the start time and the end time, the influence time period is obtained; specifically including the following steps:

[0064] The start time is rounded down, and the end time is rounded up to obtain the influence time period.

[0065] In the above embodiment, preferably, according to the influence time period and the time granularity, the sequence number of the influence time period is obtained; specifically including the following steps:

[0066] In the influence time period, every interval of a time granularity obtains a sequence number of the influence time period.

[0067] In the above embodiment, preferably, the time granularity is 5s.

[0068] In this embodiment, due to the existence of time granularity, time alignment may be caused; for example, taking 10s as the time granularity, when the request with the start time of 2021-6-9; 13:30:23 arrives, it is assumed that the request needs to affect 3 time influence periods; then the time period of its influence may be 2021-6-9; 13:30:23~2021-6-9; 13:30:53; if 2021-6-9; 13:30:23~2021-6-9; 13:30:50 is rounded down, 27s is affected; if 2021-6-9 13:30:23~2021-6-9 13:31:00 is rounded up, 37s is affected.

[0069] For this, the present application is as follows: reduce the time granularity to 5s, use rounding down for the start time and rounding up for the end time, that is, 2021-6-9; 13:30:20~2021-6-9; 13:30:40. For the above-mentioned list, the following 5 sequences are recorded: the last digit is the time granularity in one hour, for example, 30 minutes and 20 seconds, the calculation method is (30*60+20) / 5=364.

[0070] The feature node is:

[0071] Feature value+2021-6-9 13-364;

[0072] Feature value+2021-6-9 13-365;

[0073] Feature value+2021-6-9 13-366;

[0074] Feature value+2021-6-9 13-367;

[0075] Feature value+2021-6-9 13-368;

[0076] In the above embodiment, preferably, the order creation request is received, and the time influence range and creation information are obtained; specifically including the following steps:

[0077] The order creation request is received, the order creation request is subjected to idempotency check to screen out repeated order creation requests, and the time influence range and creation information of the order creation request passing the idempotency check are obtained;

[0078] In this embodiment, the order creation request contains an operation code op_code and a business identifier busi_id, and the operation code op_code and the business identifier busi_id are subjected to idempotency check.

[0079] In the above embodiment, preferably, the feature node table comprises a single-day table and a double-day table; and the feature node is stored in the corresponding single-day table or double-day table according to the serial number of the time period affected by the feature node.

[0080] In the present embodiment, the feature node is stored in the single-day table or double-day table corresponding to the time according to the time information in the feature node; thus the feature node table written on the current day is different from that written on the next day.

[0081] In the above embodiment, preferably, the single-day table or double-day table in the feature node table used on the previous day is cleaned up.

[0082] The application further discloses a configurable control system for repeating handling of CRM business, comprising:

[0083] An order receiving module is configured to receive an order creation request, acquire a time influence range and creation information;

[0084] A serial number calculating module is configured to calculate a serial number of an influence time period according to the time influence range and time granularity;

[0085] A feature value calculating module is configured to calculate a feature value according to the creation information;

[0086] A generating module is configured to generate a feature node according to the serial number of the influence time period and the feature value;

[0087] A node inserting module is configured to insert the feature node into a feature node table.

[0088] In the several embodiments provided by the present application, it should be understood that the disclosed device and method can be implemented in other ways. For example, the device embodiment described above is only illustrative, and for example, the division of the modules, modules or units is only a logical function division, and actual implementation can have another division manner, for example, a plurality of units, modules or components can be combined or integrated into another device, or some features can be ignored or not executed.

[0089] The units can or can not be physically separated, and the components displayed as units can be one physical unit or multiple physical units, that is, can be located in one place, or can be distributed to multiple different places. According to actual needs, part or all of the units can be selected to achieve the purpose of the embodiment scheme.

[0090] In addition, each functional unit in each embodiment of the present application can be integrated in one processing unit, or each unit can exist physically, or two or more units can be integrated in one unit. The above integrated unit can be realized in the form of hardware or in the form of a software functional unit.

[0091] In particular, the processes described above with reference to the flow charts can be implemented as computer software programs in accordance with embodiments of the present disclosure. For example, embodiments of the present disclosure include a computer program product comprising a computer program carried on a computer readable medium, the computer program comprising program code for executing the methods illustrated by the flow charts. In such embodiments, the computer program can be downloaded and installed from a network via a communication section, and / or installed from a detachable medium. When the computer program is executed by a central processing unit (CPU), the above-described functions defined in the methods of the present disclosure are executed. It should be noted that the above-described computer readable medium of the present disclosure can be a computer readable signal medium or a computer readable storage medium or any combination of the two. The computer readable storage medium may, for example, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus or device, or any combination of the above.

[0092] The flow charts and block diagrams in the drawings are illustrations of possible architectural, functional, and operational architectures of systems, methods, and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flow charts or block diagrams can represent a module, a segment, or a portion of code which comprises one or more executable instructions for implementing the specified logical functions. It should also be noted that in some alternative implementations, the functions noted in the blocks can occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently or in the reverse order, depending on the functionality involved. It will also be noted that each block in the block diagrams and / or flow charts, and combinations of blocks in the block diagrams and / or flow charts, can be implemented by special purpose hardware-based systems which perform the specified functions or operations, or combinations of special purpose hardware and computer instructions.

[0093] The above description is merely that of a specific implementation of the present disclosure, but the scope of protection of the present disclosure is not limited thereto. Any changes or substitutions within the technical scope of the present disclosure should be encompassed within the scope of protection of the present disclosure. Therefore, the scope of protection of the present disclosure should be subject to the scope of protection of the claims.

Claims

1. A method of configurable control of CRM business process repetition, characterized in that, The method comprises the following steps: receiving an order creation request, obtaining a time influence range and creation information; setting a time granularity, calculating a sequence number of an influence time period according to the time influence range and the time granularity; calculating a feature value according to the creation information; generating a feature node according to the sequence number of the influence time period and the feature value; inserting the feature node into a feature node table; if the insertion is successful, creating an order; the feature node table comprises a single-day table and a double-day table; the feature node is inserted into the corresponding single-day table or double-day table according to the sequence number of the influence time period.

2. The method of claim 1, wherein the CRM business process is configurable. According to the time influence range and the time granularity, the sequence number of the influence time period is calculated, which comprises the following steps: The time influence range comprises a start time and a time influence period; the end time is calculated according to the start time, the time influence period and the time granularity; obtaining an influence time period according to the start time and the end time; obtaining the sequence number of the influence time period according to the influence time period and the time granularity.

3. The method of claim 2, wherein: the start time is rounded down, and the end time is rounded up.

4. The method of claim 3, wherein, According to the influence time period and the time granularity, the sequence number of the influence time period is obtained; which comprises the following steps: In the influence time period, a sequence number of an influence time period is obtained every time the time granularity is separated.

5. The method of claim 4, wherein: the time granularity is 5s.

6. The method of claim 1, wherein the CRM business process is configurable. receiving an order creation request, obtaining a time influence range and creation information; which comprises the following steps: receiving an order creation request, performing idempotency check on the order creation request to exclude duplicate order creation requests; obtaining the time influence range and creation information of the order creation request that passes the idempotency check.

7. The method of claim 6, wherein the CRM business process is configured to repeat. It also comprises the following steps: cleaning up the single-day table or double-day table in the feature node table used the day before.

8. The method of claim 1, wherein: the creation information comprises business information and user information; the business information comprises an operation code op_code and a business identifier busi_id; the user information comprises a user code custIdType; The feature value is: the operation code op_code, the business identifier busi_id and the user code custIdType, which are sorted in order and then hashed.

9. A system for implementing the method of configurable control of CRM business process re-engineering according to any one of claims 1 to 8, characterized in that, It comprises: an order receiving module for receiving an order creation request, obtaining a time influence range and creation information; a sequence number calculation module for calculating a sequence number of an influence time period according to a time influence range and a time granularity; a feature value calculation module for calculating a feature value according to creation information; a generation module for generating a feature node according to the sequence number of the influence time period and the feature value; a node insertion module for inserting the feature node into a feature node table.

Images