10.1.5 N-CREATE SERVICE

The N-CREATE service is used by a DIMSE-service-user to request a peer DIMSE-service-user to create a new managed SOP Instance, complete with its identification and the values of its associated Attributes, and simultaneously to register its identification. It is a confirmed service.

10.1.5.1 N-CREATE parameters

Table 10.1-5 lists the parameters for this service.

Table 10.1-5N-CREATE PARAMETERS

DIMSE Parameter Name Req/Ind Rsp/Conf
Message ID M
Message ID Being Responded To M
Affected SOP Class UID M U(=)
Affected SOP Instance UID U C
Attribute List U U
Status M

10.1.5.1.1 Message ID

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: The Message ID (0000,0110) is recommended to be unique within the scope of an Association, to support debug procedures.

10.1.5.1.2 Message ID being responded to

This parameter specifies the Message ID (0000,0110) of the operation request/indication to which this response/confirmation applies.

10.1.5.1.3 Affected SOP class UID

For the request/indication, this parameter specifies the SOP Class of the new SOP Instance which is to be created by the performing DIMSE-service-user. The performing DIMSE-service-user assigns to the new SOP Instance, a set of Attribute Values as specified by the definition of its SOP Class. For the response/confirmation, this parameter specifies the SOP class of the SOP Instance which was created. 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.

10.1.5.1.4 Affected SOP instance UID

For the request/indication, this parameter specifies the SOP Instance which is used by the performing DIMSE-service-user. If the SOP Instance UID is not supplied by the invoking DIMSE-service-user, then the performing DIMSE-service-user assigns a value to this identification of instance. For the response/confirmation, this parameter may only be included in the success response/confirmation and shall be included if it is not supplied by the invoking DIMSE-service-user.

10.1.5.1.5 Attribute list

When this parameter is supplied by the invoking DIMSE-service-user, it contains a set of Attribute identifiers and values that the performing DIMSE-service-user is to assign to the new managed SOP Instance. When returned by the performing DIMSE-service-user, this parameter contains the complete list of all Attribute identifiers and values that were assigned to the new managed SOP Instance. It may be included in the success response/confirmation.

10.1.5.1.6 Status

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 type 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.

⎯ duplicate SOP Instance: the new managed SOP Instance Value supplied by the invoking DIMSE-service-user was already registered for a managed SOP Instance of the specified SOP Class.

⎯ invalid Attribute Value: the Attribute 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.

⎯ missing Attribute: a required Attribute was not supplied.

⎯ missing Attribute Value: a required Attribute Value was not supplied and a default value was not available.

⎯ mistyped argument: one of the parameters supplied has not been agreed for use on the Association between the DIMSE-service-users.

⎯ no such Attribute: the Tag for the specified Attribute 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 operation.

⎯ unrecognized operation: the operation is not one of those agreed between the DIMSE-service-users.

10.1.5.2 N-CREATE service procedures

The following N-CREATE procedures apply:

a) The invoking DIMSE-service-user requests the creation and registration of a new managed SOP Instance by issuing an N-CREATE request primitive to the DIMSE-service-provider.

b) The DIMSE-service provider issues an N-CREATE indication primitive to the performing DIMSE-service-user.

c) If the operation can be performed, the performing DIMSE-service-user creates and registers the new managed SOP Instance and generates a response indicating acceptance of the N-CREATE request primitive by issuing an N-CREATE response primitive to the DIMSE-service-provider. In this case the following procedure does not apply.

d) If the operation cannot be performed, then the performing DIMSE-service-user rejects the N-CREATE request by issuing an N-CREATE response primitive with the appropriate error code to the DIMSE-service-provider.

e) The DIMSE-service-provider issues an N-CREATE confirmation primitive to the invoking DIMSE-service-user, completing the N-CREATE operation.

The performing DIMSE-service-user may return an N-CREATE response primitive with the status of Failed or Refused before the entire N-CREATE indication (Data Set) has been completely transmitted by the invoking DIMSE-service-user. A N-CREATE response primitive with the status of Success or Warning shall not be returned until the entire N-CREATE 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.