GB/T 42443-2023 PDF EnglishUS$260.00 · In stock · Download in 9 seconds
GB/T 42443-2023: Information technology - Automatic identification and data capture techniques - Syntax for high-capacity ADC media 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 42443-2023: Information technology - Automatic identification and data capture techniques - Syntax for high-capacity ADC media---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/GBT42443-2023 GB NATIONAL STANDARD OF THE PEOPLE’S REPUBLIC OF CHINA ICS 35.040 CCS L 71 Information Technology – Automatic Identification and Data Capture Techniques – Syntax for High-Capacity ADC Media (ISO/IEC 15434:2019, MOD) ISSUED ON: MARCH 17, 2023 IMPLEMENTED ON: OCTOBER 01, 2023 Issued by: State Administration for Market Regulation; Standardization Administration of the People’s Republic of China. Table of ContentsForeword ... 3 Introduction ... 5 1 Scope ... 6 2 Normative References ... 6 3 Terms and Definitions ... 7 4 Conventions of Symbols in Document ... 7 5 Message Format ... 7 6 Human-Readable Representations ... 21 Appendix A (Normative) GB/T1988-1998 Subset (Table of Hexadecimal and Decimal Values) ... 23 Bibliography ... 25 Information Technology – Automatic Identification and Data Capture Techniques – Syntax for High-Capacity ADC Media1 ScopeThis Document specifies when using the high-capacity ADC media between trading partners (particularly between suppliers and recipients) and where applicable, when supporting carrier applications (such as bills of lading, carrier sorting and tracking), the transmission structure, syntax and encoding of message and data formats. Data encoded according to this Document includes: --- data available for shipping, receiving and counting transport units; --- data in paper or electronic form relating to unit loads or transport packages that may be included in supporting documentation; --- data that can be used for sorting and tracking transport units. This Document gives GB/T1988-1998 characters for automatic data collection. This Document does not supersede or replace any applicable safety or other marking or labeling requirements. Unless there are any other mandatory labeling requirements, this Document applies.2 Normative ReferencesThe provisions in following documents become the essential provisions of this Document through reference in this Document. For the dated documents, only the versions with the dates indicated are applicable to this Document; for the undated documents, only the latest version (including all the amendments) is applicable to this Document. GB/T 1988-1998 Information technology - 7-bit Coded character set for information interchange (eqv ISO/IEC 646:1991) GB/T 12905-2019 Bar code terminology GB/T 37056-2018 Article numbering terminology3 Terms and DefinitionsFor the purposes of this Document, the terms and definitions given in GB/T 12905-2019 and GB/T 37056-2018 apply.4 Conventions of Symbols in DocumentThis Document is formatted as follows in the message examples. Bold and uppercase letters: The entered text should be exactly the same as the displayed text (in this Document, FS, GS, US, RS, EoT are used to represent special non-printable characters. The special characters in GB/T 1988-1998 used in this Document shall comply with the provisions of Appendix A). Italics and lowercase letters: variable parameters. User shall provide appropriate value. In some cases, the default value should be used.5 Message Format5.1 General The message format defines the method of transferring data from the high-capacity ADC media reading device to the user application software. In order to include multiple data formats in the data stream, a two-layer encapsulation structure is adopted. The outermost layer of the message is the message encapsulation that defines the header and tailer of the message. There are one or more format encapsulations containing data in the message encapsulation (see Figure 1). Multiple formats in a single message can only be used for bilateral agreements between trading partners. The message encapsulation shall include: --- 1 message header; --- 1 or more format encapsulations, and; --- 1 message tailer (when needed). Each format encapsulation within the message encapsulation shall include: --- 1 format header; --- formatted data stored according to the rules defined by the format, and; --- Format, containing one or more fields; --- Field, containing 1 or more data elements; --- Data element (field), may contain 1 or more child elements (subfield). 5.2.2 Message header 5.2.2.1 General The message header consists of 2 parts: --- Conformance identifier of 3 characters; --- Format tailer character. The complete message header shall be: 5.2.2.2 Conformance identifiers The conformance identifier shall be the first 3 characters in the message header. Conformance identifiers are “[” “)” “ >”. Appendix A gives the table of decimal and hexadecimal values of GB/T1988-1998 characters used in this Document. 5.2.2.3 Format trailer characters The format tailer character shall be the 4th character in the message header. The format tailer character is the non-printable character “RS” (as per Appendix A). The format trailer character is used throughout the message to mark the end of the data format encapsulation (see 5.3.16). 5.2.3 Message trailer The message tailer identifies the end of the message in the data stream, which shall be the end of the transaction character. The message tailer is “EoT” (according to Appendix A). Except for the possible occurrence of “EoT” characters in format “09” (binary data), message tailer characters shall not be used elsewhere in the message. Message trailers shall not be used together with formats “02” [to complete an electronic data interchange (EDI) message/transaction] and “08” (structured data using CII syntax rules). 5.3 Format encapsulation 5.3.1 General Format messages give the beginning and end of data in a given format and provide the following 5.3.15 Format header “13” ~ “99” (reserved format) The format headers “13” ~ “99” are reserved for future use. 5.3.16 Format trailer The format tailer identifies the end of the format message. The format tailer shall include the format tailer character and the non-printable character “RS” (as per Appendix A). Format trailer characters shall not be used in non-binary data elsewhere in the message. The format trailer shall not be used together with Format “02” (finish EDI message/transaction) and Format “08” (CII - complete message). 5.4 Data format 5.4.1 General Within a given format encapsulation, data shall be formatted using one and only one of the following methods: --- transportation; --- finish EDI message/transaction (ASC X12, UN/EDIFACT or CII standard); --- structured text (ASC X12 or UN/EDIFACT subset); --- structured data using the GS1 application identifier rules; --- structured data using the ASC MH10 data identifier rules; --- text with free format; --- CII message records without message group header and tailer; --- binary data; --- structured data using the text element identifier rules. If more than one format is included in the message, Format “01” (if used) shall be the first format in the message. 5.4.2 Format “00” (reserved) The format header “00” is reserved for future use. 5.4.3 Format “01” carrier sorting and tracking (transportation) 5.4.3.1 General Format “01” consists of two parts: the first part is mandatory data, which is common to all carrier sorting and tracking applications; the second part is optional data, which is suitable for specific applications between trading partners. The organization controlling the data structures in the format is identified by a version identifier in the format header: --- Version “02”: Formatted according to the rules of ASC MH10/SC 8 in ANS MH10.8.2 (using the measurement identifiers in kilograms and pounds); --- Version “06”: Formatted according to the rules of the International Air Transport Association (IATA); --- Version “56”: Formatted according to the rules of the International Federation of Freight Forwarders Associations (FIATA); --- Version “96”: Formatted according to the rules of ASC MH10/SC 8 (measurement identifiers using pounds only). 5.4.3.2 Version “02” of Format “01” 5.4.3.2.1 Mandatory data Mandatory data is required for version “02” of format “01”. Subsequent data elements shall be in the following order, immediately after the format header. Each data element is defined as fixed length or variable length. The field length is variable; and the minimum field length and maximum field length are as follows. All fields are separated by the data element separator (“GS”) defined in the format header. Recipient postal code: (an 00…11) Recipient country code: (n 03) Class of service (specified by the carrier): (an 01…03) Delivery number (controlled by the carrier): (an 01…20) Standard Carrier Number Code (SCAC) of the original carrier: (an 02…04) (SCAC of the carrier who intends to transport the package) The recommended class of service is a 3-digit number data. 5.4.3.2.2 Optional data There are 9 optional data elements. Optional data elements (if used) shall immediately follow mandatory data in the order specified below. Each data element is defined as fixed length or variable length. If the field length is variable, the minimum and maximum field lengths are as Standard Carrier Numeric Code (SCAC) of original carrier: (an 02…04) The service category shall be 3-digit data. 5.4.3.3.2 Optional data There are 9 optional data elements. If optional data elements are used, optional data shall follow mandatory data in the following order. Each data element is defined as fixed length or variable length. The field length is variable, and the minimum field length and maximum field length (min...max) are as follows. All optional fields, including blank fields, shall be separated using a data element separator (“GS”) (as per Appendix A). Data that has been identified as optional data may not be required in all applications. The optional data fields and associated lengths are shown below. Carrier assigned shipper ID (pickup location): (an 01…10) Julian date for picking: (n 13) Shipment ID number: (an 01...30) n/x (the nth container out of a total of x containers): (n 01…04/n 01…04) Quality (if used, decimal is a character): (r 01...10) Cross match (value Y or N): (a 01) Delivery to street address: (an 01...35) Delivery to city: (an 01...35) Delivery to municipalities/provinces: (an 02) 5.4.4 Format “02” (finish EDI message/transaction) Format “02” is used to encode the entire EDI transaction/message for the purpose of passing it directly to the EDI converter. Format “02” shall be ASC X12, UN/EDIFACT or CII standard. Format “02” includes encapsulation structures defined by applicable standards, such as ISA, GS, ST, SE, GE and IEA fields (applicable to ASC X12) or UNA, UNB, UNH, UNT and UNZ fields (applicable to UN/EDIFACT), or record of message group header, message and message group tailer (applicable to CII standard). The message tailer character “EoT” and the format tailer character “RS” shall not be used with the Format “02”. There shall be no more than one Format “02” within a data message. Format “02” shall not be combined with any other data format within the data message. 5.4.5 Format “03” (structured data using ASC X12 elements) The format “03” is used to represent structured data according to ASC X12 rules in ANS X12, such as place of receipt and place of delivery, etc. This format allows encoding of data represented by a single ASC X12 field without encapsulation, i.e., ISA/IEA, GS/GE, and ST/SE; or a single ASC X12 transaction set with encapsulation, i.e., ST/SE. This data cannot be passed directly to the EDI converter. For format “03”, the ASC X12 format version is included in the format header. The character “FS” shall be used as the ASC X12 field terminator. The character “GS” shall be used as ASC X12 data element separators. The character “US” shall be used as the ASC X12 child element separator. EDI fields encoded with binary data, such as BIN, shall not be used in format “03”. Binary data shall only be encoded in format “09” (see 5.3.12). 5.4.6 Format “04” (structured data using the UN/EDIFACT element) Format “04” is used to represent structured data according to UN/EDIFACT rules, such as place of receipt and place of delivery, etc. Format “04” allows encoding of data represented by separate UN/EDIFACT fields without encapsulation, i.e., UNB/UNA/UNZ and UNH/UNT; or a single UN/EDIFACT message with encapsulation, i.e., UNH /UNT. This data cannot be passed directly to the EDI converter. For format type “04”, the format header contains the UN/EDIFACT format version. The character “FS” shall be used as UN/EDIFACT field terminators. The character “GS” shall be used as UN/EDIFACT data element separators. The character “US” shall be used as UN/EDIFACT child element separator. 5.4.7 Format “05” (using GS1 application identifier) Each data element in format “05” shall be preceded by the corresponding GS1 Application Identifier (AI) code specified in the GS1 General Specification, followed by the data element separator “GS”; unless the data element is the last field in the data format, i.e., the last format “05” data element followed by the format tailer character “RS”. 5.4.8 Format “06” (using ASC MH10 data identifier) Each data element in format “06” shall be preceded by the corresponding ASC MH10 data identifier (DI) code as specified in ANS MH10.8.2, followed by the data element separator “GS”; unless the data element is the last filed in the data format, i.e., the last format “06” data element is followed by the format tailer character “RS”. 5.4.9 Format “07” (text format with free format) Format “07” allows text information with free format. This data format has no variable header (CSDD), followed by the data element separator “GS”; unless the data element is the last field in the data format, i.e., the last data element of the format “12” followed by the format tailer character “RS”. (The hexadecimal and decimal values of terminators and separators shall be as specified in Appendix A) Format “12” shall be used with agreement between trading partners. 5.4.14 Format “13” (restrictions) To avoid conflict with ISO/IEC 15961-2 format “13”, this format shall not be used. 5.4.15 Format “14” ~ “99” (reserved) The format headers “14” ~ “99” are reserved for future use.6 Human-Readable RepresentationsNon-printable control characters shall comply with the provisions of Appendix A. The non- printable characters come from the character set in GB/T1988-1998, as shown below. --- RS, the letter pair of two letters, the superscript R and the subscript S, together represent a non-printable format tailer control character, called the record separator. The encoding of RS is a single byte with decimal value 030 (equivalent to hexadecimal value 1E). --- GS, the letter pair of two letters, superscript G and subscript S, together represent a non- printable data element separator control character, called group separator. The encoding of GS is a single byte with decimal value 029 (equivalent to hexadecimal value 1D). --- FS, the letter pair of two letters, the superscript F and the subscript S, together represent a non- printable element termination control character, called the field separator. The encoding of FS is a single byte with decimal value 028 (equivalent to hexadecimal value 1C). --- US, the letter pair of two letters, the superscript U and the subscript S, together represent a non-printable child element separator control character. The encoding for US is a single byte with decimal value 031 (equivalent to hexadecimal value 1F). --- EoT, a three-letter alphabet string, superscript E, small O (smaller font size of capital letter O, equivalent to the size of superscript and subscript characters) and subscript T, indicating a non- printable terminator control character, which is called the end of transmission. The encoding of the EoT is a single byte with the decimal value 04 (equivalent to the hexadecimal value 04). NOTE: If the literal letters RS, GS, FS, US, EoT, or other incompatible characters are encoded in the data string, the resulting data shall be erroneous and not in compliance with the provisions of this Document; in application programs built as per this Document, such a data string is incomprehensible, that is, it cannot be decoded, parsed and interpreted correctly. In the following message example from this Document, the non-printable control characters are ......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 42443-2023 be delivered?Answer: The full copy PDF of English version of GB/T 42443-2023 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 42443-2023_English with my colleagues?Answer: Yes. The purchased PDF of GB/T 42443-2023_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 42443-2023 -- 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 42443-2023?A step-by-step guide to download PDF of GB/T 42443-2023_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 42443-2023". 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 |
