CN117118800A - Information sending method, system and related equipment - Google Patents

Detailed Description

The present application will be further described in detail with reference to the accompanying drawings, for the purpose of making the objects, technical solutions and advantages of the present application more apparent, and the described embodiments should not be construed as limiting the present application, and all other embodiments obtained by those skilled in the art without making any inventive effort are within the scope of the present application.

The terms "first," "second," "third," "fourth" and the like in the description and in the claims and drawings, if any, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments described herein may be implemented in other sequences than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

In the following description, reference is made to "one embodiment" or "one specific example" and the like, which describe a subset of all possible embodiments, but it is to be understood that "one embodiment" or "one specific example" may be the same subset or a different subset of all possible embodiments and may be combined with each other without conflict. In the following description, the term plurality refers to at least two. Some value as referred to herein reaches a threshold value (if any), and in some specific examples may include the former being greater than the latter; if any reference is made to "any" or "at least one" or the like, that particular reference may be made to any one of the examples listed or any combination between those examples.

Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of the application only and is not intended to be limiting of the application.

For the convenience of understanding and description, before explaining the present application in further detail, terms and terminology involved in the embodiments of the present application will be explained, and the terms and terms involved in the embodiments of the present application are applicable to the following explanation.

Cloud platforms (cloud computing), also known as cloud computing platforms or cloud systems, refer to services that provide computing, networking, and storage capabilities based on hardware resources and software resources.

The short message channel of the embodiment of the application can be a short message sending interface directly provided by an operator, and the purposes of carrying out short message batch sending and custom sending with a client designated number are realized.

ID (Identity document), which is an abbreviation for various proprietary words such as identification number, account number, unique code, proprietary number, industrial design, national abbreviation, legal word, general account, decoder, software company, etc.

Message reach is the notification of specified content to a specified user through various channels or means.

A Process (Process), which is a running activity of a program in a computer on a certain data set, is a basic unit of resource allocation of a system, and is a basis of an operating system structure. In early process-oriented computer architecture, a process is the basic execution entity of a program; in contemporary thread-oriented computer architectures, the process is a container for the threads. A program is a description of instructions, data, and their organization, and a process is an entity of a program.

Redis cache is an open source log type, key-Value database written in ANSIC language, supporting network, capable of being based on memory and persistent, and provides multiple language API.

Referring to fig. 1, fig. 1 shows a schematic view of an application environment suitable for an embodiment of the present application. The method provided by the embodiment of the application can be applied to the interactive system 100 shown in fig. 1, where the interactive system 100 includes a terminal device 101 and a server 102, and the server 102 is in communication connection with the terminal device 101, where the server 102 may be a conventional server or a cloud server, and is not limited herein specifically. The terminal device 101 may be a variety of electronic devices having a display screen and supporting data input, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, wearable electronic devices, and the like; specifically, the data input may be based on a voice module provided on the terminal device 101 to input voice, a character input module to input characters, an image input module to input images, or the like, or may be based on a gesture recognition module provided on the terminal device 101, so that a user may implement interaction modes such as gesture input. The terminal device 101 may have a client application installed thereon, and the user may communicate with the server 102 based on the client application (e.g., APP, applet, etc.), or may also implement the aforementioned data input based on the client application. Similarly, the server 102 may be deployed with a server application, such as a cloud platform program, where the server application may implement the method in conjunction with the client application, for example, to perform a related process on data input by the client application, such as returning a certain information to the terminal device 101.

In the embodiment of the present application, the server 102 may enable a second channel different from the first channel based on a request for sending non-system information (such as certain promotion information) from a target hosting end (such as a computer of a registered merchant), and send the non-system information to a user end in a book of the target hosting end (such as each registered user mobile phone of the merchant) through the second channel, so as to implement promotion of non-system information such as marketing, and increase operation performance of the merchant. The above application environments are merely examples for facilitating understanding, and it is to be understood that embodiments of the present application are not limited to the above application environments.

The method of the present application will be described in further detail below.

Referring to fig. 2, a first aspect of the present application provides a specific embodiment of an information sending method, which includes the following steps:

21. a second channel distinct from the first channel is enabled based on a request for transmission of non-system class information by the target resident.

The cloud platform comprises a first channel, a second channel and a third channel, wherein the first channel supports sending of system type information but limits sending of non-system type information, the system type information refers to external service information configured by the cloud platform aiming at the resident terminal, the external service comprises identity authentication and/or project (progress) reminding, and the second channel is configured by a plurality of pieces of non-system type information customized by different resident terminals in a historical period of time.

In practical application, the resident terminal custom-defined pieces of non-system information often have personalized colors or marketing purposes, and are limited to be sent without conforming to the information format required by the unified cloud platform, so that from the aspect of commercial operation, another path is needed to be developed to popularize the information.

22. And sending the non-system information to the in-album user side of the target resident side through the second channel.

The second channel in the embodiment of the application can support sending of the non-system information and simultaneously can support sending of the system information so as to avoid high single channel error rate, namely, the system information can be sent out through the first channel or the second channel.

In summary, in the embodiment of the application, besides the first channel, the second channel supporting sending of non-system information is started, so that the sending authority of the information is opened, the information popularization channels of the resident end are enriched, and the requirement of more information access is met. In addition, the addition of at least one second channel can effectively reduce the error rate and the time delay caused by a single channel.

On the basis of the above illustration, some specific possible implementation examples will be provided below, and in practical applications, implementation contents between these examples may be implemented by combination as required according to the corresponding functional principles and application logic.

Referring to fig. 3 to 4, another embodiment of an information sending method is provided, and the embodiment includes the following steps:

301. a timing transmission function is configured for each transmission request.

In practical application, the function of not sending short messages in rest time can be added, so that the short message disturbing people can be effectively avoided. Thus, in some specific examples, for task requests to send system class information and/or non-system class information, a timed send time (i.e., lock time) may be configured for each task such that various types of information are sent out at the lock time.

302. And verifying whether the sending task is in the timing sending time.

To reduce the effects of disturbance, information may be sent periodically via a timing strategy, which may include system-class information and/or non-system-class information. Specifically, it can be verified whether the current transmission task is within the allowable timing transmission time; the system type information is sent out through a first channel or a second channel; if not, the information corresponding to the current sending task is cached (for example, cached in a redis library) until the next timing sending time arrives, and the information corresponding to the current sending task is reissued.

In some specific examples, step 32 may be preceded by the following operations: and distinguishing system type information and non-system type information in various types of information through the information identification. For example, the current information can be judged by the ID and/or text content carried by various information, whether the current information is system information (such as that the beginning of ID number is XT or contains "system" type) or non-system information (such as that the beginning of ID number is YY or YX or contains "preferential, promotion, discount, salt" or the like type). Generally, the system information can be sent to the user end or the resident end through a first channel inside the cloud platform, while the non-system information can be sent through a docking channel outside the cloud platform, such as a second channel of a common short message channel opened by an operator, and the like, and of course, the system information can also be sent through the second channel.

The above steps 301 or 302 and the operations of "distinguishing the system class information from the non-system class information" in the various types of information may be performed simultaneously or in any order, and may be specific depending on the actual situation.

31. A second channel distinct from the first channel is enabled based on a request for transmission of non-system class information by the target resident.

In some specific examples, the non-system information includes resident customized marketing information, and may specifically include preferential ordering information of a product at a certain time, or upgrade information of a package service, and other operation contents. In addition, because the information of the information to be sent is different in size, if a lot of information is to be sent to a batch of clients, the communication channel needs to be configured and applied with the purposes of policies such as fast propagation, etc., so that the corresponding process of configuring the second channel may include: collecting customized marketing information (or operation information) of different residents in a period of time; and determining channel parameters for transmitting the marketing information according to the transmission time and/or the information size of each marketing information under the preset bandwidth so as to form a second channel.

For example, operation type short messages such as product preferential ordering short messages, package upgrading short messages and the like defined by a plurality of resident terminals within half a year can be collected, character lengths (namely occupied space sizes) of the short messages are counted, and/or transmission time used when the short messages are successfully sent out under different bandwidths is counted, a channel parameter configuration model is iteratively trained through the character lengths and/or the transmission time corresponding to the short messages, and a second channel parameter is determined through a model result which finally reaches a convergence condition. The convergence condition may be that a communication channel configured by a channel parameter result output by the model reaches a threshold value for successful delivery rates of a plurality of operation type short messages; the successful transfer rate may be used to indicate the ratio of successful receipt of the short message by the contact number participating in the test within a preset period, or may be used to indicate the degree of influence of the channel parameter output by the model on the sending delay and success rate of the short message. The channel parameters may include a transmission frequency and/or network bandwidth, and the transmission frequency may represent a speed of configuring transmission information per second, such as 100 to 999 pieces/second. Generally, the larger the transmission frequency and the network bandwidth, the better the response effect of the configured communication channel, but the higher the requirement on resources such as gateway, so the successful reaching rate threshold limited by the convergence condition should be set comprehensively from the aspects of communication quality, application cost, and the like, and the success reaching rate threshold can be specifically determined by self-determination, and is not limited herein.

32. And sending the non-system information to the in-album user side of the target resident side through the second channel.

Specifically, the information corresponding to the current transmission task may be transmitted in the timing transmission time. In some specific examples, the information may be distributed in terms of priority relationships, so as to avoid poor experiences such as congestion and delay caused by centrally sending the information, so the operations of step 32 may include: and obtaining the hierarchical relationship among different resident terminals, and preferentially opening a second channel to the resident terminal with the current medium level. The rank relation herein may be assessed from any dimension such as residence time, payment amount, and business evaluation, and is not particularly limited.

33. The backup channel is attributed and/or enabled when the transmission fails.

In some specific examples, in the face of a possible failure of information transmission, corresponding countermeasures may be initiated to improve repair efficiency and response speed. For example, if the transmission of the non-system type information fails, the failure reason is checked and fed back, and/or the standby second channel is enabled to retransmit the non-system type information. Of course, failure of transmission of system class information may also initiate countermeasures as described above.

As can be seen from the above description, the embodiment of the application can flexibly configure the task times and time for sending the short message at regular time, greatly reduce the management workload, and limit the sending of the message in the rest period so as to avoid the interference of marketing short message. In addition, a plurality of channels are provided, so that the influence on the service process and efficiency caused by short message sending errors due to a single channel can be avoided.

The operations of steps 31 to 32 and 21 to 23 are similar, and detailed descriptions thereof are omitted. In contrast to the illustration shown in fig. 2, the content of the steps (such as steps 301, 302, and 33) added in the foregoing need not necessarily be executed in the specific implementation, and if two or more steps are added, these steps may be implemented in combination or separately, depending on the actual scenario.

At present, the cloud platform short message sending only can support the sending of system short messages, marketing short messages cannot be sent, and short message triggering requires manual clicking of a sending button (high manual input cost and easy error), so that the system operation cost is increased, meanwhile, short messages can be clicked at any time, and short message disturbing can be easily caused; in addition, a single SMS cloud platform or channel is easy to make mistakes so as to influence the business process and efficiency.

In contrast, as shown in fig. 4, the content of the foregoing embodiment of the present application may include a configuration platform, a service platform (or called cloud platform), a sms platform, a sending platform (external), and a client (or called user end): the newly added short message platform service is used for distinguishing system short messages and marketing short messages (or called operation type short messages), and the operation type short messages are connected with external short message channel services, so that operation means are enriched, and meanwhile, the requirement of message touch is met; providing an alternative short message sending scheme so as to avoid influencing the service process and efficiency due to short message sending errors of the cloud platform; the times and time of the timing short message sending tasks can be flexibly configured, and the operation configuration and management workload is greatly reduced; meanwhile, in order to avoid disturbing people in marketing short messages, a function of not sending short messages in rest time is added. Specific:

1. configuration platform

a) Setting timing tasks (any date and time can be selected once): t1, t2 and t3..

b) Routine tasks (repeated execution): t1/d1, t1/d 2..the term "t 1 herein may be consistent with t1 set by the timing task described above to indicate that a short message is sent at a timing t1 time until the period time d1 (every 1 day).

2. Service platform

a) Timing tasks t1, t2 and t3..A service platform is automatically triggered by a time node, and after the service platform receives a request, a check service is started to judge whether the current task is in a time node allowing a short message to be sent;

b) If yes, automatically carrying a short message ID and triggering a short message platform by content, and sending a short message;

c) If no, that is, if not in the time period of allowing transmission, the short message request is cached in the list data structure of the redis, and meanwhile, a conventional task is newly added (if existing, no adding is performed) to the task platform, for example, at the time point t1 of each day, the service of the dispatch service platform is triggered, and the service can take out the short message request from the list stored before the redis at the moment and perform reissue. In other words, if the timed task is not within the time period in which transmission is allowed, its cache is turned into regular task arrival time reissue.

3. Short message platform

a) Receiving a service push message ID and content, filling the message content into a message template, generating a new message, and judging whether a system message is a message or not according to the message ID;

b) If yes, continuing to judge whether the internal short message channel is started, if yes, selecting the short message channel to push the common short message, and sending the common short message to the butt joint channel;

c) If yes, the system short message is sent, but the internal short message channel of the cloud platform is continuously judged to be in the state of 'not being started', and the short message is pushed to the cloud platform to be sent;

d) If not, the short message belongs to the operation type short message (under the condition of two classifications), and the short message channel is selected to push the common short message, so that the docking channel sends the common short message.

4. Sending platform (outside)

And the channel transmits or pushes the short message to the client.

5. Client terminal

And the client acquires the short message, can verify the validity of the short message, and ends the flow.

Referring to fig. 5, a second aspect of the present application provides a specific example of a cloud platform system, the system including:

a processing unit 501, configured to enable a second channel different from the first channel based on a request for sending non-system class information from a target resident terminal; the cloud platform comprises a first channel, a second channel and a third channel, wherein the first channel supports sending of system type information but limits sending of non-system type information, the system type information refers to external service information configured by the cloud platform aiming at the resident end, the external service comprises identity authentication and/or project reminding, and the second channel is configured by a plurality of pieces of non-system type information customized by different resident ends in a historical period of time;

and the sending unit 502 is configured to send the non-system information to the in-album client of the target resident terminal through the second channel.

Optionally, the non-system class information comprises resident terminal customized marketing class information; the processing unit 501 is specifically configured to:

collecting customized marketing information of different resident terminals in a period of time;

and determining channel parameters for transmitting the marketing information according to the transmission time and/or the information size of each marketing information under the preset bandwidth so as to form a second channel.

Optionally, the processing unit 501 is further configured to:

for task requests for transmitting system class information and/or non-system class information, a timed transmission time is configured for each task so that various kinds of information are transmitted at a lock time.

Optionally, the processing unit 501 is further configured to:

verifying whether the current transmission task is within the allowable timing transmission time;

if yes, sending information corresponding to the current sending task at the timing sending time; the system type information is sent out through a first channel or a second channel;

if not, caching the information corresponding to the current transmission task, and replying the information corresponding to the current transmission task until the next timing transmission time arrives.

Optionally, the processing unit 501 is further configured to:

and distinguishing system type information and non-system type information in various types of information through the information identification.

Optionally, the processing unit 501 is specifically configured to:

and obtaining the hierarchical relationship among different resident terminals, and preferentially opening a second channel to the resident terminal with the current medium level.

Optionally, the processing unit 501 is further configured to:

if the non-system information is failed to be sent, the failure reason is checked and fed back, and/or a standby second channel is started to resend the non-system information.

In the embodiment of the present application, the operations performed by each unit of the cloud platform system are similar to those described in the foregoing first aspect or any one of the specific method embodiments of the first aspect, and are not described herein in detail. Of course, the method described in the first aspect of the present application may be implemented in the embodiment described in the second aspect of the present application.

Referring to fig. 6, an electronic device 600 of an embodiment of the present application may include one or more central processing units (CPUs, central processing units) 601 and a memory 605, where the memory 605 stores one or more application programs or data.

Wherein the memory 605 may be volatile storage or persistent storage. The program stored in the memory 605 may include one or more modules, each of which may include a series of instruction operations in the electronic device. Still further, the central processor 601 may be arranged to communicate with the memory 605 to execute a series of instruction operations in the memory 605 on the electronic device 600.

The electronic device 600 may also include one or more power supplies 602, one or more wired or wireless network interfaces 603, one or more input/output interfaces 604, and/or one or more operating systems, such as Windows ServerTM, mac OS XTM, unixTM, linuxTM, freeBSDTM, etc.

The cpu 601 may perform the operations performed by the foregoing first aspect or any specific method embodiment of the first aspect, which are not described herein.

The application provides a computer readable storage medium comprising instructions which, when run on a computer, cause the computer to perform a method as described in the first aspect or any particular implementation of the first aspect.

The present application provides a computer program product comprising instructions or a computer program which, when run on a computer, causes the computer to perform a method as described above in the first aspect or any particular implementation of the first aspect.

It should be understood that, in various embodiments of the present application, the sequence number of each step does not mean that the execution sequence of each step should be determined by the function and the internal logic, and should not limit the implementation process of the embodiments of the present application.

It will be clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the system (if any) and the apparatus described above may refer to the corresponding processes in the foregoing method embodiments, which are not described in detail herein.

In the several embodiments provided by the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the elements is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple elements or components may be combined or integrated into another system or apparatus, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.

The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on this understanding, the technical solution of the present application may be embodied essentially or in part or all of the technical solution or in part in the form of a software product (computer program product) stored in a storage medium, including instructions for causing a computer device (which may be a personal computer, a service server, or a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a read-only memory (ROM), a random access memory (RAM, random access memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.