H.4.5 Print Job SOP Class

H.4.5.1 IOD Description

The Print Job IOD is an abstraction of the Print Job transaction and is the basic information entity to monitor the execution of the Print Process. A Print Job contains one film or multiple films, all belonging to the same film session.

The Print Job SOP Class is created by N-ACTION operation of the Film Session SOP Class, Film Box SOP Class, or Pull Print Request SOP Class. The Print Job SOP Instance is deleted after the films are printed or after a failure condition.

H.4.5.2 DIMSE Service Group

The DIMSE Services which are applicable to the IOD are shown below.

DIMSE Service Element Usage SCU/SCP
N-EVENT-REPORT M/M
N-GET U/M

The meaning of the Usage SCU/SCP is described in Section H.2.4.

This Section describes the behavior of the DIMSE Services which are specific for this IOD. The general behavior of the DIMSE Services is specified in PS 3.7.

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.

H.4.5.2.2 N-GET

The N-GET is used to retrieve an instance of the Print Job SOP Class.

H.4.5.2.2.1 Attributes

The Attributes which may be retrieved are shown in Table H.4-15.

Table H.4-15 N-GET ATTRIBUTES

Attribute Name Tag Usage SCU/SCP
Execution Status (2100,0020) U/M
Execution Status Info (2100,0030) U/M
Print Priority (2000,0020) U/M
Creation Date (2100,0040) U/U
Creation Time (2100,0050) U/U
Printer Name (2110,0030) U/U
Originator (2100,0070) U/U

The meaning of the Usage SCU/SCP is described in Section H.2.4.

H.4.5.2.2.2 Behavior

The SCU uses the N-GET to request the SCP to get a Print Job SOP Instance. The SCU shall specify in the N-GET request primitive the UID of the SOP Instance to be retrieved.

The SCP shall return the values for the specified Attributes of the specified SOP Instance.

The SCP shall return the status code of the requested SOP Instance retrieval. The meaning of success, warning, and failure status codes is defined in Section H.2.5.

H.4.5.3 Execution Status Information

Status Information is defined in PS 3.3. Implementation specific warning and error codes shall be defined in the Conformance Statement.

H.4.5.4 SOP Class Definition and UID

The Print Job SOP Class UID shall have the value “1.2.840.10008.5.1.1.14”.