title>GB/T 14805.3-1999 Application-level grammar rules for electronic data interchange for administration, commerce and transport (Syntax version number: 4) Part 3: Syntax rules specific to interactive electronic data interchange - GB/T 14805.3-1999 - Chinese standardNet - bzxz.net
Home > GB > GB/T 14805.3-1999 Application-level grammar rules for electronic data interchange for administration, commerce and transport (Syntax version number: 4) Part 3: Syntax rules specific to interactive electronic data interchange
GB/T 14805.3-1999 Application-level grammar rules for electronic data interchange for administration, commerce and transport (Syntax version number: 4) Part 3: Syntax rules specific to interactive electronic data interchange

Basic Information

Standard ID: GB/T 14805.3-1999

Standard Name: Application-level grammar rules for electronic data interchange for administration, commerce and transport (Syntax version number: 4) Part 3: Syntax rules specific to interactive electronic data interchange

Chinese Name: 用于行政、商业和运输业电子数据交换的应用级语法规则 (语法版本号:4)第3部分:交互式电子数据交换专用的语法规则

Standard category:National Standard (GB)

state:Abolished

Date of Release1999-08-02

Date of Implementation:2000-03-01

Date of Expiration:2007-11-01

standard classification number

Standard ICS number:Information technology, office machinery and equipment>>Information technology applications>>35.240.60 Information technology in transportation and trade

Standard Classification Number:Electronic Components and Information Technology>>Information Processing Technology>>L70 Comprehensive Information Processing Technology

associated standards

alternative situation:Replaced by GB/T 14805.3-2007

Procurement status:idt ISO 9735-3:1998

Publication information

publishing house:China Standards Press

ISBN:155066.1-16480

Publication date:2004-08-22

other information

Review date:2004-10-14

Drafting unit:China Institute of Standardization and Information Classification and Coding

Focal point unit:National Electronic Business Standardization Technical Committee

Publishing department:State Administration of Quality and Technical Supervision

competent authority:National Standardization Administration

Introduction to standards:

This standard specifies the grammatical rules for the transmission of interactive messages exchanged between computer application systems. GB/T 14805.3-1999 Application-level grammatical rules for electronic data interchange in administration, commerce and transport (grammar version number: 4) Part 3: Grammar rules for interactive electronic data interchange GB/T14805.3-1999 Standard download decompression password: www.bzxz.net

Some standard content:

National Standard of the People's Republic of China
GB/T14805.3—1999
idt ISO 9735-3:1998
Electronic data interchange for administration, commerce and transport (EDIFACT)Application level syntax rules (Syntax version number :4)-Part 3: Syntax rules specific to interactive EDI1999-08-02 issued
State Administration of Quality and Technical Supervision
2000-03-01 implementation
GB/T14805.3—1999
iKAoNiKAca-
This standard is equivalent to ISO9735-3:1998 "United Nations application-level syntax rules for electronic data interchange for administration, commerce and transport Part 3: Syntax rules specific to interactive electronic data interchange". GB/T14805.X series of standards, under the general title of "Application-level grammar rules for electronic data interchange for administration, commerce and transport (grammar version number: 4)", currently includes the following 10 parts: Part 1: Common grammar rules and grammar service directory Part 2: Grammar rules specific to batch electronic data interchange Part 3: Grammar rules specific to interactive electronic data interchange Part 4: Grammar and service report message for batch electronic data interchange (message type CONTRL) Part 5: Security rules for batch electronic data interchange (authenticity, integrity and non-repudiation of origin) Part 6: Security authentication and confirmation message (message type AUTACK) Part 7: Security rules for batch electronic data interchange (confidentiality) Part 8: Related data in electronic data interchange Part 9: Key and certificate management message (message type KEYMAN) Part 10: Security rules for interactive electronic data interchange New parts may be added in the future.
GB/T14805.X series of standards correspond to the fourth edition of ISO9735. Although ISO9735:1998 replaces the earlier versions, users can still use the earlier versions according to the relevant provisions of ISO9735:1998. In view of this, the national standard GB/T14805-1993 formulated by my country in 1993 based on the 1998 version, 1990 version and 1992 version of ISO9735 can also continue to be used for a period of time in the future. Therefore, the release and implementation of this series of standards do not replace GB/T14805-1993.
Appendix A, Appendix B and Appendix C of this standard are all informative appendices. This standard is proposed and managed by the China Institute of Standardization and Information Classification and Coding. This standard is jointly drafted by the China Institute of Standardization and Information Classification and Coding, the Business Standardization Department of the General Administration of Customs, the Data Transmission Institute of the Ministry of Posts and Telecommunications, and the Water Transport Institute of the Ministry of Communications.
The main drafters of this standard are: Liu Bisong, Cheng Nufan, Hu Hanjing, Fang Qing, Shi Wenlai, Chen Shuyi, Liu Fang, and Chen Qiming. I
GB/T14805.3—1999
ISO Foreword
ISO (International Organization for Standardization) is a worldwide federation of national standards bodies (ISO national member bodies). The development of international standards is generally carried out through ISO technical committees. Each member body interested in the project of an established technical committee has the right to express its opinions to the technical committee. Any official and non-official international organization in liaison with ISO can directly participate in the development of international standards. ISO and IEC (International Electrotechnical Commission) work closely in all areas of electrotechnical standards. Draft international standards formally adopted by the technical committee must be voted on by the member groups, and publication as an international standard requires at least 75% of the member groups to vote in favor.
This international standard ISO9735 was drafted by the Trade Department of the United Nations Economic Commission for Europe (UN/ECE) (as part of UN/EDIFACT) and formally adopted by ISO/TC154 (Technical Committee for Documents and Data Elements in Administration, Commerce and Industry) through the "fast voting procedure".
Since this standard replaces earlier versions and uses the mandatory data element 0002 (Syntax version number) in the exchange header (UNB) segment to identify this version, exchanges that continue to use the syntax rules of earlier versions should use the following syntax version numbers to distinguish them from each other. ISO 9735:1988 - Syntax version number: 1 ISO 9735:1988 (revised and reprinted 1990) - Syntax version number: 2 ISO 9735:1988 (revised and reprinted 1990) and its amendment No. 1, 1992 - Syntax version number: 3 ISO/IEC 9735 (current version) consists of the following parts under the general title "United Nations application-level syntax for electronic data interchange for administration, commerce and transport (Syntax version number: 4)": ISO 9735-1 Common syntax rules and syntax service catalogue ISO 9735-2 Syntax rules specific to batch electronic data interchange ISO 9735-3 Interactive electronic data interchange (Syntax version number: 4) Syntax rules for sub-data interchange ISO9735-4 Syntax and service report message for batch electronic data interchange (message type CONTRL) ISO9735-5 Security rules for batch electronic data interchange (authenticity, integrity and non-repudiation of origin) ISO9735-6 Security authentication and confirmation message (message type AUTACK) ISO9735-7 Security rules for batch electronic data interchange (confidentiality) ISO9735-8 Related data in electronic data interchange ISO9735-9 Key and certificate management message (message type KEYMAN) ISO9735-10 Security rules for interactive electronic data interchange New parts may be added in the future.
In this standard, Appendix A, Appendix B and Appendix C are informative appendices. GB/T14805.3—1999
ISO Introduction
KAONiKAca-
This standard contains application-level rules for structuring data in electronic message exchange in an open environment, depending on the needs of batch or interactive processing. The United Nations Economic Commission for Europe (UN/ECE) has agreed to use these rules as application-level syntax rules for electronic data interchange for administration, commerce and transport (EDIFACT). These rules are part of the United Nations Trade Data Interchange Directory (UNTDID). UNTDID also contains guidelines for batch and interactive message design. This standard can be used for any application, but messages using these rules can only be called EDIFACT messages if they comply with other guidelines, rules and directories in UNTDID. For UN/EDIFACT, interactive messages should comply with the interactive EDI message design rules, which are maintained in UNTDID. Communication specifications and protocols are not within the scope of this standard. This standard is a new addition to ISO9735 (current version). It provides for the exchange of EDIFACT messages in an interactive (conversational) EDI environment.
Interactive EDI (I-EDI) has the following characteristics: a formalized link between two parties using a dialogue; - the ability to dynamically indicate the direction of an I-EDI transaction based on the results of previous exchanges in the dialogue; - short response times;
- all messages exchanged in a dialogue relate to the same business transaction; - a transaction is a controlled collection of dialogues that can take place between two or more parties. These characteristics distinguish I-EDI from the batch EDI specified in ISO 9735-2 (Syntax Rules for Batch Electronic Data Interchange). This standard has been largely aligned with ISO 9735-2 for the sake of consistency and to simplify implementation by users who wish to use both batch and interactive processing.
1 Scope
National Standard of the People's Republic of China
Application-level syntax rules for electronic data interchange for administration, commerce and transport
(Syntax version number: 4)
Part 3: Interactive electronic data interchange
Special syntax rules
Electronic data interchange foradministration, commerce and transportCommerce and transport (EDIFACT)—Application level syntax rules (Syntax version number :4)-Part 3: Syntax rules specific to interactive EDIGB/T14805.3—1999
idtIS09735-3.1998
This standard specifies syntax rules for the transmission of interactive messages exchanged between computer application systems. For the transmission of packets in an interactive environment, see GB/T14805.8.2 Conformance
Conformance to a standard means supporting all its requirements, including all options. If not all options are supported, any conformance statement shall contain a statement identifying those options that are declared to be conformant. If the structure and representation of the data exchanged conform to the syntax rules specified in this standard, the data are in a conformant state. Devices supporting this standard are in a conformant state when they can create and/or interpret data whose structure and representation conform to this standard.
Conformity with this standard shall include conformity with GB/T 14805.1. When clauses defined in related standards are identified in this standard, these clauses shall constitute part of the consistency judgment criteria. 3 Referenced standards
The clauses contained in the following standards become the clauses of this standard through reference in this standard. When this standard was published, the versions shown were valid. All standards will be revised, and parties using this standard should explore the possibility of using the latest versions of the following standards. Members of ISO and IEC maintain registrations of currently valid international standards. GB/T14805.1—1999 Application-level grammar rules for electronic data interchange in administration, commerce and transport (Syntax version number: 4) Part 1: Common grammar rules and grammar service directory (idtISO9735-1): 1998) GB/T14805.8—1999
4 Definition
Application-level grammar rules for electronic data interchange in administration, commerce and transport (Syntax version number: 4) Part 8: Related data in electronic data interchange (idtISO9735-8: 1998) The definitions adopted in this standard can be found in Appendix A of GB/T14805.1. Approved by the State Administration of Quality and Technical Supervision on August 2, 1999 and implemented on March 1, 2000
5I-EDI exchange structure
GB/T14805.3—1999
-KAoNiKAca-
In I-EDI exchange, the service string notification (if used), the header service segment and the trailer service segment appear in the following order: Name
Service string notification
Interactive exchange header
Interactive message header
Interactive message trailer
Interactive exchange trailer
Message body
Conditional
Mandatory
Mandatory
Mandatory
In the above figure, the lines on the left indicate pairs of header and trailer segments. For simplicity, the exchange shown in the figure contains only one message. The specification of the service string notification is shown in Appendix B of GB/T14805.1. The specification of the interactive header and trailer is shown in Appendix C of GB/T14805.1. Note: The segments used in UN/EDIFACT messages are defined in the United Nations Trade Data Interchange Directory (UNTDID). 5.1 I-EDI messages in transactions (see Figure 1). 2
Generally remember
The initiator changes the connection
GB/T14805.3—1999
I-EDI transaction
The data element
is based on the data element
and the data element
is exchanged
data element
data element
accompanying single number element
a I-EDI message in a transaction (schematic diagram) Figure 1
Combined data
data element
data element
An I-EDI transaction includes:||tt ||A dialogue contains:
an initiator exchange
a corresponding responder exchange
an initiator exchange contains:
GB/T14805.3—1999
-UNA, service string announcement (if used) UIB, interactive exchange header
a message (if any)
-UIZ, interactive exchange tail
a responder exchange contains:
-UIB, interactive exchange header
message (if any)
-UIZ, interactive exchange tail
a message contains:
-UI H, interactive message header
a message body
UIT, interactive message tail
a message body contains:
segment and/or segment group
a segment group contains:
a trigger segment
segment and possible segment group
a segment contains:
two segment markers
an independent data element and/or a compound data element and/or repeated independent data element and/or repeated compound data element. A repeated independent data element is:
one or more occurrences of the same independent data element. A repeated compound data element is:
one occurrence of the same compound data element. One or more occurrences of a composite data element contains:
One or more component data elementsThe component data elements are:
A simple data element
An independent data element is:
Simple data element
A simple data element contains:
Data element value
I-EDI message in transaction (illustrative diagram)
Figure 1 (end)
6 Dialogue control
KANiKAca-bzxZ.net
-An I-EDI transaction is an instance of a specific script, consisting of one or more dialogues, which occur simultaneously or sequentially between two or more participants.
GB/T14805.3—1999
A dialogue consists of a pair of alternating EDIFACT exchanges, one of which is the initiator exchange and the other is the responder exchange. The following transfer shall occur:
The initiator begins a dialog by sending an Exchange Header segment to the responder. Before the Exchange Header segment, UNA segments may be placed as needed, and after the Exchange Header segment, messages may be placed as needed. The responder replies to the initiator with an Exchange Header segment. After the Exchange Header segment, messages may be placed as needed (note: the value of UNA sent by the initiator also applies to the responder).
The initiator sends a Query message to the responder. The responder replies to the initiator with a Reply message. The initiator and responder exchange other messages as needed. The initiator ends the dialog by sending an Exchange End segment to the responder. Before the Exchange End segment, messages may be placed as needed. The responder replies to the initiator with an Exchange End segment. Before the Exchange End segment, messages may be placed as needed. Several variations are possible:
For each message from the initiator to the responder, the responder may have none, one, or more reply messages to the initiator, and vice versa.
The UIR service segment may alternate with messages. Either party may terminate the conversation prematurely at any time using the UR service segment. One or more messages may be combined with one of the following: an exchange header; an exchange trailer; an exchange header and an exchange trailer (forming a complete conversation). Although the exchange of data controlled by the initiator is a common mode of operation for interactive applications, the I-EDI syntax does not exclude other modes of operation. See Appendix A for examples. Figure 2 is a flow chart of two exchanges that together form a conversation. Initiator Exchange
Segment Name
Service Notification
Exchange Header
Exchange Stabilization
Segment Tags
UTH., UIT
Side Exchange
Exchange Header
Exchange Distance
Figure 2 Flow Chart of Two I-EDI Exchanges
UIH. . LTT
The arrows in Figure 2 indicate the direction of data flow. Note that UNA is only sent by the initiator. The status in Figure 2 indicates mandatory (M) or conditional (C) and the number of allowed repetitions. At least one message should be sent in each exchange. See Appendix A for details.
GB/T14805.3—1999
Appendix A
(Suggestive Appendix)
Examples to illustrate the sequence of segments
Example a) The first and last messages are paired messages with the exchange header and exchange trailer, respectively: Initiator UIB..UIH...Segment and/or segment group..UIT Responder
Initiator
Responder
Initiator
Responder
UIB...UIH...Segment and/or segment group...UITUIH..Segment and/or segment group...UIT
UIH..Segment and/or segment group.. .UIT
UIH...segment and/or segment group...UIT
UIH...segment and/or segment group.UIT
Initiator
UIH...segment or/or segment group...UIT...UIZUIH...segment or/or segment group...UIT...U
Responder
-KAONiKAca-
Example b) Paired messages with separated exchange header and exchange trailer with UNA (note that UNA is only sent by the initiator, but also applies to the responder):
Initiator
Responder|| tt||Initiator
Responder
Initiator
Responder
Initiator
Responder
UNA...UIB
UIH..segments and/or segment groups..UIT
UIH...segments and/or segment groups...UIT
UIH...segments and/or segment groups..UIT
UIH..segments and/or segment groups..UIT
UIH...segments and/or segment groups..UIT
Initiator| |tt||Responder
Example c) A single message combined with an exchange header and an exchange trailer:Initiator
Responder
UIB...UIH...Segments and/or segment groups...UIT..UIZUIB...UIH...Segments and/or segment groups..UIT.UIZExample d) A sequence of multiple messages with the last message combined with an exchange trailer:UIB
Initiator
Responder
Initiator
UIH...Segments and/or segment groups..UIT
Responder
UIH(F). Segments and/or segment groups...UIT
UIH(L). Segment and/or segment group..UIT
Initiator
UIH... Segment and/or segment group..UIT..UIZ
Responder
UIH... Segment and/or segment group..UIT..UIZ
Example e) Paired message with separate exchange header and exchange trailer with UNA, in which a pair of UIRs are embedded: Initiator UNA..UIB
Responder
Initiator
Responder| |tt||Initiator
Responder
Initiator
Responder
UIH...Segment and/or segment group..UIT
GB/T14805.3—1999
UIH...Segment and/or segment group...UIT
UIR...Report function, code type = 'n' (query status)UIR..Report function, code type = 'n' (status report)UIH..Segment and/or segment group or segment group...UIT
UIH...segment and/or segment group..UIT
Initiator
Responder
Example f) Paired message with separate exchange header and exchange trailer with UNA, where UIR is used to report serious errors detected by the responder Initiator
Responder
Initiator
Responder
Initiator
Responder
Initiator
Responder Party
UNA...UIB
UIH...Segment and/or segment group..UIT
UIH..Segment and/or segment group.UIT
UIH.Segment and/or segment group.UIT
UIH...Segment and/or segment group..UIT
UIH...Segment and/or segment group..UIT
UIH...Segment and/or segment group..UIT
UIR..Reporting function, code type = 'n' (Discarding the conversation) Reason code indicates the scope of the problem.
No further exchanges can be made in this conversation. Example g) Dialogue that cannot be started. The responding party reports the rejection of the start of the conversation with UIR: Initiating party UNA...UB
Responding party UIR...Reporting function, code type = 'n' (Discarding the conversation) Reason code indicates the scope of the problem.
No further exchanges can be made in this conversation. Example h) A paired message in which the first and last message are combined with an exchange header and an exchange trailer, respectively, where pause and continue are used:
Initiator
Responder
Initiator
Responder
Responder
UIB...UIH...Segment and/or segment group..UITUIB...UIH..Segment and/or segment group..UIT
UIH..Segment and/or segment group.UIT
UIH..Segment and/or segment group.UIT
UIR...Reporting function, code type = 'n' (Pause conversation) Reason code indicates the reason for the pause, such as insufficient resources. No further data flow in the dialog until a certain time has passed:Responder
Initiator
Responder
Initiator
Responder
UIR.Report function, code type = 'n' (continue dialog)UIH..segment and/or segment group..UIT
UIH...segment and/or segment group...UIT
UIH...segment and/or segment group...UIT...UIZUIH...segment and/or segment group...UIT...UIZ7||t t||B1I-EDI Functions
GB/T14805.3—1999
Appendix B
(Informative Appendix)
I-EDI Functions, States and Events
FKAOiKAca
In the following clauses, the term "application" may refer to the main application program or to the part of the I-EDI operation that manages the I-EDI dialogue, depending on the context. The term "contact" refers to the logical relationship between two applications, rather than any other meaning used in other standards. Note that the following functions do not necessarily map onto a single service segment or message. Start Dialogue Request
Allows an application to pass sufficient information to a remote application to be able to initiate a contact between the two applications. Start Dialogue Confirmation
Allows a remote application to pass sufficient information to the initiating application to notify it that the contact has been accepted. Start Dialogue Rejection
Allows a remote application to transmit sufficient information to the initiating application to notify it that the contact cannot be accepted. Send Data
Allows an application to send business information to another application. Request Status
Allows an application to request status or control information from the other application in a contact Report Status (Reply)
Allows an application to send status or control information to the other application in a contact. This can be a reply to a Request Status, or as an unsolicited attached report. Suspend Conversation
Allows an application to request that a conversation be suspended until it requests that it be continued. Continue Conversation
Allows an application to request that a conversation be continued that it had previously requested to be suspended. Abandon Conversation
Allows an application to unconditionally terminate a contact if it cannot maintain the contact End Conversation Request
Allows an application to request that the other application in a contact terminate the contact. This function usually occurs at the end of a business transaction. End Conversation Acknowledge
Allows the responding application to confirm to the requesting application that the contact has been terminated. Complete Conversation Request
Allows an application to transmit enough information to a remote application to establish a contact, pass data, and terminate the contact between the two applications in a single transfer.
Full Dialog Confirmation
Allows a remote application to pass sufficient information to the initiating application to notify it of the acceptance of a connection, the return of data, and the termination of the connection in a single transmission.
B2 Data Requirements
Table B1 indicates how the abstract I-EDI functions are mapped into I-EDI service segments and messages, where the "s" (status) column indicates whether the segment is mandatory or conditional in the I-EDI function, and the "R" column indicates its repetition count. 83—1999
Appendix B
(Informative Appendix)
I-EDI Functions, States and Events
FKAOiKAca
In the following clauses, the term "application" may refer to either the main application program or the part of the I-EDI operation that manages the I-EDI dialogue, depending on the context. The term "contact" refers to the logical relationship between two applications and not to any other meaning used in other standards. Note that the following functions do not necessarily map onto a single service segment or message. Start Dialogue Request
Allows an application to pass sufficient information to a remote application to be able to initiate a contact between the two applications. Start Dialogue Confirm
Allows a remote application to pass sufficient information to the initiating application to notify it that the contact has been accepted. Start Dialogue Reject
Allows a remote application to transmit sufficient information to the initiating application to notify it that the contact cannot be accepted. Transfer Data
Allows one application to transfer business information to another application. Request Status
Allows an application to request status or control information from the other application in a contactReport Status (Reply)
Allows an application to send status or control information to the other application in a contact. This may be a reply to a request status, or as an unsolicited adjunct report.Suspend Conversation
Allows an application to request that a conversation be suspended until it requests that it be continued.Continue Conversation
Allows an application to request that a conversation be continued that it had previously requested to be suspended.Abandon Conversation
Allows an application to unconditionally terminate a contact if it cannot maintain the contactEnd Conversation Request
Allows an application to request that the other application in a contact terminate the contact. This function typically occurs at the end of a business transaction.End Conversation Acknowledge
Allows the responding application to confirm to the requesting application that the contact has been terminated.Complete Conversation Request
Allows an application to transmit enough information to a remote application to establish a contact, pass data, and terminate the contact in a single transmission between the two applications.
Full Dialog Confirmation
Allows a remote application to pass sufficient information to the initiating application to notify it of the acceptance of a connection, the return of data, and the termination of the connection in a single transmission.
B2 Data Requirements
Table B1 indicates how the abstract I-EDI functions are mapped into I-EDI service segments and messages, where the "s" (status) column indicates whether the segment is mandatory or conditional in the I-EDI function, and the "R" column indicates its repetition count. 8
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.