Reminder event processing method, device and electronic device

Abstract

The present application discloses a method, device and electronic device for processing a reminder event, which belongs to the field of communication technology. The method includes: when a reminder event reaches a reminder time, determining whether a game interface of a game application is displayed, the game interface includes a local game object; when a game interface of a game application is displayed, determining a game state corresponding to the game interface; when the game state is in a target game state, maintaining the display of the game interface and performing a target operation, the target operation includes at least one of the following: displaying a reminder message of the reminder event in a message display area of ​​the game interface, and outputting the reminder message through the target game object voice.

Description

Technical Field

[0001] The present application belongs to the field of communication technology, and specifically relates to a reminder event processing method, device and electronic device. Background Art

[0002] With the development of communication technology, electronic devices have more and more functions, for example, electronic devices have an alarm clock function.

[0003] At present, after setting the alarm in the alarm application of the electronic device, the user may play games through the electronic device. In this case, when the alarm reaches the reminder time, the electronic device can usually remind the user in the form of a top pop-up box.

[0004] However, this traditional alarm reminder method makes the interaction between the electronic device and the user monotonous. The user can close the pop-up box and continue the game by simply swiping up, which may cause the user to forget what needs to be done. Summary of the invention

[0005] The purpose of the embodiments of the present application is to provide a reminder event processing method, device and electronic device, which can solve the problem that the traditional alarm reminder method makes the interaction between the electronic device and the user single.

[0006] In a first aspect, an embodiment of the present application provides a reminder event processing method, the method comprising: when a reminder event reaches a reminder time, determining whether a game interface of a game application is displayed, the game interface including a local game object; when a game interface of a game application is displayed, determining a game state corresponding to the game interface; when the game state is in a target game state, keeping the above-mentioned game interface displayed, and performing a target operation, the target operation comprising at least one of the following: displaying a prompt message of the reminder event in a message display area of ​​the game interface, and outputting the prompt message through voice of the target game object.

[0007] In a second aspect, an embodiment of the present application provides a reminder event processing device, which includes: a determination module, a display module and an execution module; the determination module is used to determine whether a game interface of a game application is displayed when the reminder event reaches the reminder time, and the game interface includes a local game object; and when the game interface of the game application is displayed, determine the game state corresponding to the game interface; the display module is used to keep displaying the above-mentioned game interface when the determination module determines that the game state is in the target game state; the execution module is used to perform a target operation when the determination module determines that the game state is in the target game state, and the target operation includes at least one of the following: displaying a prompt message of the reminder event in the message display area of ​​the game interface, and outputting the prompt message through the voice of the target game object.

[0008] In a third aspect, an embodiment of the present application provides an electronic device, which includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the method described in the first aspect.

[0009] In a fourth aspect, an embodiment of the present application provides a readable storage medium, on which a program or instruction is stored, and when the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented.

[0010] In a fifth aspect, an embodiment of the present application provides a chip, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the method described in the first aspect.

[0011] In an embodiment of the present application, when the reminder event reaches the reminder time, the reminder event processing device can determine whether the game interface of the game application is displayed. Then, the reminder event processing device can determine the game state corresponding to the game interface when the game interface of the game application is displayed. Finally, the reminder event processing device can keep displaying the game interface and perform the target operation when the game state is in the target game state. Among them, the game interface includes a local game object; the target operation includes at least one of the following: displaying a reminder message of the reminder event in the message display area of ​​the game interface, and outputting the reminder message through the target game object voice. Through the above scheme, compared with the alarm clock reminder method in the related art that makes the interaction between the electronic device and the user single, which may cause the user to forget what needs to be done, the reminder event processing device in the present application can combine the game with the reminder event. When the reminder event reaches the reminder time, if it is determined that the reminder event processing device displays the game interface of the game application, and the game state of the game interface is in the target game state, the reminder event processing device can keep displaying the game interface, and display the reminder message of the reminder event in the message display area of ​​the game interface, or output the reminder message through the target game object voice, so as to achieve the purpose of prompting the user. In this way, not only the fun of the user's gaming experience is improved, but also the user can be effectively reminded without affecting the user's gaming, and the interaction between the user and the electronic device is enriched. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Figure 1 A flowchart of a reminder event processing method provided in an embodiment of the present application;

[0013] Figure 2 One of the interface schematic diagrams applied to a reminder event processing method provided in an embodiment of the present application;

[0014] Figure 3 A second schematic diagram of an interface used in a method for processing a reminder event provided in an embodiment of the present application;

[0015] Figure 4 A third schematic diagram of an interface used in a method for processing a reminder event provided in an embodiment of the present application;

[0016] Figure 5 A fourth schematic diagram of an interface used in a method for processing a reminder event provided in an embodiment of the present application;

[0017] Figure 6 A schematic diagram of the structure of a reminder event processing device provided in an embodiment of the present application;

[0018] Figure 7 One of the structural schematic diagrams of an electronic device provided in an embodiment of the present application;

[0019] Figure 8 The second structural diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0020] The following will be combined with the drawings in the embodiments of the present application to clearly describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. All other embodiments obtained by ordinary technicians in this field based on the embodiments in the present application belong to the scope of protection of this application.

[0021] The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here. And the objects distinguished by "first", "second", etc. are usually a class, and the number of objects is not limited. For example, the first object can be one or more. In addition, "and / or" in the specification and claims represents at least one of the connected objects, and the character " / " generally represents that the objects associated before and after are in an "or" relationship.

[0022] The reminder event processing method provided by the embodiment of the present application is described in detail below through specific embodiments and application scenarios in conjunction with the accompanying drawings.

[0023] Figure 1 A flowchart of a reminder event processing method provided in an embodiment of the present application includes steps 201 to 203:

[0024] Step 201: When a reminder event reaches a reminder time, the reminder event processing device determines whether the reminder event processing device displays a game interface of a game application.

[0025] Wherein, the above-mentioned game interface includes the local game object.

[0026] In the embodiment of the present application, the above-mentioned reminder event can be an alarm clock or a schedule, which is not limited in the embodiment of the present application. For example, the schedule can be set through a calendar application.

[0027] In the embodiment of the present application, the above-mentioned reminder time may include at least one of the following: year, month, day, hour, minute, and second.

[0028] Optionally, the above-mentioned game interface may further include at least one of the following: at least one non-player game object, at least one opposite-end game object, which is not limited in this embodiment of the present application.

[0029] In the embodiment of the present application, the game corresponding to the above-mentioned game application can be a strategy game, a chess and card game, or any possible game, which is not limited in the embodiment of the present application. For example, the game corresponding to the above-mentioned game application can be a multiplayer online battle arena game (MOBA), which can also be called an action real-time strategy game.

[0030] It should be noted that, after the user triggers the reminder event processing device to set a reminder event, the reminder event processing device can synchronize the reminder event to the game application.

[0031] Step 202: When displaying a game interface of a game application, the reminder event processing device determines a game state corresponding to the game interface.

[0032] In the embodiment of the present application, the game state may include at least one state. For example, the game state may be an idle game state (such as the first game state described below) or an active game state (such as the second game state described below), which is not limited in the embodiment of the present application.

[0033] Optionally, in the embodiment of the present application, the determining of the game state corresponding to the game interface in the above step 202 may specifically include the following steps: the reminder event processing device may determine the game state corresponding to the above game interface according to the estimated death frequency corresponding to the game object in the game interface. The game object in the game interface includes at least one of the following: a local game object, at least one non-player game object, and at least one opposite-end game object.

[0034] Exemplarily, the reminder event processing device can determine that the game state is a first game state when the estimated death frequency is less than a first preset threshold value; and determine that the game state is a second game state when the estimated death frequency is greater than or equal to the first preset threshold value.

[0035] For example, the reminder event processing device can be divided into two scenes according to the intensity of the battle around the local game object during game operation, namely scene A and scene B. Among them, scene A means that the intensity of the battle around the local game object is mild, and the local game object may be wandering around or fighting soldiers, etc. At this time, game characters generally do not die frequently around the local game object, and at this time, scene A can be determined as an idle game state; scene B means that the intensity of the battle around the local game object is intense, and the local game object may be in a group battle or fighting a difficult monster (boss), etc. At this time, game characters may die frequently around the local game object, and at this time, scene B can be determined as an active game state.

[0036] It should be noted that the reminder event processing device may not perform any operation when the game interface of the game application is not displayed.

[0037] It should be noted that, when the game interface of the game application is displayed, the reminder event processing device can parse the reminder event whose reminder time is later than the current time.

[0038] Step 203: When the game state is in the target game state, the event processing device is reminded to keep displaying the game interface and execute the target operation.

[0039] Among them, the above-mentioned target operation includes at least one of the following: displaying a prompt message of the above-mentioned reminder event in the message display area of ​​the above-mentioned game interface, and outputting the prompt message through the voice of the target game object.

[0040] In the embodiment of the present application, the above-mentioned target game state can be the above-mentioned idle game state, or it can be the above-mentioned active game state, and the embodiment of the present application is not limited to this.

[0041] In the embodiment of the present application, the above-mentioned prompt message can be a text message or a voice message, which is not limited in the embodiment of the present application. It should be noted that when the prompt message is a text message, the reminder event processing device can convert the text message into a voice message; when the prompt message is a voice message, the reminder event processing device can convert the voice message into a text message.

[0042] In the embodiment of the present application, the above-mentioned target game object can be a local game object, a non-player game object, or an opposite-end game object. It can be specifically set according to actual needs, and the embodiment of the present application does not limit this.

[0043] It should be noted that the above-mentioned keeping displaying the above-mentioned game interface means that the game interface remains stationary, the game is still in progress, and the game interface still updates the game screen in real time.

[0044] Optionally, in an embodiment of the present application, when a reminder event reaches a reminder time, the reminder event processing device may remind the user in at least two possible implementation methods without affecting the user's game.

[0045] In the first possible implementation:

[0046] Exemplarily, when the target game state is the first game state, the step 203 may specifically include the following steps A1 to A3:

[0047] Step A1: When the game state is in the first game state, the reminder event processing device displays N non-player game objects in the game interface.

[0048] Among them, a non-player game object is used to trigger an operation for the above reminder event, and N is a positive integer.

[0049] Exemplarily, the N non-player game objects mentioned above may be original non-player game objects or newly added non-player game objects, which is not limited in this embodiment of the present application.

[0050] In one example, the original non-player game objects mentioned above refer to non-player game objects displayed in the game interface, and the newly added non-player game objects refer to non-player game objects that are not displayed in the game interface but exist in the game application.

[0051] Step A2: The reminder event processing device receives a first input from a user to a first non-player game object among the N non-player game objects.

[0052] Exemplarily, the first input may be: a user's click input on the first non-player game object, or a user's click input on the first control, or a voice command input by the user, or a specific gesture input by the user, which may be determined according to actual usage requirements, and the present application embodiment does not limit this. The first control may be an existing control or a newly added control, and the present application embodiment does not limit this.

[0053] The specific gesture in the embodiment of the present application can be any one of a single-click gesture, a sliding gesture, a drag gesture, a pressure recognition gesture, a long press gesture, an area change gesture, a double-press gesture, and a double-click gesture; the click input in the embodiment of the present application can be a single-click input, a double-click input, or any number of click inputs, etc., and can also be a long press input or a short press input.

[0054] Exemplarily, the first non-player game object may be one or more, which is not limited in this embodiment of the present application.

[0055] Step A3: In response to the first input, the event processing device is reminded to keep displaying the game interface and execute the target operation.

[0056] Among them, the above-mentioned target game object is the above-mentioned first non-player game object.

[0057] For example, when a user sets an alarm 1 on his mobile phone and is playing a MOBA game. Figure 2 As shown, the mobile phone displays a game interface 31 of a MOBA game application, and the game interface 31 displays a local player character 32 (i.e., the local game object mentioned above) and a non-player character (NPC). The NPC is NPC1. When the alarm 1 reaches the reminder time, the mobile phone detects that the mobile phone displays the game interface 31, and then the mobile phone can detect the game status of the game interface 31. When the mobile phone detects that the local player character 32 is wandering around, as shown in FIG. Figure 3 As shown, the mobile phone can display the text "Reminder" above NPC1. If the user wants to know the text content in the alarm clock 1, the user can aim at the NPC1 and click the "Attack" button (i.e., the first input mentioned above), that is, hit the NPC1. At this time, the mobile phone can keep displaying the game interface 31, and the text content in the alarm clock 1 can be broadcasted by NPC1 voice.

[0058] Optionally, in the embodiment of the present application, after N non-player game objects are displayed in the game interface in the above step A1, the method may further include the following steps A4 and A5:

[0059] Step A4: the reminder event processing device receives a second input from the user to a second non-player game object among the N non-player game objects.

[0060] Exemplarily, the second input may be: a click input of a second non-player game object by a user, or a click input of a second control by a user, or a voice command input by a user, or a specific gesture input by a user, which may be determined according to actual use requirements, and the present application embodiment does not limit this. The second control may be an existing control or a newly added control, and the present application embodiment does not limit this.

[0061] Exemplarily, the second non-player game object may be one or more, which is not limited in the embodiment of the present application.

[0062] Step A5: In response to the second input, the event processing device is prompted to perform the first operation.

[0063] Among them, the above-mentioned first operation includes any of the following items: keeping the above-mentioned game interface displayed and postponing the reminder time of the above-mentioned prompt event; instructing the game system of the above-mentioned game application to take over the local game object and display the prompt interface of the prompt event; instructing the game system to hang up the local game object and display the prompt interface.

[0064] For example, when the mobile phone detects that the local player character 32 is wandering around, Figure 3 As shown, the mobile phone can also display 3 additional NPCs, namely NPC2, NPC3 and NPC4. The text "Postpone" is displayed above NPC2, the text "Take Over" is displayed above NPC3, and the text "Hang Up" is displayed above NPC4. When the user wants to postpone the alarm 1, the user can aim at NPC2 and click the "Attack" button (i.e. the second input mentioned above), that is, hit the NPC2. At this time, the mobile phone can keep displaying the game interface 31 and postpone the next reminder time of the alarm 1 by 5 minutes. When the user wants the game system to take over the local player character, the user can aim at NPC3 and click the "Attack" button (i.e. the second input mentioned above), that is, hit the NPC3. At this time, the mobile phone can instruct the game system of the MOBA game application to take over the local player character 32 and display the prompt interface of the alarm 1 in full screen. When the user wants the local player character to hang up, the user can aim at NPC4 and click the "Attack" button (i.e. the second input mentioned above), that is, hit the NPC4. At this time, the mobile phone can instruct the game system to hang up the local player character 32 and display the prompt interface of the alarm 1 in full screen.

[0065] In this way, the user can quickly implement different operations on the alarm clock through the multiple non-player game objects displayed by the reminder event processing device, thus enriching the interaction between the user and the reminder event processing device.

[0066] Optionally, in the embodiment of the present application, when the first operation is to keep displaying the game interface and postpone the reminder time of the prompt event, after the above step A4, the method further includes the following step A6:

[0067] Step A6: In response to the second input, the reminder event processing device cancels the display of all or part of the N non-player game objects in the game interface.

[0068] Exemplarily, if the above-mentioned N non-player game objects are all non-player game objects not displayed in the game interface, the reminder event processing device can cancel the display of the N non-player game objects in the game interface; if some of the above-mentioned N non-player game objects are non-player game objects not displayed in the game interface, the reminder event processing device can cancel the display of some non-player game objects in the game interface.

[0069] It should be noted that there is no obvious order for the reminder event processing device to execute the above step A6 and the above step A5. For example, the reminder event processing device may execute the above step A5 before executing the above step A6, or after executing the above step A6, or at the same time as executing the above step A6, and the present application embodiment does not limit this.

[0070] For example, combining Figure 3 , when the user aims at NPC2 and clicks the "attack" button (i.e. the second input above), Figure 2 As shown, the mobile phone can keep displaying the game interface 31 and cancel the display of NPC2, NPC3 and NPC4 in the game interface 31.

[0071] In the second possible implementation:

[0072] Exemplarily, when the target game state is the second game state, the step 203 may specifically include the following steps B1 and B2:

[0073] Step B1: When the game state is in the second game state, the reminder event processing device determines whether at least one game object among the at least one opposite-end game object is alive.

[0074] It should be noted that the at least one opposite-end game object is a game object corresponding to other users.

[0075] Exemplarily, the reminder event processing device may determine whether the at least one opposite-end game object is alive by reading data in the game application program.

[0076] Step B2: The reminder event processing device keeps displaying the game interface and executes the target operation when at least one of the game objects is not alive.

[0077] For example, combining Figure 2 , the game interface 31 also displays two opposite-end player characters, namely the teammate player character and the enemy player character of the local player character 32. When the alarm 1 reaches the reminder time, the mobile phone detects that the mobile phone displays the game interface 31, and then the mobile phone can detect the game status of the game interface 31. When the mobile phone detects that the local player character 32 is in a team battle, if the mobile phone determines that the teammate player or the enemy player character is dead, such as Figure 4 As shown, the mobile phone can continue to display the game interface 31, and display the text content in the alarm clock 1 in the message display area above the game interface 31, and broadcast the text content through the local player character 32 voice.

[0078] Optionally, in the embodiment of the present application, the method may further include the following steps B3 to B6:

[0079] Step B3: The reminder event processing device determines whether the local game object is alive when the above game state is in the second game state.

[0080] Exemplarily, the reminder event processing device can determine whether the local game object is alive by reading data in the game application.

[0081] In one example, the reminder event processing device may execute the above-mentioned step B3 after the above-mentioned step B2.

[0082] Step B4: When the local game object is not alive, the reminder event processing device displays M logos in the above game interface.

[0083] Wherein, an identifier is used to trigger an operation for the above reminder event, and M is a positive integer.

[0084] Exemplarily, the logo in the embodiments of the present application is text, symbol, image, etc. used to indicate information, and controls or other containers can be used as carriers for displaying information, including but not limited to text logos, symbol logos, and image logos.

[0085] Step B5: The reminder event processing device receives the user's third input of the target identifier among the above M identifiers.

[0086] Exemplarily, the third input mentioned above can be: a click input of the target logo by the user, or a voice command input by the user, or a specific gesture input by the user. The specific one can be determined according to actual usage requirements, and the embodiment of the present application is not limited to this.

[0087] Step B6: In response to the third input, the event processing device is prompted to perform a second operation.

[0088] Among them, the above-mentioned second operation includes any one of the following: keeping the above-mentioned game interface displayed and postponing the reminder time of the above-mentioned prompt event; instructing the game system of the above-mentioned game application to take over the local game object and display the prompt interface of the prompt event; instructing the game system to hang up the local game object and display the prompt interface.

[0089] For example, combining Figure 2 , when the mobile phone detects that the local player character 32 is in a group battle, the mobile phone can detect whether the local player character 32 is alive. In the case where the mobile phone determines that the local player character 32 is dead, such as Figure 5 As shown, the mobile phone can display three options in the game interface 31, namely, the "Postpone" option 41, the "Take Over" option 42, and the "Hang Up" option 43. When the user wants to postpone the alarm 1, the user can click the "Postpone" option 41 (i.e., the third input mentioned above). At this time, the mobile phone can keep displaying the game interface 31 and postpone the next reminder time of the alarm 1 by 10 minutes. When the user wants the game system to take over the local player character, the user can click the "Take Over" option 42 (i.e., the third input mentioned above). At this time, the mobile phone can instruct the game system of the MOBA game application to take over the local player character 32 and display the prompt interface of the alarm 1 in full screen. When the user wants the local player character to hang up, the user can click the "Hang Up" option 43 (i.e., the third input mentioned above). At this time, the mobile phone can instruct the game system to hang up the local player character 32 and display the prompt interface of the alarm 1 in full screen.

[0090] In this way, the reminder event processing device can remind the user in different ways under different game states. This not only allows the user to receive effective reminders without affecting the user's game, but also enriches the interaction between the user and the reminder event processing device.

[0091] Optionally, in the embodiment of the present application, when the game application does not include a resurrection timer, after the above step B3, the method may further include the following steps B7 and B8:

[0092] Step B7: When the local game object is not alive, the reminder event processing device adds a resurrection timer in the game application and displays the timing time of the resurrection timer in the game interface.

[0093] Exemplarily, the above-mentioned game application does not include a resurrection timer, which means that the local game object will be resurrected immediately after death, so there is no need for a resurrection timer.

[0094] Exemplarily, the above-mentioned resurrection timer can be a count-up timer or a count-down timer, which is not limited in the embodiment of the present application.

[0095] Step B8: When the above timing time satisfies the first condition, the reminder event processing device instructs the game system to revive the local game object.

[0096] Exemplarily, the first condition mentioned above may be that the timing time reaches a preset time, or that the timing time is greater than or equal to a second preset threshold, which is not limited in the embodiment of the present application.

[0097] For example, when the mobile phone determines that the local player character 32 is dead, the mobile phone can add a resurrection timer in the game application, combined with Figure 5 The top of the game interface 31 also displays the countdown time of the resurrection timer of 20 seconds. When the countdown time reaches 0 seconds, the mobile phone can instruct the game system to resurrect the local game object. In this way, the user can be provided with time to operate the alarm clock.

[0098] In the reminder event processing method provided by the embodiment of the present application, the reminder event processing device can determine whether the game interface of the game application is displayed when the reminder event reaches the reminder time. Then, the reminder event processing device can determine the game state corresponding to the game interface when the game interface of the game application is displayed. Finally, the reminder event processing device can keep displaying the game interface and perform the target operation when the game state is in the target game state. Among them, the game interface includes a local game object; the target operation includes at least one of the following: displaying a reminder message of the reminder event in the message display area of ​​the game interface, and outputting the reminder message through the target game object voice. Through the above scheme, compared with the alarm clock reminder method in the related art, which makes the interaction between the electronic device and the user single, and may cause the user to forget what needs to be done, the reminder event processing device in the present application can combine the game with the reminder event. When the reminder event reaches the reminder time, if it is determined that the electronic device displays the game interface of the game application, and the game state of the game interface is in the target game state, the reminder event processing device can keep displaying the game interface, and display the reminder message of the reminder event in the message display area of ​​the game interface, or output the reminder message through the target game object voice, so as to achieve the purpose of prompting the user. In this way, not only the fun of the user's gaming experience is improved, but also the user can be effectively reminded without affecting the user's gaming, and the interaction between the user and the electronic device is enriched.

[0099] It should be noted that the reminder event processing method provided in the embodiment of the present application can be executed by a reminder event processing device, or a control module in the reminder event processing device for executing the reminder event processing method. In the embodiment of the present application, the reminder event processing device provided in the embodiment of the present application is illustrated by taking the reminder event processing device executing the reminder event processing method as an example.

[0100] Figure 6 A possible structural diagram of a reminder event processing device provided in an embodiment of the present application is as follows: Figure 6 As shown, the reminder event processing device 500 includes: a determination module 501, a display module 502 and an execution module 503, wherein: the determination module 501 is used to determine whether a game interface of a game application is displayed when the reminder event reaches the reminder time, and the game interface includes a local game object; and when the game interface of the game application is displayed, determine the game state corresponding to the game interface; the display module 502 is used to keep displaying the game interface when the determination module 501 determines that the game state is in the target game state; the execution module 503 is used to perform a target operation when the determination module 501 determines that the game state is in the target game state, and the target operation includes at least one of the following: displaying a prompt message of the reminder event in the message display area of ​​the game interface, and outputting the prompt message through the voice of the target game object.

[0101] Optionally, the game interface includes at least one of the following: at least one non-player game object, at least one opponent game object; a determination module 501, specifically used to determine the game state corresponding to the game interface according to the estimated death frequency corresponding to the game object in the game interface.

[0102] Alternatively, if Figure 6 As shown, the reminder event processing device 500 also includes: a receiving module 504; the above-mentioned target game state is the first game state; the display module 502 is also used to display N non-player game objects in the game interface when the determination module 501 determines that the game state is in the first game state, and one non-player game object is used to trigger an operation for the reminder event, N is a positive integer; the receiving module 504 is used to receive a first input from a user to a first non-player game object among the above-mentioned N non-player game objects; the display module 502 is specifically used to keep displaying the above-mentioned game interface in response to the first input received by the receiving module 504; the execution module 503 is specifically used to execute the target operation in response to the first input received by the receiving module 504; wherein the above-mentioned target game object is the first non-player game object.

[0103] Optionally, the receiving module 504 is further used to receive a second input from a user for a second non-player game object among the above-mentioned N non-player game objects; the execution module 503 is further used to perform a first operation in response to the second input received by the receiving module 504, and the first operation includes any one of the following: keeping the above-mentioned game interface displayed and postponing the reminder time of the above-mentioned prompt event; instructing the game system of the game application to take over the local game object and display the prompt interface of the prompt event; instructing the game system to hang up the local game object and display the prompt interface.

[0104] Optionally, the first operation is to keep displaying the game interface and postpone the reminder time of the prompt event; the display module 502 is also used to cancel the display of all or part of the N non-player game objects in the game interface in response to the second input received by the receiving module 504.

[0105] Optionally, the target game state is the second game state; the determination module 501 is further used to determine whether at least one game object among at least one opposite game object is alive when the game state is in the second game state; the display module 502 is specifically used to keep displaying the game interface when the determination module 501 determines that at least one game object is not alive; the execution module 603 is specifically used to execute the target operation when the determination module 501 determines that at least one game object is not alive.

[0106] Alternatively, if Figure 6 As shown, the reminder event processing device 500 also includes: a receiving module 504; a determination module 501, which is also used to determine whether the local game object is alive when the game state is in the second game state; a display module 502, which is also used to display M identifiers in the game interface when the determination module 501 determines that the local game object is not alive; one identifier is used to trigger an operation for the reminder event, and M is a positive integer; the receiving module 504 is also used to receive a third input from the user for a target identifier among the above M identifiers; the execution module 503 is also used to perform a second operation in response to the third input received by the receiving module 504; wherein the second operation includes any one of the following: keeping the above game interface displayed and postponing the reminder time of the above reminder event; instructing the game system of the game application to take over the local game object and display the prompt interface of the prompt event; instructing the game system to hang up the local game object and display the prompt interface.

[0107] It should be noted that if Figure 6 As shown, the modules that must be included in the reminder event processing device 500 are indicated by solid-line boxes, such as the determination module 501 ; the modules that may or may not be included in the reminder event processing device 500 are indicated by dotted-line boxes, such as the receiving module 504 .

[0108] The reminder event processing device provided in the embodiment of the present application can determine whether the game interface of the game application is displayed when the reminder event reaches the reminder time. Then, the reminder event processing device can determine the game state corresponding to the game interface when the game interface of the game application is displayed. Finally, the reminder event processing device can keep displaying the game interface and perform the target operation when the game state is in the target game state. Among them, the game interface includes a local game object; the target operation includes at least one of the following: displaying a reminder message of the reminder event in the message display area of ​​the game interface, and outputting the reminder message through the target game object voice. Through the above scheme, compared with the alarm clock reminder method in the related art, which makes the interaction between the electronic device and the user single, and may cause the user to forget what needs to be done, the reminder event processing device in the present application can combine the game with the reminder event. When the reminder event reaches the reminder time, if it is determined that the reminder event processing device displays the game interface of the game application, and the game state of the game interface is in the target game state, the reminder event processing device can keep displaying the game interface, and display the reminder message of the reminder event in the message display area of ​​the game interface, or output the reminder message through the target game object voice, so as to achieve the purpose of prompting the user. In this way, not only the fun of the user's gaming experience is improved, but also the user can be effectively reminded without affecting the user's gaming, and the interaction between the user and the electronic device is enriched.

[0109] The beneficial effects of various implementations in this embodiment can be specifically referred to the beneficial effects of the corresponding implementations in the above method embodiment. To avoid repetition, they will not be described again here.

[0110] The reminder event processing device in the embodiment of the present application can be a device, or a component, integrated circuit, or chip in a terminal. The device can be a mobile electronic device or a non-mobile electronic device. Exemplarily, the mobile electronic device can be a mobile phone, a tablet computer, a laptop computer, a PDA, an in-vehicle electronic device, a wearable device, an ultra-mobile personal computer (UMPC), a netbook, or a personal digital assistant (PDA), etc. The non-mobile electronic device can be a server, a network attached storage (NAS), a personal computer (PC), a television (TV), a teller machine or a self-service machine, etc., which is not specifically limited in the embodiment of the present application.

[0111] The reminder event processing device in the embodiment of the present application may be a device having an operating system. The operating system may be an Android operating system, an iOS operating system, or other possible operating systems, which are not specifically limited in the embodiment of the present application.

[0112] The reminder event processing device provided in the embodiment of the present application can achieve Figures 1 to 5 To avoid repetition, the various processes implemented by the method embodiment are not described here.

[0113] Optional, such as Figure 7 As shown, an embodiment of the present application also provides an electronic device 600, including a processor 601, a memory 602, and a program or instruction stored in the memory 602 and executable on the processor 601. When the program or instruction is executed by the processor 601, each process of the above-mentioned reminder event processing method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0114] It should be noted that the electronic devices in the embodiments of the present application include the mobile electronic devices and non-mobile electronic devices mentioned above.

[0115] Figure 8 A schematic diagram of the hardware structure of an electronic device to implement an embodiment of the present application.

[0116] The electronic device 100 includes but is not limited to components such as a radio frequency unit 101, a network module 102, an audio output unit 103, an input unit 104, a sensor 105, a display unit 106, a user input unit 107, an interface unit 108, a memory 109, and a processor 110.

[0117] Those skilled in the art will appreciate that the electronic device 100 may also include a power source (such as a battery) for supplying power to various components, and the power source may be logically connected to the processor 110 through a power management system, thereby implementing functions such as managing charging, discharging, and power consumption management through the power management system. Figure 8 The electronic device structure shown in the figure does not constitute a limitation on the electronic device. The electronic device may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently, which will not be described in detail here.

[0118] Among them, the processor 110 is used to determine whether a game interface of a game application is displayed when the reminder event reaches the reminder time, and the game interface includes a local game object; and when the game interface of the game application is displayed, determine the game state corresponding to the game interface; the display unit 106 is used to keep displaying the game interface when the processor 110 determines that the game state is in the target game state; the processor 110 is also used to perform a target operation when it is determined that the game state is in the target game state, and the target operation includes at least one of the following: displaying a prompt message of the reminder event in the message display area of ​​the game interface, and outputting the prompt message through the voice of the target game object.

[0119] Optionally, the game interface includes at least one of the following: at least one non-player game object and at least one opponent game object; the processor 110 is specifically used to determine the game state corresponding to the game interface according to the estimated death frequency corresponding to the game object in the game interface.

[0120] Optionally, the target game state is the first game state; the display unit 106 is further used to display N non-player game objects in the game interface when the processor 110 determines that the game state is in the first game state, and one non-player game object is used to trigger an operation for a reminder event, where N is a positive integer; the user input unit 107 is used to receive a first input from a user to a first non-player game object among the N non-player game objects; the display unit 106 is specifically used to keep displaying the game interface in response to the first input received by the user input unit 107; the processor 110 is specifically used to execute the target operation in response to the first input received by the user input unit 107; wherein the target game object is the first non-player game object.

[0121] Optionally, the user input unit 107 is further used to receive a second input from a user for a second non-player game object among the above-mentioned N non-player game objects; the processor 110 is further used to perform a first operation in response to the second input received by the user input unit 107, and the first operation includes any one of the following: keeping the above-mentioned game interface displayed and postponing the reminder time of the above-mentioned prompt event; instructing the game system of the game application to take over the local game object and display the prompt interface of the prompt event; instructing the game system to hang up the local game object and display the prompt interface.

[0122] Optionally, the first operation is to keep displaying the game interface and postpone the reminder time of the prompt event; the display unit 106 is also used to cancel the display of all or part of the N non-player game objects in the game interface in response to the second input received by the user input unit 107.

[0123] Optionally, the target game state is a second game state; the processor 110 is further used to determine whether at least one game object among at least one opposite game object is alive when the game state is in the second game state; the display unit 106 is specifically used to keep displaying the game interface when the processor 110 determines that at least one game object is not alive; and to perform a target operation when at least one game object is not alive.

[0124] Optionally, the processor 110 is further used to determine whether the local game object is alive when the game state is in the second game state; the display unit 106 is further used to display M identifiers in the game interface when the processor 110 determines that the local game object is not alive; one identifier is used to trigger an operation for a reminder event, and M is a positive integer; the user input unit 107 is further used to receive a third input from the user for a target identifier among the above-mentioned M identifiers; the processor 110 is further used to perform a second operation in response to the third input received by the user input unit 107; wherein the second operation includes any one of the following: keeping the above-mentioned game interface displayed and postponing the reminder time of the above-mentioned prompt event; instructing the game system of the game application to take over the local game object and display the prompt interface of the prompt event; instructing the game system to hang up the local game object and display the prompt interface.

[0125] The electronic device provided by the embodiment of the present application can determine whether the game interface of the game application is displayed when the reminder event reaches the reminder moment. Then, the electronic device can determine the game state corresponding to the game interface when the game interface of the game application is displayed. Finally, the electronic device can keep displaying the game interface and perform the target operation when the game state is in the target game state. Among them, the game interface includes a local game object; the target operation includes at least one of the following: displaying a reminder message of the reminder event in the message display area of ​​the game interface, and outputting the reminder message through the target game object voice. Through the above scheme, compared with the alarm clock reminder method in the related art, which makes the interaction between the electronic device and the user single, and may cause the user to forget what needs to be done, the electronic device in the present application can combine the game with the reminder event. When the reminder event reaches the reminder moment, if it is determined that the electronic device displays the game interface of the game application, and the game state of the game interface is in the target game state, the electronic device can keep displaying the game interface, and display the reminder message of the reminder event in the message display area of ​​the game interface, or output the reminder message through the target game object voice, so as to achieve the purpose of prompting the user. In this way, not only the fun of the user's gaming experience is improved, but also the user can be effectively reminded without affecting the user's gaming, and the interaction between the user and the electronic device is enriched.

[0126] The beneficial effects of various implementations in this embodiment can be specifically referred to the beneficial effects of the corresponding implementations in the above method embodiment. To avoid repetition, they will not be described again here.

[0127] It should be understood that in the embodiment of the present application, the input unit 104 may include a graphics processor (Graphics Processing Unit, GPU) 1041 and a microphone 1042, and the graphics processor 1041 processes the image data of the static picture or video obtained by the image capture device (such as a camera) in the video capture mode or the image capture mode. The display unit 106 may include a display panel 1061, and the display panel 1061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 107 includes a touch panel 1071 and other input devices 1072. The touch panel 1071 is also called a touch screen. The touch panel 1071 may include two parts: a touch detection device and a touch controller. Other input devices 1072 may include but are not limited to a physical keyboard, a function key (such as a volume control button, a switch button, etc.), a trackball, a mouse, and a joystick, which will not be repeated here. The memory 109 can be used to store software programs and various data, including but not limited to applications and operating systems. The processor 110 can integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, the user interface, and the application program, etc., and the modem processor mainly processes wireless communication. It is understandable that the above-mentioned modem processor may not be integrated into the processor 110.

[0128] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the above-mentioned reminder event processing method embodiment are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0129] The processor is a processor in the electronic device described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0130] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned reminder event processing method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0131] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0132] It should be noted that, in this article, the terms "comprise", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise one..." do not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method may be performed in an order different from that described, and various steps may also be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0133] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a computer software product, which is stored in a storage medium (such as ROM / RAM, a disk, or an optical disk), and includes a number of instructions for a terminal (which can be a mobile phone, a computer, a server, or a network device, etc.) to execute the methods described in each embodiment of the present application.

[0134] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms without departing from the purpose of the present application and the scope of protection of the claims, all of which are within the protection of the present application.

Claims

1. A method for processing a reminder event, characterized in that: The method comprises: When the reminder event reaches the reminder time, determining whether a game interface of the game application is displayed, the game interface including the local game object; When a game interface of the game application is displayed, determining a game state corresponding to the game interface; When the game state is in the target game state, the game interface is kept displayed, and a target operation is performed, wherein the target operation includes at least one of the following: displaying a prompt message of the reminder event in a message display area of ​​the game interface, and outputting the prompt message through the voice of the target game object in the game interface; The game interface includes at least one non-player game object, and the target game state is a first game state; When the game state is in the target game state, the game interface is kept displayed, and a target operation is performed, including: When the game state is in the first game state, N non-player game objects are displayed in the game interface, one non-player game object is used to trigger an operation for the reminder event, and N is a positive integer; Receiving a first input from a user to a first non-player game object among the N non-player game objects; In response to the first input, the game interface is kept displayed, and a target operation is performed; wherein the target game object is the first non-player game object.

2. The method according to claim 1, characterized in that The game interface includes at least one of the following: at least one non-player game object, at least one opponent game object; The determining the game state corresponding to the game interface includes: The game state corresponding to the game interface is determined according to the estimated death frequency corresponding to the game object in the game interface.

3. The method according to claim 1, characterized in that After displaying N non-player game objects in the game interface, the method further includes: receiving a second input from a user to a second non-player game object among the N non-player game objects; In response to the second input, a first operation is performed, and the first operation includes any one of the following: keeping the game interface displayed and postponing the reminder time of the reminder event; instructing the game system of the game application to take over the local game object and display the prompt interface of the reminder event; instructing the game system to hang up the local game object and display the prompt interface.

4. The method according to claim 3, characterized in that The first operation is to keep displaying the game interface and postpone the reminder time of the reminder event; After receiving a second user input to a second non-player game object among the N non-player game objects, the method further includes: In response to the second input, all or part of the N non-player game objects are canceled from display in the game interface.

5. The method according to claim 2, characterized in that: The target game state is a second game state; When the game state is in the target game state, the game interface is kept displayed, and a target operation is performed, including: When the game state is in the second game state, determining whether at least one game object among the at least one opposite game object is alive; When the at least one game object is not alive, the game interface is kept displayed and the target operation is performed.

6. The method according to claim 5, characterized in that The method further comprises: When the game state is in the second game state, determining whether the local game object is alive; In the case where the local game object is not alive, M identifiers are displayed in the game interface; one identifier is used to trigger an operation for the reminder event, and M is a positive integer; receiving a third input from a user regarding a target identifier among the M identifiers; In response to the third input, performing a second operation; Among them, the second operation includes any one of the following: keeping the game interface displayed and postponing the reminder time of the reminder event; instructing the game system of the game application to take over the local game object and display the prompt interface of the reminder event; instructing the game system to hang up the local game object and display the prompt interface.

7. A reminder event processing device, characterized in that: The reminder event processing device includes: a determination module, a display module and an execution module; The determination module is used to determine whether a game interface of a game application is displayed when the reminder event reaches the reminder time, the game interface including a local game object; and determine a game state corresponding to the game interface when the game interface of the game application is displayed; The display module is used to keep displaying the game interface when the determination module determines that the game state is in the target game state; The execution module is used to execute a target operation when the determination module determines that the game state is in a target game state, and the target operation includes at least one of the following: displaying a prompt message of the reminder event in a message display area of ​​the game interface, and outputting the prompt message through a target game object voice; The game interface includes at least one non-player game object, and the target game state is a first game state; The reminder event processing device further includes: a receiving module; The display module is specifically used to display N non-player game objects in the game interface when the game state is in the first game state, and one non-player game object is used to trigger an operation for the reminder event, where N is a positive integer; The receiving module is used to receive a first input from a user on a first non-player game object among the N non-player game objects displayed by the display module; The display module is further configured to keep displaying the game interface in response to the first input received by the receiving module; The execution module is specifically configured to execute a target operation in response to the first input received by the receiving module; wherein the target game object is the first non-player game object.

8. The reminder event processing device according to claim 7, characterized in that: The game interface includes at least one of the following: at least one non-player game object, at least one opponent game object; The determination module is specifically used to determine the game state corresponding to the game interface according to the estimated death frequency corresponding to the game object in the game interface.

9. An electronic device, characterized in that: It comprises a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the reminder event processing method as described in any one of claims 1 to 6.

10. A readable storage medium, characterized in that: The readable storage medium stores a program or instruction, and when the program or instruction is executed by the processor, the steps of the reminder event processing method according to any one of claims 1 to 6 are implemented.

Images