CN114968941A - Vehicle-end file deleting method and system, electronic equipment and readable storage medium - Google Patents
Vehicle-end file deleting method and system, electronic equipment and readable storage medium Download PDFInfo
- Publication number
- CN114968941A CN114968941A CN202210615572.5A CN202210615572A CN114968941A CN 114968941 A CN114968941 A CN 114968941A CN 202210615572 A CN202210615572 A CN 202210615572A CN 114968941 A CN114968941 A CN 114968941A
- Authority
- CN
- China
- Prior art keywords
- file
- vehicle
- factor
- vehicle end
- score
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 61
- 230000032683 aging Effects 0.000 claims description 80
- 206010021703 Indifference Diseases 0.000 claims description 31
- 238000007726 management method Methods 0.000 claims description 29
- 238000004364 calculation method Methods 0.000 claims description 11
- 238000012217 deletion Methods 0.000 claims description 8
- 230000037430 deletion Effects 0.000 claims description 8
- 238000013523 data management Methods 0.000 claims description 6
- 238000000605 extraction Methods 0.000 claims description 3
- 238000012216 screening Methods 0.000 claims description 3
- 238000004590 computer program Methods 0.000 description 18
- 238000004891 communication Methods 0.000 description 12
- 238000010586 diagram Methods 0.000 description 12
- 238000012545 processing Methods 0.000 description 9
- 230000006870 function Effects 0.000 description 6
- 230000008569 process Effects 0.000 description 6
- 230000003287 optical effect Effects 0.000 description 5
- 238000013075 data extraction Methods 0.000 description 4
- 238000011161 development Methods 0.000 description 4
- 230000018109 developmental process Effects 0.000 description 4
- 238000012423 maintenance Methods 0.000 description 4
- 238000012986 modification Methods 0.000 description 4
- 230000004048 modification Effects 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 206010063385 Intellectualisation Diseases 0.000 description 2
- 238000013507 mapping Methods 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 239000004065 semiconductor Substances 0.000 description 2
- 238000007792 addition Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004422 calculation algorithm Methods 0.000 description 1
- 230000015556 catabolic process Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/16—File or folder operations, e.g. details of user interfaces specifically adapted to file systems
- G06F16/162—Delete operations
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2455—Query execution
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/284—Relational databases
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computational Linguistics (AREA)
- Human Computer Interaction (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention relates to the technical field of file management, and discloses a vehicle end file deleting method, a system, electronic equipment and a readable storage medium.
Description
Technical Field
The invention relates to the technical field of file management, in particular to a method and a system for deleting a vehicle-side file, electronic equipment and a readable storage medium.
Background
The vehicle intellectualization is the inevitable trend of the future development of the automobile, along with the continuous development of the automobile intellectualization and the continuous increase of the data volume, the internal controller of the intelligent automobile can generate the vehicle end data with use value according to different automobile scenes, and the vehicle end data can be used for secondary calculation of a vehicle end or uploaded to a cloud end for reuse. However, the vehicle is not only limited by the factors such as low battery power, high CPU load of the controller, etc., but also affected by external factors such as poor network signals and damaged communication network, so that the vehicle-side data cannot be uploaded to the cloud, and therefore the vehicle-side data needs to be temporarily stored in the local memory of the controller, and the vehicle-side data is uploaded to the cloud again under normal conditions.
At present, in order to prevent the situation that a sufficient running space cannot be provided for a controller program due to overflow of an internal storage space of a controller, and jamming, stagnation or even breakdown occurs, the storage duration of a vehicle-end file is queried regularly and circularly, and then the vehicle-end file is deleted according to a query result. However, the method cannot perform centralized management on the vehicle-end files, so that the deleting steps of the vehicle-end files are messy, the use value of the vehicle-end data cannot be accurately judged, the vehicle-end data is mistakenly deleted, and the risk of data loss and data error of the vehicle-end files exists.
Disclosure of Invention
The following presents a simplified summary in order to provide a basic understanding of some aspects of the disclosed embodiments. This summary is not an extensive overview nor is intended to identify key/critical elements or to delineate the scope of such embodiments but rather as a prelude to the more detailed description that is presented later.
In view of the above disadvantages of the prior art, the present invention discloses a method, a system, an electronic device and a readable storage medium for deleting a vehicle-side file, so as to perform centralized management on the vehicle-side file and avoid data loss and data errors of the vehicle-side file.
The invention discloses a vehicle end file deleting method, which comprises the following steps: acquiring a vehicle end file and a plurality of file attribute fields, and establishing a vehicle end database according to each file attribute field; generating file configuration information according to the vehicle-end file, and storing the file configuration information into the vehicle-end database, wherein the file configuration information comprises file attribute information corresponding to each file attribute field and file aging scores corresponding to the vehicle-end file, and the file aging scores are obtained by calculation according to at least part of the file attribute information; extracting data from the vehicle-side database to obtain the file aging score; and judging whether the vehicle end file is deleted or not according to the file aging score.
Optionally, the file attribute information is generated by: extracting the vehicle-end file to obtain original attribute information, wherein the original attribute information comprises at least one of file storage size, file storage position, generated scene label and file creation time; carrying out relation matching according to a preset priority corresponding relation to obtain a file priority corresponding to the generated scene label, and calculating according to the file creation time to obtain a file storage time corresponding to the vehicle end file; and determining at least one of the file storage size, the file storage position, the generated scene label, the file creation time, the file priority and the file storage duration as file attribute information.
Optionally, the file aging score is determined by: extracting information from the file attribute information to obtain one or more indifference factors; performing relationship matching according to a preset factor weight corresponding relationship to obtain a factor weight corresponding to each indifference factor, and inputting each indifference factor into a corresponding preset factor score formula for calculation to obtain a factor score corresponding to each indifference factor; and inputting each factor score and each factor weight into a preset aging score formula for calculation to obtain a file aging score corresponding to the vehicle end file.
Optionally, extracting information from the file attribute information to obtain one or more indifference factors, including: performing relationship matching according to a preset factor quantity corresponding relationship to obtain a cold desert factor dimension corresponding to the generated scene label, wherein the cold desert factor dimension comprises one dimension or multiple dimensions; if the dimension of the indifference factor comprises one dimension, determining the storage time of the file as the indifference factor; and if the dimension of the indifference factor comprises multiple dimensions, determining the storage duration of the file and the priority of the file as the indifference factor.
Optionally, the data extraction is performed on the vehicle-side database to obtain the file aging score, and the method includes: establishing a file management thread; the file management thread is used for carrying out information updating on file configuration information in the vehicle-end database according to a preset updating rule; the file management thread is also used for pulling data of the vehicle-end database to obtain the file configuration information.
Optionally, the vehicle end file includes one or more files, and whether to delete the vehicle end file is determined according to the file aging score, where the file aging score includes at least one of: comparing a file aging score corresponding to a vehicle end file with a preset factor score threshold, and determining whether to delete the vehicle end file according to a comparison result corresponding to the vehicle end file; and if the additional files are received and preset storage space conditions are met, screening each vehicle-end file according to the file aging scores corresponding to each vehicle-end file to obtain a target file, and deleting the target file, wherein the storage space conditions comprise that a predicted storage space is larger than or equal to a preset storage space threshold value, and the predicted storage space is obtained by summing the file storage size of the additional files and the file storage size of each vehicle-end file.
Optionally, after the vehicle-end database is established according to each of the file attribute fields, the method further includes: and establishing a management folder in a vehicle end database, wherein the management folder is used for storing the vehicle end files.
Optionally, after generating the file configuration information according to the vehicle end file, the method further includes: performing identification distribution on the vehicle end file to obtain a file identification corresponding to the vehicle end file; and adding the file identification into the file configuration information, and performing data management on the vehicle end file and the file configuration information in the vehicle end database based on the file identification.
The invention discloses a vehicle end file deleting system, which comprises: the acquisition module is used for acquiring a vehicle end file and a plurality of file attribute fields and establishing a vehicle end database according to each file attribute field; the generating module is used for generating file configuration information according to the vehicle-end file and storing the file configuration information into the vehicle-end database, wherein the file configuration information comprises file attribute information corresponding to each file attribute field and file aging scores corresponding to the vehicle-end file, and the file aging scores are obtained by calculation according to at least part of the file attribute information; the extraction module is used for extracting data from the vehicle-end database to obtain the file aging score; and the determining module is used for judging whether the vehicle end file is deleted according to the file aging score.
The invention discloses an electronic device, comprising: a processor and a memory; the memory is used for storing computer programs, and the processor is used for executing the computer programs stored by the memory so as to make the electronic equipment execute the method.
The invention discloses a computer-readable storage medium, on which a computer program is stored: which when executed by a processor implements the method described above.
The invention has the beneficial effects that:
and establishing a vehicle end database according to the acquired file attribute field, generating file configuration information according to the vehicle end file, storing the file configuration information into the vehicle end database, extracting a file aging score from the vehicle end database, and judging whether to delete the vehicle end file according to the file aging score. In this way, the vehicle end database is established, and the vehicle end database is used for generating, inquiring and pulling the file attribute information and the file aging score of the vehicle end file, so that the vehicle end file is managed in a centralized manner, a vehicle end controller can conveniently judge the use value of the vehicle end file through the file aging score, the deleting step of the vehicle end file is simplified, and data loss and data errors of the vehicle end file are avoided.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and together with the description, serve to explain the principles of the application. It is obvious that the drawings in the following description are only some embodiments of the application, and that for a person skilled in the art, other drawings can be derived from them without inventive effort. In the drawings:
FIG. 1 is a schematic flow chart illustrating a method for deleting a file at a vehicle end according to an embodiment of the present invention;
FIG. 2-a is a schematic diagram of a configuration of an end-of-vehicle controller in an embodiment of the present invention;
FIG. 2-b is a schematic diagram of another embodiment of an end-of-vehicle controller according to the present invention;
FIG. 3 is a schematic flow chart illustrating another method for deleting files at a vehicle end according to an embodiment of the present invention;
FIG. 4 is a schematic structural diagram of a vehicle-side file deletion system according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of an electronic device in an embodiment of the present invention.
Detailed Description
The embodiments of the present invention are described below with reference to specific embodiments, and other advantages and effects of the present invention will be easily understood by those skilled in the art from the disclosure of the present specification. The invention is capable of other and different embodiments and of being practiced or of being carried out in various ways, and its several details are capable of modification in various respects, all without departing from the spirit and scope of the present invention. It should be noted that, in the following embodiments and examples, subsamples may be combined with each other without conflict.
It should be noted that the drawings provided in the following embodiments are only for illustrating the basic idea of the present invention, and the components related to the present invention are only shown in the drawings rather than drawn according to the number, shape and size of the components in actual implementation, and the type, quantity and proportion of the components in actual implementation may be changed freely, and the layout of the components may be more complicated.
In the following description, numerous details are set forth to provide a more thorough explanation of embodiments of the present invention, however, it will be apparent to one skilled in the art that embodiments of the present invention may be practiced without these specific details, and in other embodiments, well-known structures and devices are shown in block diagram form, rather than in detail, in order to avoid obscuring embodiments of the present invention.
The terms "first," "second," and the like in the description and in the claims, and the above-described drawings of embodiments of the present disclosure, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It should be understood that the data so used may be interchanged under appropriate circumstances such that embodiments of the present disclosure described herein may be made. Furthermore, the terms "comprising" and "having," as well as any variations thereof, are intended to cover non-exclusive inclusions.
The term "plurality" means two or more, unless otherwise specified.
In the embodiment of the present disclosure, the character "/" indicates that the preceding and following objects are in an or relationship. For example, A/B represents: a or B.
The term "and/or" is an associative relationship that describes objects, meaning that three relationships may exist. For example, a and/or B, represents: a or B, or A and B.
Referring to fig. 1, an embodiment of the present disclosure provides a method for deleting a vehicle-side file, including:
step S101, obtaining a vehicle end file and a plurality of file attribute fields, and establishing a vehicle end database according to each file attribute field;
step S102, generating file configuration information according to the vehicle-end file, and storing the file configuration information into a vehicle-end database;
the file configuration information comprises file attribute information corresponding to each file attribute field and file aging scores corresponding to the vehicle-end files, and the file aging scores are obtained by calculation according to at least part of the file attribute information;
step S103, data extraction is carried out on the vehicle-side database to obtain a file aging score;
and step S104, judging whether the vehicle end file is deleted or not according to the file aging score.
The vehicle end file deleting method comprises the steps of establishing a vehicle end database according to an obtained file attribute field, generating file configuration information according to a vehicle end file, storing the file configuration information into the vehicle end database, extracting a file aging score from the vehicle end database, and judging whether to delete the vehicle end file according to the file aging score. In this way, the vehicle end database is established, and the vehicle end database is used for generating, inquiring and pulling the file attribute information and the file aging score of the vehicle end file, so that the vehicle end file is managed in a centralized manner, a vehicle end controller can conveniently judge the use value of the vehicle end file through the file aging score, the deleting step of the vehicle end file is simplified, and data loss and data errors of the vehicle end file are avoided.
Optionally, establishing a vehicle-end database according to each file attribute field, including: the method comprises the steps of establishing a vehicle-end database based on an SQLite (lightweight database), and establishing a File attribute field in the vehicle-end database through a data manager (data manager), wherein the File attribute field comprises one or more of File identification (File ID), File storage size, File storage position, generated scene label, File establishing time, File priority, File storage duration, File aging score, File modification time, File deletion time and the like.
Optionally, after the vehicle-end database is established according to the file attribute fields, the method further includes: and establishing a management folder in the vehicle-end database, wherein the management folder is used for storing vehicle-end files.
Like this, through managing the folder unified storage car end file, compare in putting into a plurality of folders with car end file classification, be convenient for carry out data processing logic to the car end file, realize the centralized management to the car end file, promoted development efficiency and upload high in the clouds efficiency to maintenance cost has been reduced.
Optionally, the file attribute information is generated by: extracting the vehicle-end file to obtain original attribute information, wherein the original attribute information comprises at least one of file storage size, file storage position, generated scene label and file creation time; carrying out relation matching according to a preset priority corresponding relation to obtain a file priority corresponding to the generated scene label, and calculating according to file creation time to obtain file storage time corresponding to the vehicle end file; and determining at least one of file storage size, file storage position, scene tag generation, file creation time, file priority and file storage duration as file attribute information.
In some embodiments, generating the context label includes one or more of a collision context, a driving context, a misfire context, a fault context, and the like, of the vehicle.
Optionally, the file aging score is determined by: extracting information of the file attribute information to obtain one or more indifference factors; performing relationship matching according to a preset factor weight corresponding relationship to obtain factor weights corresponding to the desert factors, and inputting the desert factors into corresponding preset factor score formulas to calculate to obtain factor scores corresponding to the desert factors; and inputting the factor scores and the factor weights into a preset aging score formula for calculation to obtain the file aging scores corresponding to the vehicle end files.
Optionally, extracting information from the file attribute information to obtain one or more indifference factors, including: performing relationship matching according to a preset factor quantity corresponding relationship to obtain a cold desert factor dimension corresponding to the generated scene label, wherein the cold desert factor dimension comprises one dimension or multiple dimensions; if the dimension of the indifference factor comprises one dimension, determining the storage time of the file as the indifference factor; and if the dimension of the indifference factor comprises multiple dimensions, determining the storage time length of the file and the priority of the file as the indifference factor.
In some embodiments, the indifference factor is not limited to the file storage duration and the file priority, and may also be extended by file attribute information such as the file storage size and the generated scene tag.
Therefore, one or more indifference factors are determined from the file attribute information, and compared with the method that the use value of the vehicle-end file is singly judged through the file storage duration, the aging score of the file is determined through the multiple indifference factors, the reference range of the aging score of the file is increased, the judgment flexibility is improved, the use value of the file is judged more accurately through the aging score of the file, and the useful vehicle-end file is prevented from being deleted by mistake.
Optionally, the preset factor score formula corresponding to the file storage duration includes:
in the formula, x 1 The method comprises the steps of obtaining a factor score corresponding to file storage time, wherein t is the file storage time, e is a natural constant, and a is a constant coefficient, wherein the unit of the file storage time is day.
Optionally, the preset factor score formula corresponding to the file priority includes:
in the formula, x 2 The file priority is a factor score corresponding to the file priority, M is the file priority, and M is a preset maximum value corresponding to the file priority, wherein the greater the file priority is, the higher the importance degree of the vehicle-end file is.
In some embodiments, each factor score is normalized such that each factor score ranges in value [0,1 ].
In some embodiments, the factor score corresponds to a factor weight that is a sum of 1.
Optionally, the file aging score corresponding to the vehicle end file is determined by the following formula:
in the formula, S is the aging score of the file corresponding to the vehicle end file, n is the number of factor scores, and x i Is the ith factor score, w i And the factor weight corresponding to the ith factor score.
In some embodiments, if the file storage duration is 7 days, the file priority is 8, the factor weight corresponding to the file storage duration is 0.5, the factor weight corresponding to the file priority is 0.5, and the constant coefficient is
The file aging score corresponding to the car-end file is 0.448.
Optionally, after generating the file configuration information according to the vehicle-end file, the method further includes: carrying out identification distribution on the vehicle end file to obtain a file identification corresponding to the vehicle end file; and adding the file identification into the file configuration information, and performing data management on the vehicle end file and the file configuration information in the vehicle end database based on the file identification.
Optionally, the data management includes addition, deletion, modification and check.
Therefore, the File identification (File ID) is used as the unique key word of the vehicle end File, so that data management of the vehicle end File is facilitated, the File aging score is obtained, and the diversified management requirement of the vehicle end File is met.
In some embodiments, the file configuration information is created in JSON (JSON Object Notation) format.
In some embodiments, when a vehicle is started, data is pulled from a cloud (a server side) to obtain a configuration file corresponding to a vehicle side file, and the configuration file is updated, wherein the configuration file comprises a scene label, a scene event and a corresponding relationship between the scene label and the scene event; extracting data from the updated configuration file and storing the data into an operation memory; and when a scene event corresponding to the scene tag occurs, writing the scene tag into the vehicle-end database together according to the scene tag corresponding to the scene event.
In some embodiments, the scene tag determines a vehicle-end file processing mode, that is, if the indifference factor dimension corresponding to the scene tag is one-dimensional, the data extracted from the updated configuration file includes a factor score threshold; and if the dimension of the indifference factor corresponding to the scene label is multidimensional, extracting data from the updated configuration file, wherein the data comprises a factor score threshold, file storage duration and file priority.
Optionally, the data extraction is performed on the vehicle-side database to obtain a file aging score, and the method includes: establishing a file management thread; the file management thread is used for updating information of file configuration information in the vehicle-end database according to a preset updating rule; the file management thread is also used for pulling data of the vehicle-end database to obtain file configuration information.
Optionally, the update rule comprises at least one of: after receiving the additional file; uploading the vehicle end file to the front of the cloud end; after a preset updating time period, which includes 30s to 7 days, elapses, for example, the preset updating time period is 30 s.
Optionally, after the data of the vehicle-side database is pulled to obtain the file configuration information, the file management thread is further configured to store the file configuration information in an associated container of a controller memory map (map).
Optionally, the file management thread is further configured to obtain a file storage location corresponding to each vehicle-end file; and if the folder corresponding to the file storage position does not exist, creating the folder corresponding to the file storage position.
Optionally, the vehicle end file includes one or more.
Optionally, the determining whether to delete the vehicle-end file according to the file aging score includes at least one of: comparing the file aging score corresponding to the vehicle end file with a preset factor score threshold, and determining whether to delete the vehicle end file according to a comparison result corresponding to the vehicle end file; and if the additional files are received and preset storage space conditions are met, screening the vehicle-end files according to the file aging scores corresponding to the vehicle-end files to obtain target files, and deleting the target files, wherein the storage space conditions comprise that the predicted storage space is larger than or equal to a preset storage space threshold value, and the predicted storage space is obtained by summing the file storage size of the additional files and the file storage size of the vehicle-end files.
Therefore, the file aging score and the file storage space are determined from the database, compared with the method for regularly and circularly inquiring the storage time to delete the vehicle-end file, the vehicle-end file is directly deleted according to the read data to meet the requirement of the storage space without polling, the deletion efficiency is improved, and the maintenance cost is reduced.
Optionally, the method further comprises: acquiring a deletion instruction comprising an attribute identifier, wherein the attribute identifier is used for representing at least part of file attribute information; matching the vehicle end files of the vehicle end database according to the attribute identification to obtain data to be deleted corresponding to the attribute identification; and deleting the data to be deleted.
Therefore, the vehicle-end files can be matched through the file attribute information of the vehicle-end database to obtain the data to be deleted, and the vehicle-end data can be deleted conveniently.
Optionally, if the vehicle-end controller is connected to the cloud, the method further includes: and uploading the vehicle end file and the file configuration information corresponding to the vehicle end file to the cloud end, and reserving the vehicle end file and the file configuration information corresponding to the vehicle end file.
Therefore, the vehicle end files of the vehicle end database and the file configuration information corresponding to the vehicle end files are reserved through the vehicle end database, the vehicle end files are backed up, mapping management between the cloud end and the vehicle end is established through file identification, and compared with the situation that the vehicle end files are directly deleted after being uploaded to the cloud end, the situation that the vehicle end files are lost due to uploading misjudgment or cloud end errors is avoided.
As shown in connection with fig. 2-a, the vehicle end controller includes a vehicle end controller 201 and a local memory 202. The local storage 202 is used for storing vehicle-end files; the vehicle-end controller 201 is configured to poll the vehicle-end files in the local storage 202, so as to delete the vehicle-end files according to the storage duration.
As shown in fig. 2-b, an embodiment of the present disclosure provides a vehicle-end controller for implementing a vehicle-end file deletion method, which includes a vehicle-end controller 201, a local storage 202, and a vehicle-end database 203. The local storage 202 is used for storing vehicle-end files; the vehicle-end database 203 is used for uniformly storing the vehicle-end files in the local storage 202 in a management folder and generating file configuration information corresponding to the vehicle-end files; the vehicle-end controller 201 is configured to manage the vehicle-end files according to the file configuration information, and determine whether to delete the corresponding vehicle-end files by pulling the aging scores of the files.
Referring to fig. 3, an embodiment of the present disclosure provides a method for deleting a vehicle-side file, including:
step S301, a vehicle-end controller acquires a plurality of file attribute fields;
step S302, the vehicle end controller establishes a vehicle end database according to each file attribute field;
step S303, a vehicle end database acquires a vehicle end file, and stores the vehicle end file in a preset management folder;
step S304, the vehicle end database generates file configuration information corresponding to the vehicle end file;
the file configuration information comprises one or more of file identification, file storage size, file storage position, generated scene label, file creation time, file priority, file storage time, file aging score, file modification time, file deletion time and the like;
step S305, the vehicle-end controller pulls the file aging score from the vehicle-end database;
step S306, the vehicle-end controller determines whether to delete the corresponding vehicle-end file according to the file aging score;
step S307, the vehicle end controller pulls the vehicle end file and the file configuration information corresponding to the vehicle end file;
step S308, the vehicle end controller uploads the vehicle end file and file configuration information corresponding to the vehicle end file to the cloud end.
The vehicle end file deleting method comprises the steps of establishing a vehicle end database according to an obtained file attribute field, generating file configuration information according to a vehicle end file, storing the file configuration information into the vehicle end database, extracting a file aging score from the vehicle end database, and judging whether to delete the vehicle end file according to the file aging score. Has the following advantages:
the method comprises the steps that firstly, a vehicle end database is established, and file attribute information and file aging scores of vehicle end files are generated, inquired and pulled by the vehicle end database, so that the vehicle end files are managed in a centralized mode, a vehicle end controller can judge the use value of the vehicle end files through the file aging scores conveniently, the deleting steps of the vehicle end files are simplified, and data loss and data errors of the vehicle end files are avoided;
secondly, vehicle-end files are stored in a unified mode through the management file folders, compared with the mode that the vehicle-end files are placed into a plurality of file folders in a classified mode, data processing logic of the vehicle-end files is convenient to execute, centralized management of the vehicle-end files is achieved, development efficiency and cloud uploading efficiency are improved, and maintenance cost is reduced;
thirdly, one or more indifference factors are determined from the file attribute information, and compared with the method that the use value of the vehicle-end file is singly judged through the file storage duration, the aging score of the file is determined through the multiple indifference factors, the reference range of the aging score of the file is increased, and the judgment flexibility is improved, so that the use value of the file is judged more accurately through the aging score of the file, and the useful vehicle-end file is prevented from being deleted by mistake;
fourthly, the file identification is used as the only key word of the vehicle end file, so that data management of the vehicle end file is facilitated, the aging score of the file is obtained, and the diversified management requirement of the vehicle end file is met;
fifthly, determining the file aging score and the file storage space from the database, deleting the vehicle-end file compared with the time for inquiring the storage space in a timing cycle, not polling the vehicle-end file, and directly deleting the vehicle-end file according to the read data to meet the requirement of the storage space, so that the deleting efficiency is improved, and the maintenance cost is reduced;
sixthly, vehicle end files can be matched through file attribute information of a vehicle end database to obtain data to be deleted, and vehicle end data can be deleted conveniently;
and seventhly, the vehicle end files of the vehicle end database and file configuration information corresponding to the vehicle end files are reserved through the vehicle end database, so that the vehicle end files are backed up, mapping management between the cloud end and the vehicle end is established through file identification, and compared with the situation that the vehicle end files are directly deleted after being uploaded to the cloud end, the situation that the vehicle end files are lost due to uploading misjudgment or cloud end errors is avoided.
Referring to fig. 4, an embodiment of the present disclosure provides a vehicle-side file deleting system, which includes an obtaining module 401, a generating module 402, an extracting module 403, and a determining module 404; the obtaining module 401 is configured to obtain a vehicle-end file and a plurality of file attribute fields, and establish a vehicle-end database according to each file attribute field; the generating module 402 is configured to generate file configuration information according to the vehicle-end file, and store the file configuration information in a vehicle-end database, where the file configuration information includes file attribute information corresponding to each file attribute field and a file aging score corresponding to the vehicle-end file, and the file aging score is calculated according to at least a part of the file attribute information; the extraction module 403 is configured to perform data extraction on the vehicle-side database to obtain a file aging score; the determining module 404 is configured to determine whether to delete the vehicle-end file according to the file aging score.
The vehicle-end file deleting system provided by the embodiment of the disclosure is adopted, a vehicle-end database is established according to the obtained file attribute field, file configuration information is generated according to the vehicle-end file and stored in the vehicle-end database, the file aging score is extracted from the vehicle-end database, and whether the vehicle-end file is deleted or not is judged according to the file aging score. In this way, the vehicle end database is established, and the vehicle end database is used for generating, inquiring and pulling the file attribute information and the file aging score of the vehicle end file, so that the vehicle end file is managed in a centralized manner, a vehicle end controller can conveniently judge the use value of the vehicle end file through the file aging score, the deleting step of the vehicle end file is simplified, and data loss and data errors of the vehicle end file are avoided.
FIG. 5 illustrates a schematic structural diagram of a computer system suitable for use in implementing the electronic device of an embodiment of the present application. It should be noted that the computer system 500 of the electronic device shown in fig. 5 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present application.
As shown in fig. 5, the computer system 500 includes a Central Processing Unit (CPU)501, which can perform various appropriate actions and processes, such as executing the methods in the above-described embodiments, according to a program stored in a Read-Only Memory (ROM) 502 or a program loaded from a storage section 508 into a Random Access Memory (RAM) 503. In the RAM 503, various programs and data necessary for system operation are also stored. The CPU 501, ROM 502, and RAM 503 are connected to each other via a bus 504. An Input/Output (I/O) interface 505 is also connected to bus 504.
The following components are connected to the I/O interface 505: an input portion 506 including a keyboard, a mouse, and the like; an output section 507 including a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, a speaker, and the like; a storage portion 508 including a hard disk and the like; and a communication section 509 including a Network interface card such as a LAN (Local Area Network) card, a modem, or the like. The communication section 509 performs communication processing via a network such as the internet. The driver 510 is also connected to the I/O interface 505 as necessary. A removable medium 511 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 510 as necessary, so that a computer program read out therefrom is mounted into the storage section 508 as necessary.
In particular, according to embodiments of the application, the processes described above with reference to the flow diagrams may be implemented as computer software programs. For example, embodiments of the present application include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising a computer program for performing the method illustrated by the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 509, and/or installed from the removable medium 511. The computer program executes various functions defined in the system of the present application when executed by a Central Processing Unit (CPU) 501.
It should be noted that the computer readable medium shown in the embodiments of the present application may be a computer readable signal medium or a computer readable storage medium or any combination of the two. The computer readable storage medium may be, for example, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a Read-Only Memory (ROM), an Erasable Programmable Read-Only Memory (EPROM), a flash Memory, an optical fiber, a portable Compact Disc Read-Only Memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present application, a computer-readable signal medium may comprise a propagated data signal with a computer-readable computer program embodied therein, either in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. The computer program embodied on the computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wired, etc., or any suitable combination of the foregoing.
The disclosed embodiments also provide a computer-readable storage medium on which a computer program is stored, which when executed by a processor implements any of the methods in the embodiments.
The computer-readable storage medium in the embodiments of the present disclosure may be understood by those skilled in the art as follows: all or part of the steps for implementing the above method embodiments may be performed by hardware associated with a computer program. The aforementioned computer program may be stored in a computer readable storage medium. When executed, the program performs steps comprising the method embodiments described above; and the aforementioned storage medium includes: various media that can store program codes, such as ROM, RAM, magnetic or optical disks.
The electronic device disclosed in this embodiment includes a processor, a memory, a transceiver, and a communication interface, where the memory and the communication interface are connected to the processor and the transceiver and perform mutual communication, the memory is used to store a computer program, the communication interface is used to perform communication, and the processor and the transceiver are used to run the computer program, so that the electronic device performs the steps of the above method.
In this embodiment, the Memory may include a Random Access Memory (RAM), and may also include a non-volatile Memory (non-volatile Memory), such as at least one disk Memory.
The Processor may be a general-purpose Processor, and includes a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), a Network Processor (NP), and the like; the Integrated Circuit may also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, a discrete Gate or transistor logic device, or a discrete hardware component.
The above description and drawings sufficiently illustrate embodiments of the disclosure to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, and other changes. The examples merely typify possible variations. Individual components and functions are optional unless explicitly required, and the sequence of operations may vary. Portions and subsamples of some embodiments may be included in or substituted for portions and subsamples of other embodiments. Furthermore, the words used in the specification are words of description only and are not intended to limit the claims. As used in the description of the embodiments and the claims, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. Similarly, the term "and/or" as used in this application is meant to encompass any and all possible combinations of one or more of the associated listed. Furthermore, the terms "comprises," "comprising," and variations thereof, when used in this application, specify the presence of stated sub-samples, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other sub-samples, integers, steps, operations, elements, components, and/or groups thereof. Without further limitation, an element defined by the phrase "comprising an …" does not exclude the presence of other like elements in a process, method or apparatus that comprises the element. In this document, each embodiment may be described with emphasis on differences from other embodiments, and the same and similar parts between the respective embodiments may be referred to each other. For methods, products, etc. of the embodiment disclosures, reference may be made to the description of the method section for relevance if it corresponds to the method section of the embodiment disclosure.
Those of skill in the art would appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software may depend upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the disclosed embodiments. It can be clearly understood by the skilled person that, for convenience and brevity of description, the specific working processes of the system, the apparatus and the unit described above may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the embodiments disclosed herein, the disclosed methods, products (including but not limited to devices, apparatuses, etc.) may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units may be only one logical division, and there may be other divisions in actual implementation, for example, a plurality of units or components may be combined or may be integrated into another system, or some subsamples may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form. The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to implement the present embodiment. In addition, functional units in the embodiments of the present disclosure may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. In the description corresponding to the flowcharts and block diagrams in the figures, operations or steps corresponding to different blocks may also occur in different orders than disclosed in the description, and sometimes there is no specific order between the different operations or steps. For example, two sequential operations or steps may in fact be executed substantially concurrently, or they may sometimes be executed in the reverse order, depending upon the functionality involved. Each block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
Claims (11)
1. A vehicle end file deleting method is characterized by comprising the following steps:
acquiring a vehicle end file and a plurality of file attribute fields, and establishing a vehicle end database according to each file attribute field;
generating file configuration information according to the vehicle-end file, and storing the file configuration information into the vehicle-end database, wherein the file configuration information comprises file attribute information corresponding to each file attribute field and file aging scores corresponding to the vehicle-end file, and the file aging scores are obtained by calculation according to at least part of the file attribute information;
extracting data from the vehicle-side database to obtain the file aging score;
and judging whether the vehicle end file is deleted or not according to the file aging score.
2. The method of claim 1, wherein the file attribute information is generated by:
extracting the vehicle-end file to obtain original attribute information, wherein the original attribute information comprises at least one of file storage size, file storage position, generated scene label and file creation time;
carrying out relation matching according to a preset priority corresponding relation to obtain a file priority corresponding to the generated scene label, and calculating according to the file creation time to obtain a file storage time corresponding to the vehicle end file;
and determining at least one of the file storage size, the file storage position, the generated scene label, the file creation time, the file priority and the file storage duration as file attribute information.
3. The method of claim 2, wherein the file aging score is determined by:
extracting information from the file attribute information to obtain one or more indifference factors;
performing relationship matching according to a preset factor weight corresponding relationship to obtain a factor weight corresponding to each indifference factor, and inputting each indifference factor into a corresponding preset factor score formula for calculation to obtain a factor score corresponding to each indifference factor;
and inputting each factor score and each factor weight into a preset aging score formula for calculation to obtain a file aging score corresponding to the vehicle end file.
4. The method of claim 3, wherein extracting information from the file attribute information to obtain one or more indifference factors comprises:
performing relationship matching according to a preset factor quantity corresponding relationship to obtain a cold desert factor dimension corresponding to the generated scene label, wherein the cold desert factor dimension comprises one dimension or multiple dimensions;
if the dimension of the indifference factor comprises one dimension, determining the storage time of the file as the indifference factor;
and if the dimension of the indifference factor comprises multiple dimensions, determining the storage duration of the file and the priority of the file as the indifference factor.
5. The method of claim 1, wherein extracting data from the vehicle-side database to obtain the document aging score comprises:
establishing a file management thread;
the file management thread is used for carrying out information updating on file configuration information in the vehicle-end database according to a preset updating rule;
the file management thread is also used for pulling data of the vehicle-end database to obtain the file configuration information.
6. The method of claim 1, wherein the vehicle-end file includes one or more, and determining whether to delete the vehicle-end file based on the file aging score includes at least one of:
comparing a file aging score corresponding to a vehicle end file with a preset factor score threshold, and determining whether to delete the vehicle end file according to a comparison result corresponding to the vehicle end file;
and if the additional files are received and preset storage space conditions are met, screening each vehicle-end file according to the file aging scores corresponding to each vehicle-end file to obtain a target file, and deleting the target file, wherein the storage space conditions comprise that a predicted storage space is larger than or equal to a preset storage space threshold value, and the predicted storage space is obtained by summing the file storage size of the additional files and the file storage size of each vehicle-end file.
7. The method of any one of claims 1 to 6, wherein after building a vehicle-side database from each of the file attribute fields, the method further comprises:
and establishing a management folder in a vehicle end database, wherein the management folder is used for storing the vehicle end files.
8. The method of any of claims 1 to 6, wherein after generating file configuration information from the vehicle-end file, the method further comprises:
carrying out identification distribution on the vehicle end file to obtain a file identification corresponding to the vehicle end file;
and adding the file identification into the file configuration information, and performing data management on the vehicle end file and the file configuration information in the vehicle end database based on the file identification.
9. A vehicle-end file deletion system is characterized by comprising:
the acquisition module is used for acquiring a vehicle end file and a plurality of file attribute fields and establishing a vehicle end database according to each file attribute field;
the generating module is used for generating file configuration information according to the vehicle end file and storing the file configuration information into the vehicle end database, wherein the file configuration information comprises file attribute information corresponding to each file attribute field and file aging scores corresponding to the vehicle end file, and the file aging scores are obtained by calculation according to at least part of the file attribute information;
the extraction module is used for extracting data from the vehicle-end database to obtain the file aging score;
and the determining module is used for judging whether the vehicle end file is deleted according to the file aging score.
10. An electronic device, comprising:
one or more processors;
storage means for storing one or more programs which, when executed by the one or more processors, cause the electronic device to carry out the method of any one of claims 1 to 8.
11. A computer readable storage medium having computer readable instructions stored thereon which, when executed by a processor of a computer, cause the computer to perform the method of any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210615572.5A CN114968941A (en) | 2022-05-31 | 2022-05-31 | Vehicle-end file deleting method and system, electronic equipment and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210615572.5A CN114968941A (en) | 2022-05-31 | 2022-05-31 | Vehicle-end file deleting method and system, electronic equipment and readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114968941A true CN114968941A (en) | 2022-08-30 |
Family
ID=82960389
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210615572.5A Pending CN114968941A (en) | 2022-05-31 | 2022-05-31 | Vehicle-end file deleting method and system, electronic equipment and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114968941A (en) |
Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106802957A (en) * | 2017-01-19 | 2017-06-06 | 广东欧珀移动通信有限公司 | File management method, device and terminal device |
| CN108021698A (en) * | 2017-12-21 | 2018-05-11 | 努比亚技术有限公司 | Delet method, device and the computer-readable storage medium of storage file |
| CN108021590A (en) * | 2016-10-28 | 2018-05-11 | 阿里巴巴集团控股有限公司 | A kind of destination object attribute determining method, attribute update method and device |
| CN108280902A (en) * | 2018-01-19 | 2018-07-13 | 京东方科技集团股份有限公司 | The document handling method and device of vehicle-mounted monitoring equipment, vehicle-mounted monitoring equipment |
| CN109408469A (en) * | 2018-09-05 | 2019-03-01 | 中国平安人寿保险股份有限公司 | Stale data document handling method, device, electronic device and storage medium |
| CN110673800A (en) * | 2019-09-29 | 2020-01-10 | 苏州浪潮智能科技有限公司 | Data operation method, device and equipment of file system and readable storage medium |
| CN110737604A (en) * | 2019-08-30 | 2020-01-31 | 北京奇艺世纪科技有限公司 | method, device, electronic equipment and storage medium for automatically cleaning memory |
| CN111984601A (en) * | 2020-08-31 | 2020-11-24 | 深圳壹账通智能科技有限公司 | Log file deleting method and device, electronic equipment and storage medium |
| CN112486920A (en) * | 2020-11-23 | 2021-03-12 | 上海传兴科技有限公司 | File processing method, mobile terminal and storage medium |
| CN112817912A (en) * | 2021-02-20 | 2021-05-18 | 平安科技（深圳）有限公司 | File management method and device, computer equipment and storage medium |
| CN114238233A (en) * | 2021-12-16 | 2022-03-25 | 中国平安财产保险股份有限公司 | Automatic file cleaning method, device, equipment and storage medium |
| CN114356856A (en) * | 2021-12-21 | 2022-04-15 | 苏州凌云视界智能设备有限责任公司 | Data deleting method, device, equipment and storage medium |
-
2022
- 2022-05-31 CN CN202210615572.5A patent/CN114968941A/en active Pending
Patent Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108021590A (en) * | 2016-10-28 | 2018-05-11 | 阿里巴巴集团控股有限公司 | A kind of destination object attribute determining method, attribute update method and device |
| CN106802957A (en) * | 2017-01-19 | 2017-06-06 | 广东欧珀移动通信有限公司 | File management method, device and terminal device |
| CN108021698A (en) * | 2017-12-21 | 2018-05-11 | 努比亚技术有限公司 | Delet method, device and the computer-readable storage medium of storage file |
| CN108280902A (en) * | 2018-01-19 | 2018-07-13 | 京东方科技集团股份有限公司 | The document handling method and device of vehicle-mounted monitoring equipment, vehicle-mounted monitoring equipment |
| CN109408469A (en) * | 2018-09-05 | 2019-03-01 | 中国平安人寿保险股份有限公司 | Stale data document handling method, device, electronic device and storage medium |
| CN110737604A (en) * | 2019-08-30 | 2020-01-31 | 北京奇艺世纪科技有限公司 | method, device, electronic equipment and storage medium for automatically cleaning memory |
| CN110673800A (en) * | 2019-09-29 | 2020-01-10 | 苏州浪潮智能科技有限公司 | Data operation method, device and equipment of file system and readable storage medium |
| CN111984601A (en) * | 2020-08-31 | 2020-11-24 | 深圳壹账通智能科技有限公司 | Log file deleting method and device, electronic equipment and storage medium |
| CN112486920A (en) * | 2020-11-23 | 2021-03-12 | 上海传兴科技有限公司 | File processing method, mobile terminal and storage medium |
| CN112817912A (en) * | 2021-02-20 | 2021-05-18 | 平安科技（深圳）有限公司 | File management method and device, computer equipment and storage medium |
| CN114238233A (en) * | 2021-12-16 | 2022-03-25 | 中国平安财产保险股份有限公司 | Automatic file cleaning method, device, equipment and storage medium |
| CN114356856A (en) * | 2021-12-21 | 2022-04-15 | 苏州凌云视界智能设备有限责任公司 | Data deleting method, device, equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3951321A1 (en) | Method and system for rapid generation of reference driving route, terminal and storage medium | |
| CN111951144A (en) | Method and device for determining violation road section and computer readable storage medium | |
| CN108711025B (en) | Car rental vehicle inventory query method and device, electronic equipment and storage medium | |
| CN114036253A (en) | High-precision map data processing method and device, electronic equipment and medium | |
| CN114003613A (en) | High-precision map lane line updating method and device, electronic equipment and storage medium | |
| CN109300139A (en) | Method for detecting lane lines and device | |
| CN114863047A (en) | Intersection virtual line drawing method and device, electronic equipment and computer program product | |
| US20220242458A1 (en) | Method for seclecting parking location, intelligent control device and autonomous driving vehicle | |
| CN113139139A (en) | Method, apparatus, electronic device, and medium for determining boarding point | |
| CN114968941A (en) | Vehicle-end file deleting method and system, electronic equipment and readable storage medium | |
| CN114548192A (en) | Sample data processing method and device, electronic equipment and medium | |
| CN116415747A (en) | Method and device for determining carpooling route and electronic equipment | |
| CN113780480B (en) | Method for constructing multi-target detection and category identification model based on YOLOv5 | |
| CN114005015B (en) | Training method of image recognition model, electronic device and storage medium | |
| CN113139258B (en) | Road data processing method, device, equipment and storage medium | |
| CN115115231A (en) | Index system construction method and device, electronic equipment and storage medium | |
| CN113312457B (en) | Method, computing system, and computer readable medium for problem resolution | |
| CN115062240A (en) | Parking lot sorting method and device, electronic equipment and storage medium | |
| CN109726615A (en) | A kind of recognition methods of road boundary and device | |
| CN112579841B (en) | Multi-mode database establishment method, retrieval method and system | |
| CN112150853A (en) | Parking lot management method and device, storage medium and electronic equipment | |
| CN116226297B (en) | Visual search method, system, equipment and storage medium for data model | |
| CN115984827B (en) | Point cloud sensing method, computer equipment and computer readable storage medium | |
| CN113096436B (en) | Indoor parking method and device | |
| CN113656425B (en) | Electronic map updating method and device, electronic equipment, storage medium and product |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |