Resource data processing method and device, computer equipment and readable storage medium
By receiving resource adjustment requests, extracting contract characteristic data and calling the postponement rule recommendation model, the postponement problem of holiday resource adjustment in resource transfer business is solved, and automated and personalized resource data processing is realized, and efficiency and accuracy are improved.
Patent Information
- Application Number
- CN202411521594.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-10-29
- Publication Date
- 2024-12-27
AI Technical Summary
In the existing resource transfer business, the repricing mechanism is not postponed by default during holidays, resulting in inaccurate resource use and complex adjustments to the pricing mechanism, reducing resource data processing efficiency.
By receiving resource adjustment requests, extracting contract characteristic data, determining whether the initial resource adjustment date is a holiday, calling the postponement rule recommendation model, predicting and determining the postponed target resource adjustment date, and pushing it to the request object to realize automated and personalized postponement deal with.
The process of determining the resource adjustment date has been optimized, errors caused by human factors have been reduced, and the efficiency and accuracy of resource data processing have been improved, and the need for postponed processing of resource transfer during holidays has been met.
Smart Images

Figure CN119204581A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of artificial intelligence technology, and in particular to a resource data processing method, apparatus, computer equipment, computer-readable storage medium, and computer program product. Background Art
[0002] In the resource transfer business, the contract usually stipulates relevant information about resource transfer, including pricing and repricing of resource transfer. The original repricing mechanism does not postpone by default when encountering holidays. If the repricing date is a holiday, the repricing will be carried out normally on the holiday. This processing method cannot meet the requirements for deferring the processing of certain specific resource transfers when the repricing date encounters a holiday, resulting in inaccurate resource usage.
[0003] At present, the adjustment of the pricing mechanism for resource transfer is usually done manually. Since the adjustment of the pricing mechanism needs to take into account not only business days but also holiday information of the resource type, the difficulty of adjustment is greatly increased, which reduces the efficiency of resource data processing. Summary of the invention
[0004] Based on this, it is necessary to provide an efficient resource data processing method, device, computer equipment, computer-readable storage medium and computer program product to address the above technical problems.
[0005] In a first aspect, the present application provides a resource data processing method, comprising:
[0006] Receive a resource adjustment request carrying a contract identifier sent by a request object;
[0007] Acquire contract information corresponding to the contract identifier, and extract contract characteristic data from the contract information, wherein the contract characteristic data includes a resource adjustment period and a resource adjustment day;
[0008] Determining an initial resource adjustment date based on the resource adjustment cycle and the resource adjustment date;
[0009] When it is determined that the initial resource adjustment date is a holiday based on preset calendar information, the trained postponement rule recommendation model is called with the contract feature data as input to predict a postponement rule matching the contract information, wherein the postponement rule recommendation model is trained based on historical contract data carrying a postponement rule category label;
[0010] According to the postponement rule, the initial resource adjustment date and the preset calendar information, the postponed target resource adjustment date is determined, and the target resource adjustment date is pushed to the request object.
[0011] In one of the embodiments, the preset calendar information includes a calendar corresponding to a resource type and an institution business calendar;
[0012] Determining whether the initial resource adjustment date is a holiday based on preset calendar information includes:
[0013] Extracting first holiday information from a calendar corresponding to the resource type, and extracting second holiday information from the organization's business calendar;
[0014] Integrate the first holiday information and the second holiday information to obtain holiday list information;
[0015] The initial resource adjustment date is compared with the holiday list information to determine whether the initial resource adjustment date is a holiday.
[0016] In one embodiment, after determining the postponed target resource adjustment date, the method further includes:
[0017] Based on the target resource adjustment date and the preset approval process triggering condition, determining whether the preset postponed approval process needs to be triggered;
[0018] If it is determined that the postponement approval process needs to be triggered, a postponement approval form is generated based on the target resource adjustment date and the contract information, and the postponement approval form is submitted to the approval personnel for approval;
[0019] In a case where the deferred approval is approved, the initial resource adjustment date in the contract information is updated to the target resource adjustment date, and the contract information is updated.
[0020] In one embodiment, the contract characteristic data includes notification requirement data; after updating the contract information, the method further includes:
[0021] Obtaining preference data of the request object;
[0022] Determine a message push channel and a message push time according to the user preference data and the notification requirement data;
[0023] Based on the message push time and the push channel, a resource adjustment message is pushed, wherein the resource adjustment message includes an initial resource adjustment date, a target resource adjustment date, and a postponement rule.
[0024] In one embodiment, after predicting the postponement rule matching the contract information, the method further includes:
[0025] Pushing a rule confirmation message to the request object, so that the request object can confirm whether the postponement rule needs to be changed, the rule confirmation message carries the postponement rule and the preset optional postponement rule;
[0026] Receiving the confirmed postponement rule fed back by the request object;
[0027] Based on the confirmed postponement rule fed back by the requesting object, the initial resource adjustment date and the preset calendar information, the postponed target resource adjustment date is determined, and the target resource adjustment date is pushed to the requesting object.
[0028] In one embodiment, the target postponement rules include: no postponement, postponement to the next working day but not across a month, or postponement to the next working day across a month.
[0029] In a second aspect, the present application further provides a resource data processing device, comprising:
[0030] A request receiving module, used for receiving a resource adjustment request carrying a contract identifier sent by a request object;
[0031] A data extraction module, used to obtain contract information corresponding to the contract identifier, and extract contract characteristic data from the contract information, wherein the contract characteristic data includes a resource adjustment period and a resource adjustment day;
[0032] A resource adjustment date determination module, configured to determine an initial resource adjustment date based on the resource adjustment cycle and the resource adjustment date;
[0033] A deferral rule recommendation module, for, when it is determined based on preset calendar information that the initial resource adjustment date is a holiday, using the contract feature data as input, calling a trained deferral rule recommendation model, and predicting a deferral rule matching the contract information, wherein the deferral rule recommendation model is trained based on historical contract data carrying deferral rule category labels;
[0034] The target resource adjustment date determination module is used to determine the postponed target resource adjustment date according to the postponement rule, the initial resource adjustment date and the preset calendar information, and push the target resource adjustment date to the request object.
[0035] In a third aspect, the present application further provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps in any one of the above-mentioned resource data processing method embodiments when executing the computer program.
[0036] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the steps in any one of the above-mentioned resource data processing method embodiments are implemented.
[0037] In a fifth aspect, the present application also provides a computer program product, including a computer program, which, when executed by a processor, implements the steps in any one of the above-mentioned resource data processing method embodiments.
[0038] The resource data processing method, device, computer equipment, computer-readable storage medium and computer program product are pre-trained based on historical contract data and deferred rule labels to obtain a deferred rule recommendation model. In actual applications, after receiving a resource adjustment request, the contract information is obtained, and the contract feature data is extracted from the contract information. First, the initial resource adjustment date is determined based on the resource adjustment cycle and resource adjustment date in the contract feature data. Then, when the initial resource adjustment date is a holiday based on the calendar information, the trained deferred rule recommendation model is called with the contract feature data as input to predict the deferred rule matching the contract information. Finally, the actual resource adjustment date after deferred is derived based on the deferred rule, the initial resource adjustment date and the calendar information. The entire solution provides a standard and automated resource processing solution by introducing an intelligent deferred rule recommendation model, optimizes the process of determining the resource adjustment date, does not require manual calendar checking, and considers complex rules and factors to determine the deferred date. It can intelligently match the deferred rule suitable for the customer according to different contract information, and determine the accurate resource adjustment date, thus realizing a personalized deferred solution, reducing errors caused by human factors, and improving the efficiency and accuracy of resource data processing. BRIEF DESCRIPTION OF THE DRAWINGS
[0039] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the drawings required for use in the embodiments of the present application or related technical descriptions will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.
[0040] FIG1 is an application environment diagram of a resource data processing method in one embodiment;
[0041] Figure 2 A schematic diagram of a process flow of a resource data processing method in one embodiment;
[0042] Figure 3 A schematic diagram of a flow chart of a resource data processing method in another embodiment;
[0043] Figure 4 A flowchart of the step of approving the target resource adjustment date in an embodiment;
[0044] Figure 5 A schematic diagram of a process of adjusting a personalized push resource message in an embodiment;
[0045] Figure 6 is a detailed flowchart of a resource data processing method in another embodiment;
[0046] Figure 7 is a structural block diagram of a resource data processing device in one embodiment;
[0047] Figure 8 is a structural block diagram of a resource data processing device in another embodiment;
[0048] FIG. 9 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION
[0049] In order to make the purpose, technical solutions and advantages of the present application clearer, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application. It should be noted that in the embodiments of the present application, certain software, groups, models and other existing solutions in the industry may be mentioned, which should be considered as exemplary, and their purpose is only to illustrate the feasibility of the implementation of the technical solution of the present application, but it does not mean that the applicant has or will necessarily use the solution.
[0050] It should be noted that the user information (including but not limited to user device information, user personal information and contract information, etc.) and data (including but not limited to data used for analysis such as contract feature data, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations. The acquisition, storage, use and processing of data in the technical solution of this application are in compliance with relevant provisions of national laws and regulations.
[0051] The resource data processing method provided in the embodiment of the present application can be applied in the application environment shown in FIG1 . The terminal 102 communicates with the server 104 via a network. The data storage system can store data that the server 104 needs to process. The data storage system can be integrated on the server 104, or placed on the cloud or other network servers, and the data storage system stores the trained deferred rule recommendation model.
[0052] Specifically, the requesting object, such as a customer or a business person, may perform a contract signing operation at the terminal 102 at an offline counter. In the signing process, the business person will agree with the customer on a resource adjustment method, and send a resource processing request to the server 104 through the terminal 102. The server 104 receives the resource adjustment request carrying the contract identifier sent by the requesting object, extracts the contract identifier, obtains the contract information corresponding to the contract identifier, and extracts the contract feature data from the contract information. The contract feature data includes a resource adjustment cycle and a resource adjustment date. Based on the resource adjustment cycle and the resource adjustment date, the initial resource adjustment date is determined. Then, it is determined whether the initial resource adjustment date is a holiday. When the initial resource adjustment date is determined to be a holiday based on the preset calendar information, the contract feature data is used as input to call a trained deferral rule recommendation model to predict a deferral rule matching the contract information. The deferral rule recommendation model is trained based on historical contract data carrying deferral rule category labels. Finally, according to the deferral rule, the initial resource adjustment date and the preset calendar information, the target resource adjustment date after deferral is determined, and the target resource adjustment date is pushed to the requesting object.
[0053] The terminal 102 may be, but is not limited to, various personal computers, laptops, smart phones, tablet computers, IoT devices, and portable wearable devices. The IoT devices may be smart speakers, smart TVs, smart air conditioners, smart car devices, projection devices, etc. Portable wearable devices may be smart watches, smart bracelets, head-mounted devices, etc. Head-mounted devices may be virtual reality (VR) devices, augmented reality (AR) devices, smart glasses, etc. The server 104 may be an independent physical server, a server cluster or distributed system consisting of multiple physical servers, or a cloud server that provides cloud computing services.
[0054] In an exemplary embodiment, Figure 2 As shown, a resource data processing method is provided, and the method is applied to the server 104 in FIG. 1 as an example for description, including the following steps S100 to S500. Among them:
[0055] S100: receiving a resource adjustment request carrying a contract identifier sent by a request object.
[0056] The contract identifier is data used to uniquely identify the contract, including but not limited to the contract number, contract name, and contract code. The request object refers to the object that sends the resource adjustment request, including but not limited to the user, user account, or the device logged in by the user account. Resources include but are not limited to transferable virtual resources such as computing resources, network resources, and financial resources.
[0057] In this embodiment, taking the resource as a financial resource, the request object as a customer, and the customer intending to sign a loan contract with a financial institution as an example, it can be explained as follows: the customer handles a loan business at an offline counter or online of a financial institution, and handles the loan contract signing business by operating on the interactive interface of the terminal. The customer sends a resource adjustment request carrying a contract identifier to the server through the terminal, and the server receives the resource adjustment request.
[0058] S200, acquiring contract information corresponding to the contract identifier, and extracting contract characteristic data from the contract information, the contract characteristic data including a resource adjustment cycle and a resource adjustment date.
[0059] Contract characteristic data refers to specific information defined in the contract that can describe the characteristics and terms of the contract, including but not limited to basic contract information such as contract number, contract type, and contract term, information about the contracting parties, and information about terms. Resource adjustment cycle refers to the resource adjustment cycle agreed in the contract, which can be one year, half a year, or other time. Resource adjustment date refers to the specific date for adjusting resources agreed in the contract. Resource types include but are not limited to domestic resource types and foreign resource types. Taking financial resources as an example, resource types can be currencies, including RMB and other currencies such as foreign currencies. Resource adjustment date can be the first loan date. Resource adjustment cycle is the interest rate adjustment cycle.
[0060] Following the previous step, after receiving the resource adjustment request, the server parses the contract identifier in the request, such as the contract number, and then queries the contract information database through the contract number to obtain the corresponding contract details. Then, the contract feature data can be extracted from the contract details by regular matching or keyword matching, including contract type, resource type, affiliated organization, resource adjustment cycle, resource adjustment date and resource type.
[0061] For example, taking the adjustment of loan interest rates as an example, when a loan contract is signed, the relevant interest rate information used in the loan contract is usually agreed upon, including interest rate determination and interest rate repricing. On the interest rate adjustment day, the interest rate will be readjusted. At present, interest rate repricing can only default to not being postponed when encountering holidays. If the interest rate adjustment day is a holiday, the interest rate will be adjusted normally on the holiday. In specific implementation, the server can obtain the corresponding loan contract according to the contract number of the loan contract, and then extract the contract feature data such as the interest rate adjustment period, interest rate adjustment date, and currency from the loan contract.
[0062] S300: Determine an initial resource adjustment date based on a resource adjustment cycle and a resource adjustment date.
[0063] The initial resource adjustment date refers to the next resource adjustment date determined based on the resource adjustment cycle and the specific resource adjustment date, combined with the current date. For example, if the resource adjustment date is agreed to be adjusted once every six months, and the resource adjustment date is January 1 of each year, then the next initial resource adjustment date is determined to be July 1. If the resource adjustment date is agreed to be adjusted once a year, and the resource adjustment date is January 1 of each year, then the next initial resource adjustment date is determined to be January 1. Taking the interest rate adjustment as an example, the initial resource adjustment date can be determined based on the first loan date and the interest rate adjustment cycle.
[0064] S400, when it is determined that the initial resource adjustment date is a holiday based on preset calendar information, the trained postponement rule recommendation model is called with the contract feature data as input to predict a postponement rule that matches the contract information.
[0065] In this embodiment, the calendar information refers to a holiday calendar, including but not limited to the holiday arrangement calendar of the business organization and the public holiday calendar of each region. The deferred rule recommendation model is trained based on historical contract data carrying deferred rule category labels.
[0066] In practical applications, developers can pre-collect historical contract data based on different currencies, extract contract feature data of historical contract data of different currencies, and annotate the contract feature data of different contracts based on the deferral rules agreed in the historical contract data. The annotated contract feature data is used as a training set to train a classification model such as a random forest or a classifier to obtain a deferral rule recommendation model that can predict matching deferral rules based on different contract feature data.
[0067] During specific implementation, the server can determine whether the initial resource adjustment date is a holiday based on calendar information. If the initial resource adjustment date is determined to be a holiday, it is necessary to determine whether the initial resource adjustment date needs to be postponed in case of a holiday, and how to postpone it specifically. The server uses the extracted contract feature data as input, and inputs the contract feature data into the trained postponement rule recommendation model, and the model predicts the postponement rule that best matches the contract feature data. In this embodiment, at least three postponement rules are provided, namely, no postponement, postponement to the next working day but not across months, and postponement to the next working day can span months. By providing at least three postponement rules, it is possible to flexibly select the effect of holiday postponement processing for different currencies.
[0068] For example, the request object sends a resource adjustment request with contract number C123456789. The server obtains the specific information of contract C123456789 from the database and extracts contract feature data including contract type, currency, affiliated institution, interest rate adjustment cycle, first loan date, etc. According to the first loan date and interest rate adjustment cycle, the next interest rate adjustment date is calculated to be April 30, 2023. By comparing with the preset calendar information, it is found that April 30, 2023 is a holiday. The above contract feature data is input into the trained postponement rule recommendation model, and the most matching postponement rule is predicted to be "postponed to the next working day across the month".
[0069] S500, determining the postponed target resource adjustment date according to the postponement rule, the initial resource adjustment date and the preset calendar information, and pushing the target resource adjustment date to the request object.
[0070] The target resource adjustment date refers to the actual resource adjustment date derived from the initial resource adjustment date after taking into account the deferral rules.
[0071] Continuing from the previous embodiment, since April 30, 2023 is a holiday, combined with the calendar information, it is found that the May Day holiday is approaching. Therefore, according to the postponement rule of "postponed to the next working day across the month", the next interest rate adjustment date is determined to be May 4, 2023. At this time, the interest rate adjustment date can be pushed to the customer so that the customer can know the predicted next interest rate adjustment date in time. In other embodiments, if the predicted postponement rule is "next working day but not across the month", based on the postponement rule, the next interest rate adjustment date is determined to be April 28, 2023.
[0072] In the above resource data processing method, a deferral rule recommendation model is pre-trained based on historical contract data and deferral rule labels. In actual applications, after receiving a resource adjustment request, the contract information is obtained, and the contract feature data is extracted from the contract information. First, the initial resource adjustment date is determined based on the resource adjustment cycle and resource adjustment date in the contract feature data. Then, when the initial resource adjustment date is determined to be a holiday based on the calendar information, the trained deferral rule recommendation model is called to predict the deferral rule that matches the contract information. Finally, the actual resource adjustment date after deferral is derived based on the deferral rule, the initial resource adjustment date, and the calendar information. The entire solution provides a standard and automated resource processing solution by introducing an intelligent deferral rule recommendation model, optimizes the process of determining the resource adjustment date, and does not require manual calendar checks and consideration of complex rules and factors to determine the deferral date. It can intelligently match deferral rules suitable for customers based on different contract information and determine the accurate resource adjustment date, thereby realizing a personalized deferral solution, reducing errors caused by human factors, and improving the efficiency and accuracy of resource data processing. In an exemplary embodiment, Figure 3 As shown, the preset calendar information includes the calendar corresponding to the resource type and the organization's business calendar.
[0073] Determine whether the initial resource adjustment date is a holiday based on the preset calendar information, including:
[0074] S302, extract the first holiday information from the calendar corresponding to the resource type, extract the second holiday information from the organization's business calendar, integrate the first holiday information and the second holiday information to obtain holiday list information, compare the initial resource adjustment date with the holiday list information, and determine whether the initial resource adjustment date is a holiday.
[0075] In this embodiment, the calendar information includes a calendar corresponding to the resource type and an institutional business calendar. Among them, the calendar corresponding to the resource type refers to the holiday arrangements of the country or region related to a specific resource (such as currency). These calendars usually include public holidays, special events and other non-working days that affect the relevant transactions and settlements of the resource. For example, if the contract involves foreign currencies such as the euro, it is necessary to refer to the holiday calendars of the eurozone member states. The institutional business calendar refers to the non-working day arrangements defined internally by financial institutions or other enterprises. These calendars include not only public holidays, but may also include special non-working days of the institution itself, such as system maintenance days, internal training days, and year-end settlement days.
[0076] In specific implementation, judging whether the initial resource adjustment date is a holiday can be: obtaining calendar information corresponding to the resource type, such as the currency calendar, extracting the first holiday information from the calendar information, obtaining the organization business calendar information, extracting the second holiday information from the organization business calendar information, then integrating the first holiday information and the second holiday information to obtain the integrated holiday list information, and then comparing the initial resource adjustment date with the holiday list information. If the initial resource adjustment date exists in the holiday list information, the initial resource adjustment date is judged to be a holiday. According to the contract feature data, the trained postponement rule recommendation model is called to predict the postponement rule matching the contract information. According to the predicted postponement rule, the initial resource adjustment date, the resource type, and the preset organization business calendar and calendar information corresponding to the resource type, the postponed target resource adjustment date is determined. Finally, the communication address information of the request object is obtained, and the target resource adjustment date information is pushed to the request object in a push manner. Further, the resource adjustment date is updated in the contract information, and the initial resource adjustment date is replaced with the target resource adjustment date to obtain the updated contract information, and the postponement processing of this resource adjustment date is completed. The postponed contract information will be synchronized to the business system and trigger a series of business processes such as subsequent bill adjustment and customer notification. If the initial resource adjustment date does not process the holiday list, the initial resource adjustment date is directly determined as the final target resource adjustment date.
[0077] In this embodiment, by combining the calendar corresponding to the resource type and the organization's business calendar, it is possible to more comprehensively and accurately determine whether the initial resource adjustment date handles holidays.
[0078] Considering the importance of the interest rate adjustment date, relevant approval personnel can approve and confirm it after the target interest rate adjustment date is determined. Figure 4 As shown, in an exemplary embodiment, after determining the postponed target resource adjustment date, the method further includes:
[0079] S600: Based on the target resource adjustment date and the preset approval process triggering condition, it is determined whether the preset postponed approval process needs to be triggered.
[0080] S620: When it is determined that the postponement approval process needs to be triggered, a postponement approval form is generated based on the target resource adjustment date and contract information, and the postponement approval form is submitted to the approval personnel for approval.
[0081] S640: When the deferred approval is approved, the initial resource adjustment date in the contract information is updated to the target resource adjustment date, and the contract information is updated.
[0082] The approval process triggering conditions are a series of conditions pre-set based on actual conditions, including but not limited to the extension days conditions and the contract importance conditions.
[0083] In actual application, after determining the target resource adjustment date, it can be: obtaining the preset approval process trigger condition, judging whether it is necessary to trigger the postponement approval process, if it is determined that the postponement days are greater than the day threshold such as 3 days based on the target resource adjustment date and the initial resource adjustment date, it is determined that the approval process needs to be triggered. Subsequently, based on the target resource adjustment date and the contract information, a postponement approval form is generated using a preset postponement approval form template; and the generated postponement approval form is pushed to the corresponding approval personnel through the preset list of approval personnel. After receiving the postponement approval form, the approval personnel approve whether the target resource adjustment date is feasible and complete the approval process. The server obtains the approval result of the approval personnel on the postponement approval form and judges whether the postponement approval form is approved; if the postponement approval form is approved, the contract information and the initial resource adjustment date are obtained, the initial resource adjustment date is updated to the target resource adjustment date, and the contract information is updated according to the updated resource adjustment date, and the updated contract information is stored in the contract database. It can be understood that in other embodiments, the postponement days threshold can also be other values, and other approval conditions can also be set.
[0084] In other embodiments, it is also possible to directly trigger the approval process without setting the approval process trigger condition after determining the target resource adjustment date, and after approval, the initial resource adjustment date in the contract information is updated to the target resource adjustment date, and the contract information is updated. The specific conditions may be determined according to actual conditions and are not limited here.
[0085] In this embodiment, by introducing the approval mechanism, the compliance and rationality of the resource adjustment day operation can be improved, and the possibility of resource adjustment errors can be reduced.
[0086] like Figure 5 As shown, in an exemplary embodiment, the contract characteristic data includes notification requirement data; after updating the contract information, the method further includes:
[0087] S700, obtaining preference data of the request object.
[0088] S720, determining a message push channel and a message push time according to the preference data and the notification requirement data.
[0089] S740: Push a resource adjustment message based on the message push time and push channel. The resource adjustment message includes an initial resource adjustment date, a target resource adjustment date, and a postponement rule.
[0090] The request object's preference data includes the request object's (usually a customer or user) personal preferences for the method and time of receiving messages. This data can help the system more accurately meet the user's personalized needs and improve the user experience. Notification requirement data refers to the specific requirements of the business, system or customer for message push, such as notification must be made within a certain time period, must be notified through a specific channel, etc. Message push channels include but are not limited to email, SMS and in-app notifications.
[0091] In specific implementation, the historical behavior data and personal information data of the request object can be obtained, and the data fusion technology can be used to clean and integrate the data to obtain the preference data of the request object. Subsequently, the optimal message push channel and push time are determined based on the notification requirement data in the contract information and the preference data of the request object. Subsequently, the preset message push template can be referred to, and the resource adjustment message can be generated based on the initial resource adjustment date, the target resource adjustment date, and the postponement rules, and the resource adjustment message can be pushed to the request object through the message middleware. If the request object does not confirm receipt of the message within the specified time, the resource adjustment message is pushed again through the message retry mechanism until the request object confirms receipt or the maximum number of retries is reached.
[0092] For example, if it is determined based on the preference data and notification requirement data that the customer prefers to receive messages via email and SMS, and hopes to receive them between 9 am and 5 pm on weekdays. The system requires that it must be sent 3 working days before the target resource adjustment date and sent by at least one electronic method. Assuming that the current date is April 10, 2023, the initial resource adjustment date is April 30, 2023 (Labor Day holiday), the deferral rule is "defer to the next working day", and the target resource adjustment date is May 4, 2023 (Thursday), then the target push time should be within the working hours of April 26, 2023. Based on the above content, the initial resource adjustment date, target resource adjustment date, deferral rule and other information are encapsulated to generate a resource adjustment message such as "Dear customer, according to your contract terms, the initial resource adjustment date is April 30, 2023. Since this date is a holiday, according to the deferral rule "defer to the next working day", the new target resource adjustment date is May 4, 2024. Please be aware and make corresponding preparations." Afterwards, the resource adjustment message will be pushed to customers via email during working hours on April 26, 2023.
[0093] In this embodiment, personalized message push can be achieved by combining preference data and notification requirement data to push resources to adjust messages to customers.
[0094] In an exemplary embodiment, after predicting the deferral rules that match the contract information, the method also includes: pushing a rule confirmation message to the requesting object, for the requesting object to confirm whether the target deferral rule needs to be changed, the rule confirmation message carries the deferral rules and preset optional deferral rules, and receives the confirmed deferral rules fed back by the requesting object.
[0095] Since the deferral rules are related to the next actual interest rate adjustment date and may affect the customer's business, after predicting the deferral rules that match the contract information, the predicted deferral rules can be pushed to the customer for the customer to confirm whether to adjust the initial resource adjustment date according to the predicted deferral rules. It is understandable that in other embodiments, business personnel can make it clear in advance that certain products and resources require unified resource adjustment rules, and customers cannot flexibly choose deferral rules. In actual applications, it is determined whether the customer needs to confirm the resource adjustment rules.
[0096] In specific implementation, it can be determined whether the deferral rule can be flexibly selected by the customer based on the contract type and the agreed information in the contract regarding whether the deferral rule can be flexibly determined by the customer. If it is determined that the deferral rule can be flexibly determined by the customer, the predicted deferral rule will be marked as the "recommended deferral rule". Subsequently, based on the recommended deferral rule and other optional deferral rules except the recommended deferral rule, rule confirmation information is generated, and a rule confirmation message carrying the recommended deferral rule and other optional deferral rules is pushed to the requesting object, so that the requesting object can confirm whether the recommended deferral rule needs to be adjusted. If adjustment is required, the requesting object can also filter out a deferral rule that meets the requesting object's expectations from other optional deferral rules.
[0097] If the requesting object confirms that the recommended deferral rule does not need to be changed, the recommended deferral rule will be determined as the target deferral rule, and the subsequent resource adjustment date calculation process will begin; if the requesting object selects other optional deferral rules, the deferral rule selected by the requesting object will be obtained and determined as the target deferral rule. Subsequently, based on the target deferral rule determined by the requesting object, the initial resource adjustment date, and the preset calendar information, the target resource adjustment date after deferral will be recalculated and pushed to the requesting object.
[0098] In this embodiment, by pushing the predicted deferral rule to the requesting object, the requesting object is allowed to determine whether the deferral rule is feasible, so that the finally determined interest rate adjustment date can meet the user's expectations.
[0099] In order to make a clearer description of the resource data processing method provided by the present application, the following is a specific embodiment and the attached Figure 6 To illustrate, this specific embodiment includes the following steps:
[0100] S100: receiving a resource adjustment request carrying a contract identifier sent by a request object.
[0101] S200, acquiring contract information corresponding to the contract identifier, and extracting contract characteristic data from the contract information, the contract characteristic data including a resource adjustment cycle and a resource adjustment date.
[0102] S300: Determine an initial resource adjustment date based on a resource adjustment cycle and a resource adjustment date.
[0103] S320: Based on the calendar information corresponding to the resource type and the organization's business calendar, determine whether the initial resource adjustment date is a holiday.
[0104] Specifically, the first holiday information can be extracted from the calendar corresponding to the resource type, the second holiday information can be extracted from the organization's business calendar, the first holiday information and the second holiday information can be integrated to obtain the holiday list information, the initial resource adjustment date can be compared with the holiday list information, and it can be determined whether the initial resource adjustment date is a holiday.
[0105] S400, when it is determined that the initial resource adjustment date is a holiday based on preset calendar information, the trained postponement rule recommendation model is called with the contract feature data as input to predict a postponement rule that matches the contract information.
[0106] S450: Push a rule confirmation message carrying the deferral rule to the request object, and receive the confirmed deferral rule fed back by the request object.
[0107] S520, determining the postponed target resource adjustment date according to the confirmed postponement rule, the initial resource adjustment date and the preset calendar information fed back by the request object, and pushing the target resource adjustment date to the request object.
[0108] S660, when it is determined that the deferred approval process needs to be triggered, a deferred approval form is generated and submitted to the approval personnel for approval. When the deferred approval is approved, the initial resource adjustment date in the contract information is updated to the target resource adjustment date, and the contract information is updated.
[0109] S760, pushing a resource adjustment message according to the preference data and the notification requirement data, the resource adjustment message including an initial resource adjustment date, a target resource adjustment date, and a postponement rule.
[0110] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.
[0111] Based on the same inventive concept, the embodiment of the present application also provides a resource data processing device for implementing the resource data processing method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in one or more resource data processing device embodiments provided below can refer to the above limitations on the resource data processing method, and will not be repeated here.
[0112] In an exemplary embodiment, Figure 7 As shown, a resource data processing device 700 is provided, comprising: a request receiving module 710, a data extraction module 720, a resource adjustment date determination module 730, a postponement rule recommendation module 740 and a target resource adjustment date determination module 750, wherein:
[0113] The request receiving module 710 is used to receive a resource adjustment request carrying a contract identifier sent by a request object.
[0114] The data extraction module 720 is used to obtain the contract information corresponding to the contract identifier, and extract the contract characteristic data from the contract information, where the contract characteristic data includes the resource adjustment cycle and the resource adjustment date.
[0115] The resource adjustment date determination module 730 is used to determine the initial resource adjustment date based on the resource adjustment cycle and the resource adjustment date.
[0116] The postponement rule recommendation module 740 is used to, when it is determined that the initial resource adjustment date is a holiday based on the preset calendar information, use the contract feature data as input, call the trained postponement rule recommendation model, and predict the postponement rule matching the contract information. The postponement rule recommendation model is trained based on the historical contract data carrying the postponement rule category label;
[0117] The target resource adjustment date determination module 750 is used to determine the postponed target resource adjustment date according to the postponement rule, the initial resource adjustment date and the preset calendar information, and push the target resource adjustment date to the request object.
[0118] In some exemplary embodiments, the preset calendar information includes a calendar corresponding to a resource type and an organization business calendar; Figure 8 As shown, the device also includes a data comparison module 732, which is used to extract the first holiday information from the calendar corresponding to the resource type, extract the second holiday information from the organization's business calendar, integrate the first holiday information and the second holiday information, obtain holiday list information, compare the initial resource adjustment date with the holiday list information, and determine whether the initial resource adjustment date is a holiday.
[0119] like Figure 8 As shown, in some exemplary embodiments, the device also includes a rule approval module 760, which is used to determine whether a preset deferred approval process needs to be triggered based on the target resource adjustment date and the preset approval process trigger condition. If it is determined that the deferred approval process needs to be triggered, a deferred approval form is generated based on the target resource adjustment date and the contract information, and the deferred approval form is submitted to the approval personnel for approval. If the deferred approval is approved, the initial resource adjustment date in the contract information is updated to the target resource adjustment date, and the contract information is updated.
[0120] In some exemplary embodiments, the contract characteristic data includes notification requirement data; Figure 8 As shown, the device also includes a message push module 770, which is used to obtain the preference data of the request object, determine the message push channel and message push time according to the preference data and notification requirement data, and push the resource adjustment message based on the message push time and push channel. The resource adjustment message includes the initial resource adjustment date, the target adjustment resource date and the resources.
[0121] In some exemplary embodiments, Figure 8 As shown, the device also includes a rule confirmation module 780, which is used to push a rule confirmation message to the request object so that the request object can confirm whether the deferral rule needs to be changed. The rule confirmation message carries the deferral rule and the preset optional deferral rule, and receives the confirmed deferral rule fed back by the request object.
[0122] Each module in the resource data processing device can be implemented in whole or in part by software, hardware, or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute operations corresponding to each module.
[0123] In an exemplary embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be shown in FIG9. The computer device includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. The processor, the memory and the input / output interface are connected via a system bus, and the communication interface is connected to the system bus via the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store data such as contract feature data, deferred rules and deferred rule recommendations. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal via a network connection. When the computer program is executed by the processor, a method is implemented.
[0124] Those skilled in the art will understand that the structure shown in FIG. 9 is merely a block diagram of a partial structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different arrangement of components.
[0125] In an exemplary embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the steps in any one of the resource data processing method embodiments described above are implemented.
[0126] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in any one of the resource data processing method embodiments described above are implemented.
[0127] In one embodiment, a computer program product is provided, including a computer program, which implements the steps in any one of the resource data processing method embodiments described above when executed by a processor.
[0128] A person of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment method can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., but are not limited to this.
[0129] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.
[0130] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.
Claims
1. A resource data processing method, characterized in that: The method comprises: Receive a resource adjustment request carrying a contract identifier sent by a request object; Acquire contract information corresponding to the contract identifier, and extract contract characteristic data from the contract information, wherein the contract characteristic data includes a resource adjustment period and a resource adjustment day; Determining an initial resource adjustment date based on the resource adjustment cycle and the resource adjustment date; When it is determined that the initial resource adjustment date is a holiday based on preset calendar information, the trained postponement rule recommendation model is called with the contract feature data as input to predict a postponement rule matching the contract information, wherein the postponement rule recommendation model is trained based on historical contract data carrying a postponement rule category label; According to the postponement rule, the initial resource adjustment date and the preset calendar information, the postponed target resource adjustment date is determined, and the target resource adjustment date is pushed to the request object.
2. The method according to claim 1, characterized in that The preset calendar information includes the calendar corresponding to the resource type and the institution's business calendar; Determining whether the initial resource adjustment date is a holiday based on preset calendar information includes: Extracting first holiday information from a calendar corresponding to the resource type, and extracting second holiday information from the organization's business calendar; Integrate the first holiday information and the second holiday information to obtain holiday list information; The initial resource adjustment date is compared with the holiday list information to determine whether the initial resource adjustment date is a holiday.
3. The method according to claim 1, characterized in that After determining the postponed target resource adjustment date, the following steps are also included: Based on the target resource adjustment date and the preset approval process triggering condition, determining whether the preset postponed approval process needs to be triggered; If it is determined that the postponement approval process needs to be triggered, a postponement approval form is generated based on the target resource adjustment date and the contract information, and the postponement approval form is submitted to the approval personnel for approval; In a case where the deferred approval is approved, the initial resource adjustment date in the contract information is updated to the target resource adjustment date, and the contract information is updated.
4. The method according to claim 3, characterized in that The contract characteristic data includes notification requirement data; after the contract information is updated, the method further includes: Obtaining preference data of the request object; Determine a message push channel and a message push time according to the preference data and the notification requirement data; Based on the message push time and the push channel, a resource adjustment message is pushed, wherein the resource adjustment message includes an initial resource adjustment date, a target resource adjustment date, and a postponement rule.
5. The method according to any one of claims 1 to 4, characterized in that: After predicting the postponement rule matching the contract information, the method further includes: Pushing a rule confirmation message to the request object, so that the request object can confirm whether the postponement rule needs to be changed, the rule confirmation message carries the postponement rule and the preset optional postponement rule; Receiving the confirmed postponement rule fed back by the request object; Based on the confirmed postponement rule fed back by the requesting object, the initial resource adjustment date and the preset calendar information, the postponed target resource adjustment date is determined, and the target resource adjustment date is pushed to the requesting object.
6. The method according to any one of claims 1 to 4, characterized in that: The postponement rules include: no postponement, postponement to the next working day but not across a month, or postponement to the next working day across a month.
7. A resource data processing device, characterized in that: The device comprises: A request receiving module, used for receiving a resource adjustment request carrying a contract identifier sent by a request object; A data extraction module, used to obtain contract information corresponding to the contract identifier, and extract contract characteristic data from the contract information, wherein the contract characteristic data includes a resource adjustment period and a resource adjustment day; A resource adjustment date determination module, configured to determine an initial resource adjustment date based on the resource adjustment cycle and the resource adjustment date; A deferral rule recommendation module, for, when it is determined based on preset calendar information that the initial resource adjustment date is a holiday, using the contract feature data as input, calling a trained deferral rule recommendation model, and predicting a deferral rule matching the contract information, wherein the deferral rule recommendation model is trained based on historical contract data carrying deferral rule category labels; The target resource adjustment date determination module is used to determine the postponed target resource adjustment date according to the postponement rule, the initial resource adjustment date and the preset calendar information, and push the target resource adjustment date to the request object.
8. The device according to claim 7, characterized in that The preset calendar information includes a calendar corresponding to the resource type and an institutional business calendar. The device also includes a data comparison module, which is used to extract first holiday information from the calendar corresponding to the resource type, extract second holiday information from the institutional business calendar, integrate the first holiday information and the second holiday information to obtain holiday list information, compare the initial resource adjustment date with the holiday list information, and determine whether the initial resource adjustment date is a holiday.
9. The device according to claim 7, characterized in that The device also includes a rule approval module, which is used to determine whether a preset deferred approval process needs to be triggered based on the target resource adjustment date and the preset approval process trigger condition. If it is determined that the deferred approval process needs to be triggered, a deferred approval form is generated based on the target resource adjustment date and the contract information, and the deferred approval form is submitted to the approval personnel for approval. If the deferred approval is approved, the initial resource adjustment date in the contract information is updated to the target resource adjustment date, and the contract information is updated.
10. The device according to claim 9, characterized in that The contract characteristic data includes notification requirement data; the device also includes a message push module, which is used to obtain the preference data of the request object, determine the message push channel and message push time according to the preference data and the notification requirement data, and push a resource adjustment message based on the message push time and the push channel, and the resource adjustment message includes an initial resource adjustment date, a target adjusted resource date and resources.
11. The device according to any one of claims 7 to 10, characterized in that The device also includes a rule confirmation module, which is used to push a rule confirmation message to the request object so that the request object can confirm whether the deferral rule needs to be changed. The rule confirmation message carries the deferral rule and the preset optional deferral rule, and receives the confirmed deferral rule fed back by the request object.
12. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.
13. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.
14. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.
