GB/T 39044-2020 in English
VALIDAccess specification of government service platform
- Issued on:2020-07-21
- Implemented on:2020-10-01
- File Format:PDF
- Delivery:Via email within 1~3 business days
$156.00
| Standard No: | GB/T 39044-2020 |
| Document status: | VALID |
| Title in English: | Access specification of government service platform |
| Title in Chinese: | 政务服务平台接入规范 |
| Language: | English |
| File Format: | Electronic (PDF) |
| Delivery: | Via email within 1~3 business days |
| Issued on: | 2020-07-21 |
| Implemented on: | 2020-10-01 |
| ICS Classification: | 35.240-Applications of information technology |
| Professional Classification: | GB-National Standard |
| Related Keywords: | key access requirements access module technical requirements
government service platform introduction analysis government service items third-party service access take logistics access specification |
| Related Topics: | Service Platform
Service Platform national platform Government service service platform for Government platform Testbed Services GBT39044 GB/T 39044-2020 Operation and maintenance access Government services business Satellite positioning platform service provider Government services |
《GB/T 39044-2020政务服务平台接入规范》由TC594（全国行政管理和服务标准化技术委员会）归口，TC594SC1（全国行政管理和服务标准化技术委员会行政管理分会）执行，主管部门为国务院办公厅。
Introduction
Analysis of the core framework of the standard
GB/T39044-2020 has built an access architecture that includes 8 modules, including government service items and unified identity authentication, and clarified the two types of access relationships between platforms (vertical) and systems (horizontal). The standard highlights the three principles of "unified authentication, license sharing, and security and controllability", and requires the interconnection of systems through standardized interfaces such as HTTP/JSON.
Comparison of key access requirements
| Access module | Technical requirements | Management requirements | Security requirements |
|---|---|---|---|
| Electronic certificate sharing | Directory push + exception correction mechanism | Requires account registration to obtain a license | Data tamper-proof transmission |
| Unified identity authentication | Support implicit login token | Real-name verification information synchronization | Uniform logout session destruction |
| Security assurance system | Level 3 or above of the 2.0 security protection system | Cascade monitoring and auditing | Crypto application security assessment |
Technology evolution and implementation suggestions
1. Background of standard formulation
In response to the requirements of the State Council Letter No. 108 (2016), the problem of "information islands" existing in the early government affairs system was solved. Through standardized interface specifications, data intercommunication between national, provincial and municipal platforms was achieved. For example, the Shandong Provincial Government Cloud has completed the connection of 87 provincial departments' systems based on this standard.
2. Typical implementation cases
Jiangsu Province adopted the SDK access package method to connect the medical insurance query services of 13 cities to the provincial platform, with an average daily call volume of more than 500,000 times. Special attention should be paid during implementation: - The electronic certificate catalogue must be coded according to the "ZWFW C0124-2018" standard. - Operation and maintenance monitoring data must include 15 basic indicators such as CPU/memory
3. Key points for third-party service access
Take logistics docking as an example:
1) A real-time callback interface for delivery order status must be provided
2) Encrypted transmission must be performed using the national secret SM4 algorithm
3) Fault recovery time is promised to be ≤15 minutes
Solutions to common problems
Q: How does the municipal platform connect to the provincial electronic seal system?
A: Three steps need to be completed:
1) Deploy provincial electronic seal client plug-in on the municipal platform
2) Apply for institutional digital certificate and register seal
3) Realize seal approval linkage through WebService interface
Q: Precautions for historical system transformation
A: It is recommended to adopt the "gateway proxy + data cleaning" mode:
1) Convert non-standard protocols through API gateway
2) Establish a data quality verification rule library
3) Keep 3 months of data traceability period
Loading PDF document...
Error loading PDF. Please make sure the file is valid and try again.
We also recommend
-
GB/T 34941-2017 in English
Information technology service-Digitize marketing-Programmatic marketing technology requirements
2017-11-01 -
GB/T 38840-2020 in English
Digital technique application of building and residence community-Primary data element
2020-06-02 -
GB/T 39046-2020 in English
Basic data specification of government service platform
2020-07-21
