A message pushing method and device

Abstract

The present disclosure provides a message pushing method and device, wherein the method comprises: determining a list of accounts associated with a target device; each account in the list of accounts corresponds to a message receiving object; obtaining each target account in the list of accounts selected by a user, and determining a message receiving type configured by the user for each target account; and pushing a message of the message receiving object corresponding to each target account to the target device based on each target account and the message receiving type corresponding to each target account. This embodiment improves the efficiency of the user receiving messages by simultaneously pushing the messages of the message receiving objects corresponding to each target account to the target device, thereby improving the convenience and efficiency of the user processing messages.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and more specifically, to a message push method and apparatus. Background Technology

[0002] When third-party merchants operate on e-commerce platforms, they typically run multiple stores simultaneously. After logging into the client on their device, merchants can usually only receive business message notifications from the currently logged-in store. To view business messages from other simultaneously operated stores, they need to switch to another store's account, resulting in low message receiving efficiency and impacting the convenience and efficiency of message processing for users. Summary of the Invention

[0003] In view of this, the present disclosure provides at least one message push method, apparatus, electronic device, and storage medium, which can improve the efficiency of users receiving messages, thereby improving the convenience and efficiency of users processing messages.

[0004] In a first aspect, embodiments of this disclosure provide a message push method, including:

[0005] Based on the user-initiated account association operation, determine each candidate account associated with the target device;

[0006] Obtain at least one target account selected by the user from each candidate account, and receive the push message corresponding to the target account;

[0007] Push the message to be pushed to the target device corresponding to the target account.

[0008] Optionally, based on the user-initiated account association operation, candidate accounts associated with the target device are determined, including:

[0009] Obtain user-uploaded account data and verify the login status of each account to be associated in the account data;

[0010] In response to the valid login status of the account to be associated, the account to be associated is identified as a candidate account to be associated with the target device.

[0011] Optionally, before pushing the message to be pushed to the target account to the target device, the method further includes:

[0012] Determine the message receiving type for the target account;

[0013] Push the message to be pushed to the target device, which corresponds to the message receiving type.

[0014] Optionally, the message receiving type for the target account can be determined, including:

[0015] Determine whether the configuration information stored in the local storage location includes the message receiving type corresponding to the target account;

[0016] In response to the configuration information including the message receiving type corresponding to the target account, the message receiving type configured by the user for the target account is retrieved from the local storage location;

[0017] If the configuration information does not include the message receiving type corresponding to the target account, retrieve the message receiving type configured by the user for the target account to determine the message receiving type corresponding to the target account.

[0018] Optionally, before pushing the message to be pushed to the target account to the target device, the method further includes:

[0019] Based on the message type of the message to be pushed, the notification requirements of the message to be pushed are determined, and the message is pushed to the target device based on the notification requirements.

[0020] Optionally, the method further includes:

[0021] In response to the notification requirement of the message to be pushed, a repeat notification task corresponding to the message to be pushed is created.

[0022] In response to the expiration of the recurring notification task corresponding to the message to be pushed, determine the push status of the message to be pushed;

[0023] If the push status of the message to be pushed is incomplete, generate a duplicate notification message for the message to be pushed and push it to the target device; if the push status of the message to be pushed is completed, delete the duplicate notification task corresponding to the message to be pushed.

[0024] Secondly, embodiments of this disclosure provide a message push device, including:

[0025] The determination module is used to determine each candidate account associated with the target device based on the account association operation initiated by the user.

[0026] The acquisition module is used to acquire at least one target account selected by the user from each candidate account and to receive the push message corresponding to the target account.

[0027] The push module is used to push the messages corresponding to the target account to the target device.

[0028] Thirdly, embodiments of this disclosure also provide an electronic device, including: a processor, a memory, and a bus. The memory stores machine-readable instructions executable by the processor. When the computer device is running, the processor communicates with the memory via the bus. When the machine-readable instructions are executed by the processor, the steps of the first aspect or any optional implementation of the first aspect are performed.

[0029] Fourthly, embodiments of this disclosure also provide a computer-readable storage medium storing a computer program that, when executed by a processor, performs the steps of the first aspect or any optional implementation thereof.

[0030] Fifthly, embodiments of this disclosure also provide a computer program product, including a computer program that, when executed by a processor, implements the methods of any of the above embodiments.

[0031] Any of the above aspects or any implementation thereof enables the same target device to simultaneously receive business messages from multiple message receiving objects by associating multiple accounts with the target device and configuring different message receiving types for each account. When a user logs in, the system can identify candidate accounts associated with the current target device. Each candidate account can correspond to a message receiving object. Taking an e-commerce operation scenario as an example, the message receiving object here can represent different stores opened by the same merchant. The user can select the target account from the candidate accounts and set the desired message type. The execution entity of this embodiment can then push messages from the message receiving objects corresponding to the target accounts to the target device based on the target accounts selected by the user and the corresponding message receiving types. Thus, the user can jump to the corresponding message processing page and quickly enter the message processing flow by triggering messages, without having to switch accounts one by one to check if there are any pending messages. This not only improves the efficiency of message pushing but also enhances the convenience and efficiency of message processing for users.

[0032] The effects of the aforementioned message push device, electronic device, and storage medium are described in the description of the aforementioned message push method, and will not be repeated here. Attached Figure Description

[0033] To more clearly illustrate the technical solutions of the embodiments of this disclosure, the accompanying drawings used in the embodiments will be briefly described below. These drawings are incorporated in and constitute a part of this specification. They illustrate embodiments conforming to this disclosure and, together with the specification, serve to explain the technical solutions of this disclosure. It should be understood that the following drawings only show some embodiments of this disclosure and should not be considered as limiting the scope. Those skilled in the art can obtain other related drawings based on these drawings without creative effort.

[0034] Figure 1 A flowchart of a message push method provided in an embodiment of this disclosure is shown;

[0035] Figure 2This diagram illustrates a structural schematic of a message push method provided in an embodiment of the present disclosure.

[0036] Figure 3 A flowchart illustrating a message push method provided in an embodiment of this disclosure is shown.

[0037] Figure 4 A schematic diagram of a repeat notification process provided by an embodiment of this disclosure is shown;

[0038] Figure 5 A schematic diagram of a message push device provided in an embodiment of this disclosure is shown;

[0039] Figure 6 An exemplary system architecture in which embodiments of this disclosure can be applied is shown;

[0040] Figure 7 A schematic diagram of the structure of a computer system used to implement the embodiments of the present disclosure is shown. Detailed Implementation

[0041] To make the objectives, technical solutions, and advantages of the embodiments of this disclosure clearer, the technical solutions of the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this disclosure, and not all of them. The components of the embodiments of this disclosure described and shown in the accompanying drawings can generally be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of this disclosure provided in the accompanying drawings is not intended to limit the scope of the claimed disclosure, but merely represents selected embodiments of this disclosure. All other embodiments obtained by those skilled in the art based on the embodiments of this disclosure without inventive effort are within the scope of protection of this disclosure.

[0042] It should be noted that the collection, use, storage, sharing and transfer of user personal information involved in the technical solution of the present invention all comply with the provisions of relevant laws and regulations, and require notification to users and obtaining their consent or authorization. When applicable, user personal information is subjected to de-identification and / or anonymization and / or encryption technical processing.

[0043] The above problems and solutions are the result of the inventor's practice and careful research. The discovery process of the above problems and the solutions proposed for the above problems should be considered as the inventor's contribution to this disclosure.

[0044] The technical solutions of this disclosure will now be clearly and completely described with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this disclosure, and not all of them. The components of this disclosure described and shown in the accompanying drawings can generally be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of this disclosure provided in the accompanying drawings is not intended to limit the scope of the claimed disclosure, but merely to illustrate selected embodiments of this disclosure. All other embodiments obtained by those skilled in the art based on the embodiments of this disclosure without inventive effort are within the scope of protection of this disclosure.

[0045] It should be noted that similar labels and letters in the following figures indicate similar items. Therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures.

[0046] To facilitate understanding of this embodiment, a message push method disclosed in this disclosure will first be described in detail. The execution subject of the message push method provided in this disclosure is generally a computer device with certain computing capabilities. This computer device may include, for example, a terminal device, a server, or other processing devices. The terminal device may be a user equipment (UE), mobile device, user terminal, terminal, cellular phone, cordless phone, personal digital assistant (PDA), handheld device, computing device, in-vehicle device, wearable device, etc. In some possible implementations, this message push method can be implemented by the processor calling computer-readable instructions stored in memory.

[0047] See Figure 1 The diagram shows a flowchart of a message push method provided in an embodiment of this disclosure. The method includes steps S101 to S103, wherein:

[0048] S101: Based on the user-initiated account association operation, determine each candidate account associated with the target device.

[0049] In this embodiment, the user can pre-bind the device and the account. In specific implementation, a unique identifier can be generated for the target device, which can be generated based on the target device's hardware information, operating system information, and current timestamp information, as long as the identifier can uniquely identify the target device. This embodiment does not specifically limit the method for generating the device identifier.

[0050] In this embodiment, each account can correspond to one message receiving object. Taking an e-commerce operation scenario as an example, the message receiving object can correspond to different stores operated by the same merchant, and each account can be used to receive messages from different stores. After obtaining the identification code of the target device, when a user logs in to the device, multiple accounts can be bound. For example, the user can associate the accounts of multiple message receiving objects with the device identification code through authorization. The account of each message receiving object can be mapped to the unique identification code of the device, and then the system can save the binding relationship between the device identification code and each account.

[0051] For example, consider a scenario where a single user operates multiple stores on an e-commerce platform. When a user logs into a target device, they can be required to bind accounts for multiple stores. The user can then associate these store accounts with the target device's device identifier by entering the account passwords for each store or by scanning a QR code for verification and authorization. In this scenario, the target device can be a mobile phone or computer, the message recipient can be a store, and each store's account can be the account corresponding to the message recipient. It should be noted that an account can also be associated with different devices. Continuing the example above, if store A is large and requires three staff members to operate it simultaneously, then store A's account can be associated with the devices of these three staff members. Furthermore, in addition to store A's account, each staff member's device can also bind multiple accounts from other stores such as store B or store C. This disclosure does not specifically limit this aspect.

[0052] In practice, after the account binding is completed, the candidate accounts associated with the current target device can be obtained. Assuming that the target device is bound to 6 candidate accounts, they can be sorted according to the binding time or other dimensions of information to obtain a list of accounts associated with the target device. Figure 2 This is a schematic diagram of the structure of a message push method provided in an embodiment of this disclosure, as shown below. Figure 2 As shown, after obtaining the list of accounts associated with the target device, it can be written to a database or cache storage location. Thus, when the user logs into the target device next time, there is no need to bind the account again. It is only necessary to retrieve the list of accounts that are bound to the device identifier of the current target device from the storage location.

[0053] like Figure 2As shown, the association between the target device and the account can be affected by operations such as login, logout, account switching, and login state expiration. Login refers to the user successfully verifying their identity by entering their password, scanning a QR code, or using other authentication methods. The target device then records the login status of that account and associates it with that account. Logout refers to the user actively ending their current account's login state; the target device no longer retains the account's authentication information and session state, meaning the user actively unbinds themselves from the current account. Account switching refers to the user switching to another account on the target device. After switching accounts, the target device can establish a session association with the new account to handle messages for that account. Login state expiration refers to the account's login information expiring or becoming invalid, usually due to timeout, password changes, or security verification issues. In this case, the target device can re-authenticate the account to restore the binding relationship between the target device and the account.

[0054] In this embodiment of the disclosure, if the user has pre-bound an account, candidate accounts associated with the current target device can be retrieved from a database or cache. Before determining the list of accounts associated with the target device, the login status of each candidate account can be determined. Specifically, based on the account association operation initiated by the user, determining each candidate account associated with the target device includes: obtaining account data uploaded by the user, verifying the login status of each account to be associated in the account data; and, in response to the valid login status of the account to be associated, determining the account to be associated as a candidate account associated with the target device.

[0055] In practice, after a user logs into the target device, they can query all accounts that have been associated with the target device from local storage locations such as a database or cache. Then, the login status of all accounts can be verified. As described earlier, for accounts whose storage timeouts or password changes have occurred, their login status is invalid, and these accounts can be removed. The remaining accounts are candidate accounts for association with the target device. Alternatively, for accounts with invalid login status, a request can be sent to the user to log in again. When the user logs in again with the corresponding account, their login status can be updated to valid, thus obtaining the corresponding candidate accounts.

[0056] In practical implementation, to ensure query efficiency, Redis (Remote Dictionary Server)'s hash structure can be used for storage. To ensure the atomicity and consistency of data operations, LUA (Linguistic Script Universal) scripts can be used to ensure that two storage operations are completed within the same transaction, preventing data inconsistencies. Regarding data persistence, after data is stored in Redis, it can be asynchronously persisted to the database using a message queue, ensuring data recovery in case of failure. The persisted data can be used for disaster recovery, while online queries can prioritize using the data in Redis. For example, if multiple accounts are bound to the target device, the system may need to store account information in Redis and update the binding status between the device and the accounts. To ensure no data conflicts or inconsistencies between these two operations, LUA scripts are used to guarantee that these two operations are atomic, ensuring that they either both execute successfully or neither executes, thus maintaining system data consistency.

[0057] It should be noted that the embodiments of this disclosure do not specifically limit the storage method for storing the association between the device identifier and the account in the local storage location. In practical applications, it can be set according to actual needs. In addition to the above method, other storage methods can also be used to store the binding relationship and status between the device and the account. The embodiments of this disclosure do not specifically limit this, as long as the function can be achieved.

[0058] S102: Obtain at least one target account selected by the user from the candidate accounts, and receive the push message corresponding to the target account.

[0059] In this embodiment, after determining the candidate accounts associated with the target device, the user can select the target account from among the candidate accounts to receive messages. The number of target accounts can be arbitrarily set according to the user's selection; alternatively, to ensure that messages can be received and processed in a timely manner, the system can pre-set an upper limit for the selection of target accounts. This embodiment does not impose specific limitations on either aspect, and the settings can be adjusted according to actual conditions in practical applications. After selecting the target accounts to receive messages, the execution entity of this embodiment can accept the messages to be pushed to the corresponding target accounts and push them to the target device.

[0060] In this embodiment of the disclosure, before pushing the message to be pushed corresponding to the target account to the target device, the method further includes: determining the message receiving type of the target account; and pushing the message to be pushed corresponding to the message receiving type to the target device.

[0061] In practical implementation, users can not only set the target accounts to receive messages, but also set the message types that each target account should receive. Therefore, the execution entity of this embodiment can filter the messages to be pushed to the target accounts based on the message receiving types set by the user, and then push them to the target devices. System notifications or other unimportant messages can be omitted from the push, thereby improving message processing efficiency. Specifically, determining the message receiving type for the target account includes: determining whether the configuration information stored in the local storage location includes a message receiving type corresponding to the target account; in response to the configuration information including a message receiving type corresponding to the target account, retrieving the message receiving type configured by the user for the target account from the local storage location; in response to the configuration information not including a message receiving type corresponding to the target account, retrieving the message receiving type configured by the user for the target account to determine the message receiving type corresponding to the target account.

[0062] In specific implementation, before pushing messages to the target device, the executing entity of this embodiment can filter all messages according to the message receiving type corresponding to each target account, and then push the filtered messages to the target device. Alternatively, all messages can be pushed to the target device, and only messages under the message receiving type can be notified. When pushing messages, since the same message receiving object may correspond to multiple target accounts, the messages can be integrated according to the dimension of the message receiving object and pushed to the target device. After receiving the pushed message, the application installed on the target device can perform operations such as account switching according to the message receiving object identifier corresponding to the account in the message body content, so that users can process messages more conveniently and efficiently.

[0063] In practice, when binding an account to a target device, users can set the message receiving type for each account. For example, the account for store A can be set to receive only after-sales messages, while the account for store B can be set to receive both order and marketing messages. After setting the message receiving type for each account, it can also be stored locally in the manner described above for future retrieval. Figure 3 This is a schematic diagram of a message push process provided in an embodiment of this disclosure, such as... Figure 3As shown, after a user logs into the target device and enables multi-account message reception, they can select target accounts from a list of confirmed accounts to receive messages from. For example, if the list includes 10 accounts, the user can select 5 target accounts to receive messages from during login. After the user selects the target accounts, the system can query the local storage location to see if a message reception type corresponding to that account is saved, based on the account's identifier information. Once the user completes the initial target account selection on the target device, the selection record can be saved in both the cache and the database. This record includes the selected target accounts and their corresponding message reception types. Upon the user's next login, the system can retrieve the previously saved data from the cache. Since cache storage time is limited, data can be retrieved from the database when it expires. After retrieving the previously saved target accounts and their corresponding message reception types, this information can be displayed to the user to determine whether to continue with the previous settings. If updates to the previously saved data are needed, the user can make changes at this point, and the updated data can then be saved in the local storage location. Alternatively, if the user has not set the message receiving type corresponding to the target account in the configuration information in advance, the message receiving type corresponding to the target account can be determined by obtaining the configuration information currently uploaded by the user and based on the configuration content in the configuration information.

[0064] In another possible implementation, the user may be asked the target account for receiving messages and the message receiving type corresponding to each target account each time the user logs in. This disclosure does not specifically limit this, but only requires that the function can be achieved.

[0065] S103: Push the message to be pushed to the target device corresponding to the target account.

[0066] In this embodiment of the disclosure, before pushing the message to be pushed to the target device corresponding to the target account, the method further includes: determining the notification requirement of the message to be pushed based on the message type of the message to be pushed, so as to push the message to the target device based on the notification requirement.

[0067] In practical implementation, different message types may have different notification requirements. Continuing with the example of a merchant operating multiple stores on an e-commerce platform, customer after-sales issues may have a higher processing priority for the e-commerce merchant. If users do not handle these messages promptly, it may affect the store's rating and reputation. System notification messages, on the other hand, typically have a lower processing priority. Therefore, different notification requirements can be set for different types of business messages, enabling the execution entity of this embodiment to push messages to the target device according to the notification requirements. These notification requirements can be set by the user or pre-defined for different application scenarios. This embodiment does not specifically limit their implementation; the goal is to achieve the desired functionality.

[0068] In one possible implementation, for messages with high processing priority, their notification requirements can be set as repeat notifications. Specifically, the method further includes: in response to the notification requirement of the message to be pushed being repeated, creating a repeat notification task corresponding to the message to be pushed; in response to the expiration of the repeat notification task corresponding to the message to be pushed, determining the push status of the message to be pushed; if the push status of the message to be pushed is incomplete, generating repeat notification information for the message to be pushed and pushing it to the target device; if the push status of the message to be pushed is complete, deleting the repeat notification task corresponding to the message to be pushed.

[0069] In practice, as exemplified above, messages with high processing priority can be pushed to them using repeated notifications. Figure 4 This is a schematic diagram of a repeat notification process provided in an embodiment of the present disclosure, such as... Figure 4As shown, when messages with time-sensitive or high-priority processing requirements, such as orders and after-sales messages, are received, it can first be determined whether this type of message needs to be repeated based on pre-set notification requirements. If not, the message can be pushed directly. If this type of message needs to be repeated, a repeated notification task can be created for it, and the message can be saved in Redis using a string structure. The key can be set as the message identifier, and the value can be determined based on the user account, the identifier of the message recipient, the name of the message recipient, and the message body. At the same time, the message identifier and the task expiration time can be saved in the task engine. The task engine can scan all the repeated notification tasks saved there. When the task expires, it can call the business interface to query whether the task has been completed. If it has not been completed, the corresponding repeated notification information can be generated and pushed to the target device in a preset form. The preset form here can be a key prompt box displayed on the application homepage, or it can be a text message or email reminder, etc. This embodiment does not specifically limit this. If the query determines that the repeated notification task has been completed, the repeated notification task can be deleted from the task engine. It's important to note that the task engine can take the form of a time wheel. This means that after the initial reminder, the interface can be called again after a preset time to check if the task has been completed, i.e., whether the message has been processed. If it hasn't been processed, the process of repeating the reminder can continue. Furthermore, users can also set single-reminder reminders for repeating messages. That is, once a message has been reminded repeatedly, it is removed from the task engine, and the repeat reminder process for that message is no longer triggered.

[0070] It should be noted that the embodiments disclosed herein do not specifically limit the types of messages that need to be repeatedly notified. In practical applications, in addition to setting high-priority messages as the type of messages that need to be repeatedly notified as required above, other types of message notification requirements can also be set by oneself.

[0071] According to a second aspect of the embodiments of this disclosure, such as Figure 5 As shown, a message push device 500 is provided, including:

[0072] The determination module 501 is used to determine each candidate account associated with the target device based on the account association operation initiated by the user.

[0073] The acquisition module 502 is used to acquire at least one target account selected by the user from each candidate account, and to receive the message to be pushed corresponding to the target account;

[0074] The push module 503 is used to push the message to be pushed corresponding to the target account to the target device.

[0075] Optionally, the determination module 501 is specifically used for:

[0076] Obtain user-uploaded account data and verify the login status of each account to be associated in the account data;

[0077] In response to the valid login status of the account to be associated, the account to be associated is identified as a candidate account to be associated with the target device.

[0078] Optionally, the acquisition module 502 is also used for:

[0079] Determine the message receiving type for the target account;

[0080] Push the message to be pushed to the target device, which corresponds to the message receiving type.

[0081] Optionally, module 502 is specifically used for:

[0082] Determine whether the configuration information stored in the local storage location includes the message receiving type corresponding to the target account;

[0083] In response to the configuration information including the message receiving type corresponding to the target account, the message receiving type configured by the user for the target account is retrieved from the local storage location;

[0084] If the configuration information does not include the message receiving type corresponding to the target account, retrieve the message receiving type configured by the user for the target account to determine the message receiving type corresponding to the target account.

[0085] Optionally, the push module 503 is specifically used for:

[0086] Based on the message type of the message to be pushed, the notification requirements of the message to be pushed are determined, and the message is pushed to the target device based on the notification requirements.

[0087] Optionally, the push module 503 is also used for:

[0088] In response to the notification requirement of the message to be pushed, a repeat notification task corresponding to the message to be pushed is created.

[0089] In response to the expiration of the recurring notification task corresponding to the message to be pushed, determine the push status of the message to be pushed;

[0090] If the push status of the message to be pushed is incomplete, generate a duplicate notification message for the message to be pushed and push it to the target device; if the push status of the message to be pushed is completed, delete the duplicate notification task corresponding to the message to be pushed.

[0091] According to a third aspect of the present disclosure, an electronic device for push notifications is provided, comprising: one or more processors; and a storage device for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the method provided in the first aspect of the present invention.

[0092] According to a fourth aspect of the present disclosure, a computer-readable medium is provided having a computer program stored thereon, which, when executed by a processor, implements the method provided in the first aspect of the present invention.

[0093] According to a fifth aspect of the present invention, a computer program product is provided, comprising a computer program that, when executed by a processor, implements the method of any of the above embodiments.

[0094] Figure 6 An exemplary system architecture 600 is shown that can be applied to the message push method or message push device implemented in this disclosure.

[0095] like Figure 6 As shown, system architecture 600 may include terminal devices 601, 602, and 603, a network 604, and a server 605. Network 604 serves as the medium for providing communication links between terminal devices 601, 602, and 603 and server 605. Network 604 may include various connection types, such as wired or wireless communication links, or fiber optic cables, etc.

[0096] Users can use terminal devices 601, 602, and 603 to interact with server 605 via network 604 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 601, 602, and 603, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social media platform software, etc. (for example only).

[0097] Terminal devices 601, 602, and 603 can be various electronic devices with displays and web browsing capabilities, including but not limited to smartphones, tablets, laptops, and desktop computers.

[0098] Server 605 can be a server that provides various services, such as a backend management server (for example only) that supports shopping websites browsed by users using terminal devices 601, 602, and 603. The backend management server can process received push message requests and send the processing results (for example only) back to the terminal devices.

[0099] It should be noted that the message push method provided in this embodiment of the invention is generally executed by server 605, and correspondingly, the message push device is generally set in server 605. The message push method provided in this embodiment of the invention can also be executed by terminal devices 601, 602, and 603, and correspondingly, the message push device can be set in terminal devices 601, 602, and 603.

[0100] It should be understood that Figure 6 The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.

[0101] The following is for reference. Figure 7 It shows a schematic diagram of the structure of a computer system 700 suitable for implementing a terminal device of the present invention. Figure 7 The terminal device shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of the present invention.

[0102] like Figure 7 As shown, the computer system 700 includes a central processing unit (CPU) 701, which can perform various appropriate actions and processes based on programs stored in read-only memory (ROM) 702 or programs loaded from storage section 708 into random access memory (RAM) 703. The RAM 703 also stores various programs and data required for the operation of the system 700. The CPU 701, ROM 702, and RAM 703 are interconnected via a bus 704. An input / output (I / O) interface 705 is also connected to the bus 704.

[0103] The following components are connected to the I / O interface 705: an input section 706 including a keyboard, mouse, etc.; an output section 707 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 708 including a hard disk, etc.; and a communication section 709 including a network interface card such as a LAN card, modem, etc. The communication section 709 performs communication processing via a network such as the Internet. A drive 710 is also connected to the I / O interface 705 as needed. A removable medium 711, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on the drive 710 as needed so that computer programs read from it can be installed into the storage section 708 as needed.

[0104] In particular, according to the embodiments disclosed in this invention, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this invention include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 709, and / or installed from removable medium 711. When the computer program is executed by central processing unit (CPU) 701, it performs the functions defined above in the system of this invention.

[0105] It should be noted that the computer-readable medium shown in this invention can be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this invention, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this invention, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media can also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.

[0106] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0107] The modules described in the embodiments of the present invention can be implemented in software or hardware. The described modules can also be set in a processor. For example, a processor includes a determining module, an acquiring module, and a pushing module. The names of these modules do not necessarily limit the module itself. For example, the determining module can also be described as "a module that determines each candidate account associated with the target device based on the account association operation initiated by the user".

[0108] In another aspect, the present invention also provides a computer-readable medium, which may be included in the device described in the above embodiments; or it may exist independently and not assembled into the device. The computer-readable medium carries one or more programs, and when the one or more programs are executed by the device, the device implements the following method: based on an account association operation initiated by a user, determining each candidate account associated with a target device; obtaining at least one target account selected by the user from each candidate account; receiving a message to be pushed corresponding to the target account; and pushing the message to be pushed corresponding to the target account to the target device.

[0109] Finally, it should be noted that the above embodiments are merely specific implementations of this disclosure, used to illustrate the technical solutions of this disclosure, and not to limit it. The protection scope of this disclosure is not limited thereto. Although this disclosure has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that any person skilled in the art can still modify or easily conceive of changes to the technical solutions described in the foregoing embodiments, or make equivalent substitutions for some of the technical features, within the scope of the technology disclosed in this disclosure. Such modifications, changes, or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this disclosure, and should all be covered within the protection scope of this disclosure. Therefore, the protection scope of this disclosure should be determined by the protection scope of the claims.

Claims

1. A message push method, characterized in that, include: Based on the user-initiated account association operation, determine each candidate account associated with the target device; Obtain at least one target account selected by the user from each candidate account, and receive the message to be pushed corresponding to the target account; The message to be pushed to the target account is pushed to the target device.

2. The method according to claim 1, characterized in that, Based on the user-initiated account association operation, the candidate accounts associated with the target device are identified, including: Obtain user-uploaded account data and verify the login status of each account to be associated in the account data; In response to the valid login status of the account to be associated, the account to be associated is identified as a candidate account to be associated with the target device.

3. The method according to claim 1, characterized in that, Before pushing the message to be pushed to the target account to the target device, the method further includes: Determine the message receiving type of the target account; The message to be pushed, corresponding to the message receiving type, is pushed to the target device.

4. The method according to claim 3, characterized in that, Determining the message receiving type of the target account includes: Determine whether the configuration information stored in the local storage location includes a message receiving type corresponding to the target account; In response to the configuration information including a message receiving type corresponding to the target account, the message receiving type configured by the user for the target account is obtained from the local storage location; In response to the fact that the configuration information does not include a message receiving type corresponding to the target account, the message receiving type configured by the user for the target account is obtained to determine the message receiving type corresponding to the target account.

5. The method according to claim 1, characterized in that, Before pushing the message to be pushed to the target account to the target device, the method further includes: Based on the message type of the message to be pushed, the notification requirement of the message to be pushed is determined, and the message is pushed to the target device based on the notification requirement.

6. The method according to claim 5, characterized in that, The method further includes: In response to the notification requirement of the message to be pushed being repeated, a repeated notification task corresponding to the message to be pushed is created; In response to the expiration of the recurring notification task corresponding to the message to be pushed, the push status of the message to be pushed is determined; If the push status of the message to be pushed is incomplete, generate a duplicate notification message for the message to be pushed and push it to the target device; if the push status of the message to be pushed is completed, delete the duplicate notification task corresponding to the message to be pushed.

7. A message push device, characterized in that, include: The determination module is used to determine each candidate account associated with the target device based on the account association operation initiated by the user. The acquisition module is used to acquire at least one target account selected by the user from each candidate account, and to receive the message to be pushed corresponding to the target account; The push module is used to push the message to be pushed corresponding to the target account to the target device.

8. An electronic device, characterized in that, include: One or more processors; Storage device for storing one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors implement the method as described in any one of claims 1-6.

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

10. A computer program product comprising a computer program that, when executed by a processor, implements the method according to any one of claims 1-6.

Images