A method, device and storage medium for modifying a resource scheduling record

Abstract

The application relates to the technical field of resource management, in particular to a resource scheduling record correction method and device, equipment and a storage medium. An unknown resource scheduling record is acquired, identification information of the unknown resource scheduling record is sent to a service node such as a host and / or a microservice, then identification information of to-be-corrected data determined based on the unknown resource scheduling record and returned by the service node, that is, the unknown resource scheduling record inconsistent with the resource scheduling record of the service node, is received, the to-be-corrected data is associated and compared with the unknown resource scheduling record according to the identification information of the to-be-corrected data, the resource scheduling record to be corrected is obtained, a correction request for correcting the resource scheduling record to be corrected is generated, and the correction request is sent to the service node, so that the service node corrects the resource scheduling record to be corrected. Based on the above-mentioned mode, on the one hand, the reliability of resource scheduling correction is ensured, and on the other hand, the correction efficiency of resource scheduling is improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of resource management, and particularly relates to a resource scheduling record correction method and device, equipment and a storage medium. BACKGROUND

[0002] In a distributed business core system, in order to ensure the consistency in the middle for resource scheduling events, for the inconsistent resource scheduling records after the day change, the consistency correction scheme after the event is needed to ensure the consistency of the resource scheduling records, specifically, generally includes the following steps: screening resource scheduling records, checking inconsistent resource scheduling records, and correcting inconsistent resource scheduling records.

[0003] Further, in order to ensure the consistency of the correction processing, before the inconsistent resource scheduling records are corrected, the corresponding resource scheduling correction service needs to be designed for each service node in the distributed business core system, and the corresponding account strategy is configured, so that when the inconsistent resource scheduling records are determined, the correction and adjustment are performed through resource scheduling. However, this way has the following defects in the implementation process:

[0004] 1. The reliability of resource scheduling cannot be guaranteed.

[0005] In the related art, the correction of inconsistent resource scheduling records is realized by designing the corresponding resource scheduling correction service for each service node.

[0006] However, in general scenarios, the above-mentioned resource scheduling correction service is newly developed and designed, and all possible application problems that may occur cannot be fully considered in the design stage, so it is difficult to guarantee the reliability of the resource scheduling for the correction of inconsistent resource scheduling records. In addition, if a resource scheduling event is added subsequently, the above-mentioned resource scheduling correction service needs to be designed synchronously, that is, the design and application of such high coupling exist the problem of complex design and maintenance in the distributed business core system.

[0007] 2. The processing efficiency of correction is low.

[0008] In the related art, if the inconsistent resource scheduling records are transmitted from the service node to the integration layer, an interface containing all field contents of the input message, the return message and the resource scheduling data area needs to be designed for the inconsistent resource scheduling records.

[0009] However, since the above-mentioned interface needs to consider all related data of the inconsistent resource scheduling records, the interface will be very long, which will increase the data transmission time for the target object, and increase the development, maintenance and error risks for the design and development personnel. SUMMARY

[0010] Embodiments of the present application provide a resource scheduling record correction method, device, equipment and storage medium, which are used to solve the problems of low processing efficiency and poor reliability of existing resource scheduling correction.

[0011] In a first aspect, the embodiments of the present application provide a resource scheduling record correction method, comprising:

[0012] obtaining an unknown resource scheduling record, and sending identification information of the unknown resource scheduling record to a service node, wherein the service node at least includes a host or a microservice;

[0013] receiving identification information of to-be-corrected data returned by the service node, the to-be-corrected data being determined based on the unknown resource scheduling record, wherein the to-be-corrected data is an unknown resource scheduling record inconsistent with a resource scheduling record of the service node;

[0014] associating and comparing the to-be-corrected data with the unknown resource scheduling record based on the identification information of the to-be-corrected data, to obtain a to-be-corrected resource scheduling record;

[0015] generating a correction request for correcting the to-be-corrected resource scheduling record based on the to-be-corrected resource scheduling record, and sending the correction request to the service node, so that the service node corrects the to-be-corrected resource scheduling record.

[0016] In a second aspect, the present application provides a resource scheduling record correction device, comprising:

[0017] a sending module, which obtains an unknown resource scheduling record, and sends identification information of the unknown resource scheduling record to a service node, wherein the service node at least includes a host or a microservice;

[0018] a receiving module, which receives identification information of to-be-corrected data returned by the service node, the to-be-corrected data being determined based on the unknown resource scheduling record, wherein the to-be-corrected data is an unknown resource scheduling record inconsistent with a resource scheduling record of the service node;

[0019] an association and comparison module, which associates and compares the to-be-corrected data with the unknown resource scheduling record based on the identification information of the to-be-corrected data, to obtain a to-be-corrected resource scheduling record;

[0020] a correction module, which generates a correction request for correcting the to-be-corrected resource scheduling record based on the to-be-corrected resource scheduling record, and sends the correction request to the service node, so that the service node corrects the to-be-corrected resource scheduling record.

[0021] In an optional embodiment, the sending module is specifically configured to:

[0022] determine a scheduling type of the unknown resource scheduling record, wherein the scheduling type comprises at least an outbound call or an inbound call;

[0023] if the scheduling type of the unknown resource scheduling record is the outbound call, send the identification information of the unknown resource scheduling record to a host;

[0024] if the call type of the unknown resource scheduling record is the inbound call, send the identification information of the unknown resource scheduling record to a micro service.

[0025] In an optional embodiment, the receiving module is further configured to:

[0026] receive identification information of to-be-corrected data returned by the service node based on the unknown resource scheduling record,

[0027] in response to receiving the identification information of the unknown resource scheduling record, judge whether the identification information of the unknown resource scheduling record matches identification information of a resource scheduling record of the service node;

[0028] if yes, establish a first association relationship between the unknown resource scheduling record and the resource scheduling record of the service node;

[0029] perform comparison between the unknown resource scheduling record and the resource scheduling record of the service node having the first association relationship, to obtain an inconsistent unknown resource scheduling record and the resource scheduling record of the service node in comparison result;

[0030] determine respective identification information of the inconsistent unknown resource scheduling record and the resource scheduling record of the service node in comparison result, and take the determined identification information as identification information of to-be-corrected data.

[0031] In an optional embodiment, after the determination of the identification information of the inconsistent unknown resource scheduling record and the identification information of the resource scheduling record of the service node, the receiving module is further configured to:

[0032] in response to the determination of the identification information of to-be-corrected data, send the to-be-corrected data and the identification information of the to-be-corrected data to a preset resource scheduling record database;

[0033] Based on the identification information of the to-be-corrected data, information archiving is performed on the to-be-corrected data.

[0034] In an optional embodiment, the associating and comparing the to-be-corrected data with the unknown resource scheduling record to obtain the to-be-corrected resource scheduling record, the associating and comparing module is specifically configured to:

[0035] In response to receiving the identification information of the to-be-corrected data, a second association relationship between the identification information of the to-be-corrected data and the identification information of the unknown resource scheduling record is established;

[0036] An association between the to-be-corrected data and the unknown resource scheduling record with the second association relationship is performed to obtain to-be-corrected data and resource scheduling records with inconsistent comparison results;

[0037] The identification information of the to-be-corrected data and the resource scheduling record with inconsistent comparison results is determined as the to-be-corrected resource scheduling record.

[0038] In an optional embodiment, the generating a correction request for correcting the to-be-corrected resource scheduling record based on the to-be-corrected resource scheduling record, the correction module is specifically configured to:

[0039] In response to satisfying a preset correction trigger condition, a resource scheduling access identifier for correcting the to-be-corrected resource scheduling record is determined, wherein the correction trigger condition at least includes: reaching a preset trigger time, satisfying a preset trigger period, and receiving a correction trigger instruction;

[0040] From a preset resource configuration scheme set, a target resource configuration scheme corresponding to the resource scheduling access identifier is determined;

[0041] The target resource configuration scheme is used to configure a correction request for correcting the to-be-corrected resource scheduling record.

[0042] In an optional embodiment, after the correction request is sent to the service node to enable the service node to correct the to-be-corrected resource scheduling record, the correction module is further configured to:

[0043] Receive a correction response result of the service node in response to the correction request, which is generated based on the correction request for consistent resource scheduling of the to-be-corrected resource scheduling record;

[0044] Based on the correction response result, state change information corresponding to the to-be-corrected resource scheduling record is obtained, wherein the state change information represents the change of the scheduling state of the to-be-corrected resource scheduling record;

[0045] The state change information is used to adjust the scheduling state of the to-be-corrected resource scheduling record.

[0046] In an optional embodiment, the identification information of the resource scheduling record includes a resource scheduling event identifier corresponding to the resource scheduling record and a sub-resource scheduling event identifier corresponding to the resource scheduling record.

[0047] The resource scheduling event identifier is used to uniquely identify the resource scheduling event.

[0048] Therefore, different resource scheduling records generated based on the resource scheduling event all carry the same resource scheduling event identifier.

[0049] The resource scheduling sub-event identifier is used to identify a resource scheduling record generated for the resource scheduling event.

[0050] Therefore, different resource scheduling records generated based on the resource scheduling event all carry different resource scheduling sub-event identifiers.

[0051] In a third aspect, the embodiments of the present application further provide an electronic device including a memory and a processor, the memory storing a computer program capable of running on the processor, and when the computer program is executed by the processor, the processor implements any of the resource scheduling record correction methods in the first aspect.

[0052] In a fourth aspect, the embodiments of the present application further provide a computer readable storage medium, the computer readable storage medium storing a computer program, and when the computer program is executed by a processor, the resource scheduling record correction method in the first aspect is implemented.

[0053] In a fifth aspect, the embodiments of the present application further provide a computer program product, when the computer program product is invoked by a computer, the computer executes the method in the first aspect.

[0054] The embodiments of the present application provide a resource scheduling record correction method, device, electronic device and storage medium. An unknown resource scheduling record is obtained, and identification information of the unknown resource scheduling record is sent to a service node, such as a host and / or a microservice. Then, identification information of to-be-corrected data determined based on the unknown resource scheduling record, i.e., an unknown resource scheduling record inconsistent with a resource scheduling record of the service node, is received from the service node. Further, according to the identification information of the to-be-corrected data, the to-be-corrected data is associated and compared with the unknown resource scheduling record to obtain a to-be-corrected resource scheduling record. A correction request for correcting the to-be-corrected resource scheduling record is generated, and the correction request is sent to the service node, so that the service node corrects the to-be-corrected resource scheduling record.

[0055] The modification method of the resource scheduling record provided by the embodiments of the present application returns the identification information of the to-be-modified data by the service node, which can reduce the data amount between information transmission, and further improve the processing performance and implementation efficiency of the physical device. In addition, because only the identification information of the to-be-modified data returned by the service node is received, the design of the data receiving interface does not need to consider the content field of the to-be-modified data in different business scenarios. In other words, the design process in the above modification process can be simplified, thereby reducing the coupling degree requirement of the content field of the to-be-modified data in the modification process, and avoiding the need for repeated design for different application scenarios due to the requirement of the content field of the to-be-modified data in different application scenarios. On the other hand, the modification method of the resource scheduling record provided by the embodiments of the present application does not need to design and develop a resource scheduling modification service for the specific business requirement of the application scenario when applied to various application scenarios, thereby improving the applicability of the modification processing of the resource scheduling record in different application scenarios, avoiding the problems of long development period and difficult maintenance, and further achieving the technical effects of simplifying the modification processing flow and improving the reliability of resource scheduling. BRIEF DESCRIPTION OF DRAWINGS

[0056] Figure 1 The modification method of the resource scheduling record provided by the embodiments of the present application is shown in the schematic diagram;

[0057] Figure 2 A possible application scenario architecture diagram is provided for the embodiments of the present application;

[0058] Figure 3 The modification method of the resource scheduling record provided by the embodiments of the present application is shown in the flowchart;

[0059] Figure 4 The schematic diagram of distributing unknown resource scheduling records is provided for the embodiments of the present application;

[0060] Figure 5 The first schematic diagram of screening unknown resource scheduling records is provided for the embodiments of the present application;

[0061] Figure 6 The second schematic diagram of screening unknown resource scheduling records is provided for the embodiments of the present application;

[0062] Figure 7 The schematic diagram of generating to-be-modified resource scheduling records is provided for the embodiments of the present application;

[0063] Figure 8 The schematic diagram of the modification device of the resource scheduling record is provided for the embodiments of the present application;

[0064] Figure 9An electronic device schematic diagram provided by an embodiment of the present application. DETAILED DESCRIPTION

[0065] The technical solutions in the embodiments of the present application will be clearly and completely described in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by a person of ordinary skill in the art without creative work fall within the protection scope of the present application.

[0066] It should be noted that, in the description of the present application, "a plurality of" is understood as "at least two". The association relationship of the associated objects is described, which means that there can be three relationships, for example, A and / or B can mean that A exists alone, A and B exist together, and B exists alone. A and B are connected, which means that A and B are directly connected and A and B are connected through C. In addition, in the description of the present application, "first", "second", and the like are used only for the purpose of distinguishing the description, and cannot be understood as indicating or implying relative importance, nor indicating or implying order.

[0067] In addition, in the technical solutions of the present application, the collection, transmission, use, etc. of data all meet the requirements of relevant national laws and regulations.

[0068] In order to facilitate those skilled in the art to understand, first, some terms and terms related to the embodiments of the present application are briefly described and explained as follows:

[0069] Day change: refers to the time of changing the system resource scheduling, that is, the system switches from the current working day to the next working day, in addition, if resource scheduling occurs during the day change process, it can be submitted and correctly handled as usual.

[0070] For example, in the embodiments of the present application, for bank business, there is a corresponding end time for daily operation, after the time, the business that has not been completed for the day needs to be centrally processed under the condition of legality and compliance, and the business data of the day is cleared, so as to make all preparations for accepting the next day business, and the process of switching the day to the next day is regarded as day change. In some more specific scenarios, inconsistent resource scheduling records before day change need to be centrally processed to ensure that each resource scheduling event and its corresponding resource scheduling record can remain consistent after day change.

[0071] Resource: refers to the total of all material, financial and human resources in the region, specifically, it can be divided into two categories of natural resources and social resources. Among them, natural resources can include sunlight, air, water, forest and other material resources; social can include human resources, information resources and various material wealth created by labor.

[0072] For example, in the embodiments of the present application, the schedulable resources of the target object can represent the transaction funds stored in the savings account of the target object, and in some more specific scenarios, can also refer to the schedulable assets such as foreign currencies held by the target object in a legal and compliant manner, and the present application does not make any limitation in this regard.

[0073] Resource scheduling: refers to the process of effectively adjusting, analyzing, measuring or using the schedulable resources in a certain time range under the relevant scene.

[0074] For example, in the embodiments of the present application, the target object can initiate a resource scheduling request of a specified savings amount or margin amount to the bank based on the total amount of funds under the savings account and / or the total amount of margin under the corresponding margin account, so as to ensure the normal transaction between the two parties.

[0075] Resource scheduling record: information compliance record made on the source of funds held by the target object, details and other related information.

[0076] For example, in the embodiments of the present application, the distributed business core system can be provided with the resource scheduling record required for the target object to handle the business such as transaction flow, source of funds, risk rating, and in some more specific scenarios, can also include the flow record of the target object's own funds transaction, the handling period of the target configuration account bound by the target object, the compliance level of the target object's own funds, etc., to record the business change of the target object under the actual condition.

[0077] Resource configuration scheme: a scheduling scheme configured for the to-be-corrected resource scheduling record under the target scene, which is commonly used to meet the correction needs of the to-be-corrected resource scheduling record under the target scene.

[0078] For example, in the embodiments of the present application, the distributed business core system can regard the modification logic or product used to realize the correction of the to-be-corrected resource scheduling record under the target scene as a resource configuration scheme for the correction needs of the target scene; specifically, in the embodiments of the present application, the target object can determine the resource configuration scheme corresponding to the resource scheduling access identifier, which is used for consistent correction operation of the to-be-corrected resource scheduling record, and further meets the correction needs of the inconsistent resource scheduling records generated based on the same target resource scheduling under the target scene.

[0079] Further, based on the above explanations of the terms and related terms, the design idea of the present application will be further described and explained as follows:

[0080] In the modification scenario of the resource scheduling record, the integration layer generally filters out unknown resource scheduling records with the scheduling type of internal call and unknown resource scheduling records with the scheduling type of external call from the access data in the unknown state based on the scheduling type of the resource scheduling record, and then distributes the unknown resource scheduling records with different scheduling types to the service node. Specifically, the resource scheduling event identifier of the unknown resource scheduling record with internal call is sent to the host, and the resource scheduling event identifier of the unknown resource scheduling record with external call is sent to the microservice.

[0081] At the service node end, the host filters out the to-be-modified data based on the unknown resource scheduling record with internal call sent by the integration layer, and returns the to-be-modified data to the integration layer. The microservice filters out the to-be-modified data based on the unknown resource scheduling record with external call sent by the integration layer, and returns the to-be-modified data to the integration layer. The to-be-modified data includes the inconsistent resource scheduling record, the input message, the return message, and all field contents in the resource scheduling data area.

[0082] At the integration layer end, the integration layer associates and compares the to-be-modified data returned by the service node with the unknown resource scheduling record, generates the to-be-modified resource scheduling record, and then initiates a modification request for the resource scheduling processing of the to-be-modified resource scheduling record.

[0083] Further, the system application needs to design a corresponding resource scheduling modification service for each service node, design an assembly interface of a corresponding resource scheduling request message, and configure a mapping rule of the original resource scheduling record-resource scheduling modification processing and the resource scheduling modification request message assembly for the same. The resource scheduling modification service refers to a service called to modify the original abnormal resource scheduling event. Further, after the resource scheduling modification request message is assembled, the corresponding resource scheduling modification service of the service node is called for modification processing.

[0084] However, the related art still has the following defects:

[0085] 1. The reliability of resource scheduling cannot be guaranteed.

[0086] In the related art, the modification service of resource scheduling is newly developed and designed, and all possible application problems cannot be comprehensively considered in the design stage. Therefore, it is difficult to guarantee the reliability of resource scheduling after the inconsistent resource scheduling record is modified.

[0087] 2. The development workload is large.

[0088] In the related art, if a new resource scheduling event is added, the correction service of the above resource scheduling needs to be designed synchronously, that is, the design with high coupling is applied to the distributed business core system, which causes complex design maintenance and leads to huge development workload.

[0089] 3. The corrected processing efficiency is low.

[0090] In the related art, the service node returns the to-be-corrected data to the integration layer, and the to-be-corrected data includes inconsistent resource scheduling record input messages, return messages, and all field contents in the resource scheduling data area, which will cause a very large amount of interactive data between the integration layer and the service node, and further affect the transmission performance of the service node to the integration layer.

[0091] 4. The interactive data is redundant.

[0092] In the related art, all related data of inconsistent resource scheduling records need to be considered, so the interface for data transmission is designed to be very long, which increases the data transmission time for the target object and increases the development, maintenance, and error risks for the design and development personnel.

[0093] To solve the above defects in the related art and further improve the operation efficiency of business handling, embodiments of the present application provide a correction method and device of resource scheduling record, an electronic device and a storage medium, as shown in the following Figure 1 The unknown resource scheduling record is obtained, and the identification information of the unknown resource scheduling record is sent to the service node such as a host and / or a microservice. Then, the identification information of the to-be-corrected data returned by the service node based on the unknown resource scheduling record is received, that is, the unknown resource scheduling record inconsistent with the resource scheduling record of the service node. Further, according to the identification information of the to-be-corrected data, the to-be-corrected data is associated and compared with the unknown resource scheduling record to obtain the to-be-corrected resource scheduling record, and a correction request for correcting the to-be-corrected resource scheduling record is generated. Then, the correction request is sent to the service node, so that the service node corrects the to-be-corrected resource scheduling record.

[0094] The modification method of the resource scheduling record provided by the embodiments of the present application returns the identification information of the to-be-modified data by the service node, which can reduce the data amount between information transmission, and further improve the processing performance and implementation efficiency of the entity device. In addition, because only the identification information of the to-be-modified data returned by the service node is received, the design of the data receiving interface does not need to consider the content field of the to-be-modified data in different business scenarios. In other words, the design process in the above modification process can be simplified, thereby reducing the coupling degree requirement of the content field of the to-be-modified data in the modification process, and avoiding the need for repeated design for different application scenarios due to the requirement of the content field of the to-be-modified data in different application scenarios. On the other hand, the modification method of the resource scheduling record provided by the embodiments of the present application does not need to design and develop a resource scheduling modification service for the specific business requirement of the application scenario when applied to various application scenarios, thereby improving the applicability of the modification processing of the resource scheduling record for different application scenarios, avoiding the problems of long development period and difficult maintenance, and further achieving the technical effects of simplifying the modification processing flow and improving the reliability of resource scheduling.

[0095] Based on the above technical effects, the preferred embodiments of the present application are described below in conjunction with the drawings of the specification. It should be understood that the preferred embodiments described herein are only used to illustrate and explain the present application, and do not limit the present application, and the embodiments and features in the embodiments can be combined with each other without conflict.

[0096] Referring to Figure 2 The figure is a possible application scenario architecture provided by the embodiments of the present application, mainly for the modification of the resource scheduling record of the distributed business core system. Specifically, the application scenario architecture includes an integration layer and a service node, and the service node includes a host and a microservice.

[0097] Among them, the resource scheduling of the host refers to the service running on the mainframe, and the microservice refers to the atomic service provided on the distributed business core system.

[0098] For example, in the embodiments of the present application, the modification of the resource scheduling record refers to the modification of the original abnormal resource scheduling event. In some more specific scenarios, when a resource scheduling event needs to perform two resource scheduling actions of transfer out and transfer in, the account transferred out is on the host (mainframe) system, and the account transferred in has been migrated to the distributed business core system. If the resource scheduling fails, a consistency modification means is needed to ensure the consistency of the two, that is, both transfer out and transfer in are successful or both fail. Further, when the consistency modification means fails, a resource scheduling modification operation is needed to be performed to transfer the transferred resource back to the transferred account or add the corresponding transferred resource to the transferred account.

[0099] Based on the above application scenarios, the service handling method provided by the embodiments of the present application will be further described and explained in combination with the accompanying drawings. Referring to FIG. 1, the embodiments of the present application provide a resource scheduling record modification method, which comprises the following steps: Figure 3 The embodiments of the present application provide a resource scheduling record modification method, which comprises the following steps:

[0100] Step 301: Obtain an unknown resource scheduling record, and send identification information of the unknown resource scheduling record to a service node.

[0101] The identification information at least comprises a resource scheduling event identification corresponding to the resource scheduling record, and a sub-resource scheduling event identification corresponding to the resource scheduling record. Here, if the resource scheduling event identification is used to uniquely identify a resource scheduling event, then different resource scheduling records generated based on the resource scheduling event carry the same resource scheduling event identification; if the resource scheduling sub-event identification is used to identify a resource scheduling record generated for a resource scheduling event, then different resource scheduling records generated based on the resource scheduling event all carry different resource scheduling sub-event identifications.

[0102] Specifically, a resource scheduling event may pass through multiple systems and multiple deployment units, that is, multiple sub-resource scheduling events (atomic resource scheduling events) are invoked. Further, in the calling process of resource scheduling across systems, the resource scheduling record of each sub-resource scheduling event carries the same resource scheduling event identification and different resource scheduling sub-event identifications. In some more specific scenarios, in response to that the background system A receives a resource scheduling sub-event a initiated by a target object, the background system A invokes a resource scheduling sub-event b on the system B and a resource scheduling sub-event c on the system C, respectively, then the resource scheduling record of each of the resource scheduling sub-event a, the resource scheduling sub-event b and the resource scheduling sub-event c contains the same resource scheduling event identification, and based on the calling sequence of each resource scheduling sub-event, the resource scheduling sub-event identification is generated in sequence, that is, the resource scheduling record of each of the resource scheduling sub-event a, the resource scheduling sub-event b and the resource scheduling sub-event c contains the resource scheduling sub-event identification which is sequentially increased.

[0103] In addition, the above resource scheduling record refers to the information required by the system to process the resource scheduling (sub) event. Optionally, the resource scheduling record is a request message (i.e. input message) of the resource scheduling (sub) event. For example, for the resource scheduling (sub) event of withdrawing money, the request message can include an account card number, a verification password, a withdrawal amount, etc.

[0104] In the embodiments of the present application, as shown in FIG. 2, the resource scheduling record modification method comprises the following steps: Figure 4The diagram illustrates a method for distributing unknown resource scheduling records. The integration layer filters the acquired access data, selecting unknown resource scheduling records with unknown status. Then, based on the scheduling type of each unknown resource scheduling record, it sends the identification information of unknown resource scheduling records with outbound call scheduling type to the host and sends the identification information of unknown resource scheduling records with inbound call scheduling type to the microservice.

[0105] Step 302: Receive the identification information of the data to be corrected, which is determined based on the unknown resource scheduling record, returned by the service node.

[0106] Specifically, in this embodiment of the application, in order to reduce the amount of interactive data during transmission, after sending unknown resource scheduling records to the host and microservices, the integration layer is used to receive the identification information of the data to be corrected returned by the host and microservices, wherein the data to be corrected is: unknown resource scheduling records that are inconsistent with the resource scheduling records of the host or microservices in the unknown resource scheduling records.

[0107] In an alternative embodiment, the above-mentioned filtering of data to be corrected for unknown resource scheduling records can be performed by the host and microservices.

[0108] For example, such as Figure 5 As shown, for the host, in response to receiving the identification information of an unknown resource scheduling record sent by the integration layer, the unknown resource scheduling record is identified and downloaded (i.e., obtained). Then, for the unknown resource scheduling records whose identification information matches, the integration layer sends outbound calls to, and the host's resource scheduling records, a first association is established. Each resource scheduling record with the first association is compared, and resource scheduling records with inconsistent comparison results are treated as data to be corrected. These inconsistent resource scheduling records (data to be corrected) are uploaded (i.e., saved). Finally, the identification information of the data to be corrected is returned to the integration layer. Since the data returned by the host to the integration layer is the identification information of the data to be corrected, in other words, it is not necessary to return the relevant data of the data to be corrected, such as the input messages, return messages, and all field contents of the resource scheduling data area of ​​the inconsistent resource scheduling records. Therefore, the goal of reducing the amount of interactive data can be achieved, thereby improving the processing performance and implementation efficiency of the physical device.

[0109] For example, such as Figure 6As shown, for the microservice, in response to receiving the identification information of the unknown resource scheduling record sent by the integration layer, the unknown resource scheduling record is determined, and the resource scheduling record of the microservice is downloaded (i.e., downloaded, acquired), then for the unknown resource scheduling record sent by the integration layer and the resource scheduling record of the microservice that match the identification information, a first association relationship is established, and each resource scheduling record with the first association relationship is compared, then the resource scheduling records with inconsistent comparison results are taken as the to-be-corrected data, and the inconsistent resource scheduling records (to-be-corrected data) are uploaded (i.e., uploaded, saved), and finally the identification information of the to-be-corrected data is returned to the integration layer. Since the data returned by the microservice to the integration layer is the identification information of the to-be-corrected data, in other words, it is not necessary to return the related data of the to-be-corrected data, such as the input message, the return message and all field contents in the resource scheduling data area of the inconsistent resource scheduling record, so that the purpose of reducing the amount of interactive data can be achieved, and the processing performance and implementation efficiency of the entity device are improved.

[0110] Optionally, the implementation of uploading the to-be-corrected data can be that the inconsistent resource scheduling records and the identification information thereof are sent to a preset resource scheduling record database, and information archiving is performed on the newly added to-be-corrected data in the preset resource scheduling record database. In some more specific scenarios, the preset resource scheduling record database can refer to a historical resource scheduling record table. By uploading the to-be-corrected data, when the integration layer initiates a correction request in the subsequent step, the corresponding data can be directly obtained from the preset resource scheduling record database to complete the correction processing.

[0111] Step 303: based on the identification information of the to-be-corrected data, the to-be-corrected data is associated and compared with the unknown resource scheduling record, and a to-be-corrected resource scheduling record is obtained.

[0112] In the embodiment of the application, for the integration layer, in response to receiving the identification information of the to-be-corrected data returned by the host or the microservice, each inconsistent resource scheduling record in the to-be-corrected data is determined, then based on the unknown resource scheduling record, for the inconsistent resource scheduling record and the unknown resource scheduling record that match the identification information, a second association relationship is established, and each resource scheduling record with the second association relationship is compared, and a final to-be-corrected resource scheduling record is obtained.

[0113] For example, Figure 7As shown, for the integration layer, the unknown resource scheduling record of the outbound call scheduling type of the integration layer is associated and compared with the to-be-corrected data returned by the host to generate the to-be-corrected resource scheduling record of the outbound call scheduling type, that is, the data for accessing the resource scheduling correction operation, and the to-be-corrected resource scheduling record is filed. Similarly, the unknown resource scheduling record of the inbound call scheduling type of the integration layer is associated and compared with the to-be-corrected data returned by the microservice to generate the to-be-corrected resource scheduling record of the inbound call scheduling type, that is, the data for accessing the resource scheduling correction operation, and the to-be-corrected resource scheduling record is filed. Further, the resource scheduling access identifier of the to-be-corrected resource scheduling record is determined, and the preliminary determined to-be-corrected resource scheduling record is associated and compared with the unknown resource scheduling flow of the integration layer to generate the final to-be-corrected resource scheduling record for accessing the resource scheduling correction operation, and the to-be-corrected resource scheduling record is filed.

[0114] Optionally, the resource scheduling access identifier can be a resource scheduling event identifier, or a flow number. In some cases, the flow number can include a resource scheduling event identifier.

[0115] Step 304: Based on the to-be-corrected resource scheduling record, a correction request for correcting the to-be-corrected resource scheduling record is generated, and the correction request is sent to the service node, so that the service node corrects the to-be-corrected resource scheduling record.

[0116] In order to reduce the development workload, improve the processing efficiency of correction, and ensure the reliability of the resource scheduling process, in the embodiment of the application, the correction processing is performed in the way of correcting on the next day. In some more specific scenarios, it is applicable when the consistency guarantee of the same day is unsuccessful, such as system failure such as shutdown, or business reasons such as insufficient balance, account state anomaly, etc. Then, after screening the to-be-corrected resource scheduling record, the resource scheduling correction processing is performed in the way of correcting after ensuring the correct state of the next day, thereby avoiding modification of various database tables and avoiding the uncertainty of resource scheduling and huge development workload caused by redeveloping the correction service of resource scheduling.

[0117] Specifically, in response to satisfying a preset correction trigger condition, a resource scheduling access identifier for correcting the to-be-corrected resource scheduling record is determined, and then a target resource configuration scheme corresponding to the resource scheduling access identifier is determined from a preset resource configuration scheme set, and the target resource configuration scheme is used to configure a correction request for correcting the to-be-corrected resource scheduling record. Here, the correction trigger condition at least includes one of the following three cases or a combination: the current time reaches a preset trigger time; the current time satisfies a preset trigger period; and a trigger instruction for indicating correction sent by a target object is received.

[0118] For example, in an embodiment of the present application, for the application scenario of fund transaction, the above-mentioned resource scheduling access identifier can be a transaction code, which is a unique code of a function. For example, the transaction code of a debit card transfer is A00000001, and the transaction code of an ATM (Automated Teller Machine) withdrawal is A00000002.

[0119] Further, in the embodiment of the present application, after sending the correction request to the host and / or microservice to make the host and / or microservice correct the to-be-corrected resource scheduling record, a correction response result of the host and / or microservice based on the correction request is received, the correction response result being generated by the host and / or microservice for the consistent resource scheduling of the to-be-corrected resource scheduling record. Then, based on the correction response result, state change information corresponding to the to-be-corrected resource scheduling record is obtained, i.e., the change of the scheduling state of the to-be-corrected resource scheduling record. Then, the state change information is used to correct the scheduling state of the to-be-corrected resource scheduling record.

[0120] In summary, the correction method of the resource scheduling record provided in the embodiment of the present application can reduce the amount of data in information transmission by returning the identification information of the to-be-corrected data from the service node, thereby improving the processing performance and implementation efficiency of the entity device. In addition, because only the identification information of the to-be-corrected data returned by the service node is received, the design of the data receiving interface does not need to consider the content field of the to-be-corrected data in different business scenarios. In other words, the design process in the above-mentioned correction process can be simplified, thereby reducing the coupling degree requirement of the content field of the to-be-corrected data in the correction process and avoiding the need for repeated design for different application scenarios due to the requirement of the content field of the to-be-corrected data in different application scenarios. On the other hand, the correction method of the resource scheduling record provided in the embodiment of the present application does not need to design and develop a resource scheduling correction service for a specific business requirement of an application scenario when applied to various application scenarios, thereby improving the applicability of the correction processing of the resource scheduling record for different application scenarios and avoiding the problems of long development period and difficult maintenance, thereby achieving the technical effects of simplifying the correction processing flow and improving the reliability of resource scheduling.

[0121] Referring to Figure 8 The embodiment of the present application provides a resource scheduling record correction device, which comprises a sending module 801, a receiving module 802, an association comparison module 803 and a correction module 804, wherein:

[0122] The sending module 801 acquires an unknown resource scheduling record and sends identification information of the unknown resource scheduling record to a service node, wherein the service node at least comprises a host or a microservice.

[0123] The receiving module 802 receives identification information of to-be-corrected data returned by the service node based on the unknown resource scheduling record, wherein the to-be-corrected data is an unknown resource scheduling record inconsistent with the resource scheduling record of the service node;

[0124] The association comparison module 803 performs association comparison between the to-be-corrected data and the unknown resource scheduling record based on the identification information of the to-be-corrected data, to obtain a to-be-corrected resource scheduling record;

[0125] The correction module 804 generates a correction request for correcting the to-be-corrected resource scheduling record based on the to-be-corrected resource scheduling record, and sends the correction request to the service node, so that the service node corrects the to-be-corrected resource scheduling record.

[0126] In an optional embodiment, the sending module 801 is specifically configured to:

[0127] determine a scheduling type of the unknown resource scheduling record, wherein the scheduling type at least includes an outbound call or an inbound call;

[0128] if the scheduling type of the unknown resource scheduling record is the outbound call, send the identification information of the unknown resource scheduling record to a host;

[0129] if the call type of the unknown resource scheduling record is the inbound call, send the identification information of the unknown resource scheduling record to a microservice.

[0130] In an optional embodiment, the receiving module 802 receives identification information of to-be-corrected data returned by the service node based on the unknown resource scheduling record,

[0131] the service node determines the identification information of the to-be-corrected data based on the unknown resource scheduling record, and the receiving module 802 is further configured to:

[0132] in response to receiving the identification information of the unknown resource scheduling record, judge whether the identification information of the unknown resource scheduling record matches the identification information of the resource scheduling record of the service node;

[0133] if yes, establish a first association relationship between the unknown resource scheduling record and the resource scheduling record of the service node;

[0134] perform comparison between the unknown resource scheduling record and the resource scheduling record of the service node having the first association relationship, to obtain an unknown resource scheduling record and the resource scheduling record of the service node with inconsistent comparison results.

[0135] determine the identification information of the inconsistent unknown resource scheduling record and the resource scheduling record of the service node, and take the determined identification information as the identification information of the to-be-corrected data.

[0136] In an optional embodiment, after determining the identification information of the inconsistent unknown resource scheduling record and the identification information of the resource scheduling record of the service node, and taking the determined identification information as the identification information of the to-be-corrected data, the receiving module 802 is further configured to:

[0137] in response to determining the identification information of the to-be-corrected data, sending the to-be-corrected data and the identification information of the to-be-corrected data to a preset resource scheduling record database;

[0138] based on the identification information of the to-be-corrected data, performing information archiving on the to-be-corrected data.

[0139] In an optional embodiment, the associating and comparing the to-be-corrected data with the unknown resource scheduling record to obtain the to-be-corrected resource scheduling record, the associating and comparing module 803 is specifically configured to:

[0140] in response to receiving the identification information of the to-be-corrected data, establishing a second association relationship between the identification information of the to-be-corrected data and the identification information of the unknown resource scheduling record;

[0141] performing comparison between the to-be-corrected data having the second association relationship and the unknown resource scheduling record to obtain to-be-corrected data and resource scheduling records with inconsistent comparison results;

[0142] determining the identification information of the to-be-corrected data and the resource scheduling record with inconsistent comparison results, as the to-be-corrected resource scheduling record.

[0143] In an optional embodiment, the generating a correction request for correcting the to-be-corrected resource scheduling record based on the to-be-corrected resource scheduling record, the correcting module 804 is specifically configured to:

[0144] in response to satisfying a preset correction trigger condition, determining a resource scheduling access identifier for correcting the to-be-corrected resource scheduling record, wherein the correction trigger condition at least includes: reaching a preset trigger time, satisfying a preset trigger period, and receiving a correction trigger instruction;

[0145] from a preset set of resource configuration schemes, determining a target resource configuration scheme corresponding to the resource scheduling access identifier;

[0146] The target resource configuration scheme is used to configure a correction request for correcting the to-be-corrected resource scheduling record.

[0147] In an optional embodiment, after the correction request is sent to the service node to enable the service node to correct the to-be-corrected resource scheduling record, the correction module 804 is further configured to:

[0148] receive a correction response result of the service node in response to the correction request, the correction response result being generated based on the correction request and being used to perform consistent resource scheduling on the to-be-corrected resource scheduling record;

[0149] obtain state change information corresponding to the to-be-corrected resource scheduling record based on the correction response result, the state change information being used to represent a change in a scheduling state of the to-be-corrected resource scheduling record;

[0150] use the state change information to adjust the scheduling state of the to-be-corrected resource scheduling record.

[0151] In an optional embodiment, the identification information of the resource scheduling record includes a resource scheduling event identifier corresponding to the resource scheduling record and a sub-resource scheduling event identifier corresponding to the resource scheduling record.

[0152] The resource scheduling event identifier is used to uniquely identify the resource scheduling event.

[0153] Therefore, different resource scheduling records generated based on the resource scheduling event all carry the same resource scheduling event identifier.

[0154] The resource scheduling sub-event identifier is used to identify a resource scheduling record generated for the resource scheduling event.

[0155] Therefore, different resource scheduling records generated based on the resource scheduling event all carry different resource scheduling sub-event identifiers.

[0156] Based on the same inventive concept as the above application embodiments, the present application embodiments also provide an electronic device, which can be used for correcting a resource scheduling record. In an embodiment, the electronic device can be a server, a terminal device, or other electronic devices. In this embodiment, the structure of the electronic device can be as shown in Figure 9 The electronic device includes a memory 901, a communication interface 903, and one or more processors 902.

[0157] The memory 901 is configured to store a computer program executed by the processor 902. The memory 901 can mainly include a program storage area and a data storage area, where the program storage area can store an operating system and programs required for running the instant messaging function, etc.; and the data storage area can store various instant messaging information and operation instruction sets, etc.

[0158] The memory 901 can be a volatile memory, for example, a random-access memory (RAM); or the memory 901 can be a non-volatile memory, for example, a read-only memory, a flash memory, a hard disk drive (HDD) or a solid-state drive (SSD), or the memory 901 can be any other medium capable of carrying or storing desired program codes in the form of instructions or data structures and capable of being accessed by a computer, but is not limited to this. The memory 901 can be a combination of the above memories.

[0159] The processor 902 can include one or more central processing units (CPUs) or digital processing units, etc. The processor 902 is configured to invoke the computer program stored in the memory 901 to implement the above-mentioned resource scheduling record correction method.

[0160] The communication interface 903 is configured to communicate with a terminal device and other servers.

[0161] The specific connection medium between the above-mentioned memory 901, communication interface 903 and processor 902 is not limited in the embodiments of the present application. In the embodiments of the present application, the memory 901 and the processor 902 are connected through a bus 904, and the bus 904 is represented by a thick line in the embodiments of the present application, and the connection mode between other components is only schematically illustrated and is not limited. The bus 904 can be divided into an address bus, a data bus, a control bus, etc. For convenience of representation, only one thick line is used to represent the bus 904 in the embodiments of the present application, but it does not mean that there is only one bus or only one type of bus. Figure 9 Figure 9 The connection mode between other components is only schematically illustrated and is not limited. The bus 904 can be divided into an address bus, a data bus, a control bus, etc. For convenience of representation, only one thick line is used to represent the bus 904 in the embodiments of the present application, but it does not mean that there is only one bus or only one type of bus. Figure 9

[0162] ​​According to an aspect of the present application, a computer program product or computer program is provided, which comprises computer instructions stored in a computer readable storage medium. A processor of a computer device reads the computer instructions from the computer readable storage medium, and the processor executes the computer instructions to cause the computer device to perform the method for modifying a resource scheduling record in any of the above embodiments. The program product can adopt any combination of one or more readable media. The readable medium can be a readable signal medium or a readable storage medium. The readable storage medium may, for example, be but is not limited to an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or apparatus, or any combination of the above. More specific examples (non-exhaustive list) of the readable storage medium include an electrical connection having one or more wires, a portable disc, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0163] According to an aspect of the present application, the present application also provides a computer program product which, when invoked by a computer, causes the computer to perform the method for modifying a resource scheduling record.

[0164] The embodiments of the present application provide a method and device for modifying a resource scheduling record, an electronic device and a storage medium. An unknown resource scheduling record is obtained, and identification information of the unknown resource scheduling record is sent to a service node, such as a host and / or a microservice. Then, identification information of to-be-modified data determined based on the unknown resource scheduling record, i.e., an unknown resource scheduling record inconsistent with the resource scheduling record of the service node, is received from the service node. Further, the to-be-modified data is associated and compared with the unknown resource scheduling record according to the identification information of the to-be-modified data, to obtain a to-be-modified resource scheduling record. A modification request for modifying the to-be-modified resource scheduling record is generated, and the modification request is sent to the service node, so that the service node modifies the to-be-modified resource scheduling record.

[0165] The method for modifying the resource scheduling record provided in the embodiments of the present application returns the identification information of the to-be-modified data from the service node, which can reduce the data amount between information transmission, and further improve the processing performance and implementation efficiency of the entity device. In addition, since only the identification information of the to-be-modified data returned by the service node is received, the design of the data receiving interface does not need to consider the content field of the to-be-modified data in different business scenarios. In other words, the design process in the above modification process can be simplified, thereby reducing the coupling degree requirement of the content field of the to-be-modified data in the modification process, and avoiding the need for repeated design for different application scenarios due to the requirement of the content field of the to-be-modified data in different application scenarios. On the other hand, the method for modifying the resource scheduling record provided in the embodiments of the present application does not need to design and develop a resource scheduling modification service for a specific business requirement of an application scenario when applied to various application scenarios, thereby improving the applicability of the modification processing of the resource scheduling record in different application scenarios, avoiding the problems of long development period and difficult maintenance, and further achieving the technical effects of simplifying the modification processing flow and improving the reliability of resource scheduling.

[0166] The present application is described with reference to the flowcharts and / or block diagrams according to the methods, devices (systems), and computer program products of the present application. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, and the combination of flows and / or blocks in the flowcharts and / or block diagrams can be implemented by computer program instructions. These computer program instructions can be provided to a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing devices to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing devices generate a means for implementing the functions specified in the flowcharts and / or block diagrams. Figure 1 The functions specified in one or more flows and / or blocks Figure 1 The functions specified in one or more flows and / or blocks.

[0167] These computer program instructions can also be stored in a computer-readable memory that can guide the computer or other programmable data processing devices to work in a specific way, so that the instructions stored in the computer-readable memory produce a product including instruction means, which implements the functions specified in the flowcharts and / or block diagrams. Figure 1 The functions specified in one or more flows and / or blocks Figure 1 The functions specified in one or more flows and / or blocks.

[0168] These computer program instructions can also be loaded into a computer or other programmable data processing device, so that a series of operation steps are performed on the computer or other programmable device to produce a computer-implemented process, so that the instructions executed on the computer or other programmable device provide a means for implementing the functions specified in the flowcharts and / or block diagrams. Figure 1 The functions specified in one or more flows and / or blocks Figure 1 Figure 1steps of the functions specified in the one or more blocks.

[0169] It will be apparent to those skilled in the art that various modifications and variations can be made to the present application without departing from the spirit or scope of the application. Thus, it is intended that the present application cover the modifications and variations of this application provided they come within the scope of the appended claims and their equivalents.

Claims

1. A method of modifying a resource scheduling record, characterized by, The method comprises the following steps: acquiring an unknown resource scheduling record, and sending identification information of the unknown resource scheduling record to a service node, wherein the service node comprises at least a host or a microservice; receiving identification information of to-be-corrected data returned by the service node, wherein the to-be-corrected data is an unknown resource scheduling record inconsistent with a resource scheduling record of the service node; based on the identification information of the to-be-corrected data, associating and comparing the to-be-corrected data with the unknown resource scheduling record to obtain a to-be-corrected resource scheduling record; based on the to-be-corrected resource scheduling record, generating a correction request for correcting the to-be-corrected resource scheduling record, and sending the correction request to the service node to make the service node correct the to-be-corrected resource scheduling record.

2. The method of claim 1, wherein, The step of sending the identification information of the unknown resource scheduling record to the service node comprises the following steps: determining a scheduling type of the unknown resource scheduling record, wherein the scheduling type comprises at least an outbound call or an inbound call; if the scheduling type of the unknown resource scheduling record is the outbound call, sending the identification information of the unknown resource scheduling record to the host; if the call type of the unknown resource scheduling record is the inbound call, sending the identification information of the unknown resource scheduling record to the microservice.

3. The method of claim 1, wherein, The step of receiving the identification information of the to-be-corrected data returned by the service node based on the unknown resource scheduling record comprises the following steps: in response to receiving the identification information of the unknown resource scheduling record, judging whether the identification information of the unknown resource scheduling record matches the identification information of the resource scheduling record of the service node; if yes, establishing a first association relationship between the unknown resource scheduling record and the resource scheduling record of the service node; performing comparison between the unknown resource scheduling record and the resource scheduling record of the service node having the first association relationship to obtain an unknown resource scheduling record and the resource scheduling record of the service node with inconsistent comparison results; determining the identification information of the unknown resource scheduling record and the resource scheduling record of the service node with inconsistent comparison results respectively, and taking the determined identification information as the identification information of the to-be-corrected data. After the step of determining the identification information of the unknown resource scheduling record and the identification information of the resource scheduling record of the service node with inconsistent comparison results, and taking the determined identification information as the identification information of the to-be-corrected data, the method further comprises the following steps:

4. The method of claim 3, wherein, in response to determining the identification information of the to-be-corrected data, sending the to-be-corrected data and the identification information of the to-be-corrected data to a preset resource scheduling record database; based on the identification information of the to-be-corrected data, performing information archiving on the to-be-corrected data. The step of associating and comparing the to-be-corrected data with the unknown resource scheduling record to obtain the to-be-corrected resource scheduling record comprises the following steps:

5. The method of claim 1, wherein, ​ In response to receiving the identification information of the to-be-corrected data, a second association relationship is established between the identification information of the to-be-corrected data and the identification information of the unknown resource scheduling record; A comparison is performed between the to-be-corrected data and the unknown resource scheduling record having the second association relationship, and a to-be-corrected data and a resource scheduling record with inconsistent comparison results are obtained; The identification information of the to-be-corrected data and the resource scheduling record with inconsistent comparison results is determined as a to-be-corrected resource scheduling record.

6. The method of claim 1, wherein, The to-be-corrected resource scheduling record is used to generate a correction request for correcting the to-be-corrected resource scheduling record, including: In response to satisfying a preset correction trigger condition, a resource scheduling access identifier for correcting the to-be-corrected resource scheduling record is determined, wherein the correction trigger condition at least includes: reaching a preset trigger time, satisfying a preset trigger period, and receiving a correction trigger instruction; From a preset resource configuration scheme set, a target resource configuration scheme corresponding to the resource scheduling access identifier is determined; The target resource configuration scheme is used to configure a correction request for correcting the to-be-corrected resource scheduling record.

7. The method of claim 1, wherein, After the correction request is sent to the service node to make the service node correct the to-be-corrected resource scheduling record, it further includes: A correction response result of consistent resource scheduling for the to-be-corrected resource scheduling record is generated based on the correction request in response to the service node; Based on the correction response result, state change information corresponding to the to-be-corrected resource scheduling record is obtained, wherein the state change information represents the change of the scheduling state of the to-be-corrected resource scheduling record; The state change information is used to adjust the scheduling state of the to-be-corrected resource scheduling record.

8. The method according to any one of claims 1 to 7, wherein, The identification information of the resource scheduling record includes: A resource scheduling event identifier for uniquely identifying a same resource scheduling event, Then, the same resource scheduling event identifier is carried in different resource scheduling records generated based on the same resource scheduling event; A resource scheduling tracking sequence includes at least one resource scheduling sub-event identifier, and the resource scheduling sub-event identifier is used to identify a resource scheduling record generated for the same resource scheduling event, Then, different resource scheduling sub-event identifiers are carried in different resource scheduling records generated based on the same resource scheduling event.

9. An apparatus for modifying a resource scheduling record, characterized by It includes: A sending module acquires an unknown resource scheduling record and sends identification information of the unknown resource scheduling record to a service node, wherein the service node at least includes a host or a microservice; A receiving module receives identification information of to-be-corrected data returned by the service node based on the unknown resource scheduling record, wherein the to-be-corrected data is an unknown resource scheduling record inconsistent with a resource scheduling record of the service node; An association comparison module performs association comparison between the to-be-corrected data and the unknown resource scheduling record based on the identification information of the to-be-corrected data, and obtains a to-be-corrected resource scheduling record. The correction module generates a correction request for correcting the to-be-corrected resource scheduling record based on the to-be-corrected resource scheduling record, and sends the correction request to the service node, so that the service node corrects the to-be-corrected resource scheduling record.

10. The apparatus of claim 9, wherein, The sending module is specifically configured to: determine a scheduling type of the unknown resource scheduling record, wherein the scheduling type at least includes an outbound call or an inbound call; if the scheduling type of the unknown resource scheduling record is the outbound call, send the identification information of the unknown resource scheduling record to a host; if the call type of the unknown resource scheduling record is the inbound call, send the identification information of the unknown resource scheduling record to a micro service.

11. The apparatus of claim 9, wherein, The receiving module is further configured to: in response to receiving the identification information of the unknown resource scheduling record, determine whether the identification information of the unknown resource scheduling record matches identification information of a resource scheduling record of the service node; if yes, establish a first association relationship between the unknown resource scheduling record and the resource scheduling record of the service node; perform comparison between the unknown resource scheduling record and the resource scheduling record of the service node having the first association relationship, to obtain an unknown resource scheduling record and the resource scheduling record of the service node having inconsistent comparison results; determine respective identification information of the unknown resource scheduling record and the resource scheduling record of the service node having inconsistent comparison results, and take the determined identification information as identification information of to-be-corrected data. After determining the identification information of the unknown resource scheduling record and the identification information of the resource scheduling record of the service node having inconsistent comparison results, and taking the determined identification information as the identification information of the to-be-corrected data, the receiving module is further configured to:

12. The apparatus of claim 11, wherein, in response to determining the identification information of the to-be-corrected data, send the to-be-corrected data and the identification information of the to-be-corrected data to a preset resource scheduling record database; based on the identification information of the to-be-corrected data, perform information archiving on the to-be-corrected data. The association comparison module is specifically configured to:

13. The apparatus of claim 9, wherein, in response to receiving the identification information of the to-be-corrected data, establish a second association relationship between the identification information of the to-be-corrected data and the identification information of the unknown resource scheduling record; perform comparison between the to-be-corrected data and the unknown resource scheduling record having the second association relationship, to obtain to-be-corrected data and a resource scheduling record having inconsistent comparison results; determine respective identification information of the to-be-corrected data and the resource scheduling record having inconsistent comparison results, as to-be-corrected resource scheduling records. ​ 14. The apparatus of claim 9, wherein, The modification module is configured to generate a modification request for modifying the to-be-modified resource scheduling record based on the to-be-modified resource scheduling record. In response to a preset modification trigger condition being met, the modification module is configured to determine a resource scheduling access identifier for modifying the to-be-modified resource scheduling record, wherein the modification trigger condition at least includes: a preset trigger time being reached, a preset trigger period being met, and a modification trigger instruction being received. The modification module is configured to determine, from a preset resource configuration scheme set, a target resource configuration scheme corresponding to the resource scheduling access identifier. The modification module is configured to configure, by using the target resource configuration scheme, a modification request for modifying the to-be-modified resource scheduling record.

15. The apparatus of claim 9, wherein, After the modification module sends the modification request to the service node to enable the service node to modify the to-be-modified resource scheduling record, the modification module is further configured to: receive a modification response result of consistent resource scheduling for the to-be-modified resource scheduling record generated by the service node in response to the modification request; obtain state change information corresponding to the to-be-modified resource scheduling record based on the modification response result, wherein the state change information represents a change in a scheduling state of the to-be-modified resource scheduling record; adjust the scheduling state of the to-be-modified resource scheduling record by using the state change information.

16. The apparatus of any one of claims 9-15, wherein, The identification information of the resource scheduling record includes a resource scheduling event identifier corresponding to the resource scheduling record and a sub-resource scheduling event identifier corresponding to the resource scheduling record. The resource scheduling event identifier is used to uniquely identify the resource scheduling event. Therefore, different resource scheduling records generated based on the resource scheduling event all carry the same resource scheduling event identifier. The resource scheduling sub-event identifier is used to identify a resource scheduling record generated for the resource scheduling event. Therefore, different resource scheduling records generated based on the resource scheduling event all carry different resource scheduling sub-event identifiers.

17. An electronic device, comprising: The computer program product comprises computer program code, which, when executed on a computer, causes the computer to perform the method according to any one of claims 1-8. The computer program product comprises computer program code, which, when executed on a computer, causes the computer to perform the method according to any one of claims 1-8. The computer program product comprises computer program code, which, when executed on a computer, causes the computer to perform the method according to any one of claims 1-8.

18. A computer-readable storage medium, characterized in that, ​ 19. A computer program product, characterised in that, ​

Images