CN111125153A

CN111125153A - Object management method, device, client and medium

Info

Publication number: CN111125153A
Application number: CN201911371824.9A
Authority: CN
Inventors: 王智培; 杨柳; 青欣; 王曦; 张文峰; 冯诚; 丁茂霞; 马宁
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2019-12-26
Filing date: 2019-12-26
Publication date: 2020-05-08

Abstract

The embodiment of the application discloses an object management method, an object management device, a client and a medium, wherein the method comprises the following steps: in response to a storage trigger event for a target image, displaying a duration setting interface of the target object on a user interface; and storing the target object according to the time length setting operation detected in the time length setting interface. According to the embodiment of the application, the target object can be stored and managed according to the time length setting operation, the target object can be automatically deleted, and convenience is improved.

Description

Object management method, device, client and medium

Technical Field

The present application relates to the field of internet technologies, and in particular, to the field of computer technologies, and in particular, to an object management method, an object management apparatus, a client, and a computer storage medium.

Background

At present, most clients have an object storage function, where objects may include documents, images, and the like; when the client detects the object storage requirement of the user, the client can directly store the object in which the user is interested into the database. As the object storage function is widely used, more and more objects are stored in the database; to save memory, users are often required to manually manage objects stored in a database to delete objects that are no longer of value. However, because the number of object files is large, it takes a lot of time and effort for a user to find a target object to be deleted each time the user deletes the object, and then the user deletes the target object. Therefore, the conventional object management method is low in convenience.

Disclosure of Invention

The embodiment of the application provides an object management method, an object management device, a client and a medium, which can perform storage management on a target object according to time length setting operation, realize automatic deletion of the target object and improve convenience.

In one aspect, an embodiment of the present application provides an object management method, where the object management method includes:

in response to a storage triggering event for a target object, displaying a duration setting interface of the target object on a user interface;

and storing the target object according to the time length setting operation detected in the time length setting interface.

In another aspect, an embodiment of the present application provides an object management apparatus, including:

the display unit is used for responding to a storage trigger event aiming at a target object and displaying a time length setting interface of the target object on a user interface;

and the processing unit is used for storing the target object according to the time length setting operation detected in the time length setting interface.

In another aspect, an embodiment of the present application provides a client, where the client includes an input interface and an output interface, and the client further includes:

a processor adapted to implement one or more instructions; and the number of the first and second groups,

a computer storage medium storing one or more instructions adapted to be loaded by the processor and to perform the steps of:

In yet another aspect, an embodiment of the present application provides a computer storage medium storing one or more instructions, where the one or more instructions are adapted to be loaded by a processor and execute the object management method described above.

The method and the device for setting the target object time length can respond to a storage triggering event aiming at the target object, and a time length setting interface of the target object is displayed on a user interface; and storing the target object according to the time length setting operation detected in the time length setting interface. The target object is stored according to the time length setting operation, so that the target object can be automatically deleted after the effective storage time length is obtained according to the time length setting operation; the target object is not required to be searched and deleted by the user with a great deal of time and energy, so that the complicated operation of human participation can be reduced to a certain extent, and the convenience of object management is improved.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

FIG. 1 is a schematic diagram of an object management scheme provided by an embodiment of the present application;

fig. 2 is a schematic flowchart of an object management method according to an embodiment of the present application;

FIG. 3a is a schematic diagram of a duration setting interface provided by an embodiment of the present application;

FIG. 3b is a schematic diagram of another duration setting interface provided by embodiments of the present application;

FIG. 3c is a schematic diagram of another duration setting interface provided by embodiments of the present application;

FIG. 4 is a flowchart illustrating an object management method according to another embodiment of the present application;

fig. 5a is an application scenario diagram of an object management method according to an embodiment of the present application;

fig. 5b is an application scenario diagram of another object management method provided in the embodiment of the present application;

fig. 5c is an application scenario diagram of another object management method provided in the embodiment of the present application;

fig. 5d is an application scenario diagram of another object management method provided in the embodiment of the present application;

fig. 5e is an application scenario diagram of another object management method provided in the embodiment of the present application;

fig. 5f is an application scenario diagram of another object management method provided in the embodiment of the present application;

fig. 5g is an application scenario diagram of another object management method provided in the embodiment of the present application;

fig. 5h is an application scenario diagram of another object management method provided in the embodiment of the present application;

fig. 5i is an application scenario diagram of another object management method provided in the embodiment of the present application;

fig. 6 is a schematic structural diagram of an object management apparatus according to an embodiment of the present application;

fig. 7 is a schematic structural diagram of a client according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application.

To help users better manage objects (e.g., images, documents, etc.) stored within a database, thereby enhancing the user experience; the embodiment of the application provides an object management scheme, and the object management scheme can be specifically executed by any client. In one embodiment, the client may refer to a terminal device (terminal for short), where the terminal may include but is not limited to: a portable terminal device such as a smart phone, a tablet computer, a laptop computer, or a desktop computer, etc. In another embodiment, the client may refer to an APP (application) running in the terminal, where the APP may include but is not limited to: the system comprises a browser APP, an instant messaging APP (such as Tencent QQ APP and WeChat APP), a content interaction platform APP (such as microblog APP) and the like. For convenience of illustration, the following clients are all described by taking APP running in the terminal as an example. Referring to fig. 1, an object management scheme proposed in the embodiment of the present application mainly includes two parts, namely object attribute saving and cleaning task scheduling; the working principle of each part is as follows:

(one) object property holding section:

in a specific implementation, when the client detects that the user is in a storage requirement for a certain object, the object may be obtained through step s 11. The client can also provide a time length setting interface for the user, so that the user can set the effective storage time length of the object through the time length setting interface; the effective storage duration here refers to a storage duration in which the object can be stored in the terminal. For example, if the object can be stored in the terminal for 2 days, the effective storage time of the object is 2 days. Accordingly, the client may obtain the valid storage duration of the object through step s12, and record the attribute information of the object through step s 13. Wherein, the attribute information at least comprises a storage starting time and an effective storage duration; the storage start time is a time when the object is stored in the terminal. For example, if an object is stored in the terminal on day 12, month 3 in 2019, the storage start time of the object is 12, month 3 in 2019. It should be understood that the storage start time may be as accurate as an hour, or a minute of second, depending on business requirements; for example, if an object is stored in the terminal 8:00 in the morning of 12/3/2019, the storage start time of the object is 8:00 in the morning of 12/3/2019. After recording the attribute information of the object, the client may store the object in the database through step s 14. It should be appreciated that the client may perform the above steps s11-s14 each time it stores an object; i.e. the database may include one or more objects and attribute information of the objects.

(II) a cleaning task scheduling part:

in the embodiment of the application, the cleaning tasks can be divided into real-time cleaning tasks and periodic cleaning tasks; the periodic cleaning task here means: and cleaning the objects in the database at a preset frequency. Wherein, the fixed frequency can be set according to the service requirement or experience value; for example, the fixed frequency may be set to perform 1 cleaning task per day (i.e., 24 hours), or 1 cleaning task every 8 hours, and so on. For convenience of illustration, the embodiment of the present application is described by taking a periodic cleaning task as an example. In a specific implementation, when the client stores the object, the client can automatically register a clock notification to the terminal system through the program code; by this clock notification implementation a periodic cleaning task is started, via step s15, each time a period of the cleaning task arrives. After the periodic cleaning task is started, the client may read the attribute information of each object in the database through step s 16. For any object, the client may obtain the stored duration of the any object, and determine whether the stored duration of the any object is greater than or equal to the valid storage duration of the any object through step s 17. If yes, indicating that any object is invalid, and cleaning (namely deleting) any object; at this point, the any object can be deleted through step s 18; if not, then either object may be retained via step s 19. It should be understood that the client may repeatedly execute the steps s17-s19 after reading the attribute information of each object through the step s16, thereby realizing that all failed objects in the database will be automatically deleted.

Therefore, according to the object management scheme provided by the embodiment of the application, the effective storage time length is set for each object, so that each object can be automatically deleted after the corresponding effective storage time length is passed, the invalid object stored in the database can be automatically cleared, and the convenience of object management is improved. In addition, by automatically deleting the invalid object, the complicated operation of manual participation can be reduced, the time and the energy of a user for cleaning the object are saved, and the user experience is effectively improved.

Based on the description of the object management scheme, an embodiment of the present application provides an object management method, which can be executed by the aforementioned client. Referring to fig. 2, the object management method may include the following steps S201 to S203:

s201, responding to a storage trigger event aiming at the target object, and displaying a time length setting interface of the target object on a user interface.

In the embodiment of the present application, the target object may include: a target image or a target document; the target image may include any one of: a screenshot image, a web page image, or a captured image, etc. The screen capture image is an image obtained by capturing a screen of current content displayed on the user interface, and the screen capture is an operation of capturing the current content within a visualization range displayed on the user interface to obtain an image including the current content within the visualization range. The webpage image refers to an image downloaded from the internet, such as an image downloaded from an application interface of a browser APP, an image downloaded from a session interface of an instant messaging APP, an image downloaded from a content sharing interface of a content interaction platform APP, and the like. The captured image refers to an image obtained by capturing an image by a camera component (such as a camera). The storage triggering event is an event for triggering the storage target object; specifically, if the target object is a target document, the storage triggering event of the target object may include: an event of saving a currently compiled target document, or an event of successfully downloading a target document from the internet. If the target image comprises a screenshot image, the storage triggering event for the target image may comprise: and responding to screen capture operation, and capturing the screen of the current content displayed in the user interface to obtain an event of a screen capture image. If the target image comprises a web page image, the storage triggering event of the target image may include: and responding to the storage operation, and successfully downloading the webpage image from the Internet. If the target image comprises a captured image, the storage triggering event for the target image may comprise: and responding to the shooting operation, and calling the camera shooting assembly to shoot the image to obtain the event of the shot image.

In particular implementations, the client may detect whether there is a trigger event for the target object. If the client detects a storage trigger event for the target object, a duration setting interface of the target object may be displayed on the user interface in response to the storage trigger event for the target object. The duration setting interface is an interface capable of providing duration setting service for a user; the duration setting interface may be an interface formed by a part of or all of the regions in the user interface, or may be an operation frame which is independent of the user interface and is displayed in the user interface, such as a duration setting menu; the following description will be given by taking the time length setting interface as a time length setting menu as an example. After the client displays the time length setting interface in the user interface, the user can execute corresponding time length setting operation in the time length setting interface, so that an effective storage time length is set for the target object. In one embodiment, the duration setting interface may include a duration selection area, and the duration selection area may include at least one candidate duration therein. The number and the value of the candidate durations can be set according to actual service requirements; for example, 4 candidate durations may be set, in turn: 1 day, 2 days, 7 days and 30 days as shown in figure 3 a. In this embodiment, the user may select one candidate duration from the at least one candidate duration as the valid storage duration of the target object; accordingly, the duration setting operation may include: selecting a duration selection operation for selecting an effective storage duration for the target object from the at least one candidate duration; the effective storage duration of the target object is the selected candidate duration.

In another embodiment, the duration setting interface may include a duration defining area; the duration definition area is used to set the effective storage duration of the target object, and may specifically include a start time definition area and an end time definition area, as shown in fig. 3 b. In this embodiment, the user may customize the start storage time of the target object in the start time definition area in the duration definition area and the end storage time of the target object in the end time definition area in the duration definition area 3012; in this case, the duration setting operation includes: a first setting operation and a second setting operation detected in the duration definition region; the first setting operation is used for setting the starting storage time of the target object, and the second setting operation is used for setting the ending storage time of the target object; the effective storage of the target object is the difference between the ending storage time and the starting storage time of the target object. Or the client can automatically acquire the initial storage time of the target object and fill the acquired initial storage time into the initial time setting area; in this case, the user can only need to customize the ending storage time of the target image in the ending time definition area in the duration definition area, so that the user operation can be saved; in this case, the duration setting operation may include only: a second setting operation detected in the duration definition region. In another embodiment, the duration setting interface may include a duration selection area and a duration definition area, as shown in fig. 3 c; in this embodiment, the duration setting operation may include: and selecting a duration selecting operation or a first setting operation and a second setting operation of the valid storage duration for the target object from the at least one candidate duration. It should be understood that the user may not perform any duration setting operation in the duration setting interface; then the client in this case may default the target object to be a permanently valid object.

S202, storing the target object according to the time length setting operation detected in the time length setting interface.

The client can detect the time length setting operation of the user in the time length setting interface and store the target object according to the time length setting operation. The client can also obtain the effective storage time length of the target image according to the time length setting operation detected in the time length setting interface; and setting an attribute field for the target object, and adding the initial storage time and the effective storage time length to the attribute field of the target object so as to detect whether the target object is invalid or not according to data in the attribute field of the target object. Wherein, if the duration setting operation includes: selecting a duration selection operation for selecting an effective storage duration for the target object from the at least one candidate duration; then, according to the duration setting operation detected in the duration setting interface, a specific implementation manner of obtaining the effective storage duration of the target image may be: determining a selected candidate duration from at least one candidate duration according to a duration selection operation detected in a duration setting interface; and determining the selected candidate duration as the effective storage duration of the target object. For example, the duration selection area of the duration setting interface includes 4 candidate durations, which are respectively: 1 day, 2 days, 7 days, and 30 days; if the user selects the option of "2 days", the client may use "2 days" as the effective storage duration of the target object. If the duration setting operation comprises: a first setting operation and a second setting operation detected in the duration definition region; then, according to the duration setting operation detected in the duration setting interface, a specific implementation manner of obtaining the effective storage duration of the target image may be: acquiring initial storage time of the target object according to a first setting operation detected in the duration definition area, and acquiring ending storage time of the target object according to a second setting operation detected in the duration definition area; and calculating to obtain the effective storage duration of the target object according to the ending storage time and the starting storage time. The effective storage time length can be obtained by calculating the difference between the ending storage time and the starting storage time; for example, if the ending storage time is 12/5/2019, the starting storage time is 12/3/2019, and the difference between the ending storage time and the starting storage time is 2 days, the effective storage duration of the target object is 2 days. It should be noted that all the effective storage time periods mentioned in the embodiments of the present application are described in units of "days"; in practical applications, however, the unit of the effective storage time period may be accurate to an hour or a minute or a second according to an empirical value or a traffic demand.

The client can also detect whether the target object is invalid or not according to the effective storage duration of the target object, wherein the effective storage duration of the target object is obtained according to duration setting operation. If the target object is invalid, deleting the target object; otherwise, the target object may continue to be stored. The step of detecting whether the target object is invalid or not according to the effective storage duration of the target object may include at least the following two specific implementations:

in a first specific implementation, a stored duration of the target object may be obtained, where the stored duration may be obtained by calculating a difference between a current system time of the terminal and an initial storage time of the target object. For example, if the current system time of the terminal is 12/4/2019, and the initial storage time is 12/3/2019, the difference between the current system time and the initial storage time is 1 day, and the stored time length of the target object is 1 day. If the stored time length is greater than or equal to the effective storage time length of the target object, determining that the target object is invalid; otherwise, determining that the target object is not invalid.

In a second specific implementation, the ending storage time of the target object can be determined according to the effective storage duration and the starting storage time of the target object; if the current system time of the terminal is greater than or equal to the end storage time, determining that the target object is invalid; otherwise, determining that the target object is not invalid. It should be noted that, in the second specific implementation, if the duration setting operation includes a second setting operation for setting an ending storage time of the target object, that is, the client may directly obtain the ending storage time according to the duration setting operation, the step of determining the ending storage time of the target object according to the valid storage duration and the starting storage time may not be performed in the second specific implementation.

Please refer to fig. 4, which is a flowchart illustrating another object management method according to an embodiment of the present application. The object management method may be performed by the above-mentioned client. Referring to fig. 4, the object management method may include the following steps S401 to S406:

s401, responding to a storage trigger event aiming at the target object, and displaying a duration setting interface of the target object on a user interface.

In particular implementations, the client may display a duration setting entry for the target object in the user interface in response to a storage triggering event for the target object. For example, taking a target object as a screen capture image as an example; when the user browses the atlas content in the internet or the atlas content local to the terminal by using the browser, the screen capture operation can be performed on the content displayed on the user interface. Correspondingly, the client can respond to the screen capture operation and capture the current content displayed in the user interface to obtain a screen capture image; after the screenshot is obtained, it may be considered that a storage triggering event for the target object (i.e., the screenshot) is detected, and a duration setting entry may be displayed in the user interface, as shown in fig. 5 a. Optionally, when the target object is a screenshot image, the client may further generate a preview image of the screenshot image in response to a storage trigger event for the screenshot image; and the preview image may be displayed in a user interface. The specific implementation of generating the preview image of the screenshot image may be: compressing the screenshot image according to a preset compression ratio to obtain a preview image; in this embodiment, a schematic diagram of displaying the preview image can be seen in fig. 5 b. Or, if the user interface includes a first display area and a second display area; the first display area is used for displaying data contents (such as image contents and character contents), and the second display area is used for displaying user operation icons; the screen capture image obtained by capturing the current content displayed by the user interface may include: the data content in the first display area and the user operation icon in the second display area. In this case, a specific embodiment of generating the preview image of the screenshot image may be: performing image cutting processing on the screen capture image according to the first display area to obtain an intermediate image, wherein the intermediate image comprises data content in the first display area; then, compressing the intermediate image to obtain a preview image; in this embodiment, a schematic diagram of displaying the preview image can be seen as shown in fig. 5 c.

After the client displays the time length setting entry, the user can execute a trigger operation on the time length setting entry to trigger the client to display a time length setting interface; triggering operations herein may include, but are not limited to: click operations, press operations, and the like. Accordingly, if the client detects the trigger operation for the duration setting entry, the client may display the duration setting interface of the target object on the user interface in response to the trigger operation for the duration setting entry, as shown in fig. 5 d. After the client displays the duration setting interface, the user can execute a corresponding duration setting operation in the duration setting interface and click a determination button in the duration setting interface to trigger the client to store the target object according to the duration setting operation detected in the duration setting interface through the step S402; the duration setting operation herein may include: a duration selection operation, or a first setting operation and a second setting operation. Taking the time length setting operation including the time length selecting operation as an example, if the user selects the candidate time length of "7 days" and clicks the determination button, the client may be triggered to set the operation according to the time length detected in the time length setting interface, store the target object, and automatically delete the target object after "7 days".

S402, storing the target object according to the time length setting operation detected in the time length setting interface.

After the client stores the target object, the client can also generate storage prompt information of the target object according to the effective storage duration of the target object, wherein the effective storage duration of the target object is obtained according to duration setting operation; the storage prompting information is used for prompting the stored target object, and the target object is deleted after the effective storage time length. Then, the storage prompt information is displayed in the user interface. Wherein, the storage prompt information can be presented in the user interface in a toast (simple message prompt box) prompt mode; the storage prompt message may automatically disappear after displaying for a fixed duration (e.g., 1 second, 5 seconds, etc.). For example, taking the target object as the target image and the effective storage duration of the target image is "7 days", the storage prompt message may be "saved image, which is to be deleted after 7 days", as shown in fig. 5 e.

After the client stores the target object, the stored time length of the target image can be obtained, and whether the stored time length of the target image is larger than or equal to the effective storage time length of the target object or not is detected. If the stored time length is greater than or equal to the effective storage time length of the target object, determining that the target object is invalid, and deleting the target object; otherwise, it may be determined that the target object is not stale and the target object continues to be stored. Optionally, the client in the embodiment of the present application may further support an early warning prompt function; by the early warning prompting function, the user can be prompted that the target object is about to be deleted when the target object reaches the first 1 day or a certain specific time (such as the first 5 hours of the target object being deleted). The specific process of implementing the warning prompt function by the client may be seen in the following steps S403 to S406.

S403, determining the remaining storage duration of the target object according to the stored duration and the effective storage duration of the target object; the effective storage time length of the target object is obtained according to the time length setting operation.

And S404, detecting an early warning prompt event of the target object according to the remaining storage duration.

In the specific implementation process of steps S403-S404, a difference between the valid storage duration and the stored duration of the target object may be calculated to obtain a remaining storage duration of the target object; then, an early warning prompt event of the target object can be detected according to the remaining storage duration. Specifically, if the stored duration of the target object is obtained in a real-time obtaining manner, the specific implementation of step S404 may be: detecting whether the residual storage time length is less than or equal to a preset time length threshold value or not; if the residual storage time is less than or equal to a preset time threshold, determining that an early warning prompt event of the target object is detected; otherwise, determining that the early warning prompting event is not detected. The preset duration threshold may be set according to an empirical value or a service requirement, for example, the preset duration threshold may be set to be 1 day or 5 hours. If the stored duration of the target object is obtained through the periodic obtaining manner, the specific implementation of step S404 may be: detecting whether the residual storage time length is less than or equal to the period time length corresponding to the periodic acquisition mode; if the residual storage duration is less than or equal to the period duration, determining that an early warning prompt event of the target object is detected; otherwise, determining that the early warning prompting event is not detected.

S405, if the early warning prompt event of the target object is detected, early warning prompt information of the target object is generated.

In a specific implementation, if the stored time of the target object is acquired in a real-time acquisition manner, and the early warning prompt event includes that the remaining storage time is less than or equal to a preset time threshold, the early warning prompt information can be generated according to the remaining storage time; the early warning prompt information in this case may be used to prompt that the target object is to be deleted after the remaining storage period has elapsed. For example, if the target object is a target image and the remaining storage time of the target image is "5 hours", the warning prompt message may be "the target image is to be deleted after 5 hours"; for another example, if the target object is a target document and the remaining storage time of the target document is "15 hours", the warning notice information may be "the target document is to be deleted after 15 hours". If the stored time length of the target object is acquired in a periodic acquisition mode, and the early warning prompt event comprises that the residual storage time length is less than or equal to the period time length corresponding to the periodic acquisition mode, generating early warning prompt information according to the period time length; the early warning prompt information in this case may be used to prompt that the target object is to be deleted after the period duration has elapsed. For example, if the target object is a target image, the remaining storage time of the target image is "5 hours", and the period time is "1 day", the warning prompt message may be "the target image is to be deleted after 1 day" or "an image is to be deleted after 1 day"; for another example, if the target object is a target document, and the remaining storage time of the target document is "15 hours" and the period time is "1 day", the warning notice information may be "the target document is to be deleted after 1 day" or "the document is to be deleted after 1 day".

S406, early warning prompt information is displayed in the user interface.

After the client generates the early warning prompt information, the early warning prompt information can be displayed in a user interface. In specific implementation, the client can display the early warning prompt information in the form of a headup prompt bar or a system notification bar message. The headup prompt bar is prompt information which can pop up at the top of the user interface when the user interface is lightened, and the headup prompt bar can automatically disappear after displaying fixed time (such as 1 second, 5 seconds and the like); the early warning prompt information is displayed in the form of the headup prompt bar, so that the attention of a user can be attracted, and the effect of early warning prompt is enhanced. The system notification bar message is prompt information displayed in a system notification bar of the terminal, and the system notification bar message disappears only after detecting the deletion operation of the user on the system notification bar message; the early warning prompt information is displayed in the form of the system notification bar message, so that the timeliness of the early warning prompt information can be improved, and a user can check the early warning prompt information through sliding down the system notification bar for a long time.

The early warning prompt information is mainly used for prompting the user that the target object is about to be deleted, and the user can usually view the target object in the scene. In order to facilitate that the user can directly view the target object after seeing the early warning prompt message, the client in the embodiment of the application may further set an object viewing entry in the early warning prompt message, so that the user can directly view the target object through the object viewing entry. Taking a target object as a screenshot image as an example, as shown in fig. 5f, the early warning prompt information displayed by the client includes an object viewing entry; and if the client detects a trigger operation (such as a click operation, a press operation and the like) aiming at the object viewing inlet, displaying the target image in the user interface.

In practical application, there may be a situation that a user does not want to delete a target object after viewing the target object; based on this, the embodiment of the application may provide a cancel delete button for the user while displaying the target object, so that the user may cancel the automatic deletion of the target object through the cancel delete button. Specifically, the client may display the target object and a cancel delete button in the user interface in response to a trigger operation for the object view entry; taking the target object as the screenshot image as an example, a schematic diagram of displaying the target object and the cancel delete button in the user interface may be shown in fig. 5 g. As can be seen from the foregoing, the valid storage duration is stored in the attribute field of the target object, and if the client detects the trigger operation for the cancel delete button, the valid storage duration is deleted from the attribute field, so as to implement setting the target object as a permanently valid object. Optionally, the client may also replace the valid storage duration in the attribute field with a permanently valid identifier (e.g., -1 ") to implement setting the target object as a permanently valid object; or, the client may add an attribute field for the target object to store the persistent valid identifier, and set the priority of the new attribute field to be higher than the priority of the attribute field for storing the valid storage duration, so as to set the target object as the persistent valid object.

In practical application, there may be a situation that a user wants to modify the effective storage duration of a target object after viewing the target object; based on this, the embodiment of the application may also provide a duration modification button for the user while displaying the target object, so that the user may modify the effective storage duration of the target object through the duration modification button. Specifically, the client may display a duration modification button in the user interface in response to a trigger operation for the object view portal; taking the target object as the target image as an example, a schematic diagram of the display duration modification button may be as shown in fig. 5 h. It should be understood that fig. 5h is only an exemplary diagram and is not intended to limit the specific content displayed by the user interface. In practical application, when responding to the trigger operation of the object viewing entry, the client only displays the target object and the duration modification button, and does not display the cancel deletion button. The user can execute triggering operation (such as clicking operation and pressing operation) on the time length modification button to trigger the client to display the time length modification interface; the duration modification interface may be an interface formed by a part of or all of the regions in the user interface, or may be an operation box which is independent of the user interface and is displayed in the user interface, such as a duration modification menu; the following description will be given by taking the time length modification interface as a time length modification menu as an example. Correspondingly, if the client detects the trigger operation for the duration modification button, the duration modification interface may be displayed in the user interface, as shown in fig. 5 i. The client can also update the effective storage duration in the attribute field according to the duration modification operation detected in the duration modification interface, and store the target object according to the updated effective storage duration.

Based on the description of the above embodiment of the object management method, the embodiment of the present invention further discloses an object management apparatus, which may be a computer program (including a program code) running in a client. The object management apparatus may perform the methods shown in fig. 1, 2, and 4. Referring to fig. 6, the object management apparatus may operate the following units:

a display unit 601, configured to display a duration setting interface of a target object on a user interface in response to a storage trigger event for the target object;

the processing unit 602 is configured to store the target object according to the duration setting operation detected in the duration setting interface.

In one embodiment, the duration setting interface includes a duration selection area, and the duration selection area includes at least one candidate duration; the duration setting operation includes: selecting a duration selection operation for selecting an effective storage duration for the target object from the at least one candidate duration; and the effective storage duration of the target object is the selected candidate duration.

In another embodiment, the duration setting interface includes a duration defining area, and the duration defining area is used to set the effective storage duration of the target object; the duration setting operation includes: a first setting operation and a second setting operation detected in the duration definition area; the first setting operation is used for setting the starting storage time of the target object, and the second setting operation is used for setting the ending storage time of the target object; the effective storage of the target object is the difference between the ending storage time and the starting storage time of the target object.

In yet another embodiment, the processing unit 602 is further configured to: detecting whether the target object is invalid or not according to the effective storage duration of the target object, wherein the effective storage duration of the target object is obtained according to the duration setting operation; if the target object is invalid, deleting the target object; otherwise, storing the target object.

In another embodiment, when the processing unit 602 is configured to detect whether the target object fails according to the valid storage duration of the target object, it may specifically be configured to: acquiring the stored duration of the target object; if the stored time length is greater than or equal to the effective storage time length of the target object, determining that the target object is invalid; otherwise, determining that the target object is not invalid.

In yet another embodiment, the processing unit 602 is further configured to: acquiring the stored time length of the target image, and determining the remaining storage time length of the target object according to the stored time length and the effective storage time length of the target object; the effective storage time length of the target object is obtained according to the time length setting operation; detecting an early warning prompt event of the target object according to the residual storage duration; if the early warning prompt event of the target object is detected, generating early warning prompt information of the target object; the display unit 601 may also be configured to: and displaying the early warning prompt information in the user interface.

In another embodiment, the stored duration of the target object is obtained by a real-time obtaining manner; correspondingly, when the processing unit 602 is configured to detect the early warning event of the target object according to the remaining storage duration, it may specifically be configured to: detecting whether the residual storage time length is less than or equal to a preset time length threshold value or not; if the residual storage time length is less than or equal to the preset time length threshold value, determining that an early warning prompt event of the target object is detected; otherwise, determining that the early warning prompting event is not detected; and the early warning prompt information is used for prompting that the target object is deleted after the residual storage time length.

In another embodiment, the stored duration of the target object is obtained by a periodic obtaining manner; correspondingly, when the processing unit 602 is configured to detect the early warning event of the target object according to the remaining storage duration, it may specifically be configured to: detecting whether the residual storage time length is less than or equal to the period time length corresponding to the periodic acquisition mode; if the residual storage duration is less than or equal to the period duration, determining that an early warning prompt event of the target object is detected; otherwise, determining that the early warning prompting event is not detected; and the early warning prompt information is used for prompting that the target object is deleted after the period duration.

In another embodiment, the valid storage duration is stored in an attribute field of the target object, and the early warning prompt information includes an object viewing entry; accordingly, the display unit 601 may also be configured to: in response to a triggering operation for the image viewing portal, displaying the target object and a cancel delete button in the user interface; the processing unit 602 may also be configured to: and if the trigger operation aiming at the cancel deletion button is detected, deleting the effective storage duration from the attribute field.

In still another embodiment, the display unit 601 may further be configured to: in response to a triggering operation for the object view portal, displaying a duration modification button in the user interface; if the trigger operation aiming at the duration modification button is detected, displaying the duration modification interface in the user interface; the processing unit 602 may also be configured to: and updating the effective storage time length in the attribute field according to the time length modification operation detected in the time length modification interface, and storing the target object according to the updated effective storage time length.

In yet another embodiment, the processing unit 602 is further configured to: generating storage prompt information of the target object according to the effective storage duration of the target object, wherein the effective storage duration of the target object is obtained according to the duration setting operation; the storage prompt information is used for prompting that the target object is stored, and the target object is deleted after the effective storage time length; the display unit 601 may also be used to: and displaying the storage prompt information in the user interface.

In another embodiment, when the display unit 601 is configured to display a duration setting interface of a target object on the user interface in response to a storage triggering event for the target object, it may specifically be configured to: in response to a storage triggering event for a target object, displaying a duration setting entry of the target object in the user interface; and responding to the trigger operation aiming at the duration setting inlet, and displaying a duration setting interface of the target object on the user interface.

In another embodiment, the target object is a screenshot image, and the storage triggering event of the target object includes: responding to screen capture operation, and capturing the screen of the current content displayed in the user interface to obtain an event of a screen capture image; accordingly, the processing unit 602 may be further configured to: generating a preview image for a screenshot image in response to a storage trigger event for the screenshot image; the display unit 601 may also be used to: displaying the preview image in the user interface.

According to an embodiment of the present invention, each step involved in the methods shown in fig. 1, fig. 2 and fig. 4 may be executed by each unit in the object management device shown in fig. 6. For example, steps S201 to S202 shown in fig. 2 may be performed by the display unit 601 and the processing unit 602 shown in fig. 6, respectively; as another example, steps S401 and S406 shown in fig. 4 may be performed by the display unit 601 shown in fig. 6, and steps S402 to S405 may be performed by the processing unit 602 shown in fig. 6.

According to another embodiment of the present invention, the units in the object management apparatus shown in fig. 6 may be respectively or entirely combined into one or several other units to form the object management apparatus, or some unit(s) thereof may be further split into multiple functionally smaller units to form the object management apparatus, which may achieve the same operation without affecting the achievement of the technical effect of the embodiment of the present invention. The units are divided based on logic functions, and in practical application, the functions of one unit can be realized by a plurality of units, or the functions of a plurality of units can be realized by one unit. In other embodiments of the present invention, the object-based management apparatus may also include other units, and in practical applications, these functions may also be implemented by being assisted by other units, and may be implemented by cooperation of a plurality of units.

According to another embodiment of the present invention, the object management apparatus device shown in fig. 6 may be constructed by running a computer program (including program codes) capable of executing the steps involved in the respective methods shown in fig. 1, fig. 2, and fig. 4 on a general-purpose computing device such as a computer including a processing element such as a Central Processing Unit (CPU), a random access storage medium (RAM), a read only storage medium (ROM), and a storage element, and implementing the object management method of the embodiment of the present invention. The computer program may be recorded on a computer-readable recording medium, for example, and loaded and executed in the above-described computing apparatus via the computer-readable recording medium.

Based on the description of the method embodiment and the device embodiment, the embodiment of the invention also provides the client. Referring to fig. 7, the client includes at least a processor 701, an input interface 702, an output interface 703, and a computer storage medium 704. Wherein the computer storage medium 704 is configured to store a computer program comprising program instructions, and the processor 701 is configured to execute the program instructions stored by the computer storage medium 704. If the client is a terminal device, the processor 701 may be a Central Processing Unit (CPU), and the computer storage medium 704 may be directly stored in a memory of the client. If the client is an APP running in the terminal device, the processor 701 may be a microprocessor, and the computer storage medium 704 may be stored in a memory of the terminal device where the client is located.

The processor 701 is a computing core and a control core of the client, and is adapted to implement one or more instructions, and in particular, to load and execute the one or more instructions to implement a corresponding method flow or a corresponding function; in one embodiment, the processor 701 according to an embodiment of the present invention may be configured to perform a series of image management processes, including: in response to a storage triggering event for a target object, displaying a duration setting interface of the target object on a user interface; and storing the target object according to the duration setting operation detected in the duration setting interface, and the like.

The embodiment of the invention also provides a computer storage medium (Memory), which is a Memory device in the client and used for storing programs and data. It is understood that the computer storage medium herein may include both a built-in storage medium in the client and, of course, an extended storage medium supported by the client. Within which may be stored one or more instructions, which may be one or more computer programs (including program code), suitable for loading and execution by processor 701. The computer storage medium may be a high-speed RAM memory, or may be a non-volatile memory (non-volatile memory), such as at least one disk memory; and optionally at least one computer storage medium located remotely from the processor.

In one embodiment, one or more instructions stored in a computer storage medium may be loaded and executed by processor 701 to perform the corresponding steps described above with respect to the method in the image management embodiment; in particular implementations, one or more instructions in the computer storage medium are loaded by processor 701 and perform the following steps:

In yet another embodiment, the one or more instructions may be further loaded and specifically executed by the processor 701: detecting whether the target object is invalid or not according to the effective storage duration of the target object, wherein the effective storage duration of the target object is obtained according to the duration setting operation; if the target object is invalid, deleting the target object; otherwise, storing the target object.

In another embodiment, when detecting whether the target object is invalid according to the valid storage duration of the target object, the one or more instructions are loaded and specifically executed by the processor 701: acquiring the stored duration of the target object; if the stored time length is greater than or equal to the effective storage time length of the target object, determining that the target object is invalid; otherwise, determining that the target object is not invalid.

In yet another embodiment, the one or more instructions may be further loaded and specifically executed by the processor 701: acquiring the stored duration of the target object, and determining the remaining storage duration of the target object according to the stored duration and the effective storage duration; the effective storage time length of the target object is obtained according to the time length setting operation; detecting an early warning prompt event of the target object according to the residual storage duration; if the early warning prompt event of the target object is detected, generating early warning prompt information of the target object; and displaying the early warning prompt information in the user interface.

In another embodiment, the stored duration of the target object is obtained by a real-time obtaining manner; correspondingly, when the early warning prompt event of the target object is detected according to the remaining storage duration, the one or more instructions are loaded and specifically executed by the processor 701: detecting whether the residual storage time length is less than or equal to a preset time length threshold value or not; if the residual storage time length is less than or equal to the preset time length threshold value, determining that an early warning prompt event of the target object is detected; otherwise, determining that the early warning prompting event is not detected; and the early warning prompt information is used for prompting that the target object is deleted after the residual storage time length.

In another embodiment, the stored duration of the target object is obtained by a periodic obtaining manner; correspondingly, when the early warning prompt event of the target object is detected according to the remaining storage duration, the one or more instructions are loaded and specifically executed by the processor 701: detecting whether the residual storage time length is less than or equal to the period time length corresponding to the periodic acquisition mode; if the residual storage duration is less than or equal to the period duration, determining that an early warning prompt event of the target object is detected; otherwise, determining that the early warning prompting event is not detected; and the early warning prompt information is used for prompting that the target object is deleted after the period duration.

In another embodiment, the valid storage duration is stored in an attribute field of the target object, and the early warning prompt information includes an object viewing entry; accordingly, the one or more instructions may also be loaded and specifically executed by processor 701: in response to a triggering operation for the object view portal, displaying the target object and a cancel delete button in the user interface; and if the trigger operation aiming at the cancel deletion button is detected, deleting the effective storage duration from the attribute field.

In yet another embodiment, the one or more instructions may be further loaded and specifically executed by the processor 701: in response to a triggering operation for the object view portal, displaying a duration modification button in the user interface; if the trigger operation aiming at the duration modification button is detected, displaying the duration modification interface in the user interface; and updating the effective storage time length in the attribute field according to the time length modification operation detected in the time length modification interface, and storing the target object according to the updated effective storage time length.

In yet another embodiment, the one or more instructions may be further loaded and specifically executed by the processor 701: generating storage prompt information of the target object according to the effective storage duration of the target object, wherein the effective storage duration of the target object is obtained according to the duration setting operation; the storage prompt information is used for prompting that the target object is stored, and the target object is deleted after the effective storage time length; and displaying the storage prompt information in the user interface.

In another embodiment, when the duration setting interface of the target object is displayed on the user interface in response to a storage triggering event for the target object, the one or more instructions are loaded and specifically executed by the processor 701: in response to a storage triggering event for a target object, displaying a duration setting entry of the target object in the user interface; and responding to the trigger operation of the duration setting inlet, and displaying a duration setting interface of the target image on the user interface.

In another embodiment, the target object is a screenshot image, and the storage triggering event of the target object includes: responding to screen capture operation, and capturing the screen of the current content displayed in the user interface to obtain an event of a screen capture image; accordingly, the one or more instructions may also be loaded and specifically executed by processor 701: generating a preview image for the screenshot image in response to a storage trigger event for the screenshot image; displaying the preview image in the user interface.

The above disclosure is only for the purpose of illustrating the preferred embodiments of the present invention, and it is therefore to be understood that the invention is not limited by the scope of the appended claims.

Claims

1. An object management method, comprising:

2. The method of claim 1, wherein the duration setting interface comprises a duration selection area, the duration selection area including at least one candidate duration therein;

the duration setting operation includes: selecting a duration selection operation for selecting an effective storage duration for the target object from the at least one candidate duration; and the effective storage duration of the target object is the selected candidate duration.

3. The method of claim 1, wherein the duration setting interface comprises a duration defining area for setting a valid storage duration of the target object;

the duration setting operation includes: a first setting operation and a second setting operation detected in the duration definition area; the first setting operation is used for setting the starting storage time of the target object, and the second setting operation is used for setting the ending storage time of the target object; the effective storage of the target object is the difference between the ending storage time and the starting storage time of the target object.

4. The method of any one of claims 1-3, further comprising:

detecting whether the target object is invalid or not according to the effective storage duration of the target object, wherein the effective storage duration of the target object is obtained according to the duration setting operation;

if the target object is invalid, deleting the target object; otherwise, storing the target object.

5. The method of claim 4, wherein the detecting whether the target object is invalid according to the valid storage duration of the target object comprises:

acquiring the stored duration of the target object;

if the stored time length is greater than or equal to the effective storage time length of the target object, determining that the target object is invalid; otherwise, determining that the target object is not invalid.

6. The method of any one of claims 1-3, further comprising:

acquiring the stored time length of the target object, and determining the remaining storage time length of the target object according to the stored time length and the effective storage time length of the target object; the effective storage time length of the target object is obtained according to the time length setting operation;

detecting an early warning prompt event of the target object according to the residual storage duration;

if the early warning prompt event of the target object is detected, generating early warning prompt information of the target object; and displaying the early warning prompt information in the user interface.

7. The method of claim 6, wherein the stored duration of the target object is obtained by a real-time acquisition; the detecting the early warning prompt event of the target object according to the remaining storage duration includes:

detecting whether the residual storage time length is less than or equal to a preset time length threshold value or not;

if the residual storage time length is less than or equal to the preset time length threshold value, determining that an early warning prompt event of the target object is detected; otherwise, determining that the early warning prompting event is not detected;

and the early warning prompt information is used for prompting that the target object is deleted after the residual storage time length.

8. The method of claim 6, wherein the stored duration of the target object is obtained by a periodic acquisition; the detecting the early warning prompt event of the target object according to the remaining storage duration includes:

detecting whether the residual storage time length is less than or equal to the period time length corresponding to the periodic acquisition mode;

if the residual storage duration is less than or equal to the period duration, determining that an early warning prompt event of the target object is detected; otherwise, determining that the early warning prompting event is not detected;

and the early warning prompt information is used for prompting that the target object is deleted after the period duration.

9. The method of claim 6, wherein the valid storage duration is stored in an attribute field of the target object, wherein the warning alert message includes an object view entry, and wherein the method further comprises:

in response to a triggering operation for the object view portal, displaying the target object and a cancel delete button in the user interface;

and if the trigger operation aiming at the cancel deletion button is detected, deleting the effective storage duration from the attribute field.

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

in response to a triggering operation for the object view portal, displaying a duration modification button in the user interface;

if the trigger operation aiming at the duration modification button is detected, displaying the duration modification interface in the user interface;

and updating the effective storage time length in the attribute field according to the time length modification operation detected in the time length modification interface, and storing the target object according to the updated effective storage time length.

11. The method of any one of claims 1-3, further comprising:

generating storage prompt information of the target object according to the effective storage duration of the target object, wherein the effective storage duration of the target object is obtained according to the duration setting operation; the storage prompt information is used for prompting that the target object is stored, and the target object is deleted after the effective storage time length;

and displaying the storage prompt information in the user interface.

12. The method of claim 1, wherein the displaying a duration setting interface for a target object on the user interface in response to a storage triggering event for the target object comprises:

in response to a storage triggering event for a target object, displaying a duration setting entry of the target object in the user interface;

and responding to the trigger operation aiming at the duration setting inlet, and displaying a duration setting interface of the target object on the user interface.

13. The method of claim 12, wherein the target object is a screenshot image, the storage triggering event for the target object comprising: responding to screen capture operation, and capturing the screen of the current content displayed in the user interface to obtain an event of a screen capture image; the method further comprises the following steps:

generating a preview object for the screenshot image in response to a storage trigger event for the screenshot image;

displaying the preview image in the user interface.

14. An object management apparatus, comprising:

15. A client, comprising an input interface and an output interface, further comprising:

a computer storage medium having stored thereon one or more instructions adapted to be loaded by the processor and to execute the object management method of any of claims 1-13.