Information transmission method, device and equipment

Abstract

The invention provides an information transmission method, device and equipment. The information transmission method comprises the following steps: receiving a message sending request sent by a message sender based on a message sending account; based on the message sending request, obtaining a message receiving account, message content of the to-be-sent message and a message sending mode; generating a message task record corresponding to each message receiving account according to the message content, wherein each message task record comprises a to-be-sent message; determining message sending time according to the message sending mode; and in response to the arrival of the message sending time, sending the to-be-sent message to the message receiving account corresponding to each message task record based on each message task record so as to improve the amount of information transmitted by message transmission and the information transmission efficiency.

Description

TECHNICAL FIELD

[0001] Embodiments of the present application relate to the technical field of data communication, and in particular, to an information transmission method, device and equipment. BACKGROUND

[0002] Currently, investors often perform investment operations on virtual resources through financial clients. The financial clients can push service information, such as holiday greetings, marketing activities, investment reports, etc., to the investors through service numbers subscribed by the investors. However, this information transmission manner has the problem that the investors cannot know which customer manager sends the service information, which not only affects the user experience of the investors, but also affects the information distribution effect, resulting in a low amount of transmitted information and a low information transmission efficiency and success rate. SUMMARY

[0003] The present application provides an information transmission method, device and equipment, which can solve the problem of a low amount of transmitted information and a low information transmission efficiency and success rate in the related art, can improve the amount of transmitted information and the information transmission efficiency and success rate, and improve the information transmission effect and user experience.

[0004] In a first aspect, the present application provides an information transmission method, comprising: receiving a message sending request sent by a message sender based on a message sending account; obtaining a message receiving account, message content of a to-be-sent message and a message sending mode based on the message sending request; generating a message task record corresponding to each message receiving account respectively according to the message content, each message task record comprising the to-be-sent message; determining a message sending time according to the message sending mode; and in response to the arrival of the message sending time, sending the to-be-sent message to the message receiving account corresponding to each message task record based on each message task record.

[0005] In a second aspect, the present application provides an information transmission device, comprising: a request receiving module configured to receive a message sending request sent by a message sender based on a message sending account; a content determining module configured to obtain a message receiving account, message content of a to-be-sent message and a message sending mode based on the message sending request; a task generating module configured to generate a message task record corresponding to each message receiving account respectively according to the message content, each message task record comprising the to-be-sent message; a time determining module configured to determine a message sending time according to the message sending mode; and a message sending module configured to, in response to the arrival of the message sending time, send the to-be-sent message to the message receiving account corresponding to each message task record based on each message task record.

[0006] In a third aspect, the present application provides an electronic device, comprising a processor and a memory, the memory being configured to store a computer program, and the processor being configured to invoke and run the computer program stored in the memory to execute the method in the first aspect or any implementation manner thereof.

[0007] In a fourth aspect, the present application provides a computer readable storage medium for storing a computer program, the computer program causing a computer to execute the method according to the first aspect or any implementation manner thereof.

[0008] In a fifth aspect, the present application provides a computer program product comprising computer program instructions, the computer program instructions causing a computer to execute the method according to the first aspect or any implementation manner thereof.

[0009] In a sixth aspect, the present application provides a computer program, the computer program causing a computer to execute the method according to the first aspect or any implementation manner thereof.

[0010] Other technical features and effects involved in the technical solutions of the present application will be introduced in subsequent embodiments. To avoid repetition, they will not be described here. BRIEF DESCRIPTION OF DRAWINGS

[0011] The drawings used in the embodiment description are introduced as follows.

[0012] Figure 1 An application scenario graph provided for the embodiments of the present application; Figure 2 A flowchart of an information transmission method provided for the embodiments of the present application; Figure 3 A schematic diagram of an information transmission method provided for the embodiments of the present application; Figure 4 A schematic diagram of another information transmission method provided for the embodiments of the present application; Figure 5 A schematic diagram of another information transmission method provided for the embodiments of the present application; Figure 6 A schematic diagram of another information transmission method provided for the embodiments of the present application; Figure 7 A schematic diagram of another information transmission method provided for the embodiments of the present application; Figure 8 A schematic diagram of another information transmission method provided for the embodiments of the present application; Figure 9 A schematic diagram of another information transmission method provided for the embodiments of the present application; Figure 10 A schematic diagram of an information transmission device provided for the embodiments of the present application; Figure 11 A schematic diagram of an electronic device provided for the embodiments of the present application. DETAILED DESCRIPTION

[0013] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0014] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or server that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or devices.

[0015] In one embodiment, the technical solution of this application can be used in information transmission scenarios, for example, in a scenario where a message sender sends a message to a message receiver's message receiving account based on the message sending account. The message sender can be a client manager, the message receiver can be an investor, and the message sending account and message receiving account can be user accounts corresponding to the same financial client, but are not limited to these.

[0016] For example, Figure 1 An application scenario diagram provided for an embodiment of this application, such as... Figure 1 As shown, this application scenario may include a first terminal device 110, a server 120, and a second terminal device 130 connected via a wired or wireless network. The server 120 may be a single server, a server cluster consisting of multiple servers, or a cloud platform control center, but is not limited to these. The first terminal device 110 or the second terminal device 130 may be a mobile phone, tablet computer, laptop computer, or desktop computer, but is not limited to these.

[0017] It should be noted that, Figure 1 The terminal devices and servers mentioned are merely examples; in practice, other numbers or types of devices may also be included.

[0018] Specifically, the message sender can log in to the message sending account using the financial client installed on the first terminal device 110 and trigger a message sending request through the first terminal device 110. Then, the server 120 can receive the message sending request sent by the message sender based on the message sending account, and obtain the message receiving account, the message content of the message to be sent, and the message sending mode based on the message sending request. Next, the server 120 generates a message task record corresponding to each message receiving account based on the message content, and each message task record includes the message to be sent. Then, the server 120 determines the message sending time based on the message sending mode. Afterwards, in response to the arrival of the message sending time, the server 120 sends the message to be sent to the message receiving account corresponding to each message task record based on each message task record. Finally, the message receiver can log in to the message receiving account using the financial client installed on the second terminal device 130, and the second terminal device 130 can obtain and display the message to be sent by the server 120.

[0019] It should be noted that all technical solutions in this application can be combined in any way to form optional embodiments of this application. To avoid repetition, these will not be elaborated upon.

[0020] Furthermore, in the specific embodiments of this application, related data, information, requests or instructions are involved, such as message sending account, message sending request, message receiving account, message to be sent, message sending mode, message task record, message sending time and data involved in request verification. When the embodiments of this application are applied to specific products or technologies, user permission, consent or authorization is required, and the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions.

[0021] The technical solution of this application will be described in detail below: In one embodiment, Figure 2 A flowchart illustrating an information transmission method provided in this application embodiment, the method can be performed by, for example... Figure 1 The server 120 shown is used for execution, but is not limited to this.

[0022] like Figure 2 As shown, the method may include S210-S250: S210: Receive a message sending request sent by the message sender based on the message sending account.

[0023] The message sending account refers to the management account used by the message sender, who is the creator of the mass messaging task corresponding to this message sending request. The message sender can be a customer manager of the Customer Relationship Management (CRM) system or a business person in the middle platform, but is not limited to these.

[0024] For example, a message sending request may include the message receiving account, the message content to be sent, and the message sending mode. It is understood that one message sending request can correspond to one mass messaging task.

[0025] In this context, the message receiving account is the user account of the message recipient. The message recipient can be an investor, or a customer managed in a CRM system, but is not limited to these. The message receiving account can be an account selected by the message sender based on the message sending account or filtered according to pre-set specific filtering conditions. For example, the message receiving account can be an account within the message sending permission scope of the message sending account, specifically at least one account from all message receiving accounts managed by the message sender. It should be noted that the number of message receiving accounts in a message sending request can be one or more; this application does not impose any limitation on this.

[0026] The message content can be in at least one of the following formats: text, image, file, audio, or video; this application does not impose any restrictions on this. Specifically, the message content can be business service information, such as proactively greeting customers who haven't yet established contact, sending blessings to customers who have upgraded to a premium membership, inviting them to events, or reminding them of their benefits and rewards. Furthermore, multiple message templates can be pre-defined, each containing message content of a specific type. The message sender can select a template based on their message sending account and determine the message content to be sent in the message request based on the message content within that template, ensuring the standardization and consistency of information transmission.

[0027] Message sending modes include real-time sending mode and scheduled sending mode. Real-time sending mode means that the message to be sent is sent immediately after a message sending request is triggered by the message sending account. Scheduled sending mode means that the message to be sent is sent after a specified duration following a message sending request is triggered by the message sending account, or at a specified time after a message sending request is triggered. The specified duration and specified time can be selected or entered by the message sender through their message sending account.

[0028] Specifically, the system can determine the message content in a message sending request based on the sending account, and then determine the receiving account and sending mode based on the message content. For example, keywords can be extracted from the message content to identify target keywords. These target keywords can be preset keywords within a predefined content theme dimension, which may include, but is not limited to, report push, holiday greetings, wealth management maturity, market changes, virtual resource trading, and rights acquisition. Then, the receiving account and sending mode can be determined based on the target keywords and account mapping relationship. The account mapping relationship is the mapping relationship between keywords, receiving accounts, and sending modes. For example, in the account mapping relationship, the keyword "research report" corresponds to all receiving accounts managed by the sending account (or the sender), and the corresponding sending mode is real-time sending. The keyword "Spring Festival" corresponds to accounts that subscribe to holiday content pushes among all receiving accounts managed by the sending account (or the sender), and the corresponding sending mode is scheduled sending, with the sending time being the day before the holiday corresponding to the keyword "Spring Festival".

[0029] For example, such as Figure 3 As shown, the message sender, such as investment advisor 1, can log in to the financial client based on their message sending account and trigger the "IM Bulk Message" button displayed on the financial client. The financial client can then redirect to the bulk message configuration page. Next, as in the technical solution described in the above embodiment, the message receiving account (corresponding to the message sending request) can be selected, filled in, or automatically generated on the message configuration page. Figure 3 The target audience shown in the image), the message content of the message to be sent (the message content corresponds to...) Figure 3 The message template shown is... Figure 3 The application template and message type shown in the image) and message sending mode (corresponding to) Figure 3 (The sending method shown in the image). In addition, a preview of the message to be sent can be displayed on the bulk message configuration page. It can also respond to the "Cancel" button below the preview to withdraw the content of the confirmed message sending request; it can respond to the "Save" button below the preview to display a save prompt, and respond to the "OK" button in the save prompt to save the content of the confirmed message sending request and simultaneously display it in the bulk message list, setting the message sending status to draft; it can respond to the "Submit" button below the preview to send a message sending request, allowing the server to receive message sending requests sent by the message sender based on the message sending account.

[0030] S220: Obtain the message receiving account, message content of the message to be sent, and message sending mode based on the message sending request.

[0031] For example, as shown in the above embodiments, the message sending request includes the message receiving account, the message content of the message to be sent, and the message sending mode. Therefore, the content of the message sending request can be directly extracted to obtain the message receiving account, the message content of the message to be sent, and the message sending mode.

[0032] Furthermore, it is understandable that situations where the message content includes attachments or other large amounts of data, or where there are many message receiving accounts, can lead to a large amount of data in the message sending request, resulting in slow transmission or even failure. Therefore, before executing S210, the data volume of each message receiving account and message content can be determined. If the data volume of either the message receiving account or the message content exceeds a data volume threshold, the message receiving account or message content can be stored in a preset storage unit (e.g., memory or cloud storage), which can be compressed before storage. Then, the storage unit address of the preset storage unit is written into the message sending request. Subsequently, when executing S220, the storage unit address of the preset storage unit can be obtained first, and the message receiving account or message content can be retrieved based on the storage unit address.

[0033] In one embodiment, before executing S230, the message sending request can be validated for the first time; if the first request validation passes, S230 can be executed; otherwise, S230 can be skipped and a message indicating that the request validation for the message sending account failed can be returned.

[0034] For example, the first request verification includes at least one of the following: The message name in the message content is validated for uniqueness. For example, it can be checked whether the message name is consistent with the name of a historical message sent by the message sending account within a preset historical time range, so as to avoid the same message being sent repeatedly. The system checks for duplicate accounts among each message receiving account; that is, it checks for duplicate message receiving accounts in the message sending request. If duplicates are found, deduplication can be performed. The message sending time indicated by the message sending mode is verified. For example, it can be verified whether the message sending time indicated by the message sending mode is a time before the current time, or whether it exceeds a preset time range. Perform sensitive word verification on message sending requests; Verify the message sending permissions of the message sending account. For example, check whether there are any accounts other than all message receiving accounts corresponding to the message sending permissions of the message sending account in the message sending request. Verify whether the message sending request corresponds to the new operation. Each message sending request has a unique request identifier. The request corresponding to the new operation means that the message sending request has never existed in the system before and is a new message sending request that has been triggered.

[0035] For example, such as Figure 4 As shown, after executing S220, data verification can be performed on the mass messaging task. This involves performing the first verification on the message sending request. If the verification passes, it can be checked whether the message sending request corresponds to a new operation. If the message sending request does not correspond to a new operation, historical message sending records can be queried, i.e., a retrospective lookup of the mass messaging records is performed. If a sending record for the corresponding mass messaging task exists in the historical message sending records, the historical message sending records are updated according to the message sending request. If the message sending request corresponds to a new operation, a historical message sending record is added to the message sending request. This avoids duplicate or missing records for message sending requests.

[0036] S230: Generate a message task record corresponding to each message receiving account based on the message content. Each message task record includes the message to be sent.

[0037] A message task record can be understood as a message instruction to be sent, which instructs the sender to the corresponding message receiving account.

[0038] For example, you can iterate through each message receiving account in the message sending request. For each message receiving account, you can first create a blank initial message task record that does not contain any content. Then, copy the message content of the message to be sent into the initial message task record and bind the message receiving account to the initial message task record. For example, you can add the message receiving account to a preset field position in the initial message task record to obtain the message task record corresponding to each message receiving account.

[0039] In addition, the status of the message task record at this time can be set to "pending to send". After executing S250, the status can be set to "sent".

[0040] S240: Determine the message sending time based on the message sending mode.

[0041] For example, in conjunction with the above embodiments, if the message sending mode is real-time sending mode, the message sending time is determined to be the current moment; if the message sending mode is timed sending mode, the message sending time is determined to be the moment corresponding to the timed sending mode, for example, it can be the moment after a specified duration from the current moment or a specified moment.

[0042] In one embodiment, before executing S250, a second request verification can be performed on the message to be sent; after the second request verification passes, S250 can be executed; otherwise, S250 can be omitted, and a request verification failure message corresponding to the message sending account can be returned.

[0043] For example, the second request for verification includes at least one of the following: Perform sensitive word verification on message sending requests; Verify the message sending permissions of the message sending account. For example, it can verify whether the message sending account has the permission to send message content or send messages to the message receiving account. Verify whether the message sending account exists in the message sending system. For example, you can query the message sending account in the message sending system. If the message sending account is found in the message sending system, it is confirmed that the message sending account exists in the message sending system, thus avoiding the message sending account being a canceled account or an unregistered account. Verify whether there is an account follow-up person for each message receiving account. For example, you can query the customer follow-up account of the account follow-up person for each message receiving account in the CRM system. If it can be found, it is confirmed that there is an account follow-up person, so as to avoid the message receiving account having no account to reply to the response message. Verify whether the message sending account has enabled the mass message sending function. For example, the mass message sending function refers to the function of sending a message to be sent to different message receiving accounts at once. If there are multiple message receiving accounts in the message sending request, this verification can be performed. Verify whether the message sending account has enabled pre-allocated message sending. For example, pre-allocated message sending means configuring the sending permission of the message to be sent to a specific message sending account. If the message sending account in S210 is that specific message sending account, this verification can be performed. To verify whether a message sending request has been sent, for example, after a message sending request is sent to a message receiving account, the message receiving account can return a first receiving identifier carrying the request identifier of the message sending request to the message sending account. When performing this verification, the request identifier of the message sending request can be used to check whether the first receiving identifier exists. If it does not exist, it is determined that the message sending request has not been sent; if it exists, it is determined that the message sending request has been sent. Verify whether the message sending account matches the account that sent the message sending request. For example, after receiving a message sending request from the message sending account, a second receiving identifier can be generated, carrying the message sending account and the request identifier of the message sending request. When performing this verification, the request identifier of the message sending request can be used to query the second receiving identifier, and it can be determined whether the account in the second receiving identifier is the message sending account. If the account in the second receiving identifier is the message sending account, it is determined that the message sending account matches the account that sent the message sending request; otherwise, it is determined that they do not match.

[0044] Understandably, performing two verifications on message content—one based on manual review and the other on automated server-side keyword checks—can further reduce public opinion issues caused by message non-compliance and ensure the standardization and consistency of information transmission. Furthermore, given the time delay between scheduled sending and the actual delivery of a message after approval, performing a second real-time verification before sending minimizes risks arising from non-compliant message content or sending permission issues.

[0045] S250: In response to the arrival of the message sending time, send the message to be sent to the message receiving account corresponding to each message task record based on each message task record.

[0046] Specifically, S250 includes the following steps: S250-1: Determine the message sending account as the key, and determine the value corresponding to each key for each message task record to obtain the message data structure of the message receiving account corresponding to each message task record.

[0047] S250-2: Generate message sending instructions for each message receiving account based on each message data structure.

[0048] The message sending command can contain a message data structure. For example, the message data structure can be written into the request body of the message sending command, and the request header of the message sending command can contain the corresponding message receiving account.

[0049] S250-3: Send the message to be sent to each message receiving account according to each message sending instruction.

[0050] Specifically, in one embodiment, for each message receiving account, at least one message receiving group can be obtained by taking at least one message receiving account belonging to the same customer follow-up account; and using each customer follow-up account as a different sending batch, the corresponding message to be sent can be sent to the message receiving accounts under the at least one message receiving group according to the message sending instruction.

[0051] For example, for each message receiving group, the corresponding message receiving account can be obtained from the request headers of each message sending command under that group. The batch message sending interface of the customer follow-up account can then be directly called to send the message data structure from the request body of the message sending command to each message receiving account. After receiving the message data structure, the message receiving account can parse it to obtain the customer follow-up account and message task record, and then display the message receiving page based on these information. This avoids the instantaneous exhaustion of network bandwidth and overload of downstream interfaces caused by sending a large number of concurrent messages at once, thus improving system stability and throughput.

[0052] In this context, the customer follow-up account refers to the account used by the person who follows up on the message. The person who follows up on the message is the account that actually communicates and interacts with the message receiving account (e.g., the user of the message recipient), i.e., the account that actually sends the message to be sent. It can be understood that the customer follow-up account and the message sending account can be the same account or different accounts. One customer follow-up account corresponds to at least one message receiving account.

[0053] Furthermore, during the execution of S250-3, message sending can be delayed for certain message receiving accounts. For example, in one embodiment, before executing S250-3, message receiving accounts can be filtered to determine a first message receiving account that is currently online and a second message receiving account that is currently offline. The message to be sent can be sent to the first message receiving account first; the account status of the second message receiving account is checked periodically, and if the account status of the second message receiving account is detected to be online, the message to be sent is sent to the second message receiving account.

[0054] Furthermore, based on the customer follow-up account corresponding to the message receiving account and the account's active time period, the message receiving account is divided into multiple message receiving groups, and a message forwarding gateway is set up for each message receiving group. For a target message receiving group, in response to the account's active time period corresponding to the target message receiving group at the time of message sending, the message data structure in the request body of the message sending instruction is sent to the message forwarding gateway. The message forwarding gateway detects the account status of each message receiving account under the message receiving group. If the account status of the message receiving account is detected to be online, the message to be sent is sent to the message receiving account.

[0055] The account activity period refers to the time within a day when an account is online and engages in account-triggered activities (such as viewing messages, reading push notifications, or executing transactions). When an account activity period is detected, a message to be sent can be sent to the corresponding message-receiving account, thereby improving message delivery effectiveness.

[0056] The above embodiments are described below with reference to schematic diagrams: In one embodiment, such as Figure 5 As shown, the message sending request can be validated first, i.e., the initial request is validated. After passing the validation, it can be verified whether the message sending request is a request under the "add" operation, and the group message record can be processed according to the validation result. This is similar to... Figure 4 The process shown is similar. Afterwards, before executing S250, a second verification request can be performed on the message to be sent, for example, to check for sensitive words in the message content. After the verification passes, the message to be sent can be submitted to the OA approval process for manual verification.

[0057] In one embodiment, such as Figure 6 As shown, Figure 6 For the second verification request process, the following can be verified in sequence. If any of them fail, an error message will be generated directly: whether the message content contains sensitive words, whether the CRM system contains a message sending account, whether the message receiving account has a corresponding main follow-up customer manager (i.e., account follow-up person) account, whether the main follow-up customer manager of the message receiving account has enabled the IM (Instant Messaging) function, whether the main follow-up customer manager supports chatting with the message receiving account, whether the message sending account has the permission to create group sending tasks, whether the message to be sent has been sent, whether the message sending account is the account that sent the message sending request, and whether other verifications have passed (other verifications can be any of the verification items in the above embodiments).

[0058] In one embodiment, such as Figure 7As shown, the server can obtain a list of bulk message sending tasks, i.e., the message task record for each message receiving account. Then, it iterates through each message receiving account; if no un-visited account exists, the process ends. For each message receiving account, a first request verification can be performed. If successful, the message sending status is set to "pending"; otherwise, it's set to "sending failed." After the first verification passes, the message sending account is identified as the key, and the message task record as the corresponding value, resulting in a message data structure, such as a map collection. Then, the message data structure for each message receiving account can be iterated through. If no un-visited message data structure exists, the bulk message update is considered complete, and a completion reminder is sent to the account follow-up person and the message sender. For each message receiving account's message data structure, a second request verification can be performed on the corresponding pending message. If it fails, the message sending status is updated to "sending failed," and a failure reason is generated (i.e., the reason the second verification failed). After the second verification passes, a message sending request can be constructed based on the message data structure to obtain the message sending instruction. Furthermore, the message sending status for each message receiving account can be set to "sending in progress" in batches. Simultaneously, multiple message sending commands are sent by calling the batch one-on-one chat API (Application Programming Interface). One one-on-one chat API corresponds to one message receiving account. The server then parses the API response, which indicates successful message sending. Next, the server can perform business processing as needed, such as storing the message in the database, for example, returning the response to the message sending account and recording it. Finally, the sending status of each message sending command can be updated to "sent successfully" in batches.

[0059] In one embodiment, such as Figure 8 and Figure 9 As shown, account managers can configure basic information on the message configuration page based on the message sending account. This basic information includes the content of the message sending request, such as the message content, the target audience (i.e., the message receiving accounts), and the sending mode. Then, as... Figure 3In the corresponding implementation, the configured content can be canceled, saved, or submitted. If the submission of the configuration content is triggered, the message content in the configuration content can be checked for sensitive words. If the check is successful, it enters the approval process. At the same time, the mass-sending task message (i.e., the message to be sent corresponding to the message sending request) can be displayed to the mass-sending list. At this time, the status of the mass-sending task message is "under review". In the above approval process, the reviewer can approve the mass-sending task message. The server's OA service can send the review callback to the server's basic service and IM service. The IM service can generate a one-to-one associated sending details, i.e., message sending instructions, based on the sending audience and account follow-up person, and set the message sending status to "pending sending". Then, before the formal sending, the message content is checked for sensitive words again, and it is determined whether the account manager's current permissions allow sending. If the sending verification fails, the message sending status is set to "sending failed", and the reason for the failure is recorded. If the verification passes, the batch one-on-one chat API is called to send in batches, and then business processing is performed based on the API response packet.

[0060] Figure 10 This is a schematic diagram of an information transmission device provided in an embodiment of this application. Figure 10 As shown, the information transmission device 1000 includes: In one embodiment, the request receiving module 1010 is used to receive a message sending request sent by a message sender based on a message sending account; the content determining module 1020 is used to obtain the message receiving account, the message content of the message to be sent, and the message sending mode based on the message sending request; the task generating module 1030 is used to generate a message task record corresponding to each message receiving account according to the message content, and each message task record includes a message to be sent; the time determining module 1040 is used to determine the message sending time according to the message sending mode; and the message sending module 1050 is used to send the message to be sent to the message receiving account corresponding to each message task record in response to the arrival of the message sending time.

[0061] For example, the first verification module 1060 is used to: perform a first request verification on the message sending request; the first request verification includes at least one of the following: verifying the uniqueness of the message name in the message content; verifying whether there are duplicate accounts in each message receiving account; verifying the message sending time indicated by the message sending mode; performing sensitive word verification on the message sending request; verifying the message sending permissions of the message sending account; and verifying whether the message sending request is a request corresponding to a new operation.

[0062] For example, the first verification module 1060 is specifically used to: query historical message sending records in response to a message sending request that is not a request corresponding to a new operation; update the historical message sending records according to the message sending request if there is a sending record corresponding to the message sending request in the historical message sending records; and add a historical message sending record to the message sending request in response to a message sending request that is a request corresponding to a new operation.

[0063] For example, the second verification module 1070 is used to: perform a second request verification on the message to be sent; the second request verification includes at least one of the following: verifying the message sending request for sensitive words; verifying the message sending permissions of the message sending account; verifying whether the message sending account exists in the message sending system; verifying whether each message receiving account has an account follower; verifying whether the message sending account has enabled the message mass sending function; verifying whether the message sending account has enabled pre-allocated message sending; verifying whether the message sending request has been sent; and verifying whether the message sending account is consistent with the account that sent the message sending request.

[0064] For example, the message sending module 1050 is specifically used to: determine the message sending account as a keyword, determine each message task record as the value corresponding to each keyword, and obtain the message data structure of the message receiving account corresponding to each message task record; generate a message sending instruction for each message receiving account according to each message data structure; and send the message to be sent to each message receiving account according to each message sending instruction.

[0065] For example, the message sending module 1050 is specifically used to: for each message receiving account, obtain at least one message receiving group based on at least one message receiving account belonging to the same customer follow-up account; and send the corresponding message to be sent to the message receiving accounts under the at least one message receiving group according to the message sending instruction, using each customer follow-up account as a different sending batch.

[0066] It should be understood that the device embodiments and method embodiments can correspond to each other, and similar descriptions can be referred to the method embodiments. To avoid repetition, further details will not be provided here. Specifically, Figure 10 The apparatus 1000 shown can execute the above-described method embodiments, and the aforementioned and other operations and / or functions of each module in the apparatus 1000 are respectively for implementing the corresponding processes in the above-described methods. For the sake of brevity, they will not be described in detail here.

[0067] The apparatus 1000 of this application embodiment has been described above from the perspective of functional modules in conjunction with the accompanying drawings. It should be understood that this functional module can be implemented in hardware, in software instructions, or in a combination of hardware and software modules. Specifically, the steps of the method embodiments in this application can be completed by integrated logic circuits in the processor's hardware and / or by software instructions. The steps of the method disclosed in this application embodiment can be directly embodied as being executed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. Optionally, the software module can be located in a mature storage medium in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps in the above method embodiments.

[0068] Figure 11 This is a schematic diagram of an electronic device provided in an embodiment of this application. (As shown...) Figure 11 As shown, the electronic device 1100 may include: The system includes a memory 1110 and a processor 1120. The memory 1110 stores computer programs and transfers the program code to the processor 1120. In other words, the processor 1120 can retrieve and run the computer program from the memory 1110 to implement the methods described in the embodiments of this application.

[0069] For example, the processor 1120 can be used to execute the above-described method embodiments according to instructions in the computer program.

[0070] In some embodiments of this application, the processor 1120 may include, but is not limited to: General-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.

[0071] In some embodiments of this application, the memory 1110 includes, but is not limited to: Volatile memory and / or non-volatile memory. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), and Direct Rambus RAM (DR RAM).

[0072] In some embodiments of this application, the computer program may be divided into one or more modules, which are stored in the memory 1110 and executed by the processor 1120 to complete the method provided in this application. The one or more modules may be a series of computer program instruction segments capable of performing specific functions, which describe the execution process of the computer program in the electronic device.

[0073] like Figure 11 As shown, the electronic device may also include: Transceiver 1130, which can be connected to processor 1120 or memory 1110.

[0074] The processor 1120 can control the transceiver 1130 to communicate with other devices; specifically, it can send information or data to other devices or receive information or data sent by other devices. The transceiver 1130 may include a transmitter and a receiver. The transceiver 1130 may further include antennas, and the number of antennas may be one or more.

[0075] It should be understood that the various components in the electronic device are connected through a bus system, which includes a data bus, a power bus, a control bus, and a status signal bus.

[0076] This application also provides a computer storage medium storing a computer program thereon, which, when executed by a computer, enables the computer to perform the methods of the above-described method embodiments. Alternatively, embodiments of this application also provide a computer program product containing instructions that, when executed by a computer, cause the computer to perform the methods of the above-described method embodiments.

[0077] When implemented using software, it can be implemented entirely or partially as a computer program product. This computer program product includes one or more computer instructions. When these computer program instructions are loaded and executed on a computer, the computer can perform all or part of the corresponding processes in the methods of the embodiments of this application, producing the functions achievable by the methods of the embodiments of this application. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital video discs (DVDs)), or semiconductor media (e.g., solid state disks (SSDs)).

[0078] Those skilled in the art will recognize that the modules and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0079] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple modules or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or modules may be electrical, mechanical, or other forms.

[0080] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical modules; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. For example, the functional modules in the various embodiments of this application may be integrated into one processing module, or each module may exist physically separately, or two or more modules may be integrated into one module.

[0081] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. An information transmission method, characterized in that, include: Receive message sending requests sent by message senders based on the message sending account; Based on the message sending request, obtain the message receiving account, the message content of the message to be sent, and the message sending mode; Based on the message content, a message task record is generated for each message receiving account, and each message task record includes the message to be sent. Determine the message sending time according to the message sending mode; In response to the arrival of the message sending time, the message to be sent is sent to the message receiving account corresponding to each message task record, based on each message task record.

2. The method according to claim 1, characterized in that, Before generating the message task record corresponding to each message receiving account based on the message content, the method further includes: The message sending request is subject to a first request verification; the first request verification includes at least one of the following: The uniqueness of the message name in the message content is verified; Verify whether there are duplicate accounts among each of the message receiving accounts; Verify the message sending time indicated by the message sending mode; Perform sensitive word verification on the message sending request; Verify the message sending permissions of the account that sent the message; Verify whether the message sending request is a request corresponding to a new operation.

3. The method according to claim 2, characterized in that, Also includes: In response to the message sending request not being a request corresponding to a new operation, query historical message sending records; If a sending record corresponding to the message sending request exists in the historical message sending record, then the historical message sending record is updated according to the message sending request; In response to the message sending request being a request corresponding to a new operation, the historical message sending record is added to the message sending request.

4. The method according to claim 1, characterized in that, Before sending the message to be sent to the message receiving account corresponding to each message task record, the method further includes: A second verification request is performed on the message to be sent; the second verification request includes at least one of the following: Perform sensitive word verification on the message sending request; Verify the message sending permissions of the account that sent the message; The system verifies whether the message sending account exists in the message sending system. Verify whether each message receiving account has an account follower; Verify whether the message sending account has enabled the group message sending function; Verify whether the message sending account has enabled pre-allocated message sending; Verify whether the message sending request has been sent; Verify whether the account that sent the message is the same as the account that sent the message sending request.

5. The method according to any one of claims 1-4, characterized in that, The step of sending the message to be sent to the message receiving account corresponding to each message task record, based on each message task record, includes: The message sending account is determined as a keyword, and each message task record is determined as a value corresponding to each keyword, so as to obtain the message data structure of the message receiving account corresponding to each message task record; Based on each of the message data structures, generate a message sending instruction for each of the message receiving accounts; According to each of the message sending instructions, the message to be sent is sent to each of the message receiving accounts respectively.

6. The method according to claim 5, characterized in that, The step of sending the message to be sent to each message receiving account according to each message sending instruction includes: For each of the aforementioned message receiving accounts, at least one message receiving group is obtained based on at least one message receiving account belonging to the same customer follow-up account; Using each of the aforementioned customer follow-up accounts as different sending batches, the corresponding messages to be sent are sent to the message receiving accounts under the at least one message receiving group according to the message sending instruction.

7. An information transmission device, characterized in that, include: The request receiving module is used to receive message sending requests sent by message senders based on their message sending accounts. The content determination module is used to obtain the message receiving account, the message content of the message to be sent, and the message sending mode based on the message sending request; The task generation module is used to generate a message task record corresponding to each message receiving account based on the message content, and each message task record includes the message to be sent; A time determination module is used to determine the message sending time according to the message sending mode; The message sending module is used to send the message to be sent to the message receiving account corresponding to each message task record in response to the arrival of the message sending time.

8. An electronic device, characterized in that, include: processor; as well as Memory for storing the executable instructions of the processor; The processor is configured to execute the method of any one of claims 1-6 by executing the executable instructions.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the method described in any one of claims 1-6.

10. A computer program product containing instructions, characterized in that, When the computer program product is run on an electronic device, the electronic device causes the electronic device to perform the method according to any one of claims 1-6.

Images