GB/T 16263.1-2025 English PDFUS$779.00 ยท In stock
Delivery: <= 6 days. True-PDF full-copy in English will be manually translated and delivered via email. GB/T 16263.1-2025: Information technology - ASN.1 encoding rules - Part 1: Specification of Basic Encoding Rules(BER), Canonical Encoding Rules(CER) and Distinguished Encoding Rules(DER) Status: Valid GB/T 16263.1: Historical versions
Basic dataStandard ID: GB/T 16263.1-2025 (GB/T16263.1-2025)Description (Translated English): Information technology - ASN.1 encoding rules - Part 1: Specification of Basic Encoding Rules(BER), Canonical Encoding Rules(CER) and Distinguished Encoding Rules(DER) Sector / Industry: National Standard (Recommended) Classification of Chinese Standard: L79 Classification of International Standard: 35.100.60 Word Count Estimation: 38,330 Date of Issue: 2025-04-25 Date of Implementation: 2025-11-01 Older Standard (superseded by this standard): GB/T 16263.1-2006 Issuing agency(ies): State Administration for Market Regulation, China National Standardization Administration GB/T 16263.1-2025: Information technology - ASN.1 encoding rules - Part 1: Specification of Basic Encoding Rules (BER) , Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER)---This is a DRAFT version for illustration, not a final translation. Full copy of true-PDF in English version (including equations, symbols, images, flow-chart, tables, and figures etc.) will be manually/carefully translated upon your order. ICS 35.100.60 CCSL79 National Standard of the People's Republic of China Replaces GB/T 16263.1-2006 Information technology ASN.1 encoding rules Part 1.Basic Encoding Rules (BER), Regular Encoding Rules (CER) and Degenerate Encoding Rules (DER) Specification (ISO /IEC 8825-1.2021, IDT) Published on April 25, 2025, implemented on November 1, 2025 State Administration for Market Regulation The National Standardization Administration issued Table of contentsPreface III Introduction V 1 Scope 1 2 Normative references 1 3 Terms and Definitions 2 4 Abbreviations 3 5 Notation 3 6 Agreement 3 7 Compliance 3 8 Basic coding structure 4 8.1 General Rules for Coding 4 8.2 Encoding of Boolean Values 7 8.3 Encoding of integer values 7 8.4 Encoding of enumeration values 8 8.5 Encoding of real values 8 8.6 Encoding of bit string values 9 8.7 Encoding of octet string values 10 8.8 Encoding of Null Values 11 8.9 Encoding of sequence values 11 8.10 Encoding of a single sequence value 11 8.11 Encoding of collection values 11 8.12 Encoding of a single set value 11 8.13 Encoding of selected values 12 8.14 Encoding of prefixed type values 12 8.15 Open Type Encoding 12 8.16 Encoding of singleton values 13 8.17 Encoding of embedded pdv type values 13 8.18 Encoding of external type values 13 8.19 Encoding of object identifier values 14 8.20 Encoding of associated object identifier values 15 8.21 Encoding of OID Internationalized Resource Identifier Values 15 8.22 Encoding of Relative OID Internationalized Resource Identifier Values 16 8.23 Encoding of restricted string values 16 8.24 Encoding of unrestricted string values 18 8.25 Encoding of Useful Type Values 18 8.26 The TIME type and the encoding of useful time type values 18 9 Regular encoding rules 19 9.1 Length form 19 9.2 String Encoding Format 19 9.3 Collection Components 19 10 Atypical Coding Rules 20 10.1 Length format 20 10.2 String Encoding Format 20 10.3 Collection Components 20 11 Limitations of BER Use for CER and DER 20 11.1 Boolean values 20 11.2 Unused bit 20 11.3 Real Values 21 11.4 GeneralString value 21 11.5 Collection and Sequence Components with Default Values 21 11.6 Single Collection Components 21 11.7 GeneralizedTime 21 11.8 UTCTime(Universal Coordinated Time) 22 11.9 TIME Type and Useful Time Types 22 12 Use of BER, CER and DER in transfer syntax definition 22 Appendix A (Informative) Coding Example 24 Appendix B (Informative) Object Identifier Assignment 27 Appendix C (Informative) Examples of real value encoding 28 References 30ForewordThis document is in accordance with the provisions of GB/T 1.1-2020 "Guidelines for standardization work Part 1.Structure and drafting rules for standardization documents" Drafting. This document is Part 1 of GB/T 16263 Information Technology ASN.1 Coding Rules. GB/T 16263 has published the following part. --- Part 1.Specifications of Basic Encoding Rules (BER), Regular Encoding Rules (CER) and Untypical Encoding Rules (DER); --- Part 2.Specification of Restricted Encoding Rules (PER); --- Part 4.XML Encoding Rules (XER); --- Part 5.Mapping of W3C XML Schema Definitions to ASN.1. This document replaces GB/T 16263.1-2006 "Information Technology ASN.1 Encoding Rules Part 1.Basic Encoding Rules (BER), Compared with GB/T 16263.1-2006, the Standard for Regular Encoding Rules (CER) and Untypical Encoding Rules (DER) has made structural adjustments and In addition to logical changes, the main technical changes are as follows. --- "UTF8" was added to the abbreviations and "ULA" was deleted (see Chapter 4, Chapter 4 of the.2006 edition); --- Added relevant provisions on coding structure (see 8.1.1.5); --- Changed the description of real value 0 encoding (see 8.5.2, 8.5.3 and 8.5.9, 8.5.2 and 8.5.8 of the.2006 edition); --- Added relevant provisions for "encoding of prefixed type values" (see 8.14.1); --- Added "Encoding of OID international resource identifier values", "Encoding of relative OID international resource identifier values", "TIME class relevant provisions of "Encoding of Type and Useful Time Type Values" (see 8.21, 8.22 and 8.26); --- Added the relevant provisions for converting "TIME type and useful time type values" to the standard format (see 11.9); --- Added "OID International Resource Identifier" to identify and describe basic encoding rules (see Chapter 12); This document is equivalent to ISO /IEC 8825-1.2021 "Information technology ASN.1 encoding rules Part 1.Basic encoding rules (BER), Regular Encoding Rules (CER), and Degenerate Encoding Rules (DER) specifications. The following minimal editorial changes were made to this document. --- Change the normative references to specific clauses in the text to date references; --- Delete the "Note" in the normative reference documents and quote the latest version of ISO /IEC 10646.The reference content does not involve technical changes; --- In Chapter 4, the abbreviation "ULA" which is not cited in the whole text is deleted; ---Unify the abbreviations "UTF-8" and "UTF8" throughout the text to the abbreviation "UTF8" defined in Chapter 4. Please note that some of the contents of this document may involve patents. The issuing organization of this document does not assume the responsibility for identifying patents. This document was proposed and coordinated by the National Technical Committee for Information Technology Standardization (SAC/TC28). This document was drafted by. China Electronics Technology Standardization Institute, Shenzhen CESI Information Technology Co., Ltd., Chinese Academy of Sciences Research Institute, Lenovo (Beijing) Co., Ltd., Jiangsu CESI Technology Development Co., Ltd., Holsat Technology Group Co., Ltd., Beijing Telecom Regulatory Commission Planning and Design Institute Co., Ltd., Shanghai Tianchen Micro-Nano Technology Co., Ltd., China Mobile (Hangzhou) Information Technology Co., Ltd., Anhui Telecom Planning Design Co., Ltd., Institute of Automation, Chinese Academy of Sciences, Wuxi Internet of Things Industry Research Institute, Tianjin Special Equipment Supervision and Inspection Technology Research Institute, Chongqing Quality and Standardization Research Institute, and Shilian Power Information Technology Co., Ltd. The main drafters of this document are. Su Jingru, Zhang Xueqian, Zhang Chi, Liu Min, Ma Yilong, Wang Yuwei, Zhang Feng, Li Jiajing, Zhou Lixiong, Jia Jingrun, Liu Qiong, He Saike, Luan Haijing, Wang Yawei, Wu Mingjuan, Wang Xuan, Zhang Cheng, Liu Yumei, Xiang Lei, Dong Xuan, Zhao Yizheng, Zhang Peijie, Chen Shuyi, Li Jufeng, Sun Fanli and Liu Bilong. The previous versions of this document and the documents it replaces are as follows. ---First published in.1996 as GB/T 16263-1996; ---First revised in.2006 to GB/T 16263.1-2006; ---This is the second revision.IntroductionGB/T 16262.1-2025, GB/T 16262.2-2025, GB/T 16262.3-2025 and GB/T 16262.4-2025 (Abstract Syntax Notation One or ASN.1) together specifies the notation for abstract syntax. This document defines the encoding of type values defined using ASN.1 notation. The application of these encoding rules produces the transfer syntax for these values, and also applies to decoding. This document defines three sets of encoding rules, namely basic encoding rules, regular encoding rules and atypical encoding rules. In the code, the basic encoding rules give various choices for how the encoder transmitter encodes the data value, while the regular encoding rules and the atypical encoding rules Then only one encoding is selected from those allowed by the basic encoding rules, excluding all options for the sender. The set of restrictions that atypical encoding rules impose on basic encoding rules is different from each other. Appendix A gives examples of applying basic coding rules. Appendix B summarizes the assignment of Object Identifier and OID International Resource Identifier values generated in this document. Appendix C gives examples of applying the basic encoding rules to encoded real numbers. GB/T 16263 is planned to consist of 8 parts. --- Part 1.Basic Encoding Rules (BER), Regular Encoding Rules (CER) and Untypical Encoding Rules (DER) specifications. To specify a set of basic encoding rules. --- Part 2.Specification of the compressed encoding rules (PER). The purpose is to specify a set of compressed encoding rules. --- Part 3.Encoding Control Notation (ECN) Specification. The purpose is to standardize the ASN.1 Encoding Control Notation. --- Part 4.XML Encoding Rules (XER). The purpose is to specify the Basic XML Encoding Rules (BASIC-XER), regular XML Encoding Rules Set (CXER) and Extended XML Encoding Rules Set (EXTENDED-XER). --- Part 5.Mapping of W3C XML Schema Definitions to ASN.1.The purpose is to define the mapping from any XSD schema to ASN.1 There are two versions of the mapping mode. --- Part 6.Registration and application of PER coded instructions. The purpose is to specify the PER coded instruction format, mechanism, registration agency Methods of operation, PER and ASN.1 related. --- Part 7.Octet Encoding Rules (OER) Specification. The purpose is to provide constraints for the Basic Octet Encoding Rules and Generates a unique encoding for any given ASN.1 value. --- Part 8.JavaScript Object Notation Encoding Rules (JER) specification. The purpose is to specify a set of JavaScript objects Representation encoding rules for applications that interoperate with JSON. Information technology ASN.1 encoding rules Part 1.Basic Encoding Rules (BER), Regular Encoding Rules (CER) and Degenerate Encoding Rules (DER) Specification1 ScopeThis document specifies a set of basic encoding rules that are also applicable to decoding this transfer syntax and are used to identify the transmitted This document also specifies regular encoding rules and a set of atypical encoding rules that restrict the encoding of values to the basic encoding rules. An alternative encoding is provided.2 Normative referencesThe contents of the following documents constitute essential clauses of this document through normative references in this document. For referenced documents without a date, only the version corresponding to that date applies to this document; for referenced documents without a date, the latest version (including all amendments) applies to This document. GB/T 16262.1-2025 Information technology Abstract syntax notation 1 (ASN.1) Part 1.Basic notation specification (ISO / IEC 8824-1.2021, IDT) GB/T 16262.2-2025 Information technology Abstract syntax notation 1 (ASN.1) Part 2.Information object specification (ISO /IEC 8824-2.2021,IDT) Note. GB/T 2311-2000 Information technology character code structure and extension technology (ISO /IEC 2022.1994, IDT) Note. GB/T 12054-1989 Registration procedure for data processing escape sequences (ISO 2375.1985, NEQ) Note. SJ/Z9047-1987 Information processing - Method for representing numerical values in character string form for information exchange (ISO 6093.1985, IDT) ISO /IEC 7498-1 Information technology Open Systems Interconnection Basic reference model Part 1.Basic model Note. GB/T 9387.1-1998 Information technology Open Systems Interconnection Basic Reference Model Part 1.Basic Model (ISO /IEC 7498-1. 1994,IDT) Note. GB/T 13000-2025 Information technology Universal coded character set (UCS) (ISO /IEC 10646.2020, MOD) ......Tips & Frequently Asked Questions:Question 1: How long will the true-PDF of GB/T 16263.1-2025_English be delivered?Answer: Upon your order, we will start to translate GB/T 16263.1-2025_English as soon as possible, and keep you informed of the progress. The lead time is typically 4 ~ 6 working days. The lengthier the document the longer the lead time.Question 2: Can I share the purchased PDF of GB/T 16263.1-2025_English with my colleagues?Answer: Yes. The purchased PDF of GB/T 16263.1-2025_English will be deemed to be sold to your employer/organization who actually pays 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. If you need your currency to be printed on the invoice, please write an email to Sales@ChineseStandard.net. In 2 working-hours, we will create a special link for you to pay in any currencies. Otherwise, follow the normal steps: Add to Cart -- Checkout -- Select your currency to pay.Question 5: Should I purchase the latest version GB/T 16263.1-2025?Answer: Yes. Unless special scenarios such as technical constraints or academic study, you should always prioritize to purchase the latest version GB/T 16263.1-2025 even if the enforcement date is in future. Complying with the latest version means that, by default, it also complies with all the earlier versions, technically. |
