Social relation management method and device based on time delay

Abstract

The invention discloses a social relation management method and device based on time delay. The method comprises the following steps: receiving a forgetting instruction of a user to a target friend; moving the target friend to the forgetting list and starting timing, updating the relationship state to be forgetting and unidirectionally hiding in the UI interface; monitoring whether the user sends a recovery instruction within a preset time limit; if a recovery instruction is received, recovering the friend relationship and UI display; and if the recovery instruction is not received and the time limit is expired, the permanent deletion operation is automatically executed. According to the embodiment of the invention, by introducing the reversible forgetting state with time delay buffering, the technical problems that the existing social relation deletion operation is stiff, irreversible and heavy in decision psychological burden are solved, the technical effects of operation regret period, emotion buffering and automation are realized, the user experience and the product stickiness are remarkably improved, and the user experience is improved. The method is suitable for a social application or system contact management module of various intelligent devices such as a smart phone and a tablet personal computer.

Description

Technical Field

[0001] This invention relates to the field of wearable device technology, and in particular to a method and apparatus for social relationship management based on time delay. Background Technology

[0002] With the widespread adoption of smart devices and the development of social networks, social applications have become indispensable tools in people's daily lives. Users use these applications to establish, maintain, and manage social relationships with others. In the process of managing social relationships, "deleting a friend" is a commonly used function to terminate social relationships that are no longer needed.

[0003] However, existing friend deletion mechanisms in smart devices and social applications have many technical flaws and user experience issues, as follows:

[0004] First, in existing technologies, the "delete friend" operation is instantaneous and irreversible, or the reverse operation is extremely cumbersome. In scenarios where users delete friends due to emotional fluctuations (such as impulsive actions or after arguments), this mechanism offers no buffer. Once deleted, if a user later regrets it, restoring the friendship requires searching for the other person's account again, sending a friend request, and waiting for their approval—a complex process with a low success rate, resulting in irreversible losses due to emotional actions.

[0005] Secondly, current friend management mechanisms employ a binary decision-making model of "either / or," offering only two options: "keep" or "permanently delete," placing a heavy psychological burden on users. For friends with whom they have distant relationships but important memories, or those they temporarily wish to "have some peace and quiet" but are unwilling to completely sever ties with, users are often caught in a dilemma of "reluctant to delete but also unwilling to maintain contact." While existing "block" functions can achieve information blocking, they are highly aggressive and easily escalate conflicts, failing to meet users' complex psychological need for "distance rather than a complete break."

[0006] Furthermore, existing friend management functions are static and mechanical, lacking consideration for the time dimension and human behavioral psychology. The system passively executes users' "add" or "delete" commands, failing to proactively assist users in making rational decisions. Some applications' "recycle bin" or "recently deleted" functions require users to manually clean them up again; otherwise, invalid data will occupy system storage resources for a long time, and users need to remember the cleanup time, increasing the management burden and leading to low system resource management efficiency.

[0007] Finally, a rigid deletion mechanism can easily trigger negative emotions in users (such as regret and anxiety). This negative experience, when associated with social applications or smart devices, can reduce users' positive feelings and loyalty to the product, affecting user stickiness and market competitiveness.

[0008] In summary, the existing social relationship deletion mechanisms suffer from technical problems such as being rigid, irreversible, causing heavy psychological burdens for decision-making, and lacking a human touch. These problems have become key factors restricting the improvement of user experience in social applications, and a technical solution that can solve these problems is urgently needed. Summary of the Invention

[0009] This invention provides a time-delay-based social relationship management method and apparatus, which can solve the technical problems of irreversible emotional operations, excessive psychological burden of decision-making, and lack of human dimension in social relationship management in existing friend deletion mechanisms. It achieves the technical effects of operation regret period, emotional buffer, and automated follow-up, reduces users' psychological pressure, and improves the system's intelligence level and user experience.

[0010] In a first aspect, embodiments of the present invention provide a social relationship management method based on time delay, comprising:

[0011] Receives a forget instruction from a user for a target friend, the forget instruction being triggered through the user interface of a smart device;

[0012] In response to the forget command, the target friend is moved to the forget list, the relationship status between the target friend and the user is updated to forgotten, and the target friend is removed from the user's friend list and chat list. At the same time, a log record containing the target friend ID, the forget operation timestamp, and the preset time limit is generated.

[0013] Start the timer to keep track of the preset time period;

[0014] Within the preset time period, continuously monitor whether the user issues a recovery command for the target friend;

[0015] If the recovery instruction is received within the preset period, the relationship status of the target friend is restored to friend, the friend is removed from the forgotten list and re-displayed in the friend list, the timer is stopped and the corresponding log record is cleared.

[0016] If the preset time limit is reached and the recovery instruction is not received, then the target friend will be permanently deleted, and the relevant data and log records of the target friend will be cleared.

[0017] Optionally, the preset period can be a system default value or a custom setting provided by the user through the settings interface of the smart device.

[0018] Optionally, after moving the target friend to the forget list, the method further includes:

[0019] The user who performs the forget operation will no longer display the target friend in their friend list or chat list, and the user's activity information will be invisible to the target friend, while the target friend's friend list will still display the user.

[0020] Optionally, after starting the timer and timing the preset period, the method further includes:

[0021] Before the preset deadline is reached, a reminder notification is sent to the user. The reminder notification includes the target friend's information and a countdown to the deadline. The reminder notification can take the form of an application push notification, SMS notification, or in-app pop-up notification. The user can directly jump to the forgotten list interface through the reminder notification.

[0022] Optionally, the forget instruction can be triggered by: the user clicking the forget button on the target friend's profile page, long-pressing the target friend in the friend list and selecting the forget option, or dragging the target friend's avatar to a preset forget area on the smart device's UI interface.

[0023] Secondly, embodiments of the present invention provide a social relationship management device based on time delay, comprising:

[0024] The instruction receiving module is used to receive forgetting and retrieval instructions from users for target friends through the user interface of smart devices;

[0025] The status processing module connects to the database of the smart device. It is used to update the relationship status of the target friend to forgotten in response to the forget command and move it between the friend list, chat list and forgotten list. It is also used to roll back the relationship status to friend in response to the restore command.

[0026] The logging module is used to generate a log record containing the target friend's ID, the timestamp of the forgetting operation, and a preset time limit when the target friend is moved to the forgotten list, and to clean up the corresponding log record after the recovery operation or permanent deletion operation is performed;

[0027] The time management module is used to start a timer for the target friend moved to the forget list, keep track of the preset period, and send a trigger signal when the period expires;

[0028] The operation monitoring module is used to continuously monitor whether the user issues a recovery command for the target friend within a preset period of time;

[0029] The recovery execution module is used to coordinate the status processing module, log recording module, and time management module to perform relationship status rollback, UI display update, timer stop, and log clearing operations when a recovery command is received.

[0030] The automatic deletion module is used to permanently delete the target friend and clean up related data when it receives a timeout trigger signal from the time management module.

[0031] Optionally, the preset period can be a system default value or a custom setting provided by the user through the settings interface of the smart device.

[0032] Optionally, it also includes a hiding module, which is used to prevent the target friend from being displayed in the friend list and chat list of the user who performed the forgetting operation after the target friend is moved to the forget list, and the user's dynamic information is not visible to the target friend, while the target friend's friend list still displays the user.

[0033] Optionally, it also includes a reminder module, which is used to send a reminder notification to the user at a predetermined time before the preset period is reached after the timer is started and the preset period is counted. The reminder notification includes the target friend information and the countdown to the expiration of the period. The reminder notification can take the form of an application push notification, SMS notification or in-app pop-up notification. The user can directly jump to the forgotten list interface through the reminder notification.

[0034] Optionally, the forget instruction can be triggered by: the user clicking the forget button on the target friend's profile page, long-pressing the target friend in the friend list and selecting the forget option, or dragging the target friend's avatar to a preset forget area on the smart device's UI interface.

[0035] Thirdly, embodiments of the present invention also provide a computing device, comprising:

[0036] Memory, used to store program instructions;

[0037] The processor is used to call the program instructions stored in the memory and execute the aforementioned time-delay-based social relationship management method according to the obtained program.

[0038] Fourthly, embodiments of the present invention also provide a computer-readable non-volatile storage medium, including computer-readable instructions, which, when read and executed by a computer, cause the computer to perform the aforementioned time-delay-based social relationship management method.

[0039] This invention provides a time-delay-based social relationship management method, which includes receiving a user's forgetting instruction for a target friend; moving the target friend to a forget list and starting a timer, updating its relationship status to forgotten and unilaterally hiding it in the UI; monitoring whether the user issues a recovery instruction within a preset period; if a recovery instruction is received, restoring the friend relationship and UI display; if no recovery instruction is received and the period expires, automatically performing a permanent deletion operation. This invention solves the technical problems of existing social relationship deletion operations being rigid, irreversible, and psychologically burdensome by introducing a reversible forgetting state with a time delay buffer. It achieves the technical effects of an operation regret period, emotional buffering, and automated cleanup, significantly improving user experience and product stickiness. It is applicable to social applications or system contact management modules on various smart devices such as smartphones and tablets. Attached Figure Description

[0040] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0041] Figure 1 A schematic diagram of a system architecture provided for an embodiment of the present invention;

[0042] Figure 2 A flowchart illustrating a time-delay-based social relationship management method provided in an embodiment of the present invention;

[0043] Figure 3 This is a schematic diagram of a time-delay-based social relationship management device provided in an embodiment of the present invention. Detailed Implementation

[0044] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this invention, and not all of them. Based on the embodiments of this invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this invention.

[0045] First of all, with Figure 1The structure shown is used as an example to describe the wearable device to which this invention applies. In this invention embodiment, the wearable device 100 may include, but is not limited to, components such as a radio frequency (RF) circuit 110, a memory 120, an input unit 130, a WiFi module 170, a display unit 140, a sensor 150, an audio circuit 160, a processor 180, and a motor 190.

[0046] As those skilled in the art will understand, Figure 1 The structure of the wearable device 100 shown is merely an example and not a limitation. The wearable device 100 may also include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0047] RF circuit 110 can be used for signal reception and transmission during information transmission or calls. Specifically, it receives downlink information from the base station and processes it for the processor 180; additionally, it transmits uplink data from the wearable device 100 to the base station. Typically, RF circuitry includes, but is not limited to, antennas, at least one amplifier, transceiver, coupler, low-noise amplifier (LNA), duplexer, etc. Furthermore, RF circuit 110 can also communicate wirelessly with networks and other devices. The aforementioned wireless communication can use any communication standard or protocol, including but not limited to Global System for Mobile communication (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Long Term Evolution (LTE), email, Short Messaging Service (SMS), etc.

[0048] The memory 120 can be used to store software programs and modules. The processor 180 executes various functional applications and data processing of the wearable device 100 by running the software programs and modules stored in the memory 120. The memory 120 may mainly include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function (such as sound playback function, image playback function, etc.), etc.; the data storage area may store data created according to the use of the wearable device 100 (such as audio data, phone book, etc.). In addition, the memory 120 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device.

[0049] The input unit 130 can be used to receive input numerical or character information, and to generate key signals related to user settings and function control of the wearable device 100. Specifically, the input unit 130 may include a touch panel 131, a camera device 132, and other input devices 133. The camera device 132 can take pictures of the images to be acquired, and then transmit the images to the processor 180 for processing, and finally present the graphics to the user through the display panel 141. The touch panel 131, also known as a touch screen, can collect touch operations on or near the user (such as operations performed by the user using a finger, stylus, or any suitable object or accessory on or near the touch panel 131), and drive the corresponding connected devices according to a pre-set program. Optionally, the touch panel 131 may include two parts: a touch detection device and a touch controller. The touch detection device detects the user's touch position and the signal generated by the touch operation, transmitting the signal to the touch controller. The touch controller receives touch information from the touch detection device, converts it into touch point coordinates, and sends it to the processor 180. It can also receive and execute commands from the processor 180. Furthermore, the touch panel 131 can be implemented using various types of sensors, including resistive, capacitive, infrared, and surface acoustic wave sensors. In addition to the touch panel 131 and the camera device 132, the input unit 130 may also include other input devices 133. Specifically, these other input devices 132 may include, but are not limited to, one or more of the following: a physical keyboard, function keys (such as volume control buttons, power buttons, etc.), a trackball, and a joystick.

[0050] The display unit 140 can be used to display information input by the user or information provided to the user, as well as various menus of the wearable device 100. The display unit 140 may include a display panel 141, which may optionally be configured using a liquid crystal display (LCD), organic light-emitting diode (OLED), or similar technology. Furthermore, a touch panel 131 may cover the display panel 141. When the touch panel 131 detects a touch operation on or near it, it transmits the information to the processor 180 to determine the type of touch event. Subsequently, the processor 180 provides corresponding visual output on the display panel 141 based on the type of touch event.

[0051] The visual output external display panel 141, which is recognizable by the human eye, can serve as a display device in this embodiment of the invention, used to display text or image information. Although in Figure 1 In this embodiment, the touch panel 131 and the display panel 141 are two separate components to realize the input and output functions of the wearable device 100. However, in some embodiments, the touch panel 131 and the display panel 141 can be integrated to realize the input and output functions of the wearable device 100.

[0052] In addition, the wearable device 100 may also include at least one sensor 150, such as an attitude sensor, a distance sensor, a light sensor, and other sensors.

[0053] Specifically, an attitude sensor can also be called a motion sensor, and one type of motion sensor can be an angular velocity sensor (also known as a gyroscope). When configured in the wearable device 100, it measures the angular velocity of the wearable device 100 when it is in motion, such as when it is tilted or turned. Thus, the gyroscope can accurately analyze and determine the actual actions of the user using the wearable device 100, and then perform corresponding operations on the wearable device 100. Examples include: motion sensing, shaking (using the wearable device 100 to perform certain functions), and inertial navigation based on the motion of an object when there is no GPS signal (such as in a tunnel).

[0054] Sensors can also include optical sensors, which are mainly used to collect information such as the wavelength and intensity of various light rays to adjust the backlight intensity of the display panel 141.

[0055] Furthermore, in this embodiment of the invention, other sensors such as barometers, hygrometers, thermometers, and infrared sensors may also be configured as sensor 150, which will not be described in detail here.

[0056] The light sensor may also include a proximity sensor that can turn off the display panel 141 and / or backlight when the wearable device 100 is moved to the ear.

[0057] Audio circuit 160, speaker 161, and microphone 162 provide an audio interface between the user and wearable device 100. Audio circuit 160 converts received audio data into electrical signals and transmits them to speaker 161, where speaker 161 converts them into sound signals for output. On the other hand, microphone 162 converts collected sound signals into electrical signals, which are received by audio circuit 160, converted into audio data, and then processed by processor 180 before being transmitted via RF circuit 110 to, for example, another wearable device 100, or to memory 120 for further processing.

[0058] WiFi is a short-range wireless transmission technology. Wearable device 100, through WiFi module 170, can help users send and receive emails, browse web pages, and access streaming media, providing users with wireless broadband internet access. Although Figure 1 WiFi module 170 is shown, but it is understood that it is not a necessary component of wearable device 100 and can be omitted as needed without changing the nature of the invention.

[0059] The processor 180 is the control center of the wearable device 100. It connects to various parts of the wearable device 100 via various interfaces and lines. By running or executing software programs and / or modules stored in the memory 120, and by calling data stored in the memory 120, it performs various functions and processes data of the wearable device 100, thereby providing overall monitoring of the wearable device 100. Optionally, the processor 180 may include one or more processing units; preferably, the processor 180 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and applications, and the modem processor mainly handles wireless communication.

[0060] It is understandable that the aforementioned modem processor may not be integrated into the processor 180.

[0061] The wearable device 100 may also include at least one motor 190. Since the wearable device 100 is an energy-consuming device, the motor 190 may be a small motor. At the same time, multiple motors may be configured for the wearable device 100 depending on the power that the motor can provide.

[0062] The wearable device 100 also includes a power supply (not shown in the figure) for powering the various components.

[0063] Preferably, the power supply can be logically connected to the processor 180 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. Although not shown, the wearable device 100 may also include a Bluetooth module, etc., which will not be described in detail here.

[0064] It should be noted that the above Figure 1 The structure shown is merely an example, and the embodiments of the present invention are not limited thereto.

[0065] The wearable device in this embodiment of the invention is applicable to the social application or system contact management module of various wearable devices such as smartwatches, bracelets, AR / VR devices, and handheld devices, and is used to realize flexible and humanized management of social relationships.

[0066] Figure 2 An exemplary embodiment of the present invention provides a time-delay-based social relationship management process, which can be executed by a time-delay-based social relationship management device.

[0067] like Figure 2 As shown, by constructing a "forgetting" logic layer with a time delay buffer, flexible management of social relationships is achieved. This process specifically includes:

[0068] Step 210: Receive the user's forget instruction for the target friend.

[0069] The forget command is triggered through the user interface of the smart device. The smart device receives the forget command from the user for a specific friend through its user interface (UI). The triggering methods for this forget command are diverse to adapt to different users' operating habits, including but not limited to:

[0070] Set up a dedicated "Forget" button on the target friend's profile page; users can trigger an action by clicking this button.

[0071] In the friend list, the user long-presses the target friend's entry, and an operation menu with the forget option pops up. The user selects this option to trigger the command.

[0072] A specific forgetting area is preset in the UI of the smart device. Users can trigger the command by dragging the avatar of the target friend to that area.

[0073] Step 220: In response to the forget command, move the target friend to the forget list, update the relationship status between the target friend and the user to forgotten, remove the target friend from the user's friend list and chat list, and generate a log record containing the target friend ID, the forget operation timestamp, and a preset time limit value.

[0074] Upon responding to the forget command, a series of linked operations are executed, including the following sub-steps:

[0075] Status Change. In the smart device's database, the relationship status field between the target friend and the current user is updated from friend to forgotten, establishing a special status identifier to distinguish different social relationship types.

[0076] Remove the target friend's entry from the user's frequently used main views such as the friend list and chat list to avoid the user being disturbed by the friend's information; at the same time, add the target friend to a dedicated forget list view, which is usually set in a secondary menu such as the application's settings or privacy management, so that the user can access it at any time without taking up space on the main operation interface.

[0077] Log recording. Generate a complete operation log, which includes at least the target friend ID (used to uniquely identify the friend), the forgotten operation timestamp (recording the specific time the command was triggered), and the preset expiration date (the currently effective delayed deletion period). This log is used as the basis for subsequent timing, recovery operations, and data cleanup.

[0078] Furthermore, embodiments of the present invention can also achieve a one-way concealment function: after the target friend is moved to the forget list, the target friend will no longer be displayed in the friend list and chat list of the user who performed the forget operation, and the user's dynamic information will not be visible to the target friend, while the target friend's friend list will still display the user.

[0079] For example, when user A performs the forgetting operation, target friend B will no longer be displayed in user A's friend list and chat list, and user A's dynamic information (such as Moments, status updates, etc.) will not be visible to target friend B; while target friend B's friend list will still display user A, and messages sent by B to A will be temporarily stored by the system or a message will be displayed that "the other party has not yet received the message", so as to avoid B feeling that he / she has been "forgotten" and reduce social conflicts.

[0080] Step 230: Start the timer to keep track of the preset time period.

[0081] The timer module of the smart device is invoked to start a timer for the forgotten record of the target friend. The timer can be either countdown or forward, and will begin timing for a preset period. This preset period can be a system default value or customized by the user through the smart device's settings interface. The preset period can be set based on experience, for example, 7 days, 15 days, 30 days, 60 days, etc.

[0082] In addition, the preset period setting adopts a flexible mode: it provides a system default value (such as 30 days) to adapt to the usage habits of most users; it also provides a custom interface, allowing users to select options such as 7 days, 15 days, 30 days, and 60 days through the application settings interface, or manually enter a specific number of days (such as 10 days), so that the period setting is more in line with the user's personalized needs.

[0083] Step 240: Within the preset time limit, continuously monitor whether the user issues a recovery command for the target friend. If yes, proceed to step 250; otherwise, proceed to step 260.

[0084] During the entire preset period after the timer starts, the system continuously monitors the user's actions on the "Forgotten List" interface through the operation monitoring module, focusing on whether the user issues a "restore" command for the target friend's entry. The triggering method for the restore command is adapted to the forget command, such as clicking the "restore" button after the target friend's entry in the Forgotten List, or long-pressing the entry and selecting the "restore friend" option. This step is a decision branch point, and the system executes different subsequent processes based on the timer status and operation monitoring results. If a restore command for the target friend is received from the user within the preset period, the system proceeds to step S250 to perform the restore operation; if the timer reaches the preset period and no restore command for the target friend is received during this period, the system proceeds to step S260 to perform an automatic deletion operation.

[0085] Step 250: Restore the relationship status of the target friend to friend, remove it from the forgotten list and re-display it in the friend list, stop the timer and clear the corresponding log records.

[0086] After responding to the recovery command, execute the following sub-steps to achieve lossless restoration of social relationships:

[0087] State rollback. The relationship status field of the target friend is restored from forgotten to friend in the database, returning to the state before the forget operation was performed.

[0088] UI rollback. Removes the target friend's entry from the forgotten list and re-appears it in the user's friend list. If there was previous chat history, the chat session with that friend is restored in the chat list.

[0089] Clear the records. Stop the timer corresponding to the target friend, and clear or archive the log records generated in step S220 to avoid invalid logs occupying storage resources.

[0090] Furthermore, after the recovery operation is performed, the target friend's historical chat history, friend tags (such as "classmate" or "family"), and permission settings (such as whether to allow viewing Moments or receiving message notifications) are all fully restored to the state before the forgetting operation was performed, ensuring the continuity of the user's social data.

[0091] Step 260: Perform a permanent deletion operation on the target friend and clear the relevant data and log records of the target friend.

[0092] When the timer reaches its preset expiration date and no recovery command is received, the following sub-steps are automatically triggered to permanently terminate the social relationship:

[0093] Perform permanent deletion. Invoke the traditional "delete friend" core process to completely remove the target friend from the user's friend relationships. This includes deleting the target friend's chat history and contact details (such as phone number and address) stored locally on the smart device, and removing the friend relationship mapping on the server side to ensure that neither party has friend permissions.

[0094] Clean up the data. Permanently delete the target friend's entry in the "Forgot List", the log records generated in step S230, as well as all cached data and associated permission settings related to the friend, freeing up system storage resources.

[0095] Furthermore, this method includes a reminder step: at a predetermined time before the preset deadline, the system automatically sends a reminder notification to the user. This notification includes the target friend's nickname, avatar, and other identifying information, as well as a countdown to the deadline (e.g., "Your forgotten friend XXX will be permanently deleted in 24 hours"), allowing users to quickly identify and make decisions. The notification format can be chosen by the user, including app push notifications, SMS notifications, or in-app pop-up notifications, and includes a link directly to the "Forgotten List" interface, allowing users to quickly access and perform restoration or other operations. The preset time can use the system default value (e.g., 24 hours) or be customized by the user, with options including 24 hours, 12 hours, and 6 hours to meet the reminder needs of different users.

[0096] To make the technical solution, objective, and beneficial effects of the present invention clearer, the present invention will be described in detail below with reference to specific embodiments. It should be understood that the specific embodiments described herein are only for explaining the present invention and are not intended to limit the present invention.

[0097] Example 1: Application in smartphone social applications.

[0098] This embodiment takes a social APP on a smartphone (hereinafter referred to as "target APP") as an example to illustrate the specific implementation process of the social relationship management method based on time delay of the present invention.

[0099] 1. Initial configuration

[0100] During the development phase of the target app, the social relationship management device of this invention is integrated into the app's client, specifically including:

[0101] Add a "Relationship Status" field to the APP's database, with values ​​including "Friend" and "Forgotten", to identify the type of relationship between the user and their friends;

[0102] Set up a "Forgot" button (friend profile page), a long-press operation menu (friend list), and a "Forgot Area" (homepage sidebar) in the app's UI as the trigger entry points for the forget command;

[0103] Add a "Forgotten List" interface in "Settings - Privacy Management" to display forgotten friends. Each friend entry has an "Restore" button and an "Delete Now" button.

[0104] Configure the time management module. The default preset period is 30 days. Users can select 7 days, 15 days, 30 days, or 60 days in "Privacy Management - Forgot Settings", or manually enter a custom period of 1-90 days.

[0105] The configuration notification module has a default reminder time of 24 hours before the deadline. Users can customize it to 12 hours or 6 hours. The reminder method is application push notification by default, but it can be switched to SMS notification.

[0106] 2. Specific operating procedures:

[0107] User A and User B are friends on the target app. User A has a disagreement with User B and wants to temporarily stop seeing User B. The specific steps are as follows:

[0108] Step S100: Trigger the forget instruction.

[0109] User A opens the target app, enters User B's profile page, and clicks the "Forgot" button at the bottom of the page. A confirmation pop-up window appears, prompting "After being forgotten, the other person will be hidden from your friend list and automatically deleted after 30 days. They can be restored in the Forgot List." User A clicks "Confirm," and the target app's instruction receiving module receives the forget instruction.

[0110] Step S200: Perform forgetting processing.

[0111] The status processing module updates the relationship status between user A and user B in the database from "friends" to "forgotten";

[0112] In the UI, User B's entry is removed from User A's "Friends List" and "Chat List" and added to the "Forgot List" (path: Settings - Privacy Management - Forgot List);

[0113] The logging module generates the following logs: Target friend ID (B's user ID: 123456), Forgot operation timestamp (2024-05-01 14:30:25), and preset time limit (30 days);

[0114] The timing management module starts the timer, begins timing in positive mode, and records the currently forgotten duration.

[0115] Meanwhile, the one-way anonymity feature is enabled: User B will no longer be displayed in User A's friend list and chat list, and User A's Moments updates will not be visible to User B; User A will still be displayed in User B's friend list, and messages sent by User B to User A will be displayed in the target app with the message "The other party has not yet received your message" and the message will be temporarily stored on the server and not pushed to User A.

[0116] Step S300: Monitor recovery commands.

[0117] During the 30-day preset period from May 1, 2025 to May 31, 2025, the operation monitoring module continuously monitors user A's operations in the "Forgot List", focusing on whether user A clicks the "Restore" button after user B's entry.

[0118] Step S400: Resume operation within the specified time limit.

[0119] On May 5, 2025, User A and User B reached a settlement and wished to restore their friendship. The steps are as follows:

[0120] User A enters the "Forgotten List", finds User B's entry, clicks the "Restore" button on the right, and triggers the restore command;

[0121] The operation monitoring module captures the recovery command and transmits it to the recovery execution module;

[0122] The recovery execution module coordinates with other modules: the status processing module rolls back the relationship status to "friends," removes user B's entry from the forgotten list in the UI, and restores it to the friend list and chat list; the timer management module stops the timer; and the log recording module clears the corresponding forgotten log.

[0123] After the recovery is complete, User A can view User B's activity normally. User B's temporarily stored messages will be pushed to User A's chat list. Historical chat records, friend tags (such as "college classmates"), and Moments permission settings will all be restored to their previous state.

[0124] Step S500: Automatic deletion upon expiration of the time limit.

[0125] If user A does not perform the recovery operation for user B within the preset period of 30 days, the specific process is as follows:

[0126] 2025-05-30 14:30:25 (24 hours before the deadline), the notification module generates a push notification: "Your forgotten friend B (ID:123456) will be permanently deleted in 24 hours. Click to view details." User A can click the notification to jump directly to the forgotten list.

[0127] If user A does not perform any operation, at 14:30:25 on 2025-05-31, the time management module will send a time limit expiration signal;

[0128] The automatic deletion module responds to the following signals: it calls the APP's friend deletion interface to remove the friend relationship between user A and user B, and the server deletes the friend relationship mapping between the two parties; the status handling module permanently removes user B from the forgotten list; the log recording module clears the forgotten log; the system cleans up user A's local storage of user B's chat history, cached avatar, contact information and other data.

[0129] After deletion, User A's friend list and chat list will no longer contain User B's information, and User B's friend list will no longer display User A. Both parties need to add each other as friends again to establish a social relationship.

[0130] Example 2: Application in the Contacts section of a Smartwatch System

[0131] This embodiment uses the system contact management module of a smartwatch as an example to illustrate the specific application of the present invention:

[0132] The smartwatch's operating system integrates the social relationship management device of this invention, with the following specific configuration:

[0133] The system's contact database has added a "relationship status" field, supporting "friend" and "forgotten" identifiers;

[0134] How to trigger the "Forgot" command: Long press the contact entry and select "Forgot" from the pop-up menu;

[0135] The forgotten list is set in "Contacts - Settings - Forgotten Management";

[0136] The default preset period is 15 days, and users can choose 7 days, 15 days, or 30 days.

[0137] The reminder method is a combination of smartwatch vibration and on-screen pop-up notification, with the default reminder time being 12 hours before the expiration date.

[0138] Detailed operating procedures:

[0139] User C maintains contact with family member D through the system contacts on their smartwatch. Because they do not want to be disturbed by calls or messages from D for the time being, they perform the following actions:

[0140] Trigger the forget command: User C long-presses D's entry in the contact list of the smartwatch, selects "Forget", and the system receives the forget command after confirmation;

[0141] Forgotten handling: Remove D's contact entry from the frequently used contacts list, add it to the "Forgotten Management" list, update the relationship status to "Forgotten", generate a log containing D's contact ID, operation timestamp, and 15-day period, and start a timer;

[0142] One-way anonymity: User C's contact list does not contain D. When D calls C, the smartwatch does not ring or pop up a window, but only records the missed call in the background; C's calls and messages are visible to D normally.

[0143] Recovery Operation: 5 days later, if user C wants to restore D's contact status, he / she goes to the "Forgotten Management" list, clicks "Restore" after D's entry, the system performs a status rollback and UI update, restores D's display in the list of frequently used contacts, and pushes missed call records to user C;

[0144] Automatic deletion: If user C does not recover, the system will automatically delete D's contact information and forgotten logs after 15 days, revoke related permissions, and D's incoming calls will be treated as unknown calls.

[0145] Based on the same technological concept Figure 3 An exemplary embodiment of the present invention illustrates the structure of a time-delay-based social relationship management device, which can execute a time-delay-based social relationship management process.

[0146] like Figure 3 As shown, the device may include:

[0147] The instruction receiving module 310 is used to receive forgetting instructions and retrieval instructions from the user for a target friend through the user interface of the smart device;

[0148] The status processing module 320 is connected to the database of the smart device. It is used to update the relationship status of the target friend to forgotten in response to the forget command and move it between the friend list, chat list and forgotten list. It is also used to roll back the relationship status to friend in response to the restore command.

[0149] The logging module 330 is used to generate a log record containing the target friend ID, the forgetting operation timestamp and a preset time limit when the target friend is moved to the forgotten list, and to clean up the corresponding log record after the recovery operation or permanent deletion operation is performed.

[0150] The timing management module 340 is used to start a timer for the target friend moved to the forget list, keep track of the preset period, and send a trigger signal when the period expires;

[0151] The operation monitoring module 350 is used to continuously monitor whether the user issues a recovery command for the target friend within a preset period of time;

[0152] The recovery execution module 360 ​​is used to coordinate the status processing module, log recording module and time management module to perform relationship status rollback, UI display update, timer stop and log clearing operations when a recovery command is received;

[0153] The automatic deletion module 370 is used to permanently delete the target friend and clean up related data when it receives the expiration trigger signal from the time management module.

[0154] Optionally, the preset period can be a system default value or a custom setting provided by the user through the settings interface of the smart device.

[0155] Optionally, it also includes a concealment module 380, which is used to prevent the target friend from being displayed in the friend list and chat list of the user who performed the forgetting operation after the target friend is moved to the forget list, and the user's dynamic information is not visible to the target friend, while the target friend's friend list still displays the user.

[0156] Optionally, it also includes a reminder module 390, which is used to send a reminder notification to the user at a predetermined time before the preset period is reached after the timer is started and the preset period is counted. The reminder notification includes the target friend information and the countdown to the expiration of the period. The reminder notification can take the form of an application push notification, SMS notification or in-application pop-up notification. The user can directly jump to the forgotten list interface through the reminder notification.

[0157] Optionally, the forget instruction can be triggered by: the user clicking the forget button on the target friend's profile page, long-pressing the target friend in the friend list and selecting the forget option, or dragging the target friend's avatar to a preset forget area on the smart device's UI interface.

[0158] Based on the same technical concept, embodiments of the present invention also provide a computing device, including:

[0159] Memory, used to store program instructions;

[0160] The processor is used to call the program instructions stored in the memory and execute the aforementioned time-delay-based social relationship management method according to the obtained program.

[0161] Based on the same technical concept, embodiments of the present invention also provide a computer-readable non-volatile storage medium, including computer-readable instructions, which, when read and executed by a computer, cause the computer to perform the aforementioned time-delay-based social relationship management method.

[0162] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0163] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0164] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0165] Although preferred embodiments of the invention have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including both the preferred embodiments and all changes and modifications falling within the scope of the invention.

[0166] Obviously, those skilled in the art can make various modifications and variations to this invention without departing from its spirit and scope. Therefore, if these modifications and variations fall within the scope of the claims of this invention and their equivalents, this invention also intends to include these modifications and variations.

Claims

1. A time delay based social relationship management method, characterized in that, The method comprises the following steps: receiving a forgetting instruction of a user for a target friend, the forgetting instruction being triggered through a user interface of a smart device; in response to the forgetting instruction, moving the target friend to a forgetting list, updating the relationship status of the target friend with the user to forgetting, and removing the target friend from the friend list and the chat list of the user, and generating a log record containing the target friend ID, the forgetting operation timestamp, and a preset deadline value; starting a timer to count the preset deadline; continuously monitoring whether the user issues a recovery instruction for the target friend within the preset deadline; if the recovery instruction is received within the preset deadline, restoring the relationship status of the target friend to a friend, removing the target friend from the forgetting list and displaying the target friend in the friend list again, stopping the counting and clearing the corresponding log record; if the counting reaches the preset deadline and the recovery instruction is not received, performing a permanent deletion operation on the target friend, and cleaning up the related data and log record of the target friend.

2. The method of claim 1, wherein, The preset deadline is a system default value or a custom setting value set by the user through a setting interface of the smart device.

3. The method of claim 1, wherein, After moving the target friend to the forgetting list, the method further comprises the following steps: the target friend is no longer displayed in the friend list and the chat list of the user who performs the forgetting operation, and the dynamic information of the user is not visible to the target friend, and the friend list of the target friend still displays the user.

4. The method of claim 1, wherein, After starting the timer to count the preset deadline, the method further comprises the following steps: sending a reminder notification to the user at a predetermined time before the counting reaches the preset deadline, the reminder notification containing target friend information and a countdown of the deadline, the form of the reminder notification including an application push notification, an SMS notification, or an in-application pop-up window notification, and the user can directly jump to the forgetting list interface through the reminder notification.

5. The method according to any one of claims 1 to 4, characterized in that, The triggering mode of the forgetting instruction includes: clicking the forgetting button on the profile page of the target friend, long pressing the target friend in the friend list and selecting the forgetting option, or dragging the avatar of the target friend to a preset forgetting area of the UI interface of the smart device.

6. A time delay based social relationship management apparatus, characterized by, The method comprises the following steps: an instruction receiving module for receiving a forgetting instruction and a recovery instruction of a user for a target friend through a user interface of a smart device; a state processing module connected with a database of the smart device, for updating the relationship status of the target friend to forgetting in response to the forgetting instruction, and moving the target friend between the friend list, the chat list, and the forgetting list, and for rolling back the relationship status to a friend in response to the recovery instruction; a log record module for generating a log record containing the target friend ID, the forgetting operation timestamp, and the preset deadline value when the target friend is moved to the forgetting list, and cleaning up the corresponding log record after the recovery operation or the permanent deletion operation is performed; a timing management module for starting a timer for the target friend moved to the forgetting list, counting the preset deadline, and issuing a trigger signal when the deadline expires; an operation monitoring module for continuously monitoring whether the user issues a recovery instruction for the target friend within the preset deadline; The recovery execution module is configured to, when receiving the recovery instruction, coordinate the state processing module, the log recording module and the timing management module to perform the relationship state rollback, the UI display update, the timing stop and the log clearing operation. The automatic deletion module is configured to, when receiving the expiration trigger signal from the timing management module, perform the permanent deletion operation on the target friend and the related data cleaning.

7. The apparatus of claim 6, wherein, The preset expiration time is a system default value or a custom setting by the user through a setting interface of the smart device.

8. The apparatus of claim 6, wherein, The system further comprises a concealment module configured to, after moving the target friend to the forgotten list, no longer display the target friend in a friend list and a chat list of a user performing the forgotten operation, and the dynamic information of the user is invisible to the target friend, and the friend list of the target friend still displays the user.

9. A computing device, comprising: The system comprises: a memory configured to store program instructions; a processor configured to call the program instructions stored in the memory and perform the method according to any one of claims 1 to 5 according to the obtained program execution right.

10. A computer-readable non-transitory storage medium, characterized in that, The computer readable instructions, when read and executed by the computer, cause the computer to perform the method according to any one of claims 1 to 5.

Images