MLchartDataset catalogue

Patent · US11100042B2 · B2 · US

Methods and systems relating to network based storage

(11) Publication number
US11100042B2
(21) Application number
15/982,255
(22) Filing date
2018-05-17
(30) Priority date
2017-05-18
(43) Publication date
2021-08-24
(45) Date of grant
2021-08-24
(51) IPC
G06F 17/30; G06F 11/14; G06F 21/62; H04L 29/08; G06F 16/11; G06F 16/17; G06F 16/174; G06F 16/18
(52) CPC
  • G06F Electric digital data processing: 16/125, 11/1448, 11/1451, 11/1461, 11/1469, 16/1734, 16/1748, 16/181, 16/1873, 21/6218, 2201/815, 2221/2141, 3/0604, 3/0619, 3/064, 3/0652, 3/067
  • H04L Transmission of digital information, e.g. telegraphic communication: 67/1097
(72) Inventors
Geoffrey Bourgeois; Greg Campbell
(54) Title
Methods and systems relating to network based storage
(57) Abstract

Cloud storage provides for accessible interfaces, near-instant elasticity and scalability, multi-tenancy, and metered resources within a framework of distributed resources acing to provide highly fault tolerant solutions with high data durability. However, cloud storage also has drawbacks and limitations with information uploading and how information is subsequently accessed.

Full text
View on Google Patents

Claims (5)

  1. A computer-implemented method relating to the remote storage of data within cloud based storage comprising the step of: synchronizing the source metadata and security access control lists to content that is ingested into cloud storage through drive shipping; wherein the step of synchronizing the source metadata and security access control lists to content that is ingested into cloud storage through drive shipping comprises the steps of: writing drive shipped content to a cloud storage account; ingesting the data from the cloud storage account into a cloud archive storage account with a special write operation such that whilst there is a blob written its correct metadata blob is not yet available and hence no item version records are created that correspond to the blob record; deleting each blob from the source cloud storage once it is written to cloud storage archive account; configuring with a domain account with read/write access a ‘blobless’ mode connector setting for data that has already been ingested through the drive shipping method; wherein no blobs are staged during ingestion although a hash value is computed for the blob and passed in the blob metadata associated with the item version metadata information; and a deduplication algorithm results in the source/original item version metadata being mapped and recorded for the blob records already ingested via drive shipping.
  2. The computer implemented method according to claim 1, wherein the connector is established with a connector service software used to authenticate and authorize with the cloud storage tenant and requires a special ‘Write Blobless Items’ permission; if the account has this permission, the software in the cloud storage will permit the hash value to be used otherwise this will fail as unauthorized; and if there is no blob in the cloud storage with a hash value that is submitted in the ‘blobless’ mode of ingestion, then an error is returned for the item.
  3. The computer implemented method according to claim 1, wherein the connector allows all metadata and permissions relating to blobs to be associated with the blobs after their ingestion into a cloud storage through drive shipping.
  4. The computer implemented method according to claim 1, wherein at least one of metadata and permissions associated with the blobs within the cloud storage account are re-associated with the blobs within the cloud archive storage account once the blobs have been ingested.
  5. The computer implemented method according to claim 1, wherein the method runs a connector to allow at least one of metadata and permissions to be associated with the blobs within the cloud archive storage account once the blobs have been ingested.

Description

This invention relates to network and/or cloud based storage and more particularly to methods, processes, and knowledge worker interfaces for writing, managing, and classifying data to network and/or cloud storage including:

Cloud storage has evolved in the last decade from a model being presented as a solution to evolving data storage needs to the main storage form for many enterprises, organizations and individuals. In 2013 over 1,000 Petabytes of data were stored in the cloud, i.e. over 1,000,000,000 Gigabytes. By 2014 a single social network, Facebook™, alone stored approximately 400 Petabytes of data. Cloud storage represents a data storage model where data is stored in logical pools, the physical storage spans multiple servers and often locations, and the physical environment is typically owned and managed by a hosting company and/or service provider. These cloud storage providers are responsible for keeping the data available and accessible, and the physical environment protected and running. People and organizations buy or lease storage capacity from the providers to store user, organization, or application data. Cloud storage services may be accessed through a co-located cloud computer service, a web service application programming interface (API) or by applications that utilize the API, such as cloud desktop storage, a cloud storage gateway or Web-based content management systems.

Citations (1)

  • US20150127607A1
Record as JSON
{
  "publication_number": "US11100042B2",
  "country": "US",
  "kind": "B2",
  "title": "Methods and systems relating to network based storage",
  "abstract": "Cloud storage provides for accessible interfaces, near-instant elasticity and scalability, multi-tenancy, and metered resources within a framework of distributed resources acing to provide highly fault tolerant solutions with high data durability. However, cloud storage also has drawbacks and limitations with information uploading and how information is subsequently accessed.",
  "claims": [
    "1. A computer-implemented method relating to the remote storage of data within cloud based storage comprising the step of: synchronizing the source metadata and security access control lists to content that is ingested into cloud storage through drive shipping; wherein the step of synchronizing the source metadata and security access control lists to content that is ingested into cloud storage through drive shipping comprises the steps of: writing drive shipped content to a cloud storage account; ingesting the data from the cloud storage account into a cloud archive storage account with a special write operation such that whilst there is a blob written its correct metadata blob is not yet available and hence no item version records are created that correspond to the blob record; deleting each blob from the source cloud storage once it is written to cloud storage archive account; configuring with a domain account with read/write access a ‘blobless’ mode connector setting for data that has already been ingested through the drive shipping method; wherein no blobs are staged during ingestion although a hash value is computed for the blob and passed in the blob metadata associated with the item version metadata information; and a deduplication algorithm results in the source/original item version metadata being mapped and recorded for the blob records already ingested via drive shipping.",
    "2. The computer implemented method according to claim 1, wherein the connector is established with a connector service software used to authenticate and authorize with the cloud storage tenant and requires a special ‘Write Blobless Items’ permission; if the account has this permission, the software in the cloud storage will permit the hash value to be used otherwise this will fail as unauthorized; and if there is no blob in the cloud storage with a hash value that is submitted in the ‘blobless’ mode of ingestion, then an error is returned for the item.",
    "3. The computer implemented method according to claim 1, wherein the connector allows all metadata and permissions relating to blobs to be associated with the blobs after their ingestion into a cloud storage through drive shipping.",
    "4. The computer implemented method according to claim 1, wherein at least one of metadata and permissions associated with the blobs within the cloud storage account are re-associated with the blobs within the cloud archive storage account once the blobs have been ingested.",
    "5. The computer implemented method according to claim 1, wherein the method runs a connector to allow at least one of metadata and permissions to be associated with the blobs within the cloud archive storage account once the blobs have been ingested."
  ],
  "description_excerpt": "This invention relates to network and/or cloud based storage and more particularly to methods, processes, and knowledge worker interfaces for writing, managing, and classifying data to network and/or cloud storage including:\n\nCloud storage has evolved in the last decade from a model being presented as a solution to evolving data storage needs to the main storage form for many enterprises, organizations and individuals. In 2013 over 1,000 Petabytes of data were stored in the cloud, i.e. over 1,000,000,000 Gigabytes. By 2014 a single social network, Facebook™, alone stored approximately 400 Petabytes of data. Cloud storage represents a data storage model where data is stored in logical pools, the physical storage spans multiple servers and often locations, and the physical environment is typically owned and managed by a hosting company and/or service provider. These cloud storage providers are responsible for keeping the data available and accessible, and the physical environment protected and running. People and organizations buy or lease storage capacity from the providers to store user, organization, or application data. Cloud storage services may be accessed through a co-located cloud computer service, a web service application programming interface (API) or by applications that utilize the API, such as cloud desktop storage, a cloud storage gateway or Web-based content management systems.",
  "cpc": [
    "G06F 16/125",
    "G06F 11/1448",
    "G06F 11/1451",
    "G06F 11/1461",
    "G06F 11/1469",
    "G06F 16/1734",
    "G06F 16/1748",
    "G06F 16/181",
    "G06F 16/1873",
    "G06F 21/6218",
    "G06F 2201/815",
    "G06F 2221/2141",
    "G06F 3/0604",
    "G06F 3/0619",
    "G06F 3/064",
    "G06F 3/0652",
    "G06F 3/067",
    "H04L 67/1097"
  ],
  "ipc": [
    "G06F 17/30",
    "G06F 11/14",
    "G06F 21/62",
    "H04L 29/08",
    "G06F 16/11",
    "G06F 16/17",
    "G06F 16/174",
    "G06F 16/18"
  ],
  "inventors": [
    "Geoffrey Bourgeois",
    "Greg Campbell"
  ],
  "filing_date": "2018-05-17",
  "publication_date": "2021-08-24",
  "grant_date": "2021-08-24",
  "priority_date": "2017-05-18",
  "application_number": "US-201815982255-A",
  "family_id": "64270163",
  "cited_by_count": 1,
  "citations": [
    "US20150127607A1"
  ]
}

Record 1,515 of 8,000 in Patents full text (MLC-0201). Request the full dataset.