Message sending method and device, equipment and storage medium

By using delay queues in the Internet medical platform to manage the sending of the call prompt message, the problem of lag in the chat interface caused by multiple messages popping up simultaneously is solved, and the user experience and platform usage efficiency is improved.

CN118942737APending Publication Date: 2024-11-12BEIJING JINGDONG TUOXIAN TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411140482.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-19
Publication Date
2024-11-12

AI Technical Summary

Technical Problem

When receiving treatment on existing Internet medical platforms, the chat interface has caused the interface to display stutter due to multiple messages popping up at the same time.

Method used

Use a delay queue to temporarily store message identifiers and determine different delay times for each message identifier to ensure that messages are queued and sent in order to avoid multiple messages popping up at the same time.

Benefits of technology

It effectively avoids stuttering of the chat interface, improves the user experience, and improves the efficiency of using Internet medical platforms.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118942737A_ABST
    Figure CN118942737A_ABST
Patent Text Reader

Abstract

The embodiment of the invention discloses a message sending method and device, equipment and a storage medium, and relates to the technical field of computers, and the method can comprise the steps: receiving a reception instruction, generating each reception prompt message based on reception information carried by the reception instruction, and storing each reception prompt message into a predetermined database; adding the message identifier corresponding to each reception prompt message to a predetermined delay queue, and determining different delay time for each message identifier added to the delay queue; and for each message identifier in the delay queue, under the condition that the delay time of the current message identifier meets the dequeue condition of the delay queue, dequeue operation is performed on the current message identifier, a current reception prompt message corresponding to the current message identifier is acquired from the database, and the current reception prompt message is sent. By adopting the technical scheme provided by the embodiment of the invention, the situation of interface display lagging caused by the fact that a plurality of messages are popped up at the same time on the chat interface can be avoided.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Embodiments of the present invention relate to the field of Internet medical technology, and in particular, to a message sending method, device, equipment and storage medium. Background Art

[0002] At present, Internet medical platforms can provide patients with a variety of online medical services such as online consultation, electronic health record management, and remote consultation. Taking online consultation services as an example, Internet medical platforms can provide independent instant messaging (IM) channels for doctors and patients. Doctors can communicate with patients in the chat interface corresponding to the IM channel to realize online consultation.

[0003] However, in the process of implementing the present invention, it is found that there are at least the following problems in the prior art: In the prior art, whenever the Internet medical platform connects a new patient to the attending doctor, the platform will simultaneously generate multiple prompt messages (for example, prompts set by the attending doctor, the chief complaint information of the patient, etc.), and these multiple prompt messages will be sent through the corresponding IM channel at the same time. In this way, multiple messages will pop up on the chat interface between the attending doctor and the patient at the same time, and the interface display may freeze. Summary of the invention

[0004] The embodiments of the present invention provide a message sending method, apparatus, device and storage medium, which can avoid the situation where the interface display is stuck due to multiple messages popping up simultaneously on the chat interface.

[0005] In the first aspect, an embodiment of the present invention provides a message sending method, which may include: upon receiving a consultation instruction, generating each consultation prompt message based on the consultation information carried by the consultation instruction, and storing each consultation prompt message in a predetermined database; adding a message identifier corresponding to each consultation prompt message to a predetermined delay queue, and determining a different delay time for each message identifier added to the delay queue; for each message identifier in the delay queue, when the delay time of the current message identifier meets the dequeue condition of the delay queue, dequeueing the current message identifier, obtaining the current consultation prompt message corresponding to the current message identifier from the database, and sending the current consultation prompt message.

[0006] In a second aspect, an embodiment of the present invention further provides a message sending device, which may include: a message generating module, a queue adding module, and a message sending module;

[0007] Specifically, the message generation module is used to generate each reception prompt message based on the reception information carried by the reception instruction when a reception instruction is received, and store each reception prompt message in a predetermined database; the queue adding module is used to add the message identifier corresponding to each reception prompt message to a predetermined delay queue, and determine a different delay time for each message identifier added to the delay queue; the message sending module is used to dequeue the current message identifier for each message identifier in the delay queue when the delay time of the current message identifier meets the dequeue condition of the delay queue, and obtain the current reception prompt message corresponding to the current message identifier from the database, and send the current reception prompt message.

[0008] In a third aspect, an embodiment of the present invention provides a message sending device, the message sending device comprising:

[0009] one or more processors;

[0010] A memory for storing one or more programs;

[0011] When the one or more programs are executed by the one or more processors, the one or more processors implement the message sending method provided by any embodiment of the present invention.

[0012] In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements a message sending method as provided in any embodiment of the present invention.

[0013] In a fifth aspect, an embodiment of the present invention further provides a computer program product on which a computer program is stored, and when the program is executed by a processor, the message sending method provided by any embodiment of the present invention is implemented.

[0014] The embodiments of the above invention have the following advantages or beneficial effects:

[0015] In the technical solution provided by the embodiment of the present invention, whenever the Internet medical platform newly connects a patient to a certain doctor (i.e., when receiving a consultation instruction), each consultation reminder message can be generated based on the consultation information carried in the consultation instruction. Among them, each generated consultation reminder message has a different message identifier, and each consultation reminder message can be stored in a predetermined database based on the message identifier. Then, the message identifiers corresponding to each consultation reminder message can be added to a predetermined delay queue. In the process of adding each message identifier to the delay queue, a different delay time can be determined for each message identifier added to the delay queue. In the process of processing the delay queue, for each message identifier added to the delay queue, when the delay time of the current message identifier meets the dequeue condition of the delay queue, the current message identifier can be dequeued first, and then the current consultation reminder message corresponding to the current message identifier can be obtained from the database, and the current consultation reminder message can be sent. Since a delay queue is used to temporarily store each message identifier, and in the process of adding each message identifier to the delay queue, a different delay time is determined for each message identifier, so there is a certain time interval between the time when each message identifier exits the delay queue; and for each consultation reminder message, the current consultation reminder message is sent only when the current message identifier corresponding to the current consultation reminder message exits the delay queue, so for each consultation reminder message generated according to the same consultation information, there is a certain time interval between the message sending times of each consultation reminder message. It can be seen that in the technical solution provided by the embodiment of the present invention, by pre-creating a delay queue with the message identifier of the consultation reminder message as a queue element, the interval sending of multiple consultation reminder messages generated at the same time (i.e., each consultation reminder message generated according to the same consultation information) can be achieved. In this way, the chat interface of the attending doctor and the patient being treated will not pop up multiple messages at the same time, which can avoid the situation where the interface display is stuck due to the chat interface popping up multiple messages at the same time. In addition, the user experience of the Internet medical platform can be improved. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1 It is a flowchart of a message sending method provided by an embodiment of the present invention;

[0017] Figure 2 It is a flowchart of another message sending method provided by an embodiment of the present invention;

[0018] Figure 3 It is a simplified flow chart of matching candidate threads for a patient admission reminder message provided by an embodiment of the present invention;

[0019] Figure 4 It is a simplified flowchart of a message sending method provided by an embodiment of the present invention;

[0020] Figure 5 It is a structural schematic diagram of a message sending device provided by an embodiment of the present invention;

[0021] Figure 6 It is a structural diagram of a message sending device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0022] The present invention will be further described in detail below in conjunction with the accompanying drawings and embodiments. It is to be understood that the specific embodiments described herein are only used to explain the present invention, rather than to limit the present invention. It should also be noted that, for ease of description, only parts related to the present invention, rather than all structures, are shown in the accompanying drawings.

[0023] The term "and / or" in this article is merely a description of the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone.

[0024] In addition, the terms "including" and "having" and any variations thereof mentioned in the description of the embodiments of the present invention are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device including a series of steps or units is not limited to the listed steps or units, but may optionally include other steps or units that are not listed, or may optionally include other steps or units that are inherent to these processes, methods, products or devices.

[0025] It should be noted that, in the embodiments of the present invention, words such as "exemplary" or "for example" are used to indicate examples, illustrations or explanations. Any embodiment or design scheme described as "exemplary" or "for example" in the embodiments of the present invention should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a specific way.

[0026] In the description of the embodiments of the present invention, unless otherwise specified, “plurality” or “each” means two or more than two.

[0027] Figure 1 A flowchart of a message sending method provided in an embodiment of the present invention, which can be applied to an application scenario where an Internet medical platform provides online consultation services. The method can be executed by a message sending device provided in an embodiment of the present invention, which can be implemented in software and / or hardware and integrated in a message sending device.

[0028] The message sending method provided in the embodiment of the present invention can be applied to an Internet medical platform, which can provide an independent IM channel for the attending doctor and the patient, and the attending doctor can communicate with the patient in the chat interface corresponding to the IM channel. Correspondingly, the message sending device can be a server or server cluster of the Internet medical platform.

[0029] like Figure 1 As shown, the message sending method provided in the embodiment of the present invention specifically includes the following steps:

[0030] S110. When receiving a consultation instruction, generate each consultation prompt message based on the consultation information carried in the consultation instruction, and store each consultation prompt message in a predetermined database.

[0031] In a possible implementation, the patient can select a doctor or a department to be treated in the Internet medical platform, and enter the treatment information (the treatment information includes the main complaint information such as the symptom description entered by the patient, and also includes the user information of the patient to be treated). The Internet medical platform can respond to the selection operation and input operation of the patient to be treated, and match the patient to be treated with a doctor; afterwards, the Internet medical platform can create an IM channel for the doctor and the patient to be treated according to the user information of the matched doctor and the treatment information of the patient to be treated, and trigger the treatment instruction at the same time, which carries the user information of the doctor and the treatment information of the patient to be treated. Then, the Internet medical platform can generate various treatment prompt messages for the IM channel based on the treatment information. These treatment prompt messages need to be sent to the corresponding chat interface through the IM channel. After the patient and the doctor see these treatment prompt messages displayed in the chat interface, they know that the communication channel between the two has been established and can start online communication.

[0032] Exemplarily, each consultation prompt message may include a prompt message corresponding to the attending doctor, for example, the prompt message may be an access prompt voice or access prompt language set by the attending doctor. The Internet medical platform may determine the prompt message according to the user information of the attending doctor.

[0033] In another example, each consultation reminder message may also include a reminder message corresponding to the patient being consulted, for example, the reminder message may be the chief complaint information of the patient being consulted. The Internet medical platform may determine the chief complaint information from the consultation information of the patient being consulted, and determine the reminder message based on the chief complaint information.

[0034] It should be noted that in the embodiments of the present invention, the collection, collection, update, analysis, processing, use, transmission, storage and other aspects of the user personal information involved (such as the user information of the doctor who receives the patient and the medical information of the patient who receives the patient) are in compliance with the provisions of relevant laws and regulations, are used for legitimate purposes, and do not violate public order and good morals. Necessary measures are taken for user personal information to prevent illegal access to user personal information data and maintain the security of user personal information, network security and national security.

[0035] In an embodiment of the present invention, in the process of generating each consultation reminder message based on the consultation information carried by the consultation instruction, a different message identifier can be determined for each consultation reminder message. Exemplarily, the message identifier can be a digital number, and the Internet medical platform can determine a different digital number for each consultation reminder message based on a predetermined number generation rule.

[0036] After determining the message identifier for each consultation reminder message, for each consultation reminder message, the message identifier of the current consultation reminder message can be used as the keyword (key) and the content of the current consultation reminder message can be used as the key value (value) to store the current consultation reminder message in a predetermined remote dictionary service (Remote Dictionary Server, Redis) database.

[0037] S120: Add the message identifiers corresponding to the respective admission prompt messages to a predetermined delay queue, and determine a different delay time for each message identifier added to the delay queue.

[0038] In the embodiment of the present invention, a delay queue can be predetermined, and the queue element of the delay queue is a message identifier. In the delay queue, the order of dequeuing of the message identifier is not related to the order of enqueuing of the message identifier, but is related to the delay time of the message identifier. The earlier the delay time of the message identifier, the earlier the dequeuing order of the message identifier; conversely, the later the delay time of the message identifier, the later the dequeuing order of the message identifier.

[0039] After the Internet medical platform stores each consultation reminder message in a predetermined database, it can add the message identifier corresponding to each consultation reminder message to the delay queue. During the adding process, it is necessary to determine a different delay time for each message identifier. In one possible implementation, the time interval of the delay time corresponding to each message identifier can be determined as a predetermined time interval. Taking the predetermined time interval of 2 seconds as an example, if each consultation reminder message includes message A, message B, and message C, it can be determined that the delay time of message A is 2 seconds after the current moment, the delay time of message B is 4 seconds after the current moment, and the delay time of message C is 6 seconds after the current moment.

[0040] S130. For each message identifier in the delay queue, when the delay time of the current message identifier meets the dequeue condition of the delay queue, the current message identifier is dequeued, and the current consultation reminder message corresponding to the current message identifier is obtained from the database, and the current consultation reminder message is sent.

[0041] The delay time of the current message identifier satisfies the dequeue condition of the delay queue, that is, the current moment reaches the delay time of the current message identifier.

[0042] When the delay time of the current message identifier meets the dequeue condition of the delay queue, the current message identifier can be dequeued, that is, the current message identifier in the delay queue is deleted; after that, the current message identifier can be used as the key to search for the corresponding value in the Redis database, and the found value is the content of the current admission reminder message corresponding to the current message identifier.

[0043] In one possible implementation, after obtaining the current consultation reminder message corresponding to the current message identifier from the database, the Internet medical platform can push the current consultation reminder message to the chat interface corresponding to the IM channel created for the attending doctor and the patient, so that the attending doctor and the patient can see the current consultation reminder message in the chat interface.

[0044] Optionally, after obtaining the current consultation reminder message corresponding to the current message identifier from the database and sending the current consultation reminder message, the message sending method provided by the embodiment of the present invention further includes: deleting the current consultation reminder message stored in the database.

[0045] In the embodiment of the present invention, after the current patient consultation reminder message is sent, the current patient consultation reminder message stored in the database can be deleted. In this way, not only can storage resources be saved, but also the unsent patient consultation reminder messages can be managed easily.

[0046] Optionally, deleting the current reception reminder message stored in the database may include: after determining that the current reception reminder message is sent successfully, deleting the current reception reminder message stored in the database; in addition, adding the message identifiers corresponding to each reception reminder message to a predetermined delay queue, and determining a different delay time for each message identifier added to the delay queue, the message sending method provided by the embodiment of the present invention also includes: creating a verification task for each reception reminder message; and executing each verification task.

[0047] Among them, for each verification task, the task content of the current verification task includes: after a preset time, obtaining a consultation reminder message corresponding to the current verification task from the database; if it is determined that the consultation reminder message corresponding to the current verification task is successfully obtained from the database, the consultation reminder message corresponding to the current verification task is sent again. The preset time can be a predetermined time, for example, the preset time can be 1 minute.

[0048] After the Internet medical platform determines that the current consultation reminder message has been sent successfully, it can delete the current consultation reminder message stored in the database. That is, all the consultation reminder messages stored in the database are consultation reminder messages to be sent (including consultation reminder messages that have not been sent, and consultation reminder messages that have been sent but not successfully). Moreover, the Internet medical platform can create verification tasks for each reception prompt message while adding the message identifiers corresponding to each reception prompt message to the delay queue; for each verification task, the task content of the current verification task includes: after a preset time, obtaining the reception prompt message corresponding to the current verification task from the database; in the case where it is determined that the reception prompt message corresponding to the current verification task is not obtained from the database, it can be determined that the reception prompt message corresponding to the current verification task has been deleted from the database, that is, it can be determined that the reception prompt message corresponding to the current verification task has been successfully sent; on the contrary, in the case where it is determined that the reception prompt message corresponding to the current verification task is successfully obtained from the database, it can be determined that the reception prompt message corresponding to the current verification task has not been deleted from the database, that is, it can be determined that the reception prompt message corresponding to the current verification task has not been successfully sent, and at this time, the reception prompt message corresponding to the current verification task can be sent again. It can be seen that in an embodiment of the present invention, a set of compensation sending logic for reception prompt messages is provided, and the compensation sending logic can send the reception prompt message that failed to be sent due to network abnormalities and other reasons for a second time. In this way, the reliability of sending each admission reminder message at intervals can be improved, ensuring that each admission reminder message is not lost.

[0049] In the message sending method provided by the embodiment of the present invention, whenever the Internet medical platform newly connects a patient to a certain doctor (i.e., when receiving a consultation instruction), each consultation reminder message can be generated based on the consultation information carried in the consultation instruction. Among them, each generated consultation reminder message has a different message identifier, and each consultation reminder message can be stored in a predetermined database based on the message identifier. Then, the message identifiers corresponding to each consultation reminder message can be added to a predetermined delay queue. In the process of adding each message identifier to the delay queue, a different delay time can be determined for each message identifier added to the delay queue. In the process of processing the delay queue, for each message identifier added to the delay queue, when the delay time of the current message identifier meets the dequeue condition of the delay queue, the current message identifier can be dequeued first, and then the current consultation reminder message corresponding to the current message identifier can be obtained from the database, and the current consultation reminder message can be sent. Since a delay queue is used to temporarily store each message identifier, and in the process of adding each message identifier to the delay queue, a different delay time is determined for each message identifier, so there is a certain time interval between the time when each message identifier exits the delay queue; and for each consultation reminder message, the current consultation reminder message is sent only when the current message identifier corresponding to the current consultation reminder message exits the delay queue, so for each consultation reminder message generated according to the same consultation information, there is a certain time interval between the message sending times of each consultation reminder message. It can be seen that in the technical solution provided by the embodiment of the present invention, by pre-creating a delay queue with the message identifier of the consultation reminder message as a queue element, the interval sending of multiple consultation reminder messages generated at the same time (i.e., each consultation reminder message generated according to the same consultation information) can be achieved. In this way, the chat interface of the attending doctor and the patient being treated will not pop up multiple messages at the same time, which can avoid the situation where the interface display is stuck due to the chat interface popping up multiple messages at the same time. In addition, the user experience of the Internet medical platform can be improved.

[0050] Reference Figure 2 , is a flow chart of another message sending method provided by an embodiment of the present invention. The method in this embodiment can be combined with various optional solutions in the message sending method provided by the previous embodiment to further optimize the message sending method provided by the previous embodiment. Figure 2 As shown, the specific steps include:

[0051] S210. When receiving a consultation instruction, generate each consultation prompt message based on the consultation information carried in the consultation instruction, and store each consultation prompt message in a predetermined database.

[0052] Optionally, the reception information includes user information of the receiving doctor and user information of the patient being received; each reception prompt message is generated based on the reception information carried in the reception instruction, including: generating a first prompt message based on the reception information; determining whether the reception information satisfies each candidate prompt condition; for each candidate prompt condition, when it is determined that the reception information satisfies the current prompt condition, obtaining a second prompt message pre-configured for the current prompt condition; and determining each reception prompt message based on the first prompt message and each second prompt message.

[0053] In one possible implementation, the first prompt message includes a prompt message corresponding to the user information of the attending doctor, for example, it may be an access prompt voice or access prompt language set by the attending doctor; the first prompt message may also include a prompt message corresponding to the user information of the attending patient, for example, it may be the chief complaint information of the attending patient.

[0054] Each candidate prompt condition may be a pre-determined prompt condition. For example, a candidate prompt condition may be that the patient is younger than 6 years old; correspondingly, the second prompt message pre-configured for the candidate prompt condition may be: "Please note that the patient is younger than 6 years old." In another example, a candidate prompt condition may be that the patient has a family history of XX types of genetic diseases; correspondingly, the second prompt message pre-configured for the candidate prompt condition may be: "Please note that the patient has a family history of XX types of genetic diseases."

[0055] In an embodiment of the present invention, a plurality of candidate prompt conditions are pre-determined for the consultation information, and a second prompt message is configured for each candidate prompt condition. When the consultation information satisfies a certain candidate prompt condition, the second prompt message corresponding to the candidate prompt condition can also be determined as a consultation prompt message. In this way, by enriching the types of consultation prompt messages, it is convenient for the attending doctor to quickly understand the condition of the patient being treated, thereby facilitating communication between the attending doctor and the patient being treated. In addition, in the prior art, the Internet medical platform only prompts basic information (for example, the first prompt message in the embodiment of the present invention) to avoid the situation where the interface display is stuck due to multiple messages popping up on the chat interface at the same time. In an embodiment of the present invention, since it is possible to implement the interval sending of multiple consultation prompt messages generated at the same time, it is possible to achieve the enrichment of the types of consultation prompt messages while avoiding the situation where the interface display is stuck due to multiple messages popping up on the chat interface at the same time, so that the type and number of messages generated by the Internet medical platform are no longer restricted.

[0056] S220: Add the message identifiers corresponding to the respective admission prompt messages to a predetermined delay queue, and determine a different delay time for each message identifier added to the delay queue.

[0057] Optionally, a different delay time is determined for each message identifier added to the delay queue, including: based on the admission information, determining a target delay rule from each candidate delay rule; and according to the target delay rule, determining a different delay time for each message identifier added to the delay queue.

[0058] In a possible implementation, each candidate delay rule may include delay rule A and delay rule B. If each consultation prompt message includes only the first prompt message but does not include the second prompt message (that is, the consultation information does not satisfy any one of the candidate prompt conditions), the target delay rule may be determined to be delay rule A; conversely, if each consultation prompt message includes not only the first prompt message but also the second prompt message (that is, the consultation information satisfies at least one of the candidate prompt conditions), the target delay rule may be determined to be delay rule B.

[0059] Among them, delay rule A can be that the time interval of the delay time corresponding to each message identifier is the first time interval, and the delay time of the message identifier of the reception prompt message corresponding to the attending doctor is before the message identifier of the reception prompt message corresponding to the patient being received. That is, the reception prompt message corresponding to the attending doctor is sent first, and then the reception prompt message corresponding to the patient being received is sent. Taking the first time interval of 3 seconds as an example, delay rule A can be that the delay time corresponding to the message identifier of the access prompt voice or access prompt message set by the attending doctor is determined to be 1 second after the current moment; and the delay time corresponding to the message identifier of the prompt message of the chief complaint information of the patient being received is determined to be 4 seconds after the current moment.

[0060] Delay rule B may be that the time interval of the delay time corresponding to each message identifier is the second time interval, and the delay time of the message identifier of the first prompt message is before the second prompt message. In the first prompt message, the delay time of the message identifier of the reception prompt message corresponding to the attending doctor is before the message identifier of the reception prompt message corresponding to the patient being treated. In each second prompt message, the delay time of the message identifier of the second prompt message is related to the priority of the corresponding candidate prompt condition. The higher the priority of the corresponding candidate prompt condition, the earlier the delay time of the message identifier of the second prompt message; conversely, the lower the priority of the corresponding candidate prompt condition, the later the delay time of the message identifier of the second prompt message. That is, the reception prompt message corresponding to the attending doctor is sent first, and then the reception prompt message corresponding to the patient being treated is sent, and then each second prompt message is sent according to the priority. Among them, the priority of each candidate prompt condition can be pre-configured by the operator of the Internet medical platform. Exemplarily, the second time interval can be 2 seconds.

[0061] In the embodiment of the present invention, in different consultation scenarios (for example, different patients being consulted), the types of consultation reminder messages generated according to the consultation information and the number of consultation reminder messages may be different. Based on this, the embodiment of the present invention pre-configures different candidate delay rules for different consultation scenarios. In this way, in different consultation scenarios, different candidate delay rules can be used to adaptively adjust the sending interval and sending order of each consultation reminder message to meet the communication needs of different patients being consulted and the attending doctors in different consultation scenarios, thereby further improving the user experience of the Internet medical platform.

[0062] S230. For each message identifier in the delay queue, when the delay time of the current message identifier meets the dequeue condition of the delay queue, the current message identifier is dequeued, and the current consultation prompt message corresponding to the current message identifier is obtained from the database.

[0063] S240: Determine a target thread for the current patient admission prompt message from among the candidate threads.

[0064] In an embodiment of the present invention, a target thread can be determined for the current reception prompt message from each candidate thread based on a predetermined rule. In a possible implementation, each candidate thread can be sorted, and if the current reception prompt message is the first reception prompt message, the first candidate thread among each candidate thread is determined as the target thread; if the current reception prompt message is not the first reception prompt message, the candidate thread corresponding to the previous reception prompt message of the current reception prompt message can be determined first, and then, among each candidate thread, the candidate thread sorted after the candidate thread corresponding to the previous reception prompt message can be determined as the target thread.

[0065] Optionally, a target thread is determined for the current reception prompt message from each candidate thread, including: determining thread parameters corresponding to the current reception prompt message based on a hash value of a message batch corresponding to the current reception prompt message and the total number of threads of each candidate thread; matching the thread parameters corresponding to the current reception prompt message with the thread parameters corresponding to each candidate thread, and determining the target thread according to the matching result.

[0066] In a possible implementation, the Internet medical platform generates each consultation reminder message based on the consultation information and creates a corresponding IM channel, and can determine a corresponding message batch for each consultation reminder message. Specifically, each consultation reminder message of the same IM channel corresponds to the same message batch, and the consultation reminder messages of different IM channels correspond to different message batches. Moreover, for each consultation reminder message of the same message batch, the corresponding consultation doctor is the same, and the corresponding patient is the same.

[0067] If the message batch is digitally numbered, the digital number of the message batch can be directly determined as the hash value of the message batch; if the message batch is a string, the string of the message batch can be mapped to the hash value of the message batch through a predetermined hash function.

[0068] For example, if X represents the thread parameter corresponding to the current patient admission reminder message, Hash represents the hash value of the message batch corresponding to the current patient admission reminder message, and Y represents the total number of threads of each candidate thread, then X=Hash%Y, that is, X is the result of the modulo operation of Hash on Y. For example, if Hash is equal to 9 and the total number of threads is 4, then X is equal to 1.

[0069] Among them, the thread parameters corresponding to the current patient reception prompt message are used to characterize the candidate thread that executes the task of sending the current patient reception prompt message. In the embodiment of the present invention, different thread parameters can be determined in advance for different candidate threads. After the thread parameters corresponding to the current patient reception prompt message are determined, the thread parameters corresponding to the current patient reception prompt message can be matched with the thread parameters corresponding to each candidate thread in turn. If the thread parameters corresponding to the current patient reception prompt message are the same as the thread parameters corresponding to a candidate thread, the candidate thread can be determined as the target thread.

[0070] In an embodiment of the present invention, for each admission reminder message of the same message batch (i.e., the same IM channel), if they are processed by different candidate threads, the sending order of these admission reminder messages may be disordered (that is, the sending order is inconsistent with the corresponding delay rule). Based on this, in an embodiment of the present invention, the total number of threads is modulo the hash value of the message batch, and the candidate threads are matched for the admission reminder messages according to the modulo result. In this way, it can be ensured that each admission reminder message of the same message batch is matched to the same candidate thread, that is, each admission reminder message of the same message batch can be processed by the same candidate thread, thereby ensuring that the messages in the same IM channel are not sent out of order.

[0071] Take a doctor who sees 4 patients at the same time as an example. Figure 3 , is a simplified flow chart of matching candidate threads for a patient admission reminder message provided by an embodiment of the present invention. Figure 3As shown, the total number of candidate threads is 4. When matching candidate threads for the doctor A-patient A message batch (the corresponding admission information of the admission reminder messages in this message batch is: the doctor is doctor A, and the patient is patient A), the doctor A-patient A message batch can be matched to thread 1 according to the result of the hash value % 4 of the message batch. Similarly, the doctor A-patient B message batch can be matched to thread 2, the doctor A-patient C message batch can be matched to thread 3, and the doctor A-patient D message batch can be matched to thread 4.

[0072] S250: Add the current patient admission reminder message to the target thread, so as to execute the task of sending the current patient admission reminder message through the target thread.

[0073] Optionally, the message sending method provided by an embodiment of the present invention also includes: when a thread configuration instruction is received, based on the configuration parameters carried by the thread configuration instruction, performing a thread update operation on each candidate thread, and performing a parameter update operation on the thread parameters corresponding to each updated candidate thread.

[0074] The thread update operation is any one of a thread adding operation, a thread deleting operation, and a thread reconfiguration operation.

[0075] In one possible implementation, the thread configuration instruction may be an instruction triggered by an operation performed by an operator of the Internet medical platform in the configuration interface of the platform. For example, if the operator reselects or inputs the total number of candidate threads in the configuration interface of the platform, the thread configuration instruction may be triggered, and the configuration parameters carried in the thread configuration instruction may be the total number of candidate threads reselected or input. For another example, if the operator reselects or inputs the execution parameters of the candidate threads (which may be the survival time of the idle thread, etc.) in the configuration interface of the platform, the thread configuration instruction may be triggered, and the configuration parameters carried in the thread configuration instruction may be the execution parameters of the reselected or input candidate threads.

[0076] For example, if the total number of threads of each candidate thread is 5, and the configuration parameter carried by the thread configuration instruction is that the total number of threads is 6, then the thread update operation is a thread addition operation. At this time, the Internet medical platform can add a new candidate thread based on the current candidate threads; if the total number of threads of each candidate thread is 5, and the configuration parameter carried by the thread configuration instruction is that the total number of threads is 4, then the thread update operation is a thread deletion operation. At this time, the Internet medical platform can delete a candidate thread from the current candidate threads. If the configuration parameter carried by the thread configuration instruction is the execution parameter of the reselected or input candidate thread, then the thread update operation is a thread reconfiguration operation. At this time, the Internet medical platform can reconfigure each candidate thread based on the execution parameter of the reselected or input candidate thread.

[0077] In different consultation scenarios (for example, different time periods), the number of consultation reminder messages generated by the Internet medical platform may be different. Based on this, in an embodiment of the present invention, it is possible to support the operators of the Internet medical platform to dynamically configure candidate threads according to different consultation scenarios to meet the business needs of different consultation scenarios.

[0078] In the embodiment of the present invention, on the basis of the above-mentioned embodiment, since in actual application, there will be multiple doctors online at the same time in the Internet medical platform, and each doctor can see multiple patients at the same time, the Internet medical platform will generate a large number of consultation reminder messages. In this way, if the main thread of the Internet medical platform is used to execute the task of sending a large number of consultation reminder messages, it may cause a backlog of message sending, affecting the timeliness of message sending. Based on this, in the embodiment of the present invention, multiple candidate threads can be used to execute the task of sending a large number of consultation reminder messages, thereby solving the problem of a large number of message backlogs and ensuring the timeliness of message sending.

[0079] It should be noted that the message sending method proposed in the embodiment of the present invention and the aforementioned embodiment belong to the same inventive concept. The technical details not fully described in this embodiment can be referred to the aforementioned embodiment, and the beneficial effects of the aforementioned embodiment are also applicable to this embodiment.

[0080] In order to more clearly describe the technical solution provided by the embodiment of the present invention, refer to Figure 4 , is a simplified flow chart of a message sending method provided by an embodiment of the present invention. The method in this embodiment can be combined with various optional solutions in the message sending method provided by the previous embodiment, and the message sending method provided by the previous embodiment is further optimized.

[0081] like Figure 4As shown, the Internet medical platform will generate a batch of consultation reminder messages during operation. For any consultation reminder message in the batch of consultation reminder messages, the Internet medical platform will first store the consultation reminder message in a predetermined database (corresponding to Figure 4 S1.1 in the above), then adding the message identifier corresponding to the patient admission reminder message to the predetermined delay queue. In the process of adding the message identifier corresponding to the patient admission reminder message to the delay queue, a delay time (corresponding to Figure 4 S1.2 in ), and a corresponding verification task (corresponding to Figure 4 In S1.3), the verification task is executed after a preset time. In addition, a message-based timer is deployed in the Internet medical platform. When the message identifier meets the dequeue condition, the message-based timer can pull the message identifier from the delay queue (corresponding to Figure 4 Then, the patient consultation reminder message corresponding to the message identifier is obtained from the database (corresponding to Figure 4 S2.2 in the above example), and add the patient admission reminder message to the corresponding thread (corresponding to Figure 4 S2.3 in the thread), send the consultation reminder message through the IM channel in the thread (corresponding to Figure 4 After the Internet medical platform determines that the consultation reminder message has been sent successfully, it can delete the consultation reminder message stored in the database (corresponding to Figure 4 After the execution timing of the verification task is triggered (corresponding to S2.5 in Figure 4 S3.1 in the above example) can obtain the patient consultation reminder message from the database again. If the patient consultation reminder message is successfully obtained from the database (corresponding to Figure 4 2), it means that the admission reminder message has not been sent successfully, and the compensation logic can be executed to resend the admission reminder message through the IM channel (corresponding to Figure 4 S3.3 in ).

[0082] It should be noted that the message sending method proposed in the embodiment of the present invention and the aforementioned embodiment belong to the same inventive concept. The technical details not fully described in this embodiment can be referred to the aforementioned embodiment, and the beneficial effects of the aforementioned embodiment are also applicable to this embodiment.

[0083] Figure 5 This is a schematic diagram of the structure of a message sending device provided in an embodiment of the present invention. The device includes: a message generating module 510, a queue adding module 520, and a message sending module 530.

[0084] Exemplarily, the message generating module 510 may execute S110 in the above method embodiment, the queue adding module 520 may execute S120 in the above method embodiment, and the message sending module 530 may execute S130 in the above method embodiment.

[0085] Specifically, the message generation module 510 is used to generate each reception prompt message based on the reception information carried by the reception instruction when a reception instruction is received, and store each reception prompt message in a predetermined database; the queue adding module 520 is used to add the message identifier corresponding to each reception prompt message to a predetermined delay queue, and determine a different delay time for each message identifier added to the delay queue; the message sending module 530 is used to dequeue the current message identifier for each message identifier in the delay queue when the delay time of the current message identifier meets the dequeue condition of the delay queue, and obtain the current reception prompt message corresponding to the current message identifier from the database, and send the current reception prompt message.

[0086] Optionally, in a possible implementation manner, the message sending module 530 is specifically configured to:

[0087] A target thread is determined for the current admission prompt message from each candidate thread; the current admission prompt message is added to the target thread, so that the task of sending the current admission prompt message is executed through the target thread.

[0088] Optionally, in another possible implementation, the message sending module 530 is further configured to:

[0089] Based on the hash value of the message batch corresponding to the current reception prompt message and the total number of threads of each candidate thread, the thread parameters corresponding to the current reception prompt message are determined; the thread parameters corresponding to the current reception prompt message are matched with the thread parameters corresponding to each candidate thread, and the target thread is determined according to the matching result.

[0090] Optionally, in another possible implementation, the message sending device further includes an updating module;

[0091] The update module is used to perform a thread update operation on each candidate thread based on the configuration parameters carried by the thread configuration instruction when receiving the thread configuration instruction, and perform a parameter update operation on the thread parameters corresponding to each updated candidate thread; wherein the thread update operation is any one of a thread addition operation, a thread deletion operation, and a thread reconfiguration operation.

[0092] Optionally, in another possible implementation, the message sending device further includes a deletion module;

[0093] The deleting module is used to delete the current consultation prompt message stored in the database after the message sending module 530 obtains the current consultation prompt message corresponding to the current message identifier from the database and sends the current consultation prompt message.

[0094] Optionally, in another possible implementation, the message sending device further includes a creation module and an execution module;

[0095] A creation module, used for adding the message identifiers corresponding to the respective consultation reminder messages to the predetermined delay queue in the queue adding module 520, and after determining different delay times for the message identifiers added to the delay queue, creating verification tasks for the respective consultation reminder messages;

[0096] An execution module is used to execute each verification task; wherein, for each verification task, the task content of the current verification task includes: after a preset time period, obtaining the admission reminder message corresponding to the current verification task from the database; when it is determined that the admission reminder message corresponding to the current verification task is successfully obtained from the database, the admission reminder message corresponding to the current verification task is sent again.

[0097] Optionally, in another possible implementation, the consultation information includes user information of the doctor who is consulting and user information of the patient who is consulting. The message generation module 510 is specifically used for:

[0098] Generate a first prompt message based on the consultation information; determine whether the consultation information satisfies each candidate prompt condition; for each candidate prompt condition, if it is determined that the consultation information satisfies the current prompt condition, obtain a second prompt message pre-configured for the current prompt condition; determine each consultation prompt message based on the first prompt message and each second prompt message.

[0099] Optionally, in another possible implementation, the queue adding module 520 is specifically configured to:

[0100] Based on the admission information, a target delay rule is determined from each candidate delay rule; and according to the target delay rule, a different delay time is determined for each message identifier added to the delay queue.

[0101] The message sending device provided in the embodiment of the present invention belongs to the same inventive concept as the message sending method provided in the aforementioned embodiments. For details that are not fully described in the embodiment of the message sending device, reference can be made to the relevant contents of the aforementioned method embodiments, and the corresponding beneficial effects can also be referred to the beneficial effect analysis of the aforementioned method embodiments.

[0102] Figure 6 A schematic diagram of the structure of a message sending device provided in an embodiment of the present invention. Figure 6A block diagram of an exemplary message sending device 12 suitable for use in implementing embodiments of the present invention is shown. Figure 6 The message sending device 12 shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.

[0103] like Figure 6 As shown, the message sending device 12 is in the form of a general purpose computing device. The components of the message sending device 12 may include, but are not limited to: one or more processors or processing units 16, a system memory 28, and a bus 18 connecting different system components (including the system memory 28 and the processing unit 16).

[0104] Bus 18 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor or a local bus using any of a variety of bus architectures. By way of example, these architectures include, but are not limited to, an Industry Standard Architecture (ISA) bus, a Micro Channel Architecture (MAC) bus, an Enhanced ISA bus, a Video Electronics Standards Association (VESA) local bus, and a Peripheral Component Interconnect (PCI) bus.

[0105] The message sending device 12 typically includes a variety of computer system readable media. These media can be any available media that can be accessed by the message sending device 12, including volatile and non-volatile media, removable and non-removable media.

[0106] System memory 28 may include computer system readable media in the form of volatile memory, such as random access memory (RAM) 30 and / or cache memory (i.e., Figure 6 The message sending device 12 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, the storage system 34 may be used to read and write non-removable, non-volatile magnetic media ( Figure 6 not shown, usually called a "hard drive"). Although Figure 6 Not shown in the figure, a disk drive for reading and writing to a removable non-volatile disk (e.g., a "floppy disk"), and an optical disk drive for reading and writing to a removable non-volatile optical disk (e.g., a CD-ROM, a DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to the bus 18 via one or more data medium interfaces. The system memory 28 may include at least one program product having a set (e.g., at least one) of program modules that are configured to perform the functions of the various embodiments of the present invention.

[0107] A program / utility 40 having a set (at least one) of program modules 42 may be stored, for example, in system memory 28, such program modules 42 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment. Program modules 42 generally perform the functions and / or methods of the embodiments described herein.

[0108] The message sending device 12 may also communicate with one or more external devices 14 (e.g., keyboards, pointing devices, displays 24, etc.), one or more devices that enable a user to interact with the message sending device 12, and / or any device that enables the message sending device 12 to communicate with one or more other computing devices (e.g., network cards, modems, etc.). Such communication may be performed through an input / output (I / O) interface 22. Furthermore, the message sending device 12 may also communicate with one or more networks (e.g., local area networks (LANs), wide area networks (WANs), and / or public networks, such as the Internet) through a network adapter 20. Figure 6 As shown, the network adapter 20 communicates with other modules of the message sending device 12 via the bus 18. It should be understood that although Figure 6 Not shown, other hardware and / or software modules may be used in conjunction with the message sending device 12, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0109] The processing unit 16 executes various functional applications and data processing by running the program stored in the system memory 28, such as implementing the steps of the message sending method provided by any of the aforementioned embodiments of the present invention, the method comprising: receiving a consultation instruction, generating each consultation reminder message based on the consultation information carried by the consultation instruction, and storing each consultation reminder message in a predetermined database; adding the message identifier corresponding to each consultation reminder message to a predetermined delay queue, and determining a different delay time for each message identifier added to the delay queue; for each message identifier in the delay queue, when the delay time of the current message identifier meets the dequeue condition of the delay queue, dequeueing the current message identifier, obtaining the current consultation reminder message corresponding to the current message identifier from the database, and sending the current consultation reminder message.

[0110] Of course, those skilled in the art can understand that the processor can also implement the technical solution of the message sending method provided by any embodiment of the present invention.

[0111] The present embodiment provides a computer-readable storage medium having a computer program stored thereon. When the program is executed by a processor, the steps of a message sending method as provided in any of the foregoing embodiments of the present invention are implemented, the method comprising: receiving a consultation instruction, generating each consultation reminder message based on the consultation information carried in the consultation instruction, and storing each consultation reminder message in a predetermined database; adding a message identifier corresponding to each consultation reminder message to a predetermined delay queue, and determining a different delay time for each message identifier added to the delay queue; for each message identifier in the delay queue, when the delay time of the current message identifier meets the dequeue condition of the delay queue, dequeueing the current message identifier, obtaining the current consultation reminder message corresponding to the current message identifier from the database, and sending the current consultation reminder message.

[0112] The computer storage medium of the embodiment of the present invention can adopt any combination of one or more computer-readable media. The computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. The computer-readable storage medium can be, for example, but not limited to: an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples (non-exhaustive list) of computer-readable storage media include: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this document, a computer-readable storage medium can be any tangible medium containing or storing a program, which can be used by an instruction execution system, device or device or used in combination with it.

[0113] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, which carry computer-readable program code. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0114] The program code embodied on the computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

[0115] Computer program code for performing the operation of the present invention may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or messaging device. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0116] This embodiment provides a computer program product, on which a computer program is stored. When the program is executed by a processor, the steps of the message sending method provided in any of the aforementioned embodiments of the present invention are implemented.

[0117] It should be understood by those skilled in the art that the modules or steps of the present invention described above can be implemented by a general-purpose computing device, they can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices, optionally, they can be implemented by a program code executable by a computer device, so that they can be stored in a storage device and executed by the computing device, or they can be made into individual integrated circuit modules, or multiple modules or steps therein can be made into a single integrated circuit module for implementation. Thus, the present invention is not limited to any specific combination of hardware and software.

[0118] Note that the above are only preferred embodiments of the present invention and the technical principles used. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and that various obvious changes, readjustments and substitutions can be made by those skilled in the art without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in more detail through the above embodiments, the present invention is not limited to the above embodiments, and may include more other equivalent embodiments without departing from the concept of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims

1. A message sending method, characterized in that: include: When receiving a consultation instruction, generating each consultation prompt message based on the consultation information carried in the consultation instruction, and storing each consultation prompt message in a predetermined database; Adding the message identifiers corresponding to the respective admission reminder messages to a predetermined delay queue, and determining a different delay time for each of the message identifiers added to the delay queue; For each message identifier in the delay queue, when the delay time of the current message identifier meets the dequeue condition of the delay queue, the current message identifier is dequeued, and the current consultation reminder message corresponding to the current message identifier is obtained from the database, and the current consultation reminder message is sent.

2. The message sending method according to claim 1, characterized in that: The sending of the current patient admission reminder message includes: Determine a target thread for the current admission prompt message from each candidate thread; The current admission reminder message is added to the target thread, so that the task of sending the current admission reminder message is executed through the target thread.

3. The message sending method according to claim 2, characterized in that: Determining a target thread for the current admission prompt message from each candidate thread includes: Determine the thread parameter corresponding to the current patient admission prompt message based on the hash value of the message batch corresponding to the current patient admission prompt message and the total number of threads of each candidate thread; The thread parameters corresponding to the current patient admission prompt message are matched with the thread parameters corresponding to each of the candidate threads, and the target thread is determined according to the matching result.

4. The message sending method according to claim 3, characterized in that: The method further comprises: When a thread configuration instruction is received, a thread update operation is performed on each candidate thread based on the configuration parameters carried by the thread configuration instruction, and a parameter update operation is performed on the thread parameters corresponding to each updated candidate thread; wherein the thread update operation is any one of a thread addition operation, a thread deletion operation, and a thread reconfiguration operation.

5. The message sending method according to claim 1, characterized in that: After obtaining the current patient consultation reminder message corresponding to the current message identifier from the database and sending the current patient consultation reminder message, the method further includes: The current patient admission reminder message stored in the database is deleted.

6. The message sending method according to claim 5, characterized in that: After adding the message identifiers corresponding to the respective admission reminder messages to a predetermined delay queue and determining a different delay time for each of the message identifiers added to the delay queue, the method further includes: Creating a verification task for each of the patient admission reminder messages; Execute each of the verification tasks; wherein, for each of the verification tasks, the task content of the current verification task includes: after a preset period of time, obtaining a consultation reminder message corresponding to the current verification task from the database; when it is determined that the consultation reminder message corresponding to the current verification task is successfully obtained from the database, the consultation reminder message corresponding to the current verification task is sent again.

7. The message sending method according to any one of claims 1 to 6, characterized in that: The consultation information includes the user information of the doctor who receives the consultation and the user information of the patient who receives the consultation; The generating of each consultation prompt message based on the consultation information carried by the consultation instruction includes: generating a first prompt message based on the consultation information; Determine whether the patient information meets each candidate prompt condition; For each candidate prompt condition, when it is determined that the patient information meets the current prompt condition, obtaining a second prompt message pre-configured for the current prompt condition; The respective consultation prompt messages are determined according to the first prompt message and the respective second prompt messages.

8. The message sending method according to claim 7, characterized in that: Determining a different delay time for each message identifier added to the delay queue includes: Based on the patient admission information, determining a target delay rule from candidate delay rules; According to the target delay rule, a different delay time is determined for each message identifier added to the delay queue.

9. A message sending device, characterized in that: include: A message generating module, configured to generate, upon receiving a consultation instruction, each consultation prompt message based on the consultation information carried in the consultation instruction, and store each consultation prompt message in a predetermined database; A queue adding module, used for adding the message identifiers corresponding to the respective admission reminder messages to a predetermined delay queue, and determining a different delay time for each of the message identifiers added to the delay queue; A message sending module is used to dequeue the current message identifier for each message identifier in the delay queue when the delay time of the current message identifier meets the dequeue condition of the delay queue, obtain the current consultation reminder message corresponding to the current message identifier from the database, and send the current consultation reminder message.

10. A message sending device, characterized in that: The message sending device comprises: one or more processors; A memory for storing one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the message sending method as described in any one of claims 1 to 8.

11. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the message sending method according to any one of claims 1 to 8 is implemented.