WO2021212476A1 - Communication method, device and system - Google Patents

Abstract

Disclosed are a communication method, a device and a system. Said method comprises: acquiring a message determined by a user; acquiring a condition set by a user; issuing an instruction for creating the condition; creating the condition; determining whether the condition set by the user is created successfully, the information of the unsuccessful creation being displayed on a client of the user in cases where the condition set by the user is not created successfully, and the message being displayed on a client of a receiver of the message after the condition set by the user is satisfied in cases where the condition set by the user is created successfully. By means of the present disclosure, condition messages that are trustworthy to users are sent.

Description

A communication method, equipment and system Technical field

The present disclosure relates to the field of computing technology, in particular to a communication method, equipment and system.

Background technique

Some existing instant messaging applications can send messages regularly. However, in other cases, for example, the sender sets a certain position when sending the message, and the message can be displayed only when the terminal device of the recipient reaches the position. At this time, it is possible that because the GPS of the receiver's terminal device is not turned on or damaged, the correct position of the receiver's terminal device cannot be obtained, so that the receiver cannot receive the corresponding message even if it reaches the set position. At this time, the sender does not know that it is impossible to send the message, and therefore fails to take other measures.

Summary of the invention

The technical problem to be solved by the present disclosure is to provide a communication method that can ensure the integrity and accuracy of communication and improve the efficiency of the communication process.

The present disclosure proposes a communication method, which is applied to the client, and includes:

Acquiring a message determined by the user, where the message includes the recipient and content of the message;

Get the conditions set by the user;

Issue an instruction to create the condition set by the user, or send the condition set by the user;

Obtain the information about whether the user setting condition is successfully created, where:

In the case that the creation of the user setting condition is unsuccessful, the message indicating that the creation of the condition is unsuccessful is displayed; in the case that the creation of the user setting condition is successful, when the user setting condition is satisfied, the message is received The client of the party displays the message.

Corresponding to the above method, the present disclosure proposes a terminal device including a memory and a processor, where the memory is used to store executable instructions; the processor is used to execute the instructions to implement the method according to the above communication.

The present disclosure also proposes a server device, including a memory, for storing computer program instructions for executing the above-mentioned communication method for downloading.

The present disclosure also proposes a communication method applied to a server, including:

Obtain a user-determined message sent by the client and conditions set by the user, where the message includes the recipient and content of the message;

Issue an instruction to create the condition according to the condition set by the user;

Determine whether the user setting condition is successfully created;

Sending information about whether the user setting conditions are successfully created to the client, where:

In the case that the creation of the user setting conditions is unsuccessful, the client displays the information that the creation is unsuccessful; in the case that the creation of the user setting conditions is successful, when the user setting conditions are met, the The client of the recipient of the above condition displays the message.

Corresponding to the above method, the present disclosure also proposes a server device, including a memory and a processor, where the memory is used to store executable instructions; the processor is used to execute the instructions to implement the above communication method.

The present disclosure also proposes a communication method, including:

Acquiring a message determined by the user, where the message includes the recipient and content of the message;

Get the conditions set by the user;

Issue an instruction to create the condition according to the condition set by the user;

Create the conditions;

It is determined whether the creation of the user setting condition is successful, wherein, in the case that the creation of the user setting condition is unsuccessful, the message that the creation is unsuccessful is displayed on the client of the user; and the creation of the user setting condition is successful In this case, when the conditions set by the user are satisfied, the message is displayed on the client of the recipient of the message.

The present disclosure also proposes a communication system, which is characterized in that it includes at least a client and a server, and executes the above-mentioned communication method.

Compared with the prior art, the communication method, terminal device and server device described in the present disclosure enable the sender to reliably send condition-based messages by adopting the above technical solutions, thereby enhancing the reliability of condition-based messages.

Description of the drawings

FIG. 1 is a schematic diagram of a computer architecture of an embodiment of the present disclosure;

FIG. 2 is a schematic diagram of a system constituted by a terminal device and a server according to an embodiment of the present disclosure;

3 to 11 are schematic diagrams of the interface of the first embodiment of the present disclosure;

12 to 15 are schematic diagrams of the interface of the second embodiment of the present disclosure;

16 to 19 are schematic diagrams of the interface of the third embodiment of the present disclosure;

FIG. 20 is a diagram of a friend display list interface in an embodiment of the present disclosure;

Figure 21 is a flowchart of three main core links in an embodiment of the present disclosure;

FIG. 22 is a flowchart of a client sending a condition message in an embodiment of the present disclosure;

FIG. 23 is a processing flowchart of a message server in an embodiment of the present disclosure;

FIG. 24 is a flowchart of a conditional message system in an embodiment of the present disclosure;

FIG. 25 is a flowchart of a general method of an embodiment of the present disclosure;

26 to 29 are schematic diagrams of the interfaces of the fourth and fifth embodiments of the present disclosure;

Detailed ways

The specific embodiments of the present disclosure will be described in further detail below in conjunction with the accompanying drawings of the specification.

For the terminal device or server used in the embodiments of the present disclosure, refer to the schematic diagram of the computer structure shown in FIG. 1. In the figure, the computer system 10 includes a central processing unit (CPU) 12, a random access memory (RAM) 13, a storage unit 14, a communication unit 15, an input unit 16, and a display unit 17 connected via a communication bus 11.

The central processing unit CPU12 can comprehensively control the processing executed by the computer system 10. RAM13 is volatile memory. The storage unit 14 may be a non-volatile storage medium, including, for example, a readable storage medium such as a magnetic hard disk, a solid state hard disk, an optical disk, or a flash memory disk. Among them, common flash memories include NAND, NOR, and the like. Generally, programs or codes can be stored in the storage unit 14 in advance, and after being loaded into the RAM 13 by the CPU 12, the CPU 12 executes the program instructions to complete corresponding functions.

The communication unit 15 may include, for example, an RJ45 module for a network adapter, a WIFI module, a 2G-5G mobile communication module, or a Bluetooth module. The computer system can be connected to the network through the communication unit 15 and communicate with other computer systems on the network.

The input unit 16 includes a keyboard, a mouse, or a touch screen, etc. On the client, the user can issue instructions to the computer system 10 through operations performed on the input unit 16.

The display unit 17 may include a graphics controller and a display device connected to the graphics controller, and specifically may include a liquid crystal (LCD), a light emitting diode (LED) display, a cathode ray tube (CRT) display, or a touch screen.

The computer system 10 may use operating systems such as Windows, Andriod, iOS, or Linux.

It should be noted that this hardware configuration is only an example. In addition, a computer system with different hardware than that shown in FIG. 1 can also be used. For example, some servers can remove the display unit, and some terminal devices have cameras. Specifically, the terminal device of the embodiment of the present disclosure may be a mobile device such as a mobile phone, a tablet computer (PAD), or a notebook computer, as well as a desktop computer.

FIG. 2 is a schematic diagram of the structure of a network system 20 composed of a terminal device 21 and a server 23 used in an embodiment of the disclosure. The terminal device 21 and the server 23 are connected through the network 22. The network 22 may be a local area network or the Internet, etc., and protocols such as Hypertext Transfer Protocol (HTTP), Transmission Control Protocol/Internet Protocol (TCP/IP), or Wireless Internet (WIFI) are used for communication. The server 23 may have the same computer architecture as FIG. 1, and the storage device in its storage unit 14 contains instructions capable of implementing the method provided by the embodiment of the present disclosure. The server 23 may adopt server frameworks such as Tomcat, Nginx, Spring Boot, Spring Cloud, etc., so that the server can communicate with its clients.

In another network system shown in FIG. 2, the terminal device 21 can download the instruction from the storage device of the server 23 via the network 22, and after execution, the method provided in the embodiment of the present disclosure can be implemented.

The ellipsis in all the drawings in the embodiments of the present disclosure represent specific content. Because it has nothing to do with the subject matter to be protected by the embodiments of the present disclosure, and to highlight the key point, it is indicated by an ellipsis.

The method of sending a message disclosed in the present disclosure does not directly send the message to the receiving user, but when certain conditions are met, it is finally transmitted to the receiving user and displayed on the client. This article calls this kind of message a conditional message.

First, the first embodiment will be described.

Emily lives in California, USA. She is a secretary of a company. She is busy at work, so she had to set a message in advance to remind her manager of the meeting the next day.

FIG. 3 is the communication interface 300 with the manager on the Emily client. Among them, 311 items are the user names of their managers, and items 321 and 322 are the usual conversations between the two, and the specific content is omitted. The 301 vertical bar on the far right indicates that the area on its left can be slid. In the bottom area, item 332 is a message input box, item 333 is a send button, and item 331 is an extension button.

Click this 331 item expansion button, the bottom area of the interface 300 expands and becomes as shown in FIG. 4. Among them, items 341 to 344 are buttons corresponding to voice input, video input, photo input, and transfer instructions, which can be clicked to send corresponding messages. These are all existing technologies.

Click the "Condition" button of item 345, and the setting interface 500 of the condition message shown in FIG. 5 will appear. Among them, item 511 indicates that the interface name is "Set Condition". The interface includes a message input area 520, of which item 521 is an enlarged message input box, and below are the aforementioned icons 341-344. The interface also includes a condition setting area 530. Among them, item 531 displays "Condition", item 532 is "Name", which means that the input in the input box behind it is the name of the condition message, so that the user can use this name to search for the condition message. The user may not enter this name. The following items 533, 534, and 535 are buttons for adding conditions, corresponding to "increase time", "increase position", and "increase other" respectively.

Emily enters the message "Listen to the financial report in your office" in the input box 521, and then in order to set the sending time of this message, click item 533, and the interface 600 shown in Figure 6 appears. The top 611 item shows "Timing" (timing). The timing setting includes the date setting in the area 620 and the specific time setting in the date in the area 630.

In area 620, item 621 displays “Day Setting”, item 622 to item 625 are four setting interfaces that can only be single-selected. Item 622 is to set a specific date; item 623 is to set the date range; item 624 indicates that the date is set to "every day"; item 625 indicates that the date is set to "every working day". Emily selected the above 622 items and set the date as "September 4, 2019".

In the area 630, item 631 displays "Hour&Minute Setting", and the four checkboxes below are used to input hours and minutes. Among them, the 632 items and 633 items are used to input the specific time; and the upper and lower input boxes of the 634 item are used to input the time period, which respectively indicate the start time and the end time. Emily selects the above 634 items and sets the time from "9:00" to "10:30".

After Emily sets the time in the interface 600 shown in FIG. 6, she clicks the "Increase Time" button in item 641 in FIG. 6 to return to the previous interface 500 shown in FIG. 7. Compared with the interface in Figure 5, Figure 7 has added 5331 items under 533 to display user setting conditions, and the time indicated is the above set time, that is, from 9:00 to 10:30 on September 4, 2019. After Emily enters the name of the conditional message "Schedule" after item 532, and clicks the item button "Send" of item 541, the client terminal returns to the dialogue interface 300 between Emily and the manager as shown in FIG. 8.

Item 821 in Figure 8 is the time when this message was sent, which is 6:36 pm on September 3. Item 827 is the specific message content, which is the same as item 521 in Figure 7. Compared with general instant messages, 822 items indicating that this is a conditional message ("Condition Message") have been added, 823 items indicating its name is "Schedule" (plan), and 824 items indicating its status ("Satus") . Among the 824 items, it is also shown that the condition is not established ("No Established"), and the 825 item in the next row shows that the reason ("Reason") is a time conflict ("Time Conflict"). Emily clicks on the 825 item, and the window shown in Figure 9 pops up. Among them, 911 is the title, which displays "Reason: Time Conflict". The specific reasons are shown below, of which 921 items show "In the plan, September 4, 2019 is scheduled from 9:00 to 10:00." 922 items show that the existing arrangement is "hosting a technical meeting in room 807". That is, in the previously set condition message of the same name "Schedule", a meeting to be held from 9:00 to 10:00 on the same day has been set. Since the start time is the same as the new setting, it starts at 9:00, so the time of the two conflicts, so the above information is displayed.

Emily clicks the 923 item confirmation button, returns to the interface shown in Figure 8, and clicks the 826 item "Reset" (reset). At this time, the client terminal displays the interface shown in Figure 6 again, and Emily changes the time of item 634 from "14:30" to "16:00". After Emily confirms the modified time, the client returns to the dialog interface 300 with the manager, as shown in Figure 10. 1022～1026 items are added in the figure. Compared with the above 822～827 items, the difference is that the status of 1024 items is displayed as "Estalished" (established), indicating that the condition has been created successfully, and the 1025 items display "No Show". "Means that because the conditions have not been met, that is, the above set time has not been reached, it has not been displayed on the client of the recipient, that is, Emily’s manager.

On the second day, at 9:00 am on September 4, in the dialog window with Emily in the Emily manager client, as shown in Figure 11, the condition message 1121 item set earlier was first received. "Host a technical meeting in room 807". Then at 2:30 in the afternoon, I received 1122 items of the condition message set the day before, the content is the same as item 1026 in Figure 10 above, that is, "listen to the financial report in your office".

When a logic error is found when setting the conditions, such as the time conflict in this embodiment, the error message is displayed as items 824 and 825 in Figure 8. In this way, the rationality of the time arrangement is ensured. If the logic error is not checked and the error prompt is not displayed, Emily will not revise the work plan, which will eventually lead to confusion in the work.

In another embodiment, other colleagues of Emily want to use the above room 807, and the time conflicts with the time when Emily’s manager presides the meeting, this will also cause logic errors.

The following is the second embodiment, using position conditions.

Davis is Emily's husband. On September 6th or 7th, Emily will go shopping at Wal-Mart, but she is not sure when. Since Davis was going on a business trip, in order to remind Emily, he sent a conditional message in the dialogue with Emily. That is, in the condition setting interface 500 shown in FIG. 5, click 534 item "add position", and the position selection interface 1200 shown in FIG. 12 appears. The top 1211 item displays "Select Place". After Davis enters "Wallmart" in the 1221 item input box below, the map display area 1230 is automatically located to the nearest Wal-Mart supermarket, as shown in the figure 1231 As shown in the item. These are all existing technologies. Finally, Davis clicked the 1241 button to confirm.

At this time, return to the interface 500 shown in FIG. 13. In the figure, a display address of 5341 has been added, namely "Wal-Mart, 1919 Davis Street, San Leandro, California". Davis enters the message content "Dear, buy me a razor" in the 521 entry box in the picture, and then clicks 541 to send this conditional message.

After it is sent, the dialogue interface with Emily on Davis' client will display the information of the condition message as shown in items 1422 to 1425 in Figure 14. Among them, the status of the 1422 display conditions ("Status") is not established ("No EstAblished"), and the 1423 display reason ("Reason") is that the other party's GPS is not turned on ("GPS Not Opned"). Therefore, after Davis clicks 1424 "Reminder" (reminder), the client automatically generates and sends an instant message to Emily as shown in item 1431 for the user Davis, and the content is "Please be the condition The message turns on GPS".

When Emily saw the above message at noon the next day, she turned on the GPS. After the system detected it, the dialogue interface with Emily in Davis' client showed the conditional messages of 1441～1443. The status of the condition message is as shown in item 1442: the other party's GPS is turned on, the condition is successfully established, and it is not displayed. The content of the message is 1443 items, the same as the above 1425 items.

In the end, Emily decided to go to the supermarket on September 7th, the last day of Davis's business trip. When Emily drove to the Wal-Mart Supermarket at 3:05 pm, the system detected that the location conditions were met. At this time, in the dialogue interface between Emily’s client and Davis, three items as shown in Figure 15 were received. Conditional message. Since the trigger conditions are the same, they are all displayed in a large box. Among them, 1521 items are 1443 items in Figure 14, 1531 items and 1541 items are the news that Davis added later, such as September 5 and 6, and the contents are "and bread", "beef and milk" respectively. .

In this embodiment, if it is not detected whether Emily's GPS is turned on, Davis' client will not display the message that the condition creation is unsuccessful, and thus will not be processed further. In this way, when Emily arrives at the Wal-Mart supermarket, she will not receive a message from Davis.

The following is the third embodiment.

In addition to time and location, Emily can also send conditional messages triggered by other events to Davis in the interface shown in Figure 5. When Emily clicks 535 item "add other" in FIG. 5, the other event setting interface 1600 shown in FIG. 16 is obtained. Among them, 1611 items display "Select Other Events", 1621 items display "Weather" (weather), the following three options correspond to "Rain" (雨), "Snow" (下雪) and "Cold wave" (寒潮). After Emily selects the first item, 1622 "Rain", click the 1691 "Add" button at the bottom, so in the interface 500 shown in Figure 17, add the 5351 item "Weather, rain" "Event, and the client automatically adds "it will rain at [&Time]. Bring an umbrella" in the message input box of 521 in the interface. The message is pre-set according to conditions, where "[&Time]" represents the forecasted time when it will rain, which is replaced by the system according to the actual time. .

Emily also clicked on the 533 items in the above figure, in the interface shown in Figure 6 that appeared, single-selected 625 items "every working day", checked the 632 items and filled in the specific time, and finally clicked on the 641 item. A time condition is added to the returned interface 500, as shown in item 5332 in Figure 17, which means "7:50 in the morning of every working day". In this way, Emily sets two conditions on the interface shown in Figure 17.

After Emily presses the 541 "Send" button in Figure 17 described above, she sends a conditional message to the message server, but the message server itself cannot provide weather conditions, so it is necessary to check whether it is accessible and can provide weather forecasts. Weather server. When it is detected that access is possible and the weather server can return weather forecast data, a message prompting the establishment of the weather conditions on Emily's client is successful, as shown in item 1821 "Established" in FIG. 18. The content of item 1822 in the figure is the same as the content of item 521 in figure 17.

Although the conditions were created successfully, due to a problem with the weather server on a certain day, for example, the connection between the message server and the weather server was interrupted, the weather server was down, the weather sensor connected to the weather server failed, etc., the monitoring of the weather conditions failed , Facing the situation that Davis could not receive the conditional message even if it was about to rain. At this time, in the dialogue interface between Emily and Davis in Fig. 18, a message box 1830 indicating that the condition monitoring fails is displayed. Among them, 1831 items show that the message source is "System Messages", 1832 items show that the status of conditional messages is "Failed", indicating that the condition monitoring is invalid; 1833 items show that the reason for the failure is "Weather Server Error" ( Server error); Item 1834 displays "Reminder" (reminder), item 1835 is the original message content, the same as item 1822.

Emily clicks on the above item 1834, so in the dialogue interface with Emily on the Davis client shown in Figure 19, the content in the 1920 box is displayed. Among them, items 1921 and 1922 are the same as items 1832 and 1833 in the above figure 18, which respectively display the condition failure information and the reason for the failure. Item 1923 displays "Continue when the weather server is restored?", the 1924 item "OK" button below it means confirmation, and the 1925 item button "Cancel" means canceling this conditional message. Davis pressed the 1924 confirmation button. Later, when the weather server was restored, not only the message that the conditions were established ("Established") was displayed on the sender client, but also the 1932 message "weather server restored" was displayed on the interface shown in Figure 19 on the receiver client. According to item 1931, the message is "System Message" (system message). At this time, the conditions are re-established.

When Davis usually goes out to work at about 8:00 in the morning. When the above-mentioned set time is 7:50 on a certain working day, as the above-mentioned weather conditions are detected to be met, Davis’ client receives Emily’s conditional message as shown in item 1941 in Figure 19, reminding "this afternoon It's going to rain, please bring an umbrella." Among them, "[&Time]" in item 521 in Figure 17 is replaced by "this afternoon" (this afternoon) by the system. In this embodiment, when the sender Emily receives the information that the successfully created condition is invalid, she chooses to send a reminder message to the receiver Davis. Therefore, even if the message server is not restored, Davis can determine whether it is raining or not by going directly to other weather service websites. If the failure message is not displayed when the weather server fails, both parties believe that the conditions are still valid, which will cause Davis to not bring an umbrella because he does not know it is going to rain.

In another embodiment, Davis can send himself a message about the weather conditions.

Summarizing the above embodiments, the condition in the condition message may be related to time and location, or other events. The conditions may have parameter settings, such as specific time, location, etc., or there may be no parameters. When the conditions preset by the user are met, for example, the weather forecast in the third embodiment is about to rain, the conditions are triggered, and the common terminology in this field is the occurrence of the event. In order to monitor whether the condition is triggered, a listener can be established to monitor the event.

The communication system adopting the method of the present disclosure is referred to as a conditional message communication system in this article. The system at least includes a client and a message server. Wherein, the client may be installed on the terminal device 21 of the network system shown in FIG. 2, and the message server may be installed on the server device 23 in FIG. 2. The two can be connected through the network 22 so that the system can send and receive conditional messages. At the same time, instant messaging can also be carried out.

In one embodiment, in order to ensure the normal and effective operation of the conditional message communication system, compared with the existing instant messaging, the communication system at least realizes three main core links as shown in FIG. 21.

The first core link S1 is to issue an instruction to establish a corresponding listener according to the conditions selected by the user. The system first identifies the condition selected by the user, and issues an instruction to monitor whether the condition is met, that is, to monitor the event, such as an instruction to establish a listener that can monitor the event. A listener is a component that listens to a state change of a domain object, that is, a monitoring mechanism established to detect whether the conditions are met. For example, in the scene of using the Java language, the interface EventListener can be used as the base class to establish the class and object of the listener; in the environment of using PHP, the event binding mechanism can be used to realize the monitoring and so on.

The system should determine the source of the condition according to the condition, that is, the location where the condition is generated or triggered, and the type of listener corresponding to the condition. For example, the system in the first embodiment recognizes that a time listener can be established in the message server. In the second embodiment, the system recognizes that a location listener is to be established on the receiver's device. According to the third embodiment, the system can identify whether it is raining or not on the weather server according to the conditions. In this link, the system can first identify the location of the condition, such as the sender client, receiver client or weather server, and then send the condition over, and finally determine the corresponding condition at the specific location. The type of listener.

The second core link is S2, which is the establishment of a listener and monitoring. In this link, the first step is to ensure that the listener can be established according to the instructions of the above S1 link. For example, in the third embodiment above, if the listener is provided in the weather server, the weather server can establish a corresponding listener, such as whether it is raining, according to the instructions issued by the message server in the above S1 link. If the weather server receives the instruction but cannot establish a listener according to the instruction, the condition cannot be monitored. This requires the cooperation of the weather server with corresponding modules to complete the function of establishing a listener.

Second, make sure that the listener can successfully listen. The working mechanism of the listener is to judge the specific data related to the condition. Therefore, in order to achieve successful monitoring, it is also necessary that the data can be provided normally. For example, for the time-related conditions in the first embodiment, since there are generally stable and reliable timing devices on the sender terminal device, the receiver terminal device, and the message server device, and the operating system provides access to the timing device, Therefore, the time data for judging whether the conditions are met can be stably provided, and there is the right of access at any time, so the time conditions can be regarded as the internal conditions of the conditional message communication system of the present disclosure. For another example, in another embodiment, after the received message is monitored, it is checked if a certain preset keyword is contained in the message, and then the message is forwarded. The message in this embodiment is the internal data of the conditional message communication system, which can be fully grasped, so the conditions established on the message data also belong to the internal conditions of the communication system. Since the data of the internal conditions can be obtained completely, it is always possible to effectively monitor whether the internal conditions are triggered according to the data.

In contrast, the condition data of external conditions may not always be provided normally and stably. For example, in the second embodiment, since the GPS on the mobile phone of the receiver client is not turned on, even if a listener is set up, since there is no location data provided by the GPS, it is impossible to determine whether Emily has reached the Wal-Mart supermarket. Location. Another example is the weather event in the third embodiment. If the weather data sensor connected to the weather server is faulty, it will not be able to successfully monitor whether there is a preset rainy weather. These situations are not solvable by the conditional message communication system itself, and belong to the situation where an external condition error cannot be successfully monitored. Therefore, when establishing a listener for external conditions, it is also necessary to check whether the data of the external conditions can be provided normally.

Only when the listener is established and the data required by the listener can be obtained normally and steadily, can the condition trigger be accurately captured. This situation belongs to the successful creation of the condition.

Furthermore, after the listener is established, it is necessary to check whether the provision of the data required by the condition is wrong. When a problem is found, such as when the GPS described in the second embodiment is turned off again, a message can be sent to the sender and the receiver at the same time to remind the monitoring of the conditions to be invalid. That is, when it is impossible to monitor whether the condition occurs, the user should be informed of this situation, so that the user has the opportunity to correct the error, or use other methods to deliver the message.

Regardless of internal or external conditions, logic error checking steps can be added as in the first embodiment. The logic error generally refers to an error caused by resource conflicts caused during setting, such as time resources, office resources, and so on. If there is a logical error, even if a preset message is received after the condition is triggered, it will be meaningless to the receiving user due to the existence of the error. So check for logic errors when creating conditions. If a logical error is found and the condition creation is unsuccessful, it will be reported back to the user in time, so that the user can correct the error in time and avoid the loss caused by the error. See the situation in Example 1.

In another embodiment, the listener can be established directly according to user instructions, ignoring logic errors. This situation is artificially canceling logical errors.

Only when there is no external condition error and no logic error, can a listener be established for the condition according to the instructions of the above S1 link and work effectively, and the condition can be called successful creation. When the conditions are successfully created, item 1024 in Figure 10 can display "Established".

The third core link S3 is to process monitoring signals. When the listener detects that the event occurs, that is, when the user setting condition is met, it will send a signal, indicating that the user setting condition corresponding to the listener has been met. The system can identify this signal, find the message corresponding to the signal, and send the message to the recipient client and display it. For example, in the third embodiment, when the weather forecast is raining as set in advance, the listener established on the weather server sends a monitoring signal to the message server. After receiving the signal, the message server finds the corresponding message and sends it to the client of the recipient.

The realization position of each of the above three links can be on the sender, server or receiver respectively. The positions of the three links can be different or the same.

For example, for the time monitoring in the first embodiment, the timer of the sender device can be used, and all the steps are completed in the sender client; or the timer of the message server device can be used to complete all the steps in the message server; The timer of the receiver's device is all completed in the receiver's client. For the location monitoring in the second embodiment, the S1 and S3 links can be completed in the message server, and the GPS listener can be set on the receiver's client to realize the S2 link; S1 can also be completed in the message server, and the S1 link can be completed in the receiver's client. After completing S2 and S3, the message is first sent to the recipient's client, and the message is displayed only when it is monitored that the mobile phone where the recipient's client is located arrives at the Wal-Mart supermarket. For the third embodiment, the S1 and S3 links can be completed in the message server, and the listener can be established in the weather server to realize the S2 link.

Since the terminal where the sender and the receiver are located may be shut down, battery exhausted, etc., their stability is far less than that of the server, so the S1 and S3 links can be set in the message server. The listener in the S2 link is set at a position suitable for monitoring, that is, where the monitoring event occurs; if there are multiple positions to choose from, such as the monitoring time, try to set it on the server.

According to the above system, the steps of sending a condition message on the client can refer to the flowchart of the client shown in FIG. 22.

In step S2201 after the start, a message determined by the user is obtained, where the message includes the recipient and content of the message. The determination of the message recipient includes that when the user enters the dialogue interface with a friend, the friend is selected as the message recipient by default. As we will talk about later, to send messages in share fractions, we also need to select to receive friends through a list interface that displays friends, such as Figure 20. The message content determined by the user includes the message directly input by the user, such as the content in item 521 in Fig. 5, or the message sent by the user through the interface of items 341 to 344 in Fig. 5; messages preset according to conditions, such as Fig. 17 Of the 521 items in the content, of course the sending user can also modify the preset message. The content of the message may also include, for example, the shared content mentioned in the following embodiments.

Step S2202: Acquire the conditions set by the user. When responding to an operation that the user wants to set conditions, for example, the user clicks on item 345 in FIG. 4, the client terminal displays one or more conditions to the user, allowing the user to select and set parameters. Here, the one or more conditions that are displayed to the user are actually a promise to the user and a requirement for the displayed conditions: when the conditions selected by the user are met, it is possible to send the user's message to Recipient and display the possibility. In order to achieve this, the above-mentioned conditions can at least meet the realization of the above-mentioned core links S1 and S3. If the core link S2 cannot be realized temporarily, a message that the condition creation is unsuccessful can be sent to the receiving user, and the receiving user can adopt other communication methods or wait for the successful realization of the link S2. When the core link S2 is successfully implemented and the conditions are also met, the receiving user can receive the message.

The client can directly display its interface according to pre-determined and settable conditions. For example, the internal conditions that can be provided by the conditional message system itself, such as the time-related conditions shown in items 621 to 634 in Figure 6, can meet the above S1 to S3 links, so the conditions are used as a module of the client. Called directly by the client and displayed.

The client can also request the message server to obtain conditionable data stored in the server database, and after receiving the conditional data, display the conditional interface for the user to select. In this way, the conditions displayed by the terminal can also be changed according to the change of the settable condition data in the message server, which is more flexible. For example, the server stores the conditions of a certain shopping mall’s promotional activities during the discount season. Emily can choose to send the promotional information to Davis when there are mobile phone products instead of other products such as notebook promotional information. After the discount season is over, clear the promotional condition data in the server, and the outdated promotional conditions will not be displayed on the user client.

Therefore, this step may further include sending a request to the message server to obtain and display the settable condition information for the user to select, such as items 1221 and 1232 in FIG. 12, items 1621 and 1622 in FIG. 16, and so on. The displayed condition can realize the above-mentioned core links S1 and S3 within the message system, and at least provides the user with a most basic possibility to send a message according to the condition. And the conditions are displayed for the user to choose, so that the user can more intuitively view the conditions that can be set.

Receive the user's setting of the condition. The user's setting of the conditions includes selecting one or more conditions; setting the parameters of the conditions, directly confirming the default parameters, or directly confirming the conditions without parameters, etc. The conditions selected by the user for parameter setting or direct confirmation become user setting conditions.

Step S2203: Send an instruction to create the condition set by the user, or send the condition set by the user. For example, if the condition of a certain condition message is a specific location of the sender's client, the aforementioned core link S2 is located on the sender's client, so the core link S1 can also be set on the sender's client. At this time, the sender client directly issues an instruction to create the user setting condition. In other cases, for example, the above core link S1 is placed on the message server, or on the receiver's client, the message content and conditions can be sent to the message server, or first sent to the message server and then forwarded to the receiver Party client.

Step S2204: Obtain information about whether the user setting condition is successfully created, wherein in the case that the user setting condition is not successfully created, the information indicating that the condition creation is unsuccessful is displayed; in the case that the user setting condition is successfully created Next, when the conditions set by the user are satisfied, the message is displayed on the client of the recipient of the message.

For example, in the second embodiment, when the GPS of the receiver's client is not turned on and the condition creation is unsuccessful, a message indicating that the condition creation is unsuccessful is displayed on the sender's client, as shown in item 1422 in FIG. 14. If there is no such processing mechanism, that is, an error occurs when the listener is created to monitor the condition without corresponding information feedback, the sender Emily does not know whether the condition in the condition message she sent has been successfully monitored. There may be situations where the conditions are not successfully monitored but Emily believes that they are successfully monitored, so Emily’s message cannot be sent to Davis in time according to the conditions set by him, which delays the matter. With the above error feedback mechanism, when there is an error feedback, the sender user can have the opportunity to correct the error or use other communication methods to deliver the message; and in the absence of error feedback, the sender can also determine the sent The conditional message can be correctly sent to the recipient as expected.

Correspondingly, Figure 23 shows an implementation method applied to a message server.

Step S2301: Obtain the message and the set conditions determined by the user. That is, the condition message sent by the client in step S2203 in FIG. 22 is received. After receiving, the message server may first store the condition information and the corresponding message content.

In step S2302, an instruction to create a condition is issued. That is, according to the condition message received in the previous step, the aforementioned core link S1 is executed.

Step S2303: It is determined whether the user setting condition is successfully created. For example, the sending end, receiving end or other application server that executes the above core link S2 sends information about whether a listener is created and working normally to the message server, so that the message server determines whether the user setting condition is created success. Or when the aforementioned core link S2 is located on the message server, it is directly determined whether the user setting conditions are successfully created. In this step, it can also include checking for logic errors.

Step S2304: Send information about whether the user setting conditions are successfully created to the client. Wherein, in the case that the creation of the user setting condition is unsuccessful, the client displays the message that the creation is unsuccessful; in the case that the creation of the user setting condition is successful, when the user setting condition is satisfied, The message is displayed on the client of the recipient of the message.

Figure 24 shows the implementation flow chart of a specific conditional message system.

In the described embodiment, a table with settable conditions is added to the database of the message server, where each record has a settable condition, expressed as follows according to the java data structure, in which the keyword private is omitted, and the meaning of each member variable See note.

In the above definition, ConditionParamArray represents an array of parameters to which the condition belongs, where each array member represents a pointer to a specific parameter object, and the class to which the parameter object belongs may have a common base class, and the common base class may include parameter names And other shared information. The condition parameter array also includes information about how each parameter is combined, such as logical AND, logical OR, and so on.

The nIDConditionSource in the above definition represents the ID of the condition source. For example, when the value is 1, 2, 3, 4, it means that the trigger position of the condition is located at the sender client, receiver client, message server or other application server. The specific information of the condition source is stored in the strParamOfConditionSource variable. For example, when the value is "GPS", it means the GPS location is to be monitored; when the value is "http::\\www.weather.com", it means the location of the weather server to be monitored. These two variables are used together to determine the location of the condition.

In the database of the message server, a table of conditional messages set by the user is also added to store the conditional messages submitted by the user. Each record is represented as follows according to the java data structure:

The last three variables represent the information of a condition set by the user. Among them, nSelected_Conditiion_RecordID represents the ID number selected by the user that can set conditions, that is, the nID in the above Conditiion_Record. The array class SelecedParamArray is used to store the parameters of the above conditions selected or input by the user. For example, the parameters corresponding to the 534 conditions in Figure 13 are the contents of the 5341 items under it. Its internal structure can be similar to ConditionParamArray in Condition_Record. And the last bStatus variable represents the status of the condition, the default value is 0, which means that the condition is created unsuccessfully or fails after being created successfully, 1 means that the condition is created successfully, and 2 means that the condition has been met.

The bStatus, nSelected_Conditiion_RecordID and arraySelParam in the above Condition_Message definition realize one condition together, and can refer to realize multiple conditions.

For the specific implementation of each embodiment above, refer to FIG. 24. Among them, 24100 is the sender client, 24200 is the message server, and 24300 is the receiver client.

First, in response to user input, the client 24100 determines the settable conditions of the message (S24101), such as reading from the above-mentioned settable database in the server, and displays the interface of the conditions (S24102). Receiving a condition message determined by the user (S24103) includes not only the recipient, the sender, and the specific message content of the message, but also information about the conditions set by the user. Then send the condition message to the message server (S24104).

The message server 24200 receives the condition message (S24201), and first saves the condition message in the condition message table set by the user in the database (S24202). At this time, the record in the table corresponds to the default value of the bStatus data in the Condition_Message 0, that is, the condition has not been created successfully.

Then, an instruction to create a listener is issued (S24203). For example, firstly, search the settable condition table according to the nSelected_Conditiion_RecordID in the user set condition record to obtain the corresponding settable condition record. Then obtain nIDConditionSource and strParamOfConditionSource from the settable condition record, such as "2" and "GPS", respectively, indicating that the receiver's client should monitor GPS. After determining the trigger location of the condition, send an instruction to establish a listener to the location, such as the recipient client. The instruction may include condition message identification data idConditon_Message in Condition_Message, and data representing the condition itself, nSelected_Conditiion_RecordID, arraySelParam.

After the monitoring instruction is issued, information about whether the monitoring device is successfully established is also obtained (S24204). And send the information to the sender's client (S24205). The sender client 24100 receives the information (S24104), and displays information about whether the condition is successfully created (S24105). For example, when the establishment is unsuccessful, the client displays the 824 items in Figure 8 and the 1422 items in Figure 14 to the user; if the creation is successful, the above bStatus data must be set to 1, and then the sender client will send the condition creation Success information is displayed, such as 1024 items in Figure 10.

When the listener detects that the condition is met, it sends a monitoring signal to the server 24200. The signal may be in the form of a message, Http or Tcp request, etc., which includes the nSelected_Conditiion_RecordID data that identifies the condition and the idConditon_Message that identifies the condition message. data. After receiving the service request or message (S24206), the message server 24200 first determines whether the above-mentioned monitoring signal is received (S24207), for example, whether the signal contains a keyword indicating that this is a monitoring signal, etc. If not, perform general processing on the service request (S24210), and then return to the above step S24206; if yes, search the condition message table set by the user according to the idConditon_Message number of the condition message in the signal, and find all The message corresponding to the above condition (S24208). In the found records, the bStatus corresponding to the nSelected_Conditiion_RecordID condition is set to 2, that is, the condition is satisfied. If it is found that all the conditions have been met, then read idReceiver or strMessage respectively to get the message content and receiver. Then send the message (S24209), and finally return to step (S24206).

After the recipient client 24300 receives the message (S24301) sent in step S24209, it can display the message (S24302). In this way, the recipient user sees the sender's condition message.

In Fig. 24, in step S24202 of saving the condition message, the parameters of the conditions set by the user can also be checked logically. For example, the time set by Emily in the first embodiment is different from the time set by her manager. If there is a conflict, it returns a message that the listener cannot be established successfully, and directly executes steps S24204 and S24205.

FIG. 25 is a flowchart of a general method of the present disclosure.

Step S2501: Obtain a message determined by the user, where the message includes the recipient and content of the message.

Step S2502: Acquire the conditions set by the user.

Step S2503: According to the condition set by the user, an instruction to create the condition is issued.

Step S2504: Create the condition. For example, a listener is established for the condition. If the server of the third-party application establishes the listener according to the instructions of the previous step, the third-party server also needs to have corresponding functional modules.

Step S2505: Determine whether the creation of the user setting condition is successful, where: in the case that the creation of the user setting condition is unsuccessful, display the unsuccessful creation information on the user's client; and set the condition in the user In the case of a successful creation, when the user setting conditions are met, the message is displayed on the client of the recipient of the message.

In the above method, the following further extended methods can also be included. The extended method is also applicable to the method of the client shown in FIG. 22 or the method of the message server shown in FIG. 23, for example.

Further, the method further includes obtaining and displaying information about the invalidation of the condition when the successfully created condition fails when the user-set condition is successfully created.

Or further, on the premise that the condition is successfully created, the client also obtains and displays the information of the successful creation. This allows the sender to be more certain that the condition has been created successfully.

Or further, in the case that the creation of the user setting condition is unsuccessful, the information showing the unsuccessful creation of the condition includes an interface for sending a reminder message, and the interface for the reminder message is used to trigger the reception of the message The party sends information related to the message. The information may be, for example, item 1424 in FIG. 14 for reminding to correct errors; or, in another embodiment, it is directly the content of the message.

Or further, it also includes acquiring the settable conditions of the message and displaying the conditions.

Or further, the conditions include the internal conditions of the communication system using the method of the present disclosure or the external conditions of the system.

Or further, the reasons for the unsuccessful creation of the conditions include logic errors or errors in the external conditions of the communication system using the method of the present disclosure.

Or further, the trigger position of the user setting condition is located in any of the following positions: the terminal where the message sender client is located, the terminal where the message receiver client is located, the message server, or the third-party application server. Listeners can be established in these locations to monitor whether the conditions set by the user are triggered.

Through the above method, a reliable conditional message communication system can be realized, that is, when the user obtains the information that the condition setting is unsuccessful or invalid, they will know that even if the condition is met, the message corresponding to the condition will not be received ; When the user does not receive the above-mentioned unsuccessful or invalid information, they will know that the condition is in a state of being effectively monitored, and when the condition occurs, the message will be received. If there is no such feedback information, the user is not sure whether the message can be received when the condition actually occurs.

In the following embodiment, not only the directly sent message can be set with conditions, but the shared message can also be set with conditions.

The following is about the fourth embodiment.

Davis asked Emily to choose a favorite product as a Christmas present for her. Emily went to the Amazon website and chose the Apple phone on the web page shown in Figure 26. In the figure, item 2601 is the product name, item 2602 represents the price of US$628.4, item 2603 represents the icon shared to Facebook and Twitter, and item 2604 represents the icon shared to the conditional messaging application using the disclosed method. After clicking this icon, the QR code shown in Figure 27 2750 will pop up.

The two-dimensional code contains the web address of the webpage, and ordinary real-time sharing can be performed through the webpage. However, after scanning by the client using the method of the present disclosure, the client sends the web address to the message server and recognizes that it is an Amazon website. Generally, the sales page of Amazon.com has a code similar to the following to indicate the sales price of the product:

"<span id="priceblock_ourprice"class="a-size-mediuma-color-pricepriceBlockBuyingPriceString">$628.40</span>".

Therefore, the message server finds a field with "id" as "priceblock_ourprice" in the webpage file, and can read the price of the commodity as "$628.40" in it, and monitor it.

Therefore, when the message server recognizes that this is a commodity sales page that can monitor price changes, it sends relevant information to the sender's client, and Emily's client displays the interface 2800 in FIG. 28. In the figure, item 2811 indicates that this is a "Web Page Shere Setting" interface. Item 2821 displays "Content", and the input box of item 2822 is the URL of the web page shown in Figure 26 automatically filled in by the client.

The following 2831 items represent the recipient users of the sharing. Davis clicks on the 2832 item to the right of the 2831 item, and a user list selection interface as shown in Figure 20 will pop up. Emily returned after selecting the 2011 Davis item, showing the selected name in the 2,833 item.

If Emily does not tick item 2841, but directly clicks the item 2851 send button, then the shared instant message can be sent to Davis. However, Emily thought it was a bit expensive and wanted to wait for the price to drop before letting Davis buy it. At that time, I checked the 2841 "Condition" and filled in "570" after the 2842 "Price<=" (price is less than or equal to), which means that when the commodity drops to less than 570 yuan, the sending office State the news to Davis. At this time, the input box of item 2822 mentioned above automatically adds "This thing has been reduced in price below US$570" after the shared URL. But Emily deleted this sentence and added "I like this!" (I like this). Then press the 2851 item send button.

The client on Emily's mobile phone sends the above condition message to the message server. After the message server issues an instruction to establish a listener step in step S24203 in FIG. 24, it first accesses the web site to ensure that the web page is accessible. Then search for the above-mentioned "id=priceblock_ourprice" field in the file of the webpage to ensure that the price can be read; then determine whether the price is higher than the price set by the user, or whether the price set by the user is a negative value, etc. If a problem occurs in any of the steps described here, the message server will send to the sender client information that the creation of the user setting conditions is unsuccessful.

Thereafter, the message server adds a new monitoring thread, or adds a new task to another existing monitoring thread to monitor the price change. For example, in the monitoring thread, through a loop statement, every certain time, such as one minute, one hour, or one day, visit the URL of the webpage shown in Figure 26, after obtaining the webpage code of the webpage, look for the id as the above "priceblock_ourprice" The corresponding price. In this process, for example, due to resource constraints, the newly added monitoring thread fails to be created successfully, or the existing monitoring thread is cancelled or suspended, the message server will send a conditional creation unsuccessful to the sender client information. After the condition is successfully created, if the product is removed from the shelves, for example, the web page cannot be accessed or the "id=priceblock_ourprice" field cannot be searched, the message server sends the information that the created condition is invalid to The client can let the user know that the condition message has expired.

When Christmas comes, Amazon's website cuts prices, and the above event listener finds that the price has become US$567, which meets Emily's pre-set conditions. Then the message server sends a monitoring signal to itself, which only contains the information that the condition has been met. Through steps S24206 to S24209, S24301, and S24302 in FIG. 24, it is finally displayed on the terminal of Davis, as shown in FIG. 29. Among them, the 2921 message shows the URL and the aforementioned "I like this!" input by Emily (I like this).

Regarding the fifth embodiment below, another way is adopted to achieve the effects of the fourth embodiment.

In FIG. 26, when Emily clicks on item 2604 to share using the method of the present disclosure, a dialog box shown in 2700 in FIG. 27 pops up. Among them, the title of the 2701 display window is "Condition", and the following item 2711 represents the single option of "direct sharing", that is, common and unconditional sharing. Item 2712 indicates that only when the price of the commodity is less than or equal to the price entered by the user in Item 2713, the sharing will be performed. Emily single-select 2712 item, and enter "570" in the following 2713 items, and finally click the 2714 item "OK" button to confirm. At this time, a two-dimensional code is also popped up. Different from the sixth embodiment, this two-dimensional code not only contains website information but also condition information.

By scanning the code, Emily’s client obtains the above information and transmits the above information to the message server. The message server checks the above-mentioned information, such as whether the website is an authenticated website or the like. After checking that there is no problem, the client displays an interface 2800 such as that shown in Figure 28, and the interface automatically displays the data filled in by Emily in Figure 27, such as the 2842 item price "570". Emily also selects Davis as the receiving user by clicking on item 2832. When the server receives the condition message sent by the Emily client, it goes through steps S24201 and S24202 in Figure 24 and in step S24203, because it detects that the condition is related to the pre-authenticated Amazon website, it sends the establishment to the Amazon website. The request of the relevant listener.

Because a set of agreements acceptable to both parties have been established after pre-authentication, the server of the Amazon website can recognize the request and establish a corresponding listener. At this time, the server of the Amazon website does not use the method of checking the price every other time used in the fourth embodiment, but whenever the price modification function is called to modify the price of the product, it checks whether the URL of the product whose price is modified is Figure 26 shows the URL of the Apple mobile phone. The server of the Amazon website returns information about whether the listener is successfully set to the message server, and forwards it to the sender's client, and displays information about whether the condition is successfully created on it. After the listener on the server of the Amazon website is successfully set, when the price of the mobile phone is lower than the US$570 set by Emily, a listener signal is sent to the message server. In this way, when Christmas is coming, after the price of the mobile phone is lowered, the monitoring signal is triggered. According to steps S24206-24209, 24301, 24302 in Figure 24, Davis sees Emily as shown in item 2921 in Figure 29. News.

If during the monitoring process, the mobile phone is sold out without a price reduction, when the Amazon website server performs the delisting operation, the delisting information will be sent to the message server at the same time, and the message server will send the message server to the sender customer. The terminal sends a message that the monitoring is over, and finally displays on the client terminal that the product is out of stock, that is, the message that the condition is invalid after being successfully created.

Note that on the Amazon website alone, there are hundreds of millions of items that can be set as conditions. All of them are put into the message server and can be set in the condition database, and displayed on the client for users to choose. But come. Therefore, it can be seen from the fourth and fifth embodiments that the way of monitoring the shared website has great convenience and flexibility. The fourth embodiment adopts the establishment of a query listener on the message server to monitor specific fields in a specific URL, and it is possible to implement sending and receiving conditional messages without changing the existing application server, such as the server of the Amazon website. The fifth implementation enables Amazon.com to receive the request of the message server to establish a listener and return the listener message. The advantage is that the monitoring task is placed at the location of the event, that is, the Amazon website server, which also reduces the burden of the message server, and the overall configuration is more reasonable.

In another embodiment, the interface shown in FIG. 26 is an interface on a mobile terminal such as a tablet computer or a mobile phone. After clicking on 2604 items, the interface shown in Figure 28 will pop up directly for the user to set conditions. The process used can be the same as in the fourth or fifth embodiment.

Based on the above methods, this article also discloses a terminal device, which is characterized by comprising a memory and a processor, wherein the memory is used to store executable instructions; the processor is used to execute the instructions to implement According to Figure 22, the method of communication and its extended method. In addition, this article also discloses a server device, which is characterized by comprising a memory for storing computer program instructions for executing the communication method and its expansion method described in FIG. 22 for downloading.

This document also discloses a server device, which is characterized by comprising a memory and a processor, wherein the memory is used to store executable instructions; the processor is used to execute the instructions to implement the communication according to FIG. 23 Method and its extension method.

This article also discloses a communication system, which is characterized in that it includes at least a client and a server, and executes the communication method and the extended method described in FIG. 25. Optionally, the system further includes a third-party application server, such as the weather server in the third embodiment of this document.

The examples of well-known brands cited in the present disclosure are only to illustrate the applicable scenarios and the progress brought about by the technical solutions of the present disclosure, and do not actually occur.

As for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and for related parts, please refer to the part of the description of the method embodiment. The device embodiments described above are only illustrative.

The specific embodiments described above further describe the purpose, technical solutions and beneficial effects of the present disclosure in further detail. It should be understood that the above are only specific embodiments of the present disclosure and are not intended to limit the present disclosure. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present disclosure shall be included in the protection scope of the present disclosure.

Claims (28)

1. A method of communication, applied to the client, characterized in that:

   Acquiring a message determined by the user, where the message includes the recipient and content of the message;

   Get the conditions set by the user;

   Issue an instruction to create the condition set by the user, or send the condition set by the user;

   Obtain the information about whether the user setting condition is successfully created, where:

   In the case that the creation of the user setting condition is unsuccessful, the message indicating that the creation of the condition is unsuccessful is displayed; in the case that the creation of the user setting condition is successful, when the user setting condition is satisfied, the message is received The client of the party displays the message.
2. 4. The communication method according to claim 1, further comprising: in the case that the user-set condition is successfully created, when the successfully created condition fails, acquiring and displaying information about the condition failure.
3. 4. The communication method according to claim 1, wherein when the user setting condition is successfully created, the information indicating that the condition is successfully created is also displayed.
4. The communication method according to claim 1, characterized in that, in the case that the creation of the condition set by the user is unsuccessful, the information showing that the creation of the condition is unsuccessful includes an interface for sending a reminder message, the reminder message The interface is used to trigger the sending of information related to the message determined by the user to the recipient of the message.
5. The method of communication according to claim 1, further comprising receiving a settable condition of the message and displaying the condition.
6. The communication method according to claim 1, wherein the conditions include internal conditions of the communication system using the method or external conditions of the communication system.
7. The communication method according to claim 1, wherein the reason for the unsuccessful creation of the condition includes a logic error or an error of an external condition of the communication system using the method.
8. The communication method according to claim 1, wherein the trigger position of the user setting condition is located at any of the following positions: the terminal where the message sender client is located, the terminal where the message receiver client is located, the message server, or a third party application server.
9. The communication method according to claim 1, wherein the content of the message determined by the user includes content shared by the user.
10. A terminal device, characterized by comprising a memory and a processor, wherein the memory is used to store executable instructions; the processor is used to execute the instructions to implement the instructions according to any one of claims 1 to 9 State the method of communication.
11. A server device characterized by comprising a memory for storing computer program instructions for executing the communication method of any one of claims 1 to 9 for downloading.
12. A method of communication, applied to a server, characterized in that:

    Obtain a user-determined message sent by the client and conditions set by the user, where the message includes the recipient and content of the message;

    Issue an instruction to create the condition according to the condition set by the user;

    Determine whether the user setting condition is successfully created;

    Sending information about whether the user setting conditions are successfully created to the client, where:

    In the case that the creation of the user setting conditions is unsuccessful, the client displays the information that the creation is unsuccessful; in the case that the creation of the user setting conditions is successful, when the user setting conditions are met, the The client of the recipient of the message displays the message.
13. The communication method according to claim 12, further comprising: in the case that the user setting condition is successfully created, after obtaining the invalidation information of the successfully created condition, sending the condition invalidation information, wherein, The condition invalidation information is acquired and displayed by the client.
14. The communication method according to claim 12, further comprising sending settable condition information, wherein the settable condition information is acquired and displayed by the client.
15. The communication method according to claim 12, wherein the conditions include internal conditions of the communication system using the method or external conditions of the communication system.
16. The communication method according to claim 12, wherein the reason for the unsuccessful creation of the condition includes a logic error or an error of an external condition of the communication system using the method.
17. The communication method according to claim 12, wherein the trigger position of the user setting condition is located at any of the following positions: the terminal where the message sender client is located, the terminal where the message receiver client is located, the message server, or a third party application server.
18. The communication method according to claim 12, wherein the content of the message determined by the user includes content shared by the user.
19. A server device, characterized by comprising a memory and a processor, wherein the memory is used to store executable instructions; the processor is used to execute the instructions to implement any one of claims 12 to 18 State the method of communication.
20. A method of communication, characterized in that,

    Acquiring a message determined by the user, where the message includes the recipient and content of the message;

    Get the conditions set by the user;

    Issue an instruction to create the condition according to the condition set by the user;

    Create the conditions;

    It is determined whether the creation of the user setting condition is successful, wherein: in the case that the creation of the user setting condition is unsuccessful, the message that the creation is unsuccessful is displayed on the client of the user; when the creation of the user setting condition is successful In this case, when the conditions set by the user are satisfied, the message is displayed on the client of the recipient of the message.
21. The method of communication according to claim 20, further comprising: in the case that the user setting condition is successfully created, when the invalidation information of the successfully created condition is obtained, the client of the user The terminal displays the information that the condition has failed.
22. 22. The communication method according to claim 20, wherein, in the case that the user setting condition is successfully created, a message indicating that the condition is created successfully is displayed on the client of the user.
23. The method of communication according to claim 20, further comprising obtaining settable conditions of the message and displaying the conditions.
24. The communication method according to claim 20, wherein the conditions include internal conditions of the communication system using the method or external conditions of the communication system.
25. The communication method according to claim 21, wherein the reason for the unsuccessful creation of the condition includes a logic error or an error of an external condition of the communication system using the method.
26. The communication method according to claim 20, wherein the trigger position of the user setting condition is located at any of the following positions: the terminal where the message sender client is located, the terminal where the message receiver client is located, the message server, or a third party application server.
27. The communication method according to claim 20, wherein the content of the message determined by the user includes content shared by the user.
28. A communication system, characterized in that it includes at least a client and a server, and implements the communication method described in claims 20-27.

Images