H.4.5.2.1 N-EVENT-REPORT

The N-EVENT-REPORT is used to report execution status changes to the SCU in an asynchronous way.

H.4.5.2.1.1 Attributes

The arguments of the N-EVENT-REPORT are defined as shown in Table H.4-14.

Note: The encoding of Notification Event Information is defined in PS 3.7.

Table H.4-14 NOTIFICATION EVENT INFORMATION

Event Type Name Event Type ID Attribute Tag Usage SCU/SCP
Pending 1 Execution Status Info (2100,0030) U/M
Film Session Label (2000,0050) U/U
Printer Name (2110,0030) U/U
Printing 2 Execution Status Info (2100,0030) U/M
Film Session Label (2000,0050) U/U
Printer Name (2110,0030) U/U
Done 3 Execution Status Info (2100,0030) U/M
Film Session Label (2000,0050) U/U
Printer Name (2110,0030) U/U
Failure 4 Execution Status Info (2100,0030) U/M
Film Session Label (2000,0050) U/U
Printer Name (2110,0030) U/U

H.4.5.2.1.2 Behavior

The SCP uses the N-EVENT-REPORT to inform the SCU about each execution change. The SCP shall only use the N-EVENT-REPORT within the context of the Association in which the Print Job SOP Instance was created.

Note: If SCU wants to monitor the complete execution process of a Print Job, then the SCU should only release the Association after the receipt of the event type Done or Failure.

The SCU shall return the confirmation from the N-EVENT-REPORT operation.

If the Event Type Name = Failure or Pending then the error/pending condition is stored in the Execution Status Info argument. The possible values of the Execution Status Info argument are defined in H.4.5.3.

If the Event Type Name = Failure or Done then the SCP shall delete the Print Job SOP Instance after receiving a confirmation from the SCU.