|
- |
C |
1 |
- |
Service string advice |
|
This segment is used to inform the receiver of the interchange that a set of service string characters which are different to the default characters are being used. |
|
| |
|
- |
M |
1 |
- |
Interchange header |
|
This segment is used to envelope the interchange, as well as to identify both, the party to whom the interchange is sent and the party who has sent the interchange. The principle of the UNB segment is the same as a physical envelope which covers one or more letters or documents, and which details, both the address where delivery is to take place and the address from where the envelope has come. |
|
| |
|
- |
M |
1 |
- |
Message header |
|
This segment is used to head, identify and specify a message. |
|
| |
|
- |
M |
99 |
- |
USH-USA-SG2 |
|
A group of segments identifying the security service and security mechanisms applied and containing the data necessary to carry out the validation calculations.
This segment group shall specify the security service and algorithm(s) applied to the referenced EDIFACT structure. Each security header group shall be linked to a security trailer group, and additionally linked to the USY segment(s). |
|
| |
|
- |
M |
1 |
- |
Security header |
|
A segment specifying a security service applied to the referenced EDIFACT structure. |
|
| |
|
- |
C |
3 |
- |
Security algorithm |
|
This segment is used to identify a security algorithm, the technical usage made of it, and contains the technical parameters required in order to generate the hash value. |
|
| |
|
- |
C |
2 |
- |
USC-USA |
|
A group of segments containing the data necessary to validate the security methods applied. |
|
| |
|
- |
M |
1 |
- |
Certificate |
|
This segment either contains information regarding the certificate, and identifies the certification authority which has generated the certificate, or is used to identify bilaterally interchanged signature keys. |
|
| |
|
- |
C |
3 |
- |
Security algorithm |
|
This segment is used to identify a security algorithm, the technical usage made of it, and contains the technical parameters required in order to generate the digital signature. |
|
| |
|
- |
M |
1 |
- |
Secured data identification |
|
This segment shall contain identification of the interchange sender and interchange recipient. |
|
| |
|
- |
M |
9999 |
- |
USX-USY |
|
This segment group shall be used to identify a party in the security process and to give security information for the referenced EDIFACT structure. |
|
| |
|
- |
M |
1 |
- |
Security references |
|
This segment shall contain references to EDIFACT structures (i.e., interchanges, groups or messages) to which security services were applied. |
|
| |
|
- |
M |
9 |
- |
Security on references |
|
This segment contains a link to the security header group and the result of the security services applied to the referenced EDIFACT structure (i.e., the digital signature) as specified in this linked security header group. |
|
| |
|
- |
M |
99 |
- |
UST |
|
A group of segments containing a link with security header segment group and the result of the security services applied to the message/package. |
|
| |
|
- |
M |
1 |
- |
Security trailer |
|
A segment establishing a link between security header and security trailer segment group, and stating the number of security segments in these groups. |
|
| |
|
- |
M |
1 |
- |
Message trailer |
|
A service segment ending a message, giving the total number of segments and the control reference number of the message. |
|
| |
|
- |
M |
1 |
- |
Interchange trailer |
|
This segment is used to provide the trailer of an interchange. |
|
| |
