Message pushing method and device, server and storage medium

Abstract

The application discloses a message pushing method and device, a server and a storage medium, and relates to the technical field of message pushing. The method comprises the following steps: obtaining a to-be-pushed request corresponding to a target user; wherein the to-be-pushed request comprises a to-be-pushed message; if it is determined according to a pushing parameter corresponding to the target user that the to-be-pushed message needs to be delayed, then the to-be-pushed message is cached, and a delay time corresponding to the to-be-pushed message is determined according to the pushing parameter corresponding to the target user and a pushing time interval; and when the delay time corresponding to the to-be-pushed message arrives, the to-be-pushed message is pushed to a user terminal of the target user. The message pushing method realizes that each pushing message has a certain time interval, thereby avoiding that a user receives multiple messages in a short time, avoiding disturbing the user, improving the user experience, and improving the pushing effect by making the user see the content of each pushing message as much as possible.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of Internet, and in particular to a message pushing method and device, a server and a storage medium. BACKGROUND

[0002] Pushing a message that a user subscribes or is interested in to a user terminal by a mobile phone application (APP) is an important means for an APP manufacturer to achieve an operation target and maintain a user retention rate. Efficient and friendly message pushing can effectively attract users, improve the attention of users to the APP, and thus achieve the purpose of activating and retaining users. On the contrary, if the message pushing is not friendly, it may cause users to be dissatisfied and even uninstall the APP, and finally lead to user loss and a decline in business indicators.

[0003] The APP message pushing process in the related art is generally as follows: a pushing server receives a pushing request of each business upstream, and after receiving the pushing request, sends a message included in the pushing request to a user terminal.

[0004] However, in the message pushing scheme in the related art, the pushing server immediately pushes a message to a user terminal after receiving a pushing request, which may cause a user to receive multiple messages in a short time, easily disturb the user, and also may cause multiple messages to be aggregated and hidden, so that the user cannot see the content of each message, and the pushing effect is affected. Therefore, the message pushing scheme in the related art has the problems of poor user experience and poor pushing effect. SUMMARY

[0005] The present application provides a message pushing method, device, server and storage medium to solve the technical problems of poor user experience and poor pushing effect in the related art.

[0006] According to an aspect of the present application, a message pushing method is provided, which includes:

[0007] Obtaining a to-be-pushed request corresponding to a target user; wherein the to-be-pushed request includes a to-be-pushed message;

[0008] If it is determined according to a pushing parameter corresponding to the target user that the to-be-pushed message needs to be delayed, the to-be-pushed message is cached, and a delay time corresponding to the to-be-pushed message is determined according to the pushing parameter corresponding to the target user and a pushing time interval;

[0009] When the delay time corresponding to the to-be-pushed message arrives, the to-be-pushed message is pushed to a user terminal of the target user.

[0010] According to another aspect of the present invention, a message push device is provided, the device being disposed in a target push server, comprising:

[0011] The acquisition module is used to acquire the push request corresponding to the target user; wherein, the push request includes the push message;

[0012] The first determining module is used to cache the message to be pushed when it is determined, based on the push parameters corresponding to the target user, that the message to be pushed needs to be delayed, and to determine the delay time corresponding to the message to be pushed based on the push parameters corresponding to the target user and the push time interval.

[0013] The push module is used to push the message to be pushed to the target user's user terminal when the delay time corresponding to the message to be pushed is reached.

[0014] According to another aspect of the present invention, a server is provided, the server comprising:

[0015] At least one processor; and

[0016] A memory communicatively connected to the at least one processor; wherein,

[0017] The memory stores a computer program that can be executed by the at least one processor, which enables the at least one processor to perform the message push method according to any embodiment of the present invention.

[0018] According to another aspect of the present invention, a computer-readable storage medium is provided, the computer-readable storage medium storing computer instructions, the computer instructions being configured to cause a processor to execute and implement the message push method described in any embodiment of the present invention.

[0019] The message push method, apparatus, server, and storage medium provided in this invention cache the message to be pushed when it is determined that the push needs to be delayed based on the push parameters corresponding to the target user. The delay time corresponding to the message to be pushed is determined based on the push parameters corresponding to the target user and the push time interval. When the delay time arrives, the message to be pushed is pushed to the target user's terminal. This achieves delayed push of messages in scenarios with frequent message pushes, ensuring a certain time interval between each push message. This avoids users receiving multiple messages in a short period, preventing user disturbance and improving user experience. Furthermore, delayed push ensures that users see the content of each push message as much as possible, improving the push effect.

[0020] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

[0021] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0022] Figure 1 This is a schematic diagram illustrating an application scenario of the message push method provided in an embodiment of the present invention;

[0023] Figure 2 A flowchart of the message push method provided in Embodiment 1 of the present invention;

[0024] Figure 3 A flowchart of the message push method provided in Embodiment 2 of the present invention;

[0025] Figure 4 A flowchart of the message push method provided in Embodiment 3 of the present invention;

[0026] Figure 5 Screenshot of the message push method provided in this embodiment of the invention;

[0027] Figure 6 A flowchart of the message push method provided in Embodiment 4 of the present invention;

[0028] Figure 7 This is a schematic diagram illustrating another application scenario of the message push method provided in this embodiment of the invention;

[0029] Figure 8 A flowchart of the message push method provided in Embodiment 5 of the present invention;

[0030] Figure 9 This is a schematic diagram of the structure of a message push device provided in an embodiment of the present invention;

[0031] Figure 10 This is a schematic diagram of another message push device provided in an embodiment of the present invention;

[0032] Figure 11 This is a schematic diagram of the structure of a server that implements the message push method of this invention. Detailed Implementation

[0033] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

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

[0035] Figure 1 This is a schematic diagram illustrating an application scenario of the message push method provided in an embodiment of the present invention. For example... Figure 1 As shown, the message push method provided in this embodiment can be executed by the target push server 11. In this embodiment, the target push server 11 can be a server in a push server cluster or a standalone server; this embodiment is not limited to this. The target push server 11 is communicatively connected to the upstream business-related communication device 12. For example, the communication device 12 can be a server. The target push server 11 can also be communicatively connected to the user terminal 13. For example, the user terminal 13 can be a mobile phone, tablet computer, in-vehicle computer, smart wearable device, etc. The upstream business-related communication device 12 can generate a push request and send it to the target push server 11. The target push server 11 receives the push request and pushes the push message in the push request to the user terminal 13.

[0036] The message push method provided in this embodiment caches the message to be pushed when it is determined that the push needs to be delayed based on the push parameters corresponding to the target user. It also determines the delay time corresponding to the message to be pushed based on the push parameters corresponding to the target user and the push time interval. When the delay time is reached, the message to be pushed is pushed to the target user's terminal. This achieves the goal of delaying the push of the message to be pushed in scenarios with frequent pushes, and ensures that there is a certain time interval between each push message. This avoids the user receiving multiple messages in a short period of time, so as not to disturb the user and improve the user experience. At the same time, the delayed push can ensure that the user sees the content of each push message as much as possible, thus improving the push effect.

[0037] Figure 2 This is a flowchart of a message push method provided in Embodiment 1 of the present invention. This embodiment is applicable to situations where the push server needs to delay pushing messages to user terminals. The method can be executed by a message push device, which can be implemented in hardware and / or software, and can be configured in the target push server. Figure 2 As shown, the method includes:

[0038] Step 201: Obtain the push request corresponding to the target user.

[0039] Among them, the push request includes the message to be pushed.

[0040] In this embodiment, the target user refers to the user who needs the push notification. The push request in this embodiment refers to a request that has not yet been pushed to the target user. The push request may include the message to be pushed. In this embodiment, the push message may include various information, such as advertisements, app promotion information, news, etc.

[0041] Optionally, the push request may also include a user identifier so that the target push server can determine the correspondence between the push request and the user. Of course, in scenarios where the user is configured with default settings, the push request may not include the user identifier.

[0042] The target push server can proactively obtain push requests from the communication devices of the upstream business, or the communication devices of the upstream business can send push requests to the target push server when there is a push requirement.

[0043] Step 202: If it is determined that the message to be pushed needs to be delayed based on the push parameters corresponding to the target user, then cache the message to be pushed and determine the delay time corresponding to the message to be pushed based on the push parameters corresponding to the target user and the push time interval.

[0044] In this embodiment, after receiving the push request, it is not immediately pushed to the user terminal as in related technologies. Instead, it first determines whether the push message needs to be delayed. Specifically, it determines whether the push message needs to be delayed based on the push parameters corresponding to the target user.

[0045] In this embodiment, the push parameters corresponding to the target user are used to indicate the push parameters of the previous push message of the message to be pushed. For example, it can be the last push time generated after the previous push message of the message to be pushed was pushed, or it can be the next valid push time corresponding to the previous push message of the message to be pushed.

[0046] In one possible implementation, the storage duration of the push parameters corresponding to the target user is equal to the push time interval. When it is determined that the push parameters corresponding to the target user exist, it means that the push will be relatively frequent. Therefore, in order to improve the user experience and the push effect, the message to be pushed is cached.

[0047] While caching messages to be pushed, the target push server can also determine the delay time for the messages to be pushed based on the push parameters corresponding to the target user and the push time interval. In this embodiment, the push time interval refers to the minimum time interval between pushing two push messages.

[0048] For example, the delay time in this embodiment can be determined based on the push time interval, the current time when the message to be pushed is received, and the time of the last push.

[0049] In one implementation, this embodiment sets a delay time for the message to be pushed, so that the push time of the message to be pushed is at least one push time interval from the push time of the previous push message.

[0050] Step 203: When the delay time corresponding to the message to be pushed is reached, push the message to be pushed to the target user's terminal.

[0051] In this embodiment, "delay time arrival" refers to the delay time being updated to zero. After determining the delay time, the delay time is updated in real time. When the delay time is zero, the message to be pushed is sent to the target user's terminal. For example, assuming the delay time corresponding to the message to be pushed is 10 minutes, then "delay time arrival" means that the delay time for the message to be pushed has been updated from 10 minutes to zero minutes.

[0052] In this embodiment, the method of displaying the push message on the user's terminal is not limited. After the target user's terminal receives the push message, the push message can be displayed on the user's terminal in at least one of the following forms: text, voice, video, and image.

[0053] The message push method provided in this embodiment caches the message to be pushed when it is determined that the push needs to be delayed based on the push parameters corresponding to the target user. It also determines the delay time corresponding to the message to be pushed based on the push parameters corresponding to the target user and the push time interval. When the delay time is reached, the message to be pushed is pushed to the target user's terminal. This achieves the goal of delaying the push of the message to be pushed in scenarios with frequent pushes, and ensures that there is a certain time interval between each push message. This avoids the user receiving multiple messages in a short period of time, so as not to disturb the user and improve the user experience. At the same time, the delayed push can ensure that the user sees the content of each push message as much as possible, thus improving the push effect.

[0054] For the same type of upstream business, the message push method provided in this embodiment can prevent users from receiving multiple messages from the same business in a short period of time.

[0055] Figure 3 This is a flowchart of a message push method provided in Embodiment 2 of the present invention. The message push method provided in this embodiment... Figure 2 Based on the illustrated embodiment and various optional implementation schemes, the steps preceding step 202 will be described in detail. In this embodiment, the push request may further include the message type of the message to be pushed. For example... Figure 3 As shown, the method includes:

[0056] Step 301: Obtain the push request corresponding to the target user.

[0057] Among them, the push request includes the message to be pushed.

[0058] The implementation process and technical principles of step 301 are similar to those of step 201, and will not be repeated here.

[0059] Step 302: Determine whether the message to be pushed can be delayed based on the message type of the message to be pushed and the pre-stored mapping relationship between message types and delayed push tags.

[0060] In this embodiment, the types of messages to be pushed are divided into at least two: messages that can be delayed and messages that cannot be delayed, to meet different business types and achieve flexible message push. For messages that can be delayed, it is necessary to determine whether to delay the push; for messages that cannot be delayed, the message is sent immediately.

[0061] In this embodiment, after receiving a push request, the target push server can determine whether the push request can be delayed based on the message type of the message to be pushed included in the push request and the pre-stored mapping relationship between message types and delayable push tags. Specifically, if the mapping relationship determines that the message type of the push request has a delayable push tag, then the push request is determined to be delayed.

[0062] Understandably, delayed push of marked messages can also be achieved by directly including a delayed push tag in the push request.

[0063] Step 303: When it is determined that the message to be pushed can be delayed, proceed to the step of caching the message if it is determined that the message to be pushed needs to be delayed based on the push parameters corresponding to the target user.

[0064] Step 304: If it is determined that the message to be pushed needs to be delayed based on the push parameters corresponding to the target user, then cache the message to be pushed and determine the delay time corresponding to the message to be pushed based on the push parameters corresponding to the target user and the push time interval.

[0065] Step 305: When the delay time corresponding to the message to be pushed is reached, push the message to be pushed to the target user's terminal.

[0066] The implementation process and technical principles of steps 304 and 202, and steps 305 and 203 are similar, and will not be repeated here.

[0067] In one possible implementation, before step 302, the message push method provided in this embodiment may further include the following steps.

[0068] Step 3011: When it is determined that the current push mode is configured as delayed push mode, determine whether the message to be pushed can be delayed based on the message type of the message to be pushed and the pre-stored mapping relationship between message types and delayed push tags.

[0069] Step 3012: When it is determined that the current push mode is configured as non-delayed push mode, push the message to be pushed to the target user's user terminal.

[0070] In this implementation, the push mode can be set to either delayed push mode or non-delayed push mode according to user or business needs. In delayed push mode, step 302 is executed; in non-delayed push mode, the message to be pushed is directly pushed to the target user's terminal.

[0071] The message push method provided in this embodiment, on the one hand, divides message types into at least two types: messages that can be delayed and messages that cannot be delayed, thereby enabling different push modes to be used for different message types to meet different business needs and achieve flexible message push. On the other hand, the push mode can be set to delayed push mode or non-delayed push mode according to user needs or business needs, which can also meet different business needs and achieve flexible and configurable message push.

[0072] Figure 4 This is a flowchart of a message push method provided in Embodiment 3 of the present invention. The message push method provided in this embodiment... Figure 2 and Figure 3 Based on the illustrated embodiments and various optional implementation schemes, steps 202 and 203 will be described in detail. For example... Figure 4 As shown, the method includes:

[0073] Step 401: Obtain the push request corresponding to the target user.

[0074] Among them, the push request includes the message to be pushed.

[0075] The implementation process and technical principles of step 401 are similar to those of step 201, and will not be repeated here.

[0076] Step 402: If it is determined that the message to be pushed needs to be delayed based on the push parameters corresponding to the target user, then the message to be pushed is cached in the delay queue, and the delay time corresponding to the message to be pushed is determined according to the push parameters corresponding to the target user and the push time interval.

[0077] The delay queue (DelayQueue) is located in one of the following locations: the local memory of the target push server, the memory of other servers in the push server cluster besides the target push server, or the distributed cache, which is located in the cache server cluster that communicates with the push server cluster.

[0078] In this embodiment, a delayed queue is used to cache the messages to be pushed and to time the delay time, so that the message push method does not need to rely on additional third-party services such as scheduled tasks, thus making it convenient.

[0079] In one implementation, the delayed queue in this embodiment is located in the local memory of the target push server. Because the delayed queue is located in local memory, the target push server can store messages in and retrieve messages from the delayed queue more quickly.

[0080] In another implementation, the delay queue in this embodiment is located in the memory of servers other than the target push server in the push server cluster. The push server in this implementation is a server within the push server cluster. The servers in the push server cluster are interconnected. This implementation allows the delay queue to be set in the memory of servers other than the target push server when the target push server's memory storage space is insufficient, thereby saving storage space on the target push server and improving its operating speed.

[0081] In another implementation, the delayed queue in this embodiment is located in a distributed cache. The distributed cache is located in a cache server cluster that communicates with the push server cluster. This implementation allows for distributed scaling, enabling the cluster to be expanded on demand and facilitating support for more delayed message pushes.

[0082] Step 403: When the delay time corresponding to the message to be pushed arrives, retrieve the message to be pushed from the delay queue and push the message to the target user's terminal.

[0083] In one possible implementation, step 403 can be implemented as follows: when the delay time corresponding to the message to be pushed arrives, the message to be pushed is retrieved from the delay queue through a delayed push thread, and the push interface is called to push the message to the target user's terminal. This implementation uses a dedicated delayed push thread to retrieve the message to be pushed from the delay queue and call the push interface to push the message to the user terminal, resulting in high efficiency.

[0084] Based on the above implementation, the message push method provided in this embodiment may further include the following steps: when the delay queue is empty or the delay time corresponding to the push messages in the delay queue has not yet arrived, control the delayed push thread to enter a waiting state. Specifically, thread waiting can be implemented by calling the operating system's thread waiting function UNSAFE.park(false, 0L). Controlling the delayed push thread to enter a waiting state can avoid occupying the processor resources of the target push server.

[0085] Optionally, the message push method provided in this embodiment further includes: when the number of push messages cached in the delay queue exceeds a preset threshold, an alarm message is displayed. Specifically, the alarm message can be sent to the device or application corresponding to the relevant staff member by calling the communication interface.

[0086] Figure 5 This is a screenshot of the interface of the message push method provided in an embodiment of the present invention. Figure 5 As shown, an alarm message is displayed in interface 501 to remind relevant staff that too many messages pushed by upstream business have caused the delay queue cache to exceed the limit.

[0087] The message push method provided in this embodiment uses a delay queue to cache messages to be pushed and to time the delay time, so that the implementation of the message push method does not rely on additional third-party services such as scheduled tasks, thus making it convenient.

[0088] Figure 6 This is a flowchart of a message push method provided in Embodiment 4 of the present invention. The message push method provided in this embodiment... Figure 2 , Figure 3 and Figure 4 Based on the illustrated embodiments and various optional implementation schemes, a detailed description is provided of one implementation method for the push parameters corresponding to the target user. In this embodiment, the push parameters corresponding to the target user include: the last push time. The last push time is generated after the previous push message before the message to be pushed was sent, and the storage time of the last push time is less than the push interval. Figure 6 As shown, the method includes:

[0089] Step 601: Obtain the push request corresponding to the target user.

[0090] Among them, the push request includes the message to be pushed.

[0091] The implementation process and technical principles of step 601 are similar to those of step 201, and will not be repeated here.

[0092] Step 602: If it is determined that the message to be pushed needs to be delayed when the previous push time corresponding to the target user is determined, then the message to be pushed is cached, and the delay time corresponding to the message to be pushed is determined according to the previous push time, the push time interval and the current time when the message to be pushed is obtained.

[0093] In this embodiment, the last push time for the target user is generated after the previous push message to be pushed has been sent. Furthermore, the storage time of the last push time is less than the push interval. When a previous push time for the target user is determined to exist, it indicates that pushes are being sent too frequently and need to be delayed. Therefore, the message to be pushed is cached, and its corresponding delay time is calculated.

[0094] For example, it can be based on the formula:

[0095] DelayTime = PushTimeOut - (CurrentTime - LastPushTime) determines the delay time for the message to be pushed. Here, DelayTime represents the delay time for the message to be pushed, PushTimeOut represents the push time interval, CurrentTime represents the current time, and LastPushTime represents the last push time.

[0096] As can be understood, in the formula above, CurrentTime-LastPushTime represents the time interval between the current time and the last push time. To ensure that the push interval between two messages is at least PushTimeOut, subtracting this time interval from PushTimeOut gives the delay time for the message to be pushed.

[0097] In one possible implementation, the previous push time is stored in a distributed cache. Determining the existence of a previous push time for the target user includes: when the previous push time for the target user is found in the distributed cache, determining that a previous push time for the target user exists.

[0098] More specifically, the last push time (LastPushTime) is stored in the distributed cache in key-value format. The key format is: frequency: interval: [biz]: [uid], and the value is a timestamp in seconds.

[0099] Figure 7 This is a schematic diagram illustrating another application scenario of the message push method provided in this embodiment of the invention. For example... Figure 7 As shown, target push server 71 is a server in push server cluster 70. The servers in push server cluster 70 are interconnected. The distributed cache is located in cache server cluster 72, which is communicatively connected to push server cluster 70. When determining whether a previous push time corresponding to the target user exists, target push server 71 can search the distributed cache of cache server cluster 72 to see if such a time exists. This implementation allows for distributed scaling, enabling the cluster to be expanded on demand and facilitating support for more delayed message pushes.

[0100] Step 603: When the delay time corresponding to the message to be pushed is reached, push the message to be pushed to the target user's terminal.

[0101] The implementation process and technical principles of step 603 are similar to those of step 203, and will not be repeated here.

[0102] Optionally, in this embodiment, after the message to be pushed is sent, the last push time is updated to the sending time of the message to be pushed.

[0103] The following example illustrates the above process. Assume PushTimeOut is 15 minutes. At 14:01, the target push server receives a push request A corresponding to target user A, which includes a message A1 to be pushed. Assume the last push time was 13:50, meaning the previous push message for message A1 was pushed at 13:50. At 14:01, the storage time of the last push time 13:50 has not yet exceeded the 15-minute push interval. Therefore, the target push server determines that a previous push time exists for the target user, determines that message A1 needs to be delayed, and caches message A1. Based on the last push time 13:50, the 15-minute push interval, and the current time 14:01 when the message was received, the delay time corresponding to the message to be pushed is determined. In one possible implementation, according to the calculation formula for DelayTime in this embodiment, the delay time can be determined as: Delay time = 15 minutes - (14:01 - 13:50) = 4 minutes. Four minutes later, at 14:05, the message A1 to be pushed will be sent to the target user's terminal.

[0104] In the message push method provided in this embodiment, the push parameters corresponding to the target user include the last push time. The last push time is generated after the previous push message before the message to be pushed is sent, and the storage time of the last push time is less than the push interval. Whether the message to be pushed needs to be delayed is determined based on whether the last push time exists, which has high efficiency. At the same time, it accurately ensures that there is a certain time interval between each push message, further improving the user experience and push effect.

[0105] Figure 8 This is a flowchart of a message push method provided in Embodiment 5 of the present invention. The message push method provided in this embodiment... Figure 2 , Figure 3 and Figure 4 Based on the illustrated embodiments and various optional implementation schemes, another implementation method for the push parameters corresponding to the target user is described in detail. In this embodiment, the push parameters corresponding to the target user include: the next valid push time corresponding to the previous push message of the message to be pushed. The next valid push time corresponding to the previous push message of the message to be pushed is generated after the previous push message is obtained, and the storage time of the next valid push time corresponding to the previous push message of the message to be pushed is less than the push time interval. For example... Figure 8 As shown, the method includes:

[0106] Step 801: Obtain the push request corresponding to the target user.

[0107] Among them, the push request includes the message to be pushed.

[0108] The implementation process and technical principles of step 801 are similar to those of step 201, and will not be repeated here.

[0109] Step 802: If it is determined that the message to be pushed needs to be delayed when the next valid push time corresponding to the previous push message is determined, then the message to be pushed is cached, and the next valid push time corresponding to the message to be pushed is determined according to the next valid push time corresponding to the previous push message and the time interval.

[0110] In this embodiment, the next valid push time corresponding to the previous push message of the message to be pushed is generated after the previous push message is obtained. Since the storage time of the next valid push time corresponding to the previous push message of the message to be pushed is less than the push interval, when it is determined that there is a next valid push time corresponding to the previous push message of the message to be pushed, it means that the push is too frequent at this time and needs to be delayed. Therefore, the message to be pushed is cached and its corresponding delay time is calculated.

[0111] In step 802, the next valid push time for the message to be pushed is determined based on the next valid push time corresponding to the previous push message and the time interval.

[0112] For example, the next valid push time corresponding to the previous push message and the time interval can be used to determine the next valid push time corresponding to the message to be pushed.

[0113] Step 803: Determine the delay time corresponding to the message to be pushed based on the next valid push time corresponding to the message to be pushed and the current time when the message to be pushed is obtained.

[0114] For example, it can be based on the formula:

[0115] DelayTime = NextValidTime – CurrentTime, which determines the delay time for the message to be pushed. Here, DelayTime represents the delay time for the message to be pushed, CurrentTime represents the current time, and NextValidTime represents the next valid push time for the message to be pushed.

[0116] It is understandable that the next valid push time for a message to be pushed is essentially the actual time that the message needs to be pushed. Therefore, the delay time for the message to be pushed is the difference between the actual time that the message needs to be pushed and the current time when the message was received.

[0117] In one possible implementation, the next valid push time corresponding to the previous push message of the message to be pushed is stored in a distributed cache. Determining the existence of a next valid push time corresponding to the previous push message of the message to be pushed includes: when the next valid push time corresponding to the previous push message of the message to be pushed is found in the distributed cache, then the existence of a next valid push time corresponding to the previous push message of the message to be pushed is confirmed. This implementation allows for distributed scaling, enabling the cluster to be expanded on demand and facilitating support for more delayed message pushes.

[0118] Step 804: When the delay time corresponding to the message to be pushed is reached, push the message to be pushed to the target user's terminal.

[0119] The implementation process and technical principles of step 804 are similar to those of step 203, and will not be repeated here.

[0120] The following example illustrates the process. Assume the PushTimeout interval is 15 minutes. At 14:01, the target push server receives a push request A for target user A, which includes a message A1 to be pushed. Assume the next valid push time for the previous push message of message A1 is 13:50, meaning the previous push message for message A1 was actually pushed at 13:50. At 14:01, the storage time of the next valid push time 13:50 for the previous push message of message A1 has not yet exceeded the 15-minute push interval. Therefore, the target push server determines that the next valid push time for the previous push message of message A1 exists, determines that message A1 needs to be delayed, and caches message A1. The sum of the next valid push time 13:50 for the previous push message of message A1 and the 15-minute push interval is determined as the next valid push time for message A1, 14:05. Based on the next valid push time (14:05) for the message to be pushed and the current time (14:01) when the message was received, the delay time for the message to be pushed is determined. In one possible implementation, according to the formula for calculating DelayTime in this embodiment, the delay time can be determined as: Delay time = 14:05 - 14:01 = 4 minutes. The message to be pushed, A1, is pushed to the target user's terminal 4 minutes later, at 14:05.

[0121] In one possible implementation, the next valid push time has a range of values: [StartValidTime, EndValideTime]. This implementation is suitable for message types that are only allowed to start pushing at a specific time. In this implementation, the next valid push time must fall within the range [StartValidTime, EndValideTime] for a message to be pushed.

[0122] During the first push notification, if the current time of push message A2 is less than StartValidTime, then it must wait until StartValidTime before it can be sent. The next valid sending time for push message A2 is StartValidTime, and its delay time is calculated using the formula: DelayTime = NextValidTime - CurrentTime. Since NextValidTime is equal to StartValidTime, then DelayTime = StartValidTime - CurrentTime.

[0123] During the first push notification, if the current time of push message A2 falls between StartValidTime and EndValidTime, then the next valid send time for push message A2 will be the current time, with a delay of zero; that is, push message A2 will be sent directly. The delay time is calculated as: DelayTime = NextValidTime - CurrentTime. Since NextValidTime is CurrentTime, this is equivalent to DelayTime = CurrentTime - CurrentTime = 0.

[0124] During the first push notification, if the current time of push message A2 is greater than EndValideTime, sending is not allowed. For example, push notifications should not be sent to users after 11 PM.

[0125] The storage time for the next valid sending time of push message A2 is the push time interval.

[0126] In the subsequent push process, suppose that during the second push, message A3 to be pushed is obtained.

[0127] If it is determined that there is no next valid sending time for the previous push message A2 of the message to be pushed A3, then the push will be performed according to the logic of the first push.

[0128] If it is determined that there is a next valid sending time for the previous push message A2 of the message to be pushed A3, it indicates that the current push is too frequent and needs to be delayed. The next valid push time for the message to be pushed A3 is determined based on the next valid push time of the previous push message A2 and the push time interval. For example, the next valid push time for the message to be pushed A3 can be the sum of the next valid push time of the previous push message A2 and the push time interval. If the next valid push time for the message to be pushed A3 falls between StartValidTime and EndValidTime, then a delay in pushing the message is allowed. For example, the delay time for the message to be pushed A3 is:

[0129] DelayTime = NextValidTime – CurrentTime, where NextValidTime refers to the next valid push time for the message A3 to be pushed.

[0130] If the next valid push time for message A3 is greater than EndValideTime, then the push of message A3 will not be allowed.

[0131] The following examples illustrate this implementation. Assume the next valid push time ranges from [14:00, 23:00], meaning messages are only allowed to be pushed to user terminals between 2 PM and 11 PM. Assume the push timeout is 15 minutes.

[0132] If the target push server receives push message A4 corresponding to target user A at 13:50 during the first push, it will need to wait until 14:00 to send it. The next valid time to send push message A4 is 14:00, and the delay time is 14:00-13:50=10 minutes.

[0133] During the second push, if the target push server receives message A5 for target user A at 13:52, and determines that the next valid send time of the previous push message A4 for message A5 exists at 14:00, then message A5 needs to be pushed with a delay. The sum of the next valid push time of the previous push message A4 (14:00) and the push interval of 15 minutes is determined as the next valid push time for message A5: 14:15. Since 14:15 falls between StartValidTime and EndValidTime, the delayed push of message A5 is allowed. The delay time for message A5 is: 14:15 - 13:52 = 23 minutes.

[0134] It should be noted that the storage time for the next valid send time of the previous push message to be pushed is calculated from the time represented by that next valid send time itself, not from the moment that next valid send time was generated. For example, in the example above, the next valid send time of 14:00 for the previous push message A4 to be pushed, which is to be pushed, is stored for 15 minutes starting from 14:00, that is, it needs to be stored up to 14:15.

[0135] In the message push method provided in this embodiment, the push parameters corresponding to the target user include the next valid push time corresponding to the previous push message of the message to be pushed. The next valid push time corresponding to the previous push message of the message to be pushed is generated after the previous push message is obtained. The storage time of the next valid push time corresponding to the previous push message of the message to be pushed is less than the push interval. Whether a push delay is needed is determined based on whether a next valid push time corresponding to the previous push message of the message to be pushed exists, resulting in high efficiency. At the same time, it accurately ensures that there is a certain time interval between each push message, further improving the user experience and push effect.

[0136] Figure 9 This is a schematic diagram of a message push device provided in an embodiment of the present invention. The device is installed in a target push server. Figure 9 As shown, the message push device provided in this embodiment includes the following modules: an acquisition module 91, a first determination module 92, and a push module 93.

[0137] The acquisition module 91 is used to acquire the push request corresponding to the target user.

[0138] Among them, the push request includes the message to be pushed.

[0139] The first determining module 92 is used to cache the message to be pushed when it is determined that the message to be pushed needs to be delayed based on the push parameters corresponding to the target user, and to determine the delay time corresponding to the message to be pushed based on the push parameters corresponding to the target user and the push time interval.

[0140] The push module 93 is used to push the message to be pushed to the target user's terminal when the delay time corresponding to the message to be pushed is reached.

[0141] In one implementation, the first determining module 92 is specifically used to cache the message to be pushed in a delayed queue. The delayed queue is located in one of the following locations: the local memory of the target push server, the memory of other servers in the push server cluster besides the target push server, or a distributed cache located in a cache server cluster that is communicatively connected to the push server cluster.

[0142] In this implementation, the push module 93 is specifically used to: retrieve the message to be pushed from the delay queue when the delay time corresponding to the message to be pushed arrives, and push the message to be pushed to the user terminal of the target user.

[0143] More specifically, the push module 93 is used to: when the delay time corresponding to the message to be pushed arrives, retrieve the message to be pushed from the delay queue through the delayed push thread, and call the push interface to push the message to be pushed to the target user's terminal.

[0144] Optionally, the device further includes a control module, used to control the delayed push thread to enter a waiting state when the delay queue is empty or the delay time corresponding to the push messages in the delay queue has not arrived.

[0145] Optionally, the device further includes a notification module, used to provide an alarm message when the number of push messages cached in the delay queue exceeds a preset threshold.

[0146] In one implementation, the push parameters corresponding to the target user include: the last push time. The last push time is generated after the previous push message before the message to be pushed was sent, and the storage time of the last push time is less than the push interval.

[0147] In this implementation, the first determining module 92 is specifically used to: determine that the message to be pushed needs to be delayed when it is determined that there is a previous push time corresponding to the target user. The first determining module 92 is specifically used to: determine the delay time corresponding to the message to be pushed based on the previous push time, the push time interval, and the current time when the message to be pushed is obtained. More specifically, the first determining module 92 is specifically used to: determine the delay time according to the formula:

[0148] DelayTime = PushTimeOut - (CurrentTime - LastPushTime) determines the delay time for the message to be pushed; where DelayTime represents the delay time for the message to be pushed, PushTimeOut represents the push time interval, CurrentTime represents the current time, and LastPushTime represents the last push time.

[0149] Optionally, the last push time is stored in a distributed cache. The first determining module 92 is specifically used to: when the last push time corresponding to the target user is found in the distributed cache, determine that the last push time corresponding to the target user exists.

[0150] In one implementation, the push parameters corresponding to the target user include: the next valid push time corresponding to the previous push message of the message to be pushed. The next valid push time corresponding to the previous push message of the message to be pushed is generated after the previous push message is obtained, and the storage time of the next valid push time corresponding to the previous push message of the message to be pushed is less than the push interval. In this implementation, the first determining module 92 is specifically used to: determine that the message to be pushed needs to be delayed when it is determined that there is a next valid push time corresponding to the previous push message of the message to be pushed.

[0151] The first determining module 92 is specifically used to: determine the next valid push time corresponding to the message to be pushed based on the next valid push time corresponding to the previous push message and the time interval; and determine the delay time corresponding to the message to be pushed based on the next valid push time corresponding to the message to be pushed and the current time when the message to be pushed is obtained.

[0152] More specifically, the first determining module 92 is specifically used to: determine the next valid push time corresponding to the previous push message of the message to be pushed as the sum of the next valid push time and the time interval.

[0153] The first determining module 92 is specifically used for: based on the formula:

[0154] DelayTime = NextValidTime - CurrentTime, which determines the delay time for the message to be pushed; where DelayTime represents the delay time for the message to be pushed, CurrentTime represents the current time, and NextValidTime represents the next valid push time for the message to be pushed.

[0155] The message push device provided in the embodiments of the present invention can execute the message push method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the method execution.

[0156] Figure 1 0 is a schematic diagram of another message push device provided in an embodiment of the present invention. This embodiment... Figure 9 Based on the illustrated embodiments and various optional implementations, the system further includes the following modules: a second determining module 94 and a third determining module 95.

[0157] The second determining module 94 is used to determine whether a message to be pushed can be delayed based on the message type of the message to be pushed and the pre-stored mapping relationship between message types and delayed push tags.

[0158] The third determining module 95 is used to determine, when it is determined that the push message to be pushed can be delayed, to perform the step of caching the push message if it is determined that the push message to be pushed needs to be delayed based on the push parameters corresponding to the target user.

[0159] Optionally, the device further includes a fourth determining module, configured to, when it is determined that the current push mode is configured as a delayed push mode, determine whether the message to be pushed can be delayed based on the message type of the message to be pushed and the pre-stored mapping relationship between message types and delayed push tags. In this implementation, the push module 93 is further configured to, when it is determined that the current push mode is configured as a non-delayed push mode, push the message to be pushed to the target user's user terminal.

[0160] The message push device provided in the embodiments of the present invention can execute the message push method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the method execution.

[0161] Figure 11 This is a schematic diagram of the structure of a server implementing the message push method of this embodiment of the invention. The server 10 in this embodiment is intended to represent various forms of servers, such as laptop computers, desktop computers, workstations, servers, blade servers, mainframe computers, and other suitable computers. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

[0162] like Figure 11As shown, server 10 includes at least one processor 11 and memory, such as read-only memory (ROM) 12 and random access memory (RAM) 13, communicatively connected to at least one processor 11. The memory stores computer programs executable by at least one processor. The processor 11 can perform various appropriate actions and processes based on the computer program stored in the ROM 12 or loaded from storage unit 18 into the RAM 13. The RAM 13 can also store various programs and data required for the operation of server 10. The processor 11, ROM 12, and RAM 13 are interconnected via bus 14. Input / output (I / O) interface 15 is also connected to bus 14.

[0163] Multiple components in server 10 are connected to I / O interface 15, including: input unit 16, such as keyboard, mouse, etc.; output unit 17, such as various types of monitors, speakers, etc.; storage unit 18, such as disk, optical disk, etc.; and communication unit 19, such as network card, modem, wireless transceiver, etc. Communication unit 19 allows server 10 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0164] Processor 11 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. Processor 11 executes the various message push methods and various optional implementations described above.

[0165] In some embodiments, the message push method may be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or installed on server 10 via ROM 12 and / or communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the message push method described above may be performed. Alternatively, in other embodiments, processor 11 may be configured to perform the message push method by any other suitable means (e.g., by means of firmware).

[0166] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0167] Computer programs used to implement the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be performed. The computer programs may be executed entirely on a machine, partially on a machine, or as a standalone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0168] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0169] To provide interaction with the user, the systems and techniques described herein can be implemented on a server having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the server. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including voice input, speech input, or tactile input).

[0170] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), middleware components (e.g., application servers), or frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0171] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a hosting product within the cloud computing service system to address the shortcomings of traditional physical hosts and VPS services, such as high management difficulty and weak business scalability.

[0172] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.

[0173] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A message push method, characterized in that, When applied to a target push server, the method includes: Obtain the push request corresponding to the target user; wherein, the push request includes the push message; If it is determined that the message to be pushed needs to be delayed based on the push parameters corresponding to the target user, then the message to be pushed is cached, and the delay time corresponding to the message to be pushed is determined based on the push parameters corresponding to the target user and the push time interval. When the delay time corresponding to the message to be pushed is reached, the message to be pushed is pushed to the user terminal of the target user. The push parameters corresponding to the target user include: the last push time, which is generated after the previous push message before the message to be pushed was sent, and the storage time of the last push time is less than the push time interval; determining the delay time corresponding to the message to be pushed based on the push parameters corresponding to the target user and the push time interval includes: according to the formula: Determine the delay time corresponding to the message to be pushed, wherein, This indicates the delay time corresponding to the message to be pushed. This indicates the push time interval. Indicates the current time. Indicates the time of the last push; or, The push parameters corresponding to the target user include: the next valid push time corresponding to the previous push message of the message to be pushed, wherein the next valid push time corresponding to the previous push message of the message to be pushed is generated after the previous push message is obtained, and the storage time of the next valid push time corresponding to the previous push message of the message to be pushed is less than the push time interval; determining the delay time corresponding to the message to be pushed based on the push parameters corresponding to the target user and the push time interval includes: determining the next valid push time corresponding to the message to be pushed as the sum of the next valid push time corresponding to the previous push message of the message to be pushed and the push time interval; according to the formula: Determine the delay time corresponding to the message to be pushed, wherein, This indicates the delay time corresponding to the message to be pushed. Indicates the current time. This indicates the next valid push time for the message to be pushed.

2. The method according to claim 1, characterized in that, The request to be pushed also includes the message type of the message to be pushed; If, based on the push parameters corresponding to the target user, it is determined that the message to be pushed needs to be delayed, before caching the message to be pushed, the method further includes: Based on the message type of the message to be pushed and the pre-stored mapping relationship between message types and delayed push tags, determine whether the message to be pushed can be delayed. When it is determined that the message to be pushed can be delayed, the step of caching the message to be pushed is executed if the push parameters corresponding to the target user indicate that the message to be pushed needs to be delayed.

3. The method according to claim 2, characterized in that, Before determining whether a message to be pushed can be delayed based on its message type and the pre-stored mapping relationship between message types and delayable push tags, the method further includes: When it is determined that the current push mode is configured as delayed push mode, the step of determining whether the message to be pushed can be delayed is executed based on the message type of the message to be pushed and the pre-stored mapping relationship between message types and delayed push tags. When it is determined that the current push mode is configured as non-delayed push mode, the message to be pushed is pushed to the user terminal of the target user.

4. The method according to any one of claims 1 to 3, characterized in that, The cached message to be pushed includes: The message to be pushed is cached in a delayed queue; wherein the delayed queue is located in one of the following locations: in the local memory of the target push server, in the memory of other servers in the push server cluster besides the target push server, or in a distributed cache, wherein the distributed cache is located in a cache server cluster that is communicatively connected to the push server cluster.

5. The method according to claim 4, characterized in that, The step of pushing the message to the target user's terminal when the delay time corresponding to the message to be pushed arrives includes: When the delay time corresponding to the message to be pushed arrives, the message to be pushed is retrieved from the delay queue and pushed to the user terminal of the target user.

6. The method according to claim 5, characterized in that, The step of retrieving the message to be pushed from the delay queue and pushing the message to the target user's terminal when the delay time corresponding to the message to be pushed arrives includes: When the delay time corresponding to the message to be pushed arrives, the message to be pushed is retrieved from the delay queue through the delayed push thread, and the push interface is called to push the message to be pushed to the user terminal of the target user.

7. The method according to claim 6, characterized in that, The method further includes: When the delay queue is empty or the delay time corresponding to the push message in the delay queue has not been reached, the delayed push thread is controlled to enter a waiting state.

8. The method according to claim 4, characterized in that, The method further includes: An alarm message is issued when the number of push messages cached in the delay queue exceeds a preset threshold.

9. The method according to any one of claims 1 to 3, characterized in that, The step of determining that the message to be pushed needs to be delayed based on the push parameters corresponding to the target user includes: If it is determined that there is a previous push time for the target user, it is determined that the message to be pushed needs to be delayed.

10. The method according to claim 9, characterized in that, The time of the last push is stored in a distributed cache; Determining the existence of the last push notification time for the target user includes: When the last push time corresponding to the target user is found in the distributed cache, it is determined that the last push time corresponding to the target user exists.

11. The method according to any one of claims 1 to 3, characterized in that, The step of determining that the message to be pushed needs to be delayed based on the push parameters corresponding to the target user includes: When it is determined that there is a next valid push time corresponding to the previous push message of the message to be pushed, it is determined that the push message needs to be delayed.

12. A message push device, characterized in that, The device is installed in the target push server and includes: The acquisition module is used to acquire the push request corresponding to the target user; wherein, the push request includes the push message; The first determining module is used to cache the message to be pushed when it is determined, based on the push parameters corresponding to the target user, that the message to be pushed needs to be delayed, and to determine the delay time corresponding to the message to be pushed based on the push parameters corresponding to the target user and the push time interval. The push module is used to push the message to be pushed to the user terminal of the target user when the delay time corresponding to the message to be pushed is reached; The push parameters corresponding to the target user include: the last push time, which is generated after the previous push message before the message to be pushed was sent, and the storage time of the last push time is less than the push time interval; the first determining module is specifically used to: according to the formula: Determine the delay time corresponding to the message to be pushed, wherein, This indicates the delay time corresponding to the message to be pushed. This indicates the push time interval. Indicates the current time. Indicates the time of the last push; or, The push parameters corresponding to the target user include: the next valid push time corresponding to the previous push message of the message to be pushed; wherein, the next valid push time corresponding to the previous push message of the message to be pushed is generated after the previous push message is obtained, and the storage time of the next valid push time corresponding to the previous push message of the message to be pushed is less than the push time interval; the first determining module is specifically used to: determine the next valid push time corresponding to the message to be pushed as the sum of the next valid push time corresponding to the previous push message of the message to be pushed and the push time interval; according to the formula: Determine the delay time corresponding to the message to be pushed, wherein, This indicates the delay time corresponding to the message to be pushed. Indicates the current time. This indicates the next valid push time for the message to be pushed.

13. A server, characterized in that, The server includes: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the message push method according to any one of claims 1-11.

14. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that are used to cause a processor to execute the message push method according to any one of claims 1-11.

Images