*DIMSE C-Service:

A subset of the DIMSE services that supports operations on Composite SOP Instances related to composite In-formation object definitions with peer DIMSE-service-users. The DIMSE-C services allow a DICOM Application Entity to explicitly request an operation by another DICOM Application Entity on Composite SOP Instances. The operations allowed are intended to be effectively compatible with those provided by previous versions of this standard. DIMSE-C provides only operation services. DIMSE-C provides the following operation services that are all confirmed services and as such a response is expected:

a. The C-STORE service is invoked by a DIMSE-service-user to request the storage of Composite SOP Instance information by a peer DIMSE-service-user.
b. The C-FIND service is invoked by a DIMSE-service-user to match a series of Attribute strings against the Attributes of the set of SOP Instances managed by a peer DIMSE-service-user. The C-FIND service returns 
  for each match a list of requested Attributes and their values.
c. The C-GET service is invoked by a DIMSE-service-user to fetch the information for one or more Composite SOP Instances from a peer DIMSE-service-user, based upon the Attributes supplied by the invoking DIMSE-  
  service-user.
d. The C-MOVE service is invoked by a DIMSE-service-user to move the information for one or more Composite SOP Instances from a peer DIMSE-service-user, to a third party DIMSE-service-user, based upon the 
  attributes supplied by the invoking DIMSE-service-user.
e. The C-ECHO service is invoked by a DIMSE-service-user to verify end-to-end communications with a peer DIMSE-service-user.

******************************************************************************************************************************************************************************************************************
*DIMSE N-Service:

DIMSE-N Services are services applicable only to a Normalized IOD. DIMSE-N Services provide both operation and notification services.

a. N-EVENT-REPORT Service: 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.
b. N-GET Service: The N-GET service is used by a DIMSE-service-user to retrieve Attribute values from a peer DIMSE-service-user. It is a confirmed service.
c. N-SET Service: The N-SET service is used by a DIMSE-service-user to request the modification of Attribute Values from a peer DIMSE-service-user. It is a confirmed service.
d. N-ACTION Service: The N-ACTION service is used by a DIMSE-service-user to request an action by a peer DIMSE-service-user. It is a confirmed service.
e. 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.
f. N-DELETE Service: The N-DELETE service is used by an invoking DIMSE-service-user to request a peer DIMSE-service-user to delete a managed SOP Instance and to de-register its identification. It is a confirmed 
  service.

******************************************************************************************************************************************************************************************************************
*Application Event Logging Service:

The Application Event Logging Service Class defines an application-level class-of-service that facilitates the network transfer of Event Log Records to be logged or recorded in a central location. The Application Event Logging Service Class addresses the class of application specific logs (e.g., procedural event logs) that are managed by a medical application. The Application Event Logging Service Class does not specify the means of accessing the central logs. SOP Classes of the Application Event Logging Service Class are implemented using the DIMSE-N N-ACTION service.

SCU Behavior: The SCU shall request logging of events that occur during a Study, using the N-ACTION request primitive. The SCU shall receive N-ACTION responses.

SCP Behavior: The SCP shall manage the creation of SOP Instances of the Procedure Log Storage Service. It shall receive, via the N-ACTION request primitive, requests for logging of events that occur during a Study. The SCP shall (consonant with application dependent constraints) incorporate those event records into a Procedure Log SOP Instance for the specified Study. The SCP shall return, via the N-ACTION response primitive, the N-ACTION Response Status Code applicable to the associated action request.

******************************************************************************************************************************************************************************************************************
*Relevant Patient Information Query Service:

The Relevant Patient Information Query Service Class defines an application-level class-of-service that facilitates the access to relevant patient information such as it is known at the time of query. The query information model consists of two entities with a one-to-one relationship: The Patient and the Patient Information. The Patient Information may be general, or specific to a particular imaging or procedure domain. A general SOP Class is defined along with some additional domain specific SOP Classes. C-FIND DIMSE-C Service is used in the construction of SOP Classes of the Relevant Patient Information Query Service Class.

SCU Behavior: The SCU requests that the SCP perform a match for the matching keys and return values for the Return Keys that have been specified in the Identifier of the request, against the Relevant Patient Information that the SCP possesses.

SCP Behavior: The SCP generates a C-FIND response for at most one match with an Identifier containing the values of all matching key attributes and all known Return Key Attributes requested. The response contains one relevant patient information instance in the form that matches the Template that was requested. This response shall contain a status of Pending. When the process of matching is complete, with zero or one match, a C-FIND response is sent with a status of Success and no Identifier.

******************************************************************************************************************************************************************************************************************
*Instance Availability Notification Service:

The Instance Availability Notification Service Class defines an application-level class-of-service that allows one DICOM AE to notify another DICOM AE of the presence and availability of SOP instances that may be retrieved. The AE from which such SOP Instance scan later be retrieved may or may not be the SCU performing the notification. The Instance Availability Notification Service Class consists of a single SOP Class: The Instance Availability Notification SOP Class. The SOP Class specifies Attributes, operations, and behavior applicable to the SOP Class. The conformance requirements shall be specified in terms of the Service Class Provider (SCP) and the Service Class User (SCU). The Instance Availability Notification Service Class uses the Instance availability notification IOD and the N-CREATE DIMSE-service.

SCU Behavior: The SCU shall specify in the N-CREATE request primitive the SOP Class and SOP Instance UIDs of the Instance Availability Notification SOP Instance that is created and for which attribute values are to be provided. The SCU shall provide Attribute values for the Instance Availability Notification SOP Class Attributes.

SCP Behavior: The SCP shall return, via the N-CREATE response primitive, the N-CREATE Response status code applicable to the associated request.

******************************************************************************************************************************************************************************************************************
*Storage Commitment Service:

In order to have medical image management in addition to medical image communication, there is a need for a Service Class within DICOM that ensures that there is an explicitly defined commitment to store the SOP Instances.
The Storage Commitment Service Class defines an application-level class-of-service that facilitates this commitment to storage. The Storage Commitment Service Class enables an Application Entity (AE) acting as an SCU to request another Application Entity (AE)acting as an SCP to make the commitment for the safekeeping of the SOP Instances (i.e., that the SOP Instances will be kept for an implementation specific period of time and can be retrieved). 
The AE where such SOP Instances can later be retrieved may be the SCP where storage commitment was accepted or it may be distinct from that SCP.

SCU Behavior: The SCU transmits the SOP Instances to the SCP using an appropriate mechanism. The request for storage commitment is transmitted to the SCP together with a list of references to one or more SOP Instances.

N-EVENT-REPORT: The Storage Commitment Result notification allows an SCP to inform the SCU whether or not it has accepted storage commitment responsibility for the SOP Instances referenced by a Storage Commitment Request. This notification is also used to convey error in-formation (i.e., storage commitment could not be achieved for one or more of the referenced SOP Instances).
This notification shall be invoked through the N-EVENT-REPORT primitive.

SCP Behavior: The SCP implementation defines how it provides its commitment to storage. Certain SCPs may commit to permanently store the SOP Instances (e.g., an archive system) while other SCPs may commit to provide storage of the SOP Instances for a limited amount of time.

******************************************************************************************************************************************************************************************************************
*Basic Worklist Management Service:

The Basic Worklist Management Service Class defines an application-level class-of-service that facilitates the access to worklists.
A worklist is the structure to present information related to a particular set of tasks. It specifies particular details for each task. The information supports the selection of the task to be performed first, and supports the performance of that task.

a. Modality Worklist(MWL): The Modality Worklist SOP class defined within the Basic Worklist Management Service Class defines an application-level class of service that facilitates the communication of information to the imaging modality about Scheduled Procedure Steps, and entities related to the Scheduled Procedure Steps. As will be detailed below, part of the information carried by the worklist mechanism is intended to be used by the imaging modality itself, but much of the information is intended to be presented to the modality operator.

SCU Behavior: An implementation that conforms to the Modality Worklist SOP Class shall support queries against the Worklist Information Model. An implementation that conforms to the Modality Worklist SOP Class as an SCU shall state in its Conformance Statement whether it requests matching on Optional Matching Key Attributes.

SCP Behavior: An implementation that conforms to the Modality Worklist SOP Class shall support queries against the Worklist Information Model.

******************************************************************************************************************************************************************************************************************
*Structured Reporting Storage SOP Classes:

The Structured Reporting Storage SOP Classes extend the functionality of the Storage Service class to extend the SCP behavior and conformance requirements.

SCU Behavior: The following has been documented in the implementation of the Structured Reporting Storage SOP Classes as an SCU : Basic Text SR, Extensible SR, Enhanced SR, and SOP Classes for which it is the Related General SOP Class ,Comprehensive 3D SR, Comprehensive SR, and SOP Classes for which they are the Related General SOP Classes, Mammography CAD SR ,Chest CAD SR ,Procedure Log ,X-Ray Radiation Dose SR ,Radiopharmaceutical Radiation Dose SR ,Spectacle Prescription Report, Colon CAD SR ,Macular Grid Thickness and Volume Report and Implantation Plan SR Document.

SCP Behavior: An SCP intending to display or otherwise render a Structured Report shall convey its full meaning in an unambiguous manner. Full meaning" includes not just the Content Tree (i.e., the Items of the Content Sequence), but all Attributes of the Data Set that are necessary to properly interpret the Structured Report. This includes those Attributes that set the initial Observation Context for the Content Tree, i.e., the patient, procedure, and observer identifiers, and the Completion status and Verification status of the Structured Report. For an SCP of a Structured Reporting Storage SOP Class that is displaying or otherwise rendering the structured report contained in a SOP Instance of the Class, the general form in which the structured report related Attributes are rendered.

******************************************************************************************************************************************************************************************************************
*DICOM DIR:

Provides a directory that facilitates access to the information stored in the files of a File-set based on key medical information. Such a directory facility relies on a hierarchical information model of medical summary information referencing the content of the files stored in a File-set on a storage medium. Standardizing such a directory function is a key element to facilitate the interchange of medical imaging data and is intended to support the complete range of modality imaging information. Directory Records serve to reference objects stored in the Files of the File-set.
The DICOMDIR File is identified by a single component File ID, DICOMDIR. Other files in the File-set may have File IDs made of a single component or multiple components.

SCU Behavior: It uses subset of the DIMSE services that supports operations of C-STORE, C-FIND, C-GET, C-MOVE. It supports the distribution of the directory information among a logical tree of several files (with the DICOMDIR file at its root).

SCP Behavior: The SCP implementation defines how it provides its DICOM DIR storage. The entire directory information is specified to be stored in a single File with a DICOMDIR File ID.

******************************************************************************************************************************************************************************************************************
*Media Creation Management Service: 
The Media Creation Management Service Class defines a mechanism by which an SCU can instruct a device to create Interchange Media containing a set of Composite SOP Instances that have already been transferred to the media creation device using the Storage Service Class.

SCU Behavior: The SCU transmits the SOP Instances to the SCP using the Storage Service Class. SCU shall invoke the N-CREATE and the N-ACTION operations. The Media Creation Management Service Class defines a mechanism by which an SCU can instruct a device to create Interchange Media containing a set of Composite SOP Instances that have already been transferred to the media creation device using the Storage Service Class. It is the responsibility of the SCU to negotiate and store instances with an appropriate Transfer Syntax should a specific Transfer Syntax be required by a requested profile. The Initiate Media Creation operation allows an SCU to request an SCP to create Interchange Media according to an already created Media Creation Management SOP Instance.

SCP Behavior: SCP shall support the N-CREATE, the N-ACTION and the N-GET operations. The SCP uses this operation to create a new media creation request containing the set of SOP Instances that shall be included in the Interchange Media. The application profile for the set of instances, which implies the form of the media created (i.e., CD, DVD or MOD), can either be left to the discretion of the SCP, or explicitly specified in the media creation request. In the latter case, if the device is unable to create the requested profiles, an error shall be returned. Success or failure of media creation is subsequently indicated by the SCU requesting the status from the SCP on the same or a separate association.

******************************************************************************************************************************************************************************************************************
*Ophthalmic Refractive Measurements Storage SOP Classes:

Refractive instruments are the most commonly used instruments in eye care. At present many of them have the capability for digital output, but their data is most often addressed by manual input into a paper or electronic record. Lensometry, Autorefraction, Keratometry, Subjective Refraction, and Visual Acuity Measurements SOP Classes support devices such as lensometers, auto-refractors, kerato-meters, autophoropters, and autoprojectors.

SCU Behavior: The SCU invokes a C-STORE DIMSE Service with a SOP Instance that meets the requirements of the corresponding IOD. The SCU shall recognize the status of the C-STORE service and take appropriate action upon the success or failure of the service.

SCP Behavior: An SCP of a Storage SOP Class acts as a performing DIMSE-service-user for the C-STORE Service. By performing this service successfully, the SCP indicates that the SOP Instance has been successfully stored.
******************************************************************************************************************************************************************************************************************
*Color Palette Storage Service:

The Color Palette Storage Service Class defines an application-level class-of-service that allows one DICOM AE to send a Color Palette SOP Instance to another DICOM AE. The Color Palette Storage Service Class consists of a single SOP Class: The Color Palette Storage SOP Class. It uses the Color Palette IOD that represents the Color Palette IE. The Color Palette Storage Service Class uses the C-STORE DIMSE Service.

SCU Behavior: Color Palette Storage Service Class uses the C-STORE DIMSE Service. The SCU shall recognize the status of the C-STORE service and take appropriate action based on the success or failure of the service. This SOP Class places no further requirements on what the SCU shall do other than that it shall distinguish between successful and failed C-STORE responses.

SCP Behavior: The SCP shall return, via the C-STORE response primitive, the Response Status Code applicable to the associated request. The SCP shall store and provide access to all attributes defined in the Color Palette IOD, as well as any Standard Extended Attributes included in the SOP Instance.
******************************************************************************************************************************************************************************************************************
*Color Palette Query/Retrieve Service Class:

The Color Palette Query/Retrieve Service Class defines an application-level class-of-service that facilitates access to Color Palette composite objects. This Service Class are implemented using the DIMSE-C C-FIND, C-MOVE and C-GET services.  It uses the Color Palette IOD that represents the Color Palette IE. The semantics of the C-MOVE and C-GET services are the same as those defined in the Service Definition of the Query/Retrieve Service Class.

SCU Behavior: Color Palette Query/Retrieve Service Class uses the C-FIND, C-MOVE and C-GET DIMSE Service. The SCU shall recognize the status of the response and take appropriate action based on the success or failure of the service.

SCP Behavior: The SCP shall return, via the DIMSE-C C-FIND, C-MOVE and C-GET services response primitive, the Response Status Code applicable to the associated request. The SCP shall process the respective request and provide access to all attributes defined in the Color Palette IOD.SCP generates the response of the respective request and send response to the SCU.
******************************************************************************************************************************************************************************************************************
*Softcopy Presentation State Storage SOP Classes:

The Softcopy Presentation State Storage SOP Classes extend the functionality of the Storage Service class to add the ability to convey an intended presentation state or record an existing presentation state. The SOP Classes specify the information and behavior that may be used to present (display) images that are referenced from within the SOP Classes.

SCU Behavior: The SCU of a Softcopy Presentation State Storage SOP Class Service request the SCP to store the Grayscale Softcopy Presentation State Storage SOP Instance and generate its Presentation State.

SCP Behavior: A device acting as an SCP of these SOP Classes shall make all mandatory presentation Attributes available for application to the referenced images at the discretion of the display device user, for all Image Storage SOP Classes for which the Softcopy Presentation State Storage SOP Class is supported.
******************************************************************************************************************************************************************************************************************
*Hanging Protocol Storage Service Class:

The Hanging Protocol Storage Service Class defines an application-level class-of-service that allows one DICOM AE to send a Hanging Protocol SOP Instance to another DICOM AE.

SCU Behavior: The DICOM AE that claims conformance to this SOP Class as an SCU shall be capable of sending a Hanging Protocol SOP Instance that meets the requirements of the Hanging Protocol IOD. It shall be invoked by the SCU through the use of the DIMSE C-STORE request used in conjunction with this SOP Class.

SCP Behavior: The DICOM AE that claims conformance to this SOP Class as an SCP shall receive a Hanging Protocol SOP Instance through the use of the DIMSE C-STORE service used in conjunction with this SOP Class.
******************************************************************************************************************************************************************************************************************
*Hanging Protocol Query/Retrieve Service Class:

The Hanging Protocol Query/Retrieve Service Class defines an application-level class-of-service that facilitates access to Hanging Protocol composite objects. It provides query and retrieve/transfer capabilities similar to the Basic Worklist Management Service Class and Query/Retrieve Service Class.

SCU Behavior: Hanging Protocol Query/Retrieve Service Class uses the C-FIND, C-MOVE and C-GET DIMSE Service. The SCU recognizes the status of the response and take appropriate action based on the success or failure of the service.
	
SCP Behavior: The SCP returns, via the DIMSE-C C-FIND, C-MOVE and C-GET services response primitive, the Response Status Code applicable to the associated request. The SCP processes the respective request and provide access to all attributes defined in the Hanging Protocol IOD. SCP generates the response of the respective request and send response to the SCU.  
******************************************************************************************************************************************************************************************************************
*Substance Administration Query Service Class:

The Substance Administration Query Service Class defines an application-level class-of-service that facilitates obtaining detailed in-formation about substances or devices used in imaging, image-guided treatment, and related procedures. It also facilitates obtaining approval for the administration of a specific contrast agent or drug to a specific patient.

SCU Behavior: Substance Approval Query SOP Class SCU supports queries against the Information Model using the baseline C-FIND SCU Behavior. Process for connection and association establishment is same as it is for C-Find DIMSE service.

SCP Behavior: Substance Administration Query Service Class SCP acts as a DICOM Application Entity(AE) which returns information about the Attributes of a substance, device, or a substance administration act. This information is organized into well-defined Substance Administration Query Information Models.
******************************************************************************************************************************************************************************************************************
*Instance and Frame Level Retrieve SOP Classes:

Composite Instance Root Retrieve Service is a service within the DICOM Query/Retrieve Service class. The retrieve capability of this service allows a DICOM AE to retrieve Composite Instances or selected frames from a remote DICOM AE over single Association or request the remote DICOM AE to initiate a transfer of Composite Object Instances or selected frames from image objects to another DICOM AE.

SCU Behavior: The Instance and Frame Level Retrieve SCU supplies Unique and Frame Range Key values to identify the requested SOP Instance(s) for C-Move and C-Get operation.

SCP Behavior: The Instance and Frame Level Retrieve SCP creates new SOP instances if necessary and then initiates C-STORE sub-operations for the corresponding storage SOP Instances. These C-STORE sub-operations occur on a different Association than the C-MOVE and C-Get service.
*******************************************************************************************************************************************************************************************************************
*Composite Instance Retrieve Without Bulk Data SOP Classes:

Composite Instance Retrieve Without Bulk Data Service is a service within the DICOM Query/Retrieve Service class. The retrieve capability of this service allows a DICOM AE to retrieve Composite Instances without retrieving their pixel data or other potentially large Attributes.

SCU Behavior: The SCU specifies one Instance UID or a list of Instance UIDs. SCUs of the Composite Instance Retrieve Without Bulk Data Service generate retrievals using the C-GET,under which it support the C-STORE sub-operations generated by the C-GET. 

SCP Behavior: The SCP shall identify a set of Entities at the level of the transfer based upon the values in the Unique Keys in the Identifier of the C-GET request. The SCP shall initiate C-STORE sub-operations for the identified SOP Instances, but shall not include in this C-STORE sub operation the Attributes described.
******************************************************************************************************************************************************************************************************************
*Implant Template Query/Retrieve Service Classes:

The Implant Template Query/Retrieve Service Classes define application-level classes-of-service that facilitate access to Implant Template and Implant Assembly Template composite objects.

SCU Behavior: Implant Template SCU is capable to send C-Find, C-Move and C-Get request to Implant Template SCP. Process for connection and association establishment is same as it is for other DIMSE services.

SCP Behavior: Implant Template SCP acts as a DICOM AE which possesses information about the Attributes of a number of Implant Template or Implant Assembly Template composite SOP Instances. The information is organized into an Information Model. It supports C-Find, C-get and C-Move operations.
******************************************************************************************************************************************************************************************************************
*Unified Procedure Step Service and SOP Classes:

The Unified Procedure Step Service Class provides for management of simple worklists, including creating new worklist items, querying the worklist, and communicating progress and results. A worklist is a list of Unified Procedure Step (UPS) instances. Each UPS instance unifies the worklist details for a single requested procedure step together with the result details of the corresponding performed procedure step. There is a one to one relationship between the procedure step request and the procedure step performed.

SCU Behavior: Unified Procedure Step Service and SOP Classes uses the N-ACTION, N-Set, N-Create-FIND, N-Event Report and N-GET DIMSE Services. The SCU recognizes the status of the response and take appropriate action based on the success or failure of the service
	
SCP Behavior: The SCP returns, via the N-ACTION, N-Set, N-Create-FIND, N-Event Report and N-GET DIMSE services response primitive, the Response Status Code applicable to the associated request. The SCP processes the respective request and provide access to all attributes defined in the UPS service Class. SCP generates the response of the respective request and send response to the SCU. 
******************************************************************************************************************************************************************************************************************
*RT Machine Verification Service Classes:

The RT Machine Verification Service Classes define an application-level class-of-service that facilitates the independent verification of geometric and dosimetric settings on a radiation delivery system prior to delivery of a radiation treatment. The service classes are intended for use with both conventional (e.g., photon, electron) as well as particle therapy (e.g., proton, ion) treatments.

SCU Behavior: RT Machine Verification SCU is the radiation delivery system used to administer the treatment. It initializes external verification of a new plan using the N-CREATE command. It uses the N-SET command request to instruct the SCP on the specified Attributes to be verified. It then requests that the verification start using an N-ACTION command. It may then optionally request the beam's verification parameters using an N-GET. It terminates the verification session at the Plan Level using an N-DELETE.

SCP Behavior: RT Machine Verification SCP acts as Machine Parameter Verifier (MPV). After it receives the N-Create request from SCU, it then retrieves the data necessary to perform verification through DICOM or other means. After receiving N-Action request the SCP compares the values of the specified Attributes against the values of the Attributes from the referenced plan, and signals the status of the verification using N-EVENT-REPORT command with the Treatment Verification Status (3008,002C) Attribute indicating the verification result.
******************************************************************************************************************************************************************************************************************
*Display System Management Service Class:

The Display System Service Class allows service users retrieve parameters related to the Display Subsystem(s).

SCU Behavior: Display System Management SCU uses the N-GET to request the SCP to provide the contents of a Display System SOP Instance. The SCU specifies in the N-GET request primitive the UID of the SOP Instance from which attributes are to be returned.

SCP Behavior: Display System Management SCP returns the values for the specified Attributes of the Display System SOP Instance. It also returns the status code for the requested SOP Instance retrieval.
*******************************************************************************************************************************************************************************************************************

*WADO -Web Access to DICOM Persistent Objects:

1.WADO-URI

DICOM URI Service defines several action types as C-GET, C-MOVE and C-STORE. This action retrieves the DICOM instances presented as per the request given by user. It does that by using HTTP Get method.

SCU Behavior: The parameters of the query component of the Request-URI are sent to the web Server through the HTTP GET method request.

SCP Behavior: As the request comes from SCU it match a set of Attributes against the Attributes of a set of composite SOP Instances maintained by SCU. SCP generates the response with the corresponding status to the SCU. The returned DICOM object shall be encoded using one of the transfer syntaxes specified in the transfer syntax query parameter. By default, the transfer syntax shall be "Explicit VR Little Endian".

2.WADO-WS Request/Response

The DICOM Web Service defines several action types as RetrieveImagingDocumentSet, RetrieveRenderedImagingDocumentSet, RetrieveImagingDocumentSetMetadata. It is Simple Object Access Protocol. It is a XML-based protocol for accessing services. It returns the corresponding document as per the respective request.

SCU Behavior: In WADO-WS Specific Web Services parameters to be used for the sending the request to the server as per the wsdl rule of particular action. The SCU transmits the SOP Instances to the SCP as mention in the web service parameters. SCU invoked the C-GET operation and send request to the respective server.

SCP Behavior: As per the request comes from SCU it match a set of Attributes against the Attributes of a set of composite SOP Instances maintained by SCU. SCP generates the response with the corresponding status to the SCU.

3.WADO-RS Request/Response

DICOM RESTful Service defines several action types as RetrieveStudy, RetrieveSeries, RetrieveInstance,RetrieveFrames,RetrieveMetadata. This action retrieves the DICOM instances presented as per the request given by user. Basically, it is REST Architecture based Web Services.

SCU Behavior: In WADO-RS Specific RESTful Services parameters to be used for the sending the request to the server by using particular action. The SCU transmits the SOP Instances to the SCP as mention in the rest service parameters of each action. SCU invoked the C-GET operation and send request to the respective server.

SCP Behavior: As per the request comes from SCU WADO-RS it match a set of attributes against the set of composite SOP Instances maintained by SCU.SCP generates the response with the corresponding status to the SCU and send the requested document to the SCU.

******************************************************************************************************************************************************************************************************************

*Security Profile:

1.Online Electronic Storage Secure Use Profile:

The Online Electronic Storage Secure Use Profile allows Application Entities to track and verify the status of SOP Instances. When communicating with an Application Entity that supports Storage service. This transfer occurs on a Secure Transport Connection layer. The two Application Entities involved in the transfer authenticate each other and confirm via the authentication process.

SCU Behavior: The transfer confirmed using the push model of the Storage Commitment Service Class. It generates C-Store Request and N-Action Request from SCU to send the storage request to the SCP. The sending Application Entity set the SOP Instance Status

SCP Behavior: The receiving Application Entity verifies the status of the SOP instance status. If it is modified then it may reject the request. Otherwise it stores the SOP instance into the given location using storage commitment push model.

2.The Basic TLS Secure Transport Connection Profile:

Basic TLS Secure Transport Connection Profile utilize the framework and negotiation mechanism specified by the Transport Layer Security. IP ports on which an implementation accepts TLS connections. It required the digital certificate and with keystore(JKS) at SCP and SCU side.

SCU Behavior: It generates the C-STORE request based on the TLS Secure Transport Connection layer with the digital certificate and Clientkeystore (JKS). It sends request to the SCP on the secure layer.

SCP Behavior: It verifies the request comes from the SCU on the basis of Digital Certificate and ServerKeyStore(JKS). If it is verified then process the request of C-STORE and store the file into specific location.

3.Digital Signature Profiles:

The Digital Signature Profile outlines the use of RSA encryption of a MAC to generate a Digital Signature which is then encrypted using a private RSA key. Typically, the certificate and associated private key used to produce Creator RSA Digital Signatures of the Application Entity.

SCU Behavior: SCU generates the C-STORE request with the Digitally Sign the DataSet using private key. It uses the digital certificate and key and add the digital signature with the dataset with the help of DSP signer and send request to the SCP.

SCP Behavior: SCP verifies the request by using verifier which Verify All the Digital Signatures present in Dataset. If the signature verified successfully then it processes the request create the response of C-STORE request and send it to the SCU.


4.Application Level Confidentiality Profiles:

The Basic DICOM Media Security Profile allows encapsulation of a DICOM File into a Secure DICOM File. It encrypts some confidential contents of the file and generates the secure Dicom file, for the further use where security is concern. Again, we can retrieve the contents of the original file by decryption. This security aspects security is addressed: confidentiality, integrity, data origin authentication.

SCU Behavior: It initialized the C-STORE request and encrypt the confidential data using the encryption algorithm AES, DES, TRIPPEL DES etc. It sends the encrypted data to the SCP for the storage purpose.

SCP Behavior: When SCU request arrives, SCP carries the process of Decrypt the data set using the key provided to re-identify the attributes. If the data is successfully decrypted then only it process the C-STORE request of the SCU. It generates the response of the respective request and send it to the SCU.

******************************************************************************************************************************************************************************************************************
*Print Management Service Class:

The Print Management Service Class defines an application-level class-of-service that facilitates the printing of images and image related data on a hard copy medium.

SCU Behavior: Print Management Service Class uses the N-ACTION, N-Set, N-Create, N-Delete, N-Event Report and N-GET DIMSE Services. The SCU recognizes the status of the response and take appropriate action based on the success or failure of the service.
	
SCP Behavior: The SCP returns, via the N-ACTION, N-Set, N-Create, N-Delete, N-Event Report and N-GET DIMSE services response primitive, the Response Status Code applicable to the associated request. The SCP processes the respective request and provide access to all attributes defined in the UPS service Class. SCP generates the response of the respective request and send response to the SCU. 
******************************************************************************************************************************************************************************************************************

*Media Storage Application Profiles :

The Media Storage Application Profiles Class defines an application-level class-of-service that allows to crate compress and Mail DICOMDIR File Set  .The Media Storage Application Profiles consists of a single Profile: Media Storage Application Profiles. It uses the DICOM IOD The Media Storage Application Profiles uses the  DIMSE M-Service.

SCP Behavior:The SCP shall return, via the M-Services and Media Storage Application Profiles, The SCP shall store, Generate, Compress DICOMDIR File-set on different media store. It also able to send  and read DICOMDIR File-Set via Mail.

******************************************************************************************************************************************************************************************************************

*Dicom Parser Serializers :

TheDicom Parser Serializers Classes defines an application-level class-of-service that allows to Parse Dicom Imagage Serially .The Dicom Parser Serializer also able to convert BMP and JPEG images images into Dicom.

SCU Behavior:The SCU shall return, via the DICOM Base, The SCU shall Convert into Dicom Formats and Serializes these images. 
