US12216707B1

US12216707B1 - System and method for managing storage space in a data management system

Info

Publication number: US12216707B1
Application number: US18/458,412
Authority: US
Inventors: Prem Pradeep Motgi; Dharmesh M. Patel; Manpreet Singh Sokhi
Original assignee: Dell Products LP
Current assignee: Dell Products LP
Priority date: 2023-08-30
Filing date: 2023-08-30
Publication date: 2025-02-04
Anticipated expiration: 2043-08-30

Abstract

Methods and systems for managing storage space in a data management system are disclosed. To manage storage space, data management system may limit the types and quantity of data stored within the data management system. Data management system may prioritize deletion of data based on relevancy of the data for one or more purposes with respect to an individual. To identify relevant data, data management system may analyze data, including audio recordings of interactions between the individual for which the data is regarding and other individuals that provide services to the individual and identify topics of the data. Based on the analysis of the data and identified topics, data management system may establish a ranking order of the topics that are more relevant to the individual.

Description

FIELD

Embodiments disclosed herein relate generally to storage management. More particularly, embodiments disclosed herein relate to systems and methods to manage storage space in a data management system.

BACKGROUND

Computing devices may provide computer-implemented services. The computer-implemented services may be used by users of the computing devices and/or devices operably connected to the computing devices. The computer-implemented services may be performed with hardware components such as processors, memory modules, storage devices, and communication devices. The operation of these components and the components of other devices may impact the performance of the computer-implemented services.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments disclosed herein are illustrated by way of example and not limitation in the figures of the accompanying drawings in which like references indicate similar elements.

FIG. 1 shows a block diagram illustrating a system in accordance with an embodiment.

FIGS. 2A-2D show diagrams illustrating data flows in accordance with an embodiment.

FIGS. 3A-3C show flow diagrams illustrating methods of managing storage space in accordance with an embodiment.

FIG. 4 shows a block diagram illustrating a data processing system in accordance with an embodiment.

DETAILED DESCRIPTION

Various embodiments will be described with reference to details discussed below, and the accompanying drawings will illustrate the various embodiments. The following description and drawings are illustrative and are not to be construed as limiting. Numerous specific details are described to provide a thorough understanding of various embodiments. However, in certain instances, well-known or conventional details are not described in order to provide a concise discussion of embodiments disclosed herein.

Reference in the specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in conjunction with the embodiment can be included in at least one embodiment. The appearances of the phrases “in one embodiment” and “an embodiment” in various places in the specification do not necessarily all refer to the same embodiment.

References to an “operable connection” or “operably connected” means that a particular device is able to communicate with one or more other devices. The devices themselves may be directly connected to one another or may be indirectly connected to one another through any number of intermediary devices, such as in a network topology.

In general, embodiments disclosed herein relate to methods and systems for managing storage space in a data management system. The data management system may collect, store, and/or otherwise manage data on behalf of an individual. However, storing data in the data management system may consume limited storage resources available to the data management system (and/or the data management system may include insufficient resources to store all data collected for an individual).

To manage storage space, the data management system may (i) select portions of data to remove and/or delete, (ii) proactively reject some portions of not-yet-stored data, and/or (iii) perform other types of storage space management actions. Some portions of data may include data that is more relevant or helpful for an individual and/or other individuals than other portions of data. Thus, deletion or rejection of data that may include relevant information may be disadvantageous for the individual by reducing the ability of the desired services to be provided using the data.

To address the potential deletion or rejection of relevant data, the data management system may prioritize deletion and/or rejection of data on the basis of relevancy of the portions of data for one or more purposes with respect to an individual. To discriminate more relevant data from less relevant data, the data management system may analyze data being collected and stored, audio recordings of interactions between the individual and other individuals that provide services, and/or other types of data that may include information identifying relevant content to the individual for which the data is stored.

By identifying relevant content to the individual, the system may establish topics that are relevant to the individual and prioritize storage of data including and/or relating to the topics over storage of data relating to other topics. The data management system may update the topics relevant to the individual and/or adjust relevancy rankings of the topics as new information regarding the topics is obtained. By proactively updating the relevant topics and relevancy rankings for the topics, the data management system may be more likely to retain the more desirable data and remove the less desirable data to the individual for which the data is regarding.

Thus, embodiments disclosed herein may provide an improved system for managing limited storage space in a data management system. The improved storage management system may discriminate more relevant data from less relevant data based on topics relevant to the individual for which the data is being stored. Relevancy ratings of the topics relevant to the individual may be adjusted dynamically as new information is obtained by the system. By doing so, a system in accordance with embodiments disclosed herein may prioritize deletion of data based on the relevancy of the data for one or more purposes with respect to the individual. By managing storage of data based on relevancy of the data to the individual, the storage management system may automatically and/or semiautomatically manage the data being stored in limited storage resources of the data management system. Thereby, the functionality of the data management system (e.g., to store data for an individual) may be maintained without user input during limited storage capacity events (e.g., limited storage resources are consumed).

In an embodiment, a method for managing storage space in a data management system is disclosed. The method may include identifying an occurrence of a storage space management event; based on the occurrence of the storage space management event: identifying a portion of data managed by the data management system for deletion using topic classifications for the data and topic rankings for the topic classifications; and initiating deletion of the identified portion of the data.

The topic rankings may be based at least in part on an audio transcript. The audio transcript may be based on an audio file. The audio file may include audio data based on at least one conversation between two people.

The two people may include a first person for which the data may be stored by the data management system, and a second person which provides at least one service to the first person.

The at least one service may be a medical service, and the at least one conversation may be part of the at least one service.

The topic rankings may be based at least in part on instances of topics discussed during the at least one conversation between the two people.

The topic rankings may specify a rank ordering of the topic classifications.

The topic classifications may be based at least in part on the topics discussed the at least one conversation between the two people.

The topic classifications may include an enumeration of each unique topic of the topics discussed during the at least one conversation between the two people.

The topic classifications may be related to a service provided by one of the two people, and exclude topics unrelated to the service provided by the one of the two people.

Identifying the occurrence of the storage space management event may include: monitoring available storage space available to the data management system; making a determination that the available storage space meets a storage space criteria; and based on the determination, concluding that a storage space management event for the data management system has occurred.

Identifying the portion of the data may include: rank ordering the data based on the topic rankings to obtain rank ordered portions of the data; and selecting, based on the rank ordering, the portion of the data.

Selecting the portion of the data may include: identifying a quantity of the data to be deleted based on the available storage space and the storage space criteria; and selecting lowest ranked portions of the rank ordered portions of the data for deletion until a quantity of the selected lowest ranked portions of the rank ordered portions of the data meets the identified quantity of the data to be deleted.

The method may include: prior to identifying the occurrence of the storage space management event: obtaining an audio transcript from a data source; performing a transcription process, using the audio transcript, to obtain a text transcript; performing an analysis of the text transcript; and identifying, based on the analysis of the text transcript, the topic classifications and the topic rankings for the topic classifications.

The method may include: prior to identifying the occurrence of the storage space management event: obtaining unclassified data from the data source; and performing a topic identification process using the unclassified data and the topic classifications to identify a topic classification of the topic classifications for the unclassified data.

In an embodiment, a non-transitory media is provided. The non-transitory media may include instructions that when executed by a processor cause the computer-implemented method to be performed.

In an embodiment, a data processing system is provided. The data processing system may include the non-transitory media and a processor, and may perform the computer-implemented method when the computer instructions are executed by the processor.

Turning to FIG. 1 , a block diagram illustrating a system in accordance with an embodiment is shown. The system shown in FIG. 1 may provide computer-implemented services. The computer-implemented services may include data management services, data storage services, data access and control services, database services, and/or any other type of service that may be implemented with a computing device.

The system may include data management system 102. Data management system 102 may provide all, or a portion, of the computer-implemented services. To provide the computer-implemented services, data may be stored in data management system 102. The data stored in data management system 102 may include data usable (i) by an individual for which the data is stored, (ii) by other individuals to assist the individual, and/or (iii) by other individuals for other types of use. For example, the data may include healthcare information for an individual and the data may be usable by other individuals such as healthcare providers to diagnose and/or treat the individual for various health conditions.

The data stored in data management system 102 may be collected from data source 100. While illustrated with respect to a single data source, the system of FIG. 1 may include any number of data sources through which data management system 102 may obtain data. Data source 100 may include hardware and/or software components configured to obtain data, store data, provide data to other entities, and/or to perform any other task to facilitate performance of the computer-implemented services.

For example, an individual's healthcare information may be obtained from a healthcare provider system (e.g., data source 100) for use by the individual and/or other individuals (via associated devices). The data collected from data source 100 may include any quantity, size, and type of data. The data may include, for example, an audio recording (e.g., audio file) of a conversation between an individual and a healthcare provider, digitized results of medical tests, etc.

By storing data in data management system 102, the aggregated data may be usable for a variety of purposes. For example, in the healthcare context, the data may be usable for diagnostic purposes, verification purposes (e.g., second opinions), to facilitate studies by third parties that may use the data, etc. While described with respect to the healthcare services context, it will be appreciated that data may be stored in data management system 102 for other purposes and/or with respect to other contexts. For example, the stored data may be relevant for other types of services, uses, etc. without departing from embodiments disclosed herein.

However, storing data in data management system 102 may consume limited storage resources available to data management system 102. For example, data management system 102 may have a finite amount of storage resources for storing data. If all of the storage resources are consumed, additional data may not be stored in data management system 102 thereby limited use of the data and computer implemented services provided with the data.

In general, embodiments disclosed herein may provide methods, systems, and/or devices for managing limited storage capacity in data management systems. To manage limited storage capacity, data management system 102 may limit the types and quantity of data stored in data management system 102. For example, data management system 102 may (i) identify portions of stored data for removal and/or deletion in order to free some of the limited storage capacity, (ii) proactively reject some portions of not-yet-stored data for storage to retain some of the limited storage capacity that is already free, and/or (iii) perform other types of storage space management actions with respect to various portions of data managed by data management system 102.

Data management system

102 may select the portions of data for performance of management actions on the basis of relevancy of the portions of data for one or more purposes. For example, some portions of the data stored in the data management system may be more relevant or helpful for an individual and/or other individuals (e.g., service providers such as medical professional) to provide services to the individual than other portions of the data stored in the data management system. Deletion of data that may include relevant information for an individual may be disadvantageous for the individual by reduce the ability of the desired services to be provided using the data managed by data management system 102. Therefore, data management system 102 may prioritize deletion of data based on the relevancy of the data for one or more purposes with respect to an individual.

In order to discriminate more relevant data from less relevant data, the data management system may analyze the data being collected and stored, audio recordings of interactions between the individual and other individuals that provide services (e.g., a purpose for the data) to the individual, and/or other types of data that may include content relevant to discerning purposes (e.g., topics) that are relevant to the individual for which the data is stored. For example, data management system 102 may analyze an audio recording of a conversation between an individual and a healthcare provider to identify medical conditions impacting the individual. Based on this identification, data management system 102 may establish topics that are relevant to the individual, and prioritize storage of data including and/or relating to the topics (e.g., in this example, diagnosis, treatment, etc. of these medical conditions) over storage of data relating to other topics.

As new information regarding the topics becomes available, the topics and relevancy ratings (e.g., some topics may be of higher relevancy) for the topics may be updated. Consequently, the topics for which storage of data is prioritized may be dynamically updated over time.

By dynamically updating the topics and relevancy rankings for the topics over time, embodiments disclosed herein may provide a storage system that is more likely to retain data that is more desirable to an individual, and purge other data that is less desirable to the individual. The disclosed embodiments may do so in an automated and/or semiautomated fashion thereby reduce a cognitive burden on an individual for managing the data stored in limited storage resources of data management system 102.

To provide the above noted functionality, the system of FIG. 1 may include data source 100, data management system 102, data consumer 104, user device 106, and communication system 108. Each of these components is discussed below.

Data source

100 may (i) facilitate collection and transmission of data (e.g., regarding and/or relating to an individual) to data management system 102, (ii) provide information identifying the individual or entity sourcing the data to data management system 102, and/or (iii) otherwise facilitate collection of data by data management system 102. Data source 100 may be include a system operated by a medical provider which may collect, store, and/or provide access to data for a patient or individual, a personal device that collects information about an individual (e.g., cellphone, smart watch, etc.), and/or another type of data collection device. While described with respect to a medical provider, it will be appreciated that data source 100 may provide data related to other purposes without departing from embodiments disclosed herein. Refer to FIG. 2A for additional details regarding obtaining data using data source 100.

Data source

100 may be managed by (i) an individual or a patient for which the data is being collected, (ii) professional individuals that may provide a service for an individual, and/or (iii) other individuals or entities that may provide services for an individual. For example, data source 100 may be implemented using a professional medical device and/or another device operated by a medical provider.

To manage storage of collected data, data management system 102 may (i) obtain data from data source 100, (ii) for audio data, perform a transcription process to obtain a text transcript of the audio data, (iii) perform an analysis of the text transcript of the data, (iv) based on the analysis of the text transcript, identify topic classifications and topic rankings for the topic classifications, (v) when new data is obtained, perform a topic identification process to identify a topic classification for the new data, (vi) selectively store or reject the new data for storage (e.g., depending on the topic classification and other factors) with an identifier based on the result of the topic identification process, and (vii) perform storage space management actions (e.g., based on topic classifications for stored data, topic rankings, and/or other factors) to manage storage space of data management system 102. Refer to FIGS. 2A-2C for additional details regarding storing data.

To manage storage space, data management system 102 may perform any number of storage space management actions, which may include (i) identifying when storage space is unavailable (and/or meets other criteria), (ii) identifying portion(s) of data to delete and/or portions of not yet stored data to discard without storing, and/or (iii) deleting the identified portion(s) of data. Similarly, data management system 102 may also provide access to stored data (e.g., to the individual for which the data is being managed and/or to data consumer 104). Refer to FIG. 2D for additional details regarding managing storage space.

Data consumer

104 may (i) obtain limited access to selective portions of data stored in data management system 102, (ii) submit requests for access to data stored in data management system 102 by a third party or other individual, (iii) provide information identifying the individual or entity requesting access to the data and/or other types of information upon which decisions to grant access may be based, and/or (iv) once a request for access is granted (e.g., by user device 106), obtain access to data stored in data management system 102 (e.g., data for which access has been granted based on the submitted requests).

User device

106 may facilitate (i) access and control over data stored in data management system 102 by an individual, (ii) designation of portions of data for use by other individuals (e.g., data consumer 104), and/or (iii) performance of other management operations. User device 106 may be registered with data management system 102. For example, data management system 102 may confirm the identity of user device 106 based on a registration of the device, the registration may indicate that user device 106 is being used by the user or individual.

When providing their functionality, any of data source 100, data management system 102, data consumer 104, and/or user device 106 may perform all, or a portion, of the methods shown in FIGS. 3A-3C.

Any of (and/or components thereof) data source 100, data management system 102, data consumer 104, and user device 106 may be implemented using a computing device (also referred to as a data processing system) such as a host or a server, a personal computer (e.g., desktops, laptops, and tablets), a “thin” client, a personal digital assistant (PDA), a Web enabled appliance, a mobile phone (e.g., Smartphone), an embedded system, local controllers, an edge node, and/or any other type of data processing device or system. For additional details regarding computing devices, refer to FIG. 4 .

Any of the components illustrated in FIG. 1 may be operably connected to each other (and/or components not illustrated) with communication system 108. In an embodiment, communication system 108 includes one or more networks that facilitate communication between any number of components. The networks may include wired networks and/or wireless networks (e.g., and/or the Internet). The networks may operate in accordance with any number and types of communication protocols (e.g., such as the internet protocol).

While illustrated in FIG. 1 as including a limited number of specific components, a system in accordance with an embodiment may include fewer, additional, and/or different components than those illustrated therein.

To further clarify embodiments disclosed herein, diagrams illustrating data flows implemented by a system over time in accordance with an embodiment are shown in FIGS. 2A-2D. In FIGS. 2A-2D, a first set of shapes (e.g., 204, 208) is used to represent data structures, a second set of shapes (e.g., 200, 206) is used to represent processes performed using data, and a third set of shapes (e.g., 226) is used to represent large scale data structures such as databases.

Turning to FIG. 2A, a first data flow diagram illustrating data flows, data processing, and/or other operations that may be performed by the system of FIG. 1 in accordance with an embodiment is shown. The data flows, data processing, and/or other operations may be performed when data is obtained from a data source. In FIG. 2A, example flows between data source 100 and data management system 102 are shown. It will be appreciated that similar data flow with respect to any devices (e.g., devices that may collect and transmit data to data management system 102 such as user device 106) and data management system 102 may be present.

To provide computer-implemented services, data management system 102 may obtain, store, and/or otherwise manage data for an individual. Data management system 102 may (i) obtain data from data source 100, and (ii) store some or all of the collected data for future use. However, data management system 102 may have a limited capacity for storing data. Consequently, data management system 102 may perform various storage space management processes over time, as discussed in greater detail with respect to FIGS. 2B-2D.

To obtain the data, data management system 102 and data sources 100 may cooperate with one another for data collection purposes.

To cooperate with data management system 102 for data collection purposes, data source 100 may perform data collection process 200. During data collection process 200, data may be (i) collected using data generation components 202, and (ii) provided all or a portion of the collected data (and/or derived data that is based at least in part on the collected data) to data management system 102.

Data generation components

202 may include software components and/or hardware components to collect data. For example, data generation components 202 may include sensors, generative components, and display components of data source 100. The display components may be used to display prompts to a user of data source 100 (e.g., to instruct a user how to participate in data collection processes). The generative components may be used to generate various stimulations (e.g., optical, audio, etc.) for the user (e.g., so that data may be collected). The sensors may be used to obtain information regarding the user and the impact of the stimulations on the user.

Once collected, the data may be prepared for transmission to data management system. To prepare the collected data for transmission, the data may be enriched with additional information by adding metadata. The metadata may include, for example, (i) information regarding how the data was collected, (ii) information regarding for which entity the data was collected such as a user for which data management system 102 manages data, (iii) collection time, and/or other information that may enhance the collected data.

To add the metadata, data source 100 may store information regarding the user. For example, data source 100 may store identification data 204. Identification data 204 may include information regarding the identity of the individual for which the collected data is regarding/relating to. For example, identifying information such as the individual's name, date of birth, and/or any other identifying information for the individual for which the data is regarding.

Identification data 204 may also include information regarding the identity of the user and/or entity operating data source 100. For example, identifying information such as the user's and/or entity's name, IP address, and/or any other information useful to identify the operator and/or manager of data source 100.

Once enhanced, the collected data and corresponding metadata may be provided to data management system 102.

To cooperate with data source 100 for data collection purposes, data management system 102 may perform data ingest process 206. During data ingest process 206, the collected data obtained from data source 100 may be (i) classified with respect to which user the collected data is associated, (ii) managed in accordance with user-based access controls, and (iii) queued in raw data queue 210 for additional processing. Refer to FIGS. 2B-2D for additional details regarding the additional processing that may be performed on collected data.

To classify the data with respect to a user, the metadata may specify the user for which the data was collected. The user specified by the metadata may checked against users listed in registered user repository 212. Registered user repository 212 may include information regarding users that received data management services from data management system 102. Thus, when collected data is obtained, it may be verified as being relevant to users using registered user repository 212 (if not relevant, it may be discarded).

To manage the collected data in accordance with access controls, access to the data may be at least partially restricted. The restrictions for access to the collected data may be specified by relational data 208. Relational data 208 may specify restrictions on access to data managed by data management system 102 on behalf of different users. For example, the users may specify limits on the ability of other entities to access data managed by data management system 102 on behalf of the users.

For example, relational data 208 may specify whether and to what extent a data consumer (e.g., 104) may access the data stored by data management system 102 on behalf of a user. The access controls may be granular, thereby allowing a user to control which data consumers are able to access different portions of data. The access controls for a user may be established on a topic by topic basis. Thus, access to data for a given consumer may be given on a topic basis thereby allowing a user to provide a data consumer with access to all, or a portion, of the data managed by data management system that is related to one or more topics. Refer to FIGS. 2B-2D for additional information regarding topics.

To prepare the collected data for additional processing, the collected data may be queued in raw data queue 210. Raw data queue 210 may be implemented as a first in first out queue, or other type of queue. Raw data queue 210 may buffer data until it is processed and stored for long term retention.

Turning to FIG. 2B, a second data flow diagram illustrating data flows, data processing, and/or other operations that may be performed by the system of FIG. 1 in accordance with an embodiment is shown. The data flows, data processing, and/or other operations may be performed when data is classified with respect to its relevancy to different topics.

As discussed above, the system may manage storage of data based on the relevancy of the data for one or more purposes with respect to an individual (e.g., for which the data is being collected and stored). To discriminate more relevant data from less relevant data, data management system 102 may classify the relevancy of data with respect to topics that are relevant to the individual.

To classify the collected data and/or stored data, topic identification process 218 may be performed. During topic identification process 218, portions of data (e.g., data portion 214) may be obtained from the raw data queue and/or data repository 222 (e.g., if re-classifying data). The portions of data may reflect discrete portions such as files.

Once obtained, data portion 214 may be classified with respect to certain topics that have been identified as being relevant to an individual. The topics that are relevant to the individual may be specified by identified topics 216. Refer to FIG. 2C for additional details regarding identifying topics that are relevant to different individuals.

To classify data portion 214 with respect to identified topics 216, various classification models 219 may be used. The classification models 219 may be implemented using, for example, inference models (e.g., decision trees, machine learning models, rules based systems, etc.). Classification models 219 may include any number of such inference models.

In an embodiment, at least some of the inference models are implemented by training a neural network to perform classification. The neural network may be trained using supervised learning, self-supervised learning, semi-supervised learning, and/or unsupervised learning. For example, with supervised learning, some number of instances of data may be hand-labeled by a subject matter expert or other person with respect to the topics (may be any number of topics, may include more topics than identified topics 216) for which the data is relevant to obtain a training data set. Once obtained, the training data set may be used to train the neural network (e.g., to set the weights of neurons and/or other features of the neural network).

In an embodiment, classification models 219 includes different models that are adapted to classify different types of data. For example, different inference models of classification models 219 may be adapted to handle images, text documents, tabular data sets, and/or other types of data, respectively.

In an embodiment, classification models 219 includes multiple different models that may be used to classify data portion 214. For example, data portion 214 may include different types of data. The inference models from classification models 219 may be used to identify topics for these different types of data, thereby identifying multiple topics to which data portion 214 may be relevant.

In an embodiment, at least one inference model from classification models 219 is trained to identify more than one topic for the ingested data. For example, the inference model may specify a range of different topics to which data portion 214 is relevant. The range of different topics may include a variety of topics that may be relevant to the individual and/or user for which the data is being stored in data management system 102.

To obtain topic classifications 220 for data portion 214, data portion 214 may be ingested by any of the models of classification models 219. The models may, as output, indicate any number of topics to which data portion 214 is relevant. The topics output by classification models 219 may be filtered against identified topics 216 to identify topic classifications 220. For example, if classification models 219 indicate that data portion 214 is relevant for the topics of “head”, “neck”, “balloons”, and “tattoo”, but identified topics 216 only specify the topics of “head” and “neck”, then the topics “balloons” and “tattoo” may be filtered out resulting in topic classifications 220 only including the topics “head” and “neck”.

Once topic classifications 220 are obtained, data portion 214 and topic classifications may be stored in data repository 222 for future use. Topic classifications 220 and data portion 214 may be associated with each other in data repository 222. Topic classifications 220 may be used, for example, to service future storage space management events (e.g., occurrence of limited storage space availability) by facilitating identification of the topics for which data portion 214 is relevant.

However, as discussed above, to identify topic classifications 220, identified topics 216 (e.g., that are relevant to a user, purpose, etc.) may need to be available.

Turning to FIG. 2C, a third data flow diagram illustrating data flows, data processing, and/or other operations that may be performed by the system of FIG. 1 in accordance with an embodiment is shown. The data flows, data processing, and/or other operations may be performed to identify topics relevant to a user, purpose, and/or another basis.

To obtain identified topics 216, data including clues and/or other information usable to identify topics that are relevant may be collected. For example, audio recordings of interactions (e.g., conversations) between an individual (e.g., a user of the data management system) and other individuals that provide services (e.g., a purpose for the data) to the individual may be obtained. The resulting audio data 230—and/or other types of data that may include content relevant to discern purposes (e.g., topics) relevant to the individual for which the data is being collected and stored—may be used to identify topics relevant to the individual.

For example, audio data 230 may include an audio recording of a conversation between a patient and a medical provider in which the two people discuss diagnosis, treatment, etc. for a particular type of medical condition such as diabetes. The conversation may be analyzed to identify topics (e.g., medical conditions, medical tests, etc.) that are relevant to the patient.

In order to analyze audio data 230, transcription process 232 may be performed. During transcription process 232, audio data 230 may be transcribed to obtain text transcript 234. Transcription process 232 may be performed using an inference model (not shown), artificial intelligence model (AI model), natural language processing, and/or automated transcription modalities. For example, audio data 230 may be ingested by an inference model through which audio data 230 is analyzed and transcribed into a text format (e.g., text transcript 234).

Once text transcript 234 is obtained, topic analysis process 236 may be performed in order to obtain identified topics 216 and topic rankings 238. Identified topics 216 may, as noted above, indicate topics that are relevant to a user of the data management system, and topic rankings 238 may indicate a rank order of the topics indicated by the identified topics 216. The rank order may be with respect to relevancy of the topics to the user.

During topic analysis process 236, text transcript 234 may be analyzed to (i) identify topics relevant to a user, and (ii) relative importance of each of the topics to the user.

To identify topics relevant to the user, text transcript 234 may be analyzed via (i) automated textual analysis to identify frequency/number of occurrences of difference utterances (e.g., words, phrases, etc.) made during the conversation captured in audio data 230, (ii) inferencing using inference models, (iii) large language model based natural language processing, and/or other text analysis modalities. The resulting output of any of these analyzation techniques may include a list of (i) topics that arose during the conversation captured in audio data 230, (ii) frequencies/counts of the topics, (iii) levels of emphasis on the different topics made by the different participants in the conversation, (iv) participants in the conversation that brought up the topics during the conversation, (v) duration of time during the conversation each topic was the topic of the conversation, (vi) opinion polarity (e.g., positive, neutral, negative, etc.) of each topic identified in the data, and/or other information regarding the topics during the conversation.

Identified topics

216 may be established based on any of the aforementioned information obtained via analysis of text transcript 234. For example, identified topics 216 may include (i) all topics that met a minimum threshold of interest (e.g., brought up above a threshold number of times/met a duration of time requirement as the topic of conversation) during the conversation captured by audio data 230, (ii) a prescribed number of the topics that were of the highest interest, etc.

Topic rankings

238 may be established based on the level of interest in each of identified topics 216 identified based on the conversation captured by audio data 230. For example, topics rankings 238 may rank identified topics 216 based on the number of times, frequency of utterance, and/or other quantification regarding interest in each of identified topics 216.

For example, an AI model may analyze text data (e.g., text transcript 234) regarding medical diagnosis, treatment, etc. for an individual and identify features (e.g., certain group of text or words) related to diabetes (e.g., topic). As such, the AI model may establish the topic of diabetes to be relevant to the individual and assign a relevancy value to the topic of diabetes (e.g., topic rankings 238).

Identified topic classifications

216 and topic rankings 238 may be stored in a data repository (not shown, may be data repository 222 shown in FIG. 2B) of data management system 102.

Over time, identified topic classifications 216 and topics rankings 238 may be updated as new data is collected (e.g., audio data 230). Continuing with the above example, additional audio data that captures a conversation during which a new topic (e.g., such as a new medical condition) is discussed may be obtained and analyzed. Doing so may increase a relevancy value (e.g., topic ranking) for the new topic when compared to the topic of diabetes.

Once obtained, identified topic classifications 216 and topics rankings 238 may be used to manage limited storage resources of a data management system by discriminating less relevant data from more relevant data in an automated manner.

Turning to FIG. 2D, a fourth data flow diagram illustrating data flows, data processing, and/or other operations that may be performed by the system of FIG. 1 in accordance with an embodiment is shown. The data flows, data processing, and/or other operations may be performed to manage storage space of a data management system.

To manage storage space, data management system (e.g., 102, FIG. 1 ) may monitor the condition of its available storage space, arrival of new data, and/or other characteristics of its operation to identify occurrences of storage space management events. A storage space management event may indicate that the data management system should take action to manage its limited storage resources.

To manage its limited storage resources, storage space management process 240 may be performed. During storage space management process 240, less relevant data may be discriminated from more relevant data stored in data repository 222 to identify portions of data that may be of lower impact if removed. For example, removal of portions of data that are less relevant to the individual may not affect the ability of other individuals to provide services (e.g., medical diagnosis, treatment, etc.) which may be more relevant for the individual. The identified portions of data may be added to data deletion list 242.

To discriminate less relevant data from more relevant data, storage space management process 240 may, for a given portion of data, retrieve the topics classifications (e.g., 220) for the portion of data from data repository 222. To do so, an identifier for the portion of the data may be provided to data repository 222. In response to the identifier, data repository 222 may return the corresponding topics classifications 220 for the portion of data. Storage management process 240 may repeat the above process for each portion of data to obtain the topics classifications (e.g., 220) for each portion of stored data.

Once obtained, a ranking order for the portion of data may be obtained using topic rankings 238. The rank order may be obtained by obtaining a quantification for each portion of data. For example, each topic of topic classifications 220 for a given portion of data may be given a corresponding weight using topic rankings 238 (e.g., higher rank topic classification is given a higher weight). The weighted topic classifications for a given portion of data may be summed to obtain a quantification for the portion of data. The quantification may be used to rank order the portions of data from most relevant (e.g., high value quantification) to least relevant (e.g., lowest value quantification). The ranking order may be used to select identifiers of portions of data to add to data deletion list 242.

For example, data deletion list 242 may be populated with identifiers for portions of data (e.g., stored in data repository 222) that are the lowest ranked ordered (e.g., least relevant data that is least likely to have an undesired impact if deleted). Any number of identifiers may be added to data deletion list 242 based on any criteria (e.g., all portions of data falling below a threshold quantification, a number of portions that if deleted will result in the available storage space being increased above a threshold, etc.).

Data deletion list

242 may be used when a storage space management event has occurred. For example, the storage space management may be when storage space availability is limited and additional data is received from a data source (e.g., data source 100). Data deletion list 242 may be provided to other entities for similar or different uses.

Thus, using the data flows and processes shown in FIGS. 2A-2D, storage space may be automatically managed via discrimination of less relevant data from more relevant. The discriminated less relevant data may be deleted or otherwise utilized to manage the operating condition of a data management system.

As discussed above, the components of FIGS. 1-2D may perform various methods to manage operation of data processing systems. FIGS. 3A-3C illustrate methods that may be performed by the components of the system of FIGS. 1-2D. In the diagram discussed below and shown in FIGS. 3A-3C, any of the operations may be repeated, performed in different orders, omitted, and/or performed in parallel with or in a partially overlapping in time manner with other operations.

Turning to FIG. 3A, a flow diagram illustrating a method for managing storage space in a data management system in accordance with an embodiment is shown. The method may be performed, for example, by any of data source 100, data management system 102, data consumer 104, user device 106, and/or other components of the system shown in FIGS. 1-2D.

Prior to operation 300, a data management system may have obtained data for an individual and stored the data in a data repository within the data management system. The data may have been obtained through various processes such as generation, acquisition from external entity (e.g., medical provider), acquisition from the individual whose data is being stored, and/or by any other method. The data may include data relating to healthcare information for an individual (e.g., medical records) and/or topics discussed during conversations between a first person and a second person. The data may be classified and processed by the data management system based on topics (e.g., types of data) relevant to the individual. To classify and process the data, the data management system may identify topic and topic rankings for the identified topics for an individual. Refer to FIG. 3B for additional details regarding identifying topics and ranking the topics.

At operation 300, an occurrence of a storage space management event may be identified. The occurrence of the storage space management event may be identified using a schedule that specifies when storage space management process are to be performed, enumerated types of events such as the available storage space falling below a threshold level, and/or via other methods. To identify whether enumerated types of events have occurred, an analysis process may be performed and which may include (i) monitoring available storage space available to the data management system, (ii) making a determination that the available storage space meets a storage space criteria, (iii) based on the determination, concluding that a storage space management event for the data management system has occurred, and/or (iv) via other methods.

Monitoring available storage space available to the data management system may be performed by (i) a user checking the available storage space manually, (ii) an operating system (and/or other type of management entity such as an agent) analyzing the available storage space, for example, on a scheduled time basis, and/or (iii) and/or any other methods. For example, an operating system may perform an analysis of the storage space capacity for a data management system based on a scheduled time (e.g., once per hour, once per day, etc.) and identify an amount of storage space available.

To determine whether the available storage space meets a storage space criteria, a comparison between the identified storage space availability and the storage space criteria may be made. For example, the data management system and/or another entity may perform a comparison process using the available storage space and the storage space criteria to identify whether the available storage space has met the storage space criteria.

The storage space criteria may include a minimum storage space availability to store data (e.g., on behalf of an individual) in order for the data management system to operate efficiently and successfully. The storage space criteria may be established (i) by the user and/or individual for which the data is regarding (e.g., via the user device), and/or (ii) by the operation of the data management system (e.g., in cooperation with limited storage resources for each individual for which data is being stored).

Based on the determination of whether the available storage space meets the storage space criteria, data management system may make a conclusion regarding whether a storage space management event has occurred. Concluding that a storage space management event for the data management system has occurred may include updating a data structure to record instance of storage space availability, recording information regarding the storage space availability for future processes, automatically initiating performance of various processes responsive the event, and/or any other method. For example, a data management system may record information about the storage space management event (e.g., information regarding whether available storage space meets the storage space criteria) and save the information in a data structure to utilize the information at a later point in time.

At operation 302, responsive and/or based on the storage space management event, a portion of data managed by a data management system may be identified for deletion using topic classifications for the data and topic rankings for the topic classifications. The portion of data may be identified by (i) rank ordering the data based on the topic rankings, (ii) selecting, based on the rank ordering of the data, the portion of the data, and/or any other method. The portion of the data may be selected by (i) identifying a quantity of the data to be deleted based on the available storage space and the storage space criteria, (ii) selecting the lowest ranked portions of the rank ordered data for deletion until a quantity of the selected lowest ranked portions of the rank ordered data meets the identified quantity of the data to be deleted, etc.

The topic classifications for the data may, as discussed above, be based at least in part on the topics discussed during the conversation between the two people. The topic classifications may include an enumeration of each unique topic of topics discussed during the conversation between two people. For example, an audio recording may include a conversation between patient and a medical provider discussing a patient's diabetes diagnosis, treatment, etc. In this example, diabetes may be identified as the topic classification in which some portion of data obtained from a data source (e.g., medical provider system) may be associated.

The topics classifications may be a subset of the topics discussed during the conversation. For example, a purpose for storage of data (and/or other limitations) may be placed on the topic classifications. In such cases, the topics from the conversation may be filtered based on the purposes of storage of the data to identify the subset of the topics on which the topic classifications may be based. The purpose may be specified by a user, may be identified via automated means, and/or may be obtained using other methods.

The topic rankings may be based, at least in part, on instances of the topics discussed during a conversation between the two people. For example, a counter of the utterances for the topics, duration of conversation dedicated to each topic, and/or other quantifications may be derived from the conversation. The topic rankings may be based on these quantifications (e.g., more frequently uttered topics may be ranked more highly than less frequently uttered topics).

The portion of data may be added to a deletion list.

At operation 304, deletion of the identified portion of the data may be initiated. The deletion of the identified portion of the data may be performed by providing instructions to management entities that manage data stored in the data storage system to delete the identified portion of the data (and/or other portions of data specified by the data deletion list), and/or via other methods.

For example, deletion of the portion of the data identified as the lowest ranked portion of the data may be initiated by providing an identifier for the portion of the data to be deleted and/or instructions to delete the portion of the data in order of the lowest ranked portions of the rank ordered data. Deletion of the identified portion of the data may be performed in a manner specified by the data management system.

The method may end following operation 304.

Thus, using the method illustrated in FIG. 3A, less relevant data stored by a data management system may be deleted (and/or otherwise managed) to facilitate storage and use of more relevant data. The automated method may or may not involve user activity. For example, the less relevant data may be automatically identified and deleted. In another example, the automatically identified data may be presented to a user for confirmation prior to automated deletion.

Turning to FIG. 3B, a flow diagram illustrating a method for obtaining a classification and rankings for data in accordance with an embodiment is shown. The method may be performed, for example, by any of data source 100, data management system 102, data consumer 104, user device 106, and/or other components of the system shown in FIGS. 1-2D.

At operation 306, an audio transcript from a data source may be obtained. The audio transcript may be obtained by (i) receiving the audio transcript from a data source and/or another entity via communication by a data processing system, (ii) reading it from storage, and/or (iii) any other methods. The audio transcript may be based on an audio recording which may include a conversation between two people.

At operation 308, a transcription process, using the audio transcript, to obtain a text transcript may be performed. The transcription process may be performed by (i) processing the audio transcript into text data, (ii) providing the audio transcript to a third party or another entity to obtain the text transcript, and/or (iii) any other methods. For example, a data processing system may be trained to translate audio files to text files (e.g., natural language processing) through speech recognition. As an additional example, the audio transcript may be provided to third party and/or an external operating system to perform the transcription process through which the text transcript may be obtained.

At operation 310, an analysis of the text transcript may be performed. The analysis may be performed by (i) processing the text data, (ii) providing the text transcript to a third party and/or another entity to analyze the text data, and/or (iii) any other methods. For example, a data processing system may process the text transcript by identifying a semantic context of the text (e.g., selecting a meaning of a word based on context), identifying text with similar topic keywords and groups of information associated with the topic keywords, and/or any other methods.

At operation 312, topic classifications and topic rankings for the topic classifications may be identified based on the analysis of the text transcript. The topic classifications may be identified by (i) receiving information regarding topic classifications and topic rankings, (ii) generating the topic classifications and topic rankings, and/or (iii) via any other method to obtain topic classifications and topic rankings. Refer to FIG. 2C for additional details regarding obtaining the topic classifications and topic rankings.

The method may end following operation 312.

Thus, using the method shown in FIG. 3B, embodiments disclosed herein may facilitate automatic identification of topics that are relevant to a user, and rankings for the topics. The topic classifications and topics rankings may be used to classify data as being relevant to various topics that are relevant to a user.

Turning to FIG. 3C, a flow diagram illustrating a method of classifying data for topic relevancy in accordance with an embodiment is shown. The method may be performed, for example, by any of data source 100, data management system 102, data consumer 104, user device 106, and/or other components of the system shown in FIGS. 1-2D.

At operation 314, unclassified data (e.g., a portion of data) from a data source may be obtained. The unclassified data may be obtained by (i) receiving it from a third party and/or entity via communication by a data processing system, (ii) reading it from storage, and/or (iii) via any other method. The unclassified data may include data which has not been analyzed and/or categorized in regard to topics for which it may be relevant.

At operation 316, a topic identification process using the unclassified data and topic classifications to identify a topic classification of the topic classifications for the unclassified data may be performed. The topic identification process may be performed by classifying the data using an inference model or other type of data with respect to any number of topics, and filtering the topics based on the topics identified as being relevant to the user (e.g., the topic classifications).

The method may end following operation 316.

Using the methods illustrated in FIGS. 3A-3C, embodiments disclosed herein may facilitate storage space management in a data management system in which data is stored on behalf of an individual. Storage space management may include prioritizing storage of data that is more relevant to the individual and deleting data that is less relevant to the individual.

Any of the components illustrated in FIGS. 1-2D may be implemented with one or more computing devices. Turning to FIG. 4 , a block diagram illustrating an example of a data processing system (e.g., a computing device) in accordance with an embodiment is shown. For example, system 400 may represent any of data processing systems described above performing any of the processes or methods described above. System 400 can include many different components. These components can be implemented as integrated circuits (ICs), portions thereof, discrete electronic devices, or other modules adapted to a circuit board such as a motherboard or add-in card of the computer system, or as components otherwise incorporated within a chassis of the computer system. Note also that system 400 is intended to show a high level view of many components of the computer system. However, it is to be understood that additional components may be present in certain implementations and furthermore, different arrangement of the components shown may occur in other implementations. System 400 may represent a desktop, a laptop, a tablet, a server, a mobile phone, a media player, a personal digital assistant (PDA), a personal communicator, a gaming device, a network router or hub, a wireless access point (AP) or repeater, a set-top box, or a combination thereof. Further, while only a single machine or system is illustrated, the term “machine” or “system” shall also be taken to include any collection of machines or systems that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein.

In one embodiment, system 400 includes processor 401, memory 403, and devices 405-407 via a bus or an interconnect 410. Processor 401 may represent a single processor or multiple processors with a single processor core or multiple processor cores included therein. Processor 401 may represent one or more general-purpose processors such as a microprocessor, a central processing unit (CPU), or the like. More particularly, processor 401 may be a complex instruction set computing (CISC) microprocessor, reduced instruction set computing (RISC) microprocessor, very long instruction word (VLIW) microprocessor, or processor implementing other instruction sets, or processors implementing a combination of instruction sets. Processor 401 may also be one or more special-purpose processors such as an application specific integrated circuit (ASIC), a cellular or baseband processor, a field programmable gate array (FPGA), a digital signal processor (DSP), a network processor, a graphics processor, a network processor, a communications processor, a cryptographic processor, a co-processor, an embedded processor, or any other type of logic capable of processing instructions.

Processor

401, which may be a low power multi-core processor socket such as an ultra-low voltage processor, may act as a main processing unit and central hub for communication with the various components of the system. Such processor can be implemented as a system on chip (SoC). Processor 401 is configured to execute instructions for performing the operations discussed herein. System 400 may further include a graphics interface that communicates with optional graphics subsystem 404, which may include a display controller, a graphics processor, and/or a display device.

Processor

401 may communicate with memory 403, which in one embodiment can be implemented via multiple memory devices to provide for a given amount of system memory. Memory 403 may include one or more volatile storage (or memory) devices such as random access memory (RAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), static RAM (SRAM), or other types of storage devices. Memory 403 may store information including sequences of instructions that are executed by processor 401, or any other device. For example, executable code and/or data of a variety of operating systems, device drivers, firmware (e.g., input output basic system or BIOS), and/or applications can be loaded in memory 403 and executed by processor 401. An operating system can be any kind of operating systems, such as, for example, Windows® operating system from Microsoft®, Mac Os®/iOS® from Apple, Android® from Google®, Linux®, Unix®, or other real-time or embedded operating systems such as VxWorks.

System

400 may further include IO devices such as devices (e.g., 405, 406, 407, 408) including network interface device(s) 405, optional input device(s) 406, and other optional IO device(s) 407. Network interface device(s) 405 may include a wireless transceiver and/or a network interface card (NIC). The wireless transceiver may be a WiFi transceiver, an infrared transceiver, a Bluetooth transceiver, a WiMax transceiver, a wireless cellular telephony transceiver, a satellite transceiver (e.g., a global positioning system (GPS) transceiver), or other radio frequency (RF) transceivers, or a combination thereof. The NIC may be an Ethernet card.

Input device(s) 406 may include a mouse, a touch pad, a touch sensitive screen (which may be integrated with a display device of optional graphics subsystem 404), a pointer device such as a stylus, and/or a keyboard (e.g., physical keyboard or a virtual keyboard displayed as part of a touch sensitive screen). For example, input device(s) 406 may include a touch screen controller coupled to a touch screen. The touch screen and touch screen controller can, for example, detect contact and movement or break thereof using any of a plurality of touch sensitivity technologies, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with the touch screen.

IO devices 407 may include an audio device. An audio device may include a speaker and/or a microphone to facilitate voice-enabled functions, such as voice recognition, voice replication, digital recording, and/or telephony functions. Other IO devices 407 may further include universal serial bus (USB) port(s), parallel port(s), serial port(s), a printer, a network interface, a bus bridge (e.g., a PCI-PCI bridge), sensor(s) (e.g., a motion sensor such as an accelerometer, gyroscope, a magnetometer, a light sensor, compass, a proximity sensor, etc.), or a combination thereof. IO device(s) 407 may further include an imaging processing subsystem (e.g., a camera), which may include an optical sensor, such as a charged coupled device (CCD) or a complementary metal-oxide semiconductor (CMOS) optical sensor, utilized to facilitate camera functions, such as recording photographs and video clips. Certain sensors may be coupled to interconnect 410 via a sensor hub (not shown), while other devices such as a keyboard or thermal sensor may be controlled by an embedded controller (not shown), dependent upon the specific configuration or design of system 400.

To provide for persistent storage of information such as data, applications, one or more operating systems and so forth, a mass storage (not shown) may also couple to processor 401. In various embodiments, to enable a thinner and lighter system design as well as to improve system responsiveness, this mass storage may be implemented via a solid state device (SSD). However, in other embodiments, the mass storage may primarily be implemented using a hard disk drive (HDD) with a smaller amount of SSD storage to act as an SSD cache to enable non-volatile storage of context state and other such information during power down events so that a fast power up can occur on re-initiation of system activities. Also a flash device may be coupled to processor 401, e.g., via a serial peripheral interface (SPI). This flash device may provide for non-volatile storage of system software, including a basic input/output software (BIOS) as well as other firmware of the system.

Storage device

408 may include computer-readable storage medium 409 (also known as a machine-readable storage medium or a computer-readable medium) on which is stored one or more sets of instructions or software (e.g., processing module, unit, and/or processing module/unit/logic 428) embodying any one or more of the methodologies or functions described herein. Processing module/unit/logic 428 may represent any of the components described above. Processing module/unit/logic 428 may also reside, completely or at least partially, within memory 403 and/or within processor 401 during execution thereof by system 400, memory 403 and processor 401 also constituting machine-accessible storage media. Processing module/unit/logic 428 may further be transmitted or received over a network via network interface device(s) 405.

Computer-readable storage medium 409 may also be used to store some software functionalities described above persistently. While computer-readable storage medium 409 is shown in an exemplary embodiment to be a single medium, the term “computer-readable storage medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The terms “computer-readable storage medium” shall also be taken to include any medium that is capable of storing or encoding a set of instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of embodiments disclosed herein. The term “computer-readable storage medium” shall accordingly be taken to include, but not be limited to, solid-state memories, and optical and magnetic media, or any other non-transitory machine-readable medium.

Processing module/unit/logic 428, components and other features described herein can be implemented as discrete hardware components or integrated in the functionality of hardware components such as ASICS, FPGAs, DSPs or similar devices. In addition, processing module/unit/logic 428 can be implemented as firmware or functional circuitry within hardware devices. Further, processing module/unit/logic 428 can be implemented in any combination hardware devices and software components.

Note that while system 400 is illustrated with various components of a data processing system, it is not intended to represent any particular architecture or manner of interconnecting the components; as such details are not germane to embodiments disclosed herein. It will also be appreciated that network computers, handheld computers, mobile phones, servers, and/or other data processing systems which have fewer components or perhaps more components may also be used with embodiments disclosed herein.

Some portions of the preceding detailed descriptions have been presented in terms of algorithms and symbolic representations of operations on data bits within a computer memory. These algorithmic descriptions and representations are the ways used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. An algorithm is here, and generally, conceived to be a self-consistent sequence of operations leading to a desired result. The operations are those requiring physical manipulations of physical quantities.

It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the above discussion, it is appreciated that throughout the description, discussions utilizing terms such as those set forth in the claims below, refer to the action and processes of a computer system, or similar electronic computing device, that manipulates and transforms data represented as physical (electronic) quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage, transmission or display devices.

Embodiments disclosed herein also relate to an apparatus for performing the operations herein. Such a computer program is stored in a non-transitory computer readable medium. A non-transitory machine-readable medium includes any mechanism for storing information in a form readable by a machine (e.g., a computer). For example, a machine-readable (e.g., computer-readable) medium includes a machine (e.g., a computer) readable storage medium (e.g., read only memory (“ROM”), random access memory (“RAM”), magnetic disk storage media, optical storage media, flash memory devices).

The processes or methods depicted in the preceding figures may be performed by processing logic that comprises hardware (e.g. circuitry, dedicated logic, etc.), software (e.g., embodied on a non-transitory computer readable medium), or a combination of both. Although the processes or methods are described above in terms of some sequential operations, it should be appreciated that some of the operations described may be performed in a different order. Moreover, some operations may be performed in parallel rather than sequentially.

Embodiments disclosed herein are not described with reference to any particular programming language. It will be appreciated that a variety of programming languages may be used to implement the teachings of embodiments disclosed herein.

In the foregoing specification, embodiments have been described with reference to specific exemplary embodiments thereof. It will be evident that various modifications may be made thereto without departing from the broader spirit and scope of the embodiments disclosed herein as set forth in the following claims. The specification and drawings are, accordingly, to be regarded in an illustrative sense rather than a restrictive sense.

Claims

What is claimed is:

1. A method for managing storage space in a data management system, the method comprising:

identifying an occurrence of a storage space management event indicating limited storage space availability in the data management system;

remediating the storage space management event by at least:

identifying a portion of data managed by the data management system for deletion using topic classifications for the data and topic rankings for the topic classifications, each of the data is associated with one or more of the topic classifications and the identifying comprises:

determining a topic ranking of the topic rankings for each of the topic classifications, the topic ranking indicating a rank of each of the topic classifications,

obtaining a quantification for each of the data using the ranks of all of the one or more topic classifications associated with each respective one of the data,

generating, based on the quantification, a rank order of the data from a highest value quantification to a lowest value quantification, the rank order indicating a relevancy of the data to a user associated with the data with the highest value quantification indicating highest relevancy data to the user and the lowest value quantification indicating lowest relevancy data to the user, and

identifying the portion of the data using the rank order starting from data associated with the lowest value quantification; and

deleting the identified portion of the data to resolve the limited storage space availability in the data management system by deleting the lowest relevancy data to the user while retaining the highest relevancy data to the user; and

prior to the data being managed by the data management system:

obtaining, by the data management system, the data from one or more data sources and a file comprising data based on at least one conversation between two people;

after obtaining the data and by the data management system:

generating a first set of topics for each of the data using a classification model hosted by the data management system;

generating a second set of topics for each of the data based on topics identified in the at least one conversation between the two people; and

filtering out from the first set of topics any topics not included in the second set of topics to obtain a third set of topics for each of the data, the third set of topics being the topic classifications; and

storing the data with the topic classifications in a storage of the data management system.

2. The method of claim 1, wherein the file is an audio file comprising an audio transcript, the audio transcript comprising audio data from the at least one conversation between the two people.

3. The method of claim 2, wherein the two people comprise a first person for which the data is stored by the data management system, and a second person which provides at least one service to the first person, the first person being the user.

4. The method of claim 3, wherein the at least one service is a medical service, and the at least one conversation being part of the at least one service.

5. The method of claim 2, wherein the topic rankings are based at least in part on instances of the topics discussed during the at least one conversation between the two people.

6. The method of claim 1, wherein the topic classifications are related to a service provided by one of the two people, and exclude topics unrelated to the service provided by the one of the two people.

7. The method of claim 1, wherein identifying the occurrence of the storage space management event comprises:

monitoring available storage space of the data management system;

making a determination that the available storage space meets a storage space criteria; and

based on the determination, concluding that the storage space management event for the data management system has occurred.

8. The method of claim 7, wherein selecting the portion of the data comprises:

identifying a quantity of the data to be deleted based on the available storage space and the storage space criteria; and

selecting a quantity of data starting from the lowest value quantification within the rank order for deletion until the quantity of selected data starting from the lowest value quantification within the rank order meets the identified quantity of the data to be deleted.

9. The method of claim 1, further comprising:

prior to identifying the occurrence of the storage space management event:

obtaining, as the file, an audio transcript from a data source;

performing a transcription process, using the audio transcript, to obtain a text transcript;

performing an analysis of the text transcript; and

identifying, based on the analysis of the text transcript, the topic classifications and the topic rankings for the topic classifications.

10. The method of claim 9, further comprising:

prior to identifying the occurrence of the storage space management event:

obtaining unclassified data from the data source; and

performing a topic identification process using the unclassified data and the topic classifications to identify a topic classification of the topic classifications for the unclassified data.

11. A non-transitory machine-readable medium having instructions stored therein, which when executed by a processor, cause the processor to perform operations for managing storage space in a data management system, the operations comprising:

remediating the storage space management event by at least:

prior to the data being managed by the data management system:

after obtaining the data and by the data management system:

12. The non-transitory machine-readable medium of claim 11, wherein the file is an audio file comprising an audio transcript, the audio transcript comprising audio data from the at least one conversation between the two people.

13. The non-transitory machine-readable medium of claim 12, wherein the two people comprise a first person for which the data is stored by the data management system, and a second person which provides at least one service to the first person, the first person being the user.

14. A data processing system, comprising:

a processor; and

a memory coupled to the processor to store instructions, which when executed by the processor, cause the processor to perform operations for managing storage space in a data management system, the operations comprising:

identifying an occurrence of a storage space management event indicating limited storage space availability in the data processing system;

remediating the storage space management event by at least:

identifying a portion of data managed by the data management system for deletion using topic classifications for the topic classifications, each of the data is associated with one or more of the topic classifications and the identifying comprises:

obtaining a quantification for each of the data using the ranks of all of the one or more topic classifications associated with each respective one of the data, and

prior to the data being managed by the data management system:

after obtaining the data and by the data management system:

15. The data processing system of claim 14, wherein the file is an audio file comprising an audio transcript, the audio transcript comprising audio data from the at least one conversation between the two people.

16. The data processing system of claim 15, wherein the two people comprise a first person for which the data is stored by the data management system, and a second person which provides at least one service to the first person, the first person being the user.

17. The non-transitory machine-readable medium of claim 13, wherein the at least one service is a medical service, and the at least one conversation being part of the at least one service.

18. The non-transitory machine-readable medium of claim 17, wherein the topic rankings are based at least in part on instances of the topics discussed during the at least one conversation between the two people.

19. The data processing system of claim 16, wherein the at least one service is a medical service, and the at least one conversation being part of the at least one service.

20. The data processing system of claim 19, wherein the topic rankings are based at least in part on instances of the topics discussed during the at least one conversation between the two people.