DESC:FIELD OF INVENTION [0001] The embodiments herein generally relate to wireless communications systems. More particularly, related to a mechanism for sharing enriched information associated with a call. The present application is based on, and claims priority from an Indian Application Number 5820/CHE/2014 filed on 20th November, 2014, the disclosure of which is hereby incorporated by reference herein. BACKGROUND OF THE INVENTION [0002] Traditionally, services like voice and call associated data (i.e., web browsing, apps, or the like) are accessed independently by a user. Since, the call and data are accessed on different interfaces, it is difficult to access call and data at the same time even if they are related to each other thus, limiting the user experience. [0003] Thus, there is need of a simple and robust mechanism to share enriched information associated with a call and in a timely manner. OBJECT OF INVENTION [0004] The principal object of the embodiments herein is to provide a mechanism for sharing enriched information associated with a call and in a timely manner. [0005] Another object of the embodiments herein is to provide a mechanism for receiving, at a receiver device, a message comprising enriched information from a sender device, where the enriched information is received before establishing a call. [0006] Another object of the embodiments herein is to provide a mechanism for receiving, at a receiver device, a message comprising enriched information from a sender device, where the enriched information is received after establishing a call. [0007] Another object of the embodiments herein is to provide a mechanism for receiving, at a receiver device, a message comprising enriched information from a sender device, where the enriched information is received after terminating a call. [0008] Another object of the embodiments herein is to provide a mechanism for determining, at the receiver device, a correlation between the enriched information with the call. [0009] Another object of the embodiments herein is to provide a mechanism for displaying, at the receiver device, the enriched information based on the correlation. [0010] Yet another object of the embodiment herein is to provide a mechanism for sending, by a sender device, a message comprising enriched information to a receiver device, where the enriched information is sent before establishing a call. [0011] Yet another object of the embodiment herein is to provide a mechanism for sending, by a sender device, a message comprising enriched information to a receiver device, where the enriched information is sent after establishing a call. [0012] Yet another object of the embodiment herein is to provide a mechanism for sending, by a sender device, a message comprising enriched information to a receiver device, where the enriched information is sent after terminating a call. [0013] Yet another object of the embodiment herein is to provide a mechanism for receiving, by a server, a message comprising enriched information from a sender device, where the enriched information is received before establishing a call. [0014] Yet another object of the embodiment herein is to provide a mechanism for receiving, by a server, a message comprising enriched information from a sender device, where the enriched information is received after establishing a call. [0015] Yet another object of the embodiment herein is to provide a mechanism for receiving, by a server, a message comprising enriched information from a sender device, where the enriched information is received after terminating a call. SUMMARY [0016] Accordingly the embodiments herein provide a method for sharing enriched information associated with a call. The method includes receiving, at a receiver device, a message comprising enriched information from a sender device, where the enriched information is received before establishing a call, after establishing a call, or after terminating a call. Further, the method includes determining, at the receiver device, a correlation between the enriched information with the call. Further, the method includes displaying, at the receiver device, the enriched information based on the correlation. [0017] Accordingly the embodiments herein provide a method for sharing enriched information associated with a call. The method includes sending, by a sender device, a message comprising enriched information to a receiver device, where the enriched information is sent before establishing a call, after establishing a call, or after terminating a call. [0018] Accordingly the embodiments herein provide a method for receiving, by a server, a message comprising enriched information from a sender device, where the enriched information is received before establishing a call, after establishing a call, or after terminating a call. The method includes sending, by the server, the message to the receiver device. [0019] Accordingly the embodiments herein provide a receiver device for sharing enriched information associated with a call. The receiver device includes a memory and a processor coupled to the memory, where the processor coupled to the memory. The processor configured with processor executable instructions to receive a message including enriched information from a sender device, where the enriched information is received before establishing a call, after establishing a call, or after terminating a call. Further, the processor configured with processor executable instructions to determine a correlation between the enriched information with the call. Further, the processor configured with processor executable instructions to display the enriched information based on the correlation. [0020] Accordingly the embodiments herein provide a sender device for sharing enriched information associated with a call. The sender device includes a memory and a processor coupled to the memory, where the processor coupled to the memory. The processor configured with processor executable instructions to send a message comprising enriched information to a receiver device, where the enriched information is sent before establishing a call, after establishing a call, or after terminating a call. [0021] Accordingly the embodiments herein provide a server for sharing enriched information associated with a call. The server includes a memory and a processor coupled to the memory, where the processor coupled to the memory. The processor configured with processor executable instructions to receive a message comprising enriched information from a sender device, where the enriched information is received before establishing a call, after establishing a call, or after terminating a call. Further, the processor configured with processor executable instructions to send the message to the receiver device. [0022] Accordingly the embodiments herein provide a computer program product comprising computer executable program code recorded on a computer readable non-transitory storage medium, the computer executable program code when executed causing the actions including receiving, at a receiver device, a message comprising enriched information from a sender device, where the enriched information is received before establishing a call, after establishing a call, or after terminating a call. Further, the computer executable program code when executed causing the actions including determining, at the receiver device, a correlation between the enriched information with the call. Further, the computer executable program code when executed causing the actions including displaying, at the receiver device, the enriched information based on the correlation. [0023] Accordingly the embodiments herein provide a computer program product comprising computer executable program code recorded on a computer readable non-transitory storage medium, the computer executable program code when executed causing the actions including sending, by a sender device, a message comprising enriched information to a receiver device, where the enriched information is sent before establishing a call, after establishing a call, or after terminating a call. [0024] Accordingly the embodiments herein provide a computer program product comprising computer executable program code recorded on a computer readable non-transitory storage medium, the computer executable program code when executed causing the actions including receiving, by a server, a message comprising enriched information from a sender device, where the enriched information is received before establishing a call, after establishing a call, or after terminating a call. Further, the computer executable program code when executed causing the actions including sending, by the server, the message to the receiver device. [0025] These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. It should be understood, however, that the following descriptions, while indicating preferred embodiments and numerous specific details thereof, are given by way of illustration and not of limitation. Many changes and modifications may be made within the scope of the embodiments herein without departing from the spirit thereof, and the embodiments herein include all such modifications. BRIEF DESCRIPTION OF FIGURES [0026] This invention is illustrated in the accompanying drawings, throughout which like reference letters indicate corresponding parts in the various figures. The embodiments herein will be better understood from the following description with reference to the drawings, in which: [0027] FIG. 1 illustrates a wireless communication system for sharing enriched information associated with a call, according to an embodiment disclosed herein; [0028] FIG. 2 illustrates various units in a sender device, according to an embodiment disclosed herein; [0029] FIG. 3 illustrates various units in a receiver device, according to an embodiment disclosed herein; [0030] FIG. 4 illustrates various units in a server, according to an embodiment disclosed herein; [0031] FIG.5 is a flow diagram illustrating a method for sharing enriched information associated with a call by a sender device, according to an embodiment as disclosed herein; [0032] FIG. 6 is a flow diagram illustrating a method for displaying enriched information associated with a call on a receiver device, according to an embodiment as disclosed herein; [0033] FIG. 7 is a flow diagram illustrating a method for sharing enriched information associated with a call via a server, according to an embodiment as disclosed herein; [0034] FIG. 8 is a sequence diagram illustrating a method for sharing enriched information associated with a call in a session, according to an embodiment as disclosed herein; [0035] FIG. 9 is a sequence diagram illustrating a method for sharing enriched information associated with a call using a SIP message, according to an embodiment as disclosed herein; [0036] FIG. 10 is a sequence diagram illustrating a method for establishing an enriched call setup, where enriched information is shared initially followed by a call setup, according to an embodiment as disclosed herein; [0037] FIG. 11 is a flow diagram illustrating a method for establishing enriched call, where enriched information is shared initially followed by a call setup, according to an embodiment as disclosed herein; [0038] FIG. 12 is a sequence diagram illustrating a method for establishing an enriched call, where the call is setup initially followed by sharing enriched information associated with the call, according to an embodiment as disclosed herein; [0039] FIG. 13 is flow diagram illustrating a method establishing an enriched call, where the call is setup initially followed by sharing enriched information associated with the call, according to an embodiment as disclosed herein; [0040] FIG. 14 is a sequence diagram illustrating a method for sharing enriched information before establishing a call, according to embodiment as disclosed herein; [0041] FIG. 15 is a sequence diagram illustrating a method for sharing enriched information after establishing a call, according to an embodiment as disclosed herein; [0042] FIG. 16 is a sequence diagram illustrating a method for sharing enriched information after terminating a call, according to an embodiment as disclosed herein; and [0043] FIG. 17 illustrates a computing environment implementing the method for sharing enriched information associated with a call, according to an embodiment as disclosed herein. DETAILED DESCRIPTION OF INVENTION [0044] The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. Also, the various embodiments described herein are not necessarily mutually exclusive, as some embodiments can be combined with one or more other embodiments to form new embodiments. The term “or” as used herein, refers to a non-exclusive or, unless otherwise indicated. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein can be practiced and to further enable those skilled in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein. [0045] The embodiments herein disclose a method for sharing enriched information associated with a call. The method includes receiving a message including enriched information from a sender device. The enriched information is received before establishing a call, after establishing a call, or after terminating a call. Further, the method includes determining a correlation between the enriched information with the call. Further, the method includes displaying the enriched information based on the correlation. [0046] In an embodiment, the call is a Circuit Switched (CS) call or a Packet Switched (PS) call. [0047] In an embodiment, the message received from the sender device includes the enriched information and a call setup request when the call is the PS call. [0048] In an embodiment, a receiver device fetches the enriched information from at least one information source. [0049] In an embodiment, the enriched information is automatically accepted by the receiver device. [0050] In an embodiment, the enriched information includes sender provided information. [0051] Another object of the embodiment herein discloses a method for sharing enriched information associated with the call. The method includes sending a message comprising enriched information to the receiver device. The enriched information is sent before establishing a call, after establishing a call, or after terminating a call. [0052] In an embodiment, the sender device fetches the enriched information from the information source(s). [0053] Another object of the embodiment herein discloses a method for sharing enriched information associated with the call. The method includes receiving the message including the enriched information from the sender device. The enriched information is received before establishing the call, after establishing the call, or after terminating the call. Further, the method includes sending the message to the receiver device. [0054] In an embodiment, the server is an Enhance Visual Call (EVC) server. [0055] Unlike the conventional systems and methods, the proposed method provides a robust and simple mechanism for sharing the enriched information associated with the call thus, enhancing communication experience. The proposed method allows the user to enhance the standard (or plain) voice call experience. In an example, the sender can share the enriched information to receiver. The receiver receives the call and the enriched information such as a subject, a location, a picture, or the like is shared before establishing the call with a receiver device by a sender device. In another example, the sender or receiver can share the enriched information during the call. In another example, the sender can share the enriched information when the call is rejected or unanswered by the receiver. [0056] The labels “First” and “Second” are used for illustrative purpose and are not intended to limit the scope of the invention. Further, it is to be understood that the labels “First” and “Second” may be used interchangeably and can be plurality of devices. [0057] The Call described throughout the description refers to either Circuit Switched (CS) call or Packet Switched (PS) call. [0058] The words “Content source” and “Information source” are used interchangeably throughout the description. [0059] Referring now to the drawings, and more particularly to FIGS. 1 through 17, where similar reference characters denote corresponding features consistently throughout the figures, there are shown preferred embodiments. [0060] FIG. 1 illustrates a wireless communication system 100 for sharing enriched information associated with a call, according to an embodiment disclosed herein. In an embodiment, the wireless communication system 100 includes a sender device 102 and a receiver device 104. In another embodiment, in addition to the sender device 102 and the receiver device 104, the wireless communication system 100 includes a server (not shown) which helps in exchanging one or more signaling messages between the sender device 102 and the receiver device 104. The signaling messages are exchanged for sharing the enriched information associated with the call. The sender device 102 or the receiver device 104 can be, for example, a laptop, a desktop computer, a mobile phone, a smart phone, Personal Digital Assistants (PDAs), a tablet, a phablet, a consumer electronic device, dual display devices, or any other electronic device. [0061] In an embodiment, consider a scenario where a sender (i.e., can be referred as Enhanced Visual Call (EVC) user) associated with the sender device 102 tries to establish an enriched call with a receiver (i.e., can be referred as EVC user) associated with the receiver device 104. Before establishing the enriched call, the sender device 102 can be configured to send a message including the enriched information to the receiver device 104. In an embodiment, the sender device 102 sends the enriched information before establishing a call with the receiver device 104. In another embodiment, the sender device 102 sends the enriched information after establishing a call with the receiver device 104. In another embodiment, the sender device 102 sends the enriched information after terminating a call with the receiver device 104. The enriched information can be, for example, the text (i.e., plain text or real-time text), multimedia contents, profile information, Social Networking Site (SNS) content, web content, context of the call, location information, customer identifier, or the like. In an embodiment, the EVC user can be either the normal end user or the business end user where both need to have the EVC service subscription. [0062] After receiving the enriched information, the receiver device 104 can be configured to correlate the enriched information with the call. In an embodiment, the enriched information received by the receiver device 104 is associated (i.e., correlated) with the call. Therefore, to correlate the enriched information with the call, a common Extensible Markup Language (XML) structure is defined for the EVC specific events. In an embodiment, the XML structure is defined for the EVC specific events using the Converged IP Messaging (CPM) event framework. The element “enriched information () is the root EVC event element that appears under the element as described in [CPM-CONV-TS_2.1] section 6.7 “CPM Event Reporting Framework”, and includes “call correlation information (i.e., ) element”, which is used to uniquely identify the call associated with the enriched information. The call correlation information element can include one “from (i.e., ) element”, which is a unique identifier of the originating sender and can be either MSISDN or SIP URI. Further, the call correlation information element one “to (i.e., ) element, which is a unique identifier of the receiver and can either be Mobile Station International Subscriber Directory Number (MSISDN) or Session Initiation Protocol (SIP) Uniform Resource Locator (URL). [0063] Further, optionally, the call correlation information element can include one “call segment (i.e., ) element”, which is a unique identifier for identifying a Packet Switched (PS) call transaction. Further, optionally, the call correlation information element can include one “subject (i.e., ) element”, which is the information about the call added by the sender. In an embodiment, the maximum length of the subject field is 100 characters. Further, the call correlation information element can include any other elements which help in sharing the enriched information and establish the enriched call. [0064] Further, the enriched information element can include call associated data (i.e., ) element containing the enriched information that is being shared and have a “type” attribute to indicate the type of scenario. The possible values are “P2P” indicating person-to-person scenario, “b2c” indicating business-to-client scenario, or “wpc” indicating web and call scenario. Further, the enriched information element can include one or more link (i.e., ) elements for sharing a hyperlink such as a Hyper Text Transfer Protocol (HTTP) URL to the information to which the sender needs to associate the call. The URL may represent a reference user profile, blogs, SNS content, picture, a filled web form, or web content related to the call. [0065] Further, optionally, the enriched information element can include a location (i.e., ) element for sharing the sender’s location information. The location element can include element which represents the latitude and element which represents the longitude or any other representation of the location information. Further, optionally, the enriched information element can include a web reference identifier (i.e., ) element for sharing the sender’s web transaction reference associated with the browsing business web content information. Further, optionally, the enriched information element can include any other element. [0066] Further, the receiver device 104 can be configured to display the enriched information based on the correlation. In an embodiment, the receiver device 104 fetches the enriched information from at least one information source. In an example, consider a scenario where an EVC user-B (i.e., sender) tries to establish the call with an EVC user-A (i.e., receiver). The EVC user-B selects the contact of the EVC user-A; and the SNS content (i.e., enriched information) to be shared with the EVC user-A before placing the call. After receiving the SNS content, the EVC user-A views the SNS content of the EVC user-B before accepting the incoming call. Further, the EVC user-A can also share his/her SNS content with the EVC user-B thus, continuing the call. The EVC user-B can also view the SNS content of the EVC user-A during the ongoing call. [0067] In another example, consider a scenario where the sender tries to establish the call a pizza center. Before establishing the call, the sender shares the enriched information with the pizza center (i.e., receiver), where the information regarding the enriched information is displayed to the receiver. Further, the functionalities of the sender device 102 are explained in conjunction with the FIG. 2. The functionalities of the receiver device 104 are explained in conjunction with the FIG. 3. [0068] Unlike the conventional systems and methods, the proposed method enhances the standard (i.e., plain) voice call experience. In an example, the sender can share the enriched information to the receiver. The receiver can view the enriched information including the subject, the location, the picture, or the like while receiving the call from the sender (i.e., pre-call scenario). In another example, the sender can share the enriched information such as messages, files (or group of files like presentations), the location, the background, audio, video, or the like during the call (i.e., mid-call experience). In another example, the sender can share the enriched information with the receiver after terminating the call. [0069] In an embodiment, in case of a Circuit Switched (CS) call and a Packet Switched (PS) call, the enriched information can be shared in a separate message from the call. In another embodiment, in case of the PS call, the enriched information can be sent inside the call. When the enriched information is sent inside the call, then the process for correlating the enriched information associated with the call is eliminated. [0070] The FIG. 1 shows the limited overview of the wireless communication system 100 but, it is to be understood that other embodiments are not limited thereto. Further, the wireless communication system 100 can include any number of devices and a server. Further, the wireless communication system 100 includes any number of hardware or software components communicating with each other. By way of illustration, both an application running on a device and the device itself can be a component. [0071] FIG. 2 illustrates various units in a sender device 102, according to an embodiment as disclosed herein. In an embodiment, the sender device 102 includes a memory unit 202, a processor unit 204, a receiver (Rx) unit 206, and a transmitter (Tx) unit 208. [0072] The memory unit 202 may include one or more computer-readable storage media. The memory unit 202 may include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. In addition, the memory unit 202 may, in some examples, be considered a non-transitory storage medium. The term “non-transitory” may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term “non-transitory” should not be interpreted to mean that the memory unit 202 is non-movable. In some examples, the memory unit 202 can be configured to store larger amounts of information than the memory. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in Random Access Memory (RAM) or cache). [0073] The processor unit 204 can be configured to send the message including the enriched information to the receiver device 104 by using the Tx unit 208. In an embodiment, the processor unit 204 can be configured to send the enriched information before establishing the call with the receiver device 104. In another embodiment, the processor unit 204 can be configured to send the enriched information in parallel while establishing the call. In another embodiment, the processor unit 204 can be configured to send the enriched information after establishing the call. In another embodiment, the processor unit 204 can be configured to send the enriched information after terminating the call. Further, the processor unit 204 can be configured to fetch the enriched information from the information source(s). The Rx unit 206 communicates internally with the units and externally with the receiver device 104. Further, the functionalities of the sender device 102 are explained in conjunction with the FIGS. 8 – 16. [0074] In an embodiment, the call is the CS call or the PS call. In an embodiment, the message received from the sender device 102 includes the enriched information and a call setup request when the call is the PS call. In an example, the enriched information and the call setup request can be included in the same message and can be sent to the receiver device 104. [0075] The FIG. 2 shows exemplary units of the sender device 102 but it is to be understood that other embodiments are not limited thereon. In other embodiments, the sender device 102 may include less or more number of units. Further, the labels or names of the units are used only for illustrative purpose and does not limit the scope of the invention. One or more units can be combined together to perform same or substantially similar function in the sender device 102. [0076] FIG. 3 illustrates various units in the receiver device 104, according to an embodiment as disclosed herein. In an embodiment, the receiver device 104 includes a memory unit 302, a processor unit 304, a receiver (Rx) unit 306, and a transmitter (Tx) unit 308. [0077] The memory unit 302 may include one or more computer-readable storage media. The memory unit 302 may include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. In addition, the memory unit 302 may, in some examples, be considered a non-transitory storage medium. The term “non-transitory” may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term “non-transitory” should not be interpreted to mean that the memory unit 302 is non-movable. In some examples, the memory unit 302 can be configured to store larger amounts of information than the memory. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in Random Access Memory (RAM) or cache). [0078] The processor unit 304 can be configured to receive the message including the enriched information from the sender device 102 by using the Rx unit 306. In an embodiment, the processor unit 304 can be configured to receive the enriched information before establishing the call with the sender device 102. In another embodiment, the processor unit 304 can be configured to receive the enriched information after establishing the call with the sender device 102. In another embodiment, the processor unit 304 can be configured to receive the enriched information after terminating the call with the sender device 102. The processor unit 304 fetches the enriched information from the information source. [0079] Further, the processor unit 304 can be configured to determine the correlation between the enriched information and the call. Further, the processor unit 304 can be configured to display the enriched information based on the correlation. The Tx unit 308 communicates internally with the units and externally with the sender device 102. Further, the functionalities of the receiver device 104 are explained in conjunction with the FIGS. 8 – 16. [0080] The FIG. 3 shows exemplary units of the receiver device 104 but it is to be understood that other embodiments are not limited thereon. In other embodiments, the receiver device 104 may include less or more number of units. Further, the labels or names of the units are used only for illustrative purpose and does not limit the scope of the invention. One or more units can be combined together to perform same or substantially similar function in the receiver device 104. [0081] FIG. 4 illustrates various units in the server, according to an embodiment as disclosed herein. In an embodiment, the server 400 includes a memory unit 402, a processor unit 404, a receiver (Rx) unit 406, and a transmitter (Tx) unit 408. In an embodiment, the server can be an Enhanced Visual Call (EVC) server. [0082] The memory unit 402 may include one or more computer-readable storage media. The memory unit 402 may include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. In addition, the memory unit 402 may, in some examples, be considered a non-transitory storage medium. The term “non-transitory” may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term “non-transitory” should not be interpreted to mean that the memory unit 402 is non-movable. In some examples, the memory unit 402 can be configured to store larger amounts of information than the memory. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in Random Access Memory (RAM) or cache). [0083] The processor unit 404 can be configured to receive the message including the enriched information from the sender device 102. In an embodiment, the processor unit 404 can be configured to receive the enriched information before establishing the call. In another embodiment, the processor unit 404 can be configured to receive the enriched information after establishing the call. In another embodiment, the processor unit 404 can be configured to receive the enriched information after terminating a call. Further, the processor unit 404 can be configured to send the message to the receiver device 104. The Rx unit 406 and the Tx unit 408 communicates internally with the units and externally with the sender device 102 and the receiver device 104. Further, the functionalities of the server 400 are explained in conjunction with the FIGS. 8 – 16. [0084] The FIG. 4 shows exemplary units of the server 400 but it is to be understood that other embodiments are not limited thereon. In other embodiments, the server 400 may include less or more number of units. Further, the labels or names of the units are used only for illustrative purpose and does not limit the scope of the invention. One or more units can be combined together to perform same or substantially similar function in the server 400. [0085] FIG.5 is a flow diagram illustrating a method 500 for sharing the enriched information associated with the call by the sender device 102, according to an embodiment as disclosed herein. At step 502, the method 500 includes fetching the enriched information from the information source. The method 500 allows the processor unit 204 to fetch the enriched information from the information source. [0086] At step 504, the method 500 includes sending the message including the enriched information to the receiver device 104. The method 500 allows the processor unit 204 to send the message including the enriched information to the receiver device 104. In an embodiment, the enriched information is sent before establishing the call. In another embodiment, the enriched information is sent after establishing the call. In another embodiment, the enriched information is sent after terminating the call. [0087] The various actions, acts, blocks, steps, or the like in the method 500 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some of the actions, acts, blocks, steps, or the like may be omitted, added, modified, skipped, or the like without departing from the scope of the invention. [0088] FIG. 6 is a flow diagram illustrating a method 600 for displaying the enriched information associated with the call on the receiver device 104, according to an embodiment as disclosed herein. At step 602, the method 600 includes receiving the message including the enriched information from the sender device 102. The method 600 allows the processor unit 304 to receive the message including the enriched information from the sender device 102. In an embodiment, the enriched information is received before establishing the call. In another embodiment, the enriched information is received after establishing the call. In another embodiment, the enriched information is received before terminating the call. In an embodiment, the enriched information is fetched from the information source. [0089] At step 604, the method 600 includes determining the correlation between the enriched information with the call. The method 600 includes the processor unit 304 to determine the correlation between the enriched information with the call. At step 606, the method 600 includes displaying the enriched information based on the correlation. The method 600 allows the processor unit 304 to display the enriched information based on the correlation. [0090] The various actions, acts, blocks, steps, or the like in the method 600 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some of the actions, acts, blocks, steps, or the like may be omitted, added, modified, skipped, or the like without departing from the scope of the invention. [0091] FIG. 7 is a flow diagram illustrating a method 700 for sharing the enriched information associated with the call via the server 400, according to an embodiment as disclosed herein. The server 400 can be the EVC server. [0092] At step 702, the method 700 includes receiving the message including the enriched information from the sender device 102. The method 700 allows the server 400 to receive the message including the enriched information. At step 704, the method 700 includes sending the message to the receiver device 104. The method 700 allows the server 400 to send the message to the receiver device 104. [0093] The various actions, acts, blocks, steps, or the like in the method 700 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some of the actions, acts, blocks, steps, or the like may be omitted, added, modified, skipped, or the like without departing from the scope of the invention. [0094] FIG. 8 is a sequence diagram illustrating a method for sharing the enriched information associated with a call in a session, according to an embodiment as disclosed herein. In an embodiment, the sender device 102 includes an enriched client 102A, contents handling client 102B, and a call handling client 102C. Similarly, the receiver device 104 includes an enriched client 104A, contents handling client 104B, and a call handling client 104C. In an embodiment, the wireless communication system can include a content server 800A and Telephony AS 800B. The enriched client 102A, which resides in the sender device and allows the sender to use the EVC enabled services by interacting with other EVC functional components and other external entities. Similarly, the enriched client 104A, which resides in the receiver device and allows the receiver to use the EVC enabled services by interacting with other EVC functional components and other external entities. [0095] In an embodiment, consider a scenario where the sender (can be referred as EVC user) tries to place the enriched call request to the receiver (can be referred as EVC user) for sharing the enriched information. The enriched information can be, for example, the text (i.e., plain text or real-time text), multimedia contents, profile information, SNS content, web content, location information, or the like. In an embodiment, the EVC user can be either the normal end user or the business end user where both need to have the EVC service subscription. The signaling sequence 800 depicts communication between the sender device 102, the receiver device 104, and the server 400. [0096] In an embodiment, the server 400, which resides in the network domain and interacts with the enriched clients (i.e., enriched client 102A and enriched client 102A) and other network components such as EVC XML Document Management Server (XDMS), or other external entities; Further, the server 400 is a user-specific functional component. The functionalities are performed in the home network, and are invoked when servicing the requests from the EVC user. The server 400 handles requests related to EVC data, on behalf of the EVC user it serves and enforces EVC user preferences and service provider policies. Additionally, the server 400 is responsible for authorization and authentication of all the requests coming from or terminating into enriched client. The server 400 also handles enriched client registration, ensures data integrity and confidentiality, and user privacy. [0097] At step 802: The enriched client 102A of the sender device 102 obtains the enriched information (i.e., content, URL, or the like) for composing call correlation information (i.e., call-corrlelation-info) and EVC data (i.e., call-associated-data). [0098] At step 804: The enriched client 102A sends a SIP INVITE message to the server 400. In an embodiment, the SIP INVITE message includes EVC service related IP Multimedia Subsystem (IMS) Communication Service Identifier (ICSI) and IMS Application Reference Identifier (IARI) (i.e., ICSI: EVC, IARI: oma.evc). The SIP INVITE message is used to establish a SIP session with a Message Session Relay Protocol (MSRP) channel to transmit the enriched information. In an embodiment, the ICSI and IARI are used to distinctly identify the enriched calling scenarios. 3rd Generation Partnership Project (3GPP) has defined service and application identifiers to be used for IMS services. These identifiers can be used by both clients (i.e., sender device 102 and the receiver device 104) and network. The clients can use the identifiers to indicate their capability to the network. The EVC ICSI is urn-7:3gpp-service: ims.icsi.oma.evc. When enriched information sharing is to be defined as an application within the EVC service, the EVC service uses the IARI to explicitly identify itself. The IARI to be used for the EVC service may be: urn-7:3gpp-application.ims.iari.oma.evc. Further, the ICSI and the IARI are coded as Uniform Resource Name(s) (URNs) and included into a SIP message by using the two 3GPP defined media feature tags: g.3gpp.icsi-ref and g.3gpp.iari-ref, respectively. For example: • +g.3gpp.iari-ref="urn%3Aurn-7%3A3gpp-application.ims.iari.oma.evc • +g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.oma.evc [0099] Further, the following SIP messages can carry these service identifiers as described below: • INVITE (in Accept-Contact and Contact header) and subsequent 200 OK (in Contact header). • REGISTER (in Contact header, handling of service identifier in REGISTER method in the network is optional) and subsequent 200 OK (in Contact header). • OPTIONS (in Contact header of 200OK) • MESSAGE [00100] At step 806: After receiving the SIP INVITE message, the server 400 transmits the SIP INVITE message to the enriched client 104A of the receiver device 104, for sharing the enriched information. [00101] At step 808: The enriched client 104A automatically accepts (i.e., Auto_Accept) the SIP INVITE message received from the server 400 for receiving the enriched information. [00102] At step 810: After accepting the SIP INVITE message, the enriched client 104A sends 200 OK response message(s) to the server 400. The server 400 transmits the 200 OK response message(s) to the enriched client 102A. [00103] At step 812: After receiving the 200 OK response message, a MSRP channel is established between the enriched client 102A and the enriched client 104A. The MSRP channel is used to transmit XML payload containing the enriched information. In an embodiment, the enriched information is shared either in the form of a push message or a pull message. In an embodiment, a XML-based protocol is used to share the enriched information to the enriched client 104A. In an example, the structure of the enriched information is shown below: Structure of Enriched Information: [MSISDN or SIP URI] [MSISDN or SIP URI] < evc:call-seq>[CSeq#] < evc:subject>this is call subject < evc:call-associated-data type=”p2p”> [HTTP URL] 17.308688 77.695313