The N-EVENT-REPORT service is used by a DIMSE-service-user to report an event to a peer DIMSE-service-user. It is a confirmed service.
Table 10.1-1 lists the parameters for this service.
Table 10.1-1 N-EVENT-REPORT PARAMETERS
|DIMSE Parameter Name||Req/Ind||Rsp/Conf|
|Message ID Being Responded To||⎯||M|
|Affected SOP Class UID||M||U(=)|
|Affected SOP Instance UID||M||U(=)|
|Event Type ID||M||C(=)|
This parameter identifies the operation. It is used to distinguish this operation from other notifications or operations that the DIMSE-service-provider may have in progress. No two identical values for the Message ID (0000,0110) shall be used for outstanding operations or notifications.
Note: Τhe Message ID (0000,0110) is recommended to be unique within the scope of an Association, to support debug procedures.
This parameter specifies the Message ID (0000,0110) of the notification request/indication to which this response/confirmation applies.
For the request/indication, this parameter specifies the SOP Class of the SOP Instance for the event. It may be included in the response/confirmation. If included in the response/confirmation, this parameter shall be equal to the value in the request/indication.
For the request/indication, this parameter specifies the SOP Instance for the event. It may be included in the response/confirmation. If included in the response/confirmation, this parameter shall be equal to the value in the request/indication.
This parameter specifies the type of event being reported. It may be included in the success response/confirmation and shall be included if the Event Reply parameter is included.
Note: Service Class Specifications contained in PS 3.4 defines any application usage of the Event Type ID parameter.
This application-specific parameter contains information that the invoking DIMSE-service-user is able to supply about the event.
Note: Service Class Specifications contained in PS 3.4 defines any application usage of the Event Information parameter.
This application-specific parameter contains the optional reply to the event report. It may only be included in the success response/confirmation.
Note: Service Class Specifications contained in PS 3.4 defines any application usage of the Event Reply parameter.
This parameter contains the error or success notification for the operation. It shall be included by the performing DIMSE-service-user in any response/confirmation. The following types of status may occur:
⎯ class-instance conflict: the specified SOP Instance is not a member of the specified SOP class.
⎯ duplicate invocation: the Message ID (0000,0110) specified is allocated to another notification or operation.
⎯ invalid argument value: the event information value specified was out of range or otherwise inappropriate.
⎯ invalid SOP Instance: the SOP Instance UID specified implied a violation of the UID construction rules.
⎯ mistyped argument: one of the parameters supplied has not been agreed for use on the Association between the DIMSE-service-users.
⎯ no such argument: the event information specified was not recognized.
⎯ no such event type: the event type specified was not recognized.
⎯ no such SOP class: the SOP Class was not recognized.
⎯ no such SOP Instance: the SOP Instance was not recognized.
⎯ processing failure: a general failure in processing the operation was encountered.
⎯ resource limitation: the operation was not performed due to resource limitation.
⎯ success: successful notification.
⎯ unrecognized operation: the operation is not one of those agreed between the DIMSE-service-users.
The following N-EVENT-REPORT procedures apply:
a) The invoking DIMSE-service-user reports an event to the performing DIMSE-service-user by issuing an N-EVENT-REPORT request primitive to the DIMSE-service-provider.
b) The DIMSE-service-provider issues an N-EVENT-REPORT indication primitive to the performing DIMSE-service-user.
c) The performing DIMSE-service-user reports acceptance or rejection of the N-EVENT-REPORT request primitive by issuing an N-EVENT-REPORT response primitive to the DIMSE-service-provider.
d) The DIMSE-service-provider issues an N-EVENT-REPORT confirmation primitive to the invoking DIMSE-service-user, completing the N-EVENT-REPORT notification.
The performing DIMSE-service-user may return an N-EVENT-REPORT response primitive with the status of Failed or Refused before the entire N-EVENT-REPORT indication (Data Set) has been completely transmitted by the invoking DIMSE-service-user. A N-EVENT-REPORT response primitive with the status of Success or Warning shall not be returned until the entire N-EVENT-REPORT indication has been received by the performing DIMSE-service-user.
Note: Such an occurrence of a "Failed" response is often called an early failed response.