GB/T 31916.3-2018 PDF EnglishUS$760.00 · In stock · Download in 9 seconds
GB/T 31916.3-2018: Information Technology - Cloud Data Storage and Management - Part 3: Distributed File Storage Application Interface Delivery: 9 seconds. True-PDF full-copy in English & invoice will be downloaded + auto-delivered via email. See step-by-step procedure Status: Valid
Similar standardsGB/T 31916.3-2018: Information Technology - Cloud Data Storage and Management - Part 3: Distributed File Storage Application Interface---This is an excerpt. Full copy of true-PDF in English version (including equations, symbols, images, flow-chart, tables, and figures etc.), auto-downloaded/delivered in 9 seconds, can be purchased online: https://www.ChineseStandard.net/PDF.aspx/GBT31916.3-2018 NATIONAL STANDARD OF THE PEOPLE’S REPUBLIC OF CHINA ICS 35.100.05 L 79 Information Technology - Cloud Data Storage and Management - Part 3.Distributed File Storage Application Interface Issued on. JUNE 7, 2018 Implemented on. JANUARY 1, 2019 Issued by. State Administration for Market Regulation; Standardization Administration of the People’s Republic of China. Table of ContentsForeword... 5 1 Scope... 6 2 Compliance... 6 3 Normative References... 6 4 Terms, Definitions and Abbreviations... 7 4.1 Terms and Definitions... 7 4.2 Abbreviations... 7 5 Interface Positioning and System Structure of Distributed File Storage... 7 5.1 Interface Positioning of Distributed File Storage... 7 5.2 System Structure of Distributed File Storage... 8 6 General Requirements of Application Interface... 9 6.1 Overview... 9 6.2 Naming Rules... 9 6.3 Supplementary Error Message... 10 6.4 Public Request Header... 10 6.5 Public Response Header... 10 7 Requirements of File Interface... 10 7.1 Overview... 10 7.2 Create File... 11 7.3 Delete File... 14 7.4 Upload File... 16 7.5 Download File... 19 7.6 Append File... 22 7.7 Copy File... 24 7.8 Rename File... 27 7.9 View File Status... 29 7.10 Modify File Attribute... 32 7.11 File Search... 35 7.12 File Read... 37 7.13 File Write... 40 8 Requirements of Folder Interface... 42 8.1 Overview... 42 8.2 Create Folder... 42 8.3 Delete Folder... 45 8.4 Upload Folder... 47 8.5 Download Folder... 50 8.6 Copy Folder... 52 8.7 Rename Folder... 55 8.8 View Folder Status... 57 8.9 Modify Folder Attribute... 59 8.10 Folder Search... 62 8.11 List Folder Content... 64 9 Requirements of Recycle Bin Interface... 66 9.1 Overview... 66 9.2 Recover Files in Recycle Bin... 67 9.3 Query Files in Recycle Bin... 69 9.4 Final Delete Files in Recycle Bin... 71 9.5 Clear Trash... 73 9.6 Recover All... 75 10 Requirements of Extended Attribute Interface... 77 10.1 Overview... 77 10.2 Set Extended Attribute... 77 10.3 Delete Extended Attribute... 80 10.4 Read Extended Attribute... 82 10.5 List Extended Attribute... 85 11 Requirements of Snapshot Interface... 87 11.1 Overview... 87 11.2 Create Snapshot... 87 11.3 Delete Snapshot... 89 11.4 List Snapshot... 91 11.5 Rename Snapshot... 94 12 Requirements of Access Control List Interface... 96 12.1 Overview... 96 12.2 Add ACL Rule... 97 12.3 Read ACL... 99 12.4 Modify ACL Rule... 102 12.5 Delete ACL... 105 12.6 Delete ACL Rule... 106 12.7 Delete Default ACL Rule... 108 Appendix A (normative) Distributed File Storage Management Interface... 111 Appendix B (normative) Supplementary Error Message... 1301 ScopeThis Part of GB/T 31916 provides an architecture of distributed file storage; stipulates general requirements and application interface of distributed file storage. This Part is applicable to the design, development, testing and application of distributed file storage.2 ComplianceThe interface defined in this Part can be divided into required and optional. Specifically speaking, file interface, folder interface and recycle bin interface are required, while others are optional. Parameters commanded by each interface might contain required parameters and optional parameters. Compliance contains the following circumstances. a) A system implements all the interfaces (including required interfaces and optional interfaces), which may be claimed as complete compliance with this Part. b) A system implements all the required interfaces, which may be claimed as compliance with this Part. c) A system does not implement all the required interfaces, which may be claimed as non-compliance with this Part.3 Normative ReferencesThe following documents are indispensable to the application of this document. In terms of references with a specified date, only versions with a specified date are applicable to this document. In terms of references without a specified date, the latest version (including all the modifications) is applicable to this document. GB/T 7408-2005 Data Elements and Interchange Formats - Information Interchange - Representation of Dates and Times; GB/T 31916.1-2015 Information Technology - Cloud Data Storage and Management - Part 1.General; RFC 822 Standard for the Format of ARPA Internet Text Messages; RFC 2616 Hypertext Transfer Protocol HTTP/1.1; RFC 7159 The JavaScript Object Notation (JSON) Data Interchange Format4 Terms, Definitions and Abbreviations4.1 Terms and Definitions What is defined in GB/T 31916.1-2015 and the following terms and definitions are applicable to this document. 4.1.1 Distributed file system Distributed file system is a file system, which is installed on the operating system as an application. Its storage resource is distributed on different computer nodes and connected through the computer network. 4.2 Abbreviations The following abbreviations are applicable to this document.5 Interface Positioning and System Structure of Distributed File Storage5.1 Interface Positioning of Distributed File Storage The positioning of distributed file storage interface in the application layer is shown in Figure 1.From the perspective of the operating system, the application-layer distributed file storage, which is an application of the traditional operating system, does not involve relevant operation of the kernel of the operating system. Thus, distributed file storage’s dependence and restriction of the operating system is avoided. 5.2 System Structure of Distributed File Storage System structure of distributed file storage includes. metadata server, data storage data, monitoring server and client-side. Figure 2 demonstrates a general architecture of distributed file storage.6 General Requirements of Application Interface6.1 Overview General requirements of distributed file storage application interface include 8 items of content, namely, interface protocol, identity security management, naming rules, description of status code message, supplementary error message, public request header, public response header and description of error message. 6.2 Naming Rules Naming rules of all the files, folds and paths are as follows. 6.3 Supplementary Error Message Error response of distributed file storage is relatively complicated. HTTP status code needs a description of supplementary error message. The format of error message shall comply with the requirements in 5.4 in GB/T 31916.1-2015.Please refer to Appendix B for a description of supplementary error message. 6.4 Public Request Header Information that public request header shall include is shown in Table 1 (see RFC 2616).7 Requirements of File Interface7.1 Overview File interface of distributed file storage is an interface that conducts operation of files in the system, including create file, delete file, upload file, download file, append file, copy file, rename file, view file status, modify file attributes, file search, file read, and file write. File interface is required. 7.2 Create File 7.2.1 Functional description The operating parameter of create file is. CreateFile, which is used to create files in distributed file storage. The created file name shall be unique in the folder. 7.2.2 Definition of request 7.2.3 Request URL In which, [Account] signifies account ID. [Path] signifies the location of created file. 7.2.4 Request message header Define it in accordance with public request header. 7.2.5 Request message parameters Please refer to Table 3 for request message parameters. 7.2.6 Request message body Null. 7.2.7 Response status code Please refer to Table 4 for response status code and its description. 7.2.8 Definition of response 7.2.9 Response message header Define it in accordance with public response header. 7.2.10 Response message body Please refer to Table 5 for a description of various parameters in response message body. 7.2.11 Examples of request and response message Examples of request message and response message are as follows. 7.3 Delete File 7.3.1 Functional description The operating parameter of delete file is. DeleteFile, which is used to delete file. When deleting a file, the system shall place it into the recycle bin. 7.3.2 Definition of request 7.3.3 Request URL In which, [Account] signifies account ID. [Path] signifies the location of file. 7.3.4 Request message header Define it in accordance with public request header. 7.3.5 Request message parameters Please refer to Table 6 for request message parameters. 7.3.6 Request message body Null. 7.3.7 Response status code Please refer to Table 7 for response status code and its description. 7.4 Upload File 7.4.1 Functional description The operating parameter of upload file is. UploadFile, which is used to upload local file to distributed file storage. 7.4.2 Definition of request 7.4.3 Request URL In which, [Account] signifies account ID. [Path] signifies the location of folder, where file is uploaded to. 7.4.4 Request message header Define it in accordance with public request header. 7.5 Download File 7.6 Append File 7.6.1 Functional description The operating parameter of append file is. AppendFile, which is used to append file in distributed file storage. 7.6.2 Definition of request 7.6.3 Request URL In which, [Account] signifies account ID. [Path] signifies the location of file. 7.6.4 Request message header Define it in accordance with public request header. 7.7 Copy File 7.7.1 Functional description The operating parameter of copy file is. CopyFile, which is used to copy file in distributed file storage. 7.7.2 Definition of request 7.7.3 Request URL In which, [Account] signifies account ID. [Path] signifies the location of file to be copied. 7.7.4 Request message header Define it in accordance with public request header. 7.8 Rename File 7.8.1 Functional description The operating parameter of rename file is. RenameFile, which is used to rename file in distributed file storage. 7.8.2 Definition of request 7.8.3 Request URL In which, [Account] signifies account ID. [Path] signifies the path of file to be renamed. 7.8.4 Request message header Define it in accordance with public request header. 7.8.5 Request message parameters Please refer to Table 21 for request message parameters.8 Requirements of Folder Interface8.1 Overview Folder interface of distributed file storage is an interface that conducts operation of folder in the system, including create folder, delete folder, upload folder, download folder, copy folder, rename folder, review folder status, modify folder attribute, folder search and list folder content. Folder interface is required. 8.2 Create Folder 8.2.1 Functional description The operating parameter of create folder is. Mkdir, which is used to create folders in distributed file storage. The created folder name shall be unique in the parent folder. 8.2.2 Definition of request 8.2.3 Request URL In which, [Account] signifies account ID. [Path] signifies the location of created folder. 8.2.4 Request message header Define it in accordance with public request header. 8.2.5 Request message parameters Please refer to Table 38 for request message parameters. 8.2.8 Definition of response 8.2.9 Response message header Define it in accordance with public response header. 8.2.10 Response message body Please refer to Table 40 for a description of various parameters in response message body. 8.6 Copy Folder 8.6.1 Functional description The operating parameter of copy folder is. CopyFolder, which is used to copy folder in distributed file storage. 8.6.2 Definition of request 8.6.3 Request URL In which, [Account] signifies account ID. [Path] signifies the location of folder to be copied. 8.6.4 Request message header Define it in accordance with public request header.9 Requirements of Recycle Bin Interface9.1 Overview Recycle bin interface of distributed file storage is an interface that conducts operation of recycle bin in the system. As a special folder in the system, recycle bin is used to store files and folders deleted by user. Recycle bin interface includes recover file, query trash, final delete file, clear trash and recover all. Recycle bin interface is required. 9.2 Recover Files in Recycle Bin 9.3 Query Files in Recycle Bin 9.3.1 Functional description The operating parameter of query files in recycle bin is. QueryTrash, which is used to query file or folder information in the recycle bin. 9.3.2 Definition of request 9.3.3 Request URL In which, [Account] signifies account ID. 9.3.4 Request message header Define it in accordance with public request header. 9.5 Clear Trash 9.5.1 Functional description The operating parameter of empty the recycle bin is. ClearTrash, which is used to empty files or folders in the recycle bin. 9.5.2 Definition of request 9.5.3 Request URL In which, [Account] signifies account ID. 9.5.4 Request message header Define it in accordance with public request header. 9.6 Recover All 9.6.1 Functional description The operating parameter of recover all is. RecoverAll, which is recover all the files or folders in the recycle bin. 9.6.2 Definition of request 9.6.3 Request URL In which, [Account] signifies account ID. 9.6.4 Request message header Define it in accordance with public request header. ......Source: Above contents are excerpted from the full-copy PDF -- translated/reviewed by: www.ChineseStandard.net / Wayne Zheng et al. Tips & Frequently Asked Questions:Question 1: How long will the true-PDF of English version of GB/T 31916.3-2018 be delivered?Answer: The full copy PDF of English version of GB/T 31916.3-2018 can be downloaded in 9 seconds, and it will also be emailed to you in 9 seconds (double mechanisms to ensure the delivery reliably), with PDF-invoice.Question 2: Can I share the purchased PDF of GB/T 31916.3-2018_English with my colleagues?Answer: Yes. The purchased PDF of GB/T 31916.3-2018_English will be deemed to be sold to your employer/organization who actually paid for it, including your colleagues and your employer's intranet.Question 3: Does the price include tax/VAT?Answer: Yes. Our tax invoice, downloaded/delivered in 9 seconds, includes all tax/VAT and complies with 100+ countries' tax regulations (tax exempted in 100+ countries) -- See Avoidance of Double Taxation Agreements (DTAs): List of DTAs signed between Singapore and 100+ countriesQuestion 4: Do you accept my currency other than USD?Answer: Yes. www.ChineseStandard.us -- GB/T 31916.3-2018 -- Click this link and select your country/currency to pay, the exact amount in your currency will be printed on the invoice. Full PDF will also be downloaded/emailed in 9 seconds.How to buy and download a true PDF of English version of GB/T 31916.3-2018?A step-by-step guide to download PDF of GB/T 31916.3-2018_EnglishStep 1: Visit website https://www.ChineseStandard.net (Pay in USD), or https://www.ChineseStandard.us (Pay in any currencies such as Euro, KRW, JPY, AUD).Step 2: Search keyword "GB/T 31916.3-2018". Step 3: Click "Add to Cart". If multiple PDFs are required, repeat steps 2 and 3 to add up to 12 PDFs to cart. Step 4: Select payment option (Via payment agents Stripe or PayPal). Step 5: Customize Tax Invoice -- Fill up your email etc. Step 6: Click "Checkout". Step 7: Make payment by credit card, PayPal, Google Pay etc. After the payment is completed and in 9 seconds, you will receive 2 emails attached with the purchased PDFs and PDF-invoice, respectively. Step 8: Optional -- Go to download PDF. Step 9: Optional -- Click Open/Download PDF to download PDFs and invoice. See screenshots for above steps: Steps 1~3 Steps 4~6 Step 7 Step 8 Step 9 |
