Message fuse method and device, computer device and storage medium

Abstract

The application relates to a message fusing method and device, computer equipment and a storage medium, which can be used in the financial field in artificial intelligence technology and can also be used in any field except the financial field. The method comprises the following steps: acquiring a message type, a sending time and a user end for receiving a to-be-sent message of the to-be-sent message; acquiring an interface response duration of a server corresponding to a sending interface; the sending interface is used for sending the to-be-sent message; acquiring historical access data generated by a user end corresponding to a historical message; determining whether the to-be-sent message needs to be fused according to the interface response duration, the historical access data, the message type and the sending time of the to-be-sent message; and if yes, fusing the to-be-sent message. The method can prevent the problem of server downtime caused by the accumulation of to-be-sent messages.

Description

TECHNICAL FIELD

[0001] The present application can be used in the field of finance in artificial intelligence technology, and can also be used in any field other than the field of finance. The application field of the present application is not limited. BACKGROUND

[0002] With the rise of user terminals in mobile phones, various types of messages will be pushed to users by user terminals for users to check.

[0003] In the traditional technology, the server corresponding to the user terminal will send the message as a to-be-sent message to each user terminal through an interface after determining the message provided for the user. Although this method can complete the sending of the to-be-sent message, when the number of user terminals is large and the to-be-sent message is large, there will be a problem of server downtime due to a large number of to-be-sent messages. SUMMARY

[0004] Therefore, it is necessary to provide a message fusing method, device, computer equipment and storage medium capable of avoiding server downtime in view of the above technical problems.

[0005] In a first aspect, the present application provides a message fusing method, comprising:

[0006] obtaining the message type, sending time and user terminal for receiving the to-be-sent message of the to-be-sent message;

[0007] obtaining the interface response time of the server corresponding sending interface; the sending interface is used for sending the to-be-sent message;

[0008] obtaining the historical access data generated by the user access history message corresponding to the user terminal;

[0009] determining whether the to-be-sent message needs to be fused according to the interface response time, the historical access data, the message type and the sending time of the to-be-sent message;

[0010] if yes, fusing the to-be-sent message.

[0011] In one embodiment, determining whether the to-be-sent message needs to be fused according to the interface response time, the historical access data, the message type and the sending time of the to-be-sent message, comprises:

[0012] determining whether the to-be-sent message is allowed to be fused according to the interface response time and the preset response time threshold;

[0013] if yes, determining whether the to-be-sent message needs to be fused according to the historical access data of the user corresponding to the user terminal, the message type and the sending time of the to-be-sent message.

[0014] In one embodiment, the historical access data includes: a message type of the historical message; and the method further includes:

[0015] determining whether the message type of the historical message corresponding to the user terminal is consistent with the message type of the to-be-sent message;

[0016] In the case where the message type of the historical message is inconsistent with the message type of the to-be-sent message, it is determined that the to-be-sent message needs to be subjected to the fuse processing.

[0017] In one embodiment, the historical access data includes: historical access time information of the historical message; and the method further includes:

[0018] In the case where the message type of the historical message is consistent with the message type of the to-be-sent message, it is determined, according to the historical access time information of the historical message, whether the to-be-sent message needs to be subjected to the fuse processing.

[0019] In one embodiment, the historical access time information includes: a historical access time period of the historical message; and the method further includes:

[0020] determining whether the sending time of the to-be-sent message is in the historical access time period of the historical message;

[0021] In the case where the sending time is not in the historical access time period, it is determined that the to-be-sent message needs to be subjected to the fuse processing.

[0022] In one embodiment, the historical access time information includes: a historical access time length of the historical message; and the method further includes:

[0023] In the case where the historical access time length of the historical message does not satisfy a preset access time length threshold, it is determined that the to-be-sent message needs to be subjected to the fuse processing.

[0024] In a second aspect, the present application further provides a message fuse processing device, which includes:

[0025] a message data acquisition module, configured to acquire a message type, a sending time of a to-be-sent message, and a user terminal for receiving the to-be-sent message;

[0026] a response time length acquisition module, configured to acquire an interface response time length of a sending interface corresponding to a server; the sending interface is configured to send the to-be-sent message;

[0027] a historical data acquisition module, configured to acquire historical access data generated by a user terminal corresponding to a user accessing a historical message;

[0028] The message fuse judgment module is configured to determine whether the to-be-sent message needs to be subjected to the fuse processing according to the interface response duration, the historical access data, the message type of the to-be-sent message, and the sending time.

[0029] The message fuse processing module is configured to, if yes, subject the to-be-sent message to the fuse processing.

[0030] In a third aspect, the present application further provides a computer device, comprising a memory and a processor, the memory stores a computer program, and the processor implements the following steps when executing the computer program:

[0031] obtaining a message type, a sending time of a to-be-sent message, and a user terminal for receiving the to-be-sent message;

[0032] obtaining an interface response duration of a sending interface corresponding to the server; the sending interface is used for sending the to-be-sent message;

[0033] obtaining historical access data generated by a user terminal corresponding to user access historical messages;

[0034] determining whether the to-be-sent message needs to be subjected to the fuse processing according to the interface response duration, the historical access data, the message type of the to-be-sent message, and the sending time;

[0035] if yes, subjecting the to-be-sent message to the fuse processing.

[0036] In a fourth aspect, the present application further provides a computer readable storage medium, which stores a computer program, and the computer program implements the following steps when executed by a processor:

[0037] obtaining a message type, a sending time of a to-be-sent message, and a user terminal for receiving the to-be-sent message;

[0038] obtaining an interface response duration of a sending interface corresponding to the server; the sending interface is used for sending the to-be-sent message;

[0039] obtaining historical access data generated by a user terminal corresponding to user access historical messages;

[0040] determining whether the to-be-sent message needs to be subjected to the fuse processing according to the interface response duration, the historical access data, the message type of the to-be-sent message, and the sending time;

[0041] if yes, subjecting the to-be-sent message to the fuse processing.

[0042] In a fifth aspect, the present application further provides a computer program product, comprising a computer program, and the computer program implements the following steps when executed by a processor:

[0043] acquire a message type, a sending time of the to-be-sent message, and a user terminal used for receiving the to-be-sent message;

[0044] acquire an interface response duration of a sending interface corresponding to the server, the sending interface being used for sending the to-be-sent message;

[0045] acquire historical access data generated by a user terminal corresponding to a user access historical message;

[0046] determine, according to the interface response duration, the historical access data, the message type of the to-be-sent message, and the sending time, whether the to-be-sent message needs to be subjected to a fuse processing;

[0047] if yes, subject the to-be-sent message to the fuse processing.

[0048] The message fuse processing method, device, computer device, and storage medium acquire a message type, a sending time of the to-be-sent message, and a user terminal used for receiving the to-be-sent message; acquire an interface response duration of a sending interface corresponding to the server, the sending interface being used for sending the to-be-sent message; acquire historical access data generated by a user terminal corresponding to a user access historical message; and determine, according to the interface response duration, the historical access data, the message type of the to-be-sent message, and the sending time, whether the to-be-sent message needs to be subjected to a fuse processing; if yes, subject the to-be-sent message to the fuse processing. The application determines, according to the access habit (i.e., the historical access data) of the user terminal and the pressure condition (i.e., the interface response duration) of the server, whether the to-be-sent message needs to be subjected to the fuse processing, thereby preventing the problem of server downtime caused by accumulation of the to-be-sent message. BRIEF DESCRIPTION OF DRAWINGS

[0049] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the related art, the following will briefly introduce the drawings needed to be used in the embodiments or the related art description. Obviously, the drawings in the following description only some embodiments of the present application, and for those skilled in the art, other drawings can also be obtained without creative labor on the basis of these drawings.

[0050] Figure 1 An application environment diagram of a message fuse processing method provided by the present embodiment;

[0051] Figure 2 A flowchart of a first message fuse processing method provided by the present embodiment;

[0052] Figure 3 A flowchart of a second message fuse processing method provided by the present embodiment;

[0053] Figure 4 A structural block diagram of a message fuse processing device provided by the present embodiment;

[0054] Figure 5 An internal structure diagram of a computer device is provided for this embodiment.

[0055] Figure 6 An internal structure diagram of a computer device is provided for this embodiment. DETAILED DESCRIPTION

[0056] In order to make the purposes, technical solutions and advantages of the present application clearer, the present application is further described in detail below in combination with the drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and not to limit the present application.

[0057] The message fusing method provided by the embodiments of the present application can be applied to an application environment as shown in Figure 1 . The user end 102 communicates with the server 104 through a network. The server 104 includes a database and a message source system. When the server has a to-be-sent message to be sent to the user end, it determines whether to perform fusing processing on the to-be-sent message in the sending source system according to the interface response time length, historical access data, message type and sending time of the to-be-sent message stored in the database. Specifically, the server 104 acquires the message type, sending time and user end for receiving the to-be-sent message of the to-be-sent message; acquires the interface response time length of the sending interface corresponding to the server; the sending interface is used to send the to-be-sent message; acquires the historical access data generated by the user access history message corresponding to the user end; determines whether the to-be-sent message needs to be fused according to the interface response time length, historical access data, message type and sending time of the to-be-sent message; if yes, the to-be-sent message is fused. The user end 102 can be, but is not limited to, various personal computers, notebook computers, smart phones, tablet computers, Internet of Things devices and portable wearable devices. The Internet of Things device can be a smart speaker, a smart television, a smart air conditioner, a smart vehicle device, etc. The portable wearable device can be a smart watch, a smart bracelet, a head-mounted device, etc. The server 104 can be implemented by an independent server or a server cluster composed of multiple servers.

[0058] In an exemplary embodiment, as shown in Figure 2 , a message fusing method is provided. Taking the server 104 in Figure 1 as an example, the method includes the following steps 201 to 205. Wherein:

[0059] Step 201, acquiring the message type, sending time and user end for receiving the to-be-sent message of the to-be-sent message.

[0060] The to-be-sent message can be a push message to be sent to the user terminal, and can include an article, an audio / video, etc. The message type can be a type of message content of the to-be-sent message, such as a science and technology type, a finance type, etc. The sending time can be a time of sending the to-be-sent message.

[0061] Specifically, the server obtains the to-be-sent message, and parses the to-be-sent message to obtain the message type, the sending time, and the user terminal for receiving the to-be-sent message.

[0062] In step 202, an interface response duration of a sending interface corresponding to the server is obtained.

[0063] The sending interface is used to send the to-be-sent message. The interface response duration can be a response time when the sending interface sends a message to the outside.

[0064] Specifically, the server obtains the interface response duration of the sending interface corresponding to the server.

[0065] In step 203, historical access data generated by a user terminal corresponding to a user accessing a historical message is obtained.

[0066] The historical message can be a historical message sent by the server. The historical access data can be message data of the historical message viewed by the user.

[0067] Specifically, the server obtains the historical access data generated by the user terminal corresponding to the user accessing the historical message.

[0068] In step 204, whether the to-be-sent message needs to be subjected to a fuse processing is determined according to the interface response duration, the historical access data, the message type of the to-be-sent message, and the sending time.

[0069] The fuse processing can be a processing of discarding the to-be-sent message.

[0070] Specifically, when it is determined that the interface response duration exceeds a preset duration threshold, whether the to-be-sent message needs to be subjected to the fuse processing is determined according to the historical access data, the message type of the to-be-sent message, and the sending time.

[0071] In step 205, if yes, the to-be-sent message is subjected to the fuse processing.

[0072] Specifically, the server deletes and discards the to-be-sent message sent to the user terminal.

[0073] The message fusing method, device, computer device and storage medium, obtain a message type, a sending time of a to-be-sent message and a user terminal used for receiving the to-be-sent message; obtain an interface response duration of a server corresponding to a sending interface; the sending interface is used for sending the to-be-sent message; obtain historical access data generated by a user terminal corresponding to a historical message; determine whether the to-be-sent message needs to be fused according to the interface response duration, the historical access data, the message type and the sending time of the to-be-sent message; if yes, the to-be-sent message is fused. The application determines whether the to-be-sent message needs to be fused according to the access habit (that is, the historical access data) of the user terminal and the pressure condition (that is, the interface response duration) of the server, thereby preventing the problem of server downtime caused by the backlog of the to-be-sent message.

[0074] In some embodiments, determining whether the to-be-sent message needs to be fused according to the interface response duration, the historical access data, the message type and the sending time of the to-be-sent message comprises: determining whether the to-be-sent message is allowed to be fused according to the interface response duration and a preset response duration threshold; if yes, determining whether the to-be-sent message needs to be fused according to the historical access data of the user terminal corresponding to a user, the message type and the sending time of the to-be-sent message.

[0075] Specifically, the server determines the size relationship between the interface response duration and the preset response duration threshold; if it is determined that the interface response duration is not greater than the preset response duration threshold, the to-be-sent message does not need to be fused; if it is determined that the interface response duration is greater than the preset response duration threshold, the to-be-sent message is allowed to be fused, and further, whether the to-be-sent message needs to be fused is determined according to the historical access data of the user terminal corresponding to a user, the message type and the sending time of the to-be-sent message.

[0076] The embodiment determines whether the to-be-sent message needs to be fused by determining the size relationship between the interface response duration and the preset response duration threshold, thereby further avoiding the problem of server downtime.

[0077] In some embodiments, the historical access data comprises: a message type of a historical message; determining whether the to-be-sent message needs to be fused according to the historical access data of the user terminal corresponding to a user, the message type and the sending time of the to-be-sent message comprises:

[0078] determining whether the message type of the historical message corresponding to the user terminal is consistent with the message type of the to-be-sent message;

[0079] In the case that the message type of the historical message is not consistent with the message type of the to-be-sent message, it is determined that the to-be-sent message needs to be fused.

[0080] Specifically, it is determined whether the message type of the historical message corresponding to the user end is consistent with the message type of the to-be-sent message. If not, it is determined that the to-be-sent message needs to be handled by the fusing. If yes, it is further determined whether the to-be-sent message needs to be handled by the fusing according to the historical access time information of the historical message.

[0081] In some embodiments, the historical access time information includes historical access time periods of the historical message, and the method further includes: in the case where the message type of the historical message is consistent with the message type of the to-be-sent message, determining whether the to-be-sent message needs to be handled by the fusing according to the historical access time information of the historical message.

[0082] The embodiment further determines whether the message type of the historical message is consistent with the message type of the to-be-sent message, and then determines whether the to-be-sent message needs to be handled by the fusing, thereby further avoiding the problem of server downtime.

[0083] In some embodiments, the historical access time information includes historical access time periods of the historical message, and the method further includes: determining whether the sending time of the to-be-sent message is in the historical access time period of the historical message, and in the case where the sending time is not in the historical access time period, determining that the to-be-sent message needs to be handled by the fusing.

[0084] Specifically, it is determined whether the sending time of the to-be-sent message is in the historical access time period of the historical message. If yes, it is further determined whether the to-be-sent message needs to be handled by the fusing according to the historical access time period. If not, it is determined that the to-be-sent message needs to be handled by the fusing.

[0085] The embodiment further determines whether the sending time is in the historical access time period of the historical message, and then determines whether the to-be-sent message needs to be handled by the fusing, thereby further avoiding the problem of server downtime.

[0086] In some embodiments, the historical access time information includes historical access time periods of the historical message, and the method further includes: in the case where the historical access time period of the historical message does not satisfy a preset access time period threshold, determining that the to-be-sent message needs to be handled by the fusing.

[0087] Specifically, the server determines whether the historical access time period of the historical message satisfies a preset access time period threshold. In the case where the historical access time period does not satisfy the preset access time period threshold, it is determined that the to-be-sent message needs to be handled by the fusing. If yes, it is proved that the user of the user end has a probability of inquiring the to-be-sent message, and the to-be-sent message does not need to be handled by the fusing.

[0088] In this embodiment, whether the historical access duration meets the preset access duration threshold is further determined, and then it is determined whether the to-be-sent message needs to be subjected to the fuse processing, thereby further avoiding the problem of server downtime.

[0089] In one embodiment, an optional method of message fuse is given in this embodiment, and the method is described by taking a server as an example. As shown in Figure 3 the method comprises the following steps:

[0090] In step 301, the message type, sending time of the to-be-sent message, and the user terminal for receiving the to-be-sent message are obtained.

[0091] In step 302, the interface response duration of the server corresponding to the sending interface is obtained.

[0092] In step 303, the historical access data of the user terminal corresponding to the historical message is obtained.

[0093] In step 304, whether the to-be-sent message is allowed to be subjected to the fuse processing is determined according to the interface response duration and the preset response duration threshold. If yes, step 305 is executed, and if no, step 308 is executed.

[0094] In step 305, whether the message type of the historical message corresponding to the user terminal is consistent with the message type of the to-be-sent message is determined. If yes, step 306 is executed, and if no, step 309 is executed.

[0095] In step 306, whether the sending time of the to-be-sent message is in the historical access period of the historical message is determined. If yes, step 307 is executed, and if no, step 309 is executed.

[0096] In step 307, whether the historical access duration of the historical message meets the preset access duration threshold is determined. If yes, step 308 is executed, and if no, step 309 is executed.

[0097] In step 308, the to-be-sent message is sent to the user terminal.

[0098] In step 309, the to-be-sent message is subjected to the fuse processing.

[0099] It should be understood that although each step in the flowchart involved in the embodiments described above is shown in sequence according to the arrow, these steps are not necessarily executed in the order indicated by the arrow. Unless otherwise specified herein, the execution of these steps is not strictly limited in sequence, and these steps can be executed in other orders. Moreover, at least some of the steps in the flowchart involved in the embodiments described above can include multiple steps or multiple stages, which are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily sequential, but can be alternately or alternately executed with at least part of other steps or steps or stages in other steps.

[0100] Based on the same inventive concept, the embodiments of the present application also provide a message fusing device for implementing the message fusing method described above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme described in the above method, so the specific limitations in one or more message fusing device embodiments provided below can refer to the limitations of the message fusing method described above, which will not be repeated here.

[0101] In an exemplary embodiment, as shown in Figure 4 A message fusing device is provided, comprising: a message data acquisition module 10, a response time acquisition module 11, a historical data acquisition module 12, a message fusing judgment module 13 and a message fusing processing module 14, wherein:

[0102] The message data acquisition module 10 is configured to acquire the message type, sending time of the to-be-sent message and the user terminal for receiving the to-be-sent message;

[0103] The response time acquisition module 11 is configured to acquire the interface response time of the server corresponding to the sending interface; the sending interface is configured to send the to-be-sent message;

[0104] The historical data acquisition module 12 is configured to acquire the historical access data generated by the user terminal corresponding to the user access historical message;

[0105] The message fusing judgment module 13 is configured to determine whether the to-be-sent message needs to be fused according to the interface response time, the historical access data, the message type and the sending time of the to-be-sent message;

[0106] The message fusing processing module 14 is configured to perform the fusing processing on the to-be-sent message if the determination result is yes.

[0107] In some embodiments, Figure 4The message fuse judgment module 13 in the message fuse device is further configured to determine whether the to-be-sent message is allowed to be subjected to the fuse processing according to the interface response time length and the preset response time length threshold; if yes, determine whether the to-be-sent message needs to be subjected to the fuse processing according to the historical access data of the user corresponding to the user end, the message type of the to-be-sent message and the sending time.

[0108] In some embodiments, Figure 4 The message fuse judgment module 13 in the message fuse device is further configured to determine whether the message type of the historical message corresponding to the user end is consistent with the message type of the to-be-sent message; and in the case that the message type of the historical message is not consistent with the message type of the to-be-sent message, determine that the to-be-sent message needs to be subjected to the fuse processing.

[0109] In some embodiments, Figure 4 The message fuse judgment module 13 in the message fuse device is further configured to, in the case that the message type of the historical message is consistent with the message type of the to-be-sent message, determine whether the to-be-sent message needs to be subjected to the fuse processing according to the historical access time information of the historical message.

[0110] In some embodiments, Figure 4 The message fuse judgment module 13 in the message fuse device is further configured to determine whether the sending time of the to-be-sent message is in the historical access time period of the historical message; and in the case that the sending time is not in the historical access time period, determine that the to-be-sent message needs to be subjected to the fuse processing.

[0111] In some embodiments, Figure 4 The message fuse judgment module 13 in the message fuse device is further configured to, in the case that the historical access time length of the historical message does not satisfy the preset access time length threshold, determine that the to-be-sent message needs to be subjected to the fuse processing.

[0112] The above modules in the message fuse device can be all or partially realized by software, hardware and combinations thereof. The above modules can be embedded in or independent of the processor in the computer device in hardware form, or can be stored in the memory in the computer device in software form, so as to be called and executed by the processor to perform the operations corresponding to the above modules.

[0113] In one exemplary embodiment, a computer device, which can be a server, is provided, and an internal structure diagram of the computer device can be as shown in Figure 5As shown in the figure. The computer device includes a processor, a memory, an input / output interface (I / O for short) and a communication interface. Among them, the processor, the memory and the input / output interface are connected through the system bus, and the communication interface is connected to the system bus through the input / output interface. Among them, the processor of the computer device is used to provide computing and control ability. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store interface response time, historical access data and to-be-sent messages and other data. The input / output interface of the computer device is used to exchange information between the processor and external devices. The communication interface of the computer device is used to communicate with external terminals through network connection. The computer program is executed by the processor to implement a message fusing method.

[0114] In an exemplary embodiment, a computer device, which can be a terminal, is provided, and an internal structure diagram thereof can be as shown in the figure. Figure 6 As shown in the figure. The computer device includes a processor, a memory, an input / output interface (I / O for short) and a communication interface. Among them, the processor, the memory and the input / output interface are connected through the system bus, and the communication interface is connected to the system bus through the input / output interface. Among them, the processor of the computer device is used to provide computing and control ability. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store interface response time, historical access data and to-be-sent messages and other data. The input / output interface of the computer device is used to exchange information between the processor and external devices. The communication interface of the computer device is used to communicate with external terminals through network connection. The computer program is executed by the processor to implement a message fusing method. The display unit of the computer device is used to form a visually visible picture, which can be a display screen, a projection device or a virtual reality imaging device. The display screen can be a liquid crystal display screen or an electronic ink display screen. The input device of the computer device can be a touch layer overlaid on the display screen, or can be a key, trackball or touchpad arranged on the shell of the computer device, or can be an external keyboard, touchpad or mouse, etc.

[0115] Those skilled in the art can understand that, Figure 5 and Figure 6The structure shown in the figure is only a block diagram of part of the structure related to the scheme of the present application, and does not constitute a limitation on the computer device to which the scheme of the present application is applied. The specific computer device can include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0116] In an embodiment, a computer device is also provided, including a memory and a processor, the memory storing a computer program, and the processor implementing the steps in the above method embodiments when executing the computer program.

[0117] In an embodiment, a computer readable storage medium is provided, storing a computer program, and the computer program implementing the steps in the above method embodiments when executed by a processor.

[0118] In an embodiment, a computer program product is provided, including a computer program, and the computer program implementing the steps in the above method embodiments when executed by a processor

[0119] It should be noted that the data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in the present application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of related data need to comply with relevant regulations.

[0120] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a non-volatile computer readable storage medium, and when the computer program is executed, the processes of the above-mentioned embodiments of the methods can be included. Any reference to memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical storage, high-density embedded non-volatile memory, resistive memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration but not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM), etc. The database involved in the embodiments provided in the present application can include at least one of a relational database and a non-relational database. The non-relational database can include a distributed database based on a block chain, etc., without being limited thereto. The processor involved in the embodiments provided in the present application can be a general-purpose processor, a central processing unit, a graphics processing unit, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, etc., without being limited thereto.

[0121] Any combination of the technical features of the above embodiments can be made. In order to make the description simple, all possible combinations of the technical features in the above embodiments are not described, however, as long as the combination of the technical features does not exist, it should be considered as the scope of the present application.

[0122] The above embodiments only express several implementation manners of the present application, and the description is more specific and detailed, but it should not be understood as a limitation on the scope of the patent of the present application. It should be pointed out that for ordinary skilled in the art, without departing from the concept of the present application, a number of modifications and improvements can be made, which are within the scope of protection of the present application. Therefore, the protection scope of the present application should be subject to the appended claims.

Claims

1. A message fuse method, characterized by, The method applied to a server comprises: acquiring a message type, a sending time of a to-be-sent message, and a user terminal for receiving the to-be-sent message; acquiring an interface response duration of a sending interface corresponding to the server; the sending interface is used for sending the to-be-sent message; acquiring historical access data generated by a user access history message corresponding to the user terminal; determining whether the to-be-sent message needs to be subjected to a fuse processing according to the interface response duration, the historical access data, the message type of the to-be-sent message, and the sending time; if yes, subjecting the to-be-sent message to the fuse processing.

2. The method of claim 1, wherein, The determining whether the to-be-sent message needs to be subjected to the fuse processing according to the interface response duration, the historical access data, the message type of the to-be-sent message, and the sending time comprises: determining whether the to-be-sent message is allowed to be subjected to the fuse processing according to the interface response duration and a preset response duration threshold value; if yes, determining whether the to-be-sent message needs to be subjected to the fuse processing according to the historical access data of the user corresponding to the user terminal, the message type of the to-be-sent message, and the sending time.

3. The method of claim 2, wherein, The historical access data comprises a message type of the historical message; the determining whether the to-be-sent message needs to be subjected to the fuse processing according to the historical access data of the user corresponding to the user terminal, the message type of the to-be-sent message, and the sending time comprises: determining whether the message type of the historical message corresponding to the user terminal is consistent with the message type of the to-be-sent message; in a case where the message type of the historical message is not consistent with the message type of the to-be-sent message, determining that the to-be-sent message needs to be subjected to the fuse processing.

4. The method of claim 3, wherein, The historical access data comprises historical access time information of the historical message; the method further comprises: in a case where the message type of the historical message is consistent with the message type of the to-be-sent message, determining whether the to-be-sent message needs to be subjected to the fuse processing according to the historical access time information of the historical message.

5. The method of claim 4, wherein, The historical access time information comprises a historical access time period of the historical message; the determining whether the to-be-sent message needs to be subjected to the fuse processing according to the historical access time information of the historical message comprises: determining whether the sending time of the to-be-sent message is in the historical access time period of the historical message; in a case where the sending time is not in the historical access time period, determining that the to-be-sent message needs to be subjected to the fuse processing.

6. The method of claim 5, wherein, The historical access time information comprises a historical access duration of the historical message; the method further comprises: in a case where the historical access duration of the historical message does not satisfy a preset access duration threshold value, determining that the to-be-sent message needs to be subjected to the fuse processing.

7. A message fuse device, characterized by The device comprises: a message data acquisition module, configured to acquire a message type, a sending time of a to-be-sent message, and a user terminal for receiving the to-be-sent message; a response duration acquisition module, configured to acquire an interface response duration of a sending interface corresponding to the server; the sending interface is used for sending the to-be-sent message; A historical data acquisition module is configured to acquire historical access data generated by a user access history message corresponding to the user terminal; A message fuse judgment module is configured to determine whether the to-be-sent message needs to be subjected to a fuse processing according to the interface response time length, the historical access data, the message type of the to-be-sent message, and the sending time; A message fuse processing module is configured to, if yes, subject the to-be-sent message to the fuse processing.

8. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that, The processor executes the computer program to implement the steps of the method in any one of claims 1 to 6.

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

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

Images