Storage of shard data
AssigneeGM Cruise Holdings LLC
InventorsMikhail Chernov, Xiaojun Sun
Life of this patent
Estimating the term…
Abstract
A method for storing shard data and data formats for storing shard data are proposed. Shard data entries are generated and stored, wherein each shard data entry comprises a definition of one or more semantic objects covered by the shard data entry. Shard metadata is generated and stored, wherein the metadata comprises references to the shard data entries and, for each of the shard data entries, data representative of a bounding box indicative of an area in a geographical area that is covered by the shard data entry.
Claims20
A method comprising:
- determining semantic objects to be stored in a shard;
- generating a shard file to be stored in a file storage system, wherein the shard file includes data of the semantic objects for the shard;
- generating shard metadata for the shard, wherein the shard metadata includes:
- (1) a unique string value representing a name of the shard, the unique string value comprising a non-unique string value representing a subtype of the shard and a sequence number;
- and
- (2) floating point values defining a polygonal shape indicative of an area that is covered by the semantic objects of the shard;
- generating a shard metadata file having the shard metadata for the shard to be stored in the file storage system;
- and
- delivering the shard file to one or more clients using the shard metadata file, wherein the one or more clients include one or more of:
- an autonomous vehicle, a vehicle, and a computer environment.
One or more non-transitory computer-readable storage media comprising instruction for execution which, when executed by a processor, are operable to perform operations, the operations comprising:
- determining, from a shard-to-object relations database, semantic objects to be stored in a shard;
- generating a shard file to be stored in a file storage system, wherein the shard file includes data of the semantic objects for the shard;
- generating shard metadata for the shard, wherein the shard metadata includes:
- (1) an integer value as an identifier of the shard, the integer value being used as a foreign key to the shard-to-object relations database;
- (2) a unique string value representing a name of the shard, the unique string value comprising a non-unique string value representing a subtype of the shard and a sequence number;
- and
- (3) floating point values defining a polygonal shape indicative of an area that is covered by the semantic objects of the shard;
- generating a shard metadata file having the shard metadata for the shard to be stored in the file storage system;
- and
- delivering the shard file to one or more clients using the shard metadata file, wherein the one or more clients include one or more of:
- an autonomous vehicle, a vehicle, and a computer environment.
A computer system comprising:
- one or more processors;
- one or more non-transient computer-readable storage devices to store instructions;
- one or more database storage devices to store shard data comprising:
- semantic objects linked to a shard;
- and
- shard metadata corresponding to the shard, wherein the shard metadata for a shard includes:
- (1) a unique string value representing a name of the shard, the unique string value comprising a non-unique string value representing a subtype of the shard and a sequence number;
- and (2) floating point values defining a polygonal shape indicative of an area that is covered by the semantic objects of the shard;
- wherein the instructions encode a database exporter to export the shard data from the one or more database storage devices;
- and
- a file storage system to:
- receive shard data exported by the database exporter and store the shard data as a shard file, wherein a shard file includes data for the semantic objects linked to the shard;
- and
- receive shard metadata exported by the database exporter and store the shard metadata and other shard metadata for other shards as a shard metadata file;
- wherein the instructions further encode an uploader to deliver the shard file to one or more clients using the shard metadata file, the one or more clients including one or more of:
- an autonomous vehicle, a vehicle, and a computer environment.
Dependencies are inferred from the claim text.