N.7.3.2.3.1 SCU of the UPS Push SOP Class
N.7.3.2.3.1.1 SCU of the UPS Push SOP Class - N-CREATE
Table N.7-16 lists the Status Codes that the SCU of the UPS Push SOP Class supports for the N-CREATE message and defines the application behavior when encountering the listed Status Codes.
[Describe the behavior of the application when it receives any of the Status Codes listed in the table below, e.g., displaying and logging the error code or retrying the request. For each additional status code supported add a row to the table.
In the "Other status codes" row document the behavior of the application in case it encounters an unknown status code.]
Table N.7-16. Status Codes for N-CREATE of the UPS Push SOP Class - SCU
|
Service Status
|
Further Meaning
|
Status Code
|
Behavior
|
|
Success
|
The UPS was created as requested
|
0000
|
|
|
Warning
|
The UPS was created with modifications
|
B300
|
|
|
Attribute Value Out of Range
|
0116
|
|
|
Attribute List Error
|
0107
|
|
|
Failure
|
Duplicate invocation
|
0210
|
|
|
No such Attribute
|
0105
|
|
|
Invalid Attribute Value
|
0106
|
|
|
Attribute List Error
|
0107
|
|
|
Processing failure
|
0110
|
|
|
Duplicate SOP Instance
|
0111
|
|
|
Invalid SOP Instance
|
0117
|
|
|
No such SOP Class
|
0118
|
|
|
Missing Attribute
|
0120
|
|
|
Missing Attribute Value
|
0121
|
|
|
Refused: Not Authorized
|
0124
|
|
|
Unrecognized operation
|
0211
|
|
|
Mistyped argument
|
0212
|
|
|
Resource limitation
|
0213
|
|
|
Failed: The provided Value of UPS State was not "SCHEDULED".
|
C309
|
|
|
-
|
Other status codes
|
anything else
|
|
N.7.3.2.3.1.2 SCU of the UPS Push SOP Class Request UPS Cancel - N-ACTION
Table N.7-17 lists the Status Codes that the SCU of the Request UPS Cancel on UPS Push SOP Class supports for the N-ACTION message and defines the application behavior when encountering the listed Status Codes.
[Describe the behavior of the application when it receives any of the Status Codes listed in the table below, e.g., displaying and logging the error code or retrying the request. For each additional status code supported add a row to the table.
In the "Other status codes" row document the behavior of the application in case it encounters an unknown status code.]
Table N.7-17. N-ACTION of the UPS Push SOP Class Request UPS Cancel - SCU
|
Service Status
|
Further Meaning
|
Status Code
|
Behavior
|
|
Success
|
The cancel request is acknowledged
|
0000
|
|
|
Warning
|
The UPS is already in the requested state of CANCELED
|
B304
|
|
|
Failure
|
Class-instance conflict
|
0119
|
|
|
Duplicate invocation
|
0210
|
|
|
Invalid argument Value
|
0115
|
|
|
Invalid Object instance
|
0117
|
|
|
Mistyped argument
|
0212
|
|
|
No such action
|
0123
|
|
|
No such argument
|
0114
|
|
|
No such SOP Class
|
0118
|
|
|
No such SOP Instance
|
0112
|
|
|
Processing failure
|
0110
|
|
|
Resource limitation
|
0213
|
|
|
Unrecognized operation
|
0211
|
|
|
Refused: Not Authorized
|
0124
|
|
|
Failed: The UPS is already COMPLETED
|
C311
|
|
|
Failed: Performer chooses not to cancel
|
C313
|
|
|
Specified SOP Instance UID does not exist or is not a UPS Instance managed by this SCP
|
C307
|
|
|
Failed: The performer cannot be contacted
|
C312
|
|
|
-
|
Other status codes
|
anything else
|
|
N.7.3.2.3.1.3 SCU of the UPS Push SOP Class - N-GET
Table N.7-18 lists the Status Codes that the SCU of the UPS Push SOP Class supports for the N-GET message and defines the application behavior when encountering the listed Status Codes.
[Describe the behavior of the application when it receives any of the Status Codes listed in the table below, e.g., displaying and logging the error code or retrying the request. For each additional status code supported add a row to the table.
In the "Other status codes" row document the behavior of the application in case it encounters an unknown status code.]
Table N.7-18. Status Codes for N-GET of the UPS Push SOP Class - SCU
|
Service Status
|
Further Meaning
|
Status Code
|
Behavior
|
|
Success
|
Success
|
0000
|
|
|
Warning
|
Requested optional Attributes are not supported.
|
0001
|
|
|
Failure
|
Class-instance conflict
|
0119
|
|
|
Attribute List error
|
0107
|
|
|
Duplicate invocation
|
0210
|
|
|
Mistyped argument
|
0212
|
|
|
Invalid Object instance
|
0117
|
|
|
No such SOP Class
|
0118
|
|
|
No such SOP Instance
|
0112
|
|
|
Processing failure
|
0110
|
|
|
Resource limitation
|
0213
|
|
|
Unrecognized operation
|
0211
|
|
|
Refused: Not Authorized
|
0124
|
|
|
Failed: Specified SOP Instance UID does not exist or is not a UPS Instance managed by this SCP
|
C307
|
|
|
-
|
Other status codes
|
anything else
|
|
N.7.3.2.3.2 SCU of the UPS Pull SOP Class
N.7.3.2.3.2.1 SCU of the UPS Pull SOP Class - C-FIND
Table N.7-19 lists the Status Codes that the SCU of the UPS Pull SOP Class supports for the C-FIND message and defines the application behavior when encountering the listed Status Codes.
[Describe the behavior of the application when it receives any of the Status Codes listed in the table below, e.g., displaying and logging the error code or retrying the request. For each additional status code supported add a row to the table.
In the "Other status codes" row document the behavior of the application in case it encounters an unknown status code.]
Table N.7-19. Status Codes for C-FIND of the UPS Pull SOP Class - SCU
|
Service Status
|
Further Meaning
|
Status Code
|
Behavior
|
|
Success
|
Matching is complete - No final identifier is supplied
|
0000
|
|
|
Failure
|
Refused: Out of Resources
|
A700
|
|
|
Error: Data Set does not match SOP Class
|
A900
|
|
|
Failed: Unable to process
|
C000-CFFF
|
|
|
Failed: SOP Class Not Supported
|
0122
|
|
|
Cancel
|
Matching terminated due to cancel
|
FE00
|
|
|
Pending
|
Matches are continuing - Current Match is supplied and any Optional Keys were supported in the same manner as Required Keys.
|
FF00
|
|
|
Matches are continuing - Warning that one or more Optional Keys were not supported for existence for this Identifier
|
FF01
|
|
|
-
|
Other status codes
|
anything else
|
|
N.7.3.2.3.2.2 SCU of the UPS Pull SOP Class - N-GET
Table N.7-20 lists the Status Codes that the SCU of the UPS Pull SOP Class supports for the N-GET message and defines the application behavior when encountering the listed Status Codes.
[Describe the behavior of the application when it receives any of the Status Codes listed in the table below, e.g., displaying and logging the error code or retrying the request. For each additional status code supported add a row to the table.
In the "Other status codes" row document the behavior of the application in case it encounters an unknown status code.]
Table N.7-20. Status Codes for N-GET of the UPS Pull SOP Class - SCU
|
Service Status
|
Further Meaning
|
Status Code
|
Behavior
|
|
Success
|
Success
|
0000
|
|
|
Warning
|
Requested optional Attributes are not supported.
|
0001
|
|
|
Failure
|
Class-instance conflict
|
0119
|
|
|
Attribute List error
|
0107
|
|
|
Duplicate invocation
|
0210
|
|
|
Mistyped argument
|
0212
|
|
|
Invalid Object instance
|
0117
|
|
|
No such SOP Class
|
0118
|
|
|
No such SOP Instance
|
0112
|
|
|
Processing failure
|
0110
|
|
|
Resource limitation
|
0213
|
|
|
Unrecognized operation
|
0211
|
|
|
Refused: Not Authorized
|
0124
|
|
|
Failed: Specified SOP Instance UID does not exist or is not a UPS Instance managed by this SCP
|
C307
|
|
|
-
|
Other status codes
|
anything else
|
|
N.7.3.2.3.2.3 SCU of the UPS Pull SOP Class - N-SET
Table N.7-21 lists the Status Codes that the SCU of the UPS Pull SOP Class supports for the N-SET message and defines the application behavior when encountering the listed Status Codes.
[Describe the behavior of the application when it receives any of the Status Codes listed in the table below, e.g., displaying and logging the error code or retrying the request. For each additional status code supported add a row to the table.
In the "Other status codes" row document the behavior of the application in case it encounters an unknown status code.]
Table N.7-21. Status Codes for N-SET of the UPS Pull SOP Class - SCU
|
Service Status
|
Further Meaning
|
Status Code
|
Behavior
|
|
Success
|
Success
|
0000
|
|
|
Warning
|
Requested optional Attributes are not supported.
|
0001
|
|
|
Coerced invalid Values to valid Values
|
B305
|
|
|
Attribute Value Out of Range
|
0116
|
|
|
Attribute List error
|
0107
|
|
|
Failure
|
Class-instance conflict
|
0119
|
|
|
Duplicate invocation
|
0210
|
|
|
Invalid Attribute Value
|
0106
|
|
|
Mistyped argument
|
0212
|
|
|
Missing Attribute Value
|
0121
|
|
|
No such Attribute
|
0105
|
|
|
Attribute List error
|
0107
|
|
|
No such SOP Class
|
0118
|
|
|
No such SOP Instance
|
0112
|
|
|
Processing failure
|
0110
|
|
|
Resource limitation
|
0213
|
|
|
Unrecognized operation
|
0211
|
|
|
Refused: Not Authorized
|
0124
|
|
|
Failed: The UPS is not in the "IN PROGRESS" state
|
C310
|
|
|
Failed: The correct Transaction UID was not provided
|
C301
|
|
|
Failed: The UPS may no longer be updated
|
C300
|
|
|
Failed: Specified SOP Instance UID does not exist or is not a UPS Instance managed by this SCP
|
C307
|
|
|
-
|
Other status codes
|
anything else
|
|
N.7.3.2.3.2.4 SCU of the Change UPS State of UPS Pull SOP Class - N-ACTION
Table N.7-22 lists the Status Codes that the SCU of the Change UPS State of UPS Pull SOP Class supports for the N-ACTION message and defines the application behavior when encountering the listed Status Codes.
[Describe the behavior of the application when it receives any of the Status Codes listed in the table below, e.g., displaying and logging the error code or retrying the request. For each additional status code supported add a row to the table.
In the "Other status codes" row document the behavior of the application in case it encounters an unknown status code.]
Table N.7-22. Status Codes for N-ACTION of the UPS Pull SOP Class - SCU
|
Service Status
|
Further Meaning
|
Status Code
|
Behavior
|
|
Success
|
The requested state change was performed
|
0000
|
|
|
Warning
|
The UPS is already in the requested state of CANCELED
|
B304
|
|
|
The UPS is already in the requested state of COMPLETED
|
B306
|
|
|
Failure
|
Class-instance conflict
|
0119
|
|
|
Duplicate invocation
|
0210
|
|
|
Invalid argument Value
|
0115
|
|
|
Invalid Object instance
|
0117
|
|
|
Mistyped argument
|
0212
|
|
|
No such action
|
0123
|
|
|
No such argument
|
0114
|
|
|
No such SOP Class
|
0118
|
|
|
No such SOP Instance
|
0112
|
|
|
Processing failure
|
0110
|
|
|
Resource limitation
|
0213
|
|
|
Unrecognized operation
|
0211
|
|
|
Refused: Not Authorized
|
0124
|
|
|
Failed: The UPS may no longer be updated
|
C300
|
|
|
Failed: The correct Transaction UID was not provided
|
C301
|
|
|
Failed: The UPS is already IN PROGRESS
|
C302
|
|
|
Failed: The UPS may only become SCHEDULED via N-CREATE, not N-SET or N-ACTION
|
C303
|
|
|
Failed: The UPS has not met final state requirements for the requested state change
|
C304
|
|
|
Specified SOP Instance UID does not exist or is not a UPS Instance managed by this SCP
|
C307
|
|
|
Failed: The UPS is not yet in the "IN PROGRESS" state
|
C310
|
|
|
-
|
Other status codes
|
anything else
|
|
N.7.3.2.3.3 SCU of the UPS Watch SOP Class
N.7.3.2.3.3.1 SCU of the Un/Subscribe on UPS Watch SOP Class - N-ACTION
Table N.7-23 lists the Status Codes that the SCU of the Un/Subscribe of the UPS Watch SOP Class supports for the N-ACTION message and defines the application behavior when encountering the listed Status Codes.
[Describe the behavior of the application when it receives any of the Status Codes listed in the table below, e.g., displaying and logging the error code or retrying the request. For each additional status code supported add a row to the table.
In the "Other status codes" row document the behavior of the application in case it encounters an unknown status code.]
Table N.7-23. Status Codes for N-ACTION (subscribe/unsubscribe) of the UPS Watch SOP Class - SCU
|
Service Status
|
Further Meaning
|
Status Code
|
Behavior
|
|
Success
|
The requested change of subscription state was performed
|
0000
|
|
|
Warning
|
Deletion Lock not granted.
|
B301
|
|
|
Failure
|
Class-instance conflict
|
0119
|
|
|
Duplicate invocation
|
0210
|
|
|
Invalid argument Value
|
0115
|
|
|
Invalid Object instance
|
0117
|
|
|
Mistyped argument
|
0212
|
|
|
No such action
|
0123
|
|
|
No such argument
|
0114
|
|
|
No such SOP Class
|
0118
|
|
|
No such SOP Instance
|
0112
|
|
|
Processing failure
|
0110
|
|
|
Resource limitation
|
0213
|
|
|
Unrecognized operation
|
0211
|
|
|
Refused: Not Authorized
|
0124
|
|
|
Failed: Specified SOP Instance UID does not exist or is not a UPS Instance managed by this SCP
|
C307
|
|
|
Failed: Receiving AE-TITLE is Unknown to this SCP
|
C308
|
|
|
Failed: Specified action not appropriate for specified instance
|
C314
|
|
|
Failed: SCP does not support Event Reports
|
C315
|
|
|
-
|
Other status codes
|
anything else
|
|
N.7.3.2.3.3.2 SCU of the UPS Watch SOP Class - N-GET
Table N.7-24 lists the Status Codes that the SCU of the UPS Watch SOP Class supports for the N-GET message and defines the application behavior when encountering any the listed Status Codes.
[Describe the behavior of the application when it receives any of the Status Codes listed in the table below, e.g., displaying and logging the error code or retrying the request. For each additional status code supported add a row to the table.
In the "Other status codes" row document the behavior of the application in case it encounters an unknown status code.]
Table N.7-24. Status Codes for N-GET of the UPS Watch SOP Class - SCU
|
Service Status
|
Further Meaning
|
Status Code
|
Behavior
|
|
Success
|
Success
|
0000
|
|
|
Warning
|
Requested optional Attributes are not supported.
|
0001
|
|
|
Failure
|
Class-instance conflict
|
0119
|
|
|
Attribute List error
|
0107
|
|
|
Duplicate invocation
|
0210
|
|
|
Mistyped argument
|
0212
|
|
|
Invalid Object instance
|
0117
|
|
|
No such SOP Class
|
0118
|
|
|
No such SOP Instance
|
0112
|
|
|
Processing failure
|
0110
|
|
|
Resource limitation
|
0213
|
|
|
Unrecognized operation
|
0211
|
|
|
Refused: Not Authorized
|
0124
|
|
|
Failed: Specified SOP Instance UID does not exist or is not a UPS Instance managed by this SCP
|
C307
|
|
|
-
|
Other status codes
|
anything else
|
|
N.7.3.2.3.3.3 SCU of the UPS Watch SOP Class - C-FIND
Table N.7-25 lists the Status Codes that the SCU of the UPS Watch SOP Class supports for the C-FIND message and defines the application behavior when encountering the listed Status Codes.
[Describe the behavior of the application when it receives any of the Status Codes listed in the table below, e.g., displaying and logging the error code or retrying the request. For each additional status code supported add a row to the table.
In the "Other status codes" row document the behavior of the application in case it encounters an unknown status code.]
Table N.7-25. Status Codes for C-FIND of the UPS Watch SOP Class - SCU
|
Service Status
|
Further Meaning
|
Status Code
|
Behavior
|
|
Success
|
Matching is complete - No final identifier is supplied
|
0000
|
|
|
Failure
|
Refused: Out of Resources
|
A700
|
|
|
Error: Data Set does not match SOP Class
|
A900
|
|
|
Failed: Unable to process
|
C000-CFFF
|
|
|
Failed: SOP Class Not Supported
|
0122
|
|
|
Cancel
|
Matching terminated due to cancel
|
FE00
|
|
|
Pending
|
Matches are continuing - Current Match is supplied and any Optional Keys were supported in the same manner as Required Keys.
|
FF00
|
|
|
Matches are continuing - Warning that one or more Optional Keys were not supported for existence for this Identifier
|
FF01
|
|
|
-
|
Other status codes
|
anything else
|
|
N.7.3.2.3.3.4 SCU of the Request UPS Cancellation on UPS Watch SOP Class - N-ACTION
Table N.7-26 lists the Status Codes that the SCU of the Request UPS Cancellation on UPS Watch SOP Class supports for the C-ACTION message and defines the application behavior when encountering the listed Status Codes.
[Describe the behavior of the application when it receives any of the Status Codes listed in the table below, e.g., displaying and logging the error code or retrying the request. For each additional status code supported add a row to the table.
In the "Other status codes" row document the behavior of the application in case it encounters an unknown status code.]
Table N.7-26. Status Codes for N-ACTION (request cancel) of the UPS Watch SOP Class - SCU
|
Service Status
|
Further Meaning
|
Status Code
|
Behavior
|
|
Success
|
The cancel request is acknowledged
|
0000
|
|
|
Warning
|
The UPS is already in the requested state of CANCELED
|
B304
|
|
|
Failure
|
Class-instance conflict
|
0119
|
|
|
Duplicate invocation
|
0210
|
|
|
Invalid argument Value
|
0115
|
|
|
Invalid Object instance
|
0117
|
|
|
Mistyped argument
|
0212
|
|
|
No such action
|
0123
|
|
|
No such argument
|
0114
|
|
|
No such SOP Class
|
0118
|
|
|
No such SOP Instance
|
0112
|
|
|
Processing failure
|
0110
|
|
|
Resource limitation
|
0213
|
|
|
Unrecognized operation
|
0211
|
|
|
Refused: Not Authorized
|
0124
|
|
|
Failed: The UPS is already COMPLETED
|
C311
|
|
|
Failed: Performer chooses not to cancel
|
C313
|
|
|
Specified SOP Instance UID does not exist or is not a UPS Instance managed by this SCP
|
C307
|
|
|
Failed: The performer cannot be contacted
|
C312
|
|
|
-
|
Other status codes
|
anything else
|
|
N.7.3.2.3.4 SCU of the UPS Event SOP Class
N.7.3.2.3.4.1 SCU of the UPS Event SOP Class - N-EVENT-REPORT
Table N.7-27 lists the Status Codes that the SCU of the UPS Event SOP Class supports for the N-EVENT-REPORT message and defines the application behavior when encountering the listed Status Codes.
[Describe the behavior of the application when it receives any of the Status Codes listed in the table below, e.g., displaying and logging the error code or retrying the request. For each additional status code supported add a row to the table.
In the "Other status codes" row document the behavior of the application in case it encounters an unknown status code.]
Table N.7-27. Status Codes for the N-EVENT-REPORT of the UPS Event SOP Class - SCU
|
Service Status
|
Further Meaning
|
Status Code
|
Behavior
|
|
Success
|
|
0000
|
|
|
Failure
|
Class-instance conflict
|
0119
|
|
|
Duplicate invocation
|
0210
|
|
|
Invalid argument Value
|
0115
|
|
|
Invalid SOP Instance
|
0117
|
|
|
Mistyped argument
|
0212
|
|
|
No such event type
|
0113
|
|
|
No such argument
|
0114
|
|
|
No such SOP Class
|
0118
|
|
|
No such SOP Instance
|
0112
|
|
|
Processing failure
|
0110
|
|
|
Resource limitation
|
0213
|
|
|
Unrecognized operation
|
0211
|
|
|
-
|
Other status codes
|
anything else
|
|
N.7.3.2.3.5 SCP of the UPS Push SOP Class
N.7.3.2.3.5.1 SCP of the UPS Push SOP Class - N-CREATE
Table N.7-28 lists the Status Codes that the SCP of the UPS Push SOP Class supports for the N-CREATE message and defines conditions in which the listed Status Codes are sent.
[Describe the condition which causes the application to send the specific Status Codes. For each other status code used add a row to the table.]
Table N.7-28. Status Codes for N-CREATE of the UPS Push SOP Class - SCP
|
Service Status
|
Further Meaning
|
Status Code
|
Condition
|
|
Success
|
The UPS was created as requested
|
0000
|
|
|
Warning
|
The UPS was created with modifications
|
B300
|
|
|
Attribute Value out of Range
|
0116
|
|
|
Attribute List Error
|
0107
|
|
|
Failure
|
Duplicate invocation
|
0210
|
|
|
Duplicate SOP Instance
|
0111
|
|
|
Invalid Attribute Value
|
0106
|
|
|
Invalid SOP Instance
|
0117
|
|
|
Missing Attribute
|
0120
|
|
|
Missing Attribute Value
|
0121
|
|
|
Mistyped argument
|
0212
|
|
|
No such Attribute
|
0105
|
|
|
No such SOP Class
|
0118
|
|
|
Processing failure
|
0110
|
|
|
Resource limitation
|
0213
|
|
|
Unrecognized operation
|
0211
|
|
|
Refused: Not Authorized
|
0124
|
|
|
Failed: The provided Value of UPS State was not "SCHEDULED".
|
C309
|
|
N.7.3.2.3.5.2 SCP of Request UPS Cancel on UPS Push SOP Class - N-ACTION
Table N.7-29 lists the Status Codes that the SCP of the UPS Push SOP Class supports for the N-ACTION message and defines conditions in which the listed Status Codes are sent.
[Describe the condition which causes the application to send the specific Status Codes. For each other status code used add a row to the table.]
Table N.7-29. Status Codes for N-ACTION (request cancel) of the UPS Push SOP Class - SCP
|
Service Status
|
Further Meaning
|
Status Code
|
Condition
|
|
Success
|
The cancel request is acknowledged
|
0000
|
|
|
Warning
|
The UPS is already in the requested state of CANCELED
|
B304
|
|
|
Failure
|
Class-instance conflict
|
0119
|
|
|
Duplicate invocation
|
0210
|
|
|
Invalid argument Value
|
0115
|
|
|
Invalid Object instance
|
0117
|
|
|
Mistyped argument
|
0212
|
|
|
No such action
|
0123
|
|
|
No such argument
|
0114
|
|
|
No such SOP Class
|
0118
|
|
|
No such SOP Instance
|
0112
|
|
|
Processing failure
|
0110
|
|
|
Resource limitation
|
0213
|
|
|
Unrecognized operation
|
0211
|
|
|
Refused: Not Authorized
|
0124
|
|
|
Failed: The UPS is already COMPLETED
|
C311
|
|
|
Failed: Performer chooses not to cancel
|
C313
|
|
|
Specified SOP Instance UID does not exist or is not a UPS Instance managed by this SCP
|
C307
|
|
|
Failed: The performer cannot be contacted
|
C312
|
|
N.7.3.2.3.5.3 SCP of the UPS Push SOP Class - N-GET
Table N.7-30 lists the Status Codes that the SCP of the UPS Push SOP Class supports for the N-GET message and defines conditions in which the listed Status Codes are sent.
[Describe the condition which causes the application to send the specific Status Codes. For each other status code used add a row to the table.]
Table N.7-30. Status Codes for N-GET of the UPS Push SOP Class - SCP
|
Service Status
|
Further Meaning
|
Status Code
|
Condition
|
|
Success
|
Success
|
0000
|
|
|
Warning
|
Requested optional Attributes are not supported.
|
0001
|
|
|
Attribute List error
|
0107
|
|
|
Failure
|
Class-instance conflict
|
0119
|
|
|
Duplicate invocation
|
0210
|
|
|
Mistyped argument
|
0212
|
|
|
Invalid Object instance
|
0117
|
|
|
No such SOP Class
|
0118
|
|
|
No such SOP Instance
|
0112
|
|
|
Processing failure
|
0110
|
|
|
Resource limitation
|
0213
|
|
|
Unrecognized operation
|
0211
|
|
|
Refused: Not Authorized
|
0124
|
|
|
Failed: Specified SOP Instance UID does not exist or is not a UPS Instance managed by this SCP
|
C307
|
|
N.7.3.2.3.6 SCP of the UPS Pull SOP Class
N.7.3.2.3.6.1 SCP of the UPS Pull SOP Class - C-FIND
Table N.7-31 lists the Status Codes that the SCP of the UPS Pull SOP Class supports for the C-FIND message and defines conditions in which the listed Status Codes are sent.
[Describe the condition which causes the application to send the specific Status Codes. For each other status code used add a row to the table.]
Table N.7-31. Status Codes C-FIND of the UPS Pull SOP Class - SCP
|
Service Status
|
Further Meaning
|
Status Code
|
Condition
|
|
Success
|
Matching is complete - No final identifier is supplied
|
0000
|
|
|
Cancel
|
Matching terminated due to cancel
|
FE00
|
|
|
Failure
|
Refused: Out of Resources
|
A700
|
|
|
Error: Data Set does not match SOP Class
|
A900
|
|
|
Failed: Unable to process
|
C000-CFFF
|
|
|
Failed: SOP Class Not Supported
|
0122
|
|
|
Pending
|
Matches are continuing - Current Match is supplied and any Optional Keys were supported in the same manner as Required Keys.
|
FF00
|
|
|
Matches are continuing - Warning that one or more Optional Keys were not supported for existence for this Identifier
|
FF01
|
|
N.7.3.2.3.6.2 SCP of the UPS Pull SOP Class - N-GET
Table N.7-32 lists the Status Codes that the SCP of the UPS Pull SOP Class supports for the N-GET message and defines conditions in which the listed Status Codes are sent.
[Describe the condition which causes the application to send the specific Status Codes. For each other status code used add a row to the table.]
Table N.7-32. Status Codes for N-GET of the UPS Pull SOP Class - SCP
|
Service Status
|
Further Meaning
|
Status Code
|
Condition
|
|
Success
|
Success
|
0000
|
|
|
Warning
|
Requested optional Attributes are not supported.
|
0001
|
|
|
Attribute List error
|
0107
|
|
|
Failure
|
Class-instance conflict
|
0119
|
|
|
Duplicate invocation
|
0210
|
|
|
Mistyped argument
|
0212
|
|
|
Invalid Object instance
|
0117
|
|
|
No such SOP Class
|
0118
|
|
|
No such SOP Instance
|
0112
|
|
|
Processing failure
|
0110
|
|
|
Resource limitation
|
0213
|
|
|
Unrecognized operation
|
0211
|
|
|
Refused: Not Authorized
|
0124
|
|
|
Failed: Specified SOP Instance UID does not exist or is not a UPS Instance managed by this SCP
|
C307
|
|
N.7.3.2.3.6.3 SCP of the UPS Pull SOP Class - N-SET
Table N.7-33 lists the Status Codes that the SCP of the UPS Pull SOP Class supports for the N-SET message and defines conditions in which the listed Status Codes are sent.
[Describe the condition which causes the application to send the specific Status Codes. For each other status code used add a row to the table.]
Table N.7-33. Status Codes for N-SET of the UPS Pull SOP Class - SCP
|
Service Status
|
Further Meaning
|
Status Code
|
Condition
|
|
Success
|
Success
|
0000
|
|
|
Warning
|
Requested optional Attributes are not supported.
|
0001
|
|
|
Attribute Value Out of Range
|
0116
|
|
|
Attribute List error
|
0107
|
|
|
Coerced invalid Values to valid Values
|
B305
|
|
|
Failure
|
Class-instance conflict
|
0119
|
|
|
Duplicate invocation
|
0210
|
|
|
Invalid Attribute Value
|
0106
|
|
|
Mistyped argument
|
0212
|
|
|
Invalid Object instance
|
0117
|
|
|
Missing Attribute Value
|
0121
|
|
|
No such Attribute
|
0105
|
|
|
No such SOP Class
|
0118
|
|
|
No such SOP Instance
|
0112
|
|
|
Processing failure
|
0110
|
|
|
Resource limitation
|
0213
|
|
|
Unrecognized operation
|
0211
|
|
|
Refused: Not Authorized
|
0124
|
|
|
Failed: The UPS is not in the "IN PROGRESS" state
|
C310
|
|
|
Failed: The correct Transaction UID was not provided
|
C301
|
|
|
Failed: The UPS may no longer be updated
|
C300
|
|
|
Failed: Specified SOP Instance UID does not exist or is not a UPS Instance managed by this SCP
|
C307
|
|
N.7.3.2.3.6.4 SCP of the Change UPS State of UPS Pull SOP Class - N-ACTION
Table N.7-34 lists the Status Codes that the SCP of the Change UPS State of the UPS Pull SOP Class supports for the N-ACTION message and defines conditions in which the listed Status Codes are sent.
[Describe the condition which causes the application to send the specific Status Codes. For each other status code used add a row to the table.]
Table N.7-34. Status Codes for N-ACTION (change state) of the UPS Pull SOP Class - SCP
|
Service Status
|
Further Meaning
|
Status Code
|
Condition
|
|
Success
|
The requested state change was performed
|
0000
|
|
|
Warning
|
The UPS is already in the requested state of CANCELED
|
B304
|
|
|
The UPS is already in the requested state of COMPLETED
|
B306
|
|
|
Failure
|
Class-instance conflict
|
0119
|
|
|
Duplicate invocation
|
0210
|
|
|
Invalid argument Value
|
0115
|
|
|
Invalid Object instance
|
0117
|
|
|
Mistyped argument
|
0212
|
|
|
No such action
|
0123
|
|
|
No such argument
|
0114
|
|
|
No such SOP Class
|
0118
|
|
|
No such SOP Instance
|
0112
|
|
|
Processing failure
|
0110
|
|
|
Resource limitation
|
0213
|
|
|
Unrecognized operation
|
0211
|
|
|
Refused: Not Authorized
|
0124
|
|
|
Failed: The UPS may no longer be updated
|
C300
|
|
|
Failed: The correct Transaction UID was not provided
|
C301
|
|
|
Failed: The UPS is already IN PROGRESS
|
C302
|
|
|
Failed: The UPS may only become SCHEDULED via N-CREATE, not N-SET or N-ACTION
|
C303
|
|
|
Failed: The UPS has not met final state requirements for the requested state change
|
C304
|
|
|
Specified SOP Instance UID does not exist or is not a UPS Instance managed by this SCP
|
C307
|
|
|
Failed: The UPS is not yet in the "IN PROGRESS" state
|
C310
|
|
N.7.3.2.3.7 SCP of the UPS Watch SOP Class
N.7.3.2.3.7.1 SCP of the Un/Subscribe on UPS Watch SOP Class - N-ACTION
Table N.7-35 lists the Status Codes that the SCP of the Un/Subscribe on the UPS Watch SOP Class supports for the N-ACTION message and defines conditions in which the listed Status Codes are sent.
[Describe the condition which causes the application to send the specific Status Codes. For each other status code used add a row to the table.]
Table N.7-35. Status Codes for N-ACTION (Un/subscribe) ) of the UPS Watch SOP Class - SCP
|
Service Status
|
Further Meaning
|
Status Code
|
Condition
|
|
Success
|
The requested change of subscription state was performed
|
0000
|
|
|
Warning
|
Deletion Lock not granted.
|
B301
|
|
|
Failure
|
Class-instance conflict
|
0119
|
|
|
Duplicate invocation
|
0210
|
|
|
Invalid argument Value
|
0115
|
|
|
Invalid Object instance
|
0117
|
|
|
Mistyped argument
|
0212
|
|
|
No such action
|
0123
|
|
|
No such argument
|
0114
|
|
|
No such SOP Class
|
0118
|
|
|
No such SOP Instance
|
0112
|
|
|
Processing failure
|
0110
|
|
|
Resource limitation
|
0213
|
|
|
Unrecognized operation
|
0211
|
|
|
Refused: Not Authorized
|
0124
|
|
|
Failed: Specified SOP Instance UID does not exist or is not a UPS Instance managed by this SCP
|
C307
|
|
|
Failed: Receiving AE-TITLE is Unknown to this SCP
|
C308
|
|
|
Failed: Specified action not appropriate for specified instance
|
C314
|
|
|
Failed: SCP does not support Event Reports
|
C315
|
|
N.7.3.2.3.7.2 SCP of the UPS Watch SOP Class - N-GET
Table N.7-36 lists the Status Codes that the SCP of the UPS Watch SOP Class supports for the N-GET message and defines conditions in which the listed Status Codes are sent.
[Describe the condition which causes the application to send the specific Status Codes. For each other status code used add a row to the table.]
Table N.7-36. Status Codes for N-GET of the UPS Watch SOP Class - SCP
|
Service Status
|
Further Meaning
|
Status Code
|
Condition
|
|
Success
|
Success
|
0000
|
|
|
Warning
|
Requested optional Attributes are not supported.
|
0001
|
|
|
Attribute List error
|
0107
|
|
|
Failure
|
Class-instance conflict
|
0119
|
|
|
Duplicate invocation
|
0210
|
|
|
Mistyped argument
|
0212
|
|
|
Invalid Object instance
|
0117
|
|
|
No such SOP Class
|
0118
|
|
|
No such SOP Instance
|
0112
|
|
|
Processing failure
|
0110
|
|
|
Resource limitation
|
0213
|
|
|
Unrecognized operation
|
0211
|
|
|
Refused: Not Authorized
|
0124
|
|
|
Failed: Specified SOP Instance UID does not exist or is not a UPS Instance managed by this SCP
|
C307
|
|
N.7.3.2.3.7.3 SCP of the UPS Watch SOP Class - C-FIND
Table N.7-37 lists the Status Codes that the SCP of the UPS Watch SOP Class supports for the C-FIND message and defines conditions in which the listed Status Codes are sent.
[Describe the condition which causes the application to send the specific Status Codes. For each other status code used add a row to the table.]
Table N.7-37. Status Codes C-FIND of the UPS Watch SOP Class - SCP
|
Service Status
|
Further Meaning
|
Status Code
|
Condition
|
|
Success
|
Matching is complete - No final identifier is supplied
|
0000
|
|
|
Failure
|
Refused: Out of Resources
|
A700
|
|
|
Error: Data Set does not match SOP Class
|
A900
|
|
|
Failed: Unable to process
|
C000-CFFF
|
|
|
Failed: SOP Class Not Supported
|
0122
|
|
|
Cancel
|
Matching terminated due to cancel
|
FE00
|
|
|
Pending
|
Matches are continuing - Current Match is supplied and any Optional Keys were supported in the same manner as Required Keys.
|
FF00
|
|
|
Matches are continuing - Warning that one or more Optional Keys were not supported for existence for this Identifier
|
FF01
|
|
N.7.3.2.3.7.4 SCP of the Request UPS Cancellation on UPS Watch SOP Class - N-ACTION
Table N.7-38 lists the Status Codes that the SCP of the Request UPS Cancellation on UPS Watch SOP Class supports for the N-ACTION message and defines conditions in which the listed Status Codes are sent.
[Describe the condition which causes the application to send the specific Status Codes. For each other status code used add a row to the table.]
Table N.7-38. Status Codes for N-ACTION (cancel request) of the UPS Watch SOP Class - SCP
|
Service Status
|
Further Meaning
|
Status Code
|
Condition
|
|
Success
|
The cancel request is acknowledged
|
0000
|
|
|
Warning
|
The UPS is already in the requested state of CANCELED
|
B304
|
|
|
Failure
|
Class-instance conflict
|
0119
|
|
|
Duplicate invocation
|
0210
|
|
|
Invalid argument Value
|
0115
|
|
|
Invalid Object instance
|
0117
|
|
|
Mistyped argument
|
0212
|
|
|
No such action
|
0123
|
|
|
No such argument
|
0114
|
|
|
No such SOP Class
|
0118
|
|
|
No such SOP Instance
|
0112
|
|
|
Processing failure
|
0110
|
|
|
Resource limitation
|
0213
|
|
|
Unrecognized operation
|
0211
|
|
|
Refused: Not Authorized
|
0124
|
|
|
Failed: The UPS is already COMPLETED
|
C311
|
|
|
Failed: Performer chooses not to cancel
|
C313
|
|
|
Specified SOP Instance UID does not exist or is not a UPS Instance managed by this SCP
|
C307
|
|
|
Failed: The performer cannot be contacted
|
C312
|
|