GB/T 36107-2018 Data exchange interface for unified social credit code of legal persons and other organizations GB/T36107-2018 |tt||Standard compression package decompression password: www.bzxz.net
This standard specifies the terms and definitions, abbreviations, data exchange modes, data exchange processes, and data exchange interface specifications for the data exchange interface for the return of unified social credit code information of legal persons and other organizations. This standard applies to the unified social credit code data exchange between the national, provincial (district, municipal) and military registration management departments and the organization code management departments.

ICS35.020
National Standard of the People's Republic of China
GB/T36107—2018
Data exchange interface of the unified social credit identifierfor legal entities and other organizations
Data exchange interface of the unified social credit identifierfor legal entities and other organizationsIssued on March 15, 2018
General Administration of Quality Supervision, Inspection and Quarantine of the People's Republic of ChinaStandardization Administration of the People's Republic of China
Implementation on July 1, 2018
GB/T36107—2018
Normative references
Terms and definitions
Abbreviations
Data exchange mode
Data exchange process
Data exchange interface specification
This standard was drafted in accordance with the rules given in GB/T1.1-2009. This standard was proposed and managed by the National Technical Committee for Standardization of Social Credit (SAC/TC470). GB/T36107—2018
The main drafting units of this standard are: National Organization Code Management Center, Office of the Central Organization Commission, National Development and Reform Commission, Ministry of Civil Affairs, Ministry of Human Resources and Social Security, State Administration of Taxation, State Administration for Industry and Commerce, National Bureau of Statistics, China National Institute of Standardization, Shandong Provincial Institute of Standardization, Harbin Institute of Standardization, Liaoning Provincial Institute of Standardization, Yunnan Provincial Institute of Standardization, Chinese Academy of Surveying and Mapping, and Information Center of Shandong Provincial Administration for Industry and Commerce. Drafters of this standard: Sun Zhen, Yuan Hui, Ke Zhiyong, Zhao Jie, Qian Xiaodong, Sun Tai, Liu Jiping, Zhou Li, He Yiming, Yan Chang, Yu Hui, Yin Yan, Zhu Huiyan, Ma Yufei, Feng Xiaojing, Jin Jiang, Gong Zheng, Yue Shiyu, Zhou Gang, Wang Aowei, Zhang Dongqing, Zhang Ye, Hou Bo, Liu Jia, Deng Xiangwu, Wang Bo, Yang Yang, Xu Xiaodong, Li Yifeng, Zhu Xuncheng, Huan Deming, Li Fenglong, Song Shunxiang, Meng Ju, Song ShaohuiiiiKAoNiKAca
1 Scope
Unified social credit code data exchange interface for legal persons and other organizations|| tt||GB/T36107—2018
This standard specifies the terms and definitions, abbreviations, data exchange modes, data exchange processes, and data exchange interface specifications for the data exchange interface of the unified social credit code information of legal persons and other organizations. This standard applies to the unified social credit code data exchange between the national, provincial (district, municipal) and military registration management departments and the organization code management departments.
2 Normative reference documents
The following documents are essential for the application of this document. For all referenced documents with dates, only the versions with dates apply to this document. For any undated referenced document, its latest version (including all amendments) shall apply to this document GB/T17969.8 Information Technology Open Systems Interconnection OSI Registration Authority Operating Procedures Part 8: Generation and Registration of Universally Unique Identifiers (UUIDs) and Their Use as ASN.1 Object Identifier Components GB32100 Coding Rules for Unified Social Credit Codes for Legal Persons and Other Organizations GB/T36104
Basic Data Elements of Unified Social Credit Codes for Legal Persons and Other Organizations GB/T36105 Coding Operation Specifications for Unified Social Credit Codes for Legal Persons and Other Organizations 3 Terms and Definitions
The terms and definitions defined in GB32100 and GB/T36105 and the following terms and definitions shall apply to this document. 3.1
Data exchange
data exchange
The process of providing data between various entities. 4 Abbreviations
The following abbreviations shall apply to this document.
Extensible Markup Language (ExtensibleMarkupLanguage) 5 Data Exchange Mode
The data exchange mode can adopt the national credit information sharing platform, provincial credit information sharing platform, government information platform, data interface between government departments, etc., establish a working mechanism based on provinces (departments), clarify the shared content, strictly follow the operating procedures, and establish a cross-level, cross-regional, and cross-departmental information exchange and data sharing mechanism. 6 Data Exchange Process
6.1 Data Exchange Flowchart
The data exchange process includes the sending of business data by the registration management department, the receiving of business data by the organization code management department, business data verification and processing result feedback. For details of the data exchange process, please refer to Figure 1. Note: For details of S001, S002 and S003 in Figure 1, please refer to 7.2. 1 Registration Management Department
Sending Message
6 Business Processing
5 Registration management department
Receive message
6.2 Business data transmission
Registration information message S001
Receipt message S002
Processing result message S003
Figure 1 Data exchange flow chart
2 Organization code management department
Receive message
3 Verification
Verification passed
4 Storage
After the registration management department collects and organizes the data, it organizes the data into a message and sends it to the organization code management department. 6.3
Business data reception
The organization code management department receives the business data sent by the registration management department and gives relevant information feedback. After receiving the data message, it is verified and analyzed according to the established message specifications. 6.4 Business data verification and feedback
After receiving the data from the registration management department, the organization code management department shall conduct verification and feedback. 7 Data exchange interface specification
7.1 Data exchange interface format
7.1.1 Message technical description
Data exchange adopts the message format defined by XML specification for message transmission, and the message encoding format shall adopt UTF-8. 7.1.2 Message structure
《? xmlversion=\1.o\encoding=\UTF-8\?>(Object)
(EnvelopeInfo)
（Version>Version number《/Version）(Messageld>Message numberUser original message name《/FileName>《MessageType>Message business typeReceiver numberNumber of business message records
(Packagelnfo)
Business message part, marking the transmitted business information《/P ackageInfo>
(/Object)
Message data item element description
Message data item element description is shown in Table 1.
Table 1 Message data item element description table
Data item element
Node name
Chinese description
Data type
Data length
Node description
Envelope part message format
xml node name, case sensitive
Chinese description corresponding to xml node
xml section Data type of point
Data length of xml node
Whether the value of xml node must exist
Data related description of xml node
The message format of the envelope part (EnvelopeInfo) is shown in Table 2. String: character type
GB/T36107—2018
Number: numeric type
Boolean: Boolean type
Table 2 Envelope part (Envelopelnfo) message format table sequence number
Node name|| tt||Version
Messageld
FileName
Chinese Description
Version Number
Message Number
User Original Message Name
Data Type
Character Type
Character Type
Data Length
Node Description
Value in this standard is 1.0.00
The unique identifier of this message, the value is
uuid, in line with GB/T17969.8
The stub address of this message on the sender's server. The address format is not limited
(relative or absolute address). It is recommended to retain the message stub for 15 days to facilitate traceability and anti-repudiation, etc.
iiKANiKAca
GB/T36107—2018
Node name
MessageType
Senderld
Receiverld
SendTime
Extends
Message service type
Chinese description
Message service type
Sender number
Receiver number
Sending time
Number of business message records
Extended information
Message service type is shown in Table 3.
Message type
Business type
Registration information message format
Receipt receipt message format
Processing result message format
Registration information message format (S001)
Table 2 (continued)
Data type
Character type
Character type
Character type
Numeric type
Character type
Data lengthbzxZ.net
Message business type table
Table 3 main
Node description
See 7.1.5 for values
Sender's unified social credit code
Receiver's unified social credit code
Format is yyyy-MM-dd hh:mm:
ss where hh is in 24-hour format
The maximum number of records does not exceed 1000
This standard is used when it cannot be met during transmission. The sender and the receiver can negotiate on their own. The format adopts
xml format and utf-8 encoding
The registration management department is the sender and the organization code management department is the receiver. The organization code management department is the sender and the registration management department is the receiver. The organization code management department is the sender and the registration management department is the receiver. The node name of the registration information message service message part meets the requirements of GB/T36104. The node name adopts the field name or internal identifier.
The registration information node (dminfo) is defined as follows: (PackageInfo)
Tip: This standard content only shows part of the intercepted content of the complete standard. If you need the complete standard, please go to the top to download the complete standard document for free.