GB/T 45346-2025 Information technology―Technical requirements for graph database management system English, Anglais, Englisch, Inglés, えいご
This is a draft translation for reference among interesting stakeholders. The finalized translation (passing through draft translation, self-check, revision and verification) will be delivered upon being ordered.
ICS 35.240.01
CCS L 70
National Standard of the People's Republic of China
GB/T 45346-2025
Information technology - Technical requirements for graph database management system
信息技术 图数据库管理系统技术要求
(English Translation)
Issue date: 2025-02-28 Implementation date: 2025-09-01
Issued by the State Administration for Market Regulation
the Standardization Administration of the People's Republic of China
Contents
Foreword
1 Scope
2 Normative references
3 Terms and definitions
4 Abbreviations
5 Reference architecture
6 Storage tier functional requirements
7 Computing layer functional requirements
8 Interface layer functional requirements
9 Functional requirements of tool layer
10 Operation and maintenance management requirements
Bibliography
Information technology - Technical requirements for graph database management system
1 Scope
This document determines the reference architecture of the graph database management system (hereinafter referred to as "graph database system"), and specifies the storage, calculation, interfaces, tools, operation and maintenance management requirements of the graph database system.
This document is applicable to the design, development, testing, evaluation, etc. of graph database systems.
2 Normative references
The following documents contain requirements which, through reference in this text, constitute provisions of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.
GB/T 1988 Seven-bit encoded character set for information exchange in information technology
GB 18030 Information Technology Chinese Encoded Character Set
GB/T 35273-2020 Information security technology Personal information security specifications
3 Terms and definitions
For the purpose of this document, the terms and definitions given in and the following apply.
3.1
graph
data structure that describes entities and their relationships using vertices and edges
3.2
graph database
non-relational database that uses a graph data model to store entities and their relationship information
Note 1: The data model of graph database consists of vertices and edges (i.e. the relationship between vertices).
Note 2: The graph database supports functions such as graph query, graph traversal and graph analysis, and is suitable for the exploration and discovery of complex relationships.
[Source： GB/T 37722-2019,3.1,modified]
3.3
graph database management system
system for defining, establishing, manipulating, controlling, managing, and using graph databases
3.4
graph schema
framework for defining types and relationships of vertices, edges, and their properties in a graph database that provides a comprehensive description of graph data structures, types, and constraints to ensure consistency and integrity of graph data
3.5
graph computing
abstract representation of the graph structure of data, and computational techniques on such data structures
4 Abbreviations
For the purpose of this document, the terms and definitions given in and the following apply.
ACID: Atomic, Consistency, Isolation, Durability
API: Application Programming Interface
BASE: Basic Availability, Soft state, Eventual consistency
CPU: Central Processing Unit
CSV: Comma Separate Values
DCL: Data Control Language
DDL: Data Definition Language
DML: Data Manipulation Language
GQL: Graphic Query Language
IOPS: Input/Output operations Per Second
IT: Information Technology
LDAP: Lightweight Directory Access Protocol
RDF: Resource Description Framework
REST: REpresentational State Transfer
XML: eXtensible Markup Language
5 Reference Architecture
The reference architecture of the graph database system is shown in Figure 1.
The reference architecture of a graph database system consists of five parts: storage layer, computation layer, interface layer, tool layer, and operation and maintenance management.
6 Storage tier functional requirements
6.1 Figure model
6.1.1 Figure Data Structure
6.1.1.1 Figure data structure representation
The graph data structure shall be represented as an attribute graph or as an RDF graph.
6.1.1.2 Attribute diagram structure
For the graph data structure represented by attribute graph, vertices and edges are used to abstract various business scenarios. The attribute diagram structure shall conform to
The following requirements:
a) It is composed of vertices and edges, vertices represent entities, edges represent relationships between entities, vertices and edges have types, types can be represented by labels, and there can be multiple edges of the same type between two vertices;
b) Use vertex attributes to represent attributes of entities, such as ID, timestamp, version number or name, etc.;
c) Use edge attributes to represent attributes of relationships between entities, such as strength, weight or quality;
d) Support the expression of directed attribute graph and undirected attribute graph at the same time;
e) The semantics of relationships between entities are expressed using the direction of the edge, which has a starting vertex and an ending vertex.
6.1.1.3 RDF diagram structure
Use RDF diagrams to describe the relationships among resources, attributes and values, and meet the following requirements:
a) Use vertices to represent resources, which can be objects with unique identifiers, or valued contents such as strings and integers;
b) using edges to represent directed links between resources, called predicates or attributes;
c) Use the incoming vertex of the edge to represent the subject, the outgoing vertex to represent the object, and the two vertices connected by the edge form a subject (subject)-predicate (predicate)-The statement of the object, that is, the triple.
Standard
GB/T 45346-2025 Information technology―Technical requirements for graph database management system (English Version)
Standard No.
GB/T 45346-2025
Status
valid
Language
English
File Format
PDF
Word Count
11500 words
Price(USD)
345.0
Implemented on
2025-9-1
Delivery
via email in 1~5 business day
Detail of GB/T 45346-2025
Standard No.
GB/T 45346-2025
English Name
Information technology―Technical requirements for graph database management system
GB/T 45346-2025 Information technology―Technical requirements for graph database management system English, Anglais, Englisch, Inglés, えいご
This is a draft translation for reference among interesting stakeholders. The finalized translation (passing through draft translation, self-check, revision and verification) will be delivered upon being ordered.
ICS 35.240.01
CCS L 70
National Standard of the People's Republic of China
GB/T 45346-2025
Information technology - Technical requirements for graph database management system
信息技术 图数据库管理系统技术要求
(English Translation)
Issue date: 2025-02-28 Implementation date: 2025-09-01
Issued by the State Administration for Market Regulation
the Standardization Administration of the People's Republic of China
Contents
Foreword
1 Scope
2 Normative references
3 Terms and definitions
4 Abbreviations
5 Reference architecture
6 Storage tier functional requirements
7 Computing layer functional requirements
8 Interface layer functional requirements
9 Functional requirements of tool layer
10 Operation and maintenance management requirements
Bibliography
Information technology - Technical requirements for graph database management system
1 Scope
This document determines the reference architecture of the graph database management system (hereinafter referred to as "graph database system"), and specifies the storage, calculation, interfaces, tools, operation and maintenance management requirements of the graph database system.
This document is applicable to the design, development, testing, evaluation, etc. of graph database systems.
2 Normative references
The following documents contain requirements which, through reference in this text, constitute provisions of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.
GB/T 1988 Seven-bit encoded character set for information exchange in information technology
GB 18030 Information Technology Chinese Encoded Character Set
GB/T 35273-2020 Information security technology Personal information security specifications
3 Terms and definitions
For the purpose of this document, the terms and definitions given in and the following apply.
3.1
graph
data structure that describes entities and their relationships using vertices and edges
3.2
graph database
non-relational database that uses a graph data model to store entities and their relationship information
Note 1: The data model of graph database consists of vertices and edges (i.e. the relationship between vertices).
Note 2: The graph database supports functions such as graph query, graph traversal and graph analysis, and is suitable for the exploration and discovery of complex relationships.
[Source： GB/T 37722-2019,3.1,modified]
3.3
graph database management system
system for defining, establishing, manipulating, controlling, managing, and using graph databases
3.4
graph schema
framework for defining types and relationships of vertices, edges, and their properties in a graph database that provides a comprehensive description of graph data structures, types, and constraints to ensure consistency and integrity of graph data
3.5
graph computing
abstract representation of the graph structure of data, and computational techniques on such data structures
4 Abbreviations
For the purpose of this document, the terms and definitions given in and the following apply.
ACID: Atomic, Consistency, Isolation, Durability
API: Application Programming Interface
BASE: Basic Availability, Soft state, Eventual consistency
CPU: Central Processing Unit
CSV: Comma Separate Values
DCL: Data Control Language
DDL: Data Definition Language
DML: Data Manipulation Language
GQL: Graphic Query Language
IOPS: Input/Output operations Per Second
IT: Information Technology
LDAP: Lightweight Directory Access Protocol
RDF: Resource Description Framework
REST: REpresentational State Transfer
XML: eXtensible Markup Language
5 Reference Architecture
The reference architecture of the graph database system is shown in Figure 1.
The reference architecture of a graph database system consists of five parts: storage layer, computation layer, interface layer, tool layer, and operation and maintenance management.
6 Storage tier functional requirements
6.1 Figure model
6.1.1 Figure Data Structure
6.1.1.1 Figure data structure representation
The graph data structure shall be represented as an attribute graph or as an RDF graph.
6.1.1.2 Attribute diagram structure
For the graph data structure represented by attribute graph, vertices and edges are used to abstract various business scenarios. The attribute diagram structure shall conform to
The following requirements:
a) It is composed of vertices and edges, vertices represent entities, edges represent relationships between entities, vertices and edges have types, types can be represented by labels, and there can be multiple edges of the same type between two vertices;
b) Use vertex attributes to represent attributes of entities, such as ID, timestamp, version number or name, etc.;
c) Use edge attributes to represent attributes of relationships between entities, such as strength, weight or quality;
d) Support the expression of directed attribute graph and undirected attribute graph at the same time;
e) The semantics of relationships between entities are expressed using the direction of the edge, which has a starting vertex and an ending vertex.
6.1.1.3 RDF diagram structure
Use RDF diagrams to describe the relationships among resources, attributes and values, and meet the following requirements:
a) Use vertices to represent resources, which can be objects with unique identifiers, or valued contents such as strings and integers;
b) using edges to represent directed links between resources, called predicates or attributes;
c) Use the incoming vertex of the edge to represent the subject, the outgoing vertex to represent the object, and the two vertices connected by the edge form a subject (subject)-predicate (predicate)-The statement of the object, that is, the triple.
