CN114579942B

CN114579942B - Data management method, system and storage medium

Info

Publication number: CN114579942B
Application number: CN202210210836.9A
Authority: CN
Inventors: 朱文豪; 王炳洋
Original assignee: Beijing Dajia Internet Information Technology Co Ltd
Current assignee: Beijing Dajia Internet Information Technology Co Ltd
Priority date: 2022-03-04
Filing date: 2022-03-04
Publication date: 2024-08-13
Anticipated expiration: 2042-03-04
Also published as: CN114579942A

Abstract

The disclosure relates to a data management method, a system and a storage medium, and belongs to the technical field of computers. The method comprises the following steps: acquiring description data of an object, and determining the object as an alternative object; converting the object from the candidate object into a potential object in case the description data passes authentication, wherein the potential object is an object with possibility of generating behavior data; in the case where the behavior data of the object is acquired, the object is converted from the potential object into a first object, which refers to an object that has generated behavior data and is not managed by other objects. The method provides a division standard for the stage where the object is located, the object is defined as an alternative object, a potential object and a first object according to the division standard, the object is defined based on the stage where the object is located, and the definition of the object based on the stage where the object is located has universality.

Description

Data management method, system and storage medium

Technical Field

The present disclosure relates to the field of computer technologies, and in particular, to a data management method, system, and storage medium.

Background

With the development of computer technology, an enterprise typically manages an enterprise-related object, which is a person, an enterprise, or an organization, etc., through a data management system. During the management process, the objects may be in different phases. Therefore, how to determine the type of an object based on the stage in which the object is located is a problem to be solved.

Disclosure of Invention

The present disclosure provides a data management method, system and storage medium, and proposes a division standard for a stage where an object is located, so as to define the object based on the stage where the object is located, and have universality for the definition of the object.

According to an aspect of the embodiments of the present disclosure, there is provided a data management method, the method including:

Acquiring description data of an object, and determining the object as an alternative object;

Converting the object from the candidate object into a potential object in case the description data passes authentication, wherein the potential object is an object with possibility of generating behavior data;

In the case where the behavior data of the object is acquired, the object is converted from the potential object into a first object, which refers to an object that has generated behavior data and is not managed by other objects.

In some embodiments, after the converting the object from the potential object to the first object in the case where the behavior data of the object is acquired, the method further includes:

And converting the first object into a second object managed by the third object when the first object and the third object establish an association relationship, wherein the second object refers to an object which generates behavior data and is managed by other objects.

In some embodiments, after the converting the first object to a second object managed by the third object, the method further comprises:

and deleting the association relation established by the object and the third object under the condition that the behavior data is not generated within a first preset time period after the first object is converted into the second object, and converting the object from the second object into the first object.

In some embodiments, after the converting the object from the potential object to the first object, the method further comprises:

and re-determining the object as the candidate object under the condition that no behavior data is generated within a second preset time period after the object is converted into the first object.

In some embodiments, the description data includes object identity data, and the method further comprises, in the event that the description data is authenticated, prior to converting the object from the candidate object to a potential object:

In the case that the object identity data is included in the determination database, the description data is determined to be authenticated.

In some embodiments, the method further comprises:

And counting the behavior data generated by the object to obtain a data chart of the object, wherein the data chart is used for reflecting the behavior data of the object.

In some embodiments, the determining the object as an alternative object includes:

storing the object corresponding to the type of the candidate object;

the converting the object from the candidate object to a potential object includes:

Replacing the candidate object type stored corresponding to the object with a potential object type;

the converting the object from the potential object to a first object includes:

And replacing the potential object type stored corresponding to the object with the first object type.

In some embodiments, the method further comprises:

And under the condition that the first object and the third object establish an association relationship, replacing the first object type stored corresponding to the object with the second object type.

According to still another aspect of the embodiments of the present disclosure, there is provided a data management system including: the system comprises an initial module, an object authentication module, a behavior data acquisition module and an object maintenance module;

The initial module is used for acquiring the description data and determining an object to which the description data belongs as an alternative object;

The object authentication module is used for authenticating the description data acquired by the initial module, and converting an object to which the description data belongs from the alternative object into a potential object under the condition that the description data passes authentication, wherein the potential object is an object with possibility of generating behavior data;

The behavior data acquisition module is used for acquiring behavior data corresponding to the object to which the description data belongs under the condition that the object authentication module authenticates the description data;

And the object maintenance module is used for converting the object to which the behavior data belongs from the potential object into a first object under the condition that the behavior data acquisition module acquires the behavior data, wherein the first object refers to an object which generates the behavior data and is not managed by other objects.

In some embodiments, the object maintenance module is further configured to, in a case where the first object and the third object establish an association relationship, convert the first object into a second object managed by the third object, where the second object refers to an object that has generated behavior data and is managed by other objects.

In some embodiments, the object maintenance module is further configured to delete the association relationship established between the object and the third object, and convert the object from the second object to the first object, where no behavior data is generated within a first preset period of time after the first object is converted to the second object.

In some embodiments, the object maintenance module is further configured to re-determine the object as the candidate object if no behavior data is generated within a second preset time period after the object is converted into the first object.

In some embodiments, the description data includes object identity data, and the object authentication module is configured to determine that the description data is authenticated if the object identity data is included in the determination database.

In some embodiments, the data management system further comprises a data processing module;

The data processing module is used for counting the behavior data generated by the object to obtain a data chart of the object, and the data chart is used for reflecting the behavior data of the object.

In some embodiments, the initial module is further configured to store the object in correspondence with an alternative object type;

the object authentication module is further configured to replace an alternative object type stored corresponding to the object with a potential object type if the description data passes authentication;

The object maintenance module is further configured to replace a potential object type stored corresponding to the object with a first object type when the object behavior data acquisition module acquires behavior data.

In some embodiments, the object maintenance module is further configured to replace a first object type stored corresponding to the object with a second object type if the first object and the third object establish an association relationship.

According to still another aspect of the embodiments of the present disclosure, there is provided a data management system including:

One or more processors;

a memory for storing the one or more processor-executable instructions;

wherein the one or more processors are configured to perform the data management method of the above aspect.

According to still another aspect of the embodiments of the present disclosure, there is provided a computer-readable storage medium, which when executed by a processor of a data management system, causes the data management system to perform the data management method of the above aspect.

According to yet another aspect of embodiments of the present disclosure, there is provided a computer program product comprising a computer program that is executed by a processor to implement the data management method of the above aspect.

According to the technical scheme provided by the embodiment of the disclosure, a division standard for a stage where an object is located is provided, namely, an object in a stage where descriptive data is acquired is defined as an alternative object, an object in a stage where descriptive data authentication passes is defined as a potential object, and an object in a stage where behavioral data is generated is defined as a first object, so that the definition of the object based on the stage where the object is located is realized. In addition, the processes of acquiring the description data, authenticating the description data and generating the behavior data by the object can occur in various scenes, and the stages where the object is positioned are divided according to the processes, so that the definition of the object based on the stages is universal, and the method is suitable for various scenes.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the principles of the disclosure.

FIG. 1 is a schematic diagram of a data management system, according to an example embodiment.

Fig. 2 is a flow chart illustrating a method of data management according to an exemplary embodiment.

FIG. 3 is a flow chart illustrating another method of data management according to an exemplary embodiment.

FIG. 4 is a schematic diagram illustrating a transition of stages at which an object is located, according to an example embodiment.

FIG. 5 is a flow chart illustrating another method of data management according to an exemplary embodiment.

FIG. 6 is a flowchart illustrating another data management method according to an example embodiment.

Fig. 7 is a flow chart illustrating another data management method according to an exemplary embodiment.

Fig. 8 is a block diagram illustrating a structure of a terminal according to an exemplary embodiment.

Fig. 9 is a block diagram illustrating a structure of a server according to an exemplary embodiment.

Detailed Description

In order to enable those skilled in the art to better understand the technical solutions of the present disclosure, the technical solutions of the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings.

It should be noted that the terms "first," "second," and the like in the description of the present disclosure and the claims and the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the disclosure described herein may be capable of operation in sequences other than those illustrated or described herein. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present disclosure as detailed in the accompanying claims.

The terms "at least one", "a plurality", "each", "any" and the like as used in this disclosure include one, two or more, and a plurality includes two or more, each referring to each of the corresponding plurality, and any one refers to any one of the plurality. For example, the plurality of objects includes 3 objects, and each object refers to each of the 3 objects, and any one refers to any one of the 3 objects, which may be the first, the second, or the third.

The user data (including but not limited to user equipment information, user personal information, etc.) related to the present disclosure is information authorized by the user or sufficiently authorized by each party.

The data management method provided by the embodiment of the disclosure is executed by a data management system. Fig. 1 is a schematic diagram of a data management system including an initial module 101, an object authentication module 102, a behavioral data acquisition module 103, and an object maintenance module 104, according to an example embodiment. In the data management process, the initial module 101 acquires description data, determines an object to which the description data belongs as an alternative object, then the object authentication module 102 authenticates the description data acquired by the initial module 101, and in the case that the description data passes the authentication, the object to which the description data belongs is converted into a potential object from the alternative object, then the behavior data acquisition module 103 acquires behavior data, and the object maintenance module 104 converts the object to which the behavior data belongs from the potential object into a first object after acquiring the behavior data according to the module 103.

Optionally, the data management system further includes a data processing module 105, where the data processing module 105 can count behavior data generated by the object to obtain a data chart of the object.

In some embodiments, the data management system is a server that includes the above-described initialization module 101, object authentication module 102, behavior data acquisition module 103, object maintenance module 104, and data processing module 105.

FIG. 2 is a flowchart illustrating a method of data management, see FIG. 2, performed by a data management system, according to an exemplary embodiment, comprising the steps of:

In step 201, description data of an object is acquired, and the object is determined as an alternative object.

In the embodiment of the disclosure, the data management system determines the object as the candidate object when the description data of the object is acquired and the subsequent operation is not performed yet. Wherein the object refers to enterprises, individuals, organizations and the like, the description data of the object refers to data describing the object, the description data at least comprises an object identifier and a contact way of the object, and the alternative object refers to an object which does not determine whether the object is qualified for generating behavior data.

In step 202, in the event that the description data is authenticated, the object is converted from an alternative object to a potential object, the potential object being an object having a likelihood of generating behavioural data.

In order to ensure the security of the object, the object is converted from the candidate object into the potential object by authenticating the description data, i.e. determining that the object is secure in case the description data is authenticated, and deeming the object to qualify for generating the behavior data, i.e. having the possibility of generating the behavior data.

In step 203, in the case where the behavior data of the object is acquired, the object is converted from the potential object into a first object, which refers to an object that has generated the behavior data and is not managed by other objects.

Wherein behavior data refers to data generated based on operations performed by the object. In the case where the behavior data of the object is acquired, that is, the object is considered to have performed the corresponding operation, the object may be converted from the potential object into the first object at this time.

FIG. 3 is a flowchart illustrating another data management method, see FIG. 3, performed by a data management system, according to an exemplary embodiment, comprising the steps of:

In step 301, description data of an object is acquired, and the object is determined as an alternative object.

The object refers to enterprises, individuals, organizations and the like, the description data of the object refers to data describing the object, and the description data at least comprises an object identifier and a contact way of the object. For example, in the case where the object is a person, the description data of the object includes information such as a name, a contact address, and the like of the object; in the case that the object is an enterprise, the description data of the object includes information such as an enterprise name, an enterprise code, and the like of the object. An alternative object refers to an object that has not yet qualifyed to produce behavioral data.

In some embodiments, the data management system obtaining descriptive data for an object includes two cases: the first is that the data management system firstly acquires the description data of the object, and the second is that the data management system already stores the description data of the object, and updates the stored description data. For the second case, it is possible that the data management system has determined that the object is another type of object before updating the description data, but since it cannot be guaranteed whether the updated description data can be authenticated, in order to guarantee security, the object is again determined as an alternative object and then the subsequent management flow is performed.

In some embodiments, the data management system stores the object in correspondence with the candidate object type, thereby indicating that the object is determined to be a candidate object. Optionally, the object identifier of the object is stored corresponding to an alternative object type, or the contact way of the object is stored corresponding to the alternative object type, or the data capable of uniquely representing the object in the description data of the object is stored corresponding to the alternative object type.

In step 302, the description data is authenticated, and an authentication result is obtained.

In some embodiments, the description data includes object identity data, the data management system stores a database having stored therein secure object identity information, and the description data is compared with data in the database, and in the case that the object identity data in the description data is included in the database, the description data is determined to pass authentication. The object identity data is data uniquely representing the object, such as object identification, contact information and the like. For example, in the case where the object is an enterprise, the enterprise code in the description data is compared with the enterprise code in the database, and in the case where the credit code of the enterprise is stored in the database, the description data is considered to be authenticated.

According to the embodiment of the disclosure, the description data is authenticated, so that the object passing authentication can be ensured to generate the behavior data, and adverse effects caused by unsafe objects are avoided. For example, taking an object as an enterprise, when other enterprises select a partner, the object is determined to be an alternative object first, then description data of the object is authenticated, and if the authentication process finds that a credit code corresponding to the object is not stored in a database, subsequent cooperation is not performed, so that adverse effects are avoided, but if the credit code corresponding to the object is stored in the database, the object can be determined to be a potential object, and subsequent cooperation can be performed with the object.

In some embodiments, the data management system is capable of authenticating the description data of the object immediately after the description data is acquired; or the data management system performs unified authentication on the plurality of acquired description data after the last authentication is performed every fixed time length; or after a fixed time period after the description data of the object is acquired, authenticating the description data, and the embodiment of the disclosure does not limit the timing of authentication.

In the embodiment of the present disclosure, the authentication result includes that the authentication is passed or that the authentication is not passed, and in the case that the authentication is passed, step 303 is executed; in case the authentication is not passed, i.e. it means that the object is not a secure object, which may subsequently have adverse effects if interactive data is generated, it is thus determined that the object is currently an object that is not qualified for generating interactive data yet, i.e. the object is still an alternative object, and no further steps are performed, which object is still an alternative object.

In step 303, in the event that the description data is authenticated, the object is converted from an alternative object to a potential object.

Wherein the description data of the object indicates that the object qualifies for generating behavior data if the authentication is passed, i.e. the potential object has the possibility to generate behavior data.

In some embodiments, the data management system replaces the candidate object type stored corresponding to the object with the potential object type, thereby indicating that the object is determined to be a candidate object.

In step 304, the object is converted from the potential object to the first object in case behavior data of the object is obtained.

The behavior data is data generated based on an operation performed by an object, and includes data such as a behavior occurrence time, an object on which the operation performed by the object acts, and consumption generated by the object. For example, the object purchases an item, and the corresponding generated behavior data includes data of the purchased item, purchase time, and the like.

In some embodiments, the data management system replaces the potential object type stored corresponding to the object with the first object type, thereby indicating that the object is determined to be the first object.

In step 305, in the case where the first object establishes an association relationship with the third object, the first object is converted into a second object managed by the third object.

The second object is an object that has generated behavior data and is managed by another object, and the third object is any object different from the first object. Establishing the association relationship refers to binding the object with a third object. Optionally, the data capable of uniquely representing the object in the description data of the object is stored in correspondence with the object account corresponding to the third object, that is, it is determined that an association relationship is established between the object and the third object. For example, if the object is a person, the name of the object can be stored in association with the object account corresponding to the third object.

For example, the object refers to a customer that needs to be served, the third object refers to a serviceman a, and the customer can be bound with the serviceman a, and then the serviceman a can provide services for the customer.

In some embodiments, the data management system replaces a first object type stored corresponding to the object with a second object type, thereby indicating that the object is determined to be a second object.

In the embodiment of the disclosure, the third object can establish an association relationship with a plurality of first objects at the same time, and all the first objects establishing the association relationship with the third object are managed by the third object.

In step 306, if no behavior data is generated within the first preset time period after the first object is converted into the second object, the association relationship between the object and the third object is deleted, and the second object is converted into the first object.

The first preset time period is any time period, for example, the first preset time period is one day, one week, one month or other time periods. Because the second object is managed by the special third object, when the second object does not generate behavior data within a certain time, more management cost is generated for the third object, but corresponding benefits are not received, at the moment, the second object can be converted into the first object again by deleting the association relation between the first object and the third object, and because the first object does not need to be specially managed by the special object, the management cost is saved.

In some embodiments, the data management system replaces the second object type stored corresponding to the object with the first object type, thereby indicating that the object is converted to the first object.

In some embodiments, after the object is converted from the second object to the first object, the object can also establish an association relationship with other third objects again, that is, the object is converted from the first object to the second object managed by the other third objects again. Optionally, the association relationship with the other third object can be established only if the object generates new behavior data again.

In other embodiments, the object is redetermined as the candidate object in the event that no behavioral data is generated within a second preset time period after the object is converted to the first object. Wherein the second preset time period is longer than the first preset time period.

For the circulation process among the candidate object, the potential object, the first object and the second object in the above embodiment, the schematic representation shown in fig. 4 can be adopted, and referring to fig. 4, the candidate object can be converted into the potential object, the potential object can be converted into the first object, and the first object and the second object can be mutually converted. Alternatively, the candidate object, the potential object, the first object and the second object can be divided into two lifecycles, namely, the candidate object, the potential object, the transition from the potential object to the first object is taken as a front link lifecycle, and the mutual transition between the first object and the second object is taken as a back link lifecycle.

In another embodiment, the data management system is further capable of counting behavior data generated by the object to obtain a data chart of the object, wherein the data chart is used for reflecting the behavior data of the object. For example, the data graph may be a table, bar graph, pie chart, or other form. In the embodiment of the disclosure, since the behavior data generated by the object is dispersed, by counting the behavior data of the object, it is convenient to check all the behavior data of the object.

The above embodiment is described by taking any object as an example, and the type of the object can be determined by using the above embodiment for other objects.

In addition, in the data management process, only the management of the object is considered, and the actual service scene is not integrated in the management process, so that the separation of the object management and the service management is realized, and the object management can be focused.

In another embodiment, the data management system includes an initialization module, an object authentication module, a behavioral data acquisition module, an object maintenance module, and a data processing module. FIG. 5 is a flowchart illustrating a method of data management, see FIG. 5, performed by a data management system, the method comprising the steps of:

in step 501, an initial module obtains description data of an object and determines the object as an alternative object.

In some embodiments, the initial module stores the object in correspondence with the candidate object type.

In step 502, the object authentication module authenticates the description data to obtain an authentication result.

In some embodiments, the object authentication module determines that the description data is authenticated in the event that the description data includes object identity data in the description data in the determination database.

In step 503, the object authentication module converts the object from the candidate object to a potential object if the authentication result is authentication pass.

In some embodiments, the object authentication module is configured to replace an alternative object type stored corresponding to the object with a potential object type if the description data is authenticated.

In step 504, the behavioral data acquisition module acquires behavioral data of the object.

In step 505, the object maintenance module converts the object from the potential object to the first object if the behavior data acquisition module acquires the behavior data of the object, and converts the first object to the second object managed by the third object if the first object and the third object establish an association relationship.

In some embodiments, the object maintenance module replaces the potential object type stored corresponding to the object with the first object type if the object behavior data acquisition module acquires the behavior data; and the object maintenance module replaces the first object type stored corresponding to the object with the second object type under the condition that the first object and the third object establish an association relation.

In some embodiments, the object maintenance module deletes the association relationship established between the object and the third object and converts the object from the second object to the first object if no behavior data is generated within a first preset time period after the first object is converted to the second object.

In some embodiments, the object maintenance module redefines the object as the candidate object if no behavior data is generated within a second preset time period after the object is converted to the first object.

The embodiments of steps 501-505 are the same as the embodiments of steps 301-306 described above, and are not described in detail herein.

In step 506, the data processing module performs statistics on the behavior data generated by the object to obtain a data chart of the object.

In some embodiments, the data processing module includes a data acquisition sub-module, a data filtering sub-module, and a data analysis sub-module, wherein the data acquisition sub-module is configured to obtain behavioral data of the object from the other modules; the data filtering sub-module is used for filtering unimportant data in the acquired behavior data so as to reduce the data processing amount, for example, filtering out the behavior occurrence time in the behavior data; the data analysis sub-module is used for converting the filtered behavior data into a chart form.

And the data management system is divided into different modules, and the modules respectively realize different functions, so that a technician can separately develop the different modules, namely develop a plurality of modules in parallel when developing the data management system, thereby improving the development efficiency.

In addition, as the data management system does not add related functions of actual services, as long as the objects can be divided into the alternative objects, the potential objects, the first objects and the second objects in the subsequent multiple service scenes, the data management system provided by the embodiment of the disclosure can be used, so that multiplexing of the data management system is realized, and the data management system is not limited to be used in one service scene. And for the use of users, the functions of the data management system are simpler due to the management of the business, and the user can operate more conveniently during the use. And the code written when the data management system is developed can be reduced, so that the data management system corresponds to fewer codes, and the risk possibly caused by the codes is reduced.

In addition, the data management system only relates to the management of clients, and other functions related to actual services can be developed on the basis of the data management system in the subsequent actual application process, so that the data management system has high expandability and usability.

In addition, the above embodiments describe the data management process by using the data management system as an execution body, and in some embodiments, the data management system can provide a corresponding page for the terminal, and the data management process is implemented by interaction between the terminal and the management server. Fig. 6 is a flow chart illustrating another data management method, see fig. 6, performed interactively by a data management system and a terminal, the method comprising the steps of:

In step 601, the terminal displays a data acquisition interface.

The data acquisition interface is provided by the data management system for the terminal and is used for acquiring the description data of the object.

In step 602, the terminal transmits description data of the object acquired through the data acquisition interface to the data management system.

In some embodiments, the terminal sends the description data to an initial module in the data management system to cause the initial module to obtain the description data.

In step 603, the data management system receives description data for the object and determines the object as an alternative object.

In step 604, the data management system converts the object from the candidate object to a potential object if the description data passes authentication.

In step 605, the terminal displays a behavior acquisition interface.

The behavior acquisition interface is provided by the data management system for the terminal and is used for acquiring the behavior data of the object.

In step 606, the terminal transmits behavior data of the object acquired through the behavior acquisition interface to the data management system.

In some embodiments, the terminal sends the behavior data to a behavior data acquisition module in the data management system, so that the behavior data acquisition module acquires the behavior data.

In step 607, the data management system converts the object from the potential object to a first object if behavior data of the object is acquired, and converts the first object to a second object managed by a third object if the first object establishes an association with the third object.

In step 608, the data management system calculates behavior data generated by the object to obtain a data graph of the object.

In step 609, the terminal displays the data chart in the data presentation interface.

In some embodiments, the data display interface is further provided with a query field, and the user queries the description data, the behavior data and the data chart of the object by inputting the object identifier corresponding to the object to be queried in the query field. For example by entering the name of the object.

The above-described data management process will be described below by taking an object as a customer to be served as an example. FIG. 7 is a flowchart illustrating another data management method, see FIG. 7, performed by a data management system, according to an exemplary embodiment, the method comprising the steps of:

in step 701, description data of a client is acquired, and the client is determined as an alternative client.

In step 702, the description data is authenticated, and an authentication result is obtained.

In step 703, in the event that the authentication result is authentication pass, the client is converted from an alternative client to a potential client.

In step 704, the customer is converted from a potential customer to an open sea customer in the case of acquiring the consumption data of the customer, and the open sea customer is converted to a private sea customer managed by the service person in the case of establishing an association between the open sea customer and the service person.

In step 705, the consumer data generated by the object is counted to obtain a data chart for the customer.

The embodiments of steps 701-705 are the same as the embodiments of steps 301-306 described above, and are not repeated here.

Fig. 8 is a block diagram illustrating a structure of a terminal 800 according to an exemplary embodiment. The terminal 800 may be a portable mobile terminal such as: a smart phone, a tablet computer, an MP3 player (Moving Picture Experts Group Audio Layer III, motion picture expert compression standard audio plane 3), an MP4 (Moving Picture Experts Group Audio Layer IV, motion picture expert compression standard audio plane 4) player, a notebook computer, or a desktop computer. Terminal 800 may also be referred to by other names of user devices, portable terminals, laptop terminals, desktop terminals, and the like.

The terminal 800 includes: a processor 801 and a memory 802.

Processor 801 may include one or more processing cores, such as a 4-core processor, an 8-core processor, and the like. The processor 801 may be implemented in at least one hardware form of DSP (DIGITAL SIGNAL Processing), FPGA (Field-Programmable gate array), PLA (Programmable Logic Array ). The processor 801 may also include a main processor, which is a processor for processing data in an awake state, also referred to as a CPU (Central Processing Unit ), and a coprocessor; a coprocessor is a low-power processor for processing data in a standby state. In some embodiments, the processor 801 may integrate a GPU (Graphics Processing Unit, image processor) for rendering and drawing of content required to be displayed by the display screen. In some embodiments, the processor 801 may also include an AI (ARTIFICIAL INTELLIGENCE ) processor for processing computing operations related to machine learning.

Memory 802 may include one or more computer-readable storage media, which may be non-transitory. Memory 802 may also include high-speed random access memory, as well as non-volatile memory, such as one or more magnetic disk storage devices, flash memory storage devices. In some embodiments, a non-transitory computer readable storage medium in memory 802 is used to store at least one program code for execution by processor 801 to perform the operations performed by a terminal in the data management methods provided by the method embodiments in the present disclosure.

In some embodiments, the terminal 800 may further optionally include: a peripheral interface 803, and at least one peripheral. The processor 801, the memory 802, and the peripheral interface 803 may be connected by a bus or signal line. Individual peripheral devices may be connected to the peripheral device interface 803 by buses, signal lines, or a circuit board. Specifically, the peripheral device includes: at least one of radio frequency circuitry 804, a display 805, a camera assembly 806, audio circuitry 807, a positioning assembly 808, and a power supply 809.

Peripheral interface 803 may be used to connect at least one Input/Output (I/O) related peripheral to processor 801 and memory 802. In some embodiments, processor 801, memory 802, and peripheral interface 803 are integrated on the same chip or circuit board; in some other embodiments, either or both of the processor 801, the memory 802, and the peripheral interface 803 may be implemented on separate chips or circuit boards, which is not limited in this embodiment.

The Radio Frequency circuit 804 is configured to receive and transmit RF (Radio Frequency) signals, also known as electromagnetic signals. The radio frequency circuit 804 communicates with a communication network and other communication devices via electromagnetic signals. The radio frequency circuit 804 converts an electrical signal into an electromagnetic signal for transmission, or converts a received electromagnetic signal into an electrical signal. Optionally, the radio frequency circuit 804 includes: antenna systems, RF transceivers, one or more amplifiers, tuners, oscillators, digital signal processors, codec chipsets, subscriber identity module cards, and so forth. The radio frequency circuitry 804 may communicate with other terminals via at least one wireless communication protocol. The wireless communication protocol includes, but is not limited to: the world wide web, metropolitan area networks, intranets, generation mobile communication networks (2G, 3G, 4G, and 5G), wireless local area networks, and/or WiFi (WIRELESS FIDELITY ) networks. In some embodiments, the radio frequency circuitry 804 may also include NFC (NEAR FIELD Communication) related circuitry, which is not limited by the present disclosure.

The display 805 is used to display a UI (User Interface). The UI may include graphics, text, icons, video, and any combination thereof. When the display 805 is a touch display, the display 805 also has the ability to collect touch signals at or above the surface of the display 805. The touch signal may be input as a control signal to the processor 801 for processing. At this time, the display 805 may also be used to provide virtual buttons and/or virtual keyboards, also referred to as soft buttons and/or soft keyboards. In some embodiments, the display 805 may be one and disposed on a front panel of the terminal 800; in other embodiments, the display 805 may be at least two, respectively disposed on different surfaces of the terminal 800 or in a folded design; in other embodiments, the display 805 may be a flexible display disposed on a curved surface or a folded surface of the terminal 800. Even more, the display 805 may be arranged in an irregular pattern other than rectangular, i.e., a shaped screen. The display 805 may be made of LCD (Liquid CRYSTAL DISPLAY), OLED (Organic Light-Emitting Diode), or other materials.

The camera assembly 806 is used to capture images or video. Optionally, the camera assembly 806 includes a front camera and a rear camera. The front camera is arranged on the front panel of the terminal, and the rear camera is arranged on the back of the terminal. In some embodiments, the at least two rear cameras are any one of a main camera, a depth camera, a wide-angle camera and a tele camera, so as to realize that the main camera and the depth camera are fused to realize a background blurring function, and the main camera and the wide-angle camera are fused to realize a panoramic shooting and Virtual Reality (VR) shooting function or other fusion shooting functions. In some embodiments, the camera assembly 806 may also include a flash. The flash lamp can be a single-color temperature flash lamp or a double-color temperature flash lamp. The dual-color temperature flash lamp refers to a combination of a warm light flash lamp and a cold light flash lamp, and can be used for light compensation under different color temperatures.

Audio circuitry 807 may include a microphone and a speaker. The microphone is used for collecting sound waves of users and the environment, converting the sound waves into electric signals, inputting the electric signals to the processor 801 for processing, or inputting the electric signals to the radio frequency circuit 804 for voice communication. For stereo acquisition or noise reduction purposes, a plurality of microphones may be respectively disposed at different portions of the terminal 800. The microphone may also be an array microphone or an omni-directional pickup microphone. The speaker is used to convert electrical signals from the processor 801 or the radio frequency circuit 804 into sound waves. The speaker may be a conventional thin film speaker or a piezoelectric ceramic speaker. When the speaker is a piezoelectric ceramic speaker, not only the electric signal can be converted into a sound wave audible to humans, but also the electric signal can be converted into a sound wave inaudible to humans for ranging and other purposes. In some embodiments, audio circuit 807 may also include a headphone jack.

The location component 808 is utilized to locate the current geographic location of the terminal 800 for navigation or LBS (Location Based Service, location-based services). The positioning component 808 may be a positioning component based on the United states GPS (Global Positioning System ), the Beidou system of China, the Granati positioning system of Russia, or the Galileo positioning system of the European Union.

A power supply 809 is used to power the various components in the terminal 800. The power supply 809 may be an alternating current, direct current, disposable battery, or rechargeable battery. When the power supply 809 includes a rechargeable battery, the rechargeable battery may be a wired rechargeable battery or a wireless rechargeable battery. The wired rechargeable battery is a battery charged through a wired line, and the wireless rechargeable battery is a battery charged through a wireless coil. The rechargeable battery may also be used to support fast charge technology.

In some embodiments, the terminal 800 also includes one or more sensors 810. The one or more sensors 810 include, but are not limited to: acceleration sensor 811, gyro sensor 812, pressure sensor 813, optical sensor 814, and proximity sensor 815.

The acceleration sensor 811 can detect the magnitudes of accelerations on three coordinate axes of the coordinate system established with the terminal 800. For example, the acceleration sensor 811 may be used to detect components of gravitational acceleration in three coordinate axes. The processor 801 may control the display screen 805 to display a user interface in a landscape view or a portrait view based on the gravitational acceleration signal acquired by the acceleration sensor 811. Acceleration sensor 811 may also be used for the acquisition of motion data of a game or user.

The gyro sensor 812 may detect a body direction and a rotation angle of the terminal 800, and the gyro sensor 812 may collect a 3D motion of the user to the terminal 800 in cooperation with the acceleration sensor 811. The processor 801 may implement the following functions based on the data collected by the gyro sensor 812: motion sensing (e.g., changing UI according to a tilting operation by a user), image stabilization at shooting, game control, and inertial navigation.

The pressure sensor 813 may be disposed at a side frame of the terminal 800 and/or at a lower layer of the display 805. When the pressure sensor 813 is disposed on a side frame of the terminal 800, a grip signal of the terminal 800 by a user may be detected, and the processor 801 performs left-right hand recognition or shortcut operation according to the grip signal collected by the pressure sensor 813. When the pressure sensor 813 is disposed at the lower layer of the display screen 805, the processor 801 controls the operability control on the UI interface according to the pressure operation of the user on the display screen 805. The operability controls include at least one of a button control, a scroll bar control, an icon control, and a menu control.

The optical sensor 814 is used to collect the ambient light intensity. In one embodiment, the processor 801 may control the display brightness of the display screen 805 based on the ambient light intensity collected by the optical sensor 814. Specifically, when the intensity of the ambient light is high, the display brightness of the display screen 805 is turned up; when the ambient light intensity is low, the display brightness of the display screen 805 is turned down. In another embodiment, the processor 801 may also dynamically adjust the shooting parameters of the camera assembly 806 based on the ambient light intensity collected by the optical sensor 814.

A proximity sensor 815, also known as a distance sensor, is provided on the front panel of the terminal 800. The proximity sensor 815 is used to collect the distance between the user and the front of the terminal 800. In one embodiment, when the proximity sensor 815 detects a gradual decrease in the distance between the user and the front face of the terminal 800, the processor 801 controls the display 805 to switch from the bright screen state to the off screen state; when the proximity sensor 815 detects that the distance between the user and the front surface of the terminal 800 gradually increases, the processor 801 controls the display 805 to switch from the off-screen state to the on-screen state.

Those skilled in the art will appreciate that the structure shown in fig. 8 is not limiting and that more or fewer components than shown may be included or certain components may be combined or a different arrangement of components may be employed.

In an exemplary embodiment, a data management system is provided that includes one or more processors and a memory for storing the one or more processor-executable instructions; wherein the one or more processors are configured to perform the data management method in the above-described embodiments.

In some embodiments, the data management system is provided as a server. Fig. 9 is a block diagram illustrating a structure of a server 900 according to an exemplary embodiment, where the server 900 may have a relatively large difference according to a configuration or performance, and may include one or more processors (Central Processing Units, CPUs) 901 and one or more memories 902, where at least one program code is stored in the memories 902, and the at least one program code is loaded and executed by the processors 901 to implement the methods provided in the above-described method embodiments. Of course, the server may also have a wired or wireless network interface, a keyboard, an input/output interface, and other components for implementing the functions of the device, which are not described herein.

In an exemplary embodiment, a computer readable storage medium is also provided, which when executed by a processor of the data management system, enables the data management system to perform the steps performed by the terminal or server in the data management method described above. Alternatively, the computer readable storage medium may be a ROM (Read Only Memory), a RAM (random access Memory ), a CD-ROM (compact disc Read Only Memory), a magnetic tape, a floppy disk, an optical data storage device, and the like.

In an exemplary embodiment, a computer program product is also provided, comprising a computer program that is executed by a processor to implement the above-described data management method.

In some embodiments, a computer program according to an embodiment of the present application may be deployed to be executed on one electronic device, or on a plurality of electronic devices located at one site, or on a plurality of electronic devices distributed at a plurality of sites and interconnected by a communication network, where the plurality of electronic devices distributed at the plurality of sites and interconnected by the communication network may constitute a blockchain system.

Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure herein. This disclosure is intended to cover any adaptations, uses, or adaptations of the disclosure following the general principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

It is to be understood that the present disclosure is not limited to the precise arrangements and instrumentalities shown in the drawings, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. A method of data management, the method comprising:

Acquiring description data of an object, and determining the object as an alternative object, wherein the description data refers to data for describing the object, and the description data comprises object identity data;

Converting the object from the potential object into a first object under the condition that the behavior data of the object is acquired, wherein the first object refers to an object which has generated the behavior data and is not managed by other objects;

The method further comprises the steps of:

2. The data management method according to claim 1, wherein after the converting the first object into the second object managed by the third object, the method further comprises:

3. The method of claim 1, wherein after the converting the object from the potential object to a first object, the method further comprises:

4. The data management method according to claim 1, wherein, in the case where the description data is authenticated, before converting the object from the candidate object to a potential object, the method further comprises:

5. The method of data management according to claim 1, wherein the method further comprises:

6. The data management method according to claim 1, wherein the determining the object as an alternative object includes:

storing the object corresponding to the type of the candidate object;

the converting the object from the potential object to a first object includes:

7. The method of data management according to claim 6, wherein the method further comprises:

8. A data management system, the data management system comprising: the system comprises an initial module, an object authentication module, a behavior data acquisition module and an object maintenance module;

The device comprises an initial module, a storage module and a storage module, wherein the initial module is used for acquiring description data and determining an object to which the description data belongs as an alternative object, the description data refers to data for describing the object, and the description data comprises object identity data;

The object maintenance module is used for converting an object to which the behavior data belongs from the potential object into a first object under the condition that the behavior data acquisition module acquires the behavior data, wherein the first object refers to an object which generates the behavior data and is not managed by other objects;

The object maintenance module is further configured to, when the first object and the third object establish an association relationship, convert the first object into a second object managed by the third object, where the second object is an object that has generated behavior data and is managed by another object.

9. The data management system of claim 8, wherein the object maintenance module is further configured to delete the association relationship established between the object and the third object and convert the object from the second object to the first object if no behavior data is generated within a first preset period of time after the first object is converted to the second object.

10. The data management system of claim 8, wherein the object maintenance module is further configured to re-determine the object as the candidate object if no behavior data is generated within a second preset time period after the object is converted to the first object.

11. The data management system of claim 8, wherein the object authentication module is configured to determine that the description data is authenticated if the object identity data is included in a determination database.

12. The data management system of claim 8, wherein the data management system further comprises a data processing module;

13. The data management system of claim 8, wherein the initial module is further configured to store the object in correspondence with an alternate object type;

14. The data management system of claim 13, wherein the object maintenance module is further configured to replace a first object type stored corresponding to the object with a second object type if the first object establishes an association with a third object.

15. A data management system, the data management system comprising:

One or more processors;

a memory for storing the one or more processor-executable instructions;

wherein the one or more processors are configured to perform the data management method of any one of claims 1 to 7.

16. A computer readable storage medium, characterized in that instructions in the computer readable storage medium, when executed by a processor of a data management system, enable the data management system to perform the data management method of any one of claims 1 to 7.

17. A computer program product comprising a computer program, characterized in that the computer program, when executed by a processor, implements the data management method of any one of claims 1 to 7.