CN112688856A

CN112688856A - Method and device for releasing friend relationship

Info

Publication number: CN112688856A
Application number: CN202011441498.7A
Authority: CN
Inventors: 陈大年; 姚莲; 文潇; 屠小英; 朱聪
Original assignee: Shanghai Zhangmen Science and Technology Co Ltd
Current assignee: Shanghai Zhangmen Science and Technology Co Ltd
Priority date: 2020-12-11
Filing date: 2020-12-11
Publication date: 2021-04-20
Anticipated expiration: 2040-12-11
Also published as: CN112688856B; WO2022121524A1

Abstract

The application aims to provide a method for releasing friend relationship, which comprises the following steps: responding to a friend relation establishment event between a first user and a second user, and starting a timer aiming at the friend relation; before the timer reaches a timing duration corresponding to the timer, responding to a session interaction event corresponding to a session between the first user and the second user, and terminating the timer; otherwise, if the timer reaches the timing duration corresponding to the timer, the session is cancelled and/or the friend relationship is released. According to the method and the device, when any conversation interaction event does not occur after the friend relationship is established between the two users, the conversation between the two users is automatically hidden and/or the friend relationship between the two users is released, so that the social application interface of the users is enabled to be cleaner, the social efficiency and social experience of the users can be greatly improved, and the safety of communication between the users can be guaranteed.

Description

Method and device for releasing friend relationship

Technical Field

The present application relates to the field of communications, and in particular, to a technique for releasing a friend relationship.

Background

With the development of the times, the mobile terminal is more and more widely used, the social range of people is greatly expanded, people start to more and more use the social application on the mobile terminal to communicate with other people, and a user can communicate with friends anytime and anywhere through the social application. In social applications, once a friend relationship between two users is established, a user can only manually release the friend relationship, otherwise, the friend relationship will be maintained all the time.

Disclosure of Invention

An object of the present application is to provide a method and an apparatus for releasing a friend relationship.

According to an aspect of the present application, there is provided a method for releasing a friend relationship, the method comprising:

responding to a friend relation establishment event between a first user and a second user, and starting a timer aiming at the friend relation;

before the timer reaches a timing duration corresponding to the timer, responding to a session interaction event corresponding to a session between the first user and the second user, and terminating the timer; otherwise, if the timer reaches the timing duration corresponding to the timer, the session is cancelled and/or the friend relationship is released.

According to an aspect of the present application, there is provided a first device for releasing a buddy relationship, the device including:

the one-to-one module is used for responding to a friend relationship establishment event between a first user and a second user and starting a timer aiming at the friend relationship;

a second module, configured to respond to a session interaction event corresponding to a session between the first user and the second user before the timer reaches a timing duration corresponding to the timer, and terminate the timer; otherwise, if the timer reaches the timing duration corresponding to the timer, the session is cancelled and/or the friend relationship is released.

According to an aspect of the present application, there is provided an apparatus for releasing a buddy relationship, wherein the apparatus includes:

a processor; and

a memory arranged to store computer executable instructions that, when executed, cause the processor to:

According to one aspect of the application, there is provided a computer-readable medium storing instructions that, when executed, cause a system to:

Compared with the prior art, the method and the device have the advantages that the timer aiming at the friend relationship is started in response to the friend relationship establishment event between the first user and the second user, the timer is stopped in response to the session interaction event corresponding to the session between the first user and the second user before the timer reaches the timing duration corresponding to the timer, otherwise, if the timer reaches the timing duration corresponding to the timer, the session is cancelled, and/or the friend relationship is relieved, so that the session between the two users can be automatically hidden and/or the friend relationship between the two users can be automatically relieved when any session interaction event does not occur after the friend relationship is established between the two users after expiration, the social application interface of the users can be enabled to be more fresh, and the social efficiency and the social experience of the users can be greatly improved, and the safety of interaction between users can be guaranteed.

Drawings

Other features, objects and advantages of the present application will become more apparent upon reading of the following detailed description of non-limiting embodiments thereof, made with reference to the accompanying drawings in which:

fig. 1 is a flowchart illustrating a method for deleting a buddy application according to an embodiment of the present application;

fig. 2 is a diagram illustrating a first user equipment structure for deleting a friend application according to an embodiment of the present application;

FIG. 3 illustrates an exemplary system that can be used to implement the various embodiments described in this application.

The same or similar reference numbers in the drawings identify the same or similar elements.

Detailed Description

The present application is described in further detail below with reference to the attached figures.

In a typical configuration of the present application, the terminal, the device serving the network, and the trusted party each include one or more processors (e.g., Central Processing Units (CPUs)), input/output interfaces, network interfaces, and memory.

The Memory may include forms of volatile Memory, Random Access Memory (RAM), and/or non-volatile Memory in a computer-readable medium, such as Read Only Memory (ROM) or Flash Memory. Memory is an example of a computer-readable medium.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, Phase-Change Memory (PCM), Programmable Random Access Memory (PRAM), Static Random-Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), electrically Erasable Programmable Read-Only Memory (EEPROM), flash Memory or other Memory technology, Compact Disc Read-Only Memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device.

The device referred to in this application includes, but is not limited to, a user device, a network device, or a device formed by integrating a user device and a network device through a network. The user equipment includes, but is not limited to, any mobile electronic product, such as a smart phone, a tablet computer, etc., capable of performing human-computer interaction with a user (e.g., human-computer interaction through a touch panel), and the mobile electronic product may employ any operating system, such as an Android operating system, an iOS operating system, etc. The network Device includes an electronic Device capable of automatically performing numerical calculation and information processing according to a preset or stored instruction, and the hardware includes, but is not limited to, a microprocessor, an Application Specific Integrated Circuit (ASIC), a Programmable Logic Device (PLD), a Field Programmable Gate Array (FPGA), a Digital Signal Processor (DSP), an embedded Device, and the like. The network device includes but is not limited to a computer, a network host, a single network server, a plurality of network server sets or a cloud of a plurality of servers; here, the Cloud is composed of a large number of computers or web servers based on Cloud Computing (Cloud Computing), which is a kind of distributed Computing, one virtual supercomputer consisting of a collection of loosely coupled computers. Including, but not limited to, the internet, a wide area network, a metropolitan area network, a local area network, a VPN network, a wireless Ad Hoc network (Ad Hoc network), etc. Preferably, the device may also be a program running on the user device, the network device, or a device formed by integrating the user device and the network device, the touch terminal, or the network device and the touch terminal through a network.

Of course, those skilled in the art will appreciate that the foregoing is by way of example only, and that other existing or future devices, which may be suitable for use in the present application, are also encompassed within the scope of the present application and are hereby incorporated by reference.

In the description of the present application, "a plurality" means two or more unless specifically limited otherwise.

Fig. 1 is a flowchart illustrating a method for releasing a buddy relationship according to an embodiment of the present application, where the method includes steps S11 and S12. In step S11, the first device starts a timer for the friendship in response to a friendship establishment event between the first user and the second user; in step S12, the first device terminates the timer in response to a session interaction event corresponding to the session between the first user and the second user before the timer reaches a timing duration corresponding to the timer; otherwise, if the timer reaches the timing duration corresponding to the timer, the session is cancelled and/or the friend relationship is released.

In step S11, the first device starts a timer for the friendship in response to a friendship establishment event between the first user and the second user. In some embodiments, the first device may be a network device (server), or may be a first user device used by a first user, or may be a second user device used by a second user. In some embodiments, the first user or the second user actively initiates a friend application requesting to add the other party as a friend, and triggers the friend relationship establishment event after the other party confirms to pass. In some embodiments, the server may also automatically initiate a friend application requesting to add a friend who is a friend to the first user or the second user, and trigger a friend relationship establishment event after the confirmation of the friend passes. In some embodiments, the first user may also actively initiate a friend application requesting to add the second user as a friend, the second user also actively initiates a friend application requesting to add the second user as a friend, and after any party confirms that the friend relationship is passed, the friend relationship establishing event is triggered. In some embodiments, the first user may also actively initiate a request to add a friend application of which the second user is a friend, and the server automatically initiates a request to add a friend application of which the first user is a friend for the second user, and triggers a friend relationship establishment event. In some embodiments, if the first device is a server, a timer for the friend relationship is started in the server, and if the first device is a first user device or a second user device, the timer for the friend relationship is started locally at the first user device or locally at the second user device, at this time, the timer on the first user device and the timer on the second user device may be synchronized, or may be independent of each other. In some embodiments, if the first device is a server, the timing duration of the timer is configured by the server, and a maintainer or a user of the server may modify the timing duration as needed, and if the first device is a first user device or a second user device, the timing duration of the timer may be configured locally by the first user device or locally by the second user device, and the first user or the second user may modify the timing duration according to their own needs, or the timing duration of the timer may be configured by the server and provided to the first user device or the second user device, and the maintainer or the user of the server may modify the timing duration as needed and provide the updated timing duration to the first user device or the second user device.

In step S12, the first device terminates the timer in response to a session interaction event corresponding to the session between the first user and the second user before the timer reaches a timing duration corresponding to the timer; otherwise, if the timer reaches the timing duration corresponding to the timer, the session is cancelled and/or the friend relationship is released. In some embodiments, before the timer reaches the timing duration, if a session interaction event occurs in the session between the first user and the second user, the timer is terminated and deleted. In some embodiments, session interaction events include, but are not limited to, any party in the session having sent a session message in the session, having initiated a voice or video call, having sent location information, having initiated a shared real-time location, having sent a red envelope, having initiated a transfer of money, having sent a file, business card, card ticket, and other various interaction information. In some embodiments, if the timer reaches the timing duration, the timer is deleted, and the session between the first user and the second user is cancelled or the friend relationship between the first user and the second user is cancelled on the session list page or the historical session page, or the session is cancelled and the friend relationship is cancelled. In some embodiments, if the first device is a first user device or a second user device, the presence session may be canceled directly, the friend relationship cancellation may need to send a friend cancellation request to the server, and the friend relationship is cancelled by the server, if the first device is the server, the friend relationship may be canceled directly, the presence session cancellation may need to send indication information for indicating cancellation of the presence session to the first user device or the second user device, and the presence session is cancelled by the first user device or the second user device. In some embodiments, after the first user or the second user cancels presentation of the session between the first user and the second user on the session list page or the historical session page, the session between the first user and the second user may be opened by searching for the first user or the second user on the contact page or the address book page, and the corresponding session page is entered. According to the method and the device, when any conversation interaction event does not occur after the friend relationship is established between the two users, the conversation between the two users is automatically hidden and/or the friend relationship between the two users is released, so that the social application interface of the users is enabled to be cleaner, the social efficiency and social experience of the users can be greatly improved, and the safety of communication between the users can be guaranteed.

In some embodiments, the timing length comprises a first timing length and a second timing length, the first timing length being less than the second timing length; wherein the step S12 includes: the first device responds to a session interaction event corresponding to a session between the first user and the second user before the timer reaches the first timing length, and terminates the timer; otherwise, if the timer reaches the first timing duration, canceling the presentation of the session and continuing timing; before the timer reaches the second timing duration, responding to a session interaction event corresponding to the session between the first user and the second user, and terminating the timer; otherwise, if the timer reaches the second timing duration, the friend relationship is released. In some embodiments, the timing duration includes a first timing duration and a second timing duration, the first timing duration is less than the second timing duration, before the timer reaches the first timing duration, if a session interaction event occurs in a session between the first user and the second user, the timer is terminated and deleted, otherwise, when the timer reaches the first timing duration, the presentation of the session between the first user and the second user is cancelled on a session list page or a historical session page and the timing is continued, before the timer reaches the second timing duration, if a session interaction event occurs in the session between the first user and the second user, the timer is terminated and deleted, otherwise, when the timer reaches the first timing duration, the timer is deleted, and the friend relationship between the first user and the second user is released.

In some embodiments, the step S11 includes step S111 (not shown). In step S111, the first device responds to a friendship establishment event between the first user and the second user, detects whether a channel source type corresponding to the friendship establishment event is a predetermined channel source type, and starts a timer for the friendship if the channel source type is the predetermined channel source type. In some embodiments, it is required to detect whether a channel source type corresponding to the friendship establishment event is a predetermined channel source type, if so, a timer for the friendship between the first user and the second user is started, otherwise, the timer is not started. In some embodiments, the channel source type corresponding to the friendship establishment event is used to represent the friendship established by the first user and the second user through what channel source, where the channel source includes but is not limited to a stranger channel source and an acquaintance channel source, the stranger channel means that both sides do not know when establishing the friendship, and the acquaintance channel means that both sides already know when establishing the friendship rest, for example, the first user is the second user who sees in a "nearby people" channel, and then sends an add friend request to the second user, where the "nearby people" channel is a stranger channel, and for example, the first user is the second user who sees in a mobile phone contact list channel and then sends an add friend request to the second user, where the mobile phone contact list channel is an acquaintance channel, because of the friendship established through the acquaintance channel, generally, the timer has reserved value and meaning, so that the corresponding timer cannot be started for the friend relationship established through the acquaintance channel, and only the corresponding timer can be started for the friend relationship established through the stranger channel.

In some embodiments, the predetermined channel source types include, but are not limited to:

1) automatic initiation of a friendship establishment event between two users by a network device

In some embodiments, the server automatically helps the first user or the second user initiate a friend application requesting to add the second user or the first user as a friend, and after the other side confirms that the friend relationship is established between the first user and the second user. For example, the server automatically determines one or more users recommended to the second user, the one or more users including the first user, and then automatically initiates a friend application requesting to add the one or more users as friends to the second user.

2) Event establishment by a user by finding friends nearby with other users

In some embodiments, the first user sees the second user through a "people nearby" channel, then sends a friend adding request to the second user, and after the second user confirms that the friend relationship is established between the first user and the second user.

3) The user initiates a friend relationship establishment event with other users through a stranger friend adding channel

In some embodiments, the first user sees the second user through any other stranger friend-adding channel (e.g., a "hot chat" channel, a "message tree" channel, a "look-to-eye" channel, etc.) other than the "nearby people" channel, and then issues an add friend request to the second user, and after the second user confirms that the second user passes, a friend relationship is established between the first user and the second user.

In some embodiments, the channel source types corresponding to the friend relationship establishing event include a first channel source type used by the first user to request to add the second user as a friend and a second channel source type used by the second user to request to add the first user as a friend, where the first channel source type is different from the second channel source type; wherein, if the first device is a first user device used by the first user, the step S111 includes: responding to a friend relationship establishment event between the first user and the second user by the first equipment, detecting whether the first channel source type is a preset channel source type, and if so, starting a first timer corresponding to the first user and aiming at the friend relationship; if the first device is a second user device used by the second user, the step S111 includes: responding to a friend relationship establishment event between the first user and the second user by the first equipment, detecting whether the second channel source type is a preset channel source type, and if so, starting a timer corresponding to the second user and aiming at the friend relationship; if the first device is a network device, the step S111 includes: responding to a friend relationship establishment event between the first user and the second user by the first equipment, detecting whether the first channel source type and the second channel source type are preset channel source types, and starting a timer aiming at the friend relationship if the first channel source type and the second channel source type are both the preset channel source types; if only one of the two is the predetermined channel source type, only starting the timer corresponding to the user associated with the one, and aiming at the friend relationship, so as to cancel the presentation of the session only when the timer reaches the time duration corresponding to the timer, or not executing any operation. In some embodiments, if the first channel source type used by the first user to request addition of the second user as a friend is different from the second channel source type used by the second user to request addition of the first user as a friend, for each of the first user and the second user, if the first device is the first user device or the second user device, it is required to separately determine whether the channel source type corresponding to the user is the predetermined channel source type, and if so, a timer corresponding to the user and aiming at the friend relationship between the first user and the second user is started on the first user device or the second user device. For example, the first user is a second user who sees the second user through a "nearby person" channel, and then sends a request for adding a friend to the second user, the "nearby person" channel is a stranger channel, the second user is a first user who sees the first user through a mobile phone address book channel, and then sends a request for adding a friend to the first user, the mobile phone address book channel is an acquaintance channel, after any one of the first user and the second user confirms the request for adding a friend sent by the other user, the two users establish a friend relationship, the channel source type corresponding to the first user is different from the channel source type corresponding to the second user, for the first user, the second user is a friend who is added through the stranger channel, and for the second user, the first user is a friend who is added through the acquaintance channel. In some embodiments, if the first device is a server, it is required to comprehensively determine whether the channel source type corresponding to the first user and the channel source type corresponding to the second user satisfy the predetermined channel source type, if both the channel source type and the channel source type satisfy, a timer for the friend relationship between the first user and the second user is normally started, if both the channel source type and the channel source type do not satisfy, the timer is not started, no operation is subsequently performed, if only one of the channel source type and the channel source type satisfies, the timer for the friend relationship corresponding to the user associated with the one of the channel source and the channel source type corresponding to the second user is also started, the timer for the friend relationship corresponding to the user associated with the other of the channel source and the channel source type corresponding to the second user is not started, the started timer will only trigger to cancel presentation of the session between the first user and the second user when the time reaches the corresponding timing duration, without triggering the release of the friend relationship between the first user and the second user.

In some embodiments, if yes, the starting of the first timer corresponding to the first user for the friend relationship includes: if the friend relationship information is the first friend relationship information, the network equipment sends a timer starting request to the network equipment, receives instruction information fed back by the network equipment aiming at the timer starting request, and starts a first timer corresponding to the first user aiming at the friend relationship if the instruction information indicates that the timer is allowed to be started, wherein the network equipment determines the instruction information by detecting whether the second channel source type is a preset channel source type, the instruction information indicates that the first timer is started if the second channel source type is the preset channel source type, and otherwise, the instruction information indicates that the first timer is not started. In some embodiments, the first device is a first user device, and if a first channel source type corresponding to the first user meets a predetermined channel source type, the first user device queries the server whether to start a timer corresponding to the first user on the first user device, and the server detects whether a second channel source type corresponding to the second user also meets the predetermined channel source type, and if so, the server instructs the first user device to start the first timer, otherwise, the server instructs the first user device not to start the first timer.

In some embodiments, if yes, starting a second timer corresponding to the second user and aiming at the friend relationship includes: if the friend relationship is the first channel source type, the network device determines the instruction information by detecting whether the first channel source type is a preset channel source type, if the first channel source type is the preset channel source type, the instruction information indicates to start the second timer, and if the friend relationship is the second channel source type, the instruction information indicates not to start the second timer. In some embodiments, the first device is a second user device, and if a second channel source type corresponding to a second user meets a predetermined channel source type, the second user device queries the server whether to start a timer corresponding to the second user on the second user device, and the server detects whether a first channel source type corresponding to the first user also meets the predetermined channel source type, if so, the server instructs the second user device to start the second timer, otherwise, the server instructs the second user device not to start the second timer.

In some embodiments, the step S111 includes: the method comprises the steps that a first device responds to a friend relationship establishing event between a first user and a second user, whether a friend application source type corresponding to the friend relationship establishing event is a preset friend application source type or not is detected, if yes, whether an expired automatic processing function is started or not is judged according to friend relationship configuration information corresponding to the friend relationship, and if yes, a timer aiming at the friend relationship is started. In some embodiments, it is further required to determine whether the expired automatic processing function is currently started according to the friend relationship configuration information between the first user and the second user, and only when the state currently indicated by the friend relationship configuration information is that the expired automatic processing function is started, the timer for the friend relationship is started. In some embodiments, the friend relationship configuration information may be maintained locally at the first user equipment or locally at the second user equipment, and the first user or the second user may change the state currently indicated by the friend relationship configuration information according to the own needs. In some embodiments, the friend relationship configuration information may be maintained in a server, and a maintenance person or a user of the server may change a state indicated by the friend relationship configuration information as needed. In some embodiments, the first user device or the second user device may maintain one common buddy relationship configuration information for a plurality of buddy relationships between the first user or the second user and different buddies thereof, or may maintain one buddy relationship configuration information for each buddy relationship separately. In some embodiments, the server may maintain a common friend relationship configuration information for the first user and the second user, or may maintain a friend relationship configuration information for each user separately, where the friend relationship configuration information is applicable to a plurality of friend relationships between the first user or the second user and different friends thereof.

In some embodiments, the buddy relationship configuration information includes the timing duration. In some embodiments, if the first user device or the second user device maintains the friend relationship configuration information, the first user or the second user may change the timing duration in the friend relationship configuration information according to the need of the first user or the second user, and if the server maintains the friend relationship configuration information, the maintenance person or the user of the server may change the timing duration in the friend relationship configuration information according to the need.

In some embodiments, the method further comprises: the first device determines the friend relationship configuration information based on at least one of: the channel source type; the number of common friends of the first user and the second user; and the historical conversation interaction frequency information of the first user and the historical conversation interaction frequency information of the second user. In some embodiments, the friend relationship configuration information suitable for the friend relationship may be determined according to a channel source type corresponding to the friend relationship establishing event. In some embodiments, the friend relationship configuration information suitable for the friend relationship may be further determined according to the number of common friends of the first user and the second user, for example, the greater the number of common friends is, the longer the timing duration in the friend relationship configuration information is. In some embodiments, the friend relationship configuration information suitable for the friend relationship may be further determined according to the historical session interaction frequency information of the first user and the other users and the historical session interaction frequency information of the second user and the other users, where the frequency information includes, but is not limited to, frequency information (for example, how many time intervals the first user or the second user will perform session interaction operations on average) and frequency information (for example, how many time intervals the first user or the second user will perform session interaction operations on average per day), for example, if the historical session interaction frequency of the first user is high, the timing duration in the friend relationship configuration information corresponding to the first user is short, and if the historical session interaction frequency of the second user is low, the timing duration in the friend relationship configuration information corresponding to the second user is long.

In some embodiments, the method further comprises: the first device terminates the timer in response to a first switching event that switches the status indicated by the buddy relationship configuration information from turning on an expired automatic processing function to turning off the expired automatic processing function. In some embodiments, if the first device is a first user device or a second user device, the first switching event may be that the first user or the second user switches the state indicated by the buddy relationship configuration from the open expired automatic processing function to the close expired automatic processing function, or, if the first device is a server, the first switching event may also be that a maintainer or a user of the server switches the state indicated by the buddy relationship configuration from the open expired automatic processing function to the close expired automatic processing function.

In some embodiments, the method further comprises: and the first equipment responds to a second switching event of switching the state indicated by the friend relationship configuration information from closing the expired automatic processing function to opening the expired automatic processing function, and restarts the timer if the session does not generate any historical session interaction event and the timer is not timed to end. In some embodiments, if the first device is a first user device or a second user device, the second switching event may be that the first user or the second user switches the state indicated by the buddy relationship configuration from closing the expired automatic processing function to opening the expired automatic processing function, or, if the first device is a server, the second switching event may also be that a maintainer or a user of the server switches the state indicated by the buddy relationship configuration from closing the expired automatic processing function to opening the expired automatic processing function. In some embodiments, restarting the timer may be restarting the timer at the current time according to the start time, or resetting the timer and restarting the timer according to the start time of 0.

In some embodiments, the restarting the timer includes, but is not limited to: restarting the timer, wherein the starting time of the timer is the current time; the timer is reset and restarted. In some embodiments, the start time of the timer may be set to the current time from which the timer is restarted. In some embodiments, the timer may be reset, the start time of the timer reset to 0, and the timer restarted from 0.

In some embodiments, the method further comprises: and the first equipment responds to a timing duration change event corresponding to the friend relationship configuration information, calculates whether the absolute value of the time interval between the starting time corresponding to the timer and the current time is less than or equal to the changed timing duration, if so, cancels the presentation of the session and/or relieves the friend relationship, and otherwise, continuously times the timer according to the changed timing duration. In some embodiments, the event of changing the timing duration may be that the first user or the second user changes the timing duration in the friend relationship configuration information, or may also be that a maintenance person or a user of the server changes the timing duration in the friend relationship configuration information. In some embodiments, the timing duration of the timer is set to the modified timing duration, and the timer continues to count.

In some embodiments, the method further comprises: and the first equipment responds to the timing duration change event corresponding to the friend relationship configuration information, resets the timer and restarts the timer according to the changed timing duration. In some embodiments, the timer is reset, the start time of the timer is reset to 0, the timing duration of the timer is set to the modified timing duration, and then the timer is restarted from 0.

In some embodiments, if the first device is a first user device used by a first user or a second user device used by a second user; wherein the method further comprises: the method comprises the steps that a first device responds to an upgrade completion event for upgrading from a historical version to a current version, if no historical session interaction event is generated in a session between a first user and a second user, whether a time interval absolute value between a friend relationship establishment time corresponding to a friend relationship between the first user and the second user and the current time is larger than or equal to a timing duration or not is detected, if yes, the session is cancelled, and/or the friend relationship is cancelled. In some embodiments, if the first device is a first user device or a second user device, in response to an upgrade complete event for upgrading from the historical version to the current version, the historical version does not include the expired automatic processing function, and the current version includes the expired automatic processing function. In some embodiments, it is required to determine whether the session between the first user and the second user generates the historical session interaction event, the historical session interaction record of the first user or the second user may be obtained locally at the first user device or the second user device, or the historical session interaction record of the first user or the second user may be requested from the server, and then it may be determined whether the session between the first user and the second user generates the historical session interaction event according to the historical session interaction record. In some embodiments, the time for establishing the friend relationship corresponding to the friend relationship between the first user and the second user needs to be obtained, and may be directly obtained from the local of the first user device or the local of the second user device, or may be obtained by requesting the server.

In some embodiments, the method further comprises: and if the absolute value of the time interval between the friend relationship establishing time corresponding to the session and the current time is less than the timing duration, the first device starts a timer aiming at the friend relationship, wherein the starting time of the timer is the current time. In some embodiments, the start time of the timer for the buddy relationship may be set as the current time, the timing duration of the timer is still the timing duration in the buddy relationship configuration information, and then the timer is started. In some embodiments, the timing duration of the timer may also be set to be a difference between the timing duration in the buddy relationship configuration information and the current time, the starting time of the timer is 0, and then the timer is started.

In some embodiments, the method further comprises: presenting the conversation through a first presentation mode by the first equipment in the timing process of the timer, wherein the first presentation mode is different from a second presentation mode corresponding to the conversation without starting the timer; and updating and presenting the session through the second presentation mode in response to the timing ending event of the timer. In some embodiments, during the counting of the timer, the session is presented on a session list page or a historical session page through a first presentation mode, wherein the first presentation mode is different from a second presentation mode used by the session list page or the historical session page to present other sessions which do not start the timer. For example, the first presentation mode may be to highlight the session, or may be to present specific text or specific icons, animations, etc. in a display area of the session. In some embodiments, after the timer expires, the presentation manner of the session in the session list page or the historical session page is adjusted from the first presentation manner to the second presentation manner.

In some embodiments, the first presenting manner includes presenting first countdown information determined according to the current time and the timing duration in a display area of the session, wherein the first countdown information is updated in real time based on the current time. In some embodiments, if the timing duration is of a time point type (e.g., 24 days at 30 months and 1 month), then first countdown information may be determined according to the current time and the timing duration, and the first countdown information is used for indicating how much time the current time has left from the end of the timer. In some embodiments, if the timing duration is a time period type (e.g., 24 hours), the first countdown information may be determined according to the start time of the timer (i.e., the buddy relationship establishment time corresponding to the buddy relationship), the current time, and the timing duration. In some embodiments, the first countdown information may include only text information, or may include both text information and icons, animations, and the like.

In some embodiments, the method further comprises: in the timing process of the timer, responding to an event that the first user or the second user enters a session page corresponding to the session, the first device presents second countdown information determined according to the current time and the timing duration in the session page, wherein the second countdown information is updated in real time based on the current time; canceling presentation of the second countdown information in the session page in response to a timing expiration event of the timer. In some embodiments, in the timing process of the timer, if the first user or the second user enters the session page corresponding to the session, the second countdown information is presented in the session page, where the second countdown information is similar to the first countdown information and is not described herein again. In some embodiments, after the timer expires, the second countdown information is dismissed from being presented in the session page.

In some embodiments, said releasing said buddy relationship comprises: and releasing the friend relationship, and presenting release indication information about the friend relationship to the first user and/or the second user. In some embodiments, the dismissal indication information may include identification information of the first user or identification information of the second user. In some embodiments, the release indication information is used to alert the first user or the second user that the system has automatically released his friend relationship with the other party. In some embodiments, if the first device is a first user device or a second user device, the cancellation indication information may be directly presented, and if the first device is a server, the server needs to send the cancellation indication information to the first user device or the second user device for display.

In some embodiments, the releasing the friend relationship, presenting release indication information about the friend relationship to the first user and/or the second user, includes: and releasing the friend relationship, presenting release indication information about the friend relationship to the first user and/or the second user, detecting whether the first user and the second user present a session page corresponding to the session or not, and if so, automatically exiting the session page. In some embodiments, when the friend relationship is released, if the first user equipment or the second user equipment is currently presenting the session page corresponding to the session, the first user equipment or the second user equipment may automatically quit the session. In some embodiments, if the first device is a first user device or a second user device, it may be directly detected whether a session page corresponding to the session is currently presented, if the first device is a server, the server may send the release indication information to the first user device or the second user device for presentation, and after receiving the release indication information, the first user device or the second user device may detect whether the session page corresponding to the session is currently presented.

In some embodiments, if the first device is a first user device used by a first user or a second user device used by a second user, the method further includes: in the timing process of the timer, in response to an opening operation performed by the first user or the second user for a session page corresponding to the session, performing at least one of the following operations: resetting and restarting the timer; and changing the corresponding timing duration of the timer, wherein the changed timing duration is greater than the timing duration before the change. In some embodiments, in the timing process of the timer, if the first user or the second user opens a session page corresponding to the session, the timer is reset, the start time of the timer is set to 0, and then the timer is restarted from 0, where the timing duration of the timer remains unchanged. In some embodiments, the timing duration of the timer is modified, the modified timing duration being greater than the timing duration before the modification. In some embodiments, the changed timing duration is positively correlated with the number of times of opening, performed by the first user or the second user, of the session page corresponding to the session in the timing process of the timer, and the changed timing duration is larger as the number of times of opening is larger. In some embodiments, the change in the timing length has a predetermined threshold, and if the changed timing length exceeds the predetermined threshold, the changed timing length is set to the predetermined threshold, and then the change in the timing length is not continued. In some embodiments, each time the timing duration is changed according to a predetermined increase amplitude, the timing duration may be changed according to the same increase amplitude, or the timing duration may be changed according to a different increase amplitude, and the increase amplitude is smaller as the number of times of opening is larger. In some embodiments, if the first device is a server, the first user device or the second user device needs to send an open event of the session page corresponding to the session to the server.

In some embodiments, the de-presenting the session and/or releasing the buddy relationship includes: canceling the presentation of the session, and/or canceling the friend relationship, and recording expired automatic processing information corresponding to the friend relationship, wherein the expired automatic processing information includes at least one of establishment time of the friend relationship, an automatic processing event type corresponding to the friend relationship, processing time corresponding to the automatic processing event, identification information of the first user, identification information of the second user, identification information of the session, and timing duration corresponding to the timer. In some embodiments, a point is made for an event that a presence session is cancelled, or a point is made for an event that a buddy relationship is cancelled, and expired automatic processing information corresponding to the buddy relationship is recorded, where the expired automatic processing information includes, but is not limited to, a time of establishing the buddy relationship, an automatic processing event type corresponding to the buddy relationship (whether a presence session is cancelled or a buddy relationship is cancelled), a processing time corresponding to the automatic processing event, identification information of a first user (e.g., user name information, user ID information, etc.), identification information of a second user, identification information of the session (e.g., session name information, session ID information, etc.), a timing duration of a timer corresponding to the session, and the like. In some embodiments, if the first device is the first user device or the second user device, the recorded expiration automatic processing information corresponding to the friend relationship may be uploaded to the server after the dotting is completed.

In some embodiments, if the first device is a first user device used by the first user or a second user device used by the second user; wherein the method further comprises: and responding to an expired automatic processing information uploading initiating event, and uploading one or more expired automatic processing information corresponding to one or more friend relationships currently recorded by the first equipment to network equipment. In some embodiments, if the first device is a first user device or a second user device, the uploading operation of the expired automatic processing information may be initiated at each start of the social application, or the uploading operation of the expired automatic processing information may be initiated when a time interval from a previous uploading operation reaches or exceeds a predetermined time threshold (for example, 1 day), for example, the uploading operation of the expired automatic processing information is initiated every other day. In some embodiments, when the uploading operation of the expired automatic processing information is performed, one or more expired automatic processing information corresponding to one or more friend relationships of the first user or the second user and one or more historical friends of the first user or the second user, which are recorded currently, are uploaded to the server.

Fig. 2 is a diagram illustrating a structure of a first device for releasing a buddy relationship according to an embodiment of the present application, where the first device includes a one-to-one module 11 and a two-to-one module 12. A one-to-one module 11, configured to respond to a friend relationship establishment event between a first user and a second user, and start a timer for the friend relationship; a second module 12, configured to terminate the timer in response to a session interaction event corresponding to a session between the first user and the second user before the timer times to a timing duration corresponding to the timer; otherwise, if the timer reaches the timing duration corresponding to the timer, the session is cancelled and/or the friend relationship is released.

A module 11, configured to respond to a friendship establishment event between a first user and a second user, and start a timer for the friendship. In some embodiments, the first device may be a network device (server), or may be a first user device used by a first user, or may be a second user device used by a second user. In some embodiments, the first user or the second user actively initiates a friend application requesting to add the other party as a friend, and triggers the friend relationship establishment event after the other party confirms to pass. In some embodiments, the server may also automatically initiate a friend application requesting to add a friend who is a friend to the first user or the second user, and trigger a friend relationship establishment event after the confirmation of the friend passes. In some embodiments, the first user may also actively initiate a friend application requesting to add the second user as a friend, the second user also actively initiates a friend application requesting to add the second user as a friend, and after any party confirms that the friend relationship is passed, the friend relationship establishing event is triggered. In some embodiments, the first user may also actively initiate a request to add a friend application of which the second user is a friend, and the server automatically initiates a request to add a friend application of which the first user is a friend for the second user, and triggers a friend relationship establishment event. In some embodiments, if the first device is a server, a timer for the friend relationship is started in the server, and if the first device is a first user device or a second user device, the timer for the friend relationship is started locally at the first user device or locally at the second user device, at this time, the timer on the first user device and the timer on the second user device may be synchronized, or may be independent of each other. In some embodiments, if the first device is a server, the timing duration of the timer is configured by the server, and a maintainer or a user of the server may modify the timing duration as needed, and if the first device is a first user device or a second user device, the timing duration of the timer may be configured locally by the first user device or locally by the second user device, and the first user or the second user may modify the timing duration according to their own needs, or the timing duration of the timer may be configured by the server and provided to the first user device or the second user device, and the maintainer or the user of the server may modify the timing duration as needed and provide the updated timing duration to the first user device or the second user device.

A second module 12, configured to terminate the timer in response to a session interaction event corresponding to a session between the first user and the second user before the timer times to a timing duration corresponding to the timer; otherwise, if the timer reaches the timing duration corresponding to the timer, the session is cancelled and/or the friend relationship is released. In some embodiments, before the timer reaches the timing duration, if a session interaction event occurs in the session between the first user and the second user, the timer is terminated and deleted. In some embodiments, session interaction events include, but are not limited to, any party in the session having sent a session message in the session, having initiated a voice or video call, having sent location information, having initiated a shared real-time location, having sent a red envelope, having initiated a transfer of money, having sent a file, business card, card ticket, and other various interaction information. In some embodiments, if the timer reaches the timing duration, the timer is deleted, and the session between the first user and the second user is cancelled or the friend relationship between the first user and the second user is cancelled on the session list page or the historical session page, or the session is cancelled and the friend relationship is cancelled. In some embodiments, if the first device is a first user device or a second user device, the presence session may be canceled directly, the friend relationship cancellation may need to send a friend cancellation request to the server, and the friend relationship is cancelled by the server, if the first device is the server, the friend relationship may be canceled directly, the presence session cancellation may need to send indication information for indicating cancellation of the presence session to the first user device or the second user device, and the presence session is cancelled by the first user device or the second user device. In some embodiments, after the first user or the second user cancels presentation of the session between the first user and the second user on the session list page or the historical session page, the session between the first user and the second user may be opened by searching for the first user or the second user on the contact page or the address book page, and the corresponding session page is entered. According to the method and the device, when any conversation interaction event does not occur after the friend relationship is established between the two users, the conversation between the two users is automatically hidden and/or the friend relationship between the two users is released, so that the social application interface of the users is enabled to be cleaner, the social efficiency and social experience of the users can be greatly improved, and the safety of communication between the users can be guaranteed.

In some embodiments, the timing length comprises a first timing length and a second timing length, the first timing length being less than the second timing length; wherein the second module 12 is configured to: before the timer reaches the first timing length, responding to a session interaction event corresponding to a session between the first user and the second user, and terminating the timer; otherwise, if the timer reaches the first timing duration, canceling the presentation of the session and continuing timing; before the timer reaches the second timing duration, responding to a session interaction event corresponding to the session between the first user and the second user, and terminating the timer; otherwise, if the timer reaches the second timing duration, the friend relationship is released. Here, the related operations are the same as or similar to those of the embodiment shown in fig. 1, and therefore are not described again, and are included herein by reference.

In some embodiments, the one-to-one module 11 includes one-to-one module 111 (not shown). A module 111, configured to respond to a friendship establishment event between a first user and a second user, detect whether a channel source type corresponding to the friendship establishment event is a predetermined channel source type, and if so, start a timer for the friendship. Here, the specific implementation manner of one-to-one module 111 is the same as or similar to the embodiment related to step S111 in fig. 1, and therefore, the detailed description is omitted, and the detailed description is incorporated herein by reference.

2) Event establishment by a user by finding friends nearby with other users

Here, the type of the related predetermined channel source is the same as or similar to that of the embodiment shown in fig. 1, and therefore, the description thereof is omitted, and the description thereof is incorporated herein by reference.

In some embodiments, the channel source types corresponding to the friend relationship establishing event include a first channel source type used by the first user to request to add the second user as a friend and a second channel source type used by the second user to request to add the first user as a friend, where the first channel source type is different from the second channel source type; wherein, if the first device is a first user device used by the first user, the one-to-one module 111 is configured to: responding to a friend relationship establishment event between the first user and the second user, detecting whether the first channel source type is a preset channel source type, and if so, starting a first timer corresponding to the first user and aiming at the friend relationship; if the first device is a second user device used by the second user, the one-to-one module 111 is configured to: responding to a friend relationship establishment event between the first user and the second user by the first equipment, detecting whether the second channel source type is a preset channel source type, and if so, starting a timer corresponding to the second user and aiming at the friend relationship; if the first device is a network device, the one-to-one module 111 is configured to: responding to a friend relationship establishing event between the first user and the second user, detecting whether the first channel source type and the second channel source type are preset channel source types, and starting a timer aiming at the friend relationship if the first channel source type and the second channel source type are both the preset channel source types; if only one of the two is the predetermined channel source type, only starting the timer corresponding to the user associated with the one, and aiming at the friend relationship, so as to cancel the presentation of the session only when the timer reaches the time duration corresponding to the timer, or not executing any operation. Here, the related operations are the same as or similar to those of the embodiment shown in fig. 1, and therefore are not described again, and are included herein by reference.

In some embodiments, if yes, the starting of the first timer corresponding to the first user for the friend relationship includes: if the friend relationship information is the first friend relationship information, the network equipment sends a timer starting request to the network equipment, receives instruction information fed back by the network equipment aiming at the timer starting request, and starts a first timer corresponding to the first user aiming at the friend relationship if the instruction information indicates that the timer is allowed to be started, wherein the network equipment determines the instruction information by detecting whether the second channel source type is a preset channel source type, the instruction information indicates that the first timer is started if the second channel source type is the preset channel source type, and otherwise, the instruction information indicates that the first timer is not started. Here, the related operations are the same as or similar to those of the embodiment shown in fig. 1, and therefore are not described again, and are included herein by reference.

In some embodiments, if yes, starting a second timer corresponding to the second user and aiming at the friend relationship includes: if the friend relationship is the first channel source type, the network device determines the instruction information by detecting whether the first channel source type is a preset channel source type, if the first channel source type is the preset channel source type, the instruction information indicates to start the second timer, and if the friend relationship is the second channel source type, the instruction information indicates not to start the second timer. Here, the related operations are the same as or similar to those of the embodiment shown in fig. 1, and therefore are not described again, and are included herein by reference.

In some embodiments, the one-to-one module 111 is configured to: responding to a friend relationship establishing event between a first user and a second user, detecting whether a friend application source type corresponding to the friend relationship establishing event is a preset friend application source type, if so, judging whether an expired automatic processing function is started at present according to friend relationship configuration information corresponding to the friend relationship, and if so, starting a timer aiming at the friend relationship. Here, the related operations are the same as or similar to those of the embodiment shown in fig. 1, and therefore are not described again, and are included herein by reference.

In some embodiments, the buddy relationship configuration information includes the timing duration. Here, the related operations are the same as or similar to those of the embodiment shown in fig. 1, and therefore are not described again, and are included herein by reference.

In some embodiments, the apparatus is further configured to: determining the friend relationship configuration information based on at least one of: the channel source type; the number of common friends of the first user and the second user; and the historical conversation interaction frequency information of the first user and the historical conversation interaction frequency information of the second user. Here, the related operations are the same as or similar to those of the embodiment shown in fig. 1, and therefore are not described again, and are included herein by reference.

In some embodiments, the apparatus is further configured to: and in response to a first switching event that the state indicated by the friend relationship configuration information is switched from the state of starting an expired automatic processing function to the state of closing the expired automatic processing function, terminating the timer. Here, the related operations are the same as or similar to those of the embodiment shown in fig. 1, and therefore are not described again, and are included herein by reference.

In some embodiments, the apparatus is further configured to: and in response to a second switching event of switching the state indicated by the friend relationship configuration information from closing the expired automatic processing function to opening the expired automatic processing function, if the session does not generate any historical session interaction event and the timer is not timed to end, restarting the timer. Here, the related operations are the same as or similar to those of the embodiment shown in fig. 1, and therefore are not described again, and are included herein by reference.

In some embodiments, the restarting the timer includes, but is not limited to: restarting the timer, wherein the starting time of the timer is the current time; the timer is reset and restarted. Here, the related operations are the same as or similar to those of the embodiment shown in fig. 1, and therefore are not described again, and are included herein by reference.

In some embodiments, the apparatus is further configured to: responding to a timing duration change event corresponding to the friend relationship configuration information, calculating whether a time interval absolute value between a starting time corresponding to the timer and the current time is less than or equal to the changed timing duration, if so, canceling the presentation of the session, and/or removing the friend relationship, otherwise, continuing to time the timer according to the changed timing duration. Here, the related operations are the same as or similar to those of the embodiment shown in fig. 1, and therefore are not described again, and are included herein by reference.

In some embodiments, the apparatus is further configured to: and responding to a timing duration change event corresponding to the friend relationship configuration information, resetting the timer and restarting the timer according to the changed timing duration. Here, the related operations are the same as or similar to those of the embodiment shown in fig. 1, and therefore are not described again, and are included herein by reference.

In some embodiments, if the first device is a first user device used by a first user or a second user device used by a second user; wherein the device is further configured to: responding to an upgrade completion event for upgrading from a historical version to a current version, if no historical session interaction event is generated in a session between the first user and the second user, detecting whether a time interval absolute value between a friend relationship establishment time corresponding to a friend relationship between the first user and the second user and the current time is larger than or equal to the timing duration, and if so, canceling the presentation of the session and/or canceling the friend relationship. Here, the related operations are the same as or similar to those of the embodiment shown in fig. 1, and therefore are not described again, and are included herein by reference.

In some embodiments, the apparatus is further configured to: and if the absolute value of the time interval between the friend relation establishment time corresponding to the session and the current time is less than the timing duration, starting a timer aiming at the friend relation, wherein the starting time of the timer is the current time. Here, the related operations are the same as or similar to those of the embodiment shown in fig. 1, and therefore are not described again, and are included herein by reference.

In some embodiments, the apparatus is further configured to: presenting the conversation in a first presentation mode in the timing process of the timer, wherein the first presentation mode is different from a second presentation mode corresponding to other conversations not starting the timer; and updating and presenting the session through the second presentation mode in response to the timing ending event of the timer. Here, the related operations are the same as or similar to those of the embodiment shown in fig. 1, and therefore are not described again, and are included herein by reference.

In some embodiments, the first presenting manner includes presenting first countdown information determined according to the current time and the timing duration in a display area of the session, wherein the first countdown information is updated in real time based on the current time. Here, the related operations are the same as or similar to those of the embodiment shown in fig. 1, and therefore are not described again, and are included herein by reference.

In some embodiments, the apparatus is further configured to: in the timing process of the timer, in response to an event that the first user or the second user enters a session page corresponding to the session, presenting second countdown information determined according to the current time and the timing duration in the session page, wherein the second countdown information is updated in real time based on the current time; canceling presentation of the second countdown information in the session page in response to a timing expiration event of the timer. Here, the related operations are the same as or similar to those of the embodiment shown in fig. 1, and therefore are not described again, and are included herein by reference.

In some embodiments, said releasing said buddy relationship comprises: and releasing the friend relationship, and presenting release indication information about the friend relationship to the first user and/or the second user. Here, the related operations are the same as or similar to those of the embodiment shown in fig. 1, and therefore are not described again, and are included herein by reference.

In some embodiments, the releasing the friend relationship, presenting release indication information about the friend relationship to the first user and/or the second user, includes: and releasing the friend relationship, presenting release indication information about the friend relationship to the first user and/or the second user, detecting whether the first user and the second user present a session page corresponding to the session or not, and if so, automatically exiting the session page. Here, the related operations are the same as or similar to those of the embodiment shown in fig. 1, and therefore are not described again, and are included herein by reference.

In some embodiments, if the first device is a first user device used by a first user or a second user device used by a second user, the device is further configured to: in the timing process of the timer, in response to an opening operation performed by the first user or the second user for a session page corresponding to the session, performing at least one of the following operations: resetting and restarting the timer; and changing the corresponding timing duration of the timer, wherein the changed timing duration is greater than the timing duration before the change. Here, the related operations are the same as or similar to those of the embodiment shown in fig. 1, and therefore are not described again, and are included herein by reference.

In some embodiments, the de-presenting the session and/or releasing the buddy relationship includes: canceling the presentation of the session, and/or canceling the friend relationship, and recording expired automatic processing information corresponding to the friend relationship, wherein the expired automatic processing information includes at least one of establishment time of the friend relationship, an automatic processing event type corresponding to the friend relationship, processing time corresponding to the automatic processing event, identification information of the first user, identification information of the second user, identification information of the session, and timing duration corresponding to the timer. Here, the related operations are the same as or similar to those of the embodiment shown in fig. 1, and therefore are not described again, and are included herein by reference.

In some embodiments, if the first device is a first user device used by the first user or a second user device used by the second user; wherein the device is further configured to: and responding to an expired automatic processing information uploading initiating event, and uploading one or more expired automatic processing information corresponding to one or more friend relationships currently recorded by the first equipment to network equipment. Here, the related operations are the same as or similar to those of the embodiment shown in fig. 1, and therefore are not described again, and are included herein by reference.

In some embodiments, as shown in FIG. 3, the system 300 can be implemented as any of the devices in the various embodiments described. In some embodiments, system 300 may include one or more computer-readable media (e.g., system memory or NVM/storage 320) having instructions and one or more processors (e.g., processor(s) 305) coupled with the one or more computer-readable media and configured to execute the instructions to implement modules to perform the actions described herein.

For one embodiment, system control module 310 may include any suitable interface controllers to provide any suitable interface to at least one of processor(s) 305 and/or any suitable device or component in communication with system control module 310.

The system control module 310 may include a memory controller module 330 to provide an interface to the system memory 315. Memory controller module 330 may be a hardware module, a software module, and/or a firmware module.

System memory 315 may be used, for example, to load and store data and/or instructions for system 300. For one embodiment, system memory 315 may include any suitable volatile memory, such as suitable DRAM. In some embodiments, the system memory 315 may include a double data rate type four synchronous dynamic random access memory (DDR4 SDRAM).

For one embodiment, system control module 310 may include one or more input/output (I/O) controllers to provide an interface to NVM/storage 320 and communication interface(s) 325.

For example, NVM/storage 320 may be used to store data and/or instructions. NVM/storage 320 may include any suitable non-volatile memory (e.g., flash memory) and/or may include any suitable non-volatile storage device(s) (e.g., one or more Hard Disk Drives (HDDs), one or more Compact Disc (CD) drives, and/or one or more Digital Versatile Disc (DVD) drives).

NVM/storage 320 may include storage resources that are physically part of the device on which system 300 is installed or may be accessed by the device and not necessarily part of the device. For example, NVM/storage 320 may be accessible over a network via communication interface(s) 325.

Communication interface(s) 325 may provide an interface for system 300 to communicate over one or more networks and/or with any other suitable device. System 300 may wirelessly communicate with one or more components of a wireless network according to any of one or more wireless network standards and/or protocols.

For one embodiment, at least one of the processor(s) 305 may be packaged together with logic for one or more controller(s) (e.g., memory controller module 330) of the system control module 310. For one embodiment, at least one of the processor(s) 305 may be packaged together with logic for one or more controller(s) of the system control module 310 to form a System In Package (SiP). For one embodiment, at least one of the processor(s) 305 may be integrated on the same die with logic for one or more controller(s) of the system control module 310. For one embodiment, at least one of the processor(s) 305 may be integrated on the same die with logic for one or more controller(s) of the system control module 310 to form a system on a chip (SoC).

In various embodiments, system 300 may be, but is not limited to being: a server, a workstation, a desktop computing device, or a mobile computing device (e.g., a laptop computing device, a holding computing device, a tablet, a netbook, etc.). In various embodiments, system 300 may have more or fewer components and/or different architectures. For example, in some embodiments, system 300 includes one or more cameras, a keyboard, a Liquid Crystal Display (LCD) screen (including a touch screen display), a non-volatile memory port, multiple antennas, a graphics chip, an Application Specific Integrated Circuit (ASIC), and speakers.

The present application also provides a computer readable storage medium having stored thereon computer code which, when executed, performs a method as in any one of the preceding.

The present application also provides a computer program product, which when executed by a computer device, performs the method of any of the preceding claims.

The present application further provides a computer device, comprising:

one or more processors;

a memory for storing one or more computer programs;

the one or more computer programs, when executed by the one or more processors, cause the one or more processors to implement the method of any preceding claim.

It should be noted that the present application may be implemented in software and/or a combination of software and hardware, for example, implemented using Application Specific Integrated Circuits (ASICs), general purpose computers or any other similar hardware devices. In one embodiment, the software programs of the present application may be executed by a processor to implement the steps or functions described above. Likewise, the software programs (including associated data structures) of the present application may be stored in a computer readable recording medium, such as RAM memory, magnetic or optical drive or diskette and the like. Additionally, some of the steps or functions of the present application may be implemented in hardware, for example, as circuitry that cooperates with the processor to perform various steps or functions.

In addition, some of the present application may be implemented as a computer program product, such as computer program instructions, which when executed by a computer, may invoke or provide methods and/or techniques in accordance with the present application through the operation of the computer. Those skilled in the art will appreciate that the form in which the computer program instructions reside on a computer-readable medium includes, but is not limited to, source files, executable files, installation package files, and the like, and that the manner in which the computer program instructions are executed by a computer includes, but is not limited to: the computer directly executes the instruction, or the computer compiles the instruction and then executes the corresponding compiled program, or the computer reads and executes the instruction, or the computer reads and installs the instruction and then executes the corresponding installed program. Computer-readable media herein can be any available computer-readable storage media or communication media that can be accessed by a computer.

Communication media includes media by which communication signals, including, for example, computer readable instructions, data structures, program modules, or other data, are transmitted from one system to another. Communication media may include conductive transmission media such as cables and wires (e.g., fiber optics, coaxial, etc.) and wireless (non-conductive transmission) media capable of propagating energy waves such as acoustic, electromagnetic, RF, microwave, and infrared. Computer readable instructions, data structures, program modules, or other data may be embodied in a modulated data signal, for example, in a wireless medium such as a carrier wave or similar mechanism such as is embodied as part of spread spectrum techniques. The term "modulated data signal" means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. The modulation may be analog, digital or hybrid modulation techniques.

By way of example, and not limitation, computer-readable storage media may include volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules or other data. For example, computer-readable storage media include, but are not limited to, volatile memory such as random access memory (RAM, DRAM, SRAM); and non-volatile memory such as flash memory, various read-only memories (ROM, PROM, EPROM, EEPROM), magnetic and ferromagnetic/ferroelectric memories (MRAM, FeRAM); and magnetic and optical storage devices (hard disk, tape, CD, DVD); or other now known media or later developed that can store computer-readable information/data for use by a computer system.

An embodiment according to the present application comprises an apparatus comprising a memory for storing computer program instructions and a processor for executing the program instructions, wherein the computer program instructions, when executed by the processor, trigger the apparatus to perform a method and/or a solution according to the aforementioned embodiments of the present application.

It will be evident to those skilled in the art that the present application is not limited to the details of the foregoing illustrative embodiments, and that the present application may be embodied in other specific forms without departing from the spirit or essential attributes thereof. The present embodiments are therefore to be considered in all respects as illustrative and not restrictive, the scope of the application being indicated by the appended claims rather than by the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein. Any reference sign in a claim should not be construed as limiting the claim concerned. Furthermore, it is obvious that the word "comprising" does not exclude other elements or steps, and the singular does not exclude the plural. A plurality of units or means recited in the apparatus claims may also be implemented by one unit or means in software or hardware. The terms first, second, etc. are used to denote names, but not any particular order.

Various aspects of various embodiments are defined in the claims. These and other aspects of the various embodiments are specified in the following numbered clauses:

1. a method for releasing friend relationship is applied to a first device side, wherein the method comprises the following steps:

2. The method of clause 1, wherein the timing length comprises a first timing length and a second timing length, the first timing length being less than the second timing length;

before the timer reaches a timing duration corresponding to the timer, responding to a session interaction event corresponding to a session between the first user and the second user, and terminating the timer; otherwise, if the timer reaches the timing duration corresponding to the timer, canceling the presentation of the session and/or canceling the friend relationship, including:

before the timer reaches the first timing length, responding to a session interaction event corresponding to a session between the first user and the second user, and terminating the timer; otherwise, if the timer reaches the first timing duration, canceling the presentation of the session and continuing timing;

before the timer reaches the second timing duration, responding to a session interaction event corresponding to the session between the first user and the second user, and terminating the timer; otherwise, if the timer reaches the second timing duration, the friend relationship is released.

3. The method of clause 1, wherein said initiating a timer for a friendship in response to a friendship establishment event between a first user and a second user comprises:

responding to a friend relationship establishing event between a first user and a second user, detecting whether a channel source type corresponding to the friend relationship establishing event is a preset channel source type, and if so, starting a timer aiming at the friend relationship.

4. The method of clause 3, wherein the predetermined channel source type comprises at least one of:

the network equipment automatically initiates a friend relation establishment event between two users;

the method comprises the steps that a user searches nearby persons to initiate a friend relationship establishment event with other users;

and initiating a friend relationship establishment event with other users by the user through a stranger friend adding channel.

5. The method according to clause 3 or 4, wherein the channel source types corresponding to the friend relationship establishing event include a first channel source type used by the first user requesting to add the second user as a friend and a second channel source type used by the second user requesting to add the first user as a friend, and the first channel source type is different from the second channel source type;

if the first device is a first user device used by the first user, the responding to a friend relationship establishment event between the first user and a second user, detecting whether a channel source type corresponding to the friend relationship establishment event is a preset channel source type, and if so, starting a timer aiming at the friend relationship, including:

responding to a friend relationship establishment event between the first user and the second user, detecting whether the first channel source type is a preset channel source type, and if so, starting a first timer corresponding to the first user and aiming at the friend relationship;

if the first device is a second user device used by the second user, responding to a friend relationship establishment event between the first user and the second user, detecting whether a channel source type corresponding to the friend relationship establishment event is a preset channel source type, and if so, starting a timer aiming at the friend relationship, wherein the method comprises the following steps:

responding to a friend relationship establishment event between the first user and the second user, detecting whether the second channel source type is a preset channel source type, and if so, starting a timer corresponding to the second user and aiming at the friend relationship;

if the first device is a network device, responding to a friend relationship establishment event between a first user and a second user, detecting whether a channel source type corresponding to the friend relationship establishment event is a preset channel source type, and if so, starting a timer aiming at the friend relationship, wherein the method comprises the following steps:

responding to a friend relationship establishing event between the first user and the second user, detecting whether the first channel source type and the second channel source type are preset channel source types, and starting a timer aiming at the friend relationship if the first channel source type and the second channel source type are both the preset channel source types; if only one of the two is the predetermined channel source type, only starting the timer corresponding to the user associated with the one, and aiming at the friend relationship, so as to cancel the presentation of the session only when the timer reaches the time duration corresponding to the timer, or not executing any operation.

6. The method according to clause 5, wherein, if yes, starting a first timer for the friend relationship corresponding to the first user includes:

if the friend relationship information is the first friend relationship information, the network equipment sends a timer starting request to the network equipment, receives instruction information fed back by the network equipment aiming at the timer starting request, and starts a first timer corresponding to the first user aiming at the friend relationship if the instruction information indicates that the timer is allowed to be started, wherein the network equipment determines the instruction information by detecting whether the second channel source type is a preset channel source type, the instruction information indicates that the first timer is started if the second channel source type is the preset channel source type, and otherwise, the instruction information indicates that the first timer is not started.

7. The method according to clause 5, wherein, if yes, starting a second timer corresponding to the second user and aiming at the friend relationship includes:

if the friend relationship is the first channel source type, the network device determines the instruction information by detecting whether the first channel source type is a preset channel source type, if the first channel source type is the preset channel source type, the instruction information indicates to start the second timer, and if the friend relationship is the second channel source type, the instruction information indicates not to start the second timer.

8. The method according to clause 3, wherein the responding to the friend relationship establishing event between the first user and the second user, detecting whether a channel source type corresponding to the friend relationship establishing event is a predetermined channel source type, and if so, starting a timer for the friend relationship, including:

responding to a friend relationship establishing event between a first user and a second user, detecting whether a friend application source type corresponding to the friend relationship establishing event is a preset friend application source type, if so, judging whether an expired automatic processing function is started at present according to friend relationship configuration information corresponding to the friend relationship, and if so, starting a timer aiming at the friend relationship.

9. The method of clause 8, wherein the buddy relationship configuration information includes the timing length.

10. The method of clause 8, wherein the method further comprises:

determining the friend relationship configuration information based on at least one of:

the channel source type;

the number of common friends of the first user and the second user;

and the historical conversation interaction frequency information of the first user and the historical conversation interaction frequency information of the second user.

11. The method of clause 8, wherein the method further comprises:

and in response to a first switching event that the state indicated by the friend relationship configuration information is switched from the state of starting an expired automatic processing function to the state of closing the expired automatic processing function, terminating the timer.

12. The method of clause 8 or 11, wherein the method further comprises:

and in response to a second switching event of switching the state indicated by the friend relationship configuration information from closing the expired automatic processing function to opening the expired automatic processing function, if the session does not generate any historical session interaction event and the timer is not timed to end, restarting the timer.

13. The method of clause 12, wherein the restarting the timer comprises at least one of:

restarting the timer, wherein the starting time of the timer is the current time;

the timer is reset and restarted.

14. The method of clause 8, wherein the method further comprises:

responding to a timing duration change event corresponding to the friend relationship configuration information, calculating whether a time interval absolute value between a starting time corresponding to the timer and the current time is less than or equal to the changed timing duration, if so, canceling the presentation of the session, and/or removing the friend relationship, otherwise, continuing to time the timer according to the changed timing duration.

15. The method of clause 5, wherein the method further comprises:

and responding to a timing duration change event corresponding to the friend relationship configuration information, resetting the timer and restarting the timer according to the changed timing duration.

16. The method of clause 1, wherein if the first device is a first user device used by a first user or a second user device used by a second user;

wherein the method further comprises:

responding to an upgrade completion event for upgrading from a historical version to a current version, if no historical session interaction event is generated in a session between the first user and the second user, detecting whether a time interval absolute value between a friend relationship establishment time corresponding to a friend relationship between the first user and the second user and the current time is larger than or equal to the timing duration, and if so, canceling the presentation of the session and/or canceling the friend relationship.

17. The method of clause 16, wherein the method further comprises:

and if the absolute value of the time interval between the friend relation establishment time corresponding to the session and the current time is less than the timing duration, starting a timer aiming at the friend relation, wherein the starting time of the timer is the current time.

18. The method of clause 1, wherein the method further comprises:

presenting the conversation in a first presentation mode in the timing process of the timer, wherein the first presentation mode is different from a second presentation mode corresponding to other conversations not starting the timer;

and updating and presenting the session through the second presentation mode in response to the timing ending event of the timer.

19. The method of clause 18, wherein the first presentation comprises presenting first countdown information determined according to the current time and the timed duration in a display area of the session, wherein the first countdown information is updated in real-time based on the current time.

20. The method of clause 1, wherein the method further comprises:

in the timing process of the timer, in response to an event that the first user or the second user enters a session page corresponding to the session, presenting second countdown information determined according to the current time and the timing duration in the session page, wherein the second countdown information is updated in real time based on the current time;

canceling presentation of the second countdown information in the session page in response to a timing expiration event of the timer.

21. The method of clause 1, wherein said releasing the buddy relationship comprises:

and releasing the friend relationship, and presenting release indication information about the friend relationship to the first user and/or the second user.

22. The method of clause 21, wherein the releasing the friendship, presenting release indication information about the friendship to the first user and/or the second user, comprises:

and releasing the friend relationship, presenting release indication information about the friend relationship to the first user and/or the second user, detecting whether the first user and the second user present a session page corresponding to the session or not, and if so, automatically exiting the session page.

23. The method of clause 1, wherein if the first device is a first user device used by a first user or a second user device used by a second user;

wherein the method further comprises:

in the timing process of the timer, in response to an opening operation performed by the first user or the second user for a session page corresponding to the session, performing at least one of the following operations:

resetting and restarting the timer;

and changing the corresponding timing duration of the timer, wherein the changed timing duration is greater than the timing duration before the change.

24. The method of clause 1, wherein the de-presenting the session and/or releasing the buddy relationship comprises:

canceling the presentation of the session, and/or canceling the friend relationship, and recording expired automatic processing information corresponding to the friend relationship, wherein the expired automatic processing information includes at least one of establishment time of the friend relationship, an automatic processing event type corresponding to the friend relationship, processing time corresponding to the automatic processing event, identification information of the first user, identification information of the second user, identification information of the session, and timing duration corresponding to the timer.

25. The method of clause 24, wherein if the first device is a first user device used by the first user or a second user device used by the second user;

wherein the method further comprises:

and responding to an expired automatic processing information uploading initiating event, and uploading one or more expired automatic processing information corresponding to one or more friend relationships currently recorded by the first equipment to network equipment.

26. An apparatus for releasing a buddy relationship, the apparatus comprising:

a processor; and

a memory arranged to store computer executable instructions that, when executed, cause the processor to perform the method of any of clauses 1 to 25.

27. A computer-readable medium storing instructions that, when executed by a computer, cause the computer to perform the operations of the method of any of clauses 1 to 25.

28. A computer program product comprising a computer program, characterized in that the computer program realizes the steps of the method according to any of clauses 1 to 25 when executed by a processor.

Claims

2. The method of claim 1, wherein the timing length comprises a first timing length and a second timing length, the first timing length being less than the second timing length;

3. The method of claim 1, wherein said initiating a timer for a buddy relationship between a first user and a second user in response to a buddy relationship establishment event comprises:

responding to a friend relationship establishing event between a first user and a second user, detecting whether a channel source type corresponding to the friend relationship establishing event is a preset channel source type, and if so, starting a timer aiming at the friend relationship;

wherein the predetermined channel source type comprises at least one of:

4. The method according to claim 3, wherein the channel source type corresponding to the friend relationship establishing event includes a first channel source type used by the first user to request addition of the second user as a friend and a second channel source type used by the second user to request addition of the first user as a friend, and the first channel source type is different from the second channel source type;

5. The method of claim 4, wherein, if yes, starting a first timer for the friend relationship corresponding to the first user comprises:

6. The method of claim 4, wherein the starting a second timer corresponding to the second user for the friend relationship if yes comprises:

7. The method of claim 3, wherein the responding to a friend relationship establishing event between a first user and a second user, detecting whether a channel source type corresponding to the friend relationship establishing event is a predetermined channel source type, and if so, starting a timer for the friend relationship comprises:

8. The method of claim 7, wherein the buddy relationship configuration information comprises the timing duration.

9. The method of claim 7, wherein the method further comprises:

the channel source type;

the number of common friends of the first user and the second user;

10. The method of claim 7, wherein the method further comprises at least one of:

terminating the timer in response to a first switching event that switches the state indicated by the buddy relationship configuration information from turning on an expired automatic processing function to turning off the expired automatic processing function;

responding to a second switching event of switching the state indicated by the friend relationship configuration information from closing an expired automatic processing function to opening the expired automatic processing function, and restarting the timer if the session does not generate any historical session interaction event and the timer is not timed to end;

wherein the restarting the timer comprises at least one of:

the timer is reset and restarted.

11. The method of claim 7, wherein the method further comprises:

responding to a timing duration change event corresponding to the friend relationship configuration information, and executing at least one of the following operations:

calculating whether the absolute value of the time interval between the starting time corresponding to the timer and the current time is less than or equal to the changed timing duration, if so, canceling the presentation of the session and/or removing the friend relationship, otherwise, continuing timing by the timer according to the changed timing duration;

and resetting the timer and restarting the timer according to the changed timing duration.

12. The method of claim 1, wherein if the first device is a first user device used by a first user or a second user device used by a second user;

wherein the method further comprises:

13. The method of claim 12, wherein the method further comprises:

14. The method of claim 1, wherein the method further comprises:

15. The method of claim 14, wherein the first presenting comprises presenting first countdown information determined according to the current time and the timed duration in a display area of the session, wherein the first countdown information is updated in real-time based on the current time.

16. The method of claim 1, wherein the method further comprises:

17. The method of claim 1, wherein if the first device is a first user device used by a first user or a second user device used by a second user;

wherein the method further comprises:

resetting and restarting the timer;

18. An apparatus for releasing a buddy relationship, the apparatus comprising:

a processor; and

a memory arranged to store computer executable instructions that, when executed, cause the processor to perform the method of any of claims 1 to 17.

19. A computer-readable medium storing instructions that, when executed by a computer, cause the computer to perform operations of any of the methods of claims 1-17.

20. A computer program product comprising a computer program, characterized in that the computer program realizes the steps of the method according to any one of claims 1 to 17 when executed by a processor.