GA/T 1375.2-2017 in English
VALIDResource service bus—Part 2:Technical requirements
- Issued on:2017-09-07
- Implemented on:2017-09-07
- File Format:PDF
- Delivery:Via email within 1~3 business days
$243.00
| Standard No: | GA/T 1375.2-2017 |
| Document status: | VALID |
| Title in English: | Resource service bus—Part 2:Technical requirements |
| Title in Chinese: | 资源服务总线 第2部分：技术要求 |
| Language: | English |
| File Format: | Electronic (PDF) |
| Delivery: | Via email within 1~3 business days |
| Issued on: | 2017-09-07 |
| Implemented on: | 2017-09-07 |
| ICS Classification: | 35.240.01-Applications of information technology in general |
| Chinese Classification: | A90-Social and public safety in general |
| Professional Classification: | GA-Security |
| Related Keywords: | resource service bus
bus message bus performs service identification resolution format mandatory requirements bus technical requirements |
| Related Topics: | Technical Service Department
ga/t 380 resource service bus ga/t 1053 bus line GA/T 1399.1-2017 Server Resource Metrics Standard Resource Service Bus ga/t2017 |
Introduction
Overview of the Standard Technical Framework
This part, as the core technical requirements of the GA/T1375 series of standards, establishes the three major technical systems of the resource service bus:
| Technical Dimensions | Core Elements | Standardization Requirements |
|---|---|---|
| Basic Attributes | 11 types of basic attribute fields | Including key information such as identifiers, organization codes, IP addresses, etc. |
| Routing Mode | Bus routing/autonomous routing | Supports both synchronous and asynchronous communication mechanisms |
| Message Structure | 5 types of standard messages | XML format mandatory requirements |
Bus core attribute specifications
Standard Table 1 defines in detail the 11 basic attributes of the bus, of which the key attributes include:
- Bus_name (ZX_MC): needs to reflect functional characteristics
- Bus identifier (ZXBZBM): globally unique identifier
- Population address list: a composite structure containing IP addresses and port numbers
Application Case: Bus Deployment in a Provincial Public Security Bureau
In the construction of the XX Provincial Police Cloud Platform, the ZX_GAJGJGDM attribute is used to implement the hierarchical identification of the public security organs across the province. class=instrument>ZX_RKDZLB defines a multi-node load balancing address, supporting an average of 2 million+ service calls per day.
Routing Technology Implementation
6.1 Bus Routing Mode
The standard stipulates a strict permission verification process:
- The service requester sends a request message
- The bus performs service identification resolution and permission verification
- Responses are processed differently according to synchronous/asynchronous mode
6.2 Autonomous Routing Innovation
Introduction of a pre-authorization mechanism:
| Process Stages | Parties | Key Operations |
|---|---|---|
| Authorization Application | Service Requester→Bus | Submit an RA message containing personnel identity information |
| Authorization response | Bus→Service requester | Return AU message with timeliness |
| Service call | Service requester→Provider | Direct connection of SR message carrying authorization information |
In-depth analysis of message structure
The standard defines a complete message attribute system:
Bus message (SBmessage)
Contains 6 types of mandatory attributes:
- Message number (ZX_BWBH): uses 22-bit encoding rules
- Population address list: supports multi-level nested structure
- Message content: Supports GA/T1375.5-2017 and other standard encapsulation
Implementation recommendations
Key points for system construction
- Identification system design: It is recommended to use "administrative division code + timestamp + serial number" to form a 22-bit bus identifier
- Message security processing: Implement national secret SM4 encryption for ZXBWNR content
- Log audit optimization: The asynchronous request cache table should be equipped with an automatic cleanup mechanism
Standard evolution direction
In combination with the development of cloud computing, it is recommended for subsequent versions:
- Add RESTful API support
- Supplement microservice architecture adaptation requirements
- Improve containerized deployment specifications
Loading PDF document...
Error loading PDF. Please make sure the file is valid and try again.
We also recommend
-
GA/T 462-2004 in English
Public order administration information system framework of functions
2004-01-07 -
GA/T 608-2019 in English
Basic functional requirements for management system of information network for public security
2019-04-19 -
GA/T 1375.1-2017 in English
Resource service bus—Part 1:Architecture
2017-09-07
