Information processing method, device, equipment, storage medium and product

Abstract

The present application provides an information processing method, device, equipment, storage medium and product, which belongs to the field of data batch processing. The method includes: if the current job is completed, determining whether there is a preset cross-domain event for the job; if so, assembling the message information corresponding to the event according to the event name corresponding to the event corresponding to the job, and sending the message information to the corresponding message middleware, so that the message middleware sends the message information to the corresponding downstream scheduling device, and the downstream scheduling device executes the corresponding job for the corresponding target tenant based on the message information. The method of the present application communicates between different cross-domain devices through the message middleware, so that different cross-domain devices can interact effectively.

Description

Technical Field

[0001] The present application relates to the field of data batch processing, and in particular to an information processing method, device, equipment, storage medium and product. Background Art

[0002] For application systems such as credit process management systems, loan systems, deposit systems, payment settlement systems, etc., there are requirements for the background to regularly receive data from external systems, process the data, provide the processed data to the business of the system, and provide data to external systems. The integration of these functional requirements is a batch processing project.

[0003] Traditional batch scheduling across systems can use CONTROL-M-based scheduling systems and Airflow-based scheduling systems. Different business platforms usually build their own scheduling systems. There is a need for interaction between the scheduling systems of these heterogeneous platforms. Due to the different interfaces between different scheduling systems, when different scheduling systems interact with each other, users are required to provide adaptive interfaces for the corresponding scheduling systems.

[0004] However, the interfaces of different scheduling systems are often quite different and closed, which brings instability to the interaction between different cross-scheduling systems. Summary of the invention

[0005] The present application provides an information processing method, apparatus, device, storage medium and product, which are used to solve the problem that interfaces of different scheduling systems are often quite different, so that different cross-scheduling systems cannot interact well.

[0006] In a first aspect, the present application provides an information processing method, comprising:

[0007] If the current job is completed, determining whether there is a preset cross-domain event for the job;

[0008] If so, assemble the message information corresponding to the event according to the event name corresponding to the event corresponding to the job, and send the message information to the corresponding message middleware, so that the message middleware sends the message information to the corresponding downstream scheduling device, and the downstream scheduling device executes the corresponding job for the corresponding target tenant based on the message information.

[0009] In a second aspect, the present application also provides an information processing method, comprising:

[0010] Receive message information sent by the message middleware, parse the message information to obtain the event name corresponding to the event, the message information is assembled by the upstream scheduling device according to the event name corresponding to the event corresponding to the job after determining that there is a preset cross-domain event in the job;

[0011] Determine whether a corresponding cache exists;

[0012] If there is a corresponding cache, the corresponding target tenant is determined according to the event name in the cache area, and the corresponding job is executed for the corresponding target tenant.

[0013] In a third aspect, the present application provides an information processing device, including:

[0014] A first determining unit, configured to determine whether a preset cross-domain event exists in the current job if the current job is completed;

[0015] The first processing unit is used to assemble the message information corresponding to the event according to the event name corresponding to the event corresponding to the job, and send the message information to the corresponding message middleware, so that the message middleware sends the message information to the corresponding downstream scheduling device, and the downstream scheduling device executes the corresponding job for the corresponding target tenant based on the message information.

[0016] In a fourth aspect, the present application further provides an information processing device, comprising:

[0017] A receiving unit, used to receive message information sent by the message middleware, parse the message information to obtain an event name corresponding to the event, wherein the message information is assembled by the upstream scheduling device according to the event name corresponding to the event corresponding to the job after determining that there is a preset cross-domain event in the job;

[0018] A second determining unit, used to determine whether a corresponding cache exists;

[0019] The second processing unit is configured to determine the corresponding target tenant according to the event name in the cache area if a corresponding cache exists, and execute a corresponding operation for the corresponding target tenant.

[0020] In a fifth aspect, the present invention provides an upstream scheduling device, comprising: a processor, a memory and a transceiver;

[0021] Interconnection of processor, memory and transceiver circuits;

[0022] Memory stores computer-executable instructions;

[0023] A transceiver, used to send and receive data and requests;

[0024] The processor executes the computer-executable instructions stored in the memory, so that the processor performs the method as described in the first aspect.

[0025] In a sixth aspect, the present invention provides a downstream scheduling device, comprising: a processor, a memory and a transceiver;

[0026] Interconnection of processor, memory and transceiver circuits;

[0027] Memory stores computer-executable instructions;

[0028] A transceiver, used to send and receive data and requests;

[0029] The processor executes the computer-executable instructions stored in the memory, so that the processor performs the method as described in the second aspect.

[0030] In a seventh aspect, the present invention provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are executed by a processor, they are used to implement the method described in the first aspect or the second aspect.

[0031] In an eighth aspect, the present invention provides a computer program product, comprising a computer program, which implements the method described in the first aspect or the second aspect when executed by a processor.

[0032] The present application provides an information processing method, apparatus, device, storage medium and product. If the current job is completed, it is determined whether there is a preset cross-domain event for the job; if so, the message information corresponding to the event is assembled according to the event name corresponding to the event corresponding to the job, and the message information is sent to the corresponding message middleware, so that the message middleware sends the message information to the corresponding downstream scheduling device, and the downstream scheduling device executes the corresponding job for the corresponding target tenant based on the message information, and communicates between different cross-domain devices through the message middleware, so that different cross-domain devices can interact effectively. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0034] Figure 1 It is a schematic diagram of the network architecture of the information processing method provided by the present invention;

[0035] Figure 2 is a flowchart of an information processing method provided by Embodiment 1 of the present invention;

[0036] Figure 3 This is a schematic diagram of the device connection relationship of the information processing method provided by an embodiment of the present invention;

[0037] Figure 4 is a flowchart of an information processing method provided by Embodiment 2 of the present invention;

[0038] Figure 5 is a flowchart of an information processing method provided by Embodiment 3 of the present invention;

[0039] Figure 6 is a flowchart of an information processing method provided by Embodiment 5 of the present invention;

[0040] Figure 7 is a flowchart of an information processing method provided by Embodiment 8 of the present invention;

[0041] Figure 8 is a flowchart of an information processing method provided by Embodiment 9 of the present invention;

[0042] Fig. 9 is a flowchart of an information processing method provided by Embodiment 10 of the present invention;

[0043] Fig.10 is a schematic diagram of the structure of an information processing device provided by an embodiment of the present invention;

[0044] Fig.11 is a schematic diagram of the structure of an information processing device provided by another embodiment of the present invention;

[0045] Fig.12 is a block diagram of an upstream scheduling device for implementing the information processing method of an embodiment of the present invention;

[0046] Fig.13 It is a block diagram of a downstream scheduling device for implementing the information processing method of an embodiment of the present invention.

[0047] The above drawings have shown clear embodiments of the present application, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0048] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0049] In order to clearly understand the technical solution of the present application, the solution of the prior art is first introduced in detail.

[0050] For application systems such as credit process management systems, loan systems, deposit systems, payment settlement systems, etc., there are requirements for the background to receive data from external systems at regular intervals, process data, provide the processed data to the business of the system, and provide data to external systems. The integration of these functional requirements is a batch processing project. Traditional batch scheduling across systems can use CONTROL-M-based scheduling systems and Airflow-based scheduling systems, etc. Different business platforms usually build their own scheduling systems, such as traditional big data platforms and AI platforms. There is a need for interaction between the scheduling systems of these heterogeneous platforms. For example, the required data on the AI ​​platform is obtained after processing on the big data platform, which requires communication between different platforms. Since the API interfaces between the scheduling systems of different platforms are different, when different scheduling systems interact, users need to provide adaptive API interfaces for the corresponding scheduling systems.

[0051] However, the API interfaces of different scheduling systems are often quite different and closed, lacking the necessary means of interaction, which brings instability to the interaction between different cross-scheduling systems. Moreover, there is no unified message for cross-system communication through APIs.

[0052] Therefore, in view of the problem that the interfaces of different scheduling systems in the prior art are often quite different, which makes it difficult for different cross-scheduling systems to interact well, the inventors found in their research that communication between different cross-domain devices is carried out through message middleware. If the current job is completed, it is determined whether there is a preset cross-domain event for the job; if so, the message information corresponding to the event is assembled according to the event name corresponding to the job, and the message information is sent to the corresponding message middleware, so that the message middleware can send the message information to the corresponding downstream scheduling device, and the downstream scheduling device executes the corresponding job for the corresponding target tenant based on the message information. The same message information is defined to facilitate the downstream scheduling domain to subscribe and process according to the message information.

[0053] Therefore, based on the above creative findings, the inventors have proposed a technical solution of the embodiment of the present invention. The network architecture and application scenarios of the information processing method provided by the embodiment of the present invention are introduced below.

[0054] like Figure 1As shown, the network architecture corresponding to the information processing method provided by the embodiment of the present invention includes: an upstream scheduling device 1, a RocketMQ message middleware 2 and a downstream scheduling device 3. The RocketMQ message middleware 2 is communicated with the upstream scheduling device 1 and the downstream scheduling device 3 respectively. If the upstream scheduling device 1 determines that the current job is completed, it determines whether there is a preset cross-domain event for the current job; if so, it assembles the message information corresponding to the event according to the event name corresponding to the event corresponding to the job, and sends the message information to the RocketMQ message middleware 2. The RocketMQ message middleware 2 is communicated with multiple downstream scheduling devices 3. The RocketMQ message middleware 2 sends the message information to the corresponding downstream scheduling device 3. Figure 1 Only one downstream scheduling device 3 is shown in the figure. The downstream scheduling device 3 parses the message information to obtain the corresponding event name and determines whether there is a corresponding cache. If there is a corresponding cache, the corresponding target tenant is determined according to the event name in the cache area, and the corresponding job is performed for the corresponding target tenant. The communication between different cross-domain devices is carried out through the message middleware, so that different cross-domain devices can interact effectively. The same message information is defined to facilitate the subscription processing of the downstream scheduling domain.

[0055] Embodiment 1

[0056] Figure 2 is a flow chart of the information processing method provided in the first embodiment of the present invention, such as Figure 2 As shown, the execution subject of the information processing method provided in this embodiment is an information processing device, and the information processing device is located in the upstream scheduling device. The information processing method provided in this embodiment includes the following steps:

[0057] Step 101: If the current job is completed, determine whether there is a preset cross-domain event for the current job.

[0058] In this embodiment, the upstream scheduling device and the downstream scheduling device communicate with each other through the middleware. The upstream scheduling device is connected to at least one upstream tenant terminal in communication. The upstream scheduling domain can perform corresponding operations for each tenant. The downstream scheduling device is connected to at least one downstream tenant terminal in communication. The downstream scheduling domain can perform corresponding operations for each tenant. Among them, the upstream scheduling device is also called the upstream scheduling domain, and the downstream scheduling device is also called the downstream scheduling domain. Figure 3As shown, the upstream scheduling system includes upstream scheduling device A, upstream scheduling device B and upstream scheduling device C, wherein upstream scheduling device A is connected to tenant A1 terminal and tenant A2 respectively, upstream scheduling device B is connected to tenant B1 terminal and tenant B2 respectively, upstream scheduling device C is connected to tenant C1, and the upstream scheduling device can perform corresponding operations for each tenant. Upstream scheduling device A, upstream scheduling device B and upstream scheduling device are connected to the message middleware RocketMQ, and RocketMQ is respectively connected to downstream scheduling device D, downstream scheduling device E and downstream scheduling device F of the downstream scheduling system, wherein downstream scheduling device D is respectively connected to tenant D1, downstream scheduling device E is connected to tenant E1, and downstream scheduling device F is respectively connected to tenant F1 and tenant F2, and the downstream scheduling device can perform corresponding operations for each tenant.

[0059] Among them, the RocketMQ architecture is divided into message producers and message consumers. Producers produce messages and put them into RocketMQ, and consumers pull messages from RocketMQ for consumption. RocketMQ is a publish / subscribe model, that is, after a producer generates and sends a message, it can be received by multiple consumers. The generator is the upstream scheduling domain, which publishes the corresponding message to RocketMQ, and the consumer is the downstream scheduling domain, which subscribes to messages from RocketMQ. It should be noted that the message middleware can also be other suitable message middleware, not limited to RocketMQ.

[0060] In this embodiment, it is determined whether the current job is completed. If the current job is completed, it is further determined whether there is a preset cross-domain event for the job, wherein the cross-domain event is a pre-configured cross-domain output event, which is set according to actual conditions.

[0061] Step 102, if yes, assemble the message information corresponding to the event according to the event name corresponding to the job, and send the message information to the corresponding message middleware, so that the message middleware sends the message information to the corresponding downstream scheduling device, and the downstream scheduling device executes the corresponding job for the corresponding target tenant based on the message information.

[0062] In this embodiment, if there is a preset cross-domain event, it means that a tenant of the downstream scheduling device has subscribed to the event. The upstream scheduling device assembles the message information corresponding to the event according to the event name corresponding to the event. Different events have different names. The message information is sent to the corresponding message middleware, and the message middleware sends the message information to the corresponding downstream scheduling device, and the downstream scheduling device performs the corresponding operation for the corresponding target tenant based on the message information.

[0063] In this embodiment, if the current job is completed, it is determined whether there is a preset cross-domain event for the current job. If so, the message information corresponding to the event is assembled according to the event name corresponding to the event corresponding to the job, and the message information is sent to the downstream scheduling device. The downstream scheduling device executes the corresponding job for the corresponding target tenant based on the message information, and communicates between different cross-domain devices through the message middleware, so that different cross-domain devices can interact effectively. Compared with the existing method, there is no need for the user to provide an adaptive interface for the corresponding scheduling system.

[0064] Embodiment 2

[0065] Figure 4 is a flow chart of an information processing method provided by Embodiment 2 of the present invention, such as Figure 4 As shown, based on the information processing method provided in the first embodiment of the present invention, the message information corresponding to the event is further refined according to the event name corresponding to the event corresponding to the job in step 102, which specifically includes the following steps:

[0066] Step 102a, obtaining an event name corresponding to the event, a corresponding event business date, a corresponding event identifier, a corresponding upstream scheduling device identifier, and a corresponding upstream tenant identifier.

[0067] In this embodiment, the relevant information of the event is obtained, including the event name, event business date, event identifier, upstream scheduling device identifier and upstream tenant identifier, and the event identifier is the event batch number. Among them, the upstream scheduling device identifier can be the name of the upstream scheduling device that completes the job, and the upstream scheduling device completes the corresponding job for the corresponding upstream tenant, and the upstream tenant name is the upstream tenant identifier.

[0068] Step 102b, assembling the message information corresponding to the event based on the event name corresponding to the event, the corresponding event business date, the corresponding event identifier, the corresponding upstream scheduling device identifier and the corresponding upstream tenant identifier.

[0069] In this embodiment, the message information is assembled based on the event name, event business date, event identifier, upstream scheduling device identifier and upstream tenant identifier corresponding to the event, and the message information is further published to the message middleware, which sends the message information to the downstream scheduling device. The same message information is defined to facilitate the downstream scheduling domain to determine the tenant who subscribes to the message information and execute the corresponding job for the tenant.

[0070] Embodiment 3

[0071] Figure 5 is a flow chart of an information processing method provided by Embodiment 3 of the present invention, such as Figure 5As shown, based on the information processing method provided in the first embodiment of the present invention, after sending the message information to the corresponding message middleware in step 102, the following steps are also included:

[0072] Step 1021, determine whether the message information is sent successfully.

[0073] In this embodiment, it is determined whether the message information is sent successfully, that is, the upstream scheduling device determines whether the message information is sent to the corresponding message middleware.

[0074] Step 1022: If not, the message information is added to the cross-domain event failure table, and the status information of the message information is recorded as to be reissued, and the message information with the status information of to be reissued in the cross-domain event failure table is reissued.

[0075] In this embodiment, if the message information is not sent successfully, the message information is further added to the cross-domain event failure table, and the status information of the message information is recorded as to be resent. The message information with status information of to be resent in the cross-domain event failure table is resent at a preset interval, and the message information that failed to be sent is attempted to be resent, so that the message middleware can receive the message information.

[0076] Embodiment 4

[0077] Based on the information processing method provided in the third embodiment of the present invention, step 1021 is further refined, and specifically includes the following steps:

[0078] Step 1021a: If a successful sending prompt message fed back by the message middleware is received, it is determined that the message information is sent successfully.

[0079] In this embodiment, the message information is sent to the message middleware, and the message middleware feeds back a prompt message of successful sending after receiving the message information. The message information sending status can be determined by whether the feedback prompt message of successful sending is received. If the prompt message of successful sending fed back by the message middleware is received, it is determined that the message information is sent successfully.

[0080] Step 1021b: If no successful sending prompt information fed back by the message middleware is received, it is determined that the message information is not sent successfully.

[0081] In this embodiment, if the successful sending prompt information fed back by the message middleware is not received, it is determined that the message information has failed to be sent. Whether the information is sent successfully can be accurately determined based on whether the prompt information is received.

[0082] Embodiment 5

[0083] Figure 6 is a flowchart of an information processing method provided by Embodiment 5 of the present invention, such as Figure 6As shown, based on the information processing method provided in the third embodiment of the present invention, the resending of the message information corresponding to the event whose status information in the cross-domain event failure table is to be resent in step 1022 is further refined, and specifically includes the following steps:

[0084] Step 1022c, enable the thread and set a distributed lock for the thread.

[0085] In this embodiment, the thread is enabled, and a distributed lock is set for the thread. The expiration time is set for the distributed lock, for example, 10 minutes, to ensure that only one thread scans the cross-domain event failure table at the same time.

[0086] Step 1022d: The calling thread scans the cross-domain event failure table, and determines whether the status information of the message to be resent in the cross-domain event failure table satisfies the preset resending condition.

[0087] In this embodiment, the enabled thread is called to scan the cross-domain event failure table to further determine whether the status information in the cross-domain event failure table is the message information to be resent meets the preset retransmission condition. The preset retransmission condition is a pre-set retransmission condition. If the condition is met, the information can be resent; if the condition is not met, it means that it has been sent multiple times and the information will not be resent.

[0088] Step 1022e: If yes, the message information in the cross-domain event failure table that meets the preset resending condition is resent to the corresponding message middleware.

[0089] In this embodiment, if the status information in the cross-domain event failure table indicates that the message information to be resent meets the preset resending condition, the message information in the cross-domain event failure table that meets the preset resending condition is sent to the message middleware again.

[0090] It should be noted that if the status information in the cross-domain event failure table indicates that the message information to be retransmitted does not meet the preset retransmission condition, the message information in the cross-domain event failure table that does not meet the preset retransmission condition is deleted from the cross-domain event failure table.

[0091] In this embodiment, if the resending condition is met, the corresponding message information continues to be sent so that the message middleware can receive the corresponding information.

[0092] Embodiment 6

[0093] On the basis of the information processing method provided in the fifth embodiment of the present invention, the step 1022d of determining whether the status information in the cross-domain event failure table is the message information to be resent satisfies the preset resending condition is further refined, specifically including the following steps:

[0094] Step 1022d1, determine whether there is message information in the cross-domain event failure table whose status information is to be resent and the number of resends does not exceed the preset number.

[0095] In this embodiment, the cross-domain event failure table records the number of retransmissions of the message information whose status information is to be retransmitted. When determining whether the message information whose status information is to be retransmitted in the cross-domain event failure table meets the preset retransmission condition, it can be determined by the number of retransmissions. Determine whether there is message information whose status information is to be retransmitted and the number of retransmissions does not exceed the preset number in the cross-domain event failure table, wherein the preset number can be set according to the actual situation.

[0096] Step 1022d2: If there is message information whose status information is to be resent and the number of resends does not exceed the preset number, it is determined that the message information whose status information is to be resent in the cross-domain event failure table meets the preset resend condition.

[0097] In this embodiment, if there is message information whose status information is to be retransmitted and the number of retransmissions does not exceed the preset number of times, it means that the message information has been retransmitted many times, but the number of retransmissions has not reached the upper limit, and it is determined that the message information whose status information in the cross-domain event failure table is to be retransmitted meets the preset retransmission conditions.

[0098] Step 1022d3: If there is message information whose status information is to be resent and whose resending times have exceeded the preset times, it is determined that the message information whose status information is to be resent in the cross-domain event failure table does not meet the preset resending condition.

[0099] In this embodiment, if there is a message whose status information is to be resent and the number of resends has exceeded the preset number of times, it means that the message information has been resent multiple times and the number of resends has reached the upper limit, and it is determined that the message information whose status information in the cross-domain event failure table is to be resent does not meet the preset resend condition. Multiple resends can improve the sending success rate so that the message middleware can receive the corresponding message information.

[0100] Embodiment 7

[0101] Based on the information processing method provided in the fifth embodiment of the present invention, after step 1022e, the following steps are further included:

[0102] Step 1023, determine whether the message information is sent successfully.

[0103] In this embodiment, it is determined whether the message information is sent successfully, that is, the upstream scheduling device determines whether the message information is sent to the message middleware.

[0104] Step 1024: If yes, the status information corresponding to the message information is changed to sent.

[0105] In this embodiment, if the message information is sent successfully, the status information corresponding to the message information is changed from to be resent to sent, and the message information whose status information is sent is not resent subsequently.

[0106] Step 1025: If not, update the number of retransmissions corresponding to the message information and execute step 1022c.

[0107] In this embodiment, if the message information is successful, the number of retransmissions is updated, the number of retransmissions in the cross-domain event failure table is updated, the message information is retransmitted again at a preset interval, the thread is enabled at a preset interval, and a distributed lock is set for the thread, the thread is called to scan the cross-domain event failure table, and it is determined whether the status information in the cross-domain event failure table is the message information to be retransmitted meets the preset retransmission condition. If the condition is met, the message information in the domain event failure table that meets the preset retransmission condition is resent to the corresponding message middleware. Attempt to retransmit the message information that failed to be sent so that the message middleware can receive the message information.

[0108] Embodiment 8

[0109] Figure 7 is a flow chart of an information processing method provided by Embodiment 8 of the present invention, such as Figure 7 As shown, the information processing method provided in this embodiment is executed by an information processing device, and the information processing device is located in a downstream scheduling device. The information processing method provided in this embodiment includes the following steps:

[0110] Step 201, receiving the message information sent by the message middleware, parsing the message information to obtain the event name corresponding to the event, the message information is assembled by the upstream scheduling device according to the event name corresponding to the event corresponding to the job after determining that the job has a preset cross-domain event.

[0111] In this embodiment, the upstream scheduling device and the downstream scheduling device communicate through the message middleware, and the downstream scheduling device receives the message information sent by the message middleware, parses the message information to obtain the event name corresponding to the event, the corresponding event business date, the corresponding event identifier, the corresponding upstream scheduling device identifier, and the corresponding upstream tenant identifier. The message information is assembled by the upstream scheduling device according to the event name corresponding to the event corresponding to the job after determining that there is a cross-domain event in the job.

[0112] Step 202: Determine whether there is a corresponding cache.

[0113] In this embodiment, it is determined whether there is a corresponding cache. If there is a corresponding cache, the corresponding operation is performed in the cache area; if there is no corresponding cache, the corresponding operation is performed in the memory area.

[0114] Step 203: If there is a corresponding cache, the corresponding target tenant is determined in the cache area according to the event name, and a corresponding operation is performed for the corresponding target tenant.

[0115] In this embodiment, if there is a corresponding cache, the corresponding target tenant is determined according to the event name in the cache area, and the target tenant is the tenant who subscribes to the event, and the corresponding job is further performed for the corresponding target tenant. Accessing the cache is faster than directly accessing the database in the memory.

[0116] In this embodiment, determining the target tenant in the cache area can effectively improve efficiency.

[0117] Embodiment 9

[0118] Figure 8 is a flowchart of an information processing method provided by Embodiment 9 of the present invention, such as Figure 8 As shown, based on the information processing method provided in the eighth embodiment of the present invention, the step 203 of determining the corresponding target tenant according to the event name in the cache area is further refined, specifically including the following steps:

[0119] Step 2031: retrieve the mapping relationship between the preset event name and the subscription tenant in the cache area.

[0120] In this embodiment, there is a mapping relationship between a preset event name and a subscription tenant in the cache area, and the subscription tenant pre-subscribes to an event, so that the mapping relationship between the subscribed event name and the subscription tenant is configured according to the subscription relationship. The mapping relationship between the preset event name and the subscription tenant is retrieved in the cache area.

[0121] Step 2032: Determine the corresponding target tenant in the cache area according to the corresponding event name and the mapping relationship between the preset event name and the subscribed tenant.

[0122] In this embodiment, the event name obtained by parsing the message information is determined in the cache area according to the obtained event name and the mapping relationship between the preset event name and the subscribed tenant, that is, the user who subscribes to the event.

[0123] Optionally, before step 2031, the method further includes:

[0124] Step 20311, obtain the latest mapping relationship between the preset event name and the subscription tenant, and use the latest mapping relationship between the preset event name and the subscription tenant to update the mapping relationship between the preset event name and the subscription tenant in the memory area and the cache area.

[0125] In this embodiment, the latest mapping relationship between the preset event name and the subscription tenant is obtained at a preset time interval, the mapping relationship between the preset event name and the subscription tenant stored in the memory area is updated with the latest mapping relationship between the preset event name and the subscription tenant, and the mapping relationship between the preset event name and the subscription tenant in the cache area is updated with the latest mapping relationship between the preset event name and the subscription tenant, so that the mapping relationship between the memory area and the cache area is kept at the latest version.

[0126] Embodiment 10

[0127] Fig. 9 is a flowchart of an information processing method provided by Embodiment 10 of the present invention, such as Fig. 9 As shown, based on the information processing method provided in Embodiment 9 of the present invention, step 2032 is further refined, specifically including the following steps:

[0128] Step 2032a: Match the corresponding event name with the preset event name in the mapping relationship in the cache area.

[0129] In this embodiment, the acquired event name is matched with the preset event name in the mapping relationship in the cache area, and the target tenant is determined according to the matching result.

[0130] Step 2032b: Determine in the cache area a subscription tenant corresponding to a preset event name that matches the corresponding event name, and determine the corresponding subscription tenant as the corresponding target tenant.

[0131] In this embodiment, a subscription tenant corresponding to a preset event name matching the corresponding event name is determined in the cache area, and the subscription tenant is determined as the target tenant. Matching in the cache area can effectively alleviate system pressure.

[0132] Embodiment 11

[0133] Based on the information processing method provided in the eighth embodiment of the present invention, after step 202, the following steps are further included:

[0134] Step 2021: If there is no corresponding cache, the corresponding target tenant is determined in the memory area according to the event name, and a corresponding operation is performed for the corresponding target tenant.

[0135] In this embodiment, if there is no corresponding cache, the corresponding operation is performed in the memory area, and the corresponding target tenant is determined in the memory area according to the event name. Specifically, there is a mapping relationship between the preset event name and the subscribed tenant in the memory area, and the subscribed tenant has subscribed to an event in advance, so the mapping relationship between the subscribed event name and the subscribed tenant is configured according to the subscription relationship. The mapping relationship between the preset event name and the subscribed tenant is retrieved in the memory area, and the target tenant, that is, the user who subscribes to the event, is determined in the memory area according to the obtained event name and the mapping relationship between the preset event name and the subscribed tenant. The corresponding operation is further performed for the corresponding target tenant.

[0136] In this embodiment, access to the cache is faster than directly accessing the database in the memory. Not only the memory but also the cache can be accessed, and multiple methods are provided.

[0137] Embodiment 12

[0138] Based on the information processing method provided in the eighth embodiment of the present invention, after step 203, the following steps are further included:

[0139] Step 204 , a prompt message indicating that the message has been sent successfully is fed back to the message middleware, so that the message middleware can confirm that the message has been consumed successfully according to the prompt message.

[0140] In this embodiment, after receiving the message information sent by the message middleware, a prompt message of successful message sending is fed back to the message middleware, and the message middleware confirms that the message information is successfully consumed based on the prompt information, which is equivalent to the downstream scheduling domain device confirming the message information. Under normal circumstances, the message middleware sends 16 times by default. If all 16 times fail, it will no longer be sent. As a consumer, when the downstream scheduling device pulls information from the message middleware, it will not pull the message information that has been successfully sent, that is, the message information that has been successfully consumed. This avoids the resending of successfully sent information and reduces the repeated operations of the middleware.

[0141] Fig.10 is a schematic diagram of the structure of an information processing device provided by an embodiment of the present invention, such as Fig.10 As shown, the information processing device 200 provided in this embodiment includes a first determining unit 201 and a first processing unit 202 .

[0142] The first determination unit 201 is used to determine whether there is a preset cross-domain event for the job if the current job is completed. The first processing unit 202 is used to assemble the message information corresponding to the event according to the event name corresponding to the job, and send the message information to the corresponding message middleware, so that the message middleware sends the message information to the corresponding downstream scheduling device, and the downstream scheduling device executes the corresponding job for the corresponding target tenant based on the message information.

[0143] Optionally, the first processing unit is also used to obtain the event name corresponding to the event, the corresponding event business date, the corresponding event identifier, the corresponding upstream scheduling device identifier and the corresponding upstream tenant identifier; and assemble the event corresponding message information based on the event name corresponding to the event, the corresponding event business date, the corresponding event identifier, the corresponding upstream scheduling device identifier and the corresponding upstream tenant identifier.

[0144] Optionally, the first determination unit is also used to determine whether the message information is sent successfully; if not, the message information is added to the cross-domain event failure table, and the status information of the message information is recorded as to be reissued, and the message information with status information of to be reissued in the cross-domain event failure table is reissued.

[0145] Optionally, the first determination unit is further configured to determine that the message information is sent successfully if a prompt message indicating successful sending is fed back by the message middleware is received; and to determine that the message information is not sent successfully if no prompt message indicating successful sending is fed back by the message middleware is received.

[0146] Optionally, the first processing unit is further used to enable the thread and set a distributed lock for the thread;

[0147] The calling thread scans the cross-domain event failure table and determines whether the status information in the cross-domain event failure table for the message information to be resent meets the preset resending conditions; if so, the message information in the cross-domain event failure table that meets the preset resending conditions is resent to the corresponding message middleware.

[0148] Optionally, the first processing unit is also used to determine whether there is message information in the cross-domain event failure table whose status information is to be retransmitted and the number of retransmissions does not exceed a preset number of times; if there is message information whose status information is to be retransmitted and the number of retransmissions does not exceed a preset number of times, then it is determined that the message information in the cross-domain event failure table whose status information is to be retransmitted meets the preset retransmission condition; if there is message information whose status information is to be retransmitted and the number of retransmissions has exceeded a preset number of times, then it is determined that the message information in the cross-domain event failure table whose status information is to be retransmitted does not meet the preset retransmission condition.

[0149] Optionally, the first determination unit is further used to determine whether the message information is sent successfully; if so, change the status information of the message information to sent; if not, update the number of retransmissions of the message information and enable the thread.

[0150] Fig.11 is a schematic diagram of the structure of an information processing device provided by another embodiment of the present invention. Fig.11 As shown, the information processing device 300 provided in this embodiment includes a receiving unit 301 , a second determining unit 302 , and a second processing unit 303 .

[0151] Among them, the receiving unit 301 is used to receive the message information sent by the message middleware, parse the message information to obtain the event name corresponding to the event, and the message information is assembled by the upstream scheduling device according to the event name corresponding to the job after determining that there is a preset cross-domain event in the job. The second determination unit 302 is used to determine whether there is a corresponding cache. The second processing unit 303 is used to determine the corresponding target tenant according to the event name in the cache area if there is a corresponding cache, and execute the corresponding job for the corresponding target tenant.

[0152] Optionally, the second processing unit is further used to retrieve the mapping relationship between the preset event name and the subscribed tenant in the cache area; and determine the corresponding target tenant in the cache area according to the corresponding event name and the mapping relationship between the preset event name and the subscribed tenant.

[0153] Optionally, the second processing unit is also used to match the corresponding event name with the preset event name in the mapping relationship in the cache area; determine the subscription tenant corresponding to the preset event name that matches the corresponding event name in the cache area, and determine the corresponding subscription tenant as the corresponding target tenant.

[0154] Optionally, the second processing unit is further configured to determine a corresponding target tenant according to the event name in the memory area if there is no corresponding cache, and execute a corresponding job for the corresponding target tenant.

[0155] Optionally, the second processing unit is further used to feed back prompt information of successful message sending to the message middleware, so that the message middleware can confirm successful consumption of the message information according to the prompt information.

[0156] Fig.12 is a block diagram of an upstream scheduling device for implementing the information processing method of an embodiment of the present invention, such as Fig.12 As shown, the upstream scheduling device 400 includes: a memory 401 , a processor 402 and a transceiver 403 .

[0157] The processor 402, the memory 401 and the transceiver 403 are interconnected;

[0158] A transceiver 403, used for sending and receiving data and requests;

[0159] The memory 401 stores computer executable instructions;

[0160] The processor 402 executes the computer execution instructions stored in the memory 401, so that the processor 402 executes the methods provided in Embodiments 1 to 7.

[0161] Fig.13 is a block diagram of a downstream scheduling device for implementing the information processing method of an embodiment of the present invention, such as Fig.13 As shown, the downstream scheduling device 500 includes: a memory 501 , a processor 502 and a transceiver 503 .

[0162] The processor 502, the memory 501 and the transceiver 503 are interconnected;

[0163] A transceiver 503, used for sending and receiving data and requests;

[0164] The memory 501 stores computer executable instructions;

[0165] The processor 502 executes the computer execution instructions stored in the memory 501, so that the processor 502 executes the methods provided in Embodiments 8 to 12.

[0166] In an exemplary embodiment, a computer-readable storage medium is further provided, in which computer-executable instructions are stored. The computer-executable instructions are executed by a processor to execute the method in any one of the above embodiments.

[0167] In an exemplary embodiment, a computer program product is also provided, including a computer program, and the computer program is executed by a processor to execute the method in any one of the above embodiments.

[0168] Those skilled in the art will readily appreciate other embodiments of the present invention after considering the specification and practicing the invention disclosed herein. The present invention is intended to cover any variations, uses or adaptations of the present invention that follow the general principles of the present invention and include common knowledge or customary techniques in the art that are not disclosed by the present invention. The description and examples are to be considered exemplary only, and the true scope and spirit of the present invention is indicated by the following claims.

[0169] It should be understood that the present invention is not limited to the exact construction that has been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present invention is limited only by the appended claims.

Claims

1. An information processing method, characterized in that: The method comprises: If the current job is completed, determining whether there is a preset cross-domain event for the job; If so, assemble the message information corresponding to the event according to the event name corresponding to the event corresponding to the job, and send the message information to the corresponding message middleware, so that the message middleware sends the message information to the corresponding downstream scheduling device. The message middleware is connected to multiple downstream scheduling devices, and the downstream scheduling device parses the message information to obtain the event name corresponding to the event, determines the corresponding target tenant in the cache area according to the mapping relationship between the event name and the preset event name and the subscribed tenant, and executes the corresponding job for the corresponding target tenant. The cache area contains the mapping relationship.

2. The method according to claim 1, characterized in that The assembling of message information corresponding to the event according to the event name corresponding to the event corresponding to the job includes: Obtain an event name, a corresponding event business date, a corresponding event identifier, a corresponding upstream scheduling device identifier, and a corresponding upstream tenant identifier corresponding to the event; The message information corresponding to the event is assembled based on the event name corresponding to the event, the corresponding event business date, the corresponding event identifier, the corresponding upstream scheduling device identifier and the corresponding upstream tenant identifier.

3. The method according to claim 1, characterized in that After sending the message information to the corresponding message middleware, the method further includes: Determine whether the message information is sent successfully; If not, the message information is added to the cross-domain event failure table, and the status information of the message information is recorded as to be reissued, and the message information whose status information in the cross-domain event failure table is to be reissued is reissued.

4. The method according to claim 3, characterized in that The determining whether the message information is sent successfully includes: If a successful sending prompt message fed back by the message middleware is received, it is determined that the message information is sent successfully; If the successful sending prompt information fed back by the message middleware is not received, it is determined that the message information is not sent successfully.

5. The method according to claim 3, characterized in that: The reissuing the message information to be resent for which the status information in the cross-domain event failure table is to be resent includes: Enable a thread and set a distributed lock for the thread; Calling the thread to scan the cross-domain event failure table, and determining whether the message information to be resent in the cross-domain event failure table satisfies a preset resending condition; If so, the message information in the cross-domain event failure table that meets the preset resending conditions is resent to the corresponding message middleware.

6. The method according to claim 5, characterized in that The determining whether the status information in the cross-domain event failure table is the message information to be resent satisfies the preset resending condition includes: Determine whether there is message information in the cross-domain event failure table whose status information is to be resent and the number of resends does not exceed the preset number; If there is a message whose status information is to be resent and the number of resends does not exceed the preset number of times, it is determined that the message information whose status information is to be resent in the cross-domain event failure table meets the preset resend condition; If there is message information whose status information is to be resent and whose resending times have exceeded a preset number, it is determined that the message information whose status information is to be resent in the cross-domain event failure table does not meet the preset resending condition.

7. The method according to claim 5, characterized in that After the message information that meets the preset resending condition in the cross-domain event failure table is resent to the corresponding message middleware, the method further includes: Determine whether the message information is sent successfully; If yes, changing the status information of the message information to sent; If not, the number of retransmissions of the message information is updated, and the step of enabling the thread is executed.

8. An information processing method, characterized in that: The method comprises: Receive message information sent by the message middleware, parse the message information to obtain the event name corresponding to the event, the message information is assembled by the upstream scheduling device according to the event name corresponding to the event corresponding to the job after determining that there is a preset cross-domain event in the job, and the message middleware is connected to multiple downstream scheduling devices; Determine whether a corresponding cache exists; If there is a corresponding cache, the corresponding target tenant is determined in the cache area according to the mapping relationship between the event name and the preset event name and the subscribed tenant, and the corresponding operation is performed for the corresponding target tenant, and the cache area contains the mapping relationship.

9. The method according to claim 8, characterized in that The method further comprises: Retrieve the mapping relationship between the preset event name and the subscription tenant in the cache area.

10. The method according to claim 9, characterized in that The determining the corresponding target tenant in the cache area according to the mapping relationship between the corresponding event name and the preset event name and the subscribed tenant includes: Matching the corresponding event name with the preset event name in the mapping relationship in the cache area; Determine in the cache area a subscription tenant corresponding to the preset event name that matches the corresponding event name, and determine the corresponding subscription tenant as the corresponding target tenant.

11. The method according to claim 8, characterized in that After determining whether there is a corresponding cache, the method further includes: If there is no corresponding cache, the corresponding target tenant is determined according to the event name in the memory area, and the corresponding job is executed for the corresponding target tenant.

12. The method according to claim 8, characterized in that After receiving the message information sent by the message middleware, the method further includes: Feedback prompt information of successful message sending to the message middleware, so that the message middleware can confirm successful message information consumption according to the prompt information.

13. An information processing device, characterized in that: The device comprises: A first determining unit, configured to determine whether a preset cross-domain event exists in the current job if the current job is completed; The first processing unit is used to assemble the message information corresponding to the event according to the event name corresponding to the event corresponding to the job, and send the message information to the corresponding message middleware, so that the message middleware sends the message information to the corresponding downstream scheduling device, the message middleware is connected to multiple downstream scheduling devices, the downstream scheduling device parses the message information to obtain the event name corresponding to the event, determines the corresponding target tenant in the cache area according to the mapping relationship between the event name and the preset event name and the subscribed tenant, and executes the corresponding job for the corresponding target tenant, and the cache area contains the mapping relationship.

14. An information processing device, characterized in that: The device comprises: A receiving unit, used to receive message information sent by the message middleware, parse the message information to obtain an event name corresponding to the event, the message information is assembled by the upstream scheduling device according to the event name corresponding to the event corresponding to the job after determining that there is a preset cross-domain event in the job, and the message middleware is connected to multiple downstream scheduling devices; A second determining unit, used to determine whether a corresponding cache exists; The second processing unit is used to determine the corresponding target tenant in the cache area according to the mapping relationship between the event name and the preset event name and the subscribed tenant if a corresponding cache exists, and perform corresponding operations for the corresponding target tenant, and the cache area contains the mapping relationship.

15. An upstream scheduling device, comprising: Processor, memory and transceiver; Interconnection of processor, memory and transceiver circuits; A transceiver, used to send and receive data and requests; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory, so that the processor performs the method according to any one of claims 1 to 7.

16. A downstream scheduling device, comprising: Processor, memory and transceiver; Processor, memory and transceiver circuit interconnection; A transceiver, used to send and receive data and requests; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory, so that the processor performs the method according to any one of claims 8 to 12.

17. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, which are used to implement the method according to any one of claims 1 to 12 when executed by a processor.

18. A computer program product, comprising a computer program, which implements the method according to any one of claims 1 to 12 when executed by a processor.

Images