Interface interaction method and device, equipment and storage medium

Abstract

The embodiment of the invention relates to an interface interaction method and device, equipment and a storage medium. The method comprises the steps that in an interface associated with a first user and a second user, an interaction identifier is presented, and the state of the interaction identifier is determined based on historical interaction of the first user and the second user; in response to the interaction identifier being in the first state, presenting reminding information associated with the first event in the interface; and in response to the fact that the first event is completed by cooperation of the first user and the second user, updating the interaction identifier from the first state to the second state, wherein the interaction identifier is further configured to update from the first state to the second state in response to the following conditions being satisfied: the first user and the second user cooperate to complete the second event in each of the plurality of time periods. In this way, according to the embodiment of the invention, the interaction efficiency between users can be improved.

Description

Technical Field

[0001] Example embodiments of the present disclosure generally relate to the field of computers, and more particularly, to methods, devices, apparatuses, and computer-readable storage media for interface interaction. Background Art

[0002] As network technology matures, more and more users use network platforms to interact and communicate. For example, in some interactive scenarios, network platforms provide interactive identifiers for users who interact with each other to indicate the interactive information between users. The status of the interactive identifier will be updated as the users interact. The existing method of maintaining the interactive identifier cannot meet the needs of users. Summary of the invention

[0003] In a first aspect of the present disclosure, a method for interface interaction is provided. The method includes: presenting an interaction identifier in an interface associated with a first user and a second user, wherein the state of the interaction identifier is determined based on the historical interaction between the first user and the second user; in response to the interaction identifier being in a first state, presenting reminder information associated with a first event in the interface; and in response to the first event being completed collaboratively by the first user and the second user, updating the interaction identifier from the first state to the second state, wherein the interaction identifier is further configured to be updated from the first state to the second state in response to the following condition being met: the first user and the second user both collaboratively complete the second event in each time period of a plurality of time periods.

[0004] In a second aspect of the present disclosure, a device for interface interaction is provided. The device includes: a first presentation module, configured to present an interaction identifier in an interface associated with a first user and a second user, wherein the state of the interaction identifier is determined based on the historical interaction between the first user and the second user; a second presentation module, configured to present reminder information associated with a first event in the interface in response to the interaction identifier being in a first state; and an update module, configured to update the interaction identifier from a first state to a second state in response to the first event being completed collaboratively by the first user and the second user, wherein the interaction identifier is further configured to be updated from a first state to a second state in response to the following condition being met: the first user and the second user both collaboratively complete the second event in each time period of multiple time periods.

[0005] In a third aspect of the present disclosure, an electronic device is provided. The device includes at least one processing unit; and at least one memory, the at least one memory is coupled to the at least one processing unit and stores instructions for execution by the at least one processing unit. When the instructions are executed by the at least one processing unit, the device executes the method of the first aspect.

[0006] In a fourth aspect of the present disclosure, a computer-readable storage medium is provided, wherein a computer program is stored on the computer-readable storage medium, and the computer program can be executed by a processor to implement the method of the first aspect.

[0007] It should be understood that the contents described in this content section are not intended to limit the key features or important features of the embodiments of the present disclosure, nor are they intended to limit the scope of the present disclosure. Other features of the present disclosure will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] The above and other features, advantages and aspects of the embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. In the accompanying drawings, the same or similar reference numerals represent the same or similar elements, wherein:

[0009] Figure 1 A schematic diagram showing an example environment in which embodiments according to the present disclosure may be implemented;

[0010] FIG. 2A to FIG. 2F shows an example interface according to some embodiments of the present disclosure;

[0011] Figure 3 A flowchart showing an example process of interface interaction according to some embodiments of the present disclosure;

[0012] Figure 4 A schematic structural block diagram showing an example device for interface interaction according to some embodiments of the present disclosure; and

[0013] Figure 5 A block diagram of an electronic device capable of implementing various embodiments of the present disclosure is shown. DETAILED DESCRIPTION

[0014] Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as being limited to the embodiments set forth herein. On the contrary, these embodiments are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are only for exemplary purposes and are not intended to limit the scope of protection of the present disclosure.

[0015] It should be noted that the titles of any sections / subsections provided herein are not restrictive. Various embodiments are described throughout this article, and any type of embodiment may be included under any section / subsection. In addition, the embodiments described in any section / subsection may be combined in any manner with any other embodiments described in the same section / subsection and / or different sections / subsections.

[0016] In the description of the embodiments of the present disclosure, the term "including" and similar terms should be understood as open inclusion, that is, "including but not limited to". The term "based on" should be understood as "based at least in part on". The term "one embodiment" or "the embodiment" should be understood as "at least one embodiment". The term "some embodiments" should be understood as "at least some embodiments". Other explicit and implicit definitions may be included below. The terms "first", "second", etc. may refer to different or the same objects. Other explicit and implicit definitions may be included below.

[0017] The embodiments of the present disclosure may involve user data, data acquisition and / or use, etc. These aspects are subject to the corresponding laws, regulations and relevant provisions. In the embodiments of the present disclosure, all data collection, acquisition, processing, processing, forwarding, use, etc. are carried out on the premise that the user knows and confirms. Accordingly, when implementing each embodiment of the present disclosure, the type, scope of use, usage scenario, etc. of the data or information that may be involved should be informed to the user and the user's authorization should be obtained in an appropriate manner in accordance with the relevant laws and regulations. The specific notification and / or authorization method can vary according to the actual situation and application scenario, and the scope of the present disclosure is not limited in this respect.

[0018] In this specification and the embodiments, if personal information processing is involved, it will be processed on the premise of having a legal basis (such as obtaining the consent of the subject of personal information, or it is necessary to perform a contract, etc.), and will only be processed within the scope of regulations or agreements. If a user refuses to process personal information other than the necessary information for basic functions, it will not affect the user's use of basic functions.

[0019] As mentioned above, as network technology becomes increasingly mature, more and more users use network platforms to interact and communicate. For example, in some interactive scenarios, network platforms will provide interactive identifiers for users who interact with each other to indicate the interactive information between users. The status of the interactive identifier will be updated as the users interact. The existing method of maintaining the interactive identifier cannot meet the needs of users.

[0020] The embodiment of the present disclosure proposes a scheme for interface interaction. According to the scheme, an interaction identifier can be presented in an interface associated with a first user and a second user, wherein the state of the interaction identifier is determined based on the historical interaction between the first user and the second user; in response to the interaction identifier being in a first state, reminder information associated with a first event is presented in the interface; and in response to the first event being completed collaboratively by the first user and the second user, the interaction identifier is updated from the first state to the second state, wherein the interaction identifier is further configured to be updated from the first state to the second state in response to the following condition being met: the first user and the second user both collaboratively complete the second event in each time period of multiple time periods.

[0021] In this way, the embodiments of the present disclosure can present an interaction identifier determined based on the historical interactions of the first user and the second user in an interface associated with the first user and the second user. Further, in response to the interaction identifier being in the first state, the embodiments of the present disclosure can present reminder information associated with the first event in the interface so that the first user and the second user can collaborate to complete the first event, thereby updating the interaction identifier from the first state to the second state. In addition, the embodiments of the present disclosure can also support the first user and the second user to complete the second event within multiple time periods to update the state of the interaction identifier. In this way, the embodiments of the present disclosure can support the first user and the second user to update the state of the interaction identifier by collaboratively completing the first event or the second event associated with multiple time periods, enriching the way users update the state of the interaction identifier, improving the efficiency of users maintaining the interaction identifier, and meeting the interaction needs of users.

[0022] Various example implementations of the solution are described in detail below in conjunction with the accompanying drawings.

[0023] Example Environment

[0024] Figure 1 1 is a schematic diagram of an example environment 100 in which embodiments of the present disclosure can be implemented. Figure 1 As shown, example environment 100 may include electronic device 110 .

[0025] In this example environment 100, the electronic device 110 may run an application 120 that supports interface interaction. The application 120 may be any appropriate type of application for interface interaction, examples of which may include, but are not limited to, media applications, conference applications, social applications, or other appropriate applications. The user 140 may interact with the application 120 via the electronic device 110 and / or its attached devices.

[0026] exist Figure 1 In the environment 100, if the application 120 is in an active state, the electronic device 110 can present an interface 150 for supporting interface interaction through the application 120.

[0027] In some embodiments, the electronic device 110 communicates with the server 130 to provide services for the application 120. The electronic device 110 can be any type of mobile terminal, fixed terminal or portable terminal, including a mobile phone, a desktop computer, a laptop computer, a notebook computer, a netbook computer, a tablet computer, a media computer, a multimedia tablet, a handheld computer, a portable game terminal, a VR / AR device, a personal communication system (PCS) device, a personal navigation device, a personal digital assistant (PDA), an audio / video player, a digital camera / camcorder, a positioning device, a television receiver, a radio receiver, an e-book device, a game device, or any combination of the foregoing, including accessories and peripherals of these devices or any combination thereof. In some embodiments, the electronic device 110 can also support any type of interface for the user (such as a "wearable" circuit, etc.).

[0028] The server 130 may be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content distribution networks, and big data and artificial intelligence platforms. The server 130 may include, for example, a computing system / server, such as a mainframe, an edge computing node, a computing device in a cloud environment, etc. The server 130 may provide background services for the application 120 that supports virtual scenes in the electronic device 110.

[0029] A communication connection may be established between the server 130 and the electronic device 110. The communication connection may be established in a wired manner or a wireless manner. The communication connection may include, but is not limited to, a Bluetooth connection, a mobile network connection, a Universal Serial Bus (USB) connection, a Wireless Fidelity (WiFi) connection, etc., and the embodiments of the present disclosure are not limited in this respect. In the embodiments of the present disclosure, the server 130 and the electronic device 110 may implement signaling interaction through the communication connection between the two.

[0030] It should be understood that the structure and function of the various elements in the environment 100 are described for exemplary purposes only and do not imply any limitation on the scope of the present disclosure.

[0031] Some example embodiments of the present disclosure will be described below with continued reference to the accompanying drawings.

[0032] Example Interaction

[0033] FIG. 2A to FIG. 2F 200A to 200F according to some embodiments of the present disclosure. The interfaces 200A to 200F may be composed of, for example, Figure 1 The electronic device 110 is provided as shown.

[0034] In some embodiments, the electronic device 110 may present an interaction identifier in an interface associated with a first user (e.g., user B) and a second user (e.g., user A). As an example, the interface associated with the first user and the second user may include a conversation interface, a game interface, or a media content viewing interface, etc. Alternatively, the interface associated with the first user and the second user may include multiple interfaces provided by multiple different applications.

[0035] In some embodiments, Figure 2A As shown, the electronic device 110 can present an interface 200A associated with the first user and the second user. For example, the interface 200A can be provided by the B application (e.g., also referred to as the second application). The electronic device 110 can present an interactive logo in the interface 200A. For example, the electronic device 110 can present a visual representation 205 (e.g., "spark") corresponding to the interactive logo in the interface 200A. It should be noted that the visual representation 205 here is only an exemplary description, and the present disclosure is not intended to limit the visual elements of the interactive logo.

[0036] In some embodiments, the interaction identifier is determined based on the historical interaction between the first user and the second user. As an example, the interaction identifier may indicate the degree of interaction between the first user and the second user. For example, such historical interaction may include, for example, a first group of interaction events in which the first user and the second user jointly participated. The first user and the second user may obtain the interaction identifier in response to the interaction attributes of the first group of interaction events satisfying a preset condition. For example, the interaction attributes may include interaction frequency, interaction content, etc.

[0037] In some embodiments, the interaction identifier may be associated with the virtual object. For example, the virtual object may be associated with the first user and the second user. As an example, the virtual object is provided to the first user and the second user in response to the historical interaction between the first user and the second user satisfying a preset condition. For example, such historical interaction may include, for example, a second set of interaction events in which the first user and the second user jointly participated. The first user and the second user may obtain the virtual object in response to the interaction attributes of the second set of interaction events satisfying a preset condition. For example, the interaction attributes may include interaction frequency, interaction content, etc.

[0038] For example, such a first group of interaction events and / or a second group of interaction events may include text message interactions, image message interactions, audio message interactions, video call interactions, voice call interactions, emoticon interactions, etc. in a conversation. For example, an interaction identifier or a virtual object may be provided to the first user and the second user in response to the number of consecutive days of the conversation between the first user and the second user meeting a preset number of days.

[0039] As an example, the interaction identifier may include a first state and a second state. For example, the first state may indicate that the historical interaction between the first user and the second user satisfies a first preset condition. As an example, such a first preset condition may include, for example, that the duration of no interaction between the first user and the second user reaches a preset duration (e.g., 24 hours). Alternatively, the second state may indicate that the historical interaction between the first user and the second user satisfies a second preset condition. As an example, such a second preset condition may include that the duration of no interaction between the first user and the second user does not reach a preset duration (e.g., 24 hours).

[0040] Alternatively, the interactive logo in the first state and the interactive logo in the second state may correspond to different visual representations (e.g., different shapes or different colors, etc.). For example, the interactive logo in the first state may correspond to a first visual representation (e.g., "gray sparks"). For example, the interactive logo in the second state may correspond to a second visual representation (e.g., "red sparks" or "black sparks", etc.). The present disclosure is not intended to limit the specific forms of expression of the first visual representation and the second visual representation.

[0041] As an example, the electronic device 110 may present a visual representation of a virtual object in an interface. The visual representation of the virtual object is determined based on the current state of the interactive identifier. For example, the electronic device 110 may present a visual representation 208 of a virtual object in an interface 200A. As an example, since the current state of the interactive identifier is the first state, the visual representation 208 is a form of expression corresponding to the first state (e.g., a "gray virtual image"). In this way, the embodiments of the present disclosure can associate the visual representation of the virtual object with the current state of the interactive identifier, so that the user can be reminded of the current state of the interactive identifier based on the visual representation of the virtual object, which helps to remind the user to update the state of the interactive identifier as soon as possible by completing the corresponding event, thereby meeting the needs of the user.

[0042] In some embodiments, the electronic device 110 may present reminder information associated with the first event in the interface in response to the interactive identifier being in the first state. As an example, the reminder information associated with the first event may include reminder information 206 associated with the visual representation 205 of the interactive identifier. Such reminder information 206 may, for example, include presenting the visual representation 205 based on a color (e.g., "gray") corresponding to the first state. Such a reminder message 206 may also include text information (e.g., "disappears after X days"). The text message here may indicate that the interactive identifier is currently in the first state and that the interactive identifier will disappear after X days.

[0043] In some embodiments, the electronic device 110 may periodically present reminder information associated with the first event in the interface in response to the interactive identifier being in the first state. For example, the electronic device 110 may present reminder information associated with the first event in the interface every predetermined time period (e.g., 24 hours) in response to the interactive identifier being in the first state. Alternatively, the electronic device 110 may present reminder information associated with the first event in the interface in response to the interactive identifier being in the first state and receiving an input message from the first user or the second user.

[0044] As an example, the reminder information associated with the first event may include, for example, a reminder message. Interface 200A may include a second interface of a second application. For example, the electronic device 110 may present reminder information 210 associated with the first event (also referred to as second reminder information, for example, "chat in application A, and rekindle the spark immediately to application A") in interface 200A. In some embodiments, the second interface includes a conversation interface. The conversation interface is associated with the first user and the second user. As an example, interface 200A may be a conversation interface between user B and user A. For example, a client (e.g., an electronic device) associated with user B may present interface 200A based on the operation of user B, that is, interface 200A is associated with the client of user B. For example, the electronic device 110 may present identification information associated with user A in interface 200A (e.g., avatar 207-1 and name 207-2 (e.g., "user A")). The electronic device 110 may present identification information associated with user B in interface 200A (e.g., avatar 209).

[0045] As an example, the electronic device 110 may trigger the presentation of the first interface of the first application (e.g., A application) in response to an operation (e.g., also referred to as a first operation) on a second reminder message (e.g., reminder message 210) on a second interface (e.g., interface 200A) of a second application (e.g., B application). As an example, the electronic device 110 may present an access entry 212 corresponding to the first application in the second reminder message (e.g., "Go to A application"). Further, the electronic device 110 may trigger the presentation of the first interface of the first application in response to a trigger (e.g., a click operation) on the access entry 212. As an example, the first interface is associated with the completion of the first event.

[0046] In some embodiments, the electronic device 110 may update the interaction identifier from the first state to the second state in response to the first event being completed collaboratively by the first user and the second user. That is, after the first user and the second user collaborate to complete the first event, the electronic device 110 may trigger the interaction identifier to be updated from the first state to the second state. As an example, such a first event may, for example, indicate at least one interactive operation collaboratively completed by the first user and the second user. Such at least one interactive operation may, for example, be associated with at least one interactive event in a group of interactive events. Such at least one interactive event may, for example, include text message interaction, image message interaction, audio message interaction, video call interaction, voice call interaction, or emoticon interaction in a conversation, etc. Such at least one interactive event may, for example, also include other interactive events unrelated to the conversation (e.g., accessing specified content or performing specified interactive operations, etc.). As an example, the first event may indicate the interactive operation of the first user and the second user in the first application. That is, the first event requires the first user and the second user to complete in the first application.

[0047] As an example, the first event may be a non-periodic event. For example, the first event may indicate that the first user and the second user perform a conversation operation in the first application (for example, send messages to each other in the first application). For example, the electronic device 110 may immediately update the state of the interaction identifier (for example, from the first state to the second state) in response to the completion of such a non-periodic event (for example, the first user and the second user send a message to each other once in the first application).

[0048] The opposite of non-periodic events is periodic events, and such periodic events require that corresponding events be completed in each event cycle of multiple event cycle contents. For example, the second event may be a periodic event.

[0049] As an example, the interaction identifier can also be configured to be updated from the first state to the second state in response to the following conditions being met. Such conditions can, for example, include that the first user and the second user both collaborate to complete the second event in each time period of multiple time periods. For example, the second event is a periodic event. As an example, the second event can include that the first user and the second user send messages to each other at least once every day for three consecutive days. In other words, the first user and the second user need to send messages to each other once on the first day, the second day, and the third day of three consecutive days to complete the second event. In this way, it takes at least three days for the first user and the second user to update the interaction identifier from the first state to the second state.

[0050] Alternatively, the second event may be associated with a second application. The second application is different from the first application. That is, the first event and the second event need to be completed in different applications. In this way, the embodiments of the present disclosure can provide users with operation methods for updating the status of interaction identifiers associated with different applications, and the diverse selection methods meet the interaction needs of different users.

[0051] As an example, the first event may be associated with the first application. Figure 2B As shown, the electronic device 110 may present an interface 200B associated with the first user and the second user. For example, the interface 200B may be associated with a first application. The first application (e.g., "A application") is different from the aforementioned second application (e.g., "B application").

[0052] As an example, the electronic device 110 may present the interface 200B associated with the first user and the second user in response to the user's preset operation on the first application. Figure 2A The access entry 212 in the interface 200B is triggered (for example, a click operation) to present the interface 200B associated with the first user and the second user.

[0053] In some embodiments, the electronic device 110 may present reminder information 215 (also referred to as first reminder information, for example, “Chat with each other in A application and rekindle the spark immediately”) associated with the first event in the first interface (e.g., interface 200B) of the first application (e.g., A application).

[0054] As an example, the first interface of the first application (e.g., interface 200B) may include, for example, a first conversation interface between a first user and a second user. As an example, interface 200B may be a second conversation interface between user B and user A. For example, electronic device 110 may present identification information associated with user A in interface 200B (e.g., avatar 213-1 and name 213-2 (e.g., "User A")). Electronic device 110 may present identification information associated with user B in interface 200B (e.g., avatar 214). For example, a client associated with user B may present interface 200B based on the operation of user B, that is, interface 200B is associated with the client of user B.

[0055] Alternatively, the electronic device 110 may present a visual representation 219 corresponding to the virtual object in the interface 200B. The electronic device 110 may present a visual representation 220 (e.g., “spark”) corresponding to the interactive identifier in the interface 200B. The electronic device 110 may also present a reminder message 221 (e.g., “disappears after X days”) in the interface 200B in response to the interactive identifier being in the first state.

[0056] In some embodiments, the electronic device 110 may send a message (e.g., also referred to as a first message) in the first conversation interface in response to an operation (also referred to as a second operation) on a first reminder message (e.g., reminder message 215) presented in the first conversation interface (e.g., interface 200B). As an example, the first message comes from a first user (e.g., user B). As an example, the electronic device 110 may present a control 218 (e.g., "Rekindle the Spark") associated with the first message in the first reminder message. Further, the electronic device 110 may present the first message from the first user in the first conversation interface in response to a trigger (e.g., a click operation) on the control 218.

[0057] In some embodiments, Figure 2C As shown, the electronic device 110 may present the first message 225 in the interface 200C (e.g., the first conversation interface of the A application). As an example, the first message 225 may be associated with the interaction identifier. For example, the first message 225 may include a visual representation associated with the interaction identifier.

[0058] Alternatively, the electronic device 110 may also present a reminder message 230 (also referred to as a third reminder message, for example, “Invite the other party to chat on application A and rekindle the spark immediately by sending an invitation”) in the first conversation interface (e.g., interface 200C) in response to the first message being sent. Further, the electronic device 110 may send a message (also referred to as a second message) in the first conversation interface in response to an operation on the reminder message 230 (also referred to as a third operation). As an example, the electronic device 110 may provide a control 232 (e.g., “Initiate an invitation”) in the reminder message 230. Further, the electronic device 110 may present a second message from the first user in the first conversation interface in response to triggering the control 232 (e.g., a click operation).

[0059] In some embodiments, Figure 2D As shown, the electronic device 110 may present the second message 235 in the interface 200D (e.g., the first conversation interface). As an example, the second message 235 may include text content (e.g., "Invite you to rekindle the spark in application A", "Open application A", etc.). As an example, the second message 235 may also include identification information associated with the first application (e.g., identification 236). Alternatively, the second message 235 may also include a preset text message.

[0060] Additionally, the second message may include an access portal (or link) corresponding to the first application. For example, the access portal may support the second user's selection of the access portal, triggering the presentation of the first interface of the first application (e.g., a first conversation interface associated with the first user and the second user) to the second user.

[0061] Alternatively, the electronic device 110 may trigger, in response to a third operation on the third reminder message, to present the second message in a second conversation interface of a second application (e.g., application B). As an example, the second conversation interface may be associated with the first user and the second user. Figure 2E As shown, the electronic device can present the second message (e.g., message 240) from the first user in interface 200E (e.g., the second conversation interface). For example, the client associated with the second user (e.g., user A) can present interface 200E based on the operation of the second user, that is, interface 200E is associated with the client of the second user. Further, the client associated with the second user (e.g., electronic device) can present the first interface of the first application in response to a trigger (e.g., a click operation) to message 240.

[0062] As an example, Figure 2FAs shown, the client associated with the second user can present the first interface of the first application (e.g., interface 200F). As an example, the client associated with the second user can present an input message 245 (also referred to as a third message, e.g., “I’m here”) from the second user in interface 200F in response to receiving an input message from the second user.

[0063] Additionally, the client associated with the second user may update the state of the interaction identifier from the first state to the second state in response to receiving the input message 245 to confirm that the first event is completed (for example, the first user and the second user have completed messaging each other in the first application). For example, the client associated with the second user may present a visual representation 250 (for example, "red sparks" or "black sparks") of the interaction identifier in the second state in the interface 200F. Alternatively, the client associated with the second user may present descriptive information 251 (for example, "300") associated with the interaction identifier in the second state in the interface 200F to indicate the interaction information (for example, number of days of interaction) between the first user and the second user.

[0064] Alternatively, the client associated with the second user may present a visual representation 255 of the virtual object associated with the second state (e.g., a “white visual image” or a “red visual image”, etc.) in interface 200F in response to the state of the interaction identifier being updated from the first state to the second state.

[0065] Alternatively, the client associated with the second user may respond to the interaction identifier being in the first state for a preset period of time (e.g., 7 days) and both the first event and the second event being uncompleted, triggering the cessation of presenting the interaction identifier in the interface associated with the first user and the second user.

[0066] In some embodiments, the first interface of the first application and the second interface of the second application may have the same interface layout (e.g., the style of the message area and the style of the message component, etc.). Alternatively, the first message content (e.g., "chat history") presented in the first interface associated with the first user and the second user may be at least partially the same as the second message content presented in the second interface associated with the first user and the second user.

[0067] Based on the process described above, the embodiment of the present disclosure can present an interaction identifier determined based on the historical interaction between the first user and the second user in an interface associated with the first user and the second user. Further, in response to the interaction identifier being in the first state, the embodiment of the present disclosure can present reminder information associated with the first event in the interface so that the first user and the second user can collaborate to complete the first event, thereby updating the interaction identifier from the first state to the second state. In addition, the embodiment of the present disclosure can also support the first user and the second user to complete the second event within multiple time periods to update the state of the interaction identifier. In this way, the embodiment of the present disclosure can support the first user and the second user to update the state of the interaction identifier by collaboratively completing the first event or the second event associated with multiple time periods, enriching the way users update the state of the interaction identifier, improving the efficiency of users maintaining the interaction identifier, and meeting the interaction needs of users.

[0068] Example Process

[0069] Figure 3 FIG. 3 is a flowchart showing an example process 300 of interface interaction according to some embodiments of the present disclosure. The process 300 may be implemented at the electronic device 110. Figure 1 The process 300 is described below.

[0070] like Figure 3 As shown, in box 310, the electronic device 110 presents an interaction indicator in an interface associated with the first user and the second user, wherein the state of the interaction indicator is determined based on the historical interaction between the first user and the second user.

[0071] In box 320, in response to the interaction indicator being in the first state, the electronic device 110 presents reminder information associated with the first event in the interface.

[0072] In box 330, in response to the first event being completed collaboratively by the first user and the second user, the electronic device 110 updates the interaction identifier from the first state to the second state, wherein the interaction identifier is further configured to be updated from the first state to the second state in response to the following condition being met: the first user and the second user both collaboratively complete the second event in each time period of multiple time periods.

[0073] In some embodiments, the first event is a non-periodic event and the second event is a periodic event.

[0074] In this way, the embodiments of the present disclosure can provide users with different types of events to update the status of the interaction identifier, enrich the user's choices, and meet the user's interaction needs.

[0075] In some embodiments, the first event is associated with a first application and the second event is associated with a second application different from the first application.

[0076] In this way, the embodiments of the present disclosure can provide users with events associated with different applications to update the status of interaction identifiers, enriching the user's choices and satisfying the user's interaction needs.

[0077] In some embodiments, the first event indicates an interactive operation between the first user and the second user in the first application.

[0078] In this way, the embodiments of the present disclosure can support the user to update the status of the interaction identifier based on the interactive operation in the first application, thereby improving the efficiency of the user in updating the status of the interaction identifier and meeting the needs of the user.

[0079] In some embodiments, presenting reminder information associated with the first event in an interface includes: presenting first reminder information associated with the first event in a first interface of a first application.

[0080] In this way, the embodiments of the present disclosure can present reminder information associated with the first event in the interface associated with the first application, thereby indicating to the user how to update the interaction identification status, improving the user's interaction efficiency and meeting the user's needs.

[0081] In some embodiments, presenting first reminder information associated with a first event in a first interface of a first application includes: presenting the first interface of the first application in response to a first operation on second reminder information presented in a second interface of a second application, the second reminder information being associated with the first event; and presenting the first reminder information in the first interface.

[0082] In this way, the embodiment of the present disclosure can present the reminder information associated with the first event to the user in the second interface of the second application. And the present disclosure can trigger the presentation of the first interface of the first application based on the user's operation, and present the reminder information associated with the first event in the first interface. In this way, the present disclosure can provide a convenient jump entry and guidance instructions for the user to complete the first event in the first application, thereby improving the efficiency of the user to complete the first event.

[0083] In some embodiments, the first interface is a first conversation interface between a first user and a second user, and process 300 further includes: sending a first message in the first conversation interface in response to a second operation on the first reminder information presented on the first interface.

[0084] In this way, the embodiments of the present disclosure can support the first user's interactive operation on the first reminder information, and present the first message based on the interactive operation, thereby helping the first user to quickly complete the operation associated with the first event and remind the second user to complete the first event, thereby improving the interaction efficiency between the first user and the second user and the efficiency of completing the first event.

[0085] In some embodiments, the first message is associated with an interaction identifier.

[0086] In this way, the embodiment of the present disclosure associates the first message with the interaction identifier, which can help the first user more clearly indicate to the second user the need to update the status of the interaction identifier, thereby helping to improve the interaction efficiency between the first user and the second user and the efficiency of completing the first event.

[0087] In some embodiments, process 300 further includes: in response to the first message being sent, presenting third reminder information in the first conversation interface; and in response to a third operation on the third reminder information, sending a second message in the first conversation interface.

[0088] In this way, an embodiment of the present disclosure can present a reminder message for completing a first event to a first user in response to a first message being sent, and send a second message based on the operation of the first user to help the first user guide the second user to complete the first event faster.

[0089] In some embodiments, process 300 further includes: triggering presentation of a second message in a second session interface of a second application, the second session interface being associated with the first user and the second user, the second message including an access entry corresponding to the first application.

[0090] In this way, the embodiment of the present disclosure can trigger the presentation of the second message in the second conversation interface of the second application in response to the second message being sent in the first application. And provide an access entry corresponding to the first application in the second message. In this way, the embodiment of the present disclosure can support users to complete cross-application reminder operations based on the first application, so that the second user can be reminded to complete the first event more conveniently. Providing an access entry corresponding to the first application in the second message further facilitates the efficiency of the second user entering the first application to complete the first event, saves the user's time, and meets the user's interactive needs.

[0091] In some embodiments, presenting reminder information associated with the first event in an interface includes: presenting second reminder information associated with the first event in a second interface of a second application.

[0092] In this way, the embodiment of the present disclosure can present reminder information associated with the first event in the second application, so that the user can know the method of updating the status of the interaction identifier, thereby meeting the needs of the user.

[0093] In some embodiments, process 300 further includes: in response to a first operation on the second reminder information, triggering presentation of a first interface of the first application, the first interface being associated with completing the first event.

[0094] In this way, the embodiments of the present disclosure can trigger the presentation of the first interface of the first application associated with the first event based on the user's operation on the reminder information in the second application, thereby saving the user's time in opening the first application, improving the user's efficiency in completing the first event, and meeting the user's needs.

[0095] In some embodiments, presenting reminder information associated with the first event in the interface includes: periodically presenting reminder information associated with the first event in the interface while the interaction indicator is in the first state.

[0096] In this way, the embodiments of the present disclosure meet the user's need for reminders by periodically reminding the user, which helps prevent the user from forgetting to update the status of the interaction identifier, and can provide a shortcut to continuously remind the user to update the status of the interaction identifier, thereby meeting the user's needs.

[0097] In some embodiments, the interaction identifier is associated with a virtual object, the virtual object is associated with the first user and the second user, and process 300 also includes: presenting a visual representation of the virtual object in the interface, the visual representation is determined based on the current state of the interaction identifier.

[0098] In this way, the embodiments of the present disclosure can associate the visual representation of the virtual object with the current state of the interactive marker, so that the user can be reminded of the current state of the interactive marker based on the visual representation of the virtual object, which helps to remind the user to update the state of the interactive marker as soon as possible by completing the corresponding event, thereby meeting the needs of the user.

[0099] Example devices and equipment

[0100] The embodiments of the present disclosure also provide corresponding devices for implementing the above methods or processes. Figure 4 A schematic structural block diagram of an example apparatus 400 for interface interaction according to some embodiments of the present disclosure is shown. The apparatus 400 may be implemented as or included in the electronic device 110. Each module / component in the apparatus 400 may be implemented by hardware, software, firmware, or any combination thereof.

[0101] like Figure 4As shown, the device 400 includes: a first presentation module 410, configured to present an interaction identifier in an interface associated with a first user and a second user, wherein the state of the interaction identifier is determined based on the historical interaction between the first user and the second user; a second presentation module 420, configured to present reminder information associated with a first event in the interface in response to the interaction identifier being in a first state; and an update module 430, configured to update the interaction identifier from a first state to a second state in response to the first event being collaboratively completed by the first user and the second user, wherein the interaction identifier can also be updated from the first state to the second state in response to the following condition being met: the first user and the second user both collaboratively complete the second event in each time period of multiple time periods.

[0102] In some embodiments, the first event is a non-periodic event and the second event is a periodic event.

[0103] In some embodiments, the first event is associated with a first application and the second event is associated with a second application different from the first application.

[0104] In some embodiments, the first event indicates an interactive operation between the first user and the second user in the first application.

[0105] In some embodiments, the second presentation module 420 is further configured to present first reminder information associated with the first event in the first interface of the first application.

[0106] In some embodiments, the second presentation module 420 is also configured to: present the first interface of the first application in response to a first operation on the second reminder information presented on the second interface of the second application, wherein the second reminder information is associated with the first event; and present the first reminder information in the first interface.

[0107] In some embodiments, the first interface is a first conversation interface between a first user and a second user, and the device 400 also includes a first sending module, which is configured to: send a first message in the first conversation interface in response to a second operation on the first reminder information presented on the first interface.

[0108] In some embodiments, the first message is associated with an interaction identifier.

[0109] In some embodiments, the device 400 also includes a second sending module, which is configured to: present a third reminder message in the first conversation interface in response to the first message being sent; and send a second message in the first conversation interface in response to a third operation on the third reminder message.

[0110] In some embodiments, the device 400 also includes a first trigger module, which is configured to: trigger the presentation of a second message in a second session interface of a second application, the second session interface is associated with the first user and the second user, and the second message includes an access entry corresponding to the first application.

[0111] In some embodiments, the second presentation module 420 is further configured to present second reminder information associated with the first event in a second interface of the second application.

[0112] In some embodiments, the device 400 further includes a second trigger module, which is configured to: in response to a first operation on the second reminder information, trigger presentation of a first interface of the first application, where the first interface is associated with completion of the first event.

[0113] In some embodiments, the second presentation module 420 is further configured to: periodically present reminder information associated with the first event in the interface while the interaction indicator is in the first state.

[0114] In some embodiments, the interaction identifier is associated with a virtual object, the virtual object is associated with a first user and a second user, and the device 400 also includes a third presentation module, which is configured to: present a visual representation of the virtual object in the interface, and the visual representation is determined based on the current state of the interaction identifier.

[0115] The units included in the device 400 can be implemented in various ways, including software, hardware, firmware, or any combination thereof. In some embodiments, one or more units can be implemented using software and / or firmware, such as machine executable instructions stored on a storage medium. In addition to or as an alternative to machine executable instructions, some or all of the units in the device 400 can be implemented at least in part by one or more hardware logic components. As an example and not limitation, exemplary types of hardware logic components that can be used include field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), and the like.

[0116] Figure 5 1 shows a block diagram of an electronic device 500 in which one or more embodiments of the present disclosure may be implemented. It should be understood that Figure 5 The electronic device 500 shown is merely exemplary and should not constitute any limitation on the functionality and scope of the embodiments described herein. Figure 5 The electronic device 500 shown can be used to implement Figure 1 An electronic device 110.

[0117] like Figure 5As shown, the electronic device 500 is in the form of a general electronic device. The components of the electronic device 500 may include, but are not limited to, one or more processors or processing units 510, a memory 520, a storage device 530, one or more communication units 540, one or more input devices 550, and one or more output devices 560. The processing unit 510 may be an actual or virtual processor and is capable of performing various processes according to a program stored in the memory 520. In a multi-processor system, multiple processing units execute computer executable instructions in parallel to improve the parallel processing capability of the electronic device 500.

[0118] The electronic device 500 typically includes a plurality of computer storage media. Such media may be any accessible media that is accessible to the electronic device 500, including but not limited to volatile and non-volatile media, removable and non-removable media. The memory 520 may be a volatile memory (e.g., registers, caches, random access memory (RAM)), a non-volatile memory (e.g., a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), flash memory), or some combination thereof. The storage device 530 may be a removable or non-removable medium, and may include a machine-readable medium, such as a flash drive, a disk, or any other medium, which may be capable of being used to store information and / or data and may be accessed within the electronic device 500.

[0119] The electronic device 500 may further include additional removable / non-removable, volatile / non-volatile storage media. Figure 5 As shown in , a disk drive for reading or writing from a removable, non-volatile disk (e.g., a "floppy disk") and an optical drive for reading or writing from a removable, non-volatile optical disk may be provided. In these cases, each drive may be connected to the bus (not shown) by one or more data media interfaces. The memory 520 may include a computer program product 525 having one or more program modules that are configured to perform various methods or actions of various embodiments of the present disclosure.

[0120] The communication unit 540 implements communication with other electronic devices through a communication medium. Additionally, the functions of the components of the electronic device 500 can be implemented in a single computing cluster or multiple computing machines that can communicate through a communication connection. Therefore, the electronic device 500 can operate in a networked environment using a logical connection with one or more other servers, a network personal computer (PC), or another network node.

[0121] The input device 550 may be one or more input devices, such as a mouse, a keyboard, a tracking ball, etc. The output device 560 may be one or more output devices, such as a display, a speaker, a printer, etc. The electronic device 500 may also communicate with one or more external devices (not shown) through the communication unit 540 as needed, such as a storage device, a display device, etc., communicate with one or more devices that allow a user to interact with the electronic device 500, or communicate with any device that allows the electronic device 500 to communicate with one or more other electronic devices (e.g., a network card, a modem, etc.). Such communication may be performed via an input / output (I / O) interface (not shown).

[0122] According to an exemplary implementation of the present disclosure, a computer-readable storage medium is provided, on which computer-executable instructions are stored, wherein the computer-executable instructions are executed by a processor to implement the method described above. According to an exemplary implementation of the present disclosure, a computer program product is also provided, which is tangibly stored on a non-transitory computer-readable medium and includes computer-executable instructions, and the computer-executable instructions are executed by a processor to implement the method described above.

[0123] Various aspects of the present disclosure are described herein with reference to the flowcharts and / or block diagrams of the methods, devices, equipment, and computer program products implemented according to the present disclosure. It should be understood that each box in the flowchart and / or block diagram and the combination of each box in the flowchart and / or block diagram can be implemented by computer-readable program instructions.

[0124] These computer-readable program instructions can be provided to a processing unit of a general-purpose computer, a special-purpose computer, or other programmable data processing device, thereby producing a machine, so that when these instructions are executed by the processing unit of the computer or other programmable data processing device, a device that implements the functions / actions specified in one or more boxes in the flowchart and / or block diagram is generated. These computer-readable program instructions can also be stored in a computer-readable storage medium, and these instructions cause the computer, programmable data processing device, and / or other equipment to work in a specific manner, so that the computer-readable medium storing the instructions includes a manufactured product, which includes instructions for implementing various aspects of the functions / actions specified in one or more boxes in the flowchart and / or block diagram.

[0125] Computer-readable program instructions can be loaded onto a computer, other programmable data processing apparatus, or other device so that a series of operational steps are performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, so that the instructions executed on the computer, other programmable data processing apparatus, or other device implement the functions / actions specified in one or more boxes in the flowchart and / or block diagram.

[0126] The flow chart and block diagram in the accompanying drawings show the possible architecture, function and operation of the system, method and computer program product according to multiple implementations of the present disclosure. In this regard, each square box in the flow chart or block diagram can represent a part of a module, program segment or instruction, and a part of a module, program segment or instruction includes one or more executable instructions for realizing the logical function of the specification. In some implementations as replacements, the function marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two continuous square boxes can actually be executed substantially in parallel, and they can sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be realized by a special hardware-based system that performs the function or action of the specification, or can be realized by a combination of special hardware and computer instructions.

[0127] The above descriptions of various implementations of the present disclosure are exemplary, non-exhaustive, and not limited to the disclosed implementations. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described implementations. The selection of terms used herein is intended to best explain the principles of the implementations, practical applications, or improvements to the technology in the market, or to enable other persons of ordinary skill in the art to understand the various implementations disclosed herein.

Claims

1. A method for interface interaction, comprising: In an interface associated with a first user and a second user, presenting an interaction indicator, wherein a state of the interaction indicator is determined based on a historical interaction between the first user and the second user; In response to the interaction indicator being in the first state, presenting reminder information associated with the first event in the interface; as well as In response to the first event being completed collaboratively by the first user and the second user, the interaction identifier is updated from the first state to the second state, wherein the interaction identifier is also configured to be updated from the first state to the second state in response to the following condition being met: the first user and the second user both collaborate to complete the second event in each time period of multiple time periods. The method according to claim 1 , wherein the first event is a non-periodic event and the second event is a periodic event. 3 . The method of claim 1 , wherein the first event is associated with a first application and the second event is associated with a second application different from the first application. The method according to claim 3 , wherein the first event indicates an interactive operation between the first user and the second user in the first application.

5. The method according to claim 3, wherein presenting reminder information associated with the first event in the interface comprises: First reminder information associated with the first event is presented in a first interface of the first application.

6. The method according to claim 5, wherein presenting first reminder information associated with the first event in the first interface of the first application comprises: In response to a first operation on second reminder information presented on a second interface of a second application, presenting the first interface of the first application, wherein the second reminder information is associated with the first event; as well as The first reminder information is presented in the first interface.

7. The method according to claim 5, wherein the first interface is a first conversation interface between the first user and the second user, and the method further comprises: In response to a second operation on the first reminder information presented on the first interface, a first message is sent in the first conversation interface. The method according to claim 7 , wherein the first message is associated with the interaction identifier.

9. The method according to claim 7, further comprising: In response to the first message being sent, presenting third reminder information in the first conversation interface; as well as In response to a third operation on the third reminder information, a second message is sent in the first conversation interface.

10. The method according to claim 9, further comprising: Triggering presentation of the second message in a second conversation interface of the second application, where the second conversation interface is associated with the first user and the second user, and the second message includes an access entry corresponding to the first application.

11. The method according to claim 3, wherein presenting reminder information associated with the first event in the interface comprises: Second reminder information associated with the first event is presented in a second interface of the second application.

12. The method according to claim 11, further comprising: In response to a first operation on the second reminder information, presentation of a first interface of the first application is triggered, where the first interface is associated with completion of the first event.

13. The method according to claim 1, wherein presenting reminder information associated with the first event in the interface comprises: While the interactive identifier is in the first state, the reminder information associated with the first event is periodically presented in the interface.

14. The method according to claim 1, wherein the interaction identifier is associated with a virtual object, and the virtual object is associated with the first user and the second user, and the method further comprises: A visual representation of the virtual object is presented in the interface, wherein the visual representation is determined based on a current state of the interaction indicator.

15. A device for interface interaction, comprising: A first presentation module is configured to present an interaction indicator in an interface associated with a first user and a second user, wherein a state of the interaction indicator is determined based on a historical interaction between the first user and the second user; A second presentation module is configured to present reminder information associated with the first event in the interface in response to the interaction indicator being in the first state; as well as An update module is configured to update the interaction identifier from the first state to the second state in response to the first event being completed collaboratively by the first user and the second user, wherein the interaction identifier is also configured to update from the first state to the second state in response to the following condition being met: the first user and the second user both collaborate to complete the second event in each time period of multiple time periods.

16. An electronic device, comprising: at least one processing unit; as well as At least one memory, the at least one memory being coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit, the instructions causing the electronic device to perform the method according to any one of claims 1 to 14 when executed by the at least one processing unit.

17. A computer-readable storage medium having a computer program stored thereon, wherein the computer program can be executed by a processor to implement the method according to any one of claims 1 to 14.

Images