Data processing method and apparatus

Abstract

Embodiments of the present specification provide a data processing method and device, wherein the data processing method comprises: obtaining at least one to-be-sent short message and a receiving party corresponding to each to-be-sent short message; determining at least one to-be-processed short message corresponding to each receiving party according to the at least one to-be-sent short message and the receiving party of each to-be-sent short message; merging the at least one to-be-processed short message corresponding to each receiving party to obtain a target short message corresponding to each receiving party, and sending the target short message corresponding to each receiving party to the receiving party. This method can effectively avoid the problem that a user receives multiple short messages in a short period of time, optimize the user experience, reduce the carrier channel cost and platform processing burden, ensure the reach effect of short message information, and improve the overall efficiency of short message marketing.

Description

Technical Field

[0001] The embodiments in this specification relate to the field of computer technology, and in particular to a data processing method. Background Technology

[0002] With the development of mobile internet, SMS marketing has become an important means for businesses to reach users. During large-scale promotional events, multiple businesses often use the same SMS service platform to send marketing messages to their target user groups.

[0003] However, since different merchants' target user groups highly overlap, if they send text messages independently, a large number of users will receive multiple marketing text messages with similar content in a short period of time, which will not only affect the user experience, but also increase the operator's channel costs and the platform's processing burden. Summary of the Invention

[0004] In view of the above, embodiments of this specification provide a data processing method. One or more embodiments of this specification also relate to a data processing apparatus, a computing device, a computer-readable storage medium, and a computer program product, to address the technical deficiencies existing in the prior art.

[0005] According to a first aspect of the embodiments of this specification, a data processing method is provided, comprising: Obtain at least one SMS message to be sent and the corresponding recipient for each SMS message; Based on the at least one SMS message to be sent and the recipient of each SMS message to be sent, determine at least one SMS message to be processed corresponding to each recipient; The system merges at least one pending SMS message corresponding to each recipient to obtain the target SMS message corresponding to each recipient, and sends the target SMS message corresponding to each recipient to each recipient.

[0006] According to a second aspect of the embodiments of this specification, a data processing apparatus is provided, comprising: The acquisition module is configured to acquire at least one SMS message to be sent and the corresponding recipient of each SMS message to be sent. The determining module is configured to determine at least one pending SMS message corresponding to each recipient based on the at least one pending SMS message to be sent and the recipient of each pending SMS message; The sending module is configured to merge at least one pending SMS message corresponding to each recipient to obtain the target SMS message corresponding to each recipient, and send the target SMS message corresponding to each recipient to each recipient.

[0007] According to a third aspect of the embodiments of this specification, a computing device is provided, comprising: Memory and processor; The memory is used to store computer programs / instructions, and the processor is used to execute the computer programs / instructions, which, when executed by the processor, implement the steps of the above-described data processing method.

[0008] According to a fourth aspect of the embodiments of this specification, a computer-readable storage medium is provided that stores a computer program / instructions that, when executed by a processor, implement the steps of the data processing method described above.

[0009] According to a fifth aspect of the embodiments of this specification, a computer program product is provided, including a computer program / instructions that, when executed by a processor, implement the steps of the above-described data processing method.

[0010] This specification provides a data processing method in one embodiment, which obtains at least one SMS message to be sent and its corresponding recipient, then determines at least one SMS message to be processed for each recipient based on this information, and then merges the SMS messages to be processed for each recipient to generate a target SMS message for each recipient and sends it uniformly. This method can effectively avoid the problem of users receiving multiple SMS messages in a short period of time, optimize user experience, reduce operator channel costs and platform processing burden, ensure the delivery effect of SMS messages, and improve the overall efficiency of SMS marketing. Attached Figure Description

[0011] Figure 1 This is a schematic diagram illustrating a data processing method provided in one embodiment of this specification. Figure 2 This is a flowchart illustrating a data processing method provided in one embodiment of this specification; Figure 3 This is a schematic diagram of the processing procedure of a data processing method provided in one embodiment of this specification; Figure 4 This is a schematic diagram of the structure of a data processing apparatus provided in one embodiment of this specification; Figure 5 This is a structural block diagram of a computing device provided in one embodiment of this specification. Detailed Implementation

[0012] Many specific details are set forth in the following description to provide a full understanding of this specification. However, this specification can be implemented in many other ways than those described herein, and those skilled in the art can make similar extensions without departing from the spirit of this specification. Therefore, this specification is not limited to the specific implementations disclosed below.

[0013] The terminology used in one or more embodiments of this specification is for the purpose of describing particular embodiments only and is not intended to be limiting of the one or more embodiments of this specification. The singular forms “a,” “described,” and “the” as used in one or more embodiments of this specification and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used in one or more embodiments of this specification refers to and includes any or all possible combinations of one or more associated listed items.

[0014] It should be understood that although the terms first, second, etc., may be used to describe various information in one or more embodiments of this specification, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, first may also be referred to as second without departing from the scope of one or more embodiments of this specification, and similarly, second may also be referred to as first. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to a determination."

[0015] Furthermore, it should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in one or more embodiments of this specification are all information and data authorized by the user or fully authorized by all parties. Moreover, the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation entry points are provided for users to choose to authorize or refuse.

[0016] This specification provides a data processing method, and also relates to a data processing apparatus, a computing device, a computer-readable storage medium, and a computer program product, which will be described in detail in the following embodiments.

[0017] With the widespread adoption of mobile internet, SMS marketing has become a crucial means for businesses to reach users, especially during large-scale promotional events. Multiple businesses often use the same SMS service platform to send marketing messages to their target audience. However, because different businesses have highly overlapping target user groups, sending messages independently can easily lead to users repeatedly receiving similar messages within a short period. This not only severely impacts user experience, triggering complaints or unsubscriptions, but also wastes channel costs and system resources, and reduces marketing effectiveness due to information overload.

[0018] While existing "user deduplication" strategies can avoid receiving duplicate information, they often only retain information about a single merchant and cannot achieve the goal of reaching multiple merchants jointly.

[0019] This specification presents a data processing method that aims to both avoid repeatedly disturbing users and fully deliver SMS messages from multiple messages.

[0020] See Figure 1 , Figure 1 A schematic diagram of a data processing method according to an embodiment of this specification is shown. Specifically, the data processing method is applied to a data processing system, which includes a terminal device 102 of the SMS provider, an SMS service platform 104, and a terminal device 106 of the receiver. The terminal device 102 is used to send an SMS sending task to the SMS service platform 104. The SMS sending task includes the SMS to be sent and the corresponding receiver.

[0021] The SMS service platform 104 obtains at least one SMS message to be sent and the recipients corresponding to each SMS message; based on the at least one SMS message to be sent and the recipients of each SMS message to be sent, it determines at least one SMS message to be processed for each recipient; it merges the at least one SMS message to be processed for each recipient to obtain the target SMS message for each recipient, and sends the target SMS message for each recipient to each recipient; in fact, the target SMS message will be sent to the recipient's end device 106.

[0022] The edge device 102 may include a browser, an app (application), or a web application such as an H5 (Hypertext Markup Language 5) application, a lightweight application (also known as a mini-program), or a cloud application. The edge device can be developed based on a software development kit (SDK) provided by the server, such as a real-time communication (RTC) SDK. The edge device can be deployed in an electronic device and depends on the device's operation or certain apps within the device to run. The electronic device may have a display screen and support information browsing, such as a personal mobile terminal like a mobile phone, tablet, or personal computer. Various other types of applications can also be configured in the electronic device, such as human-computer interaction applications, model training applications, data processing applications, web browser applications, shopping applications, search applications, instant messaging tools, email clients, and social media platform software.

[0023] The SMS service platform 104 can be understood as a server providing various services, including physical servers and cloud servers. For example, it could be a server providing communication services to multiple clients, a server supporting the training of models used on clients, or a server processing data sent by clients. It should be noted that the SMS service platform 104 can be implemented as a distributed server cluster composed of multiple servers, or as a single server. The SMS service platform 104 can also be a server for a distributed system, or a server integrated with blockchain. Furthermore, the SMS service platform 104 can be a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDNs), and big data and artificial intelligence platforms, or an intelligent cloud computing server or intelligent cloud host with artificial intelligence technology.

[0024] See Figure 2 , Figure 2 A flowchart of a data processing method provided in one embodiment of this specification is shown, which specifically includes the following steps.

[0025] Step 202: Obtain at least one SMS message to be sent and the corresponding recipient for each SMS message.

[0026] In this context, a text message to be sent can be understood as a text message prepared to be pushed to the recipient. Text messages usually contain promotional content, notification information, or advertising copy. The recipient can be understood as the target user who receives the text message, and is usually identified by a phone number.

[0027] Specifically, at least one text message to be sent is collected, and the recipient of each text message to be sent is determined, so that the aggregation processing can be performed on the case where one recipient corresponds to multiple text messages to be sent, thereby reducing the disturbance to the recipient.

[0028] In practice, the SMS provider submits SMS sending tasks, which also specify the recipients of the SMS messages. Upon receiving at least one SMS sending task, at least one SMS message and its recipients can be determined based on that task. The specific implementation method is as follows: Obtain at least one SMS message to be sent and the corresponding recipient for each SMS message, including: Receive SMS sending task submitted by at least one SMS provider, wherein the SMS sending task carries the SMS to be sent and the recipient; Based on at least one SMS sending task, collect SMS messages to be sent from each SMS provider, obtain the at least one SMS message to be sent, and determine the recipient of each SMS message to be sent.

[0029] The SMS provider can be understood as the entity that initiates the SMS sending task, usually a merchant, service provider, or marketing platform; the SMS sending task can be understood as a sending instruction initiated by the SMS provider, which includes the SMS to be sent and a list of target users.

[0030] Specifically, the system receives SMS sending tasks submitted by different SMS providers. Each task specifies the content to be sent and the corresponding target user list. By aggregating these tasks, the system collects the SMS messages to be sent from each provider and records the recipient for each message, thus obtaining at least one SMS message to be sent and its corresponding recipient.

[0031] For example, Merchant A submits an SMS sending task containing promotional information for children's cold medicine and a corresponding target user list (e.g., 1 million phone numbers); Merchant B also submits an SMS sending task containing promotional information for medical devices and a corresponding target user list (e.g., 800,000 phone numbers). Upon receiving these two SMS sending tasks, two SMS messages to be sent and their corresponding 1.8 million phone numbers are collected.

[0032] In practical applications, when submitting SMS sending tasks, SMS providers can also specify the planned sending time for the SMS messages to be sent, such as a planned sending time for an SMS message at 10:00 AM on January 1, 2023. In the embodiments of this specification, when collecting and processing SMS sending tasks, the SMS sending tasks will be classified and batched according to the planned sending time. That is, the system will aggregate all SMS sending tasks that are scheduled to be sent at the same future time (i.e., the planned sending time) together and process and send them as a batch. Based on this, at least one SMS message to be sent will correspond to the same planned sending time, which also lays the data foundation for subsequent SMS merging, ensuring that only the SMS content is merged, without changing the recipient or the planned sending time.

[0033] The data processing method provided in the embodiments of this specification achieves the collection of at least one SMS message to be sent by centrally receiving and summarizing SMS sending tasks from multiple SMS providers, thus providing a data foundation for subsequent processing.

[0034] Step 204: Based on the at least one SMS message to be sent and the recipient of each SMS message to be sent, determine at least one SMS message to be processed corresponding to each recipient.

[0035] In this context, at least one pending SMS message for each recipient can be understood as a set of pending SMS messages formed by aggregating the content of all pending SMS messages associated with each recipient. This set may contain one or more SMS messages from different SMS providers.

[0036] Specifically, after obtaining at least one text message to be sent and the recipient of each text message to be sent, the data is further reorganized around the recipient, that is, all text messages to be sent associated with the same recipient are aggregated to form a set of text messages to be processed corresponding to each recipient (i.e., at least one text message to be processed corresponding to each recipient).

[0037] For example, during a promotional event, merchant A sends a promotional text message t1 about children's cold medicine to user U1, and merchant B sends a promotional text message t2 about medical devices to the same user U1. Therefore, based on the collected promotional text message t1, promotional text message t2, and recipient information (the recipient is user U1 in both cases), promotional text message t1 and promotional text message t2 are identified as the two pending text messages for user U1.

[0038] In one or more embodiments of this specification, since the recipients of different SMS messages to be sent may overlap, by acquiring at least one SMS sending task and collecting at least one SMS message to be sent and its corresponding recipient, an initial recipient set is determined based on at least one recipient, and a target recipient set containing unique recipients is obtained through deduplication. Specific implementation methods are described below: Based on the at least one SMS message to be sent and the recipient of each SMS message to be sent, determine at least one SMS message to be processed corresponding to each recipient, including: Based on the at least one SMS message to be sent and the recipients of each SMS message to be sent, an initial set of recipients is obtained; The initial receiver set is deduplicated to obtain the target receiver set; Identify at least one unprocessed SMS message corresponding to each recipient in the target recipient set.

[0039] The initial recipient set can be understood as an original set formed based on the recipient identifiers corresponding to at least one SMS message to be sent, which may contain duplicate recipients. The target recipient set can be understood as a unique set of recipients obtained after deduplication of the initial recipient set, where each recipient appears once. Deduplication can be understood as the process of identifying and merging duplicate records in a dataset. In the embodiments of this specification, deduplication refers to the operation of removing duplicate recipients from the initial recipient set based on the recipient identifier.

[0040] Specifically, based on all SMS messages to be sent, obtain all corresponding recipients to form an initial recipient set that may contain duplicates; perform a deduplication operation on this initial recipient set to eliminate duplicate recipient identifiers and obtain a unique target recipient set; for each recipient in the target recipient set, collect all SMS messages to be sent associated with that recipient according to the original correspondence between SMS messages to be sent and recipients, forming its corresponding set of SMS messages to be processed.

[0041] For example, Merchant A plans to send SMS messages to users U1, U2, and U3, while Merchant B plans to send SMS messages to users U2, U3, and U4. The process involves obtaining all recipient information to get an initial recipient set {U1, U2, U3, U2, U3, U4}; after deduplication, a target recipient set {U1, U2, U3, U4} is obtained; for each recipient in this target recipient set, at least one SMS message to be processed is identified, i.e., user U1 corresponds to one SMS message from Merchant A, user U2 corresponds to two SMS messages from both Merchant A and Merchant B, user U3 corresponds to two SMS messages from both Merchant A and Merchant B, and user U4 corresponds to one SMS message from Merchant B.

[0042] The data processing method provided in the embodiments of this specification obtains a target recipient set containing unique recipients by first collecting and then deduplicating data. Then, for each recipient in the target recipient set, all the text messages to be processed associated with them are determined. This realizes data integration and organization at the recipient level, providing a data foundation for text message processing at the user level.

[0043] Step 206: Merge at least one pending SMS message corresponding to each recipient to obtain the target SMS message corresponding to each recipient, and send the target SMS message corresponding to each recipient to each recipient.

[0044] In this context, at least one pending SMS message can be understood as one or more SMS messages to be sent, initiated by the same or different SMS providers and addressed to the same recipient. Merging can be understood as the process of integrating the SMS messages from at least one pending SMS message into a single, coherent, and complete SMS message through redundancy removal and structured arrangement. The target SMS message can be understood as the SMS message content that is finally generated after merging and prepared to be sent to the recipient, which may contain the core information of the original multiple pending SMS messages.

[0045] Specifically, for each recipient, upon receiving at least one pending SMS message, these pending SMS messages are merged into a single target SMS message through processes such as content redundancy removal, information structure reorganization, and length adaptation. It should be noted that if a recipient has only one pending SMS message, that pending SMS message is directly used as the target SMS message, and the target SMS messages corresponding to each recipient are sent to the terminal devices corresponding to each recipient (i.e., the end-side devices of the recipients mentioned above) through the SMS sending channel.

[0046] For example, the pending SMS messages for user U2 include SMS t1 from merchant A and SMS t2 from merchant B. SMS t1 and SMS t2 are merged to obtain a target SMS t3, and finally this merged target SMS t3 is sent to user U2.

[0047] By merging at least one pending SMS message from the same recipient to generate a structured target SMS message and sending it, the core information of multiple SMS messages can be retained while reducing the number of SMS messages sent. This effectively reduces the frequency of user reception and saves channel costs and system resources.

[0048] In one or more embodiments of this specification, if the number of text messages to be processed for a certain recipient exceeds a preset value, the recipient is identified as a duplicate recipient, and the text messages to be processed for the duplicate recipient are merged. Specific implementation methods are as follows: Merging at least one pending SMS message corresponding to each recipient to obtain the target SMS message corresponding to each recipient includes: Determine the number of pending SMS messages for any given recipient; If the number of pending SMS messages exceeds a preset value, the corresponding recipient will be identified as a duplicate recipient; otherwise, the corresponding recipient will be identified as a single recipient. The pending SMS message corresponding to a single recipient is identified as the target SMS message; Merge at least two pending SMS messages corresponding to duplicate recipients to obtain the target SMS message corresponding to the duplicate recipient.

[0049] The preset value can be understood as a pre-defined threshold used to determine whether a recipient is a duplicate recipient. In this embodiment, the preset value is 1. A duplicate recipient can be understood as a recipient that is listed as a target user in multiple SMS sending tasks, meaning that the number of SMS messages to be processed for a recipient exceeds one. In other words, a duplicate recipient corresponds to at least two SMS messages to be processed, which may come from different SMS providers or multiple SMS sending tasks from the same SMS provider. A single recipient can be understood as a recipient associated with only one SMS message to be processed.

[0050] Specifically, for each recipient, the number of text messages to be processed is counted; the number of text messages is compared with a preset value. If the number of text messages exceeds the preset value, the recipient is marked as a duplicate recipient; otherwise, it is marked as a single recipient. In this embodiment, the preset value is 1, that is, if the number of text messages exceeds 1, the recipient is marked as a duplicate recipient.

[0051] For a single recipient, their unique pending SMS message is directly used as the target SMS message without merging. For multiple recipients, at least two pending SMS messages need to be merged to generate a merged target SMS message.

[0052] For example, if the preset value is 1, and user U1 only associates with one SMS message from merchant A, then user U1 is determined to be a single recipient, and the corresponding SMS message from merchant A is directly used as the target SMS message; if user U2 associates with two SMS messages from both merchant A and merchant B, the number of SMS messages is 2 (exceeding the preset value), then user U2 is determined to be a duplicate recipient, and these two SMS messages need to be merged to generate a merged target SMS message.

[0053] The data processing method provided in the embodiments of this specification determines the repetition of recipients based on the number of associated SMS messages to be processed, realizes differentiated processing for single recipients and duplicate recipients, performs SMS merging for duplicate recipients that need to be merged, and ensures data processing efficiency.

[0054] In one or more embodiments of this specification, when merging at least two unprocessed SMS messages, redundant content in each unprocessed SMS message is removed, and the messages are organized using a preset merging module to form a highly readable target SMS message. Specific implementation methods are described below: Merge at least two pending SMS messages corresponding to duplicate recipients to obtain the target SMS message corresponding to the duplicate recipient, including: For at least two pending SMS messages corresponding to duplicate recipients, redundant content in each pending SMS message is removed to obtain the target content of each pending SMS message. Each pending SMS message is generated through a preset SMS message template, and the redundant content includes the general template content in the preset SMS message template. The target content of each SMS message to be processed is organized according to a preset merging template to obtain the target SMS messages of the duplicate recipients. The preset merging template includes a parallel format template or a segmented format template.

[0055] The preset SMS template can be understood as the content structure framework followed by the SMS provider when generating SMS messages. It typically includes fixed template statements (i.e., general template content) and variable information fill-in sections. Redundant content can be understood as text that appears repeatedly in each SMS message without affecting the core message delivery. This is usually fixed template statements within the preset SMS template, such as fixed beginnings and endings of SMS messages, or formatted statements in marketing templates. Target content can be understood as the core information retained after removing redundant content from each SMS message. This is typically the content filled in by the SMS provider in the variable information fill-in section, such as product names, prices, discount conditions, and links.

[0056] A preset merge template can be understood as a pre-built arrangement template used to organize multiple target contents into a structured text message. Common forms include horizontal parallel format (such as using "|" to separate) and vertical segmented format (such as using line breaks to separate).

[0057] Specifically, for at least two pending SMS messages corresponding to duplicate recipients, the common template content generated by the preset SMS template is extracted from each pending SMS message. The common template content is removed as redundant content, and the retained content is used as the target content of each pending SMS message, which usually contains the core information of the pending SMS message. The target content of the at least two pending SMS messages is organized and arranged according to the preset merging template to generate a target SMS message with a clear structure and complete information, thereby completing the aggregation from multiple SMS messages to a single merged SMS message.

[0058] For example, two pending text messages from duplicate recipient U2 are from merchant A and merchant B respectively. Both pending text messages contain the general template statement "Consult official customer service, beware of fraud, please reply R to refuse." After removing redundant content from each pending text message, the target content of text message t1 corresponding to merchant A is extracted, which includes "Children's cold medicine oral liquid as low as 28 / box > jk.page1", and the target content of text message t2 corresponding to merchant B is "Buy 3 get 1 free on promotional day, limited to 200 people! Plus subsidy 114.3 / box > jk.page2". Then, the two target contents are organized according to a preset merging template. For example, in this embodiment, the target text message is generated using a parallel format template as "[Health Platform] Children's cold medicine oral liquid as low as 28 / box > jk.page1 | Buy 3 get 1 free on promotional day, limited to 200 people! Plus subsidy 114.3 / box > jk.page2, consult official customer service, beware of fraud, please reply R to refuse."

[0059] The data processing method provided in this specification removes redundancy and merges multiple unprocessed SMS messages from duplicate recipients using templates. This reduces the length of the content without affecting readability while retaining the core information of the multiple unprocessed SMS messages. The structured target information can enhance the user's information acquisition efficiency, reduce sending costs, and improve the overall reach and user experience.

[0060] In one or more embodiments of this specification, when organizing multiple target contents according to a preset merging template, it is necessary to determine the arrangement order of the target contents, and then organize the multiple target contents according to the arrangement order to generate a target SMS message. Specific implementation methods are described below: The target content of each unprocessed SMS message is organized according to a preset merging template to obtain the target SMS messages from duplicate recipients, including: Determine the SMS attribute information of each SMS to be processed, and determine the order of each SMS to be processed according to the attribute priority rules; According to the arrangement order, the target content of each SMS message to be processed is organized according to the preset merging template to obtain the target SMS messages of duplicate recipients.

[0061] The SMS attribute information can be understood as information describing the characteristics of the SMS message, including but not limited to the sending time, the type of merchant sending the message, and the SMS category. The attribute priority rules can be understood as rules used to sort the SMS messages to be processed, such as sorting by sending time, merchant type priority, user preference, or marketing campaign level. The sorting order can be understood as the order in which multiple target messages are sorted according to the attribute priority rules, used to determine the presentation order of these target messages in the merged target SMS messages. The preset merging template is a structural framework for organizing SMS content. This template can be dynamically adjusted according to the type of SMS provider (e.g., e-commerce, service notifications), SMS field (e.g., health, apparel), or user personalized preferences; no limitations are imposed here.

[0062] Specifically, the SMS attribute information of each SMS to be processed is extracted. Based on preset attribute priority rules (such as time priority rules, SMS category priority rules, user preference priority rules, etc.), the order of these target contents in the merged SMS is determined. Then, the target contents are filled into the preset merge template according to the order of arrangement to generate the final target SMS.

[0063] For example, two pending SMS messages for recipient U2 are sent from merchant A (category "Pharmaceuticals", sent at 10:00 AM) and merchant B (category "Medical Devices", sent at 10:05 AM). Based on the priority rule of "sent time", the target content for merchant A is arranged first, followed by the target content for merchant B. Furthermore, the horizontal parallel format template can be dynamically selected based on the SMS provider type (both are health-related), ultimately generating the target SMS message as "[Health Platform] Target content for merchant A | Target content for merchant B".

[0064] The data processing method provided in this specification, through prioritizing SMS attribute information and combining it with dynamic template organization, achieves intelligent arrangement and personalized presentation of merged SMS content. This step not only makes the merged information structure more in line with user reading habits and improves information acquisition efficiency, but also dynamically adjusts the content order and format according to project needs and user preferences, further optimizing user experience and enhancing the accuracy and overall effectiveness of joint marketing.

[0065] In one or more embodiments of this specification, the SMS messages to be processed are first sorted according to their sending time to obtain an initial sorting order. If the sending times are the same, the initial sorting order is then adjusted according to category priority to obtain the final sorting order of the SMS messages to be processed. Specific implementation methods are described below: Determine the SMS attribute information of each SMS message to be processed, and determine the order of the SMS messages to be processed according to the attribute priority rules, including: The sending time of each pending SMS message is determined, and the pending SMS messages are sorted according to the time priority in the attribute priority rules to obtain the initial sorting order. If at least two pending SMS messages have the same sending time, determine the object type of at least two pending SMS messages, and sort the at least two pending SMS messages in the initial sorting order according to the type priority in the attribute priority rule, so as to obtain the sorting order of each pending SMS message.

[0066] Here, "sending time" can be understood as the time parameter when the SMS provider submits the SMS sending task, used to control the sending sequence of SMS messages. "Time priority" can be understood as the rule in the attribute priority rules that prioritizes sending time. "Object type" can be understood as the category to which the SMS provider or SMS content belongs, such as merchant type (e.g., e-commerce, service provider), industry category (e.g., pharmaceuticals, apparel), or marketing nature (e.g., promotion, notification), etc., without further limitation. "Type priority" can be understood as the rule that prioritizes object types according to their importance when sending times are the same. "Initial arrangement order" can be understood as the order obtained after preliminary sorting based on time priority; this initial arrangement order needs further adjustment if there are cases of the same sending time.

[0067] Specifically, the sending time of each pending SMS message is obtained, and they are initially sorted according to the order of time to generate an initial sorting order. If there are multiple pending SMS messages with the same sending time, the object type of these pending SMS messages with the same sending time is further identified, and they are sorted a second time according to the preset type priority rules (such as according to the importance of merchant type, industry priority, etc.) to obtain the final sorting order.

[0068] For example, receiver U2 has three pending SMS messages: SMS A (sent at 10:00, object type "medicine"), SMS B (sent at 10:00, object type "medical device"), and SMS C (sent at 10:05). First, they are sorted by time priority, with SMS A and B (sent at the same time) ranked first, and SMS C ranked last, resulting in the initial order [A, B, C]. Since SMS A and B have the same time, they are further sorted according to type priority rules (assuming "medicine" has higher priority than "medical device"), resulting in the final order [A, B, C].

[0069] The data processing method provided in this specification employs a dual sorting approach based on the priority of sending time and object type, ensuring the rationality and adaptability of the content order when merging multiple SMS messages. This step not only guarantees the timely presentation of time-sensitive information but also maintains the order of content importance through type priority when time conflicts occur. Consequently, the merged SMS message has a clear structure and is well-organized, improving the user's reading experience and information acquisition efficiency, and enhancing the practical effectiveness of merging and sending multi-source SMS messages.

[0070] In one or more embodiments described herein, upon receiving a target SMS message, the recipient can interact with the message content to obtain feedback information, which is then returned to the corresponding SMS provider. Specific implementation details are as follows: After sending the target SMS message corresponding to each recipient to each recipient, the process also includes: In response to the recipient's interactive behavior on the target SMS content in the target SMS, feedback information corresponding to the target SMS content is obtained, wherein the target SMS content comes from at least one unprocessed SMS contained in the target SMS; The feedback information is returned to the SMS provider corresponding to the target SMS content.

[0071] Interactive behavior can be understood as the actions performed by the recipient on the received target SMS content, including but not limited to clicking links, redirecting to a specified page, or making a purchase. Target SMS content can be understood as specific information fragments contained within the target SMS, originating from the SMS to be processed, such as promotional information or links from a merchant. Feedback information can be understood as data generated based on the recipient's interactive behavior, which can be used to evaluate the effectiveness of the SMS, such as conversion records and behavior paths.

[0072] Specifically, after the target SMS is sent, the system can monitor the recipient's interaction with the specific content of the target SMS. When an interaction occurs, the system can identify the target SMS content corresponding to that interaction, collect relevant behavioral data to form feedback information, and send this feedback information to the corresponding original SMS provider. This allows the SMS provider to perform actions such as attribution based on the feedback information.

[0073] For example, user U2 receives a merged target SMS message containing links to pending SMS message A (from merchant a) and pending SMS message B (from merchant b). If user U2 clicks the link in pending SMS message A, the click is recorded, feedback information (such as click time, user ID, and source link) is generated, and this feedback information is returned to merchant a. If the user subsequently completes a purchase through this link, the purchase conversion information is further fed back to merchant a to help the merchant evaluate the marketing effectiveness.

[0074] The data processing method provided in the embodiments of this specification tracks user interaction behavior after the target SMS is sent and returns feedback information to the corresponding SMS provider, thereby enabling independent effect evaluation of the content from each source in the target SMS. This allows each SMS provider to accurately obtain the reach and conversion effect of its own marketing content, providing data support for subsequent optimization of marketing strategies and adjustment of sent content.

[0075] See Figure 3 , Figure 3 A schematic diagram of the processing procedure of a data processing method provided in one embodiment of this specification is shown.

[0076] The system receives SMS sending tasks submitted by multiple merchants. Each task contains a list of target users (i.e., recipients) and SMS messages to be sent. It collects the SMS messages to be sent from these multiple tasks, obtaining an initial set of recipients consisting of all target users. By deduplicating all target users, it generates a unique set of users (i.e., the target recipient set), and records the set of SMS messages to be processed associated with each user (containing at least one SMS message to be processed).

[0077] For users who have two or more pending SMS messages associated with them, they are identified as duplicate users (i.e., duplicate recipients in the above embodiments), and the multiple pending SMS messages associated with them are merged. For duplicate users, the SMS content of all pending SMS messages associated with them is obtained, and a structured merged SMS message (i.e., target SMS message) is generated through intelligent fusion processing. The merged target SMS message is sent to the duplicate user, while non-duplicate users (i.e., single recipients in the above embodiments) are sent normally with the original content.

[0078] The specific intelligent fusion processing includes removing common template phrases from each SMS message (such as "Dear user", "Click the link", "Reply R to refuse", etc.) and retaining the core information; organizing the retained core information according to a preset merging template (such as parallel or segmented format).

[0079] It should be noted that the target SMS message can be optimized in the embodiments of this specification to ensure that it meets the SMS message character limit (e.g., 70 Chinese characters), thereby reducing the number of messages sent while controlling costs. If the content of the merged SMS message exceeds the character limit of a single SMS message, the actual number of messages will be charged. However, if the content of the SMS messages from the three merchants is merged and the length of the target SMS message is 140 Chinese characters (corresponding to the character count of 2 SMS messages), then the cost of one SMS message can be saved.

[0080] In the embodiments of this specification, the preset merging template can be dynamically adjusted according to the merchant type, industry attributes, or user preferences to improve the relevance and readability of information presentation. For example, merchants in the same category (such as e-commerce) adopt a horizontal parallel format, while merchants across categories (such as e-commerce and service notifications) adopt a segmented layout.

[0081] In addition, the system can record user interactions such as clicks and conversions on merged SMS messages and return the corresponding feedback information to the relevant merchants.

[0082] To facilitate understanding, the following example illustrates the method in detail: Assume that Merchant A (a pharmaceutical company) and Merchant B (a medical device company) both plan to send SMS messages to 1 million users during a promotional period. After deduplication, there are 1.5 million unique users, of which 500,000 are overlapping users. For these 500,000 overlapping users, the system extracts Merchant A's message "[Health Platform] Children's cold medicine oral liquid as low as 28 / box > jk.page1, consult official customer service, beware of fraud, please reply R to refuse delivery," and Merchant B's message "[Health Platform] Buy 3 get 1 free on promotional day, limited to 200 people! Plus subsidy 114.3 / box > jk.page2, consult official customer service, beware of fraud, please reply R to refuse delivery."

[0083] After removing generic template statements, the merged SMS message, using the preset template, reads: "【Health Platform】Children's Cold Medicine Oral Liquid as low as 28 / box > jk.page1 | Buy 3 Get 1 Free on Activity Day (Limited to 200 Customers! Subsidy 114.3 / box > jk.page2, Contact official customer service, beware of scams, reply R to refuse delivery." This merged SMS message contains two core messages, allowing users to receive both merchants' promotional information in a single message, reducing inconvenience and increasing information reach. Compared to sending individual messages, the merged SMS message is more focused, easier for users to find, and if the user has content they are interested in, it will also expose other merchants' content, increasing conversion rates.

[0084] The data processing method provided in this specification reduces the number of repeated SMS messages received by a user from multiple messages to a single merged SMS message containing the content of multiple messages. This effectively reduces the frequency of user disturbance and the complaint rate. Furthermore, by merging SMS messages, the core information of multiple merchant SMS messages can be retained, maximizing the value of joint marketing. By reducing the total number of messages sent, not only can channel costs and system load be reduced, but information readability is also improved through structured presentation. In fact, the configurable preset merging template supports flexible scenario expansion and can be applied to different industries and marketing scenarios.

[0085] This data processing method can ensure the effectiveness of SMS user outreach while reducing the frequency with which users receive SMS messages from the same SMS service platform. It improves user experience, reduces the risk of complaints, and further optimizes the quality of marketing content delivery on the platform, effectively improving SMS conversion efficiency.

[0086] Corresponding to the above method embodiments, this specification also provides data processing apparatus embodiments. Figure 4 A schematic diagram of the structure of a data processing apparatus according to one embodiment of this specification is shown. Figure 4 As shown, the device includes: The acquisition module 402 is configured to acquire at least one SMS message to be sent and the recipient corresponding to each SMS message to be sent. The determining module 404 is configured to determine at least one pending SMS message corresponding to each recipient based on the at least one pending SMS message to be sent and the recipient of each pending SMS message; The sending module 406 is configured to merge at least one pending SMS message corresponding to each recipient to obtain the target SMS message corresponding to each recipient, and send the target SMS message corresponding to each recipient to each recipient.

[0087] Optionally, the acquisition module 402 is further configured to: Receive SMS sending task submitted by at least one SMS provider, wherein the SMS sending task carries the SMS to be sent and the recipient; Based on at least one SMS sending task, collect SMS messages to be sent from each SMS provider, obtain the at least one SMS message to be sent, and determine the recipient of each SMS message to be sent.

[0088] Optionally, the determining module 404 is further configured to: Based on the at least one SMS message to be sent and the recipients of each SMS message to be sent, an initial set of recipients is obtained; The initial receiver set is deduplicated to obtain the target receiver set; Identify at least one unprocessed SMS message corresponding to each recipient in the target recipient set.

[0089] Optionally, the sending module 406 is further configured to: Determine the number of pending SMS messages for any given recipient; If the number of pending SMS messages exceeds a preset value, the corresponding recipient will be identified as a duplicate recipient; otherwise, the corresponding recipient will be identified as a single recipient. The pending SMS message corresponding to a single recipient is identified as the target SMS message; Merge at least two pending SMS messages corresponding to duplicate recipients to obtain the target SMS message corresponding to the duplicate recipient.

[0090] Optionally, the sending module 406 is further configured to: For at least two pending SMS messages corresponding to duplicate recipients, redundant content in each pending SMS message is removed to obtain the target content of each pending SMS message. Each pending SMS message is generated through a preset SMS message template, and the redundant content includes the general template content in the preset SMS message template. The target content of each SMS message to be processed is organized according to a preset merging template to obtain the target SMS messages of the duplicate recipients. The preset merging template includes a parallel format template or a segmented format template.

[0091] Optionally, the sending module 406 is further configured to: Determine the SMS attribute information of each SMS to be processed, and determine the order of each SMS to be processed according to the attribute priority rules; According to the arrangement order, the target content of each SMS message to be processed is organized according to the preset merging template to obtain the target SMS messages of duplicate recipients.

[0092] Optionally, the sending module 406 is further configured to: The sending time of each pending SMS message is determined, and the pending SMS messages are sorted according to the time priority in the attribute priority rules to obtain the initial sorting order. If at least two pending SMS messages have the same sending time, determine the object type of at least two pending SMS messages, and sort the at least two pending SMS messages in the initial sorting order according to the type priority in the attribute priority rule, so as to obtain the sorting order of each pending SMS message.

[0093] The device further includes: The feedback module is configured to respond to the recipient's interactive behavior on the target SMS content in the target SMS, obtain feedback information corresponding to the target SMS content, wherein the target SMS content comes from at least one pending SMS contained in the target SMS; and return the feedback information to the SMS provider corresponding to the target SMS content.

[0094] The above is an illustrative scheme of a data processing apparatus according to this embodiment. It should be noted that the technical solution of this data processing apparatus and the technical solution of the data processing method described above belong to the same concept. For details not described in detail in the technical solution of the data processing apparatus, please refer to the description of the technical solution of the data processing method described above.

[0095] Figure 5 A structural block diagram of a computing device 500 according to one embodiment of this specification is shown. The components of the computing device 500 include, but are not limited to, a memory 510 and a processor 520. The processor 520 is connected to the memory 510 via a bus 530, and a database 550 is used to store data.

[0096] The computing device 500 also includes an access device 540, which enables the computing device 500 to communicate via one or more networks 560. Examples of these networks include Public Switched Telephone Network (PSTN), Local Area Network (LAN), Wide Area Network (WAN), Personal Area Network (PAN), or combinations of communication networks such as the Internet. The access device 540 may include one or more of any type of wired or wireless network interface (e.g., a network interface card (NIC)), such as an IEEE 802.11 Wireless Local Area Network (WLAN) wireless interface, a Wi-MAX (Worldwide Interoperability for Microwave Access) interface, an Ethernet interface, a Universal Serial Bus (USB) interface, a cellular network interface, a Bluetooth interface, or a Near Field Communication (NFC) interface.

[0097] In one embodiment of this specification, the above-described components of the computing device 500 and Figure 5 Other components, not shown, can also be connected to each other, for example, via a bus. It should be understood that... Figure 5 The block diagram of the computing device shown is for illustrative purposes only and is not intended to limit the scope of this specification. Those skilled in the art can add or replace other components as needed.

[0098] The computing device 500 can be any type of stationary or mobile computing device, including mobile computers or mobile computing devices (e.g., tablet computers, personal digital assistants, laptop computers, notebook computers, netbooks, etc.), mobile phones (e.g., smartphones), wearable computing devices (e.g., smartwatches, smart glasses, etc.) or other types of mobile devices, or stationary computing devices such as desktop computers or personal computers (PCs). The computing device 500 can also be a mobile or stationary server.

[0099] The processor 520 is used to execute the following computer program / instructions, which, when executed by the processor, implement the steps of the above-described data processing method.

[0100] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the computing device embodiments are basically similar to the data processing method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions of the data processing method embodiments.

[0101] An embodiment of this specification also provides a computer-readable storage medium storing a computer program / instructions that, when executed by a processor, implement the steps of the above-described data processing method.

[0102] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the computer-readable storage medium embodiments are basically similar to the data processing method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions of the data processing method embodiments.

[0103] An embodiment of this specification also provides a computer program product, including a computer program / instructions that, when executed by a processor, implement the steps of the above-described data processing method.

[0104] The above is an illustrative scheme of a computer program product according to this embodiment. It should be noted that the technical solution of this computer program product and the technical solution of the data processing method described above belong to the same concept. For details not described in detail in the technical solution of the computer program product, please refer to the description of the technical solution of the data processing method described above.

[0105] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0106] The computer instructions include computer program code, which may be in the form of source code, object code, executable file, or certain intermediate forms. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording media, USB flash drive, portable hard drive, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunication signals, and software distribution media, etc. It should be noted that the content included in the computer-readable medium may be appropriately added or removed according to the requirements of patent practice. For example, in some regions, according to patent practice, computer-readable media may not include electrical carrier signals and telecommunication signals.

[0107] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that the embodiments in this specification are not limited to the described order of actions, because according to the embodiments in this specification, some steps can be performed in other orders or simultaneously. Furthermore, those skilled in the art should also understand that the embodiments described in this specification are all preferred embodiments, and the actions and modules involved are not necessarily essential to the embodiments in this specification.

[0108] In the above embodiments, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0109] The preferred embodiments disclosed above are merely illustrative of this specification. The optional embodiments do not exhaustively describe all details, nor do they limit the invention to the specific implementations described. Clearly, many modifications and variations can be made based on the embodiments described herein. These embodiments are selected and specifically described in this specification to better explain the principles and practical applications of the embodiments, thereby enabling those skilled in the art to better understand and utilize this specification. This specification is limited only by the claims and their full scope and equivalents.

Claims

1. A data processing method, comprising: Obtain at least one SMS message to be sent and the corresponding recipient for each SMS message; Based on the at least one SMS message to be sent and the recipient of each SMS message to be sent, determine at least one SMS message to be processed corresponding to each recipient; The system merges at least one pending SMS message corresponding to each recipient to obtain the target SMS message corresponding to each recipient, and sends the target SMS message corresponding to each recipient to each recipient.

2. The method as described in claim 1, wherein obtaining at least one SMS message to be sent and the recipient corresponding to each SMS message to be sent includes: Receive SMS sending task submitted by at least one SMS provider, wherein the SMS sending task carries the SMS to be sent and the recipient; Based on at least one SMS sending task, collect SMS messages to be sent from each SMS provider, obtain the at least one SMS message to be sent, and determine the recipient of each SMS message to be sent.

3. The method as described in claim 1, wherein determining at least one pending text message corresponding to each recipient based on the at least one pending text message to be sent and the recipient of each pending text message to be sent includes: Based on the at least one SMS message to be sent and the recipients of each SMS message to be sent, an initial set of recipients is obtained; The initial receiver set is deduplicated to obtain the target receiver set; Identify at least one unprocessed SMS message corresponding to each recipient in the target recipient set.

4. The method as described in claim 1, wherein at least one pending SMS message corresponding to each recipient is merged to obtain a target SMS message corresponding to each recipient, comprising: Determine the number of pending SMS messages for any given recipient; If the number of pending SMS messages exceeds a preset value, the corresponding recipient will be identified as a duplicate recipient; otherwise, the corresponding recipient will be identified as a single recipient. The pending SMS message corresponding to a single recipient is identified as the target SMS message; Merge at least two pending SMS messages corresponding to duplicate recipients to obtain the target SMS message corresponding to the duplicate recipient.

5. The method as described in claim 4, wherein merging at least two pending SMS messages corresponding to duplicate recipients to obtain a target SMS message corresponding to the duplicate recipient, includes: For at least two pending SMS messages corresponding to duplicate recipients, redundant content in each pending SMS message is removed to obtain the target content of each pending SMS message. Each pending SMS message is generated through a preset SMS message template, and the redundant content includes the general template content in the preset SMS message template. The target content of each SMS message to be processed is organized according to a preset merging template to obtain the target SMS messages of the duplicate recipients. The preset merging template includes a parallel format template or a segmented format template.

6. The method as described in claim 5, wherein the target content of each text message to be processed is organized according to a preset merging template to obtain the target text messages of duplicate recipients, includes: Determine the SMS attribute information of each SMS to be processed, and determine the order of each SMS to be processed according to the attribute priority rules; According to the arrangement order, the target content of each SMS message to be processed is organized according to the preset merging template to obtain the target SMS messages of duplicate recipients.

7. The method as described in claim 6, wherein determining the SMS attribute information of each SMS message to be processed and determining the order of the SMS messages to be processed according to attribute priority rules, includes: The sending time of each pending SMS message is determined, and the pending SMS messages are sorted according to the time priority in the attribute priority rules to obtain the initial sorting order. If at least two pending SMS messages have the same sending time, determine the object type of at least two pending SMS messages, and sort the at least two pending SMS messages in the initial sorting order according to the type priority in the attribute priority rule, so as to obtain the sorting order of each pending SMS message.

8. The method according to any one of claims 1-7, after sending the target SMS message corresponding to each recipient to each recipient, further includes: In response to the recipient's interactive behavior on the target SMS content in the target SMS, feedback information corresponding to the target SMS content is obtained, wherein the target SMS content comes from at least one unprocessed SMS contained in the target SMS; The feedback information is returned to the SMS provider corresponding to the target SMS content.

9. A data processing apparatus, comprising: The acquisition module is configured to acquire at least one SMS message to be sent and the corresponding recipient of each SMS message to be sent. The determining module is configured to determine at least one pending SMS message corresponding to each recipient based on the at least one pending SMS message to be sent and the recipient of each pending SMS message; The sending module is configured to merge at least one pending SMS message corresponding to each recipient to obtain the target SMS message corresponding to each recipient, and send the target SMS message corresponding to each recipient to each recipient.

10. A computing device, comprising: Memory and processor; The memory is used to store computer programs / instructions, and the processor is used to execute the computer programs / instructions, which, when executed by the processor, implement the steps of the data processing method according to any one of claims 1 to 8.

11. A computer-readable storage medium storing a computer program / instructions that, when executed by a processor, implement the steps of the data processing method according to any one of claims 1 to 8.

12. A computer program product comprising a computer program / instructions that, when executed by a processor, implement the steps of the data processing method according to any one of claims 1 to 8.

Images