EDA event transmission method and device, equipment and medium

Abstract

The invention relates to the technical field of computers, in particular to an EDA event transmission method and device, equipment and a medium, and is used for solving the problem that when the transmission process of an EDA event is that the transmission modes of different subscribers are the same, the resource consumption of a publisher is relatively high. The method comprises the following steps: if a signing sending mode of a to-be-transmitted EDA event is a first preset mode, directly sending the to-be-transmitted EDA event to a non-target subscriber for each non-target subscriber; and for each target subscriber, if the subscription information of the to-be-transmitted EDA event meets a triggering condition corresponding to the target subscriber, adding the to-be-transmitted EDA event into a set corresponding to the target subscriber, and when the EDA event in the set corresponding to the target subscriber meets a first preset condition, transmitting the to-be-transmitted EDA event to the target subscriber. And packaging the EDA events in the set corresponding to the target subscriber together and sending the EDA events to the target subscriber.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a method, device, equipment and medium for transmitting an EDA event. Background Art

[0002] Event Driven Architecture (EDA) is an integrated model for publishing, capturing, processing, and responding to events in distributed systems in real time. If an event occurs in an application, the event generated by EDA is referred to as an EDA event, which will automatically be sent to other applications so that all applications that need to know about the event can take corresponding actions.

[0003] At present, the delivery of EDA events usually adopts the publish / subscribe mechanism. The current delivery process of EDA events is that the sending method of different subscribers is the same, but some subscribers need to subscribe to more events, while some subscribers need to subscribe to fewer events. In this regard, a large number of EDA events generated need to be sent to the subscriber. Since a sending process needs to be generated each time it is sent, it will lead to relatively large resource consumption. Summary of the invention

[0004] The embodiments of the present application provide an EDA event delivery method, apparatus, device and medium, which are used to solve the problem that the EDA event delivery process may cause large resource consumption of the publisher when the sending methods of different subscribers are the same.

[0005] In a first aspect, the present application provides a method for delivering an EDA event, comprising:

[0006] Get the EDA event to be delivered;

[0007] If the contracted sending mode of the EDA event to be delivered is the first preset mode, when the subscribers corresponding to the EDA event to be delivered include non-target subscribers, for each non-target subscriber, the EDA event to be delivered is directly sent to the non-target subscriber;

[0008] When the subscribers corresponding to the EDA event to be delivered include the target subscriber, for each target subscriber, if the contract information of the EDA event to be delivered meets the trigger condition corresponding to the target subscriber, the EDA event to be delivered is added to the collection corresponding to the target subscriber; when the EDA event in the collection corresponding to the target subscriber meets the first preset condition, the EDA events in the collection corresponding to the target subscriber are packaged together and sent to the target subscriber.

[0009] The above method can send the EDA event to be delivered directly to the non-target subscriber when the subscribers corresponding to the EDA event to be delivered include the target subscriber and the non-target subscriber, and add the EDA event to be delivered to the collection corresponding to the target subscriber when the contract information of the EDA event to be delivered meets the trigger condition corresponding to the target subscriber. When the EDA events in the collection corresponding to the target subscriber meet the preset conditions, they are packaged together and sent to the target subscriber. This not only ensures that the non-target subscriber can receive the EDA event in time, but also reduces the number of sending processes, alleviating the problem of resource waste on the publisher.

[0010] In a possible embodiment, before directly sending the to-be-delivered EDA event to each non-target subscriber, the method further includes:

[0011] If the number of subscribers corresponding to the EDA event to be delivered is greater than 1, the number of the EDA events to be delivered is copied to the same number as the number of subscribers corresponding to the EDA event to be delivered.

[0012] In a possible embodiment, after obtaining the EDA event to be transmitted, the method further includes:

[0013] If the contracted sending mode of the EDA event to be delivered is the second preset mode, stopping sending the EDA event to be delivered to the subscriber corresponding to the EDA event to be delivered.

[0014] In a possible embodiment, the signing sending mode of the EDA event to be delivered is determined in the following manner:

[0015] According to the event type of the EDA event to be delivered, a preset mode is selected from a plurality of preset modes, and the selected preset mode is used as the signing and sending mode of the EDA event to be delivered; or

[0016] When the second preset condition is met, a selection interface is displayed; wherein the content of the selection interface includes multiple preset modes; and in response to the user's selection instruction, the preset mode selected in the selection instruction is used as the signing and sending mode of the EDA event to be transmitted.

[0017] In a possible embodiment, the trigger condition corresponding to the target subscriber is determined in the following manner:

[0018] When the third preset condition is met, an event configuration table and an event contract table are displayed; wherein the event configuration table includes multiple content types of the target subscriber; and the event contract table includes a threshold value corresponding to each content type of the target subscriber;

[0019] In response to an input instruction from a user, a trigger condition corresponding to the target subscriber is determined according to the content type input in the input instruction and a threshold value corresponding to the input content type.

[0020] In a possible embodiment, the first preset condition includes part or all of the following:

[0021] The cumulative number of EDA events in the set corresponding to the target subscriber reaches a preset number;

[0022] The cumulative size of EDA events in the set corresponding to the target subscriber exceeds a preset size;

[0023] The content of the EDA event to be delivered in the collection corresponding to the target subscriber includes preset content;

[0024] The time for forming the set corresponding to the target subscriber exceeds the preset time;

[0025] The memory capacity is larger than the preset capacity.

[0026] In a second aspect, the present application provides an EDA event transmission device, including:

[0027] An acquisition module is used to acquire EDA events to be delivered;

[0028] A first processing module, configured to, if the contracted sending mode of the EDA event to be delivered is the first preset mode, directly send the EDA event to be delivered to each non-target subscriber when the subscribers corresponding to the EDA event to be delivered include non-target subscribers;

[0029] The second processing module is used to, when the subscribers corresponding to the EDA event to be delivered include the target subscriber, for each target subscriber, if the contract information of the EDA event to be delivered meets the trigger condition corresponding to the target subscriber, add the EDA event to be delivered to the collection corresponding to the target subscriber; when the EDA event in the collection corresponding to the target subscriber meets the first preset condition, package the EDA events in the collection corresponding to the target subscriber together and send them to the target subscriber.

[0030] In a possible embodiment, the first processing module is specifically configured to copy the number of the EDA events to be delivered to the same number of subscribers as the number of subscribers corresponding to the EDA events to be delivered if the number of subscribers corresponding to the EDA events to be delivered is greater than one.

[0031] In a possible embodiment, the device further includes a third processing module;

[0032] The third processing module is configured to stop sending the EDA event to be delivered to a subscriber corresponding to the EDA event to be delivered if the contracted sending mode of the EDA event to be delivered is the second preset mode.

[0033] In a possible embodiment, the determination module is specifically configured to select a preset mode from a plurality of preset modes according to the event type of the EDA event to be transmitted, and use the selected preset mode as the signing and sending mode of the EDA event to be transmitted; or

[0034] When the second preset condition is met, a selection interface is displayed; wherein the content of the selection interface includes multiple preset modes; and in response to the user's selection instruction, the preset mode selected in the selection instruction is used as the signing and sending mode of the EDA event to be transmitted.

[0035] In a possible embodiment, the second processing module is further used to:

[0036] When the third preset condition is met, an event configuration table and an event contract table are displayed; wherein the event configuration table includes multiple content types of the target subscriber; and the event contract table includes a threshold value corresponding to each content type of the target subscriber;

[0037] In response to an input instruction from a user, a trigger condition corresponding to the target subscriber is determined according to the content type input in the input instruction and a threshold value corresponding to the input content type.

[0038] In a possible embodiment, the first preset condition includes part or all of the following:

[0039] The cumulative number of EDA events in the set corresponding to the target subscriber reaches a preset number;

[0040] The cumulative size of EDA events in the set corresponding to the target subscriber exceeds a preset size;

[0041] The content of the EDA event to be delivered in the collection corresponding to the target subscriber includes preset content;

[0042] The time for forming the set corresponding to the target subscriber exceeds the preset time;

[0043] The memory capacity is larger than the preset capacity.

[0044] In a third aspect, the present application provides an electronic device, including:

[0045] A memory for storing program instructions;

[0046] The processor is used to call the program instructions stored in the memory, and execute the steps included in any one of the methods in the first aspect according to the obtained program instructions.

[0047] In a fourth aspect, the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, wherein the computer program includes program instructions, and when the program instructions are executed by a computer, the computer executes any one of the methods described in the first aspect.

[0048] In a fifth aspect, the present application provides a computer program product, comprising: a computer program code, when the computer program code is run on a computer, the computer executes any one of the methods described in the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0049] Figure 1 A flowchart of a method for delivering an EDA event provided in an embodiment of the present application;

[0050] Figure 2 A schematic diagram of selecting a type of system and subscriber provided in an embodiment of the present application;

[0051] Figure 3 A schematic diagram of a signing and sending mode for selecting an EDA event to be delivered provided in an embodiment of the present application;

[0052] Figure 4 A flowchart of a method for determining a trigger condition corresponding to a target subscriber provided in an embodiment of the present application;

[0053] Figure 5 A schematic diagram of determining a trigger condition corresponding to a target subscriber provided in an embodiment of the present application;

[0054] Figure 6 A schematic diagram of a transmission system of an EDA event provided in an embodiment of the present application;

[0055] Figure 7 A structural diagram of an EDA event transmission device provided in an embodiment of the present application;

[0056] Figure 8 A structural diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0057] In order to make the purpose, technical scheme and advantages of the present application clearer, the technical scheme in the embodiment of the present application will be clearly and completely described below in conjunction with the drawings in the embodiment of the present application. Obviously, the described embodiment is only a part of the embodiment of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the field without making creative work are within the scope of protection of the present application. In the absence of conflict, the embodiments in the present application and the features in the embodiments can be arbitrarily combined with each other. In addition, although the logical order is shown in the flow chart, in some cases, the steps shown or described can be performed in an order different from that here.

[0058] The terms "first" and "second" in the specification and claims of the present application and the above-mentioned drawings are used to distinguish different objects, rather than to describe a specific order. In addition, the term "comprising" and any of their variations are intended to cover non-exclusive protection. For example, a process, method, system, product or device comprising a series of steps or units is not limited to the listed steps or units, but optionally also includes steps or units that are not listed, or optionally also includes other steps or units inherent to these processes, methods, products or devices. "Multiple" in the present application can mean at least two, for example, two, three or more, and the embodiments of the present application are not limited.

[0059] The following is a description of exemplary embodiments of the present application in conjunction with the accompanying drawings, including various details of the embodiments of the present application to facilitate 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 of the present application. Similarly, for the sake of clarity and conciseness, the description of well-known functions and structures is omitted in the following description. It should be noted that in the embodiments of the present application, certain software, components, models and other existing solutions in the industry may be mentioned, which should be considered as exemplary, and their purpose is only to illustrate the feasibility of the implementation of the technical solution of the present application, but it does not mean that the applicant has or will necessarily use the solution.

[0060] In the technical solution of this application, the acquisition, dissemination, storage, and use of data are in compliance with the requirements of relevant national laws and regulations.

[0061] Before introducing the EDA event delivery method provided in the embodiment of the present application, in order to facilitate understanding, the technical background of the embodiment of the present application is first introduced in detail.

[0062] EDA events are generally used in online transactions in the field of financial transactions. Online transactions refer to transactions directly provided by the system to the outside world, which are transactional, real-time and concurrent. Online transactions include withdrawal transactions, balance inquiries and updates, generation of transaction flow, generation of account usage records, generation of accounting vouchers, and registration of deposit and cash account general ledgers.

[0063] At present, the transmission process of EDA events is the same for different subscribers, but some subscribers need to subscribe to more events, while some subscribers need to subscribe to fewer events. Taking the transaction-recording system as an example, withdrawal transactions, balance updates, etc. all need to be sent to the transaction-recording system. The business volume of withdrawal transactions is relatively large, so a large number of EDA events generated need to be sent to the related system. Since each sending requires a sending process, it will lead to relatively large resource consumption.

[0064] For example, it is necessary to subtract the balance from the amount in the user account in the withdrawal system to obtain the remaining amount in the user account. If there is a SMS notification of balance change service, it is necessary to notify the system that executes the service, execute the SMS notification service, and the system that records changes in the user account records the transaction. Therefore, after the EDA event is published by the publisher, the system that executes the service is the first subscriber, and the system that records changes in the user account is the second subscriber. The EDA event needs to be sent to these two subscribers, and the publisher will establish two sending processes, one sending process to the first subscriber and one sending process to the second subscriber.

[0065] However, when another user also makes a withdrawal, but this user does not have the SMS balance change service, then its subscriber is only the system that records the changes in the user's account, and the publisher will establish a sending process, which is sent to the second subscriber. By analogy, when there are a large number of users making withdrawals, the publisher will establish the same number of sending processes as the subscribers corresponding to the large number of EDA events, resulting in excessive resource consumption.

[0066] In response to the above technical problems, the present application proposes the following technical concept: subscribers are differentiated and different EDA event delivery processes are given to different subscribers.

[0067] The technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems are described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0068] Combination Figure 1 As shown, an embodiment of the present application provides a method for transmitting an EDA event, including:

[0069] S100: Obtain the EDA event to be transmitted;

[0070] The EDA event to be transmitted may be generated based on a business, such as an online transaction and a batch transaction.

[0071] S101: If the contracted sending mode of the EDA event to be delivered is the first preset mode, when the subscribers corresponding to the EDA event to be delivered include non-target subscribers, for each non-target subscriber, the EDA event to be delivered is directly sent to the non-target subscriber;

[0072] The first preset mode may be that after receiving an EDA event, the publisher sends it to several specific subscribers. For example, all subscribers are subscribers 1 to 100, and the first preset mode is that after receiving an EDA event, the publisher sends the EDA event to subscribers 20 to 30.

[0073] In some embodiments, on the publisher side, the subscribers corresponding to the event type of each EDA event to be delivered are stored. For example: when the event type is a withdrawal transaction, the subscribers corresponding to the withdrawal transaction include subscriber 1 and subscriber 2; when the event type is balance inquiry and update, the subscribers corresponding to balance inquiry and update include subscriber 1; when the event type is the generation of transaction flow, the subscribers corresponding to the generation of transaction flow include subscribers 1 to subscriber 3; when the event type is the generation of account usage records, the subscribers corresponding to the generation of transaction flow include subscribers 1 to subscriber 3; when the event type is the generation of accounting vouchers, the subscribers corresponding to the generation of transaction flow include subscribers 1 to subscriber 3; when the event type is the registration of the general ledger of deposits and cash accounts, the subscribers corresponding to the generation of transaction flow include subscribers 1 to subscriber 3. When the EDA event to be delivered is obtained, the event type of the EDA event to be delivered is determined, and the subscriber corresponding to the event type is used as the subscriber corresponding to the EDA event to be delivered.

[0074] It should be noted that the subscriber corresponding to each event type can be set based on experience, and the present invention does not impose any specific limitation on this.

[0075] In some embodiments, on the publisher side, each EDA event directly corresponds to its own subscriber, which can be set by itself.

[0076] The non-target subscriber and the target subscriber introduced in the following step 102 may be preset. For example, the preset method may be preset by the user.

[0077] Exemplary, combined Figure 2As shown, the user can enter the user name and password on the login interface. When the user name and password entered by the user are verified to be correct, the main page is displayed. The main page includes multiple options, option 1, option 2, and option 3. For example, option 1 for setting the target subscriber and the non-target subscriber, after the user clicks option 1, the setting interface is displayed, and the system and parameters are displayed by clicking the "+" area. The setting interface includes all the systems in the bank, system 1 to system 10. The user selects one by one and clicks the "OK" button to generate a corresponding relationship between the system and the parameter. By analogy, the user selects system 1 to system 5 as the target subscriber, and the user selects system 6 to system 10 as the non-target subscriber, then the parameters of the subscribers of system 1 to system 10 are saved. The saving method can be shown in Table 1:

[0078] Table 1

[0079]

[0080] When the parameter is 1, it indicates that the system is a target subscriber, and when the parameter is 0, it indicates that the system is a non-target subscriber.

[0081] S102: When the subscribers corresponding to the EDA event to be delivered include the target subscriber, for each target subscriber, if the contract information of the EDA event to be delivered meets the trigger condition corresponding to the target subscriber, the EDA event to be delivered is added to the collection corresponding to the target subscriber. When the EDA event in the collection corresponding to the target subscriber meets the first preset condition, the EDA events in the collection corresponding to the target subscriber are packaged together and sent to the target subscriber.

[0082] Exemplarily, after obtaining the EDA event to be delivered, by querying Table 1, it is determined whether the subscriber corresponding to the EDA event to be delivered is a target subscriber or a non-target subscriber. For example, when the subscribers corresponding to the EDA event to be delivered include subscribers 1 to 3 and subscribers 7 to 8, the subscribers corresponding to the EDA event to be delivered include non-target subscribers and target subscribers. For non-target subscribers, that is, subscribers 7 and 8, the EDA event to be delivered can be sent directly to subscribers 7 and 8 without special processing.

[0083] For subscriber 1, if the contract information of the EDA event to be delivered meets the trigger condition corresponding to subscriber 1, the EDA event to be delivered is added to the collection corresponding to subscriber 1. When the collection corresponding to subscriber 1 meets the first preset condition, the EDA events in the collection corresponding to subscriber 1 are packaged together and sent to subscriber 1. For subscriber 2, if the contract information of the EDA event to be delivered meets the trigger condition corresponding to subscriber 2, the EDA event to be delivered is added to the collection corresponding to subscriber 2. When the collection corresponding to subscriber 2 meets the first preset condition, the EDA events in the collection corresponding to subscriber 2 are packaged together and sent to subscriber 2. For subscriber 3, if the contract information of the EDA event to be delivered meets the trigger condition corresponding to subscriber 3, the EDA event to be delivered is added to the collection corresponding to subscriber 3. When the collection corresponding to subscriber 3 meets the first preset condition, the EDA events in the collection corresponding to subscriber 3 are packaged together and sent to subscriber 3.

[0084] In summary, in the embodiment of the present invention, if there are non-target subscribers among the subscribers corresponding to the EDA event, the EDA event can be sent directly to the non-target subscribers, thus ensuring that the non-target subscribers can receive the EDA event in a timely manner. If there are target subscribers at the EDA time, the EDA event can be added to the set corresponding to the target subscriber, and the EDA event sent to the target subscriber can be sent together to the target subscriber, thus reducing the number of sending processes and alleviating the problem of high resource consumption of the publisher.

[0085] In some embodiments, before directly sending the EDA event to be delivered to each non-target subscriber, the method further includes:

[0086] If the number of subscribers corresponding to the EDA event to be delivered is greater than 1, the number of EDA events to be delivered is copied to the same number as the number of subscribers corresponding to the EDA event to be delivered.

[0087] For the example mentioned in step 102, the subscribers corresponding to the EDA events to be delivered include subscribers 1 to 3 and subscribers 7 to 8, which are 5 subscribers in total. Then the number of EDA events to be delivered is copied to 5.

[0088] In some embodiments, after obtaining the EDA event to be delivered, the method further includes:

[0089] If the contracted sending mode of the EDA event to be delivered is the second preset mode, the sending of the EDA event to be delivered to the subscriber corresponding to the EDA event to be delivered is stopped.

[0090] In detail, since the publisher receives invalid data for all subscribers when it obtains the EDA event to be delivered, the contract sending mode of the EDA event to be delivered can be set to the second preset mode. In this way, the EDA event to be delivered can be stopped from being sent to the subscribers corresponding to the EDA event to be delivered, thereby avoiding sending invalid data to the subscribers and reducing the situation of processing invalid data.

[0091] In some embodiments, the present invention provides an implementation method for determining a contracted sending mode of an EDA event to be delivered:

[0092] Method 1: According to the event type of the EDA event to be delivered, a preset mode is selected from multiple preset modes, and the selected preset mode is used as the signing and sending mode of the EDA event to be delivered.

[0093] For example, the preset mode includes a first preset mode and a second preset mode. When the event type is an event of invalid data, it can be set to the second preset mode. When the event type of the EDA event to be delivered is an event of invalid data, the contract sending mode of the EDA event to be delivered is the second preset mode. When the event type is valid data but only needs to be sent to some specific subscribers, it is set to the first preset mode; when the event type of the EDA event to be delivered is an event of valid data but only needs to be sent to some specific subscribers, the contract sending mode of the EDA event to be delivered is the first preset mode.

[0094] Method 2: When the second preset condition is met, a selection interface is displayed; wherein the content of the selection interface includes multiple preset modes; and in response to the user's selection instruction, the preset mode selected in the selection instruction is used as the signing and sending mode of the EDA event to be transmitted.

[0095] The second preset condition can be that after the user logs in successfully, Figure 2 As shown, the main page is displayed. The user selects option 2 on the main page and the selection interface is displayed. Figure 3 As shown, the selection interface includes a first preset mode and a second preset mode. When the user clicks on the circle signed by the first preset mode, the outer circle turns black and is selected. The first preset mode is the signing and sending mode for the EDA event to be delivered. When the user clicks on the circle signed by the second preset mode, the second preset mode is the signing and sending mode for the EDA event to be delivered.

[0096] In some embodiments, in combination Figure 4 As shown, the triggering condition corresponding to the target subscriber is determined in the following way:

[0097] S400: When the third preset condition is met, an event configuration table and an event contract table are displayed; wherein the event configuration table includes multiple content types of the target subscriber; and the event contract table includes a threshold value corresponding to each content type of the target subscriber;

[0098] S401: responding to an input instruction from a user, and determining a trigger condition corresponding to a target subscriber according to a content type input in the input instruction and a threshold corresponding to the input content type.

[0099] Exemplary, combined Figure 2 As shown, after the user logs in, the main page is displayed. The main page includes multiple options. The user clicks on the configuration option. Figure 5 As shown, the event configuration table and event contract table are displayed. The event configuration table includes multiple content types of the target subscriber, such as account number, card number, transaction amount, balance after transaction, currency, banknote identification, customer number, sub-account, and contract number; when the user selects account number / card number+transaction amount+currency+banknote identification, it means that the four content types of account number / card number, transaction amount, currency, and banknote identification are the content types of the target subscriber. After the user clicks Submit, click the event contract table, and the thresholds corresponding to the four content types of account number / card number, transaction amount, currency, and banknote identification are displayed in the event contract table. For example, the user fills in the account number / card number: 3106666666666666666, transaction amount: 500, currency: 156-RMB, banknote identification: 1, then the threshold corresponding to the account number / card number is 310666666666666666, the threshold corresponding to the transaction amount is 500, the threshold corresponding to the currency is RMB, and the threshold corresponding to the banknote identification is 1. According to the above content types and the thresholds corresponding to the content types, the trigger conditions corresponding to the target subscriber are generated as follows: the account / card number is 3106666666666666666, the transaction amount is greater than 500, the currency is 156-RMB, and the banknote identification is 1.

[0100] Of course, the types of content selected in the trigger conditions include but are not limited to: account / card number mode, account / card number + transaction amount mode, account / card number + balance after transaction mode, account / card number + transaction amount + currency + banknote identification mode, account / card number + balance after transaction + currency + banknote identification mode, customer number mode, sub-account mode, contract number mode, etc. Different subscribers can use different trigger condition modes to subscribe to the same event.

[0101] When executing online transactions or batch transactions, the trigger conditions corresponding to the subscribers of the EDA event are obtained according to the event configuration table, and then the event contract table is accessed to obtain the contract record. The fields involved in the trigger condition mode of each subscriber are used to determine whether the event needs to be pushed to this subscriber.

[0102] In some embodiments, the first preset condition includes part or all of the following:

[0103] The number of EDA events in the collection corresponding to the target subscriber reaches the preset number;

[0104] The cumulative size of EDA events in the collection corresponding to the target subscriber exceeds the preset size;

[0105] The content of the EDA event to be delivered in the collection corresponding to the target subscriber includes preset content;

[0106] The time for forming the collection corresponding to the target subscriber exceeds the preset time;

[0107] The memory capacity is larger than the preset capacity.

[0108] Specifically, when the number of EDA events in the set corresponding to the target subscriber reaches a preset number, the EDA events in the set corresponding to the target subscriber can be packaged together and sent to the target subscriber. When the cumulative size of the EDA events in the set corresponding to the target subscriber exceeds the preset size, it means that the size of the data packet of the EDA events in the set corresponding to the target subscriber exceeds the preset size, and it will be packaged and sent to the target subscriber.

[0109] When the EDA event to be delivered is an emergency event, but also meets the triggering conditions of the EDA event to be delivered, the EDA event to be delivered can be added to the set corresponding to the target subscriber and sent to the target subscriber immediately. For example, when the EDA event to be delivered is not received, the set corresponding to the target subscriber is EDA event 1 and EDA event 2. When the EDA event to be delivered is received, if the content of the EDA event contains preset content, EDA event 1, EDA event 2 and the EDA event to be delivered are packaged together and sent to the target subscriber. The preset content of the EDA event to be delivered can be a parameter or identifier in the EDA event. When it is detected that the EDA event to be delivered contains this parameter or identifier, it is determined that the content of the EDA event to be delivered contains the preset content.

[0110] In order to maintain the real-time nature of events, a preset time may be set. When the time for forming the set corresponding to the target subscriber exceeds the preset time, the EDA events in the set corresponding to the target subscriber are packaged and sent to the target subscriber.

[0111] When the memory capacity of the publisher is not high, it may cause device freeze. To avoid this situation, the embodiment of the present invention proposes that when the memory capacity is greater than the preset capacity, the EDA events in the set corresponding to the target subscriber are packaged together and sent to the target subscriber.

[0112] Of course, the above preset conditions provided in the embodiment of the present invention can be used in combination or individually, and the present invention does not impose any specific limitation on this.

[0113] Based on the technical solution provided by the above embodiment of the present invention, combined with Figure 6 As shown, an embodiment of the present invention provides an EDA event delivery system, including a publisher 600, an event router 601, a subscriber 1, a subscriber 2, ..., a subscriber N.

[0114] The publisher 600 is used to obtain the EDA event to be delivered; if the contract sending mode of the EDA event to be delivered is the first preset mode, and the number of subscribers corresponding to the EDA event to be delivered is greater than 1, the number of EDA events to be delivered is copied to the same number as the number of subscribers corresponding to the EDA event to be delivered. When the subscribers corresponding to the EDA event to be delivered include non-target subscribers, the EDA event to be delivered is directly sent to the event routing 601 for each non-target subscriber; when the subscribers corresponding to the EDA event to be delivered include target subscribers, for each target subscriber, if the contract information of the EDA event to be delivered meets the trigger condition corresponding to the target subscriber, the EDA event to be delivered is added to the set corresponding to the target subscriber. When the EDA event in the set corresponding to the target subscriber meets the first preset condition, the EDA event in the set corresponding to the target subscriber is packaged together and sent to the event routing 601.

[0115] For example, the non-target subscribers corresponding to the EDA event to be delivered are subscriber 1 and subscriber 2; and the target subscriber corresponding to the EDA event to be delivered is subscriber N.

[0116] Event routing 601 is used to send the EDA events to be delivered to subscribers 1 and 2; and to send the EDA events packaged in the set corresponding to the target subscriber to subscriber N.

[0117] The list of subscribers to whom the EDA event to be delivered is sent is synchronized by the publisher to the event routing, so that the event routing can send the EDA event to be delivered to different subscribers based on the subscriber list.

[0118] The publisher 600 may also perform event configuration and event contract signing, and generate trigger conditions corresponding to the target subscriber based on the event configuration table and the event contract signing table.

[0119] Based on the same inventive concept, the present application embodiment provides a transmission device for EDA events, please refer to Figure 7 As shown, the device comprises:

[0120] An acquisition module 700 is used to acquire EDA events to be delivered;

[0121] The first processing module 701 is configured to, if the contracted sending mode of the EDA event to be delivered is the first preset mode, directly send the EDA event to be delivered to each non-target subscriber when the subscribers corresponding to the EDA event to be delivered include non-target subscribers;

[0122] The second processing module 702 is used for, when the subscribers corresponding to the EDA event to be delivered include the target subscriber, for each target subscriber, if the contract information of the EDA event to be delivered meets the trigger condition corresponding to the target subscriber, adding the EDA event to be delivered to the collection corresponding to the target subscriber; when the EDA event in the collection corresponding to the target subscriber meets the first preset condition, packaging the EDA events in the collection corresponding to the target subscriber together and sending them to the target subscriber.

[0123] Optionally, the first processing module 701 is specifically configured to copy the number of the EDA events to be delivered to the same number of subscribers as the number of subscribers corresponding to the EDA events to be delivered if the number of subscribers corresponding to the EDA events to be delivered is greater than one.

[0124] Optionally, the device further includes a third processing module;

[0125] The third processing module is configured to stop sending the EDA event to be delivered to a subscriber corresponding to the EDA event to be delivered if the contracted sending mode of the EDA event to be delivered is the second preset mode.

[0126] Optionally, the determining module is specifically configured to select a preset mode from a plurality of preset modes according to the event type of the EDA event to be transmitted, and use the selected preset mode as the signing and sending mode of the EDA event to be transmitted; or

[0127] When the second preset condition is met, a selection interface is displayed; wherein the content of the selection interface includes multiple preset modes; and in response to the user's selection instruction, the preset mode selected in the selection instruction is used as the signing and sending mode of the EDA event to be transmitted.

[0128] Optionally, the second processing module is further used to:

[0129] When the third preset condition is met, an event configuration table and an event contract table are displayed; wherein the event configuration table includes multiple content types of the target subscriber; and the event contract table includes a threshold value corresponding to each content type of the target subscriber;

[0130] In response to an input instruction from a user, a trigger condition corresponding to the target subscriber is determined according to the content type input in the input instruction and a threshold value corresponding to the input content type.

[0131] Optionally, the first preset condition includes part or all of the following:

[0132] The cumulative number of EDA events in the set corresponding to the target subscriber reaches a preset number;

[0133] The cumulative size of EDA events in the set corresponding to the target subscriber exceeds a preset size;

[0134] The content of the EDA event to be delivered in the collection corresponding to the target subscriber includes preset content;

[0135] The time for forming the set corresponding to the target subscriber exceeds the preset time;

[0136] The memory capacity is larger than the preset capacity.

[0137] It should be noted that it should be understood that the division of the various modules of the above device is only a division of logical functions. In actual implementation, they can be fully or partially integrated into one physical entity, or they can be physically separated. And these modules can all be implemented in the form of software calling through processing elements; they can also be all implemented in the form of hardware; some modules can also be implemented in the form of software called by processing elements, and some modules can be implemented in the form of hardware. The processing element here can be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each module above can be completed by an integrated logic circuit of hardware in the processor element or instructions in the form of software.

[0138] Based on the same inventive concept, an embodiment of the present application provides an electronic device, Figure 8 A schematic diagram of the structure of an electronic device provided by some embodiments is shown. Figure 8 As shown, the electronic device includes: a processor 810, a memory 820, a communication interface 830 and a communication bus 840, wherein the processor 810, the communication interface 830, and the memory 820 communicate with each other through the communication bus 840;

[0139] The memory 820 stores a computer program, and when the program is executed by the processor 810, the processor 810 executes any one of the data analysis report construction methods.

[0140] The above-mentioned processor 810 can be a general-purpose processor, including a central processing unit CPU, a network processor (NP), etc.; it can also be a digital signal processor DSP, an application-specific integrated circuit ASIC, a field programmable gate array FPGA or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.

[0141] The memory 820 is connected to the processor 810 via the system bus 840 to complete the communication between them. The memory 820 is used to store computer program instructions.

[0142] The system bus 840 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The system bus 840 may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus. The transceiver is used to realize communication between the database access device and other computers (such as clients, read-write libraries, and read-only libraries). The memory may include random access memory (RAM) and may also include non-volatile memory.

[0143] Based on the same inventive concept, an embodiment of the present application provides a computer-readable storage medium, and a computer program product includes: a computer program code, when the computer program code is executed on a computer, the computer executes any one of the EDA event transmission methods.

[0144] Based on the same inventive concept, the embodiment of the present application also provides a computer program product, which includes: computer program code, when the computer program code is run on a computer, the computer executes any of the EDA event delivery methods discussed above. Since the principle of solving the problem by the above computer program product is similar to the data analysis report construction method, the implementation of the above computer program product can refer to the implementation of the method, and the repeated parts will not be repeated.

[0145] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.

[0146] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0147] These computer program instructions may also be stored in a computer readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0148] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of user-operated steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable device to implement the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0149] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. A method for delivering an EDA event, characterized in that: include: Get the EDA event to be delivered; If the contracted sending mode of the EDA event to be delivered is the first preset mode, when the subscribers corresponding to the EDA event to be delivered include non-target subscribers, for each non-target subscriber, the EDA event to be delivered is directly sent to the non-target subscriber; When the subscribers corresponding to the EDA event to be delivered include the target subscriber, for each target subscriber, if the contract information of the EDA event to be delivered meets the trigger condition corresponding to the target subscriber, the EDA event to be delivered is added to the collection corresponding to the target subscriber; when the EDA event in the collection corresponding to the target subscriber meets the first preset condition, the EDA events in the collection corresponding to the target subscriber are packaged together and sent to the target subscriber.

2. The method for transmitting an EDA event according to claim 1, characterized in that: Before directly sending the to-be-delivered EDA event to each non-target subscriber, the method further includes: If the number of subscribers corresponding to the EDA event to be delivered is greater than 1, the number of the EDA events to be delivered is copied to the same number as the number of subscribers corresponding to the EDA event to be delivered.

3. The method for transmitting an EDA event according to claim 2, characterized in that: After obtaining the EDA event to be transmitted, the method further includes: If the contracted sending mode of the EDA event to be delivered is the second preset mode, stopping sending the EDA event to be delivered to the subscriber corresponding to the EDA event to be delivered.

4. The method for transmitting an EDA event according to claim 2, characterized in that: The signing and sending mode of the EDA event to be delivered is determined by: According to the event type of the EDA event to be delivered, selecting a preset mode from a plurality of preset modes, and using the selected preset mode as the signing and sending mode of the EDA event to be delivered; or When the second preset condition is met, a selection interface is displayed; wherein the content of the selection interface includes multiple preset modes; and in response to the user's selection instruction, the preset mode selected in the selection instruction is used as the signing and sending mode of the EDA event to be transmitted.

5. The method for transmitting EDA events according to claim 1, characterized in that: Determine the trigger conditions corresponding to the target subscriber in the following ways: When the third preset condition is met, an event configuration table and an event contract table are displayed; wherein the event configuration table includes multiple content types of the target subscriber; and the event contract table includes a threshold value corresponding to each content type of the target subscriber; In response to an input instruction from a user, a trigger condition corresponding to the target subscriber is determined according to the content type input in the input instruction and a threshold value corresponding to the input content type.

6. The method for transmitting an EDA event according to any one of claims 1 to 5, characterized in that: The first preset condition includes part or all of the following: The cumulative number of EDA events in the set corresponding to the target subscriber reaches a preset number; The cumulative size of EDA events in the set corresponding to the target subscriber exceeds a preset size; The content of the EDA event to be delivered in the collection corresponding to the target subscriber includes preset content; The time for forming the set corresponding to the target subscriber exceeds the preset time; The memory capacity is larger than the preset capacity.

7. A device for transmitting an EDA event, characterized in that: include: An acquisition module is used to acquire EDA events to be delivered; A first processing module, configured to, if the contracted sending mode of the EDA event to be delivered is the first preset mode, directly send the EDA event to be delivered to each non-target subscriber when the subscribers corresponding to the EDA event to be delivered include non-target subscribers; The second processing module is used to, when the subscribers corresponding to the EDA event to be delivered include the target subscriber, for each target subscriber, if the contract information of the EDA event to be delivered meets the trigger condition corresponding to the target subscriber, add the EDA event to be delivered to the collection corresponding to the target subscriber; when the EDA event in the collection corresponding to the target subscriber meets the first preset condition, package the EDA events in the collection corresponding to the target subscriber together and send them to the target subscriber.

8. The EDA event transmission device according to claim 7, characterized in that: The first processing module is specifically configured to copy the number of the EDA events to be delivered to the same number as the number of subscribers corresponding to the EDA events to be delivered if the number of subscribers corresponding to the EDA events to be delivered is greater than one.

9. The EDA event transmission device according to claim 8, characterized in that: The device also includes a third processing module; The third processing module is configured to stop sending the EDA event to be delivered to a subscriber corresponding to the EDA event to be delivered if the contracted sending mode of the EDA event to be delivered is the second preset mode.

10. The EDA event transmission device according to claim 8, characterized in that: The determining module is specifically configured to select a preset mode from a plurality of preset modes according to the event type of the EDA event to be transmitted, and use the selected preset mode as the signing and sending mode of the EDA event to be transmitted; or When the second preset condition is met, a selection interface is displayed; wherein the content of the selection interface includes multiple preset modes; and in response to the user's selection instruction, the preset mode selected in the selection instruction is used as the signing and sending mode of the EDA event to be transmitted.

11. The EDA event transmission device according to claim 7, characterized in that: The second processing module is further used for: When the third preset condition is met, an event configuration table and an event contract table are displayed; wherein the event configuration table includes multiple content types of the target subscriber; and the event contract table includes a threshold value corresponding to each content type of the target subscriber; In response to an input instruction from a user, a trigger condition corresponding to the target subscriber is determined according to the content type input in the input instruction and a threshold value corresponding to the input content type.

12. The EDA event transmission device according to any one of claims 7 to 11, characterized in that: The first preset condition includes part or all of the following: The cumulative number of EDA events in the set corresponding to the target subscriber reaches a preset number; The cumulative size of EDA events in the set corresponding to the target subscriber exceeds a preset size; The content of the EDA event to be delivered in the collection corresponding to the target subscriber includes preset content; The time for forming the set corresponding to the target subscriber exceeds the preset time; The memory capacity is larger than the preset capacity.

13. An electronic device, characterized in that: include: A memory for storing program instructions; A processor is used to call the program instructions stored in the memory, and execute the steps included in any one of claims 1-6 according to the obtained program instructions.

14. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, wherein the computer program includes program instructions, and when the program instructions are executed by a computer, the computer executes the method according to any one of claims 1 to 6.

15. A computer program product, characterized in that The computer program product comprises: a computer program code, and when the computer program code is run on a computer, the computer is enabled to execute the method according to any one of claims 1 to 6.

Images