GB/T 39461-2020.Data
interface of the international logistics information system . Interface communication methods, data transmission, data conversion, communication message requirements, security requirements, interface functions and interface management.
GB/T 39461 is suitable for international logistics stakeholders to develop and use international logistics information system data interfaces, and can also be used by management departments to manage international logistics information systems and related interfaces.
2 Normative references
The following documents are essential for the application of this document. For dated reference documents, only the dated version applies to this document. For undated referenced documents, the latest version (including all amendments) applies to this document.
GB/T 7408 Data elements and interchange formats Date and time representation for information exchange
GB/T 14805 (all parts) Electronic Data Interchange for Administration, Commerce and Transport (EDIFACT) application-level syntax rules (Grammar version number: 4, Grammar release number: 1)
GB/T 18354-2006 Logistics terminology
GB/T 26318 Logistics network information system risks and prevention
GB/T 26320 International Freight Forwarding Information Exchange Specification
3 Terms and Definitions, Abbreviations
3.1 Terms and Definitions
GB/T 18354-2006 and the following terms and definitions apply to this document .
3.1.1
Logistics information logistics information
A general term for knowledge, materials, images, data, and files that reflect the contents of various logistics activities.
[GB/T 18354-2006, definition 2.23].
3.1.2
international logistics information system
Information system applied to international logistics management.
3.1.3
public key infrastructure
Infrastructure that provides security services established using public key theory and technology.
Note: Basic technologies include encryption, digital signatures, data integrity mechanisms, digital envelopes, double digital signatures, etc.
3.2 Abbreviations
The following abbreviations apply to this document.
ANSI: American National Standards Institute
AS2: Communication transmission protocol (Applicability Statement 2)
This standard specifies the international logistics information system (hereinafter referred to as: system ) basic requirements for data interfaces, interface communication methods, data transmission, data conversion, communication message requirements, security requirements, interface functions and interface management. This standard is applicable to the development and use of international logistics information system data interfaces by international logistics stakeholders, and can also be used as a management department for the management of international logistics information systems and related interfaces.

ICS03.100.01
A02
GB
National Standard of the People's Republic of China
GB/T39461—2020
International Logistics Information System Data Interface||tt| |Data interface of the international logistics information system2020-11-19 Released
State Administration for Market Regulation
National Standardization Administration Committee
Released
Implemented on 2021-06-01
Foreword
Scope
2
3
5
6
7
8|| tt||9
10
11
Normative reference documents
Terms and definitions, abbreviations
Basic requirements
Interface communication Method
Data transmission
Data conversion
Communication message requirements
Security requirements
Interface function
Interface management.||tt| |Appendix A (informative appendix)
Appendix B (informative appendix)
item
times
general example of XML structure of communication message message
General example of JSON structure of communication message messages GB/T39461—2020
Foreword
This standard is drafted in accordance with the rules given in GB/T1.1-2009GB/T39461—2020
Please Note that some content in this document may involve patents. The publisher of this document assumes no responsibility for identifying these patents. This standard is proposed and coordinated by the National Shenzi Business Standardization Technical Committee (SAC/TC83). This standard was drafted by: Shenzhen Kunxin International Freight Forwarding Co., Ltd., Xiamen Denghan Shipping Co., Ltd., Beijing Jiuxing Times Technology Co., Ltd., Jiaxing Dadi Logistics Co., Ltd., Yiwu Jinlong Yijingtong Supply Chain Service Co., Ltd., Chongqing Shenzi Engineering Vocational College, China Institute of Standardization, Shanghai Xinjingcheng International Logistics Co., Ltd., Xinjiang High-tech Project Development Research Institute (Co., Ltd.), Beijing Zongheng Standard Technology Co., Ltd., Dalian Wanfa United Aviation and Trade Technology Co., Ltd., Kashgar Jinlida International Logistics Center Co., Ltd., Xinjiang Drouya International Logistics Co., Ltd., Xinjiang Agricultural University, Tumushuke Haina Import and Export Co., Ltd., Guangdong Xinyi Management Consulting Co., Ltd., Hotan Hengyang Foreign Trade Co., Ltd., Yili TORRIDA TRANSPORT LIMITED. Drafters of this standard: Lin Zhong, Zhang Yinfen, Lin Ting, Yao Shuhong, Zhang Wenhui, Ge Ju, Huang Zhiping, Guo Jiangzhu, Lin Xiaowei, Jin Xufeng, Cao Jianfeng, Yang Xijiang, Chen Feng, Kang Shuchun, Chen Ming, Xiang Guolun, Lei Yufeng, Gong Su Xin, Hou Huimin, Cai Yidi, Zhong Jing m
G
1 scope
International logistics information system data interface
GB/T39461—2020
This standard specifies the basic requirements for data interfaces, interface communication methods, data transmission, data conversion, communication message requirements, security requirements, interface functions and interface management of the international logistics information system (hereinafter referred to as the system). This standard is applicable to the development and use of international logistics information system data interfaces by international logistics stakeholders, and can also be used as a management department for the management of international logistics information systems and related interfaces. Normative reference documents
2
52
The following documents are essential for the application of this document. For dated references, only the dated version applies to this document. For undated referenced documents, the latest version (including all amendments) applies to this document. Date and time representation
GB/T7408 Data elements and exchange formats Information exchange GB/T14805 (all parts) Electronic Data Interchange for Administration, Commerce and Transport (EDIFACT) application-level syntax rules (syntax version number: 4, Grammar release number: 1)
GB/T18354-2006 Logistics terminology
GB/T26318 Logistics network information system risks and prevention GB/T26320 International freight forwarding information exchange specifications 3 terms and definitions, abbreviations| |tt||3
3.1
Terms and Definitions
The terms and definitions defined in GB/T18354-2006 and the following apply to this document. 3.1.1
Logistics information
logisticsinformation
is a general term for knowledge, materials, images, data and documents that reflect the content of various logistics activities. [GB/T18354-2006, definition 2.23]. 3.1.2
international logistics information system International logistics information system
is an information system applied to international logistics management. 3.1.3
Public key infrastructure
public key infrastructure
Infrastructure that provides security services established using public key theory and technology Note: Basic technologies include encryption, digital signatures, data Integrity mechanisms, digital envelopes, double digital signatures, etc. 3.2
2 Abbreviations
The following abbreviations apply to this document.
ANSI:
AS2：
American National Standards Institute (AmericanNationalStandardsInstitute) Communication Transmission Protocol (ApplicabilityStatement2) GB/T39461—2020
ebMS：
FTP :
HTTP:
HTTPS:
JSON:
PKI:
SFTP:
SMTP:
SSL:
TLS:
Electronic Business Message Service Specification (FileTransferProtocol) HyperText Transfer Protocol (HyperTextTransferProtocol) HyperTextTransferProtocoloverSecureSocketLayer) Object Notation (JavaScriptObjectNotation) Public Key Basics Facility (publickeyinfrastructure) Secure File Transfer Protocol (SecretFileTransferProtocol) Simple Mail Transfer Protocol (SimpleMailTransferProtocol) Secure Sockets Layer (SecureSocketsLayer) Secure Transport Layer Protocol TransportLayerSecurityUN/EDIFACT: United Nations Electronic Data Interchange for Administration, Commerce and Transportation (UnitedNations/Elec -tronicDataInterchangeForAdministration,CommerceandTransport)UUID:
The Extensible Markup Language (ExtensibleMarkupLanguage) interface communication method is shown in Chapter 5. The system should specify one of the methods for communication. 4.2
Transmission control
Transmission control should specify the requirements for transmission means, transmission communication requirements, transmission content, data specifications, system components and communication messages.
Interface Security
4.3
See Chapter 9 for interface security related requirements.
Transmission content
4.4
The transmission content should include various logistics information related to the system user. Examples: basic cargo information, warehousing information, logistics status information, processing information, packaging information, loading and unloading information, etc. 5Interface components and processes
4.5
The transmission interface should include but not be limited to communication components, security components, verification components, format conversion components, code translation components, etc. The sender's processing process should go through code translation, data verification, format conversion, encryption and signature, and finally be sent to the receiver interface system through the communication component according to the agreed communication method. After receiving the message message from the sender through the communication component, the receiver should first verify the reliability of the message, whether the format meets the requirements, format conversion and code translation, and then deliver it to the logistics information system. 4.6
Interface management
Interface management requirements should include but are not limited to monitoring of the information transmission process, management and maintenance of interface types, interface relationships, data status and historical information.
2
SAG
Interface communication mode
5
5.1 Synchronous response mode
The initiator sends a data request to the receiver, and the receiver The processing results should be returned synchronously. 5.2
Asynchronous response type
GB/T39461—2020
The initiator sends a data request to the receiver. The sender no longer waits for the receiver's processing result, and the receiver completes the processing. Send receipt information. When using this method, the initiator should clearly inform the recipient of the necessary information such as the return receipt request method and address. 5.3 Conversational
The initiator and the receiver establish a channel that can transmit data to each other multiple times. 5.4 Broadcast notification
The sender pushes a single or multiple interface messages in the form of broadcast notification to one or more receivers, and the receiver processes the interface information at an appropriate time.
5.5 Subscription
One party subscribes to an event from the other party, and the subscriber should be notified when the other party responds to the event. 5.6 File transfer type
The sender and receiver transmit interface information through files. Reliable message transmission method
5.7
The client and server transmit messages through storage queues and take corresponding processing. 5.8 Unspecified methods
For unspecified methods, the system shall publish the communication methods and requirements of both the initiator and the recipient in the form of document publication. 6 Data transmission
6.1 Transmission means
Transmission means should support multiple protocols, including but not limited to HTTP, HTTPS, SFTP, FTP, SMTP, ebMS and AS2.
6.2 Transmission protocol requirements
6.2.1HTTP, FTP and Socket
When transmitting data using HTTP, FTP and Socket (socket) methods, part of the transmission message should be combined or All content is encrypted, signed, etc. to prevent data leakage and data tampering during the transmission process. 6.2.2 HTTPS
When using HTTPS communication and transmission, two-way authentication should be used on the basis of complying with its own basic specifications method to ensure the validity and legality of the interactive parties. Www.bzxZ.net
6.2.3AS2
When using AS2 for data transmission, HTTPS should be used to transmit data. 6.2.4 Other transmissions
Other transmission protocols should comply with their own requirements. 6.3 Transmission content
6.3.1 Content classification
Transmission content should be classified according to the different functional areas involved in the generation and function of information. 6.3.2 Transmission information
Transmission information should include but not be limited to order information, location information, start and end time information, as well as information related to transportation methods, payment methods, delivery methods, settlement methods, etc.
6.4 Message Transmission Guarantee
6.4.1 Message Transmission
SAC
The initiator should ensure that the message is sent once and only once before receiving the message confirmation. In businesses that require high data accuracy, if you need to ensure the unique validity of the sending behavior, you can use the token mechanism (Token). If you need to ensure the unique authenticity of the data contained in the sent message, you can use idempotence. sexual mechanism. 6.4.2 Message confirmation
The logistics information interface system should have a synchronous or asynchronous reception of the message recipient's receipt information and communication abnormality compensation mechanism. Receipt information should include clear message status.
The cancellation status is divided into two types:
Accepted (Accepted), indicating that the recipient has recognized and accepted the information; Rejected (Rejected), indicating that the recipient does not recognize the information. 6.4.3 Message resend mechanism
The logistics information system should have a message resend mechanism. If the sender does not receive a confirmed message, it should perform a retry operation until a confirmed message is received, or it should judge If the number of retries has been exceeded and a delivery failure message is notified. 6.4.4 Message backup mechanism
When an error occurs, the system should automatically back up the file and the cause of the error, and place the file in a specific directory. 6.4.5 Error code publication
Clear error codes and status codes should be published, and the codes should not be ambiguous or confusing. The code should include but not be limited to system code and business code, and a clear distinction should be made. 6.5 Electronic data exchange
Shenzi data exchange shall follow the general principles and requirements for information exchange in GB/T14805 (all parts), and comply with the relevant provisions on information exchange rules in GB/T2632C4
. 7
Data conversion
Data conversion functions and components
7.1
GB/T39461—2020
The system interface should provide complete data conversion functions to achieve Conversion between different formats and translation of data content ensures normal reception of various types of data between systems.
Data conversion functions and components are shown in Figure 1. Sender and receiver A
Business
Service
Message
Message
System
System
7.2 Convertible Data Format
Message Service Controller
Code
Conversion
Format
Conversion
Figure 1
Message||tt ||Confirmation message
Message
Confirmation message
Transmitter B
Message Service Controller
Format
Code| |tt||Conversion
Data conversion functions and components
Conversion
Business
Service
Information
System
The system interface should support the conversion of multiple data formats, including but not limited to XML, JSON and custom text. 8 Communication message requirements
8.1 Overview
When transmitting interface messages, it should include but not Limited to the clear multi-layer structure of message header and message body. Message header
8.2
The message header is used to express the general information of the message, including but not limited to the following information: Message number: the message number used to determine the unique request identity, UUID can be used ;Business code: the business number code determined by the sender and receiver; Sender code: sender identification number; Receiver code: receiver identification number; Send time: the time when the interface message is sent, and its time format should comply with GB/ T7408 regulations. 8.3 The message body
should completely describe the specific business situation.
8.4 Other specification requirements
The message structure and content should comply with the corresponding national standards and the UN/EDIFACT series of messages, ANSI series of messages and other series of messages developed by public organizations and departments.
See Appendix A for a general example of communication message XML structure. 5
GB/T39461—2020
Please refer to Appendix B for a general example of the JSON structure of communication message messages. 9 Security requirements
9.1 Privacy
The system should use SSL technology to ensure the privacy of data transmission. It is recommended to use TLS1.2 and above. The sender can digest the transmitted information, use the private key to digitally sign and encrypt the digest, and send the signature and encryption results to the receiver together with the message.
9.2 Anti-computation tampering
The system should use PKI digital certificate cross-certification to digitally sign messages. It should ensure that data is not tampered with during transmission and achieve non-repudiation of message sending and receiving.
The receiver can use the public key for verification to ensure the integrity of the data. 9.3
Safety specifications
System security should comply with the regulations in GB/T26318. 10
Interface functions
Interface functions include but are not limited to the following aspects: the control component is the system interface master control component, which is used to control and coordinate the processing sequence and process of the interface processing component; the communication component is used The external communication service layer of the interface system and the partner interface system should include communication protocols such as HTTP and FTP;
security components are used for security needs, including providing encryption functions, decryption functions, and signature functions for security needs and verify signature functions;
The verification component is used for verification needs, including providing verification functions for data format and whether the data conforms to the interface specification: the format conversion component should convert the format and data according to the specific interface specification requirements. Parse and convert into formats and data that the logistics system can understand:
The code translation component should use the codes specified in existing national standards or international standards when transmitting. When non-standard code translation functions are used, non-standard code translation functions should be provided. The schematic diagram of interface function association is shown in Figure 2.
Receiver interface system
Control component
Logistics information
Department
6
Generation
Code translation|| tt||group
formula conversion
dimension
pieces
+
check
dimension
pieces|| tt||Security component
Initiator interface system
Control component
Transfer
Verification group
Security component
Figure 2 interface Functional association diagram
Code translation component
Logistics information system
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.