GA/T 543.13-2017 in English
VALIDThe data elements for public security(13)
- Issued on:2017-02-10
- Implemented on:2017-02-10
- File Format:PDF
- Delivery:Via email within 1~3 business days
$214.00
本分册规定了16个公安数据元。
本分册适用于公安信息化建设、应用和管理。
Introduction
Standard Background and Evolution
As the 13th part of the GA/T 543 series of standards, this standard was released in February 2017 and developed under the leadership of the Science, Technology and Informatization Bureau of the Ministry of Public Security. This standard continues the technical framework of the public security informatization standards system, focusing on data standardization in the resource service bus (RSB) scenario. Together with GA/T 541 (Management Procedures) and GA/T 542 (Authorization Rules), it constitutes a complete data element standard system.
Core Data Element Analysis
| Data Element Name | Identifier | Data Type | Key Value Domain |
|---|---|---|---|
| Bus Service Interface Type Code | ZXFWJKLXDM | Character Type(c2) | 01-WebService,02-FMQ,03-MQ,04-SOCKET |
| Bus Service Identification Code | ZXFWBZBM | Character Type(c21) | S+12-digit Organization Code+8-digit Serial Number |
| Routing mode code | LYFSDM | Character type (c2) | 00-Bus selection, 01-Bus routing, 02-Autonomous routing |
Key Technical Features
Coding Rule System
The standard establishes strict coding specifications:
1. Service Identification Code adopts a 21-digit fixed-length structure of "S+Organization Code+Serial Number"
2. The organization code shall preferably use the public security agency code specified in GA/T 380
3. Non-industry organizations shall use the 9-digit code of the Quality Supervision Bureau padded with zeros to 12 digits
Enumeration Value Standardization
Through reference to the GA/T 2000 series of standards:
- Bus Service Status Code (GA/T 2000.224)
- Message Type Code (GA/T 2000.223)
- Industry Category Code (GA/T 2000.225)
Implementation Recommendations
- System Interconnection Specifications: The bus service interface must support the following four protocols: WebService/FMQ/MQ/SOCKET
- Coding Management: Establish a central registration system for service identification codes to ensure code uniqueness
- Version Control: The version number uses the n5,2 format (e.g., 1.00). Changes to the major version number require re-registration
- Message Tracking: Combine the DE01126 message numbering rules to achieve full-link tracking
Application Scenario Examples
Cross-system service call scenario:
When the municipal police system calls the provincial population database service:
1. The service requester uses the DE00929 standard code (A+institution code+serial number)
2. The service provider generates an identification code according to DE01130
3. The bus message carries the DE01128 category code and DE01126 unique number

Loading PDF document...
Error loading PDF. Please make sure the file is valid and try again.
We also recommend
-

GA/T 2000.148-2024 in English
Public Security Information Code Part 148: Classification and code of online inspection issues
2024-03-28