Method for sending, method for receiving, terminal, device and medium for reminding message

By introducing reminder messages and reminder assistant mini-programs in the instant messaging program, users can set limited reminder permissions on the authorization interface, solving the privacy leakage and information harassment problems caused by the establishment of friend relationships in the social scenario of strangers, and achieving further Safe social communication.

CN112083983BActive Publication Date: 2024-11-22GUANGZHOU TENCENT TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN201910517470.8
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2019-06-14
Publication Date
2024-11-22
Estimated Expiration
2039-07-25

AI Technical Summary

Technical Problem

In instant messaging programs, in the accidental social scenario of strangers, communication between users can easily lead to unnecessary friend relationships, leading to personal privacy leakage and spam harassment.

Method used

Through the sending and receiving methods of reminder messages, using the reminder topic and reminder assistant applet, users can grant limited reminder permissions on the authorization reminder interface, including limited time and limited number of times, to avoid establishing formal friend relationships.

Benefits of technology

It effectively avoids unnecessary friend relationship establishment, protects users' personal privacy, reduces information harassment, relieves social pressure, and simplifies the process of sending reminder messages.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN112083983B_ABST
    Figure CN112083983B_ABST
Patent Text Reader

Abstract

The present application discloses a method for sending, receiving, terminal, device and medium of a reminder message, and relates to the field of computer networks. The receiving method comprises: obtaining the subject title of a reminder subject; displaying the authorization reminder interface of the reminder subject according to the subject title of the reminder subject; after receiving an authorization operation on the authorization reminder interface, granting the reminder subject a reminder permission with limited conditions, wherein the limited conditions include at least one of limited time and limited number of times; and receiving a reminder message of the reminder subject. The sending method comprises: displaying a creation interface of a reminder subject; creating the reminder subject according to the creation operation received in the creation interface; obtaining the authorized user corresponding to the reminder subject, wherein the authorized user is a user account that grants the reminder subject a reminder permission with limited conditions, and sending a reminder message to the authorized user corresponding to the reminder subject.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of computer networks, and in particular to a method for sending, a method for receiving, a terminal, a device and a medium for sending a reminder message. Background Art

[0002] When implementing point-to-point communication in an instant messaging program, users need to add each other as friends.

[0003] In the related art, user A uses an instant messaging program to scan the QR code of user B and add user B as a friend in the instant messaging program. Then, user A uses the instant messaging program to send an instant messaging message to user B, and user B uses the instant messaging program to receive the instant messaging message sent by user A.

[0004] In many occasional social scenarios with strangers, user A and user B will only communicate a few times and then never communicate again. Therefore, the above technical solution will generate unnecessary friend relationships, increase the complexity of the social relationship chain, and leak the user's contact information to strangers, resulting in user privacy leakage and spam harassment. Summary of the invention

[0005] The embodiments of the present application provide a method for sending, a method for receiving, an apparatus, a terminal and a device for reminding messages, which can solve the problem in the related art that in the occasional social scene of strangers, unnecessary friendships are generated when users communicate with each other, resulting in the leakage of user privacy and spam harassment. The technical solution is as follows:

[0006] According to one aspect of the present application, a method for receiving a reminder message is provided, the method comprising:

[0007] Get the topic title of the reminder topic;

[0008] According to the subject title of the reminder subject, display the authorization reminder interface of the reminder subject;

[0009] After receiving the authorization operation on the authorization reminder interface, granting the reminder subject a reminder permission with limited conditions, wherein the limited conditions include at least one of limited time and limited number of times;

[0010] Receive a reminder message of the reminder topic.

[0011] According to another aspect of the present application, a method for receiving a reminder message is provided, which is applied to a terminal having a first host program and a first reminder assistant applet installed therein, wherein the first reminder assistant applet depends on the first host program to run, and the method includes:

[0012] Scanning a graphic code corresponding to the reminder theme through the first host program;

[0013] Obtaining a subject title corresponding to the reminder subject from the graphic code;

[0014] Calling the first reminder assistant applet through the first host program, and displaying the authorization reminder interface of the reminder subject according to the subject title of the reminder subject through the first reminder assistant applet;

[0015] After receiving the authorization operation on the authorization reminder interface, granting the reminder subject a reminder permission with limited conditions, wherein the limited conditions include at least one of limited time and limited number of times;

[0016] The reminder message of the reminder topic is received through the first reminder assistant applet.

[0017] According to another aspect of the present application, a method for sending a reminder message is provided, the method comprising:

[0018] Display the reminder topic creation interface;

[0019] Creating the reminder topic according to the creation operation received in the creation interface;

[0020] Obtaining an authorized user corresponding to the reminder subject, wherein the authorized user is a user account that grants the reminder subject a reminder authority with limited conditions, wherein the limited conditions include at least one of limited time and limited number of times;

[0021] Send a reminder message to the authorized user corresponding to the reminder topic.

[0022] According to another aspect of the present application, a method for sending a reminder message is provided, which is applied to a terminal having a second host program and a second reminder assistant applet installed therein, wherein the second reminder assistant applet depends on the second host program to run, and the method includes:

[0023] Displaying a reminder topic creation interface through the second reminder assistant applet;

[0024] Creating the reminder topic through the second reminder assistant applet according to the creation operation received in the creation interface;

[0025] Obtaining, through the second reminder assistant applet, an authorized user corresponding to the reminder subject, wherein the authorized user is a user account that grants the reminder subject a reminder permission with limited conditions, wherein the limited conditions include at least one of limited time and limited number of times;

[0026] Send a reminder message to the authorized user corresponding to the reminder topic through the second reminder assistant applet.

[0027] According to another aspect of the present application, a method for sending a reminder message is provided, the method comprising:

[0028] Receive the authorization instruction sent by the First Reminder Assistant applet;

[0029] Granting reminder authority with limited conditions to the reminder subject according to the authorization instruction;

[0030] Receive a reminder message of the reminder topic sent by the second reminder assistant applet;

[0031] When the reminder message meets the limited condition, the reminder message is sent to the first reminder assistant applet.

[0032] According to another aspect of the present application, a device for receiving a reminder message is provided, the device comprising:

[0033] An acquisition module is used to obtain the subject title of the reminder subject;

[0034] A display module, used to display the authorization reminder interface of the reminder subject according to the subject title of the reminder subject;

[0035] A receiving module, configured to grant a reminder permission with limited conditions to the reminder subject after receiving the authorization operation on the authorization reminder interface, wherein the limited conditions include at least one of limited time and limited number of times;

[0036] The receiving module is also used to receive a reminder message of the reminder topic.

[0037] According to another aspect of the present application, a device for receiving a reminder message is provided, the device comprising:

[0038] A display module, used to display a reminder topic creation interface;

[0039] The receiving module is used to create a reminder topic according to the creation operation received in the creation interface;

[0040] An acquisition module, used to acquire an authorized user corresponding to a reminder subject, where the authorized user is a user account that grants a reminder permission with limited conditions to the reminder subject, where the limited conditions include at least one of a limited time and a limited number of times;

[0041] The sending module is used to send messages to authorized users corresponding to the reminder topic.

[0042] According to another aspect of the present application, a device for receiving a reminder message is provided, the device comprising:

[0043] A scanning module, used for scanning a graphic code corresponding to the reminder theme through the first host program;

[0044] An acquisition module, used to acquire a subject title corresponding to the reminder subject from the graphic code;

[0045] A display module, used to call the first reminder assistant applet through the first host program, and display the authorization reminder interface of the reminder subject according to the subject title of the reminder subject through the first reminder assistant applet;

[0046] A receiving module, configured to grant a reminder permission with limited conditions to the reminder subject after receiving the authorization operation on the authorization reminder interface, wherein the limited conditions include at least one of limited time and limited number of times;

[0047] The receiving module is also used to receive a reminder message of the reminder topic through the first reminder assistant applet.

[0048] According to another aspect of the present application, a device for receiving a reminder message is provided, the device comprising:

[0049] A display module, used to display a creation interface of a reminder topic through a second reminder assistant applet;

[0050] A receiving module, used to create a reminder topic according to the creation operation received in the creation interface through the second reminder assistant applet;

[0051] An acquisition module, used to acquire an authorized user corresponding to a reminder subject through a second reminder assistant applet, wherein the authorized user is a user account that grants a reminder permission with limited conditions to the reminder subject, wherein the limited conditions include at least one of a limited time and a limited number of times;

[0052] The sending module is used to send a reminder message to the authorized user corresponding to the reminder topic through the second reminder assistant applet.

[0053] According to another aspect of the present application, a terminal is provided, comprising: a host program and a reminder assistant applet; the reminder assistant applet depends on the host program to run, and the terminal is used to implement the reminder message receiving method and reminder message sending method as described above.

[0054] According to another aspect of the present application, a computer-readable storage medium is provided, in which at least one instruction, at least one program, a code set or an instruction set is stored, and the at least one instruction, the at least one program, the code set or the instruction set is loaded and executed by the processor to implement the method for receiving a reminder message and the method for sending a reminder message as described above.

[0055] The beneficial effects brought by the technical solution provided by the embodiment of the present application include at least:

[0056] A communication relationship is established between the second client (sender) and the first client (receiver) by creating a reminder topic, and the recipient authorizes the reminder topic under limited conditions (including at least one of a limited time and a limited number of times). There is no need for the sender and the receiver to establish a friend relationship. Instead, the reminder topic is used as a communication link, which avoids the generation of unnecessary friend relationships, personal privacy leaks and information harassment between users in accidental social scenarios with strangers, and alleviates the social pressure of users. BRIEF DESCRIPTION OF THE DRAWINGS

[0057] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0058] Figure 1 This is a schematic diagram of an interface in a reminder assistant applet provided by an exemplary embodiment of the present application;

[0059] Figure 2 is a block diagram of an implementation environment provided by an exemplary embodiment of the present application;

[0060] Figure 3 is a flowchart of a method for receiving a reminder message provided by an exemplary embodiment of the present application;

[0061] Figure 4 is a flow chart of a method for sending a reminder message provided by an exemplary embodiment of the present application;

[0062] Figure 5 is a flowchart of a method for sending a reminder message provided by another exemplary embodiment of the present application;

[0063] Figure 6 is a flowchart of a method for receiving a reminder message provided by another exemplary embodiment of the present application;

[0064] Figure 7 is a structural block diagram of a terminal provided by an exemplary embodiment of the present application;

[0065] Figure 8 is a flowchart of a method for a reminder assistant applet to send a reminder message provided by another exemplary embodiment of the present application;

[0066] Fig. 9 is a flowchart of a method for a reminder assistant applet to receive a reminder message provided by another exemplary embodiment of the present application;

[0067] Fig.10This is a schematic diagram of an interface for creating a reminder theme in a reminder assistant applet provided by an exemplary embodiment of the present application;

[0068] Fig.11 This is a schematic diagram of an interface of a reminder assistant applet displaying a graphic code corresponding to a reminder theme provided by an exemplary embodiment of the present application;

[0069] Fig.12 This is a schematic diagram of the interface of the reminder assistant applet authorization process provided by an exemplary embodiment of the present application;

[0070] Fig.13 This is a schematic diagram of the interface for sending a reminder message of a reminder assistant applet provided by an exemplary embodiment of the present application;

[0071] Fig.14 This is a schematic diagram of an interface for a reminder assistant applet to receive a reminder message provided by an exemplary embodiment of the present application;

[0072] Fig.15 It is a structural diagram of a device for receiving a reminder message provided by an exemplary embodiment of the present application;

[0073] Fig.16 It is a structural diagram of a device for sending a reminder message provided by an exemplary embodiment of the present application;

[0074] Fig.17 is a structural diagram of a device for receiving a reminder message provided by another exemplary embodiment of the present application;

[0075] Fig.18 It is a schematic diagram of the device structure of an electronic device provided by an exemplary embodiment of the present application. DETAILED DESCRIPTION

[0076] In order to make the objectives, technical solutions and advantages of the present application clearer, the implementation methods of the present application will be further described in detail below with reference to the accompanying drawings.

[0077] First, the nouns involved in the embodiments of the present application are introduced:

[0078] Reminder: It reminds the user of something that may be forgotten. Some applications in the terminal have the reminder function, such as reminder items, memos, and To do lists. Users can create reminder topics that need to be reminded through memos. For example, the user creates a reminder topic on the memo: take medicine at 1 p.m. When the time is 1 p.m., the memo will send a reminder message to remind the user that it is time to take medicine.

[0079] Strong reminder: refers to strengthening the reminder in a way that makes it difficult for users to ignore the content of the reminder theme. For example, the same reminder theme is: take medicine at 1 pm. When the time is 1 pm, in the case of a strong reminder, the terminal will generate a special ringing, flashing signal light, vibration, and display at least one of the reminder content. The user needs to operate the reminder content on the terminal application, such as canceling the reminder or delaying the reminder, and the terminal will stop generating special ringing, flashing signal light, vibration, and displaying at least one of the reminder content. Compared with the ordinary reminder method, the above-mentioned strong reminder method requires the user to manually change the reminder, and the reminder message is less likely to be ignored.

[0080] Sender: refers to the user (or user account) who sends the reminder message. The user sends a reminder message to other users through the reminder assistant applet or an application with reminder function (including the host program that the applet depends on). The reminder message includes: the name of the reminder topic and at least one of the reminder content.

[0081] Recipient: refers to the user (or user account) who receives the reminder message. The user receives reminder messages from other users through the reminder assistant applet or an application with reminder function (including the host program that the applet depends on), and the reminder message interface is displayed on the terminal display screen, or the terminal reminds in at least one of a ringtone, a flashing signal light, and a vibration. The reminder message includes: at least one of the name of the reminder topic and the content of the reminder topic.

[0082] Reminder topic: In some embodiments, it is also called a reminder event, which is not limited in this application. It refers to the topic on which the reminder message is based. The reminder topic includes: at least one of the reminder topic title and the reminder topic content. For example, the reminder topic is a patent application sharing meeting, and the reminder message is to attend the patent application sharing meeting at 3 pm.

[0083] Reminder QR code: refers to the QR code corresponding to the reminder subject. The recipient receives the reminder message by scanning the reminder QR code.

[0084] Scan code authorization: When the recipient scans the reminder QR code, he / she needs to perform authorization operation and grant valid reminder permissions to the reminder subject. After performing the authorization operation, he / she will receive the reminder message.

[0085] Send reminder message: When at least one recipient scans the reminder QR code and authorizes, the sender can send a reminder message to the recipient.

[0086] When implementing point-to-point communication in an instant messaging program, users need to add each other as friends to establish a communication relationship. The way to add friends includes at least one of the following ways: user A uses a camera to scan user B's QR code, user A searches for user B's account, username or nickname in the instant messaging program, queries user B's account and other information in the instant messaging program through user B's phone number in the address book, and queries user B's account and other information in the instant messaging program through the radar function in the instant messaging program. When user A successfully adds user B as a friend, user A can use the instant messaging program to send instant messaging messages to user B, and user B can use the instant messaging program to receive instant messaging messages sent by user A.

[0087] In the occasional social scene of strangers, user A and user B will only communicate a few times and then never communicate again. For example, when user A receives a courier, the courier (user B) sends an instant messaging message to user A through a logistics-related instant messaging program (such as Taobao program, Cainiao GOGO program, Fengchao program, etc.), reminding user A to collect the courier. After user A collects the courier, the communication with user B on the logistics-related instant messaging program will be terminated, but user A and user B are still friends on the logistics-related instant messaging program. In this way, user B knows user A's personal information, which increases the complexity of user A's social relationship chain. In serious cases, it is easy to cause user privacy leakage and spam harassment, and put a certain amount of social pressure on user A.

[0088] The method provided in the present application can be applied to an application (host program), or an application (host program) with a reminder function, or a small program with a reminder function that depends on a host program. The following embodiments are described by applying the method to an application and a small program with a reminder function that depends on a host program.

[0089] Take the method of receiving reminder messages applied to a strong reminder assistant applet that depends on the host program as an example for explanation. Figure 1 FIG. 1 shows a schematic diagram of an interface in a strong reminder assistant applet provided by an exemplary embodiment of the present application. Figure 1 As shown in (a), the interface 11 of the strong reminder assistant applet includes: information 111 of the reminder subject (including: the QR code corresponding to the reminder subject, the title of the reminder subject and the number of users who receive the reminder message), a virtual button 112 for editing the reminder content and a menu virtual button 113 for the QR code corresponding to the reminder subject. The host program scans the QR code corresponding to the reminder subject, such as Figure 1As shown in (b), the scanning interface 12 includes: a graphic code scanning box 114, a code scanning option 115, an auxiliary lighting option 116 and a return virtual button 117. When the user scans the QR code corresponding to the reminder subject, an authorization reminder interface 13 is generated, such as Figure 1 As shown in (c), the authorization reminder interface 13 includes: reminder subject information 118 (including the title of the reminder subject and the reminder mode of the reminder subject, such as receiving a strong reminder), a confirmation authorization option 119, a cancellation authorization option 121, and an option 122 to close the authorization reminder interface. After the user authorizes to receive reminder messages, the reminder message corresponding to the reminder subject is received in a variety of ways, such as receiving the reminder message in the service notification message bar in the message interface. In one example, the reminder message is displayed in the lock screen interface 20 of the terminal, such as Figure 1 As shown in (d), the lock screen interface 20 displays a prompt message 132 and an "I know" virtual button 133 indicating that the strong reminder assistant applet has sent a reminder message. The prompt message 132 is used to prompt the user to receive the reminder message. In one example, the reminder message does not display the detailed content of the message. The "I know" virtual button 133 is used by the user to close the reduced screen interface 20 that displays the reminder message. In some embodiments, the "I know" virtual button 133 is also named as an "I know" virtual button, a "Cancel reminder" virtual button, a close virtual button, etc., which is not limited in this application. The user can view the reminder subject operation, or delete the authorized reminder subject, and cancel the reminder permission granted to the reminder subject according to the deletion operation.

[0090] Figure 2 The following is a block diagram of a computer system provided by an exemplary embodiment of the present application. The computer system 100 includes: a first terminal 120 , a server 140 , and a second terminal 160 .

[0091] The first terminal 120 has an application program that supports instant messaging installed and running, or a reminder assistant applet installed and running. The application program can be any one of the Internet Pager (ICQ), Skype, Microsoft Network Service (MSN), QQ or WeChat produced by Tencent Technology Co., Ltd. of China, Feiqiu, Feige, and Taobao, Aliwangwang, and Cainiao Guoguo produced by Alibaba Group of China, or a small program that depends on the host program. The first terminal 120 is a terminal used by the first user. The first user uses the instant messaging program on the first terminal 120 to send an instant messaging message, which includes but is not limited to: at least one of text, voice, picture, video, music, web link, file, and reminder message. Indicatively, the message is a reminder message.

[0092] The first terminal 120 is connected to the server 140 via a wireless network or a wired network.

[0093] The server 140 includes at least one of a single server, multiple servers, a cloud computing platform, and a virtualization center. Schematically, the server 140 includes a processor 144 and a memory 142, and the memory 142 includes a display module 1421, a receiving and sending module 1422, and an acquisition module 1423. The server 140 is used to provide background services for applications that support three-dimensional virtual environments. Optionally, the server 140 undertakes the main computing work, and the first terminal 120 and the second terminal 160 undertake the secondary computing work; or, the server 140 undertakes the secondary computing work, and the first terminal 120 and the second terminal 160 undertake the main computing work; or, the server 140, the first terminal 120 and the second terminal 160 adopt a distributed computing architecture for collaborative computing.

[0094] The second terminal 160 installs and runs an application that supports instant messaging, or has a reminder assistant applet installed. The application can be any one of an Internet pager (ICQ), Skype, Microsoft Service Network (MSN), QQ or WeChat (Wechat) produced by Tencent Technology Co., Ltd. of China, Feiqiu, Feige, and Taobao, Aliwangwang, and Cainiao Guoguo produced by Alibaba Group of China, or a small program that depends on the host program. The first terminal 120 is a terminal used by the first user. The first user uses the instant messaging program on the first terminal 120 to send an instant messaging message, which includes but is not limited to: at least one of text, voice, picture, video, music, web link, file, and reminder message. Indicatively, the message is a reminder message.

[0095] Optionally, the applications installed on the first terminal 120 and the second terminal 160 are the same, or the applications installed on the two terminals are the same type of applications on different control system platforms. The first terminal 120 may refer to one of a plurality of terminals, and the second terminal 160 may refer to one of a plurality of terminals. This embodiment is only illustrated by the first terminal 120 and the second terminal 160. The device types of the first terminal 120 and the second terminal 160 are the same or different, and the device types include at least one of a smart phone, a tablet computer, an e-book reader, an MP3 player, an MP4 player, a laptop portable computer, and a desktop computer. The following embodiments are illustrated by taking the terminal including a smart phone as an example.

[0096] Those skilled in the art will appreciate that the number of the above terminals may be more or less. For example, the above terminal may be only one, or the above terminals may be dozens or hundreds, or more. The embodiment of the present application does not limit the number of terminals and device types.

[0097] Figure 3 A method for receiving a reminder message provided by an exemplary embodiment of the present application is shown. The method is applied to Figure 2 In the first terminal 120 or the second terminal 160 of the computing system shown or in other terminals in the computer system. The method comprises the following steps:

[0098] Step 301, obtain the subject title of the reminder subject.

[0099] The first client (receiver) obtains the topic title of the reminder topic by scanning a graphic code, clicking a link, clicking a virtual button on the application interface (eg, a "Join" virtual button, a "Follow" virtual button, etc.).

[0100] Illustratively, the subject title of the reminder topic includes at least one of the following forms: participating in an activity, work arrangement, collecting items, disease treatment, etc. In one example, the subject title of the reminder topic is participating in an activity, such as participating in a patent application sharing meeting.

[0101] Step 302: displaying the authorization reminder interface of the reminder topic according to the topic title of the reminder topic.

[0102] The first client (receiver) displays an authorization reminder interface of the reminder subject according to the subject title of the reminder subject, and the authorization reminder interface is used to remind the recipient to perform authorization operation.

[0103] If the user needs to receive reminder messages, the authorization operation needs to be performed on the authorization reminder interface. Optionally, the authorization reminder interface includes at least one of the following forms of information: reminder authorization symbol (for example: an exclamation mark with a warning mark or reminder meaning, with any color or shape, which is not limited in this application), authorized account, nickname, user name, authorization time, authorization content (including: some functions on the terminal operating system, such as at least one of the recording function, camera function, positioning function, microphone function, and receiver function, or the recipient's phone number, email address and other personal information, or the recipient's hobbies, social circle, etc.).

[0104] Indicatively, the recipient displays an authorization reminder interface of the reminder subject in an authorization manner of an authorized account and a nickname.

[0105] Step 303: after receiving the authorization operation on the authorization reminder interface, granting the reminder subject a reminder permission with limited conditions, wherein the limited conditions include at least one of limited time and limited number of times.

[0106] The first client performs an authorization operation, and after receiving the authorization operation on the authorization reminder interface, grants a reminder permission with limited conditions to the reminder subject.

[0107] Optionally, the limited condition includes at least one of limited time and limited number of times. Limited time means that the sender can send the reminder message within a certain period of time, and limited number of times means that the sender can send the reminder message a limited number of times.

[0108] Illustratively, the limited condition includes both limited time and limited number of times. For example, the sender grants three reminder permissions to the reminder subject within one hour, that is, the sender can send reminder messages of the reminder subject three times within one hour.

[0109] Optionally, the first client (receiver) can set the authorization operation of the reminder subject according to actual conditions, usage habits, personal preferences, etc., or the authorization operation of the first client (receiver) is already set by the background server (default setting). Setting the authorization operation includes at least one of the following forms: authorization times and authorization time. In one example, the recipient sets the authorization for the reminder subject twice.

[0110] Optionally, the first client (recipient) authorizes the reminder topic arbitrarily (including at least one of the following methods: arbitrary number of authorizations and arbitrary time for authorization operations). In one example, the reminder topic is created at 10:00 a.m., and both user A and user B receive reminder messages for the reminder topic. User A authorizes the reminder topic twice, at 10:00 a.m. and 10:10 a.m.; user B authorizes the reminder topic ten times, starting from 11:00 a.m. and authorizing once every 30 minutes.

[0111] Step 304, receiving a reminder message of the reminder topic.

[0112] After the first client (receiver) performs authorization operation on the reminder subject, the reminder message of the reminder subject can be received.

[0113] Optionally, the reminder message includes: at least one of: a subject title of the reminder topic, subject content of the reminder topic, a reminder time of the reminder topic, and an expiration time of the reminder topic. Schematically, the reminder message includes the subject title and content of the reminder topic. For example, after the recipient authorizes the reminder topic, the recipient receives a reminder message of the reminder topic. The subject title of the reminder topic is Patent Application Sharing Session, and the subject content of the reminder topic is 3 pm, Room 101, Building A, please attend the meeting on time. That is, the recipient receives a reminder message about the time and place of the patent application sharing session.

[0114] To sum up, the method provided in this embodiment establishes a communication relationship with the first client (receiver) by creating a reminder topic through the second client (sender), and the reminder topic is authorized by the receiver under limited conditions (including at least one of limited time and limited number of times). There is no need for the sender and the receiver to establish a friend relationship. Instead, the reminder topic is used as a communication link, which avoids the generation of unnecessary friend relationships, personal privacy leaks and information harassment between users in accidental social scenarios with strangers, and alleviates the social pressure of users.

[0115] Based on the default settings of the background server, the second client (sender) grants a valid reminder permission to the reminder subject once, which simplifies the operation steps of the sender when sending reminder messages and improves the efficiency of sending reminder messages; when the sender can set the reminder permission with limited conditions, the user can set the limited conditions (including: at least one of limited time and limited number of times) according to his personal habits and preferences, realizing the user's personalized setting function.

[0116] Figure 4 A flowchart showing a method for sending a reminder message provided by an exemplary embodiment of the present application is shown. The method is applied to Figure 2 In the first terminal 120 or the second terminal 160 of the computing system shown or in other terminals in the computer system. The method comprises the following steps:

[0117] Step 401, displaying a reminder topic creation interface.

[0118] The creation interface of the reminder topic is displayed on the second client (sender). Optionally, the creation interface is an interface in an application with a reminder function, or an interface in a small program with a reminder function that depends on a host program. Schematically, the creation interface is an interface in an application with a reminder function. For example, the creation interface of the reminder topic is displayed on the memo application on the second client.

[0119] Optionally, the creation interface includes at least one of the following information: the title of the reminder theme, the content of the reminder theme, the effective time of the reminder, the expiration time of the reminder, the sending time of the reminder message, the receiving time of the reminder message, and notes. Schematically, the creation interface includes the title of the reminder theme as an example for explanation. For example, the sender creates a reminder theme by inputting the title of the reminder theme (for example, an open class on the application of mathematics) on the creation interface. Schematically, the creation interface includes the title of the reminder theme, the content of the reminder theme and notes as an example for explanation. For example, the sender creates a reminder theme by inputting the title of the reminder theme (for example, an open class on the application of mathematics), the content of the reminder theme (for example, the application of mathematics in life and the application of mathematics in other subjects) and notes (for example, the open class time is from 10:00 to 11:30, with a 20-minute break in between, please bring your own computer) on the creation interface.

[0120] Step 402: Create a reminder topic according to the creation operation received in the creation interface.

[0121] The second client (sender) performs a creation operation and creates a reminder topic according to the creation operation received in the creation interface.

[0122] Optionally, the creation operation is to perform a creation operation on at least one of the following information: the subject title of the reminder subject, the subject content of the reminder subject, the reminder effective time, the reminder expiration time, the reminder message sending time, the reminder message receiving time, notes, etc. The reminder subject is created according to the sender's creation information. Schematically, the sender performs a creation operation on the subject title of the reminder subject.

[0123] For example, the sender creates a reminder topic with the subject title of Project Scheduling Workshop Reminder Topic.

[0124] Step 403, obtain the authorized user corresponding to the reminder subject, the authorized user is a user account that grants the reminder subject a reminder permission with limited conditions, and the limited conditions include at least one of limited time and limited number of times. Limited time means that the sender can send reminder messages within a certain period of time, and limited number of times means that the sender can send reminder messages a limited number of times.

[0125] The second client (sender) obtains the authorized user corresponding to the reminder subject, where the authorized user is a user account that grants the reminder subject a reminder authority with limited conditions.

[0126] Optionally, the user account of the authorized user is an account registered by the user on an application with a reminder function. The account can be a mobile phone number, email address, or an account on a third-party application (for example, a WeChat account, QQ number, Weibo account, Baidu account, Taobao account, Alipay account, etc.) used by the user. The authorized user can use the above user account to grant reminder permissions to the reminder subject.

[0127] Optionally, the limited condition includes at least one of a limited time and a limited number of times. The limited time means that the sender can send the reminder message within a certain period of time, and the limited number of times means that the sender can send the reminder message a limited number of times.

[0128] Optionally, the limited time is arbitrary, and the limited number of times is any integer greater than zero. The developer can set the limited time and limited number of times through the background server, or the user can set the limited time and limited number of times through the application. Indicatively, the limited condition is a limited time and a limited number of times, for example, the sender sends three reminder messages to the authorized user within three hours. Optionally, when the sender exceeds any of the limited time or the limited number of times, the operation of sending a reminder message cannot be performed. Indicatively, when the sender has sent a reminder message a limited number of times (for example, three times), the sender can no longer continue to send reminder messages because the limited number of times has been exceeded. At this time, if the sender needs to send a reminder message, it is necessary to recreate the reminder topic.

[0129] Optionally, the first client (receiver) can set the authorization operation of the reminder subject according to actual conditions, usage habits, personal preferences, etc., or the authorization operation of the first client (receiver) is already set by the background server (default setting). Setting the authorization operation includes at least one of the following forms: authorization times and authorization time. In one example, the recipient sets the authorization for the reminder subject twice.

[0130] Optionally, the first client (recipient) authorizes the reminder topic arbitrarily (including at least one of the following methods: arbitrary number of authorizations and arbitrary time for authorization operations). In one example, the reminder topic is created at 10:00 a.m., and both user A and user B receive reminder messages for the reminder topic. User A authorizes the reminder topic twice, at 10:00 a.m. and 10:10 a.m.; user B authorizes the reminder topic ten times, starting from 11:00 a.m. and authorizing once every 30 minutes.

[0131] Step 404: Send a reminder message to the authorized user corresponding to the reminder topic.

[0132] After the second client (sender) obtains the authorized user corresponding to the reminder subject, it may send a reminder message to the authorized user corresponding to the reminder subject.

[0133] Optionally, the reminder message includes: at least one of: a subject title of the reminder topic, subject content of the reminder topic, a reminder time of the reminder topic, and an expiration time of the reminder topic. Schematically, the reminder message including the subject title and content of the reminder topic is taken as an example for explanation. For example, after the sender obtains the authorized user corresponding to the reminder topic, the reminder message is sent to the authorized user corresponding to the reminder topic. The subject title of the reminder topic is an open class on the application of mathematics, and the subject content of the reminder topic is the application of mathematics in life and the application of mathematics in other subjects. That is, the sender sends a reminder message about the relevant course content of the open class on the application of mathematics.

[0134] To sum up, the method provided in this embodiment establishes a communication relationship with the first client (receiver) by creating a reminder topic through the second client (sender), and the reminder topic is authorized by the receiver under limited conditions (including at least one of limited time and limited number of times). There is no need for the sender and the receiver to establish a friend relationship. Instead, the reminder topic is used as a communication link, which avoids the generation of unnecessary friend relationships, personal privacy leaks and information harassment between users in accidental social scenarios with strangers, and alleviates the social pressure of users.

[0135] The following describes the method for the backend server to send a reminder message to the client and the method for receiving a reminder message, respectively. Figure 5 and Figure 6 shown.

[0136] Figure 5 A flowchart of a method for sending a reminder message provided by another exemplary embodiment of the present application is shown. The method can be applied to Figure 2 In the first terminal 120 or the second terminal 160 of the computer system shown or in other terminals in the computer system. The method comprises the following steps:

[0137] Step 501: The second client displays a reminder topic creation interface.

[0138] The reminder topic creation interface is displayed on an application with a reminder function on the second client (sender). For example, the reminder topic creation interface is displayed on a memo application on the second client.

[0139] Step 502: The second client generates a reminder topic creation request according to the creation operation received in the creation interface. The reminder topic creation request carries a topic title of the reminder topic.

[0140] The second client (sender) performs a creation operation, and generates a creation request for a reminder topic according to the creation operation received in the creation interface, wherein the creation request for the reminder topic carries a topic title of the reminder topic. In one example, the creation request for the reminder topic may also include at least one of the topic content of the reminder topic, the reminder message sending time, the reminder message receiving time, the reminder effective time, and the reminder expiration time.

[0141] Step 503: The second client sends a request to create a reminder topic to the background server.

[0142] The second client sends a request to create a reminder topic to the background server.

[0143] Step 504: the backend server receives the creation request of the reminder topic, and the creation request carries the topic title of the reminder topic.

[0144] The backend server receives a creation request of a reminder topic sent by the second client, wherein the creation request includes any one of the options involved in the above embodiments. In one example, the creation request carries a topic title of the reminder topic.

[0145] Step 505: the backend server generates a topic identifier of the reminder topic according to the reminder topic creation request.

[0146] The backend server generates a topic ID for the reminder topic according to the reminder topic creation request. If there are multiple reminder topics, the same reminder topic ID is generated for multiple reminder topics; or, each reminder topic ID is generated for multiple reminder topics; or, a common group ID and corresponding sub-IDs are generated for multiple reminder topics.

[0147] Table 1 is used below to exemplify the correspondence between the subject identifier of a reminder subject, the subject title of a reminder subject, the subject content of a reminder subject, the user (authorized user) receiving the reminder message, and the limited conditional reminder authority.

[0148] Table 1

[0149]

[0150] Among them, the subject identifier 2019061320090001 of the reminder topic is used to represent the 0001th reminder topic at 13:09 on June 13, 2019. This embodiment does not limit the type of the subject identifier of the reminder topic. The subject title of the reminder topic in Table 1 is Participate in the Patent Application Sharing Conference. The number of authorized users of this reminder topic is 78 people, and the number of times each person receives the reminder message of the reminder topic is 3; the subject title of the reminder topic is Project Arrangement Meeting. The number of authorized users of this reminder topic is 10 people, and each person receives two reminder messages of the reminder topic within 20 minutes.

[0151] Step 506: The backend server sends a reminder topic creation response to the second client.

[0152] The backend server sends a creation response of the reminder topic to the second client, and the second client performs subsequent operations according to the creation response.

[0153] Step 507: The second client creates a reminder topic.

[0154] The second client successfully creates the reminder topic according to the creation response of the reminder topic sent by the background server.

[0155] Step 508: the backend server sends a reminder theme identifier to the second client, where the reminder theme identifier is used for the second client to display a graphic code corresponding to the reminder theme.

[0156] The backend server sends a reminder theme identifier to the second client. Optionally, the reminder theme identifier is used for the second client to display at least one of the following forms: a graphic code (e.g., a barcode, a QR code), a character verification code (e.g., including at least one type of text, numbers, and English), a link, a virtual button (e.g., a "join" virtual button, or a "follow" virtual button) corresponding to the reminder theme. In one example, the reminder theme identifier is used to display the graphic code corresponding to the reminder theme.

[0157] Step 509: The second client displays the graphic code corresponding to the reminder theme.

[0158] The second client displays a graphic code corresponding to the reminder theme. Optionally, the graphic code is a barcode or a QR code. In one example, the graphic code is a QR code.

[0159] To summarize, by scanning the graphic code to obtain the reminder subject, the operating steps for the first client (recipient) to obtain the reminder subject are simplified, the recipient can obtain the reminder subject more quickly, and the efficiency of the background server in counting authorized users is improved. The graphic code can be stored in a variety of ways (for example, electronic or paper version), so that the recipient can authorize the reminder subject in a variety of ways (for example, sending an electronic version of the graphic code through a terminal or printing the graphic code on paper).

[0160] Figure 6 A flowchart of a method for receiving a message provided by another exemplary embodiment of the present application is shown. The method can be applied to Figure 2 In the first terminal 120 or the second terminal 160 of the computer system shown or in other terminals in the computer system. The method comprises the following steps:

[0161] Step 510: The first client scans a graphic code corresponding to the reminder theme.

[0162] The first client (receiver) scans the graphic code corresponding to the reminder theme through the camera on the terminal. Optionally, the first client performs the scanning operation by authorizing the camera on the terminal to be turned on in the application with the reminder function, or the first client directly uses the camera on the terminal to perform the scanning operation. In one example, the recipient authorizes the camera on the terminal to be turned on in the application with the reminder function to scan the graphic code corresponding to the reminder theme.

[0163] Step 511: The first client obtains a topic title of a reminder topic.

[0164] The first client (receiver) obtains the subject title of the reminder subject by scanning the graphic code corresponding to the reminder subject.

[0165] Step 512: The first client displays an authorization reminder interface of the reminder topic according to the topic title of the reminder topic.

[0166] According to the subject title of the reminder subject obtained by the first client (receiver), an authorization reminder interface of the reminder subject is displayed on an application with a reminder function, and the authorized user of the first client authorizes the reminder subject by operating the authorization reminder interface.

[0167] Step 513: After receiving the authorization operation on the authorization reminder interface, the first client generates an authorization instruction, which carries the subject identifier and limited conditions of the reminder subject.

[0168] After receiving the authorization operation on the authorization reminder interface, the first client generates an authorization indication, which carries the subject identifier of the reminder subject and limited conditions.

[0169] Optionally, the authorization operation is clicking a corresponding authorization virtual button on the authorization interface, for example, the corresponding authorization virtual button on the authorization interface is an "OK" virtual button, or a "Join" virtual button, or a "Follow" virtual button. In one example, the authorization operation is to complete the authorization process by clicking a corresponding "OK" virtual button on the authorization interface.

[0170] The authorization instruction carries a subject identifier of the reminder subject and limited conditions. In one example, the authorization instruction also carries an account identifier of the authorized user.

[0171] Step 514: The first client sends an authorization instruction to the backend server.

[0172] The first client sends an authorization indication to the background server, where the authorization indication is used to instruct the background server to perform subsequent operations.

[0173] Step 515: the backend server receives the authorization instruction.

[0174] The background server receives the authorization indication sent by the first client, and the authorization indication includes at least one of the following indications: the authorized user's account, nickname, user name, authorization time, and authorization content (including: some functions on the terminal operating system, such as recording function, camera function, positioning function, microphone function, and at least one of the handset functions, or the recipient's phone number, email address and other personal information, or the recipient's interests, hobbies, social circle, etc.).

[0175] Step 516: the backend server queries the subject identifier of the corresponding reminder subject according to the authorization instruction.

[0176] The backend server queries the subject identifier of the corresponding reminder subject according to the received authorization instruction sent by the first client.

[0177] Step 517: the backend server sends an authorization indication corresponding to the subject identifier of the reminder subject to the second client.

[0178] When the background server queries the subject identifier of the reminder subject corresponding to the first client (receiver), it sends an authorization instruction corresponding to the subject identifier of the reminder subject to the second client (sender).

[0179] Step 518, the second client obtains the authorized user corresponding to the reminder subject, where the authorized user is a user account that grants the reminder subject a reminder authority with limited conditions, where the limited conditions include at least one of limited time and limited number of times.

[0180] The second client (sender) obtains the authorized user corresponding to the reminder subject according to the corresponding authorization instruction. In one example, the authorized user is a user account that grants reminder authority with limited conditions to the reminder subject. Optionally, the user account of the authorized user is an account registered by the user on an application with a reminder function. The account can be a mobile phone number, email address, or account on a third-party application used by the user (for example, a WeChat account, QQ number, Weibo account, Baidu account, Taobao account, Alipay account, etc.). The authorized user can use the above user account to grant reminder authority to the reminder subject.

[0181] Optionally, the limited condition includes at least one of a limited time and a limited number of times. The limited time means that the sender can send the reminder message within a certain period of time, and the limited number of times means that the sender can send the reminder message a limited number of times. In one example, the limited condition is that the sender can send the reminder message twice.

[0182] Optionally, the first client (receiver) can set the authorization operation of the reminder subject according to actual conditions, usage habits, personal preferences, etc., or the authorization operation of the first client (receiver) is already set by the background server (default setting). Setting the authorization operation includes at least one of the following forms: authorization times and authorization time. In one example, the recipient sets the authorization for the reminder subject twice.

[0183] Optionally, the first client (recipient) authorizes the reminder topic arbitrarily (including at least one of the following methods: arbitrary number of authorizations and arbitrary time for authorization operations). In one example, the reminder topic is created at 10:00 a.m., and both user A and user B receive reminder messages for the reminder topic. User A authorizes the reminder topic twice, at 10:00 a.m. and 10:10 a.m.; user B authorizes the reminder topic ten times, starting from 11:00 a.m. and authorizing once every 30 minutes.

[0184] Step 519: The second client sends a reminder message to the background server.

[0185] The second client sends a reminder message corresponding to the reminder topic to the background server.

[0186] Step 520: the backend server receives a reminder message of the reminder topic.

[0187] The backend server receives the reminder message of the reminder topic.

[0188] Step 521 , the backend server checks whether the reminder message satisfies the limited conditions. When the reminder message satisfies the limited conditions, the process proceeds to step 522 .

[0189] The background server checks whether the reminder message of the received reminder topic meets the limited conditions. When the reminder message meets the limited conditions, it enters step 522; when the reminder message does not meet the limited conditions, the second client (sender) cannot send the reminder message to the first client (receiver).

[0190] Step 522: The backend server sends a reminder message to the authorized user corresponding to the reminder topic.

[0191] When the reminder message of the reminder topic meets the limited conditions, the background server sends the reminder message to the authorized user corresponding to the reminder topic.

[0192] Step 523: The second client receives a reminder message of the reminder topic.

[0193] The first client (receiver) receives the reminder message of the reminder topic.

[0194] In summary, the method provided in this embodiment establishes a communication relationship with the first client (receiver) by creating a reminder topic by the second client (sender), and the recipient authorizes the reminder topic under limited conditions (including at least one of limited time and limited number of times). It does not require the sender and the receiver to establish a friend relationship, but uses the reminder topic as a communication link, avoiding the generation of unnecessary friend relationships, personal privacy leakage and information harassment between users in accidental social scenarios with strangers, and relieving the social pressure of users. At the same time, the above method can be applied to various types of applications on the client, making it more convenient for users who are not friends to establish communication relationships.

[0195] Figure 7 A structural block diagram of a terminal provided by an exemplary embodiment of the present application is shown. A host program 162 and a mini-program 164 are installed and run in the user terminal. The host program 162 can be any one of an instant messaging program and a social program. In this application, the terminal is taken as an instant messaging program as an example. A mini-program is a program that relies on the host program 162 to run. There can be multiple mini-programs, one of which is a reminder assistant mini-program. The user enters the reminder assistant mini-program 164 through the host program 162. Optionally, the reminder assistant mini-program needs to obtain the user's information, or the reminder assistant mini-program does not need to obtain the user's information. Schematically, the example that the reminder assistant mini-program does not need to obtain the user's information is used for explanation.

[0196] The host program 162 is an application that carries the reminder assistant applet 164 and provides an environment for the implementation of the reminder assistant applet 164. The host program 162 is a native application. A native application is an application that can run directly on the operating system 161. The host program 162 can be a social application, a dedicated application that specifically supports the reminder assistant applet 164, a file management application, an email application, or a game application, etc. Social applications include instant messaging applications (for example, WeChat, QQ, etc.), social networking sites (Social Network Service, SNS) applications, or live broadcast applications, etc. Mini programs are applications that can run in the environment provided by the host program. Mini programs can be social applications, file management applications, email applications, or game applications, etc. Schematically, the mini program is taken as an example of the reminder assistant applet 164. The host program 162 can be a WeChat program (WeChat).

[0197] The applet logic layer unit 164b and the corresponding applet view layer unit 164a are used to implement the applet instance. An applet can be implemented by an applet logic layer unit 164b and at least one applet view layer unit 164a. The applet view layer unit 164a and the applet page can be in a one-to-one correspondence.

[0198] The applet view layer unit 164a is used to organize the view of the applet and render it. The applet logic layer unit 164b is used to process the data processing logic of the applet and the corresponding applet page. The unit can be a process or a thread. The applet view layer unit 164a is such as an applet view layer thread, and the applet logic layer unit 164b is such as an applet logic layer thread. The applet logic layer unit 164b can run in a virtual machine. The applet view layer unit 164a and the applet logic layer unit 164b can communicate through the host program native unit 162a. The host program native unit 162a is the interface for the host program 162 to communicate with the applet. The host program native unit 162a can be a thread or process of the host program 162 itself. The page logic code belonging to the program package of each applet page can be registered by the applet logic layer unit 164b at startup, and the registered page logic code can be executed when the page logic code is needed to process data.

[0199] The methods, systems, and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field can know that with the evolution of technology and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0200] The following describes the method for sending and receiving reminder messages in combination with the host program and the applet installed on the terminal, as shown in FIG. Figure 8 and Fig. 9 shown.

[0201] Figure 8 A flowchart showing a method for sending a reminder message provided by another exemplary embodiment of the present application is shown. The method can be applied to Figure 7 The method comprises the following steps:

[0202] Step 801: The second client displays a reminder topic creation interface through a second reminder assistant applet.

[0203] The second client displays the creation interface of the reminder theme by opening the second reminder assistant applet in the second host program. Optionally, the second host program can be a social application, or an application with a reminder function, or a live broadcast application, or a music application. Schematically, the second host program is a WeChat program.

[0204] Combination Fig.10 , describes the interface for creating reminder topics, Fig.10 The following is a schematic diagram of a creation interface of a reminder assistant applet provided by an exemplary embodiment of the present application. In some embodiments, the reminder assistant applet may also be named as a strong reminder assistant, or a reminder applet, or a strong reminder applet. The present application does not limit the name of the applet. Schematically, the present application embodiment takes the name of the applet as a strong reminder assistant as an example for explanation. Fig.10 As shown in (a). On the interface 20 of the strong reminder assistant applet, a create strong reminder virtual button 201 and a historical message 202 are displayed. Optionally, the create strong reminder virtual button 201 can also be a reminder virtual button, or a create virtual button. The name of the virtual button is not limited in this application. The historical message 202 includes the historical records of all reminder messages of the users of the second client. In an example, the reminder message in the historical record 202 includes the subject title of the reminder subject, the time when the reminder message was sent, the subject content of the reminder subject, and the number of people who sent the reminder message. Click the create strong reminder virtual button 201, and the interface 20 of the strong reminder assistant applet jumps to the creation interface 21, as shown in FIG. Fig.10 As shown in (b). The creation interface 21 includes: a reminder theme setting control 203, a save virtual button 204, an expression option 205 and a return option 206. The reminder theme setting control 203 is used to receive a reminder theme editing operation, and obtain a theme title of the reminder theme according to the reminder theme editing operation. Optionally, a content setting control is also displayed on the creation interface 21, and the content setting control is used to receive a content editing operation, and obtain a theme introduction of the reminder theme according to the content editing operation. Schematically, the theme title of the reminder theme is entered in the reminder theme setting control 203, and the theme title of the reminder theme is Patent Application Sharing Session, such as Fig.10 (c) is shown in the figure. The virtual save button 204 is used to create a reminder topic. The user can create a reminder topic by entering the topic title of the reminder topic and clicking Save. Optionally, the topic title of the reminder topic can also contain an emoticon. The user clicks the emoticon option 205 to select the emoticon to be added to the topic title of the reminder topic. Optionally, the return option 206 is used to exit the strong reminder assistant applet.

[0205] Step 802: The second client generates a reminder topic creation request through the second reminder assistant applet according to the creation operation received in the creation interface. The reminder topic creation request carries the topic title of the reminder topic.

[0206] The second client generates a reminder topic creation request through the second reminder assistant applet according to the creation operation received in the creation interface, and the reminder topic creation request carries a topic title of the reminder topic.

[0207] In one example, the second client receives a creation operation in which the user clicks the save virtual button 204 in the creation interface 21 through the second strong reminder assistant applet.

[0208] Step 803: The second client sends a request to create a reminder topic to the background server.

[0209] The second client sends a request to create a reminder topic to the background server through the second reminder assistant applet.

[0210] Step 804: the backend server receives a request to create a reminder topic, where the request carries a topic title of the reminder topic.

[0211] The backend server receives a reminder topic creation request sent by the second client through the second reminder assistant applet, wherein the creation request includes any one of the options involved in the above embodiments. In one example, the creation request carries a topic title of the reminder topic.

[0212] Step 805: the backend server generates a reminder topic identifier according to the reminder topic creation request.

[0213] The backend server generates a topic ID for the reminder topic according to the reminder topic creation request. If there are multiple reminder topics, the same reminder topic ID is generated for multiple reminder topics; or, each reminder topic ID is generated for each reminder topic; or, a common group ID and corresponding sub-IDs are generated for multiple reminder topics.

[0214] Table 2 is used below to exemplify the correspondence between the subject identifier of the reminder subject, the subject title of the reminder subject, the subject content of the reminder subject, the user (authorized user) receiving the reminder message, and the limited conditional reminder authority.

[0215] Table 2

[0216]

[0217] Among them, the subject identifier 2019061321090004 of the reminder subject is used to represent the 0004th reminder subject at 21:09 on June 13, 2019. This embodiment does not limit the type of subject identifier of the reminder subject. The subject title of the reminder subject in Table 2 is "The takeaway you ordered has arrived", the authorized user of the reminder subject is 1 person, and the number of times the authorized user has received the reminder message of the reminder subject is 3; the subject title of the reminder subject is "The second half of the popular trend lecture hall is open", the authorized users of the reminder subject are 500 people, and each person receives two reminder messages of the reminder subject within 20 minutes.

[0218] Step 806: The backend server sends a reminder topic creation response to the second client.

[0219] The background server sends a creation response of the reminder topic to the second reminder assistant applet in the second host program on the second client, and the second client performs subsequent operations according to the creation response through the second reminder assistant applet.

[0220] Step 807: The second client creates a reminder topic through the second reminder assistant applet.

[0221] The second client successfully creates the reminder topic through the second reminder assistant applet according to the creation response of the reminder topic sent by the background server.

[0222] Step 808: the backend server sends a reminder theme identifier to the second client, and the reminder theme identifier is used for the second reminder assistant applet to display a graphic code corresponding to the reminder theme.

[0223] The backend server sends a reminder theme identifier to the second client. Optionally, the reminder theme identifier is used for the second client to display at least one of the following forms: a graphic code (e.g., a barcode, a QR code), a character verification code (e.g., including at least one type of text, numbers, and English), a link, a virtual button (e.g., a "join" virtual button, or a "follow" virtual button) corresponding to the reminder theme through the second reminder assistant applet. In one example, the reminder theme identifier is used to display the graphic code corresponding to the reminder theme.

[0224] Step 809: The second client displays the graphic code corresponding to the reminder theme through the second reminder assistant applet.

[0225] The second client displays a graphic code corresponding to the reminder theme through the second reminder assistant applet. Optionally, the graphic code is a barcode or a QR code. In one example, the graphic code is a QR code, such as Fig.11 shown. Fig.11The interface diagram of a strong reminder assistant applet displaying a graphic code corresponding to a reminder theme provided by an exemplary embodiment of the present application is shown. The graphic code display interface 11 of the second strong reminder assistant applet includes: information 111 of the reminder theme (including: a QR code corresponding to the reminder theme, the title of the reminder theme, and the number of users who receive the reminder message), a virtual button 112 for editing the reminder content, and a virtual menu button 113 for the QR code corresponding to the reminder theme, such as Fig.11 Optionally, the user can operate the QR code. In one example, by clicking the menu virtual button 113, a dialog box 207 appears, which includes: options for saving the reminder code, resetting the QR code, and deleting the reminder, as shown in FIG. Fig.11 The user saves the reminder code to the terminal through the second strong reminder assistant applet and obtains a picture containing the strong reminder QR code, as shown in (b). Fig.11 As shown in (c), the picture displays information 111 of the reminder theme (including: the strong reminder QR code corresponding to the reminder theme and the theme title of the reminder theme). Optionally, when the strong reminder QR code is invalid, the user can reset the strong reminder QR code by clicking the reset QR code option in the second strong reminder assistant applet, and display the QR code corresponding to the new reminder theme. Optionally, the reminder theme can be deleted by clicking the delete reminder option, and the deleted reminder theme will no longer remind.

[0226] To summarize, in the above method, by displaying the graphic code corresponding to the reminder subject, the subject identifier of the reminder subject is corresponded to the graphic code, so that the first client (receiver) can authorize the reminder subject by scanning the graphic code, simplifying the authorization operation steps of the recipient, and the second client (sender) can send a reminder message to the recipient in a variety of ways (for example, sending an electronic version of the graphic code through a terminal, or printing a paper version of the graphic code).

[0227] Fig. 9 A flowchart showing a method for receiving a reminder message provided by another exemplary embodiment of the present application is shown. The method can be applied to Figure 7 The method comprises the following steps:

[0228] Step 810: The first client scans the graphic code corresponding to the reminder theme through the first host program.

[0229] The first client terminal scans the graphic code corresponding to the reminder theme through the first host program. Fig.12 , Fig.12The following is a schematic diagram of an interface for an authorization process provided by an exemplary embodiment of the present application. The user scans the graphic code corresponding to the reminder theme through the first host program. In one example, the host program is the WeChat program. The user scans the graphic code corresponding to the reminder theme through the "Scan" function set in the WeChat program. Fig.12 As shown in (a). The interface 12 of the "Scan" function includes: a graphic code scanning box 114, a code scanning option 115, an auxiliary lighting option 116 and a return virtual button 117. The graphic code scanning box 114 is used to scan the graphic code corresponding to the reminder theme, the code scanning option 115 is used to scan the graphic code (including barcodes and QR codes), and the auxiliary lighting option 116 is used to illuminate the graphic code in a dark environment to ensure that the graphic code can be scanned normally.

[0230] Step 811: The first client obtains a topic title corresponding to the reminder topic from the graphic code.

[0231] The first client scans the graphic code corresponding to the reminder theme through the first host program to obtain the theme title of the reminder theme.

[0232] Step 812: The first client calls the first reminder assistant applet through the first host program, and displays the authorization reminder interface of the reminder subject according to the subject title of the reminder subject through the first reminder assistant applet.

[0233] The first client calls the first reminder assistant applet through the first host program, and displays the authorization reminder interface of the reminder subject according to the subject title of the reminder subject through the first reminder assistant applet, such as Fig.12 As shown in (b). The method is applied to a host program running a reminder assistant applet, and the reminder assistant applet depends on the host program. In one example, the authorization reminder interface 13 is the applet interface of the strong reminder assistant applet. The authorization reminder interface 13 displays information 118 of the reminder subject (including the subject title and reminder method of the reminder subject, such as receiving strong reminders), a confirmation authorization option 119, a cancellation authorization option 121, and an option 122 for closing the authorization reminder interface. The confirmation authorization option 119 is used to confirm that the user has authorized the reminder subject, the cancellation authorization option 121 is used for the user to cancel the authorization of the reminder subject, and the option 122 for closing the authorization reminder interface is used to close the authorization reminder interface 13.

[0234] Step 813: After receiving the authorization operation on the authorization interface, the first client generates an authorization instruction, which carries the subject identifier and limited conditions of the reminder subject.

[0235] The user generates an authorization instruction by selecting the Determine Authorization option 119 on the authorization interface 13 of the first reminder assistant applet in the first host program on the first client, and the authorization instruction carries the subject identifier of the reminder subject and limited conditions. The limited conditions include at least one of limited time and limited number of times. Limited time means that the sender can send the reminder message within a certain period of time, and limited number of times means that the sender can send the reminder message a limited number of times.

[0236] Optionally, when the confirmation control 119 (in some embodiments, also named as the confirmation authorization option, which is not limited in this application) on the authorization reminder interface 13 is triggered, the first client sends a first authorization indication of the reminder subject to the background server through the first reminder assistant applet. The first authorization indication is used by the server to grant a valid reminder permission to the reminder subject once.

[0237] In one example, after the user clicks the confirmation control 119 on the authorization reminder interface 13, a valid authorization instruction is sent to the background server through the first reminder assistant applet, that is, a valid reminder permission is granted to the reminder subject. In the same reminder subject, after a valid reminder permission is granted, the connection between the receiver and the sender is interrupted, and the sender needs to regenerate the reminder QR code so that the user (receiver) can perform a new authorization operation.

[0238] Alternatively, after the number setting control on the authorization reminder interface 13 is set to n, a second authorization instruction of the reminder subject is sent to the server, and the second authorization instruction is used to instruct the server to grant n valid reminder permissions to the reminder subject.

[0239] Optionally, the developer sets the number of times the control is set through the background server, or the user sets the number of times the control is set on the authorization reminder interface 13 of the reminder assistant applet. Optionally, n is any integer greater than zero. In one example, the user sets the number of times control on the authorization reminder interface 13 of the reminder assistant applet to five times (that is, the value of n is 5), then in the same reminder topic, the number of times the reminder topic is granted valid reminder permissions is five, and after five valid reminder authorizations, the connection between the receiver and the sender is interrupted, and the sender needs to regenerate the reminder QR code so that the user (receiver) can perform a new authorization operation.

[0240] Alternatively, after the event setting control on the authorization reminder interface 13 is set to t, a third authorization instruction of the reminder subject is sent to the server, and the third authorization instruction is used to instruct the server to grant the reminder subject a reminder authority valid within the duration t.

[0241] Optionally, the developer sets the duration t of the event setting control through the background server, or the user sets the duration t of the event setting control on the authorization reminder interface 13 of the reminder assistant applet. Optionally, t is any number greater than zero. Optionally, the unit of t is hours, minutes, seconds, or milliseconds. In one example, the user sets the duration of the event setting control on the authorization reminder interface 13 of the reminder assistant applet to one hour (that is, the value of t is 1, and the unit is hours). Then, in the same reminder topic, the duration of granting effective reminder permission to the reminder topic is one hour. Within one hour, the user can perform authorized operations. After more than one hour, the connection between the receiver and the sender is interrupted, and the sender needs to regenerate the reminder QR code so that the user (receiver) can perform new authorization operations.

[0242] Optionally, the first client (receiver) can set the authorization operation of the reminder subject according to actual conditions, usage habits, personal preferences, etc., or the authorization operation of the first client (receiver) is already set by the background server (default setting). Setting the authorization operation includes at least one of the following forms: authorization times and authorization time. In one example, the recipient sets the authorization for the reminder subject twice.

[0243] Optionally, the first client (recipient) authorizes the reminder topic arbitrarily (including at least one of the following methods: arbitrary number of authorizations and arbitrary time for authorization operations). In one example, the reminder topic is created at 10:00 a.m., and both user A and user B receive reminder messages for the reminder topic. User A authorizes the reminder topic twice, at 10:00 a.m. and 10:10 a.m.; user B authorizes the reminder topic ten times, starting from 11:00 a.m. and authorizing once every 30 minutes.

[0244] To sum up, based on the default settings of the background server, the second client (sender) grants the reminder subject a valid reminder permission once, which simplifies the sender's operation steps when sending reminder messages and improves the efficiency of sending reminder messages; when the sender can set the reminder permission with limited conditions, the user can set the limited conditions (including: at least one of limited time and limited number of times) according to his personal habits and preferences, realizing the user's personalized setting function.

[0245] The above method can also be applied to the reminder assistant applet, so that users who have not installed the application (host program) can also authorize the reminder theme.

[0246] like Fig.12As shown in (a), after the user authorizes to receive reminder messages, the program interface 14 of the host program is displayed, and the program interface 14 displays a chat message option 123 and an authorized reminder subject bar 124. The user performs at least one of the following operations through the authorized reminder subject bar 124: viewing the reminder subject operation, or deleting the authorized reminder subject, and canceling the reminder permission granted to the reminder subject according to the deletion operation. Fig.12 (d), the user clicks the reminder subject bar 124, and the program interface 14 jumps to the reminder message interface 15, which displays the message 125 of the reminder subject, the information 126 of the reminder subject (including: the subject title of the reminder subject and the reminder effective time) and the return button 117. Optionally, the return button is used to exit the reminder message interface 15, or return to the program interface 14. The user receives the reminder message corresponding to the reminder subject in various ways, for example, receiving the reminder message in the service notification message bar in the message interface.

[0247] To sum up, the second client (recipient) can view the reminder topic at any time and delete the authorized reminder topic. The deletion operation is used to cancel the reminder permission granted to the reminder topic to avoid unnecessary trouble for the recipient due to receiving reminder messages when he cannot receive reminder messages (for example, the recipient cannot be disturbed during a meeting, so he can cancel receiving reminder messages).

[0248] Step 814: The first client sends an authorization instruction to the backend server.

[0249] The first client sends an authorization instruction to the background server through the first reminder assistant applet, and the authorization instruction is used to instruct the background server to perform subsequent operations.

[0250] Step 815: the backend server receives the authorization instruction sent by the first reminder assistant applet.

[0251] The backend server receives the authorization instruction sent by the first client through the first reminder assistant applet, and the authorization instruction includes at least one of the following instructions: the authorized user's account, nickname, user name, authorization time, and authorization content (including: some functions on the terminal operating system, such as recording function, camera function, positioning function, microphone function, and receiver function, or the recipient's phone number, email address and other personal information, or the recipient's hobbies, social circle, etc.). In one example, the authorized user's account is the user's WeChat account.

[0252] Step 816: the backend server queries the topic identifier of the corresponding reminder topic according to the authorization instruction.

[0253] The backend server queries the subject identifier of the corresponding reminder subject according to the authorization instruction received from the first client through the first reminder assistant applet.

[0254] Step 817: the backend server sends an authorization indication corresponding to the subject identifier of the reminder subject to the second client.

[0255] When the background server queries the subject identifier of the reminder subject corresponding to the first reminder program assistant, it sends an authorization instruction corresponding to the subject identifier of the reminder subject to the second client.

[0256] Step 818, the second client obtains the authorized user corresponding to the reminder subject through the second reminder assistant applet, the authorized user is a user account that grants reminder authority with limited conditions to the reminder subject, and the limited conditions include at least one of limited time and limited number of times.

[0257] The second client obtains the authorized user corresponding to the reminder topic through the second reminder assistant applet according to the corresponding authorization instruction. In one example, the authorized user is a user account that grants the reminder topic reminder authority with limited conditions. Optionally, the limited conditions include at least one of limited time and limited number of times. In one example, the sender can send a topic message of the reminder topic in one hour.

[0258] Optionally, the first client (receiver) can set the authorization operation of the reminder subject according to actual conditions, usage habits, personal preferences, etc., or the authorization operation of the first client (receiver) is already set by the background server (default setting). Setting the authorization operation includes at least one of the following forms: authorization times and authorization time. In one example, the recipient sets the authorization for the reminder subject twice.

[0259] Optionally, the first client (receiver) authorizes the reminder topic arbitrarily (including at least one of the following methods: arbitrary number of authorizations and arbitrary time for performing the authorization operation). In one example, the reminder topic is created at 10:00 a.m., and both user A and user B receive reminder messages for the reminder topic. User A authorizes the reminder topic twice, at 10:00 a.m. and 10:10 a.m.; user B authorizes the reminder topic ten times, starting from 11:00 a.m. and once every 30 minutes.

[0260] Step 819: The second client sends a reminder message to the background server through the second reminder assistant applet.

[0261] The second client sends a reminder message corresponding to the reminder topic to the background server through the second reminder assistant applet.

[0262] Step 820: the backend server receives a reminder message of the reminder topic sent by the second reminder assistant applet.

[0263] The backend server receives the reminder message of the reminder topic sent by the second reminder assistant applet.

[0264] Step 821, the backend server checks whether the reminder message meets the limited conditions. When the reminder message meets the limited conditions, it goes to step 822.

[0265] The background server checks whether the reminder message of the received reminder topic meets the limited conditions. When the reminder message meets the limited conditions, it enters step 822; when the reminder message does not meet the limited conditions, the second client cannot send the reminder message to the first client through the second reminder assistant applet.

[0266] Step 822: The backend server sends a reminder message to the authorized user corresponding to the reminder topic.

[0267] When the reminder message of the reminder topic meets the limited conditions, the background server sends the reminder message to the authorized user corresponding to the reminder topic.

[0268] Combination Fig.13 Describes the method of sending a reminder message to the authorized user corresponding to the reminder topic. Fig.13 A schematic diagram of an interface for sending a reminder by a strong reminder assistant applet provided by an exemplary embodiment of the present application is shown. In one example, when there is at least one authorized user who authorizes the reminder subject, a graphic code generation interface 11 corresponding to the reminder subject is displayed on the second strong reminder assistant applet on the second client, such as Fig.13 As shown in (a), the graphic code generation interface 11 displays information 111 of the reminder subject (including: a reminder QR code corresponding to the reminder subject, a subject title of the reminder subject, and the number of authorized users of the reminder subject. In one example, the number of authorized users is 1), a virtual button 112 for editing the reminder content, and a menu virtual button 113 of the QR code corresponding to the reminder subject. When the user clicks the virtual button 112 for editing the reminder content, the reminder message editing interface 11 jumps to the reminder message editing interface 17 of the reminder subject, as shown in FIG. Fig.13 The reminder editing interface 17 displays a reminder title editing control 127, a content editing control 128, a send option 129, and a return option 117. Optionally, the user edits at least one of the reminder title and the reminder content. Schematically, the reminder title is edited as Patent Application Sharing Session, such as Fig.13 (b) of the reminder topic; the subject content of the reminder topic is edited as Room 101, Building A, and you need to bring a computer, such as Fig.13As shown in (c), optionally, the user can add any emoticon in the editing area of ​​the subject title of the reminder subject and the subject content of the reminder subject through the emoticon option 205. Optionally, the user can exit the reminder message editing interface 17 through the return option 117. When the user completes the editing operation of the subject title of the reminder subject and the subject content of the reminder subject, the reminder message is obtained according to the reminder message editing operation, and the send option 129 is clicked, and the editing reminder interface 17 jumps to the reminder message sending interface 19, and the reminder message is sent to the authorized user corresponding to the reminder subject.

[0269] Step 823: The first client receives a reminder message of the reminder topic through the first reminder assistant applet.

[0270] The first client receives a reminder message of the reminder topic through the first reminder assistant applet.

[0271] Combination Fig.14 Describes how to receive reminder messages. Fig.14 A schematic diagram of an interface for a strong reminder assistant to receive a reminder message provided by an exemplary embodiment of the present application is shown.

[0272] Optionally, the receiving reminder mode includes at least one of a normal reminder mode and a strong reminder mode, and the strong reminder mode includes at least one of the following reminder modes: displaying a reminder message in a lock screen interface, displaying a reminder message in a message display page provided by a reminder assistant applet, displaying a reminder message in a message display page provided by a host program, calling an operating system to play a reminder sound corresponding to a reminder message through a host program or a reminder assistant applet, and calling an operating system to control a signal light for reminder through a host program or a reminder assistant applet. In one example, a reminder message is displayed on the lock screen interface of a terminal, such as Fig.14 As shown in (a). The lock screen interface 20 displays a prompt message 132 of the reminder message sent by the strong reminder assistant applet and an "I know" virtual button 133. Optionally, the prompt message 132 can be set to display part of the content of the reminder message, such as the nickname, avatar, summary of the reminder message, etc. of the sender of the reminder message. The "I know" virtual button 133 is used to turn off the display content of the strong reminder message on the lock screen interface. In some embodiments, the "I know" virtual button 133 can be an "I know" virtual button or a virtual button to close the reminder, which is not limited in this application.

[0273] In one example, a reminder message is displayed in a message display page provided by the host program, such as Fig.14The message display page 21 displays a message option 123, a strong reminder bar 124, and a service notification message bar 134. Optionally, the service notification message bar 134 displays the subject title of the reminder subject and the number of reminder messages. The user enters the service notification interface 22 by clicking on the service notification message bar 134. Fig.14 As shown in (c), the service notification interface 22 displays a setting option 135, a reminder message list 136, and a return option 117. The setting option 135 is used to set the reminder method of the reminder message, and optionally, to set at least one of the reminder frequency, content, time, reminder tone, and shielding of reminder messages of a certain reminder topic. The reminder message list 136 displays the topic title and content of the reminder topic, and the time when the reminder message is sent. The return option 117 is used to exit the service notification interface 22.

[0274] In summary, the method provided in this embodiment establishes a communication relationship with the first client (receiver) by creating a reminder topic by the second client (sender), and the recipient authorizes the reminder topic under limited conditions (including at least one of limited time and limited number of times). It does not require the sender and the receiver to establish a friend relationship, but uses the reminder topic as a communication link, avoiding the generation of unnecessary friend relationships, personal privacy leakage and information harassment between users in accidental social scenarios with strangers, and relieving the social pressure of users. At the same time, the above method can be applied not only to various types of applications on the client, but also to small programs in the host program, making it more convenient for users who are not friends to establish communication relationships.

[0275] The above-mentioned diverse strong reminder methods facilitate users to make personalized settings according to their personal habits and preferences. At the same time, users can receive reminder messages in multiple interfaces such as the host program and the reminder assistant applet, ensuring that users can accurately and quickly receive reminder messages for the corresponding reminder topics.

[0276] The above method can edit the subject title, subject content and reminder message of the reminder subject, so that the second client (sender) can create a reminder subject that meets the requirements according to actual needs and personal habits or preferences (for example, adding emoticons).

[0277] The following is an embodiment of the device of the present application. For details not described in detail in the embodiment of the device, reference can be made to the corresponding records in the above method embodiment, and they will not be repeated herein.

[0278] Fig.15The schematic diagram of the structure of a message receiving device provided by an exemplary embodiment of the present application is shown. The device can be implemented as all or part of a terminal through software, hardware or a combination of both, and the device includes: an acquisition module 1510, a display module 1520 and a receiving module 1530, wherein the receiving module 1530 is an optional module.

[0279] The acquisition module 1510 is used to acquire the subject title of the reminder subject.

[0280] The display module 1520 is used to display the authorization reminder interface of the reminder topic according to the topic title of the reminder topic.

[0281] The receiving module 1530 is used to grant a reminder permission with limited conditions to the reminder subject after receiving the authorization operation on the authorization reminder interface. The limited conditions include at least one of limited time and limited number of times.

[0282] The receiving module 1530 is further configured to receive a reminder message of a reminder topic.

[0283] In an optional embodiment, the receiving module 1530 is also used for: when the confirmation control on the authorization reminder interface is triggered, sending a first authorization indication of the reminder subject to the server, the first authorization indication is used to instruct the server to grant the reminder subject one valid reminder permission; or, after the number setting control on the authorization reminder interface is set to n, sending a second authorization indication of the reminder subject to the server, the second authorization indication is used to instruct the server to grant the reminder subject n valid reminder permissions; or, after the event setting control on the authorization reminder interface is set to t, sending a third authorization indication of the reminder subject to the server, the third authorization indication is used to instruct the server to grant the reminder subject a reminder permission that is valid for a duration of t.

[0284] In an optional embodiment, the authorization instruction carries: the subject identifier of the reminder subject and the limited condition.

[0285] In an optional embodiment, the acquisition module 1510 is further used to: scan a graphic code corresponding to the reminder theme; and read a theme title of the reminder theme from the graphic code.

[0286] In an optional embodiment, the above method is applied to a host program running a reminder assistant applet, and the reminder assistant applet depends on the host program to run; the authorization reminder interface is the applet interface of the reminder assistant applet.

[0287] In an optional embodiment, the display module 1520 is also used to: display the reminder message in a strong reminder manner, and the strong reminder manner includes at least one of the following reminder methods: displaying the reminder message in the lock screen interface; displaying the reminder message in the message display page provided by the reminder assistant applet.

[0288] In an optional embodiment, the display module 1520 is also used to display the authorized reminder subject in the program interface of the host program; the receiving module 1530 is also used to: receive a deletion operation on the authorized reminder subject; and cancel the reminder permission granted to the reminder subject according to the deletion operation.

[0289] Fig.16 The schematic diagram of the structure of a message sending device provided by an exemplary embodiment of the present application is shown. The device can be implemented as all or part of a terminal through software, hardware or a combination of both, and the device includes: a display module 1610, a receiving module 1620, an acquisition module 1630 and a sending module 1640, wherein the receiving module 1620 is an optional module.

[0290] The display module 1610 is used to display a reminder topic creation interface.

[0291] The receiving module 1620 is used to create a reminder topic according to the creation operation received in the creation interface.

[0292] Acquisition module 1630, for acquiring an authorized user corresponding to a reminder subject, where the authorized user is a user account that grants a reminder permission with limited conditions to the reminder subject, where the limited conditions include at least one of a limited time and a limited number of times;

[0293] The sending module 1640 is used to send a reminder message to the authorized user corresponding to the reminder topic.

[0294] In an optional embodiment, the display module 1610 is also used to: display a graphic code corresponding to the reminder theme, the graphic code carrying the theme identifier of the reminder theme; the acquisition module 1630 is also used to: acquire the authorized user who scans the graphic code for authorization processing.

[0295] In an optional embodiment, the display module 1610 is also used to: create an interface displaying a reminder theme setting control; the receiving module 1620 is also used to: receive a theme editing operation on the reminder theme setting control in the creation interface; the acquisition module 1630 is also used to: obtain a theme title of the reminder theme according to the reminder theme editing operation; and create a reminder theme according to the theme title of the reminder theme.

[0296] In an optional embodiment, the display module 1610 is also used to: create an interface that also displays a content setting control; the receiving module 1620 is also used to: receive content editing operations on the content setting controls in the creation interface; the acquisition module 1630 is also used to: obtain a theme introduction of the reminder theme based on the content editing operation; and create a reminder theme based on the theme title and theme content of the reminder theme.

[0297] In an optional embodiment, the display module 1610 is also used to: display the reminder message editing interface of the reminder topic; the receiving module 1620 is also used to: receive the reminder message editing operation in the reminder message editing interface; the acquisition module 1630 is also used to: obtain the reminder message according to the reminder message editing operation; the sending module 1640 is also used to: send the reminder message to the authorized user corresponding to the reminder topic.

[0298] The device embodiment of the present application is described below in conjunction with the reminder assistant applet.

[0299] Fig.17 The schematic diagram of the structure of a message receiving device provided by another exemplary embodiment of the present application is shown. The device can be implemented as all or part of a terminal through software, hardware or a combination of both, and the device includes: a scanning module 1710, an acquisition module 1720, a display module 1730, and a receiving module 1740.

[0300] Scanning module 1710, used to scan the graphic code corresponding to the reminder theme through the first host program;

[0301] The acquisition module 1720 is used to acquire the subject title corresponding to the reminder subject from the graphic code;

[0302] The display module 1730 is used to call the first reminder assistant applet through the first host program, and display the authorization reminder interface of the reminder subject according to the subject title of the reminder subject through the first reminder assistant applet;

[0303] Receiving module 1740, configured to grant a reminder permission with limited conditions to the reminder subject after receiving the authorization operation on the authorization reminder interface, wherein the limited conditions include at least one of limited time and limited number of times;

[0304] The receiving module 1740 is further configured to receive a reminder message of a reminder topic through the first reminder assistant applet.

[0305] In an optional embodiment, the receiving module 1740 is also used for: when the confirmation control on the authorization reminder interface is triggered, sending a first authorization indication of the reminder subject to the server, the first authorization indication is used to instruct the server to grant the reminder subject one valid reminder permission; or, after the number setting control on the authorization reminder interface is set to n, sending a second authorization indication of the reminder subject to the server, the second authorization indication is used to instruct the server to grant the reminder subject n valid reminder permissions; or, after the event setting control on the authorization reminder interface is set to t, sending a third authorization indication of the reminder subject to the server, the third authorization indication is used to instruct the server to grant the reminder subject a reminder permission that is valid for a duration of t.

[0306] In an optional embodiment, the authorization instruction carries: the subject identifier of the reminder subject and the limited condition.

[0307] In an optional embodiment, the scanning module 1710 is further used to: scan the graphic code corresponding to the reminder theme; the acquisition module 1720 is further used to: read the theme title of the reminder theme from the graphic code.

[0308] In an optional embodiment, the above method is applied to a host program running a reminder assistant applet, and the reminder assistant applet depends on the host program to run; the authorization reminder interface is the applet interface of the reminder assistant applet.

[0309] In an optional embodiment, the display module 1730 is also used to: display the reminder message in a strong reminder manner, and the strong reminder manner includes at least one of the following reminder methods: displaying the reminder message in the lock screen interface; displaying the reminder message in the message display page provided by the reminder assistant applet.

[0310] In an optional embodiment, the display module 1730 is also used to: display the authorized reminder subject in the program interface of the host program; the receiving module 1740 is also used to: receive a deletion operation on the authorized reminder subject; and cancel the reminder permission granted to the reminder subject according to the deletion operation.

[0311] Combination Fig.16 , a message sending device provided by another exemplary embodiment of the present application is described. The device can be implemented as all or part of the terminal through software, hardware or a combination of both, and the device includes: a display module 1610, a receiving module 1620, an acquisition module 1630 and a sending module 1640, wherein the receiving module 1620 is an optional module.

[0312] Display module 1610, used to display a reminder theme creation interface through the second reminder assistant applet;

[0313] The receiving module 1620 is used to create a reminder topic according to the creation operation received in the creation interface through the second reminder assistant applet;

[0314] Acquisition module 1630, used to acquire the authorized user corresponding to the reminder subject through the second reminder assistant applet, where the authorized user is a user account that grants the reminder subject a reminder permission with limited conditions, where the limited conditions include at least one of limited time and limited number of times;

[0315] The sending module 1640 is used to send a reminder message to the authorized user corresponding to the reminder topic through the second reminder assistant applet.

[0316] In an optional embodiment, the display module 1610 is also used to: display a graphic code corresponding to the reminder theme, the graphic code carrying the theme identifier of the reminder theme; the acquisition module 1630 is also used to: acquire the authorized user who scans the graphic code for authorization processing.

[0317] In an optional embodiment, the display module 1610 is also used to: create an interface displaying a reminder theme setting control; the receiving module 1620 is also used to: receive a theme editing operation on the reminder theme setting control in the creation interface; the acquisition module 1630 is also used to: obtain a theme title of the reminder theme according to the reminder theme editing operation; and create a reminder theme according to the theme title of the reminder theme.

[0318] In an optional embodiment, the display module 1610 is also used to: create an interface that also displays a content setting control; the receiving module 1620 is also used to: receive content editing operations on the content setting controls in the creation interface; the acquisition module 1630 is also used to: obtain a theme introduction of the reminder theme based on the content editing operation; and create a reminder theme based on the theme title and theme content of the reminder theme.

[0319] In an optional embodiment, the display module 1610 is also used to: display the reminder message editing interface of the reminder topic; the receiving module 1620 is also used to: receive the reminder message editing operation in the reminder message editing interface; the acquisition module 1630 is also used to: obtain the reminder message according to the reminder message editing operation; the sending module 1640 is also used to: send the reminder message to the authorized user corresponding to the reminder topic.

[0320] The following is an explanation of the electronic equipment used in this application. Please refer to Fig.18, which shows a block diagram of an electronic device 1800 provided by an exemplary embodiment of the present application. The electronic device 1800 may be a portable mobile terminal, such as a smart phone, a tablet computer, an MP3 player (Moving Picture Experts Group Audio Layer III), an MP4 player (Moving Picture Experts Group Audio Layer IV). The electronic device 1800 may also be called a user device, a portable terminal, or other names.

[0321] Typically, the electronic device 1800 includes a processor 1801 and a memory 1802 .

[0322] The processor 1801 may include one or more processing cores, such as a 4-core processor, an 8-core processor, etc. The processor 1801 may be implemented in at least one hardware form of DSP (Digital Signal Processing), FPGA (Field-Programmable Gate Array), and PLA (Programmable Logic Array). The processor 1801 may also include a main processor and a coprocessor. The main processor is a processor for processing data in the awake state, also known as a CPU (Central Processing Unit); the coprocessor is a low-power processor for processing data in the standby state. In some embodiments, the processor 1801 may be integrated with a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content to be displayed on the display screen. In some embodiments, the processor 1801 may also include an AI (Artificial Intelligence) processor, which is used to process computing operations related to machine learning.

[0323] The memory 1802 may include one or more computer-readable storage media, which may be tangible and non-transitory. The memory 1802 may also include a high-speed random access memory, and a non-volatile memory, such as one or more disk storage devices, flash memory storage devices. In some embodiments, the non-transitory computer-readable storage medium in the memory 1802 is used to store at least one instruction, which is used to be executed by the processor 1801 to implement the receiving method and sending method of the reminder message provided in the present application.

[0324] In some embodiments, the electronic device 1800 may further include: a peripheral device interface 1803 and at least one peripheral device. Specifically, the peripheral device includes: at least one of a radio frequency circuit 1804 , a touch display screen 1805 , a camera 1806 , an audio circuit 1807 and a power supply 1808 .

[0325] The peripheral device interface 1803 may be used to connect at least one peripheral device related to I / O (Input / Output) to the processor 1801 and the memory 1802. In some embodiments, the processor 1801, the memory 1802, and the peripheral device interface 1803 are integrated on the same chip or circuit board; in some other embodiments, any one or two of the processor 1801, the memory 1802, and the peripheral device interface 1803 may be implemented on a separate chip or circuit board, which is not limited in this embodiment.

[0326] The radio frequency circuit 1804 is used to receive and transmit RF (Radio Frequency) signals, also known as electromagnetic signals. The radio frequency circuit 1804 communicates with the communication network and other communication devices through electromagnetic signals. The radio frequency circuit 1804 converts the electrical signal into an electromagnetic signal for transmission, or converts the received electromagnetic signal into an electrical signal. Optionally, the radio frequency circuit 1804 includes: an antenna system, an RF transceiver, one or more amplifiers, a tuner, an oscillator, a digital signal processor, a codec chipset, a user identity module card, etc. The radio frequency circuit 1804 can communicate with other terminals through at least one wireless communication protocol. The wireless communication protocol includes but is not limited to: the World Wide Web, a metropolitan area network, an intranet, various generations of mobile communication networks (2G, 3G, 4G and 5G), a wireless local area network and / or a WiFi (Wireless Fidelity) network. In some embodiments, the radio frequency circuit 1804 may also include circuits related to NFC (Near Field Communication), which is not limited in this application.

[0327] The touch display screen 1805 is used to display a UI (User Interface). The UI may include graphics, text, icons, videos, and any combination thereof. The touch display screen 1805 also has the ability to collect touch signals on the surface or above the surface of the touch display screen 1805. The touch signal may be input to the processor 1801 as a control signal for processing. The touch display screen 1805 is used to provide virtual buttons and / or virtual keyboards, also known as soft buttons and / or soft keyboards. In some embodiments, the touch display screen 1805 may be one, and the front panel of the electronic device 1800 is set; in other embodiments, the touch display screen 1805 may be at least two, which are respectively set on different surfaces of the electronic device 1800 or are folded; in still other embodiments, the touch display screen 1805 may be a flexible display screen, which is set on the curved surface or folded surface of the electronic device 1800. Even, the touch display screen 1805 may also be set to a non-rectangular irregular shape, that is, a special-shaped screen. The touch display screen 1805 may be made of materials such as LCD (Liquid Crystal Display), OLED (Organic Light-Emitting Diode, organic light-emitting diode).

[0328] The camera assembly 1806 is used to capture images or videos. Optionally, the camera assembly 1806 includes a front camera and a rear camera. Typically, the front camera is used to realize video calls or selfies, and the rear camera is used to realize the shooting of photos or videos. In some embodiments, there are at least two rear cameras, which are any one of a main camera, a depth of field camera, and a wide-angle camera, so as to realize the fusion of the main camera and the depth of field camera to realize the background blur function, and the fusion of the main camera and the wide-angle camera to realize panoramic shooting and VR (Virtual Reality) shooting functions. In some embodiments, the camera assembly 1806 may also include a flash. The flash can be a monochrome temperature flash or a dual-color temperature flash. A dual-color temperature flash refers to a combination of a warm light flash and a cold light flash, which can be used for light compensation at different color temperatures.

[0329] The audio circuit 1807 is used to provide an audio interface between the user and the electronic device 1800. The audio circuit 1807 may include a microphone and a speaker. The microphone is used to collect sound waves from the user and the environment, and convert the sound waves into electrical signals and input them into the processor 1801 for processing, or input them into the radio frequency circuit 1804 to achieve voice communication. For the purpose of stereo acquisition or noise reduction, there may be multiple microphones, which are respectively arranged at different parts of the electronic device 1800. The microphone may also be an array microphone or an omnidirectional acquisition microphone. The speaker is used to convert the electrical signal from the processor 1801 or the radio frequency circuit 1804 into sound waves. The speaker may be a traditional film speaker or a piezoelectric ceramic speaker. When the speaker is a piezoelectric ceramic speaker, it can not only convert the electrical signal into sound waves audible to humans, but also convert the electrical signal into sound waves inaudible to humans for purposes such as ranging. In some embodiments, the audio circuit 1807 may also include a headphone jack.

[0330] The power supply 1808 is used to power various components in the electronic device 1800. The power supply 1808 can be an alternating current, a direct current, a disposable battery, or a rechargeable battery. When the power supply 1808 includes a rechargeable battery, the rechargeable battery can be a wired rechargeable battery or a wireless rechargeable battery. A wired rechargeable battery is a battery that is charged through a wired line, and a wireless rechargeable battery is a battery that is charged through a wireless coil. The rechargeable battery can also be used to support fast charging technology.

[0331] In some embodiments, the electronic device 1800 further includes one or more sensors 1810 , including but not limited to: an acceleration sensor 1811 , a gyroscope sensor 1812 , a pressure sensor 1813 , an optical sensor 1814 , and a proximity sensor 1815 .

[0332] The acceleration sensor 1811 can detect the magnitude of acceleration on the three coordinate axes of the coordinate system established by the electronic device 1800. For example, the acceleration sensor 1811 can be used to detect the components of gravity acceleration on the three coordinate axes. The processor 1801 can control the touch display screen 1805 to display the user interface in a horizontal view or a vertical view according to the gravity acceleration signal collected by the acceleration sensor 1811. The acceleration sensor 1811 can also be used for collecting game or user motion data.

[0333] The gyro sensor 1812 can detect the body direction and rotation angle of the electronic device 1800, and the gyro sensor 1812 can cooperate with the acceleration sensor 1811 to collect the user's 3D actions on the electronic device 1800. The processor 1801 can implement the following functions based on the data collected by the gyro sensor 1812: motion sensing (such as changing the UI according to the user's tilt operation), image stabilization during shooting, game control, and inertial navigation.

[0334] The pressure sensor 1813 can be set on the side frame of the electronic device 1800 and / or the lower layer of the touch display screen 1805. When the pressure sensor 1813 is set on the side frame of the electronic device 1800, it can detect the user's holding signal of the electronic device 1800, and perform left and right hand recognition or shortcut operations according to the holding signal. When the pressure sensor 1813 is set on the lower layer of the touch display screen 1805, the operability controls on the UI interface can be controlled according to the user's pressure operation on the touch display screen 1805. The operability controls include at least one of a button control, a scroll bar control, an icon control, and a menu control.

[0335] The optical sensor 1814 is used to collect the ambient light intensity. In one embodiment, the processor 1801 can control the display brightness of the touch display screen 1805 according to the ambient light intensity collected by the optical sensor 1814. Specifically, when the ambient light intensity is high, the display brightness of the touch display screen 1805 is increased; when the ambient light intensity is low, the display brightness of the touch display screen 1805 is reduced. In another embodiment, the processor 1801 can also dynamically adjust the shooting parameters of the camera assembly 1806 according to the ambient light intensity collected by the optical sensor 1814.

[0336] The proximity sensor 1815, also called a distance sensor, is usually arranged on the front of the electronic device 1800. The proximity sensor 1815 is used to collect the distance between the user and the front of the electronic device 1800. In one embodiment, when the proximity sensor 1815 detects that the distance between the user and the front of the electronic device 1800 is gradually decreasing, the processor 1801 controls the touch display screen 1805 to switch from the screen-on state to the screen-off state; when the proximity sensor 1815 detects that the distance between the user and the front of the electronic device 1800 is gradually increasing, the processor 1801 controls the touch display screen 1805 to switch from the screen-off state to the screen-on state.

[0337] Those skilled in the art will understand that Fig.18 The structure shown in the figure does not constitute a limitation on the electronic device 1800, and may include more or less components than those shown in the figure, or combine certain components, or use different component arrangements.

[0338] The present application also provides a terminal, which includes: a host program and a reminder assistant applet; the reminder assistant applet depends on the host program to run, and the terminal is used to implement the reminder message receiving method and reminder message sending method provided by the above-mentioned method embodiments.

[0339] The present application also provides a computer device, which includes: a processor and a memory, wherein the memory stores at least one instruction, at least one program, a code set or an instruction set, and the at least one instruction, at least one program, a code set or an instruction set is loaded and executed by the processor to implement the reminder message receiving method and the reminder message sending method provided in the above-mentioned method embodiments.

[0340] The present application also provides a computer-readable storage medium, which stores at least one instruction, at least one program, code set or instruction set. The at least one instruction, the at least one program, the code set or instruction set is loaded and executed by the processor to implement the reminder message receiving method and reminder message sending method provided in the above-mentioned method embodiments.

[0341] It should be understood that the "plurality" mentioned in this article refers to two or more. "And / or" describes the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the associated objects are in an "or" relationship.

[0342] A person skilled in the art will understand that all or part of the steps to implement the above embodiments may be accomplished by hardware or by instructing related hardware through a program, and the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a disk or an optical disk, etc.

[0343] The above description is only a preferred embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application should be included in the protection scope of the present application.

Claims

1. A method for receiving a reminder message, It is characterized in that The method is performed by a first client, and includes: Get the topic title of the reminder topic; According to the subject title of the reminder subject, display the authorization reminder interface of the reminder subject; After receiving the authorization operation on the authorization reminder interface, granting the reminder subject a reminder permission with limited conditions, wherein the limited conditions include at least one of a limited time and a limited number of times, wherein the limited time is used to indicate the duration for which the second client is allowed to send the reminder message, and the limited number of times is used to indicate that the second client is allowed to send the reminder message a limited number of times; The reminder message of the reminder topic is received.

2. The method according to claim 1, It is characterized in that After receiving the authorization operation on the authorization reminder interface, granting the reminder subject a reminder permission with limited conditions, including: When the confirmation control on the authorization reminder interface is triggered, a first authorization instruction of the reminder subject is sent to the server, where the first authorization instruction is used to instruct the server to grant a valid reminder permission to the reminder subject once; or, After the number setting control on the authorization reminder interface is set to n, a second authorization instruction of the reminder subject is sent to the server, wherein the second authorization instruction is used to instruct the server to grant n valid reminder permissions to the reminder subject; or, After the event setting control on the authorization reminder interface is set to t, a third authorization instruction of the reminder subject is sent to the server, and the third authorization instruction is used to instruct the server to grant the reminder subject a reminder authority valid for a period of t.

3. The method according to claim 2, It is characterized in that Any one of the first authorization indication, the second authorization indication and the third authorization indication carries: the subject identifier of the reminder subject and the limited condition.

4. The method according to any one of claims 1 to 3, It is characterized in that The acquiring of the subject information of the reminder subject includes: Scan the graphic code corresponding to the reminder theme; The subject title of the reminder subject is read from the graphic code.

5. The method according to any one of claims 1 to 3, It is characterized in that The method is applied to a host program running a reminder assistant applet, and the reminder assistant applet depends on the host program to run; The authorization reminder interface is the applet interface of the reminder assistant applet.

6. The method according to claim 5, It is characterized in that After receiving the reminder message of the reminder topic, the method further includes: The reminder message is displayed in a strong reminder mode, and the strong reminder mode includes at least one of the following reminder modes: Displaying the reminder message on the lock screen interface; Displaying the reminder message in a message display page provided by the reminder assistant applet; Displaying the reminder message in a message display page provided in the host program; Invoking the operating system through the host program or the reminder assistant applet to play the reminder sound corresponding to the reminder message; The host program or the reminder assistant applet calls the operating system to control the signal light for reminder.

7. The method according to claim 5, It is characterized in that After granting the reminder subject with limited conditional reminder permission, the method further includes: Displaying the authorized reminder subject in the program interface of the host program; Receiving a deletion operation on the authorized reminder topic; The reminder permission granted to the reminder subject is cancelled according to the deletion operation.

8. A method for receiving a reminder message, It is characterized in that Applied to a terminal having a first host program and a first reminder assistant applet installed therein, wherein the first reminder assistant applet depends on the first host program to run, the method comprising: The first client scans the graphic code corresponding to the reminder theme through the first host program; The first client obtains a subject title corresponding to the reminder subject from the graphic code; The first client calls the first reminder assistant applet through the first host program, and displays the authorization reminder interface of the reminder subject according to the subject title of the reminder subject through the first reminder assistant applet; After receiving the authorization operation on the authorization reminder interface, the first client grants the reminder subject a reminder permission with limited conditions, wherein the limited conditions include at least one of a limited time and a limited number of times, wherein the limited time is used to indicate the duration for which the second client is allowed to send the reminder message, and the limited number of times is used to indicate that the second client is allowed to send the reminder message a limited number of times; The first client receives a reminder message of the reminder topic through the first reminder assistant applet.

9. A method for sending a reminder message, It is characterized in that The method comprises: Display the reminder topic creation interface; Creating the reminder topic according to the creation operation received in the creation interface; Obtaining an authorized user corresponding to the reminder subject, wherein the authorized user is a user account that grants the reminder subject a reminder authority with limited conditions, wherein the limited conditions include at least one of limited time and limited number of times; Send a reminder message to the authorized user corresponding to the reminder topic.

10. The method according to claim 9, It is characterized in that The obtaining of the authorized user corresponding to the reminder topic includes: Displaying a graphic code corresponding to the reminder theme, wherein the graphic code carries a theme identifier of the reminder theme; The authorized user who scans the graphic code for authorization processing is obtained.

11. The method according to claim 9, It is characterized in that The creation interface displays a reminder theme setting control; The step of creating the reminder topic according to the creation operation received in the creation interface includes: Receiving a reminder theme editing operation on the reminder theme setting control in the creation interface; Obtaining a subject title of the reminder subject according to the reminder subject editing operation; The reminder topic is created according to the topic title of the reminder topic.

12. The method according to claim 11, It is characterized in that The creation interface also displays a content setting control; Before creating the reminder topic according to the topic title of the reminder topic, the method further includes: Receiving a content editing operation on the content setting control in the creation interface; Obtaining a topic introduction of the reminder topic according to the content editing operation; The reminder topic is created based on the topic title of the reminder topic and the reminder topic content.

13. The method according to any one of claims 9 to 12, It is characterized in that The sending of a reminder message to an authorized user corresponding to the reminder topic includes: Display the reminder message editing interface of the reminder topic; Receiving a reminder message editing operation in the reminder message editing interface; Obtaining the reminder message according to the reminder message editing operation; The reminder message is sent to the authorized user corresponding to the reminder topic.

14. A method for sending a reminder message, It is characterized in that Applied to a terminal having a second host program and a second reminder assistant applet installed, the second reminder assistant applet running dependent on the second host program, the method comprising: Displaying a reminder topic creation interface through the second reminder assistant applet; Creating the reminder topic through the second reminder assistant applet according to the creation operation received in the creation interface; Obtaining, through the second reminder assistant applet, an authorized user corresponding to the reminder subject, wherein the authorized user is a user account that grants the reminder subject a reminder permission with limited conditions, wherein the limited conditions include at least one of limited time and limited number of times; Send a reminder message to the authorized user corresponding to the reminder topic through the second reminder assistant applet.

15. A method for sending a reminder message, It is characterized in that The method comprises: The backend server receives the authorization instruction sent by the first client through the first reminder assistant applet; The backend server grants a reminder permission with limited conditions to the reminder subject according to the authorization indication, wherein the limited condition includes at least one of a limited time and a limited number of times, wherein the limited time is used to indicate the duration for which the second client is allowed to send the reminder message, and the limited number of times is used to indicate that the second client is allowed to send the reminder message a limited number of times; The backend server receives a reminder message of the reminder topic sent by the second client through the second reminder assistant applet; When the reminder message meets the limited condition, the background server sends the reminder message to the first reminder assistant applet.

16. The method according to claim 15, It is characterized in that The backend server receives a reminder message of the reminder topic sent by the second client through the second reminder assistant applet, including: The backend server receives a reminder topic creation request sent by the second client through the second reminder assistant applet, wherein the creation request carries a topic title of the reminder topic; The backend server creates a subject identifier of the reminder subject according to the subject title of the reminder subject; The background server feeds back the theme identifier of the reminder theme to the second reminder assistant applet, and the theme identifier of the reminder theme is used by the second reminder assistant applet to generate a graphic code corresponding to the reminder theme.

17. A device for receiving a reminder message, It is characterized in that The device comprises: An acquisition module is used to obtain the subject title of the reminder subject; A display module, used to display the authorization reminder interface of the reminder subject according to the subject title of the reminder subject; A receiving module, configured to grant a reminder permission with limited conditions to the reminder subject after receiving the authorization operation on the authorization reminder interface, wherein the limited condition includes at least one of a limited time and a limited number of times, wherein the limited time is used to indicate the duration for which the second client is allowed to send the reminder message, and the limited number of times is used to indicate that the second client is allowed to send the reminder message a limited number of times; The receiving module is further used to receive the reminder message of the reminder topic.

18. A device for sending a reminder message, It is characterized in that The device comprises: A display module, used to display a reminder topic creation interface; The receiving module is used to create a reminder topic according to the creation operation received in the creation interface; An acquisition module, used to acquire an authorized user corresponding to a reminder subject, where the authorized user is a user account that grants a reminder permission with limited conditions to the reminder subject, where the limited conditions include at least one of a limited time and a limited number of times; The sending module is used to send messages to authorized users corresponding to the reminder topic.

19. A terminal, It is characterized in that The terminal includes: a host program and a reminder assistant applet; the reminder assistant applet depends on the host program to run, and the terminal is used to implement the reminder message receiving method as described in any one of claims 1 to 8 and the reminder message sending method as described in any one of claims 9 to 16.

20. A computer-readable storage medium, It is characterized in that The storage medium stores at least one instruction, at least one program, a code set or an instruction set, and the at least one instruction, the at least one program, the code set or the instruction set are loaded and executed by the processor to implement the method for receiving the reminder message as described in any one of claims 1 to 8 and the method for sending the reminder message as described in any one of claims 9 to 16.