Method, device, equipment and computer readable medium for interaction data

Abstract

The application discloses a method, device and equipment for interactive data and a computer readable medium, and relates to the technical field of big data. A specific embodiment of the method comprises the following steps: a plurality of loan subsystems affiliated to a loan main system generate account data files of the loan subsystems after completing daily settlement; after the loan subsystems send the account data files, it is checked whether all the loan subsystems of the loan main system send account data files; if all the loan subsystems of the loan main system have sent account data files, the loan subsystems generate and send a closing file of the loan main system based on the identification of all the loan subsystems. The embodiment does not need thread monitoring for the sending of the account data files, thereby avoiding waste of resources.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of big data, and in particular to a method and device for interacting data, equipment and computer readable medium. BACKGROUND

[0002] The loan system needs to send the system account data file into account after the end of the day. The end of the day refers to the end of the day after the loan system performs data batch processing, and after the processing is completed, the day is cut into the next day. In order to improve efficiency, when each system sends the account data file, it notifies the account closure, and then performs the account batch processing. Thus, the mechanism of "closing account first, processing first" is realized.

[0003] The loan system includes multiple subsystems, and a new subsystem thread is created to poll the account data file sending situation of each subsystem at regular intervals. Alternatively, each subsystem forwards the account data file through an intermediate system, and the loan system learns the account data file sending situation of the subsystem through the intermediate system.

[0004] In the process of implementing the present application, the inventors have found that at least the following problems exist in the prior art: Whether a new thread is created or the account data file is forwarded through an intermediate system, a resident thread needs to be added. Since the utilization rate of the resident thread is low, resources are wasted. SUMMARY

[0005] Therefore, the embodiments of the present application provide a method and device for interacting data, equipment and computer readable medium, which do not need thread to monitor the sending of account data files, thereby avoiding wasting resources.

[0006] To achieve the above object, according to one aspect of the embodiments of the present application, a method for interacting data is provided, comprising:

[0007] After completing daily settlement, a plurality of loan subsystems subordinate to a loan main system generate account data files of the loan subsystems;

[0008] After the loan subsystems send the account data files, it is checked whether all loan subsystems of the loan main system send account data files;

[0009] If all loan subsystems of the loan main system have sent account data files, the loan subsystem generates and sends a closure file of the loan main system based on the identification of the all loan subsystems.

[0010] After completing daily settlement, a plurality of loan subsystems subordinate to a loan main system generate account data files of the loan subsystems, comprising:

[0011] The loan main system is divided into the plurality of loan subsystems according to business types.

[0012] The loan subsystem generates an account data file of the loan subsystem according to a system identifier of the loan subsystem after completing daily settlement.

[0013] After the loan subsystem sends the account data file, the loan subsystem checks whether all loan subsystems of the loan main system send account data files, including:

[0014] After the time zone of the business processing of the loan subsystem ends, the loan subsystem sends the account data file;

[0015] The loan subsystem checks whether all loan subsystems of the loan main system send account data files.

[0016] The loan subsystem checks whether all loan subsystems of the loan main system send account data files, including:

[0017] The loan subsystem acquires a state identifier of an account data file of a loan subsystem in the loan main system;

[0018] The loan subsystem checks whether all loan subsystems of the loan main system send account data files according to the state identifier of the account data file of the loan subsystem.

[0019] The loan subsystem checks whether all loan subsystems of the loan main system send account data files according to the state identifier of the account data file of the loan subsystem, including:

[0020] The loan subsystem updates a state identifier of an account data file of a loan subsystem;

[0021] The loan subsystem checks whether all loan subsystems of the loan main system send account data files based on the updated state identifier of the account data file of the loan subsystem.

[0022] The state identifier of the account data file includes a state identifier set in a state list;

[0023] The loan subsystem checks whether all loan subsystems of the loan main system send account data files according to the state identifier of the account data file of the loan subsystem, including:

[0024] The loan subsystem traverses the state list according to system identifiers of all loan subsystems in the loan main system to check whether all loan subsystems of the loan main system send account data files.

[0025] The loan subsystem checks whether all loan subsystems of the loan main system send account data files, including:

[0026] Based on the correspondence between the system identifier and the status identifier, checking whether all loan subsystems of the loan main system have sent the account data file.

[0027] All loan subsystems of the loan main system have sent the account data file, including:

[0028] The correspondence between the system identifier and the status identifier includes one-to-one correspondence, and it is determined that all loan subsystems of the loan main system have sent the account data file.

[0029] The account data file status identifier includes a status graph.

[0030] The checking whether all loan subsystems of the loan main system have sent the account data file according to the account data file status identifier of the all loan subsystems, including:

[0031] Detecting the integrity of the status graph to check whether all loan subsystems of the loan main system have sent the account data file.

[0032] The detecting the integrity of the status graph to check whether all loan subsystems of the loan main system have sent the account data file, including:

[0033] Based on the original shape of the status graph, the integrity of the status graph is detected to check whether all loan subsystems of the loan main system have sent the account data file.

[0034] All loan subsystems of the loan main system have sent the account data file, including:

[0035] The original shape of the status graph is consistent with the shape of the status graph, and it is determined that all loan subsystems of the loan main system have sent the account data file.

[0036] The original shape includes a complete closed graph.

[0037] The original graph includes a circle.

[0038] The loan subsystem generates and sends the loan main system's closing file based on the identifier of the all loan subsystems, including:

[0039] The loan subsystem generates and sends the loan main system's closing file based on the identifier of the all loan subsystems and the current time point.

[0040] According to a second aspect of the embodiments of the present application, an interactive data device is provided, including:

[0041] The generating module is configured to control a plurality of loan subsystems subordinate to a loan main system to generate an account data file of the loan subsystem after daily settlement is completed;

[0042] The checking module is configured to check whether all the loan subsystems of the loan main system send the account data file after the loan subsystem sends the account data file.

[0043] The sending module is configured to control the loan subsystem to generate and send a closing file of the loan main system based on the identification of all the loan subsystems when all the loan subsystems of the loan main system have sent the account data file.

[0044] The checking module is specifically configured to control the loan subsystem to send the account data file after a time zone of business processing of the loan subsystem is ended.

[0045] The checking module is configured to check whether all the loan subsystems of the loan main system send the account data file.

[0046] The checking module is specifically configured to acquire an account data file state identification of the loan subsystem in the loan main system.

[0047] The checking module is configured to check whether all the loan subsystems of the loan main system send the account data file according to the account data file state identification of the loan subsystem.

[0048] According to a third aspect of the embodiment of the present application, an electronic device for interactive data is provided, comprising:

[0049] One or more processors;

[0050] A storage device configured to store one or more programs,

[0051] When the one or more programs are executed by the one or more processors, the one or more processors implement the method as described above.

[0052] According to a fourth aspect of the embodiment of the present application, a computer readable medium is provided, which stores a computer program, and the program is executed by a processor to implement the method as described above.

[0053] According to a fifth aspect of the embodiment of the present application, a computer program product is provided, which comprises a computer program, and the program is executed by a processor to implement the method as described above.

[0054] An embodiment of the above application has the following advantages or beneficial effects: a plurality of loan subsystems under a loan main system generate account data files of the loan subsystems after daily settlement is completed; after the loan subsystems send the account data files, the loan subsystems check whether all loan subsystems of the loan main system send account data files; when all loan subsystems of the loan main system have sent account data files, the loan subsystems generate and send a closing file of the loan main system based on the identification of all loan subsystems. The loan subsystems check whether all loan subsystems send account data files, without adding threads to monitor the sending of account data files, thereby fully utilizing existing resources to avoid waste of additional thread resources.

[0055] Further effects of the above non-conventional optional mode will be described below in conjunction with the specific embodiments. BRIEF DESCRIPTION OF DRAWINGS

[0056] The accompanying drawings are used to better understand the present application and do not constitute undue limitations on the present application. Among them:

[0057] Figure 1 is a main flow diagram of a method of interactive data according to an embodiment of the present application;

[0058] Figure 2 is a flow diagram of generating account data files of loan subsystems according to an embodiment of the present application;

[0059] Figure 3 is a flow diagram of checking loan subsystems according to an embodiment of the present application;

[0060] Figure 4 is a daily cut diagram of loan subsystems according to an embodiment of the present application;

[0061] Figure 5 is a flow diagram of checking all loan subsystems of a loan main system according to an embodiment of the present application;

[0062] Figure 6 is a flow diagram of updating the state identification of account data files according to an embodiment of the present application;

[0063] Figure 7 is a diagram of a state graph according to an embodiment of the present application;

[0064] Figure 8 is a diagram of a circular state graph according to an embodiment of the present application;

[0065] Figure 9 is a diagram of checking integrity based on a circular state graph according to an embodiment of the present application;

[0066] Figure 10 is a main structure schematic diagram of the device of interaction data according to the embodiment of the present application;

[0067] Figure 11 is an exemplary system architecture diagram to which the embodiment of the present application can be applied;

[0068] Figure 12 is a structure schematic diagram of a computer system of a terminal device or a server suitable for being used to implement the embodiment of the present application. DETAILED DESCRIPTION

[0069] The exemplary embodiments of the present application are described below with reference to the accompanying drawings, including various details of the embodiments of the present application to assist in understanding, which should be considered as merely exemplary. Therefore, those of ordinary skill in the art should recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the present application. Also, for the sake of clarity and conciseness, the description below omits the description of well-known functions and structures. The acquisition, storage, use, processing, etc. of data in the technical solutions of the present application comply with the relevant provisions of national laws and regulations.

[0070] The number of accounting data files is determined according to the size of the business volume, and there is no complete same. The accounting engine system usually performs entry running batch at T+1 in the morning, and T is the upload date of the accounting data file. Therefore, it is necessary to perform the accounting engine running batch first, and then send all the accounting data files. In addition to the loan system, there are many other subsystems in the system that send accounting data files.

[0071] In the loan system, a main system contains multiple subsystems. Since each subsystem handles business differently, considering historical reasons, data may be stored in one or more subsystems, and accounting data files need to be sent to the accounting engine system for accounting. On the same day, after the accounting data files of each subsystem are sent to the accounting engine system, the main system sends the closing file to indicate that all the accounting data files of the system today are sent.

[0072] In recent years, due to the increasing strength of financial digitization, the data volume has increased rapidly. The amount of accounting data is also growing every day, so higher requirements are put forward for the processing capacity and efficiency of the accounting system.

[0073] Currently, the following two ways are mainly used to send accounting data files.

[0074] Method one

[0075] Each subsystem sends the accounting data file to the accounting engine respectively, and notifies the main system after sending, and the main system sends the closing file after receiving all the notifications from the subsystems.

[0076] Since the main system needs to newly create a sub-thread, it needs to poll the sending completion of the accounting data file of each subsystem. A resident thread has low resource utilization, which wastes resources and is not efficient, and it is not easy to monitor its scheduling.

[0077] Method two

[0078] Among the plurality of subsystems, one subsystem is selected as an intermediate system. The intermediate system collects the accounting data files of other subsystems and sends them to the accounting engine, and sends the closing file after all the accounting data files are sent. The accounting data file is transferred through the intermediate system, and a resident thread needs to be newly created. Since one node is added to the transmission, the transmission time is longer, and the efficiency is not high. Moreover, the transmission failure probability is increased, and the retransmission probability is increased.

[0079] In summary, whether a sub-thread is newly created or an accounting data file is forwarded through an intermediate system, a resident thread needs to be newly created. Since the utilization rate of the resident thread is low, resources are wasted.

[0080] In order to solve the problem of monitoring the sending of the accounting data file while avoiding wasting resources, the technical solutions in the embodiments of the present application can be used.

[0081] Referring to Figure 1 , Figure 1 The method for interacting data according to the embodiment of the present application mainly includes the following steps: checking whether all the loan subsystems of the loan main system send the accounting data file, without newly creating a thread to monitor all the loan subsystems. As shown in Figure 1 , the specific steps include the following steps:

[0082] S101, after completing daily settlement, a plurality of loan subsystems subordinate to the loan main system generate the accounting data file of the loan subsystem.

[0083] In the embodiment of the present application, the loan main system refers to a system composed of a plurality of loan subsystems. The loan main system is used for processing loan data. The loan main system has a plurality of loan subsystems. The loan subsystems each process different businesses, and each loan subsystem can independently and in parallel generate and send its own accounting data file.

[0084] Referring to Figure 2 , Figure 2 The flowchart for generating the accounting data file of the loan subsystem according to the embodiment of the present application is shown in the figure. The specific steps include the following steps:

[0085] S201, the loan main system is divided into multiple loan subsystems according to the business type.

[0086] The loan main system includes multiple loan subsystems, and each loan subsystem can be responsible for one or more businesses. In order to clarify the role of each loan subsystem, the loan main system is divided into multiple loan subsystems according to the business type.

[0087] As an example, the loan main system is divided into a loan subsystem responsible for real estate mortgage loans, a loan subsystem responsible for industrial loans, and a loan subsystem responsible for Internet loans according to the type of loan business.

[0088] S202, the loan subsystem generates the loan subsystem's accounting data file according to the system identifier of the loan subsystem after completing daily settlement.

[0089] Each loan subsystem can independently generate a financial data file. Specifically, after completing daily settlement, the loan subsystem can generate the loan subsystem's accounting data file according to its own system identifier. As an example, the system identifier of the loan subsystem A is 00a, and the accounting data file is generated according to 00a.

[0090] Each loan subsystem is independent, and multiple loan subsystems can generate the accounting data file of the loan subsystem according to the system identifier.

[0091] In Figure 2 the embodiment, each loan subsystem subordinate to the loan main system can generate its own accounting data file.

[0092] S102, the loan subsystem sends the accounting data file, and checks whether all loan subsystems of the loan main system send the accounting data file.

[0093] In the embodiment of the application, the subject of checking whether all loan subsystems of the loan main system send the accounting data file is the loan subsystem. For each loan subsystem, the above check needs to be performed, and thus there is no need to create a new thread to monitor other loan subsystems.

[0094] Referring to Figure 3 , Figure 3 is a flowchart of checking the loan subsystem according to the embodiment of the application. Specifically, it includes the following steps:

[0095] S301, the loan subsystem sends the accounting data file after the time zone of the loan subsystem business processing ends.

[0096] Each loan subsystem has a corresponding business processing time zone. As an example, the business processing time zone of loan subsystem a is: 20:00 to 21:30. The business processing time zone of loan subsystem b is: 20:30 to 21:30.

[0097] The loan subsystem processes business within the business processing time zone. After the end of the business processing time zone, it is indicated that the accounting data file has been generated, and the day switching is completed. The day switching is to change the time of system accounting, switching from the current working day to the next working day.

[0098] Referring to Figure 4 , Figure 4 is a schematic diagram of day switching of a loan subsystem according to an embodiment of the present application. Figure 4 There are three loan subsystems that need to send accounting data files, and the loan subsystems are marked with triangles, which are loan subsystem 1, loan subsystem 2 and loan subsystem 3. Each loan subsystem is relatively independent in accounting data processing, accounting data file generation, accounting data file sending and its own day switching, and is not constrained and affected by other loan subsystems.

[0099] The loan subsystem 1, because the business processing time zone is earlier than the other two loan subsystems, first completes the "current day" day switching and enters the next day accounting data file processing.

[0100] The loan subsystem 2, because the business volume of the previous day is large, the processing time is longer than before, and the sending of the accounting data file is the latest, and finally the loan subsystem 2 sends the closing file. At this time, the main system composed of the loan subsystem 1, the loan subsystem 2 and the loan subsystem 3 completes the "previous day" accounting day switching.

[0101] The loan subsystem 3 is in the middle of the processing speed, and is in the process of "current day" accounting data processing.

[0102] After the end of the business processing time zone of the loan subsystem, the loan subsystem sends the accounting data file. Specifically, the loan subsystem sends the accounting data file to the accounting engine.

[0103] It should be noted that if there are multiple loan subsystems, each loan subsystem independently processes business within its own business processing time zone and is not affected and constrained by other loan subsystems.

[0104] S302, check whether all loan subsystems of the loan main system send accounting data files.

[0105] The loan subsystem that has sent the accounting data file checks whether all loan subsystems of the loan main system send the accounting data file.

[0106] As an example, the loan subsystem a has sent the account data file, then it can be checked whether all the loan subsystems of the loan main system have sent the account data file; the loan subsystem b has sent the account data file, then it can be checked whether all the loan subsystems of the loan main system have sent the account data file.

[0107] In Figure 3 Embodiments, each loan subsystem which has sent the account data file can check whether all the loan subsystems of the loan main system have sent the account data file.

[0108] In an embodiment of the present application, checking whether all the loan subsystems of the loan main system have sent the account data file can adopt the technical solutions in Figure 5

[0109] Referring to Figure 5 , Figure 5 is a flowchart of checking all the loan subsystems of the loan main system according to an embodiment of the present application. Specifically, it comprises the following steps:

[0110] S501, obtaining the account data file state identifier of the loan subsystem in the loan main system.

[0111] In order to check whether the loan subsystem has sent the account data file, the account data file state identifier needs to be obtained. The account data file state identifier is an identifier marking that the account data file has been sent.

[0112] As an example, the account data file state identifier is stored in the loan main system. After the loan subsystem sends the account data file, the account data file state identifier of the loan subsystem is stored in the loan main system. The account data file state identifier has a corresponding relationship with the system identifier of the loan subsystem. That is, based on the system identifier of the loan subsystem, the account data file state identifier can be obtained; based on the account data file state identifier, the system identifier of the loan subsystem can be obtained.

[0113] It can be understood that if the loan subsystem has sent the account data file, the account data file state identifier can be obtained; if the loan subsystem has not sent the account data file, the account data file state identifier cannot be obtained.

[0114] S502, checking whether all the loan subsystems of the loan main system have sent the account data file according to the account data file state identifier of the loan subsystem.

[0115] According to the account data file state identifier of the loan subsystem, whether all the loan subsystems of the loan main system have sent the account data file can be checked.

[0116] Referring to Figure 6 ​, Figure 6 This is a flowchart illustrating the process of updating the status identifier of an accounting data file according to an embodiment of the present invention. Specifically, it includes the following steps:

[0117] In one embodiment of the present invention, considering the different time zones of the loan subsystem's business processing, the status identifier of the loan subsystem's accounting data file will change. For example: in the first time period, accounting data file status identifier 1 and accounting data file status identifier 2 are received; in the second time period, accounting data file status identifier 3 is received.

[0118] S601. Update the status identifier of the accounting data file of the loan subsystem.

[0119] The status flag of the loan subsystem's accounting data file is updated according to a preset cycle. As an example, the status flag of the loan subsystem's accounting data file is updated in the loan master system every 30 minutes.

[0120] S602. Based on the updated accounting data file status identifier of the loan subsystem, verify whether all loan subsystems of the loan master system have sent accounting data files.

[0121] Updating the status flag of the loan subsystem's accounting data files reflects the current status of the accounting data files sent by the loan subsystem. Furthermore, based on the updated status flag, the system verifies whether all loan subsystems within the main loan system have sent their accounting data files.

[0122] exist Figure 6 In this embodiment, the updated accounting data file status identifier is used for verification, thereby improving the accuracy of the verification.

[0123] In embodiments of the present invention, the accounting data file status identifier can take multiple forms. The following description addresses two scenarios based on the accounting data file status identifier.

[0124] Scenario 1:

[0125] The accounting data file status identifiers include those set in the status list. Verifying whether all loan subsystems within the main loan system have sent accounting data files can be achieved by iterating through the status categories.

[0126] Specifically, based on the system identifiers of all loan subsystems in the loan master system, the status list is traversed to check whether all loan subsystems in the loan master system have sent accounting data files.

[0127] The status list records status identifiers. Each status identifier corresponds one-to-one with the status identifier of the accounting data file. That is, if the loan subsystem has sent the accounting data file, the status list will include the status identifier corresponding to the accounting data file status identifier.

[0128] As an example, based on the correspondence between the system identifier and the state identifier, it is checked whether all loan subsystems of the loan main system have sent the account data file.

[0129] The system identifier is obtained by traversing the state list, and based on the one-to-one correspondence between the system identifier and the state identifier, the system identifier of the system that has sent the account data file is determined. If the determined system identifier is the identifier of all loan subsystems of the loan main system, it is determined that all loan subsystems of the loan main system have sent the account data file; if the determined system identifier is not the identifier of all loan subsystems of the loan main system, it is determined that part of the loan subsystems of the loan main system have sent the account data file.

[0130] In an embodiment of the present application, the correspondence between the system identifier and the state identifier includes one-to-one correspondence, and it is determined that all loan subsystems of the loan main system have sent the account data file.

[0131] Case two:

[0132] The state identifier of the account data file includes a state figure. The checking of whether all loan subsystems of the loan main system have sent the account data file can be achieved by detecting the integrity of the state figure.

[0133] Specifically, the integrity of the state figure is detected to check whether all loan subsystems of the loan main system have sent the account data file. As an example, each loan subsystem is a part of the state figure. The figures of all loan subsystems of the loan main system form a complete state figure.

[0134] Referring to Figure 7 , Figure 7 is a schematic view of the state figure according to an embodiment of the present application. Figure 7 The numbers in the state figure of are respectively corresponding to four loan subsystems. If all the four loan subsystems have sent the account data file, the state figure is formed.

[0135] In an embodiment of the present application, the integrity of the state figure is detected based on the original shape of the state figure to check whether all loan subsystems of the loan main system have sent the account data file.

[0136] For the state figure, the integrity of the state figure can be detected based on the original shape of the state figure. The original shape of the state figure is the figure before the state figure is segmented. As an example, the original shape includes a complete closed figure, such as a circle, a square, or an ellipse, etc.

[0137] As an example, the original shape of the state figure is consistent with the shape of the state figure, and it is determined that all loan subsystems of the loan main system have sent the account data file; the original shape of the state figure is different from the shape of the state figure, and it is determined that not all loan subsystems of the loan main system have sent the account data file.

[0138] S103, when all loan subsystems of the loan main system have sent the account data file, the loan subsystem generates and sends the closing file of the loan main system based on the identification of all loan subsystems.

[0139] When all loan subsystems of the loan main system have sent the account data file, on the one hand, it indicates that the closing file can be established; on the other hand, it indicates that the loan subsystem of the current interaction data is the last loan subsystem that sends the account data file.

[0140] For each loan subsystem, after sending its own account data file, it checks whether all loan subsystems of the loan main system have sent the account data file. The last loan subsystem that sends the account data file checks whether all loan subsystems of the loan main system have sent the account data file, and then generates and sends the closing file of the loan main system.

[0141] In an embodiment of the present application, the loan subsystem generates and sends the closing file of the loan main system based on the identification of all loan subsystems and the current time point. It can be understood that the closing file includes the identification of all loan subsystems under the loan main system and the current time point.

[0142] In the above embodiment of the present application, after completing daily settlement, the plurality of loan subsystems under the loan main system generate the account data file of the loan subsystem; after the loan subsystem sends the account data file, it checks whether all loan subsystems of the loan main system have sent the account data file; when all loan subsystems of the loan main system have sent the account data file, the loan subsystem generates and sends the closing file of the loan main system based on the identification of all loan subsystems. The loan subsystem checks whether all loan subsystems have sent the account data file, without the need to add a thread to monitor the sending of the account data file, thereby fully utilizing the existing resources to avoid waste of additional thread resources.

[0143] Referring to Figure 8 , Figure 8 is a schematic diagram of a circular state figure according to an embodiment of the present application. The circular state figure is divided into four blocks, each identified by a number. That is, the system identification is 1 to 4.

[0144] The loan main system divides the circular state figure according to the number of subordinate loan subsystems when it is first online, and numbers and identifies the puzzle corresponding to the loan subsystem.

[0145] If a loan subsystem is added or deleted, the loan main system updates the divided circular state figure and notifies each loan subsystem.

[0146] Referring to Figure 9 , Figure 9 is a schematic diagram of checking integrity based on a circular state figure according to an embodiment of the present application.

[0147] In the loan main system, the number of loan subsystems that need to send account data files every day is fixed, so the division mode of the circular state figure is the same, that is, the number of puzzle pieces is fixed, and the puzzle piece number corresponding to the loan subsystem does not change.

[0148] The loan subsystems 1 to 4 are numbered and run independently, and each generates its own account data file after the end of the day.

[0149] The loan subsystems send their account data files to the accounting engine system for entry without any sequence. Figure 9 The circular puzzle also has no sequence. After sending the account data file, the puzzle is completed according to its own system identification, that is, the number. There are as many loan subsystems as there are account data files to be sent, and there are as many puzzle pieces.

[0150] After the loan subsystems complete the puzzle of their respective numbers, the integrity of the figure is immediately checked, that is, whether the puzzle is complete. The last puzzle loan subsystem, that is, the loan subsystem 3 corresponding to the dashed puzzle, checks the integrity of the image, and generates a closing file. Figure 9

[0151] Referring to Figure 10 , Figure 10 is a main structure schematic diagram of an interactive data device according to an embodiment of the present application. The interactive data device can implement the interactive data method, as shown in Figure 10 The interactive data device specifically includes:

[0152] The generating module 1001 is configured to control a plurality of loan subsystems subordinate to a loan main system to generate account data files of the loan subsystems after completing daily settlement.

[0153] The checking module 1002 is configured to control the loan subsystems to check whether all loan subsystems of the loan main system send account data files after the loan subsystems send the account data files.

[0154] ​The sending module 1003 is configured to: when all the loan subsystems of the loan main system have sent the account data files, control the loan subsystem to generate and send a closing file of the loan main system based on identification of all the loan subsystems.

[0155] In an embodiment of the present application, the generating module 1001 is specifically configured to control the loan main system to be divided into the plurality of loan subsystems according to business types.

[0156] The control is performed on the loan subsystem to generate an account data file of the loan subsystem according to a system identification of the loan subsystem after daily settlement is completed.

[0157] In an embodiment of the present application, the checking module 1002 is specifically configured to control the loan subsystem to send the account data file after a time zone of business processing of the loan subsystem is ended.

[0158] The checking module 1002 is configured to check whether all the loan subsystems of the loan main system send the account data files.

[0159] In an embodiment of the present application, the checking module 1002 is specifically configured to acquire an account data file state identification of a loan subsystem in the loan main system.

[0160] The checking module 1002 is configured to check whether all the loan subsystems of the loan main system send the account data files according to the account data file state identification of the loan subsystem.

[0161] In an embodiment of the present application, the checking module 1002 is specifically configured to update the account data file state identification of the loan subsystem.

[0162] The checking module 1002 is configured to check whether all the loan subsystems of the loan main system send the account data files based on the updated account data file state identification of the loan subsystem.

[0163] In an embodiment of the present application, the account data file state identification includes a state identification set in a state list.

[0164] The checking module 1002 is configured to traverse the state list according to system identification of all the loan subsystems in the loan main system, and check whether all the loan subsystems of the loan main system send the account data files.

[0165] In an embodiment of the present application, the checking module 1002 is specifically configured to check whether all the loan subsystems of the loan main system send the account data files based on a corresponding relationship between the system identification and the state identification.

[0166] In an embodiment of the present application, the checking module 1002 is specifically configured for determining that all loan subsystems of the loan main system have sent the account data file based on the one-to-one correspondence between the system identifier and the state identifier.

[0167] In an embodiment of the present application, the state identifier of the account data file comprises a state figure.

[0168] The checking module 1002 is specifically configured for detecting the integrity of the state figure to check whether all loan subsystems of the loan main system have sent the account data file.

[0169] In an embodiment of the present application, the checking module 1002 is specifically configured for detecting the integrity of the state figure based on an original shape of the state figure to check whether all loan subsystems of the loan main system have sent the account data file.

[0170] In an embodiment of the present application, the checking module 1002 is specifically configured for determining that all loan subsystems of the loan main system have sent the account data file based on the original shape of the state figure being consistent with the shape of the state figure.

[0171] In an embodiment of the present application, the original shape comprises a complete closed figure.

[0172] In an embodiment of the present application, the original figure comprises a circle.

[0173] In an embodiment of the present application, the sending module 1003 is specifically configured for controlling the loan subsystem to generate and send the closing file of the loan main system based on the identifier of all loan subsystems and the current time point.

[0174] Figure 11 An exemplary system architecture 1100 of the method of interactive data or the apparatus of interactive data to which embodiments of the present application can be applied is shown.

[0175] As shown in Figure 11 The system architecture 1100 can include terminal devices 1101, 1102, 1103, a network 1104 and a server 1105. The network 1104 is a medium for providing a communication link between the terminal devices 1101, 1102, 1103 and the server 1105. The network 1104 can include various connection types, such as wired, wireless communication links or optical fiber cables, etc.

[0176] The user can use the terminal devices 1101, 1102, 1103 to interact with the server 1105 through the network 1104 to receive or send messages, etc. Various communication client applications can be installed on the terminal devices 1101, 1102, 1103, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc. (only as examples).

[0177] The terminal devices 1101, 1102, 1103 can be various electronic devices with display screens and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers, desktop computers, etc.

[0178] The server 1105 can be a server providing various services, such as a background management server supporting a shopping website browsed by the user using the terminal devices 1101, 1102, 1103 (only as an example). The background management server can analyze and process received product information query requests, etc., and feed back the processing results (such as target push information, product information - only as examples) to the terminal devices.

[0179] It should be noted that the method for interacting data provided by the embodiments of the present application is generally executed by the server 1105, and accordingly, the device for interacting data is generally provided in the server 1105.

[0180] It should be understood that, Figure 11 The number of terminal devices, networks and servers in

[0181] A computing program product of an embodiment of the present application includes a computer program, which, when executed by a processor, implements the method for interacting data provided by the embodiments of the present application.

[0182] Reference will be made to Figure 12 which shows a structural schematic diagram of a computer system 1200 of a terminal device suitable for being used to implement the embodiments of the present application. Figure 12 The terminal device shown is only an example, and should not bring any limitation to the functions and use range of the embodiments of the present application.

[0183] As Figure 12As shown, the computer system 1200 includes a central processing unit (CPU) 1201 which can perform various suitable actions and processes in accordance with programs stored in a read only memory (ROM) 1202 or loaded from the storage section 1208 into a random access memory (RAM) 1203. Various programs and data required for the operation of the system 1200 are also stored in the RAM 1203. The CPU 1201, the ROM 1202, and the RAM 1203 are connected to each other through a bus 1204. An input / output (I / O) interface 1205 is also connected to the bus 1204.

[0184] Connected to the I / O interface 1205 are an input section 1206 including a keyboard, a mouse, etc.; an output section 1207 including a display such as a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 1208 including a hard disk, etc.; and a communication section 1209 including a network interface card such as a LAN card, a modem, etc. The communication section 1209 performs communication processing via a network such as the Internet. A drive 1210 is also connected to the I / O interface 1205 as necessary. A removable recording medium 1211 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc. is attached to the drive 1210 as necessary, so that a computer program read therefrom is installed into the storage section 1208 as necessary.

[0185] In particular, the processes described above with reference to the flow charts can be implemented as computer software programs in accordance with the embodiments of the present disclosure. For example, the embodiments of the present disclosure include a computer program product comprising a computer program carried on a computer readable medium, the computer program containing program codes for executing the methods shown in the flow charts. In such embodiments, the computer program can be downloaded and installed from a network by the communication section 1209, and / or installed from the removable recording medium 1211. When the computer program is executed by the central processing unit (CPU) 1201, the above-described functions defined in the system of the present disclosure are performed.

[0186] It should be noted that the computer-readable medium shown in the present application can be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may, for example, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or component, or any combination of the above. More specific examples of computer-readable storage media can include, but are not limited to, an electrical connection having one or more wires, a portable computer diskette, 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 disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, the computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, device or component. In the present application, the computer-readable signal medium can include a data signal carried in a baseband or as a part of a carrier wave, which carries computer-readable program code. Such a propagated data signal can take various forms, including but not limited to an electromagnetic signal, an optical signal or any suitable combination of the above. The computer-readable signal medium can also be any computer-readable medium other than the computer-readable storage medium, which can send, propagate or transmit a program for use by or in conjunction with an instruction execution system, device or component. The program code contained on the computer-readable medium can be transmitted by any suitable medium, including but not limited to wireless, wire, optical cable, RF, etc., or any suitable combination of the above.

[0187] The flowcharts and block diagrams in the drawings illustrate the possible implementation architectures, functions and operations of the systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowcharts or block diagrams can represent a module, a program segment or a part of code containing one or more executable instructions for implementing the specified logical functions. It should also be noted that in some alternative implementations, the functions noted in the blocks can occur in different order than that shown in the drawings. For example, two blocks that are shown in succession can actually be executed substantially in parallel, and sometimes in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams or flowcharts, and the combination of blocks in the block diagrams or flowcharts, can be implemented by a dedicated hardware-based system that performs the specified functions or operations, or can be implemented by a combination of dedicated hardware and computer instructions.

[0188] The modules described in the embodiments of the present application can be implemented in the form of software or hardware. The modules described can also be arranged in a processor, for example, a processor can be described as including a generating module, a checking module and a sending module. In some cases, the names of the modules do not constitute a limitation on the modules themselves, for example, the generating module can also be described as "generating an account data file of a plurality of loan subsystems subordinate to a loan main system after daily settlement is completed".

[0189] As another aspect, the present application also provides a computer readable medium, which can be included in the device described in the above embodiments or exist separately without being assembled into the device. The computer readable medium carries one or more programs, which, when executed by the device, cause the device to include:

[0190] generating an account data file of a plurality of loan subsystems subordinate to a loan main system after daily settlement is completed;

[0191] checking whether all the loan subsystems of the loan main system have sent account data files after the loan subsystem sends the account data file;

[0192] generating and sending a closing file of the loan main system based on the identification of all the loan subsystems when all the loan subsystems of the loan main system have sent account data files.

[0193] According to the technical scheme of the embodiments of the present application, a plurality of loan subsystems subordinate to a loan main system generate an account data file of the loan subsystem after daily settlement is completed; the loan subsystem checks whether all the loan subsystems of the loan main system have sent account data files after the loan subsystem sends the account data file; and the loan subsystem generates and sends a closing file of the loan main system based on the identification of all the loan subsystems when all the loan subsystems of the loan main system have sent account data files. The loan subsystem checks whether all the loan subsystems have sent account data files, without the need to add a thread to monitor the sending of the account data file, thereby making full use of the existing resources to avoid the waste of additional thread resources.

[0194] The above specific embodiments do not constitute a limitation on the protection scope of the present application. Those skilled in the art should understand that various modifications, combinations, sub-combinations and substitutions can be made depending on design requirements and other factors. Any modification, equivalent replacement and improvement made within the spirit and principles of the present application should be included in the protection scope of the present application.

Claims

1. A method of interacting data, characterized by, The method comprises the following steps: a plurality of loan subsystems under a loan main system generate account data files of the loan subsystems after completing daily settlement; after the loan subsystems send the account data files, the loan subsystems acquire state identifiers of the account data files of the loan subsystems in the loan main system; and according to the state identifiers of the account data files of the loan subsystems, the loan subsystems check whether all the loan subsystems of the loan main system send the account data files; after all the loan subsystems of the loan main system have sent the account data files, the loan subsystems generate and send a closing file of the loan main system based on identifiers of all the loan subsystems; the checking whether all the loan subsystems of the loan main system send the account data files according to the state identifiers of the account data files of all the loan subsystems comprises: the state identifiers of the account data files comprise state identifiers arranged in a state list; according to system identifiers of all the loan subsystems in the loan main system, the state list is traversed to check whether all the loan subsystems of the loan main system send the account data files; the checking whether all the loan subsystems of the loan main system send the account data files according to the state identifiers of the account data files of all the loan subsystems comprises: the state identifiers of the account data files comprise state graphics; the completeness of the state graphics is detected to check whether all the loan subsystems of the loan main system send the account data files.

2. The method of claim 1, wherein, the plurality of loan subsystems under the loan main system generate the account data files of the loan subsystems after completing the daily settlement, which comprises the following steps: the loan main system is divided into the plurality of loan subsystems according to business types; after completing the daily settlement, the loan subsystems generate the account data files of the loan subsystems according to system identifiers of the loan subsystems.

3. The method of claim 1, wherein, after the loan subsystems send the account data files, the checking whether all the loan subsystems of the loan main system send the account data files comprises: after a time zone of business processing of the loan subsystem ends, the loan subsystem sends the account data files; the checking whether all the loan subsystems of the loan main system send the account data files.

4. The method of claim 1, wherein, the checking whether all the loan subsystems of the loan main system send the account data files according to the state identifiers of the account data files of all the loan subsystems comprises: the state identifiers of the account data files of the loan subsystems are updated; based on the updated state identifiers of the account data files of the loan subsystems, the checking whether all the loan subsystems of the loan main system send the account data files is performed.

5. The method of claim 1, wherein, the checking whether all the loan subsystems of the loan main system send the account data files comprises: based on a corresponding relationship between the system identifiers and the state identifiers, the checking whether all the loan subsystems of the loan main system send the account data files is performed.

6. The method of claim 5, wherein, after all the loan subsystems of the loan main system have sent the account data files, the corresponding relationship between the system identifiers and the state identifiers comprises one-to-one correspondence, and it is determined that all the loan subsystems of the loan main system have sent the account data files. ​ 7. The method of claim 1, wherein, The integrity of the state figure is detected to check whether all loan subsystems of the loan main system send the account data file, including: The integrity of the state figure is detected based on the original shape of the state figure to check whether all loan subsystems of the loan main system send the account data file.

8. The method of claim 7, wherein, All loan subsystems of the loan main system have sent the account data file, including: The original shape of the state figure is consistent with the shape of the state figure, and it is determined that all loan subsystems of the loan main system have sent the account data file.

9. The method of claim 7, wherein, The original shape includes a complete closed figure.

10. The method of claim 7, wherein, The original shape includes a circle.

11. The method of claim 1, wherein, The loan subsystem generates and sends the closing file of the loan main system based on the identification of all loan subsystems, including: The loan subsystem generates and sends the closing file of the loan main system based on the identification of all loan subsystems and the current time point.

12. An apparatus for interacting data, characterized by Including: A generation module is configured to control a plurality of loan subsystems under a loan main system to generate account data files of the loan subsystems after completing daily settlement; A checking module is configured to control the loan subsystem to obtain an account data file state identifier of the loan subsystem in the loan main system after the loan subsystem sends the account data file; check whether all loan subsystems of the loan main system send the account data file according to the account data file state identifier of the loan subsystem; and the account data file state identifier includes a state identifier set in a state list; the state list is traversed according to system identifiers of all loan subsystems in the loan main system to check whether all loan subsystems of the loan main system send the account data file; and the account data file state identifier includes a state figure; the integrity of the state figure is detected to check whether all loan subsystems of the loan main system send the account data file; A sending module is configured to control the loan subsystem to generate and send the closing file of the loan main system based on the identification of all loan subsystems when all loan subsystems of the loan main system have sent the account data file.

13. The apparatus of claim 12, wherein the interaction data is further characterized by, The checking module is specifically configured to control the loan subsystem to send the account data file after a time zone of business processing of the loan subsystem ends. Check whether all loan subsystems of the loan main system send the account data file.

14. An electronic device for interacting with data, characterized in that Including: One or more processors; A storage device configured to store one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors implement the method in any one of claims 1-11.

15. A computer readable medium having stored thereon a computer program, characterized in that, The program is executed by the processor to implement the method in any one of claims 1-11.

16. A computer program product comprising a computer program, characterized in that, The computer program is executed by the processor to implement the method in any one of claims 1-11.

Images